Legal claims defining the scope of protection. Each claim is shown in both the original legal language and a plain English translation.
1. A method of providing users access to Internet-ubiquitous value-added on-line services by way of an appended top-level domain (TLD) naming convention, the method comprising: storing, at a non-transitory data storage medium, data indicating that a third-party is authorized to utilize, in response to Internet queries from users, a proprietary software-as-a-service (SaaS) application comprising device-executable coded instructions stored at a non-transitory data storage medium of a server (SaaS server), wherein: the third-party possesses rights to a uniform resource locator (third-party URL) corresponding to a distinct IP address, the third-party URL sequentially includes a second level domain (SLD) and a Top Level Domain (TLD), and utilizing the SaaS application includes processing, by a data processor operably coupled with the SaaS server, information relating to the third-party, and transmitting a reply from the SaaS server to the querying user, wherein the reply includes the third-party information and a result of the processing; receiving, at a TLD authority server, an Internet query from a user, wherein the query sequentially includes the third-party URL and a proprietary TLD suffix, and wherein the proprietary TLD suffix is registered with an authorized Internet registration organization and corresponds to an IP address of the TLD authority server; parsing past the TLD suffix of the query, via a URL-parsing mechanism operably coupled with the TLD authority server, and determining an identity of the third party corresponding to the remaining third-party URL; confirming, via an authenticating/routing mechanism operably coupled with the data storage medium at which is stored the third-party authorization data, that the identified third-party is authorized to utilize the SaaS stored at the SaaS server; and routing the query to the SaaS server for utilization of the SaaS, but not routing the query to the IP address corresponding to the third-party URL.
A method for delivering online services using a special website address ending (TLD). It involves storing data confirming a company's right to use a software application (SaaS) on a server. When a user sends a web request that includes this company's address and the special TLD ending, a server for the TLD receives it. This server identifies the company, verifies their authorization to use the SaaS, and then redirects the request to the SaaS server instead of the company's usual website address. The SaaS server processes the request, accesses company-specific data, and sends a reply back to the user that includes the company information and the results from the SaaS application.
2. The method of claim 1 , further comprising: routing to the TLD authorization server user Internet queries having URLs that tem with the proprietary TLD suffix.
The method of providing online services using a special website address ending (TLD) also includes directing website requests that end with the proprietary TLD suffix to the TLD authorization server. This means any web address ending in the specific TLD (e.g., ".specialtld") will automatically be routed to the server responsible for managing that TLD, allowing it to process the request and route it to the correct SaaS application as described in the method for delivering online services using a special website address ending (TLD).
3. The method of claim 2 , wherein the routing involves a first routing to resolve the registered TLD suffix and a second routing to resolve the third-party URL behind the TLD suffix.
The method, which involves routing website requests that end with the proprietary TLD suffix to the TLD authorization server, uses a two-step routing process. First, the system figures out where to send requests based on the special TLD suffix. Second, after the request reaches the TLD server, it figures out where to send the request based on the company's website address *before* the TLD suffix, sending the request to a specific SaaS application as described in the method for delivering online services using a special website address ending (TLD).
4. The method of claim 3 , wherein the first routing is performed by a first server and the second routing is performed by a second server.
The method using a two-step routing process is divided between two different servers. The initial routing, based on the registered TLD suffix (like ".specialtld"), is handled by a first server. The second routing step, which determines the specific SaaS application to use based on the part of the web address before the TLD suffix, is handled by a second server. This splits the routing responsibility, improving performance and scalability as described in the method for delivering online services using a special website address ending (TLD).
5. The method of claim 4 , wherein the first server is configured further to maintain routing, and meta-tag information for one or more Internet-connected devices.
The first server, responsible for the initial routing based on the TLD suffix, also manages routing information and meta-tag data for various devices connected to the Internet. So, in addition to directing traffic based on the TLD, it keeps track of how to reach different devices and associated metadata, adding extra functionality to the routing process as part of the system for delivering online services using a special website address ending (TLD).
6. The method of claim 1 , wherein the routing the query to the SaaS server includes mapping the SLD of the third party URL to a particular one or more SaaS applications authorized for use by the third party, and identifying an IP address of the SaaS server configured with the one or more SaaS applications.
When the query is sent to the SaaS server, part of the routing process involves determining which specific SaaS application the company is authorized to use. The system maps the company's website address (the part before the TLD suffix) to one or more specific SaaS applications they are allowed to access. Then, it identifies the exact IP address of the server hosting those SaaS applications, ensuring the request is sent to the right place and processed using the appropriate software as described in the method for delivering online services using a special website address ending (TLD).
7. The method of claim 1 , wherein the SaaS application includes one or more software applications chosen from the group consisting of calendaring applications, social networking applications, geo-mapping applications, geo-locating applications, e-couponing applications, meta-tagging applications, demographic data mining applications, expert ranking applications, wild applications, blogging applications, journaling applications, travel applications, database correlation applications, data lookup applications, and ticketing applications.
The SaaS application, used in this method of delivering online services using a special website address ending (TLD), can be any of several types of software. Examples include calendaring, social networking, geo-mapping, geo-locating, e-couponing, meta-tagging, demographic data mining, expert ranking, wild applications, blogging, journaling, travel, database correlation, data lookup, and ticketing applications. The key is that the SaaS provides a specific online service related to the company's website address.
8. The method of claim 1 , wherein the SaaS application is configured to present a standardized use model to one or more Internet users who make one or more queries.
The SaaS application, used for providing access to Internet services through a special website address ending (TLD), is designed to present a consistent experience to all users, no matter which query they make. This means that regardless of the specific company or the data being processed, the SaaS application offers a standardized way for users to interact with the service, providing a uniform and predictable user experience as described in the method for delivering online services using a special website address ending (TLD).
9. The method of claim 1 , wherein the TLD authority server is a different server from the SaaS server.
The server responsible for managing the special TLD ending (TLD authority server) is a physically separate server from the server hosting the SaaS applications. This separation of responsibilities enhances security and scalability. The TLD authority server handles the initial routing and authentication, while the SaaS server focuses on processing the data and delivering the online service as described in the method for delivering online services using a special website address ending (TLD).
Unknown
August 12, 2014
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.