Data processing method and equipment

Abstract

The embodiment of the invention provides a data processing method and equipment, and relates to the technical field of data processing. According to the method, the operation equipment can realize rapid and efficient interaction with the user equipment and the CP equipment, so that the user equipment can efficiently obtain the promotion content for display. The method comprises the following steps: receiving a service calling request, wherein the service calling request is used for obtaining promotion content corresponding to a first service; first verification information corresponding to the first service is obtained, the first verification information is used for judging whether a first interface is available or not, and the first interface is an interface corresponding to the first service; under the condition that the first verification information indicates that the first interface is available, first content data are obtained, and the first content data comprise promotion content corresponding to the first service. And sending the first service data to the user equipment, wherein the first service data corresponds to the first content data.

Description

Technical Field

[0001] This application relates to the field of data processing technology, and in particular to a data processing method and apparatus. Background Technology

[0002] Currently, a user's electronic device (referred to as a user device) can provide the user with a variety of different services. For example, these various services may include the push display of promotional content.

[0003] For example, a user device can obtain data on promotional content from an operator device. The operator device, in turn, can obtain relevant information from the corresponding content provider (CP) device based on the user device's needs.

[0004] As promotional content becomes increasingly diverse, the operational equipment will interact with multiple content provider (CP) devices to deliver various promotional content corresponding to different services to user devices. Therefore, the operational equipment needs to be able to interact efficiently with each CP device and / or user device. Summary of the Invention

[0005] This application provides a data processing method and apparatus that enables operating equipment to achieve fast and efficient interaction with user equipment and CP equipment, thereby enabling user equipment to efficiently obtain and display promotional content.

[0006] In some implementations, this solution can provide corresponding interface configurations for different services, thereby enabling CP devices to quickly and efficiently apply for and access the corresponding service interfaces. In some implementations, the operation equipment can also manage the applied interfaces. In some implementations, the operation equipment can also quickly and efficiently provide corresponding service data based on user device requests, so that user devices can display promotional content based on the service data.

[0007] To achieve the above technical objectives, this application adopts the following technical solution:

[0008] Firstly, a data processing method is provided, applied to a first device for providing promotional content to a user device. The method includes: receiving a service call request for obtaining promotional content corresponding to a first service; obtaining first verification information corresponding to the first service for determining whether a first interface is available, wherein the first interface is the interface corresponding to the first service; if the first verification information indicates that the first interface is available, obtaining first content data, the first content data including the promotional content corresponding to the first service; and sending the first service data to the user device, wherein the first service data corresponds to the first content data.

[0009] In this way, the first device can trigger the retrieval of corresponding promotional content based on the request sent by the user device. In this example, the first device can verify the first verification information before retrieving the promotional content to avoid responding to invalid requests. Once the business call request is confirmed to be valid, the first device can quickly retrieve the first content data based on the configured information of the first interface of the first business and provide the corresponding first business data to the user device. This improves the efficiency of the user device in retrieving the content data of the first business.

[0010] Optionally, the first device stores first configuration information corresponding to the first interface. This first configuration information includes request header information and / or request body information. Before obtaining the first verification information corresponding to the first service, the method further includes: obtaining the first configuration information; and determining that the service call request is valid based on the service call request and the first configuration information.

[0011] Optionally, the first configuration information includes at least one required field, and determining that the service call request is valid includes: determining that in the service call request, none of the required fields indicated by the first configuration information are empty.

[0012] Therefore, the first device can negotiate and specify the format and content of service call request information with other devices such as user equipment through the first configuration information. Furthermore, this first configuration information enables the first device to efficiently determine whether a currently received service call request is available.

[0013] Optionally, the first verification information includes at least one of the following: the signature verification rule corresponding to the first interface, the basic information corresponding to the first interface, the request header information corresponding to the first interface, and the request body information corresponding to the first interface.

[0014] Optionally, the first verification information includes the signature verification rule corresponding to the first interface, and the signature verification rule indicates the data encryption / decryption method corresponding to the first service. The first verification information indicating that the first interface is available includes: the signature verification rule of the service call request is consistent with the first signature verification rule, and the first signature verification rule is the signature verification rule corresponding to the first service.

[0015] Optionally, the first device has a preset first reference field. The first reference field includes data of a first parameter encrypted according to the first verification rule. The first parameter is a parameter that needs to be carried in a preset business call request. The method further includes: obtaining the first parameter from the business call request; encrypting the first parameter according to the first verification rule to obtain first verification data; and determining that the verification rule of the business call request is consistent with the first verification rule based on the consistency between the first verification data and the first reference field.

[0016] Optionally, the first parameter includes: the first application identifier AppID corresponding to the first service, and / or the timestamp corresponding to the first service.

[0017] This solution provides a specific method for verifying signature rules. In this application, different services can use different signature verification rules. Thus, before subsequent data transmission, the first device can verify these rules to further determine whether the service call request uses pre-agreed rules (such as the relevant configuration of the first interface), and to ensure smooth subsequent data transmission.

[0018] Optionally, before obtaining the first content data, the method further includes: determining that there is a first sub-interface, which corresponds to an effective interface application, which is an access request for the first interface, and different interface applications correspond to different content provider (CP) devices.

[0019] Optionally, the first sub-interface corresponds to a second device, which is a CP device. Before acquiring the first content data, the method further includes: receiving an access request from the second device, the access request being used to request access to the first interface; storing the data of the access request. The access request data includes a first interface address URL, and the address indicated by the first interface URL stores the first data provided by the second device corresponding to the first service. Acquiring the first content data includes: acquiring the first content data from the first URL indicated by the first sub-interface. The first content data includes the first data provided by the second device.

[0020] In this application, the process of making the interface effective may include: interface configuration, interface application, review and confirmation, configuration taking effect, etc.

[0021] Specifically, after the second device initiates an interface request for the first interface, the first device can review and confirm the request to control whether the interface request can continue to be used subsequently. The first device can also achieve fine-grained management of reviewed and confirmed access requests by adding or removing them from the "currently called interfaces".

[0022] Optionally, before sending the first service data to the user equipment, the method further includes: determining the existence of a second sub-interface, the second sub-interface corresponding to a valid interface application, the interface application being an access request for the first interface. The second sub-interface corresponds to a third device. The third device is a CP device. Obtaining second content data from the third device. Generating the first service data based on the first content data and the second content data. For example, the first device can perform aggregation processing based on the first content data and the second content data to generate the first service data.

[0023] Therefore, the first device can simultaneously obtain content data from multiple CP devices when the first interface has been reviewed and confirmed by multiple CP devices and the configuration is effective. By aggregating and processing the obtained first service data, the first device can send all content data to the user device in a single communication, thereby reducing the corresponding communication overhead.

[0024] Optionally, the first device stores second configuration information corresponding to the first interface. This second configuration information includes response body information. After obtaining the first content data, the method further includes: obtaining the second configuration information corresponding to the first interface. Based on the first content data and the second configuration information, the validity of the first content data is determined.

[0025] Optionally, the second configuration information includes at least one required field. Determining the validity of the first content data includes: determining that none of the required fields indicated by the second configuration information in the first content data are empty.

[0026] In this way, after receiving the content data, the first device can also verify the content data according to the configured response body information corresponding to the first interface. If the verification passes, the validity of the content data can be guaranteed, thereby ensuring the validity and accuracy of the business data sent by the first device to the user device.

[0027] In the above implementation, the functions and processing of the first device are defined by the response after the first device receives the service call request. In some implementations, the first device can configure corresponding interfaces for each service. After the configuration is completed, each user device and CP device can interact with the first device according to the interface configuration (such as signature verification information, basic information, request header information, request body information, response body information, etc.) when it needs to use the corresponding service.

[0028] During the interface configuration process, the first device can provide a corresponding visual interface for easy configuration. After the interface configuration is complete, the first device can submit its request to the CP device via its corresponding visual interface, allowing the CP device to apply for access.

[0029] Optionally, before receiving a business call request, the method further includes configuring at least one of the following information for the first interface: signature verification rules, request header information, request body information, and response body information.

[0030] Optionally, the method further includes: receiving an access request from a second device to the first interface. The second device is a CP device. An interface access interface is displayed to the second device, which includes operation entries corresponding to the first interface.

[0031] Optionally, the method further includes: displaying an application access details page corresponding to the first interface to the second device. The application access details page includes at least one fill-in field. The at least one fill-in field includes the address of the first interface where the second device provides promotional content corresponding to the first service.

[0032] Optionally, the device receives the fill content from the at least one filler item sent by the second device. If the second device verifies and approves the application for the first interface, the device stores the access request data, which includes the address of the first interface.

[0033] In a second aspect, a data processing apparatus is provided for implementing the functions of the first apparatus according to the methods provided in the first aspect and any possible design thereof.

[0034] Optionally, the data processing device may be an operational device or an operational server.

[0035] Thirdly, this application also provides a chip system applied to an electronic device; the chip system may include one or more interface circuits and one or more processors. The interface circuits and processors are interconnected via lines, and the interface circuits are used to receive signals from the electronic device's memory and send the signals to the processors, the signals including computer instructions stored in the memory. When the processor executes the aforementioned computer instructions, the relevant device executes the technical solutions provided in the first aspect and any possible implementation thereof.

[0036] Fourthly, this application also provides a computer-readable storage medium including computer instructions that, when executed on an electronic device, cause the device to perform the technical solutions provided in the first aspect and any possible implementation thereof.

[0037] Fifthly, this application also provides a computer program product that, when run on a computer, causes the computer to execute the technical solutions provided in the first aspect and any possible implementation thereof.

[0038] It is understood that the solutions provided in the second to fifth aspects of this application can be respectively associated with the first aspect and any of its possible designs, and therefore the beneficial effects achieved are similar, which will not be elaborated here. Attached Figure Description

[0039] Figure 1 This is a schematic diagram of an electronic device interface interaction;

[0040] Figure 2 This is a schematic diagram of a communication scenario;

[0041] Figure 3 A schematic diagram of the composition of an operating device provided in an embodiment of this application;

[0042] Figure 4 A schematic diagram illustrating the logical function of an interface configuration module provided in an embodiment of this application;

[0043] Figure 5 A schematic diagram of a page for configuring a new interface provided in an embodiment of this application;

[0044] Figure 6 A schematic diagram of an interface showing a configured interface provided for an embodiment of this application;

[0045] Figure 7 A schematic diagram of an interface access interface provided in an embodiment of this application;

[0046] Figure 8 This application provides a schematic diagram of an application access details page interface.

[0047] Figure 9 A schematic diagram of an interface access management page provided in an embodiment of this application;

[0048] Figure 10 A logical diagram illustrating a multi-interface interaction provided in an embodiment of this application;

[0049] Figure 11 A schematic diagram illustrating an inter-device interaction process provided in an embodiment of this application;

[0050] Figure 12 A schematic diagram illustrating another multi-device interaction process provided in an embodiment of this application;

[0051] Figure 13 A flowchart illustrating a data processing method provided in an embodiment of this application;

[0052] Figure 14 This is a schematic diagram of the composition of a data processing device provided in an embodiment of this application;

[0053] Figure 15 This is a schematic diagram of the composition of a chip system provided in an embodiment of this application. Detailed Implementation

[0054] With the development of electronic devices, the functions that electronic devices can provide to users have become more and more abundant.

[0055] For example, electronic devices can interact with servers in the cloud to push various information, advertisements and other content to users.

[0056] Take mobile phones as an example.

[0057] It's understandable that electronic devices can display different interfaces to users through their screens. Users can switch between different interfaces by swiping left or right on the screen. After an electronic device is unlocked, the default interface is usually the main screen. The main screen can include various display elements, such as icons of applications already installed on the device.

[0058] refer to Figure 1 This provides a schematic diagram of electronic device interface interaction.

[0059] like Figure 1 As shown, the main interface of the electronic device can display icons for applications A1 and A2 that have been installed on the electronic device.

[0060] In some implementations, electronic devices can display pushed content to users through the negative one screen.

[0061] Users can input a left swipe gesture on the main interface to instruct the electronic device to switch to displaying the negative one screen.

[0062] Correspondingly, electronic devices can switch displays such as Figure 1 The negative one screen in the middle.

[0063] In this example, electronic devices can display a variety of different promotional content to users through the negative one screen.

[0064] These different promotional contents can be displayed to users through different business windows, depending on the corresponding business.

[0065] In such Figure 1 In the example, the promotional content displayed on the current negative one screen can be shown to the user through business window 1, business window 2 and business window 3.

[0066] For example, business window 1 can display promotional content for the "Application Suggestions" service. Business window 2 can display promotional content for the "Popular Applications" service. Business serial port 3 can display promotional content for the "Trending Searches" service.

[0067] Different services can correspond to different content providers (CPs). For example, service window 1 corresponds to service 1 and can be used to display promotional content provided by content provider 1. Similarly, service window 2 corresponds to service 2 and can be used to display promotional content provided by content provider 2. And service window 3 corresponds to service 3 and can be used to display promotional content provided by content provider 3.

[0068] In practice, when promotional content is transferred between the content provider's device (e.g., CP device) and the user's electronic device (e.g., mobile phone in the example above), it can be achieved through the corresponding operating device. In this application, the operating device can also be referred to as the first device.

[0069] For example, the operating equipment corresponding to an electronic device may include equipment that provides promotional services for the electronic device. In some implementations, the operating equipment that provides promotional services for the electronic device may belong to the same manufacturer as the electronic device. For example, the operating equipment of brand A can provide promotional services for mobile phones of brand A.

[0070] In other implementations, the operating equipment that provides promotional services for electronic devices may also be contracted with other manufacturers that are different from the electronic device manufacturers.

[0071] As an example, see reference Figure 2 This provides a schematic diagram of a communication scenario.

[0072] Through this Figure 2 The cooperation of various devices in the communication scenario shown enables the push of promotional content from the CP device to the user's electronic device (such as the user device).

[0073] In such Figure 2 In the example, the user equipment can establish a communication connection with the operator equipment. The operator equipment can establish a communication connection with the CP (Content Provider) equipment. This communication connection can be based on a wired or wireless communication connection.

[0074] When a user device wants to receive push content, it can send a corresponding request message to the operator's device. The operator's device can then retrieve the push content from the corresponding content provider (CP) device and transmit it to the user device. This allows the user device to display the received push content. For example, the user device can display something like... Figure 1 The content displayed on the negative one screen is shown.

[0075] In actual implementation, the content and fields to be displayed vary depending on the specific business. The operating equipment can configure corresponding interfaces for different business configurations. This allows the operating equipment to transmit promotional content to the CP equipment based on the interface configuration.

[0076] refer to Figure 1 For example, the types of promotional content that user devices obtain from operational devices can be diverse. Correspondingly, the operational devices need to configure separate data transmission interfaces for different services. This leads to long business development cycles and cumbersome configurations.

[0077] Based on this, embodiments of this application provide a data processing method that enables operating equipment to provide a unified configuration entry point for different services. When a CP device successfully connects to the operating equipment, the operating equipment can use this solution to conveniently manage the successfully connected services.

[0078] For example, refer to Figure 3 This is a schematic diagram of the composition of an operating device provided in an embodiment of this application.

[0079] like Figure 3 As shown in this application, the operating equipment may include a front-end service module and a back-end service module.

[0080] The foreground service module interacts with the user device. It can also retrieve corresponding business data based on business requests sent by the user device. Furthermore, the foreground service module can send the retrieved business data to the user device, enabling the user device to display pushed content based on the data.

[0081] The backend service module supports the various functions of the frontend service module.

[0082] For example, the backend service module can be used to configure and store the interface configurations corresponding to various services. The backend service module can also provide functions such as interface access and interface management.

[0083] like Figure 3 As shown, in some embodiments of this application, the backend service module may include an interface configuration module, an interface access module, an access management module, and a request allocation module.

[0084] like Figure 3 The various software modules can work together to enable the operating equipment to provide a unified interface and configuration for different services, thereby improving the efficiency of service access and service push.

[0085] The following will explain each point separately.

[0086] In this application, the interface configuration module can be used to configure information about one or more interfaces corresponding to different services. These interfaces can then be used for subsequent service access and service push.

[0087] As an example, see reference Figure 4 This provides a schematic diagram of the logical functions of an interface configuration module.

[0088] like Figure 4 As shown, in this application, the interface configuration module can be used to configure signature verification rules, interface information, and interface interface for at least one service. For example, the at least one service may include, for instance, ... Figure 1 The examples shown include application suggestions, popular application services, and trending search services.

[0089] Among them, the signature verification rules can be used to indicate the encryption / decryption configuration of data during the data transmission process of the corresponding business.

[0090] For example, the signature verification rules can correspond to the business logic.

[0091] The interface configuration module can configure the first signature verification rule for the first service. If a second service exists, the interface configuration module can configure the second signature verification rule for that second service.

[0092] In some embodiments, the interface configuration module can configure one or more encryption / decryption configurations for the same service.

[0093] For example, the interface configuration module can configure multiple signature verification rules for the first service. Each signature verification rule corresponds to a signature verification algorithm in the database. In this way, during the subsequent processing of the first service, at least one of the multiple signature verification rules can be selectively used for data transmission.

[0094] The interface configuration module can also be used to configure interface information. In some embodiments, this interface information may also be referred to as upstream call interface information. The upstream may include content providers such as CP servers.

[0095] By configuring this interface information, a standard set of interface content can be configured for services of the same or similar types. This allows the CP server to automatically select the appropriate interface for access based on the current service requirements.

[0096] As an example, the interface information may include at least one of the following:

[0097] Basic information, request headers, request body, and response body. The request headers, request body, and response body can be collectively referred to as request parameters.

[0098] In some embodiments, request header information and request body information can be used to constrain data interaction between user equipment and operating equipment. For example, user equipment can request to the operating equipment to invoke an opened interface through a service invocation request. This service invocation request may include request header information and request body information for the corresponding service.

[0099] In other embodiments, the response body information can be used to constrain data interaction between the CP device and the operating device. For example, the CP device can send CP content data to the operating device based on a CP content acquisition request from the operating device. This CP content data may include various parameters indicated by the response body information.

[0100] The following will explain each point separately.

[0101] In this application, the basic information may also be referred to as interface basic information. This basic information may include at least one of the following: interface name, interface code, interface description, parameter information, etc.

[0102] Each item in the basic information can be associated with a type of business information. For example, the interface name can include: activation page interface, or result page interface, etc. Similarly, the interface code can include activation page, or result page, etc.

[0103] In this way, by configuring the basic information, each business in the corresponding business category can apply for interface access based on the configuration items of the basic information.

[0104] In this example, the request parameters corresponding to the request headers, request body, and response body can be associated with each specific business function.

[0105] The request header and request body information can be used to configure relevant information indicating the corresponding service. The response body information can be used to configure relevant information about the content that the service needs to push.

[0106] For example, the request header information may include multiple configuration items. Each configuration item may correspond to a piece of related information. Any piece of related information may include at least one of the following:

[0107] Parameter name (or simply name), parameter value, whether it is required, example, remarks, description, whether it participates in the signature verification, signature verification order, etc.

[0108] As an example, the request header information may include configuration item 1. The content of configuration item 1 may include parameter name, parameter value, and whether it is required.

[0109] For example, in configuration item 1, the parameter name can be configured as "Content-Type", the parameter value can be configured as "application / json", and whether it is required can be configured as "Yes".

[0110] As another example, the request header information may include configuration item 2. The content of configuration item 2 may include parameter name, parameter value, whether it is required, example, remarks, etc.

[0111] For example, in configuration item 2, the parameter name can be configured as "x-request-nonce", the parameter value can be configured as "request id", whether it is required can be configured as "yes", the example can be configured as "xxx", and the remarks can be configured as "the parameter is not empty, the parameter is not more than 64 characters, and the request is a unique identifier".

[0112] Similar to request headers, request bodies can also include multiple configuration items. Each configuration item can correspond to one piece of related information. Any piece of related information can include at least one of the following:

[0113] Parameter name (or simply name), parameter type (or simply type), required, example, description, whether it participates in signature verification, and signature verification order.

[0114] As an example, the request body information may include configuration item 3. The content of configuration item 3 may include name, type, whether it is required, remarks, etc.

[0115] For example, in configuration item 3, the name can be configured as "cityName", the type can be configured as "string", the required field can be configured as "required", and the remarks can be configured as "city name".

[0116] As another example, the request body information may include configuration item 4. The content of configuration item 4 may include name, type, whether it is required, remarks, etc.

[0117] For example, in configuration item 4, the name can be configured as "isPersonalizedClosed", the type can be configured as "boolean", the required field can be configured as "required", and the remarks can be configured as "whether to enable personalized recommendation service, true can be configured to disable and false can be configured to enable".

[0118] Furthermore, in this example, the response body information may also include multiple configuration items. Each configuration item can correspond to information related to a push notification. Any such related item can include at least one of the following:

[0119] Parameter name, parameter value, parameter type, required, example, description, and remarks.

[0120] As an example, the response body information may include configuration item 5. The content of configuration item 5 may include name, type, whether it is required, remarks, etc.

[0121] For example, in configuration item 5, the name can be configured as "code", the type can be configured as "string", the required field can be configured as "required", and the remarks can be configured as "error code information".

[0122] As another example, the response body information may include configuration item 6. The content of configuration item 6 may include parameter name, parameter value, example, whether it is required, remarks, etc.

[0123] For example, in configuration item 6, the parameter name can be configured as "x-request-nonce", the parameter value can be configured as "request id", whether it is required can be configured as "yes", the example can be configured as "xxx", and the remarks can be configured as "the parameter is not empty, the parameter is not more than 64 characters, and the request is a unique identifier".

[0124] As another example, the response body information may include configuration item 7. The content of configuration item 7 may include parameter name, parameter type, whether it is required, remarks, etc.

[0125] For example, in configuration item 7, the parameter name can be configured as "data", the parameter type can be configured as "object", whether it is required can be configured as "yes", and the remarks can be configured as "the returned response body".

[0126] It should be noted that the above descriptions of the interface information are merely examples and do not constitute a limitation on the functionality of the interface configuration module. In other embodiments, the interface configuration module may also configure more or fewer interface information items for each service.

[0127] Therefore, by configuring the interface information, the interface configuration module can configure the interface information for each service separately. This allows CP devices to populate and send data based on the corresponding interface information when they want to access the operator's equipment to provide push content, achieving rapid interface access and efficient transmission of the content.

[0128] In this embodiment, in addition to configuring the aforementioned information (such as interface information), the interface configuration module can also provide a corresponding visual interface to facilitate operators in performing the above configurations on operational devices. This visual interface can be referred to as the interface interface. In some implementations, the interface configuration module can automatically generate the interface data for this interface interface once the signature verification rules and interface information have been configured.

[0129] For example, refer to Figure 5 This provides a schematic diagram of a page for configuring a new interface.

[0130] In some embodiments, when a new interface configuration needs to be created, the operating device may display the configuration on a display screen within the operating device (or communicatively connected to the operating device). Figure 5 The interface shown is as follows. Therefore, the operating equipment can automatically (or be controlled by the operating personnel) fill in the various configuration items in the basic information and request parameter settings on the interface according to the configuration requirements of the newly created interface.

[0131] like Figure 5 In the example shown, basic information may include name, description, code, etc. Operating devices can flexibly populate the various configuration items in the basic information according to the actual needs of the newly created interface.

[0132] In this example, request parameter settings may include request header information, request body information, and response body information.

[0133] Similar to the configuration of basic information, operational devices can flexibly configure configuration items corresponding to the newly created structure in the request header information, request body information, and response body information.

[0134] like Figure 5 As shown in the example, the request header information can include the content of configuration item 2 above. For example, the parameter name can be configured as "x-request-nonce", the parameter value can be configured as "request id", whether it is required can be configured as "yes", the example can be configured as "xxx", and the remarks can be configured as "parameter is not empty, parameter is not greater than 64 characters, unique identifier of request".

[0135] The request body information can include the content of configuration item 3 above. For example, the name can be configured as "cityName", the type can be configured as "string", the required field can be configured as "required", and the remarks can be configured as "city name".

[0136] The response body information can include the content of configuration item 3 above. For example, the name can be configured as "cityName", the type can be configured as "string", the required field can be configured as "required", and the remarks can be configured as "city name".

[0137] Thus, through such Figure 5 As shown in the interface, operators can configure new interfaces on their devices, either independently or under the control of operators, through a visual interface. This newly created interface configuration can be used by content providers (CPs) to apply for access, and then used to deliver promotional content.

[0138] In some embodiments, such as Figure 5 As shown, the page for creating a new interface configuration may also include a button 501. After completing an interface configuration, users can save the new interface configuration by clicking or enabling this button 501.

[0139] In some embodiments, after saving the configuration of the newly created interface, the operating equipment can also display the configurations of each interface that have been configured through the interface.

[0140] For example, refer to Figure 6 This is a schematic diagram of an interface that displays a configured interface.

[0141] like Figure 6 In the example, the interfaces that have been configured can include interface 1 and interface 2.

[0142] Take interface 1 as an example.

[0143] The display items for this interface 1 may include: the interface name is "Activation Page Interface", the interface code is "Activity page", and the interface description is "After access, it can be displayed on the activation page to increase exposure".

[0144] The entry for Interface 1 may also display key configuration parameters. The "xxx" displayed in this parameter information may include the signature verification rules configured for this activation page interface, interface information, and at least a portion of the content in the interface interface.

[0145] In addition, Figure 6 The example may also include operation function options for interface 1. For instance, if it is necessary to adjust the interface configuration of interface 1, this operation function option can be used to access the interface configuration page of interface 1 (e.g., ...). Figure 5 (As shown on the page). This allows for adjustments and editing of the various configurations for Interface 1.

[0146] exist Figure 6 The example also shows entries for other configured interfaces. For instance, other configured interfaces could include interface 2. Interface 2's interface name is "Result Page Interface," its interface code is "Result page," and its interface description is "After integration, it can be displayed on the results page, increasing exposure." Similar to the entry for interface 1, the entry for interface 2 can also include interface 2's parameter information, operation function options (such as deletion), etc. Further details will not be elaborated further.

[0147] Therefore, through such Figure 6 The interface shown allows the operating equipment to clearly and comprehensively display the configured interfaces and provide convenient access points for various functions of the configured interfaces.

[0148] Figure 6 An example of the configured interface being displayed on the user interface is provided. In this application, the configuration data of the configured interface can be stored by the interface configuration module in a server included in the operating equipment (or connected to the operating equipment for communication). In some implementations, the server of the operating equipment can be configured with a database. For example, the database can be based on MySQL, and / or Oracle, and / or Redis. Taking an operating equipment server including a Redis-based database as an example...

[0149] The interface configuration module can store the configured signature verification rules, interface information, interface interface, and corresponding business identifiers (such as business ID, process ID, etc.) in Redis. This allows the operation equipment to retrieve the corresponding signature verification rules, interface information, and interface interface from Redis when the corresponding CP device requests the configured interface, thereby achieving automated interface access and content delivery.

[0150] The above embodiments provide relevant solutions for configuring interfaces on operating equipment.

[0151] After the interface configuration is complete, the operating equipment can also provide the configured interfaces to the CP equipment, so that the CP equipment can select the corresponding interface from the configured interfaces for access based on the content to be pushed. In some embodiments, the interface information configured for each service can be requested for access by one or more CP devices.

[0152] For example, if a CP device wants to access a configured interface, it can log in to the website corresponding to the operating device and request access to the interface access interface.

[0153] In response, the interface access module of the operating equipment can obtain information about the configured interfaces.

[0154] For example, the interface access module can retrieve information about the interface of the configured interface from the database.

[0155] Therefore, the interface access module can send interface information of the interface access interface to the CP device based on the interface interface. This allows the CP device's display screen to show the configured interfaces based on the received interface access interface information. This process can also be simply referred to as the interface access module displaying the interface access interface to the CP device.

[0156] In some embodiments, the content displayed on the interface access interface shown by the interface access module to the CP device can be similar to, for example... Figure 6 The interface configuration shown is similar.

[0157] In other embodiments, the content displayed on the interface access interface shown by the interface access module to the CP device may not include, for example, Figure 6 The operation function options are included. This prevents the CP device from tampering with the configured interface.

[0158] In other embodiments, the content displayed on the interface access interface shown by the interface access module to the CP device may include the corresponding function operation options of the CP device. This allows the CP device to apply for interface access through the corresponding function operation options.

[0159] As an example, Figure 7 A schematic diagram of an interface access point is provided. Continuing with the example, we will use configured interfaces 1 and 2.

[0160] like Figure 7 As shown, in the interface access interface, the interface access module can display the entries for interface 1 and interface 2 to the CP device. Figure 7 In the example, interface 1 and interface 2 can also display corresponding function operation options. These function operation options can be used by the CP device to trigger interface access.

[0161] For example, the interface access options may include a "Request Access" button. This way, when a CP device needs to access interface 1 or interface 2 to transmit promotional content through the corresponding interface, it can do so through this button. Figure 7 The "Request Access" button on the interface shown requests access permission for the corresponding interface from the operating equipment.

[0162] Taking a CP device wanting to access interface 1 as an example, the CP device can operate the "Request Access" button in the interface 1 entry, either independently or under the control of the CP developer, such as by entering selection or clicking.

[0163] Since this interface access interface can be displayed from the interface access module of the operating equipment to the CP equipment, the interface access module of the operating equipment can obtain the operation information after a button in the interface access interface is operated. For example, the operation information may include: the operation already entered on the CP equipment to indicate that an access request is being made for interface 1.

[0164] Next, the interface access module of the operation or equipment can display the application access details page of interface 1 to the CP device.

[0165] For example, the interface access module can send the interface information of the application access details page of interface 1 to the CP device. Correspondingly, the CP device can switch the display of the application access details page of interface 1 on the display screen.

[0166] As an example, see reference Figure 8 This provides a schematic diagram of the interface for applying for access details.

[0167] In this example, the access request details page may include one or more fields. These fields can be filled in by the CP device. These fields can be stored as basic information for the interface access request.

[0168] For example, the fields to be filled in may include: company name, company description, application description, access time, interface address (url), load test report, etc.

[0169] In other embodiments, the filler items may include more information, such as queries per second (QPS) and response latency, reflecting the communication capabilities of the CP device.

[0170] In this example, the CP device can be based on, for example... Figure 8 The application access details page shown prompts you to enter the basic information for the current interface access request for interface 1.

[0171] For example, the company name can be "Company A," the name of the CP device owner. The company description can be "Company A Travel." The application description can be "Company A applies for access activation page." The access date can be "September 19, 2024." The interface URL can be "http: / / A.com / v1.activepage." The load test report can include "xxx.zip," etc.

[0172] The interface URL can be used to retrieve push content from the address indicated by the interface URL after successful access.

[0173] After completing the input of each field, the CP device can click the submit button on the access request details page. This completes the access request for Interface 1.

[0174] In this embodiment of the application, the interface access module can store the such... Figure 8 Information for the fill-in items on the page shown.

[0175] For example, the interface access module can store CP access information. For instance, the interface access module can store this CP access information in the database of the operating equipment.

[0176] The CP access information may include, for example: Figure 8 At least one of the items shown in the fill-in field. For example, the CP access information may include access time, interface URL, etc. After the CP device's access request is activated, the operator's equipment obtains the corresponding push content based on the CP access information.

[0177] In this example, the CP device submits an interface access application (e.g., by clicking "e.g., ..."). Figure 8 After clicking the submit button (as shown), the interface access module can generate the corresponding access request record. This access request record can be reviewed by the operating equipment, and after the review is approved (or confirmed), the CP device can complete the interface access to interface 1.

[0178] In some embodiments, the access management module of the operating device can be used to review the applied access requests.

[0179] For example, after receiving an access request for interface 1, the access interface module can send the access request information for interface 1 to the access management module.

[0180] Correspondingly, the access management module can review the completed interface access request.

[0181] In some implementations, the access management module can display information such as the access request information for interface 1 on the display screen of the operating equipment. Figure 9 The interface shown is connected to the management page.

[0182] The interface access management page displays completed interface access requests.

[0183] It is understandable that the above example uses the CP device making an interface access request to interface 1 as an example.

[0184] In other embodiments, other CP devices or the same CP device may also make interface access requests to other interfaces (such as interface 2).

[0185] Thus, in this way Figure 9 The interface access management page shown can display one or more interface access requests that have been submitted for review.

[0186] like Figure 9 As shown, the interface access management page displays relevant information for each submitted interface access request.

[0187] The relevant information for this interface access request can be obtained from the access management module based on, for example... Figure 8 The application access details page is generated by the CP device filling in the populated fields.

[0188] For example, such as Figure 9 As shown, when Company A's CP device applies for access to interface 1, the interface access management page can include the interface access request.

[0189] In this example, the interface access request may include the interface name (such as the activation page interface corresponding to interface 1), the application number (such as No. 123), the application description (such as Company A applying for access to the activation page), etc.

[0190] The interface access management page may also include function buttons for managing the applied interfaces.

[0191] For example, such as Figure 9 As shown, the function button may include an "Approve" button and a "Reject" button.

[0192] Taking the example of the operating device determining that an interface access request can be approved, the access management module can automatically or under the control of the operations personnel operate the "Approve" button. Thus, the interface access request for Interface 1 is successful, and the operating device can obtain the push content from the interface URL provided by the CP device based on the access time requested by the CP device. The operating device can then push this content to the user device.

[0193] Taking the example where the operating equipment determines that the interface access request has been rejected, the access management module can automatically or under the control of the operations personnel operate the "Reject" button. Therefore, the interface access request for interface 1 fails. The operating equipment may subsequently refrain from responding to or operating on this interface access request from the CP device for interface 1.

[0194] In some embodiments of this application, the access management module may also have the function of managing approved access requests.

[0195] For example, refer to Figure 10 This provides a logical diagram illustrating multi-interface interaction.

[0196] In such Figure 10 In the example, the access management module can display the approved interfaces in the "Interfaces applying for access" display area.

[0197] In some embodiments, as illustrated in the examples above, after the application for access to the interface has been approved, the operating device can obtain subsequent promotional content and push it to the user device according to the interface to which the corresponding CP device needs to access.

[0198] In other embodiments, such as Figure 10 As shown, the access management module can further manage the access interfaces that have completed the review process.

[0199] For example, such as Figure 10As shown in interface 1001, approved interface access items can include: Company A's application to access the activation page interface, Company B's application to access the activation page interface, and Company C's application to access the activation page interface.

[0200] The access management module can add requested interfaces to the currently invoked interfaces, either automatically or under the control of operations personnel, based on actual needs. This enables flexible management of approved interface access items. For example, after adding an interface access item to the currently invoked interface, that interface access item is enabled, and the operating equipment can perform subsequent operations based on the enabled interface access item. In this application, enabling an interface access item can also be simply referred to as interface enabling.

[0201] For example, refer to Figure 10 In this example, each interface access item can display an "Add" or "Delete" button. For instance, in the interface requesting access, each interface access item can be configured with an "Add" button, allowing users to add the corresponding interface access item to the currently called interface. Similarly, in the currently called interface, each interface access item can be configured with a "Delete" button, allowing users to remove the corresponding interface access item from the currently called interface.

[0202] Taking adding the "Company B applies for access to the activation page interface" interface to the currently called interface as an example, the access management module can, either automatically or under the control of operations personnel, operate the "Add" button corresponding to the "Company B applies for access to the activation page interface" interface. Accordingly, the access management module can add the "Company B applies for access to the activation page interface" interface to the list of currently called interfaces.

[0203] In addition, the access management module can refresh the interface displayed on the screen. For example, switching to display interface 1002. Interface 1002 displays the updated currently called interfaces and the interface access items in the requested access interfaces. It can be seen that the interface access item for "Company B's Request Access Activation Page Interface" has been enabled and added to the list of currently called interfaces.

[0204] In some embodiments, the access management module may also have the function of adjusting the priority order of enabled interface access items. Corresponding to, for example... Figure 10 In the example, in the list of currently called interfaces, the access interface item that appears earlier in the list has higher priority.

[0205] It is understandable that the priority order of different interface access items can correspond to the order in which the content is pushed to the user's device.

[0206] For example, combining Figure 1 Taking the example of Company A and Company B both applying to access the activation page interface of the "Hot Search" service, Company A corresponds to application C1, and Company B corresponds to application C2.

[0207] Thus, after "Company A applies for access to the activation page interface" is enabled, the operation equipment can obtain the push content of application C1 in the trending search service through Company A's CP equipment. The operation equipment can then transmit the push content of application C1 in the trending search service to the user equipment. As a result, the user equipment can display the card corresponding to application C1's trending search in service window 3.

[0208] Similarly, after "Company B applies for access to the activation page interface" is enabled, the operation device can obtain the push content of application C2 in the hot search business through Company B's CP device. The operation device can then transmit the push content of application C2 in the hot search business to the user device. As a result, the user device can display the card corresponding to the hot search of application C2 in business window 3.

[0209] In such Figure 1 In the example, the card corresponding to the trending search of application C1 is displayed before the card corresponding to the trending search of application C2. This corresponds to the fact that the access interface item "Company A applies for access to the activation page interface" has a higher priority than "Company B applies for access to the activation page interface". In other words, under the same business, the higher the priority of the access interface item, the earlier it is displayed on the user's device, and the higher the probability of exposure.

[0210] Continue to refer to Figure 10 In such Figure 10 In the example, the access management module may have the ability to adjust the priority of the enabled access interface items in the currently invoked interface.

[0211] For example, let's take the example of adjusting the priority of "Company B applying for access to the activation page interface" to be higher than that of "Company A applying for access to the activation page interface".

[0212] In interface 1002, the operating device can, either automatically or under the control of the operating personnel, drag the access interface item "Company B applies for access to the activation page interface" onto the access interface item "Company A applies for access to the activation page interface". This allows for the adjustment of the priority of the access interface item "Company B applies for access to the activation page interface".

[0213] Correspondingly, the access management module can switch to display interface 1003 after the priority is adjusted. In interface 1003, the currently called interfaces can be displayed from top to bottom in order of priority, based on the updated access interface items.

[0214] For example, in interface 1003, in the list of currently called interfaces, the access interface item for "Company B applying for access activation page interface" can be located above the access interface item for "Company A applying for access activation page interface".

[0215] In this way, after the operating device pushes the promotional content of "Company A applies for access to the activation page interface" and "Company B applies for access to the activation page interface" to the user's device, the card corresponding to the hot search of application C2 can be displayed before the card corresponding to the hot search of application C1 on the user's device.

[0216] Based on the above implementation descriptions, in this embodiment of the application, after the operating equipment configures the interface information for each service through the interface configuration module, it only needs to perform a single operation to review the interface access request sent by the CP device to complete the processing of an interface access request. Furthermore, the operating equipment can conveniently and quickly manage the reviewed interface access items through the access management module.

[0217] In this application, the operating equipment can also use a request allocation module to perform subsequent processing on the already opened access interface items, so as to obtain push content from the corresponding CP device and transmit the push content to the user equipment, so that the user equipment can display the received information.

[0218] As explained above, after completing the interface configuration for the service, the CP device can apply for access to the required interfaces. If the application is approved, the interface information for that service, as well as the CP access information, can be stored in the operator's database.

[0219] The interface information can be information about the interface configured for this service in the operating equipment. For example, the interface information may include at least one of the following: basic information, request header information, request body information, and response body information.

[0220] CP access information may include information entered by the CP device when requesting access. (Reference) Figure 8 As explained in the description, in some embodiments, the CP access information may include at least one of the following: enterprise name (i.e., the name of the enterprise to which the CP device belongs), enterprise description, application description, access time, interface URL, stress test report, etc.

[0221] In this application, the request allocation module in the operating equipment can have the ability to read information stored in the database. That is, when one or more services have been configured, applied for access, and approved, the request allocation module can obtain the interface information and CP access information of the one or more services from the database.

[0222] In some implementations, the database can be integrated into the request allocation module. In other implementations, the request allocation module can read the data from the database via inter-module data transmission lines within the operating equipment.

[0223] The following explanation uses the database integrated into the request allocation module as an example. That is, the request allocation module can store interface information and CP access information for one or more services that have been configured, applied for access, and approved.

[0224] For example, refer to Figure 11 This is a schematic diagram illustrating an inter-device interaction process provided in an embodiment of this application. Based on this... Figure 11 Once the solution shown is implemented, the operating equipment can work with the user equipment and the CP equipment to push promotional content to the user equipment.

[0225] like Figure 11 As shown, the solution may include:

[0226] S1101. Configure, access, and verify the interfaces of the back-end service module for operating equipment.

[0227] For example, the interface configuration module, interface access module, and interface management module in the backend service module of the operating equipment can cooperate with each other, according to... Figures 4 to 10 The provided solution enables interface configuration, interface access, and review and confirmation for one or more business processes.

[0228] As an example, the backend service module can configure interfaces for the first service. The first CP device corresponding to the first service can apply to access the first interface of the first service. The operation equipment can review the access request for the first interface. If the review is confirmed, the first interface enters the interface enabled state. Thus, when a user device needs to push and display the first service, it can obtain the corresponding content data through the enabled first interface.

[0229] Corresponding to, for example Figure 1 For example, the first business could be application suggestions, popular applications, trending searches, etc.

[0230] Taking the first business as an example, we can provide an application suggestion.

[0231] The first CP device can be the CP device corresponding to any one of the applications A1, A2, A3, or A4.

[0232] Based on the foregoing explanation, when the first interface is enabled, the request distribution module in the backend service module can store the interface information and CP access information corresponding to the first interface. It can be understood that the first interface corresponds to the first service. Thus, when the first service needs to be used, the operating device can obtain various data corresponding to the first service (such as promotional content data) through the first interface.

[0233] S1102, The front-end service module of the operating equipment receives service call requests from user equipment.

[0234] For example, the service invocation request may indicate a call to a first service. In some implementations, the service invocation request may include parameters (such as required parameters) indicated by the request header information and / or request body information corresponding to the first service.

[0235] In some embodiments, the service call request may carry the service ID of the first service and / or the interface ID of the first interface. It is understood that on the user's device, the first application corresponding to the first service can be installed and run, thereby providing the user with the functionality of the first service.

[0236] For example, taking the first business as... Figure 1 The example shown illustrates an application recommendation. The user's device can install and run the application corresponding to the recommended application. Therefore, through this application, the system controls the user's device to provide application recommendations to the user. In some implementations, the application corresponding to the recommended application can be an app store or similar application.

[0237] Thus, in some implementations, the first business ID and / or the interface ID of the first interface may include the application ID of the first application, such as the AppID of the first application.

[0238] In other embodiments, the business call request may also include other content. For example, the business call request may include a timestamp corresponding to the business request.

[0239] In this example, the user equipment can generate and send the service call request based on the user's operation. For example, the user equipment can receive a user's action such as... Figure 1 When the user inputs a leftward swipe gesture on the main interface, a service call request is generated and sent. Similarly, when the user device inputs a preset command to display promotional content, a service call request is generated and sent.

[0240] Therefore, the front-end service module can determine which first interface needs to be called based on the business ID of the first business and / or the interface ID of the first interface.

[0241] In the following example, a business call request carries the business ID of the first business, which includes the AppID of the first application.

[0242] S1103. The front-end service module sends a verification information acquisition request to the request allocation module, and the request allocation module sends verification information to the front-end service module. In this example, the verification information can be used by the front-end service module to determine whether the interface corresponding to the first service is available.

[0243] For example, the verification information may include at least one of the following:

[0244] The signature verification rules for the first interface, the basic information for the first interface, the request header information for the first interface, and the request body information for the first interface.

[0245] In some implementations, the front-end service module can send the identifier corresponding to the first interface / first service to the request allocation module in the verification information acquisition request. For example, the verification information acquisition request may include the AppID corresponding to the first application.

[0246] Based on the foregoing explanation, the request allocation module can obtain information about interfaces that have been applied for and approved. In this way, the request allocation module can determine the verification information corresponding to the first service based on the AppID of the received first application. The request allocation module can also send the verification information corresponding to the first service to the front-end service module.

[0247] S1104, Front-end service module verification information has passed.

[0248] In this example, the front-end service module can verify the authentication information corresponding to the first received service request. Therefore, if the authentication information passes verification, it indicates that the received service call request is valid and available.

[0249] In some implementations, the front-end service module can process the verification information according to the verification rules configured for the first business. If the verification is successful, the verification information is considered validated.

[0250] In other implementations, the front-end service module can perform basic information and / or request header and / or request body mandatory field validation on the verification information based on the interface information configured for the first service. If all mandatory fields indicated by the interface information corresponding to the first service in the verification information are not empty, the verification information is deemed to have passed.

[0251] In other implementations, the front-end service module can perform signature verification and mandatory field validation on the verification information. If the signature verification is successful and / or all mandatory fields are not empty, the verification information is deemed to have passed.

[0252] In this example, we take the successful verification of the verification information for the first service as an example.

[0253] S1105. The front-end service module sends a CP access information acquisition request to the request allocation module. The request allocation module sends CP access information to the front-end service module.

[0254] In this example, the front-end service module can determine that it can obtain the corresponding content data from the CP device if the verification information passes.

[0255] For example, the front-end service module can use S1105 to obtain information such as the interface URL of the CP device that has applied for the first service from the request allocation module.

[0256] In some implementations, the front-end service module can include the AppID of the first application in the CP access information acquisition request. Correspondingly, the request allocation module can use the AppID of the first application to send back the corresponding CP access information to the front-end service module. This CP access information may include information such as the interface URL sent by the CP device corresponding to the first application when requesting access to the first interface.

[0257] S1106. The front-end service module sends a CP content acquisition request to the CP device. The CP device sends CP content data to the front-end service module.

[0258] For example, the front-end service module can determine the address of the CP device corresponding to the first application that provides promotional content based on the address indicated by the obtained interface URL. In this way, the front-end service module can obtain the promotional content corresponding to the first service from that address.

[0259] In some implementations, the CP content data may include parameters indicated by the response body information corresponding to the first service.

[0260] S1107, Front-end service module confirms CP content data verification passed.

[0261] In this example, the front-end service module can verify the received CP content data.

[0262] It is understandable that CP content data can include the response body corresponding to the promotional content. In this way, the front-end service module can verify the CP content data based on the response body information configured for the first business (first interface).

[0263] For example, the front-end service module can perform mandatory field validation on the required fields in the CP content data.

[0264] The following example uses the case where the CP content data verification passes.

[0265] S1108, The front-end service module sends business data to the user equipment.

[0266] For example, the business data may include response information corresponding to the business call request. For instance, the business data may include content provider (CP) data.

[0267] In some implementations, the front-end service module can perform format conversion, content filtering, and other processing on the CP content data before sending it, based on the user device's requirements for displaying the promotional content, and then obtain business data to send to the user device.

[0268] In this way, the user equipment can display the interface based on the received service data. For example, the user equipment can... Figure 1 The negative one screen shows the business window corresponding to the first business.

[0269] It is understandable that, such as Figure 11 In the implementation of the scheme shown, the user equipment can obtain the promotional content corresponding to the first service through the operation equipment by sending a service call request.

[0270] Combination Figure 1 For example, in some cases, the first interface of the first service can be applied for and approved by multiple CP devices. In this application, the user equipment can simultaneously obtain more promotional content from these multiple CP devices by sending a single service call request.

[0271] For example, in combination Figure 1 Taking the first service as an application suggestion as an example, the CP devices applying for the first interface can include: the CP device corresponding to application A1, the CP device corresponding to application A2, the CP device corresponding to application A3, the CP device corresponding to application A4, etc. In this way, the user device can send a single service call request to simultaneously obtain more promotional content from the CP devices corresponding to application A1, application A2, application A3, and application A4.

[0272] As an example, combined Figure 11 ,refer to Figure 12 This provides yet another flowchart illustrating multi-device interaction. In this... Figure 12 The example shown assumes that the CP devices applying for the first interface include a first CP device and a second CP device, and that both applications have been reviewed and confirmed.

[0273] like Figure 12 As shown, the solution may include:

[0274] S1201. Configure, access, and verify the interfaces of the back-end service module for operating equipment.

[0275] For example, the processing of S1201 can be referred to as follows: Figure 11 S1101 in the middle.

[0276] In this example, the backend service module can configure the interface for the first service. The backend service module can also receive access requests from both the first CP device and the second CP device for the first interface of the first service. This is illustrated by the example where the access requests from the operating device to both the first CP device and the second CP device are reviewed and confirmed.

[0277] S1202, The front-end service module of the operating equipment receives service call requests from user equipment.

[0278] For example, the processing of S1202 can be referred to as follows: Figure 11 S1102 in the middle.

[0279] In some embodiments, a service call request may correspond to a first service. Through this service call request, the user equipment can request promotional content corresponding to the first service from the operating equipment.

[0280] S1203, The front-end service module sends a verification information acquisition request to the request distribution module, and the request distribution module sends verification information to the front-end service module.

[0281] S1204, Front-end service module verification information has passed.

[0282] For example, the processing of S1203-S1204 can be referred to as follows: Figure 11 S1103-S1104 in the middle.

[0283] S1205. The front-end service module sends a CP access information acquisition request to the request allocation module. The request allocation module sends CP access information to the front-end service module.

[0284] For example, the processing of S1205 can be referred to as follows: Figure 11 S1105 in the middle.

[0285] In this example, both the first CP device and the second CP device have initiated access requests to the first interface. Therefore, the request allocation module can send the CP access information of the first CP device and the CP access information of the second CP device to the front-end service module, respectively.

[0286] The CP access information of the first CP device may include information such as the interface URL for the first CP device to provide promotional content.

