WO2024120525A1 - 固定带宽业务的承载方法、装置、电子设备及存储介质 - Google Patents
固定带宽业务的承载方法、装置、电子设备及存储介质 Download PDFInfo
- Publication number
- WO2024120525A1 WO2024120525A1 PCT/CN2023/137469 CN2023137469W WO2024120525A1 WO 2024120525 A1 WO2024120525 A1 WO 2024120525A1 CN 2023137469 W CN2023137469 W CN 2023137469W WO 2024120525 A1 WO2024120525 A1 WO 2024120525A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- service data
- cbr
- frame
- cbr service
- container
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 58
- 230000005540 biological transmission Effects 0.000 claims abstract description 16
- 230000015654 memory Effects 0.000 claims description 20
- 238000004590 computer program Methods 0.000 claims description 15
- 238000004891 communication Methods 0.000 claims description 10
- 238000010586 diagram Methods 0.000 description 17
- 101100012902 Saccharomyces cerevisiae (strain ATCC 204508 / S288c) FIG2 gene Proteins 0.000 description 4
- 230000006978 adaptation Effects 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- 101001121408 Homo sapiens L-amino-acid oxidase Proteins 0.000 description 3
- 102100026388 L-amino-acid oxidase Human genes 0.000 description 3
- 101100233916 Saccharomyces cerevisiae (strain ATCC 204508 / S288c) KAR5 gene Proteins 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 101000827703 Homo sapiens Polyphosphoinositide phosphatase Proteins 0.000 description 2
- 102100023591 Polyphosphoinositide phosphatase Human genes 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000011161 development Methods 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04J—MULTIPLEX COMMUNICATION
- H04J3/00—Time-division multiplex systems
- H04J3/02—Details
- H04J3/06—Synchronising arrangements
- H04J3/0635—Clock or time synchronisation in a network
- H04J3/0638—Clock or time synchronisation among nodes; Internode synchronisation
- H04J3/0658—Clock or time synchronisation among packet nodes
- H04J3/0661—Clock or time synchronisation among packet nodes using timestamps
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04J—MULTIPLEX COMMUNICATION
- H04J3/00—Time-division multiplex systems
- H04J3/02—Details
- H04J3/06—Synchronising arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/565—Conversion or adaptation of application format or content
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
- H04L67/63—Routing a service request depending on the request content or context
Definitions
- the embodiments of the present disclosure relate to the field of electronic communication technology, and in particular to a method, device, electronic device and storage medium for carrying a fixed bandwidth service.
- MTN Metropolitan Transmission Network
- MTN consists of the metropolitan transmission network segment layer and the metropolitan transmission network path layer.
- the metropolitan transmission network segment layer supports port binding and is compatible with the Ethernet underlying protocol stack and standard Ethernet optical modules;
- the metropolitan transmission network path layer supports time division multiplexing switching based on 66B code blocks, has a complete end-to-end operation and maintenance management mechanism, and supports cross-multiplexing of any Nx5G channelized customer signals.
- MTN is also developing time division multiplexing channels with smaller granularity, such as channels with 10Mbps granularity.
- E1 and other types of constant bit rate (CBR) services are byte bit stream encoding, while MTN is based on 64/66B code block streams consistent with the Ethernet bottom layer. Therefore, CBR bit streams cannot be directly filled into MTN channels.
- CBR constant bit rate
- MTN is based on 64/66B code block streams consistent with the Ethernet bottom layer. Therefore, CBR bit streams cannot be directly filled into MTN channels.
- E1 has a bandwidth of 2Mbps, while the minimum slice channel granularity of MTN is 10Mbps. If multiple CBR service data are carried in one MTN channel, different frame formats are used respectively, which makes the implementation complicated, and the performance such as latency of different data channels is inconsistent, resulting in poor carrying efficiency.
- the embodiments of the present disclosure provide a method, device, electronic device and storage medium for carrying a fixed bandwidth service.
- the present disclosure provides a method for carrying a fixed bandwidth service, including:
- the frame container includes an S0 code block, a data code block, a D code block and a T code block.
- the frame container is used to load multiple CBR service data.
- the multiple CBR service data are interleaved and mapped to an area in the frame container where the service payload is placed according to a fixed byte length.
- the area for placing the service payload includes at least one of the following areas: an area for placing the service payload in the D code block, and an area for placing the service payload in the T code block.
- the fixed byte length is one byte.
- the frame container includes frame overhead.
- the frame overhead carries a container empty indication
- the container empty indication is used to indicate whether the frame container is loaded with each channel of CBR service data in the multiple channels of CBR service data.
- the container empty indication is a plurality of first bits, and one first bit indicates whether the frame container is loaded with one of the multiple CBR service data;
- the container empty indication is a second bit
- the second bit in the frame container and the frame container number jointly indicate whether one of the multiple CBR service data is loaded.
- the bytes in the area for placing the service payload and used to load the first CBR service data are filled with a fixed value
- the first channel of CBR service data is any channel of CBR service data among the multiple channels of CBR service data.
- the bytes used to load different CBR service data are respectively provided with negative adjustment opportunity bytes for adapting the deviation between the service data flow receiving rate and the container sending rate.
- the frame overhead carries a negative adjustment indication
- the negative justification indication is used to indicate whether the negative justification opportunity byte of the frame container is loaded with CBR service data.
- the negative adjustment indication is a plurality of third bits, one third bit indicating whether the negative adjustment opportunity byte set in the byte used to load one of the CBR service data of the multiple CBR service data is loaded with CBR service data;
- the negative adjustment indication is a fourth bit
- the fourth bit in the frame container and the frame container number jointly indicate whether the negative adjustment opportunity byte set in the byte used to load one of the multiple CBR service data is loaded with CBR service data.
- the frame overhead carries a client-side failure indication
- the client-side failure indication is used to indicate whether the port status of the CBR client-side port providing each channel of CBR service data among the multiple channels of CBR service data is normal.
- the client-side failure indication is a plurality of fifth bits, and one fifth bit indicates whether the port status of the CBR client-side port providing one of the multiple CBR service data is normal;
- the client-side failure indication is a sixth bit
- the sixth bit in the frame container and the frame container number jointly indicate whether the port status of the CBR client-side port providing one of the multiple CBR service data is normal.
- the frame overhead carries clock frequency information
- the clock frequency information includes the timestamp of each channel of CBR service data in the multiple channels of CBR service data.
- the embodiment of the present disclosure provides a bearing device for a fixed bandwidth service, including:
- a transmission module used for transmitting a frame container carrying a fixed bandwidth CBR service and having a fixed frame length in a metropolitan area transmission network channel;
- the frame container includes an S0 code block, a data code block, a D code block and a T code block.
- the frame container is used to load multiple CBR service data.
- the multiple CBR service data are interleaved and mapped to an area in the frame container where the service payload is placed according to a fixed byte length.
- An embodiment of the present disclosure provides an electronic device, including: a processor, a memory, and a communication bus;
- the communication bus is used to realize the communication connection between the processor and the memory
- the processor is used to execute one or more computer programs stored in the memory to implement the above-mentioned fixed bandwidth service bearing method.
- the present disclosure provides a computer-readable storage medium having a computer program stored thereon.
- the computer program is executed by a processor, the above-mentioned fixed bandwidth service bearing method is implemented.
- the embodiments of the present disclosure provide a method, device, electronic device and storage medium for carrying fixed bandwidth services, the method comprising: in a metropolitan area transmission network channel, transmitting a frame container with a fixed frame length that carries fixed bandwidth CBR services; wherein the frame container comprises an S0 code block, a data code block, a D code block and a T code block, the frame container is used to load multiple CBR service data, and the multiple CBR service data is interleaved and mapped to an area in the frame container where the service payload is placed according to a fixed byte length.
- the technical solution provided by the embodiments of the present disclosure can effectively solve the adaptation between bit stream encoding and 64/66B code block stream, and a unified frame format can be used when loading multiple CBR service data, the delay performance can be kept consistent, bandwidth adaptation is achieved and carrying efficiency is guaranteed.
- FIG1 is a schematic diagram of a flow chart of a method for carrying a fixed bandwidth service provided in an embodiment of the present disclosure
- FIG2 is a schematic diagram of an exemplary frame container provided by an embodiment of the present disclosure.
- FIG3 is a schematic diagram of the structure of a bearing device for a fixed bandwidth service provided by an embodiment of the present disclosure
- FIG. 4 is a schematic diagram of the structure of an electronic device provided in an embodiment of the present disclosure.
- FIG1 is a flow chart of a method for carrying fixed bandwidth services provided by the present disclosure. As shown in FIG1, in the present disclosure, the method for carrying fixed bandwidth services The main steps include:
- the frame container includes S0 code blocks, data code blocks, D code blocks and T code blocks.
- the frame container is used to load multiple CBR service data.
- the multiple CBR service data are interleaved and mapped to the area in the frame container where the service payload is placed according to a fixed byte length.
- a bearer device may transmit a frame container carrying a CBR service and having a fixed frame length in an MTN channel, wherein the number of frame containers transmitted in the MTN channel may be multiple, for example, one frame container is transmitted at a fixed time interval.
- the specific number of frame containers and the fixed frame length of the frame container are not limited in the embodiment of the present disclosure.
- the frame container has a unified and fixed frame structure.
- the frame container includes an S0 code block, a data code block, a D code block, and a T code block.
- the frame container includes an area for placing a service payload, and the area for placing the service payload includes at least one of the following areas: an area for placing the service payload in the D code block, and an area for placing the service payload in the T code block.
- a frame container can carry multiple channels of CBR service data, and the amount of CBR service data actually loaded in one frame container can be set according to actual needs and application scenarios.
- a frame container can carry four channels of CBR service data.
- one frame container can actually carry three channels of CBR service data, and another frame container can actually carry four channels of CBR services.
- the embodiments of the present disclosure do not limit this.
- multiple CBR service data when multiple CBR service data are loaded into a frame container, they are interleaved and mapped to the area in the frame container where the service is placed according to a fixed byte length.
- the fixed byte length may be one byte, that is, the multiple CBR service data are interleaved and mapped to the area in the frame container where the service payload is placed according to a single byte.
- the fixed byte length may also be other byte lengths, and the byte length used for the interleaving mapping of multiple CBR service data in each frame container is unified, and the specific fixed byte length is not limited in the embodiments of the present disclosure.
- FIG2 is a schematic diagram of an exemplary frame container provided by an embodiment of the present disclosure. As shown in FIG2, four CBR service data are interleaved and mapped according to single bytes, with the first CBR service data E1#1 filled with 1 byte, the second CBR service data E1#2 filled with 1 byte, the third CBR service data E1#3 filled with 1 byte, and the fourth CBR service data E1#4 filled with 1 byte, interleaved and filled in sequence. The area where service payload is placed.
- the frame container includes a frame overhead. As shown in FIG2 , the frame container starts with an S0 code block, followed by a frame overhead, an area for placing a service payload, and a T code block, wherein the T code block can be a code block with a data filling area such as T7, and the area for placing the service payload in the T code block belongs to the area for placing the service payload in the entire frame container.
- the T code block can be a code block with a data filling area such as T7, and the area for placing the service payload in the T code block belongs to the area for placing the service payload in the entire frame container.
- the frame overhead carries a container empty indication; the container empty indication is used to indicate whether the frame container is loaded with each CBR service data in multiple CBR service data.
- the frame container can be used to load four-way CBR service data
- the frame overhead carries a container empty indication to indicate whether the frame container is actually loaded with four-way CBR service data.
- the container empty indication is a plurality of first bits, and one first bit indicates whether the frame container is loaded with one CBR service data among multiple CBR service data; or, the container empty indication is a second bit, and the second bit in the frame container is combined with the frame container number to indicate whether one CBR service data is loaded.
- a frame container can load four channels of CBR service data, and different first bits are used in the frame overhead to respectively identify whether the first, second, third, and fourth channels of CBR service data are loaded.
- first first bit when the first first bit is 0, it means that in the area where the service payload is placed, the byte used to load the first channel of CBR service data is loaded with the first channel of CBR service data, that is, the frame container is loaded with the first channel of CBR service data; when the first first bit is 1, it means that in the area where the service payload is placed, the byte used to load the first channel of CBR service data is not loaded with the first channel of CBR service data, that is, the frame container is not loaded with the first channel of CBR service data.
- a frame container can load four channels of CBR service data, and a second bit is used in the frame overhead to indicate the loading status of the four channels of CBR service data by combining with different frame container numbers.
- the value of the second bit in the frame overhead of a frame container number of 1 indicates whether the byte used to load the first channel of CBR service data in the area where the service payload is placed is loaded with the first channel of CBR service data
- the value of the second bit in the frame overhead of a frame container number of 2 indicates whether the byte used to load the second channel of CBR service data in the area where the service payload is placed is loaded with the second channel of CBR service data
- the value of the second bit in the frame overhead of a frame container number of 3 indicates whether the byte used to load the third channel of CBR service data in the area where the service payload is placed is loaded with the third channel of CBR service data
- the frame container number The value of the second bit in the frame overhead of 4 indicates whether the byte used to load the
- whether one of the multiple CBR service data is loaded can be indicated by using a different frame container number combined with the second bit.
- the second bits in the frame overhead of frame container numbers 1, 5 and 9 all indicate whether the first CBR service data is loaded.
- the bytes used to load the first CBR service data in the area where the service payload is placed are filled with fixed values; wherein the first CBR service data is any CBR service data among multiple CBR service data.
- a frame container can load four channels of CBR service data.
- the area of the service payload placed in the frame container can be filled with fixed values for bytes that are loaded but not loaded with one of the CBR service data. For example, these bytes are all filled with a fixed value of 1.
- the bytes used to load different CBR service data are respectively provided with negative adjustment opportunity bytes for adapting the deviation between the service data flow receiving rate and the container sending rate.
- a frame container can load four channels of CBR service data.
- the bytes used to load the first, second, third, and fourth channels of CBR service data are each provided with a negative adjustment opportunity byte at a fixed position, which is used to adapt the deviation between the data flow receiving rate of the four channels of CBR service data and the container sending rate.
- the first byte of each of the bytes corresponding to the first, second, third, and fourth channels of CBR service data is set as a negative adjustment opportunity byte.
- the first byte of the bytes used to load the first channel of CBR service data that is, the negative adjustment opportunity byte, will not be filled with the first channel of CBR service data, and can be filled with other values, for example, the filling value 0.
- the frame overhead carries a negative adjustment indication, which is used to indicate whether the negative adjustment opportunity byte of the frame container is loaded with CBR service data.
- the bytes used to load the CBR service data of different paths are respectively provided with negative adjustment opportunity bytes, and the frame overhead carries
- the negative adjustment byte use indication indicates whether the negative adjustment opportunity bytes respectively set in the bytes for loading CBR service data of different channels in the area where the service payload is placed are loaded with CBR service data.
- the negative adjustment indication is a plurality of third bits, one third bit indicating whether the negative adjustment opportunity byte set in the byte for loading one CBR service data of multiple CBR service data is loaded with CBR service data;
- the negative adjustment indication is a fourth bit
- the fourth bit in the frame container and the frame container number jointly indicate whether the negative adjustment opportunity byte set in the byte used to load one CBR service data of multiple CBR service data loads CBR service data.
- a frame container can load four channels of CBR service data, and different third bits are used in the frame overhead to indicate whether the negative adjustment opportunity byte set in the byte for loading the first, second, third, and fourth channels of CBR service data is loaded with CBR service data.
- the first third bit indicates whether the negative adjustment opportunity byte set in the byte for loading the first channel of CBR service data is loaded with CBR service data; when the first third bit is 0, it indicates that the negative adjustment opportunity byte set in the byte for loading the first channel of CBR service data is loaded with CBR service data, and when the first third bit is 1, it indicates that the negative adjustment opportunity byte set in the byte for loading the first channel of CBR service data is not loaded with CBR service data.
- the negative adjustment opportunity byte can be filled with a fixed value, for example, a fixed value of 0, that is, the negative adjustment opportunity byte is used to adapt the deviation between the service data flow receiving rate of the first channel of CBR service data and the container sending rate.
- a frame container can load four channels of CBR service data, and a fourth bit is used in the frame overhead to indicate the use of the negative adjustment opportunity byte set in the byte for loading each channel of CBR service data in the area where the service payload is placed by combining with different frame container numbers.
- the value of the fourth bit in the frame overhead with the frame container number of 1 indicates whether the negative adjustment opportunity byte set in the byte for loading the first channel of CBR service data is loaded with CBR service data;
- the value of the fourth bit in the frame overhead with the frame container number of 2 indicates whether the negative adjustment opportunity byte set in the byte for loading the second channel of CBR service data is loaded with CBR service data;
- the value of the fourth bit in the frame overhead with the frame container number of 3 indicates whether the negative adjustment opportunity byte set in the byte for loading the third channel of CBR service data is loaded with CBR service data;
- the value of the fourth bit in the frame overhead with the frame container number of 4 indicates whether the negative adjustment opportunity byte set in the byte for loading the fourth channel of CBR service data is loaded with CBR service data.
- different frame container numbers can be used in combination with the fourth bit to indicate, for example, the fourth bit in the frame overhead of frame container numbers 1, 5 and 9 all indicate whether the negative adjustment opportunity byte set in the byte for loading the first CBR service data is loaded with CBR service data.
- the frame overhead carries a client-side failure indication, which is used to indicate whether the port status of the CBR client-side port providing each channel of CBR service data among multiple channels of CBR service data is normal.
- a frame container can load four channels of CBR service data and carry a client-side failure indication in the frame overhead, which is used to indicate whether the port status of the CBR client-side port providing each of the first, second, third, and fourth channels of CBR service data is normal.
- the client-side failure indication is a plurality of fifth bits, and one fifth bit indicates whether the port status of a CBR client-side port providing one CBR service data of multiple channels is normal;
- the client-side failure indication is a sixth bit
- the sixth bit in the frame container and the frame container number jointly indicate whether the port status of the CBR client-side port providing one CBR service data of multiple CBR service data is normal.
- the client-side failure indication may be a plurality of fifth bits or a sixth bit.
- the client-side port status of 4 E1 services indicates whether the client-side port status of 4 E1 services is normal (for example, when the indication value is 0, the client-side port status is normal; when the indication value is 1, the client-side port status is invalid, and the E1 payload of the channel is all set to 1). In this way, the failure status of the E1 client signal at the sending end can be transmitted to the other end.
- a frame container can carry four channels of CBR service data, and different fifth bits are used in the frame overhead to indicate whether the port status of the CBR client-side port providing the first, second, third, and fourth channels of CBR service data is normal.
- the first fifth bit indicates whether the port status of the CBR client-side port providing the first channel of CBR service data is normal. Whether the port status is normal; when the first fifth bit is 0, it indicates that the port status of the CBR client-side port providing the first CBR service data is normal; when the first fifth bit is 1, it indicates that the port status of the CBR client-side port providing the first CBR service data is invalid.
- a frame container can load four channels of CBR service data, and a sixth bit is used in the frame overhead to indicate whether the port status of the CBR client-side port providing each channel of CBR service data in multiple channels of CBR service data is normal by combining with different frame container numbers.
- the value of the sixth bit in the frame overhead of the frame container number 1 indicates whether the port status of the CBR client-side port providing the first channel of CBR service data is normal; the value of the sixth bit in the frame overhead of the frame container number 2 indicates whether the port status of the CBR client-side port providing the second channel of CBR service data is normal; the value of the sixth bit in the frame overhead of the frame container number 3 indicates whether the port status of the CBR client-side port providing the third channel of CBR service data is normal; the value of the sixth bit in the frame overhead of the frame container number 4 indicates whether the port status of the CBR client-side port providing the fourth channel of CBR service data is normal.
- the frame overhead carries clock frequency information; the clock frequency information includes the timestamp of each channel of CBR service data in the multiple channels of CBR service data.
- a frame container can carry multiple CBR service data, and the timestamps of the multiple CBR service data can be carried in the frame overheads of different frame containers respectively.
- the timestamp field and the container frame number can jointly indicate the complete timestamp of a certain CBR service data. For example, several timestamps of certain container frame numbers are combined into the timestamp of the first CBR service data, and several timestamps of certain container frame numbers are combined into the timestamp of the second CBR service data.
- the timestamp can be carried periodically with the transmission of the frame container, which is not limited in the embodiments of the present disclosure.
- the embodiment of the present disclosure provides a method for carrying a fixed bandwidth service, including: in a metropolitan area transmission network channel, transmitting a frame container with a fixed frame length that carries a fixed bandwidth CBR service; wherein the frame container includes an S0 code block, a data code block, a D code block, and a T code block, and the frame container is used to load multiple CBR service data, and the multiple CBR service data is interleaved and mapped to an area in the frame container where the service payload is placed according to a fixed byte length.
- the method for carrying a fixed bandwidth service provided by the embodiment of the present disclosure can effectively solve the adaptation between bit stream encoding and 64/66B code block stream, and a unified frame format can be used when loading multiple CBR service data, and the delay performance can be kept consistent, bandwidth adaptation is achieved, and carrying efficiency is guaranteed.
- FIG3 is a schematic diagram of the structure of a bearing device for a fixed bandwidth service provided by an embodiment of the present disclosure.
- the bearer device for the fixed bandwidth service includes:
- the transmission module 301 is used to transmit a frame container carrying a fixed bandwidth CBR service and having a fixed frame length in a metropolitan area transmission network channel;
- the frame container includes an S0 code block, a data code block, a D code block and a T code block.
- the frame container is used to load multiple CBR service data.
- the multiple CBR service data are interleaved and mapped to an area in the frame container where the service payload is placed according to a fixed byte length.
- the area for placing the service payload includes at least one of the following areas: an area for placing the service payload in the D code block, and an area for placing the service payload in the T code block.
- the fixed byte length is one byte.
- the frame container includes a frame overhead.
- the frame overhead carries a container empty indication
- the container empty indication is used to indicate whether the frame container is loaded with each channel of CBR service data in the multiple channels of CBR service data.
- the container empty indication is a plurality of first bits, and one first bit indicates whether the frame container carries one of the multiple CBR service data;
- the container empty indication is a second bit
- the second bit in the frame container and the frame container number jointly indicate whether one of the multiple CBR service data is loaded.
- the bytes in the area for placing the service payload for loading the first CBR service data are filled with a fixed value
- the first channel of CBR service data is any channel of CBR service data among the multiple channels of CBR service data.
- bytes used to load CBR service data of different paths are respectively provided with negative adjustment opportunity bytes for adapting to the deviation between the service data flow receiving rate and the container sending rate.
- the frame overhead carries a negative adjustment indication
- the negative adjustment indication is used to indicate whether the negative adjustment opportunity byte of the frame container is loaded with CBR Business data.
- the negative adjustment indication is a plurality of third bits, one third bit indicating whether the negative adjustment opportunity byte set in the byte for loading one of the CBR service data of the multiple CBR service data is loaded with CBR service data;
- the negative adjustment indication is a fourth bit
- the fourth bit in the frame container and the frame container number jointly indicate whether the negative adjustment opportunity byte set in the byte used to load one of the multiple CBR service data is loaded with CBR service data.
- the frame overhead carries a client-side failure indication
- the client-side failure indication is used to indicate whether the port status of the CBR client-side port providing each channel of CBR service data among the multiple channels of CBR service data is normal.
- the client-side failure indication is a plurality of fifth bits, and one fifth bit indicates whether the port status of the CBR client-side port providing one of the multiple CBR service data is normal;
- the client-side failure indication is a sixth bit
- the sixth bit in the frame container and the frame container number jointly indicate whether the port status of the CBR client-side port providing one of the multiple CBR service data is normal.
- the frame overhead carries clock frequency information
- the clock frequency information includes the timestamp of each channel of CBR service data in the multiple channels of CBR service data.
- FIG4 is a schematic diagram of the structure of an electronic device provided by the embodiment of the present disclosure.
- the electronic device includes: a processor 401, a memory 402, and a communication bus 403;
- the communication bus 403 is used to realize the communication connection between the processor 401 and the memory 402;
- the processor 401 is configured to execute one or more computer programs stored in the memory 402 to implement the above-mentioned method for carrying fixed bandwidth services.
- the present disclosure provides a computer-readable storage medium on which a computer program is stored.
- the computer-readable storage medium may be a volatile memory, such as a random access memory. (Random-Access Memory, RAM); or non-volatile memory (non-volatile memory), such as read-only memory (Read-Only Memory, ROM), flash memory (flash memory), hard disk drive (Hard Disk Drive, HDD) or solid-state drive (SSD); it can also be a respective device including one or any combination of the above memories, such as a mobile phone, a computer, a tablet device, a personal digital assistant, etc.
- RAM Random-Access Memory
- non-volatile memory such as read-only memory (Read-Only Memory, ROM), flash memory (flash memory), hard disk drive (Hard Disk Drive, HDD) or solid-state drive (SSD)
- SSD solid-state drive
- the embodiments of the present disclosure may be provided as methods, systems, or computer program products. Therefore, the present disclosure may take the form of hardware embodiments, software embodiments, or embodiments combining software and hardware. Furthermore, the present disclosure may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) containing computer-usable program code.
- a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) containing computer-usable program code.
- each process and/or box in the flow diagram and/or block diagram can be implemented by computer program instructions, as well as the combination of the processes and/or boxes in the flow diagram and/or block diagram.
- These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for implementing the functions specified in one process or multiple processes in the implementation flow diagram and/or one box or multiple boxes in the block diagram.
- These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including an instruction device that implements the functions specified in implementing one or more processes in the flowchart and/or one or more boxes in the block diagram.
- These computer program instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, whereby the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and/or one or more boxes in the block diagram.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Time-Division Multiplex Systems (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
本公开实施例公开了一种固定带宽业务的承载方法、装置、电子设备和存储介质,方法包括:在城域传送网通道中,传输承载固定带宽CBR业务、具有固定帧长的帧容器;其中,帧容器包括S0码块、数据码块D码块和T码块,帧容器用于装载多路CBR业务数据,多路CBR业务数据按照固定字节长度交织映射至帧容器中放置业务净荷的区域。
Description
相关申请的交叉引用
本申请主张在2022年12月9日在中国提交的中国专利申请号No.202211585294.X的优先权,其全部内容通过引用包含于此。
本公开实施例涉及电子通信技术领域,尤其涉及一种固定带宽业务的承载方法、装置、电子设备及存储介质。
城域传送网(Metropolitan Transmission Network,MTN)作为一种新型传送网技术体系,能够实现时分复用技术和分组交换的有效融合。MTN由城域传送网段层和城域传送网通路层构成。其中,城域传送网段层支持端口绑定,兼容以太网底层协议栈及标准以太网光模块;城域传送网通路层支持基于66B码块的时分复用交换,具备完善的端到端操作维护管理机制,支持任意Nx5G信道化客户信号的交叉复用。随着业务的发展,MTN也在发展更小颗粒度的时分复用通道,例如10Mbps颗粒度的通道。
然而,E1等类型固定带宽(Constant Bit Rate,CBR)业务是字节比特流编码,而MTN是基于和以太网底层一致的64/66B码块流,因此,CBR比特流无法直接填充至MTN通道中,此外,E1等类型CBR业务与MTN通道带宽存在差距,E1为2Mbps带宽,而MTN最小切片通道颗粒度为10Mbps,如果在一个MTN通道中承载多路CBR业务数据时,分别用不同的帧格式,则实现复杂,而且不同路数据的情况时延等性能不一致,承载效率较差。
发明内容
为至少部分地解决上述问题,本公开实施例提供一种固定带宽业务的承载方法、装置、电子设备及存储介质。
本公开实施例的技术方案是这样实现的:
本公开实施例提供了一种固定带宽业务的承载方法,包括:
在城域传送网通道中,传输承载固定带宽CBR业务、具有固定帧长的帧容器;
其中,所述帧容器包括S0码块、数据码块D码块和T码块,所述帧容器用于装载多路CBR业务数据,所述多路CBR业务数据按照固定字节长度交织映射至所述帧容器中放置业务净荷的区域。
在上述方法中,所述放置业务净荷的区域至少包括以下区域中的一个:所述D码块中放置业务净荷的区域,所述T码块中放置业务净荷的区域。
在上述方法中,所述固定字节长度为一个字节。
在上述方法中,所述帧容器中包含帧开销。
在上述方法中,所述帧开销中携带容器空载指示;
所述容器空载指示,用于指示所述帧容器是否装载所述多路CBR业务数据中各路CBR业务数据。
在上述方法中,所述容器空载指示为多个第一比特,一个第一比特指示所述帧容器是否装载所述多路CBR业务数据其中一路CBR业务数据;
或者,所述容器空载指示为一个第二比特,所述帧容器中的第二比特与帧容器号,联合指示是否装载所述多路CBR业务数据其中一路CBR业务数据。
在上述方法中,在所述帧容器中未装载第一路CBR业务数据的情况下,所述放置业务净荷的区域内,用于装载所述第一路CBR业务数据的字节填充有固定值;
其中,所述第一路CBR业务数据为所述多路CBR业务数据中任一路CBR业务数据。
在上述方法中,所述放置业务净荷的区域内,用于装载不同路CBR业务数据的字节中分别设置有负调整机会字节,用于适配业务数据流接收速率与容器发送速率之间的偏差。
在上述方法中,所述帧开销中携带负调整指示;
所述负调整指示,用于指示所述帧容器的负调整机会字节是否装载CBR业务数据。
在上述方法中,所述负调整指示为多个第三比特,一个第三比特,指示用于装载所述多路CBR业务数据其中一路CBR业务数据的字节中设置的负调整机会字节是否装载CBR业务数据;
或者,所述负调整指示为一个第四比特,所述帧容器中的第四比特与帧容器号,联合指示用于装载所述多路CBR业务数据其中一路CBR业务数据的字节中设置的负调整机会字节是否装载CBR业务数据。
在上述方法中,所述帧开销中携带客户侧失效指示;
所述客户侧失效指示,用于指示提供所述多路CBR业务数据中各路CBR业务数据的CBR客户侧端口的端口状态是否正常。
在上述方法中,所述客户侧失效指示为多个第五比特,一个第五比特指示提供所述多路CBR业务数据其中一路CBR业务数据的CBR客户侧端口的端口状态是否正常;
或者,所述客户侧失效指示为一个第六比特,所述帧容器中的第六比特与帧容器号,联合指示提供所述多路CBR业务数据其中一路CBR业务数据的CBR客户侧端口的端口状态是否正常。
在上述方法中,所述帧开销中携带时钟频率信息;
所述时钟频率信息,包括所述多路CBR业务数据中各路CBR业务数据的时戳。
本公开实施例提供可一种固定带宽业务的承载装置,包括:
传输模块,用于在城域传送网通道中,传输承载固定带宽CBR业务、具有固定帧长的帧容器;
其中,所述帧容器包括S0码块、数据码块D码块和T码块,所述帧容器用于装载多路CBR业务数据,所述多路CBR业务数据按照固定字节长度交织映射至所述帧容器中放置业务净荷的区域。
本公开实施例提供了一种电子设备,包括:处理器、存储器和通信总线;
所述通信总线,用于实现所述处理器和所述存储器之间的通信连接;
所述处理器,用于执行所述存储器存储的一个或者多个计算机程序,以实现上述固定带宽业务的承载方法。
本公开实施例提供了一种计算机可读存储介质,其上存储有计算机程序,
该计算机程序被处理器执行时实现上述固定带宽业务的承载方法。
本公开实施例提供了一种固定带宽业务的承载方法、装置、电子设备和存储介质,方法包括:在城域传送网通道中,传输承载固定带宽CBR业务、具有固定帧长的帧容器;其中,帧容器包括S0码块、数据码块D码块和T码块,帧容器用于装载多路CBR业务数据,多路CBR业务数据按照固定字节长度交织映射至帧容器中放置业务净荷的区域。本公开实施例提供的技术方案,可以有效解决比特流编码和64/66B码块流之间的适配,而且在多路CBR业务数据装载时可以采用统一的帧格式实现,时延性能能够保持一致,实现了带宽适配且保证了承载效率。
图1为本公开实施例提供的一种固定带宽业务的承载方法的流程示意图;
图2为本公开实施例提供的一种示例性的帧容器示意图;
图3为本公开实施例提供的一种固定带宽业务的承载装置的结构示意图;
图4为本公开实施例提供的一种电子设备的结构示意图。
为了使本公开的目的、技术方案及优点更加清楚明白,以下结合附图及实施例,对本公开进行进一步详细说明。应当理解,此处描述的具体实施例仅仅用以解释本公开,并不用于限定本公开。
下面将通过实施例并结合附图具体地对本公开的技术方案以及本公开的技术方案如何解决上述技术问题进行详细说明。下面的实施例可以相互结合,对于相同或相似的概念或过程可能在某些实施例中不再赘述。
另外,本公开实施例所记载的技术方案之间,在不冲突的情况下,可以任意组合。
本公开实施例提供了一种固定带宽业务的承载方法,通过固定带宽业务的承载装置实现,该承载装置可以是手机、平板电脑等电子设备,本公开实施例不作限定。图1为本公开实施例提供的一种固定带宽业务的承载方法的流程示意图。如图1所示,在本公开的实施例中,固定带宽业务的承载方法
主要包括以下步骤:
S101、在城域传送网通道中,传输承载固定带宽CBR业务、具有固定帧长的帧容器;
其中,帧容器包括S0码块、数据码块D码块和T码块,帧容器用于装载多路CBR业务数据,多路CBR业务数据按照固定字节长度交织映射至帧容器中放置业务净荷的区域。
在本公开的实施例中,承载装置可以在MTN通道中,传输承载CBR业务、具有固定帧长的帧容器,其中,MTN通道中传输的帧容器的数量可以为多个,例如,每间隔固定时长传输一个帧容器。具体的帧容器的数量,以及帧容器的固定帧长本公开实施例不作限定。
在本公开的实施例中,帧容器具有统一固定的帧结构。帧容器包括S0码块、数据码块D码块和T码块,帧容器中包括放置业务净荷的区域,放置业务净荷的区域至少包括以下其中区域中的一个:D码块中放置业务净荷的区域,T码块中放置业务净荷的区域。
需要说明的是,在本公开的实施例中,帧容器可以装载多路CBR业务数据,在一个帧容器中实际装载的CBR业务数据的数量可以根据实际需求和应用场景设定,例如,帧容器可以装载四路CBR业务数据,在实际应用中,一个帧容器可以实际装载三路CBR业务数据,另一个帧容器可以实际装载四路CBR业务,本公开实施例不作限定。
需要说明的是,在本公开的实施例中,多路CBR业务数据在装载到帧容器时,按照固定字节长度交织映射至帧容器中放置业务的区域。其中,固定字节长度可以为一个字节,即多路CBR业务数据是按照单字节交织映射至帧容器中放置业务净荷的区域。当然,固定字节长度还可以是其他字节长度,对于各个帧容器中多路CBR业务数据的交织映射所采用的字节长度是统一的,具体的固定字节长度本公开实施例不作限定。
图2为本公开实施例提供的一种示例性的帧容器示意图。如图2所示,四路CBR业务数据按照单字节交织映射,以第一路CBR业务数据E1#1填充1字节、第二路CBR业务数据E1#2填充1字节、第三路CBR业务数据E1#3填充1字节、第四路CBR业务数据E1#4填充1字节,依次交织填充在可以
放置业务净荷的区域。
在本公开的实施例中,帧容器中包含帧开销。如图2所示,帧容器由S0码块起始,然后依次是帧开销,放置业务净荷的区域和T码块,其中,T码块可以采用T7等具备数据填充区域的码块,T码块中放置业务净荷的区域属于整个帧容器中放置业务净荷的区域。
在本公开的实施例中,帧开销中携带容器空载指示;容器空载指示,用于指示帧容器是否装载多路CBR业务数据中各路CBR业务数据。
在本公开的实施例中,参见2所示,帧容器中可以用来装载四路CBR业务数据,帧开销中携带容器空载指示,用于指示帧容器是否实际装载了四路CBR业务数据。
在本公开的实施例中,容器空载指示为多个第一比特,一个第一比特指示帧容器是否装载多路CBR业务数据其中一路CBR业务数据;或者,容器空载指示为一个第二比特,帧容器中的第二比特与帧容器号联合指示是否装载一路CBR业务数据。
示例性的,在本公开的实施例中,帧容器可以装载四路CBR业务数据,帧开销中用不同的第一比特分别标识第一、第二、第三、第四路的CBR业务数据是否装载。例如,第一个第一比特为0时,表示放置业务净荷的区域内,用于装载第一路CBR业务数据的字节装载了第一路CBR业务数据,即帧容器装载了第一路CBR业务数据;第一个第一比特为1时,表示放置业务净荷的区域内,用于装载第一路CBR业务数据的字节未装载第一路CBR业务数据,即帧容器未装载第一路CBR业务数据。
示例性的,在本公开的实施例中,帧容器可以装载四路CBR业务数据,帧开销中用一个第二比特,通过与不同帧容器号联合指示四路CBR业务数据的装载情况。例如,帧容器号为1的帧开销中第二比特的值,表示放置业务净荷的区域内用于装载第一路CBR业务数据的字节是否装载了第一路CBR业务数据;帧容器号为2的帧开销中第二比特的值,表示放置业务净荷的区域内用于装载第二路CBR业务数据的字节是否装载了第二路CBR业务数据;帧容器号为3的帧开销中第二比特的值,表示放置业务净荷的区域内用于装载第三路CBR业务数据的字节是否装载了第三路CBR业务数据;帧容器号
为4的帧开销中第二比特的值,表示放置业务净荷的区域内用于装载第四路CBR业务数据的字节是否装载了第四路CBR业务数据。
需要说明的是,在本公开的实施例中,对于采用第二比特与帧容器号联合指示CBR业务数据的是否装载的方式,多路CBR业务数据其中一路CBR业务数据是否装载可以采用不同的帧容器号联合第二比特指示,例如,帧容器号1、5和9的帧开销中的第二比特都指示是否装载第一路CBR业务数据。
在本公开的实施例中,在帧容器中未装载第一路CBR业务数据的情况下,放置业务净荷的区域内,用于装载第一路CBR业务数据的字节填充有固定值;其中,第一路CBR业务数据为多路CBR业务数据中任一路CBR业务数据。
示例性的,在本公开的实施例中,帧容器可以装载四路CBR业务数据,当帧容器未装载第一、第二、第三、第四路的CBR业务数据其中一些路CBR业务数据时,可以在帧容器中放置业务净荷的区域内,用于装载但未装载其中一路CBR业务数据的字节填充固定值,例如这些字节均填充固定值1。
在本公开的实施例中,放置业务净荷的区域内,用于装载不同路CBR业务数据的字节中分别设置有负调整机会字节,用于适配业务数据流接收速率与容器发送速率之间的偏差。
示例性的,在本公开的实施例中,帧容器可以装载四路CBR业务数据,帧容器中放置业务净荷的区域内,用于分别装载第一、第二、第三、第四路CBR业务数据的字节中各自在固定位置设置有负调整机会字节,用于适配四路CBR业务数据的数据流接收速率与容器发送速率之间偏差。例如,参见图2,将用于分别装载第一、第二、第三、第四路CBR业务数据对应的字节中,各自的第一个字节设置为负调整机会字节,如果第一路CBR业务数据的数据流接收速率导致需要发送慢一些时,用于装载第一路CBR业务数据的字节中第一个字节,即负调整机会字节将不填充第一路CBR业务数据,可以填充其他值,例如,填充值0。
在本公开的实施例中,帧开销中携带负调整指示;负调整指示,用于指示帧容器的负调整机会字节是否装载CBR业务数据。
需要说明的是,在本公开的实施例中,放置业务净荷的区域内,用于装载不同路CBR业务数据的字节中分别设置有负调整机会字节,帧开销中携带
负调整字节使用指示,指示放置业务净荷的区域内,用于装载不同路CBR业务数据的字节中分别设置的负调整机会字节是否装载了CBR业务数据。
在本公开的实施例中,负调整指示为多个第三比特,一个第三比特,指示用于装载多路CBR业务数据其中一路CBR业务数据的字节中设置的负调整机会字节是否装载CBR业务数据;
或者,负调整指示为一个第四比特,帧容器中的第四比特与帧容器号,联合指示用于装载多路CBR业务数据其中一路CBR业务数据的字节中设置的负调整机会字节是否装载CBR业务数据。
示例性的,在本公开的实施例中,帧容器可以装载四路CBR业务数据,帧开销中用不同的第三比特分别指示用于装载第一、第二、第三、第四路的CBR业务数据的字节中设置的负调整机会字节是否装载CBR业务数据。例如,第一个第三比特指示用于装载第一路CBR业务数据的字节中设置的负调整机会字节是否装载CBR业务数据;第一个第三比特为0时,表示用于装载第一路CBR业务数据的字节中设置的负调整机会字节中装载了CBR业务数据,第一个第三比特为1时,表示用于装载第一路CBR业务数据的字节中设置的负调整机会字节中未装载CBR业务数据,此时,该负调整机会字节可填充固定值,例如,固定值0,也就是使用了该负调整机会字节适配了第一路CBR业务数据的业务数据流接收速率与容器发送速率之间的偏差。
示例性的,在本公开的实施例中,帧容器可以装载四路CBR业务数据,帧开销中用一个第四比特,通过与不同帧容器号联合指示放置业务净荷的区域中,用于装载各路CBR业务数据的字节中设置的负调整机会字节的使用情况。例如,帧容器号为1的帧开销中第四比特的值,指示用于装载第一路CBR业务数据的字节中设置的负调整机会字节是否装载CBR业务数据;帧容器号为2的帧开销中第四比特的值,指示用于装载第二路CBR业务数据的字节中设置的负调整机会字节是否装载CBR业务数据;帧容器号为3的帧开销中第四比特的值,指示用于装载第三路CBR业务数据的字节中设置的负调整机会字节是否装载CBR业务数据;帧容器号为4的帧开销中第四比特的值,指示用于装载第四路CBR业务数据的字节中设置的负调整机会字节是否装载CBR业务数据。
需要说明的是,在本公开的实施例中,对于采用第四比特与帧容器号联合指示负调整机会字节是否装载CBR业务数据的方式,用于装载多路CBR业务数据其中一路CBR业务数据的字节中设置的负调整机会字节是否装载CBR业务数据,可以采用不同的帧容器号联合第四比特指示,例如,帧容器号1、5和9的帧开销中的第四比特,都指示用于装载第一路CBR业务数据的字节中设置的负调整机会字节是否装载CBR业务数据。
在本公开的实施例中,帧开销中携带客户侧失效指示;客户侧失效指示,用于指示提供多路CBR业务数据中各路CBR业务数据的CBR客户侧端口的端口状态是否正常。
示例性的,在本公开的实施例中,帧容器可以装载四路CBR业务数据,在帧开销中携带客户侧失效指示,用于指示提供第一、第二、第三、第四路的CBR业务数据中各路CBR业务数据的CBR客户侧端口的端口状态是否正常。
在本公开的实施例中,客户侧失效指示为多个第五比特,一个第五比特指示提供多路CBR业务数据其中一路CBR业务数据的CBR客户侧端口的端口状态是否正常;
或者,客户侧失效指示为一个第六比特,帧容器中的第六比特与帧容器号,联合指示提供多路CBR业务数据其中一路CBR业务数据的CBR客户侧端口的端口状态是否正常。
需要说明的是,在本公开的实施例中,与上述容器空载指示和负调整指示类似,客户侧失效指示可以为多个第五比特或一个第六比特。
示例性的,表示4路E1业务的客户侧端口状态是否正常(例如该指示值为0时,客户侧端口状态正常;该指示值为1时,客户侧端口状态失效,该路E1净荷全置1)。通过这种方法,可以将发送端的E1客户信号的失效情况传递给对端。
示例性的,在本公开的实施例中,帧容器可以装载四路CBR业务数据,帧开销中用不同的第五比特,分别指示提供第一、第二、第三、第四路的CBR业务数据中各路CBR业务数据的CBR客户侧端口的端口状态是否正常。例如,第一个第五比特指示提供第一路CBR业务数据的CBR客户侧端口的端
口状态是否正常;第一个第五比特为0时,表示提供第一路CBR业务数据的CBR客户侧端口的端口状态正常,第一个第五比特为1时,表示提供第一路CBR业务数据的CBR客户侧端口的端口状态失效。
示例性的,在本公开的实施例中,帧容器可以装载四路CBR业务数据,帧开销中用一个第六比特,通过与不同帧容器号联合指示提供多路CBR业务数据中各路CBR业务数据的CBR客户侧端口的端口状态是否正常。例如,帧容器号为1的帧开销中第六比特的值,指示提供第一路CBR业务数据的CBR客户侧端口的端口状态是否正常;帧容器号为2的帧开销中第六比特的值,指示提供第二路CBR业务数据的CBR客户侧端口的端口状态是否正常;帧容器号为3的帧开销中第六比特的值,指示提供第三路CBR业务数据的CBR客户侧端口的端口状态是否正常;帧容器号为4的帧开销中第六比特的值,指示提供第四路CBR业务数据的CBR客户侧端口的端口状态是否正常。
在本公开的实施例中,帧开销中携带时钟频率信息;时钟频率信息,包括多路CBR业务数据中各路CBR业务数据的时戳。
需要说明的是,在本公开的实施例中,帧容器可以装载多路CBR业务数据,对于多路CBR业务数据的时戳可以分别在不同帧容器的帧开销中携带,时戳域段和容器帧号可以联合指示某一路CBR业务数据完整的时戳,例如,某几个容器帧号的几段时戳组合成第一路CBR业务数据的时戳,另外某几个容器帧号的几段时戳组合成第二路CBR业务数据的时戳。此外,时戳可以随着帧容器的传输周期性的携带,本公开实施例不作限定。
本公开实施例提供了一种固定带宽业务的承载方法,包括:在城域传送网通道中,传输承载固定带宽CBR业务、具有固定帧长的帧容器;其中,帧容器包括S0码块、数据码块D码块和T码块,帧容器用于装载多路CBR业务数据,多路CBR业务数据按照固定字节长度交织映射至帧容器中放置业务净荷的区域。本公开实施例提供的固定带宽业务承载的方法,可以有效解决比特流编码和64/66B码块流之间的适配,而且在多路CBR业务数据装载时可以采用统一的帧格式实现,时延性能能够保持一致,实现了带宽适配且保证了承载效率。
图3为本公开实施例提供的一种固定带宽业务的承载装置的结构示意图。
如图3所示,固定带宽业务的承载装置包括:
传输模块301,用于在城域传送网通道中,传输承载固定带宽CBR业务、具有固定帧长的帧容器;
其中,所述帧容器包括S0码块、数据码块D码块和T码块,所述帧容器用于装载多路CBR业务数据,所述多路CBR业务数据按照固定字节长度交织映射至所述帧容器中放置业务净荷的区域。
在本公开一实施例中,所述放置业务净荷的区域至少包括以下区域中的一个:所述D码块中放置业务净荷的区域,所述T码块中放置业务净荷的区域。
在本公开一实施例中,所述固定字节长度为一个字节。
在本公开一实施例中,所述帧容器中包含帧开销。
在本公开一实施例中,所述帧开销中携带容器空载指示;
所述容器空载指示,用于指示所述帧容器是否装载所述多路CBR业务数据中各路CBR业务数据。
在本公开一实施例中,所述容器空载指示为多个第一比特,一个第一比特指示所述帧容器是否装载所述多路CBR业务数据其中一路CBR业务数据;
或者,所述容器空载指示为一个第二比特,所述帧容器中的第二比特与帧容器号,联合指示是否装载所述多路CBR业务数据其中一路CBR业务数据。
在本公开一实施例中,在所述帧容器中未装载第一路CBR业务数据的情况下,所述放置业务净荷的区域内,用于装载所述第一路CBR业务数据的字节填充有固定值;
其中,所述第一路CBR业务数据为所述多路CBR业务数据中任一路CBR业务数据。
在本公开一实施例中,所述放置业务净荷的区域内,用于装载不同路CBR业务数据的字节中分别设置有负调整机会字节,用于适配业务数据流接收速率与容器发送速率之间的偏差。
在本公开一实施例中,所述帧开销中携带负调整指示;
所述负调整指示,用于指示所述帧容器的负调整机会字节是否装载CBR
业务数据。
在本公开一实施例中,所述负调整指示为多个第三比特,一个第三比特,指示用于装载所述多路CBR业务数据其中一路CBR业务数据的字节中设置的负调整机会字节是否装载CBR业务数据;
或者,所述负调整指示为一个第四比特,所述帧容器中的第四比特与帧容器号,联合指示用于装载所述多路CBR业务数据其中一路CBR业务数据的字节中设置的负调整机会字节是否装载CBR业务数据。
在本公开一实施例中,所述帧开销中携带客户侧失效指示;
所述客户侧失效指示,用于指示提供所述多路CBR业务数据中各路CBR业务数据的CBR客户侧端口的端口状态是否正常。
在本公开一实施例中,所述客户侧失效指示为多个第五比特,一个第五比特指示提供所述多路CBR业务数据其中一路CBR业务数据的CBR客户侧端口的端口状态是否正常;
或者,所述客户侧失效指示为一个第六比特,所述帧容器中的第六比特与帧容器号,联合指示提供所述多路CBR业务数据其中一路CBR业务数据的CBR客户侧端口的端口状态是否正常。
在本公开一实施例中,所述帧开销中携带时钟频率信息;
所述时钟频率信息,包括所述多路CBR业务数据中各路CBR业务数据的时戳。
本公开实施例还提供了一种电子设备。图4为本公开实施例提供的一种电子设备的结构示意图。如图4所示,在本公开的实施例中,电子设备包括:处理器401、存储器402和通信总线403;
所述通信总线403,用于实现所述处理器401和所述存储器402之间的通信连接;
所述处理器401,用于执行所述存储器402存储的一个或者多个计算机程序,以实现上述固定带宽业务的承载方法。
本公开实施例提供了一种计算机可读存储介质,其上存储有计算机程序,该计算机程序被处理器执行时实现上述固定带宽业务的承载方法。计算机可读存储介质可以是易失性存储器(volatile memory),例如随机存取存储器
(Random-Access Memory,RAM);或者非易失性存储器(non-volatile memory),例如只读存储器(Read-Only Memory,ROM),快闪存储器(flash memory),硬盘(Hard Disk Drive,HDD)或固态硬盘(Solid-State Drive,SSD);也可以是包括上述存储器之一或任意组合的各自设备,如移动电话、计算机、平板设备、个人数字助理等。
本领域内的技术人员应明白,本公开的实施例可提供为方法、系统、或计算机程序产品。因此,本公开可采用硬件实施例、软件实施例、或结合软件和硬件方面的实施例的形式。而且,本公开可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器和光学存储器等)上实施的计算机程序产品的形式。
本公开是参照根据本公开实施例的方法、设备(系统)、和计算机程序产品的实现流程示意图和/或方框图来描述的。应理解可由计算机程序指令实现流程示意图和/或方框图中的每一流程和/或方框、以及实现流程示意图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器,使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在实现流程示意图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中,使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品,该指令装置实现在实现流程示意图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上,使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理,从而在计算机或其他可编程设备上执行的指令提供用于实现在实现流程示意图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
以上所述,仅为本公开的具体实施方式,但本公开的保护范围并不局限于此,任何熟悉本技术领域的技术人员在本实用申请揭露的技术范围内,可
轻易想到的变化或替换,都应涵盖在本公开的保护范围之内。因此,本公开的保护范围应以所述权利要求的保护范围为准。
Claims (16)
- 一种固定带宽业务的承载方法,包括:在城域传送网通道中,传输承载固定带宽CBR业务、具有固定帧长的帧容器;其中,所述帧容器包括S0码块、数据码块D码块和T码块,所述帧容器用于装载多路CBR业务数据,所述多路CBR业务数据按照固定字节长度交织映射至所述帧容器中放置业务净荷的区域。
- 根据权利要求1所述的方法,其中,所述放置业务净荷的区域至少包括以下区域中的一个:所述D码块中放置业务净荷的区域,所述T码块中放置业务净荷的区域。
- 根据权利要求1所述的方法,其中,所述固定字节长度为一个字节。
- 根据权利要求1所述的方法,其中,所述帧容器中包含帧开销。
- 根据权利要求4所述的方法,其中,所述帧开销中携带容器空载指示;所述容器空载指示,用于指示所述帧容器是否装载所述多路CBR业务数据中各路CBR业务数据。
- 根据权利要求5所述的方法,其中,所述容器空载指示为多个第一比特,一个第一比特指示所述帧容器是否装载所述多路CBR业务数据其中一路CBR业务数据;或者,所述容器空载指示为一个第二比特,所述帧容器中的第二比特与帧容器号,联合指示是否装载所述多路CBR业务数据其中一路CBR业务数据。
- 根据权利要求1所述的方法,其中,在所述帧容器中未装载第一路CBR业务数据的情况下,所述放置业务净荷的区域内,用于装载所述第一路CBR业务数据的字节填充有固定值;其中,所述第一路CBR业务数据为所述多路CBR业务数据中任一路CBR业务数据。
- 根据权利要求1所述的方法,其中,所述放置业务净荷的区域内,用于装载不同路CBR业务数据的字节中分 别设置有负调整机会字节,用于适配业务数据流接收速率与容器发送速率之间的偏差。
- 根据权利要求4所述的方法,其中,所述帧开销中携带负调整指示;所述负调整指示,用于指示所述帧容器的负调整机会字节是否装载CBR业务数据。
- 根据权利要求9所述的方法,其中,所述负调整指示为多个第三比特,一个第三比特,指示用于装载所述多路CBR业务数据其中一路CBR业务数据的字节中设置的负调整机会字节是否装载CBR业务数据;或者,所述负调整指示为一个第四比特,所述帧容器中的第四比特与帧容器号,联合指示用于装载所述多路CBR业务数据其中一路CBR业务数据的字节中设置的负调整机会字节是否装载CBR业务数据。
- 根据权利要求4所述的方法,其中,所述帧开销中携带客户侧失效指示;所述客户侧失效指示,用于指示提供所述多路CBR业务数据中各路CBR业务数据的CBR客户侧端口的端口状态是否正常。
- 根据权利要求11所述的方法,其中,所述客户侧失效指示为多个第五比特,一个第五比特指示提供所述多路CBR业务数据其中一路CBR业务数据的CBR客户侧端口的端口状态是否正常;或者,所述客户侧失效指示为一个第六比特,所述帧容器中的第六比特与帧容器号,联合指示提供所述多路CBR业务数据其中一路CBR业务数据的CBR客户侧端口的端口状态是否正常。
- 根据权利要求4所述的方法,其中,所述帧开销中携带时钟频率信息;所述时钟频率信息,包括所述多路CBR业务数据中各路CBR业务数据的时戳。
- 一种固定带宽业务的承载装置,包括:传输模块,用于在城域传送网通道中,传输承载固定带宽CBR业务、具 有固定帧长的帧容器;其中,所述帧容器包括S0码块、数据码块D码块和T码块,所述帧容器用于装载多路CBR业务数据,所述多路CBR业务数据按照固定字节长度交织映射至所述帧容器中放置业务净荷的区域。
- 一种电子设备,包括:处理器、存储器和通信总线;所述通信总线,用于实现所述处理器和所述存储器之间的通信连接;所述处理器,用于执行所述存储器存储的一个或者多个计算机程序,以实现权利要求1至13任一项所述的固定带宽业务的承载方法。
- 一种计算机可读存储介质,其上存储有计算机程序,该计算机程序被处理器执行时实现如权利要求1至13任一项所述的固定带宽业务的承载方法。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202211585294.XA CN118175208A (zh) | 2022-12-09 | 2022-12-09 | 固定带宽业务的承载方法、装置、电子设备及存储介质 |
CN202211585294.X | 2022-12-09 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2024120525A1 true WO2024120525A1 (zh) | 2024-06-13 |
Family
ID=91349314
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2023/137469 WO2024120525A1 (zh) | 2022-12-09 | 2023-12-08 | 固定带宽业务的承载方法、装置、电子设备及存储介质 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN118175208A (zh) |
WO (1) | WO2024120525A1 (zh) |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101155006A (zh) * | 2006-09-30 | 2008-04-02 | 华为技术有限公司 | 一种固定速率业务传送的方法与装置 |
US20200366412A1 (en) * | 2018-02-09 | 2020-11-19 | Huawei Technologies Co., Ltd. | Method and Apparatus for Processing Service Data in Optical Transport Network |
WO2022152012A1 (zh) * | 2021-01-18 | 2022-07-21 | 中兴通讯股份有限公司 | 客户业务承载方法及装置 |
CN114866618A (zh) * | 2019-04-30 | 2022-08-05 | 华为技术有限公司 | 光传送网中的数据传输方法及装置 |
-
2022
- 2022-12-09 CN CN202211585294.XA patent/CN118175208A/zh active Pending
-
2023
- 2023-12-08 WO PCT/CN2023/137469 patent/WO2024120525A1/zh unknown
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101155006A (zh) * | 2006-09-30 | 2008-04-02 | 华为技术有限公司 | 一种固定速率业务传送的方法与装置 |
US20200366412A1 (en) * | 2018-02-09 | 2020-11-19 | Huawei Technologies Co., Ltd. | Method and Apparatus for Processing Service Data in Optical Transport Network |
CN114866618A (zh) * | 2019-04-30 | 2022-08-05 | 华为技术有限公司 | 光传送网中的数据传输方法及装置 |
WO2022152012A1 (zh) * | 2021-01-18 | 2022-07-21 | 中兴通讯股份有限公司 | 客户业务承载方法及装置 |
Non-Patent Citations (4)
Title |
---|
"Interfaces for the metro transport network; G.8312 (12/20)", ITU-T STANDARD G.8312, INTERNATIONAL TELECOMMUNICATION UNION, GENEVA ; CH, no. G.8312 (12/20), 22 December 2020 (2020-12-22), Geneva ; CH , pages 1 - 24, XP044304372 * |
CHINA MOBILE: "SPN 2.0", CHINA MOBILE - TECHNICAL WHITE PAPER, 8 July 2022 (2022-07-08), XP093179254, Retrieved from the Internet <URL:https://www.digitalelite.cn/h-nd-4848.html> * |
LIUYAN HAN, YE WEN, WANG MINXUE, LI HAN: "Development of SPN 2.0 for 5G and Computing Power)", COMMUNICATIONS WORLD, no. 17, 10 September 2022 (2022-09-10), pages 33 - 35, XP093179249, DOI: 10.13571/j.cnki.cww.2022.17.009 * |
LIUYAN HAN, YE WEN, WANG MINXUE, LI HAN: "SPN Moves towards Small Particle Slice 2.0 Era", COMMUNICATIONS WORLD, no. 14, 15 July 2021 (2021-07-15), pages 31 - 33, XP093179251, DOI: 10.13571/j.cnki.cww.2021.14.011 * |
Also Published As
Publication number | Publication date |
---|---|
CN118175208A (zh) | 2024-06-11 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN109600188B (zh) | 数据传输方法、传输设备和传输系统 | |
US11108485B2 (en) | Clock synchronization method and apparatus | |
CN102484548B (zh) | 用于周期性时间戳传输的设备、网络组件及方法 | |
WO2018090856A1 (zh) | 用于建立灵活以太网群组的方法和设备 | |
US20210243668A1 (en) | Radio Link Aggregation | |
JP6962599B2 (ja) | クライアントサービス送信方法および装置 | |
GB2448933A (en) | Content synchronization for mobile communication network | |
WO2021109705A1 (zh) | 灵活以太网组的管理方法、设备及计算机可读存储介质 | |
CN102377678B (zh) | 一种数据传输处理方法及装置 | |
US9438431B2 (en) | Method of transmitting traffic in a communications network and communications network apparatus | |
WO2024120525A1 (zh) | 固定带宽业务的承载方法、装置、电子设备及存储介质 | |
CN102308591A (zh) | 一种通信网络数据传输方法、节点和系统 | |
CN101707623A (zh) | 一种小内存系统中的文件发送方法及装置 | |
CN114338831B (zh) | 一种网关通信方法、通信设备和存储介质 | |
US20240146433A1 (en) | Time slot allocation processing method, device and storage medium | |
EP2798790B1 (en) | Compression method for tdm frames in a packet network | |
WO2024165009A1 (zh) | 数据处理方法、装置、相关设备及存储介质 | |
WO2021031573A1 (zh) | 一种数据发送的控制方法及装置 | |
WO2023005738A1 (zh) | 灵活以太网时隙协商方法、接收端、发送端及存储介质 | |
WO2023284563A1 (zh) | 时隙配置方法、时隙配置装置及计算机可读存储介质 | |
JP2005519541A (ja) | 第1データストリームを第2データストリームに変換する方法及び装置 | |
CN113923778A (zh) | 一种切片通道的信息传输方法、装置及设备 | |
FI120175B (fi) | Digitaalisen informaation siirtäminen kehitysvälitteisessä tiedonsiirtoverkossa |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 23900093 Country of ref document: EP Kind code of ref document: A1 |