Equipment communication method and equipment based on protocol conversion

Abstract

The invention discloses an equipment communication method and equipment based on protocol conversion, and relates to the technical field of servers. The method comprises the following steps: in response to a communication request sent to second equipment by first equipment deployed on a server, acquiring a first protocol version corresponding to the first equipment, historical communication characteristics of transmitted data and a second protocol version corresponding to the second equipment; according to a service scene and historical address mapping information in the historical communication features, constructing an address conversion relationship between the first device and the target memory block; converting first protocol header information corresponding to the first protocol version into second protocol header information corresponding to the second protocol version according to a service scene in the historical communication feature, and constructing a protocol header information conversion relationship between the first device and the target memory block; and realizing communication between the first equipment and the second equipment according to the address conversion relation and the protocol header information conversion relation. The method can improve the communication efficiency between devices.

Description

Technical Field

[0001] This application relates to the field of server technology, and in particular to a device communication method and device based on protocol conversion. Background Technology

[0002] With the rapid development of technologies such as cloud computing and artificial intelligence, server data centers are increasingly demanding higher communication efficiency between heterogeneous devices. Among them, the CXL (Compute Express Link) protocol, as a new generation of high-speed interconnect standard, is mainly used to solve the problem of efficient communication between heterogeneous devices such as CPUs, GPUs, and memory expansion cards.

[0003] Currently, the mixed deployment of heterogeneous devices with different versions is leading to increasingly prominent compatibility issues, severely hindering the large-scale application of the CXL protocol. Related technologies utilize independent protocol conversion chips to achieve interconnection between devices of different versions. However, when using protocol conversion chips to interconnect different versions of devices, the conversion latency is significant, thus reducing the communication efficiency between devices. Summary of the Invention

[0004] This application provides a device communication method and device based on protocol conversion, so as to at least solve the problem of low communication efficiency between devices in related technologies.

[0005] On the one hand, this application provides a device communication method based on protocol conversion, including:

[0006] In response to a communication request sent from a first device deployed on the server to a second device, the system obtains the first protocol version corresponding to the first device, historical communication characteristics of the transmitted data, and the second protocol version corresponding to the second device.

[0007] Based on the business scenarios and historical address mapping information in historical communication characteristics, construct the address translation relationship between the target memory blocks used to process communication requests in the first device and the second device;

[0008] Based on the business scenarios in historical communication characteristics, the first protocol header information corresponding to the first protocol version is converted into the second protocol header information corresponding to the second protocol version, and the protocol header information conversion relationship between the first device and the target memory block is constructed.

[0009] Based on the address translation relationship and protocol header information translation relationship between the first device and the target memory block, communication between the first device and the second device is realized.

[0010] On the other hand, this application provides a device communication apparatus based on protocol conversion, comprising:

[0011] The acquisition unit is used to respond to a communication request sent by a first device deployed on the server to a second device, and to acquire the first protocol version corresponding to the first device, the historical communication characteristics of the transmitted data, and the second protocol version corresponding to the second device.

[0012] The first construction unit is used to construct the address translation relationship between the target memory block used to process communication requests in the first device and the second device based on the business scenario and historical address mapping information in the historical communication characteristics.

[0013] The second construction unit is used to convert the first protocol header information corresponding to the first protocol version into the second protocol header information corresponding to the second protocol version based on the business scenarios in the historical communication characteristics, and to construct the protocol header information conversion relationship between the first device and the target memory block.

[0014] The communication unit is used to realize communication between the first device and the second device based on the address translation relationship and protocol header information translation relationship between the first device and the target memory block.

[0015] This application also provides an electronic device, including: a memory for storing a computer program; and a processor for implementing the steps of any of the above-described protocol-conversion-based device communication methods when executing the computer program.

[0016] This application also provides a computer-readable storage medium storing a computer program, wherein when the computer program is executed by a processor, it implements the steps of any of the above-described device communication methods based on protocol conversion.

[0017] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of any of the above-described protocol-conversion-based device communication methods.

[0018] This application provides a device communication method and device based on protocol conversion. The method includes: responding to a communication request sent by a first device deployed on a server to a second device; obtaining a first protocol version corresponding to the first device, historical communication characteristics of transmitted data, and a second protocol version corresponding to the second device; constructing an address translation relationship between the first device and a target memory block in the second device used to process the communication request based on the business scenario and historical address mapping information in the historical communication characteristics; converting the first protocol header information corresponding to the first protocol version to the second protocol header information corresponding to the second protocol version based on the business scenario in the historical communication characteristics, and constructing a protocol header information translation relationship between the first device and the target memory block; and realizing communication between the first device and the second device based on the address translation relationship and the protocol header information translation relationship between the first device and the target memory block. In the embodiments of this application, since the address translation relationship and protocol header information translation relationship between different versions of devices are constructed through the business scenario and historical address mapping information in the historical communication characteristics, and data transmission between different versions of devices is realized through the address translation relationship and protocol header information translation relationship, no additional protocol conversion chip is required, avoiding the conversion delay caused by the protocol conversion chip, thus improving the communication efficiency between devices. Attached Figure Description

