A method for implementing domain address translation in a multi-domain scenario

Abstract

The present invention belongs to the technical field of video monitoring platform, and relates to a method for realizing domain address conversion in a multi-domain scenario, which at least includes a client, a user agent module, a streaming media module and a domain agent module; after processing, the streaming media module returns the stream URL address to the user agent module through a response; the user agent module receives the response of the streaming media, and transmits the stream URL address and the domain where the client is located to the domain agent module; the domain agent module can convert the original address into the target domain address where the client is located, and return it to the user agent module; the user agent module returns the stream address to the client, and pulls the audio and video stream from the streaming media. The present invention does not need to make special requirements for streaming media configuration, client configuration, and network equipment, and at the same time gets rid of the dependence on specific network equipment, ensuring that in a multi-domain environment, domain address conversion can be performed efficiently and smoothly.

Description

Technical Field

[0001] The present invention belongs to the technical field of video monitoring platforms, and in particular relates to a method for implementing network domain address conversion in a multi-domain scenario. Background Art

[0002] A video surveillance platform usually includes basic modules such as client proxy gateway, device access gateway, streaming gateway (or module), storage module, and its supporting client program. For the video surveillance industry, live broadcast and on-demand audio and video resources are the most basic business needs. Audio and video are often transmitted through common streaming protocols, such as rtsp, rtmp, http-flv, http-ws, hls protocols, etc., and the URL format is such as: rtsp: / / 192.168.1.10:554 / live / id_xxx; of course, there are also some private protocol transmission formats, but in general it can be regarded as a combination of a series of addresses and ports.

[0003] In actual application scenarios, a video surveillance platform will be deployed in a fixed network environment, but it often has to serve multiple relatively complex network environments. For example, the video surveillance platform is deployed in LAN A, and its access clients may be in: 1. Access from within LAN A in the same network environment as the video surveillance platform; 2. Access from within LAN B isolated from LAN A but with some ports connected through network devices such as routers or three-layer switches; 3. Access from home through the Internet. For the clients in these three different scenarios, it is not possible to return the same set of streaming media addresses and ports to access streaming media when they make video on demand requests.

[0004] Therefore, when the video surveillance platform receives a video-on-demand request and returns a streaming media URL address, it needs to provide different corresponding streaming media URL addresses to clients in different network environments.

[0005] Now the plan:

[0006] Solution 1: In the streaming media configuration, add multiple domain address configurations, and then return different network addresses according to the request type. For Solution 1, the streaming media module generally needs to support many protocol formats, such as rtsp, rtmp, http-flv, http-ws, hls, private protocols, etc. Each protocol has a different service port. This requires the streaming media itself to maintain multiple sets of domain addresses and ports, which greatly increases the design complexity and efficiency of streaming media. The complexity increases with the increase in domain types.

[0007] Solution 2: Directly use special network equipment, such as a gateway, to parse the message and replace the specific address and port in the message to ensure that when the other end receives it, it is a mapped and accessible address. For Solution 2: Existing network hardware equipment, such as a gateway, can only perform address conversion for standard communication protocols, such as the signaling of the GB / T 28181 protocol, and cannot parse private communication protocols, so the applicable scenarios are very limited. On the other hand, affected by the actual conditions of the project, many old network devices do not support similar address conversion functions.

[0008] Solution 3: Pre-configure the address and port information related to the streaming media in the current video surveillance platform at the client, then perform address conversion on the received streaming address, and then access the streaming. For Solution 3: It is necessary to provide client software with different configuration parameters for customers in different usage scenarios; and this solution is only applicable to the situation where the customer's computer is in a relatively fixed network environment. If the customer's computer often changes the network environment, the configuration of its client also needs to be modified and switched. All of the above greatly increases the subsequent operation and maintenance costs and affects the customer experience. Furthermore, when a third-party platform is connected to the video surveillance platform, and the streaming media resources need to be transmitted between platforms (such as the GB / T 28181 cascade scenario), there is no way to require the third-party platform to increase the configuration information of the streaming media address and port of the video surveillance platform.

