WO2008031362A1

WO2008031362A1 - Bearing network, system, device and method for multicast broadcast service

Info

Publication number: WO2008031362A1
Application number: PCT/CN2007/070680
Authority: WO
Inventors: Liang Gu; Jianjun Wu
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2006-09-12
Filing date: 2007-09-12
Publication date: 2008-03-20
Also published as: CN101145927B; CN101145927A

Abstract

A bearing network, a system, a device and a method for multicast broadcast service are disclosed, which allow the WiMAX network bearing the MBS service. In the present invention, a media stream from the content provision network is born in an IP stream or an IP multicast group in a one-to-one or many-to-one manner, respectively; the respective IP stream or IP multicast group is born in a service stream or a data path in a one-to-one or many-to-one manner, respectively, and is sent to a terminal via an air interface. A content identification could indicate an IP stream, but it could also indicate an IP multicast group if and only if the IP multicast group contains one IP stream. The object of the MBS that the terminal anticipates could be an IP multicast group or an IP stream. The object born by the air interface could be a service stream or a data path. When a plurality of IP streams are born on a single MCID, the LCID would be required to differentiate a plurality of content identification.

Description

Bearer network, system, device and method for multicast broadcast service

This application claims priority to Chinese Patent Application No. 200610153367.2, entitled "Hosting Network, System and Method for Multicast Broadcasting Service", filed on September 12, 2006, the entire contents of which are incorporated by reference. In this application.

Technical field

The present invention relates to the field of wireless communications, and in particular to a multicast broadcast technology in a WiMAX network. Background technique

WiMAX ( Worldwide Interoperability for Microwave Access) is a wireless metropolitan area network technology used to implement wireless broadband access. Figure 1 shows the WiMAX end-to-end reference model. As can be seen, the WiMAX system mainly includes a mobile station (Mobile Station, referred to as "MS") / Subscriber Station ("Sc"), an Access Service Network ("ASN"), and a connection service network. (Connected Service Network, referred to as "CSN").

The ASN is defined as a network function set for providing a wireless access service for a WiMAX user terminal. The ASN includes a base station (Base Station, referred to as "BS") and an ASN GateWay (ASN GateWay, ASN-GW) network element, The ASN may be shared by multiple CSNs.

The main functions of the ASN include the functions of the BS and the functions of the ASN-GW. Among them, the functions of the BS are: providing L2 connection of BS and subscriber station SS/MS, radio resource management, measurement and power control, and compression and encryption of air interface data. The functions of ASN-GW include: proxy function for SS/MS authentication, authorization and accounting functions; network discovery and selection for NSP; relay function for providing L3 information for SS, such as IP address allocation .

CSN is defined to provide IP connection services for WiMAX user terminals. The CSN mainly provides the following functions: IP address allocation of SS/MS, Internet access, Authentication, Authorization, Account ("AAA") proxy or server, user-based authorization control, ASN to CSN Tunnels, billing for WiMAX subscribers, and settlement between operators, tunneling between CSNs in roaming, switching between ASNs, and various WiMAX services (such as location-based services, multimedia multicast and broadcast services, IP Multimedia Subsystem Service).

The MS/SS is a user equipment, and the user uses the device to access the WiMAX network.

The usual communication is communication between one node and another, but with the user's needs The increase, as well as the introduction of multiple media, requires new transmission modes, ie, one-to-many points may also include multi-point to multi-point communication. In order to support these modes, it is also desirable to meet the resource utilization effectiveness of the communication, that is, the reuse of some key communication resources, such as the bandwidth of the air interface, the connection identifier.

(Connection ID, referred to as "CID") and the transmission tunnel of the access network, etc. Therefore, in the prior art, a multicast broadcast service ("MBS") is introduced.

In the traditional communication concept, broadcast and multicast are technologies that transfer data from one data source to multiple targets. The above MBS provides a specification for transmitting data from one data source to multiple users in a mobile network, thereby realizing network resource sharing and improving the utilization of network resources, especially the utilization of air interface resources.

