CN109150940B - Service object information sending method, service object information publishing method, server and client - Google Patents

Service object information sending method, service object information publishing method, server and client Download PDF

Info

Publication number
CN109150940B
CN109150940B CN201710498559.5A CN201710498559A CN109150940B CN 109150940 B CN109150940 B CN 109150940B CN 201710498559 A CN201710498559 A CN 201710498559A CN 109150940 B CN109150940 B CN 109150940B
Authority
CN
China
Prior art keywords
object information
information
access tool
service
verification
Prior art date
Legal status (The legal status 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 status listed.)
Active
Application number
CN201710498559.5A
Other languages
Chinese (zh)
Other versions
CN109150940A (en
Inventor
杜磊
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Alibaba Group Holding Ltd
Original Assignee
Alibaba Group Holding Ltd
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 Alibaba Group Holding Ltd filed Critical Alibaba Group Holding Ltd
Priority to CN201710498559.5A priority Critical patent/CN109150940B/en
Publication of CN109150940A publication Critical patent/CN109150940A/en
Application granted granted Critical
Publication of CN109150940B publication Critical patent/CN109150940B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/51Discovery or management thereof, e.g. service location protocol [SLP] or web services

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

The embodiment of the application provides a service object information sending method, a service object information publishing method, a server and a client. The method for sending the service object information comprises the following steps: receiving business object information to be issued; the information of the business object to be issued comprises at least one attribute value; calling an access tool of a service platform stored by the management terminal to provide the service object information to be issued to the access tool; wherein, the access tool comprises a check rule set; wherein the set of verification rules comprises at least one verification rule; the check rule is used for checking the attribute value; and when the verification result of the access tool on the to-be-released business object information is successful, sending the to-be-released business object information to the business platform so that the business platform can release the to-be-released business object information. The method improves the issuing efficiency of the business object information.

Description

Service object information sending method, service object information publishing method, server and client
Technical Field
The application relates to the field of computer internet, in particular to a service object information sending method, a service object information publishing method, a server and a client.
Background
In real life, more and more people are used to use e-commerce services, booking airline tickets, hotels, restaurants and the like. The network brings convenience to the life of people.
The existing electronic commerce platform mostly adopts the architecture of a client, a merchant management end and a service platform. The consumer can interact with the service platform through the client side to perform query or preset operation. For example, a consumer uses a mobile phone app (application) provided by an Online Travel Agent (OTA) website to book a hotel room, or book an airline ticket, and the like. The merchant management terminal provides the merchant with the functions of managing and releasing the commodities in the service platform. For example, an airline may use a merchant management terminal to publish flight information in a service platform, and a hotel may use the merchant management terminal to publish room information in the service platform. The business platform establishes a bridge between the ultimate consumer and the merchant providing the service.
At present, when a merchant management end publishes a commodity on a service platform, the merchant management end mostly sends information to the service platform, and the service platform performs information verification on the service platform. In some cases, in particular: merchants want to publish activity information for a hotel, such as discounting costs for rooms. The merchant inputs the name, the room, the number and the like of the hotel as release information through the merchant management terminal, and the information is sent to the service platform. Hotel information and the like are set in the service platform. The service platform can check the received release information to realize the normalization of the related data. If the verification is successful, the service platform considers that the information is correct and can issue the information. If the verification fails, the service platform considers that the information is unsuccessfully issued, and feeds back failure information to the merchant management terminal.
In this mode, the merchant receives the failure message and may continually attempt to enter a different message in anticipation of passing the verification by the service platform. Therefore, in a scene that a merchant issues a piece of information, the service platform may repeatedly receive multiple issuing requests and repeatedly perform verification. In a big data scenario, the business platform may correspond to a very large number of merchant management terminals. If each merchant administration terminal issues a piece of information, verification failure may occur. Therefore, a large workload may occur on the service platform, which may result in a reduction in efficiency at the entire system level. Moreover, since the business object information is verified by the business platform, and the merchant management end and the business platform perform data interaction through the internet, the merchant management end needs to wait for verification feedback of the business server after sending every time in the process of issuing the business object information, so that the working efficiency of the merchant is low.
Disclosure of Invention
The embodiment of the application provides a service object information sending method, a service object information publishing method, a server and a client, and aims to solve the problem that the service platform is high in workload in the existing information sending method.
The embodiment of the application provides a method for sending business object information, which receives the business object information to be released; the information of the business object to be issued comprises at least one attribute value; calling an access tool of a service platform stored by a management terminal, and verifying the service object information to be issued; wherein, the access tool comprises a check rule set; wherein the set of verification rules comprises at least one verification rule; the check rule is used for checking the attribute value; and when the access tool successfully verifies the to-be-released business object information, sending the to-be-released business object information to the business platform.
The embodiment of the application also provides a server, which comprises a network communication unit, a memory and a processor; the network communication unit is used for receiving service object information to be issued, which is provided by a client, wherein the service object information comprises at least one attribute value; when the business object information passes the verification, the business object information is sent to the business platform; the memory is used for storing an access tool provided by the service platform; wherein, the access tool comprises a check rule set; wherein the set of verification rules comprises at least one verification rule; the check rule is used for checking the attribute value; the processor is used for calling an access tool provided by a service platform to provide the service object information to the access tool; and checking the business object information based on the access tool.
An embodiment of the present application further provides a server, including: the receiving module is used for receiving the information of the business object to be issued, which is provided by the client; wherein, the business object information comprises at least one attribute value; the calling module is used for calling an access tool provided by a service platform so as to provide the service object information to the access tool; wherein, the access tool comprises a check rule set; wherein the set of verification rules comprises at least one verification rule; the check rule is used for checking the attribute value; and the sending module is used for sending the business object information to the business platform when the verification result of the access tool on the business object information is successful.
The embodiment of the application also provides a client, which comprises input equipment, a memory, a processor and a network communication unit; the input equipment is used for inputting the service object information to be issued, and the service object information comprises at least one attribute value; the memory is used for storing an access tool provided by the service platform; wherein, the access tool comprises a check rule set; wherein the set of verification rules comprises at least one verification rule; the check rule is used for checking the attribute value; the processor is used for calling an access tool provided by a service platform to provide the service object information to the access tool; checking the business object information based on the access tool; and the network communication unit is used for sending the service object information to the service platform under the condition that the service object information is successfully verified.
The embodiment of the present application further provides a method for publishing service object information, which is applied to a service platform, and the method includes: receiving service object information to be issued sent by a management end of a resource provider; the business object information is verified through an access tool stored in the management terminal, the verification result is information of successful verification, and the business object information comprises at least one attribute value; the access tool stored by the management terminal is used for accessing the service platform; the access tool comprises a check rule set; wherein the set of verification rules comprises at least one verification rule; the check rule is used for checking the attribute value; and issuing the service object information.
An embodiment of the present application provides a server, including: the receiving module is used for receiving the information of the service object to be issued sent by the management end of the resource provider; wherein, the business object information comprises at least one attribute value; the management terminal stores an access tool of the service platform; the access tool comprises a check rule set; wherein the set of verification rules comprises at least one verification rule; the check rule is used for checking the attribute value; and the issuing module is used for issuing the service object information.
The embodiment of the present application further provides a method for sending service object information, which is applied to a management end of a resource provider, and the method includes: generating business object information to be issued; the information of the business object to be issued comprises at least one attribute value; sending the service object information to a server of a management end, so that the server calls an access tool of a stored service platform to provide the service object information to be issued to the access tool, wherein the access tool comprises a check rule set, the check rule set comprises at least one check rule, and the check rule is used for checking the attribute value; and the server is used for sending the information of the business object to be issued to the business platform when the verification result of the access tool on the information of the business object to be issued is successful, so that the business platform can issue the information of the business object to be issued.
An embodiment of the present application further provides a client, including: the generating module is used for generating the business object information to be issued; the information of the business object to be issued comprises at least one attribute value; the calling module is used for calling an access tool stored by a client to provide the business object information for the access tool; wherein, the access tool comprises a check rule set; wherein the set of verification rules comprises at least one verification rule; the check rule is used for checking the attribute value; and the sending module is used for sending the to-be-issued business object information to the business platform under the condition that the verification result of the access tool on the to-be-issued business object information is successful, so that the business platform can issue the to-be-issued business object information.
The embodiment of the present application further provides a method for sending service object information, where the method includes: receiving business object information to be issued; calling an access tool stored in a management terminal to verify the business object information to be issued; wherein, the access tool comprises a check rule set; wherein the set of verification rules comprises at least one verification rule; and under the condition of successful verification, sending the information of the service object to be issued to a service platform.
In the embodiment of the application, the service object information is verified by calling the access tool arranged at the local part of the merchant management terminal, so that the verification of the service object on the service platform is avoided, the technical problems of low information sending efficiency, large service platform load and poor user experience of the existing information sending method are solved, and the technical effects of improving the information sending efficiency and improving the user experience are achieved.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only some embodiments described in the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without any creative effort.
Fig. 1 is a schematic block diagram of a service management system according to an embodiment of the present application;
fig. 2 is a schematic flowchart of a method for sending service object information according to an embodiment of the present application;
fig. 3 is a diagram illustrating a scenario of a method for sending service object information according to an embodiment of the present application;
fig. 4 is a data flow diagram of a method for sending business object information according to an embodiment of the present application;
fig. 5 is a schematic diagram illustrating a recommended value feedback of a service object information sending method according to an embodiment of the present application;
fig. 6 is a schematic diagram of another first recommended value feedback situation of a service object information sending method according to an embodiment of the present application;
fig. 7 is a schematic diagram of another recommended value feedback situation of a service object information sending method according to an embodiment of the present application;
fig. 8 is a schematic diagram of another recommended value feedback situation three of a service object information sending method according to an embodiment of the present application;
fig. 9 is a schematic structural diagram of a server according to an embodiment of the present application;
fig. 10 is a schematic structural diagram of a server provided in an embodiment of the present application;
fig. 11 is a schematic structural diagram of a client according to an embodiment of the present application;
FIG. 12 is a flowchart illustrating another business object information publishing method according to the present embodiment;
fig. 13 is a schematic structural diagram of another server provided in this embodiment of the present application
Fig. 14 is a schematic flowchart of a method for sending business object information according to an embodiment of the present application;
fig. 15 is a schematic structural diagram of a client according to an embodiment of the present application;
fig. 16 is a flowchart illustrating a method for sending business object information according to an embodiment of the present application.
Detailed Description
In order to make those skilled in the art better understand the technical solutions in the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Please refer to fig. 1. The embodiment of the application provides a service management system. The service management system comprises: the system comprises a client, a merchant management end and a service platform.
The client can perform data interaction with the business platform so as to provide the business platform with the operation of the consumer, and the business object information issued by the business platform is consulted. The business object information can be room information related to accommodation, catering, ticket business, box information, table information, airplane ticket information, movie theater ticket information, stadium ticket information and the like which are not listed. The customer can perform operations such as query of the business object information through the client, and can also issue an order through the client to reserve the business object represented by the business object information. Specifically, for example, a consumer reserves a room for accommodation by operating a client.
The client can be a desktop computer, a tablet computer, a notebook computer, a smart phone, a digital assistant, a smart wearable device, and the like. Wherein, wearable equipment of intelligence can include intelligent bracelet, intelligent wrist-watch, intelligent glasses, intelligent helmet etc.. Of course, the client is not limited to the electronic device with certain entities, and may also be software running in the electronic device. Specifically, for example, the client may be a web page provided to the consumer by a website facilitator, or may be an application provided to the consumer by the facilitator.
The merchant management terminal can be used for merchants to issue and manage business object information in the business platform. Specifically, for example, the merchant may be a hotel, and the hotel may publish the house source information in the service platform through the merchant management terminal. In this way, the customer can consult the room reserved for the hotel through the client.
The merchant management side is not limited to a client mode, but may be a management system using a client and server mode. Under the mode that the merchant management end adopts a single client, the client can directly carry out data communication with the service platform, and the business object information of the merchant is issued and managed. When the merchant management end adopts a mode of the client and the server, the merchant can record and store business object information of the merchant through the server and manage the business object information by using the interaction between the client and the server. Moreover, the server of the merchant management end can realize data communication between the server of the merchant management end and the service platform by calling the access tool provided by the service platform, so that the merchant can send related instructions to the server by operating the client, the server is communicated with the service platform, and the service object information is managed and issued in the service platform.
The client of the merchant management end can be a desktop computer, a tablet computer, a notebook computer, a smart phone, a digital assistant, a smart wearable device and the like. Wherein, wearable equipment of intelligence can include intelligent bracelet, intelligent wrist-watch, intelligent glasses, intelligent helmet etc.. Of course, the client of the merchant management end is not limited to the electronic device with certain entity, and may also be software running in the electronic device.
The service platform may comprise one or more servers operating independently, or distributed servers, or a server cluster consisting of a plurality of servers. The server may include a network communication unit, a processor, a memory, and the like. The distributed memory may include a plurality of processors and a plurality of network communication units and a plurality of memories, etc. The plurality of memories may be a plurality of independent physical memories or may be a distributed storage system.
The business platform can be used for establishing a communication channel for the customer end of the consumer and the merchant management end. The business platform can receive the business object information issued by the merchant management end, so that a consumer can browse the business object information issued by the merchant management end through data interaction between the client and the business platform. Furthermore, the customer can send an order request to the service platform through the client for locking the service object represented by the service object information. The business platform can place an order after corresponding matching logic is carried out, and informs the customer terminal and the merchant management terminal of the customer so as to complete the locking of the business object pointed by the order request. Specifically, for example, an OTA website is taken as an example. The hotel can publish or modify the house source information on the house source information management page provided by the OTA website. The consumer can search for the house source and make an order for a room in a page or mobile application provided by the OTA website. The service server inside the OTA forms a service platform, and provides data interaction support for functions of hotel publishing house source information, user room reservation and the like.
Please refer to fig. 2. The embodiment of the application provides a method for sending business object information.
In the present embodiment, the method for transmitting the business object information can be applied to the management side of the resource provider, but the method is not limited to the management side of the resource provider, and may be applied to an intermediate side of data processing, for example. The present application is not limited thereto.
In this embodiment, the resource provider may refer to a merchant that publishes the business object information in the business platform. The business object characterized by the business object information may be considered a resource. Thus, the administrator of the resource provider may be the merchant administrator.
The service object information transmission method may include the following steps.
Step S11: receiving business object information to be issued; wherein, the business object information comprises at least one attribute value.
In this embodiment, the receiving, by the application merchant management end, the to-be-released business object information may be that data information is input by a merchant using the merchant management end. When the merchant management end is a single computer, the manner of receiving the information of the business object to be published may be receiving an input of the merchant at the merchant management end through an input device. When the merchant management end is a system constructed by the client and the server, the mode of receiving the information of the business object to be published may be that the server receives the information of the business object to be published sent by the client. At this time, the information of the business object to be published sent by the client may be input by the merchant at the client.
In this embodiment, the business object represented by the business object information may be a commodity or a service. The business object may correspond to a good or service in the real world. I.e. a business object may represent a good or service in the real world. Specifically, for example, in a scenario where a merchant publishes room information, a business object may represent a room. The business object may represent food when the merchant publishes food information for sale. When the merchant issues the clothing information for sale, the business object may represent the clothing. The business object may be an airline ticket, a hotel room, a bus ticket, a train ticket, and the like. Are not further enumerated here.
In this embodiment, the business object information may include some characterizing information for describing the goods or services. The characterizing information may be an attribute of the business object. Specifically, for example, the service object is a room, and the service object information may include a hotel name, a room type, a quantity, a price, and the like. The business object is a flight and the business object information may include airline name, flight number, flight time, number of seats, and the like. The service object information to be released may be specifically service object information that is prepared to be released or modified on the service platform by the merchant.
In this embodiment, the attribute value may be a specific value of the representation information of the service object. The number of attribute values included in each service object information may be one or more. Specifically, for example, the service object is a movie ticket, and the service object information may include a name of a theater, a name of a movie hall, a type of a movie, a number of seats, and the like. The business object information may include attribute values of "happy blue sea theater", "pearl hall", "3D", "60", and the like.
Step S13: calling an access tool of a service platform stored by a management terminal, and verifying the service object information to be issued; wherein, the access tool comprises a check rule set; wherein the set of verification rules comprises at least one verification rule; the check rule is used for checking the attribute value.
In this embodiment, the service platform may be a platform for storing and managing data information of all service objects. Constraint conditions can be set in the service platform according to the representation information of the service object, so that the service object information issued by different merchants can have consistent data formats. Therefore, the method and the system can facilitate the interaction of the customer with the service platform by using the client to inquire the service object information. Specifically, for example, the attribute value of the name is referred to, and the attribute value of the name is to be based on the attribute value of the name recorded in the service platform, and the service object information issued by different merchants. For example, in some cases, the business object information issued by different merchants may actually be the same business object, and if the names of the business objects by the different merchants are different, it may be difficult for the business platform to respond to the query request of the consumer, and all the business object information is provided to the corresponding client. If different merchants issue the business object information, the names of the same business object in the business object information which is finally successfully issued are consistent, so that the business platform can perform data query operation very conveniently. As another example, the business platform may set constraints, such as an agreed-upon format of "year-month-day", with respect to the attribute values of time. Therefore, the service platform is convenient for date matching operation in the inquiry process. In summary, the service platform requires data consistency. The specific constraint conditions may be different for the business object information of different business objects.
In this embodiment, the access tool is provided for the merchant management end to use, and the merchant management end may perform data interaction with the service platform through the access tool. The data format, communication protocol, etc. communicated with the service platform may be agreed upon in the access tool. Therefore, the merchant management terminal can perform data interaction with the service platform by calling the access tool on the basis of having self service logic.
In this embodiment, the access tool may be provided as a separate functional unit at the merchant management site. It should be noted that the access tool may be stored in the merchant management side, but the access tool is not limited to be stored in the merchant management side. For example, the access tool may be a separate unit provided by the business platform, separate from the merchant management side, but electrically connected to the merchant management side. In particular, the access tool may simply be software, which is stored in the memory of the merchant management site. When the merchant management end needs to interact with the business platform, the access tool can be read from the storage. The access means may also be an electronic device separate from the merchant administration site and in electrical communication with the merchant administration site. The merchant management terminal can perform data interaction with the access tool in a wired or wireless mode. The wireless mode includes but is not limited to WIFI or bluetooth. The access tool can perform data interaction with the service platform through the network.
In this embodiment, the check rule may be a concrete expression of a constraint condition of the attribute value. The check rule may specifically specify a value range of the attribute value, or a data format of the attribute value, and the like. Of course, the check rules may also agree on other dimensions for the attribute values, which are not further enumerated herein. The check rule is used for checking the attribute value, and may be understood as determining whether the attribute value meets the convention of the check rule. For example, whether the attribute value is in the value range agreed by the check rule, or whether the attribute value adopts the data format agreed by the check rule. Specifically, for example, the business object may be an airline ticket, and the check rule for the attribute value of the flight information may include a currently existing flight number. And when the attribute value is the same as a certain flight number in the check rule, considering that the check result aiming at the attribute value is successful, and otherwise, considering that the check is failed.
In the present embodiment, the sum of the check rules included in the access tool constitutes the set of check rules. The check rule set may include only one check rule, or may include a plurality of check rules. Specifically, for example, the check rule set may include a check rule for a room in a hotel as a business object, a check rule for a movie ticket as a business object, a check rule for an airline ticket as a business object, and the like. The check rule for the room in the hotel as the service object may include a check rule for the name of the hotel, a check rule for the house type of the room, a check rule for the time, and the like. The check rule that the business object is an airline ticket may include a check rule for an airline name, a check rule for a flight number, a check rule for the number of seats, a check rule for a takeoff time, and the like. The business objects are different, and the corresponding check rules can be different. Here, the description is omitted.
In this embodiment, the service object information may be sent to the service platform only after all the attribute values of the service object information are successfully verified by the access tool. Or, a certain piece of information in the service object information may be set as key information, and when the key information is successfully verified, the service object information may be sent to the service platform.
In this embodiment, an access tool of a service platform stored in a management terminal is called to verify the service object information to be issued. Specifically, for example, the merchant management end may invoke an access tool provided by the service platform, transfer the service object information to be published to the access tool, and perform specific verification on the service object information to be published by using the access tool. Wherein the access tool may have a call interface function or the like. The business management terminal provides the business object information to the interface function in a parameter mode when the access tool is called. In this way, the interface function can provide the received parameters to the corresponding check function, so as to check the attribute value included in the service object information. Of course, the service object information may be stored in a specified path or in a specified data structure for the server. Thus, after the access tool is called, the business object information can be read from the specified path or data structure during the process of executing the access tool. Specifically, for example, the service object information is stored in a certain path of the memory, or the service object information is recorded by a data table or the like. Of course, other embodiments of the method for passing the business object information to the access tool are possible and are not further described herein. Other modifications can be made by those skilled in the art while still remaining within the spirit of the embodiments of the present invention, and the scope of the invention should be determined by the appended claims.
Step S15: and when the verification result of the access tool on the business object information is successful, sending the business object information to the business platform so that the business platform can issue the business object information to be issued.
In this embodiment, the successful verification may mean that the attribute value of the service object information conforms to the corresponding verification rule. It is understood that the attribute value is within the value range agreed by the check rule, or the format of the attribute value conforms to the specification of the check rule. Specifically, for example, the flight number is "14201", and "14201, 16201, 14207, 14501" is included in the corresponding check rule. Through the verification discovery, the verification rule includes "14201", which can be regarded as that the verification is passed, i.e. the verification is successful. Conversely, if there is no flight number "14201" in the check rule, the check may be deemed to have failed.
In this embodiment, if the verification is not successful, the verification fails. The verification failure may mean that the attribute value of the service object information does not conform to the corresponding verification rule. It can be understood that the attribute value is outside the value range agreed by the check rule, or the format of the attribute value does not conform to the check rule. Specifically, for example, the attribute value of the hotel name is "hangzhou Shangri-La Hotel", and the corresponding check rule includes "hangzhou Shangri-La Hotel," and "hangzhou Shangri-La Hotel. Through the verification of the access tool, the fact that any hotel name in the verification rule is not the same as the attribute value of the hotel name can be regarded as verification failure.
In this embodiment, the service object information is sent to the service platform, specifically, the access tool sends the successfully verified service object information to a server of the service platform in a wired or wireless manner according to a network communication protocol. The network communication protocol can be Http, TCP/IP or FTP protocol. For example, the server at the merchant management side may send information such as "hotel a", "standard room", "100" and the like to the hectometer travel information network according to the Http protocol, so that the hectometer travel information network may modify and publish the remaining number of the economic rooms of hotel a recorded in the hectometer travel information network according to the information.
In this embodiment, when the result of the verification of the service object information by the access tool is successful, the service object information is sent to the service platform, so that the service platform issues the service object information to be issued. Specifically, the access tool may check the attribute value of the business object information. And checking whether the attribute value of the business object information accords with a corresponding check rule. And if the attribute value is in a value range agreed by the verification rule or the format of the attribute value conforms to the specification of the verification rule, the verification result of the access tool on the service object is considered to be successful. And under the condition of successful verification, sending the service object information to the service platform. Further, the service platform may distribute the service object information on a platform such as a website. Specifically, for example, the service object is a train ticket, and the service object information includes "972 times", "89", and "empty seat". The access tool may first check for the train number "972" in the business object information. And if the train number identical to the train number attribute value '972' exists in the verification rule, determining that the verification is successful. Further, the data format is agreed to be integer in the check rule in the check seat number "89". When the number of seats "89" is considered to be the integer, the result of the verification of the business object information may be considered to be successful. The service object information may be sent to the service platform. After receiving the service object information, the service platform can issue corresponding train ticket information on the service platform according to the service object information, so that a consumer can know the latest condition of the train ticket in time.
In this embodiment, when the result of the verification of the business object information by the access tool is a verification failure, the access tool may select a value closer to the attribute value from the verification rule corresponding to the attribute value of the business object information as a recommended value, and feed the recommended value back to the merchant client. Specifically, for example, it is found that, at the time of verification, the verification rule for the flight number does not have the same flight number as the flight number "14201", and thus the verification fails. At this time, the access tool may select an attribute value flight number "14200" closer to "14201" from the check rule as a recommended value to send to the merchant client. The airline company can check the original input process and determine the reason of the verification failure by taking the feedback recommended value '14200' as a reference: mistaking flight number "14200" for "14201". Therefore, the business object information can be re-input according to the corresponding modification of the error.
In this embodiment, the access tool may feed back the recommended value in various ways. Specifically, after the access tool receives complete business object information input by the merchant through the merchant management terminal, under the condition of failure in verification, a numerical value close to the attribute value is selected according to the attribute value of the business object information and is fed back to the merchant management terminal as a recommended value. Therefore, the merchant can be prompted to input the wrong input and please re-input the wrong input after checking. Or after the merchant inputs part of the business object information through the merchant management terminal, the access tool selects a numerical value related to or closer to the input attribute value of the part of the business object in the verification rule as a recommended value according to the input attribute value of the part of the business object information, and feeds the recommended value back to the merchant management terminal. Therefore, the content of follow-up input of the merchant can be prompted, the merchant can conveniently continue to input the content, and the experience degree of the merchant is improved. Specifically, for example, the business object is an airline ticket, and the business object information input by the airline company may include an airline name, a flight number, a departure time, and the like. Accordingly, the business object information may include attribute values of "spring and autumn airlines", "812 times", "2017, 1 month, and 3 days". In some cases, for example, when the flight number "812 times" is checked, the check is considered to fail if there are no "812 times" in the flight number specified by the check rule. For example, the flight numbers agreed in the check rule include "793 times", "810 times", "820 times", and the like. The flight number "810 times" may be provided as a recommended value to the merchant management site. Specifically, in another example, when the merchant management end wants to publish the business object information, the merchant management end may provide the attribute value input by the merchant to the access tool in real time when the "spring and autumn airlines" is input. At this time, the access tool can select information related to the "spring and autumn airlines" from the verification rules as recommended values according to the attribute values of the "spring and autumn airlines" and feed the recommended values back to the user interface of the merchant management end so as to prompt the merchant of the contents subsequently input. For example, a plurality of flight numbers "810", "820", "813", "91", "93" with spring and autumn airlines may be displayed below the input box as recommended values for the merchant to select. At this point, if the flight number "810" to be entered has appeared below the input box, the merchant may click directly on "810" displayed below the input box for confirmation. Therefore, the method and the device can bring convenience to the use operation of the merchant in a mode of feeding back the recommendation value to the merchant operation interface.
In this embodiment, it is further necessary to supplement that the server may first call the verification rule set in the access tool into the memory, so as to increase the verification speed. For example, the server of the merchant management end may extract the verification rule set provided by the online travel service platform in the access tool and store the extracted verification rule set in the preset memory of the server of the merchant management end. When the information of the business object to be issued is verified, a verification rule set stored in a preset memory of a server of a merchant management end can be directly called for verification.
In the embodiment of the application, by calling the access tool provided by the service platform, the attribute value of the service object information to be published is checked locally (namely, at the merchant management end), so that the check of the service object information on the service platform is avoided, and the technical problem of large workload of the service platform due to the fact that the check needs to be performed on the service platform in the existing method is solved. Furthermore, the operation time of issuing the business object information by the merchant using the merchant management terminal is reduced.
Referring to fig. 3 and 4, in a specific scenario example, a merchant management side includes a client and a server. And the merchant uses the client to perform related operation so as to download instructions to the server, and then issues the service object information through the server and the service platform.
In this scenario example, the merchant needs to publish room information. And the business uses the operation interface provided by the client to input the business object information. Specifically, the business object information may include a hotel name "hangzhou Shangri-La Hotel", a house type "standard room", a quantity "10", a time "2017/2/15", and the like. And after receiving the attribute value input by the merchant, the client provides the attribute value to the server for verification. The client side can also send the business object information to the server of the merchant management side after the merchant input is finished and the submission is indicated.
In this scenario example, after receiving the service object information sent by the client through the network, the server of the merchant management end may invoke an access tool provided by the service platform. The business platform can be an online travel service platform. When the server calls the access tool, the server can load the code of the access tool stored in the storage into the memory, and then execute the corresponding instruction. A set of validation rules may be integrated into the access tool. And the method is used for verifying the business object information.
In this scenario example, the server executes the code of the access tool and issues a call notification to the service platform. The business platform can judge whether the verification rule set updating information exists according to the stored updating time of the merchant management terminal. For example, the update time of the merchant management terminal recorded in the service platform is 2017, 1 and 10 months, and the current time is 2017, 1 and 15 months, at which time the service platform may check whether the modification, increase, or extinction of the verification rule occurs between the date of 2017, 1 and 10 months and the date of 2017, 1 and 15 months. If so, generating the corresponding information into verification rule set updating information, and sending the verification rule set updating information to the merchant management terminal. If the modification, the increase or the abolishment of the verification rule and the like do not occur, the merchant management end can be informed by feedback information without updating.
In this scenario example, after the merchant management side sends out the call notification, the feedback of the service platform may be waited. When the merchant management receives the validation rule set update message, the validation rule set in the access tool may be modified based on the validation rule set update message. After the modification is completed, the business object information can be verified based on the modified verification rule set. When the business management end receives the feedback of the business platform and does not need to update the verification rule set, the business object information can be continuously verified according to the verification rule set in the access tool.
In this scenario example, when the server of the merchant management terminal invokes the access tool, the service object information is provided to the access tool in a parameter transfer manner, and then the service object information can be verified. During specific verification, each attribute value of the service object information can be matched with the corresponding verification rule, and whether the service object information passes the verification or not is judged. When all the attribute values of the service object information conform to the corresponding check rule, the check can be considered to be successful, and when part of the attribute values do not conform to the check rule, the check can be considered to be failed. For example, for an attribute value of a hotel name, "hangzhou Shangri La Hotel," a value range of the hotel name is given in a manner of enumerating in a corresponding check rule, such as "hangzhou Shangri La Wuxing-level Hotel," "Suzhou Shangri La DaHotel," and so on. When the name consistent with the attribute value exists in the check rule, the check of the attribute value can be considered to be successful, and when the name consistent with the attribute value does not exist in the check rule, the check of the attribute value is considered to be failed. The number-specific check rule may be to determine whether a value of the attribute value is in a specified data format, for example, whether the value is integer. The time-based check rule may be a rule for determining whether the attribute value is in a predetermined time format.
In this scenario example, referring to fig. 5, the client provides the business object information to the server only when the business completes the attribute value input of the business object information and indicates submission. The hotel name "hangzhou Shangri La Hotel" is different from "hangzhou Shangri La five-star Hotel" and "Suzhou Shangri La Hotel" in the calibration rule, and the calibration can be considered as failed. At this time, "hangzhou Shangri La five-star hotel" may be provided to the operation interface of the merchant to prompt the merchant, as can be seen in FIG. 6. Or the Hangzhou Shanglira five-star hotel and the Suzhou Shanglira big hotel are provided for the operation interface of the merchant. To facilitate the merchant in making corrections to the previously entered attribute values. As shown in fig. 7, the merchant may modify the hotel name to "hangzhou Shangri La five-star hotel" and resend it to the server.
In this scenario example, the server on the merchant administration side performs the functional logic of the access tool. And after the verification of the business object information is successful, sending the business object information to a business platform. For example, after the hotel name inputted by the merchant is "hangzhou Shangri La five-star hotel", house type "standard room", number "10", time "2017/2/15", and other business object information, the access tool has the check rules that the hotel name value ranges are "hangzhou Shangri La five-star hotel", "Suzhou Shangri La big hotel", the house type value ranges are "big bed house", "standard room", and "president suite", the data format of the number is integer, and the time format is "YYYYY/MM/DD". It can be obtained that the service object information conforms to the corresponding check rule. At this time, aiming at the successful verification of the business object information, the server of the merchant management end sends the business object information to the business platform. After receiving the service object information, the service platform may perform a publishing function. Therefore, when a consumer uses the client to inquire the room information in the service platform, the service object information issued at this time can be inquired.
Referring to fig. 8, in an embodiment, the step of invoking the access tool may specifically include the following steps.
S17: and sending a calling notice to the service platform to notify that the access tool of the service platform is called.
In this embodiment, the sending of the call notification may specifically be sending a signal to the corresponding service platform while the access tool is called, to indicate that the access tool of the service platform is being called. The calling notice can have a specified data format, and when the business platform receives the calling notice, the business platform can know the merchant management terminal sending the calling notice by identifying the calling notice.
In this embodiment, it should be noted that in the specific implementation, the call notification may be sent to the service platform each time the access tool is called. Or sending the call notification at regular time according to a preset rule. For example, it may be designed to send a call notification to the service platform the first time the access tool is called each day. It may also be designed to access the tool five times per call, send a call notification to the service platform, etc. And for a specific calling rule, the design can be flexibly carried out according to specific conditions. The present application is not limited thereto.
S19: and receiving the updating information of the check rule set fed back by the service platform.
In this embodiment, the verification rule set update information may include: the service platform modifies the information of the check rule; newly adding information of a check rule in the service platform; revocation information of the verification rule in the service platform, and the like. The update information of the check rule set may be modification of a value range of a specific agreed attribute value, modification of a data format of the attribute value, or the like. Specifically, for example, the name of a hotel in the original checking rule is "the great hotel in the lake Tai Suzhou". The hotel modifies the name of the hotel to be 'Suzhou big hotel' on the business platform due to the adjustment of the operation strategy. At this time, the updating information of the check rule set fed back by the service platform may include that the name of the hotel corresponding to the original check rule is modified from "suzhou taihu hotel" to "suzhou hotel". Of course, only modifications to the value of the attribute are enumerated here. When the method is implemented, the data format modification and updating of the attribute values can be further included. Specifically, for example, the format of the flight departure time specified as input in the original check rule must be the following format "XX year YY month ZZ date". For convenience of input, the format of the flight departure time is modified and updated again by the service platform to be XX/YY/ZZ. At this time, the check rule set update information fed back by the service platform may include that the flight departure time format in the original check rule is modified into a form of "XX/YY/ZZ". Of course, for the check rules of other dimensions for agreeing on the attribute values, there are other corresponding check rule sets to update information. In this regard, this embodiment is not described.
In this embodiment, the receiving of the update information of the check rule set fed back by the service platform may specifically be receiving, by an access tool, the update information of the check rule set fed back by the service platform according to a network communication protocol.
S21: modifying the set of verification rules based on the verification rule set update information.
In this embodiment, the modifying the check rule set based on the update information of the check rule set may specifically be modifying an original check rule set according to the update information of the check rule set. Specifically, when the verification rule set update information includes a modification to the value range of the specific agreed attribute value, the value range of the specific agreed attribute value in the original verification rule set is modified according to the verification rule set update information. And when the updating information of the verification rule set comprises the data format modification of the attribute value, modifying the data format of the attribute value in the original verification rule set according to the updating information of the verification rule set. And correspondingly modifying the related content of the original check rule for the update information of the check rule set of other dimensions for appointing the attribute value. In this regard, this embodiment is not described.
In one embodiment, the method for sending the service object information may further include: and when the access tool fails to verify the business object information, feeding back verification failure information to the client.
In this embodiment, the verification failure may mean that the attribute value of the service object information does not conform to the corresponding verification rule. It can be understood that the attribute value is outside the value range agreed by the check rule, or the format of the attribute value does not conform to the check rule. Specifically, for example, the attribute value of the hotel name is "hangzhou Shangri-La Hotel", and the corresponding check rule includes "hangzhou Shangri-La Hotel," and "hangzhou Shangri-La Hotel. Through the verification of the access tool, the fact that any hotel name is not the same as the attribute value of the hotel name in the verification rule is found, and the verification can be regarded as failure.
In this embodiment, the failure information may specifically be prompt information that is fed back to an operation interface of the merchant management end by the access tool to prompt the merchant to input an error when the verification fails. Specifically, for example, the access tool does not find the name having the same attribute value as the name of the "fat bread" in the verification rule set, and when the verification fails, a prompt message "input error is provided, and the name is a food! "as the above failure information. Based on the failure information, the merchant can check whether the name of the entered food is consistent with the name of the food recorded on the service platform. If the name is wrong, the name can be modified and then the name is input again.
In one embodiment, the verification failure information includes at least one recommended value matching the attribute value; the method may further comprise: in the verification rule for verifying the attribute value, obtaining a verification value matched with the attribute value based on a preset matching rule, wherein the obtained verification value is used as the recommended value; the check rule comprises at least one check value, and the check value is used as a reference for checking the attribute value.
In the present embodiment, the recommended value that matches the attribute value may be information that is closer to the attribute value of the information and has a relatively small difference in the check rule. Specifically, for example, the business object information is the number of vacant seats of 19412 flight. The check fails because there is no flight number in the check rule that is the same as the 19412 flight number attribute value. At this time, when the access tool transmits failure information to the merchant management side, the flight number "19411" relatively close to the flight number attribute value 19412 may be selected as a recommended value from the flight numbers "19411", "19231", and "18321" in the check rule set according to the flight number attribute value 19412. And feeding back the recommended value as a part of failure information to a management end of the merchant. For example, the information "input error!can be popped up in an input page on the merchant's administrative side! Is it to enter 19411 flights? ". Therefore, when the verification fails, the merchant can receive prompt information indicating that the input is wrong, and also can receive a recommended value related to the business object as a reference basis during modification, so that the merchant can modify the error in a targeted manner according to the recommended value to accurately input the business object information meeting the requirements.
In this embodiment, the failure information may include one recommended value or may include a plurality of recommended values. For example, the business object information input is named "hangzhou Shangri La Hotel", and when the verification fails, the failure information fed back by the access tool may include one recommended value "hangzhou Shangri La Hotel", or may include a plurality of recommended values, which are "hangzhou Shangri La Hotel", "Suzhou Shangri Li La Hotel", and "hangzhou Shangri Li La Hotel", respectively. Therefore, the hotel name which is required to be input can be conveniently selected by the merchant from more recommended values.
In this embodiment, the verification failure information includes at least one recommended value that matches the attribute value. Specifically, the access tool may search, according to the attribute value of the service object information, one or more pieces of information relatively close to the attribute value from the verification rule set as the recommended value. And the one or more recommended values and the failure prompt information form failure information which is fed back to the merchant management terminal.
In one embodiment, the method for sending the service object information may further include: in the verification rule for verifying the attribute value, obtaining a verification value which is in accordance with a preset matching rule with the attribute value, wherein the obtained verification value is used as the recommended value; the check rule comprises at least one check value, and the check value is used as a reference for checking the attribute value.
In this embodiment, the check rule may give a value range of the corresponding attribute value in an enumerated manner. The data listed in the check rule are check values, and are used for judging whether the input attribute value is located in the check values listed in the check rule. In this way, the check value in the check rule can be used as a reference for checking the attribute value.
In this embodiment, the preset matching rule may be used to screen a part of the verification values from the verification rules, and provide the part of the verification values as recommended values to the operation interface of the merchant management terminal. The preset matching rule can screen a verification value which is closer to the input attribute value in the verification rule as a recommended value. The recommended value may be used to prompt the merchant to enter corresponding information. Specifically, for example, the service object is a train ticket, and the shift information of the service object information input by the merchant is "861 times". The check rule set may include check rules for train shift information, and the check rules may include "568", "754", "863", and the like. When the information of the shift is checked for "861 times", it is found that the information of the shift is not in the value range of the check rule, and the check value "863 times" which is closer to "861 times" can be used as the recommended value according to the preset matching rule.
In one embodiment, the preset matching rule may include: the recommended value includes part or all of the characters that constitute the attribute value. In this embodiment, specifically, when determining whether the check value in the check rule can be used as the recommended value, the check value including all or part of the characters of the attribute value may be used as the recommended value. Namely, the check value and the attribute value are considered to accord with the preset matching rule. Specifically, for example, the check value "861 times" includes all characters of the attribute value "861 times", and the check value and the attribute value may be considered to match. Or, for example, the check value "863 times" may include only a part of characters in the attribute value "861 times", but "863 times" may be provided as a recommended value to the operation interface of the merchant.
Referring to fig. 9, the present application further provides a server. The server may specifically comprise a network communication unit 81, a memory 83 and a processor 85. The network communication unit 81, the memory 83 and the processor 85 are connected through a data line inside the server, and data interaction can be performed between them.
The network communication unit 81 may be specifically configured to receive service object information provided by a client, where the service object information includes at least one attribute value; and when the business object information passes the verification, the business object information is sent to the business platform.
The memory 83 is specifically configured to store an access tool provided by the service platform; wherein, the access tool comprises a check rule set; wherein the set of verification rules comprises at least one verification rule; the check rule is used for checking the attribute value.
The processor 85 is specifically configured to invoke an access tool provided by a service platform, so as to provide the service object information to the access tool; and checking the business object information based on the access tool.
In this embodiment, the network communication unit 81 may specifically perform network data interaction according to a network communication protocol. Such as, for example, Http, TCP/IP, or FTP protocols.
In this embodiment, the business object represented by the business object information may specifically be a commodity or a service. Wherein the business object may correspond to a good or service in the real world. I.e. a business object may represent a good or service in the real world. Specifically, for example, in a scenario where a merchant publishes room information, a business object may represent a room. The business object may represent food when the merchant publishes food information for sale. When the merchant issues the clothing information for sale, the business object may represent the clothing. Are not further enumerated here.
In this embodiment, the business object information may include some characterizing information for describing the goods or services. The characterizing information may be an attribute of the business object. Specifically, for example, the service object is a room, and the service object information may include a hotel name, a room type, a quantity, a price, and the like. The business object is an airline ticket, and the business object information may include an airline name, a flight number, a flight time, a number of seats, and the like.
In this embodiment, the attribute value may be a specific value of the representation information of the service object. The number of attribute values included in each service object information may be one or more.
In this embodiment, the memory 83 may be a unit or a module with a storage function inside the server. Or an external storage device which is independent of the server and connected with the server. Wherein the access tools provided by the service platform may be stored in the memory 83. In addition, the set of validation rules stored in the access tool may also be stored in the memory 83.
In this embodiment, the check rule may be a concrete expression of a constraint condition of the attribute value. The check rule may specifically specify a value range of the attribute value, or a data format of the attribute value, and the like. Of course, the check rules may also agree on other dimensions for the attribute values, which are not further enumerated herein. The check rule is used for checking the attribute value, and may be understood as determining whether the attribute value meets the convention of the check rule. For example, whether the attribute value is in the value range agreed by the check rule, or whether the attribute value adopts the data format agreed by the check rule. Specifically, for example, the business object may be an airline ticket, and the check rule for the attribute value of the flight information may include a currently existing flight number. And when the attribute value is the same as a certain flight number in the check rule, considering that the check result aiming at the attribute value is successful, and otherwise, considering that the check is failed.
In the present embodiment, the sum of the check rules included in the access tool constitutes the set of check rules. The check rule set may include only one check rule, or may include a plurality of check rules. Specifically, for example, the check rule set may include a check rule for a room in a hotel as a business object, a check rule for a movie ticket as a business object, a check rule for an airline ticket as a business object, and the like. The check rule for the room in the hotel as the service object may include a check rule for the name of the hotel, a check rule for the house type of the room, a check rule for the time, and the like. The check rule that the business object is an airline ticket may include a check rule for an airline name, a check rule for a flight number, a check rule for the number of seats, a check rule for a takeoff time, and the like. The business objects are different, and the corresponding check rules can be different. Here, the description is omitted.
In this embodiment, the processor 85 may specifically be an electronic device with data processing capability. The processor 85 may be configured to invoke a service platform to provide an access tool stored in the memory 83, and check the attribute value of the service object information through the access tool. According to the check result, the network communication unit 81 is controlled to perform a specific operation through the server internal data line.
In this embodiment, the successful verification may mean that the attribute value of the service object information conforms to the corresponding verification rule. It is understood that the attribute value is within the value range agreed by the check rule, or the format of the attribute value conforms to the specification of the check rule. Specifically, for example, the flight number is "14201", and "14201, 16201, 14207, 14501" is included in the corresponding check rule. Through the verification discovery, the verification rule includes "14201", which can be regarded as that the verification is passed, i.e. the verification is successful. Conversely, if there is no flight number "14201" in the check rule, the check may be deemed to have failed.
In this embodiment, if the verification is unsuccessful, the verification fails. The verification failure may mean that the attribute value of the service object information does not conform to the corresponding verification rule. It can be understood that the attribute value is outside the value range agreed by the check rule, or the format of the attribute value does not conform to the check rule. Specifically, for example, the attribute value of the hotel name is "hangzhou Shangri-La Hotel", and the corresponding check rule includes "hangzhou Shangri-La Hotel," and "hangzhou Shangri-La Hotel. Through the verification of the access tool, the fact that any hotel name in the verification rule is not the same as the attribute value of the hotel name can be regarded as verification failure.
In the present embodiment, if the check is passed, the processor 85 may control the network communication unit 81 to transmit the checked service object information to the service platform through the internal data line. If the verification fails, the processor 85 may control the access tool to generate a recommended value similar to the attribute value compared to the business object according to the verification rule set through the internal data line; the network communication unit 81 is then controlled to send the recommended value to the merchant for reference.
In one embodiment, the processor 85 calls the check rule set into the memory storage 83 of the server before checking the business object information.
In this embodiment, in order to improve the verification speed, before the processor 85 verifies the business object information, the verification rule set originally stored in the access tool may be extracted and stored in the memory 83 of the server, so that during the specific verification, the corresponding verification rule set may be quickly obtained from the memory 83 of the server through the internal data line of the server, thereby reducing the time for obtaining the verification rule from the access tool, improving the verification speed, and improving the information sending rate. For example, the processor of the server of the OTA web site may first extract the set of validation rules from the access tool and store the set of validation rules in memory internal to the server of the OTA web site. When checking the guest room information of a hotel, the checking rule set can be directly obtained from the memory inside the server, and the attribute value of the guest room information of the hotel is checked. Therefore, the check rule set can be prevented from being acquired through the access tool, and the technical effects of improving the check speed and improving the information sending efficiency are achieved.
The specific functions of the server and the processor 85 in the above embodiments can be explained in comparison with the foregoing embodiments in the present application.
The processor 85 may be implemented in any suitable manner. For example, the processor may take the form of, for example, a microprocessor or processor and a computer-readable medium that stores computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, an embedded microcontroller, and so forth. The present application is not limited.
Based on the same inventive concept, another server is provided in the embodiments of the present invention, as described in the following embodiments. Because the principle of the server for solving the problem is similar to the business object information sending method, the implementation of the server can refer to the implementation of the business object information sending method, and repeated parts are not described again. As used hereinafter, the term "unit" or "module" may be a combination of software and/or hardware that implements a predetermined function. Although the means described in the embodiments below are preferably implemented in software, an implementation in hardware, or a combination of software and hardware is also possible and contemplated.
Please refer to fig. 10, which is a block diagram of another server according to an embodiment of the present invention. The server may specifically include: a receiving module 91, a calling module 93 and a sending module 95. This structure will be specifically explained below.
The receiving module 91 may be specifically configured to receive service object information provided by a client; wherein, the business object information comprises at least one attribute value.
The invoking module 93 may be specifically configured to invoke an access tool provided by a service platform, so as to provide the object information to the access tool; wherein, the access tool comprises a check rule set; wherein the set of verification rules comprises at least one verification rule; the check rule is used for checking the attribute value.
The sending module 95 may be specifically configured to send the service object information to the service platform when the access tool successfully verifies the service object information.
In this embodiment, the receiving module 91 may specifically be a unit or a device having a data receiving function. Such as network communication units, data transceivers, etc. In a specific implementation, the receiving module 91 may receive the service object information provided by the client according to a network communication protocol.
In this embodiment, the calling module 93 may specifically be a processor having a data processing function. In particular, the calling module 93 may call an access tool provided by the service platform and stored locally. The access tool includes a check rule set provided by the service platform, and the calling module 93 may call the access tool to check the attribute value of the service object information according to the check rule set.
In this embodiment, if the verification is successful, the service object information may be sent to the service platform through the sending module 95. If the verification fails, the access tool may select, according to the attribute value of the business object, information closer to the attribute value from the verification rule set as a recommended value, and feed the recommended value back to the merchant through the sending module 95, so that the business object is referred by the merchant.
In this embodiment, the sending module 95 may specifically be a unit or a device having a data sending function. In specific implementation, the sending module 95 may send the service object information passing the verification to the service platform according to a network communication protocol. And the recommended value can also be sent to the merchant management terminal according to the network communication protocol.
Referring to fig. 11, the present application embodiment provides a client, which may specifically include an input device 82, a memory 84, a processor 86, and a network communication unit 88. The input device 82, the memory 84, the processor 86 and the network communication unit 88 may be connected through a data line inside the client, and further, data interaction may be performed between the components.
In this embodiment, the client may specifically be a merchant management terminal provided for a merchant to use. Through the client, a merchant can input the information of the business object to be published so as to publish the business object on the business platform.
The input device 82 may be specifically configured to input service object information to be published, where the service object information includes at least one attribute value.
The memory 84 may be specifically configured to store an access tool provided by the service platform; wherein, the access tool comprises a check rule set; wherein the set of verification rules comprises at least one verification rule; the check rule is used for checking the attribute value.
The processor 86 may be specifically configured to invoke an access tool provided by a service platform, so as to provide the service object information to the access tool; and checking the business object information based on the access tool.
The network communication unit 88 may be specifically configured to send the service object information to the service platform when the service object information is successfully verified.
In this embodiment, the input device 82 may be a keyboard, a mouse, a touch screen, or the like. Or a voice input device such as a microphone or a microphone having a voice recognition function. It may also be software with data input function, such as corresponding APP, etc. In specific implementation, a merchant may input the service object information to be published to the client through the input device.
In one particular scenario example, a lighting theater is to release the remaining ticket information for the theater a movie. The theatre light staff may first through the client input device 82: the mouse and the keyboard are used for inputting the information of the service objects to be released, namely the number of the residual movie tickets of the movie A of the optical movie theater. Wherein, the service object information includes a plurality of attribute values: "light cinema", "movie a" and "movie ticket". The client's processor 86, upon receiving the business object information, may invoke an access tool stored in memory 84 and provided by the business platform (e.g., the kvaray movie network) to check the attribute values of the piece of business object information. The access tool comprises a check rule set, the check rule set comprises at least one check rule, and the check rule is used for checking the attribute value. The processor 86 may utilize the access tool to perform specific verification of the attribute values of the business objects according to the verification rules in the set of verification rules. In case of successful verification, the processor 86 may send the to-be-published service object information to the service platform for publishing through the network communication unit 88 according to a network communication protocol, for example, Http, TCP/IP, FTP, or the like.
In one embodiment, the client may further include a display for providing the verification result information and the sending status information to the merchant.
In this embodiment, the display may be an electronic device such as a liquid crystal display or an LED display. In specific implementation, when the verification is successful, the display can display to the merchant: and prompting information of successful verification. When the information of the business object to be published is sent to the business platform, the display can display to a merchant: and sending successful prompt information. When the verification fails, the following can be displayed to the merchant through the display: if the verification fails, please re-input prompt information after the verification.
In this embodiment, in the case of a failure in verification, the processor may select, from the verification rules of the verification rule set, information closer to the attribute value as a recommended value according to the attribute value of the to-be-issued object information, and feed back the recommended value to the merchant. In particular, the processor may display to the merchant via the display: and if the verification fails, the prompt information input again after the verification is requested, and meanwhile, the related recommended value is displayed for the reference of the merchant, so that the merchant can find errors in time and input accurate information of the object to be issued.
Please refer to fig. 12. The embodiment of the application also provides a service object information publishing method based on the service platform. The method may specifically comprise the following steps.
Step S23: receiving service object information to be issued sent by a management end of a resource provider through a stored access tool; the business object information is verified through an access tool stored in the management terminal, the verification result is information of successful verification, and the business object information comprises at least one attribute value; the access tool stored by the management terminal is used for accessing the service platform; the access tool comprises a check rule set; wherein the set of verification rules comprises at least one verification rule; the check rule is used for checking the attribute value.
In this embodiment, the receiving, by the application service platform, the to-be-published object information sent by the merchant management end through the stored access tool may specifically be that the service platform receives, in a wired or wireless manner and according to a preset network communication protocol, the to-be-published service object information sent after the verification by the access tool stored in the merchant management end is passed. The business object information to be published may be specifically business object information that is prepared by a merchant to be published on a business platform and is input by using a merchant management terminal. For example, the number of rooms remaining in a hotel.
In this embodiment, the service object information received by the service platform may specifically be the service object information that is verified successfully after being verified by the access tool stored in the management terminal. Specifically, before the service object information to be issued is sent to the service platform, the access tool stored in the management terminal may perform verification, where the successfully verified service object information can be sent to and received by the service platform. The service object information which is not successfully verified or not verified by the access tool cannot be sent to the service platform, that is, the service platform cannot generally receive the service object information which is not successfully verified or not verified by the access tool. Therefore, the service platform can be better prevented from receiving the service object information of which the attribute value does not conform to the corresponding check rule, such as the service object information with a wrong name or the service object information with a wrong input format.
In this embodiment, the service object information includes at least one attribute value, and it is understood that the service object information may include one attribute value or may include a plurality of service attribute values. For example, the room price of XX hotel standard rooms includes three attribute values of hotel name, room type and price.
In this embodiment, the access tool may be specifically provided to the merchant management end by the service platform, and stored in the merchant management end. Of course, the service platform may also be a unit provided to the merchant management terminal, which is independent from the service platform and the merchant management terminal, but is electrically connected to the merchant management terminal. The access tool stored by the merchant management terminal is used for accessing the business platform, and it can be understood that the access tool can be used as a bridge for contacting the business platform and the merchant management terminal.
In this embodiment, the access tool includes a check rule set; wherein the set of verification rules comprises at least one verification rule; the check rule is used for checking the attribute value. Therefore, the access tool can verify the attribute value of the business object information to be issued on a merchant management end instead of a business platform according to the specific verification rule in the verification rule set. After the verification is passed, the access tool sends the information of the business object to be issued to the business platform through the merchant management end and receives the information by the business platform.
Step S25: and issuing the service object information.
In this embodiment, the issuing of the service object information may specifically be that the server of the service platform updates the corresponding service object information on the service platform according to the service object information. The update may specifically include one or more of the following: the existing information content of the original business object on the business platform is modified or deleted, the new information content of the original business object on the business platform is increased, and the information content of the new business object on the business platform is increased. And making the updated business object information accessible. Specifically, for example, the service object information is "a room price of 360 yuan between suzhou hotel standards", and the OTA website service platform may perform corresponding update according to the service object information, that is, the room price of the suzhou hotel standards on the OTA website is modified to "360 yuan". And makes the updated rate information accessible. In this manner, when a consumer issues a request to query the rate between Suzhou hotel standards, the service platform may provide the updated rate to the consumer.
In one embodiment, the service platform receives the service object information, and indicates that the at least one attribute value of the service object information passes the verification of the verification rule.
In this embodiment, the service platform receives the service object information, and may consider that the service object information has passed the verification of the access tool. Namely, at least one attribute value in the business object information passes the verification of the verification rule in the access tool. Specifically, it may be that an attribute value of the service object information passes the verification of the verification rule. For example, when the service object information is a train number of a train ticket, only one attribute value of the train number information is checked. The corresponding checking rule can be the current train number. And when the attribute value is the same as one train number in the verification rule, the verification result aiming at the attribute value is considered to be successful, namely the verification of the verification rule is passed. In this way, the access tool can send the business object information to the business object platform through the merchant management terminal. Further, the piece of service object information can be received by the service platform. Or the plurality of attribute values of the business object information are checked through the check rule. For example, when price of service object information is equal to or higher than a certain hotel standard room price, it is necessary to check each of a plurality of attribute values of the service object information. The plurality of attribute values may specifically include: hotel name, room type, price. Only after the three attribute values are verified by the verification rule, the service object information can be sent and then received. Of course, the service object information may also include a plurality of attribute values, but only one of the plurality of attribute values that is set as the attribute value of the key information is checked to pass through the check rule, that is, the service object information may be considered to pass through the check. The service object information can be sent and then received by the service platform.
In an embodiment, the method for publishing business object information may further be specifically executed with reference to the following steps.
S27: receiving the updating information; the update information is accompanied by at least one check rule.
In the present embodiment, update information is received. Specifically, the service platform may receive the update information from the platform management end. The platform management terminal can be a client terminal provided for the working personnel of the service platform and used for controlling and managing the service platform. The client can be an electronic device such as a desktop computer, a tablet computer, a notebook computer and a smart phone. Specifically, for example, in order to unify the data format in the service platform, the service platform of the OTA website receives the update information sent by the management end of the OTA website platform, which modifies all the time formats on the service platform from the original format of "XX year YY month ZZ date" to "XX/YY/ZZ". Or the service platform receives the updated information provided by the merchant. For example, the sun travel agency issues a modification request for changing the name of the travel agency to "moon travel agency" through the business administration side. And the service platform of the OTA website can receive the updated information of the travel agency about the change of the name of the travel agency through the merchant management terminal.
In this embodiment, the update information may be accompanied by at least one check rule, and specifically, one check rule may be accompanied by the update information, or a plurality of check rules may be accompanied by the update information. For example, the updated information of the moon travel agency, which is obtained by changing the name of the travel agency, is accompanied by a check rule about the name of the travel agency. The service platform can obtain the check rule through reading the updated information. The service platform can further modify and update the calibration rules corresponding to the calibration rule set stored in the service platform according to the acquired calibration rules. For example, the name of the travel agency of the solar travel agency in the original check rule may be modified to the moon travel agency according to the check rule attached to the update information provided by the travel agency.
S29: and sending at least one check rule attached to the updating information to a management end of the resource provider so as to update the check rule in the access tool.
In this embodiment, the at least one check rule attached to the update information is sent to the merchant management end, which may specifically be that the service platform sends one or more check rules in the update information to the merchant management end in a wired or wireless manner according to a preset communication protocol. For example, the OTA website service platform may send the check rule for changing the name of the travel agency attached to the update information to the merchant management terminal through the internet.
In this embodiment, the check rule attached to the update information is sent to the merchant management end, where the service platform sends the check rule attached to the update information to the merchant management end according to the preset rule and under the condition that the preset rule is satisfied. For example, the preset rule may be that when the service platform receives an update message with a verification rule attached, the verification rule is sent to the merchant management end. The preset rule may also be that when the service platform receives a plurality of update information with the check rule attached, and the number of the check rules attached by the accumulated plurality of update information reaches five, the five check rules are sent to the merchant management end together. The preset rule may also be that, when the service platform receives six update messages with verification rules attached, the service platform sends the verification rules attached to the six update messages to the merchant management terminal together. Of course, the preset rule may be other preset rules than the three listed preset rules. And corresponding preset rules can be flexibly designed according to actual requirements. Of course, in the present embodiment, the description relating to the number may be merely for example, and does not constitute a limitation of the specific number.
In this embodiment, the updating of the check rule in the access tool may be that after the merchant management end receives the check rule sent by the service platform, the access tool stored in the merchant management end obtains the check rule, and modifies and updates the corresponding check rule according to the check rule. Therefore, the check rule used for checking by the access tool is consistent with the check rule stored on the service platform, and the check error is avoided. For example, the access tool at the merchant management end can update the check rule about the name of the travel agency in the access tool according to the check rule for changing the name of the travel agency, which is sent by the OTA website service platform. I.e. the name of the travel agency in the check rule is modified to a new name of the travel agency.
In an embodiment, the method for publishing business object information may further be specifically executed with reference to the following steps.
S31: receiving a call notification sent by the access tool; the calling notification indicates that the access tool is called by the management terminal.
In this embodiment, the receiving of the call notification sent by the access tool may be that the service platform receives, in a wired or wireless manner, the call notification sent by the access tool stored in the merchant management end according to a preset communication protocol. The calling notice has a specified data format, the service platform can read and identify the calling notice, and the access tool of the merchant management terminal corresponding to the calling notice is determined to be sent according to the calling notice.
In this embodiment, the call notification indicates that the access instrument was called by the merchant management site. It can be understood that the service platform may determine, according to the verification notification, that the access tool sending the verification notification is being invoked by the corresponding merchant management terminal. However, it should be noted that, in the specific implementation, the access tool may send a call notification to the service platform every time the access tool is called, and the corresponding service platform receives a call notification. Or according to a preset rule, sending a calling notice when each preset time period of the access tool is called, and corresponding to the corresponding calling notice received by each preset time period of the service platform.
S33: sending verification rule set updating information to the management terminal so as to update the verification rules in the access tool; wherein the check rule set update information includes at least one check rule.
In this embodiment, the sending of the update information of the check rule set to the merchant management terminal may be that the service platform sends the update information of the check rule set to the merchant management terminal according to a preset rule when a condition specified by the preset rule is satisfied. For example, the preset rule may be that, each time the service platform receives the call notification, all updated check rules in the time period of the call notification of the last call notification are arranged into check rule set update information, and the check rule set update information is sent to the merchant management terminal. Specifically, when receiving the call notification, the service platform may retrieve a time point at which the access tool that sent the call notification last sent the call notification; searching updated check rules on the service platform in a time period from the last calling time point to the current calling time point (the updated check rules can comprise deletion and/or modification of the original check rules and addition of new check rules), and sorting the updated check rules into check rule set updating information; and then the updating information of the checking rule set is sent to a corresponding access tool in a wired or wireless mode. The preset rule may also be that after the service platform accumulatively receives five times of call notifications sent by the merchant management terminal, the service platform arranges the check rules updated on the service platform in the time period from the time point of sending the update information of the check rule set last time to the time point of this time into the more detailed information of the check rule set, and sends the more detailed information of the check rule set to the merchant management terminal. The preset rule may also be that after the service platform accumulates six updated check rules, the service platform arranges the six updated check rules into check rule set update information and sends the check rule set update information to the merchant management terminal when receiving the call notification. Of course, the preset rule may be other preset rules than the three listed preset rules. The design can be flexible according to actual needs. In this regard, the embodiments of the present application are not described. In a specific implementation, for example, the OTA website service platform receives a call notification sent by the access tool of the merchant management terminal a at 9: 30. The service platform retrieves that the time point of last call notification of the merchant management terminal A is 7:50 of the same day. According to the preset rule, the service platform can arrange the verification rule updated on the service platform into verification rule set updating information in the time period from 7:50 to 9:30, and the verification rule set updating information is sent to the merchant management terminal A through the network. Of course, in the present embodiment, the description relating to the number may be merely for example, and does not constitute a limitation of the specific number.
In this embodiment, the update information of the check rule set may specifically include one check rule, or may include a plurality of check rules. Of course, if the service platform does not have any update of the check rule according to the preset rule, the service platform may not send the update information of the check rule set to the merchant management terminal.
In this embodiment, the verification rule in the access tool is updated, and specifically, the verification rule in the access tool may be the access tool stored in the merchant management end, and the corresponding verification rule in the access tool is updated according to the verification rule set update information, so that the verification rule used by the access tool to verify the service object information is consistent with the verification rule stored on the service platform.
Fig. 13 is a structural diagram of a server based on a service platform according to an embodiment of the present invention. The server may specifically include: a receiving module 97 and a publishing module 99. This structure will be specifically explained below.
The receiving module 97 may be specifically configured to receive service object information to be issued, which is sent by a management end of a resource provider; wherein, the business object information comprises at least one attribute value; the management terminal stores an access tool of the service platform; the access tool comprises a check rule set; wherein the set of verification rules comprises at least one verification rule; the check rule is used for checking the attribute value.
The publishing module 99 may be specifically configured to publish the service object information.
In this embodiment, the receiving module 97 may specifically be a unit or a device having a data receiving function. Such as network communication units, data transceivers, etc. In a specific implementation, the receiving module 97 may receive the service object information provided by the client according to a network communication protocol. It should be noted that the business object information may specifically be the business object information that is verified by the access tool of the merchant management terminal.
In this embodiment, the issuing module 99 may specifically include a data updating unit having a data processing function. The updating, by the data updating unit, the service object information on the service platform according to the service object information may include: the existing information content of the original business object on the business platform is modified or deleted, the new information content of the original business object on the business platform is increased, and the information content of the new business object on the business platform is increased. And making the updated business object information accessible. Specifically, for example, the service object information is 80 vacant seats of the second class of the bullet train 801, and the publishing module 99 of the train ticket network service platform may modify the remaining number of vacant seats of the second class of the bullet train 801 to "80" according to the service object information through an internal data updating unit, and make the remaining number of vacant seats of the second class of the bullet train 801 be in a publicly accessible state. In this way, when the passenger sends a request for inquiring seats of the second class of 801 motor cars to the service platform through the internet, the updated amount of the remaining seats without seats can be provided to the passenger.
The embodiment of the application also provides a method for sending the business object information, which is applied to a management end of a resource provider. Specifically, referring to fig. 14, the method may specifically include the following steps.
S31: generating business object information to be issued; the information of the service object to be issued comprises at least one attribute value.
S33: sending the service object information to a server of a management end, so that the server calls an access tool of a stored service platform to provide the service object information to be issued to the access tool, wherein the access tool comprises a check rule set, the check rule set comprises at least one check rule, and the check rule is used for checking the attribute value; and the server is used for sending the information of the business object to be issued to the business platform when the verification result of the access tool on the information of the business object to be issued is successful, so that the business platform can issue the information of the business object to be issued.
In this embodiment, the generating of the to-be-released business object information may specifically be acquiring input information of a merchant, and generating the to-be-released business object information according to the input information of the merchant. Specifically, for example, a staff member of the lighting theater can press the white position in the name column of the theater through the touch screen and input the lighting theater. And then, selecting a movie name option in the popped item classification list about the lighting cinema, and inputting a movie name: a movie. The remaining movie tickets option is checked in the popped-up item category sub-list for movie a, and the number is entered: 30. according to the information input by the merchant, the corresponding business object information to be issued can be generated: the number of remaining tickets for the movie theatre a was 30.
In this embodiment, the information about the service object to be published may specifically include one attribute value, or may include a plurality of attribute values. For example, the business object information to be released, in which the number of remaining tickets of a movie in a movie theater a is 30, includes a plurality of attribute values, which are: "light cinema", "a movie", "30".
In this embodiment, the sending of the service object information to be published to the server of the management end may specifically be sending the service object information to be published to the server of the management end through an internal data connection or through a wireless network, for example, WIFI or bluetooth.
In this embodiment, the server at the management end may verify the information of the object to be distributed by calling an access tool provided by the service platform and stored in the server. The access tool comprises a check rule set consisting of one or more check rules. In specific implementation, the server can specifically verify the attribute value of the service object information to be issued according to the verification rule in the verification rule set through the access tool. And under the condition of successful verification, the server at the management end can send the service object information to be issued to the service platform for issuing according to a network communication protocol, such as Http, TCP/IP or FTP.
In this embodiment, in the case of a failure of verification, the server at the management end may generate a prompt message indicating that the verification fails, so as to prompt the verification failure, so as to regenerate accurate information of the service object to be issued after the check. Meanwhile, the server can search information which is closer to the attribute value of the information of the object to be issued as recommendation information according to the check rule set in the access tool. So that the error can be modified in time according to the recommendation information to generate accurate information of the object to be issued.
The embodiment of the application also provides a client. Specifically, please refer to fig. 15. The client may specifically include: a generation module 101, a calling module 103 and a sending module 105.
The generating module 101 may be specifically configured to generate service object information to be published; the information of the service object to be issued comprises at least one attribute value.
The invoking module 103 may be specifically configured to invoke an access tool stored by a client, so as to provide the service object information to the access tool; wherein, the access tool comprises a check rule set; wherein the set of verification rules comprises at least one verification rule; the check rule is used for checking the attribute value.
The sending module 105 may be specifically configured to send the to-be-issued service object information to the service platform when a verification result of the to-be-issued service object information by the access tool is successful, so that the service platform issues the to-be-issued service object information.
In this embodiment, the generating module 101 may specifically include a data input device and the like. In specific implementation, the generating module 101 may obtain, through the data input device, related information about the to-be-published business object information, and generate corresponding to-be-published business object information according to the obtained related information about the to-be-published business object information.
In this embodiment, the calling module 103 may specifically include an electronic device with data processing capability, such as a processor. In specific implementation, the calling module 103 may call the stored access tool to check the information of the service object to be published. Wherein, the access tool comprises a check rule set; wherein the set of verification rules comprises at least one verification rule; the check rule is used for checking the attribute value.
In this embodiment, the sending module 105 may specifically include a network communication unit. In specific implementation, the sending module 105 may send the verified information of the service object to be published to the service platform according to a network communication protocol, for example, Http, TCP/IP, or FTP, for publishing.
In this embodiment, the client may further include a prompt module, which is specifically configured to generate prompt information of a verification failure in the case of the verification failure, so that the generation module 101 regenerates accurate information of the service object to be published after checking.
In this embodiment, the client may further include a recommendation module, and specifically, the recommendation module may be configured to search, according to a check rule in the access tool, for a recommended value that is the most recommended value of information close to the to-be-released business object information, and send the recommended value to the generation module 101, so that the generation module 101 may generate accurate to-be-released business object information with the recommended value as a reference.
In this embodiment, the client may specifically be a merchant management terminal provided for a merchant to use. The business can send the business object information to be released to the business platform through the client. When the client is implemented specifically, the generation module 101 can be used for generating the information of the business object to be issued; calling an access tool stored in a client through a calling module 103 to check the information of the business object to be issued; and under the condition of successful verification, sending the information of the service object to be issued to the service platform through the sending module 105.
The embodiment of the application also provides a method for sending the business object information. Specifically, please refer to fig. 16. The above method may specifically comprise the following steps.
S41: and receiving the information of the service object to be issued.
S43: calling an access tool stored in a management terminal to verify the business object information to be issued; wherein, the access tool comprises a check rule set; wherein the set of verification rules includes at least one verification rule.
S45: and under the condition of successful verification, sending the information of the service object to be issued to a service platform.
In this embodiment, the business object sending method may be a business object sending method applied to a merchant management end.
In this embodiment, the to-be-published service object information may specifically include at least one attribute value. For example, the to-be-published business object information may be: the rent price of the class A rental houses rented by the XX elite apartment is 1000 yuan per month. The service object information to be released comprises three attribute values of 'XX elite apartment', 'class A rental housing' and '1000 yuan per month'. Of course, in specific implementation, the number of the attribute values of the service object information to be published may also be one, two, or four, five, and so on, according to specific situations. The number of attribute values included in the service object information to be issued is not limited in the present application.
In this embodiment, the access tool may be provided by the service platform, but is not stored in the server of the service platform. The access tool may be stored in the management side. Or the management terminal can be independent from the management terminal, but is connected with the management terminal in a wireless or wired mode. Thus, the management terminal can call the access tool in a wired or wireless mode.
In this embodiment, the upper access tool includes a check rule set, where the check rule set includes at least one check rule, and the check rule is used to check the attribute value. In specific implementation, the attribute value of the service object information to be issued can be specifically checked according to the check rule in the access tool.
In this embodiment, in the case that the verification is successful, the to-be-issued service object information may be sent to the service platform according to a network communication protocol. And under the condition of verification failure, prompt information of verification failure can be generated so as to obtain accurate information of the business object to be issued.
In this embodiment, in the case of a failure in verification, information that is closer to the information of the to-be-released service object may be searched from the verification rules of the verification rule set of the access tool as a recommended value according to the information of the to-be-released service object, so that accurate information of the to-be-released service object may be obtained according to the recommended value.
From the above description, it can be seen that the service object information sending method and the server provided in the embodiments of the present application avoid verifying the attribute value on the service platform by calling the access tool set locally and verifying the service object information by using the access tool, thereby solving the technical problems of low sending efficiency, large service platform workload and poor merchant experience in the existing information sending method, and achieving the technical effects of improving the information sending efficiency and improving the merchant experience; the check rule set in the access tool is extracted and stored in the local storage device, so that the check rule in the storage device can be directly called to check the attribute value of the service object during checking, and the information sending efficiency is improved; and the recommendation value is fed back to the merchant for reference through the access tool, so that the merchant experience is further improved, and the merchant can use the recommendation value conveniently.
Embodiments of the present application also provide a computer storage medium, in which program instructions may be stored. The program instructions when executed may implement: receiving business object information to be issued, wherein the business object information to be issued comprises at least one attribute value; calling an access tool of a service platform stored by the management terminal to provide the service object information to be issued to the access tool, wherein the access tool comprises a check rule set, the check rule set comprises at least one check rule, and the check rule is used for checking the attribute value; and when the verification result of the access tool on the to-be-released business object information is successful, sending the to-be-released business object information to the business platform so that the business platform can release the to-be-released business object information.
Embodiments of the present application also provide a computer-readable storage medium, in which computer program instructions may be stored. The program instructions, when executed by a processor, may implement: and generating business object information to be issued, wherein the business object information comprises at least one attribute value. Calling a stored access tool provided by a service platform to provide the service object information to the access tool; and checking the business object information based on the access tool. Wherein, the access tool comprises a check rule set; wherein the set of verification rules comprises at least one verification rule; the check rule is used for checking the attribute value. And sending the information of the business object to be issued to the business platform for the business platform to issue the information of the business object to be issued under the condition that the verification result of the access tool on the information of the business object to be issued is successful.
Embodiments of the present application also provide a computer storage medium, in which program instructions may be stored. The program instructions when executed may implement: receiving service object information to be issued sent by a management end of a resource provider through a stored access tool, wherein the service object information comprises at least one attribute value, the access tool stored by the management end is used for accessing the service platform, the access tool comprises a check rule set, the check rule set comprises at least one check rule, and the check rule is used for checking the attribute value; and issuing the service object information.
Embodiments of the present application also provide a computer-readable storage medium having computer program instructions stored therein. The program instructions, when executed by a processor, may implement: and receiving the information of the service object to be issued. And calling an access tool stored in a management terminal to verify the information of the business object to be issued. And under the condition of successful verification, sending the information of the service object to be issued to a service platform.
A computer storage medium may be a device with data storage capabilities. In particular, for example, computer storage media may include, but are not limited to, ROM/RAM, magnetic disks, optical disks, and the like. The specific functions and effects achieved when the program instructions are executed can be explained with reference to other embodiments.
In the 90 s of the 20 th century, improvements in a technology could clearly distinguish between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate a dedicated integrated circuit chip 2. Furthermore, nowadays, instead of manually making an Integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Language Description Language), traffic, pl (core unified Programming Language), HDCal, JHDL (Java Hardware Description Language), langue, Lola, HDL, laspam, hardbyscript Description Language (vhr Description Language), and the like, which are currently used by Hardware compiler-software (Hardware Description Language-software). It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.
From the above description of the embodiments, it is clear to those skilled in the art that the present application can be implemented by software plus necessary general hardware platform. Based on such understanding, the technical solutions of the present application may be essentially or partially implemented in the form of a software product, which may be stored in a storage medium, such as a ROM/RAM, a magnetic disk, an optical disk, etc., and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the method described in the embodiments or some parts of the embodiments of the present application.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments can be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the embodiments of the server, reference may be made to the introduction of embodiments of the method described above for a comparative explanation.
The application may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The application may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
Although the present application has been described in terms of embodiments, those of ordinary skill in the art will recognize that there are numerous variations and permutations of the present application without departing from the spirit of the application, and it is intended that the appended claims encompass such variations and permutations without departing from the spirit of the application.

Claims (17)

1. A method for sending business object information is applied to a management end of a resource provider, and is characterized in that the method comprises the following steps:
receiving business object information to be issued; the information of the business object to be issued comprises at least one attribute value;
calling an access tool of a service platform stored by a management terminal, and verifying the service object information to be issued; wherein, the access tool comprises a check rule set; wherein the set of verification rules comprises at least one verification rule; the check rule is used for checking the attribute value; the access tool is a tool which is provided for the management end by the service platform and is used for carrying out data interaction and verifying service object information with the service platform;
and when the access tool successfully verifies the to-be-released business object information, sending the to-be-released business object information to the business platform.
2. The method of claim 1, wherein in the step of invoking the access tool, further comprising:
sending a call notification to the service platform to notify that an access tool of the service platform is called;
receiving the updating information of the check rule set fed back by the service platform;
modifying the set of verification rules based on the verification rule set update information.
3. The method of claim 1, further comprising:
and when the access tool fails to verify the business object information, feeding back verification failure information to the client.
4. The method of claim 3, wherein the check failure information includes at least one recommended value matching the attribute value; the method further comprises the following steps:
in the verification rule for verifying the attribute value, obtaining a verification value matched with the attribute value based on a preset matching rule, wherein the obtained verification value is used as the recommended value; the check rule comprises at least one check value, and the check value is used as a reference for checking the attribute value.
5. The method according to claim 1, wherein the service object characterized by the service object information comprises any one of: airline tickets, hotel rooms, bus tickets, train tickets.
6. A server is applied to a management end of a resource provider and comprises a network communication unit, a memory and a processor;
the network communication unit is used for receiving service object information to be issued, which is provided by a client of a management end and comprises at least one attribute value; when the business object information passes the verification, the business object information is sent to the business platform;
the memory is used for storing an access tool provided by the service platform; wherein, the access tool comprises a check rule set; wherein the set of verification rules comprises at least one verification rule; the check rule is used for checking the attribute value; the access tool is a tool which is provided for the management end by the service platform and is used for carrying out data interaction and verifying service object information with the service platform;
the processor is used for calling an access tool provided by a service platform to provide the service object information to the access tool; and checking the business object information based on the access tool.
7. The server according to claim 6, wherein the processor calls the set of validation rules into a memory storage of the server prior to validating the business object information.
8. A server, applied to a management side of a resource provider, includes:
the receiving module is used for receiving the information of the business object to be issued, which is provided by the client of the management end; wherein, the business object information comprises at least one attribute value;
the calling module is used for calling an access tool which is provided by a service platform and stored in a server so as to provide the service object information to the access tool; wherein, the access tool comprises a check rule set; wherein the set of verification rules comprises at least one verification rule; the check rule is used for checking the attribute value; the access tool is a tool which is provided for the management end by the service platform and is used for carrying out data interaction and verifying service object information with the service platform;
and the sending module is used for sending the business object information to the business platform when the verification result of the access tool on the business object information is successful.
9. The client is applied to a management end of a resource provider and comprises an input device, a memory, a processor and a network communication unit;
the input equipment is used for inputting the service object information to be issued, and the service object information comprises at least one attribute value;
the memory is used for storing an access tool provided by the service platform; wherein, the access tool comprises a check rule set; wherein the set of verification rules comprises at least one verification rule; the check rule is used for checking the attribute value; the access tool is a tool which is provided for the management end by the service platform and is used for carrying out data interaction and verifying service object information with the service platform;
the processor is used for calling an access tool provided by a service platform to provide the service object information to the access tool; checking the business object information based on the access tool;
and the network communication unit is used for sending the service object information to the service platform under the condition that the service object information is successfully verified.
10. A method for releasing business object information is applied to a business platform, and the method comprises the following steps:
receiving service object information to be issued sent by a management end of a resource provider;
the business object information is verified through an access tool stored in the management terminal, the verification result is information of successful verification, and the business object information comprises at least one attribute value; the access tool stored by the management terminal is used for accessing the service platform; the access tool comprises a check rule set; wherein the set of verification rules comprises at least one verification rule; the check rule is used for checking the attribute value; the access tool is a tool which is provided for the management end by the service platform and is used for carrying out data interaction and verifying service object information with the service platform;
and issuing the service object information.
11. The method of claim 10, wherein the business object information is received, and wherein the at least one attribute value of the business object information is verified by the verification rule.
12. The method of claim 10, further comprising:
receiving the updating information; the updating information is attached with at least one check rule;
and sending at least one check rule attached to the updating information to the management end so as to update the check rule in the access tool.
13. The method of claim 10, further comprising:
receiving a call notification sent by the access tool; the calling notification represents that the access tool is called by the management terminal;
sending verification rule set updating information to the management terminal so as to update the verification rules in the access tool; wherein the check rule set update information includes at least one check rule.
14. A server, which is applied to a service platform, the method includes:
the receiving module is used for receiving the information of the service object to be issued sent by the management end of the resource provider; wherein, the business object information comprises at least one attribute value; the management terminal stores an access tool of the service platform; the access tool comprises a check rule set; wherein the set of verification rules comprises at least one verification rule; the check rule is used for checking the attribute value; the access tool is a tool which is provided for the management end by the service platform and is used for carrying out data interaction and verifying service object information with the service platform;
and the issuing module is used for issuing the service object information.
15. A method for sending business object information is applied to a client of a management end of a resource provider, and comprises the following steps:
generating business object information to be issued; the information of the business object to be issued comprises at least one attribute value;
sending the service object information to a server of a management end, so that the server calls a stored access tool of a service platform to provide the service object information to be issued to the access tool, wherein the access tool comprises a check rule set, the check rule set comprises at least one check rule, and the check rule is used for checking the attribute value; and the server is used for sending the information of the business object to be issued to the business platform when the access tool successfully verifies the information of the business object to be issued, so that the business platform can issue the information of the business object to be issued; the access tool is provided for the management end by the service platform and is used for carrying out data interaction with the service platform and verifying service object information.
16. A client, applied to a management side of a resource provider, the method includes:
the generating module is used for generating the business object information to be issued; the information of the business object to be issued comprises at least one attribute value;
the calling module is used for calling an access tool stored by a client to provide the business object information for the access tool; wherein, the access tool comprises a check rule set; wherein the set of verification rules comprises at least one verification rule; the check rule is used for checking the attribute value; the access tool is a tool which is provided for the management end by the service platform and is used for carrying out data interaction and verifying service object information with the service platform;
and the sending module is used for sending the to-be-issued business object information to the business platform under the condition that the verification result of the access tool on the to-be-issued business object information is successful, so that the business platform can issue the to-be-issued business object information.
17. A method for sending business object information is applied to a management end of a resource provider, and comprises the following steps:
receiving business object information to be issued; the information of the business object to be issued comprises at least one attribute value;
calling an access tool stored in a management terminal to verify the business object information to be issued; wherein, the access tool comprises a check rule set; wherein the set of verification rules comprises at least one verification rule; the check rule is used for checking the attribute value; the access tool is a tool which is provided for the management end by the service platform and is used for carrying out data interaction and verifying service object information with the service platform;
and under the condition of successful verification, sending the information of the service object to be issued to a service platform.
CN201710498559.5A 2017-06-27 2017-06-27 Service object information sending method, service object information publishing method, server and client Active CN109150940B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201710498559.5A CN109150940B (en) 2017-06-27 2017-06-27 Service object information sending method, service object information publishing method, server and client

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201710498559.5A CN109150940B (en) 2017-06-27 2017-06-27 Service object information sending method, service object information publishing method, server and client

