A method for providing topology information, use of a name service server, a device, a computer program, a computer-readable medium and a method for configuring a device to be named within an industrial network, wherein a) the device to be named receives a neighbouring name message from a neighbouring device, b) a self-naming module creates a topological neighbouring domain name based on the neighbouring name message, c) the self-naming module transmits the topological neighbouring domain name to a name service server, d) the self-naming module receives from the name service server a response message, which includes at least one device name of the device to be named belonging to the topological neighbouring domain name, and e) at least one device name from the response message is assigned to the device to be named and this name is stored as the device name by the self-naming module.

Systems and methods are provided for embedding a sender's unique identification in a digital message, for providing additional communication data to a recipient device, and for controlling communications between the sender and multiple recipients and among those recipients depending on the sender's preferences, among other embodiments.

Systems and methods are described for the generation of domain names that may be associated with a particular user device and may be encrypted to obfuscate the domain names of content requested by the user device.

A method includes receiving a request to provision an embedded subscriber identity module (eSIM) profile to an eSIM-enabled device. The request includes a proxy eSIM identifier (EID) prefix. The eSIM profile is associated with a service provider of a mobile communication service a user of the device subscribes to. The method also includes determining whether the proxy EID prefix includes an address of a target discovery server the device is configured to connect to, and when the proxy EID prefix includes the address the method includes extracting the address of the target discovery server from the proxy EID prefix. Using the extracted address of the target discovery server, the method also includes registering a discovery event with the target discovery server indicating that the service provider has reserved the eSIM profile to the proxy EID or an actual EID assigned to the device.

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.

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.

Systems and methods presented herein provide for real time communications between service provider subscribers. In one embodiment, a web server is operable to provide a network-to-network interface (NNI) with a plurality of service providers, to communicate with the service providers through WebRTC links, and to retrieve contact information of subscribers to the service providers over the WebRTC links. The web server also includes a database operable to store the contact information of the subscribers. The web server is also operable to process a connection request from a first of the subscribers to connect with a second of the subscribers, to retrieve the second subscriber's contact information from the database, to push a notification message to a device of the second subscriber using the second subscriber's contact information (e.g., a user identity), and to establish a WebRTC connection between first and second subscribers when the second subscriber accepts the connection.

Embodiments generally relate to network device management. The present technology discloses techniques that can enable an automatic generation of a network topology table for network management. It can use customized identifiers for servers in a server network. It can further enable an automated harvest of network information by utilizing service controllers embedded at different levels of a network.

Exemplary methods at a content centric networking (CCN) gateway located at an autonomous system (AS), wherein the CCN gateway is communicatively coupled to a CCN domain name system (DNS) server, include receiving, on a first face, a first interest message comprising of a first content name identifying a first content being requested by the first interest message. The methods include in response to determining the first content is not located at the AS, determining a first remote AS name that identifies a first remote AS where the first content is located, generating a first 2-level (2L) content name comprising of the first remote AS name and the first content name, forwarding the first interest message comprising of the first 2L content name, and in response to receiving a first content object (CO) message comprising of the first 2L content name and the first content, forwarding the first content.

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.