WO2004043024A1 - Method for supporting multicast broadcast/multicast service to employ shared iu signaling connection - Google Patents

Method for supporting multicast broadcast/multicast service to employ shared iu signaling connection Download PDF

Info

Publication number
WO2004043024A1
WO2004043024A1 PCT/KR2003/002358 KR0302358W WO2004043024A1 WO 2004043024 A1 WO2004043024 A1 WO 2004043024A1 KR 0302358 W KR0302358 W KR 0302358W WO 2004043024 A1 WO2004043024 A1 WO 2004043024A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
rnc
sgsn
relocation
mbms service
Prior art date
Application number
PCT/KR2003/002358
Other languages
French (fr)
Inventor
Sung-Ho Choi
Kook-Heui Lee
Qinghai Gao
Detao Li
Lixiang Xu
Original Assignee
Samsung Electronics Co., Ltd.
Beijing Samsung Telecom R & D Center
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Samsung Electronics Co., Ltd., Beijing Samsung Telecom R & D Center filed Critical Samsung Electronics Co., Ltd.
Publication of WO2004043024A1 publication Critical patent/WO2004043024A1/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup
    • H04W76/12Setup of transport tunnels
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/02Details
    • H04L12/16Arrangements for providing special services to substations
    • H04L12/18Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/0005Control or signalling for completing the hand-off
    • H04W36/0007Control or signalling for completing the hand-off for multicast or broadcast services, e.g. MBMS
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/12Reselecting a serving backbone network switching or routing node
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/02Details
    • H04L12/16Arrangements for providing special services to substations
    • H04L12/18Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/189Arrangements for providing special services to substations for broadcast or conference, e.g. multicast in combination with wireless systems
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services

Definitions

  • This invention relates to a method of how the procedurees related with RANAP message and lu interface supporting MBMS service to employ shared signaling connection on lu interface in a mobile communication system.
  • MBMS Multicast Broadcast Multicast Service
  • 3GPP 3 rd Generation Partnership Project
  • the standard under development is TR23.846, and the latest version is 1.0.0.
  • MBMS service is a unidirectional point-to-multipoint (p-t-m) service, and its most remarkable characteristic is that it can make use of radio resources and network resources efficiently.
  • FIG. 1 describes MBMS architecture.
  • MBMS architecture is based on Core Network of General Packet Radio Service (hereinafter referred to as GPRS), and has added new network units.
  • GPRS General Packet Radio Service
  • the MBMS architecture as shown in Figure 1 is described below.
  • Broadcast/Multicast Service Center (referred to as BM-SC) 101 is the service control center of MBMS system.
  • the transmission network of MBMS service is composed of Gateway GPRS Supporting Node 102 (hereinafter referred to as GGSN) and Service GPRS Supporting Node 103 (hereinafter referred to as SGSN), providing routes for data transfer.
  • Home Location Register 106 (hereinafter referred to as HLR) saves the data related with users and can provide services such as user's authentication.
  • UTRAN UMTS Terrestrial Radio Access Network 104
  • Iu 107 indicates the interface between Access Network and Core Network.
  • User Equipment (hereinafter referred to as UE) 105 is a terminal device used to receive data. Radio resources used by MBMS service are not dedicated for one user, but are shared by all users using this service.
  • Figure 2 is the corresponding signaling flow. Each step of the flow is described in detail as follows.
  • a source RNC decides to execute SRNS relocation procedure.
  • the source RNC sends a "Relocation Required” message to an original SGSN.
  • the original SGSN forwards a "Relocation Request” message to a new SGSN.
  • the new SGSN sends the "Relocation Request” message to a target RNC and a radio access bearer (hereinafter referred to as RAB) is established between the target RNC and the new SGSN. After the resources needed by RAB including resources on the user plane are allocated successfully, the target RNC sends a "Relocation Request Acknowledge" message to the new SGSN.
  • RAB radio access bearer
  • the new SGSN forwards a "Relocation Response" message to the original SGSN.
  • the original SGSN sends a "Relocation Command" message to the source RNC.
  • IP layer network protocol layer
  • the source RNC sends a "Relocation Commit" message to the target RNC, which is used to transmit SRNS Context to the target RNC and the role of SRNS converts from source RNC to target RNC.
  • the target RNC When the target RNC receives the trigger message for executing relocation, it sends a "Relocation Detection" message to the new SGSN. Thereafter, the target RNC starts to play the role of Serving Radio Network Controller (hereinafter referred to as SRNC). 210 UE exchanges mobility-related information, such as new SRNC Identity, expression of location area and upstream user data, with the target RNC.
  • SRNC Serving Radio Network Controller
  • the new SGSN sends an "Update Packet Data Protocol (hereinafter referred to as PDP) Context Request" message to the corresponding GGSN after receiving the "Relocation Detection” message.
  • PDP Packet Data Protocol
  • GGSN updates PDP context and returns an "Update PDP Context Response” message.
  • the new SGSN examines each MBMS service in MBMS Context of UE. If a certain service is joined by UE in SGSN for the first time, a GPRS Tunnel Protocol (hereinafter referred to as GTP) tunnel is established between SGSN and GGSN, and MBMS Context is created at GGSN.
  • GTP GPRS Tunnel Protocol
  • the target SRNC initiates a Relocation Complete procedure after receiving an "UTRAN Mobility Information Confirm" message.
  • the new SGSN sends a "Relocation Complete” message to notify the original SGSN of the completion of the SRNS relocation procedure.
  • 213 Release an lu connection between the source RNC and the source SGSN as well as user resources.
  • RAI Route Area Indication
  • CAMEL Customized Applications for Mobile network Enhanced Logic
  • the "RAB Assignment Request” message includes information on the following several aspects: - RABs To Be Setup Or Modified List: information such as RAB Identity (ID) to be setup or modified, RAB parameters on user plane, etc.
  • This message is connection-oriented. There is no identity of information element UE being included in the message. Similarly, messages of "RAB Assignment Response" and "Initial UE Information” also don't include identity of UE. SGSN and RNC may get UE information according to lu connection identity.
  • the Relocation Request message includes information on the following several aspects:
  • this information element indicates whether the execution of SRNS relocation is related with UE.
  • Source ID indicates the source of SRNC relocation.
  • Target ID indicates the target ID of SRNC relocation, which might be either an ID of target RNC, or a global Cell ID of target cell (in the case of relocating from UMTS to GSM).
  • Source RNC To Target RNC Transparent Container includes parameters such as encryption information, cell load information and mapping relation between Radio Access Bearer (RAB) and transmission channel.
  • RAB Radio Access Bearer
  • - Old BSS To New BSS Information information created by Source RNC and transferred to Target RNC, includes password index, RAB information, transmission channel information as the like.
  • the Relocation Command message includes information on the following several aspects:
  • Target RNC To Source RNC Transparent Container includes parameters such as encryption information, cell load information and mapping relation between Radio Access Bearer (RAB) and transport channel.
  • RAB Radio Access Bearer
  • - Inter-System Information Transparent Container includes temporary ID of transmission network and radio resource control information.
  • RAB Radio Access Bearer
  • RNC Network Controller
  • CN Network Controller
  • SCCP Signaling Connection Control Part
  • RNC initiates an establishment of SCCP signaling connection
  • RNC When RNC receives a non-access stratum message from UE for the first time, and if there is no lu connection for this UE, RNC initiates the procedure of SCCP connection establishment. RNC sends a "SCCP Connection Request" message including one RANAP message in its data field to CN.
  • CN initiates an establishment of SCCP signaling connection when executing relocation. CN initiates an establishment of lu connection by sending a
  • SCCP Connection Request message to RNC, and the data field of the "SCCP Connection Request” includes a RANAP message (optional).
  • RNC When RNC decides to execute SRNS relocation procedure, it sends a "Relocation Required" message to a Source SGSN. However, since there is no ID of UE in the "Relocation Required” message, if the message is sent through the shared lu connection of certain MBMS service that UE receives, SGSN will not know the "Relocation Required” message comes from which UE. Other RANAP messages, such as "Relocation Command”, “RAB Assignment Request”, “RAB Assignment Response”, "Initial UE Information” and “Direct Transfer” will encounter the same problem of RNC or SGSN unable to identify when sending through a shared lu connection. lu release procedure is used to release lu signaling connection as well as
  • UTRAN resources related with this signaling connection During relocation procedure, if the moving UE is not the unique user of certain MBMS service, after SGSN sends a "lu Release Command" to a Source RNC, it will release the shared connection as well as user plane resources for MBMS. This is unreasonable, and it should be that transmitting proper message will only release UTRAN resources related with the moving user.
  • RNC In the conditions of existing SCCP connection establishment: when RNC receives a non-access stratum message from UE for the first time, if there is no lu connection for this UE, RNC initiates the procedure of SCCP connection establishment. If UE has upstream non-MBMS data necessary for being transmitted while receiving MBMS service, it will send a Service Request message to RNC. According to above described conditions for SCCP connection establishment, RNC will initiate a procedure to setup dedicated lu connection for the UE. This is true if a plurality of UEs receiving a same kind of MBMS service, dedicated lu connections will be setup for a plurality of UEs, which is contradict with the shared lu connection mode. CN initiates an establishment of SCCP signaling connection when executing relocation.
  • CN initiates an lu signaling connection establishment procedure by sending a "SCCP Connection Request" message to RNC. If a shared lu connection for certain MBMS service has been setup between a target RNC and a new SGSN when UE moves to the RNC, then it is unnecessary to setup a dedicated lu connection for the UE. So it is necessary to modify the existing conditions of SCCP connection establishment.
  • the object of the present invention is to provide a method that can support to use shared lu signaling connection for MBMS service in a mobile communication system by modifying existing specifications (e.g. message, flow).
  • a method of supporting MBMS service to employ shared lu signaling connection comprises:
  • RNC checks whether the UE receives MBMS service or not, when forwarding the non-access stratum message "Service Request" of the UE to
  • the SGSN and if there is a shared lu connection for the UE to receive certain MBMS service, don't initiate a SCCP Connection Establishment procedure, and the RNC forwards the non-access stratum message of the UE through the shared lu connection to the SGSN; (d) After receiving the "Service Request" message, in the case where the service request is accepted, the SGSN returns a "Service Acceptance" message to MS;
  • the SGSN sends an "RAB Assignment Request” message to the RNC through the shared lu connection for receiving certain MBMS service by the
  • the RNC allocates resources and sends an "RAB Assignment Response” message through the shared lu connection, and adding an information element, i.e. Permanent NAS UE Identity, to existing message "RAB Assignment Response" for identifying the UE in UTRAN and CN;
  • the SGSN receives the "RAB Assignment Response” message from the RNC and knows that the corresponding user plane bearer establishment for UE has been completed according to ID of the UE in this message.
  • This invention makes WCDMA system able to support shared lu connection mode for MBMS service. It solves the problem of user mobility caused by shared connection being employed for MBMS service on lu interface, and at the same time, solves the problem of how MBMS shared lu signaling connection provides service for UE dedicated non-MBMS service in WCDMA system. Modifications for the specification made in the invention will not affect the existing functions of the system. It keeps backward compatibility.
  • Figure 1 is a schematic diagram of MBMS system architecture
  • Figure 2 shows the existing SRNS relocation procedure
  • Figure 3 shows SRNS relocation procedure that supports shared lu connection
  • Figure 4 is the procedure of MBMS shared lu signaling connection serving UE dedicated non-MBMS service.
  • a new information element i.e. Permanent NAS UE Identity
  • Permanent NAS UE Identity is added to this message for identifying UE in UTRAN and CN.
  • SGSN finds other signaling connections (e.g. shared lu signaling connections that other UEs can use) that have been save by this information element.
  • This parameter uses the type of International Mobile User Identity (hereinafter referred to as IMSI). This parameter is optional. For UEs that don't receive MBMS service, this message is transferred through UE dedicated lu; while for UEs that receive MBMS service, this message is transferred through shared lu connection. This parameter is meaningful.
  • an information element i.e. Permanent NAS UE Identity
  • RNC finds other signaling connections (e.g. RRC signaling connection or other shared lu signaling connection that other UEs can use) that have been save by this information element.
  • This parameter is the type of IMSI.
  • an information element i.e. Permanent NAS UE Identity shall be added to RAB
  • RNC and SGSN can then distinguish which UE the operation of RAB establishing, modifying or releasing will be performed for.
  • Initial UE Information and Direct Transfer message shall also be added with an information element, i.e. Permanent NAS UE Identity.
  • SGSN finds that a moving user is the last user leaving or quitting a certain MBMS service, it sends an "lu Release Command" message to a Source RNC for requesting to release a certain shared lu connection and UTRAN resources related with this connection. If the moving user is the last user of several MBMS services between SGSN and RNC, SGSN needs to send the "lu Release Command" message to Source RNC repeatedly.
  • SGSN needs to send an "RAB Assignment Request" message to RNC for releasing a non-MBMS RAB for this user.
  • RNC decides to perform different operations according to a message received:
  • RNC receives an "lu Release Command” from SGSN, it releases an lu connection and relevant resources and then returns an "lu Release Complete” message to SGSN.
  • RNC receives an "RAB Assignment Request” message, it releases RAB indicated in the message for the UE according to ID of UE, i.e. Permanent NAS UE Identity, in the message, and returns a "RAB Assignment Response” message to SGSN.
  • a Target RNC receives a "Relocation Request” message from a new SGSN, according to MBMS context in the message, it sends a "MBMS Service Request” message to the new SGSN to request for a certain MBMS service, if the Target RNC hasn't yet joined in the service used by UE. If the Target RNC hasn't yet joined in several MBMS services used by UE, it is necessary to send this message repeatedly for several times.
  • the trigger condition of existing SCCP connection establishment is modified as follows:
  • RNC initiates an establishment of SCCP signaling connection
  • RNC When RNC receives a Non-Access Stratum (NAS) message transmitted from UE for the first time, if there is neither lu connection for this UE nor shared lu connection for UE to receive MBMS service, RNC initiates a NAS message transmitted from UE for the first time, if there is neither lu connection for this UE nor shared lu connection for UE to receive MBMS service, RNC initiates a NAS (NAS) message transmitted from UE for the first time, if there is neither lu connection for this UE nor shared lu connection for UE to receive MBMS service, RNC initiates a NAS (NAS) message transmitted from UE for the first time, if there is neither lu connection for this UE nor shared lu connection for UE to receive MBMS service, RNC initiates a NAS message transmitted from UE for the first time, if there is neither lu connection for this UE nor shared lu connection for UE to receive MBMS service, RNC initiate
  • RNC sends a "SCCP Connection Request" message including one RANAP message in its data field to CN.
  • CN When CN performs relocation, if UE hasn't received MBMS service or there is no shared signaling connection for UE to receive MBMS service between RNC and SGSN, then CN initiates an establishment of SCCP signaling connection. CN initiates the establishment of lu connection by sending a "SCCP Connection Request" message to RNC, whose data field includes one RANAP message (optional).
  • CN will not initiate the procedure of SCCP connection establishment.
  • SRNS relocation procedure is shown in Figure 3. Each step is described in detail as followings:
  • a Source RNC decides to perform SRNS relocation procedure; 302
  • the Source RNC constructs a "Relocation Required" message, if a lu connection dedicated for UE exists (UE doesn't receive MBMS service), then directly sends the message to SGSN. If the UE is receiving the MBMS service, then there is no dedicated lu connection for the UE, and the message is sent to SGSN through the shared lu connection for UE to receive a certain MBMS service.
  • Information elements of the Relocation Required message include Permanent NAS UE Identity. According to ID of the UE, SGSN can get known which UE has roamed.
  • An Original SGSN forwards a "Relocation Request” message including MBMS Context to a new SGSN.
  • the New SGSN sends a "Relocation Request” message to a Target RNC.
  • SGSN initiates a SCCP Signaling Connection Establishment procedure during sending the "Relocation Request" message.
  • SGSN initiates an establishment of lu connection by sending a "SCCP Connection Request" message to RNC, whose data field includes one RANAP message (optional).
  • RNC Radio Network Controller
  • the target RNC If the target RNC hasn't joined in a corresponding service, it sends a "MBMS Service Request" message to SGSN.
  • Radio access bearer including RABs of MBMS is established between the target RNC and the new SGSN.
  • the target RNC sends a "Relocation Request Acknowledge" message to the new SGSN.
  • Information elements of the "Relocation Request Acknowledge” message include Permanent NAS UE Identity.
  • the new SGSN forwards the "Relocation Response" to the original
  • the original SGSN sends a "Relocation Command" message including information element Permanent NAS UE Identity to the Source RNC.
  • IP layer network protocol layer
  • the source RNC sends "Relocation Commit" to the target RNC. This procedure is used to transmit SRNS Context to the target RNC and the role of SRNS converts from the source RNC to the target RNC.
  • the target RNC When the target RNC receives a trigger message for performing relocation, it sends a "Relocation Detect" message to the new SGSN, the
  • Relocation Detect message includes information element, Permanent NAS UE Identity. After that, the target RNC starts to play the role of Serving Radio Network Controller (hereinafter referred to as SRNC).
  • SRNC Serving Radio Network Controller
  • 313 UE exchanges mobility-related information, such as new SRNC Identity, expression of location area and upstream user data, with the target RNC.
  • mobility-related information such as new SRNC Identity, expression of location area and upstream user data, with the target RNC.
  • the new SGSN sends an "Update Packet Data Protocol (hereinafter referred to as PDP) Context Request" message to the corresponding GGSN after receiving the "Relocation Detection” message.
  • PDP Packet Data Protocol
  • GGSN updates PDP context and returns an "Update PDP Context Response” message.
  • the new SGSN examines each MBMS service in MBMS Context of UE. If a certain service is joined by UE in SGSN for the first time, a GTP tunnel is established between SGSN and GGSN, and MBMS Context is created at GGSN.
  • the target SRNC initiates a Relocation Complete procedure after receiving a "UTRAN Mobility Information Confirm" message.
  • the new SGSN sends the "Relocation Complete” message to notify the original SGSN of the completion of SRNS relocation procedure, and the original SGSN returns a "Relocation Complete Acknowledge” message.
  • 317 Release relevant resources between the Source RNC and the Source SGSN.
  • the shared connection and user plane resources corresponding to MBMS service shall be released.
  • SGSN sends an "lu Release Command" message to the Source RNC for requesting RNC to release a corresponding lu connection and UTRAN resources related with this connection; the Source RNC releases corresponding resources and sends an "lu Release Complete” message to SGSN.
  • the UE is the last user of the source RNC for several services, then above release procedure is performed for several times.
  • SGSN sends an "RAB Assignment Request” message to RNC for releasing non-MBMS RAB of this user.
  • the Source RNC releases corresponding resources and sends an "RAB Assignment Response" message to SGSN.
  • These two messages both include information element Permanent NAS UE Identity. RNC and SGSN may get known which user's RAB should be released.
  • the moving user is not the last user that receives MBMS service and the user doesn't receive other non-MBMS service than MBMS service, this step is unnecessary.
  • RAI Route Area Indication
  • MS Since an RRC connection has been existed, MS has upstream data of non-MBMS service to be sent, and constructs a "Service Request" message.
  • the service 403 MS sends the "Service Request” message to SGSN for requesting SGSN to reserve resources.
  • the service type parameter of "Service Request” message shall be set as data.
  • SGSN In the case where the service request is accepted, SGSN returns a "Service Acceptance" message to MS. For the UE receiving MBMS service, this message is sent through the shared lu signaling connection.
  • RNC 406 SGSN sends an "RAB Assignment Request" message to RNC through the shared lu connection used for UE receiving a certain MBMS service for requesting the establishment of RAB.
  • a new information element, i.e. Permanent NAS UE Identity, included in the message "RAB Assignment Request" is used to identify UE in UTRAN and CN.
  • RNC finds other signaling connections (e.g. shared lu signaling connections that other UEs can use) that have been save by this information element.
  • RNC sends an "Establishment of RB" message to MS for notifying MS of that new establishment of RAB ID request establishment of radio resources.
  • RNC returns an "RAB Assignment Response" to SGSN through the shared lu signaling connection, which indicates the completion of user plane bearer establishment.
  • the message includes information element Permanent NAS UE Identity.
  • SGSN For each Re-established RAB by using modified QoS, SGSN initiates a "PDP Context Modification" procedure to notify MS and GGSN of corresponding to the new negotiated QoS of PDP Context. 411 MS sends upstream data packets.

Abstract

A method of supporting MBMS service to employ shared Iu signaling connection comprises: UE has non-MBMS service necessary for being transmitted while receiving MBMS service; The UE sends a non-access stratum message 'Service Request' to SGSN; RNC checks whether the UE receives MBMS service or not, and the RNC forwards the non-access stratum message of the UE through the shared Iu connection to the SGSN; After receiving the 'Service Request' message, in the case where the service request is accepted, the SGSN returns a 'Service Acceptance' message to MS; The SGSN sends an 'RAB Assignment Request' message for identifying the UE in UTRAN and CN to the RNC; The RNC allocates resources and sends an 'RAB Assignment Response' message to existing message 'RAB Assignment Response'; The SGSN receives the message from the RNC and knows the corresponding user plane bearer establishment for UE has been completed.

Description

METHOD FOR SUPPORTING MULTICAST BROADCAST/MULTICAST SERVICE TO EMPLOY SHARED IU SIGNALING CONNECTION
BACKGROUND OF THE INVENTION
1. Field of invention
This invention relates to a method of how the procedurees related with RANAP message and lu interface supporting MBMS service to employ shared signaling connection on lu interface in a mobile communication system.
2. Description of prior art
Multicast Broadcast Multicast Service (hereinafter referred to as MBMS) is a new service under standardization by 3rd Generation Partnership Project (hereinafter referred to as 3GPP). The standard under development is TR23.846, and the latest version is 1.0.0. MBMS service is a unidirectional point-to-multipoint (p-t-m) service, and its most remarkable characteristic is that it can make use of radio resources and network resources efficiently.
In order to explain this invention, Figure 1 describes MBMS architecture. MBMS architecture is based on Core Network of General Packet Radio Service (hereinafter referred to as GPRS), and has added new network units. The MBMS architecture as shown in Figure 1 is described below. Broadcast/Multicast Service Center (referred to as BM-SC) 101 is the service control center of MBMS system. The transmission network of MBMS service is composed of Gateway GPRS Supporting Node 102 (hereinafter referred to as GGSN) and Service GPRS Supporting Node 103 (hereinafter referred to as SGSN), providing routes for data transfer. Home Location Register 106 (hereinafter referred to as HLR) saves the data related with users and can provide services such as user's authentication. UMTS Terrestrial Radio Access Network 104 (hereinafter referred to as UTRAN) provides radio resources for MBMS service over the air-interface. Iu 107 indicates the interface between Access Network and Core Network. User Equipment (hereinafter referred to as UE) 105 is a terminal device used to receive data. Radio resources used by MBMS service are not dedicated for one user, but are shared by all users using this service.
The SRNS relocation procedure is described in 3GPP specification TR
23.846 vl .2.0. Figure 2 is the corresponding signaling flow. Each step of the flow is described in detail as follows.
201 A source RNC decides to execute SRNS relocation procedure.
202 The source RNC sends a "Relocation Required" message to an original SGSN. 203 The original SGSN forwards a "Relocation Request" message to a new
SGSN.
204 The new SGSN sends the "Relocation Request" message to a target RNC and a radio access bearer (hereinafter referred to as RAB) is established between the target RNC and the new SGSN. After the resources needed by RAB including resources on the user plane are allocated successfully, the target RNC sends a "Relocation Request Acknowledge" message to the new SGSN.
205 The new SGSN forwards a "Relocation Response" message to the original SGSN.
206 The original SGSN sends a "Relocation Command" message to the source RNC.
207 The source RNC starts to copy data and sends them to the target RNC through network protocol layer (hereinafter referred to as IP layer).
208 The source RNC sends a "Relocation Commit" message to the target RNC, which is used to transmit SRNS Context to the target RNC and the role of SRNS converts from source RNC to target RNC.
209 When the target RNC receives the trigger message for executing relocation, it sends a "Relocation Detection" message to the new SGSN. Thereafter, the target RNC starts to play the role of Serving Radio Network Controller (hereinafter referred to as SRNC). 210 UE exchanges mobility-related information, such as new SRNC Identity, expression of location area and upstream user data, with the target RNC.
211 If the SRNS relocation is the one between different SGSNs, the new SGSN sends an "Update Packet Data Protocol (hereinafter referred to as PDP) Context Request" message to the corresponding GGSN after receiving the "Relocation Detection" message. GGSN updates PDP context and returns an "Update PDP Context Response" message. The new SGSN examines each MBMS service in MBMS Context of UE. If a certain service is joined by UE in SGSN for the first time, a GPRS Tunnel Protocol (hereinafter referred to as GTP) tunnel is established between SGSN and GGSN, and MBMS Context is created at GGSN. 212 The target SRNC initiates a Relocation Complete procedure after receiving an "UTRAN Mobility Information Confirm" message. The new SGSN sends a "Relocation Complete" message to notify the original SGSN of the completion of the SRNS relocation procedure. 213 Release an lu connection between the source RNC and the source SGSN as well as user resources.
214 If a new Route Area Indication (hereinafter referred to as RAI) is different from an original one, UE initiates a route location update procedure.
Cl, C2 and C3 execute Customized Applications for Mobile network Enhanced Logic (hereinafter referred to as CAMEL).
Existing RANAP message
In 3GPP specification TR 25.413 v5.0.0, the "RAB Assignment Request" message includes information on the following several aspects: - RABs To Be Setup Or Modified List: information such as RAB Identity (ID) to be setup or modified, RAB parameters on user plane, etc.
- RABs To Be Released List: RAB ID to be released, release reason.
This message is connection-oriented. There is no identity of information element UE being included in the message. Similarly, messages of "RAB Assignment Response" and "Initial UE Information" also don't include identity of UE. SGSN and RNC may get UE information according to lu connection identity.
The Relocation Request message includes information on the following several aspects:
- Relocation Type: this information element indicates whether the execution of SRNS relocation is related with UE.
- Cause: indicates the reason for initiating relocation. Source ID: indicates the source of SRNC relocation.
- Target ID: indicates the target ID of SRNC relocation, which might be either an ID of target RNC, or a global Cell ID of target cell (in the case of relocating from UMTS to GSM).
Source RNC To Target RNC Transparent Container: includes parameters such as encryption information, cell load information and mapping relation between Radio Access Bearer (RAB) and transmission channel. - Old BSS To New BSS Information: information created by Source RNC and transferred to Target RNC, includes password index, RAB information, transmission channel information as the like.
The Relocation Command message includes information on the following several aspects:
- Target RNC To Source RNC Transparent Container: includes parameters such as encryption information, cell load information and mapping relation between Radio Access Bearer (RAB) and transport channel.
- Inter-System Information Transparent Container: includes temporary ID of transmission network and radio resource control information.
- L3 information: messages of wireless network layer.
- RABs To Be Released List: information on Radio Access Bearer (hereinafter referred to as RAB) to be released.
- RABs Subject To Data Forwarding List: information on RAB subject to forward data.
These messages are between Source RNC and Source SGSN during relocation procedure, and are connection-oriented. So there is no ID of UE being included in these messages, and SGSN and RNC can get the UE which is relocated according to lu connection ID. Similarly, other messages such as "Relocation Request Acknowledge",
"Relocation Detection", "Relocation Complete", "Relocation Preparation Failure", "Relocation Failure", and "Relocation Cancel" in relocation procedure are all connection-oriented, therefore there is no ID of UE being included in information elements of these messages.
Signaling connection establishment and release of existing lu interface
When information of UE and CN needs to be exchanged between Radio
Network Controller (hereinafter referred to as RNC) and CN and there is no
Signaling Connection Control Part (hereinafter referred to as SCCP) for this UE on lu interface, start to establish a new SCCP connection. SCCP connection is established as follows:
I) RNC initiates an establishment of SCCP signaling connection
When RNC receives a non-access stratum message from UE for the first time, and if there is no lu connection for this UE, RNC initiates the procedure of SCCP connection establishment. RNC sends a "SCCP Connection Request" message including one RANAP message in its data field to CN.
II) CN initiates an establishment of SCCP signaling connection
CN initiates an establishment of SCCP signaling connection when executing relocation. CN initiates an establishment of lu connection by sending a
"SCCP Connection Request" message to RNC, and the data field of the "SCCP Connection Request" includes a RANAP message (optional).
Above are only the cases where SCCP connection establishment have been decided at present. And the others will be introduced in the future.
When RNC decides to execute SRNS relocation procedure, it sends a "Relocation Required" message to a Source SGSN. However, since there is no ID of UE in the "Relocation Required" message, if the message is sent through the shared lu connection of certain MBMS service that UE receives, SGSN will not know the "Relocation Required" message comes from which UE. Other RANAP messages, such as "Relocation Command", "RAB Assignment Request", "RAB Assignment Response", "Initial UE Information" and "Direct Transfer" will encounter the same problem of RNC or SGSN unable to identify when sending through a shared lu connection. lu release procedure is used to release lu signaling connection as well as
UTRAN resources related with this signaling connection. During relocation procedure, if the moving UE is not the unique user of certain MBMS service, after SGSN sends a "lu Release Command" to a Source RNC, it will release the shared connection as well as user plane resources for MBMS. This is unreasonable, and it should be that transmitting proper message will only release UTRAN resources related with the moving user.
In the conditions of existing SCCP connection establishment: when RNC receives a non-access stratum message from UE for the first time, if there is no lu connection for this UE, RNC initiates the procedure of SCCP connection establishment. If UE has upstream non-MBMS data necessary for being transmitted while receiving MBMS service, it will send a Service Request message to RNC. According to above described conditions for SCCP connection establishment, RNC will initiate a procedure to setup dedicated lu connection for the UE. This is true if a plurality of UEs receiving a same kind of MBMS service, dedicated lu connections will be setup for a plurality of UEs, which is contradict with the shared lu connection mode. CN initiates an establishment of SCCP signaling connection when executing relocation. CN initiates an lu signaling connection establishment procedure by sending a "SCCP Connection Request" message to RNC. If a shared lu connection for certain MBMS service has been setup between a target RNC and a new SGSN when UE moves to the RNC, then it is unnecessary to setup a dedicated lu connection for the UE. So it is necessary to modify the existing conditions of SCCP connection establishment.
SUMMARY OF THE INVENTION
The object of the present invention is to provide a method that can support to use shared lu signaling connection for MBMS service in a mobile communication system by modifying existing specifications (e.g. message, flow).
To accomplish above object, a method of supporting MBMS service to employ shared lu signaling connection comprises:
(a) UE has non-MBMS service necessary for being transmitted while receiving MBMS service;
(b) The UE sends a non-access stratum message "Service Request" to SGSN;
(c) RNC checks whether the UE receives MBMS service or not, when forwarding the non-access stratum message "Service Request" of the UE to
SGSN, and if there is a shared lu connection for the UE to receive certain MBMS service, don't initiate a SCCP Connection Establishment procedure, and the RNC forwards the non-access stratum message of the UE through the shared lu connection to the SGSN; (d) After receiving the "Service Request" message, in the case where the service request is accepted, the SGSN returns a "Service Acceptance" message to MS;
(e) The SGSN sends an "RAB Assignment Request" message to the RNC through the shared lu connection for receiving certain MBMS service by the
UE in order to request to establish RAB, and adding an information element, i.e. Permanent NAS UE Identity, to existing message "RAB Assignment
Request" for identifying the UE in UTRAN and CN;
(f)The RNC allocates resources and sends an "RAB Assignment Response" message through the shared lu connection, and adding an information element, i.e. Permanent NAS UE Identity, to existing message "RAB Assignment Response" for identifying the UE in UTRAN and CN; (g) The SGSN receives the "RAB Assignment Response" message from the RNC and knows that the corresponding user plane bearer establishment for UE has been completed according to ID of the UE in this message.
This invention makes WCDMA system able to support shared lu connection mode for MBMS service. It solves the problem of user mobility caused by shared connection being employed for MBMS service on lu interface, and at the same time, solves the problem of how MBMS shared lu signaling connection provides service for UE dedicated non-MBMS service in WCDMA system. Modifications for the specification made in the invention will not affect the existing functions of the system. It keeps backward compatibility.
BRIEF DESCRIPTION OF THE DRAWINGS
Figure 1 is a schematic diagram of MBMS system architecture; Figure 2 shows the existing SRNS relocation procedure;
Figure 3 shows SRNS relocation procedure that supports shared lu connection; Figure 4 is the procedure of MBMS shared lu signaling connection serving UE dedicated non-MBMS service.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT
(1) Modifications to existing messages
Relocation Required:
Based on existing specification, a new information element, i.e. Permanent NAS UE Identity, is added to this message for identifying UE in UTRAN and CN. SGSN finds other signaling connections (e.g. shared lu signaling connections that other UEs can use) that have been save by this information element. This parameter uses the type of International Mobile User Identity (hereinafter referred to as IMSI). This parameter is optional. For UEs that don't receive MBMS service, this message is transferred through UE dedicated lu; while for UEs that receive MBMS service, this message is transferred through shared lu connection. This parameter is meaningful.
Relocation Command:
Based on the existing specification, an information element, i.e. Permanent NAS UE Identity, is newly added to this message for identifying UE in UTRAN and CN. RNC finds other signaling connections (e.g. RRC signaling connection or other shared lu signaling connection that other UEs can use) that have been save by this information element. This parameter is the type of IMSI.
Other messages used for relocation on lu Interface: an information element, i.e. Permanent NAS UE Identity shall be newly added to Relocation Request Acknowledge, Relocation Detection; Relocation Complete, Relocation Preparation Failure, Relocation Cancel, Relocation Cancel Confirmation.
Messages for establishing, modifying and releasing bearer on user plane: an information element, i.e. Permanent NAS UE Identity shall be added to RAB
Assignment Request, RAB Assignment Response, RAB Release Request. RNC and SGSN can then distinguish which UE the operation of RAB establishing, modifying or releasing will be performed for.
Meanwhile, Initial UE Information and Direct Transfer message shall also be added with an information element, i.e. Permanent NAS UE Identity.
(2) Modification to the flow of SRNS relocation signaling
In this signaling flow, after the Source SGSN has executed the step of forwarding Relocation Confirmation to the new SGSN (the 12th step in Figure 2):
- If SGSN finds that a moving user is the last user leaving or quitting a certain MBMS service, it sends an "lu Release Command" message to a Source RNC for requesting to release a certain shared lu connection and UTRAN resources related with this connection. If the moving user is the last user of several MBMS services between SGSN and RNC, SGSN needs to send the "lu Release Command" message to Source RNC repeatedly.
If the moving user is not the last user receiving MBMS service and the user is receiving other non-MBMS service besides the MBMS service, SGSN needs to send an "RAB Assignment Request" message to RNC for releasing a non-MBMS RAB for this user.
If the moving user is not the last user receiving MBMS service and the user isn't receiving other non-MBMS service than MBMS service, then this step is unnecessary.
RNC decides to perform different operations according to a message received:
If RNC receives an "lu Release Command" from SGSN, it releases an lu connection and relevant resources and then returns an "lu Release Complete" message to SGSN. - If RNC receives an "RAB Assignment Request" message, it releases RAB indicated in the message for the UE according to ID of UE, i.e. Permanent NAS UE Identity, in the message, and returns a "RAB Assignment Response" message to SGSN. In this signaling flow, after a Target RNC receives a "Relocation Request" message from a new SGSN, according to MBMS context in the message, it sends a "MBMS Service Request" message to the new SGSN to request for a certain MBMS service, if the Target RNC hasn't yet joined in the service used by UE. If the Target RNC hasn't yet joined in several MBMS services used by UE, it is necessary to send this message repeatedly for several times.
(3) SCCP Connection Establishment and Release
In order to support the means of employing shared lu signaling connection for MBMS service in a mobile communication system, the trigger condition of existing SCCP connection establishment is modified as follows:
In the case of SCCP connection establishment:
I) RNC initiates an establishment of SCCP signaling connection
When RNC receives a Non-Access Stratum (NAS) message transmitted from UE for the first time, if there is neither lu connection for this UE nor shared lu connection for UE to receive MBMS service, RNC initiates a
SCCP Connection Establishment procedure. RNC sends a "SCCP Connection Request" message including one RANAP message in its data field to CN.
When RNC sends a "MBMS Service Request" message to SGSN, if there is no lu connection used for this service on lu interface, then RNC initiates a SCCP connection establishment procedure. One RANAP message is included in the data field of "SCCP Connection Establishment Request" (Please refer to "A Method of Signaling Bearer Connection for MBMS on lu Interface"). I) CN initiates an establishment of SCCP signaling connection
When CN performs relocation, if UE hasn't received MBMS service or there is no shared signaling connection for UE to receive MBMS service between RNC and SGSN, then CN initiates an establishment of SCCP signaling connection. CN initiates the establishment of lu connection by sending a "SCCP Connection Request" message to RNC, whose data field includes one RANAP message (optional).
If there exists a shared signaling connection for UE to receive MBMS service between RNC and SGSN, CN will not initiate the procedure of SCCP connection establishment.
In order to support the shared lu signaling connection for MBMS service in the mobile communication system, SRNS relocation procedure is shown in Figure 3. Each step is described in detail as followings:
301 A Source RNC decides to perform SRNS relocation procedure; 302 The Source RNC constructs a "Relocation Required" message, if a lu connection dedicated for UE exists (UE doesn't receive MBMS service), then directly sends the message to SGSN. If the UE is receiving the MBMS service, then there is no dedicated lu connection for the UE, and the message is sent to SGSN through the shared lu connection for UE to receive a certain MBMS service. Information elements of the Relocation Required message include Permanent NAS UE Identity. According to ID of the UE, SGSN can get known which UE has roamed.
303 An Original SGSN forwards a "Relocation Request" message including MBMS Context to a new SGSN. 304 The New SGSN sends a "Relocation Request" message to a Target RNC.
If UE doesn't receive MBMS service or there is no shared signaling connection for UE to receive MBMS service between RNC and SGSN, SGSN initiates a SCCP Signaling Connection Establishment procedure during sending the "Relocation Request" message. SGSN initiates an establishment of lu connection by sending a "SCCP Connection Request" message to RNC, whose data field includes one RANAP message (optional). In the case where UE doesn't receive MBMS service, what is established is a dedicated lu connection for the UE.
If shared signaling connection for UE to receive MBMS service between RNC and SGSN exists, then the new SGSN directly sends the "Relocation Request" to the Target RNC, and will not initiate SCCP connection establishment procedure.
305 If the target RNC hasn't joined in a corresponding service, it sends a "MBMS Service Request" message to SGSN.
306 Radio access bearer including RABs of MBMS is established between the target RNC and the new SGSN. 307 After the resources needed by RAB including resources on the user plane are allocated, the target RNC sends a "Relocation Request Acknowledge" message to the new SGSN. Information elements of the "Relocation Request Acknowledge" message include Permanent NAS UE Identity. 308 The new SGSN forwards the "Relocation Response" to the original
SGSN.
309 The original SGSN sends a "Relocation Command" message including information element Permanent NAS UE Identity to the Source RNC.
310 The source RNC starts to copy data and sends them to the target RNC through network protocol layer (hereinafter referred to as IP layer).
311 The source RNC sends "Relocation Commit" to the target RNC. This procedure is used to transmit SRNS Context to the target RNC and the role of SRNS converts from the source RNC to the target RNC.
312 When the target RNC receives a trigger message for performing relocation, it sends a "Relocation Detect" message to the new SGSN, the
"Relocation Detect" message includes information element, Permanent NAS UE Identity. After that, the target RNC starts to play the role of Serving Radio Network Controller (hereinafter referred to as SRNC).
313 UE exchanges mobility-related information, such as new SRNC Identity, expression of location area and upstream user data, with the target RNC.
314 If the SRNS relocation is the one between different SGSNs, the new SGSN sends an "Update Packet Data Protocol (hereinafter referred to as PDP) Context Request" message to the corresponding GGSN after receiving the "Relocation Detection" message. GGSN updates PDP context and returns an "Update PDP Context Response" message. The new SGSN examines each MBMS service in MBMS Context of UE. If a certain service is joined by UE in SGSN for the first time, a GTP tunnel is established between SGSN and GGSN, and MBMS Context is created at GGSN.
315 The target SRNC initiates a Relocation Complete procedure after receiving a "UTRAN Mobility Information Confirm" message. The "Relocation
Complete" message includes information element, Permanent NAS UE Identity.
316 The new SGSN sends the "Relocation Complete" message to notify the original SGSN of the completion of SRNS relocation procedure, and the original SGSN returns a "Relocation Complete Acknowledge" message. 317 Release relevant resources between the Source RNC and the Source SGSN.
If the UE is the last one that uses MBMS service in the source RNC, the shared connection and user plane resources corresponding to MBMS service shall be released. SGSN sends an "lu Release Command" message to the Source RNC for requesting RNC to release a corresponding lu connection and UTRAN resources related with this connection; the Source RNC releases corresponding resources and sends an "lu Release Complete" message to SGSN. If the UE is the last user of the source RNC for several services, then above release procedure is performed for several times. If the moving user is not the last user that receives MBMS service, SGSN sends an "RAB Assignment Request" message to RNC for releasing non-MBMS RAB of this user. The Source RNC releases corresponding resources and sends an "RAB Assignment Response" message to SGSN. These two messages both include information element Permanent NAS UE Identity. RNC and SGSN may get known which user's RAB should be released.
If the moving user is not the last user that receives MBMS service and the user doesn't receive other non-MBMS service than MBMS service, this step is unnecessary.
318 If the new Route Area Indication (hereinafter referred to as RAI) is different from the original, UE initiates a route location update procedure.
The procedure of MBMS shared lu signaling connection serving UE dedicated non-MBMS service is shown in Figure 4. Each step is described as following: 401 MS receives MBMS service.
402 Since an RRC connection has been existed, MS has upstream data of non-MBMS service to be sent, and constructs a "Service Request" message.
403 MS sends the "Service Request" message to SGSN for requesting SGSN to reserve resources. The service type parameter of "Service Request" message shall be set as data. When RNC forwards Non-Access Stratum message "Service Request" of UE to SGSN, if lu connection for the UE or the shared lu connection for UE to receive MBMS service has existed, then RNC forwards the "Service Request" message through the existed connection.
405 In the case where the service request is accepted, SGSN returns a "Service Acceptance" message to MS. For the UE receiving MBMS service, this message is sent through the shared lu signaling connection.
406 SGSN sends an "RAB Assignment Request" message to RNC through the shared lu connection used for UE receiving a certain MBMS service for requesting the establishment of RAB. A new information element, i.e. Permanent NAS UE Identity, included in the message "RAB Assignment Request" is used to identify UE in UTRAN and CN. RNC finds other signaling connections (e.g. shared lu signaling connections that other UEs can use) that have been save by this information element.
407 RNC sends an "Establishment of RB" message to MS for notifying MS of that new establishment of RAB ID request establishment of radio resources.
408 MS returns an "Establishment of RB Complete" to notify RNC of radio bearer establishment success.
409 RNC returns an "RAB Assignment Response" to SGSN through the shared lu signaling connection, which indicates the completion of user plane bearer establishment. The message includes information element Permanent NAS UE Identity.
410 For each Re-established RAB by using modified QoS, SGSN initiates a "PDP Context Modification" procedure to notify MS and GGSN of corresponding to the new negotiated QoS of PDP Context. 411 MS sends upstream data packets.

Claims

WHAT IS CLAIMED IS:
1. A method of supporting MBMS service to employ shared lu signaling connection comprises: (a) UE has non-MBMS service necessary for being transmitted while receiving MBMS service;
(b) the UE sends a non-access stratum message "Service Request" to SGSN;
(c) RNC checks whether the UE receives MBMS service or not, when forwarding the non-access stratum message "Service Request" of the UE to SGSN, and if there is a shared lu connection for the UE to receive certain MBMS service, don't initiate a SCCP Connection Establishment procedure, and the RNC forwards the non-access stratum message of the UE through the shared lu connection to the SGSN;
(d) after receiving the "Service Request" message, in the case where the service request is accepted, the SGSN returns a "Service Acceptance" message to
MS;
(e) the SGSN sends an "RAB Assignment Request" message to the RNC through the shared lu connection for receiving certain MBMS service by the UE in order to request to establish RAB, and adding an information element, i.e. Permanent NAS UE Identity, to existing message "RAB Assignment Request" for identifying the UE in UTRAN and CN;
(f) the RNC allocates resources and sends an "RAB Assignment Response" message through the shared lu connection, and adding an information element, i.e. Permanent NAS UE Identity, to existing message "RAB Assignment Response" for identifying the UE in UTRAN and CN;
(g) the SGSN receives the "RAB Assignment Response" message from the RNC and knows that the corresponding user plane bearer establishment for UE has been completed according to ID of the UE in this message.
2. The method according to Claim 1, wherein further comprises that the modifications to the establishment procedure of the RNC initiating the SCCP signaling connection comprising: the RNC initiates the establishment of SCCP signaling connection; when the RNC receives a non-access stratum message from UE for the first time, if there is no lu connection for this UE, the RNC initiates the procedure of SCCP connection establishment, and the RNC sends an "SCCP Connection Request" message including one RANAP message in its data field to CN.
3. The method according to Claim 1, wherein a new information element, i.e. Permanent NAS UE Identity, is added to existing messages of "Initial UE Information" and "Direct Transfer" for identifying the UE in UTRAN and CN.
4. A method of supporting MBMS service to employ shared lu signaling connection comprises:
(a) SRNC decides to perform relocation procedure;
(b) the SRNC constructs a "Relocation Required" message, and if there is no dedicated lu signaling connection for the UE, then the "Relocation Required" message is sent to an original SGSN through the shared lu signaling connection for UE receiving a certain MBMS service;
(c) the original SGSN forwards a "Relocation Request" to a new SGSN;
(d) the new SGSN sends the "Relocation Request" message to a Target RNC, and if UE doesn't receive MBMS service or there is no shared signaling connection for UE to receive MBMS service between RNC and SGSN, SGSN then initiates a SCCP Signaling Connection Establishment procedure; otherwise, the "Relocation Request" message is sent to the Target RNC through the shared lu signaling connection for UE receiving the certain MBMS service;
(e) after the Target RNC allocates RAG for the service required by UE, a "Relocation Request Acknowledge" message is sent to the new SGSN through the shared lu signaling connection for UE receiving the certain MBMS service;
(f) after the original SGSN receives the "Relocation Response" message from the new SGSN, a "Relocation Command" message is sent to an original RNC through the shared lu signaling connection for UE receiving the certain MBMS service;
(g) after a Target RNC receives a "Relocation Commit" message from the original RNC, a "Relocation Detect" message is sent to the new SGSN through the shared lu signaling connection for UE receiving the certain MBMS service; (h) after the Target RNC receives a "UE Mobility Information Confirm" message from UE, a "Relocation Complete" message is sent to the new SGSN through the shared lu signaling connection for UE receiving the certain MBMS service; (i) after the Source SGSN forwards Relocation Complete Acknowledge to the new SGSN:
♦ if the SGSN finds that the moving user is the last user leaving or quitting the certain MBMS service, SGSN sends an "lu Release Command" message to the Source RNC for requesting to release a certain shared lu connection as well as UTRAN resources related with this connection, and if the moving user is the last user for several MBMS services between SGSN and RNC, it is necessary for SGSN to send the "lu Release Command" message to Source RNC repeatedly for several times;
♦ if the moving user is not the last one receiving the MBMS service, this step is unnecessary;
♦ if the moving user is not the last one receiving the MBMS service and the user receives other non-MBMS service than the MBMS service, it is necessary for SGSN to send an "RAB Assignment Request" message to RNC for releasing a non-MBMS RAB of this user; (j) if the Source RNC receives the "lu Release Command" or the "RAB Assignment Request" message of the Source SGSN, relevant resources is released and an "lu Release Complete" or "RAB Assignment Response" message is sent back respectively.
5. The method according to Claim 4, wherein a new information element, i.e.
Permanent NAS UE Identity, is added to existing messages of "Relocation Required", "Relocation Command", "Relocation Request
Acknowledge", "Relocation Detect" and "Relocation Complete" for identifying the UE in UTRAN and CN.
6. The method according to Claim 4, wherein further comprises that the modifications to the establishment procedure of CN initiating SCCP signaling connection comprising: when CN performs relocation, if UE doesn't receive MBMS service or there is no shared signaling connection for UE to receive MBMS service between RNC and SGSN, CN initiates the establishment of SCCP signaling connection, and CN initiates the establishment of lu connection by sending an "SCCP Connection Request" message including one RANAP message in its data field to the RNC; if a shared signalling connection for UE to receive MBMS service between RNC and SGSN has existed, CN doesn't initiate the procedure of SCCP connection establishment.
7. The method according to Claim 4, wherein further comprises, in the
SRNS relocation flow, after the Target RNC receives the "Relocation Request" message from the new SGSN, according to MBMS context in the message, if the Target RNC doesn't join in a certain MBMS context used by UE, it sends a "MBMS Service Request" message to the new SGSN for requesting the service, and if the Target RNC doesn't join in several MBMS services used by UE, it is necessary to send this message repeatedly for several times.
PCT/KR2003/002358 2002-11-05 2003-11-05 Method for supporting multicast broadcast/multicast service to employ shared iu signaling connection WO2004043024A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CNA021503435A CN1499853A (en) 2002-11-05 2002-11-05 Method for supporting services in multimedia broadcast and multicast by sharing Lu signaling connection
CN02150343.5 2002-11-05

Publications (1)

Publication Number Publication Date
WO2004043024A1 true WO2004043024A1 (en) 2004-05-21

Family

ID=32304076

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2003/002358 WO2004043024A1 (en) 2002-11-05 2003-11-05 Method for supporting multicast broadcast/multicast service to employ shared iu signaling connection

Country Status (2)

Country Link
CN (1) CN1499853A (en)
WO (1) WO2004043024A1 (en)

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1760957A1 (en) * 2004-12-02 2007-03-07 Huawei Technologies Co., Ltd. A method for distributing resources of bearer network
CN100407856C (en) * 2004-09-07 2008-07-30 中兴通讯股份有限公司 Method for preventing from transmitting accessing message spanning wireless network controller by Iur interface
US7457275B2 (en) * 2002-04-09 2008-11-25 Jianguo Zhao Method for implementing Iu-Flex based MBMS
GB2455545A (en) * 2007-12-13 2009-06-17 Nec Corp MBMS Bearer establishment reconfiguration and release
CN101193340B (en) * 2006-11-29 2010-12-08 华为技术有限公司 Method and device for establishing MBMS wireless access carrier indication
CN102075980A (en) * 2009-11-25 2011-05-25 中国移动通信集团福建有限公司 Method and device for obtaining system switching information element
US8325641B2 (en) 2004-09-30 2012-12-04 Huawei Technologies Co., Ltd Method and apparatus for service identifying and routing in multimedia broadcast/multicast service system
US8363619B2 (en) 2007-01-29 2013-01-29 Huawei Technologies Co., Ltd. Method, apparatus and system for establishing S1 signaling connection in an evolved network
US8855099B2 (en) 2007-03-19 2014-10-07 Qualcomm Incorporated Selective phase connection establishment
WO2017054544A1 (en) * 2015-09-30 2017-04-06 华为技术有限公司 Enhanced multimedia broadcast multicast service (embms) implementation method and apparatus
CN110876207A (en) * 2012-03-30 2020-03-10 交互数字专利控股公司 Method for use in a wireless transmit/receive unit WTRU and WTRU

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100421515C (en) * 2005-05-20 2008-09-24 华为技术有限公司 Method for realizing multi-cast business data based on mobile network
CN100450004C (en) * 2005-07-27 2009-01-07 华为技术有限公司 Transmitting method and receiving method for multimedia broadcasting/multicasting service
CN100396135C (en) * 2005-08-01 2008-06-18 华为技术有限公司 Method for reporting RAB assignation fault in wide-band CDMA system
CN100428860C (en) * 2006-02-14 2008-10-22 华为技术有限公司 Multimedia broadcast/multicast service linking method
CN101018408B (en) * 2007-02-01 2010-10-06 华为技术有限公司 Service implementation method, network device and network

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5673265A (en) * 1994-05-19 1997-09-30 Integrated Network Corporation Scalable multimedia network
US5949871A (en) * 1996-02-20 1999-09-07 Hewlett-Packard Company Method and apparatus for providing a service in a switched telecommunications system wherein a control message is altered by a receiving party
US6335927B1 (en) * 1996-11-18 2002-01-01 Mci Communications Corporation System and method for providing requested quality of service in a hybrid network

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5673265A (en) * 1994-05-19 1997-09-30 Integrated Network Corporation Scalable multimedia network
US5949871A (en) * 1996-02-20 1999-09-07 Hewlett-Packard Company Method and apparatus for providing a service in a switched telecommunications system wherein a control message is altered by a receiving party
US6335927B1 (en) * 1996-11-18 2002-01-01 Mci Communications Corporation System and method for providing requested quality of service in a hybrid network

Cited By (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7457275B2 (en) * 2002-04-09 2008-11-25 Jianguo Zhao Method for implementing Iu-Flex based MBMS
CN100407856C (en) * 2004-09-07 2008-07-30 中兴通讯股份有限公司 Method for preventing from transmitting accessing message spanning wireless network controller by Iur interface
US8325641B2 (en) 2004-09-30 2012-12-04 Huawei Technologies Co., Ltd Method and apparatus for service identifying and routing in multimedia broadcast/multicast service system
EP1760957A4 (en) * 2004-12-02 2008-03-26 Huawei Tech Co Ltd A method for distributing resources of bearer network
EP1760957A1 (en) * 2004-12-02 2007-03-07 Huawei Technologies Co., Ltd. A method for distributing resources of bearer network
CN101193340B (en) * 2006-11-29 2010-12-08 华为技术有限公司 Method and device for establishing MBMS wireless access carrier indication
US8842638B2 (en) 2007-01-29 2014-09-23 Huawei Technologies Co., Ltd. Method, apparatus and system for establishing S1 signaling connection in an evolved network
US11129058B2 (en) 2007-01-29 2021-09-21 Huawei Technologies Co., Lid. Method, apparatus, and system for establishing signaling connection in communication network
US10172042B2 (en) 2007-01-29 2019-01-01 Huawei Technologies Co., Ltd. Method, apparatus and system for establishing signaling
US8363619B2 (en) 2007-01-29 2013-01-29 Huawei Technologies Co., Ltd. Method, apparatus and system for establishing S1 signaling connection in an evolved network
US8855099B2 (en) 2007-03-19 2014-10-07 Qualcomm Incorporated Selective phase connection establishment
US8792404B2 (en) 2007-12-13 2014-07-29 Nec Corporation MBMS bearer establishment reconfiguration and release
GB2455545B (en) * 2007-12-13 2010-01-27 Nec Corp MBMS bearer establishment reconfiguration and release
GB2455545A (en) * 2007-12-13 2009-06-17 Nec Corp MBMS Bearer establishment reconfiguration and release
CN102075980A (en) * 2009-11-25 2011-05-25 中国移动通信集团福建有限公司 Method and device for obtaining system switching information element
CN110876207A (en) * 2012-03-30 2020-03-10 交互数字专利控股公司 Method for use in a wireless transmit/receive unit WTRU and WTRU
WO2017054544A1 (en) * 2015-09-30 2017-04-06 华为技术有限公司 Enhanced multimedia broadcast multicast service (embms) implementation method and apparatus

Also Published As

Publication number Publication date
CN1499853A (en) 2004-05-26

Similar Documents

Publication Publication Date Title
KR100651436B1 (en) Method for multimedia broadcast/multicast service signaling bearer connection on iu interface
US8165053B2 (en) Method for supporting MBMS service transmission in LTE system
KR100588072B1 (en) A communication system comprising a plurality of communication networks
JP3908763B2 (en) Method of changing point-to-point (PtP) channel and point-to-multipoint (PtM) channel in MBMS
US7953042B2 (en) Handover method and apparatus between different systems
US7215958B2 (en) Relocation method, system and network element
US20070213058A1 (en) Method and apparatus for supporting handoff and serving radio network subsystem relocation procedures in a single tunnel gprs-based wireless communication system
US20060109812A1 (en) Temporary mobile group identifier generation and distribution method
US20070213060A1 (en) Method and apparatus for supporting handoff in an lte gtp based wireless communication system
US6955918B2 (en) Serving network entity relocation
CN101005692A (en) Method for reducing terminal switch between LTE and 3G cut-in technology
US7970423B2 (en) Context linking scheme
KR20070006539A (en) Hand-over method and apparatus between differential systems
WO2004043024A1 (en) Method for supporting multicast broadcast/multicast service to employ shared iu signaling connection
WO2010111814A1 (en) Apparatus and method for moving wcdma mobile station in the manner of the least packet loss
EP1521487A1 (en) Method, system and radio access network nodes for user data connection re-establishment
CN103428888A (en) Method and system for establishing direct tunnel
WO2011018040A1 (en) Method and system for cell update
WO2007102953A1 (en) Method and apparatus for supporting handoff and serving radio network subsystem relocation procedures in a single tunnel gprs-based wireless communication system
WO2004043020A1 (en) Method for identifying user equipment states by core network and user equipment
WO2014009439A1 (en) Reporting user related information in a mobile communication network
WO2009152757A1 (en) Data message sending method, apparatus and communication system
WO2013000289A1 (en) Mobility management method for direct tunnel, network element, and system
KR20100069442A (en) Method of bearer establishment for mbms dat transmission in the packeted-based mobile communication system
WO2008134978A1 (en) Relocating method, communication system and radio network controller

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): JP KR US

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PT RO SE SK TR

121 Ep: the epo has been informed by wipo that ep was designated in this application
WWE Wipo information: entry into national phase

Ref document number: 1031/KOLNP/2004

Country of ref document: IN

122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP

WWW Wipo information: withdrawn in national office

Ref document number: JP