TW202536757A - Location-based service web push system - Google Patents

Abstract

A Location-Based Service Web Push System, comprising multiple consumer devices, at least one telecommunications operator server, multiple web servers, at least one push administrator device, and a push server. The telecommunications operator server is configured to provide multiple pieces of location information, each corresponding to different consumer devices. The push administrator device is configured to issue a push command. The push server, which is communicatively connected to the telecommunications operator server, receives the push command. It is designed to retrieve the corresponding location information based on the location-specific data from the telecommunications operator server, generate at least one push message according to the push command, and transmit the push message to the corresponding consumer devices in the form of a web push, alongside the location information.

Description

Location-based web page push system

A web page push system, particularly a location-based web page push system.

Current push advertising systems primarily target ads based on user behavior and preferences; however, their personalization in terms of geolocation is relatively limited. Specifically, traditional push advertising relies mainly on users' browsing history, interests, and other online behaviors. While this method allows for personalized ad delivery, its effectiveness is limited for ads requiring regional or location-specific targeting. For example, a restaurant operating only in a specific area might find its push ads being sent to users thousands of miles away, which is clearly detrimental to promoting regional offers. The Global Positioning System (GPS) provides precise geolocation information. However, GPS also has its limitations. First, it requires the target device (usually a smartphone or tablet) to have GPS enabled, but not all users are willing or accustomed to keeping GPS on, especially considering the increased battery consumption. Therefore, relying on GPS for ad delivery may limit the reach and effectiveness of advertising. In conclusion, current push advertising systems have significant shortcomings in terms of regional and location-specific ad delivery. Therefore, it is necessary to develop a new location-based service (LBS) web push system to more effectively address these issues.

In view of the above problems, this invention provides a location-based webpage push system. It obtains consumer location data through telecommunications operators and uses this data for webpage push notifications to achieve targeted advertising delivery within a specified area, effectively increasing the effectiveness of regional advertising delivery. The specific technical means are as follows: A location-based webpage push system includes multiple consumer devices, at least one telecommunications operator server, multiple web servers, at least one push notification manager device, and one push notification server. The telecommunications operator server is adapted to provide multiple location information, which corresponds to different consumer devices. The web servers are connected to the telecommunications operator server. The push notification manager device is adapted to provide a push notification instruction, which includes at least one location-specific data. The push server is communicatively connected to the telecom operator's server and the push management device, and receives push instructions. The push server includes a location acquisition module and a push module. The location acquisition module is adapted to obtain corresponding location information from the telecom operator's server based on the location specification data. The push module generates at least one push message according to the push instruction and transmits the push message, along with the location information, to the corresponding consumer device. The push message is transmitted to the consumer device in the form of a web page push. In the aforementioned location-based web page push system, the push server further includes a feedback data collection module. If the push message is clicked on the consumer device, the feedback data collection module generates an attribute tag associated with the consumer device that clicked the push message. In the aforementioned location-based webpage push notification system, the push notification module is further adapted to send the push notification message to the consumer device based on the attribute tag. In the aforementioned location-based webpage push notification system, the push notification server further includes a tag database module adapted to store and manage the attribute tag. In the aforementioned location-based webpage push notification system, the push notification manager device is further adapted to connect to the push notification server and browse the attribute tag. In the aforementioned location-based webpage push notification system, the push notification manager device is further adapted to input at least one tag browsing request data, and the tag database module is adapted to receive the tag browsing request data and display the corresponding attribute tag on the push notification manager device based on the tag browsing request data. In the location-based web push system described above, when the push module sends a push message to the consumer device based on the attribute tag, the feedback data collection module copies the attribute tag and maps the copied attribute tag to other consumer devices around the consumer device receiving the push message. In the location-based web push system described above, the attribute tag also includes a weight value, and the push module is further adapted to send the push message to the consumer device based on the weight value of the attribute tag. In the location-based web push system described above, the weight value of the copied attribute tag is copied from the original attribute tag, and the weight value of the copied attribute tag decreases over time.

