CN101990167A

CN101990167A - Instruction-transmitting method of multicast broadcast connection protocol data unit

Info

Publication number: CN101990167A
Application number: CN200910174334XA
Authority: CN
Inventors: 石晓娟; 吕开颖; 刘扬
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2009-07-31
Filing date: 2009-09-07
Publication date: 2011-03-23
Also published as: WO2011012037A1

Abstract

The invention discloses an instruction-transmitting method of a multicast broadcast connection protocol data unit. In the method, a base station transmits the protocol data unit of multicast broadcast connection to a subscriber station, wherein the protocol data unit contains protocol header and load; the data of SDU or segmented by the SDU in the load are from one or more of multicast broadcast service contents; the one or more of multicast broadcast service contents belong to one multicast broadcast service connection; the multicast service identifier which identifies the multicast broadcast service connection can be carried in the resource allocation information of the control channel; and the identifiers used for distinguishing different multicast broadcast service contents are indicated in the protocol header or carried in the resource allocation information of the control channel. By adopting the method of the invention, the cost of multicast broadcast service signaling connection can be reduced, the efficient transmission of the multicast broadcast service can be realized and the utilization rate of the air interface resource can be increased.

Description

Method for sending and indicating multicast broadcast connection protocol data unit

Technical Field

The invention relates to the technical field of mobile communication, in particular to a method for sending and indicating a multicast broadcast connection protocol data unit.

Background

In the new generation of WiMAX technology, Multicast Broadcast Service is referred to as Enhanced-Multicast Broadcast Service (E-MBS), which is a technology for transmitting data from one data source to multiple targets. The multicast broadcast service can effectively improve the utilization rate of network resources, particularly air interface resources. With the application and popularization of multimedia sharing services, multicast broadcast service transmission is performed efficiently, which becomes especially important for next generation broadband mobile communication systems.

In IEEE802.16 network reference model layering, a common part sublayer receives Data from a convergence sublayer through a Medium Access Control (MAC) layer Service Access point (ap) to form a MAC layer Service Data Unit (SDU). MAC SDUs can be segmented and reassembled, and then encapsulated with a Protocol header to form a MAC layer Protocol Data Unit (PDU), which is a MAC layer Data Unit for transmitting messages between a base station and a subscriber station.

The MAC PDU consists of a protocol header and a variable length payload (optional) as shown in fig. 1. The protocol Header includes a MAC Header, and may include one or more Extended Headers (EH). In IEEE802.16m, there are two types of MAC headers: a generic MAC header and a compressed MAC header as shown in fig. 2 and 3, respectively. Wherein the compressed MAC header is particularly used for the transmission of MAC PDUs for persistent allocation and group allocation connections. There are three types of expansion heads: a segment packing extension header, a segment extension header, and a multiplexing extension header, as shown in fig. 4, 5, and 6, respectively. Wherein, the segment packing extension header is used for segmentation or packing of SDU or SDU segment from a certain transmission connection; the segment extension header is used for segmentation of an SDU or SDU segment from a certain management connection; the multiplexed extension header is composed of a plurality of multiplexed extension header sub-blocks (as shown in fig. 7) for packetization of SDUs or SDU fragments from a plurality of connections.

For unicast service, IEEE802.16m specifies that a base Station allocates a unique Station Identifier (STID) to each subscriber Station registered in a network, and multiple unicast connections under the same subscriber Station (or STID) are distinguished by a traffic Flow Identifier (FID). That is, in a base station region, each unicast connection is jointly defined by an STID and an FID, wherein the STID is carried in the resource allocation information of the unicast control channel, and the FID is indicated in the MAC PDU header, thereby realizing the transmission indication of the unicast connection protocol data unit.

For Multicast broadcast services, IEEE802.16m specifies that each Multicast service connection in an E-MBS zone (E-MBSzone) is assigned a common Multicast service identification (msctid), which is included in control information to indicate the different Multicast service connections. Under the connection of a multicast broadcast service, only one E-MBS content can be contained, or a plurality of E-MBS contents can be contained simultaneously, and the different E-MBS contents are distinguished by logical channel identifications. However, various protocol headers in the existing IEEE802.16m are designed for unicast connection, and no indication method for multicast broadcast connection protocol data unit transmission has been proposed yet.

Disclosure of Invention

In view of the above, the present invention provides a method for indicating multicast broadcast connection protocol data unit transmission, so as to solve the problem in the prior art that an indication method for multicast broadcast connection protocol data unit transmission has not been proposed yet.

According to the present invention, a method for indicating the transmission of a multicast broadcast connection protocol data unit is provided.

The method for indicating the transmission of the multicast broadcast connection protocol data unit comprises the following steps: the base station sends a protocol data unit of the multicast broadcast connection to the subscriber station, wherein the protocol data unit comprises a protocol header and a load.

Further, the payload of the pdu consists of one or more SDU or SDU segments, the data of the SDU or SDU segments being from one or more multicast broadcast service contents, the multicast broadcast service contents belonging to a multicast broadcast service connection.

Preferably, when the data of the SDU or SDU fragment is from multiple multicast broadcast service contents, the method further includes: the protocol head of the protocol data unit carries an identifier for indicating the multicast broadcast service content, and the resource allocation information of the control channel indicates a multicast service identifier for identifying the multicast broadcast service connection.

Preferably, the protocol header may comprise a multicast broadcast compressed MAC header.

Preferably, the multicast broadcast compressed MAC header includes at least one of the following indication fields: an extension header indication field indicating whether the protocol header contains an extension header, a length field indicating the length of an SDU or SDU fragment constituting a payload, and a reserved field.

Preferably, the protocol header may also include a multicast broadcast generic MAC header.

Preferably, the multicast broadcast generic MAC header includes at least one of the following indication fields: an identification field for indicating the content of the multicast broadcast service, an extension header indication field for indicating whether the protocol header contains an extension header, a length field for indicating the length of the SDU or the SDU segment forming the payload, and a reserved field.

Preferably, when the data of the SDU or SDU fragment constituting the payload is from one multicast broadcast service content, the special identifier for indicating that the identification field of the multicast broadcast service content is reserved indicates that the multicast broadcast generic MAC header is not used for indicating the identification of the respective multicast broadcast service content.

Further, when the extension header indication field indicates that the protocol header contains an extension header, the protocol header further includes: one or more expansion heads.

Preferably, each extension header comprises at least one of the following indication fields: indicating whether the extension header is a header termination identification field of the last extension header of the protocol header, indicating a type of the extension header, an extension header type field, an extension header entity and a reserved field, wherein the type of the extension header comprises: a multicast broadcast segment packing extension head and a multicast broadcast multiplexing extension head.

Further, when the extension header wraps the extension header for a multicast broadcast segment, the extension header is used to segment or wrap SDUs or SDU segments from one multicast broadcast service content.

Preferably, when the extension header is a multicast broadcast segment packed extension header, the extension header entity includes the following indication fields: the system comprises a sequence number field indicating the sequence number of SDU or SDU segment forming the load, a segment control field indicating segment control information, N-1 length fields and N field termination marks indicating the termination of the length fields, wherein N is the number of SDU or SDU segment forming the load.

Further, when the extension header is a multicast broadcast multiplexing extension header, the extension header is used for packing and multiplexing SDUs or SDU segments from one or more multicast broadcast service contents.

Preferably, when the extension header is a multicast broadcast multiplex extension header, the extension header entity includes at least one of: one or more multicast broadcast multiplexing extension head sub-blocks and a reserved domain, wherein each multicast broadcast multiplexing extension head sub-block corresponds to one multicast broadcast service content contained in the load.

Preferably, the multicast broadcast multiplexing extension header sub-block is used to describe the SDU or SDU segment of the multicast broadcast service content corresponding to the multicast broadcast multiplexing extension header sub-block, and includes the following indication fields: a block termination identification field indicating whether the extension head sub-block is the last extension head sub-block, an identification field for indicating the content of the multicast broadcast service, a segment control field, a sequence number field, a field termination identification and a length field.

Preferably, if the protocol header includes a multicast broadcast compressed MAC header, each multicast broadcast multiplexing extension header sub-block includes an identifier for indicating multicast broadcast service content, and when the data of the SDU or SDU fragment is from a multicast broadcast service content, a special identifier for indicating that an identifier field of the multicast broadcast service content is reserved indicates that the multicast broadcast multiplexing extension header sub-block does not have an identifier for indicating the multicast broadcast service content; if the protocol header includes a multicast broadcast generic MAC header, the 1 st multicast broadcast multiplex extension header sub-block does not contain an identification for indicating the contents of the multicast broadcast service.

Preferably, for the above length fields, the 1 st multicast broadcast multiplexing extension header sub-block includes N1-1 length fields, and the ith multicast broadcast multiplexing extension header sub-block in the rest multicast broadcast multiplexing extension header sub-blocks includes Ni length fields, where N1 is the number of SDUs or SDU segments corresponding to the 1 st multicast broadcast multiplexing extension header sub-block in the payload, and Ni is the number of SDUs or SDU segments corresponding to the ith multicast broadcast multiplexing extension header sub-block in the payload.

Preferably, for the above-mentioned domain termination identifier, the ith multicast broadcast multiplexing extension header sub-block includes Ni domain termination identifiers, where Ni is the number of SDUs or SDU segments corresponding to the ith multicast broadcast multiplexing extension header sub-block in the payload.

