WO2009103244A1

WO2009103244A1 - Method and system for setup multicast broadcasting service in wireless network

Info

Publication number: WO2009103244A1
Application number: PCT/CN2009/070502
Authority: WO
Inventors: 顾亮; 王丽梅; 张伟
Original assignee: 华为技术有限公司
Priority date: 2008-02-21
Filing date: 2009-02-23
Publication date: 2009-08-27
Also published as: CN101515858B; CN101515858A

Abstract

A method and system for the terminal in a wireless network joining in the multicast broadcast service lead the terminal to be capable of joining in MBS service successfully, and receiving MBS service content. The terminal acquires MBS service parameter of multicast broadcast service from the network side, which contains a first identifier for indicating the empty port connection and a second identifier for indicating the service content, for leading the terminal to be capable of receiving MBS service content indicated in the second identifier from the empty port connection indicated in the first identifier after receiving MBS service parameter, and successfully joining in MBS service. The terminal is capable of initiating MBS service joining process, acquiring MBS service parameter and joining in the desired MBS service by sending the request message of joining MBS service; the network side can also initiate actively MBS service joining process, send MBS service parameter to the terminal, and invite the terminal to join in MBS service.

Description

Method and apparatus for initiating multicast broadcast service in a wireless network This application claims to be filed on the Chinese Patent Office on February 21, 2008, and the application number is 200810065393. 9. The invention name is "a method for a terminal to join a multicast broadcast service in a wireless network, The priority of the Chinese Patent Application, the entire disclosure of which is incorporated herein by reference. TECHNICAL FIELD The present invention relates to the field of wireless communications, and in particular, to a method and apparatus for initiating a multicast broadcast service in a wireless network. BACKGROUND OF THE INVENTION

IEEE 802.16 was promulgated in December 2001 by the Institute of Electrical and Electronics Engineers (IEEE) to provide the last mile of wireless broadband access in metropolitan area networks.

Worldwide Interoperabi lity for Microwave Access (WiMAX) is the industry's wireless metropolitan area network access technology based on the IEEE 802.16 series of standards. Its basic goal is to provide a point-to-multipoint network in the metropolitan area network. Broadband wireless access means that can interoperate effectively in a multi-vendor environment.

Figure 1 shows the WiMAX end-to-end reference model, where the R1 interface is a wireless air interface.

As can be seen, WiMAX mainly includes mobile station (Mobi le Station, MS) / subscriber station (Subscribe

Station, SS), Access Service Network (ASN) and Connectivity Service Network (CSN).

The ASN is defined as a network function set that provides a wireless access service for a WiMAX user terminal. The ASN includes a base station BS (Base Station) and a B ASN gateway (ASN GateWay "ASN-GW") network element, and one ASN may be multiple. CSN sharing.

CSN is defined to provide IP connection services for WiMAX user terminals.

The MS/SS is a (mobile) terminal that the user uses to access the WiMAX network.

What people usually call communication is communication between one node and another node, but as user needs increase and multiple media are introduced, users need to perform one-to-many or many-to-many communication, resulting in Point to Multipoint (PTM) transmission mode. In order to support these modes on the mobile network, a one-to-many multicast broadcast service is realized, and in order to effectively utilize mobile network resources, the prior art is based on WiMAX. The MBS service is defined on the basis. The MBS service is a point-to-multipoint service that provides a data source to send data to multiple users in a mobile network, realizes network resource sharing, and improves utilization of network resources, especially air interface resources. The MBS defined by WiMAX can not only realize plain text low-rate message-like multicast and broadcast, but also realize high-speed multimedia service multicast and broadcast, which undoubtedly conforms to the trend of future mobile data development.

The MBS service based on WiMAX network supports two access modes: single base station access and multiple base station access. In the multi-base station access mode, the concept of an MBS domain (ie, MBS Zone, identified by MBS_zone ID) is defined. An MBS domain is a collection of base stations, and all base stations in an MBS domain use the same Mult icast CID. And the MBS Group Security Association (MBS GSA), which transmits the content of the same MBS service flow, and the terminal that has registered the MBS service can receive the MBS service data through multiple base stations in the MBS domain, and is in an idle state. When the terminal moves across the base station in the MBS domain, the connection does not need to be re-established, and the MBS service can be received without being affected, and the seamless switching of the MBS service is realized. Single-base station access MBS is a special case of multi-base station access MBS. The MBS domain is limited to one base station coverage. All users in the MBS domain receiving the MBS use the same multicast connection identifier.

There is no related art in the prior art regarding how a terminal joins an MBS service. SUMMARY OF THE INVENTION The embodiments of the present invention provide a method and apparatus for initiating a multicast broadcast service in a wireless network, so that the terminal can successfully join the MBS service and receive the MBS service content.

A method for initiating a multicast broadcast service in a wireless network, comprising:

The anchor service flow licensor Anthor SFA obtains the MBS service join request from the terminal carrying the service first identifier, or the MBS service creation request from the multicast multicast service server MBS Server and/or the policy decision entity PDF carrying the service second identifier. ;

The Anthor SFA sends an MBS service creation request carrying the first identifier of the service or the second identifier of the service to the base station BS, where the MBS service creation request is used by the BS to initiate an MBS service creation process.

A network side functional entity, including:

An obtaining unit, configured to obtain an MBS service joining request for carrying the first identifier of the service from the terminal, or an MBS service creation request for carrying the second identifier of the service from the multicast multicast service server MBS Server and/or the policy decision entity PDF;

And a sending unit, configured to send, to the base station BS, an MBS service creation request that carries the first identifier of the service or the second identifier of the service, where the MBS service creation request is used by the BS to initiate an MBS service creation process.

By comparison, it can be found that, in the embodiment of the present invention, the first identifier of the carried service is obtained by acquiring the terminal The MBS service join request, or the MBS service creation request from the multicast multicast service server MBS Server and/or the policy decision entity PDF carrying the service second identifier, and sending the first identifier or the service carrying the service to the BS The second identified MBS service creation request enables the terminal to successfully join the MBS service and receive the MBS service. BRIEF DESCRIPTION OF DRAWINGS FIG. 1 is a schematic diagram of a network structure of a WiMAX in the prior art;

2 is a flowchart of a method for a terminal to join an MBS service in a wireless network according to an embodiment of the present invention; FIG. 3 is a flowchart of a method for a terminal to join an MBS service in a wireless network according to an embodiment of the present invention; A flowchart of a method for a terminal to join an MBS service in a wireless network according to an embodiment of the present invention; FIG. 5 is a flowchart of a method for a terminal to join an MBS service in a wireless network according to an embodiment of the present invention; A structural diagram of a network layer functional entity. In the embodiment of the present invention, the terminal acquires the MBS service parameter of the multicast broadcast service from the network side, where the terminal includes a first identifier indicating the air interface connection and a second identifier indicating the service content, after receiving the MBS service parameter, the terminal receives the MBS service parameter. The MBS service content indicated by the second identifier is received from the air interface connection indicated by the first identifier, and the MBS service is successfully added.

In the embodiment of the present invention, the terminal obtains the multicast broadcast service MBS service parameter from the network side, and the terminal may send the MBS service join request to obtain the multicast broadcast service MBS service parameter from the network side, or may be added by the network side MBS service. In the process, the terminal acquires a multicast broadcast service MBS service parameter from the network side.

The embodiments of the present invention are described below. The embodiment of the present invention relates to a method for a terminal to join an MBS service in a wireless network. In this embodiment, the terminal initiates an MBS service joining process by sending an MBS service join request, and the terminal has clarified the MBS service that it wishes to join before joining the MBS service. In which MBS Zones are broadcasted, the terminal can obtain relevant information in the service announcement phase (Servi ce Announce); the terminal can also know which MBS Zones the current BS belongs to in the DCD message broadcasted by the current BS, if these MBSs are broadcasted. In the zone, there is an MBS Zone where the MBS service that the terminal wants to join, and the terminal can initiate the MBS service joining process. Specifically as shown in Figure 2.

The terminal sends an MBS service join request message to the base station BS, for example, the DSA-REQ message of the process DSA process is added by the dynamic service flow, and the MBS service join request message carries the MBS Zone identifier (MBS) where the MBS service to be joined is located. Zone ID) Further, in the embodiment of the present invention, the MBS service join request message may further carry the MBS service authentication information. Optionally, the MBS service join request message may further carry the maximum MBS service capability information supported by the terminal, and is used to notify the network, and the network may determine, according to the actual quality of service (QoS) requirement of the MBS service, whether the terminal can Receive business normally.

202. The BS receives the MBS service join request message of the terminal, and can verify the message authentication code of the MBS service join request message, such as HMAC/CMAC, to verify whether the terminal is a legitimate user of the network, and after the verification succeeds, the BS connects to the service. The serving service network gateway (Serving Access Service Network GateWay, Serving ASN-GW) sends an MBS service join request message, which may be an RR-REQ message or a DP-REQ message, and the MBS service join request message may carry the MBS Zone ID, further The terminal identifier MSID and/or MBS service authentication information may also be carried.

Optionally, the following situations exist in this step:

a) If the resource for carrying the MBS service between the BS and the Serving ASN-GW is not pre-configured, and the corresponding resource reservation has not been performed, if the BS holds the resource reservation information required by the MBS service, the BS The MBS service join request message sent to the Serving ASN-GW may further include a resource reservation request, requesting that the MBS service perform corresponding resource reservation on the BS and the Serving ASN-GW.

b) If the bearer channel between the BS and the Serving ASN-GW for transmitting the MBS service is not pre-configured, and the corresponding bearer channel has not been created, if the BS holds the bearer channel information required by the MBS service, the BS direction The MBS service join request message sent by the Serving ASN-GW may further include a bearer channel setup request, and apply for establishing a bearer channel on the BS and the Serving ASN-GW for transmitting the MBS service. The implementation of the bearer channel between the BS and the Serving ASN-GW can be performed through a tunnel such as Generic Route Encapsulation (GRE), Virtual Local Area Network (VLAN), and Multi Protocol Label Switching (MPLS). Technology to achieve.

c) In the case that the MBS service join request message includes the maximum MBS service capability information of the terminal, if the BS holds the actual capability requirement of the MBS service, that is, the resource reservation information required by the MBS service, the BS may determine whether the terminal is The MBS service can be received normally. If the resource reservation information of the MBS service is not available on the BS, the MBS service join request message sent by the BS to the Serving ASN-GW may further include the maximum MBS service capability information of the terminal, requesting Serving. The ASN-GW makes a decision.

