KR20050100859A - Method for management service context in order to paging user equipment with cs service in multimedia broadcast/multicast service - Google Patents

Abstract

The present invention relates to a multicast multimedia broadcasting service (MBMS). In order to call the MBMS service, a radio network controller (RNC) manages an MBMS context corresponding to the MBMS service. The radio network controller allows a user terminal having a dedicated channel and not included in the MBMS context of the radio network controller (RNC) to receive a dedicated call message for a desired MBMS service. To this end, the user terminal includes an indicator or related information indicating that it has participated in the MBMS service in the first NAS message to request access to the CS domain. The wireless network controller searches for an SGSN corresponding to the user terminal, receives MBMS service information of the user terminal, and stores the received MBMS service information in an MBMS context. The present invention has the effect of increasing the success rate and reliability of the MBMS call.

Description

Service context management method for calling user terminal in line service in multicast multimedia broadcasting service.

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a Multicast Multimedia Broadcast Service (hereinafter, referred to as an MBMS service), and more particularly, to a method of managing MBMS service information for an MBMS service.

Due to the development of communication technology, the services provided by the mobile communication system using the wideband code division multiple access (CDMA) scheme are not only conventional voice services but also large capacity such as packet data and circuit data. It is evolving into packet service communication for transmitting data and multimedia broadcasting / communication for transmitting multimedia service. Accordingly, in order to support the multimedia broadcasting / communication, an MBMS service that provides a service from one or more multimedia data sources to a plurality of user equipments (hereinafter referred to as UEs) has been discussed.

The MBMS service refers to a service for transmitting the same multimedia data to multiple receivers through a wireless network. In this case, by allowing multiple receivers to share one radio channel, it is possible to save radio transmission resources. The MBMS service supports multimedia transmission forms such as real-time video, audio, still images, and text. The MBMS service is a service that can simultaneously provide audio data and video data according to the multimedia transmission format, and requires a large amount of transmission resources. In the case of the MBMS service, since the same data must be transmitted to a plurality of cells in which users are located, one-to-one (Point to Point: PtP) or one-to-many (Point to Multiple :) according to the number of users located in each cell Called PtM).

1 schematically illustrates nodes participating in providing an MBMS service in a mobile communication network.

Referring to FIG. 1, UEs 161, 162, 163, 171, and 172 refer to terminal devices or subscribers capable of receiving MBMS services, and are referred to as cell 1 160 and cell 2 170. Is controlled by a base station apparatus, Node B, which wirelessly transmits MBMS related data to subscribers. A Radio Network Controller (RNC) 140 controls the plurality of cells 160 and 170, selectively transmits multimedia data to a specific cell, and is configured to provide MBMS service. Control the wireless channel. The connection between the RNC 140 and the UEs 161-172 is called a Radio Resource Control (RRC) interface.

The RNC 140 is connected to a Packet Switched or Packet Service (PS) network such as the Internet by a Serving GPRS Support Node (hereinafter referred to as 'SGSN') 130. Communication between the RNC 140 and the PS network is made by packet switched signaling (PS signaling). In particular, the connection between the RNC 140 and the SGSN 130 is called an Iu-PS interface. In addition, the part including the RNC 140 and the SGSN 130 for packet service is called a PS domain.

SGSN 130 controls the MBMS-related services of each subscriber. Representative examples of the role played by the SGSN 130 include managing a service related data of each subscriber and selectively transmitting multimedia data to a specific RNC 140.

The Transit NW 120 provides a communication path between the Broadcast Multicast Service Center (BM-SC) 110 and the SGSN 130 and to an external network through a Gateway GPRS Support Node (GGSN). Can be connected. The BM-SC 110 is responsible for scheduling of MBMS data as a source of MBMS data.

Meanwhile, the RNC 140 is connected to a circuit switched (CS) network by a mobile switching center (hereinafter referred to as 'MSC') 150. The CS network refers to a voice-based legacy communication network that is connection-based. Communication between the RNC 140 and the MSC 150 is performed by circuit switched signaling (CS signaling). In particular, the connection between the RNC 140 and the MSC 150 is called an Iu-CS interface. In addition, the part including the RNC 140 and the MSC 150 for the circuit service is called a CS domain.

MBMS data streams are delivered to UEs 161, 162, 163, 171 and 172 via the transport network 120, SGSN 130, RNC 140, Node B and cells 160, 170.

