PON-based multi-protocol communication method and equipment

Abstract

The invention discloses a PON-based multi-protocol communication method and device, and the method comprises the steps: distributing a corresponding internal scheduling time slot to each network protocol processing unit for data uploading to each network protocol processing unit when a data processing module detects that the network protocol processing units connected with each field bus device have to-be-uploaded service data; and when one internal scheduling time slot is used up, interrupting the uploading of the service data until the next internal scheduling time slot allocated to the internal scheduling time slot is recovered from interrupting the uploading of the data. And the PON module monitors a global scheduling time slot allocation instruction issued by the optical line terminal in real time, converts an uploaded data frame into an electric signal, transmits the electric signal to the optical module through an internal link, converts the electric signal into an optical signal through the optical module in an allocated global scheduling time slot, and uploads the optical signal to the optical line terminal through an optical distribution network. Real-time performance and orderliness of transmission of service data in multiple field bus devices in a PON network are achieved, the requirement of industrial communication for data transmission is met, and transmission resource distribution is optimized.

Description

Technical Field

[0001] This invention relates to the field of industrial control technology, and in particular to a multi-protocol communication method and device based on PON. Background Technology

[0002] Currently, in information transmission between control equipment in process industries, some products use fieldbuses such as Profibus-DP, Modbus, and CAN, while others use switches. The former consumes a large amount of copper wire and suffers from drawbacks such as short transmission distance, low transmission rate, and poor anti-interference capability, failing to meet the market's demand for long-distance, high-bandwidth transmission. The latter can only achieve point-to-point fiber optic signal transmission; when there are many dispersed points in the field, a large number of optical fibers are needed for connection, significantly increasing the number of fiber optic transmission devices and increasing the difficulty and cost of on-site construction and subsequent maintenance. Furthermore, different devices and fields use various types of fieldbuses, each requiring the development of corresponding communication modules. Besides the high development costs, this also significantly impacts the space and power supply of field devices. In addition, PON networks, due to their high bandwidth and wide coverage, have become an important carrier network for industrial remote communication. However, existing technologies have limitations in adapting to data transmission from multiple fieldbus devices and coordinating with PON networks. These limitations include single-protocol units easily monopolizing transmission resources, leading to data delays; lack of coordination with PON global scheduling; and susceptibility to transmission conflicts, making it difficult to meet the needs of real-time, orderly industrial data transmission. Summary of the Invention

[0003] To address the shortcomings of existing technologies, this invention discloses a multi-protocol communication method based on PON for use in multi-protocol communication devices. The multi-protocol communication device includes an optical module, a PON module, and a data processing module, and comprises the following steps:

[0004] When the data processing module detects that the network protocol processing unit connected to each fieldbus device has service data to be uploaded, it allocates the corresponding internal scheduling time slot to each network protocol processing unit for its own data upload; and interrupts the upload of the service data when an internal scheduling time slot is used up, until the next internal scheduling time slot allocated to it resumes the interrupted data upload.

[0005] The PON module encapsulates the standard Ethernet frames containing service data received from the data processing module according to the PON protocol to form upload data frames.

[0006] The PON module monitors the global scheduling time slot allocation command issued by the optical line terminal in real time, converts the uploaded data frame into an electrical signal and transmits it to the optical module through the internal link, and then converts the electrical signal into an optical signal through the optical module within the allocated global scheduling time slot before uploading it to the optical line terminal through the optical distribution network.

[0007] Preferably, when the data processing module detects that the network protocol processing units connected to each fieldbus device have service data to be uploaded, it allocates corresponding internal scheduling time slots to each network protocol processing unit for their respective data uploads; and interrupts the upload of the service data when an internal scheduling time slot is exhausted, until the next internal scheduling time slot allocated to it resumes the interrupted data upload, including:

[0008] The data processing module monitors the data transmission requests of each network protocol processing unit and determines the real-time requirement of the corresponding data transmission request based on the request code in the data transmission request according to the preset priority filtering rules.

[0009] Add data requests with high real-time requirements to the internal priority queue, and add data requests with low real-time requirements to the internal regular queue.

[0010] When executing internal scheduling time slots, the data processing module checks whether there are any pending data transmission requests in the internal priority queue. If there are, it continuously allocates corresponding internal scheduling time slots to each data transmission request in the priority queue until the internal priority queue is empty. After there are no pending data transmission requests in the internal priority queue, it allocates corresponding internal scheduling time slots to each data transmission request in the internal ordinary queue.

[0011] Preferably, the data processing module interrupts the upload of the service data when an internal scheduling time slot is exhausted, and resumes the interrupted data upload only when the next internal scheduling time slot is allocated to it. Specifically, this includes:

[0012] If the data processing module detects that the corresponding network protocol processing unit is still uploading and sending data when an internal scheduling time slot is exhausted, it will take the currently transmitted data packet as the last packet of the internal scheduling time slot, interrupt the remaining data upload of the network protocol processing unit, and start receiving data transmission from another network protocol processing unit in the next internal scheduling time slot; the upload of the interrupted data in the previous time slot will be resumed when the next cycle of internal scheduling time slot allocated to the network protocol processing unit arrives.

[0013] Preferably, the PON-based multi-protocol communication method further includes: the PON module parses the electrical signal received by the optical module and determines whether the transmission target of the signal received by the optical module is the device itself. If it is not the device itself, it is filtered out; otherwise, the electrical signal is converted into an Ethernet protocol frame and sent to the data processing module.

[0014] Preferably, the PON-based multiprotocol communication method further includes:

[0015] The data processing module sorts the network data packets sent by the PON module according to the network type and destination port number, and assigns them to the corresponding network protocol processing unit or character device processing unit for processing.

[0016] After receiving the network data packet, the character device processing unit parses it based on a custom protocol format and verifies the parsing result based on the data length, checksum, and header information. If the verification passes, it checks whether the device data is valid. If valid, it sends it to the corresponding device processing unit.

[0017] This invention also discloses a multi-protocol communication device, comprising an optical module, a PON module, and a data processing module, wherein:

[0018] The data processing module is configured to allocate corresponding internal scheduling time slots to each network protocol processing unit for data uploading when it detects that the network protocol processing unit connected to each fieldbus device has service data to be uploaded; and to interrupt the uploading of the service data when an internal scheduling time slot is used up, until the next internal scheduling time slot allocated to it resumes the interrupted data uploading.

[0019] The PON module is configured to encapsulate and process standard Ethernet frames containing service data received from the data processing module according to the PON protocol to form upload data frames; and to monitor the global scheduling time slot allocation instructions issued by the optical line terminal in real time, convert the upload data frames into electrical signals and transmit them to the optical module through the internal link, and then convert the electrical signals into optical signals through the optical module within the allocated global scheduling time slots, and then upload them to the optical line terminal through the optical distribution network.

[0020] Preferably, the data processing module is configured to monitor the data transmission requests of each network protocol processing unit, determine the real-time requirement of the corresponding data transmission request based on the request code in the data transmission request according to a preset priority filtering rule; add the data transmission requests with high real-time requirements to the internal priority queue, and add the data transmission requests with low real-time requirements to the internal ordinary queue; and when executing the internal scheduling time slot, check whether there are any pending data transmission requests in the internal priority queue. If so, continuously allocate corresponding internal scheduling time slots to each data transmission request in the priority queue until the internal priority queue is empty; after there are no pending data transmission requests in the internal priority queue, allocate corresponding internal scheduling time slots to each data transmission request in the internal ordinary queue.

[0021] Preferably, the data processing module is configured to, when an internal scheduling time slot is exhausted, if it detects that the corresponding network protocol processing unit is still uploading and sending data, then take the currently transmitted data packet as the last packet of the internal scheduling time slot, interrupt the remaining data uploading of the network protocol processing unit, and start receiving data transmission from another network protocol processing unit in the next internal scheduling time slot; until the next cycle of internal scheduling time slot allocated to the network protocol processing unit arrives, the uploading of data interrupted in the previous time slot is resumed.

[0022] Preferably, the PON module is further configured to parse the electrical signal received by the optical module and determine whether the transmission target of the signal received by the optical module is the device itself. If it is not the device itself, it is filtered out; otherwise, the electrical signal is converted into an Ethernet protocol frame and sent to the data processing module.

[0023] Preferably, the data processing module includes a network protocol processing unit, a Profinet device processing unit, a Modbus-TCP device processing unit, an Ethernet IP device processing unit, a character device processing unit, a CAN device processing unit, a Profibus-DP device processing unit, and a Modbus-RTU device processing unit. The network protocol processing unit can forward data frames sent by the PON module to the Profinet device processing unit, Modbus-TCP device processing unit, Ethernet IP device processing unit, or character device processing unit. The character device processing unit, upon receiving a data frame, parses it based on a custom protocol format and verifies the parsing result based on data length, checksum, and header information. If the verification passes, it checks whether the device data is valid. If valid, it sends the data to the corresponding CAN device processing unit, Profibus-DP device processing unit, or Modbus-RTU device processing unit.

[0024] This invention discloses a PON-based multi-protocol communication method and device. When a data processing module detects that network protocol processing units connected to various fieldbus devices have service data to upload, it allocates corresponding internal scheduling time slots to each network protocol processing unit for data upload. When an internal scheduling time slot is exhausted, the upload of the service data is interrupted until the next internal scheduling time slot is allocated to it, at which point the interrupted data upload resumes. The PON module encapsulates the standard Ethernet frames containing service data received from the data processing module according to the PON protocol to form upload data frames. The PON module monitors the global scheduling time slot allocation command issued by the optical line terminal in real time, converts the upload data frame into an electrical signal, transmits it to the optical module through an internal link, and then converts the electrical signal into an optical signal through the optical module within the allocated global scheduling time slot before uploading it to the optical line terminal via the optical distribution network. By utilizing internal scheduling time slot allocation, the monopolization of transmission resources by a single network protocol processing unit is avoided, effectively solving the latency problem when multiple protocol data are uploaded concurrently. At the same time, through the real-time monitoring and coordination of global scheduling time slots by the PON module, the collaboration between multi-protocol data upload and global scheduling of the PON network is realized, avoiding uplink transmission conflicts and achieving real-time and orderly transmission of service data from multiple fieldbus devices in the PON network. This meets the requirements of industrial communication for data transmission latency and optimizes the allocation of transmission resources.

[0025] Additional aspects and advantages of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. Attached Figure Description

[0026] The accompanying drawings, which are included to provide a further understanding of the invention and form part of this application, illustrate exemplary embodiments of the invention and, together with their description, serve to explain the invention and do not constitute an undue limitation thereof. In the drawings:

[0027] Figure 1 This is a schematic diagram of the steps of a PON-based multi-protocol communication method disclosed in an embodiment of the present invention.

[0028] Figure 2 This is a schematic diagram illustrating the data processing principle of a data processing module disclosed in an embodiment of the present invention.

[0029] Figure 3 This is a schematic diagram of the data uplink principle of the network protocol processing unit disclosed in an embodiment of the present invention.

[0030] Figure 4 This is a schematic diagram of the time slot allocation and scheduling principle of the PON protocol processing unit disclosed in an embodiment of the present invention.

[0031] Figure 5This is a schematic diagram of the data uplink principle of the PON protocol processing unit disclosed in an embodiment of the present invention.

[0032] Figure 6 This is a schematic diagram of the downlink data principle of the PON protocol processing unit disclosed in an embodiment of the present invention.

[0033] Figure 7 This is a schematic diagram of the downlink data principle of the network protocol processing unit disclosed in an embodiment of the present invention.

[0034] Figure 8 This is a schematic diagram of a custom data protocol for a character device processing unit disclosed in an embodiment of the present invention.

[0035] Figure 9 This is a schematic diagram of the downlink data processing unit of a character device according to an embodiment of the present invention.

[0036] Figure 10-13 This is a schematic diagram of the various structures of a multi-protocol communication device disclosed in an embodiment of the present invention. Detailed Implementation

[0037] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. All other embodiments obtained by those skilled in the art based on the described embodiments of the present invention without creative effort are within the scope of protection of the present invention.

[0038] Unless otherwise defined, the technical or scientific terms used herein shall have the ordinary meaning as understood by one of ordinary skill in the art to which this invention pertains. The terms “first,” “second,” and similar terms used in the specification and claims of this patent application do not indicate any order, quantity, or importance, but are merely used to distinguish different components. Similarly, the terms “an” or “a” and similar terms do not indicate a limitation of quantity, but rather indicate the presence of at least one.

[0039] A PON-based multi-protocol communication method is provided for a multi-protocol communication device, which includes an optical module, a PON module, and a data processing module.

[0040] In this embodiment, as shown in the appendix Figure 1 As shown, the PON-based multiprotocol communication method may specifically include the following steps.

[0041] Step S1: When the data processing module detects that the network protocol processing unit connected to each fieldbus device has service data to be uploaded, it allocates a corresponding internal scheduling time slot to each network protocol processing unit for its own data upload; and interrupts the upload of the service data when an internal scheduling time slot is used up, until the next internal scheduling time slot allocated to it resumes the interrupted data upload.

[0042] Specifically, the data processing module of the multi-protocol communication device monitors the service data upload requests of each network protocol processing unit in real time. Each network protocol processing unit is connected to a fieldbus device. When a target network protocol processing unit is detected to have service data to upload, the data processing module allocates a corresponding internal scheduling time slot to support its service data upload. During the service data upload process, if the currently allocated internal scheduling time slot is exhausted, the service data upload operation of the target network protocol processing unit is interrupted until the data processing module allocates the next internal scheduling time slot, at which point the interrupted upload process resumes.

[0043] In this embodiment, as shown in the appendix Figure 2 As shown, step S1 can specifically include the following:

[0044] Step S11: The data processing module monitors the data transmission requests of each network protocol processing unit and determines the real-time requirement of the corresponding data transmission request based on the request code in the data transmission request according to the preset priority filtering rules.

[0045] The data processing module of the multi-protocol communication device continuously monitors the data transmission requests initiated by each network protocol processing unit and uses the request code carried in the data transmission request as the basis for judgment according to the preset priority filtering rules. Through the real-time correlation attribute corresponding to the request code, it determines the real-time requirement level of each data transmission request and clarifies whether the data transmission request belongs to the category of high real-time requirement or low real-time requirement.

[0046] Specifically, during the monitoring process, the data processing module synchronously collects the request code carried in each data transmission request. This request code is an information carrier that represents the real-time requirement of the data. It carries attribute characteristics that are directly related to the real-time nature of data transmission. By obtaining this request code, the data processing module provides a unique and clear information basis for determining the real-time requirement level of subsequent data transmission requests.

[0047] The preset priority filtering rules are specifically constructed based on the correspondence logic between request codes and real-time requirements. The mapping logic between the real-time association attributes of request codes and the real-time requirement level is predefined. The differences in real-time requirements of data requests are directly distinguished by the attribute characteristics of the request codes, dividing them into two different real-time requirement levels: high real-time requirement and low real-time requirement. At the same time, corresponding request code attribute thresholds are matched for the two real-time requirement levels, forming a fixed and unified filtering standard to ensure that the data processing module has a consistent logical framework for judging the real-time performance of data requests.

[0048] After obtaining the request code for sending data, the data processing module initiates a real-time requirement level determination process based on preset priority filtering rules: by identifying and matching the real-time related attributes carried by the request code, the attribute characteristics of the request code are compared with the real-time requirement level mapping relationship defined in the rules. If the real-time related attributes of the request code meet the threshold definition of high real-time requirement in the rules, the data sending request is determined to belong to the high real-time requirement category; if the real-time related attributes of the request code meet the threshold definition of low real-time requirement in the rules, the data sending request is determined to belong to the low real-time requirement category.

[0049] Step S12: Add data requests with high real-time requirements to the internal priority queue, and add data requests with low real-time requirements to the internal ordinary queue.

[0050] After determining the real-time requirement level of each data transmission request, the data processing module categorizes and queues the requests according to their real-time requirement level. Data transmission requests deemed to have high real-time requirements are added one by one to a preset priority queue within the data processing module; data transmission requests deemed to have low real-time requirements are added one by one to a preset ordinary queue within the data processing module, thus achieving orderly categorized storage of data transmission requests with different real-time requirements.

[0051] Step S13: When the data processing module executes the internal scheduling time slot, it detects whether there are any pending data transmission requests in the internal priority queue. If there are, it continuously allocates corresponding internal scheduling time slots to each data transmission request in the priority queue until the internal priority queue is empty. After there are no pending data transmission requests in the internal priority queue, it allocates corresponding internal scheduling time slots to each data transmission request in the internal ordinary queue.

[0052] When the data processing module enters the internal scheduling time slot allocation process, it first checks the status of the internal priority queue to determine if there are any unprocessed data transmission requests in the priority queue. If unprocessed data transmission requests are detected in the priority queue, the data processing module continuously allocates corresponding internal scheduling time slots to each data transmission request in the priority queue in sequence until all unprocessed data transmission requests in the priority queue have completed time slot allocation and the processing flow has progressed, at which point the priority queue is in an empty queue state. When there are no unprocessed data transmission requests in the priority queue, the data processing module then switches to the internal ordinary queue and allocates corresponding internal scheduling time slots to each data transmission request in the ordinary queue that is queued in the order of request time.

[0053] Specifically, in another embodiment, as shown in the appendix Figure 3 As shown, the network protocol processing unit within the data processing module continuously checks whether different device processing units have network packets to send: First, it checks whether the Profinet device processing unit has network packets to send; if so, it allocates a transmission time slot and waits for the transmission to complete. Next, it checks whether the Modbus-TCP device processing unit has network packets to send; if so, it also allocates a transmission time slot and waits for the transmission to complete. Then, it checks whether the EthernetIP device processing unit has network packets to send; if so, it allocates a transmission time slot and waits for the transmission to complete. Finally, it checks whether the character device processing unit has network packets to send; if so, it allocates a transmission time slot and waits for the transmission to complete. If a device processing unit has no network packets to send, it directly proceeds to the next device processing unit's check process, and so on, ensuring that network packets are sent in an orderly manner by each device processing unit.

[0054] In another embodiment, the preset priority filtering rule uses the request code carried in the data transmission request as the basis for judgment. The request code is an unsigned number of one byte, which can be used as a quantitative identifier representing the real-time requirement of the data transmission request. The mapping logic between the request code value and the real-time requirement includes: the value of the request code is negatively correlated with the real-time requirement of the data transmission request, that is, the smaller the request code value, the higher the corresponding real-time requirement; the larger the request code value, the lower the corresponding real-time requirement. At the same time, a value threshold of 128 for the request code is set as the dividing line between real-time requirement levels: when the request code value is less than 128, the data transmission request is determined to be a priority request with high real-time requirement; when the request code value is greater than or equal to 128, the data transmission request is determined to be a normal request with low real-time requirement. For the priority requests and normal requests determined above, the priority requests are assigned to a preset internal priority queue, and the normal requests are assigned to a preset internal normal queue, so as to achieve physical isolation of data transmission requests with different real-time requirements at the queue level.

[0055] As attached Figure 4As shown, the scheduling priority of the internal priority queue is higher than that of the internal ordinary queue. That is, when the data processing module performs time slot allocation, it first checks whether there are any pending requests in the internal priority queue. If there are pending requests in the internal priority queue, it continuously allocates internal scheduling time slots for requests in that queue until the internal priority queue is empty. Only when there are no pending requests in the internal priority queue are internal scheduling time slots allocated to requests in the internal ordinary queue, ensuring that requests with high real-time requirements receive transmission resources first. For the internal priority queue and the internal ordinary queue, the internal sorting is based on the request initiation time. That is, data transmission requests within the same queue are queued according to the order in which they were initiated, waiting for time slot allocation, to avoid delays in processing of earlier-initiated requests within the same queue due to the insertion of later-initiated requests.

[0056] In this embodiment, step S1 may further include: if the data processing module detects that the corresponding network protocol processing unit is still uploading and sending data when an internal scheduling time slot is exhausted, it takes the currently transmitted data packet as the last packet of the internal scheduling time slot, interrupts the remaining data uploading of the network protocol processing unit, and starts receiving data transmission from another network protocol processing unit in the next internal scheduling time slot; until the internal scheduling time slot allocated to the network protocol processing unit for the next cycle arrives, the uploading of the interrupted data in the previous time slot is resumed.

[0057] During the internal scheduling time slot management and data transmission control process of the data processing module in a multi-protocol communication device, when the termination time of the currently allocated internal scheduling time slot is detected to be approaching, the data processing module monitors the service data transmission status of the network protocol processing unit corresponding to that time slot in real time to determine whether it is still in the data uploading stage. If it is detected that the network protocol processing unit is still uploading data, the data processing module marks the currently transmitted data packet as the terminating data packet of that internal scheduling time slot; after the terminating data packet is sent, the uploading process of the remaining service data of the network protocol processing unit is immediately terminated, thereby preventing a single network protocol processing unit from monopolizing transmission resources and ensuring the transmission of other network protocol processing units. After terminating the remaining data uploading of the target network protocol processing unit, the data processing module immediately switches to the resource allocation and data reception process of the next internal scheduling time slot, and starts the reception operation of the service data to be uploaded by another network protocol processing unit, realizing the orderly rotation of transmission resources among the network protocol processing units. For network protocol processing units whose data upload has been interrupted, the data processing module will track them according to the preset time slot period allocation; the data upload process that was interrupted in the previous time slot will be resumed when the next internal scheduling time slot allocated to the network protocol processing unit is started.

[0058] Step S2: The PON module encapsulates the standard Ethernet frame containing service data received from the data processing module according to the PON protocol to form an upload data frame.

[0059] As attached Figure 5 As shown, the PON module of the multi-protocol communication device first receives a standard Ethernet frame transmitted by the data processing module. This standard Ethernet frame carries the service data of the fieldbus device. The PON protocol processing unit integrated inside the PON module initiates the PON protocol encapsulation process. According to the PON protocol specifications, it performs format conversion and data encapsulation operations on the received standard Ethernet frame. By adding key structures such as header information and check fields required by the PON protocol, the frame structure originally adapted for Ethernet transmission is transformed into a frame structure that conforms to the PON network transmission specifications, generating an upload data frame that can be transmitted in the PON network.

[0060] Step S3: The PON module monitors the global scheduling time slot allocation command issued by the optical line terminal in real time, converts the uploaded data frame into an electrical signal and transmits it to the optical module through the internal link, and then converts the electrical signal into an optical signal through the optical module within the allocated global scheduling time slot before uploading it to the optical line terminal through the optical distribution network.

[0061] The PON module continuously monitors the global scheduling time slot allocation commands issued by the optical line terminal (OLT) in real time, accurately obtaining the uplink transmission time window allocated by the OLT for the multi-protocol communication device, ensuring the synchronization of data transmission with the PON network scheduling rhythm. After detecting and confirming the allocated global scheduling time slot, the PON module performs electrical signal conversion processing on the upload data frame encapsulated according to the PON protocol, converting the upload data frame conforming to the PON protocol specification into an electrical signal adapted for internal link transmission. Through the preset internal link between the PON module and the optical module, the electrical signal is stably transmitted to the optical module. During the effective period of the global scheduling time slot allocated by the OLT, the optical module activates the photoelectric conversion function, converting the received electrical signal into an optical signal that meets the transmission requirements of the PON network. This optical signal is transmitted through the optical distribution network and accurately uploaded to the OLT, completing the uplink transmission of service data from the multi-protocol communication device to the OLT.

[0062] The PON module also prioritizes each uploaded data frame containing service data using a similar priority allocation method as described in steps S11 to S13 above. Specifically, it determines the real-time requirement of the corresponding data transmission request based on the request code in the data transmission request; it adds data transmission requests with high real-time requirements to an external priority queue and adds data transmission requests with low real-time requirements to an external ordinary queue.

[0063] While waiting for the Optical Line Terminal (OLT) to allocate an uplink time slot to this device, when the PON module detects that a global scheduling time slot has been allocated to this device, the PON module first sends the corresponding PON protocol data frame from the external priority queue to the optical module via an electrical signal. The optical module then converts the electrical signal into an optical signal and uploads it to the OLT via the optical distribution network. Within this global scheduling time slot, the PON module continuously forwards and uploads each PON protocol data frame from the external priority queue to the OLT until the external priority queue is empty or the global scheduling time slot ends. If the external priority queue is empty but the global scheduling time slot has not yet ended, the PON module continues to send the corresponding PON protocol data frame from the external ordinary queue to the optical module via an electrical signal. The optical module then converts the electrical signal into an optical signal and uploads it to the OLT via the optical distribution network until the external ordinary queue is empty or the global scheduling time slot ends. If the optical module is still transmitting signals when the global scheduling time slot ends, the currently transmitting data packet will be used as the last packet of the global scheduling time slot, interrupting the remaining data transmission of the optical module. The transmission of the interrupted data will resume in the next global scheduling time slot. In one specific embodiment, each field device sends a request along with a one-byte unsigned number as a request code. The larger the number, the lower the real-time requirement, with 0 being the highest and 255 the lowest. Requests greater than or equal to 128 are considered normal requests, and those less than 128 are considered priority requests. Real-time requirements can be distinguished based on the request code. Requests with low real-time requirements enter the normal queue, while those with high real-time requirements enter the priority queue. Under normal circumstances, each queue can be queued according to the request time, waiting for time slot allocation.

[0064] Furthermore, business feature identification can be used to extract and classify the features of industrial business data; by analyzing the metadata carried by the data frame, including the equipment identification and data type information mentioned in the previous document, and the business attributes extracted from the data content, such as periodic instructions for production process control, sudden alarm information generated when equipment is abnormal, and non-real-time collected data for subsequent statistical analysis, industrial business can be divided into three different types for different time slot allocation: (1) Periodic high-reliability business, which is mostly control instructions to ensure continuous production operation and has extremely high requirements for transmission cycle stability and reliability; (2) Sudden high-priority business, which mainly includes information that needs to be handled urgently, such as equipment fault alarms, and is highly sensitive to transmission delay; (3) Non-real-time ordinary business, which is mostly equipment status statistical data with a long cycle and has relatively low requirements for transmission timeliness. For each type of business, key feature parameters are further marked, including the cycle requirements of business operation, the maximum tolerable delay of data transmission, and the fluctuation range of data volume, to provide accurate basis for subsequent time slot allocation.

[0065] For the aforementioned sudden high-priority services and non-real-time ordinary services, a service-aware dynamic time slot allocation mechanism can be added to the existing time slot allocation rules of the PON module to achieve precise matching of time slot resources with the actual needs of industrial services. Specifically, this can include the following steps.

[0066] Step S101: A fixed range of time slot resources is allocated on the optical line terminal (OLT) side as a shared time slot pool. The basic parameters of this shared time slot pool are configured according to requirements. The shared time slot pool is configured to carry non-real-time ordinary service data transmission. The basic parameters include, but are not limited to, the starting time slot number, the total number of time slots, and the minimum guaranteed time slot ratio for ordinary services. The minimum guaranteed time slot ratio for ordinary services can be no less than 30%. Non-real-time ordinary services can be statistical services with low transmission timeliness requirements and allowable delays (e.g., a maximum tolerable delay of no more than 300 seconds). Their data is generated by the character device processing unit or network protocol processing unit of the data processing module within the multi-protocol communication equipment, and transmission has no fixed cycle. Examples include routine data in process industries such as equipment temperature statistics and energy consumption data. These services are generated by the data processing module within the multi-protocol communication equipment, and transmission requests are initiated by the multi-protocol communication equipment. Furthermore, the total number of time slots in the shared time slot pool needs to be set based on the estimated amount of ordinary service data from the on-site multi-protocol communication equipment, and its time slot range should not overlap with the reserved time slot segments for periodic services.

[0067] In step S102, the PON module receives the time slot request frame sent by the data processing module and sends the time slot request frame to the optical module via an electrical signal. The optical module then converts the electrical signal into an optical signal and forwards it to the optical line terminal (OLT). The time slot request frame contains the device ID, service type marker, and encapsulated data length.

[0068] In step S103, the optical line terminal (OLT) parses the time slot request frame. If the service type in the time slot request frame is marked as "normal", it queries the number of currently available time slots in the shared time slot pool. If the available time slots are greater than the time slots required for data transmission, it allocates a corresponding number of idle time slots from the shared time slot pool and feeds back to the optical module of the multi-protocol communication device through a time slot allocation response frame. The time slot required for data transmission is defined as data length / PON link rate / time slot duration, where the service type in the time slot request frame for non-real-time normal service data is marked as "normal".

[0069] Specifically, the currently available time slots in the shared time slot pool are the number of unoccupied and uncompressed time slots in the pool. After the data processing module within the multi-protocol communication device generates Ethernet frames for service data, it hands them over to its internal PON module for encapsulation into PON protocol request frames, which are then sent to the Optical Line Terminal (OLT) via the optical module. If multiple multi-protocol communication devices simultaneously request ordinary service time slots, the OLT allocates them according to the order of request time, ensuring that the waiting time for each request does not exceed 10 seconds.

[0070] Step S104: If the service type in the time slot request frame is marked as high priority, then the time slot request frame is treated as a burst high priority service request frame. The number of compressible time slots in the shared time slot pool is calculated. The number of compressible time slots is the current total number of available time slots in the shared time slot pool minus the minimum guaranteed time slots for ordinary services. If the number of compressible time slots is greater than the time slots required for data transmission of the time slot request frame, then the available time slots in the shared time slot pool are compressed to the minimum guaranteed time slots for ordinary services, and the released compressible time slots are allocated to the burst high priority service.

[0071] The high-priority emergency service can be an alarm or control service that requires urgent transmission due to equipment malfunction in the process industry. Urgent transmission can refer to a maximum tolerable latency of ≤10ms, and its service type is actively identified by the data processing module of the multi-protocol communication device in the request frame. The compression rule for the shared time slot pool can be configured such that the available time slots in the compressed shared time slot pool must not be less than 30% of the total number of time slots, thereby preventing ordinary services of the multi-protocol communication device from being unable to obtain time slots for extended periods.

[0072] Step S105: After the PON module receives the service end identifier frame corresponding to the high-priority service in the burst sent by the data processing module, it forwards it to the optical line terminal (OLT) through the optical module. The OLT restores the available time slots in the shared time slot pool to the number before compression. For ordinary service requests that did not obtain time slots during compression, it prioritizes allocating the restored idle time slots to ensure that the average waiting time of ordinary services does not exceed a set period. The set period can be 30 seconds. The service end identifier frame carries a transmission end marker. The OLT completes the restoration of the shared time slot pool within 1 second after receiving the service end identifier frame to avoid idle time slot resources.

[0073] In another embodiment, for periodic high-reliability services, such as valve opening adjustment commands and motor speed control signals, characteristic parameters corresponding to these services can be pre-configured. These characteristic parameters include at least the unique identifier of the multi-protocol communication device to which the service belongs, the service transmission period, the single-frame data length, and the maximum tolerable latency. Periodic high-reliability services are control-type services that ensure continuous operation of process industry production and have high requirements for transmission period stability and reliability. Their transmission period is fixed, and the maximum tolerable latency does not exceed 50ms. For services where the transmission period needs to be longer than a single frame of data, and for different periodic services under the same device ID, their characteristic parameters need to be configured separately and stored in the OLT-side database. The theoretical minimum transmission time = single-frame data length / PON link transmission rate.

[0074] Step S201: On the optical line terminal (OLT) side, according to the priority order of service transmission cycle from small to large, allocate continuous fixed time slots for each periodic high-reliability service to form a mapping table containing device ID, service type and corresponding reserved time slots; the reserved time slots include time slot start number and time slot number, and the reserved time slots of different services do not overlap.

[0075] The reserved time slots are continuous time slot intervals allocated from the total time slot resources on the OLT side, dedicated to the transmission of a specific periodic high-reliability service. The duration of each time slot is preset according to the PON link rate, such as 2ms / time slot. If the reserved time slot requirement of a newly configured service conflicts with the allocated time slots, the OLT side automatically adjusts the reserved time slots for subsequent services, regenerates the mapping table, and overwrites the original stored data.

[0076] In step S202, the line terminal (OLT) embeds the reserved time slot information corresponding to each device ID in the mapping table into the header extension of the PON protocol initialization configuration frame and sends it to each multi-protocol communication device corresponding to the device ID. The reserved time slot information serves as a reserved time slot identifier, allowing the multi-protocol communication device to identify its dedicated time slot.

[0077] The OLT establishes a direct communication link with the multi-protocol communication device via the ODN. The reserved time slot identifier is a global configuration of the multi-protocol communication device by the OLT. The header extension bit is an additional field in the frame header that conforms to the PON protocol specification and does not affect the compatibility of the original frame structure. Its length is 8 bytes, with the first 4 bytes storing the time slot start number and the last 4 bytes storing the number of time slots. The reserved time slot identifier is sent once when the multi-protocol communication device is powered on and initialized. If the characteristic parameters are subsequently adjusted, the OLT will resend the updated reserved time slot identifier. After receiving the identifier, the multi-protocol communication device will pass it to its subordinate data processing module through the internal bus.

[0078] In step S203, the PON module of each multi-protocol communication device continuously monitors the usage status of each reserved time slot, including time slot occupancy rate and data frame integrity. Data frame integrity is verified and detected by the data processing module before data transmission. If the idle rate of a reserved time slot exceeds a set percentage for multiple consecutive service cycles, or the data frame loss rate exceeds a set value, an alarm signal is sent to the OLT-side maintenance platform. For example, if statistics show that the idle rate of a reserved time slot exceeds 80% for five consecutive service cycles, or the data frame loss rate exceeds 1%, an alarm signal is sent to the OLT-side maintenance platform. The idle rate is the ratio of the number of time slots within the reserved time slot that have not transmitted valid data to the total number of time slots in that time slot. The valid data refers to service data generated by the data processing module within the multi-protocol communication device that conforms to the fieldbus protocol. After receiving the alarm signal on the OLT side, the length of the reserved time slot for that service can be adjusted based on maintenance instructions, releasing redundant time slots to the shared time slot pool, thereby improving the overall utilization rate of the entire PON time slot resource.

[0079] The aforementioned time slot allocation mechanism, through reservation and flexible adjustment, addresses periodic high-reliability services by pre-planning dedicated fixed time slot segments. This allows the device to directly use reserved time slots for data transmission without initiating additional time slot requests during the corresponding service period, effectively ensuring deterministic latency for such services. For ordinary services, a flexible time slot adjustment strategy is employed. A shared time slot pool is configured for non-real-time ordinary services. When a sudden high-priority service occurs, the available time slots in the shared time slot pool are appropriately compressed, ensuring that the compression does not lead to a prolonged lack of transmission resources for ordinary services. Simultaneously, the compressed and released time slots are prioritized for allocation to the sudden high-priority service to meet its urgent transmission needs. After the high-priority service transmission is completed, the original capacity of the shared time slot pool is restored, guaranteeing the normal transmission rights of ordinary services.

[0080] The data processing module also includes a fine-grained data flow tracing and rollback mechanism. This mechanism is integrated into the data processing module and establishes a bidirectional data interaction link with each protocol processing unit within the module to perform fine-grained data flow tracing. Specifically, it includes the following steps.

[0081] Step S301: After receiving the data frame, the data processing module assigns a globally unique data frame identifier to the data frame and parses it, records the process status of each parsing and processing node and generates a processing trajectory log. The process status includes protocol parsing progress, industrial bus protocol type identification result, verification method and intermediate result, format conversion status, time slot application status and link identifier.

[0082] Specifically, the data processing module generates a globally unique data frame identifier for each data frame entering the module. This identifier is composed of a unique universal identification code for the device pre-stored in the data processing module, a frame reception timestamp generated by high-precision clock synchronization, and a random sequence. This identifier flows synchronously with the data frame to each processing unit within the module. Step-level status recording is performed at each processing node in the entire process of protocol parsing, data verification, format encapsulation, and transmission within the data processing module. This step-level status recording records the key states of the data frame at each processing node, including protocol parsing, data verification, format encapsulation, and transmission. The recorded content includes protocol parsing progress, industrial bus protocol type identification results, verification methods and intermediate results, format conversion status, time slot application status, and link identifier. All status data carries the data frame identifier and step timestamp, and is written to the data storage unit of the data processing module in real time, generating a refined and traceable processing trajectory log.

[0083] The processing nodes specifically include: a protocol parsing node: recording the parsing start / completion timestamp, the parsing completion rate of key fields in the PON protocol frame header, the industrial bus protocol type identification result, and the protocol version information; a data verification node: recording the verification algorithm type, such as CRC32, MD5, parity check, intermediate calculated values ​​during the verification process, verification results, and the difference data bit identifier when failure occurs; a format encapsulation node: recording the field mapping progress between standard Ethernet frames and industrial protocol frames, such as source address, destination address, data field conversion status, encapsulation operation start / completion status, and integrity verification result of the encapsulated frame structure; and a transmission sending node: recording the sending time of the PON time slot request command, the time slot request response result, including success / timeout / rejection, time slot allocation number, and the link identifier of the optical module / fieldbus interface, such as port number and link rate.

[0084] Step S302: Detect whether there is an abnormal situation in the data frame. If an abnormality is detected in the data frame processing, a data stream rollback operation is performed. The data stream rollback operation includes constructing a state chain graph for the abnormal data frame based on its processing trajectory log, identifying the most recent valid state branch, and then issuing a local re-execution instruction to the corresponding processing unit.

[0085] Specifically, if an anomaly is triggered in data frame processing, such as a checksum mismatch, data length exceeding the limit, or time slot application timeout, the mechanism will persistently store the processing trajectory of the data frame, forming a data flow log that can be queried through the data frame identifier index, providing a basis for anomaly localization. Simultaneously, the data flow rollback function in the mechanism is activated, querying the data flow log through the data frame identifier to construct a state chain graph of the data frame, marking the success or failure status and key parameters of each step, such as error codes and request codes. Based on preset priority filtering rules, the nearest correct state branch is identified, and then a partial re-execution instruction is sent to the corresponding processing unit within the module. When sub-message verification fails, only the character device processing unit is triggered to read the original data from the fieldbus interface module cache and re-execute the verification and conversion. When the format encapsulation is incorrect, only the network protocol processing unit is notified to re-execute the encapsulation based on the parsed data, avoiding full-process retransmission.

[0086] Step S303: Extract the priority queue identifier field from the extended frame header of the data frame to be retransmitted, and determine the priority queue to which the data frame belongs by comparing it with the preset priority filtering rules of the data processing module. The priority queue can be divided into multiple sub-queues from high to low according to the request code threshold. If it is determined to be a high-priority sub-queue, the mechanism sends a priority time slot request tag to the PON protocol processing unit in the data processing module. The PON protocol processing unit increases its time slot priority according to the preset priority filtering rules and prioritizes the allocation of uplink resources. If there are no free time slots, a pre-request is made.

[0087] The internal priority queue obtained based on the preset priority filtering rules can be further divided into multi-level sub-queues. Each sub-queue is divided in descending order of the request code threshold: Fault Alarm Sub-queue: Highest priority, mainly carrying equipment fault alarm data, such as hardware failures, communication link interruptions, and over-threshold alarms. This type of data has the highest urgency and must be transmitted and processed first to support the industrial system's rapid response to abnormal states; its priority is the highest among all data frames. Emergency Control Command Sub-queue: Second highest priority, containing real-time control commands, such as equipment start / stop commands and emergency parameter adjustment commands. This type of data directly affects the operating status of industrial field equipment and requires millisecond-level transmission latency. It takes priority over non-control data in scheduling. If a rollback and re-execution are triggered, a high-priority time slot can be requested simultaneously to reduce control latency. Real-time Monitoring Sub-queue: Medium priority, covering high-frequency real-time monitoring data, such as equipment operating parameters and real-time sensor sampling values. This type of data needs to maintain temporal continuity to support system status assessment. Its scheduling priority is lower than control commands but higher than non-real-time data. During retransmission, the time slot application priority is dynamically adjusted according to its sampling period; the higher the sampling frequency, the higher the retransmission priority. High-priority configuration sub-queues have the lowest priority and primarily carry data such as device configuration updates and parameter synchronization. While important, this type of data has lower timeliness requirements and only acquires scheduling resources when there is no need for higher-priority data transmission. During retransmission, time slot applications are initiated according to a preset period to avoid consuming critical business resources. Each sub-queue is precisely distinguished through a frame header priority identifier field. The data processing module dynamically adjusts time slot allocation based on the above hierarchical rules to ensure that high-priority data receives priority processing in both normal transmission and abnormal rollback scenarios, adapting to the differentiated timeliness requirements of different business data in industrial scenarios.

[0088] If a data frame is determined to be in the priority queue, such as a data frame containing a device fault alarm or an emergency control command, the mechanism immediately sends a priority time slot request flag to the PON protocol processing unit within the data processing module. The flag frame structure includes a globally unique identifier of the data frame to be retransmitted, its priority level, and the estimated time for local re-execution completion. After receiving the priority time slot request flag, the PON protocol processing unit, according to a preset priority filtering rule, raises the time slot request priority of the data frame to the highest level in the current request queue. When receiving a global scheduling time slot allocation command from the optical line terminal (OLT), it prioritizes matching uplink time slot resources for the data frame. If there are no free time slots in the current period, it triggers a time slot pre-request to reserve a time slot of the corresponding priority for the next period. The mechanism obtains the progress data of local re-execution in real time. When it detects that the re-execution operation is completed and the data frame meets the transmission conditions, it immediately sends a transmission ready signal to the PON protocol processing unit. The PON protocol processing unit then converts the data frame into an uplink data frame conforming to the PON protocol within the allocated priority time slot and uploads it to the optical line terminal through the optical module.

[0089] In this embodiment, as shown in the appendix Figure 6 As shown, the PON-based multiprotocol communication method may also include:

[0090] In step S4, the PON module parses the electrical signal received by the optical module and determines whether the target of the signal received by the optical module is this device. If it is not this device, it is filtered out; otherwise, the electrical signal is converted into an Ethernet protocol frame and sent to the data processing module.

[0091] The optical module receives optical signals transmitted from the optical distribution network and converts them into electrical signals adapted for processing by the PON module. The converted electrical signals are then transmitted to the PON module via a pre-defined link between the optical module and the PON module. The PON module initiates its signal processing procedure. Its integrated PON protocol processing unit parses the received electrical signals and extracts the PON protocol data frames contained within the signals according to the PON protocol specifications, ensuring accurate acquisition of complete information within the data frames. After parsing the PON protocol data frames, the PON protocol processing unit further extracts target identification information from the data frames, using this identification information to determine the current connection of the optical module. The PON module determines whether the target of the received signal is the local multi-protocol communication device. If the target is not the local device, the PON module filters out the PON protocol data frame corresponding to the signal according to the data filtering mechanism, without performing subsequent data processing and transmission. If the target is the local device, the PON protocol processing unit performs format conversion processing on the parsed PON protocol data frame, converting it into a standard Ethernet protocol frame. Then, the converted Ethernet protocol frame is sent to the data processing module through the internal transmission link between the PON module and the data processing module, realizing the downlink data transmission of the PON protocol processing unit.

[0092] In this embodiment, step S4 may also include the following:

[0093] The data processing module sorts the network data packets sent by the PON module according to the network type and destination port number, and assigns them to the corresponding network protocol processing unit or character device processing unit for processing.

[0094] After receiving the network data packet, the character device processing unit parses it based on a custom protocol format and verifies the parsing result based on the data length, checksum, and header information. If the verification passes, it checks whether the device data is valid. If valid, it sends it to the corresponding device processing unit.

[0095] After receiving network data packets transmitted by the PON module, the data processing module initiates a data sorting process. It uses the network type information and destination port number carried by the network data packets as the basis for judgment. By identifying and matching these two types of information, it clarifies the processing requirements corresponding to each network data packet: if the data packet needs to be processed by network protocol-related logic, it is assigned to the corresponding network protocol processing unit; if the data packet needs to be processed by character device-related logic, it is assigned to the character device processing unit, thereby achieving accurate routing of network data packets according to processing type.

[0096] Specifically, in another embodiment, as shown in the appendix Figure 7 As shown, the network protocol processing unit receives network data and checks its Ethernet type field. If the Ethernet type is 0x8892, the network data packet is allocated to the Profinet device processing unit. If the Ethernet type is not 0x8892, it continues to check if it is 0x0800. When the Ethernet type is 0x0800, the destination port number field of the network data is further parsed. If the destination port number is 0xAF12 or 0x08AE, the network data packet is allocated to the EthernetIP device processing unit. If the destination port number is neither 0xAF12 nor 0x08AE, it continues to check if it is 0x01f6. If it is, the network data packet is allocated to the Model-TCP device processing unit. If the Ethernet type and port number matching conditions are not met, the network data packet is allocated to the character device processing unit, thus realizing the downlink data processing of the network protocol processing unit.

[0097] After receiving the allocated network data packet, the character device processing unit parses the data packet according to a preset custom protocol format, extracting the core data and associated identification information within the data packet. After parsing, the character device processing unit sequentially initiates a multi-dimensional verification process: first, it verifies the data length of the parsed data to confirm whether the data length conforms to the valid range specified by the custom protocol; second, it verifies the checksum to verify the integrity and accuracy of the data through preset verification rules; simultaneously, it verifies the packet header information to ensure the validity and correctness of key information such as the header identifier and version. If all three verifications pass, the character device processing unit further checks whether the parsed device data conforms to the business logic and data specifications of the corresponding fieldbus device to determine the validity of the device data. If the device data is valid, the character device processing unit sends the device data to the corresponding device processing unit, providing data support for the business interaction between the device processing unit and the fieldbus device.

[0098] As attached Figure 8As shown, the custom protocol format for the character device processing unit data includes the structure of the received network data frame. The data frame consists of four parts: an 8-byte custom header, a 256-byte CAN data frame, a 512-byte Profibus-DP or Modbus-RTU data, and a 4-byte checksum.

[0099] In another embodiment, as shown in the appendix Figure 9 As shown, the character device processing unit first performs a length check operation on the network data. If the length check does not conform to the valid range specified by the custom protocol, the current data processing flow is terminated and an error is fed back. If the length check conforms to the valid range specified by the custom protocol, the next step is to check the checksum. If the checksum fails, the process is terminated and an error is fed back. After the checksum is verified, the header information is checked to see if it meets the requirements. If the header information does not conform to the preset specification, the process is terminated. After the network data passes all the above pre-checks, the protocol data validity determination and distribution are performed: on the one hand, the validity of the CAN protocol data is verified. If the verification is successful, the CAN protocol data is forwarded to the CAN device processing unit. On the other hand, the validity of the Profibus-DP / Modbus-RTU protocol data is verified. If the verification is successful, the protocol type is further distinguished based on the specific fields and structural characteristics of the message. If it is determined to be Profibus-DP protocol data, it is forwarded to the Profibus-DP device processing unit. If it is determined to be Modbus-RTU protocol data, it is forwarded to the Modbus-RTU device processing unit, thus realizing the downlink data transmission of the character device processing unit.

[0100] The PON-based multi-protocol communication method enables compatible access of multiple fieldbus protocols to the PON network. It optimizes transmission resource allocation through hierarchical time slot scheduling, thereby improving bandwidth utilization. Combined with multi-dimensional data verification and target device filtering, it ensures data integrity and validity. At the same time, it reduces uplink transmission latency, meeting the real-time and reliable transmission requirements of multi-protocol data in industrial scenarios.

[0101] As attached Figure 10As shown, another embodiment also discloses a multi-protocol communication device, which includes an optical module 1, a PON module 2, and a data processing module 3. The data processing module 3 is configured to allocate corresponding internal scheduling time slots to each network protocol processing unit when it detects service data to be uploaded by the network protocol processing units connected to various fieldbus devices; and to interrupt the upload of the service data when an internal scheduling time slot is exhausted, until the next internal scheduling time slot allocated to it resumes the interrupted data upload. The PON module 2 is configured to encapsulate the received standard Ethernet frames containing service data from the data processing module according to the PON protocol to form upload data frames; and to monitor the global scheduling time slot allocation command issued by the optical line terminal in real time, convert the upload data frames into electrical signals and transmit them to the optical module through an internal link, and then convert the electrical signals into optical signals through the optical module 1 within the allocated global scheduling time slot before uploading them to the optical line terminal via the optical distribution network.

[0102] In another embodiment, such as Figure 11 As shown, the multi-protocol communication device is configured as follows: optical fiber is accessed via an optical module, and the optical module and PON module achieve physical layer connection; the PON module integrates a storage module unit and a minimum system unit, and completes data interaction with the PHY interface of the data processing module through the physical layer PHY interface; the data processing module is configured with the storage module unit and the minimum system unit, and internally integrates CAN interface, Ethernet interface, RS-485 interface and fieldbus interface module, which is compatible with protocols such as CAN, Profinet, Modbus-TCP, EtherNetIP, Profibus-DP, Modbus-RTU; the data processing module is also connected to an interface selection module to realize the interface selection and configuration functions; the PON module and the data processing module are respectively connected to the power management module to obtain power supply and power management support.

[0103] In another embodiment, such as Figure 12As shown, the multi-protocol communication equipment is integrated into a multi-protocol communication system, which comprises three parts: a control cabinet, an optical distribution network (ODN), and a remote I / O cabinet. The control cabinet integrates a controller and an optical line terminal (OLT). The OLT is connected to the ODN with a splitting ratio of 1:64 or 1:128 via optical fiber. The ODN is connected to the multi-protocol communication module in the remote I / O cabinet via optical fiber. The multi-protocol communication module interfaces with field I / O modules supporting bus protocols such as CAN (Controller Area Network), and connects to bus instruments based on protocols such as Modbus-RTU, Modbus-TCP, Profinet, and EtherNetIP, as well as various types of field instruments, such as Field Instrument Type 1, Field Instrument Type 2, and Field Instrument Type 3, thereby enabling data interaction and transmission between multi-protocol industrial field devices.

[0104] In this embodiment, the data processing module 3 is configured to monitor the data transmission requests of each network protocol processing unit, determine the real-time requirement of the corresponding data transmission request based on the request code in the data transmission request according to a preset priority filtering rule; add the corresponding data transmission requests with high real-time requirements to the internal priority queue, and add the corresponding data transmission requests with low real-time requirements to the internal ordinary queue; when executing the internal scheduling time slot, detect whether there are any pending data transmission requests in the internal priority queue, and if so, continuously allocate the corresponding internal scheduling time slot to each data transmission request in the priority queue until the internal priority queue is empty; after there are no pending data transmission requests in the internal priority queue, allocate the corresponding internal scheduling time slot to each data transmission request in the internal ordinary queue.

[0105] The data processing module avoids high real-time data transmission latency by using hierarchical queue management based on real-time requirements and priority-driven scheduling, ensuring the time determinism of data transmission in industrial scenarios and improving the efficiency of transmission resource scheduling.

[0106] In this embodiment, the data processing module 1 can also be configured to, when an internal scheduling time slot is exhausted, if it is detected that the corresponding network protocol processing unit is still uploading and sending data, take the currently transmitted data packet as the last packet of the internal scheduling time slot, interrupt the remaining data uploading of the network protocol processing unit, and start receiving data transmission from another network protocol processing unit in the next internal scheduling time slot; until the next cycle of internal scheduling time slot allocated to the network protocol processing unit arrives, the uploading of data interrupted in the previous time slot will be resumed.

[0107] By using time-slot interruption and recovery, transmission resources are time-division multiplexed, avoiding single-protocol processing units from monopolizing resources, ensuring fairness in data transmission among multiple units, and ensuring the complete continuation of interrupted data, thereby improving the concurrent processing capability of multiple protocols.

[0108] In this embodiment, the PON module 2 can be further configured to parse the electrical signal received by the optical module and determine whether the transmission target of the signal received by the optical module is this device. If it is not this device, it is filtered out; otherwise, the electrical signal is converted into an Ethernet protocol frame and sent to the data processing module.

[0109] In this embodiment, the data processing module 3 can be configured as needed and may include a network protocol processing unit, a Profinet device processing unit, a Modbus-TCP device processing unit, an Ethernet IP device processing unit, a character device processing unit, a CAN device processing unit, a Profibus-DP device processing unit, or a Modbus-RTU device processing unit. The network protocol processing unit can forward data frames sent by the PON module to the Profinet device processing unit, Modbus-TCP device processing unit, Ethernet IP device processing unit, or character device processing unit. The character device processing unit, upon receiving a data frame, parses it based on a custom protocol format and verifies the parsing result based on data length, checksum, and header information. If the verification passes, it checks whether the device data is valid; if valid, it sends it to the corresponding CAN device processing unit, Profibus-DP device processing unit, or Modbus-RTU device processing unit.

[0110] Specifically, such as Figure 13 As shown, the PON module has a built-in PON protocol processing unit that interacts with the protocol identification and processing unit of the data processing module. The protocol identification and processing unit of the data processing module has the function of identifying and distributing multiple industrial protocols, including EtherNetIP, Modbus-TCP, and EtherNet. It forwards data to the corresponding EtherNetIP, Modbus-TCP, EtherNet, and flat-layer protocol processing units for processing. The EtherNetIP and Modbus-TCP protocol processing units are connected to the network interface circuit. The flat-layer protocol processing unit is further subdivided into CAN, Profinet, EtherNetIP, and Modbus-TCP protocol processing units. The CAN protocol processing unit interfaces with the CAN interface circuit, while the Profinet and Modbus-TCP protocol processing units interface with the RS485 interface circuit, thus enabling the identification, processing, and interface adaptation of multiple types of industrial protocols.

[0111] The functions of the aforementioned multi-protocol communication device basically correspond to the steps of the PON-based multi-protocol communication method disclosed in the previous embodiments, so they will not be described in detail here. For details, please refer to the previously disclosed embodiments of the PON-based multi-protocol communication method. It should be noted that the various embodiments in this specification are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. The same or similar parts between the various embodiments can be referred to mutually.

[0112] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

[0113] In summary, the above description is only a preferred embodiment of the present invention. All equivalent changes and modifications made within the scope of the claims of the present invention should be covered by the present invention.

Claims

1. A PON-based multi-protocol communication method for use in a multi-protocol communication device, the multi-protocol communication device comprising an optical module, a PON module, and a data processing module, characterized in that, Includes the following steps: When the data processing module detects that the network protocol processing unit connected to each fieldbus device has service data to be uploaded, it allocates the corresponding internal scheduling time slot to each network protocol processing unit for its own data upload; and interrupts the upload of the service data when an internal scheduling time slot is used up, until the next internal scheduling time slot allocated to it resumes the interrupted data upload. The PON module encapsulates the standard Ethernet frames containing service data received from the data processing module according to the PON protocol to form upload data frames. The PON module monitors the global scheduling time slot allocation command issued by the optical line terminal in real time, converts the uploaded data frame into an electrical signal and transmits it to the optical module through the internal link, and then converts the electrical signal into an optical signal through the optical module within the allocated global scheduling time slot before uploading it to the optical line terminal through the optical distribution network.

2. The PON-based multi-protocol communication method according to claim 1, characterized in that, When the data processing module detects that the network protocol processing unit connected to each fieldbus device has business data to be uploaded, it allocates the corresponding internal scheduling time slots to each network protocol processing unit for their respective data upload. And when an internal scheduling slot is exhausted, the upload of the service data will be interrupted until the next internal scheduling slot allocated to it is resumed, including: The data processing module monitors the data transmission requests of each network protocol processing unit and determines the real-time requirement of the corresponding data transmission request based on the request code in the data transmission request according to the preset priority filtering rules. Add data requests with high real-time requirements to the internal priority queue, and add data requests with low real-time requirements to the internal regular queue. When executing internal scheduling time slots, the data processing module checks whether there are any pending data transmission requests in the internal priority queue. If there are, it continuously allocates corresponding internal scheduling time slots to each data transmission request in the priority queue until the internal priority queue is empty. After there are no pending data transmission requests in the internal priority queue, it allocates corresponding internal scheduling time slots to each data transmission request in the internal ordinary queue.

3. The PON-based multi-protocol communication method according to claim 2, characterized in that, When an internal scheduling time slot expires, the data processing module interrupts the upload of the service data until the next internal scheduling time slot allocated to it resumes the interrupted data upload. Specifically, this includes: If the data processing module detects that the corresponding network protocol processing unit is still uploading and sending data when an internal scheduling time slot is exhausted, it will take the currently transmitted data packet as the last packet of the internal scheduling time slot, interrupt the remaining data upload of the network protocol processing unit, and start receiving data transmission from another network protocol processing unit in the next internal scheduling time slot; the upload of the interrupted data in the previous time slot will be resumed when the next cycle of internal scheduling time slot allocated to the network protocol processing unit arrives.

4. The PON-based multiprotocol communication method according to claim 3, characterized in that, Also includes: The PON module parses the electrical signals received by the optical module and determines whether the target of the signal received by the optical module is this device. If it is not this device, it is filtered out; otherwise, the electrical signal is converted into an Ethernet protocol frame and sent to the data processing module.

5. The PON-based multiprotocol communication method according to claim 4, characterized in that, Also includes: The data processing module sorts the network data packets sent by the PON module according to the network type and destination port number, and assigns them to the corresponding network protocol processing unit or character device processing unit for processing. After receiving the network data packet, the character device processing unit parses it based on a custom protocol format and verifies the parsing result based on the data length, checksum, and header information. If the verification passes, it checks whether the device data is valid. If valid, it sends it to the corresponding device processing unit.

6. A multi-protocol communication device, characterized in that, It includes optical modules, PON modules, and data processing modules, among which: The data processing module is configured to allocate corresponding internal scheduling time slots to each network protocol processing unit for data uploading when it detects that the network protocol processing unit connected to each fieldbus device has service data to be uploaded; and to interrupt the uploading of the service data when an internal scheduling time slot is used up, until the next internal scheduling time slot allocated to it resumes the interrupted data uploading. The PON module is configured to encapsulate and process standard Ethernet frames containing service data received from the data processing module according to the PON protocol to form upload data frames; and to monitor the global scheduling time slot allocation instructions issued by the optical line terminal in real time, convert the upload data frames into electrical signals and transmit them to the optical module through the internal link, and then convert the electrical signals into optical signals through the optical module within the allocated global scheduling time slots, and then upload them to the optical line terminal through the optical distribution network.

7. The multi-protocol communication device according to claim 6, characterized in that: The data processing module is configured to monitor the data transmission requests of each network protocol processing unit, and determine the real-time requirement of the corresponding data transmission request based on the request code in the data transmission request according to a preset priority filtering rule; add the data transmission requests with high real-time requirements to the internal priority queue, and add the data transmission requests with low real-time requirements to the internal ordinary queue; when executing the internal scheduling time slot, check whether there are any pending data transmission requests in the internal priority queue. If there are, continuously allocate the corresponding internal scheduling time slot to each data transmission request in the priority queue until the internal priority queue is empty; after there are no pending data transmission requests in the internal priority queue, allocate the corresponding internal scheduling time slot to each data transmission request in the internal ordinary queue.

8. The multi-protocol communication device according to claim 7, characterized in that: The data processing module is configured to, when an internal scheduling time slot expires, if it detects that the corresponding network protocol processing unit is still uploading and sending data, then treat the currently transmitted data packet as the last packet of the internal scheduling time slot, interrupt the remaining data upload of the network protocol processing unit, and start receiving data transmission from another network protocol processing unit in the next internal scheduling time slot; until the next cycle of internal scheduling time slot allocated to the network protocol processing unit arrives, the upload of the interrupted data in the previous time slot will be resumed.

9. The multi-protocol communication device according to claim 8, characterized in that: The PON module is also configured to parse the electrical signal received by the optical module and determine whether the transmission target of the signal received by the optical module is this device. If it is not this device, it is filtered out; otherwise, the electrical signal is converted into an Ethernet protocol frame and sent to the data processing module.

10. The multi-protocol communication device according to claim 9, characterized in that: The data processing module includes a network protocol processing unit, a Profinet device processing unit, a Modbus-TCP device processing unit, an Ethernet IP device processing unit, a character device processing unit, a CAN device processing unit, a Profinet-DP device processing unit, and a Modbus-RTU device processing unit. The network protocol processing unit can forward data frames sent by the PON module to the Profinet device processing unit, Modbus-TCP device processing unit, EthernetIP device processing unit, or character device processing unit. The character device processing unit parses the data frame based on a custom protocol format after receiving it, and verifies the parsing result based on the data length, checksum, and header information. If the verification passes, it checks whether the device data is valid. If valid, it sends it to the corresponding CAN device processing unit, Profinet-DP device processing unit, or Modbus-RTU device processing unit.

Images