Linkage parameter configuration method and device, computer equipment and storage medium

Abstract

The invention relates to the technical field of computers, and discloses a linkage parameter configuration method and device, computer equipment and a storage medium. The target linkage parameter comprises a first linkage parameter which is expected to be executed by the target content distribution network locally and / or a second linkage parameter which is expected to be executed locally by the target content distribution network; writing the target linkage parameter into header information of the hypertext transfer protocol request to obtain a target hypertext transfer protocol request; and sending the target hypertext transfer protocol request to the target content distribution network, so that the target content distribution network generates a first execution strategy based on the target linkage parameter.

Description

Technical Field

[0001] The present disclosure relates to the field of computer technology, and in particular to a method, an apparatus, a computer device and a storage medium for configuring linkage parameters. Background Art

[0002] In some application scenarios, end-cloud linkage is involved. For example, if you want to ensure the performance of live broadcast on the link between the edge node of the content delivery network (CDN) on the server side and the terminal player, you need strong coordination and optimization between the terminal player and the CDN edge node. Only by combining the status information of both parties and optimizing the decision can you approach the optimal solution. Therefore, a linkage mechanism between the terminal player and the CDN edge node is needed. Among them, the most important thing about this linkage mechanism is the configuration of the linkage parameters. Summary of the invention

[0003] In view of this, the present disclosure provides a method, apparatus, computer device and storage medium for configuring linkage parameters to solve the problem of configuring terminal-cloud linkage parameters.

[0004] In a first aspect, the present disclosure provides a method for configuring linkage parameters, the method comprising:

[0005] Acquire target linkage parameters, where the target linkage parameters include first linkage parameters that the local expects the target content distribution network to execute and / or second linkage parameters that the target content distribution network expects the local to execute;

[0006] Writing the target linkage parameter into the header information of a hypertext transfer protocol request to obtain a target hypertext transfer protocol request;

[0007] The target hypertext transfer protocol request is sent to the target content distribution network, so that the target content distribution network generates a first execution strategy based on the target linkage parameter.

[0008] In a second aspect, the present disclosure provides a method for configuring linkage parameters, the method comprising:

[0009] Receiving a target hypertext transfer protocol request, wherein header information of the target hypertext transfer protocol request includes a target linkage parameter, wherein the target linkage parameter includes a first linkage parameter that the client expects to be executed locally and / or a second linkage parameter that the local expects the client to execute;

[0010] Parsing the target hypertext transfer protocol request to obtain the target linkage parameter;

[0011] The first execution strategy is generated based on the target linkage parameter.

[0012] In a third aspect, the present disclosure provides a device for configuring linkage parameters, the device comprising:

[0013] A target linkage parameter acquisition module, used to acquire target linkage parameters, wherein the target linkage parameters include a first linkage parameter that the local expects the target content distribution network to execute and / or a second linkage parameter that the target content distribution network expects the local to execute;

[0014] A target linkage parameter writing module, used for writing the target linkage parameter into the header information of the hypertext transfer protocol request to obtain a target hypertext transfer protocol request;

[0015] The target hypertext transfer protocol request sending module is used to send the target hypertext transfer protocol request to the target content distribution network, so that the target content distribution network generates a first execution strategy based on the target linkage parameter.

[0016] In a fourth aspect, the present disclosure provides a device for configuring linkage parameters, the device comprising:

[0017] A target hypertext transfer protocol request receiving module, used to receive a target hypertext transfer protocol request, wherein the header information of the target hypertext transfer protocol request includes a target linkage parameter, wherein the target linkage parameter includes a first linkage parameter that the client expects to execute locally and / or a second linkage parameter that the local expects the client to execute;

[0018] A target hypertext transfer protocol request parsing module, used for parsing the target hypertext transfer protocol request to obtain the target linkage parameter;

[0019] The first execution strategy generating module is used to generate the first execution strategy based on the target linkage parameter.

[0020] In a fifth aspect, the present disclosure provides a computer device, comprising: a memory and a processor, the memory and the processor are communicatively connected to each other, computer instructions are stored in the memory, and the processor executes the method for configuring linkage parameters of the above-mentioned first aspect or any corresponding embodiment thereof by executing the computer instructions.

[0021] In a sixth aspect, the present disclosure provides a computer-readable storage medium having computer instructions stored thereon, the computer instructions being used to enable a computer to execute the method for configuring linkage parameters of the first aspect or any corresponding embodiment thereof.

[0022] The method for configuring linkage parameters provided by the embodiment of the present disclosure includes, in the target linkage parameters, a first linkage parameter that the client expects the target CDN to execute and / or a second linkage parameter that the target CDN expects the client to execute, and the linkage between the client device and the target CDN is achieved through the configuration of the first linkage parameter and the second linkage parameter. Since there is no constraint on the length of the data carried in the header information of the Hypertext Transfer Protocol (http) request, multiple linkage parameters can be configured according to demand, that is, through the configuration of the end-cloud linkage parameters, the client and the target CDN can both communicate data according to the expected demand of the other end, thereby ensuring the coordinated linkage between the end and the cloud. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] In order to more clearly illustrate the specific embodiments of the present disclosure or the technical solutions in the prior art, the drawings required for use in the specific embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0024] Figure 1 is a flowchart of a method for configuring linkage parameters according to an embodiment of the present disclosure;

