Provided are a proxy end registration method, a proxy end registration system, a computer-readable memory medium, and a terminal. The method includes: receiving, by a management end, heartbeat information sent by a proxy end, and determining whether a management end database contains a UUID in the heartbeat information, wherein the heartbeat information is generated according to a MAC address of the proxy end and timestamp information; if not, determining whether a first hash counter in the heartbeat information is 0, the first hash counter being used for indicating a heartbeat IP transformation state of the heartbeat information; if the first hash counter is not 0, notifying the proxy end of the need to re-register; or if the first hash counter is 0, allowing the proxy end to register.

Systems and methods for resolving names in a data network. A data network includes an information-centric network layer, ICN-layer, with multiple routers, and a name resolution layer with multiple name resolvers. Each router receives an interest packet announcement describing data objects provided by a data producer. Each router determines a first name resolver of the name resolution layer closest to the data producer and sends a name of the provided data object and geo-location of the data producer to the first name resolver. The first name resolver transmits the name of the data object and geo-location of the data producer to other name resolvers. Each router receives an interest packet request describing a data object requested by a data consumer. Each router transmits the interest packet request to a second name resolver spatially closest to the data consumer. Each name resolver provides the geo-location of the requested data object to the data consumer.

Systems and methods for resolving names in a data network. A data network includes an information-centric network layer, ICN-layer, with multiple routers, and a name resolution layer with multiple name resolvers. Each router receives an interest packet announcement describing data objects provided by a data producer. Each router determines a first name resolver of the name resolution layer closest to the data producer and sends a name of the provided data object and geo-location of the data producer to the first name resolver. The first name resolver transmits the name of the data object and geo-location of the data producer to other name resolvers. Each router receives an interest packet request describing a data object requested by a data consumer. Each router transmits the interest packet request to a second name resolver spatially closest to the data consumer. Each name resolver provides the geo-location of the requested data object to the data consumer.

Methods are taught for creating training data for a learning algorithm, training the learning algorithm with the training data and using the trained learning algorithm to suggest domain names to users. A domain name registrar may store activities of a user on a registrar website. Preferably, domain name searches, selected suggested domain names and domain names registered to the user are stored as the training data in a training database. The training data may be stored so that earlier activities act as inputs to the learning algorithm while later activities are the expected outputs of the learning algorithm. Once trained, the learning algorithm may receive activities of other users and suggest domain names to the other users based on their activities.

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 a confirm domain event message or a deny domain event message.

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. Disclosed is a method for binding or unbinding a functional alias with at least one mission critical services (MCX) group in an MCX network, including creating or updating, by an MCX server, an association of a functional alias with the at least one MCX group when the SIP message request is received to create binding of the functional alias with at least one MCX group, or disassociating by the MCX server an association of the functional alias with the at least one MCX group when the SIP message request is received to remove the binding of the functional alias with the at least one MCX group, and sending, by the MCX server, an SIP message response to MCX client device confirming whether the creation or removal of binding of the functional alias with the at least one MCX group is successful or unsuccessful.

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. Disclosed is a method for binding or unbinding a functional alias with at least one mission critical services (MCX) group in an MCX network, including creating or updating, by an MCX server, an association of a functional alias with the at least one MCX group when the SIP message request is received to create binding of the functional alias with at least one MCX group, or disassociating by the MCX server an association of the functional alias with the at least one MCX group when the SIP message request is received to remove the binding of the functional alias with the at least one MCX group, and sending, by the MCX server, an SIP message response to MCX client device confirming whether the creation or removal of binding of the functional alias with the at least one MCX group is successful or unsuccessful.

Embodiments of this application relate to the communications field, and describe an alias management method and device. One example method includes the following operations: a functional alias management entity receives a management request message sent by a first client, where the management request message includes an identity of a user and information about an alias requested to be managed; and the functional alias management entity sends a management response message to the first client when the user has an alias management right, where the management response message includes the identity of the user, and information about an alias that is successfully managed.

Embodiments of this application relate to the communications field, and describe an alias management method and device. One example method includes the following operations: a functional alias management entity receives a management request message sent by a first client, where the management request message includes an identity of a user and information about an alias requested to be managed; and the functional alias management entity sends a management response message to the first client when the user has an alias management right, where the management response message includes the identity of the user, and information about an alias that is successfully managed.

Aspects described herein include a method for use with a software-defined network controller, as well as an associated computer program product and system. The method comprises assigning a segment identifier to an endpoint node within a destination domain of a plurality of domains. Adjacent domains of the plurality of domains are connected via a respective set of two or more domain border routers. The method further comprises assigning a respective segment identifier to each domain. Each domain border router advertises the segment identifiers of the respective two adjacent domains. The method further comprises, responsive to a request from a headend node within a source domain of the plurality of domains, computing a path from the headend node to the endpoint node. The path includes (i) the segment identifiers of any domains between the headend node and the endpoint node, and (ii) the segment identifier of the endpoint node.