A standardized interface system and method for multi-scenario service docking

Abstract

The application provides a standardized interface system and method for multi-scene service docking, belonging to the field of digital media technology. First, service interface information sets containing interactive formats, data transmission modes and function call specification information are obtained from service registration centers of various digital media scenes. Then, interface interaction requirements are analyzed, and an interface interaction requirement list containing interactive trigger conditions, data exchange types and response timeliness requirements is generated. Next, an interface adaptation rule set containing format, transmission and call adaptation rules is generated according to the requirement list. Then, the rule set is used to adapt and process service interfaces of various scenes, and a standardized interface interaction module is obtained. Finally, a cross-scene service interaction protocol is constructed through the module, guiding data interaction and function calls of service interfaces of different digital media scenes, so that efficient and standardized docking of digital media multi-scene services is realized.

Description

Technical Field

[0001] This invention relates to the field of digital media technology, and more specifically, to a standardized interface system and method for multi-scenario service integration. Background Technology

[0002] In the current booming development of the digital media field, various digital media platforms have sprung up like mushrooms after rain, covering multiple formats such as video, audio, and text, and are widely used in many scenarios such as social entertainment, news information, online education, and e-commerce marketing. Due to differences in development teams, technical architectures, and business focuses, the service systems in different digital media scenarios exhibit great diversity in their service interfaces, including interaction formats, data transmission methods, and function call specifications.

[0003] For example, social media platform service interfaces may focus on the rapid sharing of user social relationships and content, using a concise JSON format for data interaction and transmitting data via real-time push notifications. In contrast, online education platform service interfaces prioritize the accuracy and completeness of course information, learning progress, and other data, potentially using XML format and exchanging data through scheduled batch transmissions. These differences make seamless integration and efficient interaction between services in different digital media scenarios difficult.

[0004] Currently, most existing digital media service integration methods are customized for specific scenarios or platforms, lacking a universal, standardized interface method to achieve automated and intelligent integration of services across multiple scenarios. Customized development not only requires significant investment of human, material, and time resources, but also struggles to quickly adapt to new scenario requirements as digital media businesses continue to expand and evolve, leading to difficulties in system maintenance and upgrades. This severely restricts the innovative development and cross-scenario integration of the digital media industry. Summary of the Invention

[0005] In view of the aforementioned problems, and in conjunction with the first aspect of the present invention, embodiments of the present invention provide a standardized interface method for multi-scenario service integration, the method comprising:

[0006] The service interface information set is obtained from the service registration center of each scenario. The service interface information set includes the interaction format information, data transmission method information and function call specification information of the service interface in each scenario.

[0007] Based on the service interface information set, the interface interaction requirements are analyzed to obtain an interface interaction requirement list. The interface interaction requirement list includes the interaction trigger conditions, data exchange types and response time requirements between service interfaces in each scenario.

[0008] An interface adaptation rule set is generated based on the interface interaction requirement list. The interface adaptation rule set includes format adaptation rules for unifying the service interface interaction format in various scenarios, transmission adaptation rules for coordinating data transmission methods, and call adaptation rules for standardizing function call processes.

[0009] Based on the interface adaptation rule set, the service interfaces of each scenario are adapted to obtain a standardized interface interaction module. The standardized interface interaction module is compatible with the interaction format, data transmission method and function call specification of the service interfaces of each scenario.

[0010] A cross-scenario service interaction protocol is constructed through the standardized interface interaction module. The cross-scenario service interaction protocol is used to guide service interfaces in different scenarios to achieve data interaction and function calls through the standardized interface interaction module.

[0011] In another aspect, embodiments of the present invention also provide a standardized interface system for multi-scenario service integration, including a processor and a machine-readable storage medium. The machine-readable storage medium is connected to the processor. The machine-readable storage medium is used to store programs, instructions, or code. The processor is used to execute the programs, instructions, or code in the machine-readable storage medium to implement the above-described method.

[0012] Based on the above, service interface information sets are obtained from service registration centers of various scenarios. These sets are then analyzed in depth to identify interface interaction requirements, generating an interface interaction requirement list that clarifies the key elements and specific requirements for interaction between service interfaces in different scenarios. An interface adaptation rule set generated from the requirement list is used to standardize multiple key dimensions, including interaction format, data transmission method, and function call process, ensuring effective coordination and compatibility for differences in service interfaces across different digital media scenarios. The standardized interface interaction module, obtained by adapting the service interfaces of each scenario according to the adaptation rule set, can seamlessly connect to service interfaces of various digital media scenarios. Finally, the cross-scenario service interaction protocol built through the standardized interface interaction module provides unified and standardized interaction guidelines for service interfaces in different digital media scenarios, achieving efficient and stable data interaction and function calls across scenarios. This significantly improves the integration efficiency and collaborative capabilities of digital media services, reduces the cost and difficulty of multi-scenario service integration, and enhances the system's flexibility and scalability. Attached Figure Description

[0013] Figure 1 This is a schematic diagram of the execution flow of the standardized interface method for multi-scenario service integration provided in the embodiments of the present invention.

[0014] Figure 2This is a schematic diagram of exemplary hardware and software components of the standardized interface system for multi-scenario service interoperability provided in the embodiments of the present invention. Detailed Implementation

[0015] The present invention will now be described in detail with reference to the accompanying drawings. Figure 1 This is a flowchart illustrating a standardized interface method for multi-scenario service integration provided in one embodiment of the present invention. The standardized interface method for multi-scenario service integration will be described in detail below.

[0016] Step S110: Obtain a set of service interface information from the service registration center of each scenario. The set of service interface information includes the interaction format information, data transmission method information and function call specification information of the service interfaces in each scenario.

[0017] In this embodiment, video content distribution platforms, content creation tool services, and user interaction community services in the digital media field are selected as three different scenarios. The video content distribution platform is used to push various types of video content to users; the content creation tool service provides creators with functions such as video editing and adding special effects; and the user interaction community service allows users to interact with videos by commenting and liking them. Each scenario has a corresponding service registry center that stores relevant information about its respective service interfaces.

[0018] To obtain the service interface information set, communication connections need to be established with the service registry centers for these three scenarios. These communication connections use standard network communication protocols, obtaining the necessary information by sending request commands to each service registry center.

[0019] Step S111: Access the service registration center of each scenario and send a service interface information query request. The service interface information query request includes the information type identifier information to be obtained. The information type identifier information corresponds to the interaction format information, data transmission method information and function call specification information.

[0020] When accessing the service registry of a video content distribution platform, the information type identifiers in the constructed service interface information query request are set to "interaction format information identifier," "data transmission method information identifier," and "function call specification information identifier," respectively. This request is then transmitted over the network to the service registry of the video content distribution platform. The same operation is also applied to the service registry of the content creation tool service and the user interaction community service.

[0021] Step S112: Receive the service interface information set returned by the service registration center of each scenario. The service interface information set includes the interaction format information, data transmission method information and function call specification information of the service interfaces in each scenario.

[0022] After receiving a query request, the service registry center of the video content distribution platform can retrieve its stored information and then return the corresponding set of service interface information. This interaction format information may include video metadata fields, such as video name, duration, resolution, and other related format descriptions; data transmission method information, covering the protocol and encryption method used to transmit video data; and function call specification information, involving the relevant specifications for calling the platform's video push and query functions.

[0023] The service interface information set returned by the service registry center of the content creation tool service may include interaction format information, which may involve the format field of the video file output by the creation tool; data transmission method information, which is related to the way the tool transmits data such as the created video clips between itself and other services; and function call specification information, which is about the rules for calling functions such as editing and adding effects.

[0024] The information returned by the service registration center for user interaction community services may include the field format of user comments, likes, and other data, the data transmission method information, the transmission protocol and encryption of this interactive data, and the function call specification information, which is the specification for calling community interaction functions.

[0025] Step S120: Analyze the interface interaction requirements based on the service interface information set to obtain an interface interaction requirement list. The interface interaction requirement list includes the interaction triggering conditions, data exchange types, and response time requirements between service interfaces in each scenario.

[0026] After obtaining the service interface information sets for the three scenarios, the service interface information is analyzed to clarify the interaction requirements between the service interfaces in different scenarios, thereby forming a list of interface interaction requirements.

[0027] Step S121: Parse the interaction format information in the service interface information set to extract the field definition information, field type information and field arrangement order information of each service interface.

[0028] For the interaction format information of the video content distribution platform service interface, extract the field definition information, field type information and field arrangement order information related to video metadata from its interaction format description.

[0029] Step S1211: Perform structured parsing on the interaction format information in the service interface information set, identify the field definition description content of each service interface, and extract the field name, meaning and constraint conditions from the field definition description content as field definition information.

[0030] When performing structured parsing of the interaction format information of the video content distribution platform service interface, the field definitions and descriptions related to video metadata were identified. From these, the following fields were extracted: "Video Identifier," which is a unique identifier for the video, with constraints that it cannot be repeated and cannot be empty; "Video Title," which is a brief description of the video content, with constraints that the character length must be within a certain range; and "Publish Time," which is the time the video was uploaded to the platform, with constraints that it must conform to a specific time format.

[0031] Similarly, by parsing the interaction format information of the content creation tool service interface, the following fields are extracted: "Project Identifier" field, which means a unique identifier for the creation project, with the constraint that it cannot be repeated; "Material Path" field, which means the storage path of the materials used to create the video, with the constraint that the path format is correct; and "Effect Type" field, which means the type of effect added to the video, with the constraint that it belongs to the type of the preset effect list.

[0032] For the user interaction community service interface, the following fields are extracted: "User Identifier", which is a unique identifier for users, with the constraint that it cannot be repeated; "Comment Content", which is the text of the user's comment on the video, with the constraint that it conforms to the content specifications stipulated by the community; and "Number of Likes", which is the number of times the user has liked the video, with the constraint that it must be a non-negative integer.

[0033] Step S1212: Analyze the field type annotations in the interactive format information to determine the data type, length, and value range of each field as field type information.

