Abstract:
Es wird ein Verfahren zum Betrieb eines Automatisierungsgerätes (12) angegeben, bei dem im Zusammenhang mit oder vor dem Aufbau einer Kommunikation zu einem entfernten Kommunikationsteilnehmer (20) anhand einer den jeweiligen entfernten Kommunikationsteilnehmer (20) identifizierenden Kennung eine zur Kommunikation mit diesem entfernten Kommunikationsteilnehmer (20) verwendbare Adresse ermittelt wird, wobei es sich bei der Kennung insbesondere um eine Adresse in einem IPv4-Format und bei der zur Kommunikation mit dem entfernten Kommunikationsteilnehmer (20) verwendbaren Adresse um eine Adresse in einem IPv6-Format handelt, so dass in transparenter Weise auch für Automatisierungsgeräte und Applikationen, die bisher nur für die Verarbeitung von Adressdaten in einem bisher gebräuchlichen Format, also insbesondere dem IPv4-Format vorgesehen sind, eine transparente Migration zu einem zukünftigen Adressformat, also insbesondere IPv6, möglich ist.
Abstract:
The invention relates to a communication system (100) comprising at least one first communication network (10- 1, 10-2) designed for communication according to a first protocol, at least one second communication network (20) designed for communication according to a second protocol, and at least one third communication network (30-1, 30-2) designed for communication according to the first and second protocols. The at least one first communication network (10-1, 10-2) and/or the at least one second communication network (20) and/or the at least one third communication network (30-1, 30-2) are coupled together for the exchange of messages. The inventive system also comprises a mobile computer (40) designed for communication according to the first and second protocols, and a target computer (42) which is designed for communication according to the first protocol and/or the second protocol, and is associated with the first, second or third communication network (10-1, 10-2, 30, 30- 25 1, 30-2). The inventive communication system is designed in such a way that when the mobile computer (40) is connected to a network connection computer (31) of the third communication network (30-1, 30-2), before the establishment of a communication connection to the target computer, the protocol to be used for communication with the network connection computer (31) is determined.
Abstract:
Systems and methods ensure that datagrams retain integrity in light of the problems associated with the internetworking protocol's use of datagram identifiers drawn from a first pool of datagram identifiers. The methods involve controlling the use of datagram identifiers to ensure that only certain identifiers are allowable. A second pool of datagram identifiers is created that is different from the first pool. A datagram identifier is drawn from the second pool and assigned to a datagram in a manner that the datagram identifier is controlled from being reused during the lifetime of the datagram. In alternative embodiments the number of available datagram identifiers is either increased through optional header fields, or reduced through tracking allowed datagram identifiers. A first host notifies a second host of an allowed identifier. The second host uses the allowed identifier as a datagram identifier.
Abstract:
A method of defending against a denial-of-service (DoS) attack on an IPv6 neighbor cache includes steps of determining a number of neighbor cache entries currently stored in the neighbor cache and then determining whether the number of entries exceeds a neighbor cache threshold that is less than a neighbor cache limit defining a maximum capacity of the neighbor cache. When the number of entries in the neighbor cache exceeds the neighbor cache threshold, stateless neighbor resolution is triggered. Stateless neighbor resolution entails sending a neighbor solicitation to resolve an address for an incoming packet without logging a corresponding entry in the neighbor cache. Additional techniques that complement the above method involve purging of neighbor cache entries designated as incomplete, prioritization of the entries based on trustworthiness, shortening the incomplete-status timer to less than 3 seconds, and curtailing the number of retransmissions of the neighbor solicitations
Abstract:
The object of the invention is to achieve seamless transition of applications between different protocols. A network system adopting a first IP protocol is provided. The network system comprises an address allocating server and a communication terminal supporting both the first IP protocol and a second IP protocol different from the first IP protocol, wherein the address allocating server dynamically allocating an address of the second IP protocol to the communication terminal. The communication terminal comprises a dynamic address manager for acquiring said dynamically allocated address of the second IP protocol of said communication terminal from the address allocating server and a second IP protocol address of the destination of a second IP protocol packet from a second IP protocol application, and an address adapter for encapsulating the second IP protocol packet from the second IP protocol application into a first IP protocol packet, wherein the second IP protocol address of said communication terminal in the header of the second IP protocol packet and the second IP protocol address of the destination are encapsulated into said first IP protocol packet.
Abstract:
A method for communicating between serving general packet radio service support nodes SGSN, adapting to the mobile communication network which coexists multiple SGSN supporting different IP protocol version, that characterizes in, in advance configuring for SGSN with IP address of all IP protocol version supported by itself, when source SGSN initiates communication to target SGSN, first detecting IP protocol version supported by target SGSN, then based on the detected result, communicating with target SGSN using IP protocol version supported by source/target. The invention can implement mutually communicating between SGSN supporting the different IP protocol version, improving compatibility of network.
Abstract:
An IPv4 node is able to send an IPv4 packet to an IPv4 destination via an IPv6 access network, based on translation of the IPv4 packet into an IPv6 packet for transmission via the IPv6 access network. The IPv4 packe is translated into the IPv6 packet by a local gateway. The IPv6 packet has an IPv6 source address that includes a prescribed address prefix assigned to the local gateway, and an IPv4 address of the IPv4 node. The IPv6 packet also includes an IPv6 destination address that includes a second a address prefix assigned to a remote gateway, and a second IPv4 adress of the IPv4 destination. The IPv6 packet is converted by the remote gateway into an IPv4 packet for reception by the IPv4 destination via an IPv4 network.
Abstract:
A telecommunications system comprises a gateway support node (GGSN) operable to establish a tunnelling protocol bearer for communicating IPv6 internet protocol packets to and from a user equipment (UE) across an Ipv4 internet protocol packet data network. An address allocation server (DHCP) allocates an IPv6 address to the user equipment for the communication, based on an IPv4 link local address comprising a tunnelling end identifier of the tunnelling protocol bearer which ends at the gateway support node.
Abstract:
A method for managing the route in the Virtual Private Network based on IPv6 includes the steps: A, When the Provider Edge PE or the Customer Edge CE in the VPN based on IPv6 issuing the route, the issued route carrying the VPN-ID attribute and Export Route Targets which indicate the different VPNs; B, after the PE in the VPN based on the IPv6 receiving the route issued judging whether the VPN-ID attribute and the Export Route Targets carried by the route match the VPN-ID attribute and the import route targets attribute of the Route Targets set by at least one of the all sites connected with itself respectively, if it is, then doing the step C; otherwise, doing not receive the route, ending; C, the PE receiving the route, and storing the route according to the VPN-ID attribute and the corresponding Route Targets.