Signal sending method, signal receiving method, device and storage medium

Abstract

Embodiments of the present application provide a signal sending method, a signal receiving method, a device and a storage medium, wherein the sending method comprises: splitting A first sub-member signals and a second sub-member signal from an original customer signal; mapping each first sub-member signal to a corresponding first FlexO instance, each first FlexO instance carrying one first sub-member signal of one original customer signal; mapping the second sub-member signal to a corresponding second FlexO instance, each second FlexO instance carrying multiple second sub-member signals from different original customer signals; and sending the first FlexO instance and the second FlexO instance. The above scheme can reduce the bandwidth waste of the FlexO instance, improve the carrying efficiency of the FlexO instance, and is suitable for ODU4, ODUCn and other customer service carrying scenarios.

Description

Technical Field

[0001] The embodiments of this application relate to, but are not limited to, the field of communication technology, and in particular to a signal transmission method, a signal reception method, an electronic device, a computer-readable storage medium, and a computer program product. Background Technology

[0002] Optical Transport Networks (OTNs) carry customer services at different rates by defining different levels of Optical Channel Data Unit (ODU) containers, such as ODUk (k=0,1,2,3,4, etc.) and ODUUCn. Flex Optical Transport Network (FlexO) instances are a flexible optical transport architecture where ODU containers can be mapped to their sub-time slots, thus enabling the carrying of services at different rates. In the newly defined standard, the planned rate for each FlexO instance member is 100 Gbit / s. However, the rate of ODU4 is 104.794 Gbit / s, and the rate of ODUUCn is 105.2 Gbit / s. This means that one FlexO instance member cannot meet the rate requirements of one ODU4 / ODUCn customer service. In related technologies, using two FlexO instance members to carry one ODU4 / ODUCn customer service results in bandwidth waste. Therefore, how to efficiently carry ODU4 and ODUUCn customer services per FlexO instance member is a current research direction. Summary of the Invention

[0003] This application provides a signal transmission method, a signal reception method, an electronic device, a computer-readable storage medium, and a computer program product, aiming to enable FlexO instance members to more efficiently carry customer services.

[0004] In a first aspect, embodiments of this application provide a signal transmission method, the transmission method comprising: From the original client signal, A first sub-member signals and one second sub-member signal are extracted, where A is a positive integer; Each of the first sub-member signals is mapped to a corresponding first FlexO instance, and each first FlexO instance carries one of the first sub-member signals of the original client signal. The second sub-member signal is mapped to a corresponding second FlexO instance, and each second FlexO instance carries multiple second sub-member signals from different original client signals; Send the first FlexO instance and the second FlexO instance.

[0005] In the above scheme, the FlexO instance members include two types: a first FlexO instance and a second FlexO instance. The first FlexO instance is configured to support carrying one first sub-member signal, and the second FlexO instance is configured to support carrying multiple second sub-member signals from different original customer signals. To achieve efficient customer service carrying by FlexO instance members, the above scheme splits the original customer signal into A first sub-member signals and one second sub-member signal. In practical scenarios, the first sub-member signal can be configured with a rate close to that of the first FlexO instance, so that one first FlexO instance can exactly carry one first sub-member signal. The second sub-member signal can be considered as the remaining traffic after subtracting A first sub-member signals from the original customer signal. By centrally carrying the second sub-member signals of multiple original customer signals through one second FlexO instance, bandwidth waste of FlexO instances can be reduced, and carrying efficiency of FlexO instances can be improved. The above scheme is applicable to customer service carrying scenarios such as ODU4 and ODUCn, avoiding the bandwidth waste problem that exists when using related technologies to carry customer services such as ODU4 and ODUCn.

[0006] Secondly, embodiments of this application provide a signal receiving method, the receiving method comprising: Receive at least one first FlexO instance and at least one second FlexO instance, each first FlexO instance carrying a first sub-member signal of an original client signal, and each second FlexO instance carrying a second sub-member signal of the original client signal; Extract the first sub-member signal from the first FlexO instance, and extract the second sub-member signal from the second FlexO instance; The target original customer signal is obtained by merging A first sub-member signals and one second sub-member signal that belong to the target original customer signal, where A is a positive integer.

[0007] In the above scheme, the members of the FlexO instance include two types: a first FlexO instance and a second FlexO instance. The first FlexO instance is configured to support carrying a first sub-member signal, and the second FlexO instance is configured to support carrying a second sub-member signal. The A first sub-member signals and one second sub-member signal obtained from the splitting of the target original client signal are carried by n first FlexO instances and one second FlexO instance. After receiving the first and second FlexO instances, the first sub-member signals are extracted from the first FlexO instances, and the second sub-member signals are extracted from the second FlexO instances. By merging the A first sub-member signals and one second sub-member signal belonging to the target original client signal, the target original client signal can be recovered.

[0008] Thirdly, embodiments of this application also provide an electronic device, including: at least one processor; at least one memory for storing at least one program; at least one program is executed by at least one processor to perform the information sending method described in the first aspect or the information receiving method described in the second aspect.

[0009] Fourthly, embodiments of this application also provide a computer-readable storage medium storing computer-executable instructions, which are used to execute the information sending method described in the first aspect or the information receiving method described in the second aspect.

[0010] Fifthly, embodiments of this application also provide a computer program product, including a computer program or computer instructions, wherein the computer program or computer instructions are stored in a computer-readable storage medium, a processor of an electronic device reads the computer program or computer instructions from the computer-readable storage medium, and the processor executes the computer program or computer instructions, causing the electronic device to perform the information sending method described in the first aspect or the information receiving method described in the second aspect.

[0011] For a description of the beneficial effects of any of the third to fifth aspects, please refer to the description of the beneficial effects of the first to second aspects, which will not be repeated here.

[0012] It should be understood that the above general description and the following detailed description are merely exemplary and do not limit this application. Attached Figure Description

[0013] Figure 1 A schematic diagram of the OTN frame structure provided for related technologies; Figure 2 A schematic diagram illustrating how customer business is mapped to multiple FlexOinstances for transmission, provided for related technologies; Figure 3 A schematic flowchart illustrating a signal transmission method provided in an embodiment of this application; Figure 4 A schematic diagram of a first encapsulation format for a first encapsulation frame provided in an embodiment of this application; Figure 5 A schematic diagram of a second encapsulation format for a first encapsulation frame provided in an embodiment of this application; Figure 6 A schematic diagram of a third encapsulation format for a first encapsulation frame provided in an embodiment of this application; Figure 7 A schematic diagram illustrating various overhead formats of a packaged frame using actual encapsulation, provided for embodiments of this application; Figure 8 A schematic diagram illustrating the process of splitting the original customer signal provided in this application embodiment; Figure 9 A schematic diagram illustrating the splitting process of an ODU4 signal provided in an embodiment of this application; Figure 10 A schematic diagram illustrating a process for mapping raw customer signals to a FlexO instance, provided in an embodiment of this application; Figure 11 This application provides another schematic diagram illustrating the process of mapping raw customer signals to FlexO instances in an embodiment of the present application. Figure 12 A schematic diagram of the time slot allocation for ODU4 provided for related technologies; Figure 13 A schematic diagram illustrating the splitting of an original customer signal provided in an embodiment of this application; Figure 14 A schematic diagram illustrating the splitting of another original customer signal provided in an embodiment of this application; Figure 15 A schematic diagram of the encapsulation of the second sub-member signal provided in an embodiment of this application; Figure 16 A schematic diagram of a FlexO instance provided in an embodiment of this application; Figure 17 This application provides a schematic diagram illustrating a process for mapping an ODUcn signal to a FlexO instance. Figure 18 This application provides another schematic diagram illustrating the process of mapping an ODUcn signal to a FlexO instance. Figure 19 A schematic flowchart illustrating a signal receiving method provided in an embodiment of this application; Figure 20 This application provides a schematic diagram of a process for restoring the original customer signal. Figure 21 This is a schematic diagram of an electronic device provided in an embodiment of this application. Detailed Implementation

[0014] To make the objectives, technical methods, 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.

[0015] It should be noted that although the flowchart shows a logical order, in some cases, the steps shown or described may be performed in a different order than that shown in the flowchart. In the description of the specification, claims, and the foregoing drawings, "at least one" means one or more; "more than" means two or more; "greater than," "less than," and "exceeding" are understood to exclude the stated number; "above," "below," and "within" are understood to include the stated number. The use of terms such as "first," "second," etc., is merely for distinguishing technical features and should not be construed as indicating or implying relative importance, or implicitly specifying the number of indicated technical features, or implicitly indicating the order of the indicated technical features.

[0016] In this embodiment, "and / or" describes the relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent the existence of A alone, the simultaneous existence of A and B, or the existence of B alone. A and B can be singular or plural. The character " / " generally indicates that the preceding and following associated objects are in an "or" relationship. "At least one of the following" and similar expressions refer to any combination of these items, including any combination of singular or plural items. For example, at least one of a, b, and c can represent: the existence of a alone, the existence of b alone, the existence of c alone, the simultaneous existence of a and b, the simultaneous existence of a and c, the simultaneous existence of b and c, or the simultaneous existence of a, b, and c, where a, b, and c can be single or multiple.

[0017] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of the terms "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0018] Communication networks are the highways of the information age. In the past, communication primarily consisted of voice services, and communication networks employing Synchronous Digital Hierarchy (SDH) and OTN technologies effectively met the needs of voice transmission. OTN networks carry customer services at different rates through defined containers such as ODU0, ODU1, ODU2, ODU3, ODU4, and ODUCn. Specifically, ODU4 has a rate of 104.794 Gbit / s, and ODUCn has a rate of n × 105.2 Gbit / s.

[0019] Currently, OTN communication equipment is based on the G.709 protocol standard. The process of OTN transmitting customer services is as follows: the customer signal is first mapped to the Optical Payload Unit (OPU), then the OPU is mapped to the ODU, and finally the ODU is mapped to the OTN frame for transmission. Please refer to [link to OTN frame]. Figure 1 A schematic diagram of the OTN frame structure provided for related technologies, such as Figure 1 As shown, the OTN frame structure is based on fixed-length frames, each consisting of 4 rows × 3824 columns of bytes. The first 16 columns of the OTN frame constitute the overhead (OH) region, including the frame alignment field (alignm), the Optical Transport Unit (OTU) overhead field (OTU OH), the ODU overhead field (ODU OH), and the OPU overhead field (OPU OH). Columns 17-3824 (a total of 3807 columns) constitute the payload region, where customer services are carried. It should be understood that the frame structures of ODU4 and ODUCn mentioned in the embodiments of this application can be referred to. Figure 1 The structure shown.

[0020] It should be understood that the `alignm` field is used for frame header positioning, including the Frame Alignment Signal (FAS) field and the Multiframe Alignment Signal (MFAS) field. The FAS field consists of 6 bytes, with the content being 6 bytes of hexadecimal data. The first 3 bytes are F6, and the last 3 bytes are 28, i.e., the 6 bytes are F6F6F6282828. The FAS field is used to identify the start position of the OTN frame, ensuring that the receiver can correctly identify the frame boundaries. The MFAS field is used for multiframe indication, indicating the sequential number of each frame in a multiframe. The MFAS field is one byte long and can represent data values ​​between 0 and 255, therefore a multiframe can consist of a maximum of 256 frames. In a multiframe, the MFAS field content of the first frame is 00, and the MFAS field content of subsequent frames increases sequentially, such as 00, 01, 02, 03...254, 255.

[0021] Figure 1 It also shows the specific fields included in the first 14 columns of the OTN overhead bytes, such as... Figure 1 As shown, the overhead area of ​​OTN contains some reserved (RES) fields whose specific uses have not yet been defined. The RES fields are usually set to 0 by default.

[0022] It should be understood that the FlexO standard defines a logical layer that carries customer business logic, composed of multiple instance members. Please refer to [link / reference]. Figure 2 This is a diagram illustrating how customer business processes are mapped to multiple FlexOinstances for transmission, providing insights into related technologies. For example... Figure 2As shown, n instance members constitute the FlexO transport layer. The frame structure of each instance member is 128 (rows) * 5140 bits (5440 bits if a Forward Error Correction (FEC) field is included). In the instance member frame structure, the frame header (the first row, the first 1280 bits) is the overhead field, which has a positioning function. The remaining part of the instance member frame structure, excluding the overhead, is the frame payload area, used to carry customer services. In relevant standards, FlexO-1 is defined as consisting of 1 instance, FlexO-2 as 2 instances, FlexO-4 as 4 instances, and FlexO-8 as 8 instances. From FlexO-1 to FlexO-8, the rate of one instance is slightly greater than 105 Gbps (in bits per second). Each instance can carry exactly one ODU4 or one ODUCN member. Thus, FlexO-8 (and similarly FlexO-2, FlexO-4, etc.) can perfectly carry 8 ODU4 or 8 ODUCN members. Figure 2 In the ODU4 customer service, each ODU4 member can choose one instance to transmit; for the ODU4 customer service, each member can choose one instance to transmit.

[0023] In the current research on the FlexO-16 standard, many vendors recommend reducing the instance rate to around 100G (i.e., the rate for carrying customer services is 100G). This means the FlexO-16 standard's rate is 16 * 100G, not 16 * 105G. This reduces the total bandwidth by 16 * 5G = 90G, allowing for transmission over longer distances. When the instance rate is reduced in the FlexO-16 standard, each instance carries a customer service rate of 100G. Each instance cannot carry one ODU4 (104.794G) customer service or one ODUCN (105.2G) member. Using two instances to carry one ODU4 or one ODUCN member results in significant bandwidth waste.

[0024] To address the aforementioned issues, this application provides a signal transmission method, a signal reception method, an electronic device, a computer-readable storage medium, and a computer program product, aiming to enable FlexO instance members to more efficiently support customer services.

[0025] Please see Figure 3This is a flowchart illustrating a signal transmission method provided in an embodiment of this application. It can be understood that... Figure 3 The signal transmission method shown is applied at the transmitting end. For example... Figure 3 As shown, the method includes steps S101-S104, which are described in detail below.

[0026] Step S101: Split the original customer signal into A first sub-member signals and one second sub-member signal, where A is a positive integer.

[0027] Step S102: Map each first sub-member signal to the corresponding first FlexO instance, with each first FlexO instance carrying a first sub-member signal of an original client signal; Step S103: Map the second sub-member signal to the corresponding second FlexO instance, where each second FlexO instance carries multiple second sub-member signals from different original client signals; Step S104: Send the first FlexO instance and the second FlexO instance.

[0028] It should be noted that the original client signal in the embodiments of this application can be an OTN frame signal, such as an ODU4 frame signal or an ODUCN frame signal.

[0029] In one possible implementation, the original client signal has a rate of S1 (first rate). The second FlexO instance and the first FlexO instance both have a rate of S2 (second rate), with S1 being greater than S2. The original client signal is split into A (A≥1) first sub-member signals and one second sub-member signal. The rate of each first sub-member signal is close to, but slightly less than, the rate of the first FlexO instance. Thus, one first FlexO instance can carry exactly one first sub-member signal. The second sub-member signal is the fractional portion remaining after subtracting A first sub-member signals from the original client signal; therefore, it can also be called a fractional sub-member signal. The second sub-member signal is carried by the second FlexO instance. It should be understood that one second FlexO instance can carry multiple second sub-member signals split from the original client signal to avoid bandwidth waste and improve service carrying efficiency.

[0030] In one possible implementation, A is equal to the integer part obtained by dividing the first rate S1 and the second rate S2. For example, if the rate of the original client signal is 105G (i.e., the first rate S1 is 105G) and the rate of the FlexO instance is 100G (i.e., the second rate S2 is 100G), then the original client signal can be split into a first sub-member signal with a rate of 100G and a second sub-member signal with a rate of 5G. The 100G first sub-member signal is mapped to one FlexO instance (first FlexO instance), and the 5G second sub-member signal is mapped to another FlexO instance (second FlexO instance). The remaining bearer space of the second FlexO instance can be used to carry the second sub-member signals split from other original client signals. For example, if the rate of the original client signal is 210G (i.e., the first rate S1 is 210G) and the rate of the FlexO instance is 100G (i.e., the second rate S2 is 100G), then the original client signal can be split into two first sub-member signals with a rate of 100G and one second sub-member signal with a rate of 10G. The two 100G first sub-member signals are mapped to two first FlexO instances, and the 10G second sub-member signal is mapped to one second FlexO instance. The remaining bearer space of the second FlexO instance can be used to carry other second sub-member signals split from the original client signal.

[0031] In one possible implementation, the payload of a second FlexO instance is divided into multiple sub-time slots, and a second sub-member signal is mapped to one or more sub-time slots of the second FlexO instance. For example, if the payload of the second FlexO instance is divided into 20 sub-time slots, each sub-time slot can carry 5G services, assuming the current rate of the second sub-member signal is 5G, then the current second sub-member signal is mapped to one sub-time slot of the second FlexO instance; assuming the current rate of the second sub-member signal is 10G, then the current second sub-member signal is mapped to two sub-time slots of the second FlexO instance.

[0032] In one possible implementation, mapping each first sub-member signal to a corresponding first FlexO instance specifically includes: mapping each first sub-member signal to a corresponding first encapsulation frame, and adding encapsulation attribute information of the first sub-member signal at a preset position in the first encapsulation frame; and mapping each first encapsulation frame to a corresponding first FlexO instance.

[0033] For example, the first encapsulation frame of this application embodiment may have multiple encapsulation formats, and each encapsulation format will be described below.

[0034] Please see Figure 4 This is a schematic diagram of a first encapsulation format for a first encapsulation frame provided in an embodiment of this application. Figure 4As shown, the first encapsulation frame adopts a real encapsulation form, including overhead and a first sub-member signal, wherein the first sub-member signal carries the original overhead in the original client signal.

[0035] Figure 4 In the example, the overhead in the first encapsulation frame carries encapsulation attribute information, which may include at least one of the following: Frame information (FAS) is used to indicate the start position of the first encapsulation frame, so that the receiver can determine the boundary of the first encapsulation frame by detecting the frame information, and determine the start position of the current first sub-member signal according to the predefined encapsulation format of the first encapsulation frame. Frame sequence information (MFAS / SN) is used to indicate the sequential position of the original customer signal to which the current first sub-member signal belongs. It should be understood that a customer service can be carried by multiple customer signal frames. The aforementioned original customer signal belongs to one of the customer signal frames of the current customer service. By carrying the frame sequence information corresponding to the current first sub-member signal in the first encapsulation frame, the receiving end can easily determine which customer signal frame the current first sub-member signal belongs to, and thus recover each customer signal frame (original customer signal) of the current customer service. The total number of sub-members information is used to indicate the total number of first and second sub-member signals contained in the original client signal to which the current sub-member signal belongs; The sub-member number information is used to indicate the number of the current first sub-member signal. It should be understood that an original client signal is divided into multiple sub-members (including at least one first sub-member and one second sub-member), and each sub-member has a corresponding number. By carrying the sub-member number information corresponding to the current first sub-member signal in the first encapsulation frame, the receiving end can easily determine the sequential position of the current first sub-member signal and thus recover the original client signal. Sub-member type information is used to indicate the type of the current first sub-member signal so that the receiver can determine whether the sub-member signal carried in the current first encapsulation frame is the first sub-member signal or the second sub-member signal; Encapsulation type information is used to indicate the encapsulation position of the encapsulation attribute information corresponding to the current first sub-member signal. In the first encapsulation format, the encapsulation type information should indicate that the encapsulation attribute information is encapsulated in the overhead of the encapsulation frame.

