Consideration for IP-Based TVR (Time-Variant Routing)

There were three use cases had been defined in the TVR's use case document . The first is resource preservation; one example of a network where nodes must perform resource preservation is an energy-harvesting, wireless sensor network. The second is operating efficiency; one example of a network where nodes might seek to optimize operating cost is a set of nodes operating over cellular connections that charge both On-Peak and Off-Peak data rates. The third is dynamic reachability; some examples of this use case are mobile satellites, predictable moving vessels and so on. Satellite network and terrestrial network use different physical and link layer protocols, making it difficult to achieve convergence at the bottom layer. This problem can be solved at the network layer. On the one hand, TCP/IP is a simple and open protocol, which can help break the boundaries between heterogeneous networks to realize global interconnection. On the other hand, the business is basically based on IP, and the development of IP-based space network can help realize the business integration and collaboration between heaven and earth and the integration and sharing of network resources, thus reducing the cost of network construction and operation and maintenance, and not only realizing the integration of heaven and earth in a more efficient way, but also better meeting the needs of personal communication and information access, and improving the user experience. The development of IP-based space network can not only realize the integration of air and sky more efficiently, but also better satisfy the needs of personal communication and information acquisition, and improve the user experience and satisfaction. Although the TCP/IP protocol architecture is very mature for terrestrial networks, there are still many challenges in applying it to the heterogeneous satellite network with time-variant characteristics. The current terrestrial network is homogeneous and topologically fixed by default, while the satellite network, which has time-variant characteristics, is a heterogeneous and dynamic network. This document makes some considerations on using IP for the satellite network.

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here.

Considering requirements for on using IP for the satellite network.

Networking using IP provides superior flexibility, enhanced scalability, and support for dynamic routing and mobile access, among other things. However, the topology of satellite networks containing time-varying characteristics changes frequently, and traditional static routing techniques cannot meet the demand. Therefore, dynamic routing, such as OSPF, is needed to adapt to the dynamic changes in network topology. Therefore, o MUST provide a discovery and resolving methodology for the dynamic routing.

Satellite network may need to support multiple service types, such as voice, video, data, etc., which have different requirements for QoS. Therefore, it is necessary to design effective QoS guarantee mechanisms, such as differential service (DiffServ), integrated service (IntServ), etc., to meet the needs of different services.. Therefore, o MUST support Quality of Service (QoS) guarantee for the needs of different services.

Since a satellite network may be composed of several different heterogeneous networks, it is necessary to address the need for multiple heterogeneous network connections. Therefore, o MUST Support heterogeneous network interconnectioncation.

This document This document makes some considerations on using IP for the satellite network, which is one of TVR's use cases.

TBD.