It is worth noting that the above MBS can not only realize multicast and broadcast of plain text and low-rate message services, but also realize multicast and broadcast of high-speed multimedia services, for example, video on demand, television broadcast, video conference, online education. , interactive games, and more.

The prior art protocol supports the MBS signaling and data transmission over the air interface. The MBS transmission mode can be divided into a single BS mode and a multiple BS mode, and the concept of the MBS domain is defined in the multi-BS mode. The so-called MBS domain is a collection of BSs. The BS in this set must satisfy one condition: the Multicast Connection Identifier ("MCID") and the Security Association ("Security Association") used when sending MBS data. SA" ) must be consistent. The prior art does not describe the single BS mode in detail; however, in the multi-BS mode, how the BS transmits MBS data, how the MS receives the MBS data, and how the BS informs the MBS data that the MS is interested in has a corresponding description.

The main descriptions of the air interface in existing systems are as follows:

First, the downlink mapping message (DL-MAP, Downlink MAP) broadcasted on the broadcast CID includes zero to one or more multicast broadcast service mapping information (MBS-MAP-IE, Multicast Broadcast Service MAP Information Element), MBS- Each item on the MAP-IE is identified by an MBS domain ID.

Second, an MBS-MAP-IE identifies the physical resource of a multicast broadcast service map (MBS-MAP, Multicast Broadcast MAP) message on the air interface; if it is a single BS mode, it directly indicates the physical resource of the MBS.

Third, an MBS-MAP message can contain zero to one or more multicast broadcast service data messages. MBS-DATA-IE, the physical parameters between these MBS-DATA-IEs can be consistent or inconsistent, determined by the network side; but an MBS-DATA-IE has only one physical parameter set.

Fourth, one MBS-DATA-IE contains one or more MCIDs; the reason why one MBS-DATA-IE is required to contain one or more MCIDs is to reduce the MBS-MAP message length and consider the same downlink coding. The MCID corresponding to the MBS data of the DIUC (Downlink Interval Usage Code) is indicated in an MBS-DATA-IE. In the data transmission, the same MAC-PDU (Medium Access Control- Protocol Data Unit) of the DIUC is placed on one physical resource, although the data of different MBS is in the physical resource. Mixed together, but can be distinguished on the MAC layer by the MCID on the MAC-PDU header. Not all MCIDs correspond to the same MBS, but each MCID corresponds to one MBS.

Fifth, an extended MBS-DATA-IE, an MCID also contains one or more logical channel IDs. The logical channel ID is used in the air interface to inform the MS of the currently indicated MBS data whether it has content of interest.

In addition, the downlink channel descriptor (DCD, Downlink Channel Descriptor) can carry zero to one or more MBS domain IDs. The multicast broadcast service content identifier (MBS Content ID) corresponds to the group information of the MCID and the logical channel ID. The upper layer data stream carried by the WiMAX access network service flow (Service Flow, referred to as "SF") or the access network data path ("DP") is identified by the multicast broadcast service content identifier.

The DL-MAP message indicates the physical resource to be sent by the next MBS-MAP message, but does not distinguish the MCID and the logical channel ID included in the MBS-MAP message; the MBS-DATA-IE also has the physical resource for the next MBS-MAP message. The indication differs from the indication in the DL-MAP in that the MBS-MAP message here is a special MBS-MAP message, which must contain an MBS-DATA-IE, which is owned by the MBS-DATA-IE and the current MBS. -DATA-IE - MCID and logical channel ID. In this way, the terminal does not need to receive the DL-MAP message one by one, and only needs to know the transmission time of the next MBS-MAP message from the current MBS-MAP-IE.

In addition, there is a change indication in the MBS-DATA-IE. If there is no change, the MBS data is directly received; otherwise, the new MBS-DATA-IE needs to be parsed to update the relevant MBS information of the terminal. How the air interface link layer carries MBS is described in the existing standards:

1. The air interface link layer can carry a SF on the network side through a unicast air interface connection (CID) or a multicast air interface connection (MCID);

2. The SF on the network side is identified by the SFID. One SF can carry one or more high-level data streams, and the upper-layer data stream is identified by the Content ID.

However, the prior art only describes how the air interface link layer carries the MBS, and does not provide a complete service bearer scheme from the MBS server to the terminal. That is to say, the prior art does not give a complete technical solution, such as not giving a service from a content service provider, how to be hosted and managed in a WiMAX network, and not giving an object of the existing defined Content ID. Identifies what the object of the MS joins the MBS, what the object is hosted by an air interface connection, and when it carries multiple Content IDs and so on. Different bearer modes correspond to completely different solutions. It can be seen that no specific solution is given in the prior art.

Summary of the invention

The present invention provides a bearer network, system, device and method for a multicast broadcast service, so that a WiMAX network can carry an MBS service.

The present invention provides a bearer network for a multicast broadcast service, including:

a first bearer network, configured to carry each media stream from the content providing network in an IP flow or an IP multicast group in a one-to-one or multiple-to-one manner;

The access service network is configured to carry each IP stream or IP multicast group from the first bearer network in a service flow or a data channel in a one-to-one or multiple-to-one manner, and send the information to the terminal through an air interface.

The present invention also provides a bearer system for a multicast broadcast service, including:

The multicast broadcast service server is configured to carry the media streams from the content providing network in an IP flow or an IP multicast group to the at least one multicast broadcast service agent in a one-to-one or multiple-to-one manner;

a multicast broadcast service agent for at least one of at least one multicast broadcast service server

The IP stream or the IP multicast group is respectively carried in a service flow or a data channel in a one-to-one or many-to-one manner;

And a base station, configured to send the service flow or the data channel to a terminal in a different air interface connection. The invention also provides a multicast broadcast service server, comprising:

a module for receiving a media stream;

A module for transmitting one or more of the media streams in an IP stream or an IP multicast group in a one-to-one or many-to-one manner.

The invention also provides a multicast broadcast service agent, comprising:

a module for receiving at least one IP flow or IP multicast group from at least one multicast broadcast service server;

And a module for transmitting the at least one IP stream or IP multicast group in a service flow or a data channel in a one-to-one or many-to-one manner.

The present invention also provides a bearer method for a multicast broadcast service, including:

Each media stream from the content providing network is respectively carried in an IP stream or an IP multicast group in a one-to-one or many-to-one manner;

Each IP stream or IP multicast group is carried in a service flow or a data channel in a one-to-one or many-to-one manner, and is sent to the terminal through an air interface.

The technical solution of the present invention carries each media stream in an IP flow or an IP multicast group in a one-to-one or many-to-one manner in a CSN, and respectively pairs each IP flow or IP multicast group in the ASN. One or many to one ways are carried in the service flow. Through this bearer model, the MBS service from the content service provider can be successfully carried in the WiMAX network, and the service bearers between the layers have certain independence and independence, and there is no need to modify the existing WiMAX protocol.

The present invention provides a specific factor by which a media stream can be carried to an IP stream or an IP multicast group, and an IP stream or an IP multicast group can be carried to the service stream, thereby making the present invention more practical.

DRAWINGS

1 is a schematic diagram of a WiMAX network architecture according to the prior art;

2 is a schematic diagram of a bearer network of an MBS according to a first embodiment of the present invention;

3 is a schematic diagram of a bearer system of an MBS according to a second embodiment of the present invention;

4 is a flow chart of a method for carrying an MBS according to a third embodiment of the present invention.

detailed description

The invention will be further described in detail below with reference to the accompanying drawings.

In the present invention, the CSN separates each media stream from the content providing network into one-to-one or many-to-one The mode is carried in the IP stream or IP multicast group and transmitted to the ASN. The ASN carries the IP flows or IP multicast groups from the CSN in the service flow in a one-to-one or many-to-one manner, respectively, through the air interface. The terminal sends. Each layer network may carry different data streams provided by the upper layer network in the same data stream of the layer network, or may carry different data streams provided by the upper layer network in different data streams of the layer network. The specific bearer mode is determined by the network side entity.