203. The Serving ASN-GW receives the MBS service join request message from the BS, and sends an MBS service join request message to the MBS proxy (MBS Proxy) or the anchor MBS data function (Anchor MBS DPF), such as an MBS. The request message, the MBS service join request message may carry the MBS Zone ID, and further, may carry the terminal identifier MSID and/or the MBS service authentication information.

The MBS Proxy and/or anchor MBS data function Anchor MBS DPF described in the embodiment of the present invention is logical The functional entities are described as an example. In a specific networking, these logical functional entities may be separate physical entities or integrated into other physical entities such as Access Service Network GateWay (Access Service Network GateWay). Or in a base station.

Optionally, the following situations exist in this step:

a) If the resources for carrying the MBS service between the Serving ASN-GW and the MBS Proxy or the Anchor MBS DPF are not pre-configured, and the corresponding resource reservation has not been performed, if the Serving ASN-GW holds the MBS service request The resource reservation information may be included in the MBS service join request message sent by the U-U Serving ASN-GW to the MBS Proxy or the Anchor MBS DPF, and the request is for the MBS service in the Serving ASN-GW and the MBS The corresponding resource reservation is performed on the Proxy or Anchor MBS DPF.

b) If the bearer channel between the Serving ASN-GW and the MBS Proxy or the Anchor MBS DPF for transmitting the MBS service is not pre-configured, and the corresponding bearer channel has not been created, if the Serving ASN-GW holds the MBS service requirement And carrying the channel information, the MBS service join request message sent by the Serving ASN-GW to the MBS Proxy or the Anchor MBS DPF may further include a bearer channel setup request, for transmitting the MBS service in the Serving ASN-GW with the MBS Proxy or Anchor Apply for a bearer channel on the MBS DPF. The implementation of the bearer channel between the Serving ASN-GW and the MBS Proxy or the Anchor MBS DPF can be implemented by Generic Route Encapsulation (GRE), Virtual Local Area Network (VLAN), and Multi Protocol Label Switching. , MPLS) and other tunneling technologies to achieve.

c) For the case where the MBS service join request message includes the maximum MBS service capability information of the terminal, if the Serving ASN-GW holds the actual capability requirement of the MBS service, that is, the resource reservation information required by the MBS service, the Serving ASN-GW may Determining whether the terminal can receive the MBS normally; if the Serving ASN-GW does not have the resource reservation information of the MBS service, the serving ASN-GW may also send the MBS service join request message to the MBS Proxy or the Anchor MBS DPF. Contains the maximum MBS service capability information of the terminal, and requests the MBS Proxy WL Anchor MBS DPF to make a decision.

In the embodiment of the present invention, if the MBS Proxy or the Anchor MBS DPF is integrated on the Serving ASN-GW, step 203 may be omitted.

204. The MBS Proxy or the Anchor MBS DPF receives the MBS service join request message from the Serving ASN-GW. Optionally, the MBS service may be sent to the MBS server or the Policy Decision Function (PDF). The request, as may be an MBS Auth Req message, requests the MBS server or policy decision entity PDF to verify that the terminal has the right to receive the MBS service. The request may also carry the MBS Zone ID, and further, the network access identifier (Network Access ID) of the terminal may also be carried. NAD and/or MBS service authentication information, etc.

Optionally, the following situations exist in this step:

a) If the ASN-GW where the MBS Proxy or Anchor MBS DPF is located or other functional entities on the ASN-GW, such as a Service Flow Authorizer (SFA), the MBS service has been saved. The subscription information, the U MBS Proxy or the Anchor MBS DPF may not send the MBS service authentication request to the MBS Server or the PDF, and the ASN-GW may perform the MBS service subscription information and/or the MBS service authentication information according to the maintenance. To process the MBS service join request message of the terminal.

b) If the resource for carrying the MBS service between the MBS Proxy or the Anchor MBS DPF and the MBS Server is not pre-configured, and the corresponding resource reservation has not been performed, if the MBS Proxy or the Anchor MBS DPF or the MBS Proxy Or the ASN-GW where the Anchor MBS DPF is located has the resource reservation information required by the MBS service, and the MBS service authentication request sent by the MBS Proxy or the Anchor MBS DPF to the MBS Server may also include the resource reservation in this step. Apply, apply for the corresponding resource reservation on the MBS Proxy or Anchor MBS DPF and MBS Server to carry the MBS service.

c) If the bearer channel between the MBS Proxy or Anchor MBS DPF and the MBS Server for transmitting the MBS service is not pre-configured and the corresponding bearer channel has not been created, if MBS Proxy or Anchor MBS

The DSF or the ASN-GW where the MBS Proxy or the Anchor MBS DPF is located can hold the bearer channel information required by the MBS service. In this step, the MBS service authentication request sent by the MBS Proxy or the Anchor MBS DPF to the MBS Server can also be used. A bearer channel setup request is included, and a bearer channel is requested to be established on the MBS Proxy or the Anchor MBS DPF and the MBS Server for transmitting the MBS service. The implementation of the bearer channel between MBS Proxy or Anchor MBS DPF and MBS Server can be through GRE, Layer 2 Tunneling Protocol (L2TP), VLAN, MPLS, IP Security (IPSec), etc. Tunnel technology can be implemented by IP multicast technology, such as IGMP and Multicast Discovery (MLD).

d) If the MBS Proxy or Anchor MBS DPF also receives the maximum MBS service capability information of the terminal, if the MBS Proxy or Anchor MBS DPF or the ASN-GW where the MBS Proxy or Anchor MBS DPF is located holds the actual MBS service The capability requirement, that is, the resource reservation information, the MBS Proxy or the Anchor MBS DPF can determine whether the terminal can normally receive the MBS service according to the received maximum capability information of the terminal and the resource reservation information required by the MBS service; If the ASN-GW where the MBS Proxy or the Anchor MBS DPF is located does not have the resource reservation information of the MBS service, the received maximum MBS service capability information of the terminal may be saved for subsequent determination.

205, after the MBS Server receives the MBS service authentication request from the MBS Proxy or the Anchor MBS DPF, If the MBS service subscription information of the terminal is maintained, the MBS service subscription information and/or the MBS service authentication information is used to confirm whether the terminal has the right to enjoy the MBS service, such as whether the terminal subscribes to the MBS service. Whether the group or the terminal has been authorized to obtain the authorization key (MAK) of the MBS service; if the MBS Server does not maintain the corresponding information and cannot determine whether the terminal has the capability to enjoy the MBS service, the MBS Server can also PDF requests for MBS service authentication.

If the PDF receives the MBS service authentication request from the MBS Server or the MBS Proxy or the Anchor MBS DPF, the user can determine whether the terminal has the ability to enjoy the MBS service according to the user subscription information and the service policy, and return the service authentication result to the MBS Server or Return to MBS Proxy or Anchor MBS DPF. Optionally, the PDF may also send the MBS service subscription information of the terminal to the MBS Server or the MBS Proxy or the Anchor MBS DPF, so that the MBS Server or the MBS Proxy or the Anchor MBS DPF can process the received terminal in a later process. MBS service authentication request.

206. The MBS Server or PDF returns the MBS service authentication result to the MBS Proxy or Anchor MBS DPF through the MBS service authentication response, such as an MBS Auth Rsp message. Optionally, the MBS Server or the PDF may also send the MBS service subscription information of the terminal to a functional entity such as an SFA in the ASN-GW where the MBS Proxy or the Anchor MBS DPF or the MBS Proxy or the Anchor MBS DPF is located. Therefore, the MBS Proxy or Anchor MBS DPF can process the received MBS service join request of the terminal in the future process.

Optionally, any of the following conditions exist in this step:

a) Optionally, if the broadcast range of the MBS service is dynamically established, and no terminal in the ASN or the MBS Zone has received the MBS service, the MBS Server may update the downlink play of the MBS service after the MBS service is successfully authenticated. The list, that is, the identifier or IP address of the ASN-GW or MBS Proxy or Anchor MBS DPF where the MBS Proxy or Anchor MBS DPF is located is added to the downlink playlist of the MBS service.

b) Optionally, after the MBS service is successfully authenticated, the MBS Server updates the user statistics of the MBS service, so that the MBS Server determines the actual number of users currently using the MBS service.

c) Optionally, if the ASN network entity, such as the BS and the ASN-GW, has not previously obtained the resource reservation information and/or the bearer channel information required by the MBS service, the MBS Server may also deliver the MBS service request in this step. Resource reservation information and/or bearer channel information.

d) corresponding to the option b) of step 204, if the MBS Server receives the resource reservation request from the MBS Proxy or the Anchor MBS DPF, it determines whether to accept the resource reservation application according to its own resource status and service policy, and may In this step, the result of the resource reservation is returned to the MBS Proxy or the Anchor MBS DPF.

e) Corresponding to step 204 of option c), if MBS Server receives from MBS Proxy or Anchor MBS

The DPF bearer channel establishment request, the MBS Server determines whether to connect according to its own resource status and service policy. Subject to this request, and in this step, the result of the bearer channel establishment can be returned to the MBS Proxy or Anchor MBS DPF.

207, MBS Proxy or Anchor MBS DPF receives the MBS service authentication response from MBS Sever or PDF, and returns an MBS service join response message to the Serving ASN-GW according to the MBS service authentication result carried by the MBS Proxy or the MBS DGW, for example, may be an MBS Response message.

Optionally, any of the following conditions may exist in this step:

a) corresponding to the situation a) in step 203, if the resource reservation application of the Serving ASN-GW is received, it is determined according to the network resource status and the service policy whether to accept the resource reservation application, and if accepted, the corresponding resource reservation is performed. In this step, the result of the resource reservation can be returned to the Serving ASN-GW.

b) corresponding to the case b) in the step 203, if receiving the bearer channel establishment request of the Serving ASN-GW, determining whether to accept the request according to the network resource status and the service policy, and if yes, performing the corresponding bearer channel establishment, In the step, the result of the bearer channel establishment is returned to the Serving ASN-GW.

c) Optionally, if in the case d) of step 204, if the ASN-GW where the MBS Proxy or the Anchor MBS DPF is located does not have the resource reservation information required by the MBS, the terminal capability cannot be judged, but after In the step, if the MBS service resource reservation information sent by the MBS Server or the PDF is received in the step 206, the MBS service resource reservation information sent by the MBS Proxy or the Anchor MBS DPF according to the MBS Server or the PDF and the situation in step 204 are obtained. d) The maximum MBS service capability information of the terminal stored in the terminal determines whether the terminal can receive the MBS service normally. In this step, the Serving ASN-GW decision result may be notified.

