ES2361002T3 - A MOTOR AND A COMPANY TO COMPANY SYSTEM (B2B) TO FACILITATE THE EXCHANGE OF INFORMATION USING DATA IN REAL TIME. - Google Patents

Abstract

A method for providing unsolicited content information from a content provider to a telecommunications device that operates in a mobile telephony telecommunications system, said method being carried out in a Company-to-Company engine connected to the system. telecommunications in which said B2B engine receives real-time information from said mobile telephony telecommunications system and provides content information to said mobile telephony telecommunications device, the said method comprising: receiving a subscription for a particular event activation associated with a mobile phone telecommunications device of the content provider, in which the B2B provider agrees to notify the content provider whenever the telecommunication system reports the said event activation associated with the mobile phone telecommunications device; receive from the telecommunication system, a report of said event activation associated with the mobile telephony telecommunications device; notify the content provider that the telecommunication system has reported the said event activation associated with the mobile telephony telecommunications device; receive real-time information from the content provider in response to the notification stage; and send the content information to the mobile phone telecommunications device.

Description

RELATED APPLICATION INDICATION This Patent Application claims priority benefit, and incorporates herein as a reference to the full description of the U.S. Provisional Application. co-dependent for the Serial No. Patent 60 / 235,142 filed on September 22, 2003.

BACKGROUND OF THE INVENTION

Field of the Invention The present invention generally relates to a business-to-business system and, in particular, to an engine and a business-to-business system (B2B - Business to Business) capable of intelligently providing information in real time associated with a mobile phone telecommunications network and subscribers to a content provider.

Background and Objects of the Present Invention The increasing accessibility to information on the Internet has made a wide variety of content available. Typically, users access this content in a fixed home or office location through an Internet Service Provider (ISP). Internet content providers send their content, along with advertising or other commercial information, through the ISP directly to the user. While some ISPs routinely keep caching, for example, Yahoo and America On Line (AOL) by providing additional content, most ISPs are purely conduits of information, and therefore are not expected to have added value as it is Technology and mature service.

A more recent, concurrent development is wireless Internet access by mobile phone users. Due to this convergence of telecommunications and the Internet, a growing variety of devices are resulting from multipurpose and are now available to access the Internet wirelessly, for example, mobile phones, personal data assistants (PDAs - Personal Data Assistants) ) or other communications devices. As with ISPs, however, Internet content providers are using telecommunications equipment as a mere conduit to pass information through it, thereby marginalizing the perceived value of these physical connections belonging to telecommunications operators. This operation paradigm is illustrated in FIGURE 1 and is generally designated therein by reference number 100, where several content providers, for example, restaurant information 105, weather information 110 and other portals 115 of that type, channel the respective data through a "conduit", ie the equipment 120 of the telecommunication operators, to a user in real time.

In view of the high cost of telecommunications network infrastructure and the need to avoid perceived obsolescence, telecommunications system operators must restructure the interface between the content provider and the user to better exploit the advantages in technological convergence. In particular, a system and methodology is needed that offers an alternative paradigm that avoids the marginalization of telecommunications infrastructure and services and prevents the loss of identity. In addition, paradigm 100 of FIGURE 1 fails to make use of any real-time information that is inherently provided within a service telecommunications network, such as location status, which belongs to the mobile telephone user, an area that will be Critical in numerous future applications.

Example prior art methods relating to the location and information provided to and from a mobile telephone station include Pat. from U.S. No. 5,559,520 which generally describes tracking a user's location change using a GPS system and providing information from a transmitter to the user regarding the geographical coordinates of a vehicle.

U.S. Patent No. 5,926,108 generally describes providing mobile information to a pager. The pager first requests information from the system, which in turn determines the location of the pager and sends motion information based on this location and optionally reserves tickets for the pager user.

U.S. Patent No. 6,131,028 generally describes providing a specific predefined feature based on the geographic location of a user. These features could be call transmission based on the location or predefined business establishment addresses.

U.S. Patent No. 5,930,699 generally describes providing information about a company based on a location of a mobile telephone station. The cell identity is determined by the system and information regarding a company in that area is sent to the mobile phone station.

image 1

U.S. Patent No. 6,091,956 generally describes a system that provides services about sites and events that a mobile computer finds in its current location or potential destinations. The mobile computer is informed of events related to sites that the user wishes to visit. Based on this information, the mobile computer can respond, avoid completely, communicate with other people or modify its plans in view of such events.

U.S. Patent No. 6,108,533 generally describes providing a mobile telephone station with the ability to search, using keys, information in a database. Such information may require knowledge of the location of the mobile telephone station and search for the key provided by the mobile telephone station in the location database of that area.

U.S. Patent No. 6,115,611 generally describes having an information center connected to a plurality of mobile telephone terminals. The mobile telephone terminals that access the location information as well as other useful information for the user of the mobile telephone terminal from the information center. The information center is used to accumulate information and / or services from the mobile telephone terminals and provide information to the mobile telephone terminal relating to the location information of the mobile telephone terminal.

WO 99/45732 describes a method, arrangement and apparatus for providing a mobile telephone user with removable information from a database. The method comprises the steps of establishing a communication connection between a mobile telephone station and a base station or base stations of a mobile telephone communication network. The location of the mobile telephone station is then determined on the basis of the base station or the base stations, and this identified location information is processed in the mobile telephone communication network in order to allow obtaining of information related to the area related to the location determined from the database. The information related to the area obtained is then transmitted to the mobile telephone station.

It is, therefore, an object of the present invention to provide a new system and methodology for the use of the Internet by mobile telephony, which offer more value to telecommunications network operators and better exploit the technological advantages of the network.

Another object is that the system and methodology of the present invention make better use of the real-time information available on telecommunications networks about mobile phone users and the content available, thereby taking advantage of the network's capabilities to generate a benefit. Another object of the present invention is that the enabler described here takes advantage of the real-time capabilities of a telecommunications network.

A further object of the present invention is that the enabler better personalize services based on user situations, for example, user mobility.

These objects are resolved by the competences of the independent claims. Advantageous embodiments are described in dependent claims.

The present invention is directed to a system and a method for facilitating the exchange of information between a wireless telecommunications system having at least one telecommunications device therein and an information service provider. A business-to-business engine (B2B - Company-to-Company) is connected to the telecommunications system to receive real-time information regarding a telecommunications device within the telecommunications system. This real-time information is provided by the B2B engine to the information service provider, which consequently provides content data to the telecommunications device within the telecommunications system.

BRIEF DESCRIPTION OF THE DRAWINGS The described invention will be described with reference to the accompanying drawings, which show important sample embodiments of the invention and which are incorporated into the specification of this document as a reference, in which:

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, which provides a business-to-business engine that connects with external content providers and that provides real-time subscriber information in addition; FIGURE 3 also illustrates the telecommunications system of FIGURE 2, which demonstrates the interaction between telecommunications operators and content providers as a 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 phone telecommunications providers and content providers using the business-to-business engine; FIGURE 5 illustrates example interactions between the business-to-business engine of the present invention and different elements of a network; FIGURE 6 illustrates an architecture of a number of application modules in a preferred embodiment of the present invention; FIGURE 7 illustrates an alternative architecture for the application modules shown in FIGURE 6 in accordance with another embodiment of the present invention; FIGURE 8 is a flow chart illustrating a signal flow used in the initialization of a user's subscription; FIGURE 9 illustrates a preferred interface between a portal and a user equipment by means of the B2B engine of the present invention; FIGURE 10 is a flow chart illustrating a number of signals used to initialize an "OFF" trigger that complies with the teachings of the present invention; FIGURE 11 is another flow chart illustrating a signal flow for an event that takes place in a telecommunications system in accordance with the teachings of the present invention; FIGURE 12 is a flow chart illustrating a user indication connected to the B2B engine of the present invention; FIGURE 13 is a flow chart illustrating an update of the location area to the B2B engine of the present invention; FIGURE 14 illustrates an architecture of 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 a network node notification to the B2B engine; FIGURE 16 illustrates the real-time information communications associated with a mobile telephone subscriber from various network elements to the B2B engine in accordance with the teachings of the present invention; FIGURE 17 illustrates several of the protocols used in conjunction with the present invention, particularly between the B2B engine and several network nodes; and FIGURE 18 illustrates an example and joint work configuration of a B2B engine with different network architectures.

