WO2002025892A2 - An apparatus for facilitating realtime information interexchange between a telecommunications network and a service provider - Google Patents
An apparatus for facilitating realtime information interexchange between a telecommunications network and a service provider Download PDFInfo
- Publication number
- WO2002025892A2 WO2002025892A2 PCT/US2001/029505 US0129505W WO0225892A2 WO 2002025892 A2 WO2002025892 A2 WO 2002025892A2 US 0129505 W US0129505 W US 0129505W WO 0225892 A2 WO0225892 A2 WO 0225892A2
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- information
- engine
- realtime
- module
- service provider
- Prior art date
Links
Classifications
-
- 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
- G06Q50/00—Systems or methods specially adapted for specific business sectors, e.g. utilities or tourism
- G06Q50/10—Services
-
- 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
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F15/00—Digital computers in general; Data processing equipment in general
- G06F15/16—Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
-
- 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/9537—Spatial or temporal dependent retrieval, e.g. spatiotemporal queries
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/52—Network services specially adapted for the location of the user terminal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/535—Tracking the activity of the user
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/55—Push-based network services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/40—Network security protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
- H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
- H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
- H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
- H04W28/18—Negotiating wireless communication parameters
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
Definitions
- ISP Internet Service Provider
- content providers on the Internet forward their content, along with advertisements or other commercial information, through the ISP directly to the user.
- ISPs currently maintain cache, e.g., Yahoo and America On Line (AOL) by providing additional content
- AOL America On Line
- U.S. Pat. No. 5,930,699 generally describes providing information about a business based on a location of a mobile station. The cell identity is determined by the system and information regarding a business in that area is sent to the mobile station.
- an object of the present invention to provide a new system and methodology for mobile Internet usage, which offer more value to the telecommunications network operators and better exploits technological advantages of the network.
- the enabler described herein leverages the realtime capabilities of a telecommunications network. It is an additional object of the present invention that the enabler better personalize services based upon user situation, e.g., user mobility.
- the present invention is directed to a Business-to- Business (B2B) engine, apparatus and method for facilitating information interexchange between a telecommunications network and an information service provider.
- the B2B engine includes an interface module for interfacing with the telecommunications network and with the information service provider.
- the interface module allows the B2B engine to receive realtime information from the telecommunications network and provide the realtime information to the information service provider.
- the B2B engine includes a processor that controls the operation of the B2B engine and at least one application module interconnected to the processor that enhances the monitoring and realtime information retrieval of mobile terminals within the telecommunications network.
- the B2B engine also facilitates the reporting of the realtime information within the telecommunications network to the information service provider, thereby enabling content data and/or services to be provided to the mobile terminal .
- FIGURE 1 illustrates a conventional telecommunications system for providing a variety of Internet-based content to a subscriber
- FIGURE 2 illustrates a telecommunications system in accordance with the principles of the present invention, providing a business-to-business engine interfacing with external content providers and providing realtime subscriber information thereto;
- FIGURE 3 further illustrates the telecommunications system of FIGURE 2, demonstrating the interaction between telecommunications operators and the content providers by way of the business-to-business engine in accordance with the present invention
- FIGURE 4 illustrates a preferred embodiment of the present invention illustrated in FIGURES 2 and 3, demonstrating the interaction between mobile telecommunications operators and content providers using the business-to-business engine;
- FIGURE 6 illustrates an architecture of a number of application modules in a preferred embodiment of the present invention
- FIGURE 7 illustrates an alternate architecture for the application modules from that shown in FIGURE 6 in accordance with another embodiment of the present invention
- FIGURE 8 is a flow diagram illustrating a flow of signals employed in user subscription initialization
- FIGURE 9 illustrates a preferred interface between a portal and user equipment through the B2B engine of the present invention
- FIGURE 10 is a flow diagram illustrating a number of signals employed in initiating an "OFF" trigger pursuant to the teachings of the present invention
- FIGURE 11 is another flow diagram illustrating a flow of signals for an event occurring in a telecommunication system in accordance with the teachings of the present invention.
- FIGURE 12 is a flow diagram illustrating a user-on indication to the B2B engine of the present invention.
- FIGURE 13 is a flow diagram illustrating a location area update to the B2B engine of the present invention
- FIGURE 14 illustrates an architecture in a preferred embodiment of the present invention, demonstrating a number of interactions between the B2B engine and several network nodes;
- FIGURE 15 illustrates an example of network node notification to the B2B engine
- FIGURE 16 illustrates the communications of realtime information associated with mobile subscriber from various network elements to the B2B engine in accordance with the teachings of the present invention
- FIGURE 17 illustrates a number of the protocols used in connection with the present invention, particularly between the B2B engine and several network nodes;
- FIGURE 18 illustrates an exemplary configuration and interworking of a B2B engine with different network architectures. DETAILED DESCRIPTION OF THE PRESENTLY PREFERRED EXEMPLARY EMBODIMENTS
- FIGURE 1 illustrates a conventional telecommunications system that supplies information to telecom subscribers.
- the contents of the restaurant and weather information, 105 and 110 are supplied from the content providers to the end users directly.
- the telecom operators 120 are only pipe providers passing the information to the end users, akin to many current ISPs.
- the telecom operators 120 do not share any realtime information 130 about the user with the content providers and are only a means to pass information one-way from the content providers directly to the users who, of course/ operate in realtime.
- the serving mobile telecommunication network already knows the approximate location of the mobile subscriber, since the serving mobile telecommunications network merely act as a conduit for communicating such information, the mobile subscriber nevertheless has to manually provide the location information to the Internet content provider.
- the B2B engine 210 is connected to a telecommunication system 230 and to the Internet 250.
- the telecommunication system 230 preferably includes a wireless service provider or any service provider that services a number of subscriber or user terminals, e.g., cellular phones, personal data assistants (PDAs) or any wireless or wireline communications device or equipment capable of receiving signals.
- the B2B engine 210 is coupled, via a link 248 to the Internet, generally designated by the reference numeral 250, which includes content provider applications that supply information to users pro-actively. The supplied information may be found at and forwarded from a weather server 260, a financial server 262, a news server 264 and/or an ad server 266, via a respective link 252 to the Internet 250, which provides the gateway for the respective services.
- the telecom operators 120 are mobile operators, e.g., in accordance with the Global Subscriber Mobile (GSM) system, Personal Communication System (PCS) or other mobile telecommunication standard.
- GSM Global Subscriber Mobile
- PCS Personal Communication System
- the B2B engine 210 resident within the mobile network maintains the realtime information exchange between the mobile operators 120 and the respective content providers, e.g., the aforedescribed restaurant information 105, weather information 110 and portals 115.
- a preferred embodiment of the present invention integrates a realtime system, e.g., the aforementioned telecom operator 120, and a non-realtime system, e.g., content providers, using the business-to-business (B2B) engine 210 of the present invention.
- the B2B engine 210 communicates with the respective telecom operators 120 and the associated network elements to get realtime information about their subscribers, processes the subscriber information and supplies the information to the content providers in accordance with the certain subscribed events previously requested by those content providers.
- FIGURE 5 there are illustrated exemplary interactions between the business-to-business
- B2B engine 210 of the present invention and different elements of the network.
- Realtime systems 270 such as wireless communication systems, wire line communication systems and ISPs, interface with the B2B engine 210 to provide realtime information about subscribers and end users to the B2B engine 210.
- Content providers 272 are coupled to the B2B engine 210 to get realtime information from the B2B engine 210 and the behavior information of subscribers .
- the content providers 272 also provide information to an end user, e.g., a wireless communication subscriber, a wire line subscriber or an ISP subscriber and designated generally by reference numeral 274, through the B2B engine 210.
- application modules and services associated with the B2B engine can independently generate and provide certain desired services to those monitored mobile subscribers. Accordingly, a number of B2B developers 278 develop and update application modules in the B2B engine 210 to support new services and/or enhance existing services.
- B2B engine 210 into a telecommunications network having various protocols of operation will entail creation of a variety of databases, interfaces and portals necessary to facilitate the flow and interexchange of information.
- a user's preferences may be stored in a preferences database and trigger conditions or events
- the wireless Internet subscriber uses the time of arrival, e.g., via plane, to initiate a variety of actions to facilitate coordination of travel needs. If time zone changes occur, an alert may be generated confirming the subscriber of the time change .
- all those desired events are subscribed with the B2B Engine by content providers.
- the B2B Engine thereafter communicates with the serving mobile telecommunications network and determines that a particular event has occurred for a mobile subscriber and communicates such triggering event with the subscribed content provider to enable the content provider to automatically effectuate all those services.
- B2B business-to-business
- FIGURE 6 there are illustrated a variety of business-to-business (B2B) engine 210 application modules 220 in a preferred embodiment of the present invention.
- the B2B engine application module 220 includes a variety of discrete modules, each having an important role in the system.
- the B2B application modules 220 include an Interface module (IM) 280, a Data Collection Module (DCM) 282, a Behavior Analysis Module (BAM) 284, a Service Development Environment (SDE) 286, a Realtime Delivery Module (RDM) 288, a Rules Development
- IM Interface module
- DCM Data Collection Module
- BAM Behavior Analysis Module
- SDE Service Development Environment
- RDM Realtime Delivery Module
- the aforementioned Interface Module (IM) 280 is responsible for interfacing the application modules 282-296 with the content providers and the telecommunication systems.
- the IM 280 interfaces with several external components, such as different telecommunication systems and ISPs.
- the IM 280 also provides an interface with the content providers.
- One of the primary functions of the IM 280 is to link external components in the network to the application modules in the B2B engine. 210.
- the IM 280 internally interfaces with the Data Collection Module (DCM) 282 and the Realtime Delivery Module (RDM) 288. It should, of course, be understood that the IM 280 also could be interfaced with other internal modules, as well as external components of the network, depending on the system requirements .
- DCM Data Collection Module
- RDM Realtime Delivery Module
- the Data Collection module (DCM) 282 is responsible for retrieving and storing realtime data from telecommunication systems and ISPs.
- the DCM 282 internally interfaces with the Business Data Subscription Module (BDSM) 292 to find out about data subscriptions from the content providers.
- the DCM 282 also interfaces with the Behavior Analysis Module (BAM) 284 and with the Realtime Delivery Module (RDM) 288 to deliver realtime information to the content providers .
- BDSM Business Data Subscription Module
- BAM Behavior Analysis Module
- RDM Realtime Delivery Module
- the Rules Development Environment (RDE) 290 allows the development of rules used for the development of services.
- the RDE 290 stores the rules in a Rule Repository (Rrep) .
- the rules could be constantly updated to suite new services being adopted and varied according to the preferences of various components in the system.
- the Service Development Environment (SDE) 286 allows telecom operators or end users to develop new sets of services based on a set of rules.
- the SDE 286 is internally interfaced with the Rule Repository to develop services and with the Service Execution Module (SEM) 294.
- the Service Execution Module (SEM) 294 executes the service used, and is internally interfaced with the SDE 286 and the BDSM 292.
- the Business Data/End User Subscription Module (BDSM) 292 allows the content providers to subscribe to realtime and behavioral data, and also allows end users to subscribe to the services. To do that, the BDSM 292 is internally interfaced with the RDM 288.
- the Performance and Charging Module (PACM) 296 is responsible for collecting statistics, keeping track of the number of times realtime data was requested by the content providers and the number of subscribers accessing their services.
- the PACM 296 also keeps track of other statistical data that could be helpful to fully utilize the network and its performance.
- the PACM 296 also produces charging for post processing.
- the Operation and Maintenance Module (OAMM) 298 is responsible for managing and configuring the B2B engine 210.
- the OAMM 298 is capable of configuring the content providers, maintaining the B2B engine, handling faults in the system, and managing the security issues in the system, as well as other operational and maintenance functionalities.
- the IM 315 Upon reception of a subscription event from a portal, by the B2B engine Interface Module (IM) 315, the IM 315 interfaces with the Validation Module (VM) 345 to validate this subscription event.
- the VM 345 interfaces with the data collection module (DCM) 350, which allows the submission of the subscriber identity and allows the storage of the events in a subscription database (SD) .
- SD subscription database
- the SD must be secure and preferably scalable to allow expansion to the number of subscribers.
- the DCM 350 also is responsible for informing the portal that the subscribed user has been successfully registered in the B2B engine 310 database. Events received from the network nodes indicating the status of the mobile subscriber, arrive at the Interface Module and processed at the Event Reception and Processing Module (ERPM) 330. These events are validated using the Validation Module (VM) 345, by accessing the subscribed user preference in the SD, which is done to ensure that the user is a registered B2B engine 310 subscriber.
- ERPM Event
- the event ' is packed and a notification is sent to the portal, using the Event Forwarding Module (EFM) 355, via a highly secure HTTP notification message.
- EMF Event Forwarding Module
- CM Charging Module
- the B2B engine 364 receives the event notification 370 and processes the information therein. Th s internal validation is done in a preferred embodiment using a layered architecture, such as also discussed in connection with FIGURES 6 and 7.
- a first layer or class generally designated by the reference numeral 372
- requests establishment of a new connection step 374.
- a second layer or class 766 inserts this subscription event (step 378) in a third layer or class 380 which validates the user identification number (MSISDN) (step 382) and stores (step 384) the subscription information in a database.
- MSISDN user identification number
- an acknowledgment is sent (step 386) to the portal 362 regarding the subscription event notification 370, preferably using an HTTP protocol .
- the B2B engine thereafter monitors the requested realtime information associated with that particular mobile subscriber.
- the SIM toolkit 434 which resides in the mobile station 430 is used for value-added services and e-commerce using the mobile station, enabling transactions over the Internet. For example, using a SIM toolkit-enabled mobile station, a user may be able to check their bank account, pay bills, and all other services achieved by today' s wire line Internet access.
- the SIM toolkit 434 is preferably programmed into a SIM card, designated generally in FIGURE 9 by the reference numeral 436, and additionally enables an interface between the network and the end user.
- a preferred embodiment of the Mobile Equipment (ME) /Subscriber Interface Module (SIM) interaction with the B2B engine will be described hereinafter with reference to FIGURES 10-13.
- a Mobile Station generally designated by the reference numeral 452, includes a Subscriber Identification Module (SIM) toolkit 454 located therein.
- the SIM toolkit 454 transmits, with a determined intervals, short message service (SMS) messages, generally designated in the figure by the reference numeral 456, containing the subscriber status and the mobile station 452 ISDN number (MSISDN) .
- SMS short message service
- MSISDN mobile station ISDN number
- the SIM toolkit 454 performs this action to keep an associated B2B engine 458 informed of the realtime information and location of the MS 452. Receipt of this message initiates a timer 460 for the B2B engine 458. If the timer 474 does not expire and another message is received before expiration, within the predetermined time interval, the timer is reset.
- the B2B engine 458 will assume that the mobile station 452 has been turned off, e.g., sometime after transmission of SMS message 462 to the B2B engine 458. This, as an example, could be an indication that the user is busy or asleep and that no new contents should be sent by the portal to the subscribed user.
- a subscribed end user enters information and preferences (step 504) at a portal 502, particularly, into a portal database.
- a SIM application is initialized for realtime services and over the air activation for a subscribed user, and a plurality of SIM data is downloaded (step 506) from the portal database to a Short Message Switching Center (SMSC) 508, e.g., over an air interface.
- SMSC Short Message Switching Center
- ME Mobile Equipment
- a SIM toolkit generally designated by the reference numeral 516, which resides in the mobile equipment 512, sends an SMS message 518 informing a B2B engine 520 of the subscribed user's status and providing the user's MSISDN number.
- the aforementioned SMS message 518 is unpacked (step 524) in the B2B engine 520 by the socket listener 522, which then creates a new event (step 526) based on the information provided in the SMS message 518.
- a second layer or class generally designed by the reference numeral 528 in the B2B engine 520, upon receipt of the new event information 526, then establishes a new connection 830 and validates 532 the event subscribed 526 by comparing the user identity and preferences with what is stored in a B2B database, generally designated by the reference numeral 534.
- a third layer or class generally designated in the figure by the reference numeral ' 536, processes the event (step 538) and optionally stores the modified information in the B2B database 534.
- the processed event 538 information is forwarded by the third class 536 to a fourth class 540.
- An event notification message 542 is sent to the portal 502 by the fourth layer 540 in the B2B engine 520, informing the portal 502 that an event was received and providing the portal 802 with the user's MSISDN.
- the portal 502 upon receipt of the event notification message 542 then sends an acknowledge message 544 to the B2B engine 520, acknowledging the reception of the event notification 542 , preferably using an HTTP protocol.
- charging 546 occurs for all information provided, and charging 546 for the realtime event information provided to the portal 502 will occur after the acknowledgment message 544.
- the charging record will be created in the B2B Engine which will log all the relevant information related to the event.
- information is preferably delivered by the portal 502 to the end user at the ME 512 using an SMS message. It should, of course, be understood that the contents could alternatively be sent using a Wireless Application protocol (WAP) , using a WAP over an SMS message or other such protocols .
- WAP Wireless Application protocol
- the subscribed user employs Mobile Equipment (ME) 512, sometimes referred to as a mobile station, which includes a SIM card 514, on which a SIM application is programmed and running.
- a B2B engine 520 client application resides on the Subscriber Identification Module (SIM) and is responsible for reporting realtime events occurring within the mobile equipment (ME) /Network entity to the B2B engine 820 server node.
- SIM Subscriber Identification Module
- the client application uses triggers from the SIM card 514 to invoke a SIM toolkit operation 516 to send Short Messages to the B2B engine server 520 with information on the realtime events happening in the ME-Network.
- the short message sent is addressed to the B2B engine and the mobile telecommunication operator acts as conduit to this information sent.
- the SIM Application toolkit 516 provides mechanisms which allow applications, existing in the SIM 514, to interact and operate with the Mobile Equipment (ME) 512 download the ME profile to the SIM 514, download data (step 506) to the SIM 514, transfer a user's menu selection to the SIM 514, call control by the SIM 514, MO Short Message control by the SIM 514 and security.
- the proactive SIM 514 could display text, play a tone, send a short message, set up a call, etc., as is understood in the art.
- FIGURES 12 and 13 illustrate a preferred embodiment of the SIM/mobile entity reporting events to the B2B engine for realtime services.
- the B2B engine is updated of such a change by the mobile Equipment (ME) .
- the exemplary events that are reported to the B2B engine server are the ON/OFF, Cell Global Identity (CGI) and the location area (LA) change.
- a timing diagram generally designated in the figure by the reference numeral 550, of a user "ON" indication to a B2B engine 552.
- a given Mobile Equipment (ME) 554 first initializes an associated SIM 556. This initialization (step 558) is done by activating and testing the SIM device 556 to ascertain what functions are supported. At present, this SIM 856 initialization is preferably performed pursuant to a GSM 11.11 standard, although it is understood that alternative initialization protocols may be alternatively used.
- the identification of a proactive SIM 556 is done at this stage by having the proactive SIM service activated in a SIM service table (step 560) .
- the proactive SIM 556 shall not send proactive SIM-related commands to the ME, and vice versa.
- the ME 554 shall then send a STATUS command (step 562) periodically to the proactive SIM 556 during idle mode, as well as during a call, thereby enabling the proactive SIM 556 to respond with a command since the ME 554 always initiates commands to the SIM 556.
- the first message sent is the STATUS message (step 564) , which is used to trigger (step 564) the appropriate B2B engine 552 client application residing on the SIM card.
- the client application reads appropriate files on the SIM 556 and packs the relevant information into a short message and requests the SIM to send it onwards to the ME (step 570) .
- the SIM 856 sends a message (step 566) informing the ME 554 that further information is available.
- the ME 554 then responds using a FETCH command (step 568) to get the information from the SIM 556.
- the SIM 556 upon receipt of the aforementioned FETCH command 568, sends the composed short message from the client application to the ME 554 (step 570A) in order for the information to be sent to the B2B engine. Following that, the ME 554 sends the short message (step 572) to the B2B engine, informing that the MS 554 has been turned on. The B2B engine 552 receives this message and interprets it further to provide enhanced services. The ME 554 then responds to the SIM 556 informing that the message regarding the event has been sent (step 574) . The SIM 556, in turn, acknowledges the response and sends a normal ending message (step 576) .
- Mobile Equipment 554 may also communicate using other packet based protocols, such as USSD messages or WAP.
- the ME forwards a set location update status message (step 586) to the SIM 856, and then informs the client application residing in the SIM, via an envelope command (step 588), that the location area update has occurred.
- the client application is triggered 588A and takes this data from the envelope command, reads and adds appropriate data from the SIM 556 and packs a short message.
- This packed short message is sent (step 590) by the client application to the SIM 556, as indicated in FIGURE 13, in step 590A the SIM informs the ME of the request to send a short message.
- the ME asks the SIM to provide the data for the short message which it does in 593.
- the ME transmits the packed short message to the B2B engine (step 594) which uses the data to provide enhanced services.
- the ME 554 then as usual informs the SIM 556 that the short message has been sent (step 596) and the SIM 556 returns a normal ending message (step 598) .
- the updated information is sent to the B2B engine by the mobile station to update its status and preferences in the B2B engine, as described hereinabove.
- the network nodes self monitor any desired subscriber events update and automatically provide the data to the B2B engine on a realtime basis.
- the HLR client application Upon any update to the user status or any change regarding the user in a database, the HLR client application is triggered and sends an update to the B2B engine informing the engine of such a change.
- This client application in the HLR is adapted to recognize any change and automatically report this change to the B2B engine.
- All network nodes are also programmed to recognize any event and notify the B2B engine of this event, using the triggering mechanism of the client application.
- the MSC/VLR tracks the mobility of the user and upon a detected change, for example the user location is changed, the MSC/VLR client application is triggered and informs the B2B engine of this change.
- the MSC could work together with the MPC to pin-point the user location and send the information to the B2B engine.
- the MSC/VLR client application is programmed to interact with the RNS to inform the B2B engine of any handover or radio triggers occurring related to the user.
- the RNS also contains a client application as in all involved network
- the B2B engine then performs the necessary operations on this information and acts accordingly.
- the client application catches a trigger event in the network nodes (i.e. HLR, MSC/VLR, etc.) representing any change to the subscriber status
- the client application in the network nodes informs the B2B engine .
- the B2B engine 210 as described hereinabove could receive information/events regarding the subscribed user from the network nodes without requesting this information.
- these network nodes are requested to gather realtime information about the subscribed user.
- a Home Location Register (HLR) 610 is polled to determine the registration information of the mobile subscriber, e.g., using Mobile Application Part (MAP), TCP/IP or like protocols.
- MAP Mobile Application Part
- the B2B engine 210 interfaces with communication nodes in the network 600 to request information about the subscribed events from these nodes.
- the B2B engine 210 polls a Mobile Switching Center (MSC) /Visitor Location Register (VLR) 615 to request the mobility information, VLR record and the call control of related events to a subscriber, e.g., using Message TCP/IP or like protocols.
- MSC Mobile Switching Center
- VLR Visitor Location Register
- the B2B Engine when the B2B Engine requires certain information such as subscriber's status from the HLR, a message is sent to the HLR requesting the information. The HLR will inturn respond with the response message informing the B2B engine of the current subscriber status. This same requesting mechanism could be used with the other network nodes.
- a message could be sent by the B2B engine to any network node requesting information about the subscriber. Upon reception of such a message the network node gets the information and sends it to the B2B engine.
- the B2B engine could act as a GSM Service Control Function (gsmSCF) node and interrogates the HLR at regular or periodic intervals to get the status and the location information of a subscriber.
- gsmSCF GSM Service Control Function
- FIGURE 18 illustrates the B2B engine interfacing with different network architectures.
- the B2B engine interfaces with a 2.5G wireless telecommunications system 710 as shown in this figure and in previous Figure 14.
- the B2B engine could be interfaced with other systems such as a second generation (2G) wireless telecommunications operator system 730. It also can be interconnected with a 3G wireless telecommunications system 750 which is currently under development.
- 2G second generation
- 3G wireless telecommunications system 750 which is currently under development.
- the system architectures that are connected to the B2B engine are different, the same procedure could be used with each network node in the system, as was described hereinabove.
- the portal and content aggregators are externally connected to the B2B engine, as described herein.
- the portal and/or content aggregators in a preferred embodiment of- the presently claimed invention, may be incorporated within the B2B engine as well. Meaning that the B2B engine could be in charge of gathering data content and selectively supplying the data content to the users.
- realtime information and realtime networks discussed with reference to the embodiments hereinabove represent the ideal timing of such networks and information disregarding any delays and/or processing in the network nodes and any other equipment.
- a realtime network may be any network that functions in realtime or near realtime performance.
- realtime information may be information that is substantially realtime or near realtime.
Abstract
Description
Claims
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP01975275A EP1319284A2 (en) | 2000-09-22 | 2001-09-18 | An apparatus for facilitating realtime information interexchange between a telecommunications network and a service provider |
JP2002528980A JP2004513540A (en) | 2000-09-22 | 2001-09-18 | Apparatus for facilitating real-time information exchange between a communication network and a service provider |
KR10-2003-7004122A KR20030040482A (en) | 2000-09-22 | 2001-09-18 | An apparatus for facilitating realtime information interexchange between a telecommunications network and a service provider |
AU2001294614A AU2001294614A1 (en) | 2000-09-22 | 2001-09-18 | An apparatus for facilitating realtime information interexchange between a telecommunications network and service provider |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US23514200P | 2000-09-22 | 2000-09-22 | |
US60/235,142 | 2000-09-22 | ||
US09/755,942 US20020038362A1 (en) | 2000-09-22 | 2001-01-05 | Apparatus for facilitating realtime information interexchange between a telecommunications network and a service provider |
US09/755,942 | 2001-01-05 |
Publications (2)
Publication Number | Publication Date |
---|---|
WO2002025892A2 true WO2002025892A2 (en) | 2002-03-28 |
WO2002025892A3 WO2002025892A3 (en) | 2002-05-30 |
Family
ID=26928610
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2001/029505 WO2002025892A2 (en) | 2000-09-22 | 2001-09-18 | An apparatus for facilitating realtime information interexchange between a telecommunications network and a service provider |
Country Status (8)
Country | Link |
---|---|
US (1) | US20020038362A1 (en) |
EP (1) | EP1319284A2 (en) |
JP (1) | JP2004513540A (en) |
KR (1) | KR20030040482A (en) |
CN (1) | CN1476697A (en) |
AU (1) | AU2001294614A1 (en) |
TW (1) | TW517489B (en) |
WO (1) | WO2002025892A2 (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2003067851A1 (en) * | 2002-02-05 | 2003-08-14 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and business-to-business engine for realtime information interexchange between a telecommunications network and a service provider |
US8407320B2 (en) | 2007-02-26 | 2013-03-26 | Research In Motion Limited | Method and system for correlation of mobile channel subscription with delivery context |
Families Citing this family (39)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5835061A (en) | 1995-06-06 | 1998-11-10 | Wayport, Inc. | Method and apparatus for geographic-based communications service |
US8606851B2 (en) | 1995-06-06 | 2013-12-10 | Wayport, Inc. | Method and apparatus for geographic-based communications service |
EP1226697B1 (en) | 1999-11-03 | 2010-09-22 | Wayport, Inc. | Distributed network communication system which enables multiple network providers to use a common distributed network infrastructure |
US8041817B2 (en) | 2000-06-30 | 2011-10-18 | At&T Intellectual Property I, Lp | Anonymous location service for wireless networks |
US6675017B1 (en) * | 2000-06-30 | 2004-01-06 | Bellsouth Intellectual Property Corporation | Location blocking service for wireless networks |
US7130630B1 (en) | 2000-12-19 | 2006-10-31 | Bellsouth Intellectual Property Corporation | Location query service for wireless networks |
US7116977B1 (en) | 2000-12-19 | 2006-10-03 | Bellsouth Intellectual Property Corporation | System and method for using location information to execute an action |
US7085555B2 (en) | 2000-12-19 | 2006-08-01 | Bellsouth Intellectual Property Corporation | Location blocking service from a web advertiser |
US7428411B2 (en) | 2000-12-19 | 2008-09-23 | At&T Delaware Intellectual Property, Inc. | Location-based security rules |
US7224978B2 (en) | 2000-12-19 | 2007-05-29 | Bellsouth Intellectual Property Corporation | Location blocking service from a wireless service provider |
US7245925B2 (en) | 2000-12-19 | 2007-07-17 | At&T Intellectual Property, Inc. | System and method for using location information to execute an action |
US7110749B2 (en) | 2000-12-19 | 2006-09-19 | Bellsouth Intellectual Property Corporation | Identity blocking service from a wireless service provider |
US7181225B1 (en) | 2000-12-19 | 2007-02-20 | Bellsouth Intellectual Property Corporation | System and method for surveying wireless device users by location |
KR100460274B1 (en) * | 2001-08-11 | 2004-12-04 | (주)넷피아닷컴 | System for providing informations related a location using keyword name and method thereof |
US7103810B2 (en) * | 2002-04-18 | 2006-09-05 | International Business Machines Corporation | System for the tracking of errors in a communication network enabling users to selectively bypass system error logs and make real-time responses to detected errors |
WO2004061550A2 (en) * | 2002-07-26 | 2004-07-22 | Network General Technology | Network analyzer co-processor system and method |
US7412481B2 (en) * | 2002-09-16 | 2008-08-12 | Oracle International Corporation | Method and apparatus for distributed rule evaluation in a near real-time business intelligence system |
US7899879B2 (en) * | 2002-09-06 | 2011-03-01 | Oracle International Corporation | Method and apparatus for a report cache in a near real-time business intelligence system |
US8255454B2 (en) * | 2002-09-06 | 2012-08-28 | Oracle International Corporation | Method and apparatus for a multiplexed active data window in a near real-time business intelligence system |
US8165993B2 (en) * | 2002-09-06 | 2012-04-24 | Oracle International Corporation | Business intelligence system with interface that provides for immediate user action |
US7945846B2 (en) | 2002-09-06 | 2011-05-17 | Oracle International Corporation | Application-specific personalization for data display |
US7401158B2 (en) * | 2002-09-16 | 2008-07-15 | Oracle International Corporation | Apparatus and method for instant messaging collaboration |
EP1434409A1 (en) * | 2002-12-23 | 2004-06-30 | Koninklijke KPN N.V. | Setting user preferences via a mobile terminal |
WO2007014574A1 (en) * | 2005-08-02 | 2007-02-08 | Galini Associates Ltd | System and method for controlling multiple services with restricted access |
CN100539503C (en) * | 2005-12-31 | 2009-09-09 | 华为技术有限公司 | Information issuing system, public media information publication system and dissemination method |
US7797679B2 (en) | 2006-08-31 | 2010-09-14 | Research In Motion Limited | System and method for providing a parameter for an application operating on an electronic device |
US8484328B2 (en) * | 2007-02-23 | 2013-07-09 | Avaya Inc. | Apparatus and method for stateful web services enablement |
ATE556524T1 (en) * | 2007-02-26 | 2012-05-15 | Research In Motion Ltd | METHOD AND SYSTEM FOR ASSOCIATING A MOBILE CHANNEL SUBSCRIPTION TO DELIVERY CONTEXTS |
US9078095B2 (en) | 2008-03-14 | 2015-07-07 | William J. Johnson | System and method for location based inventory management |
US8639267B2 (en) | 2008-03-14 | 2014-01-28 | William J. Johnson | System and method for location based exchanges of data facilitating distributed locational applications |
US8600341B2 (en) | 2008-03-14 | 2013-12-03 | William J. Johnson | System and method for location based exchanges of data facilitating distributed locational applications |
US8634796B2 (en) | 2008-03-14 | 2014-01-21 | William J. Johnson | System and method for location based exchanges of data facilitating distributed location applications |
US8566839B2 (en) | 2008-03-14 | 2013-10-22 | William J. Johnson | System and method for automated content presentation objects |
US8761751B2 (en) | 2008-03-14 | 2014-06-24 | William J. Johnson | System and method for targeting data processing system(s) with data |
KR101640476B1 (en) * | 2011-09-16 | 2016-07-25 | 한국전자통신연구원 | Test analysis system of network and analysis method thereof |
WO2013133870A2 (en) | 2012-03-07 | 2013-09-12 | Snap Trends, Inc. | Methods and systems of aggregating information of social networks based on geographical locations via a network |
US9477991B2 (en) | 2013-08-27 | 2016-10-25 | Snap Trends, Inc. | Methods and systems of aggregating information of geographic context regions of social networks based on geographical locations via a network |
US9894489B2 (en) | 2013-09-30 | 2018-02-13 | William J. Johnson | System and method for situational proximity observation alerting privileged recipients |
WO2017133059A1 (en) * | 2016-02-04 | 2017-08-10 | 华为技术有限公司 | Service data transmission method and apparatus |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP0785535A1 (en) * | 1996-01-16 | 1997-07-23 | Mitsubishi Denki Kabushiki Kaisha | Integrated guidance system for vehicles |
WO2000049825A1 (en) * | 1999-02-19 | 2000-08-24 | Aersoft Limited | A transaction orientated data transport mechanism for use in digital cellular networks |
Family Cites Families (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH04213265A (en) * | 1990-12-07 | 1992-08-04 | Fujitsu Ltd | Inter-service operation control system |
JPH0876706A (en) * | 1994-09-07 | 1996-03-22 | Nippon Telegr & Teleph Corp <Ntt> | Electronic advertisement method and device |
JPH09257501A (en) * | 1996-01-16 | 1997-10-03 | Mitsubishi Electric Corp | Comprehensive guide system |
US5946618A (en) * | 1996-11-04 | 1999-08-31 | Qualcomm Incorporated | Method and apparatus for performing position-based call processing in a mobile telephone system using multiple location mapping schemes |
FI108905B (en) * | 1998-03-03 | 2002-04-15 | Ericsson Telefon Ab L M | Method, arrangement and apparatus for providing information |
US6345239B1 (en) * | 1999-08-31 | 2002-02-05 | Accenture Llp | Remote demonstration of business capabilities in an e-commerce environment |
US7636665B2 (en) * | 2000-01-04 | 2009-12-22 | Intuit Inc. | Method and system for remotely managing business and employee administration functions |
US6526275B1 (en) * | 2000-04-24 | 2003-02-25 | Motorola, Inc. | Method for informing a user of a communication device where to obtain a product and communication system employing same |
US6725048B2 (en) * | 2000-09-22 | 2004-04-20 | Ericsson Inc. | Traffic congestion management when providing realtime information to service providers |
-
2001
- 2001-01-05 US US09/755,942 patent/US20020038362A1/en not_active Abandoned
- 2001-09-18 WO PCT/US2001/029505 patent/WO2002025892A2/en not_active Application Discontinuation
- 2001-09-18 KR KR10-2003-7004122A patent/KR20030040482A/en not_active Application Discontinuation
- 2001-09-18 AU AU2001294614A patent/AU2001294614A1/en not_active Abandoned
- 2001-09-18 JP JP2002528980A patent/JP2004513540A/en active Pending
- 2001-09-18 EP EP01975275A patent/EP1319284A2/en not_active Withdrawn
- 2001-09-18 CN CNA018193196A patent/CN1476697A/en active Pending
- 2001-09-21 TW TW090123353A patent/TW517489B/en not_active IP Right Cessation
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP0785535A1 (en) * | 1996-01-16 | 1997-07-23 | Mitsubishi Denki Kabushiki Kaisha | Integrated guidance system for vehicles |
WO2000049825A1 (en) * | 1999-02-19 | 2000-08-24 | Aersoft Limited | A transaction orientated data transport mechanism for use in digital cellular networks |
Non-Patent Citations (2)
Title |
---|
HELLAKER J ET AL: "Real-time traveller information - in everyone's pocket? - a pilot test using hand-portable GSM terminals" VEHICLE NAVIGATION AND INFORMATION SYSTEMS CONFERENCE, 1993., PROCEEDINGS OF THE IEEE-IEE OTTAWA, ONT., CANADA 12-15 OCT. 1993, NEW YORK, NY, USA,IEEE, 12 October 1993 (1993-10-12), pages 49-52, XP010219744 ISBN: 0-7803-1235-X * |
KRELLER B ET AL: "UMTS: A MIDDLEWARE ARCHITECTURE AND MOBILE API APPROACH" IEEE PERSONAL COMMUNICATIONS, IEEE COMMUNICATIONS SOCIETY, US, vol. 5, no. 2, 1 April 1998 (1998-04-01), pages 32-38, XP000751833 ISSN: 1070-9916 * |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2003067851A1 (en) * | 2002-02-05 | 2003-08-14 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and business-to-business engine for realtime information interexchange between a telecommunications network and a service provider |
GB2401513A (en) * | 2002-02-05 | 2004-11-10 | Ericsson Telefon Ab L M | Method and business-to-business engine for a realtime information interexchange between a telecommunications network and a service provider |
US8407320B2 (en) | 2007-02-26 | 2013-03-26 | Research In Motion Limited | Method and system for correlation of mobile channel subscription with delivery context |
Also Published As
Publication number | Publication date |
---|---|
EP1319284A2 (en) | 2003-06-18 |
CN1476697A (en) | 2004-02-18 |
AU2001294614A1 (en) | 2002-04-02 |
KR20030040482A (en) | 2003-05-22 |
WO2002025892A3 (en) | 2002-05-30 |
JP2004513540A (en) | 2004-04-30 |
US20020038362A1 (en) | 2002-03-28 |
TW517489B (en) | 2003-01-11 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP1319295B1 (en) | A business to business engine and system for facilitating information interexchange using realtime data | |
US7043231B2 (en) | System, method and apparatus for polling telecommunications nodes for real-time information | |
US6725048B2 (en) | Traffic congestion management when providing realtime information to service providers | |
US20020038362A1 (en) | Apparatus for facilitating realtime information interexchange between a telecommunications network and a service provider | |
US6816720B2 (en) | Call-based provisioning of mobile equipment location information | |
US20020037709A1 (en) | System, method and apparatus for facilitating the receipt of realtime information from telecommunications nodes | |
US20020037744A1 (en) | Telecommunications device for sending realtime information to a business-to-business engine for facilitating services to the telecommunications device | |
US20020037722A1 (en) | Facilitating realtime information interexchange between a telecommunications network and a service provider | |
US20020095312A1 (en) | Facilitating realtime information interexchange between a telecommunications network and a service provider | |
ES2361002T3 (en) | A MOTOR AND A COMPANY TO COMPANY SYSTEM (B2B) TO FACILITATE THE EXCHANGE OF INFORMATION USING DATA IN REAL TIME. |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A2 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PH PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A2 Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
AK | Designated states |
Kind code of ref document: A3 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PH PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A3 Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
DFPE | Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101) | ||
WWE | Wipo information: entry into national phase |
Ref document number: 2002528980 Country of ref document: JP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1020037004122 Country of ref document: KR |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2001975275 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 018193196 Country of ref document: CN |
|
WWP | Wipo information: published in national office |
Ref document number: 1020037004122 Country of ref document: KR |
|
WWP | Wipo information: published in national office |
Ref document number: 2001975275 Country of ref document: EP |
|
REG | Reference to national code |
Ref country code: DE Ref legal event code: 8642 |
|
WWW | Wipo information: withdrawn in national office |
Ref document number: 2001975275 Country of ref document: EP |