US20140304370A1 - Providing mobile versions of web resources - Google Patents
Providing mobile versions of web resources Download PDFInfo
- Publication number
- US20140304370A1 US20140304370A1 US13/640,882 US201113640882A US2014304370A1 US 20140304370 A1 US20140304370 A1 US 20140304370A1 US 201113640882 A US201113640882 A US 201113640882A US 2014304370 A1 US2014304370 A1 US 2014304370A1
- Authority
- US
- United States
- Prior art keywords
- mobile communication
- communication device
- internet domain
- web
- domain name
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- H04L67/32—
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/957—Browsing optimisation, e.g. caching or content distillation
- G06F16/9577—Optimising the visualization of content, e.g. distillation of HTML documents
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/957—Browsing optimisation, e.g. caching or content distillation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/04—Protocols specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
Definitions
- the present invention relates to the identification of web resources suitable for use by mobile communication devices.
- the invention has application in ensuring that the most appropriate web resources are provided to mobile communication devices.
- Web resources are intended for use by desktop and laptop personal computers (PCs). This means that they are often unsuitable for use by mobile communication devices.
- Web resources typically web sites and web pages, may include script, graphics, images, animations, video data, audio data, layouts etc. that are not supported by a mobile communication device.
- a web site may include objects encoded using Java® or Adobe® Flash script, but a mobile communication device may not have the correct software to use such objects.
- an image on a web site may be too large to be displayed on a mobile communication device.
- the mobile communication device may send a request for a web resource, which request includes an internet domain name, e.g. “bobspizzashop.com”.
- the mobile network retrieves the web resource from the web server using the internet domain name (or, more specifically, an Internet Protocol (IP) address for the server at which the web resource is located, which IP address can be retrieved from the Domain Name System (DNS) of the internet using the internet domain name).
- IP Internet Protocol
- DNS Domain Name System
- the transcoding involves identifying the type of mobile communication device that made the request and adapting the web resource to be suitable for that device. For example, if the web resource is encoded using script that is not supported by the type of mobile communication device, the web resource may be converted to script that is supported by the type of mobile communication device. Similarly, an image included in the web resource may be resized to suit the limitations of the display of the mobile communication device.
- Transcoding of web resources in this way faces some difficulties.
- the results can be variable and imperfect.
- the transcoded web resource may vary according to the mobile network operator which carried out the transcoding.
- the owner of the initial web resource therefore has little control over the user experience when accessing the web resource via a mobile communication device. This is clearly undesirable from the perspective of the owner of the web resource.
- web resources are specifically encoded for use by mobile communication devices.
- web resources specifically encoded for use by mobile communication devices are based on web resources intended for use by PCs.
- an organisation may have two web sites, one for use by PCs and the other specifically encoded for use by mobile communication devices. This allows the owner of the web resources to control the user experience even when the web resources are accessed on a mobile communication device.
- a method for providing a mobile specific web resource to a mobile communication device comprising:
- the mobile communication device receiving a request from the mobile communication device, the request including a first internet domain name comprising a top level domain and one or more further elements;
- an apparatus for providing a mobile specific web resource to a mobile communication device comprising a server for:
- the mobile communication device receiving a request from the mobile communication device, the request including a first internet domain name comprising a top level domain and one or more further elements;
- the first and second aspects of the present invention can assist in the identification and subsequent delivery of web resources that are appropriate for a mobile communication device.
- An initial request may be made using a first internet domain name which contains a top level domain. This top level domain may be removed and further internet domain names containing at least some of the remaining elements of the first internet domain name may be generated. Web resources identified by these generated internet domain names may be retrieved where possible and then analysed to determine which of these is most appropriate for the mobile communication device. This allows web resources that are appropriate for mobile communication devices to be identified and delivered to the mobile communication device.
- a web resource owner may have established a web page designed for PCs hosted at an IP address associated with internet domain name “bobspizzashop.com” and a version of this web page specifically encoded for mobile communication devices hosted at an IP address associated with internet domain name “mobile.bobspizzashop.com”.
- a mobile communication device may send a request including a first internet domain name “bobspizzashop.com.mobi”.
- bobspizzashop.com By generating further internet domain names that contain the string “bobspizzashop”, both the internet domain name “bobspizzashop.com” and the internet domain name “mobile.bobspizzashop.com” may be identified, and the web pages hosted the IP addresses associated with these addresses may be retrieved. It may then be determined that the web page hosted at the IP address associated with the internet domain name “mobile.bobspizzashop.com” is the most appropriate for the mobile communication device, and this web page may be delivered to the mobile communication device.
- Preferred embodiments of the present invention allow the mobile communication device to request internet domain names having a particular top level domain, such as “.mobi”, in the knowledge that this will cause the server to determine the most appropriate web resource for the mobile communication device.
- a particular top level domain such as “.mobi”
- the first internet domain name and the one or more further internet domain names have different top level domains but the same main distinctive label.
- the main distinctive label is “bobspizzashop”. This is relatively memorable for a user, who does not need to remember other aspects of the internet domain name at which the web resources designed for the mobile communication device are hosted in order to access them.
- the first internet domain name is mapped to the IP address of the most appropriate web resource.
- the first internet domain name may be stored together with an IP address of the most appropriate web resource. This allows the determined web resource to be delivered when subsequent requests are received including the first internet domain name without the requirement to repeat the steps of generating one or more further internet domain names comprising the one or more further elements; retrieving one or more web resources identified by the one or more further internet domain names; and analysing the one or more web resources to determine which is most appropriate for delivery to the mobile communication device.
- the web resources hosted at internet domain name “mobile.bobspizzashop.com” are imperfectly designed for the specific mobile communication device that has made the request.
- the web site owner may have only provided a web site for PCs, such as that hosted at internet domain name “bobspizzashop.com”.
- the server may be a transcoder. In such circumstances, it is preferable that the most appropriate web resource is transcoded before being delivered to the mobile communication device.
- the transcoded web resource is stored. This allows the transcoded web resources to be delivered at a later date without the requirement for transcoding step to occur again.
- the transcoded web page is stored for a predetermined period of time. As such, changes in the most appropriate web resource are reflected in the transcoded web resource delivered to the mobile communication device after this period expires.
- a method of providing a mobile specific web resource to a mobile communication device comprising
- a request from a mobile communication device including a first internet domain name comprising a top level domain and one or more further elements;
- an apparatus for providing a mobile specific web resource to a mobile communication device comprising a server for:
- a request from a mobile communication device including a first internet domain name comprising a top level domain and one or more further elements;
- a request from a mobile communication device can use a first internet domain name made up of a truncated internet domain name and a top level domain, wherein the truncated internet domain name identifies a known web resource.
- the truncated internet domain name may be generated by removing the top level domain, the web resource may then be retrieved and analysed, and the web resource may then be transcoded in dependence on this analysis. That is, the web resource can be transcoded after an assessment has been made of whether this is necessary.
- the medium may be a physical storage medium such as a Read Only Memory (ROM) chip. Alternatively, it may be a disk such as a Digital Video Disk (DVD-ROM) or Compact Disk (CD-ROM). It could also be a signal such as an electronic signal over wires, an optical signal or a radio signal such as to a satellite or the like.
- ROM Read Only Memory
- DVD-ROM Digital Video Disk
- CD-ROM Compact Disk
- the invention also extends to a processor running the software or code, e.g. a computer configured to carry out the method described above.
- FIG. 1 is a schematic diagram of a transcoding system
- FIG. 2 is a sequence diagram illustrating use of the transcoding system.
- a transcoding system 1 comprises a mobile communication device 2 , such as a mobile telephone, smart phone, Personal Digital Assistant (PDA) or such like, that retrieves a web resource using a mobile communication network 3 and the internet 4 via a transcoder 5 .
- the mobile communication network 3 is typically a terrestrial or satellite mobile communication network.
- the mobile communication device 2 uses a Wireless Local Area Network (WLAN) or such like to connect to the internet 4 instead of the mobile communication network 3 .
- WLAN Wireless Local Area Network
- the mode of connection to the internet 4 is inessential, but the mobile communication device 2 itself is usually characterised by limitations in its ability to use web resources intended for use by desktop and laptop personal computers (PCs).
- Web resources include web sites, web pages, feeds, data or video files and so on.
- a web page intended for use by PCs is stored at a web server 6 .
- the web page is part of a web site under the control of a web site owner 7 .
- the web server 6 is also under the control of the web site owner 7 , but in other examples, the web server 6 may be controlled by another party, such as an Internet Service Provider (ISP), on behalf of the web site owner 7 .
- ISP Internet Service Provider
- a registrar 8 is responsible for registering new internet domain names with an internet domain name registry 9 , which for simplicity is considered to be part of the internet 4 in FIG. 1 .
- the registry 9 is responsible for the generic top level domain (TLD) “.mobi” and the registrar 8 handles requests by registrants to register internet domain names with the “.mobi” TLD.
- TLD top level domain
- the registrar may offer various services to the web site owner 7 in exchange for the registration at the registry 9 of an internet domain name having the TLD “.mobi”. However, for the purposes of illustrating the present invention, it is not necessary that the web site owner 7 and the registrar 8 enter into such an arrangement.
- the registrar 8 generates a variety of new internet domain names having “.mobi” as the TLD and another element as the second level domain. These other elements used as second level domains are typically those known for use as top level domains for existing web resources. For example, the registrar 8 may generate “com.mobi”, where “corn” is the second level domain and “.mobi” is the top level domain. Other domain names that the registrar 8 may generate can include “uk.mobi”, “org.mobi”, “info.mobi” and so on. In general the registrar generates domain names that use existing generic top level domains (gTLDs), such as “.com”, “.info”, “.co” and so on, as the second level domain and “.mobi” as the top level domain.
- gTLDs generic top level domains
- the registrar 8 then registers these domain names with the registry 9 . Specifically, the registrar 8 then sends requests to the registry 9 to create resource records for the new internet domain names.
- the registrar 8 sends ⁇ create> requests using Extensible Provisioning Protocol (EPP), as described in the Network Working Group Request for Comments (RFC) 4930 that can be found at http://tools.ietf.org/html/rfc4930.
- EPP ⁇ create> requests map the new internet domain names, such as “com.mobi”, to the Internet Protocol (IP) address of the transcoder 5 .
- IP Internet Protocol
- the new internet domain names are mapped to the IP address of the transcoder 5 in the DNS 10 of the internet in such a manner that the addition of lower level domains to the new internet domain names does not change this mapping.
- the new internet domain name is “com.mobi”
- any internet domain name of the form “*.com.mobi”, where “*” is a wildcard which may represent any allowable internet domain name element is mapped to the transcoder 5 .
- new internet domain names which use the majority of or even all existing gTLDs as a second level domain in combination with “.mobi” as a TLD are registered. Accordingly, when browsing the internet, a user may add “.mobi” to the end of an existing internet domain name in order to access the transcoder 5 and make use of the invention as described below.
- a web site owner 7 who has established a web page for PCs hosted at an IP address associated with internet domain name “bobspizzashop.com” and has also established a web page specifically encoded for mobile communication devices (a “mobile web page”) hosted at an IP address associated with internet domain name “mobile.bobspizzashop.com”.
- a user wishing to access the web resources belonging to the web site owner 7 on a mobile communication device 2 may be unaware of the existence of the mobile web page. Even if aware of the existence of the mobile web page, the user may not know the internet domain name of the mobile web page and may therefore be unable to access it. However, the user is aware of the internet domain name associated with the IP address at which the web page for PCs is hosted (i.e. “bospizzashop.com”).
- the user may discover the existence and location of a mobile web page by adding the “.mobi” top level domain to the known internet domain when browsing. That is, the user of the mobile communication device 2 may browse to “bobspizzashop.com.mobi”. Moreover, if no mobile web page exists, the user of the mobile communication device 2 may use the same technique, i.e. browsing to “bobspizzashop.com.mobi” to access a transcoded version of the web page for PCs at “bobspizzashop.com”. This transcoded version of the web page for PCs is adapted so as to be suitable for the mobile communication device 2 .
- the mobile communication device 2 browses to a web page at an internet domain name having the “.mobi” top level domain, e.g. “bobspizzashop.com.mobi”. Assuming the mobile communication device 2 does not know the IP address associated with the internet domain name “bobspizzashop.com.mobi”, this initiates a lookup query to the DNS 10 , at step S 2 .
- the DNS 10 provides the IP address of the transcoder 5 to the mobile communication device 2 at step S 3 . Using this IP address, the mobile communication device 2 sends a HyperText Transfer Protocol (HTTP) request to the transcoder 5 for the web page, e.g. using Uniform Resource Locator (URL) “http://bobspizzashop.com.mobi/webpage”, at step S 4 .
- HTTP HyperText Transfer Protocol
- the transcoder then 5 generates further internet domain names using the internet domain name “bobspizzashop.com.mobi”.
- the transcoder 5 generates a truncated internet domain name by removing the top level domain name, i.e. “.mobi”, thereby leaving the internet domain name associated with the PC web page, i.e. “bobspizzashop.com”.
- the transcoder may additionally generate a number of potential internet domain names based on the truncated internet domain name. For example, the transcoder may generate potential internet domain names “m.bobspizzashop.com” and “mobile.bobspizzashop.com”.
- the potential internet domain names typically share the main distinctive element (in this case, “bobspizzashop”) with the truncated internet domain name and the internet domain name used in the request sent by the mobile communication device 2 , while they may add or remove other elements to or from the truncated internet domain name.
- bobspizzashop main distinctive element
- the transcoder 5 initiates lookup queries to the DNS 10 for the further internet domain names it has generated, i.e. the truncated internet domain name and the potential internet domain names. For example, the transcoder 5 may initiate lookup queries for “bobspizzashop.com”, “m.bobspizzashop.com” and “mobile.bobspizzashop.com”.
- the DNS 10 provides the results of the lookup queries to the transcoder 5 . These will include the IP address associated with the PC web page at the truncated internet domain name “bobspizzashop.com” as well any IP addresses that are associated with the potential internet domain names. It is likely that not all of the prospective internet domain names used in the lookup queries will have a validly assigned IP address, in which case the DNS 10 returns either no result or a conventional error message for these internet domain names.
- the transcoder 5 uses the IP addresses received from the DNS 10 to send HyperText Transfer Protocol (HTTP) requests, at step S 7 , to the web server 6 for web pages using Uniform Resource Locator (URLs) based on the truncated internet domain name and the potential internet domain names, such as “http://bobspizzashop.com/webpage”, “http://mobile.bobspizzashop.com/webpage”, “http://m.bobspizzashop.com/webpage”, “http://bobspizzashop.com/mobile” and so on.
- URLs Uniform Resource Locator
- FIG. 2 a single web server 6 is illustrated in FIG. 2 , the skilled person will appreciate that different web pages may be hosted by different web servers.
- the IP addresses received by the transcoder 5 allow it to direct its request to the correct web server(s).
- the web server 6 then returns the requested web pages to the transcoder 5 , at step S 8 .
- These will include at least the PC web page associated with internet domain name “bobspizzashop.com” and may include other web pages which the transcoder 5 has located, which may or may not be optimised for use by mobile communication device 2 .
- the transcoder 5 analyses the returned web pages to determine which is the most appropriate for delivery to the mobile communication device 2 .
- the web page identified by internet domain name “bobspizzashop.com” is designed for viewing on a PC
- the web page identified by internet domain name “mobile.bobspizzashop.com” is designed for viewing on the mobile communication device 2 . It is therefore preferable to deliver the web page from “mobile.bobspizzashop.com” to the mobile communication device 2 , instead of that from “bobspizzashop.com”.
- a first mobile web page designed for mobile communication devices 2 may be stored at an address associated with internet domain name “mobile.bobspizzashop.com” and a second web page designed for mobile communication devices 2 may be stored at an address associated with internet domain name “m.bobspizzashop.com”.
- the transcoder 5 will determine which of the web pages designed for mobile communication devices 2 is most appropriate for the particular mobile communication device that made the original request.
- the transcoder 5 transcodes the determined web page if required.
- the web page determined to be most appropriate for the mobile communication device is then returned to the mobile communication device, at step S 10 .
- the web page returned to the mobile communication device may or may not have been transcoded by the transcoder 5 .
- the transcoder 5 has now established which internet domain name associated with “bobspizzashop.com.mobi” provides the most appropriate web page for the mobile communication device 2 .
- the transcoder 5 stores this information. That is, the transcoder 5 maps the internet domain name “bospizzashop.com.mobi” to the address of the most appropriate web page.
- the transcoder 5 may also store the most appropriate web page itself.
- the transcoded version of the web page may also be stored.
- future requests for “bobspizzashop.com.mobi” are dealt with more efficiently without the requirement to identify IP addresses by trying a variety of lookup queries at the DNS 10 . This is described below with reference to steps S 12 to S 15 .
- a subsequent request for “bobspizzashop.com.mobi” is made.
- this subsequent request is indicated coming from the mobile communication device 2 which made the initial request at step S 1 , although in practice it could originate with a different mobile communication device.
- the transcoder 5 recognises the internet domain name “bobspizzashop.com.mobi” as this information has been saved by the transcoder 5 at step S 11 .
- the transcoder 5 has also saved the URL of the web page which was determined to be most appropriate for delivery to the mobile communication device 2 . Accordingly, the transcoder 5 may use this information to request the most appropriate web page from the web server 6 , at step S 13 .
- the web server 6 returns the web page to the transcoder 5 , at step S 14 , and this is subsequently forwarded to the mobile communication device, at step S 15 .
- transcoder 5 If the web page has been previously transcoded by transcoder 5 , then there is no need for the transcoder 5 to obtain the web page from the web server 6 again (steps S 13 and S 14 ). In these circumstances, the transcoded web page is simply returned to the mobile communication device 2 from the transcoder 5 .
- transcoded web resources may be stored for a limited period to ensure that content delivered to the mobile communication device 2 reflects the current state of the web page itself.
- transcoded web resources may be stored for a week, a day, or any other appropriate time period.
- the appropriate time period may vary according to the type of content reflected by the web page. For example, a web page relating to breaking news may be expected to be updated regularly, meaning that it would only be appropriate to store a transcoded version of this web page for a short period, if at all.
Abstract
Description
- The present invention relates to the identification of web resources suitable for use by mobile communication devices. In particular, but not exclusively, the invention has application in ensuring that the most appropriate web resources are provided to mobile communication devices.
- Most web resources are intended for use by desktop and laptop personal computers (PCs). This means that they are often unsuitable for use by mobile communication devices. Web resources, typically web sites and web pages, may include script, graphics, images, animations, video data, audio data, layouts etc. that are not supported by a mobile communication device. For example, a web site may include objects encoded using Java® or Adobe® Flash script, but a mobile communication device may not have the correct software to use such objects. Similarly, an image on a web site may be too large to be displayed on a mobile communication device.
- It is known to convert web resources intended for use by PCs to be suitable for use by mobile communication devices. This conversion is known as transcoding and is often carried out by mobile network operators. When the user of a mobile communication device seeks access to a given web resource via the mobile communication network, instead of the mobile communication device being provided with the web resource itself, it is provided with a transcoded version of the web resource.
- In more detail, the mobile communication device may send a request for a web resource, which request includes an internet domain name, e.g. “bobspizzashop.com”. The mobile network retrieves the web resource from the web server using the internet domain name (or, more specifically, an Internet Protocol (IP) address for the server at which the web resource is located, which IP address can be retrieved from the Domain Name System (DNS) of the internet using the internet domain name). However, instead of delivering the web resource straight to the mobile communication device, the operator of the mobile network first transcodes the web resource.
- Typically, the transcoding involves identifying the type of mobile communication device that made the request and adapting the web resource to be suitable for that device. For example, if the web resource is encoded using script that is not supported by the type of mobile communication device, the web resource may be converted to script that is supported by the type of mobile communication device. Similarly, an image included in the web resource may be resized to suit the limitations of the display of the mobile communication device.
- Transcoding of web resources in this way faces some difficulties. In particular, as the initial web resources are designed without the subsequent transcoding process in mind, the results can be variable and imperfect. For example, the transcoded web resource may vary according to the mobile network operator which carried out the transcoding. The owner of the initial web resource therefore has little control over the user experience when accessing the web resource via a mobile communication device. This is clearly undesirable from the perspective of the owner of the web resource.
- In view of the above, many web resources are specifically encoded for use by mobile communication devices. Usually, web resources specifically encoded for use by mobile communication devices are based on web resources intended for use by PCs. For example, an organisation may have two web sites, one for use by PCs and the other specifically encoded for use by mobile communication devices. This allows the owner of the web resources to control the user experience even when the web resources are accessed on a mobile communication device.
- However, the provision of separate web resources that are specifically encoded for use by mobile communication devices is only effective if the users of mobile communication devices are able to access them. For example, where a company has two web sites, one for use by PCs and the other specifically encoded for use by mobile communication devices, the mobile communication device must access the correct web site if it is to make use of the web resources that have been specifically encoded for it. However, there is currently no predictable way in which a user may be alerted as to the presence or otherwise and location of web resources specifically encoded for mobile communication devices.
- The complexity of the above difficulties is increased by the variety of capabilities of different mobile communication devices. The owner of a web resource may wish to provide separate versions of that resource specifically encoded for different types of mobile communication device which will access the resource. However, providing a large variety of web resources makes even more difficult for users to locate the appropriate resource for their mobile communication device. As a result, owners of web resources are typically hesitant to make the necessary investment to optimise those web resources for each type of mobile communication device. This leads to a limited user experience.
- According to a first aspect of the present invention, there is provided a method for providing a mobile specific web resource to a mobile communication device, the method comprising:
- receiving a request from the mobile communication device, the request including a first internet domain name comprising a top level domain and one or more further elements;
- generating further internet domain names comprising the one or more further elements;
- retrieving web resources identified by the one or more further internet domain names;
- analysing the web resources to determine which is most appropriate for delivery to a mobile communication device; and
- delivering the most appropriate web resource to the mobile communication device.
- According to a second aspect of the present invention, there is provided an apparatus for providing a mobile specific web resource to a mobile communication device, the apparatus comprising a server for:
- receiving a request from the mobile communication device, the request including a first internet domain name comprising a top level domain and one or more further elements;
- generating further internet domain names comprising the one or more further elements;
- retrieving web resources identified by the one or more further internet domain names;
- analysing the web resources to determine which is most appropriate for delivery to a mobile communication device; and
- delivering the most appropriate web resource to the mobile communication device.
- So, the first and second aspects of the present invention can assist in the identification and subsequent delivery of web resources that are appropriate for a mobile communication device. An initial request may be made using a first internet domain name which contains a top level domain. This top level domain may be removed and further internet domain names containing at least some of the remaining elements of the first internet domain name may be generated. Web resources identified by these generated internet domain names may be retrieved where possible and then analysed to determine which of these is most appropriate for the mobile communication device. This allows web resources that are appropriate for mobile communication devices to be identified and delivered to the mobile communication device.
- For example, a web resource owner may have established a web page designed for PCs hosted at an IP address associated with internet domain name “bobspizzashop.com” and a version of this web page specifically encoded for mobile communication devices hosted at an IP address associated with internet domain name “mobile.bobspizzashop.com”. In this example, a mobile communication device may send a request including a first internet domain name “bobspizzashop.com.mobi”. By generating further internet domain names that contain the string “bobspizzashop”, both the internet domain name “bobspizzashop.com” and the internet domain name “mobile.bobspizzashop.com” may be identified, and the web pages hosted the IP addresses associated with these addresses may be retrieved. It may then be determined that the web page hosted at the IP address associated with the internet domain name “mobile.bobspizzashop.com” is the most appropriate for the mobile communication device, and this web page may be delivered to the mobile communication device.
- Preferred embodiments of the present invention allow the mobile communication device to request internet domain names having a particular top level domain, such as “.mobi”, in the knowledge that this will cause the server to determine the most appropriate web resource for the mobile communication device. For example, in preferred embodiments a particular top level domain, such as “.mobi”, may be suffixed to existing internet domain names in order to cause the server to determine the most appropriate web resource for the mobile communication device.
- Preferably, the first internet domain name and the one or more further internet domain names have different top level domains but the same main distinctive label. For instance, in the example given above, the main distinctive label is “bobspizzashop”. This is relatively memorable for a user, who does not need to remember other aspects of the internet domain name at which the web resources designed for the mobile communication device are hosted in order to access them.
- Preferably, the first internet domain name is mapped to the IP address of the most appropriate web resource. For example, the first internet domain name may be stored together with an IP address of the most appropriate web resource. This allows the determined web resource to be delivered when subsequent requests are received including the first internet domain name without the requirement to repeat the steps of generating one or more further internet domain names comprising the one or more further elements; retrieving one or more web resources identified by the one or more further internet domain names; and analysing the one or more web resources to determine which is most appropriate for delivery to the mobile communication device.
- Referring again to the example given above, it may be that the web resources hosted at internet domain name “mobile.bobspizzashop.com” are imperfectly designed for the specific mobile communication device that has made the request. Alternatively, the web site owner may have only provided a web site for PCs, such as that hosted at internet domain name “bobspizzashop.com”. For this reason, the server may be a transcoder. In such circumstances, it is preferable that the most appropriate web resource is transcoded before being delivered to the mobile communication device.
- Preferably, the transcoded web resource is stored. This allows the transcoded web resources to be delivered at a later date without the requirement for transcoding step to occur again. In preferred examples, the transcoded web page is stored for a predetermined period of time. As such, changes in the most appropriate web resource are reflected in the transcoded web resource delivered to the mobile communication device after this period expires.
- According to a third aspect of the present invention, there is provided a method of providing a mobile specific web resource to a mobile communication device, the method comprising
- receiving a request from a mobile communication device, the request including a first internet domain name comprising a top level domain and one or more further elements;
- generating a truncated internet domain name by removing the top level domain from the first internet domain name;
- retrieving a web resource identified by the truncated internet domain name;
- analysing the retrieved web resource to determine whether it is appropriate for the mobile communication device;
- transcoding the web resource if it is not appropriate for the mobile communication device; and
- delivering the web resource to the mobile communication device.
- According to a fourth aspect of the present invention, there is provided an apparatus for providing a mobile specific web resource to a mobile communication device, the apparatus comprising a server for:
- receiving a request from a mobile communication device, the request including a first internet domain name comprising a top level domain and one or more further elements;
- generating a truncated internet domain name by removing the top level domain from the first internet domain name;
- retrieving a web resource identified by the truncated internet domain name;
- analysing the retrieved web resource to determine whether it is appropriate for the mobile communication device;
- transcoding the web resource if it is not appropriate for the mobile communication device; and
- delivering the web resource to the mobile communication device.
- So, the third and fourth aspects of the present invention can also assist in the identification and subsequent delivery of web resources that are appropriate for a mobile communication device. In particular, a request from a mobile communication device can use a first internet domain name made up of a truncated internet domain name and a top level domain, wherein the truncated internet domain name identifies a known web resource. When the request is received, the truncated internet domain name may be generated by removing the top level domain, the web resource may then be retrieved and analysed, and the web resource may then be transcoded in dependence on this analysis. That is, the web resource can be transcoded after an assessment has been made of whether this is necessary.
- Use of the words “apparatus”, “transcoder” and so on are intended to be general rather than specific. Whilst these features of the invention may be implemented using an individual component, such as a computer or a central processing unit (CPU), they can equally well be implemented using other suitable components or a combination of components. For example, the invention could be implemented using a hard-wired circuit or circuits, e.g. an integrated circuit, or using embedded software. It can also be appreciated that the invention can be implemented, at least in part, using computer program code. According to another aspect of the present invention, there is therefore provided computer software or computer program code adapted to carry out the method described above when processed by a computer processing means. The computer software or computer program code can be carried by computer readable medium. The medium may be a physical storage medium such as a Read Only Memory (ROM) chip. Alternatively, it may be a disk such as a Digital Video Disk (DVD-ROM) or Compact Disk (CD-ROM). It could also be a signal such as an electronic signal over wires, an optical signal or a radio signal such as to a satellite or the like. The invention also extends to a processor running the software or code, e.g. a computer configured to carry out the method described above.
- A preferred embodiment of the invention is described below, by way of example only, with reference to the accompanying drawings.
-
FIG. 1 is a schematic diagram of a transcoding system; and -
FIG. 2 is a sequence diagram illustrating use of the transcoding system. - Referring to
FIG. 1 , atranscoding system 1 comprises amobile communication device 2, such as a mobile telephone, smart phone, Personal Digital Assistant (PDA) or such like, that retrieves a web resource using amobile communication network 3 and theinternet 4 via atranscoder 5. Themobile communication network 3 is typically a terrestrial or satellite mobile communication network. In other examples, themobile communication device 2 uses a Wireless Local Area Network (WLAN) or such like to connect to theinternet 4 instead of themobile communication network 3. The mode of connection to theinternet 4 is inessential, but themobile communication device 2 itself is usually characterised by limitations in its ability to use web resources intended for use by desktop and laptop personal computers (PCs). - Web resources include web sites, web pages, feeds, data or video files and so on. In the illustrated example, a web page intended for use by PCs is stored at a
web server 6. The web page is part of a web site under the control of aweb site owner 7. In this example, theweb server 6 is also under the control of theweb site owner 7, but in other examples, theweb server 6 may be controlled by another party, such as an Internet Service Provider (ISP), on behalf of theweb site owner 7. - A
registrar 8 is responsible for registering new internet domain names with an internetdomain name registry 9, which for simplicity is considered to be part of theinternet 4 inFIG. 1 . In this example, theregistry 9 is responsible for the generic top level domain (TLD) “.mobi” and theregistrar 8 handles requests by registrants to register internet domain names with the “.mobi” TLD. - The registrar may offer various services to the
web site owner 7 in exchange for the registration at theregistry 9 of an internet domain name having the TLD “.mobi”. However, for the purposes of illustrating the present invention, it is not necessary that theweb site owner 7 and theregistrar 8 enter into such an arrangement. - Instead, the
registrar 8 generates a variety of new internet domain names having “.mobi” as the TLD and another element as the second level domain. These other elements used as second level domains are typically those known for use as top level domains for existing web resources. For example, theregistrar 8 may generate “com.mobi”, where “corn” is the second level domain and “.mobi” is the top level domain. Other domain names that theregistrar 8 may generate can include “uk.mobi”, “org.mobi”, “info.mobi” and so on. In general the registrar generates domain names that use existing generic top level domains (gTLDs), such as “.com”, “.info”, “.co” and so on, as the second level domain and “.mobi” as the top level domain. - The
registrar 8 then registers these domain names with theregistry 9. Specifically, theregistrar 8 then sends requests to theregistry 9 to create resource records for the new internet domain names. In this example, theregistrar 8 sends <create> requests using Extensible Provisioning Protocol (EPP), as described in the Network Working Group Request for Comments (RFC) 4930 that can be found at http://tools.ietf.org/html/rfc4930. The EPP <create> requests map the new internet domain names, such as “com.mobi”, to the Internet Protocol (IP) address of thetranscoder 5. This mapping of the new internet domain names to the IP address of thetranscoder 5 propagates throughout the domain name system (DNS) 10 of the internet through the exchange of zone files as explained at www.dns.net. - The new internet domain names are mapped to the IP address of the
transcoder 5 in theDNS 10 of the internet in such a manner that the addition of lower level domains to the new internet domain names does not change this mapping. For example, where the new internet domain name is “com.mobi”, any internet domain name of the form “*.com.mobi”, where “*” is a wildcard which may represent any allowable internet domain name element, is mapped to thetranscoder 5. - Preferably, new internet domain names which use the majority of or even all existing gTLDs as a second level domain in combination with “.mobi” as a TLD are registered. Accordingly, when browsing the internet, a user may add “.mobi” to the end of an existing internet domain name in order to access the
transcoder 5 and make use of the invention as described below. - For example, consider a
web site owner 7 who has established a web page for PCs hosted at an IP address associated with internet domain name “bobspizzashop.com” and has also established a web page specifically encoded for mobile communication devices (a “mobile web page”) hosted at an IP address associated with internet domain name “mobile.bobspizzashop.com”. A user wishing to access the web resources belonging to theweb site owner 7 on amobile communication device 2 may be unaware of the existence of the mobile web page. Even if aware of the existence of the mobile web page, the user may not know the internet domain name of the mobile web page and may therefore be unable to access it. However, the user is aware of the internet domain name associated with the IP address at which the web page for PCs is hosted (i.e. “bospizzashop.com”). - In the preferred embodiment of the present invention, the user may discover the existence and location of a mobile web page by adding the “.mobi” top level domain to the known internet domain when browsing. That is, the user of the
mobile communication device 2 may browse to “bobspizzashop.com.mobi”. Moreover, if no mobile web page exists, the user of themobile communication device 2 may use the same technique, i.e. browsing to “bobspizzashop.com.mobi” to access a transcoded version of the web page for PCs at “bobspizzashop.com”. This transcoded version of the web page for PCs is adapted so as to be suitable for themobile communication device 2. - Referring to
FIG. 2 , at step S1 themobile communication device 2 browses to a web page at an internet domain name having the “.mobi” top level domain, e.g. “bobspizzashop.com.mobi”. Assuming themobile communication device 2 does not know the IP address associated with the internet domain name “bobspizzashop.com.mobi”, this initiates a lookup query to theDNS 10, at step S2. TheDNS 10 provides the IP address of thetranscoder 5 to themobile communication device 2 at step S3. Using this IP address, themobile communication device 2 sends a HyperText Transfer Protocol (HTTP) request to thetranscoder 5 for the web page, e.g. using Uniform Resource Locator (URL) “http://bobspizzashop.com.mobi/webpage”, at step S4. - The transcoder then 5 generates further internet domain names using the internet domain name “bobspizzashop.com.mobi”. In particular, the
transcoder 5 generates a truncated internet domain name by removing the top level domain name, i.e. “.mobi”, thereby leaving the internet domain name associated with the PC web page, i.e. “bobspizzashop.com”. The transcoder may additionally generate a number of potential internet domain names based on the truncated internet domain name. For example, the transcoder may generate potential internet domain names “m.bobspizzashop.com” and “mobile.bobspizzashop.com”. The potential internet domain names typically share the main distinctive element (in this case, “bobspizzashop”) with the truncated internet domain name and the internet domain name used in the request sent by themobile communication device 2, while they may add or remove other elements to or from the truncated internet domain name. - At step S5, the
transcoder 5 initiates lookup queries to theDNS 10 for the further internet domain names it has generated, i.e. the truncated internet domain name and the potential internet domain names. For example, thetranscoder 5 may initiate lookup queries for “bobspizzashop.com”, “m.bobspizzashop.com” and “mobile.bobspizzashop.com”. - At step S6, the
DNS 10 provides the results of the lookup queries to thetranscoder 5. These will include the IP address associated with the PC web page at the truncated internet domain name “bobspizzashop.com” as well any IP addresses that are associated with the potential internet domain names. It is likely that not all of the prospective internet domain names used in the lookup queries will have a validly assigned IP address, in which case theDNS 10 returns either no result or a conventional error message for these internet domain names. - Using the IP addresses received from the
DNS 10, thetranscoder 5 sends HyperText Transfer Protocol (HTTP) requests, at step S7, to theweb server 6 for web pages using Uniform Resource Locator (URLs) based on the truncated internet domain name and the potential internet domain names, such as “http://bobspizzashop.com/webpage”, “http://mobile.bobspizzashop.com/webpage”, “http://m.bobspizzashop.com/webpage”, “http://bobspizzashop.com/mobile” and so on. Although asingle web server 6 is illustrated inFIG. 2 , the skilled person will appreciate that different web pages may be hosted by different web servers. The IP addresses received by thetranscoder 5 allow it to direct its request to the correct web server(s). - The
web server 6 then returns the requested web pages to thetranscoder 5, at step S8. These will include at least the PC web page associated with internet domain name “bobspizzashop.com” and may include other web pages which thetranscoder 5 has located, which may or may not be optimised for use bymobile communication device 2. Thetranscoder 5 analyses the returned web pages to determine which is the most appropriate for delivery to themobile communication device 2. In the example described above, the web page identified by internet domain name “bobspizzashop.com” is designed for viewing on a PC, while the web page identified by internet domain name “mobile.bobspizzashop.com” is designed for viewing on themobile communication device 2. It is therefore preferable to deliver the web page from “mobile.bobspizzashop.com” to themobile communication device 2, instead of that from “bobspizzashop.com”. - There may be multiple web pages designed for
mobile communication devices 2. For example, a first mobile web page designed formobile communication devices 2 may be stored at an address associated with internet domain name “mobile.bobspizzashop.com” and a second web page designed formobile communication devices 2 may be stored at an address associated with internet domain name “m.bobspizzashop.com”. In this case, thetranscoder 5 will determine which of the web pages designed formobile communication devices 2 is most appropriate for the particular mobile communication device that made the original request. - In some cases, it may be desirable to transcode the web page determined as most suitable for the
mobile communication device 2. This may be because none of the identified web pages are designed for mobile communication devices in general (for example, if the mobile web site at internet domain name “mobile.bobspizzashop.com” did not exist), or because they have not been optimised for the particularmobile communication device 2 that made the initial request at step S1. At step S9, thetranscoder 5 transcodes the determined web page if required. - The web page determined to be most appropriate for the mobile communication device is then returned to the mobile communication device, at step S10. As explained above, the web page returned to the mobile communication device may or may not have been transcoded by the
transcoder 5. - It is notable that the
transcoder 5 has now established which internet domain name associated with “bobspizzashop.com.mobi” provides the most appropriate web page for themobile communication device 2. In order to avoid duplication of effort, and to reduce lag times in future, at step S11, thetranscoder 5 stores this information. That is, thetranscoder 5 maps the internet domain name “bospizzashop.com.mobi” to the address of the most appropriate web page. Thetranscoder 5 may also store the most appropriate web page itself. The transcoded version of the web page may also be stored. As such, future requests for “bobspizzashop.com.mobi” are dealt with more efficiently without the requirement to identify IP addresses by trying a variety of lookup queries at theDNS 10. This is described below with reference to steps S12 to S15. - At step S12 a subsequent request for “bobspizzashop.com.mobi” is made. For clarity, this subsequent request is indicated coming from the
mobile communication device 2 which made the initial request at step S1, although in practice it could originate with a different mobile communication device. On receiving the request, thetranscoder 5 recognises the internet domain name “bobspizzashop.com.mobi” as this information has been saved by thetranscoder 5 at step S11. Thetranscoder 5 has also saved the URL of the web page which was determined to be most appropriate for delivery to themobile communication device 2. Accordingly, thetranscoder 5 may use this information to request the most appropriate web page from theweb server 6, at step S13. Theweb server 6 returns the web page to thetranscoder 5, at step S14, and this is subsequently forwarded to the mobile communication device, at step S15. - If the web page has been previously transcoded by
transcoder 5, then there is no need for thetranscoder 5 to obtain the web page from theweb server 6 again (steps S13 and S14). In these circumstances, the transcoded web page is simply returned to themobile communication device 2 from thetranscoder 5. - Information may be stored by the transcoder for a limited period to ensure that content delivered to the
mobile communication device 2 reflects the current state of the web page itself. For example, transcoded web resources may be stored for a week, a day, or any other appropriate time period. The appropriate time period may vary according to the type of content reflected by the web page. For example, a web page relating to breaking news may be expected to be updated regularly, meaning that it would only be appropriate to store a transcoded version of this web page for a short period, if at all. - The described embodiments of the invention are only examples of how the invention may be implemented. Modifications, variations and changes to the described embodiments will occur to those having appropriate skills and knowledge. These modifications, variations and changes may be made without departure from the scope of the invention defined in the claims and its equivalents.
Claims (22)
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
GB1006229A GB2479565A (en) | 2010-04-14 | 2010-04-14 | Providing mobile versions of web resources |
GB1006229.7 | 2010-04-14 | ||
PCT/EP2011/055959 WO2011128417A1 (en) | 2010-04-14 | 2011-04-14 | Providing mobile versions of web resources |
Publications (2)
Publication Number | Publication Date |
---|---|
US20140304370A1 true US20140304370A1 (en) | 2014-10-09 |
US9654596B2 US9654596B2 (en) | 2017-05-16 |
Family
ID=42245200
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/640,882 Active US9654596B2 (en) | 2010-04-14 | 2011-04-14 | Providing mobile versions of web resources |
Country Status (4)
Country | Link |
---|---|
US (1) | US9654596B2 (en) |
EP (1) | EP2558961B1 (en) |
GB (1) | GB2479565A (en) |
WO (1) | WO2011128417A1 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20160043989A1 (en) * | 2014-08-06 | 2016-02-11 | Go Daddy Operating Company, LLC | Search engine optimization of domain names and websites |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB2553243B (en) * | 2015-12-24 | 2018-05-16 | Num Tech Ltd | Methods, apparatuses, and computer programs for data processing, and hierarchical domain name system zone files |
GB2545748B8 (en) | 2015-12-24 | 2019-09-18 | Num Tech Ltd | Methods, apparatuses, and computer programs for data processing, and hierarchical domain name system zone files |
Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020178234A1 (en) * | 2001-03-06 | 2002-11-28 | Birchley Philip Alan | Browser software |
US20040068579A1 (en) * | 2002-08-13 | 2004-04-08 | International Business Machines Corporation | System and method to refresh proxy cache server objects |
US20080033998A1 (en) * | 2006-08-03 | 2008-02-07 | Yahoo! Inc. | Agent for identifying domains with content arranged for display by a mobile device |
US20090024698A1 (en) * | 2007-07-18 | 2009-01-22 | Networks Solutions, Llc | Mobile content service |
US20090094677A1 (en) * | 2005-12-23 | 2009-04-09 | International Business Machines Corporation | Method for evaluating and accessing a network address |
GB2464313A (en) * | 2008-10-10 | 2010-04-14 | Mtld Top Level Domain Ltd | Trancoding a web page |
US20100114879A1 (en) * | 2008-10-30 | 2010-05-06 | Netseer, Inc. | Identifying related concepts of urls and domain names |
US20110004850A1 (en) * | 2009-07-06 | 2011-01-06 | Philip Michael Lodico | Methods and apparatus for determining website validity |
US8201081B2 (en) * | 2007-09-07 | 2012-06-12 | Google Inc. | Systems and methods for processing inoperative document links |
Family Cites Families (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1271877B1 (en) * | 2001-06-22 | 2008-11-05 | Microsoft Corporation | Wireless browser |
WO2006091154A2 (en) * | 2005-02-25 | 2006-08-31 | Mobizoft Ab | A terminal independent addressing system for access to a web page via a public mobile network |
-
2010
- 2010-04-14 GB GB1006229A patent/GB2479565A/en not_active Withdrawn
-
2011
- 2011-04-14 EP EP11714557.3A patent/EP2558961B1/en active Active
- 2011-04-14 US US13/640,882 patent/US9654596B2/en active Active
- 2011-04-14 WO PCT/EP2011/055959 patent/WO2011128417A1/en active Application Filing
Patent Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020178234A1 (en) * | 2001-03-06 | 2002-11-28 | Birchley Philip Alan | Browser software |
US20040068579A1 (en) * | 2002-08-13 | 2004-04-08 | International Business Machines Corporation | System and method to refresh proxy cache server objects |
US20090094677A1 (en) * | 2005-12-23 | 2009-04-09 | International Business Machines Corporation | Method for evaluating and accessing a network address |
US20080033998A1 (en) * | 2006-08-03 | 2008-02-07 | Yahoo! Inc. | Agent for identifying domains with content arranged for display by a mobile device |
US20090024698A1 (en) * | 2007-07-18 | 2009-01-22 | Networks Solutions, Llc | Mobile content service |
US8201081B2 (en) * | 2007-09-07 | 2012-06-12 | Google Inc. | Systems and methods for processing inoperative document links |
GB2464313A (en) * | 2008-10-10 | 2010-04-14 | Mtld Top Level Domain Ltd | Trancoding a web page |
US20100114879A1 (en) * | 2008-10-30 | 2010-05-06 | Netseer, Inc. | Identifying related concepts of urls and domain names |
US20110004850A1 (en) * | 2009-07-06 | 2011-01-06 | Philip Michael Lodico | Methods and apparatus for determining website validity |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20160043989A1 (en) * | 2014-08-06 | 2016-02-11 | Go Daddy Operating Company, LLC | Search engine optimization of domain names and websites |
Also Published As
Publication number | Publication date |
---|---|
EP2558961A1 (en) | 2013-02-20 |
US9654596B2 (en) | 2017-05-16 |
WO2011128417A1 (en) | 2011-10-20 |
GB2479565A (en) | 2011-10-19 |
EP2558961B1 (en) | 2018-10-17 |
GB201006229D0 (en) | 2010-06-02 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8396990B2 (en) | Transcoding web resources | |
US8412767B2 (en) | Mobile content service | |
US9451046B2 (en) | Managing CDN registration by a storage provider | |
US20170295133A1 (en) | Establishing unique sessions for dns subscribers | |
US9219705B2 (en) | Scaling network services using DNS | |
US9444780B1 (en) | Content provided DNS resolution validation and use | |
US20230388361A1 (en) | Network address resolution | |
US8484373B2 (en) | System and method for redirecting a request for a non-canonical web page | |
KR101455625B1 (en) | Method for enriching content of a web page with presence information | |
US20110307776A1 (en) | Transcoding a web page | |
US9672295B2 (en) | Computer system | |
CN110933193B (en) | Domain name resolution method and device, electronic equipment and computer readable storage medium | |
US9654596B2 (en) | Providing mobile versions of web resources | |
US20040107266A1 (en) | URL management system and URL management server | |
US20180351777A1 (en) | Trustworthy Provisioning of DNS Resolutions Within Web Content | |
JP2005267435A (en) | Cache processing program and cache processor | |
TW201129039A (en) | Domain name parsing system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: AFILIAS TECHNOLOGIES LIMITED, IRELAND Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:CREMIN, RONAN;HARVIN, TREY;CETRARO, FRANCESCO;AND OTHERS;REEL/FRAME:029528/0371 Effective date: 20121109 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
AS | Assignment |
Owner name: PNC BANK, NATIONAL ASSOCIATION, PENNSYLVANIA Free format text: SECURITY INTEREST;ASSIGNORS:AFILIAS PUBLIC LIMITED COMPANY;AFILIAS TECHNOLOGIES LIMITED;REEL/FRAME:044262/0004 Effective date: 20171130 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |
|
AS | Assignment |
Owner name: AFILIAS USA, INC., PENNSYLVANIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:PNC BANK, NATIONAL ASSOCIATION;REEL/FRAME:054832/0354 Effective date: 20201229 Owner name: 101DOMAIN, INC., PENNSYLVANIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:PNC BANK, NATIONAL ASSOCIATION;REEL/FRAME:054832/0354 Effective date: 20201229 Owner name: AFILIAS TECHNOLOGIES LIMITED, PENNSYLVANIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:PNC BANK, NATIONAL ASSOCIATION;REEL/FRAME:054832/0354 Effective date: 20201229 Owner name: AFILIAS LIMITED (F/K/A AFILIAS PUBLIC LIMITED COMPANY), PENNSYLVANIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:PNC BANK, NATIONAL ASSOCIATION;REEL/FRAME:054832/0354 Effective date: 20201229 |
|
AS | Assignment |
Owner name: DEVICEATLAS LIMITED, IRELAND Free format text: CHANGE OF NAME;ASSIGNOR:AFILIAS TECHNOLOGIES LIMITED;REEL/FRAME:063019/0470 Effective date: 20201127 |