[0019] To more clearly illustrate the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0020] Figure 1 The flowchart of the device communication method based on protocol conversion provided in the embodiments of this application Figure 1 ;

[0021] Figure 2 A schematic diagram of a device communication method based on protocol conversion provided in this application embodiment. Figure 1 ;

[0022] Figure 3 Schematic diagram of the device communication apparatus based on protocol conversion provided in the embodiments of this application Figure 1 ;

[0023] Figure 4 A schematic diagram of the structure of the electronic device provided in this application. Detailed Implementation

[0024] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the protection scope of this application.

[0025] It should be noted that, in the description of this application, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. The terms "first," "second," etc., in this application are used to distinguish similar objects and are not used to describe a specific order or sequence.

[0026] With the rapid development of technologies such as cloud computing and artificial intelligence, server data centers are increasingly demanding higher communication efficiency between heterogeneous devices. Among these, the CXL (Compute Express Link) protocol, as a next-generation high-speed interconnect standard, is primarily used to solve the problem of efficient communication between heterogeneous devices such as CPUs, GPUs, and memory expansion cards. However, supporting the mixed deployment of different versions of heterogeneous devices has led to increasingly prominent compatibility issues, severely hindering the large-scale application of the CXL protocol.

[0027] In related technologies, interconnection between different versions of devices is achieved by deploying independent protocol conversion chips. These chips are responsible for protocol format conversion, address mapping, and cache consistency maintenance. However, when using protocol conversion chips to interconnect different versions of devices, the conversion latency is significant, thus reducing the communication efficiency between devices.

[0028] Therefore, how to fully utilize the bandwidth of multiple memory channels to improve the memory access speed of servers is a technical problem that urgently needs to be solved.

[0029] To address the aforementioned technical problems, this application proposes a device communication method based on protocol conversion. If a device sends a communication request to another device, it obtains the historical communication data characteristics of the device. Based on the historical communication data characteristics, it constructs the address conversion relationship and protocol header information conversion relationship between the device and other devices, thereby enabling communication between the device and other devices.

[0030] Optionally, the specific steps include: First, in response to a communication request sent by a first device deployed on the server to a second device, obtaining the first protocol version corresponding to the first device, historical communication characteristics of the transmitted data, and the second protocol version corresponding to the second device. Then, based on the business scenario and historical address mapping information in the historical communication characteristics, constructing an address translation relationship between the first device and the target memory block in the second device used to process the communication request; based on the business scenario in the historical communication characteristics, converting the first protocol header information corresponding to the first protocol version into the second protocol header information corresponding to the second protocol version, constructing a protocol header information translation relationship between the first device and the target memory block. Finally, based on the address translation relationship and protocol header information translation relationship between the first device and the target memory block, realizing communication between the first device and the second device.

[0031] In this embodiment, by constructing address conversion relationships and protocol header information conversion relationships between different versions of devices through the business scenarios and historical address mapping information in historical communication characteristics, data transmission between different versions of devices is realized through the address conversion relationships and protocol header information conversion relationships. This eliminates the need to deploy additional protocol conversion chips, avoids conversion delays caused by protocol conversion chips, and thus improves the communication efficiency between devices.

[0032] To enable those skilled in the art to better understand the present application, the present application will be further described in detail below with reference to the accompanying drawings and specific embodiments.

[0033] The specific application environment architecture or specific hardware architecture on which the execution of the protocol-based device communication method depends is described here.

[0034] In some embodiments, a cross-version device interaction system on a server is used to convert protocols between different versions of devices to achieve data transmission between them. Optionally, the cross-version device interaction system may include a three-layer architecture: a hardware layer, a protocol adaptation layer, and a software management layer. The hardware layer architecture includes: heterogeneous devices installed on the server (e.g., CPU, GPU, memory expansion card), a switch, a protocol conversion engine, a compression engine, and a self-learning module. The protocol adaptation layer includes: a version adaptation sublayer, a protocol header processing module, and a dynamic intelligent compression controller. The software management layer includes: a global memory manager, a dynamic routing controller, an application interface layer, and a policy optimizer.

[0035] The following explains the background technology and some terms involved in this application:

[0036] CXL (Compute Express Link): A high-speed interconnect protocol for devices such as CPUs, GPUs, and memory.

[0037] CXL.io: The input / output sub-protocol in the CXL protocol, based on PCIe 5.0 / 6.0 extensions, supports device enumeration and link management.

[0038] CXL.cache: The caching subprotocol in the CXL protocol, which supports device access to the cache of host memory.

[0039] CXL.mem: The memory sub-protocol in the CXL protocol, which supports direct access of devices to host memory.

[0040] PTE (Protocol Translation Engine): A hardware module used to implement cross-version protocol format conversion in CXL.

[0041] VAS (Version Adaptation Sub-Layer): A layered architecture component used to ensure compatibility with multiple version protocols.

[0042] GMM (Global Memory Manager): A global memory manager used to uniformly schedule memory resources across multiple versions of CXL devices.

[0043] ATT (Address Translation Table): The address translation table is used for address space mapping between CXL 1.x devices and the global memory pool.

[0044] VCA (Version Capability Advertisement): A message format used for exchanging protocol version information between CXL devices.

[0045] SLM (Self-Learning Module): A self-learning module that can optimize protocol conversion and compression strategies by analyzing historical data.

[0046] DIC (Dynamic Intelligent Compression): A technology that automatically adjusts the compression method according to different scenarios.

[0047] Figure 1 The flowchart of the device communication method based on protocol conversion provided in the embodiments of this application Figure 1 The execution entity of this protocol-conversion-based device communication method can be a server. For example... Figure 1 As shown, the method includes:

[0048] S101. In response to a communication request sent from a first device deployed on the server to a second device, obtain the first protocol version corresponding to the first device, the historical communication characteristics of the transmitted data, and the second protocol version corresponding to the second device.

[0049] In this embodiment of the disclosure, the first device and the second device can be any type of device installed on the server. For example, a CPU, GPU, memory expansion card, etc. Optionally, the first device and the second device are heterogeneous devices installed on the server via PCIe (Peripheral Component Interconnect Express) slots.

[0050] For example, during the link initialization phase, the master device (e.g., a CXL switch deployed on a server) sends a more intelligent version probe frame by extending the enumeration process of the CXL.io protocol. This probe frame can not only obtain version information of slave devices (e.g., memory expansion cards), but also collect historical communication data characteristics of the devices, such as commonly used protocol fields and data transmission frequencies.

[0051] Optionally, after receiving a version probe frame from a device (e.g., a memory expansion card), the device returns its own version information (e.g., 1.1) and related historical data characteristics. The self-learning module (SLM) of the master device analyzes the historical data characteristics and determines the conversion strategy in combination with historical conversion records. The specific method is described in steps S102 and S103.

[0052] S102. Based on the business scenarios and historical address mapping information in the historical communication characteristics, construct the address translation relationship between the target memory blocks used to process communication requests in the first device and the second device.

[0053] In this embodiment of the disclosure, the business scenario is used to indicate the application scenario of the transmitted data. For example, model training, database query, etc. The historical address mapping information is used to indicate the address translation relationship of the transmitted data.

[0054] In some embodiments, constructing an address translation relationship between a first device and a target memory block in a second device for processing communication requests based on the business scenario and historical address mapping information in historical communication characteristics may include the following steps (1) to (2):

[0055] (1) Based on the business scenarios in the historical communication characteristics, determine the target memory block used to process communication requests and the first memory address corresponding to the target memory block in the second device.

[0056] In this embodiment of the disclosure, multiple memory blocks can be dynamically classified and adjusted according to their usage frequency and access patterns in the second device. Frequently accessed memory blocks will be allocated to faster storage areas.

[0057] In some embodiments, this step may include: determining a target memory access pattern corresponding to a business scenario based on the business scenario in historical communication characteristics, wherein the memory access pattern is used to represent the access pattern of memory; determining a target storage region corresponding to the target memory access pattern from the correspondence between memory access patterns and storage regions based on the target memory access pattern, wherein different storage regions correspond to different data transmission speeds; and determining a target memory block in the second device used to process communication requests and a first memory address corresponding to the target memory block from the target storage region.

[0058] Optionally, the storage area includes a high-speed storage area, a medium-speed storage area, and a low-speed storage area. The data transfer speed of the high-speed storage area is greater than or equal to a first data transfer speed, the data transfer speed of the low-speed storage area is less than or equal to a second data transfer speed, and the data transfer speed of the medium-speed storage area is greater than the second data transfer speed and less than the first data transfer speed. In this embodiment, the values ​​of the first data transfer speed and the second data transfer speed are not specifically limited and can be set and modified as needed.

[0059] Optionally, the memory access pattern includes one or more of the following: contiguous address access pattern, random address access pattern, and periodic address access pattern. For example, the memory access pattern corresponding to the model training data is a contiguous address access pattern, and the storage area corresponding to the contiguous address access pattern is a high-speed storage area.

[0060] In this embodiment of the disclosure, since memory blocks can be dynamically classified and adjusted according to the frequency of memory use and access patterns, frequently accessed memory blocks will be allocated to faster storage areas, which can meet the data transmission needs of various address access patterns and thus improve the user experience.

[0061] (2) Based on the historical address mapping information in the historical communication features, the second memory address corresponding to the first device is converted into the first memory address, and the address translation relationship between the first device and the target memory block is constructed.

[0062] In this embodiment of the disclosure, the protocol conversion engine analyzes the historical address mapping patterns based on the self-learning module, thereby quickly converting the second memory address corresponding to the first device into the first memory address.

[0063] For example, the first device is a CXL 1.x version GPU device, and the second device is a CXL 3.0 version memory pool. Accordingly, the second memory address is the local address corresponding to the GPU device, and the second memory address is the global address corresponding to the memory pool.

[0064] In some embodiments, the historical address mapping information includes multiple historical address mappings with mapping frequencies greater than a preset mapping frequency; optionally, the memory address is converted according to the pre-stored mapping information; correspondingly, this step may include: selecting a target historical address mapping corresponding to the second memory address from multiple historical address mappings according to the historical address mapping information in the historical communication features; and converting the second memory address corresponding to the first device into a first memory address according to the target historical address mapping.

[0065] In this embodiment of the disclosure, based on the frequency and pattern of the recorded address mappings, when certain address mappings occur frequently, they can be pre-converted and stored in the historical address mapping information. Then, the memory address can be converted according to the pre-stored mapping information, thereby improving the memory address conversion speed.

[0066] Optionally, the process of generating historical address mapping information includes: obtaining the mapping frequency corresponding to the address mapping of data transmitted by the first device, wherein the mapping frequency is determined based on the ratio of the number of mappings over a preset duration to the preset duration; if the mapping frequency is greater than or equal to the preset frequency, the address mapping is stored in the historical address mapping information. In this embodiment of the disclosure, the value of the preset frequency is not specifically limited and can be set and modified as needed.

[0067] S103. Based on the business scenarios in the historical communication characteristics, convert the first protocol header information corresponding to the first protocol version into the second protocol header information corresponding to the second protocol version, and construct the protocol header information conversion relationship between the first device and the target memory block.

[0068] In this embodiment of the disclosure, a scenario identifier bit may be added to identify the application scenario to which the data transmission belongs. Accordingly, based on the service scenario in the historical communication characteristics, the first protocol header information corresponding to the first protocol version is converted into the second protocol header information corresponding to the second protocol version, including: determining the service scenario identifier field and the identifier information corresponding to the service scenario based on the service scenario in the historical communication characteristics; and performing protocol header extension on the first protocol header information corresponding to the first protocol version based on the protocol identifier field and the identifier information corresponding to the protocol identifier field to obtain the second protocol header information corresponding to the second protocol version.

[0069] It should be noted that, in addition to the original protocol header extensions, the self-learning module will analyze the usage of newly added fields in different scenarios. For example, in some low-priority applications, the priority identifier field changes less frequently, and the system will use a more efficient encoding method to handle it.

[0070] In some embodiments, the method further includes: obtaining the usage status of each of the multiple identifier fields in the second protocol header information of the historical communication features; if the usage status of the identifier field meets the preset compression conditions, then the identifier field is compressed.

[0071] Optionally, the usage includes the repetition rate of the identification information corresponding to the identification field, and the preset compression condition includes the repetition rate of the identification information corresponding to the identification field being greater than the preset repetition rate; and / or, the usage includes the number of changes of the identification information corresponding to the identification field, and the preset compression condition includes the number of changes of the identification information corresponding to the identification field being less than the preset number of changes.

[0072] It should be noted that this application can also use an LSTM (Long Short-Term Memory) model, combined with historical data provided by a self-learning module, to predict route labels and address offsets, and adjust the parameters of the prediction model according to different application scenarios. For example, for periodic data transmission, the LSTM model will pay more attention to the patterns in historical cycles.

[0073] In some embodiments, for text-based protocol headers, a compression algorithm with a higher compression ratio can be selected; for scenarios with high real-time requirements, a faster compression algorithm can be selected. Accordingly, the identification field is compressed, including: obtaining the data type and transmission scenario corresponding to the identification field; if the data type is text, the identification field is compressed using a first compression algorithm; if the transmission scenario is a real-time transmission scenario, the identification field is compressed using a second compression algorithm; wherein, the first compression algorithm is a compression algorithm with a compression ratio greater than a preset compression ratio, and the second compression algorithm is a compression algorithm with a compression speed greater than a preset compression speed.

[0074] In this embodiment of the disclosure, since an appropriate compression algorithm can be selected to compress the identifier field according to the data type and transmission scenario corresponding to the identifier field, the compression efficiency of the identifier field is improved, thereby improving the user experience.

[0075] It should be noted that, in order to further improve the efficiency of protocol conversion, the conversion parameters during the conversion process can be recorded in real time, and the conversion strategy can be automatically adjusted based on the conversion parameters.

[0076] In some embodiments, the conversion parameters include conversion time and / or conversion error rate. Optionally, the conversion parameters include the conversion error rate. Accordingly, automatically adjusting the conversion strategy based on the conversion parameters may include: if the conversion error rate corresponding to the current conversion strategy is greater than a preset value, then switching to a backup conversion strategy.

[0077] In other embodiments, the conversion parameters include data transmission rate. Optionally, the monitoring window size is automatically adjusted based on the volatility of data transmission. When data transmission is unstable, the window size is reduced, allowing the compression strategy to respond to changes more quickly. Correspondingly, if the change in data transmission rate is greater than a preset change, the current monitoring window time is reduced by a preset time. In this case, reducing the window size can increase the monitoring frequency, thereby allowing the compression strategy to respond to changes more quickly.

[0078] The monitoring window is used to detect data related to the compression strategy, such as data duplication rate. Optionally, when the detected data duplication rate exceeds a preset duplication rate threshold, the compression strategy is automatically activated to facilitate timely improvement of the protocol's conversion efficiency through compression.

[0079] In this embodiment of the disclosure, the values ​​of the preset change amount, preset time, and preset repetition rate threshold are not specifically limited, and can be set and modified according to different scenario requirements.

[0080] It should be noted that, in this embodiment of the disclosure, the self-learning module SLM can also learn the ability of different devices to process compressed frames. For older devices with weaker processing capabilities, the proportion of compressed frames sent will be reduced to ensure communication stability.

[0081] S104. Based on the address translation relationship and protocol header information translation relationship between the first device and the target memory block, communication between the first device and the second device is realized.

[0082] In this embodiment, a version adaptation sublayer can be used to load a first protocol conversion module corresponding to the first device based on a first protocol version and a second protocol conversion module corresponding to the second device based on a second protocol version. When the first device transmits data to the second device, the first protocol conversion module converts the first protocol header information of the data into second protocol header information that the second device can receive, thereby enabling communication between the first and second devices. When the second device transmits data to the first device, the second protocol conversion module converts the address of the second protocol header information of the data into first protocol header information that the first device can receive, thereby enabling communication between the first and second devices.

[0083] Optionally, the protocol conversion module includes CXL 1.x, CXL 2.0, and CXL 3.0 modules. The CXL 1.x module dynamically adjusts the processing priority of DMA requests based on local memory usage to avoid memory access conflicts. The CXL 2.0 module adjusts the routing label generation strategy based on the load across server memory pools to balance the load among servers. The CXL 3.0 module optimizes the timing of protocol header compression / decompression based on the cascading configuration of multi-level switches, reducing the processing pressure on intermediate nodes.

[0084] In some embodiments, device performance parameters can also be obtained, and the operating parameters of the protocol conversion module can be adjusted according to these parameters. Optionally, the device performance parameters include processing speed and / or memory size. If the device's processing speed is less than a preset processing speed and / or its memory size is less than a preset memory size, the proportion of compressed frames sent by the protocol conversion module is reduced to ensure communication stability.

[0085] This application can also construct network topology information corresponding to the device version information of multiple devices, and select a suitable data transmission path by combining the current load and historical failure information of the devices.

[0086] Optionally, when selecting a data transmission path using the single-source shortest path algorithm, the stability parameters of different paths can be considered, prioritizing the path with the highest stability parameter. The stability parameter indicates the stability of the data transmission path; a higher stability parameter indicates greater stability. Optionally, the stability parameter is negatively correlated with device load and historical device failure rate.

[0087] The following explanation uses CXL 1.x GPU accessing the CXL 3.0 memory pool as an example. Figure 2 As shown, the specific process is as follows:

[0088] Step 1: Device Access and Version Negotiation: After the GPU is connected to the CXL switch, the switch sends a smart version probe frame, which not only identifies the GPU as CXL 1.x and the memory pool as CXL 3.0, but also collects the GPU's historical communication characteristics, such as the periodic data transmission characteristic often used in AI training scenarios.

[0089] Step 2: Load the conversion protocol module: The version adaptation sublayer VAS automatically loads the CXL 1.x and 3.0 modules, and adjusts the module running parameters according to the performance parameters of the GPU and memory pool, and initializes the protocol conversion engine PTE, compression engine and self-learning module SLM.

[0090] Step 3: Memory access request generation: The GPU requests memory through a unified API. The Global Memory Manager (GMM) combines the needs of the business scenario (e.g., AI training scenario) and the current state of the memory pool to allocate an appropriate CXL 3.0 memory block and return the global address.

[0091] Step 4: Protocol Conversion and Compression: The protocol conversion engine PTE quickly converts the GPU's local address to a global address based on the historical address mapping patterns analyzed by the self-learning module SLM, and inserts a 3.0 protocol header with scene identifiers. The compression engine selects an appropriate compression algorithm based on the data characteristics of the AI ​​training scene. When the protocol header repetition rate reaches 85%, compression is enabled (8 bytes → 3 bytes).

[0092] Step 5: Dynamic routing and forwarding: Based on VCA information, path stability, and compression efficiency, the switch selects the optimal path that supports compression and forwards the request to the target memory.

[0093] Step 6: Data Response Processing: When the memory returns data, the switch decompresses the protocol header and converts it to 1.x format. At the same time, SLM records the effect of this conversion and compression for subsequent optimization. Finally, the data is sent back to the GPU.

[0094] This application proposes a device communication method based on protocol conversion: First, in response to a communication request sent by a first device deployed on a server to a second device, the method obtains the first protocol version corresponding to the first device, historical communication characteristics of transmitted data, and the second protocol version corresponding to the second device. Then, based on the business scenario and historical address mapping information in the historical communication characteristics, an address translation relationship is constructed between the first device and the target memory block in the second device used to process the communication request. Based on the business scenario in the historical communication characteristics, the first protocol header information corresponding to the first protocol version is converted to the second protocol header information corresponding to the second protocol version, thus constructing a protocol header information conversion relationship between the first device and the target memory block. Finally, communication between the first device and the second device is achieved based on the address translation relationship and the protocol header information conversion relationship between the first device and the target memory block. In this embodiment, since the address translation relationship and protocol header information conversion relationship between different version devices are constructed through the business scenario and historical address mapping information in the historical communication characteristics, and data transmission between different version devices is achieved through the address translation relationship and protocol header information conversion relationship, no additional protocol conversion chip is required, avoiding the conversion delay caused by the protocol conversion chip, thus improving the communication efficiency between devices.

[0095] Figure 3 This is a schematic diagram of the device communication apparatus based on protocol conversion provided in an embodiment of this application. Figure 3 As shown, the device includes:

[0096] The acquisition unit 301 is used to respond to a communication request sent by the first device deployed on the server to the second device, and to acquire the first protocol version corresponding to the first device, the historical communication characteristics of the transmitted data, and the second protocol version corresponding to the second device.

[0097] The first construction unit 302 is used to construct the address translation relationship between the target memory block used to process communication requests in the first device and the second device based on the business scenario and historical address mapping information in the historical communication characteristics.

[0098] The second construction unit 303 is used to convert the first protocol header information corresponding to the first protocol version into the second protocol header information corresponding to the second protocol version according to the business scenario in the historical communication characteristics, and to construct the protocol header information conversion relationship between the first device and the target memory block.

[0099] The communication unit 304 is used to realize communication between the first device and the second device based on the address translation relationship and protocol header information translation relationship between the first device and the target memory block.

[0100] In some embodiments, the first construction unit 302 constructs an address translation relationship between the first device and the target memory block in the second device used to process communication requests based on the service scenario and historical address mapping information in the historical communication features. This includes: determining the target memory block in the second device used to process communication requests and the first memory address corresponding to the target memory block based on the service scenario in the historical communication features; converting the second memory address corresponding to the first device into the first memory address based on the historical address mapping information in the historical communication features, and constructing an address translation relationship between the first device and the target memory block.

[0101] In some embodiments, the historical address mapping information includes multiple historical address mappings with mapping frequencies greater than a preset mapping frequency; correspondingly, the first construction unit 302 converts the second memory address corresponding to the first device into a first memory address based on the historical address mapping information in the historical communication features, including: selecting a target historical address mapping corresponding to the second memory address from multiple historical address mappings based on the historical address mapping information in the historical communication features; and converting the second memory address corresponding to the first device into a first memory address based on the target historical address mapping.

[0102] In some embodiments, the process of generating historical address mapping information includes: obtaining the mapping frequency corresponding to the address mapping of data transmitted by the first device, wherein the mapping frequency is determined based on the ratio of the number of mappings over a preset duration to the preset duration; if the mapping frequency is greater than or equal to the preset frequency, the address mapping is stored in the historical address mapping information.

[0103] In some embodiments, the first construction unit 302 determines the target memory block and the corresponding first memory address in the second device for processing communication requests based on the service scenario in the historical communication characteristics, including: determining the target memory access pattern corresponding to the service scenario based on the service scenario in the historical communication characteristics, wherein the memory access pattern is used to represent the memory access rules; determining the target storage region corresponding to the target memory access pattern from the correspondence between the memory access pattern and the storage region based on the target memory access pattern, wherein different storage regions correspond to different data transmission speeds; and determining the target memory block and the corresponding first memory address in the second device for processing communication requests from the target storage region.

[0104] In some embodiments, the second construction unit 303 converts the first protocol header information corresponding to the first protocol version into the second protocol header information corresponding to the second protocol version based on the service scenario in the historical communication features, including: determining the service scenario identifier field and the identifier information corresponding to the service scenario based on the service scenario in the historical communication features; and performing protocol header extension on the first protocol header information corresponding to the first protocol version based on the protocol identifier field and the identifier information corresponding to the protocol identifier field to obtain the second protocol header information corresponding to the second protocol version.

[0105] In some embodiments, the device further includes a protocol compression module, which is used to obtain the usage status of each of the multiple identifier fields in the second protocol header information of the historical communication features; if the usage status of the identifier field meets the preset compression conditions, the identifier field is compressed.

[0106] In some embodiments, the usage includes the repetition rate of the identification information corresponding to the identification field, and the preset compression condition includes the repetition rate of the identification information corresponding to the identification field being greater than a preset repetition rate; and / or, the usage includes the number of changes of the identification information corresponding to the identification field, and the preset compression condition includes the number of changes of the identification information corresponding to the identification field being less than a preset number of changes.

[0107] In some embodiments, the protocol compression module compresses the identifier field, including: obtaining the data type and transmission scenario corresponding to the identifier field; if the data type is text, the identifier field is compressed using a first compression algorithm; if the transmission scenario is a real-time transmission scenario, the identifier field is compressed using a second compression algorithm; wherein, the first compression algorithm is a compression algorithm with a compression ratio greater than a preset compression ratio, and the second compression algorithm is a compression algorithm with a compression speed greater than a preset compression speed.

[0108] This application provides a device communication apparatus based on protocol conversion. By constructing address conversion relationships and protocol header information conversion relationships between different versions of devices through business scenarios and historical address mapping information in historical communication characteristics, data transmission between different versions of devices is realized through address conversion relationships and protocol header information conversion relationships. No additional protocol conversion chip is required, avoiding the conversion delay caused by the protocol conversion chip, thus improving the communication efficiency between devices.

[0109] For a description of the features of the device communication apparatus based on protocol conversion provided in this application, please refer to the relevant description of the device communication method based on protocol conversion, which will not be repeated here.

[0110] Figure 4 A schematic diagram of the structure of the electronic device provided in this application. Figure 4 As shown, the electronic device 40 provided in this embodiment includes at least one processor 401 and a memory 402. Optionally, the electronic device 40 further includes a communication component 403. The processor 401, memory 402, and communication component 403 are connected via a bus.

[0111] In a specific implementation, at least one processor 401 executes computer execution instructions stored in memory 402, causing at least one processor 401 to execute the above-described embodiment of the device communication method based on protocol conversion.

[0112] The specific implementation process of processor 401 can be found in the above method embodiments, and its implementation principle and technical effect are similar. It will not be repeated here.

[0113] In the above embodiments, it should be understood that the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the application can be directly manifested as being executed by a hardware processor, or executed by a combination of hardware and software modules within the processor.

[0114] The memory may include random access memory (RAM) and may also include non-volatile memory (NVM), such as at least one disk storage device.

[0115] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.

[0116] Embodiments of this application also provide a computer-readable storage medium storing a computer program, wherein the computer program is configured to execute the steps in any of the above embodiments of the device communication method based on protocol conversion when it is run.

[0117] In one exemplary embodiment, the aforementioned computer-readable storage medium may include, but is not limited to, various media capable of storing computer programs, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard disk, magnetic disk, or optical disk.

[0118] Embodiments of this application also provide a computer program product, which includes a computer program that, when executed by a processor, implements the steps in any of the above-described embodiments of the device communication method based on protocol conversion.

[0119] Embodiments of this application also provide another computer program product, including a non-volatile computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps in any of the above-described embodiments of the device communication method based on protocol conversion.

[0120] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0121] The foregoing has provided a detailed description of a device communication method and device based on protocol conversion provided in this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the embodiments above are merely for the purpose of helping to understand the method and its core ideas. It should be noted that those skilled in the art can make various improvements and modifications to this application without departing from its principles, and these improvements and modifications also fall within the protection scope of the claims of this application.

Claims

1. A device communication method based on protocol conversion, characterized in that, include: In response to a communication request sent from a first device deployed on the server to a second device, the system obtains the first protocol version corresponding to the first device, historical communication characteristics of the transmitted data, and the second protocol version corresponding to the second device. Based on the business scenarios and historical address mapping information in the historical communication characteristics, an address translation relationship is constructed between the first device and the target memory block in the second device used to process the communication request. Based on the business scenarios in the historical communication features, the first protocol header information corresponding to the first protocol version is converted into the second protocol header information corresponding to the second protocol version, and a protocol header information conversion relationship between the first device and the target memory block is constructed. Based on the address translation relationship and protocol header information translation relationship between the first device and the target memory block, communication between the first device and the second device is realized.

2. The device communication method according to claim 1, characterized in that, The step of constructing the address translation relationship between the target memory blocks used to process the communication request in the first device and the second device based on the service scenarios and historical address mapping information in the historical communication characteristics includes: Based on the service scenario in the historical communication characteristics, the target memory block used to process the communication request and the first memory address corresponding to the target memory block are determined in the second device; Based on the historical address mapping information in the historical communication features, the second memory address corresponding to the first device is converted into the first memory address, thereby constructing an address translation relationship between the first device and the target memory block.

3. The device communication method according to claim 2, characterized in that, The historical address mapping information includes multiple historical address mappings with mapping frequencies greater than a preset mapping frequency; Accordingly, the step of converting the second memory address corresponding to the first device into the first memory address based on the historical address mapping information in the historical communication features includes: The step involves selecting the target historical address mapping corresponding to the second memory address from multiple historical address mappings based on the historical address mapping information in the historical communication features. Based on the target historical address mapping, the second memory address corresponding to the first device is converted to the first memory address.

4. The device communication method according to claim 3, characterized in that, The process of generating the historical address mapping information includes: Obtain the mapping frequency corresponding to the address mapping of the data transmitted by the first device, wherein the mapping frequency is determined based on the ratio of the number of mappings over a preset duration to the preset duration; If the mapping frequency is greater than or equal to the preset frequency, the address mapping is stored in the historical address mapping information.

5. The device communication method according to claim 2, characterized in that, The step of determining the target memory block for processing the communication request in the second device and the first memory address corresponding to the target memory block based on the service scenario in the historical communication characteristics includes: Based on the business scenarios in the historical communication characteristics, the target memory access pattern corresponding to the business scenario is determined, and the memory access pattern is used to represent the memory access rules; Based on the target memory access mode, the target storage region corresponding to the target memory access mode is determined from the correspondence between memory access modes and storage regions, wherein different storage regions correspond to different data transfer speeds; Determine the target memory block in the second device used to process the communication request and the first memory address corresponding to the target memory block from the target storage area.

6. The device communication method according to claim 1, characterized in that, The step of converting the first protocol header information corresponding to the first protocol version into the second protocol header information corresponding to the second protocol version based on the service scenario in the historical communication characteristics includes: Based on the business scenarios in the historical communication features, determine the business scenario identifier field corresponding to the business scenario and the identifier information corresponding to the business scenario identifier field; Based on the protocol identifier field corresponding to the business scenario and the identifier information corresponding to the protocol identifier field, the first protocol header information corresponding to the first protocol version is extended to obtain the second protocol header information corresponding to the second protocol version.

7. The device communication method according to claim 1, characterized in that, The method further includes: Obtain the usage status of each of the multiple identifier fields in the second protocol header information of the historical communication features; If the usage of the identifier field meets the preset compression conditions, then the identifier field is compressed.

8. The device communication method according to claim 7, characterized in that, The usage scenario includes the repetition rate of the identification information corresponding to the identification field, and the preset compression condition includes the repetition rate of the identification information corresponding to the identification field being greater than a preset repetition rate; and / or, The usage scenario includes the number of times the identification information corresponding to the identification field changes, and the preset compression condition includes the number of times the identification information corresponding to the identification field changes being less than a preset number of changes.

9. The device communication method according to claim 7, characterized in that, The compression process for the identifier field includes: Obtain the data type and transmission scenario corresponding to the identification field; If the data type is text, the identifier field is compressed using a first compression algorithm; if the transmission scenario is a real-time transmission scenario, the identifier field is compressed using a second compression algorithm. The first compression algorithm is a compression algorithm with a compression ratio greater than a preset compression ratio, and the second compression algorithm is a compression algorithm with a compression speed greater than a preset compression speed.

10. An electronic device, characterized in that, include: Memory, used to store computer programs; A processor, configured to implement the steps of the device communication method based on protocol conversion as described in any one of claims 1 to 9 when executing the computer program.

Images