[0034] In the video content distribution platform service interface, the data type label of the "Video Identifier" field indicates that its data type is string, with a fixed length of a certain number of characters, and the value range is a combination of letters and numbers; the data type of "Video Title" is string, with a length between the minimum and maximum number of characters, and the value range is any legal character; the data type of "Publication Time" is date and time, with a fixed length, and the value range is legal date and time values.

[0035] In the content creation tool service interface, the "project identifier" data type is a string with a fixed length of several characters, and the value range is a combination of characters generated by specific rules; the "material path" data type is a string with a length within a certain range, and the value range is a string that conforms to the file system path rules; the "effect type" data type is an enumeration type with a fixed length, and the value range is the value in the preset effect type list.

[0036] In the user interaction community service interface, the "User Identifier" data type is a string with a fixed length of several characters, and the value range is a unique character combination generated by the system; the "Comment Content" data type is a string with a length between the minimum and maximum number of characters, and the value range is characters that conform to the content specifications; the "Number of Likes" data type is an integer, the length of which is determined according to the integer range, and the value range is zero and positive integers.

[0037] Step S1213: Parse the field arrangement description in the interactive format information and obtain the order of each field in the data transmission process as the field arrangement order information.

[0038] By analyzing the field arrangement description of the video content distribution platform service interface interaction format, it was found that the order of the fields during data transmission is "video identifier", "video title", and "publication time".

[0039] The fields in the content creation tool service interface are arranged in the following order: "Project Identifier", "Material Path", and "Effect Type".

[0040] The fields in the user interaction community service interface are arranged in the following order: "User ID", "Comment Content", and "Number of Likes".

[0041] Step S1214: Associate and store the extracted field definition information, field type information, and field arrangement order information with the corresponding service interface to generate an interaction format feature set.

[0042] The field definition information, field type information, and field order information extracted from the video content distribution platform service interface are associated and stored in a data structure. This data structure contains the service interface name and its corresponding information. Similarly, the information from the content creation tool service interface and the user interaction community service interface is associated and stored. The associated information of these three service interfaces is integrated to form an interactive format feature set.

[0043] Step S122: Classify the data transmission method information in the service interface information set to determine the transmission protocol type, transmission encryption method and transmission rate limit information used by each service interface. Also, analyze the function call specification information in the service interface information set to obtain the call parameter requirements, return value format and error code definition information of each service interface.

[0044] The data transmission method information and function call specification information in the information sets of the three scenario service interfaces are processed to obtain the corresponding parameters and specifications.

[0045] Step S1221: Parse the data transmission method information in the service interface information set field by field, extract the content describing the transmission protocol, and determine the transmission protocol type used by each service interface. The transmission protocol type includes text-based protocols and binary-based protocols.

[0046] The data transmission method information of the video content distribution platform's service interface was analyzed, and the content of each field was examined to extract the section describing the transmission protocol, confirming that it uses a text-based protocol. This protocol organizes data in text format, making it highly readable.

[0047] The data transmission method information in the content creation tool service interface describes a binary-based protocol. This protocol transmits data in binary form, resulting in high transmission efficiency.

[0048] After parsing the data transmission method information of the user interaction community service interface, it was determined that it uses a text-based protocol.

[0049] Step S1222: Parse the description of encryption processing in the data transmission method information, and identify the transmission encryption method used by each service interface. The transmission encryption method includes symmetric encryption and asymmetric encryption.

[0050] The data transmission method information in the video content distribution platform service interface indicates that it uses symmetric encryption. This symmetric encryption method uses the same key for both encryption and decryption.

[0051] The data transmission method information of the content creation tool service interface indicates that it uses an asymmetric encryption method, employing a public key for encryption and a private key for decryption.

[0052] The user interaction community service interface uses symmetric encryption to encrypt data transmission.

[0053] Step S1223: Extract the transmission rate-related description from the data transmission method information, and determine the upper and lower limits of the transmission rate for each service interface as transmission rate limitation information.

[0054] From the data transmission method information of the video content distribution platform service interface, the relevant description of the transmission rate is extracted, and the upper limit of the transmission rate is determined to be a certain range, and the lower limit is a certain range.

[0055] In the data transmission method information of the content creation tool service interface, the description of the transmission rate gives an upper limit and a lower limit of the transmission rate.

[0056] The upper and lower limits of the transmission rate of the user interaction community service interface are also extracted from its data transmission method information, and are the corresponding ranges.

[0057] Step S1224: Associate the determined transmission protocol type, transmission encryption method, and transmission rate limit information with the corresponding service interface to generate a transmission feature set.

[0058] The text-based protocol, symmetric encryption method, and corresponding transmission rate limits of the video content distribution platform service interface are associated and stored in a specific data structure. Similarly, relevant information from the content creation tool service interface and the user interaction community service interface is associated and stored. Then, these three sets of associated information are integrated to generate a transmission feature set.

[0059] Step S1225: Extract the function call specification information from the service interface information set, and obtain the parameter name, parameter type, parameter quantity and the dependency relationship between parameters required by each service interface from the call parameter description part as the call parameter requirements.

[0060] The function call specification information for the video content distribution platform service interface shows that when calling the "Video Query" function, the required parameter name is "Query Condition," the parameter type is string, the parameter quantity is one, and this parameter has no other parameter dependencies. When calling the "Video Push" function, the parameter names are "User Preference" and "Video List," the parameter types are string and list respectively, and the parameter quantity is two. The "Video List" parameter depends on the "User Preference" parameter to determine the content range.

[0061] In the function call specification information of the content creation tool service interface, the parameter name for calling the "Material Import" function is "Material Address", the parameter type is string, the number of parameters is one, and there are no parameter dependencies; the parameter names for calling the "Effect Add" function are "Project Identifier" and "Effect Parameter", the parameter types are string and dictionary respectively, the number of parameters is two, and "Effect Parameter" depends on the project attribute corresponding to "Project Identifier".

[0062] In the user interaction community service interface, the parameter names for calling the "comment submission" function are "user identifier", "video identifier" and "comment text". All parameters are of string type, and there are three parameters. The "comment text" depends on the validity of "user identifier" and "video identifier". The parameter name for calling the "like statistics" function is "video identifier". The parameter type is string, and there is only one parameter with no parameter dependency.

[0063] Step S1226: Parse the return value description in the function call specification information to determine the structure, data type, and field information of the data returned by each service interface as the return value format.

[0064] The function call specification information of the video content distribution platform service interface indicates in the return value description section that the "video query" function returns data with a list structure and a composite data type, including fields such as "video identifier", "video title", and "publication time"; the "video push" function returns data with a list structure and a composite data type, including fields such as "video identifier" and "push priority".

[0065] In the content creation tool service interface, the data returned by the "Material Import" function is an object with a composite data type, containing fields such as "Import Status" and "Material ID"; the data returned by the "Effect Addition" function is an object with a composite data type, containing fields such as "Add Result" and "Project Update Time".

[0066] The "Comment Submission" function of the user interaction community service interface returns data with an object structure and a composite data type, including fields such as "Submission Status" and "Comment ID"; the "Like Statistics" function returns data with an object structure and a composite data type, including fields such as "Video Identifier" and "Current Number of Likes".

[0067] Step S1227: Extract the error handling section from the function call specification information, and obtain the error identifier, error description, and error level defined by each service interface as error code definition information.

[0068] In the function call specification information of the video content distribution platform service interface, the error handling section shows that the error identifier "E101" is described as "the query condition is empty" and the error level is general; the error identifier "E102" is described as "the video does not exist" and the error level is severe.

[0069] In the error handling section of the content creation tool service interface, the error label "F201" corresponds to the error description "invalid material address" and the error level is general; the error label "F202" corresponds to the error description "project identifier does not exist" and the error level is severe.

[0070] In the user interaction community service interface, the error description corresponding to the error identifier "C301" is "invalid user identifier", and the error level is general; the error description corresponding to the error identifier "C302" is "comment content violates regulations", and the error level is severe.

[0071] Step S123: Based on the extracted field definition information, field type information, field arrangement order information, transmission protocol type, transmission encryption method, transmission rate limit information, call parameter requirements, return value format and error code definition information, analyze the interaction possibilities and interaction constraints between service interfaces in different scenarios, and generate an interface interaction requirement list containing the interaction trigger conditions, data exchange types and response time requirements between service interfaces in each scenario.

[0072] Based on the information extracted above, we analyze the interaction between service interfaces in three different scenarios: video content distribution platform, content creation tool service, and user interaction community service.

[0073] Step S1231: Summarize the extracted field definition information, field type information, field arrangement order information, transmission protocol type, transmission encryption method, transmission rate limit information, call parameter requirements, return value format and error code definition information to establish a feature information database for each scenario service interface.

[0074] All information extracted from the three service interfaces, including field definition information and field type information, is aggregated into a unified database. This database is categorized according to the scenario to which the service interface belongs, with each service interface entry containing its corresponding information, forming a feature information database.

[0075] Step S1232: Select two service interfaces from the feature information database for any two different scenarios, compare the field definition information of the two service interfaces to determine the compatibility of the fields, and if the field names and meanings are consistent and the field type information is matched, then it is determined that the two service interfaces have the possibility of interaction at the field level.

[0076] We selected the video content distribution platform service interface and the content creation tool service interface for analysis. Comparing their field definitions, we found that the "video identifier" field has the same name and meaning in both interfaces, and the field type information is string, with matching attributes such as length. Therefore, we determined that these two service interfaces have the potential for interaction at the field level.

[0077] Then, by selecting the video content distribution platform service interface and the user interaction community service interface, it was found that the fields such as "video identifier" and "user identifier" match in name, meaning and type, thus confirming that they have the potential for interaction at the field level.

[0078] By selecting the content creation tool service interface and the user interaction community service interface, and comparing them, it was found that some related fields matched in name, meaning and type, confirming that there was potential for interaction at the field level.

[0079] Step S1233: Compare the transmission protocol type and transmission encryption method of the two service interfaces, analyze the feasibility of the transmission protocol conversion and the compatibility of the encryption method. If there is a feasible conversion method and the encryption method is compatible, then it is determined that the two service interfaces have the possibility of interaction at the transmission layer.

[0080] The video content distribution platform service interface uses a text-based protocol and symmetric encryption, while the content creation tool service interface uses a binary-based protocol and asymmetric encryption. Analysis revealed a feasible method for converting between the text-based and binary-based protocols, and that symmetric and asymmetric encryption can be compatible through key conversion. Therefore, it was determined that these two service interfaces have the potential to interact at the transmission layer.

[0081] Both the video content distribution platform service interface and the user interaction community service interface adopt text-based protocols and symmetric encryption. The transmission protocol does not need to be converted and the encryption method is compatible, thus enabling interaction at the transmission level.

[0082] The content creation tool service interface uses a binary-based protocol and asymmetric encryption, while the user interaction community service interface uses a text-based protocol and symmetric encryption. Analysis reveals the existence of protocol conversion methods, and the encryption methods can also achieve compatibility through corresponding conversions, thus indicating the possibility of interaction at the transmission layer.

[0083] Step S1234: Compare the call parameter requirements and return value formats of the two service interfaces to determine the degree of matching between the parameters and the return values. If the call parameters can meet the mutual requirements through conversion and the return value formats can be mutually recognized, then it is determined that the two service interfaces have the possibility of interaction at the function call level.

[0084] Among the call parameter requirements of the video content distribution platform service interface and the content creation tool service interface, some parameters can meet each other's requirements through format conversion, and the return value format can be recognized by the other party after parsing. Therefore, it is determined that there is a possibility of interaction at the function call level.

[0085] After analysis, the call parameters and return value formats of the video content distribution platform service interface and the user interaction community service interface were determined to be able to be matched and identified through conversion and parsing, and thus have the potential for interaction at the function call level.

[0086] The call parameters and return value formats of the content creation tool service interface and the user interaction community service interface were also analyzed and found to be interactive through conversion and recognition, thus indicating the possibility of interaction at the function call level.

[0087] Step S1235: Based on the results of the interaction probability judgment at the field level, transmission level, and function call level, determine the global interaction probability between the two service interfaces.

[0088] Based on the above three levels of assessment, the video content distribution platform service interface and the content creation tool service interface have the potential to interact at all three levels, thus confirming the possibility of global interaction between the two.

[0089] The video content distribution platform service interface and the user interaction community service interface also have the possibility of interaction at all three levels, and there is the possibility of global interaction.

[0090] After comprehensive evaluation, the content creation tool service interface and the user interaction community service interface also have the potential for global interaction.

[0091] Step S1236: Analyze the transmission rate limit information and error code definition information of the two service interfaces to determine the possible transmission rate bottlenecks and error handling conflicts during the interaction process, which will serve as interaction constraints.

[0092] The transmission rate range of the video content distribution platform service interface differs from that of the content creation tool service interface. When a large amount of data is exchanged simultaneously, a transmission rate mismatch may occur, creating a bottleneck. Furthermore, their error code definitions differ, potentially leading to error recognition conflicts during interaction. These factors constitute limitations on their interaction.

[0093] The transmission rate ranges of the video content distribution platform service interface and the user interaction community service interface also differ, which may lead to rate bottlenecks. Furthermore, different error code definitions may cause error handling conflicts, becoming a limiting condition for interaction.

[0094] The content creation tool service interface and the user interaction community service interface also suffer from bottlenecks caused by mismatched transmission rates and error code conflicts, which serve as limitations on interaction.

[0095] Step S1237: Based on the global interaction possibility and interaction constraints, determine the interaction triggering conditions between the two service interfaces. The interaction triggering conditions include data update triggering, time-based triggering, and event-driven triggering.

[0096] For the video content distribution platform service interface and the content creation tool service interface, when the content creation tool service completes video production and updates video data, the interaction between the two is triggered, i.e., data update trigger; at the same time, data synchronization is set at a fixed time every day, i.e., time-based trigger; when the content creation tool service adds specific effects, the interaction is also triggered, i.e., event-driven trigger.

[0097] The video content distribution platform service interface and the user interaction community service interface are interconnected. When the comment or like data in the user interaction community is updated, an interaction is triggered. Data is synchronized once per hour, which is time-based triggering. When the number of likes a user gives to a video reaches a certain threshold, an interaction is triggered, which is event-driven triggering.

[0098] The content creation tool service interface and the user interaction community service interface are triggered as follows: when the project data of the creation tool is updated, data interaction is triggered at a fixed time every day, i.e., time-based triggering; when a user mentions a creation project in the community, interaction is triggered, i.e., event-driven triggering.

[0099] Step S1238: Determine the data exchange type between the two service interfaces based on the field definition information and the call parameter requirements. The data exchange type includes basic information exchange, business data exchange, and control command exchange.

[0100] The video content distribution platform service interface and the content creation tool service interface exchange basic metadata (i.e., basic information exchange) based on the definition information of fields such as "video identifier" and "project identifier" and related calling parameter requirements; exchange data such as material usage and editing progress during the video production process (i.e., business data exchange); and transmit video publishing instructions, modification instructions, etc. (i.e., control instruction exchange).

[0101] The video content distribution platform service interface and the user interaction community service interface exchange basic user information and basic video information, i.e., basic information exchange; they also exchange user comment content and like statistics, i.e., business data exchange; and they transmit video recommendation instructions and comment hiding instructions, i.e., control instruction exchange.

[0102] The content creation tool service interface and the user interaction community service interface exchange basic project information, basic user information, etc., i.e., basic information exchange; exchange user feedback data and material usage suggestions for the project, i.e., business data exchange; and transmit project collaboration instructions and material sharing instructions, i.e., control instruction exchange.

[0103] Step S1239: Combining the transmission rate limit information and the response requirements of the function call, set the response timeliness requirements between the two service interfaces. The response timeliness requirements include the maximum response time and the number of timeout retries.

[0104] Between the video content distribution platform service interface and the content creation tool service interface, a maximum response time is set to a certain duration based on the transmission rate limitations of both and the response speed requirements when calling functions, and the number of times to retry after timeout is set to a certain number.

[0105] Between the video content distribution platform service interface and the user interaction community service interface, a maximum response time is set to another duration, and the number of retries after timeout is set to a certain number.

[0106] Between the content creation tool service interface and the user interaction community service interface, a maximum response time is set to the corresponding duration, and the number of retries after timeout is set to the corresponding number.

[0107] Step S12310: Perform the above analysis on each pair of service interfaces for all different scenarios, and compile the interaction triggering conditions, data exchange types and response time requirements between service interfaces for each scenario. Then, classify and summarize the results according to the scenario category of the service interface to generate an interface interaction requirement list.

[0108] The analysis results between the video content distribution platform service interface and the content creation tool service interface, as well as the analysis results between the content creation tool service interface and the user interaction community service interface, were compiled. The results were then categorized into three scenarios: video content distribution platform, content creation tool service, and user interaction community service. The interaction trigger conditions, data exchange types, and response time requirements between each scenario and other scenarios were clearly listed, forming an interface interaction requirement list.

[0109] Step S130: Generate an interface adaptation rule set based on the interface interaction requirement list. The interface adaptation rule set includes format adaptation rules for unifying the interaction format of service interfaces in various scenarios, transmission adaptation rules for coordinating data transmission methods, and call adaptation rules for standardizing function call processes.

[0110] Based on the generated list of interface interaction requirements, format adaptation rules, transmission adaptation rules, and invocation adaptation rules are constructed for the interaction triggering conditions, data exchange types, response time requirements, etc., and then integrated into an interface adaptation rule set.

[0111] Step S131: Classify and statistically analyze the data exchange types in the interface interaction requirement list, determine the interaction format features corresponding to different data exchange types, and construct format adaptation rules based on the interaction format features. The interaction format features include the required fields of data fields, the field length range, and the field association relationship. The format adaptation rules include mapping rules that map field definition information of different interaction formats to unified field definitions, conversion rules that convert different field type information to standard field types, and sorting rules that adjust the arrangement order of different fields to the standard arrangement order.

[0112] The three data exchange types in the interface interaction requirement list—basic information exchange, business data exchange, and control command exchange—are categorized and statistically analyzed. The number of times each type appears and the fields involved are recorded.

[0113] Step S1311: Traverse all data exchange types in the interface interaction requirement list, count the frequency of each data exchange type, sort them from high to low frequency, and determine the primary and secondary data exchange types.

[0114] By reviewing the list of interface interaction requirements, it was found that basic information exchange occurred most frequently, followed by business data exchange, and control command exchange occurred least frequently. Therefore, basic information exchange was determined to be the primary data exchange type, while business data exchange and control command exchange were determined to be secondary data exchange types.

[0115] Step S1312: For each data exchange type, extract the corresponding interaction format information, analyze the required fields of the data fields, and generate the required fields of the data fields.

[0116] For basic information exchange types, the corresponding interaction format information is extracted. Analysis reveals that fields such as "video identifier," "user identifier," and "project identifier" are mandatory, while other fields are optional. Corresponding mandatory field requirements are then generated.

[0117] For business data exchange types, the analysis revealed that fields such as "material usage record", "comment content", and "number of likes" are mandatory fields, and corresponding mandatory field requirements were generated.

[0118] For control command exchange types, fields such as "command type" and "target identifier" are required, and corresponding required field requirements are generated.

[0119] Step S1313: Measure the length values ​​of each data field, determine the minimum and maximum length values ​​of each field, and obtain the field length range.

[0120] For the "Video Identifier" field in basic information exchange, its length is measured in different interaction scenarios to determine the minimum and maximum length values, thus obtaining the length range of this field. The same method is applied to various fields in other data exchange types to determine the length range of each field.

[0121] Step S1314: Analyze the dependencies between different data fields and determine the field associations.

