CN101155343B - Method and system for adding multicast broadcasting service to terminal in wireless network - Google Patents

Abstract

The present invention relates to the wireless communication domain, a method for adding multicast broadcast service into a terminal of a wireless network and system thereof are disclosed, to lead the terminal to be capable of adding MBS service, and receiving MBS service content. In the present invention, the terminal acquires the MBS service parameter from the network side, wherein containing a first identification for indicating empty ora connection and a second identification for indicating service content, to lead the terminal to be capable of receiving MBS service content of the second identification indication from the empty ora connection in the first identification indication after receiving the MBS service parameter, and successfully adding the MBS service. The terminal is capable of initiating MBS service adding course through sending adding MBS service requested message, to acquire MBS service parameter and add desired MBS service; the network side can also initiate actively MBS service adding course, to send MBS service parameter to the terminal, and invite the terminal add MBS service.

Description

Method and system for terminal to join multicast broadcast service in wireless network

Technical Field

The invention relates to the field of wireless communication, in particular to a multicast broadcast technology.

Background

IEEE802.16 is an Institute of electrical and electronics Engineers ("IEEE") standard promulgated in 12 months 2001 for providing last mile wireless broadband access in metropolitan area networks. The IEEE802.16 standard mainly includes three standards, 802.16a, 802.16RevD and 802.16 e.

Worldwide Interoperability for Microwave Access (WiMAX) is a wireless metropolitan area network Access technology based on IEEE802.16 series standards in the industry at present, and a basic objective of the technology is to provide a broadband wireless Access means capable of effectively interoperating in a multi-vendor environment of a metropolitan area network point-to-multipoint.

Specifically, the 802.16 series of standards specify the protocol layers of the air interface part of the WiMAX system, which mainly include a physical layer (PHY) and a Medium Access Control (MAC) layer. The PHY layer physically completes operations such as modulation and demodulation, encoding and decoding of signals, and the MAC layer mainly completes a media access control function of the WiMAX system.

Fig. 1 shows a WiMAX end-to-end reference model. Wherein the R1 interface is a wireless air interface, mainly defined by ieee802.16d/e. And the other interfaces are wired interfaces.

As can be seen, WiMAX mainly includes a Mobile Station (MS)/a Subscriber Station (SS), an Access Service Network (ASN) and a Connectivity Service Network (CSN).

The ASN is defined as a network function set providing wireless access service for WiMAX user terminals, and includes a BS and an ASN GateWay (ASN GateWay abbreviated as "ASN-GW") network element, and one ASN may be shared by multiple CSNs.

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

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

Communication is generally referred to as communication between one node and another node, but as the demand of users increases and various media are introduced, users need to perform one-to-many or many-to-many communication, so that a Point-to-Multipoint (PTM) transmission mode is generated. In order to support these modes on the mobile network, a one-to-many multicast broadcast service is implemented, and meanwhile, in order to effectively utilize the mobile network resources, the prior art defines the MBS service on the basis of WiMAX. The MBS service is a point-to-multipoint service that provides one data source to send data to multiple users in a mobile network, thereby implementing network resource sharing, and improving the utilization rate of network resources, especially air interface resources. The MBS defined in WiMAX can not only realize the pure text low-rate message multicast and broadcast, but also realize the multicast and broadcast of high-speed multimedia services, which undoubtedly follows the trend of future mobile data development.

The MBS service based on the 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 MBS domain (i.e. MBS Zone, identified by MBS _ Zone id) is defined, where a MBS domain is a set of base stations, all base stations in a MBS domain use the same Multicast CID and MBS Group security association (MBS Group security association, abbreviated as "MBS GSA"), send the content of the same MBS service stream, a terminal registered with MBS service can receive MBS service data through multiple base stations in the MBS domain, and when the terminal in idle state moves across base stations in the MBS domain, it does not need to re-establish connection, and can receive MBS service without being affected, thereby implementing seamless switching of MBS service. The single base station accessing MBS is a special case of accessing the MBS by a plurality of base stations, the range of an MBS domain is limited to be within the coverage range of one base station, and all users receiving the MBS in one MBS domain use the same multicast connection identifier. The prior art does not describe the single base station mode in detail; however, in the multi-base station mode, how the base station sends the MBS data, how the terminal receives the MBS data, and how the base station notifies the terminal of sending the MBS data that the terminal is interested in are described correspondingly.

The existing protocol has corresponding description on an air interface in an MBS system, but has no relevant technology on how a terminal joins in an MBS service.

Disclosure of Invention

The invention mainly aims to provide a method and a system for adding a multicast broadcast service into a terminal in a wireless network, so that the terminal can successfully add an MBS service and receive MBS service contents.

In order to achieve the above object, the present invention provides a method for a terminal to join a multicast broadcast service in a wireless network, wherein the terminal acquires MBS service parameters of the multicast broadcast service from a network side, and the MBS service parameters comprise a first identifier for indicating air interface connection and a second identifier for indicating 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;

wherein, if no terminal currently receives the MBS service in the access service network or MBS domain, the method also comprises the following steps:

the MBS server directly updates the downlink play list of the MBS service stored by the MBS server; or,

the access service network gateway or MBS agent requests the MBS server to register the MBS service, and triggers the MBS server to update the stored downlink play list of the MBS service.

The terminal obtains the MBS service parameters from the network side by sending a request message for joining the MBS service or by an MBS service joining process initiated by the network side.

In addition, in the method, the terminal sends the request message for joining the MBS service through the dynamic service flow adding process, and the request message comprises MBS content identification and/or MBS domain identification.

In addition, in the method, the joining process of the MBS service is assisted by a 3-layer multicast technology, and the request message for joining the MBS service sent by the terminal comprises an IP multicast address list and/or an MBS content identifier of the MBS service.

In addition, in the method, the network side sends a request for joining the MBS service to the terminal when the terminal accesses the network or requires to dynamically establish the MBS service, and initiates the joining process of the MBS service;

the request for joining the MBS service sent to the terminal comprises an air interface connection identifier of the MBS service, one or more MBS content identifiers and/or a multicast security alliance identifier.

In addition, in the method, before the network side initiates an MBS service joining process to the terminal or the terminal sends the request message for joining the MBS service, the terminal subscribes the MBS service and acquires the authorization key of the MBS service.

In addition, in the method, before the network side initiates an MBS service joining process to the terminal or sends the MBS service parameters to the terminal, the network side authenticates the MBS service to the terminal according to the MBS service subscription information of the terminal and/or the MBS service authentication result of the terminal, and determines that the terminal is authorized to receive the MBS service.

In addition, in the method, the network element of the network side initiating the MBS service joining process is one of the following: the anchor is accessed into a service network gateway or a functional entity, an MBS server and an MBS agent in the gateway;

the network element for the network side to perform MBS service authentication on the terminal is one of the following elements: the anchor access service network gateway or the functional entity in the gateway, MBS server, MBS agent, authentication, authorization and accounting server.

In addition, in the method, after any network element of the anchor access service network gateway or the functional entity, the MBS server, the MBS agent, the authentication, the authorization and the charging server in the gateway completes the MBS service authentication of the terminal, the authentication result and/or the MBS service subscription information are/is sent to one of the other network elements or any combination thereof.

In addition, in the method, the request message for joining MBS service sent by the terminal also contains MBS service authentication information, the network side authenticates MBS service to the terminal according to MBS service subscription information, MBS service authentication information and/or MBS service authentication result of the terminal, and determines whether the terminal is authorized to receive MBS service.

In addition, in the method, the request for joining MBS service also includes information indicating the maximum MBS service capability of the terminal, and the network side identifies whether the terminal can receive the MBS service according to the maximum MBS service capability of the terminal and/or the service resource reservation information of the MBS stored by the network side.

In addition, in the method, the MBS service parameter also comprises MBS service quality parameter, after the terminal receives the MBS service parameter, the terminal determines whether the terminal can receive the MBS service according to the maximum MBS service capability of the terminal and the MBS service quality parameter.

In addition, in the method, if the broadcast range of the MBS service is dynamically established and no terminal currently receives the MBS service in the base station, the method further comprises the following steps:

the access service network gateway directly updates the downlink play list of the MBS service stored by the access service network gateway;

or, the base station requests the access service network gateway to register the MBS service, and triggers the access service network gateway to update the downlink play list of the MBS service stored in the access service network gateway.

In addition, in the method, after the terminal joins the MBS service, the method further includes the following steps:

and the MBS server, the access service network gateway/MBS agent and the base station respectively update the user statistics of the MBS service.

In addition, in the method, if the resources and/or bearer channels used for carrying the MBS service between the base station and the access serving network gateway are not pre-configured, the method further comprises the following steps:

if the resource reservation between the base station and the access service network gateway and/or the establishment of a corresponding bearing channel are not carried out when the terminal requests to join the MBS service, and the base station holds the resource reservation information and/or the bearing channel information required by the MBS service, the base station requests the access service network gateway or the MBS agent to carry out the resource reservation and/or the establishment of the bearing channel according to the resource reservation information and/or the bearing channel information required by the MBS service;

and the access service network gateway or the MBS agent determines whether to accept the resource reservation request and/or the bearer channel establishment request according to the network resource condition and the service strategy.

In addition, the method also comprises the following steps:

if the terminal has not performed corresponding resource reservation and/or established corresponding bearer channel after the terminal passes the MBS service authentication,

the access service network gateway or the MBS agent performs resource reservation and/or bearer channel establishment for the transmission of the MBS service between the base station and the access service network by sending a resource reservation request and/or a bearer channel establishment request to the base station; or the MBS server sends down the resource reservation information and/or the bearing channel information required by the MBS service, and the base station requests a service network gateway or an MBS agent to reserve resources and/or establish a bearing channel according to the resource reservation information and/or the bearing channel information;

and the base station or the access service network gateway or the MBS agent determines whether to accept the corresponding resource reservation request and/or the bearer channel establishment request according to the network resource condition and the service strategy.

In addition, in the method, if the resource for carrying the MBS service between the access service network gateway and the MBS server is not pre-configured, the method further comprises the following steps:

if the terminal does not perform corresponding resource reservation and/or establish corresponding bearing channel when requesting to join the MBS service, and the access service network gateway/MBS agent holds the resource reservation information and/or bearing channel information required by the MBS service, the access service network gateway or MBS agent requests the MBS server to perform resource reservation and/or establish the bearing channel according to the resource reservation information and/or bearing channel information required by the MBS service;

and the MBS server determines whether to accept the resource reservation request and/or the bearer channel establishment request according to the network resource condition and the service strategy.

In addition, the method also comprises the following steps:

if the terminal has not performed corresponding resource reservation and/or established corresponding bearer channel after the terminal passes the MBS service authentication,

the MBS server performs resource reservation and/or bearer channel establishment for the transmission of the MBS service between the access service network and the MBS server by sending a resource reservation request and/or bearer channel establishment request to the access service network gateway or the MBS agent;

or, the MBS server sends down the resource reservation information and/or the bearer channel information required by the MBS service, and the access service network gateway or the MBS agent requests the MBS server to reserve resources and/or establish the bearer channel according to the resource reservation information and/or the bearer channel information;

and the access service network gateway or the MBS agent or the MBS server determines whether to accept the corresponding resource reservation request and/or the bearer channel establishment request according to the network resource condition and the service strategy.

In addition, in the method, the first identifier is an air interface unicast connection identifier, or an air interface multicast connection identifier, or an air interface broadcast identifier;

the second identification is MBS content identification or IP multicast address of the multicast group;

the MBS service parameter further includes one or any combination of the following:

the MBS system comprises MBS domain identification corresponding to the MBS service, at least one MBS content identification, multicast safety alliance identification, unicast safety alliance identification, MBS service quality parameter and MBS service stream identification.

In addition, in the method, after the terminal acquires the multicast security alliance identifier, the terminal acquires the service key of the MBS from the base station, and receives the MBS service content through the MBS service encryption key by utilizing the MBS service key and the MBS service encryption key generated by the MBS authorization key issued by the network side to the terminal.

In addition, in the method, the MBS service key is generated by the base station, or obtained by the base station from the access service network gateway or the MBS agent.

In addition, in the method, if the MBS service uses an IP multicast technology at the IP layer, the method further includes the following steps: and the access service network gateway or the MBS agent informs a multicast router to add the terminal into a corresponding multicast group.

The invention also provides a system for adding the terminal into the multicast broadcast service in the wireless network, which comprises the terminal and a network side, wherein the network side comprises a unit for providing the MBS service parameter for the terminal, and the service parameter comprises a first identifier for indicating the air interface connection and a second identifier for indicating the service content;

the terminal comprises a unit for acquiring the MBS service parameter from the network side and a unit for receiving the MBS service content indicated by the second identifier from the air interface connection indicated by the first identifier according to the acquired MBS service parameter;

when no terminal receives the MBS service currently in the access service network or MBS domain, the MBS server is used for directly updating the downlink play list of the MBS service stored in the MBS server; or, the access service network gateway or the MBS agent is configured to request the MBS server to register the MBS service, and trigger the MBS server to update the downlink playlist of the MBS service stored in the MBS server.

The terminal also includes a unit for sending a request message for joining MBS service to the network side, initiating MBS service joining process through the request message, and obtaining the MBS service parameter.

In addition, in the system, the network side further includes a unit for initiating an MBS service joining process to the terminal when the terminal accesses the network or requires to dynamically establish the MBS service, and providing the MBS service parameters for the terminal.

In addition, in the system, the network side further includes one or any combination of the following units:

means for evaluating whether the terminal has the capability of receiving the MBS service;

a unit for performing MBS service authentication on the terminal;

a unit for reserving network side resources for the MBS service;

a unit for establishing a bearer channel for the MBS service;

a unit for registering and/or updating downlink play list for the MBS service;

and the unit is used for generating a key for the MBS service.

And the unit is used for counting the number of users for the MBS service.

Further in the system, the device is one of the following or any combination thereof:

the system comprises a base station, an access service network gateway and/or an MBS agent, an MBS server and an authentication, authorization and accounting server.

The main difference between the technical scheme of the present invention and the prior art can be found by comparing, that the terminal obtains the MBS service parameters of the multicast broadcast service from the network side, wherein the MBS service parameters include a first identifier indicating an air interface connection and a second identifier indicating service contents, so that after receiving the MBS service parameters, the terminal can receive the MBS service contents indicated by the second identifier from the air interface connection indicated by the first identifier, and successfully join the MBS service.

The terminal can initiate the MBS service adding process by sending the request message for adding the MBS service, acquire the MBS service parameter and add the required MBS service; the network side can also initiate the MBS service joining process actively, send MBS service parameters to the terminal, invite the terminal to join the MBS service. Therefore, both the network side and the terminal side can actively operate according to actual requirements.

The terminal can send MBS service request message through DSA process, the message carries MBS domain identification, and informs the network side of MBS service that the terminal needs to join. Because the MBS domain may contain a plurality of MBS services at the same time, in order to clarify the identification, the message can also carry the MBS content identification so as to uniquely indicate the MBS service to be added, so that the terminal does not need to add other MBS services in the same MBS domain at the same time. In addition, under the condition that the MBS content identification is globally unique, the MBS content identification can be carried only.

Or, the terminal may send the MBS service request through an Internet Group Management Protocol ("IGMP") Protocol message, where the message carries an IP multicast address, and also can explicitly indicate the MBS service that the terminal needs to join on the network side.

On the network side, the MBS server can carry out MBS service authentication on the terminal through interacting with the AAA server, or the ASN gateway/MBS agent carries out MBS service authentication on the terminal according to the authentication result obtained in advance, and through the service authentication, the terminals which are added into the MBS service are ensured to subscribe the MBS service and obtain the authorization of the service, thereby preventing the illegal user from obtaining the related service and hindering the rights and interests of the legal user.

The network side or the terminal compares the maximum capability of the terminal with the minimum requirement required by the MBS service to determine whether the terminal has the capability of bearing the MBS service, and the terminal is prevented from receiving the service outside the capability range, thereby causing the waste of network resources and the extra loss of the terminal.

When the terminal joins the service, the base station or ASN gateway or MBS agent or MBS server need to make statistics again for the number of users using the MBS service, so that the MBS service can be carried by adopting a reasonable mode; when no terminal uses the MBS service before, the ASN gateway or the MBS agent or the MBS server needs to update the relevant service play list to ensure that the content of the play list is consistent with the actual content.

If the resources or bearer channels used for bearing the MBS service between the base station and the ASN gateway or between the ASN gateway and the MBS server are not pre-configured and corresponding resource reservation and bearer channel establishment are not performed, the base station or the ASN gateway or the MBS server can perform corresponding resource reservation and bearer channel establishment at any time before MBS service parameters are issued to the terminal according to the resource reservation information and bearer channel information actually required by the MBS service.

Drawings

Fig. 1 is a schematic diagram of a network structure of WiMAX in the prior art;

fig. 2 is a flowchart of a method for a terminal to join an MBS service in a wireless network according to a first 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 a fourth embodiment of the present invention;

fig. 4 is a flowchart of a method for a terminal to join an MBS service in a wireless network according to a fifth 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 a sixth embodiment of the present invention.

Detailed Description

In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention will be described in further detail with reference to the accompanying drawings.

In the invention, the terminal acquires the MBS service parameters of the multicast broadcast service from the network side, wherein the MBS service parameters comprise a first identifier for indicating air interface connection and a second identifier for indicating service content, so that the terminal can receive the MBS service content indicated by the second identifier from the air interface connection indicated by the first identifier after receiving the MBS service parameters and successfully join the MBS service.

The first embodiment of the present invention will be explained below. The first embodiment of the invention relates to the method that the terminal adds MBS business in the wireless network, in this embodiment, initiate MBS business to add the course by the terminal initiative, the terminal already confirms that his interested MBS business broadcasts in which MBS domains (MBS Zone) before adding MBS business, in the actual operation, the terminal can obtain the relevant information in the business announces the stage (serviceAnnounce); the terminal can also know which MBS zones the current BS belongs to in the DCD message broadcasted by the current BS, and if the MBS zones which the terminal interested in the MBS service is located in the broadcasted MBS zones, the terminal can initiate the MBS service adding process. As shown in particular in fig. 2.

In step 201, the terminal sends an MBS service join request message DSA-REQ to the BS, where the message carries an MBS Zone identity (MBS Zone ID) and/or MBS service authentication information where the MBS service to be joined is located.

Optionally, the message may also carry the current maximum MBS Service capability information supported by the terminal, and is used to inform the network side and make a decision whether the terminal can normally receive the Service according to the actual Quality of Service (QoS) requirement of the MBS Service.

In step 202, after receiving the MBS Service join request from the terminal, the BS first verifies the message authentication code HMAC/CMAC of the request message to verify whether the terminal is a valid user of the Network, and after verification succeeds, the BS sends an MBS Service join request message, such as RR-REQ, to an Access Service Network GateWay (Access Service Network GateWay, referred to as "ASN-GW"), where the message carries the terminal identifier MSID, MBS Zone ID, and/or MBS Service authentication information. There are also several cases in this step:

a) if the resources used for bearing the MBS service between the BS and the ASN-GW are not pre-configured and corresponding resource reservation is not carried out yet, and the BS currently holds the resource reservation information required by the MBS service, the MBS service adding request message sent by the BS to the ASN-GW also comprises a resource reservation application for requesting corresponding resource reservation on the BS and the ASN-GW for the MBS service;

b) if the bearing channel between BS and ASN-GW for transmitting the MBS service is not pre-configured and no corresponding bearing channel is created, if the BS holds the bearing channel information required by the MBS service, the MBS service joining request message sent by the BS to the ASN-GW also contains a bearing channel establishing request, and the bearing channel is applied to the BS and the ASN-GW for transmitting the MBS service. The realization of the bearer channel between the BS and the ASN-GW can be realized by using tunneling technologies such as Generic Routing Encapsulation (GRE), Virtual Local Area Network (VLAN), Multi Protocol Label Switching (MPLS), and the like, as referred to in the prior art.

c) For the condition that the request message contains the maximum MBS service capability information of the terminal, if the BS holds the actual capability requirement of the MBS service, namely the resource reservation information required by the MBS service, the BS directly judges whether the terminal can normally receive the MBS; if the BS does not have the resource reservation information of the MBS service, the MBS service adding request message sent by the BS to the ASN-GW also contains the maximum MBS service capability information of the terminal, and the ASN-GW is requested to further judge the maximum MBS service capability information.

In step 203, after receiving the MBS service join request from the BS, the ASN-GW sends an MBS service authentication request to an MBS Server (MBS Server) to request the MBS Server to verify whether the terminal has the right to receive the MBS service. The request may also carry MBS Zone ID, Network Access identity (NAI for short) of the terminal, and/or MBS service authentication information. There are also several cases in this step:

a) if the functional entity on the ASN-GW or ASN-GW, such as service flow Authorization (SFA for short) or MBS Proxy, already stores the Authorization information (service authentication result) of the MBS service, the ASN-GW does not need to send an MBS service authentication request to the MBS Server, and processes the MBS service join request of the corresponding terminal according to the maintained MBS Authorization information.

b) If the resources between the ASN-GW and the MBS Server for bearing the MBS service are not pre-configured and corresponding resource reservation is not performed, and the ASN-GW holds the resource reservation information required by the MBS service, the MBS service authentication request message sent by the ASN-GW to the MBS Server in the step also contains a resource reservation application for bearing the MBS service for applying corresponding resource reservation on the ASN-GW and the MBS Server.

c) If the bearer channel between ASN-GW and MBS Server for transmitting the MBS service is not pre-configured and no corresponding bearer channel is created, and the ASN-GW holds the bearer channel information required by the MBS service, the MBS service authentication request message sent by the ASN-GW to the MBS Server in this step also contains a bearer channel establishment request, and applies for establishing the bearer channel on the ASN-GW and MBS Server for transmitting the MBS service. The implementation of the bearer channel between the ASN-GW and the MBS Server may be a Tunneling technique such as GRE, Layer2 Tunneling Protocol (abbreviated as "L2 TP"), VLAN, MPLS, and IP Security (abbreviated as "IPSec"), or an IP Multicast technique such as IGMP and Multicast listener discovery (abbreviated as "MLD").

d) After ASN-GW receives the maximum MBS service capability information of the terminal, if ASN-GW holds the actual capability requirement of MBS service, namely the resource reservation information, ASN-GW judges 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; otherwise, if the ASN-GW does not currently have the resource reservation information of the MBS service, temporarily store the received maximum capability information of the terminal for subsequent further determination.

In step 204, after receiving the MBS service authentication request from the ASN-GW, the MBS Server retrieves the MBS service authorization information if it maintains the MBS service authorization information of the terminal, searches and confirms whether the terminal has the right to enjoy the MBS service, such as whether the terminal is in the subscription group of the MBS service, and whether the terminal is authorized, obtains an authorization key (MAK) of the MBS service, and the like; if the MBS Server does not maintain corresponding information and can not independently judge whether the terminal has the capability of enjoying the MBS service, the MBS Server also needs to request the AAA Server where the terminal account is located to carry out MBS service authentication.

If AAA Server receives the authentication request from MBS Server, then step 205 is entered, and judges whether the terminal has the ability to enjoy the MBS service according to the user subscription information and service strategy, and returns the service authentication result to MBS Server. Meanwhile, optionally, the AAA Server may also send the MBS service subscription information of the terminal to the MBS Server, so that the MBS Server can directly process the received MBS service authentication request of the terminal in a subsequent process.

In step 206, the MBS Server returns the MBS service authentication result to the ASN-GW. Meanwhile, optionally, the MBS Server may send the MBS service authentication information of the terminal to the ASN-GW or a certain functional entity in the ASN-GW, such as the SFA or the MBS Proxy, so that the ASN-GW can directly process the received MBS service join request of the terminal in the future process. There are also any of the following in this step:

a) optionally, if the broadcast range of the MBS service is dynamically established and no terminal receives the MBS service yet in the ASN or the MBS zone, the MBS server may directly update the downlink play list of the MBS service after the MBS service authentication is successful, that is, add the identifier or IP address of the ASN-GW or MBS Proxy in the downlink play list of the MBS service.

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

c) Optionally, if the ASN network entity, such as BS and ASN-GW, does not know the resource reservation information and/or bearer channel information required by the MBS service before, the MBS Server in this step may simultaneously issue the resource reservation information and/or bearer channel information required by the MBS service.

d) Corresponding to option b) of step 203, if the MBS Server receives the resource reservation application from the ASN-GW, it determines whether to accept the resource reservation application according to its own resource status and service policy, and returns the result of resource reservation to the ASN-GW in this step.

e) Corresponding to optional c) in step 203, if the MBS Server receives the bearer establishment request from the ASN-GW, the MBS Server determines whether to accept the request according to its own resource status and service policy, and returns the result of bearer establishment to the ASN-GW in this step.

Optionally, in step 207, if the broadcast range of the MBS service is dynamically established, and no terminal receives the MBS service yet in the ASN or MBS Zone, and in step 206, the MBS Server does not update the downlink play list, after the MBS service authentication is successful, the ASN-GW or MBS Proxy registers the MBS service to the MBS Server, and triggers the MBS Server to update the downlink play list of the MBS service stored therein, that is, the identifier or IP address of the ASN-GW or MBS Proxy is added to the downlink play list of the MBS service; in addition, if the bearing channel between the ASN-GW and the MBS Server is not established before, or the bearing channel information and/or the resource reservation information of the MBS service is not yet issued (i.e., the ASN-GW/MBS Proxy does not have the bearing channel information and/or the resource reservation information of the MBS service, and cannot request the MBS Server to establish a corresponding bearing channel and/or reserve a corresponding resource), the MBS Server issues the bearing channel information and/or the resource reservation information of the MBS service to the ASN-GW/MBS Proxy while responding to the registration request.

Optionally, in step 208, if the bearer channel and/or resource reservation for transmitting the MBS service between the BS and the ASN-GW is not pre-configured and corresponding resource reservation has not been performed and/or a corresponding bearer channel has not been created (i.e., in step 202, the BS does not send a bearer channel establishment request and/or a resource reservation request), the ASN-GW sends a resource reservation request and/or a bearer channel establishment request to the BS, and performs resource reservation and/or establishes a corresponding bearer channel for transmitting the MBS service between the BS and the ASN-GW.

Optionally, in step 209, if the bearer channel and/or resource reservation for transmitting the MBS service between the ASN-GW and the MBS Server is not pre-configured and has not performed corresponding resource reservation and/or created a corresponding bearer channel (i.e., in step 203, the ASN-GW has not sent the bearer channel setup request and/or the resource reservation request), in this step, the ASN-GW sends the resource reservation request and/or the bearer channel setup request to the MBS Server, and performs resource reservation and/or establishes a corresponding bearer channel for transmitting the MBS service between the ASN-GW and the MBS Server.

Step 208 and step 209 may be performed in any order, or in parallel.

Then step 210 is entered, after receiving the MBS service authentication result from the MBS server, the ASN-GW returns the result of the MBS service join request to the BS according to the authentication result. There are also any of the following in this step:

a) corresponding to the case a) in step 202, if the ASN-GW receives the resource reservation application from the BS, it determines whether to accept the resource reservation application according to the network resource status and the service policy. And if so, performing corresponding resource reservation. The result of resource reservation is returned to the BS in this step.

b) Corresponding to the case b) in step 202, if the ASN-GW receives the bearer path creation request of the BS, the ASN-GW determines whether to accept the request according to the network resource status and the service policy. And if so, establishing a corresponding bearer channel. In this step, the result of bearer establishment is returned to the BS.

c) Optionally, if in step 203d), the ASN-GW does not have the resource reservation information required by the MBS, and cannot determine the terminal capability, but in the following steps, if in step 206, MBS service resource reservation information delivered by the MBS Server is received, the ASN-GW determines whether the terminal can normally receive the MBS service according to the MBS service resource reservation information delivered by the MBS Server and the terminal maximum MBS service capability information stored in step 203 d). And informs the BS of the decision result in this step.

d) Optionally, if the broadcast range of the MBS service is dynamically established and no terminal receives the MBS service yet in the BS, the ASN-GW needs to update the downlink play list of the MBS service after the MBS service authentication is successful, that is, add the base station identifier BSID in the downlink play list of the MBS service;

e) optionally, after receiving the successful authentication message of the MBS service, the ASN-GW may directly update the user statistics of the MBS service, so that the ASN-GW or MBS Proxy correctly counts the number of users currently using the MBS service within the BS range, and further may obtain the number of users using the MBS service within the ASN or MBS Zone;

f) corresponding to c) in step 206, optionally, after the ASN-GW obtains the resource reservation information and the bearer channel information of the MBS service, it issues the information to the BS in this step.

Optionally, in step 211, after the BS receives the response of the MBS service adding request, if the broadcast range of the MBS service is dynamically established, and no terminal has yet received the MBS service in the BS, and the ASN-GW has not updated the downlink playlist, the BS registers the MBS service with the ASN-GW after the MBS service authentication is successful, and triggers the ASN-GW to update the downlink playlist of the MBS service stored in the ASN-GW, that is, adds a Base Station Identifier (BSID) in the downlink playlist of the MBS service; after the ASN-GW updates the downlink play list, if no bearer channel between ASN-GW and MBS Server is established currently, and ASN-GW does not initiate registration of the MBS service to MBS Server, ASN-GW may further register with MBS Server to update the MBS service downlink play list on MBS Server, that is, trigger MBS Server to add an identifier or IP address of ASN-GW or MBS Proxy in the MBS service downlink play list.

Optionally, in step 212, after the ASN-GW receives the registration request from the BS, if the bearer channel and/or resource reservation for transmitting the MBS service between the current ASN-GW and the MBS Server is not established, and in the previous step, the ASN-GW does not initiate registration with the MBS Server, the ASN-GW may register the MBS service with the MBS Server in this step, and the MBS Server issues corresponding resource reservation information and/or bearer channel information when responding to the registration request, and after receiving the registration request, the ASN-GW further issues the resource reservation information and/or bearer channel information of the MBS service to the BS when responding to the registration request from the BS.

Optionally, in step 213, after the BS receives the resource reservation information and/or the bearer channel information, if the bearer channel and/or the resource reservation for transmitting the MBS service between the BS and the ASN-GW is not pre-configured, and in the previous step, the BS has not sent the corresponding resource reservation request and/or the request for creating the bearer channel, and the ASN-GW has not actively issued the resource reservation request and/or the request for creating the bearer channel, in this step, the BS sends the resource reservation request and/or the request for creating the bearer channel to the ASN-GW, and performs resource reservation and/or creates the corresponding bearer channel for transmitting the MBS service between the BS and the ASN-GW.

Optionally, in step 214, after the ASN-GW performs corresponding resource reservation and/or establishes a corresponding bearer channel for the MBS service, if the bearer channel and/or resource reservation for transmitting the MBS service between the ASN-GW and the MBS Server is not pre-configured, and in the previous step, corresponding resource reservation and/or corresponding bearer channel creation have not been performed yet, in this step, the ASN-GW sends a resource reservation request and/or a bearer channel establishment request to the MBS Server, and performs resource reservation and/or corresponding bearer channel establishment for transmitting the MBS service between the ASN-GW and the MBS Server.

Optionally, in step 215, if the BS uses a link layer multicast mode to transmit the MBS service 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 a service Encryption Key (MTK) for the MBS service during air interface transmission.

The BS can request the ASN-GW to send the MGTEK key request message to the BS, if the ASN-GW does not generate the MGTEK for the MBS service currently, the MGTEK is generated for the MBS service firstly, and then the generated MGTEK is sent to the BS.

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

Then step 216 is entered, the BS sends an MBS service join response message DSA-RSP to the terminal, where the message carries the MBS Zone ID, air interface connection identifier CID or air interface multicast connection identifier MCID corresponding to the MBS service requested to be joined by the terminal, all MBS content identifiers carried on the CID or MCID, and multicast security association identifier GSA ID.

Then step 217 is entered, the terminal sends MBS service joining acknowledgement message DSA-ACk to the BS after receiving MBS service joining response message, to confirm the completion of the process.

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

Then step 218 is entered, after the terminal obtains the multicast security alliance identifier, the terminal initiates a Key Request message Key Request to the BS for requesting the multicast service Key MGTEK of the MBS service, where the Request message carries the GSA ID of the MBS service.

Step 219 is entered, after the BS receives the request, the BS sends the MGTEK generated or obtained before to the terminal, the terminal generates an MBS service encryption key MTK according to the pre-obtained MAK and MGTEK together, and receives the corresponding MBS service according to the multicast broadcast service parameters obtained from the network side. In this embodiment, the resource reservation information refers to description information of resources required for carrying the MBS service, such as classifier parameters and rules, QoS parameters and/or header compression parameters and rules. The bearer channel information refers to a resource description message required by a bearer channel carrying the MBS service, such as a bearer channel type, a bearer channel identifier, and/or a bearer channel protocol type. The maximum MBS capability information of the terminal refers to the maximum resource description information, such as bandwidth and packet loss rate, that the terminal currently has and can receive the MBS service. Typically the device capabilities of the terminal or the sum of resources currently unoccupied. The MBS service refers to one Service Flow (SF) defined by IEEE802.16d/e.

It should be noted that, in this embodiment, if the terminal requests to join the MBS multicast service, the terminal needs to subscribe to the MBS service and obtain an 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 above process, and the request messages in steps 201 to 203 may not carry the authentication information of the MBS, or the authentication information is only used to notify each node on the network side that the terminal joins the MBS service. In this case, the service authentication in step 204 may be omitted, and it is not necessary to issue any service authentication result or service authorization information in the subsequent steps.

The second embodiment of the present invention relates to a method for a terminal to join an MBS service in a wireless network, which is substantially the same as the first embodiment, but the difference is that in the first embodiment, the terminal carries an MBS Zone ID in a request message for joining the MBS service to identify an MBS service that needs to be joined, however, since there may be a plurality of MBS services in one MBS Zone, in the present embodiment, the terminal needs to carry an MBS Content ID of the MBS service in addition to the MBS Zone ID in the request message. Therefore, in this embodiment, the air interface standard ieee802.16e needs to be modified, so that the DSA-REQ message may carry the MBS Content ID.

The third embodiment of the invention relates to a method for adding MBS service to a terminal in a wireless network, which is the same as the second embodiment, and the difference is that in the second embodiment, the terminal needs to carry MBS Zone ID and specific MBS Content ID of MBS service requested to be added in the request message for adding MBS service, but the embodiment is improved on the basis of the second embodiment, in the embodiment, the MBS Content ID of MBS service is globally unique, in the service adding request message, only the specified MBS Content ID needs to be carried, and the MBS Zone on which the service is broadcasted does not need to be concerned. In this embodiment, the air interface standard ieee802.16e also needs to be modified, and the DSA-REQ is required to carry the MBS Content ID.

In the fourth embodiment of the invention, a 3-layer multicast technology is used for assisting in completing the process of adding the terminal into the MBS service, so that the process of adding the terminal into a specified MBS service is completed on the basis of not changing the existing air interface protocol (IEEE802.16d/e).

In this embodiment, the terminal has already obtained the IP multicast address list related to the MBS service, the MBS Content ID list carried by the MBS service, the corresponding relationship between the IP multicast address and the MBS Content ID, and/or in which MBS zones the MBS service is broadcasted before joining the MBS service, and in a specific application, the terminal can obtain the above information, for example, at the service notification stage or through other approaches. Before initiating the MBS service joining process, if the terminal knows the MBS Zone in which the service is broadcasted, the terminal can also know which MBS zones the current BS belongs to by detecting the DCD message broadcasted by the current BS so as to determine whether the current terminal is in the MBS Zone in which the MBS service which the current terminal is interested is, if not, the joining process is not initiated. As shown in particular in figure 3.

In step 301, the terminal sends an MBS service Join request IGMP Join to the Anchor ASN-GW (Anchor ASN-GW), where the message carries the IP multicast address and/or service authentication information to be joined. The message may be carried on an Initial Service Flow (ISF) channel of the terminal.

In step 302, after receiving the MBS service join request from the terminal, the anchor ASN-GW sends the MBS service join request to the MBSProxy, where the request carries the terminal identifier MSID and the IP multicast group address and/or service authentication information to be joined by the terminal.

In step 303, the MBS Proxy sends an MBS service authentication request to the MBS Server after receiving the MBS service join request, for requesting to verify whether the terminal has the right to receive the MBS service. The request may also carry a network access identifier NAI, an IP multicast group address, and/or an MBSContent ID of the terminal. There are also several cases in this step:

a) if a certain functional entity, such as SFA, on the ASN-GW where the MBS Proxy or MBS Proxy is located already stores the authorization information of the MBS service, i.e. the MBS Proxy can already perform MBS service authentication processing, the MBS Proxy does not need to send an MBS service authentication request to the MBS Server, and can process the MBS service adding request of the corresponding terminal according to the maintained MBS authorization information.

b) If the carrying channel between ASN-GW and MBS Server for transmitting the MBS service is not pre-configured and the corresponding carrying channel is not established, the MBS service authentication request message sent by MBS Proxy to MBS Server also contains the carrying channel establishing request, and applies for establishing the carrying channel on ASN-GW and MBS Server for transmitting the MBS service. The realization of the bearing channel between the ASN-GW and the MBS Server can be GRE, L2TP, VLAN, MPLS, IPSec and other tunnel technologies, and can also be IP multicast technologies, such as IGMP, MLD and the like.

In step 304, after receiving the MBS service authentication request, if the MBS Server itself maintains the MBS service authorization information of the terminal, retrieving the MBS service authorization information to search and confirm whether the terminal has the capability of enjoying the MBS service; if the MBS Server does not maintain the corresponding authorization information and can not judge whether the terminal has the capability of enjoying the MBS service, the MBS Server also needs to request the AAA Server where the terminal account is located to carry out MBS service authentication.

In step 305, the AAA determines whether the terminal has the capability of enjoying the MBS service according to the user subscription information and the service policy, and informs the MBS Server of the service authentication result. At this time, optionally, the AAA may simultaneously issue the MBS service authorization information of the terminal to the MBS Server, so that the MBS Server can directly process the received MBS service authentication request of the terminal in a subsequent process.

In step 306, the MBS Server returns the MBS service authentication result to the MBS Proxy. Meanwhile, optionally, the MBS Server may send the MBS service authorization information of the terminal to a certain functional entity, such as an SFA, in the ASN-GW where the MBS Proxy is located, so that the MBS Proxy can directly process the received MBS service join request of the terminal in the subsequent process. In addition, there may be several cases in this step:

a) optionally, if the broadcast range of the MBS service is dynamically established and no terminal receives the MBS service yet in the ASN or MBS Zone, the MBS server may directly update the downlink play list of the MBS service after the MBS service authentication is successful, that is, add the identifier or IP address of the ASN-GW or MBS Proxy in the downlink play list of the MBS service.

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

c) Optionally, if the ASN-GW and/or MBS portal does not know the resource reservation information and/or bearer channel information required by the MBS service before, the MBS Server in this step may issue the resource reservation information and/or bearer channel information required by the MBS service at the same time.

d) Corresponding to step 303b), the MBS Server determines whether to accept the request for establishing the bearer channel according to its own resource status and service policy, and returns the result of establishing the bearer channel to the MBS Proxy in this step.

After receiving the MBS service authentication result from the MBS server, the MBS Proxy then proceeds to step 307 or step 308, and there is no precedence relationship between step 307 and step 308.

In step 307, the MBS Proxy returns the result of the MBS service join request to the Anchor ASN-GW according to the authentication result.

In step 308, the MBS Proxy sends an MBS service join request, such as RR-REQ, to the BS according to the authentication result. There may also be several situations in this step:

a) if the resources for carrying the MBS service between the BS and the ASN-GW are not pre-configured and corresponding resource reservation has not been performed (i.e., the BS has not sent a resource reservation application in the previous step), the response message sent by the MBS Proxy to the BS for the terminal to join the MBS service also includes a resource reservation application, and applies for corresponding bearer resources on the BS and the ASN-GW for carrying the MBS service.

b) If the bearer channel between the BS and the ASN-GW for transmitting the MBS service is not pre-configured and the corresponding bearer channel has not been created (i.e., the BS has not sent a bearer channel creation request in the previous step), the response message sent by the MBS Proxy to the BS for the terminal to join the MBS service also includes a bearer channel establishment request, and applies for establishing the bearer channel on the BS and the ASN-GW for transmitting the MBS service. The implementation of the bearer channel between the BS and the ASN-GW may be a tunneling technique such as GRE, VLAN, MPLS, and the like.

c) Optionally, if the broadcast range of the MBS service is dynamically established and no terminal receives the MBS service yet in the BS, the MBS Proxy may directly update the downlink play list of the MBS service after the MBS service authentication is successful, that is, add the base station identifier BSID in the downlink play list of the MBS service.

d) Optionally, after the MBS service authentication is successful, the MBS Proxy updates the user statistics of the MBS service, so that the ASN-GW or the MBS Proxy counts the number of users using the MBS service under the BS, and further knows the number of users using the MBS service in the ASN or MBS Zone.

In step 309, after receiving the MBS service join request response, if the response is a successful response, the BS sends an MBS service join request message DSA-REQ to the terminal, where the message carries one or more of an MBS Zone ID, an air interface connection identifier CID, an air interface multicast connection identifier MCID, all MBS content identifiers MBS ContentID carried on the CID or MCID, a multicast security association identifier GSA ID, a unicast security association, and QoS parameters of the MBS service to be joined.

Optionally, in step 310, if the BS determines to use a link layer multicast mode to transmit the MBS service 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 a service encryption key MTK when the MBS service is transmitted over the air interface.

The BS can request the ASN-GW to send the MGTEK key request message to the BS, if the ASN-GW does not generate the MGTEK for the MBS service currently, the MGTEK is generated for the MBS service firstly, and then the generated MGTEK is sent to the BS.

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

There is no fixed order between this step and step 309.

Then step 311 is entered, after the terminal receives the DSA-REQ message from the BS, it 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 can bear, if so, the corresponding MBS service context is saved. The terminal responds to MBS service adding response message DSA-RSP to BS, the message carries the result of adding MBS service.

Optionally, in step 312, if the broadcast range of the MBS service is dynamically established and no terminal has received the MBS service in the BS before, that is, the BS has not registered the MBS service with the MBS Proxy, the BS initiates service registration with the MBS Proxy to update the downlink play list of the MBS service in the ASN-GW, that is, add the base station identifier BSID in the downlink play list of the MBS service.

Also optionally, in step 313, after the MBS Proxy updates the downlink playlist of the MBS service in the ASN-GW, if no terminal has received the MBS service in the ASN or MBS Zone before, that is, the MBS Proxy does not register the MBS service with the MBS Server, the MBS Proxy registers with the MBS Server in this step to update the downlink playlist of the MBS service in the MBS Server, that is, the identifier or IP address of the ASN-GW or MBS Proxy is added to the downlink playlist of the MBS service in the MBS Server.

Optionally, in this step, if the bearer channel and/or resource reservation for transmitting the MBS service between the ASN-GW/MBS Proxy and the MBS Server is not established, and corresponding resource reservation information and/or bearer channel information has not been issued before. The MBS Server issues the resource reservation information and/or bearer establishment information while responding to the registration request of the ASN-GW. After receiving the request, ASN-GW sends down the resource reservation information and/or the bearing channel information of MBS service to BS when responding to the registration request of BS.

Optionally, in step 314, if the bearer channel and/or resource reservation for transmitting the MBS service between the BS and the ASN-GW is not pre-configured, and in the previous step, the BS does not perform a corresponding resource reservation request and/or create a corresponding bearer channel request, and the ASN-GW or the MBSProxy does not actively initiate a resource reservation request and/or create a corresponding bearer channel request, in this step, the BS sends a resource reservation request and/or a bearer channel establishment request to the ASN-GW, and performs resource reservation and/or establishes a corresponding bearer channel for transmitting the MBS service between the BS and the ASN-GW.

Optionally, in step 315, after receiving the resource reservation request and/or the bearer channel establishment request from the BS, the ASN-GW or MBS Proxy may determine whether to grant corresponding resource reservation and/or establish a corresponding bearer channel according to the network resource condition. In addition, if the bearer channel and/or resource reservation for transmitting the MBS service between the ASN-GW and the MBS Server is not pre-configured, and in the previous step, a corresponding resource reservation request and/or a request for creating a corresponding bearer channel is not sent to the MBS Server, the MBS Proxy sends a resource reservation request and/or a bearer channel establishment request to the MBS Server, and performs resource reservation and/or establishes a corresponding bearer channel for transmitting the MBS service between the ASN-GW and the MBS Server.

In step 316, the BS sends the MBS service join request response result of the terminal to the MBSProxy or Serving ASN-GW. There may also be several situations in this step:

a) if the response message sent by the MBS Proxy to the BS for the terminal to join the MBS service also includes the resource reservation application in step 308a), the BS determines whether to accept the resource reservation application according to the air interface resource status and the admission control policy in this step. And if so, performing corresponding resource reservation. In this step, the result of resource reservation is returned to the MBS Proxy.

b) If the response message sent by the MBS Proxy to the BS for the terminal to join the MBS service further includes a bearer establishment request in step 308b), the BS determines whether to accept the bearer establishment request according to the air interface resource status and the admission control policy in this step. And if so, establishing a corresponding bearer channel. In this step, the result of establishing the bearer channel is returned to the MBS Proxy.

In step 317, the BS sends an MBS service join acknowledgement message DSA-ACK to the terminal after receiving the MBS service join response DSA-RSP message, to confirm that the procedure is completed.

In step 318, after obtaining the multicast security association identifier, the terminal initiates a Key Request message Key Request to the BS, which is used to Request the multicast service Key MGTEK of the MBS service, where the Request message carries the GSA ID of the MBS service.

In step 319, after receiving the request, the BS sends the MGTEK generated or obtained before to the terminal, and the terminal generates an MBS service encryption key MTK according to the pre-obtained MAK and MGTEK together, and receives the corresponding MBS service according to the multicast broadcast service parameters obtained from the network side.

It should be noted that, in this embodiment, if the terminal requests to join the MBS multicast service, the terminal needs to subscribe to the MBS service and obtain an 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 above process, and the request message in steps 301 to 303 may not carry the authentication information of the MBS, or the authentication information is only used to notify each node on the network side that the terminal joins the MBS service. And the service authentication in step 304 can be omitted, and any service authentication result or service authorization information does not need to be issued in the subsequent steps.

The fifth embodiment of the present invention relates to a method for a terminal to join an MBS service in a wireless network, which is substantially the same as the fourth embodiment, but the difference is that in the fourth embodiment, the terminal already acquires the corresponding relationship between the IP multicast address and the MBS Content ID before initiating the MBS service joining process, whereas in the present embodiment, the terminal does not acquire the corresponding relationship between the IP multicast address and the MBS Content ID before joining the MBS service, and the network side notifies the terminal of the corresponding relationship in the MBS service joining process of the terminal.

Specifically, as shown in fig. 4, steps 401 to 417 are similar to steps 301 to 317, and are not repeated herein.

In step 418, after receiving the MBS service join result sent by the BS, the MBS Proxy/Serving ASN-GW sends to the terminal an MBS Content ID list corresponding to the IP multicast address to which it joins, where the message may also carry one or more of an MBS Zone ID, an air interface connection identifier CID or an air interface multicast connection identifier MCID corresponding to the MBS service to be joined, all MBS Content identifiers MBS Content ID carried on the CID or MCID, a multicast security association identifier GSA ID, or a unicast security association.

There is no fixed precedence relationship between this step and step 417.

Steps 419 and 420 are similar to steps 318 and 319.

In the sixth embodiment of the present invention, the MBS service joining process initiated by the network side actively occurs during the process of establishing the preset stream after the terminal accesses the network, or during the time when the network side entity requires to dynamically establish the MBS service. For the multicast service, before the network side requests the terminal to join the MBS service, the terminal needs to subscribe the MBS service and obtain the authorization key MAK of the MBS service, where the subscription message may be included in the subscription message of the user. As shown in particular in fig. 5.

In this embodiment, there are several possibilities that the network side entity sends the MBS service creation request:

if the subscription information of the user has been sent to the access network entity Anchor ASN-GW at the initial access stage of the terminal, in step 501, a function entity, such as SFA, in the Anchor ASN-GW or the Anchor ASN-GW may initiate an MBS service creation request to the MBS Proxy, where the request also needs to carry the terminal identifier MSID.

Or in step 501', the MBS Server sends an MBS service creation request to the MBS Proxy, where the message carries the NAI or MSID. The following options may also be included in this step:

a) optionally, if the broadcast range of the MBS service is dynamically established and no terminal receives the MBS service yet in the ASN or MBS zone, the MBS Server may directly update the downlink play list of the MBS service, that is, add the identifier or IP address of the ASN-GW or MBS Proxy in the downlink play list of the MBS service.

b) Optionally, the MBS Server may update the user statistics of the MBS service, so that the MBSServer counts the number of actual users currently using the MBS service.

In step 502, if the MBS Proxy already obtains the user subscription information in the terminal network access authentication stage, the MBS Proxy may directly trigger the MBS service creation request, or after receiving the MBS service creation request from the MBS server or Anchor ASN-GW, the MBS Proxy further initiates the MBS service creation request to the BS. If the MBS service transmission uses the IP Multicast technology at the IP layer, the MBS Proxy is also responsible for notifying a corresponding Multicast router (Multicast router, abbreviated as "MR") and adding the terminal to a corresponding Multicast group.

In addition, the following options can be included in the present step:

a) optionally, if the broadcast range of the MBS service is dynamically established and no terminal has received the MBS service before the BS, the MBS Proxy may directly update the downlink play list of the MBS service, that is, add the base station identifier BSID in the downlink play list of the MBS service.

b) Optionally, the MBS Proxy updates the user statistics of the MBS service, so that the ASN-GW or the MBS Proxy counts the number of users using the MBS service in the BS, and further knows the number of users using the MBS service in the ASN network or the MBS Zone.

c) If the resources used for bearing the MBS service between the ASN-GW and the BS are not pre-configured and corresponding resource reservation is not performed, the MBS service creation request message sent by the MBS Proxy to the BS can also contain a resource reservation application for bearing the MBS service to apply for corresponding bearing resources on the BS and the ASN-GW.

d) If the bearer channel between BS and ASN-GW for transmitting the MBS service is not pre-configured and no corresponding bearer channel is created, the request message sent by MBS Proxy to BS for adding MBS service by terminal also includes a bearer channel establishment request, and applies for establishing bearer channel on BS and ASN-GW for transmitting the MBS service. The implementation of the bearer channel between the BS and the ASN-GW may be a tunneling technique such as GRE, VLAN, MPLS, and the like.

Optionally, in step 503, if the BS uses a link layer multicast mode to transmit the MBS service and the MBS service is not a broadcast service, the BS requests an MBS service key MGTEK to the MBS Proxy, where the key is used to generate a service encryption key MTK when the MBS service is transmitted over the air interface.

The BS can request the ASN-GW to send the MGTEK key request message to the BS, if the ASN-GW does not generate the MGTEK for the MBS service currently, the MGTEK is generated for the MBS service firstly, and then the generated MGTEK is sent to the BS.

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

In step 504, the BS sends an MBS service join request message DSA-REQ to the terminal, where the message carries one or more of an MBS Zone ID, an air interface connection identifier CID or an air interface multicast connection identifier MCID corresponding to the MBS service to be joined, all MBS content identifiers MBSContent ID carried on the CID or MCID, a multicast security association identifier GSA ID or a unicast security association, and QoS parameters of the MBS service.

In step 505, after receiving the DSA-REQ message, 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 can bear, and if so, saves the context of the corresponding MBS service. The terminal returns a MBS service joining response message DSA-RSP to the BS, and the message carries the result of joining the MBS service.

Optionally, in step 506, if the broadcast range of the MBS service is dynamically established and no terminal has received the MBS service before the BS, that is, the BS has not registered the MBS service with the MBS Proxy, the BS initiates registration with the ASN-GW to update the downlink playlist of the MBS service, that is, adds the base station identifier BSID in the downlink playlist of the MBS service in the ASN-GW.

Also optionally, in step 507, after the MBS Proxy updates the downlink play list of the MBS service in the ASN-GW, if no terminal has received the MBS service in the ASN or MBS Zone before, that is, the MBS Proxy does not register the MBS service with the MBS Server, the MBS Proxy registers with the MBS Server in this step to update the downlink play list of the MBS service in the MBS Server, that is, the identifier or IP address of the ASN-GW or MBS Proxy is added to the downlink play list of the MBS service in the MBS Server.

Optionally, in this step, if the bearer channel and/or resource reservation for transmitting the MBS service between the ASN-GW/MBS Proxy and the MBS Server is not established, and corresponding resource reservation information and/or bearer channel information has not been issued before. The MBS Server issues the resource reservation information and/or bearer establishment information while responding to the registration request of the ASN-GW. After receiving the request, ASN-GW sends down the resource reservation information and/or the bearing channel information of MBS service to BS when responding to the registration request of BS.

Optionally, in step 508, if the bearer channel and/or resource reservation for transmitting the MBS service between the BS and the ASN-GW is not pre-configured, and corresponding resource reservation has not been performed and/or a corresponding bearer channel has not been created, and in step 502, the MBS Proxy sends the MBS service creation request message to the BS without the resource reservation application and/or the bearer channel establishment request, in this step, the BS sends the resource reservation request and/or the bearer channel establishment request to the ASN-GW or the MBS Proxy, and performs resource reservation and/or establishes a corresponding bearer channel for transmitting the MBS service between the BS and the ASN-GW.

Optionally, in step 509, after the ASN-GW or MBS Proxy receives the resource reservation request and/or bearer channel establishment request from the BS, it may determine whether to grant corresponding resource reservation and/or establish a corresponding bearer channel according to the air interface resource condition. And if the bearing channel and/or resource reservation used for transmitting the MBS service between the ASN-GW and the MBS Server is not pre-configured and corresponding resource reservation and/or corresponding bearing channel creation are not performed, the ASN-GW or the MBS Proxy sends a resource reservation request and/or a bearing channel establishment request to the MBS Server, and performs resource reservation and/or corresponding bearing channel establishment for transmitting the MBS service between the ASN-GW and the MBS Server.

In step 510, after receiving the DSA-RSP message, the BS returns the MBS service join request result to the MBS Proxy, specifically, through the response message RR-RSP. In addition, there may be several cases in this step:

a) corresponding to step 502a), if the MBS service creation request message sent by the MBS Proxy to the BS does not contain the resource reservation application, in this step, the BS determines whether to accept the resource reservation application according to the air interface resource status and the admission control policy. And if so, performing corresponding resource reservation. And in this step, the ASN-GW resource reservation result is informed.

b) Corresponding to step 502b), if the MBS service creation request message sent by the MBS Proxy to the BS does not include a bearer establishment request, in this step, the BS determines whether to accept the requested bearer establishment according to the air interface resource status and the admission control policy. And if so, establishing a corresponding bearer channel. And in this step, the ASN-GW is informed of the result of the bearer channel establishment.

And after the MBS Proxy acquires the MBS service creation result, notifying an initiator of the MBS service creation request. If the initiator of the MBS service creation request is Anchor ASN-GW, that is, corresponding to step 501 and step 501', step 511 is entered, and the MBS Proxy returns the service creation result to the Anchor ASN-GW; if the initiator of the MBS service creation request is the MBS Server, i.e. corresponding to step 501 ', then step 511' is entered, and the MBS Proxy returns the service creation result to the MBS Server; if the initiator of the MBS service creation request is the MBS Proxy, this step may be omitted.

In step 512, the BS sends an MBS service join acknowledgement message DSA-ACK to the terminal after receiving the MBS service join response message DSA-RSP, for acknowledging that the service join process is completed.

In step 513, after obtaining the multicast security association identifier, the terminal initiates a Key Request message Key Request to the BS, which is used to Request the multicast service Key MGTEK of the MBS service, where the Request message carries the GSA ID of the MBS service.

In step 514, after receiving the request, the BS sends the MGTEK generated or obtained before to the terminal, and the terminal generates an MBS service encryption key MTK according to the pre-obtained MAK and MGTEK together, and receives the corresponding MBS service according to the multicast broadcast service parameters obtained from the network side.

It is worth mentioning that in the above embodiments, the entities may exist independently or in a functional entity, and when the entities exist in the same physical entity, the internal primitives are used for the interaction between them. For example, the ASN-GW and the BS can be the same physical entity, the Anchor ASN-GW and the servingASN-GW can be the same physical entity, the MBS Proxy and the ASN-GW can be the same physical entity, and the like.

The MBS Proxy entity is a functional entity which processes MBS service signaling and/or service for the terminal in the ASN network or MBS Zone. In the above embodiments, the functional entity may be located in the Anchor ASN-GW, or located in the Serving ASN-GW, or independently located in the MBS Zone. When the MBS Proxy is positioned in the Anchor ASN-GW, the message interaction between the MBS Proxy and the Anchor ASN-GW is realized through the internal primitive.

The seventh embodiment of the invention relates to a system for adding a multicast broadcast service to a terminal in a wireless network, which comprises the terminal and a network side, wherein the network side comprises a unit for initiating an MBS service adding process to the terminal when the terminal accesses the network or requires to dynamically establish the MBS service, and providing MBS service parameters for the terminal. The service parameter comprises a first identifier for indicating air interface connection and a second identifier for indicating service content; the terminal also comprises a unit for acquiring MBS service parameters from the network side; a unit for receiving MBS service content indicated by the second identifier from the air interface connection indicated by the first identifier according to the acquired MBS service parameter; and/or a unit for sending a request message for joining the MBS service to the network side, initiating an MBS service joining process through the request message, and acquiring MBS service parameters.

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

a unit for judging whether the terminal has the ability to receive MBS service;

a unit for carrying out MBS service authentication on the terminal;

a unit for reserving network side resources for MBS service;

a unit for establishing a bearer channel for MBS service;

a unit for registering and/or updating downlink play list for MBS service;

and the unit is used for generating a key for the MBS service.

The above units may be one of the following or any combination thereof: base station, ASN-GW and/or MBS agent, MBS server, AAA server.

While the invention has been shown and described with reference to certain preferred embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention.

Claims (27)

1. A method for adding multicast broadcast service to a terminal in a wireless network is characterized in that the terminal acquires MBS service parameters of the multicast broadcast service from a network side, wherein the MBS service parameters comprise a first identifier for indicating air interface connection and a second identifier for indicating 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;

wherein, if no terminal currently receives the MBS service in the access service network or MBS domain, the method also comprises the following steps:

the MBS server directly updates the downlink play list of the MBS service stored by the MBS server; or,

the access service network gateway or MBS agent requests the MBS server to register the MBS service, and triggers the MBS server to update the stored downlink play list of the MBS service.

2. The method of claim 1, wherein the terminal obtains the MBS parameters from the network side by sending a request message for joining MBS services or by an MBS service joining procedure initiated by the network side.

3. The method of claim 2, wherein the terminal sends the request message for joining MBS service through a dynamic service stream joining process, and the request message includes MBS content identification and/or MBS domain identification.

4. The method of claim 2, wherein the joining process of the MBS service is assisted by a layer 3 multicast technology, and the request message for joining the MBS service sent by the terminal includes an IP multicast address list and/or an MBS content identifier of the MBS service.

5. The method for adding multicast broadcast service to terminal in wireless network according to claim 2, wherein the network side sends the request for adding MBS service to the terminal when the terminal accesses network or requires to dynamically establish MBS service, and initiates the MBS service adding process;

the request for joining the MBS service sent to the terminal comprises an air interface connection identifier of the MBS service, at least one MBS content identifier and/or a multicast security alliance identifier.

6. Method for a terminal to join a multicast broadcast service in a wireless network according to claim 2,

before the network side initiates an MBS service joining process to the terminal or the terminal sends the request message for joining the MBS service, the terminal subscribes the MBS service and acquires an authorization key of the MBS service.

7. Method for a terminal to join a multicast broadcast service in a wireless network according to claim 2,

before the network side initiates an MBS service joining process to the terminal or sends the MBS service parameters to the terminal, the network side authenticates the MBS service to the terminal according to the MBS service subscription information of the terminal and/or the MBS service authentication result of the terminal, and determines that the terminal is authorized to receive the MBS service.

8. The method of claim 7, wherein the network element of the network side initiating the MBS service joining procedure is one of the following: the anchor is accessed into a service network gateway or a functional entity, an MBS server and an MBS agent in the gateway;

the network element for the network side to perform MBS service authentication on the terminal is one of the following elements: the anchor access service network gateway or the functional entity in the gateway, MBS server, MBS agent, authentication, authorization and accounting server.

9. The method of claim 8, wherein the anchor access service network gateway or any network element of the gateway, MBS server, MBS proxy, authentication, authorization, and accounting server completes the MBS service authentication of the terminal, and then issues the authentication result and/or the MBS service subscription information to one or any combination of the other network elements.

10. The method of adding multicast broadcast service to terminal in wireless network according to claim 3 or 4, characterized in that the request message for adding MBS service sent by the terminal also contains MBS service authentication information, the network side authenticates MBS service to the terminal according to MBS service subscription information, MBS service authentication information and/or MBS service authentication result of the terminal, and determines whether the terminal has right to receive the MBS service.

11. The method according to claim 3 or 4, wherein the request for joining MBS service further includes information indicating the maximum MBS service capability of the terminal, the method further includes:

the network side identifies whether the terminal can receive the MBS service according to the maximum MBS service capability of the terminal and/or the service resource reservation information of the MBS stored by the network side.

12. The method for adding multicast broadcast service to a terminal in a wireless network according to any one of claims 1 to 9, wherein the MBS service parameters further include MBS service quality parameters, and after receiving the MBS service parameters, the terminal determines whether the terminal can receive the MBS service according to the maximum MBS service capability of the terminal and the MBS service quality parameters.

13. Method according to any of claims 1 to 9, wherein if the transmission range of the MBS service is dynamically established and no terminal currently receives the MBS service in the base station, the method further comprises the following steps:

the access service network gateway directly updates the downlink play list of the MBS service stored by the access service network gateway; or,

and the base station requests the access service network gateway to register the MBS service and triggers the access service network gateway to update the downlink play list of the MBS service stored by the access service network gateway.

14. The method for a terminal to join a multicast broadcast service in a wireless network according to any of claims 1 to 9, wherein after the terminal joins the MBS service, the method further comprises the following steps:

and the MBS server, the access service network gateway/MBS agent and the base station respectively update the user statistics of the MBS service.

15. The method according to any of claims 1 to 9, wherein if the resources and/or bearer channels for carrying the MBS service between the base station and the access serving network gateway are not pre-configured, the method further comprises the following steps:

if the resource reservation between the base station and the access service network gateway and/or the establishment of a corresponding bearing channel are not carried out when the terminal requests to join the MBS service, and the base station holds the resource reservation information and/or the bearing channel information required by the MBS service, the base station requests the access service network gateway or the MBS agent to carry out the resource reservation and/or the establishment of the bearing channel according to the resource reservation information and/or the bearing channel information required by the MBS service;

and the access service network gateway or the MBS agent determines whether to accept the resource reservation request and/or the bearer channel establishment request according to the network resource condition and the service strategy.

16. The method according to any of claims 1 to 9, further comprising the steps of:

if the terminal has not performed corresponding resource reservation and/or established corresponding bearer channel after the terminal passes the MBS service authentication,

the access service network gateway or the MBS agent performs resource reservation and/or bearer channel establishment for the transmission of the MBS service between the base station and the access service network by sending a resource reservation request and/or a bearer channel establishment request to the base station; or, the MBS server sends down the resource reservation information and/or the bearer channel information required by the MBS service, and the base station requests a service network gateway or an MBS agent to reserve resources and/or establish a bearer channel according to the resource reservation information and/or the bearer channel information;

and the base station or the access service network gateway or the MBS agent determines whether to accept the corresponding resource reservation request and/or the bearer channel establishment request according to the network resource condition and the service strategy.

17. The method according to any of claims 1 to 9, wherein if the resources for carrying the MBS service between the access service network gateway and the MBS server are not pre-configured, the method further comprises the following steps:

if the terminal does not perform corresponding resource reservation and/or establish corresponding bearing channel when requesting to join the MBS service, and the access service network gateway/MBS agent holds the resource reservation information and/or bearing channel information required by the MBS service, the access service network gateway or MBS agent requests the MBS server to perform resource reservation and/or establish the bearing channel according to the resource reservation information and/or bearing channel information required by the MBS service;

and the MBS server determines whether to accept the resource reservation request and/or the bearer channel establishment request according to the network resource condition and the service strategy.

18. The method according to any of claims 1 to 9, further comprising the steps of:

if the terminal has not performed corresponding resource reservation and/or established corresponding bearer channel after the terminal passes the MBS service authentication,

the MBS server performs corresponding resource reservation and/or establishes a corresponding bearing channel for the transmission of the MBS service between the access service network and the MBS server by sending a resource reservation request and/or a bearing channel establishment request to the access service network gateway or the MBS agent;

or, the MBS server sends down the resource reservation information and/or the bearer channel information required by the MBS service, and the access service network gateway or the MBS agent requests the MBS server to perform corresponding resource reservation and/or establish a corresponding bearer channel according to the resource reservation information and/or the bearer channel information;

and the access service network gateway or the MBS agent or the MBS server determines whether to accept the corresponding resource reservation request and/or the bearer channel establishment request according to the network resource condition and the service strategy.

19. The method according to any of claims 1 to 9, wherein the first identifier is an air interface unicast connection identifier, or an air interface multicast connection identifier, or an air interface broadcast identifier;

the second identification is MBS content identification or IP multicast address of the multicast group;

the MBS service parameter further includes one or any combination of the following:

MBS domain identification, MBS content identification, multicast security alliance identification, unicast security alliance identification, MBS service quality parameter and MBS service stream identification corresponding to the MBS service.

20. The method of claim 19 wherein the terminal acquires the MBS service key from the base station after acquiring the multicast security association identifier, generates an MBS service encryption key using the MBS service key and an MBS authorization key issued by the network side to the terminal, and receives the MBS service content through the MBS service encryption key.

21. The method of claim 20, wherein the MBS service key is generated by the base station or obtained by the base station from the access service gateway or the MBS agent.

22. Method according to any of claims 1 to 9, wherein if said MBS service uses IP multicast technology at IP layer, it further comprises the following steps: and the access service network gateway or the MBS agent informs a multicast router to add the terminal into a corresponding multicast group.

23. A system for adding multicast broadcast service to a terminal in a wireless network comprises the terminal and a network side, and is characterized in that the network side comprises a unit for providing MBS service parameters for the terminal, and the service parameters comprise a first identifier for indicating air interface connection and a second identifier for indicating service content;

the terminal comprises a unit for acquiring the MBS service parameter from the network side and a unit for receiving the MBS service content indicated by the second identifier from the air interface connection indicated by the first identifier according to the acquired MBS service parameter;

when no terminal receives the MBS service currently in the access service network or MBS domain, the MBS server is used for directly updating the downlink play list of the MBS service stored in the MBS server; or, the access service network gateway or the MBS agent is configured to request the MBS server to register the MBS service, and trigger the MBS server to update the downlink playlist of the MBS service stored in the MBS server.

24. The system of claim 23, wherein the terminal further comprises a unit for sending a request message for joining MBS service to the network side, initiating an MBS service joining process through the request message, and acquiring the MBS service parameters.

25. The system of claim 23, wherein the network side further comprises a unit for initiating an MBS service joining procedure to the terminal when the terminal accesses the network or requires to dynamically establish the MBS service, and providing the MBS service parameters to the terminal.

26. The system according to claim 23, wherein the network side further comprises one or any combination of the following elements:

means for evaluating whether the terminal has the capability of receiving the MBS service;

a unit for performing MBS service authentication on the terminal;

a unit for performing resource reservation for the MBS service;

a unit for establishing a bearer channel for the MBS service;

a unit for registering and/or updating downlink play list for the MBS service;

a unit for generating a key for the MBS service;

and the unit is used for counting the number of users for the MBS service.

27. The system according to any of claims 23 to 26, wherein the unit is one or any combination of the following:

the system comprises a base station, an access service network gateway and/or an MBS agent, an MBS server and an authentication, authorization and accounting server.

Images