CN110070379B - Message transmission method, device and server - Google Patents

Message transmission method, device and server Download PDF

Info

Publication number
CN110070379B
CN110070379B CN201810067580.4A CN201810067580A CN110070379B CN 110070379 B CN110070379 B CN 110070379B CN 201810067580 A CN201810067580 A CN 201810067580A CN 110070379 B CN110070379 B CN 110070379B
Authority
CN
China
Prior art keywords
field
server
type
type field
supported
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
CN201810067580.4A
Other languages
Chinese (zh)
Other versions
CN110070379A (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 CN201810067580.4A priority Critical patent/CN110070379B/en
Publication of CN110070379A publication Critical patent/CN110070379A/en
Application granted granted Critical
Publication of CN110070379B publication Critical patent/CN110070379B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/02—Marketing; Price estimation or determination; Fundraising
    • G06Q30/0241—Advertisements
    • G06Q30/0242—Determining effectiveness of advertisements
    • G06Q30/0246—Traffic
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions
    • G06Q30/0601—Electronic shopping [e-shopping]
    • G06Q30/0611—Request for offers or quotes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/06—Message adaptation to terminal or network requirements
    • H04L51/066—Format adaptation, e.g. format conversion or compression
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Strategic Management (AREA)
  • Development Economics (AREA)
  • General Business, Economics & Management (AREA)
  • Physics & Mathematics (AREA)
  • Marketing (AREA)
  • General Physics & Mathematics (AREA)
  • Economics (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Game Theory and Decision Science (AREA)
  • Information Transfer Between Computers (AREA)
  • Computer And Data Communications (AREA)

Abstract

The application provides a message transmission method, a message transmission device and a server, wherein the method comprises the following steps: receiving a request message sent by a second server; acquiring a first type field from a field set corresponding to the second server; acquiring a second type field corresponding to the first type field and a parameter value corresponding to the second type field; the first type field is a field supported by a second server, and the second type field is a field supported by the first server; transmitting a response message to the request message to the second server; the response message is associated with the first type field and the parameter value. Through the technical scheme of this application, the consumption of manpower resources is significantly reduced.

Description

Message transmission method, device and server
Technical Field
The present application relates to the field of internet technologies, and in particular, to a message transmission method, device and server.
Background
The DSP (Demand Side Platform) is a cross-medium, cross-platform and cross-terminal advertisement delivery platform provided for advertisers, realizes accurate delivery based on audiences through data integration and analysis, and can monitor and optimize continuously in real time. ADX (Ad Exchange, advertisement transaction platform) is a large-scale transaction platform converging various media traffic, and is a transaction place for DSP to realize accurate purchasing of audience.
The DSP interacts with the ADX via an RTB (Real Time Bidding, real-time bidding) protocol, e.g., the ADX sends an RTB request message to the DSP to provide resource information to the DSP, and the DSP sends an RTB response message to the ADX to provide bid information to the ADX, which performs a bidding process according to the RTB response message.
When the DSP interacts with multiple ADXs, the RTB protocol is used for interaction, but the requirements of different ADXs on the format and content of the RTB response message are different. For example, ADX1 can only parse RTB response messages of format A, and ADX2 can only parse RTB response messages of format B.
Based on this, the user needs to develop software code for each ADX, such as developing software code a for ADX1, developing software code B for ADX 2; the DSP sends an RTB response message of format a to ADX1 based on software code a and the DSP sends an RTB response message of format B to ADX2 based on software code B.
However, the above method requires a large amount of software code to be developed by the user, and the consumption of human resources is relatively large.
Disclosure of Invention
The application provides a message transmission method, which is applied to a first server, and comprises the following steps:
receiving a request message sent by a second server;
acquiring a first type field from a field set corresponding to the second server;
Acquiring a second type field corresponding to the first type field and a parameter value corresponding to the second type field; the first type field is a field supported by a second server, and the second type field is a field supported by the first server;
transmitting a response message to the request message to the second server; wherein the response message is associated with the first type field and the parameter value.
The application provides a message transmission method applied to an advertisement demand side platform DSP, comprising the following steps:
receiving a real-time bidding RTB request message sent by an advertisement trading platform ADX;
acquiring a first type field from the field set corresponding to the ADX;
acquiring a second type field corresponding to the first type field and a parameter value corresponding to the second type field; the first type of field is a field supported by the ADX, and the second type of field is a field supported by the DSP;
and sending a response message for the request message to the ADX, wherein the response message is related to the first type field and the parameter value, so that the ADX performs advertisement bidding according to the response message.
The application provides a message transmission device, which is applied to a first server, and comprises:
The receiving module is used for receiving the request message sent by the second server;
the acquisition module is used for acquiring a first type field from the field set corresponding to the second server, and acquiring a second type field corresponding to the first type field and a parameter value corresponding to the second type field; the first type field is a field supported by a second server, and the second type field is a field supported by the first server;
a sending module, configured to send a response message for the request message to the second server; wherein the response message is associated with the first type field and the parameter value.
The present application provides a first server, the first server comprising:
the receiver is used for receiving the request message sent by the second server;
the processor is used for acquiring a first type field from the field set corresponding to the second server, and acquiring a second type field corresponding to the first type field and a parameter value corresponding to the second type field; the first type field is a field supported by a second server, and the second type field is a field supported by the first server;
a transmitter for transmitting a response message to the request message to the second server; wherein the response message is associated with the first type field and the parameter value.
Based on the above technical solution, in the embodiment of the present application, after receiving a request message sent by a second server, a first server may obtain a first type field (i.e., a field supported by the second server) from a field set corresponding to the second server, obtain a second type field corresponding to the first type field (i.e., a field supported by the first server) and a parameter value corresponding to the second type field, and then send a response message related to the first type field and the parameter value to the second server, so that the second server performs advertisement bidding processing according to the response message. The mode adopts the configuration management method to assemble the first type field and the parameter value corresponding to the response message, thereby greatly reducing the manpower resource consumption and avoiding the need of developing a large number of software codes for users.
Drawings
FIG. 1 is a schematic view of an application scenario in one embodiment of the present application;
FIG. 2 is a flow chart of a message transmission method in one embodiment of the present application;
FIG. 3 is a schematic diagram of field encoding in one embodiment of the present application;
FIG. 4 is a flow chart of a message transmission method in another embodiment of the present application;
FIG. 5 is a schematic diagram of a configuration interface in one embodiment of the present application;
FIG. 6 is a flow chart of a message transmission method in another embodiment of the present application;
FIG. 7 is a flow chart of a message transmission method in another embodiment of the present application;
fig. 8 is a block diagram of a message transmission apparatus in one embodiment of the present application.
Detailed Description
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this application and the claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to any or all possible combinations including one or more of the associated listed items.
It should be understood that although the terms first, second, third, etc. may be used herein to describe various information, these information should not be limited by these terms. These terms are only used to distinguish one type of information from another. For example, a first message may also be referred to as a second message, and similarly, a second message may also be referred to as a first message, without departing from the scope of the present application. Depending on the context, furthermore, the word "if" used may be interpreted as "at … …" or "at … …" or "in response to a determination".
In the embodiment of the present application, a message transmission method is provided, and the method may be applied to a system including a first server and a second server, where the number of the first servers may be one or more, and the number of the second servers may be one or more, and for convenience of description, a first server and a plurality of second servers are taken as an example, and the first server may be connected to each second server. Wherein the first server may include, but is not limited to, a DSP and the second server may include, but is not limited to, an ADX.
Referring to fig. 1, which is a schematic view of an application scenario in the embodiment of the present application, the first server may be a DSP101, and the second server may be an ADX102 or an ADX103. Of course, fig. 1 is only an example of the present application, and in practical application, the number of DSPs may be greater, and the number of ADXs may be greater.
In one example, DSP101 and ADX102/ADX103 may interact via an RTB protocol (e.g., openRTB, open real-time bidding protocol). Specifically, ADX102/ADX103 sends an RTB request message to DSP101 that may carry resource information, i.e., a resource for displaying an advertisement, such as a location of website a that is capable of displaying the advertisement. After receiving the RTB request message, the DSP101 may send an RTB response message to the ADX102/ADX103, where the RTB response message may carry bid information for the resource information, and advertisement information, where the bid information may be a bid for the resource information, such as 1.1 element, and the advertisement information may be an advertisement that needs to be displayed. After receiving the RTB response message, the ADX102/ADX103 can display the advertisement corresponding to the advertisement information at the position corresponding to the resource information if the bidding is determined to be successful according to the bidding information; if the bid is determined to be successful according to the bid information, the advertisement corresponding to the advertisement information is not displayed at the position corresponding to the resource information.
In one example, when DSP101 interacts with ADX102/ADX103, although the RTB protocol is used for interaction, the format and content requirements of the RTB response message are different for different ADXs, such as ADX102 parsing the RTB response message of format a, ADX103 parsing the RTB response message of format B, etc. For example, based on the need for RTB response messages, the RTB response messages received by ADX102 may carry field a, field B, and field C, while the RTB response messages received by ADX103 may carry field a, field B, field D, and field E. For another example, based on the demand for RTB response messages, RTB response messages received by ADX102 carry bid price information that is represented using "price=1.1", and RTB response messages received by ADX103 also carry bid price information, but that is represented using "price=1.1", and so on.
For the above findings, in the embodiment of the present application, the second field supported by the DSP101 (for convenience of distinction, the field supported by the DSP101 may be referred to as the second field) may be encoded to obtain the second field number corresponding to the second field (for convenience of distinction, the field number corresponding to the second field may be referred to as the second field number). In addition, based on the requirements of the ADX102/ADX103 on the format and the content of the RTB response message, the first type field supported by the ADX102/ADX103 (for convenience of distinction, the field supported by the ADX102/ADX103 may be referred to as a first type field) and the first field number corresponding to the first type field (for convenience of distinction, the field number corresponding to the first type field may be referred to as a first field number). Further, since the first type field supported by ADX102/ADX103 is known, the first type field may be carried in the RTB response message, such as the above-mentioned priority or priority.
In addition, the DSP101 may record locally "bid price=1.1", the "bid price" is a second type field supported by the DSP101, and "1.1" is a parameter value corresponding to the "bid price", and it is obvious that the parameter value of "1.1" cannot be queried using the first type field "price or" priority ". In summary, a first field number corresponding to a first field (e.g. "price or priority") may be used to query a second field number corresponding to the first field number, and then query a second field (e.g. "bid price") corresponding to the second field number, so that a parameter value "1.1" corresponding to the second field may be queried locally.
After the above processing, the RTB response message may carry the first type field "price or price", and the parameter value "1.1" corresponding to the first type field "price or price". Further, since the "price or the" priority "is a field of the first type supported by the ADX102/ADX103, the ADX102/ADX103 can correctly parse the RTB response message, and thus perform the bidding process based on the RTB response message.
In summary, for each ADX, the content of the RTB response message may be assembled based on the first field supported by the ADX, the first field number corresponding to the first field, the second field supported by the DSP, and the second field number corresponding to the second field, and the RTB response message supported by the ADX may be generated, so as to provide a configured management method, and greatly reduce the technical cost and the labor cost of docking.
The implementation flow of the message transmission method is described in detail below with reference to specific embodiments.
Referring to fig. 2, which is a flowchart of a message transmission method according to an embodiment of the present application, the method may be applied to a first server (such as the DSP101 described above), and the method may include the following steps:
step 201, a second type field supported by a first server is obtained.
Step 202, for the second type field supported by the first server, obtaining a second field number corresponding to the second type field, that is, for each second type field, obtaining a second field number corresponding to the second type field.
Step 203, record the corresponding relation between the second field and the second field number in the mapping table.
In one example, the above execution sequence is only given for convenience of description, and in practical application, the execution sequence between steps may be changed, which is not limited. Moreover, in other embodiments, the steps of the corresponding methods need not be performed in the order shown and described herein, and the methods may include more or less steps than described herein. Furthermore, individual steps described in this specification, in other embodiments, may be described as being split into multiple steps; various steps described in this specification, in other embodiments, may be combined into a single step.
In one example, the first server may perform steps 201-203 after normal operation to record the correspondence between the second type field and the second field number in the mapping table. Alternatively, the first server may perform steps 201-203 when interfacing with the first ADX to record the correspondence between the second type field and the second field number in the mapping table. Alternatively, the first server may perform steps 201 to 203 when the second type field supported by the first server changes (for example, the field a is supported before the change, and the fields a and B are supported after the change), so as to record the correspondence between the second type field and the second field number in the mapping table.
Of course, the above procedure is given only as a few examples, and the execution timing of the above steps is not limited, as long as the correspondence between the second type field and the second field number is recorded in the mapping table before the first server communicates with the second server (the first server sends the response message to the second server).
For step 201, in one example, the first server can obtain the second type of field that it supports, such as cur, customdata, price. As shown in fig. 3, for example, the second type field supported by the first server, where the second type field is not limited, the fields carried by the RTB response message may be the second type field.
With continued reference to fig. 3, the "id" in the first column indicates the identity of the requestor, which is associated with the resource information provided by the ADX, i.e., the identity of the resource information carried by the RTB request message. The first column, "seatbid" represents the seat identification of the bid, which can be understood as the identification of the RTB response message, i.e., what number of bids. The "bidid" of the first column represents the identity of the DSP. The first column of "cur" represents bidding units such as dollars, renminbi, pounds, and the like. The "customdata" of the first column represents user data, i.e., data related to the advertiser. The first column, "nbr" indicates the reason for no bidding, which may be given when the DSP is not bidding.
With continued reference to FIG. 3, the second column of "bid" represents the advertiser's bid identification. The second column of "seal" indicates the seat identification of the bid, i.e., the number of bids. The "group" of the second column indicates the group to which the advertiser belongs.
With continued reference to FIG. 3, the "id" of the third column represents the identification of the advertisement information, i.e., the identification of the advertisement provided by the DSP. The "impid" of the third column indicates the presentation identifier of the advertisement information, that is, the advertisement information is presented at the resource location corresponding to the presentation identifier. The third column of "price" represents the price of the bid, such as 1.1. The "adid" of the third column represents the identity of the advertiser. The third column, "nurl" indicates a post-deduction notification URL (Uniform Resource Locator ), such as a deduction notification sent to the URL after successful bidding and deduction indicating successful deduction. The "adm" of the third column indicates an address representing an advertisement from which the details of the advertisement can be found and displayed. The third column "adomain" represents domain information. The third column of "bundle" represents information binding the APP (application program), which is the package name of the APP. The third column, "iurl" represents the URL address of a binding APP from which the APP can be downloaded. The third column of "cid" represents the identity of the delivery plan. The third column of "crid" represents the identity of the impression creative. The third column "cat" represents a category table. The third column of "attr" represents creative attribute information. The third column of "dealid" represents private bid information. The third column of "h" represents the height information of the advertisement. The third column of "w" represents width information of the advertisement.
With respect to step 202, in one example, the process for "obtaining the second field number corresponding to the second field type" may include, but is not limited to: and encoding the second type field to obtain a second field number corresponding to the second type field. Specifically, in the process of encoding the second field to obtain the second field number corresponding to the second field, a preset encoding strategy may be adopted to encode the second field to obtain the second field number corresponding to the second field. Wherein, the preset encoding strategy is used for: for a plurality of second type fields of the same level, the second field numbers corresponding to the plurality of second type fields are numbered sequentially; for the second type field contained in the second type field nest of the previous level, a second field number corresponding to the second type field contained in the nest is generated based on the second field number of the second type field of the previous level.
Continuing with fig. 3, to encode the second field, an example of a second field number corresponding to the second field is obtained. For "id" of the first column, "seatbid" of the first column, "bidid" of the first column, "cur" of the first column, "customdata" of the first column, "nbr" of the first column are a plurality of second-class fields belonging to the same level, so that the second field numbers corresponding to these second-class fields are numbered sequentially, for example, the second field number corresponding to "id" is 01, the second field number corresponding to "seatbid" is 02, the second field number corresponding to "bidid" is 03, the second field number corresponding to "cur" is 04, the second field number corresponding to "customdata" is 05, and the second field number corresponding to "nbr" is 06.
For "bid" of the second column, "set" of the second column, and "group" of the second column are a plurality of second type fields belonging to the same level, and these second type fields may also be second type fields contained in the "seatbid" nest of the upper level, so the second field numbers of these second type fields may be generated based on the second field number 02 of "seatbid", for example, the second field number of "bid" is 0201, the second field number of "set" is 0202, and the second field number of "group" is 0203.
For all the fields in the third column, the fields are a plurality of second fields belonging to the same level, and the second fields may also be second fields contained in the nesting of the "bid" in the previous level, so the second field numbers of the second fields may be generated based on the second field number 0201 of the "bid", for example, the second field number 020101 of the "id" corresponding to the second field number 020102 of the "unique" corresponding to the second field number 020103 of the "unique", the second field number 020104 of the "aded" corresponding to the second field number 020105 of the "nurl", the second field number 020106 of the "ademain" corresponding to the second field number 020107, the second field number 020108 of the "bundle" corresponding to the second field number 02010A, the second field number 02010B "corresponding to the" C10 of the "C", the second field number 020h "corresponding to the" of the second field number 02010A, the "corresponding to the" C10 of the "C" corresponding to the "and the second field number 020h" corresponding to the second field number 02010.
In one example, the second field number is illustrated by hexadecimal, and in practical application, it may be represented by decimal, octal, or other system, which is not limited thereto. Also, when hexadecimal is employed, then the second field number 01 may be denoted as 0x01, 0201 may be denoted as 0x0201, 020101 may be denoted as 0x020101, and so on, and no further description is given of this second field number.
For step 203, in one example, after obtaining the second field and the second field number, the correspondence between the second field and the second field number may be recorded in the mapping table, as shown in table 1.
TABLE 1
Of course, the mapping table shown in table 1 is only an example, and the content of this mapping table is not limited.
Referring to fig. 4, which is a flowchart of a message transmission method according to an embodiment of the present application, the method may be applied to a first server (such as the DSP101 described above), and the method may include the following steps:
step 401, obtaining, from a second server, a first type field supported by the second server.
Step 402, adding the first type field to the field set corresponding to the second server.
In one example, the above execution sequence is only given for convenience of description, and in practical application, the execution sequence between steps may be changed, which is not limited. Moreover, in other embodiments, the steps of the corresponding methods need not be performed in the order shown and described herein, and the methods may include more or less steps than described herein. Furthermore, individual steps described in this specification, in other embodiments, may be described as being split into multiple steps; various steps described in this specification, in other embodiments, may be combined into a single step.
In one example, the first server may perform steps 401-402 while interfacing with the second server. Alternatively, the first server performs steps 401-402 when the first type of field supported by the second server changes (e.g., field a is supported before the change, and fields a and B are supported after the change).
Of course, the above procedure is given only as a few examples, and the execution timing of the above steps is not limited, as long as the first type field is already added to the field set corresponding to the second server before the first server communicates with the second server (the first server sends the response message to the second server).
For step 401, in one example, the second server can obtain the first type field supported by itself, such as cur, price, and the like, and provide the first type field to the first server, so that the first server can obtain the first type field supported by the second server from the second server, and the first type field is not limited.
With respect to step 402, in one example, the process for "adding the first type of field to the set of fields corresponding to the second server" may include, but is not limited to, the following: for the acquired first field supported by the second server, a first field number corresponding to the first field can be acquired, and the first field number are added into a field set corresponding to the second server.
For the process of acquiring the first field number corresponding to the first field, the first field may be displayed on the configuration interface, and the first field number corresponding to the first field may be input by the user, as shown in fig. 5, which is a schematic diagram of the configuration interface. When a user inputs a first field number corresponding to a first field, the first field number has a corresponding relation with the second field number. The first server may also establish a number table according to the correspondence between the first field number and the second field number.
For example, if the first type of fields displayed in the configuration interface include the priority and the dealid, the user knows that the meanings of the first type of fields priority are the same as the meanings of the second type of fields priority, so that the first field number 0xFF020103 is input for the first type of fields priority, and the first field number 0xFF020103 has a corresponding relationship with the second field number 020103, and the first server can record the corresponding relationship between the first field number 0xFF020103 and the second field number 020103 in the numbering table. In addition, the user knows that the meaning of the first type field dealid is the same as that of the second type field dealid, so that the first field number 0xFF02010E is input for the first type field dealid, the first field number 0xFF02010E has a corresponding relation with the second field number 02010E, and the first server records the corresponding relation between the first field number 0xFF02010E and the second field number 02010E in the numbering table.
Of course, the above-mentioned 0xFF020103, 0xFF02010E is just an example, and the user may also input other first field numbers, which is not limited. For example, the first field number 020103 may be input to the first type field priority, that is, the first field number 020103 is the same as the second field number 020103, so that even if no number table is generated, the first server can know the correspondence between the first field number and the second field number. For example, the first field number 120103 may be input for the first type field priority, and the first server may learn the correspondence between the first field number and the second field number according to the number table as long as the correspondence between the first field number 120103 and the second field number 020103 is recorded in the number table.
After the first type field and the first field number are obtained, a protobuf (Protocol buffers) storage mode may be used to store the correspondence between the first type field and the first field number, and of course, other storage modes may also be used to store the correspondence between the first type field and the first field number, which is not limited. For example, storage means such as XML (Extensible Markup Language ) or JSON (JavaScript Object Notation, java description language object markup) may be employed.
Through the above processing, a storage structure may be obtained, and the storage structure is referred to as a field set (i.e., fields sets), where each first type field supported by the second server and a first field number corresponding to each first type field are recorded in the field set, and includes a correspondence between the first type field and the first field number. The field sets may also be serialized into strings and stored in a database after base64 encoding.
In one example, when each second server interfaces with the first server, the first server may generate a set of fields corresponding to the second server, i.e., one set of fields for each second server. When a new second server is docked with the first server, a field set corresponding to the new second server may also be generated.
Referring to fig. 6, which is a flowchart of a message transmission method according to an embodiment of the present application, the method may be applied to a first server (such as the DSP101 described above), and the method may include the following steps:
step 601, a request message, such as an RTB request message, sent by a second server is received.
Step 602, obtaining a first type field from the field set corresponding to the second server.
Wherein the first type field is a field supported by the second server.
Step 603, obtaining a second field corresponding to the first field and a parameter value corresponding to the second field. Wherein the second type field is a field supported by the present first server.
Step 604, sending a response message to the request message to the second server, the response message being associated with the first type field and the parameter value. Wherein the response message may be an RTB response message.
In one example, the association of the response message with the first type field and the parameter value may specifically be: the response message carries the first type field and the parameter value.
In one example, the above execution sequence is only given for convenience of description, and in practical application, the execution sequence between steps may be changed, which is not limited. Moreover, in other embodiments, the steps of the corresponding methods need not be performed in the order shown and described herein, and the methods may include more or less steps than described herein. Furthermore, individual steps described in this specification, in other embodiments, may be described as being split into multiple steps; various steps described in this specification, in other embodiments, may be combined into a single step.
In one example, the first server may provide an online service, and after the second server has resource information (e.g., in a live scenario, the live page has resource information for displaying advertisements), an RTB request message may be sent to the first server, thereby triggering the first server to perform steps 601-604.
For step 602, in one example, since the field set corresponding to the second server has been generated and each field of the first type supported by the second server is recorded in the field set, each field of the first type supported by the second server may be obtained from the field set corresponding to the second server.
With respect to step 603, in one example, the process for "obtaining the second type field corresponding to the first type field" may include, but is not limited to, the following manners: acquiring a first field number corresponding to a first field from a field set corresponding to a second server, and determining a second field number corresponding to the first field number; then, inquiring a mapping table through the second field number to obtain a second type field corresponding to the second field number; the mapping table is used for recording the corresponding relation between the second field number and the second type field.
The field set corresponding to the second server is generated, and the first type of field supported by the second server and the first field number corresponding to the first type of field are recorded in the field set, so that the first field number corresponding to the first type of field can be obtained from the field set corresponding to the second server. For each first type field supported by the second server, a first field number corresponding to the first type field may be obtained from the field set, and for convenience of description, a first type field is taken as an example to be described later.
Wherein, for the process of determining the second field number corresponding to the first field number, the method may include, but is not limited to: mode one, a second field number identical to the first field number is determined. Or, in the second mode, the number table is queried through the first field number to obtain a second field number corresponding to the first field number; the numbering table is used for recording the corresponding relation between the first field number and the second field number.
If the user inputs the first field number for the first type of field, the first server may determine the second field number that is the same as the first field number, in the same manner as the first field number and the second field number.
In addition, if the first server generates a numbering table, and the numbering table records the corresponding relation between the first field number and the second field number, after obtaining the first field number, the first server may query the numbering table through the first field number to obtain the second field number corresponding to the first field number.
The above process has been described, and the first server generates a mapping table, where the mapping table is used to record the corresponding relationship between the second field number and the second field, so after obtaining the second field number, the mapping table can be queried through the second field number to obtain the second field corresponding to the second field number.
For step 603, in one example, for the "get parameter value corresponding to second class field" procedure, it may include, but is not limited to: because the second type field is a field supported by the first server, the first server can directly query the local data through the second type field to obtain a parameter value corresponding to the second type field. For example, the local data includes a correspondence between the price and 1.1 element, so that when the local data is queried through the price of the second field, the 1.1 element of the parameter value corresponding to the price can be obtained. Since the local data is not queried using the first type field references, there is no problem that the correct parameter value cannot be obtained.
Of course, the above procedure is only an example of obtaining the parameter value corresponding to the second type field from the local data, and the procedure is not limited as long as the parameter value corresponding to the second type field can be obtained from the local data.
With respect to step 604, in one example, the process for "send response message to request message to second server" may include: a response message to the request message is generated, in which a first type field supported by the second server is carried instead of the second type field supported by the first server. In addition, the parameter value carried in the response message is the parameter value of the second type field corresponding to the first type field. For example, the response message may carry a first type field priority, and a parameter value of 1.1.
The response message may be an RTB response message, such as a BidResponse message. The content carried by the response message may include all the first type fields supported by the second server, and the parameter values corresponding to the first type fields (i.e., the parameter values of the second type field corresponding to the first type field), where the content carried by the response message is not limited, and all the fields or part of the fields, and the parameter values of the fields shown in fig. 3 are not limited.
Based on the above technical solution, in the embodiment of the present application, after receiving a request message sent by a second server, a first server may obtain a first type field from a field set corresponding to the second server, and obtain a second type field corresponding to the first type field, and a parameter value corresponding to the second type field, and send a response message related to the first type field and the parameter value to the second server, so that the second server performs advertisement bidding processing according to the response message. The mode adopts the configuration management method to assemble the first type field and the parameter value corresponding to the response message, thereby greatly reducing the manpower resource consumption and avoiding the need of developing a large number of software codes for users.
Based on the same application concept as the above method, the embodiment of the present application further provides a message transmission method, which can be applied to a DSP, and is shown in fig. 7, which is a flow chart of the method.
Step 701, receiving an RTB request message sent by ADX.
Step 702, obtaining a first field from the field set corresponding to the ADX.
Step 703, obtaining a second field corresponding to the first field and a parameter value corresponding to the second field; the first type of field is an ADX supported field and the second type of field is a DSP supported field.
Step 704, sending a response message for the request message to the ADX, where the response message is related to the first type field and the parameter value, so that the ADX performs advertisement bidding according to the response message.
The process flow of steps 701 to 704 is similar to the above embodiment, and the detailed description is not repeated.
Based on the same application concept as the above method, the embodiment of the present application provides a message transmission device, which can be applied to a first server. As shown in fig. 8, which is a structural diagram of the apparatus, the apparatus includes:
a receiving module 801, configured to receive a request message sent by a second server;
an obtaining module 802, configured to obtain a first type field from a field set corresponding to the second server, and obtain a second type field corresponding to the first type field and a parameter value corresponding to the second type field; the first type field is a field supported by a second server, and the second type field is a field supported by the first server;
a sending module 803, configured to send a response message for the request message to the second server; wherein the response message is associated with the first type field and the parameter value.
The obtaining module 802 is further configured to obtain, from a second server, a first field supported by the second server, and add the first field supported by the second server to a field set corresponding to the second server;
when a first field supported by the second server is added to a field set corresponding to the second server, a first field number corresponding to the first field is acquired for the acquired first field, and the first field number are added to the field set corresponding to the second server.
The obtaining module 802 is specifically configured to obtain, from a field set corresponding to the second server, a first field number corresponding to the first field, and determine a second field number corresponding to the first field number, in a process of obtaining a second field corresponding to the first field;
inquiring a mapping table through the second field number to obtain a second type field corresponding to the second field number; the mapping table is used for recording the corresponding relation between the second field number and the second type field.
The obtaining module 802 is further configured to obtain, for a second field supported by the first server, a second field number corresponding to the second field before obtaining the second field corresponding to the first field, and record, in a mapping table, a correspondence between the second field and the second field number;
In the process of determining a second field number corresponding to the first field number, inquiring a number table through the first field number to obtain the second field number corresponding to the first field number; the numbering table is used for recording the corresponding relation between the first field number and the second field number.
Based on the same application concept as the above method, the embodiment of the present application provides a first server, where the first server may include: a receiver, a processor, and a transmitter; the receiver is used for receiving the request message sent by the second server; the processor is configured to obtain a first type field from a field set corresponding to the second server, and obtain a second type field corresponding to the first type field and a parameter value corresponding to the second type field; the first type field is a field supported by a second server, and the second type field is a field supported by the first server; the transmitter is configured to send a response message to the request message to the second server; the response message is associated with the first type field and the parameter value.
Based on the same application concept as the above method, the embodiments of the present application further provide a machine-readable storage medium, where a number of computer instructions are stored, and when executed, perform the following processes: receiving a request message sent by a second server; acquiring a first type field from a field set corresponding to the second server; acquiring a second type field corresponding to the first type field and a parameter value corresponding to the second type field; the first type field is a field supported by a second server, and the second type field is a field supported by the first server; transmitting a response message to the request message to the second server; wherein the response message is associated with the first type field and the parameter value.
The system, apparatus, module or unit set forth in the above embodiments may be implemented in particular by a computer chip or entity, or by a product having a certain function. A typical implementation device is a computer, which may be in the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or a combination of any of these devices.
For convenience of description, the above devices are described as being functionally divided into various units, respectively. Of course, the functions of each element may be implemented in one or more software and/or hardware elements when implemented in the present application.
It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present application may take the form of a computer program product on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
Moreover, these computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The foregoing is merely exemplary of the present application and is not intended to limit the present application. Various modifications and changes may be made to the present application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc. which are within the spirit and principles of the present application are intended to be included within the scope of the claims of the present application.

Claims (15)

1. A method of message transmission, applied to a first server, the method comprising:
receiving a request message sent by a second server;
acquiring a first type field from a field set corresponding to the second server;
acquiring a second type field corresponding to the first type field, and inquiring local data through the second type field to obtain a parameter value corresponding to the second type field; the first type field is a field supported by the second server, and the first type field is a field not supported by the first server, and the second type field is a field supported by the first server; wherein the second server is any one of a plurality of second servers, and the first type field is a field not supported by other second servers;
Transmitting a response message to the request message to the second server; wherein the response message is related to parameter values corresponding to the first type field and the second type field.
2. The method according to claim 1, wherein before the obtaining the first type of field from the field set corresponding to the second server, the method further includes:
acquiring a first type field supported by the second server from the second server;
and adding the first type field supported by the second server to a field set corresponding to the second server.
3. The method according to claim 2, wherein the process of adding the first type of field supported by the second server to the field set corresponding to the second server specifically includes:
and aiming at the acquired first field, acquiring a first field number corresponding to the first field, and adding the first field and the first field number to a field set corresponding to a second server.
4. A method according to claim 1 or 3, characterized in that,
the process of obtaining the second type field corresponding to the first type field specifically includes:
Acquiring a first field number corresponding to the first field from a field set corresponding to the second server, and determining a second field number corresponding to the first field number;
inquiring a mapping table through the second field number to obtain a second type field corresponding to the second field number; the mapping table is used for recording the corresponding relation between the second field number and the second type field.
5. The method of claim 4, wherein the step of determining the position of the first electrode is performed,
before the second type field corresponding to the first type field is obtained, the method further includes:
and aiming at a second field supported by the first server, acquiring a second field number corresponding to the second field, and recording the corresponding relation between the second field and the second field number in a mapping table.
6. The method of claim 5, wherein the step of determining the position of the probe is performed,
the process of obtaining the second field number corresponding to the second type field specifically includes:
and encoding the second type field to obtain a second field number corresponding to the second type field.
7. The method of claim 6, wherein the encoding the second field to obtain the second field number corresponding to the second field specifically includes:
Encoding the second type field by adopting a preset encoding strategy to obtain a second field number corresponding to the second type field; wherein, the preset encoding strategy is used for: for a plurality of second type fields of the same level, the second field numbers corresponding to the plurality of second type fields are numbered sequentially;
for the second type field contained in the second type field nest of the previous level, the second field number corresponding to the second type field contained in the nest is generated based on the second field number of the second type field of the previous level.
8. The method of claim 4, wherein the step of determining the position of the first electrode is performed,
the process of determining the second field number corresponding to the first field number specifically includes:
inquiring a numbering table through the first field number to obtain a second field number corresponding to the first field number; the numbering table is used for recording the corresponding relation between the first field number and the second field number.
9. The method according to claim 1, wherein the first server comprises in particular an advertisement-requiring side platform DSP and the second server comprises in particular an advertisement transaction platform ADX; the request message specifically comprises a real-time bidding RTB request message, and the response message specifically comprises an RTB response message.
10. A method of message transmission, for use with an advertising demand side platform DSP, comprising:
receiving a real-time bidding RTB request message sent by an advertisement trading platform ADX;
acquiring a first type field from the field set corresponding to the ADX;
acquiring a second type field corresponding to the first type field, and inquiring local data through the second type field to obtain a parameter value corresponding to the second type field; the first type of field is a field supported by the ADX, and the first type of field is a field not supported by the DSP, and the second type of field is a field supported by the DSP; wherein the ADX is any ADX of a plurality of ADXs, and the first type field is a field not supported by other ADXs;
and sending a response message aiming at the request message to the ADX, wherein the response message is related to the parameter values corresponding to the first type field and the second type field, so that the ADX carries out advertisement bidding processing according to the response message.
11. A message transmission apparatus for use with a first server, the apparatus comprising:
the receiving module is used for receiving the request message sent by the second server;
the acquisition module is used for acquiring a first type field from the field set corresponding to the second server, acquiring a second type field corresponding to the first type field, and inquiring local data through the second type field to obtain a parameter value corresponding to the second type field; the first type field is a field supported by the second server, and the first type field is a field not supported by the first server, and the second type field is a field supported by the first server; wherein the second server is any one of a plurality of second servers, and the first type field is a field not supported by other second servers;
A sending module, configured to send a response message for the request message to the second server; wherein the response message is related to parameter values corresponding to the first type field and the second type field.
12. The apparatus of claim 11, wherein the device comprises a plurality of sensors,
the acquisition module is further configured to acquire a first field supported by a second server from the second server, and add the first field supported by the second server to a field set corresponding to the second server;
when a first field supported by the second server is added to a field set corresponding to the second server, a first field number corresponding to the first field is acquired for the acquired first field, and the first field number are added to the field set corresponding to the second server.
13. The device according to claim 11 or 12, wherein,
the acquiring module is specifically configured to acquire a first field number corresponding to the first field from a field set corresponding to the second server in a process of acquiring a second field corresponding to the first field, and determine a second field number corresponding to the first field number;
Inquiring a mapping table through the second field number to obtain a second type field corresponding to the second field number; the mapping table is used for recording the corresponding relation between the second field number and the second type field.
14. The apparatus of claim 13, wherein the device comprises a plurality of sensors,
the obtaining module is further configured to obtain, for a second field supported by the first server, a second field number corresponding to the second field before obtaining the second field corresponding to the first field, and record, in a mapping table, a correspondence between the second field and the second field number;
in the process of determining a second field number corresponding to the first field number, inquiring a number table through the first field number to obtain the second field number corresponding to the first field number; the numbering table is used for recording the corresponding relation between the first field number and the second field number.
15. A first server, the first server comprising:
the receiver is used for receiving the request message sent by the second server;
the processor is used for acquiring a first type field from the field set corresponding to the second server, acquiring a second type field corresponding to the first type field, and inquiring local data through the second type field to obtain a parameter value corresponding to the second type field; the first type field is a field supported by the second server, and the first type field is a field not supported by the first server, and the second type field is a field supported by the first server; wherein the second server is any one of a plurality of second servers, and the first type field is a field not supported by other second servers;
A transmitter for transmitting a response message to the request message to the second server; wherein the response message is related to parameter values corresponding to the first type field and the second type field.
CN201810067580.4A 2018-01-24 2018-01-24 Message transmission method, device and server Active CN110070379B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201810067580.4A CN110070379B (en) 2018-01-24 2018-01-24 Message transmission method, device and server

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201810067580.4A CN110070379B (en) 2018-01-24 2018-01-24 Message transmission method, device and server

Publications (2)

Publication Number Publication Date
CN110070379A CN110070379A (en) 2019-07-30
CN110070379B true CN110070379B (en) 2024-03-12

Family

ID=67365535

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201810067580.4A Active CN110070379B (en) 2018-01-24 2018-01-24 Message transmission method, device and server

Country Status (1)

Country Link
CN (1) CN110070379B (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112230983B (en) * 2020-10-15 2021-08-03 上海嗨普智能信息科技股份有限公司 Information processing method, electronic device, and medium
CN112991023B (en) * 2021-04-22 2021-11-02 深圳华锐金融技术股份有限公司 Order data processing method and device, computer equipment and storage medium

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7010503B1 (en) * 2000-03-10 2006-03-07 Ams Services, Inc. Traffic reduction in networked data collection
EP1906608A1 (en) * 2006-09-30 2008-04-02 Samsung Electronics Co., Ltd. Apparatus and method for interfacing in a communication system
CN103491146A (en) * 2013-09-10 2014-01-01 百川通联（北京）网络技术有限公司 Method, device and system for releasing network information
WO2014145905A2 (en) * 2013-03-15 2014-09-18 Brightroll, Inc. Compact data interface for real time bidding in digital video advertisement systems
CN104102655A (en) * 2013-04-09 2014-10-15 腾讯科技（北京）有限公司 Method, system and device for releasing media information
CN106846062A (en) * 2017-01-22 2017-06-13 腾讯科技（深圳）有限公司 A kind of control method, the advertisement transaction platform of the advertisement exposure frequency
CN107171970A (en) * 2017-05-05 2017-09-15 湖南快乐阳光互动娱乐传媒有限公司 Method and system for advertisement delivery in real-time bidding system

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140358680A1 (en) * 2013-06-04 2014-12-04 Chacha Search, Inc. Method and system for advertisements in responses

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7010503B1 (en) * 2000-03-10 2006-03-07 Ams Services, Inc. Traffic reduction in networked data collection
EP1906608A1 (en) * 2006-09-30 2008-04-02 Samsung Electronics Co., Ltd. Apparatus and method for interfacing in a communication system
WO2014145905A2 (en) * 2013-03-15 2014-09-18 Brightroll, Inc. Compact data interface for real time bidding in digital video advertisement systems
CN104102655A (en) * 2013-04-09 2014-10-15 腾讯科技（北京）有限公司 Method, system and device for releasing media information
CN103491146A (en) * 2013-09-10 2014-01-01 百川通联（北京）网络技术有限公司 Method, device and system for releasing network information
CN106846062A (en) * 2017-01-22 2017-06-13 腾讯科技（深圳）有限公司 A kind of control method, the advertisement transaction platform of the advertisement exposure frequency
CN107171970A (en) * 2017-05-05 2017-09-15 湖南快乐阳光互动娱乐传媒有限公司 Method and system for advertisement delivery in real-time bidding system

Also Published As

Publication number Publication date
CN110070379A (en) 2019-07-30

Similar Documents

Publication Publication Date Title
JP6968100B2 (en) How to identify user behavioral preferences and how to present recommended information and devices
US9715554B2 (en) Methods and apparatus to identify usage of quick response codes
CA2767699C (en) Methods and systems to present network notifications in conjunction with display advertisements
US20140237496A1 (en) Audience segment validation device and method
CN106471539A (en) System and method for obscuring audience measurement
CN110148014B (en) Information processing method, information processing device, blockchain node equipment and storage medium
CN105894313A (en) Methods And Apparatus To Associate Transactions With Media Impressions
CN106101157A (en) Via AD tagged content combination in media based on web
CN104981795A (en) Conversion tracking for installation of applications on mobile devices
KR20130005776A (en) Receiver terminal capable of playing cid contentstmt, server and method for providing cid contents service
CN103226780A (en) Method for determining advertisement space channel and advertisement release server
US12079832B2 (en) Method and system for identifying recipients of a reward associated with a conversion
JP2004185589A (en) Point linkage system
CN110070379B (en) Message transmission method, device and server
CN111522735A (en) Shunting method and device for test experiment
US20190066154A1 (en) Escrow Agent for Conversion Verification
US20240289840A1 (en) Method and system for identifying recipients of a reward associated with a conversion
CN108053237A (en) A kind of crowd portrayal report-generating method, advertisement placement method and platform
TWI808949B (en) Data object information processing method, device and system
CN106709749B (en) Media information delivery method and server
CN110580637A (en) advertisement putting method, demander platform and computer storage medium
US20170316454A1 (en) System and Methods for Determining Consumer Brand Awareness of Online Advertising Using Recognition
CN111865753A (en) Method and device for determining parameters of media information, storage medium and electronic device
CN113781144B (en) Live shopping order generation method, device, electronic equipment and computer medium
JP2009252217A (en) Content distribution control device, content distribution control method, and content distribution control system

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
REG Reference to a national code

Ref country code: HK

Ref legal event code: DE

Ref document number: 40010992

Country of ref document: HK

GR01 Patent grant
GR01 Patent grant