An address management method, system, and device to avoid a problem that a same Internet Protocol (IP) address is assigned to different packet data unit (PDU) sessions and to effectively use IP addresses in an address pool. The method includes: obtaining, by a session management network element, an identifier of a user plane function network element serving a terminal and session information of the terminal; determining, by the session management network element based on the identifier of the user plane function network element and the session information, an address pool identifier corresponding to the session; sending, by the session management network element, the address pool identifier to a server, where the address pool identifier is used to assign an IP address to the session; and receiving, by the session management network element from the server, the IP address corresponding to the session.

An address management method, system, and device to avoid a problem that a same Internet Protocol (IP) address is assigned to different packet data unit (PDU) sessions and to effectively use IP addresses in an address pool. The method includes: obtaining, by a session management network element, an identifier of a user plane function network element serving a terminal and session information of the terminal; determining, by the session management network element based on the identifier of the user plane function network element and the session information, an address pool identifier corresponding to the session; sending, by the session management network element, the address pool identifier to a server, where the address pool identifier is used to assign an IP address to the session; and receiving, by the session management network element from the server, the IP address corresponding to the session.

Embodiments are presented for collaborative device address generation between a wireless client device and a network infrastructure component, such as a wireless access point. The wireless client device and network infrastructure component share information to facilitate collaborative generation of a sequence of device addresses. This shared information includes, in some embodiments, key information and moving factor information. The key information and moving factor information is used to generate a token. A sequence of tokens is generated by updating the moving factor as each token is generated. A corresponding sequence of device addresses are then derived based on the sequence of tokens. Since the wireless client device and the network infrastructure device apply equivalent methods to generate respective sequences of addresses, the network infrastructure is able to efficiently identify a source wireless client device when observing a new device address on a wireless network.

Embodiments are presented for collaborative device address generation between a wireless client device and a network infrastructure component, such as a wireless access point. The wireless client device and network infrastructure component share information to facilitate collaborative generation of a sequence of device addresses. This shared information includes, in some embodiments, key information and moving factor information. The key information and moving factor information is used to generate a token. A sequence of tokens is generated by updating the moving factor as each token is generated. A corresponding sequence of device addresses are then derived based on the sequence of tokens. Since the wireless client device and the network infrastructure device apply equivalent methods to generate respective sequences of addresses, the network infrastructure is able to efficiently identify a source wireless client device when observing a new device address on a wireless network.

A DNS (Domain Name Server) proxy is configured as a DNS server for clients on the enterprise network to send two or more DNS queries to collect each available IP addresses on a SDWAN member link. IP address collection can be responsive to receiving a DNS request from a client for assigning a FQDN (Fully Qualified Domain Name). Service quality can be evaluated for the service on each member link of the IP addresses. An IP address is assigned to the client based on the service quality evaluation. A notification is transmitted to the client in a DNS response to the IP address request, with the chosen IP address information for configuration.

A DNS (Domain Name Server) proxy is configured as a DNS server for clients on the enterprise network to send two or more DNS queries to collect each available IP addresses on a SDWAN member link. IP address collection can be responsive to receiving a DNS request from a client for assigning a FQDN (Fully Qualified Domain Name). Service quality can be evaluated for the service on each member link of the IP addresses. An IP address is assigned to the client based on the service quality evaluation. A notification is transmitted to the client in a DNS response to the IP address request, with the chosen IP address information for configuration.

A solution is disclosed for providing automatic multicast address assignment and conflict resolution for AV streams multicast over a networked AV system. The solution includes a device for monitoring the system for messages associated with AV streams multicast over the system and implementing a conflict resolution protocol when a conflict of multicast addresses is detected, where the conflict resolution protocol utilizes automatically randomly selecting a preliminary multicast address from a defined range of addresses.

A solution is disclosed for providing automatic multicast address assignment and conflict resolution for AV streams multicast over a networked AV system. The solution includes a device for monitoring the system for messages associated with AV streams multicast over the system and implementing a conflict resolution protocol when a conflict of multicast addresses is detected, where the conflict resolution protocol utilizes automatically randomly selecting a preliminary multicast address from a defined range of addresses.

Embodiments are presented for collaborative device address generation between a wireless client device and a network infrastructure component, such as a wireless access point. The wireless client device and network infrastructure component share information to facilitate collaborative generation of a sequence of device addresses. This shared information includes, in some embodiments, key information and moving factor information. The key information and moving factor information is used to generate a token. A sequence of tokens is generated by updating the moving factor as each token is generated. A corresponding sequence of device addresses are then derived based on the sequence of tokens. Since the wireless client device and the network infrastructure device apply equivalent methods to generate respective sequences of addresses, the network infrastructure is able to efficiently identify a source wireless client device when observing a new device address on a wireless network.

A device implementing the subject system may include at least one processor configured to receive, by a first system process, a first network address that corresponds to a domain name that was resolved by a second system process, the resolving having been responsive to a resolution request therefor by an application process. The at least one processor may be further configured to receive, by the first system process, a second network address for which a network connection was opened by the application process. The at least one processor may be further configured to, responsive to determining that the application process opened a network connection for a network address for which the application process did not provide, to the second system process, a resolution request for the corresponding domain name, provide, by the first system process, an indication of the network address in conjunction with an indication of the application process.