Preferably, the method may further include: the protocol head of the protocol data unit does not carry an identifier for indicating the multicast broadcast service content, the resource allocation information of the control channel indicates a multicast service identifier for identifying the multicast broadcast service connection and an identifier for indicating the multicast broadcast service content, and the sequence of the identifiers in the resource allocation information is the same as the sequence of the multicast broadcast service content in the protocol data unit.

Preferably, the payload of the protocol data unit may consist of one or more SDUs or SDU segments, wherein the data of the SDU or SDU segments is from one or more multicast broadcast service connections.

Preferably, the method further comprises: and indicating a multicast service identifier for identifying the multicast broadcast service connection in the resource allocation information of the control channel, wherein the sequence of the multicast service identifier in the resource allocation information is consistent with the sequence of the multicast broadcast service connection in the protocol data unit.

Preferably, the protocol header comprises a multicast broadcast compressed MAC header.

Preferably, the multicast broadcast compressed MAC header includes at least one of the following indication fields: the extension header indicates a field, a length field and a reserved field.

Further, when the extended header indication field indicates that the multicast broadcast compressed MAC header is followed by an extended header, the protocol header further includes: one or more expansion heads.

Preferably, the extension header includes at least one of the following indication fields: a header termination identification field, an extension header type field, an extension header entity, and a reserved field.

Preferably, when the extension header is a multicast broadcast segment packing extension header, if the load is from a multicast broadcast service content, the extension header is used for segmenting or packing the SDU or SDU segment from the multicast broadcast service content; if the load is from a multicast broadcast service connection, the extension header is used to segment or pack the SDU or SDU segment from the multicast broadcast service connection.

Preferably, the multicast broadcast segment packing extension header includes the following indication fields: the system comprises a sequence number field, a segmentation control field, N-1 length fields and N field termination marks, wherein N is the number of SDUs or SDU segments forming a load.

Further, when the extension header is a multicast broadcast multiplexing extension header, if the load is from one or more multicast broadcast service contents and the multicast broadcast service contents belong to a multicast broadcast service connection, the extension header is used for packing and multiplexing the SDU or SDU segments from the multicast broadcast service contents; if the payload is from one or more multicast broadcast service connections, the extension header is used to packet multiplex the SDUs or SDU segments from the multicast broadcast service connections.

Preferably, the multicast broadcast multiplexing extension header includes at least one of: one or more multicast broadcast multiplex extension head sub-blocks and a reserved domain, wherein each multicast broadcast multiplex extension head sub-block corresponds to one multicast broadcast service content or one multicast broadcast service connection contained in the load.

Preferably, the multicast broadcast multiplexing extension header sub-block is used to describe the information of the SDU or SDU fragment corresponding to the multicast broadcast service content or multicast broadcast service connection, and the multicast broadcast multiplexing extension header sub-block includes the following indication fields: block termination identification field, segment control field, sequence number field, field termination identification, length field.

Preferably, for the above length fields, the 1 st multicast broadcast multiplexing extension header sub-block includes N1-1 length fields, and the ith multicast broadcast multiplexing extension header sub-block in the remaining multicast broadcast multiplexing extension header sub-blocks includes Ni length fields, where N1 is the number of SDUs or SDU segments included in the payload and corresponding to the 1 st multicast broadcast multiplexing extension header sub-block, and Ni is the number of SDUs or SDU segments included in the payload and corresponding to the ith multicast broadcast multiplexing extension header sub-block.

Preferably, for the above-mentioned domain termination identifier, the ith multicast broadcast multiplexing extension header sub-block includes Ni domain termination identifiers, where Ni is the number of SDUs or SDU segments corresponding to the ith multicast broadcast multiplexing extension header sub-block and included in the payload.

Through at least one scheme of the invention, when the protocol data unit is sent, the Logical Channel Identifier (LCID) or the multicast service identifier (MSTID) is indicated in the protocol header or carried in the resource allocation information of the control channel, thereby solving the problem that the prior art does not provide an indication method for the sending of the multicast broadcast connection protocol data unit, reducing the cost of multicast broadcast service signaling, realizing the high-efficiency transmission of the multicast broadcast service and improving the utilization rate of air interface resources.

Additional features and advantages of the invention will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. The objectives and other advantages of the invention will be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.

Drawings

The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description serve to explain the principles of the invention and not to limit the invention. In the drawings:

FIG. 1 is a diagram illustrating a MAC PDU format in IEEE802.16 m;

FIG. 2 is a diagram illustrating a generic MAC header format in IEEE802.16 m;

FIG. 3 is a diagram illustrating a compressed MAC header format in a conventional IEEE802.16 m;

FIG. 4 is a diagram of a conventional IEEE802.16m SDH format;

FIG. 5 is a diagram illustrating a conventional fragment extension header format in IEEE802.16 m;

FIG. 6 is a diagram illustrating a format of a multiplexing extended header in IEEE802.16 m;

FIG. 7 is a diagram illustrating a multiplexing extended header sub-block format in IEEE802.16 m;

FIG. 8A is a schematic diagram of a protocol header in a first form of a protocol header;

FIG. 8B is a diagram illustrating the format of E-MBS multiplexing extension header sub-block in the protocol header of the first form;

FIG. 9A is a diagram illustrating a format of a protocol header in a protocol header of the second form;

FIG. 9B is a diagram of the format of the protocol header E-MBS multiplexing extension header sub-block in the protocol header of the second form;

fig. 10A is a schematic diagram of a format of a protocol header in a protocol header of the third form;

FIG. 10B is a diagram of the format of the protocol header E-MBS multiplexing extension header sub-block in the protocol header of the second form;

FIG. 11 is a diagram of a protocol header format in example one;

FIG. 12 is a diagram of a protocol header format in example two;

FIG. 13 is a diagram of a protocol header format in example three;

FIG. 14 is a schematic diagram of a protocol header format in example four;

FIG. 15 is a schematic diagram of an example fifth protocol header format;

FIG. 16 is a schematic diagram of a protocol header format in example six;

FIG. 17 is a diagram of a protocol header format in example seven;

FIG. 18 is a schematic diagram of an example eighth protocol header format;

FIG. 19 is a diagram of an example nine protocol header format;

FIG. 20 is a diagram of an example tenth protocol header format;

FIG. 21 is a schematic diagram of a protocol header format in example eleven;

FIG. 22 is a schematic diagram of an example twelve-protocol header format;

FIG. 23 is a schematic diagram of a protocol header format in example thirteen;

fig. 24 is a diagram of an example fourteen protocol header format.

Detailed Description

Overview of the function

In the embodiment of the invention, aiming at the sending of the multicast broadcast protocol data unit, according to the composition of the MAC PDU load, whether a Logical Channel Identifier (LCID) or a multicast Service identifier (MSTID) is indicated in a protocol header, the difference of domain length and the like, when the protocol data unit is sent, the Logical Channel Identifier (LCID) or the multicast Service identifier (MSTID) or the protocol header is indicated or carried in the resource allocation information of a control channel, and the method can be simultaneously applied to the protocol header with the load containing one or more multicast broadcast Service connections (E-MBS Service) or the load containing one or more multicast broadcast Service contents (E-MBS Content) under two conditions, thereby providing a method for sending indication of the multicast broadcast connection protocol data unit.

The embodiments and features of the embodiments in the present application may be combined with each other without conflict.

The preferred embodiments of the present invention will be described in conjunction with the accompanying drawings, and it will be understood that they are described herein for the purpose of illustration and explanation and not limitation.

According to an embodiment of the present invention, a method for indicating transmission of a multicast broadcast connection protocol data unit is provided.

In an embodiment of the invention, a base station sends protocol data units of a multicast broadcast connection to subscriber stations. The protocol data unit comprises a protocol header and a load, wherein the data of the Service data SDU or the SDU segment in the load is from one or more multicast broadcast Service contents (E-MBSContent) or from one or more multicast broadcast Service connections (E-MBS Service), different multicast broadcast Service contents are distinguished by Logical Channel Identifiers (LCID), and different multicast broadcast Service connections are distinguished by multicast Service identifiers (MSTID).

In the embodiment of the invention, when the SDU or the SDU segment forming the PDU load comes from a plurality of multicast broadcast service contents, a plurality of corresponding Logical Channel Identifications (LCID) are carried in a protocol header of the PDU; or, in the embodiment of the present invention, when the SDU or SDU segment constituting the PDU payload is from multiple multicast broadcast service contents or multiple multicast broadcast service connections, corresponding multiple Logical Channel Identifiers (LCIDs) or multiple multicast service identifiers (MSTIDs) are carried in the resource allocation information of the control channel, and the sequence of the multiple Logical Channel Identifiers (LCIDs) or the multiple multicast service identifiers (MSTIDs) in the resource allocation information is consistent with the sequence of the multiple multicast broadcast service contents or multicast broadcast service connections constituting the PDU payload.

Based on the above different indication methods of Logical Channel Identifier (LCID) or multicast service identifier (MSTID), the embodiments of the present invention correspondingly provide three types of PDU header configuration forms, which are described below.

Protocol header of the first form

With this form of protocol header, the SDUs or SDU segments that make up the multicast broadcast protocol data unit payload come from one or more multicast broadcast service contents, and the one or more multicast broadcast service contents belong to a multicast broadcast service connection. The multicast service identifier for identifying the multicast broadcast service connection may be indicated in the resource allocation information of the control channel, and specifically, the multicast service identifier may be explicitly carried in the resource allocation information, or may be implicitly indicated by other information in the resource allocation information. When the data of the SDU or SDU fragment is from multiple multicast broadcast service contents, multiple Logical Channel Identifications (LCIDs) for distinguishing different multicast broadcast service contents are indicated in the protocol header.

The protocol header is a multicast broadcast protocol header provided by combining the compressed MAC header and the segmented packed extension header format in the current IEEE802.16m and an E-MBS multiplexing extension header with a logical channel identifier designed according to a unicast multiplexing extension header.

The multicast broadcast protocol header includes: an E-MBS compressed MAC header, possibly containing one or more extension headers; wherein the E-MBS compressed MAC header includes and is not limited to one or more of the following indication fields: the extension header indicates a field EH, a length field, a reserved field, etc. The structure of the multicast broadcast protocol header is shown in fig. 8A.

Specifically, the extension header indication field (EH) indicates whether the E-MBS compressed MAC header includes an extension header, which may specifically be represented by 1 bit, and indicates according to a value of the bit, for example, if the value of the bit is 1, it indicates that the MAC header includes an extension header, and otherwise, the bit does not include the extension header;

specifically, the length field indicates the length of the 1 st MAC SDU or SDU segment in the payload, and specifically may be 7 bits, 11 bits, or other positive integer bits;

specifically, the reserved field is located at the end of the MAC header, and is a reserved bit with a variable length, and is used for filling the E-MBS compressed MAC header so that the length of the E-MBS compressed MAC header is an integer multiple of 8 bits.

Further, when the extension header indication field in the E-MBS compressed MAC header is 1 (i.e. when the protocol header includes an extension header), the multicast broadcast protocol header simultaneously includes one or more extension headers. In particular, each extension header may include, but is not limited to, one or more of the following indication fields: a header termination identification field, an extended header type field, an extended header entity, etc. Wherein,

(1) the header termination identification field indicates whether the extension header is the last extension header, which may be represented by 1 bit, and indicates according to the value of the bit, for example, if the value is 1, it indicates that the extension header is the last extension header, otherwise, it is not;

(2) the extension header type field indicates the specific type of the extension header, and the extension header may be: E-MBS subsection packing expansion head, E-MBS multiplexing expansion head or other type E-MBS expansion head;

further, when the extension header is an E-MBS segment packed extension header for segmenting or packing an SDU or SDU segment from one multicast broadcast service content, the E-MBS segment packed extension header includes at least one of the following indication fields: a sequence number field, a segment control field, N (N is the number of SDUs or SDU segments in the load) field termination identifiers, N-1 length fields, a reserved field and the like. Wherein,

(1) the sequence number field indicates the sequence number of the SDU or SDU fragment, and may be specifically expressed by 10 bits;

(2) the segment control field is used to indicate segment control information, and may be expressed by 2 bits, for example, 00 indicates that the payload of the PDU consists of 1 or more SDUs, 01 indicates that the payload consists of 0, 1 or more SDUs plus the first segment of a certain SDU (1 SDU can be divided into three parts, a head segment, a tail segment and a middle segment), 10 indicates that the payload consists of the tail segment of a certain SDU plus 0, 1 or more SDUs, 11 indicates that the payload consists of the tail segment of a certain SDU plus 1 or more SDUs plus the head segment of a certain SDU, and 11 may also indicate that the payload consists of only the middle segment of a certain SDU;

(3) the N-1 length fields respectively indicate the lengths of N-1 MAC SDUs or SDU segments except the 1 st MAC SDU segment in the load, and the length fields can be 7 bits, 11 bits or other positive integer bits;

(4) n field termination marks, at least one field termination mark exists (even if there is no length field, the value of the field termination mark is 1 at this time), the first field termination mark is used to indicate whether there is a length field in the extension header entity, the rest N-1 field termination marks are respectively located after N-1 length fields and are used to indicate whether there is a length field after the field termination mark, which can be expressed by 1 bit, the value of 1 indicates that there is no length field after the field termination mark, otherwise, there is a field termination mark, when the number of SDU or SDU segments in PDU is 1, there is no length field and only one field termination mark in the extension header entity, and the field termination mark value is 1, indicating that there is no length field after it, otherwise, the value of the first field termination mark is 0, indicating that there is a length field after it is;

(5) the reserved domain is positioned at the tail of the E-MBS segmented packing expansion head, is a reserved bit, has variable length and is used for filling the integral multiple of the length of 8 bits of the E-MBS segmented packing expansion head.

Further, when the extension header is an E-MBS multiplexing extension header, the E-MBS multiplexing extension header is used for packet multiplexing of SDUs or SDU segments whose data come from one or more multicast broadcast service contents, and the E-MBS multiplexing extension header includes at least one of: one or M E-MBS multiplexing expansion head sub-blocks and a reserved domain, wherein each E-MBS multiplexing expansion head sub-block indicates the specific information of the corresponding multicast broadcast service content (or logic channel) in the load, and each E-MBS multiplexing expansion head sub-block comprises the following indication domains: a block termination identification field, a logical channel identification field, a segment control field, a sequence number field, a field termination identification, a length field, etc.; fig. 8B is a diagram illustrating the format of the E-MBS multiplexing extension header in this case, wherein,

(1) the block termination identification domain indicates whether other E-MBS multiplexing expansion head sub-blocks exist behind the E-MBS multiplexing expansion head sub-block, and can be expressed by 1 bit, and the value of 1 indicates that other E-MBS multiplexing expansion head sub-blocks exist behind the E-MBS multiplexing expansion head sub-block, otherwise, the value is not;

(2) the logical channel identification domain indicates the logical channel of the multicast broadcast service content corresponding to the E-MBS multiplexing expansion head sub-block, which can be 8 bits, 4 bits or other positive integer bits, each E-MBS multiplexing expansion head sub-block contains the logical channel identification domain, when the load only contains one multicast broadcast service content, namely the multicast broadcast multiplexing expansion head only contains one multicast broadcast multiplexing expansion head sub-block, the logical channel identification domain is a reserved special identification and indicates that the multicast broadcast multiplexing expansion head sub-block has no logical channel identification;

(3) the sequence number field indicates a load sequence number expressed by 10 bits;

(4) the segment control field indicates segment control information, which is expressed by 2 bits, 00 indicates that the payload consists of 1 or more SDUs, 01 indicates that the payload consists of 0, 1 or more SDUs plus the first segment of a certain SDU (1 SDU can be divided into three parts, namely a first segment, a last segment and a middle segment), 10 indicates that the payload consists of the last segment of a certain SDU plus 0, 1 or more SDUs, 11 indicates that the payload consists of the last segment of a certain SDU plus 1 or more SDUs plus the first segment of a certain SDU, and 11 can also indicate that the payload consists of only the middle segment of a certain SDU;

(5) the 1 st E-MBS multiplexing expansion head sub-block has N1-1 length domains, which respectively indicate the lengths of N1-1 SDUs or SDU segments except the 1 st (N1 is the number of SDUs or SDU segments under the multicast broadcast service content corresponding to the 1 st multicast broadcast multiplexing expansion head sub-block) which correspond to the E-MBS multiplexing expansion head sub-block, and the length of the 1 st SDU or SDU segment which corresponds to the 1 st E-MBS multiplexing expansion head sub-block and is under the multicast broadcast service content is indicated by the length domain in the compressed MAC head; for the rest M-1E-MBS multiplexing expansion head sub-blocks, the ith E-MBS multiplexing expansion head sub-block has Ni (Ni is the number of SDUs or SDU segments under the multicast broadcast service content corresponding to the ith multicast broadcast multiplexing expansion head sub-block) length domains, respectively indicates the length of Ni SDUs or SDU segments under the multicast broadcast service content corresponding to the ith E-MBS multiplexing expansion head sub-block, and the length domains can be 7 bits, 11 bits or other positive integer bits;

(6) the 1 st E-MBS multiplexing extension header sub-block has N1 domain termination identifiers, wherein, the 1 st domain termination identifier indicates whether the multicast broadcast multiplexing extension header sub-block contains a length domain, and the rest N1-1 domain termination identifiers are respectively positioned after the N1-1 length domains and are used for indicating whether the length domain still exists after the domain termination identifier; for the rest M-1 multicast broadcast multiplexing extension head sub-blocks, the ith multicast broadcast multiplexing extension head sub-block comprises Ni domain termination identifiers which are respectively positioned behind the Ni length domains and used for indicating whether the length domains still exist behind the domain termination identifiers; the value of the domain termination identifier is 0, which indicates that a length domain exists after the domain termination identifier, otherwise, the length domain does not exist;

(7) the reserved domain is positioned at the tail of the E-MBS multiplexing expansion head, is a reserved bit, has variable length and is used for filling the E-MBS multiplexing expansion head sub-block into integral multiple of 8 bits.

Protocol header of the second form

With this form of protocol header, the SDUs or SDU segments that make up the multicast broadcast protocol data unit payload come from one or more multicast broadcast service contents, and the one or more multicast broadcast service contents belong to a multicast broadcast service connection. The multicast service identifier for identifying the multicast broadcast service connection may be indicated in the resource allocation information of the control channel, and specifically, the multicast service identifier may be explicitly carried in the resource allocation information, or may be implicitly indicated by other information in the resource allocation information. When data of an SDU or SDU fragment constituting a protocol data unit payload is from a plurality of multicast broadcast service contents, a plurality of Logical Channel Identifications (LCIDs) for distinguishing different multicast broadcast service contents are indicated in a protocol header.

The protocol header is a multicast broadcast protocol header provided by combining the formats of a general MAC header, a segmented packing extension header and a multiplexing extension header in the existing IEEE802.16m and replacing a service stream identifier with a logical channel identifier.

The multicast broadcast protocol header includes: an E-MBS generic MAC header, possibly containing one or more extension headers; wherein, the E-MBS general MAC header comprises at least one of the following indication domains: a logical channel identification field, an extended header indication field EH, a length field and a reserved field, etc. The structure of the multicast broadcast protocol header is shown in fig. 9A.

Specifically, the logical channel identification field in the E-MBS universal MAC header indicates a logical channel corresponding to the 1 st E-MBS content in the load, which may be 4 bits, 8 bits, or other positive integer bits, and when the load only contains one multicast broadcast service content, the logical channel identification field in the E-MBS universal MAC header is a reserved special identifier, indicating that the E-MBS universal MAC header has no logical channel identifier;

specifically, the extension header indication field EH in the E-MBS generic MAC header indicates whether the E-MBS generic MAC header includes an extension header or not, and may specifically be represented by 1 bit, and is indicated by a value of the bit, for example, if the value is 1, it indicates that the MAC header includes an extension header, and otherwise, the MAC header does not include the extension header;

specifically, the length field in the E-MBS generic MAC header indicates the length of the 1 st SDU or SDU segment in the payload, and specifically may be 7 bits, 11 bits, or other positive integer bits;

specifically, the reserved field in the E-MBS generic MAC header is located at the end of the MAC header, is a reserved bit, has a variable length, and is used to complement the E-MBS generic MAC header so that the length of the E-MBS generic MAC header is an integer multiple of 8 bits.

Further, when the extension header indication field EH in the E-MBS generic MAC header is 1 (i.e. indicates that the protocol header includes an extension header), the multicast broadcast protocol header includes one or more E-MBS extension headers at the same time. Specifically, each E-MBS expansion head comprises at least one of the following indication fields: a header termination identification field, an extended header type field, an extended header entity, etc. Wherein,

(2) the extension header type field indicates the specific type of the extension header, and the extension header may be: E-MBS segmented packing expansion head, E-MBS multiplexing expansion head or other types of E-MBS expansion heads.

Further, when the extension header is an E-MBS segment packed extension header for segmenting or packing an SDU or SDU segment from one multicast broadcast service content, the E-MBS segment packed extension header includes at least one of the following indication fields: a sequence number field, a segment control field, N (N is an integer greater than 1 and represents the number of SDU or SDU segments in PDU) field termination marks, N-1 length fields, a reserved field and the like; wherein,

(1) the sequence number field represents a load sequence number, and can be specifically expressed by 10 bits;

(2) the segment control field indicates segment control information, which may be expressed by 2 bits, for example, 00 indicates that the payload consists of one or more SDUs, 01 indicates that the payload consists of 0, 1, or more SDUs plus a first segment of a certain SDU (one SDU may be divided into three parts, a first segment, a last segment, and a middle segment), 10 indicates that the payload consists of a last segment of a certain SDU plus 0, 1, or more SDUs, 11 indicates that the payload consists of a last segment of a certain SDU plus 1 or more SDUs plus a first segment of a certain SDU, and 11 may also indicate that the payload consists of only a middle segment of a certain SDU;

(3) n field termination marks, at least one field termination mark exists (even if there is no length field, the value of the field termination mark is 1 at this time), the first field termination mark is used to indicate whether there is a length field in the extension header entity, the rest N-1 field termination marks are respectively located behind N-1 length fields and are used to indicate whether there is a length field behind the field termination mark, which can be expressed by 1 bit, the value of 1 indicates that there is no length field behind the field termination mark, otherwise, if the number of SDU or SDU segments in PDU is 1, there is no length field in the extension header entity and only one field termination mark, and the field termination mark value is 1, indicating that there is no length field behind, otherwise, the value of the first field termination mark is 0, indicating that there is a length field behind it;

(4) the N-1 length fields respectively indicate the lengths of N-1 SDUs or SDU segments except the 1 st SDU in the load, and the length fields can be 7 bits, 11 bits or other positive integer bits;

Further, when the extension header is an E-MBS multiplexing extension header, the E-MBS multiplexing extension header is used for packet multiplexing of SDUs or SDU segments whose data come from one or more multicast broadcast service contents, and the E-MBS multiplexing extension header includes at least one of: one or M E-MBS multiplexing extension head sub-blocks and a reserved domain, wherein each E-MBS extension head sub-block indicates the specific information of the corresponding multicast broadcast service content (or logic channel) in the load, and comprises the following indication domains: a block termination identification field, a logical channel identification field, a segment control field, a sequence number field, a field termination identification, a length field, etc. Fig. 9B is a diagram illustrating the format of the E-MBS multiplexing extension header in this case, wherein,

(1) the block termination identification field indicates whether other multiplexing extension header sub-blocks exist after the multiplexing extension header sub-block, and can be expressed by 1 bit, and the value of 1 indicates that other multiplexing extension header sub-blocks exist after the multiplexing extension header sub-block, otherwise, the value does not exist;

(2) the logical channel identification domain indicates the logical channel of the multicast broadcast service content corresponding to the E-MBS multiplexing expansion head sub-block, the 1 st E-MBS multiplexing expansion head sub-block does not contain the logical channel identification of the E-MBS content corresponding to the E-MBS multiplexing expansion head sub-block, but is indicated by the logical channel identification in the E-MBS general MAC head, and the length of the logical channel identification can be 8 bits, 4 bits or other positive integer bits;

(3) the sequence number field indicates the sequence number of the load, expressed by 10 bits;

(4) the segment control field indicates segment control information, which is expressed by 2 bits, 00 indicates that the payload consists of one or more SDUs, 01 indicates that the payload consists of 0, 1 or more SDUs plus the first segment of a certain SDU (one SDU can be divided into three parts, namely a first segment, a last segment and a middle segment), 10 indicates that the payload consists of the last segment of a certain SDU plus 0, 1 or more SDUs, 11 indicates that the payload consists of the last segment of a certain SDU plus 1 or more SDUs plus the first segment of a certain SDU, and 11 may also indicate that the payload consists of only the middle segment of a certain SDU;

(5) the 1 st E-MBS multiplexing expansion head sub-block has N1-1 length domains, which respectively indicate the lengths of N1-1 SDUs or SDU segments except the 1 st (N1 is the number of SDUs or SDU segments under the multicast broadcast service content corresponding to the 1 st multicast broadcast multiplexing expansion head sub-block) which correspond to the E-MBS multiplexing expansion head sub-block, and the length of the 1 st SDU or SDU segment which corresponds to the 1 st E-MBS multiplexing expansion head sub-block and is under the multicast broadcast service content is indicated by the length domain in the general MAC head; for the rest M-1E-MBS multiplexing expansion head sub-blocks, the ith E-MBS multiplexing expansion head sub-block has Ni (Ni is the number of SDUs or SDU segments under the multicast broadcast service content corresponding to the ith multicast broadcast multiplexing expansion head sub-block) length domains, respectively indicates the length of Ni SDUs or SDU segments under the multicast broadcast service content corresponding to the ith E-MBS multiplexing expansion head sub-block, and the length domains can be 7 bits, 11 bits or other positive integer bits;

(6) the 1 st E-MBS multiplexing extension header sub-block has N1 domain termination identifiers, wherein, the 1 st domain termination identifier indicates whether the multicast broadcast multiplexing extension header sub-block contains a length domain, and the rest N1-1 domain termination identifiers are respectively positioned after the N1-1 length domains and are used for indicating whether the length domain still exists after the domain termination identifier; for the rest M-1E-MBS multiplexing expansion head sub-blocks, the ith E-MBS multiplexing expansion head sub-block has Ni domain termination marks which are respectively positioned behind the Ni length domains and used for indicating whether the length domains still exist behind the domain termination marks; the value of the domain termination identifier is 0, which indicates that a length domain exists after the domain termination identifier, otherwise, the length domain does not exist;

(7) the reserved domain is positioned at the tail of the E-MBS multiplexing expansion head, is a reserved bit, has variable length and is used for filling the integer multiple of the sub-block length of the E-MBS multiplexing expansion head to 8 bits.

Protocol header of the third form

When the protocol header in this form is used, the SDU or SDU segment constituting the multicast broadcast protocol data unit load comes from one or more multicast broadcast service contents belonging to one multicast broadcast service connection, or the SDU or SDU segment constituting the multicast broadcast protocol data unit load comes from one or more multicast broadcast service connections. The Logical Channel Identifier (LCID) for distinguishing different multicast broadcast service contents or the multicast service identifier (MSTID) for distinguishing different multicast broadcast service connections is carried in the resource allocation indication message, specifically, the multicast service identifier or the logical channel identifier may be carried explicitly in the resource allocation information, or the multicast service identifier or the logical channel identifier may be implicitly indicated by other information in the resource allocation information without being indicated in the protocol header, and an order of the Logical Channel Identifier (LCID) or the multicast service identifier (MSTID) in the resource allocation indication message is consistent with an order of the multicast broadcast service contents or the multicast broadcast service connections corresponding to the SDU or SDU fragment in the protocol data unit load.

The protocol header is a multicast broadcast protocol header provided by combining the formats of a compressed MAC header and a segmented packed extension header in the existing IEEE802.16m and an E-MBS multiplexing extension header without a logical channel identifier designed according to a unicast multiplexing extension header.

The multicast broadcast protocol header includes: an E-MBS compressed MAC header, possibly containing one or more extension headers; wherein, the E-MBS compressed MAC header comprises but is not limited to one or more of the following indication fields: the extension header indicates a field EH, a length field, a reserved field, and the like. The structure of the multicast broadcast protocol header is shown in figure 10A,

specifically, the extended header indication field EH of the E-MBS compressed MAC header indicates whether an extended header is included after the MAC header in a protocol header of the PDU, which may specifically be represented by 1 bit, and different states are indicated by different values of the bit, for example, if the value of the bit is 1, it indicates that an extended header is included after the MAC header, otherwise, it is not included;

specifically, the length field in the E-MBS compressed MAC header indicates the length of the 1 st SDU or SDU segment in the payload, and may specifically be 7 bits, 11 bits, or other positive integer bits;

specifically, the reserved field in the E-MBS compressed MAC header is located at the end of the MAC header, is a reserved bit with a variable length, and is used to complement the E-MBS compressed MAC header so that the length of the E-MBS compressed MAC header is an integer multiple of 8 bits.

Further, when the extension header indication field EH in the E-MBS compressed MAC header is 1, the multicast broadcast protocol header simultaneously contains one or more extension headers. Specifically, each extension header includes at least one of the following indication fields: a header termination identification field, an extended header type field, an extended header entity, etc., wherein,

(1) the header termination identification field indicates whether the extension header is the last extension header, and may be represented by 1 bit, and indicates according to a value of the bit, for example, a value of 1 indicates that the extension header is the last extension header, otherwise, the extension header is not;

Further, when the extension header is an E-MBS segment packed extension header for segmenting or packing an SDU or SDU segment from one multicast broadcast service content, the E-MBS segment packed extension header includes at least one of the following indication fields: a sequence number field, a segment control field, N (N is an integer greater than 1 and represents the number of MAC SDU or SDU segments) fields, a termination identifier, a length field, a reserved field, etc. Wherein,

(2) the segment control field indicates segment control information, which may be expressed by 2 bits, 00 indicates that the payload consists of one or more SDUs, 01 indicates that the payload consists of 0, 1, or more SDUs plus a first segment of a certain SDU (one SDU may be divided into three parts, a first segment, a last segment, and a middle segment), 10 indicates that the payload consists of a last segment of a certain SDU plus 0, 1, or more SDUs, 11 indicates that the payload consists of a last segment of a certain SDU plus 1 or more SDUs plus a first segment of a certain SDU, and 11 may also indicate that the payload consists of only a middle segment of a certain SDU;

(3) the length field is N-1 (N represents the number of MAC SDU or SDU segments), which respectively indicates the length of N-1 SDU or SDU segments except the 1 st SDU in the load, and the length field can be 7 bits, 11 bits or other positive integer bits;

(4) the domain termination identifiers are N, at least one domain termination identifier exists (even if there is no length domain, the value of the domain termination identifier is 1 at this time), the first domain termination identifier is used to indicate whether there is a length domain in the extension header entity, the rest N-1 domain termination identifiers are respectively located after N-1 length domains (i.e. there is a domain termination identifier after each length domain of N-1 length domains), and are used to indicate whether there is a length domain after the domain termination identifier, which is expressed by 1 bit, the value of 1 indicates that there is no length domain after the domain termination identifier, otherwise, if the number of SDU or SDU segments in PDU is 1, there is no length domain in the extension header entity, and there is only one domain termination identifier, and the value of the domain termination identifier is 1, indicating that there is no length domain thereafter, otherwise, the value of the first domain termination identifier is 0, indicating that a length field follows;

Further, when the extension header is an E-MBS multiplexing extension header, the E-MBS multiplexing extension header is used for packet multiplexing of SDUs or SDU segments whose data come from one or more multicast broadcast service contents, and the E-MBS multiplexing extension header includes at least one of: one or M E-MBS multiplexing expansion head sub-blocks and a reserved domain, wherein each E-MBS multiplexing expansion head sub-block indicates the specific information corresponding to the multicast broadcast service content or the multicast broadcast service connection in the load, and each E-MBS multiplexing expansion head sub-block comprises the following indication domains: a block termination identification field, a segment control field, a sequence number field, a field termination identification, a length field, etc. Fig. 10B is a diagram illustrating the format of the E-MBS multiplexing extension header in this case, wherein,

(2) the sequence number field indicates the sequence number of the load, expressed by 10 bits;

(3) the segment control field indicates segment control information, which is expressed by 2 bits, 00 indicates that the payload consists of one or more SDUs, 01 indicates that the payload consists of 0, 1 or more SDUs plus the first segment of a certain SDU (one SDU can be divided into three parts, namely a first segment, a last segment and a middle segment), 10 indicates that the payload consists of the last segment of a certain SDU plus 0, 1 or more SDUs, 11 indicates that the payload consists of the last segment of a certain SDU plus 1 or more SDUs plus the first segment of a certain SDU, and 11 may also indicate that the payload consists of only the middle segment of a certain SDU;

(4) the 1 st E-MBS multiplexing expansion head sub-block has N1-1 length domains, respectively indicates the length of N1-1 SDUs or SDU segments except the 1 st SDU or SDU segment under the condition that the E-MBS multiplexing expansion head sub-block corresponds to the multicast broadcast service content or the multicast broadcast service connection, and the length of the 1 st SDU or SDU segment under the condition that the E-MBS multiplexing expansion head sub-block corresponds to the multicast broadcast service content or the multicast broadcast service connection is indicated by the length domain in the multicast broadcast compression MAC head; the other M-1E-MBS multiplexing expansion head sub-blocks, the ith E-MBS multiplexing expansion head sub-block has Ni length domains which respectively indicate the length of Ni SDUs or SDU segments under the connection of the multicast broadcast service content or the multicast broadcast service corresponding to the ith E-MBS multiplexing expansion head sub-block, and the length domains can be 7 bits, 11 bits or other positive integer bits;

(5) the 1 st E-MBS multiplexing extension header sub-block has N1 domain termination identifiers, wherein, the 1 st domain termination identifier indicates whether the multicast broadcast multiplexing extension header sub-block contains a length domain, and the rest N1-1 domain termination identifiers are respectively positioned after the N1-1 length domains and are used for indicating whether the length domain still exists after the domain termination identifier; for the rest M-1E-MBS multiplexing expansion head sub-blocks, the ith E-MBS multiplexing expansion head sub-block has Ni domain termination marks which are respectively positioned behind the Ni length domains and used for indicating whether the length domains still exist behind the domain termination marks; the value of the domain termination identifier is 0, which indicates that a length domain exists after the domain termination identifier, otherwise, the length domain does not exist;

(6) the reserved domain is positioned at the tail of the E-MBS multiplexing expansion head, is a reserved bit, has variable length and is used for filling the integer multiple of the sub-block length of the E-MBS multiplexing expansion head to 8 bits.

The technical solutions provided by the embodiments of the present invention are described below by specific examples.

Example one

In this embodiment, the SDU or SDU segment constituting the multicast broadcast protocol data unit payload is from one multicast broadcast Service Content (E-MBS Content) or one multicast broadcast Service connection (E-MBS Service), and the length field in the protocol header is 7 bits.

When the protocol data unit is sent, the protocol header of the first form or the protocol header of the third form may be used, and specifically, the structure of the protocol header is as shown in fig. 11. Wherein, the extension head type field in the multicast broadcast protocol head is indicated as E-MBS segmented packing extension head.

It is noted that no Logical Channel Identification (LCID) or multicast traffic identification (MSTID) is needed in the protocol header, since the load comes from one multicast broadcast traffic content or one multicast broadcast traffic connection. In addition, the length of the 1 st SDU or SDU fragment constituting the payload is indicated by a length field of 7 bits in the MAC header, and the lengths of the 2 nd to nth (N is an integer greater than 1 indicating the number of fragments of the MAC SDU or SDU) SDUs or SDU fragments are indicated by a length field of N-1 7 bits in the segment packing extension header.

Example two

In this embodiment, the SDU or SDU segment that constitutes the multicast broadcast protocol data unit payload is from one multicast broadcast service content, and the length field in the protocol header is 7 bits.

When the protocol data unit is sent, the protocol header in the second form, that is, the multicast broadcast protocol header combining the common MAC header and the segmented packing extension header format in the current IEEE802.16m, is adopted, as shown in fig. 12. Wherein, the extension head type field in the multicast broadcast protocol head is indicated as E-MBS segmented packing extension head.

It is noted that since the payload is from a multicast broadcast content, no Logical Channel Identification (LCID) is needed in the protocol header, and the 4-bit logical channel identification field in the MAC header is used as a meaningless reserved field. In addition, the length of the 1 st SDU or SDU fragment constituting the payload is indicated by a length field of 7 bits in the MAC header, and the lengths of the 2 nd to nth (N is an integer greater than 1 indicating the number of fragments of the MAC SDU or SDU) SDUs or SDU fragments are indicated by a length field of N-1 7 bits in the segment packing extension header.

EXAMPLE III

In this embodiment, the SDU or SDU segment constituting the multicast broadcast protocol data unit payload is from one multicast broadcast Service Content (E-MBS Content) or one multicast broadcast Service connection (E-MBS Service), and the length field in the protocol header is 11 bits.

When the protocol data unit is transmitted, the protocol header of the first form or the protocol header of the third form is used, and the structure of the multicast broadcast protocol header is shown in fig. 13. Wherein, the extension head type field in the multicast broadcast protocol head is indicated as E-MBS segmented packing extension head.

It is noted that no Logical Channel Identification (LCID) or multicast traffic identification (MSTID) is needed in the protocol header, since the load comes from one multicast broadcast traffic content or one multicast broadcast traffic connection. In addition, the length of the 1 st SDU or SDU fragment constituting the payload is indicated by a length field of 11 bits in the MAC header, and the lengths of the 2 nd to nth (N is an integer greater than 1 indicating the number of fragments of the MAC SDU or SDU) SDUs or SDU fragments are indicated by a length field of N-1 11 bits in the segment packing extension header.

Example four

In this embodiment, the SDU or SDU segment that constitutes the multicast broadcast protocol data unit payload is from one multicast broadcast service content, and the length field in the protocol header is 11 bits.

When the protocol data unit is transmitted, the protocol header of the second form is adopted, that is, the multicast broadcast protocol header combining the common MAC header and the segmented packing extension header format in the current IEEE802.16m, and the structure of the multicast broadcast protocol header is shown in fig. 14. Wherein, the extension head type field in the multicast broadcast protocol head is indicated as E-MBS segmented packing extension head.

It is noted that since the payload is from a multicast broadcast content, no Logical Channel Identification (LCID) is needed in the protocol header, and the 4-bit logical channel identification field in the MAC header is used as a meaningless reserved field. In addition, the length of the 1 st SDU or SDU fragment constituting the payload is indicated by a length field of 11 bits in the MAC header, and the lengths of the 2 nd to nth (N is an integer greater than 1 indicating the number of fragments of the MAC SDU or SDU) SDUs or SDU fragments are indicated by a length field of N-1 11 bits in the segment packing extension header.

EXAMPLE five

In this embodiment, the SDU or SDU segment constituting the multicast broadcast protocol data unit payload is from one or more multicast broadcast service contents belonging to one multicast broadcast service connection, and the protocol header has a length field of 7 bits and a logical channel field of 8 bits.

When the protocol data unit is sent, the protocol header of the first form is adopted, that is, a Logical Channel Identifier (LCID) is indicated in the protocol header, and a multicast broadcast protocol header combining a compressed MAC header in the existing IEEE802.16m and an E-MBS multiplexing extension header with a Logical Channel Identifier (LCID) designed according to a unicast multiplexing extension header is adopted, and the structure of the multicast broadcast protocol header is shown in fig. 15.

Wherein, the extension header type field in the multicast broadcast protocol header is indicated as E-MBS multiplexing extension header, as shown in fig. 15A. Or, the extension header does not include the extension header type field, and the extension header entity is an E-MBS multiplexing extension header, as shown in fig. 15B.

In particular, when the SDU or SDU fragment constituting the multicast broadcast protocol data unit payload is from only one multicast broadcast service content, the E-MBS multiplexing extension header contains only one E-MBS multiplexing extension header sub-block, and the protocol header does not contain a logical channel identification.

It should be noted that, when the load is from multiple multicast broadcast service contents, each E-MBS multiplexing extension header sub-block includes an 8-bit logical channel identifier LCID, which includes an E-MBS multiplexing extension header sub-block corresponding to the 1 st multicast broadcast service content, and is different from the 2 nd to mth (M is the number of E-MBS multiplexing extension header sub-blocks in the extension header) E-MBS multiplexing extension header sub-blocks, the 1 st E-MBS multiplexing extension header sub-block does not include the length indication of the 1 st SDU or SDU segment in the multicast broadcast service content, and the length of the 1 st SDU or SDU segment in the 1 st multicast broadcast service content is indicated by the length field of 7 bits in the extension header.

EXAMPLE six

When the protocol data unit is transmitted, the protocol header of the second form described above is used, that is, the Logical Channel Identifier (LCID) is indicated in the protocol header, and the multicast broadcast protocol header of the service stream identifier is replaced by the Logical Channel Identifier (LCID) in combination with the current format of the universal MAC header and the multiplexing extension header in ieee802.16m, and the structure of the multicast broadcast protocol header is shown in fig. 16.

Wherein, the extension header type field in the multicast broadcast protocol header is indicated as E-MBS multiplexing extension header, as shown in fig. 16A. Or, the extension header does not include the extension header type field, and the extension header entity is an E-MBS multiplexing extension header, as shown in fig. 16B.

In particular, when the SDU or SDU segment forming the multicast broadcast protocol data unit load comes from a multicast broadcast service content, the E-MBS multiplexing extension header only contains one E-MBS multiplexing extension header sub-block, and the protocol header does not contain a logical channel identifier.

It should be noted that, when the load is from multiple multicast broadcast service contents, different from the 2 nd to mth (M is the number of the E-MBS multiplexing extension header sub-blocks in the extension header) E-MBS multiplexing extension header sub-blocks, the 1 st E-MBS multiplexing extension header sub-block does not include a logical channel identifier LCID of 8 bits, meanwhile, the 1 st E-MBS multiplexing extension header sub-block does not include the length indication of the 1 st SDU or SDU segment in the multicast broadcast service content, and the length of the 1 st SDU or SDU segment in the 1 st multicast broadcast service content is indicated by the length field of 7 bits in the extension header.

EXAMPLE seven

In this embodiment, the SDU or SDU segment constituting the multicast broadcast protocol data unit payload is from one or more multicast broadcast service contents, and the multicast broadcast service contents belong to one multicast broadcast service connection, and the length field in the protocol header is 11 bits and the logical channel field is 8 bits.

When the protocol data unit is sent, the protocol header in the first form described above is used, that is, the Logical Channel Identifier (LCID) is indicated in the protocol header, and a multicast broadcast protocol header combining the compressed MAC header in the current ieee802.16m and the E-MBS multiplexing extension header with the Logical Channel Identifier (LCID) and designed according to the unicast multiplexing extension header is used, and the structure of the multicast broadcast protocol header is shown in fig. 17.

Wherein, the extension header type field in the multicast broadcast protocol header is indicated as E-MBS multiplexing extension header, as shown in fig. 17A. Or, the extension header does not include the extension header type field, and the extension header entity is an E-MBS multiplexing extension header, as shown in fig. 17B.

It should be noted that, when the load is from multiple multicast broadcast service contents, each E-MBS multiplexing extension header sub-block includes an 8-bit logical channel identifier LCID, which includes an E-MBS multiplexing extension header sub-block corresponding to the 1 st multicast broadcast service content, and is different from the 2 nd to mth (where M is the number of E-MBS multiplexing extension header sub-blocks in the extension header) E-MBS multiplexing extension header sub-blocks, the 1 st E-MBS multiplexing extension header sub-block does not include the length indication of the 1 st SDU or SDU segment in the multicast broadcast service content, and the length of the 1 st SDU or SDU segment in the 1 st multicast broadcast service content is indicated by the length field of 11 bits in the extension header.

Example eight

In this embodiment, the SDU or SDU segment constituting the multicast broadcast protocol data unit load is derived from one or more multicast broadcast service contents, and the multicast broadcast service contents belong to one multicast broadcast service connection, and the length field in the protocol header is 11 bits and the logical channel field is 8 bits, when the protocol data unit is transmitted.

When the protocol data unit is transmitted, the protocol header of the second form described above is used, that is, the Logical Channel Identifier (LCID) is indicated in the protocol header, and the multicast broadcast protocol header of the service stream identifier is replaced with the Logical Channel Identifier (LCID) by using the format of the common MAC header and the multiplexing extension header in the current ieee802.16m, where the structure of the multicast broadcast protocol header is shown in fig. 18.

Wherein, the extension header type field in the multicast broadcast protocol header is indicated as E-MBS multiplexing extension header, as shown in fig. 18A. Or, the extension header does not include the extension header type field, and the extension header entity is an E-MBS multiplexing extension header, as shown in fig. 18B.

It should be noted that, when the load is from multiple multicast broadcast service contents, unlike the 2 nd to mth (M is the number of the E-MBS multiplexing extension header sub-blocks in the extension header) E-MBS multiplexing extension header sub-blocks, the 1 st E-MBS multiplexing extension header sub-block does not include a Logical Channel Identifier (LCID) of 8 bits, and meanwhile, the 1 st E-MBS multiplexing extension header sub-block does not include the length indication of the 1 st SDU or SDU segment in the multicast broadcast service content, and the length of the 1 st SDU or SDU segment in the 1 st multicast broadcast service content is indicated by the length field of 11 bits in the extension header.

Example nine

In this embodiment, the SDU or SDU segment constituting the multicast broadcast protocol data unit payload is from one or more multicast broadcast service contents belonging to one multicast broadcast service connection, and the protocol header has a length field of 7 bits and a logical channel field of 4 bits.

When the protocol data unit is sent, the protocol header of the first form described above is adopted, that is, the Logical Channel Identifier (LCID) is indicated in the protocol header, and a multicast broadcast protocol header combining the compressed MAC header in the current ieee802.16m and the E-MBS multiplexing extension header with the Logical Channel Identifier (LCID) designed according to the unicast multiplexing extension header is adopted, and the structure of the multicast broadcast protocol header is shown in fig. 19.

Wherein, the extension header type field in the multicast broadcast protocol header is indicated as E-MBS multiplexing extension header, as shown in fig. 19A. Or, the extension header does not include the extension header type field, and the extension header entity is an E-MBS multiplexing extension header, as shown in fig. 19B.

