EIP message header processing method and system

Abstract

The invention discloses a processing method and system of an EIP message header, and relates to the technical field of data processing. Establishment of a compressed context does not only depend on network layer information of a terminal station level any more; the compressed context is generated based on first connection identification information which is carried in an EIP connection establishment request initiated by a master station to a slave station and can uniquely identify EIP connection in an EIP connection establishment process, so that the granularity of the compressed context is refined to a single EIP connection level; and the master station performs context synchronization with the slave station according to the compressed context, and the master station and the slave station can perform message header compression and decompression on the subsequently received EIP message according to the synchronized context, so that a decompression end can accurately restore complete header information of the EIP message based on the synchronized context corresponding to the single EIP connection level.

Description

Technical Field

[0001] This application relates to the field of industrial network technology, and in particular to a method and system for processing EIP (Ethernet / IP) message headers. Background Technology

[0002] Traditional message header compression techniques typically differentiate between different protocol types based on the session establishment process and configure different compression context strategies for different types of sessions.

[0003] However, in application architectures that integrate EIP and wireless networks, a Terminal Station (TS) connects to multiple EIP slave devices via wired connections. All I / O data from the slave devices is aggregated through this Terminal Station and then transmitted over the wireless interface. Since the wireless link only uses the IP address and MAC address of the Terminal Station as communication endpoints, from the perspective of the air interface, all uplink and downlink packets appear to be sent to or originate from the same physical terminal node.

[0004] In this situation, traditional packet header compression technology only constructs the compression context based on the network layer information at the terminal station level, which makes it impossible for the decompression end to distinguish EIP packets from different slave stations, and thus unable to accurately restore key information such as the slave station identifier in the packet header. Summary of the Invention

[0005] The main purpose of this application is to provide a method and system for processing EIP message headers, which aims to enable the decompression end to accurately restore the complete header information of EIP messages based on the first compression context corresponding to a single EIP connection level.

[0006] To achieve the above objectives, this application proposes a method for processing EIP headers, applied to a main station. The method for processing EIP headers includes:

[0007] During the connection establishment phase, a compressed context is generated based on the first connection identifier information carried in the EIP connection establishment request initiated by the master station to the slave station. The first connection identifier information is used to uniquely identify the EIP connection. Based on the compression context, the master station and slave station perform context synchronization so that the master station and slave station can compress and decompress the headers of subsequently received EIP messages according to the synchronized context.

[0008] In one embodiment, the step of generating a compression context based on the first connection identifier information carried in the EIP connection establishment request initiated by the master station to the slave station includes: Parse the first connection identifier information to obtain the first connection identifier field; The current connection attributes are determined based on the first connection identifier field; Generate a compression context based on the current connection attributes.

[0009] In one embodiment, the current connection attributes include new connection, updated connection, and added connection; the compression context includes a first compression context, a second compression context, and a third compression context; the first connection identifier field includes a device identifier field and a service identifier field; and the step of generating a compression context based on the current connection attributes includes: When the current connection attribute is a newly established connection, the generated content includes an initial connection identifier field, an initial connection identifier index, and a first compression context with initial compression parameters; When the current connection attribute is an update connection, the generated content includes the initial connection identifier index and the updated compression parameters in a second compression context; When the current connection attribute is "add connection", the generated content includes the added service identifier field, the initial connection identifier index, and the third compression context of the added compression parameters.

[0010] In one embodiment, the step of determining the current connection attribute based on the first connection identifier field includes: Iterate through the main site's local context list and determine whether there exists a local context that completely matches all field values ​​in the first connection identifier field; If no local context exists that matches any value in the first connection identifier field, then the current connection attribute is determined to be a new connection. If a local context exists that exactly matches all field values ​​in the first connection identifier field, then the current connection attribute is determined to be an update connection; If a local context exists that matches only some of the field values ​​in the first connection identifier field, then the current connection attribute is determined to be an added connection.

[0011] In one embodiment, the step of synchronizing the compression context with the slave station includes at least one of the following: The compression context is updated to the local context list of the master station, and the compression context is sent to the slave station. When the context confirmation information is received from the slave station, it is determined that the context synchronization is successful. The compression context is updated in the master station's local context list, and the connection identifier index and connection identifier field in the compression context are sent to the slave station as the fourth compression context. The slave station can then use the connection identifier field in the fourth compression context to find the context to be improved from the slave station's local context list and fill the context to be improved with the connection identifier index of the fourth compression context, thereby achieving context synchronization. The context to be improved includes a fifth compression context, which is generated by the slave station based on the second connection identifier information.

[0012] In one embodiment, after determining that context synchronization was successful or that context synchronization was achieved, the method further includes: When a downlink EIP message is received, the second connection identifier field in the EIP message is parsed, and a unique context is determined from the local context list of the master station based on the second connection identifier field. The target device identifier index and the target service identifier index are determined based on the unique context corresponding to the main station; Based on the unique context corresponding to the master station, the header of the EIP message is compressed, and the target device identifier index and the target service identifier index are appended to the compressed header to form a compressed message, which is then sent to the slave station.

[0013] To achieve the above objectives, this application proposes a method for processing EIP headers, applied to a slave station. The method for processing EIP headers includes: Receive context-related information sent by the master station, wherein the context-related information includes a compressed context, which is generated by the master station during the connection establishment phase based on the first connection identifier information in the EIP connection establishment request initiated from the master station to the slave station, and the first connection identifier information is used to uniquely identify the EIP connection; Based on the context-related information, the master station and slave station perform context synchronization so that the master station and slave station can compress and decompress the headers of subsequently received EIP messages according to the synchronized context.

[0014] In one embodiment, before the step of receiving context-related information sent by the master station, the method further includes: During the connection establishment phase, the second connection identifier information carried in the EIP connection establishment request initiated by the master station to the slave station is obtained; A fifth compression context is generated based on the second connection identifier information.

[0015] In one embodiment, the context-related information further includes a fourth compressed context, and the step of synchronizing the context with the main station based on the context-related information includes at least one of the following: The compressed context is updated in the slave station's local context list, and context confirmation information is sent back to the master station to achieve context synchronization; Based on the connection identifier field in the fourth compression context, the context to be improved is retrieved from the slave station's local context list, and the connection identifier index in the fourth compression context is filled into the context to be improved. The improved context is then updated in the slave station's local context list, and context confirmation information is sent back to the master station to achieve context synchronization. The fourth compression context is the one sent by the master station to the local station using the connection identifier index and connection identifier field in the compression context. The context to be improved includes the fifth compression context.

[0016] In one embodiment, after the step of synchronizing the context with the main station based on the context-related information, the method further includes: When a compressed message is received from the master station, the target device identifier index and the target service identifier index in the compressed message are parsed. Based on the target device identifier index and the target service identifier index, a unique context is determined from the slave station's local context list; Based on the unique context corresponding to the slave station, the compressed message is decompressed to obtain the decompressed EIP message, and the decompressed EIP message is sent to the target device.

[0017] In addition, to achieve the above objectives, this application also proposes an EIP header processing system, which includes a master station and a slave station. When data is downlinked, the master station is the compression end and the slave station is the decompression end. When data is uplinked, the slave station is the compression end and the master station is the decompression end. When data is transmitted downlink, during the connection establishment phase, the master station generates a compression context based on the first connection identifier information carried in the EIP connection establishment request initiated by the master station to the slave station, and sends context-related information to the slave station. The first connection identifier information is used to uniquely identify the EIP connection, and the context-related information includes the compression context. The slave station receives the context-related information sent by the master station and performs context synchronization with the master station based on the context-related information.

[0018] One or more technical solutions proposed in this application have at least the following technical effects: In this application, during the connection establishment phase, the master station generates a compression context based on the first connection identifier information carried in the EIP connection establishment request initiated by the master station to the slave station. It can be understood that the establishment of the compression context in this application no longer relies solely on the network layer information at the terminal station level, but rather on the first connection identifier information carried in the EIP connection establishment request initiated by the master station to the slave station during the EIP connection establishment process, which uniquely identifies the EIP connection. This refines the granularity of the compression context to the individual EIP connection level. The master station synchronizes the compression context with the slave station, and both the master and slave stations can then compress and decompress the headers of subsequently received EIP packets based on the synchronized context. Therefore, the decompression end can accurately restore the complete header information of the EIP packet based on the synchronized context corresponding to a single EIP connection level. Attached Figure Description

[0019] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0020] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0021] Figure 1 This is a first flowchart illustrating the method for processing the EIP header in this application. Figure 2 A schematic diagram of a wired-wireless converged topology provided for Embodiment 1 of the EIP header processing method of this application; Figure 3 This is a schematic diagram of the second process of EIP header compression and decompression provided in Embodiment 1 of this application; Figure 4 This is a schematic diagram of a scenario provided in Embodiment 1 of this application; Figure 5 This is a third flowchart provided for Embodiment 4 of the method for processing the EIP header of this application; Figure 6 This is a schematic diagram of the fourth process of EIP header compression and decompression provided in Embodiment 4 of this application.

[0022] The purpose, features, and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0023] It should be understood that the specific embodiments described herein are merely illustrative of the technical solutions of this application and are not intended to limit this application.

[0024] To better understand the technical solution of this application, a detailed description will be provided below in conjunction with the accompanying drawings and specific implementation methods.

[0025] Based on this, embodiments of this application provide a method for processing EIP message headers, referring to... Figure 1 , Figure 1 This is a flowchart illustrating the first embodiment of the EIP header processing method of this application.

[0026] In this embodiment, the EIP header processing method includes steps S10 to S30: Step S10: During the connection establishment phase, a compressed context is generated based on the first connection identifier information carried in the EIP connection establishment request initiated by the master station to the slave station, wherein the first connection identifier information is used to uniquely identify the EIP connection. Step S20: Synchronize the compression context with the slave station so that the master station and slave station can compress and decompress the headers of subsequently received EIP messages according to the synchronized context.

[0027] It should be noted that the execution entity in this embodiment can be a master station, which can be a compression end or a decompression end. The master station belongs to the processing system of the EIP header. The processing system of the EIP header also includes a slave station. When the data is downlinked (i.e., the master station sends data to the slave station), the master station is the compression end and the slave station is the decompression end. When the data is uplinked (i.e., the slave station sends data to the master station), the slave station is the compression end and the master station is the decompression end.

[0028] Specifically, such as Figure 2 As shown, in the EIP header processing system, the master station (MS) is typically a PLC controller deployed in the control center; the slave station (TS) is typically a field-side I / O module or a smart device with communication capabilities. The master and slave stations are connected via a wireless link and communicate using the Ethernet / IP protocol.

[0029] Reference Figure 3Before the master station communicates with the slave station, multiple logical transmission channels need to be pre-configured for the slave station to support concurrent transmission of multiple EIP connections on a shared wireless link. Based on this, the master station formally initiates a communication session with a specific slave station by sending an EIP connection establishment request to the target slave station. Specifically, the EIP connection establishment process follows the CIP (Common Industrial Protocol) specification. The master station initiates the connection establishment process by sending an EIP connection establishment request to the slave station; for example, the master station initiates the connection establishment process by sending a Forward Open request message to the slave station. This Forward Open request message is a CIP explicit message and contains connection identification information to uniquely identify the connection.

[0030] It is understandable that when the master station initiates an EIP connection establishment request to the slave station, it enters the connection establishment phase. During the connection establishment phase, the master station uses the first connection identifier information carried in the EIP connection establishment request to the slave station in the following specific manner: when the master station initiates the EIP connection establishment request to the slave station, it confirms that it has entered the connection establishment phase; during the connection establishment phase, the master station parses and obtains the connection identifier information carried in the connection establishment request.

[0031] For example, the master station could capture the Forward Open request message corresponding to the EIP connection establishment request through methods such as listening, proxy forwarding, or protocol stack hooking. Then, by parsing the message structure, it could extract the aforementioned connection identification information. Since each EIP connection is unique within the EIP header processing system, the extracted connection identification information can accurately map to a specific master-slave communication session. Even if multiple slave stations share the same terminal station's wireless interface, logical-level connection differentiation can be achieved through this connection identification information.

[0032] The first connection identification information includes at least the CID (Connection ID, a unique 32-bit identifier assigned by the master station when initiating the connection), the initiating sequence number, the responding sequence number, and the connection sequence number. Since the connection identification information can uniquely identify an EIP connection, it distinguishes between EIP connections established between different slave stations and the master station after accessing the wireless network through the same terminal station.

[0033] Therefore, the current EIP connection can be uniquely identified based on the first connection identifier information.

[0034] Furthermore, in this embodiment, the master station generates a compression context based on the first connection identifier information. That is, it generates a corresponding compression context for the current single EIP connection. This compression context is used to record the packet header feature information related to the current EIP connection, which serves as the basis for subsequent packet header compression and decompression.

[0035] Specifically, the compression context may include at least one of the following: connection identifier field, compression strategy configuration, etc.

[0036] Furthermore, the master station synchronizes the compression context to the slave station to ensure that both ends perform compression / decompression processing based on the same context information during subsequent data transmission, thereby avoiding decompression failure or field misalignment due to context mismatch and ensuring communication reliability.

[0037] In this embodiment, during the connection establishment phase, the master station generates a compression context based on the first connection identifier information carried in the EIP connection establishment request initiated by the master station to the slave station. This refines the granularity of the compression context to the individual EIP connection level. Even if multiple slave stations share the same terminal station's wireless interface, the decompression end can accurately restore the complete header information of the EIP packet based on the synchronized context corresponding to the individual EIP connection level.

[0038] Based on the first embodiment of this application, in the second embodiment of this application, the content that is the same as or similar to that in Embodiment 1 above can be referred to the above description and will not be repeated hereafter. Based on this, the implementation method for generating the compression context according to the first connection identifier information can be: Parse the first connection identifier information to obtain the first connection identifier field; determine the current connection attribute based on the first connection identifier field; generate a compression context based on the current connection attribute.

[0039] To improve the efficiency of updating the compression context, after the master station receives the EIP connection establishment request sent by the master station, it performs structured parsing on the first connection identifier information carried in the EIP connection establishment request to obtain the first connection identifier field.

[0040] The first connection identifier field includes information such as the CID field, the initiating sequence number field, the responding sequence number field, and the connection sequence number. Based on this first connection identifier field, the connection attributes of the current EIP connection can be deduced. This current connection attribute can be understood as the relationship between the current connection request and the local context of the main site.

[0041] It should be noted that the current connection attributes include newly created connection, updated connection, and added connection; the compression context includes a first compression context, a second compression context, and a third compression context, and the first connection identifier field includes a device identifier field and a service identifier field. For example... Figure 4As shown, the device identifier field corresponds to Figure 4 The connection identifier field 1 and the business identifier field correspond to... Figure 4 The connection identifier field 2 in the document.

[0042] The device identification field includes the IP address and MAC address, while the service identification field includes the CID message. The device identification field is used to identify the network layer and link layer identity of the communication endpoint, and the service identification field is used to identify the specific EIP application layer session or service flow. Therefore, the device identification field and the service identification field in the first connection identification field can uniquely identify the terminal station, slave station, and service flow corresponding to the current connection.

[0043] Specifically, the implementation of generating a compression context based on the current connection attributes can be as follows: When the current connection attribute is a new connection, the generated content includes an initial connection identifier field, an initial connection identifier index, and a first compression context with initial compression parameters; when the current connection attribute is an updated connection, the generated content includes the initial connection identifier index and a second compression context with updated compression parameters; when the current connection attribute is an added connection, the generated content includes an added service identifier field, the initial connection identifier index, and a third compression context with added compression parameters.

[0044] When the current connection attribute is a newly established connection, the generated content includes an initial connection identifier field, an initial connection identifier index, and a first compression context with initial compression parameters. The initial connection identifier field is the complete first connection identifier field parsed from the EIP connection establishment request, and includes a device identifier field and a service identifier field. The initial connection identifier index is a unique local index key generated based on the connection identifier field, used for subsequent quick lookup and matching of this context. The initial connection identifier index includes a device identifier index and a service identifier index. The initial compression parameters include the I / O packet length (referring to the payload length of the periodic I / O data packets transmitted by the EIP connection) and the communication period (referring to the time interval between I / O data exchange between the master and slave stations), etc. The initial compression parameters refer to... Figure 4 2. Compressed information in the middle.

[0045] When a wireless link is briefly interrupted and reconnected, or when the master station initiates connection parameter adjustments, there may be a need to update the connection. To improve the efficiency of updating the compression context, when the current connection attribute is an update connection, the generated content only includes the initial connection identifier index and the updated compression parameters in the second compression context. It can be understood that in the scenario of updating the connection, by reusing the initial connection identifier index in the first compression context (original context), it is ensured that the master and slave stations can correctly associate with the first compression context based on the initial connection identifier index and obtain the unchanged fields from the original context. That is, unchanged fields do not need to be repeatedly updated or synchronized, thereby reducing resource overhead. Only the changed fields (updated compression parameters) are added to the second compression context, making it easier to update the changed fields to the original context later.

[0046] When a master station needs to establish multiple parallel business channels with the same slave station, or when a new logical slave station instance needs to be added under a terminal station, there may be a need to increase connections. To improve the efficiency of adding compression contexts, when the current connection attribute is "adding a connection," the generated content includes an added business identifier field, the initial connection identifier index, and a third compression context with added compression parameters. It can be understood that in the scenario of adding connections, by reusing the initial connection identifier index in the first compression context (original context), it is ensured that the master station and slave station can correctly associate with the first compression context based on the initial connection identifier index and obtain unchanged fields from the original context; that is, unchanged fields do not need to be repeatedly updated or synchronized, thereby reducing resource overhead. Only the changed fields (the added business identifier field and the added compression parameters) are added to the third compression context, making it easier to update the changed fields to the original context subsequently.

[0047] Alternatively, the current connection attribute can be determined by parsing the CIP connection management field in the connection identification information. The CIP connection management field includes the connection sequence number, connection path, RPI (RequestedPacket Interval), and CID. If the combination of connection sequence number and connection path has not appeared before, it is determined to be a new connection; if the same connection sequence number exists but the RPI changes from 10ms to 5ms, it is determined to be an updated connection; if the same connection path exists but the CID is different, it may be an added connection.

[0048] This embodiment distinguishes between three connection attributes: new, updated, and added, and dynamically generates a compressed context with structural adaptation. This not only improves the flexibility of context management but also significantly reduces the synchronization signaling overhead on the wireless air interface.

[0049] Specifically, the method for determining the current connection attribute based on the first connection identifier field may be as follows: Iterate through the main site's local context list and determine if there exists a local context that completely matches all field values ​​in the first connection identifier field. If there is no local context that matches any field value in the first connection identifier field, determine that the current connection attribute is a new connection. If there is a local context that completely matches all field values ​​in the first connection identifier field, determine that the current connection attribute is an update connection. If there is a local context that only matches some field values ​​in the first connection identifier field, determine that the current connection attribute is an add connection.

[0050] It is understandable that by traversing the main site's local context list and determining whether there exists a local context that completely matches all field values ​​in the first connection identifier field, the current connection attribute can be determined. Specifically, the main site's local context list includes compressed contexts corresponding to historical connections maintained by the main site, and all field values ​​in the first connection identifier field include device identifier field values ​​and service identifier field values.

[0051] According to the characteristics of the EIP protocol, the connection identifier field remains fixed throughout the entire transmission process, provided that both communicating parties agree on it. Therefore, the master station can accurately determine the connection attribute by comparing the connection identifier field in the connection establishment request with the corresponding field in the context maintained locally by the master station.

[0052] If there is no local context in the master station's local context list that matches any field value in the first connection identifier field, that is, if all field values ​​in the first connection identifier field do not match all field values ​​in the master station's local context list, it indicates that the connection request comes from a brand new master-slave device session, and the master station determines that the current connection attribute is a new connection.

[0053] If a local context exists that completely matches all field values ​​in the first connection identifier field, that is, all field values ​​in the first connection identifier field completely match all field values ​​of a certain context in the main station's local context list, it indicates that the connection request corresponds to an existing EIP session, and the main station determines that the current connection attribute is an update connection.

[0054] If a local context exists that matches only some of the field values ​​in the first connection identifier field, for example, a local compression context that matches only the device identifier field value in the first connection identifier field but not the service identifier field value, it indicates that the connection request shares some identity information with an existing context (e.g., a new slave station under the same terminal station, or a new service flow under the same master-slave device pair), the master station determines the current connection attribute as adding a connection.

[0055] Through the judgment mechanism, the main site can accurately identify the relationship between connection requests and existing contexts, thereby generating appropriate compressed contexts for different scenarios.

[0056] In this embodiment, by generating a compression context for the changed fields in both update and add scenarios, control signaling overhead is significantly reduced, wireless air interface bandwidth usage is lowered, and overall system throughput efficiency is improved.

[0057] Based on the first and second embodiments of this application, the same or similar content as the above embodiments in the third embodiment of this application can be referred to the above description and will not be repeated hereafter. Based on this, this embodiment provides two methods for generating compression contexts. In the first method, the main station generates a compression context independently based on the connection identifier information, and then performs compression context synchronization, as described above. Figure 3 In the second method for generating the compression context, the master station and the slave station each generate a compression context based on the connection identifier information, and then perform compression context synchronization, as described above. Figure 6 .

[0058] Specifically, the implementation method for context synchronization with the slave station based on the compression context includes at least one of the following: First, the compression context is updated in the local context list of the master station, and the compression context is sent to the slave station. When the context confirmation information is received from the slave station, the context synchronization is confirmed to be successful.

[0059] It is understandable that after generating the compressed context, the master station first updates the compressed context to the master station's local context list and sends the complete compressed context to the slave station through the control channel; when the master station receives the context confirmation information (e.g., ACK message) returned by the slave station, it determines that the context synchronization is successful.

[0060] Second, the compression context is updated in the master station's local context list, and the connection identifier index and connection identifier field in the compression context are sent to the slave station as the fourth compression context. The slave station can then use the connection identifier field in the fourth compression context to find the context to be improved from the slave station's local context list and fill the context to be improved with the connection identifier index in the fourth compression context to achieve context synchronization. The context to be improved includes a fifth compression context, which is generated by the slave station based on the second connection identifier information.

[0061] Understandably, in the second compression context generation method, after the master station generates the compression context and stores it in the master station's local context list, it does not directly send the complete context. Instead, it extracts the connection identifier index and connection identifier field, encapsulates them into a fourth compression context, and sends it to the slave station.

[0062] The slave station can generate the fifth compression context based on the second connection identifier information by: parsing the second connection identifier information to obtain the second connection identifier field, determining the connection attributes based on the second connection identifier field, and generating the fifth compression context based on the connection attributes.

[0063] After receiving the fourth compression context, the slave station combines the second connection identifier information parsed during the connection establishment phase (i.e., the identifier obtained locally from the EIP connection request, which has the same fields as the first connection identifier information) to generate the fifth compression context. The slave station then uses the connection identifier index and fields carried in the fourth compression context to complete the fifth compression context, thereby completing context synchronization.

[0064] This approach can reduce the air interface load of the management station and is suitable for smart gateway scenarios where the terminal station has certain protocol parsing capabilities.

[0065] Specifically, after confirming that context synchronization is successful or has been achieved, the following implementation methods also exist: When a downlink EIP message is received, the second connection identifier field in the EIP message is parsed. Based on the second connection identifier field, a unique context is determined from the local context list of the master station. The target device identifier index and the target service identifier index are determined based on the unique context corresponding to the master station. Based on the unique context corresponding to the master station, the header of the EIP message is compressed, and the target device identifier index and the target service identifier index are appended to the compressed header to form a compressed message. The compressed message is then sent to the slave station.

[0066] It is understandable that after the master station confirms that context synchronization is successful or completes context synchronization, the master station performs packet header compression or decompression operations during subsequent data transmission. Specifically, when the master station receives a downlink EIP packet, it first parses the second connection identifier field in the EIP packet. Based on the second connection identifier field, the master station performs a matching query in the master station's local context list to determine the unique corresponding compressed context. Since each EIP connection is globally unique in the system, and the context is indexed by the connection identifier field, this matching process can efficiently locate the unique context.

[0067] Based on the determined unique context, the master station further obtains the target device identifier index and the target service identifier index pre-stored in the unique context; wherein, the target device identifier index is used to identify the network identity of the communication endpoint, and the target service identifier index is used to identify the specific EIP service session.

[0068] Furthermore, the master station compresses the original header of the EIP message based on the compression parameters recorded in the unique context, retaining only dynamically changing fields (such as compression parameters); and fills the target device identifier index and target service identifier index into the compressed header as context indication information.

[0069] For example, the master station fills the generated context indication information into the compressed message header, replacing the original redundant connection identifier field, to form the final compressed message. This compressed message is then sent to the slave station. When the slave station receives the downlink EIP message, it decompresses the EIP message header based on this compressed message. This compressed message retains only dynamically changing fields and context indication information, significantly reducing header overhead.

[0070] It is understandable that when the master station receives the uplink EIP message, it decompresses the message header based on the compressed message sent by the slave station.

[0071] It should be noted that the two methods for generating the compressed context can be dynamically selected based on the actual network topology and resource constraints (such as air interface bandwidth and terminal computing power). For example, when the terminal station has protocol parsing capabilities, a collaborative approach between the master and slave stations to generate the context can reduce air interface resource overhead, avoid missing context information, and improve system scalability.

[0072] It is understood that in the second method of generating the compression context, this embodiment assumes that the authority to assign an index to the connection identifier field belongs to the management station, so as to achieve unified management of connection identifiers across the network and avoid index conflicts.

[0073] In this embodiment, two methods for generating compression contexts are provided. At the same time, by explicitly carrying the device identifier index and service identifier index in the compressed message, the slave station can quickly and unambiguously locate the complete compression context of the corresponding EIP connection even if it only observes the unified terminal station network information, thereby improving the decompression accuracy.

[0074] Based on the above embodiments, the fourth embodiment of this application also provides a method for processing EIP headers, referring to... Figure 5 , Figure 5 This is a flowchart illustrating the fourth embodiment of the EIP header processing method of this application. In this embodiment, the EIP header processing method further includes steps A10 to A20: Step A10: Receive context-related information sent by the master station, wherein the context-related information includes a compressed context, which is generated by the master station during the connection establishment phase based on the first connection identifier information in the EIP connection establishment request initiated from the master station to the slave station. The first connection identifier information is used to uniquely identify the EIP connection. Step A20: Synchronize the context with the master station based on the context-related information, so that the master station and slave station can compress and decompress the headers of subsequently received EIP messages based on the synchronized context.

[0075] It should be noted that the execution subject in this embodiment can be a slave station, which can be a compression end or a decompression end.

[0076] Specifically, the context-related information includes at least a compressed context, which is generated by the master station during the connection establishment phase based on the first connection identification information extracted from the EIP connection establishment request initiated from the master station to the slave station. The connection identification information is used to uniquely identify the EIP connection.

[0077] It is understandable that when the slave station receives context-related information sent by the master station, it can perform context synchronization with the master station based on the context-related information; when receiving EIP messages subsequently, the master station and the slave station can perform header compression and decompression processing based on the synchronized context.

[0078] Since the compression context is generated by the master station based on the first connection identification information obtained from the EIP connection establishment request initiated by the master station to the slave station, and the connection identification information is used to uniquely identify the EIP connection, the slave station can accurately decompress EIP packets from different slave stations but sharing the same terminal station radio interface based on the connection-level unique compression context.

[0079] In one feasible implementation, prior to the step of receiving context-related information sent by the master station, the method further includes: During the connection establishment phase, the second connection identifier information carried in the EIP connection establishment request initiated by the master station to the slave station is obtained; based on the second connection identifier information, a fifth compression context is generated.

[0080] It is understood that this embodiment provides two methods for generating compression contexts. In the first method, the master station generates a compression context solely based on the connection identifier information, and then performs compression context synchronization. In the second method, both the master station and the slave station generate compression contexts based on the connection identifier information, and then perform compression context synchronization.

[0081] In the first method of generating a compression context, the slave station can receive the compression context sent by the master station and perform context synchronization with the master station based on the compression context.

[0082] In the second method for generating the compression context, the slave station can synchronously obtain the second connection identifier information carried in the EIP connection establishment request initiated by the master station to the slave station during the connection establishment phase; and generate the fifth compression context based on the second connection identifier information. The specific generation method is the same as described in the above embodiments and will not be repeated here.

[0083] It is understood that the context-related information also includes a fourth compressed context, and the step of synchronizing the context with the main station based on the context-related information includes at least one of the following: First, the compressed context is updated in the slave station's local context list, and context confirmation information is sent back to the master station to achieve context synchronization.

[0084] Specifically, under the first compression context generation method, after receiving the compression context generated separately by the master station, the slave station updates the compression context to the slave station's local context list and sends context confirmation information back to the master station to achieve context synchronization.

[0085] Second, the slave station retrieves the context to be improved from its local context list based on the connection identifier field in the fourth compressed context, fills the context to be improved with the connection identifier index in the fourth compressed context, updates the improved context in the slave station's local context list, and sends context confirmation information back to the master station to achieve context synchronization. The fourth compressed context is the context sent locally by the master station using the connection identifier index and connection identifier field in the compressed context. The context to be improved includes the fifth compressed context.

[0086] Specifically, under the second compression context generation method, the slave station has generated a fifth compression context based on the second connection identifier information obtained locally. After receiving the fourth compression context sent by the master station (i.e., the connection identifier index and connection identifier field extracted by the master station from the compression context), the slave station searches for the context to be improved in its local context list according to the connection identifier field in the fourth compression context, and fills the context to be improved with the connection identifier index in the fourth compression context to form a complete context entry. Subsequently, the improved context is updated to the slave station's local context list, and context confirmation information is sent back to the master station to achieve bidirectional collaborative synchronization.

[0087] Furthermore, after the step of synchronizing the context with the main station based on the context-related information, the method further includes: When a compressed message is received from the master station, the target device identifier index and the target service identifier index in the compressed message are parsed; based on the target device identifier index and the target service identifier index, a unique context is determined from the slave station's local context list; based on the unique context corresponding to the slave station, the compressed message is decompressed to obtain a decompressed EIP message, and the decompressed EIP message is sent to the target device.

[0088] It is understood that after completing the step of context synchronization with the master station based on the aforementioned context-related information, the slave station performs message decompression during the data transmission phase. Specifically, when receiving a compressed message sent by the master station, the slave station first parses the target device identifier index and the target service identifier index carried in the compressed message. The target device identifier index is used to identify the network identity of the communication endpoint, and the target service identifier index is used to identify the specific EIP service session.

[0089] Subsequently, the slave station performs a joint matching query in its local context list based on the target device identifier index and the target service identifier index to determine the unique corresponding compressed context. Since the indexes are uniformly allocated by the master station and are globally unique, this matching process can efficiently and unambiguously locate the target context.

[0090] Next, the slave station decompresses the compressed message based on the determined unique context to restore the original EIP message. Specifically, the slave station removes the index field used to indicate the context from the compressed message; at the same time, it fills in and reconstructs the connection identifier field and compression information extracted from the unique context according to the protocol format of the original EIP message header, thereby restoring a complete EIP message header consistent with that of the master station.

[0091] Finally, the slave station forwards the decompressed complete EIP message to the corresponding target device, completing end-to-end communication. During downlink data transmission, the target device is the slave station; during uplink data transmission, the target device is the master station.

[0092] Through the above mechanism, even if multiple slave stations share the same terminal station's wireless air interface address, the slave station can still accurately locate the context unique to each EIP connection using dual indexes, ensuring that the packet header is accurately restored, which significantly improves the reliability and scalability of EIP communication in industrial wireless converged networks.

[0093] For example, to help understand the implementation flow of the EIP header processing method obtained in this embodiment in conjunction with the above embodiments, please refer to... Figure 3 . Figure 3 This diagram illustrates the first step of the EIP header compression and decompression process.

[0094] Specifically, under the first method of generating the compression context, such as Figure 3 As shown, when an EIP connection establishment request message (e.g., a Forward Open message) arrives, the master station (management station) first parses the connection identification information carried in it. This information includes, but is not limited to, IP address, MAC address, and CIP protocol layer parameters (such as CID, connection sequence number, etc.). Subsequently, the slave station (terminal station) determines the current connection attributes (such as new, updated, or added) based on the connection identification information, extracts the relevant message header fields, and fills them to generate the corresponding compressed context.

[0095] Next, the master station sends the compression context as context-related information to the slave station. After receiving the context confirmation information returned by the slave station, the master station confirms that the context synchronization is successful and can then enter the compression working state.

[0096] For subsequent data packets belonging to this EIP connection, the master station identifies static or redundant fields (such as fixed IP, MAC, port, etc.) in the packet header based on the synchronized compression context, omits or encodes them as differential information, and retains only dynamically changing fields; at the same time, it appends the corresponding context identifier (such as device identifier index and service identifier index) to the compressed packet header to form a compressed group and sends it to the slave station.

[0097] Accordingly, on the slave side, it first receives and saves the compression context sent by the master station. Subsequently, whenever a new connection establishment request message is received, the slave station also parses the connection identification information within it and determines whether its local context needs to be updated (e.g., due to changes in I / O cycles or packet length caused by connection renegotiation). By ensuring that the local context is always the latest received valid version, the slave station can maintain complete context synchronization with the master station. This allows it to accurately reconstruct the original EIP header based on the correct context after receiving compressed packets, ensuring reliable execution of the compression and decompression process.

[0098] This process enables end-to-end collaboration from connection establishment and context synchronization to data compression / decompression, effectively supporting efficient and unambiguous EIP communication in scenarios where multiple slave stations share the wireless interface of the terminal station.

[0099] For example, to help understand the implementation flow of the EIP header processing method obtained in this embodiment in conjunction with the above embodiments, please refer to... Figure 6 . Figure 6 This diagram illustrates a second process for compressing and decompressing EIP message headers.

[0100] Specifically, in the second method of generating a compressed context, the MS local context is generated first. The MS obtains the local context information by parsing the connection establishment request message and saves it into the context list.

[0101] This process performs local context maintenance for establishing new connections, adding connections, and updating connections respectively: For local context maintenance of newly created connections, when creating a new context, the local context maintained by MS should include connection identifier field 1, connection identifier field 2, the index of connection identifier field 1 and the index of connection identifier field 2, as well as compression information.

[0102] Regarding context updates, connection establishment updates in EIP typically involve changes to compression information such as I / O packet length and period. During a context update, the MS locates the context to be updated in its local context list based on Connection Identifier Field 1 and Connection Identifier Field 2, and replaces the compression information fields in the context to be updated with the corresponding fields from the connection establishment request.

[0103] The process for adding a context is the same as for creating a new connection. When a new local context needs to be added, MS will generate a new context, which includes connection identifier field 1, connection identifier field 2, the index of connection identifier field 1 and the index of connection identifier field 2 (used to distinguish different connection information), and compression information.

[0104] TS generates a local context through the connection establishment request, and its generation method is the same as that on the MS side. However, the difference is that TS does not include the connection identifier 1 index and connection identifier 2 index when generating the context.

[0105] MS and TS can parse the context from the connection establishment request message and store it locally; the purpose of sending the compressed context over the air interface is to send the connection identifier 1 index and the connection identifier 2 index, so that the context lists maintained locally by MS and TS have the same identifier index.

[0106] Specifically, the compressed context sent by the MS over the air interface includes fields such as Connection Identifier 1 index, Connection Identifier 2 index, Connection Identifier Field 1, and Connection Identifier Field 2. Subsequently, the TS receives the compressed context sent by the MS over the air interface. Based on Connection Identifier Field 1 and Connection Identifier Field 2 in the air interface message, the TS searches for the context to be completed in its locally generated context list (i.e., both have the same Connection Identifier Field 1 and Connection Identifier Field 2). Then, the TS fills the locally stored context with the Connection Identifier Field 1 index and Connection Identifier Field 2 index from the air interface message, thus completing the context consistency synchronization.

[0107] It should be noted that the above examples are only for understanding this application and do not constitute a limitation on the processing method of the EIP header of this application. Any simple modifications based on this technical concept are within the protection scope of this application.

[0108] This application also provides a system for processing EIP message headers; please refer to [reference needed]. Figure 2 The EIP header processing system includes a master station and a slave station. When data is transmitted downstream, the master station is the compression end and the slave station is the decompression end. When data is transmitted upstream, the slave station is the compression end and the master station is the decompression end. When data is transmitted downlink, during the connection establishment phase, the master station generates a compression context based on the first connection identifier information carried in the EIP connection establishment request initiated by the master station to the slave station, and sends context-related information to the slave station. The first connection identifier information is used to uniquely identify the EIP connection, and the context-related information includes the compression context. The slave station receives the context-related information sent by the master station and performs context synchronization with the master station based on the context-related information.

[0109] The EIP header processing system provided in this application, employing the EIP header processing method described in the above embodiments, effectively addresses the technical problem of accurately restoring the complete header information of EIP packets. Compared with the prior art, the beneficial effects of the EIP header processing system provided in this application are the same as those of the EIP header processing method provided in the above embodiments, and other technical features of the EIP header processing system are the same as those disclosed in the methods of the above embodiments, and will not be repeated here.

[0110] The above descriptions are merely some embodiments of this application and do not limit the scope of protection of this application. Any equivalent structural transformations made based on the technical concept of this application and the content of this specification and drawings, or direct / indirect applications in other related technical fields, are included within the scope of protection of this application. All actions involving the acquisition of signals, information, or data in this application are performed in accordance with the relevant data protection laws and policies of the country where the application is located and with authorization from the owner of the corresponding device.

Claims

1. A method for processing EIP message headers, characterized in that, When applied to the main station, the method for processing the EIP header includes: During the connection establishment phase, a compressed context is generated based on the first connection identifier information carried in the EIP connection establishment request initiated by the master station to the slave station. The first connection identifier information is used to uniquely identify the EIP connection. Based on the compression context, the master station and slave station perform context synchronization so that the master station and slave station can compress and decompress the headers of subsequently received EIP messages according to the synchronized context.

2. The EIP header processing method as described in claim 1, characterized in that, The step of generating a compressed context based on the first connection identifier information carried in the EIP connection establishment request initiated by the master station to the slave station includes: Parse the first connection identifier information to obtain the first connection identifier field; The current connection attributes are determined based on the first connection identifier field; Generate a compression context based on the current connection attributes.

3. The EIP header processing method as described in claim 2, characterized in that, The current connection attributes include new connection, updated connection, and added connection; the compression context includes a first compression context, a second compression context, and a third compression context; the first connection identifier field includes a device identifier field and a service identifier field; the step of generating a compression context based on the current connection attributes includes: When the current connection attribute is a newly established connection, the generated content includes an initial connection identifier field, an initial connection identifier index, and a first compression context with initial compression parameters; When the current connection attribute is an update connection, the generated content includes the initial connection identifier index and the updated compression parameters in a second compression context; When the current connection attribute is "add connection", the generated content includes the added service identifier field, the initial connection identifier index, and the third compression context of the added compression parameters.

4. The EIP header processing method as described in claim 2, characterized in that, The step of determining the current connection attribute based on the first connection identifier field includes: Iterate through the main site's local context list and determine whether there exists a local context that completely matches all field values ​​in the first connection identifier field; If no local context exists that matches any value in the first connection identifier field, then the current connection attribute is determined to be a new connection. If a local context exists that exactly matches all field values ​​in the first connection identifier field, then the current connection attribute is determined to be an update connection; If a local context exists that matches only some of the field values ​​in the first connection identifier field, then the current connection attribute is determined to be adding a connection.

5. The EIP header processing method as described in claim 1, characterized in that, The step of synchronizing the context with the slave station based on the compression context includes at least one of the following: The compression context is updated to the local context list of the master station, and the compression context is sent to the slave station. When the context confirmation information is received from the slave station, it is determined that the context synchronization is successful. The compression context is updated in the master station's local context list, and the connection identifier index and connection identifier field in the compression context are sent to the slave station as the fourth compression context. The slave station can then use the connection identifier field in the fourth compression context to find the context to be improved from the slave station's local context list and fill the context to be improved with the connection identifier index of the fourth compression context, thereby achieving context synchronization. The context to be improved includes a fifth compression context, which is generated by the slave station based on the second connection identifier information.

6. The EIP header processing method as described in claim 5, characterized in that, After confirming that context synchronization was successful or that context synchronization was achieved, the following steps are also included: When a downlink EIP message is received, the second connection identifier field in the EIP message is parsed, and a unique context is determined from the local context list of the master station based on the second connection identifier field. The target device identifier index and the target service identifier index are determined based on the unique context corresponding to the main station; Based on the unique context corresponding to the master station, the header of the EIP message is compressed, and the target device identifier index and the target service identifier index are appended to the compressed header to form a compressed message, which is then sent to the slave station.

7. A method for processing EIP message headers, characterized in that, When applied to slave stations, the method for processing the EIP header includes: Receive context-related information sent by the master station, wherein the context-related information includes a compressed context, which is generated by the master station during the connection establishment phase based on the first connection identifier information in the EIP connection establishment request initiated from the master station to the slave station, and the first connection identifier information is used to uniquely identify the EIP connection; Based on the context-related information, the master station and slave station perform context synchronization so that the master station and slave station can compress and decompress the headers of subsequently received EIP messages according to the synchronized context.

8. The method for processing the EIP header as described in claim 7, characterized in that, Before the step of receiving context-related information sent by the master station, the method further includes: During the connection establishment phase, the second connection identifier information carried in the EIP connection establishment request initiated by the master station to the slave station is obtained; A fifth compression context is generated based on the second connection identifier information.

9. The method for processing the EIP header as described in claim 8, characterized in that, The context-related information also includes a fourth compression context, and the step of synchronizing the context with the main station based on the context-related information includes at least one of the following: The compressed context is updated in the slave station's local context list, and context confirmation information is sent back to the master station to achieve context synchronization; Based on the connection identifier field in the fourth compression context, the context to be improved is retrieved from the slave station's local context list, and the connection identifier index in the fourth compression context is filled into the context to be improved. The improved context is then updated in the slave station's local context list, and context confirmation information is sent back to the master station to achieve context synchronization. The fourth compression context is the one sent by the master station to the local station using the connection identifier index and connection identifier field in the compression context. The context to be improved includes the fifth compression context.

10. The method for processing the EIP header as described in claim 9, characterized in that, After the step of synchronizing the context with the main site based on the context-related information, the method further includes: When a compressed message is received from the master station, the target device identifier index and the target service identifier index in the compressed message are parsed. Based on the target device identifier index and the target service identifier index, a unique context is determined from the slave station's local context list; Based on the unique context corresponding to the slave station, the compressed message is decompressed to obtain the decompressed EIP message, and the decompressed EIP message is sent to the target device.

11. A system for processing EIP message headers, characterized in that, The EIP header processing system includes a master station and a slave station. When data is transmitted downstream, the master station is the compression end and the slave station is the decompression end. When data is transmitted upstream, the slave station is the compression end and the master station is the decompression end. When data is transmitted downlink, during the connection establishment phase, the master station generates a compression context based on the first connection identifier information carried in the EIP connection establishment request initiated by the master station to the slave station, and sends context-related information to the slave station. The first connection identifier information is used to uniquely identify the EIP connection, and the context-related information includes the compression context. The slave station receives the context-related information sent by the master station and performs context synchronization with the master station based on the context-related information.

Images