image2

DETAILED DESCRIPTION OF THE CURRENTLY PREFERRED EXAMPLE EMBODIMENTS The numerous innovative teachings of the present application will be described with particular reference to the currently preferred example embodiments. However, it should be understood that this class of embodiments provides only a few examples of the many advantageous uses of the innovative teachings of this memory. In general, the statements in the specification of the present application do not necessarily delimit any of the different claimed inventions. In addition, some of the things indicated may apply to some features of the invention but not to others.

The present invention explains a system and methodology for providing personalized, adaptable and intelligent information and services associated to mobile telephone subscribers based on real-time information of mobile telephone subscribers, which include but are not limited to current activity, preferences, location , use and behavior patterns of the mobile telephone subscriber, inherent in real-time networks.

As noted earlier in this specification, FIGURE 1 illustrates a conventional telecommunications system that provides information to telecommunication subscribers. In the prior art, the contents of restaurant and weather information, 105 and 110, for example, are supplied from content providers to end users directly. Telecommunication operators 120, however, in this paradigm are only conduit providers that pass information to end users, similar to many current ISPs. In particular, and as described in more detail hereinbelow, telecommunication operators 120 do not share any real-time information 130 about the user with content providers and are only a means of passing information one way from Content providers directly to users who, of course, operate in real time. As an illustration, in order for a mobile telephone subscriber to obtain the meteorological information associated with the current location of the subscriber in a conventional system, although the service mobile telephone telecommunications network already knows the approximate location of the mobile telephone subscriber, Since the mobile telephony telecommunications service network merely acts as a conduit for communicating such information, the mobile telephone subscriber nevertheless has to manually provide the location information to the Internet content provider.

Referring now to FIGURE 2, a business-to-business engine (B2B - Company-to-Company) 210 according to a preferred embodiment of the present invention is illustrated. The business-to-business engine 210 includes a number of application modules 220 therein, as illustrated and described more fully hereinafter with reference to FIGURES 6 and 7 and the accompanying text. In a preferred configuration, the B2B engine 210 runs on network hardware, generally designated in FIGURE 2 by reference number 224, for example, a Sparc processor, and uses an operating system / middleware 222, for example OS Solaris, which is stable and performs several functions described in more detail below in this report. It should, of course, be understood that alternative hardware and software can be used in the implementation of the instant invention, as understood by one skilled in the art. Also with reference to FIGURE 2, the B2B engine 210 is connected to a telecommunications system 230 and the Internet 250.

image3

Telecommunication system 230 preferably includes a wireless service provider or any service provider serving a number of subscriber or user terminals, for example, mobile phones, personal data assistants (PDAs) or any device of wireless communications or equipment capable of receiving signals. In addition, the B2B engine 210 is coupled, via a link 248 to the Internet, generally designated by reference number 250, which includes applications from the content provider that provides information to users proactively. The information provided can be found in and sent from a weather server 260, a financial server 262, a news server 264 and / or an ad server 266, via a link 252 corresponding to the Internet 250, which provides the gateway link for the respective services.

An Internet portal for collecting and providing certain services based on such collected information may also be connected to Internet 250. Such portal may also communicate with other associated servers 260, 262, 264, 266, and communicate such collected information to a petitioner by Internet medium 250.

Referring now to FIGURE 3, a preferred embodiment of the present invention is illustrated, showing the alternative paradigm of the instant invention compared to the conventional paradigm shown in FIGURE 1. The B2B Engine 210 connected to a telecommunication operator 120 Service communicates certain real-time information associated with a particular mobile phone subscriber to any one of the content providers, such as a restaurant information provider 105, a weather information provider 110 or a service portal 115. Each From these providers or content portal you can then use the real-time information received associated with a particular mobile telephone subscriber to provide a particularized service for that state or real-time preference of that particular subscriber. As an illustration, a request for Italian restaurants in the surroundings will be answered and provided to the requesting mobile telephone subscriber without the mobile telephone subscriber manually entering the current location of the same. The B2B engine would automatically receive the current location of the requesting mobile phone subscriber and communicate this information in real time (location information) to the content provider proactively.

As also described in FIG. 8, in order for a particular content provider to receive certain real-time information or event associated with a particular mobile phone subscriber, the content provider must subscribe to the B2B engine. The content provider may need to provide a mobile phone identification number associated with a particular mobile phone subscriber and subscribe to the B2B engine to monitor and provide the content provider with certain real-time information associated with that particular mobile phone subscriber. As an example, the weather information provider can subscribe to the B2B engine to monitor a particular subscriber location and "connected" information. As a result, whenever that particular subscriber turns on their mobile phone station, such real-time information will be provided to the weather information provider through the B2B engine. The weather information provider will in turn automatically provide the current weather information associated with that particular location to the mobile telephone subscriber. The mobile telephone subscriber does not need to manually request weather information nor does the user have to manually enter his current location. The act of turning on your phone will automatically activate the generation of these predefined services. As another illustration, when a user arrives in a city, the meteorological information of this city, the headlines of news relating to this city, the location of traffic in that city, etc. It is sent to the user. All this is done automatically without the user's knowledge, but according to your preference, the network intelligently determines that the user needs this information while in this location. Also, if a roaming user passes through a conflictive or bad neighborhood area, the B2B engine will intelligently know the user's location and inform the portal, which will send information regarding the crime rate or the latest news headlines for This current location. This will help people who travel, and in general it will help people regardless of how often they travel. In addition, in a preferred embodiment of the present invention, the entire network is interconnected and intelligently exchanges information regarding the state of the user to provide the best service to the end user. The B2B engine provides this interconnection capability and intelligently connects information providers or portals, with the mobile phone operators in which the user resides. A non-real-time system, a portal and a real-time system, a mobile phone operator interact and operate smoothly despite the difference in their operational nature.

The content provider information, such as restaurant information 105, weather information 110 and portals 115, can channel or send the requested information or service through a telecommunication operator 120 directly, as in FIGURE 1, or alternatively , can be sent to the telecommunication operator 120 through a B2B engine 210, such as the engine 210 described in connection with FIGURE 2 and also hereinafter. It should be understood that the B2B engine 210 of the present invention, preferably resides in the telecommunications network and is interposed between the content providers and the telecommunication operators 120. Accordingly, the B2B engine 210 is responsible for obtaining the aforementioned real-time information 130 associated with the respective user, for example, location and / or preferences, and for processing this information. The B2B 210 engine, when the status information is received in real time, sends the data in real time to the content providers, thereby allowing the particularization according to the respective location and preferences in real time of the user.

image4