[0025] Figure 2 is a flowchart of another method for configuring linkage parameters according to an embodiment of the present disclosure;

[0026] Figure 3 is a flowchart of another method for configuring linkage parameters according to an embodiment of the present disclosure;

[0027] Figure 4 is a structural block diagram of a device for configuring linkage parameters according to an embodiment of the present disclosure;

[0028] Figure 5 is a structural block diagram of another linkage parameter configuration device according to an embodiment of the present disclosure;

[0029] Figure 6 It is a schematic diagram of the hardware structure of the computer device of the embodiment of the present disclosure. DETAILED DESCRIPTION

[0030] In order to make the purpose, technical solution and advantages of the embodiments of the present disclosure clearer, the technical solution in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are part of the embodiments of the present disclosure, rather than all the embodiments. Based on the embodiments in the present disclosure, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present disclosure.

[0031] In the related art, the configuration of the end-cloud linkage parameters is to carry the configuration parameters of the end-cloud linkage in the form of a query in the request uniform resource locator (Uniform / Universal Resource Locator, referred to as URL), so as to achieve communication between the client and the CDN. If the query parameter only_audio=1 is carried in the URL to inform the CDN to only send audio data to achieve communication between the end and the cloud, the URL can be expressed as:

[0032] http: / / xx.xxx.com / xxxxx / xxxxonly_audio=1

[0033] However, as the number of end-cloud linkage parameters increases, the above method of carrying query parameters in the URL will cause the URL to be too long. For URLs, there is a maximum length constraint. For example, in http 1.1, the maximum length of the URL is limited to 1024 characters, and the excess part will be automatically truncated, resulting in the failure of the function corresponding to the truncated end-cloud linkage parameter.

[0034] At the same time, the query parameter structure is simple, and each linkage parameter can only be arranged in sequence in the URL. However, some end-cloud linkage parameters may have a matching relationship, and this sequential arrangement method will break the matching relationship, making it difficult for this method to support functions with complex linkage parameter configurations and difficult to expand.

[0035] Furthermore, the above method only covers the one-way linkage of the client informing the CDN to perform a certain action, that is, the client carries the query parameter in the URL to inform the CDN of the action it expects the CDN to perform, but does not support the reverse. In other words, the above method cannot support informing the client of the linkage parameters of the action that the CDN expects the client to perform. Therefore, the above method is only a one-way linkage and cannot achieve two-way linkage.

[0036] Based on this, the embodiment of the present disclosure provides a method for configuring linkage parameters, by writing linkage parameters into the header information of an http request to obtain a target http request, and then sending the target http request to a target CDN, so that the target CDN generates a first execution strategy based on the target linkage parameters. Since the header information of the http request has no limit on its length, and a complex data structure can be used in the header information to characterize the linkage parameters, thereby ensuring the integrity of the matching relationship between the linkage parameters. In addition, in the header information, corresponding linkage parameters can be added according to demand, so that the linkage parameters can be extended.

[0037] According to an embodiment of the present disclosure, an embodiment of a method for configuring linkage parameters is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0038] In this embodiment, a method for configuring linkage parameters is provided, which can be used for the above-mentioned client, such as a computer, a mobile terminal, etc. Accordingly, the local described in this embodiment is the client. Figure 1 is a flow chart of a method for configuring linkage parameters according to an embodiment of the present disclosure, such as Figure 1 As shown, the process includes the following steps:

[0039] Step S101, obtaining target linkage parameters.

[0040] The target linkage parameter includes a first linkage parameter that the local expects the target CDN to execute and / or a second linkage parameter that the target CDN expects the local to execute.

[0041] The end-cloud linkage is implemented based on the target application, such as instant messaging applications, live broadcast applications, etc. The target application is installed in the client, and the target application is connected to the target application server. The target application server can be a cloud platform or other representation forms, and there is no limitation on it here. Taking the cloud platform as an example, the cloud platform sends the target linkage parameters to the client, and the client obtains the target linkage parameters accordingly.

[0042] The target linkage parameters include the first linkage parameters and / or the second linkage parameters. The first linkage parameters are the linkage parameters that the client expects the target CDN to execute, such as frame loss function parameters, recommended packet sending rate, round-trip delay, etc. The second linkage parameters are the linkage parameters that the target CDN expects the client to execute, such as acquisition delay, acquisition packet loss rate, etc. Of course, the specific parameters included in the first linkage parameters and the second linkage parameters are set according to actual needs, and no limitation is made here. For example, in scenario A, the target linkage parameters only include the first linkage parameters; in scenario B, the target linkage parameters only include the second linkage parameters; in scenario C, the target linkage parameters include the first linkage parameters and the second linkage parameters.