Although not shown, there may be multiple SGSNs for one MBMS service and multiple RNCs for each SGSN. Each SGSN is an RNC, each RNC performs selective data transmission to each of a plurality of cells, and for this purpose, a list of nodes (i.e., SGSN is a list of RNCs and a RNC is a list of cells) to which the data stream should be delivered. Saves and performs selective MBMS data transmission only to the stored nodes later.

In order for UEs to access a network and receive a service, a context, which is a set of information required to provide a corresponding service between UEs and network nodes, must be created. Typically, the context includes a UE context and a MM (Mobility Management) context.

First, the RNC creates UE contexts for UEs that have established a Radio Resource Control (RRC) connection. The UE context consists of basic information such as UE identifier (ID), location information of the UE, RRC status information of the UE, and radio resource information allocated to the UE, and is managed by the RNC while the RRC connection is active. do.

The MM context is for managing the location of the UE in the core network. In order for the UE to receive the PS service, first, the MM context of the UE must be generated in the SGSN and the GGSN through a GPRS attach procedure. The MM context of SGSN is UE such as International Mobile Subscriber Identity (IMSI), Temporary Mobile Subscriber Identity (P-TMSI), International Mobile Equipment Identity (IMEI), and Mobile Subscriber Integrated Switched Data Network (ISDN) Number (MS-ISDN). It includes an identifier, a routing area (RA), location information such as a service area code (SAC), authentication / encryption related information, billing information, and DRX parameters (Discontinuous Reception Parameters).

Network nodes such as RNC, MSC, SGSN manage the connection state of the UE for efficient signaling transmission and data transmission. The RNC manages the RRC state of the UE. The RRC state is determined according to whether the UE is connected to the RRC connection. If the UE makes an RRC connection, it is in an RRC-Connected state. If the UE does not make an RRC connection, it is in an RRC-Idle state.

SGSN manages the PMM status of the UE. The UE for which the MM context is not created in the SGSN is in the PMM-Detached state. The UE whose MM context is created in SGSN through GPRS Attach is divided into PMM-CONNECTED and PMM-IDLE states. If the UE has an Iu-PS signaling connection and is in an RRC-Connected state at the same time, it is a PMM-CONNECTED state. If the UE does not have an Iu-PS signaling connection or the RRC-Idle state, the PMM-Idle state.

The MSC manages the CMM state of the UE. If the UE has an Iu-CS signaling connection and is in the RRC-Connected state at the same time, the UE is in the CMM-Connected state. If the UE does not have an Iu-CS signaling connection or the RRC-Idle state, the CMM-Idle state.

In particular, for UEs that want to receive MBMS service, contexts for MBMS service, that is, MBMS UE context and MBMS service context, are defined in network nodes for MBMS service. The two contexts are collectively referred to as MBMS contexts. The MBMS UE context stores information on MBMS services joined for each UE. The MBMS service context is not generated for each UE in the network nodes transmitting MBMS data, but for each MBMS service or for each session in the service.

In order to achieve the MBMS service, an MBMS service context must be created in UEs and BM-SCs which are endpoints of the MBMS service. In addition, MBMS service contexts are created in RNC, SGSN, and GGSN network nodes transmitting MBMS data before MBMS data is transmitted.

Before the MBMS session starts, only if the UE has set up a Radio Access Bearer (RAB) including a Dedicated Channel (DCH) for the PS for dedicated services (these UEs are in the Cell-DCH state). SGSN sends MBMS service information to RNC. Therefore, when the UE is in the PMM-Idle state or in the PMM-Connected state for performing the Routing Area Update procedure, since the relevant information of the UE is not registered in the MBMS service context of the RNC, the UE is not registered. May not receive MBMS calls from the PS network. This may occur when the RRC connection for the CS service is established between the UE and the RNC, but the PS network does not know this.

When the MBMS session starts, the BM-SC sends an MBMS SESSION START REQUEST message to the corresponding RNC via SGSN, and the RNC sends the MBMS SESSION START REQUEST message received from the SGSN to call UEs for the MBMS service. Check the service identifier. This is because the MBMS SESSION START REQUEST message does not have a UE identifier, so as to identify identifiers of UEs joining the MBMS service using the MBMS service identifier included in the MBMS SESSION START REQUEST message.

In the MBMS calling procedure, the RNC calculates Notification Instance (NI) values using the MBMS Service Identifier (eg, Temporary MBMS Group Identifier) and the DRX parameter. The RNC turns on or off an MBMS Notification Indication Channel (MICH) for a time period indicated by a predetermined modulation period with the NI to indicate whether to receive the MCCH (MBMS Control Channel) of related UEs, and the MICH The UEs are called through a section of the associated MCCH starting after a predetermined time from the corresponding section of.

At this time, to call UEs in the Cell-DCH state, a PAGING TYPE 2 message transmitted through the DCCH is used. However, if a UE is in PMM-Idle mode or PMM-Connected mode to perform a Routing Area Update procedure, since UE related information is not registered in the MBMS service context of the RNC, It is not possible to send the PAGING TYPE 2 message.

That is, the RNC uses a common channel (CCH) to call UEs in PS-IDLE mode. Since the UE actually has a dedicated channel for circuit service with a CS network, an MBMS call is made through the shared channel. Does not receive Accordingly, the UE may not receive MBMS data even though it has requested MBMS service.

Accordingly, an object of the present invention, which is invented to solve the above problems, is to provide a method for performing an MBMS service call to all UEs participating in an MBMS service in a mobile communication system.

Another object of the present invention is to provide a method for performing an MBMS call to UEs in line service in order to provide an MBMS service in a mobile communication system.

It is still another object of the present invention to update and maintain an MBMS service context for UEs that transmit a Non Access Stratum (NAS) message for line service while joining an MBMS service in a radio network controller (RNC). In providing.

It is still another object of the present invention to provide a method for a UE participating in an MBMS service to signal an RNC with a minimum bit in consideration of a PMM state when a NAS (Non Access Stratum) message is transmitted for line service.

In order to achieve the above objects, a preferred embodiment of the present invention provides a packet service and a circuit service to the user terminals by controlling communication between the base station communicating with the user terminals in the cell and the base station and the user terminals. A mobile communication system for providing a multicast multimedia broadcasting (MBMS) service to a plurality of user terminals, including a radio network controller (RNC) providing a service node for managing the radio network controller. In the method of managing the service information for,

After the at least one MBMS service joins the user terminal in the packet service standby mode, the routing information for the packet service is included in the request message for establishing the connection of the line service and transmitted to the wireless network controller;

Acquiring, by the radio network controller, service identifier information of the at least one MBMS service in which the user terminal participates in response to the routing information of the request message;

And storing the obtained service identifier information for the user terminal.

Another preferred embodiment of the present invention, which is invented to achieve the above objects, provides a packet service and a circuit service to the user terminals by controlling communication between the base station communicating with the user terminals in the cell and the base station and the user terminals. A mobile communication system including a radio network controller (RNC) providing a service node for managing the radio network controller, and providing a multicast multimedia broadcasting (MBMS) service to the plurality of user terminals. In the method of managing the service information for,

After joining at least one MBMS service, a user terminal in packet service access mode and not having a radio access bearer for packet service, has at least one MBMS service joined by the user terminal in a request message for line service. Including the service participation indicator indicating and transmitting to the wireless network controller;

Acquiring, by the wireless network controller, service identifier information of the at least one MBMS service joined by the user terminal in response to the service participation indicator of the request message;

And storing the obtained service identifier information for the user terminal.

Hereinafter, the configuration and operation of the present invention will be described with reference to the accompanying drawings. DETAILED DESCRIPTION The following detailed description presents representative embodiments in the present invention to achieve the above technical problem. And other embodiments that can be presented with the present invention are replaced by the description.

The present invention described below is to manage the MBMS service context for the MBMS service according to the PMM state and the CMM state for user terminals (UEs) participating in one or more MBMS services. Therefore, in this specification, only a user terminal will be considered as a user terminal participating in one or more MBMS services. First, the management of the MBMS service context in the radio network controller (RNC) is divided into before and after the session for the MBMS service is started. Explain.

Iu signaling for the MBMS service is not maintained until the MBMS session starts. In order to prevent unnecessary Iu signaling exchange, SGSN does not perform MBMS UE Linking procedure on Iu when the UE has PS signaling connection but no PS RAB. Herein, linking refers to an operation of associating UE information with corresponding subscribed MBMS service information in the RNC and SGSN. Therefore, before starting a session, the following two cases do not store UE information in the MBMS service context in the RNC.

First, the UE is in PMM-IDLE mode

Second, the UE is in PMM-CONNECTED mode but does not have a PS RAB.

On the other hand, in the case of PMM-CONNECTED mode but PS RAB before the session starts, the UE information is stored in the MBMS service context in the RNC.

In contrast, after the start of the MBMS session, even if the UE is in the PMM-CONNECTED mode, the MBMS UE linking procedure is performed on Iu according to SGSN's decision.

If a UE which does not perform an MBMS UE linking procedure on Iu transitions to a CELL-DCH state for service with a CS domain before starting an MBMS session, the UE may not be notified that the MBMS service has been started when the session starts. Occurs. In order to solve this problem, in the preferred embodiment of the present invention, when the UE participates in the MBMS service, when the UE requests CS connection establishment to the CS domain, the MBMS Join Indicator: MBMS Joined IND) is transmitted to RNC. The MBMS participation indicator is a 1-bit indicator (1) or "0" indicates that at least one MBMS service that the UE is participating in exists. In this specification, it will be described that the MBMS participation indicator is set to on when there is at least one MBMS service that the UE is participating in.

When the RNC receives the MBMS participation indicator, the RNC receives the MBMS service information from the corresponding SGSN and stores the MBMS service information in the MBMS service context. In this case, the MBMS service information for the UEs in the PMM-IDLE state may be stored in the MBMS service context or may be stored in the other context like the information for other UEs.

In order to establish a CS connection, the NAS layer of the UE transmits a non-access stratum (NAS) message to the RNC in an RRC message of an RRC layer, which is an access stratum (AS) layer. Here, the RRC layer is a layer that is in charge of a radio connection between the UE and the RNC, and the RRC message is specifically an INITIAL DIRECT TRANSFER message. The NAS means an interface between the RNC and CN nodes (SGSN or MSC), and the NAS message is, for example, a CM (Configuration Module) SERVICE REQUEST message defined in the 3GPP TS 24.008 standard.

2 shows a simplified structure of an INITIAL DIRECT TRANSFER message 200 including a NAS message 206. The main parameters included in the INITIAL DIRECT TRANSFER message 200 are described below.

The CN domain ID 202 indicates a domain to be transmitted and has a value indicating either a CS domain or a PS domain. The Intra Domain NAS Node Selector (hereinafter referred to as IDNNS) 204 is a parameter required for selecting a CN node corresponding to the UE when the RNC is connected with multiple CN nodes (MSC or SGSN). to be. If the CN domain ID indicates a CS domain, IDNNS includes a routing parameter based on the Temporary Mobile Station Identity (TMSI). On the other hand, when the CN domain ID indicates the PS domain, IDNNS includes routing parameters based on Packet TMSI (P-TMSI).

The serving RNC (hereinafter referred to as SRNC) that receives the INITIAL DIRECT TRANSFER message 200 selects an MSC or SGSN corresponding to the UE by using the CN domain ID 202 and the IDNNS parameter 204 and selects the selected CN node. Set up the Iu signaling connection with. In addition, the SRNC extracts the NAS message 206 from the INITIAL DIRECT TRANSFER message 200 and stores the NAS message 206 in a Radio Access Network Application Part (RANAP) message and transmits the selected message to the selected MSC or SGSN. The RANAP refers to signaling between the RNC and CN nodes.

3 illustrates a message flow diagram when a PMM-IDLE UE transitions to a CELL-DCH state to establish a connection to a CS domain according to an embodiment of the present invention.

Referring to FIG. 3, in step 310, the UE 300 does not have an Iu-PS signaling connection in the PMM-IDLE state, and thus the SRNC 301 does not have information about the UE 300 in an MBMS service context. not. In step 320, the NAS layer of the UE 300 generates an initial NAS message (eg, a configuration module (CM) SERVICE REQUEST message, etc.) for a service request to the CS domain. In order to deliver the NAS message to the corresponding CN node, the MSC, the RRC layer of the UE 300 uses an INITIAL DIRECT TRANSFER message. If the UE 300 participates in the MBMS service and is in the PMM-IDLE state, the MBMS participation indicator set to on and IDNNS based on the P-TMSI are further included in the INITIAL DIRECT TRANSFER message. Further including means that the INITIAL DIRECT TRANSFER message already includes IDNNS based on TMSI of CS domain.

Meanwhile, in another embodiment, when the INITIAL DIRECT TRANSFER message includes IDNNS based on P-TMSI, the UE 300 may request that the UE 300 requests to connect to the PS domain by the IDNNS. The indicator may be omitted.

In step 320, when the SRNC 301 receives the INITIAL DIRECT TRANSFER message and confirms that the MBMS participation indicator set to on is included, the SRNC 301 prepares to transmit the MBMS SERVICE LIST REQUEST message. In addition, the SGSN 302 is selected to transmit an MBMS SERVICE LIST REQUEST message from IDNNS included in the INITIAL DIRECT TRANSFER message. The SRNC 301 transmits an MBMS Service List request message to the selected SGSN 302 in step 330, and includes an MBMS service list response including MBMS service identifier information in which the UE 300 participates from the SGSN 302 in step 331. Receive the message. In this case, the MBMS service identifier information is a list of MBMS service identifiers indicating MBMS services in which the UE participates, and thus, steps 330 and 331 are referred to as MBMS Service List procedures.

Then, in step 340, the SRNC 301 adds the information of the UE 300 to the corresponding MBMS service context according to the MBMS service identifier information. Alternatively, the MBMS service identifier information is stored in the UE context of the UE 300. Then, when the SESSION START REQUEST message is received from the SGSN 302, the RNC 301 delivers a dedicated paging message through the DCCH to the corresponding UEs using the MBMS service context or the UE context, thereby providing an MBMS service. Announce that it has started.

4 illustrates a message flow diagram when a UE which is in a PMM-CONNECTED state and does not have a PS RAB transitions to a CELL-DCH state to establish a connection to a CS domain according to an embodiment of the present invention.

Referring to FIG. 4, in step 410, the UE 400 has an Iu-PS signaling connection in a PMM-CONNECTED state but does not have a PS RAB, so that the SRNC 401 has information about the UE 400 in an MBMS service context. Don't have In step 420, the NAS layer of the UE 400 generates an initial NAS message, for example, a CM SERVICE REQUEST message, to make a service request to the CS domain. The RRC layer of the UE 400 uses the INITIAL DIRECT TRANSFER message to deliver the NAS message to the corresponding CN node, the MSC. If the UE 400 is participating in the MBMS service and is in the PMM-CONNECTED state and does not have the PS RAB, the MBMS participation indicator set to on is included in the INITIAL DIRECT TRANSFER message.

In step 420, if the SRNC 301 receives the INITIAL DIRECT TRANSFER message and confirms that the MBMS participation indicator set to on is included, the SRNC 301 prepares to transmit the MBMS SERVICE LIST REQUEST message. The SRNC 401 also selects an SGSN 402 having an Iu-PS signaling connection for the UE 400 and exchanges MBMS Service List request and response messages with the selected SGSN 402 in steps 430 and 431. The steps 430 and 331 are for providing the MBMS service identifier information in which the UE 400 participates from the SGSN 402 to the SRNC 401, which is called an MBMS Service List procedure.

The SRNC 401 that has received the MBMS service identifier information in which the UE 400 participates through the MBMS Service List procedure adds the information of the UE 400 to the MBMS service context corresponding to the MBMS service identifier information in step 440. Let's do it. Alternatively, the MBMS service identifier information is stored in the UE context of the UE 400. Subsequently, when a SESSION START REQUEST message is received from the SGSN 402, the RNC 401 transfers a dedicated paging message through DCCH to the corresponding UEs using the MBMS service context or the UE context and MBMS service. Announce that it has started.

Briefly explaining the main points of the embodiments of the present invention shown in Figures 3 and 4 as follows.

1) In case of PMM-IDLE

-Add MBNN participation indicator and IDNNS based on P-TMSI to INITIAL DIRECT TRANSFER message for MBMS service,

Add IDNNS based on P-TMSI to INITIAL DIRECT TRANSFER message for MBMS service.

2) PMM-CONNECTED and PS RAB does not exist

Add the MBMS Participation Indicator to the INITIAL DIRECT TRANSFER message for the MBMS service.

3) In case of PMM-CONNECTED mode and PS RAB exists

There is no added parameter for MBMS service.

In the PMM-IDLE mode, since the MBMS Service List procedure uses a connectionless IuPS signaling connection, the MBMS Service List request / response messages include additional parameters such as UE ID, RNC ID, and SGSN ID. If the PMM-CONNECTED mode and no PS RAB is present, the MBMS Service List procedure uses a Connection Oriented Iu PS signaling connection and thus does not require the additional parameters.

Hereinafter, operations for the preferred embodiments of the present invention will be described in detail with reference to FIGS. 5 to 7.

