CN113364849A

CN113364849A - DDS-based cross-wide area network dual-roaming data transmission method, system and storage medium

Info

Publication number: CN113364849A
Application number: CN202110609358.4A
Authority: CN
Inventors: 汪芸; 黄志勇; 雷媛元; 丘笑天; 罗其林
Original assignee: Nanjing Zhenrong Software Technology Co ltd
Current assignee: Nanjing Zhenrong Software Technology Co ltd
Priority date: 2021-06-01
Filing date: 2021-06-01
Publication date: 2021-09-07
Anticipated expiration: 2041-06-01
Also published as: CN113364849B

Abstract

The invention discloses a DDS-based cross-wide area network dual-roaming data transmission method, a system and a storage medium, wherein the method comprises the following steps: the first step is as follows: generating a unique identifier GUID for identifying a transmitting-receiving entity by using the application name and marking as AppName; the second step is that: exchanging data such as GUID, AppName, IP address and the like among gateways; the third step: mapping the GUID and the IP address; the fourth step: and addressing the transceiving entity based on the three steps to finish data transmission. The invention introduces the concept of data transceiving entity identifier to manage and convert GUID, application name and IP address. Through the operation, the DDS system supports the cross-wide area network, and simultaneously supports the roaming of the data transceiver in the wide area network environment, thereby providing effective support for the data roaming transmission of the cross-wide area network. A user does not need to pay attention to network composition and topology, and data transmission is carried out through a specified destination opposite terminal; the application can roam among the sub-networks, and the flexibility of the application is enhanced.

Description

DDS-based cross-wide area network dual-roaming data transmission method, system and storage medium

Technical Field

The invention relates to the field of computer networks, in particular to a DDS-based cross-wide area network dual-roaming data transmission method, a system and a storage medium.

Background

Compared with a wired network, a wireless network is easier to deploy and more flexible to use, and is widely applied to various research fields. The market growth speed of wireless networks is faster and faster, and the wireless networks become an indispensable important part in the life of people. Roaming is one of the important key services in network transmission, and supports that a mobile user can access the network for data transmission anywhere, so that the data transmission is not limited by the geographical position. Under the support of roaming service, mobile users can enjoy the convenience of mobile communication and acquire massive information in the internet. The roaming service greatly improves the network experience of the mobile user and meets the requirements of the mobile user.

Currently, most wireless networks belong to wireless communication networks with fixed infrastructure, in which a mobile subscriber needs to connect to one base station and the remaining data transmission work can be forwarded to other networks via the base station. The fixity of the base station enables the existing telecommunication roaming service to only support the roaming of a data sender, and not support the simultaneous roaming of a data transceiver.

Data Distribution Service (DDS), an efficient topic-based publish/subscribe Data model standard proposed by OMG. The method has the characteristic of taking data as a center, provides a global data space concept, and realizes decoupling in space and time. The node where the data is generated, i.e. the publisher (also called data writer), only needs to submit the generated data to the communication middleware, and the communication middleware transmits the data to the node needing the data, i.e. the subscriber (also called data reader) according to the information grasped by the communication middleware. The publisher and the subscriber do not need to know the existence and the position information of each other, and loose coupling of the publisher and the subscriber is achieved.

However, the DDS implements UDP multicast as a data space, so it does not support transmission across network segments and wide area networks, and the existing data roaming service does not support simultaneous roaming of data transceivers.

Disclosure of Invention

The purpose of the invention is as follows: aiming at the problems that the existing DDS system only supports a local area network and does not support a cross-wide area network, and the existing data roaming service only supports sender roaming and does not support simultaneous roaming of a sender and a receiver, the DDS-based cross-wide area network dual-roaming data transmission method is provided, and a system for realizing the method is further provided.

The technical scheme is as follows: in addition, the characteristic that the DDS supports data transceivers to simultaneously switch physical equipment is fully utilized to construct a more universal cross-wide area network data transmission mechanism, and effective support is provided for data roaming transmission in the cross-wide area network. In order to achieve the above object, the present invention adopts a technical solution of a DDS-based method for transmitting dual roaming data across a wide area network, which is characterized by comprising the following steps:

the first step is as follows: and (4) registering the user. Generating a unique identifier GUID for identifying a transmitting-receiving entity by using an application name AppName so as to complete the creation of the transmitting-receiving entity; the method comprises the following specific steps:

the registration process comprises a registration service flow, a user return processing flow and the like. The registration service flow consists of the following steps: (1) it is checked whether the AppName conflicts with an existing AppName. If yes, returning to null, otherwise, continuing to execute the following steps (2) - (4); (2) converting the AppName into a 4-byte abstract through a Hash function; (3) checking whether the abstract is repeated with the existing abstract, if so, the corresponding self-increment value of the abstract is + 1; (4) concatenate digest and selfie concatenate, store this information in a file, and return this value to the application, which represents the GUID key. The user return processing flow is composed of the following steps: (1) checking whether the GUID obtained from the registration service is empty; (2) if the GUID is not null, the GUID and domain number are stored locally and the entity is created with this information. If the GUID obtained in the first step is empty, it is checked whether the AppName is registered locally. If so, the entity is created with that AppName's information, otherwise an error is returned. The flow of user registration is shown in fig. 1.

The second step is that: exchanging data such as GUID, AppName, IP address and the like among gateways; the method comprises the following specific steps:

assume that two entities creating a DDS, called DP1 and DP2, are in two different local area networks. After creating the DP1 and DP2 entities, the gateway of the lan where the DP1 and DP2 are located records the GUID, AppName, and IP address of the two entities. In addition, in order to support data transmission across the wide area network, the gateway modifies the IP address, and the specific process is as follows: when the entity node DP1 in the DDS is on line, it will send its own Data (p1) to the subnet gateway where it is located, the Data (p1) includes GUID, AppName and IP address of DP 1. After receiving the data, the gateway modifies the IP address into the gateway address of itself to generate a new data entity

Will be

Sending to other gateways, and recording after other gateways receive

Will also be modified

The IP address is modified into the gateway address of the IP address, and a new data entity is generated

Continue to make a pair

And forwarding is carried out. The inter-gateway data exchange process is shown in fig. 2.

The third step: mapping the GUID and the IP address; the method comprises the following specific steps:

ZR-GAIPM performs designated peer-to-peer delivery, finds the entity's IP address information based on the GUID the user has come in, and then sends the data to that address. The specific flow is that (1) when a data writer and a data reader of ZR-GAIPM match, information is exchanged, wherein the exchanged information comprises the GUID and the IP address used by the reader. The ZR-GAIPM bottom layer will keep this information so that it can find the IP address used by the entity based on the entity's GUID. (2) When a data writer specifies the peer to send data, the GUID of the entity (which may be a domain participant or a data reader) is passed in. And the ZR-GAIPM bottom layer finds corresponding address information according to the GUID of the transmitted entity and then sends data to the address. The ZR-GAIPM also carries the GUID of the entity in the packet when sending data to ensure that only this entity can receive the data.

The fourth step: based on the working contents of the three steps, addressing of the transmitting and receiving entity is carried out to complete data transmission; the method comprises the following specific steps:

when the DP1 sends data to the DP2, the data is sent to the subnet gateway 1 of the subnet where the DP1 is located, the subnet gateway 1 finds the next hop subnet gateway 2 according to the mapping relation between the GUID and the IP address, the data is sent to the subnet gateway 2, and the gateway 2 matches the data to the node DP2 in the subnet according to the mapping relation between the GUID and the IP address. Finally, the data is sent to the DP2, completing the data transmission across the wide area network. The data transfer process is shown in fig. 3.

Through the steps, data roaming receiving and sending under the roaming scene of the receiver and the sender are completed.

Has the advantages that: (1) by introducing a gateway node, the DDS-based data communication across the wide area network is realized; (2) by means of the GUID and AppName mapping relation maintained and exchanged among the gateways, a user can carry out addressing and data transmission through a specified destination opposite terminal without paying attention to network composition and topology; (3) by means of the GUID and IP address mapping relation maintained and exchanged between gateways, the application can roam between subnets, and the application flexibility is enhanced.