It should be noted that, when the load is from multiple multicast broadcast service contents, each E-MBS multiplexing extension header sub-block includes a 4-bit Logical Channel Identifier (LCID), which includes an E-MBS multiplexing extension header sub-block corresponding to the 1 st multicast broadcast service content, and is different from the 2 nd to mth (M is the number of E-MBS multiplexing extension header sub-blocks in the extension header) E-MBS multiplexing extension header sub-blocks, the 1 st E-MBS multiplexing extension header sub-block does not include the length indication of the 1 st SDU or SDU segment in the multicast broadcast service content, and the length of the 1 st SDU or SDU segment in the 1 st multicast broadcast service content is indicated by the length field of 7 bits in the extension header.

Example ten

When the protocol data unit is transmitted, the protocol header of the second form described above is used, that is, the Logical Channel Identifier (LCID) is indicated in the protocol header, and the multicast broadcast protocol header of the service stream identifier is replaced by the Logical Channel Identifier (LCID) in combination with the current format of the universal MAC header and the multiplexing extension header in ieee802.16m, where the structure of the multicast broadcast protocol header is shown in fig. 20.

Wherein, the extension header type field in the multicast broadcast protocol header is indicated as E-MBS multiplexing extension header, as shown in fig. 20A. Or, the extension header does not include the extension header type field, and the extension header entity is an E-MBS multiplexing extension header, as shown in fig. 20B.

It should be noted that, when the load is from multiple multicast broadcast service contents, unlike the 2 nd to mth (M is the number of the E-MBS multiplexing extension header sub-blocks in the extension header) E-MBS multiplexing extension header sub-blocks, the 1 st E-MBS multiplexing extension header sub-block does not include a 4-bit Logical Channel Identifier (LCID), and meanwhile, the 1 st E-MBS multiplexing extension header sub-block does not include the length indication of the 1 st SDU or SDU segment in the multicast broadcast service content, and the length of the 1 st SDU or SDU segment in the 1 st multicast broadcast service content is indicated by a 7-bit length field in the extension header.

EXAMPLE eleven

In this embodiment, the SDU or SDU segment constituting the multicast broadcast protocol data unit payload is from one or more multicast broadcast service contents belonging to one multicast broadcast service connection, and the protocol header has a length field of 11 bits and a logical channel field of 4 bits.

When the protocol data unit is sent, the protocol header in the first form described above is used, that is, the Logical Channel Identifier (LCID) is indicated in the protocol header, and a multicast broadcast protocol header combining the compressed MAC header in the current ieee802.16m and the E-MBS multiplexing extension header with the Logical Channel Identifier (LCID) and designed according to the unicast multiplexing extension header is used, and the structure of the multicast broadcast protocol header is shown in fig. 21.

Wherein, the extension header type field in the multicast broadcast protocol header is indicated as E-MBS multiplexing extension header, as shown in fig. 21A. Or, the extension header does not include the extension header type field, and the extension header entity is an E-MBS multiplexing extension header, as shown in fig. 21B.

It should be noted that, when the load is from multiple multicast broadcast service contents, each E-MBS multiplexing extension header sub-block includes a 4-bit Logical Channel Identifier (LCID), which includes an E-MBS multiplexing extension header sub-block corresponding to the 1 st multicast broadcast service content, and is different from the 2 nd to mth (M is the number of E-MBS multiplexing extension header sub-blocks in the extension header) E-MBS multiplexing extension header sub-blocks, the 1 st E-MBS multiplexing extension header sub-block does not include the length indication of the 1 st SDU or SDU segment in the multicast broadcast service content, and the length of the 1 st SDU or SDU segment in the 1 st multicast broadcast service content is indicated by the length field of 11 bits in the extension header.

Example twelve

When the protocol data unit is transmitted, the protocol header of the second form described above is used, that is, the Logical Channel Identifier (LCID) is indicated in the protocol header, and the multicast broadcast protocol header of the service stream identifier is replaced with the Logical Channel Identifier (LCID) by using the format of the common MAC header and the multiplexing extension header in the current ieee802.16m, where the structure of the multicast broadcast protocol header is shown in fig. 22.

Wherein, the extension header type field in the multicast broadcast protocol header is indicated as E-MBS multiplexing extension header, as shown in fig. 22A. Or, the extension header does not include the extension header type field, and the extension header entity is an E-MBS multiplexing extension header, as shown in fig. 22B.

It should be noted that, when the load is from multiple multicast broadcast service contents, unlike the 2 nd to mth (M is the number of the E-MBS multiplexing extension header sub-blocks in the extension header) E-MBS multiplexing extension header sub-blocks, the 1 st E-MBS multiplexing extension header sub-block does not include a 4-bit Logical Channel Identifier (LCID), and meanwhile, the 1 st E-MBS multiplexing extension header sub-block does not include the length indication of the 1 st SDU or SDU segment in the multicast broadcast service content, and the length of the 1 st SDU or SDU segment in the 1 st multicast broadcast service content is indicated by the length field of 11 bits in the extension header.

EXAMPLE thirteen

In this embodiment, the SDU or SDU segment constituting the multicast broadcast protocol data unit payload is from one or more multicast broadcast service contents belonging to one multicast broadcast service connection, or the SDU or SDU segment constituting the multicast broadcast protocol data unit payload is from one or more multicast broadcast service connections, and the length field in the protocol header is 7 bits.

When the pdu is sent, a protocol header in the third form as described above is adopted, that is, a multicast service identifier (MSTID) or a Logical Channel Identifier (LCID) is indicated in the resource allocation information of the control channel, specifically, the multicast service identifier may be explicitly carried in the resource allocation information, or the multicast service identifier may be implicitly indicated by other information in the resource allocation information, and the order of the Logical Channel Identifier (LCID) or the multicast service identifier (MSTID) indicated in the resource allocation information corresponds to the multicast broadcast service content multiplexed in the load or the multicast broadcast service connection multiplexed in one-to-one manner, and the structure of the multicast broadcast protocol header is shown in fig. 23.

Wherein, the extension header type field in the multicast broadcast protocol header is indicated as E-MBS multiplexing extension header, as shown in fig. 23A. Or, the extension header does not include the extension header type field, and the extension header entity is an E-MBS multiplexing extension header, as shown in fig. 23B.

In particular, when the SDU or SDU fragment constituting the multicast broadcast protocol data unit payload is from one multicast broadcast service content or from one multicast broadcast service connection, the E-MBS multiplexing extension header contains only one E-MBS multiplexing extension header sub-block.

It should be noted that, when the load is from multiple multicast broadcast service contents or multiple multicast broadcast service connections, each E-MBS multiplexing extension header sub-block does not include a Logical Channel Identifier (LCID) or a multicast service identifier (MSTID), and is different from 2 nd to mth (M is the number of E-MBS multiplexing extension header sub-blocks in the extension header) E-MBS multiplexing extension header sub-blocks, the 1 st E-MBS multiplexing extension header sub-block does not include the multicast broadcast service content or the length indication of the 1 st SDU or SDU segment under the multicast broadcast service connection, and the length of the 1 st multicast broadcast service content or the 1 st SDU or SDU segment under the 1 st multicast broadcast service connection is indicated by a length field of 7 bits in the extension header.

Example fourteen

In this embodiment, the SDU or SDU segment constituting the multicast broadcast protocol data unit payload is from one or more multicast broadcast service contents belonging to one multicast broadcast service connection, or the SDU or SDU segment constituting the multicast broadcast protocol data unit payload is from one or more multicast broadcast service connections, and the length field in the protocol header is 11 bits.

When the pdu is sent, the above-mentioned protocol header in the third form is adopted, that is, the Logical Channel Identifier (LCID) or the multicast service identifier (MSTID) is carried in the resource allocation information of the control channel, and the sequence of the Logical Channel Identifier (LCID) or the multicast service identifier (MSTID) in the resource allocation information corresponds to the multicast broadcast service content multiplexed in the load or the multicast broadcast service multiplexed one-to-one, and the structure of the multicast broadcast protocol header is shown in fig. 24.

Wherein, the extension header type field in the multicast broadcast protocol header is indicated as E-MBS multiplexing extension header, as shown in fig. 24A. Or, the extension header does not include the extension header type field, and the extension header entity is an E-MBS multiplexing extension header, as shown in fig. 24B.

It should be noted that, when the load is from multiple multicast broadcast service contents or multiple multicast broadcast service connections, each E-MBS multiplexing extension header sub-block does not include a Logical Channel Identifier (LCID) or a multicast service identifier (MSTID), and is different from 2 nd to mth (M is the number of E-MBS multiplexing extension header sub-blocks in the extension header) E-MBS multiplexing extension header sub-blocks, the 1 st E-MBS multiplexing extension header sub-block does not include the length indication of the 1 st SDU or SDU segment under the multicast broadcast service contents or multicast broadcast service connections, and the length of the 1 st SDU or SDU segment under the 1 st multicast broadcast service contents or multicast broadcast service connections is indicated by a length field of 11 bits in the extension header.

As described above, with the technical solution provided by the embodiment of the present invention, when sending a multicast broadcast connection protocol data unit, a Logical Channel Identifier (LCID) or a multicast service identifier (MSTID) is indicated in a protocol header or carried in resource allocation information of a control channel, and by designing a format of a multicast broadcast connection protocol header under different conditions, several unified MAC layer header format selections are provided for being suitable for sending the multicast broadcast connection protocol data unit. The protocol data unit sending indication method designed aiming at the multicast broadcast connection characteristics provides a flexible indication mode for sending the protocol data unit special for the multicast broadcast connection, reduces the overhead of multicast broadcast connection signaling, realizes the high-efficiency transmission of multicast broadcast connection services, and improves the utilization rate of air interface resources.

