Method and Apparatus for Service Identifying and Routing in Multimedia Broadcast/Multicast Service System

Abstract

Embodiments of the present invention disclose a method and apparatus for service identifying and routing in a multimedia broadcast and multicast service (MBMS) system. The apparatus includes a radio access network equipment (RNC) and a core network equipment (CN) communicating with each other via an Iu connection; CN includes a module for service information transmission which is used to send the identity information corresponding to the service the UE joins to RNC, and RNC includes a module for service identifying and routing which is used to identify the service according to the identity information and determine the routing of the MBMS service in the non access stratum. RNC obtains the identity information corresponding to the service the UE joins through interaction of interface information with CN, identifies the service and determines the routing of the MBMS service in the non access stratum.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows the system architecture of MBMS defined by 3GPP;

FIG. 2 is the flowchart of the MBMS multicast mode;

FIG. 3 is the flowchart of the MBMS broadcast mode;

FIG. 4 is a schematic diagram illustrating the use of NSAPI;

FIG. 5 is the flowchart of UTRAN obtaining from CN the list of services a UE joins without PS connection;

FIG. 6 is the flowchart of UTRAN obtaining from CN the list of services a UE joins with PS connection;

FIG. 7 is the flowchart of the first embodiment in accordance with an embodiment of this invention in which CN informs RNC and UE of the NSAPI without an Iu connection of PS domain;

FIG. 8 is the flowchart of the fourth embodiment in accordance with an embodiment of this invention in which CN informs RNC and UE of the NSAPI with an Iu connection of PS domain;

FIG. 9 is a schematic diagram illustrating the structure of the apparatus for service identifying and routing in an MBMS system in accordance with an embodiment of this invention.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENT

In order to make clearer the objectives, solution, and merits of this invention, a detailed description is hereinafter given to the embodiments with reference to the accompanying drawings.

The core of the solution in accordance with the embodiment is as follows: CN, via an Iu procedure, not only informs the RNC of the list of services UE joins, but also sends the identity information corresponding to service (NSAPI, TI or RAB ID). RNC and UE lookup the related PDP context in NAS according to the identity information and implement the routing. The step of obtaining identity information may be performed before RNC determines the bearer mode, or after RNC has determined the bearer mode such that only the identity information corresponding to the services adopting the PTP bearer mode needs to be obtained.

The identity information in this embodiment may include NSAPI or TI or RAB ID, and the NSAPI mentioned in this invention may be replaced by TI or RAB ID. This invention is applicable to such systems as GSM, WCDMA, CDMA 2000, etc. and herein is described by taking WCDMA system as an example. It can be easily seen by persons skilled in the art that UTRAN mentioned in this invention may correspond to RAN in other radio communication systems and RNC in this invention may correspond to BSC in other radio communication systems.

Since routing in NAS through NSAPI is in accordance with the prior art, description of this invention is focused on the method for obtaining NSAPI.

There are two circumstances in which NSAPI is obtained: one is that there is no Iu connection in the PS domain, then it is needed to inform UE of the NSAPI through an approach without connection; the other is that there is MBMS connection, then it is needed to inform UE of the NSAPI through a UE linking procedure.

Next, the solution in accordance with this invention is described with reference to specific embodiments.

FIG. 7 is the flowchart of the first embodiment in accordance with this invention. As shown in FIG. 7, a method for informing RNC and UE of the NSAPI when there is no Iu connection in the PS domain is presented, including the steps of:

Step 710: UE sets up a CS connection with an MSC of the core network, i.e. sets up an Iu connection in the CS domain so as to implement signaling connection between the UE and the MSC. At this time, Iu of the UE in the PS domain is in the PMM-IDLE state, i.e. there is no signaling connection in the Iu-PS interface at this time.

Step 720: RNC sends, in the non-connection mode (i.e. in the mode without connection in the PS domain), to SGSN in the CN the request for the list of services this UE joins and the NSAPI corresponding to the service. This request message includes MBMS SERVICE INFO REQ, which contains at least the identity of this UE. This identity herein is the IMSI of the UE.

Step 730: After receiving the message of MBMS SERVICE INFO REQ, SGSN searches in its own service database according to the IMSI in the received message, obtains all the lists of service the UE corresponding to the IMSI joins and the NSAPI corresponding to the services, and returns to RNC the message of MBMS SERVICE INFO RESPONSE, which includes all the found lists of service the UE corresponding to the IMSI joins and the NSAPI corresponding to the services as well as the IMSI of the UE.

RNC obtains the NSAPI by reading the message of MBMS SERVICE INFO RESPONSE, identifies the service according to the NSAPI, and matches the service with an appropriate PDP context in the NAS using the NSAPI, thus implementing the routing. RNC can inform the UE of the obtained NSAPI through the interface Uu, UE then can also identify the service according to the NSAPI, match the service with the appropriate PDP context in the NAS using the NSAPI, and thereby implement the routing.

In accordance with this embodiment, RNC may use other identifications of UE other than IMSI when obtaining service information, e.g. using TMSI (Temperate Mobile Subscription Identity) or URNTI instead of the above IMSI.

The second embodiment of this invention has the same procedure as the above first embodiment while the distinction between the two is as follows: The request message sent by RNC to SGSN in step 720 is used in requesting the list of services the UE joins and the RAB ID corresponding to the services; and in step 730, SGSN searches in its own service database according to the UE identity, obtains all the lists of service the UE corresponding to this UE identity joins and the RAB ID corresponding to the services, and returns to RNC all the found lists of service the UE joins and the RAB ID information corresponding to the services; RNC then informs the UE in turn. Likewise, RNC and UE may match the service with an appropriate PDP context in the NAS according to the RAB ID, and thereby implement the routing.

The third embodiment of this invention has the same procedure as the above first embodiment while the distinction between the two is as follows: The request message sent by RNC to SGSN in step 720 is used in requesting the list of services the UE joins and the TI information corresponding to the service; and in step 730, SGSN searches in its own service database according to the UE identity, obtains all the lists of service the UE corresponding to this UE identity joins and the TI information corresponding to the services, and returns to RNC all the found lists of service the UE joins and the TI information corresponding to the services; RNC then informs the UE in turn. Likewise, RNC and UE may match the service with an appropriate PDP context in the NAS according to the TI information, and thereby implement the routing.

FIG. 8 is the flowchart of the fourth embodiment in accordance with this invention. As shown in FIG. 8, in the fourth embodiment of this invention, RNC and UE are informed of NSAPI when there is a PS connection (i.e. there is an MBMS connection). Since there is an Iu-PS connection for signaling connection in this embodiment, RAN sends the NSAPI of UE using a UE Linking procedure, which includes the steps of:

Step 801: UE initiates a procedure of setting up PMM connection to CN via RNC. By the procedure of setting up PMM connection, CN can obtain the identity information of the UE, e.g. the IMSI, TMSI, or URNTI of the UE.

Step 802: CN (specifically, SGSN in CN) searches the database according to the identity information of the UE, determines the information of all the lists of service this UE joins and the identity information corresponding to the services, i.e. NSAPI, and then notifies RNC of the lists of service the UE joins and the corresponding NSAPI through a special Iu procedure, i.e. through the signaling of MBMS UE LINKING REQUEST.

Step 803: After receiving the signaling of MBMS UE LINKING REQUEST, RNC returns to CN a signaling of MBMS UE LINKING RESPONSE, informing CN that the list of services the UE joins and the corresponding NSAPI have been obtained, and informs the UE of the NSAPI.

RNC obtains the NSAPI by reading the signaling of MBMS UE LINKING RESQUEST, identifies the service according to the NSAPI, and matches the service with an appropriate PDP context in the NAS using the NSAPI, thus implementing the routing. RNC can inform the UE of the obtained NSAPI through the interface Uu, UE then can also identify the service according to the NSAPI, match the service with the appropriate PDP context in the NAS using the NSAPI, and thereby implement the routing.

The fifth embodiment of this invention has some changes from the fourth embodiment, i.e. in step 802, the identity information includes the RAB ID corresponding to the service; and likewise, RNC and UE can identify a service according to RAB ID, match the service with an appropriate PDP context in the NAS, and thereby implement the routing.

Similar to the fifth embodiment, the sixth embodiment of this invention has some changes from the fourth embodiment, i.e. in step 802, the identity information includes the TI information corresponding to the service; and likewise, RNC and UE can identify a service according to TI information, match the service with an appropriate PDP context in the NAS, and thereby implement the routing.

In the above six embodiments, the list of services UE joins and the identity information corresponding to the service are obtained at the same time. In the seventh embodiment, the process of obtaining the list of services UE joins and the process of obtaining the identity information corresponding to the service are carried out separately, and the specific obtaining processes are the same as the above six embodiments except for the contents obtained.

As the process of obtaining the identity information corresponding to the service in the above six embodiments are carried out at the same time as the process of obtaining the list of services UE joins and the procedure of obtaining the list of services UE joins is categorized as a counting procedure, it means that the list of service and the corresponding identity information are obtained before RNC decides the bearer mode to be used.

The eighth embodiment of this invention has changed from the first six embodiments: the identity information may also be obtained after RNC has decided the bearer mode to be used. Then for the services adopting the PTP bearer mode, the identity information, NSAPI or TI or RAB ID, corresponding to service is obtained through a special Iu procedure, which is as follows: To obtain the list of services UE joins through the MBMS SERVICE ID REQUEST (without PS connection) procedure in the prior art, and after RNC has decided the bearer mode of the cell, obtain the NSAPI or TI or RAB ID of various lists of service through a special Iu procedure for the services adopting the PTP bearer mode. This special Iu procedure is similar to the first, second, and third embodiments except for the distinction that the MBMS SERVICE INFO REQ is used in requesting the identity information corresponding to the service the UE joins and the MBMS SERVICE INFO RESPONSE is used in returning to RNC the identity information corresponding to the service the UE joins.

Obtain the list of services UE joins through the UE LINKING (with PS connection) procedure in the prior art, and after RNC has decided the bearer mode of the cell, obtain the identity information, NSAPI or TI or RAB ID, corresponding to the service through a special Iu procedure for the services adopting the PTP bearer mode. This special Iu procedure is similar to the fourth, fifth, and sixth embodiments except for the difference that the MBMS UE LINKING REQUEST is used in returning the identity information corresponding to the service the UE joins.

Based on the foregoing method, this invention presents an apparatus for service identifying and routing in an MBMS system as well, the structure of which is shown in FIG. 9. As shown in FIG. 9, the apparatus includes: an RAN device (e.g. RNC) 91 and a CN device (e.g. SGSN) 92 communicate with each other through Iu interface. The distinction from the prior art lies in that the CN device further includes a module for service information transmission 921 which is used in sending to the RAN device the identity information (e.g. NSAPI, RAB ID, or TI) corresponding to the service UE joins and the RAN device further includes a module for service identifying and routing 911 which is used in identifying a service according to the identity information and determining the routing of the MBMS service in the non access stratum.

The apparatus further includes a sub-module for UE link processing 922; when there is an Iu connection of PS domain in the Iu interface between the RAN device and the CN device, the module for service information transmission sends the identity information to the CN device using the sub-module for UE link processing 922.

The apparatus further includes a sub-module for MBMS service information processing 923; when there are only Iu connections of CS domain in the Iu interface between the RAN device and the CN device, the module for service information transmission sends the identity information to the CN device using the sub-module for MBMS service information processing 922.

In addition, the module for service information transmission 921 is further used in sending to the RAN device the information of list of service UE joins; and is also further used in sending to the RAN device the identity information of UE (e.g. IMSI, TMSI, or URNTI).

The foregoing description is only preferred embodiments of this invention and should not be construed as limiting the protection scope thereof. Any changes or substitutions within the technical scope disclosed by this invention which are easily known to people skilled in the art should be covered by the protection scope of this invention.

Claims

1. A method for service identifying and routing in a multimedia broadcast and multicast service (MBMS) system, comprising the steps of: a radio access network (RAN) device obtaining identity information corresponding to a service that a user equipment (UE) joins, through interaction of interface information with a core network (CN);the RAN device identifying the service according to the identity information, and determining a route of the MBMS service in the non access stratum.

2. The method according to claim 1, wherein the identity information corresponding to the service comprises the network service access point identifier (NSAPI).

3. The method according to claim 1, wherein the identity information corresponding to the service comprises the radio access bearer identity (RAB ID).

4. The method according to claim 1, wherein the identity information corresponding to the service comprises the transaction identity (TI).

