Source: https://patents.google.com/patent/US9710828B2/en
Timestamp: 2018-08-20 13:13:29
Document Index: 669472321

Matched Legal Cases: ['§119', 'Application No. 7751948', 'Application No. 10', 'Application No. 200880122228', 'Application No. 200780008231', 'Application No. 200980103451', 'Application No. 10', 'Application No. 2009232311', 'Application No. 2008', 'Application No. 10']

US9710828B2 - System for creating separate data serving spaces for each mobile carrier in a plurality of mobile carriers - Google Patents
System for creating separate data serving spaces for each mobile carrier in a plurality of mobile carriers Download PDF
US9710828B2
US9710828B2 US14140870 US201314140870A US9710828B2 US 9710828 B2 US9710828 B2 US 9710828B2 US 14140870 US14140870 US 14140870 US 201314140870 A US201314140870 A US 201314140870A US 9710828 B2 US9710828 B2 US 9710828B2
US14140870
US20140108147A1 (en )
Kenta Umezu
Ian B. Brayshaw
A system is described for creating a separate data serving space for each mobile carrier in a plurality of mobile carriers. The system may include a processor, a memory and an interface. The memory may store a keyword, a plurality of mobile data items corresponding to the keyword and a plurality of mobile carriers, and a search request. The interface may communicate with a user through a mobile device. The processor may be operatively connected to the interface and the memory and may store the plurality of mobile data items in the memory. The processor may receive a mobile search request from a user via the interface, and may determine the mobile carrier in communication with the interface. The processor may then retrieve the mobile data item corresponding to the keyword and the determined mobile carrier and may serve the retrieved mobile data item to the user.
This patent document is a continuation of U.S. patent application Ser. No. 11/830,230, filed Jul. 30, 2007, pending, which is a continuation of U.S. patent application Ser. No. 11/712,276 filed on Feb. 28, 2007, which claims the benefit of the filing date under 35 U.S.C. §119(e) of Provisional U.S. Patent Application Ser. No. 60/779,840, filed Mar. 6, 2006, all of which are hereby incorporated herein by reference.
The present description relates generally to a system and method, generally referred to as a system, for creating separate data serving spaces for each mobile carrier in a plurality of mobile carriers, and more particularly, but not exclusively, to creating separate mobile advertisement serving spaces for each mobile carrier in a plurality of mobile carriers.
The mobile phone may be increasingly important as an information and content access device. Currently there may be over 2 billion mobile phones globally, versus 800 million personal computers. Mobile operators may be increasingly looking to high value data services as a way to overcome the continuing voice revenue decline. Billions of dollars may be being spent globally on wireless licenses with billions more in investments in the pipeline for development of infrastructure and services by wireless service and content providers. Carriers may be introducing new data, content and multimedia services as a means of generating new revenue streams, reversing negative revenue trends, retaining and attracting customers as well as increasing returns on investment, and extending and differentiating their service offering to consumers. The emergence of these wireless technologies may be creating unique opportunities for wireless carriers, advertisers and publishers to generate additional revenue streams through new and existing customers. As consumer adoption of wireless technology continues to increase, marketing via mobile devices may become an important part of all integrated data communications strategies.
However, usage patterns for mobile search and Web search may differ, as well as the expectations of the users and the advertisers. Combined with a completely different user experience, these may change the value of clicks and lead opportunities. Most current mobile devices may have limited browser capabilities that do not support the rich feature set of the Web. Handset capabilities may impact the search behavior of mobile users, where the limitations of numeric-pad keyed entry narrow the searched-for terms. The small screen size on mobile devices may have an impact on the performance of the search implementations. The size of screens on mobile handsets may limit the creative that can be displayed per listing, and the number of listings per screen. Current web search marketing systems may not account for these physical differences between mobile handsets and computers.
The mobile marketplace may be very fragmented in terms of handset and network technologies, and this may impact the display of listings and advertiser offer sites. For mobile devices, there may not be an HTML-like standard adhered to by all carriers, and the “standards” that are present may tend to be operator specific, and may be incompatible with other “standards”. This may lead to markets within markets, where, for example in Japan, advertisers may create separate sites and campaigns for NODE users, and XHTML and WML users. This fragmentation may also be barrier to entry for advertisers due to the investment required to support the different technologies and interact with each individual carrier. Advertisers may be faced with either a large start-up investment, or foregoing traffic from certain operators.
A system is disclosed for creating separate data serving spaces for each mobile carrier in a plurality of mobile carriers. The system may include a processor, a memory and an interface. The memory may be operatively connected to the processor and the interface and may store a keyword, a plurality of mobile data items, wherein each mobile data item corresponds to the keyword and a mobile carrier, and a mobile search request. The interface may be operatively connected to the memory, and the processor and may communicate with a user though a mobile device of a mobile carrier. The processor may be operatively connected to the interface and the memory, and may store the plurality of mobile data items in the memory. The processor may receive a mobile search request for the keyword from a user via the interface. The processor may determine which mobile carrier of the mobile device is with and the processor may retrieve the mobile data item corresponding to the keyword and the determined mobile carrier. The processor may serve the retrieved mobile data item to the user via the interface.
FIG. 1 is a block diagram of a general overview of a system for creating separate data serving spaces for each mobile carrier in a plurality of mobile earners.
FIG. 2 is block diagram of a simplified view of a network environment implementing a system for creating separate data serving spaces for each mobile carrier in a plurality of mobile carriers.
FIG. 3 is a block diagram of a system for creating separate data serving spaces for each mobile carrier in a plurality of mobile carriers.
FIG. 4 is a flowchart illustrating the operations of the systems of FIG. 1, FIG. 2, and FIG. 3, or other systems for creating separate data serving spaces for each mobile carrier in a plurality of mobile carriers.
FIG. 5 is a flowchart illustrating steps that may be taken by a revenue generator in the systems of FIG. 1, FIG. 2, and FIG. 3, or other systems for creating separate data serving spaces for each mobile carrier in a plurality of mobile earners.
FIG. 6 is a flowchart illustrating steps that may be taken by a user in the systems of FIG. 1, FIG. 2, and FIG. 3, or other systems for creating separate data serving spaces for each mobile carrier in a plurality of mobile carriers.
FIG. 7 is an illustration a general computer system that may be used in a system for creating separate data serving spaces for each mobile carrier in a plurality of mobile carriers.
FIG. 8 is a screenshot of a revenue generator's account summary screen in the systems of FIG. 1, FIG. 2, and FIG. 3, or other systems for creating separate data serving spaces for each mobile carrier in a plurality of mobile carriers.
FIG. 9 is a screenshot of a revenue generator's account preferences screen in the systems of FIG. 1, FIG. 2, and FIG. 3, or other systems for creating separate data serving spaces for each mobile carrier in a plurality of mobile earners.
FIG. 10 is a screenshot of a revenue generator's campaign summary screen in the systems of FIG. 1, FIG. 2, and FIG. 3, or other systems for creating separate data serving spaces for each mobile carrier in a plurality of mobile earners.
FIG. 11 is a screenshot of a revenue generator's listing management screen in the systems of FIG. 1, FIG. 2, and FIG. 3, or other systems for creating separate data serving spaces for each mobile carrier in a plurality of mobile earners.
FIG. 12 is a screenshot of a revenue generator's listing management screen showing a call offer entry in the systems of FIG. 1, FIG. 2, and FIG. 3, or other systems for creating separate data serving spaces for each mobile carrier in a plurality of mobile carriers.
FIG. 13 is a screenshot of a revenue generator's listing management screen showing a mobile site URL entry in the systems of FIG. 1, FIG. 2, and FIG. 3, or other systems for creating separate data serving spaces for each mobile carrier in a plurality of mobile carriers.
FIG. 14 is a screenshot of a revenue generator's listings' editorial status in the systems of FIG. 1, FIG. 2, and FIG. 3, or other systems for creating separate data serving spaces for each mobile carrier in a plurality of mobile carriers. [0025] FIG. 15 is a screenshot of a revenue generator's budgeting screen in the systems of FIG. 1, FIG. 2, and FIG. 3, or other systems for creating separate data serving spaces for each mobile carrier in a plurality of mobile carriers.
FIG. 16 is a screenshot of a revenue generator's add money screen in the systems of FIG. 1, FIG. 2, and FIG. 3, or other systems for creating separate data serving spaces for each mobile carrier in a plurality of mobile carriers.
FIG. 17 is a screenshot of a revenue generator's add money confirmation screen in the systems of FIG. 1, FIG. 2, and FIG. 3, or other systems for creating separate data serving spaces for each mobile carrier in a plurality of mobile carriers.
FIG. 18 is a screenshot of a revenue generator's add payment method in the systems of FIG. 1, FIG. 2, and FIG. 3, or other systems for creating separate data serving spaces for each mobile carrier in a plurality of mobile carriers.
FIG. 19 is a screenshot of a revenue generator's update payment method in the systems of FIG. 1, FIG. 2, and FIG. 3, or other systems for creating separate data serving spaces for each mobile carrier in a plurality of mobile carriers.
A system and method, generally referred to as a system, may relate to creating separate data serving spaces for each mobile carrier in a plurality of mobile carriers, and more particularly, but not exclusively, to creating separate mobile advertisement serving spaces for each mobile carrier in a plurality of mobile carriers. The principles described herein may be embodied in many different forms.
FIG. 1 provides a general overview of a system 100 for creating separate data serving spaces for each mobile carrier in a plurality of mobile carriers. Not all of the depicted components may be required, however, and some implementations may include additional components. Variations in the arrangement and type of the components may be made without departing from the spirit or scope of the claims as set forth herein. Additional, different or fewer components may be provided.
In operation, one of the revenue generators 110A-N, such as revenue generator A 110A, may provide information to the service provider 130. This information may relate to the transaction taking place between the revenue generator A 110A and the service provider 130, or may relate to an account the revenue generator A 110A maintains with the service provider 130. In the case of a revenue generator A 110A who is a mobile advertiser, the revenue generator A 110A may provide initial information necessary to open an account with the service provider 130.
A revenue generator A 110A who is a mobile advertiser may maintain one or more accounts with the service provider 130. For each account the revenue generator A 110A may maintain one or more campaigns. For each campaign the revenue generator A 110A may maintain one or more listings. A listing may include a search keyword and one or more carrier listings. Each carrier listing may identify the mobile carrier and may include an advertisement title, an advertisement description, a bid amount and a mobile site URL, if any. A carrier listing may represent an association between a search keyword, a mobile advertisement and a carrier whose users are targeted by the mobile advertisement.
There may be some instances where multiple revenue generators 110A-N may have bid on the same search keyword for the same MNO, such as MNO A 115A. The service provider 130 may serve to the users 120AA-NN the online advertisements that the users 120AA-NN may be most likely to click on. For example, the service provider 130 may include a relevancy assessment to determine the relevancy of the multiple mobile advertisements to the search keyword. The more relevant a mobile advertisement may be to the keyword the more likely it may be that the user AA 120AA may click on the advertisement. Exemplary ways to determine relevance are described in more detail below. Methods for assessing relevancy in online web search marketing may also apply to mobile search marketing.
The service provider 130 may already have information relating to the geographic location of the user AA 120AA and other information describing the user A 120A, such as gender, age, etc. This information may have been previously supplied to the service provider 130 by the user AA 120AA. Alternatively or in addition, the service provider 130 may obtain the location of the user AA 120AA based on the IP address of the user AA 120AA. The service provider 130 may use a current date/time stamp to store the date/time when the user AA 120AA interacted with the service provider 130. The service provider 130 may use any of the information describing the user, or the keyword searched for by the user, in determining the relevancy of an advertisement to the search.
FIG. 2 provides a simplified view of a network environment implementing a system 200 for creating separate data serving spaces for each mobile carrier in a plurality of mobile carriers. Not all of the depicted components may be required, however, and some implementations may include additional components not shown in the figure. Variations in the arrangement and type of the components may be made without departing from the spirit or scope of the claims as set forth herein. Additional, different or fewer components may be provided.
Some or all of the advertising services server 260, service provider server 240, and third-party server 250 may be in communication with each other by way of network 235 and may be the system or components described below in FIG. 7. The advertising services server 260, third-party server 250 and service provider server 240 may each represent multiple linked computing devices. Multiple distinct third party servers, such as the third-party server 250, may be included in the system 200. The third-party server 250 may be an MNO gateway server 215A-N or a server associated with, or in communication with, an MNO gateway server 215A-N.
The data connection of the mobile device may be a cellular connection, such as a GSM/GPRS/WCDMA connection, a wireless data connection, an internet connection, an infra-red connection, a Bluetooth connection, or any other connection capable of transmitting data. The data connection may be used to connect directly to the network 230, or to connect to the network 230 through the MNO gateway servers 215A-N. The MNO gateway servers 215A-N may control the access the mobile applications 210AA-NN may have to the network. The MNO gateway servers 215A-N may also control the technology supporting the respective mobile applications 220AA-NN. This may affect all aspects of the user experience, such as signal strength and availability, speed and billing mechanisms. For example, the MNO gateway server A 215A may only allow the users 120AA-NN access to content provided by partners of the MNO A 115A. Furthermore, the MNO gateway servers 215A-N may only allow users 120AA-NN access to data in a specific format, such as WML, XHTML, NTT DOCOMO NODE HTML, or cHTML. Alternatively or in addition, the mobile applications 220AA-NN may only support one of the aforementioned formats.
The service provider server 240 may include one or more of the following: an application server, a data source, such as a database server, a middleware server, and an advertising services server. One middleware server may be a mobile commerce platform, such as the YAHOO! SUSHI platform, which may properly encode data, such as mobile pages or mobile advertisements, to the formats specific to the MNO gateway servers 215A-N. The service provider server 240 may co-exist on one machine or may be running in a distributed configuration on one or more machines. The service provider server 240 may collectively be referred to as the server. The service provider server 240 may receive requests from the users 120AA-NN and the revenue generators 110AA-NN and may serve mobile pages to the users 120AA-NN and web pages and/or mobile pages to the revenue generators 110A-N based on their requests.
There may be several configurations of database servers, application servers, middleware servers and advertising services servers included in the service provider server 240 or the third party server 250. Database servers may include MICROSOFT SQL SERVER, ORACLE, IBM DB2 or any other database software, relational or otherwise. The application server may be APACHE TOMCAT, MICROSOFT IIS, ADOBE COLDFUSION, Y APACHE or any other application server that supports communication protocols. The middleware server may be any middleware that connects software components or applications. The application server on the service provider server 240 or the third party server 250 may serve pages, such as web pages to the users 120A-N and the revenue generators 110A-N. The advertising services server 260 may also exist independent of the service provider server 240 and the third party server 250.
FIG. 3 provides a view of the functionality of creating separate data serving spaces for each mobile carrier in a plurality of mobile carriers. Not all of the depicted components may be required, however, and some implementations may include additional components not shown in the figure. Variations in the arrangement and type of the components may be made without departing from the spirit or scope of the claims as set forth herein. Additional, different or fewer components may be provided.
Alternatively or in addition, the service provider 130 may provide distinct mobile search sites for each of the MNOs 115A-N and the world wide web. The mobile search sites may contain a hidden input variable or some other indicator that indicates the source of the search request. For example the mobile search site for the carrier SPRINT may include a hidden INPUT variable with a value of “usmobsprintsb” indicating that the search request originated from the MNO SPRINT. Alternatively or in addition the service provider 130 may provide a dedicated feed for each of the MNOs 115A-N. The feed may be implemented by a separate application server for each of the MNOs 115A-N. The particular feed the request is received from may indicate the source of the request.
Once the traffic controller 350 determines the origin of the traffic, the traffic controller 350 may forward the traffic to the appropriate handler. If the traffic originated from one of the MNOs 115A-N, then the traffic may be directed to the mobile traffic handler 330. If the traffic was generated from the world wide web 310, the traffic controller 350 may direct the traffic to the web traffic handler 340. If the system 100 implements keyword separation through the use of a database field, the traffic controller 350 may supply the origin of the request to the mobile traffic handler 330.
Alternatively, or in addition, the service provider 130 may utilize middleware, such as the YAHOO! SUSHI platform, to properly encode the “WAP ads” for each MNO 115A-N. The data associated with the “WAP ad” may be communicated to the middleware in XML format and the middleware may encode the “WAP ad” to conform to the underlying technology of each MNO 115A-N, such as WML, XHTML, NTT DOCOMO NODE HTML, or cHTML.
FIG. 4 is a flow chart illustrating the operations of the systems of FIG. 1, FIG. 2, and FIG. 3, or other systems for creating separate data serving spaces for each mobile carrier in a plurality of mobile carriers. At block 410, the service provider 130 may receive a keyword search request from one of the users 120AA-NN, such as the user AA 120AA. At block 420 the service provider 130 may identify the source of the request, such as by identifying the IP address of the requesting user AA 120AA. The IP address of the request may be used to determine whether the request originated from a mobile network, and, if so, which mobile network. If the request was generated by a page belonging to the service provider 130, the page may have hidden variables identifying the source MNO of the request. Alternatively or in addition the service provider 130 may have a dedicated feed for the MNO.
At block 430, the service provider 130 may determine whether the request originated from a mobile network. If the request did not originate from a mobile network, the system 100 may move to block 440. At block 440 the request may be handled as traditional web traffic and may be forwarded to the web search marketing system. If the service provider 130 determines the request was generated from a mobile network the system 100 may move to block 450. At block 450 the originating mobile network, may be identified, such as the MNO A 115A. The mobile network may be identified by the IP address of the requesting user AA 120AA. If the request was generated by a page belonging to the service provider 130, the page may have hidden variables identifying the source MNO of the request. Alternatively or in addition the service provider 130 may have a dedicated feed for the MNO.
Once the revenue generator, such as the revenue generator A 110A, has been selected, the system 100 may move to block 470. At block 470 the service provider 130 may determine whether the revenue generator A 110A has a mobile advertisement for the MNO A 115A. If the revenue generator A 110A does not have a mobile advertisement the system 100 may move to block 480. At block 480 the service provider 130 may generate the aforementioned “WAP ad” for the revenue generator A 110A. The “WAP” ad may be based on data stored in the advertisement title and/or advertisement description field of the MNO listing.
FIG. 5 is a flowchart illustrating steps that may be taken by one of the revenue generators 110A-N in the systems of FIG. 1, FIG. 2, and FIG. 3, or other systems for creating separate data serving spaces for each mobile carrier in a plurality of mobile carriers. The steps may occur when one of the revenue generators 110A-N, such as the revenue generator A 110A, wishes to bid on keywords for a carrier, such as the MNO A 115A. At block 510 the revenue generator A 110A interacts with the service provider server 240, such as by logging onto the service provider 130. At block 520 the revenue generator A 110A may communicate a request to bid on mobile keywords.
FIG. 6 is a flowchart illustrating steps that may be taken by one of the users 120AA-NN in the systems of FIG. 1, FIG. 2, and FIG. 3, or other systems for creating separate data serving spaces for each mobile carrier in a plurality of mobile carriers. The steps may occur when one of the users 120AA-NN, such as the user AA 120AA, performs a search on a mobile application 220AA-NN, such as the mobile application AA 220AA, via a MNO 115A-N, such as the MNO A 115A. At block 610, the user AA 120AA may interact with the service provider 130 via the mobile application AA 220AA, such as by performing a search from the mobile application AA 220AA. At block 620 the service provider 130 may determine the carrier the request of the user AA 120AA originates from, such as the MNO A 115A. At block 630 the service provider 130 may determine which advertisements may relate to the keyword searched for on the MNO A 115A. The service provider 130 may select advertisements from revenue generators 110A-N who may have bid on the keyword searched for from the MNO A 115A. The service provider 130 may select an advertisement of the revenue generator A 110A with the highest bid for the keyword from the MNO A 115A. Alternatively or in addition the service provider 130 may select more than one advertisement to display to the user AA 120AA. The size of the screen on the device of the user AA 120AA may be a factor used in determining how many advertisements to communicate to the user AA 120AA.
FIG. 7 illustrates a general computer system 700, which may represent a service provider server 240, a third party server 250, an advertising services server 260, a mobile device or any of the other computing devices referenced herein. The computer system 700 may include a set of instructions 724 that may be executed to cause the computer system 700 to perform anyone or more of the methods or computer based functions disclosed herein. The computer system 700 may operate as a standalone device or may be connected, e.g., using a network, to other computer systems or peripheral devices.
In a networked deployment, the computer system may operate in the capacity of a server or as a client user computer in a server-client user network environment, or as a peer computer system in a peer-to-peer (or distributed) network environment. The computer system 700 may also be implemented as or incorporated into various devices, such as a personal computer (PC), a tablet PC, a set-top box (STB), a personal digital assistant (PDA), a mobile device, a palmtop computer, a laptop computer, a desktop computer, a communications device, a wireless telephone, a land-line telephone, a control system, a camera, a scanner, a facsimile machine, a printer, a pager, a personal trusted device, a web appliance, a network router, switch or bridge, or any other machine capable of executing a set of instructions 724 (sequential or otherwise) that specify actions to be taken by that machine. In a particular embodiment, the computer system 700 may be implemented using electronic devices that provide voice, video or data communication. Further, while a single computer system 700 may be illustrated, the term “system” shall also be taken to include any collection of systems or subsystems that individually or jointly execute a set, or multiple sets, of instructions to perform one or more computer functions.
The computer-readable medium 722 may be a single medium, or the computer-readable medium 722 may be a single medium or multiple media, such as a centralized or distributed database, and/or associated caches and servers that store one or more sets of instructions. The term “computer-readable medium” may also include any medium that may be capable of storing, encoding or carrying a set of instructions for execution by a processor or that may cause a computer system to perform anyone or more of the methods or operations disclosed herein.
The computer-readable medium 722 may include a solid-state memory such as a memory card or other package that houses one or more non-volatile read-only memories. The computer-readable medium 722 also may be a random access memory or other volatile re-writable memory. Additionally, the compute-readable medium 722 may include a magneto-optical or optical medium, such as a disk or tapes or other storage device to capture carrier wave signals such as a signal communicated over a transmission medium. A digital file attachment to an e-mail or other self-contained information archive or set of archives may be considered a distribution medium that may be a tangible storage medium. Accordingly, the disclosure may be considered to include anyone or more of a computer-readable medium or a distribution medium and other equivalents and successor media, in which data or instructions may be stored.
FIG. 8 is a screenshot 800 of an implementation of a revenue generator account summary view of a revenue generator interface in the systems of FIG. 1, FIG. 2, and FIG. 3, or other systems for creating separate data serving spaces for each mobile carrier in a plurality of mobile carriers. A revenue generator interface may be displayed to one of the revenue generators 110A-N, such as the revenue generator A 110A, when the revenue generator A 110A interacts with the service provider 130. The screenshot 800 may include an alerts table 810, an account summary table 820, an account performance table 830, an account drop-down box 840, and a revenue generator identifier 850.
The revenue generator currently interacting with the service provider 130 may be identified by the revenue generator identifier 850. In the screenshot 800, the revenue generator may be identified as “ysmmobile”. The revenue generator A 110A may be able to change the account being viewed by selecting a different account from the account drop-down box 840. In the screenshot 840 the account currently being viewed may be “Mobile Test A/C (2010 165833)”. The alerts table 810, account summary table 820 and account performance table 830, may display data relating to the selected account, such as the “Mobile Test A/C (2010165833)” account.
FIG. 9 is a screenshot 900 of an implementation of a revenue generator account preferences view of a revenue generator interface in the systems of FIG. 1, FIG. 2, and FIG. 3, or other systems for creating separate data serving spaces for each mobile carrier in a plurality of mobile carriers. A revenue generator interface may be displayed to one of the revenue generators 110A-N, such as the revenue generator A 110A, when the revenue generator A 110A interacts with the service provider 130. The account preferences screen may allow the revenue generator A 110A to view or change default settings for the selected account. The screenshot 900 may include an account drop-down box 840, a revenue generator identifier 850, a default bid textbox 910, a mobile site checkbox 920, a default URL textbox 930, a default phone number textbox 940, a logo display 950, a logo textbox 960, a browse button 970 and an update button 980.
FIG. 10 is a screenshot 1000 of an implementation of a revenue generator campaign summary view of a revenue generator interface in the systems of FIG. 1, FIG. 2, and FIG. 3, or other systems for creating separate data serving spaces for each mobile carrier in a plurality of mobile carriers. A revenue generator interface may be displayed to one of the revenue generators 110A-N, such as the revenue generator A 110A, when the revenue generator A 110A interacts with the service provider 130. The campaign summary screen may allow the revenue generator A 110A to view the current campaigns, change the status of the campaigns and rename, add or delete campaigns. The screenshot 1000 may include a campaign summary table 1010, an account drop-down box 840, and a revenue generator identifier 850. The campaign summary table 1010 may include an add campaign textbox 1020, an add campaign button 1022, an update button 1018 and one or more rows of data, each representing a campaign of the revenue generator A 110A. Each row of data may include a campaign name link 1012, the number of keywords in the campaign, the status of the campaign, a new status drop-down box 1040, a rename campaign textbox 1014, and a delete checkbox 1016.
FIG. 11 is a screenshot 1100 of an implementation of a revenue generator listing management view of a revenue generator interface in the systems of FIG. 1, FIG. 2, and FIG. 3, or other systems for creating separate data serving spaces for each mobile carrier in a plurality of mobile carriers. A revenue generator interface may be displayed to one of the revenue generators 110A-N, such as the revenue generator A 110A, when the revenue generator A 110A interacts with the service provider 130. The listing interface screen may allow the revenue generator A 110A to add/modify/view their listings, and their carrier listings. The screenshot 1100 may include a listing summary table 1110, a manage creative table 1140, a manage offer table 1160, an account drop-down box 840, and a revenue generator identifier 850.
The listing summary table 1110 may display all of the listings of the campaign identified by the campaign drop-down box 1112. The campaign drop-down box may allow the revenue generator A 110A to choose one of the campaigns associated with the account identified in the account drop-down box 840. The account drop-down box 840 may include all of the accounts associated with the revenue generator A 110A. The summary listing table 1110 may contain a row of data for each listing of the campaign. The data may include the keyword associated with the listing, the max bid of the listing, and the status of the listing. The revenue generator may be able to enter a new max bid for the keyword in the new max bid textbox 1122. The status of the keyword maybe modified by changing the new status drop-down box 1124. The campaign the listing is associated with may be modified by the change campaign drop-down box 1126. The listing may be deleted by clicking on the delete checkbox 1128. The revenue generator A 110A may submit the changes by clicking on the update listings button 1130. The previous listings link 1132 and the next listings link 1134 may allow the revenue generator A 110A to view other listings associated with the selected campaign.
The revenue generator A 110A may be able to click on the keyword link 1120 to change the data related to the carrier listings of the keyword. When the revenue generator A 110A clicks on a keyword link 1120, the manage creative table 1140 and the manage offer table 1160 may update to reflect the data associated with the keyword link 1120 clicked on. The carrier listings data may be modified in the manage creative table 1140 and the manage offer table 1160. The manage creative table 1140 may allow the revenue generator A 110A to modify the advertisement associated with each carrier listing for the keyword. The revenue generator A 110A may be able to view data associated with each of the carrier listings by clicking through the carrier tabs 1170.
FIG. 12 is a screenshot 1200 of an implementation of a revenue generator listing management view of a revenue generator interface in the systems of FIG. 1, FIG. 2, and FIG. 3, or other systems for creating separate data serving spaces for each mobile carrier in a plurality of mobile carriers. The screenshot 1200 demonstrates the implementation of a “WAP ad” for revenue generators 110A-N who may not have mobile sites for a particular carrier. This functionality may be demonstrated in the manage creative table 1140. The remainder of the screenshot 1200 may be similar or the same as the screenshot 1100 in FIG. 11. A revenue generator interface may be displayed to one of the revenue generators 110A-N, such as the revenue generator A 110A, when the revenue generator A 110A interacts with the service provider 130.
FIG. 13 is a screenshot 1300 of an implementation of a revenue generator editorial status view of a revenue generator interface in the systems of FIG. 1, FIG. 2, and FIG. 3, or other systems for creating separate data serving spaces for each mobile carrier in a plurality of mobile carriers. A revenue generator interface may be displayed to one of the revenue generators 110A-N, such as the revenue generator A 110A, when the revenue generator A 110A interacts with the service provider 130. The editorial status screen may allow the revenue generator A 110A to view the editorial status of their listings. The screenshot 1300 may include an editorial status table 1310, a campaign drop-down box 1320, a type drop-down box 1330, a go button 1340, an account drop-down box 840, and a revenue generator identifier 850.
FIG. 14 is a screenshot 1400 of an implementation of a revenue generator budgeting view of a revenue generator interface in the systems of FIG. 1, FIG. 2, and FIG. 3, or other systems for creating separate data serving spaces for each mobile carrier in a plurality of mobile carriers. A revenue generator interface may be displayed to one of the revenue generators 110A-N, such as the revenue generator A 110A, when the revenue generator A 110A interacts with the service provider 130. The budgeting view may allow the revenue generator A 110A to control the budgeting of their accounts across all carriers. The screenshot 1400 may include a budgeting table 1410, an enable budgeting checkbox 1412, an account budget amount 1414, a credit card drop-down box 1416, a replenish amount textbox 1418, a continue button 1420, an account drop-down box 840, and a revenue generator identifier 850.
FIG. 15 is a screenshot 1500 of an implementation of a revenue generator add money view of a revenue generator interface in the systems of FIG. 1, FIG. 2, and FIG. 3, or other systems for creating separate data serving spaces for each mobile carrier in a plurality of mobile carriers. A revenue generator interface may be displayed to one of the revenue generators 110A-N, such as the revenue generator A 110A, when the revenue generator A 110A interacts with the service provider 130. The add money view may allow the revenue generator A 110A to add money to an account. The screenshot 1500 may include a credit card dropdown box 1416, a charge amount textbox 1550, a continue button 1560, an account drop-down box 840, and a revenue generator identifier 850.
The revenue generator A 110A may enter an amount to add to an account in the charge amount textbox 1550. A credit card to charge the amount to may be selected from the credit card drop-down box 1416. The revenue generator A 110A may continue to the next screen by clicking on the continue button 1560. The revenue generator A 110A may use the money added to the account to place bids across any MNOs 115A-N associated with the account.
FIG. 16 is a screenshot 1600 of an implementation of a revenue generator add money confirmation view of a revenue generator interface in the systems of FIG. 1, FIG. 2, and FIG. 3, or other systems for creating separate data serving spaces for each mobile carrier in a plurality of mobile carriers. A revenue generator interface may be displayed to one of the revenue generators 110A-N, such as the revenue generator A 110A, when the revenue generator A 110A interacts with the service provider 130. The add money confirmation view may show the revenue generator A 110A a summary of their add money request specified in FIG. 15. The revenue generator A 110A may reach the add money confirmation screenshot 1600 by clicking on the continue button 1560 in FIG. 15.
The screenshot 1600 may include a payment summary view 1610, an account drop-down box 840, and a revenue generator identifier 850. The payment summary view 1610 may include a submit request button 1612. The revenue generator may click on the submit request button 1612 to communicate their add money request to the service provider server 240. The revenue generator A 110A may use the added money to pay for advertising across all the MNOs 115A-N. The service provider 130 may utilize an independent cross-network payment mechanism to seamlessly handle payments to all of the MNOs 115A-N.
FIG. 17 is a screenshot 1700 of an implementation of a revenue generator add payment method screen of a revenue generator interface in the systems of FIG. 1, FIG. 2, and FIG. 3, or other systems for creating separate data serving spaces for each mobile carrier in a plurality of mobile carriers. A revenue generator interface may be displayed to one of the revenue generators 110A-N, such as the revenue generator A 110A, when the revenue generator A 110A interacts with the service provider 130. The screenshot 1700 may include an add payment method table 1710, an account drop-down box 840, and a revenue generator identifier 850. The add payment method screen may allow the revenue generator A 110A to add a payment method to the account identified in the account drop-down box 840.
FIG. 18 is a screenshot 1800 of an implementation of a revenue generator update payment method screen of a revenue generator interface in the systems of FIG. 1, FIG. 2, and FIG. 3, or other systems for creating separate data serving spaces for each mobile carrier in a plurality of mobile carriers. A revenue generator interface may be displayed to one of the revenue generators 110A-N, such as the revenue generator A 110A, when the revenue generator A 110A interacts with the service provider 130. The screenshot 1800 may include an update payment method table 1810, an account drop-down box 840, and a revenue generator identifier 850. The update payment method screen may allow the revenue generator A 110A to update a payment method of the account identified in the account drop-down box 840.
FIG. 19 is a screenshot 1900 of an implementation of a revenue generator reports view of a revenue generator interface in the systems of FIG. 1, FIG. 2, and FIG. 3, or other systems for creating separate data serving spaces for each mobile carrier in a plurality of mobile carriers. A revenue generator interface may be displayed to one of the revenue generators 110A-N, such as the revenue generator A 110A, when the revenue generator A 110A interacts with the service provider 130. The screenshot 1900 may include a recent reports table 1910, a generate report table 1940, an account drop-down box 840, and a revenue generator identifier 850.
storing in a database data defining a plurality of search listings,
each respective search listing originating with a respective advertiser seeking to provide the respective search listing only to a mobile device operating on a specified mobile carrier network of a plurality of mobile carrier networks exclusive of other mobile carrier networks of the plurality of mobile networks,
each respective mobile carrier network of the plurality of mobile carrier networks employing a respective underlying technology,
the data for a respective search listing including
data defining a search keyword to be matched with a search request,
a carrier identifier field to identify the specified mobile carrier network of the plurality of mobile carrier networks to which the respective search listing may be served and
a keyword separation field to distinguish the search keyword from the carrier identifier field while storing the data defining the plurality of search listings for the plurality of mobile carrier networks in a common database;
at a processor of a server system, receiving a search request from a mobile carrier network of the plurality of mobile carrier networks, including
receiving a keyword,
receiving data identifying the respective mobile carrier network and
receiving a separator between the keyword and the data identifying the respective mobile carrier network, and
using the separator to distinguish the keyword from the data identifying the respective mobile carrier network,
the search request originating with an originating mobile device in wireless communication with the mobile carrier network;
in response to the received search request, at the processor selecting a plurality of search listings as search results from the database including
selecting search results having a carrier identifier matching the data identifying the identified mobile carrier network so that search results conforming to the respective underlying technology of the identified mobile carrier network may be provided in response to the received search request; and
at the processor, serving the plurality of search results to the identified mobile carrier network for communication to the originating mobile device.
formatting the search results using the carrier identifier field; and
serving the formatted search results to the identified mobile carrier network for communication to the originating mobile device.
formatting the search results using the carrier identifier field and information about capability of a web browser of the originating mobile device so that the respective advertiser does not have to accommodate the capability of the web browser of the originating mobile device in search listings of the respective advertiser and so that the search results appear properly on the web browser of the originating mobile device; and
4. The method of claim 1 wherein selecting the plurality of search listings as search results comprises selecting search listings matching the received keyword of the received search request.
memory configured to store a plurality of mobile data items of respective advertisers, each respective mobile data item including
data identifying a mobile carrier network of a plurality of mobile carrier networks on which the respective mobile data item may be served to a user of a mobile device in wireless communication with the mobile carrier network, each respective mobile carrier network of the plurality of mobile carrier networks employing a respective underlying technology,
a keyword to be matched with a search request received from a mobile device in wireless communication with the identified mobile carrier network, and
a keyword separator to distinguish the data identifying the mobile carrier network from the keyword to permit storage of the plurality of mobile data items for the plurality of mobile carrier networks commonly together in the memory;
an interface configured for communication of data with respective mobile carrier networks of the plurality of mobile carrier networks;
a traffic controller in data communication with the memory and the interface, the traffic controller configured to
receive through the interface data defining a keyword search request;
identify an internet protocol (IP) address in the data defining the keyword search request; and
use the IP address to identify the mobile carrier network from which the keyword search request was received;
supplement the data of the keyword search request with a data field indicating the identity of the identified mobile carrier network;
communicate the supplemented keyword search request; and
identify a mobile carrier network from which the keyword search request was received;
a mobile traffic handler configured to
receive the supplemented keyword search request from the traffic controller;
use the identity of the identified mobile carrier network to select one or more mobile data items from the memory which are related to the supplemented keyword search request and include data identifying the identified mobile carrier network so that the selected mobile data items conform to the respective underlying technology of the identified mobile carrier network when provided in response to the received keyword search request; and
serve the one or more selected mobile data items to the identified mobile carrier network for communication to a web browser of the originating mobile device.
6. The system of claim 5 wherein the mobile traffic handler is further configured to
use the identity of the identified mobile carrier network to select one or more mobile advertisements related to the keyword search request from the memory which include data identifying the identified mobile carrier network; and
serve the selected one or more mobile advertisements to the identified mobile carrier network for communication to the web browser of the originating mobile device.
7. The system of claim 5 wherein the mobile traffic handler is further configured to format the mobile data item according to underlying communication technology of the identified mobile carrier network from which the keyword search request was received.
8. The system of claim 5 wherein the traffic handler is configured to identify if the received keyword search request originated from a source other than a mobile network and forward the received search request to a web traffic handler.
US14140870 2006-03-06 2013-12-26 System for creating separate data serving spaces for each mobile carrier in a plurality of mobile carriers Active US9710828B2 (en)
US77984006 true 2006-03-06 2006-03-06
US11712276 US20070264987A1 (en) 2006-03-06 2007-02-28 System for serving advertisements over mobile devices
US11830230 US8660896B2 (en) 2006-03-06 2007-07-30 System for creating separate data serving spaces for each mobile carrier in a plurality of mobile carriers
US14140870 US9710828B2 (en) 2006-03-06 2013-12-26 System for creating separate data serving spaces for each mobile carrier in a plurality of mobile carriers
US15493931 US20170228780A1 (en) 2006-03-06 2017-04-21 System for creating separate data serving spaces for each mobile carrier in a plurality of mobile carriers
US11830230 Continuation US8660896B2 (en) 2006-03-06 2007-07-30 System for creating separate data serving spaces for each mobile carrier in a plurality of mobile carriers
US15493931 Continuation US20170228780A1 (en) 2006-03-06 2017-04-21 System for creating separate data serving spaces for each mobile carrier in a plurality of mobile carriers
US20140108147A1 true US20140108147A1 (en) 2014-04-17
US9710828B2 true US9710828B2 (en) 2017-07-18
ID=38475377
US11712276 Abandoned US20070264987A1 (en) 2006-03-06 2007-02-28 System for serving advertisements over mobile devices
US11830194 Active 2027-10-25 US7917392B2 (en) 2006-03-06 2007-07-30 System for separating mobile search traffic from web search traffic using keyword separation
US11830230 Active 2030-08-16 US8660896B2 (en) 2006-03-06 2007-07-30 System for creating separate data serving spaces for each mobile carrier in a plurality of mobile carriers
US11830344 Active 2030-03-02 US8996405B2 (en) 2006-03-06 2007-07-30 System for providing for a revenue generator to bid exclusively on mobile search traffic
US11830406 Active 2030-05-07 US8494906B2 (en) 2006-03-06 2007-07-30 System for providing for a revenue generator to bid individually on mobile search traffic originating from each mobile carrier in a plurality of mobile carriers
US11830431 Abandoned US20070288318A1 (en) 2006-03-06 2007-07-30 System for displaying the advertising performance of a revenue generator for each mobile carrier in a plurality of mobile carriers
US11830307 Abandoned US20070270188A1 (en) 2006-03-06 2007-07-30 System for dynamically generating a mobile page related to a revenue generator and formatted for display on a mobile device of a mobile carrier
US12975041 Active US8185438B2 (en) 2006-03-06 2010-12-21 System for separating mobile search traffic from web search traffic using keyword separation
US14140870 Active US9710828B2 (en) 2006-03-06 2013-12-26 System for creating separate data serving spaces for each mobile carrier in a plurality of mobile carriers
US14540884 Pending US20150073905A1 (en) 2006-03-06 2014-11-13 System for providing for a revenue generator to bid exclusively on mobile search traffic
US15493931 Pending US20170228780A1 (en) 2006-03-06 2017-04-21 System for creating separate data serving spaces for each mobile carrier in a plurality of mobile carriers
US (11) US20070264987A1 (en)
EP (1) EP1999703A4 (en)
JP (1) JP5053298B2 (en)
KR (1) KR20080099306A (en)
CN (1) CN101401118A (en)
WO (1) WO2007103094A3 (en)
US20090006396A1 (en) * 2007-06-04 2009-01-01 Advanced Mobile Solutions Worldwide, Inc. Contextual search
US8010087B2 (en) * 2007-08-20 2011-08-30 Yahoo! Inc. Mobile carrier capability
US20090089144A1 (en) * 2007-10-01 2009-04-02 Hodge Jr Rickey Edward Bid based advertising to telecommunication devices
US20100054128A1 (en) * 2008-08-29 2010-03-04 O'hern William Near Real-Time Alerting of IP Traffic Flow to Subscribers
US8068879B2 (en) * 2008-12-10 2011-11-29 Motorola Mobility, Inc. Displaying a message on a personal communication device
US8407351B2 (en) * 2009-11-25 2013-03-26 Nokia Corporation Method and apparatus for ensuring transport of user agent information
WO2012047895A3 (en) * 2010-10-05 2012-05-31 Google Inc. Search change model
US8619952B2 (en) * 2011-01-06 2013-12-31 Google Inc. Displaying phone number on the landing page based on keywords
KR101272670B1 (en) * 2011-11-28 2013-06-10 엔에이치엔(주) Apparatus, method and computer readable recording medium of distinguishing access network of a user terminal
CN103686684A (en) * 2012-09-20 2014-03-26 腾讯科技（深圳）有限公司 Offline cache method and device
US9626691B2 (en) * 2013-05-02 2017-04-18 Google Inc. Determining a bid modifier value to maximize a return on investment in a hybrid campaign
US20150348106A1 (en) * 2014-05-29 2015-12-03 Google Inc. Dynamic content item creation
JPH08172495A (en) 1994-12-20 1996-07-02 Fujitsu Ltd Service system for bearing of call charge
KR20000036964A (en) 2000-04-03 2000-07-05 김준연 User-oriented real-time custom advertisement service offering system and method
KR20010090958A (en) 2000-04-08 2001-10-22 김석준 Mobile internet service system and advertising method using that
KR20010097071A (en) 2000-04-19 2001-11-08 박기오 Advertising method using wire/wireless communication equipments
KR20010102668A (en) 2000-05-04 2001-11-16 차상균 Method and system for selectively providing advertisements using a wireless mobile terminal
KR20020000289A (en) 2000-06-22 2002-01-05 노상원 An advertising apparatus and an advertising method in accordance with an action analysis of user
US20020078101A1 (en) 2000-11-20 2002-06-20 Chang William Ho Mobile and pervasive output client device
KR20020065806A (en) 2001-02-07 2002-08-14 주식회사 언와이어드코리아 Targeting Advertisement Service System in Wireless Internet Network and Method thereof
US20020129137A1 (en) 2001-03-09 2002-09-12 International Business Machines Corporation Method and system for embedding correlated performance measurements for distributed application performance decomposition
US20020161791A1 (en) 2001-04-06 2002-10-31 Sami Hanhikoski Method and equipment for the use of a distributed database and the application utilizing the database independently from the terminal
US20030055725A1 (en) 2000-03-21 2003-03-20 Jaewon Lee Advertisement providing system by using a wireless internet and method thereof
KR20030026446A (en) 2001-09-25 2003-04-03 (주) 엘지텔레콤 The apparatus and method of mobilephone location based ad contents service
US20030154446A1 (en) 2002-01-28 2003-08-14 Constant Nicholas Robert Character-based, graphically expressive mobile messaging system
JP2004038367A (en) 2002-07-01 2004-02-05 Nec Corp Internet web page connecting system and marketing information collecting system using cellular phone with camera, and method
US6822663B2 (en) 2000-09-12 2004-11-23 Adaptview, Inc. Transform rule generator for web-based markup languages
KR20040099223A (en) 2004-11-03 2004-11-26 주식회사 에코마케팅 System, apparatus and method for providing the target advertisement based on the recency of a searching keyword and computer readable medium processing the method
JP2005251021A (en) 2004-03-05 2005-09-15 Docomo Systems Inc Information retrieval system
KR20050097155A (en) 2004-03-31 2005-10-07 엔에이치엔(주) Method for billing advertiser for keyword advertisement in internet search engine and a system thereof
JP2005300806A (en) 2004-03-17 2005-10-27 Pcphase Corp Advertisement system utilizing cellular phone corresponding to internet
KR20060004579A (en) 2004-07-08 2006-01-12 에스케이 텔레콤주식회사 Central management system for mobile advertisement service
KR20060028515A (en) 2004-09-24 2006-03-30 주식회사 팬택 Method and system for providing advertisement based on location of mobile communication terminal
US20060100928A1 (en) 2004-11-09 2006-05-11 Walczak Robert Jr System and method for providing content to a mobile communication device
KR20060062360A (en) 2004-12-03 2006-06-12 에스케이 텔레콤주식회사 Method and system for providing advertizing message service based on location of mobile communication terminal
US20060149630A1 (en) 2004-11-16 2006-07-06 Elliott Joseph F Opt-in delivery of advertisements on mobile devices
US20060172697A1 (en) 2005-02-02 2006-08-03 Gallego Fernando P Information broadcasting and support system using mobile devices
US20060184512A1 (en) 2005-02-17 2006-08-17 Microsoft Corporation Content searching and configuration of search results
US20060194572A1 (en) 2005-02-28 2006-08-31 Clearsky Mobile Media, Inc. Wireless interactive property advertising system and methods
US7136661B2 (en) 2003-07-08 2006-11-14 Lucent Technologies Inc. Weather alert notification to mobile station upon weather alert occurrence during a time period
KR20060127318A (en) 2005-06-07 2006-12-12 에스케이 텔레콤주식회사 Affiliate marketing method and system thereof
US20070042754A1 (en) 2005-07-29 2007-02-22 Bajikar Sundeep M Security parameter provisioning in an open platform using 3G security infrastructure
US20070061334A1 (en) 2005-09-14 2007-03-15 Jorey Ramer Search query address redirection on a mobile communication facility
US20070174258A1 (en) 2006-01-23 2007-07-26 Jones Scott A Targeted mobile device advertisements
US20070198339A1 (en) 2006-02-22 2007-08-23 Si Shen Targeted mobile advertisements
KR100757757B1 (en) 2006-10-26 2007-09-11 엔에이치엔(주) Method and device for information searching on wireless internet
US20070214043A1 (en) 2006-03-08 2007-09-13 Fujitsu Limited Advertisement providing service control system
US20070213069A1 (en) 2006-03-07 2007-09-13 Samsung Electronics Co., Ltd. Versatile system for adaptive subchannel allocation in wireless communications
US20080221983A1 (en) 2007-03-06 2008-09-11 Siarhei Ausiannik Network information distribution system and a method of advertising and search for supply and demand of products/goods/services in any geographical location
US7801892B2 (en) 2004-04-17 2010-09-21 Nhn Business Platform Corporation System and method for selecting search listing in an internet search engine and ordering the search listings
US1047310A (en) * 1910-04-13 1912-12-17 Star Storm Front Company Side curtain for automobiles.
WO2001089243A1 (en) * 2000-05-18 2001-11-22 Telefonaktiebolaget Lm Ericsson (Publ) Targeted messaging to end user terminal connected to a service node in a communications network
US6886016B2 (en) * 2001-09-12 2005-04-26 International Business Machines Corporation Method and system for supporting multivalue attributes in a database system
DE60206604T2 (en) * 2002-06-06 2006-07-06 Sumitomo Wiring Systems, Ltd., Yokkaichi A connector and a method for pressing a connection contact therein
US20060179630A1 (en) * 2004-05-11 2006-08-17 Davis J G Method of using multi-ceramic based liquid insulation compositions and textile products coated with multi-ceramic based liquid insulation compositions
US7458159B2 (en) * 2004-11-12 2008-12-02 Kai U.S.A., Ltd. Folding knife having a locking mechanism
US7778871B2 (en) * 2005-05-03 2010-08-17 International Business Machines Corporation Optimal sequencing of marketing events
US7298011B2 (en) * 2005-08-30 2007-11-20 Taiwan Semiconductor Manufacturing Co., Ltd. Semiconductor device with recessed L-shaped spacer and method of fabricating the same
US20070288318A1 (en) 2006-03-06 2007-12-13 Yahoo! Inc. System for displaying the advertising performance of a revenue generator for each mobile carrier in a plurality of mobile carriers
"CTIA: Smaato Introduces New Mobile Ad Solutions for Carriers: Advertising Delivery Support for Java Phones, Smartphones & Mobile Web; Launch of New Version of Soma Mobile Advertising Platform," CTIA-San Francisco Moscone Center, Booth # 108, Oct. 23-25, 2007, 2 pages. Retrieved from http://www.smaato.com/download/pressarea/Smaato-CTIA13 20071022-release.pdf.
"CTIA: Smaato Introduces New Mobile Ad Solutions for Carriers: Advertising Delivery Support for Java Phones, Smartphones & Mobile Web; Launch of New Version of Soma Mobile Advertising Platform," CTIA-San Francisco Moscone Center, Booth # 108, Oct. 23-25, 2007, 2 pages. Retrieved from http://www.smaato.com/download/pressarea/Smaato-CTIA-20071022-release.pdf.
"ESME," Wikipedia, the free encyclopedia, p. 1, http://en.wikipedia.org/wiki/ESME, last modified Dec. 20, 2006, last visited Oct. 9, 2007.
"Internet White Paper 2006," Internet White Paper, R&D, Tokyo, Japan, Jun. 21 2006, 15 pages.
"Internet White Paper 2006," Internet White Paper, R&D, Tokyo, Japan, Jun. 21, 2006, 15 pages.
"Limbo Offers Purina Pet Lodown," Adweek, pp. 1-2, http://www.adweek.com/aw/ig-interactive/article-display.jsp?vnu-content-id=1003665626, dated Oct. 31, 2007, last visited Apr. 1, 2008.
"Limbo Offers Purina Pet Lodown," Adweek, pp. 1-2, http://www.adweek.com/aw/iq-interactive/article-display.jsp?vnu-content-id=1003665626, dated Oct. 31, 2007, last visited Apr. 1, 2008.
"Mobile Search Engines White Paper," Sonera MediaLab, 2002, 13 pages.
"My First 6 Yahoo Panama 'Enhancement' Requests [Archive]", Search Engine Watch Forums, pp. 1-2, http://forums.searchenginewatch.com/archive/index.php/t-15882.html, containing posts from Jan. 18, 2007 to Jan. 25, 2007, last visited Apr. 23, 2008.
"Network Switching Subsystem," Wikipedia, the free encyclopedia, pp. 1-6, http://en.wikipedia.org/wiki/Network-Switching-Subsystem, last modified Oct. 9, 2007, last visited Oct. 9, 2007.
"Short message service center," Wikipedia, the free encyclopedia, pp. 1-2, http://en.wikipedia.org/wiki/Short-message-service-center, last modified Sep. 11, 2007, last visited Oct. 9, 2007.
"Short message service," Wikipedia, the free encyclopedia, pp. 1-5, http://en.wikipedia.org/wiki/Short-message service, last modified Oct. 9, 2007, last visited Oct. 9, 2007.
"Short message service," Wikipedia, the free encyclopedia, pp. 1-5, http://en.wikipedia.org/wiki/Short-message-service, last modified Oct. 9, 2007, last visited Oct. 9, 2007.
"Signal Transfer Point," Wikipedia, the free encyclopedia, p. 1, http://en.wikipedia.org/wiki/Signal-transfer-point, last modified Aug. 16, 2007, last visited Oct. 9, 2007.
"Smaato-Media / Developers," pp. 1-2, http://www.smaato.com/mo-mediadev.php, available at least as of Jan. 3, 2008.
"Smaato-Mobile Carriers," pp. 1-2, http://www.smaato.com/mo-carriers.php, available as least as of Jan. 3, 2008.
"Smaato-Mobile Marketing," pp. 1-2, http://www.smaato.com/mobile.php, available at least as of Jan. 3, 2008.
"Strong Partners for Effective Mobile Advertising: Adconion Media Group and Smaato Enter Strategic Partnership," San Mateo / Munich, Germany-May 9, 2007, 2 pages. Retrieved from http://www.smaato.com/download/pressarea/Smaato-AMD-20070503-release.pdf.
"CTIA: Smaato Introduces New Mobile Ad Solutions for Carriers: Advertising Delivery Support for Java Phones, Smartphones & Mobile Web; Launch of New Version of Soma Mobile Advertising Platform," CTIA—San Francisco Moscone Center, Booth # 108, Oct. 23-25, 2007, 2 pages. Retrieved from http://www.smaato.com/download/pressarea/Smaato—CTIA13 20071022—release.pdf.
"CTIA: Smaato Introduces New Mobile Ad Solutions for Carriers: Advertising Delivery Support for Java Phones, Smartphones & Mobile Web; Launch of New Version of Soma Mobile Advertising Platform," CTIA—San Francisco Moscone Center, Booth # 108, Oct. 23-25, 2007, 2 pages. Retrieved from http://www.smaato.com/download/pressarea/Smaato—CTIA—20071022—release.pdf.
"Limbo Offers Purina Pet Lodown," Adweek, pp. 1-2, http://www.adweek.com/aw/ig—interactive/article—display.jsp?vnu—content—id=1003665626, dated Oct. 31, 2007, last visited Apr. 1, 2008.
"Limbo Offers Purina Pet Lodown," Adweek, pp. 1-2, http://www.adweek.com/aw/iq—interactive/article—display.jsp?vnu—content—id=1003665626, dated Oct. 31, 2007, last visited Apr. 1, 2008.
"My First 6 Yahoo Panama ‘Enhancement’ Requests [Archive]", Search Engine Watch Forums, pp. 1-2, http://forums.searchenginewatch.com/archive/index.php/t-15882.html, containing posts from Jan. 18, 2007 to Jan. 25, 2007, last visited Apr. 23, 2008.
"Network Switching Subsystem," Wikipedia, the free encyclopedia, pp. 1-6, http://en.wikipedia.org/wiki/Network—Switching—Subsystem, last modified Oct. 9, 2007, last visited Oct. 9, 2007.
"Short message service center," Wikipedia, the free encyclopedia, pp. 1-2, http://en.wikipedia.org/wiki/Short—message—service—center, last modified Sep. 11, 2007, last visited Oct. 9, 2007.
"Short message service," Wikipedia, the free encyclopedia, pp. 1-5, http://en.wikipedia.org/wiki/Short—message service, last modified Oct. 9, 2007, last visited Oct. 9, 2007.
"Short message service," Wikipedia, the free encyclopedia, pp. 1-5, http://en.wikipedia.org/wiki/Short—message—service, last modified Oct. 9, 2007, last visited Oct. 9, 2007.
"Signal Transfer Point," Wikipedia, the free encyclopedia, p. 1, http://en.wikipedia.org/wiki/Signal—transfer—point, last modified Aug. 16, 2007, last visited Oct. 9, 2007.
"Smaato—Media / Developers," pp. 1-2, http://www.smaato.com/mo—mediadev.php, available at least as of Jan. 3, 2008.
"Smaato—Mobile Carriers," pp. 1-2, http://www.smaato.com/mo—carriers.php, available as least as of Jan. 3, 2008.
"Smaato—Mobile Marketing," pp. 1-2, http://www.smaato.com/mobile.php, available at least as of Jan. 3, 2008.
"Strong Partners for Effective Mobile Advertising: Adconion Media Group and Smaato Enter Strategic Partnership," San Mateo / Munich, Germany—May 9, 2007, 2 pages. Retrieved from http://www.smaato.com/download/pressarea/Smaato—AMD—20070503—release.pdf.
Advisory Action mailed Apr. 16, 2010 for U.S. Appl. No. 11/830,431, 3 pages.
Advisory Action mailed Aug. 10, 2010 for U.S. Appl. No. 11/776,081, 3 pages.
Advisory Action mailed Aug. 3, 2010 for U.S. Appl. No. 11/712,276, 3 pages.
Advisory Action mailed Feb. 14, 2011 for U.S. Appl. No. 11/963,154, 3 pages.
Advisory Action mailed May 27, 2010 for U.S. Appl. No. 11/830,406, 3 pages.
Advisory Action mailed May 3, 2010 for U.S. Appl. No. 11/830,344, 3 pages.
AT&T Acquires Ingenio and Their Pay-Per-Call Network, Nov. 19, 2007, retrieved from the internet on Sep. 9, 2012, 2 pages.
CrunchBase: Ingenio, Jun. 27, 2012, retrieved from the Internet on Sep. 9, 2012, 4 pages.
European Search Report dated Aug. 10, 2011 for corresponding European Application No. 7751948.6, 6 pages.
Examiner's Answer to Appeal Brief mailed Aug. 30, 2010 for U.S. Appl. No. 11/830,344, 16 pages.
Examiner's Answer to Appeal Brief mailed Aug. 4, 2010 for U.S. Appl. No. 11/830,431, 11 pages.
Examiner's Answer to Appeal Brief mailed Jan. 18, 2010 for U.S. Appl. No. 11/712,276, 16 pages.
Examiner's Answer to Appeal Brief mailed Oct. 21, 2010 for U.S. Appl. No. 11/830,406, 22 pages.
Final Office Action dated Jul. 15, 2011 for U.S. Appl. No. 12/059,460, 13 pages.
Final Office Action dated Jul. 6, 2011 for U.S. Appl. No. 12/180,782, 14 pages.
Final Office Action dated Jun. 21, 2011 for U.S. Appl. No. 12/059,421, 12 pages.
Final Office Action dated Nov. 23, 2011 for U.S. Appl. No. 12/059,325, 11 pages.
Final Office Action dated Nov. 3, 2011 for U.S. Appl. No. 12/059,386, 14 pages.
Final Office Action mailed Apr. 13, 2011 for U.S. Appl. No. 11/963,082, 13 pages.
Final Office Action mailed Apr. 29, 2010 for U.S. Appl. No. 11/776,081, 13 pages.
Final Office Action mailed Aug. 23, 2010 for U.S. Appl. No. 11/776,073, 17 pages.
Final Office Action mailed Feb. 12, 2010 for U.S. Appl. No. 11/830,431, 11 pages.
Final Office Action mailed Feb. 16, 2011 for U.S. Appl. No. 11/830,307, 17 pages.
Final Office Action mailed Feb. 17, 2011 for U.S. Appl. No. 12/026,522, 23 pages.
Final Office Action mailed Feb. 24, 2010 for U.S. Appl. No. 11/830,344, 15 pages.
Final Office Action mailed Feb. 3, 2011 for U.S. Appl. No. 11/963,029, 13 pages.
Final Office Action mailed Mar. 23, 2010 for U.S. Appl. No. 11/830,406, 14 pages.
Final Office Action mailed Mar. 5, 2010 for U.S. Appl. No. 11/712,276, 13 pages.
Final Office Action mailed Nov. 23, 2010 for U.S. Appl. No. 11/963,154, 19 pages.
Final Office Action mailed Sep. 7, 2010 for U.S. Appl. No. 12/165,175, 18 pages.
Ingenio Pay Per Call Advertising, undated, retrieved from the Internet on Sep. 9, 2012, 2 pages.
International Preliminary Report on Patentability dated Aug. 10, 2010 for corresponding International Application No. PCT/US2009/030196, 6 pages.
International Preliminary Report on Patentability dated Feb. 1, 2011 for corresponding International Application No. PCT/US2009/049227, 7 pages.
International Preliminary Report on Patentability dated Jan. 12, 2010 for corresponding International Application No. PCT/US2008/067099, 5 pages.
International Preliminary Report on Patentability dated Jun. 22, 2010 for corresponding International Application No. PCT/US2008/084163, 5 pages.
International Preliminary Report on Patentability dated Jun. 22, 2010 for corresponding International Application No. PCT/US2008/084172, 5 pages.
International Preliminary Report on Patentability dated Jun. 22, 2010 for corresponding International Application No. PCT/US2008/084338, 6 pages.
International Preliminary Report on Patentability dated Oct. 5, 2010 for corresponding International Application No. PCT/US2009/035657, 6 pages.
International Preliminary Report on Patentability dated Oct. 5, 2010 for corresponding International Application No. PCT/US2009/035662, 8 pages.
International Preliminary Report on Patentability dated Sep. 9, 2008 for corresponding International Application No. PCT/US2007/005217, 6 pages.
International Search Report and Written Opinion dated Aug. 16, 2007 for corresponding PCT Application No. PCT/US2007/005217, 9 pages.
International Search Report and Written Opinion of the International Searching Authority dated Aug. 31, 2009 for corresponding International Application No. PCT/US2009/035662, 9 pages.
International Search Report and Written Opinion of the International Searching Authority dated Feb. 17, 2010 for corresponding International Application No. PCT/US2009/049227, 8 pages.
International Search Report and Written Opinion of the International Searching Authority dated Feb. 18, 2009 for corresponding International Application No. PCT/US2008/067099, 7 pages.
International Search Report and Written Opinion of the International Searching Authority dated Jul. 27, 2009 for corresponding International Application No. PCT/US2009/030196, 7 pages.
International Search Report and Written Opinion of the International Searching Authority dated Jul. 31, 2009 for corresponding International Application No. PCT/US2009/035657, 7 pages.
International Search Report and Written Opinion of the International Searching Authority dated Jun. 24, 2009 for corresponding International Application No. PCT/US2008/084172, 7 pages.
International Search Report and Written Opinion of the International Searching Authority dated Jun. 24, 2009 for corresponding International Application No. PCT/US2008/084338, 8 pages.
International Search Report and Written Opinion of the International Searching Authority dated Jun. 30, 2009 for corresponding International Application No. PCT/US2008/084163, 7 pages.
Japanese Blog, printed from the internet at <http://blog.livedoor.jp/junpaku/archives/16328274.html on Apr. 24> 2009, 4 pages.
Japanese Blog, printed from the Internet at <http://halha1777.blog3.fc2.com/blog-entry-94.html> on Apr. 24, 2009, 12 pages.
Japanese Blog, printed from the internet at <http://halhal777.blog3.fc2.com/blog-entry-94.html> on Apr. 24, 2009, 12 pages.
Japanese Blog, printed from the Internet at <http://k.hatena.ne.jp/keywordblog/jmobi> on Apr. 24, 2009, 3 pages.
Japanese Blog, printed from the internet at <http://netanetaneta.seesaa.net/> on Apr. 24, 2009, 10 pages.
Japanese Blog, printed from the internet at <http://vanillachips.net/archives/20050309-2336.php> on Apr. 24, 2009, 4 pages.
Japanese Blog, printed from the internet at <http://vanillachips.net/archives/20050309—2336.php> on Apr. 24, 2009, 4 pages.
Japanese Blog, printed from the internet at <http://www.cottonwool.jp/labo/jmobi.html> on Apr. 24, 2009, 3 pages.
Japanese Blog, printed from the internet at <http://www.googleadsense.seesaa.net/article/2238902.html> on Apr. 24, 2009, 3 pages.
Japanese Blog, printed from the internet at <http://www.rc-seo.jp/000027.html> on Apr. 24, 2009, 2 pages.
Notice of Allowance mailed Feb. 17, 2010 for U.S. Appl. No. 11/830,194, 12 pages.
Notice of Allowance mailed Oct. 21, 2010 for U.S. Appl. No. 11/830,194, 9 pages.
Office Action dated Aug. 15, 2011 for U.S. Appl. No. 12/059,325, 21 pages.
Office Action dated Aug. 30, 2011 for corresponding Korean Application No. 10-2010-7016222, 7 pages.
Office Action dated Aug. 8, 2011 for corresponding Chinese Application No. 200880122228.0, 12 pages.
Office Action dated Jan. 10, 2011 for corresponding Chinese Application No. 200780008231.5, 10 pages.
Office Action dated Jul. 13, 2011 for corresponding Chinese Application No. 200980103451.5, 11 pages.
Office Action dated Jul. 28, 2010 for corresponding Korean Application No. 10-2008-7021632, 11 pages.
Office Action dated Jun. 28, 2011 for U.S. Appl. No. 12/059,386, 23 pages.
Office Action dated May 17, 2011 for corresponding Australian Application No. 2009232311.0, 3 pages.
Office Action dated Oct. 3, 2011 for corresponding Japanese Application No. 2008-558303, 8 pages.
Office Action dated Sep. 16, 2011 for corresponding Korean Application No. 10-2010-7017411, 5 pages.
Office Action dated Sep. 23, 2011 for U.S. Appl. No. 11/963,154, 22 pages.
Office Action dated Sep. 28, 2011 for U.S. Appl. No. 12/975,041, 16 pages.
Office Action mailed Apr. 30, 2010 for U.S. Appl. No. 11/776,073, 14 pages.
Office Action mailed Aug. 20, 2010 for U.S. Appl. No. 12/026,522, 18 pages.
Office Action mailed Dec. 10, 2010 for U.S. Appl. No. 11/963,082, 13 pages.
Office Action mailed Dec. 20, 2010 for U.S. Appl. No. 12/059,460, 10 pages.
Office Action mailed Dec. 22, 2009 for U.S. Appl. No. 11/776,081, 9 pages.
Office Action mailed Dec. 29, 2009 for U.S. Appl. No. 11/776,073, 13 pages.
Office Action mailed Feb. 16, 2011 for U.S. Appl. No. 12/059,421, 12 pages.
Office Action mailed Jan. 21, 2011 for U.S. Appl. No. 12/180,782, 11 pages.
Office Action mailed Jun. 10, 2010 for U.S. Appl. No. 11/963,154, 11 pages.
Office Action mailed May 4, 2010 for U.S. Appl. No. 12/165,175, 21 pages.
Office Action mailed Nov. 3, 2010 for U.S. Appl. No. 11/830,307, 17 pages.
Office Action mailed Oct. 20, 2010 for U.S. Appl. No. 11/963,029, 14 pages.
Office Action mailed Sep. 10, 2009 for U.S. Appl. No. 11/712,276, 12 pages.
Office Action mailed Sep. 11, 2009 for U.S. Appl. No. 11/830,344, 15 pages.
Office Action mailed Sep. 14, 2009 for U.S. Appl. No. 11/830,406, 15 pages.
Office Action mailed Sep. 4, 2009 for U.S. Appl. No. 11/830,194, 14 pages.
Office Action mailed Sep. 9, 2009 for U.S. Appl. No. 11/830,431, 11 pages.
STIC Search Report EIC 3600 dated Feb. 5, 2010.
STIC Search Report EIC 3600 dated Feb. 5, 2010; cited by Examiner on Feb. 17, 2010 for U.S. Appl. No. 11/830,194, 86 pages.
Supplemental Final Office Action mailed Apr. 30, 2010 for U.S. Appl. No. 11/712,276, 15 pages.
JP2009529728A (en) 2009-08-20 application
US20070270188A1 (en) 2007-11-22 application
EP1999703A4 (en) 2011-09-21 application
US8185438B2 (en) 2012-05-22 grant
WO2007103094A2 (en) 2007-09-13 application
EP1999703A2 (en) 2008-12-10 application
US7917392B2 (en) 2011-03-29 grant
US8494906B2 (en) 2013-07-23 grant
KR20080099306A (en) 2008-11-12 application
US20070287458A1 (en) 2007-12-13 application
US20070288318A1 (en) 2007-12-13 application
US8660896B2 (en) 2014-02-25 grant
WO2007103094A3 (en) 2007-10-25 application
US8996405B2 (en) 2015-03-31 grant
US20110093332A1 (en) 2011-04-21 application
CN101401118A (en) 2009-04-01 application
US20170228780A1 (en) 2017-08-10 application
JP5053298B2 (en) 2012-10-17 grant
US20070270130A1 (en) 2007-11-22 application
US20150073905A1 (en) 2015-03-12 application
US20070264987A1 (en) 2007-11-15 application
US20070266014A1 (en) 2007-11-15 application
US20070288317A1 (en) 2007-12-13 application
US20140108147A1 (en) 2014-04-17 application
US20080153520A1 (en) 2008-06-26 Targeted short messaging service advertisements
US20070239452A1 (en) 2007-10-11 Targeting of buzz advertising information