Patent Grant
11948171
This disclosure relates generally to delivery of content, and more particularly to delivery of content within reserved geographic areas.
Advertisements can be delivered to various devices, including mobile devices, within communications range of areas transmitters or other information providers. For example, advertisements can be delivered to cellular phones within range of a particular cellular phone provider's network area. Furthermore, advertisements can be delivered using digital billboards, or via the Internet, based on user interactions and preferences.
When delivering advertisements and other content to some mobile devices, currently available technologies can broadcast the content to all devices equipped to receive them. In some cases, advertisements are broadcast to any mobile device within a city, or a similar area. When delivering non-broadcast content, for example via the Internet, it is common to deliver the content in response to a request, received from the receiving device. In some cases, push technology can be used to deliver content to multiple users concurrently.
In each of these cases, a mobile device can usually receive content from multiple different content providers. Current technologies are, therefore, less than perfect.
Various embodiments disclosed herein include registering an application program for use with a content delivery platform, establishing multiple perimeters defining respective geographic areas, and maintaining records associating sponsors with particular geographic areas. The content delivery platform can receive a request from a registered application program for content to be displayed on a mobile device, and the request can be used to determine a target location. In some embodiments, a sponsor is selected based on a relationship between the target location and one or more reserved geographic areas. Content is then provided to the application program.
In some embodiments, the content delivery platform can record a request identifier associated with a received request, and provide the request identifier to the mobile device to assist in tracking future actions relating to the request for content. The content delivery platform can also receive information related to user interaction with the provided content, including the request identifier, and provide additional content in response to the received information.
Content can be delivered to a mobile device running a registered application if a target location is at least partially within a predetermined radial distance of a geographical area associated with a sponsor; if the mobile device is not located within the predetermined radial distance, the radial distance can be increased. In some embodiments, content is delivered if the target location, e.g. the location of the mobile device or another location of interest, is located entirely within a geographic area exclusively reserved by a particular sponsor. In some embodiments, the content delivery platform can select from among several sponsors in deciding which content to deliver to a mobile device.
In at least one embodiment, the content delivery system reserves exclusive interests in geographic areas for particular sponsors based on the sponsors' requests, and store a record of that interest. In some embodiments, the content delivery system receives, from a sponsor, content to be delivered to mobile devices based on a target location being positioned within particular geographic areas. The content delivery system can also reserve an interest in geographic areas that remain unreserved by other sponsors. Furthermore, some embodiments include time based restrictions.
Various embodiments can be implemented as a system that includes memory, a communications interface, and a processor that cooperate to store and execute a program of instructions implementing various methods and techniques described herein. Furthermore, some embodiments can be implemented as a computer readable medium tangibly embodying a program of instructions.
Various embodiments of the present disclosure provide for delivering content, such as advertising, to registered applications being run on any of various mobile electronic devices configured to be readily moved, carried, or otherwise transported between different various geographic areas defined by perimeters. Sponsors can reserve an exclusive interest, or in some embodiments a semi-exclusive interest, in a geographic area, so that other sponsors' advertisements are excluded from being broadcast or otherwise provided to a registered program being executed on a mobile device located within a reserved geographic area.
Referring first to
In some embodiments, a registered application program is provided to mobile devices by developer platform 108, content delivery platform 112, one of sponsor A 121, sponsor C 123, or sponsor B 125, or by another desired delivery mechanism. In some embodiments, registering the application program with content delivery platform 112 allows developer 108 to receive revenue from sponsor A 121, sponsor C 123, or sponsor B 125 for content displayed on a mobile device located within, or in proximity to, a geographical area reserved by one or more of the sponsors.
Sponsor A 121, sponsor C 123, or sponsor B 125 can reserve an exclusive interest in a particular geographic area by sending a request to content delivery platform 112. In some embodiments, the request can be for exclusive delivery of content to mobile devices running any registered application within given geographic areas, or for content to be delivered to particular registered applications based on a target location. The request can also include time limitations, limitations based on the length of time a mobile device remains within a given geographic area, or other desired limitations. Furthermore, the reserved interest can be either completely exclusive, or semi-exclusive.
System 100 can include a network, for example Internet 131, through which content delivery platform 112, can communicate to other networked devices; and communication towers 144, which can include AM or FM broadcast towers, mobile telephone stations, or other suitable communication infrastructure, including satellites (not illustrated) that might be useful in providing content based on a target location. Content delivery platform 112 can use this communication infrastructure to communicate with various computing devices, including portable computer 179, which may include laptop computers, desktop computers, palmtop computers, tablet computers, digital video recorders (DVRs), television set-top boxes, or any of various general or dedicated purpose computers that can be carried or transported; wireless device 177, which can include personal digital assistants (PDAs), cellular telephones, personal communication system (PCS) devices, music players, video players, gaming consoles, or portable televisions; or any of various devices that may be included in, or carried by, motor vehicles 171, 173, or 175, including navigation systems, satellite radios, or the like. It should be noted that the term “mobile device” can include all computing devices as listed above that can communicate with content delivery platform 112, that the above listing of devices is not exhaustive, and that a device that qualifies as one type of device may also be considered to be of another type. For example, a mobile phone may also be a general purpose computing device, a radio, a television, and a navigation system.
Still referring to
Portable computer 179 can be connected to Internet 131 via a hardwired network connection, a Wi-Fi connection or other suitable communication connection. In some embodiments, if portable computer 179 is running a registered program application, the user of portable computer 179 will receive content related exclusively to sponsor A as long as he is within sponsor A's reserved geographic area 143. In some embodiments, the driver of first motor vehicle 171 and the user of laptop 179 will still be able to receive advertisements from other sponsors through devices not running a program that has been registered on content delivery platform 112, or through non-registered programs running on the same device.
In some embodiments, the location of mobile devices, or another target location, can be determined using various suitable methods. For example, a mobile device running a registered application can provide location information to content delivery platform 112 in the form of latitude or longitude coordinates, raw or processed GPS data, or other location information received and recorded by either the device itself or another device. In some embodiments, a target location, e.g. the location of a mobile device, can be determined based on signals received from cellular transmission towers, satellites, or methods such as triangulation or dead reckoning, or by IP address. Content delivery platform 112 can receive the location of mobile devices from a third source, for example a location provider, a cellular telephone network provider, or a third party tracking source, rather than from the mobile device itself. Thus, the location of a mobile device can be received from the mobile device, determined by content delivery platform 112, received from a third-party source, or determined based on a combination of these or other methods.
Sponsor A's reserved geographic area 143 illustrates an embodiment in which a perimeter can be defined by streets, county boundaries, city boundaries, landmarks, or other features commonly found on maps. In contrast, sponsor B's reserved geographic area 145 can be an ellipse, circle, oval, or other geometric shape that can be determined, at least in part, based on a radius.
In this example, both second motor vehicle 173 and wireless device 177 are located within sponsor B's reserved geographic area 145. The driver of second motor vehicle 173 and the user of wireless device 177 can receive advertisements or other content via towers 144. For example, if the driver of second motor vehicle 173 is operating a navigation device executing an application program registered by developer 108, advertisements and other content received on the navigation device can be determined based on the location within sponsor B's reserved geographic area 145. Likewise, the user of wireless device 177 will receive advertisements related to sponsor B from within a registered application. In some embodiments, content delivery platform 112 can prevent content from sponsor A 121 and sponsor C 123 from being delivered to a mobile device carried by second motor vehicle 173 and wireless device 177, because both motor vehicle 173 and wireless device 177 are located in sponsor B's reserved geographic area 145.
Turning next to sponsor A and sponsor C's reserved geographic area 147, note that the perimeter is a square, rectangle or similarly shaped. In some embodiments, the perimeter may be defined entirely by longitude and latitude lines and/or coordinates that constitute an area. In other embodiments, sponsor A and sponsor C's reserved geographic area 147 can be partially bounded by a longitude or latitude line, a road, river, railway, county, state, parish, city, locality, or other desired boundary. In some embodiments, the perimeter of a sponsor A and sponsor C's reserved geographic area 147 can be defined by a combination of longitude or latitude lines, with one or more remaining boundaries defined based on radius or diameter.
Because third motor vehicle 175 is within sponsor A and sponsor C's reserved geographic area 147, a mobile device carried by third motor vehicle 175 can receive advertising content from either or both sponsor A and sponsor C. In some embodiments, the interest in sponsor A and sponsor C's reserved geographic area 147 can be equally divided between sponsor A 121 and sponsor C 123, while in other embodiments one of sponsor A 121 and sponsor C 123 can have an interest superior to that of the other. In some embodiments, content delivery platform 112 can deliver advertisements or other content related to Sponsor A at selected times, while content related to Sponsor C is delivered at other times. Additionally, content related to sponsor A may be delivered via a first registered application, while content related to sponsor C can be delivered via a second registered application. Thus, sponsors can advertise or provide other content to members of particular demographics based on a type of application a particular demographic is more likely to use.
Referring next to
In response to receiving the target location information 216 from object of interest 233, registered application 231 can send a request 213 to content delivery platform 212. The request can include, but is not limited to, information indicating the location of object of interest 233, a request for content, information indicating the location of registered application 231, information indicating the identity of the registered application 231, and a previously received request identifier.
Content delivery platform 212 can receive and process request 213 to identify the location of registered application 231 and the location of object of interest 233. In some embodiments, both locations need not be identified. Furthermore, in some embodiments the specific location need not be identified, as long as a determination that object of interest 233 is located within a given proximity of second sponsor's reserved area 205, or that registered application 231 is located within first sponsor's reserved area 207.
Content delivery platform 212 can provide registered application information 217 to second sponsor 225 to allow second sponsor 225 to deliver second sponsor's content 214 to registered application 231. The registered application information 217 can be an application identifier, a request identifier, a target location, a communications address, or other information that can be utilized by second sponsor 225. In some embodiments, application information 217 need not be provided to second sponsor 225, but instead can be processed internally by content delivery platform 212, and a determination can be made for second sponsor's content 214 to be delivered directly to application 231 from content delivery platform 212, or a third party (not illustrated).
Note that in the illustrated embodiment, despite the fact that registered application 231 is located within first sponsor's reserved area 207, the information delivered to registered application 231 can be content related exclusively to second sponsor's reserved area 205, in which object of interest 233 is located. This is because, in the illustrated embodiment, the target location is the location of object of interest 233, rather than the location of a mobile device executing registered application 231.
In some embodiments, information from the first sponsor can also be delivered to registered application 231, because the locations of the device running registered application 231 and object of interest 233 are both considered target locations. Furthermore, in some embodiments content need not be delivered directly from second sponsor 225, but instead can be provided by content delivery platform 212, or a third party (not illustrated).
Referring next to
As illustrated by
As further illustrated by
In some embodiments, target location G 392 can be a mobile device running two or more registered applications, and can receive content related to sponsor A, because the mobile device lies within triangular area 320. But, target location G 392 also lies within pentagonal area 371, and the mobile device can therefore receive content associated with sponsor G. In some embodiments, content related to sponsor A can be delivered via one of the registered applications, while another registered application receives and displays content related to sponsor G. In other embodiments, one of sponsor A or sponsor G can have a superior interest to the other, and a preference can be given to that sponsor's content for delivery. For example, sponsor G may have a superior interest in pentagonal area 371, which also forms part of triangular area 320. In such a case, if content related to sponsor G is available for delivery to the application on the mobile device with target location G 392, that content will be delivered in preference to content related to sponsor A. However, if there is no high priority content related to sponsor G to be delivered, content related to sponsor A may be provided in its stead. Various other priority and time sharing mechanisms and methods can be implemented according to the teachings set forth herein. Note that in some embodiments, multiple registered applications are not required to implement priority and time sharing mechanisms.
In some instances, a mobile device can have target locations, such as target location D 324 or target location E 356, located outside of areas reserved by sponsors. In such a case, a check can be made to determine if either target location D 340 or target location E 356 are located within a given proximity of a sponsor-reserved area such as triangular area 320 or octagonal area 330. So, for example, a check can be made to determine whether any reserved areas lie within a given radius of target location D 340, defining a search area 341, or within a given radius of target location E 356, defining a search area 351. In some embodiments, if no sponsor reserved area intersects an area within an initially small radius, further checks can be performed by incrementally increasing the radius. So, for example, after a first check finds no advertiser reserved areas within search areas 341 or 351, the search areas can be increased to encompass areas 343 and 353, respectively.
In the illustrated example, there is no reserved area intersecting search area 353, but sponsor H 357 has a physical address within area 353. In some embodiments, once it is determined that a registered sponsor has a physical address location within a search radius, but there are no sponsor reserved geographic areas in proximity to or encompassing a target location, an advertisement or other content can be delivered to a mobile device, such as the device with target location 356.
Another situation arises when there are no sponsor reserved geographic areas intersecting a search area, but there are multiple sponsor physical locations within a given radius. Consider area 343, which contains sponsor E's location 349, and sponsor F's location 347. Because neither sponsor E nor sponsor F has established a reserved area that intersects with search area 343, a random choice can be made between these two sponsors to determine which sponsor's content to provide to the registered application on the device with target location D 340. In other embodiments, preference may be given to one of sponsor E's location 349 and sponsor F's location 347 based on each physical locations' proximity to target location D 340, based on a travel time between the device with target location D 340 and the sponsors' locations, or based on some other desired parameter. In further embodiments, if no sponsor's reserved geographic area intersects any portion of area 343, no content is sent to mobile device D with target location 340, despite the fact that location sponsor E's location 359, and sponsor F's location 347 are both within the perimeter defining search area 343.
In some embodiments, the search radius can continue to be expanded until a search area 345 intersects with a sponsor reserved geographic area. In the illustrated embodiment, search area 345 intersects sponsor A's reserved triangular area 320. Note that sponsor G2's physical location 328 is also located within search area 345. In some embodiments, content from either sponsor A or sponsor G can be selected using any of various processes, because target location D 340 is not located entirely within triangular area 320. In some embodiments, however, because the expanded search area 345 encompasses even a portion of sponsor A's reserved triangular area 320, content related to sponsor G will be excluded, and content related to sponsor A will be exclusively provided to mobile device with target location D 340. In some embodiments, because target location D 340 is not located within sponsor A's reserved triangular area 320, content related to sponsor A will be excluded, and content related to sponsor G will be exclusively provided to mobile device with target location D 340.
Additional techniques accounting for the proximity of exclusively reserved advertising areas and sponsor's physical locations with respect to mobile device locations can be implemented according to the teaching set forth herein. For example, in some embodiments, sponsors may obtain an interest in all otherwise unreserved geographic areas. For example, a content delivery system can deliver content from a “default” sponsor, if it is determined that no other content is to be delivered to a mobile device.
Referring next to
The perimeters established can be based on map features, such as streets, rivers, landmarks, or any of the other various map features. The perimeters can also be defined by latitude and longitude, or various geometric constructs having a given relative position to either a point location, a map location, a physical address, or otherwise. Some embodiments allow for establishing perimeters defining areas based on a combination of the various types of constructs. So, for example, latitude, longitude and map features may be used to establish the reserved area, or a combination of coordinates and geometric constructs can be used in conjunction with other suitable boundary identifiers to establish an area that may be reserved specifically for content related to a particular advertiser or sponsor.
In some embodiments, the perimeters may be generated interactively, using sponsor established perimeter definitions, or other unique sponsor requests. Some embodiments employ pre-defined areas, or allow selection of areas based on predetermined factors, and present sponsors a choice from among previously established options.
As illustrated by block 407, a sponsor's request for a selected area is received. As illustrated by block 409, a check is made to determine if the selected area, or a portion of the selected area, has already been reserved by another sponsor. If the area selected by the sponsor is already owned or is otherwise unavailable, method 400 may return to block 407, and the sponsor can choose another area. In some embodiments, overlap of various sponsor areas may be allowed based on type of business, type of application used to deliver the content, or otherwise.
As illustrated by block 411, if an area selected for exclusive or semi-exclusive content delivery is available, the selected geographic area can be reserved for the sponsor. And as illustrated by block 413, the sponsor can be notified that an interest in the geographic area has been reserved for him.
A sponsor can provide content for delivery to mobile devices having target locations contained within its reserved area, as illustrated by block 415. This content can include advertisements, still image content, animated content, video content, audio content, alphanumeric identifiers, or other content suitable for delivery to mobile devices via registered applications. As illustrated by block 417, the content received from the sponsor can be stored for later delivery to registered applications running on mobile devices having target locations that exist within the sponsor's reserved area, which such target locations may include, but are not limited to, when the mobile device or target location physically enters or remains within the sponsor's reserved area for a desired length of time. In some embodiments, content can be delivered to a mobile device by the sponsor or another party in response to a notification that the mobile device or target location has entered or is contained within the sponsor's reserved area. Method 400 ends, as illustrated at block 419.
Referring next to
As illustrated by block 507 a determination is made as to whether the application sending the request for content has a target location that is located within a sponsor's reserved geographic area. In some embodiments, the target location may be the location of the device. In some embodiments, the target location may be a location other than the location of the device, as illustrated in
In some embodiments, content from one sponsor can be selected for delivery in a particular geographic area in specific situations, even though a different sponsor has generally reserved that same geographic area. For example, content from a first sponsor can be delivered during a football game to mobile devices located in a geographic area normally reserved by a second sponsor, effectively trumping content related to the second sponsor that would otherwise be delivered. In some embodiments, additional criteria can be applied to determine which sponsors' content will be provided to mobile devices in a particular geographic area.
As illustrated by block 511, selected content can be provided to an application for display on a mobile device. In at least one embodiment, different content from the same sponsor can be provided to the same device for display within different applications, or the same content from the same sponsor can be displayed for all mobile devices running all registered applications that have target locations within the delivery area for the content. For example, a first program run on a mobile device may display a first advertisement within that program while a second program running on the same device may display a second advertisement, which is different from the first advertisement. In some embodiments in which an interest in a particular geographic area is shared between multiple sponsors, a primary sponsor's content can be exclusively displayed via a first registered application running on a particular mobile device, while content from other sponsors can be displayed via a second and subsequent applications running on the same mobile device.
As illustrated by block 513, if the target location is not within a sponsor's reserved area, a determination can be made regarding whether at least one sponsor's presence is within a first predetermined radius of the target location. In some embodiments, a determination is made regarding whether a sponsor's physical location is within a predetermined radius of the target location. In some embodiments, a determination is made regarding whether a sponsor's geographic area, or a portion of a sponsor's geographic area, is contained within a predetermined radius of the target location. If at least one sponsor's presence is within a predetermined radius of the target location, a sponsor is chosen from a random or pseudo-random process, as illustrated by block 519. Content is then selected for delivery, as illustrated by block 509. As illustrated by block 515, if a sponsor's presence is not within a predetermined radius of the target location, the search radius can be increased. As illustrated by block 517, a check can be made to determine whether any more increases should be made. In some embodiments, the search radius can continue to be increased incrementally, in a logarithmic manner, or otherwise, until at least a portion of a sponsor's reserved area intersects the search area defined by the search radius. In some embodiments, the search radius can be increased a predetermined number of times, or can be limited based on system resources, time constraints, or other desired parameters. The processes illustrated by blocks 513, 515, and 517 can be repeated until a positive indication is produced by the process at block 517.
As illustrated by block 519, content from a randomly or pseudo-randomly selected sponsor can be delivered to a mobile device if the target location is not within a desired proximity to a sponsor's reserved area. In some embodiments, rather than delivering content randomly, content selections can be made based on desired criteria. Content related to a sponsor that reserved all otherwise unallocated space can be delivered to a mobile device executing a registered application. In some such embodiments, if any particular geographic areas have not yet been reserved, or if any device requesting content does not have a target location contained within a reserved geographic area, the default sponsor's content can be delivered to the mobile device. Method 500 ends as illustrated by block 521.
Preferring next to
In some embodiments, key verification can be performed by an entity other than the content providing platform. As illustrated by block 627, if a verification check on the key fails, no content is provided to the requesting application, and the method 600 ends.
As illustrated by block 609, if the key is validated a session can be initiated between the application on the mobile device, and the content delivery platform. As illustrated by block 611 in at least one embodiment, the application running on the mobile device sends the mobile device's location, or another target location, to the content delivery platform. However, in some embodiments the actual location is not sent by the device, but may be provided to the content delivery platform from another source. Furthermore, the content delivery platform, or a subsystem of a communications system employed by the content delivery platform, can determine the location of the mobile device based on raw, partially, or completely processed information received from the mobile device or from another source. For example, the mobile device can forward information associated with a target location to the content delivery platform, or the content delivery server can obtain location information from a third party application or device, from a home location register (HLR), from a visiting location register (VLR), from raw, differential, processed or semi-processed GPS data, from power signals used in code-division multiple access (CDMA) or other wireless communications systems, or otherwise.
As illustrated by block 613, the content delivery platform records the request from the registered application in a request identifier in the platform database, or some other suitable storage location. The request identifier can be used in some embodiments to track further interaction with the registered application, or to deliver additional content to a requesting mobile device. Thus, in some embodiments, a mobile device or other target location that is only temporarily located within a particular sponsor's reserved geographic area may continue to receive information from that sponsor after the mobile device, or the target location, exits the sponsor's reserved area. In other embodiments, content related to a sponsor is discontinued in response to a mobile device exiting, or the target location losing focus within, the sponsor's reserved area.
As illustrated by block 615, the content delivery platform can deliver the request identifier to the requesting application along with the requested content. As illustrated by block 617, a user of the mobile device can interact with the provided content using any of various methods such as pressing a button, selecting a user selectable object on a graphical user interface, or otherwise. The application on the mobile device can send an indication of the interaction to the content delivery platform via the same communication channel used to send the request, or via a different communications channel.
As illustrated by block 619, a registered application running on a mobile device can send an additional information request to the platform using the previously assigned request identifier. In some embodiments, using the previously assigned platform request identifier permits tracking of a series of interactions between a particular application and the content delivery platform. Furthermore, using the request identifier can allow individualized content to be delivered to different registered applications which may or may not be running on the same mobile device.
As illustrated by block 621, a determination is made regarding whether a request identifier sent in conjunction with a request for further information is maintained in the platform database or other suitable storage. As illustrated by block 623, if the request identifier is contained in the database or other storage area, the content delivery platform can update a request identifier record as being complete. And as illustrated by block 625, the content delivery platform can deliver more content to the requesting application. As illustrated by block 627, method 600 can proceed to end after delivering the additional content.
The methods and processes discussed previously, as well as other embodiments, may be implemented in a processing system executing a set of instructions stored in memory, or on a removable computer readable medium. An example of a system according to some embodiments is illustrated in
Processing system 700 includes random access memory (RAM) 720; read-only memory (ROM) 715, wherein the ROM 715 could also be erasable programmable read-only memory (EPROM) or electrically erasable programmable read-only memory (EEPROM); and input/output (I/O) adapter 725, for connecting peripheral devices such as disk units 730, optical drive 736, or tape drive 737 to system bus 710; a user interface adapter 740 for connecting keyboard 745, mouse 750, speaker 755, microphone 760, or other user interface devices to system bus 710; communications adapter 765 for connecting processing system 700 to an information network such as the Internet or any of various local area networks, wide area networks, telephone networks, or the like; and display adapter 770 for connecting system bus 710 to a display device such as monitor 775. Mouse 750 has a series of buttons 780, 785 and may be used to control a cursor shown on monitor 775.
It will be understood that processing system 700 may include other suitable data processing systems without departing from the scope of the present disclosure. For example, processing system 700 may include bulk storage and cache memories, which provide temporary storage of at least some program code in order to reduce the number of times code must be retrieved from bulk storage during execution.
Various disclosed embodiments can be implemented in hardware, software, or a combination containing both hardware and software elements. In one or more embodiments, the invention is implemented in software, which includes but is not limited to firmware, resident software, microcode, etc. Some embodiments may be realized as a computer program product, and may be implemented as a computer-usable or computer-readable medium embodying program code for use by, or in connection with, a computer, a processor, or other suitable instruction execution system.
For the purposes of this description, a computer-usable or computer readable medium can be any apparatus that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. By way of example, and not limitation, computer readable media may comprise any of various types of computer storage media, including volatile and non-volatile, removable and non-removable media implemented in any suitable method or technology for storage of information such as computer readable instructions, data structures, program modules, or other data. Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by a computer. Data structures and transmission of data (including wireless transmission) particular to aspects of the disclosure are also encompassed within the scope of the disclosure.
Various embodiments have been described for delivering content related to a commercial media program. Other variations and modifications of the embodiments disclosed may be made based on the description provided, without departing from the scope of the invention as set forth in the following claims.
This continuation patent application claims priority from U.S. Non-provisional patent application having Ser. No. 17/182,809, filed 23 Feb. 2021, entitled “EXCLUSIVE DELIVERY OF CONTENT WITHIN GEOGRAPHIC AREAS”, which claims priority from U.S. Non-provisional patent application having Ser. No. 16/019,285, filed 26 Jun. 2018, entitled “EXCLUSIVE DELIVERY OF CONTENT WITHIN GEOGRAPHIC AREAS”, now U.S. Pat. No. 10,984,447 issued on 20 Apr. 2021, which claims priority from U.S. Non-provisional patent application having Ser. No. 15/694,786, filed 2 Sep. 2017, entitled “EXCLUSIVE DELIVERY OF CONTENT WITHIN GEOGRAPHIC AREAS”, now U.S. Pat. No. 10,049,387 issued on 14 Aug. 2018, which claims priority from U.S. Non-provisional patent application having Ser. No. 15/009,961, filed 29 Jan. 2016, entitled “EXCLUSIVE DELIVERY OF CONTENT WITHIN GEOGRAPHIC AREAS”, now U.S. Pat. No. 9,779,418 issued on 3 Oct. 2017, which claims priority from U.S. Non-provisional patent application having Ser. No. 14/608,285, filed 29 Jan. 2015, entitled “EXCLUSIVE DELIVERY OF CONTENT WITHIN GEOGRAPHIC AREAS”, now U.S. Pat. No. 9,286,625 issued on 15 Mar. 2016, which claims priority from U.S. Non-provisional patent application having Ser. No. 13/856,392, filed 3 Apr. 2013, entitled “EXCLUSIVE DELIVERY OF CONTENT WITHIN GEOGRAPHIC AREAS”, now U.S. Pat. No. 8,977,247 issued on 10 Mar. 2015, which claims priority from U.S. Non-provisional patent application having Ser. No. 12/434,094, filed 1 May 2009, entitled “EXCLUSIVE DELIVERY OF CONTENT WITHIN GEOGRAPHIC AREAS”, now U.S. Pat. No. 8,433,296 issued on 30 Apr. 2013, all having a common applicant herewith and being incorporated herein in their entirety by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 6418311 | Chmaytelli et al. | Jul 2002 | B1 |
| 6449498 | Kirbas et al. | Sep 2002 | B1 |
| 6542729 | Chmaytelli et al. | Apr 2003 | B1 |
| 6542732 | Khazaka et al. | Apr 2003 | B1 |
| 6701144 | Kirbas et al. | Mar 2004 | B2 |
| 6721578 | Minear et al. | Apr 2004 | B2 |
| 6753842 | Williams et al. | Jun 2004 | B1 |
| 6782369 | Carrott | Aug 2004 | B1 |
| 6792244 | Ross et al. | Sep 2004 | B2 |
| 6810323 | Bullock et al. | Oct 2004 | B1 |
| 6847888 | Fox et al. | Jan 2005 | B2 |
| 6867733 | Sandhu et al. | Mar 2005 | B2 |
| 6947772 | Minear et al. | Sep 2005 | B2 |
| 6996394 | Minear et al. | Feb 2006 | B2 |
| 7009556 | Stewart | Mar 2006 | B2 |
| 7039398 | Chmaytelli et al. | May 2006 | B2 |
| 7054649 | Yamazaki et al. | May 2006 | B2 |
| 7065388 | Minear et al. | Jun 2006 | B2 |
| 7080402 | Bates et al. | Jul 2006 | B2 |
| 7089264 | Guido et al. | Aug 2006 | B1 |
| 7092964 | Dougherty et al. | Aug 2006 | B1 |
| 7096004 | Minear et al. | Aug 2006 | B2 |
| 7096117 | Gale et al. | Aug 2006 | B1 |
| 7099663 | Lundblade et al. | Aug 2006 | B2 |
| 7103368 | Teshima | Sep 2006 | B2 |
| 7113772 | Chmaytelli et al. | Sep 2006 | B2 |
| 7124370 | Fish | Oct 2006 | B2 |
| 7133685 | Hose et al. | Nov 2006 | B2 |
| 7164986 | Humphries et al. | Jan 2007 | B2 |
| 7200673 | Augart | Apr 2007 | B1 |
| 7203967 | Chmaytelli et al. | Apr 2007 | B2 |
| 7207802 | Wilson | Apr 2007 | B2 |
| 7219145 | Chmaytelli et al. | May 2007 | B2 |
| 7219303 | Fish | May 2007 | B2 |
| 7263351 | Ross et al. | Aug 2007 | B2 |
| 7324815 | Ross et al. | Jan 2008 | B2 |
| 7457628 | Blumberg et al. | Nov 2008 | B2 |
| 7519470 | Brasche et al. | Apr 2009 | B2 |
| 7536172 | Minear et al. | May 2009 | B2 |
| 7536695 | Alam et al. | May 2009 | B2 |
| 7565447 | Gellens et al. | Jul 2009 | B2 |
| 7577522 | Rosenberg | Aug 2009 | B2 |
| 7610048 | Ross et al. | Oct 2009 | B2 |
| 7627425 | Salmre et al. | Dec 2009 | B2 |
| 7644126 | Chymaytelli | Jan 2010 | B2 |
| 7684792 | Lundblade et al. | Mar 2010 | B2 |
| 7712660 | Keohane et al. | May 2010 | B2 |
| 7734285 | Chmaytelli et al. | Jun 2010 | B2 |
| 7743407 | Sprigg et al. | Jun 2010 | B2 |
| 7769767 | Petersen | Aug 2010 | B2 |
| 7784089 | Lundblade et al. | Aug 2010 | B2 |
| 7814106 | Guido et al. | Oct 2010 | B2 |
| 7848765 | Phillips et al. | Dec 2010 | B2 |
| 7921287 | Sprigg et al. | Apr 2011 | B2 |
| 8010134 | Barnes et al. | Aug 2011 | B2 |
| 8014762 | Chmaytelli et al. | Sep 2011 | B2 |
| 8020001 | Lundblade et al. | Sep 2011 | B2 |
| 8037515 | Lundblade | Oct 2011 | B2 |
| 8112076 | Lundblade et al. | Feb 2012 | B2 |
| 8165079 | Lee et al. | Apr 2012 | B2 |
| 8219115 | Nelissen | Jul 2012 | B1 |
| 8249577 | Chmaytelli et al. | Aug 2012 | B2 |
| 8321680 | Gantman et al. | Nov 2012 | B2 |
| 8326315 | Phillips et al. | Dec 2012 | B2 |
| 8374628 | Nelissen et al. | Feb 2013 | B1 |
| 8385944 | Nelissen | Feb 2013 | B1 |
| 8403755 | Kerr | Mar 2013 | B2 |
| 8424068 | Lundblade | Apr 2013 | B2 |
| 8468261 | Chmaytelli et al. | Jun 2013 | B2 |
| 8505078 | Hohlfeld et al. | Aug 2013 | B2 |
| 8520511 | Chmaytelli et al. | Aug 2013 | B2 |
| 8536999 | Holcman et al. | Sep 2013 | B2 |
| 8588766 | Lundblade et al. | Nov 2013 | B2 |
| 8620275 | Minear et al. | Dec 2013 | B2 |
| 8620994 | Boyd et al. | Dec 2013 | B2 |
| 8630634 | Chmaytelli et al. | Jan 2014 | B2 |
| 8644847 | Nelissen et al. | Feb 2014 | B1 |
| 8660613 | Minear et al. | Feb 2014 | B2 |
| 8750101 | Oh et al. | Jun 2014 | B2 |
| 8761714 | Son et al. | Jun 2014 | B2 |
| 8856905 | Lundblade | Oct 2014 | B2 |
| 8862150 | Phillips et al. | Oct 2014 | B2 |
| 8868581 | Ryu et al. | Oct 2014 | B2 |
| 8903407 | Chmaytelli | Dec 2014 | B2 |
| 8909248 | Phillips et al. | Dec 2014 | B2 |
| 8942995 | Kerr | Jan 2015 | B1 |
| 8943164 | Kies et al. | Jan 2015 | B2 |
| 9015692 | Clavel | Apr 2015 | B1 |
| 9122542 | Nelissen | Sep 2015 | B1 |
| 9128956 | Salmre et al. | Sep 2015 | B2 |
| 9148431 | Chmaytelli | Sep 2015 | B2 |
| RE45780 | Petersen | Oct 2015 | E |
| 9231763 | Lundblade et al. | Jan 2016 | B2 |
| 9251520 | Shen et al. | Feb 2016 | B2 |
| 9270818 | Nelissen et al. | Feb 2016 | B1 |
| 9286652 | Takishima | Mar 2016 | B2 |
| 9373116 | Kerr | Jun 2016 | B1 |
| 9400403 | Hesline et al. | Jul 2016 | B2 |
| 9436806 | Chmaytelli et al. | Sep 2016 | B2 |
| 9503834 | Ross et al. | Nov 2016 | B2 |
| 9555334 | Bernard et al. | Jan 2017 | B2 |
| 9621549 | Benoit et al. | Apr 2017 | B2 |
| 9654923 | Phillips et al. | May 2017 | B2 |
| 9654978 | Lundblade et al. | May 2017 | B2 |
| 9668096 | Phillips et al. | May 2017 | B2 |
| 9781096 | Sade et al. | Oct 2017 | B2 |
| 9836591 | Archibald et al. | Dec 2017 | B2 |
| 9936347 | Nelissen | Apr 2018 | B1 |
| 10002242 | Jakobsson et al. | Jun 2018 | B2 |
| 10019602 | Kahana et al. | Jul 2018 | B2 |
| 10043170 | Minear et al. | Aug 2018 | B2 |
| 10135613 | McLean et al. | Nov 2018 | B2 |
| 10248775 | Archibald et al. | Apr 2019 | B2 |
| 10321264 | Phillips et al. | Jun 2019 | B2 |
| 10602307 | Phillips et al. | Mar 2020 | B2 |
| 10606996 | Archibald et al. | Mar 2020 | B2 |
| RE48001 | Lundblade et al. | May 2020 | E |
| 10667080 | Phillips et al. | May 2020 | B2 |
| 10691677 | Ryu et al. | Jun 2020 | B2 |
| 10708712 | Phillips et al. | Jul 2020 | B2 |
| 10721587 | Phillips et al. | Jul 2020 | B2 |
| 10728697 | Phillips et al. | Jul 2020 | B2 |
| 10728698 | Phillips et al. | Jul 2020 | B2 |
| 10728699 | Phillips et al. | Jul 2020 | B2 |
| 11044575 | Phillips et al. | Jun 2021 | B2 |
| 11070936 | Phillips et al. | Jul 2021 | B2 |
| 11082798 | Phillips et al. | Aug 2021 | B2 |
| 11115777 | Phillips et al. | Sep 2021 | B2 |
| 20020055880 | Unold | May 2002 | A1 |
| 20020077084 | Zellner | Jun 2002 | A1 |
| 20020107706 | Oliver et al. | Aug 2002 | A1 |
| 20020107795 | Minear et al. | Aug 2002 | A1 |
| 20020123373 | Kirbas et al. | Sep 2002 | A1 |
| 20020142762 | Chmaytelli et al. | Oct 2002 | A1 |
| 20020142844 | Kerr | Oct 2002 | A1 |
| 20020169977 | Chmaytelli | Nov 2002 | A1 |
| 20020173315 | Chmaytelli et al. | Nov 2002 | A1 |
| 20020183056 | Lunblade et al. | Dec 2002 | A1 |
| 20020194325 | Chmaytelli et al. | Dec 2002 | A1 |
| 20030051169 | Sprigg et al. | Mar 2003 | A1 |
| 20030060189 | Minear et al. | Mar 2003 | A1 |
| 20030061504 | Sprigg et al. | Mar 2003 | A1 |
| 20030064705 | Desiderio | Apr 2003 | A1 |
| 20030078886 | Minear et al. | Apr 2003 | A1 |
| 20030101454 | Ozer et al. | May 2003 | A1 |
| 20030139192 | Chmaytelli et al. | Jul 2003 | A1 |
| 20030142039 | Minear et al. | Jul 2003 | A1 |
| 20030143990 | Minear et al. | Jul 2003 | A1 |
| 20030198346 | Meifu et al. | Oct 2003 | A1 |
| 20030207683 | Lempio | Nov 2003 | A1 |
| 20030208401 | Karsten et al. | Nov 2003 | A1 |
| 20040002301 | Ross et al. | Jan 2004 | A1 |
| 20040058651 | Ross et al. | Mar 2004 | A1 |
| 20040087347 | Minear et al. | May 2004 | A1 |
| 20040097244 | Yamazaki et al. | May 2004 | A1 |
| 20040176105 | Ashmore et al. | Sep 2004 | A1 |
| 20040198334 | Chmaytelli et al. | Oct 2004 | A1 |
| 20040203616 | Minear et al. | Oct 2004 | A1 |
| 20040203681 | Ross et al. | Oct 2004 | A1 |
| 20040204719 | Ross et al. | Oct 2004 | A1 |
| 20040205048 | Pizzo et al. | Oct 2004 | A1 |
| 20040214550 | Jenkins | Oct 2004 | A1 |
| 20040220906 | Gargi et al. | Nov 2004 | A1 |
| 20040253965 | Sato et al. | Dec 2004 | A1 |
| 20050009465 | Ross et al. | Jan 2005 | A1 |
| 20050054324 | Chmaytelli et al. | Mar 2005 | A1 |
| 20050055574 | Chmaytelli et al. | Mar 2005 | A1 |
| 20050058067 | Chmaytelli et al. | Mar 2005 | A1 |
| 20050097330 | Lundblade | May 2005 | A1 |
| 20050144294 | Gellens et al. | Jun 2005 | A1 |
| 20050187823 | Howes | Aug 2005 | A1 |
| 20050192878 | Minear et al. | Sep 2005 | A1 |
| 20050282535 | Chmaytelli et al. | Dec 2005 | A1 |
| 20060064346 | Steenstra et al. | Mar 2006 | A1 |
| 20060075040 | Chmaytelli | Apr 2006 | A1 |
| 20060095957 | Lundblade et al. | May 2006 | A1 |
| 20060107327 | Sprigg et al. | May 2006 | A1 |
| 20060116817 | Salmre et al. | Jun 2006 | A1 |
| 20060136292 | Bhati et al. | Jun 2006 | A1 |
| 20060136297 | Willis et al. | Jun 2006 | A1 |
| 20060141993 | Minear et al. | Jun 2006 | A1 |
| 20060223494 | Chmaytelli et al. | Oct 2006 | A1 |
| 20060236098 | Gantman et al. | Oct 2006 | A1 |
| 20060253453 | Chmaytelli et al. | Nov 2006 | A1 |
| 20060253481 | Guido et al. | Nov 2006 | A1 |
| 20060270421 | Phillips et al. | Nov 2006 | A1 |
| 20060281440 | Minear et al. | Dec 2006 | A1 |
| 20060287958 | Lundblade et al. | Dec 2006 | A1 |
| 20070066365 | Minear | Mar 2007 | A1 |
| 20070112741 | Crawford | May 2007 | A1 |
| 20070129888 | Rosenberg et al. | Jun 2007 | A1 |
| 20070180111 | Chmaytelli et al. | Aug 2007 | A1 |
| 20070185768 | Vengroff | Aug 2007 | A1 |
| 20070192409 | Kleinstern | Aug 2007 | A1 |
| 20070198698 | Boyd et al. | Aug 2007 | A1 |
| 20070198841 | Lundblade et al. | Aug 2007 | A1 |
| 20070214180 | Crawford | Sep 2007 | A1 |
| 20070219708 | Brasche et al. | Sep 2007 | A1 |
| 20070244633 | Phillips et al. | Oct 2007 | A1 |
| 20080004952 | Koli | Jan 2008 | A1 |
| 20080032666 | Hughes et al. | Feb 2008 | A1 |
| 20080032703 | Krumm et al. | Feb 2008 | A1 |
| 20080046311 | Shahine | Feb 2008 | A1 |
| 20080086356 | Glassman | Apr 2008 | A1 |
| 20080094256 | Koen | Apr 2008 | A1 |
| 20080098420 | Khivesara et al. | Apr 2008 | A1 |
| 20080109317 | Singh | May 2008 | A1 |
| 20080125099 | Brown et al. | May 2008 | A1 |
| 20080125133 | Chmaytelli | May 2008 | A1 |
| 20080137828 | Chmaytelli | Jun 2008 | A1 |
| 20080146338 | Bernard et al. | Jun 2008 | A1 |
| 20080154728 | Thomas | Jun 2008 | A1 |
| 20080155017 | Minear et al. | Jun 2008 | A1 |
| 20080162032 | Wuersch et al. | Jul 2008 | A1 |
| 20080163073 | Becker et al. | Jul 2008 | A1 |
| 20080182569 | Chmaytelli et al. | Jul 2008 | A1 |
| 20080215524 | Fuchs et al. | Sep 2008 | A1 |
| 20080225815 | Minear et al. | Sep 2008 | A1 |
| 20080262897 | Howarter et al. | Oct 2008 | A1 |
| 20080268876 | Gelfand et al. | Oct 2008 | A1 |
| 20080270235 | Yoon | Oct 2008 | A1 |
| 20080275772 | Suryanarayana | Nov 2008 | A1 |
| 20080307498 | Johnson et al. | Dec 2008 | A1 |
| 20080313039 | Altberg et al. | Dec 2008 | A1 |
| 20090024476 | Baar et al. | Jan 2009 | A1 |
| 20090029721 | Doraswamy | Jan 2009 | A1 |
| 20090063424 | Iwamura et al. | Mar 2009 | A1 |
| 20090089288 | Petersen et al. | Apr 2009 | A1 |
| 20090094248 | Petersen | Apr 2009 | A1 |
| 20090131080 | Nadler et al. | May 2009 | A1 |
| 20090135805 | Lee et al. | May 2009 | A1 |
| 20090157632 | Ryu et al. | Jun 2009 | A1 |
| 20090164602 | Kies et al. | Jun 2009 | A1 |
| 20090165083 | McLean et al. | Jun 2009 | A1 |
| 20090183264 | Chmaytelli et al. | Jul 2009 | A1 |
| 20090186595 | Son et al. | Jul 2009 | A1 |
| 20090191860 | Oh et al. | Jul 2009 | A1 |
| 20090197582 | Lewis | Aug 2009 | A1 |
| 20090210700 | Nomura et al. | Aug 2009 | A1 |
| 20090239510 | Sennett | Sep 2009 | A1 |
| 20100042320 | Salmre et al. | Feb 2010 | A1 |
| 20100070351 | Kang | Mar 2010 | A1 |
| 20100075697 | Gupta et al. | Mar 2010 | A1 |
| 20100077022 | Mikkelsen | Mar 2010 | A1 |
| 20100130179 | Colligan | May 2010 | A1 |
| 20100131501 | Deeming | May 2010 | A1 |
| 20100173608 | Lundblade et al. | Jul 2010 | A1 |
| 20100248709 | Chmaytelli et al. | Sep 2010 | A1 |
| 20100269156 | Hohlfeld et al. | Oct 2010 | A1 |
| 20100312646 | Gupta et al. | Dec 2010 | A1 |
| 20100325708 | Lundblade et al. | Dec 2010 | A1 |
| 20110010383 | Thompson et al. | Jan 2011 | A1 |
| 20120030742 | Lundblade | Feb 2012 | A1 |
| 20120126974 | Phillips et al. | May 2012 | A1 |
| 20120129553 | Phillips et al. | May 2012 | A1 |
| 20120137349 | Lundblade et al. | May 2012 | A1 |
| 20130072177 | Ross et al. | Mar 2013 | A1 |
| 20130182838 | Kelley et al. | Jul 2013 | A1 |
| 20130227667 | Lundblade | Aug 2013 | A1 |
| 20130283395 | Chmaytelli et al. | Oct 2013 | A1 |
| 20130326596 | Hohlfeld et al. | Dec 2013 | A1 |
| 20140013390 | Sade et al. | Jan 2014 | A1 |
| 20150005017 | Ryu et al. | Jan 2015 | A1 |
| 20150065177 | Phillips et al. | Mar 2015 | A1 |
| 20150148078 | Phillips et al. | May 2015 | A1 |
| 20150163632 | Phillips et al. | Jun 2015 | A1 |
| 20150382141 | Salmre et al. | Dec 2015 | A1 |
| 20160021245 | Chmaytelli | Jan 2016 | A1 |
| 20160028725 | Benoit et al. | Jan 2016 | A1 |
| 20160063281 | Kahana et al. | Mar 2016 | A1 |
| 20160171198 | Archibald et al. | Jun 2016 | A1 |
| 20160227411 | Lundblade et al. | Aug 2016 | A1 |
| 20160283064 | Ross et al. | Sep 2016 | A1 |
| 20160299854 | Deivasigamani et al. | Oct 2016 | A1 |
| 20160308849 | Sade et al. | Oct 2016 | A1 |
| 20170053108 | Jakobsson et al. | Feb 2017 | A1 |
| 20170289197 | Mandyam et al. | Oct 2017 | A1 |
| 20170310677 | Chmaytelli et al. | Oct 2017 | A1 |
| 20180068106 | Archibald et al. | Mar 2018 | A1 |
| 20180124564 | Phillips et al. | May 2018 | A1 |
| 20190156006 | Archibald et al. | May 2019 | A1 |
| 20190373402 | Phillips et al. | Dec 2019 | A1 |
| 20190373406 | Phillips et al. | Dec 2019 | A1 |
| 20190380000 | Phillips et al. | Dec 2019 | A1 |
| 20190380001 | Phillips et al. | Dec 2019 | A1 |
| 20190380002 | Phillips et al. | Dec 2019 | A1 |
| 20200112821 | Phillips et al. | Apr 2020 | A1 |
| 20200112822 | Phillips et al. | Apr 2020 | A1 |
| 20200112823 | Phillips et al. | Apr 2020 | A1 |
| 20200112824 | Phillips et al. | Apr 2020 | A1 |
| 20200112825 | Phillips et al. | Apr 2020 | A1 |
| 20200120442 | Phillips et al. | Apr 2020 | A1 |
| 20220103966 | Phillips et al. | Mar 2022 | A1 |
| Number | Date | Country |
|---|---|---|
| 20040021267 | Mar 2004 | KR |
| 20080019867 | Mar 2008 | KR |
| WO 2008082794 | Jul 2008 | WO |
| Entry |
|---|
| Jing et al., Client-Server Computing in Mobile Environments, Jun. 1999, ACM Computing Surveys, vol. 31, No. 2. |
| Claim Construction Order—Hardin et al. v. Samsung Elecs. Co., Ltd et al., 2:21-cv-00290-JRG, ECF No. 86 (E.D. Tex. Aug. 25, 2022). |
| Exhibit 1016—Complaint—Hardin et al. v. Samsung Elecs. Co., Ltd et al., 2:21-cv-00290-JRG, ECF No. 1 (E.D. Tex. Jul. 30, 2021). |
| Petition for Inter Partes Review of U.S. Pat. No. 9,779,418—Case IPR2022-01330, Aug. 2, 2022. |
| Declaration of David Williams ISO 418 Patent IPR Petition—1330, Aug. 2, 2022. |
| Petition for Inter Partes Review of U.S. Pat. No. 9,779,418—Case IPR2022-01331, Aug. 2, 2022. |
| Declaration of David Williams ISO 418 Patent IPR Petition—1331, Aug. 2, 2022. |
| Petition for Inter Partes Review of U.S. Pat. No. 9,779,418—Case IPR2022-01332, Aug. 2, 2022. |
| Declaration of David Williams ISO 418 Patent IPR Petition—1332, Aug. 2, 2022. |
| Petition for Inter Partes Review of U.S. Pat. No. 10,049,387—Case IPR2022-01327, Aug. 2, 2022. |
| Declaration of David Williams ISO 387 Patent IPR Petition—1327, Aug. 2, 2022. |
| Petition for Inter Partes Review of U.S. Pat. No. 10,049,387—Case IPR2022-01328, Aug. 2, 2022. |
| Declaration of David Williams ISO 387 Patent IPR Petition—1328, Aug. 2, 2022. |
| Petition for Inter Partes Review of U.S. Pat. No. 10,049,387—Case IPR2022-01329, Aug. 2, 2022. |
| Declaration of David Williams ISO 387 Patent IPR Petition—1329, Aug. 2, 2022. |
| Petition for Inter Partes Review of U.S. Pat. No. 10,984,447—Case IPR2022-01333, Aug. 2, 2022. |
| Declaration of David Williams ISO 447 Patent IPR Petition—1333, Aug. 2, 2022. |
| Petition for Inter Partes Review of U.S. Pat. No. 10,984,447—Case IPR2022-01334, Aug. 2, 2022. |
| Declaration of David Williams ISO 447 Patent IPR Petition—1334, Aug. 2, 2022. |
| Petition for Inter Partes Review of U.S. Pat. No. 10,984,447—Case IPR2022-01335, Aug. 2, 2022. |
| Declaration of David Williams ISO 447 Patent IPR Petition—1335, Aug. 2, 2022. |
| Exhibit 1020—Geofencing, Techopedia, https://www.techopedia.com/definition/14937/geofencing. |
| Exhibit 1021—Jonathan P. Munson & Vineet K. Gupta, Location-Based Notification as a General-Purpose Service, Proceedings of the 2nd International Workshop on Mobile Commerce 40 (2002). |
| Exhibit 1022—What We Do, Locating What's Important To You, Cell-Loc, http://web.archive.org/web/20030411221815/http://cellloc.com/what_locating.html. |
| Exhibit 1023—Alan Cohen, Location, Location, Location, PC Mag., available at https://books.google.com/books? id=elvagv988JgC&pg=PA82#v=onepage&q&f=false. |
| Exhibit 1019—Plaintiffs' Objections And Response To Defendants' Second Set Of Interrogatories To Plaintiff, Hardin et al. v. Samsung Elecs. Co., Ltd et al., 2:21-cv-00290-JRG, served Jul. 1, 2022. |
| Exhibit 1029—Defendants' Claim Construction Brief—Hardin et al. v. Samsung Elecs. Co., Ltd et al., 2:21-cv-00290-JRG, ECF 67 (E.D. Tex. Jul. 25, 2022). |
| Exhibit 1028—Plaintiffs' Claim Construction Brief—Hardin et al. v. Samsung Elecs. Co., Ltd et al., 2:21-cv-00290-JRG, ECF 58 (E.D. Tex. Jul. 8, 2022). |
| IPR2022-01327, Decision Granting Institution of Inter Partes Review of U.S. Pat. No. 10,049,387 B2, dated Feb. 7, 2023. |
| IPR2022-01328, Decision Granting Institution of Inter Partes Review of U.S. Pat. No. 10,049,387 B2, dated Feb. 8, 2023. |
| IPR2022-01329, Decision Granting Institution of Inter Partes Review of U.S. Pat. No. 10,049,387 B2, dated Feb. 8, 2023. |
| IPR2022-01330, Decision Granting Institution of Inter Partes Review of U.S. Pat. No. 9,779,418 B2, dated Feb. 8, 2023. |
| IPR2022-01331, Decision Granting Institution of Inter Partes Review of U.S. Pat. No. 9,779,418 B2, dated Feb. 7, 2023. |
| IPR2022-01332, Decision Granting Institution of Inter Partes Review of U.S. Pat. No. 9,779,418 B2, dated Feb. 8, 2023. |
| IPR2022-01333, Decision Granting Institution of Inter Partes Review of U.S. Pat. No. 10,984,447 B2, dated Feb. 7, 2023. |
| IPR2022-01334, Decision Granting Institution of Inter Partes Review of U.S. Pat. No. 10,984,447 B2, dated Feb. 8, 2023. |
| IPR2022-01335, Decision Granting Institution of Inter Partes Review of U.S. Pat. No. 10,984,447 B2, dated Feb. 8, 2023. |
| Barbeau et al., Location API 2.0 for J2ME—A New Standard in Location for Java-Enabled Mobile Phones, Jan. 31, 2008, Computer Communications. |
| Bauer et al., Information Management and Exchange in the Nexus Platform, Version 2.0, Sep. 3, 2004, Universität Stuttgart. |
| Durr et al. (“Durr 2003”), On a Location Model for Fine-Grained Geocast, Oct. 2003, UbiComp. |
| Durr et al. (“Durr 2004”), Nexus—A Platform for Context-Aware Applications, Jun. 2004, GI/ITG KuVS Fachgespräch Ortsbezogene Anwendungen und Dienste. |
| Fuchs, Realizing Location-Based Push-Services on Mobile Devices, Jul. 18, 2002, Institut für Informatik der Technischen Universität München. |
| Marmasse et al., Location-Aware Information Delivery with ComMotion, 2000, Springer-Verlag Berlin Heidelberg. |
| Martens et al., OGAS—Open Geographic Applications Standard: An Open User-Centric Description Language for Exchangeable Location-Based Services, Sep. 4, 2008, GI/ITG KuVS Fachgespräch Ortsbezogene Anwendungen und Dienste. |
| Nicklas et al., NexusScout: An Advanced Location-Based Application on a Distributed, Open Mediation Platform, 2003, VLDB Conference. |
| Parsons, The Java Location API, Jan. 2006, Dr. Dobb's Journal. |
| Ranganathan et al., MiddleWhere: A Middleware for Location Awareness in Ubiquitous Computing Applications, 2004. |
| Sohn et al., Place-Its: A Study of Location-Based Reminders on Mobile Phones, Sep. 11, 2005, UbiComp. |
| Scheifler, X Window System Protocol, X Version 11, Release 6.9, 7.0 (“X Window System Protocol 2005”), 2005. |
| Location API for Java™ 2 Micro Edition, Version 1.0.1. |
| Cheng, It's Official: Google Announces Open-Source Mobile Phone OS, Android (Nov. 5, 2007), https://arstechnica.com/gadgets/2007/11/its-official-google-announces-open-source-mobile-phone-os-android/. |
| Android Team, This is the Droid You're Looking For (Nov. 12, 2007), https://android-developers.googleblog.com/2007/11/posted-by-jason-chen-android-advocate.html. |
| Press Release, Open Handset Alliance, Open Handset Alliance Releases Android SDK (Nov. 12, 2007), https://www.openhandsetalliance.com/press_111207.html. |
| Android Team, Android: The First Week (Nov. 16, 2007), https://android-developers.googleblog.com/2007/11/android-first-week.html. |
| Android Team, Life Can Be Tough; Here Are a Few SDK Improvements to Make It a Little Easier (Dec. 14, 2007), https://android-developers.googleblog.com/2007/12/life-can-be-tough-here-are-few-sdk.html. |
| Press Release, Open Handset Alliance, Leading Mobile Players Demonstrate Early Look of Android at Mobile World Congress 2008 in Barcelona (Feb. 11, 2008), https://www.openhandsetalliance.com/press_021108.html. |
| Miller, MWC08: Hands-on With a Working Google Android Device (Feb. 12, 2008), https://www.zdnet.com/article/mwc08-hands-on-with-a-working-google-android-device/. |
| Android Team, Android SDK m5-rc14 Now Available (Feb. 13, 2008), https://android-developers.googleblog.com/2008/02/android-sdk-m5-rc14-now-available.html. |
| Android Team, Android SDK Update: m5-rc15 Released (Mar. 3, 2008), https://android-developers.googleblog.com/2008/03/android-sdk-update-m5-rc15-released.html. |
| Android Team, Announcing: Apps for Android (Mar. 4, 2008), https://android-developers.googleblog.com/2008/03/announcing-apps-for-android.html. |
| Android Team, WikiNotes for Android: Routing Intents (Mar. 19, 2008), https://android-developers.googleblog.com/2008/03/wikinotes-for-android-routing-intents.html. |
| Android Team, Android Developers Have Risen to the Challenge (Apr. 17, 2008), https://android-developers.googleblog.com/2008/04/android-developers-have-risen-to.html. |
| Android Team, The Top 50 Applications (May 12, 2008), https://android-developers.googleblog.com/2008/05/top-50-applications.html. |
| Android Team, Android Developer Challenge Judges and Top 50 Details (May 14, 2008), https://android-developers.googleblog.com/2008/05/android-developer-challenge-judges-and.html. |
| Android Team, Android Developer Challenge Slide Deck (May 14, 2008), available at https://android.googlesource.com/platform/frameworks/base/+archive/54b6cfa9a9e5b861a9930af873580d6dc20f773c.tar.gz (“adc1r1_deck.pdf”). |
| Android Team, Announcing a Beta Release of the Android SDK (Aug. 18, 2008), https://android-developers.googleblog.com/2008/08/announcing-beta-release-of-android-sdk.html. |
| Android Team, Android market: A User-Driven Content Distribution System (Aug. 28, 2008), https://android-developers.googleblog.com/2008/08/android-market-user-driven-content.html. |
| Android Team, Panoramio (Sep. 22, 2008), https://android-developers.googleblog.com/2008/09/panoramio.html. |
| Android Team, Announcing the Android 1.0 SDK, Release 1 (Sep. 23, 2008), https://android-developers.googleblog.com/2008/09/announcing-android-10-sdk-release-1.html. |
| Android Team, Android is Now Open Source (Oct. 21, 2008), https://android-developers.googleblog.com/2008/10/android-is-now-open-source.html. |
| AOSP Initial Contribution (Oct. 21, 2008), https://android.googlesource.com/platform/frameworks/base/+/54b6cfa9a9e5b861a9930af873580d6dc20f773c. |
| Android Team, The Stories Behind the Apps (Oct. 28, 2008), https://android-developers.googleblog.com/2008/10/stories-behind-apps.html. |
| Amadeo, The (Updated) History of Android (Oct. 31, 2016), http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/. |
| Android Team, SDK Archives (last updated Aug. 11, 2021), https://developer.android.com/sdk/older_releases. |
| Defendants' Invalidity Contentions Pursuant to Patent Local Rules 3-3 and 3-4 (Case No. 2:21-cv-290-JRG, E.D. Tex.) dated Mar. 17, 2022. |
| Exhibit A-1—Invalidity of U.S. Pat. No. 9,779,418 (“418 Patent”) by U.S. Patent Application Publication No. 2006/0223494 A1 (“Chmaytelli”). |
| Exhibit A-2—Invalidity of U.S. Pat. No. 9,779,418 (“418 Patent”) by U.S. Pat. No. 7,089,264 (“Guido”). |
| Exhibit A-3—Invalidity of U.S. Pat. No. 9,779,418 (“418 Patent”) by U.S. Patent App. Pub. No. 2008/0032666 A1 (“Hughes”). |
| Exhibit A-4—Invalidity of U.S. Pat. No. 9,779,418 (“418 Patent”) by U.S. Pat. No. 8,219, 115 (“Nelissen”). |
| Exhibit A-5—Invalidity of U.S. Pat. No. 9,779,418 (“418 Patent”) by U.S. App. Pub. No. 2009/0089288 A1 (“Petersen”). |
| Exhibit A-6—Invalidity of U.S. Pat. No. 9,779,418 (“418 Patent”) by U.S. Patent App. Pub. No. 2006/0270421A1 (“Phillips”). |
| Exhibit A-7—Invalidity of U.S. Pat. No. 9,779,418 (“418 Patent”) by U.S. Patent Application Pub. No. 2007/0129888A1 (“Rosenberg”). |
| Exhibit A-8—Invalidity of U.S. Pat. No. 9,779,418 (“418 Patent”) by U.S. Patent Application Publication No. US 2009/0157632 A1 (“Ryu”). |
| Exhibit A-9—Invalidity of U.S. Pat. No. 9,779,418 (“418 Patent”) by U.S. Patent Application Pub. No. 2006/0116817 A1 (“Salmre”). |
| Exhibit A-10—Invalidity of U.S. Pat. No. 9,779,418 (“418 Patent”) by U.S. Pat. No. 7,054,649 (“Yamazaki”). |
| Exhibit A-11—Invalidity of U.S. Pat. No. 9,779,418 (“418 Patent”) by Natalia Marmasse & Chris Schmandt, Location-Aware Information Delivery with ComMotion, in Lecture Notes in Computer Science 1927: Handheld and Ubiquitous Computing, Second International Symposium at 157 (Sept. 25-27, 2000) (“Marmasse”). |
| Exhibit A-12—Invalidity of U.S. Pat. No. 9,779,418 (“418 Patent”) by David Parsons, The Java Location API, Dr. Dobb's Journal, Jan. 2006, at 53 (“Parsons”). |
| Exhibit A-13—Invalidity of U.S. Pat. No. 9,779,418 (“418 Patent”) by Anand Ranganathan et al., MiddleWhere: A Middleware for Location Awareness in Ubiquitous Computing Applications, 3231 Lecture Notes in Comp. Sci. 397 (2004) (“Ranganathan”). |
| Exhibit A-14—Invalidity of U.S. Pat. No. 9,779,418 (“418 Patent”) by Timothy Sohn et al., Place-Its: A Study of Location-Based Reminders on Mobile Phones, UbiComp '05: Proceedings of the 7th International Conference on Ubiquitous Computing 232 (Sep. 2005) (“Sohn”). |
| Exhibit A-15—Invalidity of U.S. Pat. No. 9,779,418 (“418 Patent”) by Version 1.0 of the Android Operating System, Beta Versions of Android, and Android Software Development Kits (“Android 2007-2008”). |
| Exhibit A-16—Invalidity of U.S. Pat. No. 9,779,418 (“418 Patent”) by Location API for Java™ 2 Micro Edition, Version 1.0.1 (“JSR 179”). |
| Exhibit A-17—Invalidity of U.S. Pat. No. 9,779,418 (“418 Patent”) by U.S. Pat. No. 9,286,625 (“625 Patent”). |
| Exhibit A-18—Subject Matter Eligibility Contentions for U.S. Pat. No. 9,779,418 (“418 Patent”). |
| Exhibit B-1—Invalidity of U.S. Pat. No. 10,049,387 (“387 Patent”) by U.S. Patent Application Publication No. 2006/0223494 A1 (“Chmaytelli”). |
| Exhibit B-2—Invalidity of U.S. Pat. No. 10,049,387 (“387 Patent”) by U.S. Pat. No. 7,089,264 (“Guido”). |
| Exhibit B-3—Invalidity of U.S. Pat. No. 10,049,387 (“387 Patent”) by U.S. Patent App. Pub. No. 2008/0032666 A1 (“Hughes”). |
| Exhibit B-4—Invalidity of U.S. Pat. No. 10,049,387 (“387 Patent”) by U.S. Pat. No. 8,219, 115 (“Nelissen”). |
| Exhibit B-5—Invalidity of U.S. Pat. No. 10,049,387 (“387 Patent”) by U.S. App. Pub. No. 2009/0089288 A1 (“Petersen”). |
| Exhibit B-6—Invalidity of U.S. Pat. No. 10,049,387 (“387 Patent”) by U.S. Patent App. Pub. No. 2006/0270421A1 (“Phillips”). |
| Exhibit B-7—Invalidity of U.S. Pat. No. 10,049,387 (“387 Patent”) by U.S. Patent Application Pub. No. 2007/0129888A1 (“Rosenberg”). |
| Exhibit B-8—Invalidity of U.S. Pat. No. 10,049,387 (“387 Patent”) by U.S. Patent Application Publication No. US 2009/0157632 A1 (“Ryu”). |
| Exhibit B-9—Invalidity of U.S. Pat. No. 10,049,387 (“387 Patent”) by U.S. Patent Application Pub. No. 2006/0116817A1 (“Salmre”). |
| Exhibit B-10—Invalidity of U.S. Pat. No. 10,049,387 (“387 Patent”) by U.S. Pat. No. 7,054,649 (“Yamazaki”). |
| Exhibit B-11—Invalidity of U.S. Pat. No. 10,049,387 (“387 Patent”) by Natalia Marmasse & Chris Schmandt, Location-Aware Information Delivery with ComMotion, in Lecture Notes in Computer Science 1927: Handheld and Ubiquitous Computing, Second International Symposium at 157 (Sept. 25-27, 2000) (“Marmasse”). |
| Exhibit B-12—Invalidity of U.S. Pat. No. 10,049,387 (“387 Patent”) by David Parsons, The Java Location API, Dr. Dobb's Journal, Jan. 2006, at 53 (“Parsons”). |
| Exhibit B-13—Invalidity of U.S. Pat. No. 10,049,387 (“387 Patent”) by Anand Ranganathan et al., MiddleWhere: A Middleware for Location Awareness in Ubiquitous Computing Applications, 3231 Lecture Notes in Comp. Sci. 397 (2004) (“Ranganathan”). |
| Exhibit B-14—Invalidity of U.S. Pat. No. 10,049,387 (“387 Patent”) by Timothy Sohn et al., Place-Its: A Study of Location-Based Reminders on Mobile Phones, UbiComp '05: Proceedings of the 7th International Conference on Ubiquitous Computing 232 (Sep. 2005) (“Sohn”). |
| Exhibit B-15—Invalidity of U.S. Pat. No. 10,049,387 (“387 Patent”) by Version 1.0 of the Android Operating System, Beta Versions of Android, and Android Software Development Kits (“Android 2007-2008”). |
| Exhibit B-16—Invalidity of U.S. Pat. No. 10,049,387 (“387 Patent”) by Location API for Java™ 2 Micro Edition, Version 1.0.1 (“JSR 179”). |
| Exhibit B-17—Invalidity of U.S. Pat. No. 10,049,387 (“387 Patent”) by U.S. Pat. No. 9,779,418 (“418 Patent”). |
| Exhibit B-18—Subject Matter Eligibility Contentions for U.S. Pat. No. 10,049,387 (“387 Patent”). |
| Exhibit C-1—Invalidity of U.S. Pat. No. 10,984,447 (“447 Patent”) by U.S. Patent Application Publication No. 2006/0223494 A1 (“Chmaytelli”). |
| Exhibit C-2—Invalidity of U.S. Pat. No. 10,984,447 (“447 Patent”) by U.S. Pat. No. 7,089,264 (“Guido”). |
| Exhibit C-3—Invalidity of U.S. Pat. No. 10,984,447 (“447 Patent”) by U.S. Patent App. Pub. No. 2008/0032666 A1 (“Hughes”). |
| Exhibit C-4—Invalidity of U.S. Pat. No. 10,984,447 (“447 Patent”) by U.S. Pat. No. 8,219,115 (“Nelissen”). |
| Exhibit C-5—Invalidity of U.S. Pat. No. 10,984,447 (“447 Patent”) by U.S. App. Pub. No. 2009/0089288 A1 (“Petersen”). |
| Exhibit C-6—Invalidity of U.S. Pat. No. 10,984,447 (“447 Patent”) by U.S. Patent App. Pub. No. 2006/0270421A1 (“Phillips”). |
| Exhibit C-7—Invalidity of U.S. Pat. No. 10,984,447 (“447 Patent”) by U.S. Patent Application Pub. No. 2007/0129888A1 (“Rosenberg”). |
| Exhibit C-8—Invalidity of U.S. Pat. No. 10,984,447 (“447 Patent”) by U.S. Patent Application Publication No. US 2009/0157632 A1 (“Ryu”). |
| Exhibit C-9—Invalidity of U.S. Pat. No. 10,984,447 (“447 Patent”) by U.S. Patent Application Pub. No. 2006/0116817 A1 (“Salmre”). |
| Exhibit C-10—Invalidity of U.S. Pat. No. 10,984,447 (“447 Patent”) by U.S. Pat. No. 7,054,649 (“Yamazaki”). |
| Exhibit C-11—Invalidity of U.S. Pat. No. 10,984,447 (“447 Patent”) by Natalia Marmasse & Chris Schmandt, Location-Aware Information Delivery with ComMotion, in Lecture Notes in Computer Science 1927: Handheld and Ubiquitous Computing, Second International Symposium at 157 (Sept. 25-27, 2000) (“Marmasse”). |
| Exhibit C-12—Invalidity of U.S. Pat. No. 10,984,447 (“447 Patent”) by David Parsons, The Java Location API, Dr. Dobb's Journal, Jan. 2006, at 53 (“Parsons”). |
| Exhibit C-13—Invalidity of U.S. Pat. No. 10,984,447 (“447 Patent”) by Anand Ranganathan et al., MiddleWhere: A Middleware for Location Awareness in Ubiquitous Computing Applications, 3231 Lecture Notes in Comp. Sci. 397 (2004) (“Ranganathan”). |
| Exhibit C-14—Invalidity of U.S. Pat. No. 10,984,447 (“447 Patent”) by Timothy Sohn et al., Place-Its: A Study of Location-Based Reminders on Mobile Phones, UbiComp '05: Proceedings of the 7th International Conference on Ubiquitous Computing 232 (Sep. 2005) (“Sohn”). |
| Exhibit C-15—Invalidity of U.S. Pat. No. 10,984,447 (“447 Patent”) by Version 1.0 of the Android Operating System, Beta Versions of Android, and Android Software Development Kits (“Android 2007-2008”). |
| Exhibit C-16—Invalidity of U.S. Pat. No. 10,984,447 (“447 Patent”) by Location API for Java™ 2 Micro Edition, Version 1.0.1 (“JSR 179”). |
| Exhibit C-17—Invalidity of U.S. Pat. No. 10,984,447 (“447 Patent”) by U.S. Pat. No. 10,049,387 (“387 Patent”). |
| Exhibit C-18—Subject Matter Eligibility Contentions for U.S. Pat. No. 10,984,447 (“447 Patent”). |
| AdMob, Inc., “Help for Advertisers—Ad Pricing”, http://www.admob.com/home/help/helpfiles/Advertisers/Ad Pricing, May 19, 2009. |
| AdMob, Inc., “Help for Advertisers—Target the Specific User You Want to Reach”, http://www.admob.com/home/help/helpfiles/Advertisers/Target, May 19, 2009. |
| AdMob, Inc., “iPhone for Advertisers”, http://www.admob.com/home/help/helpfiles/Advertisers/iPhone Ad, May 19, 2009. |
| Google, Inc., “What are the different options for targeting ads to mobile phones and devices?”, https://adwords.google.com/support/bin/answer=107265&hl=en.sub.-US, May 18, 2009. |
| Google, Inc., “How does customized targeting work?”, http://adwords.google.com/support/bin/answer.py?answer=116, May 18, 2009. |
| Google, Inc., “How are ads ranked?”, http://adwords.google.com/support/bin/answer.py?hl=en&answer=6111, May 18, 2009. |
| Google, Inc., “How do ads cycle through the search page results?”, http://adwords.google.com/support/bin/answer.py? hl=en&answer=87402, May 18, 2009. |
| Google, Inc., “How do I create a mobile ad?”, http://adwords.google.com/support/bin/answer=29488&cbid, May 18, 2009. |
| Google, Inc., “Lesson 3c: Language & Location Targeting”, http://www.google.com/adwords/learningcenter/text/ print-19158.html, May 19, 2009. |
| Google, Inc., “What is position preference?”, http://adwords.google.com/support/bin/answer.py?hl=en&answer=31788, May 19, 2009. |
| Google, Inc., “What are mobile ads?”, http://adwords.google.com/support/bin/answer.py?answer=29492&cbid, May 18, 2009. |
| Google, Inc., “Why can't I see my ad?”, http://adwords.google.com/support/bin/answer.py?hl=en&answer=6105, May 18, 2009. |
| Wayback Machine, “Iphone App Advertisement”, http://www.blog.yieldbuild.com/2008/08/21/iphone-app-advertising/, Aug. 24, 2008. |
| Number | Date | Country | |
|---|---|---|---|
| 20220351245 A1 | Nov 2022 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 17182809 | Feb 2021 | US |
| Child | 17863208 | US | |
| Parent | 16019285 | Jun 2018 | US |
| Child | 17182809 | US | |
| Parent | 15694786 | Sep 2017 | US |
| Child | 16019285 | US | |
| Parent | 15009961 | Jan 2016 | US |
| Child | 15694786 | US | |
| Parent | 14608285 | Jan 2015 | US |
| Child | 15009961 | US | |
| Parent | 13856392 | Apr 2013 | US |
| Child | 14608285 | US | |
| Parent | 12434094 | May 2009 | US |
| Child | 13856392 | US |