[0009] Therefore, this field urgently needs a universal solution that can be applied to various complex network environments. The solution provided cannot change the configuration and design of the streaming media module due to changes in the complexity of the network environment. It needs to get rid of the dependence on special network equipment (such as network gateways) and does not require it to have the function of replacing the address information in the signaling; at the same time, it is necessary to solve the requirements for special configuration on the client side (individuals or third-party platforms). Summary of the invention

[0010] In view of the shortcomings in the current technical field, the purpose of the present invention is to propose a method for implementing domain address translation in a multi-domain scenario. This method does not require special requirements for streaming media configuration, client configuration, and network equipment, and at the same time gets rid of the dependence on specific network equipment (such as a network gate), ensuring that domain address translation can be performed efficiently and smoothly in a multi-domain environment. This method enables clients in different domains to successfully access streaming media resources, showing wide applicability and practicality.

[0011] To achieve the above-mentioned purpose, the technical solution adopted by the present invention is: a method for implementing domain address conversion in a multi-domain scenario, the method for implementing domain address conversion at least includes a client, a user agent module, a streaming media module and a domain agent module, wherein the user agent module is responsible for directly establishing a connection with the client program and processing various operations and requested services of the client program; the streaming media module is responsible for monitoring a fixed port, accepting client connections, and sending audio and video resources to the client; the domain agent module is used to maintain several groups of domain address mapping tables, and the domain agent module can convert the original address into the target domain address where the client is located;

[0012] The method for implementing domain address translation includes at least the following steps:

[0013] Step S1: The client logs in to the video surveillance platform, and the user agent module identifies and obtains the current network domain of the client through the login information of the client;

[0014] Step S2: The client sends a video-on-demand request to the user agent module;

[0015] Step S3: After receiving the on-demand request from the client, the user agent module forwards the message to the streaming media module;

[0016] Step S4: after the internal processing of the streaming media module, the streaming URL address is returned to the user agent module through a response;

[0017] Step S5: The user proxy module receives the response of the streaming media, and transmits the streaming URL address and the network domain where the client is located to the network domain proxy module;

[0018] Step S6: The domain proxy module can convert the original address into the target domain address where the client is located, and return it to the user proxy module;

[0019] Step S7: The user agent module returns the stream fetching address to the client. The signaling process is now completed, and the client can use the correct converted address to fetch the audio and video stream from the streaming media.

[0020] Furthermore, in step S6, the domain proxy module can convert the original address into the target domain address where the client is located, and the specific implementation steps are as follows:

[0021] S61, the network domain proxy module first finds the corresponding network domain mapping group in the network domain address mapping table according to the network domain where the client is located, and identifies the network domain where the current client is located;

[0022] S62, finding the mapped domain address in the domain mapping group using the streaming media address and port in the original URL as a key;

[0023] S63, then replace the original URL address, convert it to obtain the target address and destination port;

[0024] S64: Return the converted URL target address and destination port to the user agent module.

[0025] Furthermore, the multi-domain scenario includes at least an intranet domain and / or an Internet domain; wherein the number of the intranet domains is greater than or equal to M, and the number of the Internet domains is greater than or equal to N, wherein M is a natural number greater than or equal to 1, and N is a natural number greater than or equal to 1;

[0026] The video surveillance platform is deployed in any intranet domain, which contains M streaming media servers. M-1 routers are used to map the addresses and ports of the M streaming media servers in other intranet domains. N public network routers are used to map the addresses and ports of the M streaming media servers at the Internet domain exit.

[0027] The network proxy module is provided with more than one set of network address mapping tables, and each set of network address mapping tables contains at least a network domain name, a network domain ID, a source address, a source port, a destination address and a destination port.

[0028] Further, when a client in any intranet domain or any Internet domain obtains a stream, any one of the M streaming media servers returns a stream obtaining address to the domain proxy module to the client;

[0029] The network domain proxy module can query the network domain address mapping table through the network domain where the client is located, the source address and the source port, and obtain the destination address and the destination port;

[0030] The client can use the obtained destination address and destination port to correctly access the streaming media module, and use the streaming media module to send audio and video resource services to the client.