[0036] Please see Figure 5 This is a schematic diagram illustrating a second encapsulation format for the first encapsulation frame provided in an embodiment of this application. Figure 5 As shown, the first encapsulation frame adopts a virtual encapsulation form, including a first sub-member signal, which carries the original overhead in the original client signal. Figure 5 Compared to the first encapsulation frame shown Figure 4 The first encapsulation frame shown is mainly different in that... Figure 5 The first encapsulation frame shown does not encapsulate new overhead. Instead, it directly borrows some overhead information (FAS and MFAS of the alignm field) of the original overhead carried by the first sub-member signal and encapsulates the encapsulation attribute information corresponding to the first sub-member signal through the original overhead retention (RES) field.

[0037] You should be able to understand. Figure 5 In the first encapsulation frame shown, the FAS information in the alignm field of the original overhead carried by the first sub-member signal indicates the start position of the first encapsulation frame, and the MFAS information in the alignm field indicates the frame order position of the original client signal to which the current first sub-member signal belongs. Encapsulation attribute information is carried in the RES field of the original overhead carried by the first sub-member signal. The encapsulation attribute information may include at least one of the following: total number of sub-members, sub-member number information, sub-member type information, and encapsulation type information. The meanings of these encapsulation attribute information can be referred to the relevant introduction of the first encapsulation format above, and will not be repeated here. It is worth noting that in the second encapsulation format, the encapsulation type information should indicate that the encapsulation attribute information is encapsulated in the reserved (RES) field of the original overhead.

[0038] It should be noted that the length of the original overhead MFAS field is usually 8 bits, which can represent frame sequence values ​​between 0 and 255. In practical applications, when the length of the MFAS field is insufficient to represent the sequence number value (such as when the sequence number value to be represented is greater than 255, such as 1023), a new frame sequence value (SN value) can be added to the RES field.

[0039] Please see Figure 6 This is a schematic diagram of a third encapsulation format for the first encapsulation frame provided in an embodiment of this application. Figure 6 As shown, the first encapsulation frame uses a real encapsulation format, including overhead and the first sub-member signal. Figure 6 Compared to the first encapsulation frame shown Figure 4 The first encapsulation frame shown is mainly different in that... Figure 6The first encapsulation frame shown does not carry the original overhead; that is, the first sub-member signal in the first encapsulation frame only contains the payload area of ​​the original client signal. The third encapsulation format is suitable when the original client signal is split into more than one first sub-member signal. For example, if the original client signal is split into two first sub-member signals, one of the first sub-member signals uses the first or second encapsulation format (the first encapsulation frame carries the original overhead), while the other first sub-member signal uses the third encapsulation format (the first encapsulation frame does not carry the original overhead). In the third encapsulation format, the overhead in the first encapsulation frame carries encapsulation attribute information. Specific information about the encapsulation attribute information can be found in the previous introduction to the first encapsulation format, and will not be repeated here.

[0040] based on Figures 4-6 As can be seen from the first encapsulation frame format shown, in this embodiment of the application, at least one first sub-member signal carries the original overhead in the original client signal, and the encapsulation attribute information of the first sub-member signal is added at a preset position in the first encapsulation frame. The preset position here includes: the overhead position of the first encapsulation frame, or the reserved field position of the original overhead.

[0041] In one possible implementation, mapping the second sub-member signal to the corresponding second FlexO instance includes: mapping the second sub-member signal to the corresponding second encapsulation frame and adding encapsulation attribute information of the second sub-member signal to the overhead of the second encapsulation frame; and mapping the second encapsulation frame to one or more sub-slots of the corresponding second FlexO instance.

[0042] In one possible implementation, the second encapsulation frame carrying the second sub-member adopts a true encapsulation form, that is, the second encapsulation frame includes overhead and a second sub-member. The overhead of the second encapsulation frame carries encapsulation attribute information, which includes: Frame Position Information (FAS), used to indicate the start position of the second encapsulation frame, so that the receiving end can determine the boundary of the second encapsulation frame by detecting the frame position information, and determine the start position of the current first sub-member signal according to the predefined encapsulation format of the second encapsulation frame; Frame Sequence Information (MFAS / SN), used to indicate the sequential position of the original client signal to which the current second sub-member signal belongs; Total Number of Sub-members Information, used to indicate the total number of first and second sub-member signals contained in the original client signal to which the current sub-member signal belongs; Sub-member Number Information, used to indicate the number of the current second sub-member signal; Sub-member Type Information, used to indicate the type of the current second sub-member signal; Encapsulation Type Information, used to indicate the encapsulation position of the encapsulation attribute information corresponding to the current second sub-member signal. For the second encapsulation frame, the encapsulation type information should indicate that the encapsulation attribute information is encapsulated in the overhead of the encapsulation frame.

[0043] It should be noted that in the previous example, the original overhead in the original client signal is carried in the first sub-member signal. In actual implementation, the original overhead in the original client signal can also be carried in the second sub-member signal. This application embodiment does not limit this.

[0044] It should be noted that the actual encapsulation described in the embodiments of this application refers to adding newly defined overhead to the sub-members. The encapsulation overhead includes frame information, frame sequence number (SN) information, sub-member information (such as the total number of sub-members, the sub-member number information in this frame, and the sub-member type information), and encapsulation type information. That is, the encapsulated frame consists of overhead and sub-member signals. The length of the encapsulated frame is larger than the length of the sub-member signals, and the rate is higher than the rate of the sub-member signals.

[0045] Please see Figure 7 This diagram illustrates various overhead formats for encapsulated frames using actual encapsulation, as provided in the embodiments of this application. It should be understood that the first 16 bytes of the first line of the original client signal contain framing overhead: a FAS field (6 bytes) and an MFAS field (1 byte). The overhead fields of the encapsulated frame can borrow the content of the FAS and MFAS fields (as sequence values ​​of the encapsulated frame) from the original client signal, and then add 9 bytes of custom content (sub-member information (total number of sub-members, sub-member number, sub-member type), encapsulation type, etc.) to form 16 bytes as the overhead of the encapsulated frame, such as... Figure 7 The encapsulation frame overhead format in Example 1 is shown. Alternatively, only the 7-byte content of the FAS and MFAS fields of the original client signal can be simulated, without adding any other content. That is, the encapsulation frame overhead only includes the FAS and MFAS fields, as shown below. Figure 7 The encapsulation frame overhead format shown in Example 2 is an example. Alternatively, only a portion of the FAS and MFAS fields from the original client signal can be simulated (e.g., the 5 bytes of the FAS field and the MFAS field), without adding other content, such as... Figure 7 The encapsulation frame overhead format is shown in Example 3. You can also customize the overhead content of the encapsulated frame (fixed frame overhead, frame sequence values), such as... Figure 7 The encapsulation frame overhead format is shown in Example 4. Besides the frame overhead and frame sequence value, the overhead content of the encapsulated frame may also include other information (sub-member information (total number of sub-members, sub-member number, sub-member type), encapsulation type, etc.), such as... Figure 7 The encapsulation frame overhead format shown in Example 5.

[0046] The virtual encapsulation described in this application refers to directly borrowing a portion of the overhead of sub-member signals (such as FAS and MFAS fields) as the overhead of the encapsulation frame. When the overhead information of the sub-members is insufficient, reserved fields in the overhead of the sub-member signals are enabled, and these reserved fields are modified as supplementary overhead information for the encapsulation frame. For example, the reserved field positions in the overhead of the sub-member signals are used as the SN information, sub-member information (total number of sub-members, sub-member number in this frame, sub-member type), and encapsulation type information of the encapsulation frame. The length of the virtual encapsulation frame is the same as the length and rate of the sub-member signals, without increasing the additional bandwidth.

[0047] For example, the encapsulated attribute information includes at least one of the following: Frame information is used to indicate the starting position of the current sub-member signal; Frame sequence information is used to indicate the sequential position of the original client signal to which the current sub-member signal belongs; The total number of sub-members information is used to indicate the total number of first and second sub-member signals contained in the original client signal to which the current sub-member signal belongs; Sub-member number information, used to indicate the number of the current sub-member signal; Sub-member type information is used to indicate whether the current sub-member signal is the first sub-member signal or the second sub-member signal; Encapsulation type information is used to indicate whether the encapsulation attribute information corresponding to the current sub-member signal is located in the reserved field of the original overhead or in the overhead of the encapsulation frame.

[0048] It should be understood that the encapsulation frame contains encapsulation attribute information of the sub-members, so that after the receiving end receives the FlexO instance, it can extract the sub-member signals based on the encapsulation attribute information, and then recover the original client signals based on the sub-member signals.

[0049] Please see Figure 8 This is a schematic diagram illustrating a process of splitting the original customer signal, provided in an embodiment of this application. Figure 8The original client signal shown is an ODU4 signal frame with a rate of 104.794G. It is split into a first sub-member signal with a rate of approximately 100G and a second sub-member signal with a rate of approximately 5G. The first sub-member signal carries the original overhead. The first sub-member signal is then encapsulated by adding new overhead before it and adding its encapsulation attribute information to that overhead, resulting in a first encapsulated frame. Similarly, the second sub-member signal is encapsulated by adding new overhead before it and adding its encapsulation attribute information to that overhead, resulting in a second encapsulated frame. The first encapsulated frame is mapped to a first FlexO instance, and the second encapsulated frame is mapped to a second FlexO instance. Both the first and second FlexO instances have a rate of approximately 100G, slightly higher than the rate of the first sub-member signal.

[0050] It should be noted that since the overhead added by using real encapsulation in the embodiments of this application is very small, the increased rate can be ignored. The rate of the encapsulated frame using real encapsulation is basically equal to the rate of the sub-member signal.

[0051] exist Figure 8 In the example, the second encapsulation frame also carries other second sub-member signals, which are obtained by splitting from other original client signals. The two second sub-member signals in the second encapsulation frame share a single overhead. It should be understood that the number of bytes in a second sub-member signal split from an original client signal is very small. If each second sub-member signal from an original client signal were encapsulated separately, adding an overhead field to the new encapsulation frame would increase the bandwidth occupied by the overhead, resulting in bandwidth waste. Therefore, in practical implementations, multiple second sub-member signals can be encapsulated into one second encapsulation frame, with the multiple second sub-member signals in the second encapsulation frame sharing a single overhead. It should be noted that the multiple second sub-member signals in the second encapsulation frame can be arranged in frame order. For example, the first second sub-member signal in the second encapsulation frame might be a member of the first original client signal, the second second sub-member signal might be a member of the second original client signal, and so on. This way, even if multiple second sub-member signals are encapsulated in one second encapsulation frame, the frame sequence information corresponding to each second sub-member signal can be distinguished.

[0052] In one possible implementation of this application, the rate of the first FlexO instance is the second rate S2, and the payload of the original client signal includes multiple basic units of equal size; splitting the original client signal into A first sub-member signals and 1 second sub-member signal includes: splitting all basic units into A sets of first basic units and one set of second basic units based on a preset splitting rule, wherein the number of basic units contained in each set of first basic units is determined according to the second rate S2; for each set of first basic units, forming a first sub-member signal from the basic units in the set of first basic units; and forming a second sub-member signal from the basic units in the set of second basic units.

[0053] The following is combined Figure 8 The process of splitting the original customer signal is explained.

[0054] Figure 8 The original client signal in the frame is an ODU4 signal, consisting of 4 rows × 3824 columns of bytes. The first 16 columns are the overhead area, and the last 3808 columns are the payload area. Using 16 bytes as the basic unit, the 3824 columns of the ODU4 signal frame can be divided into 239 (239 × 16 = 3824) subsets, each containing 4 basic units, such as... Figure 8 As shown.

[0055] Based on preset splitting rules, all basic units of the ODU4 signal frame are split into one first basic unit set and one second basic unit set. The splitting rules include the following forms: The first method is a basically uniform, equally spaced partitioning method. For example, the basic units of the 20*k (k is a natural number) subset are assigned to the second basic unit set. That is, the basic units of the 20th, 40th, ..., 220th subsets are assigned to the second basic unit set (a total of 11 subsets), and the basic units of the remaining subsets are assigned to the first basic unit set (a total of 228 subsets). The second method is to split the basic units into front and back categories. For example, the basic units of the first 228 subsets are divided into the first basic unit set, and the basic units of the last 11 subsets are divided into the second basic unit set. The third method is algorithmic decomposition. For example, the algorithm calculates which sub-member each basic unit belongs to, and then divides the basic units accordingly. The fourth method is a fixed pattern splitting method, such as splitting all subsets according to the expected position pattern.

[0056] For an ODU4 signal frame, the bandwidth of the first basic unit set is about 100G, forming the first sub-member signal (or integer sub-member); the bandwidth of the second basic unit set is about 5G, forming the second sub-member signal (or fractional sub-member).

[0057] Please see Figure 9 This is a schematic diagram illustrating the splitting process of an ODU4 signal according to an embodiment of this application. The ODU4 signal consists of bytes arranged in 4 rows × 3824 columns. In this example, each 16 bytes is used as a basic unit, resulting in 956 basic units for the ODU4 signal. These 956 basic units are then split into a first set of basic units and a second set of basic units according to a preset splitting rule. The first set of basic units contains m1 basic units, and the second set of basic units contains m2 basic units, where m1 + m2 = 956. Specific splitting methods include the following: The first method is a basically uniform, equally spaced partitioning method. For example, the 20*k (k is a natural number) basic unit is assigned to the first basic unit set, that is, the 20th, 40th, 60th, ..., 920th basic units are assigned to the second basic unit set (a total of 46 basic units), and the rest are assigned to the first basic unit set (a total of 910 basic units). The second method is to split the basic units into front and back categories. For example, the first 910 basic units are divided into the first basic unit set, and the last 46 basic units are divided into the second basic unit set. The third method is algorithmic decomposition. For example, the algorithm calculates which sub-member each basic unit belongs to, and then divides the basic units accordingly. The fourth method is the fixed pattern splitting method, which involves splitting all basic units according to the expected position pattern. Any splitting method can be selected, such as: m1=910, m2=46; m1=911, m2=45; m1=912, m2=44; m1=913, m2=43; etc.

[0058] Please see Figure 10 This is a schematic diagram illustrating a process of mapping original customer signals to a FlexO instance, as provided in an embodiment of this application. Figure 10 The original client signal rate is approximately 105G (e.g., ODU4 and ODUCn signals both have a rate of approximately 105G). This approximately 105G signal is split into a first sub-member signal with a rate of approximately 100G and a second sub-member signal with a rate of approximately 5G. The first and second sub-member signals are then encapsulated into encapsulation frames, forming a first encapsulation frame and a second encapsulation frame, respectively. The first encapsulation frame uses virtual encapsulation, while the second encapsulation frame uses real encapsulation. The first encapsulation frame is carried by an instance without sub-slots (i.e., the first FlexO instance). Figure 10 In the first FlexO instance, instance1 is selected to carry a portion of the sub-slots on the second encapsulated frame. Figure 10 In this context, instance k belongs to the second FlexO instance.

[0059] It should be understood that in practical implementation scenarios, in addition to ODU4 and ODUCn signals with a rate of approximately 105G, other customer signals with different rates can also be mapped to FlexO instances in a similar manner.

[0060] Please see Figure 11 This is a schematic diagram illustrating another process for mapping raw customer signals to FlexO instances, provided in an embodiment of this application. Figure 11 The original client signal in the data has a rate of approximately 210G, which can be divided into two first sub-member signals with a rate of approximately 100G each and one second sub-member signal with a rate of approximately 10G. Of the two first sub-member signals, one uses virtual encapsulation and the other uses physical encapsulation; the second sub-member signal uses physical encapsulation. For the encapsulated frame formed after the sub-member signals are encapsulated, the first encapsulated frame carrying the first sub-member signal is carried by an instance without sub-slot division (i.e., the first FlexO instance). Figure 11 Instance1 and Instance2 both belong to the first FlexO instance. The second encapsulated frame carrying the second sub-member signal selects a portion of the sub-time slots to carry the signal on the instance (i.e., the second FlexO instance) that is divided into sub-time slots. Figure 11 In this context, instance k belongs to the second FlexO instance.

[0061] It should be understood that in practical implementations, the original client signal may be divided into many sub-time slots, each carrying a different upper-layer client. Please refer to [link / reference]. Figure 12 This is a time slot allocation diagram for ODU4 provided for related technologies. (Example:) Figure 12 As shown, ODU4 is divided into 84 sub-time slots, each with a rate of 1.25G, using bytes as the unit for sub-time slots. For ODU4, which uses bytes as the unit for sub-time slots, splitting requires all content from the same sub-time slot to be allocated to a single sub-member, rather than distributed across multiple different sub-members, facilitating sub-time slot organization and scheduling. In practical scenarios, all 84 sub-time slots in ODU4 may carry upper-layer client content, or some may carry upper-layer clients while others are idle. To conserve bandwidth, when splitting ODU4, idle sub-time slots are not included in the sub-member signal; their content is discarded directly. Since sub-time slots in ODU4 are based on bytes, splitting should also be done on a byte-by-byte basis.

[0062] It should be understood that when the original customer signal is split into basic units, the basic unit should be the non-idle sub-time slots in the original customer signal that carry services. That is, the idle sub-time slots in the original customer signal are filtered out, and then the bytes corresponding to the remaining non-idle sub-time slots are divided into basic units, and then sub-members are divided based on the basic units obtained from the division.

[0063] Please see Figure 13 This is a schematic diagram illustrating the splitting of a raw customer signal according to an embodiment of this application. Figure 13 As shown, the original client signal has 15296 bytes. The content of the same sub-slot is split into the same sub-member, specifically divided into three parts: m1 bytes, m2 bytes, and x bytes, where m1 + m2 + x = 15296. m1 and m2 bytes are non-idle sub-slots carrying services, with the bandwidth of m1 bytes approximately equal to the bandwidth of a FlexO instance (approximately 100G). x bytes are idle sub-slots not carrying services. m2 bytes are the remainder after subtracting the m1 non-idle sub-slot bytes and x idle sub-slot bytes from the 15296 bytes. The m1 bytes are encapsulated into a frame and mapped to an instance without sub-slots. The m2 bytes are encapsulated into a frame and mapped to a portion of the sub-slots of an instance with sub-slots. The x bytes are idle sub-slots and can therefore be discarded.

[0064] It should be understandable that, for Figure 13 The original client signal should be filtered through x idle sub-slot bytes, and the remaining (15296-x) bytes should be split to obtain a 100G portion (m1 bytes) and a fractional portion (m2 bytes). Specific splitting methods include basically uniform interval splitting, front-and-back class splitting, or fixed pattern splitting.

[0065] It should be noted that when there is an operation to filter idle sub-time slots during the splitting process, when the sub-member signals are merged at the receiving end to restore the original customer signal, the content of the filtered idle sub-time slots needs to be supplemented. Generally, the idle sub-time slots are set to 0 by default.

[0066] It should be noted that in actual implementation, besides splitting each customer signal frame individually, multiple customer signal frames can also be split as a whole. This results in a more precise proportional relationship after splitting, ensuring that the rates of the integer sub-members meet the expected rate requirements. When the customer signal rate is greater than 200G, the customer signal is split into multiple integer sub-members of approximately 100G and a fractional sub-member. When multiple sub-time slots exist in a customer signal frame, idle sub-time slots can be filtered during splitting, retaining only the non-idle sub-time slots among all sub-members to save transmission bandwidth.

[0067] Please see Figure 14 This is a schematic diagram of another original customer signal splitting provided in an embodiment of this application. Figure 14 In the example, B original client signals (each original client signal has 15296 bytes) are treated as a whole. The B×15296 bytes are split into A first sub-member signals, 1 second sub-member signal, and an idle sub-time slot portion. The A first sub-member signals contain m1, m2, ..., mA bytes respectively, for a total of m (m=m1+m2+...+mA) bytes. The rate of each first sub-member signal is approximately 100G. The idle sub-time slot portion has a total of x bytes, including all the idle sub-time slots in the a original client signals. The second sub-member signal is the remaining part (n bytes) after subtracting the m bytes of the first sub-member signal portion and the x bytes of the idle sub-time slot portion from the B×15296 bytes. It should be understood that during splitting, a sub-member signal can retain the original overhead of the original client signal. If the sub-member signal contains the original overhead, the sub-member signal is encapsulated using a virtual encapsulation method (borrowing the overhead information of the original client signal, without adding new bytes, keeping the frame length and rate unchanged, but possibly modifying the content of the original overhead retention field to pass encapsulation attribute information); if the sub-member signal does not contain the original overhead, the sub-member signal is encapsulated using a real encapsulation method (adding overhead field information, increasing the frame length and rate).

[0068] It should be noted that for the second sub-member signal (the remaining sub-member signal), each split second sub-member signal can be encapsulated separately, i.e., one second sub-member signal is encapsulated into one second encapsulation frame; alternatively, multiple split second sub-member signals can be combined for encapsulation, i.e., multiple second sub-member signals are encapsulated into one second encapsulation frame. Multiple second sub-member signals share the same overhead, thus reducing the proportion of overhead content and saving transmission bandwidth. Especially since the number of bytes in the split remaining sub-member signals is relatively small, encapsulating each remaining sub-member signal separately would result in a large proportion of encapsulation frame overhead, wasting bandwidth. Figure 15 The diagram shown is a schematic representation of the encapsulation of the second sub-member signal provided in an embodiment of this application. Figure 15In the example, some second sub-member signals are encapsulated into a second encapsulation frame on their own, while some second sub-member signals are encapsulated in combination with other second sub-member signals. Y (a positive integer) second sub-member signals are encapsulated into a second encapsulation frame, and the Y second sub-member signals use the same overhead.

[0069] In one possible real-world scenario, a 100G FlexO instance might be divided into 20 or 19 sub-time slots. Regardless of whether a 100G FlexO instance is divided into 20 or 19 sub-time slots, the bandwidth of the second encapsulation frame and the bandwidth of the FlexO instance's sub-time slots may not perfectly match. Specifically, when a 100G FlexO instance has 20 sub-time slots, each sub-time slot has a bandwidth of 5G. When the bandwidth of the second encapsulation frame is 5.5G, one sub-time slot cannot carry one second encapsulation frame, requiring two sub-time slots. When a 100G FlexO instance has 19 sub-time slots, each sub-time slot has a bandwidth of 5.26G. When the bandwidth of the second encapsulation frame is 5.2G, one sub-time slot can just carry one sub-member. However, when a sub-member has a bandwidth of 5.5G, one sub-time slot cannot carry even a fraction of a sub-member, requiring two sub-time slots to carry one second encapsulation frame. Because the rates of the FlexO instance sub-slots and the second encapsulation frame may not match, and may differ significantly, the GMP (Generic Mapping Procedure) mapping algorithm can be used when mapping the second encapsulation frame to the sub-slots in the FlexO instance. This algorithm calculates the rate ratio between the second encapsulation frame and the multiple sub-slots carrying it, determining the total number of bytes (Cm) of the second encapsulation frame carried in each sub-slot. Based on the total number of bytes (N) carried by the sub-slots, the distribution positions of the Cm bytes in the N-byte space are calculated, and the content of the second encapsulation frame is then carried at the corresponding distribution positions. The Cm value is transmitted in the overhead of the FlexO instance so that the receiving end can determine the byte distribution positions of the second encapsulation frame based on the Cm value and the N value of the sub-slot, and extract the byte content of the second encapsulation frame at the distribution positions. To ensure reliable transmission of the Cm value and avoid transmission failure due to bit errors, the Cm value can be transmitted multiple times (e.g., three times). The transmission of the Cm value is checked by comparing the content of multiple transmissions to determine if there is an error. When multiple Cm values ​​are transmitted differently, according to the majority rule, if the content is the same more than half of the time, then the equal content is taken as the correct Cm value. For example, if a Cm value is transmitted three times, as long as at least two Cm values ​​are the same, then the same Cm value is taken as the final result.

[0070] In one possible implementation of this application, before sending the second FlexO instance, the method further includes: adding a first value to the overhead of the second FlexO instance. The first value is used to indicate the amount of client service information contained in the second encapsulation frame. It is understood that the first value is the aforementioned Cm value, which indicates the amount of client service information contained in the second encapsulation frame (e.g., how many bytes the second encapsulation frame contains), so that the receiving end can determine the byte distribution position of the second encapsulation frame in multiple sub-time slots based on the number of bytes in the second encapsulation frame (Cm value) and the number of bytes in the multiple sub-time slots carrying the second encapsulation frame (N value).

[0071] It should be noted that in actual implementation, when the encapsulated frame carrying sub-member signals is mapped to a FlexO instance or a sub-slot of a FlexO instance, a position indicator value can also be set in the overhead of the FlexO instance. The position indicator value is used to indicate specific byte content of the encapsulated frame, such as the starting position of the encapsulated frame. Figure 16 The diagram shown is a schematic of a FlexO instance provided in an embodiment of this application. The overhead of the FlexO instance carries a position indicator value, which is used to determine the starting position of the encapsulation frame. In this way, when encapsulating sub-members, it is not necessary to add fixed frame overhead content to determine the starting position. Only the frame sequence (such as SN) needs to be added. In this way, the receiving end can directly determine the starting position of the encapsulation frame through the position indicator value, avoiding the need to search for fixed frame content to determine the starting position of the encapsulation frame, thus improving the efficiency of determining the starting position of the encapsulation frame.

[0072] It should be noted that in actual implementation, there are various ways to split the original client signal into multiple sub-member signals. For example, there is the basically uniform, equally spaced splitting method, such as splitting the original client signal with a bandwidth of about 105G into a first sub-member signal of about 100G and a second sub-member signal of about 5G, dividing the original client signal into 21 parts, with the ratio of the first sub-member signal to the second sub-member signal being 20:1. In every 21 basic units, 20 basic units are assigned to the first sub-member signal and 1 basic unit is assigned to the second sub-member signal, and so on, splitting at equal intervals. Algorithmic splitting methods, such as calculating which sub-member each basic unit is assigned to according to a certain algorithm. Pattern splitting methods, such as determining which sub-member each basic unit is assigned to according to a certain fixed pattern.

[0073] The following section uses the ODUcn signal as an example to illustrate the solution of this application embodiment.

[0074] Please see Figure 17 This is a schematic diagram illustrating a process of mapping an ODUcn signal to a FlexO instance, as provided in an embodiment of this application. The ODUcn consists of n (n is a positive integer) parallel sub-parts, each containing 4 rows × 3824 columns of bytes, with a rate of approximately 105G. Figure 17In the example, each sub-part of the ODUcn signal is separately split into a first sub-member signal and a second sub-member signal, resulting in n first sub-member signals and n second sub-member signals; each first sub-member signal is virtually encapsulated to obtain a first encapsulated frame corresponding to each first sub-member signal, and the first encapsulated frame is mapped to a first FlexO instance without time slots. Figure 17 In the context of instances 1, 2, ..., a first FlexO instance carries a first encapsulation frame; each second sub-member signal is actually encapsulated to obtain the second encapsulation frame corresponding to each second sub-member signal, and the second encapsulation frame is mapped to the second FlexO instance in the time slot division ( Figure 17 In the instance X), a second FlexO instance carries multiple second encapsulation frames.

