WO2025236927A1 - Optical network system, message scheduling method, communication device, and readable storage medium - Google Patents

Abstract

Disclosed in the present application are an optical network system, a message scheduling method, a communication device, and a readable storage medium. The optical network system comprises a first optical network device (100) and a second optical network device (200), wherein the second optical network device (200) performs uplink transmission on an uplink message with the first optical network device (100) by means of a service channel and at least two management channels, the service channel and all the management channels are bound to transmission containers, and the at least two management channels are bound to the same transmission container.

Description

Optical network systems, message scheduling methods, communication equipment and readable storage media

Cross-reference to related applications

This application is based on and claims priority to Chinese Patent Application No. 202410604701X, filed on May 15, 2024, the entire contents of which are incorporated herein by reference.

Technical Field

This application relates to, but is not limited to, the field of communication equipment, and particularly to an optical network system, a message scheduling method, a communication device, and a readable storage medium.

Background Technology

Optical networks generally refer to wide area networks (WANs), metropolitan area networks (MANs), or newly built large-scale local area networks (LANs) that use optical fiber as the primary transmission medium. Due to their advantages such as high transmission speed and long transmission distance, optical networks are widely used in broadband access for homes and businesses, including Fiber to the Home (FTTH), Fiber to the Room (FTTR), and Fiber to the Office (FTTO). In FTTH, FTTR, and FTTO systems, optical network equipment such as optical line terminal equipment (OLTP) and user-side equipment jointly constitute the optical access network, enabling high-speed data transmission over the fiber optic network. Since the data transmitted between optical network devices is of various types, there are also multiple data transmission channels between them. Different data transmission channels can meet the needs of different services. However, in related optical access network systems, the bandwidth allocation of each data transmission channel is independent, making it difficult to fully utilize the overall system bandwidth and failing to meet the needs of some high-bandwidth scenarios, thus affecting the user experience.

Summary of the Invention

This application provides an optical network system, a message scheduling method, a communication device, and a readable storage medium.

In a first aspect, embodiments of this application provide an optical network system, including: a first optical network device; and a second optical network device, wherein the second optical network device transmits uplink messages to the first optical network device through a service channel and at least two management channels, wherein the service channel and all the management channels are bound to a transmission container, and at least two of the management channels are bound to the same transmission container.

Secondly, embodiments of this application provide a message scheduling method applied to the first optical network device in the optical network system as described in the first aspect. The message scheduling method includes: acquiring a message to be transmitted and identifying the message to be transmitted; when the message to be transmitted is an urgent message, allocating the message to be transmitted to a first queue; when the message to be transmitted is a non-urgent message, slicing and encapsulating the message to be transmitted into multiple message fragments, and allocating the multiple message fragments to a second queue; transmitting the messages in each queue based on transmission priority, wherein the transmission priority of the first queue is higher than the transmission priority of the second queue.

Thirdly, embodiments of this application provide a communication device, including: at least one processor; at least one memory for storing at least one program; and implementing the message scheduling method as described in the fourth aspect when at least one of the programs is executed by at least one of the processors.

Fourthly, embodiments of this application also provide a computer-readable storage medium storing computer-executable instructions for performing the message scheduling method as described in the second aspect.

Attached Figure Description

Figure 1 is a schematic diagram of the structure of the optical network system provided in an embodiment of this application;

Figure 2 is a schematic diagram illustrating the effect of shared bandwidth resources for data transmission channels provided in the embodiments of this application.

Figure 3 is a schematic diagram of shared bandwidth resources for data transmission channels provided in another embodiment of this application;

Figure 4 is a schematic diagram of shared bandwidth resources for data transmission channels provided in another embodiment of this application;

Figure 5 is a schematic diagram of shared bandwidth resources for data transmission channels provided in another embodiment of this application;

Figure 6 is a flowchart of the message scheduling method provided in an embodiment of this application;

Figure 7 is a schematic diagram of message scheduling provided in an embodiment of this application;

Figure 8 is a flowchart of the steps for non-urgent message slice encapsulation provided in an embodiment of this application;

Figure 9 is a schematic diagram of the steps for downlink transmission of a non-urgent message provided in an embodiment of this application;

Figure 10 is a schematic diagram of the structure of a communication device provided in an embodiment of this application.

Detailed Implementation

To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

It is understandable that although functional modules are divided in the device schematic diagram and a logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in a different order than the module division in the device or the order in the flowchart. The terms "first," "second," etc., in the specification or the aforementioned figures are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence.

Currently, in optical access network systems, to provide different services or meet specific network requirements, multiple optical network devices need to transmit different types of message data through multiple different data transmission channels. In situations with high requirements for device management and control, in addition to establishing a service channel, multiple management channels are also established between uplink and downlink devices. Different management channels are used to transmit different types of management and control data. Related technologies can bind a transmission container (T-CONT) to each data transmission channel. By adjusting the bandwidth allocation of each transmission container, the bandwidth allocation of each data transmission channel can be adjusted. For example, when the uplink of a data transmission channel is idle (i.e., the data transmission volume is small), the bandwidth allocation of the corresponding transmission container can be reduced, and the freed-up bandwidth resources can be used by other data transmission channels. Conversely, when the uplink of a data transmission channel is busy (i.e., the data transmission volume is large), the bandwidth resources of the corresponding transmission container can be increased. This allows for the optimization of bandwidth utilization by adjusting the bandwidth resources allocated to each data transmission channel based on the real-time traffic of each channel. Although transmission containers are bound to each data transmission channel, the bandwidth of each channel is still allocated independently. However, the management channel has low bandwidth utilization due to its small data transmission volume and short transmission time, resulting in insufficient overall system bandwidth resources, particularly the management channel. Furthermore, in current optical access network systems, downlink data is transmitted in a first-in, first-out (FIFO) manner. Therefore, during urgent data transmission, it is necessary to wait for the currently transmitting data to complete before transmission begins. If the currently transmitting data is large, this increases the latency of urgent data transmission, failing to meet the needs of scenarios with high latency requirements and impacting user experience.

Based on this, this application provides an optical network system, a packet scheduling method, a communication device, and a readable storage medium. It integrates and binds multiple management channels into a single transmission container, effectively allowing multiple management channels to share a portion of the bandwidth. This releases bandwidth previously occupied independently by some channels, reduces bandwidth overhead, and improves system bandwidth utilization. Furthermore, during downlink packet transmission, packets are transmitted sequentially based on transmission priority, and packets are sliced and encapsulated to shorten the transmission time of individual packets. This not only enables priority transmission of urgent packets but also effectively reduces the transmission latency of urgent packets, thus meeting the needs of scenarios with high bandwidth and latency requirements and improving the user experience.

Firstly, referring to Figure 1, which is a schematic diagram of the structure of an optical network system provided in an embodiment of this application, it can be seen that the optical network system has a first optical network device 100 and a second optical network device 200. The first optical network device 100 serves as the uplink device of the optical network system, and the second optical network device 200 serves as the downlink device of the optical network system. A service channel and at least two management channels are established between the first optical network device 100 and the second optical network device 200. The service channel and all management channels are bound to a transmission container, and at least two management channels are bound to the same transmission container. Therefore, integrating and binding multiple management channels to the same transmission container is equivalent to multiple management channels sharing part of the bandwidth, thereby releasing the bandwidth independently occupied by some channels, reducing bandwidth overhead, and improving the system bandwidth utilization.

It should be noted that uplink equipment can refer to devices used to send data from user-end devices to the network or server. Uplink equipment can receive data transmitted uplink from user-end devices and can also transmit network or server data downlink to downlink equipment. Downlink equipment, on the other hand, can refer to devices used to receive data from the network or server. Simultaneously, downlink equipment can transmit user-end data uplink to uplink equipment. Downlink equipment can refer to user-end devices. For example, in an FTTH system, uplink equipment can refer to an Optical Line Terminal (OLT), and downlink equipment can refer to an Optical Network Unit (ONU), i.e., the terminal equipment for fiber optic access. In an FTTR system, uplink equipment can refer to the Main FTTR Unit (MFU), and downlink equipment can refer to the Sub FTTR Unit (SFU).

In some embodiments, the optical network system may be a fiber-to-the-room network system, i.e., an FTTR system. Therefore, the first optical network device 100 may be the master fiber unit in the FTTR system, i.e., the FTTR master device MFU, and the second optical network device 200 may be the slave fiber unit in the FTTR system, i.e., the FTTR slave device SFU. The management channel established between the first optical network device 100 and the second optical network device 200 may refer to the FMCI channel and the WMCI channel.

In some embodiments, the optical network system may be a fiber-to-the-home (FTTH) system. Therefore, the first optical network device 100 may be an optical line terminal (OLT) in the FTTH system, and the second optical network device 200 may be an optical network unit (ONU) in the FTTH system. The management channel established between the first optical network device 100 and the second optical network device 200 may refer to the OMCI channel and the WMCI channel.

In some embodiments, the optical network system can be a network system combining a fiber-to-the-home network system and a fiber-to-the-room network system. In this case, the first optical network device 100 can be either a master fiber unit or an optical line terminal. In the optical access network system combining FTTR and FTTH, the master fiber unit can also serve as a downlink device for the optical line terminal. Therefore, the second optical network device 200 can be either a slave fiber unit or a master fiber unit.

It should be noted that there may be multiple second optical network devices 200, meaning that the first optical network device 100 can establish service channels and at least two management channels with multiple second optical network devices 200 respectively, and perform data interaction. As the number of second optical network devices 200 in the optical network system increases, the number of management channels established in the optical network system also increases, requiring more bandwidth resources to be allocated to these management channels, significantly reducing the system's bandwidth utilization. This embodiment of the application addresses this by binding multiple management channels together into the same transmission container within the management channels established between the first optical network device 100 and the second optical network devices 200. This allows multiple management channels to share a portion of the bandwidth resources, thereby saving and releasing some bandwidth resources that were previously independently occupied by the management channels. This allows for optimized allocation of these saved and released bandwidth resources, such as providing more bandwidth resources to busy service channels, thus improving the system's bandwidth utilization.

In some embodiments, a data transmission channel includes an uplink port and a downlink port. The uplink port is located in the downlink device, i.e., the second optical network device 200, and the downlink port is located in the uplink device, i.e., the first optical network device 100. The uplink port and the downlink port can be mapped to corresponding data transmission channels. Different uplink ports or different downlink ports correspond to different data transmission channels. The downlink device can transmit data to the corresponding data transmission channel through the uplink port to achieve uplink data transmission, while the uplink device can receive data transmitted by the downlink device through the downlink port corresponding to the same data transmission channel. Therefore, the first optical network device 100 may include a service uplink port for connecting service channels and multiple management uplink ports for connecting different management channels. Correspondingly, the second optical network device 200 may include a service downlink port for connecting service channels and multiple management downlink ports for connecting different management channels.

The Optical Line Terminal (OLT) establishes a data transmission channel (GPON Encapsulation Method Port, GEM Port) between the uplink and downlink devices by configuring the corresponding bandwidth authorization and parameters. Then, it associates and binds each data transmission channel GEM Port with the transmission container T-CONT. Thus, when the downlink device needs to transmit data uplink to the first optical network device 100, it can map the message data to be transmitted to the corresponding data transmission channel GEM Port. The corresponding data transmission channel GEM Port carries the message data and maps it to the bound transmission container T-CONT for uplink transmission. Thus, the first optical network device 100 can receive the uplink transmitted data through the downlink port of the data transmission channel. Specifically, the data transmission channel can be demodulated through the transmission container T-CONT, and then the message data in the data transmission channel can be demodulated. As shown in Figure 1, the first optical network device 100, acting as an uplink device in the optical access network system, can receive data transmitted by the downlink device, namely the second optical network device 200, through a service channel and at least two management channels. Each data transmission channel is bound to a transmission container T-CONT, and at least two management channels are bound to the same transmission container T-CONT. This is equivalent to at least two management channels having their management uplink ports bound to the same transmission container T-CONT, or at least two management channels having their management downlink ports bound to the same transmission container T-CONT. Therefore, at least two management channels share a portion of the bandwidth, thereby saving and releasing some of the bandwidth resources independently occupied by the management channels, reducing bandwidth resource overhead, and improving overall bandwidth utilization.

In some embodiments, two management channels and one service channel can be established between the first optical network device 100 and the second optical network device 200. The two management channels carry different data types. For example, the optical network system can be an FTTR system, the first optical network device 100 can be an uplink device (i.e., an FTTR master device) in the FTTR system, and the second optical network device 200 can be a downlink device (i.e., an FTTR slave device). Typically, three channels are established between the uplink and downlink devices in the FTTR system: a Fiber Management & Control Interface Port (FMCIPORT), a Wireless Management & Control Interface Port (WMIPORT), and a Wireless Management & Control Interface Port (WMIPORT). The optical network system can be an FTTH system, where the first optical network device 100 can be an uplink device (i.e., an optical line terminal OLT) in the FTTH system, and the second optical network device 200 can be a downlink device (i.e., an optical network unit ONU). In the FTTH system, three channels can also be established between the uplink device and the downlink device, namely the optical network unit management and control interface port (OMCIPORT), the WMCI channel, and the service channel.

Referring to Figure 2, which is a schematic diagram illustrating the effect of shared bandwidth resources for data transmission channels provided in this embodiment of the application, Figure 2(a) shows that in the FTTR system, the data transmission channels established between the optical network device (i.e., the FTTR master device) and the downlink device (i.e., the FTTR slave device) are each bound to a different transmission container. Specifically, the first management channel (i.e., FMCIPORT) is bound to the first transmission container T-CONT, the second management channel (i.e., WMCIPORT) is bound to the second transmission container T-CONT, and the service channel is bound to the third transmission container T-CONT. Specifically, the transmission container T-CONTs are divided into five types: fixed bandwidth, guaranteed bandwidth, burst allocation with minimum guaranteed bandwidth, best-effort allocation, and combined allocation. Each transmission container T-CONT has a corresponding specific Quality of Service (QoS) characteristic. Therefore, the optical line terminal (OLT) can dynamically allocate corresponding bandwidth resources according to the actual network traffic and the needs of each transmission container T-CONT. Under normal circumstances, the service channel needs to carry a larger amount of data transmission and requires more bandwidth resources. Therefore, the third transmission container T-CONT bound to the service channel is allocated more bandwidth resources. On the other hand, the two management channels carry a smaller amount of data transmission and require less bandwidth resources. Therefore, the transmission containers T-CONT bound to the two management channels are allocated less bandwidth resources. As shown in Figure 2(a), even though the bandwidth resources allocated to the first, second, and third transmission containers T-CONT can be dynamically adjusted in real time, and the bandwidth resources of the corresponding transmission containers T-CONT can be reduced when the management channel is idle, the first and second transmission containers T-CONT still need to occupy some bandwidth, so that the bandwidth resources corresponding to the management channel cannot be fully utilized. Moreover, when the splitting ratio is higher and the number of downlink devices is greater, the bandwidth resources occupied by the transmission containers corresponding to the management channel are also greater, which reduces the overall bandwidth utilization of the system.

As shown in Figure 2(b), in this embodiment of the application, in the FTTR, the two management channels in the data transmission channel established between the first optical network device 100 (i.e., the FTTR master device) and the second optical network device 200 (i.e., the FTTR slave device) are bound to the same transmission container. That is, the first management channel (i.e., FMCIPORT) and the second management channel (i.e., WMCIPORT) are both bound to the fourth transmission container T-CONT, while the service channel is bound to the fifth transmission container T-CONT. Therefore, the two management channels are bound to the same transmission container, which is equivalent to the bandwidth resource sharing scheme of the two management channels shown in Figure 2(a). Under the condition that the overall bandwidth resources of the system remain unchanged, compared with each management channel being bound to different transmission containers and independently occupying the corresponding bandwidth resources, this embodiment of the application can save and release the bandwidth resources independently occupied by the two management channels, thereby reducing the bandwidth resource overhead and improving the overall bandwidth utilization of the system.

In some embodiments, when multiple management channels are bound to the same transmission container, the message priorities corresponding to each management channel within the same transmission container may be the same or different. For example, as shown in Figure 2(b), when the FMCI channel and the WMCI channel are bound to the fourth transmission container, the message priority of the FMCI message corresponding to the FMCI channel may be the same as the message priority of the WMCI message corresponding to the WMCI channel. That is, when it is necessary to transmit FMCI messages and WMCI messages uplink, message scheduling can be performed through QoS to prioritize the transmission of messages with earlier times; or the message priority of the FMCI message corresponding to the FMCI channel may be higher than the message priority of the WMCI message corresponding to the WMCI channel; or the message priority of the FMCI message corresponding to the FMCI channel may be lower than the message priority of the WMCI message corresponding to the WMCI channel.

In some embodiments, referring to Figure 3, which is a schematic diagram of shared bandwidth resources for data transmission channels provided in another embodiment of this application, the service channel and all management channels can be bound to the same transmission container. This is equivalent to the service uplink port and all management uplink ports being bound to the same transmission container, or the service downlink port and all management downlink ports being bound to the same transmission container. In this case, all management channels and service channels share bandwidth resources, thus fully utilizing the bandwidth resources of the management channels when they are idle. This is especially beneficial when the splitting ratio is large and the number of downlink devices is large, effectively improving the overall system bandwidth utilization. At this time, the optical line terminal (OLT) can increase the bandwidth allocation frequency to each transmission container (T-CONT), adjusting the bandwidth allocation multiple times within a 125-microsecond allocation cycle, thereby enabling timely adjustment of the bandwidth allocation of each downlink device and fully utilizing the overall system bandwidth resources.

In some embodiments, when a service channel and multiple management channels are bound together in the same transport container, the message priority of the service message corresponding to the service channel is lower than the message priority of the management message corresponding to each management channel in the same transport container, while the message priorities of the messages corresponding to each management channel may be the same or different.

In some embodiments, referring to Figure 4, which is a schematic diagram of shared bandwidth resources for data transmission channels provided in another embodiment of this application, multiple management channels established by the first optical network device 100 and the second optical network device 200 can be merged to form a shared management channel. This shared management channel can be independently bound to a transmission container. During the merging process of multiple management channels, the management uplink ports of these management channels are also merged to form the uplink ports of the management channel, and similarly, the management downlink ports of these management channels are also merged to form the downlink ports of the management channel. As shown in Figure 4, in the FTTR system, the FMCI channel and WMCI channel established between the optical network device and the downlink device can be merged to form an FMCI/WMCI channel, i.e., a shared management channel. This shared management channel is independently bound to the sixth transmission container T-CONT, while the service channel is independently bound to the seventh transmission container T-CONT. Therefore, by merging multiple management channels to achieve shared bandwidth resources, the bandwidth resources independently occupied by multiple management channels are saved and released, thereby reducing bandwidth resource overhead and improving the overall bandwidth utilization of the system.

In some embodiments, referring to Figure 5, which is a schematic diagram of shared bandwidth resources for data transmission channels provided in another embodiment of this application, a shared management channel formed by merging multiple management channels established by the first optical network device 100 and the second optical network device 200 can be bound to the same transmission container as the service channels. This is equivalent to the uplink port of the shared management channel being bound to the service uplink port of the service channel, or the downlink port of the shared management channel being bound to the service downlink port of the service channel. As shown in Figure 5, in the FTTR system, the FMCI/WMCI shared management channel formed by merging the FMCI channel and the WMCI channel is bound to the eighth transmission container T-CONT along with the service channels. In this case, all management channels and service channels share bandwidth resources, thus enabling full utilization of the management channel's bandwidth resources when the management channel is idle. This is especially beneficial when the splitting ratio is large and the number of downlink devices is large, effectively improving the overall system bandwidth utilization. At this time, the optical line terminal (OLT) can increase the bandwidth allocation frequency for each transmission container (T-CONT) and adjust the bandwidth allocation multiple times within a 125-microsecond allocation cycle, thereby enabling timely adjustment of the bandwidth allocation for each downlink device and making full use of the overall system bandwidth resources.

In some embodiments, after the management channels established by the first optical network device 100 and the second optical network device 200 are merged to form a shared management channel, independent management channels can still be established between the first optical network device 100 and the second optical network device 200. These independent management channels can be bound to different transmission containers, or they can be bound to the same transmission container, or they can be bound to the same transmission container as the shared management channel, or they can be bound to the same transmission container as the service channel.

In some embodiments, when a service channel and a shared management channel formed by merging multiple management channels are both bound to the same transport container, the message priority of the service message corresponding to the service channel is lower than the message priority of the management message corresponding to the shared management channel.

In some embodiments, the first optical network device 100, acting as an uplink device in an optical access network system, can broadcast data downlink to each downlink device, namely the second optical network device 200, through the data transmission channel connected to its downlink port. However, the downlink data broadcast adopts a first-in, first-out (FIFO) approach, which means that once a data packet begins transmission, it cannot be interrupted. If an urgent data packet is sent after a regular data packet, it will be delayed. The specific delay time depends on the size of the regular data packet being transmitted. For example, if the regular data packet is a giant Ethernet frame with a payload of up to 9000 bytes, then for a 10GB FTTR system, the urgent data packet will introduce a maximum delay of 8.2 microseconds. Therefore, the first optical network device 100 may include a message slicing unit and a message sorting unit. The message slicing unit can slice and encapsulate message data with large payloads into multiple message fragments with smaller payloads, and then transmit them downlink. This can shorten the transmission time occupied by a single message fragment, thereby reducing the waiting time for emergency data packets and effectively reducing the transmission latency of emergency messages. The message sorting unit can identify the urgency level of each data packet, i.e., the transmission priority, and sort the data packets according to the transmission priority of each data packet, and transmit them downlink in sequence. This can achieve priority transmission of emergency messages and reduce the transmission latency of emergency messages. For example, if there are no urgent messages in the data packets to be transmitted, the giant Ethernet frame to be transmitted can be broadcast downlink to each downlink device according to the transmission priority. Before broadcasting the giant Ethernet frame downlink, the packet slicing unit in the first optical network device 100 can be called to slice and encapsulate the giant Ethernet frame into multiple small-load packet fragments, and then these small-load packet fragments are broadcast downlink in sequence. When one of the packet fragments is being transmitted downlink, an urgent data packet that needs to be broadcast downlink is received. The packet sorting unit can adjust the transmission priority of the urgent data packet to the highest, which is equivalent to arranging the subsequent packet fragments to be transmitted after the urgent data packet is transmitted. Therefore, the urgent data packet can be transmitted downlink first after the currently downlinking packet fragment has finished transmitting. Since the effective payload of the packet fragment is reduced after slicing and encapsulation, the data transmission volume is small, so the transmission time occupied by the packet fragment is short. Compared with the scheme of transmitting the complete giant Ethernet frame and then transmitting the urgent data packet, it can effectively reduce the transmission delay of the urgent data packet.

Based on the structure of the optical network system proposed in the first aspect embodiment, various embodiments of the message scheduling method of the fourth aspect embodiment of this application are proposed.

Referring to Figure 6, which shows a flowchart of a packet scheduling method provided in an embodiment of this application, the packet scheduling method can be applied to the first optical network device 100 of the optical network system proposed in the first aspect embodiment. The packet scheduling method includes, but is not limited to, the following steps:

Step S100: Obtain the message to be transmitted and identify the message to be transmitted;

Step S200: When the message to be transmitted is an urgent message, the message to be transmitted is assigned to the first queue; when the message to be transmitted is a non-urgent message, the message to be transmitted is sliced and encapsulated to obtain multiple message fragments, and the multiple message fragments are assigned to the second queue.

Step S300: Transmit messages in each queue based on transmission priority.

A message to be transmitted refers to a data packet sent by a server in response to a request from a user device (i.e., a downlink device) in network communication. Upon receiving the message, the user device can perform corresponding processing to complete the requested operation. When a message to be transmitted downlink is obtained, its urgency (transmission priority) can be identified. Specifically, this can be done by checking flag bits in the message segment. If the flag bits meet the criteria for an urgent message (e.g., the flag bit is set to 1), the message to be transmitted is considered urgent; otherwise, it is considered non-urgent.

When the message to be transmitted is an urgent message, it can be assigned to the first queue. When the message to be transmitted is a non-urgent message, it can be assigned to the second queue. The transmission priority of the first queue is higher than that of the second queue. Downlink transmission of message data is based on transmission priority. Therefore, message data in the first queue will be transmitted downlink with priority over message data in the second queue. Message data in the same queue are sorted according to the time they entered the queue, or they can be further sorted according to their urgency. This enables priority transmission of urgent messages and reduces the transmission delay of urgent messages. Therefore, when there is no message data in the first queue, the message data in the second queue can be transmitted downlink.

In addition, during the process of allocating non-urgent messages to the second queue, the non-urgent messages can be sliced and encapsulated to obtain multiple message fragments, and then these multiple message fragments can be allocated to the second queue. When allocating multiple message fragments to the second queue, they can be sorted based on the content order of the multiple message fragments.

Referring to Figure 7, which is a schematic diagram of message scheduling provided in an embodiment of this application, the message data to be broadcast downlinked at the first moment includes a first message XFEM frame to be transmitted with Port-ID X and a second message XFEM frame to be transmitted with Port-ID Y. That is, the first message to be transmitted needs to be transmitted through the data transmission channel with Port-ID X, while the second message XFEM frame to be transmitted needs to be transmitted through the data transmission channel with Port-ID Y. The payload of the first message to be transmitted is an Emergency Application Protocol Data Unit (APDU), i.e., APDU N, while the payload of the second message to be transmitted is a Non-Emergency Application Protocol Data Unit (MPU), i.e., a Normal APDU M. By identifying the first and second messages to be transmitted, it is determined that the first message to be transmitted is an urgent message and the second message to be transmitted is a non-urgent message. Therefore, the first message to be transmitted is assigned to the first queue (high priority queue) and the second message to be transmitted is assigned to the second queue (low priority queue). Based on the transmission priority, the messages in each queue are broadcast downlink. Therefore, the first message APDU N in the first queue is transmitted first. At the same time, the second message APDU M is sliced and the sliced segments are encapsulated into XFEM frames to form the second message segment APDU M1 and the second message segment APDU M2. If no urgent message is obtained during subsequent transmission, the second message segment APDU M1 and the second message segment APDU M2 are transmitted sequentially after the first message APDU N is transmitted.

After the first transmission message APDU N is transmitted, the second transmission message segment APDU M1 is broadcast downlink. During the downlink broadcast transmission of the second transmission message segment APDU M1, a third transmission message XFEM frame with Port-ID X is acquired. The payload of the third transmission message is urgent APDU N+1. Therefore, the third transmission message APDU N+1 is an urgent message and is allocated to the first queue. Since downlink transmission is first-in-first-out, the second transmission message segment APDU M1 cannot be interrupted. Therefore, the third transmission message APDU N+1 will be transmitted in the second queue. After the downlink transmission of message segment APDU M1 is completed, it is transmitted first. That is, the third transmission message APDU N+1 is transmitted later than the second transmission message segment APDU M1, but the third transmission message APDU N+1 is transmitted before the second transmission message segment APDU M2. By slicing and encapsulating non-urgent messages before downlink transmission, the transmission time of a single message can be effectively shortened. At the same time, it can enable urgent messages (the third transmission message APDU N+1) to "jump the queue" in the transmission of non-urgent messages (the second transmission message APDU M), effectively reducing the optical path transmission delay of urgent messages.

Additionally, referring to FIG8, in one embodiment, step S200 in the embodiment shown in FIG6 further includes, but is not limited to, the following steps:

Step S210: When the message to be transmitted is a non-urgent message, if the payload of the message to be transmitted is greater than a preset byte threshold, the message to be transmitted is sliced and encapsulated to obtain multiple message fragments, and the multiple message fragments are allocated to the second queue.

If the message to be transmitted is determined to be non-urgent, it can be sliced according to a preset byte threshold, forming segments of the same length as the preset byte threshold. These segments are then encapsulated to obtain multiple message fragments. Therefore, when the payload of the message to be transmitted exceeds the preset byte threshold, the message can be sliced and encapsulated to form multiple message fragments. The preset byte threshold can be adjusted based on the bandwidth resources of the optical access network system.

It should be noted that if the payload of the resulting segmented message is still greater than the preset byte threshold, the segmented message can be further sliced and encapsulated until the payload of each segment is less than or equal to the preset byte threshold. By slicing and encapsulating non-urgent messages before transmission, the transmission time of non-urgent messages can be effectively shortened, facilitating the timely transmission of urgent messages and reducing transmission latency.

Additionally, referring to FIG9, in one embodiment, prior to step S300 in the embodiment shown in FIG6, there are, but are not limited to, the following steps:

Step S220: When the message to be transmitted is a non-urgent message and the payload of the message to be transmitted is less than or equal to a preset byte threshold, the message to be transmitted is allocated to the second queue.

If the message to be transmitted is determined to be non-urgent, and the payload of the message to be transmitted is less than or equal to a preset byte threshold, it can be assumed that the downlink transmission time of the message to be transmitted is short. Therefore, if an urgent message is obtained while the message to be transmitted is being transmitted downlink, the transmission of the message to be transmitted can be completed quickly and the downlink transmission of the urgent message can be carried out. The impact on the transmission delay of the urgent message is small, so there is no need to slice and encapsulate the message to be transmitted. The message to be transmitted can be directly allocated to the second queue, and then the messages in each queue can be transmitted based on the transmission priority.

In addition, in a fourth aspect, referring to FIG10, an embodiment of this application also provides a communication device 1000, FIG10 showing a schematic structural diagram of the communication device 1000 provided in an embodiment of this application. The communication device 1000 includes: at least one memory 1010, at least one processor 1020, and a program stored in the memory 1010 and executable on the processor 1020.

The processor 1020 and the memory 1010 can be connected via a bus or other means.

The non-transient software program and instructions required to implement the message scheduling method of the above embodiments are stored in the memory 1010. When executed by the processor 1020, the message scheduling method in the above embodiments is executed, for example, the method steps S100 to S300 in FIG6, the method step S210 in FIG8, and the method step S220 in FIG9 described above are executed.

The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.

Furthermore, one embodiment of this application also provides a computer-readable storage medium storing computer-executable instructions that are executed by a processor or controller, for example, by a processor in the above embodiments, causing the processor to perform the message scheduling method in the above embodiments, for example, performing method steps S100 to S300 in FIG6, method step S210 in FIG8, and method step S220 in FIG9.

This application provides an optical network system, a packet scheduling method, a communication device, and a readable storage medium. Since the uplink data volume and transmission period of management channel packets are small, multiple management channels are integrated and bound to the same transmission container. This is equivalent to multiple management channels sharing a portion of the bandwidth, thereby releasing bandwidth independently occupied by some channels, reducing bandwidth overhead, and improving system bandwidth utilization. Furthermore, during downlink packet transmission, downlink packets are transmitted sequentially based on transmission priority. Downlink packets can also be sliced and encapsulated to shorten the downlink packet transmission time. This not only enables priority transmission of urgent packets but also effectively reduces the transmission latency of urgent packets. Therefore, even in scenarios with high bandwidth requirements, it can effectively reduce latency and improve the user experience.

It will be understood by those skilled in the art that all or some of the steps and systems in the methods disclosed above can be implemented as software, firmware, hardware, and suitable combinations thereof. Some or all of the physical components can be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit. Such software can be distributed on a computer-readable medium, which can include computer storage media (or non-transitory media) and communication media (or transient media). As is known to those skilled in the art, the term computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disc (DVD) or other optical disc storage, magnetic cartridges, magnetic tape, disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and is accessible to a computer. Furthermore, as is known to those skilled in the art, communication media typically contain computer-readable instructions, data structures, program modules, or other data in modulated data signals such as carrier waves or other transmission mechanisms, and may include any information delivery medium.

Claims (14)

An optical network system, comprising: First optical network equipment; The second optical network device transmits uplink messages to the first optical network device through a service channel and at least two management channels. The service channel and all the management channels are bound to a transmission container, and at least two of the management channels are bound to the same transmission container. According to claim 1, in the optical network system, the service channel and all the management channels are bound to the same transmission container. According to the optical network system of claim 1, at least two management channels are merged into a shared management channel, and the shared management channel is bound to the transmission container. According to claim 3, in the optical network system, the service channel and the management shared channel are both bound to the same transmission container. In the optical network system according to claim 1 or 3, the service channel is independently bound to one of the transmission containers. According to the optical network system of claim 2 or 4, in the same transmission container, the message priority corresponding to each management channel is higher than the message priority corresponding to the service channel. The optical network system according to any one of claims 1 to 4, wherein, in the same transmission container, the message priorities corresponding to each of the management channels are the same or different. According to claim 1, the optical network system wherein the first optical network device is the master fiber unit in the fiber-to-the-room network system, and the second optical network device is the slave fiber unit in the fiber-to-the-room network system. According to claim 1, the optical network system wherein the first optical network device is an optical line terminal in a fiber-to-the-home network system, and the second optical network device is an optical network unit in the fiber-to-the-home network system. A packet scheduling method, applied to the first optical network device in an optical network system as described in any one of claims 1 to 9, the packet scheduling method comprising: Obtain the message to be transmitted and identify the message to be transmitted; When the message to be transmitted is an urgent message, the message to be transmitted is assigned to the first queue; when the message to be transmitted is a non-urgent message, the message to be transmitted is sliced and encapsulated to obtain multiple message fragments, and the multiple message fragments are assigned to the second queue. Messages in each queue are transmitted based on transmission priority, wherein the transmission priority of the first queue is higher than that of the second queue. According to the message scheduling method of claim 10, the step of slicing and encapsulating the message to be transmitted to obtain multiple message fragments includes: If the payload of the message to be transmitted is greater than a preset byte threshold, the message to be transmitted is sliced and encapsulated to obtain multiple message fragments. The message scheduling method according to claim 10 further includes: When the message to be transmitted is a non-urgent message and the payload of the message to be transmitted is less than or equal to a preset byte threshold, the message to be transmitted is allocated to the second queue. A communication device, comprising: At least one processor; At least one memory for storing at least one program; wherein, The message scheduling method as described in any one of claims 10 to 12 is implemented when at least one of the programs is executed by at least one of the processors. A computer-readable storage medium storing computer-executable instructions, wherein the computer-executable instructions are configured to perform the message scheduling method as described in any one of claims 10 to 12.