Please refer to Figures 1A and 1B, which illustrate the system architecture of the location-based web push system 100 of this invention. The location-based web push system 100 includes a consumer device 110, at least one telecommunications operator server 120, multiple web servers 130, at least one push administrator device 150, and one push server 140. The consumer device 110 is communicatively connected to the telecommunications operator server 120 and can connect to the web server 130 through the telecommunications operator server 120. The push server 140 is communicatively connected to both the telecommunications operator server 120 and the push administrator device 150. Consumer device 110 refers to an electronic or mobile device used by a consumer, such as a smartphone, that has internet access and web browsing capabilities. Consumer device 110 is suitable for receiving push notifications from web server 130. Furthermore, consumer device 110 connects to the internet via telecommunications operator server 120, thereby connecting to web server 130 to browse the web, and therefore its location information can be obtained by telecommunications operator server 120. Telecommunications operator server 120 is a server managed and maintained by a telecommunications network provider. Such a provider is, for example, Chunghwa Telecom or Taiwan Mobile. These telecommunications operator servers 120 are able to obtain the location information of consumer device 110. Furthermore, the telecommunications operator server 120 periodically exchanges data with the push server 140 and provides this location information to the push server 140. The telecommunications operator server 120 obtains the location data of the consumer device 110 within a specific area through its network server. For example, it obtains the location data through network nodes such as base stations or Wi-Fi nodes. It is important to note that the telecommunications operator server 120 does not provide GPS data; therefore, even if the consumer device 110 does not have GPS enabled, the telecommunications operator server 120 can still obtain the location data through network nodes. The web server 130 is a server for various websites, including but not limited to shopping websites, news websites, or social media. Consumer device 110 can connect to these web servers 130 via browser software to browse web pages. In addition to providing web page content, these web servers 130 also provide a platform allowing consumer device 110 to register and subscribe to push services, becoming a push target of push server 140. Furthermore, in one embodiment, web server 130 generates a list of subscribed consumers and provides it to push server 140. Push management device 150 refers to the device used by the person responsible for publishing push advertisements, such as an advertising placement company, hereinafter referred to as the push manager. Push management device 150 has a corresponding user interface for push managers to input and manage push instructions. The push notification contains various parameters, including at least location specification data and the push advertising content (such as text and images). Location specification data defines the target area where the push advertisement will be placed; these areas are defined based on specific boundaries, such as administrative districts, villages, streets, stations, and commercial areas. The push server 140 is responsible for processing and sending push messages. The push server 140 also has the function of connecting to the telecommunications operator server 120 and obtaining data. The push server 140 includes a location acquisition module 141 and a push module 142. The location acquisition module 141 is adapted to obtain location information received from the telecommunications operator server 120. Specifically, the location acquisition module 141 periodically exchanges data between the push server 140 and the telecommunications operator's server 120 to obtain the location information of the consumer device 110. The push module 142 is adapted to generate at least push messages based on received push instructions. These push messages include advertising content specified by the push administrator and other relevant information. After the push messages are generated, the push module 142 transmits these push messages to the corresponding consumer device 110 located within the target area based on the obtained location information. Furthermore, the push messages are delivered via web push, meaning that the push messages are received by a web browser after the consumer device 110 registers with the web server. In one embodiment, the push server 140 also includes a feedback data collection module 143 adapted to track and collect consumer responses to push notifications. When a push notification is clicked or interacted with on a consumer device 110, the feedback data collection module 143 generates an attribute tag. This attribute tag is directly associated with the consumer device 110 that clicked or interacted with the push notification. The attribute tag records the clicked ad content and also the area where the consumer device 110 was located when it clicked the ad. In this way, the attribute tag helps to further distinguish and understand consumer preferences, behavioral patterns, or frequently visited areas. In one embodiment, when push module 142 sends a push message to consumer device 110 based on attribute tags, feedback data collection module 143 copies the attribute tags and maps the copied attribute tags to other consumer devices 110 around the consumer device 110 receiving the push message. Specifically, please refer to Figure 3, which illustrates tag sharing. Push module 142 of push server 140 sends push messages to consumer device 110a based on attribute tags. At this time, feedback data collection module 143 can detect other consumer devices 110b~110d around the device via Internet node 1201 connected to consumer device 110a. Next, if these consumer devices 110b-110d do not have associated attribute tags, the feedback data collection module 143 will copy the attribute tags used for the push notification and establish an association between the copied attribute tags and the consumer devices 110b-110d. Furthermore, the consumer device 110a will send the copied attribute tags to the consumer devices 110b-110d via the Internet node 1201. The consumer devices 110b-110d will then periodically send the copied attribute tags back to the push server 140 as the basis for the next push notification. It is worth noting that the Internet node 1201 in Figure 3 is an example using a Wi-Fi icon. However, this is not the only possibility. Internet node 1201 can be other networked nodes, such as base stations, routers, routers, etc., meaning that these consumer devices 110a-110d are located in similar areas. This method further expands the number of push targets and improves the effectiveness of push advertising. In addition, the push server 140 also includes a tag database module 144 suitable for storing and managing these attribute tags. The tag database module 144 can further categorize and statistically analyze these attribute tags based on their content (e.g., preferences and location). In one embodiment, each attribute tag also includes a weight value. The push module 142 selects attributes based on their weight values; attributes with higher weight values are more likely to be selected by the push module 142, and push messages are sent to the consumer device 110 based on the selection result. Attribute tags from different sources have different weight values. For example, attribute tags generated by the telecommunications operator's server 120 have the highest weight, and these attribute tags are mostly used to indicate regions. It is worth noting that the weight value of copied attribute tags is also copied from the original attribute tags, but the weight value of the copied attribute tags decreases over time. In other words, the further back in time the copied attribute tags were generated, the smaller their weight value will be. Taking the embodiment in Figure 3 as an example, when the attribute tags of consumer device 110a are copied and shared to consumer devices 110b-110d via Internet node 1201, at the moment of sharing, the weight values of the attribute tags in consumer devices 110b-110d are equivalent to the weight values of the attribute tags in consumer device 110a. However, as time passes, the weight values of the attribute tags in 110b-110d gradually decrease. This is because only at the moment the attribute tags are shared can it be confirmed that consumer devices 110b-110d and consumer device 110a are in a similar location. Over time, consumer devices 110b-110d, carried by their users, may gradually move away from consumer device 110a and to other locations. This causes the weight values of the attribute tags on consumer devices 110b-110d to decrease, preventing ineffective push notifications. Adjusting the weight values further improves the accuracy of push advertising. Referring to Figure 1B, the push management device 150 can connect to the push server 140, allowing the push manager to view these attribute tags and their statistical data through an interface. This enables the push manager to more effectively analyze consumer responses and adjust future push advertising strategies based on this feedback data. Furthermore, the push notification manager device 150 is also adapted to input at least one tag viewing request. When the tag database module 144 receives the tag viewing request, it displays statistical data for the corresponding attribute tag on the push notification manager device 150 based on the tag viewing request. The tag viewing request may, for example, specify a specific type of tag, such as selecting a specific preference or region attribute tag. After receiving the tag viewing request, the tag database module 144 can display the specified preference or region attribute tag and statistical count on the push notification manager device 150. In other words, after inputting the relevant conditions, the push notification manager can see how many consumers might receive the push notification message. Through this iterative process of push notifications and feedback data collection, a more detailed and accurate consumer profile can be gradually drawn. This not only increases the click-through rate of push ads but also further improves the overall effectiveness and accuracy of ad delivery. This data-driven approach allows the entire system to be continuously optimized and provides push notification administrators with a wider range of ad targeting options. The following describes the application scenario of the location-based web push notification system 100. Please refer to Figures 2A and 2B, which are schematic diagrams of system operation. First, the consumer uses their smartphone (consumer device 110) to browse a shopping website (web server 130) and registers/subscribes to a push notification service. Specifically, the smartphone (consumer device 110) obtains telecommunications network services through the telecommunications operator's server 120. That is, consumer device 110 uses network services provided by Chunghwa Telecom and connects to the web server 130 to browse the shopping website. At this time, the telecommunications operator's server 120 can obtain the location information of the consumer device 110. After the consumer registers/subscribes to the push notification service, the shopping website (web server 130) provides a list of subscribers to the telecommunications operator's server 120. The location acquisition module 141 of the push server 140 periodically exchanges data with the telecommunications operator's server 120, providing subscriber lists and location data to the push server 140, for example, once a month. Next, the push manager (advertiser) uses the push manager device 150 to set up a location-specific promotional push. For example, the push manager wants to push a promotional advertisement for a restaurant located in Zhongzheng District, so Zhongzheng District is selected as the target area (location-specific data). Then, the push manager device 150 inputs the advertisement's text and image (push command), and specifies the target area for the push (corresponding to location-specific data for Zhongzheng District). The push manager device 150 sends the location-specific data containing the target area (Zhongzheng District) and the push command to the push server 140. After receiving the location-specified data and push notification instructions, the push notification module 142 generates push notification messages based on the content of the instructions (restaurant offers). It then selects the appropriate push notification recipients based on the location-specified data, location information obtained from the telecommunications operator's server 120, and the subscriber list. Next, the push notification server 140, through the push notification module 142, sends the restaurant offer push notification message to consumer devices 110 located in the Zhongzheng District, promoting the restaurant to consumers near the restaurant. After the push notification message is sent, if a consumer clicks on the push notification message on their consumer device 110, the feedback data collection module 143 generates at least one attribute tag and associates this attribute tag with the consumer. In other words, the feedback data collection module 143 essentially records the consumer, marking the type of advertisement clicked and the location of the push notification message, such as the consumer's preference for food in Zhongzheng District. In this way, through multiple push notifications and consumer clicks, a consumer profile can be gradually drawn, including consumption preferences and frequently visited areas. These attribute tags can also be used by the push notification module 142 and the location acquisition module 141 for more accurate location determination, thereby enabling more precise location-based push notifications. For example, the original target area was based on administrative districts. With feedback from attribute tags, push notifications can be further refined to a smaller scope, such as targeting neighborhoods, streets, or business districts, enabling more precise ad delivery. In one embodiment, the push notification administrator device 150 can connect to the push notification server 140 and view these attribute tags and statistical data, allowing for further analysis. Furthermore, the push notification server 140 provides attribute tag selection and filtering display methods. By selecting preferred or regional attribute tags, the push notification server 140 can display the number of user devices with the corresponding attribute tags. In other words, push notification administrators can view the number of targets that can receive push notifications under different push conditions, thus evaluating the advertising effectiveness. The location-based web push notification system 100 of this invention can send highly targeted push notifications based on location information, which improves the targeting accuracy of advertisements and messages and enhances the overall effectiveness of push advertising. Furthermore, it obtains location information through telecommunications operators, enabling the acquisition of consumer location information even without GPS. The location-based web push notification system 100 also provides an interface for push notification administrators to input push notification commands, allowing administrators to easily set up and manage push notification activities. Furthermore, through push notifications and consumer behavior feedback, a more comprehensive consumer profile can be drawn, and this data can be used by push notification managers to evaluate the potential revenue of push notification advertising, thereby improving its effectiveness. The invention is described above, but it is not intended to limit the scope of the patent rights claimed herein. The scope of patent protection shall be determined by the appended patent application and its equivalent fields. Any modifications or refinements made by those skilled in the art, without departing from the spirit or scope of this patent, constitute equivalent changes or designs made under the spirit disclosed in this invention and should be included within the scope of the patent application below.

