Patent classifications
H04L2101/30
Network address resolution
A content delivery method including the operations of receiving a uniform resource locator resolution request at an authoritative name server for a domain where the uniform resource resolution request is received based, at least in part, on a host name of the uniform resource resolution request where the host name is uniquely related to a resource associated with the uniform resource resolution request. The method further including the operation of tracking a popularity of the resource based on the host name uniquely related to the resource and providing a location within a network capable of delivering the resource where the provided location is based on the popularity of the resource.
DOMAIN NAME RECOGNITION METHOD AND DOMAIN NAME RECOGNITION DEVICE
The disclosure provides a domain name recognition method and a domain name recognition device. The domain name recognition method includes the following steps. A first string of a first domain name and a second string of a second domain name are obtained. Multiple characters of the first string and the second string are classified into multiple clusters. Multiple vectors corresponding to the clusters are generated, wherein each of the characters corresponds to one of the vectors. A first vector set corresponding to the first string and a second vector set corresponding to the second string are generated. A similarity of the first vector set and the second vector set is calculated.
Service Layer Mobility Management Of Applications
Some services offered by M2M service layers will have contact information that will be used in order to interact with applications. For example, a service layer may need to send notification messages to an application. To do this, the service layer relies on stored contact information to know how to reach the application. If the device hosting the application moves and the application changes its contact information, then the contact information that is in the service layer is stale. As a result, these services will be inefficient, or in some cases, fail altogether. Embodiments described herein provide systems and methods to enable mechanisms to update stale contact information in M2M service layers.
Deployment of a Custom Address to a Remotely Managed Computational Instance
An example embodiment may include a computational instance and a computing device within a remote network management platform. The computing device may be configured to: receive, from a client device of the managed network, a request to redirect, to a second URL, future requests addressed to a first URL; provide, to the client device, instructions to generate a certificate that binds an identity of the entity that operates the managed network to the first URL; receive, from the client device, the certificate; store the certificate and a corresponding cryptographic key; and generate a mapping between the first URL and the second URL. The computational instance may be configured to, in response to receiving a content request referencing the destination, generate a content response containing content from the destination, where any hyperlinks to the second URL in the content are replaced with hyperlinks to the first URL.
Fake web addresses and hyperlinks
A destination address is processed to determine if the destination address is a fake web address or hyperlink. The destination address may be compared with a database of known domain names to see if the domain name is legitimate or illegitimate. The designation address may also be compared to other domain names to see if it is an honest or dishonest transformation of the other domain names. Appropriate action may be taken if the designation address is a dishonest transformation of another domain name.
Apparatus and method for providing information for a wireless network connection using Wi-Fi
An apparatus, method, and system for providing information for a wireless network connection using Wi-Fi. Device information for at least one UPnP device is provided from a plurality of wireless devices including the at least one UPnP device, a device information announcement message including the device information for the at least one UPnP device is generated, and the generated device information announcement message is broadcasted. In this way, information on a UPnP device to which to connect a wireless device is provided in advance, and a user can easily perform a network connection.
Method and apparatus for determining gateway information
Embodiments of the present disclosure provide a method and an apparatus for determining gateway information. A first device obtains first information of user equipment, where the first information of the user equipment is used to indicate an area in which the user equipment subscribes to a service, and the first device determines gateway information corresponding to a first domain name, where the first domain name includes the first information of the user equipment. The first domain name includes the first information of the user equipment, and the first information is used to indicate the area in which the user equipment subscribes to the service. Compared with a method in which a number segment is used to generate a domain name, this reduces a quantity of domain names that need to be configured and maintained, and reduces maintenance costs of an operator.
SPECIFYING LINK LAYER INFORMATION IN A URL
A system of specifying link layer information in a URL is described. In an embodiment, a URL is generated which includes both a link layer network type and information which is used by a resolving device to identify a particular link layer network of the specified type. In various embodiments, the URL includes a link layer network type and a corresponding link layer network name or pairs of link layer network types and corresponding link layer network names. Where the URL comprises more than one link layer network name, the resolving device may determine at runtime which of the named link layer networks to connect to and this decision may be based on criteria or preference information included within the URL.
Cross-chain interactions using a domain name scheme in blockchain systems
Implementations of the present disclosure include identifying, by a relay that is communicatively linked with a first blockchain instance and a second blockchain instance in a unified blockchain network, a blockchain domain name of a first blockchain instance; identifying a blockchain domain name of the second blockchain instance; receiving, from a node of the first blockchain instance, an access request for accessing the second blockchain instance, wherein the access request including the blockchain domain name of the second blockchain instance; identifying a chain identifier of the second blockchain instance based on the blockchain domain name of the second blockchain instance, wherein the chain identifier of the second blockchain instance indicates a blockchain network configuration of the second blockchain instance; and providing access to the second blockchain instance for the first blockchain instance based on the blockchain network configuration indicated by the chain identifier of the second blockchain instance.
Internet of things device hierarchies
In embodiments, Internet of Things (IoT) devices may be organized according to an IoT device hierarchy, which may include parent and/or child associations between resources associated with IoT devices and/or with groupings of IoT devices. IoT devices wishing to support an IoT device hierarchy may utilize an extended IoT device resource model which provides for IoT device hierarchy information and interfaces to be provided by supporting IoT devices. A supporting resource may have one or more parent properties and/or child properties which may identify, respectively, parent or child resources which are associated with the resource. In various embodiments, these parent properties and/or child properties may include uniform resource identifiers (URI). A supporting resource may also identify an interface type for a hierarchical access interface, through which one or more descendant resources may be accessed through a single command. Other embodiments may be descried and/or claimed.