A rules engine is adapted for analyzing each match produced by a domain discovery system as matching a seed domain. Utilizing a natural language processing (NLP) library, the rules engine determines segments from the match, assigns a lexical category to each segment based on the context in how a seed domain string is used, and compares the lexical category of the segment that is closest to the seed domain string with a lexical category of the seed domain string. Based on the comparing, the rules engine determines whether the match is relevant to the seed domain and, if not, the match produced by the domain discovery system is identified as a false positive and automatically removed from a set of matches produced by the domain discovery system for the seed domain.

Aspects relate to a physical cell identifier (PCI) change within a wireless network based on a primary synchronization signal (PSS) waveform. A scheduling entity, such as an integrated-access-backhaul (IAB) node within a radio access network (RAN), may communicate with a set of one or more scheduled entities, such as other IAB nodes and/or user equipment (UEs), utilizing a first PCI. The scheduling entity may then change from the first PCI to a second PCI, where the second PCI corresponds to a different PSS waveform than the first PCI. In some examples, the scheduling entity may change the PCI as a result of a PCI collision and/or PSS collision with a neighboring scheduling entity.

A method for verifying eligibility of a domain name registrant via a verification web interface for a domain name either registered or in the process of registration with a registrar over a communications network. The method comprising: provide a network link to the registrar or to a registry operator of the domain name; receive an event request for the domain name via the verification web interface including a claim ID associated with the domain name for a domain event; receive a verification request using the network link via the verification web interface including a registrant claim ID and registrant identification information, the registrant claim ID previously provided to the registrant; confirm matching of the registrant claim ID with the claim ID; obtain registrant verification information; access external verification information and compare against the registrant verification information; and send a confirm domain event message or a deny domain event message.

Control component and method for registering device names assigned to industrial automation devices or communication devices in a name service system, wherein in order to register device names assigned to industrial automation devices or communication devices in a name service system, at least selected automation or communication devices each comprise a name service component where the selected automation or communication devices control transmission of a registration request containing an assignment between their respectively assigned device name and at least one respectively configured communication network address to a name service server via their name service component, and where a control component is respectively assigned to the name service components and enables or blocks transmission of a registration request.

A first network enabled device is in a wireless local area network (WLAN). The first network enabled device determines whether a second network enabled device is present in the WLAN. The first network enabled device executes a rule having a condition based on whether the second network enabled device is present in the WLAN and a resulting action to be performed by the first network enabled device. If the condition is met, the first network enabled device performs the resulting action.

Methods and systems for managing domain names are disclosed. A server hosts a platform that interfaces with users. The server is operably coupled to the registry and domain management database, and receives transaction requests to assign tags to one or more domain names, the tags used as identifiers to associate information with the domain names. The server stores the domain names with one or more tags and associated information in the domain management database. The server receives a request to perform a registry event on a domain name and checks if there are tags associated with the domain name of which the event was requested. If there is no assigned tag the server performs the registry event action. If there is an associated tag the server complies with the tag and associated tag information.

Embodiments relate to systems, devices, and computer-implemented methods for managing domain name space collisions by accessing information, such as a domain name string, corresponding to a domain name resolution request and response. Based on at least the domain name string, a type of use value associated with the request can be determined. Based on at least the type of use value, a name collision risk value for the request can be determined. If the name collision risk value indicates there is a specified risk of a domain name string collision, then a domain name collision mitigation strategy can be generated and/or implemented.

Approaches presented herein enable generation of a multi-dimensional tag metric in a cloud resource management environment. More specifically, a tagging namespace is provided for managing a resource in the cloud resource management environment. This namespace comprises at least two dimensions and a plurality of positions. A set of tags associated with the resource are received into the tagging namespace. A match of each tag of the set of tags to a position within the namespace into which that tag was received is verified and an alert is triggered in the case verification fails. Alternatively, in the case verification is successful, the tag-containing namespace is validated as a multi-dimensional tag metric.

A licensing server object generator identifies a plurality of servers that can be used to obtain a license for accessing a feature of an application. The licensing server object generator determines, for the identified servers, network addresses and utilizes these network addresses to generate a plurality of data objects. Each data object specifies a subset of the network addresses for the servers. The licensing server object generator makes these data objects available to enable use of the data objects to obtain the license.

A method for naming a Domain Name System (DNS) for an Internet of Things (IoT) device comprises the steps of: receiving a first message including a DNS search list by a device connected to a network on the basis of Internet Protocol Version 6 (IPv6) protocol; generating, by the device, a domain name including model information and an identifier of the device; performing, by the device, a redundancy check for the domain name on the basis of a neighbor discovery (ND) protocol; and, when the domain name is not redundant, registering the domain name and IPv6 address for the device into a DNS server on the basis of a node information (NI) protocol by a domain name-collecting apparatus connected to the network.