[0075] Please see Figure 18 This is a schematic diagram illustrating another process for mapping the ODUcn signal to a FlexO instance, provided in an embodiment of this application. Figure 18 In the example, all sub-parts of the ODUcn signal are combined as a whole. Based on this whole, it is split into multiple first sub-member signals and one second sub-member signal. Each first sub-member signal is virtually encapsulated to obtain the first encapsulated frame corresponding to each first sub-member signal. The first encapsulated frame is then mapped to the first FlexO instance without time slot division. Figure 18 In the context of instances 1, 2, ..., a first FlexO instance carries a first encapsulation frame; the second sub-member signal is actually encapsulated to obtain the second encapsulation frame corresponding to the second sub-member signal, and the second encapsulation frame is mapped to the second FlexO instance in the time slot ( Figure 18 (instance X in the middle).

[0076] Please see Figure 19 This is a flowchart illustrating a signal receiving method provided in an embodiment of this application. It can be understood that... Figure 3 The signal receiving method shown is applied at the receiving end. For example... Figure 19 As shown, the method includes steps S201-S203, which are described in detail below.

[0077] Step S201: Receive at least one first FlexO instance and at least one second FlexO instance, each first FlexO instance carrying a first sub-member signal of an original client signal, and each second FlexO instance carrying a second sub-member signal of the original client signal; Step S202: Extract the first sub-member signal from the first FlexO instance and extract the second sub-member signal from the second FlexO instance; Step S203: Merge A first sub-member signals and one second sub-member signal belonging to the target original customer signal to obtain the target original customer signal, where A is a positive integer.

[0078] It should be understood that the transmitting end splits the original client signal into A first sub-member signals and one second sub-member signal. The A first sub-member signals are mapped to A first FlexO instances for carrying, and the second sub-member signals, along with other second sub-member signals from the original client signal, are mapped to a second FlexO instance for carrying. Then, the first and second FlexO instances are transmitted. The receiving end, after receiving the first and second FlexO instances, extracts the first sub-member signals from the first FlexO instances and the second sub-member signals from the second FlexO instances. It then merges the A first sub-member signals and one second sub-member signal belonging to the target original client signal to recover the target original client signal.

[0079] In one possible implementation of this application, the overhead of the FlexO instance carries a type identifier of the FlexO instance, and the receiving end can determine whether the currently received FlexO instance is the first FlexO instance or the second FlexO instance based on the type identifier.

[0080] In one possible implementation of this application, the payload area of ​​a FlexO instance includes one or more encapsulation frames, each encapsulating one or more sub-member signals. Specifically, the payload area of ​​a first FlexO instance includes one encapsulation frame (referred to as the first encapsulation frame in this embodiment), and the first encapsulation frame encapsulates a first sub-member signal; the payload area of ​​a second FlexO instance includes one or more encapsulation frames (referred to as the second encapsulation frame in this embodiment), and the second encapsulation frame encapsulates one or more second sub-member signals. When the receiving end receives a FlexO instance, it first extracts the encapsulation frame from the payload area of ​​the FlexO instance, and then extracts the sub-member signal from the encapsulation frame.

[0081] In one possible implementation of this application, the first FlexO instance includes a first encapsulation frame carrying a first sub-member signal, the first encapsulation frame carrying framing information. Extracting the first sub-member signal from the first FlexO instance includes: identifying the framing information from the first FlexO instance, extracting the first encapsulation frame from the first FlexO instance based on the framing information, and extracting the first sub-member signal from the first encapsulation frame.

[0082] The second FlexO instance includes a second encapsulation frame carrying a second sub-member signal, the second encapsulation frame carrying framing information; extracting the second sub-member signal from the second FlexO instance includes: identifying the framing information from the second FlexO instance, extracting the second encapsulation frame from the second FlexO instance based on the framing information, and extracting the second sub-member signal from the second encapsulation frame.

[0083] It should be understood that the frame positioning information is used to determine the start position of the encapsulated frame. After receiving the FlexO instance, the receiving end detects the frame positioning information from the FlexO instance. When the frame positioning information is detected, the boundary of the encapsulated frame can be determined, and then the encapsulated frame and its sub-member signals can be extracted.

[0084] For example, the frame information can be encapsulated in the overhead of the encapsulated frame carrying the current sub-member; or, when the current sub-member contains the original overhead of the original client signal, the frame information can be located in the FAS field of the original overhead.

[0085] It should be understood that the arrival time order of the various sub-member signals at the receiving end is not fixed. For example, the A first sub-member signals and one second sub-member signal split from the target original client signal may be numbered 0, 1, ..., A, respectively. The sending end sends the corresponding FlexO instances sequentially according to the sub-member number order. However, in actual scenarios, there are delay differences when the sub-member signals are transmitted through the network, and the sub-member signals usually do not arrive at the receiving end sequentially. For example, the 0th sub-member signal may depart earlier than the 1st sub-member signal, but the 1st sub-member signal may arrive at the receiving end earlier than the 0th sub-member signal. In this case, the first FlexO instance can carry the sub-member number information corresponding to the first sub-member signal, and the second FlexO instance can carry the sub-member number information corresponding to the second sub-member signal. Before merging the A first sub-member signals and one second sub-member signal belonging to the target original client signal to obtain the target original client signal, the receiving method also includes: determining the sub-member corresponding to each first sub-member signal and each second sub-member signal according to the sub-member number information.

[0086] For example, the sub-member number information can be encapsulated in the overhead of the encapsulation frame carrying the current sub-member; or, when the current sub-member contains the original overhead of the original client signal, the sub-member number information can be encapsulated in a reserved field of the original overhead.

[0087] Specifically, the sub-member number information indicates which sub-member the signal belongs to. For example, a sub-member number of "00" indicates that the signal is sub-member number 0. After receiving the FlexO instance, the receiving end can retrieve the sub-member number information corresponding to the sub-member signal from the FlexO instance. Then, based on the sub-member number information, it determines which sub-member the current signal belongs to and adds the signal to the corresponding sub-member buffer queue. It should be understood that the receiving end can set up sub-member buffer queues numbered 0, 1, ..., A to buffer sub-member signals with corresponding numbers. After all sub-member signals of the target original client signal have arrived at the receiving end, the receiving end retrieves the sub-member signals of the target original client signal from each buffer queue and then merges the sub-member signals of the target original client signal to restore the target original client signal.

[0088] It should be understood that a customer service may consist of multiple frames, meaning a customer service includes multiple original customer signals, each with corresponding frame sequence information to indicate its frame order. For example, if the frame sequence information for an original customer signal is "00", it indicates that the original customer signal is frame 0; if the frame sequence information is "01", it indicates that the original customer signal is frame 1. When a customer service includes multiple original customer signals, the arrival time order of the sub-members of each original customer signal at the receiving end is not necessarily fixed. For example, the sending end may send the sub-members of each original customer signal sequentially according to frame order, but the sub-members of the later-sent original customer signals may arrive at the receiving end earlier than the sub-members of the earlier-sent original customer signals. In this case, the frame sequence information corresponding to the first sub-member signal can be carried in the first FlexO instance, and the frame sequence information corresponding to the second sub-member signal can be carried in the second FlexO instance. Before merging the A first sub-member signals and one second sub-member signal belonging to the target original client signal to obtain the target original client signal, the receiving method further includes: determining the frame order corresponding to each first sub-member signal and each second sub-member signal according to the frame sequence information.

[0089] Specifically, the frame sequence information corresponding to the sub-member signal is used to indicate which frame of the original client signal the sub-member signal belongs to. For example, if the frame sequence information corresponding to the sub-member signal is "00", it means that the sub-member signal belongs to the 0th frame of the original client signal. After the receiving end extracts the corresponding sub-member signal from the FlexO instance and determines which sub-member it is based on the sub-member number information, it adds the sub-member signal to the corresponding sub-member buffer queue. At the same time, it also determines the frame order of the sub-member signal based on the frame sequence information (i.e., determines which frame of the original client signal the sub-member signal belongs to), and then sorts the sub-member signals in the sub-member buffer queue according to the frame order. For example, the i-th sub-member buffer queue may contain the i-th sub-members of the original client signals in frames 0, 1, and 2. The i-th sub-members of each original client signal are arranged sequentially in the i-th sub-member buffer queue according to the frame order, so that the receiving end can perform frame alignment on the sub-members of multiple original client signals belonging to one client service and determine the sub-members belonging to the same original client signal.

[0090] For example, frame sequence information can be encapsulated in the overhead of the encapsulated frame carrying the current sub-member; or, when the current sub-member contains the original overhead of the original client signal, the frame sequence information can be located in the MFAS field of the original overhead, or in the reserved field of the original overhead, that is, the reserved field of the original overhead encapsulates SN information.

[0091] In one possible implementation of this application, the first FlexO instance and the second FlexO instance also carry information on the total number of sub-members, which is used to indicate the total number of the first and second sub-members contained in the original client signal to which the current sub-member signal belongs, so that the receiving end can recover the target original client signal according to the number of sub-members corresponding to the target original client signal.

[0092] In one possible implementation of this application, the first FlexO instance and the second FlexO instance also carry sub-member type information to indicate whether the sub-member signal in the current encapsulation frame is a first sub-member signal or a second sub-member signal. For example, if the sub-member type information in the current FlexO instance is a first sub-member type, it indicates that the current FlexO instance is a first FlexO instance and carries only one first sub-member signal; if the sub-member type information in the current FlexO instance is a second sub-member type, it indicates that the current FlexO instance is a second FlexO instance and carries multiple second sub-member signals.

[0093] In one possible implementation of this application, both the first sub-member signal and the second sub-member signal include multiple basic units. The A first sub-member signals and one second sub-member signal belonging to the target original customer signal are merged to obtain the target original customer signal. This includes: determining the position of each basic unit in the target original customer signal according to the sub-member number information and the preset splitting rules, and merging all the basic units according to the position of each basic unit to obtain the target original customer signal.

[0094] It should be understood that the target original customer signal is divided into multiple basic units. The transmitting end divides the target original customer signal into basic units according to a preset splitting rule, resulting in A first sub-member signals and one second sub-member signal. The splitting rule includes methods such as basically uniform equal-interval splitting, front-and-back splitting, algorithmic splitting, or fixed-pattern splitting. For the receiving end, it needs to perform the reverse process of splitting the target original customer signal, i.e., recovering the target original customer signal. During the recovery process, the order between member signals is first determined based on the sub-member number information. Then, according to the splitting method adopted by the transmitting end, the position of the basic unit in each member signal within the target original customer signal is determined. Finally, all basic units are merged according to the determined positions to recover the target original customer signal.

[0095] In one possible implementation of this application, the basic unit is a non-idle sub-time slot carrying services in the target original customer signal. All basic units are merged according to their positions, including: determining the position of the idle sub-time slot in the target original customer signal according to preset idle sub-time slot configuration information; and merging the non-idle sub-time slots and idle sub-time slots according to the positions of each non-idle sub-time slot and the position of the idle sub-time slot to obtain the target original customer signal.

[0096] It should be understood that the target original client signal contains some idle sub-time slots. These idle sub-time slots do not carry services and are usually set to 0 by default. To save transmission bandwidth, when the sending end splits the target original client signal, it does not include these idle sub-time slots in the sub-component signals. That is, the basic unit in the sub-component signals is a non-idle sub-time slot that carries services. In order for the receiving end to successfully recover the target original client signal, the idle sub-time slot configuration information can be told to the receiving end in advance, so that the receiving end knows the distribution of idle sub-time slots in the target original client signal. Then, in the process of recovering the target original client signal, the receiving end combines the non-idle sub-time slots and the idle sub-time slots according to the location of the non-idle sub-time slots and the distribution of the idle sub-time slots to obtain the target original client signal.

[0097] In one possible implementation of this application, the first FlexO instance includes a first encapsulation frame carrying a first sub-member signal; the receiving method further includes: removing the overhead in the first encapsulation frame to obtain the first sub-member signal.

[0098] It should be understood that the first sub-member signal is encapsulated in the first encapsulation frame through either real encapsulation or virtual encapsulation. The first encapsulation frame is then encapsulated in the first FlexO instance, so that the first sub-member signal is carried through the first FlexO instance. When the first sub-member signal is encapsulated in the first encapsulation frame through real encapsulation, the first encapsulation frame consists of overhead and the first sub-member signal. When the receiving end extracts the first sub-member signal, it removes the overhead in the first encapsulation frame and extracts only the first sub-member signal from the first encapsulation frame.

[0099] In one possible implementation of this application, the first FlexO instance includes a first encapsulation frame carrying a first sub-member signal. At least one first encapsulation frame carries a first sub-member signal that carries the original overhead of the original client signal. The reserved field of the original overhead carries encapsulation attribute information corresponding to the first sub-member signal. Before merging A first sub-member signals and one second sub-member signal belonging to the target original client signal, the receiving method further includes: for the first sub-member signal carrying the original overhead, deleting the encapsulation attribute information in the reserved field of the original overhead in the first sub-member signal.

[0100] In one possible implementation of this application, the first FlexO instance and the second FlexO instance also carry encapsulation type information to indicate whether the sub-member signals in the current encapsulation frame are encapsulated in a real or virtual manner, so that the receiving end can determine whether the reserved fields of the original overhead need to be modified.

[0101] It should be understood that when the first sub-member signal is encapsulated in the first encapsulation frame using virtual encapsulation, the first encapsulation frame borrows the original overhead from the first sub-member signal without adding new overhead bytes. However, the sending end may modify the content of the original overhead reserved field to transmit the encapsulation attribute information of the first sub-member signal. When the reserved field of the original overhead carries the encapsulation attribute information corresponding to the first sub-member signal, the receiving end needs to delete the encapsulation attribute information in the original overhead reserved field and restore the content of the reserved field to the default value of 0 during the process of restoring the target original client signal.

[0102] In one possible implementation of this application, the payload of the second FlexO instance is divided into multiple sub-time slots; extracting the second sub-member signal from the second FlexO instance includes: obtaining a first value from the overhead of the second FlexO instance, determining the amount of customer service information contained in the second sub-member signal based on the first value, and extracting the second sub-member signal from one or more sub-time slots of the second FlexO instance based on the amount of customer service information contained in the second sub-member signal.

[0103] It should be understood that since the rates of the sub-slots of the second FlexO instance and the second encapsulation frame may not match, and may differ significantly, the GMP (Generic Mapping Procedure) mapping algorithm can be used when mapping the second encapsulation frame to the sub-slots in the second FlexO instance. This algorithm calculates the rate ratio between the second encapsulation frame and the multiple sub-slots carrying the second encapsulation frame, determining the total number of bytes Cm (i.e., the first value) carried by the second encapsulation frame in each sub-slot. Based on the total number of bytes N carried by the sub-slots, the distribution positions of Cm bytes in the N-byte space are calculated, and then the content of the second encapsulation frame is carried at the corresponding distribution positions. In this embodiment, the Cm value is transmitted in the overhead of the second FlexO instance so that the receiving end can determine the byte distribution positions of the second encapsulation frame based on the Cm value and the N value of the sub-slot, and then extract the byte content of the second encapsulation frame at the distribution positions. To ensure reliable transmission of the Cm value and avoid transmission failure due to bit errors, the Cm value can be transmitted multiple times (e.g., three times). The receiving end can determine whether the transmitted Cm value is erroneous by judging whether the contents of multiple transmissions are equal. When multiple Cm values ​​are transmitted differently, according to the majority rule, if the content is the same more than half of the time, then the equal content is taken as the correct Cm value. For example, if a Cm value is transmitted three times, as long as at least two Cm values ​​are the same, then the same Cm value is taken as the final result.

[0104] The following example illustrates the process of the receiving end recovering the original customer signal.

[0105] Please see Figure 20 This is a schematic diagram illustrating a process for restoring the original customer signal, provided in an embodiment of this application. Figure 20 As shown, FlexO instances that have not been divided into sub-slots (such as...) Figure 20 The first encapsulation frame (first encapsulation frame) is extracted from instance0 and instance1 in the time-slot partitioning. Each first encapsulation frame has a bandwidth of approximately 100G. Figure 20The encapsulation frame (second encapsulation frame) of the second sub-member signal is extracted from instance A. When extracting the encapsulation frame, the frame start position can be determined based on the frame information (or FAS field) in the encapsulation frame, thus determining the boundary of the encapsulation frame, and the encapsulation frame is extracted from the instance. Based on the sub-member number information in the encapsulation frame, it is determined which sub-member the sub-member signal belongs to, and the encapsulation frame is then added to the corresponding sub-member buffer sequence. Next, the frame order relationship of the encapsulation frames is determined based on the frame sequence information (MFAS field or SN field) in the encapsulation frame, and each encapsulation frame is sorted in the sub-member buffer sequence according to the frame order relationship. All encapsulation frames are in the same frame start position and sub-member order. After aligning the frames in three dimensions (frame order, location, and time), decapsulation is performed. During decapsulation, it's necessary to first determine whether the encapsulation frame uses real or virtual encapsulation. When using real encapsulation, the decapsulation process removes the overhead of the encapsulation frame (the overhead content added during encapsulation), retaining the sub-member signal content. When using virtual encapsulation, the decapsulation process directly modifies the content of the reserved fields in the original overhead. If reserved fields are used to transmit encapsulation attributes such as the sequence number (SN), total number of sub-members, sub-member number, sub-member type, and encapsulation type, these encapsulation attributes need to be cleared, restoring the original default values ​​of the reserved fields. Following the reverse process of the splitting operation, all sub-member signals are merged to restore the original client signal content.

[0106] It should be understood that because the delay time of each sub-member signal during transmission is different, their arrival times at the receiving end vary. Some sub-member signals arrive earlier, and some arrive later. Therefore, each sub-member signal is first buffered at the receiving end, and then the time order is determined according to the serial number (SN) of the encapsulated frame. The earlier arriving sub-member waits for the later arriving sub-member. Time alignment of different sub-members is only completed when the frame sequence numbers (SNs) of all sub-members are aligned. For encapsulated frames using real encapsulation, the receiving end needs to delete the overhead information of the encapsulation frame; for encapsulated frames using virtual encapsulation, the overhead information does not need to be deleted, but the content modified for transmitting encapsulation attribute information in the reserved fields needs to be restored. The sending end can add encapsulation type information to the encapsulation frame during encapsulation. This allows the receiving end to determine whether it is virtual or real encapsulation through the encapsulation type information in the encapsulation frame, and use different decapsulation methods during decapsulation.

[0107] Please see Figure 21 This application also provides an electronic device, the electronic device 1100 including: At least one processor 1101; At least one memory 1102 is used to store at least one program; At least one program is executed by at least one processor 1101 to implement the signal transmission method or signal reception method of any of the foregoing embodiments.

[0108] This application also provides a computer program product, including a computer program or computer instructions, which are stored in a computer-readable storage medium. The processor of the electronic device reads the computer program or computer instructions from the computer-readable storage medium and executes the computer program or computer instructions, causing the electronic device to perform the signal transmission method or signal reception method of any of the foregoing embodiments.

[0109] This application also provides a computer-readable storage medium storing computer-executable instructions for performing the signal transmission method or signal reception method of any of the foregoing embodiments.

[0110] It should be understood that in the embodiments of this application, the processor can be a central processing unit (CPU), but it can also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor.

[0111] In addition, the processor may include one or more of the following: a central processing unit (CPU), a baseband processor, a digital signal processor (DSP), a microprocessor unit (MPU), a microcontroller unit (MCU), a graphics processing unit (GPU), a field programmable gate array (FPGA), an artificial intelligence processor (AI processor), or a neural processing unit (NPU).

[0112] It should also be understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of random access memory (RAM) are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced synchronous SDRAM (ESDRAM), synchronous linked DRAM (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0113] The above embodiments can be implemented, in whole or in part, by software, hardware, firmware, or any other combination thereof. When implemented using software, the above embodiments can be implemented, in whole or in part, as a computer program product. A computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more sets of available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium. A semiconductor medium can be a solid-state drive.

[0114] It should be understood that in the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0115] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software 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 this application. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0116] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0117] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. If the above functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory, random access memory, magnetic disks, or optical disks.

[0118] The above is a detailed description of the preferred embodiments of this application. However, this application is not limited to the above embodiments. Those skilled in the art can make various equivalent modifications or substitutions without departing from the spirit of this application. All such equivalent modifications or substitutions are included within the scope defined by the claims of this application.

Claims

1. A signal transmission method, the transmission method comprising: From the original client signal, A first sub-member signals and one second sub-member signal are extracted, where A is a positive integer; Each of the first sub-member signals is mapped to a corresponding first FlexO instance, and each first FlexO instance carries one of the first sub-member signals of the original client signal. The second sub-member signal is mapped to a corresponding second FlexO instance, and each second FlexO instance carries multiple second sub-member signals from different original client signals; Send the first FlexO instance and the second FlexO instance.

2. The sending method according to claim 1, characterized in that, The step of mapping each of the first sub-member signals to the corresponding first FlexO instance includes: Each of the first sub-member signals is mapped to the corresponding first encapsulation frame, and the encapsulation attribute information of the first sub-member signal is added at a preset position in the first encapsulation frame; Each of the first encapsulation frames is mapped to the corresponding first FlexO instance.

3. The sending method according to claim 2, characterized in that, At least one of the first sub-member signals carries the original overhead from the original client signal; The preset position of the first encapsulation frame includes: the overhead position of the first encapsulation frame, or the reserved field position of the original overhead.

4. The sending method according to claim 1, characterized in that, The step of mapping the second sub-member signal to the corresponding second FlexO instance includes: The second sub-member signal is mapped to the corresponding second encapsulation frame, and the encapsulation attribute information of the second sub-member signal is added to the overhead of the second encapsulation frame; The second encapsulated frame is mapped to one or more sub-slots of the corresponding second FlexO instance.

5. The transmission method according to any one of claims 2-4, characterized in that, The encapsulation attribute information includes at least one of the following: Frame information is used to indicate the starting position of the current sub-member signal; Frame sequence information, used to indicate the sequential position of the original client signal to which the current sub-member signal belongs; Sub-member number information, used to indicate the number of the current sub-member signal; The total number of sub-members information is used to indicate the total number of first and second sub-member signals contained in the original customer signal to which the current sub-member signal belongs; Sub-member type information is used to indicate whether the current sub-member signal is the first sub-member signal or the second sub-member signal; Encapsulation type information is used to indicate that the encapsulation attribute information corresponding to the current sub-member signal is located in the reserved field of the original overhead or in the overhead of the encapsulation frame.

6. The sending method according to claim 4, characterized in that, Before sending the second FlexO instance, the method further includes: Add a first value to the overhead of the second FlexO instance. The first value is used to indicate the amount of customer business information contained in the second encapsulation frame.

7. The sending method according to claim 1, characterized in that, The rate of the first FlexO instance is the second rate S2, and the payload of the original client signal includes multiple basic units of equal size; the step of splitting the original client signal into A first sub-member signals and 1 second sub-member signal includes: Based on the preset splitting rules, all the basic units are split into A first basic unit sets and a second basic unit set, and the number of basic units contained in each first basic unit set is determined according to the second rate S2. For each of the first basic unit sets, the basic units in the first basic unit set are combined into a first sub-member signal; The basic units in the second set of basic units are combined to form a second sub-member signal.

8. The sending method according to claim 7, characterized in that, The basic unit is the non-idle sub-time slot in the original customer signal that carries the service.

9. The sending method according to claim 1, characterized in that, The rate of the original client signal is the first rate S1, and the rates of the second FlexO instance and the first FlexO instance are both the second rate S2. A is equal to the integer part obtained by dividing the first rate S1 and the second rate S2.

10. A signal receiving method, the receiving method comprising: Receive at least one first FlexO instance and at least one second FlexO instance, each first FlexO instance carrying a first sub-member signal of an original client signal, and each second FlexO instance carrying a second sub-member signal of the original client signal; Extract the first sub-member signal from the first FlexO instance, and extract the second sub-member signal from the second FlexO instance; The target original customer signal is obtained by merging A first sub-member signals and one second sub-member signal that belong to the target original customer signal, where A is a positive integer.

11. The receiving method according to claim 10, characterized in that, The first FlexO instance carries the sub-member number information corresponding to the first sub-member signal, and the second FlexO instance carries the sub-member number information corresponding to the second sub-member signal. Before merging the A first sub-member signals and one second sub-member signal belonging to the target original client signal to obtain the target original client signal, the receiving method further includes: Based on the sub-member number information, determine the sub-members corresponding to each first sub-member signal and each second sub-member signal.

12. The receiving method according to claim 10, characterized in that, The first FlexO instance carries the frame sequence information corresponding to the first sub-member signal, and the second FlexO instance carries the frame sequence information corresponding to the second sub-member signal. Before merging the A first sub-member signals and one second sub-member signal belonging to the target original client signal to obtain the target original client signal, the receiving method further includes: Based on the frame sequence information, the frame order corresponding to each first sub-member signal and each second sub-member signal is determined.

13. The receiving method according to claim 11, characterized in that, Both the first sub-member signal and the second sub-member signal include multiple basic units. The step of merging A first sub-member signals and one second sub-member signal belonging to the target original customer signal to obtain the target original customer signal includes: Based on the sub-member number information and the preset splitting rules, the position of each basic unit in the target original customer signal is determined, and all the basic units are merged according to their positions to obtain the target original customer signal.

14. The receiving method according to claim 13, characterized in that, The basic unit is a non-idle sub-time slot carrying services in the target original customer signal. All basic units are merged according to their positions, including: Based on the preset idle sub-slot configuration information, determine the location of the idle sub-slot in the target original client signal; Based on the positions of the non-idle sub-time slots and the idle sub-time slots, the non-idle sub-time slots and the idle sub-time slots are merged to obtain the target original client signal.

15. The receiving method according to claim 10, characterized in that, The first FlexO instance includes a first encapsulation frame carrying the first sub-member signal; The receiving method further includes: The overhead in the first encapsulation frame is removed to obtain the first sub-member signal.

16. The receiving method according to claim 10, characterized in that, The first FlexO instance includes a first encapsulation frame carrying the first sub-member signal, at least one of the first encapsulation frames carrying the first sub-member signal carrying the original overhead of the original client signal, and the reserved field of the original overhead carrying the encapsulation attribute information corresponding to the first sub-member signal; Before merging the A first sub-member signals and one second sub-member signal belonging to the target original client signal, the receiving method further includes: For the first sub-member signal carrying the original overhead, the encapsulation attribute information in the reserved field of the original overhead in the first sub-member signal is deleted.

17. The receiving method according to claim 10, characterized in that, The first FlexO instance includes a first encapsulation frame carrying the first sub-member signal, and the first encapsulation frame carries framing information; The step of extracting the first sub-member signal from the first FlexO instance includes: The frame information is identified from the first FlexO instance, the first encapsulated frame is extracted from the first FlexO instance based on the frame information, and the first sub-member signal is extracted from the first encapsulated frame.

18. The receiving method according to claim 10, characterized in that, The second FlexO instance includes a second encapsulation frame carrying the second sub-member signal, the second encapsulation frame carrying framing information; The step of extracting the second sub-member signal from the second FlexO instance includes: The frame information is identified from the second FlexO instance, the second encapsulation frame is extracted from the second FlexO instance based on the frame information, and the second sub-member signal is extracted from the second encapsulation frame.

19. The receiving method according to claim 10, characterized in that, The payload of the second FlexO instance is divided into multiple sub-time slots; the extraction of the second sub-member signal from the second FlexO instance includes: Obtain a first value from the overhead of the second FlexO instance, and determine the amount of customer business information contained in the second sub-member signal based on the first value; Based on the amount of customer business information contained in the second sub-member signal, the second sub-member signal is extracted from one or more of the sub-time slots of the second FlexO instance.

20. An electronic device, characterized in that, include: At least one processor; At least one memory for storing at least one program; At least one of the programs is executed by at least one of the processors to perform the signal transmission method according to any one of claims 1 to 9, or the signal reception method according to any one of claims 10 to 19.

21. A computer-readable storage medium storing computer-executable instructions, characterized in that, The computer-executable instructions are used to execute the signal transmission method according to any one of claims 1 to 9, or the signal reception method according to any one of claims 10 to 19.

22. A computer program product, comprising a computer program or computer instructions, characterized in that, The computer program or the computer instructions are stored in a computer-readable storage medium. The processor of the electronic device reads the computer program or the computer instructions from the computer-readable storage medium and executes the computer program or the computer instructions, causing the electronic device to perform the signal transmission method according to any one of claims 1 to 9, or the signal reception method according to any one of claims 10 to 19.

Images