TW201935362A

TW201935362A - Information pushing method, apparatus and device

Info

Publication number: TW201935362A
Application number: TW107145885A
Authority: TW
Inventors: 林炳文
Original assignee: 香港商阿里巴巴集團服務有限公司
Priority date: 2018-02-02
Filing date: 2018-12-19
Publication date: 2019-09-01
Also published as: CN108449378B; WO2019149058A1; TWI742332B; CN108449378A

Abstract

Disclosed in the embodiments of the present description are an information pushing method, apparatus and device. For a user needing service information pushing, a region where the user is located can be determined based on a user position, and a regional pushing control condition corresponding to the region is further determined, wherein the regional pushing control condition reflects a condition needing to be satisfied for pushing service information in the region. In this way, in conjunction with a historical pushing record of the user, more multi-dimensional pushing control can be performed on the service information needing to be pushed to the user.

Description

Information push method, device and equipment

本申請係關於電腦技術領域，尤其關於一種資訊推送方法、裝置及設備。This application relates to the field of computer technology, and in particular, to a method, device, and device for pushing information.

隨著資訊技術的發展和普及，業務提供商可以面向用戶主動推送相應的業務資訊，以使得用戶獲知相應的業務產品/服務。
目前，業務提供商在向用戶推送業務資訊的過程中，通常會針對其推送的業務資訊進行疲勞度控制，亦即，在指定的時段內，向同一用戶推送業務資訊的次數小於預設值，以便降低用戶對其接收到的業務資訊的疲勞感。現有技術中，業務提供商通常會基於最近一段時間向用戶的推送次數進行疲勞度控制。
基於現有技術，需要一種更為有效的資訊推送方式。With the development and popularization of information technology, service providers can actively push corresponding business information to users, so that users can learn about the corresponding business products / services.
At present, in the process of pushing service information to users, service providers usually perform fatigue control on the service information they push. In order to reduce the fatigue of users for the business information they receive. In the prior art, a service provider usually performs fatigue control based on the number of pushes to a user in a recent period of time.
Based on the existing technology, a more effective way of pushing information is needed.

本說明書實施例提供一種資訊推送方法、裝置及設備，用以提供一種更為有效地針對業務資訊進行推送的疲勞度控制方案。
本說明書實施例採用下述技術方案：
本說明書實施例提供一種資訊推送方法，包括：
確定用戶對應的用戶位置及針對所述用戶的歷史推送記錄；
根據所述用戶位置，確定所述用戶位置所對應的地區推送控制條件；
根據所述地區推送控制條件以及所述歷史推送記錄，向所述用戶推送業務資訊。
對應地，本說明書實施例還提供一種資訊推送裝置，包括：
基礎資訊確定模組，確定用戶對應的用戶位置及針對所述用戶的歷史推送記錄；
控制條件確定模組，根據所述用戶位置，確定所述用戶位置所對應的地區推送控制條件；
推送處理模組，根據所述地區推送控制條件以及所述歷史推送記錄，向所述用戶推送業務資訊。
對應地，本說明書實施例還提供一種資訊推送設備，包括：處理器、記憶體，其中：
所述記憶體，儲存資訊推送程式；
所述處理器，調用記憶體中儲存的資訊推送序，並執行：
確定用戶對應的用戶位置及針對所述用戶的歷史推送記錄；
根據所述用戶位置，確定所述用戶位置所對應的地區推送控制條件；
根據所述地區推送控制條件以及所述歷史推送記錄，向所述用戶推送業務資訊。
本說明書實施例採用的上述至少一個技術方案能夠達到以下有益效果：
對於需要進行業務資訊推送的用戶，可基於用戶位置確定出用戶所處的地區，並進一步確定出該地區所對應的地區推送控制條件，地區推送控制條件反映了該地區下對業務資訊進行推送所需滿足的條件。那麼，再結合用戶自身的歷史推送記錄，便可以針對需要推送給用戶的業務資訊進行更為多維度的推送控制。
採用上述的資訊推送，針對所在地區發生變化的用戶而言，也就能夠更為有效對其推送的業務資訊進行疲勞度控制，從而有利於提升用戶的業務體驗。The embodiments of the present specification provide a method, device, and device for pushing information, so as to provide a fatigue control scheme for pushing service information more effectively.
The embodiments of this specification adopt the following technical solutions:
This embodiment of the specification provides a method for pushing information, including:
Determining a user position corresponding to the user and a historical push record for the user;
Determining a regional push control condition corresponding to the user location according to the user location;
Push service information to the user according to the regional push control conditions and the historical push record.
Correspondingly, an embodiment of the present specification further provides an information pushing device, including:
The basic information determination module determines a user position corresponding to the user and a historical push record for the user;
A control condition determining module, according to the user position, determining a regional push control condition corresponding to the user position;
The push processing module pushes business information to the user according to the regional push control conditions and the historical push record.
Correspondingly, an embodiment of the present specification further provides an information pushing device, including: a processor and a memory, wherein:
The memory stores an information push program;
The processor calls the information push sequence stored in the memory and executes:
Determining a user position corresponding to the user and a historical push record for the user;
Determining a regional push control condition corresponding to the user location according to the user location;
Push service information to the user according to the regional push control conditions and the historical push record.
The at least one technical solution adopted in the embodiments of the present specification can achieve the following beneficial effects:
For users who need to push business information, they can determine the user's region based on the user's location, and further determine the regional push control conditions corresponding to the region. The regional push control conditions reflect the push of business information in the region Conditions to be met. Then, combined with the user's own historical push records, more multi-dimensional push control can be performed on the business information that needs to be pushed to the user.
With the above-mentioned information push, for users who have changed in their area, they can more effectively control the fatigue of their pushed business information, which is conducive to improving the user's business experience.

為使本申請的目的、技術方案和優點更加清楚，下面將結合本申請具體實施例及相應的附圖對本申請技術方案進行清楚、完整地描述。顯然，所描述的實施例僅是本申請一部分實施例，而不是全部的實施例。基於本申請中的實施例，本領域普通技術人員在沒有做出創造性勞動前提下所獲得的所有其他實施例，都屬於本申請保護的範圍。
在實際的業務場景中，對於用戶而言，過高頻率地接收到業務提供商推送的業務資訊，可能會影響用戶體驗。故業務提供商通常會針對其向用戶推送的業務資訊進行疲勞度控制(即，控制業務資訊在指定時長內的推送次數)。目前的疲勞度控制通常是基於歷史上最近一段時間內推送業務資訊的次數，實現對當前所需推送的業務資訊進行疲勞度控制。
但某些用戶可能會在不同的地區轉移，如：對於出境用戶，其所處國家可能會發生變化；又如：對於出差用戶，其所在城市可能會發生變化。而不同的地區通常又具有不同的業務資訊待推送，這樣一來，將會增加推送業務資訊的疲勞度控制的複雜度。目前僅採用業務消息的推送頻率已不能較好地滿足實際業務情況。
為此，本說明書實施例中提供一種資訊推送方法，用以在對業務資訊進行疲勞度控制的過程中，結合地理層級的推送控制規則，實現對所需推送的業務資訊進行多維度的管控，能夠滿足目前較為複雜的業務情況，並有利於提升用戶的業務體驗。
需要說明的是，在本說明書的一個或多個實施例中，所述的業務資訊可以是諸如：銀行卡的辦理優惠資訊、會員卡的折扣資訊、優惠券的介紹信息、線上/線下活動的推廣資訊或電影的宣傳資訊等等與業務服務或產品相關的宣傳資訊，這裡不再一一列舉。同時應理解，上述的業務資訊所採用的方式包括但不限於：短信(Short Message Service，SMS)、彩信、應用通知或系統消息等。這裡並不應構成對本申請的限定。
如圖1所示，為本說明書實施例中的業務推送方法所基於的架構示意圖。
在圖1中，所述的業務伺服器內設置有相應的業務資訊疲勞度控制規則(後續可稱為推送控制條件)，特別是針對不同地理層級的推送控制條件。通常而言，業務伺服器可以根據用戶所處的位置，結合相應的地理層級的推送控制條件，針對向用戶推送的業務資訊進行疲勞度控制。
一般來說，業務伺服器是業務提供商後臺的伺服器，這裡所述的業務提供商，可包括但不限於：商店、酒店、餐館、咖啡館、加油站、影院等商家，或者是電信營運商、網站等服務提供者。在本說明書中的部分實施例中，業務伺服器還可以是業務平臺的伺服器。換言之，各業務提供商的業務服務彙集在業務平臺上，用戶可以透過該業務平臺獲得不同業務提供商所提供的業務服務。
上述的業務伺服器可採用單一伺服器、集群式伺服器或分散式伺服器等架構，這裡不進行具體限定。
圖1中的用戶透過其自身所使用的終端，便可以接收到業務伺服器所推送的業務消息。所述的終端包括但不限於：智慧手機、智慧手錶、平板電腦或智慧穿戴設備等。並且，用戶所使用的終端通常還具備基於位置的服務(Location Based Service，LBS)，從而，業務伺服器可以透過終端來獲知用戶所處的位置。
基於上述如圖1所述的架構，以下將詳細說明本說明書實施例中所提供的技術方案。
本說明書實施例中提供一種業務推送方法，如圖2所述，具體包括以下步驟：
步驟S201：確定用戶位置以及針對用戶的歷史推送記錄。
在本說明書實施例中，用戶位置的獲得和確定，可以透過用戶所使用的終端的LBS實現，這裡便不再過多贅述。
針對用戶的歷史推送記錄，可認為是在當前時刻以前針對用戶所推送的業務資訊的記錄。作為本說明書實施例中的一種可行方式，所述的歷史推送記錄中可以包括諸如“用戶標識+推送記錄+推送時間”的內容。
其中，所述的用戶標識通常可以是用戶的帳戶/ID。在實際應用場景中，用戶的帳戶/ID通常與用戶使用的終端設備相綁定，這樣一來，透過上述的LBS確定出用戶所使用的終端位置(表徵了用戶所在的位置)後，便可以進一步基於終端的MAC位址、設備號等資訊，結合預先建立的綁定關係(用戶標識與終端之間的綁定關係)，進一步確定出用戶的帳戶/ID。從而，便可以基於用戶的帳戶/ID確定出用戶的歷史推送記錄。
當然，上述過程並不應構成對本申請的限定。
步驟S203：根據所述用戶位置，確定所述用戶位置所對應的地區推送控制條件。
在本說明書實施例中，針對不同的地理區域，設置了不同的地區推送控制條件。具體來說，這裡所述的地區推送控制條件主要是針對某一地區，在設定時間段內的推送次數的控制條件。如：針對地區A，3天內向用戶推送業務資訊的次數不超過2次。
一般來說，不同地區可以設置不同的地區推送控制條件，具體可根據該地區的業務需要進行設置，這裡並不應構成對本申請的限定。當然，多個地區設置統一的地區推送控制條件，也應涵蓋在本申請的範圍內。
步驟S205：根據所述地區推送控制條件以及所述歷史推送記錄，向所述用戶推送業務資訊。
在明確了當前地區的地區推送控制條件和用戶自身的歷史推送記錄後，便可以判斷出用戶位於當前的地區的情況下，業務伺服器是否可以向該用戶推送相應的業務資訊。可見，對於業務資訊推送的控制條件，不再僅限於推送的頻率，而是可以根據用戶所在的地區進行控制。
透過上述步驟，對於需要進行業務資訊推送的用戶，可基於用戶位置確定出用戶所處的地區，並進一步確定出該地區所對應的地區推送控制條件，地區推送控制條件反映了該地區下對業務資訊進行推送所需滿足的條件。那麼，再結合用戶自身的歷史推送記錄，便可以針對需要推送給用戶的業務資訊進行更為多維度的推送控制。
採用上述的資訊推送，針對所在地區發生變化的用戶而言，也就能夠更為有效對其推送的業務資訊進行疲勞度控制，從而有利於提升用戶的業務體驗。
對於上述方法而言，其執行主體可以是業務伺服器，也可以是電信營運商的資訊推送設備(並未在圖1的架構中示出，可以理解地，電信營運商的資訊推送設備通常用於以短信/彩信等方式向用戶推送業務資訊)，並且，在執行上述步驟的過程中，執行主體可以發生變化，例如：可由業務伺服器執行上述步驟S201、203，再由電信營運商的資訊推送設備執行上述步驟S205。當然，具體將根據實際應用的需要進行確定，這裡並不構成對本申請的限定。
針對上述方法需要說明的是，在實際應用場景中，可以按照不同的地理層級來劃分相應的地區。這裡所述的地理層級，可認為是在地理上按照國家、省/州、市、商圈等劃分的層級。那麼，基於地理層級所劃分得到的不同地區，可以是諸如：XX國家、XX省/州、XX市、XX商圈等。當然，通常會根據業務需要來劃分不同地理層級的地區。
進而，可針對上述不同的地區設置相應的地區推送控制條件。換言之，前述方法中，根據所述用戶位置，確定所述用戶位置所對應的地區推送控制條件的過程具體可以包括：確定所述用戶位置所屬的地區，將預先針對所述地區設置的地區推送控制條件，確定為所述用戶位置所對應的地區推送控制條件。
如前所述，在本說明書實施例中，地區推送控制條件主要是針對該地區設置的在指定時長內推送業務資訊的次數的條件。那麼，預先針對地區設置地區推送控制條件，具體可包括：針對任一地區，設置控制時長，並在所述控制時長內設置推送次數閾值，將在控制時長內設置的推送次數閾值確定為所述地區對應的地區推送控制條件。
作為本說明書實施例中的一種方式，在地理層級上具有所屬關係的不同地區，可以設置統一的地區推送控制條件。例如：
地區1：中國；地區2：浙江省；地區3：杭州市
上述三個地區在地理層級上具有歸屬關係，假設針對這三個地區所設置的地區推送控制條件均為“3天推送1次”。那麼，假設用戶A位於杭州市，針對該用戶A推送業務資訊時，則需要分別滿足上述的三個地區推送控制條件。具體地，在該示例中的具體執行流程可如圖3所示，包括以下步驟：
步驟S301：獲取用戶A的歷史推送記錄。
步驟S303：基於用戶A的歷史推送記錄，判斷在中國地區3天內向用戶A推送業務資訊的次數是否大於或等於1次，若是，則執行步驟S303；否則，則執行步驟S305。
步驟S305：基於用戶A的歷史推送記錄，判斷在浙江省地區3天內向用戶A推送業務資訊的次數是否大於或等於1次，若是，則執行步驟S303；否則，則執行步驟S307。
步驟S307：基於用戶A的歷史推送記錄，判斷在杭州市地區3天內向用戶A推送業務資訊的次數是否大於或等於1次，若是，則執行步驟S303；否則，則執行步驟S309。
步驟S309：向用戶A推送業務資訊。
當然，作為本說明書實施例中的另一種方式，在地理層級上具有所屬關係的不同地區，可以設置不同的地區推送控制條件。仍沿用上例中的地區，那麼，按照地理層級關係，地區推送控制條件可以分別是：
中國的地區推送控制條件為：5天推送1次；
浙江省的地區推送控制條件為：3天推送1次；
杭州市的地區推送控制條件為：2天推送1次。
基於上述地區推送控制條件，在實際執行時，與圖3所示的過程相類似，這裡便不再過多贅述。
當然，上述兩個示例僅是為了更為直觀地說明本申請中資訊推送方法的實際執行流程，其中地區推送控制條件的設置也不限於此，具體可根據實際應用的需要進行確定，這裡並不應構成對本申請的限定。
此外，除了針對不同的地區設置相應的地區推送控制條件以外，還可以針對需要進行推送的業務內容設置相應的控制條件。也就是說，對於相同的業務內容，可以控制其向用戶推送的頻率或次數。一般來說，對於業務內容的控制條件適用於不同的地區，所以，在本說明書的部分實施例中，可將針對業務內容的控制條件視作針對各個地區的地區推送控制條件。亦即，預先針對地區設置地區推送控制條件，具體可包括：針對每一類型的業務內容，設置控制時長，並在所述控制時長內設置推送次數閾值，將每一類型的業務內容在控制時長內設置的推送次數閾值，確定為各地區對應的地區推送控制條件。這裡並不構成對本申請的限定。
由此，便可以根據上述的推送控制條件來決定是否需要向用戶推送相應的業務資訊。亦即，根據所述地區推送控制條件以及所述歷史推送記錄，向所述用戶推送業務資訊，具體可如圖4所示，包括以下步驟：
步驟S401：確定用戶位置所屬的地區，以及所需推送的業務內容。
步驟S403：針對用戶位置所屬的地區，以及所需推送的業務內容，判斷在指定時長內已向用戶推送的歷史業務資訊是否超過設置的推送次數閾值；若是，則執行步驟S405，否則，則執行步驟S407。
步驟S405：不向所述用戶推送業務資訊。
步驟S407：向所述用戶推送業務資訊。
在本說明書的一種可行實施例中，當向用戶推送了業務資訊之後，業務伺服器還會進行記錄，以便於重置前述的地區推送控制條件。具體而言，記錄的結構可以採用如下形式：
用戶標識+地區標識+推送時間，或者，用戶標識+內容標識+推送時間
其中，如前所述，用戶標識可以是用戶帳戶/ID等。
地區標識可以是地區的名稱、編號或簡稱等，諸如：中國(CN)、浙江省(浙)、杭州市(HZ)。當然，地區標識可能採用其他的編碼形式，這裡不應作為對本申請的限定。
內容標識通常是業務內容的標識，具體可以包括業務類型編號、業務序號、服務/產品名稱、業務提供商名稱或其組合。同樣，這裡也不應作為對本申請的限定。
舉例說明：延續前述示例，假設相應的業務伺服器向用戶A推送了某業務資訊，推送的時間為2018年02月01日-10:01，推送該業務資訊時，用戶A位於杭州市，那麼，業務伺服器所生成的推送記錄可以為：
UserA(用戶標識)-HZ(地區標識)-20180201-10:01(推送時間)
值得注意的是，由於地區“杭州市”歸屬於地區“浙江省”，而地區“浙江省”又歸屬於地區“中國”，所以，如果杭州市的地區推送控制條件重置，相應地，浙江省和中國的地區推送控制條件也將重置。換言之，業務伺服器還會生成以下推送記錄：
UserA-浙-20180201-10:01，以及，UserA-CN-20180201-10:01。
並且，在進行記錄後，業務伺服器可以重置上述地區推送控制條件，換言之，上述的地區推送控制條件可以在2018年02月01日-10:01這一時刻重新計時。
從上述的內容可見，針對疲勞度控制而言，可以採用劃分地區的方式設置不同地理層級的推送控制條件，不同地理層級的推送控制條件之間相互並不影響。並且，儲存的推送記錄更為多樣，通常基於不同的地理層級生成並儲存為多條記錄，即使其中某條記錄遺失或失效，也可以參考其他各條記錄。
以上為本說明書實施例提供的資訊推送方法，基於同樣的思路，本說明書實施例還提供相應的資訊推送裝置。
具體而言，本說明書實施例中所提供的資訊推送裝置如圖5所示，所述裝置包括：
基礎資訊確定模組501，確定用戶對應的用戶位置及針對所述用戶的歷史推送記錄；
控制條件確定模組502，根據所述用戶位置，確定所述用戶位置所對應的地區推送控制條件；
推送處理模組503，根據所述地區推送控制條件以及所述歷史推送記錄，向所述用戶推送業務資訊。
進一步地，所述基礎資訊確定模組501，透過基於位置服務確定用戶所使用的終端位置，作為用戶位置，根據預先與所述終端綁定的用戶標識，在已儲存的歷史推送記錄中，確定所述用戶的歷史推送記錄。
進一步地，所述控制條件確定模組502，確定所述用戶位置所屬的地區，將預先針對所述地區設置的地區推送控制條件，確定為所述用戶位置所對應的地區推送控制條件。
進一步地，所述控制條件確定模組502，針對任一地區，設置控制時長，並在所述控制時長內設置推送次數閾值，將在控制時長內設置的推送次數閾值確定為所述地區對應的地區推送控制條件。
進一步地，所述控制條件確定模組502，針對每一類型的業務內容，設置控制時長，並在所述控制時長內設置推送次數閾值，將每一類型的業務內容在控制時長內設置的推送次數閾值，確定為各地區對應的地區推送控制條件。
進一步地，所述推送處理模組503，針對用戶位置所屬的地區，以及所需推送的業務內容，判斷在指定時長內已向用戶推送的歷史業務資訊是否超過設置的推送次數閾值，若是，則不向所述用戶推送業務資訊；否則，則向所述用戶推送業務資訊。
所述裝置還包括：記錄生成模組504，確定所述用戶的用戶標識、地區標識以及推送時間，根據所述用戶標識、地區標識以及推送時間，生成推送記錄。
所述裝置還包括505：條件重置模組，重置所述地區推送控制條件。
基於圖5所示的裝置，在實際應用中可由實體的設備(如：終端設備)所實現，具體而言，該設備包括：處理器、記憶體，其中，
所述記憶體，儲存資訊推送程式；
所述處理器，調用記憶體中儲存的資訊推送序，並執行：
確定用戶對應的用戶位置及針對所述用戶的歷史推送記錄；
根據所述用戶位置，確定所述用戶位置所對應的地區推送控制條件；
根據所述地區推送控制條件以及所述歷史推送記錄，向所述用戶推送業務資訊。
本說明書中的各個實施例均採用遞進的方式描述，各個實施例之間相同相似的部分互相參見即可，每個實施例重點說明的都是與其他實施例的不同之處。尤其，對於裝置、設備和媒體類實施例而言，由於其基本相似於方法實施例，所以描述的比較簡單，相關之處參見方法實施例的部分說明即可，這裡就不再一一贅述。
至此，已經對本主題的特定實施例進行了描述。其它實施例在所附申請專利範圍的範圍內。在一些情況下，在申請專利範圍中記載的動作可以按照不同的順序來執行並且仍然可以實現期望的結果。另外，在附圖中描繪的過程不一定要求示出的特定順序或者連續順序，以實現期望的結果。在某些實施方式中，多工處理和並行處理可以是有利的。
在20世紀90年代，對於一個技術的改進可以很明顯地區分是硬體上的改進(例如，對二極體、電晶體、開關等電路結構的改進)還是軟體上的改進(對於方法流程的改進)。然而，隨著技術的發展，當今的很多方法流程的改進已經可以視為硬體電路結構的直接改進。設計人員幾乎都透過將改進的方法流程程式設計到硬體電路中來得到相應的硬體電路結構。因此，不能說一個方法流程的改進就不能用硬體實體模組來實現。例如，可程式設計邏輯器件(Programmable Logic Device, PLD)(例如現場可程式設計閘陣列(Field Programmable Gate Array，FPGA))就是這樣一種積體電路，其邏輯功能由用戶對器件程式設計來確定。由設計人員自行程式設計來把一個數位系統“集成”在一片PLD上，而不需要請晶片製造廠商來設計和製作專用的積體電路晶片。而且，如今，取代手工地製作積體電路晶片，這種程式設計也多半改用“邏輯編譯器(logic compiler)”軟體來實現，它與程式開發撰寫時所用的軟體編譯器相類似，而要編譯之前的原始代碼也得用特定的程式設計語言來撰寫，此稱之為硬體描述語言(Hardware Description Language，HDL)，而HDL也並非僅有一種，而是有許多種，如ABEL
(Advanced Boolean Expression Language)、AHDL(Altera Hardware Description Language)、Confluence、CUPL(Cornell University Programming Language)、HDCal、JHDL(Java Hardware Description Language)、Lava、Lola、MyHDL、PALASM、RHDL(Ruby Hardware Description Language)等，目前最普遍使用的是VHDL(Very-High-Speed Integrated Circuit Hardware Description Language)與Verilog。本領域技術人員也應該清楚，只需要將方法流程用上述幾種硬體描述語言稍作邏輯程式設計並程式設計到積體電路中，就可以很容易得到實現該邏輯方法流程的硬體電路。
控制器可以按任何適當的方式實現，例如，控制器可以採取例如微處理器或處理器以及儲存可由該(微)處理器執行的電腦可讀程式碼(例如軟體或韌體)的電腦可讀媒體、邏輯閘、開關、專用積體電路(Application Specific Integrated Circuit，ASIC)、可程式設計邏輯控制器和嵌入微控制器的形式，控制器的例子包括但不限於以下微控制器：ARC 625D、Atmel AT91SAM、Microchip PIC18F26K20 以及Silicone Labs C8051F320，記憶體控制器還可以被實現為記憶體的控制邏輯的一部分。本領域技術人員也知道，除了以純電腦可讀程式碼方式實現控制器以外，完全可以透過將方法步驟進行邏輯程式設計來使得控制器以邏輯閘、開關、專用積體電路、可程式設計邏輯控制器和嵌入微控制器等的形式來實現相同功能。因此這種控制器可以被認為是一種硬體部件，而對其內包括的用於實現各種功能的裝置也可以視為硬體部件內的結構。或者甚至，可以將用於實現各種功能的裝置視為既可以是實現方法的軟體模組又可以是硬體部件內的結構。
上述實施例闡明的系統、裝置、模組或單元，具體可以由電腦晶片或實體實現，或者由具有某種功能的產品來實現。一種典型的實現設備為電腦。具體的，電腦例如可以為個人電腦、膝上型電腦、蜂窩電話、相機電話、智慧型電話、個人數位助理、媒體播放機、導航設備、電子郵件設備、遊戲控制台、平板電腦、可穿戴設備或者這些設備中的任何設備的組合。
為了描述的方便，描述以上裝置時以功能分為各種單元分別描述。當然，在實施本申請時可以把各單元的功能在同一個或多個軟體和/或硬體中實現。
本領域內的技術人員應明白，本發明的實施例可提供為方法、系統、或電腦程式產品。因此，本發明可採用完全硬體實施例、完全軟體實施例、或結合軟體和硬體方面的實施例的形式。而且，本發明可採用在一個或多個其中包含有電腦可用程式碼的電腦可用儲存媒體(包括但不限於磁碟記憶體、CD-ROM、光學記憶體等)上實施的電腦程式產品的形式。
本發明是參照根據本發明實施例的方法、設備(系統)、和電腦程式產品的流程圖和/或方框圖來描述的。應理解可由電腦程式指令實現流程圖和/或方框圖中的每一流程和/或方框、以及流程圖和/或方框圖中的流程和/或方框的結合。可提供這些電腦程式指令到通用電腦、專用電腦、嵌入式處理機或其他可程式設計資料處理設備的處理器以產生一個機器，使得透過電腦或其他可程式設計資料處理設備的處理器執行的指令產生用於實現在流程圖一個流程或多個流程和/或方框圖一個方框或多個方框中指定的功能的裝置。
這些電腦程式指令也可儲存在能引導電腦或其他可程式設計資料處理設備以特定方式工作的電腦可讀記憶體中，使得儲存在該電腦可讀記憶體中的指令產生包括指令裝置的製造品，該指令裝置實現在流程圖一個流程或多個流程和/或方框圖一個方框或多個方框中指定的功能。
這些電腦程式指令也可裝載到電腦或其他可程式設計資料處理設備上，使得在電腦或其他可程式設計設備上執行一系列操作步驟以產生電腦實現的處理，從而在電腦或其他可程式設計設備上執行的指令提供用於實現在流程圖一個流程或多個流程和/或方框圖一個方框或多個方框中指定的功能的步驟。
在一個典型的配置中，計算設備包括一個或多個處理器(CPU)、輸入/輸出介面、網路介面和記憶體。
記憶體可能包括電腦可讀媒體中的非永久性記憶體，隨機存取記憶體(RAM)和/或非易失性記憶體等形式，如唯讀記憶體(ROM)或快閃記憶體(flash RAM)。記憶體是電腦可讀媒體的示例。
電腦可讀媒體包括永久性和非永久性、可移動和非可移動媒體可以由任何方法或技術來實現資訊儲存。資訊可以是電腦可讀指令、資料結構、程式的模組或其他資料。電腦的儲存媒體的例子包括，但不限於相變記憶體(PRAM)、靜態隨機存取記憶體(SRAM)、動態隨機存取記憶體(DRAM)、其他類型的隨機存取記憶體(RAM)、唯讀記憶體(ROM)、電可擦除可程式設計唯讀記憶體(EEPROM)、快閃記憶體或其他記憶體技術、唯讀光碟唯讀記憶體(CD-ROM)、數位多功能光碟(DVD)或其他光學儲存、磁盒式磁帶，磁帶磁片儲存或其他磁性存放裝置或任何其他非傳輸媒體，可用於儲存可以被計算設備訪問的資訊。按照本文中的界定，電腦可讀媒體不包括暫存電腦可讀媒體(transitory media)，如調製的資料信號和載波。
還需要說明的是，術語“包括”、“包含”或者其任何其他變體意在涵蓋非排他性的包含，從而使得包括一系列要素的過程、方法、商品或者設備不僅包括那些要素，而且還包括沒有明確列出的其他要素，或者是還包括為這種過程、方法、商品或者設備所固有的要素。在沒有更多限制的情況下，由語句“包括一個……”限定的要素，並不排除在包括所述要素的過程、方法、商品或者設備中還存在另外的相同要素。
本領域技術人員應明白，本申請的實施例可提供為方法、系統或電腦程式產品。因此，本申請可採用完全硬體實施例、完全軟體實施例或結合軟體和硬體方面的實施例的形式。而且，本申請可採用在一個或多個其中包含有電腦可用程式碼的電腦可用儲存媒體(包括但不限於磁碟記憶體、CD-ROM、光學記憶體等)上實施的電腦程式產品的形式。
本申請可以在由電腦執行的電腦可執行指令的一般上下文中描述，例如程式模組。一般地，程式模組包括執行特定事務或實現特定抽象資料類型的常式、程式、物件、元件、資料結構等等。也可以在分散式運算環境中實踐本申請，在這些分散式運算環境中，由透過通信網路而被連接的遠端處理設備來執行事務。在分散式運算環境中，程式模組可以位於包括存放裝置在內的本地和遠端電腦儲存媒體中。
本說明書中的各個實施例均採用遞進的方式描述，各個實施例之間相同相似的部分互相參見即可，每個實施例重點說明的都是與其他實施例的不同之處。尤其，對於系統實施例而言，由於其基本相似於方法實施例，所以描述的比較簡單，相關之處參見方法實施例的部分說明即可。
以上所述僅為本申請的實施例而已，並不用於限制本申請。對於本領域技術人員來說，本申請可以有各種更改和變化。凡在本申請的精神和原理之內所作的任何修改、等同替換、改進等，均應包含在本申請的申請專利範圍的範圍之內。In order to make the purpose, technical solution, and advantages of the present application clearer, the technical solution of the present application will be clearly and completely described in combination with specific embodiments of the present application and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of the present application, but not all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by a person of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.
In an actual business scenario, for users, receiving service information pushed by a service provider too frequently may affect the user experience. Therefore, service providers usually perform fatigue control on the service information that they push to users (that is, control the number of times the service information is pushed within a specified period of time). The current fatigue control is usually based on the number of times business information has been pushed in the past period of time in history to achieve fatigue control of the business information currently required to be pushed.
However, some users may be transferred in different regions. For example, for outbound users, the country where they are located may change; for example, for travelling users, the city where they are located may change. And different regions usually have different business information to be pushed. In this way, the complexity of fatigue control for pushing business information will be increased. At present, using only the push frequency of business messages can no longer satisfy the actual business situation.
To this end, an embodiment of the present specification provides an information push method for implementing a multi-dimensional management and control of the business information to be pushed in combination with geographic-level push control rules during the fatigue control of business information. It can meet the current more complex business conditions and is conducive to improving the user's business experience.
It should be noted that, in one or more embodiments of the present specification, the business information may be such as: bank card application discount information, membership card discount information, coupon introduction information, online / offline activities Promotion information related to business services or products, such as promotion information for movies or movie promotion information, will not be listed here one by one. At the same time, it should be understood that the methods used for the above business information include, but are not limited to: short message service (SMS), multimedia message, application notification or system message. This should not constitute a limitation on this application.
As shown in FIG. 1, it is a schematic diagram of an architecture on which a service pushing method according to an embodiment of the present specification is based.
In FIG. 1, a corresponding business information fatigue control rule (hereinafter referred to as a push control condition) is set in the service server, especially for push control conditions of different geographic levels. Generally speaking, the service server can perform fatigue control on the business information pushed to the user according to the location of the user and the corresponding geographic-level push control conditions.
Generally speaking, the service server is the server of the service provider's backend. The service provider described here may include but is not limited to: shops, hotels, restaurants, cafes, gas stations, cinemas and other businesses, or telecommunications operations Service providers such as vendors, websites. In some embodiments in this specification, the service server may also be a server of a service platform. In other words, the business services of various service providers are aggregated on a business platform, and users can obtain business services provided by different service providers through the business platform.
The above-mentioned business server may adopt a structure such as a single server, a clustered server, or a distributed server, which is not specifically limited here.
The user in FIG. 1 can receive the service message pushed by the service server through the terminal used by himself. The terminal includes, but is not limited to, a smart phone, a smart watch, a tablet computer, or a smart wearable device. In addition, the terminal used by the user usually also has a Location Based Service (LBS), so that the service server can know the location of the user through the terminal.
Based on the above-mentioned architecture shown in FIG. 1, the technical solutions provided in the embodiments of the present specification will be described in detail below.
An embodiment of this specification provides a method for pushing a service. As shown in FIG. 2, the method specifically includes the following steps:
Step S201: Determine a user position and a historical push record for the user.
In the embodiment of the present specification, the acquisition and determination of the user's location can be implemented through the LBS of the terminal used by the user, which will not be repeated here.
The historical push records for users can be considered as records of business information pushed for users before the current moment. As a feasible way in the embodiment of the present specification, the historical push record may include content such as “user identification + push record + push time”.
Wherein, the user identification may generally be a user's account / ID. In an actual application scenario, the user's account / ID is usually bound to the terminal device used by the user. In this way, after determining the terminal location (characterizing the user's location) used by the user through the above LBS, Based on the information such as the MAC address and device number of the terminal, and combined with the pre-established binding relationship (the binding relationship between the user ID and the terminal), the user's account / ID is further determined. Therefore, the user's historical push record can be determined based on the user's account / ID.
Of course, the above process should not constitute a limitation on this application.
Step S203: Determine a regional push control condition corresponding to the user location according to the user location.
In the embodiment of the present specification, different regional push control conditions are set for different geographic regions. Specifically, the regional push control conditions described herein are mainly control conditions for the number of pushes within a set period of time for a certain region. For example, for area A, the number of times business information is pushed to users within 3 days.
In general, different regions can set different regional push control conditions, which can be specifically set according to the business needs of the region, which should not constitute a limitation on this application. Of course, setting uniform regional push control conditions in multiple regions should also be covered within the scope of this application.
Step S205: Push service information to the user according to the regional push control conditions and the historical push record.
After clarifying the regional push control conditions of the current region and the user's own historical push records, it can be determined whether the service server can push the corresponding business information to the user if the user is located in the current region. It can be seen that the control conditions for pushing business information are no longer limited to the frequency of pushing, but can be controlled according to the region where the user is located.
Through the above steps, for users who need to push business information, the user's region can be determined based on the user's location, and the regional push control conditions corresponding to the region are further determined. The regional push control conditions reflect the business of the region. The conditions that need to be met for information to be pushed. Then, combined with the user's own historical push records, more multi-dimensional push control can be performed on the business information that needs to be pushed to the user.
With the above-mentioned information push, for users who have changed in their area, they can more effectively control the fatigue of their pushed business information, which is conducive to improving the user's business experience.
For the above method, the execution subject can be a service server or a telecom operator's information push device (not shown in the architecture of Figure 1. It is understandable that the telecom operator's information push device is usually used (E.g., sending service information to users by SMS / MMS, etc.), and in the process of performing the above steps, the executing subject may change, for example, the service server may perform the above steps S201 and 203, and then the information of the telecommunications operator The pushing device performs the above step S205. Of course, it will be specifically determined according to the needs of practical applications, and this does not constitute a limitation on this application.
For the above method, it needs to be explained that, in an actual application scenario, corresponding regions can be divided according to different geographic levels. The geographic level described here can be considered as a level divided geographically by country, province / state, city, business district, etc. Then, the different regions divided based on the geographic level can be, for example, XX country, XX province / state, XX city, XX business district, etc. Of course, different geographic levels are usually divided according to business needs.
Furthermore, corresponding regional push control conditions can be set for the different regions mentioned above. In other words, in the foregoing method, according to the user location, a process of determining a region push control condition corresponding to the user location may specifically include: determining a region to which the user location belongs, and pushing a region control set in advance for the region The condition is determined as a region push control condition corresponding to the user location.
As mentioned above, in the embodiment of the present specification, the regional push control condition is mainly a condition for the number of times the service information is pushed within a specified period of time set in the region. Then, setting a regional push control condition for a region in advance may specifically include: setting a control duration for any region, and setting a push number threshold within the control duration, and determining the push number threshold set within the control duration Push control conditions for the region corresponding to the region.
As a method in the embodiment of the present specification, different regions having a belonging relationship at a geographic level may set unified regional push control conditions. E.g:
Region 1: China; Region 2: Zhejiang Province; Region 3: Hangzhou The above three regions have attribution relationship at the geographic level. It is assumed that the regional push control conditions set for these three regions are all “Push once every 3 days” . Then, suppose that user A is located in Hangzhou, and when pushing service information for this user A, it is necessary to satisfy the above three regional push control conditions, respectively. Specifically, the specific execution process in this example can be shown in FIG. 3 and includes the following steps:
Step S301: Obtain a historical push record of user A.
Step S303: Based on the historical push record of the user A, determine whether the number of times the business information is pushed to the user A within 3 days in China is greater than or equal to 1; if so, execute step S303; otherwise, execute step S305.
Step S305: Based on the historical push record of user A, determine whether the number of times business information is pushed to user A within three days in Zhejiang Province is greater than or equal to one. If so, step S303 is performed; otherwise, step S307 is performed.
Step S307: Based on the historical push record of the user A, determine whether the number of times the business information is pushed to the user A within 3 days in Hangzhou area is greater than or equal to 1; if so, execute step S303; otherwise, execute step S309.
Step S309: Push service information to the user A.
Of course, as another way in the embodiment of the present specification, different regions having a belonging relationship at the geographic level may set different region push control conditions. The areas in the above example are still used. Then, according to the geographical hierarchy, the regional push control conditions can be:
Regional push control conditions in China are: push once every 5 days;
The regional push control conditions in Zhejiang Province are: push once every 3 days;
The regional push control conditions in Hangzhou are: Push once every 2 days.
Based on the above-mentioned regional push control conditions, the actual implementation is similar to the process shown in FIG. 3, and is not repeated here.
Of course, the above two examples are just to more intuitively explain the actual execution process of the information push method in this application, and the setting of the regional push control conditions is not limited to this, and can be determined according to the actual application needs. Should constitute a limitation on this application.
In addition, in addition to setting corresponding regional push control conditions for different regions, you can also set corresponding control conditions for business content that needs to be pushed. That is, for the same service content, you can control the frequency or number of times it is pushed to users. Generally, the control conditions for business content are applicable to different regions. Therefore, in some embodiments of the present specification, the control conditions for business content may be regarded as the region-specific push control conditions. That is, setting the regional push control conditions for the region in advance may specifically include: setting a control duration for each type of business content, and setting a threshold for the number of pushes within the control duration to set each type of business content in The threshold of the number of pushes set within the control duration is determined as a regional push control condition corresponding to each region. This does not constitute a limitation on this application.
Therefore, it can be determined whether the corresponding service information needs to be pushed to the user according to the above-mentioned push control conditions. That is, pushing the business information to the user according to the regional push control conditions and the historical push record, as shown in FIG. 4, and includes the following steps:
Step S401: Determine the region to which the user's location belongs, and the service content to be pushed.
Step S403: Determine whether the historical service information that has been pushed to the user within a specified time period exceeds the set number of pushes for the region to which the user's location belongs and the service content to be pushed; if yes, perform step S405, otherwise, Go to step S407.
Step S405: Do not push service information to the user.
Step S407: Push service information to the user.
In a feasible embodiment of the present specification, after the service information is pushed to the user, the service server also records to facilitate resetting the aforementioned regional push control conditions. Specifically, the structure of the record can take the following form:
User ID + region ID + push time, or user ID + content ID + push time Among them, as described above, the user ID may be a user account / ID and the like.
The area identifier can be the name, number, or short name of the area, such as: China (CN), Zhejiang Province (Zhejiang), Hangzhou (HZ). Of course, the area identification may adopt other coding forms, which should not be used as a limitation on this application.
The content identifier is usually an identifier of the service content, and may specifically include a service type number, a service serial number, a service / product name, a service provider name, or a combination thereof. Similarly, this should not be used as a limitation on this application.
Example: Continuing the previous example, suppose that the corresponding service server pushes certain business information to User A, and the time is from February 01, 2018 to 10:01. When pushing the business information, User A is located in Hangzhou, then The push record generated by the business server can be:
UserA (user identification)-HZ (region identification) -20180201-10: 01 (push time)
It is worth noting that, because the area "Hangzhou" belongs to the area "Zhejiang Province" and the area "Zhejiang Province" belongs to the area "China", so if the regional push control conditions in Hangzhou reset, correspondingly, Zhejiang Provincial and Chinese regional push control conditions will also be reset. In other words, the business server also generates the following push records:
UserA-Zhejiang-20180201-10: 01, and UserA-CN-20180201-10: 01.
In addition, after performing the recording, the service server can reset the above-mentioned regional push control conditions, in other words, the above-mentioned regional push control conditions can be retimed from February 01, 2018 to 10:01.
From the above, it can be seen that, for the fatigue control, the push control conditions at different geographic levels can be set by dividing the regions, and the push control conditions at different geographic levels do not affect each other. In addition, the stored push records are more diverse, and are usually generated and stored as multiple records based on different geographic levels. Even if one of the records is lost or invalid, you can refer to other records.
The above is the information pushing method provided by the embodiment of the present specification. Based on the same thinking, the embodiment of the present specification also provides a corresponding information pushing device.
Specifically, the information pushing device provided in the embodiment of this specification is shown in FIG. 5, and the device includes:
The basic information determining module 501 determines a user position corresponding to a user and a historical push record for the user;
A control condition determining module 502, according to the user location, determining a region push control condition corresponding to the user location;
The push processing module 503 pushes service information to the user according to the regional push control conditions and the historical push record.
Further, the basic information determination module 501 determines the location of the terminal used by the user through location-based services as the location of the user, and determines it from the stored historical push records according to the user identifier that is bound to the terminal in advance. A history push record of the user.
Further, the control condition determination module 502 determines an area to which the user location belongs, and determines the area push control condition set for the area in advance, and determines the area push control condition corresponding to the user location.
Further, the control condition determination module 502 sets a control duration for any region, sets a threshold for the number of pushes within the control duration, and determines the threshold for the number of pushes set within the control duration as the Region push control conditions corresponding to the region.
Further, the control condition determination module 502 sets a control duration for each type of business content, and sets a threshold for the number of pushes within the control duration, so that each type of business content is within the control duration. The set push frequency threshold is determined as the regional push control condition corresponding to each region.
Further, the push processing module 503 determines whether the historical business information that has been pushed to the user within a specified time period exceeds the set number of pushes for the region to which the user's location belongs and the service content to be pushed, and if so, Then no business information is pushed to the user; otherwise, business information is pushed to the user.
The device further includes a record generation module 504 that determines a user identifier, a region identifier, and a push time of the user, and generates a push record according to the user identifier, the region identifier, and the push time.
The device further includes 505: a condition resetting module that resets the area push control conditions.
Based on the apparatus shown in FIG. 5, in actual applications, it can be implemented by a physical device (such as a terminal device). Specifically, the device includes: a processor and a memory, where:
The memory stores an information push program;
The processor calls the information push sequence stored in the memory and executes:
Determining a user position corresponding to the user and a historical push record for the user;
Determining a regional push control condition corresponding to the user location according to the user location;
Push service information to the user according to the regional push control conditions and the historical push record.
Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the various embodiments can be referred to each other. Each embodiment focuses on the differences from other embodiments. In particular, for the device, device, and media embodiments, since they are basically similar to the method embodiments, the description is relatively simple. For the relevant parts, refer to the description of the method embodiments, and they will not be repeated here.
So far, specific embodiments of the present subject matter have been described. Other embodiments are within the scope of the appended patent applications. In some cases, the actions described in the scope of the patent application can be performed in a different order and still achieve the desired result. In addition, the processes depicted in the figures do not necessarily require the particular order shown or sequential order to achieve the desired result. In certain embodiments, multiplexing and parallel processing may be advantageous.
In the 1990s, for a technical improvement, it can be clearly distinguished whether it is an improvement in hardware (for example, the improvement of circuit structures such as diodes, transistors, switches, etc.) or an improvement in software (for method and process Improve). However, with the development of technology, the improvement of many methods and processes can be regarded as a direct improvement of the hardware circuit structure. Designers almost always get the corresponding hardware circuit structure by designing the improved method flow program into the hardware circuit. Therefore, it cannot be said that the improvement of a method flow cannot be realized by a hardware entity module. For example, a programmable logic device (Programmable Logic Device, PLD) (such as a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic function is determined by the user's programming of the device. Designers can program their own digital system to "integrate" on a PLD without having to ask a chip manufacturer to design and produce a dedicated integrated circuit chip. Moreover, today, instead of making integrated circuit chips manually, this programming is mostly implemented using "logic compiler" software, which is similar to the software compiler used in program development. The original source code before compilation must also be written in a specific programming language. This is called the Hardware Description Language (HDL), and there is not only one type of HDL, but many types, such as ABEL.
(Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language) Etc. At present, VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog are the most commonly used. Those skilled in the art should also be clear that as long as the method flow is logically programmed and integrated into the integrated circuit using the above-mentioned several hardware description languages, the hardware circuit implementing the logic method flow can be easily obtained.
The controller may be implemented in any suitable manner, for example, the controller may take the form of a microprocessor or processor and a computer-readable storage of computer-readable code (such as software or firmware) executable by the (micro) processor. Media, logic gates, switches, application specific integrated circuits (ASICs), programmable logic controllers and embedded microcontrollers. Examples of controllers include but are not limited to the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20 and Silicone Labs C8051F320, the memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art also know that, in addition to implementing the controller in a purely computer-readable code manner, the controller can be controlled by logic gates, switches, dedicated integrated circuits, and programmable logic by programming logic steps in the method steps. Controller and embedded microcontroller to achieve the same function. Therefore, the controller can be considered as a hardware component, and the device included in the controller for implementing various functions can also be considered as a structure in the hardware component. Or even, a device for implementing various functions can be regarded as a structure that can be both a software module implementing the method and a hardware component.
The system, device, module, or unit described in the foregoing embodiments may be specifically implemented by a computer chip or entity, or by a product having a certain function. A typical implementation is a computer. Specifically, the computer may be, for example, a personal computer, a laptop, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, or a wearable device. Or a combination of any of these devices.
For the convenience of description, when describing the above device, the functions are divided into various units and described separately. Of course, when implementing the present application, the functions of each unit may be implemented in the same software or multiple software and / or hardware.
Those skilled in the art should understand that the embodiments of the present invention may be provided as a method, a system, or a computer program product. Therefore, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk memory, CD-ROM, optical memory, etc.) containing computer-usable code therein. .
The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, and a combination of the process and / or block in the flowchart and / or block diagram may be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, special purpose computer, embedded processor, or other programmable data processing device to generate a machine for instructions executed by the processor of the computer or other programmable data processing device Means are generated for implementing the functions specified in one or more of the flowcharts and / or one or more of the block diagrams.
These computer program instructions may also be stored in computer readable memory that can guide a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory generate a manufactured article including a command device The instruction device implements the functions specified in a flowchart or a plurality of processes and / or a block or a plurality of blocks in the block diagram.
These computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operating steps can be performed on the computer or other programmable equipment to generate computer-implemented processing, and thus on the computer or other programmable equipment The instructions executed on the steps provide steps for implementing the functions specified in one or more of the flowcharts and / or one or more of the block diagrams.
In a typical configuration, a computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory.
Memory may include non-permanent memory, random access memory (RAM), and / or non-volatile memory in computer-readable media, such as read-only memory (ROM) or flash memory ( flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media includes permanent and non-permanent, removable and non-removable media. Information can be stored by any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), and other types of random access memory (RAM) , Read-only memory (ROM), electrically erasable and programmable read-only memory (EEPROM), flash memory or other memory technologies, read-only disc read-only memory (CD-ROM), digital multifunction Optical discs (DVDs) or other optical storage, magnetic tape cartridges, magnetic tape storage or other magnetic storage devices or any other non-transmitting media may be used to store information that can be accessed by computing devices. As defined herein, computer-readable media does not include temporary computer-readable media (transitory media), such as modulated data signals and carrier waves.
It should also be noted that the terms "including,""including," or any other variation thereof are intended to encompass non-exclusive inclusion, so that a process, method, product, or device that includes a range of elements includes not only those elements, but also Other elements not explicitly listed, or those that are inherent to such a process, method, product, or device. Without more restrictions, the elements defined by the sentence "including a ..." do not exclude the existence of other identical elements in the process, method, product or equipment including the elements.
Those skilled in the art should understand that the embodiments of the present application may be provided as a method, a system or a computer program product. Therefore, this application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Moreover, this application may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk memory, CD-ROM, optical memory, etc.) containing computer-usable code. .
This application may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific transactions or implement specific abstract data types. The present application can also be practiced in a decentralized computing environment. In these decentralized computing environments, transactions are performed by a remote processing device connected through a communication network. In a distributed computing environment, program modules can be located in local and remote computer storage media, including storage devices.
Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the various embodiments can be referred to each other. Each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple. For the relevant part, refer to the description of the method embodiment.
The above are only examples of the present application and are not intended to limit the present application. For those skilled in the art, this application may have various modifications and changes. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of this application shall be included in the scope of the patent application for this application.

