WO2023000954A1 - 票据处理 - Google Patents

票据处理 Download PDF

Info

Publication number
WO2023000954A1
WO2023000954A1 PCT/CN2022/103340 CN2022103340W WO2023000954A1 WO 2023000954 A1 WO2023000954 A1 WO 2023000954A1 CN 2022103340 W CN2022103340 W CN 2022103340W WO 2023000954 A1 WO2023000954 A1 WO 2023000954A1
Authority
WO
WIPO (PCT)
Prior art keywords
ticket
bill
short message
format data
link
Prior art date
Application number
PCT/CN2022/103340
Other languages
English (en)
French (fr)
Inventor
李锵
Original Assignee
支付宝(杭州)信息技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 支付宝(杭州)信息技术有限公司 filed Critical 支付宝(杭州)信息技术有限公司
Publication of WO2023000954A1 publication Critical patent/WO2023000954A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
    • G06F16/33—Querying
    • G06F16/3331—Query processing
    • G06F16/334—Query execution
    • G06F16/3344—Query execution using natural language analysis
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F40/00—Handling natural language data
    • G06F40/20—Natural language analysis
    • G06F40/258—Heading extraction; Automatic titling; Numbering
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F40/00—Handling natural language data
    • G06F40/20—Natural language analysis
    • G06F40/279—Recognition of textual entities
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/04—Billing or invoicing