[0122] In basic information exchange, analysis revealed that the "video title" depends on the "video identifier" for its existence; that is, the "video title" field only exists if the "video identifier" field is present, thus establishing the relationship between the two. In business data exchange, "comment content" depends on both the "user identifier" and the "video identifier," establishing the relationship between them. In control command exchange, "command parameters" depend on the "command type," establishing the relationship between the two.

[0123] Step S1315: Integrate the required fields, field length ranges, and field relationships of the data fields to generate interactive format features corresponding to different data exchange types.

[0124] The mandatory field requirements, length ranges, and relationships between fields for basic information exchange are integrated to form the corresponding interaction format features for basic information exchange. Similarly, relevant information for business data exchange and control command exchange is integrated to generate their respective corresponding interaction format features.

[0125] Step S1316: Collect field definition information of service interfaces for each scenario, establish a field definition mapping table, map fields with different names but the same meaning to a unified field name and meaning, and construct a mapping rule to map field definition information of different interaction formats to a unified field definition.

[0126] We collected field definitions from the video content distribution platform service interface ("Video Identifier"), the content creation tool service interface ("Project-Associated Video ID"), and the user interaction community service interface ("Associated Video Number"). We found that they have the same meaning, only different names. We established a field definition mapping table to uniformly map these fields to a "Unified Video Identifier," meaning a unique identifier for a video, and constructed corresponding mapping rules.

[0127] For other fields with the same meaning but different names, such as "User ID" and "User Number", a mapping table is also created, and mapping rules are constructed.

[0128] Step S1317: Analyze the field type information of the service interfaces in each scenario, refer to the common data type standards, establish a field type conversion comparison table, determine the methods for converting different field types to standard field types, and construct conversion rules to convert different field type information to standard field types.

[0129] Analyze the field type information of each service interface, referring to common data type standards such as string, integer, and date / time. For the "Special Effects Type" enumeration field in the content creation tool service interface, establish a field type conversion table and convert it to a standard string type. The conversion method is to use the text description corresponding to the enumeration value as the string content. For other field types, such as date / time types in different formats, convert them to standard date / time types, determine the corresponding conversion methods, and construct conversion rules.

[0130] Step S1318: Analyze the field arrangement order of the service interfaces in each scenario, and determine the standard field arrangement order based on the efficiency and readability requirements of data exchange. Establish arrangement order adjustment rules, specify the steps for adjusting different arrangement orders to the standard arrangement order, and construct sorting rules to adjust different field arrangement orders to the standard arrangement order.

[0131] Analyzing the field arrangement order of the three service interfaces, and considering the efficiency and readability requirements during data exchange, the standard field arrangement order is determined as follows: first, basic identification fields (such as "unified video identifier" and "unified user identifier"), then basic attribute fields (such as "title" and "time"), then business data fields, and finally control fields.

[0132] The steps to adjust the original order of "Video Identifier," "Video Title," and "Publish Time" in the video content distribution platform service interface to the standard order are as follows: keep the position of "Video Identifier" (corresponding to "Unified Video Identifier") unchanged, and arrange the other fields in the standard order. Corresponding adjustment steps and sorting rules have also been formulated for the order of other service interfaces.

[0133] Step S1319: Integrate the mapping rules, the conversion rules, and the sorting rules to generate format adaptation rules.

[0134] The constructed mapping rules, transformation rules, and sorting rules are integrated together to form a complete format adaptation rule, which is used to unify the interaction format of service interfaces in different scenarios.

[0135] Step S132: Perform compatibility analysis on the transmission protocol type, transmission encryption method and transmission rate limit information in the interface interaction requirement list, determine the compatibility degree and conversion conditions between each transmission method, and construct transmission adaptation rules based on the compatibility degree and conversion conditions. The transmission adaptation rules include protocol conversion rules for converting different transmission protocol types into a general transmission protocol, encryption conversion rules for adjusting different transmission encryption methods into a unified encryption method, and bandwidth allocation rules for allocating transmission bandwidth according to the transmission rate limit information.

[0136] Analyze the transmission-related information in the interface interaction requirement list to determine the conversion conditions of transmission protocols and encryption methods, and then construct transmission adaptation rules.

[0137] For example, step S1321: Collect the transmission protocol types of all service interfaces in the interface interaction requirement list, establish a transmission protocol type list, and analyze the communication principle and data format of each transmission protocol.

[0138] Collect text-based protocols for video content distribution platform service interfaces, binary protocols for content creation tool service interfaces, and text-based protocols for user interaction community service interfaces, and establish a list of transmission protocol types.

[0139] Text-based protocols communicate by transmitting data through text strings, with the data format being a readable sequence of characters, such as using specific delimiters to separate fields. Binary-based protocols, on the other hand, transmit information through blocks of binary data, communicating by parsing data according to a predefined byte structure, with the data format being a combination of byte streams.

[0140] Step S1322: Select two different transmission protocol types, determine the compatibility between each transmission protocol type through simulated communication tests, analyze the hardware support, software plug-ins and conversion algorithms required to realize protocol conversion for the combination of transmission protocol types with a set degree range of compatibility matching, and determine the protocol conversion conditions, which include the required conversion tools and conversion steps.

[0141] Simulated communication tests were conducted using both text-based and binary-based protocols, sending the same data and observing the receiver's parsing behavior. The tests revealed that the compatibility between the two protocols was within a moderate range.

[0142] The analysis focuses on the conversion tools required to achieve these two protocol conversions, such as protocol conversion plugins. The conversion steps are: first, parse the text-based protocol data into an intermediate data structure, and then convert the intermediate data structure into a binary-based protocol data format, or vice versa. These are determined as the conditions for protocol conversion.

[0143] Step S1323: Analyze the transmission encryption methods in the interface interaction requirement list to obtain the encryption algorithm, key management method and security level of each encryption method.

[0144] The analysis revealed that the symmetric encryption method used in the video content distribution platform service interface and the user interaction community service interface is a specific symmetric encryption algorithm. The key management method involves unified distribution and updating through a key server, and the security level is medium.

[0145] The content creation tool service interface uses asymmetric encryption, employing a specific asymmetric encryption algorithm. Key management involves locally generating public and private keys, with the public key being publicly distributed, resulting in a high level of security.

[0146] Step S1324: Compare the encryption and decryption processes of different transmission encryption methods, determine the compatibility between encryption methods, locate incompatible encryption method combinations based on the compatibility, and analyze the key conversion method and algorithm adjustment steps required to convert one encryption method to another as encryption conversion conditions.

[0147] Comparing the encryption and decryption processes of symmetric and asymmetric encryption, symmetric encryption uses a single key for encryption and decryption, while asymmetric encryption uses a public key for encryption and a private key for decryption. The compatibility between the two is determined to be low.

[0148] The key conversion method for transforming symmetric encryption into asymmetric encryption is as follows: The symmetric encryption key is encrypted using the public key of the asymmetric encryption algorithm and used as the transmission key. The algorithm adjustment steps are: first, the data is encrypted using the symmetric encryption algorithm, and then the symmetric key is encrypted using the public key. The method and steps for transforming asymmetric encryption into symmetric encryption are the reverse; these are the conditions for encryption conversion.

[0149] Step S1325: Extract the transmission rate limit information from the interface interaction requirement list, count the upper and lower limits of the transmission rate of different service interfaces, and analyze the possible rate conflicts when multiple interfaces interact simultaneously.

[0150] The transmission rate limit information of the three service interfaces was extracted, and the upper and lower limits of the transmission rate of the video content distribution platform service interface, the content creation tool service interface, and the user interaction community service interface were statistically determined.

[0151] Analysis revealed that when the three interfaces are simultaneously exchanging a large amount of data, the higher transmission rate of the content creation tool service interface may conflict with the rates of the other two interfaces, leading to data transmission congestion.

[0152] Step S1326: Based on the compatibility and conversion conditions between various transmission methods, select the transmission protocol that meets the first set condition as the general transmission protocol, and construct a protocol conversion rule to convert different transmission protocol types into the general transmission protocol. The protocol conversion rule includes the tools, steps and verification methods required for the conversion.

[0153] The primary condition is that, under existing conversion conditions, the conversion is relatively easy, efficient, and widely applicable. Based on this, a text-based protocol is selected as the universal transmission protocol.

[0154] In the protocol conversion rules, the conversion tool is a protocol conversion plugin; for binary-based protocol data, the conversion steps first parse it into an intermediate text format through the plugin, and then adjust it according to the format specifications of the general transmission protocol; the verification method is to perform integrity verification on the converted data to ensure that the data content is consistent with that before conversion.

[0155] Step S1327: Select an encryption method that meets the second set condition as the unified encryption method, and construct an encryption conversion rule to adjust different transmission encryption methods to a unified encryption method. The encryption conversion rule includes a key conversion process, a replacement step for the encryption algorithm, and a verification standard for encryption strength.

[0156] The second condition is that the security level meets the requirements and key management is convenient. Symmetric encryption is chosen as the unified encryption method.

[0157] In the encryption conversion rules, the key conversion process is as follows: When converting from asymmetric encryption to symmetric encryption, the receiver generates a symmetric key and decrypts the symmetric key encrypted by the sender using its own private key, thus completing the key exchange; the encryption algorithm replacement step is to stop using the asymmetric encryption algorithm and switch to a symmetric encryption algorithm; the encryption strength verification standard is to ensure that the encryption strength after conversion is not lower than the strength of the original asymmetric encryption by using a specific encryption strength testing tool.

[0158] Step S1328: Based on the transmission rate limiting information and the rate conflict analysis results of multi-interface interaction, construct a bandwidth allocation rule for allocating transmission bandwidth according to the transmission rate limiting information. The bandwidth allocation rule includes an allocation strategy based on rate priority, triggering conditions for dynamic bandwidth adjustment, and an evaluation method for allocation results.

[0159] Based on the transmission rate limitation information and rate conflict analysis results, the bandwidth allocation rule is based on the rate priority allocation strategy as follows: the content creation tool service interface has the highest priority due to its large data transmission volume and high real-time requirements; the video content distribution platform service interface has the second highest priority; and the user interaction community service interface has the lowest priority.

[0160] The trigger condition for dynamic bandwidth adjustment is: when the transmission rate of a certain interface is lower than a certain percentage of its lower limit for a continuous period of time, bandwidth adjustment is triggered.

[0161] The evaluation method for the allocation results is as follows: monitor the actual transmission rate of each interface after bandwidth allocation, compare it with its respective rate limit range, and evaluate whether the requirements are met.

[0162] Step S1329: Integrate the protocol conversion rule, the encryption conversion rule, and the bandwidth allocation rule to generate a transmission adaptation rule.

[0163] By integrating protocol conversion rules, encryption conversion rules, and bandwidth allocation rules, a transmission adaptation rule is formed, which is used to coordinate the data transmission methods of service interfaces in different scenarios.

[0164] Step S133: Perform process analysis on the interaction triggering conditions, call parameter requirements, return value format and error code definition information in the interface interaction requirement list, and construct a time sequence diagram of function calls.

[0165] Based on the interaction triggering conditions in the interface interaction requirement list, such as data update triggering, time-based triggering, and event-driven triggering, and combined with the call parameter requirements, return value format, and error code definition information, draw a sequence diagram of function calls.

[0166] The sequence diagram clearly defines the calling order, parameter passing path, return value feedback process, and error handling response order of each service interface under different triggering conditions.

[0167] In scenarios triggered by data updates, once the content creation tool service interface completes the video material update, it can generate update notification data containing "project identifier," "update time," and "material change type." This update notification data is transmitted to the transmission adaptation layer of the standardized interface interaction module according to a preset transmission path. After protocol conversion and encryption, it is forwarded to the video content distribution platform service interface. Upon receiving the data, the video content distribution platform service interface parses the video information corresponding to the "project identifier" according to the call parameter requirements and calls its own "content update detection" function to verify the material change content. The verification result is packaged in a return value format, containing fields such as "verification status," "update necessity identifier," and "processing suggestions," and sent back to the content creation tool service interface. If a data transmission timeout occurs during the process, the "timeout error identifier" in the error code definition information will be triggered. The error description is "data update notification transmission timeout," and the error level corresponds to the set level. At this time, the retry mechanism is triggered according to the error handling process.

[0168] In time-triggered scenarios, at a fixed daily time, the user interaction community service interface sends user behavior statistics to the video content distribution platform service interface. Before sending, the user interaction community service interface organizes parameters such as "statistical period," "user behavior type," and "data volume" according to the call parameter requirements, and encapsulates them into a data packet conforming to transmission specifications. This data packet is then converted to a transmission format supported by the video content distribution platform service interface through the transmission adaptation layer of the standardized interface interaction module before being sent. Upon receiving the data, the video content distribution platform service interface invokes the "data integration and analysis" function to process the data. The processing result is returned to the user interaction community service interface in a return value format containing "analysis completion indicator," "popular content indicator," and "user preference trend." If a parameter format error occurs during processing, the corresponding error code is activated, and the error message is transmitted according to the defined format, triggering a parameter retransmission process.

[0169] In an event-driven scenario, when the content creation tool service interface completes the production of a video project and marks it as "ready to publish," it automatically triggers a push request to the video content distribution platform service interface. The content creation tool service interface initiates the call according to the required parameters, including "project identifier," "video format information," and "publishing permission identifier." Upon receiving the request, the video content distribution platform service interface invokes the "publishing review" function. After approval, it sends a "new content launch notification" to the user interaction community service interface. Upon receiving the notification, the user interaction community service interface invokes the "community display update" function to update the recommendation list. Throughout this process, the return values ​​from each stage are transmitted according to a predefined format. If an insufficient permission error occurs, the corresponding error code and description information are transmitted between the relevant interfaces, triggering the permission verification process.

[0170] Through the above process analysis under different interactive triggering conditions, the timing relationships of the call order, parameter passing, return value feedback and error handling of each service interface are presented in a graphical way, and a timing relationship diagram of function call is constructed.

[0171] Step S134: Construct call adaptation rules based on the timing relationship diagram. The call adaptation rules include order rules for determining the call order based on the interaction triggering conditions, parameter conversion rules for converting different call parameter requirements into a standard parameter set, return value processing rules for unifying different return value formats into a standard return format, and error code mapping rules for mapping different error code definitions to standard error codes.

[0172] The sequence rules are based on the call flow under different interactive trigger conditions in the time sequence diagram. When data update is triggered, the call order is as follows: the content creation tool service interface first initiates a "data update notification" call, the video content distribution platform service interface responds and returns a verification result, and then decides whether to proceed with the subsequent "content synchronization" call based on the verification result. When time-based triggering is triggered, the call order is as follows: the user interaction community service interface initiates a "statistical data sending" call, the video content distribution platform service interface performs a "data processing" call and returns a result. When event-driven triggering is triggered, the call order is as follows: the content creation tool service interface initiates a "publish request" call, the video content distribution platform service interface performs a "review" call, and after the review is passed, a "notification" call is triggered to the user interaction community service interface, which then performs a "display update" call.

[0173] Parameter conversion rules are established to meet the parameter requirements of different service interfaces. Parameters such as the "query conditions" parameter of the video content distribution platform service interface, the "material address" parameter of the content creation tool service interface, and the "user identifier" parameter of the user interaction community service interface are uniformly converted into a standard parameter set containing "parameter category," "parameter value," "data type identifier," and "validation rules." For example, the "material path" parameter of the content creation tool service interface is converted into a "resource location parameter" in the standard parameter set, retaining the original path information for the parameter value, corresponding to a string type for the data type identifier, and undergoing path format validation for the validation rule; the "comment content" parameter of the user interaction community service interface is converted into a "text content parameter," with the parameter value being the comment text, the data type identifier corresponding to a string type, and content specification validation for the validation rule.

[0174] The return value processing rules unify the return value format of all service interfaces into a standard return format that includes a "processing status identifier," a "result data area," and an "additional information area." In the "video query" result returned by the video content distribution platform service interface, fields such as "video identifier" and "video title" are placed in the "result data area" of the standard return format, and "query time" is placed in the "additional information area." In the "effects addition" result of the content creation tool service interface, "addition result" is placed in the "processing status identifier," "project update time" is placed in the "additional information area," and "effect parameter details" are placed in the "result data area."

[0175] The error code mapping rules map the error code definitions of each service interface to unified standard error codes. The "timeout error identifier" of the video content distribution platform service interface is mapped to "transmission error 001" in the standard error code set; the "parameter error identifier" of the content creation tool service interface is mapped to "parameter error 002"; and the "permission error identifier" of the user interaction community service interface is mapped to "permission error 003". Simultaneously, error descriptions are also uniformly converted to a standard format including "error scenario," "specific reason," and "handling suggestions," and error levels are converted according to a set unified level system.

[0176] Step S135: Integrate the format adaptation rules, transmission adaptation rules and invocation adaptation rules to generate an interface adaptation rule set.

[0177] The rules are summarized as follows: mapping rules, conversion rules, and sorting rules in the format adaptation rules; protocol conversion rules, encryption conversion rules, and bandwidth allocation rules in the transmission adaptation rules; and order rules, parameter conversion rules, return value processing rules, and error code mapping rules in the call adaptation rules. A rule association table is established to clarify the application scenarios and call order of different rules in the interaction process. For example, in an interaction triggered by a data update, the field mapping and conversion in the format adaptation rules are applied first, then the protocol and encryption conversion are performed using the transmission adaptation rules, and finally, the function call is executed according to the order and parameter conversion rules in the call adaptation rules. All rules undergo compatibility checks to ensure that the application of different rules does not conflict in the same interaction scenario. After verification, these rules are combined into a complete set, namely the interface adaptation rule set.

[0178] Step S140: Perform adaptation processing on the service interfaces of each scenario according to the interface adaptation rule set to obtain a standardized interface interaction module. The standardized interface interaction module is compatible with the interaction format, data transmission method and function call specifications of the service interfaces of each scenario.

[0179] In this embodiment, based on the previously generated interface adaptation rule set, the service interfaces of the video content distribution platform, content creation tool service, and user interaction community service are adapted accordingly. The adaptation process adjusts and unifies the interface's interaction format, data transmission method, and function call specifications according to the rules in the rule set, thereby achieving seamless integration between service interfaces in different scenarios.

[0180] Step S141: Call the format adaptation rules in the interface adaptation rule set to perform format conversion processing on the interaction format information of each scenario service interface, and convert the field definition information, field type information and field arrangement order information of each service interface into a unified standard interaction format to obtain the format-adapted service interface information.

[0181] For the "Video Identifier" field in the video content distribution platform service interface, it is mapped to the standard field "Resource Unique Identifier" according to the mapping rules in the format adaptation rules to ensure consistency in name and meaning. In the field type information, the original "Video Identifier" was a string with a fixed length of several characters. This has been converted to the corresponding string type in the standard field type, with the length adjusted according to the standard range to meet the requirements of the standard field type. Regarding the field arrangement order, the original order of "Video Identifier," "Video Title," and "Publish Time" in the interface has been adjusted to the standard order of "Resource Unique Identifier," "Resource Name," and "Creation Time."

[0182] The "Project Identifier" field of the content creation tool service interface is mapped to the standard field "Unique Identifier of Production Project". The field type is converted to the standard string type, the length is adjusted to the standard range, and the field arrangement order is reordered according to standard rules. Fields such as "Unique Identifier of Production Project", "Source Path of Material", and "Special Effect Application Type" are arranged in standard order.

[0183] The "User Identifier" in the user interaction community service interface is mapped to the standard field "User Unique Identifier". The field type is converted to the standard string type, the length meets the standard requirements, and the field order is adjusted to the standard order of "User Unique Identifier", "Interaction Content", and "Number of Interaction Behaviors".

