Oam message transmission method and apparatus, related device and storage medium

Patent metadata

Field	Value
Publication number	US-12592865-B2
Application number	US-202118008718-A
Country	US
Kind code	B2
Filing date	Jun 8, 2021
Priority date	Jun 8, 2020
Publication date	Mar 31, 2026
Grant date	Mar 31, 2026

Abstract

This disclosure discloses an operations, administration and maintenance (OAM) message transmission method, apparatus, sending end device, receiving end device and storage medium. The method includes: sending an OAM block by the sending end device; wherein only a single OAM block is sent in each sending period.

First claim

What is claimed is:

1 . An operations, administration and maintenance (OAM) message transmission method, performed by a sending end device, comprising:
sending an OAM block carrying an OAM message, wherein only a single OAM block is sent in each sending period; wherein the OAM block comprises a type-1 OAM block and a type-2 OAM block, wherein the type-1 OAM block and the type-2 OAM block are provided with periodic sending opportunities, respectively, and the periodic sending opportunities of the type-1 OAM block are not overlapped with the periodic sending opportunities of the type-2 OAM block; after sending of the type-1 OAM block in one period is completed, in case that there is the type-2 OAM block that needs to be sent, the type-2 OAM block is sent at the sending opportunity of the type-2 OAM block in a next period, and the type-1 OAM block is sent at the sending opportunity of the type-1 OAM block in a period immediately following the next period; in case that there is no type-2 OAM block that needs to be sent, no OAM block is sent at the sending opportunity of the type-2 OAM block in the next period, and the type-1 OAM block is sent at the sending opportunity of the type-1 OAM block in the period immediately following the next period.

2 . The OAM message transmission method according to claim 1 , wherein at least one field in the OAM block is used for indicating that the block is a block for OAM.

3 . The OAM message transmission method according to claim 1 , wherein a plurality of OAM messages are carried in one OAM block, and the plurality of OAM messages are of different types;
or, wherein one OAM message is carried in at least two OAM blocks.

4 . The OAM message transmission method according to claim 3 , wherein, in case that one OAM message is carried in at least two OAM blocks, a value of a first field in the OAM block is used for indicating whether the OAM message starts.

5 . The OAM message transmission method according to claim 4 , wherein in case that the value of the first field of the OAM block indicates that the OAM message starts, a second field in the OAM block is used for indicating a type of the OAM message carried in the block;
or, wherein in case that the value of the first field of the OAM block indicates other situation except that the OAM message starts, a second field used for indicating a type of the OAM message is not contained in the OAM block.

6 . The OAM message transmission method according to claim 3 , wherein, in case that one OAM message is carried in at least two OAM blocks, a value of a third field in the OAM block is used for indicating whether the OAM message ends.

7 . The OAM message transmission method according to claim 4 , wherein a third field used for indicating whether the OAM message ends is not contained in the OAM block.

8 . The OAM message transmission method according to claim 1 , wherein one OAM message is carried in a plurality of the type-2 OAM blocks;
the type-2 OAM blocks corresponding to a current OAM message are not sent until sending of the type-2 OAM blocks corresponding to a previous OAM message is completed; and/or, wherein different types of OAM messages are carried in different types of OAM blocks respectively.

9 . A sending end device, comprising: a first processor and a first memory configured to store a computer program executable by the first processor,
wherein the first processor is configured to execute the computer program, to implement steps of the method according to claim 1 .

10 . An OAM message transmission method, performed by a receiving end device, comprising:
receiving only a single OAM block in a period corresponding to one sending period, wherein an OAM message is carried in the single OAM block; wherein the OAM block comprises a type-1 OAM block and a type-2 OAM block, wherein the type-1 OAM block and the type-2 OAM block are provided with periodic sending opportunities, respectively, and the periodic sending opportunities of the type-1 OAM block are not overlapped with the periodic sending opportunities of the type-2 OAM block; after receiving of the type-1 OAM block in the period corresponding to the one sending period is completed, in case that there is the type-2 OAM block that needs to be received, the type-2 OAM block is received at the sending opportunity of the type-2 OAM block in a period corresponding to a next sending period, and the type-1 OAM block is received at the sending opportunity of the type-1 OAM block in a period corresponding to a sending period immediately following the next sending period; in case that there is no type-2 OAM block that needs to be received, no OAM block is received at the sending opportunity of the type-2 OAM block in the period corresponding to the next sending period, and the type-1 OAM block is received at the sending opportunity of the type-1 OAM block in the period corresponding to the sending period immediately following the next sending period.

11 . The OAM message transmission method according to claim 10 , wherein the OAM message is extracted from the received OAM block;
and/or, wherein at least one field in the OAM block is used for indicating that the block is a block for OAM.

12 . The OAM message transmission method according to claim 10 , wherein a plurality of OAM messages are carried in one OAM block, and the plurality of OAM messages are of different types;
or, wherein one OAM message is carried in at least two OAM blocks.

13 . The OAM message transmission method according to claim 12 , wherein, in case that one OAM message is carried in at least two OAM blocks, a value of a first field in the OAM block is used for indicating whether the OAM message starts.

14 . The OAM message transmission method according to claim 13 , wherein in case that the value of the first field of the OAM block indicates that the OAM message starts, a second field in the OAM block is used for indicating a type of the OAM message carried in the block;
or, wherein in case that the value of the first field of the OAM block indicates other situation except that the OAM message starts, a second field used for indicating a type of the OAM message is not contained in the OAM block.

15 . The OAM message transmission method according to claim 12 , wherein, in case that one OAM message is carried in at least two OAM blocks, a value of a third field in the OAM block is used for indicating whether the OAM message ends.

16 . The OAM message transmission method according to claim 13 , wherein a third field used for indicating whether the OAM message ends is not contained in the OAM block.

17 . The OAM message transmission method according to claim 10 , wherein one OAM message is carried in a plurality of the type-2 OAM blocks;
the type-2 OAM blocks corresponding to a current OAM message are not received until receiving of the type-2 OAM blocks corresponding to a previous OAM message is completed; and/or, wherein different types of OAM messages are carried in different types of OAM blocks respectively.

18 . A receiving end device, comprising: a second processor and a second memory configured to store a computer program executable by the second processor,
wherein the second processor is configured to execute the computer program, to implement steps of the method according to claim 10 .

Assignees

• China Mobile Comm Co Ltd Res Inst
• China Mobile Communications Group Co Ltd

Inventors

• Li Han
• Han Liuyan
• Cheng Weiqiang
• Zhang Dechao

Classifications

• H04L5/0058

  Allocation criteria · CPC title

• H04L5/0053

  Allocation of signalling, i.e. of overhead other than pilot signals · CPC title

• H04L5/0044

  Allocation of payload; Allocation of data channels, e.g. PDSCH or PUSCH · CPC title

• H04L43/0852

  Delays · CPC title

• H04L43/10

  Active monitoring, e.g. heartbeat, ping or trace-route · CPC title