Business data transmission method, device, related equipment and storage medium

Abstract

The present application discloses a service data transmission method, apparatus, transmitting device, receiving device, and storage medium. The method includes: receiving time division multiplexing (TDM) service data at the transmitting device; mapping the TDM service data to a payload area of ​​a service frame; the service frame comprising an overhead area and a payload area; the overhead area comprising a first pointer; the first pointer being used to indicate the starting position of the service data in the payload area; and transmitting the service frame.

Description

Technical Field

[0001] The present application relates to an optical transmission network, and in particular to a service data transmission method, apparatus, related equipment and storage medium. Background Art

[0002] Currently, Optical Transport Networks (OTN) are widely used in backbone, metro core, and metro aggregation networks, and are now expanding into edge networks, such as access networks. As OTN moves further toward the network edge, it faces increasing demands for carrying services at varying rates. This demand for service carrying is characterized by both the sheer volume of services and the diversity of speeds. In particular, dedicated line services below 1G are expected to proliferate in large numbers, along with a significant number of high-value time-division multiplexing (TDM) services carried by Synchronous Digital Hierarchy (SDH) terminal equipment.

[0003] However, in the related art, there is currently no effective solution for how to carry TDM services in OTN. Summary of the Invention

[0004] To solve related technical problems, the embodiments of the present application provide a business data transmission method, apparatus, related equipment and storage medium.

[0005] The technical solution of the embodiment of the present application is implemented as follows:

[0006] The present invention provides a method for transmitting service data, which is applied to a transmitting device and includes:

[0007] Receive TDM service data;

[0008] Mapping TDM service data to a payload area of ​​a service frame; the service frame comprises an overhead area and a payload area; the overhead area comprises a first pointer; the first pointer is used to indicate a starting position of the service data in the payload area;

[0009] Send service frames.

[0010] In the above solution, the TDM service includes a synchronous transport mode (STM)-N service;

[0011] Receive TDM service data, including:

[0012] Receive STM-N frames;

[0013] Mapping the TDM service data to the payload area of ​​the service frame includes:

[0014] Demapping the received STM-N frame to obtain at least one container;

[0015] Performing local clock synchronization on the at least one container and generating a second pointer; the second pointer is used to indicate a starting position of the at least one container in a payload area of ​​an management unit (AU) or a tributary unit (TU);

[0016] Add the second pointer to the at least one container to obtain at least one AU or TU;

[0017] At least one AU or TU is mapped to the payload area of ​​the service frame.

[0018] In the above solution, demapping the received STM-N frame to obtain at least one container includes:

[0019] Demap the received STM-N frame to obtain at least one AU-4;

[0020] Demapping is performed on at least one AU-4 to obtain at least one VC-4 container.

[0021] In the above solution, demapping the received STM-N frame to obtain at least one container includes:

[0022] Demap the received STM-N frame to obtain at least one AU-4;

[0023] Demapping at least one AU-4 to obtain at least one VC-4 container;

[0024] Demapping is performed on at least one VC-4 container to obtain multiple TU groups (TUGs)-3;

[0025] Demap multiple TUG-3s to obtain multiple TU-3s;

[0026] Demap multiple TU-3s to obtain multiple VC-3 containers;

[0027] Perform clock synchronization on the multiple VC-3 containers and generate the second pointer.

[0028] In the above solution, demapping the received STM-N frame to obtain at least one container includes:

[0029] Demap the received STM-N frame to obtain at least one AU-4;

[0030] Demapping at least one AU-4 to obtain at least one VC-4 container;

[0031] Demapping is performed on at least one VC-4 container to obtain multiple TUG-3s;

[0032] Demap multiple TUG-3s to obtain multiple TUG-2s;

[0033] Demap multiple TUG-2s to obtain multiple TU-12s;

[0034] Demap multiple TU-12s to obtain multiple VC-12 containers;

[0035] Perform clock synchronization on the multiple VC-12 containers and generate the second pointer.

[0036] In the above solution, the STM-N service includes one of the following:

[0037] STM-1;

[0038] STM-4;

[0039] STM-16;

[0040] STM-64.

[0041] In the above solution, the TDM service includes the E1 service;

[0042] The TDM service data includes:

[0043] Receive E1 frames;

[0044] Map the E1 frame into a container;

[0045] Performing local clock synchronization on the container and generating a third pointer; the third pointer indicates a starting position of the container in the payload area of ​​the TU;

[0046] Add the third pointer to the container to obtain a TU;

[0047] The TU is mapped to the payload area of ​​the service frame.

[0048] In the above solution, the service frame includes one of the following:

[0049] Optical service unit OSU frame;

[0050] Optical Data Unit (ODU) frame.

[0051] In the above solution, the length of the first pointer in the overhead area of ​​the service frame is 8 bits.

[0052] The present invention also provides a method for transmitting service data, which is applied to a receiving device and includes:

[0053] Receive a service frame; the service frame includes an overhead area and a payload area; the overhead area includes a first pointer; the first pointer is used to indicate the starting position of the service data in the payload area;

[0054] Demap the received service frame to obtain TDM service data.

[0055] In the above solution, the TDM service includes one of the following:

[0056] STM-N services;

[0057] E1 service.

[0058] In the above solution, the STM-N service includes one of the following:

[0059] STM-1;

[0060] STM-4;

[0061] STM-16;

[0062] STM-64.

[0063] In the above solution, the service frame includes one of the following:

[0064] OSU frame;

[0065] ODU frame.

[0066] In the above solution, the length of the first pointer in the overhead area of ​​the service frame is 8 bits. The embodiment of the present application also provides a service data transmission device, including:

[0067] A first receiving unit, configured to receive TDM service data;

[0068] A first processing unit is configured to map TDM service data to a payload area of ​​a service frame; the service frame comprises an overhead area and a payload area; the overhead area comprises a first pointer; the first pointer is configured to indicate a starting position of the service data in the payload area;

[0069] The sending unit is used to send service frames.

[0070] The present invention also provides a device for transmitting service data, including:

[0071] A second receiving unit is configured to receive a service frame; the service frame comprises an overhead area and a payload area; the overhead area comprises a first pointer; the first pointer is configured to indicate a starting position of service data in the payload area;

[0072] The second processing unit is used to demap the received service frame to obtain TDM service data.

[0073] The embodiment of the present application further provides a sending end device, comprising: a first processor and a first communication interface; wherein,

[0074] The first communication interface is used to receive TDM service data;

[0075] The first processor is configured to map the TDM service data to a payload area of ​​a service frame; the service frame comprises an overhead area and a payload area; the overhead area comprises a first pointer; the first pointer is configured to indicate a starting position of the service data in the payload area;

[0076] The first communication interface is also used to send service frames.

[0077] The present invention further provides a receiving device, including:

[0078] The second communication interface is configured to receive a service frame; the service frame comprises an overhead area and a payload area; the overhead area comprises a first pointer; the first pointer is configured to indicate a starting position of service data in the payload area;

[0079] The second processor is used to demap the received service frame to obtain TDM service data.

[0080] The embodiment of the present application further provides a transmitting end device, comprising: a first processor and a first memory for storing a computer program that can be run on the processor,

[0081] The first processor is configured to execute the steps of any one of the above-mentioned methods on the sending end device side when running the computer program.

[0082] The embodiment of the present application further provides a receiving end device, comprising: a second processor and a second memory for storing a computer program that can be run on the processor,

[0083] The second processor is configured to execute the steps of any one of the above-mentioned methods on the receiving end device side when running the computer program.

[0084] An embodiment of the present application also provides a storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of any of the above-mentioned methods on the sending end device side, or implements the steps of any of the above-mentioned methods on the receiving end device side.

[0085] The service data transmission method, apparatus, related equipment, and storage medium provided in the embodiments of the present application are as follows: a transmitting end device receives TDM service data; maps the TDM service data to the payload area of ​​a service frame and transmits the service frame; the service frame includes an overhead area and a payload area; the overhead area includes a first pointer; the first pointer is used to indicate the starting position of the service data in the payload area; and after receiving the service frame, the receiving end device demaps the received service frame to obtain the TDM service data. In the embodiments of the present application, the TDM service is mapped to the service frame, the service frame includes an overhead area and a payload area, pointer positioning information is set in the overhead area, the pointer positioning information is used to indicate the starting position of the service in the payload, and the TDM service is placed in the payload, thereby realizing the transmission of the TDM service in the network. BRIEF DESCRIPTION OF THE DRAWINGS

[0086] Figure 1 This is a schematic diagram of an OSU frame format in the related art;

[0087] Figure 2 This is another OSU frame format diagram in the related art;

[0088] Figure 3 This is a flowchart of a method for transmitting business data according to an embodiment of the present application;

[0089] Figure 4 This is a schematic diagram of the TDM service data processing flow in an embodiment of the present application;

[0090] Figure 5 This is a schematic diagram of an OSU frame format according to an embodiment of the present application;

[0091] Figure 6 This is a schematic diagram of the mapping process of a single VC in an embodiment of the present application;

[0092] Figure 7 This is a schematic diagram of the mapping process of multiple VCs according to an embodiment of the present application;

[0093] Figure 8 This is a flowchart of another method for transmitting business data according to an embodiment of the present application;

[0094] Figure 9 This is a flowchart of a method for transmitting business data according to a third embodiment of the present application;

[0095] Figure 10 This is a structural diagram of a business data transmission device according to an embodiment of the present application;

[0096] Figure 11 This is a structural diagram of another device for transmitting business data according to an embodiment of the present application;

[0097] Figure 12This is a schematic diagram of the structure of the sending end device according to an embodiment of the present application;

[0098] Figure 13 This is a schematic diagram of the receiving device structure according to an embodiment of the present application;

[0099] Figure 14 This is a schematic diagram of the business data transmission system structure of an embodiment of the present application. DETAILED DESCRIPTION

[0100] The present application will be described in further detail below with reference to the accompanying drawings and embodiments.

[0101] When using 1.25G granularity pipes to carry services with a rate lower than 1G, bandwidth waste is significant. Based on this, a technical solution is proposed to use OSUs to transport services with a rate lower than 1G. Specifically, service data is carried in OSU frames, which are then directly mapped and multiplexed into m payload blocks per transmission cycle of an Optical Data Unit-k (ODUk) (rate greater than 1G), which are then aggregated and transmitted via the ODUk.

[0102] The OSU frame structure is 192 bytes long and includes an overhead area and a payload area. The overhead area is a fixed 7 bytes, and the payload area is a fixed 185 bytes. The OSU bit rate can be any value of n*minimum basic rate (for example, assuming the minimum basic rate is 2 Mbps, the OSU bit rate is n*2 Mbps), where the specific value of n depends on the customer's service rate.

[0103] The ODUk payload area is divided into consecutive payload blocks, each of which is also 192 bytes in size. Every P consecutive payload blocks is called a transmission cycle, where the value of P depends on the ODUk payload rate and the minimum basic rate: P = ODUk payload rate / minimum basic rate. The minimum basic rate can be a preset value, such as 2M or 10M. This solves the problem of arbitrary rate granularity through OSU and direct mapping of payload blocks, and improves bandwidth utilization to a certain extent compared to the traditional 1.25G granularity.

[0104] In the 192-byte OSU frame, the overhead size is 7 bytes and the payload size is 185 bytes. In the related art, for the OSU frame, the bearer structure of the packet (PKT) service (bandwidth can be varied) is defined (e.g. Figure 1 As shown) and the bearer structure of the constant bit rate (CBR, Constant Bit Rate) service (fixed rate) (as shown) Figure 2 As shown), the bearer structure for TDM services is not defined.

[0105] In addition, for TDM services, if only simple transparent transmission is required, CBR service frames can be used for transmission. However, there is currently no effective bearer solution for handling containers of various granularities (such as individual VC-4, VC-3, or VC-12 particles) in TDM services.

[0106] In addition, in the related art, the components of the STM-N signal, namely various types of containers such as VC-4, VC-3 or VC-12, need to go in different directions, that is, reach different destinations. There is no effective solution to this problem.

[0107] Based on this, in various embodiments of the present application, the TDM service is mapped into a service frame, which consists of an overhead area and a payload area. Pointer positioning information is set in the overhead area. The pointer positioning information is used to represent the starting position of the service in the payload, and the TDM service is placed in the payload, thereby realizing the transmission of the TDM service in the network.

[0108] The embodiment of the present application provides a service data transmission method, which is applied to a sending end device, such as Figure 3 As shown, the method includes the following steps:

[0109] Step 301: Receive TDM service data;

[0110] Step 302: Mapping the TDM service data to the payload area of ​​the service frame; the service frame includes an overhead area and a payload area; the overhead area includes a first pointer; the first pointer is used to indicate the starting position of the service data in the payload area;