Referring now to FIGURE 4 of the Drawings, another preferred embodiment of the present invention is illustrated in which telecommunication providers 120 are mobile telephone providers, for example, in accordance with the Global Subscriber Mobile (GSM-De) system. Global Subscriber Mobile Telephony), Personal Communication System (PCS-Personal Communication System) or other mobile telecommunication standard. The B2B 210 engine resident within the mobile phone network maintains the exchange of information in real time between mobile phone providers 120 and the respective content providers, for example, the above-described restaurant information 105, weather information 110 and portals 115. The B2B 210 engine determines real-time information about mobile phone subscribers in communication with the mobile phone operators' network, communicating with the network and the respective users in order to determine a variety of subscriber information: subscriber rules 242 for its application and any requirement conditions, subscriber preferences 244, subscriber status 246 and any intelligence factor 248 necessary to meet the needs of the mobile telephone subscriber. This subscriber information is collected for each user and provided to the content providers, who provide the information to the mobile telephone subscriber. Restaurant information 105, weather information 110 and portals 115 are particularized according to the state of the user in real time, and provided from the B2B engine 210 to the real-time content providers, by the B2B engine 210 regarding to the real-time status, requirements, preferences, rules and / or location of the registered user. A preferred embodiment of the present invention integrates a real-time system, for example, the telecommunication operator 120 mentioned above, and a non-real-time system, for example content providers, using the businessto-business engine (B2B - Company -a-Company) 210 of the present invention. The B2B engine 210, as described herein, communicates with the respective telecommunication operators 120 and the associated network elements to obtain real-time information about their subscribers, processes the subscriber information and provides the information to the subscribers. Content providers according to certain subscribed events requested by those content providers.

In another preferred embodiment of the present invention, there are a plurality of telecommunication operators 120, each having discrete subscribers associated with them. Each telecommunication operator 120 in this embodiment preferably acts independently and provides real-time information about the respective subscribers to the content providers. In a preferred embodiment of the present invention, each telecommunication operator 120 is provided with a unique identification number. The respective or respective content provider or providers in accordance with the request made by an identifiable telecommunication operator 120, then sends or sends the requested information to the user subscribed in that network of the telecommunication operator 120.

Referring now to FIGURE 5, example interactions between the business-to-business engine (B2B-Company-Company) 210 of the present invention and different network elements are illustrated. Real-time systems 270, such as wireless communication systems, cable communication systems and ISPs, communicate with the B2B 210 engine to provide real-time information about subscribers and end users to the B2B 210 engine The 272 content providers are coupled to the B2B 210 engine to obtain real-time information of the B2B 210 engine and subscriber behavior information.

Service providers 272 also provide information to an end user, for example, a wireless communication subscriber, a cable subscriber or an ISP subscriber and are generally designated by reference number 274, through the B2B engine 210.

With another reference to FIGURE 5, instead of communicating these events in real time to external content providers, the application modules and services associated with the B2B engine can generate and provide certain desired services independently to those monitored mobile phone subscribers . Accordingly, a number of B2B developers develop and update application modules in the B2B 210 engine to support new services and / or improve existing services.

In an alternative embodiment of the present invention the B2B engine 210 is connected to a portal or content aggregators to provide information to the end user. Portals and content aggregators collect information from different content providers and provide the information collected to the end user through different means that will be explained in more detail below in this report.

In particular, the end user is registered in the portal or in the content aggregators. Through the user's subscription, the portals pass the subscription, as an event, to the B2B 210 engine. The B2B 210 engine receives the user's subscription event and stores it in the 210A memory or engine database. It should be understood that the database is preferably an internal database within the B2B 210 engine or an external database that could be accessed by the B2B 210 engine.

image5

It must, of course, be understood by a person not skilled in the art that the inclusion of a B2B 210 engine in a telecommunications network that has several operating protocols will lead to the creation of a variety of databases, interfaces and portals required. to facilitate the flow and exchange of information. For example, a user's preferences can be stored in a database of preferences and activation conditions or events (rules) operate to initiate a communication. Internet mobile phone users will expect access in some way equivalent to that of a fixed station, as well as enhanced, personalized services based on mobility.

As explained, for mobile phone operators, there is an opportunity to become more than a mere conduit provider by exploiting the relationship with subscribers (monthly accounts, personal information) and take advantage of the wireless Internet to generate new benefits. Content providers, in turn, face several challenges to make their content available and personal to subscribers. In reality, the customization of Internet services by telecommunications operators coincides with the Internet, particularly with the arrival of vertical portals and personalized user profiles.

As described above in connection with FIGURES 2-5 and explained in more detail hereinbelow, the system and methodology of the present invention is an intelligent engine that takes advantage of the activity, preferences, location, use and patterns of subscriber behavior, inherent within a mobile telephone network to provide customized real-time mobile phone Internet services in real time. In particular, the present invention allows content providers to build personalized content based on mobility and allows mobile operators to take advantage of mobility information in the mobile telecommunication network to increase the value chain. In addition, the present invention provides a platform for service providers to build new Internet services based on real-time information associated with mobile telephone subscribers within a mobile telephone telecommunications network.

As also explained below in connection with the portals and interfaces of the present invention, a variety of new functions are provided by creating the mobile phone's Internet environment in real time. In particular, a personal preference user interface and database provide a mechanism both for selecting personal preferences and for storing those preferences of an Internet subscriber in a database managed by the telecommunications operator. The requirement real-time mobility information is provided by means of interfaces with network nodes and / or with network elements in the telecommunications system. A rules-based environment allows wireless Internet subscribers to customize or develop new services based on real-time events. Customizable services based on sample rules include:

When the mobile phone is turned on, access to information from finance.yahoo.com provide by means of a short message service to a mobile phone.

In this example, the wireless Internet subscriber uses the switching on of their own mobile phone as a real-time event to request a service, and personalizes that service to provide news from a particular network site in a particular format. Another example service includes:

When the arrival to a new city is detected,

re-route calls to the new number

Provide a request for hotel room and car rental for travel coordinator

wait for confirmation receipt

acknowledge confirmation

alert the user.

In this example, the wireless Internet subscriber uses the arrival time, for example, by plane, to initiate a variety of actions in order to facilitate the coordination of travel needs. If a time zone change occurs, an alert can be generated confirming the time change to the subscriber.

As described above, all those desired events are subscribed with the B2B Engine by content providers. The B2B Engine then communicates with the mobile telephony telecommunications network of the service and determines that that particular event has occurred for a mobile telephone subscriber to communicate such an activation event to the subscriber's content provider in order to allow The content provider automatically performs all those services.

The numerous features of a business-to-business engine (B2B - Company-to-Company) have been explained earlier in this report. To achieve the aforementioned functionalities and to allow its interconnection with the network, certain features and components should be available in the B2B engine. Referring now to FIGURE 6, a variety of business-to-business engine application modules 210 (B2B Company-to-Company) are illustrated in a preferred embodiment of the present invention. As shown, the B2B engine application module 220 includes a variety of discrete modules, each having an important function in the system. In particular, B2B application modules 220 include an Interface Module (IM - Interface Module) 280, a Data Collection Module (DCM - Data Collection Module) 282, a Behavior Analysis Module (BAM - Behavior Analysis Module) ) 284, a Service Development Environment (SDE - Service Development Environment) 286, a Realtime Delivery Module (RDM - Real Time Delivery Module) 288, a Rules Development Environment (RDE - Rules Development Environment) 290, a Business Data / End User Subscription Module (BDSM - Company Data Subscription Module / End User) 292, a Service Execution Module (SEM - Service Execution Module) 294, a Performance and Charging Module (PACM - Operating Module and Billing) 296 and an Operation and Maintenance Module (OAMM) 298.

image6

The aforementioned Interface Module (IM) 280 is responsible for interconnecting with application modules 282-296 with content providers and telecommunication systems. The IM 280 is interconnected with several external components, such as different telecommunication systems and ISPs. IM 280 also provides an interface with content providers. One of the primary functions of the IM 280 is to connect external components in the network with the application modules in the B2B 210 engine. In a preferred embodiment, the IM 280 is interconnected internally with the Data Collection Module (DCM - Collection Module of Data) 282 and with the Realtime Delivery Module (RDM - Real Time Delivery Module) 288. It should, of course, be understood that the IM 280 could also be interconnected with other internal modules, as well as external network components, depending of the system requirements.