[0043] The target CDN corresponds to the client, that is, the CDN on the client's communication link. The server of the target application configures the target linkage parameters according to the requirements and sends them to the client. Accordingly, the client can learn the second linkage parameters that the target CDN expects to execute locally. The client then writes the target linkage parameters into the header information of the http request to obtain the target http request, and sends the target http request to the target CDN, that is, the target CDN can learn the first linkage parameters and the second linkage parameters.

[0044] Step S102, writing the target linkage parameter into the header information of the hypertext transfer protocol request to obtain the target hypertext transfer protocol request.

[0045] The header information of the http request includes preset header information and target linkage parameters, wherein the preset header information includes but is not limited to the compression algorithm that the client can receive, the language type that the client can receive, etc., and the specific content is set according to actual needs. The target linkage parameter can be after the preset header information, and is represented by the field corresponding to the target linkage parameter to distinguish the preset header information. For example, the preset header information includes fields 1 to 5, and their corresponding field contents, and the field corresponding to the target linkage parameter is field A. The target linkage parameter is written as the field content of field A after field A, thereby realizing that the target linkage parameter is written into the header information of the http request and obtaining the target http request.

[0046] Step S103: sending the target hypertext transfer protocol request to the target content distribution network, so that the target content distribution network generates a first execution strategy based on the target linkage parameter.

[0047] After obtaining the target http request, the target http request is sent to the target CDN according to the corresponding protocol specification. Accordingly, the target CDN can obtain the target linkage parameter in the target http request to generate the first execution strategy based on the target linkage parameter.

[0048] The first execution strategy is used for the processing strategy of subsequent end-cloud communication, such as packet loss processing, frame rate processing, etc. If there is no target linkage parameter, the target CDN will process according to its own settings, which may not be compatible with the client, resulting in poor communication effect. Through the transmission of target linkage parameters, the target CDN can learn the needs of the client, thereby adjusting its own first execution strategy to ensure better end-cloud communication effect.

[0049] The method for configuring linkage parameters provided in this embodiment includes, in the target linkage parameters, a first linkage parameter that the client expects the target CDN to execute and / or a second linkage parameter that the target CDN expects the client to execute. The linkage between the client device and the target CDN is achieved through the configuration of the first linkage parameter and the second linkage parameter. Since there is no constraint on the length of the data carried in the header information of the http request, multiple linkage parameters can be configured according to demand, that is, through the configuration of the end-cloud linkage parameters, the client and the target CDN can both communicate data according to the expected needs of the other end, thereby ensuring the coordinated linkage between the end and the cloud.

[0050] In this embodiment, a method for configuring linkage parameters is provided, which can be used for the above-mentioned client, such as a computer, a mobile terminal, etc. Figure 2 is a flow chart of a method for configuring linkage parameters according to an embodiment of the present disclosure, such as Figure 2 As shown, the process includes the following steps:

[0051] Step S201, obtaining target linkage parameters.

[0052] The target linkage parameters include the first linkage parameters that the local expects the target CDN to execute and / or the second linkage parameters that the target CDN expects the local to execute. Figure 1 Step S101 of the illustrated embodiment will not be described in detail here.

[0053] Step S202, writing the target linkage parameter into the header information of the hypertext transfer protocol request to obtain the target hypertext transfer protocol request.

[0054] Specifically, the above step S202 includes:

[0055] Step S2021, obtaining a linkage parameter template.

[0056] The linkage parameter template is used to indicate the representation form of the linkage parameter in the header information.

[0057] The linkage parameter template represents the writing location and writing format of the target linkage parameters. The linkage parameter template is used to reuse the writing constraints of the target linkage parameters, without the need to re-edit the target linkage parameters obtained each time, thus improving the configuration efficiency of the end-cloud linkage parameters. After writing the target linkage parameters in the linkage parameter template, the end-cloud linkage parameters can be directly written into the header information.

[0058] Step S2022, determine the position of the target field in the linkage parameter template.

[0059] Among them, the target field corresponds to the target linkage parameter.

[0060] The target field represents the position of the target linkage parameter in the linkage parameter template. The identification of the target field can be determined after character recognition of the linkage parameter target. In addition, since the linkage parameter template is fixed and the position of the target field in the linkage parameter template is also fixed, the position of the target field in the linkage parameter can be obtained through one identification, and the position is recorded. The position of the target field can be obtained by directly extracting the recorded result later.

[0061] In some optional implementations, step S2022 includes:

[0062] Step a1, determining the position of a first target field in a linkage parameter template, where the first target field corresponds to a first linkage parameter.

[0063] Step a2, determining the position of the second target field in the linkage parameter template, the second target field corresponds to the second linkage parameter, and the target field includes the first target field and / or the second target field.

[0064] As described above, the target linkage parameter includes the first linkage parameter and / or the second linkage parameter, and accordingly, the corresponding first target field and the second target field need to be set in the linkage parameter template, wherein the first target field corresponds to the first linkage parameter, and the second target field corresponds to the second linkage parameter.