[0184] After the above format conversion process, the interaction format of each service interface is unified into the standard interaction format, forming the service interface information after format adaptation.

[0185] Step S142: Apply the transmission adaptation rules in the interface adaptation rule set to perform transmission coordination processing on the data transmission method information in the format-adapted service interface information, convert the transmission protocol type of each service interface to a general transmission protocol, adjust the transmission encryption method to a unified encryption method, and allocate transmission bandwidth according to the transmission rate limit information to obtain the transmission-adapted service interface information.

[0186] The video content distribution platform's service interface originally used a text-based protocol. Following the protocol conversion rules in the transmission adaptation guidelines, it was converted to a general transmission protocol. During the conversion, the text-based protocol data was encapsulated according to the data frame format of the general transmission protocol, adding frame headers, frame trailers, and verification fields. The original symmetric encryption method was adjusted to a unified encryption method according to the encryption conversion rules. By generating a key that conforms to the requirements of the unified encryption method, the original symmetric encryption key was converted to a new key format, and the data encryption process was adjusted to meet the algorithm requirements of the unified encryption method.

[0187] The content creation tool service interface originally used a binary-based protocol. When converting to a universal transmission protocol, the binary data was encoded according to the encoding method of the universal transmission protocol to enable its transmission. The original asymmetric encryption method was adjusted to a unified encryption method. Through key conversion, the public and private keys were converted into the key form required by the unified encryption method, and the parameter settings of the encryption algorithm were adjusted to achieve a unified encryption method.

[0188] The user interaction community service interface was converted from a text-based protocol to a universal transmission protocol, and the symmetric encryption method was changed to a unified encryption method. The conversion process was similar to that of the video content distribution platform service interface.

[0189] Regarding bandwidth allocation, based on the transmission rate limits of each service interface, the upper and lower limits of the transmission rate of the video content distribution platform service interface, and considering the rate limits of the content creation tool service interface and the user interaction community service interface, a larger proportion of bandwidth is allocated to the video content distribution platform service interface to meet its needs for transmitting large amounts of video content; a medium proportion of bandwidth is allocated to the content creation tool service interface to accommodate the transmission of materials and project files; and an appropriate proportion of bandwidth is allocated to the user interaction community service interface to meet the transmission of user interaction data. Thus, after transmission coordination processing, the service interface information after transmission adaptation is obtained.

[0190] Step S143: Using the call adaptation rules in the interface adaptation rule set, perform call specification processing on the function call specification information in the service interface information after transmission adaptation, determine the call order according to the interaction triggering conditions, convert the call parameter requirements into a standard parameter set, unify the return value format into a standard return format, and map the error code definition to a standard error code to obtain the service interface information after call adaptation.

[0191] When the interaction is triggered by a data update, the order in which the content creation tool service interface calls the video content distribution platform service interface is determined according to the order rules in the call adaptation rules. The original call parameters "Project Identifier" and "Material Change Information" of the content creation tool service interface are converted to the "Unique Identifier of Production Project" and "Resource Change Details" parameters in the standard parameter set, with the parameter types and quantities adjusted according to the requirements of the standard parameter set. In the return value format, the original "Import Status" and "Material ID" are converted to the "Operation Execution Status" and "Resource Identifier" fields in the standard return format, ensuring consistency in structure and data type. The original error code "F201" (Invalid Material Address) is mapped to the standard error code "Resource Path Error," and the error description is converted to "Invalid resource source path, operation cannot be performed" in the standard format, with the error level corresponding to the corresponding level of the standard error level.

[0192] When the timed event is triggered, the user interaction community service interface calls the video content distribution platform service interface first, following a sequential rule. The call parameters "statistical period" and "user behavior type" are converted to "data statistical time range" and "user interaction behavior category" in the standard parameter set. The original "analysis completion identifier" and "popular content identifier" in the return value format are converted to "data processing status" and "high-attention resource identifier." The error code "statistical data format error" is mapped to the standard error code "parameter format mismatch," and error messages are converted according to the standard format.

[0193] When an event-driven event is triggered, the content creation tool service interface calls the video content distribution platform service interface according to a sequential rule, which in turn calls the user interaction community service interface. The call parameters and return value formats are converted according to standard parameter sets and standard return formats, and error codes are also mapped to corresponding standard error codes. Through this call specification processing, the adapted service interface information is obtained.

[0194] Step S1431: Deploy the format-adapted service interface information, the transmission-adapted service interface information, and the call-adapted service interface information to the corresponding layers of the framework structure to obtain a standardized interface interaction module that is compatible with the interaction format, data transmission method, and function call specifications of service interfaces in various scenarios.

[0195] The format-adapted service interface information is deployed to the format adaptation layer of the standardized interface interaction module framework. This layer sets up a field mapping table, a type conversion lookup table, and a sorting rule execution unit. When data enters, these components are automatically invoked to process the data interaction format, ensuring that it conforms to the standard interaction format.

[0196] The adapted service interface information is deployed to the transport adaptation layer, which includes a protocol conversion tool, an encryption conversion unit, and a bandwidth allocation controller. The protocol conversion tool is responsible for converting different transport protocols into a common transport protocol, the encryption conversion unit performs unified processing of encryption methods, and the bandwidth allocation controller dynamically allocates transport bandwidth according to set rules.

[0197] The adapted service interface information is deployed to the call adaptation layer, which includes a sequence rule executor, a parameter conversion unit, a return value processing unit, and an error code mapping unit. The sequence rule executor coordinates the calls to each service interface according to the set call order, the parameter conversion unit converts the call parameters into a standard parameter set, the return value processing unit standardizes the format of the returned data, and the error code mapping unit converts error codes into standard error codes.

[0198] Data is transferred between different layers through an internal communication mechanism. Data processed by the format adaptation layer is passed to the transport adaptation layer, processed by the transport adaptation layer, and then passed to the call adaptation layer. Data processed by the call adaptation layer is used for interaction between service interfaces. Through this deployment, a standardized interface interaction module is formed that is compatible with the interaction format, data transmission method, and function call specifications of service interfaces in various scenarios.

[0199] Step S150: Construct a cross-scenario service interaction protocol through the standardized interface interaction module. The cross-scenario service interaction protocol is used to guide service interfaces in different scenarios to realize data interaction and function calls through the standardized interface interaction module.

[0200] Once the standardized interface interaction module is built, a cross-scenario service interaction protocol is constructed based on the processing rules and specifications at each level in the module, in order to standardize the interaction behavior between service interfaces in different scenarios.

[0201] Step S151: Extract the standard interaction format information of the format adaptation layer in the standardized interface interaction module, and determine the data field exchange specification for cross-scenario service interaction. The data field exchange specification includes the mandatory field requirements, field type restrictions, and field transmission order.

[0202] From the standard interaction format information extracted from the format adaptation layer, "resource unique identifier", "resource name" and "creation time" are determined to be mandatory fields for cross-scenario data interaction. These fields must be included in any data exchange process and cannot be omitted.

[0203] Regarding field type restrictions, "Resource Unique Identifier" is restricted to a string type, and the character composition must conform to specific rules; "Resource Name" is a string type, and the character length is between the minimum and maximum number of characters; "Creation Time" is a date and time type, and the format must conform to the set standard format.

[0204] The order in which fields are passed is determined according to the standard arrangement in the format adaptation layer. When interacting with data across different scenarios, the fields are passed in the order of “resource unique identifier”, “resource name”, and “creation time”.

[0205] Step S152: Obtain the general transmission protocol information, unified encryption method information and transmission bandwidth allocation rules of the transmission adaptation layer in the standardized interface interaction module, and construct the data transmission specification for cross-scenario service interaction. The data transmission specification includes the selection criteria for the transmission protocol, the application method of the encryption algorithm and the execution criteria for bandwidth allocation.

[0206] The selection criteria for the transmission protocol are set to prioritize the use of the general transmission protocol in the standardized interface interaction module. When the general transmission protocol cannot meet the special needs of a specific scenario, a protocol compatibility assessment is required. If the assessment is passed, other protocols can be used, but they need to be converted through the transmission adaptation layer.

[0207] The application of encryption algorithms stipulates that data must be encrypted using a unified encryption method within the transport adaptation layer before transmission. During encryption, the generation, distribution, and updating of keys must adhere to the key management rules of the unified encryption method to ensure the security and consistency of the encryption.

[0208] The bandwidth allocation criteria are based on the transmission bandwidth allocation rules of the transmission adaptation layer, and are dynamically allocated according to the service priority and data transmission volume of each service interface. When multiple service interfaces transmit data simultaneously, services with higher priority receive more bandwidth resources, and services with large data transmission volumes are given appropriate preference in bandwidth allocation to ensure data transmission efficiency.

[0209] Step S153: Invoke the call order rules, standard parameter set information, standard return format information and standard error code information of the call adaptation layer in the standardized interface interaction module to generate the function call specification for cross-scenario service interaction. The function call specification includes the triggering conditions for call initiation, the format requirements for parameter passing, the return value processing flow and the error handling response mechanism.

[0210] The triggering conditions for the call are set according to the call order rules of the call adaptation layer, and are divided into three types: data update trigger, time-based trigger, and event-driven trigger. Each triggering condition corresponds to a specific call initiation time and call object.

[0211] The format requirements for parameter passing must follow the standard parameter set information. All call parameters must be converted to the format in the standard parameter set, including elements such as parameter category, parameter value, data type identifier, and validation rules, to ensure that the parameters can be correctly parsed by the receiver.

[0212] The return value processing procedure stipulates that after receiving the return value, the receiver parses it according to the standard return format information, extracts key information such as "operation execution status" and "resource identifier," and performs subsequent operations based on the status information. If the return value contains an error identifier, the error handling process is initiated.

[0213] The error handling response mechanism is based on standard error codes. When an error occurs, appropriate handling measures are executed according to the error code's level and description. Low-level errors can trigger a retry mechanism, medium-level errors require parameter verification and adjustment, and high-level errors require notifying the relevant interfaces for troubleshooting and repair.

[0214] Step S154: Integrate the data field exchange specification, data transmission specification, and function call specification to construct the main framework of the cross-scenario service interaction protocol. The main framework includes a data exchange part, a transmission part, and a call part.

[0215] In this application scenario within the digital media field, the data exchange component is specifically designed to standardize the interaction of data fields between video content distribution platforms, content creation tool services, and user interaction community services. It clarifies which fields must be transmitted during the interaction, which fields have strict type restrictions, and the order in which these fields are transmitted. For example, when the content creation tool service transmits completed video information to the video content distribution platform, the transmission of fields such as "video identifier" and "video title" must adhere to the specifications outlined here.

[0216] The transmission section focuses on the rules governing data transfer between the three service scenarios. It defines which transmission protocol should be selected in different situations, the specific application of a common transmission protocol in various interaction scenarios, how a unified encryption method ensures data transmission security, and how bandwidth allocation rules function when multiple services are transmitting data simultaneously. For example, when a video content distribution platform simultaneously transmits large amounts of video data to multiple user interaction community services, the transmission specifications will guide how to allocate bandwidth reasonably to avoid transmission congestion.

[0217] The invocation section primarily standardizes the functional invocation process between the three service scenarios. It clarifies various triggering conditions for initiating invocations, such as how to trigger the video content distribution platform to adjust the push priority of a video when a user's "likes" on a video in the user interaction community service reach a certain number; it specifies the format requirements for parameter passing to ensure that parameters passed between different services can be correctly parsed; and it describes the specific process for handling return values, as well as the response mechanism when errors occur during the invocation process.

[0218] Next, the specifications of each part in the main framework are verified for consistency, so that the data field exchange specification and the data transmission specification are consistent during the data transmission process, the data transmission specification and the function call specification are coordinated in terms of call sequence, and the data field exchange specification and the function call specification are matched in terms of parameter passing.

[0219] When checking the consistency between the data field exchange specification and the data transmission specification, attention should be paid to whether the size and format of the data fields match the carrying capacity of the transmission protocol. For example, the format and size of certain large video metadata fields specified in the data field exchange specification must be able to be effectively carried by the general transmission protocol defined in the transmission specification, so that transmission failures do not occur due to excessively large fields or incompatible formats.

[0220] When verifying the consistency between data transmission specifications and function call specifications, it's possible to analyze whether the timing of function calls is compatible with the speed and rhythm of data transmission. For example, if the function call specification stipulates that a call needs to complete multiple data interactions within a short period, the bandwidth allocation and transmission rate settings in the transmission specification must meet these timing requirements to ensure that the call process is not interrupted due to transmission delays.

[0221] When verifying the compatibility of parameter passing between the data field exchange specification and the function call specification, it can be confirmed whether the parameters passed during the function call conform to the field definitions and requirements in the data field exchange specification. For example, the function call specification stipulates that a "user preference" parameter needs to be passed when calling the push function of a video content distribution platform. The field definition, type, etc. of this parameter must be consistent with the relevant provisions in the data field exchange specification to ensure that the video content distribution platform can correctly parse the parameter and execute the corresponding push operation.

[0222] Based on the correlation verification results, the main framework is adjusted and optimized, and conflicting or inconsistent specification content is corrected to obtain a cross-scenario service interaction protocol. This cross-scenario service interaction protocol is used to guide service interfaces in different scenarios to realize data interaction and function calls through standardized interface interaction modules.

[0223] If, during correlation verification, it is found that the length definition of a field in the data field exchange specification exceeds the maximum carrying length of the general transmission protocol in the transmission specification, the length of that field needs to be adjusted to meet the transmission requirements. Alternatively, if it is found that the triggering condition of a call in the function call specification conflicts with the transmission timing in the data transmission specification, the triggering condition or transmission timing should be modified to ensure that the two can work in harmony.

[0224] After the above adjustments and optimizations, the resulting cross-scenario service interaction protocol can effectively guide video content distribution platforms, content production tool services, and user interaction community services to conduct smooth data interaction and function calls through the previously built standardized interface interaction modules, achieving seamless connection between the three scenario services and improving the operational efficiency and synergy of the entire digital media system.

[0225] Figure 2 The diagram illustrates exemplary hardware and software components of a standardized interface system 100 for multi-scenario service interfacing, which can implement the ideas of this application, according to some embodiments of this application. For example, processor 120 can be used in the standardized interface system 100 for multi-scenario service interfacing and to perform the functions in this application.

[0226] For example, the standardized interface system 100 for multi-scenario service interfacing may include a network port 110 connected to a network, one or more processors 120 for executing program instructions, a communication bus 130, and different forms of storage media 140, such as a disk, ROM, or RAM, or any combination thereof. Exemplarily, the standardized interface system 100 for multi-scenario service interfacing may also include program instructions stored in ROM, RAM, or other types of non-transitory storage media, or any combination thereof. The methods of this application can be implemented according to these program instructions. The standardized interface system 100 for multi-scenario service interfacing also includes an I / O interface 150 between the computer and other input / output devices.

[0227] Furthermore, this embodiment of the invention also provides a readable storage medium, wherein computer-executable instructions are preset in the readable storage medium, and when the processor executes the computer-executable instructions, the standardized interface method for multi-scenario service integration described above is implemented.

[0228] It should be noted that, in order to simplify the description of the present invention and thus help to understand one or more embodiments of the invention, multiple features may sometimes be grouped into one embodiment, drawing or description thereof in the foregoing description of the embodiments of the present invention.

Claims

1. A standardized interface method for multi-scenario service integration, characterized in that, The method includes: The service interface information set is obtained from the service registration center of each scenario. The service interface information set includes the interaction format information, data transmission method information and function call specification information of the service interface in each scenario. Based on the service interface information set, the interface interaction requirements are analyzed to obtain an interface interaction requirement list. The interface interaction requirement list includes the interaction trigger conditions, data exchange types and response time requirements between service interfaces in each scenario. An interface adaptation rule set is generated based on the interface interaction requirement list. The interface adaptation rule set includes format adaptation rules for unifying the service interface interaction format in various scenarios, transmission adaptation rules for coordinating data transmission methods, and call adaptation rules for standardizing function call processes. Based on the interface adaptation rule set, the service interfaces of each scenario are adapted to obtain a standardized interface interaction module. The standardized interface interaction module is compatible with the interaction format, data transmission method and function call specification of the service interfaces of each scenario. A cross-scenario service interaction protocol is constructed through the standardized interface interaction module. The cross-scenario service interaction protocol is used to guide service interfaces in different scenarios to realize data interaction and function calls through the standardized interface interaction module. The step of generating an interface adaptation rule set based on the interface interaction requirement list includes: The data exchange types in the interface interaction requirement list are classified and statistically analyzed to determine the interaction format characteristics corresponding to different data exchange types. Based on the interaction format characteristics, format adaptation rules are constructed. The interaction format characteristics include the required fields of data fields, the field length range, and the field association relationship. The format adaptation rules include mapping rules for mapping field definition information of different interaction formats to unified field definitions, conversion rules for converting different field type information to standard field types, and sorting rules for adjusting the arrangement order of different fields to the standard arrangement order. A compatibility analysis is performed on the transmission protocol types, transmission encryption methods, and transmission rate limit information in the interface interaction requirement list to determine the compatibility degree and conversion conditions between each transmission method. Based on the compatibility degree and conversion conditions, transmission adaptation rules are constructed. The transmission adaptation rules include protocol conversion rules for converting different transmission protocol types into a general transmission protocol, encryption conversion rules for adjusting different transmission encryption methods into a unified encryption method, and bandwidth allocation rules for allocating transmission bandwidth according to transmission rate limit information. A process analysis is performed on the interaction triggering conditions, call parameter requirements, return value format and error code definition information in the interface interaction requirement list to construct a time sequence diagram of function calls; Based on the timing relationship diagram, call adaptation rules are constructed. The call adaptation rules include order rules for determining the call order according to the interaction triggering conditions, parameter conversion rules for converting different call parameter requirements into a standard parameter set, return value processing rules for unifying different return value formats into a standard return format, and error code mapping rules for mapping different error code definitions to standard error codes. The format adaptation rules, transmission adaptation rules, and invocation adaptation rules are integrated to generate an interface adaptation rule set.

2. The standardized interface method for multi-scenario service integration according to claim 1, characterized in that, The process of analyzing interface interaction requirements based on the service interface information set yields a list of interface interaction requirements, including: The interaction format information in the service interface information set is parsed and processed to extract the field definition information, field type information and field arrangement order information of each service interface; The data transmission method information in the service interface information set is classified and processed to determine the transmission protocol type, transmission encryption method and transmission rate limit information used by each service interface. In addition, the function call specification information in the service interface information set is analyzed to obtain the call parameter requirements, return value format and error code definition information of each service interface. Based on the extracted field definition information, field type information, field arrangement order information, transmission protocol type, transmission encryption method, transmission rate limit information, call parameter requirements, return value format, and error code definition information, the interaction possibilities and interaction constraints between service interfaces in different scenarios are analyzed, and an interface interaction requirement list containing the interaction trigger conditions, data exchange types, and response time requirements between service interfaces in each scenario is generated.

3. The standardized interface method for multi-scenario service integration according to claim 2, characterized in that, The process of obtaining service interface information sets from service registration centers in various scenarios includes: Access the service registration center of each scenario and send a service interface information query request. The service interface information query request includes the information type identification information to be obtained. The information type identification information corresponds to the interaction format information, data transmission method information and function call specification information. Receive a set of service interface information returned by the service registration center for each scenario. The set of service interface information includes the interaction format information, data transmission method information and function call specification information of the service interfaces in each scenario. The step involves parsing the interaction format information in the service interface information set to extract the field definition information, field type information, and field arrangement order information of each service interface, including: The interaction format information in the service interface information set is structured and parsed to identify the field definition descriptions of each service interface. The names, meanings, and constraints of the fields are extracted from the field definition descriptions as field definition information. Analyze the field type annotations in the interactive format information to determine the data type, length, and value range of each field as field type information; Parse the field arrangement description in the interactive format information to obtain the order of each field in the data transmission process as the field arrangement order information; The extracted field definition information, field type information, and field arrangement order information are associated and stored with the corresponding service interfaces to generate an interaction format feature set.

4. The standardized interface method for multi-scenario service integration according to claim 2, characterized in that, The process involves classifying the data transmission method information in the service interface information set to determine the transmission protocol type, encryption method, and transmission rate limit information used by each service interface. It also involves analyzing the function call specification information in the service interface information set to obtain the call parameter requirements, return value format, and error code definition information for each service interface, including: The data transmission method information in the service interface information set is parsed field by field to extract the content describing the transmission protocol and determine the transmission protocol type used by each service interface. The transmission protocol type includes text-based protocols and binary-based protocols. The description of encryption processing in the data transmission method information is analyzed to identify the transmission encryption method used by each service interface, including symmetric encryption and asymmetric encryption. Extract the transmission rate-related description from the data transmission method information, and determine the upper and lower limits of the transmission rate for each service interface as transmission rate limitation information; Associate the determined transmission protocol type, transmission encryption method, and transmission rate limit information with the corresponding service interface to generate a transmission feature set; The function call specification information in the service interface information set is extracted, and the parameter names, parameter types, parameter quantities and dependencies between parameters required by each service interface are obtained from the call parameter description section as call parameter requirements; The return value description section of the parsing function call specification information is used to determine the structure, data type, and field information of the data returned by each service interface as the return value format; Extract the error handling section from the function call specification information, and obtain the error identifier, error description, and error level defined by each service interface as error code definition information; The obtained call parameter requirements, return value format, and error code definition information are associated with the corresponding service interface to generate a set of function call features.

5. The standardized interface method for multi-scenario service integration according to claim 2, characterized in that, Based on the extracted field definition information, field type information, field arrangement order information, transmission protocol type, transmission encryption method, transmission rate limit information, call parameter requirements, return value format, and error code definition information, the system analyzes the interaction possibilities and constraints between service interfaces in different scenarios, generating an interface interaction requirement list that includes interaction trigger conditions, data exchange types, and response time requirements between service interfaces in each scenario, including: The extracted field definition information, field type information, field arrangement order information, transmission protocol type, transmission encryption method, transmission rate limit information, call parameter requirements, return value format and error code definition information are summarized to establish a feature information database for service interfaces in each scenario. Select two service interfaces from the feature information database for any two different scenarios, compare the field definition information of the two service interfaces to determine the compatibility of the fields, and if the field names and meanings are consistent and the field type information is matched, then it is determined that the two service interfaces have the possibility of interaction at the field level. Compare the transmission protocol types and encryption methods of the two service interfaces, analyze the feasibility of transmission protocol conversion and the compatibility of encryption methods. If there is a feasible conversion method and the encryption methods are compatible, then it is determined that the two service interfaces have the possibility of interaction at the transmission layer. By comparing the call parameter requirements and return value formats of the two service interfaces, the degree of matching between the parameters and return values ​​is determined. If the call parameters can meet each other's requirements through conversion and the return value formats can be mutually recognized, then it is determined that the two service interfaces have the possibility of interaction at the function call level. Based on the results of the interaction probability assessment at the combined field level, transmission level, and function call level, the global interaction probability between the two service interfaces is determined. Analyze the transmission rate limit information and error code definition information of the two service interfaces to identify potential transmission rate bottlenecks and error handling conflicts during the interaction process, which will serve as interaction constraints. Based on the global interaction possibilities and interaction constraints, the interaction triggering conditions between the two service interfaces are determined. The interaction triggering conditions include data update triggering, time-based triggering, and event-driven triggering. Based on the field definition information and the call parameter requirements, the data exchange type between the two service interfaces is determined. The data exchange type includes basic information exchange, business data exchange, and control command exchange. Based on the transmission rate limit information and the response requirements of the function call, the response timeliness requirements between the two service interfaces are set, and the response timeliness requirements include the maximum response time and the number of timeout retries; The above analysis was performed on all service interfaces in pairs for different scenarios. The interaction trigger conditions, data exchange types and response time requirements between service interfaces in each scenario were compiled. The compiled results were then classified and summarized according to the scenario category of the service interface to generate a list of interface interaction requirements.

6. The standardized interface method for multi-scenario service integration according to claim 1, characterized in that, The process of classifying and statistically analyzing the data exchange types in the interface interaction requirement list, determining the interaction format characteristics corresponding to different data exchange types, and constructing format adaptation rules based on the interaction format characteristics includes: Iterate through all data exchange types in the interface interaction requirement list, count the frequency of each data exchange type, sort them from high to low frequency, and determine the primary and secondary data exchange types. For each data exchange type, extract the corresponding interaction format information, analyze the required fields of the data fields, and generate the required fields of the data fields. Measure the length values ​​of each data field, determine the minimum and maximum length values ​​of each field, and obtain the field length range; Analyze the dependencies between different data fields to determine the field relationships; Integrate the required fields, field length ranges, and field relationships of data fields to generate interactive format features corresponding to different data exchange types; Collect field definition information of service interfaces in various scenarios, establish a field definition mapping table, map fields with different names but the same meaning to a unified field name and meaning, and construct mapping rules to map field definition information with different interaction formats to a unified field definition; Analyze the field type information of service interfaces in various scenarios, refer to common data type standards, establish a field type conversion reference table, determine the methods for converting different field types to standard field types, and construct conversion rules to convert different field type information to standard field types; Analyze the field arrangement order of service interfaces in various scenarios, combine the efficiency and readability requirements of data exchange, determine the standard field arrangement order, establish arrangement order adjustment rules, specify the steps to adjust different arrangement orders to the standard arrangement order, and construct sorting rules to adjust different field arrangement orders to the standard arrangement order. The mapping rules, the conversion rules, and the sorting rules are integrated to generate format adaptation rules.

7. The standardized interface method for multi-scenario service integration according to claim 1, characterized in that, The standard interface interaction module is obtained by performing adaptation processing on the service interfaces of each scenario according to the interface adaptation rule set, including: The format adaptation rules in the interface adaptation rule set are called to perform format conversion processing on the interaction format information of each scenario service interface. The field definition information, field type information and field arrangement order information of each service interface are converted into a unified standard interaction format to obtain the format-adapted service interface information. By applying the transmission adaptation rules in the interface adaptation rule set, the data transmission method information in the format-adapted service interface information is processed for transmission coordination, the transmission protocol type of each service interface is converted into a general transmission protocol, the transmission encryption method is adjusted to a unified encryption method, and the transmission bandwidth is allocated according to the transmission rate limit information to obtain the transmission-adapted service interface information. Using the call adaptation rules in the interface adaptation rule set, the function call specification information in the transmitted adapted service interface information is processed to meet the call specification requirements. The call order is determined according to the interaction triggering conditions. The call parameter requirements are converted into a standard parameter set. The return value format is unified into a standard return format. The error code definition is mapped to a standard error code to obtain the service interface information after call adaptation. The interface functions of the adapted service interface information are integrated and processed, and the service interfaces with related functions are logically associated to construct an interface function association graph. Based on the interface function association graph, a framework structure for a standardized interface interaction module is built. The framework structure includes a format adaptation layer, a transmission adaptation layer, and a call adaptation layer. The format adaptation layer is used to perform format conversion processing, the transmission adaptation layer is used to perform transmission coordination processing, and the call adaptation layer is used to perform call specification processing. The format-adapted service interface information, the transmission-adapted service interface information, and the call-adapted service interface information are deployed to the corresponding layers of the framework structure to obtain a standardized interface interaction module that is compatible with the interaction format, data transmission method, and function call specifications of service interfaces in various scenarios.

8. The standardized interface method for multi-scenario service integration according to claim 1, characterized in that, The construction of a cross-scenario service interaction protocol through the standardized interface interaction module includes: Extract the standard interaction format information of the format adaptation layer in the standardized interface interaction module, and determine the data field exchange specification for cross-scenario service interaction. The data field exchange specification includes the mandatory field requirements, field type restrictions, and field transmission order. Obtain the general transmission protocol information, unified encryption method information and transmission bandwidth allocation rules of the transmission adaptation layer in the standardized interface interaction module, and construct the data transmission specification for cross-scenario service interaction. The data transmission specification includes the selection criteria for the transmission protocol, the application method of the encryption algorithm and the execution criteria for bandwidth allocation. The standardized interface interaction module calls the call order rules, standard parameter set information, standard return format information, and standard error code information of the adaptation layer to generate a function call specification for cross-scenario service interaction. The function call specification includes the triggering conditions for call initiation, the format requirements for parameter passing, the process for handling return values, and the response mechanism for error handling. By integrating the aforementioned data field exchange specifications, data transmission specifications, and function call specifications, a main framework for a cross-scenario service interaction protocol is constructed. This main framework includes a data exchange component, a transmission component, and a call component. The specifications of each part in the main framework are verified for correlation, so that the data field exchange specification and the data transmission specification are consistent during the data transmission process, the data transmission specification and the function call specification are coordinated in terms of call timing, and the data field exchange specification and the function call specification are matched in terms of parameter passing. Based on the correlation verification results, the main framework is adjusted and optimized, and conflicting or inconsistent specification content is corrected to obtain the cross-scenario service interaction protocol. The cross-scenario service interaction protocol is used to guide service interfaces in different scenarios to realize data interaction and function calls through the standardized interface interaction module.

9. A standardized interface system for multi-scenario service integration, characterized in that, The standardized interface system for multi-scenario service interoperability includes a processor and a memory, the memory and the processor are connected, the memory is used to store programs, instructions or code, and the processor is used to execute the programs, instructions or code in the memory to implement the standardized interface method for multi-scenario service interoperability as described in any one of claims 1-8.

Images