US20100205652A1 - Methods and Systems for Handling Online Request Based on Information Known to a Service Provider - Google Patents
Methods and Systems for Handling Online Request Based on Information Known to a Service Provider Download PDFInfo
- Publication number
- US20100205652A1 US20100205652A1 US12/226,880 US22688007A US2010205652A1 US 20100205652 A1 US20100205652 A1 US 20100205652A1 US 22688007 A US22688007 A US 22688007A US 2010205652 A1 US2010205652 A1 US 2010205652A1
- Authority
- US
- United States
- Prior art keywords
- information
- request
- message
- online
- logical identifier
- 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.)
- Abandoned
Links
Images
Classifications
-
- 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/953—Querying, e.g. by the use of web search engines
- G06F16/9535—Search customisation based on user profiles and personalisation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR 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
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/02—Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR 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
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR 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
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR 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/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0241—Advertisements
- G06Q30/0251—Targeted advertisements
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR 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/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0241—Advertisements
- G06Q30/0251—Targeted advertisements
- G06Q30/0253—During e-commerce, i.e. online transactions
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR 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/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0241—Advertisements
- G06Q30/0251—Targeted advertisements
- G06Q30/0254—Targeted advertisements based on statistics
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR 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/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0241—Advertisements
- G06Q30/0251—Targeted advertisements
- G06Q30/0255—Targeted advertisements based on user history
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR 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/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0241—Advertisements
- G06Q30/0251—Targeted advertisements
- G06Q30/0264—Targeted advertisements based upon schedule
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR 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/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0241—Advertisements
- G06Q30/0251—Targeted advertisements
- G06Q30/0269—Targeted advertisements based on user profile or attribute
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR 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/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0241—Advertisements
- G06Q30/0277—Online advertisement
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR 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
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR 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
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/12—Accounting
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0892—Network architectures or network communication protocols for network security for authentication of entities by using authentication-authorization-accounting [AAA] servers or protocols
-
- 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/10—Protocols in which an application is distributed across nodes in the network
-
- 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/2866—Architectures; Arrangements
- H04L67/30—Profiles
- H04L67/306—User profiles
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/02—Services making use of location information
- H04W4/023—Services making use of location information using mutual or relative location information between multiple location based services [LBS] targets or of distance thresholds
Definitions
- the present invention relates generally to online requests effected over computer networks such as the Internet and, more particularly, to methods and systems for handling online requests based on information known to a service provider.
- Computer networks such as the Internet allow users to make various online requests.
- a user can make a request for an online transaction (e.g., a request to purchase a product or service offered on a network site, a request to transfer funds to or from a financial account, etc.); a request for a delivery of a product or service to a particular place (e.g., a request to have food delivered to a house or other building); a request for an access to online private content (e.g., a request to access an online email account); a request for a download of data (e.g., a request to download a video file, an audio file, a software upgrade file, streaming video, streaming audio, etc.); etc.
- an online transaction e.g., a request to purchase a product or service offered on a network site, a request to transfer funds to or from a financial account, etc.
- a request for a delivery of a product or service to a particular place e.g., a request to have
- a network element processes information related to the online request and provided by the user. For example, where a user makes a request to purchase a product or service offered on a network site using a credit card, a server operated by a card issuing bank that issued the credit card typically processes credit card information (e.g., a card number, an expiry date, and/or a cardholder's name) provided by the user in order to approve or deny the online transaction attempted to be made by the user; where a user makes a request to have a given product or service delivered to a house or other building, a server operated by an entity responsible to effect this delivery typically processes a civic address of the house or other building provided by the user in order to determine where to deliver the product or service; where a user makes a request to access an online email account, a server operated by an entity providing the online email account typically processes a user name and password provided by the user in order to identify and control access to the online email
- Handling of an online request made by a user often involves verifying whether information related to the online request and provided by the user has been legitimately used by the user and/or can be trusted. For example, where a user makes a request to purchase a product or service offered on a network site and provides credit card information for this purpose, a verification as to whether the user is legitimately providing the credit card information is typically made in an effort to counter fraudulent online transactions; where a user makes a request to have a given product or service delivered to a house or other building and provides a civic address for this purpose, a verification as to whether the civic address is valid may be made in an effort to avoid delivery to a wrong or invalid address; etc.
- the present invention provides a method comprising: obtaining first information, the first information relating to an online request made using a communication apparatus; using a logical identifier assigned to the communication apparatus to obtain second information, the second information pertaining to a profile associated with the logical identifier; comparing the first information to the second information; and performing an action related to handling of the online request based on a result of the comparing.
- the present invention also provides an apparatus comprising an interface for receiving messages and a processing unit coupled to the interface.
- the processing unit is responsive to receipt of a message at the interface for: obtaining first information, the first information relating to an online request made using a communication apparatus; using a logical identifier assigned to the communication apparatus to obtain second information, the second information pertaining to a profile associated with the logical identifier; comparing the first information to the second information; and performing an action related to handling of the online request based on a result of the comparing.
- the present invention also provides a computer-readable medium storing a program element for execution by a computer.
- the program element comprises: first program code for causing the computer to obtain first information, the first information relating to an online request made using a communication apparatus; second program code for causing the computer to use a logical identifier assigned to the communication apparatus to obtain second information, the second information pertaining to a profile associated with the logical identifier; third program code for causing the computer to perform a comparison of the first information to the second information; and fourth program code for causing the computer to perform an action related to handling of the online request based on a result of the comparison.
- the present invention also provides a method comprising: receiving a first message conveying a logical identifier; consulting a database on a basis of the logical identifier to obtain information known to a service provider involved in assigning the logical identifier; processing the information to generate a second message to be used in handling an online request made using a communication apparatus to which is assigned the logical identifier; and transmitting the second message.
- the present invention also provides an apparatus comprising an interface for receiving a first message conveying a logical identifier and a processing unit coupled to the interface.
- the processing unit is operative for: consulting a database on a basis of the logical identifier to obtain information known to a service provider involved in assigning the logical identifier; processing the information to generate a second message to be used in handling an online request made using a communication apparatus to which is assigned the logical identifier; and causing said interface to transmit the second message.
- the present invention also provides a computer-readable medium storing a program element for execution by a computer.
- the program element comprises: first program code for causing the computer to receive a first message conveying a logical identifier; second program code for causing the computer to consult a database on a basis of the logical identifier to obtain information known to a service provider involved in assigning the logical identifier; third program code for causing the computer to process the information to generate a second message to be used in handling an online request made using a communication apparatus to which is assigned the logical identifier; and fourth program code for causing the computer to transmit the second message.
- FIG. 1 shows an architecture allowing a user of a communication apparatus connected to a public packet-switched network to access and interact with network sites of that network, for example, to make online requests, in accordance with an embodiment of the present invention
- FIG. 2 shows an example of potential contents of a profile information database accessible to a profile information server of the architecture shown in FIG. 1 ;
- FIGS. 3A and 3B illustrate an example of interaction between the profile information server, a transaction validation server and other elements of the architecture shown in FIG. 1 , in an example scenario where the user of the communication apparatus makes a request for an online transaction using a credit card;
- FIG. 3C illustrates a variant to the example considered in FIGS. 3A and 3B ;
- FIG. 4 shows an example of potential contents of a database accessible to the transaction validation server shown in FIGS. 3A and 3B ;
- FIGS. 5 to 7 illustrate an example process by which the profile information database of the architecture shown in FIG. 1 may be populated, in accordance with an embodiment of the present invention.
- FIG. 1 depicts an architecture allowing a user 10 of a communication apparatus 12 connected to a public packet-switched network 14 (e.g., the Internet) to access and interact with network sites (e.g., web sites) of the network 14 , in accordance with an embodiment of the present invention.
- a public packet-switched network 14 e.g., the Internet
- network sites e.g., web sites
- the communication apparatus 12 comprises a computing device 16 and a network interface unit 18 .
- the computing device 16 may be implemented as a personal computer (PC) such as a desktop computer, a laptop computer, or a tablet PC.
- the computing device 16 is provided with at least one input device such as a keyboard, a mouse, a touchscreen, a stylus, a microphone, etc., as well as a display and possibly one or more other output devices (e.g., speakers) that enable interaction between the user 10 and the computing device 16 .
- the computing device 16 is operative to run a software application implementing a network browser (e.g., a web browser) with which the user 10 can interact via the display (and possibly one or more other output devices) and the at least one input device in order to access and interact with network sites of the public packet-switched network 14 .
- a network browser e.g., a web browser
- the network interface unit 18 enables the communication apparatus 12 to exchange data with the public packet-switched network 14 via a communication link 20 .
- the network interface unit 18 may be implemented as a modem such as a broadband modem (e.g., a digital subscriber line (DSL) modem or a cable modem) or a narrowband modem (e.g., a dial-up modem).
- a broadband modem e.g., a digital subscriber line (DSL) modem or a cable modem
- a narrowband modem e.g., a dial-up modem
- the network interface unit 18 may be integrated into the computing device 16 (e.g., it may be a card internal to the computing device 16 ).
- the communication link 20 may traverse one or more network elements and comprise one or more physical links and one or more logical links.
- the communication link 20 may comprise a physical link 17 between the network interface unit 18 and a network element 21 .
- the physical link 17 may comprise a copper twisted pair, a coax cable, an Ethernet link, a fiber optic link (e.g., fiber to the premises (FTTP)), a fixed wireless link, a satellite link, or a combination thereof.
- the network element 21 may be a DSL access multiplexer (DSLAM), a cable modem termination system (CMTS), or another type of network element.
- DSL access multiplexer DSL access multiplexer
- CMTS cable modem termination system
- the communication link 20 may also comprise a dedicated logical link 19 between the network element 21 and another network element 23 that provides access to the public packet-switched network 14 .
- the network element 23 may be a network access server (NAS), a router, etc. It will be appreciated that the communication link 20 may take on many forms in various embodiments.
- the communication apparatus 12 comprises the computing device 16 and the network interface unit 18 , it will be appreciated that the communication apparatus 12 may comprise other components in other embodiments.
- the communication apparatus 12 is assigned a logical identifier.
- the logical identifier which may be assigned to the computing device 16 or the network interface unit 18 , may be an Internet Protocol (IP) address (e.g., in compliance with IPv4 or IPv6) or a proprietary address, label or tag.
- IP Internet Protocol
- the logical identifier may be statically assigned to the communication apparatus 12 in which case it does not change over time (e.g., a static IP address).
- the logical identifier may be dynamically assigned to the communication apparatus 12 in which case it may change over time (e.g., a dynamic IP address).
- the logical identifier may be assigned to the communication apparatus 12 by a network element that is part of the communication link 20 (e.g., the network element 23 in embodiments where it is a network access server).
- This network element may assign the logical identifier to the communication apparatus 12 when the communication apparatus 12 is activated (e.g., when the network interface unit 18 and/or the computing device 16 is/are powered-up) or otherwise regains network connectivity and/or at certain time intervals which may range from an hour or less to several months or more.
- the network element assigning the dynamic IP address to the communication apparatus 12 may do so in accordance with the Dynamic Host Configuration Protocol (DHCP) using a pool of IP addresses accessible to that network element.
- DHCP Dynamic Host Configuration Protocol
- assignment of the logical identifier to the communication apparatus 12 may be effected in various ways in various embodiments.
- the user 10 can use the communication apparatus 12 to access and interact with network sites of the public packet-switched network 14 .
- These network sites are implemented by servers 30 1 . . . 30 N connected to the public packet-switched network 14 .
- the servers 30 1 . . . 30 N and the network sites that they implement are operated, managed or otherwise associated with various entities, including, for example, companies, governmental organizations, non-profit organizations, and individuals.
- Each of the servers 30 1 . . . 30 N comprises suitable hardware, firmware, software, control logic, or a combination thereof for implementing a plurality of functional components, including an interface and a processing unit.
- the interface of each of the servers 30 1 . . . 30 N is adapted to receive and send data (e.g., in the form of messages) from and to communication apparatus (such as the communication apparatus 12 ) connected to the public packet-switched network 14 as well as other elements (e.g., computers or databases) communicatively coupled to that server but not necessarily connected to the packet-switched network 14 .
- the processing unit of each of the servers 30 1 . . . 30 N is adapted to effect various processing operations to implement that server's functionality.
- Interaction of the user 10 with a network site implemented by a server 30 n (1 ⁇ n ⁇ N) typically involves the network browser implemented by the computing device 16 interacting with the server 30 n in order to allow the user 10 to view, hear or otherwise be exposed to content (e.g., web pages) of the network site via the display and/or one or more other output devices of the computing device 16 , and possibly to input information (e.g., by entering text, selecting an option, etc.) and/or one or more commands (e.g., by clicking on a graphical button or a hyperlink) via the at least one input device of the computing device 16 .
- content e.g., web pages
- input information e.g., by entering text, selecting an option, etc.
- commands e.g., by clicking on a graphical button or a hyperlink
- the online request can be any request made online, i.e., any request made by way of the communication apparatus 12 transmitting data over the public packet-switched network 14 .
- the online request can be a request for anything which can be requested online.
- the online request may be:
- the online request can be a request for anything which can be requested online.
- the user 10 In making the online request while interacting with the network site implemented by the server 30 n the user 10 provides via the communication apparatus 12 information related to the online request.
- This information which is hereinafter referred to as “request-related information”, can take on various forms depending on the nature of the online request being made. For example:
- the request-related information may be provided by the user 10 via the communication apparatus 12 in various ways.
- the user 10 may use the at least one input device of the computing device 16 to input the request-related information and cause this information to be sent by the communication apparatus 12 to the server 30 n (or another computer associated with the server 30 n ) over the public packet-switched network 14 .
- the request-related information may have been previously stored in a memory of the computing device 16 , in which case the user 10 may use the at least one input device of the computing device 16 to cause the communication apparatus 12 to send the request-related information to the server 30 n (or another computer associated with the server 30 n ) over the public packet-switched network 14 .
- a request handling element 51 adapted to process the request-related information provided by the user 10 via the communication apparatus 12 in order to handle the online request made by the user 10 .
- Functionality of the request handling element 51 depends on the nature of the online request being made. For example:
- the request handling element 51 may be communicatively coupled to the server 30 via a communication path 79 .
- the communication path 79 may be established over the public packet-switched network 14 and/or another network 59 (e.g., a financial network).
- another network 59 e.g., a financial network
- the request handling element 51 comprises suitable hardware, firmware, software, control logic, or a combination thereof for implementing a plurality of functional components, including an interface and a processing unit.
- the interface of the request handling element 51 is adapted to receive and send data (e.g., in the form of messages) from and to servers, other computers and/or other elements (e.g., databases).
- the processing unit of the request handing element 51 is adapted to effect various processing operations to implement that element's functionality.
- the request handling element 51 may be part of the server 30 n .
- the online request is a request for an access to online private content that is provided by the server 30 n , a request for a download of data that is provided by the server 30 n , or a request for a delivery of a product or service offered on the network site implemented by the server 30 n .
- the request handling element 51 may have access to a database 53 . More particularly, depending on the nature of the online request made by the user 10 , upon processing the request-related information provided by the user 10 via the communication apparatus 12 , the request handling element 51 may determine that this information matches information included in a record (not shown) that is contained in the database 53 . In such cases, the record is associated with a party (who may or may not be the user 10 ) having a relationship with the entity operating, managing or otherwise associated with the request handling element 51 . For example, the record may be a profile or other account associated with the party. The record may include personal information regarding the party.
- this personal information may include a name, a gender, a date of birth or an age, a nationality, a correspondence language, a civic address (e.g., a residential or work address), a phone number (e.g., a residential, work, Voice-over-Internet Protocol (VoIP), or mobile phone number), an email address, and/or an instant messaging (IM) identifier of the party.
- a civic address e.g., a residential or work address
- a phone number e.g., a residential, work, Voice-over-Internet Protocol (VoIP), or mobile phone number
- VoIP Voice-over-Internet Protocol
- IM instant messaging
- Other personal information regarding the party may be included in the record.
- the party may be more than one person, in which cases the record may include personal information regarding each such person.
- the personal information regarding the party may be included in the record as a result of interaction between the party and the entity operating, managing or otherwise associated with the request handling element 51 (e.g., during a
- Specific contents of the database 53 will depend on the nature of the online request made by the user 10 and the functionality of the request handling element 51 . A specific example of potential contents of the database 53 will be considered later on.
- the request handling element 51 may use the personal information included in the record that is contained in the database 53 and that includes information matching the request-related information, in order to handle the online request made by the user 10 .
- the personal information included in the record that is contained in the database 53 can also be viewed as information related to the online request.
- the request handling element 51 and the database 53 may be part of separate network elements and communicatively coupled to one another via a communication link, which may traverse one or more network elements and comprise one or more physical links and one or more logical links.
- the request handling element 51 and the database 53 may be part of a common network element.
- the database 53 may be distributed amongst a plurality of network elements and/or physical locations.
- a network element 34 hereinafter referred to as a “profile information server”, which can interact with the request handling element 51 as part of a process to handle the online request made by the user 10 using the communication apparatus 12 .
- the profile information server 34 allows information pertaining to a profile that is associated with the logical identifier assigned to the communication apparatus 12 to be used in order to handle the online request made by the user 10 using the communication apparatus 12 .
- the communication link 61 may be established over a network 63 , which may comprise part of the public packet-switched network 14 , a financial network and/or another network, and may traverse one or more network elements and comprise one or more physical links and one or more logical links.
- the communication link 61 may be a dedicated and secure link established between the profile information server 34 and the request handling element 51 . It will be recognized that the communication link 61 may be implemented in various manners in different embodiments.
- the profile information server 34 has access to a profile information database 36 .
- the profile information server 34 and the profile information database 36 may be part of separate network elements and communicatively coupled to one another via a communication link, which may traverse one or more network elements and comprise one or more physical links and one or more logical links.
- the profile information server 34 and the profile information database 36 may be part of a common network element.
- the profile information database 36 may be distributed amongst a plurality of network elements and/or physical locations.
- the profile information database 36 stores a plurality of records 40 1 . . . 40 M .
- Each of the records 40 1 . . . 40 M associates a profile to a logical identifier assigned to a communication apparatus (such as the logical identifier assigned to the communication apparatus 12 ).
- the profile in a record 40 m (1 ⁇ m ⁇ M) includes information known to a service provider involved in assigning the logical identifier that is associated with that profile.
- the service provider may be an access service provider (ASP, also sometimes called a regional access network provider (RANP)) that may or may not be an internet service provider (ISP).
- ASP access service provider
- RTP regional access network provider
- ISP internet service provider
- the information in the record 40 m may include:
- a profile that is associated with a given logical identifier assigned to a communication apparatus can include any information known to a service provider involved in assigning the given logical identifier to the communication apparatus.
- the profile information database 36 may be populated.
- the profile information database 36 stores the records 40 1 . . . 40 M that associate profiles to logical identifiers.
- the profile information server 34 is operative to use information included in the profile information database 36 as part of its interaction with the request handling element 51 in order to handle the online request made by the user 10 using the communication apparatus 12 .
- the profile information server 34 comprises suitable hardware, firmware, software, control logic, or a combination thereof for implementing a plurality of functional components, including an interface and a processing unit.
- the interface of the profile information server 34 is adapted to receive and send data (e.g., in the form of messages) from and to the request handling element 51 , and possibly other servers, computers and/or other elements (e.g., databases) communicatively coupled to the profile information server 34 via communication links (not shown) that may be established over the public packet-switched network 14 and/or another network and that may traverse one or more network elements and comprise one or more physical links and one or more logical links.
- the processing unit of the profile information server 34 is adapted to effect various processing operations to implement that server's functionality.
- the profile information server 34 Operation of the profile information server 34 , its interaction with the request handling element 51 , as well as operation of other network elements, will now be illustrated in the context of an example where the online request made by the user 10 using the communication apparatus 10 is a request for an online transaction. More particularly, in this example, it is assumed that the user 10 , while interacting with the network site implemented by the server 30 n , makes a request to purchase a product or service offered on the network site using a particular credit card. Accordingly, for purposes of this example, and with reference to FIG. 3A , the request handling element 51 is a transaction validation server associated with a card issuing bank, i.e., a financial institution that issued the particular credit card used by the user 10 .
- a card issuing bank i.e., a financial institution that issued the particular credit card used by the user 10 .
- the transaction validation server 51 has access to the aforementioned database 53 .
- the database 53 stores a plurality of records 57 1 . . . 57 P .
- each of the records 57 1 . . . 57 P is associated with a credit card and includes information regarding that credit card (i.e., credit card information).
- a record 57 p (1 ⁇ p ⁇ P) also includes personal information regarding a party to which has been issued the credit card associated with that record.
- this personal information may include a name, a gender, a date of birth or an age, a nationality, a correspondence language, a civic address (e.g., a residential or work address), a phone number (e.g., a residential, work, or mobile phone number), and/or an email address of the party.
- Other personal information regarding the party may be included.
- the party may be more than one person, in which cases the record 57 p may include personal information regarding each such person.
- the personal information regarding the party may be included in the record 57 p as a result of interaction between the party and the card issuing bank (e.g., when the party requests to obtain the credit card in question).
- Each of the records 57 1 . . . 57 P also includes additional information used to process an online transaction attempted to be made using the credit card associated with that record. For instance, this additional information may include a credit limit, a balance due, a list of recent transactions, etc.
- the user 10 interacts with the network site implemented by the server 30 n using the computing device 16 of the communication apparatus 12 in order to select the product or service that he/she desires to purchase. This may involve the user 10 using an online shopping cart implemented by the server 30 n . Upon selecting the desired product or service, the user 10 indicates that he/she desires to purchase that product or service, for instance, by selecting a “check-out” option on the network site.
- the network site then prompts the user 10 to provide payment information to pay for the selected product or service.
- the user 10 thus proceeds to enter credit card information (e.g., a card number, an expiry date, and/or a cardholder's name) regarding the particular credit card.
- the user 10 indicates his/her intent to submit an order to purchase the selected product or service using the entered credit card information, for instance, by selecting a “submit order” option on the network site.
- the computing device 16 of the communication apparatus 12 transmits to the server 30 n a message 102 .
- the message 102 conveys (i) order information indicative of the selected product or service; (ii) purchase amount information indicative of an amount to be paid to purchase the selected product or service; and (iii) the credit card information entered by the user 10 to purchase the selected product or service.
- the message 102 may also convey the logical identifier assigned to the communication apparatus 12 .
- the logical identifier assigned to the communication apparatus 12 may not be conveyed by the message 102 but may already be known to the server 30 n due to prior interaction between the computing device 16 and the server 30 n .
- the information to be transmitted to the server 30 n as part of the message 102 may be encrypted by the computing device 16 prior to being transmitted to the server 30 n .
- This encryption may be effected using the Secure Socket Layer (SSL) protocol or some other encryption technique, by virtue of interaction between the computing device 16 and the server 30 n .
- SSL Secure Socket Layer
- the server 30 n Upon receiving the message 102 , the server 30 n processes the message 102 , possibly decrypting one or more of its portions, and proceeds to send a message 104 to a payment gateway 60 .
- the payment gateway 60 is a network element that is connected to a financial network 68 and that is used by the server 30 n to process online transactions attempted to be made via the network site implemented by the server 30 n .
- the financial network 68 interconnects a plurality of servers or other computers associated with banks and/or other financial institutions, including, in this example, the transaction validation server 51 that is associated with the card issuing bank and a server 70 that is associated with an acquiring bank, i.e., a financial institution that is used by an entity, in this case, a merchant, which operates, manages or is otherwise associated with the server 30 n .
- the transaction validation server 51 that is associated with the card issuing bank
- a server 70 that is associated with an acquiring bank, i.e., a financial institution that is used by an entity, in this case, a merchant, which operates, manages or is otherwise associated with the server 30 n .
- the message 104 sent to the payment gateway 60 may be identical to the message 102 , i.e., it may be a relayed version of the message 102 .
- the message 104 may be generated by the server 30 n based on the message 102 and possibly other information known to the server 30 n (e.g., the logical identifier assigned to the communication apparatus 12 , if not conveyed by the message 102 but already known to the server 30 n ).
- the message 104 conveys (i) the purchase amount information indicative of an amount to be paid to purchase the selected product or service; (ii) the credit card information entered by the user 10 to purchase the selected product or service; and (iii) the logical identifier assigned to the communication apparatus 12 .
- information conveyed by the message 104 may be encrypted prior to transmission to the payment gateway 60 .
- the payment gateway 60 Upon receiving the message 104 , the payment gateway 60 processes the message 104 , possibly decrypting one or more of its portions. Based on content of the message 104 , the payment gateway 60 determines that it originates from the server 30 n and proceeds to send a message 106 , over the financial network 68 , to the server 70 , which is associated with the acquiring bank used by the merchant associated with the server 30 n .
- the message 106 which can be viewed as a request for transaction authorization, is intended to elicit from the financial network 68 a response as to whether the online transaction requested by the user 10 is approved or denied.
- the payment gateway 60 generates the message 106 based on the message 104 such that the message 106 conveys (i) the purchase amount information indicative of an amount to be paid to purchase the selected product or service; (ii) the credit card information entered by the user 10 to purchase the selected product or service; and (iii) the logical identifier assigned to the communication apparatus 12 .
- the server 70 receives the message 106 and processes it to gain knowledge that a transaction involving the merchant associated with the server 30 n is attempted to be effected. Based on the credit card information conveyed by the message 106 , the server 70 proceeds to send a message 108 to the transaction validation server 51 over the financial network 68 .
- the message 108 may be identical to the message 106 , i.e., it may be a relayed version of the message 106 . Alternatively, the message 108 may be generated by the server 70 based on the message 106 and possibly other information known to the server 70 .
- the message 108 conveys (i) the purchase amount information indicative of an amount to be paid to purchase the selected product or service; (ii) the credit card information entered by the user 10 to purchase the selected product or service; and (iii) the logical identifier assigned to the communication apparatus 12 .
- the transaction validation server 51 which is associated with the card issuing bank that issued the particular credit card that has been used by the user 10 in making the request to purchase the selected product or service, receives the message 108 .
- the transaction validation server 51 proceeds to process the message 108 to determine whether the online transaction requested by the user 10 is to be approved or denied.
- the transaction validation server 51 uses personal information regarding a party to which has been issued the particular credit card used by the user 10 in order to determine whether the online transaction requested by the user 10 is to be approved or denied.
- the transaction validation server 51 consults the database 53 to identify a particular one of the records 57 1 . . . 57 P that includes information matching the credit card information conveyed by the message 108 . Upon identifying the particular one of the records 57 1 . . . 57 P , the transaction validation server 51 obtains therefrom personal information regarding a party to which has been issued the particular credit card associated with that particular record. Specifically, the transaction validation server 51 obtains one or more elements (e.g., a name, a phone number, a civic address, and/or an email address) of the personal information included in the particular one of the records 57 1 . . . 57 P .
- elements e.g., a name, a phone number, a civic address, and/or an email address
- the transaction validation server 51 obtains from the particular one of the records 57 1 . . . 57 P a name of the party to which has been issued the particular credit card used by the user 10 and associated with that particular record. It will be appreciated that, in other examples, various other elements of the personal information included in the particular one of the records 57 1 . . . 57 P may be obtained by the transaction validation server 51 and used in determining whether the online transaction requested by the user 10 is to be approved or denied.
- the personal information used by the transaction validation server 51 in determining whether the online transaction requested by the user 10 is to be approved or denied may be obtained by the transaction validation server 51 directly from the credit card information entered by the user 10 and conveyed by the message 108 .
- the credit card information entered by the user 10 and conveyed by the message 108 may include a cardholder's name appearing on the particular credit card (i.e., the name of the party to which has been issued the particular credit card), in which cases this name may be obtained by the transaction validation server 51 directly from the message 108 , rather than being obtained from the particular one of the records 57 1 . . . 57 P .
- the transaction validation server 51 effects a verification as to whether the name of the party to which has been issued the particular credit card used by the user 10 corresponds to a name included in a profile associated to the logical identifier assigned to the communication apparatus 12 used by the user 10 .
- the transaction validation server 51 interacts with the profile information server 34 to effect this verification on a basis of the logical identifier assigned to the communication apparatus 12 and conveyed by the message 108 .
- the transaction validation server 51 sends a message 110 to the profile information server 34 over the communication link 61 .
- the message 110 can be viewed as a request to confirm whether the logical identifier assigned to the communication apparatus 12 (and conveyed by the message 108 ) is associated with a profile which includes a name that corresponds to name of the party to which has been issued the particular credit card used by the user 10 (i.e., the name obtained from the particular one of the records 57 1 . . . 57 P ).
- the message 110 thus conveys the logical identifier assigned to the communication apparatus 12 and the name of the party to which has been issued the particular credit card used by the user 10 .
- the profile information server 34 receives the message 110 and proceeds to process it. More particularly, in this embodiment, the profile information server 34 extracts the logical identifier assigned to the communication apparatus 12 and conveyed by the message 110 , and consults the profile information database 36 in an attempt to find a particular one of the records 40 1 . . . 40 M that corresponds to this logical identifier.
- the profile information server 34 may send to the transaction validation server 51 a message (not shown) indicating that no profile associated with this logical identifier, and thus no name included in such profile, can be found.
- the transaction validation server 51 may take remedial action. For example, the transaction validation server 51 may deny the online transaction attempted to be made using the communication apparatus 12 without performing any further processing operation to assess whether it should be approved or denied.
- the transaction validation server 51 may perform additional processing operations to determine whether the online transaction requested by the user 10 is to be approved or denied, including processing operations to re-assess legitimacy of the online transaction requested by the user 10 , i.e., to probe more deeply into whether the user 10 legitimately used the credit card information conveyed by the message 108 .
- these additional processing operations may effect conventional verifications, such as a card security code (CSC) verification whereby the user 10 is asked to enter the particular credit card's CSC; an address verification system (AVS) whereby the user 10 is asked to enter a billing address for the particular credit card which is compared to an actual billing address known to the card issuing bank; a phone call to a party to which the card issuing bank issued the particular credit card to verbally confirm legitimacy of the online transaction requested by the user 10 , etc.
- CSC card security code
- AVS address verification system
- the profile information server 34 finds the particular one of the records 40 1 . . . 40 M , which associates the logical identifier assigned to the communication apparatus 12 (and conveyed by the message 110 ) to a profile including information known to a service provider involved in assigning the logical identifier to the communication apparatus 12 .
- This information includes personal information regarding a party to which the service provider provides a network access service. In this case, this personal information includes a name of the party to which the service provider provides a network access service.
- the profile information server 34 obtains from the particular one of the records 40 1 . . . 40 M the name of the party to which the service provider provides a network access service.
- the profile information server 34 proceeds to compare the name of the party to which the service provider provides a network access service (obtained from the particular one of the records 40 1 . . . 40 M ) to the name of the party to Which has been issued the particular credit card used by the user 10 (conveyed by the message 110 ). Based on a result of this comparison, the profile information server 34 performs an action related to validation of the online transaction requested by the user 10 using the communication apparatus 12 . More specifically, in this embodiment, the action performed by the profile information server 34 comprises generating and transmitting to the transaction validation server 51 a message 112 that indicates whether the name of the party to which the service provider provides a network access service (obtained from the particular one of the records 40 1 . . .
- the transaction validation server 51 receives the message 112 and processes it to learn whether the name of the party to which the service provider provides a network access service (obtained from the particular one of the records 40 1 . . . 40 M ) corresponds to the name of the party to which has been issued the particular credit card used by the user 10 (conveyed by the message 110 ). As discussed below, the transaction validation server 51 handles the request for the online transaction made by the user 10 in different manners depending on whether the name of the party to which the service provider provides a network access service (obtained from the particular one of the records 40 1 . . . 40 M ) corresponds to or does not correspond to the name of the party to which has been issued the particular credit card used by the user 10 (conveyed by the message 110 ).
- the transaction validation server 51 concludes based on the message 112 that legitimacy of the request for the online transaction made by the user 10 is not established. This may result in the online transaction being denied by the transaction validation server 51 without performing any further processing operation to assess whether it should be approved or denied.
- this may result in the transaction validation server 51 performing additional processing operations to determine whether the online transaction requested by the user 10 is to be approved or denied, including processing operations to re-assess legitimacy of the request for the online transaction made by the user 10 , i.e., to probe more deeply into whether the user 10 legitimately used the credit card information conveyed by the message 108 .
- these additional processing operations may effect conventional verifications, such as a card security code (CSC) verification, an address verification system (AVS), a phone call to verbally confirm legitimacy of the online transaction requested by the user 10 , etc.
- CSC card security code
- AVS address verification system
- the transaction validation server 51 concludes based on the message 112 that legitimacy of the request for the online transaction made by the user 10 is established. In other words, the transaction validation server 51 concludes based on the message 112 that the request for the online transaction made by the user 10 is legitimate, i.e., that the user 10 legitimately used the credit card information entered at step 200 and conveyed in the message 108 .
- the transaction validation server 51 proceeds to perform other processing operations to determine whether the online transaction requested by the user 10 is to be approved or denied. Approval or denial of the online transaction can be determined based on various factors. For example, based on the additional information (e.g., a credit limit, a balance due, etc.) included in the particular one of the records 57 1 . . . 57 P and the purchase amount information indicative of an amount to be paid to purchase the selected product or service that is conveyed by the message 108 , the transaction validation server 51 may determine whether the online transaction is to be approved or denied. It will be appreciated that approval or denial of the online transaction may be determined by the transaction validation server 51 based on other factors.
- additional information e.g., a credit limit, a balance due, etc.
- the transaction validation server 51 may determine whether the online transaction is to be approved or denied. It will be appreciated that approval or denial of the online transaction may be determined by the transaction validation server 51 based on other factors.
- the transaction validation server 51 Upon determining whether the online transaction is approved or denied, the transaction validation server 51 sends a message 114 to the server 70 over the financial network 68 .
- the message 114 indicates whether the online transaction is approved or denied. If the online transaction is denied, the message 114 may indicate (e.g., by a code) a reason for this denial, such as insufficient funds, an unavailable bank link, etc.
- the server 70 receives the message 114 and processes it to know whether the online transaction is approved or denied. If approved, the online transaction is eventually settled via a settlement process involving the acquiring bank and the card issuing bank. This settlement process is well known and thus not described herein.
- the server 70 proceeds to send a message 116 to the payment gateway 60 .
- the message 116 may be identical to the message 114 , i.e., it may be a relayed version of the message 114 .
- the message 116 may be generated by the server 70 based on the message 114 .
- the message 116 indicates whether the online transaction is approved or denied and, if applicable, may indicate a reason for denial of the online transaction.
- the payment gateway 60 Upon receiving the message 116 , the payment gateway 60 processes it and proceeds to send a message 118 to the server 30 n . Generated by the payment gateway 60 on a basis of the message 116 , the message 118 indicates whether the online transaction is approved or denied and, if applicable, may indicate a reason for denial of the online transaction. Information conveyed by the message 118 may be encrypted by the payment gateway 60 prior to being transmitted to the server 30 n .
- the server 30 n receives the message 118 .
- the server 30 n processes the message 118 , possibly decrypting one or more of its portions, to ascertain whether the online transaction is approved or denied. Approval or denial of the online transaction (and a reason for denial, if applicable) may be recorded by the server 30 n for future reference.
- the server 30 n proceeds to send a message 120 to the computing device 16 of the communication apparatus 12 in order to communicate approval or denial of the online transaction to the user 10 . Since it travels over the public packet-switched network 14 , information conveyed by the message 120 may be encrypted by the server 30 n prior to being transmitted to the computing device 16 .
- the computing device 16 Upon receiving the message 120 , the computing device 16 processes the message 120 , possibly decrypting one or more of its portions, so as to communicate approval or denial of the online transaction to the user 10 . For example, this may be achieved by displaying a “transaction approved” or “transaction denied” message (or any conceivable variant thereof) on the display of the computing device 16 .
- validation of the online transaction requested by the user 10 can be effected using information known to the service provider involved in assigning the logical identifier to the communication apparatus. This enables the transaction validation server 51 to conveniently and efficiently establish legitimacy of the request for the online transaction made by the user 10 in a way that is transparent to the user 10 .
- FIG. 3C illustrates one possible variant.
- messages have been exchanged as described above in connection with FIG. 3A , leading up to receipt of the message 108 by the transaction validation server 51 , which proceeds to process the message 108 to determine whether the online transaction requested by the user 10 is to be approved or denied.
- the transaction validation server 51 sends a message 110 * to the profile information server 34 over the communication link 61 .
- the message 110 * can be viewed as a request to obtain a name included in a profile that is associated with the logical identifier assigned to the communication apparatus 12 (and conveyed by the message 108 ).
- the message 110 * thus conveys the logical identifier assigned to the communication apparatus 12 .
- the profile information server 34 receives the message 110 * and proceeds to process it. More particularly, in this embodiment, the profile information server 34 extracts the logical identifier assigned to the communication apparatus 12 and conveyed by the message 110 *, and consults the profile information database 36 in an attempt to find a particular one of the records 40 1 . . . 40 M that corresponds to this logical identifier.
- the profile information server 34 may send to the transaction validation server 51 a message (not shown) indicating that no profile associated with this logical identifier, and thus no name included in such profile, can be found.
- the transaction validation server 51 may take remedial action. For example, the transaction validation server 51 may deny the online transaction attempted to be made using the communication apparatus 12 without performing any further processing operation to assess whether it should be approved or denied.
- the transaction validation server 51 may perform additional processing operations to determine whether the online transaction requested by the user 10 is to be approved or denied, including processing operations to re-assess legitimacy of the online transaction requested by the user 10 , i.e., to probe more deeply into whether the user 10 legitimately used the credit card information conveyed by the message 108 .
- these additional processing operations may effect conventional verifications, such as a card security code (CSC) verification whereby the user 10 is asked to enter the particular credit card's CSC; an address verification system (AVS) whereby the user 10 is asked to enter a billing address for the particular credit card which is compared to an actual billing address known to the card issuing bank; a phone call to a party to which the card issuing bank issued the particular credit card to verbally confirm legitimacy of the online transaction requested by the user 10 , etc.
- CSC card security code
- AVS address verification system
- the profile information server 34 finds the particular one of the records 40 1 . . . 40 M , which associates the logical identifier assigned to the communication apparatus 12 (and conveyed by the message 110 *) to a profile including information known to a service provider involved in assigning the logical identifier to the communication apparatus 12 .
- This information includes personal information regarding a party to which the service provider provides a network access service. In this case, this personal information includes a name of the party to which the service provider provides a network access service.
- the profile information server 34 thus obtains from the particular one of the records 40 1 . . . 40 M the name of the party to which the service provider provides a network access service.
- the profile information server 34 proceeds to perform an action related to validation of the online transaction requested by the user 10 using the communication apparatus 12 .
- the action performed by the profile information server 34 comprises generating and transmitting to the transaction validation server 51 a message 112 * that conveys the name obtained from the particular one of the records 40 1 . . . 40 M , i.e., the name of the party to which the service provider provides a network access service.
- This action is related to validation of the online transaction requested by the user 10 since the message 112 * will be used by the transaction validation server 51 to validate the online transaction, as discussed below.
- the transaction validation server 51 receives the message 112 * and processes it. More particularly, the transaction validation server 51 compares the name of the party to which the service provider provides a network access service (obtained from the particular one of the records 40 1 . . . 40 M of the database 36 ) to the name of the party to which has been issued the particular credit card used by the user 10 (obtained from the particular one of the records 57 1 . . . 57 P of the database 53 at step 240 ). Based on a result of this comparison, the transaction validation server 51 performs an action related to validation of the online transaction requested by the user 10 using the communication apparatus 12 . More specifically, in this embodiment, the action performed by the transaction validation server 51 comprises validating the online transaction requested by the user 10 in different manners depending on a result of this comparison.
- the transaction validation server 51 concludes that legitimacy of the request for the online transaction made by the user 10 is not established. This may result in the online transaction being denied by the transaction validation server 51 without performing any further processing operation to assess whether it should be approved or denied.
- this may result in the transaction validation server 51 performing additional processing operations to determine whether the online transaction requested by the user 10 is to be approved or denied, including processing operations to re-assess legitimacy of the request for the online transaction made by the user 10 , i.e., to probe more deeply into whether the user 10 legitimately used the credit card information entered at step 200 and conveyed in the message 108 .
- these additional processing operations may effect conventional verifications, such as a card security code (CSC) verification, an address verification system (AVS), a phone call to verbally confirm legitimacy of the online transaction requested by the user 10 , etc.
- CSC card security code
- AVS address verification system
- the transaction validation server 51 concludes that legitimacy of the request for the online transaction made by the user 10 is established. In other words, the transaction validation server 51 concludes that the request for the online transaction made by the user 10 is legitimate, i.e., that the user 10 legitimately used the credit card information entered at step 200 and conveyed in the message 108 .
- the transaction validation server 51 proceeds to perform other processing operations to determine whether the online transaction requested by the user 10 is to be approved or denied. Approval or denial of the online transaction can be determined based on various factors. For example, based on the additional information (e.g., a credit limit, a balance due, etc.) included in the particular one of the records 57 1 . . . 57 P and the purchase amount information indicative of an amount to be paid to purchase the selected product or service that is conveyed by the message 108 , the transaction validation server 51 may determine whether the online transaction is to be approved or denied. It will be appreciated that approval or denial of the online transaction may be determined by the transaction validation server 51 based on other factors.
- additional information e.g., a credit limit, a balance due, etc.
- the transaction validation server 51 may determine whether the online transaction is to be approved or denied. It will be appreciated that approval or denial of the online transaction may be determined by the transaction validation server 51 based on other factors.
- the transaction validation server 51 Upon determining whether the online transaction is approved or denied, the transaction validation server 51 sends the message 114 to the server 70 over the financial network 68 , as described above in connection with FIG. 3B . This variant then continues as described above in connection with FIG. 3B .
- the online request made using the communication apparatus 12 is a request for an online transaction
- principles described herein apply to other types of online requests, including a request for a delivery of a product or service to a particular place, a request for an access to online private content, a request for an access to a private network, a request for a download of data, or any other request that can be made online.
- the online request made using the communication apparatus 12 is handled on a basis of a name known to a service provider involved in assigning the logical identifier to the communication apparatus 12
- other information known to the service provider and part of the profile associated with this logical identifier may be used in other cases, depending on the nature of the online request being made.
- a civic address known to the service provider may be used to handle the requested delivery
- a bandwidth known to the service provider to be available to the communication apparatus 12 may be used to handle the requested download of data; etc.
- the transaction validation server 51 interacts with the profile information server 34
- other network elements may interact with the profile information server 34 as part of a process to handle an online request made by the user 10 via the communication apparatus 12 .
- the payment gateway 60 , the server 70 , the server 30 n or any other network element may interact with the profile information server 34 as part of a process to handle an online request made by the user 10 via the communication apparatus 12 .
- the profile information database 36 stores the records 40 1 . . . 40 M that associate logical identifiers to profiles which include information known to one or more service providers involved in assigning these logical identifiers.
- This example will illustrate one possible manner by which an association between the logical identifier assigned to the communication apparatus 12 and a profile including information known to a service provider involved in assigning the logical identifier to the communication apparatus 12 , may be stored in the profile information database 36 as part of one of the records 40 1 . . . 40 M .
- a given service provider owning, managing or otherwise associated with one or more network elements of the communication link 20 connecting the communication apparatus 12 to the public packet-switched network 14 provides a network access service to a given party (who may or may not be the user 10 ) occupying, owning, managing or otherwise associated with premises where the communication apparatus 12 is located.
- the given party has a business relationship with the given service provider. As part of this business relationship, the given party interacts with the given service provider (e.g., during a registration or service activation phase) to provide personal information regarding itself.
- this personal information may include a name, a gender, a date of birth or an age, a nationality, a correspondence language, a civic address (e.g., a residential or work address), a phone number (e.g., a residential, work, VoIP or mobile phone number), an email address, and/or an IM identifier of the given party. If the given party is more than one person, personal information regarding each such person may be provided.
- the given party also indicates a service point location (e.g., a service address) where the network access service is to be delivered, selects a level of service to be obtained, provides billing information (e.g., a billing address and/or credit card information) to pay for the network access service, etc.
- a service point location e.g., a service address
- billing information e.g., a billing address and/or credit card information
- the given service provider stores in the profile information database 36 a profile associated with the given party, in which is included information provided by the given party while interacting with the given service provider and possibly other information not obtained from the given party but pertaining to the network access service provided to the given party.
- the infrastructure described above in connection with FIG. 1 and partly shown in FIG. 5 comprises an operation support system (OSS) 122 .
- the OSS 122 represents a collection of systems that perform management, inventory, engineering, planning, repair and other functions for the given service provider.
- one of the functions of the OSS 122 may include management of network elements, assets and equipment.
- the OSS 122 maintains a mapping 124 between, on the one hand, ports of various access multiplexers or other network elements under control of the given service provider and, on the other, service point locations of communication apparatus (such as the communication apparatus 12 ) connected to those ports.
- the mapping 124 maintained by the OSS 122 relates a port 104 of the network element 21 to a service point location, i.e., the location of a service point where the communication apparatus 12 is located.
- this service point location may be expressed as a civic address, a set of geo-coordinates, or any other information identifying where the service point is located.
- the network element 21 of the communication link 20 connecting the communication apparatus 12 to the public packet-switched network 14 is an access multiplexer under control of the given service provider.
- the access multiplexer 21 may be a DSLAM.
- the access multiplexer 21 is connected to the network element 23 , which, in this embodiment, is a network access server (NAS) operated by the given service provider.
- the NAS 23 which may also sometimes be referred to as a broadband remote access server (BRAS), a remote access server (RAS) or a broadband access server (BAS), provides access to the public packet-switched network 14 .
- Communication between the access multiplexer 21 and the NAS 23 can take place over the dedicated logical link 19 between these elements.
- the dedicated logical link 19 which may traverse an intervening access data network (not shown), can be implemented in various ways.
- the dedicated logical link 19 may be implemented as an asynchronous transfer mode (ATM) permanent virtual circuit (PVC).
- the dedicated logical link 19 may be implemented as a virtual local area network (VLAN). It will be appreciated that various other implementations of the dedicated logical link 19 are possible.
- the access multiplexer 21 allows data arriving from the NAS 23 along given ATM PVCs, VLANs or other dedicated logical links to be sent over corresponding physical links via corresponding one of its ports, and vice versa.
- the access multiplexer 21 can be said to implement a mapping 134 between, on the one hand, dedicated logical links and, on the other, ports of the access multiplexer 21 .
- the mapping 134 implemented by the access multiplexer 21 relates the dedicated logical link 19 to the port 104 of the access multiplexer 21 .
- the mapping 134 can be maintained by either the access multiplexer 21 or the OSS 122 .
- the infrastructure shown in FIG. 5 further comprises an authorization element 142 connected to the NAS 23 .
- the authorization element 142 may be a server (e.g., an Authentication, Authorization, and Accounting (AAA) server) responsive to queries from the NAS 23 .
- AAA Authentication, Authorization, and Accounting
- the authorization element 142 and the NAS 23 may communicate using the Remote Authentication Dial In User Service (RADIUS) protocol, a description of which is available at www.ietf.org/rfc/rfc2865.txt.
- the authorization element 142 may be a functional element integrated with the NAS 23 .
- the NAS 23 is operative to maintain a pool 127 of logical identifiers that can be used by various communication apparatus, including the communication apparatus 12 .
- the pool 127 of addresses may be built up as a cooperative effort between the NAS 23 and the OSS 122 , while in other embodiments, it may not be necessary for the OSS 122 to be involved in creating the pool 127 of logical identifiers.
- the pool 127 of logical identifiers may be maintained by the authorization element 142 , and may be made accessible to the authorization element 142 without needing to pass through the NAS 23 .
- the profile information server 34 and the profile information database 36 that it has access to, can be linked to other components of the infrastructure of FIG. 5 in various ways.
- the profile information server 34 may be connected to the NAS 23 by a link 175 .
- the profile information server 34 may be connected to the authorization element 142 by a link 177 .
- the nature of the connection between the profile information server 34 and either the NAS 23 or the authorization element 142 is immaterial.
- the profile information server 34 may be part of either the OSS 122 , the NAS 23 or the authorization element 142 .
- the profile information server 34 and the profile information database 36 may be part of separate network elements and communicatively coupled to one another via a communication link, which may traverse one or more network elements and comprise one or more physical links and one or more logical links.
- the profile information server 34 and the profile information database 36 may be part of a common network element.
- the profile information database 36 may be distributed amongst a plurality of network elements and/or physical locations. Also, it should be appreciated that the profile information database 36 may be managed, maintained and/or updated by an entity that may be the given service provider or a different entity.
- the access multiplexer 21 can be omitted. This may be true in embodiments where the communication apparatus 12 implements a wireless access point.
- the connection between the wireless access point and the NAS 23 may be provided by a dedicated point-to-point link.
- the dedicated logical link 19 instead of the dedicated logical link 19 , there may be a shared link leading to the communication apparatus 12 .
- FIG. 6 illustrates an example of a possible event flow upon activation of the communication apparatus 12 , which may occur, for instance, as the network interface unit 18 and/or the computing device 16 of the communication apparatus 12 is/are powered up. Thereafter:
- the NAS 23 assigns the logical identifier 193 to the dedicated logical link 19 .
- the fact that the NAS 23 assigns the logical identifier 193 to the dedicated logical link 19 allows the NAS 23 to construct and maintain a mapping 144 between, on the one hand, various dedicated logical links (such as the dedicated logical link 19 and others) and, on the other, logical identifieres corresponding to those dedicated logical links.
- the logical identifier 193 and the identity of the dedicated logical link 193 to which it is assigned are sent back by the NAS 23 to the authorization element 142 , and it is the authorization element 142 that maintains the aforementioned mapping 144 between dedicated logical links and logical identifieres corresponding to those dedicated logical links.
- mappings 124 , 134 maintained in the OSS 122 and/or the access multiplexer 21 and the mapping 144 maintained in the NAS 23 or the authorization element 142 the following describes how one can create an association between logical identifieres and service point locations.
- the OSS 122 can create an intermediate mapping 166 between, on the one hand, dedicated logical links and, on the other hand, service point locations of communication apparatus having logical connections with the NAS 23 which traverse those dedicated logical links.
- the intermediate mapping 166 would associate the dedicated logical link 19 to the service point location of the communication apparatus 12 .
- the OSS 122 transmits the intermediate mapping 166 to the profile information server 34 .
- the profile information server 34 may be operative to combine the intermediate mapping 166 (received from the OSS 122 ) with the aforementioned mapping 144 (received from the NAS 23 or the authorization element 142 ), thus creating a final mapping 176 between, on the one hand, logical identifieres and, on the other, service point locations of communication apparatus having logical connections with the NAS 23 which traverse respective dedicated logical links to which those logical identifieres have been assigned.
- the final mapping 176 would specify that the logical identifier 193 corresponds to the service point location of the communication apparatus 12 , i.e., the location of the service point where the communication apparatus 12 is located.
- the profile associated with the given party and stored in the profile information database 36 by the given service provider includes the service point location where the network access service is to be delivered to the given party.
- the profile information server 34 associates, in the profile information database 36 , the profile associated with the given party to the logical identifier 193 assigned to the communication apparatus 12 .
- the profile information database 36 can be populated with logical identifieres and profiles associated with these logical identifieres.
- the aforementioned credentials which may be hard coded or programmably installed on the communication apparatus 12 or entered by the user 10 of the communication apparatus and which may be included in the access request 184 sent by the communication apparatus 12 to the NAS 23 , can be used to associate the logical identifier 193 assigned to the communication apparatus 12 to the profile associated with the given party and stored in the profile information database 36 .
- these credentials which are known by the service provider to have been provided to the given party, may be linked by the given service provider to the profile associated with the given party.
- the given service provider may associate, in the profile information database 36 , the profile associated with the given party to the logical identifier 193 assigned to the communication apparatus 12 .
- the profile information database 36 may be updated accordingly.
- the communication apparatus 12 may be connected to a router that is connected to the communication link 20 and that may be connected to one or more other communication apparatuses at premises where the communication apparatus 12 is located.
- the router may perform network address translation (NAT) for packets passing therethrough.
- NAT network address translation
- the logical identifier assigned to the communication apparatus 12 may include a portion identifying the router and a portion identifying the communication apparatus 12 connected thereto.
- the logical identifier assigned to the communication apparatus 12 may include an IP address assigned to the router, as well as a port number of a port of the router to which is connected the communication apparatus 12 or a local IP address assigned to the communication apparatus 12 by the router.
- the profile information server 34 interacts with the request handling element 51 using the information included in the particular one of the records 40 1 . . . 40 M in the profile information database 36 without the user 10 being explicitly informed of this fact, in other embodiments there may be mechanisms to notify the user 10 of this fact or confirm with the user 10 that he/she allows this information to be used by the profile information server 34 in its interaction with the request handling element 51 .
- an applet, widget or other suitable element may be implemented to notify the user 10 via the computing device 16 (e.g., via a pop-up window) of the interaction between the profile information server 34 and the request handling element 51 and possibly to allow the user 10 to confirm whether information (or control which information) included in the particular one of the records 40 1 . . . 40 M in the profile information database 36 can be used by the profile information server 34 as part of this interaction.
- the given party (who may or may not be the user 10 ) occupying, owning, managing or otherwise associated with premises where the communication apparatus 12 is located may have previously authorized the service provider providing the network access service to the communication apparatus 12 (e.g., during a registration phase) to use information contained in the particular one of the records 40 1 . . . 40 M as part of a process to handle an online request made via the communication apparatus 12 .
- the user 10 may make an online request during a telephone call established (at least partly) over the public packet-switched network 14 (or a private packet-switched network) and such online request may be handled using principles described herein.
- the communication apparatus 12 may comprise a VoIP phone, a Plain Old Telephone Service (POTS) phone equipped with an analog terminal adapter (ATA), or a soft phone (i.e., a computer equipped with telephony software).
- POTS Plain Old Telephone Service
- ATA analog terminal adapter
- soft phone i.e., a computer equipped with telephony software
- a server operated by the given entity may determine the logical identifier assigned to the communication apparatus 12 (based on packets received during the call) and may use this logical identifier to exchange messages with the profile information server 34 in order to effect verification of the request-related information provided by the user 10 .
- Interaction between the server operated by the given entity and the profile information server 34 may be similar to interaction between the request handling element 51 and the profile information server 34 .
- a given component described herein may be implemented as pre-programmed hardware or firmware elements (e.g., application specific integrated circuits (ASICs), electrically erasable programmable read-only memories (EEPROMs), etc.) or other related elements.
- a given component described herein e.g., the profile information server 34 or the request handling element 51
- the program instructions may be stored on a medium which is fixed, tangible, and readable directly by the given component (e.g., removable diskette, CD-ROM, ROM, fixed disk, USB key, etc.).
- the program instructions may be stored remotely but transmittable to the given component via a modem or other interface device connected to a network over a transmission medium.
- the transmission medium may be either a tangible medium (e.g., optical or analog communications lines) or a medium implemented using wireless techniques (e.g., RF, microwave, infrared or other wireless transmission schemes).
Abstract
Methods and systems for handling online requests based on information known to a service provider. One method may comprise: obtaining first information, the first information relating to an online request made using a communication apparatus; using a logical identifier assigned to the communication apparatus to obtain second information, the second information pertaining to a profile associated with the logical identifier; comparing the first information to the second information; and performing an action related to handling of the online request based on a result of the comparing.
Description
- This application claims the benefit under 35 USC 119(e) of U.S. Provisional Patent Application No. 60/941,830 filed on Jun. 4, 2007 and hereby incorporated by reference herein.
- The present invention relates generally to online requests effected over computer networks such as the Internet and, more particularly, to methods and systems for handling online requests based on information known to a service provider.
- Computer networks such as the Internet allow users to make various online requests. For example, a user can make a request for an online transaction (e.g., a request to purchase a product or service offered on a network site, a request to transfer funds to or from a financial account, etc.); a request for a delivery of a product or service to a particular place (e.g., a request to have food delivered to a house or other building); a request for an access to online private content (e.g., a request to access an online email account); a request for a download of data (e.g., a request to download a video file, an audio file, a software upgrade file, streaming video, streaming audio, etc.); etc.
- In order to handle an online request made by a user, a network element (e.g., a server) processes information related to the online request and provided by the user. For example, where a user makes a request to purchase a product or service offered on a network site using a credit card, a server operated by a card issuing bank that issued the credit card typically processes credit card information (e.g., a card number, an expiry date, and/or a cardholder's name) provided by the user in order to approve or deny the online transaction attempted to be made by the user; where a user makes a request to have a given product or service delivered to a house or other building, a server operated by an entity responsible to effect this delivery typically processes a civic address of the house or other building provided by the user in order to determine where to deliver the product or service; where a user makes a request to access an online email account, a server operated by an entity providing the online email account typically processes a user name and password provided by the user in order to identify and control access to the online email account; etc.
- Handling of an online request made by a user often involves verifying whether information related to the online request and provided by the user has been legitimately used by the user and/or can be trusted. For example, where a user makes a request to purchase a product or service offered on a network site and provides credit card information for this purpose, a verification as to whether the user is legitimately providing the credit card information is typically made in an effort to counter fraudulent online transactions; where a user makes a request to have a given product or service delivered to a house or other building and provides a civic address for this purpose, a verification as to whether the civic address is valid may be made in an effort to avoid delivery to a wrong or invalid address; etc.
- While there are techniques for verifying whether information related to an online request and provided by a user making the online request has been legitimately used by the user and/or can be trusted, these techniques are sometimes inconvenient, cumbersome, and/or ineffective. In particular, existing techniques may be ineffective in situations where the information provided by the user is incorrect; out of date, or susceptible to fraud.
- Accordingly, there remains a need for improvement in verifying whether information related to an online request and provided by a user making the online request has been legitimately used by the user and/or can be trusted.
- As embodied and broadly described herein, the present invention provides a method comprising: obtaining first information, the first information relating to an online request made using a communication apparatus; using a logical identifier assigned to the communication apparatus to obtain second information, the second information pertaining to a profile associated with the logical identifier; comparing the first information to the second information; and performing an action related to handling of the online request based on a result of the comparing.
- The present invention also provides an apparatus comprising an interface for receiving messages and a processing unit coupled to the interface. The processing unit is responsive to receipt of a message at the interface for: obtaining first information, the first information relating to an online request made using a communication apparatus; using a logical identifier assigned to the communication apparatus to obtain second information, the second information pertaining to a profile associated with the logical identifier; comparing the first information to the second information; and performing an action related to handling of the online request based on a result of the comparing.
- The present invention also provides a computer-readable medium storing a program element for execution by a computer. The program element comprises: first program code for causing the computer to obtain first information, the first information relating to an online request made using a communication apparatus; second program code for causing the computer to use a logical identifier assigned to the communication apparatus to obtain second information, the second information pertaining to a profile associated with the logical identifier; third program code for causing the computer to perform a comparison of the first information to the second information; and fourth program code for causing the computer to perform an action related to handling of the online request based on a result of the comparison.
- The present invention also provides a method comprising: receiving a first message conveying a logical identifier; consulting a database on a basis of the logical identifier to obtain information known to a service provider involved in assigning the logical identifier; processing the information to generate a second message to be used in handling an online request made using a communication apparatus to which is assigned the logical identifier; and transmitting the second message.
- The present invention also provides an apparatus comprising an interface for receiving a first message conveying a logical identifier and a processing unit coupled to the interface. The processing unit is operative for: consulting a database on a basis of the logical identifier to obtain information known to a service provider involved in assigning the logical identifier; processing the information to generate a second message to be used in handling an online request made using a communication apparatus to which is assigned the logical identifier; and causing said interface to transmit the second message.
- The present invention also provides a computer-readable medium storing a program element for execution by a computer. The program element comprises: first program code for causing the computer to receive a first message conveying a logical identifier; second program code for causing the computer to consult a database on a basis of the logical identifier to obtain information known to a service provider involved in assigning the logical identifier; third program code for causing the computer to process the information to generate a second message to be used in handling an online request made using a communication apparatus to which is assigned the logical identifier; and fourth program code for causing the computer to transmit the second message.
- These and other aspects of the invention will become apparent to those of ordinary skill in the art upon review of the following description of embodiments of the invention in conjunction with the accompanying drawings.
- A detailed description of embodiments of the present invention is provided herein below, by way of example only, with reference to the accompanying drawings, in which:
-
FIG. 1 shows an architecture allowing a user of a communication apparatus connected to a public packet-switched network to access and interact with network sites of that network, for example, to make online requests, in accordance with an embodiment of the present invention; -
FIG. 2 shows an example of potential contents of a profile information database accessible to a profile information server of the architecture shown inFIG. 1 ; -
FIGS. 3A and 3B illustrate an example of interaction between the profile information server, a transaction validation server and other elements of the architecture shown inFIG. 1 , in an example scenario where the user of the communication apparatus makes a request for an online transaction using a credit card; -
FIG. 3C illustrates a variant to the example considered inFIGS. 3A and 3B ; -
FIG. 4 shows an example of potential contents of a database accessible to the transaction validation server shown inFIGS. 3A and 3B ; and -
FIGS. 5 to 7 illustrate an example process by which the profile information database of the architecture shown inFIG. 1 may be populated, in accordance with an embodiment of the present invention. - It is to be expressly understood that the description and drawings are only for purposes of illustration of example embodiments of the present invention and are an aid for understanding. They are not intended to be a definition of the limits of the invention.
-
FIG. 1 depicts an architecture allowing auser 10 of acommunication apparatus 12 connected to a public packet-switched network 14 (e.g., the Internet) to access and interact with network sites (e.g., web sites) of thenetwork 14, in accordance with an embodiment of the present invention. - In this embodiment, the
communication apparatus 12 comprises acomputing device 16 and anetwork interface unit 18. For example, thecomputing device 16 may be implemented as a personal computer (PC) such as a desktop computer, a laptop computer, or a tablet PC. Thecomputing device 16 is provided with at least one input device such as a keyboard, a mouse, a touchscreen, a stylus, a microphone, etc., as well as a display and possibly one or more other output devices (e.g., speakers) that enable interaction between theuser 10 and thecomputing device 16. Thecomputing device 16 is operative to run a software application implementing a network browser (e.g., a web browser) with which theuser 10 can interact via the display (and possibly one or more other output devices) and the at least one input device in order to access and interact with network sites of the public packet-switchednetwork 14. - The
network interface unit 18 enables thecommunication apparatus 12 to exchange data with the public packet-switchednetwork 14 via acommunication link 20. For example, in various embodiments, and depending on the nature of thecommunication link 20, thenetwork interface unit 18 may be implemented as a modem such as a broadband modem (e.g., a digital subscriber line (DSL) modem or a cable modem) or a narrowband modem (e.g., a dial-up modem). Although it is shown as being a separate component inFIG. 1 , thenetwork interface unit 18 may be integrated into the computing device 16 (e.g., it may be a card internal to the computing device 16). - The
communication link 20 may traverse one or more network elements and comprise one or more physical links and one or more logical links. For example, thecommunication link 20 may comprise aphysical link 17 between thenetwork interface unit 18 and anetwork element 21. Thephysical link 17 may comprise a copper twisted pair, a coax cable, an Ethernet link, a fiber optic link (e.g., fiber to the premises (FTTP)), a fixed wireless link, a satellite link, or a combination thereof. Depending on the nature of thephysical link 17, thenetwork element 21 may be a DSL access multiplexer (DSLAM), a cable modem termination system (CMTS), or another type of network element. Thecommunication link 20 may also comprise a dedicatedlogical link 19 between thenetwork element 21 and anothernetwork element 23 that provides access to the public packet-switchednetwork 14. For instance, thenetwork element 23 may be a network access server (NAS), a router, etc. It will be appreciated that thecommunication link 20 may take on many forms in various embodiments. - While in this embodiment the
communication apparatus 12 comprises thecomputing device 16 and thenetwork interface unit 18, it will be appreciated that thecommunication apparatus 12 may comprise other components in other embodiments. - In order to exchange data with the public packet-switched
network 14, thecommunication apparatus 12 is assigned a logical identifier. The logical identifier, which may be assigned to thecomputing device 16 or thenetwork interface unit 18, may be an Internet Protocol (IP) address (e.g., in compliance with IPv4 or IPv6) or a proprietary address, label or tag. The logical identifier may be statically assigned to thecommunication apparatus 12 in which case it does not change over time (e.g., a static IP address). Alternatively, the logical identifier may be dynamically assigned to thecommunication apparatus 12 in which case it may change over time (e.g., a dynamic IP address). - The logical identifier may be assigned to the
communication apparatus 12 by a network element that is part of the communication link 20 (e.g., thenetwork element 23 in embodiments where it is a network access server). This network element may assign the logical identifier to thecommunication apparatus 12 when thecommunication apparatus 12 is activated (e.g., when thenetwork interface unit 18 and/or thecomputing device 16 is/are powered-up) or otherwise regains network connectivity and/or at certain time intervals which may range from an hour or less to several months or more. For instance, in embodiments where the logical identifier is a dynamic IP address, the network element assigning the dynamic IP address to thecommunication apparatus 12 may do so in accordance with the Dynamic Host Configuration Protocol (DHCP) using a pool of IP addresses accessible to that network element. It will be recognized that assignment of the logical identifier to thecommunication apparatus 12 may be effected in various ways in various embodiments. - As mentioned previously, the
user 10 can use thecommunication apparatus 12 to access and interact with network sites of the public packet-switchednetwork 14. These network sites are implemented by servers 30 1 . . . 30 N connected to the public packet-switchednetwork 14. The servers 30 1 . . . 30 N and the network sites that they implement are operated, managed or otherwise associated with various entities, including, for example, companies, governmental organizations, non-profit organizations, and individuals. - Each of the servers 30 1 . . . 30 N comprises suitable hardware, firmware, software, control logic, or a combination thereof for implementing a plurality of functional components, including an interface and a processing unit. The interface of each of the servers 30 1 . . . 30 N is adapted to receive and send data (e.g., in the form of messages) from and to communication apparatus (such as the communication apparatus 12) connected to the public packet-switched
network 14 as well as other elements (e.g., computers or databases) communicatively coupled to that server but not necessarily connected to the packet-switchednetwork 14. The processing unit of each of the servers 30 1 . . . 30 N is adapted to effect various processing operations to implement that server's functionality. - Interaction of the
user 10 with a network site implemented by a server 30 n (1≦n≦N) typically involves the network browser implemented by thecomputing device 16 interacting with the server 30 n in order to allow theuser 10 to view, hear or otherwise be exposed to content (e.g., web pages) of the network site via the display and/or one or more other output devices of thecomputing device 16, and possibly to input information (e.g., by entering text, selecting an option, etc.) and/or one or more commands (e.g., by clicking on a graphical button or a hyperlink) via the at least one input device of thecomputing device 16. - Occasionally, during his/her interaction with the network site implemented by the server 30 n, the
user 10 may use thecommunication apparatus 12 to make an online request. The online request can be any request made online, i.e., any request made by way of thecommunication apparatus 12 transmitting data over the public packet-switchednetwork 14. The online request can be a request for anything which can be requested online. For example, in various embodiments, the online request may be: -
- a request for an online transaction (e.g., a request to purchase a product or service offered on the network site implemented by the server 30 n; a request to pay a bill for a previously obtained product or service via the network site; a request to transfer funds to or from an account, such as a bank account or an online wallet account, via the network site; a request to buy or sell securities (e.g., stocks, bonds, etc.) via the network site; a request to make a donation to a charity or other institution through the network site; etc.);
- a request for a delivery of a product or service to a particular place (e.g., a request to deliver food to a house or other building, a request to send a cab to a house or other building, etc.);
- a request for an access to online private content (e.g., a request to access an online email account (e.g., a Hotmail® or Gmail® account), an online subscriber account (e.g., a telephone service subscriber account, a television service subscriber account), or any other online content intended to be accessible only to a particular person or group);
- a request for an access to a private network (e.g., a request to access an enterprise's private work from a location outside the enterprise's premises, etc.); or
- a request for a download of data (e.g., a request to download a video file, an audio file, a software upgrade file, streaming video, audio or other media, or any other data downloadable via the network site implemented by the server 30 n).
- These examples are presented for illustrative purposes only and should not be considered limiting in any way since, as mentioned above, the online request can be a request for anything which can be requested online.
- In making the online request while interacting with the network site implemented by the server 30 n the
user 10 provides via thecommunication apparatus 12 information related to the online request. This information, which is hereinafter referred to as “request-related information”, can take on various forms depending on the nature of the online request being made. For example: -
- In embodiments where the online request is a request for an online transaction, the request-related information may be information regarding a transaction object. A “transaction object” refers to any physical or virtual object designed to be used in an attempt to make a transaction. For example, a transaction object may be a payment card (e.g., a credit card, a debit card, etc.), a financial account (e.g., a bank account, an online wallet account, etc.), an electronic check, a set of one or more digital cash (electronic money) certificates, or any other physical or virtual object designed to be used in an attempt to make a transaction. The information regarding the transaction object is hereinafter referred to as “transaction object information” and can take on various forms depending on the nature of the online transaction to be made and the nature of the transaction object itself. In various possible examples, the transaction object information may be:
- payment card information regarding a payment card in situations where, for instance, the
user 10 desires to purchase a product or service offered on the network site implemented by the server 30 n, pay a bill for a previously obtained product or service via the network site, or make a donation to a charity or other institution through the network site, using the payment card. Such payment card information may be, for instance, credit card information regarding a credit card (e.g., a card number, an expiry date, and/or a cardholder's name) or debit card information regarding a debit card (e.g., a card number and/or a cardholder's name); - electronic check information regarding an electronic check (e.g., a check number and/or a checking account number) in situations where, for instance, the
user 10 desires to effect a payment via the network site implemented by the server 30 n using the electronic check; - digital cash information regarding a set of one or more digital cash certificates (e.g., digital cash certificate identifiers) in situations where, for instance, the
user 10 desires to effect a payment via the network site implemented by the server 30 n using the set of one or more digital cash certificates; or - financial account information regarding a financial account (e.g., an account number and/or a holder's name) in situations where, for instance, the
user 10 desires to effect a transfer of funds to or from the financial account via the network site implemented by the server 30 n.
- payment card information regarding a payment card in situations where, for instance, the
- These examples are presented for illustrative purposes only since, as mentioned above, the transaction object information provided by the
user 10 via thecommunication apparatus 12 can take on many different forms depending on the nature of the online transaction to be made and the nature of the transaction object itself. - In embodiments where the online request is a request for a delivery of a product or service to a particular place, the request-related information may be a location where the product or service is to be delivered. For instance, the location may be expressed as a civic address of a house or other building.
- In embodiments where the online request is a request for an access to online private content, the request-related information may be identification and authentication information used to identify and authenticate the
user 10 in order to allow him/her to access the online private content. For instance, the identification and authentication information may include a user name and a password. - In embodiments where the online request is a request for an access to a private network, the request-related information may be identification and authentication information used to identify and authenticate the
user 10 in order to allow him/her to access the private network. For instance, the identification and authentication information may include a user name and a password. - In embodiments where the online request is a request for a download of data, the request-related information may be a bandwidth believed by the
user 10 to be available to download the data. For instance, the bandwidth may be specified by theuser 10 selecting, from a plurality of options corresponding to different connection speeds (e.g., 56, 256 or 1048 kbps) presented on the network site implemented by the server 30 n, the option corresponding to the connection speed that theuser 10 believes is available to download data to thecommunication apparatus 12.
- In embodiments where the online request is a request for an online transaction, the request-related information may be information regarding a transaction object. A “transaction object” refers to any physical or virtual object designed to be used in an attempt to make a transaction. For example, a transaction object may be a payment card (e.g., a credit card, a debit card, etc.), a financial account (e.g., a bank account, an online wallet account, etc.), an electronic check, a set of one or more digital cash (electronic money) certificates, or any other physical or virtual object designed to be used in an attempt to make a transaction. The information regarding the transaction object is hereinafter referred to as “transaction object information” and can take on various forms depending on the nature of the online transaction to be made and the nature of the transaction object itself. In various possible examples, the transaction object information may be:
- It will be appreciated that these examples are presented for illustrative purposes only since, as mentioned above, the request-related information can take on many different forms depending on the nature of the online request being made.
- The request-related information may be provided by the
user 10 via thecommunication apparatus 12 in various ways. For example, theuser 10 may use the at least one input device of thecomputing device 16 to input the request-related information and cause this information to be sent by thecommunication apparatus 12 to the server 30 n (or another computer associated with the server 30 n) over the public packet-switchednetwork 14. Alternatively, the request-related information may have been previously stored in a memory of thecomputing device 16, in which case theuser 10 may use the at least one input device of thecomputing device 16 to cause thecommunication apparatus 12 to send the request-related information to the server 30 n (or another computer associated with the server 30 n) over the public packet-switchednetwork 14. - Continuing with
FIG. 1 , there is provided arequest handling element 51 adapted to process the request-related information provided by theuser 10 via thecommunication apparatus 12 in order to handle the online request made by theuser 10. Functionality of therequest handling element 51 depends on the nature of the online request being made. For example: -
- In embodiments where the online request is a request for an online transaction, the
request handling element 51 may be a transaction validation server adapted to validate the online transaction requested to be made. In such embodiments, the transaction validation server is operated, managed or otherwise associated with an entity responsible for validating the online transaction requested to be made using the transaction object information provided by theuser 10 via thecommunication apparatus 12. For instance, this entity may be a bank or other financial institution that provides the transaction object to the user 10 (e.g., a card issuing bank in cases where the transaction object is a credit card or a debit card). - In embodiments where the online request is a request for a delivery of a product or service to a particular place, the
request handling element 51 may be adapted to verify the location of the particular place and arrange for the product or service to be delivered to the particular place. - In embodiments where the online request is a request for an access to online private content, the
request handling element 51 may be adapted to provide the online private content and control access thereto. - In embodiments where the online request is a request for an access to a private network, the
request handling element 51 may be adapted to control access to the private network. - In embodiments where the online request is a request for a download of data, the
request handling element 51 may be adapted to provide the data and allow it to be downloaded.
- In embodiments where the online request is a request for an online transaction, the
- Depending on the nature of the online request, in some embodiments, the
request handling element 51 may be communicatively coupled to the server 30 via acommunication path 79. Thecommunication path 79 may be established over the public packet-switchednetwork 14 and/or another network 59 (e.g., a financial network). For example, this may be the case where the online request is a request for an online transaction and therequest handling element 51 is a transaction validation server remote from the server 30 n. In such embodiments, therequest handling element 51 comprises suitable hardware, firmware, software, control logic, or a combination thereof for implementing a plurality of functional components, including an interface and a processing unit. The interface of therequest handling element 51 is adapted to receive and send data (e.g., in the form of messages) from and to servers, other computers and/or other elements (e.g., databases). The processing unit of therequest handing element 51 is adapted to effect various processing operations to implement that element's functionality. In other embodiments, therequest handling element 51 may be part of the server 30 n. For example, this may be the case where the online request is a request for an access to online private content that is provided by the server 30 n, a request for a download of data that is provided by the server 30 n, or a request for a delivery of a product or service offered on the network site implemented by the server 30 n. - As shown in
FIG. 1 , in some embodiments, therequest handling element 51 may have access to adatabase 53. More particularly, depending on the nature of the online request made by theuser 10, upon processing the request-related information provided by theuser 10 via thecommunication apparatus 12, therequest handling element 51 may determine that this information matches information included in a record (not shown) that is contained in thedatabase 53. In such cases, the record is associated with a party (who may or may not be the user 10) having a relationship with the entity operating, managing or otherwise associated with therequest handling element 51. For example, the record may be a profile or other account associated with the party. The record may include personal information regarding the party. For instance, this personal information may include a name, a gender, a date of birth or an age, a nationality, a correspondence language, a civic address (e.g., a residential or work address), a phone number (e.g., a residential, work, Voice-over-Internet Protocol (VoIP), or mobile phone number), an email address, and/or an instant messaging (IM) identifier of the party. Other personal information regarding the party may be included in the record. Also, in some cases, the party may be more than one person, in which cases the record may include personal information regarding each such person. The personal information regarding the party may be included in the record as a result of interaction between the party and the entity operating, managing or otherwise associated with the request handling element 51 (e.g., during a registration phase where the record is created). - Specific contents of the
database 53 will depend on the nature of the online request made by theuser 10 and the functionality of therequest handling element 51. A specific example of potential contents of thedatabase 53 will be considered later on. - For now, suffice it to say that, in some embodiments, upon processing the request-related information provided by the
user 10 via thecommunication apparatus 12, therequest handling element 51 may use the personal information included in the record that is contained in thedatabase 53 and that includes information matching the request-related information, in order to handle the online request made by theuser 10. In these embodiments, by virtue of being used to handle the online request, the personal information included in the record that is contained in thedatabase 53 can also be viewed as information related to the online request. - In some embodiments, the
request handling element 51 and thedatabase 53 may be part of separate network elements and communicatively coupled to one another via a communication link, which may traverse one or more network elements and comprise one or more physical links and one or more logical links. In other embodiments, therequest handling element 51 and thedatabase 53 may be part of a common network element. In yet other embodiments, thedatabase 53 may be distributed amongst a plurality of network elements and/or physical locations. - With continued reference to
FIG. 1 , in accordance with an embodiment of the present invention, there is provided anetwork element 34, hereinafter referred to as a “profile information server”, which can interact with therequest handling element 51 as part of a process to handle the online request made by theuser 10 using thecommunication apparatus 12. As further discussed below, theprofile information server 34 allows information pertaining to a profile that is associated with the logical identifier assigned to thecommunication apparatus 12 to be used in order to handle the online request made by theuser 10 using thecommunication apparatus 12. - Interaction between the
profile information server 34 and therequest handling element 51 takes place over acommunication link 61. Thecommunication link 61 may be established over anetwork 63, which may comprise part of the public packet-switchednetwork 14, a financial network and/or another network, and may traverse one or more network elements and comprise one or more physical links and one or more logical links. For example, thecommunication link 61 may be a dedicated and secure link established between theprofile information server 34 and therequest handling element 51. It will be recognized that thecommunication link 61 may be implemented in various manners in different embodiments. - The
profile information server 34 has access to aprofile information database 36. In some embodiments, theprofile information server 34 and theprofile information database 36 may be part of separate network elements and communicatively coupled to one another via a communication link, which may traverse one or more network elements and comprise one or more physical links and one or more logical links. In other embodiments, theprofile information server 34 and theprofile information database 36 may be part of a common network element. In yet other embodiments, theprofile information database 36 may be distributed amongst a plurality of network elements and/or physical locations. - Referring additionally to
FIG. 2 , there is shown an example of potential contents of theprofile information database 36. In this example, theprofile information database 36 stores a plurality of records 40 1 . . . 40 M. Each of the records 40 1 . . . 40 M associates a profile to a logical identifier assigned to a communication apparatus (such as the logical identifier assigned to the communication apparatus 12). - The profile in a record 40 m (1≦m≦M) includes information known to a service provider involved in assigning the logical identifier that is associated with that profile. The service provider may be an access service provider (ASP, also sometimes called a regional access network provider (RANP)) that may or may not be an internet service provider (ISP). For example, the information in the record 40 m may include:
-
- personal information regarding a party to which the service provider provides a network access service. For instance, this personal information may include a name, a gender, a date of birth or an age, a nationality, a correspondence language, a civic address (e.g., a residential or work address), a phone number (e.g., a residential, work, VoIP or mobile phone number), an email address, an IM identifier, and/or financial information (e.g., credit or debit card information, bank account information, or other information used to pay for the network access service) of the party. Other personal information regarding the party may be included in the record. Also, in some cases, the party may be more than one person, in which cases the record 40 m may include personal information regarding each such person. The personal information regarding the party may be included in the record 40 m as a result of interaction between the party and the service provider (e.g., during a registration or service activation phase where the record 40 m is created); and/or
- a location of a service point where the communication apparatus to which is assigned the logical identifier in the record 40 m is located. The “service point” refers to a physical point where the service provider provides a network access service to an end-user (such as the user 10) of the communication apparatus to which is assigned the logical identifier in the record 40 m. For example, the service point may be a house or other building (or an area thereof). The location of the service point, which is hereinafter referred to as the “service point location”, may be expressed as a civic address (e.g., a service address), a set of geo-coordinates, or any other information identifying where the service point is located; and/or
- a bandwidth available to the communication apparatus to which is assigned the logical identifier in the record 40 m.
- This example of information content of a profile is presented for illustrative purposes only and should not be considered limiting in any respect. Generally, a profile that is associated with a given logical identifier assigned to a communication apparatus can include any information known to a service provider involved in assigning the given logical identifier to the communication apparatus.
- An example process by which the
profile information database 36 may be populated is described later on. For now, suffice it to say that theprofile information database 36 stores the records 40 1 . . . 40 M that associate profiles to logical identifiers. - The
profile information server 34 is operative to use information included in theprofile information database 36 as part of its interaction with therequest handling element 51 in order to handle the online request made by theuser 10 using thecommunication apparatus 12. To that end, theprofile information server 34 comprises suitable hardware, firmware, software, control logic, or a combination thereof for implementing a plurality of functional components, including an interface and a processing unit. The interface of theprofile information server 34 is adapted to receive and send data (e.g., in the form of messages) from and to therequest handling element 51, and possibly other servers, computers and/or other elements (e.g., databases) communicatively coupled to theprofile information server 34 via communication links (not shown) that may be established over the public packet-switchednetwork 14 and/or another network and that may traverse one or more network elements and comprise one or more physical links and one or more logical links. The processing unit of theprofile information server 34 is adapted to effect various processing operations to implement that server's functionality. - Operation of the
profile information server 34, its interaction with therequest handling element 51, as well as operation of other network elements, will now be illustrated in the context of an example where the online request made by theuser 10 using thecommunication apparatus 10 is a request for an online transaction. More particularly, in this example, it is assumed that theuser 10, while interacting with the network site implemented by the server 30 n, makes a request to purchase a product or service offered on the network site using a particular credit card. Accordingly, for purposes of this example, and with reference toFIG. 3A , therequest handling element 51 is a transaction validation server associated with a card issuing bank, i.e., a financial institution that issued the particular credit card used by theuser 10. - Also, for purposes of this example, the
transaction validation server 51 has access to theaforementioned database 53. With additional reference toFIG. 4 , there is shown an example of potential contents of thedatabase 53 in this case. Thedatabase 53 stores a plurality of records 57 1 . . . 57 P. In this example, each of the records 57 1 . . . 57 P is associated with a credit card and includes information regarding that credit card (i.e., credit card information). A record 57 p (1≦p≦P) also includes personal information regarding a party to which has been issued the credit card associated with that record. - For instance, this personal information may include a name, a gender, a date of birth or an age, a nationality, a correspondence language, a civic address (e.g., a residential or work address), a phone number (e.g., a residential, work, or mobile phone number), and/or an email address of the party. Other personal information regarding the party may be included. Also, in some cases, the party may be more than one person, in which cases the record 57 p may include personal information regarding each such person. The personal information regarding the party may be included in the record 57 p as a result of interaction between the party and the card issuing bank (e.g., when the party requests to obtain the credit card in question). Each of the records 57 1 . . . 57 P also includes additional information used to process an online transaction attempted to be made using the credit card associated with that record. For instance, this additional information may include a credit limit, a balance due, a list of recent transactions, etc.
- Thus, referring to
FIG. 3A , theuser 10 interacts with the network site implemented by the server 30 n using thecomputing device 16 of thecommunication apparatus 12 in order to select the product or service that he/she desires to purchase. This may involve theuser 10 using an online shopping cart implemented by the server 30 n. Upon selecting the desired product or service, theuser 10 indicates that he/she desires to purchase that product or service, for instance, by selecting a “check-out” option on the network site. - The network site then prompts the
user 10 to provide payment information to pay for the selected product or service. In this example, theuser 10 thus proceeds to enter credit card information (e.g., a card number, an expiry date, and/or a cardholder's name) regarding the particular credit card. Theuser 10 then indicates his/her intent to submit an order to purchase the selected product or service using the entered credit card information, for instance, by selecting a “submit order” option on the network site. - At this point, the
computing device 16 of thecommunication apparatus 12 transmits to the server 30 n amessage 102. In this example, themessage 102 conveys (i) order information indicative of the selected product or service; (ii) purchase amount information indicative of an amount to be paid to purchase the selected product or service; and (iii) the credit card information entered by theuser 10 to purchase the selected product or service. Themessage 102 may also convey the logical identifier assigned to thecommunication apparatus 12. Alternatively, the logical identifier assigned to thecommunication apparatus 12 may not be conveyed by themessage 102 but may already be known to the server 30 n due to prior interaction between thecomputing device 16 and the server 30 n. - Since it travels over the public packet-switched
network 14, the information to be transmitted to the server 30 n as part of themessage 102 may be encrypted by thecomputing device 16 prior to being transmitted to theserver 30 n. This encryption may be effected using the Secure Socket Layer (SSL) protocol or some other encryption technique, by virtue of interaction between thecomputing device 16 and the server 30 n. - Upon receiving the
message 102, the server 30 n processes themessage 102, possibly decrypting one or more of its portions, and proceeds to send amessage 104 to apayment gateway 60. Thepayment gateway 60 is a network element that is connected to afinancial network 68 and that is used by the server 30 n to process online transactions attempted to be made via the network site implemented by the server 30 n. Thefinancial network 68 interconnects a plurality of servers or other computers associated with banks and/or other financial institutions, including, in this example, thetransaction validation server 51 that is associated with the card issuing bank and aserver 70 that is associated with an acquiring bank, i.e., a financial institution that is used by an entity, in this case, a merchant, which operates, manages or is otherwise associated with the server 30 n. - The
message 104 sent to thepayment gateway 60 may be identical to themessage 102, i.e., it may be a relayed version of themessage 102. Alternatively, themessage 104 may be generated by the server 30 n based on themessage 102 and possibly other information known to the server 30 n (e.g., the logical identifier assigned to thecommunication apparatus 12, if not conveyed by themessage 102 but already known to theserver 30 n). In this example, themessage 104 conveys (i) the purchase amount information indicative of an amount to be paid to purchase the selected product or service; (ii) the credit card information entered by theuser 10 to purchase the selected product or service; and (iii) the logical identifier assigned to thecommunication apparatus 12. Here again, information conveyed by themessage 104 may be encrypted prior to transmission to thepayment gateway 60. - Upon receiving the
message 104, thepayment gateway 60 processes themessage 104, possibly decrypting one or more of its portions. Based on content of themessage 104, thepayment gateway 60 determines that it originates from the server 30 n and proceeds to send amessage 106, over thefinancial network 68, to theserver 70, which is associated with the acquiring bank used by the merchant associated with the server 30 n. Themessage 106, which can be viewed as a request for transaction authorization, is intended to elicit from the financial network 68 a response as to whether the online transaction requested by theuser 10 is approved or denied. In this example, thepayment gateway 60 generates themessage 106 based on themessage 104 such that themessage 106 conveys (i) the purchase amount information indicative of an amount to be paid to purchase the selected product or service; (ii) the credit card information entered by theuser 10 to purchase the selected product or service; and (iii) the logical identifier assigned to thecommunication apparatus 12. - The
server 70 receives themessage 106 and processes it to gain knowledge that a transaction involving the merchant associated with the server 30 n is attempted to be effected. Based on the credit card information conveyed by themessage 106, theserver 70 proceeds to send amessage 108 to thetransaction validation server 51 over thefinancial network 68. Themessage 108 may be identical to themessage 106, i.e., it may be a relayed version of themessage 106. Alternatively, themessage 108 may be generated by theserver 70 based on themessage 106 and possibly other information known to theserver 70. In this example, themessage 108 conveys (i) the purchase amount information indicative of an amount to be paid to purchase the selected product or service; (ii) the credit card information entered by theuser 10 to purchase the selected product or service; and (iii) the logical identifier assigned to thecommunication apparatus 12. - The
transaction validation server 51, which is associated with the card issuing bank that issued the particular credit card that has been used by theuser 10 in making the request to purchase the selected product or service, receives themessage 108. Thetransaction validation server 51 proceeds to process themessage 108 to determine whether the online transaction requested by theuser 10 is to be approved or denied. - As part of its operation, in accordance with an embodiment of the present invention and as a measure to counter fraudulent online transactions, the
transaction validation server 51 uses personal information regarding a party to which has been issued the particular credit card used by theuser 10 in order to determine whether the online transaction requested by theuser 10 is to be approved or denied. - More particularly, in this embodiment, the
transaction validation server 51 consults thedatabase 53 to identify a particular one of the records 57 1 . . . 57 P that includes information matching the credit card information conveyed by themessage 108. Upon identifying the particular one of the records 57 1 . . . 57 P, thetransaction validation server 51 obtains therefrom personal information regarding a party to which has been issued the particular credit card associated with that particular record. Specifically, thetransaction validation server 51 obtains one or more elements (e.g., a name, a phone number, a civic address, and/or an email address) of the personal information included in the particular one of the records 57 1 . . . 57 P. - For purposes of this example, assume that the
transaction validation server 51 obtains from the particular one of the records 57 1 . . . 57 P a name of the party to which has been issued the particular credit card used by theuser 10 and associated with that particular record. It will be appreciated that, in other examples, various other elements of the personal information included in the particular one of the records 57 1 . . . 57 P may be obtained by thetransaction validation server 51 and used in determining whether the online transaction requested by theuser 10 is to be approved or denied. It will also be appreciated that, in some cases, the personal information used by thetransaction validation server 51 in determining whether the online transaction requested by theuser 10 is to be approved or denied may be obtained by thetransaction validation server 51 directly from the credit card information entered by theuser 10 and conveyed by themessage 108. For example, in some cases, the credit card information entered by theuser 10 and conveyed by themessage 108 may include a cardholder's name appearing on the particular credit card (i.e., the name of the party to which has been issued the particular credit card), in which cases this name may be obtained by thetransaction validation server 51 directly from themessage 108, rather than being obtained from the particular one of the records 57 1 . . . 57 P. - Thus, in accordance with an embodiment of the present invention, the
transaction validation server 51 effects a verification as to whether the name of the party to which has been issued the particular credit card used by theuser 10 corresponds to a name included in a profile associated to the logical identifier assigned to thecommunication apparatus 12 used by theuser 10. To that end, thetransaction validation server 51 interacts with theprofile information server 34 to effect this verification on a basis of the logical identifier assigned to thecommunication apparatus 12 and conveyed by themessage 108. - With reference to
FIG. 3B , thetransaction validation server 51 sends amessage 110 to theprofile information server 34 over thecommunication link 61. In this embodiment, themessage 110 can be viewed as a request to confirm whether the logical identifier assigned to the communication apparatus 12 (and conveyed by the message 108) is associated with a profile which includes a name that corresponds to name of the party to which has been issued the particular credit card used by the user 10 (i.e., the name obtained from the particular one of the records 57 1 . . . 57 P). Themessage 110 thus conveys the logical identifier assigned to thecommunication apparatus 12 and the name of the party to which has been issued the particular credit card used by theuser 10. - The
profile information server 34 receives themessage 110 and proceeds to process it. More particularly, in this embodiment, theprofile information server 34 extracts the logical identifier assigned to thecommunication apparatus 12 and conveyed by themessage 110, and consults theprofile information database 36 in an attempt to find a particular one of the records 40 1 . . . 40 M that corresponds to this logical identifier. - If the
profile information server 34 is unable to find a particular one of the records 40 1 . . . 40 M that corresponds to the logical identifier assigned to thecommunication apparatus 12 and conveyed by themessage 110, theprofile information server 34 may send to the transaction validation server 51 a message (not shown) indicating that no profile associated with this logical identifier, and thus no name included in such profile, can be found. Upon receiving this message, thetransaction validation server 51 may take remedial action. For example, thetransaction validation server 51 may deny the online transaction attempted to be made using thecommunication apparatus 12 without performing any further processing operation to assess whether it should be approved or denied. Alternatively, thetransaction validation server 51 may perform additional processing operations to determine whether the online transaction requested by theuser 10 is to be approved or denied, including processing operations to re-assess legitimacy of the online transaction requested by theuser 10, i.e., to probe more deeply into whether theuser 10 legitimately used the credit card information conveyed by themessage 108. For instance, these additional processing operations may effect conventional verifications, such as a card security code (CSC) verification whereby theuser 10 is asked to enter the particular credit card's CSC; an address verification system (AVS) whereby theuser 10 is asked to enter a billing address for the particular credit card which is compared to an actual billing address known to the card issuing bank; a phone call to a party to which the card issuing bank issued the particular credit card to verbally confirm legitimacy of the online transaction requested by theuser 10, etc. - For purposes of this example, assume that a particular one of the records 40 1 . . . 40 M corresponds to the logical identifier assigned to the
communication apparatus 12 and conveyed by themessage 110. Theprofile information server 34 thus finds the particular one of the records 40 1 . . . 40 M, which associates the logical identifier assigned to the communication apparatus 12 (and conveyed by the message 110) to a profile including information known to a service provider involved in assigning the logical identifier to thecommunication apparatus 12. This information includes personal information regarding a party to which the service provider provides a network access service. In this case, this personal information includes a name of the party to which the service provider provides a network access service. Based on themessage 110, which requests a confirmation as to whether the logical identifier assigned to thecommunication apparatus 12 is associated with a profile which includes a name that corresponds to name of the party to which has been issued the particular credit card used by theuser 10, theprofile information server 34 obtains from the particular one of the records 40 1 . . . 40 M the name of the party to which the service provider provides a network access service. - The
profile information server 34 proceeds to compare the name of the party to which the service provider provides a network access service (obtained from the particular one of the records 40 1 . . . 40 M) to the name of the party to Which has been issued the particular credit card used by the user 10 (conveyed by the message 110). Based on a result of this comparison, theprofile information server 34 performs an action related to validation of the online transaction requested by theuser 10 using thecommunication apparatus 12. More specifically, in this embodiment, the action performed by theprofile information server 34 comprises generating and transmitting to the transaction validation server 51 amessage 112 that indicates whether the name of the party to which the service provider provides a network access service (obtained from the particular one of the records 40 1 . . . 40 M) corresponds to the name of the party to which has been issued the particular credit card used by the user 10 (conveyed by the message 110). This action is related to validation of the online transaction requested by theuser 10 since themessage 112 will be used by thetransaction validation server 51 to validate the online transaction, as discussed below. - The
transaction validation server 51 receives themessage 112 and processes it to learn whether the name of the party to which the service provider provides a network access service (obtained from the particular one of the records 40 1 . . . 40 M) corresponds to the name of the party to which has been issued the particular credit card used by the user 10 (conveyed by the message 110). As discussed below, thetransaction validation server 51 handles the request for the online transaction made by theuser 10 in different manners depending on whether the name of the party to which the service provider provides a network access service (obtained from the particular one of the records 40 1 . . . 40 M) corresponds to or does not correspond to the name of the party to which has been issued the particular credit card used by the user 10 (conveyed by the message 110). - If the
message 112 indicates that the name of the party to which the service provider provides a network access service (obtained from the particular one of the records 40 1 . . . 40 M) does not correspond to the name of the party to which has been issued the particular credit card used by the user 10 (conveyed by the message 110), thetransaction validation server 51 concludes based on themessage 112 that legitimacy of the request for the online transaction made by theuser 10 is not established. This may result in the online transaction being denied by thetransaction validation server 51 without performing any further processing operation to assess whether it should be approved or denied. Alternatively, this may result in thetransaction validation server 51 performing additional processing operations to determine whether the online transaction requested by theuser 10 is to be approved or denied, including processing operations to re-assess legitimacy of the request for the online transaction made by theuser 10, i.e., to probe more deeply into whether theuser 10 legitimately used the credit card information conveyed by themessage 108. For instance, and as mentioned above, these additional processing operations may effect conventional verifications, such as a card security code (CSC) verification, an address verification system (AVS), a phone call to verbally confirm legitimacy of the online transaction requested by theuser 10, etc. - On the other hand, if the
message 112 indicates that the name of the party to which the service provider provides a network access service (obtained from the particular one of the records 40 1 . . . 40 M) corresponds to the name of the party to which has been issued the particular credit card used by the user 10 (conveyed by the message 110), thetransaction validation server 51 concludes based on themessage 112 that legitimacy of the request for the online transaction made by theuser 10 is established. In other words, thetransaction validation server 51 concludes based on themessage 112 that the request for the online transaction made by theuser 10 is legitimate, i.e., that theuser 10 legitimately used the credit card information entered at step 200 and conveyed in themessage 108. - The
transaction validation server 51 proceeds to perform other processing operations to determine whether the online transaction requested by theuser 10 is to be approved or denied. Approval or denial of the online transaction can be determined based on various factors. For example, based on the additional information (e.g., a credit limit, a balance due, etc.) included in the particular one of the records 57 1 . . . 57 P and the purchase amount information indicative of an amount to be paid to purchase the selected product or service that is conveyed by themessage 108, thetransaction validation server 51 may determine whether the online transaction is to be approved or denied. It will be appreciated that approval or denial of the online transaction may be determined by thetransaction validation server 51 based on other factors. - Upon determining whether the online transaction is approved or denied, the
transaction validation server 51 sends amessage 114 to theserver 70 over thefinancial network 68. Themessage 114 indicates whether the online transaction is approved or denied. If the online transaction is denied, themessage 114 may indicate (e.g., by a code) a reason for this denial, such as insufficient funds, an unavailable bank link, etc. - The
server 70 receives themessage 114 and processes it to know whether the online transaction is approved or denied. If approved, the online transaction is eventually settled via a settlement process involving the acquiring bank and the card issuing bank. This settlement process is well known and thus not described herein. - The
server 70 proceeds to send amessage 116 to thepayment gateway 60. Themessage 116 may be identical to themessage 114, i.e., it may be a relayed version of themessage 114. Alternatively, themessage 116 may be generated by theserver 70 based on themessage 114. Themessage 116 indicates whether the online transaction is approved or denied and, if applicable, may indicate a reason for denial of the online transaction. - Upon receiving the
message 116, thepayment gateway 60 processes it and proceeds to send amessage 118 to the server 30 n. Generated by thepayment gateway 60 on a basis of themessage 116, themessage 118 indicates whether the online transaction is approved or denied and, if applicable, may indicate a reason for denial of the online transaction. Information conveyed by themessage 118 may be encrypted by thepayment gateway 60 prior to being transmitted to the server 30 n. - The server 30 n receives the
message 118. The server 30 n processes themessage 118, possibly decrypting one or more of its portions, to ascertain whether the online transaction is approved or denied. Approval or denial of the online transaction (and a reason for denial, if applicable) may be recorded by the server 30 n for future reference. The server 30 n proceeds to send amessage 120 to thecomputing device 16 of thecommunication apparatus 12 in order to communicate approval or denial of the online transaction to theuser 10. Since it travels over the public packet-switchednetwork 14, information conveyed by themessage 120 may be encrypted by the server 30 n prior to being transmitted to thecomputing device 16. - Upon receiving the
message 120, thecomputing device 16 processes themessage 120, possibly decrypting one or more of its portions, so as to communicate approval or denial of the online transaction to theuser 10. For example, this may be achieved by displaying a “transaction approved” or “transaction denied” message (or any conceivable variant thereof) on the display of thecomputing device 16. - It will thus be appreciated that validation of the online transaction requested by the
user 10 can be effected using information known to the service provider involved in assigning the logical identifier to the communication apparatus. This enables thetransaction validation server 51 to conveniently and efficiently establish legitimacy of the request for the online transaction made by theuser 10 in a way that is transparent to theuser 10. - While the above-described example illustrates one possible manner of verifying whether the name of the party to which has been issued the particular credit card used by the
user 10 corresponds to a name included in a profile associated to the logical identifier assigned to thecommunication apparatus 12 used by theuser 10, it will be appreciated that this verification may be effected in various other manners in other embodiments. - For example,
FIG. 3C illustrates one possible variant. In this variant, messages have been exchanged as described above in connection withFIG. 3A , leading up to receipt of themessage 108 by thetransaction validation server 51, which proceeds to process themessage 108 to determine whether the online transaction requested by theuser 10 is to be approved or denied. - The
transaction validation server 51 sends amessage 110* to theprofile information server 34 over thecommunication link 61. In this embodiment, themessage 110* can be viewed as a request to obtain a name included in a profile that is associated with the logical identifier assigned to the communication apparatus 12 (and conveyed by the message 108). Themessage 110* thus conveys the logical identifier assigned to thecommunication apparatus 12. - The
profile information server 34 receives themessage 110* and proceeds to process it. More particularly, in this embodiment, theprofile information server 34 extracts the logical identifier assigned to thecommunication apparatus 12 and conveyed by themessage 110*, and consults theprofile information database 36 in an attempt to find a particular one of the records 40 1 . . . 40 M that corresponds to this logical identifier. - If the
profile information server 34 is unable to find a particular one of the records 40 1 . . . 40 M that corresponds to the logical identifier assigned to thecommunication apparatus 12 and conveyed by themessage 110*, theprofile information server 34 may send to the transaction validation server 51 a message (not shown) indicating that no profile associated with this logical identifier, and thus no name included in such profile, can be found. Upon receiving this message, thetransaction validation server 51 may take remedial action. For example, thetransaction validation server 51 may deny the online transaction attempted to be made using thecommunication apparatus 12 without performing any further processing operation to assess whether it should be approved or denied. Alternatively, thetransaction validation server 51 may perform additional processing operations to determine whether the online transaction requested by theuser 10 is to be approved or denied, including processing operations to re-assess legitimacy of the online transaction requested by theuser 10, i.e., to probe more deeply into whether theuser 10 legitimately used the credit card information conveyed by themessage 108. For instance, these additional processing operations may effect conventional verifications, such as a card security code (CSC) verification whereby theuser 10 is asked to enter the particular credit card's CSC; an address verification system (AVS) whereby theuser 10 is asked to enter a billing address for the particular credit card which is compared to an actual billing address known to the card issuing bank; a phone call to a party to which the card issuing bank issued the particular credit card to verbally confirm legitimacy of the online transaction requested by theuser 10, etc. - For purposes of this example, assume that a particular one of the records 40 1 . . . 40 M corresponds to the logical identifier assigned to the
communication apparatus 12 and conveyed by themessage 110*. Theprofile information server 34 thus finds the particular one of the records 40 1 . . . 40 M, which associates the logical identifier assigned to the communication apparatus 12 (and conveyed by themessage 110*) to a profile including information known to a service provider involved in assigning the logical identifier to thecommunication apparatus 12. This information includes personal information regarding a party to which the service provider provides a network access service. In this case, this personal information includes a name of the party to which the service provider provides a network access service. Theprofile information server 34 thus obtains from the particular one of the records 40 1 . . . 40 M the name of the party to which the service provider provides a network access service. - The
profile information server 34 proceeds to perform an action related to validation of the online transaction requested by theuser 10 using thecommunication apparatus 12. In this embodiment, the action performed by theprofile information server 34 comprises generating and transmitting to the transaction validation server 51 amessage 112* that conveys the name obtained from the particular one of the records 40 1 . . . 40 M, i.e., the name of the party to which the service provider provides a network access service. This action is related to validation of the online transaction requested by theuser 10 since themessage 112* will be used by thetransaction validation server 51 to validate the online transaction, as discussed below. - The
transaction validation server 51 receives themessage 112* and processes it. More particularly, thetransaction validation server 51 compares the name of the party to which the service provider provides a network access service (obtained from the particular one of the records 40 1 . . . 40 M of the database 36) to the name of the party to which has been issued the particular credit card used by the user 10 (obtained from the particular one of the records 57 1 . . . 57 P of thedatabase 53 at step 240). Based on a result of this comparison, thetransaction validation server 51 performs an action related to validation of the online transaction requested by theuser 10 using thecommunication apparatus 12. More specifically, in this embodiment, the action performed by thetransaction validation server 51 comprises validating the online transaction requested by theuser 10 in different manners depending on a result of this comparison. - If the name of the party to which the service provider provides a network access service (obtained from the particular one of the records 40 1 . . . 40 M) does not correspond to the name of the party to which has been issued the particular credit card used by the user 10 (obtained from the particular one of the records 57 1 . . . 57 P), the
transaction validation server 51 concludes that legitimacy of the request for the online transaction made by theuser 10 is not established. This may result in the online transaction being denied by thetransaction validation server 51 without performing any further processing operation to assess whether it should be approved or denied. Alternatively, this may result in thetransaction validation server 51 performing additional processing operations to determine whether the online transaction requested by theuser 10 is to be approved or denied, including processing operations to re-assess legitimacy of the request for the online transaction made by theuser 10, i.e., to probe more deeply into whether theuser 10 legitimately used the credit card information entered at step 200 and conveyed in themessage 108. For example, as mentioned above, these additional processing operations may effect conventional verifications, such as a card security code (CSC) verification, an address verification system (AVS), a phone call to verbally confirm legitimacy of the online transaction requested by theuser 10, etc. - On the other hand, if the name of the party to which the service provider provides a network access service (obtained from the particular one of the records 40 1 . . . 40 M) corresponds to the name of the party to which has been issued the particular credit card used by the user 10 (obtained from the particular one of the records 57 1 . . . 57 P), the
transaction validation server 51 concludes that legitimacy of the request for the online transaction made by theuser 10 is established. In other words, thetransaction validation server 51 concludes that the request for the online transaction made by theuser 10 is legitimate, i.e., that theuser 10 legitimately used the credit card information entered at step 200 and conveyed in themessage 108. - The
transaction validation server 51 proceeds to perform other processing operations to determine whether the online transaction requested by theuser 10 is to be approved or denied. Approval or denial of the online transaction can be determined based on various factors. For example, based on the additional information (e.g., a credit limit, a balance due, etc.) included in the particular one of the records 57 1 . . . 57 P and the purchase amount information indicative of an amount to be paid to purchase the selected product or service that is conveyed by themessage 108, thetransaction validation server 51 may determine whether the online transaction is to be approved or denied. It will be appreciated that approval or denial of the online transaction may be determined by thetransaction validation server 51 based on other factors. - Upon determining whether the online transaction is approved or denied, the
transaction validation server 51 sends themessage 114 to theserver 70 over thefinancial network 68, as described above in connection withFIG. 3B . This variant then continues as described above in connection withFIG. 3B . - While this variant illustrates another possible manner of verifying whether the name of the party to which has been issued the particular credit card used by the
user 10 corresponds to a name included in a profile associated to the logical identifier assigned to thecommunication apparatus 12 used by theuser 10, it will be appreciated that this verification may be effected in various other manners in other embodiments. - Although the example considered above relates to an online transaction involving an online purchase using a credit card, principles described herein apply to other types of online transactions, including, for example, those involving online purchases or payments using other payment objects (e.g., digital cash, electronic checks) or online fund transfers involving accounts (e.g., bank accounts, online wallet accounts).
- Also, while in the example considered above the online request made using the
communication apparatus 12 is a request for an online transaction, principles described herein apply to other types of online requests, including a request for a delivery of a product or service to a particular place, a request for an access to online private content, a request for an access to a private network, a request for a download of data, or any other request that can be made online. - In addition, while in the example considered above the online request made using the
communication apparatus 12 is handled on a basis of a name known to a service provider involved in assigning the logical identifier to thecommunication apparatus 12, other information known to the service provider and part of the profile associated with this logical identifier may be used in other cases, depending on the nature of the online request being made. For example, where the online request is a request for a delivery of a product or service to a particular place, a civic address known to the service provider may be used to handle the requested delivery; where the online request is a request for a download of data to thecommunication apparatus 12, a bandwidth known to the service provider to be available to thecommunication apparatus 12 may be used to handle the requested download of data; etc. - Furthermore, while in the above-considered example certain messages are exchanged between various elements of the architecture depicted in
FIG. 1 , it will be appreciated that different messages may be exchanged in other embodiments. - Moreover, although in the above-considered example the
transaction validation server 51 interacts with theprofile information server 34, it will be appreciated that, in other embodiments, other network elements may interact with theprofile information server 34 as part of a process to handle an online request made by theuser 10 via thecommunication apparatus 12. For example, in some embodiments, and depending on the nature of the online request, thepayment gateway 60, theserver 70, the server 30 n or any other network element may interact with theprofile information server 34 as part of a process to handle an online request made by theuser 10 via thecommunication apparatus 12. - Also, while the above-described example relates to an online request made over the public packet-switched
network 14, it will be recognized that principles described herein can be applied to an online request made over a private packet-switched network. - Turning now to
FIG. 5 , an example process by which theprofile information database 36 may be populated will be described. It is recalled that theprofile information database 36 stores the records 40 1 . . . 40 M that associate logical identifiers to profiles which include information known to one or more service providers involved in assigning these logical identifiers. - This example will illustrate one possible manner by which an association between the logical identifier assigned to the
communication apparatus 12 and a profile including information known to a service provider involved in assigning the logical identifier to thecommunication apparatus 12, may be stored in theprofile information database 36 as part of one of the records 40 1 . . . 40 M. - In this example, a given service provider owning, managing or otherwise associated with one or more network elements of the
communication link 20 connecting thecommunication apparatus 12 to the public packet-switchednetwork 14 provides a network access service to a given party (who may or may not be the user 10) occupying, owning, managing or otherwise associated with premises where thecommunication apparatus 12 is located. In order to benefit from the network access service, the given party has a business relationship with the given service provider. As part of this business relationship, the given party interacts with the given service provider (e.g., during a registration or service activation phase) to provide personal information regarding itself. For example, this personal information may include a name, a gender, a date of birth or an age, a nationality, a correspondence language, a civic address (e.g., a residential or work address), a phone number (e.g., a residential, work, VoIP or mobile phone number), an email address, and/or an IM identifier of the given party. If the given party is more than one person, personal information regarding each such person may be provided. During interaction with the given service provider, the given party also indicates a service point location (e.g., a service address) where the network access service is to be delivered, selects a level of service to be obtained, provides billing information (e.g., a billing address and/or credit card information) to pay for the network access service, etc. Interaction between the given party and the given service provider may take place via a customer service representative of the given service provider or via a web site implemented by the given service provider. - The given service provider stores in the profile information database 36 a profile associated with the given party, in which is included information provided by the given party while interacting with the given service provider and possibly other information not obtained from the given party but pertaining to the network access service provided to the given party.
- In this example, the infrastructure described above in connection with
FIG. 1 and partly shown inFIG. 5 comprises an operation support system (OSS) 122. TheOSS 122 represents a collection of systems that perform management, inventory, engineering, planning, repair and other functions for the given service provider. In this light, one of the functions of theOSS 122 may include management of network elements, assets and equipment. Thus, theOSS 122 maintains amapping 124 between, on the one hand, ports of various access multiplexers or other network elements under control of the given service provider and, on the other, service point locations of communication apparatus (such as the communication apparatus 12) connected to those ports. In this case, themapping 124 maintained by theOSS 122 relates aport 104 of thenetwork element 21 to a service point location, i.e., the location of a service point where thecommunication apparatus 12 is located. As mentioned previously, this service point location may be expressed as a civic address, a set of geo-coordinates, or any other information identifying where the service point is located. - Also, in this example, the
network element 21 of thecommunication link 20 connecting thecommunication apparatus 12 to the public packet-switchednetwork 14 is an access multiplexer under control of the given service provider. In one embodiment, theaccess multiplexer 21 may be a DSLAM. - The
access multiplexer 21 is connected to thenetwork element 23, which, in this embodiment, is a network access server (NAS) operated by the given service provider. TheNAS 23, which may also sometimes be referred to as a broadband remote access server (BRAS), a remote access server (RAS) or a broadband access server (BAS), provides access to the public packet-switchednetwork 14. Communication between theaccess multiplexer 21 and theNAS 23 can take place over the dedicatedlogical link 19 between these elements. The dedicatedlogical link 19, which may traverse an intervening access data network (not shown), can be implemented in various ways. For example, in one embodiment, the dedicatedlogical link 19 may be implemented as an asynchronous transfer mode (ATM) permanent virtual circuit (PVC). In another embodiment, the dedicatedlogical link 19 may be implemented as a virtual local area network (VLAN). It will be appreciated that various other implementations of the dedicatedlogical link 19 are possible. - The
access multiplexer 21 allows data arriving from theNAS 23 along given ATM PVCs, VLANs or other dedicated logical links to be sent over corresponding physical links via corresponding one of its ports, and vice versa. Thus, theaccess multiplexer 21 can be said to implement amapping 134 between, on the one hand, dedicated logical links and, on the other, ports of theaccess multiplexer 21. In this example, themapping 134 implemented by theaccess multiplexer 21 relates the dedicatedlogical link 19 to theport 104 of theaccess multiplexer 21. In two example embodiments, themapping 134 can be maintained by either theaccess multiplexer 21 or theOSS 122. - The infrastructure shown in
FIG. 5 further comprises anauthorization element 142 connected to theNAS 23. The nature of the connection between theNAS 23 and theauthorization element 142 is immaterial. For example, in one embodiment, theauthorization element 142 may be a server (e.g., an Authentication, Authorization, and Accounting (AAA) server) responsive to queries from theNAS 23. In such an embodiment, theauthorization element 142 and theNAS 23 may communicate using the Remote Authentication Dial In User Service (RADIUS) protocol, a description of which is available at www.ietf.org/rfc/rfc2865.txt. In another embodiment, theauthorization element 142 may be a functional element integrated with theNAS 23. - In this example, the
NAS 23 is operative to maintain apool 127 of logical identifiers that can be used by various communication apparatus, including thecommunication apparatus 12. In some embodiments, thepool 127 of addresses may be built up as a cooperative effort between theNAS 23 and theOSS 122, while in other embodiments, it may not be necessary for theOSS 122 to be involved in creating thepool 127 of logical identifiers. In still other embodiments, thepool 127 of logical identifiers may be maintained by theauthorization element 142, and may be made accessible to theauthorization element 142 without needing to pass through theNAS 23. - The
profile information server 34, and theprofile information database 36 that it has access to, can be linked to other components of the infrastructure ofFIG. 5 in various ways. For example, in one embodiment, theprofile information server 34 may be connected to theNAS 23 by alink 175. In another embodiment, theprofile information server 34 may be connected to theauthorization element 142 by alink 177. The nature of the connection between theprofile information server 34 and either theNAS 23 or theauthorization element 142 is immaterial. In other embodiments, theprofile information server 34 may be part of either theOSS 122, theNAS 23 or theauthorization element 142. - As previously mentioned, in some embodiments, the
profile information server 34 and theprofile information database 36 may be part of separate network elements and communicatively coupled to one another via a communication link, which may traverse one or more network elements and comprise one or more physical links and one or more logical links. In other embodiments, theprofile information server 34 and theprofile information database 36 may be part of a common network element. In yet other embodiments, theprofile information database 36 may be distributed amongst a plurality of network elements and/or physical locations. Also, it should be appreciated that theprofile information database 36 may be managed, maintained and/or updated by an entity that may be the given service provider or a different entity. - It will be appreciated that numerous modifications and variations of the infrastructure of
FIG. 5 are possible. For example, in some embodiments, theaccess multiplexer 21 can be omitted. This may be true in embodiments where thecommunication apparatus 12 implements a wireless access point. For instance, in such embodiments, the connection between the wireless access point and theNAS 23 may be provided by a dedicated point-to-point link. As another example, in some embodiments, instead of the dedicatedlogical link 19, there may be a shared link leading to thecommunication apparatus 12. - Reference is now made to
FIG. 6 , which illustrates an example of a possible event flow upon activation of thecommunication apparatus 12, which may occur, for instance, as thenetwork interface unit 18 and/or thecomputing device 16 of thecommunication apparatus 12 is/are powered up. Thereafter: -
- The communication apparatus. 12 establishes physical layer connectivity with the
access multiplexer 21 over thephysical link 17. - This is followed by establishment of Ethernet connectivity between the
communication apparatus 12 and theaccess multiplexer 21. - The
communication apparatus 12 verifies its ability to communicate using Point-to-Point Protocol over Ethernet (PPPoE). For a more detailed explanation of PPPoE, one may refer to Internet Request For Comments (RFC) 2516, available from the Internet Engineering Task Force (http://www.ietf.org), hereby incorporated by reference herein. - Next, assuming that the
communication apparatus 12 has the ability to communicate using PPPoE, thecommunication apparatus 12 verifies whether it should make a so-called “access request” automatically or in response to user input (which can be obtained via a software application). For purposes of this example, let it be assumed that conditions have been met such that thecommunication apparatus 12 should make an access request. - The
communication apparatus 12 begins entry into PPPoE communication by broadcasting an “initiation” packet over the dedicatedlogical link 19. - The
NAS 23 responds to receipt of the initiation packet by sending an “offer” packet to thecommunication apparatus 12. Thus, at this stage, it can be said that alogical connection 182 has been defined between a first endpoint (the communication apparatus 12) and a second endpoint (the NAS 23). - Following receipt of the offer packet, the
communication apparatus 12 sends anaccess request 184 to theNAS 23 with the ultimate goal of accessing the public packet-switchednetwork 14. Theaccess request 184 may comprise credentials that can be hard coded or programmably installed on thecommunication apparatus 12. Alternatively, the credentials may be entered by theuser 10 of thecommunication apparatus 12. - Upon receipt of the
access request 184 containing the credentials along the dedicatedlogical link 19, theNAS 23 executes an authorization procedure as follows. TheNAS 23 communicates the credentials to theauthorization element 142, e.g., via a RADIUS Access-Request message 188. In response to receipt of the credentials from theNAS 23, theauthorization element 142 determines whether the credentials allow access to the public packet-switchednetwork 14. For example, this can be determined by consulting a database (not shown). If the credentials allow access to the public packet-switchednetwork 14, theauthorization element 142 returns an acceptance message (e.g., a RADIUS Access-Accept message). On the other hand, if the credentials do not allow access to the public packet-switchednetwork 14, theauthorization element 142 returns a refusal message (e.g., a RADIUS Access-Reject message). For purposes of this example, assume that the credentials allow access to the public packet-switchednetwork 14, resulting in issuance of anacceptance message 190. In this example, two alternatives are possible:- Alternative 1 (where the
pool 127 of logical identifiers is maintained by the authorization element 142): theauthorization element 142 obtains alogical identifier 193 from thepool 127 of logical identifieres that is maintained by theauthorization element 142. Thelogical identifier 193 is sent to theNAS 23, which assigns thelogical identifier 193 to the dedicatedlogical link 19. - Alternative 2 (where the
pool 127 of logical identifieres is maintained by the NAS 23): responsive to receipt of theacceptance message 190 from theauthorization element 142, theNAS 23 obtains alogical identifier 193 from thepool 127 of logical identifieres that is maintained by theNAS 23. Thelogical identifier 193 so obtained is assigned by theNAS 23 to the dedicatedlogical link 19.
- Alternative 1 (where the
- The
NAS 23 sends a “confirmation” packet back to thecommunication apparatus 12, thus completing establishment of a PPPoE session between the endpoints of thelogical connection 182. - Additional hand-shaking may be performed between the
communication apparatus 12 and theNAS 23 in order to establish a Point-to-Point Protocol (PPP) session between the endpoints of thelogical connection 182. - Following this, further hand-shaking may be undertaken between the
communication apparatus 12 and theNAS 23 in order to establish an Internet Protocol Control Protocol (IPCP) session between the endpoints of thelogical connection 182. - During the IPCP session, the
NAS 23 releases thelogical identifier 193 towards thecommunication apparatus 12 that issued theaccess request 184, in order to allow thecommunication apparatus 12 to identify itself using thelogical identifier 193 in future communications over the dedicatedlogical link 19. Since the dedicatedlogical link 19 to which has been assigned thelogical identifier 193 leads to thecommunication apparatus 12 and since thecommunication apparatus 12 will identify itself using thelogical identifier 193 in future communications, it can be seen that thelogical identifier 193 is in essence assigned to thecommunication apparatus 12.
- The communication apparatus. 12 establishes physical layer connectivity with the
- It is recalled that once the
logical identifier 193 has been obtained from thepool 127 of logical identifieres (either by theNAS 23 or by the authorization element 142), theNAS 23 assigns thelogical identifier 193 to the dedicatedlogical link 19. - In an embodiment where the
profile information server 34 is connected to theNAS 23 by thelink 175, the fact that theNAS 23 assigns thelogical identifier 193 to the dedicatedlogical link 19 allows theNAS 23 to construct and maintain amapping 144 between, on the one hand, various dedicated logical links (such as the dedicatedlogical link 19 and others) and, on the other, logical identifieres corresponding to those dedicated logical links. - In an embodiment where the
profile information server 34 is connected to theauthorization element 142 by thelink 177, thelogical identifier 193 and the identity of the dedicatedlogical link 193 to which it is assigned are sent back by theNAS 23 to theauthorization element 142, and it is theauthorization element 142 that maintains theaforementioned mapping 144 between dedicated logical links and logical identifieres corresponding to those dedicated logical links. - Of course, those skilled in the art will be able to think of other ways of causing the
communication apparatus 12 to send theaccess request 184 over thelogical connection 182 between thecommunication apparatus 12 and theNAS 23, as well as other ways of assigning a logical identifier to the dedicatedlogical link 19 and thus to thecommunication apparatus 12. It should further be mentioned that, in some cases, the establishment of the aforementioned PPPoE, PPP and/or IPCP sessions may not be required. This is particularly the case where the dedicatedlogical link 19 is a VLAN. - In view of the preceding description, and in particular given the previously described
mappings OSS 122 and/or theaccess multiplexer 21 and themapping 144 maintained in theNAS 23 or theauthorization element 142, the following describes how one can create an association between logical identifieres and service point locations. - Specifically, with reference to
FIG. 7 , by combining themapping 124 with themapping 134, theOSS 122 can create anintermediate mapping 166 between, on the one hand, dedicated logical links and, on the other hand, service point locations of communication apparatus having logical connections with theNAS 23 which traverse those dedicated logical links. In this example, theintermediate mapping 166 would associate the dedicatedlogical link 19 to the service point location of thecommunication apparatus 12. In one embodiment, theOSS 122 transmits theintermediate mapping 166 to theprofile information server 34. - Next, the
profile information server 34 may be operative to combine the intermediate mapping 166 (received from the OSS 122) with the aforementioned mapping 144 (received from theNAS 23 or the authorization element 142), thus creating afinal mapping 176 between, on the one hand, logical identifieres and, on the other, service point locations of communication apparatus having logical connections with theNAS 23 which traverse respective dedicated logical links to which those logical identifieres have been assigned. In this example, thefinal mapping 176 would specify that thelogical identifier 193 corresponds to the service point location of thecommunication apparatus 12, i.e., the location of the service point where thecommunication apparatus 12 is located. - It is recalled that the profile associated with the given party and stored in the
profile information database 36 by the given service provider includes the service point location where the network access service is to be delivered to the given party. Thus, based on thefinal mapping 176 specifying that thelogical identifier 193 corresponds to the service point location of thecommunication apparatus 12, theprofile information server 34 associates, in theprofile information database 36, the profile associated with the given party to thelogical identifier 193 assigned to thecommunication apparatus 12. - From the above, it should be apparent that the
profile information database 36 can be populated with logical identifieres and profiles associated with these logical identifieres. - While the above-described example illustrates one possible technique for populating the
profile information database 36, it will be appreciated that other techniques may be employed in other embodiments. For example, in some embodiments, the aforementioned credentials, which may be hard coded or programmably installed on thecommunication apparatus 12 or entered by theuser 10 of the communication apparatus and which may be included in theaccess request 184 sent by thecommunication apparatus 12 to theNAS 23, can be used to associate thelogical identifier 193 assigned to thecommunication apparatus 12 to the profile associated with the given party and stored in theprofile information database 36. Specifically, these credentials, which are known by the service provider to have been provided to the given party, may be linked by the given service provider to the profile associated with the given party. Upon receiving the credentials as part of theaccess request 184 and assigning thelogical identifier 193 to thecommunication apparatus 12, the given service provider may associate, in theprofile information database 36, the profile associated with the given party to thelogical identifier 193 assigned to thecommunication apparatus 12. - It will also be appreciated that, in embodiments where the logical identifier is dynamically assigned to the communication apparatus 12 (e.g., a dynamic IP address), the
profile information database 36 may be updated accordingly. - Although in embodiments described above the
communication apparatus 12 is directly connected to thecommunication link 20, it will be appreciated that, in some embodiments, thecommunication apparatus 12 may be connected to a router that is connected to thecommunication link 20 and that may be connected to one or more other communication apparatuses at premises where thecommunication apparatus 12 is located. In such embodiments, the router may perform network address translation (NAT) for packets passing therethrough. Depending on the type of NAT performed, in some cases, the logical identifier assigned to thecommunication apparatus 12 may include a portion identifying the router and a portion identifying thecommunication apparatus 12 connected thereto. For instance, the logical identifier assigned to thecommunication apparatus 12 may include an IP address assigned to the router, as well as a port number of a port of the router to which is connected thecommunication apparatus 12 or a local IP address assigned to thecommunication apparatus 12 by the router. - Also, while in embodiments considered above the
profile information server 34 interacts with therequest handling element 51 using the information included in the particular one of the records 40 1 . . . 40 M in theprofile information database 36 without theuser 10 being explicitly informed of this fact, in other embodiments there may be mechanisms to notify theuser 10 of this fact or confirm with theuser 10 that he/she allows this information to be used by theprofile information server 34 in its interaction with therequest handling element 51. For example, in some embodiments, an applet, widget or other suitable element may be implemented to notify theuser 10 via the computing device 16 (e.g., via a pop-up window) of the interaction between theprofile information server 34 and therequest handling element 51 and possibly to allow theuser 10 to confirm whether information (or control which information) included in the particular one of the records 40 1 . . . 40 M in theprofile information database 36 can be used by theprofile information server 34 as part of this interaction. As another example, the given party (who may or may not be the user 10) occupying, owning, managing or otherwise associated with premises where thecommunication apparatus 12 is located may have previously authorized the service provider providing the network access service to the communication apparatus 12 (e.g., during a registration phase) to use information contained in the particular one of the records 40 1 . . . 40 M as part of a process to handle an online request made via thecommunication apparatus 12. - In addition, although embodiments described above considered online requests that the
user 10 can make using thecommunication apparatus 12 while interacting with network sites implemented by the servers 30 1 . . . 30 N, it will be appreciated that, in other embodiments, theuser 10 may make an online request during a telephone call established (at least partly) over the public packet-switched network 14 (or a private packet-switched network) and such online request may be handled using principles described herein. In such embodiments, thecommunication apparatus 12 may comprise a VoIP phone, a Plain Old Telephone Service (POTS) phone equipped with an analog terminal adapter (ATA), or a soft phone (i.e., a computer equipped with telephony software). For example, during a call with a representative (e.g., a customer service representative or other employee) of a given entity (e.g., a company, governmental organization, non-profit organization, etc.), theuser 10 may make a certain request. In doing so, theuser 10 may verbally provide request-related information that may need to be verified in order to handle the user's request. In this case, a server operated by the given entity may determine the logical identifier assigned to the communication apparatus 12 (based on packets received during the call) and may use this logical identifier to exchange messages with theprofile information server 34 in order to effect verification of the request-related information provided by theuser 10. Interaction between the server operated by the given entity and theprofile information server 34 may be similar to interaction between therequest handling element 51 and theprofile information server 34. - Those skilled in the art will appreciate that, in some embodiments, certain functionality of a given component described herein (e.g., the
profile information server 34 or the request handling element 51) may be implemented as pre-programmed hardware or firmware elements (e.g., application specific integrated circuits (ASICs), electrically erasable programmable read-only memories (EEPROMs), etc.) or other related elements. In other embodiments, a given component described herein (e.g., theprofile information server 34 or the request handling element 51) may comprise a processor having access to a code memory which stores program instructions for operation of the processor to implement functionality of that given component. The program instructions may be stored on a medium which is fixed, tangible, and readable directly by the given component (e.g., removable diskette, CD-ROM, ROM, fixed disk, USB key, etc.). Alternatively, the program instructions may be stored remotely but transmittable to the given component via a modem or other interface device connected to a network over a transmission medium. The transmission medium may be either a tangible medium (e.g., optical or analog communications lines) or a medium implemented using wireless techniques (e.g., RF, microwave, infrared or other wireless transmission schemes). - Although various embodiments of the present invention have been described and illustrated, it will be apparent to those skilled in the art that numerous modifications and variations can be made without departing from the scope of the invention, which is defined in the appended claims.
Claims (90)
1. A method comprising:
obtaining first information, the first information relating to an online request made using a communication apparatus to which has been assigned a logical identifier used to route data associated with the online request over a packet-switched network;
using the logical identifier to obtain second information, the second information pertaining to a profile associated with the logical identifier;
comparing the first information to the second information; and
performing an action related to handling of the online request based on a result of said comparing.
2. A method as claimed in claim 1 , wherein using the logical identifier to obtain the second information comprises consulting a database on a basis of the logical identifier.
3. A method as claimed in claim 1 , wherein using the logical identifier to obtain the second information comprises:
transmitting a first message conveying the logical identifier; and
receiving a second message conveying the second information.
4. A method as claimed in claim 1 , wherein obtaining the first information comprises receiving a message conveying the first information.
5. A method as claimed in claim 1 , wherein obtaining the first information comprises receiving a message conveying information provided via the communication apparatus and consulting a database on a basis of the information provided via the communication apparatus to obtain the first information.
6. A method as claimed in claim 1 , wherein performing an action related to handling of the online request comprises generating and transmitting a message indicative of whether the first information corresponds to the second information.
7. A method as claimed in claim 1 , wherein performing an action related to handling of the online request comprises:
handling the online request in a first manner if the result of said comparing is that the first information corresponds to the second information; and
handling the online request in a second manner different from the first manner if the result of said comparing is that the first information does not correspond to the second information.
8. A method as claimed in claim 1 , wherein the online request is a request for an online transaction, and wherein the action related to handling of the online request is an action related to validation of the online transaction.
9. A method as claimed in claim 8 , wherein using the logical identifier to obtain the second information comprises consulting a database on a basis of the logical identifier.
10. A method as claimed in claim 8 , wherein using the logical identifier to obtain the second information comprises:
transmitting a first message conveying the logical identifier; and
receiving a second message conveying the second information.
11. A method as claimed in claim 8 , wherein obtaining the first information comprises receiving a message conveying the first information.
12. A method as claimed in claim 8 , wherein obtaining the first information comprises receiving a message conveying transaction object information provided via the communication apparatus and consulting a database on a basis of the transaction object information provided via the communication apparatus to obtain the first information.
13. A method as claimed in claim 8 , wherein performing an action related to validation of the online transaction comprises generating and transmitting a message indicative of whether the first information corresponds to the second information.
14. A method as claimed in claim 8 , wherein performing an action related to validation of the online transaction comprises:
validating the online transaction in a first manner if the result of said comparing is that the first information corresponds to the second information; and
validating the online transaction in a second manner different from the first manner if the result of said comparing is that the first information does not correspond to the second information.
15. A method as claimed in claim 1 , wherein the online request is a request for a delivery of a product or service to a particular place.
16. A method as claimed in claim 1 , wherein the online request is a request for an access to online private content.
17. A method as claimed in claim 1 , wherein the online request is a request for an access to a private network.
18. A method as claimed in claim 1 , wherein the online request is a request for a download of data to the communication apparatus.
19. A method as claimed in claim 1 , wherein the second information comprises personal information regarding a party.
20. A method as claimed in claim 19 , wherein the personal information regarding the party comprises at least one of: a name, a gender, a date of birth or an age, a nationality, a correspondence language, a civic address, a phone number, an email address, an instant messaging identifier, and financial information.
21. A method as claimed in claim 1 , wherein the second information comprises a service point location associated with the logical identifier.
22. A method as claimed in claim 1 , wherein the second information comprises a bandwidth available to the communication apparatus.
23. An apparatus comprising:
an interface for receiving messages; and
a processing unit coupled to said interface, said processing unit being responsive to receipt of a message at said interface for:
obtaining first information, the first information relating to an online request made using a communication apparatus to which has been assigned a logical identifier used to route data associated with the online request over a packet-switched network;
using the logical identifier to obtain second information, the second information pertaining to a profile associated with the logical identifier;
comparing the first information to the second information; and
performing an action related to handling of the online request based on a result of said comparing.
24. An apparatus as claimed in claim 23 , wherein using the logical identifier to obtain the second information comprises consulting a database on a basis of the logical identifier.
25. An apparatus as claimed in claim 23 , wherein the message is a first message, and wherein using the logical identifier to obtain the second information comprises:
transmitting a second message conveying the logical identifier via said interface; and
receiving a third message conveying the second information via said interface.
26. An apparatus as claimed in claim 23 , wherein the message conveys the first information, and wherein obtaining the first information comprises processing the message to obtain the first information.
27. An apparatus as claimed in claim 23 , wherein the message conveys information provided via the communication apparatus, and wherein obtaining the first information comprises consulting a database on a basis of the information provided via the communication apparatus to obtain the first information.
28. An apparatus as claimed in claim 23 , wherein the message is a first message, and wherein performing an action related to handling of the online request comprises generating and transmitting a second message indicative of whether the first information corresponds to the second information.
29. An apparatus as claimed in claim 23 , wherein performing an action related to handling of the online request comprises:
handling the online request in a first manner if the result of said comparing is that the first information corresponds to the second information; and
handling the online request in a second manner different from the first manner if the result of said comparing is that the first information does not correspond to the second information.
30. An apparatus as claimed in claim 23 , wherein the online request is a request for an online transaction, and wherein the action related to handling of the online request is an action related to validation of the online transaction.
31. An apparatus as claimed in claim 30 , wherein using the logical identifier to obtain the second information comprises consulting a database on a basis of the logical identifier.
32. An apparatus as claimed in claim 30 , wherein the message is a first message, and wherein using the logical identifier to obtain the second information comprises:
transmitting a second message conveying the logical identifier; and
receiving a third message conveying the second information.
33. An apparatus as claimed in claim 30 , wherein the message conveys the first information, and wherein obtaining the first information comprises processing the message to obtain the first information.
34. An apparatus as claimed in claim 30 , wherein the message conveys transaction object information provided via the communication apparatus, and wherein obtaining the first information comprises consulting a database on a basis of the transaction object information provided via the communication apparatus to obtain the first information.
35. An apparatus as claimed in claim 30 , wherein the message is a first message, and wherein performing an action related to validation of the online transaction comprises generating and transmitting a second message indicative of whether the first information corresponds to the second information.
36. An apparatus as claimed in claim 30 , wherein performing an action related to validation of the online transaction comprises:
validating the online transaction in a first manner if the result of said comparing is that the first information corresponds to the second information; and
validating the online transaction in a second manner different from the first manner if the result of said comparing is that the first information does not correspond to the second information.
37. An apparatus as claimed in claim 23 , wherein the online request is a request for a delivery of a product or service to a particular place.
38. An apparatus as claimed in claim 23 , wherein the online request is a request for an access to online private content.
39. An apparatus as claimed in claim 23 , wherein the online request is a request for an access to a private network.
40. An apparatus as claimed in claim 23 , wherein the online request is a request for a download of data to the communication apparatus.
41. An apparatus as claimed in claim 23 , wherein the second information comprises personal information regarding a party.
42. An apparatus as claimed in claim 41 , wherein the personal information regarding the party comprises at least one of: a name, a gender, a date of birth or an age, a nationality, a correspondence language, a civic address, a phone number, an email address, an instant messaging identifier, and financial information.
43. An apparatus as claimed in claim 23 , wherein the second information comprises a service point location associated with the logical identifier.
44. An apparatus as claimed in claim 23 , wherein the second information comprises a bandwidth available to the communication apparatus.
45. A computer-readable medium storing a program element for execution by a computer, said program element comprising:
first program code for causing the computer to obtain first information, the first information relating to an online request made using a communication apparatus to which has been assigned a logical identifier used to route data associated with the online request over a packet-switched network;
second program code for causing the computer to use the logical identifier to obtain second information, the second information pertaining to a profile associated with the logical identifier;
third program code for causing the computer to perform a comparison of the first information to the second information; and
fourth program code for causing the computer to perform an action related to handling of the online request based on a result of the comparison.
46. A method comprising:
receiving a first message conveying a logical identifier used to route data over a packet-switched network;
consulting a database on a basis of the logical identifier to obtain information known to a service provider involved in assigning the logical identifier;
processing the information to generate a second message to be used in handling an online request made using a communication apparatus to which is assigned the logical identifier; and
transmitting the second message.
47. A method as claimed in claim 46 , wherein the information is first information, wherein the first message further conveys second information, the second information relating to the online request, wherein processing the first information comprises comparing the first information to the second information, and wherein the second message is indicative of whether the first information corresponds to the second information.
48. A method as claimed in claim 46 , wherein the second message conveys the information.
49. A method as claimed in claim 46 , wherein the online request is a request for an online transaction.
50. A method as claimed in claim 49 , wherein the information is first information, wherein the first message further conveys second information, the second information relating to the request for the online transaction, wherein processing the first information comprises comparing the first information to the second information, and wherein the second message is indicative of whether the first information corresponds to the second information.
51. A method as claimed in claim 49 , wherein the second message conveys the information.
52. A method as claimed in claim 46 , wherein the online request is a request for a delivery of a product or service to a particular place.
53. A method as claimed in claim 46 , wherein the online request is a request for an access to online private content.
54. A method as claimed in claim 46 , wherein the online request is a request for an access to a private network.
55. A method as claimed in claim 46 , wherein the online request is a request for a download of data to the communication apparatus.
56. A method as claimed in claim 46 , wherein the information pertains to a profile associated with the logical identifier.
57. A method as claimed in claim 46 , wherein the information comprises personal information regarding a party.
58. A method as claimed in claim 57 , wherein the personal information regarding the party comprises at least one of: a name, a gender, a date of birth or an age, a nationality, a correspondence language, a civic address, a phone number, an email address, an instant messaging identifier, and financial information.
59. A method as claimed in claim 46 , wherein the information comprises a service point location associated with the logical identifier.
60. A method as claimed in claim 46 , wherein the information comprises a bandwidth available to the communication apparatus.
61. An apparatus comprising:
an interface for receiving a first message conveying a logical identifier used to route data over a packet-switched network; and
a processing unit coupled to said interface, said processing unit being operative for:
consulting a database on a basis of the logical identifier to obtain information known to a service provider involved in assigning the logical identifier;
processing the information to generate a second message to be used in handling an online request made using a communication apparatus to which is assigned the logical identifier; and
causing said interface to transmit the second message.
62. An apparatus as claimed in claim 61 , wherein the information is first information, wherein the first message further conveys second information, the second information relating to the online request, wherein processing the first information comprises comparing the first information to the second information, and wherein the second message is indicative of whether the first information corresponds to the second information.
63. An apparatus as claimed in claim 61 , wherein the second message conveys the information.
64. An apparatus as claimed in claim 61 , wherein the online request is a request for an online transaction.
65. An apparatus as claimed in claim 64 , wherein the information is first information, wherein the first message further conveys second information, the second information relating to the request for the online transaction, wherein processing the first information comprises comparing the first information to the second information, and wherein the second message is indicative of whether the first information corresponds to the second information.
66. An apparatus as claimed in claim 64 , wherein the second message conveys the information.
67. An apparatus as claimed in claim 61 , wherein the online request is a request for a delivery of a product or service to a particular place.
68. An apparatus as claimed in claim 61 , wherein the online request is a request for an access to online private content.
69. An apparatus as claimed in claim 61 , wherein the online request is a request for an access to a private network.
70. An apparatus as claimed in claim 61 , wherein the online request is a request for a download of data to the communication apparatus.
71. An apparatus as claimed in claim 61 , wherein the information pertains to a profile associated with the logical identifier.
72. An apparatus as claimed in claim 61 , wherein the information comprises personal information regarding a party.
73. An apparatus as claimed in claim 72 , wherein the personal information regarding the party comprises at least one of: a name, a gender, a date of birth or an age, a nationality, a correspondence language, a civic address, a phone number, an email address, an instant messaging identifier, and financial information.
74. An apparatus as claimed in claim 61 , wherein the information comprises a service point location associated with the logical identifier.
75. An apparatus as claimed in claim 61 , wherein the information comprises a bandwidth available to the communication apparatus.
76. A computer-readable medium storing a program element for execution by a computer, said program element comprising:
first program code for causing the computer to receive a first message conveying a logical identifier used to route data over a packet-switched network;
second program code for causing the computer to consult a database on a basis of the logical identifier to obtain information known to a service provider involved in assigning the logical identifier;
third program code for causing the computer to process the information to generate a second message to be used in handling an online request made using a communication apparatus to which is assigned the logical identifier; and
fourth program code for causing the computer to transmit the second message.
77. A method as claimed in claim 1 , wherein the logical identifier comprises an IP address.
78. A method as claimed in claim 1 , wherein the second information comprises location information indicative of a location of the communication apparatus.
79. A method as claimed in claim 78 , wherein the location information comprises a service point location of the communication apparatus.
80. A method as claimed in claim 1 , wherein the second information is provided by a service provider involved in assigning the logical identifier.
81. An apparatus as claimed in claim 23 , wherein the logical identifier comprises an IP address.
82. An apparatus as claimed in claim 23 , wherein the second information comprises location information indicative of a location of the communication apparatus.
83. An apparatus as claimed in claim 82 , wherein the location information comprises a service point location of the communication apparatus.
84. An apparatus as claimed in claim 23 , wherein the second information is provided by a service provider involved in assigning the logical identifier.
85. A method as claimed in claim 46 , wherein the logical identifier comprises an IP address.
86. A method as claimed in claim 46 , wherein the second information comprises location information indicative of a location of the communication apparatus.
87. A method as claimed in claim 86 , wherein the location information comprises a service point location of the communication apparatus.
88. An apparatus as claimed in claim 61 , wherein the logical identifier comprises an IP address.
89. An apparatus as claimed in claim 61 , wherein the second information comprises location information indicative of a location of the communication apparatus.
90. An apparatus as claimed in claim 89 , wherein the location information comprises a service point location of the communication apparatus.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/226,880 US20100205652A1 (en) | 2007-06-04 | 2007-08-14 | Methods and Systems for Handling Online Request Based on Information Known to a Service Provider |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US94183007P | 2007-06-04 | 2007-06-04 | |
US12/226,880 US20100205652A1 (en) | 2007-06-04 | 2007-08-14 | Methods and Systems for Handling Online Request Based on Information Known to a Service Provider |
PCT/CA2007/001865 WO2008148183A1 (en) | 2007-06-04 | 2007-08-14 | Methods and systems for handling online requests based on information known to a service provider |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CA2007/001865 A-371-Of-International WO2008148183A1 (en) | 2007-06-04 | 2007-08-14 | Methods and systems for handling online requests based on information known to a service provider |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/488,699 Continuation US10831840B2 (en) | 2007-06-04 | 2014-09-17 | Methods and systems for handling online requests based on information known to a service provider |
Publications (1)
Publication Number | Publication Date |
---|---|
US20100205652A1 true US20100205652A1 (en) | 2010-08-12 |
Family
ID=40093096
Family Applications (14)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/298,720 Active 2030-06-16 US10482081B2 (en) | 2007-06-04 | 2007-06-27 | Methods and systems for validating online transactions using location information |
US12/226,880 Abandoned US20100205652A1 (en) | 2007-06-04 | 2007-08-14 | Methods and Systems for Handling Online Request Based on Information Known to a Service Provider |
US12/087,427 Active 2030-05-18 US10180958B2 (en) | 2007-06-04 | 2007-10-11 | Methods and computer-readable media for enabling secure online transactions with simplified user experience |
US12/227,709 Active 2033-03-05 US9430517B2 (en) | 2007-06-04 | 2007-10-26 | Methods and systems for presenting online content elements based on information known to a service provider |
US12/224,506 Active 2032-08-16 US9600518B2 (en) | 2007-06-04 | 2007-11-22 | Methods and systems for presenting online content elements based on information caused to be stored on a communication apparatus by a service provider |
US12/162,297 Abandoned US20100235279A1 (en) | 2007-06-04 | 2007-12-05 | Online transaction validation using a location object |
US12/292,745 Active 2032-03-27 US10691758B2 (en) | 2007-06-04 | 2008-11-25 | Methods and systems for presenting online content elements based on information known to a service provider |
US12/292,750 Active 2030-11-04 US10078660B2 (en) | 2007-06-04 | 2008-11-25 | Methods and systems for presenting online content elements based on information known to a service provider |
US14/488,699 Active US10831840B2 (en) | 2007-06-04 | 2014-09-17 | Methods and systems for handling online requests based on information known to a service provider |
US15/726,824 Active US10649984B2 (en) | 2007-06-04 | 2017-10-06 | Online transaction validation using a location object |
US16/247,009 Active US10885138B2 (en) | 2007-06-04 | 2019-01-14 | Methods and computer-readable media for enabling secure online transactions with simplified user experience |
US16/688,383 Active 2027-11-20 US11244018B2 (en) | 2007-06-04 | 2019-11-19 | Methods and systems for validating online transactions using location |
US17/094,244 Active 2027-11-05 US11687605B2 (en) | 2007-06-04 | 2020-11-10 | Methods and systems for handling online requests based on information known to a service provider |
US17/141,954 Active 2028-05-11 US11947607B2 (en) | 2007-06-04 | 2021-01-05 | Methods and computer-readable media for enabling secure online transactions with simplified user experience |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/298,720 Active 2030-06-16 US10482081B2 (en) | 2007-06-04 | 2007-06-27 | Methods and systems for validating online transactions using location information |
Family Applications After (12)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/087,427 Active 2030-05-18 US10180958B2 (en) | 2007-06-04 | 2007-10-11 | Methods and computer-readable media for enabling secure online transactions with simplified user experience |
US12/227,709 Active 2033-03-05 US9430517B2 (en) | 2007-06-04 | 2007-10-26 | Methods and systems for presenting online content elements based on information known to a service provider |
US12/224,506 Active 2032-08-16 US9600518B2 (en) | 2007-06-04 | 2007-11-22 | Methods and systems for presenting online content elements based on information caused to be stored on a communication apparatus by a service provider |
US12/162,297 Abandoned US20100235279A1 (en) | 2007-06-04 | 2007-12-05 | Online transaction validation using a location object |
US12/292,745 Active 2032-03-27 US10691758B2 (en) | 2007-06-04 | 2008-11-25 | Methods and systems for presenting online content elements based on information known to a service provider |
US12/292,750 Active 2030-11-04 US10078660B2 (en) | 2007-06-04 | 2008-11-25 | Methods and systems for presenting online content elements based on information known to a service provider |
US14/488,699 Active US10831840B2 (en) | 2007-06-04 | 2014-09-17 | Methods and systems for handling online requests based on information known to a service provider |
US15/726,824 Active US10649984B2 (en) | 2007-06-04 | 2017-10-06 | Online transaction validation using a location object |
US16/247,009 Active US10885138B2 (en) | 2007-06-04 | 2019-01-14 | Methods and computer-readable media for enabling secure online transactions with simplified user experience |
US16/688,383 Active 2027-11-20 US11244018B2 (en) | 2007-06-04 | 2019-11-19 | Methods and systems for validating online transactions using location |
US17/094,244 Active 2027-11-05 US11687605B2 (en) | 2007-06-04 | 2020-11-10 | Methods and systems for handling online requests based on information known to a service provider |
US17/141,954 Active 2028-05-11 US11947607B2 (en) | 2007-06-04 | 2021-01-05 | Methods and computer-readable media for enabling secure online transactions with simplified user experience |
Country Status (3)
Country | Link |
---|---|
US (14) | US10482081B2 (en) |
CA (6) | CA2689479A1 (en) |
WO (6) | WO2008148180A1 (en) |
Cited By (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090089356A1 (en) * | 2007-06-04 | 2009-04-02 | Bce Inc. | Methods and systems for presenting online content elements based on information known to a service provider |
US20090172033A1 (en) * | 2007-12-28 | 2009-07-02 | Bce Inc. | Methods, systems and computer-readable media for facilitating forensic investigations of online activities |
US20090182586A1 (en) * | 2008-01-10 | 2009-07-16 | Cohane Joseph P | Point-of-sale, value-added payment processing system and method thereof |
US20100174660A1 (en) * | 2007-12-05 | 2010-07-08 | Bce Inc. | Methods and computer-readable media for facilitating forensic investigations of online transactions |
US9009844B1 (en) | 2012-03-30 | 2015-04-14 | Emc Corporation | Methods and apparatus for knowledge-based authentication using historically-aware questionnaires |
US9021553B1 (en) | 2012-03-30 | 2015-04-28 | Emc Corporation | Methods and apparatus for fraud detection and remediation in knowledge-based authentication |
US20180005323A1 (en) * | 2016-06-30 | 2018-01-04 | Square, Inc. | Graphical user interface for tracking transactions |
US20190005285A1 (en) * | 2011-06-14 | 2019-01-03 | Ark Ideaz, Inc. | Authentication systems and methods |
US11244019B2 (en) * | 2017-06-09 | 2022-02-08 | Humada Holdings Inc. | Enrichment of user specific information |
US20230009431A1 (en) * | 2021-07-09 | 2023-01-12 | Justin L. Synstelien | Facilitating and provisioning customer broadband transport service |
US20230011720A1 (en) * | 2021-07-09 | 2023-01-12 | ReadyLinks Inc. | Bidirectional power feed digital communication device |
US11605066B2 (en) | 2016-06-30 | 2023-03-14 | Block, Inc. | Physical, logical separation of balances of funds |
US11756020B1 (en) | 2019-07-31 | 2023-09-12 | Block, Inc. | Gesture and context interpretation for secure interactions |
US11929887B2 (en) | 2021-07-09 | 2024-03-12 | ReadyLinks Inc. | Facilitating and provisioning customer broadband transport service |
Families Citing this family (73)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7912960B2 (en) * | 2005-06-20 | 2011-03-22 | Microsoft Corporation | Reciprocal public trust relationship |
US9088355B2 (en) | 2006-03-24 | 2015-07-21 | Arris Technology, Inc. | Method and apparatus for determining the dynamic range of an optical link in an HFC network |
WO2009111515A2 (en) | 2008-03-04 | 2009-09-11 | Wms Gaming, Inc. | Controlling wagering transactions for multi-provider game content |
US20110009188A1 (en) * | 2007-11-20 | 2011-01-13 | Adiraju Srinivyasa M | Controlling wagering transactions for multi-provider game content |
US10269024B2 (en) * | 2008-02-08 | 2019-04-23 | Outbrain Inc. | Systems and methods for identifying and measuring trends in consumer content demand within vertically associated websites and related content |
US20090240538A1 (en) * | 2008-03-20 | 2009-09-24 | Embarq Holdings Company, Llc | System and Method for Local Call-Based Advertising |
US20090313097A1 (en) * | 2008-06-13 | 2009-12-17 | Embarq Holdings Company, Llc | System and Method for Advertisers to Bid on Distributing Ads to Telephone Calling Parties |
US20110212785A1 (en) * | 2008-11-13 | 2011-09-01 | Wms Gaming, Inc. | Presenting content in wagering game systems |
US8271629B1 (en) * | 2008-12-02 | 2012-09-18 | ioBridge, Inc. | Module-based device interaction system |
US10756918B2 (en) | 2008-12-02 | 2020-08-25 | ioBridge, Inc. | Activating a device via a module-based device interaction system |
US9681357B1 (en) * | 2008-12-02 | 2017-06-13 | ioBridge, Inc. | System, method, and computer-readable medium for interaction with a device via a module-based device interaction system enabled for wireless communication |
US9497261B1 (en) * | 2008-12-02 | 2016-11-15 | ioBridge, Inc. | System, method, and computer-readable medium for wireless interaction with a device via a module-based device interaction system |
US20110040604A1 (en) * | 2009-08-13 | 2011-02-17 | Vertical Acuity, Inc. | Systems and Methods for Providing Targeted Content |
US9396485B2 (en) * | 2009-12-24 | 2016-07-19 | Outbrain Inc. | Systems and methods for presenting content |
DE102009039650A1 (en) * | 2009-09-02 | 2011-03-10 | Elektro-Bauelemente Gmbh | Method for energizing e.g. electrical operable vehicle in parking lot, involves sending releasing signal so that current is fed to vehicle, during correlation of characteristics with information, and metering electrical quantity |
US8526485B2 (en) | 2009-09-23 | 2013-09-03 | General Instrument Corporation | Using equalization coefficients of end devices in a cable television network to determine and diagnose impairments in upstream channels |
US20110161091A1 (en) * | 2009-12-24 | 2011-06-30 | Vertical Acuity, Inc. | Systems and Methods for Connecting Entities Through Content |
US10713666B2 (en) | 2009-12-24 | 2020-07-14 | Outbrain Inc. | Systems and methods for curating content |
US20110197137A1 (en) * | 2009-12-24 | 2011-08-11 | Vertical Acuity, Inc. | Systems and Methods for Rating Content |
US10607235B2 (en) * | 2009-12-24 | 2020-03-31 | Outbrain Inc. | Systems and methods for curating content |
US8170921B2 (en) * | 2009-12-29 | 2012-05-01 | Ebay, Inc. | Dynamic hosted shopping cart |
WO2011161787A1 (en) * | 2010-06-23 | 2011-12-29 | 富士通株式会社 | Communication apparatus, communication method, and communication program |
US8886773B2 (en) | 2010-08-14 | 2014-11-11 | The Nielsen Company (Us), Llc | Systems, methods, and apparatus to monitor mobile internet activity |
US8910259B2 (en) | 2010-08-14 | 2014-12-09 | The Nielsen Company (Us), Llc | Systems, methods, and apparatus to monitor mobile internet activity |
US8654640B2 (en) | 2010-12-08 | 2014-02-18 | General Instrument Corporation | System and method for IP video delivery using distributed flexible channel bonding |
US8458069B2 (en) * | 2011-03-04 | 2013-06-04 | Brighterion, Inc. | Systems and methods for adaptive identification of sources of fraud |
US20120296818A1 (en) * | 2011-05-17 | 2012-11-22 | Ebay Inc. | Method for authorizing the activation of a spending card |
US20120303310A1 (en) | 2011-05-26 | 2012-11-29 | First Data Corporation | Systems and Methods for Providing Test Keys to Mobile Devices |
US8937992B2 (en) | 2011-08-30 | 2015-01-20 | General Instrument Corporation | Method and apparatus for updating equalization coefficients of adaptive pre-equalizers |
US10225264B2 (en) | 2011-10-25 | 2019-03-05 | Salesforce.Com, Inc. | Automated authorization response techniques |
US10225242B2 (en) | 2011-10-25 | 2019-03-05 | Salesforce.Com, Inc. | Automated authorization response techniques |
US9210150B2 (en) | 2011-10-25 | 2015-12-08 | Salesforce.Com, Inc. | Two-factor authentication systems and methods |
WO2013063326A1 (en) | 2011-10-25 | 2013-05-02 | Toopher, Inc. | Two-factor authentication systems and methods |
US10212588B2 (en) | 2011-10-25 | 2019-02-19 | Salesforce.Com, Inc. | Preemptive authorization automation |
US20140337230A1 (en) * | 2011-12-01 | 2014-11-13 | Sk C&C Co., Ltd. | Method and system for secure mobile wallet transaction |
US9113181B2 (en) | 2011-12-13 | 2015-08-18 | Arris Technology, Inc. | Dynamic channel bonding partial service triggering |
US8620788B2 (en) * | 2012-03-09 | 2013-12-31 | Hartford Fire Insurance Company | System and method for dynamic financial account management |
US20130275547A1 (en) * | 2012-04-16 | 2013-10-17 | Kindsight Inc. | System and method for providing supplemental electronic content to a networked device |
US9065731B2 (en) | 2012-05-01 | 2015-06-23 | Arris Technology, Inc. | Ensure upstream channel quality measurement stability in an upstream channel bonding system using T4 timeout multiplier |
US8762266B2 (en) | 2012-05-08 | 2014-06-24 | Vantiv, Llc | Systems and methods for performing funds freeze and/or funds seizure with respect to prepaid payment cards |
WO2013185220A1 (en) * | 2012-06-15 | 2013-12-19 | Edatanetworks Inc. | Systems and methods for incenting consumers |
KR101634767B1 (en) * | 2012-07-18 | 2016-06-30 | 유니파이 게엠베하 운트 코. 카게 | Method of conveying a location information representing a physical location of a communication device, a computer program product for executing the method, and the communication device for conveying the location information |
US9136943B2 (en) | 2012-07-30 | 2015-09-15 | Arris Technology, Inc. | Method of characterizing impairments detected by equalization on a channel of a network |
KR101460179B1 (en) | 2012-11-28 | 2014-11-10 | 에스케이씨앤씨 주식회사 | Method for Temporary Payment Card Set-up and Mobile Device using the same |
US9973492B2 (en) * | 2012-12-25 | 2018-05-15 | At&T Mobility Ip, Llc | Unified mobile security system and method of operation |
US9197886B2 (en) | 2013-03-13 | 2015-11-24 | Arris Enterprises, Inc. | Detecting plant degradation using peer-comparison |
US9042236B2 (en) | 2013-03-15 | 2015-05-26 | Arris Technology, Inc. | Method using equalization data to determine defects in a cable plant |
US10356579B2 (en) | 2013-03-15 | 2019-07-16 | The Nielsen Company (Us), Llc | Methods and apparatus to credit usage of mobile devices |
US10477199B2 (en) | 2013-03-15 | 2019-11-12 | Arris Enterprises Llc | Method for identifying and prioritizing fault location in a cable plant |
US9025469B2 (en) | 2013-03-15 | 2015-05-05 | Arris Technology, Inc. | Method for estimating cable plant topology |
US9246892B2 (en) | 2013-04-03 | 2016-01-26 | Salesforce.Com, Inc. | System, method and computer program product for managing access to systems, products, and data based on information associated with a physical location of a user |
WO2015055975A1 (en) * | 2013-09-09 | 2015-04-23 | British Telecommunications Plc | Method and apparatus for communicating with an access node |
EP2854335A1 (en) | 2013-09-30 | 2015-04-01 | British Telecommunications public limited company | Data network management |
US9727866B2 (en) | 2013-10-15 | 2017-08-08 | Intuit Inc. | Methods systems and computer program products for verifying consumer identity during transaction |
US9978079B1 (en) * | 2013-12-20 | 2018-05-22 | Google Llc | Content selection based on connection information |
US9256752B2 (en) | 2014-01-07 | 2016-02-09 | Microsoft Technology Licensing, Llc | Product authorization with cross-region access |
JP5613855B1 (en) * | 2014-04-23 | 2014-10-29 | 株式会社 ディー・エヌ・エー | User authentication system |
WO2016020927A1 (en) * | 2014-08-04 | 2016-02-11 | Hewlett-Packard Development Company, L.P. | Event stream processing |
US9762688B2 (en) | 2014-10-31 | 2017-09-12 | The Nielsen Company (Us), Llc | Methods and apparatus to improve usage crediting in mobile devices |
US11423420B2 (en) | 2015-02-06 | 2022-08-23 | The Nielsen Company (Us), Llc | Methods and apparatus to credit media presentations for online media distributions |
US10311423B2 (en) | 2015-06-09 | 2019-06-04 | Zumigo, Inc. | System and method for transaction approval based on confirmation of proximity of mobile subscriber device to a particular location |
RU2625050C1 (en) * | 2016-04-25 | 2017-07-11 | Акционерное общество "Лаборатория Касперского" | System and method of transactions trusted declaration |
CN112990932A (en) * | 2016-06-07 | 2021-06-18 | 华为技术有限公司 | Data processing method, related device and system |
US10680843B2 (en) | 2016-12-21 | 2020-06-09 | British Telecommunications Public Limited Company | Network node |
US10812509B2 (en) * | 2017-10-30 | 2020-10-20 | Micro Focus Llc | Detecting anomolous network activity based on scheduled dark network addresses |
US10819707B1 (en) * | 2017-10-31 | 2020-10-27 | NortonLifeLock, Inc. | Systems and methods for validating a user's physical location |
FR3076032A1 (en) * | 2017-12-21 | 2019-06-28 | Orange | METHOD AND DEVICE FOR VALIDATING A PAYMENT TRANSACTION. |
US10728218B2 (en) * | 2018-02-26 | 2020-07-28 | Mcafee, Llc | Gateway with access checkpoint |
US20190303967A1 (en) * | 2018-03-30 | 2019-10-03 | Panasonic Intellectual Property Management Co., Ltd. | System and method to characterize a user of a handheld device |
US10812476B2 (en) | 2018-05-22 | 2020-10-20 | Salesforce.Com, Inc. | Authorization of another device for participation in multi-factor authentication |
US11108764B2 (en) | 2018-07-02 | 2021-08-31 | Salesforce.Com, Inc. | Automating responses to authentication requests using unsupervised computer learning techniques |
JP2020096275A (en) * | 2018-12-12 | 2020-06-18 | コネクトフリー株式会社 | Information communication method and information communication system |
US20230010577A1 (en) * | 2021-07-06 | 2023-01-12 | Capital One Services, Llc | Computer-Based System for Locking User Account Access |
Citations (78)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5903721A (en) * | 1997-03-13 | 1999-05-11 | cha|Technologies Services, Inc. | Method and system for secure online transaction processing |
US5903878A (en) * | 1997-08-20 | 1999-05-11 | Talati; Kirit K. | Method and apparatus for electronic commerce |
US6029150A (en) * | 1996-10-04 | 2000-02-22 | Certco, Llc | Payment and transactions in electronic commerce system |
US6041353A (en) * | 1997-04-22 | 2000-03-21 | Hitachi, Ltd. | Method for searching for network connection path |
US6169890B1 (en) * | 1992-11-11 | 2001-01-02 | Sonera Smarttrust Oy | Mobile telephone system and method for carrying out financial transactions using a mobile telephone system |
US20010053999A1 (en) * | 2000-06-09 | 2001-12-20 | Sony Corp./Sony Electronics, Inc. | System and method for providing customized advertisements over a network |
US6339761B1 (en) * | 1999-05-13 | 2002-01-15 | Hugh V. Cottingham | Internet service provider advertising system |
US20020010747A1 (en) * | 2000-07-21 | 2002-01-24 | Ableclick Corp. | Method for acquiring on-line information regarding customer preferences and a target advertising method using e-mail based on customer preferences |
US20020019831A1 (en) * | 2000-01-19 | 2002-02-14 | Wyly Wade | Methods, systems, and presentations for delivery over the internet |
US20020035622A1 (en) * | 2000-06-07 | 2002-03-21 | Barber Timothy P. | Online machine data collection and archiving process |
US20020069176A1 (en) * | 2000-12-06 | 2002-06-06 | Daniel Newman | System for obtaining fee-based data and services |
US20020077837A1 (en) * | 1999-12-16 | 2002-06-20 | Scott Krueger | Secure networked transaction system |
US20020107981A1 (en) * | 2001-02-06 | 2002-08-08 | International Business Machines Corporation | Internet domain names with regional associations |
US20020143655A1 (en) * | 2001-04-02 | 2002-10-03 | Stephen Elston | Remote ordering system for mobile commerce |
US20020161701A1 (en) * | 2001-04-30 | 2002-10-31 | Todd Warmack | Debit or credit card transaction clearing house system |
US6484148B1 (en) * | 2000-02-19 | 2002-11-19 | John E. Boyd | Electronic advertising device and method of using the same |
US6487538B1 (en) * | 1998-11-16 | 2002-11-26 | Sun Microsystems, Inc. | Method and apparatus for local advertising |
US20030023489A1 (en) * | 2001-06-14 | 2003-01-30 | Mcguire Myles P. | Method and system for providing network based target advertising |
US20030041240A1 (en) * | 2001-08-22 | 2003-02-27 | Jim Roskind | Single universal authentication system for internet services |
US20030105710A1 (en) * | 2000-07-11 | 2003-06-05 | Ellen Barbara | Method and system for on-line payments |
US20030140120A1 (en) * | 1999-12-01 | 2003-07-24 | Hartman Alex James | Method and apparatus for network access |
US20030172036A1 (en) * | 2002-03-05 | 2003-09-11 | Idan Feigenbaum | Online financial transaction veracity assurance mechanism |
US20030187949A1 (en) * | 2002-03-28 | 2003-10-02 | Bhatt Jaydutt B. | Determining geographic location of internet users |
US20040006489A1 (en) * | 2002-07-03 | 2004-01-08 | Bynon Douglas B. | Benefits services payment and credit system |
US6700965B1 (en) * | 2002-05-03 | 2004-03-02 | At&T Corp. | Identifier-triggered personalized customer relations management service |
US20040102197A1 (en) * | 1999-09-30 | 2004-05-27 | Dietz Timothy Alan | Dynamic web page construction based on determination of client device location |
US20040205004A1 (en) * | 2000-02-22 | 2004-10-14 | Paramvir Bahl | Methods and systems for providing variable rates of service for accessing networks, methods and systems for accessing the internet |
US20040250236A1 (en) * | 2003-04-30 | 2004-12-09 | O'malley Austin | Establishing and maintaining a relationship between a three-dimensional model and related data |
US6836765B1 (en) * | 2000-08-30 | 2004-12-28 | Lester Sussman | System and method for secure and address verifiable electronic commerce transactions |
US20050021853A1 (en) * | 1999-05-03 | 2005-01-27 | Parekh Sanjay M. | Systems and methods for determining, collecting, and using geographic locations of Internet users |
US6859791B1 (en) * | 1998-08-13 | 2005-02-22 | International Business Machines Corporation | Method for determining internet users geographic region |
US20050066339A1 (en) * | 2003-03-19 | 2005-03-24 | Thoen Gregory S. | System and method for seamlessly providing video content to client systems over a network |
US6895387B1 (en) * | 1999-10-29 | 2005-05-17 | Networks Associates Technology, Inc. | Dynamic marketing based on client computer configurations |
US20050108177A1 (en) * | 1999-07-30 | 2005-05-19 | Sancho Enrique D. | System and method for secure network purchasing |
US20050144073A1 (en) * | 2002-06-05 | 2005-06-30 | Lawrence Morrisroe | Method and system for serving advertisements |
US20050165684A1 (en) * | 2004-01-28 | 2005-07-28 | Saflink Corporation | Electronic transaction verification system |
US20050177562A1 (en) * | 2004-02-09 | 2005-08-11 | Limelight Networks, Inc. | Universal search engine |
US20050190901A1 (en) * | 2003-11-07 | 2005-09-01 | Oborn Patrick K. | System and method to determine and deliver quotes for distance-sensitive communication links from multiple service providers |
US6957393B2 (en) * | 2001-03-19 | 2005-10-18 | Accenture Llp | Mobile valet |
US20050260973A1 (en) * | 2004-05-24 | 2005-11-24 | Van De Groenendaal Joannes G | Wireless manager and method for managing wireless devices |
US20060020508A1 (en) * | 2004-07-23 | 2006-01-26 | Gorti Sreenivasa R | Proxy-based profile management to deliver personalized services |
US20060059044A1 (en) * | 2004-09-14 | 2006-03-16 | Chan Wesley T | Method and system to provide advertisements based on wireless access points |
US20060080147A1 (en) * | 2004-10-08 | 2006-04-13 | Mark Greenstein | Method of purchasing a product to avoid adverse selection |
US20060085357A1 (en) * | 2004-10-19 | 2006-04-20 | First Data Corporation | Methods and systems for performing credit transactions with a wireless device |
US20060085263A1 (en) * | 1997-06-25 | 2006-04-20 | Paul Greer | User demographic profile driven advertising targeting |
US20060111991A1 (en) * | 2002-07-08 | 2006-05-25 | Murray Wilshinsky | Confindential information sharing system |
US20060116924A1 (en) * | 1996-08-20 | 2006-06-01 | Angles Paul D | System and method for delivering customized advertisements within interactive communication systems |
US20060190287A1 (en) * | 2004-10-15 | 2006-08-24 | Rearden Commerce, Inc. | Fraudulent address database |
US7111789B2 (en) * | 2001-08-31 | 2006-09-26 | Arcot Systems, Inc. | Enhancements to multi-party authentication and other protocols |
US20060235795A1 (en) * | 2005-04-19 | 2006-10-19 | Microsoft Corporation | Secure network commercial transactions |
US20060271953A1 (en) * | 2005-01-05 | 2006-11-30 | Ronald Jacoby | System and method for delivering personalized advertisements |
US20070050481A1 (en) * | 1999-12-30 | 2007-03-01 | Rod Rigole | Systems and methods for online selection of service providers and management of service accounts |
US20070067297A1 (en) * | 2004-04-30 | 2007-03-22 | Kublickis Peter J | System and methods for a micropayment-enabled marketplace with permission-based, self-service, precision-targeted delivery of advertising, entertainment and informational content and relationship marketing to anonymous internet users |
US20070106660A1 (en) * | 2005-11-09 | 2007-05-10 | Bbnt Solutions Llc | Method and apparatus for using confidence scores of enhanced metadata in search-driven media applications |
US20070220604A1 (en) * | 2005-05-31 | 2007-09-20 | Long Kurt J | System and Method of Fraud and Misuse Detection |
US20070239546A1 (en) * | 2006-04-10 | 2007-10-11 | Scott Blum | Computer implemented interactive advertising system and method |
US7292996B2 (en) * | 2000-10-06 | 2007-11-06 | Openwave Systems Inc. | Method and apparatus for performing a credit based transaction between a user of a wireless communications device and a provider of a product or service |
US7359869B1 (en) * | 2000-07-14 | 2008-04-15 | Stamps.Com, Inc. | Method and system for facilitating secure electronic transactions with multiple merchants |
US20080095173A1 (en) * | 2006-10-19 | 2008-04-24 | Embarq Holdings Company, Llc | System and method for monitoring the connection of an end-user to a remote network |
US20080164308A1 (en) * | 2007-01-10 | 2008-07-10 | Aaron Jeffrey A | Credit card transaction servers, methods and computer program products employing wireless teminal location and registered purchasing locations |
US7411905B1 (en) * | 2003-09-05 | 2008-08-12 | Sprint Communications Company L.P. | Segmented IP backbone network access |
US20080255944A1 (en) * | 2007-03-29 | 2008-10-16 | Shah Nitin J | Campaign Management Platform for Network-Based Online Advertising and Directed Media Transmission System |
US20090172033A1 (en) * | 2007-12-28 | 2009-07-02 | Bce Inc. | Methods, systems and computer-readable media for facilitating forensic investigations of online activities |
US7630939B1 (en) * | 2001-03-26 | 2009-12-08 | Usa Technologies, Inc. | System and method for locally authorizing cashless transactions at point of sale |
US7665658B2 (en) * | 2005-06-07 | 2010-02-23 | First Data Corporation | Dynamic aggregation of payment transactions |
US20100174660A1 (en) * | 2007-12-05 | 2010-07-08 | Bce Inc. | Methods and computer-readable media for facilitating forensic investigations of online transactions |
US7778935B2 (en) * | 2006-03-09 | 2010-08-17 | Colella Brian A | System for secure payment and authentication |
US7818229B2 (en) * | 2004-10-19 | 2010-10-19 | Apollo Enterprise Solutions, Inc. | Method for future payment transactions |
US7827108B2 (en) * | 2008-11-21 | 2010-11-02 | Visa U.S.A. Inc. | System and method of validating a relationship between a user and a user account at a financial institution |
US7827101B2 (en) * | 2003-01-10 | 2010-11-02 | First Data Corporation | Payment system clearing for transactions |
US7941370B2 (en) * | 2006-04-25 | 2011-05-10 | Uc Group Limited | Systems and methods for funding payback requests for financial transactions |
US7983961B1 (en) * | 2005-10-27 | 2011-07-19 | Alvin Chang | Methods and apparatus for marketing profiling while preserving user privacy |
US20110208663A1 (en) * | 2004-03-19 | 2011-08-25 | Kennis Peter H | Extraction of transaction data for compliance monitoring |
US8032536B2 (en) * | 2002-12-19 | 2011-10-04 | Base Base Corporation | System and method for applying network protocols to telephony |
US8041717B2 (en) * | 2005-09-14 | 2011-10-18 | Jumptap, Inc. | Mobile advertisement syndication |
US8045956B2 (en) * | 2007-01-05 | 2011-10-25 | Macronix International Co., Ltd. | System and method of managing contactless payment transactions using a mobile communication device as a stored value device |
US8321278B2 (en) * | 2003-09-30 | 2012-11-27 | Google Inc. | Targeted advertisements based on user profiles and page profile |
US8566237B2 (en) * | 2002-11-01 | 2013-10-22 | Western Union Financial Services, Inc. | Internet payment system and method |
Family Cites Families (85)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5012466A (en) * | 1987-10-13 | 1991-04-30 | At&T Bell Laboratories | Call service initialization arrangement |
EP0706743B1 (en) * | 1993-06-28 | 1998-11-04 | Bellsouth Corporation | Mediation of open advanced intelligent network interface for public switched telephone network |
CA2184832A1 (en) * | 1994-03-17 | 1995-09-21 | Johannes H.A. Krist | System for real time optimization and profit depiction |
US20040243478A1 (en) * | 1996-09-04 | 2004-12-02 | Walker Jay S. | Purchasing, redemption, and settlement systems and methods wherein a buyer takes possession at a retailer of a product purchased using a communication network |
US8396811B1 (en) * | 1999-02-26 | 2013-03-12 | Syncada Llc | Validation approach for auditing a vendor-based transaction |
US8799100B2 (en) * | 1997-07-08 | 2014-08-05 | Groupon, Inc. | Retail system for selling products based on a flexible product description |
US6760746B1 (en) * | 1999-09-01 | 2004-07-06 | Eric Schneider | Method, product, and apparatus for processing a data request |
US6233616B1 (en) * | 1997-10-24 | 2001-05-15 | William J. Reid | Enterprise network management using directory containing network addresses of users obtained through DHCP to control routers and servers |
US6894994B1 (en) * | 1997-11-03 | 2005-05-17 | Qualcomm Incorporated | High data rate wireless packet data communications system |
US6327363B1 (en) * | 1998-04-17 | 2001-12-04 | Mci Worldcom, Inc. | Method and system for automated customer services |
US6385729B1 (en) | 1998-05-26 | 2002-05-07 | Sun Microsystems, Inc. | Secure token device access to services provided by an internet service provider (ISP) |
AU4517899A (en) | 1998-06-19 | 2000-01-05 | Protx Limited | Verified payment system |
US6125391A (en) * | 1998-10-16 | 2000-09-26 | Commerce One, Inc. | Market makers using documents for commerce in trading partner networks |
US7076504B1 (en) | 1998-11-19 | 2006-07-11 | Accenture Llp | Sharing a centralized profile |
US20040019560A1 (en) * | 1999-03-12 | 2004-01-29 | Evans Scott L. | System and method for debt presentment and resolution |
US7213061B1 (en) * | 1999-04-29 | 2007-05-01 | Amx Llc | Internet control system and method |
AU778101B2 (en) * | 1999-06-14 | 2004-11-18 | Integral Development Corporation | System and method for conducting web-based financial transactions in capital markets |
US8527337B1 (en) * | 1999-07-20 | 2013-09-03 | Google Inc. | Internet based system and apparatus for paying users to view content and receiving micropayments |
DE19946539B4 (en) * | 1999-09-28 | 2010-04-29 | T-Mobile Deutschland Gmbh | Method for billing Internet shops via mobile communications |
US6757691B1 (en) * | 1999-11-09 | 2004-06-29 | America Online, Inc. | Predicting content choices by searching a profile database |
US7647278B1 (en) * | 1999-12-29 | 2010-01-12 | Pitney Bowes Inc. | Method for facilitating a transaction between a merchant and a buyer |
US6363357B1 (en) * | 1999-12-29 | 2002-03-26 | Pitney Bowes, Inc. | Method and apparatus for providing authorization to make multiple copies of copyright protected products purchased in an online commercial transaction |
JP3545666B2 (en) | 2000-02-14 | 2004-07-21 | 株式会社東芝 | Service providing system for mobile terminals |
AUPQ600800A0 (en) | 2000-03-06 | 2000-03-23 | Interfusion.Net Pty Ltd | User-targeted information and advertising |
IL137591A0 (en) | 2000-03-24 | 2001-07-24 | Banco Bilbao Vizcaya Argentari | System and process for remote payments and transactions in real time by mobile telephone |
US6539392B1 (en) * | 2000-03-29 | 2003-03-25 | Bizrate.Com | System and method for data collection, evaluation, information generation, and presentation |
WO2001086546A1 (en) * | 2000-05-05 | 2001-11-15 | Crossmar, Inc. | Method and system for routing and processing financial transaction data |
US20020013827A1 (en) * | 2000-05-18 | 2002-01-31 | Edstrom Claes G.R. | Personal service environment management apparatus and methods |
US6892184B1 (en) * | 2000-06-19 | 2005-05-10 | E4X Inc. | System and method for multiple currency transactions |
US7660737B1 (en) * | 2000-07-18 | 2010-02-09 | Smartpenny.Com, Inc. | Economic filtering system for delivery of permission based, targeted, incentivized advertising |
US8087064B1 (en) * | 2000-08-31 | 2011-12-27 | Verizon Communications Inc. | Security extensions using at least a portion of layer 2 information or bits in the place of layer 2 information |
US20110219035A1 (en) * | 2000-09-25 | 2011-09-08 | Yevgeny Korsunsky | Database security via data flow processing |
GB0023570D0 (en) * | 2000-09-26 | 2000-11-08 | Volantis Systems Ltd | Web server |
AU2002232535A1 (en) | 2000-12-12 | 2002-06-24 | Nintendo Of America Inc. | System for identifying unauthorized sales and providing post-sale information to purchasers using electronic product registration |
US7937470B2 (en) * | 2000-12-21 | 2011-05-03 | Oracle International Corp. | Methods of determining communications protocol latency |
US20030006911A1 (en) * | 2000-12-22 | 2003-01-09 | The Cadre Group Inc. | Interactive advertising system and method |
US6606690B2 (en) * | 2001-02-20 | 2003-08-12 | Hewlett-Packard Development Company, L.P. | System and method for accessing a storage area network as network attached storage |
US7316819B2 (en) * | 2001-03-08 | 2008-01-08 | Unigene Laboratories, Inc. | Oral peptide pharmaceutical dosage form and method of production |
US20020198937A1 (en) * | 2001-03-09 | 2002-12-26 | Arif Diwan | Content-request redirection method and system |
US8156185B1 (en) * | 2001-05-17 | 2012-04-10 | Ibm Corporation | Method and system for monitoring the status of an online transaction |
US7849173B1 (en) * | 2001-12-31 | 2010-12-07 | Christopher Uhlik | System for on-demand access to local area networks |
US7117182B2 (en) * | 2002-01-08 | 2006-10-03 | International Business Machines Corporation | Method for disaggregating customer data in online transactions to preserve privacy |
US7228417B2 (en) * | 2002-02-26 | 2007-06-05 | America Online, Inc. | Simple secure login with multiple-authentication providers |
US7107285B2 (en) * | 2002-03-16 | 2006-09-12 | Questerra Corporation | Method, system, and program for an improved enterprise spatial system |
CA2436319C (en) * | 2002-08-02 | 2014-05-13 | Calin A. Sandru | Payment validation network |
US7640008B2 (en) * | 2002-10-18 | 2009-12-29 | Kineto Wireless, Inc. | Apparatus and method for extending the coverage area of a licensed wireless communication system using an unlicensed wireless communication system |
US7885644B2 (en) * | 2002-10-18 | 2011-02-08 | Kineto Wireless, Inc. | Method and system of providing landline equivalent location information over an integrated communication system |
CA2413340C (en) | 2002-11-29 | 2009-10-13 | Research In Motion Limited | System and method for conducting an electronic commercial transaction |
GB0307763D0 (en) * | 2003-04-04 | 2003-05-07 | Zap Corp Uk The Ltd | System and method of broadcasting advertisements |
US7401104B2 (en) * | 2003-08-21 | 2008-07-15 | Microsoft Corporation | Systems and methods for synchronizing computer systems through an intermediary file system share or device |
US7290278B2 (en) * | 2003-10-02 | 2007-10-30 | Aol Llc, A Delaware Limited Liability Company | Identity based service system |
KR100661313B1 (en) * | 2003-12-03 | 2006-12-27 | 한국전자통신연구원 | Multimedia communication system based on session initiation protocol capable of providing mobility using lifelong number |
US8041779B2 (en) * | 2003-12-15 | 2011-10-18 | Honda Motor Co., Ltd. | Method and system for facilitating the exchange of information between a vehicle and a remote location |
US7853533B2 (en) * | 2004-03-02 | 2010-12-14 | The 41St Parameter, Inc. | Method and system for identifying users and detecting fraud by use of the internet |
US7634550B2 (en) * | 2004-04-21 | 2009-12-15 | Sap Ag | Message-oriented middleware provider having multiple server instances |
US7889384B2 (en) * | 2004-06-03 | 2011-02-15 | International Business Machines Corporation | Method for more efficiently managing complex payloads in a point of sale system |
FI117587B (en) * | 2004-06-18 | 2006-11-30 | Nethawk Oyj | Method, device, and computer program product for monitoring data communications |
US7966405B2 (en) * | 2004-06-29 | 2011-06-21 | Microsoft Corporation | Session multiplex protocol |
US7730030B1 (en) * | 2004-08-15 | 2010-06-01 | Yongyong Xu | Resource based virtual communities |
US8732004B1 (en) * | 2004-09-22 | 2014-05-20 | Experian Information Solutions, Inc. | Automated analysis of data to generate prospect notifications based on trigger events |
US7885844B1 (en) * | 2004-11-16 | 2011-02-08 | Amazon Technologies, Inc. | Automatically generating task recommendations for human task performers |
US8170897B1 (en) * | 2004-11-16 | 2012-05-01 | Amazon Technologies, Inc. | Automated validation of results of human performance of tasks |
US20080307339A1 (en) * | 2006-03-20 | 2008-12-11 | Kidzui, Inc. | Child-oriented computing system |
US8079087B1 (en) * | 2005-05-03 | 2011-12-13 | Voltage Security, Inc. | Universal resource locator verification service with cross-branding detection |
CA2610216A1 (en) * | 2005-06-06 | 2006-12-14 | Sms.Ac, Inc. | Billing system and method for micro-transactions |
US7805706B1 (en) * | 2005-06-21 | 2010-09-28 | Unisys Corporation | Process for optimizing software components for an enterprise resource planning (ERP) application SAP on multiprocessor servers |
US8538875B2 (en) | 2005-11-04 | 2013-09-17 | Instamed Communications Llc | Process for linked healthcare and financial transaction initiation |
US20070174477A1 (en) * | 2006-01-20 | 2007-07-26 | Bostick James E | Communication profiles for integrated database messaging system |
WO2007092715A2 (en) * | 2006-02-06 | 2007-08-16 | Solidus Networks, Inc. | Method and system for providing online authentication utilizing biometric data |
US7516882B2 (en) * | 2006-03-09 | 2009-04-14 | Robert Cucinotta | Remote validation system useful for financial transactions |
US7814116B2 (en) * | 2006-03-16 | 2010-10-12 | Hauser Eduardo A | Method and system for creating customized news digests |
US20070276721A1 (en) * | 2006-05-25 | 2007-11-29 | Invelus Communications Llc | Computer implemented shopping system |
US7613735B2 (en) * | 2006-06-13 | 2009-11-03 | Alcatel-Lucent Usa Inc. | Method and apparatus for managing multimedia content |
JP4901334B2 (en) * | 2006-06-30 | 2012-03-21 | 株式会社東芝 | Memory controller |
US9430773B2 (en) * | 2006-07-18 | 2016-08-30 | American Express Travel Related Services Company, Inc. | Loyalty incentive program using transaction cards |
EP1887506A1 (en) * | 2006-08-10 | 2008-02-13 | Jepay SAS | Electronic commerce transaction process |
US8666809B2 (en) * | 2006-09-29 | 2014-03-04 | Google Inc. | Advertisement campaign simulator |
WO2008048634A2 (en) * | 2006-10-18 | 2008-04-24 | Wms Gaming Inc. | Wagering game with community game having a persistent-state feature |
US8914729B2 (en) * | 2006-10-30 | 2014-12-16 | Yahoo! Inc. | Methods and systems for providing a customizable guide for navigating a corpus of content |
US8108501B2 (en) * | 2006-11-01 | 2012-01-31 | Yahoo! Inc. | Searching and route mapping based on a social network, location, and time |
EP2122908A2 (en) * | 2006-11-29 | 2009-11-25 | Wisconsin Alumni Research Foundation | Method and apparatus for network anomaly detection |
US8019331B2 (en) * | 2007-02-26 | 2011-09-13 | Kineto Wireless, Inc. | Femtocell integration into the macro network |
WO2008148180A1 (en) | 2007-06-04 | 2008-12-11 | Bce Inc. | Methods and systems for validating online transactions using location information |
US8175975B2 (en) * | 2008-08-18 | 2012-05-08 | Alcatel Lucent | IMS device operable for financial transaction authorization and ID cards display |
KR20130009754A (en) * | 2010-02-01 | 2013-01-23 | 점프탭, 인크. | Integrated advertising system |
-
2007
- 2007-06-27 WO PCT/CA2007/001152 patent/WO2008148180A1/en active Application Filing
- 2007-06-27 CA CA002689479A patent/CA2689479A1/en not_active Withdrawn
- 2007-06-27 US US12/298,720 patent/US10482081B2/en active Active
- 2007-08-14 WO PCT/CA2007/001865 patent/WO2008148183A1/en active Application Filing
- 2007-08-14 US US12/226,880 patent/US20100205652A1/en not_active Abandoned
- 2007-08-14 CA CA2689863A patent/CA2689863C/en active Active
- 2007-10-11 WO PCT/CA2007/001802 patent/WO2008148182A1/en active Application Filing
- 2007-10-11 US US12/087,427 patent/US10180958B2/en active Active
- 2007-10-11 CA CA2690090A patent/CA2690090C/en active Active
- 2007-10-26 US US12/227,709 patent/US9430517B2/en active Active
- 2007-10-26 CA CA2654400A patent/CA2654400C/en active Active
- 2007-10-26 WO PCT/CA2007/001921 patent/WO2008148184A1/en active Application Filing
- 2007-11-22 WO PCT/CA2007/002119 patent/WO2008148185A1/en active Application Filing
- 2007-11-22 CA CA2689864A patent/CA2689864C/en active Active
- 2007-11-22 US US12/224,506 patent/US9600518B2/en active Active
- 2007-12-05 US US12/162,297 patent/US20100235279A1/en not_active Abandoned
- 2007-12-05 CA CA2690030A patent/CA2690030C/en active Active
- 2007-12-05 WO PCT/CA2007/002188 patent/WO2008148186A1/en active Application Filing
-
2008
- 2008-11-25 US US12/292,745 patent/US10691758B2/en active Active
- 2008-11-25 US US12/292,750 patent/US10078660B2/en active Active
-
2014
- 2014-09-17 US US14/488,699 patent/US10831840B2/en active Active
-
2017
- 2017-10-06 US US15/726,824 patent/US10649984B2/en active Active
-
2019
- 2019-01-14 US US16/247,009 patent/US10885138B2/en active Active
- 2019-11-19 US US16/688,383 patent/US11244018B2/en active Active
-
2020
- 2020-11-10 US US17/094,244 patent/US11687605B2/en active Active
-
2021
- 2021-01-05 US US17/141,954 patent/US11947607B2/en active Active
Patent Citations (80)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6169890B1 (en) * | 1992-11-11 | 2001-01-02 | Sonera Smarttrust Oy | Mobile telephone system and method for carrying out financial transactions using a mobile telephone system |
US20060116924A1 (en) * | 1996-08-20 | 2006-06-01 | Angles Paul D | System and method for delivering customized advertisements within interactive communication systems |
US6029150A (en) * | 1996-10-04 | 2000-02-22 | Certco, Llc | Payment and transactions in electronic commerce system |
US5903721A (en) * | 1997-03-13 | 1999-05-11 | cha|Technologies Services, Inc. | Method and system for secure online transaction processing |
US6041353A (en) * | 1997-04-22 | 2000-03-21 | Hitachi, Ltd. | Method for searching for network connection path |
US20060085263A1 (en) * | 1997-06-25 | 2006-04-20 | Paul Greer | User demographic profile driven advertising targeting |
US5903878A (en) * | 1997-08-20 | 1999-05-11 | Talati; Kirit K. | Method and apparatus for electronic commerce |
US6859791B1 (en) * | 1998-08-13 | 2005-02-22 | International Business Machines Corporation | Method for determining internet users geographic region |
US6487538B1 (en) * | 1998-11-16 | 2002-11-26 | Sun Microsystems, Inc. | Method and apparatus for local advertising |
US20050021853A1 (en) * | 1999-05-03 | 2005-01-27 | Parekh Sanjay M. | Systems and methods for determining, collecting, and using geographic locations of Internet users |
US20060123105A1 (en) * | 1999-05-03 | 2006-06-08 | Parekh Sanjay M | Systems and methods for determining, collecting, and using geographic locations of internet users |
US6339761B1 (en) * | 1999-05-13 | 2002-01-15 | Hugh V. Cottingham | Internet service provider advertising system |
US20050108177A1 (en) * | 1999-07-30 | 2005-05-19 | Sancho Enrique D. | System and method for secure network purchasing |
US20040102197A1 (en) * | 1999-09-30 | 2004-05-27 | Dietz Timothy Alan | Dynamic web page construction based on determination of client device location |
US6895387B1 (en) * | 1999-10-29 | 2005-05-17 | Networks Associates Technology, Inc. | Dynamic marketing based on client computer configurations |
US20030140120A1 (en) * | 1999-12-01 | 2003-07-24 | Hartman Alex James | Method and apparatus for network access |
US20020077837A1 (en) * | 1999-12-16 | 2002-06-20 | Scott Krueger | Secure networked transaction system |
US20070050481A1 (en) * | 1999-12-30 | 2007-03-01 | Rod Rigole | Systems and methods for online selection of service providers and management of service accounts |
US20020019831A1 (en) * | 2000-01-19 | 2002-02-14 | Wyly Wade | Methods, systems, and presentations for delivery over the internet |
US6484148B1 (en) * | 2000-02-19 | 2002-11-19 | John E. Boyd | Electronic advertising device and method of using the same |
US20040205004A1 (en) * | 2000-02-22 | 2004-10-14 | Paramvir Bahl | Methods and systems for providing variable rates of service for accessing networks, methods and systems for accessing the internet |
US20020035622A1 (en) * | 2000-06-07 | 2002-03-21 | Barber Timothy P. | Online machine data collection and archiving process |
US20010053999A1 (en) * | 2000-06-09 | 2001-12-20 | Sony Corp./Sony Electronics, Inc. | System and method for providing customized advertisements over a network |
US20030105710A1 (en) * | 2000-07-11 | 2003-06-05 | Ellen Barbara | Method and system for on-line payments |
US7359869B1 (en) * | 2000-07-14 | 2008-04-15 | Stamps.Com, Inc. | Method and system for facilitating secure electronic transactions with multiple merchants |
US20020010747A1 (en) * | 2000-07-21 | 2002-01-24 | Ableclick Corp. | Method for acquiring on-line information regarding customer preferences and a target advertising method using e-mail based on customer preferences |
US6836765B1 (en) * | 2000-08-30 | 2004-12-28 | Lester Sussman | System and method for secure and address verifiable electronic commerce transactions |
US7292996B2 (en) * | 2000-10-06 | 2007-11-06 | Openwave Systems Inc. | Method and apparatus for performing a credit based transaction between a user of a wireless communications device and a provider of a product or service |
US20020069176A1 (en) * | 2000-12-06 | 2002-06-06 | Daniel Newman | System for obtaining fee-based data and services |
US20020107981A1 (en) * | 2001-02-06 | 2002-08-08 | International Business Machines Corporation | Internet domain names with regional associations |
US6957393B2 (en) * | 2001-03-19 | 2005-10-18 | Accenture Llp | Mobile valet |
US7630939B1 (en) * | 2001-03-26 | 2009-12-08 | Usa Technologies, Inc. | System and method for locally authorizing cashless transactions at point of sale |
US20020143655A1 (en) * | 2001-04-02 | 2002-10-03 | Stephen Elston | Remote ordering system for mobile commerce |
US20020161701A1 (en) * | 2001-04-30 | 2002-10-31 | Todd Warmack | Debit or credit card transaction clearing house system |
US20030023489A1 (en) * | 2001-06-14 | 2003-01-30 | Mcguire Myles P. | Method and system for providing network based target advertising |
US20030041240A1 (en) * | 2001-08-22 | 2003-02-27 | Jim Roskind | Single universal authentication system for internet services |
US7111789B2 (en) * | 2001-08-31 | 2006-09-26 | Arcot Systems, Inc. | Enhancements to multi-party authentication and other protocols |
US20030172036A1 (en) * | 2002-03-05 | 2003-09-11 | Idan Feigenbaum | Online financial transaction veracity assurance mechanism |
US20030187949A1 (en) * | 2002-03-28 | 2003-10-02 | Bhatt Jaydutt B. | Determining geographic location of internet users |
US6700965B1 (en) * | 2002-05-03 | 2004-03-02 | At&T Corp. | Identifier-triggered personalized customer relations management service |
US20050144073A1 (en) * | 2002-06-05 | 2005-06-30 | Lawrence Morrisroe | Method and system for serving advertisements |
US20040006489A1 (en) * | 2002-07-03 | 2004-01-08 | Bynon Douglas B. | Benefits services payment and credit system |
US20060111991A1 (en) * | 2002-07-08 | 2006-05-25 | Murray Wilshinsky | Confindential information sharing system |
US8566237B2 (en) * | 2002-11-01 | 2013-10-22 | Western Union Financial Services, Inc. | Internet payment system and method |
US8032536B2 (en) * | 2002-12-19 | 2011-10-04 | Base Base Corporation | System and method for applying network protocols to telephony |
US7827101B2 (en) * | 2003-01-10 | 2010-11-02 | First Data Corporation | Payment system clearing for transactions |
US20050066339A1 (en) * | 2003-03-19 | 2005-03-24 | Thoen Gregory S. | System and method for seamlessly providing video content to client systems over a network |
US20040250236A1 (en) * | 2003-04-30 | 2004-12-09 | O'malley Austin | Establishing and maintaining a relationship between a three-dimensional model and related data |
US7411905B1 (en) * | 2003-09-05 | 2008-08-12 | Sprint Communications Company L.P. | Segmented IP backbone network access |
US8321278B2 (en) * | 2003-09-30 | 2012-11-27 | Google Inc. | Targeted advertisements based on user profiles and page profile |
US20050190901A1 (en) * | 2003-11-07 | 2005-09-01 | Oborn Patrick K. | System and method to determine and deliver quotes for distance-sensitive communication links from multiple service providers |
US20050165684A1 (en) * | 2004-01-28 | 2005-07-28 | Saflink Corporation | Electronic transaction verification system |
US20050177562A1 (en) * | 2004-02-09 | 2005-08-11 | Limelight Networks, Inc. | Universal search engine |
US20110208663A1 (en) * | 2004-03-19 | 2011-08-25 | Kennis Peter H | Extraction of transaction data for compliance monitoring |
US20070067297A1 (en) * | 2004-04-30 | 2007-03-22 | Kublickis Peter J | System and methods for a micropayment-enabled marketplace with permission-based, self-service, precision-targeted delivery of advertising, entertainment and informational content and relationship marketing to anonymous internet users |
US20050260973A1 (en) * | 2004-05-24 | 2005-11-24 | Van De Groenendaal Joannes G | Wireless manager and method for managing wireless devices |
US20060020508A1 (en) * | 2004-07-23 | 2006-01-26 | Gorti Sreenivasa R | Proxy-based profile management to deliver personalized services |
US20060059044A1 (en) * | 2004-09-14 | 2006-03-16 | Chan Wesley T | Method and system to provide advertisements based on wireless access points |
US20060080147A1 (en) * | 2004-10-08 | 2006-04-13 | Mark Greenstein | Method of purchasing a product to avoid adverse selection |
US20060190287A1 (en) * | 2004-10-15 | 2006-08-24 | Rearden Commerce, Inc. | Fraudulent address database |
US20060085357A1 (en) * | 2004-10-19 | 2006-04-20 | First Data Corporation | Methods and systems for performing credit transactions with a wireless device |
US8510189B2 (en) * | 2004-10-19 | 2013-08-13 | Apollo Enterprise Solutions, Inc. | Method for future payment transactions |
US7818229B2 (en) * | 2004-10-19 | 2010-10-19 | Apollo Enterprise Solutions, Inc. | Method for future payment transactions |
US20060271953A1 (en) * | 2005-01-05 | 2006-11-30 | Ronald Jacoby | System and method for delivering personalized advertisements |
US20060235795A1 (en) * | 2005-04-19 | 2006-10-19 | Microsoft Corporation | Secure network commercial transactions |
US20070220604A1 (en) * | 2005-05-31 | 2007-09-20 | Long Kurt J | System and Method of Fraud and Misuse Detection |
US7665658B2 (en) * | 2005-06-07 | 2010-02-23 | First Data Corporation | Dynamic aggregation of payment transactions |
US8041717B2 (en) * | 2005-09-14 | 2011-10-18 | Jumptap, Inc. | Mobile advertisement syndication |
US7983961B1 (en) * | 2005-10-27 | 2011-07-19 | Alvin Chang | Methods and apparatus for marketing profiling while preserving user privacy |
US20070106660A1 (en) * | 2005-11-09 | 2007-05-10 | Bbnt Solutions Llc | Method and apparatus for using confidence scores of enhanced metadata in search-driven media applications |
US7778935B2 (en) * | 2006-03-09 | 2010-08-17 | Colella Brian A | System for secure payment and authentication |
US20070239546A1 (en) * | 2006-04-10 | 2007-10-11 | Scott Blum | Computer implemented interactive advertising system and method |
US7941370B2 (en) * | 2006-04-25 | 2011-05-10 | Uc Group Limited | Systems and methods for funding payback requests for financial transactions |
US20080095173A1 (en) * | 2006-10-19 | 2008-04-24 | Embarq Holdings Company, Llc | System and method for monitoring the connection of an end-user to a remote network |
US8045956B2 (en) * | 2007-01-05 | 2011-10-25 | Macronix International Co., Ltd. | System and method of managing contactless payment transactions using a mobile communication device as a stored value device |
US20080164308A1 (en) * | 2007-01-10 | 2008-07-10 | Aaron Jeffrey A | Credit card transaction servers, methods and computer program products employing wireless teminal location and registered purchasing locations |
US20080255944A1 (en) * | 2007-03-29 | 2008-10-16 | Shah Nitin J | Campaign Management Platform for Network-Based Online Advertising and Directed Media Transmission System |
US20100174660A1 (en) * | 2007-12-05 | 2010-07-08 | Bce Inc. | Methods and computer-readable media for facilitating forensic investigations of online transactions |
US20090172033A1 (en) * | 2007-12-28 | 2009-07-02 | Bce Inc. | Methods, systems and computer-readable media for facilitating forensic investigations of online activities |
US7827108B2 (en) * | 2008-11-21 | 2010-11-02 | Visa U.S.A. Inc. | System and method of validating a relationship between a user and a user account at a financial institution |
Cited By (31)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9600518B2 (en) | 2007-06-04 | 2017-03-21 | Bce Inc. | Methods and systems for presenting online content elements based on information caused to be stored on a communication apparatus by a service provider |
US10482081B2 (en) | 2007-06-04 | 2019-11-19 | Bce Inc. | Methods and systems for validating online transactions using location information |
US11687605B2 (en) * | 2007-06-04 | 2023-06-27 | Bce Inc. | Methods and systems for handling online requests based on information known to a service provider |
US10078660B2 (en) | 2007-06-04 | 2018-09-18 | Bce Inc. | Methods and systems for presenting online content elements based on information known to a service provider |
US20100174649A1 (en) * | 2007-06-04 | 2010-07-08 | Bce Inc. | Methods and systems for validating online transactions using location information |
US20090089357A1 (en) * | 2007-06-04 | 2009-04-02 | Bce Inc. | Methods and systems for presenting online content elements based on information known to a service provider |
US20210056152A1 (en) * | 2007-06-04 | 2021-02-25 | Bce Inc. | Methods and systems for handling online requests based on information known to a service provider |
US20090089356A1 (en) * | 2007-06-04 | 2009-04-02 | Bce Inc. | Methods and systems for presenting online content elements based on information known to a service provider |
US10691758B2 (en) | 2007-06-04 | 2020-06-23 | Bce Inc. | Methods and systems for presenting online content elements based on information known to a service provider |
US20100174660A1 (en) * | 2007-12-05 | 2010-07-08 | Bce Inc. | Methods and computer-readable media for facilitating forensic investigations of online transactions |
US20090172033A1 (en) * | 2007-12-28 | 2009-07-02 | Bce Inc. | Methods, systems and computer-readable media for facilitating forensic investigations of online activities |
US20090182586A1 (en) * | 2008-01-10 | 2009-07-16 | Cohane Joseph P | Point-of-sale, value-added payment processing system and method thereof |
US20190005285A1 (en) * | 2011-06-14 | 2019-01-03 | Ark Ideaz, Inc. | Authentication systems and methods |
US11657241B2 (en) * | 2011-06-14 | 2023-05-23 | Ark Ideaz, Inc. | Authentication systems and methods |
US20220164556A1 (en) * | 2011-06-14 | 2022-05-26 | Ark Ideaz, Inc. | Authentication Systems and Methods |
US20230281406A1 (en) * | 2011-06-14 | 2023-09-07 | Ark Ideaz, Inc. | Authentication Systems and Methods |
US11048894B2 (en) * | 2011-06-14 | 2021-06-29 | Ark Ideaz, Inc. | Authentication systems and methods |
US11281875B2 (en) * | 2011-06-14 | 2022-03-22 | Ark Ideaz, Inc. | Authentication systems and methods |
US9021553B1 (en) | 2012-03-30 | 2015-04-28 | Emc Corporation | Methods and apparatus for fraud detection and remediation in knowledge-based authentication |
US9009844B1 (en) | 2012-03-30 | 2015-04-14 | Emc Corporation | Methods and apparatus for knowledge-based authentication using historically-aware questionnaires |
US11605066B2 (en) | 2016-06-30 | 2023-03-14 | Block, Inc. | Physical, logical separation of balances of funds |
US11657448B2 (en) | 2016-06-30 | 2023-05-23 | Block, Inc. | Physical, logical separation of balances of funds |
US10460395B2 (en) * | 2016-06-30 | 2019-10-29 | Square, Inc. | Graphical user interface for tracking transactions |
US20180005323A1 (en) * | 2016-06-30 | 2018-01-04 | Square, Inc. | Graphical user interface for tracking transactions |
US11244019B2 (en) * | 2017-06-09 | 2022-02-08 | Humada Holdings Inc. | Enrichment of user specific information |
US11756020B1 (en) | 2019-07-31 | 2023-09-12 | Block, Inc. | Gesture and context interpretation for secure interactions |
US20230009431A1 (en) * | 2021-07-09 | 2023-01-12 | Justin L. Synstelien | Facilitating and provisioning customer broadband transport service |
US20230011720A1 (en) * | 2021-07-09 | 2023-01-12 | ReadyLinks Inc. | Bidirectional power feed digital communication device |
US11558264B1 (en) * | 2021-07-09 | 2023-01-17 | ReadyLinks Inc. | Facilitating and provisioning customer broadband transport service |
US11750407B2 (en) * | 2021-07-09 | 2023-09-05 | ReadyLinks Inc. | Bidirectional power feed digital communication device |
US11929887B2 (en) | 2021-07-09 | 2024-03-12 | ReadyLinks Inc. | Facilitating and provisioning customer broadband transport service |
Also Published As
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11687605B2 (en) | Methods and systems for handling online requests based on information known to a service provider | |
US11798003B2 (en) | Methods and computer-readable media for facilitating forensic investigations of online transactions | |
US20090172033A1 (en) | Methods, systems and computer-readable media for facilitating forensic investigations of online activities | |
US7225156B2 (en) | Persistent dynamic payment service | |
KR20040069339A (en) | Method and system for secure handling of electronic business transactions on the internet | |
US20130282567A1 (en) | Method and System for Secure Mobile Remittance | |
KR20100054003A (en) | System and method for approving cash withdrawal without financial mass and program recording medium | |
KR20030076764A (en) | An entity authentication via the internet and a method for opening on-line share account using this | |
CA2633227A1 (en) | Methods, systems and computer-readable media for facilitating forensic investigations of online activities | |
KR101139648B1 (en) | System and Method for Providing Money Transfer Service Between Banking Agency by Using Internet, Program Recording Medium | |
KR20090001584A (en) | System and method for sdt international payment service | |
KR20090019033A (en) | System and method for difference computing of loan interest classified by banking channel and program recording medium | |
KR20090085566A (en) | System for integrated payment of trade transaction service and program recording medium | |
KR20090083887A (en) | System for managing lottery present by using non-faced channel | |
KR20100036460A (en) | System and method for managing virtual cyber branch and recording medium | |
KR20090029252A (en) | System for supporting loan with edi(electronic data interchange) service |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: BCE INC., CANADA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BOUCHARD, JEAN;FORTIER, STEPHANE MAXIME FRANCOIS;MURRRAY, SEAN MACLEAN;SIGNING DATES FROM 20080212 TO 20080214;REEL/FRAME:021780/0743 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |