對現有技術進行研究發現，在用車電子支付模式下，支付管道單一，使用者體驗不足。
本說明書實施例提出一種用車支付方法、裝置、系統及電子設備，其實質方案是，對目標車的用車帳單資訊，確定所述用車帳單資訊所對應的用車行為類別，獲取所述用車行為類別對應的支付管道，根據所述用車帳單資訊，向所述支付管道對應的結算端發送用車支付請求，使得所述結算端根據所述用車支付請求完成支付。本說明書實施例記載的方案提供支付管道選擇方案，具體地根據用車行為類別選擇對應的支付管道，改善單一用車行為類別造成的支付管道唯一性，給予使用者更多的支付選擇，提升使用者體驗。
為使本申請的目的、技術方案和優點更加清楚，下面將結合本說明書具體實施例及相應的附圖對本申請技術方案進行清楚、完整地描述。顯然，所描述的實施例僅是本說明書一部分實施例，而不是全部的實施例。基於本說明書中的實施例，本領域普通技術人員在沒有做出進步性勞動前提下所獲得的所有其他實施例，都屬於本申請保護的範圍。
以下結合附圖，詳細說明本說明書各實施例提供的技術方案。
圖1為本說明書實施例提出的一種用車支付系統的結構示意圖。
本說明書實施例記載的用車支付系統可以包括：
採集終端101，採集目標車C的用車行為資訊，根據所述用車行為資訊產生用車帳單資訊；
用車收費系統102，從所述採集終端101接收所述用車帳單資訊，確定所述用車帳單資訊所對應的用車行為類別，獲取所述用車行為類別對應的支付管道，根據所述用車帳單資訊產生用車支付請求；
結算端103，從所述用車收費系統102接收所述用車支付請求根據所述用車支付請求完成支付。
在本說明書實施例中，採集終端101可以採用紅外線掃描識別技術、或照相識別技術、或雷射掃描識別技術識別目標車C及用車行為資訊。
在本說明書另一實施例中，用車支付系統還可以包括：
車載終端，當與所述採集終端建立通信連接時，所述採集終端採集所述目標車的用車行為資訊。
採集終端101與目標車C之間可以建立通信連接，通過識別目標車C來採集目標車C的用車行為資訊。例如，採用IC卡識別技術、或非接觸式射頻識別技術識別目標車C及其用車行為資訊。例如，無線通訊識別技術中，目標車C中預裝車載單元(On board unit，OBU)又稱應答器(Transponder)或電子標籤(Tag)，採集終端101預裝路邊單元(Road side unit，RSU)及感應器。當車輛通過時，感應器感知車輛，RSU發出詢問信號，OBU做出回應，並進行雙向通信和資料交換，繼而OBU採集目標車C的車牌資訊及用車行為資訊。
用車行為資訊可以包含指定路段行車、停車、加油中的一種或多種。指定路段行車可以包含收費公路行車，如高速、橋樑等，對具體場景不做限定。
用車帳單資訊是對用車行為進行計費而得到的繳費單。
支付管道可以是第三方支付管道、銀行卡或其他支付管道，在此不做具體限定。
利用本說明書實施例記載的系統，可以根據用車行為類別選擇對應的支付管道，改善單一用車行為類別造成的支付管道唯一性，給予使用者更多的支付選擇，提升使用者體驗。
圖2為本說明書實施例提出的一種基於用車支付系統的用車支付方法的一個應用示例的時序圖。
步驟202：當目標車20進入預設車道，停車系統21識別車輛標識資訊，並採集入場時間。
停車系統21為採集終端的一個應用示例，入場時間為用車行為資訊的一種。
步驟204：當目標車20駛出預設車道，停車系統21識別車輛標識資訊，並採集出場時間。
步驟206：停車系統21基於兩次車輛標識資訊匹配到同一輛目標車20，根據入場時間和出場時間計算目標車20的停車時間及停車費，產生停車帳單資訊。
步驟208：停車系統21向用車收費系統22發送停車帳單資訊。
步驟210：用車收費系統22判定該用車行為類別為停車。
步驟212：用車收費系統22根據停車與支付管道之間的對應關係，確定當前的支付管道；
步驟214：用車收費系統22根據停車帳單資訊產生支付請求，將支付請求發送給已確定的支付管道側的結算端23；
步驟216：結算端23接收支付請求，並根據支付請求完成支付。
圖3為本說明書實施例提出的一種用車支付方法的流程圖。本方法的執行主體可以是用車收費系統。
步驟301：接收目標車的用車帳單資訊。
本說明書實施例記載的用車帳單資訊可以是採集終端通過採集用車行為而產生的繳費單資訊。
用車帳單資訊可以包含目標車的車輛標識、繳費金額、用車行為資訊中的一種或多種。
步驟303：確定所述用車帳單資訊所對應的用車行為類別。
用車帳單資訊所對應的用車行為類別反映了產生用車帳單資訊的用車行為所屬類別。
在本說明書實施例中，確定所述用車帳單資訊所對應的用車行為類別，可以包括：
根據所述用車帳單資訊的發送方的標識獲取用車行為類別。
用車帳單資訊的發送方的標識表徵發送方從事的業務類型，該業務類型為發送方提供特定類別的用車服務，那麼由此可以確定出用車行為類別。
在一個實施例中，發送方的標識中可以攜帶業務類型，由此從發送方的標識中直接提取出業務類型。
在本說明書另一實施例中，根據所述用車帳單資訊的發送方的標識獲取用車行為類別，可以包括：
根據所述用車帳單資訊的發送方標識，從資料庫中獲取所述發送方的業務類型；
根據所述發送方的業務類型確定所述用車行為類別。
在本說明書實施例中，用車收費系統與發送方之間存在業務關係，用車收費系統中可以儲存發送方的標識與業務類型之間的對應關係，這樣用車收費系統可以從自身資料庫中獲取到發送方的業務類型。
在本說明書實施例中，確定所述用車帳單資訊所對應的用車行為類別，可以包括：
若所述用車帳單資訊中包含所述用車行為類別，則從所述用車帳單資訊中獲取所述用車行為類別。
步驟305：獲取所述用車行為類別對應的支付管道。
在本說明書實施例中，不同的用車行為類別可以對應不同的支付管道，這可以是默認設定，還可以由使用者設定。
在本說明書實施例中，獲取所述用車行為類別對應的支付管道，可以包括：
根據所述目標車的標識，從資料庫中獲取所述支付管道與用車行為類別之間的對應關係；
利用獲取的所述支付管道與用車行為類別之間的對應關係確定所述目標車的用車行為類別對應的支付管道。
在本說明書實施例中，獲取所述用車行為類別對應的支付管道，可以包括：
向所述目標車所屬使用者的用戶端發送所述用車行為類別對應的支付管道推薦資訊；
根據所述使用者對所述支付管道資訊的回饋確定所述用車行為類別資訊對應的支付管道。
步驟307：根據所述用車帳單資訊，向所述支付管道對應的結算端發送用車支付請求，使得所述結算端根據所述用車支付請求完成支付。
具體地，可以是根據用車帳單資訊產生用車支付請求，將該用車支付請求發送給支付管道對應的結算端。
在本說明書實施例中，在向所述支付管道對應的結算端發送用車支付請求之前，還包括：
根據所述目標車的標識獲取所述目標車所屬使用者的帳戶資訊；
這樣，根據所述用車帳單資訊，向所述支付管道對應的結算端發送用車支付請求，可以包括：
根據所述用車帳單資訊和所述使用者的帳戶資訊，向所述支付管道對應的結算端發送用車支付請求。
這樣，結算端從使用者帳戶中扣除繳費金額，並將繳費金額轉入用車收費系統。那麼，之後，用車收費系統與採集終端之間進行費用結算。
本說明書實施例記載的方法提供了一種用車的支付管道選擇方案，根據用車行為類別選擇對應的支付管道，改善單一用車行為類別造成的支付管道唯一性，給予使用者更多的支付選擇，提升使用者體驗。
圖4為本說明書實施例提出的一種用車支付系統提供的用戶端介面示意圖。
參考圖4(a)，提供用車支付管道設置介面，介面中展示高速、停車、加油及其他用車行為類別；
當接收到使用者對停車對應的用車管道更改操作，則跳轉至圖4(b)所示介面，該介面提供支付管道1、支付管道2、支付1到3及支付管道4，供使用者選擇。例如，當使用者選擇支付管道2，則支付管道2高亮顯示。
圖5本說明書實施例提出的一種用車支付裝置的結構示意圖。
本裝置可以包括：
接收模組501，接收目標車的用車帳單資訊；
確定模組502，確定所述用車帳單資訊所對應的用車行為類別；
獲取模組503，獲取所述用車行為類別對應的支付管道；
發送模組504，根據所述用車帳單資訊，向所述支付管道對應的結算端發送用車支付請求，使得所述結算端根據所述用車支付請求完成支付。
可選地，確定所述用車帳單資訊所對應的用車行為類別，包括：
根據所述用車帳單資訊的發送方的標識獲取用車行為類別。
可選地，確定所述用車帳單資訊所對應的用車行為類別，包括：
若所述用車帳單資訊中包含所述用車行為類別，則從所述用車帳單資訊中獲取所述用車行為類別。
可選地，獲取所述用車行為類別對應的支付管道，包括：
根據所述目標車的標識，從資料庫中獲取所述支付管道與用車行為類別之間的對應關係；
利用獲取的所述支付管道與用車行為類別之間的對應關係確定所述目標車的用車行為類別對應的支付管道。
可選地，獲取所述用車行為類別對應的支付管道，包括：
向所述目標車所屬使用者的用戶端發送所述用車行為類別對應的支付管道推薦資訊；
根據所述使用者對所述支付管道資訊的回饋確定所述用車行為類別資訊對應的支付管道。
本說明書實施例記載的裝置提供一種用車支付管道選擇方案，具體地根據用車行為類別選擇對應的支付管道，改善單一用車行為類別造成的支付管道唯一性，給予使用者更多的支付選擇，提升使用者體驗。
基於同一個發明構思，本說明書實施例還提供了一種電子設備，包括：
處理器；以及
被配置成儲存電腦程式的記憶體，所述電腦程式在被執行時使所述處理器執行以下操作：
接收目標車的用車帳單資訊；
確定所述用車帳單資訊所對應的用車行為類別；
獲取所述用車行為類別對應的支付管道；
根據所述用車帳單資訊，向所述支付管道對應的結算端發送用車支付請求，使得所述結算端根據所述用車支付請求完成支付。
基於同一發明構思，本說明書實施例中還提供了一種電腦可讀儲存媒體，包括與電子設備結合使用電腦程式，所述電腦程式可被處理器執行以完成以下步驟：
接收目標車的用車帳單資訊；
確定所述用車帳單資訊所對應的用車行為類別；
獲取所述用車行為類別對應的支付管道；
根據所述用車帳單資訊，向所述支付管道對應的結算端發送用車支付請求，使得所述結算端根據所述用車支付請求完成支付。
在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)，如調變的資料信號和載波。
還需要說明的是，用語“包括”、“包含”或者其任何其他變體意在涵蓋非排他性的包含，從而使得包括一系列要素的過程、方法、商品或者設備不僅包括那些要素，而且還包括沒有明確列出的其他要素，或者是還包括為這種過程、方法、商品或者設備所固有的要素。在沒有更多限制的情況下，由語句“包括一個……”限定的要素，並不排除在包括所述要素的過程、方法、商品或者設備中還存在另外的相同要素。
本申請可以在由電腦執行的電腦可執行指令的一般上下文中描述，例如程式模組。一般地，程式模組包括執行特定任務或實現特定抽象資料類型的常式、程式、物件、元件、資料結構等等。也可以在分散式運算環境中實踐本申請，在這些分散式運算環境中，由通過通信網路而被連接的遠端處理設備來執行任務。在分散式運算環境中，程式模組可以位於包括存放裝置在內的本地和遠端電腦儲存媒體中。
本說明書中的各個實施例均採用循序的方式描述，各個實施例之間相同相似的部分互相參見即可，每個實施例重點說明的都是與其他實施例的不同之處。尤其，對於系統實施例而言，由於其基本相似於方法實施例，所以描述的比較簡單，相關之處參見方法實施例的部分說明即可。
以上所述僅為本申請的實施例而已，並不用於限制本申請。對於本領域技術人員來說，本申請可以有各種更改和變化。凡在本申請的精神和原理之內所作的任何修改、等同替換、改進等，均應包含在本申請的申請專利範圍之內。A study of the existing technology found that in the electronic payment mode of the car, the payment channel is single and the user experience is insufficient.
The embodiment of this specification proposes a car payment method, device, system and electronic equipment. The substantive solution is to determine the car usage behavior category corresponding to the car usage bill information for the car usage bill information of the target car, and obtain The payment channel corresponding to the car usage behavior category sends a car payment request to the settlement terminal corresponding to the payment channel according to the car usage bill information, so that the settlement terminal completes the payment according to the car payment request. The solution described in the embodiments of this specification provides a payment channel selection solution, specifically selecting the corresponding payment channel according to the type of car usage behavior, improving the uniqueness of the payment channel caused by a single car usage behavior category, giving users more payment options, and improving usage Experience.
In order to make the purpose, technical solutions and advantages of the present application clearer, the technical solutions of the present application will be described clearly and completely in conjunction with specific embodiments of the specification and the corresponding drawings. Obviously, the described embodiments are only a part of the embodiments in this specification, rather than all the embodiments. Based on the embodiments in this specification, all other embodiments obtained by a person of ordinary skill in the art without making progressive work fall within the scope of protection of this application.
The technical solutions provided by the embodiments of this specification will be described in detail below with reference to the accompanying drawings.
Fig. 1 is a schematic structural diagram of a car payment system proposed in an embodiment of this specification.
The car payment system described in the embodiment of this specification may include:
The collection terminal 101 collects car usage behavior information of the target car C, and generates car usage bill information based on the car usage behavior information;
The car usage charging system 102 receives the car usage bill information from the collection terminal 101, determines the car usage behavior category corresponding to the car usage bill information, and obtains the payment channel corresponding to the car usage category, according to Generating a car payment request from the car use bill information;
The settlement terminal 103 receives the car payment request from the car payment system 102 and completes the payment according to the car payment request.
In the embodiment of this specification, the collection terminal 101 can use infrared scanning recognition technology, or photographic recognition technology, or laser scanning recognition technology to identify the target vehicle C and the vehicle usage information.
In another embodiment of this specification, the car payment system may further include:
In the vehicle-mounted terminal, when a communication connection is established with the collection terminal, the collection terminal collects vehicle usage information of the target vehicle.
A communication connection can be established between the collection terminal 101 and the target vehicle C, and the vehicle usage behavior information of the target vehicle C can be collected by identifying the target vehicle C. For example, using IC card identification technology or non-contact radio frequency identification technology to identify the target vehicle C and its use behavior information. For example, in the wireless communication recognition technology, the on board unit (OBU) is also called transponder (Transponder) or electronic tag (Tag) pre-installed in the target vehicle C, and the road side unit (Road side unit, RSU) and sensors. When a vehicle passes, the sensor senses the vehicle, the RSU sends out an inquiry signal, and the OBU responds, and conducts two-way communication and data exchange. Then the OBU collects the license plate information of the target vehicle C and vehicle usage information.
The car use behavior information may include one or more of driving, parking, and refueling on a specified road section. The traffic on the designated road section may include the traffic on the toll road, such as high-speed, bridge, etc., and there is no restriction on the specific scene.
Car usage bill information is a payment slip obtained by charging for car usage.
The payment channel can be a third-party payment channel, bank card or other payment channel, which is not specifically limited here.
Using the system described in the embodiment of this specification, the corresponding payment channel can be selected according to the type of car usage behavior, which improves the uniqueness of the payment channel caused by a single car usage behavior category, gives users more payment options, and improves user experience.
Fig. 2 is a sequence diagram of an application example of a car payment method based on a car payment system proposed in an embodiment of this specification.
Step 202: When the target vehicle 20 enters the preset lane, the parking system 21 recognizes the vehicle identification information and collects the time of entry.
The parking system 21 is an application example of the collection terminal, and the admission time is a type of car usage information.
Step 204: When the target vehicle 20 drives out of the preset lane, the parking system 21 recognizes the vehicle identification information and collects the exit time.
Step 206: The parking system 21 matches the same target vehicle 20 based on the two vehicle identification information, calculates the parking time and parking fee of the target vehicle 20 according to the entrance time and exit time, and generates parking bill information.
Step 208: The parking system 21 sends the parking bill information to the car charging system 22.
Step 210: The car usage charging system 22 determines that the car usage behavior category is parking.
Step 212: The vehicle toll collection system 22 determines the current payment channel according to the corresponding relationship between the parking and the payment channel;
Step 214: The car toll collection system 22 generates a payment request based on the parking bill information, and sends the payment request to the settlement terminal 23 on the side of the determined payment channel;
Step 216: The settlement terminal 23 receives the payment request, and completes the payment according to the payment request.
Fig. 3 is a flowchart of a car payment method proposed in an embodiment of this specification. The execution subject of this method can be a car toll system.
Step 301: Receive the vehicle bill information of the target vehicle.
The car usage bill information recorded in the embodiment of this specification may be the payment bill information generated by the collection terminal by collecting the car usage behavior.
The car usage bill information may include one or more of the vehicle identification of the target car, the payment amount, and car usage behavior information.
Step 303: Determine the car usage behavior category corresponding to the car usage bill information.
The car usage behavior category corresponding to the car usage bill information reflects the category of the car usage behavior that generated the car usage bill information.
In the embodiment of this specification, determining the car usage behavior category corresponding to the car usage bill information may include:
Acquire the car usage behavior category according to the identifier of the sender of the car usage bill information.
The identifier of the sender of the car bill information characterizes the type of business the sender is engaged in. This type of business provides the sender with a specific type of car service, so that the type of car usage behavior can be determined from this.
In one embodiment, the service type can be carried in the identifier of the sender, thereby directly extracting the service type from the identifier of the sender.
In another embodiment of the present specification, acquiring the car usage behavior category according to the identifier of the sender of the car usage bill information may include:
Obtain the business type of the sender from the database according to the sender identifier of the vehicle bill information;
The vehicle usage behavior category is determined according to the service type of the sender.
In the embodiment of this specification, there is a business relationship between the car toll system and the sender. The car toll system can store the corresponding relationship between the sender’s identification and the business type, so that the car toll system can use its own database The service type of the sender is obtained in.
In the embodiment of this specification, determining the car usage behavior category corresponding to the car usage bill information may include:
If the car usage bill information includes the car usage behavior category, then the car usage behavior category is obtained from the car usage bill information.
Step 305: Obtain the payment channel corresponding to the vehicle usage behavior category.
In the embodiment of this specification, different types of car use behaviors can correspond to different payment channels, which can be a default setting or can be set by the user.
In the embodiment of this specification, obtaining the payment channel corresponding to the car usage behavior category may include:
According to the identifier of the target vehicle, obtain the correspondence between the payment channel and the vehicle usage behavior category from the database;
The obtained corresponding relationship between the payment channel and the car usage behavior category is used to determine the payment channel corresponding to the car usage behavior category of the target vehicle.
In the embodiment of this specification, obtaining the payment channel corresponding to the car usage behavior category may include:
Sending the payment channel recommendation information corresponding to the car usage behavior category to the user terminal of the user to which the target car belongs;
Determine the payment channel corresponding to the car use behavior category information according to the user's feedback on the payment channel information.
Step 307: Send a car payment request to the settlement terminal corresponding to the payment channel according to the car bill information, so that the settlement terminal completes the payment according to the car payment request.
Specifically, the vehicle payment request may be generated based on the vehicle bill information, and the vehicle payment request may be sent to the settlement terminal corresponding to the payment channel.
In the embodiment of this specification, before sending a car payment request to the settlement terminal corresponding to the payment channel, the method further includes:
Obtaining the account information of the user to which the target car belongs according to the identifier of the target car;
In this way, according to the car bill information, sending a car payment request to the settlement terminal corresponding to the payment channel may include:
According to the vehicle bill information and the user's account information, a vehicle payment request is sent to the settlement terminal corresponding to the payment channel.
In this way, the settlement terminal deducts the payment amount from the user account and transfers the payment amount to the car charging system. Then, after that, the fee settlement is performed between the car toll system and the collection terminal.
The method recorded in the embodiment of this specification provides a payment channel selection scheme for car use, which selects the corresponding payment channel according to the car use behavior category, improves the uniqueness of the payment channel caused by a single car use behavior category, and gives users more payment options , To enhance the user experience.
Fig. 4 is a schematic diagram of a user terminal interface provided by a car payment system according to an embodiment of the specification.
Refer to Figure 4(a) to provide an interface for setting up car payment channels, which displays high-speed, parking, refueling, and other types of car usage;
When receiving the user's operation of changing the car channel corresponding to the parking, it will jump to the interface shown in Figure 4(b), which provides payment channel 1, payment channel 2, payment 1 to 3, and payment channel 4 for users select. For example, when the user selects payment channel 2, payment channel 2 is highlighted.
Fig. 5 is a schematic structural diagram of a car payment device proposed in an embodiment of this specification.
This device can include:
The receiving module 501 receives the vehicle bill information of the target vehicle;
The determining module 502 determines the type of car usage behavior corresponding to the car usage bill information;
The obtaining module 503 obtains the payment channel corresponding to the car usage behavior category;
The sending module 504 sends a car payment request to the settlement terminal corresponding to the payment channel according to the car bill information, so that the settlement terminal completes the payment according to the car payment request.
Optionally, determining the car usage behavior category corresponding to the car usage bill information includes:
Acquire the car usage behavior category according to the identifier of the sender of the car usage bill information.
Optionally, determining the car usage behavior category corresponding to the car usage bill information includes:
If the car usage bill information includes the car usage behavior category, then the car usage behavior category is obtained from the car usage bill information.
Optionally, obtaining the payment channel corresponding to the vehicle usage behavior category includes:
According to the identifier of the target vehicle, obtain the correspondence between the payment channel and the vehicle usage behavior category from the database;
The obtained corresponding relationship between the payment channel and the car usage behavior category is used to determine the payment channel corresponding to the car usage behavior category of the target vehicle.
Optionally, obtaining the payment channel corresponding to the vehicle usage behavior category includes:
Sending the payment channel recommendation information corresponding to the car usage behavior category to the user terminal of the user to which the target car belongs;
Determine the payment channel corresponding to the car use behavior category information according to the user's feedback on the payment channel information.
The device described in the embodiment of this specification provides a payment channel selection scheme for car use, specifically selecting the corresponding payment channel according to the type of car use behavior, improving the uniqueness of the payment channel caused by a single car use behavior category, and giving users more payment options , To enhance the user experience.
Based on the same inventive concept, the embodiments of this specification also provide an electronic device, including:
Processor; and
The memory is configured to store a computer program, and when the computer program is executed, the processor performs the following operations:
Receive vehicle billing information of the target vehicle;
Determine the type of car usage behavior corresponding to the car usage bill information;
Obtain the payment channel corresponding to the vehicle usage behavior category;
According to the car bill information, a car payment request is sent to the settlement terminal corresponding to the payment channel, so that the settlement terminal completes the payment according to the car payment request.
Based on the same inventive concept, the embodiments of this specification also provide a computer-readable storage medium, including a computer program used in combination with an electronic device, and the computer program can be executed by a processor to complete the following steps:
Receive vehicle billing information of the target vehicle;
Determine the type of car usage behavior corresponding to the car usage bill information;
Obtain the payment channel corresponding to the vehicle usage behavior category;
According to the car bill information, a car payment request is sent to the settlement terminal corresponding to the payment channel, so that the settlement terminal completes the payment according to the car payment request.
In the 1990s, the improvement of a technology can be clearly distinguished from the improvement of the hardware (for example, the improvement of the circuit structure of diodes, transistors, switches, etc.) or the improvement of the software (for the process of the method). Improve). However, with the development of technology, the improvement of many methods and processes of today can be regarded as a direct improvement of the hardware circuit structure. Designers almost always get the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that the improvement of a method flow cannot be realized by the hardware entity module. For example, a Programmable Logic Device (PLD) (such as Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic function is determined by the user’s programming of the device . It is designed by the designer to "integrate" a digital system on a PLD without having to ask the chip manufacturer to design and produce a dedicated integrated circuit chip. Moreover, nowadays, instead of manually making integrated circuit chips, this kind of programming is mostly realized by using "logic compiler" software, which is similar to the software compiler used in program development and writing. The source code before compilation must also be written in a specific programming language, which is called Hardware Description Language (HDL), and there is not only one HDL, but many, 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., Currently the most commonly used are VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also be aware that only a little logic programming of the method flow using the above hardware description languages and programming into an integrated circuit can easily obtain a hardware circuit that implements the logic method flow.
The controller can be implemented in any suitable manner. For example, the controller can be a microprocessor or a processor, and a computer readable program code (such as software or firmware) that can be executed by the (micro) processor is stored. Media, logic gates, switches, application specific integrated circuits (ASIC), 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 a 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 program code manner, it is entirely possible to design the method steps with logic programming to make the controller use logic gates, switches, integrated circuits for special applications, and programmable logic. Controllers and embedded microcontrollers can realize the same functions. Therefore, such a controller can be regarded as a hardware component, and the devices included in it for realizing various functions can also be regarded as a structure within the hardware component. Or even, the device for realizing various functions can be regarded as both a software module for realizing the method and a structure within a hardware component.
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. Specifically, the computer can be, for example, a personal computer, a laptop computer, 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, a wearable Device or any combination 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 this application, the functions of each unit can be implemented in the same or multiple software and/or hardware.
Those skilled in the art should understand that the embodiments of the present invention can be provided as a method, a system, or a computer program product. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware. Moreover, the present invention can be in the form of computer program products implemented on one or more computer-usable storage media (including but not limited to disk memory, CD-ROM, optical memory, etc.) containing computer-usable program codes. .
The present invention is described with reference to flowcharts and/or block diagrams of methods, equipment (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 the combination of processes and/or blocks in the flowchart and/or block diagram can be realized by computer program instructions. These computer program instructions can be provided to the processors of general-purpose computers, dedicated computers, embedded processors, or other programmable data processing equipment to generate a machine that can be executed by the processors of the computer or other programmable data processing equipment A device for realizing the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram is generated.
These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing equipment to work in a specific manner, so that the instructions stored in the computer-readable memory generate a manufactured product including the instruction device The instruction device realizes the functions specified in one process or multiple processes in the flowchart and/or one block or multiple 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 operation steps are executed on the computer or other programmable equipment to generate computer-implemented processing, so that the computer or other programmable equipment The instructions executed above provide steps for implementing functions specified in a flow or multiple flows in the flowchart and/or a block or multiple blocks in the block diagram.
In a typical configuration, the computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
Memory may include non-permanent memory in computer-readable media, random access memory (RAM) and/or non-volatile memory, such as read-only memory (ROM) or flash memory (flash). RAM). Memory is an example of computer-readable media.
Computer-readable media include permanent and non-permanent, removable and non-removable media, and information storage can be realized by any method or technology. Information can be computer-readable instructions, data structures, program modules, 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 programmable read-only memory (EEPROM), flash memory or other memory technologies, read-only CD-ROM (CD-ROM), digital multi-function Optical discs (DVD) or other optical storage, cassette tapes, magnetic tape storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by computing devices. According to the definition in this article, computer-readable media does not include transitory media, such as modulated data signals and carrier waves.
It should also be noted that the terms "include", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, product or equipment including a series of elements includes not only those elements, but also Other elements that are not explicitly listed, or also include elements inherent to such processes, methods, commodities, or equipment. If there are no more restrictions, the element defined by the sentence "including a..." does not exclude the existence of other identical elements in the process, method, commodity, or equipment that includes the element.
This application can be described in the general context of computer-executable instructions executed by a computer, such as a program module. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or realize specific abstract data types. This application can also be implemented in a distributed computing environment. In these distributed computing environments, remote processing devices connected through a communication network perform tasks. In a distributed computing environment, program modules can be located in local and remote computer storage media including storage devices.
The various embodiments in this specification are described in a sequential manner, and the same or similar parts between the various embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, as for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and for related parts, please refer to the part of the description of the method embodiment.
The above descriptions are only examples of this application, and are not intended to limit this application. For those skilled in the art, this application can 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 of this application.