With another reference to FIGURE 6, the Data Collection Module (DCM - Data Collection Module) 282 is responsible for obtaining and storing real-time data for telecommunication systems and ISPs. DCM 282 interconnects internally with the Business Data Subscription Module (BDSM) to find out about data subscriptions from content providers. The DCM 282 is also interconnected with the Behavior Analysis Module (BAM - Behavior Analysis Module) 284 and with the Realtime Delivery Module (RDM - Real Time Delivery Module) 288 to deliver real-time information to content providers. The Behavior Analysis Module (BAM - Behavior Analysis Module) 284 is preferably a set of artificial intelligence programs that check the subscription information from the BDSM 292 and perform the real-time data analysis. Preferably, BAM 284 is coupled to RDM 288 to deliver the results to the content providers. In addition to being interconnected with BDSM 292 and RDM 288, BAM 284 is interconnected with the Data Collection Module (DCM - Data Collection Module) 282.

The Rules Development Environment (RDE) 290 allows the development of rules used for the development of services. RDE 290 stores the rules in a Rule Repository (Rrep - Rule Deposit). The rules could be constantly updated to adapt to new services that are adopted and varied according to the preferences of various system components. The Service Development Environment (SDE) 286 allows telecommunication operators or end users to develop new sets of services based on a set of rules. SDE 286 is interconnected internally with the Rules Deposit to develop services and with the Service Execution Module (SEM - Service Execution Module) 294. The Service Execution Module (SEM - Service Execution Module) 294 executes the service used, and interconnects internally with SDE 286 and with BDSM 292.

The Business Data / End User Subscription Module (BDSM - Company Data Subscription Module / End User) 292 allows content providers to subscribe to real-time and behavioral data, and also allows end users to subscribe to services . For this, BDSM 292 is internally interconnected with RDM 288. The Performance and Charging Module (PACM) is responsible for collecting statistics, keeping track of the number of times real-time data were requested by the content providers and the number of subscribers who access their services. The PACM 296 also keeps track of other statistical data that could be helpful to fully utilize the network and its operation. The PACM 296 also carries out a post process charge.

Finally, the Operation and Maintenance Module (OAMM) 298 is responsible for managing and configuring the B2B 210 engine. The OAMM 298 is capable of configuring content providers, maintaining the B2B engine, handling failures in the system, and managing security problems in the system, as well as other operation and maintenance functionalities.

It should be understood that the B2B application modules 220 illustrated in connection with FIGURE 6 and explained hereinbefore are preferably treated independently, despite the fact that they could be linked together in one module or at least several could be joined together. yes. Discrete modules preferably have a modular design for applications, and are preferably based on Java. Alternatively, other programming languages can be used that are adapted to the features mentioned above, for example, C ++, Java Servlets, Java Beans, JSP and others. As explained, an important aspect of the present invention is to have almost real-time operation. In addition to copying with real-time environments, the system is designed to reduce faults and has a fault tolerance system.

image7

Another preferred embodiment of the B2B engine, which also illustrates modularity and implementation using different modular architecture, is shown in FIGURE 7. The B2B engine in this embodiment, designated by reference number 310, also includes an interface module. 315 and an operation and maintenance module 320 as described above. However, this embodiment preferably includes an Intelligence Module (INM - Intelligence Module) 325, an Event Reception and Processing Module (ERPM), 330, a Module (CM - Cargo Module) 335, a Subscription Database (SD - Subscription Database) 340, a Validation Module (VM - Validation Module) 345, a Data Collection Module (DCM

- Data Collection Module) 350 and an Event Forwarding Module (EFM) 355.

When the event of a subscription is received from a portal, by the Interface Module (IM - Interface Module) 315 of the B2B engine, the IM 315 is interconnected with the Validation Module (VM - Validation Module) 345 to validate the event of this subscription. VM 345 is interconnected with the Data Collection Module (DCM - Data Collection Module) 350, which allows the submission of the user identity and allows the storage of events in a Subscription Database (SD - Subscription Database) . The SD must be secure and preferably scalable to allow expansion to the number of subscribers. The DCM 350 is also responsible for informing the portal that the subscribed user has been successfully registered in the B2B engine database

310. The events received from the network nodes that indicate the status of the mobile phone subscriber, arrive at the Interface Module and are processed in the Event Reception and Processing Module (ERPM), accessing the preference of the user subscribed in the SD, which is done to ensure that the user is a subscriber of the registered B2B 310 engine.

After validating the user profile, the event is packaged and a notification is sent to the portal, using the Event Forwarding Module (EFM) 355, by means of a highly secure HTTP notification message. After this notification has been sent to the portal related to the subscribed user status, the Charching Module (CM - Charge Module) 335 creates a charge record for the portal related to the information sent.

The modules, as mentioned above with respect to FIGURES 6 and 7, could be arranged in a variety of configurations to provide the functions needed by the system. However, looking at the B2B 210/310 engine from a different perspective, a different architecture could be implemented for the modules.

For a better understanding of the interaction of the portal with the B2B engine, reference is now made to FIGURE 8, which also illustrates the transmission of a subscription event from a user of a portal. FIGURE 8 represents a timing diagram, generally designated by the reference number 360, for the subscription event and the interaction of a portal 362 with a B2B engine 364 with respect to this subscription. The user first subscribes to the portal service using any of several mechanisms, for example, through the portal website 362, www.yahoo.com, etc., generally designated by reference number 366. The user , however, you need to provide different person information and preference to portal 362. This information includes the user identification number (MSISDN), the mobile phone operator and various preferences associated with the content or events that you want to be monitored. Portal 362 stores 368 all user information provided in its database. When the information is stored 368, the portal 362 sends an event notification 370 informing the appropriate B2B engine 364 in charge of the subscriber's mobile phone operator. In a preferred embodiment of the present invention, the B2B engine 364 is run by a mobile phone operator or in some cases a plurality of mobile phone operators. Notification event 370 sent to the B2B engine 364 preferably includes a user's mobile phone station identification number (MSISDN), subscription details, user events and preferences and other related information. This notification event is preferably sent using a secure HTTP protocol.

The B2B 364 engine receives notification of event 370 and processes the information therein. This internal validation occurs in a preferred embodiment using a layered structure, as also explained in connection with FIGURES 6 and 7. With reference again to FIGURE 8, when the notification of an event 370 is received, a First layer or class, generally designated by reference number 372, requests the establishment of a new connection (step 374). A second layer or class 766 inserts this subscription event (step 378) into a third layer or class 380 that validates the user identification number (MSISDN) (step 382) and stores (step 384) the subscription information in a database. When the validation stage 384 is completed, an acknowledgment (step 386) is sent to the portal 362 regarding the notification of the subscription event 370, preferably using an HTTP protocol. The B2B engine then monitors the real-time information requested with that particular mobile phone subscriber.

The B2B engine, as described earlier in this report, could operate in different ways. In an embodiment of the present invention, the B2B engine polls the relevant network nodes to request updated information. In another embodiment, the network nodes are programmed to inform the B2B engine of changes in the user's state. Another embodiment allows the mobile phone station to provide status information to the B2B engine, this is carried out by activating an application client program in a mobile phone station. However, these preferred embodiments could work concurrently. As an example, the B2B engine could poll some network nodes while other network nodes are reporting their status to the B2B engine. Also, the mobile phone station could report its status to the B2B engine and this same status report could also be provided by a network node. The B2B engine, however, intelligently determines that the information sent is relative, redundant and combines the two pieces of information to carry out advanced functions based on a better understanding of the user's status.

image8