d) Optionally, if the broadcast range of the MBS service is dynamically established, and no terminal in the Serving ASN-GW receives the MBS service, the MBS Proxy or the Anchor MBS DPF may also update the MBS service after the MBS service is successfully authenticated. The downlink playlist of the MBS service, that is, the Serving ASN-GW identifier is added to the downlink playlist of the MBS service.

e) Optionally, the MBS Proxy or the Anchor MBS DPF receives the message that the MBS service is successfully authenticated, and can update the user statistics of the MBS service, so as to correctly count the number of users currently using the MBS service in the BS range, and further The number of users using the MBS service in the ASN or MBS Zone can be known.

f) Corresponding to the situation in step 206, c), optionally, after obtaining the resource reservation information and/or the bearer channel information of the MBS service, the information may be sent to the Serving ASN_GW in this step.

g) MBS Proxy or Anchor MBS DPF can also send information about whether the MBS service session starts to Serving ASN_GW.

If the MBS Proxy or Anchor MBS DPF is integrated in the Serving ASN-GW, step 207 may be omitted.

208. Optionally, the Serving ASN-GW receives the MBS service join response message, if the authentication succeeds and the MBS After the business session has started, the Anchor Service Flow Authorizer Anchor SFA (Anchor Service Flow)

Authorization, Anchor SFA) sends an MBS service join request message, such as an RR-REQ message,

The MBS service join request message may carry the MBS Zone ID, and further, may carry information such as the terminal identifier MSID and/or the MBS service authentication information.

The Anchor SFA described in the embodiment of the present invention is only described by taking a logical function entity as an example. In a specific networking, the Anchor SFA logical function entity may be a separate physical entity, or may be integrated in other physical entities, such as Into the service network gateway ASN-GW (Access Service Network GateWay) or base station.

209. Optionally, the Anchor SFA receives the MBS service join request message from the Serving ASN-GW, sends an MBS service authentication request to the policy decision entity PDF, and requests the policy decision entity PDF to verify whether the terminal has the right to receive the MBS service. . The request may also carry an MBS Zone ID, and further, may carry a network access identifier (NAI) and/or MBS service authentication information of the terminal.

If the Anchor SFA has already stored the MBS service subscription information, the Anchor SFA may not send the MBS service authentication request to the PDF, and the Anchor SFA may process the MBS service of the terminal according to the maintained MBS service subscription information and/or the MBS service authentication information. Join the request.

If the PDF receives an authentication request from the Anchor SFA, it determines whether the terminal has the ability to enjoy the MBS service according to the user subscription information and the service policy, and returns the service authentication result to the Anchor SFA. Optional,

The PDF can also send the MBS service subscription information of the terminal to the Anchor SFA, so that the Anchor SFA can process the received MBS service authentication request of the terminal in the subsequent process.

210. The Anchor SFA allocates a Service Flow Identifier (SFID) to the MBS service, and returns the service flow identifier SFID to the Serving ASN-GW through the MBS service join response.

The RR-RSP message is returned to the Serving ASN_GW. If the Anchor SFA also performs the MBS service authorization, the SFID is assigned after the service authorization is successful, and the authorization result can also be returned to the Serving ASN_GW.

211. The Serving ASN-GW receives the MBS service join response, and returns a result of the MBS service join request to the BS through the MBS service join response according to the authentication result of the bearer, for example, the result can be returned by using the RR-RSP or the DP-RSP message. In the embodiment of the present invention, the MBS service join response may be an MBS service join response from the MBS Proxy or the Anchor MBS DPF in 207, or may be an MBS service join response from the Anchor SFA in 210.

Optionally, any of the following conditions may exist in this step:

a) Corresponding to case a) in 202, if the Serving ASN-GW receives the resource reservation request of the BS, it determines whether to accept the resource reservation application according to the network resource status and the service policy. If accepted, the corresponding resource reservation is made. In this step, the result of the resource reservation can be returned to the BS. b) Corresponding to case b) in 202, if the Serving ASN-GW receives the bearer channel creation request of the BS, the Serving ASN-GW determines whether to accept the request according to the network resource status and the service policy. If accepted, the corresponding bearer channel setup is performed. In this step, the result of the bearer channel establishment can be returned to the BS.

c) Optionally, if in case cc in 203, the Serving ASN-GW does not have the resource reservation information of the MBS service, the terminal capability cannot be judged, but in the subsequent step, as in step 207, To MBS

If the MBS service resource reservation information is sent by the server, the ASN-GW determines whether the terminal can be normal according to the MBS service resource reservation information sent by the MBS server and the maximum MBS service capability information of the terminal saved in the case c) in step 203. Receiving the MBS service, the BS decision result may be notified in this step.

d) Optionally, if the broadcast range of the MBS service is dynamically established, and no terminal in the BS receives the MBS service, the Serving ASN-GW needs to update the downlink play of the MBS service after the MBS service is successfully authenticated. For the list, the base station identity BSID may be added to the downlink playlist of the MBS service.

e) Optionally, after receiving the message that the MBS service is successfully authenticated, the Serving ASN-GW may update the user statistics of the MBS service, so that the Serving ASN-GW or the MBS Proxy correctly counts the MBS currently used in the BS range. The number of users of the service, and thus the number of users using the MBS service in the ASN or MBS Zone.

f) Corresponding to the situation in step 206, c), optionally, after obtaining the resource reservation information and/or the bearer channel information of the MBS service, the Serving ASN-GW may send the information to the BS in this step.

g) Optionally, if the Serving ASN-GW learns that the MBS service session has not started yet, the return service does not start to indicate to the BS, and terminates the MBS service joining process, and proceeds to step 219.

212~214, optionally, after the BS receives the MBS service join response, if the broadcast range of the MBS service between the BS and the Serving ASN-GW is dynamically established, and no terminal in the BS receives the MBS service, Serving The ASN-GW does not update the downlink playlist. After the MBS service is successfully authenticated, the BS registers the MBS service with the Serving ASN-GW, and triggers the Serving ASN-GW to update the saved downlink playlist of the MBS service, that is, in the MBS. The base station identifier (BSID) is added to the downlink playlist of the service; after the Serving ASN-GW updates the downlink playlist, if the bearer channel between the Serving ASN-GW and the MBS Proxy or the Anchor MBS DPF has not been established yet, and the Serving ASN-GW is not Initiating the registration of the MBS service to the MBS Proxy or the Anchor MBS DPF, and the U Serving ASN-GW may further register with the MBS Proxy or the Anchor MBS DPF to update the MBS service downlink playlist on the MBS Proxy or the Anchor MBS DPF, that is, trigger the MBS. The Proxy or Anchor MBS DPF adds the Serving ASN-GW identifier or IP address to the downlink playlist of the MBS service; after the MBS Proxy or Anchor MBS DPF updates the downlink playlist, If the bearer channel between MBS Proxy or Anchor MBS DPF and MBS Server has not been established yet, and MBS Proxy or Anchor MBS DPF does not initiate registration of the MBS service to MBS Server, MBS Proxy or Anchor MBS DPF can further forward to MBS Server. Registering to update the MBS service downlink playlist on the MBS Server, that is, triggering the MBS Server to add the identifier or IP address of the ASN-GW or MBS Proxy or Anchor MBS DPF where the MBS Proxy or Anchor MBS DPF is located in the downlink playlist of the MBS service. .

Optionally, when the MBS Sever responds to the registration request, the corresponding resource reservation information and/or bearer channel information is sent. After the ASN-GW receives the request, the MBS service further responds to the registration request of the BS. The resource reservation information and/or bearer channel information is sent to the BS.

215. Optionally, after the BS receives the resource reservation information and/or the bearer channel information, if the bearer channel and/or the resource reservation between the BS and the Serving ASN-GW for transmitting the MBS service is not pre-configured, And in the previous step, the BS does not send the corresponding resource reservation request and/or the bearer channel creation request, and the Serving ASN-GW does not deliver the resource reservation request and/or the bearer channel creation request, In the step, the BS sends a resource reservation request and/or a bearer channel setup request to the Serving ASN-GW to reserve resources and/or establish a corresponding bearer channel for transmitting the MBS service between the BS and the Serving ASN-GW.

216. Optionally, the Serving ASN-GW performs corresponding resource reservation for the MBS service and/or establishes a corresponding bearer channel, if the bearer between the Serving ASN-GW and the MBS Proxy or the Anchor MBS DPF is used to transmit the MBS service. The channel and/or resource reservation is not pre-configured, and in the previous step, the Serving ASN-GW did not send the corresponding resource reservation request and/or bearer channel creation request, and the MBS Proxy or Anchor MBS DPF did not. Sending a resource reservation request and/or a bearer channel creation request, in this step, the Serving ASN-GW sends a resource reservation request and/or a bearer channel establishment request to the MBS Proxy or the Anchor MBS DPF, in order to transmit the MBS service. Transmission between the Serving ASN-GW and the MBS Proxy or Anchor MBS DPF for resource reservation and/or establishment of corresponding bearer channels.

217. Optionally, the MBS Proxy or the Anchor MBS DPF performs corresponding resource reservation for the MBS service and/or establishes a corresponding bearer channel, if the bearer for transmitting the MBS service between the MBS Proxy or the Anchor MBS DPF and the MBS Server is used. The channel and/or resource reservation is not pre-configured, and in the previous step, the corresponding resource reservation has not been performed and/or the corresponding bearer channel has been created. In this step, MBS Proxy or Anchor MBS DPF to MBS The server sends a resource reservation request and/or a bearer channel establishment request to reserve resources and/or establish a corresponding bearer channel for transmitting the MBS service between the MBS Proxy or the Anchor MBS DPF and the MBS Server.

218. Optionally, if the BS transmits the MBS service by using a link layer multicast mode, and the MBS service is not a broadcast service, the BS further needs to obtain an MBS Group Tracfi Encryption Key (MGTEK). This key is used to generate a service encryption key (MTK) when the MBS service is transmitted in an air interface.

The BS can request the MBS by sending a request message for the MGTEK key to the MBS Proxy or the Anchor MBS DPF. The Proxy or the Anchor MBS DPF sends the generated MGTEK to the BS. If the MBS Proxy or the Anchor MBS DPF does not currently generate the MGTEK for the MBS service, the MGTEK is generated for the MBS service, and the generated MGTEK is sent to the BS. .

If the BS already has MGTEK or the MGTEK can be generated by the BS, omit this step or trigger the BS to generate MGTEK in this step.