501‧‧‧基礎資訊確定模組501‧‧‧Basic Information Determination Module

502‧‧‧控制條件確定模組 502‧‧‧Control condition determination module

503‧‧‧推送處理模組 503‧‧‧Push Processing Module

504‧‧‧記錄生成模組 504‧‧‧Record generation module

505‧‧‧重置模組 505‧‧‧Reset Module

此處所說明的附圖用來提供對本申請的進一步理解，構成本申請的一部分，本申請的示意性實施例及其說明用於解釋本申請，並不構成對本申請的不當限定。在附圖中：The drawings described here are used to provide a further understanding of the present application and constitute a part of the present application. The schematic embodiments of the present application and the description thereof are used to explain the present application, and do not constitute an improper limitation on the present application. In the drawings:

圖1為本說明書實施例提供的資訊推送方法所基於的實際應用架構示意圖； FIG. 1 is a schematic diagram of an actual application architecture based on an information pushing method provided by an embodiment of the present specification;

圖2為本說明書實施例提供的資訊推送過程示意圖； FIG. 2 is a schematic diagram of an information pushing process provided by an embodiment of the present specification; FIG.

圖3為本說明書實施例提供的在實際應用實例中的資訊推送過程示意圖； FIG. 3 is a schematic diagram of an information pushing process in an actual application example provided by an embodiment of the specification; FIG.

圖4為本說明書實施例提供的推送判斷過程的示意圖； FIG. 4 is a schematic diagram of a push judgment process according to an embodiment of the present specification; FIG.

圖5為本說明書實施例提供的資訊推送裝置結構示意圖。 FIG. 5 is a schematic structural diagram of an information pushing device according to an embodiment of the present specification.

Claims

An information push method includes: Determine the user's corresponding user location and historical push records for that user; Determining a regional push control condition corresponding to the user location according to the user location; Push business information to the user based on the region's push control conditions and the historical push record.

The method according to claim 1, determining the user location corresponding to the user and the historical push record for the user, including: Determine the terminal location used by the user as the user's location through location-based services; According to the user identifier bound to the terminal in advance, the historical push record of the user is determined from the stored historical push records.

According to the method described in claim 1, determining a region push control condition corresponding to the user location according to the user location, which specifically includes: Determine the region to which the user's location belongs; The area push control conditions set in advance for the area are determined as the area push control conditions corresponding to the user's location.

According to the method described in claim 3, setting regional push control conditions for a region in advance includes: For any region, set the control duration and set the threshold for the number of pushes within the control duration; The threshold of the number of pushes set within the control period is determined as a regional push control condition corresponding to the area.

According to the method described in claim 3, setting regional push control conditions for a region in advance includes: For each type of business content, set a control duration and set a threshold for the number of pushes within the control duration; The threshold of the number of pushes set for each type of business content within the control period is determined as a regional push control condition corresponding to each region.