The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A method for indicating transmission of a multicast broadcast connection protocol data unit, comprising:

the base station sends a protocol data unit of the multicast broadcast connection to the subscriber station, wherein the protocol data unit comprises: protocol header, payload.

2. The method according to claim 1, wherein the payload of the protocol data unit is composed of one or more service data units, SDUs, or SDU segments, the data of which is from one or more multicast broadcast service contents belonging to one multicast broadcast service connection.

3. The method of claim 2, wherein when the data of the SDU or SDU fragment is from multiple multicast broadcast service contents, the method further comprises:

and the protocol head of the protocol data unit carries an identifier for indicating the multicast broadcast service content, and the resource allocation information of the control channel indicates a multicast service identifier for identifying the multicast broadcast service connection.

4. The method of claim 3, wherein the protocol header comprises a multicast broadcast compressed MAC header.

5. The method of claim 4, wherein the multicast broadcast compressed MAC header comprises at least one of the following fields of indication: an extension header indication field indicating whether the protocol header includes an extension header, a length field indicating the length of the SDU or SDU fragment constituting the payload, and a reserved field.

6. The method of claim 3, wherein the protocol header comprises a multicast broadcast generic MAC header.

7. The method of claim 6, wherein the multicast broadcast generic MAC header comprises at least one of the following indication fields: an identification field for indicating the content of the multicast broadcast service, an extension header indication field for indicating whether the protocol header contains an extension header, a length field for indicating the length of the SDU or the SDU segment forming the load, and a reserved field.

8. The method of claim 7, wherein when the data of the SDU or SDU fragment constituting the payload is from a multicast broadcast service content, the special identifier indicating that the identifier field of the multicast broadcast service content is reserved indicates that the multicast broadcast generic MAC header has no identifier indicating that the respective multicast broadcast service content is available.

9. The method according to claim 5 or 7, wherein when the extension header indication field indicates that the protocol header contains an extension header, the protocol header further comprises: one or more expansion heads.

10. The method of claim 9, wherein each extension header comprises at least one of the following indicator fields: indicating whether the extension header is a header termination identification field of the last extension header of the protocol header, indicating a type of the extension header, an extension header type field, an extension header entity, and a reserved field, wherein the type of the extension header includes: a multicast broadcast segment packing extension head and a multicast broadcast multiplexing extension head.

11. The method of claim 10, wherein when the extension header is a multicast broadcast segment packing extension header, the extension header is used to segment or pack SDUs or SDU segments from a multicast broadcast service content.

12. The method of claim 11, wherein when the extension header is a multicast broadcast segment packed extension header, the extension header entity comprises the following indication fields: a sequence number field indicating the sequence number of the SDU or SDU segment forming the load, a segment control field indicating segment control information, N-1 length fields, and N field termination identifiers indicating the termination of the length fields, wherein N is the number of the SDU or SDU segment forming the load.

13. The method of claim 10, wherein when the extension header is a multicast broadcast multiplexing extension header, the extension header is used for packet multiplexing of SDUs or SDU segments from one or more multicast broadcast service contents.

14. The method of claim 13, wherein when the extension header is a multicast broadcast multiplex extension header, the extension header entity comprises at least one of: one or more multicast broadcast multiplexing extension head sub-blocks and a reserved domain, wherein each multicast broadcast multiplexing extension head sub-block corresponds to one multicast broadcast service content contained in the load.

15. The method of claim 14, wherein the multicast broadcast multiplexing extension header sub-block is used to describe the SDU or SDU segment of its corresponding multicast broadcast service content, and includes the following indication fields: a block termination identification field indicating whether the extension head sub-block is the last extension head sub-block, an identification field for indicating the content of the multicast broadcast service, a segment control field, a sequence number field, a field termination identification and a length field.

16. The method of claim 15,

if the protocol header comprises a multicast broadcast compressed MAC header, each multicast broadcast multiplex extension header sub-block comprises an identifier for indicating multicast broadcast service content, and when the data of the SDU or the SDU segment is from one multicast broadcast service content, the identifier field for indicating the multicast broadcast service content is a reserved special identifier which indicates that the multicast broadcast multiplex extension header sub-block does not have an identifier for indicating the multicast broadcast service content;

if the protocol header includes a multicast broadcast generic MAC header, the 1 st multicast broadcast multiplex extension header sub-block does not contain an identifier for indicating the contents of the multicast broadcast service.

17. The method of claim 15,

for the length field, the 1 st multicast broadcast multiplexing extension header sub-block includes N1-1 length fields, and the ith multicast broadcast multiplexing extension header sub-block in the rest multicast broadcast multiplexing extension header sub-blocks includes Ni length fields, where N1 is the number of SDUs or SDU segments corresponding to the 1 st multicast broadcast multiplexing extension header sub-block in the payload, and Ni is the number of SDUs or SDU segments corresponding to the ith multicast broadcast multiplexing extension header sub-block in the payload.

18. The method of claim 15,

for the domain termination identifier, the ith multicast broadcast multiplexing extension header sub-block includes Ni domain termination identifiers, where Ni is the number of SDUs or SDU segments corresponding to the ith multicast broadcast multiplexing extension header sub-block in the payload.

19. The method of claim 2, further comprising:

the protocol head of the protocol data unit does not carry an identifier for indicating the content of the multicast broadcast service, the resource allocation information of the control channel indicates a multicast service identifier for identifying the connection of the multicast broadcast service and an identifier for indicating the content of the multicast broadcast service, and the sequence of the identifiers in the resource allocation information is the same as the sequence of the content of the multicast broadcast service in the protocol data unit.

20. The method of claim 1, wherein the payload of the protocol data unit is comprised of one or more service data units, SDUs, or SDU segments, wherein data of the one or more SDUs or SDU segments is from one or more multicast broadcast service connections.

21. The method of claim 20, further comprising:

and indicating a multicast service identifier for identifying multicast broadcast service connection in the resource allocation information of the control channel, wherein the sequence of the multicast service identifier in the resource allocation information is consistent with the sequence of the multicast broadcast service connection in the protocol data unit.

22. The method of claim 19 or 21, wherein the protocol header comprises a multicast broadcast compressed MAC header.

23. The method of claim 22, wherein the multicast broadcast compressed MAC header comprises at least one of the following fields of indication: the extension header indicates a field, a length field and a reserved field.

24. The method of claim 23, wherein when the extended header indication field indicates that an extended header is included after the multicast broadcast compressed MAC header, the protocol header further comprises: one or more expansion heads.

25. The method of claim 24, wherein the extension header comprises at least one of the following indication fields: a header termination identification field, an extension header type field, an extension header entity, and a reserved field.

26. The method of claim 25,

when the extension header is a multicast broadcast segmentation packing extension header, if the load is from a multicast broadcast service content, the extension header is used for segmenting or packing SDU or SDU segmentation from the multicast broadcast service content; and if the load is from a multicast broadcast service connection, the extension header is used for segmenting or packing the SDU or the SDU segment from the multicast broadcast service connection.

27. The method of claim 26, wherein the multicast broadcast segment packing extension header comprises the following fields for indication: the system comprises a sequence number field, a segmentation control field, N-1 length fields and N field termination marks, wherein N is the number of SDUs or SDU segments forming a load.

28. The method of claim 27, wherein when the extension header is a multicast broadcast multiplexing extension header, if the payload is from one or more multicast broadcast service contents and the multicast broadcast service contents belong to one multicast broadcast service connection, the extension header is used for packet multiplexing SDUs or SDU segments from the multicast broadcast service contents; and if the load is from one or more multicast broadcast service connections, the extension header is used for packing and multiplexing the SDU or the SDU segment from the multicast broadcast service connections.

29. The method of claim 28, wherein the multicast broadcast multiplex extension header comprises at least one of: one or more multicast broadcast multiplexing extension head sub-blocks and a reserved domain, wherein each multicast broadcast multiplexing extension head sub-block corresponds to one multicast broadcast service content or one multicast broadcast service connection contained in the load.

30. The method of claim 29, wherein the multicast broadcast multiplex extension header sub-block is used for describing information of SDUs or SDU segments of its corresponding multicast broadcast service content or multicast broadcast service connection, and wherein the multicast broadcast multiplex extension header sub-block comprises the following indication fields: block termination identification field, segment control field, sequence number field, field termination identification, length field.

31. The method of claim 30,

for the length field, the 1 st multicast broadcast multiplexing extension header sub-block includes N1-1 length fields, and the ith multicast broadcast multiplexing extension header sub-block in the rest multicast broadcast multiplexing extension header sub-blocks includes Ni length fields, where N1 is the number of SDUs or SDU segments contained in the payload and corresponding to the 1 st multicast broadcast multiplexing extension header sub-block, and Ni is the number of SDUs or SDU segments contained in the payload and corresponding to the ith multicast broadcast multiplexing extension header sub-block.

32. The method of claim 31,

for the domain termination identifier, the ith multicast broadcast multiplexing extension header sub-block includes Ni domain termination identifiers, where Ni is the number of SDUs or SDU segments corresponding to the ith multicast broadcast multiplexing extension header sub-block and included in the payload.