[0065] For the method of determining the positions of the first target field and the second target field, please refer to the description of determining the positions of the target fields above, which will not be repeated here.

[0066] If the target linkage parameters currently obtained only include the first linkage parameters, when writing the linkage parameter template, the field content corresponding to the second target field is empty; accordingly, if the target linkage parameters currently obtained only include the second linkage parameters, when writing the linkage parameter template, the field content of the first target field is empty.

[0067] The first target field and the second target field are respectively corresponding to the first linkage parameter and the second linkage parameter, so that the client and the target CDN can parse the field content of the corresponding field according to the requirements, thereby ensuring the accuracy of the corresponding relationship between the linkage parameter and the corresponding object.

[0068] Step S2023: based on the position of the target field, write the target linkage parameters into the linkage parameter template to obtain the end-cloud linkage parameters.

[0069] After determining the position of the target field, the target linkage parameter is written into the linkage parameter template as the field content of the target field. When writing the target linkage parameter, the data format of the acquired target linkage parameter can be adjusted before writing, or the target linkage parameter can be directly written without adjusting the data format.

[0070] The data format of the target linkage parameter is the data format used when the server of the target application sends it to the client, including but not limited to the key-value pair format or the query parameter format, etc., which depends on the communication protocol between the server and the client of the target application.

[0071] In some optional implementations, the first linkage parameter includes at least one first function linkage parameter, which includes at least one first function linkage sub-parameter and a parameter value of the first function linkage sub-parameter. The second linkage parameter includes at least one second function linkage parameter, which includes at least one second function linkage sub-parameter and a parameter value of the second function linkage sub-parameter.

[0072] For the first linkage parameter, it includes at least one first function linkage parameter, and the first function linkage parameter corresponds to the linkage function one by one. For example, the required linkage functions include packet loss and packet sending rate, which correspond to two first function linkage parameters, that is, the first function linkage parameter 1 corresponds to packet loss, and the second function linkage parameter 2 corresponds to the packet sending rate.

[0073] Furthermore, the first function linkage parameter includes at least one first function linkage sub-parameter and a parameter value of the first function linkage sub-parameter. For example, the linkage function is the packet sending rate, that is, the second function linkage parameter 2 mentioned above. This second function linkage parameter includes the first function linkage sub-parameters corresponding to the three parameters of initial packet sending speed, round-trip delay, and packet loss rate, that is, the first function linkage sub-parameter 2a corresponds to the initial packet sending speed, the first function linkage sub-parameter 2b corresponds to the round-trip delay, and the first function linkage sub-parameter 2c corresponds to the packet loss rate. Each first function linkage sub-parameter has a corresponding parameter value, that is, the parameter value of the first function linkage sub-parameter.

[0074] The format of the second function linkage parameter is similar to that of the first function linkage parameter. For details, please refer to the above description of the first function linkage parameter, which will not be repeated here.

[0075] For example, the first target field is ClientStrategyPS, that is, the client strategy field, which is used to represent the parameter identifier corresponding to the first linkage parameter, and the second target field is VendorStrategyPS, that is, the cloud strategy field, which is used to represent the parameter identifier corresponding to the second linkage parameter.

[0076] The first linkage parameters include two first function linkage parameters, namely, the frame drop function parameter configuration DropFrameParam and the packet rate recommendation function RecommendInitialNetworkParam. The first function linkage parameter DropFrameParam includes four first function linkage sub-parameters, namely, the initial packet speed Bandwidth, the round-trip delay RTT, the packet loss rate PacketLossRate and the maximum data packet length BestMTULength. The four first function linkage sub-parameters have their own corresponding parameter values, namely, the initial packet speed Bandwidth = 4000kb / s, the round-trip delay RTT = 23ms, the packet loss rate PacketLossRate = 0.1 and the maximum data packet length BestMTULength = 1000Byte.

[0077] Of course, the linkage parameters can also be expanded according to actual needs.

[0078] The first linkage parameter includes at least one first function linkage parameter, and the first function linkage parameter includes at least one first function linkage sub-parameter, and the specific number thereof is not limited, thereby achieving flexible expansion of the linkage parameters without secondary development on the terminal side.

[0079] In some optional embodiments, if the first function linkage parameter includes multiple first function linkage sub-parameters, each first function linkage sub-parameter and the parameter value of the first function linkage sub-parameter are expressed in the form of a key-value pair, and the key-value pairs corresponding to all first function linkage sub-parameters are combined using a preset identifier, and the combined content is the parameter value of the first function linkage parameter.

[0080] The first linkage parameter may include multiple levels of parameters, for example, the levels from top to bottom are the first linkage parameter, the first function linkage parameter, and the first function linkage sub-parameter described above. Of course, the first function linkage sub-parameter is not limited to being the last level of the first linkage parameter. The depth of the specific level is set according to actual needs and is not limited here.

[0081] If the first function linkage sub-parameter is the last level, the first function linkage sub-parameter and its corresponding parameter value are expressed in the form of a key-value pair, that is, the first function linkage sub-parameter is key, and the parameter value of the first function linkage sub-parameter is value, which are expressed in the form of key:value.

[0082] If the first function linkage parameter includes multiple first function linkage sub-parameters, they are combined using a preset identifier, for example, a pair of curly brackets “{}”.

[0083] Specifically, the first linkage parameter and the second linkage parameter may be expressed in a query format or a json string format. Of course, other formats may also be used, which are not limited here.

[0084] The first linkage parameter is represented by a key-value pair and a preset identifier, which is similar to the representation method of the parameters in the URL. There is no need to develop a parsing method, which improves the configuration efficiency of the end-cloud linkage parameters.

[0085] Step S2024, write the end-cloud linkage parameters into the header information of the hypertext transfer protocol request to obtain the target hypertext transfer protocol request.

[0086] After the above steps are processed, the end-cloud linkage parameters obtained using the linkage parameter template are written into the header information of the http request to obtain the target http request.

[0087] In some optional implementations, the above step S2024 includes:

[0088] Step b1, obtaining preset header information of the Hypertext Transfer Protocol request.

[0089] Step b2: obtaining a target Hypertext Transfer Protocol request based on preset header information and end-cloud linkage parameters.

[0090] For example, in one example of header information, the preset header information is the first five fields and their field contents. The specific content of the preset header information is related to the actual communication scenario, and no limitation is made here on its specific fields and their field contents. The preset header information is combined with the end-cloud linkage parameters to obtain the target http request.

[0091] The first linkage parameter and the second linkage parameter in the end-cloud linkage parameters are expressed in the form of key-value pairs. The first linkage parameter corresponds to the first target field ClientStrategyPS, and the second linkage parameter corresponds to the second target field VendorStrategyPS.

[0092] Step S203, sending the target HTTP request to the target content distribution network, so that the target content distribution network generates a first execution strategy based on the target linkage parameter. Figure 1 The description of step S103 of the illustrated embodiment will not be repeated here.

[0093] The method for configuring linkage parameters provided in this embodiment, through the setting of linkage parameter template, only needs to query the location of the target field and write the target linkage parameters after obtaining the target linkage parameters. There is no need to organize the target linkage parameters to meet the corresponding protocol transmission requirements, thereby improving the configuration efficiency of the end-cloud linkage parameters.

[0094] In some optional implementations, the above linkage parameter configuration method includes:

[0095] Step c1, parsing the target linkage parameter to obtain a second linkage parameter.

[0096] Step c2: generating a second execution strategy based on the second linkage parameter.

[0097] As described above, the target linkage parameter is sent from the server of the target application to the client. After obtaining the target linkage parameter, the client parses it to obtain the second linkage parameter. The second linkage parameter is the parameter that the target CDN expects the client to execute. After obtaining the second linkage parameter, the second execution strategy is generated based on it.

[0098] In some optional implementations, the generation of the second execution strategy further includes obtaining the current network state, and generating the second execution strategy in combination with the current network state and the second linkage parameter. That is, the second execution strategy is generated in combination with the current state of the client and the requirements of the target CDN for the client. The second execution strategy is a strategy that needs to be executed when the client communicates with the target CDN.

[0099] The client generates a local second execution strategy based on the second linkage parameter, thereby determining the execution strategy according to the requirements of the target CDN side.

[0100] In this embodiment, a method for configuring linkage parameters is provided, which can be used for the above-mentioned target CDN end. Figure 3 is a flow chart of a method for configuring linkage parameters according to an embodiment of the present disclosure, such as Figure 3 As shown, the process includes the following steps:

[0101] Step S301, receiving a target hypertext transfer protocol request.

[0102] The header information of the target http request includes target linkage parameters, and the target linkage parameters include a first linkage parameter that the client expects to be executed locally and / or a second linkage parameter that the local expects the client to execute.

[0103] For details about the target http request, please see above Figure 1 or Figure 2 The description of the corresponding parts in the embodiments will not be repeated here.

[0104] Step S302: parse the target HTTP request to obtain target linkage parameters.

[0105] The parsing method of the target http request is related to the data format represented by the end-cloud linkage parameter in the linkage parameter template, and the specific parsing method is not limited here. After parsing the target http request, the target linkage parameter is obtained.

[0106] Step S303: Generate a first execution strategy based on the target linkage parameters.

[0107] The target linkage parameters include the first linkage parameter and / or the second linkage parameter. When generating the first execution strategy, the first linkage parameter is mainly used, and the second linkage parameter is used as a supplement. That is, the generation of the first execution strategy is mainly based on the first linkage parameter, and the second linkage parameter is used as a supplement.

[0108] In some optional implementations, step S303 includes:

[0109] Step d1, obtaining the current local communication status.

[0110] Step d2: generating a first execution strategy based on the current communication state and target linkage parameters.

