這裡將詳細地對示例性實施例進行說明，其示例表示在附圖中。下面的描述涉及附圖時，除非另有表示，不同附圖中的相同數字表示相同或相似的要素。以下示例性實施例中所描述的實施方式並不代表與本說明書相一致的所有實施方式。相反，它們僅是與如所附申請專利範圍中所詳述的、本說明書的一些方面相一致的裝置和方法的例子。
在本說明書使用的術語是僅僅出於描述特定實施例的目的，而非旨在限制本說明書。在本說明書和所附申請專利範圍中所使用的單數形式的“一種”、“所述”和“該”也旨在包括多數形式，除非上下文清楚地表示其他含義。還應當理解，本文中使用的術語“和/或”是指並包含一個或多個相關聯的列出專案的任何或所有可能組合。
應當理解，儘管在本說明書可能採用術語第一、第二、第三等來描述各種資訊，但這些資訊不應限於這些術語。這些術語僅用來將同一類型的資訊彼此區分開。例如，在不脫離本說明書範圍的情況下，第一資訊也可以被稱為第二資訊，類似地，第二資訊也可以被稱為第一資訊。取決於語境，如在此所使用的詞語“如果”可以被解釋成為“在……時”或“當……時”或“回應於確定”。
圖1是本說明書一示例性實施例示出的一種線上簽到的方法的流程示意圖。
所述線上簽到的方法可以應用在服務端，所述服務端通常由具有簽到功能的伺服器或者伺服器集群組成。
請參考圖1，所述線上簽到的方法可以包括以下步驟：
步驟102，獲取用戶的地理位置。
在本實施例中，服務端可以週期性的從客戶端獲取用戶的地理位置，服務端也可以從與客戶端的非簽到業務交互中獲取用戶的地理位置，本說明書對此不作特殊限制。
步驟104，當所述地理位置屬於預定的簽到區域時，推送簽到提醒給用戶。
在本實施例中，所述簽到區域可以包括：旅遊景區、會場、體育館等。
步驟106，接收用戶基於所述簽到提醒上傳的簽到資訊。
在本實施例中，所述簽到資訊包括：圖片資訊、文本資訊等。
步驟108，將所述簽到資訊與所述簽到區域關聯儲存。
圖2是本說明書一示例性實施例示出的另一種線上簽到的方法的流程示意圖。
所述線上簽到的方法可以應用在客戶端，所述客戶端通常是裝載在智慧終端中的應用程式（Application，APP），所述智慧終端可以包括：手機、平板電腦、PC機等，本說明書對此不作特殊限制。
請參考圖2，所述線上簽到的方法可以包括以下步驟：
步驟202，展示服務端推送的簽到提醒，所述簽到提醒是服務端在確定用戶的地理位置屬於預定的簽到區域時推送。
步驟204，回應於用戶針對所述簽到提醒輸入的確定指令，展示簽到頁面。
步驟206，將用戶基於所述簽到頁面輸入的簽到資訊上傳到服務端，以供服務端將所述簽到資訊與所述簽到區域關聯儲存。
由以上描述可以看出，本說明書可在用戶位於預定的簽到區域時，向用戶推送簽到提醒，用戶可基於該簽到提醒進行簽到，基於位置的簽到提醒推送，可有效避免虛假簽到，真實性較高，整個過程無需用戶尋找簽到入口，對於用戶而言方便、快捷。
下面以簽到區域是旅遊景區為例，分別從簽到的實現、簽到的查看兩個方面對本說明書提供的技術方案進行詳細描述。
一、簽到的實現
請參考圖3，本實施例提供的一種旅遊線上簽到的方法可以包括以下步驟：
步驟302，服務端獲取用戶的地理位置。
所述地理位置通常是座標資訊，例如，經緯度座標。
在一個例子中，服務端可以週期性的獲取用戶的地理位置。
例如，服務端可以週期性的下發位置獲取指令給客戶端，客戶端獲取到用戶的地理位置之後返回給服務端。
又例如，也可預先在客戶端配置地理位置獲取週期，客戶端依據該週期定期獲取用戶的地理位置再上傳給服務端等。
所述週期可以由開發人員進行設置，例如：2小時、4小時等，本說明書對此不作特殊限制。
在另一個例子中，服務端可從與客戶端的非簽到業務交互中獲取用戶的地理位置，以避免週期性獲取地理位置浪費服務端和客戶端的處理資源。
在實際應用中，客戶端和服務端的很多業務交互都會攜帶用戶的地理位置，例如，客戶端的外賣業務會攜帶用戶的地理位置，以便服務端獲取用戶周邊的外賣資訊；客戶端的電影票售賣業務也會攜帶用戶的地理位置，以便服務端獲取用戶周邊的電影院資訊等。
在本例中，所述非簽到業務可以包括除簽到業務之外的其他任一攜帶有用戶地理位置的業務，服務端基於與客戶端的這些業務交互中獲取用戶的地理位置，可大大節省服務端和客戶端的處理資源，避免資源浪費。
當然，在實際應用中，在從其他非簽到業務交互中獲取用戶的地理位置之前還可以先提醒用戶進行授權，這部分的處理與實現可以參照相關技術，本說明書在此不再一一贅述。
步驟304，服務端判斷所述地理位置是否屬於預定的旅遊景區。
在本實施例中，可預先保存各旅遊景區的位置資訊。服務端在獲取到用戶的地理位置之後，可判斷該地理位置是否位於某個旅遊景區內，即判斷用戶是否位於某個旅遊景區。
若用戶位於某旅遊景區，則可以執行步驟306。
若用戶沒有位於旅遊景區，則可以結束處理流程。
步驟306，服務端推送簽到提醒給客戶端。
步驟308，客戶端展示所述簽到提醒。
所述簽到提醒的內容可以由開發人員進行設置，例如：是否在**景區（用戶所在景區）簽到？
在實際應用中，當簽到區域是旅遊景區時，也可以以虛擬卡的形式實現簽到，所述虛擬卡可包括用戶所在旅遊景區的標識資訊。例如，以創建“西湖到此一遊”虛擬卡的形式來實現在西湖風景區的簽到。相應的，請參考圖4，簽到提醒可以為：是否創建西湖‘到此一遊’紀念卡。
當然，還可以以其他形式實現簽到，例如：創建虛擬勳章等，本說明書對此不作特殊限制。
步驟310，用戶確認簽到後，客戶端展示簽到頁面。
在本實施例中，當用戶點擊“確認”後，客戶端可以展示可輸入文本和圖片的簽到頁面。仍以創建虛擬卡實現簽到為例，請參考圖5，用戶可以在虛擬卡創建頁面中輸入相關資訊，例如，上傳在景區拍攝的圖片、書寫在景區的感受等。
當然，除圖片和文本之外，在進行簽到時，還可以允許用戶上傳視頻等其他種類的資訊，本說明書對此不作特殊限制。
步驟312，客戶端將用戶輸入的簽到資訊上傳到服務端。
步驟314，服務端將所述簽到資訊與所述旅遊景區關聯儲存。
在本實施例中，服務端可以保存簽到資訊與旅遊景區之間的對應關係，以便用戶查看。
步驟316，服務端將所述旅遊景區關聯的簽到資訊推送給客戶端。
在本實施例中，服務端在接收到用戶上傳的簽到資訊後，可以將其他用戶在同一景區上傳的簽到資訊推送給該用戶瀏覽。
舉例來說，假設小白在西湖風景區遊覽，服務端確定小白位於西湖風景區後，可向小白推送簽到提醒，小白確認該簽到提醒後，透過客戶端上傳照片和文字。服務端在接收到小白上傳的圖片和文字後，可以將歷史上其他用戶遊覽西湖風景區時上傳的簽到資訊推送給小白，小白就可以看到其他用戶在西湖遊覽時的簽到資訊，請參考圖6，一種簽到資訊瀏覽示意圖。當然，若以虛擬卡的形式實現簽到，請參考圖7，可展示紀念卡的瀏覽示意圖。
在本實施例中，服務端可先獲取所述旅遊景區關聯的簽到資訊。
例如，獲取該旅遊景區關聯的所有簽到資訊。
又例如，獲取預定時間段內該旅遊景區關聯的簽到資訊，所述預定時間段可以預先設置，比如：最近三天、最近一周等，本說明書對此不作特殊限制。
在獲取到該旅遊景區關聯的簽到資訊後，可對這些簽到資訊進行排序，然後可基於排序結果將這些簽到資訊推送給用戶。
在一個例子中，可按照簽到時間的先後對獲取到的簽到資訊進行排序。例如，將簽到時間相對靠後的簽到資訊排列在簽到時間相對靠前的簽到資訊之前等。
在另一個例子中，可按照簽到熱度對所述簽到資訊進行排序。例如，將簽到熱度較高的簽到資訊排列在前面等。
當然，還可以按照其他維度的特徵對簽到資訊進行排序，例如，按照用戶星級對簽到資訊進行排序，將高星級用戶的簽到資訊排列在低星級用戶的簽到資訊之前等。此外，也可以綜合考慮簽到時間、簽到熱度等對簽到資訊進行排序，本說明書對此不作特殊限制。
由以上描述可以看出，本實施例服務端可以在用戶位於景區時，向用戶推送簽到提醒，用戶可基於該簽到提醒進行旅行簽到，為自己的旅行留念。基於位置的簽到提醒推送，可有效避免虛假簽到，真實性較高，整個過程無需用戶尋找簽到入口，對於用戶而言方便、快捷。
二、簽到的查看
在本實施例中，用戶在位於旅遊景區時，可以查看其它用戶在該旅遊景區的簽到資訊。
請參考圖8，本實施例提供的一種簽到查看的方法可以包括以下步驟：
步驟802，客戶端將用戶輸入的第一簽到瀏覽請求發送給服務端。
在本實施例中，用戶可以透過客戶端提供的簽到瀏覽按鈕來查看其他用戶在同一景區的簽到資訊。
客戶端在接收到用戶點擊簽到瀏覽按鈕的指令後，可以視為接收到用戶輸入的簽到瀏覽請求，為區分用戶查看自己的簽到資訊，可將瀏覽其他用戶的簽到瀏覽請求稱為第一簽到瀏覽請求。
在本實施例中，客戶端在接收所述第一簽到瀏覽請求後，可以獲取用戶的當前位置資訊，並將該當前位置資訊攜帶在所述第一簽到瀏覽請求中發送給服務端。
步驟804，服務端獲取用戶的當前位置。
在本實施例中，服務端在接收到所述第一簽到瀏覽請求後，可從所述第一簽到瀏覽請求中獲取用戶的當前位置。
若所述第一簽到瀏覽請求中未攜帶用戶的當前位置，服務端可以下發位置獲取指令給客戶端，以獲取用戶的當前位置。
步驟806，服務端判斷所述當前位置是否屬於某一旅遊景區。
若是，則可以執行步驟808。
若否，則可以執行步驟810。
步驟808，將所述當前位置所屬的旅遊景區關聯的簽到資訊推送給客戶端。
在本實施例中，簽到資訊的推送方案可以參照前述步驟316，本說明書在此不再一一贅述。
步驟810，判斷是否存在某一旅遊景區與所述當前位置的距離小於預定距離，若存在，則將該旅遊景區關聯的簽到資訊推送給客戶端。
基於前述步驟806的判斷結果，若用戶的當前位置不屬於任一旅遊景區，說明用戶當前不在任何旅遊景區。那麼在本步驟中，可繼續判斷用戶是否與某一個旅遊景區的距離小於預定距離。
若存在某一旅遊景區，用戶與其距離小於預定距離，通常說明用戶在該旅遊景區附近，為避免定位誤差導致用戶無法瀏覽簽到資訊，可以將該旅遊景區關聯的簽到資訊推送給客戶端，以供用戶瀏覽。
若用戶與任一旅遊景區的距離均大於等於所述預定距離，則通常說明用戶距離景區較遠，此時可不允許用戶查看旅遊景區的簽到資訊，服務端可以向客戶端返回錯誤提示，以確保只有用戶在到達旅遊景區時才能查看其他用戶在該旅遊景區的簽到資訊。
在本實施例中，所述當前位置到旅遊景區的距離可以為當前位置到旅遊景區中心位置的距離，也可以為當前位置到旅遊景區邊界的最短距離，本說明書對此不作特殊限制。
可選的，用戶還可以查看自己曾經旅遊時的簽到資訊。例如，用戶可以在客戶端的個人資訊頁面中點擊簽到瀏覽按鈕，諸如，“我的簽到”按鈕，以發送簽到瀏覽請求。在本例中，可將該簽到瀏覽請求稱為第二簽到瀏覽請求。
服務端在接收到該第二簽到瀏覽請求後，可以將該用戶在歷史上上傳的簽到資訊推送給客戶端，例如，按照簽到時間對簽到資訊進行排序後推送給客戶端等，本說明書對此不作特殊限制。
與前述線上簽到的方法的實施例相對應，本說明書還提供了線上簽到的裝置的實施例。
本說明書線上簽到的裝置的實施例可以分別應用在伺服器和終端上。裝置實施例可以透過軟體實現，也可以透過硬體或者軟硬體結合的方式實現。以軟體實現為例，作為一個邏輯意義上的裝置，是透過其所在伺服器或終端的處理器將非易失性記憶體中對應的電腦程式指令讀取到記憶體中運行形成的。從硬體層面而言，如圖9所示，為本說明書線上簽到的裝置所在伺服器或終端的一種硬體結構圖，除了圖9所示的處理器、記憶體、網路介面、以及非易失性記憶體之外，實施例中裝置所在的伺服器或終端通常根據該伺服器或終端的實際功能，還可以包括其他硬體，對此不再贅述。
圖10是本說明書一示例性實施例示出的一種線上簽到的裝置的方塊圖。
請參考圖10，所述線上簽到的裝置1000可以應用在前述圖9所示的伺服器中，包括有：位置獲取單元1001、簽到提醒單元1002、簽到接收單元1003、簽到儲存單元1004、第一推送單元1005、第二推送單元1006、第三推送單元1007、第四推送單元1008以及虛擬卡單元1009。
其中，位置獲取單元1001，獲取用戶的地理位置；
簽到提醒單元1002，當所述地理位置屬於預定的簽到區域時，推送簽到提醒給用戶；
簽到接收單元1003，接收用戶基於所述簽到提醒上傳的簽到資訊；
簽到儲存單元1004，將所述簽到資訊與所述簽到區域關聯儲存。
第一推送單元1005，將所述簽到區域關聯的簽到資訊推送給用戶。
第二推送單元1006，回應於用戶發送的第一簽到瀏覽請求，獲取用戶的當前位置；將所述當前位置所屬的簽到區域關聯的簽到資訊推送給用戶。
可選的，所述第一推送單元1005和所述第二推送單元1006，對所述簽到區域關聯的簽到資訊進行排序；基於排序結果將所述簽到資訊推送給用戶。
可選的，所述第一推送單元1005和所述第二推送單元1006，按照簽到時間對所述簽到資訊進行排序。
可選的，所述第一推送單元1005和所述第二推送單元1006，按照簽到熱度對所述簽到資訊進行排序。
第三推送單元1007，在所述當前位置不屬於任一簽到區域時，判斷是否存在某一簽到區域與所述當前位置的距離小於預定距離；若存在，則將該簽到區域關聯的簽到資訊推送給用戶。
第四推送單元1008，回應於用戶發送的第二簽到瀏覽請求，將該用戶在歷史上上傳的簽到資訊推送給該用戶。
虛擬卡單元1009，根據所述簽到資訊產生虛擬簽到卡，所述虛擬簽到卡包括有所述簽到區域的標識資訊。
可選的，所述位置獲取單元1001，從與客戶端的非簽到業務交互中獲取用戶的地理位置。
可選的，所述簽到區域包括：旅遊景區。
可選的，所述簽到資訊包括：圖片資訊、文本資訊。
圖11是本說明書一示例性實施例示出的一種線上簽到的裝置的方塊圖。
請參考圖11，所述線上簽到的裝置1100可以應用在前述圖10所示的終端中，包括有：提醒展示單元1101、簽到展示單元1102以及簽到上傳單元1103。
提醒展示單元1101，展示服務端推送的簽到提醒，所述簽到提醒是服務端在確定用戶的地理位置屬於預定的簽到區域時推送；
簽到展示單元1102，回應於用戶針對所述簽到提醒輸入的確定指令，展示簽到頁面；
簽到上傳單元1103，將用戶基於所述簽到頁面輸入的簽到資訊上傳到服務端，以供服務端將所述簽到資訊與所述簽到區域關聯儲存。
上述裝置中各個單元的功能和作用的實現過程具體詳見上述方法中對應步驟的實現過程，在此不再贅述。
對於裝置實施例而言，由於其基本對應於方法實施例，所以相關之處參見方法實施例的部分說明即可。以上所描述的裝置實施例僅僅是示意性的，其中所述作為分離部件說明的單元可以是或者也可以不是物理上分開的，作為單元顯示的部件可以是或者也可以不是物理單元，即可以位於一個地方，或者也可以分佈到多個網路單元上。可以根據實際的需要選擇其中的部分或者全部模組來實現本說明書方案的目的。本領域普通技術人員在不付出創造性勞動的情況下，即可以理解並實施。
上述實施例闡明的系統、裝置、模組或單元，具體可以由電腦晶片或實體實現，或者由具有某種功能的產品來實現。一種典型的實現設備為電腦，電腦的具體形式可以是個人電腦、膝上型電腦、行動電話、相機電話、智慧型電話、個人數位助理、媒體播放機、導航設備、電子郵件收發設備、遊戲控制台、平板電腦、可穿戴設備或者這些設備中的任意幾種設備的組合。
與前述線上簽到的方法的實施例相對應，本說明書還提供一種線上簽到的裝置，該線上簽到的裝置包括：處理器以及用於儲存機器可執行指令的記憶體。其中，處理器和記憶體通常藉由內部匯流排相互連接。在其他可能的實現方式中，所述設備還可能包括外部介面，以能夠與其他設備或者部件進行通信。
在本實施例中，透過讀取並執行所述記憶體儲存的與線上簽到的邏輯對應的機器可執行指令，所述處理器被促使：
獲取用戶的地理位置；
當所述地理位置屬於預定的簽到區域時，推送簽到提醒給用戶；
接收用戶基於所述簽到提醒上傳的簽到資訊；
將所述簽到資訊與所述簽到區域關聯儲存。
可選的，在接收到用戶基於所述簽到提醒上傳的簽到資訊之後，所述處理器被促使：
將所述簽到區域關聯的簽到資訊推送給用戶。
可選的，所述處理器還被促使：
回應於用戶發送的第一簽到瀏覽請求，獲取用戶的當前位置；
將所述當前位置所屬的簽到區域關聯的簽到資訊推送給用戶。
可選的，在將簽到區域關聯的簽到資訊推送給用戶時，所述處理器被促使：
對所述簽到區域關聯的簽到資訊進行排序；
基於排序結果將所述簽到資訊推送給用戶。
可選的，在對所述簽到區域關聯的簽到資訊進行排序時，所述處理器被促使：
按照簽到時間對所述簽到資訊進行排序。
可選的，在對所述簽到區域關聯的簽到資訊進行排序時，所述處理器被促使：
按照簽到熱度對所述簽到資訊進行排序。
可選的，所述處理器還被促使：
若所述當前位置不屬於任一簽到區域，則判斷是否存在某一簽到區域與所述當前位置的距離小於預定距離；
若存在，則將該簽到區域關聯的簽到資訊推送給用戶。
可選的，所述處理器還被促使：
回應於用戶發送的第二簽到瀏覽請求，將該用戶在歷史上上傳的簽到資訊推送給該用戶。
可選的，所述處理器還被促使：
根據所述簽到資訊產生虛擬簽到卡，所述虛擬簽到卡包括有所述簽到區域的標識資訊。
可選的，在獲取用戶的地理位置時，所述處理器還被促使：
從與客戶端的非簽到業務交互中獲取用戶的地理位置。
可選的，所述簽到區域包括：旅遊景區。
可選的，所述簽到資訊包括：圖片資訊、文本資訊。
與前述線上簽到的方法的實施例相對應，本說明書還提供另一種線上簽到的裝置，該線上簽到的裝置包括：處理器以及用於儲存機器可執行指令的記憶體。其中，處理器和記憶體通常藉由內部匯流排相互連接。在其他可能的實現方式中，所述設備還可能包括外部介面，以能夠與其他設備或者部件進行通信。
在本實施例中，透過讀取並執行所述記憶體儲存的與線上簽到的邏輯對應的機器可執行指令，所述處理器被促使：
展示服務端推送的簽到提醒，所述簽到提醒是服務端在確定用戶的地理位置屬於預定的簽到區域時推送；
回應於用戶針對所述簽到提醒輸入的確定指令，展示簽到頁面；
將用戶基於所述簽到頁面輸入的簽到資訊上傳到服務端，以供服務端將所述簽到資訊與所述簽到區域關聯儲存。
與前述線上簽到的方法的實施例相對應，本說明書還提供一種電腦可讀儲存媒體，所述電腦可讀儲存媒體上儲存有電腦程式，該程式被處理器執行時實現以下步驟：
獲取用戶的地理位置；
當所述地理位置屬於預定的簽到區域時，推送簽到提醒給用戶；
接收用戶基於所述簽到提醒上傳的簽到資訊；
將所述簽到資訊與所述簽到區域關聯儲存。
可選的，在接收到用戶基於所述簽到提醒上傳的簽到資訊之後，還包括：
將所述簽到區域關聯的簽到資訊推送給用戶。
可選的，還包括：
回應於用戶發送的第一簽到瀏覽請求，獲取用戶的當前位置；
將所述當前位置所屬的簽到區域關聯的簽到資訊推送給用戶。
可選的，所述將簽到區域關聯的簽到資訊推送給用戶，包括：
對所述簽到區域關聯的簽到資訊進行排序；
基於排序結果將所述簽到資訊推送給用戶。
可選的，所述對所述簽到區域關聯的簽到資訊進行排序，包括：
按照簽到時間對所述簽到資訊進行排序。
可選的，所述對所述簽到區域關聯的簽到資訊進行排序，包括：
按照簽到熱度對所述簽到資訊進行排序。
可選的，還包括：
若所述當前位置不屬於任一簽到區域，則判斷是否存在某一簽到區域與所述當前位置的距離小於預定距離；
若存在，則將該簽到區域關聯的簽到資訊推送給用戶。
可選的，還包括：
回應於用戶發送的第二簽到瀏覽請求，將該用戶在歷史上上傳的簽到資訊推送給該用戶。
可選的，還包括：
根據所述簽到資訊產生虛擬簽到卡，所述虛擬簽到卡包括有所述簽到區域的標識資訊。
可選的，所述獲取用戶的地理位置，包括：
從與客戶端的非簽到業務交互中獲取用戶的地理位置。
可選的，所述簽到區域包括：旅遊景區。
可選的，所述簽到資訊包括：圖片資訊、文本資訊。
與前述線上簽到的方法的實施例相對應，本說明書還提供另一種電腦可讀儲存媒體，所述電腦可讀儲存媒體上儲存有電腦程式，該程式被處理器執行時實現以下步驟：
展示服務端推送的簽到提醒，所述簽到提醒是服務端在確定用戶的地理位置屬於預定的簽到區域時推送；
回應於用戶針對所述簽到提醒輸入的確定指令，展示簽到頁面；
將用戶基於所述簽到頁面輸入的簽到資訊上傳到服務端，以供服務端將所述簽到資訊與所述簽到區域關聯儲存。
上述對本說明書特定實施例進行了描述。其它實施例在所附申請專利範圍的範圍內。在一些情況下，在申請專利範圍中記載的動作或步驟可以按照不同於實施例中的順序來執行並且仍然可以實現期望的結果。另外，在附圖中描繪的過程不一定要求示出的特定順序或者連續順序才能實現期望的結果。在某些實施方式中，多工處理和並行處理也是可以的或者可能是有利的。
以上所述僅為本說明書的較佳實施例而已，並不用以限制本說明書，凡在本說明書的精神和原則之內，所做的任何修改、等同替換、改進等，均應包含在本說明書保護的範圍之內。Here, exemplary embodiments will be described in detail, and examples thereof are shown in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings indicate the same or similar elements. The implementation manners described in the following exemplary embodiments do not represent all implementation manners consistent with this specification. On the contrary, they are only examples of devices and methods consistent with some aspects of this specification as detailed in the scope of the appended application.
The terms used in this specification are only for the purpose of describing specific embodiments, and are not intended to limit the specification. The singular forms of "a", "the" and "the" used in this specification and the scope of the appended application are also intended to include plural forms, unless the context clearly indicates other meanings. It should also be understood that the term "and/or" as used herein refers to and includes any or all possible combinations of one or more associated listed items.
It should be understood that although the terms first, second, and third may be used in this specification to describe various information, the information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of this specification, the first information can also be referred to as second information, and similarly, the second information can also be referred to as first information. Depending on the context, the word "if" as used herein can be interpreted as "when" or "when" or "in response to certainty".
Fig. 1 is a schematic flowchart of an online check-in method shown in an exemplary embodiment of this specification.
The online check-in method can be applied to a server, and the server usually consists of a server or a cluster of servers with a check-in function.
Please refer to Figure 1. The online check-in method may include the following steps:
Step 102: Obtain the geographic location of the user.
In this embodiment, the server may periodically obtain the user's geographic location from the client, and the server may also obtain the user's geographic location from the non-sign-in service interaction with the client, which is not particularly limited in this specification.
Step 104: When the geographic location belongs to a predetermined sign-in area, push sign-in reminders to the user.
In this embodiment, the sign-in area may include: tourist attractions, conference venues, gymnasiums, etc.
Step 106: Receive check-in information uploaded by the user based on the check-in reminder.
In this embodiment, the sign-in information includes: picture information, text information, and so on.
Step 108: Store the check-in information in association with the check-in area.
Fig. 2 is a schematic flowchart of another online check-in method shown in an exemplary embodiment of the present specification.
The online check-in method can be applied to a client. The client is usually an application (APP) loaded in a smart terminal. The smart terminal may include a mobile phone, a tablet computer, a PC, etc. This manual There are no special restrictions on this.
Please refer to Figure 2. The online check-in method may include the following steps:
Step 202: Display the sign-in reminder pushed by the server. The sign-in reminder is pushed by the server when it determines that the geographic location of the user belongs to a predetermined sign-in area.
Step 204: In response to the user's confirmation instruction input for the sign-in reminder, a sign-in page is displayed.
Step 206: Upload the sign-in information input by the user based on the sign-in page to the server, so that the server can store the sign-in information in association with the sign-in area.
As can be seen from the above description, this manual can push a sign-in reminder to the user when the user is located in a predetermined sign-in area. The user can sign-in based on the sign-in reminder. The location-based sign-in reminder push can effectively avoid false sign-in and is more authentic. High, the whole process does not require the user to look for the sign-in entrance, which is convenient and fast for the user.
Taking the check-in area as a tourist attraction as an example, the technical solutions provided in this manual will be described in detail from two aspects: check-in realization and check-in viewing.
1. Realization of sign-in
Referring to FIG. 3, the method for checking in on a travel line provided by this embodiment may include the following steps:
Step 302: The server obtains the geographic location of the user.
The geographic location is usually coordinate information, for example, latitude and longitude coordinates.
In one example, the server can periodically obtain the geographic location of the user.
For example, the server may periodically issue a location acquisition instruction to the client, and the client returns to the server after acquiring the user's geographic location.
For another example, it is also possible to configure the geographic location acquisition period on the client in advance, and the client periodically obtains the user's geographic location according to the period and uploads it to the server.
The period can be set by the developer, for example: 2 hours, 4 hours, etc. This specification does not make special restrictions on this.
In another example, the server can obtain the user's geographic location from the non-sign-in business interaction with the client, so as to avoid periodically obtaining the geographic location from wasting processing resources of the server and the client.
In practical applications, many business interactions between the client and the server will carry the user’s geographic location. For example, the customer’s take-out business will carry the user’s geographic location so that the server can obtain takeaway information around the user; the client’s movie ticket sales business also It will carry the user's geographic location so that the server can obtain information about the cinema around the user.
In this example, the non-sign-in service may include any service other than the sign-in service that carries the user's geographic location. The server obtains the user's geographic location based on these service interactions with the client, which can greatly save the server And the processing resources of the client to avoid waste of resources.
Of course, in actual applications, the user can also be reminded to authorize before obtaining the user's geographic location from other non-sign-in business interactions. The processing and implementation of this part can refer to related technologies, and this specification will not repeat them here.
Step 304: The server determines whether the geographic location belongs to a predetermined tourist attraction.
In this embodiment, the location information of each tourist attraction can be saved in advance. After obtaining the user's geographic location, the server can determine whether the geographic location is located in a certain tourist area, that is, whether the user is located in a certain tourist area.
If the user is located in a tourist attraction, step 306 can be executed.
If the user is not located in a tourist attraction, the processing flow can be ended.
Step 306: The server pushes the sign-in reminder to the client.
Step 308: The client displays the sign-in reminder.
The content of the check-in reminder can be set by the developer, for example: whether to check-in in the ** scenic spot (the user's scenic spot)?
In practical applications, when the sign-in area is a tourist attraction, the sign-in can also be realized in the form of a virtual card, which may include identification information of the tourist attraction where the user is located. For example, in the form of creating a virtual card of "Visit to the West Lake" to realize sign-in in the West Lake Scenic Area. Correspondingly, please refer to Figure 4. The sign-in reminder can be: whether to create a commemorative card of West Lake'Visit here'
Of course, sign-in can also be realized in other forms, such as creating virtual medals, etc. This manual does not make special restrictions on this.
Step 310: After the user confirms the sign-in, the client terminal displays the sign-in page.
In this embodiment, after the user clicks "confirm", the client can display a sign-in page where text and pictures can be input. Still taking the creation of a virtual card to achieve sign-in as an example, please refer to Figure 5. The user can enter relevant information on the virtual card creation page, such as uploading pictures taken in a scenic spot, writing feelings in the scenic spot, etc.
Of course, in addition to pictures and texts, users can also be allowed to upload other types of information such as videos when signing in. This manual does not impose special restrictions on this.
Step 312: The client uploads the sign-in information input by the user to the server.
Step 314: The server stores the check-in information in association with the tourist attraction.
In this embodiment, the server can save the correspondence between the sign-in information and the tourist attractions for the user to view.
In step 316, the server pushes the sign-in information associated with the tourist attraction to the client.
In this embodiment, after receiving the check-in information uploaded by the user, the server can push the check-in information uploaded by other users in the same scenic spot to the user for browsing.
For example, suppose Xiaobai is visiting the West Lake Scenic Area. After the server determines that Xiaobai is in the West Lake Scenic Area, it can push a check-in reminder to Xiaobai. After Xiaobai confirms the check-in reminder, he uploads photos and text through the client. After receiving the pictures and text uploaded by Xiaobai, the server can push the check-in information uploaded by other users in the history of West Lake scenic area to Xiaobai, and Xiaobai can see the check-in information of other users when they visit the West Lake. Please refer to Figure 6, a schematic diagram of check-in information browsing. Of course, if the sign-in is realized in the form of a virtual card, please refer to Figure 7, which can display a schematic view of the commemorative card.
In this embodiment, the server may first obtain check-in information associated with the tourist attraction.
For example, to obtain all check-in information associated with the tourist attraction.
For another example, to obtain check-in information associated with the tourist attraction within a predetermined time period, the predetermined time period can be preset, such as the last three days, the last week, etc., which are not particularly limited in this specification.
After the check-in information associated with the tourist attraction is obtained, the check-in information can be sorted, and then the check-in information can be pushed to the user based on the sorting result.
In an example, the obtained check-in information can be sorted according to the check-in time. For example, arrange the check-in information with the check-in time relatively late before the check-in information with the check-in time relatively earlier.
In another example, the check-in information may be sorted according to check-in popularity. For example, arrange the check-in information with higher check-in popularity in the front.
Of course, the check-in information can also be sorted according to the characteristics of other dimensions, for example, the check-in information is sorted according to the user's star rating, and the check-in information of high-star users is arranged before the check-in information of low-star users. In addition, the check-in information can also be sorted by comprehensive consideration of check-in time, check-in heat, etc. This manual does not make special restrictions on this.
It can be seen from the above description that the server of this embodiment can push a sign-in reminder to the user when the user is in a scenic spot, and the user can sign in for travel based on the sign-in reminder to take a souvenir for his travel. The location-based sign-in reminder push can effectively avoid false sign-in, and the authenticity is high. The whole process does not require the user to look for the sign-in entrance, which is convenient and fast for the user.
Second, check-in
In this embodiment, when a user is located in a tourist attraction, he can view the check-in information of other users in the tourist attraction.
Please refer to FIG. 8, a check-in method provided by this embodiment may include the following steps:
In step 802, the client sends the first sign-in browsing request input by the user to the server.
In this embodiment, the user can view the check-in information of other users in the same scenic spot through the check-in browse button provided by the client.
After the client receives the user's instruction to click the sign-in browse button, it can be regarded as receiving the sign-in browse request input by the user. In order to distinguish the user from viewing his sign-in information, browse the sign-in browse request of other users as the first sign-in browse request.
In this embodiment, after receiving the first check-in browsing request, the client can obtain the user's current location information, and carry the current location information in the first check-in browsing request and send it to the server.
Step 804: The server obtains the current location of the user.
In this embodiment, after receiving the first check-in browsing request, the server can obtain the current location of the user from the first check-in browsing request.
If the first sign-in browsing request does not carry the current location of the user, the server may issue a location acquisition instruction to the client to acquire the current location of the user.
Step 806: The server judges whether the current location belongs to a certain tourist attraction.
If yes, step 808 can be performed.
If not, step 810 can be performed.
Step 808: Push the sign-in information associated with the tourist attraction to which the current location belongs to the client.
In this embodiment, the push scheme of the sign-in information can refer to the aforementioned step 316, which will not be repeated in this specification.
Step 810: It is judged whether there is a certain tourist attraction that is less than a predetermined distance from the current location, and if so, the check-in information associated with the tourist attraction is pushed to the client.
Based on the judgment result of the foregoing step 806, if the user's current location does not belong to any tourist attraction, it means that the user is not currently in any tourist attraction. Then in this step, it can continue to judge whether the distance between the user and a certain tourist attraction is less than a predetermined distance.
If there is a tourist attraction and the distance between the user and the user is less than the predetermined distance, it usually means that the user is near the tourist attraction. In order to avoid positioning errors that cause the user to be unable to browse the check-in information, the check-in information associated with the tourist attraction can be pushed to the client for User browsing.
If the distance between the user and any tourist attraction is greater than or equal to the predetermined distance, it usually means that the user is far away from the scenic spot. At this time, the user may not be allowed to view the check-in information of the tourist attraction, and the server can return an error prompt to the client to ensure Only when a user arrives at a tourist attraction can he view the check-in information of other users in the tourist attraction.
In this embodiment, the distance from the current location to the tourist attraction can be the distance from the current location to the center of the tourist attraction, or the shortest distance from the current location to the boundary of the tourist attraction, which is not particularly limited in this specification.
Optionally, the user can also view the check-in information when he traveled. For example, the user can click a check-in browsing button, such as a "my check-in" button on the personal information page of the client, to send a check-in browsing request. In this example, the check-in browsing request can be referred to as the second check-in browsing request.
After receiving the second sign-in browsing request, the server can push the sign-in information uploaded by the user in the history to the client. For example, the sign-in information is sorted according to the sign-in time and then sent to the client. No special restrictions.
Corresponding to the foregoing embodiment of the online check-in method, this specification also provides an embodiment of the online check-in device.
The embodiments of the online check-in device in this manual can be applied to the server and the terminal respectively. The device embodiments can be implemented through software, or through hardware or a combination of software and hardware. Take software implementation as an example. As a logical device, it is formed by reading the corresponding computer program instructions in the non-volatile memory into the memory through the processor of the server or terminal where it is located. From the perspective of hardware, as shown in Figure 9, it is a hardware structure diagram of the server or terminal where the online sign-in device of this manual is located, except for the processor, memory, network interface, and non- In addition to the volatile memory, the server or terminal where the device is located in the embodiment generally may include other hardware according to the actual function of the server or terminal, which will not be repeated here.
Fig. 10 is a block diagram of an online check-in device shown in an exemplary embodiment of this specification.
Please refer to FIG. 10, the online check-in device 1000 can be applied to the server shown in FIG. 9, and includes: a location acquisition unit 1001, a check-in reminder unit 1002, a check-in receiving unit 1003, a check-in storage unit 1004, a first Push unit 1005, second push unit 1006, third push unit 1007, fourth push unit 1008, and virtual card unit 1009.
Wherein, the location obtaining unit 1001 obtains the geographic location of the user;
The sign-in reminder unit 1002, when the geographic location belongs to a predetermined sign-in area, pushes a sign-in reminder to the user;
The sign-in receiving unit 1003 receives sign-in information uploaded by the user based on the sign-in reminder;
The sign-in storage unit 1004 stores the sign-in information in association with the sign-in area.
The first pushing unit 1005 pushes the sign-in information associated with the sign-in area to the user.
The second pushing unit 1006, in response to the first check-in browsing request sent by the user, obtains the user's current location; and pushes the check-in information associated with the check-in area to which the current location belongs to the user.
Optionally, the first pushing unit 1005 and the second pushing unit 1006 sort the check-in information associated with the check-in area; push the check-in information to the user based on the sorting result.
Optionally, the first pushing unit 1005 and the second pushing unit 1006 sort the check-in information according to check-in time.
Optionally, the first pushing unit 1005 and the second pushing unit 1006 sort the check-in information according to check-in popularity.
The third pushing unit 1007, when the current location does not belong to any check-in area, judge whether there is a check-in area that is less than a predetermined distance from the current location; if it exists, push the check-in information associated with the check-in area To the user.
The fourth pushing unit 1008, in response to the second sign-in browsing request sent by the user, pushes the sign-in information uploaded by the user in history to the user.
The virtual card unit 1009 generates a virtual sign-in card according to the sign-in information, and the virtual sign-in card includes identification information of the sign-in area.
Optionally, the location obtaining unit 1001 obtains the geographic location of the user from the non-sign-in service interaction with the client.
Optionally, the sign-in area includes: a tourist attraction.
Optionally, the sign-in information includes: picture information and text information.
Fig. 11 is a block diagram of an online check-in device shown in an exemplary embodiment of this specification.
Referring to FIG. 11, the online check-in apparatus 1100 can be applied to the terminal shown in FIG. 10, and includes: a reminder display unit 1101, a check-in display unit 1102, and a check-in upload unit 1103.
The reminder display unit 1101 displays the sign-in reminder pushed by the server, where the sign-in reminder is pushed by the server when it determines that the geographic location of the user belongs to a predetermined sign-in area;
The sign-in display unit 1102 displays the sign-in page in response to the confirmation instruction input by the user for the sign-in reminder;
The sign-in uploading unit 1103 uploads the sign-in information input by the user based on the sign-in page to the server, so that the server can store the sign-in information in association with the sign-in area.
For the implementation process of the functions and roles of each unit in the above-mentioned device, please refer to the implementation process of the corresponding steps in the above-mentioned method for details, which will not be repeated here.
For the device embodiment, since it basically corresponds to the method embodiment, the relevant part can refer to the part of the description of the method embodiment. The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in One place, or it can be distributed to multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution in this specification. Those of ordinary skill in the art can understand and implement it without creative work.
The systems, devices, modules or units explained in the above embodiments may be implemented by computer chips or entities, or implemented by products with certain functions. A typical implementation device is a computer. The specific form of the computer can be a personal computer, a laptop computer, a mobile phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email receiving and sending device, and a game control A console, a tablet, a wearable device, or a combination of any of these devices.
Corresponding to the foregoing embodiment of the online check-in method, this specification also provides an online check-in device. The online check-in device includes a processor and a memory for storing machine executable instructions. Among them, the processor and the memory are usually connected to each other through an internal bus. In other possible implementation manners, the device may also include an external interface to be able to communicate with other devices or components.
In this embodiment, by reading and executing the machine executable instructions stored in the memory and corresponding to the logic of online check-in, the processor is prompted to:
Get the user's geographic location;
When the geographic location belongs to a predetermined sign-in area, push sign-in reminders to the user;
Receiving sign-in information uploaded by the user based on the sign-in reminder;
The check-in information is stored in association with the check-in area.
Optionally, after receiving sign-in information uploaded by the user based on the sign-in reminder, the processor is prompted to:
Push the sign-in information associated with the sign-in area to the user.
Optionally, the processor is also prompted to:
In response to the first sign-in browsing request sent by the user, obtain the user's current location;
Push the sign-in information associated with the sign-in area to which the current position belongs to the user.
Optionally, when the check-in information associated with the check-in area is pushed to the user, the processor is prompted to:
Sort the check-in information associated with the check-in area;
Push the check-in information to the user based on the sorting result.
Optionally, when sorting the sign-in information associated with the sign-in area, the processor is prompted to:
Sort the check-in information according to check-in time.
Optionally, when sorting the sign-in information associated with the sign-in area, the processor is prompted to:
Sort the check-in information according to check-in heat.
Optionally, the processor is also prompted to:
If the current location does not belong to any check-in area, determining whether there is a check-in area that is less than a predetermined distance from the current location;
If it exists, push the sign-in information associated with the sign-in area to the user.
Optionally, the processor is also prompted to:
In response to the second sign-in browsing request sent by the user, the sign-in information uploaded by the user in the history is pushed to the user.
Optionally, the processor is also prompted to:
A virtual sign-in card is generated according to the sign-in information, and the virtual sign-in card includes identification information of the sign-in area.
Optionally, when acquiring the geographic location of the user, the processor is also prompted to:
Obtain the user's geographic location from the non-sign-in business interaction with the client.
Optionally, the sign-in area includes: a tourist attraction.
Optionally, the sign-in information includes: picture information and text information.
Corresponding to the foregoing embodiment of the online check-in method, this specification also provides another online check-in device. The online check-in device includes a processor and a memory for storing machine executable instructions. Among them, the processor and the memory are usually connected to each other through an internal bus. In other possible implementation manners, the device may also include an external interface to be able to communicate with other devices or components.
In this embodiment, by reading and executing the machine executable instructions stored in the memory and corresponding to the logic of online check-in, the processor is prompted to:
Display the sign-in reminder pushed by the server, the sign-in reminder is pushed when the server determines that the user's geographic location belongs to the predetermined sign-in area;
In response to the user's confirmation instruction input for the sign-in reminder, display the sign-in page;
The check-in information input by the user based on the check-in page is uploaded to the server, so that the server can associate and store the check-in information with the check-in area.
Corresponding to the aforementioned embodiment of the online sign-in method, this specification also provides a computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, the following steps are implemented:
Get the user's geographic location;
When the geographic location belongs to a predetermined sign-in area, push sign-in reminders to the user;
Receiving sign-in information uploaded by the user based on the sign-in reminder;
The check-in information is stored in association with the check-in area.
Optionally, after receiving the check-in information uploaded by the user based on the check-in reminder, it further includes:
Push the sign-in information associated with the sign-in area to the user.
Optional, also includes:
In response to the first sign-in browsing request sent by the user, obtain the user's current location;
Push the sign-in information associated with the sign-in area to which the current position belongs to the user.
Optionally, the pushing the sign-in information associated with the sign-in area to the user includes:
Sort the check-in information associated with the check-in area;
Push the check-in information to the user based on the sorting result.
Optionally, the sorting the sign-in information associated with the sign-in area includes:
Sort the check-in information according to check-in time.
Optionally, the sorting the sign-in information associated with the sign-in area includes:
Sort the check-in information according to check-in heat.
Optional, also includes:
If the current location does not belong to any check-in area, determining whether there is a check-in area that is less than a predetermined distance from the current location;
If it exists, push the sign-in information associated with the sign-in area to the user.
Optional, also includes:
In response to the second sign-in browsing request sent by the user, the sign-in information uploaded by the user in the history is pushed to the user.
Optional, also includes:
A virtual sign-in card is generated according to the sign-in information, and the virtual sign-in card includes identification information of the sign-in area.
Optionally, the obtaining the geographic location of the user includes:
Obtain the user's geographic location from the non-sign-in business interaction with the client.
Optionally, the sign-in area includes: a tourist attraction.
Optionally, the sign-in information includes: picture information and text information.
Corresponding to the aforementioned embodiment of the online sign-in method, this specification also provides another computer-readable storage medium with a computer program stored on the computer-readable storage medium, and when the program is executed by a processor, the following steps are implemented:
Display the sign-in reminder pushed by the server, the sign-in reminder is pushed by the server when it determines that the user's geographic location belongs to the predetermined sign-in area;
In response to the user's confirmation instruction input for the sign-in reminder, the sign-in page is displayed;
The check-in information input by the user based on the check-in page is uploaded to the server, so that the server can associate and store the check-in information with the check-in area.
The foregoing describes specific embodiments of this specification. Other embodiments are within the scope of the attached patent application. In some cases, the actions or steps described in the scope of the patent application may be performed in a different order from the embodiment and still achieve desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or sequential order shown to achieve the desired result. In some embodiments, multiplexing and parallel processing are also possible or may be advantageous.
The above descriptions are only preferred embodiments of this specification, and are not intended to limit this specification. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of this specification shall be included in this specification Within the scope of protection.