Parameter configuration method, device, equipment, medium and product
By unifying the parameter value field of the management control list length to 4 bytes and adopting a 7-byte fixed gating entry structure, the interoperability problem caused by protocol inconsistency in the 5G and TSN converged architecture is solved, improving device parsing efficiency and system reliability. It is suitable for resource-constrained wireless backhaul and industrial field networks.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- SPREADTRUM COMMUNICATION (SHANGHAI) CO LTD
- Filing Date
- 2026-03-06
- Publication Date
- 2026-05-01
AI Technical Summary
In the converged architecture of 5G and Time-Sensitive Networking (TSN), the inconsistency between the 3GPP protocol and the IEEE standard in defining the length of the management control list leads to poor interoperability between devices from different manufacturers. Furthermore, the existing variable-length TLV structure increases protocol overhead and reduces the parsing efficiency of the device-side converter.
The parameter value field for the length of the management control list is standardized to a 4-byte 32-bit unsigned integer format, and a 7-byte fixed gating entry structure is adopted. The outer parameter value length field is omitted, and parsing is performed using a predefined fixed field length.
It achieves semantic consistency of parameters among different manufacturers, significantly improves the operation performance and interoperability of the 5G and TSN converged architecture, reduces transmission overhead, and meets the requirements of time-sensitive networks for efficient and reliable gating scheduling.
Smart Images
Figure CN121967200A_ABST
Abstract
Description
Parameter configuration methods, devices, equipment, media and products Technical Field
[0001] This application relates to the field of digital information transmission technology, and in particular to a parameter configuration method, apparatus, device, medium and product. Background Technology
[0002] In the converged architecture of Fifth Generation Mobile Communication Technology (5G) and Time-Sensitive Networking (TSN), the Network-Side TSN Translator (NW-TT) needs to send gating scheduling parameters to the Device-Side TSN Translator (DS-TT) to achieve end-to-end deterministic data transmission.
[0003] In existing technologies, Ethernet port parameters, such as Administrative Control List (AdminControlList) and Administrative Control List Length (AdminControlListLength), are typically encapsulated into a three-field information element containing a parameter name field, a parameter value length field, and a parameter value field, in accordance with the 3rd Generation Partnership Project (3GPP) protocol.
[0004] However, the 3GPP protocol's definition of the parameter value length in the management control list is inconsistent with the value specified in the Institute of Electrical and Electronics Engineers (IEEE) standard. This inconsistency leads to compatibility issues when different manufacturers implement the system. Furthermore, because the management control list uses the Type-Length-Value (TLV) variable-length structure defined in IEEE, it increases protocol overhead and reduces the parsing efficiency of the device-side converter. Summary of the Invention
[0005] This application provides a parameter configuration method, apparatus, device, medium, and product, which unifies the parameter value field of the management control list length to 4 bytes, adopts a 7-byte fixed gating entry structure for the management control list, and omits the outer parameter value length field, so that the device-side converter can achieve efficient parsing based on a predefined fixed field length, thereby achieving compatible, compact, and low-latency parameter configuration.
[0006] Firstly, this application provides a parameter configuration method applied to a network-side converter, the method comprising:
[0007] Get the list of management control measures to be issued and the length of the management control measures list;
[0008] The length of the management control list is encapsulated as a first information element. The first information element includes a parameter name field, a field indicating the length of the parameter value, and a parameter value field. The parameter value field adopts a 4-byte 32-bit unsigned integer format and is used to represent the number of gated entries in the management control list.
[0009] The management control list is encapsulated as a second information element. The second information element consists of N consecutively arranged gating entries, where N is a positive integer value indicated by the length of the management control list. Each gating entry is fixed at 7 bytes, including 1 byte of gating operation name, 1 byte of gating operation entry length, 1 byte of flow gate status, and 4 bytes of time interval. The value of the gating operation entry length is fixed at 5. The second information element does not contain a parameter value length field.
[0010] The first and second information elements are sent to the device-side converter so that the device-side converter can parse the first and second information elements based on a predefined fixed field length, obtain the parsing result, and configure a local time-sensitive network gating policy according to the parsing result to achieve parameter compatibility with the network-side converter.
[0011] In one possible implementation, before sending the first information element and the second information element to the device-side converter, the method further includes:
[0012] Verify that the number N of gated entries indicated by the length of the management control list is within the preset range;
[0013] When N exceeds the preset range, discard the management control list and its length, and generate an alarm log.
[0014] In one possible implementation, after sending the first information element and the second information element to the device-side converter, the method further includes:
[0015] If a configuration confirmation message is not received from the converter on the receiving device side, and the first information element and the second information element are retransmitted within a preset timeout period, up to a maximum of a preset number of retries.
[0016] If the configuration confirmation message is not received after the preset number of retries, the time-sensitive network gating policy corresponding to this parameter configuration will be marked as unschedulable, and the upper-layer network management system will be notified.
[0017] Secondly, this application provides a parameter configuration method applied to a device-side converter, the method comprising:
[0018] The system receives a first information element and a second information element sent by the network-side converter. The first information element is encapsulated by the network-side converter according to the length of the management control list to be issued. The first information element includes a parameter name field, a field indicating the parameter value length, and a parameter value field. The parameter value field adopts a 4-byte 32-bit unsigned integer format to represent the number of gate entries in the management control list. The second information element is encapsulated by the network-side converter according to the management control list to be issued. The second information element consists of N consecutively arranged gate entries, where N is a positive integer value indicated by the length of the management control list. Each gate entry is fixed at 7 bytes, including a 1-byte gate operation name, a 1-byte gate operation entry length, a 1-byte flow gate status, and a 4-byte time interval. The value of the gate operation entry length is fixed at 5. The second information element does not contain a parameter value length field.
[0019] The first and second information elements are parsed based on a predefined fixed field length to obtain the parsing result;
[0020] Configure a local time-sensitive network gating strategy based on the parsing results to achieve parameter compatibility with the network-side converter.
[0021] In one possible implementation, after configuring the local time-sensitive network gating policy based on the parsing results, the method further includes:
[0022] Generate a configuration confirmation message to indicate successful configuration;
[0023] Send the configuration confirmation message to the network-side converter.
[0024] Thirdly, this application provides a parameter configuration device for use in a network-side converter, the device comprising:
[0025] The acquisition module is used to obtain the management control list to be issued and the length of the management control list;
[0026] The first encapsulation module is used to encapsulate the length of the management control list into a first information element. The first information element includes a parameter name field, a field indicating the length of the parameter value, and a parameter value field. The parameter value field adopts a 4-byte 32-bit unsigned integer format and is used to represent the number of gate entries in the management control list.
[0027] The second encapsulation module is used to encapsulate the management control list into a second information element. The second information element consists of N consecutively arranged gate entries, where N is a positive integer value indicated by the length of the management control list. Each gate entry is fixed at 7 bytes, including 1 byte of gate operation name, 1 byte of gate operation entry length, 1 byte of flow gate status, and 4 bytes of time interval. The value of the gate operation entry length is fixed at 5. The second information element does not contain a parameter value length field.
[0028] The delivery module sends the first and second information elements to the device-side converter, so that the device-side converter can parse the first and second information elements based on a predefined fixed field length, obtain the parsing result, and configure a local time-sensitive network gating policy according to the parsing result to achieve parameter compatibility with the network-side converter.
[0029] In one possible implementation, the device further includes: a verification module and an alarm module;
[0030] The verification module is used to verify whether the number N of gated entries indicated by the length of the management control list is within a preset range;
[0031] The alarm module is used to discard the management control list and its length, and generate an alarm log when N exceeds a preset range.
[0032] In one possible implementation, the device further includes: a confirmation module and a marking module;
[0033] The confirmation module is used to receive the configuration confirmation message sent by the converter on the device side, and if the configuration confirmation message is not received within the preset timeout period, retransmit the first information element and the second information element within a limit of no more than the preset number of retries;
[0034] The marking module is used to mark the time-sensitive network gating policy corresponding to the current parameter configuration as unschedulable if a configuration confirmation message is not received after reaching a preset number of retries, and to notify the upper-layer network management system.
[0035] Fourthly, this application provides a parameter configuration device applied to a device-side converter, comprising:
[0036] The receiving module is used to receive a first information element and a second information element sent by the network-side converter. The first information element is encapsulated by the network-side converter according to the length of the management control list to be issued. The first information element includes a parameter name field, a field indicating the parameter value length, and a parameter value field. The parameter value field adopts a 4-byte 32-bit unsigned integer format to represent the number of gate entries in the management control list. The second information element is encapsulated by the network-side converter according to the management control list to be issued. The second information element consists of N consecutively arranged gate entries, where N is a positive integer value indicated by the length of the management control list. Each gate entry is fixed at 7 bytes, including a 1-byte gate operation name, a 1-byte gate operation entry length, a 1-byte flow gate status, and a 4-byte time interval. The value of the gate operation entry length is fixed at 5. The second information element does not contain a parameter value length field.
[0037] The parsing module is used to parse the first and second information elements based on a predefined fixed field length to obtain the parsing result;
[0038] The configuration module is used to configure local time-sensitive network gating policies based on the parsing results, so as to achieve parameter compatibility with the network-side converter.
[0039] In one possible implementation, the device further includes a generation module and a feedback module;
[0040] The generation module is used to generate a configuration confirmation message indicating successful configuration.
[0041] The feedback module is used to send configuration confirmation messages to the network-side converter.
[0042] Fifthly, this application provides an electronic device, including: a processor, and a memory communicatively connected to the processor.
[0043] The memory stores the instructions that the computer executes.
[0044] A parameter configuration method in which a processor executes computer execution instructions stored in memory to implement the invention of the first or second aspect.
[0045] In a sixth aspect, this application provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement a parameter configuration method for the first or second aspect of the invention.
[0046] In a seventh aspect, this application provides a computer program product, including a computer program, which, when executed by a processor, is used to implement a parameter configuration method for the invention as described in the first or second aspect.
[0047] Eighthly, this application provides a chip, the chip including at least one processor, the processor being used to execute program instructions to implement a parameter configuration method of the invention in the first or second aspect.
[0048] Based on the implementation methods provided in the above aspects, this application can be further combined to provide more implementation methods.
[0049] This application provides a parameter configuration method, apparatus, device, medium, and product, comprising: first, obtaining a management control list to be issued and the length of the management control list; then, encapsulating the length of the management control list into a first information element, the first information element including a parameter name field, a field indicating the length of the parameter value, and a parameter value field, the parameter value field using a 4-byte 32-bit unsigned integer format, used to represent the number of gated entries in the management control list; and finally, encapsulating the management control list into a second information element, the second information element consisting of N consecutively arranged gated entries, where N is the length of the management control list. The first and second information elements are sent to the device-side converter. The device-side converter parses the first and second information elements based on the predefined fixed field lengths, obtains the parsing results, and configures the local time-sensitive network gating policy according to the parsing results, achieving parameter compatibility with the network-side converter. This achieves the following technical effects: by uniformly adopting a 4-byte 32-bit unsigned integer format for the parameter value field of the management control list length, and explicitly following the semantic definition of the number of gating entries in the IEEE standard, it effectively solves the implementation inconsistency problem caused by the inconsistent parameter value lengths between the 3GPP protocol and the IEEE standard. This ensures the consistency of parameter semantics between network-side converters and device-side converters from different vendors, significantly improving the operational performance and interoperability of the 5G and TSN converged architecture. The management control list adopts a fixed 7-byte gated entry structure and omits the outer parameter value length field, avoiding the repeated carrying of redundant length information in the traditional TLV format. In high-frequency scheduling scenarios, this can significantly reduce the number of bytes in control messages, saving bandwidth resources, and is particularly suitable for resource-constrained wireless backhaul or industrial field networks. Thus, by unifying the parameter format, fixing the gated entry structure, and removing redundant fields, high-efficiency, low-latency, and highly compatible TSN gated parameter configuration is achieved while ensuring protocol compatibility, providing key technical support for the deep integration of 5G and TSN. Attached Figure Description
[0050] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0051] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.
[0052] Figure 1 is a flowchart illustrating a parameter configuration method provided in an embodiment of this application.
[0053] Figure 2 is a flowchart illustrating a parameter configuration method provided in an embodiment of this application.
[0054] Figure 3 is a flowchart illustrating a parameter configuration method provided in an embodiment of this application.
[0055] Figure 4 is a schematic diagram of a parameter configuration device provided in an embodiment of this application.
[0056] Figure 5 is a schematic diagram of the structure of a parameter configuration device provided in an embodiment of this application.
[0057] Figure 6 is a schematic diagram of the structure of an electronic device provided in an embodiment of this application.
[0058] Figure label:
[0059] 410 - Acquisition module; 420 - First encapsulation module; 430 - Second encapsulation module; 440 - Distribution module; 510 - Receiving module; 520 - Parsing module; 530 - Configuration module; 610 - Processor; 620 - Memory; 630 - Communication component; 640 - Bus. Detailed Implementation
[0060] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.
[0061] In the embodiments of this application, the terms "first" and "second" are used to distinguish identical or similar items with substantially the same function and effect. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and that "first" and "second" do not necessarily imply difference. It should be noted that in the embodiments of this application, the words "exemplary" or "for example" are used to indicate that something is being used as an example, illustration, or description. Any embodiment or design scheme described as "exemplary" or "for example" in this application should not be construed as being better or more advantageous than other embodiments or design schemes. Specifically, the use of "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner. In the embodiments of this application, "at least one" refers to one or more, and "more than one" refers to two or more.
[0062] It should be noted that the phrase "at...time" in the embodiments of this application can refer to the instant at which a certain situation occurs, or to a period of time after the occurrence of a certain situation; the embodiments of this application do not specifically limit this. Furthermore, the parameter configuration method provided in the embodiments of this application is merely an example; a parameter configuration method may include more or fewer elements.
[0063] In the converged architecture of 5G and TSN, the network-side converter needs to send gating scheduling parameters to the device-side converter in order to achieve end-to-end deterministic data transmission and ensure the real-time performance and reliability of time-sensitive services. This is the core prerequisite for the converged architecture of 5G and TSN to realize the time-sensitive scheduling function.
[0064] In the existing technology, when encapsulating the two key gating scheduling parameters, namely the management control list and the length of the management control list, according to the relevant 3GPP protocols, the three-field structure commonly used in this field is usually adopted, namely the parameter name, the parameter value length, and the parameter value. This encapsulation method is the mainstream parameter encapsulation form in the industry at present.
[0065] However, existing technologies suffer from two major technical defects that severely impact the operational performance and interoperability of the 5G and TSN converged architecture: First, the 3GPP protocol's description of the parameter value length for the management control list is ambiguous. Specifically, the 3GPP protocol indicates the parameter value length in the management control list as 2 bytes, while the relevant IEEE standards explicitly require the parameter value to be a 32-bit unsigned integer, corresponding to a byte length of 4 bytes. This difference between the 3GPP protocol and the relevant IEEE standards leads to different manufacturers using different byte length standards when implementing this parameter encapsulation, easily resulting in inconsistent implementation schemes and thus affecting interoperability between devices. Second, existing technologies use the TLV variable-length format for encapsulating management control lists. This format requires an additional length field to identify the length of the list content. Not only is a length field included within each gated entry, but a redundant parameter value length field is also carried in the outer layer, increasing the protocol's data transmission overhead, prolonging the parameter parsing time of the device-side converter, reducing parsing efficiency, and ultimately affecting the real-time performance of TSN scheduling, failing to meet the low-latency, high-reliability transmission requirements of time-sensitive services.
[0066] Based on this, embodiments of this application propose a parameter configuration method, apparatus, device, medium, and product, which can be used in the field of digital information transmission technology and aims to solve the above-mentioned technical problems of the prior art. By uniformly adopting a 4-byte 32-bit unsigned integer format for the parameter value field of the management control list length, it is compatible with IEEE semantics and eliminates protocol ambiguity. At the same time, the management control list is encapsulated as a second information element consisting of N fixed 7-byte gating entries, and the outer parameter value length field is omitted. Thus, through a compact and fixed format design, the device-side converter can directly parse parameters based on a predefined fixed field length without dynamically calculating the length. This significantly reduces transmission overhead and improves parsing speed while ensuring parameter compatibility between the network-side converter and the device-side converter, meeting the requirements of time-sensitive networks for efficient and reliable gating scheduling.
[0067] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.
[0068] Figure 1 is a flowchart illustrating a parameter configuration method according to an embodiment of this application. The parameter configuration method of this embodiment is applied to a network-side converter. As shown in Figure 1, the method includes:
[0069] S101. Obtain the management control list to be issued and the length of the management control list.
[0070] In this application embodiment, a parameter configuration method is provided, which can be applied to the network-side converter in a 5G and TSN converged architecture. This method aims to solve the problems of low parameter parsing efficiency and poor interoperability between devices caused by inconsistent protocol definitions and redundant message formats in the prior art, thereby achieving efficient, reliable, and low-latency gating scheduling parameter distribution.
[0071] Specifically, the network-side converter first obtains the management control list to be issued and its corresponding length. The management control list defines the gating behavior of the Time-Aware Shaper (TAS) for different priority queues within each scheduling cycle. The length of the management control list, denoted as a positive integer N, indicates the number of gate entries contained in the list.
[0072] S102. Encapsulate the length of the management control list as the first information element.
[0073] In this embodiment of the application, the first information element includes a parameter name field, a field for indicating the length of the parameter value, and a parameter value field. The parameter value field adopts a 4-byte 32-bit unsigned integer format and is used to represent the number of gate entries in the management control list.
[0074] Specifically, the network-side converter can then encapsulate the length of the management control list into a first information element. This first information element follows the basic structure of 3GPP Ethernet port parameters, including three fields: the parameter name field, the length of the Ethernet port parameter value field, and the Ethernet port parameter value field.
[0075] The parameter name field identifies the parameter type as "AdminControlListLength"; the field indicating the length of the parameter value conforms to the general format requirements of the 3GPP protocol; the parameter value field uses a 4-byte 32-bit unsigned integer format, precisely matching the IEEE standard requirements, while also being compatible with the 3GPP protocol encapsulation framework, to accurately represent the number N of gated entries in the management control list.
[0076] It should be noted that although there is ambiguity in the parameter value length field of the management control list length in the 3GPP protocol (it was once interpreted as 2 bytes), this implementation clearly follows the IEEE standard and unifies the actual parameter value to 4 bytes, thereby eliminating differences in cross-vendor implementation.
[0077] S103. Encapsulate the management control list as a second information element.
[0078] In this embodiment of the application, the second information element consists of N consecutively arranged gating entries, where N is a positive integer value indicated by the length of the management control list. Each gating entry is fixed at 7 bytes, including 1 byte of gating operation name, 1 byte of gating operation entry length, 1 byte of flow gate status, and 4 bytes of time interval. The value of the gating operation entry length is fixed at 5. The second information element does not contain a parameter value length field.
[0079] Specifically, the network-side converter can then encapsulate the management control list into a second information element. This second information element consists of N consecutively arranged gated entries, each strictly fixed at 7 bytes, and organized in the following order:
[0080] The first byte is the gate operation name (GateOperationName), which specifies the gate operation type, such as setting the gate state and time interval (SetGateAndIPV).
[0081] The second byte is the gate operation entry length (GateOperationEntryLength), which is fixed at 5, indicating that subsequent operation parameters occupy a total of 5 bytes.
[0082] The third byte is the StreamGateState, which indicates whether the gate is open or closed.
[0083] Bytes 4 through 7 represent the time interval (TimeInterval), specifically a 32-bit unsigned integer in nanoseconds, indicating the duration of the current gating state.
[0084] Crucially, the second information element does not include the outer parameter value length field. In other words, when encapsulating the management control list, the length indication field preceding the parameter value in the traditional TLV structure is omitted. This is because N is explicitly stated in the first information element, allowing the device-side converter to directly read all control entries based on a fixed offset of N×7 bytes without additional length information. This simplifies the encapsulation structure, significantly reducing protocol overhead and improving parsing efficiency.
[0085] S104. Send the first information element and the second information element to the device-side converter so that the device-side converter can parse the first information element and the second information element based on a predefined fixed field length, obtain the parsing result, and configure the local time-sensitive network gating policy according to the parsing result to achieve parameter compatibility with the network-side converter.
[0086] Specifically, the network-side converter can send the first and second information elements to the device-side converter via a control plane interface (such as a dedicated TSN management channel). Upon receiving these first and second information elements, the device-side converter can directly parse them based on predefined fixed field lengths (e.g., 4 bytes for the parameter value field of the first information element and 7 bytes for each gated entry of the second information element). This eliminates the need for dynamic TLV traversal or length inference, allowing for rapid acquisition of the complete gating and scheduling strategy. Based on this, the converter can configure the gating behavior of its local TSN switching engine or virtual Ethernet port, ultimately achieving parameter semantic compatibility and scheduling synchronization with the network-side converter, ensuring deterministic transmission of end-to-end time-sensitive services.
[0087] This embodiment provides a parameter configuration method. First, the management control list to be issued and its length are obtained. Next, the management control list length is encapsulated into a first information element, which includes a parameter name field, a field indicating the parameter value length, and a parameter value field. The parameter value field uses a 4-byte 32-bit unsigned integer format to represent the number of gated entries in the management control list. Then, the management control list is encapsulated into a second information element, which consists of N consecutively arranged gated entries, where N is a positive integer value indicated by the management control list length. Each gated entry is fixed at 7 bytes, including a 1-byte gate operation name, a 1-byte gate operation entry length, a 1-byte flow gate status, and a 4-byte time interval. The gate operation entry length is fixed at 5. The second information element does not contain a parameter value length field. Finally, the first and second information elements are sent to the device-side converter, so that the device-side converter parses the first and second information elements based on a predefined fixed field length, obtains the parsing result, and configures a local time-sensitive network gating policy according to the parsing result to achieve parameter compatibility with the network-side converter.
[0088] The following technical effects were achieved: By uniformly adopting a 4-byte 32-bit unsigned integer format for the parameter value field of the management control list length, and explicitly following the semantic definition of the number of gated entries in the IEEE standard, the inconsistency problem caused by the inconsistent parameter value length between the 3GPP protocol and the IEEE standard was effectively solved. This ensures the consistency of parameter semantics between network-side converters and device-side converters from different vendors, significantly improving the operational performance and interoperability of the 5G and TSN converged architecture. The management control list adopts a fixed 7-byte gated entry structure and omits the outer parameter value length field, avoiding the repeated carrying of redundant length information in the traditional TLV format. In high-frequency scheduling scenarios, the number of bytes in the control message can be significantly reduced, saving bandwidth resources, especially suitable for resource-constrained wireless backhaul or industrial field networks. The device-side converter can directly read data by offset based on a predefined fixed field length (such as a 4-byte length value, 7-byte gated entry), without dynamically parsing the TLV nested structure or calculating the variable-length field boundary, reducing parsing latency. This deterministic parsing mechanism meets the stringent requirements of TSN for microsecond-level scheduling accuracy and low jitter, ensuring end-to-end deterministic transmission for time-sensitive services (such as industrial control and vehicle-to-everything). The fixed format design ensures a high degree of symmetry and determinism between the encapsulation logic of the network-side converter and the parsing logic of the device-side converter, reducing configuration failures caused by field misalignment and length misjudgment, and improving the reliability and maintainability of the entire 5G and TSN converged system. Thus, by unifying parameter formats, fixing the gating entry structure, and removing redundant fields, high-efficiency, low-latency, and highly compatible TSN gating parameter configuration is achieved while ensuring protocol compatibility, providing key technical support for the deep integration of 5G and TSN.
[0089] In one possible implementation, before sending the first information element and the second information element to the device-side converter, the method further includes: verifying whether the number N of gated entries indicated by the length of the management control list is within a preset range; if N exceeds the preset range, discarding the management control list and the length of the management control list, and generating an alarm log.
[0090] In this embodiment of the application, before sending the first information element and the second information element to the device-side converter, the method further includes a parameter compliance verification step to prevent abnormal configuration from causing resource exhaustion or scheduling logic errors in the TSN collaborative scheduling system (including the network-side converter, the device-side converter and the associated TSN bridging device).
[0091] Specifically, the network-side converter first parses the length of the acquired management control list to extract the indicated number of gated entries, N (where N is a positive integer). Then, the network-side converter compares this N value with a preset range. This preset range can be pre-configured based on factors such as the actual deployment scenario, the hardware processing capabilities of the device-side converter, memory limitations, and TSN scheduling cycle constraints. For example, it can be set to 1 ≤ N ≤ 1024, where the lower limit ensures the gated list is not empty, and the upper limit prevents scheduling table overflow or real-time performance degradation due to an excessive number of gated entries.
[0092] If N exceeds the preset range (e.g., N=0, N is negative, or N>1024, etc.), it is considered an invalid configuration request. In this case, the network-side converter can proactively discard the management control list to be sent and its corresponding length, suspending the parameter sending process to avoid transmitting non-compliant data to the device-side converter, causing parsing failure or gating policy errors.
[0093] Meanwhile, the network-side converter can generate a structured alarm log, which includes, but is not limited to, the following information: the type of abnormal event (such as the number of gated entries exceeding the limit); the actual received N value; the preset range; the timestamp; and the associated TSN stream identifier or Ethernet port identifier (ID).
[0094] This alarm log can be collected by upper-level management systems, such as the Network Exposure Function (NEF) in the 5G core network or the TSN configuration server, for fault diagnosis, policy optimization, or automatic repair triggering, thereby improving the security, observability, and self-healing capabilities of the entire 5G and TSN converged system.
[0095] Through the above verification mechanism, this implementation method effectively intercepts abnormal parameters caused by configuration errors, protocol parsing deviations, or external attacks, ensuring the stable operation of the gated scheduling system and providing traceable technical evidence.
[0096] In one possible implementation, after sending the first information element and the second information element to the device-side converter, the method further includes: receiving a configuration confirmation message sent by the device-side converter, and if no configuration confirmation message is received within a preset timeout period, retransmitting the first information element and the second information element for a maximum of a preset number of retries; if no configuration confirmation message is received after reaching the preset number of retries, marking the time-sensitive network gating policy corresponding to this parameter configuration as unschedulable, and notifying the upper-layer network management system.
[0097] In this embodiment of the application, after the first information element and the second information element are successfully sent to the device-side converter, the network-side converter can further execute a configuration reliability guarantee mechanism to deal with abnormal situations such as packet loss, device-side converter processing congestion or temporary failure that may occur during wireless or wired transmission.
[0098] Specifically, the network-side converter can start a timer and wait to receive a configuration confirmation message from the device-side converter. This configuration confirmation message indicates that the device-side converter has successfully parsed the gating parameters and completed the configuration of the local TSN gating policy. The configuration confirmation message can use a lightweight response format, such as an acknowledgment (ACK) or a negative acknowledgment (NACK), and its content can include the configuration status (such as success, insufficient resources, or invalid parameters) and the associated TSN flow ID.
[0099] If the network-side converter does not receive the configuration confirmation message within a preset timeout period (e.g., 500 milliseconds, which can be dynamically adjusted based on network round-trip time), it determines that the configuration transmission or application may have failed. In this case, the network-side converter can retransmit the first and second information elements, but the number of retransmissions is strictly limited, i.e., it cannot exceed a preset number of retries (e.g., 3 times). This limitation can prevent control channel congestion or scheduling delay accumulation due to continuous retransmissions, which could affect the normal configuration of other TSN services.
[0100] If the network-side converter fails to receive any valid configuration confirmation message after reaching the preset number of retries, the parameter configuration can be considered a complete failure. To prevent invalid policies from being misused or the scheduling engine from entering an uncertain state, the network-side converter can mark the TSN gating policy corresponding to this parameter configuration as unschedulable. This mark can be applied to the corresponding TSN flow, Ethernet port, or Quality of Service (QoS) flow template, causing it to be actively excluded in subsequent scheduling cycles, thus preventing data flows from being incorrectly forwarded or blocked due to the lack of valid gating rules.
[0101] Simultaneously, the network-side converter can also generate a structured fault notification message and send it to the upper-layer network management system. The upper-layer network management system can include the NEF (Neural Flow Provider) in the 5G core network, an Application Function (AF) or a standalone TSN central configuration server. The fault notification message can include: the identifier of the failed TSN flow, a summary of configuration parameters, the number of retries, a timestamp, and suggested actions (such as renegotiating the scheduling window or switching to an alternative path). This configuration reliability assurance mechanism not only improves the observability and maintainability of the gating scheduling system but also provides upper-layer applications with a basis for rapid fault recovery decisions, thereby ensuring the availability and deterministic service capabilities of the 5G and TSN converged network in key scenarios such as industrial automation and smart grids.
[0102] Figure 2 is a schematic flowchart of a parameter configuration method provided in an embodiment of this application. The parameter configuration method of this embodiment is applied to a device-side converter. As shown in Figure 2, the method includes:
[0103] S201, Receive the first information element and the second information element sent by the network-side converter.
[0104] In this embodiment, the first information element is encapsulated by the network-side converter according to the length of the management control list to be issued. The first information element includes a parameter name field, a field indicating the parameter value length, and a parameter value field. The parameter value field adopts a 4-byte 32-bit unsigned integer format to represent the number of gate entries in the management control list. The second information element is encapsulated by the network-side converter according to the management control list to be issued. The second information element consists of N consecutively arranged gate entries, where N is a positive integer value indicated by the length of the management control list. Each gate entry is fixed at 7 bytes, including 1 byte of gate operation name, 1 byte of gate operation entry length, 1 byte of flow gate status, and 4 bytes of time interval. The value of the gate operation entry length is fixed at 5. The second information element does not contain a parameter value length field.
[0105] Specifically, this embodiment also provides a parameter configuration method, which is applied to the device-side converter to efficiently and reliably receive and parse gating scheduling parameters from the network-side converter, thereby enabling time-sensitive service transmission in coordination with the 5G core network.
[0106] First, the device-side converter can receive the first and second information elements sent by the network-side converter through the control plane interface (e.g., a dedicated TSN management channel).
[0107] The first information element is generated by the network-side converter based on the length of the management control list to be issued. Its structure follows the general format of Ethernet port parameters in the 3GPP protocol and includes three fields: parameter name field, field indicating the length of parameter value field, and parameter value field.
[0108] Specifically, the parameter name field identifies the parameter type as "AdminControlListLength"; the field indicating the length of the parameter value shows the number of bytes occupied by the subsequent parameter value; the parameter value field uses a 4-byte 32-bit unsigned integer format to precisely represent the number N of gated entries contained in the management control list. This design explicitly aligns with the IEEE standard, avoiding cross-vendor compatibility issues caused by protocol ambiguity.
[0109] The second information element is generated by the network-side converter based on the complete management control list, and consists of N consecutively arranged gated entries. Each gated entry is strictly fixed at 7 bytes and is organized in the following order:
[0110] The first byte is the name of the gate operation. For example, if the value is SetGateAndIPV, it means setting the gate state and time interval.
[0111] The second byte is the length of the gating operation entry, which is fixed at 5, indicating that subsequent operation parameters occupy a total of 5 bytes.
[0112] The third byte represents the gate status, with a value of 0x00 (closed) or 0x01 (open).
[0113] The fourth to seventh bytes represent the time interval, specifically a 32-bit unsigned integer in nanoseconds, indicating the duration of the current gate state.
[0114] Crucially, the second information element does not include the outer parameter value length field. This is because N has already been explicitly stated in the first information element, allowing the device-side converter to determine data boundaries without relying on redundant length information, thus simplifying the parsing logic.
[0115] S202. Based on the predefined fixed field length, parse the first information element and the second information element to obtain the parsing result.
[0116] Specifically, the device-side converter can directly parse the first and second information elements based on a predefined fixed field length. This includes: extracting a 4-byte integer from the parameter value field of the first information element to obtain the number of gated entries N; reading N gated entries sequentially in 7-byte units, starting from the beginning of the second information element; and parsing the gate operation name, flow gate state, and time interval by offset for each gated entry, without requiring dynamic TLV traversal or length inference.
[0117] S203. Configure a local time-sensitive network gating strategy based on the parsing results to achieve parameter compatibility with the network-side converter.
[0118] Specifically, finally, the device-side converter can configure local TSN based on the parsing results. This strategy can be loaded into the gated scheduling table of the TSN bridging engine or virtual Ethernet port to control the forwarding behavior of specific priority queues within a specified time window. Through this mechanism, the device-side converter and the network-side converter achieve full compatibility in parameter semantics, format, and scheduling timing, ensuring end-to-end deterministic transmission of time-sensitive services such as industrial control and vehicle networking in the converged 5G backhaul and TSN access network.
[0119] In addition, after successful configuration, the device-side converter can generate and return a configuration confirmation message (such as ACK) to the network-side converter to support reliability assurance mechanisms (such as timeout retransmission, fault isolation, etc.) and form a closed-loop control.
[0120] In this embodiment, by employing predefined fixed field lengths (such as 4-byte length values and 7-byte gating entries), the device-side converter does not need to perform dynamic length reading and boundary judgment in the traditional TLV structure, and can directly parse data according to the offset address order. This deterministic parsing mechanism reduces processing latency, meets the TSN's requirement for microsecond-level scheduling response, and ensures the real-time performance of critical services such as industrial control and vehicle networking. The parameter value field for the length of the management control list is explicitly unified as a 4-byte 32-bit unsigned integer, strictly aligning with the semantic definition of the number of gating entries in the IEEE standard, avoiding implementation discrepancies caused by inconsistencies in parameter value lengths between the IEEE standard and 3GPP. Therefore, network-side converters and device-side converters from different vendors can interact under the same semantics, significantly improving the interoperability of the 5G and TSN converged system.
[0121] The second information element omits the outer parameter value length field, and each gated entry uses a compact 7-byte fixed structure, avoiding the storage and parsing of redundant length information. In resource-constrained embedded device-side converters, due to the use of a predefined fixed field length, the device-side converter's central processing unit (CPU) does not need to dynamically calculate data boundaries. Parsing each 7-byte gated entry requires only a fixed number of CPU clock cycles, significantly improving the real-time performance of scheduling configuration. This design saves memory bandwidth and CPU clock cycles, making it particularly suitable for high-density port or high-frequency scheduling scenarios. The fixed format simplifies and determinizes the parsing logic, effectively preventing parsing crashes or policy mismatches caused by variable-length field misalignment, length overflow, or injection of non-compliant data. Furthermore, this method does not rely on complex protocol stack support, facilitating deployment in lightweight TSN terminals or industrial gateways, improving the overall architecture's reliability and adaptability.
[0122] This implementation method enables the device-side converter to efficiently, reliably, and with low overhead complete the gating policy configuration by fixing the field length, unifying the parameter format, and removing redundant information. While ensuring compatibility with the network-side converter parameters, it provides solid support for the deep integration of 5G and TSN.
[0123] In one possible implementation, after configuring a local time-sensitive network gating policy based on the parsing results, the method further includes: generating a configuration confirmation message to indicate successful configuration; and sending the configuration confirmation message to the network-side converter.
[0124] Specifically, after the device-side converter successfully configures the local TSN gating policy based on the parsing result, this embodiment also includes a step of the device-side converter sending a configuration confirmation message to the network-side converter.
[0125] Specifically, the device-side converter first generates a structured configuration confirmation message to explicitly indicate that the gating parameter distribution and local policy loading have been completed and correctly executed. This configuration confirmation message can use a lightweight response format, and its content includes, but is not limited to, a confirmation status code, an associated identifier, a timestamp, and a verification digest.
[0126] The confirmation status code can be success, partial success, or failure. The association identifier includes the corresponding TSN flow ID, Ethernet port ID, or QoS flow identifier, used to associate the configuration confirmation message with the original configuration request. The timestamp records the local time when the policy takes effect, facilitating timing alignment and troubleshooting. The checksum can be a Cyclic Redundancy Check (CRC) value or hash value calculated on the received management control list, used to verify data integrity.
[0127] Subsequently, the device-side converter can send configuration confirmation messages to the network-side converter through a predefined control plane channel (such as the management plane associated with the N6 interface in the 3GPP architecture or a dedicated TSN configuration channel).
[0128] This confirmation mechanism enables the network-side converter to promptly obtain the configuration execution status of the device-side converter, thereby terminating the retransmission process (if a retry was initiated due to a timeout), updating the internal state machine, marking the TSN flow as scheduled, and sending it to the upper-layer system (such as AF, NEF, or TSN configuration server) to complete the end-to-end configuration loop.
[0129] By introducing this confirmation feedback mechanism, this implementation not only improves the reliability and observability of control plane interaction in 5G and TSN converged networks, but also provides key support for achieving adaptive scheduling, rapid fault isolation, and Service Level Agreement (SLA) assurance, effectively avoiding resource waste or service interruption caused by unknown configuration status.
[0130] Figure 3 is a flowchart illustrating a parameter configuration method provided in an embodiment of this application. As shown in Figure 3, the method includes:
[0131] S301, The network-side converter obtains the management control list to be issued and the length of the management control list.
[0132] S302, The network-side converter encapsulates the length of the management control list as the first information element.
[0133] S303, the network-side converter encapsulates the management control list as a second information element.
[0134] S304, The network-side converter sends the first information element and the second information element to the device-side converter.
[0135] S305, The device-side converter receives the first information element and the second information element sent by the network-side converter.
[0136] S306. The device-side converter parses the first and second information elements based on a predefined fixed field length to obtain the parsing result.
[0137] S307. The device-side converter configures a local time-sensitive network gating policy based on the parsing results to achieve parameter compatibility with the network-side converter.
[0138] S308, The device-side converter generates a configuration confirmation message to indicate that the configuration was successful.
[0139] S309, The device-side converter sends a configuration confirmation message to the network-side converter.
[0140] S310. The network-side converter receives the configuration confirmation message sent by the device-side converter, and if it does not receive the configuration confirmation message within the preset timeout period, it retransmits the first information element and the second information element within a limit not exceeding the preset number of retries.
[0141] This application embodiment can divide an electronic device or main control device into functional modules according to the above method examples. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing unit. The integrated unit can be implemented in hardware or as a software functional module. It should be noted that the module division in this embodiment is illustrative and only represents one logical functional division; in actual implementation, there may be other division methods.
[0142] Figure 4 is a schematic diagram of a parameter configuration device provided in an embodiment of this application. As shown in Figure 4, the device is applied to a network-side converter and includes: an acquisition module 410, a first encapsulation module 420, a second encapsulation module 430, and a distribution module 440.
[0143] The acquisition module 410 is used to acquire the management control list to be issued and the length of the management control list;
[0144] The first encapsulation module 420 is used to encapsulate the length of the management control list into a first information element. The first information element includes a parameter name field, a field for indicating the length of the parameter value, and a parameter value field. The parameter value field adopts a 4-byte 32-bit unsigned integer format and is used to represent the number of gate entries in the management control list.
[0145] The second encapsulation module 430 is used to encapsulate the management control list into a second information element. The second information element consists of N consecutively arranged gate entries, where N is a positive integer value indicated by the length of the management control list. Each gate entry is fixed at 7 bytes, including 1 byte of gate operation name, 1 byte of gate operation entry length, 1 byte of flow gate status, and 4 bytes of time interval. The value of the gate operation entry length is fixed at 5. The second information element does not contain a parameter value length field.
[0146] The sending module 440 is used to send the first information element and the second information element to the device-side converter, so that the device-side converter can parse the first information element and the second information element based on a predefined fixed field length, obtain the parsing result, and configure the local time-sensitive network gating policy according to the parsing result to achieve parameter compatibility with the network-side converter.
[0147] In one possible implementation, the device further includes: a verification module and an alarm module;
[0148] The verification module is used to verify whether the number N of gated entries indicated by the length of the management control list is within a preset range;
[0149] The alarm module is used to discard the management control list and its length, and generate an alarm log when N exceeds a preset range.
[0150] In one possible implementation, the device further includes: a confirmation module and a marking module;
[0151] The confirmation module is used to receive the configuration confirmation message sent by the converter on the device side, and if the configuration confirmation message is not received within the preset timeout period, retransmit the first information element and the second information element within a limit of no more than the preset number of retries;
[0152] The marking module is used to mark the time-sensitive network gating policy corresponding to the current parameter configuration as unschedulable if a configuration confirmation message is not received after reaching a preset number of retries, and to notify the upper-layer network management system.
[0153] Figure 5 is a second structural schematic diagram of a parameter configuration device provided in an embodiment of this application. As shown in Figure 5, the device is applied to a device-side converter and includes: a receiving module 510, a parsing module 520, and a configuration module 530.
[0154] The receiving module 510 is used to receive a first information element and a second information element sent by the network-side converter. The first information element is encapsulated by the network-side converter according to the length of the management control list to be issued. The first information element includes a parameter name field, a field indicating the parameter value length, and a parameter value field. The parameter value field adopts a 4-byte 32-bit unsigned integer format to indicate the number of gate entries in the management control list. The second information element is encapsulated by the network-side converter according to the management control list to be issued. The second information element consists of N consecutively arranged gate entries, where N is a positive integer value indicated by the length of the management control list. Each gate entry is fixed at 7 bytes, including a 1-byte gate operation name, a 1-byte gate operation entry length, a 1-byte flow gate status, and a 4-byte time interval. The value of the gate operation entry length is fixed at 5. The second information element does not contain a parameter value length field.
[0155] Parsing module 520 is used to parse the first information element and the second information element based on a predefined fixed field length to obtain the parsing result;
[0156] Configuration module 530 is used to configure local time-sensitive network gating policies based on the parsing results, so as to achieve parameter compatibility with network-side converters.
[0157] In one possible implementation, the device further includes a generation module and a feedback module;
[0158] The generation module is used to generate a configuration confirmation message indicating successful configuration.
[0159] The feedback module is used to send configuration confirmation messages to the network-side converter.
[0160] The parameter configuration device provided in this embodiment can execute the parameter configuration method of the above embodiment. Its implementation principle and technical effect are similar, and will not be described again here.
[0161] In the specific implementation of the aforementioned parameter configuration device, each module can be implemented as a processor, which can execute computer execution instructions stored in the memory, thereby enabling the processor to execute the aforementioned parameter configuration method.
[0162] Figure 6 is a schematic diagram of an electronic device provided in an embodiment of this application. As shown in Figure 6, the electronic device includes at least one processor 610 and a memory 620. The electronic device also includes a communication component 630. The processor 610, the memory 620, and the communication component 630 are connected via a bus 640.
[0163] In the specific implementation process, at least one processor 610 executes computer execution instructions stored in memory 620, causing at least one processor 610 to execute a parameter configuration method as executed on the electronic device side as described above.
[0164] The specific implementation process of processor 610 can be found in the above method embodiments, and its implementation principle and technical effect are similar. It will not be repeated here.
[0165] In the above embodiments, it should be understood that the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules within the processor.
[0166] The memory may include high-speed RAM, and may also include non-volatile storage (NVM), such as at least one disk storage.
[0167] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.
[0168] The above description of the functions implemented by electronic devices and main control devices has introduced the solutions provided by the embodiments of the present invention. It is understood that, in order to implement the above functions, the electronic device or main control device includes hardware structures and / or software modules corresponding to the execution of each function. By combining the units and algorithm steps of the various examples described in the embodiments of the present invention, the embodiments of the present invention can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the technical solutions of the embodiments of the present invention.
[0169] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the parameter configuration method described above.
[0170] The aforementioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The readable storage medium can be any available medium accessible to a general-purpose or special-purpose computer.
[0171] An exemplary readable storage medium is coupled to a processor, enabling the processor to read information from and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can reside in an Application Specific Integrated Circuit (ASIC). Alternatively, the processor and the readable storage medium can exist as discrete components in an electronic device or a host device.
[0172] This application also provides a computer program product, which includes a computer program stored in a readable storage medium. At least one processor of an electronic device can read the computer program from the readable storage medium, and the at least one processor executes the computer program to cause the electronic device to perform the solution provided in the above embodiments.
[0173] This application also provides a chip, which includes at least one processor for executing program instructions to perform the solutions provided in the above embodiments.
[0174] Those skilled in the art will understand that all or part of the steps of the above method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it performs the steps of the above method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disk, or optical disk.
[0175] The technical solutions of this application have been described above with reference to the preferred embodiments shown in the accompanying drawings. However, it is readily understood by those skilled in the art that the scope of protection of this application is obviously not limited to these specific embodiments. The above embodiments are only used to illustrate the technical solutions of this application and are not intended to limit them. Although this application 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 or all of the technical features therein. 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 this application.
Claims
1. A parameter configuration method, characterized in that, This method, applied to a network-side converter, includes: acquiring a management control list to be issued and its length; encapsulating the management control list length into a first information element, the first information element including a parameter name field, a field indicating the parameter value length, and a parameter value field, the parameter value field using a 4-byte 32-bit unsigned integer format to represent the number of gated entries in the management control list; encapsulating the management control list into a second information element, the second information element consisting of N consecutively arranged gated entries, where N is a positive integer value indicated by the management control list length, each gated entry is fixed at 7 bytes, including a 1-byte gate operation name, a 1-byte gate operation entry length, a 1-byte flow gate status, and a 4-byte time interval, the gate operation entry length being fixed at 5, and the second information element not containing a parameter value length field; sending the first and second information elements to a device-side converter, so that the device-side converter parses the first and second information elements based on a predefined fixed field length, obtains the parsing result, and configures a local time-sensitive network gating policy according to the parsing result to achieve parameter compatibility with the network-side converter.
2. The method according to claim 1, characterized in that, Before sending the first information element and the second information element to the device-side converter, the method further includes: verifying whether the number N of gated entries indicated by the length of the management control list is within a preset range; when N exceeds the preset range, discarding the management control list and the length of the management control list, and generating an alarm log.
3. The method according to claim 1 or 2, characterized in that, After sending the first information element and the second information element to the device-side converter, the method further includes: receiving a configuration confirmation message sent by the device-side converter; and if the configuration confirmation message is not received within a preset timeout period, retransmitting the first information element and the second information element for a maximum of a preset number of retries; and if the configuration confirmation message is still not received after reaching the preset number of retries, marking the time-sensitive network gating policy corresponding to this parameter configuration as unschedulable and notifying the upper-layer network management system.
4. A parameter configuration method, characterized in that, The method is applied to a device-side converter and includes: receiving a first information element and a second information element sent by a network-side converter. The first information element is encapsulated by the network-side converter according to the length of a management control list to be issued. The first information element includes a parameter name field, a field indicating the parameter value length, and a parameter value field. The parameter value field adopts a 4-byte 32-bit unsigned integer format to represent the number of gated entries in the management control list. The second information element is encapsulated by the network-side converter according to the management control list to be issued. The second information element consists of N consecutively arranged gated entries, where N is a positive integer value indicated by the length of the management control list. Each gated entry is fixed at 7 bytes, including a 1-byte gate operation name, a 1-byte gate operation entry length, a 1-byte flow gate status, and a 4-byte time interval. The value of the gate operation entry length is fixed at 5. The second information element does not contain a parameter value length field. The first information element and the second information element are parsed based on a predefined fixed field length to obtain a parsing result. A local time-sensitive network gating policy is configured according to the parsing result to achieve parameter compatibility with the network-side converter.
5. The method according to claim 4, characterized in that, After configuring the local time-sensitive network gating policy based on the parsing result, the method further includes: generating a configuration confirmation message to indicate successful configuration; and sending the configuration confirmation message to the network-side converter.
6. A parameter configuration device, characterized in that, This device, applied to a network-side converter, includes: an acquisition module for acquiring a management control list to be issued and its length; a first encapsulation module for encapsulating the management control list length into a first information element, the first information element including a parameter name field, a field indicating the parameter value length, and a parameter value field, the parameter value field using a 4-byte 32-bit unsigned integer format to represent the number of gated entries in the management control list; and a second encapsulation module for encapsulating the management control list into a second information element, the second information element consisting of N consecutively arranged gated entries, where N is a positive integer indicated by the length of the management control list. The numerical values are as follows: each gating entry is fixed at 7 bytes, including 1 byte for the gating operation name, 1 byte for the gating operation entry length, 1 byte for the flow gate status, and 4 bytes for the time interval. The gating operation entry length is fixed at 5. The second information element does not contain a parameter value length field. The sending module is used to send the first information element and the second information element to the device-side converter, so that the device-side converter can parse the first information element and the second information element based on the predefined fixed field length, obtain the parsing result, and configure the local time-sensitive network gating policy according to the parsing result to achieve parameter compatibility with the network-side converter.
7. A parameter configuration device, characterized in that, This device-side converter includes a receiving module for receiving a first information element and a second information element sent by the network-side converter. The first information element is encapsulated by the network-side converter according to the length of a management control list to be issued. The first information element includes a parameter name field, a field indicating the length of the parameter value, and a parameter value field. The parameter value field uses a 4-byte 32-bit unsigned integer format to represent the number of gated entries in the management control list. The second information element is encapsulated by the network-side converter according to the management control list to be issued, and the second information element consists of N consecutively arranged gated bars. The system consists of an entry, where N is a positive integer value indicated by the length of the management control list. Each gating entry is fixed at 7 bytes, including a 1-byte gating operation name, a 1-byte gating operation entry length, a 1-byte flow gate status, and a 4-byte time interval. The gating operation entry length is fixed at 5. The second information element does not contain a parameter value length field. A parsing module is used to parse the first and second information elements based on predefined fixed field lengths to obtain the parsing result. A configuration module is used to configure a local time-sensitive network gating policy according to the parsing result, achieving parameter compatibility with the network-side converter.
8. An electronic device, characterized in that, include: Memory, processor; The memory stores computer-executable instructions; the processor executes the computer-executable instructions stored in the memory, causing the processor to perform the method as claimed in any one of claims 1 to 3 or any one of claims 4 to 5.
9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as claimed in any one of claims 1 to 3 or any one of claims 4 to 5.
10. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the method as claimed in any one of claims 1 to 3 or any one of claims 4 to 5.