[0111] The current communication status includes but is not limited to the current network status, the current packet loss rate, etc. The first execution strategy is generated in combination with the current communication status and the target linkage parameters. The first execution strategy is generated in combination with the local current communication status, which ensures that the first execution strategy can not only meet the needs of the client, but also adapt to the local communication status, thereby achieving a better end-cloud linkage effect.

[0112] The method for configuring linkage parameters provided in this embodiment includes, in the target linkage parameters, a first linkage parameter that the client expects the target CDN to execute and / or a second linkage parameter that the target CDN expects the client to execute. The linkage between the client device and the target CDN is achieved through the configuration of the first linkage parameter and the second linkage parameter. Since there is no constraint on the length of the data carried in the header information of the http request, multiple linkage parameters can be configured according to demand, that is, through the configuration of the end-cloud linkage parameters, the client and the target CDN can both communicate data according to the expected needs of the other end, thereby ensuring the coordinated linkage between the end and the cloud.

[0113] As a specific application embodiment of the embodiment of the present disclosure, the server of the target application is a cloud platform, and the user sets the target configuration parameters by interacting with the cloud platform. The cloud platform sends the target configuration parameters to the client of the target application. After the client starts the target application, the client can obtain the target configuration parameters. The target configuration parameters include a first linkage parameter and a second linkage parameter. The client generates a target http request based on the linkage parameter template and the target configuration parameters, and sends the target http request to the target CDN. Correspondingly, after the target CDN receives the target http request, it parses it and can obtain the target configuration parameters. Then, the target CDN generates a first execution policy based on the target configuration parameters, and the client generates a second execution policy based on the second linkage parameters. Based on this, when the client communicates with the target CDN, the client processes data based on the second execution policy, and the target CDN processes data based on the first execution policy.

[0114] In this embodiment, a configuration device for linkage parameters is also provided, which is used to implement the above-mentioned embodiments and preferred implementation modes, and the descriptions that have been made will not be repeated. As used below, the term "module" can implement a combination of software and / or hardware of a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceivable.

[0115] This embodiment provides a configuration device for linkage parameters, such as Figure 4 As shown, including:

[0116] The target linkage parameter acquisition module 401 is used to acquire target linkage parameters, where the target linkage parameters include first linkage parameters that the local expects the target content distribution network to execute and / or second linkage parameters that the target content distribution network expects the local to execute.

[0117] The target linkage parameter writing module 402 is used to write the target linkage parameter into the header information of the hypertext transfer protocol request to obtain the target hypertext transfer protocol request.

[0118] The target hypertext transfer protocol request sending module 403 is used to send the target hypertext transfer protocol request to the target content distribution network, so that the target content distribution network generates a first execution strategy based on the target linkage parameter.

[0119] In some optional implementations, the target linkage parameter writing module 402 includes:

[0120] The linkage parameter template acquisition unit is used to acquire a linkage parameter template, where the linkage parameter template is used to represent the representation form of the linkage parameter in the header information.

[0121] The target field position determination unit is used to determine the position of the target field in the linkage parameter template, and the target field corresponds to the target linkage parameter.

[0122] The target linkage parameter writing unit is used to write the target linkage parameters in the linkage parameter template based on the position of the target field to obtain the end-cloud linkage parameters.

[0123] The end-cloud linkage parameter writing unit is used to write the end-cloud linkage parameters into the header information of the hypertext transfer protocol request to obtain the target hypertext transfer protocol request.

[0124] In some optional implementations, the target field location determination unit includes:

[0125] The first target field position determination subunit is used to determine the position of the first target field in the linkage parameter template, where the first target field corresponds to the first linkage parameter. And / or,

[0126] The second target field position determination subunit is used to determine the position of the second target field in the linkage parameter template, the second target field corresponds to the second linkage parameter, and the target field includes the first target field and / or the second target field.

[0127] In some optional embodiments, the first linkage parameters include at least one first function linkage parameter, the first function linkage parameters include at least one first function linkage sub-parameter and the parameter value of the first function linkage sub-parameter; and / or, the second linkage parameters include at least one second function linkage parameter, the second function linkage parameters include at least one second function linkage sub-parameter and the parameter value of the second function linkage sub-parameter.

[0128] In some optional embodiments, if the first function linkage parameter includes multiple first function linkage sub-parameters, each first function linkage sub-parameter and the parameter value of the first function linkage sub-parameter are expressed in the form of a key-value pair, and the key-value pairs corresponding to all first function linkage sub-parameters are combined using a preset identifier, and the combined content is the parameter value of the first function linkage parameter.

[0129] In some optional implementations, the end-cloud linkage parameter writing unit includes:

[0130] The preset header information obtaining subunit is used to obtain the preset header information of the hypertext transfer protocol request.

[0131] The target hypertext transfer protocol request determination subunit is used to obtain the target hypertext transfer protocol request based on preset header information and end-cloud linkage parameters.

[0132] In some optional embodiments, the device further comprises:

[0133] A parsing module, used for parsing the target linkage parameter to obtain the second linkage parameter;

[0134] The second execution strategy generating module is used to generate a second execution strategy based on the second linkage parameter.

