KR100617162B1 - Method of RNC registration for providing point-to-multipoint communication - Google Patents

Abstract

The present invention relates to an RNC registration method for providing a point-to-multipoint communication service for providing broadcast and multicast services while supporting mobility of a terminal. The RNC registration method for providing an MBMS service according to the present invention provides a point-to-multipoint communication service, and connects a core network (CN) providing the service with the core network and a mobile terminal. A mobile communication system including a radio network controller (RNC), comprising: counting the number of terminals using the first radio network controller as a drift radio network controller (DRNC); and If the number of the terminal is more than a predetermined value characterized in that it comprises the step of performing the RNC registration (registration) to the core network connected to the first radio network controller.

MBMS, terminal, radio network controller (RNC), core network (CN), terminal threshold, number of temporary terminals

Description

Method of RNC registration for providing point-to-multipoint communication

1 is a configuration diagram of a UMTS network to which the prior art and the present invention are applied.

2 is a diagram illustrating a connection structure between a UTRAN and a terminal in a UMTS network.

3 is a diagram illustrating a process in which a UMTS network provides a specific MBMS service using a multicast mode and a process in which a specific UE is provided with a specific service.

Figures 4a and 4b is a flow chart illustrating the process of connecting and disconnecting MBMS according to the prior art.

5A and 5B are flowcharts illustrating a process of registering and deleting an MBMS according to the related art.

6 is a view for explaining a preferred embodiment according to the present invention.

The present invention relates to a method for providing a point-to-multipoint communication service, and more particularly, to an RNC registration method for providing an MBMS service for providing broadcast and multicast services while supporting mobility of a terminal. will be.

UMTS (Universal Mobile Telecommunications System) is a third generation mobile communication system that has evolved from the European standard Global System for Mobile Communications (GSM) system.The GSM Core Network (CN) and Wideband Code Division Multiple Access (WCDMA) access technologies It aims to provide a better mobile communication service based on the above.

1 is a block diagram of a UMTS network to which the prior art and the present invention are applied. The UMTS system consists of a terminal, a UTRAN, and a core network (CN: abbreviated as CN). The UTRAN consists of one or more Radio Network Sub-systems (RNS), each of which is managed by one Radio Network Controller (RNC) and RNC. It consists of one or more Node B. Node B is managed by the RNC, the uplink receives information sent from the physical layer of the terminal, the downlink transmits data to the terminal plays a role of an access point of the UTRAN to the terminal. The RNC is responsible for allocating and managing radio resources and acting as an access point to the core network.

2 is a diagram illustrating a connection structure between a UTRAN and a terminal in a UMTS network. In order to receive the service provided by the UMTS, the terminal needs to be connected to the core network, and information on the terminal and the core network is transmitted via the UTRAN. Each terminal connected to the UMTS network is managed by a specific RNC in the UTRAN. At this time, the RNC managing the terminal is called a SRNC (Serving RNC). In other words, SRNC refers to an RNC serving as an access point with a core network for data transmission of a specific terminal. The SRNC plays the role of the second layer of the OSI (Open System Interface) for data coming in through the air interface or transmitted to the terminal, and allocates a radio resource suitable for providing a service. The radio resource management function of the SRNC includes all control functions related to a specific terminal such as transmission channel setting, handover decision, and open loop power control. A terminal accessing the core network through the UTRAN at a specific time has only one SRNC.

In general, one RNC is used for the connection between the UE and the RNC. However, when the UE moves to an area in which another RNC is in charge due to the movement of the UE, the RNC is connected to the SRNC via the RNC of the region where the UE moves.

In FIG. 2, the terminal was initially connected through R1 (RNC 1), but the terminal moved to a cell managed by R2 (RAN 2). After moving to the area managed by R2, the UE is connected to R1 through the Iur interface via R2. The management of the terminal and the role of the access point between the core network are still performed by R1, and R2 performs a partial function of simply routing user data or allocating a code that is a common resource. In the UMTS network, like R2, all RNCs connected to UE except for SRNC are called DRNC (Drift RNC). As such, one terminal may not have a DRNC according to a connection state, and may have one or several DRNCs.

The division of SRNC and DRNC is a logical division related to a specific terminal. Since the relationship between RNC and Node B in UTRAN is dependent, RNC can be distinguished in terms of Node B. That is, to distinguish between the RNC managing Node B itself and other RNCs, the RNC in charge of managing a specific Node B is called a CRNC (Controlling RNC). That is, the RNC connected to the Node B and the Iub and controlling the radio resource of the Node B corresponds to the CRNC of the Node B. In the structure of UTRAN, CRNC and Node B have a one-to-many relationship. The CRNC performs load control and congestion control of traffic in cells managed by the CRNC and admission control and code allocation for new radio links configured in these cells.

In the third layer of the radio protocol located in the RNC and the UE, a radio resource control layer (hereinafter referred to as RRC) layer is defined. The RRC is responsible for controlling transport channels and physical channels in connection with setting, resetting, and releasing radio bearers. In this case, the radio bearer means a service provided by the second layer of the radio protocol for data transmission between the terminal and the RNC, and in general, the setting of the radio bearer is a characteristic of a protocol layer and a channel necessary to provide a specific service. It means a process of defining and setting each specific parameter and operation method.

When the RRC layer of a specific terminal and the RRC layer of the RNC are connected to each other to send and receive an RRC message, the terminal is in an RRC connected mode, and when there is no connection The UE is in an RRC Idle Mode state. When the UE establishes an RRC connection with the RNC, a SRNC (Serving RNC) is generated in the RNC to directly manage the UE, and then the RNC identifies and manages the UE in a cell unit. On the other hand, the UE in the RRC idle mode can not determine the presence of the RNC, the CN (MSC or SGSN) is managed in a larger area unit (Location Area or Routing Area unit) than the cell. That is, the UE in the RRC idle mode is identified only in a large area unit, and in order to receive a normal mobile communication service such as voice or data, the terminal should be in an RRC connected mode by establishing an RRC connection with the RNC.

Hereinafter, a multimedia broadcast / multicast service (hereinafter abbreviated as MBMS) will be described in detail. MBMS refers to providing a streaming or background service to a plurality of terminals using a downlink-only MBMS bearer service. In UTRAN, MBMS bearers use point to multipoint radio bearers and point to point radio bearer services.

MBMS is divided into broadcast mode and multicast mode. The MBMS broadcast mode is a service for transmitting multimedia data to all users in a broadcast area. In this case, the broadcast area refers to an area where a broadcast service is available. MBMS multicast mode, on the other hand, is a service that transmits multimedia data only to a specific user group in a multicast area. In this case, the multicast region refers to an area where a multicast service is available. These multicast areas and broadcast areas are called service areas.

FIG. 3 illustrates a process in which a UMTS network provides a specific MBMS service (service 1) using a multicast mode, and a process in which a specific UE receives a specific service (service 1). First, a UE1 wishing to receive an MBMS service must perform a subscription procedure. In this case, subscription refers to the act of establishing a relationship between a service provider and a user. In addition, the terminal to receive the MBMS service should receive a service announcement (service announcement) provided by the network. Here, the service guide refers to a function of notifying the terminal of a list of services to be provided and related information in the future. The terminal that wants to receive the MBMS service in the multicast mode must specifically join a multicast group. In this case, the multicast group refers to a group of terminals receiving a specific multicast service. And, participation refers to a process in which a terminal joins a multicast group gathered to receive a specific multicast service. Through the participation process, the UE can inform the UMTS network of the intention to receive specific multicast data. On the contrary, a process in which a terminal participating in a specific multicast group terminates participation in the multicast group is called leave. The joining, joining and withdrawing process is a process performed for each terminal. The terminal may perform a subscription, participation, or withdrawal process at any time before, during, or after data transmission.

While a particular MBMS service is in progress, one or more sessions for that service may occur sequentially. When data to be transmitted for a particular MBMS service occurs in an MBMS data source, the CN informs the RNC of a session start. On the other hand, when the MBMS data source no longer has data to transmit for a particular MBMS service, the CN informs the RNC of the session stop. A data transfer process for a particular MBMS service may be performed between session initiation and session abort. In this case, only terminals that participate in the multicast group for a specific MBMS service may receive data transmitted through the data transmission process.

In the session initiation process, the RNC receiving the session initiation from the CN transmits an MBMS notification to the terminals. Here, the MBMS notification refers to a function in which the RNC informs the UE that data transmission of a specific MBMS service is imminent in a cell. The MBMS notification is sent more than once before the actual data of the service is transmitted. The RNC may perform a counting function to determine the number of UEs that want to receive a specific MBMS service in a specific cell using the MBMS notification process. The aggregation function is used to determine whether to set up a wireless bearer that provides a particular MBMS service in a point-to-many, point-to-point or no wireless bearer configuration. To select an MBMS radio bearer, the RNC sets a threshold internally. After performing the aggregation function, the RNC sets up a point-to-point MBMS radio bearer if the number of terminals in the cell is less than the threshold, and sets the point-to-many MBMS radio bearer if the number of terminals in the cell is greater than the threshold. Can be set. After determining the MBMS radio bearer as described above, the RNC informs the terminals of the information of the corresponding radio bearer. When the point-to-point radio bearer is configured for a specific service, all terminals to receive the service are in an RRC connected mode. However, when a point-to-multipoint radio bearer is configured for a specific service, all of the terminals to receive the service need not be in the RRC connected mode. That is, the terminal in the RRC idle mode can also receive the point-to-multipoint radio bearer. However, if there is no terminal for a specific MBMS service as a result of the aggregation, the RNC does not transmit the MBMS data without setting the radio bearer. This is because the RNC configures the radio bearer even if there is no user who wants the service, which is a waste of radio resources.

When the data of the MBMS service is transmitted from the CN for one session of the MBMS service, the RNC starts to transmit data using the configured radio bearer. And when the session is interrupted from the core network, the preset radio bearer is released.

The following describes a terminal linking process and a terminal unlinking process. The terminal connection process is a process of adding the terminal to the RRC connection mode terminal list of the MBMS service (s) subscribed to the terminal among the RRC connection mode terminal list for each MBMS service managed by the RNC. On the other hand, the terminal separation process is a process of deleting the terminal from the RRC connection mode terminal list for the MBMS service (s) subscribed to the terminal among the RRC connection mode terminal list for each MBMS service managed by the RNC.

4A is a diagram for explaining an MBMS attach process. The RNC providing the MBMS service identifies and manages the terminal in the RRC connection mode among the terminals joining the specific MBMS service for each cell in charge thereof. For this purpose, the RNC creates an RRC connected mode terminal list for each MBMS service of each cell. At this time, the RRC connection mode terminal list includes identifiers (URNTI) of terminals participating in a specific MBMS service.

In the MBMS connection process, the MBMS service that is in progress during the MBMS service in which the UE in RRC connected mode is in progress when the UE moves from a cell in charge of the SRNC to a cell in charge of the DRNC or is not in progress in the MBMS service in which the UE participates. For the service, when the terminal receives a session start from the CN for the MBMS service after the terminal moves from the cell that the SRNC is responsible for to the cell that the DRNC is responsible for, the SRNC requests the MBMS connection to the DRNC for the terminal information. By transmitting through the message (S41), the DRNC refers to the process of adding the requested terminal to the RRC connection mode terminal list that it manages for the MBMS service. In this case, the MBMS connection request message includes an ID of a cell to which the terminal moves, an ID of an MBMS service in which the terminal participates, and an identifier (URNTI) of the terminal.

When the DRNC receives an MBMS connection request message for a specific terminal from the SRNC, if the resource can be allocated to the terminal to maintain the RRC connection mode state, the DRNC accepts the MBMS connection request of the terminal, and the terminal The identifier of the terminal is added to the RRC connection mode terminal list for the MBMS service in which the terminal of the moved cell participates. After that, the DRNC transmits an acknowledgment through the MBMS connection response message to the SRNC (S43), and the SRNC receiving the SRNC keeps the terminal in the RRC connected mode even in the cell to which the terminal moves, and stores the MBMS service data. The point-to-point wireless bearer is transmitted to the terminal. That is, the MBMS service data is transmitted to the DRNC through the SRNC and then again to the terminal using a point-to-point radio bearer in the DRNC.

When the DRNC receives an MBMS connection request message for a specific UE from an SRNC, the DRNC does not always accept it. If there is no resource for DRNC to establish an RRC connection to the terminal and maintain the RRC connected mode, the DRNC rejects the MBMS connection request of the terminal and transmits a negative response to the SRNC (S43).

4B is a diagram for explaining an MBMS detach process. In the MBMS detach process, when a UE in an RRC connected mode moves from a cell in which a DRNC is in charge to another cell in charge of another RNC, the SRNC delivers an MBMS detach request message to the DRNC to the DRNC (S45). A process of causing the terminal to delete the terminal making the separation request from the RRC connection mode terminal list managed by the user for the MBMS service. In response to the MBMS separation request of the SRNC, the DRNC transmits an MBMS separation response message (S47). In this case, the MBMS separation request message includes an ID of a cell which is located before the UE moves, that is, a cell that the DRNC is responsible for, an ID of an MBMS service in which the UE participates, and an identifier of the UE (URNTI).

5A is a diagram for explaining an RNC registration process. The RNC registration process is a process in which the RNC informs the CN that the terminal (s) subscribed to a specific service are using the RNC. RRC connection mode state When the UE moves to a cell managed by the RNC without the RRC connection mode terminal list for the MBMS service, the UE informs the RNC that the UE uses the MBMS service through the UE connection process through Iur. The RNC creates a new RRC connection mode list for the MBMS service subscribed to the terminal and adds the terminal. The RNC informs the CN by transmitting an MBMS registration request message to the CN that it should receive a session start message for the MBMS service (S51). In response to the MBMS registration request of the SRNC, the CN transmits an MBMS registration response message (S53).

The RNC registration process can be divided into two cases, an implicit registration process and an explicit registration process. The registration process for the SRNC is implicit. In other words, it may be achieved through a joining process or the like without transmitting the actual MBMS registration request message. If the RNC is a DRNC for a UE subscribed to a specific MBMS service and there is no RRC connection mode terminal list for the MBMS service, an RNC registration process for the DRNC is explicitly performed. In other words, the RNC sends an MBMS registration request message to the CN.

If there is no connection mode terminal in which the RNC subscribes to a specific MBMS service using the RNC as an SRNC, but there is at least one terminal using a radio resource through Iur, the RNC registration process is specified. Is performed as In other words, the RNC sends an MBMS registration request message to the CN. The DRNC sends the MBMS registration request message only to a predetermined CN node.

FIG. 5B is a diagram for explaining an RNC deregistration process. FIG. The RNC registration deletion process is a process in which the RNC registered to a specific MBMS service in the CN informs the CN that the RRC connected mode state terminal subscribed to the MBMS service no longer uses the RNC. The RNC deletes the RRC connected mode terminal list for the MBMS service. The RNC registration deletion process can also be classified into an implicit registration deletion process and an explicit registration deletion process. The deregistration process for SRNC is implicit. In other words, it may be achieved through a terminal separation process or a leaving process without transmitting the actual MBMS registration deletion request message. When the RNC is not used as the SRNC and the role of the DRNC for the UE subscribed to the specific MBMS service is stopped, the RNC registration deletion process for the RNC is explicitly performed. In other words, the RNC transmits an MBMS registration deletion request message to the CN (S55). The CN responds to the RNC's registration deletion request by sending an MBMS registration deletion response message (S57).

In the prior art, when the RNC transmits an MBMS registration request message to a CN, the following problems exist. Conventionally, an RRC connected mode state terminal in which an RNC subscribes to a specific MBMS service using the RNC as an SRNC no longer exists, but a radio resource (i. If at least one terminal using a radio resource exists, the RNC registration process is explicitly performed. In other words, the RNC sends an MBMS registration request message to the CN. However, if the number of terminals using radio resources through the Iur is one or more and less than the threshold for the point-to-point MBMS radio bearer setting, the point-to-point MBMS radio bearer is passed through the Iur even though the MBMS service is not received from the CN. You can continue to receive MBMS service through. In other words, the RNC does not need to send an MBMS registration request message to the CN in order to receive the MBMS service from the CN. This unnecessary message increases the signaling load between the RNC and the CN, resulting in a decrease in network resource utilization efficiency.

The present invention is designed to solve the problems of the prior art as described above, an object of the present invention is that when the RNC proceeds to the RNC registration process to the CN, the RNC subscribes to a specific MBMS service using the RNC as SRNC Although there is no connection mode terminal, the number of UEs that use radio resources through another RNC and Iur belonging to a CN different from the CN to which the RNC belongs exceeds a certain threshold or a new UE additionally moves to the corresponding cell. In this case, the present invention provides an RNC registration method for providing an MBMS service, which includes transmitting an MBMS registration request message.

Summary of the Invention

In one aspect of the present invention, an RNC registration method for providing a point-to-multipoint communication service provides a point-to-multipoint communication service and provides a core network (CN) for providing the service. In a mobile communication system including a core network and a radio network controller (RNC) connecting the core network and a mobile terminal, the first radio network controller is used as a drift radio network controller (DRNC). And counting the number of terminals and performing RNC registration on the core network connected to the first radio network controller when the number of terminals is greater than or equal to a preset value.

In another aspect of the present invention, an RNC registration method for providing a point-to-multipoint communication service provides a point-to-multipoint communication service and provides a core network (CN) for providing the service. In a mobile communication system including a core network (RCC) and a radio network controller (RNC) connecting the core network and a mobile terminal, Radio resource control (RRC) provided in the first radio network controller Adding terminals using the first radio network controller as a drift radio network controller (DRNC) to a list of connected mode terminals, counting the number of the moved terminals, and the number of the terminals; In this case, it is characterized in that it comprises a step of performing the RNC registration (registration) to the core network connected to the first radio network controller.

As another aspect of the present invention, an RNC registration method for providing a point-to-multipoint communication service provides a point-to-multipoint communication service and provides a core network (CN) for providing the service. A mobile communication system comprising a core network and a radio network controller (RNC) connecting the core network and a mobile terminal, wherein the first terminal is selected from a cell controlled by a second radio network controller. Moving to a cell controlled by a radio network controller, releasing a connection by a second terminal using the first radio network controller as a serving radio network controller (SRNC) and the first radio When there is a third terminal that is moved from a cell controlled by a wireless network controller except a network controller to a cell controlled by the first wireless network controller, the first terminal and the third terminal are referred to. 1 wireless network controller And performing RNC registration to the connected core network.

Example

delete

The construction, operation, effects and other features of the present invention will become more apparent by the preferred embodiments of the present invention described below with reference to the accompanying drawings.

In the following description, the number of temporary terminals is used by a radio resource through an Iur interface when there is no RRC connected mode state terminal in which the RNC subscribes to a specific MBMS service using the RNC as a SRNC (Serving RNC). It means the number of terminals. The RNC is used as a DRNC (Drift RNC) of a terminal using a radio resource through an Iur interface.

Hereinafter, the 'terminal threshold' means a threshold value of the number of temporary terminals in which the RNC should perform an RNC registration process from the RNC to the CN to which the RNC belongs. In other words, terminals using radio resources through the CN interface to which the RNC belongs and other RNCs and Iur interfaces belonging to other CNs receive more than one MBMS service through a point-to-point MBMS radio bearer. Receiving the MBMS service is a threshold value of the number of terminals that efficiently use radio resources. The terminal threshold may be a threshold set internally for the point-to-point MBMS radio bearer and the point-to-multipoint MBMS radio bearer set by the RNC, or may be a value newly set to a value smaller than the threshold. The reason for newly setting a value smaller than the threshold is that the RNC registration process and session initiation are made in advance before the point-to-point MBMS radio bearer setup.

6 is a view for explaining a preferred embodiment of the present invention. In Fig. 6, initially UE1, UE2, UE3, ... UEn are all subscribed to a specific MBMS service, and RNC1, RNC2 and RNC3 are each from SGSNs (SGSN1, SGSN2, SGSN3) of different core networks. Receiving the specific MBMS service. RNC1 operates as an SRNC for the RRC connected mode state terminal UE1 and UE4 to UEn, RNC2 operates as an SRNC for the RRC connected mode state terminal UE2, and RNC3 operates as an SRNC for the RRC connected mode state terminal UE3. RNC1, RNC2 and RNC3 perform an implicit RNC registration process with SGSN1, SGSN2 and SGSN3 for the specific MBMS service, respectively, and generate an RRC connected mode terminal list. In other words, the MBMS registration request message is not actually transmitted from RNC1, RNC2 or RNC3 to CN, but each core network to which SGSN1, SGSN2 and SGSN3 belongs receives the MBMS service to RNC1, RNC2 and RNC3 through joining. It can be seen that the terminal exists.

In the next step, the RRC connected mode state terminal UE1 using the RNC1 as the SRNC moves to a cell managed by the RNC2 (①). Through the MBMS attach process from the RNC1 to the RNC2, the RNC2 knows the MBMS service information subscribed to the UE1, and the RNC2 operates as the DRNC of the UE1. In RNC2, an RRC connection mode terminal list for the MBMS service has already been created. Therefore, RNC2 adds UE1 to the RRC connected mode terminal list already created for the MBMS service. Since SGSN2 is a different SGSN than SGSN1, it does not have information about UE1, and it is not known that UE1 uses radio resources through Iur interface and uses RNC2.

Subsequently, when UE2 leaves RNC2 (②), SGSN2 implies that there is no terminal using RNC2 to receive the specific MBMS service and implicitly performs the MBMS registration deletion process. However, UE1 is receiving the specific MBMS service through a point-to-point MBMS radio bearer using RNC2. That is, the specific MBMS service is transmitted to RNC2 through Iur interface via SGSN1 and RNC1 and received by UE1. Therefore, RNC2 does not need to send MBMS registration request message to SGSN2 at this stage.

In the next step, UEs UE3 using RNC3 as SRNC and UEs UE4 to UEn using RNC1 as SRNC additionally move to a cell managed by RNC2 (③④ ⑤). Since the RNC2 has the RRC connection mode terminal list for the specific MBMS service, the UEs UE3 to UEn are added to the RRC connection mode terminal list for the MBMS service, and the DRNC is added to the UEs UE3 to UEn. It works as

If the number of temporary terminals of RNC2 (the number of RRC connected mode state terminals using RNC2 as DRNC and radio resources through Iur) reaches the terminal threshold, RNC2 registers RNC with CN (SGSN2). To perform. The RNC registration is performed by informing the CN that there is a terminal trying to receive a specific MBMS service in a cell managed by the RNC2, and the RNC2 transmits a registration request message to the SGSN2. Even if there is no terminal using RNC2 as an SRNC, that is, only a terminal receiving a service using RNC2 as a DRNC, since the specific MBMS service can be provided to terminals using RNC2 as a DRNC, temporary RNC2 can be provided. If the number of terminals is less than the terminal threshold, the RNC2 prevents unnecessary signaling generated by sending the MBMS registration request message to SGSN2, and RNC2 requests the registration of MBMS to SGSN2 only when the number of temporary terminals of RNC2 reaches the terminal threshold. By transmitting a message, the RNC2 can be used as a DRNC to switch from the existing point-to-point MBMS radio bearer configuration to the point-to-multipoint MBMS radio bearer configuration for terminals receiving services.

As described above, the terminal threshold value may be a threshold set internally for the point-to-point MBMS radio bearer and the point-to-multipoint MBMS radio bearer set by the RNC, or may be a value newly set to a value smaller than the threshold. . The reason for newly setting a value smaller than the threshold is that the RNC registration process and session initiation are made in advance before the point-to-point MBMS radio bearer setup.

In order to compare the number of temporary terminals with the terminal threshold, the number of RRC connected mode state terminals using RNC2 as a DRNC and a radio resource through the Iur interface must be checked once again from the RRC connected mode terminal list. That is, RRC connected mode state terminals using RNC2 as SRNC and RNC2 as DRNC and RRC connected mode state terminals using radio resources through Iur interface by one RRC connected mode terminal list for a specific MBMS service. In case of managing together, it is troublesome to check the RRC connection mode terminal list in order to grasp the number of temporary terminals. In order to reduce the time and load required at this time, it is desirable to divide the RRC connection mode terminal list into two lists.

First, the RRC-SRNC connected mode terminal list is a terminal list for a specific MBMS service subscribed to by an RRC connected mode state terminal using RNC2 as an SRNC.

Second, the RRC-DRNC connected mode terminal list is a terminal list for a specific MBMS service subscribed to by the RRC connected mode state terminal using RNC2 as a DRNC and using radio resources through an Iur interface.

If the RRC connection mode terminal list is managed by dividing the above two types, the number of terminals managed by the RRC-DRNC connection mode terminal list becomes the number of temporary terminals, so the number of temporary terminals is greater than that of using one RRC connected mode terminal list. This can reduce the time and effort to identify the problem.

As an embodiment different from the above embodiment, while one UE is receiving the specific MBMS service using RNC2 as a DRNC by using a radio resource through an Iur interface, the other UE is connected through an MBMS attach process. If it is detected that the newly moved to RNC2, it is also possible to consider the method of performing the RNC registration by sending an MBMS registration request message to the CN immediately.

Referring to FIG. 7 in more detail, when UE1 moves to a cell managed by RNC2 and receives the specific MBMS service using RNC2 as a DRNC (①), when UE2 leaves RNC2 (②), SGSN2 indicates the above. It is determined that the terminal using RNC2 does not exist to receive a specific MBMS service, and implicitly performs the MBMS registration deletion process. In this case, RNC2 needs to perform RCN registration by sending MBMS registration request message to SGSN2. In the process, when UE3 moves to a cell managed by RNC2 (③), RNC2 performs RNC registration for UE1 and UE3. In the embodiment shown in FIG. 7, the procedure of comparing the number of temporary terminals with the terminal threshold can be omitted, thereby simplifying the procedure compared to the embodiment shown in FIG. 6 and reducing the number of signaling compared to the prior art. It has an effect.

It is apparent to those skilled in the art that the present invention can be embodied in other specific forms without departing from the spirit and essential features of the present invention. Accordingly, the above detailed description should not be construed as limiting in all aspects and should be considered as illustrative. The scope of the invention should be determined by reasonable interpretation of the appended claims, and all changes within the equivalent scope of the invention are included in the scope of the invention.

According to the present invention, when the RNC proceeds with the RNC registration process to the CN, when the terminal moves from one RNC to another RNC to minimize the transmission of the signaling message required for the RNC registration process to prevent an increase in network load between the RNC There is an effect that can increase the efficiency of using the network.

Claims (21)

It provides a point-to-multipoint communication service, and provides a core network (CN) for providing the service and a radio network controller (RNC) for connecting the core network (CN) with a mobile terminal. In a mobile communication system comprising, Counting the number of terminals using the first radio network controller as a drift radio network controller (DRNC); And Performing RNC registration to a core network (CN) connected with the first radio network controller when the number of terminals is greater than or equal to a preset value; RNC registration method for providing a point-to-multipoint communication service comprising a. The method of claim 1, RNC registration for providing a point-to-multipoint communication service, characterized in that the RNC registration is performed only when there is no terminal using the first radio network controller as a serving radio network controller (SRNC). Way. The method of claim 1, The preset value is the same as a threshold for distinguishing and setting a point-to-point radio bearer and a point-to-multipoint radio bearer for providing the specific MBMS service. RNC registration method for providing point-to-multipoint communication services. The method of claim 1, The preset value is an RNC for providing a point-to-multipoint communication service, characterized in that the threshold value is smaller than a threshold for distinguishing and setting a point-to-point wireless bearer and a point-to-multiple radio bearer for providing the specific MBMS service. How to register. The method of claim 1, The performing of the registration further includes detecting a temporary terminal moving from the wireless network controller except the first wireless network controller to the first wireless network controller. How to register RNC to provide communication service The method of claim 5, wherein RNC registration method for providing a point-to-multipoint communication service characterized in that the movement detection for the terminal is made through the MBMS attach process of the first wireless network controller and the second wireless network controller. . The method of claim 1, The RNC registration is the RNC registration method for providing a point-to-multipoint communication service, characterized in that the first radio network controller performs the MBMS registration request message to the core network. A mobile terminal that provides a point-to-multipoint communication service and includes a core network (CN) for providing the service and a radio network controller (RNC) for connecting the core network and a mobile terminal. In a communication system, Adding terminals using the first radio network controller as a drift radio network controller (DRNC) to a radio resource control (RRC) connection mode terminal list included in the first radio network controller; Counting the number of the moved terminals; And Performing RNC registration to a core network connected to the first radio network controller when the number of terminals is greater than or equal to a preset value; RNC registration method for providing a point-to-multipoint communication service comprising a. The method of claim 8, The radio resource control (RRC) connection mode terminal list An RNC registration method for providing a point-to-multipoint communication service comprising an RRC-SRNC connection mode terminal list and an RRC-DRNC connection mode terminal list. The method of claim 8, wherein adding the moved terminals is performed. The RNC registration method for providing a point-to-multipoint communication service, characterized in that for adding the mobile terminal to the RRC-DRNC connected mode terminal list. The method of claim 8, The preset value is the same as a threshold for distinguishing and setting a point-to-point radio bearer and a point-to-multipoint radio bearer for providing the specific MBMS service. RNC registration method for providing point-to-multipoint communication services. The method of claim 8, The preset value is an RNC for providing a point-to-multipoint communication service, characterized in that the threshold value is smaller than a threshold for distinguishing and setting a point-to-point wireless bearer and a point-to-multiple radio bearer for providing the specific MBMS service. How to register. The method of claim 8, The RNC registration is the RNC registration method for providing a point-to-multipoint communication service, characterized in that the first radio network controller performs the MBMS registration request message to the core network. A mobile terminal that provides a point-to-multipoint communication service and includes a core network (CN) for providing the service and a radio network controller (RNC) for connecting the core network and a mobile terminal. In a communication system, Moving, by the first terminal, from a cell controlled by the second radio network controller to a cell controlled by the first radio network controller; Disconnecting, by a second terminal using the first radio network controller as a serving radio network controller (SRNC); And When there is a third terminal moved from a cell controlled by a wireless network controller except the first wireless network controller to a cell controlled by the first wireless network controller, the first terminal and the third terminal. Performing RNC registration to a core network connected to the first radio network controller for RNC registration method for providing a point-to-multipoint communication service comprising a. The method of claim 14, And after the first terminal moves, recognizing MBMS service information for the first terminal through an MBMS attach process between the first wireless network controller and the second wireless network controller. RNC registration method for providing point-to-multipoint communication services. The method of claim 14, The RNC registration is performed by delivering an MBMS registration request message to the core network. delete delete delete delete delete

Images