[0111] Step 303: Send the service frame.

[0112] In step 303, the transmitting device sends a service frame to the receiving device. In actual application, the transmitting device may also be referred to as a source device; and correspondingly, the receiving device may also be referred to as a sink.

[0113] The transmission of service data in the embodiment of the present application refers to the transmission of service data in an optical network (such as OTN). An OTN is usually composed of multiple OTN devices connected by optical fibers. Therefore, the transmitting end device and the receiving end device can specifically both be OTN devices.

[0114] In actual application, the TDM service may include an STM-N service and an E1 service.

[0115] Wherein, when the TDM service includes an STM-N service, in step 301, the transmitting end device receives an STM-N frame;

[0116] Accordingly, in step 302,

[0117] The transmitting end device demaps the received STM-N frame to obtain at least one container;

[0118] Performing local clock synchronization on the at least one container and generating a second pointer; the second pointer is used to indicate a starting position of the at least one container in the payload area of ​​the AU or TU;

[0119] Add the second pointer to the at least one container to obtain at least one AU or TU;

[0120] At least one AU or TU is mapped to the payload area of ​​the service frame.

[0121] Among them, AU and TU can be called transmission unit frames.

[0122] The STM-N frame structure has the following characteristics:

[0123] (1) It consists of 9 rows × 270 columns (bytes), each byte has 8 bits, the period of one frame is 125 μs, and the frame frequency is 8 kHz (8000 frames per second).

[0124] (2) STM-1 (i.e., N is 1) is the most basic structure of SDH frames. Each frame period is 125 μs, with 19440 bits (9 × 270 × 8), and a transmission rate of 19440 × 8000 bits = 155520 kbit / s.

[0125] (3) STM-N is composed of N STM-1s synchronously multiplexed by byte interleaving, so its rate is N times that of STM-1;

[0126] (4) The SDH frame consists of three parts: the payload area, the administration unit pointer (AU-PTR), and the section overhead (SOH). The TDM service (i.e., data) is encapsulated in a VC-4 container. The AU-PTR is added to the VC-4 container to form the AU-4. The AU-PTR is used to indicate the location of each VC-4 payload in the STM-N. The regeneration section overhead (RSOH) and multiplexing section overhead (MSOH) are then added to the AU-4 to form an STM-1 frame structure. If there are multiple consecutive VC-4s, they can be cascaded together to form a VC-4-4c, forming an STM-4 frame, or a VC-4-16c, forming an STM-16 frame, or a VC-4-64c, forming an STM-64 frame. After receiving the STM-N frame, the transmitting device will first terminate the section overhead, RSOH, and MSOH, strip out the AU-4, and then perform subsequent processing.

[0127] Therefore, in the embodiment of the present application, the STM-N service includes one of the following:

[0128] STM-1;

[0129] STM-4;

[0130] STM-16;

[0131] STM-64.

[0132] An STM-N frame consists of one or more AU-4s (i.e., it contains one or more AU-4s). Each AU-4 may consist of one or multiple VC-4 containers (i.e., one AU-4 may contain one or multiple VC-4 containers). Each VC-4 container may consist of multiple VC-3 containers or VC-12 containers (i.e., one VC-4 container may contain multiple VC-3 containers or multiple VC-12 containers). Each container may carry signals from different users and reach receiving devices with different destinations. Therefore, the transmitting device distinguishes different AU-4s in the STM frame based on the destination address, then loads VC containers with the same destination address into one or more service frames, distinguishes them by tributary port numbers (TPNs), and then continues subsequent processing based on the distinguished AU-4s.

[0133] Different types of VC containers in AU-4 result in different containers being demapped, and the corresponding transmission unit frames are also different. The following processing methods are available:

[0134] In the first case, the AU-4 only includes a VC-4 container. In this case, the transmitting end device demaps the received STM-N frame to obtain at least one AU-4. The at least one AU-4 is demapped to obtain at least one VC-4 container. The second pointer (i.e., AU-PTR) is added to the at least one VC-4 container to obtain at least one AU-4 frame. Here, the second pointer is used to locate the VC-4 container in the newly obtained AU-4 frame.

[0135] In the second case, the AU-4 contains a VC-4 container, and the VC-4 container also contains a VC-3 container. In this case, the transmitting end device demaps the received STM-N frame to obtain at least one AU-4; demaps the at least one AU-4 to obtain at least one VC-4 container; demaps the at least one VC-4 container to obtain multiple TUG-3s; demaps the multiple TUG-3s to obtain multiple TU-3s; demaps the multiple TU-3s to obtain multiple VC-3 containers; clocks are synchronized on the multiple VC-3 containers and a second pointer (TU-PTR) is generated; the multiple VC-3 containers are added with the second pointer to obtain multiple TU-3 frames; the second pointer is used to locate the VC-3 container in the newly obtained TU-3 frame.

[0136] In the third case, the AU-4 contains a VC-4 container, the VC-4 container further contains a VC-3 container, and the VC-3 container further contains a VC-12 container; at this time, the transmitting end device demaps the received STM-N frame to obtain at least one AU-4; demaps at least one AU-4 to obtain at least one VC-4 container; demaps at least one VC-4 container to obtain multiple TUG-3s; demaps multiple TUG-3s to obtain multiple TUG-2s; demaps multiple TUG-2s to obtain multiple TU-12s; demaps multiple TU-12s to obtain multiple VC-12 containers; clocks of the multiple VC-12 containers are synchronized, and the second pointer (TU-PTR) is generated; the second pointer is added to the multiple VC-12 containers to obtain multiple TU-12 frames; here, the second pointer is used to locate the VC-12 container in the newly obtained TU-12 frame.

[0137] From the above description, it can be seen that Figure 4 As shown in the figure, different VC container particles have different mapping processing methods:

[0138] (1) VC-4 particles: First, the transmitting device strips the AU-4 from the STM-N frame to obtain N AU-4s. Each AU-4 is demapped to restore it to a VC-4 (155 Mbit / s) particle (obtaining N VC-4 containers). Then, the multiple VC-4 particles are synchronized with the local clock, and a new AU-PTR is regenerated to correspond to each VC-4 container and generate a new AU-4. Multiple (M) AU-4s are sequentially arranged and mapped into the service frame.

[0139] 2) VC-3 particles: First, the transmitting device strips the AU-4 from the STM-N frame to obtain N AU-4s. Each AU-4 is demapped to restore it to a VC-4 particle. One VC-4 is then decomposed into three TUG-3s, and one TUG-3 is restored to a VC-3 container (at a rate of 45 Mbit / s). Multiple (K) VC-3 particles are synchronized with the local clock, and a new TU-PTR is regenerated to correspond to each VC-3 container. A new TU-3 is generated, and the multiple (K) TU-3s are sequentially arranged and mapped into the service frame.

[0140] 3) VC-12 particles: First, the transmitting device strips the AU-4 from the STM-N frame to obtain N AU-4s. Each AU-4 is demapped to restore it to a VC-4 particle. One VC-4 is then decomposed into three TUG-3s, and one TUG-3 is further restored to 3*7 TUG-2s. Each TUG-2 is then decomposed into three TU-12s, and each TU-12 is then restored to a VC-12 container (at a rate of 2 Mbit / s). Multiple (Q) VC-12 particles are synchronized with the local clock, and a new TU-PTR is regenerated to correspond to each VC-12 container. A new TU-12 is generated, and the multiple (Q) TU-12s are arranged sequentially and mapped into the service frame.

[0141] When the TEM service includes an E1 service (rate is 2 Mbit / s), in step 301, the transmitting end device receives an E1 frame;

[0142] Accordingly, in step 302,

[0143] The sending end device maps the E1 frame into a container;

[0144] Performing local clock synchronization on the container and generating a third pointer; the third pointer indicates a starting position of the container in the payload area of ​​the TU;

[0145] Add the third pointer to the container to obtain a TU;

[0146] The TU is mapped to the payload area of ​​the service frame.

[0147] In actual application, in related technologies, the rate of the E1 service is 2 Mbit / s. Therefore, the container corresponding to the E1 frame may be a VC-12 container, and accordingly, the TU may be a TU-12 frame.

[0148] like Figure 4As shown in FIG, for E1 service signals, the mapping processing method includes: directly encapsulating the E1 frame into a VC-12 container, regenerating a new TU-PTR after local clock synchronization, generating a new TU-12, and then mapping the TU-12 into the service frame.

[0149] In actual application, the service frame may be an OSU frame (which may be called a TDM service frame) or an ODU frame.

[0150] Among them, such as Figure 5 As shown in the figure, the OSU frame for TDM services includes an overhead area and a payload area (185 bytes). The overhead area contains a pointer indicating the AU-4, TU-3, or TU-12 service, namely the first pointer, which can be called a VC-PTR. The overhead area also contains other overhead. While maintaining the original operation, maintenance and management (OAM) functions of the OSU frame, the OSU frame's multi-service carrying capacity is improved to meet the efficient carrying requirements of specific application scenarios or specific services.

[0151] The following is a detailed description of the overhead information in the overhead area.

[0152] VC-PTR: 8 bits (i.e., the length of the first pointer in the overhead area of ​​the service frame is 8 bits), with a value of 0 to 185. It is used to indicate the initial byte position of the AU-4, TU-3, or TU-12 service in the OSU payload area. Since the payload area is 185 bytes, 8 bits can represent 256 positions, which can cover the position information of 185 bytes.

[0153] The other overheads include: version (VER), TPN, service type, general overhead, PLn, sequence number (SQ) and cyclic redundancy check (CRC) (specifically CRC8).

[0154] VER: 2 bits, version number, used to identify the OSU frame version number,

[0155] TPN: 12 bits, used to identify OSU services. When mapping one or more OSU services to an OPU bearer container, different OSU services add their own TPNs in their respective OSU frames. The receiver can distinguish different OSU services based on the TPNs carried in each OSU frame.

[0156] Service type: 3 bits, used to identify the OSU frame type (FT). Different values ​​of FT are used to distinguish between OSU basic frames and OSU extended frames.

[0157] For example, as shown in Table 1, the service type may include three OSU frame types, wherein OSU (PKT) is used to carry packet PKT services, OSU (CBR) is used to carry CBR services with a fixed bit rate, and OSU (TDM) is used to carry TDM services.

[0158]

[0159] Table 1

[0160] General overhead: 18 bits, including but not limited to path monitoring (PM), TCM and other overhead information.

[0161] PLn (n=1, 2, 3): 3 bits, used to indicate the payload length occupied by the TDM service carried in the payload area of ​​the OSU frame, specifically indicating the payload length of three consecutive OSU frames. Among these 3 bits, PL1 indicates the payload length (PL) occupied by the TDM service carried in the payload area of ​​the current OSU frame, PL2 indicates the payload length occupied by the TDM service carried in the payload area of ​​the previous OSU frame, and PL3 indicates the payload length occupied by the TDM service carried in the payload area of ​​the previous two OSU frames.

[0162] SQ: 2 bits, used to provide OSU frame loss monitoring for end-to-end OSU paths. SQ is generated when the source-side TDM service is mapped to the OSU frame. The value ranges from 0 to 3 and is transparently transmitted when the OSU frame passes through the intermediate node. The destination identifies SQ before demapping the TDM service from the OSU frame, and determines whether there is OSU frame loss in the end-to-end OSU path based on the value of SQ. For example, the source sends 0, 1, 2, 3 continuously and periodically. If the destination receives 0, 1, 2, or 0, 1, 3, or 0, 1, or 2, 3, it will be determined as frame loss. In the event of OSU destination frame loss, a maximum of 2 OSU frames can be continuously compensated to ensure the performance of the destination TDM service.

[0163] CRC8: 8 bits, used for cyclic redundancy check of the overhead interval information (bytes 1 to 6) of the OSU frame. The CRC8 check polynomial includes but is not limited to G(x) = x8 + x2 + x + 1, and the initial value is all 1s.

[0164] In actual application, when a single VC carrying a destination address exists in an STM-N frame, the VC signal (i.e., the VC container mentioned above) is first extracted from the STM-N frame and mapped into AU-4, TUG-3, or TU-12 (generated using a synchronous clock). The VC_PTR indicates the starting position of the corresponding start byte of the AU-4, TUG-3, or TU-12 in the payload area of ​​the service frame, as shown in the following example: Figure 6 shown.

[0165] When multiple VCs with the same destination address are carried in an STM-N frame, first extract p (p is an integer greater than or equal to 2) VC signals from the STM-N frame, map the p VC signals to p AU-4, TUG-3, or TU-12 frames (generated using a synchronous clock), and interleave the p AU-4, TUG-3, or TU-12 frame bytes into one signal. The VC_PTR indicates the starting position of the H1 / V1 byte corresponding to the first AU-4, TUG-3, or TU-12 in the multiplexed signal in the OSU payload area, as shown in the following example: Figure 7 shown.

[0166] When the service frame is an ODU frame, the TDM service signal is mapped to the OSU frame payload area in the above manner, and then multiplexed and mapped to the optical path payload unit (OPU), and the corresponding overhead is added to the formed OPU to form an ODU.

[0167] Accordingly, the embodiment of the present application also provides a service data transmission method, which is applied to a receiving device, such as Figure 8 As shown, the method includes the following steps:

[0168] Step 801: Receive a service frame; the service frame includes an overhead area and a payload area; the overhead area includes a first pointer; the first pointer is used to indicate the starting position of the service data in the payload area;

[0169] Step 802: Demap the received service frame to obtain TDM service data.

[0170] In actual application, during the demapping process of the received service frames, the receiving end device will first restore the service frames to VC particles. When the VC particles are sent out through the SDH interface, they will become STM-N signals or E1 signals.

[0171] The specific process of demapping the received service frame is the inverse process of the above mapping process, and the specific process of demapping the received service frame will not be described in detail here.

[0172] The present application also provides a method for transmitting business data. Figure 9 As shown, the method includes the following steps:

[0173] Step 901: The transmitting end device receives TDM service data; maps the TDM service data to the payload area of ​​the service frame; the service frame includes an overhead area and a payload area; the overhead area includes a first pointer; the first pointer is used to indicate the starting position of the service data in the payload area;

[0174] Step 902: The transmitting end device sends a service frame;

[0175] Step 903: After receiving the service frame, the receiving end device demaps the received service frame to obtain TDM service data.

[0176] The service data transmission method provided in the embodiment of the present application is as follows: the sending end device receives TDM service data; maps the TDM service data to the payload area of ​​the service frame and sends the service frame; the service frame includes an overhead area and a payload area; the overhead area includes a first pointer; the first pointer is used to indicate the starting position of the service data in the payload area; and after the receiving end device receives the service frame, it demaps the received service frame to obtain the TDM service data. In the embodiment of the present application, the TDM service is mapped to the service frame, and the service frame includes an overhead area and a payload area. Pointer positioning information is set in the overhead area. The pointer positioning information is used to characterize the starting position of the service in the payload, and the TDM service is placed in the payload, thereby realizing the transmission of the TDM service in the network. In addition, this solution can also be applied to the carrying requirements of other small-grained service transmission.

[0177] In addition, when the service frame contains an OSU frame, based on the OSU frame structure, by introducing TDM service processing, the TDM attributes are retained according to the preset processing mechanism. On the basis of maintaining the original OAM capabilities of the OSU, the OSU can achieve complete transmission of TDM services. Among them, for STM-N services, by decomposing the VC granular services in the STM-N signal and then mapping them to the OSU for transmission (there is a situation where the STM-N signal is not fully filled with services), only the VC granular services with services are transmitted, avoiding the transmission of a complete STM-N signal. In this way, the demand for efficient carrying of TDM services can be met.

[0178] In order to implement the method of the embodiment of the present application, the embodiment of the present application also provides a data transmission device, which is set on the sending end device, such as Figure 10 As shown, the device includes:

[0179] The first receiving unit 1001 is configured to receive TDM service data;

[0180] The first processing unit 1002 is configured to map TDM service data to a payload area of ​​a service frame; the service frame includes an overhead area and a payload area; the overhead area includes a first pointer; the first pointer is used to indicate a starting position of the service data in the payload area;

[0181] The sending unit 1003 is used to send a service frame.

[0182] In one embodiment, the TDM service includes an STM-N service;

[0183] The first receiving unit 1001 is specifically configured to receive an STM-N frame;

[0184] The first processing unit 1002 is configured to:

[0185] Demapping the received STM-N frame to obtain at least one container;

[0186] Performing local clock synchronization on the at least one container and generating a second pointer; the second pointer is used to indicate a starting position of the at least one container in a payload area of ​​the AU or TU;

[0187] Add the second pointer to the at least one container to obtain at least one AU or TU;

[0188] At least one AU or TU is mapped to the payload area of ​​the service frame.

[0189] Here, in one embodiment, demapping the received STM-N frame to obtain at least one container includes:

[0190] The first processing unit 1002 demaps the received STM-N frame to obtain at least one AU-4;

[0191] The first processing unit 1002 demaps at least one AU-4 to obtain at least one VC-4 container.

[0192] In one embodiment, demapping the received STM-N frame to obtain at least one container includes:

[0193] The first processing unit 1002 demaps the received STM-N frame to obtain at least one AU-4;

[0194] The first processing unit 1002 demaps at least one AU-4 to obtain at least one VC-4 container;

[0195] The first processing unit 1002 demaps at least one VC-4 container to obtain a plurality of TUG-3s;

[0196] The first processing unit 1002 demaps the multiple TUG-3s to obtain multiple TU-3s;

[0197] The first processing unit 1002 demaps the multiple TU-3s to obtain multiple VC-3 containers;

[0198] The first processing unit 1002 performs clock synchronization on the multiple VC-3 containers and generates the second pointer.

[0199] In one embodiment, demapping the received STM-N frame to obtain at least one container includes:

[0200] The first processing unit 1002 demaps the received STM-N frame to obtain at least one AU-4;

[0201] The first processing unit 1002 demaps at least one AU-4 to obtain at least one VC-4 container;

[0202] The first processing unit 1002 demaps at least one VC-4 container to obtain a plurality of TUG-3s;

[0203] The first processing unit 1002 demaps the multiple TUG-3s to obtain multiple TUG-2s;

[0204] The first processing unit 1002 demaps multiple TUG-2s to obtain multiple TU-12s;

[0205] The first processing unit 1002 demaps the multiple TU-12s to obtain multiple VC-12 containers;

[0206] The first processing unit 1002 performs clock synchronization on the multiple VC-12 containers and generates the second pointer.

[0207] In one embodiment, the TDM service includes an E1 service;

[0208] The first receiving unit 1001 is specifically configured to receive an E1 frame;

[0209] The first processing unit 1002 is specifically configured to:

[0210] Map the E1 frame into a container;

[0211] Performing local clock synchronization on the container and generating a third pointer; the third pointer indicates a starting position of the container in the payload area of ​​the TU;

[0212] Add the third pointer to the container to obtain a TU;

[0213] The TU is mapped to the payload area of ​​the service frame.

[0214] In actual application, the first receiving unit 1001 and the sending unit 1003 can be implemented by a communication interface in the business data transmission device; the first processing unit 1002 can be implemented by a processor in the business data transmission device.

[0215] In order to implement the method of the receiving end device side of the embodiment of the present application, the embodiment of the present application also provides a data transmission device, which is set on the receiving end device, such as Figure 11 As shown, the device includes:

[0216] The second receiving unit 1101 is configured to receive a service frame; the service frame comprises an overhead area and a payload area; the overhead area comprises a first pointer; the first pointer is configured to indicate a starting position of service data in the payload area;

[0217] The second processing unit 1102 is configured to demap the received service frame to obtain TDM service data.

[0218] In actual application, the second receiving unit 1101 can be implemented by a communication interface in the business data transmission device; the second processing unit 1102 can be implemented by a processor in the business data transmission device.

[0219] It should be noted that the business data transmission device provided in the above embodiment only uses the division of the above program modules as an example to illustrate when performing business data transmission. In actual applications, the above processing can be assigned to different program modules as needed, that is, the internal structure of the device can be divided into different program modules to complete all or part of the processing described above. In addition, the business data transmission device provided in the above embodiment and the business data transmission method embodiment are of the same concept. The specific implementation process is detailed in the method embodiment and will not be repeated here.

[0220] Based on the hardware implementation of the above program modules, and in order to implement the method of the transmitting end device side of the embodiment of the present application, the embodiment of the present application also provides a transmitting end device, such as Figure 12 As shown, the sending end device 1200 includes:

[0221] The first communication interface 1201 is capable of exchanging information with a receiving device;

[0222] The first processor 1202 is connected to the first communication interface 1201 to implement information interaction with the receiving device, and is used to execute the methods provided by one or more technical solutions on the sending device side when running the computer program; and the computer program is stored in the first memory 1203.

[0223] Specifically, the first communication interface 1201 is used to receive TDM service data;

[0224] The first processor 1202 is configured to map the TDM service data to a payload area of ​​a service frame; the service frame includes an overhead area and a payload area; the overhead area includes a first pointer; the first pointer is used to indicate a starting position of the service data in the payload area;

[0225] The first communication interface 1201 is also used to send service frames.

[0226] Wherein, in one embodiment, the TDM service includes an STM-N service;

[0227] The first communication interface 1201 is specifically configured to receive STM-N frames;

[0228] The first processor 1202 is configured to:

[0229] Demapping the received STM-N frame to obtain at least one container;

[0230] Performing local clock synchronization on the at least one container and generating a second pointer; the second pointer is used to indicate a starting position of the at least one container in a payload area of ​​the AU or TU;

[0231] Add the second pointer to the at least one container to obtain at least one AU or TU;

[0232] At least one AU or TU is mapped to the payload area of ​​the service frame.

[0233] Here, in one embodiment, demapping the received STM-N frame to obtain at least one container includes:

[0234] The first processor 1202 demaps the received STM-N frame to obtain at least one AU-4;

[0235] The first processor 1202 demaps at least one AU-4 to obtain at least one VC-4 container.

[0236] In one embodiment, demapping the received STM-N frame to obtain at least one container includes:

[0237] The first processor 1202 demaps the received STM-N frame to obtain at least one AU-4;

[0238] The first processor 1202 demaps at least one AU-4 to obtain at least one VC-4 container;

[0239] The first processor 1202 demaps at least one VC-4 container to obtain a plurality of TUG-3s;

[0240] The first processor 1202 demaps the multiple TUG-3s to obtain multiple TU-3s;

[0241] The first processor 1202 demaps the multiple TU-3s to obtain multiple VC-3 containers;

[0242] The first processor 1202 performs clock synchronization on the multiple VC-3 containers and generates the second pointer.

[0243] In one embodiment, demapping the received STM-N frame to obtain at least one container includes:

[0244] The first processor 1202 demaps the received STM-N frame to obtain at least one AU-4;

[0245] The first processor 1202 demaps at least one AU-4 to obtain at least one VC-4 container;

[0246] The first processor 1202 demaps at least one VC-4 container to obtain a plurality of TUG-3s;

[0247] The first processor 1202 demaps the multiple TUG-3s to obtain multiple TUG-2s;

[0248] The first processor 1202 demaps the multiple TUG-2s to obtain multiple TU-12s;

[0249] The first processor 1202 demaps the multiple TU-12s to obtain multiple VC-12 containers;

[0250] The first processor 1202 performs clock synchronization on the multiple VC-12 containers and generates the second pointer.

[0251] In one embodiment, the TDM service includes an E1 service;

[0252] The first communication interface 1201 is specifically configured to receive E1 frames;

[0253] The first processor 1202 is specifically configured to:

[0254] Map the E1 frame into a container;

[0255] Performing local clock synchronization on the container and generating a third pointer; the third pointer indicates a starting position of the container in the payload area of ​​the TU;

[0256] Add the third pointer to the container to obtain a TU;

[0257] The TU is mapped to the payload area of ​​the service frame.

[0258] It should be noted that the specific processing process of the first processor 1202 and the first communication interface 1201 can be understood by referring to the above method.

[0259] Of course, in actual application, the various components in the transmitting end device 1200 are coupled together through the bus system 12004. It can be understood that the bus system 1204 is used to realize the connection and communication between these components. In addition to the data bus, the bus system 1204 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clarity, Figure 12 Various buses are labeled as bus system 1204.

[0260] The first memory 1203 in the embodiment of the present application is used to store various types of data to support the operation of the sending end device 1200. Examples of such data include: any computer program used to operate on the sending end device 1200.

[0261] The methods disclosed in the above embodiments of the present application can be applied to the first processor 1202 or implemented by the first processor 1202. The first processor 1202 may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method can be completed by an integrated logic circuit of the hardware in the first processor 1202 or by instructions in the form of software. The above first processor 1202 may be a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The first processor 1202 can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. A general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium located in the first memory 1203. The first processor 1202 reads the information in the first memory 1203 and completes the steps of the above method in combination with its hardware.

[0262] In an exemplary embodiment, the sending device 1200 can be implemented by one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontrollers (MCUs), microprocessors, or other electronic components to execute the aforementioned method.

[0263] Based on the hardware implementation of the above program modules, and in order to implement the method of the receiving device side of the embodiment of the present application, the embodiment of the present application also provides a receiving device, such as Figure 13 As shown, the receiving end device 1300 includes:

[0264] The second communication interface 1301 is capable of exchanging information with the sending end device;

[0265] The second processor 1302 is connected to the second communication interface 1301 to implement information interaction with the sending device, and is used to execute the methods provided by one or more technical solutions on the receiving device side when running the computer program; and the computer program is stored in the second memory 1303.

[0266] Specifically, the second communication interface 1301 is used to receive a service frame; the service frame includes an overhead area and a payload area; the overhead area includes a first pointer; the first pointer is used to indicate the starting position of the service data in the payload area;

[0267] The second processor 1302 is configured to demap the received service frame to obtain TDM service data.

[0268] It should be noted that the specific processing procedures of the second processor 1302 and the second communication interface 1301 can be understood by referring to the above method.

[0269] Of course, in actual application, the various components in the receiving end device 1300 are coupled together through the bus system 1304. It can be understood that the bus system 1304 is used to realize the connection and communication between these components. In addition to the data bus, the bus system 1304 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clarity, Figure 13 Various buses are labeled as bus system 1304.

[0270] The second memory 1303 in the embodiment of the present application is used to store various types of data to support the operation of the receiving device 1300. Examples of such data include: any computer program used to operate on the receiving device 1300.

[0271] The methods disclosed in the above embodiments of the present application can be applied to or implemented by the second processor 1302. The second processor 1302 may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method can be completed by hardware integrated logic circuits or software instructions in the second processor 1302. The above second processor 1302 may be a general-purpose processor, a DSP, or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, etc. The second processor 1302 can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. A general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of the present application can be directly implemented and executed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The software module may be located in a storage medium located in the second memory 1303. The second processor 1302 reads the information in the second memory 1303 and, in conjunction with its hardware, completes the steps of the above method.

[0272] In an exemplary embodiment, the receiving device 1300 may be implemented by one or more ASICs, DSPs, PLDs, CPLDs, FPGAs, general-purpose processors, controllers, MCUs, Microprocessors, or other electronic components to perform the aforementioned method.

[0273] It can be understood that the memory (first memory 1203, second memory 1303) of the embodiment of the present application can be a volatile memory or a non-volatile memory, and can also include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic random access memory (FRAM), a flash memory, a magnetic surface memory, an optical disc, or a compact disc read-only memory (CD-ROM); the magnetic surface memory can be a magnetic disk memory or a tape memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), synchronous static random access memory (SSRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct rambus random access memory (DRRAM).The memories described in the embodiments of this application are intended to include, but are not limited to, these and any other suitable types of memories.

[0274] In order to implement the method of the embodiment of the present application, the embodiment of the present application also provides a business data transmission system, such as Figure 14 As shown, the system includes: a sending end device 1401 and a receiving end device 1402.

[0275] It should be noted that the specific processing procedures of the sending end device 1401 and the receiving end device 1402 have been described in detail above and will not be repeated here.

[0276] In an exemplary embodiment, the present application also provides a storage medium, namely a computer storage medium, specifically a computer-readable storage medium, which includes, for example, a first memory 1203 storing a computer program. The computer program can be executed by the first processor 1202 of the transmitting device 1200 to complete the steps of the aforementioned transmitting device-side method. For another example, the present application also includes a second memory 1303 storing a computer program. The computer program can be executed by the second processor 1302 of the receiving device 1300 to complete the steps of the aforementioned receiving device-side method. The computer-readable storage medium can be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface storage, optical disk, or CD-ROM.

[0277] It should be noted that: "first", "second", etc. are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0278] In addition, the technical solutions described in the embodiments of the present application can be arbitrarily combined without conflict.

[0279] The above description is merely a preferred embodiment of the present application and is not intended to limit the scope of protection of the present application.

Claims

1. A business data transmission method, characterized in that: Applicable to the sending end device, including: Receive time division multiplexing TDM service data; Mapping TDM service data to a payload area of ​​a service frame; the service frame comprises an overhead area and a payload area; the overhead area comprises a first pointer; the first pointer is used to indicate a starting position of the service data in the payload area; Send business frame; among them, The TDM service includes a synchronous transport mode STM-N service, and mapping the TDM service data to the payload area of ​​the service frame includes: Demapping the STM-N frame to obtain at least one container; Performing local clock synchronization on the at least one container and generating a second pointer; the second pointer is used to indicate a starting position of the at least one container in a payload area of ​​the management unit AU or the tributary unit TU; Add the second pointer to the at least one container to obtain at least one AU or TU; Mapping at least one AU or TU to the payload area of ​​the service frame; The TDM service includes an E1 service, and mapping the TDM service data to the payload area of ​​the service frame includes: Map the E1 frame into a container; Performing local clock synchronization on the container and generating a third pointer; the third pointer indicates a starting position of the container in the payload area of ​​the TU; Add the third pointer to the container to obtain a TU; The TU is mapped to the payload area of ​​the service frame.

2. The method according to claim 1, characterized in that The TDM service includes an STM-N service; and the receiving of TDM service data includes: Receive STM-N frames.

3. The method according to claim 1, characterized in that Demapping the STM-N frame to obtain at least one container includes: Demap the received STM-N frame to obtain at least one AU-4; Demapping is performed on at least one AU-4 to obtain at least one VC-4 container.

4. The method according to claim 1, wherein Demapping the STM-N frame to obtain at least one container includes: Demap the received STM-N frame to obtain at least one AU-4; Demapping at least one AU-4 to obtain at least one VC-4 container; Demapping is performed on at least one VC-4 container to obtain multiple TU groups TUG-3; Demap multiple TUG-3s to obtain multiple TU-3s; Demap multiple TU-3s to obtain multiple VC-3 containers; Perform clock synchronization on the multiple VC-3 containers and generate the second pointer.

5. The method according to claim 1, characterized in that Demapping the STM-N frame to obtain at least one container includes: Demap the received STM-N frame to obtain at least one AU-4; Demapping at least one AU-4 to obtain at least one VC-4 container; Demapping is performed on at least one VC-4 container to obtain multiple TUG-3s; Demap multiple TUG-3s to obtain multiple TUG-2s; Demap multiple TUG-2s to obtain multiple TU-12s; Demap multiple TU-12s to obtain multiple VC-12 containers; Perform clock synchronization on the multiple VC-12 containers and generate the second pointer.

6. The method according to claim 1, characterized in that The STM-N service includes one of the following: STM-1; STM-4; STM-16; STM-64.

7. The method according to claim 1, characterized in that The TDM service includes an E1 service; and the receiving of TDM service data includes: Receive E1 frames.

8. The method according to any one of claims 1 to 7, characterized in that The service frame includes one of the following: Optical service unit OSU frame; Optical Data Unit (ODU) frame.

9. The method according to any one of claims 1 to 7, characterized in that The length of the first pointer in the overhead area of ​​the service frame is 8 bits.

10. A method for transmitting business data, characterized in that: Applicable to receiving devices, including: Receive a service frame; the service frame includes an overhead area and a payload area; the overhead area includes a first pointer; the first pointer is used to indicate the starting position of the service data in the payload area; Demap the received service frame to obtain TDM service data; The TDM service includes an STM-N service, and the demapping of the received service frame to obtain TDM service data includes: Demapping the payload area of ​​the received service frame to obtain at least one AU or TU; At least one container is obtained using at least one AU or TU and a corresponding second pointer; the second pointer is used to indicate a starting position of the at least one container in a payload area of ​​the AU or TU; the at least one container is clock synchronized by a transmitting end device; Mapping the at least one container to obtain an STM-N frame; The TDM service includes an E1 service, and demapping the received service frame to obtain TDM service data includes: Demap the payload area of ​​the received service frame to obtain a TU; A container is obtained using the TU and a corresponding third pointer; the third pointer indicates a starting position of the container in the payload area of ​​the TU; the container is clock synchronized by a transmitting end device; The container is demapped to obtain an E1 frame.

11. The method according to claim 10, characterized in that The STM-N service includes one of the following: STM-1; STM-4; STM-16; STM-64.

12. The method according to claim 10 or 11, characterized in that The service frame includes one of the following: OSU frame; ODU frame.

13. The method according to claim 10 or 11, characterized in that The length of the first pointer in the overhead area of ​​the service frame is 8 bits.

14. A business data transmission device, characterized in that: include: A first receiving unit, configured to receive TDM service data; A first processing unit, configured to map TDM service data to a payload area of ​​a service frame; The service frame includes an overhead area and a payload area; The overhead area includes a first pointer; the first pointer is used to indicate the starting position of the service data in the payload area; The sending unit is used to send a service frame; wherein, The TDM service includes an STM-N service, and the first processing unit is configured to demap the STM-N frame to obtain at least one container; perform local clock synchronization on the at least one container and generate a second pointer; the second pointer is configured to indicate a starting position of the at least one container in a payload area of ​​an management unit AU or a tributary unit TU; add the second pointer to the at least one container to obtain at least one AU or TU; and map the at least one AU or TU to the payload area of ​​a service frame; The TDM service includes an E1 service, and the first processing unit is used to map the E1 frame into a container; synchronize the local clock of the container and generate a third pointer; the third pointer indicates the starting position of the container in the payload area of ​​the TU; add the third pointer to the container to obtain a TU; and map the TU to the payload area of ​​the service frame.

15. A business data transmission device, characterized in that: include: A second receiving unit is configured to receive a service frame; the service frame includes an overhead area and a payload area; The overhead area includes a first pointer; The first pointer is used to indicate the starting position of the service data in the payload area; The second processing unit is used to demap the received service frame to obtain TDM service data; wherein, The TDM service includes an STM-N service, and the second processing unit is configured to demap a payload area of ​​a received service frame to obtain at least one AU or TU; obtain at least one container using the at least one AU or TU and a corresponding second pointer; the second pointer is configured to indicate a starting position of the at least one container in the payload area of ​​the AU or TU; the at least one container is clock synchronized by a transmitting end device; and the at least one container is mapped to obtain an STM-N frame; The TDM service includes an E1 service, and the second processing unit is configured to demap a payload area of ​​a received service frame to obtain a TU; and obtain a container using the TU and a corresponding third pointer; The third pointer indicates the starting position of the container in the payload area of ​​the TU; the container is clock synchronized through the sending end device; and the container is demapped to obtain an E1 frame.

16. A transmitting device, characterized in that: include: A first processor and a first communication interface; wherein, The first communication interface is used to receive TDM service data; The first processor is configured to map the TDM service data to a payload area of ​​a service frame; the service frame comprises an overhead area and a payload area; the overhead area comprises a first pointer; the first pointer is configured to indicate a starting position of the service data in the payload area; The first communication interface is further used to send a service frame; wherein, The TDM service includes an STM-N service. The first processor is configured to demap an STM-N frame to obtain at least one container; perform local clock synchronization on the at least one container and generate a second pointer; the second pointer is configured to indicate a starting position of the at least one container in a payload area of ​​an administrative unit AU or a tributary unit TU; add the second pointer to the at least one container to obtain at least one AU or TU; and map the at least one AU or TU to the payload area of ​​a service frame. The TDM service includes an E1 service, and the first processor is configured to demap a payload area of ​​a received service frame to obtain a TU; A container is obtained using the TU and a corresponding third pointer; the third pointer indicates a starting position of the container in the payload area of ​​the TU; the container is clock synchronized by a transmitting end device; The container is demapped to obtain an E1 frame.

17. A receiving device, characterized in that: include: The second communication interface is configured to receive a service frame, wherein the service frame includes an overhead area and a payload area; The overhead area includes a first pointer; The first pointer is used to indicate the starting position of the service data in the payload area; The second processor is used to demap the received service frame to obtain TDM service data; wherein, The TDM service includes an STM-N service. The second processor is configured to demap a payload area of ​​a received service frame to obtain at least one AU or TU; obtain at least one container using the at least one AU or TU and a corresponding second pointer; the second pointer is configured to indicate a starting position of the at least one container in the payload area of ​​the AU or TU; the at least one container is clock synchronized by a transmitting end device; and the at least one container is mapped to obtain an STM-N frame. The TDM service includes an E1 service, and the second processor is configured to demap a payload area of ​​a received service frame to obtain a TU; and obtain a container using the TU and a corresponding third pointer; The third pointer indicates the starting position of the container in the payload area of ​​the TU; the container is clock synchronized through the sending end device; and the container is demapped to obtain an E1 frame.

18. A transmitting end device, characterized in that: include: a first processor and a first memory for storing a computer program capable of being executed on the processor, Wherein, when the first processor is used to run the computer program, it executes the steps of the method according to any one of claims 1 to 9.

19. A receiving device, characterized in that: include: a second processor and a second memory for storing a computer program capable of being executed on the processor, Wherein, when the second processor is used to run the computer program, it executes the steps of the method according to any one of claims 10 to 13.

20. A storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 9 are implemented, or the steps of the method according to any one of claims 10 to 13 are implemented.

Images