Publications (2)

Publication Number Publication Date
CN109150940A CN109150940A (en) 2019-01-04
CN109150940B true CN109150940B (en) 2022-01-21

Family

ID=64804873

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201710498559.5A Active CN109150940B (en) 2017-06-27 2017-06-27 Service object information sending method, service object information publishing method, server and client

Country Status (1)

Country Link
CN (1) CN109150940B (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111159153B (en) * 2019-12-30 2023-08-29 北京三快在线科技有限公司 Service data verification method, device, computer equipment and storage medium
CN112070584A (en) * 2020-09-09 2020-12-11 畅销家(深圳)科技有限公司 Order management method, device, equipment and storage medium

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102314457A (en) * 2010-06-30 2012-01-11 百度在线网络技术(北京)有限公司 Automatic information auditing method and system
CN102411752A (en) * 2010-09-20 2012-04-11 杜卓 System and method for realizing information release accuracy
CN102868726A (en) * 2012-08-23 2013-01-09 北京神鹰城讯科技有限公司 Method and system for publishing Internet information
CN106027644A (en) * 2016-05-18 2016-10-12 广州市忆科计算机系统有限公司 Service checking method and system
CN106651407A (en) * 2015-07-17 2017-05-10 阿里巴巴集团控股有限公司 Data acquisition method and apparatus

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030130919A1 (en) * 2001-11-20 2003-07-10 Randy Templeton Systems and methods for selectively accessing financial account information

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102314457A (en) * 2010-06-30 2012-01-11 百度在线网络技术(北京)有限公司 Automatic information auditing method and system
CN102411752A (en) * 2010-09-20 2012-04-11 杜卓 System and method for realizing information release accuracy
CN102868726A (en) * 2012-08-23 2013-01-09 北京神鹰城讯科技有限公司 Method and system for publishing Internet information
CN106651407A (en) * 2015-07-17 2017-05-10 阿里巴巴集团控股有限公司 Data acquisition method and apparatus
CN106027644A (en) * 2016-05-18 2016-10-12 广州市忆科计算机系统有限公司 Service checking method and system

Also Published As

Publication number Publication date
CN109150940A (en) 2019-01-04

Similar Documents

Publication Publication Date Title
US11921798B2 (en) Generating a contextual search stream
US9092244B2 (en) System for developing custom data transformations for system integration application programs
US7937458B2 (en) On-demand software service system and method
US9158782B2 (en) Cloud based master data management system with configuration advisor and method therefore
US8850454B2 (en) Method and computer program product for integrating a first application providing a B2B gateway and one or more second applications
US9218387B2 (en) Cloud based master data management system and method therefor
US7962381B2 (en) Service designer solution
US9015106B2 (en) Cloud based master data management system and method therefor
US20130204884A1 (en) System to Automate Mapping of Variables Between Business Process Applications and Method Therefor
US9710282B2 (en) System to automate development of system integration application programs and method therefor
US9606995B2 (en) Cloud based master data management system with remote data store and method therefor
US8756254B2 (en) Integration of CRM applications to ECS application user interface
US20140040861A1 (en) Metadata driven software architecture
CN108510337B (en) Order generation and inventory updating method, client and server
US11282021B2 (en) System and method for implementing a federated forecasting framework
CN109150940B (en) Service object information sending method, service object information publishing method, server and client
US20240070149A1 (en) Database systems and client-side data synchronization methods
US20240070151A1 (en) Database systems and client-side query transformation methods
US11936531B2 (en) Transforming content in a document using chained applications in a client-server architecture
US11966770B2 (en) Collaboration across isolated virtual environments
US11949761B2 (en) Techniques for distributed interface component generation
US11075916B2 (en) Entitlement-driven communication of functionality privileges between network-based services
US20240070139A1 (en) Database systems and methods for client-side initiation of server-side actions
US20240070146A1 (en) Database systems and methods of batching data requests for application extensions
US20240069933A1 (en) Database systems and client-side field retrieval methods

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant