|
(11) | EP 1 742 413 A1 |
| (12) | EUROPEAN PATENT APPLICATION |
| published in accordance with Art. 158(3) EPC |
|
|
|
|
|||||||||||||||||||
| (54) | A METHOD OF STARTING THE SESSION OF MULTIMEDIA BROADCAST MULTICAST SERVICE |
| (57) The present invention discloses a Multimedia Broadcat/Multicast service (MBMS) session
start method. The MBMS session start method includes the steps of: an MBMS Center
(BM-SC) initiating a session start request message via a GGSN to an SGSN; receiving
the MBMS session start request message, the SGSN sending the MBMS session start request
message to a BSC/RNC; receiving the MBMS session start request message, the BSC/RNC
checking whether to establish a bearer plane for the MBMS session, if estalishing,
activating an MBMS bearer context and the RAN establishing radio resources to the
user equipment (UE). The method makes it possible to optimize the system performance,
reduce the resource waste of the radio network, and lower the complexity of the system
processing. |
Field of the invention
[0001] The present invention relates to multimedia broadcast multicast services (MBMS) in a 3G mobile communication system, more particularly to an MBMS session start method.
Background of the invention
[0002] With the development of the 3G mobile communication technology, services with a higher speed than those in the 2G mobile communication systems are provided, with more types, including such services as Videotel, image downloading, high-speed Internet browsing and etc, wherein, one service has the feature that the service content could be sent simultaneously to the users who subscribe to the service in the radio network, such as weather forecast, news short, sports game selection and etc. With the service feature of simultaneous transmission, the multicast/broadcast technology is introduced in the 3G mobile communication systems.
[0003] As shown in Figure 1, which is a schematic diagram illustrating the working principle of MBMS, for an intermediate node, no matter how many downstream nodes, as 10, 101, or 102 shown in Figure 1, are waiting to receive the data, the upstream node will send one set of data to the intermediate node; after receiving the data, the intermediate node will make data copies according to the number of downstream nodes waiting to receive the data, and distribute the data to the downstream nodes waiting to receive the data. In this way, one set of data will be transmitted in each branch of the MBMS data transmission tree and one set of resources for transmission is occupied, and it is the same for the data transmission from the root node to its downstream nodes. The difference between a multicast service and a broadcast service is that the service information is sent to the users who subscribe to the service in a multicast service instead of all the users in the radio network in a broadcast service. As the description shown above, the network resources could be saved remarkably by using MBMS to provide identical information simultaneously for a large number of users.
[0004] As shown in Figure 2, which is a schematic diagram illustrating the radio network architecture for MBMS, in the prior art according to the 3rd Generation Partnership Project (3GPP), the radio network architecture for MBMS services is that the Broadcast/Multicast Service Centre (BM-SC) 201 is connected to Gateway GPRS (General Packet Radio Service) Support Node (GGSN) 202 via the Gmb interface or Gi interface, wherein one BM-SC 201 may be connected to multiple GGSN 202; GGSN 202 is connected to Serving GPRS Support Node (SGSN) 203 via the Gn/Gp interface, wherein one GGSN 202 may be connected to multiple SGSN 203; SGSN 203 is connected to Universal Terrestrial Radio Access Network (UTRAN) 204 in the Universal Mobile Telecommunications System (UMTS) via the Iu interface and the UTRAN 204 is connected to the User Equipment (UE) 206 via the Uu interface; or SGSN 203 may be connected to GSM/EDGE Radio Access Network (GERAN) 205 in the Global System for Mobile communications (GSM) via the Iu/Gb interface and the GERAN 205 is connected to UE 207 via the Um interface.
[0005] An MBMS bearer context is used for storing the MBMS bearer capacity, which includes all the description information for defining an MBMS bearer and will be established on all the nodes bearing the MBMS data. As shown in Table 1, an MBMS bearer context includes IP multicast address, Access Point Name (APN), Temporary Mobile Group Identifier (TMGI), state, required MBMS bearer capacity, Quality of Service (QoS), MBMS service area, list of downstream node, the number of UEs and etc, wherein, the IP multicast address identifies the MBMS bearer described by the MBMS bearer context; the APN is the access point name defined for the IP multicast address; the TMGI is the temporary mobile group identifier assigned for the MBMS bearer; the state is the activity state of the MBMS bearer ('static' or 'activated') indicating whether to establish bearer plane resources for the MBMS data transmission; the required MBMS bearer capacity identifies the least bearer capacity for the UE; the QoS is the quality of service required by the MBMS bearer; the MBMS service area is the area to which the MBMS information will be sent; the list of downstream node includes the downstream nodes that have requested the MBMS bearer and to which the MBMS data should be sent; the number of UEs is the number of UEs which join the multicast service and are dominated by the node.
| Parameter | Description | RAN | SGSN | GGSN | BM-SC |
| IP multicast address | Identifying the MBMS bearer described by the MBMS bearer context. | X | X | X | X |
| APN | Access point name defined for the IP multicast address. | X | X | X | To be studied |
| TMGI | Temporary mobile group identifier assigned for the MBMS bearer. | X | X | X | X |
| State | Activity state of the MBMS bearer ('static' or 'activated') | To be studied | X | X | X |
| Required MBMS bearer capacity | The least bearer capacity for the UE | X | X | X | |
| QoS | Quality of service required by the MBMS bearer. | X | X | X | X |
| MBMS service area | Area to which the MBMS information will be sent. | X | X | X | X |
| List of downstrea m node | List of the downstream nodes that have requested the MBMS bearer and to which the MBMS data should be sent | X | X | X | |
| Number of UEs | Number of the UEs which join the multicast service and are dominated by the node. | To be studied | X | X | To be studied |
[0006] According to the network architecture as shown in Figure 2, the session start processes for a multicast service and a broadcast service of MBMS with the prior art are hereinafter described, respectively.
[0007] For an MBMS multicast service:
The users join the MBMS multicast service through an MBMS activation process, thus the network learns which users want to receive the information of a specific MBMS service.
[0008] Through an MBMS registration process, the network nodes can establish a distribution tree from BM-SC, via GGSN, SGSN, to Base Station Controller/Radio Network Controller (BSC/RNC), so as to allow the transmission for the attributes and data of an MBMS session. In the registration process, an MBMS bearer context can be established on the related nodes while no bearer plane is established.
[0009] As shown in Figure 3, which is a schematic diagram illustrating the MBMS registration process with the cooperation of BSC/RNC and SGSN, when the BSC/RNC finds the UE dominated by itself is interested in the MBMS service but the BSC/RNC has not registered for the MBMS service, the registration process will be executed, including:
Step 301: the BSC/RNC sends an MBMS registration request message to its parent SGSN.
Step 302: upon receiving the registration request message from the BSC/RNC, the SGSN that has registered for the MBMS bearer service adds the BSC/RNC to the "list of downstream node" in the MBMS bearer context and returns an MBMS registration response message to the BSC/RNC.
[0010] The MBMS session start process will be initiated when the BM-SC is ready to transmit the data. The session start process activates all the bearer resources necessary to transmit the MBMS data in the network and notifies the interested UEs that the data transmission is to be started. By this process, the BM-SC provides the MBMS session attributes, such as QoS, MBMS service area, estimated session duration (if existing) for the related interested nodes. This process will also initiate other related processes executed by the BSC/RNC in the access network, such as sending a session notification, counting the cell users, choosing the radio bearer type, establishing radio and cabled bearer planes and etc.
[0011] Figure 4 is a schematic diagram illustrating the session start process of an MBMS multicast service in the prior art. As shown in Figure 4, the process includes:
Step 401: the BM-SC sends a session start request to the GGSN stored in the "list of downstream node" in the corresponding MBMS bearer context, indicating the data transmission is to be started, and sets the state attribute as "activated" in the MBMS bearer context. The session start request provides such session attributes as QoS, MBMS service area, the estimated session duration and etc.
Step 402: upon receiving the session start request message, the GGSN stores the session attributes obtained from the message in the MBMS bearer context, sets the state attribute of the MBMS bearer context as "activated", and sends a session start response message to the BM-SC.
Step 403: the GGSN sends an MBMS session start request to the SGSN stored in the "list of downstream node" in the corresponding MBMS bearer context.
Step 404: upon receiving the MBMS session start request message, the SGSN stores the session attributes in the MBMS bearer context, sets the state attribute of the MBMS bearer context as "activated", and sends an MBMS session start response message to the GGSN, wherein the response message provides the Tunnel Endpoint Identifier (TEID) for the bearer plane, and for the GGSN to transmit the MBMS data.
Step 405: the SGSN sends an MBMS session start request message containing the session attributes to each BSC/RNC connected to this SGSN.
Step 406: the BSC/RNC judges whether it is covered by the MBMS service area, if yes, the BSC/RNC stores the session attributes in the MBMS bearer context, sets the state attribute of the MBMS bearer context as "activated" and then executes step 407; otherwise, executes step 407 directly.
Step 407: the BSC/RNC sends an MBMS session start response message to the SGSN.
[0012] If the BSC/RNC is covered by the MBMS service area, the MBMS session start response message will include the TEID, by which the SGSN establishes the Iu bearer plane to transmit the MBMS data.
[0013] One BSC/RNC may receive multiple MBMS session start request messages carrying the parameter of the Iu bearer plane and return one MBMS session start response message to establish an Iu plane bearer to an SGSN.
[0014] If the BSC/RNC is not covered by the MBMS service area, the MBMS session start response message sent to the SGSN will include the information indicating that the BSC/RNC is not covered by the MBMS service area.
[0015] Then, the BSC/RNC will be able to establish in the MBMS service area the radio resources necessary to transmit the MBMS data to the interested UEs.
[0016] For an MBMS broadcast service:
As a broadcast service transmits the information to all the users in the radio network, it is not needed for the network nodes to execute the MBMS registration process.
[0017] Figure 5 is a schematic diagram illustrating the session start process of an MBMS broadcast service in the prior art. As shown in Figure 5, the process includes:
Step 501: the BM-SC sends a session start request message to the GGSN in the Public Land Mobile Network (PLMN), indicating the data transmission is to be started, and sets the state attribute of the MBMS bearer context as "activated". The session start request provides such session attributes as QoS, MBMS service area, the estimated session duration and etc.
Step 502: upon receiving the session start request message, the GGSN establishes an MBMS bearer context and stores in the MBMS bearer context the session attributes obtained from the message, sets the state attribute of the MBMS bearer context as "activated", and sends a session start response message to the BM-SC.
Step 503: the GGSN sends an MBMS session start request message to each SGSN.
Step 504: upon receiving the MBMS session start request message, the SGSN establishes an MBMS bearer context, stores the session attributes in the MBMS bearer context, sets the state attribute of the MBMS bearer context as "activated", and sends an MBMS session start response message to the GGSN, wherein the response message provides the TEID for the bearer plane, for the GGSN to transmit the MBMS data.
Step 505: the SGSN sends an MBMS session start request message containing the session attributes to each BSC/RNC connected to the SGSN.
Step 506: the BSC/RNC judges whether it is covered by the MBMS service area, if yes, the BSC/RNC establishes an MBMS bearer context, stores the session attributes in the MBMS bearer context, sets the state attribute of the MBMS bearer context as "activated", and then executes step 507; otherwise, executes step 507 directly.
Step 507: the BSC/RNC sends an MBMS session start response message to the SGSN.
[0018] If the BSC/RNC is covered by the MBMS service area, the MBMS session start response message will include the TEID, by which the SGSN establishes the Iu bearer plane to transmit the MBMS data.
[0019] One BSC/RNC may receive multiple MBMS session start request messages carrying the parameter of the Iu bearer plane and return one MBMS session start response message to establish an Iu plane bearer to an SGSN.
[0020] If the BSC/RNC is not covered by the MBMS service area, the MBMS session start response message sent to the SGSN will include the information indicating that the BSC/RNC is not covered by the MBMS service area.
[0021] Then, the BSC/RNC will be able to establish in the MBMS service area the radio resources necessary to transmit the MBMS data to the UEs.
[0022] As shown in the described session start processes of MBMS multicast and broadcast services, for an MBMS session, it is likely that only some of the BSC/RNCs need to receive the service provided by the session, for example, the BSC/RNCs outside the MBMS service area will not need to receive the service provided by the session. In a session start process of MBMS multicast/broadcast service in the prior art, however, the SGSN sends the MBMS session start message to all the BSC/RNCs connected to the SGSN so that the BSC/RNCs that can not receive the MBMS service have to execute the following processes as sending a notification, counting, establishing a bearer and etc.
[0023] In an MBMS session process, it is possible for some BSC/RNCs covered by the MBMS service area to be unable to establish associated MBMS session bearers when the BSC/RNC does not have sufficient radio resources or some errors occur, for example. In a session start process of MBMS multicast/broadcast services in the prior art, however, all the BSC/RNCs covered by the MBMS multicast service area will store the session attributes, set the session state to activate, and establish the associated bearers.
[0024] Therefore, the steps indicated in the above processes in the prior art lead to resource waste of the radio interface and make the system processing more complicated.
[0025] In the prior standards for a session start process of MBMS broadcast service, it is not required for the BM-SC to send down the parameter of estimated session duration. Therefore, the radio access network can not optimize the radio resource management for the MBMS broadcast service according to the session duration, thus decreasing the effectiveness of the radio interface.
[0026] In addition, in the session start process of MBMS multicast service, when the BSC/RNC is to establish an MBMS bearer, it may not have performed an MBMS registration process for the MBMS multicast service. In this case, the BSC/RNC that has not performed the MBMS registration process can not execute the session start process of an MBMS multicast service completely and thus can not implement the MBMS multicast service completely.
Summary of the invention
[0027] In view of the above, the present invention is to provide a session start method for MBMS, which could optimize system performance, reduce the resource waste of radio interface and lower the complexity of the system processing.
[0028] The present invention is further to implement a complete session start process of an MBMS multicast service for the BSC/RNC that has not performed an MBMS registration process, and to provide the radio resource management parameters for the radio access network in an MBMS broadcast service.
[0029] The present invention provides a session start method for MBMS, which includes the following steps:
a Broadcast/Multicast Service Center (BM-SC) initiating a session start request message via a Gateway GPRS Support Node (GGSN) to a Serving GPRS Support Node (SGSN);
receiving the MBMS session start request message, the SGSN sending the MBMS session start request message to a Base Station Controller (BSC)/Radio Network Controller (RNC);
receiving the MBMS session start request message, the BSC/RNC checking whether to establish a bearer plane for the MBMS session, if establishing, activating an MBMS bearer context and the BSC/RNC establishing radio resources to the user equipment (UE); if not establishing, the process being terminated.
[0030] If the session start request initiated by the BM-SC is for a multicast service, the step of the BM-SC initiating the session start request via the GGSN to the SGSN includes the following steps:
the BM-SC sending a session start request message to the GGSN stored in a list of downstream node in the corresponding MBMS bearer context, and setting a state attribute of the MBMS bearer context to activate;
receiving the session start request message, the GGSN storing a session attribute obtained from the message into the MBMS bearer context, setting the state attribute of the MBMS bearer context to activate, and sending a session start response message to the BM-SC;
the GGSN sending the MBMS session start request message to the SGSN stored in the list of downstream node in the corresponding MBMS bearer context; and
receiving the MBMS session start request message, the SGSN storing the session attributes into the MBMS bearer context, setting the state attribute of the MBMS bearer context to activate, and sending an MBMS session start response message to the GGSN, wherein the session start response message providing a Tunnel End Identifier (TEID) used for the bearer plane.
[0031] If the session start request initiated by the BM-SC is the one for a broadcast service, the step of the BM-SC initiating the session start request via the GGSN to the SGSN includes the following steps:
the BM-SC sending the session start request message to the GGSN in the Public Land Mobile Network (PLMN), and setting a state attribute of the MBMS bearer context to activate;
receiving the session start request message, the GGSN establishing the MBMS bearer context, storing a session attribute obtained from the message into the MBMS bearer context, setting the state attribute of the MBMS bearer context to activate, and sending a session start response message to the BM-SC;
the GGSN sending the MBMS session start request message to the SGSN that is connected to the GGSN;
receiving the session start request message, the SGSN establishing the MBMS bearer context, storing the session attribute into the MBMS bearer context, setting the state attribute of the MBMS bearer context to activate, and sending a session start response message to the BM-SC, wherein the session start response message provides a TEID used for the bearer plane.
[0032] The session start request may carry session attributes of an MBMS service area and a Quality of Service (QoS); the SGSN may determine, according to the MBMS service area, the BSC/RNC which is connected to the SGSN and dominates cells overlapped by the MBMS service area; and send the MBMS session start request message to each determined BSC/RNC.
[0033] The session start request may carry a session attribute of a parameter of estimated session duration; the BSC/RNC may establish the radio resources to the UE for transmitting the MBMS data according to the estimated session duration.
[0034] The SGSN may send the MBMS session start request message to each BSC/RNC that is connected with the SGSN; the BSC/RNC may check whether the cells under its domination are overlapped with the MBMS service area carried in the session start request message, if overlapped, check whether to establish a bearer plane for the MBMS session.
[0036] The checking whether to establish a bearer plane for the MBMS session, may be according to whether a user in the cells dominated by the BSC/RNC needs to receive the MBMS session and whether the BSC/RNC is capable of establishing the bearer for the MBMS session.
[0037] The BSC/RNC may send an MBMS session start response to the SGSN indicating the BSC/RNC whether to establish the bearer plane for the MBMS session.
[0038] If the session start request message initiated by the BM-SC is for a multicast service, the BSC/RNC may activate an MBMS bearer context after a registration process is performed successfully.
[0039] The registration process may include the following steps:
the BSC/RNC sending an MBMS registration request message to the SGSN; and
receiving the MBMS registration request message, the SGSN adding the BSC/RNC to a list of downstream node in the MBMS bearer context, and returning an MBMS registration response to the BSC/RNC.
[0040] As shown in the above technical schemes, according to the session start method for MBMS of the present invention, only after the BSC/RNC decides to establish an MBMS bearer will the BSC/RNC set the state of the bearer plane to activate and establish a bearer plane, thus optimizing the system performance, reducing the resource waste of the radio interface, and lowering the complexity of the system processing. In addition, in a session start process of an MBMS multicast service, it will be judged whether the BSC/RNC has performed an MBMS registration process, if not, a registration process will be executed before activating an MBMS bearer context. Therefore, an MBMS registration process is initiated when the registration has not been performed, thus ensures that the MBMS session start process could be implemented correctly and completely.
Brief description of the drawings
[0041]
Figure 1 is a schematic diagram illustrating the working principle of MBMS;
Figure 2 is a schematic diagram illustrating the radio network architecture for MBMS;
Figure 3 is a schematic diagram illustrating the MBMS registration process with the cooperation of BSC/RNC and SGSN;
Figure 4 is a schematic diagram illustrating the session start process of an MBMS multicast service in the prior art;
Figure 5 is a schematic diagram illustrating the session start process of an MBMS broadcast service in the prior art;
Figure 6 is a schematic diagram illustrating the MBMS service area and the SGSN coverage;
Figure 7 is a schematic diagram for the First Embodiment according to the present invention, illustrating the session start process of an MBMS multicast service;
Figure 8 is a schematic diagram for the Second Embodiment according to the present invention, illustrating the session start process of an MBMS multicast service;
Figure 9 is a schematic diagram for the Third Embodiment according to the present invention, illustrating the session start process of an MBMS broadcast service.
Detailed description of the invention
[0042] In order to make the objectives, technical schemes and advantages of the present invention clearer, the present invention will be hereinafter further described in detail with reference to the accompanying drawings and four
preferred embodiments.
[0043] According to the session start method for MBMS provided by the present invention, the BSC/RNC in the MBMS service area, after receiving an MBMS session start request from the SGSN, will not directly set the state of the MBMS bearer context "to activate" and establish a bearer plane then. Instead, the BSC/RNC will first judge according to the current system condition whether to establish a bearer plane for the MBMS session. Therefore, only after the BSC/RNC decides to establish an MBMS bearer, will the BSC/RNC set the state of the MBMS bearer context "to activate" and establish a bearer plane then.
[0044] In addition, in a session start process of an MBMS multicast service, it should be further examined whether the BSC/RNC which has decided to establish an MBMS bearer has registered in the upstream node, if not, an MBMS registration process will be initiated to ensure that the MBMS session start process could be executed completely and correctly.
[0045] In a session start process of an MBMS broadcast service, the BM-SC may estimate the duration of this MBMS broadcast session, and send the estimated session duration via the session start process of the MBMS broadcast service to the BSC/RNC for the radio resource management. Alternatively, the BM-SC may also not send the estimated session duration parameter to the BSC/RNC.
[0047] Figure 6 illustrates a schematic diagram illustrating the MBMS service area and the SGSN coverage of the present embodiment. The BM-SC is connected to a GGSN_X and the GGSN_X is also connected to an SGSN_X. There are four BSC/RNCs in the SGSN_X, i.e. BSC/RNC_A, BSC/RNC_B, BSC/RNC_C and BSC/RNC_D. The MBMS service area covers part of BSC/RNC_A, part of BSC/RNC_B and part of BSC/RNC_C, respectively. The SGSN_X is in the list of downstream node for the GGSN_X, and the GGSN_X is in the list of downstream node for the BM-SC.
[0048] The four preferred embodiments in the present invention are all implemented based on the condition shown in Figure 6.
First Embodiment:
[0049] Figure 7 illustrates a schematic diagram for the first Embodiment according to the present invention, illustrating the session start process of an MBMS multicast service, which includes the following steps:
Step 701: the BM-SC sends a session start request message to the GGSN stored in the "list of downstream node" in the corresponding MBMS bearer context, indicating the data transmission is to be started, and sets the state attribute of the MBMS bearer context as "activated". The session start request message provides such session attributes as QoS, MBMS service area, estimated session duration and etc.
Step 702: upon receiving the session start request message, the GGSN_X stores the session attributes obtained from the request message in the MBMS bearer context, sets the state attribute of the MBMS bearer context as "activated", and sends a session start response message to the BM-SC.
Step 703: the GGSN_X sends an MBMS session start request message to the SGSN_X stored in the "list of downstream node" in the corresponding MBMS bearer context.
Step 704: upon receiving the MBMS session start request message, the SGSN_X stores the session attributes in the MBMS bearer context, sets the state attribute of the MBMS bearer context as "activated", and sends an MBMS session start response message to the GGSN_X, wherein the response message provides the TEID for the bearer plane, and for the GGSN to transmit the MBMS data.
Step 705: according to the MBMS service area information in the session attributes, the SGSN_X determines the cells overlapped by the MBMS service area and dominated by the BSC/RNCs connected to the SGSN_X, and then sends an MBMS session start request to each BSC/RNC corresponding to the determined cell. Specifically, the SGSN_X determines the cells covered at least partially by the MBMS service area among all the cells dominated by the BSC/RNCs connected to the SGSN_X, and sends an MBMS session start request message containing the session attributes to each BSC/RNC corresponding to the determined cell and serving the MBMS service area.
[0050] In this embodiment, among the cells dominated by the BSC/RNC_D, no cell is covered by the MBMS service area in this MBMS session, therefore, the SGSN_X sends the MBMS session start request messages to BSC/RNC_A, BSC/RNC_B and BSC/RNC_C, respectively.
[0051] Step 706: upon receiving the MBMS session start request message from the SGSN_X, the BSC/RNC_A, BSC/RNC_B or BSC/RNC_C determines whether to establish a bearer plane for the MBMS session, according to whether there is a user who needs to receive the MBMS session information and is located in one of the cells dominated by the corresponding BSC/RNC, and whether the corresponding BSC/RNC is capable of establishing the radio and cabled bearers for the MBMS session.
[0053] As for the BSC/RNC_A, if it decides to establish a bearer plane for the MBMS session, it will first examine whether it has performed an MBMS registration, i.e. examine whether there exists an MBMS bearer context for the MBMS service, if yes, it will store the session attributes in the MBMS bearer context, set the state attribute of the MBMS bearer context as "activated", and then execute step 709; otherwise, it will store the session attributes in the MBMS bearer context, set the state attribute of the MBMS bearer context as "activated", and then execute step 707, step 708 and then step 709. Figure 7 shows the processing for BSC/RNC_A.
[0054] As for the BSC/RNC_B, if it decides to establish a bearer plane for the MBMS session and has performed the MBMS registration, it will store the session attributes in the MBMS bearer context, set the state attribute of the MBMS bearer context as "activated", and then execute step 709 directly.
[0055] As for the BSC/RNC_C, it decides not to establish a bearer plane for the MBMS session due to such reasons as no user interested in the MBMS session, radio or cabled resource insufficiency of the BSC/RNC_C or occurrence of other errors in the cells dominated by the BSC/RNC_C. In this case, execute step 709 directly.
[0056] Steps 707 - 708: the BSC/RNC_A performs an MBMS registration process which is completely the same as that shown in Figure 3, thus no further description is needed here.
[0058] As for the BSC/RNC_A or the BSC/RNC_B, the MBMS session start response message returned to the SGSN_X includes the TEID for the SGSN_X to establish the Iu bearer plane to transmit the MBMS data. Then, the BSC/RNC_A or the BSC/RNC_B will be able to establish in the MBMS service area the radio resources necessary to transmit the MBMS data to the interested UEs.
[0059] As for the BSC/RNC_C, the MBMS session start response message returned to the SGSN_X includes the information indicating the reason for not establishing the MBMS bearer plane.
[0060] Second Embodiment:
As shown in Figure 8, which is a schematic diagram for the Second Embodiment according to the present invention, illustrating the session start process of an MBMS multicast service. The difference between the First embodiment and Second embodiment is that the BSC/RNC_A performs the MBMS registration process after sending the MBMS session start response message to the SGSN_X in the Second Embodiment as shown in Figure 8 rather than before sending the MBMS session start response message to the SGSN_X in the First Embodiment as shown in Figure 7.
Third Embodiment:
[0061] As shown in Figure 9, which is a schematic diagram for the Third Embodiment according to the present invention, illustrating the session start process of an MBMS broadcast service, which includes the following steps:
Step 901: the BM-SC sends a session start request message to the GGSN in the PLMN, indicating the data transmission is to be started, and sets the state attribute of the MBMS bearer context as "activated". The session start request message provides such session attributes as QoS, MBMS service area, estimated session duration and etc. If the BM-SC does not estimate the session duration, the session start request message will not provide the session attribute of the estimated session duration.
Step 902: upon receiving the session start request message, the GGSN_X establishes an MBMS bearer context, stores the session attributes obtained from the request message in the MBMS bearer context, sets the state attribute of the MBMS bearer context as "activated", and sends a session start response message to the BM-SC.
Step 903: the GGSN_X sends an MBMS session start request message to the SGSN_X connected to the GGSN_X.
Step 904: upon receiving the MBMS session start request message, the SGSN_X establishes an MBMS bearer context, stores the session attributes in the MBMS bearer context, sets the state attribute of the MBMS bearer context as "activated", and sends an MBMS session start response message to the GGSN_X, wherein the response message provides the TEID for the bearer plane, and for the GGSN to transmit the MBMS data.
Step 905: according to the MBMS service area information in the session attributes, the SGSN_X determines the cells overlapped by the MBMS service area and dominated by the BSC/RNCs connected to the SGSN_X, and then sends an MBMS session start request message containing the session attributes to each BSC/RNC corresponding to the determined cell.
[0062] In this embodiment, among the cells dominated by the BSC/RNC_D, no cell is covered by the MBMS service area in this MBMS session, therefore, the SGSN_X sends the MBMS session start request messages to BSC/RNC_A, BSC/RNC_B and BSC/RNC_C, respectively.
[0063] Step 906: upon receiving the MBMS session start request message from the SGSN_X, the BSC/RNC_A, BSC/RNC_B or BSC/RNC_C determines whether to establish a bearer plane for the MBMS session, according to whether there is a user who needs to receive the MBMS session information and is located in one of the cells dominated by the corresponding BSC/RNC, and whether the corresponding BSC/RNC is capable of establishing the radio and cabled bearers for the MBMS session.
[0064] As for the BSC/RNC_A or BSC/RNC_B, if it decides to establish a bearer plane for the MBMS session, it will store the session attributes in the MBMS bearer context, set the state attribute of the MBMS bearer context as "activated", and then execute step 907.
[0065] As for the BSC/RNC_C, it decides not to establish a bearer plane for the MBMS session due to such reasons as no user interested in the MBMS session, radio or cabled resource insufficiency of the BSC/RNC_C or occurrence of other errors in the cells dominated by the BSC/RNC_C. In this case, execute step 907.
[0067] As for the BSC/RNC_A or the BSC/RNC_B, the MBMS session start response message returned to the SGSN_X includes the TEID for the SGSN_X to establish the Iu bearer plane to transmit the MBMS data. Then, the BSC/RNC_A or the BSC/RNC_B will be able to establish in the MBMS service area the radio resources necessary to transmit the MBMS data to the interested UEs. The BSC/RNC_A or the BSC/RNC_B will distribute the radio network resources according to the estimated session duration of the MBMS broadcast service in the session attributes together with the cooperation of the associated RRM arithmetic method.
[0068] As for the BSC/RNC_C, the MBMS session start response message returned to the SGSN_X includes the information indicating the reason for not establishing the MBMS bearer plane.
[0069] As a broadcast service will transmit information to all the users in the radio network, there is no MBMS registration process. Therefore, the main difference between the process in this embodiment and the process as shown in Figure 7 or Figure 8 is that there is no MBMS registration process for BSC/RNC_A. Meanwhile, compared with the process in the prior art as shown in Figure 5, in the session start process in this embodiment, a parameter of estimated session duration is carried for the radio access network to distribute the radio network resources.
Fourth Embodiment:
[0070] In the process according to this embodiment, for either a multicast service or a broadcast service, the SGSN_X does not determine the BSC/RNCs connected to the SGSN_X and covered by the MBMS service area. Instead, the SGSN_X sends a session start request message to each BSC/RNC connected to the SGSN_X. After receiving the session start request message, the BSC/RNC_A, the BSC/RNC_B, the BSC/RNC_C or the BSC/RNC_D will first compare the cells dominated by the corresponding BSC/RNC with those in the MBMS service area according to the session start request message, and examine whether there is an overlap.
[0071] If there is, for a multicast service, execute step 706 and the following steps as shown in Figure 7 or step 806 and the following steps as shown in Figure 8, while for a broadcast service, execute step 906 and the following steps as shown in Figure 9.
[0072] If there is not, no following steps will be executed. The BSC/RNC may further return an MBMS session response message to the SGSN to indicate the associated reason.
[0073] As shown in the above described embodiments, according to the session start method for MBMS in the present invention, the session start request messages are sent to the BSC/RNCs serving in the MBMS service area defined by this MBMS session, thus avoiding the unnecessary involvement of other unrelated BSC/RNCs. Furthermore, after the BSC/RNC decides to establish an MBMS bearer, will the BSC/RNC set the state of the bearer plane to activate and establish the bearer plane, thus optimizing the system performance, reducing the resource waste of the radio interface and lowering the complexity of the system processing. For an MBMS broadcast service, the parameter of estimated session duration is carried and used for the radio access network to distribute the radio network resources, while for an MBMS multicast service, the MBMS registration process will be initiated when the MBMS registration process is not performed, thus ensure a complete and correct implementation of the MBMS session start process.
a Broadcast/Multicast Service Center (BM-SC) initiating a session start request message via a Gateway GPRS Support Node (GGSN) to a Serving GPRS Support Node (SGSN);
receiving the MBMS session start request message, the SGSN sending the MBMS session start request message to a Base Station Controller (BSC)/Radio Network Controller (RNC);
receiving the MBMS session start request message, the BSC/RNC checking whether to establish a bearer plane for the MBMS session, if establishing, activating an MBMS bearer context and the BSC/RNC establishing radio resources to the user equipment (UE); if not establishing, the process being terminated.
the BM-SC sending the session start request message to the GGSN stored in a list of downstream node in the corresponding MBMS bearer context, and setting a state attribute of the MBMS bearer context to activate;
receiving the session start request message, the GGSN storing a session attribute obtained from the message into the MBMS bearer context, setting the state attribute of the MBMS bearer context to activate, and sending a session start response message to the BM-SC;
the GGSN sending the MBMS session start request message to the SGSN stored in the list of downstream node in the corresponding MBMS bearer context; and
receiving the MBMS session start request message, the SGSN storing the session attribute into the MBMS bearer context, setting the state attribute of the MBMS bearer context to activate, and sending an MBMS session start response message to the GGSN, wherein the session start response message providing a Tunnel End Identifier (TEID) used for the bearer plane.
the BM-SC sending the session start request message to the GGSN in the Public Land Mobile Network (PLMN), and setting a state attribute of the MBMS bearer context to activate;
receiving the session start request message, the GGSN establishing the MBMS bearer context, storing a session attribute obtained from the message into the MBMS bearer context, setting the state attribute of the MBMS bearer context to activate, and sending a session start response message to the BM-SC;
the GGSN sending the MBMS session start request message to the SGSN that is connected to the GGSN;
receiving the session start request message, the SGSN establishing the MBMS bearer context, storing the session attribute into the MBMS bearer context, setting the state attribute of the MBMS bearer context to activate, and sending a session start response message to the BM-SC, wherein the session start response message provides a TEID used for the bearer plane.
the SGSN determining, according to the MBMS service area, the BSC/RNC which is connected to the SGSN and dominates cells overlapped by the MBMS service area; and sending the MBMS session start request message to each determined BSC/RNC.
the BSC/RNC establishing the radio resources to the UE for transmitting the MBMS data according to the estimated session duration.
the BSC/RNC checking whether the cells under its domination are overlapped with the MBMS service area carried in the session start request message, if overlapped, checking whether to establish a bearer plane for the MBMS session.
the BSC/RNC sending an MBMS registration request message to the SGSN; and
receiving the MBMS registration request message, the SGSN adding the BSC/RNC to a list of downstream node in the MBMS bearer context, and returning an MBMS registration response to the BSC/RNC.