[0031] Furthermore, in a multi-domain scenario, it is only necessary to add and configure the corresponding address mapping relationship in the domain address mapping table according to the specific network configuration, without making any configuration changes to the streaming media, network hardware, and client, so that clients in different domains can access streaming media resources normally.

[0032] The present invention adopts the above technical solution, which has at least the following beneficial effects:

[0033] The network address conversion implementation method provided by the present invention does not change the configuration and design of the streaming media module due to the change in the complexity of the network environment, and shows a high degree of flexibility and adaptability. At the same time, this method gets rid of the dependence on specific network equipment (such as a network gate), and does not require it to have the function of replacing the address information in the signaling, thereby reducing the difficulty and cost of implementation. More importantly, it can effectively respond to and meet the special configuration requirements put forward by the client side (including individual users and third-party platforms), making it unaware of the specific network environment, ensuring that the client can stably and efficiently access streaming media resources in various complex network environments. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0035] Figure 1 It is a schematic diagram of the interaction between the modules in the method for implementing domain address translation of the present invention.

[0036] Figure 2 It is a schematic diagram of the network domain mapping table structure of the present invention.

[0037] Figure 3 It is a schematic diagram of an embodiment of a client accessing streaming media resources in a multi-domain scenario of the present invention.

[0038] Figure 4 It is a schematic diagram of an embodiment of the present invention including a network domain mapping table in a multi-domain scenario. DETAILED DESCRIPTION

[0039] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present invention. Instead, they are merely examples of devices and methods consistent with some aspects of the present invention as detailed in the appended claims.

[0040] See also Figure 1This embodiment provides a method for implementing domain address translation in a multi-domain scenario. The method for implementing domain address translation includes at least a client, a user agent module, a streaming media module and a domain agent module, wherein the user agent module is responsible for directly establishing a connection with the client program and processing various operations and requested services of the client program; the streaming media module is responsible for listening to a fixed port, accepting client connections, and sending audio and video resources to the client; the domain agent module is used to maintain a plurality of groups of domain address mapping tables, and the table structure is as follows Figure 2 As shown, the domain proxy module can convert the original address into the target domain address where the client is located; the domain address conversion implementation method includes at least the following steps:

[0041] Step S1, the client logs in to the video monitoring platform, and the user agent module identifies and obtains the current network domain of the client through the client's login information; Step S2, the client sends a video on-demand request to the user agent module; Step S3, after receiving the client's on-demand request, the user agent module forwards the message to the streaming media module; Step S4, after the streaming media module processes internally, the stream URL address is returned to the user agent module through a response; Step S5, the user agent module receives the response of the streaming media, and transmits the stream URL address and the network domain of the client to the domain agent module; Step S6, the domain agent module can convert the original address into the target domain address of the client, and return it to the user agent module; Step S7, the user agent module returns the stream address to the client, and the signaling process is completed. The client can use the correct address after conversion to pull audio and video streams from the streaming media.

[0042] As an implementation mode, in this embodiment, in step S6, the domain proxy module can convert the original address into the target domain address where the client is located, and the specific implementation steps are as follows:

[0043] S61. The domain proxy module first finds the corresponding domain mapping group in the domain address mapping table according to the domain where the client is located, and identifies the domain where the current client is located; S62. In the domain mapping group, the mapped domain address is found using the streaming media address and port in the original URL as the key; S63. The original URL address is then replaced and converted to obtain the target address and destination port; S64. The converted URL target address and destination port are returned to the user proxy module.

[0044] See also Figure 1 and Figure 2 , give a reference implementation case:

[0045] 1. Login interaction: The client logs in to the video surveillance platform through the user code. At this time, the user agent can obtain the client's network domain through the client login information: network domain X;

[0046] 2. Streaming request: The client sends a video-on-demand request to the user agent;

[0047] 3. Forwarding streaming request: After receiving the on-demand request from the client, the user agent forwards the message to the streaming media module;

[0048] 4. Streaming response: After internal processing by the streaming module, the streaming URL address is returned to the user agent through a response, such as: rtsp: / / 192.168.1.10:554 / live / abc;

