CN1960346A - Method for registering multimedia service of broadcast / multicast service - Google Patents

Abstract

The invention discloses a method for registering a multimedia broadcast/multicast service. The method is applicable to a 3G-WLAN interworking system, and the specific process includes: when the packet data gateway in the interworking system determines that it does not have the bearer context of the broadcast/multicast service according to the broadcast/multicast service access request sent by the user terminal, The packet data gateway sends a broadcast/multicast service registration request to the broadcast/multicast service center; after receiving the registration request, the broadcast/multicast service center creates the bearer context of the broadcast/multicast service and replies to the broadcast/multicast service broadcast service registration response to the packet data gateway; the packet data gateway processes the received registration response and ends the registration. The method of the invention enables the MBMS service to be carried out on the 3G-WLAN architecture, thereby making full use of the high-speed data service provided by the WLAN.

Description

A registration method for multimedia broadcast/multicast service

technical field

The invention relates to wireless communication technology, in particular to a method for registering multimedia broadcast/multicast services.

Background technique

Since the data rate provided by the third-generation (3G) mobile communication is much higher than that of the second-generation mobile communication, 3G mobile communication can support various business forms, such as video calls, picture downloads, and high-speed Internet browsing. Among the 3G services, there is a type of service that has the feature of group sending, that is, data can be sent to a certain group of users in the wireless network at the same time, such as weather forecast, news clips, sports game highlights, etc. In order to make full use of the group sending characteristics of the above-mentioned services, the 3G mobile communication system introduces the concept of broadcast/multicast from Rel-6, in order to effectively use limited air interface resources and provide greater system capacity.

In the broadcast/multicast service (MBMS, Multimedia Broadcast/Multicast Service), before the data reaches the destination node from the root node, it needs to be forwarded by the intermediate node. For an intermediate node, no matter how many destination nodes expect to receive data in its downstream, its upstream node always sends a piece of data to the intermediate node; after the intermediate node receives the data, it The data is replicated and distributed to said downstream nodes. Therefore, during the broadcast/multicast service data transmission process, each branch of the service data transmission tree only transmits one piece of data and occupies one piece of transmission resources. The difference between multicast and broadcast is that users need to subscribe to multicast services to receive information; broadcast services send information to all users in the wireless network. It can be seen from the above description that the same information can be provided to a large number of users at the same time through broadcast/multicast, thus greatly saving network resources.

FIG. 1 is a schematic structural diagram of an existing wireless network supporting broadcast/multicast services. As shown in Figure 1, broadcast/multicast service center (BM-SC, Broadcast/Multicast-Service Centre) 101 links to each other with a plurality of gateway GPRS support nodes (GGSN, Gateway GPRS SupportNode) 102 by Gmb/Gi interface; The /Gp interface is connected with multiple serving GPRS support nodes (SGSN, Serving GPRS Support Node) 103; SGSN is connected with UMTS terrestrial radio access network (UTRAN) 104 through Iu interface, or is connected with GSM enhanced wireless access through Iu/Gb interface Network (GERAN) 105 is connected. Finally, the UTRAN is connected to the user terminal (UE) 106 through the Uu interface, or the GERAN is connected to the UE through the Um interface. In the above network structure, GGSN and SGSN belong to core network (CN) nodes in the wireless network.

When the broadcast/multicast service center sends data for the multimedia broadcast/multicast service, it can be used as an access point for MBMS content transmission, authorization and initiation of MBMS bearer services in the PLMN, and can also schedule MBMS data transmission. That is, BM-SC, as a functional entity, must include the following functions: membership function, session and transmission function, proxy and transmission function, service declaration function and security function, etc.

Based on the system structure shown in Figure 1, the registration process of the existing MBMS service is shown in Figure 2, including the following steps:

Step 201, when the RNC in the UTRAN detects that the UE under its control needs to acquire MBMS service data, it will send an MBMS Registration Request (MBMS RegistrationRequest) message to the SGSN.

Step 202, if there is no bearer context for the MBMS service on the SGSN, the SGSN creates an MBMS bearer context, puts the context in the "Standby" state, and sends an MBMS Registration Request message to the GGSN, which carries an IP multicast address and APNs.

In this step, after receiving the registration request from the RNC, the SGSN will also perform the following operations:

1) Add the RNC identifier to the "list ofdownstream nodes" parameter of the MBMS bearer context created by itself.

2) Return the MBMS Registration Response (MBMS Registration Response) message to the RNC, carrying the Temporary Mobile Group Identity (TMGI) and the required MBMS bearer capacity. The required MBMS bearer capability refers to Quality of Service (QoS).

3) If the MBMS bearer context is in the "Active" state, the SGSN initiates a session start (Session Start) process to the RNC.

Step 203, if there is no bearer context for the MBMS service on the GGSN, the GGSN creates an MBMS bearer context, and sends an MBMS Registration Request message carrying the IP multicast address and APN to the agent and transmission module of the BM-SC.

In this step, after receiving the registration request from the SGSN, the GGSN will also perform the following operations:

1) Add the SGSN identifier to the "list ofdownstream nodes" parameter of the MBMS bearer context created by itself.

2) Return the MBMS Registration Response message to the SGSN, carrying the TMGI and the required MBMS bearer capacity.

3) If the MBMS bearer context is in the "Active" state, the GGSN initiates the Session Start process to the SGSN.

Step 204, the proxy and transmission module of the BM-SC adds the identifier of the GGSN to the "list of downstream nodes" parameter of the MBMS bearer context, and returns the MBMSRegistration Response message to the GGSN, carrying the TMGI and the required MBMS bearer capability in the message . At the same time, if the MBMS bearer context is in the "Active" state, the BM-SC initiates the Session Start process to the GGSN.

The registration process of the above MBMS service is designed for the system architecture of GPRS/UMTS shown in FIG. 1 , and the access network is GERAN/UTRAN.

With the increasing requirements of users for wireless access rate, wireless local area network (WLAN, Wireless Local Area Network) also emerges at the historic moment, this kind of WLAN can provide high-speed wireless data access in a small range. User terminals can be connected to the Internet (Internet) and intranet (Intranet) through the WLAN access network, or can be connected to the home/visit network in 3G systems such as 3GPP and 3GPP2 through the WLAN access network, and communicate with the 3G system. A WLAN network is called an interworking WLAN (I-WLAN).

The structure of the 3G-WLAN interworking system is shown in Figure 3, including: WLAN user terminal (WLANUE) 301, wireless local area network access network (WLAN AN) 302, wireless local area network access gateway (WAG, WLAN Access Gateway) 303, packet data Gateway (PDG, Packet Data Gateway) 304, Authentication Authorization Accounting (AAA) server 305 and BM-SC 306.

Wherein, the WLAN UE is connected to the access network 302 through the Ww interface, or the WLAN UE is directly connected to the PDG 304 through the Wu interface. The access network 302 is connected to the WAG 303 through the Wn interface, or the access network 302 is connected to the AAA server 305 through the Wa interface. WAG is connected with PDG 304 through Wp interface, and PDG 304 is connected with AAA server 305 through Wm interface. The AAA server is connected to the BM-SC 306, or the PDG is directly connected to the BM-SC, where the signaling interfaces between the PDG and the BM-SC, and between the AAA server and the BM-SC can be implemented based on the Gmb interface, and the PDG and the BM - The data interface between SCs can be implemented based on the Wi interface.

Based on the above connections, when a WLAN UE accesses locally, the UE is connected to the 3G home network via the access network; when the UE is roaming, it is connected to the 3G access network via the access network, and then the access network is connected to the UE's home network . In order to support UE roaming, some entities in the 3G access network are interconnected with corresponding entities in the home network, for example: the AAA proxy server in the 3G access network is connected to the AAA server in the home network through the Wd interface; The WAG is connected to the PDG in the home network, etc.

As a broadband access technology, WLAN can provide high-speed data services, so MBMS services can be introduced through the interconnection of WLAN and 3G systems, so as to fully provide and display MBMS services to users. However, the prior art does not provide an MBMS service registration method that uses WLAN as an access network and is suitable for the 3G-WLAN architecture, so that the MBMS service cannot be carried out on the 3G-WLAN architecture.

Contents of the invention

In view of this, the main purpose of the present invention is to provide a registration method for multimedia broadcast/multicast services, so that the 3G-WLAN environment can provide users with MBMS services.

In order to achieve the above object, the technical solution of the present invention is specifically realized in the following way:

A method for registering a multimedia broadcast/multicast service, applicable to a 3G-WLAN interworking system, wherein a packet data gateway in the interworking system determines that the broadcast/multicast service does not exist in itself according to a broadcast/multicast service access request sent by a user terminal When the bearer context of the service is used, the method includes the following steps:

a. The packet data gateway sends a broadcast/multicast service registration request to the broadcast/multicast service center;

b. After receiving the registration request, the broadcast/multicast service center creates the bearer context of the broadcast/multicast service, and replies a broadcast/multicast service registration response to the packet data gateway;

c. The packet data gateway processes the received registration response and ends the registration.

In step b, after the broadcast/multicast service center receives the registration request, the method further includes: the broadcast/multicast service center records the packet data gateway identifier in the downstream node list of the bearer context created by the broadcast/multicast service center.

In step b, after the broadcast/multicast service center sends the registration response to the packet data gateway, it further sends an information deployment notification to the packet data gateway;

Before finishing the registration in step c, the method further includes: after receiving the information deployment notification, the packet data gateway sends the bearer context information, the user ID and the tunnel ID to the WLAN access network and/or the WLAN access gateway.

Before finishing the registration in step c, the method further includes: the packet data gateway sends the bearer context information, the user ID and the tunnel ID to the WLAN access network and/or the WLAN access gateway.

In step a, the packet data gateway sends a broadcast/multicast service registration request to the broadcast/multicast service center through the AAA server;

In step b, the broadcast/multicast service center replies a broadcast/multicast service registration response to the packet data gateway through the AAA server.

In step b, after the broadcast/multicast service center receives the registration request, the method further includes: the broadcast/multicast service center respectively records the packet data gateway identifier and the The above AAA server ID.

In step a, after receiving the registration request, the AAA server creates the bearer context of the broadcast/multicast service by itself.

In step b, after the AAA server receives the registration response, the method further includes: the AAA server sends the bearer context information, the user ID and the tunnel ID to the WLAN access network and/or the WLAN access gateway.

Before ending the registration in step c, the method further includes: the packet data gateway sends an information deployment notification to the AAA server, and after receiving the notification, the AAA server sends the bearer context information, user ID and tunnel ID to the WLAN access network and/or WLAN access gateway.

Before ending the registration in step c, the method further includes: the broadcast/multicast service center sends an information deployment notification to the AAA server, and the AAA server sends the bearer context information, user ID and tunnel ID to the WLAN access network after receiving the notification and/or WLAN access gateways.

The user identifier includes at least one of the following identifiers: International Mobile Subscriber Identifier, Mobile Station Integrated Services Digital Network Number, Network Access Identifier and Session Initiation Protocol Uniform Resource Identifier.

The tunnel identifier includes at least one of the following identifiers: Internet security protocol security association, security parameter index, Internet key exchange protocol security association, and user IP address and port number.

The broadcast/multicast service registration request/response is carried by any one of the following protocols: Diameter protocol, RADIUS protocol, HTTP protocol, SIP protocol and WAP protocol.

In step a, before the packet data gateway sends a registration request, the method further includes: the packet data gateway creates a bearer context for the broadcast/multicast service;

Then, the method for processing the registration response by the packet data gateway in step c is: the packet data gateway sets its own bearer context according to the registration response.

In step a, the packet data gateway generates first bearer information for the broadcast/multicast service when creating the bearer context, and sends it through a broadcast/multicast service registration request;

In step b, after the broadcast/multicast service center receives the registration request, it sets the corresponding item of the bearer context created by itself according to the first bearer information, and generates second bearer information for the broadcast/multicast service, and then The second bearer information is sent to the packet data gateway through a broadcast/multicast service registration response;

Then in step c, the packet data gateway sets the corresponding item of its own bearer context according to the second bearer information.

The first bearer information includes: an IP multicast address and a name of a wireless local area network access point.

The second bearer information includes: temporary mobile group identifier, required MBMS bearer capability and MBMS service area.

The method for processing the registration response by the packet data gateway in step c is: the packet data gateway creates a bearer context on itself, and sets the bearer context according to the registration response.

It can be seen from the above technical solution that the registration method of the multimedia broadcast/multicast service of the present invention enables the MBMS service to be developed on the 3G-WLAN architecture by providing a complete process of MBMS service registration in the WLAN environment.

Description of drawings

FIG. 1 is a schematic structural diagram of a wireless network supporting broadcast/multicast services in the prior art;

Fig. 2 is the registration process of MBMS service in the prior art;

FIG. 3 is a composition structure of a 3G-WLAN interworking system in the prior art;

Fig. 4 is the registration procedure of MBMS service in the first embodiment of the present invention;

Fig. 5 is the registration procedure of MBMS service in the second embodiment of the present invention;

Fig. 6 is the registration procedure of MBMS service in the third embodiment of the present invention;

Fig. 7 is the registration process of the MBMS service in the fourth embodiment of the present invention;

Fig. 8 is the registration process of the MBMS service in the fifth embodiment of the present invention;

FIG. 9 is a flow chart of MBMS service registration in the sixth embodiment of the present invention.

Detailed ways

In order to make the object, technical solution and advantages of the present invention clearer, the present invention will be further described in detail below with reference to the accompanying drawings and examples.

Based on the 3G-WLAN system structure shown in Figure 3, the MBMS service registration process of the present invention is as follows:

Embodiment one,

As shown in Figure 4, the registration process of the MBMS service includes the following steps:

Step 401, WLAN UE sends MBMS service access request to PDG through access network and WAG.

Step 402, after receiving the above request, the PDG determines that it does not have the MBMS bearer context of the service, and triggers a registration process.

In step 403, the PDG sends an MBMS registration request to the BM-SC.

The registration request carries the first bearer information generated by the PDG for the MBMS bearer context of the service, and the information includes: an IP multicast address and a wireless local area network access point name (W-APN).

In this step, before the PDG sends the MBMS registration request, it can create the MBMS bearer context of the service itself.

Step 404: After receiving the registration request, the BM-SC creates the MBMS bearer context of the service, adds the PDG identifier to the list of downstream nodes (listof downstream nodes) of the created MBMS bearer context, and replies MBMS registration to the PDG Respond to the message.

Since the registration request carries the first bearer information, the BM-SC configures corresponding parameters of the MBMS bearer context created by itself according to the first bearer information.

In addition, the registration response carries the second bearer information generated by the BM-SC for the MBMS bearer context of the service, and the information includes: TMGI, required MBMS bearer capability, MBMS service area and so on.

The aforementioned MBMS registration request and/or response may be sent using any of the following protocols, namely: Diameter protocol, RADIUS protocol, HTTP protocol, SIP protocol, and WAP protocol, etc., which will not be described here.

Step 405, the PDG processes the received registration response, and the registration process ends.

If in step 403, the PDG has created its own bearer context, then the PDG will configure the corresponding parameters of the MBMS bearer context created by itself according to the second bearer information.

If the PDG does not perform the operation of creating a bearer context in step 403, after receiving the registration response in this step, the PDG may first create a bearer context, and then configure corresponding parameters of the MBMS bearer context created by itself according to the second bearer information.

Embodiment two,

As shown in Figure 5, the registration process of the MBMS service includes the following steps:

Steps 501 - 502 are the same as steps 401 - 402 in FIG. 4 , and will not be repeated here.

In step 503, the PDG creates the MBMS bearer context of the service itself, and sends an MBMS registration request to the AAA server. After receiving the above registration request, the AAA server sends the MBMS registration request to the BM-SC.

In this step, after receiving the registration request, the AAA server can also create the MBMS bearer context of the service itself, and add the PDG identifier to the list ofdownstream nodes of the bearer context.

The registration request carries the first bearer information generated by the PDG for the MBMS bearer context of the service, and the information includes: IP multicast address and W-APN.

Step 504, after receiving the registration request, the BM-SC creates the MBMS bearer context of the service, and the MBMS bearer context is set with two lists of downstream nodes, which are respectively used to record the ID of the PDG and the ID of the AAA server. Then, the BM-SC replies an MBMS registration response message to the AAA server, and the AAA server forwards the registration response to the PDG.

In this step, after the BM-SC records the PDG identifier, in the subsequent service data transmission, the BM-SC can directly send the service data to the corresponding PDG. In addition, the purpose of the BM-SC recording the AAA server identifier is to send signaling, such as session start signaling, to the WLAN AN and/or WAG according to the AAA server identifier.

The registration response carries the second bearer information generated by the BM-SC for the MBMS bearer context of the service, and the information includes: TMGI, required MBMS bearer capability, and MBMS service area.

After receiving the registration response, the AAA server may modify the second bearer information carried in the message, such as the required MBMS bearer capability.

Step 505: After receiving the registration response, the PDG configures the corresponding parameters of the MBMS bearer context created by itself according to the second bearer information, and the registration process ends.

Embodiment three,

As shown in Figure 6, the registration process of the MBMS service includes the following steps:

Steps 601 to 604 are the same as steps 501 to 504 in FIG. 5 , and will not be repeated here.

Step 605, the AAA server sends an information notification message, and sends the MBMS bearer context information, user ID and tunnel ID to WLAN AN and/or WAG.

In addition, the AAA server may receive or not receive the response message replied by the WLAN AN and/or WAG according to preset settings.

The MBMS bearer context information includes: TMGI, required MBMS bearer capability, MBMS service area and other protocol-specified bearer context parameters.

The user identification includes at least one of the following identifications: International Mobile Subscriber Identifier (IMSI), Mobile Station Integrated Services Digital Network Number (MSISDN), Network Access Identifier (NAI) and Session Initiation Protocol Uniform Resource Identifier (SIP URI ).

The tunnel identifier includes at least one of the following identifiers: Internet Security Protocol Security Association (IPsecSA), Security Parameter Index (SPI), Internet Key Exchange Protocol Security Association (IKE SA), and user IP address and port number.

Embodiment four,

As shown in Figure 7, the registration process of the MBMS service includes the following steps:

Steps 701 to 704 are the same as steps 401 to 404 in FIG. 4 , and will not be repeated here.

Step 705, BM-SC sends an information deployment notification to PDG, requesting PDG to deploy MBMS bearer context information, user ID and tunnel ID to WLAN AN and/or WAG. In this step, the information deployment notification may be carried in a registration response message, or sent in a separate message.

Step 706: After receiving the information deployment notification, the PDG sends the MBMS bearer context information, user ID and tunnel ID to the WLAN AN and/or WAG through the AAA server. In addition, the PDG can receive or not receive the response message replied by the WLAN AN and/or WAG according to preset settings.

Alternatively, in step 706, the PDG directly sends the MBMS bearer context information, the user ID and the tunnel ID to the WLAN AN and/or the WAG through an information notification message without passing through the AAA server.

Embodiment five,

As shown in Figure 8, the registration process of the MBMS service includes the following steps:

Steps 801 to 804 are the same as steps 401 to 404 in FIG. 4 , and will not be repeated here.

Step 805, PDG directly sends the information notification message carrying MBMS bearer context information, user ID and tunnel ID to WLAN AN and/or WAG. In addition, the PDG can receive or not receive the response message replied by the WLAN AN and/or WAG according to preset settings.

Alternatively, in step 805, the PDG sends an information deployment notification to the AAA server, and the AAA server sends the MBMS bearer context information, user ID and tunnel ID to the WLAN AN and/or WAG after receiving the notification.

Embodiment six,

As shown in Figure 9, the registration process of the MBMS service includes the following steps:

Steps 901 to 904 are the same as steps 401 to 404 in FIG. 4 , and will not be repeated here.

Step 905, the BM-SC sends an information deployment notification to the AAA server.

Step 906: After receiving the notification, the AAA server sends the MBMS bearer context information, user ID and tunnel ID to WLAN AN and/or WAG. In addition, the BM-SC can receive or not receive the response message replied by the WLAN AN and/or WAG according to the preset settings.

Or, in step 905, the BM-SC directly sends the MBMS bearer context information, the user ID and the tunnel ID to the WLAN AN and/or the WAG through an information notification message without going through the AAA server.

Further, in the above embodiment, after receiving the MBMS service access request, the access network and/or WAG may also judge whether it has an MBMS bearer context for the service, and if not, create a context for the service in itself. MBMS carries the context and sends a registration request to the upstream node.

For example, when the access network determines that it has no MBMS bearer context, it will send a registration request to the WAG. If the WAG has obtained the bearer context information in the previous process, it will reply a registration response carrying the bearer context information to the access network. Among them, WAG can obtain bearer context information by upstream nodes actively deploying, for example, PDG, AAA server or BM-SC sends bearer context information to WAG through information notification message; or WAG obtains from PDG through registration request.

If there is no MBMS bearer context for the service on the WAG, the WAG will send a registration request to its upstream node PDG.

It can be seen from the above-mentioned embodiments that the registration method of the multimedia broadcast/multicast service of the present invention enables the MBMS service to be carried out on the 3G-WLAN architecture by providing a complete process for registering the MBMS service in the wireless local area network environment, so that it can fully Take advantage of high-speed data services provided by WLAN.

Claims (18)

1. A method for registering a multimedia broadcast/multicast service, applicable to a 3G-WLAN interworking system, characterized in that the packet data gateway in the interworking system determines that it does not exist according to the broadcast/multicast service access request sent by the user terminal When carrying the context of the broadcast/multicast service, the method includes the following steps: a. The packet data gateway sends a broadcast/multicast service registration request to the broadcast/multicast service center; b. After receiving the registration request, the broadcast/multicast service center creates the bearer context of the broadcast/multicast service, and replies a broadcast/multicast service registration response to the packet data gateway; c. The packet data gateway processes the received registration response and ends the registration. 2. The method according to claim 1, characterized in that, in step b, after the broadcast/multicast service center receives the registration request, the method further comprises: downstream of the bearer context created by the broadcast/multicast service center The packet data gateway identifier is recorded in the node list. 3. The method according to claim 1, wherein in step b, after the broadcast/multicast service center sends the registration response to the packet data gateway, it further sends an information deployment notification to the packet data gateway; Before finishing the registration in step c, the method further includes: after receiving the information deployment notification, the packet data gateway sends the bearer context information, the user ID and the tunnel ID to the WLAN access network and/or the WLAN access gateway. 4. The method according to claim 1, characterized in that, before finishing the registration in step c, the method further comprises: the packet data gateway sends the bearer context information, the user ID and the tunnel ID to the WLAN access network and/or WLAN access gateway. 5. The method according to claim 1, wherein in step a, the packet data gateway sends a broadcast/multicast service registration request to the broadcast/multicast service center through the AAA server; In step b, the broadcast/multicast service center replies a broadcast/multicast service registration response to the packet data gateway through the AAA server. 6. The method according to claim 5, wherein in step b, after the broadcast/multicast service center receives the registration request, the method further comprises: the bearer context created by the broadcast/multicast service center itself The ID of the packet data gateway and the ID of the AAA server are respectively recorded in the list of downstream nodes. 7. The method according to claim 5, wherein in step a, after receiving the registration request, the AAA server creates the bearer context of the broadcast/multicast service by itself. 8. The method according to claim 5, wherein in step b, after the AAA server receives the registration response, the method further comprises: the AAA server sends the bearer context information, user ID and tunnel ID to the WLAN access Network and/or WLAN access gateway. 9. The method according to claim 5, characterized in that, before finishing the registration in step c, the method further comprises: the packet data gateway sends an information deployment notification to the AAA server, and after receiving the notification, the AAA server will carry the context information, The user ID and the tunnel ID are sent to the WLAN access network and/or the WLAN access gateway. 10. The method according to claim 5, characterized in that, before finishing the registration in step c, the method further comprises: the broadcast/multicast service center sends an information deployment notification to the AAA server, and the AAA server sends the bearer The context information, the user ID and the tunnel ID are sent to the WLAN access network and/or the WLAN access gateway. 11. The method according to claim 3, 4, 8, 9 or 10, wherein the user identification includes at least one of the following identifications: International Mobile Subscriber Identity, Mobile Station ISDN Number, Network Access Number Input Identifier and Session Initiation Protocol Uniform Resource Identifier. 12. The method according to claim 3, 4, 8, 9 or 10, wherein the tunnel identifier includes at least one of the following identifiers: Internet Security Protocol Security Association, Security Parameter Index, Internet Key Exchange Protocol Security association, as well as the user IP address and port number. 13. The method according to claim 1, wherein the broadcast/multicast service registration request/response is carried by any of the following protocols: Diameter protocol, RADIUS protocol, HTTP protocol, SIP protocol and WAP protocol. 14. The method according to claim 1, wherein in step a, before the packet data gateway sends out the registration request, the method further comprises: the packet data gateway creates a bearer context for the broadcast/multicast service; Then, the method for processing the registration response by the packet data gateway in step c is: the packet data gateway sets its own bearer context according to the registration response. 15. The method according to claim 14, wherein in step a, when creating the bearer context, the packet data gateway generates the first bearer information for the broadcast/multicast service, and registers the broadcast/multicast service the request is issued; In step b, after the broadcast/multicast service center receives the registration request, it sets the corresponding item of the bearer context created by itself according to the first bearer information, and generates second bearer information for the broadcast/multicast service, and then The second bearer information is sent to the packet data gateway through a broadcast/multicast service registration response; Then in step c, the packet data gateway sets the corresponding item of its own bearer context according to the second bearer information. 16. The method according to claim 15, wherein the first bearer information includes: an IP multicast address and a name of a wireless local area network access point. 17. The method according to claim 15, wherein the second bearer information includes: temporary mobile group identifier, required MBMS bearer capability and MBMS service area. 18. The method according to claim 1, wherein the method for processing the registration response by the packet data gateway in step c is: the packet data gateway creates a bearer context on itself, and sets the bearer context according to the registration response.

Images