Protocol conversion method for single-pair Ethernet and 5G / 5G-A network

Abstract

The invention relates to a protocol conversion method for a single-pair Ethernet and a 5G / 5G-A network, and belongs to the technical field of communication networks. Aiming at heterogeneous interconnection requirements of a single-pair Ethernet and a 5G / 5G-A network, a Profinet protocol is carried on the single-pair Ethernet, and protocol conversion between heterogeneous networks is completed through strategy cooperation, protocol identification, mapping, packaging and other units. The method specifically comprises the following steps of: distributing exclusive 5G / 5G-A service quality flows for different Profinet flows by utilizing a core network strategy collaboration unit; capturing and identifying Profinet data by means of a protocol identification unit, marking the Profinet data, and forwarding the Profinet data to a 5G / 5G-A data mapping entry; real-time and priority mapping is carried out on the marked data based on the quality of service and a data radio bearer mapping unit; and encapsulating the Profinet data into a 5G / 5G-A message to be sent through the data encapsulation unit, or reversely de-encapsulating the Profinet data into a Profinet message. According to the invention, protocol conversion based on service quality maintenance between the single-pair Ethernet and the 5G / 5G-A network is realized, and end-to-end deterministic transmission of cross-network industrial real-time data is ensured.

Description

TECHNICAL FIELD

[0001] The application belongs to the technical field of communication network, and relates to a protocol conversion method of single pair Ethernet and 5G / 5G-A network. BACKGROUND

[0002] In recent years, with the development of industrial internet towards intelligentization, wireless and full connection, single pair Ethernet (SPE) is gradually becoming one of the key physical layer technologies for building high-reliable industrial network architecture. Ethernet-APL (Ethernet Advanced Physical Layer) as a specific implementation of SPE for process industry, combined with 10BASE-T1L specification, can complete one network from industrial field device to terminal control system. Its network architecture can directly carry mainstream industrial Ethernet protocols such as Profinet, EtherCAT and Modbus TCP, and build a solid and stable physical layer base for process industry.

[0003] 5G relies on URLLC (Ultra-Reliable and Low-Latency Communications), network slicing and Ethernet PDU (Ethernet Protocol Data Unit) session capabilities to provide deterministic guarantee for industrial wireless. Industrial 5G further strengthens time-sensitive network integration, redundant transmission and microsecond-level clock synchronization on this basis, meeting the stringent requirements of industrial control for reliability and real-time performance. Currently, 5G is continuously evolving to the 5G-A (5G-Advanced) stage. 5G-A further improves bandwidth, reduces latency and enhances connection reliability through technologies such as carrier aggregation, millimeter wave expansion and large-scale MIMO, providing stronger underlying support for building full-connection intelligent factories and industrial wireless automation.

[0004] The conversion of SPE and 5G / 5G-A network helps the industrial internet to complete wireless and high-reliable communication, and build a unified transmission architecture from the field layer to the control layer, which can support the seamless flow of various industrial Ethernet protocols in heterogeneous networks. However, the current conversion process still faces problems such as lack of conversion method, difficulty in implementing deterministic latency and difficulty in maintaining service quality. Therefore, how to complete the heterogeneous interconnection between SPE and 5G / 5G-A network has become a core technical challenge for building end-to-end full-digital industrial internet. SUMMARY

[0005] In view of this, the purpose of the present application is to provide a protocol conversion method of single pair Ethernet and 5G / 5G-A network, which can effectively solve the problems of protocol compatibility, deterministic delay and quality of service maintenance between heterogeneous networks, and complete the high-reliability, low-latency deterministic transmission of industrial protocol data between SPE and 5G / 5G-A system.

[0006] In order to achieve the above purpose, the present application provides the following technical scheme:

[0007] A protocol conversion method of single pair Ethernet and 5G / 5G-A network, the method comprises:

[0008] S1, an industrial internet scene of single pair Ethernet and 5G / 5G-A network communication is established, including industrial field domain, wireless transmission domain and core control domain, wherein the industrial field domain is provided with a plurality of single pair Ethernet devices, the wireless transmission domain is provided with a plurality of 5G / 5G-A terminals or base stations, and the core control domain is provided with a core network policy coordination unit;

[0009] S2, Profinet protocol is carried in the single pair Ethernet device in the industrial field domain, and the sending and receiving of protocol data are carried out through the single pair Ethernet network port;

[0010] S3, QoS policy configuration is carried out in the core network policy control function network element PCF in the core control domain;

[0011] S4, a protocol identification unit, a service quality and data radio bearer mapping unit and a data encapsulation unit are set in the 5G / 5G-A terminal or base station in the wireless transmission domain; the protocol identification unit, the service quality and data radio bearer mapping unit and the data encapsulation unit are configured;

[0012] S5, after the configuration is completed, the protocol conversion of single pair Ethernet and 5G / 5G-A network is carried out, and the communication of industrial internet scene is realized.

[0013] Further, in step S1, the industrial field domain accesses Profinet slave device through single pair Ethernet communication module, and is connected with the wireless transmission domain through a plurality of single pair Ethernet communication modules, wherein in the industrial field domain, the single pair Ethernet communication modules communicate with each other through single pair Ethernet; the single pair Ethernet communication module is connected with the 5G / 5G-A terminal of the wireless transmission domain, the 5G / 5G-A terminal is connected with the 5G / 5G-A base station through 5G / 5G-A wireless link, and the 5G / 5G-A base station is connected with the switch of the core control domain; the switch of the core control domain is connected with the 5G / 5G-A core network and the Profinet master device respectively.

[0014] Furthermore, in step S2, the physical layer chip of the standard Ethernet is replaced with a physical layer chip that conforms to the single-pair Ethernet standard, and its physical interface circuit is adjusted so that the Profinet protocol data frames can achieve data communication on a single pair of twisted pairs while keeping the original frame structure of the protocol unchanged.

[0015] Further, in step S3, based on the QoS policy template predefined in the core network policy control function (PCF) by the core network policy coordination unit, the N4 rules of the user plane function (UPF) are dynamically configured through the session management function (SMF) to bind a dedicated 5QI (5G / 5G-A QoS Identifier) ​​service flow to the packet data unit (PDU) session tunnel carrying Profinet traffic. The execution steps of the core network policy coordination unit include:

[0016] S31: Construct a custom 5QI template in the PCF network element, set the corresponding 5QI values ​​for non-real-time connection management messages, non-real-time data control messages, real-time connection management messages, and real-time data control messages of Profinet traffic. The 5QI values ​​are different for different types of messages. Define detection rules for Profinet type traffic to increase the detection of Profinet traffic type in 5G / 5G-A networks.

[0017] S32: Configure policy triggering conditions in SMF network elements;

[0018] S33: Enable the pre-loading QoS policy function in the UPF network element;

[0019] S34: Connect the access and mobility management function network element (AMF) of the core network and the next-generation base station (gNB) through the NG interface;

[0020] S35: After the terminal accesses the base station and core network for the first time, the core network automatically sends the configured QoS policy to the terminal.

[0021] S36: After receiving the QoS policy, the terminal notifies the service flow capture device to allow it to capture and identify data; at this point, the construction of the 5G / 5G-A network control unit is completed.

[0022] Furthermore, in step S31, the core network QoS policy configuration process is as follows:

[0023] S311: Before the program starts, the core network pre-configures QoS policies for Profinet traffic types in the PCF network element. For non-real-time connection management packets, execute step S312; for non-real-time data control packets, execute step S313; for real-time connection management packets, execute step S314; for real-time data control packets, execute step S315.

[0024] S312: For non-real-time connection management messages, set the capture tag IDENT ID to 1, the service quality mapping to 5QI75, and configure the data radio bearer DRB 1;

[0025] S313: For non-real-time data control messages, set the capture tag IDENT ID to 2, the service quality mapping to 5QI75, and configure the data radio bearer DRB 1;

[0026] S314: For real-time connection management messages, set the capture tag IDENT ID to 6, the service quality mapping to 5QI80, and configure the data radio bearer DRB 3;

[0027] S315: For real-time connection management messages, set the capture tag IDENT ID to 7, the service quality mapping to 5QI83, and configure the data radio bearer DRB 3;

[0028] S316: After configuring the QoS policy, the PCF sends the QoS policy to the SMF, and the SMF generates the corresponding QoS rule parameters based on the policy.

[0029] S317: The SMF sends QoS rules to the UPF through the N4 interface, and the UPF executes them.

[0030] S318: The UPF informs the gNB of the QoS rules through the N3 interface, and the gNB then allocates the corresponding QoS flow;

[0031] S319: The gNB informs the terminal of the currently allocated QoS flow through the air interface, allowing the terminal to provide dedicated transmission services for different Profinet traffic; at this point, the QoS policy configuration process is complete.

[0032] Furthermore, in step S4, according to the protocol identification unit, a service flow capture device is built at the 5G / 5G-A terminal inlet to capture Ethernet-based Profinet service data and mark the real-time category, priority and subsequent message type of the message;

[0033] Based on the Quality of Service and Data Radio Bearer Mapping Unit, the core network SMF and UPF network elements are linked to map the real-time performance and priority of different Profinet type packets to the corresponding QoS flow, specify the data radio bearer DRB channel to be used, and load it into the Service Data Adaptation Protocol (SDAP) layer for subsequent processing.

[0034] Through the data encapsulation unit, a Profinet data processor is established at the 5G / 5G-A user plane SDAP layer. The processed Profinet frame is transparently transmitted to the 5G / 5G-A air interface and sent by calling the DRB bearer. During reverse transmission, the processor restores the original Profinet frame and sends it to the Profinet device.

[0035] Furthermore, the execution step S41 of the protocol identification unit specifically includes the following process:

[0036] S411: Build a traffic capture device to capture Ethernet packets on a specified network interface;

[0037] S412: Parse the captured Ethernet packets and determine the packet type based on the specific value of the Ether Type field. If the Ether Type field is 0x8892, the packet is a Profinet real-time frame packet. Proceed to the next step.

[0038] S413; If the Ether Type field is 0x0800, the IP Protocol field is 17, and the Object UUID field is 0xdea00000-6c97-11d1-8271, then the message is a Profinet non-real-time frame message, and step S414 is executed.

[0039] S413: Further analyze the real-time frame message, and determine the real-time message type through the FrameID field of the application layer data, including connection management type and data control type; if the FrameID field of the application layer data is the same, further determine the type through the ServiceID field: whether it is discovery and configuration protocol setting DCP_SetSet or discovery and basic configuration protocol acquisition DCP_Get;

[0040] S414: Further analyze non-real-time frame messages, and determine the type of non-real-time message, including connection management type and data control type, by analyzing the Opnum field under the Distributed Computing Environment / Remote Procedure Call (DCE / RPC) protocol;

[0041] S415: Add a 1-byte identifier data before the identified Profinet message to identify different message types for subsequent data mapping and encapsulation; among them, Profinet data is divided into 4 categories: non-real-time connection management message, non-real-time data control message, real-time connection management message, and real-time data control message;

[0042] S416: The service flow capture unit sends the identified and labeled data to the Quality of Service and Data Radio Bearer Mapping Unit for data mapping; at this point, the Profinet protocol identification is complete.

[0043] Furthermore, the execution step S42 of the Quality of Service and Data Radio Bearer Mapping Unit specifically includes the following process:

[0044] S421: After passing through the data identification unit in step S41, Profinet data is divided into four types of messages with different real-time properties and priorities. The first byte of the message is judged. If it is a non-real-time connection management message, step S422 is executed; if it is a non-real-time data control message, step S423 is executed; if it is a real-time connection management message, step S424 is executed; if it is a real-time data control message, step S425 is executed.

[0045] S422: This message is a non-real-time connection management message. According to the predefined mapping rules, this message is mapped to 5QI 75 and configured as Data Radio Bearer DRB 1.

[0046] S423: This message is a non-real-time data control message. According to the predefined mapping rules, this message is mapped to 5QI 75 and configured as Data Radio Bearer DRB 1.

[0047] S424: This message is a real-time connection management message. According to the predefined mapping rules, this message is mapped to 5QI 80 and configured as Data Radio Bearer DRB 3.

[0048] S425: This message is a real-time data control message. According to the predefined mapping rules, this message is mapped to 5QI 83 and configured as data radio bearer DRB 3.

[0049] S426: Forward the mapped data to the SDAP layer to begin 5G / 5G-A packet encapsulation; at this point, the mapping of Quality of Service and data radio bearer is complete.

[0050] Furthermore, the execution step S43 of the data encapsulation unit includes the following process:

[0051] S431: For different types of Profinet messages, construct the corresponding SDAP header in the SDAP layer according to the mapping rules, add it before the Profinet message, and specify the corresponding DRB;

[0052] S432: After Profinet data is processed at the SDAP layer, it is further encapsulated into a complete 5G / 5G-A message through the Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), and Media Access Control (MAC) layers, and finally transmitted wirelessly using radio frequency equipment.

[0053] S433: After receiving a 5G / 5G-A message containing Profinet data, decapsulate it into a Profinet message and send it to the Profinet device; at this point, the 5G / 5G-A protocol data encapsulation is complete.

[0054] Furthermore, in step S5, after the configuration information is completed, the overall process of Profinet adapting to the 5G / 5G-A network protocol is as follows:

[0055] S501: Data Frame Capture and Preliminary Classification: Capture Ethernet data frames and parse the Ether Type field in their Ethernet Header: If the value is 0x8892, it is identified as a Profinet real-time frame, and step S504 is executed; if the value is 0x0800, it is identified as an IP data frame, and step S502 is executed.

[0056] S502: IP Protocol Parsing: Parse the Protocol field in the IP Header: If the value is 17, it is identified as a UDP / IP data frame, and proceed to step S503;

[0057] S503: UDP payload identification: Parse UDP payload data: If the first byte is 0x04 and the 9th to 18th bytes are 0xdea00000-6c97-11d1-8271, it is identified as a Profinet non-real-time frame, and step S505 is executed;

[0058] S504: Profinet real-time frame fine classification: Parse the FrameID field of the Profinet real-time frame: If it is a connection management message, proceed to step S506; if it is a data control message, proceed to step S507.

[0059] S505: Profinet non-real-time frame fine classification: Parse the Opnum field of the Profinet non-real-time frame: If it is a connection management message, execute step S508; if it is a data control message, execute step S509.

[0060] S506. Set the IDENT ID of real-time connection management messages to 6, and uniformly map the characteristics of connection management messages, such as type, real-time and function classification, to the traffic classification identifier field according to the Profinet traffic type identifier table.

[0061] S507. Set the IDENT ID of real-time data control messages to 7, and uniformly map the characteristics of connection management messages, such as type, real-time performance, and function classification, to the traffic classification identifier field according to the Profinet traffic type identifier table.

[0062] S508. Set the IDENT ID of non-real-time connection management messages to 1, and uniformly map the characteristics of connection management messages, such as type, real-time performance, and function classification, to the traffic classification identifier field according to the Profinet traffic type identifier table.

[0063] S509. Set the IDENT ID of non-real-time data control messages to 2, and uniformly map the characteristics of connection management messages, such as type, real-time and function classification, to the traffic classification identifier field according to the Profinet traffic type identifier table.

[0064] S510: Forwards the processed data to the 5G / 5G-A data processing entry point, sets the corresponding 5QI value according to the QoS policy rules, allocates DRB, and fills the relevant information into the SDAP header;

[0065] S511: Data is encapsulated sequentially through the PDCP layer, RLC layer, and MAC layer to form a complete 5G / 5G-A message, which is then transmitted through the 5G / 5G-A air interface; at this point, the protocol adaptation between Profinet and 5G / 5G-A is complete.

[0066] The beneficial effects of this invention are as follows:

[0067] (1) This invention connects the end-to-end path from field instruments to control system by using protocol conversion between a single pair of Ethernet and 5G / 5G-A networks based on quality of service maintenance, and completes end-to-end deterministic transmission while ensuring the industrial real-time performance of the single pair of Ethernet.

[0068] (2) This invention can combine the advantages of a single pair of Ethernet physical layers and complete the connection between a single pair of Ethernet and traditional Ethernet by combining intrinsically safe single pair cables. It supports direct connection of explosion-proof instruments and meters in hazardous areas (Zone 0) (such as combustible gas sensors), and supports seamless access to the single pair of Ethernet network without changing the existing instruments and meters, thereby reducing the cost of redeploying equipment.

[0069] (3) In the process of switching between a single pair of Ethernet and 5G / 5G-A networks, the present invention provides differentiated GBR (Guaranteed Bit Rate) and scheduling priorities for industrial traffic of different priorities (such as real-time IO, alarm, diagnosis) through the 5QI policy template predefined by the core network PCF and the SMF-UPF collaborative control mechanism, so as to ensure that the end-to-end transmission meets the jitter requirements and the deterministic air interface time slot allocation.

[0070] Other advantages, objectives, and features of the invention will be set forth in part in the description which follows, and in part will be apparent to those skilled in the art from the following examination, or may be learned from practice of the invention. The objectives and other advantages of the invention can be realized and obtained through the following description. Attached Figure Description

[0071] To make the objectives, technical solutions, and advantages of the present invention clearer, the preferred embodiments of the present invention will be described in detail below with reference to the accompanying drawings, wherein:

[0072] Figure 1 This is a schematic diagram of a single-pair Ethernet and 5G / 5G-A network architecture according to an embodiment of the present invention;

[0073] Figure 2 This is a schematic diagram of the functional modules of a single-pair Ethernet and 5G / 5G-A network architecture according to an embodiment of the present invention;

[0074] Figure 3 This is a flowchart illustrating the core network QoS policy configuration process according to an embodiment of the present invention.

[0075] Figure 4 This is a flowchart illustrating the conversion between a single pair of Ethernet and 5G / 5G-A network protocols according to an embodiment of the present invention. Detailed Implementation

[0076] The following specific examples illustrate the implementation of the present invention. Those skilled in the art can easily understand other advantages and effects of the present invention from the content disclosed in this specification. The present invention can also be implemented or applied through other different specific embodiments, and various details in this specification can be modified or changed based on different viewpoints and applications without departing from the spirit of the present invention. It should be noted that the illustrations provided in the following embodiments are only schematic representations of the basic concept of the present invention. Unless otherwise specified, the following embodiments and features can be combined with each other.

[0077] The accompanying drawings are for illustrative purposes only and are schematic diagrams, not actual pictures. They should not be construed as limiting the invention. To better illustrate the embodiments of the invention, some parts in the drawings may be omitted, enlarged, or reduced, and do not represent the actual product dimensions. It is understandable to those skilled in the art that some well-known structures and their descriptions may be omitted in the drawings.

[0078] In the accompanying drawings of the embodiments of the present invention, the same or similar reference numerals correspond to the same or similar components. In the description of the present invention, it should be understood that if terms such as "upper," "lower," "left," "right," "front," and "rear" indicate the orientation or positional relationship based on the orientation or positional relationship shown in the drawings, they are only for the convenience of describing the present invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, the terms used to describe positional relationships in the drawings are only for illustrative purposes and should not be construed as limiting the present invention. For those skilled in the art, the specific meaning of the above terms can be understood according to the specific circumstances.

[0079] Please see Figures 1-4 This is a protocol conversion method for a single pair of Ethernet and 5G / 5G-A networks.

[0080] Example

[0081] This embodiment first describes in detail a protocol conversion method for a single pair of Ethernet and 5G / 5G-A networks, which specifically includes the following steps:

[0082] S1. Establish an industrial internet scenario for communication between a single pair of Ethernet and a 5G / 5G-A network, including an industrial field domain, a wireless transmission domain, and a core control domain. The industrial field domain is equipped with several single-pair Ethernet devices, the wireless transmission domain is equipped with several 5G / 5G-A terminals or base stations, and the core control domain is equipped with a core network policy coordination unit.

[0083] S2. The Profinet protocol is carried in a single pair of Ethernet devices in the industrial field, and protocol data is sent and received through a single pair of Ethernet ports.

[0084] S3. Configure QoS policies in the core network PCF (Policy Control Function) network element of the core control domain;

[0085] S4. Set up a protocol identification unit, a quality of service and data radio bearer mapping unit, and a data encapsulation unit in the 5G / 5G-A terminal or base station in the wireless transmission domain; configure the functions of the protocol identification unit, the quality of service and data radio bearer mapping unit, and the data encapsulation unit.

[0086] S5. After configuration, perform protocol conversion between a single pair of Ethernet and 5G / 5G-A networks to achieve communication in industrial internet scenarios.

[0087] In step S1 of this embodiment, Figure 1The overall architecture of the protocol-adaptive network is demonstrated, comprising three functional areas: Industrial Field Domain: Profinet device 1 accesses the network via a single pair of Ethernet communication modules, adapting to the single pair of Ethernet networks while retaining the original frame structure of Profinet traffic; Wireless Transmission Domain: Both the 5G / 5G-A terminal module and the base station module have built-in Profinet flow capture devices (based on IDENT ID tags), QoS and data radio bearer mapping units, and data encapsulation units, which transparently transmit Profinet data to the 5G / 5G-A air interface; Core Control Domain: The core network coordinates through PCF-SMF-UPF policies to pre-configure dedicated 5QI policies for PDU sessions carrying Profinet traffic, and distributes them to the terminal via the base station; The terminal allocates corresponding QoS flows for different priority traffic (such as Profinet real-time data) according to the policy, and calls DRB to complete deterministic transmission over the air interface.

[0088] The industrial field domain connects to the Profinet slave device through a single pair of Ethernet communication modules and communicates with the wireless transmission domain through several single pair of Ethernet communication modules. Within the industrial field domain, the single pair of Ethernet communication modules communicate with each other through a single pair of Ethernet.

[0089] A connection is established between a single Ethernet communication module and a 5G / 5G-A terminal in the wireless transmission domain. The 5G / 5G-A terminal communicates with the 5G / 5G-A base station via a 5G / 5G-A wireless link. The 5G / 5G-A base station is connected to the switch in the core control domain.

[0090] The switches in the core control domain are connected to the 5G / 5G-A core network and the Profinet master station equipment, respectively.

[0091] Figure 2 The diagram shows the architecture of each system unit in the protocol adaptation network. The core network policy coordination unit allocates dedicated QoS flows to different types of Profinet traffic to ensure its industrial service quality. The protocol identification unit captures Ethernet data, identifies and marks Profinet data. The service quality and data radio bearer mapping unit performs real-time and priority mapping on the marked Profinet data and assigns corresponding DRBs. Finally, the data encapsulation unit encapsulates the mapped Profinet data layer by layer into 5G / 5G-A packets for transmission, or decapsulates 5G / 5G-A packets carrying Profinet data into Profinet packets for transmission.

[0092] In step S2 of this embodiment, the physical layer chip of the standard Ethernet is replaced with a physical layer chip that conforms to the single-pair Ethernet standard, and its physical interface circuit is adjusted so that the Profinet protocol data frame can achieve data communication on a single-pair twisted pair while keeping the original frame structure of the protocol unchanged.

[0093] In step S3 of this embodiment, with the help of the core network policy coordination unit, a QoS (Quality of Service) policy template is predefined in the core network PCF (Policy Control Function) network element, and the N4 rules of the UPF (User Plane Function) network element are dynamically configured through the SMF (Session Management Function) network element to bind a dedicated 5QI (5G / 5G-A QoS Identifier) ​​service flow to the PDU (Packet Data Unit) session tunnel carrying Profinet traffic.

[0094] The execution steps of the core network policy coordination unit are as follows:

[0095] S31: Construct a custom 5QI template in the PCF network element, set the 5QI value of Profinet non-real-time connection management message to 75, non-real-time data control message to 75, real-time connection management message to 80, real-time data control message to 83, and define the detection rules for Profinet type traffic to increase the detection of Profinet traffic type in 5G / 5G-A network.

[0096] S32: Configure policy triggering conditions in SMF network elements;

[0097] S33: Enable the pre-loading QoS policy function in the UPF network element;

[0098] S34: Connect the core network's Access and Mobility Management Function (AMF) and the next-generation node B (gNB) via the NG interface;

[0099] S35: After the terminal accesses the base station and core network for the first time, the core network automatically sends the configured QoS policy to the terminal.

[0100] S36: After receiving the QoS policy, the terminal notifies the service flow capture device to allow it to capture and identify data; at this point, the construction of the 5G / 5G-A network control unit is completed.

[0101] More specifically, in step S31, such as Figure 3 The core network QoS policy configuration flowchart shown includes the following steps:

[0102] S311: Before the program starts, the core network pre-configures QoS policies for Profinet traffic types in the PCF network element. For non-real-time connection management packets, execute step S312; for non-real-time data control packets, execute step S313; for real-time connection management packets, execute step S314; for real-time data control packets, execute step S315.

[0103] S312: For non-real-time connection management messages, set the capture tag IDENT ID to 1, the service quality mapping to 5QI75, and configure the data radio bearer DRB 1;

[0104] S313: For non-real-time data control messages, set the capture tag IDENT ID to 2, the service quality mapping to 5QI75, and configure the data radio bearer DRB 1;

[0105] S314: For real-time connection management messages, set the capture tag IDENT ID to 6, the service quality mapping to 5QI80, and configure the data radio bearer DRB 3;

[0106] S315: For real-time connection management messages, set the capture tag IDENT ID to 7, the service quality mapping to 5QI83, and configure the data radio bearer DRB 3;

[0107] S316: After configuring the QoS policy, the PCF sends the QoS policy to the SMF, and the SMF generates the corresponding QoS rule parameters based on the policy.

[0108] S317: The SMF sends QoS rules to the UPF through the N4 interface, and the UPF executes them.

[0109] S318: The UPF informs the gNB of the QoS rules through the N3 interface, and the gNB then allocates the corresponding QoS flow;

[0110] S319: The gNB informs the terminal of the currently allocated QoS flow through the air interface, allowing the terminal to provide dedicated transmission services for different Profinet traffic; at this point, the QoS policy configuration process is complete.

[0111] In step S4 of this embodiment, according to the protocol identification unit, a service flow capture device is built at the 5G / 5G-A terminal ingress to capture Ethernet-based Profinet service data, marking the real-time category, priority, and subsequent message type of the packets; relying on the quality of service and data radio bearer mapping unit, the core network SMF and UPF network elements are linked to map the real-time and priority of different Profinet type packets to the corresponding QoS flow, specify the data radio bearer (DRB) to be used, and load it into the Service Data Adaptation Protocol (SDAP) layer for subsequent processing; through the data encapsulation unit, a Profinet data processor is established at the 5G / 5G-A user plane SDAP layer, and the processed Profinet frame is transparently transmitted to the 5G / 5G-A air interface, calling the DRB bearer for transmission; during reverse transmission, the processor restores the original Profinet frame and sends it to the Profinet device. Specifically, the execution processes of the protocol identification unit, the quality of service and data radio bearer mapping unit, and the data encapsulation unit are as follows:

[0112] The execution step S41 of the protocol identification unit specifically includes the following process:

[0113] S411: Build a traffic capture device to capture Ethernet packets on a specified network interface;

[0114] S412: Parse the captured Ethernet packet. If the Ether Type field is 0x8892, the packet is a Profinet real-time frame; proceed to step S413. If the Ether Type field is 0x0800 and the IP Protocol field is 17, and...

[0115] If the Object UUID field is 0xdea00000-6c97-11d1-8271 (as defined by the Profinet standard), then the message is a Profinet non-real-time frame message, and step S414 is executed.

[0116] S413: Further analyze real-time frame messages, using the FrameID (Frame Identifier) ​​field in the application layer data to determine the real-time message type, including connection management type and data control type; taking into account discovery and configuration protocol settings.

[0117] DCP_Set (Discovery and Basic Configuration Protocol Set) and Discovery and Basic Configuration Protocol Acquisition

[0118] The FrameID is the same for DCP_Get (Discovery and basic Configuration Protocol Get), and the ServiceID (Service Identifier) ​​field is used to further determine whether it is a Set or a Get.

[0119] S414: Further analyze the non-real-time frame messages by analyzing the Opnum field under the Distributed Computing Environment / Remote Procedure Call (DCE / RPC) protocol to determine the non-real-time message type, including connection management type and data control type;

[0120] S415: Add a 1-byte identifier data before the identified Profinet message to identify different message types for subsequent data mapping and encapsulation; among them, Profinet data is divided into 4 categories: non-real-time connection management message, non-real-time data control message, real-time connection management message, and real-time data control message;

[0121] S416: The service flow capture unit sends the identified and labeled data to the Quality of Service and Data Radio Bearer Mapping Unit for data mapping; at this point, the Profinet protocol identification is complete.

[0122] The execution step S42 of the Quality of Service and Data Radio Bearer Mapping Unit specifically includes the following process:

[0123] S421: After passing through the data identification unit in step S41, the Profinet data is divided into four categories of messages with different real-time characteristics and priorities. The first byte of the message is analyzed. If it is a non-real-time connection management message, step S422 is executed; if it is a non-real-time data control message, step S423 is executed; if it is a real-time connection management message, step S424 is executed; if it is a real-time data control message, step S425 is executed.

[0124] S422: This message is a non-real-time connection management message. According to the predefined mapping rules, this message is mapped to 5QI75 and the data radio bearer DRB 1 is configured.

[0125] S423: This message is a non-real-time data control message. According to the predefined mapping rules, this message is mapped to 5QI 75 and configured as Data Radio Bearer DRB 1.

[0126] S424: This message is a real-time connection management message. According to the predefined mapping rules, this message is mapped to 5QI 80 and configured as Data Radio Bearer DRB 3.

[0127] S425: This message is a real-time data control message. According to the predefined mapping rules, this message is mapped to 5QI 83 and configured as data radio bearer DRB 3.

[0128] S426: Forward the mapped data to the SDAP layer to begin 5G / 5G-A packet encapsulation; at this point, the mapping of Quality of Service and data radio bearer is complete.

[0129] As shown in Table 1, the 5G / 5G-A and Profinet traffic labeling / mapping table assigns appropriate 5QI values, capture identifiers, and DRB data radio bearers to different types of traffic based on the real-time and latency requirements of Profinet type traffic and the 5QI values ​​reserved in the 5G / 5G-A standard. For non-real-time data with a latency requirement of around 100ms, it is mapped to 5QI 75 level of the 5G / 5G-A network, with a resource type of Non-GBR (no guaranteed bit rate). The IDENTID capture flag for connection management messages is set to 1, and the data control flag is set to 2, both assigned DRB 1 as the data radio bearer. For real-time connection management data with a latency requirement of less than 10ms, it is mapped to 5QI 80 level of the 5G / 5G-A network, with a resource type of Delay-Critical GBR (delay-critical guaranteed bit rate). This level supports a packet transmission latency of 10ms. The IDENTID capture flag for connection management messages is set to 6, and DRB 3 is assigned as the data radio bearer. For real-time data control data, the capture flag is set to 7, mapped to 5QI 83 level of the 5G / 5G-A network, and DRB 3 is assigned as the data radio bearer.

[0130] Table 1

[0131]

[0132] The execution step S43 of the data encapsulation unit includes the following process:

[0133] S431: For different types of Profinet messages, construct the corresponding SDAP header in the SDAP layer according to the mapping rules, add it before the Profinet message, and specify the corresponding DRB;

[0134] S432: After Profinet data is processed at the SDAP layer, it is further encapsulated into a complete 5G / 5G-A message through the Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Medium Access Control (MAC) layer, and finally transmitted wirelessly using radio frequency equipment;

[0135] S433: After receiving a 5G / 5G-A message containing Profinet data, decapsulate it into a Profinet message and send it to the Profinet device; at this point, the 5G / 5G-A protocol data encapsulation is complete.

[0136] In step S5 of this embodiment, after the above configuration information is completed, Figure 4 The overall process of Profinet's adaptation to 5G / 5G-A network protocols is demonstrated, and the specific steps are as follows:

[0137] S501: Data Frame Capture and Preliminary Classification: Capture Ethernet data frames and parse the Ether Type field in their Ethernet Header: If the value is 0x8892, identify it as a Profinet real-time frame and proceed to step S504. If the value is 0x0800, identify it as an IP data frame and proceed to step S502.

[0138] S502: IP Protocol Parsing: Parse the Protocol field in the IP Header: If the value is 17 (UDP), it is identified as a UDP / IP data frame, and step S503 is executed;

[0139] S503: UDP payload identification: Parse UDP payload data: If the first byte is 0x04 and the 9th to 18th bytes are 0xdea00000-6c97-11d1-8271, it is identified as a Profinet non-real-time frame, and step S505 is executed;

[0140] S504: Profinet real-time frame fine classification: Parse the FrameID field of the Profinet real-time frame: If it is a connection management message, proceed to step S506; if it is a data control message, proceed to step S507.

[0141] S505: Profinet non-real-time frame fine classification: Parse the Opnum field of the Profinet non-real-time frame: If it is a connection management message, execute step S508; if it is a data control message, execute step S509.

[0142] S506. Set the IDENT ID of real-time connection management messages to 6, and uniformly map the characteristics of connection management messages, such as type, real-time and function classification, to the traffic classification identifier field according to the Profinet traffic type identifier table.

[0143] S507. Set the IDENT ID of real-time data control messages to 7, and uniformly map the characteristics of connection management messages, such as type, real-time performance, and function classification, to the traffic classification identifier field according to the Profinet traffic type identifier table.

[0144] S508. Set the IDENT ID of non-real-time connection management messages to 1, and uniformly map the characteristics of connection management messages, such as type, real-time performance, and function classification, to the traffic classification identifier field according to the Profinet traffic type identifier table.

[0145] S509. Set the IDENT ID of non-real-time data control messages to 2, and uniformly map the characteristics of connection management messages, such as type, real-time and function classification, to the traffic classification identifier field according to the Profinet traffic type identifier table.

[0146] S510: Service Quality Policy Application: The processed data is forwarded to the 5G / 5G-A data processing entry point. According to the QoS policy rules, the corresponding 5QI value is set, DRB is allocated, and relevant information is filled into the SDAP header.

[0147] S511: 5G / 5G-A Protocol Data Encapsulation and Transmission: Data is encapsulated sequentially through the PDCP layer, RLC layer, and MAC layer to form a complete 5G / 5G-A message, which is then transmitted through the 5G / 5G-A air interface; at this point, the protocol adaptation between Profinet and 5G / 5G-A is complete.

[0148] Table 2 shows the Profinet traffic type identifier table, which maps key attributes of Profinet traffic (including traffic type, real-time performance, functionality, and assigned IDENT ID value) to a 1-byte traffic classification identifier. The bit definitions of this identifier byte are as follows:

[0149] bit7~bit5: Maps the IDENT ID value;

[0150] bit4~bit2: Maps Profinet traffic type, real-time performance, and functionality;

[0151] bit1~bit0: Reserved bits, always set to 0.

[0152] Table 2

[0153]

[0154] Although the Profinet protocol is used as the bearer protocol for a single Ethernet pair in this embodiment, the solution of the present invention is not limited to the Profinet protocol. Other Ethernet-based protocols can also be used as bearer protocols. By modifying the relevant network architecture units proposed in the present invention, it can be made to handle other Ethernet protocols.

[0155] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and are not intended to limit it. Although the present invention has been described in detail with reference to preferred embodiments, those skilled in the art should understand that modifications or equivalent substitutions can be made to the technical solutions of the present invention without departing from the spirit and scope of the present invention, and all such modifications or substitutions should be covered within the scope of the claims of the present invention.

Claims

1. A protocol conversion method for a single pair of Ethernet networks and 5G / 5G-A networks, characterized in that: The method includes: S1. Establish an industrial internet scenario for communication between a single pair of Ethernet and a 5G / 5G-A network, including an industrial field domain, a wireless transmission domain, and a core control domain. The industrial field domain is equipped with several single-pair Ethernet devices, the wireless transmission domain is equipped with several 5G / 5G-A terminals or base stations, and the core control domain is equipped with a core network policy coordination unit. S2. The Profinet protocol is carried in a single pair of Ethernet devices in the industrial field, and protocol data is sent and received through a single pair of Ethernet ports. S3. Configure QoS policies in the core network policy control function (PCF) network element of the core control domain. S4. Set up a protocol identification unit, a quality of service and data radio bearer mapping unit, and a data encapsulation unit in the 5G / 5G-A terminal or base station in the wireless transmission domain; configure the functions of the protocol identification unit, the quality of service and data radio bearer mapping unit, and the data encapsulation unit. S5. After configuration, perform protocol conversion between a single pair of Ethernet and 5G / 5G-A networks to realize communication in industrial Internet scenarios.

2. The protocol conversion method for a single pair of Ethernet and 5G / 5G-A networks according to claim 1, characterized in that: In step S1, the industrial field domain connects to the Profinet slave device through a single pair of Ethernet communication modules and communicates with the wireless transmission domain through several single pairs of Ethernet communication modules. Within the industrial field domain, the single pairs of Ethernet communication modules communicate with each other via single pairs of Ethernet. A connection is established between the single pairs of Ethernet communication modules and the 5G / 5G-A terminal in the wireless transmission domain. The 5G / 5G-A terminal communicates with the 5G / 5G-A base station via a 5G / 5G-A wireless link. The 5G / 5G-A base station is connected to the switch in the core control domain. The switch in the core control domain is connected to both the 5G / 5G-A core network and the Profinet master device.

3. The protocol conversion method for a single pair of Ethernet and 5G / 5G-A networks according to claim 1, characterized in that: In step S2, the physical layer chip of the standard Ethernet is replaced with a physical layer chip that conforms to the single-pair Ethernet standard, and its physical interface circuit is adjusted so that the Profinet protocol data frames can achieve data communication on a single pair of twisted pairs while keeping the original frame structure of the protocol unchanged.

4. The protocol conversion method for a single pair of Ethernet and 5G / 5G-A networks according to claim 1, characterized in that: In step S3, based on the QoS policy template predefined in the core network policy control function (PCF) by the core network policy coordination unit, the N4 rules of the user plane function (UPF) are dynamically configured through the session management function (SMF) to bind a dedicated 5QI (5G / 5G-A QoS Identifier) ​​service flow to the Protocol Data Unit (PDU) session tunnel carrying Profinet traffic. The execution steps of the core network policy coordination unit include: S31: Construct a custom 5QI template in the PCF network element, set the corresponding 5QI values ​​for non-real-time connection management messages, non-real-time data control messages, real-time connection management messages, and real-time data control messages of Profinet traffic. The 5QI values ​​are different for different types of messages. Define detection rules for Profinet type traffic to increase the detection of Profinet traffic type in 5G / 5G-A networks. S32: Configure policy triggering conditions in SMF network elements; S33: Enable the pre-loading QoS policy function in the UPF network element; S34: Connect the access and mobility management function network element (AMF) of the core network and the next-generation base station (gNB) through the NG interface; S35: After the terminal accesses the base station and core network for the first time, the core network automatically sends the configured QoS policy to the terminal. S36: After receiving the QoS policy, the terminal notifies the service flow capture device to allow it to capture and identify data; at this point, the construction of the 5G / 5G-A network control unit is completed.

5. The protocol conversion method for a single pair of Ethernet and 5G / 5G-A networks according to claim 4, characterized in that: In step S31, the core network QoS policy configuration process is as follows: S311: Before the program starts, the core network pre-configures QoS policies for Profinet traffic types in the PCF network element. For non-real-time connection management packets, execute step S312; for non-real-time data control packets, execute step S313; for real-time connection management packets, execute step S314; for real-time data control packets, execute step S315. S312: For non-real-time connection management messages, set the capture tag IDENT ID to 1, the service quality mapping to 5QI 75, and configure the data radio bearer DRB 1; S313: For non-real-time data control messages, set the capture tag IDENT ID to 2, the service quality mapping to 5QI 75, and configure the data radio bearer DRB 1; S314: For real-time connection management messages, set the capture tag IDENT ID to 6, the service quality mapping to 5QI 80, and configure the data radio bearer DRB 3; S315: For real-time connection management messages, set the capture tag IDENT ID to 7, the service quality mapping to 5QI 83, and configure the data radio bearer DRB 3; S316: After configuring the QoS policy, the PCF sends the QoS policy to the SMF, and the SMF generates the corresponding QoS rule parameters based on the policy. S317: The SMF sends QoS rules to the UPF through the N4 interface, and the UPF executes them. S318: The UPF informs the gNB of the QoS rules through the N3 interface, and the gNB then allocates the corresponding QoS flow; S319: The gNB informs the terminal of the currently allocated QoS flow through the air interface, allowing the terminal to provide dedicated transmission services for different Profinet traffic; at this point, the QoS policy configuration process is complete.

6. The protocol conversion method for a single pair of Ethernet and 5G / 5G-A networks according to claim 1, characterized in that: In step S4, according to the protocol identification unit, a service flow capture device is built at the 5G / 5G-A terminal inlet to capture Ethernet-based Profinet service data and mark the real-time category, priority and subsequent message type of the message; Based on the Quality of Service and Data Radio Bearer Mapping Unit, the core network SMF and UPF network elements are linked to map the real-time performance and priority of different Profinet type packets to the corresponding QoS flow, specify the data radio bearer DRB channel to be used, and load it into the Service Data Adaptation Protocol (SDAP) layer for subsequent processing. Through the data encapsulation unit, a Profinet data processor is established at the 5G / 5G-A user plane SDAP layer. The processed Profinet frame is transparently transmitted to the 5G / 5G-A air interface and sent by calling the DRB bearer. During reverse transmission, the processor restores the original Profinet frame and sends it to the Profinet device.

7. The protocol conversion method for a single pair of Ethernet and 5G / 5G-A networks according to claim 6, characterized in that: The execution step S41 of the protocol identification unit specifically includes the following process: S411: Build a traffic capture device to capture Ethernet packets on a specified network interface; S412: Parse the captured Ethernet packet and determine the packet type based on the specific value of the Ether Type field. If the Ether Type field is 0x8892, the packet is a Profinet real-time frame packet, and proceed to step S413. If the Ether Type field is 0x0800, the IP Protocol field is 17, and the Object UUID field is 0xdea00000-6c97-11d1-8271, the packet is a Profinet non-real-time frame packet, and proceed to step S414. S413: Further analyze the real-time frame message, and determine the real-time message type through the FrameID field of the application layer data, including connection management type and data control type; if the FrameID field of the application layer data is the same, further determine the type through the ServiceID field: whether it is discovery and configuration protocol setting DCP_SetSet or discovery and basic configuration protocol acquisition DCP_Get; S414: Further analyze non-real-time frame messages, and determine the type of non-real-time message, including connection management type and data control type, by analyzing the Opnum field under the Distributed Computing Environment / Remote Procedure Call (DCE / RPC) protocol; S415: Add a 1-byte identifier data before the identified Profinet message to identify different message types for subsequent data mapping and encapsulation; among them, Profinet data is divided into 4 categories: non-real-time connection management message, non-real-time data control message, real-time connection management message, and real-time data control message; S416: The service flow capture unit sends the identified and labeled data to the Quality of Service and Data Radio Bearer Mapping Unit for data mapping; at this point, the Profinet protocol identification is complete.

8. The protocol conversion method for a single pair of Ethernet and 5G / 5G-A networks according to claim 7, characterized in that: The execution step S42 of the Quality of Service and Data Radio Bearer Mapping Unit specifically includes the following process: S421: After passing through the data identification unit in step S41, Profinet data is divided into four types of messages with different real-time properties and priorities. The first byte of the message is judged. If it is a non-real-time connection management message, step S422 is executed; if it is a non-real-time data control message, step S423 is executed; if it is a real-time connection management message, step S424 is executed; if it is a real-time data control message, step S425 is executed. S422: This message is a non-real-time connection management message. According to the predefined mapping rules, this message is mapped to 5QI75 and the data radio bearer DRB 1 is configured. S423: This message is a non-real-time data control message. According to the predefined mapping rules, this message is mapped to 5QI75 and the data radio bearer DRB 1 is configured. S424: This message is a real-time connection management message. According to the predefined mapping rules, this message is mapped to 5QI80 and the data radio bearer DRB 3 is configured. S425: This message is a real-time data control message. According to the predefined mapping rules, this message is mapped to 5QI83 and the data radio bearer DRB 3 is configured. S426: Forward the mapped data to the SDAP layer to begin 5G / 5G-A packet encapsulation; At this point, the mapping between Quality of Service and wireless data bearer is complete.

9. The protocol conversion method for a single pair of Ethernet and 5G / 5G-A networks according to claim 8, characterized in that: The execution step S43 of the data encapsulation unit includes the following process: S431: For different types of Profinet messages, construct the corresponding SDAP header in the SDAP layer according to the mapping rules, add it to the front of the Profinet message, and specify the corresponding DRB; S432: After Profinet data is processed at the SDAP layer, it is further encapsulated into a complete 5G / 5G-A message through the Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), and Media Access Control (MAC) layers, and finally transmitted wirelessly using radio frequency equipment. S433: After receiving a 5G / 5G-A message containing Profinet data, decapsulate it into a Profinet message and send it to the Profinet device; at this point, the 5G / 5G-A protocol data encapsulation is complete.

10. The protocol conversion method for a single pair of Ethernet and 5G / 5G-A networks according to claim 1, characterized in that: In step S5, after the configuration information is completed, the overall process of Profinet adapting to the 5G / 5G-A network protocol is as follows: S501: Data Frame Capture and Preliminary Classification: Capture Ethernet data frames and parse the EtherType field in their Ethernet Header: If the value is 0x8892, it is identified as a Profinet real-time frame, and step S504 is executed; if the value is 0x0800, it is identified as an IP data frame, and step S502 is executed. S502: IP Protocol Parsing: Parse the Protocol field in the IP Header: If the value is 17, it is identified as a UDP / IP data frame, and proceed to step S503; S503: UDP payload identification: Parse UDP payload data: If the first byte is 0x04 and the 9th to 18th bytes are 0xdea00000-6c97-11d1-8271, it is identified as a Profinet non-real-time frame, and step S505 is executed; S504: Profinet real-time frame fine classification: Parse the FrameID field of the Profinet real-time frame: If it is a connection management message, proceed to step S506; if it is a data control message, proceed to step S507. S505: Profinet non-real-time frame fine classification: Parse the Opnum field of the Profinet non-real-time frame: If it is a connection management message, execute step S508; if it is a data control message, execute step S509. S506. Set the IDENT ID of real-time connection management messages to 6, and uniformly map the characteristics of connection management messages, such as type, real-time and function classification, to the traffic classification identifier field according to the Profinet traffic type identifier table. S507. Set the IDENT ID of real-time data control messages to 7, and uniformly map the characteristics of connection management messages, such as type, real-time performance, and function classification, to the traffic classification identifier field according to the Profinet traffic type identifier table. S508. Set the IDENT ID of non-real-time connection management messages to 1, and uniformly map the characteristics of connection management messages, such as type, real-time performance, and function classification, to the traffic classification identifier field according to the Profinet traffic type identifier table. S509. Set the IDENT ID of non-real-time data control messages to 2, and uniformly map the characteristics of connection management messages, such as type, real-time and function classification, to the traffic classification identifier field according to the Profinet traffic type identifier table. S510: Forwards the processed data to the 5G / 5G-A data processing entry point, sets the corresponding 5QI value according to the QoS policy rules, allocates DRB, and fills the relevant information into the SDAP header; S511: Data is encapsulated sequentially through the PDCP layer, RLC layer, and MAC layer to form a complete 5G / 5G-A message, which is then transmitted through the 5G / 5G-A air interface; at this point, the protocol adaptation between Profinet and 5G / 5G-A is complete.

Images