CN105681203B - A kind of countermeasure that the connection of space delay tolerant network is surprisingly failed - Google Patents
A kind of countermeasure that the connection of space delay tolerant network is surprisingly failed Download PDFInfo
- Publication number
- CN105681203B CN105681203B CN201610021507.4A CN201610021507A CN105681203B CN 105681203 B CN105681203 B CN 105681203B CN 201610021507 A CN201610021507 A CN 201610021507A CN 105681203 B CN105681203 B CN 105681203B
- Authority
- CN
- China
- Prior art keywords
- connection
- failure
- node
- record
- time
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/02—Topology update or discovery
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/20—Hop count for routing purposes, e.g. TTL
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/28—Routing or path finding of packets in data switching networks using route fault recovery
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The present invention discloses a kind of countermeasure that the connection of space delay tolerant network is surprisingly failed, this method and the LTP protocol in conjunction that transmitting is provided, including establishing and using Joint failure discovery mechanism, connection restores detection mechanism, Joint failure and recovery notifying mechanism, connection figure update mechanism and the router-level topology mechanism for considering Joint failure, using the continuous re-transmission of beam as the mark of Joint failure, fail message is informed into other nodes when finding Joint failure, other nodes update link information according to notice, failure connection is excluded from path in time when calculating routing, with this come cope with spatial electromagnetic interference or the excessively low reason of node energy caused by loss of connectivity issue.
Description
Technical field
The present invention relates to technical field of the computer network.It connects and anticipates more particularly, to a kind of space delay tolerant network
The countermeasure of outer failure.
Background technology
With the continuous development of internet and space exploration technology, spatial network is designed to research hotspot.Due to space
Environment the features such as there are longer end-to-end time delay, the higher bit error rate, frequent link downs, traditional TCP/IP networks without
Method directly uses in spatial network, and the delay-tolerant network (Delay Tolerant Network, DTN) that NASA is proposed can be with
It solves these problems well, becomes a solution of spatial network.DTN agreements newly define beam (bundle) layer and remittance
Application layer data is divided into small beam (bundle) to send by poly layer, and frequent link is coped with using the strategy of storage forwarding
It interrupts, beam, which is stored in intermediate node, when no end-to-end link waits for transmission opportunity.Shu Xieyi uses EID (endpoint
ID) indicate that the both sides of communication, EID are made of node number and service number, node number, that is, DTN node serial numbers, for calculating routing, clothes
The different communication side registered on node is distinguished in business number, and node number and service number be similar to the addresses ip and end in ICP/IP protocol
Slogan.
The interaction that layer protocol completes beam layer and transport layer is converged, existing convergence-level agreement includes TCPCL (TCP
Convergence Layer protocol)、UDPCL(UDP Convergence Layers protocol)、LTPCL(LTP
Convergence Layer protocol) etc., LTP (Licklider Transmission Protocol) agreement be in order to
Cope with spatial network long delay, the high channel bit error rate, asymmetric link problem and the transport protocol designed.LTP agreements are by setting
The retransmission mechanism of meter provides reliable data transport service, LTPCLA first (LTP Convergence Layer Adapter)
All beams that next-hop node is the same neighbor node are aggregated into a data block (block), after Shu Juhe is blocking,
Block is divided into small section (segment) again, as the minimum data unit of LTP agreements, block size and section size are all can be with
It is arranged, data bundle polymerization quantity is determined according to preconfigured LTP block sizes.The type of section has RED sector (red
Part), green portion (green part), checkpoint (checkpoint), report section (report segment) and report are true
Recognize section (report ACK).RED sector is the data for needing transmitting, and green portion is not need the data of transmitting.
For each checkpoint, receiving terminal is required for replying report section accordingly and informs the section that sender has been received, sender
The section lost is retransmitted according to the report section received.Checkpoint and report section have retransmission timer, when sender cannot connect in time
Checkpoint will be retransmitted when the report section for receiving response, the beam polymerizeing in data block after checkpoint continuously retransmits ten times will be removed
Routing is recalculated, Shu Fasheng is retransmitted at this time.
Since space nodes have the characteristics that track anticipated that, communication opportunity between two nodes can be previously obtained i.e.
Link information, including communicate every time initial time, terminate time, transmission rate etc., connection figure route (Contact Graph
Routing, CGR) primary connection (contact) will be known as by communication opportunity each time, represent link information, CGR with link information
Link information is pre-configured in the way of connection in connection plan (contact plan), preconfigured link information
For the start node (from node) of connection, terminal node (to node), initial time (from time), terminate time (to
Time), transmission rate (rate), start node between terminal node at a distance from (range).Connect link information format in the works
As shown in table 1：
1 link information format of table
CGR is sent to beam from source node to hop-by-hop according to preconfigured link information by available connection with together
Destination node.
CGR is also brought high to connection figure accuracy requirement while calculating routing using precognition link information
Problem.And space environment complicated and changeable easily causes to connect the generation surprisingly failed, and presses initial connection information configuration at this time
Connection figure and actual connection state are no longer consistent, will be unable to use according to the routing calculated is configured originally, cause to route
Failure.
Accordingly, it is desirable to provide a kind of space delay tolerant network connects the countermeasure surprisingly to fail.
Invention content
The purpose of the present invention is to provide a kind of space delay tolerant networks to connect the countermeasure surprisingly to fail, and reply is empty
Between connection accident Problem of Failure in delay-tolerant network, the failure detected is connected in time after finding Joint failure and is noticed
Other nodes are given, are avoided in routing using failure connection.
In order to achieve the above objectives, the present invention uses following technical proposals：
A kind of countermeasure that the connection of space delay tolerant network is surprisingly failed, this method and LTP protocol in conjunction, by
It can ensure reliable data transmission, the probability pole that Shu Fasheng is continuously retransmitted under the normal bit error rate in the retransmission mechanism of LTP agreements
It is low, therefore the continuous re-transmission of same chain road beam is regarded as the mark of Joint failure by the present invention.
The countermeasure that a kind of connection of space delay tolerant network is surprisingly failed includes the following steps：
S1, judge whether connection occurs unexpected failure according to the transmission situation of beam in link；
S2, when finding Joint failure, other nodes are noticed into the connection of failure, and restore detection beam using connection and detect
Whether the connection of failure restores, other nodes are noticed in the connection of recovery after judging that the connection restores；
S3, when node receive Joint failure advertised information or connection restore advertised information after, update the node and locally connect
Connect the failure state accordingly connected in the works；
S4, routing is calculated for beam, the beam that failure connection is foreclosed, and preferentially forwards remaining life span small.
Preferably, step S1 further comprises following sub-step：
S1.1, failure state flag bit is added in original link information in the works in the connection of node, and establishes Shu Chong
Biography records list and failure linkage record list, and Shu Chongchuan records source node, source service number, the generated time stamp of list records beam
And next-hop node, the start node of failure linkage record list records failure connection, terminate time, minimum inspection at terminal node
Survey time interval, connection restores probe timer, failure notification sends flag bit and connection recovering mark position；
S1.2, according to the transmission situation of beam in link, utilize failure state flag bit, Shu Chongchuan record lists and failure to connect
It connects record list and judges whether connection occurs unexpected failure.
Preferably, step S1.2 further comprises following sub-step：
S1.2.1, when beam arrives, first determine whether the destination node of beam is local node, if it is thening follow the steps
S1.2.2, it is no to then follow the steps S1.2.3；
S1.2.2, judge whether beam is Joint failure state advertisement beam according to the flag bit and purpose service number of beam, if
It is that then in connection, the failure state connected is noticed in update in the works；
S1.2.3, judge whether beam retransmits, it is no to then follow the steps S1.2.4 if not thening follow the steps S4；
S1.2.4, it is checked whether according to the flag bit and purpose service number of beam and restores detection beam for connection, if it is connected
It connects recovery detection beam to be retransmitted, which is abandoned, it is no to then follow the steps S1.2.5；
S1.2.5, the record for whether having the beam in Shu Chongchuan record lists checked, believed if the re-transmission for recording beam without if
Breath, the retransmission information include the source node of beam, source service number, generated time stamp and next-hop node, then execute step S4；
If there is thening follow the steps S1.2.6；
Whether S1.2.6, the next-hop node for judging beam and the next-hop node retransmitted in recording are consistent, if inconsistent
Next-hop node in record, is changed to the next-hop node of Shu Dangqian, and execute step S4 by the re-transmission record for then updating beam；It is no
Then follow the steps S1.2.7；
S1.2.7, judge that the connection of the next-hop node of beam disabled status occurs for local node, in locality connection plan
The middle linkage flag by local node to beam next-hop node is failure；Check failure linkage record list in whether it is existing should
The record of connection, if it does not exist, then the information of failure connection is recorded in Joint failure records list, the failure connection
Information include start node, terminal node, terminate the time, probe timer is restored at minimum detection time interval and connection, and
Execute step S4；It is not re-recorded if the failure logging (record) of the existing connection, executes step S4.
Preferably, the loading section of the Joint failure state advertisement beam records the start node of connection, terminal node, rises
Begin time, termination time and failure mark.
Preferably, step S2 further comprises following sub-step：
S2.1, node open failure linkage record list execute step S2.2；
S2.2, it checks with the presence or absence of failure linkage record in list, and if so, first failure linkage record is found,
Execute step S2.3；It is no to then follow the steps S2.10；
S2.3, it checks whether the failure recovery flag bit of the failure linkage record is 1, if it is illustrates the connection of failure
It is recovered, execute step S2.4；Otherwise illustrate that the connection of failure restores not yet, execute step S2.5；
S2.4, the failure state flag bit accordingly connected is labeled as 0 in the works in locality connection, according in linkage record
The termination time calculate failure notification domain, it is 0 that will notice the failure flag tag in beam format, generates Joint failure state advertisement
Beam is sent to the node in failure notification domain, informs that the connection of other nodes is recovered, deletes in failure logging (record) list about this
The record of connection executes step S2.9, checks the next failure connection recorded in list；
S2.5, check that failure notification sends whether flag bit is 1, if it is illustrates to be transmitted across about the connection
Failure notification executes step S2.7；Otherwise explanation sends failure notification not yet, executes step S2.6；
S2.6, the failure notification domain that the connection is calculated according to the termination time in linkage record, will be in notice beam format
The flag tag that fails is 1, generates Joint failure state advertisement beam and is sent to the node in failure notification domain, informs that other nodes connect
Connect no longer valid, and it is 1 that the failure notification in failure logging (record), which is sent flag tag, executes step S2.7；
S2.7, check that Joint failure restores whether probe timer expires, and thens follow the steps S2.8 if expired, otherwise holds
Row step S2.9；
S2.8, connection recovery detection beam is sent, the destination node of beam is set as the terminal node of the connection, service number setting
It is 16, and resets connection and restore probe timer, executes step S2.9；
S2.9, check that next failure linkage record whether there is, and if so, executing step S2.3 to it；If no
In the presence of then explanation has had stepped through linkage record, executes step S2.10；
S2.10, suspend mode one second, return to step S2.2 executes new round detection.
Preferably, step S2 further includes following sub-step：
S2.11, it checks whether beam is that connection restores detection beam after beam is sent successfully, if it is illustrates that connection is extensive
It is multiple, execute step S2.12；It is no to then follow the steps S2.13；
S2.12, start node is found from failure linkage record list is the next-hops that local node, terminal node are beam
The failure recovery flag bit of the connection is labeled as 1, the mark restored as connection in step S2.3 by the connection of node；
S2.13, the information that the beam whether is recorded in Shu Chongchuan record lists checked, if there is then deleting the record.
Preferably, the failure notification domain meets institute of the time started less than the failure connection termination time for connection in the works
There are the start node and terminal node of connection.
Preferably, the detailed process of step S4 is：
It calculates and route for beam, if beam, which is connection, restores detection beam, be sent to detected neighbor node；If it is not,
When the residue for then excluding except path the connection of failure when calculating routing, and comparing the beam and the beam in queue is survived
Between, it is sent by the remaining ascending sequence of life span.
Beneficial effects of the present invention are as follows：
The failure detected connection is advertised to other sections by technical solution of the present invention in time after finding Joint failure
Point is avoided in routing using failure connection.Technical solution of the present invention is the new addition failure mark of connection in the works in connection
Will position, for indicating Joint failure state, such as：1 represents failure, and 0 represents recovery, the mistake for connecting every section when calculating is route
Effect state is taken into account.Technical solution of the present invention newly establishes Shu Chongchuan record lists and failure linkage record list, Shu Chong
Biography record list is used for recording the beam information retransmitted, as the foundation for judging that connection is failed；Fail linkage record row
Table is used for recording the connection temporarily failed.Technical solution of the present invention uses the bundle flag positions reserved Shu Xieyi and service number 15
It is new to define connection recovery detection beam, for detecting whether the connection recorded in failure linkage record list restores.Institute of the present invention
It states technical solution and newly defines Joint failure state advertisement beam using the bundle flag positions reserved Shu Xieyi and service number 16 to notice
Joint failure and recovery information.
Description of the drawings
Specific embodiments of the present invention will be described in further detail below in conjunction with the accompanying drawings.
Fig. 1 shows the flow chart for the countermeasure that the connection of space delay tolerant network is surprisingly failed.
Fig. 2 shows the flow charts that Joint failure judges.
Fig. 3 shows that connection restores the flow chart of detection and failure state notice.
Fig. 4 shows that connection restores the flow chart judged.
Fig. 5 shows the application scenarios schematic diagram for the countermeasure that the connection of space delay tolerant network is surprisingly failed.
Specific implementation mode
In order to illustrate more clearly of the present invention, the present invention is done further with reference to preferred embodiments and drawings
It is bright.Similar component is indicated with identical reference numeral in attached drawing.It will be appreciated by those skilled in the art that institute is specific below
The content of description is illustrative and be not restrictive, and should not be limited the scope of the invention with this.
The countermeasure that space delay tolerant network provided in this embodiment connection is surprisingly failed is in software I ON-3.3.1 editions
It is realized on this, this method is established and uses following five mechanism：Joint failure discovery mechanism, connection restore detection mechanism, connection
Failure and recovery notifying mechanism, the connection figure update mechanism and router-level topology mechanism for considering Joint failure.
As shown in Figure 1, the countermeasure that space delay tolerant network connection provided in this embodiment is surprisingly failed includes such as
Lower step：
S1, judge whether connection occurs unexpected mistake according to the transmission situation of beam in link using Joint failure discovery mechanism
Effect；
S2, when finding Joint failure, using Joint failure and restore notifying mechanism other sections are noticed into the connection of failure
Point；In view of Joint failure both may be temporarily failure caused by electromagnetic interference be also likely to be caused by space nodes failure it is permanent
Failure restores to visit after other nodes are noticed in the connection of failure using Joint failure and recovery notifying mechanism based on connection
Whether survey mechanism, the connection for being detected failure in time using connection recovery detection beam are restored, use and connect after judging that the connection restores
It connects failure and restores notifying mechanism and other nodes are noticed into the connection of recovery；
S3, connection status advertised information (Joint failure advertised information or connection restore advertised information) is received when node
Afterwards, the failure state that the node locality connection accordingly connects in the works is updated using connection figure update mechanism；
S4, routing is calculated for beam using the connection figure routing CGR for the router-level topology mechanism for considering Joint failure, failure is connected
The beam for connecing and foreclosing, and preferentially forward remaining life span small.
The countermeasure that space delay tolerant network connection provided in this embodiment is surprisingly failed can in time avoid not
Necessary re-transmission reduces delivery lag.
Wherein
Step S1 " judges whether connection occurs accident using Joint failure discovery mechanism according to the transmission situation of beam in link
Failure " detailed process be：
Joint failure discovery mechanism has modified connection original link information format in the works, and failure state is added for connection
Flag bit, and newly establish Shu Chongchuan record lists and failure linkage record list, be respectively intended to the beam that retransmits of record with
The connection of failure.
The link information format newly defined is as shown in table 2：
The link information format that table 2 newly defines
Joint failure state flag bit represents Joint failure for 1, and representing connection for 0 restores.
Shu Chongchuan record lists are used for recording the beam retransmitted, the content of record include the source node of beam, source service number,
Generated time stabs and next-hop node.Format is as shown in table 3：
3 beam of table retransmits record listings format
The source node of beam, source service number and generated time stamp are the unique mark of beam, for identifying different beams, under beam
The neighbours that retransmit of one hop node mark connect, and can uniquely be determined by these information and be happened at local node to next
The beam retransmitted in the connection of hop neighbor node.
CGR indicates link information using connection, after nodal test to beam is to retransmit beam, continues to detect Shu Chongchuan records
In list whether the record of the existing beam, if there is no then according to table 3 record beam retransmission information, when the beam transmission success
When the retransmission information of beam is deleted from beam retransmission list again；If it is present next-hop node and beam in inspection record
Whether next-hop node is consistent, and the re-transmission record of beam is updated if inconsistent, the next-hop node in record is changed to beam and is worked as
Preceding next-hop node shows that beam is retransmitted twice in succession in same connection if consistent, local node is arrived
The connection of the next-hop node of beam is considered as temporary failure, is in the works then local node, end by start node in locality connection
It is failure that only node, which is the linkage flag of beam next-hop node, is that beam recalculates routing, and checks using new connection plan
Whether there is or not the records of failure connection in failure linkage record list, and failure connection is recorded if not.Fail linkage record
Listings format is as shown in table 4：
The failure linkage record listings format of table 4
The start node of the linkage record list records that fail failure connection, terminates time, minimum detection time at terminal node
It is spaced BDCT (basic disrupted contact check time), connection restores probe timer, failure notification is sent
Flag bit and connection recovering mark position.Minimum detection time interval connects the benchmark for restoring probe timer as setting, will determine
When device be set as the integral multiple of minimum detection interval BDCT, after timer expires, send and connect to the terminal node of failure connection
Recovery detection beam is connect to check whether connection restores, the format that timing implement body set-up mode and connection restore detection beam is connecting
Restore described in detection mechanism.BDCT is calculated after connection is judged as failure, and recovery probe timer will be connected for the first time and set
It is set to BDCT.BDCT according to failure connection duration determine, using connection the duration 1 percent as BDCT, than
Example is adjustable：
Failure notification sends flag bit and is used for marking whether to be transmitted across this to other nodes in failure linkage record list
The failure state of connection is noticed, Initialize installation 0, and after being transmitted across failure notification, failure notification is sent flag bit label
It is 1.Whether connection recovering mark is used for marking connection recovered, and 1 is labeled as if restoring.In addition when the failure in list
After connection reaches its termination time, which is deleted in linkage record list of failing.
The detailed process of " whether the connection for being detected failure in time using connection recovery detection mechanism is restored " is in step S2：
After when BDCT seconds in the past, connection recovery probe timer is expired, and node, which will send to connect, restores detection beam to mistake
Whether the neighbor node of effect is recovered to check connection.After detecting beam transmission, resets connection and restore probe timer
For 2*BDCT.We mark connection to restore detection beam using the Shu Xieyi flag bits reserved and service number 15, will detect beam
Source node is set as local node, and destination node is set as the terminal node of failure connection, and source and destination service number is set as 15,
Transmission content is character 1.
Connection restores detection mechanism and connects the transmission interval for restoring detection beam using connection recovery probe timer to limit,
It avoids sending a large amount of connection recovery detection information to a large amount of consumption of the resources such as satellite energy generation, while using maximum probe
MT (maximum check time) is spaced to ensure to detect granularity, if the time that connection next time restores probe timer is big
In MT, then timer is provided directly as MT.If do not restored also when sending to connect to connect after recovery detects beam, recovery is connected
Detection beam will be retransmitted, and when sending node detects that connection restores detection Shu Chongchuan, connection is restored detection beam from storage
It removes.After 2*BDCT seconds, sends another connection and restore detection beam, and connection is restored into probe timer and is set as 3*
BDCT.This process is repeated until connection restores or the connection recovery probe timer time is more than MT.When connection restores detection
Timer is more than connection is restored probe timer after MT to be set as fixed value MT, MT to be configured as needed, for example set
It is set to 30 seconds or 60 seconds.
After connection restores detection beam transmission success, it is local that local sending node finds start node in certificate revocation list
Node, terminal node by detection neighbor node connection, by the connection recovering mark position of the connection in table 4 be labeled as 1.
" when finding Joint failure, using Joint failure and restore connection notice of the notifying mechanism by failure in step S2
Other nodes " and the detailed process of " other nodes are noticed in the connection of recovery using Joint failure and recovery notifying mechanism " are：
It is logical to other nodes using Joint failure state advertisement beam after connection restores when finding Joint failure or detecting
Joint failure state is accused, advertised information is placed on the loading section of beam, and Joint failure state advertisement beam format is as shown in table 5：
5 Joint failure state advertisement beam format of table
Start node, initial time, terminates the time for identifying that connection, failure mark are used for indicating to connect at terminal node
Failure state, be 1 when indicate connection fail, for 0 represent connect it is recovered, the link information of notice is placed on beam
Loading section.We reserve flag bit and service number 16 to mark Joint failure state advertisement beam using bundle agreements, will lead to
It is 16 that the source node of announcement beam, which is set as local node, destination node as node, the source and destination service number in advertised domain,.
The mechanism interior joint has failure to connect every the primary failure linkage record list of 1 second traversal, when finding to record in list
Joint failure state advertisement beam is sent to other nodes when connecing, notices Joint failure information, and in the linkage record list that will fail
The failure notification of the connection sends flag bit and is labeled as 1, indicates the failure notification for being transmitted across the connection, will no longer send out later
Give the failure notification.Equally, whether detection connection recovering mark position is 1, illustrates that connection is recovered if it is 1, in local
Corresponding Joint failure status indication is in the works to restore by connection, is noticed to other nodes using Joint failure state advertisement beam
Connection restores information, and deletes corresponding linkage record in Joint failure records list.Since certain nodes may use
Less than the connection of the failure, notifying mechanism uses failure notification domain CDAG (Contact Disruption Announce
Group) only the node into advertised domain is sent limitation Joint failure state advertisement beam, to ensure the serviceability of notice beam, is reduced
Unnecessary transmission.CDAG is defined as follows：
{ connection meets the start node for the time started being less than all connections of failure connection termination time to CDAG=in the works
And terminal node
Just have an opportunity to use the connection of the failure because only that the time started is less than the connection that failure connection terminates the time,
Therefore CDAG limitations notice is only sent to the start node and terminal node of these connections.Such as start node, the terminal node of connection 1
Point, initial time, terminate the time be respectively 1,2,100s, 300s, connect 2 be respectively 3,4,200s, 400s, 3 difference of connection
It is less than the termination time of connection 1 at the beginning of 2 due to connecting when connecting 1 failure for 5,6,400s, 500s, connects 3
Time started is more than the termination time of connection 1, then advertised domain is start node and terminal node i.e. 3 and 4 for connecting 2.Notice letter
The life span of breath is set as the time difference of information delivery time and failure connection end time.
The tool of " failure state accordingly connected in the works using connection figure update mechanism update locality connection " in step S3
Body process is：
After node receives beam, first determine whether beam is the Joint failure state advertisement beam for being sent to local node,
If it is the link information of notice, including start node, terminal node, initial time, termination time, failure mark are read out
Position.If the flag bit that fails is 1, represents corresponding connection and disabled status occurs, update locality connection plan, failed mark
Will position is labeled as 1；If the flag bit that fails is 0, the corresponding failure connection of representative is recovered, is lost in the works in locality connection
Valid flag position is labeled as 0.
Step S4 " is that beam calculates routing using the connection figure routing CGR for the router-level topology mechanism for considering Joint failure, will lose
Effect connection forecloses, and preferentially sends the small beam of remaining life span " detailed process be：
The failure state that every section of connection in path is considered when node calculates path, should if failure flag bit is 1
Connection is excluded from path, is continuing with if failure flag bit is 0, while considering to reach the remaining life span of beam, excellent
First send the small beam of remaining life span.
Step S1 further comprises following sub-step：
S1.1, failure state flag bit is added in original link information in the works in the connection of node, and establishes Shu Chong
Biography records list and failure linkage record list, and Shu Chongchuan record lists include the source node of beam, source service number, generated time stamp
And next-hop node, failure linkage record list include the start node of failure connection, terminal node, terminate time, minimum inspection
Survey time interval, connection restores probe timer, failure notification sends flag bit and connection recovering mark position；
S1.2, according to the transmission situation of beam in link, utilize failure state flag bit, Shu Chongchuan record lists and failure to connect
It connects record list and judges whether connection occurs unexpected failure.
As shown in Fig. 2, step S1.2 further comprises following sub-step：
S1.2.1, when beam arrives, first determine whether the destination node of beam is local node, if it is thening follow the steps
S1.2.2, it is no to then follow the steps S1.2.3；
S1.2.2, judge whether beam is Joint failure state advertisement beam according to the flag bit and purpose service number of beam, if
It is that then in connection, the failure state connected is noticed in update in the works；
S1.2.3, judge whether beam retransmits, it is no to then follow the steps S1.2.4 if not thening follow the steps S4；
S1.2.4, it is checked whether according to the flag bit and purpose service number of beam and restores detection beam for connection, if it is connected
It connects recovery detection beam to be retransmitted, illustrates that connection not yet restores, which is abandoned, it is no to then follow the steps S1.2.5；
S1.2.5, the record for whether having the beam in Shu Chongchuan record lists checked, believed if the re-transmission for recording beam without if
Breath, including the source node of beam, source service number, generated time stamp, next-hop node, then execute step S4 and forward the beam；If
Have, thens follow the steps S1.2.6；
Whether S1.2.6, the next-hop node for judging beam and the next-hop node retransmitted in recording are consistent, if inconsistent
Next-hop node in record, is changed to the next-hop node of Shu Dangqian, then executes step S4 by the re-transmission record for then updating beam,
It is no to then follow the steps S1.2.7；
S1.2.7, illustrate that the beam experienced continuous re-transmission on same paths at this time, judge that local node arrives
Disabled status occurs for the connection of the next-hop node of beam, in locality connection in the works by local node to the company of beam next-hop node
It connects labeled as failure；Check failure linkage record list in whether the record of the existing connection, if it does not exist, then connecting
The information of failure connection is recorded in failure logging (record) list, including when start node, terminal node, termination time, minimum detection
Between interval, connection restore probe timer, then execute step S4, if the failure logging (record) of the existing connection, no longer remembers
Record directly executes step S4；
The detailed process of step S4 is:
It calculates and route for beam, if beam, which is connection, restores detection beam, be sent to detected neighbor node；If it is not,
When the residue for then excluding except path the connection of failure when calculating routing, and comparing the beam and the beam in queue is survived
Between, it is sent by the remaining ascending sequence of life span.
As shown in figure 3, step S2 further comprises following sub-step：
S2.1, when node starts DTN programs, open failure linkage record list executes step S2.2；
S2.2, it checks with the presence or absence of failure linkage record in list, and if so, first failure linkage record is found,
Step S2.3 is executed, it is no to then follow the steps S2.10；
S2.3, it checks whether the failure recovery flag bit of the failure linkage record is 1, if it is illustrates the connection of failure
It is recovered, step S2.4 is executed, otherwise illustrates that the connection of failure restores not yet, executes step S2.5；
S2.4, first locality connection in the works by the failure state flag bit accordingly connected be labeled as 0, then according to even
The mode for connecing failure and restoring described in notifying mechanism calculates failure notification domain according to the termination time in linkage record, will notice
Failure flag tag in beam format is 0, generates Joint failure state advertisement beam and is sent to the node in failure notification domain, informs
The connection of other nodes is recovered, deletes the record in failure logging (record) list about the connection later, then executes step S2.9,
Check the next failure connection recorded in list；
S2.5, check that failure notification sends whether flag bit is 1, if it is 1, illustrates to be transmitted across about the connection
Failure notification, execute step S2.7, explanation sends failure notification not yet if being not 1, executes step S2.6；
S2.6, by Joint failure and in the way of restoring described in notifying mechanism, the failure mark in beam format will be noticed
Labeled as 1, the failure notification domain of the connection is calculated according to the termination time in linkage record, informs that the connection of other nodes has been lost
Effect, and it is 1 that the failure notification in failure logging (record), which is sent flag tag, executes step S2.7 later；
S2.7, check that Joint failure restores whether probe timer expires, and thens follow the steps S2.8 if expired, otherwise holds
Row step S2.9 detects next failure logging (record)；
S2.8, connection recovery detection beam is sent, the destination node of beam is set as the terminal node of the connection, service number setting
It is 16, and resets connection in the way of described in connection restores detection mechanism and restore probe timer, executes step later
Rapid S2.9 checks next failure linkage record；
S2.9, check that next failure linkage record whether there is, and if so, executing step S2.3 to it；If no
In the presence of then explanation has had stepped through linkage record, executes step S2.10；
S2.10, suspend mode one second are then back to step S2.2, execute new round detection.
As shown in figure 4, step S2 further includes following sub-step：
S2.11, it checks whether beam is that connection restores detection beam after beam is sent successfully, if it is illustrates that connection is extensive
It is multiple, execute step S2.12；If not execution step S2.13；
S2.12, start node is found from failure linkage record list is the next-hops that local node, terminal node are beam
The step of failure recovery flag bit of the connection is labeled as 1 by the connection of node, and connection shown in Fig. 3 restores detection flow
The mark restored as connection in S2.3；
S2.13, the information that the beam whether is recorded in Shu Chongchuan record lists checked, if there is then deleting the record；Such as
Fruit does not illustrate that beam does not occur to retransmit phenomenon then, executes CGR default actions, does not do additional treatments.
The countermeasure that space delay tolerant network provided in this embodiment connection is surprisingly failed is applied to such as Fig. 5 below
Shown in scene, the present invention is described further：
Scene shown in fig. 5 is the scene of analog satellite node earthward data center's transmission data, in scene, space section
Point operation DTN agreements, ground node run ICP/IP protocol, and gateway is responsible for realizing conversion of the DTN agreements to IP agreement, data hair
It is satellite 1 to send node, and destination node is data center, and data can be sent to gateway 5, be carried out through gateway in a form of a beam first
DTN agreements using IP network to being sent to data center after the conversion of IP agreement.Assuming that satellite node 2 arrives the company of satellite node 3
It is 1 second to 1000 seconds to connect the duration, and at 30 seconds since the antenna of node 3 breaks down, the connection of node 2 to 3 generates connection
The situation surprisingly to fail, failure duration are 600s.Assuming that being 1s at the beginning of being connected between node 1 and node 2, terminate
Time is 1000s, and at the beginning of being connected between node 3 and 5 and the termination time is respectively 1s and 1000s, between node 1 and 4
Connection is respectively 100s and 1100s, and that connected between node 4 and 6 is respectively 100s and 1100s, is connected between node 6 and 5
Be respectively 100s and 1100s, connected between node 4 and 7 be respectively 1200s and 2200s, maximum probe interval MT be 35s.
Following steps are a complete failure countermeasure flow.
Following operation is executed in source node satellite 1：
Step 1：Source node satellite 1 is to data center's transmission data, and totally two paths are available, and one is 1>2>3>5 reach
Then gateway is transferred to data center by ground IP network, another is 1>4>6>5 reach gateway 5, then pass through ground IP
Network transmission is to data center.Node 1 calculates beam according to original configuration and is using path 1 in spatial network first>2>3>5
The time of gateway 5 is reached than path 1>4>6>The time that 5 paths reach gateway 5 is early, therefore selects 1>2>3>5 be optimal path
Beam, i.e. dotted arrow meaning path are transmitted, the path can be used normally before 30 seconds.
Step 2：After 30 seconds, the connection of node 2 to 3 is failed, and node 1 is not aware that disabled status at this time,
Path 1 will be continuing with>2>3>5 send beam, because the connection of failure does not interfere with the connection that node 1 arrives node 2,
Beam can normally reach node 2, but beam will occur to retransmit phenomenon in the connection of node 2 to 3, and node 2 can use connection
Failure countermeasure finds the connection of failure and sends Joint failure state advertisement beam, and specific implementation step is specifically retouched in node 2
It states.
Step 3：After node 1 receives the beam of the transmission of node 2, determine whether that being sent to local Joint failure state leads to
Beam is accused, after being the discovery that Joint failure state advertisement beam, the linkage flag of node 2 to node 3 is to lose by update connection plan
Effect excludes the connection between node 2 and node 3 when calculating routing from path, and selection uses sub-optimal path 1>4>6>5,
Path 1 will be used always before 600s seconds>4>6>5 send beam, that is, realize arrow meaning path；
Step 4：After 600 seconds, node 2 finds that node 2 has arrived the connection of node 3 using Joint failure countermeasure
Restore, it is recovered to the connection between node 3 that failure state notice beam advertizing node 2 will be sent again at this time.When node 1 is known
The Joint failure state advertisement beam not sent finds that node 2 is recovered to the connection of node 3, at this time in locality connection meter
By the linkage flag of node 2 to node 3 to restore in drawing, follow-up beam will be continuing with path 1>2>3>5 send.
Following steps operation is executed in satellite node 2：
Step 1：When DTN programs start, start connection and restore detection mechanism, every the primary failure connection note of detection in one second
Record list.Simultaneously for the beam of arrival, node 2 can use flow shown in Fig. 2 Joint failures detection flow chart to check whether first
Beam is noticed to be sent to local failure state, because there was only the path failure that node 2 arrives node 3 in embodiment, therefore node 2 is not
It is that the failure state of oneself is noticed that destination node, which can be received,.Posterior nodal point 2 by detect beam whether be retransmit beam, due to
There is no Joint failure situation, all beams that can normally send before 30s, the beam not retransmitted, therefore node 2 is directly
Beam calculates routing, and beam will be according to path 2>3>5 Successful transmissions.
Step 2：After beam transmission success, restores flow shown in decision flow chart according to Fig. 4 connections and execute corresponding operating, it is first
First node 2 can check whether the beam of transmission success is that connection restores detection beam, because there is no disabled status before 30 seconds, because
This does not have detection beam, and halved tie executes CGR default treatments, do not do additional treatments.
Step 3：After the 30th second, surprisingly failing occur in the connection of satellite node 2 to 3, and data are in node 2 at this time
It will be unable to transmit on to 3 connection, according to LTP agreement retransmission mechanism, when the checkpoint that node 2 is sent out does not receive node 3 in time
When the report section of response, the re-transmission of checkpoint will occur, response is not received when the checkpoint that node 2 is sent out continuously retransmits ten times
When, node 2 takes out the beam polymerizeing in data block, recalculates routing, and beam will occur to retransmit phenomenon at this time.
Step 4：By Fig. 2 flows, after node 2 detects that beam is to retransmit beam, check in Shu Chongchuan record lists whether there is or not
About the record of the beam, due to being to retransmit for the first time at this time, there is no recording, then according to described in Joint failure discovery mechanism
Shu Chongchuan record formats record source node, source service number, generated time stamp, the next-hop node of beam, are recalculated later for beam
Routing, due to not yet finding that unexpected Problem of Failure occurs for 2 to 3 connection at this time, the optimal path that node 2 is calculated is still
It is 2>3>5.
Step 5：Due to connecting also in failure state, node 3 can not still respond report section at this time, and node 2 is sent out
Checkpoint continue to retransmit, when the checkpoint the number of transmissions in LTP agreements is again above ten times, beam will retransmit again.
Step 6：When node 2 detects that beam is to retransmit beam, search in Shu Chongchuan record lists about the record for retransmitting beam.
It was found that there is the record about the beam in Shu Chongchuan record lists, and the next-hop node of the next-hop node and beam in record is equal
For node 3, then disabled status has occurred in the connection of decision node 2 to node 3, by the record of the beam in Shu Chongchuan records list
It deletes, updates link information in the works in locally contact, and be failure by the linkage flag of node 2 to 3；Failure is then looked to connect
Connect in record list that whether there is or not the failure logging (record)s of the connection, because being to check failure for the first time, failure linkage record list
In and no record, failure connect list in record failure connection start node be 2, terminal node 3, terminate the time be
1000s, BDCT 10s, first time setting connection recovery probe timer is BDCT (10s), failure passes through flag bit and is 0, loses
Imitate recovering mark position 0；And routing is recalculated using new connection plan for the beam retransmitted, connection letter in the works is connected at this time
Breath has failure logging (record), therefore can beam be returned to node 1 when calculating routing.
Step 7：Node 2, every the primary failure linkage record list of one second traversal, will check failure at this time by Fig. 3 flows
The record that there is failure connection in linkage record list, checks failure link information, and it is 0 to check connection recovering mark position, is sentenced
Disconnected connection at this time restores not yet；It is 0 to continue checking for failure notification flag bit, indicates not yet to send about this to other nodes
The failure state of connection notices beam, and failure state advertised domain will be calculated with posterior nodal point 2, and then sending connection according to 3 format of table loses
State advertisement beam is imitated, and the failure notification in record is sent into flag bit and is labeled as 1.It is regular according to advertised domain, node 4 to 7
It is 1200 seconds to connect the time started, and the node 2 for being less than failure terminates time 1000s to the connection between node 3, therefore according to 4 and 7
Between connection the time started calculate advertised domain do not include node 4 and 7, but between node 4 to 6 connect the time started be
100s is less than the termination time of failure connection, therefore the advertised domain calculated according to the connection will include node 4, similarly can be obtained
Final advertised domain is { 1,3,4,5,6 }, is free of node 7.
Step 8：Node 2 continues checking for connection and restores probe timer either with or without expiring, and finds at this time there are no expiring, it
Detection finds no next failure linkage record, suspend mode at this time 1 second afterwards；
Step 9：After 1 second, node 2 continues to traverse primary failure linkage record list, detects satellite 2 to 3 at this time
Joint failure records, it is found that recovering mark position is 0, expression not yet restores, and announcement flag position is 1, shows to be transmitted across notice.
Probe timer setting is detected again, it is found that timer not yet expires, suspend mode 1 second；
Step 10：Node 2 checks again for after 1 second, it is found that timer expires not yet, continue suspend mode 1 second；Repeat this
Process knows that timer expires；When checking probe timer and expiring, sends connection and restore detection beam to neighbor node 3, and
Restore the transmission timer that the probe timer set-up mode setting described in detection mechanism restores detection beam next time according to connection
For 20s.
Step 11：Restore not yet in the connection of front nodal point 2 to the node 3 of 600s, the detection beam sent at this time equally will
It retransmits, after node 2 finds that the beam retransmitted is detection beam, directly deletes the beam.
Step 12：Timer expires again after 20s, retransmits connection detection beam, and timing is arranged according to format
Device is 30s；Same connection does not restore also, then the connection for checking re-transmission restores to delete beam after detecting beam.
Step 13：After the 30s past, connection at this time restores spy timer and expires, and sends to connect again and restores detection beam,
Because 4*BDCT is 40s at this time, it is more than MT (35s), therefore sets timer to 35s；After 35s, timer is expired again,
Detection beam is sent, and sets timer to MT, repeats this process until connection restores.
Step 14：When the connection between the posterior nodal point 2 of 600s and 3 is recovered, success will be sent by detecting beam at this time.This
When connection restore judgment mechanism detect transmission success beam be connection restore detection beam, judge local node 2 to detection beam mesh
Node 3 connection it is recovered, connection recovering mark position is labeled as 1 in failure connects list.
Step 14：The connection recovering mark position 1 that node 2 to 3 is found when node 2 traverses certificate revocation list, has shown connection
It is recovered, locality connection plan is updated at this time, is to restore corresponding linkage flag, and calculate failure state advertised domain, to notice
Node in domain sends connection and restores information, then deletes the linkage record of the recovery in failure logging (record) list.
Step 15：Since the connection of other node advised nodes 2 to 3 of warp-wise has been paid a return visit, node 1 will again be sent to beam
Node 2,；Find that locality connection plan interior joint 2 is recovered to the connection of node 3 after node 2 receives beam, then again
Use path 2>3>5 beams sent.
Obviously, the above embodiment of the present invention be only to clearly illustrate example of the present invention, and not be pair
The restriction of embodiments of the present invention may be used also on the basis of the above description for those of ordinary skill in the art
To make other variations or changes in different ways, all embodiments can not be exhaustive here, it is every to belong to this hair
Row of the obvious changes or variations that bright technical solution is extended out still in protection scope of the present invention.
Claims (6)
1. a kind of space delay tolerant network connects the countermeasure surprisingly to fail, which is characterized in that this method includes following step
Suddenly：
S1, judge whether connection occurs unexpected failure according to the transmission situation of beam in link；
S2, when finding Joint failure, other nodes are noticed into the connection of failure, and restore detection beam detection failure using connection
Connection whether restore, the connection of recovery noticed into other nodes after judging that the connection restores；
S3, when node receive Joint failure advertised information or connection restore advertised information after, update the node locality connection meter
The failure state accordingly connected in drawing；
S4, routing is calculated for beam, the beam that failure connection is foreclosed, and preferentially forwards remaining life span small；
Wherein, step S1 further comprises following sub-step：
S1.1, failure state flag bit is added in original link information in the works in the connection of node, and establishes Shu Chongchuan notes
Record list and failure linkage record list, Shu Chongchuan record the source node of list records beam, source service number, generated time stamp and under
One hop node, failure linkage record list records failure connection start node, terminal node, terminate the time, minimum detection when
Between interval, connection restores probe timer, failure notification sends flag bit and connection recovering mark position；
S1.2, according to the transmission situation of beam in link, utilize failure state flag bit, Shu Chongchuan record lists and failure connection note
Record list judges whether connection occurs unexpected failure；
Step S1.2 further comprises following sub-step：
S1.2.1, when beam arrives, first determine whether the destination node of beam is local node, if it is thening follow the steps
S1.2.2, it is no to then follow the steps S1.2.3；
S1.2.2, judge whether beam is Joint failure state advertisement beam according to the flag bit and purpose service number of beam, if it is
In connection, the failure state connected is noticed in update in the works；
S1.2.3, judge whether beam retransmits, it is no to then follow the steps S1.2.4 if not thening follow the steps S2；
S1.2.4, it is checked whether according to the flag bit and purpose service number of beam and restores detection beam for connection, if it is connected extensive
Detection beam is retransmitted again, which is abandoned, no to then follow the steps S1.2.5；
S1.2.5, the record for whether having the beam in Shu Chongchuan record lists checked, if the retransmission information for recording beam without if, institute
It includes the source node of beam, source service number, generated time stamp and next-hop node to state retransmission information, then executes step S2；If
Then follow the steps S1.2.6；
Whether S1.2.6, the next-hop node for judging beam and the next-hop node retransmitted in recording are consistent, if inconsistent more
Next-hop node in record, is changed to the next-hop node of Shu Dangqian, and execute step S2 by the re-transmission record of new beam；Otherwise it holds
Row step S1.2.7；
S1.2.7, judge that the connection of the next-hop node of beam disabled status occurs for local node, in the works will in locality connection
The linkage flag of local node to beam next-hop node is failure；Check failure linkage record list in whether the existing connection
Record, if it does not exist, then recorded in linkage record list of failing the failure connection information, it is described failure connection letter
Breath includes that start node, terminal node, termination time, minimum detection time interval and connection restore probe timer, and execute
Step S2；It is not re-recorded if the record of the existing connection, executes step S2.
2. space delay tolerant network according to claim 1 connects the countermeasure surprisingly to fail, which is characterized in that institute
State Joint failure state advertisement beam loading section record connection start node, terminal node, initial time, terminate the time and
Failure mark.
3. space delay tolerant network according to claim 1 connects the countermeasure surprisingly to fail, which is characterized in that step
Rapid S2 further comprises following sub-step：
S2.1, node open failure linkage record list execute step S2.2；
S2.2, it checks with the presence or absence of failure linkage record in list, and if so, finding first failure linkage record, executes
Step S2.3；It is no to then follow the steps S2.10；
S2.3, it checks whether the failure recovery flag bit of the failure linkage record is 1, has if it is illustrated the connection of failure
Restore, executes step S2.4；Otherwise illustrate that the connection of failure restores not yet, execute step S2.5；
S2.4, the failure state flag bit accordingly connected is labeled as 0 in the works in locality connection, according in failure linkage record
The termination time calculate failure notification domain, it is 0 that will notice the failure flag tag in beam format, generates Joint failure state advertisement
Beam is sent to the node in failure notification domain, informs that the connection of other nodes is recovered, deletes and closed in failure linkage record list
In the record of the connection, step S2.9 is executed, checks the next failure connection recorded in list；
S2.5, check that failure notification sends whether flag bit is 1, if it is illustrates to be transmitted across the failure about the connection
Notice executes step S2.7；Otherwise explanation sends failure notification not yet, executes step S2.6；
S2.6, the failure notification domain that the connection is calculated according to the termination time in failure linkage record, will be in notice beam format
The flag tag that fails is 1, generates Joint failure state advertisement beam and is sent to the node in failure notification domain, informs that other nodes connect
Connect no longer valid, and it is 1 that the failure notification in failure logging (record), which is sent flag tag, executes step S2.7；
S2.7, check that Joint failure restores whether probe timer expires, and thens follow the steps S2.8 if expired, otherwise executes step
Rapid S2.9；
S2.8, connection recovery detection beam is sent, the destination node of beam is set as the terminal node of the connection, and service number is set as
16, and reset connection and restore probe timer, execute step S2.9；
S2.9, check that next failure linkage record whether there is, and if so, executing step S2.3 to it；If do not deposited
Then illustrating to have had stepped through failure linkage record, is executing step S2.10；
S2.10, suspend mode one second, return to step S2.2 executes new round detection.
4. wanting the space delay tolerant network described in 3 to connect the countermeasure surprisingly to fail according to right, which is characterized in that step
S2 further includes following sub-step：
S2.11, it checks whether beam is that connection restores detection beam after beam is sent successfully, if it is illustrates that connection is recovered,
Execute step S2.12；It is no to then follow the steps S2.13；
S2.12, start node is found from failure linkage record list is the next-hop nodes that local node, terminal node are beam
Connection, by the failure recovery flag bit of the connection be labeled as 1, in step S2.3 as connection recovery mark；
S2.13, the information that the beam whether is recorded in Shu Chongchuan record lists checked, if there is then deleting the record.
5. wanting the space delay tolerant network described in 3 to connect the countermeasure surprisingly to fail according to right, which is characterized in that described
Failure notification domain be connection meet in the works the time started be less than failure connection terminate the time all connections start node and
Terminal node.
6. space delay tolerant network according to claim 1 connects the countermeasure surprisingly to fail, which is characterized in that step
Suddenly the detailed process of S4 is：
It calculates and route for beam, if beam, which is connection, restores detection beam, be sent to detected neighbor node；If it is not, then
The connection of failure is excluded except path when calculating routing, and compares the remaining life span of the beam and the beam in queue, is pressed
The remaining ascending sequence of life span is sent.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610021507.4A CN105681203B (en) | 2016-01-14 | 2016-01-14 | A kind of countermeasure that the connection of space delay tolerant network is surprisingly failed |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610021507.4A CN105681203B (en) | 2016-01-14 | 2016-01-14 | A kind of countermeasure that the connection of space delay tolerant network is surprisingly failed |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105681203A CN105681203A (en) | 2016-06-15 |
| CN105681203B true CN105681203B (en) | 2018-07-20 |
Family
ID=56300377
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610021507.4A Expired - Fee Related CN105681203B (en) | 2016-01-14 | 2016-01-14 | A kind of countermeasure that the connection of space delay tolerant network is surprisingly failed |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105681203B (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108833063B (en) * | 2018-08-29 | 2021-04-27 | 新华三技术有限公司 | Message retransmission method and device |
| CN111147198B (en) * | 2020-01-02 | 2021-05-25 | 中科驭数（北京）科技有限公司 | Data retransmission method and device |
| CN111262941B (en) * | 2020-01-17 | 2021-08-20 | 杭州涂鸦信息技术有限公司 | Method for reconnecting cloud server and electronic equipment |
| CN111510380B (en) * | 2020-04-13 | 2022-08-09 | 中国人民解放军国防科技大学 | Fault-tolerant routing method, device and system for delay tolerant network |
| CN112803988B (en) * | 2021-01-25 | 2022-08-02 | 哈尔滨工程大学 | Hybrid contact graph routing method based on link error rate prediction |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102571571A (en) * | 2011-12-28 | 2012-07-11 | 南京邮电大学 | Multilayer effective routing method applied to delay tolerant network (DTN) |
| CN102780637A (en) * | 2012-08-14 | 2012-11-14 | 虞万荣 | Routing method for data transmission in space delay/disruption tolerant network |
| CN102883397A (en) * | 2012-09-07 | 2013-01-16 | 航天恒星科技有限公司 | Data forwarding method of delay/disruption tolerant network (DTN) facing space environment |
| CN105072031A (en) * | 2015-08-04 | 2015-11-18 | 北京航空航天大学 | Delay-tolerant disruption-tolerant network routing method based on link transmission capacity |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8149716B2 (en) * | 2007-08-20 | 2012-04-03 | Raytheon Bbn Technologies Corp. | Systems and methods for adaptive routing in mobile ad-hoc networks and disruption tolerant networks |
-
2016
- 2016-01-14 CN CN201610021507.4A patent/CN105681203B/en not_active Expired - Fee Related
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102571571A (en) * | 2011-12-28 | 2012-07-11 | 南京邮电大学 | Multilayer effective routing method applied to delay tolerant network (DTN) |
| CN102780637A (en) * | 2012-08-14 | 2012-11-14 | 虞万荣 | Routing method for data transmission in space delay/disruption tolerant network |
| CN102883397A (en) * | 2012-09-07 | 2013-01-16 | 航天恒星科技有限公司 | Data forwarding method of delay/disruption tolerant network (DTN) facing space environment |
| CN105072031A (en) * | 2015-08-04 | 2015-11-18 | 北京航空航天大学 | Delay-tolerant disruption-tolerant network routing method based on link transmission capacity |
Non-Patent Citations (2)
| Title |
|---|
| Towards flexibility and accuracy in space DTN communications;Nikolaos Bezirgiannidis等;《CHANTS "13 Proceedings of the 8th ACM MobiCom workshop on Challenged networks》;20130930;第43-48页 * |
| 一种针对DTN通道失效的可靠性方法研究;邵清等;《计算机仿真》;20130515;第187-190页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105681203A (en) | 2016-06-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105681203B (en) | A kind of countermeasure that the connection of space delay tolerant network is surprisingly failed | |
| CN100417080C (en) | Method for detecting network chain fault and positioning said fault | |
| CN101953124B (en) | Constructing repair paths around multiple non-available links in a data communications network | |
| US7715396B2 (en) | Network routing | |
| JP6264743B2 (en) | Duplicate packet suppression | |
| CN105636011A (en) | Communications methods, system and apparatus | |
| CN107547371A (en) | A kind of message forwarding method and device | |
| US20060104210A1 (en) | Dynamic network management | |
| CN1983911B (en) | Method and system for faster detection and retransmission of lost tcp segments | |
| CN103166852B (en) | The route tracing method of LSP and routing device in MPLS network | |
| JP5363658B1 (en) | RELAY DEVICE, RELAY DEVICE CONTROL METHOD, AND NETWORK SYSTEM | |
| CN103391247A (en) | Fast reroute using loop free alternate next hop for multipoint label switched path | |
| CN101572584B (en) | Error detection method, equipment and system for message | |
| CN104038322B (en) | Intermediate node, communication network and its data transfer control method | |
| CN101335689A (en) | Traceroute implementing method and equipment | |
| CN103959722A (en) | System to improve Ethernet network | |
| US8254271B1 (en) | Point-to-multipoint connectivity verification | |
| CN108449276B (en) | Route convergence method and device | |
| WO2012075934A1 (en) | Method for detecting message loop, routing agent apparatus and networking system | |
| US20110202671A1 (en) | Method and Apparatus for Mobility Agent Recovery | |
| CN104885523B (en) | Fault handling method, packet data network, mobile management entity and network system | |
| CN101964743A (en) | Multiprotocol label-switched path APS (Active Protection System) protection and management method, equipment and system | |
| CN101453744B (en) | Service control method and apparatus | |
| CN107612772A (en) | The node state detection method and device of payment system | |
| US7869350B1 (en) | Method and apparatus for determining a data communication network repair strategy |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20180720 Termination date: 20220114 |