The first embodiment of the present invention will be described in detail below based on the above principles. The first embodiment of the present invention relates to a bearer network of an MBS, and the network bearer model of the present embodiment is as shown in FIG. 2.

Specifically, in a content providing network, a content service provider provides one or more media streams to a CSN, which may represent a specific service or a set of services. Among them, the media stream is the basic business object provided by the content service provider to the MBS server (MBS Server). The same media stream can be provided to different CSN networks, and each media stream is provided to at least one CSN.

In the CSN, the CSN uses an IP stream or an IP multicast group to carry the media stream provided by the upper layer network, and each IP multicast group includes at least one IP stream. The CSN network can carry different media streams in different IP flows, as shown in Figure 1 and 2; different media streams can also be carried in the same IP stream, as shown in Figure 2 . The IP flow refers to the IP source address, IP destination address, service priority, TOS/DSCP (Type of Service/DiffServ Code Point), protocol type, flow label, and TCP (Transmission) in the IP packet. Control Protocol (Transmission Control Protocol) / UDP (User Datagram Protocol) source port number, one or more uniquely identified IP data streams in the TCP/UDP destination port number.

The IP stream is provided as a basic service object provided by the CSN network to the ASN network. Each IP stream is sent to at least one ASN and/or MBS domain (such as the MBS zone defined by IEEE 802.16d/e), and the same IP stream can be sent to different Within the ASN network and / or MBS domain. Different IP flows are identified by the MBS Content ID defined by IEEE 802.16d/e.

When using IP multicast technology, the IP multicast address is assigned by the CSN, and the same IP multicast group can contain one or more IP flows. When an IP multicast group contains and contains only one IP stream, the Content ID can also be used to identify the multicast group. Since the specific object of the Content ID is clarified, the present embodiment provides another way of identifying the IP multicast group other than the IP multicast address. The CSN can send IP multicasts containing one or more IP flows to different ASN networks through IP multicast routing or tunneling. And / or within the MBS domain.

In the ASN, the ASN uses the SF to carry the IP flow or multicast group provided by the upper layer network CSN. The ASN can carry different IP flows or multicast groups in different SFs, as shown in Figure 2; different IP flows or multicast groups can also be carried in the same SF, as shown in Figure 2. Case 2 and Case 3.

The SF is the basic service object in the ASN. Each SF is sent to at least one BS in the same ASN and/or MBS domain, and the same SF can be sent to different BSs in the same ASN and/or MBS domain.

Different SFs are identified by the SFID defined by IEEE 802.16d/e.

In the air interface, the same SF is carried over the air interface using a CID or MCID, and the same CID or MCID can be sent to a different MS. When multiple IP flows are carried on one MCID, you need to use the logical channel ID (Logical Channel ID, LCID) for the link layer to distinguish. An LCID uniquely corresponds to a Content ID on an MCID.

Different MCIDs of the same BS If the coded modulation modes that can be used are the same, the BS can transmit multiple MCIDs on the same physical resource as needed.

It can be seen that through the above bearer model, the MBS from the content service provider can be successfully carried over

In a WiMAX network, the service bearers between layers have certain independence and independence, and there is no need to modify WiMAX's existing protocols.

It is worth mentioning that, depending on how the terminal joins the MBS, the business objects that the terminal joins are as follows:

1) When the terminal uses IP multicast to join the MBS, the IP multicast group provided by the CSN is the basic service object that the terminal joins; when one SF carries multiple IP multicast groups or one multicast group contains multiple IP flows, When an SF includes multiple data streams identified by the Content ID, the network side entity also needs to allocate an LCID for identifying, at the link layer, which upper layer services are currently transmitted by the air interface connection.

2) When the terminal carries the Content ID to join the MBS in the process of using the Dynamic Service Flow (DSA), the IP flow provided by the CSN is the basic service object that the terminal joins; when one SF carries multiple IP flows, the network The side entity also needs to allocate an LCID for identifying which IP flows are currently transmitted by the air interface connection at the link layer.

