A name resolution result control system which controls a name resolution result at a terminal which utilizes an application on one or more edge platforms which are physically deployed in a dispersed manner includes a name resolution unit configured to receive a request for name resolution for the application from the terminal and transmit information of the application on an edge platform which is optimal for the terminal to the terminal as a name resolution result, and a name resolution result control unit configured to execute control for deleting the name resolution result at the terminal by being triggered by a predetermined event.

Some examples relate to controlling network traffic pertaining to a domain name based on a Domain Name System-Internet Protocol address (DNS-IP) mapping, An example includes receiving, in a cloud computing system, a local DNS-IP mapping for a domain name from respective Access Points (APs) in a virtual local area network (VLAN) along with geographical information of respective APs; generating a global DNS-IP mapping database comprising the local DNS-IP mapping for the domain name received from respective APs in the VLAN along with geographical information of respective APs, in the cloud computing system; and determining appropriate APs to distribute the global DNS-IP mapping, based on location information of respective APs.

A network edge computing method includes receiving, by an edge data node, a service request at least processed by network edge computation scheduling; and routing, according to a service port involved in the service request, the service request to a container of the edge data node, to be processed by the container.

Systems and methods are disclosed for enforcing at least one rule associated with a geofence. At least one device is constructed and configured in network communication with a server platform and a database. The server platform defines at least one geofence for a region of interest and specifies at least one rule associated with the at least one geofence, thereby creating a rule-space model for the region of interest. The at least one geofence comprises a multiplicity of geographic designators with each geographic designator assigned with a unique IPv6 address. The at least one device receives at least one notification signal regarding the at least one rule from the at least one server platform and implements the at least one rule when the at least one device is within a predetermined distance from the at least one geofence for the region of interest.

A method is provided that includes accessing, by a server provider server of a service provider, a database storing associations between network addresses and locations. Additionally, the method includes determining a subset of the database corresponding to a first network address, each association included in the subset corresponding to an association between the first network address and a respective location. The method also includes in response to determining that the subset of the database satisfies one or more clustering criteria, calculating a representative location corresponding to the first network address, and storing an association between the first network address and the representative location in a second database.

A computing system can include an interface that receives a URL responsive to activation of an Internet link by a remote device; circuitry that determines a geolocation of the remote device; and circuitry that, based at least in part on the geolocation of the remote device, generates a redirection link.

The present invention is directed to methods and systems for enforcing at least one rule within a geofence. The rule is enforced by a fencing agent on an unmanned aerial vehicle (UAV). The geofence is defined by a plurality of geographic designators, with the plurality of geographic designators each being associated with an Internet Protocol (IP) address, preferably an IPv6 address.

A DNS server comprises: a receiver configured to receive a registration request comprising a domain name, a local address, and a scope, the registration request requests registration of the domain name; a processor coupled to the receiver and configured to execute computer instructions that cause the processor to: assign an address to the domain name based on the local address and the scope, and generate a registration response comprising the address; and a transmitter coupled to the processor and configured to transmit the registration response towards an endpoint. The processor may be further configured to cache a correspondence among the domain name, the address, and the scope.

The present invention is directed to methods and systems for requesting information from a mobile device with a fencing agent. The fencing agent determines a position with a DNS resolver, queries geofences with an IP address, receives an anchor point with an IP address from the DNS resolver. The device with the fencing agent is able to receive multiple anchor points within multiple geofences within an ROI and translate fence points into fence geometries. Geofence information is stored and registered in a database of geofences, and each geofence is associated with a plurality of geographic designators, wherein each of the plurality of geographic designators is associated with an IP address.

Improved methods for retrieval of content from CDNs is provided that includes a rendezvous controller that receives information of an identification of content being requested and an estimated location of a content requesting device. Based on this information, the rendezvous system identifies a server within a CDN from which the requested content may be retrieved. The selected server may be based on a repeatable hash function such that the likelihood that the content being requested is cached at the selected server. Steering requests to a server of the CDN which may have the content cached may reduce the number of servers within the CDN with the same cached content, particularly for the highest requested content. The rendezvous system may then return a corresponding domain name associated with the selected server and that can be subsequently submitted to a DNS for resolution to the IP address of the identified server.