100: Location-based web push system 110, 110a~110d: Consumer devices 120: Telecom operator servers 1201: Internet nodes 130: Web servers 140: Push servers 141: Location acquisition module 142: Push module 143: Feedback data collection module 144: Tag database module 150: Push administrator device

Figures 1 and 1B illustrate the system architecture of the location-based webpage push system 100 of this invention. Figures 2A and 2B illustrate the system operation. Figure 3 illustrates tag sharing.

100: Location-based web page push system

110: Consumer Devices

120: Telecom Operator Servers

130: Web server

140: Push Server

150: Push notification administrator device

Claims (9)

A location-based web push system includes: a plurality of consumer devices; at least one telecommunications operator server, communicatively connected to the consumer devices, adapted to provide multiple location information, the location information corresponding to different consumer devices; a plurality of web servers connected to the telecommunications operator server; at least one push management device adapted to provide a push instruction, the push instruction including at least one location specification data; and a push server, communicatively connected to the telecommunications operator server and the push management device, and receiving the push instruction, the push server including: a location acquisition module adapted to obtain the location information from the telecommunications operator server; and a push module, generating at least one push message according to the push instruction, and transmitting the push message to the corresponding consumer device according to the location information; The push notification was sent to the consumer's device via a webpage push notification. The location-based web push system as described in claim 1, wherein the push server further includes a feedback data collection module that generates an attribute tag associated with the consumer device that clicked the push message if the push message is clicked on the consumer device. The location-based webpage push system as described in claim 2, wherein the push module is also adapted to send the push message to the consumer device based on the attribute tag. The location-based web push system as described in claim 2, wherein the push server further includes a tag database module adapted to store and manage the attribute tags. The location-based web push system as described in claim 4, wherein the push manager device is further adapted to connect to the push server and browse the attribute tag and at least one statistical data of the attribute tag. The location-based webpage push system as described in claim 5, wherein the push management device is further adapted to input at least one tag browsing request data, the tag database module is adapted to receive the tag browsing request data, and display the corresponding attribute tag and statistical data on the push management device according to the tag browsing request data. The location-based webpage push system as described in claim 3, wherein when the push module sends the push message to the consumer device based on the attribute tag, the feedback data collection module copies the attribute tag and maps the copied attribute tag to other consumer devices around the consumer device receiving the push message. The location-based webpage push system as described in claim 7, wherein the attribute tag further includes a weight value, and the push module is also adapted to send the push message to the consumer device according to the weight value of the attribute tag. The location-based webpage push system as described in claim 8, wherein the weight value of the copied attribute tag is copied from the original attribute tag, and the weight value of the copied attribute tag decreases over time.