Drawings

Fig. 1 is a user registration flow diagram.

Fig. 2 is a diagram of inter-gateway data exchange.

Fig. 3 is a diagram of data transmission between transceiving entities.

FIG. 4 is a block diagram of ZR-GAIPM.

FIG. 5 is a diagram of a GUID structure.

Fig. 6 is a diagram of a system architecture before roaming.

Fig. 7 is a diagram of the system after roaming.

Fig. 8 is a flow chart of a method of dual roaming data transmission across wide area networks.

Detailed Description

In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is further described in detail below with reference to the accompanying drawings. It should be understood that the detailed description and specific examples, while indicating the invention, are intended for purposes of illustration only and are not intended to limit the scope of the invention.

The first embodiment is as follows:

a frame diagram of a DDS-based cross-wan dual-roaming data transmission method of the present invention is shown in fig. 3. The frame diagram consists of four modules, namely a user registration module, an internetwork data exchange module, a GUID and IP mapping module and a data transmission module. The data interaction relationship among the modules is shown in FIG. 4. When a user registers, the user registration module firstly provides the name of the application, namely the AppName, then generates a GUID through a Hash function by using the AppName, and finally returns the GUID to the user.

The data exchange module between networks firstly creates DDS entities in different interconnected local area networks, and after the entities are created, the gateway where the entities are located records the information of GUID, AppName, IP address and the like of the entities. After a certain entity is online, data such as a GUID, an AppName, an IP address and the like of the entity are sent to a subnet gateway where the entity is located, the gateway can record the data after receiving the data, and also modify the IP address into a gateway address of the entity, and then forward the GUID, the AppName and a new IP address to an interconnected gateway, so that the interconnected gateway can record the received data on one hand, and on the other hand, continuously modify the IP address in the received data and forward the IP address to other interconnected gateways. The introduction of GUID and the exchange of GUID, AppName, IP address and other operations between gateways enable the DDS system to support the data transmission across the wide area network, and in addition, because the DDS system supports the simultaneous roaming of the transceivers, the method also solves the problem that the current data roaming service does not support the simultaneous roaming of the transceivers.

After the GUID and IP mapping module is operated by the data exchange module between networks, the mapping relation between the GUID and the IP address of the entity in the network can be obtained. When a data writer (also called a data sender) sends data to a data reader (also called a data receiver), the data writer firstly transmits the GUID (the entity may be a domain participant or may be a data reader) of the entity, and then the bottom layer of the ZR-GAIPM matches the GUID of the transmitting entity according to the GUID and the mapping content of the IP address which are stored in the second step, and locates the IP address of the GUID of the transmitting entity so as to complete the mapping of the GUID and the IP address.

The data transmission module carries out addressing of the transceiving entity based on the data of the user registration module, the inter-network data exchange module and the GUID and IP mapping module to complete data transmission; the method comprises the following specific steps:

when a data sender sends data, firstly, a subnet gateway where the sender is located locates an address of a receiver (directly sends or sends the address to a subnet gateway of a next hop) according to a mapping relation between a GUID and an IP address, and if the address is directly sent, the address is directly sent through a gateway of a local area network; otherwise, the data is sent to the subnet gateway of the next hop, and then the subnet gateway of the next hop carries out the same operation.

The first step is as follows: and (4) user registration, namely generating a unique identifier for a transmitting-receiving entity in the DDS, and recording the unique identifier as a GUID.

A GUID format of 16 bytes length is defined as shown in fig. 5. The user inputs an AppName value "AppName 01" through the function interface, and the user registration module internally applies information (GUIDInfo) for assembling GUID to the gateway using RPC: including the number of the gateway, a hash field of four bytes and a duplicate avoidance field of two bytes. The gateway assigns a GUIDInfo value of: and numbering the gateways: "1"; a hash field: "0 x29ac 7392"; a weight avoidance field: "1". According to the GUID rule, the first 12 bits of the generated GUID are: "0 xffff0001000129ac 73920010". This GUID is used to create a domain participant. The user registration module fills in the last 4 bytes of content, constructs the complete GUID value "0 xfffff 0001000129ac73920010ff 726307", and creates a data writer using this GUID.

The second step is that: and exchanging data such as GUID, AppName, IP address and the like among the gateways.

As shown in fig. 2, the subnet gateway 1 and the subnet gateway 2 can mutually transmit information after sensing each other. After the subnet gateway 1 receives the self information Data (p1) sent by the application (DP 1) 192.168.1.2, it modifies the ip in it into the self outward ip value 192.168.2.1 and modifies the DP1 information after modification

To the subnet gateway 2. The subnet gateway 2 modifies the ip therein into the ip value 192.168.3.2 in the self-pair and modifies the DP1 information

To the application (DP 2). At this time, for the application (DP 2), an application node having an application name of "appname 01", a GUID value of "0 xfffff 0001000129ac73920010ff 726307", but an ip address of "192.168.3.2" is seen.

The third step: a mapping of GUIDs to IP addresses.

As shown in fig. 2, while forwarding information, each gateway maintains a mapping of GUIDs to IPs recorded in a routing table, and can find the IP of the next gateway to reach the target GUID by looking up the table. After receiving the information of the user, the subnet gateway 1 records the information into the routing table, and after receiving the information of the gateway 1, the gateway 2 also records the information correspondingly.

The matching relationship table of the entity internal record on the application DP1 formally behaves as:

application name	GUID	IP
			appname02	0xffff000100022aac73920010ff726307	192.168.1.1

The routing table record maintained on subnet gateway 1 formally behaves as:

application name	GUID	IP
			appname01	0xffff0001000129ac73920010ff726307	192.168.1.2
appname02	0xffff000100022aac73920010ff726307	192.168.2.2

The routing table record maintained on subnet gateway 2 formally behaves as:

application name	GUID	IP
			appname01	0xffff0001000129ac73920010ff726307	192.168.2.1
appname02	0xffff000100022aac73920010ff726307	192.168.3.3

The matching relationship table of the entity internal record on the application DP2 formally behaves as:

application name	GUID	IP
			appname01	0xffff0001000129ac73920010ff726307	192.168.3.2

The fourth step: based on the three steps of work, addressing of the transmitting and receiving entity is carried out to complete data transmission; the method comprises the following specific steps:

when a user calls an interface of application DP1 to send data, the AppName of the appointed opposite end is input as 'appName 02', and the data transmission model searches an internal matching relation table and sends the data for the GUID of the appointed opposite end. And the data writer searches the IP address 192.168.1.1 corresponding to the GUID, and the data is sent to the subnet gateway 1.

After receiving the data, the subnet gateway 1 searches the routing table according to the opposite end GUID to obtain the next hop IP address 192.168.2.2, and the data is sent to the subnet gateway 2.

After receiving the data, the subnet gateway 2 searches the routing table according to the opposite end GUID to obtain the next hop IP address 192.168.3.3, and the data is sent to the application DP 2.

Through the above steps, the data arrives from the application DP1 to the application DP2, completing the addressing process.

The fifth step: as shown in fig. 6, the DP2 is used to roam to subnet 3, and reallocate ip address 192.168.4.4, so that data can be transmitted continuously; the method comprises the following specific steps:

and repeating the first step to the fourth step after the DP2 is applied to be online again, and changing the mapping relation on each node.

application name	GUID	IP
			appname02	0xffff000100032aac73920010ff726307	192.168.1.1

The routing table record maintained on subnet gateway 1 formally behaves as:

application name	GUID	IP
			appname01	0xffff0001000129ac73920010ff726307	192.168.1.2
appname02	0xffff000100032aac73920010ff726307	192.168.2.3

The routing table record maintained on subnet gateway 2 formally behaves as:

application name	GUID	IP
			appname01	0xffff0001000129ac73920010ff726307	192.168.2.1

The routing table record maintained on the subnet gateway 3 formally behaves as:

application name	GUID	IP
			appname01	0xffff0001000129ac73920010ff726307	192.168.2.1
appname02	0xffff000100032aac73920010ff726307	192.168.4.4

application name	GUID	IP
			appname01	0xffff0001000129ac73920010ff726307	192.168.4.3

When a user calls an interface of the application DP1 to send data, the AppName of the appointed opposite end is still input to be 'appName 02', and the data transmission model searches an internal matching relation table and translates the table into a GUID of the appointed opposite end to send. And the data writer searches the IP address 192.168.1.1 corresponding to the GUID, and the data is sent to the subnet gateway 1.

After receiving the data, the subnet gateway 1 searches a routing table according to the opposite-end GUID to obtain the next-hop IP address 192.168.2.3, and the data is sent to the subnet gateway 3.

After receiving the data, the subnet gateway 3 searches the routing table according to the opposite end GUID to obtain the next hop IP address 192.168.4.4, and the data is sent to the application DP 2.

Through the above steps, the data arrives from the application DP1 to the application DP2, completing the roaming addressing process.

Although the preferred embodiments of the present invention have been described in detail, the present invention is not limited to the details of the embodiments, and various equivalent modifications can be made within the technical spirit of the present invention, and the scope of the present invention is also within the scope of the present invention.

Claims

1. A DDS-based cross-wide area network dual-roaming data transmission method is characterized by comprising the following steps:

step 1, marking the application name as AppName, and generating a unique identifier GUID for identifying a transmitting-receiving entity so as to complete the creation of the transmitting-receiving entity;

step 2, exchanging GUID, AppName and IP address data among gateways;

step 3, mapping GUID and IP address;

and 4, addressing the transceiving entity based on the steps 1 to 3 to complete data transmission.

2. The DDS-based cross-WAN dual-roaming data transmission method of claim 1, wherein in step 1, when the user registers, the name AppName of the application is provided first, then the AppName generates the GUID through a Hash function, and finally the GUID is returned to the user.

3. The DDS based dual-roaming data transmission method across wide area network as recited in claim 2, wherein the step 2 further comprises:

step 2-1, DDS entities in different interconnected local area networks are created, and after the entities are created, a gateway where the entities are located records GUID, AppName and IP address information of the entities;

step 2-2, after the preset entity is online, the GUID, the AppName and the IP address data of the entity are sent to a subnet gateway where the entity is located;

step 2-3, the gateway records the data after receiving the data, modifies the IP address into the gateway address of the gateway, and then forwards the GUID, the AppName and the new IP address to the interconnected gateway;

and 2-4, the interconnected gateways record the received data on one hand, and continuously modify and forward the IP addresses in the received data to other interconnected gateways on the other hand.

4. The DDS-based cross-wide area network dual-roaming data transmission method as recited in claim 1, wherein after the operation of step 2, the mapping relationship between the GUID and the IP address of the entity in the network is obtained, when the data writer sends data to the data reader, the GUID of the entity is first introduced, then the GUID of the introduced entity is matched by the bottom layer of the ZR-GAIPM according to the GUID and the mapping content of the IP address which are already stored in the second step, and the IP address of the GUID of the introduced entity is located, so as to complete the mapping between the GUID and the IP address.

5. The DDS based dual-roaming data transmission method across wide area network as recited in claim 1, wherein the step 4 further comprises:

when a data sender sends data, firstly, a subnet gateway where the sender is located locates an address of a receiver according to a mapping relation between a GUID and an IP address, and if the data sender is directly sent, the data sender is directly sent through a gateway of the local area network; otherwise, the data is sent to the subnet gateway of the next hop, and then the subnet gateway of the next hop carries out the same operation.

6. A computer-readable storage medium storing at least one instruction which, when executed by a processor, implements a method for dual roaming data transmission across wide area networks as recited in any one of claims 1-5.

7. A data transmission system, comprising:

a memory;

a processor; and

a plurality of modules stored in the memory and executed by the processor, the plurality of modules comprising:

the user registration module is used for establishing a preset application program as a receiving and sending entity;

the inter-network data exchange module exchanges GUID, AppName and IP address data among the gateways;

the GUID and IP mapping module is used for mapping the IP address to which the GUID belongs according to the value of the GUID;

and the data transmission module completes data forwarding according to the mapped IP address.