5. The method according to claim 1, wherein, if there is an Iu connection of a Packet Switching (PS) domain on the UE, the RAN device obtains the identity information corresponding to the service the UE joins through a UE Linking procedure.

6. The method according to claim 1, wherein, if there is an Iu connection of a Circuit Switching (CS) domain on the UE, the RAN device obtains the identity information corresponding to the service the UE joins through a MBMS service information requesting procedure.

7. The method according to claim 1, further comprising: the RAN device obtaining a list of services the UE joins through the interaction of interface information with the core network.

8. The method according to claim 7, wherein, the procedure of the RAN device obtaining the list of services the UE joins and the procedure of the RAN device obtaining the identity information corresponding to the service are carried out separately.

9. The method according to claim 7, wherein, the procedure of the RAN device obtaining the list of services the UE joins and the procedure of the RAN device obtaining the identity information corresponding to the service are carried out simultaneously.

10. The method according to claim 1, wherein the step of the RAN device obtaining the identity information corresponding to the service from the CN is performed before the RAN device determines the radio bearer mode of the service.

11. The method according to claim 1, wherein the step of the RAN device obtaining the identity information corresponding to the service from the CN is implemented after the RAN device has obtained the list of services the UE joins from the CN and has determined the radio bearer mode of the service.

12. The method according to claim 11, wherein after the RAN device has obtained the list of services the UE joins from the CN and has determined the radio bearer mode of the service, the RAN device obtains the identity information corresponding to the services using the PTP bearer mode from the CN.

13. The method according to claim 1, further comprising: the RAN device informing the UE of the identity information corresponding to the service, the UE identifying the service according to the identity information and the RAN device determining the route of the MBMS service in the non access stratum.

14. The method according to claim 1, wherein the RAN device is a radio network controller (RNC).

15. The method according to claim 1, wherein the RAN device obtains the identity information of the UE while obtaining the identity information corresponding to the service from the CN.

16. The method according to claim 15, wherein the identity information of UE comprises International Mobile Station Identity.

17. The method according to claim 15, wherein the identity information of UE comprises Temporary Mobile Subscriber Identity.

18. The method according to claim 15, wherein the identity information of UE comprises Radio Network Temporary Identity (URNTI).

19 . An apparatus for service identifying and routing in a multimedia broadcast and multicast service (MBMS) system, comprising: a radio access network (RAN) device and a core network (CN) device communicating with each other via Iu connection, wherein the CN device further comprises a module for service information transmission that is used to send the identity information corresponding to the service a UE joins to the RAN device; and the RAN device further comprises a module for service identifying and routing that is used to identify a service according to the identity information and determine a route of MBMS in a non access stratum.

20. The apparatus according to claim 19, further comprising a sub-module for UE link processing, wherein, if there is an Iu connection of a Packet Switching (PS) domain in the Iu connections between the RAN device and the CN device, the module for service information transmission sends the identity information to the CN device using the sub-module for UE link processing.

21. The apparatus according to claim 19, further comprising a sub-module for MBMS service information processing, wherein, if there is an Iu connection of a Circuit Switching (CS) domain in the Iu connection between the RAN device and the CN device, the module for service information transmission sends the identity information to the CN device using the sub-module for MBMS service information processing.

22. The apparatus according to claim 19, wherein the module for service information transmission is further used to send a list of services the UE joins to the RAN device.

23. The apparatus according to claim 19, wherein the RAN device is a radio network controller.

24. The apparatus according to claim 19, wherein the CN device is a Serving GPRS Support Node.

25. The apparatus according to claim 19, wherein the identity information corresponding to service comprises a network service access point identifier (NSAPI).

26. The apparatus according to claim 19, wherein the identity information corresponding to service comprises a radio access bearer identity (RAB ID).

27. The apparatus according to claim 19, wherein the identity information corresponding to service comprises a transaction identity (TI).

28. The apparatus according to claim 19, wherein the module for service information transmission is further used to send the identity information of UE to the RAN device.

29. The apparatus according to claim 28, wherein the identity information of UE comprises International Mobile Station Identity.

30. The apparatus according to claim 28, wherein the identity information of UE comprises Temporary Mobile Subscriber Identity.

31. The apparatus according to claim 28, wherein the identity information of UE comprises URNTI.