With the above explanation of the position of the B2B engine within a telecommunications network and several modules in mind, attention should now be directed to FIGURE 9, which illustrates joint example works of a B2B 410 engine in a preferred embodiment of The present invention. As illustrated, the B2B 410 engine connects to a front end portal 420, a mobile telephone station 430 (via wireless connection) and an Operation and Maintenance Management System (O&M) 415 The O&M 415 system will provide an operator or product owner with the capabilities to operate and maintain the B2B engine. All fault and alarm management can be controlled and monitored through this O&M 415 system. Also, a remote management system will be accessible, as shown in this memory or a module within the B2B engine as described above. with reference to FIGURE 6. As shown in the figure, mobile telephone station 430 may include a Wireless Application Protocol toolset 432 (WAP) and / or a development toolset 434 of Subscriber Identification Module (SIM - Subscriber Identification Module) in it.

The WAP 432 toolkit is used to develop a WAP application support, which, as understood in the sector, provides wireless user access to the contents and services of the Internet. The WAP toolset 432 preferably resides in the mobile telephone station 430, which is preferably capable of supporting the WAP protocols.

The SIM 434 toolset, which resides in the mobile phone station 430, is used for value-added and electronic commerce services that use the mobile phone station, allowing transactions over the Internet. For example, using a mobile phone station activated by a set of SIM tools, a user may be able to check his bank account, invoices and all other services achieved through the current cable Internet access. The SIM tool set 434 is preferably programmed into the SIM card, generally designated in FIGURE 9 by reference number 436, and additionally allows an interface between the network and the end user. A preferred embodiment of the interaction of Mobile Equipment (ME) / Subscriber Interface Module (SIM - Subscriber Interface Module) with the B2B engine will be described below in this specification with reference to FIGURES 11-13 . As noted, the Enterprise-to-Enterprise engine 410 is also connected to the front end portal 420, or to a number of portals, which provide information to the end user. Those skilled in the art should understand that this information is customized according to respective user preferences and is collected from various content providers. It should also be understood that the portal 420 in a preferred embodiment of the present invention could be a fake portal 422 or one designed to better exploit Internet connections, for example, a so-called WISE portal 424, as will be understood by a person not particularly skilled.

Referring to FIGURE 10, an example of an “OFF” Trigger for a cordless telephone is illustrated, the stages of which are generally designated by reference number 450. A Mobile Station (MS) designated as In general, by reference number 452, it includes a set of Subscriber Identification Module (SIM) 454 tools located therein. The SIM 454 toolset transmits, with certain intervals, short message service messages (SMS - Short Message Service), generally designated in the figure by reference number 456, which contains the status of the subscriber and the ISDN number of mobile telephone station 452 (MSISDN). The SIM 454 toolset performs this action to keep an associated B2B 458 engine informed of the real-time information and location of the MS 452. The receipt of this message starts a 460 timer for the 458 engine. B2B. If timer 474 does not expire and another message is received before expiration, within a predetermined time interval, the timer is reset. If, however, timer 472 expires in the B2B 458 engine, meaning that the B2B 458 engine did not receive any message from the user in a certain amount of time, the B2B 458 engine will assume that the mobile telephone station 452 it has been disconnected, for example, some time after the transmission of the SMS message 462 to the B2B 458 engine. This, as an example, could be an indication that the user is busy or asleep and that the portal should not send new content to the subscriber user. After the B2B 458 engine fails to receive another message after the SMS message 462 in the timer period, the B2B 458 engine validates and processes 464 this event, and sends an event notification 466, which contains the MSISDN of that user and an indication of the subscribed OFF event, to a portal 468 associated with this event. Portal 468 recognizes 470 after receipt of the notification.

Referring now to FIGURE 11, a time diagram of a usual operation of the system and methodology is illustrated, in a preferred embodiment of the present invention, the steps that are generally designated by reference number 500. As with the An embodiment described in connection with FIGURE 12, a subscriber end user enters information and preferences (step 504) in a portal 502, particularly in the database of a portal. After the end-user preferences are stored 504 in the portal database and, preferably, before the event occurs, a SIM application for real-time services and wireless activation for a subscriber user is initialized, and a plurality of SIM data is downloaded (step 506) from the portal database to a Short Message Switching Center (SMSC - Short Message Switching Center) 508, for example, on an air interface. The SIM data is then sent peer-to-peer (step 510) to the Mobile Equipment (ME) that includes a SIM card in it, generally designated by reference number 514 Once the event occurs with respect to any change in user preferences, location, etc., a set of SIM tools, generally designated by reference number 516, which resides in the mobile telephone equipment 512 , sends an SMS message 518 informing the B2B 520 engine of the status of the subscriber and providing the user's MSISDN number. When it reaches the B2B 520 engine, particularly a listener for connection 522 thereof, the aforementioned SMS message 518 is unpacked (step 524) in the B2B 520 engine by the listener for connection 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 designated by the reference number 528 in the B2B 520 engine, when the 526 information of the new event is received, It then establishes a new connection 830 and validates 532 the subscribed event 526 comparing the identity and preferences of the user with what is stored in a B2B database, generally designated by the reference number 534. When the information is received of the new connection and validation, a third layer or class, generally designated in the figure by reference number 536, processes the event (step 538) and optionally stores the inf Modified order in the B2B database 534. The processed event information 534 is sent 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 engine. of B2B 520, informing portal 502 that an event has been received and providing the 802 portal with the user's MSISDN.

image9

Portal 502, when the event notification message 542 is received then sends an acknowledgment message 544 to the B2B 520 engine, acknowledging the receipt of the event notification 542, preferably using an HTTP protocol. In a preferred embodiment of the present invention, charge 546 takes place for all information provided, and charge 546 for real-time event information provided to portal 502 will occur after acknowledgment message 544. The billing record will be created. in the B2B engine that will write down all the relevant information related to the event. As illustrated, the information is preferably provided by the portal 502 to the end user in 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.

As explained above and particularly in connection with FIGURES 12 and 13, the subscriber uses a Mobile Equipment (ME), sometimes called a mobile telephone station, which includes a SIM card 514, in the which is programmed and running a SIM application. In a preferred embodiment of the present invention, a B2B 520 engine client application resides in the Subscriber Identification Module (SIM) and is responsible for reporting real-time events that occur within the mobile equipment (ME - Mobile telephone equipment) / Network Entity to the B2B 820 engine server node. The client application uses SIM card activators 514 to request a SIM toolset operation 516 to send short messages to the server B2B engine with information about real-time events taking place in the ME Network. In this embodiment, the short message sent is directed to the B2B engine and the mobile telecommunication operator acts as a conduit for this information. The SIM 516 Application toolset provides mechanisms that allow applications, which exist in SIM 514, to interact and operate with the Mobile Equipment (ME) download the ME Profile to SIM 514, download data (step 506) to SIM 514, transfer a user menu selection to SIM 514, call control by SIM 514, MO Short Message control by SIM 514 and security. Proactive SIM 514 could display text, interpret a tone, send a short message, establish a call, etc., as understood in the sector.

The interaction between SIM 514 and ME 512 is best known with reference to the following examples described in connection with FIGURES 12 and 13, which illustrate a preferred embodiment of the SIM / mobile entity reporting events to the B2B engine for services in real time. By changing the status or preferences of the user's user, the B2B engine is updated for such change by the Mobile Equipment (ME). In these figures, the sample events that are reported to the B2B engine server are ON / OFF, Cell Global Identity (CGI) and the change of Location Area.

