Classifications

• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
  • G06Q10/00—Administration; Management
  • G06Q10/02—Reservations, e.g. for tickets, services or events
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
  • G06Q30/00—Commerce
  • G06Q30/04—Billing or invoicing

Definitions

• the present subject matter relates to business travel account transactions. More specifically, to internet enabled systems and methods for travel- related transactions without the use of a travel agent or agency, and to enhanced billing and reconciliation processes .
• Business travel accounts or enhanced business travel accounts are commonly used by customers, such as corporations, to enable the corporation's employees to book, charge and track business related travel transactions.
• a business travel account is commonly used to charge and monitor travel expenses for employees, designated individuals or groups of people conducting company business that do not have or are not assigned individual corporate transaction cards.
• a business travel account may be a cardless account that enables employee travelers to book and charge travel-related expenses, such as air and rail expenses, in the course of their employment.
• the travel supplier billing information typically takes longer to arrive at the financial services provider than the travel agent's billing information.
• the time lag or delay for arrival of the travel supplier billing information can vary, e.g., several days is commons Since the travel agent's billing information normally arrives prior to the travel supplier billing information, the financial services provider can generate a statement to expedite the billing of booked travel transactions for faster payment by the customer. The financial services provider does not have to wait to receive billing information from the travel supplier prior to generating a billing statement.
• an improved business travel account process and system that enables a user to make travel transactions or bookings using a travel service system that can generate standard travel-related data files and a travel supplier system that can generate a unique identifier and charge files for booked travel transactions.
• the generated standard invoice data files by the travel services site, travel supplier charge files, and unique identifier for a booked travel itinerary enable a financial services provider to generate a billing statement for a customer based on the data files and unique identifier received from the travel services system and to reconcile the billed travel transactions against the charge files and unique identifier received from the travel supplier.
• a method for booking and billing business travel account transactions including the steps of creating a travel itinerary online via a travel service system; transmitting the travel itinerary to a travel supplier system; generating, at the travel supplier system, a unique indicator in response to the travel itinerary; transmitting the unique indicator to the travel service system, for example, via the internet, to confirm the travel itinerary; transmitting a user communication to a user confirming the travel itinerary; transmitting a travel service data file, including the unique indicator, to a billing and reconciliation system; generating a billing statement based on the travel service data file; generating a second travel supplier charge file corresponding to the travel itinerary including the unique indicator; transmitting the travel supplier charge file, including the unique indicator, to the billing and reconciliation system; and reconciling the travel service data file with the second travel supplier charge file using the unique identifier.
• a computer-readable medium having computer- executable instructions, such as a server with appropriate applications, for billing and reconciling one or more business travel account transactions.
• the computer- executable instructions enabling the performance of: receiving a first data file from a travel service system having a unique indicator corresponding to a travel itinerary; generating a billing statement for one or more transactions based on the received first data file; sending the billing statement to a customer; receiving a second data file from a travel supplier system, including the unique indicator corresponding to the travel itinerary; reconciling the first data file with the second data file using the unique identifier; and generating a revised billing statement if the first data file and the second data file are unmatched.
• the travel itinerary is created by an authorized user via a user machine connected to the travel service system via an interconnected network such as the internet or an intranet.
• the unique indicator is generated by the travel supplier system in response to receiving the travel itinerary from the first web site; and the unique indicator is transmitted to the travel service system to confirm the travel itinerary.
• a business travel account system for implementing the booking and billing business travel account process outlined above comprising an online travel services site communicatively connected to a user computer, a travel supplier and a billing and reconciliation system through a network, or a plurality of networks, and at least one communications link where the user computer includes a browser application for connecting to the travel services system and for enabling the user to enter the travel itinerary at the travel services system.
• FIG. 1 illustrates a system than can implement an online business travel account process according to one aspect of the present subject matter
• FIGs. 2A and 2B illustrate a process for an online business travel account process according to one aspect of the present subject matter.
• FIG. 1 is a block diagram of a system 100 that can be used to implement an improved online business travel account process 200, shown in FIGs. 2A and 2B, according to one aspect of the present subject matter.
• the system 100 includes a user system 10, a travel service system 12, a travel supplier system 14, a billing and reconciliation system 16.
• the user system 10 may refer to a user or customer, or a system or network operated by the user.
• the travel service system 12 may be a travel service computer or network and the travel supplier system 14 may be one or more travel suppliers, computers or networks.
• the billing and reconciliation system 16 may be operated by a financial service provider or part of a financial service provider system.
• the system 100 can be used by a user to make online travel transactions or bookings using the travel service system 12 and travel supplier system 14, and also enables the generation of standard enriched data files, charge files and invoice files for the travel transactions to thereby permit the billing and reconciliation system 16 to generate a billing statement for a corporate customer based on the data files received from the travel service system 12 and to reconcile the billed travel transactions against the data files received from the travel supplier system 14.
• the user system 10 may include a user computer that can be any of a variety of known computerized machines having a web browser application to permit the user to access the internet and connect to a computer or server employed by the travel system 12.
• An authorized or designated user having a pre-assigned identification (ID) and security password can connect to and access the travel service system to carry out travel booking transactions.
• the company to which the business travel account belongs may create a list of authorized users and submit the list to the travel service system 12 for storage and subsequent cross-checking during user log-in.
• the travel service system 12 may have one or more computers that run or execute various software applications to permit a user to make travel bookings under a company business travel account.
• the travel service system 12 can execute a log-in application that enables secure and controlled access to the site for online booking of travel transactions.
• a web interface application and log-in application permit s ecure and authorized user access by requiring users to enter unique user IDs and passwords.
• the log-in application cross-checks the user's information against the list of authorized users.
• the travel service system 12 can execute a business travel account software application capable of generating travel service data files, including, for example, standard enriched files, invoice files, and travel service transaction files, in response to a user's travel booking.
• the generated data files can then be transmitted to the billing and reconciliation system 16 for use in generating billing statements.
• the user is connected to and permitted to interact with a travel service software application that enables the user to request or enter online booking transactions.
• the software application correlates the user's ID and password with a corresponding business travel account stored at the travel service system 12 enabling booking transactions to be billed to the correct account number.
• the correspondence of the user ID and password to the business travel account number is transparent and masked from the user. In this manner, the user is not provided with and does not see the actual account number which results in an additional layer of security for the business travel account owner, i.e., the company. Booked business travel account transactions are charged or billed to the account number corresponding to the verified user ID and password.
• the travel service software application enables the user to create a travel itinerary or select their travel booking details through the established internet connection or portal.
• the user can enter a traveler profile that can include personal and employee information.
• the user can also enter traveling information such as place of travel origin and travel destination, dates of travel and selection of a desired travel supplier, e.g., a specific airline.
• the travel software application captures the user's booking or travel itinerary details and stores the booking or travel itinerary information in an associated travel service database.
• the travel service software application then transmits the user's booking request or travel itinerary details to a selected travel supplier system 14, e.g., a specific airline site.
• the travel service system 12 preferably communicates with the travel supplier system 14 via an internet communication link.
• the travel service software application is adapted to receive a confirmation and a unique reference identifier, such as, for example, a unique reference number, from the travel supplier system 14 for the user's travel itinerary request.
• the travel service software application stores the received booking confirmation and unique reference identifier in its associated travel service database.
• the travel service system 12 can then transmit the received confirmation for the booked travel to the user system 10.
• the travel service system 12 is also adapted to transmit a travel service data file to the billing and reconciliation system 16.
• the travel service system 12 preferably communicates with the billing and reconciliation system 16 via a dedicated and direct communication link.
• the travel service data file can include one or more data files as requested or required for use in a billing and reconciliation system 16.
• the travel service data file may include a travel service invoice file and a travel service transaction fee file.
• the travel service invoice file and transaction fee file may include travel and billing information about the booked travel transaction required by the billing and reconciliation system 16 for generation of a billing statement.
• both the travel service invoice file and travel service transaction fee file may include the unique reference identifier received from the travel supplier system 14.
• the unique reference identifier enables the billing and reconciliation system 16 to properly track, bill and store booked travel transactions for customer companies and to reconcile and pay the travel supplier system 14 for the booked travel.
• the booking travel itinerary sent to the billing and reconciliation system 16 can include the user's name, user's company information, travel itinerary information, date, time and pricing information and any other requested or required information.
• the travel service data file and in particular the travel service invoice file and the travel service transaction fee file, preferably have a data file format and data content that conforms to standard data file formats used in existing systems used by travel agents or agencies.
• the travel supplier system 14 in the system 100 may include one or more machines that run or execute one or more software applications, including a web interface application and a travel supplier application.
• the travel supplier application is adapted to receive the booking request or travel itinerary transmitted by the user system 10.
• the travel supplier system 14 is adapted for communication with the travel service system 12 and the billing and reconciliation system 16 via dedicated and direct communication links. Alternatively, internet communication links may be used.
• the travel supplier application is adapted to receive the travel itinerary transmitted by the travel service system 12.
• the travel supplier application confirms the travel itinerary and generates the unique reference identifier for the user's booking request.
• the travel supplier application then transmits a confirmation and the unique reference identifier to the travel service system 12.
• the travel supplier application also stores the confirmation, unique reference identifier and received booking travel information in its associated travel supplier database. In this manner, the travel supplier system 14 may subsequently access and transmit this information as needed.
• the travel supplier system 14, via its travel supplier application preferably generates travel supplier data files, which can include a travel supplier invoice file and a travel supplier charge file, for transmission to and use by the billing and reconciliation system 16.
• the travel supplier system 14 can transmit the travel supplier data files directly to the billing and reconciliation system 16.
• the travel supplier data files can include one or more data files as requested or required by the billing and reconciliation system 16.
• the travel supplier data files may include a travel supplier invoice file and a travel supplier charge file, which contain data and information about the confirmed booking transaction and billing and pricing data.
• the travel supplier invoice file and the travel supplier charge file can include, among other data and information, the user's name, the user's company information, travel itinerary information, date, time and pricing information and other requested or required information.
• both the travel supplier invoice file and travel supplier charge file include the unique reference identifier. The unique reference identifier, along with the travel supplier invoice file and travel supplier charge file, enables the billing and reconciliation system 16 to properly track and reconcile travel bookings previously received and billed to customers.
• the travel supplier data files may have a data file format and data content that conforms to existing standard formats used in systems and processes where travel agents or agencies are used.
• the combination of the travel supplier system 14 and travel service system 12 can replace the travel agent or agency in a travel-related booking processes.
• the travel supplier system 14 and travel service system 12 can communicate with the billing and reconciliation system 16 to transmit data files to the billing and reconciliation system 16.
• the billing and reconciliation system 16 receives necessary data files to provide the billing and reconciliation system 16 with the capability to reconcile billing statements previously sent to its customers.
• the travel supplier system 14 via its application, can alternatively transmit the travel supplier data files through a third party payment service system 18, e.g., a Bibit submitter, who can then directly transmit a Bibit generated supplier charge file to the billing and reconciliation system 16.
• a third party payment service system 18 e.g., a Bibit submitter
• Such a transmission path for the travel supplier data file may be used or necessary in cases where the travel supplier system 14 does not have the capability to generate the travel supplier data files for direct transmission to the billing and reconciliation system 16.
• the travel supplier application transmits the confirmed travel itinerary details and the generated unique reference identifier to the third party payment service system 18.
• the third party payment service system 18 can then generate the travel supplier charge file for transmission to and use by the billing and reconciliation system 16.
• the billing and reconciliation system 16 can then use the travel supplier charge file for tracking and reconciliation purposes as discussed above.
• the travel supplier charge file includes one or more data files requested or required by the billing and reconciliation system 16.
• the travel supplier charge file also includes data and information about the confirmed travel booking transaction, the unique reference identifier, and billing and pricing data.
• the third party generated travel supplier charge file can also include, among other data and information, the user's name, the user's company information, travel itinerary information, date, time and other requested or required information.
• the unique reference identifier, along with other travel itinerary details, contained in the travel supplier invoice file and travel supplier charge file enable the billing and reconciliation system 16 to properly reconcile travel bookings.
• FIG. 1 also shows the billing and reconciliation system 16 in the system 100.
• the billing and reconciliation system 16 can have one or more machines or servers running and executing software applications, including a web interface application and a billing and reconciliation application.
• the billing and reconciliation system 16 via the web interface application and the billing and reconciliation application, is adapted to receive data files from the travel service system 12, and the travel supplier system 14 or, alternatively, from the third party payment service system 18, as discussed previously.
• the billing and reconciliation system 16 can store the received data files in an associated billing and reconciliation database where they are subsequently accessible as needed for billing, reconciling, reporting and other system functions.
• the billing and reconciliation system 16 preferably communicates with the travel service system 12, the travel supplier system 14 and the third party payment service system 18 via dedicated and direct communication links. While the system has been described as utilizing dedicated and direct communication links, alternatively, the system 100 may be implemented such that the communications between the elements of the system 100 occur via the internet.
• the billing and reconciliation system 16 may be adapted to receive data files in a standard data format and content usable in existing processes.
• the billing and reconciliation system 16 may receive data and information from the travel service system 12 and travel supplier system 14.
• Data files received by the billing and reconciliation system 16 preferably contain the unique reference identifier in order to provide a means for the billing and reconciliation system 16 to accurately reconcile travel charges booked on the travel service system 12
• the billing and reconciliation system 16 via the billing and reconciliation application, is adapted to carry out and execute various functions and capabilities, including tracking, storing, billing and reconciling of travel-related bookings.
• the billing and reconciliation system 16, via the received data files and unique reference identifier, is adapted to create billing statements for submission to responsible customers and to reconcile billing statements against travel charges received from the travel supplier system 14 or third party payment service system 18.
• the billing and reconciliation system 16 received the travel service data files prior to the travel supplier charge files.
• the billing and reconciliation system 16 can use the travel service files and the unique reference identifier to create billing statements for submission to company customers.
• the billing and reconciliation system 16 can generate a billing statement based on the received travel service files for submission to the responsible customer for payment. In this manner, the billing and reconciliation system 16 expedites the generation and submission of statements for payment by its customers.
• the billing and reconciliation system 16 does not have to wait for the travel supplier system 14 to submit its charge file before issuing a billing statement.
• the billing and reconciliation system 16 also receives the travel supplier invoice file, travel supplier charge file or the third party generated charge file, each having the unique reference identifier.
• the travel supplier data files typically arrive at a later time than the travel service data files. In some cases, the travel supplier system 14 may not submit the travel supplier data files until after the user has actually used the services provided by the travel supplier system 14.
• the billing and reconciliation system 16 can use the travel supplier files and/or the third party generated charge file, along with the unique reference identifier, to reconcile the previously generated and submitted billing statements against the travel supplier charges now received from the travel supplier system 14 or third party payment service system 18.
• the unique reference identifier is used as the means to determine whether the various received data files correspond. This aspect allows the billing and reconciliation system 16 to ensure that that the previously submitted statement, generated based on the travel service data files is accurate or whether the statement needs correction.
• the billing and reconciliation system 16 can also choose to wait until the data files from both the travel service system 12 and travel supplier system 14 are received to initiate the subsequent generation of the billing statement and the reconciliation of the booking charges received.
• the billing and reconciliation system 16 determines whether the travel service invoice file and transaction fee file match the travel supplier invoice file and a travel supplier charge file or the third party generated charge file. The same unique reference identifier can be used to determine whether the various received data files correspond to each other. If there is a match, the statement can then be generated and submitted to the user system 10 for payment.
• the statement can contain information requested or required by the customer, such as name of traveler, travel dates and cost, description of services, etc.
• FIGs. 2A and 2B show a flowchart for an online business travel account process 200 than can be implemented in the system 100 shown in FIG. 1, according to one aspect of the present subject matter.
• the process 200 shown enables the user to make online travel transactions or bookings using the travel service system 12 and the travel supplier system 14 which can generate standard data files and a unique reference identifier.
• the process 200 further enables the billing and reconciliation system 16 to bill a corporate customer based on travel service data files and a unique reference identifier received from the travel service system 12 and to reconcile the billed travel transactions by additionally using travel supplier data files and the unique reference identifier received from the travel supplier system 12.
• the user accesses the travel service system 12 using a computer with an internet browser.
• the user can be, for example, an employee of a company that has set up a business travel account with a financial service provider, which may in turn employ the billing and reconciliation system 16.
• Access to the travel service system 12 may be provided via the internet. Accordingly, the user may be provided with the appropriate web site address or uniform resource locator (URL) address.
• URL uniform resource locator
• the travel service system 12 can be provided by the financial services provider or can be provided by a third party vendor.
• the user enters a user ID and password to log-in and access the travel service system 12, which is preferably available only to authorized users.
• the travel service system 12 cross-checks the user's ID and password against a list of authorized users previously received from a company customer via a log-in application.
• step S 15 the online travel log-in program allows the user to proceed with travel bookings once the user ID and password have been verified.
• the online travel service application accesses the business travel account number that corresponds to the ID and password submitted for correlation of any travel booked by the user to the accessed account number.
• the accessed account number is preferably not displayed to the user. Accessing the account number is transparent to the user and is a background action that provides another layer of security for the account number. In cases where it is specifically permitted, the accessed account number may be displayed to the user.
• the online travel service system 12 captures the booking details entered by the user.
• the travel service system 12 permits the user to confirm the travel selection and to make any desired changes.
• the user decides where, when and by what means they want to travel.
• the travel details entered can include the origin and destination cities, travel dates, travel supplier desired, etc.
• the user enters the search parameters and the travel service system 12 carries out a search and then displays travel search results and options for the user. The user can then make travel selections and finalize their travel selections.
• the travel service system 12 can store the user's booking details in an associated storage location, such as a travel service site database.
• step S25 after the user has made their final travel selections, the travel service system 12 communicates or transmits the captured user booking request details to a travel supplier system 14.
• a travel supplier system 14 As noted previously, there may be more than one travel supplier system 14, though only one is shown in FIG. 1.
• step S30 the travel supplier 20 receives the user booking request sent by the travel service system 12.
• the travel service application then generates a unique reference identifier for the received user booking request.
• the reference identifier can be a unique ticket number.
• step S35 the travel supplier system 14 confirms the user booking request by transmitting the unique reference identifier for the travel transaction to the travel service system 12.
• step S40 the travel service system 12 receives the confirmation unique reference identifier from the travel supplier system 14.
• the travel supplier system 14 can then store the booking request information and the generated unique reference identifier in an accessible storage medium, such as its database.
• Step S45 the travel service system 12 transmits confirmation of the user booking request to the user.
• the travel service system 12 generates and transmits travel service site data files to the billing and reconciliation system 16.
• the travel service data files includes a travel service site invoice data file, which can contain travel details and invoice listings of charges for the user's internet booked trip, and a travel service transaction fee file, which contains the transaction fees charged by the travel service system 12 for facilitating the user's booking.
• Both travel service data files preferably contain the received unique identifier.
• the travel service data files, including the unique reference identifier are then communicated or transmitted to the billing and reconciliation system 16.
• step S55 the billing and reconciliation system 16 receives and captures the travel service data files, including the unique reference identifier, sent by the travel service system 12.
• step S60 the billing and reconciliation system 16, via the billing and reconciliation application, can store the received travel service data files in an associated storage medium, such as a designated database. The billing and reconciliation system 16 can then access the stored data files as required for billing and reconciliation of travel bookings made using a business travel account.
• step S65 the billing and reconciliation system 16 links or correlates the travel service data files through the unique reference identifier which results in a combined or matched file.
• the stored travel service invoice data file is preferably matched or correlated with the travel service site transaction fee file through the unique reference identifier.
• the combined or matched file is known in systems and processes as an MST file.
• a billing statement is produced for submission to a customer. Travel details and costs are accessed from the database and formatted for inclusion and reporting in a billing statement.
• the generated billing statement includes all booking details that the user selected for one or more travel bookings.
• the billing statement is generated at the end of a predetermined billing period agreed to by both the customer and the billing and reconciliation system 16. For example, the billing statement may be generated immediately upon receipt and matching of the travel service date files, or may be generated weekly or monthly.
• the billing statement is generated immediately upon receipt and matching of the travel service date files and prior to receipt of corresponding travel supplier charge files. Travel supplier charge files typically arrive after the travel service data files, often several business days later.
• the travel supplier system 14 generates and transmits travel supplier data files to the billing and reconciliation system 16.
• the travel supplier data files can be generated by the travel supplier system 14 or can be generated by the third party payment service system 18.
• the travel supplier data files can include a travel supplier invoice file, which can contain travel details for the user's internet booked trip, and a travel supplier charge file, which includes travel supplier charges for the user's travel. Both travel supplier invoice and charge files preferably contain the unique reference identifier.
• the travel supplier data files, which include the unique reference identifier can be communicated or transmitted to the billing and reconciliation system 16 before or after the user actually goes on the booked travel and uses the travel supplier's services.
• the travel supplier data files are preferably used for reconciliation of previously received travel bookings from the travel service system 12.
• step S80 the billing and reconciliation system 16 receives and captures the travel supplier data files, including the unique reference identifier.
• the billing and reconciliation system 16 via a billing and reconciliation application, loads and stores the received travel supplier invoice and charge files in an associated storage medium, such as the designated database.
• the received travel supplier invoice and charge files can instead be loaded in a separate reconciliation database.
• the billing and reconciliation system 16 can subsequently access the stored travel service data files and the travel supplier data files as required for reconciliation of previously billed bookings.
• step S90 the billing and reconciliation system 16 correlates the travel service data files with the travel supplier data files.
• the travel service invoice file is matched with the travel supplier charge file using the unique reference identifier.
• the matching may be done on the database or in a designated reconciliation database. Once the correlation is complete, data stored in the database, such as the reconciliation database can be deleted.
• Discrepancies uncovered in the matching step can be corrected at that time or at a later date. For example, if a billing statement has gone out to a customer for payment and has been paid, the billing and reconciliation system 16 can issue a revised billing statement with corrections found in the reconciliation step.
• the customer may be provided with a refund or a statement credit if money is due back to the customer or may be provided with a new balance if a balance is due.
• Those of ordinary skill in the art will readily recognize that many of the functions and aspects of the system 100 and process 200 can be implemented on networked computers, which may be connected for data communication via components of a network.
• each such general-purpose computer typically comprises a central processor, an internal communication bus, various types of memory (RAM, ROM, EPROM, cache memory, etc.), disk drives or other code and data storage systems, and one or more network interface cards or ports for communication purposes.
• the computer system also may be coupled to a display and one or more user input devices such as alphanumeric and other keys of a keyboard, a mouse, a trackball, etc.
• the display and user input element(s) together form a service-related user interface, for interactive control of the operation of the computer system.
• These user interface elements may be locally coupled to the computer system, for example in a workstation configuration, or the user interface elements may be remote from the computer and communicate therewith via a network.
• the elements of such a general-purpose computer system also may be combined with or built into routing elements or nodes of the network.
• the software functionalities e.g., many of the operations described above
• the software code is executable by the general-purpose computer that functions as the particular computer.
• the executable program code and possibly the associated data are stored within the general-purpose computer platform. At other times, however, the software may be stored at other locations and/or transported for loading into the appropriate general-purpose computer system.
• the embodiments involve one or more software products in the form of one or more modules of code carried by at least one machine-readable medium. Execution of such code by a processor of the computer platform enables the platform to implement the system or platform functions, in essentially the manner performed in the embodiments discussed and illustrated herein.
• terms such as computer, server or machine readable medium refer to any medium that participates in providing instructions to a processor for execution. Such a medium may take many forms, including but not limited to, non-volatile media, volatile media, and transmission media.
• Non-volatile media include, for example, optical or magnetic disks, such as any of the storage devices in any computer(s).
• Volatile media include dynamic memory, such as main memory of such a computer platform.
• Physical transmission media include coaxial cables; copper wire and fibre optics, including the wires that comprise a bus within a computer system.
• Carrier-wave transmission media can take the form of electric or electromagnetic signals, or acoustic or light waves such as those generated during radio frequency (RF) and infrared (IR) data communications.
• RF radio frequency
• IR infrared
• Computer-readable media therefore include, for example: a floppy disk, a flexible disk, hard disk, magnetic tape, any other magnetic medium, a CD-ROM, DVD, any other optical medium, punch cards, paper tape, any other physical medium with patterns of holes, a RAM, a PROM, and EPROM, a FLASH-EPROM, any other memory chip or cartridge, a carrier wave transporting data or instructions, cables or links transporting such a carrier wave, or any other medium from which a computer can read programming code and/or data. Many of these forms of computer readable media may be involved in carrying one or more sequences of one or more instructions to a processor for execution.

Landscapes

• Business, Economics & Management (AREA)
• Engineering & Computer Science (AREA)
• Development Economics (AREA)
• Tourism & Hospitality (AREA)
• Economics (AREA)
• Marketing (AREA)
• Strategic Management (AREA)
• Physics & Mathematics (AREA)
• General Business, Economics & Management (AREA)
• General Physics & Mathematics (AREA)
• Theoretical Computer Science (AREA)
• Finance (AREA)
• Accounting & Taxation (AREA)
• Entrepreneurship & Innovation (AREA)
• Human Resources & Organizations (AREA)
• Operations Research (AREA)
• Quality & Reliability (AREA)
• Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Priority Applications (1)

Applications Claiming Priority (1)

Publications (1)

Family

ID=34960466

Family Applications (1)

Country Status (1)

• 2005
  • 2005-01-24 WO PCT/US2005/002476 patent/WO2006080916A2/fr not_active Ceased

Similar Documents

Legal Events