Systems and methods involving features of terminal operation including TOS-agnostic and/or other features

• US 9,923,950 B1
• Filed: 07/24/2013
• Issued: 03/20/2018
• Est. Priority Date: 07/24/2012
• Status: Active Grant

• Current Assignee: Ports America Group, Inc. (HarborCorp)
• Original Assignee: Ports America Group, Inc. (HarborCorp)
• Inventors: Sheykh-Zade, Irina, Duffy, Teresa, Desai, Geeta, Miron, Sophie, Song, Chung Daniel, Johnson, Nathan, Hill, Theresa, Sheykh-Zade, Eldar
• Primary Examiner(s): Bates, Kevin
• Assistant Examiner(s): Pant, Ranjan
• Application Number:
  US13/987,445
• Time in Patent Office: 1,700 Days
• CPC Class Codes: H04L 67/08 specially adapted for terminal emulation, e.g. Telnet

Abstract

Systems and methods are disclosed associated with processing information involving terminal operating systems. According to one illustrative implementation, an exemplary method for processing information involving terminal operating system herein may include processing data in a TOS format associated with a TOS type, converting the data into a TOS agnostic format, and performing processing using the TOS agnostic data.

Claims

1. A method for processing information involving terminal operating systems, the method comprising:

receiving an information request from a terminal operating system (TOS) of a first TOS type;

retrieving first data responsive to the information request, the first data defining a source of requested information;

constructing a first repository instance for the first data, the constructing comprising selecting an instance type from a plurality of instance types based on the first data and resolving an appropriate service for the instance type, wherein each of the plurality of instance types corresponds to one of a plurality of TOS types and the selected instance type corresponds to a second TOS type indicated by the first data;

requesting second data using the first repository instance to access a data source for a specific site of the second TOS type, the second data having a format specific to the second TOS type;

constructing a first business object using the second data;

generating, as a function of the first business object, a TOS-agnostic output through processing of the second data; and

providing, as a function of the first business object, the TOS-agnostic output for display to the user.

2. The method of claim 1, further comprising:

instantiating a second repository instance for the first TOS type; and

requesting first data using the second repository instance to access a data source for a specific site.

3. The method of claim 2, further comprising:

instantiating a third repository instance for a third TOS type;

requesting third data using the third repository instance to access a data source for a specific site;

constructing a second business object using the third data;

generating, as a function of the second business object, a second TOS-agnostic output through processing of the third data; and

providing, as a function of the second business object, the second TOS-agnostic output for display to the user.

4. The method of claim 1, further comprising:

converting third data in a third TOS format at a second TOS to the TOS-agnostic format via transformation involving use and/or creation of one or more repository instances and construction of a common business object structure as a function of a repository instance;

wherein the method further comprises providing the first data and the third data for processing via a user interface in the TOS-agnostic format while transmitting one or more outputs in original format via the repository to the first TOS and the second TOS.

5. The method of claim 1, wherein the first TOS type and the second TOS type are a same TOS type.

6. A method for processing information involving terminal operating systems, the method comprising:

retrieving terminal site information based on a cached terminal site list;

determining a terminal operating system (TOS) and connection information to the terminal site based on the retrieved terminal site information, the TOS having a TOS format;

determining whether or not an existing repository instance corresponds to the terminal site;

creating, after determining that a repository does not exist corresponding to the terminal site, a repository instance for the terminal site, the creating comprising selecting an instance type from a plurality of instance types based on the TOS format of the determined TOS and resolving an appropriate service for the instance type, wherein each of the plurality of instance types corresponds to one of a plurality of TOS types;

returning the repository instance; and

performing processing involving the repository instance, the processing comprising processing data in a TOS-agnostic format with a business object and interacting with the terminal site in the TOS format.

7. The method of claim 6, wherein the determining the terminal operating system comprises determining a relationship between cached attribute data in the retrieved terminal site information and a corresponding TOS type.

8. The method of claim 7, wherein determining the relationship between the cached attribute data and the TOS type comprises using at least one of a reflection operation, a helper attribute, and/or a convention to determine the relationship.

9. The method of claim 8, wherein using the reflection operation comprises discovering a TOS type that:

is configured to implement interfaces configured with an inversion of control container;

is contained in a namespace of interest; and

/or

comprises a TOS type attribute of interest and/or is contained in a sub-namespace named after a TOS type of interest.

10. The method of claim 6 wherein determining the terminal operating system comprises identifying a repository type related to the TOS type in a repository type cache received with the retrieved terminal site information.

11. The method of claim 10 wherein identifying the repository type related to the TOS type comprises using at least one of a reflection operation, a helper attribute, and/or a convention to determine the relationship.

12. The method of claim 11 wherein using the reflection operation comprises discovering a TOS type that:

is configured to implement interfaces configured with an inversion of control container;

is contained in a namespace of interest; and

/or

comprises a TOS type attribute of interest and/or is contained in a sub-namespace named after a TOS type of interest.

13. A method for processing information involving terminal operating systems, the method comprising:

generating, with a first business object, first information, wherein the first business object includes a plurality of business properties and associated functions for generating the first information in a terminal operating system (TOS) agnostic format;

determining a terminal and corresponding TOS based on the first information, the TOS having a TOS format;

performing repository processing, comprising;

constructing a repository instance corresponding to the determined terminal, the constructing comprising selecting an instance type from a plurality of instance types based on the TOS format of the determined terminal and resolving an appropriate service for the instance type, wherein each of the plurality of instance types corresponds to one of a plurality of TOS types;

processing the first information into TOS-formatted first data; and

transmitting the first data to the determined terminal.

14. The method of claim 13 further comprising:

performing processing, via one or more computing devices utilizing a Model-view-Controller (MVC) design pattern, including;

receiving and processing one or more user requests associated with the first information; and

constructing and sending one or more responses to the user regarding the data transmitted to the determined terminal.

15. The method of claim 13, wherein:

the performing repository processing further comprises;

receiving TOS-formatted second data in response to the first data;

processing the second data into the business object; and

the method further comprising processing the business object based on the received second data.

16. The method of claim 13, wherein:

the performing repository processing further comprises;

receiving TOS-formatted second data in response to the first data;

processing the second data into the business object; and

transmitting the second data to the determined terminal data service.

17. The method of claim 13, wherein the information includes a terminal identifier and request.

18. The method of claim 13, wherein each repository instance connects to one of a plurality of TOS types associated with that repository instance.