Referring now to FIGURE 12, a time diagram, generally designated in the figure by reference number 550, of a user indication "ON" to a B2B 552 engine is illustrated in detail. Initially, a Mobile Equipment (ME) 554 given initializes first an associated SIM 556. This initialization (step 558) is given by activating and testing the SIM device 556 to determine which functions are supported. Currently, this initialization of SIM 856 is preferably carried out in accordance with a GSM 11.11 standard, although it is understood that alternatively alternative initialization protocols may be used. The identification of a proactive SIM 556 is given at this stage having the proactive SIM service activated in a SIM service table (step 560). However, if the ME 554 does not support the proactive SIM feature, the proactive SIM 556 will not send orders related to the proactive SIM to the ME, and vice versa. The ME 554 will then send a STATUS order (step 562) periodically to the proactive SIM 556 during idle mode, as well as during a call, thereby allowing the proactive SIM 556 to respond with an order since the ME 554 always starts orders to SIM 556.

image10

After a power up by ME 554, the first message sent is the STATUS message (step 564), which is used to activate (step 564) the appropriate B2B 552 engine client application resident on the SIM card. The client application reads appropriate files in SIM 556 and packages the relevant information in a short message and asks the SIM to transmit it to the ME (step 570). SIM 856 sends a message (step 566) informing ME 554 that other information is available. The ME 554 then responds using a SEARCH command (step 568) to obtain the information of the SIM 556. The SIM 556, when it receives the SEARCH 568 order mentioned above, sends the short composite message from the client application to the ME 554 (step 570A) in order for the information to be sent to the B2B engine. Following the above, the ME 554 sends the short message (step 572) to the B2B engine, informing that the MS 554 has been connected. The B2B 552 engine receives this message and interprets it also to provide better services. The ME 554 then responds to SIM 556 informing that the message regarding the event has been sent (step 574). SIM 556, in turn, recognizes the response and sends a normal completion message (step 576). The mobile telephone station is then connected and all the elements, such as the ME 554, the SIM 556 and the client applications 552 are aware of that occurrence. As explained above, the ME 8454 sends a periodic status order (step 578) to SIM 856, which after the ME 554 is turned on, results in an activation (step 580) to the client application 552 in SIM card 552, and from which a periodic SMS message could be sent (step 578).

Referring now to FIGURE 13, a timing diagram of a location change indication of the ME 554 to the B2B 552 engine is illustrated, in another presently preferred embodiment of the present invention. As illustrated, initialization of SIM 556 and determination of proactive SIM (Steps 558 and 560) are carried out first, again, preferably, complying with a GSM protocol 11.11. As understood in the sector, the 554 Mobile Telephone Equipment is requested by the client application and the SIM to monitor any change of location and, through any such change, the ME 554 informs the B2B 552 engine of this change. The location information as explained above may be GPS information, global cell identity information or routing area information associated with a mobile telephone subscriber. Additionally, Mobile Telephone Equipment 554 can also communicate using other packet-based protocols, such as USSD or WAP messages.

As explained, when a change in location occurs, appropriate processes are called in ME 554. The ME sends a location update status message (step 586) to SIM 856, and then informs the application of the client residing in the SIM, by means of a wrap order (step 588), that the location area update has taken place. The client application is activated 588A and takes this data from the wrapping order, reads and adds appropriate data from SIM 556 and packages a short message. This short packaged message is sent (step 590) by a client application to SIM 556, as indicated in FIGURE 13, in step 590A the SIM informs the ME of the request to send a short message. With the order FETCH 592 the ME asks the SIM to provide data for the short message, which it does in step 593. The ME transmits the short message packaged to the B2B engine (step 594) that uses the data to provide better services . The ME 554 then informs SIM 556 as always that a short message has been sent (step 596) and SIM 556 returns a normal completion message (step 598).

The updated information is sent to the B2B engine by the mobile phone station to update its status and preferences in the B2B engine, as described here above. However, in another preferred embodiment of the present invention, the network nodes auto monitor any update of desired subscriber events and automatically provide the data to the B2B engine in real time.

Referring now to FIGURE 14, the B2B 210 engine, in addition to being connected to a 640 portal or content aggregators, for example, using a Transmission Control Protocol / Internet Protocol (TCP / IP - Transmission Control Protocol / Internet Protocol) and another packet-based protocol, is also connected to several more nodes of the network, generally designated in FIGURE 14 by the reference number

600. It should be understood, as described with reference to a preferred embodiment of the present invention, that these nodes could be adapted to collect real-time information about the subscriber user. This could be achieved by programming the network nodes so that they can monitor real-time information to the B2B engine regarding the subscriber events received. The network elements can monitor and send all the events and activities of the subscriber to all the subscribers that are served within the network area, or alternatively, the network elements can monitor and send events and activities of the subscriber to those subscribers who are subscribers With the B2B engine. The interfaces of the B2B 210 engine with network nodes of network 600 to receive information about subscribed events of those nodes. The Mobile Switching Center (MSC) / Visitor Location Register (VRL) 615 sends mobility information, VLR registration and event call control corresponding to a subscriber, for example , using Message TCP / IP protocols or the like. Sending information in real time is activated when a location update or registration signal is received from the subscriber.

image11

Also, transfer triggers and radio-related activation events of the Radio Network Subsystem (RNS

- Radio Network Subsystem) 620 for the 600 system are sent to the B2B engine. As an expert understands, a Serving Generalized Packet Radio System (GPRS - Generalized Packet Radio System) Service Node (SGSN - GPRS Service Node) 625 provides mobility information and related to B2B 210 engine call control, by for example, as networks related to the domain in packets, such as a generalized packet radio system (GPRS).

A Mobile Positioning Center (MPC) provides the B2B engine 210 with information about the location of the mobile telephone subscriber within the telecommunications network. An expert should understand that the MPC 630 could be provided by a global positioning service (GPS) or by any other means to locate a mobile telephone subscriber station using, for example, TCP / IP protocols to send Location information A central service control function unit (CSCF - Central Service Control Function) 635 provides the B2B engine 210 with a translation of the subscriber's address number to an Internet protocol address (IP) and could also provide events / information related to the control using, for example, message and TCP / IP protocols.

As an expert in the telecommunications sector also understands, connecting a mobile station (MS - Mobile Telephony Station), the MSC / VLR (Mobile Switching Center / Visitor Location Register - Mobile Telephone Switching Center / Visitor Location Register ) service records the MS and authorizes the MS by contacting the Home Location Register (HLR) associated with that MS. The HLR then informs the B2B engine, through this registration and authorization, that it sends the preferred information to the mobile telephony station, as shown in a preferred embodiment described in what follows here.

The network nodes are intelligently programmed to recognize any information related to the subscribed user and by activating an event, they send the information in real time to the B2B engine informing them of the update to the state of the end user. This information is stored in the B2B engine database. The B2B 210 engine processes the information / events sent by the nodes and sends this formatted information to portal 640. By providing information / events to portal 340 through the B2B 210 engine, portal 640 is charged for this information in time real, for example, through a Billing Gateway (BGW - Billing Gateway) 645. BGW 645 provides information about when and how much to charge portals for real-time information provided. This is done by writing down relevant information in charge records for each action required by the user. The charge could be performed internally in the B2B engine using a charge module, as shown in FIGURE 7, or it could be an external application connected to the B2B engine, such as a BGW, as shown in FIGURE 14. Also, the BGW could be responsible for carrying out the charge in the mobile operator for each user or providing information, for example, in the remaining balance for subscribers accessing the network or the balance of subscriber use. BGW functionalities are numerous and flexible depending on the services and plan for each subscriber user.