[0135] This embodiment provides a configuration device for linkage parameters, such as Figure 5 As shown, including:

[0136] The target HTTP request receiving module 501 is used to receive a target HTTP request, the header information of which includes a target linkage parameter, which includes a first linkage parameter that the client expects to execute locally and / or a second linkage parameter that the local expects the client to execute.

[0137] The target hypertext transfer protocol request parsing module 502 is used to parse the target hypertext transfer protocol request to obtain target linkage parameters.

[0138] The first execution strategy generating module 503 is used to generate a first execution strategy based on the target linkage parameters.

[0139] In some optional implementations, the first execution strategy generation module 503 includes:

[0140] The current communication status acquisition unit is used to acquire the local current communication status.

[0141] The first execution strategy generating unit is used to generate a first execution strategy based on the current communication state and the target linkage parameter.

[0142] The configuration device of the linkage parameters in this embodiment is presented in the form of a functional unit, where the unit refers to an ASIC (Application Specific Integrated Circuit) circuit, a processor and memory that executes one or more software or fixed programs, and / or other devices that can provide the above functions.

[0143] The further functional description of each of the above modules and units is the same as that of the above corresponding embodiments and will not be repeated here.

[0144] The present disclosure also provides a computer device having the above Figure 4 or Figure 5 The configuration device of the linkage parameters is shown.

[0145] See also Figure 6 , Figure 6 is a schematic diagram of a computer device provided by an optional embodiment of the present disclosure, such as Figure 6 As shown, the computer device includes: one or more processors 10, a memory 20, and interfaces for connecting various components, including high-speed interfaces and low-speed interfaces. Various components are connected to each other using different buses for communication, and can be installed on a common mainboard or installed in other ways as needed. The processor can process the instructions executed in the computer device, including instructions stored in or on the memory to display the graphical information of the GUI on an external input / output device (such as, a display device coupled to the interface). In some optional embodiments, if necessary, multiple processors and / or multiple buses can be used together with multiple memories and multiple memories. Similarly, multiple computer devices can be connected, and each device provides some necessary operations (for example, as a server array, a group of blade servers, or a multi-processor system). Figure 6 A processor 10 is taken as an example.

[0146] The processor 10 may be a central processing unit, a network processor or a combination thereof. The processor 10 may further include a hardware chip. The hardware chip may be a dedicated integrated circuit, a programmable logic device or a combination thereof. The programmable logic device may be a complex programmable logic device, a field programmable gate array, a general purpose array logic or any combination thereof.

[0147] The memory 20 stores instructions executable by at least one processor 10, so that the at least one processor 10 executes the method shown in the above embodiment.

[0148] The memory 20 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created according to the use of the computer device, etc. In addition, the memory 20 may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some optional embodiments, the memory 20 may optionally include a memory remotely arranged relative to the processor 10, and these remote memories may be connected to the computer device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0149] The memory 20 may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a flash memory, a hard disk or a solid state drive; the memory 20 may also include a combination of the above types of memory.

[0150] The computer device further comprises a communication interface 30 for the computer device to communicate with other devices or a communication network.

[0151] The embodiments of the present disclosure also provide a computer-readable storage medium. The above-mentioned method according to the embodiments of the present disclosure can be implemented in hardware, firmware, or can be implemented as a computer code that can be recorded in a storage medium, or can be implemented as a computer code that is originally stored in a remote storage medium or a non-temporary machine-readable storage medium and will be stored in a local storage medium and downloaded through a network, so that the method described herein can be stored in such software processing on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only storage memory, a random access memory, a flash memory, a hard disk or a solid-state drive, etc.; further, the storage medium can also include a combination of the above-mentioned types of memory. It can be understood that a computer, a processor, a microprocessor controller, or programmable hardware includes a storage component that can store or receive software or computer code. When the software or computer code is accessed and executed by a computer, a processor, or hardware, the method shown in the above embodiment is implemented.

[0152] It is understandable that before using the technical solutions disclosed in the embodiments of the present disclosure, the types, scope of use, usage scenarios, etc. of the personal information involved in the present disclosure should be informed to the user and the user's authorization should be obtained in an appropriate manner in accordance with relevant laws and regulations.

[0153] For example, in response to receiving an active request from a user, a prompt message is sent to the user to clearly prompt the user that the operation requested to be performed will require obtaining and using the user's personal information. Thus, the user can autonomously choose whether to provide personal information to software or hardware such as an electronic device, application, server, or storage medium that performs the operation of the technical solution of the present disclosure according to the prompt message.

[0154] As an optional but non-limiting implementation, in response to receiving an active request from the user, the prompt information may be sent to the user in the form of a pop-up window, in which the prompt information may be presented in text form. In addition, the pop-up window may also carry a selection control for the user to choose "agree" or "disagree" to provide personal information to the electronic device.

[0155] It is understandable that the above notification and the process of obtaining user authorization are merely illustrative and do not constitute a limitation on the implementation of the present disclosure. Other methods that meet the relevant laws and regulations may also be applied to the implementation of the present disclosure.