According to the method described in claim 4 or 5, pushing the business information to the user according to the regional push control conditions and the historical push record includes: Determine whether the historical business information that has been pushed to the user within the specified time period exceeds the set number of pushes for the region to which the user's location belongs and the business content to be pushed If yes, do not push business information to the user; Otherwise, push the business information to the user.

The method according to claim 1, further comprising: Determine the user ID, area ID, and push time of the user; Generate a push record based on the user ID, region ID, and push time.

The method according to claim 6, further comprising: Reset the area push control conditions.

An information pushing device includes: The basic information determination module determines the user location corresponding to the user and the historical push records for the user; The control condition determination module determines a region push control condition corresponding to the user location according to the user location; The push processing module pushes business information to the user according to the regional push control conditions and the historical push record.

The device according to claim 9, the basic information determining module determines the location of the terminal used by the user through location-based services, and uses the location as a user location to push records in the stored history according to the user identification bound to the terminal in advance , Determine the user's historical push records.

According to the device described in claim 9, the control condition determining module determines a region to which the user location belongs, and determines a region push control condition set for the region in advance, and determines the region push control condition corresponding to the user location.

The device according to claim 11, the control condition determination module, for any region, sets a control duration, sets a threshold for the number of pushes within the control duration, and determines the threshold for the number of pushes set within the control duration Push control conditions for the region corresponding to that region.

The device according to claim 11, the control condition determining module, for each type of business content, sets a control duration, and sets a threshold for the number of pushes within the control duration, and controls each type of business content in the control The threshold of the number of pushes set within the duration is determined as a regional push control condition corresponding to each region.

The device according to claim 12 or 13, the push processing module judges whether the historical business information that has been pushed to the user within a specified period of time exceeds the set value for the region to which the user's location belongs and the service content to be pushed Threshold of the number of pushes. If it is, the service information is not pushed to the user; otherwise, the service information is pushed to the user.

The device according to claim 9, further comprising: a record generation module that determines a user identification, a region identification, and a push time of the user, and generates a push record according to the user identification, the area identification, and the push time.

The device according to claim 9, further comprising: a condition resetting module for resetting a push control condition in the area.

An information pushing device includes: a processor and a memory, wherein: The memory, which stores information push programs; The processor calls the information push sequence stored in the memory and executes: Determine the user's corresponding user location and historical push records for that user; Determining a regional push control condition corresponding to the user location according to the user location; Push business information to the user based on the region's push control conditions and the historical push record.