[0287] The CP access information of the second CP device may include information such as the interface URL for the second CP device to provide promotional content.

[0288] S1206a, The front-end service module sends a CP content acquisition request 1 to the first CP device. The first CP device sends CP content data 1 to the front-end service module.

[0289] S1206b: The front-end service module sends a CP content acquisition request 2 to the second CP device. The second CP device sends CP content data 2 to the front-end service module.

[0290] For example, the front-end service module can send CP content retrieval requests to each CP device that has already enabled access requests to the first interface.

[0291] For example, the front-end service module can send a CP content retrieval request 1 to the first CP device based on the interface URL corresponding to the first CP device.

[0292] For example, the front-end service module can send a CP content retrieval request to the second CP device based on the interface URL corresponding to the second CP device.

[0293] Correspondingly, each CP device can send CP content data back to the front-end service module based on the received CP content acquisition request.

[0294] For example, the first CP device can send CP content data 1 to the front-end service module.

[0295] For example, the second CP device can send CP content data 2 to the front-end service module.

[0296] S1207, Front-end service module confirms CP content data verification passed.

[0297] Similar to the description in S1107, the front-end service module can verify the received CP content data according to the response body information corresponding to the first service / first interface.

[0298] Content that passes verification can be transmitted to the user's device for display. Conversely, content that fails verification can be discarded or not transmitted to the user's device, preventing the display of promotional content with missing information or other anomalies.

[0299] In some implementations, the processes described in S1206a, S1206b, and S1207 can be executed in parallel, thereby improving the efficiency of CP content acquisition.

[0300] S1208, The front-end service module performs CP content data aggregation processing.

[0301] In this example, the front-end service module can aggregate content from multiple content providers (CPs). This allows the front-end service module to deliver promotional content from multiple CPs to the user device with a single data transmission, thus avoiding the communication overhead of multiple data transmissions.

[0302] S1209, The front-end service module sends business data to the user equipment.

[0303] For example, the business data may include data obtained after aggregating multiple content providers (CPs).

[0304] For example, the business data may include CP content data 1 corresponding to the first CP device and CP content data 2 corresponding to the second CP device, etc.

[0305] Thus, through such Figure 12 The provided solution allows user equipment to send a single service call request to obtain content data from multiple content providers (CPs) corresponding to the first service.

[0306] The above Figure 11 as well as Figure 12 In the provided solution implementation, the processing procedure executed by the operating device in the embodiments of this application is described from the perspective of multi-device interaction.

[0307] refer to Figure 13 This provides a flowchart illustrating a data processing method. Figure 13 The provided solution illustrates the process of acquiring content providers (CPs) from the perspective of operational equipment.

[0308] In this example, the operating device can trigger the execution of S1301 after receiving a service call request for the first service. The request header of the service call request may include information such as the appid and timestamp corresponding to the first service.

[0309] Understandably, in some situations, user devices may need to invoke multiple services simultaneously (such as...). Figure 1 When displaying application suggestions, popular apps, trending searches, etc., a business call request is sent to obtain the push content for each business. This business call request can include information such as the appid corresponding to each business.

[0310] S1301. Determine whether the upstream interface of the first service is enabled.

[0311] For example, if the state of the first interface corresponding to the first service is enabled, then the upstream interface of the first service is enabled.

[0312] For example, if the first interface is requested to be accessed by at least one CP device (such as the first CP device, the second CP device, etc.) and the request is verified, the first interface is in the "open" state.

[0313] Correspondingly, if the status of the first interface corresponding to the first service is not enabled, then the upstream interface of the first service is not enabled.

[0314] For example, if the first interface is not configured and saved; or if the interface information of the first interface has been configured but no CP device has applied for access; or if the interface information of the first interface has been configured and at least one CP device has applied for access but the review has not been confirmed, the status of the first interface is "not enabled".

[0315] If the upstream interface of the first service is enabled, execute S1302. Otherwise, the process ends.

[0316] In some embodiments, the upstream interface status can be determined based on cached data from a database (such as Redis).

[0317] S1302. Query the AppID and appSecret corresponding to the first service based on the AppID. The appSecret configuration is used to indicate that at least one permission of the corresponding application is enabled. For example, if application 1 (corresponding to AppID 1) has configured an appSecret, it indicates that read and write permissions of the service corresponding to application 1 are enabled.

[0318] The operating device can query the database to see if the AppID and its corresponding appSecret exist, based on the AppID in the request header of the business call request. If the AppID and its corresponding appSecret exist, it indicates that the application's business can proceed with further processing, and S1303 is executed. Conversely, if the AppID or appSecret does not exist, it indicates that the first business does not have the permission for further processing, and the process ends.

[0319] S1303, Sign the appid and timeStamp fields in the request header.

[0320] For example, the operating device encrypts (i.e., signs) the appid and timestamp in the request header of the business call request according to the signature verification rules corresponding to the first interface. For ease of explanation, the data obtained through this encryption is taken as the signature verification data.

[0321] S1304. Compare whether the Sign field and the signed data are consistent.

[0322] For example, the Sign field can be a field pre-configured in the operating device, where the appid and timestamp of the first interface are encrypted according to the signature verification rules of the first interface. The Sign field can also be called the first reference field.

[0323] In this way, the operating equipment can determine whether the signature verification rule used in the business call request is consistent with the signature verification rule corresponding to the first interface (i.e., the first business) by comparing the signature verification data and the sign field.

[0324] If the Sign field and the signed data are consistent, the signature verification rule is successful, and S1305 is executed.

[0325] Conversely, if the Sign field and the signed data are inconsistent, the signature verification rule will fail and the process will end.

[0326] In some embodiments, the operating equipment may implement S1302-S1304 through slicing technology.

[0327] S1305. Query the real-time sub-interface information of the associated activation status through the activation page interface code.

[0328] In this example, real-time sub-interface information may include one or more. Each real-time sub-interface information corresponds to an access request that is in an open state.

[0329] Understandably, each service can be configured with an activation page. And the same service can be applied for by multiple service providers (CPs).

[0330] Thus, when a CP device (e.g., the first CP device) requests the first service and the access request is approved, the activation page interface can link to a sub-interface (e.g., the first sub-interface). This first sub-interface can point to the approved access request from the first CP device. In other words, through this sub-interface, one can query the access request sent by the first CP device and its corresponding content, such as CP access information.

[0331] Correspondingly, if another CP device (such as a second CP device) applies for the first service and the access application is approved, then the activation page interface can link to another sub-interface (such as a second sub-interface). This second sub-interface can point to the approved access application of the second CP device.

[0332] In combination with the above regarding Figure 10Regarding the management of verified interfaces, in this example, if the access request corresponding to the first sub-interface is in an open state (e.g., it has been added to the currently called interface), then the corresponding first sub-interface is in an open state. Conversely, if the access request corresponding to the first sub-interface is in a closed state (e.g., it has not been added to the currently called interface), then the corresponding first sub-interface is in a closed state.

[0333] In this example, if the real-time sub-interface associated with the activation status of the activation page interface encoding query is not empty, then S1306 is executed.

[0334] Correspondingly, if the real-time sub-interface associated with the activation status of the activation page interface code query is empty, the process ends.

[0335] S1306. Obtain the request header and request body information of the sub-interface.

[0336] Taking a sub-interface of the first service as an example, the operating equipment can determine the request header and request body information of the first service based on the interface information of the first service. The request header and / or request body information of the first service may include one or more required fields.

[0337] The operating equipment can obtain the request header and request body information of each of the enabled real-time sub-interfaces.

[0338] S1307. Determine whether the business call request includes required fields indicating request header information and request body information.

[0339] For example, take the first business as an example.

[0340] The operating equipment can determine whether a business call request includes the required fields indicated by the request header and request body information based on the request header and request body information corresponding to the first business in the business call request.

[0341] If all required fields are included, then step S1308 is executed. Otherwise, the mandatory field validation fails, and the process ends.

[0342] Thus, it is possible to achieve such Figure 11 or Figure 12 The verification information shown is validated.

[0343] S1308. Assemble the request header and request body, obtain and send the CP content retrieval request.

[0344] S1309, Obtain CP content data.

[0345] S1310. Determine whether the returned data of each sub-interface includes the required fields indicated by the response body information. If it does, proceed to S1311; otherwise, end the process.

[0346] S1311. Assemble the data from each sub-interface, obtain and send the aggregated CP data.