In the preferred embodiment described hereinbefore, the network nodes preferably contain a client application (CL - Client Application) / monitoring agent (MA - Monitoring Agent) programmed in each of the network nodes that wish to report events to the B2B engine. These network nodes monitor certain user-related activations and report them to the B2B engine. The loading of a client application program on certain network nodes such as the HLR and / or the MSC / VLR could be used to monitor certain permitted triggers related to the subscriber's behavior, status, mobility parameters, etc. An example of the network nodes that provide the information to the B2B engine through any changes to a state or user preferences is provided below in this memory. Through any update to the user's status or any change related to the user in a database, the HLR client application is activated and sends an update to the B2B engine informing the engine of such change. This client application in the HLR is adapted to recognize any changes 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 activation mechanism of the client application. The MSC / VLR, for example, tracks user mobility and when a change is detected, for example, the user's location changes, the MSC / VLR client application is activated and informs the B2B engine of this change. In addition, the MSC could not work together with the MPC to indicate the user's location and send the information to the B2B engine. Also, the MSC / VLR client application is programmed to interact with the RNS to inform the B2B engine of any transfer or radio triggers that occur relative to the user. The RNS also contains a client application as in all network nodes involved in the update process.

FIGURE 15 illustrates another example of the notification, by the network node, of any change in the status and location of the subscriber. VLR 652, when there is any change in the status and location of the subscriber, will inform HLR 654 that it uses the existing standard protocols, for example, MAP 658, of such change. The determination of the change of state is carried out using a Monitoring Agent (MA - Monitoring Agent) 656 both within VLR 652 and HLR 654. The HLR 654 in turn will interact with the B2B 660 engine, which in this location is acting as a VLR 664. The B2B 660 engine, in this case, being a GSM node Srevice Control Function (gsmSCF - GSM Service Control Function) 662 obtains the status of the subscriber and the location information of the HLR 654 and stores it in a database. The B2B engine then carries out the necessary operations in this information and acts accordingly. In general, once the client application obtains an activation event on the network nodes (i.e., HLR, MSC / VLR, etc.) representing any change in the subscriber's status, the client application on the nodes of network informs the B2B engine.

image12

With another reference to FIGURE 14, the B2B engine 210, as described hereinbefore, could receive information / events related to the subscriber user of the network nodes without requesting this information. However, in another preferred embodiment of the present invention and also referring to FIGURE 14, these network nodes are asked to collect real-time information about the subscriber user. When the subscription event is stored in the B2B 210 engine database, a Home Location Register (HLR) is probed to determine the registration information of the mobile telephone subscriber, for example, using protocols Mobile Application Part (MAP), TCP / IP or others.

The B2B 210 engine interacts with communication nodes in network 600 to request information about the subscribed events of these nodes. The B2B 210 engine polls a Mobile Switching Center (MSC) / Visitor Location Register (VLR - Visitor Location Register) 615 to request mobility information, VLR registration and call control of events related to a subscriber, for example, using Message or other TCP / IP protocols. The B2B 210 engine requests a transfer activation and radio-related activation events from the Radio Network Subsystem (RNS) for the 600 system. A Mobile Positioning Center (MPC - Mobile Phone Location Center) 330 could be probed to provide the B2B engine 210 with information about the location of the mobile telephone subscriber within the telecommunications network. One skilled in the art should understand that the MPC 630 could be any other means to locate a mobile telephone subscriber station, as described hereinbefore. A central service control function (CSCF) 635 unit could also be probed to provide the B2B engine 210 with a translation of the subscriber's address number to an Internet Protocol (IP) address. , and could also provide control-related events / information using, for example, Message and TCP / IP protocols.

The B2B 210 engine provides intelligence to know which of the elements or nodes mentioned above probed to gather the necessary information for provision to a portal 640 using, for example, TCP / IP protocols. The information can be selectively requested according to the needs of the B2B engine in determining the status of a telecommunications device. The B2B 210 engine processes the information / events sent by the nodes and sends the information gathered to portal 640. By providing the information / events to portal 640 through the B2B 210 engine, portal 640 is charged a fee for this information in real time, as described hereinbefore with reference to the previous embodiment.

As an example, when the B2B engine requires certain information such as the HLR subscriber's status, a message is sent to the HLR requesting the information. The HLR will respond in turn with the reply message informing the B2B engine of the current subscriber's status. This same request mechanism could be used with the other network nodes. The B2B engine could send a message to any network node requesting information about the subscriber. When it receives such a message, the network node obtains the information and sends it to the B2B engine. The B2B engine could act as a GSM Service Control Function node (gsmSCF - GSM Service Control Function and interrogates the HLR at regular or periodic intervals to obtain the status and location information of a subscriber.

The network environment, within which the B2B 210 engine operates, is fully described earlier in this memory. In general, there are numerous service implementations provided by the business-to-business engine. Referring now to FIGURE 16, however, an alternative operation of the B2B engine 210 of the present invention is illustrated. In this alternative configuration, the B2B engine 210 receives real-time events from a mobile telephone subscriber 660, such as the status of the subscriber with reference to FIGURES 9-13, using for example Short Message Service messages (SMS - Service of short messages). The B2B engine 210 obtains this information, in addition to the other information, by polling different nodes in the network, as described hereinbefore with reference to a preferred embodiment. The network nodes, however, as described in another preferred embodiment described above herein, send the updated status information of the user to the B2B engine whenever any change regarding the subscriber occurs. The B2B 210 engine then analyzes the events based on the preferences of the subscribed user and processes the information / event gathered.

These processed events are then sent to the provider 640 of portal / content aggregators / content, for example, using an HTTP protocol. Portal 640 below customizes the contents according to the event information provided by the B2B 210 engine. The portal converts the contents, for example, to a wireless markup language (WML) used to provide content to Narrowband devices, such as mobile phone stations, PDAs, etc. The WML that contains the personalized content is provided by means of a wireless Application Protocol Gateway (WAPGW) to the subscriber via the mobile phone. However, the portal can also provide personalized content using an SMS message or any other proprietary wireless data protocol. As illustrated in FIGURE 16, the contents could be sent to the mobile telephone station via a Wireless Application Protocol Gateway (WAPGW - Wireless Application Protocol Gateway). The WAPGW is a network node that provides a direct connection between the mobile telephone network and dedicated Internet application services, such as portals. There are numerous methods that could be used to send the contents to the subscriber. For example, the contents could be sent via Short Message Service Center (SMSC - Short Message Service Center) using a Short message (SMS) or a WAP sent over an SMS message. In addition, the contents sent to the mobile telephone station could be Unstructured Supplementary Service Data (USSD - Unstructured Supplementary Service Data). This could be done using a USSD Gateway that extracts the information from the portals and sends it to the SMSC for delivery as a short message. Other transport carriers such as GPRS could be used to send content from the portals to the mobile phone station. Advances towards high-speed access systems in today's mobile phone technology lead the way to third-generation wireless (3G - Third Generation) systems. Data packet transport systems such as Generalized Packet Radio Service (GPRS

image13

- Generalized Packet Radio Service) and the Evolved Data for GSM Evolution (EDGE) provide fast connections that will allow easy and fast delivery of content to mobile phone stations. With these transport carriers in mind, all communication between mobile phone stations, the B2B engine, and Internet portals could be carried out using these transport carriers explained in this report. For example, instead of sending an SMS message via a mobile phone station through an SMSC, as described earlier in this report, a mobile phone station could communicate with the B2B engine using a network of GPRS sending data packets using high speed access.

With reference to FIGURE 17, the B2B engine 210, in addition to being connected to a portal 640 or content aggregators, for example, using a Transmission Control Protocol / Internet Protocol (TCP / IP - Transmission Control Protocol / Protocol Internet), is also connected to several other nodes in the network. In general, it should be understood that these network nodes are typically used to gather real-time information about the subscriber user. The network nodes communicate with each other using standard protocols. These protocols are used to facilitate the means of communication between network nodes and to be compatible with the requirement standards. With another reference to FIGURE 17, a preferred embodiment of the protocols used in the communication between the network nodes and the aforementioned B2B 210 engine is illustrated. It should be understood that the B2B 210 engine preferably interacts with all nodes of the network that provide event information, for example, using an IEEE 802.3 standard connection.