[0049] 5. Request domain conversion: The user agent receives the response from the streaming media and passes the streaming URL address (rtsp: / / 192.168.1.10:554 / live / abc) and the domain where the client is located (domain X) to the domain proxy module;

[0050] 6. Domain conversion response: (1) The domain proxy module first finds the corresponding domain mapping group (domain X) according to the domain where the client is located;

[0051] (2) Use the streaming media address and port in the original URL as the key (i.e. 192.168.1.10:554) in the group to find the mapped domain address (i.e. 10.0.1.10:10554);

[0052] (3) Then replace the original URL address to get rtsp: / / 10.0.1.10:10554 / live / abc;

[0053] (4) Finally, the converted URL address is returned to the user agent;

[0054] 7. Stream retrieval response: The user agent returns the stream retrieval address to the client. The signaling process is now completed. The client can use the correct converted address to pull the audio and video stream from the streaming media.

[0055] As an implementation scheme, the multi-domain scenario in this embodiment includes at least an intranet domain and / or an Internet domain; wherein the number of the intranet domains is greater than or equal to M, and the number of the Internet domains is greater than or equal to N, wherein M is a natural number greater than or equal to 1, and N is a natural number greater than or equal to 1;

[0056] The video surveillance platform is deployed in any intranet domain, which contains M streaming media servers. M-1 routers are used to map the addresses and ports of the M streaming media servers in other intranet domains. N public network routers are used to map the addresses and ports of the M streaming media servers at the Internet domain exit.

[0057] The network proxy module is provided with more than one set of network address mapping tables, and each set of network address mapping tables contains at least a network domain name, a network domain ID, a source address, a source port, a destination address and a destination port.

[0058] As an implementation scheme, in this embodiment, when a client in any intranet domain or any Internet domain obtains a stream, any one of the M streaming media servers returns a stream obtaining address to the domain proxy module to the client;

[0059] The network domain proxy module can query the network domain address mapping table through the network domain where the client is located, the source address and the source port, and obtain the destination address and the destination port;

[0060] The client can use the obtained destination address and destination port to correctly access the streaming media module, and use the streaming media module to send audio and video resource services to the client.

[0061] As an implementation plan, in this embodiment, in a multi-domain scenario, it is only necessary to add and configure the corresponding address mapping relationship in the domain address mapping table according to the specific network configuration, without making any configuration changes to the streaming media, network hardware, and client, so that clients located in different domains can access streaming media resources normally.

[0062] like Figure 3 and Figure 4 As shown, in this embodiment, a multi-domain scenario is used as an example to illustrate:

[0063] like Figure 3 As shown in the figure, the company network consists of three isolated LANs, namely intranet domain A, intranet domain B, and intranet domain C. The video surveillance platform is deployed in intranet domain B, which contains three streaming media servers. The service ports of the three streaming media are all 554. Two routers map the three streaming media address ports in intranet domain A and intranet domain C respectively, and another public network router maps the three streaming media address ports to the public network exit. The customer's application scenario includes three types of domains, namely intranet domain A, intranet domain C, and the Internet. At this time, the domain mapping table is as follows Figure 4 shown.

[0064] When client 1 in intranet domain A obtains the stream, any of the three streaming media will return a stream obtaining address to it, assuming here: 192.168.1.11:554. Then the domain proxy can query table 2 through the client's domain A, source address 192.168.1.11, and source port 554, and obtain the only query result: 10.0.0.10:11554. Then client 1 can use 10.0.0.10:11554 to correctly access the streaming media;

[0065] Similarly, when client 2 in intranet domain C and client 3 in the Internet domain obtain traffic, the process is similar to the above.

[0066] In the above scenario, if there are more complex network environments, the solution only requires the operation and maintenance personnel to add and configure the corresponding address mapping relationship in the table according to the specific network configuration, without making any configuration changes to the streaming media, network hardware, and client, so that clients in different network domains can access streaming media resources normally.

[0067] The domain address conversion implementation method provided in this embodiment is designed for multi-domain scenarios and is intended to cope with various complex network environments. The method demonstrates efficient address conversion capabilities in a multi-domain environment, and has no specific requirements for streaming media configuration, client configuration, and network equipment, thereby ensuring its wide applicability. When dealing with complex network environments, this solution can maintain the stability of the streaming media module configuration and the consistency of the design, and is not affected by the complexity of the domain environment. At the same time, the method has no special functional requirements for network equipment, and does not require it to have the ability to replace address information in signaling. In addition, for the client side (including individual users and third-party platforms), the method also has no additional configuration requirements, further simplifying the deployment process. In summary, the method ensures the efficient and smooth execution of domain address conversion in a multi-domain environment, so that clients in different domains can access streaming media resources without obstacles, fully demonstrating its wide applicability and high practicality.

[0068] Although the embodiments of the present invention have been shown and described above, it will be appreciated that the above embodiments are exemplary and are not to be construed as limitations of the present invention. A person skilled in the art may change, modify, substitute and vary the above embodiments within the scope of the present invention.

Claims

1. A method for implementing domain address translation in a multi-domain scenario, characterized in that: The method for implementing domain address conversion includes at least a client, a user agent module, a streaming media module and a domain agent module, wherein the user agent module is responsible for directly establishing a connection with a client program and processing various operations and requested services of the client program; the streaming media module is responsible for monitoring a fixed port, accepting client connections, and sending audio and video resources to the client; the domain agent module is used to maintain a plurality of sets of domain address mapping tables, and the original address can be converted into a target domain address where the client is located through the domain agent module; The method for implementing domain address translation includes at least the following steps: Step S1: The client logs in to the video surveillance platform, and the user agent module identifies and obtains the current network domain of the client through the login information of the client; Step S2: The client sends a video-on-demand request to the user agent module; Step S3: After receiving the on-demand request from the client, the user agent module forwards the message to the streaming media module; Step S4: After the streaming media module processes, the streaming URL address is returned to the user agent module through a response; Step S5: The user proxy module receives the response of the streaming media, and transmits the streaming URL address and the network domain where the client is located to the network domain proxy module; Step S6: The domain proxy module can convert the original address into the target domain address where the client is located, and return it to the user proxy module; Step S7: The user agent module returns the stream fetching URL address to the client. The signaling process is now complete, and the client can use the converted correct address to fetch the audio and video stream from the streaming media. In step S6, the domain proxy module can convert the original address into the target domain address where the client is located. The specific implementation steps are as follows: S61, the network domain proxy module first finds the corresponding network domain mapping group in the network domain address mapping table according to the network domain where the client is located, and identifies the network domain where the current client is located; S62, finding the mapped domain address in the domain mapping group using the streaming media address and port in the original URL as a key; S63, then replace the original URL address, convert it to obtain the target address and destination port; S64: Return the converted URL target address and destination port to the user agent module.

2. The method according to claim 1, characterized in that: The multi-domain scenario includes at least an intranet domain and / or an Internet domain; wherein the number of the intranet domains is greater than or equal to M, and the number of the Internet domains is greater than or equal to N, wherein M is a natural number greater than or equal to 1, and N is a natural number greater than or equal to 1; The video surveillance platform is deployed in any intranet domain, which contains M streaming media servers. M-1 routers are used to map the addresses and ports of the M streaming media servers in other intranet domains. N public network routers are used to map the addresses and ports of the M streaming media servers at the Internet domain exit. The network proxy module is provided with more than one set of network address mapping tables, and each set of network address mapping tables contains at least a network domain name, a network domain ID, a source address, a source port, a destination address and a destination port.

3. The method according to claim 2, characterized in that: When a client in any intranet domain or any Internet domain obtains a stream, any one of the M streaming media servers returns a stream obtaining URL address to the domain proxy module to the client; The network domain proxy module can query the network domain address mapping table through the network domain where the client is located, the source address and the source port, and obtain the destination address and the destination port; The client can use the obtained destination address and destination port to correctly access the streaming media module, and use the streaming media module to send audio and video resource services to the client.

4. The method according to claim 3, characterized in that: In a multi-domain scenario, you only need to add and configure the corresponding address mapping relationship in the domain address mapping table according to the specific network configuration, without making any configuration changes to the streaming media, network hardware, and client, so that clients in different domains can access streaming media resources normally.

Images