Techniques are described for detecting duplicate IP addresses at a DHCP relay agent. Embodiments identify a list of DHCP clients that have valid IP address leases from one or more DHCP servers. Additionally, network traffic from a first node passing through the DHCP relay agent is monitored. Embodiments then determine whether the first node is using a duplicate IP address, based on the monitored network traffic and the identified list of DHCP clients.

A multi-access edge computing device configured to be connected to first and second networks with different radio access technologies comprises a routing module, a comparison module and a control module. The control module performs steps when determining a user device connected to the first network intends to switch to the second network, wherein the steps comprise: according to identity information of the user device, looking up a target address in a comparison table in the comparison module, notifying the routing module to temporarily store a data packet corresponding to the user device and the first network, notifying the user device to release an original used address on the first network interface and then assigning the target address identical to the original used address to the second network interface of the user device, and transmitting the temporarily stored data packet to the second network interface of the user device.

A method for electronic device identifier assignment at a host computing device includes receiving, from a separate electronic device, a current local identifier of the separate electronic device and a full unique identifier of the separate electronic device. A host-specific identifier is assigned to the separate electronic device by, based at least in part on determining that the current local identifier of the separate electronic device is included in a set of local identifier values available for assignment, assigning the host-specific identifier to the separate electronic device with a same local identifier value as the current local identifier. Based at least in part on determining that the current local identifier of the separate electronic device is already assigned by the host computing device to a different separate electronic device, the host-specific local identifier is selected from the set of local identifier values available for assignment and assigned to the separate electronic device.

A technique that manages device addresses involves: sending, at a first device, a probe message to at least one other device, wherein the probe message includes a first MAC address of the first device, a first identifier of the first device, and an IP address to be assigned to the first device; receiving a message from a second device, the message including a second MAC address of the second device, a second identifier of the second device, and an IP address of the second device; and according to a determination that the IP address of the second device is the same as the IP address to be assigned to the first device, providing a probe alert including the identifies and indicating that an IP address conflict occurs. By writing device IDs in messages transmitted across a network, devices that may have an IP address conflict can be quickly detected.

A technique that manages device addresses involves: sending, at a first device, a probe message to at least one other device, wherein the probe message includes a first MAC address of the first device, a first identifier of the first device, and an IP address to be assigned to the first device; receiving a message from a second device, the message including a second MAC address of the second device, a second identifier of the second device, and an IP address of the second device; and according to a determination that the IP address of the second device is the same as the IP address to be assigned to the first device, providing a probe alert including the identifies and indicating that an IP address conflict occurs. By writing device IDs in messages transmitted across a network, devices that may have an IP address conflict can be quickly detected.

An IP communication system has a switching hub having at least first to (n+1)-th ports (where n is an integer equal to or greater than two); first to n-th IP devices connected to the respective first to n-th ports; and an IP address setting unit connected to the (n+1)-th port. The IP address setting unit transmits, to the switching hub, a first port open instruction to open the first port and to close the second to n-th ports, and thereafter transmits, to the switching hub, a first IP address to be set to the first IP device. Upon reception of the first port open instruction from the IP address setting unit, the switching hub opens the first port and closes the second to n-th ports. Upon reception of the first IP address, the switching hub transmits the first IP address to the first IP device.

Example session management methods and apparatus are described. One example method includes allocating a first IP address and a first user plane network element to a terminal by a session management network element. The first user plane network element allocated to the terminal supports the first IP address.

Example session management methods and apparatus are described. One example method includes allocating a first IP address and a first user plane network element to a terminal by a session management network element. The first user plane network element allocated to the terminal supports the first IP address.

A communication apparatus has a first interface for connecting with a first network and a second interface for connecting with a second network. The communication apparatus detects that an address used in the first network is changed, and furthermore, when it detects that the address that is changed in the first network duplicates an address being used in the second network, disconnects a connection of a link layer with the second network, and after the disconnection, reconstructs the second network using an address which is not duplicated by the changed address.

A replica service of a Content Centric Network can host content published by various publishers, without having to explicitly advertise a name prefix associated with these various publishers. Consumers across CCN can generate an Interest that includes a location-independent name associated with a replica service that hosts content for a given publisher, and includes a hash of the desired Content Object. CCN nodes can forward the Interest to the corresponding replica service based on the Interest's name, and the replica service can return a nameless Content Object whose hash matches the Interest's hash value. It may be possible for nameless Content Objects from various publishers to have matching hash values from time to time. CCN nodes can reduce collisions of nameless Content Objects by using a Publisher ID specified in an Interest to find a matching Content Object that was published by a desired publisher.