Communication between the nodes is carried out, as in other communication standards, using a layer structure. For example, all the protocols used use the Transmission Control Protocol / Internet Protocol (TCP / IP - Transmission Control Protocol / Internet Protocol) in their lower layers. However, in the upper layer each node uses a different protocol. For example, the B2B 210 engine communicates with portal 640 using a Hypertext Transfer Protocol (HTTP - Hypertext Transfer Protocol commonly used in Internet communication. The HLR 610 uses a MAP protocol. The Mobile Positioning Center (MPC - Mobile Phone Location Center) 630 preferably uses an MPC protocol A Short Messaging Service Center (SMSC) 650 preferably uses a Peer-to-Peer Short Message Protocol (SMPP). a-Par) The particular protocols used are well known in the sector and provide a means of interconnection between the different nodes in the network, however, it should be understood that a variety of other protocols could be used to support internal communications.

Referring now to FIGURE 18, which illustrates the B2B engine interacting with different network architectures. The B2B engine interacts with a 2.5G 710 wireless telecommunications system as shown in this figure and in FIGURE 14 above. However, the B2B engine could interact with other systems such as a second generation (2G) 730 wireless telecommunications operator system. It can also be interconnected with a 3G 750 wireless telecommunications system that is currently under development. Although 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 described earlier in this report. For example, the B2B engine could poll each of the network nodes in the 3G 750 wireless telecommunications system, or the network nodes could report any event to the B2B 210 engine regarding any update to the status of the subscriber. The engine described in the present invention could be used for numerous systems and the same procedure described hereinbefore for the 2.5G wireless telecommunications system could be applied to the 3G wireless system, as well as to other systems. The network nodes in the 3G wireless system are divided into 760 call control network nodes.

image14

770. 780 and on 790 connectivity control network nodes. Media Gateways (MGW - Media Gateway) 792 will be responsible for all means of connection capability, while call control will be executed by servers in the control layer The Control Layer, in turn, will interact with the Application Link Doors, not shown in the figure, allowing an unprecedented level of service separation from specific fixed or mobile phone carrier technologies allowing, in any way, that the service be provided anywhere and at any time. The B2B engine has the ability to connect different carrier technologies such as GSM / EDGE, WCDMA CDMA2000. The B2B engine also interacts with all the connection and control capacity nodes that track and / or register the mobile telephone subscriber. The network nodes, however, are preferably reprogrammed to include a mobility agent, as described hereinbefore with reference to FIGURES 14 and 15.

Also the mobile telephone operator described hereinbefore is a GSM operator, a person not skilled in the art should understand that the invention could be used by a PCS operator, a DAMPS operator and / or by any telephone operator. existing mobile. In addition, a single B2B engine could interconnect several mobile phone operators with several portals. Mobile phone operators could be of a different nature and use a different standard, for example, a B2B engine could provide service for a PCS operator as well as a GSM operator, concurrently. In addition, 3G mobile phone stations will also have the client application that will notify the B2B engine of any update to the user's status, similar to the one described above for GSM phones that have the client application programmed on the card of SIM in the GSM network. The SIM card as described above could be any means in which the Mobile Telephone Equipment could have a programmable module in it capable of containing applications. The SIM card described above in this memory could also be any programmable medium that is capable of storing and carrying out certain functions, such as having a fixed module in the mobile telephone station that is part of the Mobile Equipment (ME - Telephony Equipment Mobile).

However, a person skilled in the art should understand that the portal and content aggregators are externally connected to the B2B engine, as described herein. However, the portal and / or content aggregators, in a preferred embodiment of the claimed invention, can also be incorporated into the B2B engine. Which means that the B2B engine could be responsible for collecting data content and selectively providing data content to users.

One skilled in the art should understand that the real-time information and real-time networks explained with reference to the embodiments previously herein, represent the ideal times of such networks and information regardless of any delay and / or processing in the nodes. network and any other equipment. In general, a real-time network can be any network that works in real time or near real-time operation. Also, real time information may be information that is substantially real time or near real time.

As those skilled in the art will recognize, the innovative concepts described in the present application can be modified and varied in a wide range of applications. Accordingly, the scope of the subject matter of the patented matter should not be limited to any of the specific example teachings explained, but instead is defined by the following claims.

image15

Claims (8)

one.

 A method of providing unsolicited content information from a content provider to a telecommunications device that operates in a mobile telephony telecommunications system, being the cited method carried out in a Company-to-Company engine connected to the telecommunications system in which the aforementioned B2B engine receives real-time information from the said telecommunications system of mobile telephony and provides content information to said telephony telecommunication device mobile, the aforementioned method comprising: receive a subscription for a particular event activation associated with a telecommunications device mobile phone content provider, in which the B2B provider agrees to notify the provider of content provided that the telecommunication system reports the said event activation associated with the mobile phone telecommunications device; receive from the telecommunication system, a report of said event activation associated with the device mobile telephony telecommunications; notify the content provider that the telecommunication system has reported the said activation of event associated with the mobile phone telecommunications device; receive real-time information from the content provider in response to the notification stage; Y Send the content information to the mobile phone telecommunications device.

2.

 The method of claim 1, wherein the activation event is selected from a group consisting of: a power-up register by the mobile telecommunication telecommunications device; an update of change of location area by the mobile telecommunication telecommunications device; Y a periodic update by the mobile phone telecommunications device.

3.

 The method of claim 1, which also comprises the step of said Company-to-Company engine selectively poll a network element within said telecommunications system to receive real-time information associated with the aforementioned mobile telecommunication device and determine that the aforementioned trigger an event has taken place evaluating the information received in real time.

Four.

 The method of claim 1, which also comprises the step of said Company-to-Company engine receives a plurality of real-time information associated with said telecommunication device of mobile telephony of the aforementioned mobile telephony telecommunication system and determine that the aforementioned trigger an event has occurred comparing with the mentioned real-time information received.

5.

 A Company-to-Company engine to provide unsolicited content information from a provider of content to a mobile phone telecommunications device operating in a telecommunication system in that the aforementioned Company-to-Company engine receives real-time information from the aforementioned system of mobile telecommunication and provides content information to said device Mobile telephony telecommunications, comprising: means for receiving a subscription of a particular activation event associated with a device Mobile telephony telecommunications from a content provider, in which the Business-to-Business engine agrees to notify the content provider whenever the telecommunication system informs of said event of activation associated with the mobile telephony telecommunications device; a first interface module to communicate between the Company-to-Company engine and the system of mobile telecommunication, including the first interface module mentioned: means for receiving from the telecommunication system a report of said activation event associated with the mobile phone telecommunications device; Y means for sending content information received from the mobile telephony telecommunications device content provider; Y a second interface module to communicate between the Business-to-Business engine and the provider of content, including the aforementioned second interface module: media, responsible for receiving a report of the aforementioned activation event of the telecommunication system, to notify the content provider that the telecommunication system has reported the aforementioned event of activation associated with the telecommunications device; Y means to receive from the content provider, content information prepared in response to being notified that the telecommunication system reported the said activation event associated with the device mobile phone telecommunications.

6.

 The Business-to-Business engine of claim 5, wherein the activation event is selected from a group consisting of: a power-up register by the mobile telecommunication telecommunications device; an update of change of location area by the mobile telecommunication telecommunications device; Y a period update by the mobile phone telecommunications device.

7.

 The Company-to-Company engine of claim 5, which also comprises means for probing selectively to a network element within said mobile telephony telecommunications system to receive

real-time information associated with said mobile telecommunication device and to determine that said activation event has taken place evaluating the real-time information received.

8.

 The Business-to-Company engine of claim 5, which also comprises means for receiving a plurality of real-time information associated with said telecommunication device of said mobile telecommunication system and for determining whether said activation event It has taken place comparing with the aforementioned real-time information received.