[0156] Although the embodiments of the present disclosure have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present disclosure, and such modifications and variations are all within the scope defined by the appended claims.

Claims

1. A method for configuring linkage parameters, characterized in that: The method comprises: Acquire target linkage parameters, where the target linkage parameters include first linkage parameters that the local expects the target content distribution network to execute and / or second linkage parameters that the target content distribution network expects the local to execute; Writing the target linkage parameter into the header information of a hypertext transfer protocol request to obtain a target hypertext transfer protocol request; The target hypertext transfer protocol request is sent to the target content distribution network, so that the target content distribution network generates a first execution strategy based on the target linkage parameter.

2. The method according to claim 1, characterized in that The step of writing the target linkage parameter into header information of a hypertext transfer protocol request to obtain a target hypertext transfer protocol request includes: Obtaining a linkage parameter template, where the linkage parameter template is used to represent the representation form of the linkage parameter in the header information; Determine a position of a target field in the linkage parameter template, the target field corresponding to the target linkage parameter; Based on the position of the target field, write the target linkage parameter into the linkage parameter template to obtain the end-cloud linkage parameter; The end-cloud linkage parameter is written into the header information of the hypertext transfer protocol request to obtain the target hypertext transfer protocol request.

3. The method according to claim 2, characterized in that The determining the position of the target field in the linkage parameter template includes: determining a position of a first target field in the linkage parameter template, the first target field corresponding to the first linkage parameter; and / or, A position of a second target field in the linkage parameter template is determined, where the second target field corresponds to the second linkage parameter, and the target field includes the first target field and / or the second target field.

4. The method according to claim 1, characterized in that: The first linkage parameters include at least one first function linkage parameter, which includes at least one first function linkage sub-parameter and a parameter value of the first function linkage sub-parameter; and / or, the second linkage parameters include at least one second function linkage parameter, which includes at least one second function linkage sub-parameter and a parameter value of the second function linkage sub-parameter.

5. The method according to claim 4, characterized in that If the first function linkage parameter includes multiple first function linkage sub-parameters, each of the first function linkage sub-parameters and the parameter value of the first function linkage sub-parameter is expressed in the form of a key-value pair, and the key-value pairs corresponding to all the first function linkage sub-parameters are combined using a preset identifier, and the combined content is the parameter value of the first function linkage parameter.

6. The method according to claim 2, characterized in that The step of writing the end-cloud linkage parameter into the header information of the hypertext transfer protocol request to obtain a target hypertext transfer protocol request includes: Obtaining preset header information of the hypertext transfer protocol request; Based on the preset header information and the end-cloud linkage parameters, the target Hypertext Transfer Protocol request is obtained.

7. The method according to any one of claims 1 to 6, characterized in that The method further comprises: Parsing the target linkage parameter to obtain the second linkage parameter; A second execution strategy is generated based on the second linkage parameter.

8. A method for configuring linkage parameters, characterized in that: The method comprises: Receiving a target hypertext transfer protocol request, wherein header information of the target hypertext transfer protocol request includes a target linkage parameter, wherein the target linkage parameter includes a first linkage parameter that the client expects to be executed locally and / or a second linkage parameter that the local expects the client to execute; Parsing the target hypertext transfer protocol request to obtain the target linkage parameter; A first execution strategy is generated based on the target linkage parameter.

9. The method according to claim 8, characterized in that The generating the first execution strategy based on the target linkage parameter includes: Get the current local communication status; The first execution strategy is generated based on the current communication state and the target linkage parameter.

10. A linkage parameter configuration device, characterized in that: The device comprises: A target linkage parameter acquisition module, used to acquire target linkage parameters, wherein the target linkage parameters include a first linkage parameter that the local expects the target content distribution network to execute and / or a second linkage parameter that the target content distribution network expects the local to execute; A target linkage parameter writing module, used for writing the target linkage parameter into the header information of the hypertext transfer protocol request to obtain a target hypertext transfer protocol request; The target hypertext transfer protocol request sending module is used to send the target hypertext transfer protocol request to the target content distribution network, so that the target content distribution network generates a first execution strategy based on the target linkage parameter.

11. A linkage parameter configuration device, characterized in that: A target hypertext transfer protocol request receiving module, used to receive a target hypertext transfer protocol request, wherein the header information of the target hypertext transfer protocol request includes a target linkage parameter, wherein the target linkage parameter includes a first linkage parameter that the client expects to execute locally and / or a second linkage parameter that the local expects the client to execute; A target hypertext transfer protocol request parsing module, used for parsing the target hypertext transfer protocol request to obtain the target linkage parameter; The first execution strategy generating module is used to generate the first execution strategy based on the target linkage parameter.

12. A computer device, characterized in that: include: A memory and a processor, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the method for configuring linkage parameters according to any one of claims 1 to 9 by executing the computer instructions.

13. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a computer to execute the method for configuring linkage parameters according to any one of claims 1 to 9.

Images