A connection management apparatus of a relay system specifies, when terminal identification information for identifying a target terminal is acquired from a client terminal, a first relay apparatus that relays communication, and specifies connecting information for the client terminal to connect to the first relay apparatus. The connection management apparatus stores the specified connecting information and the terminal identification information in a storage in association with each other, and notifies the client terminal of the specified connecting information. When the specified first relay apparatus receives access based on the connecting information from the client terminal, the specified first relay apparatus relays the communication between the client terminal and the target terminal on the basis of the terminal identification information associated with the connecting information.

Systems and methods are disclosed for determining a topology of a network comprising a plurality of intermediary devices and intermediary paths. One method includes transmitting probes having a TTL value with a destination set to a destination device; receiving, for each probe transmitted, a response including an IP address of a responding device; determining whether more than one responding device has responded to the probes; determining whether more than one responding device has been found for two previous transmissions of probes when more than one responding device has responded to the probes; and transmitting, for each more than one responding device, probes having a decreased TTL value with a destination set to one of the IP addresses of the more than one responding devices, when more than one responding device has been found for two previous transmissions.

A computer-implemented method, in an example, may include calculating a time-to-live value for at least one packet based on a hop count between each of a plurality of processing element containers within an application streaming network; updating at least one processing element container output connection based on the calculated time-to-live value; and monitoring a streams resource metrics service for a change in a packet delivery rate.

A method for establishing a stream in a Time-Sensitive Networking (TSN) network, wherein a request message is sent by a stream subscriber to a Domain Name System (DNS) server, upon which entries are stored that each comprise a stream identifier of a first type assigned to a stream, and a stream identifier of a second type that is different from the first type and is assigned to the respective stream, and the specification of a predefined type exclusively used for, or forms these types of entries, where the request message comprises a stream identifier of the first type and the predefined type known to the at least one stream subscriber, where the stream subscriber receives a response message from the DNS server, which contains a stream identifier of the second type belonging to the stream, and where the stream subscriber logs on to the stream using the stream identifier obtained.

A method, an apparatus, and a system for implementing rate adjustment at a transmit end. The method includes: receiving, by a first network device, a first data packet sent by a previous-hop network device, where the first data packet includes a first required rate, a first deadline, and a first sending rate that correspond to a first data stream; obtaining, by the first network device, a second sending rate of the first data stream; and sending, by the first network device, a feedback packet to a second network device when the second sending rate is less than the first sending rate, where the feedback packet includes the second sending rate, and the feedback packet is used to instruct the second network device to inform, based on the second sending rate, the transmit end to adjust a rate for sending the first data stream.

Systems and methods are disclosed for determining a topology of a network comprising a plurality of intermediary devices and intermediary paths. One method includes transmitting probes having a TTL value with a destination set to a destination device; receiving, for each probe transmitted, a response including an IP address of a responding device; determining whether more than one responding device has responded to the probes; determining whether more than one responding device has been found for two previous transmissions of probes when more than one responding device has responded to the probes; and transmitting, for each more than one responding device, probes having a decreased TTL value with a destination set to one of the IP addresses of the more than one responding devices, when more than one responding device has been found for two previous transmissions.

Methods for tracing a packet in a pipeline comprising a set of tables, in an SDN using OpenFlow. The packet comprises a trace bit, and is provided with a TTL value. A first network node indicates to a second network node to have each flow table decrement the TTL value by 1, based upon the trace bit. The first network node initially sets the TTL to be 1, and then sends the packet to a first table in the second network node. The first network node receives the packet, from another table in the set, and for every remaining table, and one table at a time: a) increments the TTL value by 1, and b) repeats the sending, and the receiving, until a last table is reached or a criterion is met. The first network node then indicates a route followed by the packet.

A domain name access method and a device are described. As described herein, a domain name server (DNS) server performs resolution on a domain name requested by the terminal device. The DNS server may then send an internet protocol (IP) address of an application server obtained through the resolution and use condition information to the terminal device. With this, communication efficiency of the terminal device can be improved, and waste of transmission resources in a communications system is also avoided.

A MANET protocol, comprising: receiving a data packet (DP) from a current sender (CS) by a recipient, defining: an identity of the CS, a prior sender (PS) from which CS received DP, and a target recipient (ID), a count (HC) of hops previously traversed by DP, and a sequence identifier (SI); updating a forwarding table (FT) to mark CS as being reachable in one hop, and PS as being reachable in two hops via CS as next hop; determining if ID is the recipient; determining whether to rebroadcast by recipient, if and only if the SI is not present in a list of prior SIs; and selectively rebroadcasting DP by recipient in dependence on said determining, modified by: replacement of CS with an identity of the recipient, PS with CS, and ID with a next hop from the FT if present, and incrementing HC.

User equipment (UE) can be connected to both a first base station and a second base station. A flow controller at the first base station can determine packet latency goals associated with packets. The flow controller can also determine connection latencies associated with a first connection from the first base station to the UE and a second connection from the second base station to the UE, where one leg of a split bearer passes from the first base station to the UE over the first connection and another leg of the split bearer passes from the first base station to the second base station and then to the UE over the second connection. The flow controller can route packets with lower packet latency goals via the leg of the lower-latency connection, and route other packets with higher packet latency goals over the leg of the higher-latency connection.