5 is a flowchart illustrating the operation of a UE according to a preferred embodiment of the present invention.

Referring to FIG. 5, the UE checks whether there is a first NAS message to be transmitted to the CS domain in step 500. If there is the first NAS message to be transmitted to the CS domain as a result of the check of step 500, the process proceeds to step 505. In step 505, it is determined whether the first NAS message is for establishing a connection to a CS domain for a location area update procedure. If so, the operation for the MBMS service ends regardless of the PMM status of the UE. If the first NAS message is not for location area update, the flow proceeds to step 510. In step 510, the RRC layer of the UE sets the CN domain ID to "CS Domain" and then proceeds to step 520. In another embodiment, if there is the first NAS message to be transmitted to the CS domain, the UE proceeds directly to step 510.

In step 520, the UE determines whether there is a participating MBMS service. If the UE does not participate in the MBMS service, the operation ends. If the UE participates in the MBMS service, the process proceeds to step 530. In step 530, the UE checks whether the current PMM_Connected state. If it is not the PMM_Connected state, that is, the PMM-IDLE state, the process proceeds to step 560. If the UE is in the PMM-Connected state, in step 540, it is checked whether a RAB exists for connection with the PS domain. If the PS-RAB does not exist in the PMM_Connected state, the process proceeds to step 550. If the UE is in the PMM-Connected mode and the PS-RAB exists, the operation ends.

In step 550, the UE follows the procedure described in detail with reference to FIG. That is, in step 550, the UE generates an INITIAL DIRECT TRANSFER message including the NAS message and the CN domain ID. Since the PMM status is PMM-CONNECTED and PS RAB is not set, the MBMS participation identifier is added to the INTIAL DIRECT TRANSFER message for the MBMS service.

In step 560, the UE follows the procedure described in detail with reference to FIG. That is, in step 560, the UE generates an INITIAL DIRECT TRANSFER message including the NAS message and the CN domain ID. Since the PMM state is PMM-IDLE, the MBMS participation identifier and IDNNS are added to the INTIAL DIRECT TRANSFER message for the MBMS service. In other cases, only IDNNS is added to the INTIAL DIRECT TRANSFER message. In another case, instead of the IDNNS, the RNC adds another identifier for identifying the SGSN.

6 is a flowchart illustrating the operation of a serving RNC (SRNC) according to a preferred embodiment of the present invention.

Referring to FIG. 6, in step 600, the SRNC receives an INTIAL DIRECT TRANSFER message from the UE requesting connection establishment to the CS domain. The CN domain ID of the INITIAL DIRECT TRANSFER message is set to "CS Domain". In step 610, the SRNC checks whether an MBMS participation indicator is included in the INTIAL DIRECT TRANSFER message. If the MBMS participation indicator is included, go to step 620; otherwise, go to step 650.

In step 620, the SRNC checks whether the MBMS participation indicator is set to on. If it is not set to on, the operation ends. If it is set to on, the process proceeds to step 630 to determine whether there is a preset PS signaling for the UE. If there is PS signaling, the process proceeds to step 640, otherwise the process proceeds to step 660.

In step 650, the SRNC checks whether the INTIAL DIRECT TRANSFER message includes IDNNS for accessing the PS domain, that is, IDNNS based on P-TMSI. In this case, the inclusion of IDNNS based on P-TMSI means that PS signaling does not exist for the UE. If the IDNNS based on the P-IMSI is not included, the operation ends.

When the MBMS participation indicator set to on in the INTIAL DIRECT TRANSFER message includes PS signaling for the UE, in step 640, the SRNC requests the MBMS service identifier information to the corresponding SGSN connected through the PS signaling. Send an MBMS SERVICE LIST REQUEST message. If the INTIAL DIRECT TRANSFER message includes IDNNS for a PS domain or MBMS participation indicator set to on and there is no PS signaling for the UE, in step 660, the SRNC indicates a corresponding SGSN from the IDNNS. After selecting the step 640 is performed.

7 is a flowchart illustrating the operation of an SGSN according to an embodiment of the present invention.

Referring to FIG. 7, in step 700, the SGSN checks whether an MBMS Service List Request message is received from the RNC. When receiving the MBMS SERVICE LIST REQUEST message, in step 710, the SGSN searches for the MBMS UE context corresponding to the UE requesting the message. If there is an MBMS UE context corresponding to the UE requesting the message, in step 720, SGSN extracts MBMS service identifiers of the UE and generates MBMS service identifier information including the extracted identifiers. In step 730, the MBMS SERVICE LIST RESPONSE message including the generated MBMS service identifier information is transmitted to the RNC.

On the other hand, if there is no MBMS UE context corresponding to the UE requesting the message, in step 740, the SGSN includes the empty MBMS service identifier information in the MBMS SERVICE LIST RESPONSE message and transmits it to the RNC. In another embodiment, in step 740, the MBMS SERVICE LIST FAILURE message is transmitted to the corresponding RNC.

As described above, in the detailed description of the present invention, specific embodiments have been described. However, various modifications may be made without departing from the scope of the present invention. Therefore, the scope of the present invention should not be limited to the described embodiments, but should be determined not only by the scope of the following claims, but also by those equivalent to the scope of the claims.

According to the present invention, when UEs joining an MBMS service make a call for a circuit service or a packet service, it is possible to prevent a problem of not receiving a call of the MBMS service in the RRC access mode, thereby increasing the success rate and reliability of the MBMS call. It has an effect.

In addition, according to the present invention, in the case of the UE in the PMM-IDLE / RRC CONNECTED mode in providing the MBMS service, the MBMS service linking information of the UE is maintained in the RNC and SGSN can effectively provide the MBMS service .

1 is a diagram showing a network configuration for a multicast multimedia broadcasting service.

2 is a simplified structure of an INITIAL DIRECT TRANSFER message applied to the present invention.

3 is a diagram illustrating a procedure for transmitting related information on an MBMS service from a UE to an RNC according to an embodiment of the present invention.

4 is a diagram illustrating a procedure for transmitting related information on an MBMS service from a UE to an RNC according to another embodiment of the present invention.

5 is a flowchart illustrating operation of a UE according to a preferred embodiment of the present invention.

6 is a flowchart illustrating the operation of an RNC in accordance with a preferred embodiment of the present invention.

7 is a flowchart illustrating operation of an SGSN in accordance with a preferred embodiment of the present invention.

Claims (8)

A base station communicating with user terminals in a cell, a radio network controller (RNC) providing packet service and line service to the user terminals by controlling communication between the base station and the user terminals, and a service node managing the wireless network controller. In the mobile communication system for providing a multicast multimedia broadcasting (MBMS) service to the plurality of user terminals, Method of managing service information for the terminals, After the at least one MBMS service joins the user terminal in the packet service standby mode, the routing information for the packet service is included in the request message for establishing the connection of the line service and transmitted to the wireless network controller; Acquiring, by the radio network controller, service identifier information of the at least one MBMS service in which the user terminal participates in response to the routing information of the request message; And storing the obtained service identifier information for the user terminal. The method of claim 1, wherein the request message, And the service participation indicator indicating that there is at least one MBMS service joined by the user terminal. The method of claim 1, wherein the storing is performed. The obtained service identifier information is included in the user terminal context for the user terminal or at least one service context for each of the at least one MBMS service. The method of claim 1, wherein the acquiring The wireless network controller selects a corresponding service node with reference to the routing information included in the request message, requests the service identifier information from the selected service node, and receives the service identifier information from the service node. Characterized in that the method. The method of claim 1, wherein the transmitting of the Determine whether the request message is a message for requesting connection establishment for a location area update, and if not, include routing information for the packet service in the request message. A base station communicating with user terminals in a cell, a radio network controller (RNC) providing packet service and line service to the user terminals by controlling communication between the base station and the user terminals, and a service node managing the wireless network controller. In the mobile communication system for providing a multicast multimedia broadcasting (MBMS) service to the plurality of user terminals, Method of managing service information for the terminals, After joining at least one MBMS service, a user terminal which is in a packet service connection mode and does not have a radio access bearer for packet service, has at least one MBMS service joined by the user terminal in a request message for establishing a connection of a circuit service. Transmitting to the wireless network controller by including a service participation indicator indicating existence; Acquiring, by the wireless network controller, service identifier information of the at least one MBMS service joined by the user terminal in response to the service participation indicator of the request message; And storing the obtained service identifier information for the user terminal. The method of claim 6, wherein the storing is performed. The obtained service identifier information is included in the user terminal context for the user terminal or at least one service context for each of the at least one MBMS service. The method of claim 6, wherein the acquiring And the wireless network controller requests the service identifier information from a service node that is already connected for the packet service of the user terminal, and receives the service identifier information from the service node.