Various embodiments of the teachings herein include methods for implementing communication conversion between a server-client system and a publish-subscribe (pub-sub) system. An example may include: receiving a message from the pub-sub system, wherein a topic of the message includes information related to a target service in the server-client system to which the message is to be sent, and a payload of the message includes identification information of a consumer in the pub-sub system, wherein the consumer is to receive a response message from the server-client system; parsing the message to determine a host and a service provider that provide the target service, and the consumer who is to receive the response message; sending a request message for the target service to the service provider on the determined host; receiving the response message; adding the identification information to the response message; and sending it to the pub-sub system.

Methods, systems, and devices for wireless communications are described, including identifying a first attribute value associated with a first access point; receiving a second attribute value; and determining that the first attribute value associated with the first access point is the same as the received second attribute value. An attribute value may be an n-bit value, where n is an integer. The n-bit value may identify a BSS color. The n-bit value may, additionally or alternatively, indicate other BSS color information such as a BSSID, ESSID, SSID, or a combination thereof. It is helpful when devices detect BSS attribute value (e.g., BSS color, BSSID, MAC address, ESSID) overlap and notify other associated devices (e.g., STAs, APs) of this overlap so that a device may cease using an attribute value for power save or channel access decisions, and facilitate attribute value adjustment and correction to eliminate a BSS collision.

An apparatus for helping with multicast domain name service (MDNS) discovery includes one or more processors configured to receive a first MDNS query from the resource-seeking device, receive a first MDNS response from the resource-providing device, and generate a second MDNS response according to the first MDNS response. The second MDNS response is generated at least by including a resource record from the first MDNS response and setting a time-to-live (TTL) value of the resource record in the second MDNS response to be lower than an original TTL value as specified for the resource record in the first MDNS response. The second MDNS response is sent to the resource-seeking device in response to the first MDNS query. A hospitality establishment may thereby soft assign a media device to a user device while retaining the ability to change the media device assigned to the user device.

An apparatus for helping with multicast domain name service (MDNS) discovery includes one or more processors configured to receive a first MDNS query from the resource-seeking device, receive a first MDNS response from the resource-providing device, and generate a second MDNS response according to the first MDNS response. The second MDNS response is generated at least by including a resource record from the first MDNS response and setting a time-to-live (TTL) value of the resource record in the second MDNS response to be lower than an original TTL value as specified for the resource record in the first MDNS response. The second MDNS response is sent to the resource-seeking device in response to the first MDNS query. A hospitality establishment may thereby soft assign a media device to a user device while retaining the ability to change the media device assigned to the user device.

Systems and methods described herein provide a network tool that discovers device configurations for selected enterprise sites and automatically organizes the data to assist users, so they can build intents for network function policies in enterprise networks. An intent builder performs device discovery of network function (NF) instances in a customer network; retrieves configuration elements from the NF instances; normalizes the configuration elements; and generates a graphical user interface with rule paths based on the configuration elements. The network device receives, via the graphical user interface, user input to map source Internet protocol (IP) addresses in the rule paths to a user label and to map destination IP address in the rule paths to an application label. Based on the user input, the network device presents, via the graphical user interface, consolidated intents and generates vendor-agnostic policy rules from the consolidated intents.

Systems and methods described herein provide a network tool that discovers device configurations for selected enterprise sites and automatically organizes the data to assist users, so they can build intents for network function policies in enterprise networks. An intent builder performs device discovery of network function (NF) instances in a customer network; retrieves configuration elements from the NF instances; normalizes the configuration elements; and generates a graphical user interface with rule paths based on the configuration elements. The network device receives, via the graphical user interface, user input to map source Internet protocol (IP) addresses in the rule paths to a user label and to map destination IP address in the rule paths to an application label. Based on the user input, the network device presents, via the graphical user interface, consolidated intents and generates vendor-agnostic policy rules from the consolidated intents.

This application discloses a network capability exposure method, apparatus, and system. The method includes: An NEF receives a first request sent by an AF, where the first request includes an address of a target terminal device, and is used to request first information of the target terminal device; sends, to a first network element, a second request including the address, to request a first identifier of the target terminal device; receives the first identifier from the first network element; and sends, to a second network element, a third request including the first identifier, to request the first information.

Methods are provided in which a domain name system (DNS) service obtains a lookup request for information about a source of a traffic flow being transmitted to a network resource external of a service cluster and performs, based on the lookup request, a lookup operation for a microservice that is the source of the traffic flow, among a plurality of microservices of the service cluster registered with the DNS service. The methods further include providing information about the microservice based on the lookup operation. The information includes at least a name of the microservice for visibility of the microservice external of the service cluster.

Some embodiments establish for an entity a virtual network over several public clouds of several public cloud providers and/or in several regions. In some embodiments, the virtual network is an overlay network that spans across several public clouds to interconnect one or more private networks (e.g., networks within branches, divisions, departments of the entity or their associated datacenters), mobile users, and SaaS (Software as a Service) provider machines, and other web applications of the entity. The virtual network in some embodiments can be configured to optimize the routing of the entity's data messages to their destinations for best end-to-end performance, reliability and security, while trying to minimize the routing of this traffic through the Internet. Also, the virtual network in some embodiments can be configured to optimize the layer 4 processing of the data message flows passing through the network.

Some embodiments establish for an entity a virtual network over several public clouds of several public cloud providers and/or in several regions. In some embodiments, the virtual network is an overlay network that spans across several public clouds to interconnect one or more private networks (e.g., networks within branches, divisions, departments of the entity or their associated datacenters), mobile users, and SaaS (Software as a Service) provider machines, and other web applications of the entity. The virtual network in some embodiments can be configured to optimize the routing of the entity's data messages to their destinations for best end-to-end performance, reliability and security, while trying to minimize the routing of this traffic through the Internet. Also, the virtual network in some embodiments can be configured to optimize the layer 4 processing of the data message flows passing through the network.