[0347] For example, the processing of S1308-S1311 can be referred to as follows: Figure 12 S1206a-S1209. Further details will not be provided.

[0348] Thus, through such Figure 13 The solution shown enables the operating equipment to quickly and accurately provide the required business data to the user equipment after receiving a business call request.

[0349] It is understood that the various devices (such as operating devices) provided in the embodiments of this application include corresponding hardware structures and / or software modules for performing the above functions in order to achieve the aforementioned functions. Those skilled in the art should readily recognize that, in conjunction with the units and algorithm steps of the various examples described in the embodiments disclosed herein, the embodiments of this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the embodiments of this application.

[0350] This application embodiment can divide the operating equipment into functional modules according to the above method example. For example, each function can be divided into a separate functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0351] The foregoing mainly describes the solutions provided by the embodiments of this application from the perspective of various functional modules. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0352] The integrated modules described above can be implemented in hardware or as software functional modules. It should be noted that the module division in this embodiment is illustrative and represents only one logical functional division; in actual implementation, other division methods may be used.

[0353] For example, Figure 14 A schematic diagram of the composition of a data processing device 1400 is shown. (As shown) Figure 14 As shown, the data processing device 1400 may include a processor 1401 and a memory 1402. The memory 1402 is used to store computer execution instructions. Exemplarily, in some embodiments, when the processor 1401 executes the instructions stored in the memory 1402, the data processing device 1400 may perform any of the methods shown in the above embodiments. In some implementations, the data processing device 1400 may be configured as a server or a cloud server. The data processing device 1400 may be the aforementioned operating device.

[0354] It should be noted that all relevant content of each step involved in the above method embodiments can be referenced from the functional description of the corresponding functional module, and will not be repeated here.

[0355] Figure 15 A schematic diagram of a chip system 1500 is shown. The chip system 1500 may include a processor 1501 and a communication interface 1502, used to support related devices (such as operating equipment) in implementing the functions involved in the above embodiments. In one possible design, the chip system also includes a memory for storing necessary program instructions and data for the electronic device. The chip system may be composed of chips or may include chips and other discrete devices. It should be noted that in some implementations of this application, the communication interface 1502 may also be referred to as an interface circuit.

[0356] It should be noted that all relevant content of each step involved in the above method embodiments can be referenced from the functional description of the corresponding functional module, and will not be repeated here.

[0357] In the embodiments of this application, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of this embodiment, unless otherwise stated, "multiple" means two or more.

[0358] The functions, actions, operations, or steps in the above embodiments can be implemented, in whole or in part, by software, hardware, firmware, or any combination thereof. When implemented using software programs, they can be implemented, in whole or in part, in the form of a computer program product. This computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or include one or more data storage devices such as servers and data centers that can be integrated with the medium. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state disks, SSDs), etc.

[0359] Although this application has been described in conjunction with specific features and embodiments, it is obvious that various modifications and combinations can be made thereto without departing from the spirit and scope of this application. Accordingly, this specification and drawings are merely exemplary illustrations of this application as defined by the appended claims, and are considered to cover any and all modifications, variations, combinations, or equivalents within the scope of this application. Clearly, those skilled in the art can make various alterations and modifications to this application without departing from the spirit and scope of this application. Thus, if such modifications and modifications of this application fall within the scope of the claims of this application and their equivalents, this application is also intended to include such modifications and modifications.

Claims

1. A data processing method, characterized in that, The method is applied to a first device, which is used to provide promotional content to a user device; the method includes: Receive a business call request, the business call request being used to obtain promotional content corresponding to the first business; Obtain the first verification information corresponding to the first service. The first verification information is used to determine whether the first interface is available. The first interface is the interface corresponding to the first service. If the first verification information indicates that the first interface is available, first content data is obtained, and the first content data includes promotional content corresponding to the first service. The first service data is sent to the user equipment, and the first service data corresponds to the first content data.

2. The method of claim 1, wherein, The first device stores first configuration information corresponding to the first interface; the first configuration information includes request header information and / or request body information. Before obtaining the first verification information corresponding to the first service, the method further includes: Obtain the first configuration information; Based on the service call request and the first configuration information, the service call request is determined to be valid.

3. The method of claim 2, wherein, The first configuration information includes at least one required field. Determining that the service call request is valid includes: It is determined that in the business call request, none of the required fields indicated by the first configuration information are empty.

4. The method according to any one of claims 1 to 3, characterized in that, The first verification information includes at least one of the following: The signature verification rules corresponding to the first interface, the basic information corresponding to the first interface, the request header information corresponding to the first interface, and the request body information corresponding to the first interface.

5. The method of claim 4, wherein, The first verification information includes the signature verification rules corresponding to the first interface, and the signature verification rules indicate the data encryption / decryption method corresponding to the first service; The first verification information indicates that the first interface is available, including: The signature verification rule for the service call request is consistent with the first signature verification rule, which is the signature verification rule corresponding to the first service.

6. The method of claim 5, wherein, The first device has a preset first reference field; the first reference field includes data encrypted according to the first signature verification rule; The first parameter is a parameter that needs to be carried in the preset business call request; The method further includes: Obtain the first parameter from the business call request; According to the first signature verification rule, the first parameter is encrypted to obtain the first signature verification data; Based on the consistency between the first signature verification data and the first reference field, it is determined that the signature verification rule for the business call request is consistent with the first signature verification rule.

7. The method according to claim 6, characterized in that, The first parameter includes: the first application identifier AppID corresponding to the first service, and / or the timestamp corresponding to the first service.

8. The method according to any one of claims 1-7, characterized in that, Before acquiring the first content data, the method further includes: It is determined that a first sub-interface exists, which corresponds to a valid interface application. The interface application is an access request for the first interface, and different interface applications correspond to different content provider (CP) devices.

9. The method according to claim 8, characterized in that, The first sub-interface corresponds to the second device, which is a CP device; Before acquiring the first content data, the method further includes: Receive an access request from the second device, the access request being used to request access to the first interface; The access request data is stored; the access request data includes a first interface address URL, the address indicated by the first interface URL storing first data provided by the second device corresponding to the first service; The step of obtaining the first content data includes: The first content data is obtained from the first URL indicated by the first sub-interface; the first content data includes the first data provided by the second device.

10. The method according to claim 8 or 9, characterized in that, Before sending the first service data to the user equipment, the method further includes: It is determined that a second sub-interface exists, and the second sub-interface corresponds to a valid interface application, which is an access request for the first interface; the second sub-interface corresponds to a third device; the third device is a CP device; Obtain second content data from the third device; The first business data is generated based on the first content data and the second content data.

11. The method according to any one of claims 1-10, characterized in that, The first device stores second configuration information corresponding to the first interface; the second configuration information includes response body information. After acquiring the first content data, the method further includes: Obtain the second configuration information corresponding to the first interface; Based on the first content data and the second configuration information, the first content data is determined to be valid.

12. The method of claim 11, wherein, The second configuration information includes at least one required field. Determining the validity of the first content data includes: It is determined that in the first content data, none of the required fields indicated by the second configuration information are empty.

13. The method according to any one of claims 1-12, characterized in that, Before receiving a business invocation request, the method further includes: Configure at least one of the following information for the first interface: Verification rules, request header information, request body information, response body information.

14. The method of claim 13, wherein, The method further includes: Receive an access request from a second device to the first interface; the second device is a CP device; The interface access interface is displayed to the second device, and the interface access interface includes operation items corresponding to the first interface.

15. The method according to claim 14, characterized in that, The method further includes: The second device is shown an access request details page corresponding to the first interface; the access request details page includes at least one fill-in item. The at least one fill-in item includes the first interface address of the promotional content corresponding to the first service provided by the second device.

16. The method according to claim 15, characterized in that, Receive the fill content from the at least one fill item sent by the second device; If the second device approves and confirms the application for the first interface, it stores the access request data of the second device, which includes the address of the first interface.

17. A data processing device, characterized by The device is used to implement the function of the first device according to the method of any one of claims 1-16.

18. The apparatus of claim 17, wherein, The data processing equipment is an operating device or an operating server.

19. A chip system, characterized by The chip system is applied to an electronic device; the chip system includes one or more interface circuits and one or more processors; the interface circuits and the processors are interconnected via lines; the interface circuits are used to receive signals from the memory of the electronic device and send the signals to the processors, the signals including computer instructions stored in the memory; when the processor executes the computer instructions, the electronic device performs the method as described in any one of claims 1-16.

Images