219. The BS sends an MBS service join response message to the terminal, where the message may be a DSA-RSP message, where the message carries the MBS Zone ID, the air interface connection identifier CID, or the air interface connection identifier MCID corresponding to the MBS service that the terminal requests to join. Or all MBS content identifiers, multicast security association identifier GSA IDs, or service flow identifiers SFIDs carried on the MCID. If the MBS service session has not started or the MBS service join authorization fails, the failure result is returned and the join process is terminated.

220. The BS sends an MBS service join confirmation message to the Serving ASN-GW, and may be an RR-ACK or a DP-ACK message, to confirm that the MBS service join process is completed.

Optionally, when the terminal joins the MBS service, the BS can update the user statistics of the MBS service in the coverage area.

221. After obtaining the multicast SA identity, the terminal sends a key request message to the BS, such as a Key.

The request message is used to request the multicast service key MGTEK of the MBS service, and the request message carries the GSA ID of the MBS service.

222. After receiving the request, the BS sends the previously generated or obtained MGTEK to the terminal by using a key response message, such as a Key Reply message, and the terminal jointly generates an MBS service encryption key MTK according to the previously obtained MAK and MGTEK, and The corresponding MBS service is received according to the multicast broadcast service parameter obtained from the network side.

In this embodiment, the resource reservation information may be description information of resources required to carry the MBS service, such as classifier parameters and rules, QoS parameters, and/or header compression parameters and rules.

In this embodiment, the bearer channel information may be a resource description message required for a bearer channel carrying the MBS service, such as a bearer channel type, a bearer channel identifier, and/or a bearer channel protocol type.

In this embodiment, the maximum MBS service capability information of the terminal refers to the maximum resource description information that the terminal currently holds, which can receive the MBS service, such as bandwidth and packet loss rate. Usually refers to the device capacity of the terminal or the sum of resources that are not currently occupied. The MBS service can be a standard defined service flow (SF).

In this embodiment, if the terminal requests to join the MBS multicast service, the terminal needs to subscribe to the MBS service and obtain the authorization key (MAK) of the MBS service before joining the MBS service. If the terminal requests to join the MBS broadcast service, the authentication process may not be required in the foregoing process, and the request message of the steps 201 to 203 may not carry the MBS service authentication information, or the authentication information is only used to notify the network side. Each node joins the terminal MBS business. At this time, the service authentication of the step 204 can be omitted, and no further service authentication result or service authorization information is required to be sent in the subsequent steps.

In the embodiment of the present invention, the BS and the Servi ng ASN-GW may be two separate entities, or may be integrated in the same physical entity. If they are integrated in the same physical entity, the message interaction between them may be It is to interact with internal primitives.

In the embodiment of the present invention, the terminal initiates the MBS service joining process by sending an MBS service joining request to the network side, and obtains the MBS service parameter from the network side, and then joins the MBS service. The terminal may send an MBS service join request message through the DSA process, and carry the MBS domain identifier in the message to inform the network side of the MBS service that the terminal needs to join. Further, the network side or the terminal itself compares the maximum capability of the terminal with the minimum required for the MBS service, and determines whether the terminal is capable of carrying the MBS service, preventing the terminal from receiving services outside the capability range, causing waste of network resources and Additional loss of the terminal.

Further, when the terminal joins the service, the base station or the ASN gateway or the MBS proxy or the MBS server needs to re-statisticize the number of users using the MBS service, so that the MBS service can be carried in a reasonable mode; When using the MBS service, the ASN gateway or the MBS proxy or the MBS server needs to update the related service playlist to ensure that the content of the playlist matches the actual content.

Further, if the resource or bearer channel between the base station and the ASN gateway or the ASN gateway and the MBS server for carrying the MBS service is not pre-configured, and the corresponding resource reservation and bearer channel are not established, the base station or The ASN gateway or the MBS server can perform resource reservation and bearer channel establishment at any time before the MBS service parameters are delivered to the terminal according to the resource reservation information and the bearer channel information that are actually required by the MBS service.

The method for the terminal to join the MBS service in another wireless network according to the embodiment of the present invention is substantially the same as the foregoing embodiment. The difference is that, in the foregoing embodiment, the terminal carries the MBS Zone ID in the request message for joining the MBS service. The MBS service needs to be added. However, in the present embodiment, the terminal may further carry the MBS content identifier of the MBS service in addition to the MBS Zone ID in the request message. MBS Content ID. Therefore, in this embodiment, the standard needs to be modified so that the MBS Content ID can be carried in the MBS service join request, such as the DSA-REQ message.

The method for the terminal to join the MBS service in another wireless network according to the embodiment of the present invention is substantially the same as the foregoing embodiment, and the difference is that, in the foregoing implementation manner, the terminal needs to carry the request message for joining the MBS service. The MBS Zone ID of the MBS service and the specific MBS Content ID of the MBS service are requested to be added. The present embodiment is improved on the basis of the foregoing embodiment. In this embodiment, the MBS Content ID of the MBS service is globally unique. In the join request message, you can only carry the specified MBS Content ID, no need to care Which MBS Zone the service is broadcast on. In this embodiment, the standard needs to be modified, and the MBS service ID is required to be included in the MBS service join request, such as the DSA-REQ message.

In another embodiment of the present invention, a method for a terminal to join an MBS service in a wireless network, in this embodiment, may use a layer 3 multicast technology to assist in completing a process for a terminal to join an MBS service, so that the existing air interface protocol may not be changed. Based on the process of completing the terminal to join a specified MBS service.

In this embodiment, the terminal obtains the MBS service-related IP multicast address list and the MBS Content ID list carried by the MBS service before the MBS service is added. Further, the terminal may further include an IP multicast address and The correspondence between the MBS Content ID and/or the MBS Zones in which the MBS service is broadcast. In a specific application, the terminal may obtain the above information in the service announcement phase or through other means. Before initiating the MBS service joining process, the terminal can learn which MBS zones the BS belongs to by detecting the DCD message broadcasted by the BS, so as to determine whether the terminal is in the MBS service that the UE wants to join. MBS Zone, if not, do not initiate the join process. Specifically as shown in Figure 3.

301. The terminal sends an MBS service join request to an anchor ASN. The request may be an IGMP join, where the request carries an IP multicast address list of the MBS service to be joined. Further, in the embodiment of the present invention, the MBS The service join request may also carry the MBS service content identifier and/or the MBS service authentication information.

In this embodiment of the present invention, the message may be carried on an initial service flow (ISF) channel of the terminal.

302, the anchor ASN receives the MBS service join request of the terminal, and sends an MBS service join request to the Serving ASN-GW, for example, the MBS Request message, where the request carries the IP multicast group address list of the MBS service that the terminal wants to join, and further The terminal identifier MSID, the MBS service content identifier, and/or the MBS service authentication information may also be carried.

303. After receiving the MBS service join request of the terminal, the Serving ASN-GW sends an MBS service join request to the MBS Proxy or the Anchor MBS DPF, for example, the MBS Join Request message, where the request carries the IP address of the MBS service that the terminal wants to join. The broadcast group address list may further carry the terminal identifier MSID, the MBS service content identifier, and/or the MBS service authentication information.

304. Optionally, the MBS Proxy or the Anchor MBS DPF receives the MBS service join request, and sends an MBS service authentication request to the MBS Server or to the policy decision entity PDF, for requesting to verify whether the terminal has the right to receive the MBS service. The IP multicast group address list may also be carried in the authentication request. Further, the network access identifier NAI, MBS service authentication information, and/or MBS Content ID of the terminal may also be carried.

Optionally, there are the following situations in this step:

a) if a functional entity on the ASN-GW where the MBS Proxy or MBS Proxy is located, such as SFA, The MBS service subscription information has been saved, that is, the MBS Proxy has been able to perform the MBS service authentication process, and the MBS Proxy or the Anchor MBS DPF can send the MBS service authentication request to the MBS Server or the PDF, which can be based on the maintained MBS service subscription information. And/or the MBS service authentication information to process the MBS service join request of the terminal.

b) If the bearer channel between the MBS Proxy or the Anchor MBS DPF and the MBS Server for transmitting the MBS service is not pre-configured and the corresponding bearer channel has not been created, the MBS sent by the MBS Proxy or the Anchor MBS DPF to the MBS Server The service authentication request may further include a bearer channel setup request, and apply for establishing a bearer channel on the MBS Proxy or the Anchor MBS DPF and the MBS Server for transmitting the MBS service. The implementation of the bearer channel between the MBS Proxy or the Anchor MBS DPF and the MBS Server may be implemented by using a tunneling technology such as GRE, L2TP, VLAN, MPLS, or IPSec, or by using an IP multicast technology, such as IGMP or MLD. .

In this step, if the MBS Server receives the MBS service authentication request, if it maintains the MBS service subscription information of the terminal, it searches for the MBS service authorization information to find and confirm whether the terminal has the ability to enjoy the MBS service; If the corresponding subscription information is not maintained and the terminal cannot be judged whether it has the ability to enjoy the MBS service, the MBS Server can also request the MBS service authentication from the PDF. The PDF judges whether the terminal has the ability to enjoy the MBS service according to the user subscription information and the service policy, and informs the MBS Server of the service authentication result or returns to the MBS Proxy or the Anchor MBS DPF. In this case, optionally, the PDF can simultaneously send the MBS service subscription information of the terminal to the MBS Server or the MBS Proxy or the Anchor MBS DPF, so that the MBS Server or the MBS Proxy or the Anchor MBS DPF can be in the process. The received MBS service authentication request of the terminal can be processed.

Optionally, the MBS service authentication result is returned to the MBS Proxy or Anchor MBS in the MBS Server.

In the DPF, the MBS service subscription information of the terminal can be sent to the MBS Proxy or Anchor MBS DPF or a functional entity in the ASN-GW where the MBS Proxy or Anchor MBS DPF is located, such as SFA, so that the MBS Proxy can be followed. The received MBS service join request of the terminal can be processed in the process.

In addition, optional, there may be the following situations in this step:

Al) Optionally, if the broadcast range of the MBS service is dynamically established, and no terminal in the ASN or MBS Zone receives the MBS service, the MBS Server can directly update the downlink of the MBS service after the MBS service is successfully authenticated. The playlist, that is, the identifier or IP address of the ASN-GW or MBS Proxy or Anchor MBS DPF where the MBS Proxy or Anchor MBS DPF is located is added to the downlink playlist of the MBS service.

b l ) Optionally, after the MBS service is successfully authenticated, the MBS Server updates the user statistics of the MBS service, so that the MBS Server counts the actual number of users using the MBS service.

c) optional, if the MBS Proxy or Anchor MBS DPF is located in the ASN-GW or MBS Porxy or Anchor The MBS DPF does not know the resource reservation information and/or bearer channel information required by the MBS service. In this step, the MBS Server can deliver the resource reservation information and/or bearer channel information required by the MBS service.

d) Corresponding to the situation in step 304 b), the MBS Server determines whether to accept the request to create a bearer channel according to its own resource status and service policy. In this step, the result of the bearer channel establishment is returned to the MBS Proxy or Anchor MBS DPF.

305. After receiving the MBS service authentication result from the MBS Server, the MBS Proxy or Anchor MBS DPF returns an MBS service join response to the Serving ASN-GW according to the authentication result, and may be an MBS Join Response message, in the response message. It can carry instructions indicating whether the MBS service session has started.

306. The Serving ASN-GW returns the MBS service join response to the Anchor ASN, and may be an MBS Reply message, where the response message may carry an indication that the MBS service session has started.

307. The Anchor ASN receives the MBS service join response. If the authentication succeeds and the MBS service session has started, the MBS service join request is sent to the Anchor SFA. For example, the request may be an MBS Request message, and the request may carry the MBS Zone ID. If the MBS service session has not started or the MBS service authentication fails, the joining process is terminated, and the subsequent steps are not executed.

308. Optionally, the Anchor SFA receives the MBS service join request from the Anchor ASN, sends an MBS service authentication request to the MBS Server or to the policy decision entity PDF, and requests the MBS Server or PDF to verify whether the terminal has the MBS service. right. The MBS service authentication request may further carry an MBS Zone ID, and further, may also carry a network access identifier (NAI) of the terminal and/or MBS service authentication information. Of course, if the Anchor SFA has already stored the MBS service subscription information, the Anchor SFA may not send the MBS service authentication request to the MBS Server or the PDF, and may itself subscribe to the MBS service joining request of the information processing terminal according to the maintained MBS service.

The MBS server receives the MBS service authentication request, and if it maintains the MBS service subscription information of the terminal, retrieves the MBS service subscription information, and confirms whether the terminal has the right to enjoy the MBS service, such as whether the terminal is in the MBS service. In the subscription group, and whether the terminal has been authorized to obtain the authorization key (MAK) of the MBS service, etc.; if the MBS Server does not maintain the corresponding information and cannot independently determine whether the terminal has the ability to enjoy the MBS service, the MBS Server can also request MBS service authentication from PDF requests.

309. Optionally, if the PDF receives the MBS service authentication request from the MBS Server or the Anchor SFA, determine, according to the user subscription information and the service policy, whether the terminal has the capability to enjoy the MBS service, and return the service authentication result to the MBS. Server or return to Anchor SFA. Optionally, the PDF may also send the MBS service subscription information of the terminal to the MBS Server or the Anchor SFA, so that the MBS Server or the Anchor SFA is after the MBS Server or the Anchor SFA. The process can process the received MBS service authentication request of the terminal.

310, MBS Server or PDF returns the MBS service authentication result to Anchor SFA through the MBS service authentication response. Optionally, the MBS Server or the PDF may also send the MBS service subscription information of the terminal to the ASN_GW where the Anchor SFA or the Anchor SFA is located, so that the ASN-GW where the Anchor SFA is located can process the received terminal in the future process. The MBS service joins the request.

31 1 . After receiving the MBS service join request from the Anchor ASN, the Anchor SFA allocates a service flow identifier SFID ( Servi ce Fl ow I dent if i er ) for the MBS service, and returns the identifier to the Anchor ASN through the MBS service join response. , such as can be an MBS Response message. If the MBS service authentication of steps 308 to 310 is also performed, the SFID may be allocated after the service authentication, and the authentication result may also be returned to the Anchor ASN.

312. After receiving the MBS service join response from the Anchor SFA, the Anchor ASN may send an MBS service creation request to the BS according to the carried result, such as an RR-REQ or a DP-REQ message. This request may need to be sent to the BS via Servi ng ASN-GW.

Optionally, the following situations may exist in this step:

a) if the resource for carrying the MBS service between the BS and the Servi ng ASN-GW is not pre-configured, and the corresponding resource reservation has not been performed (ie, the BS does not send the resource reservation request in the previous step), Anchor

The MBS service creation request sent by the ASN to the BS may further include a resource reservation request, and apply for corresponding bearer resources on the BS and the Servi ng ASN-GW for carrying the MBS service.

b) if the bearer channel between the BS and the Servi ng ASN-GW for transmitting the MBS service is not pre-configured, and the corresponding bearer channel has not been created (ie, the BS has not sent the bearer channel creation request in the previous step), The MBS service creation request sent by the Anchor ASN to the BS may further include a bearer channel setup request, and apply for establishing a bearer channel on the BS and the Serving ASN-GW for transmitting the MBS service. The implementation of the bearer channel between the BS and the Serving ASN-GW can be implemented by tunneling technologies such as GRE, VLAN, and MPLS.

c) Optionally, if the broadcast range of the MBS service is dynamically established, and no terminal in the BS receives the MBS service, the Servicing ASN-GW may update the downlink playlist of the MBS service after the MBS service is successfully authenticated. That is, the base station identity BS ID is added to the downlink playlist of the MBS service.

d) Optionally, after the MBS service is successfully authenticated, the MBS Proxy or the Serving ASN-GW can update the user statistics of the MBS service, so that the Serving ASN-GW or the MBS Proxy counts the number of users using the MBS service under the BS. The number of users using the MBS service in the ASN or MBS Zone can also be known.

313. Optionally, if the MBS service is transmitted by using the link layer multicast mode, and the MBS service is not a broadcast service, the BS further needs to obtain an MBS group service encryption key MGTEK, where the key is used to generate an MBS service in an air interface transmission. When the business encryption key MTK. The BS may request to send the generated MGTEK to the BS by sending a request message for the MGTEK key to the MBS Proxy or the Anchor MBS DPF. If the MBS Proxy or the Anchor MBS DPF does not currently generate the MGTEK for the MBS service, the first The MBS service generates MGTEK, and then the generated MGTEK is sent to the BS.

314. After receiving the MBS service creation request, the BS may send an MBS service creation request to the terminal, such as a DSA-REQ message, where the MBS service creation request may carry the MBS Zone ID and the air interface corresponding to the MBS service to be joined. The connection identifier CID or the air interface multicast connection identifier MCID, all the MBS content identifiers carried on the CID or MCID, the MBS Content ID, the multicast security association identifier GSA ID or the unicast security association, the QoS parameters of the MBS service, and the service flow identifier SFID. one or more.

There is no fixed sequence between this step and step 313.

315. After receiving the MBS service creation request from the BS, the terminal determines whether the MBS service can be normally received according to the QoS parameter requirement of the MBS service and the maximum MBS service capability that the terminal itself can bear, and if yes, save the corresponding MBS service context. . The terminal responds to the MBS service creation response to the BS. If it is a DSA-RSP message, the MBS service creation response may carry the result of joining the MBS service.

316. Optionally, if the broadcast range of the MBS service is dynamically established, and no terminal in the BS has received the MBS service, that is, the BS does not register the MBS service with the Serving ASN-GW, the BS may send the Serving ASN to the Serving ASN. The GW initiates a service registration to update the downlink playlist of the MBS service in the Serving ASN-GW, that is, add the base station identity BS ID in the downlink playlist of the MBS service.

317, optional, Serving ASN-GW updates the downlink playlist of the MBS service, if before Serving

No terminal in the ASN receives the MBS service. That is, the Serving ASN-GW does not register the MBS service with the MBS Proxy or the Anchor MBS DPF. In this step, the Serving ASN-GW registers with the MBS Proxy or the Anchor MBS DPF to update the MBS. The service downlink playlist, that is, the identifier or IP address of the Serving ASN-GW is added to the downlink playlist of the MBS service in the MBS Proxy or Anchor MBS DPF.

318. Optionally, the MBS Proxy or the Anchor MBS DPF updates the downlink playlist of the MBS service. If no terminal in the previous ASN or MBS Zone receives the MBS service, the MBS Proxy or the Anchor MBS DPF does not register with the MBS Server. MBS service, in this step, the MBS Proxy or Anchor MBS DPF registers with the MBS Server to update the MBS service downlink playlist in the MBS Server, that is, add the MBS Proxy or Anchor MBS DPF to the downlink playlist of the MBS service in the MBS Server. The identifier or IP address of the ASN-GW or MBS Proxy or Anchor MBS DPF.

Optionally, in this step, if the MBS Proxy or Anchor MBS DPF is used with the MBS Server If the bearer channel and/or the resource reservation for transmitting the MBS service is not established, and the corresponding resource reservation information and/or bearer channel information is not previously delivered, the MBS Server may also send the resource reservation information when responding to the registration request. And / or bearer channel establishment information. After receiving the registration request of the Serving ASN-GW, the MBS Proxy or the Anchor MBS DPF may further send the resource reservation information and/or bearer channel information of the MBS service to the Serving ASN-GW. The Serving ASN-GW may further deliver the resource reservation information and/or bearer channel information of the MBS service to the BS in response to the registration request of the BS.

319. Optionally, if the bearer channel and/or resource reservation between the BS and the Serving ASN-GW for transmitting the MBS service is not pre-configured, and in the previous step, the BS does not perform corresponding resource reservation. Requesting and/or creating a corresponding bearer channel request, the Serving ASN-GW also does not initiate a resource reservation request and/or creates a corresponding bearer channel request, in this step, the BS may send a resource reservation request to the Serving ASN-GW. And/or carrying a channel establishment request, performing resource reservation and/or establishing a corresponding bearer channel for transmitting the MBS service between the BS and the Serving ASN-GW.

320. Optionally, if the Serving ASN-GW receives the resource reservation request and/or the bearer channel establishment request from the BS, it may determine, according to the network resource condition, whether to agree to perform corresponding resource reservation and/or establish a corresponding bearer channel. . In addition, if the bearer channel and/or resource reservation between the Serving ASN-GW and the MBS Proxy or the Anchor MBS DPF for transmitting the MBS service is not pre-configured, and in the previous step, the MBS Proxy or Anchor is not addressed. The MBS DPF sends a corresponding resource reservation request and/or a request to create a corresponding bearer channel, and the Serving ASN-GW sends a resource reservation request and/or a bearer channel establishment request to the MBS Proxy or the Anchor MBS DPF, in order to transmit the MBS service. The Serving ASN-GW transmits between the MBS Proxy or the Anchor MBS DPF for resource reservation and/or establishes a corresponding bearer channel.

321. Optionally, after receiving the resource reservation request and/or the bearer channel establishment request from the Serving ASN-GW, the MBS Proxy or Anchor MBS DPF may determine whether to agree to perform resource reservation and/or according to network resource conditions. Establish corresponding bearer channels. In addition, if the bearer channel and/or resource reservation between the MBS Proxy or the Anchor MBS DPF and the MBS Server for transmitting the MBS service is not pre-configured, and in the previous step, the corresponding resource is not sent to the MBS Sever. To reserve a request and/or create a request for a corresponding bearer channel, the MBS Proxy or Anchor MBS DPF may send a resource reservation request and/or a bearer channel setup request to the MBS Server for transmitting the MBS service in MBS Proxy or Anchor MBS DPF and The MBS Server transfers resources for resource reservation and/or establishes corresponding bearer channels.

322. The BS sends the MBS service creation response of the terminal to the Anchor ASN, and may be an RR-RSP or a DP-RSP, and may also be sent to the Anchor ASN through the Serving ASN-GW.

Optionally, the following situations may exist in this step: a) If, in case a) of step 312, the anchor ASN further includes a resource reservation request in the MBS service creation request sent by the BS, the BS may determine whether to accept the resource according to the air interface resource status and the admission control policy in this step. Reserve application. If accepted, the corresponding resource reservation is made. In this step, you can also return the result of the resource reservation to the Anchor ASN.

b) If, in step 312 b), the anchor ASN sends a request for the bearer channel creation request to the BS, the BS may determine whether to accept the bearer according to the air interface resource status and the admission control policy. Channel establishment application. If accepted, the corresponding bearer channel setup is performed. In this step, the result of the bearer channel establishment can also be returned to the Anchor ASN.

323. After receiving the MBS service creation response, the BS sends an MBS service creation confirmation to the terminal, such as a DSA-ACK message, to confirm that the process is completed.

324. After obtaining the multicast security association identifier, the terminal sends a key request message to the BS, such as a Key Reques t, a multicast service key MGTEK for requesting the MBS service, where the request message carries the GSA of the MBS service. ID.

325. After receiving the request, the BS sends the previously generated or obtained MGTEK to the terminal, and the terminal jointly generates the MBS service encryption key MTK according to the previously obtained MAK and MGTEK, and receives according to the multicast broadcast service parameter acquired from the network side. The corresponding MBS service.

In this embodiment, if the terminal requests to join the MBS multicast service, the terminal needs to subscribe to the MBS service and obtain the authorization key (MAK) of the MBS service before joining the MBS service. If the terminal requests to join the MBS broadcast service, the authentication process is not required in the foregoing process, and the request message of steps 301 to 303 may not carry the MBS service authentication information, or the authentication information is only used to notify each node on the network side. The terminal joins the MBS service. The service authentication of the step 304 can be omitted, and no service authentication result or service authorization information is required to be sent in the subsequent steps.

In the embodiment of the present invention, the terminal may send an MBS service join request to initiate an MBS service join process by using an Internet Group Management Protocol message, and the IP multicast service address may be carried in the message, and the MBS service that the terminal needs to join may also be indicated on the network side, thereby The MBS service parameters are obtained from the network side to further join the MBS service. Further, the network side or the terminal itself compares the maximum capability of the terminal with the minimum required for the MBS service, and determines whether the terminal is capable of carrying the MBS service, preventing the terminal from receiving services outside the capability range, causing waste of network resources and Additional loss of the terminal.

Further, when the terminal joins the service, the base station or the ASN gateway or the MBS proxy or the MBS server needs to re-statisticize the number of users using the MBS service, so that the MBS service can be carried in a reasonable mode; When using this MBS service, the ASN gateway or MBS proxy or MBS server needs to be performed. Update the related business playlist to ensure that the content of the playlist matches the actual.

Further, if the resource or bearer channel between the base station and the ASN gateway or the ASN gateway and the MBS server for carrying the MBS service is not pre-configured, and the corresponding resource reservation and bearer channel are not established, the base station or The ASN gateway or the MBS server may perform the resource reservation and the bearer channel at any time before the MBS service parameter is delivered to the terminal according to the resource reservation information and the bearer channel information that are actually required by the MBS service. A method for the terminal to join the MBS service in the wireless network is provided. The embodiment is substantially the same as the foregoing embodiment. The difference is that, in this embodiment, the Anchor ASN first goes to the Anchor SFA to perform service authorization and obtains the service flow identifier SFID. Send an MBS service join request to the MBS Proxy or Anchor MBS DPF and know if the MBS service session has started. Specifically, as shown in FIG. 4, 402 to 406 are similar to 307 to 311; 407 to 41 1 are similar to 302 to 306; and 412 to 425 are similar to 312 to 325, and will not be described again.

The embodiment of the present invention further provides a method for a terminal to join an MBS service in a wireless network. In this embodiment, an MBS service is initiated by the network side, and the process may occur in a process of establishing a preset flow after the terminal accesses the network. It can also occur when the network side entity requires dynamic establishment of the MBS service. For the multicast service, before the network side requests the terminal to add the MBS service, the terminal needs to subscribe to the MBS service and obtain the authorization key MAK of the MBS service, where the subscription message can be included in the subscription message of the user. Specifically as shown in Figure 5.

In this embodiment, the network side entity sends the MBS service creation request to the following possibilities: If the user's subscription information has been delivered to the access network entity, such as the Anchor ASN, in the initial network access phase, in step 501, Optionally, the MBS service creation request may be initiated by a function entity in the Anchor ASN or the Anchor ASN, such as the SFA, where the service flow identifier SFID is further carried in the request, and further, the terminal identifier MSID may be carried.

Alternatively, optionally, a core network entity, such as a PDF or MBS Server, sends an MBS service creation request to the Anchor SFA, where the message may carry a NAI or MS ID.

502. Optionally, the Anchor SFA may send an MBS service creation request, such as an RR-REQ message, to the Anchor ASN, where the request may carry the service flow identifier SFID allocated by the Anchor SFA.

503. The Anchor ASN receives the MBS service creation request from the Anchor SFA, and sends an MBS service creation request to the Serving ASN-GW, such as an RR-REQ or a DP-REQ message, where the request may carry the Anchor. The service flow identifier SFID assigned by the SFA.

504. The Serving ASN-GW receives the MBS service creation request from the Anchor ASN, and may send an MBS service join request to the MBS Proxy or the Anchor MBS DPF, such as an MBS Context Request. The message may include information such as a service flow identifier SFID, a terminal identifier MS ID, an MBS service multicast address IP Mul ti cast Addres s, or an MBS service identifier MBS Servi ce ID.

505, MBS Proxy or Anchor MBS DPF receives the MBS service join request from the Serving ASN-GW. If the MBS service transmission uses the IP multicast technology at the IP layer, the MBS Proxy or the Anchor MBS DPF can also notify the corresponding multiple. The multicast router (Mul ti cast Route, MR) adds the terminal to the corresponding multicast group. The MBS Proxy or Anchor MBS DPF may return an MBS Service Join Response to the Serving ASN-GW, such as an MBS Context Respons e message.

In addition, the following options are also available in this step:

a) Optionally, if the broadcast range of the MBS service is dynamically established, and the terminal does not receive the MBS service in the Serving ASN-GW, the MBS Proxy or the Anchor MBS DPF may update the downlink playlist of the MBS service. That is, the Servi ng ASN-GW identifier or IP address is added to the downlink playlist of the MBS service.

b) Optionally, the MBS Proxy or Anchor MBS DPF updates the user statistics of the MBS service so that the MBS Proxy or Anchor MBS DPF counts the number of users using the MBS service in the MBS Zone.

c) If the resource for carrying the MBS service between the Serving ASN-GW and the MBS Proxy or the Anchor MBS DPF is not pre-configured, and the corresponding resource reservation has not been performed, the MBS Proxy or the Anchor MBS DPF to the Serving ASN- The MBS service join response sent by the GW may further include a resource reservation request, and apply for corresponding bearer resources on the MBS Proxy or the Anchor MBS DPF and the Serving ASN-GW to carry the MBS service.

d) If the bearer channel between the Serving ASN-GW and the MBS Proxy or the Anchor MBS DPF for transmitting the MBS service is not pre-configured and the corresponding bearer channel has not been created, the MBS Proxy or the Anchor MBS DPF to the Serving ASN The MBS service join response sent by the GW may further include a bearer channel setup request, and apply for establishing a bearer channel on the Serving ASN-GW and the MBS Proxy or the Anchor MBS DPF for transmitting the MBS service. The bearer channel can be implemented by tunneling technologies such as GRE, VLAN, and MPLS.

506. The Serving ASN-GW sends an MBS service creation request to the BS, such as an RR-REQ or a DP-REQ message.

You can also include the following options in this step:

a) Optionally, if the broadcast range of the MBS service is dynamically established, and the terminal does not receive the MBS service in the previous BS, the Servi ng ASN-GW may update the downlink playlist of the MBS service, that is, in the MBS The base station identity BS ID is added to the downlink playlist of the service.

b) Optionally, the Serving ASN-GW updates the user statistics of the MBS service, so that the Servi ng ASN-GW counts the number of users using the MBS service under the ASN. c) If the resource for carrying the MBS service between the Serving ASN-GW and the BS is not pre-configured, and the corresponding resource reservation has not been performed, the Serving ASN-GW may also send the MBS service creation request to the BS. The resource reservation request is included, and the corresponding bearer resource is applied to the BS and the Serving ASN-GW for carrying the MBS service.

If the bearer channel between the BS and the Serving ASN-GW for transmitting the MBS service is not pre-configured, and the corresponding bearer channel has not been created, the MBS service creation request sent by the Serving ASN-GW to the BS may further include The bearer channel establishment request is applied to establish a bearer channel on the BS and the Serving ASN-GW for transmitting the MBS service. The bearer channel can be implemented by tunneling technologies such as GRE, VLAN, and MPLS.

507. Optionally, if the BS transmits the MBS service by using a link layer multicast mode, and the MBS service is not a broadcast service, the BS may request an MBS service key MGTEK to the MBS Proxy or the Anchor MBS DPF, where the key is used to generate The service encryption key MTK of the MBS service when transmitting in the air interface.

The BS may request the MBS Proxy or the Anchor MBS DPF to send the generated MGTEK to the BS by sending a request message for the MGTEK key to the MBS Proxy or the Anchor MBS DPF, and the request message may be sent to the MBS Proxy through the Serving ASN-GW or Anchor MBS DPF. If the MBS Proxy or the Anchor MBS DPF has not yet generated the MGTEK for the MBS service, the MGTEK is generated for the MBS service, and the generated MGTEK is sent to the BS.

If the BS already has MGTEK or the MGTEK can be generated by the BS, this step can be omitted or the BS can be triggered to generate MGTEK in this step.

508, the BS sends an MBS service creation request to the terminal, for example, a DSA-REQ message, where the MBS service creation request may carry the service flow identifier SFID and the air interface connection identifier CID corresponding to the MBS service to be joined, and further, may carry the MBS. One or more of the zone ID, the air interface multicast connection identifier, the MCID, the at least one MBS content identifier MBS Content ID, the multicast SA identity GSA ID or the unicast SA identity, and the QoS parameters of the MBS service carried on the CID or MCID .

509. The terminal receives the MBS service creation request, and determines whether the MBS service can be normally received according to the QoS parameter requirement of the MBS service and the maximum MBS service capability that the terminal itself can bear. If yes, the corresponding MBS service context is saved. The MBS service creation response is returned to the BS, and may be a DSA-RSP message, and the MBS service creation response may carry the result of joining the MBS service.

510. Optionally, if the broadcast range of the MBS service is dynamically established, and the terminal does not receive the MBS service in the BS, that is, the BS does not register the MBS service with the Serving ASN-GW, the BS may send the Serving ASN to the Serving ASN. The GW initiates registration to update the downlink playlist of the MBS service, that is, adds the base station identity BSID to the downlink playlist of the MBS service in the Serving ASN-GW.

511. Optionally, the Serving ASN-GW updates the downlink playlist of the MBS service, if the previous Serving If no terminal in the ASN receives the MBS service, that is, the Serving ASN-GW does not register the MBS service with the MBS Proxy or the Anchor MBS DPF, in this step, the Serving ASN-GW can register with the MBS Proxy or the Anchor MBS DPF to update the MBS Proxy. Or the MBS service downlink playlist in the Anchor MBS DPFr, that is, the identifier or IP address of the Serving ASN-GW is added to the downlink playlist of the MBS service in the MBS Proxy or Anchor MBS DPF.

512. Optionally, the MBS Proxy or the Anchor MBS DPF updates the downlink playlist of the MBS service. If no terminal in the MBS Zone receives the MBS service, the MBS Proxy or the Anchor MBS DPF does not register the MBS service with the MBS Server. In this step, the MBS Proxy or the Anchor MBS DPF registers with the MBS Server to update the MBS service downlink playlist in the MBS Server, that is, the MBS Proxy or Anchor MBS DPF in the downlink playlist of the MBS service in the MBS Server. The identity or IP address of the ASN-GW or MBS Proxy or Anchor MBS DPF.

Optionally, in this step, if the bearer channel and/or resource reservation for transmitting the MBS service between the MBS Proxy or the Anchor MBS DPF and the MBS Server is not established, the corresponding resource reservation information is not previously delivered. And/or carrying the channel information, the MBS Server may also send resource reservation information and/or bearer channel establishment information in response to the registration request. After receiving the registration request of the Serving ASN-GW, the MBS Proxy or the Anchor MBS DPF may further send the resource reservation information and/or bearer channel information of the MBS service to the Serving ASN-GW. After receiving the registration request of the BS, the Serving ASN-GW may further deliver the resource reservation information and/or bearer channel information of the MBS service to the BS.

513. Optionally, if the bearer channel and/or resource reservation between the BS and the Serving ASN-GW for transmitting the MBS service is not pre-configured, and corresponding resource reservation and/or corresponding creation is not performed. Carrying the channel, and in step 506, the serving ASN-GW does not include the resource reservation request and/or the bearer channel establishment request in the MBS service creation request sent by the BS, in this step, the BS sends the resource to the Serving ASN-GW. A reservation request and/or a bearer channel establishment request is used to reserve resources and/or establish a corresponding bearer channel for transmission between the BS and the Serving ASN-GW for transmitting the MBS service.

514. Optionally, the Serving ASN-GW receives the resource reservation request and/or the bearer channel establishment request from the BS, and determines whether to agree to perform resource reservation and/or establish corresponding according to the network resource condition of the Serving ASN. Bearer channel, if the bearer channel and/or resource reservation between the Serving ASN-GW and the MBS Proxy or the Anchor MBS DPF for transmitting the MBS service is not pre-configured, and the corresponding resource reservation and/or creation has not been performed yet. The corresponding bearer channel, the U Serving ASN-GW sends a resource reservation request and/or a bearer channel setup request to the MBS Proxy or the Anchor MBS DPF, and transmits the MBS service between the Serving ASN-GW and the MBS Proxy or the Anchor MBS DPF. Perform resource reservation and/or establish corresponding bearer channels. 515. Optionally, the MBS Proxy or the Anchor MBS DPF receives the resource reservation request and/or the bearer channel establishment request from the Serving ASN-GW, and determines whether to agree to perform corresponding resource reservation and/or establishment according to the air interface resource condition. Corresponding bearer channel, if the bearer channel and/or resource reservation between the MBS Proxy or Anchor MBS DPF and the MBS Server for transmitting the MBS service is not pre-configured, and the corresponding resource reservation and/or creation has not been performed yet. The corresponding bearer channel, the MBS Proxy or the Anchor MBS DPF may send a resource reservation request and/or a bearer channel setup request to the MBS Server, and reserve resources for transmitting the MBS service between the MBS Proxy or the Anchor MBS DPF and the MBS Server. And / or establish a corresponding bearer channel.

516. The BS receives the MBS service creation response, and returns the MBS service join request result to the Serving ASN-GW through the MBS service creation response, for example, sending the RR-RSP or DP-RSP message to the Serving ASN-GW.

Optionally, the following situations may exist in this step:

a) Corresponding to the case c) in the step 506, if the serving request is included in the MBS service creation request sent by the Serving ASN-GW to the BS, in this step, the BS determines whether to accept according to the air interface resource status and the admission control policy. The resource reservation application, if accepted, performs corresponding resource reservation, and may also inform the Serving ASN-GW resource reservation result in this step.

b) Corresponding to the case d) in the step 506, if the MBS service creation request sent by the Serving ASN-GW to the BS includes the bearer channel establishment request, in this step, the BS determines whether to accept according to the air interface resource status and the admission control policy. The bearer channel of the application is established. If yes, the corresponding bearer channel is established. In this step, the result of establishing the bearer channel of the Serving ASN-GW can also be notified.

517. The Serving ASN-GW returns an MBS service creation response to the Anchor ASN, such as an RR-RSP or a DP-RSP message.

518. The Anchor ASN returns the MBS service creation response to the Anchor SFA, such as an RR-RSP message.

519. After receiving the MBS service creation response, such as a DSA-RSP, the BS sends an MBS service creation confirmation to the terminal, for example, a DSA-ACK message is used to confirm that the service joining process has been completed.

520. After obtaining the multicast SA identity, the terminal sends a key request message to the BS, such as a Key.

The request is used to request the multicast service key MGTEK of the MBS service, and the request message carries the GSA ID of the MBS service.

521. After receiving the request, the BS sends the previously generated or obtained MGTEK to the terminal, and the terminal jointly generates the MBS service encryption key MTK according to the previously obtained MAK and MGTEK, and receives according to the multicast broadcast service parameter acquired from the network side. The corresponding MBS service.

In each of the above embodiments, each entity may exist independently or exist in a functional entity, and the foregoing entities are in the same In a physical entity, the interaction between them uses internal primitives. For example, the Serving ASN-GW and the BS can be the same physical entity, and the MBS Proxy and the ASN-GW can be the same physical entity.

The MBS Proxy entity is a functional entity for processing MBS service signaling and/or services for the terminal in the ASN network or MBS Zone. In the foregoing embodiments, the functional entity may be located in the Anchor ASN or in the Serving ASN-GW, or may exist independently in the MBS Zone. When the MBS Proxy is located in the Anchor ASN, its message interaction with the Anchor ASN is implemented through internal primitives.

In the embodiment of the present invention, the MBS service joining process is initiated by the network side, and the terminal obtains the MBS service parameter from the network side to join the MBS service. Further, the terminal itself compares the maximum capability of the terminal with the minimum required for the MBS service, and determines whether the terminal is capable of carrying the MBS service, preventing the terminal from receiving services outside the capability range, causing waste of network resources and additional terminal. loss.

Further, if the resource or bearer channel between the base station and the ASN gateway or the ASN gateway and the MBS server for carrying the MBS service is not pre-configured, and the corresponding resource reservation and bearer channel are not established, the base station or The ASN gateway or the MBS server may perform the resource reservation and the bearer channel at any time before the MBS service parameter is delivered to the terminal according to the resource reservation information and the bearer channel information that are actually required by the MBS service. A system for a terminal to join a multicast broadcast service in a wireless network, including a terminal and a network side, where the network side includes a process for joining an MBS service to a terminal when the terminal accesses the network or dynamically establishes an MBS service, and is a terminal. A unit that provides MBS service parameters. The service parameter includes a first identifier indicating an air interface connection and a second identifier indicating a service content; the terminal further includes a unit for acquiring an MBS service parameter from the network side; and the air interface indicated by the first identifier according to the acquired MBS service parameter a unit that receives the MBS service content indicated by the second identifier in the connection; and/or a unit that sends an MBS service join request message to the network side, initiates an MBS service join process by using the request message, and obtains an MBS service parameter.

In addition, the network side may also include one of the following units or any combination thereof:

a unit for judging whether a terminal is capable of receiving MBS services;

a unit for performing MBS service authentication on a terminal;

a unit for network side resource reservation for MBS services;

a unit for establishing a bearer channel for an MBS service; a unit for registering MBS services and/or updating a playlist of downlinks;

a unit for generating a key for an MBS service;

a unit for generating a first identifier for the MBS service;

A unit for generating a second identity for the MBS service.

The above unit may be one of the following or any combination thereof: base station, ASN-GW, MBS proxy (MBS Proxy), anchor MBS data function (Anchor MBS DPF), service access service network gateway (Serving ASN-GW), anchor Access Service Network (Anchor ASN), Anchor Service Flow Authorization Entity (Anchor SFA), MBS Server, Policy Decision Entity (PDF).

The entities such as the BS, the MBS Proxy Anchor MBS DPF, the Serving ASN-GW, the Anchor ASN, and the Anchor SFA described in the above embodiments are described by taking a logical functional entity as an example. In a specific networking, these logical functional entities are described. It can be a separate physical entity, or it can be integrated in the same physical entity. If any two or more of these logical functional entities are integrated in the same physical entity, the steps of interaction between them can be omitted.

The policy decision entity PDF described in the foregoing embodiments may be an authentication, authorization, accounting server AAA, a policy charging decision function (PCRF), a home subscriber server (HSS), or a resource standard. The core network entity, such as the RACS (Resource and Admission Subsystem), is not limited here.

The embodiment of the present invention further provides a terminal, including a first unit, configured to: acquire the MBS service parameter from a network side, where the MBS service parameter includes a first identifier for indicating an air interface connection and a first part for indicating service content. And the second unit is configured to: receive, according to the acquired MBS service parameter, the MBS service content indicated by the second identifier from the air interface connection indicated by the first identifier.

Further, in the embodiment of the present invention, the terminal may further include a third unit: configured to send an MBS service join request message to the network side, and initiate an MBS service join process by using the request message.

In this way, the terminal provided by the implementation of the present invention can obtain the MBS service parameter from the network side, thereby joining the MBS service.

The embodiment of the present invention further provides a network side functional entity, which may be an Anthor SFA. As shown in FIG. 6, the method includes:

The obtaining unit 601 is configured to obtain an MBS service join request that carries the first identifier of the service from the terminal, or an MBS service creation request that carries the second identifier of the service from the multicast multicast service server MBS Server and/or the policy decision entity PDF;

The sending unit 602 is configured to send, to the base station BS, an MBS service creation request that carries the first identifier of the service or the second identifier of the service, where the MBS service creation request is used by the BS to initiate an MBS service creation process. Further, the functional entity may further include:

a second sending unit 603, configured to send, to the MBS Server and/or the PDF, a service authentication request that carries the first identifier of the service;

The receiving unit 604 is configured to receive a service authentication response sent by the MBS Server and/or the PDF.

The first service identifier is an IP multicast address of the MBS service.

Further, the functional entity may further include:

a third transmitting unit 605;

Correspondingly, the second sending unit 603 is further configured to send, to the multicast multicast service proxy MBS Proxy/anchor multicast multicast service data channel function entity Anthor MBS DPF, an MBS service join request that carries the service first identifier; the receiving unit 604 And receiving the MBS service joining response of the fourth identifier carrying the service returned by the MBS Proxy/Anthor MBS DPF, where the fourth identifier of the service is allocated by the MBS Proxy/Anthor MBS DPF;

Correspondingly, the third sending unit 605 is configured to send, to the base station BS, an MBS service creation request that carries the first identifier of the service and the fourth identifier of the service, where the fourth identifier of the service is a multicast connection identifier (MCID) of the MBS service and / or unicast multicast service type indication for MBS services.

Further, the service second identifier is an IP multicast address and/or a service flow identifier of the MBS service.

Further, the second sending unit 603 is further configured to send, to the MBS Proxy/Anthor MBS DPF, an MBS service creation request that carries the second identifier of the service;

The receiving unit 604 is further configured to receive an MBS service creation response that carries the fourth identifier of the service returned by the MBS Proxy/Anthor MBS DPF, where the fourth identifier of the service is allocated by the MBS Proxy/Anthor MBS DPF; correspondingly, the third sending The unit 605 is further configured to send, to the base station BS, an MBS service creation request that carries the second identifier of the service and the fourth identifier of the service, where the fourth identifier of the service is a multicast connection identifier of the MBS service, and the MCID and/or the MBS service. Unicast multicast service type indication.

For a detailed description of the function of the Anthor SFA, refer to the corresponding part of the above method embodiment, and details are not described herein again.

In the embodiment of the present invention, the MBS service joining request of the first identifier of the carrying service from the terminal, or the MBS service carrying the second identifier of the carrying service from the multicast multicast service server MBS Server and/or the policy decision entity PDF is created. Sending an MBS service creation request carrying the service first identifier or the service second identifier to the base station BS, so that the terminal can successfully join the MBS service and receive the MBS service.

The foregoing embodiments are exemplified by a WiMAX wireless system, but are also applicable to other wireless systems, such as a 3GPP/SAE network, where the Serving ASN-GW corresponds to a Serving GW in a 3GPP/SAE network, and the Anchor ASN corresponds to 3GPP/SAE. The PDN-GW in the network; the same applies to 3GPP2 and its subsequent evolved networks. No longer here A narrative.

A person skilled in the art can understand that all or part of the steps of implementing the above embodiments can be completed by a program to instruct related hardware, and the program can be stored in a computer readable storage medium. , including the following steps:

The terminal obtains a multicast broadcast service MBS service parameter from the network side, where the MBS service parameter includes a first identifier for indicating an air interface connection and a second identifier for indicating a service content.

The terminal receives the MBS service content indicated by the second identifier from the air interface connection indicated by the first identifier according to the MBS service parameter.

The above-mentioned storage medium may be a read only memory, a magnetic disk or an optical disk or the like.

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

Claims

Claim

The method according to claim 1, wherein when the anchor service flow licensor Anthor SFA obtains the MBS service joining request from the terminal that carries the first identifier of the service, the method further includes:

The Anthor SFA sends a service authentication request carrying the first identifier of the service to the MBS Server and/or PDF;

The Anthor SFA receives a service authentication response sent by the MBS Server and/or PDF.

The method according to claim 2, wherein the service first identifier is an IP multicast address of the MBS service.

The method according to claim 3, wherein after the MBS service is successfully authenticated, the method further comprises: a multicast multicast service proxy MBS Proxy/anchor multicast multicast service data channel function entity Anthor MBS

The DPF sends an MBS service join request that carries the first identifier of the service;

Receiving, by the MBS Proxy/Anthor MBS DPF, the MBS service carrying the fourth identifier of the service is added, and the fourth identifier of the service is allocated by the MBS Proxy/Anthor MBS DPF;

Correspondingly, the Anthor SFA sends an MBS creation service request carrying the first identifier of the service to the base station BS, including:

And sending, to the base station BS, an MBS service creation request that carries the first identifier of the service and the fourth identifier of the service, where the fourth identifier of the service is a multicast connection identifier of the MBS service, and a unicast of the MBS service. Broadcast service type indication.

5. The method of claim 1 wherein:

The second identifier of the service is an IP multicast address and/or a service flow identifier of the MBS service.

The method according to claim 5, wherein the anchor service flow authorizer Anthor SFA obtains the second identifier of the service carrying the service from the multicast multicast service server MBS Server and/or the policy decision entity PDF After the MBS service creation request, it also includes:

Sending an MBS service creation request carrying the second identifier of the service to the MBS Proxy/Anthor MBS DPF; receiving an MBS service creation response that carries the fourth identifier of the service returned by the MBS Proxy/Anthor MBS DPF, where the fourth identifier of the service is determined by The MBS Proxy/Anthor MBS DPF allocation;

Correspondingly, the Anthor SFA sends an MBS service creation request carrying the second identifier of the service to the base station BS, including:

Sending, to the base station BS, an MBS service creation request that carries the second identifier of the service and the fourth identifier of the service, where the fourth identifier of the service is a multicast connection identifier of the MBS service, and a unicast of the MBS service. Broadcast service type indication.

The method according to claim 2, wherein after receiving the service authentication response sent by the MBS Server and/or the PDF, the Anthor SFA further includes:

The MBS Proxy/ Anthor MBS DPF initiates the bearer channel establishment process to the BS.

The method according to claim 4, wherein, after the MBS Server and/or PDF successfully authenticates the terminal, the method further includes:

The MBS Server and/or PDF updates the user statistics of the MBS service; or

Notifying the MBS Proxy/ Anthor MBS DPF to update the user statistics of the MBS service; or

The BS is notified to update the user statistics of the MBS service.

The method according to claim 4 or 6, wherein when the MBS service uses the IP multicast technology at the IP layer, the method further includes:

The MBS proxy informs the multicast router to join the terminal to the corresponding multicast group.

10. A network side functional entity, comprising:

The obtaining unit (601) is configured to obtain an MBS service joining request for carrying the service first identifier from the terminal, or an MBS service carrying the second identifier carrying the service identifier from the multicast multicast service server MBS Server and/or the policy decision entity PDF request; The sending unit (602) is configured to send, to the base station BS, an MBS service creation request that carries the first identifier of the service or the second identifier of the service, where the MBS service creation request is used by the BS to initiate an MBS service creation process.

The network side functional entity according to claim 10, further comprising:

a second sending unit (603), configured to send, to the MBS Server and/or the PDF, a service authentication request that carries the first identifier of the service;

The receiving unit (604) is configured to receive a service authentication response sent by the MBS Server and/or the PDF.

The network side functional entity according to claim 10, wherein the service first identifier is an IP multicast address of the MBS service.

The network side functional entity according to claim 11, further comprising:

a third transmitting unit (605);

The second sending unit (603) is further configured to send, to the multicast multicast service proxy MBS Proxy/anchor multicast multicast service data channel function entity Anthor MBS DPF, an MBS service join request that carries the first identifier of the service; The receiving unit (604) is further configured to receive an MBS service join response that carries the fourth identifier of the service returned by the MBS Proxy/Anthor MBS DPF, where the fourth identifier of the service is allocated by the MBS Proxy/Anthor MBS DPF;

Correspondingly, the third sending unit (605) is configured to send, to the base station BS, an MBS service creation request that carries the first identifier of the service and the fourth identifier of the service, where the fourth identifier of the service is an MBS service. The multicast connection identifies the unicast multicast service type indication for the MCID and/or MBS service.

14. The network side functional entity of claim 13 wherein:

15. The network side functional entity of claim 14 wherein:

The second sending unit (603) is further configured to send, to the MBS Proxy/the Anthor MBS DPF, an MBS service creation request that carries a second identifier of the service;

The receiving unit (604) is further configured to receive an MBS service creation response that carries the fourth identifier of the service returned by the MBS Proxy/Anthor MBS DPF, where the fourth identifier of the service is allocated by the MBS Proxy/Anthor MBS DPF;

Correspondingly, the third sending unit (605) is further configured to send, to the base station BS, the second label carrying the service. And the MBS service creation request of the fourth identifier of the service, where the fourth identifier of the service is a multicast connection identifier (MCID) of the MBS service and/or a unicast multicast service type indication of the MBS service.

The network side functional entity according to any one of claims 10 to 15, wherein the network side functional entity is an Anthor SFA.