The object that the terminal joins the MB S can be an IP multicast group, and can also be an IP stream. Therefore, the present embodiment provides multiple ways for the terminal to join the MBS. A second embodiment of the present invention relates to a bearer system of an MBS. As shown in FIG. 3, an MBS server is configured to carry each media stream from a content providing network in an IP flow or in a one-to-one or many-to-one manner. In the IP multicast group, the MBS proxy is a functional entity for processing MBS signaling for the MS in the ASN network or the MBS domain, and is configured to respectively configure at least one IP flow or IP multicast group from at least one MBS server into one-to-one or multiple The one-to-one mode is carried in the SF, and the MBS proxy is located in the ASN gateway; the BS is configured to send different SF bearers from the MBS proxy to the terminal in different air interface connections.

It can be understood that the illustration shown in FIG. 3 is merely illustrative, indicating a logical structure in which the units displayed as separate components may or may not be physically separated, and the components displayed as units may or may not be physical. Units can be located in one place or distributed to several network units. For example, the MBS proxy can be a logical entity, can be located in a BS or ASN gateway, or can be a physical entity, independent of the BS or ASN gateway.

Specifically, the MBS server is the provider of the MBS. The MBS server receives one or more media streams from one or more content providers. According to the requirements of different content providers, the quality of service (QoS) requirements of different media streams, the resource status of current MBS servers and networks, and the network service provider (NetWork Service Procider, "NSP") The service policy, MBS planning and other factors repackage the media stream in the IP stream and finally transmit it to one or more ASN gateways.

If IP multicast is used, the MBS server is also responsible for allocating IP multicast addresses, constructing IP multicast groups, and carrying one or more IP flows on the IP multicast group for transmission.

The ASN gateway is an entity within the ASN. The MBS proxy of the ASN gateway receives one or more IP flows or IP multicast groups from one or more MBS servers, and according to MBS planning requirements, MBS domain partitioning, IP flow QoS. The IP stream or IP multicast group is repackaged and carried in the SF or DP and sent to one or more BSs, such as requirements and MBS authentication requirements. The SF is a service flow identified by the SFID, and the DP is a bearer channel identified by the GRE Key (Generic Routing Encapsulation Key).

The MBS authentication request means that when the ASN gateway carries different IP flows on the same SF, it is necessary to consider whether the IP flows are from the same MBS server and have the same MBS Authorization Key (MAS). Only consider can be carried on one SF. MBS planning The request means that when the ASN gateways are carrying different IP flows on the same SF, it is necessary to consider whether the IP flows are from the same MBS server and are required to be broadcasted in the ASN network during service planning, and if it is considered to be bearable on one SF.

The BS carries different SFs on different air interface connections. As for whether the BS uses a unicast air interface to connect to a CID or a multicast air interface connection, the MCID is determined by the BS. The BS can carry different air interface link layer connections on the same physical resource according to the coding adjustment manner, and finally send to one or more MSs.

Through the MBS server, the MBS proxy, and the base station in this embodiment, the MBS from the content service provider can be smoothly carried in the WiMAX network, and the service bearers between the layers have certain independence and independence, and there is no need to modify the existing WiMAX. protocol. Moreover, the present embodiment provides a specific factor by which the media stream 7 can be carried to an IP stream or an IP multicast group, and the IP stream or the IP multicast group 7 can be carried to the SF, thereby making the present invention more practical. .

A third embodiment of the present invention relates to a method of carrying an MBS, as shown in FIG.

In step 410, the CSN carries each media stream from the content providing network in an IP stream or an IP multicast group in a one-to-one or many-to-one manner. Specifically, the CSN provides network requirements according to different content, QoS requirements of different media streams, current MBS server and network resource status, and NSP (Network Service Provider) service policy, MBS planning, and the like. The media stream is repackaged and carried in the IP stream and finally delivered to one or more ASN gateways.

Then, in step 420, the ASN carries the IP flows or IP multicast groups from the CSN in the SF or DP in a one-to-one or one-to-one manner, and sends them to the terminal through the air interface. Specifically, the ASN repackages the IP stream or the IP multicast group in the SF or DP according to the MBS planning requirements, the division of the MBS domain, the QoS requirements of the IP flow, and the MBS authentication request, and sends the packet to the SF or the DP, and sends the packet to the one or more. BS. The BS carries different SFs on different air interface connections. Whether the BS is connected to the CID using a unicast air interface or the MCID of the multicast air interface is determined by the BS. The BS can carry different air interface link layer connections on the same physical resource according to the coding adjustment manner, and finally send to one or more MSs.

It is not difficult to find that the MBS from the content service provider can be successfully carried in the WiMAX network, and the service bearers between the layers have certain independence and independence, so there is no need to modify the existing WiMAX protocol. It should be noted that, if an MS joins an MBS as a service object by using an IP multicast group, when a service flow carries multiple IP multicast groups or an IP multicast group contains multiple IP flows, the network side entity passes the LCID in the chain. The road layer identifies the upper layer service of the current air interface connection transmission. If the MS joins the MBS as the service object, the network side entity identifies the current air interface connection transmission layer at the link layer through the LCID. business. The object that the terminal joins the MBS can be an IP multicast group, and can also be an IP stream. Therefore, the present embodiment provides multiple ways for the terminal to join the MBS.

The multicast broadcast service server described in each of the foregoing embodiments may be located in a network provided by an ASN network, a CSN network, or a third-party ASP (Application Service Provider). The foregoing functional entities may be located in different physical entities or in the same physical entity, and the present invention is not limited.

As can be seen from the foregoing embodiments, the present invention carries each media stream in an IP flow or an IP multicast group in a one-to-one or many-to-one manner in the CSN, and each IP stream or IP multicast group is in the ASN. They are carried in the service flow in a one-to-one or many-to-one manner. Through this bearer model, the MBS service from the content provider can be smoothly carried in the WiMAX network, and the service bearers between the layers have certain independence and independence, and there is no need to modify the existing WiMAX protocol.

In the embodiment of the present invention, the content identifier may indicate an IP flow, or may indicate an IP multicast group when the IP multicast group includes and only includes one IP flow. Therefore, the specific object of the content identifier is clarified, and another manner of identifying the IP multicast group other than the IP multicast address is provided.

The invention also clarifies that the object that the terminal joins the MBS may be an IP multicast group or an IP stream, and provides multiple ways of joining the MBS.

The invention also clarifies that the object of the air interface connection bearer is a service flow, and when multiple IP flows are carried on one MCID, multiple content identifiers need to be distinguished by LCID.

While the invention has been illustrated and described with reference to the preferred embodiments embodiments The spirit and scope of the invention.

Claims

Rights request

A bearer network for a multicast broadcast service, comprising:

The bearer network of the multicast broadcast service according to claim 1, wherein the first bearer network is the access service network, or a network connecting a service network or a third-party application service provider.

The bearer network of the multicast broadcast service according to claim 1 or 2, wherein each of the IP multicast groups includes at least one IP flow.

The bearer network of the multicast broadcast service according to any one of claims 1 to 3, wherein the IP multicast group is indicated by a multicast broadcast service content identifier.

The bearer network of the multicast broadcast service according to any one of claims 1 to 4, wherein each media stream is provided to at least one of the first bearer networks.

The bearer network of the multicast broadcast service according to any one of claims 1 to 5, characterized in that each IP stream is transmitted to at least one of the access service network and/or the multicast broadcast service domain.

The bearer network of the multicast broadcast service according to any one of claims 1 to 6, wherein a service flow or a data channel is transmitted to the same access service network and/or multicast broadcast At least one base station within the service domain.

The bearer network of the multicast broadcast service according to any one of claims 1 to 7, wherein the same service flow or data channel is carried on the air interface by using a connection identifier CID or a multicast connection identifier MCID. The same CID or MCID is sent to at least one terminal.

The bearer network of the multicast broadcast service according to any one of claims 1 to 8, wherein the plurality of IP flows are carried on a CID or an MCID, and the logical channel identifier LCID is distinguished at the link layer. , an LCID uniquely corresponds to a multicast broadcast service content identifier on a CID or MCID.

A bearer system for a multicast broadcast service, comprising:

a multicast broadcast service server for respectively separating media streams from the content providing network into one-to-one Or a many-to-one manner is carried in an IP stream or an IP multicast group and sent to at least one multicast broadcast service agent;

And a base station, configured to send the service flow or data channel to a terminal in a different air interface connection.

The bearer system for multicast broadcast service according to claim 10, wherein the multicast broadcast service proxy is located in an access service network gateway or a base station.

The bearer system for multicast broadcast service according to claim 10 or 11, wherein the multicast broadcast service server carries the media stream in IP flow or IP multicast according to one of the following factors or any combination thereof; In the group:

The content provides the requirements of the network, the quality of service requirements of the media stream, the resource status of the multicast broadcast service server, the network resource status of the connected service network, the service policy of the network service provider, and the service plan of the multicast broadcast service.

The bearer system of the multicast broadcast service according to any one of claims 10 to 12, wherein, when the multicast broadcast service server uses the IP multicast group to carry the media stream from the content providing network, The multicast broadcast service server is also configured to allocate an IP multicast address, construct an IP multicast group, and carry at least one IP stream on the IP multicast group for transmission.

The bearer system for a multicast broadcast service according to any one of claims 10 to 13, wherein the multicast broadcast service agent sets an IP flow or an IP multicast group according to one of the following factors or any combination thereof; Hosted in a service flow or data channel:

Multicast broadcast service planning requirements, division of multicast broadcast service domains, quality of service requirements for IP flows, and authentication requirements for multicast broadcast services.

The bearer system of the multicast broadcast service according to claim 14, wherein the multicast broadcast service planning requirement comprises:

Each IP flow that can be carried in the same service flow or data channel is from the same multicast broadcast service server and has the same multicast broadcast service authentication key; or

Each IP flow that can be carried in the same service flow or data channel comes from the same multicast broadcast service service. Servers and services are required to be broadcast within the same access service network.

The bearer system of the multicast broadcast service according to claim 10, wherein the multicast broadcast service server is located in a connection service network or an access service network or a content service network.

17. A multicast broadcast service server, comprising:

a module for receiving a media stream;

The multicast broadcast service server according to claim 17, wherein when the multicast broadcast service server uses the IP multicast group to carry the media stream from the content providing network, the method further includes: Address, a module that constructs an IP multicast group, and carries at least one IP stream 7 on the IP multicast group.

The multicast broadcast service server according to claim 17 or 18, wherein the multicast broadcast service server is located in a connection service network or an access service network or a content service network.

20. A multicast broadcast service agent, comprising:

21. The multicast broadcast service agent according to claim 20, wherein the multicast broadcast service agent is located in an access service network gateway or a base station.

A bearer method for multicast broadcast service, characterized in that it comprises:

The method for carrying a multicast broadcast service according to claim 22, wherein the media stream is carried in an IP flow or an IP multicast group according to one of the following factors or any combination thereof:

The content provides the requirements of the network, the quality of service requirements of the media stream, the status of the network resources, the service policy of the network service provider, and the service plan of the multicast broadcast service.

The method for carrying a multicast broadcast service according to claim 22 or 23, wherein the IP flow or the IP multicast group is carried in the service flow or the data channel according to one of the following factors or any combination thereof:

The method for carrying a multicast broadcast service according to any one of claims 22 to 24, wherein the terminal joins the multicast broadcast service by using an IP multicast group as a service object;

When a service flow or data channel carries multiple IP multicast groups or an IP multicast group contains multiple IP flows, the logical channel identifies the LCID at the link layer to identify the upper-layer service transmitted by the current air interface.

The method for carrying a multicast broadcast service according to any one of claims 22 to 24, wherein the terminal joins the multicast broadcast service by using the IP flow as a service object;

When a service flow or data channel carries multiple IP flows, the upper layer service of the current transmission is connected to the air interface at the link layer by assigning a logical channel identifier LCID.