Definitions

  • This document relates to the technical field of data processing, in particular to a bill processing method and device.
  • Electronic bills are vouchers issued and received by enterprises or individuals in the process of buying and selling goods, providing or receiving services, and engaging in other business activities.
  • the content includes the name, quality, and negotiated price of products or services provided to buyers.
  • the download link of the bill is usually provided to the user via email or short message, and the user needs to manually click on the download link to trigger the download of the bill to complete the acquisition of the electronic bill.
  • the bill processing method includes: obtaining a short message stored in a user terminal and matching it with a bill keyword to obtain a bill short message matched with the bill keyword; identifying the format data of the bill short message, and The format data is matched with the historical format data; if the matching fails, the ticket link contained in the ticket short message is parsed to obtain the ticket.
  • a bill processing device including: a short message matching module configured to acquire a short message stored in a user terminal and match it with a bill keyword, and obtain a short message matching the bill keyword The note short message; the format data matching module is configured to identify the format data of the note short message, and matches the format data with the historical format data; the note link analysis module is configured to, in the case of a matching failure, Analyzing the ticket link included in the ticket short message to acquire the ticket.
  • One or more embodiments of the present specification provide a bill processing device, including: a processor; and a memory configured to store computer-executable instructions.
  • the processor when the computer-executable instructions are executed, the processor: obtains the short message stored in the user terminal and matches it with the ticket keyword, obtains the ticket short message matched with the ticket keyword; identifies the ticket format data of the short message, and match the format data with the historical format data; if the matching fails, parse the ticket link contained in the ticket short message to obtain the ticket.
  • One or more embodiments of this specification provide a storage medium for storing computer-executable instructions.
  • the computer-executable instructions When executed, the following process is implemented: obtain the short message stored in the user terminal and compare it with the ticket keyword Matching, obtaining the bill short message matched with the bill keyword; identifying the format data of the bill short message, and matching the format data with the historical format data; if the matching fails, parsing the bill short message containing Ticket link for ticket acquisition.
  • Fig. 1 is a processing flowchart of a bill processing method provided by one or more embodiments of this specification
  • FIG. 2 is a processing flowchart of a bill processing method applied to a short message scenario provided by one or more embodiments of this specification;
  • Fig. 3 is a schematic diagram of a bill processing device provided by one or more embodiments of this specification.
  • Fig. 4 is a schematic structural diagram of a bill processing device provided by one or more embodiments of this specification.
  • FIG. 1 it shows a processing flow chart of a bill processing method provided by this embodiment
  • FIG. 2 shows a processing flow chart of a bill processing method applied to a short message scenario provided by this embodiment.
  • the bill processing method provided in this embodiment specifically includes steps S102 to S106.
  • step S102 the short message stored in the user terminal is obtained and matched with the ticket keyword, and the ticket short message matched with the ticket keyword is obtained.
  • the bill processing method by matching the short message stored in the user terminal with the bill keyword, screens out the bill short message matching the bill keyword, and extracts the format data contained in the bill short message, and further Match the extracted format data with the historical format data to judge whether the currently processed bill short message is provided by the service provider that has recorded the historical format data, if the currently processed bill short message is provided by the service provider that has recorded the historical format data Provided, the ticket can be obtained according to the recorded historical format data of the service provider.
  • the ticket can be processed by parsing the ticket short message Acquisition, so that through the automatic matching and parsing process of the short message, the automation of the ticket processing process of the short message is realized, and the efficiency of obtaining the ticket from the short message is improved, so as to improve the ticket service experience of the user.
  • the bill keyword in this embodiment refers to the pre-configured keyword related to the bill.
  • the short message includes a short message received through a short message application, and/or a message pushed through an application or other communication methods.
  • the short message is stored in the user terminal of the user.
  • authorization processing for extracting the short message is required.
  • the authorization process is specifically carried out in the following manner: send an authorization reminder of the short message service to the user terminal; the short message service refers to a service or application for receiving and managing short messages in the user terminal; according to the user terminal According to the authorization confirmation instruction submitted by the authorization reminder, the authorization processing of the short message service is performed.
  • this embodiment provides an optional implementation mode.
  • the matching process of the bill keyword is specifically implemented in the following manner: call the short message service of the user terminal according to user authorization, read the short message stored in the short message list of the short message service; Any one in the message, this short message is matched with the bill keyword in the keyword storehouse respectively; Judge whether this short message matches with at least one bill keyword in the said keyword storehouse; If so, determine that this short message is all The note short message; if not, it is determined that the short message is a non-note short message.
  • Step S104 identifying the format data of the note short message, and matching the format data with the historical format data.
  • the format data described in this embodiment refers to the message type used to determine the short message, or data related to the keywords of the message content, such as the beginning of a short message in the short message list of the short message application of the user terminal.
  • “[xx invoice]” according to "[xx invoice]”, it can be determined that the short message is an invoice-type short message, and the service provider that issues and sends the invoice short message can be determined accordingly, then "[xx invoice]” is determined It is the format data of the short message.
  • the format data is determined based on the ticket service information.
  • the bill service information refers to data information related to the name and logo of the bill service provider, or data information related to the bill issued by the bill service provider.
  • the bill service information “[xx invoice]” extracted from the short message will be used as the format data of the short message.
  • the format data contained in the short message is identified from the overall content of the short message, so that the format data obtained through identification can be more Accurately, specifically, during the identification process, the text information contained in the note short message is identified through a semantic identification algorithm, and the format data is determined according to the text information.
  • the short message does not contain keywords such as "[xx invoice]" that clearly identifies the short message service information
  • the short message is first identified through the semantic recognition algorithm to obtain the text information contained in the short message, and then the text information is extracted from the text information.
  • the keywords related to the service information are extracted, and finally the format data of the short message is determined according to the extracted keywords.
  • the matching process is performed using the following optional implementation manner: match the ticket service information contained in the format data with the ticket service information contained in the historical format data; if the matching is successful, then Indicates that there is historical format data matching the current note short message in the format library, and the ticket acquisition of the note short message can be performed through the historical format data in the format library; otherwise, if the matching fails, it indicates that there is no current note short message in the format library The matched historical format data cannot be used to obtain the ticket of the ticket short message through the historical format data in the format library.
  • the format data of the note short message is matched with each historical format data in the format library in a traversal manner
  • the following matching process is carried out for the currently traversed historical format data: using a similarity algorithm or a matching model to calculate the similarity or matching degree between the format data of the bill short message and the currently traversed historical format data; for example, the format data contains The bill service information and the bill service information contained in the historical format data are input into the similarity algorithm or matching model to calculate the similarity or matching degree.
  • step S106 If there is no historical format data with a similarity degree or a matching degree greater than the preset threshold after the traversal is completed, it is determined that the matching fails, and the following step S106 can be performed.
  • the historical format data with similarity or matching degree greater than the preset threshold after the traversal is completed it is determined that the matching is successful, and the historical format data with the highest similarity or matching degree is determined as the target format data, that is: the format data matched history format data, and based on the note download configuration contained in the note short message and the note download configuration corresponding to the target format data, carry out the ticket acquisition processing of the note short message, if the matching is successful, it indicates that there is a current
  • the historical format data of bill short message matching can carry out the bill acquisition of described bill short message through historical format data in the format storehouse; On the contrary, if matching fails, then show that there is no historical format data of current bill short message matching in the format storehouse, The ticket acquisition of the ticket short message cannot be performed through the historical format data in the format library.
  • the returned result does not directly contain the ticket file.
  • the process of triggering the ticket link and performing operation processing on the link access result is recorded and configured as corresponding configuration information.
  • the configuration information obtained by executing the configuration If it is possible to realize access ticket links and perform operations on link access results to download ticket files, then the configuration information is referred to as: "configuration information for performing access ticket links and downloading ticket files included in link access results".
  • the ticket link refers to a link that provides access and ticket download.
  • the ticket download configuration includes at least one of the following: performing a ticket link and downloading the configuration information of the ticket file included in the link access result, performing a ticket link and executing the link corresponding to the ticket download channel in the link access result Download triggers an action to download the configuration information of the ticket file.
  • the format In the process of matching the data with the historical format data the following optional implementation manner is used for matching processing: the text information contained in the format data is matched with the ticket service information contained in the historical format data.
  • the format data of the note short message is matched with each historical format data in the format library in a traversal manner
  • the following matching process is carried out for the currently traversed historical format data: using a similarity algorithm or a matching model to calculate the similarity or matching degree between the format data of the bill short message and the currently traversed historical format data; for example, the format data contains The text information contained in the historical format data and the bill service information contained in the historical format data are input into the similarity algorithm or matching model to calculate the similarity or matching degree; If the matching fails, just execute the following step S106; if there is historical format data whose similarity or matching degree is greater than the preset threshold after the traversal, it is determined that the matching is successful, and the historical format data with the highest similarity or matching degree is determined as the target
  • the format data that is, the historical format data matched by the format data, and based on the ticket link contained in the ticket short message and the ticket download configuration
  • Step S106 if the matching fails, parse the ticket link contained in the ticket short message to acquire the ticket.
  • the ticket is obtained by analyzing the ticket link contained in the ticket short message.
  • parsing the ticket link contained in the ticket short message to obtain the ticket includes: judging whether the ticket short message contains a ticket link; if so, accessing the ticket link , and determine whether the ticket file is included in the link access result of the ticket link; if it is included, download and store the ticket file; if it is not included, perform the operations provided by the following optional implementation modes for ticket download processing: traversal format The historical format data stored in the library, and the following processing for the currently traversed historical format data: according to the ticket download configuration corresponding to the currently traversed historical format data, access the ticket link contained in the ticket short message, and perform ticket download processing ;If the ticket download is successful, terminate the traversal; if the ticket download fails, continue traversal; if not, the ticket short message cannot be processed by parsing the ticket link, and the short message of the ticket cannot be processed or skipped That's it.
  • this embodiment enriches the format data in the format library by means of a dynamically updated format library, so as to improve the success rate of matching the format data of the bill short message with the historical format data in the format library, and then improve the format data of the bill. Processing efficiency.
  • the format library is dynamically updated by recording the correspondence between the format data and the ticket download configuration for which the ticket download is successful, and updating the format data into the format library.
  • the ticket link contained in the ticket short message is parsed to obtain the ticket, or, based on the ticket link contained in the ticket short message Ticket link and ticket download configuration corresponding to the target format data
  • the electronic ticket obtained after the ticket acquisition is executed is updated to the ticket service
  • the list of tickets will be displayed when an access request submitted through the ticket access portal of the ticket service is received.
  • the ticket service includes a ticket service application installed in the user terminal, or a ticket service subroutine or applet loaded in a third-party application in the user terminal.
  • the bill processing method applied to a short message scene specifically includes Step S202 to step S216.
  • Step S202 call the short message service of the user terminal according to the user authorization, and read the short messages stored in the short message list of the short message service.
  • Step S204 for any one of the read short messages, match the short message with the receipt keywords in the keyword database.
  • Step S206 judging whether the short message matches at least one bill keyword in the keyword database; if yes, determine that the short message is a bill short message, and execute step S208; if not, determine that the short message is a non-bill short message.
  • Step S208 extracting the bill service information contained in the bill short message, and determining format data based on the bill service information.
  • Step S210 matching the ticket service information contained in the format data with the ticket service information contained in the historical format data; if the matching is successful, downloading the ticket corresponding to the historical format data based on the ticket link contained in the ticket short message and the format data matching Configure to perform ticket acquisition processing of ticket short messages.
  • Step S212 if the matching fails, judge whether the ticket short message contains a ticket link; if yes, access the ticket link, and execute step S212; if not, do not process.
  • Step S214 if the link access result returned after the ticket link is accessed contains the ticket file, download the ticket file included in the link visit result.
  • the link access result returned after the note link is accessed does not contain the note file, then traverse the historical format data stored in the format library, and perform the following processing on the currently traversed historical format data: correspond to the currently traversed historical format data According to the ticket download configuration, visit the ticket link contained in the ticket short message, and perform ticket download processing; if the ticket download is successful, terminate the traversal; if the ticket download fails, continue the traversal.
  • Step S216 updating the downloaded electronic ticket to the ticket list of the ticket service, so as to display the ticket list when an access request submitted through the ticket access portal of the ticket service is received.
  • An embodiment of a bill processing device provided in this specification is as follows: In the above embodiments, a bill processing method is provided, and correspondingly, a bill processing device is also provided, which will be described below with reference to the accompanying drawings.
  • FIG. 3 it shows a schematic diagram of a bill processing device provided in this embodiment.
  • the description is relatively simple. For relevant parts, please refer to the corresponding description of the method embodiment provided above.
  • the device embodiments described below are illustrative only.
  • This embodiment provides a bill processing device, including: a short message matching module 302, configured to obtain a short message stored in a user terminal and match it with a bill keyword, and obtain a bill short message matching the bill keyword; format The data matching module 304 is configured to identify the format data of the note short message, and matches the format data with the historical format data; the note link analysis module 306 is configured to analyze the format data in the case of a matching failure.
  • the bill processing device further includes: a target format data determination module, configured to determine the historical format data matched by the format data as the target format data if the matching is successful; the bill acquisition processing module, It is configured to perform ticket acquisition processing of the ticket short message based on the ticket link contained in the ticket short message and the ticket download configuration corresponding to the target format data.
  • a target format data determination module configured to determine the historical format data matched by the format data as the target format data if the matching is successful
  • the bill acquisition processing module It is configured to perform ticket acquisition processing of the ticket short message based on the ticket link contained in the ticket short message and the ticket download configuration corresponding to the target format data.
  • the bill link parsing module 306 includes: a bill link judging submodule configured to judge whether the bill short message contains a bill link; if so, run the link access result judging submodule; the link access result The judging submodule is configured to access the ticket link, and judges whether the ticket file is included in the link access result of the ticket link; if so, run the ticket file download submodule; the ticket file download submodule is configured to download And store the ticket file.
  • the ticket download processing submodule is run, and the ticket download processing submodule is configured to: traverse the historical format data stored in the format library, And for the historical format data currently traversed, the following processing is performed: according to the bill download configuration corresponding to the historical format data currently traversed, access the bill link contained in the bill short message, and perform bill download processing; if the bill download is successful, terminate the traversal ; If the ticket download fails, continue traversing.
  • the bill processing device further includes: a format data update module configured to record the correspondence between the format data and the ticket download configuration that successfully downloads the bill, and update the format data to the format library.
  • a format data update module configured to record the correspondence between the format data and the ticket download configuration that successfully downloads the bill, and update the format data to the format library.
  • the format data matching module 304 includes: a first format data determining submodule configured to extract the ticket service information contained in the ticket short message, and determine the format data based on the ticket service information;
  • the second format data determining submodule is configured to identify the text information contained in the note short message through a semantic recognition algorithm, and determine the format data according to the text information.
  • the format data matching module 304 includes: a first matching submodule configured to match the ticket service information contained in the format data with the ticket service information contained in the historical format data;
  • the second matching submodule is configured to match the text information contained in the format data with the ticket service information contained in the historical format data.
  • the bill processing device further includes: a bill list update module, configured to update the electronic bill obtained after the execution of the bill acquisition into the bill list of the bill service, so that when receiving the bill access through the bill service When an access request is submitted by the portal, the ticket list is displayed.
  • a bill list update module configured to update the electronic bill obtained after the execution of the bill acquisition into the bill list of the bill service, so that when receiving the bill access through the bill service When an access request is submitted by the portal, the ticket list is displayed.
  • the ticket download configuration includes at least one of the following: performing a ticket link and downloading the configuration information of the ticket file included in the link access result, performing a ticket link and executing the link corresponding to the ticket download channel in the link access result Download triggers an action to download the configuration information of the ticket file.
  • FIG. 4 is a schematic structural diagram of a bill processing device provided by one or more embodiments of this specification.
  • a bill processing device provided in this embodiment includes: as shown in FIG. 4 , the bill processing device may have relatively large differences due to different configurations or performances, and may include one or more processors 401 and memory 402, the memory One or more storage applications or data may be stored in 402 .
  • the storage 402 may be a short-term storage or a persistent storage.
  • the application program stored in the memory 402 may include one or more modules (not shown in the figure), and each module may include a series of computer-executable instructions in the bill processing device.
  • the processor 401 may be configured to communicate with the memory 402, and execute a series of computer-executable instructions in the memory 402 on the bill processing device.
  • the bill processing device may also include one or more power sources 403, one or more wired or wireless network interfaces 404, one or more input/output interfaces 405, one or more keyboards 406, and the like.
  • the bill processing device includes a memory, and one or more programs, wherein one or more programs are stored in the memory, and one or more programs may include one or more modules, and each A module may include a series of computer-executable instructions in the ticket processing device, and configured to be executed by one or more processors.
  • the one or more programs include computer-executable instructions for performing the following: obtaining The short message is matched with the bill keyword, and the bill short message matched with the bill keyword is obtained; the format data of the bill short message is identified, and the format data is matched with the historical format data; if the matching fails, Analyzing the ticket link included in the ticket short message to acquire the ticket.
  • An embodiment of a storage medium provided in this specification is as follows: Corresponding to the bill processing method described above, based on the same technical concept, one or more embodiments of this specification also provide a storage medium.
  • the storage medium provided by this embodiment is used to store computer-executable instructions, and when the computer-executable instructions are executed, the following process is implemented: obtain the short message stored in the user terminal and match it with the ticket keyword, and obtain the short message corresponding to the ticket Keyword-matched bill short message; identify the format data of the bill short message, and match the format data with historical format data; if the matching fails, parse the bill link contained in the bill short message to obtain the bill .
  • the improvement of a technology can be clearly distinguished as an improvement in hardware (for example, improvements in circuit structures such as diodes, transistors, switches, etc.) or improvements in software (improvement in method flow).
  • improvements in many current method flows can be regarded as the 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 hardware physical modules.
  • a Programmable Logic Device such as a Field Programmable Gate Array (FPGA)
  • FPGA Field Programmable Gate Array
  • HDL Hardware Description Language
  • the controller may be implemented in any suitable way, for example the controller may take the form of a microprocessor or processor and a computer readable medium storing computer readable program code (such as software or firmware) executable by the (micro)processor , logic gates, switches, application specific integrated circuits (Application Specific Integrated Circuit, 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 part of the control logic of the memory.
  • controller in addition to realizing the controller in a purely computer-readable program code mode, it is entirely possible to make the controller use logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded The same function can be realized in the form of a microcontroller or the like. 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 structures within the hardware component. Or even, means for realizing various functions can be regarded as a structure within both a software module realizing a method and a hardware component.
  • a typical implementing device is a computer.
  • the computer may 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 Combinations of any of these devices.
  • one or more embodiments of this specification may be provided as a method, system or computer program product. Accordingly, one or more embodiments of the present description may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present description may take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.
  • computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to operate in a specific manner, such that the instructions stored in the computer-readable memory produce an article of manufacture comprising instruction means, the instructions
  • the device realizes the function specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.
  • a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
  • processors CPUs
  • input/output interfaces network interfaces
  • memory volatile and non-volatile memory
  • Memory may include non-permanent storage in computer-readable media, in the form of random access memory (RAM) and/or nonvolatile memory such as read-only memory (ROM) or flash RAM. Memory is an example of computer readable media.
  • RAM random access memory
  • ROM read-only memory
  • flash RAM flash random access memory
  • Computer-readable media including both permanent and non-permanent, removable and non-removable media, can be implemented by any method or technology for storage of information.
  • Information may be computer readable instructions, data structures, modules of a program, 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), other types of random access memory (RAM), read only memory (ROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Flash memory or other memory technology, Compact Disc Read-Only Memory (CD-ROM), Digital Versatile Disc (DVD) or other optical storage, A magnetic tape cartridge, disk storage or other magnetic storage device or any other non-transmission medium that can be used to store information that can be accessed by a computing device.
  • computer-readable media excludes transitory computer-readable media, such as modulated data signals and carrier waves.
  • program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types.
  • program modules may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network.
  • program modules may be located in both local and remote computer storage media including storage devices.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Artificial Intelligence (AREA)
  • Business, Economics & Management (AREA)
  • General Engineering & Computer Science (AREA)
  • Computational Linguistics (AREA)
  • Development Economics (AREA)
  • General Health & Medical Sciences (AREA)
  • Audiology, Speech & Language Pathology (AREA)
  • Health & Medical Sciences (AREA)
  • Marketing (AREA)
  • General Business, Economics & Management (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Strategic Management (AREA)
  • Finance (AREA)
  • Economics (AREA)
  • Accounting & Taxation (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

本说明书实施例提供了票据处理方法及装置。其中，所述票据处理方法包括：获取用户终端存储的短消息并与票据关键字进行匹配，获得与所述票据关键字匹配的票据短消息；识别所述票据短消息的格式数据，并将所述格式数据与历史格式数据进行匹配；若匹配失败，解析所述票据短消息中包含的票据链接以进行票据获取。

Description

票据处理 技术领域
本文件涉及数据处理技术领域，尤其涉及一种票据处理方法及装置。
背景技术
电子票据是企业或个人在购销商品、提供或接受服务以及从事其他经营活动中，所开具和收取的凭证，内容包括向购买者提供产品或服务的名称、质量、协议价格等。在开具电子票据的过程中，通常会通过邮件或者短消息的方式携带票据下载链接提供给用户，需要用户手动点击触发票据下载链接进行票据的下载，才能完成电子票据的获取。
发明内容
本说明书一个或多个实施例提供了一种票据处理方法。所述票据处理方法，包括：获取用户终端存储的短消息并与票据关键字进行匹配，获得与所述票据关键字匹配的票据短消息；识别所述票据短消息的格式数据，并将所述格式数据与历史格式数据进行匹配；若匹配失败，解析所述票据短消息中包含的票据链接以进行票据获取。
本说明书一个或多个实施例提供了一种票据处理装置，包括：短消息匹配模块，被配置为获取用户终端存储的短消息并与票据关键字进行匹配，获得与所述票据关键字匹配的票据短消息；格式数据匹配模块，被配置为识别所述票据短消息的格式数据，并将所述格式数据与历史格式数据进行匹配；票据链接解析模块，被配置为在匹配失败的情况下，解析所述票据短消息中包含的票据链接以进行票据获取。
本说明书一个或多个实施例提供了一种票据处理设备，包括：处理器；以及，被配置为存储计算机可执行指令的存储器。其中，所述计算机可执行指令在被执行时使所述处理器：获取用户终端存储的短消息并与票据关键字进行匹配，获得与所述票据关键字匹配的票据短消息；识别所述票据短消息的格式数据，并将所述格式数据与历史格式数据进行匹配；若匹配失败，解析所述票据短消息中包含的票据链接以进行票据获取。
本说明书一个或多个实施例提供了一种存储介质，用于存储计算机可执行指令，所述计算机可执行指令在被执行时实现以下流程：获取用户终端存储的短消息并与票据关键字进行匹配，获得与所述票据关键字匹配的票据短消息；识别所述票据短消息的格式数据，并将所述格式数据与历史格式数据进行匹配；若匹配失败，解析所述票据短消息中包含的票据链接以进行票据获取。
附图说明
为了更清楚地说明本说明书一个或多个实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本说明书中记载的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图；
图1为本说明书一个或多个实施例提供的一种票据处理方法处理流程图；
图2为本说明书一个或多个实施例提供的一种应用于短消息场景的票据处理方法处理流程图；
图3为本说明书一个或多个实施例提供的一种票据处理装置示意图；
图4为本说明书一个或多个实施例提供的一种票据处理设备的结构示意图。
具体实施方式
为了使本技术领域的人员更好地理解本说明书一个或多个实施例中的技术方案，下面将结合本说明书一个或多个实施例中的附图，对本说明书一个或多个实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本说明书的一部分实施例，而不是全部的实施例。基于本说明书一个或多个实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都应当属于本文件的保护范围。
本说明书提供的一种票据处理方法实施例。参照图1，其示出了本实施例提供的一种票据处理方法处理流程图，参照图2，其示出了本实施例提供的一种应用于短消息场景的票据处理方法处理流程图。
参照图1，本实施例提供的票据处理方法，具体包括步骤S102至步骤S106。
步骤S102，获取用户终端存储的短消息并与票据关键字进行匹配，获得与所述票据关键字匹配的票据短消息。
本实施例提供的票据处理方法，通过将用户终端存储的短消息与票据关键字进行匹配的方式，筛选出与票据关键字匹配的票据短消息，并提取票据短消息中包含的格式数据，进一步将提取的格式数据与历史格式数据进行匹配，以此来判断当前处理的票据短消息是否由已记录历史格式数据的服务商提供，如果当前处理的票据短消息由已记录历史格式数据的服务商提供，则根据已记录的该服务商的历史格式数据进行票据获取即可，如果当前处理的票据短消息由未记录历史格式数据的服务商提供，则通过对票据短消息进行解析处理来进行票据获取，从而通过短消息的自动匹配和解析过程，实现对短消息的票据处理过程的自动化，提升了从短消息中获取票据的效率，以此来提升用户的票据服务体验。
本实施例所述票据关键字，是指预先配置的与票据相关的关键字，通过将短消息与票据关键字进行匹配，能够确定短消息是否为与票据相关的票据短消息；所述票据关键字具体存储在关键字库中。所述短消息，包括通过短信应用接收的短信，和/或，通过应用或者其他通讯方式推送的消息。
实际应用中，短消息存储在用户的用户终端，为确保用户的数据隐私，在从所述用户终端获取存储的短消息之前，需进行短消息提取的授权处理，本实施例提供的一种可选实施方式中，具体采用如下方式进行授权处理：向所述用户终端下发短消息服务的授权提醒；短消息服务是指用户终端内接收以及管理短消息的服务或者应用；根据所述用户终端针对所述授权提醒提交的授权确认指令，进行所述短消息服务的授权处理。
具体实施时，通过将短消息与票据关键字进行匹配确定票据短消息的过程中，为提升匹配的效率和匹配的准确性，本实施例提供一种可选实施方式中，所述短消息与所述票据关键字的匹配过程，具体采用如下方式实现：根据用户授权调用所述用户终端的短消息服务，读取所述短消息服务的短消息列表中存储的短消息；针对读取的短消息中任意一者，将该短消息分别与关键字库中的票据关键字进行匹配；判断该短消息是否与所述关键字库中至少一个票据关键字匹配；若是，确定该短消息为所述票据短消息；若否，确定该短消息为非票据短消息。
步骤S104，识别所述票据短消息的格式数据，并将所述格式数据与历史格式数据进行匹配。
本实施例所述格式数据，是指用于确定短消息的消息类型，或者与消息内容的关键词相关的数据，比如用户终端的短消息应用的短消息列表中某条短消息的开头记录有“【xx发票】”，根据“【xx发票】”能够确定该短消息为发票类短消息，并且能够据此确定开具和发送该发票短消息的服务商，则“【xx发票】”被确定为该短消息的格式数据。
具体实施时，在识别所述票据短消息的格式数据的过程中，可选的，通过提取所述票据短消息中包含的票据服务信息，基于所述票据服务信息确定所述格式数据。其中，所述票据服务信息，是指与票据服务商的名称、标识等相关的数据信息，或者与票据服务商开具的票据相关的数据信息。
例如，短消息的开头记录有“【xx发票】”，则将从短消息中提取出的“【xx发票】”这一票据服务信息，作为该短消息的格式数据。
此外，为了提升格式数据识别的全面性，本实施例提供的一种可选实施方式中，从所述短消息的整体内容出发识别其中包含的格式数据，以此使识别获得的格式数据能够更加准确，具体在识别过程中，通过语义识别算法识别所述票据短消息中包含的文本信息，并 根据所述文本信息确定所述格式数据。
例如，短消息中并未包含“【xx发票】”这样明显标识短消息服务信息的关键词，则首先通过语义识别算法对短消息进行识别，获得短消息包含的文本信息，然后从文本信息中提取出与服务信息相关的关键词，最后根据提取出的关键词确定该短消息的格式数据。
基于上述提供的通过提取所述票据短消息中包含的票据服务信息，并基于所述票据服务信息确定所述格式数据的可选实施方式，在此基础上，将所述格式数据与历史格式数据进行匹配的过程中，采用下述提供的可选实施方式进行匹配处理：将所述格式数据中包含的票据服务信息与所述历史格式数据中包含的票据服务信息进行匹配；若匹配成功，则表明格式库中存在当前票据短消息匹配的历史格式数据，可通过格式库中历史格式数据进行所述票据短消息的票据获取；反之，若匹配失败，则表明格式库中不存在当前票据短消息匹配的历史格式数据，无法通过格式库中历史格式数据进行所述票据短消息的票据获取。
具体的，将所述票据短消息的格式数据与所述历史格式数据进行匹配的过程中，采用遍历的方式将所述票据短消息的格式数据与格式库中的每个历史格式数据进行匹配处理，具体针对当前遍历的历史格式数据进行如下匹配处理：采用相似度算法或者匹配模型计算所述票据短消息的格式数据与当前遍历的历史格式数据的相似度或者匹配度；比如将格式数据中包含的票据服务信息与历史格式数据中包含的票据服务信息输入相似度算法或者匹配模型，计算相似度或者匹配度。
若遍历完成后不存在相似度或者匹配度大于预设阈值的历史格式数据，则确定匹配失败，执行下述步骤S106即可。
若遍历完成后存在相似度或者匹配度大于预设阈值的历史格式数据，则确定匹配成功，并将相似度或者匹配度最高的历史格式数据确定为目标格式数据，即：所述格式数据匹配的历史格式数据，并基于所述票据短消息中包含的票据链接以及所述目标格式数据对应的票据下载配置，进行所述票据短消息的票据获取处理，若匹配成功，则表明格式库中存在当前票据短消息匹配的历史格式数据，可通过格式库中历史格式数据进行所述票据短消息的票据获取；反之，若匹配失败，则表明格式库中不存在当前票据短消息匹配的历史格式数据，无法通过格式库中历史格式数据进行所述票据短消息的票据获取。
实际通过票据链接进行票据下载的过程中，存在一部分票据链接，这部分票据链接被触发后，返回的结果中包含票据文件，相应的，通过这部分票据链接下载票据，只需访问触发票据链接并下载票据链接被触发后返回的响应体中的票据文件即可，本实施例对这一下载过程予以记录并配置为相应的配置信息，通过执行配置的获得的配置信息，能够实现访问票据链接并下载票据文件，则将该配置信息称之为：“进行访问票据链接并下载链接 访问结果中包含的票据文件的配置信息”。
除此之外，还存在一部分票据链接，这部分票据链接被触发后，返回的结果中并未直接包含票据文件，通过这部分票据链接下载票据，还需根据票据链接被触发后返回的响应体中内容进行相应的操作处理，方能够下载票据文件，本实施例对触发票据链接并针对链接访问结果执行操作处理的过程予以记录并配置为相应的配置信息，通过执行配置的获得的配置信息，能够实现访问票据链接并针对链接访问结果执行操作处理进而下载票据文件，则将该配置信息称之为：“进行访问票据链接并下载链接访问结果中包含的票据文件的配置信息”。
其中，所述票据链接，是指提供访问和票据下载的链接。可选的，所述票据下载配置，包括下述至少一项：进行访问票据链接并下载链接访问结果中包含的票据文件的配置信息，进行访问票据链接并执行链接访问结果中票据下载通道对应的下载触发动作以下载票据文件的配置信息。
如上所述，基于上述提供的通过语义识别算法识别所述票据短消息中包含的文本信息，并根据所述文本信息确定所述格式数据的可选实施方式，在此基础上，将所述格式数据与历史格式数据进行匹配的过程中，采用下述提供的可选实施方式进行匹配处理：将所述格式数据中包含的文本信息与所述历史格式数据中包含的票据服务信息进行匹配。
具体的，将所述票据短消息的格式数据与所述历史格式数据进行匹配的过程中，采用遍历的方式将所述票据短消息的格式数据与格式库中的每个历史格式数据进行匹配处理，具体针对当前遍历的历史格式数据进行如下匹配处理：采用相似度算法或者匹配模型计算所述票据短消息的格式数据与当前遍历的历史格式数据的相似度或者匹配度；比如将格式数据中包含的文本信息与历史格式数据中包含的票据服务信息输入相似度算法或者匹配模型，计算相似度或者匹配度；若遍历完成后不存在相似度或者匹配度大于预设阈值的历史格式数据，则确定匹配失败，执行下述步骤S106即可；若遍历完成后存在相似度或者匹配度大于预设阈值的历史格式数据，则确定匹配成功，并将相似度或者匹配度最高的历史格式数据确定为目标格式数据，即所述格式数据匹配的历史格式数据，并基于所述票据短消息中包含的票据链接以及所述目标格式数据对应的票据下载配置，进行所述票据短消息的票据获取处理。
步骤S106，若匹配失败，解析所述票据短消息中包含的票据链接以进行票据获取。
上述步骤对将所述票据短消息的格式数据与历史格式数据进行匹配之后，若匹配失败，则表明格式库中不存在当前票据短消息匹配的历史格式数据，无法通过格式库中历史格式数据进行所述票据短消息的票据获取，本步骤中，通过解析所述票据短消息中包含的票据 链接的方式进行票据获取。
本实施例提供的一种可选实施方式中，解析所述票据短消息中包含的票据链接以进行票据获取，包括：判断所述票据短消息中是否包含票据链接；若是，访问所述票据链接，并判断所述票据链接的链接访问结果中是否包含票据文件；若包含，下载并存储所述票据文件；若不包含，执行下述可选实施方式提供的操作以进行票据下载处理：遍历格式库中存储的历史格式数据，并针对当前遍历的历史格式数据进行如下处理：按照当前遍历的历史格式数据对应的票据下载配置，访问所述票据短消息中包含的票据链接，并进行票据下载处理；若票据下载成功，终止遍历；若票据下载失败，继续遍历；若否，则无法通过解析票据链接的方式对所述票据短消息进行票据获取处理，不做处理或者跳过所述票据短消息即可。
在此基础上，本实施例通过动态更新的格式库的方式丰富格式库中的格式数据，以此来提升票据短消息的格式数据与格式库中历史格式数据匹配的成功率，进而来提升票据处理效率，可选的，通过记录所述格式数据与票据下载成功的票据下载配置的对应关系，并将所述格式数据更新至格式库中的方式，对格式库进行动态更新。
此外，为在提升用户的票据处理体验的基础上进一步提升用户的票据访问体验，在上述解析所述票据短消息中包含的票据链接以进行票据获取，或者，基于所述票据短消息中包含的票据链接以及所述目标格式数据对应的票据下载配置进行所述票据短消息的票据获取处理之后，本实施例提供的一种可选实施方式中，将票据获取执行后获得电子票据更新至票据服务的票据列表中，以在接收到通过所述票据服务的票据访问入口提交的访问请求时，展示所述票据列表。其中，所述票据服务包括用户终端安装的票据服务应用，或者搭载于用户终端内第三方应用的票据服务子程序或者小程序。
下述以本实施例提供的一种票据处理方法在短消息场景的应用为例，对本实施例提供的票据处理方法进行进一步说明，参见图2，应用于短消息场景的票据处理方法，具体包括步骤S202至步骤S216。
步骤S202，根据用户授权调用用户终端的短消息服务，读取短消息服务的短消息列表中存储的短消息。
步骤S204，针对读取的短消息中任意一者，将该短消息分别与关键字库中的票据关键字进行匹配。
步骤S206，判断该短消息是否与关键字库中至少一个票据关键字匹配；若是，确定该短消息为票据短消息，并执行步骤S208；若否，确定该短消息为非票据短消息。
步骤S208，提取票据短消息中包含的票据服务信息，并基于票据服务信息确定格式数 据。
步骤S210，将格式数据中包含的票据服务信息与历史格式数据中包含的票据服务信息进行匹配；若匹配成功，基于票据短消息中包含的票据链接以及格式数据匹配的历史格式数据对应的票据下载配置，进行票据短消息的票据获取处理。
步骤S212，若匹配失败，判断票据短消息中是否包含票据链接；若是，访问所述票据链接，并执行步骤S212；若否，不作处理即可。
步骤S214，若票据链接被访问后返回的链接访问结果中包含票据文件，下载链接访问结果中包含的票据文件。
此外，若票据链接被访问后返回的链接访问结果中不包含票据文件，则遍历格式库中存储的历史格式数据，并针对当前遍历的历史格式数据进行如下处理：按照当前遍历的历史格式数据对应的票据下载配置，访问所述票据短消息中包含的票据链接，并进行票据下载处理；若票据下载成功，终止遍历；若票据下载失败，继续遍历。
步骤S216，将下载的电子票据更新至票据服务的票据列表中，以在接收到通过票据服务的票据访问入口提交的访问请求时，展示票据列表。
本说明书提供的一种票据处理装置实施例如下：在上述的实施例中，提供了一种票据处理方法，与之相对应的，还提供了一种票据处理装置，下面结合附图进行说明。
参照图3，其示出了本实施例提供的一种票据处理装置示意图。
由于装置实施例对应于方法实施例，所以描述得比较简单，相关的部分请参见上述提供的方法实施例的对应说明即可。下述描述的装置实施例仅仅是示意性的。
本实施例提供一种票据处理装置，包括：短消息匹配模块302，被配置为获取用户终端存储的短消息并与票据关键字进行匹配，获得与所述票据关键字匹配的票据短消息；格式数据匹配模块304，被配置为识别所述票据短消息的格式数据，并将所述格式数据与历史格式数据进行匹配；票据链接解析模块306，被配置为在匹配失败的情况下，解析所述票据短消息中包含的票据链接以进行票据获取。
可选的，所述票据处理装置，还包括：目标格式数据确定模块，被配置为在匹配成功的情况下，将所述格式数据匹配的历史格式数据确定为目标格式数据；票据获取处理模块，被配置为基于所述票据短消息中包含的票据链接以及所述目标格式数据对应的票据下载配置，进行所述票据短消息的票据获取处理。
可选的，所述票据链接解析模块306，包括：票据链接判断子模块，被配置为判断所述票据短消息中是否包含票据链接；若是，运行链接访问结果判断子模块；所述链接访问结果判断子模块，被配置为访问所述票据链接，并判断所述票据链接的链接访问结果中是否 包含票据文件；若是，运行票据文件下载子模块；所述票据文件下载子模块，被配置为下载并存储所述票据文件。
可选的，若所述链接访问结果判断子模块运行后的运行结果为否，运行票据下载处理子模块，所述票据下载处理子模块，被配置为：遍历格式库中存储的历史格式数据，并针对当前遍历的历史格式数据进行如下处理：按照当前遍历的历史格式数据对应的票据下载配置，访问所述票据短消息中包含的票据链接，并进行票据下载处理；若票据下载成功，终止遍历；若票据下载失败，继续遍历。
可选的，所述票据处理装置，还包括：格式数据更新模块，被配置为记录所述格式数据与票据下载成功的票据下载配置的对应关系，并将所述格式数据更新至格式库中。
可选的，所述格式数据匹配模块304，包括：第一格式数据确定子模块，被配置为提取所述票据短消息中包含的票据服务信息，基于所述票据服务信息确定所述格式数据；第二格式数据确定子模块，被配置为通过语义识别算法识别所述票据短消息中包含的文本信息，并根据所述文本信息确定所述格式数据。
可选的，所述格式数据匹配模块304，包括：第一匹配子模块，被配置为将所述格式数据中包含的票据服务信息与所述历史格式数据中包含的票据服务信息进行匹配；第二匹配子模块，被配置为将所述格式数据中包含的文本信息与所述历史格式数据中包含的票据服务信息进行匹配。
可选的，所述票据处理装置，还包括：票据列表更新模块，被配置为将票据获取执行后获得电子票据更新至票据服务的票据列表中，以在接收到通过所述票据服务的票据访问入口提交的访问请求时，展示所述票据列表。
可选的，所述票据下载配置，包括下述至少一项：进行访问票据链接并下载链接访问结果中包含的票据文件的配置信息，进行访问票据链接并执行链接访问结果中票据下载通道对应的下载触发动作以下载票据文件的配置信息。
本说明书提供的一种票据处理设备实施例如下：对应上述描述的一种票据处理方法，基于相同的技术构思，本说明书一个或多个实施例还提供一种票据处理设备，该票据处理设备用于执行上述提供的票据处理方法，图4为本说明书一个或多个实施例提供的一种票据处理设备的结构示意图。
本实施例提供的一种票据处理设备，包括：如图4所示，票据处理设备可因配置或性能不同而产生比较大的差异，可以包括一个或一个以上的处理器401和存储器402，存储器402中可以存储有一个或一个以上存储应用程序或数据。其中，存储器402可以是短暂存储或持久存储。存储在存储器402的应用程序可以包括一个或一个以上模块(图示未示 出)，每个模块可以包括票据处理设备中的一系列计算机可执行指令。更进一步地，处理器401可以设置为与存储器402通信，在票据处理设备上执行存储器402中的一系列计算机可执行指令。票据处理设备还可以包括一个或一个以上电源403，一个或一个以上有线或无线网络接口404，一个或一个以上输入/输出接口405，一个或一个以上键盘406等。
在一个具体的实施例中，票据处理设备包括有存储器，以及一个或一个以上的程序，其中一个或者一个以上程序存储于存储器中，且一个或者一个以上程序可以包括一个或一个以上模块，且每个模块可以包括对票据处理设备中的一系列计算机可执行指令，且经配置以由一个或者一个以上处理器执行该一个或者一个以上程序包含用于进行以下计算机可执行指令：获取用户终端存储的短消息并与票据关键字进行匹配，获得与所述票据关键字匹配的票据短消息；识别所述票据短消息的格式数据，并将所述格式数据与历史格式数据进行匹配；若匹配失败，解析所述票据短消息中包含的票据链接以进行票据获取。
本说明书提供的一种存储介质实施例如下：对应上述描述的一种票据处理方法，基于相同的技术构思，本说明书一个或多个实施例还提供一种存储介质。
本实施例提供的存储介质，用于存储计算机可执行指令，所述计算机可执行指令在被执行时实现以下流程：获取用户终端存储的短消息并与票据关键字进行匹配，获得与所述票据关键字匹配的票据短消息；识别所述票据短消息的格式数据，并将所述格式数据与历史格式数据进行匹配；若匹配失败，解析所述票据短消息中包含的票据链接以进行票据获取。
需要说明的是，本说明书中关于存储介质的实施例与本说明书中关于票据处理方法的实施例基于同一发明构思，因此该实施例的具体实施可以参见前述对应方法的实施，重复之处不再赘述。
上述对本说明书特定实施例进行了描述。其它实施例在所附权利要求书的范围内。在一些情况下，在权利要求书中记载的动作或步骤可以按照不同于实施例中的顺序来执行并且仍然可以实现期望的结果。另外，在附图中描绘的过程不一定要求示出的特定顺序或者连续顺序才能实现期望的结果。在某些实施方式中，多任务处理和并行处理也是可以的或者可能是有利的。
在20世纪30年代，对于一个技术的改进可以很明显地区分是硬件上的改进(例如，对二极管、晶体管、开关等电路结构的改进)还是软件上的改进(对于方法流程的改进)。然而，随着技术的发展，当今的很多方法流程的改进已经可以视为硬件电路结构的直接改进。设计人员几乎都通过将改进的方法流程编程到硬件电路中来得到相应的硬件电路结构。因此，不能说一个方法流程的改进就不能用硬件实体模块来实现。例如，可编程逻辑器件 (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)，如调制的数据信号和载波。
还需要说明的是，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、商品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、商品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、商品或者设备中还存在另外的相同要素。
本说明书一个或多个实施例可以在由计算机执行的计算机可执行指令的一般上下文中描述，例如程序模块。一般地，程序模块包括执行特定任务或实现特定抽象数据类型的例程、程序、对象、组件、数据结构等等。也可以在分布式计算环境中实践本说明书的一个或多个实施例，在这些分布式计算环境中，由通过通信网络而被连接的远程处理设备来执行任务。在分布式计算环境中，程序模块可以位于包括存储设备在内的本地和远程计算机存储介质中。
本说明书中的各个实施例均采用递进的方式描述，各个实施例之间相同相似的部分互相参见即可，每个实施例重点说明的都是与其他实施例的不同之处。尤其，对于系统实施例而言，由于其基本相似于方法实施例，所以描述的比较简单，相关之处参见方法实施例的部分说明即可。
以上所述仅为本文件的实施例而已，并不用于限制本文件。对于本领域技术人员来说，本文件可以有各种更改和变化。凡在本文件的精神和原理之内所作的任何修改、等同替换、改进等，均应包含在本文件的权利要求范围之内。

Claims (14)

  1. 一种票据处理方法，包括：
    获取用户终端存储的短消息并与票据关键字进行匹配，获得与所述票据关键字匹配的票据短消息；
    识别所述票据短消息的格式数据，并将所述格式数据与历史格式数据进行匹配；
    若匹配失败，解析所述票据短消息中包含的票据链接以进行票据获取。
  2. 根据权利要求1所述的票据处理方法，还包括：
    若匹配成功，将所述格式数据匹配的历史格式数据确定为目标格式数据；
    基于所述票据短消息中包含的票据链接以及所述目标格式数据对应的票据下载配置，进行所述票据短消息的票据获取处理。
  3. 根据权利要求1所述的票据处理方法，所述解析所述票据短消息中包含的票据链接以进行票据获取，包括：
    判断所述票据短消息中是否包含票据链接；
    若是，访问所述票据链接，并判断所述票据链接的链接访问结果中是否包含票据文件；
    若是，下载并存储所述票据文件。
  4. 根据权利要求3所述的票据处理方法，若所述判断所述票据链接的链接访问结果中是否包含票据文件执行之后的执行结果为否，执行如下操作：
    遍历格式库中存储的历史格式数据，并针对当前遍历的历史格式数据进行如下处理：
    按照当前遍历的历史格式数据对应的票据下载配置，访问所述票据短消息中包含的票据链接，并进行票据下载处理；
    若票据下载成功，终止遍历；
    若票据下载失败，继续遍历。
  5. 根据权利要求4所述的票据处理方法，还包括：
    记录所述格式数据与票据下载成功的票据下载配置的对应关系，并将所述格式数据更新至格式库中。
  6. 根据权利要求1所述的票据处理方法，所述识别所述票据短消息的格式数据包括：
    提取所述票据短消息中包含的票据服务信息，基于所述票据服务信息确定所述格式数据；
    或者，
    通过语义识别算法识别所述票据短消息中包含的文本信息，并根据所述文本信息确定所述格式数据。
  7. 根据权利要求6所述的票据处理方法，所述将所述格式数据与历史格式数据进行匹配，包括：
    将所述格式数据中包含的票据服务信息与所述历史格式数据中包含的票据服务信息进行匹配；
    或者，
    将所述格式数据中包含的文本信息与所述历史格式数据中包含的票据服务信息进行匹配。
  8. 根据权利要求1所述的票据处理方法，所述获取用户终端存储的短消息并与票据关键字进行匹配，获得与所述票据关键字匹配的票据短消息，包括：
    根据用户授权调用所述用户终端的短消息服务，读取所述短消息服务的短消息列表中存储的短消息；
    针对读取的短消息中任意一者，将该短消息分别与关键字库中的票据关键字进行匹配；
    判断该短消息是否与所述关键字库中至少一个票据关键字匹配；
    若是，确定该短消息为所述票据短消息；
    若否，确定该短消息为非票据短消息。
  9. 根据权利要求1所述的票据处理方法，所述获取用户终端存储的短消息并与票据关键字进行匹配，获得与所述票据关键字匹配的票据短消息步骤执行之前，还包括：
    向所述用户终端下发短消息服务的授权提醒；
    根据所述用户终端针对所述授权提醒提交的授权确认指令，进行所述短消息服务的授权处理。
  10. 根据权利要求1所述的票据处理方法，还包括：
    将票据获取执行后获得电子票据更新至票据服务的票据列表中，以在接收到通过所述票据服务的票据访问入口提交的访问请求时，展示所述票据列表。
  11. 根据权利要求2所述的票据处理方法，所述票据下载配置，包括下述至少一项：
    进行访问票据链接并下载链接访问结果中包含的票据文件的配置信息，进行访问票据链接并执行链接访问结果中票据下载通道对应的下载触发动作以下载票据文件的配置信息。
  12. 一种票据处理装置，包括：
    短消息匹配模块，被配置为获取用户终端存储的短消息并与票据关键字进行匹配，获得与所述票据关键字匹配的票据短消息；
    格式数据匹配模块，被配置为识别所述票据短消息的格式数据，并将所述格式数据与历史格式数据进行匹配；
    票据链接解析模块，被配置为在匹配失败的情况下，解析所述票据短消息中包含的票据链接以进行票据获取。
  13. 一种票据处理设备，包括：
    处理器；以及，被配置为存储计算机可执行指令的存储器，所述计算机可执行指令在被执行时使所述处理器：
    获取用户终端存储的短消息并与票据关键字进行匹配，获得与所述票据关键字匹配的票据短消息；
    识别所述票据短消息的格式数据，并将所述格式数据与历史格式数据进行匹配；
    若匹配失败，解析所述票据短消息中包含的票据链接以进行票据获取。
  14. 一种存储介质，用于存储计算机可执行指令，所述计算机可执行指令在被执行时实现以下流程：
    获取用户终端存储的短消息并与票据关键字进行匹配，获得与所述票据关键字匹配的票据短消息；
    识别所述票据短消息的格式数据，并将所述格式数据与历史格式数据进行匹配；
    若匹配失败，解析所述票据短消息中包含的票据链接以进行票据获取。
PCT/CN2022/103340 2021-07-20 2022-07-01 票据处理 WO2023000954A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110819567.1A CN113435950B (zh) 2021-07-20 2021-07-20 票据处理方法及装置
CN202110819567.1 2021-07-20

Publications (1)

Publication Number Publication Date
WO2023000954A1 true WO2023000954A1 (zh) 2023-01-26

Family

ID=77761108

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/103340 WO2023000954A1 (zh) 2021-07-20 2022-07-01 票据处理

Country Status (2)

Country Link
CN (2) CN114969266A (zh)
WO (1) WO2023000954A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114969266A (zh) * 2021-07-20 2022-08-30 支付宝(杭州)信息技术有限公司 票据处理方法及装置

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105760385A (zh) * 2014-12-17 2016-07-13 中兴通讯股份有限公司 一种处理短信的方法及装置
US20170103400A1 (en) * 2015-10-13 2017-04-13 International Business Machines Corporation Capturing and identifying important steps during the ticket resolution process
CN110868692A (zh) * 2019-11-13 2020-03-06 杭州三体视讯科技有限公司 一种新的电子发票传输系统及方法
CN111339744A (zh) * 2015-07-31 2020-06-26 小米科技有限责任公司 票务信息展示方法、装置及存储介质
US20200410450A1 (en) * 2019-06-25 2020-12-31 International Business Machines Corporation Resolution and pipelining of helpdesk tickets needing resolutions from multiple groups
CN113435950A (zh) * 2021-07-20 2021-09-24 支付宝(杭州)信息技术有限公司 票据处理方法及装置

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10445695B2 (en) * 2015-09-04 2019-10-15 Dell Products L.P. Method and system for providing continuous reference architecture and bill of material modeling
CN106549853A (zh) * 2015-09-23 2017-03-29 九玉（北京）科技有限公司 一种邮件处理方法及装置
US20170109717A1 (en) * 2015-10-15 2017-04-20 Paypal, Inc. Secure sms / email tokenization systems
CN107424065A (zh) * 2017-05-15 2017-12-01 贾琨 一种处理电子邮件中电子发票的方法及系统
KR20190116201A (ko) * 2019-09-25 2019-10-14 주식회사 한국어음중개 온라인 채팅모듈을 이용한 전자어음 대출 시스템 및 그 방법
CN111242785A (zh) * 2020-01-21 2020-06-05 腾讯科技（深圳）有限公司 一种票据处理方法、装置及电子设备、存储介质
CN111737967A (zh) * 2020-08-27 2020-10-02 国信电子票据平台信息服务有限公司 一种电子发票收票即查验的方法及系统
CN112016340B (zh) * 2020-09-08 2024-01-26 北京速票通科技有限公司 一种发票抬头信息自动识别系统及方法
CN112783833A (zh) * 2020-12-31 2021-05-11 航天信息股份有限公司 一种ofd版式发票文件的解析系统及装置
CN112800848A (zh) * 2020-12-31 2021-05-14 中电金信软件有限公司 票据识别后信息结构化提取方法、装置和设备

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105760385A (zh) * 2014-12-17 2016-07-13 中兴通讯股份有限公司 一种处理短信的方法及装置
CN111339744A (zh) * 2015-07-31 2020-06-26 小米科技有限责任公司 票务信息展示方法、装置及存储介质
US20170103400A1 (en) * 2015-10-13 2017-04-13 International Business Machines Corporation Capturing and identifying important steps during the ticket resolution process
US20200410450A1 (en) * 2019-06-25 2020-12-31 International Business Machines Corporation Resolution and pipelining of helpdesk tickets needing resolutions from multiple groups
CN110868692A (zh) * 2019-11-13 2020-03-06 杭州三体视讯科技有限公司 一种新的电子发票传输系统及方法
CN113435950A (zh) * 2021-07-20 2021-09-24 支付宝(杭州)信息技术有限公司 票据处理方法及装置

Also Published As

Publication number Publication date
CN113435950B (zh) 2022-06-10
CN114969266A (zh) 2022-08-30
CN113435950A (zh) 2021-09-24

Similar Documents

Publication Publication Date Title
US10733983B2 (en) Parameter collection and automatic dialog generation in dialog systems
US10180989B2 (en) Generating and executing query language statements from natural language
US20180232438A1 (en) Title display method and apparatus
WO2017157178A1 (zh) 一种移动终端应用程序的更新方法和装置
US20190147059A1 (en) Method and apparatus for generating to-be-played multimedia content
WO2023000952A1 (zh) 基于邮箱的票据处理
CN111400681B (zh) 数据权限处理方法、装置及设备
CN110674188A (zh) 一种特征提取方法、装置及设备
CN110390182B (zh) 一种确定小程序类目的方法、系统及设备
CN110569428A (zh) 一种推荐模型的构建方法、装置及设备
US11265314B1 (en) Code scanning jump
WO2024066758A1 (zh) 一种业务处理的方法、装置、存储介质以及电子设备
WO2023000954A1 (zh) 票据处理
CN106156050B (zh) 一种数据处理方法及装置
CN111209277B (zh) 一种数据处理方法、装置、设备及介质
CN113011169A (zh) 一种会议纪要的处理方法、装置、设备及介质
CN109684207B (zh) 操作序列封装的方法、装置、电子设备及存储介质
CN109120509B (zh) 一种信息收集的方法及装置
US20230281208A1 (en) Automated analysis of unstructured computer text for generation of an enforcement action database using machine learning
US11677832B2 (en) Voice activated device enabling
US20210377035A1 (en) Intelligent hashing of sensitive information
US10902046B2 (en) Breaking down a high-level business problem statement in a natural language and generating a solution from a catalog of assets
CN109145084B (zh) 数据处理方法、数据处理装置和服务器
US11520839B2 (en) User based network document modification
US20230177077A1 (en) Enhancing input to conversational agents through feedback

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22845119

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE