CN1551642A - Connection method for dismantling dedicated Iu signaling for multiple user equipments at the same time - Google Patents

Abstract

A method for dismantling a plurality of user equipment dedicated signaling connections at the same time, comprising the steps: when the session ends, the RNC uses the service signaling connection to send signaling, initiates an 'Iu release request', and notifies the SGSN of the user equipment identity to be dismantled; The SGSN also uses the service signaling connection to send signaling to inform the RNC that the user ID of the dedicated signaling connection can be removed; the RNC uses the service signaling connection to send signaling to notify the SGSN user equipment of the removal of the dedicated signaling connection. The invention provides a method for dismantling dedicated signaling connections of multiple user equipments at the same time, which reduces the signaling interaction load between RNC and SGSN and effectively utilizes resources.

Description

Connection method for dismantling dedicated Iu signaling for multiple user equipments at the same time

technical field

The invention relates to a third generation mobile communication system, in particular to a connection method for dismantling dedicated Iu signaling of multiple user equipments at the same time.

Background technique

MBMS is a new service for which relevant standards are being formulated in the third generation mobile communication system partnership project for standardization. The MBMS service is a one-way point-to-multipoint service (that is, multimedia data broadcast from a single data source is sent to multiple users for reception through network transmission). The biggest feature of this kind of business is that it can effectively utilize wireless resources and network resources. MBMS services are mainly used in wireless communication network systems, such as wideband code division multiple access communication systems and global mobile communication systems. The transmission of business data in MBMS basically goes through several processes: data source transmission, intermediate network transmission, destination cell air transmission, and user reception. Fig. 3 is a logical network equipment diagram of a wireless communication system capable of providing MBMS services. In this figure, MBMS actually utilizes a General Packet Radio Service (hereinafter referred to as GPRS) network as a core transmission network. As shown in Figure 3, the broadcast and multicast service center (hereinafter referred to as BM-SC) is the data source for sending MBMS service data; the gateway GPRS support node (hereinafter referred to as GGSN) is used for the communication between the GRPS network and the external network (such as the Internet network) Connection; in the MBMS business, the gateway GPRS support node connects to BM-SC and sends MBMS data to a specific serving GPRS support node (hereinafter referred to as SGSN); the cell broadcast center is the data source of the cell broadcast, and in MBMS, the cell broadcast center Interconnected with BM-SC, so that the cell broadcast center can provide MBMS service announcement function; SGSN is used for UE access control and mobility management, and at the same time sends MBMS data from GGSN to a specific radio unit controller (hereinafter referred to as RNC) ); RNC is used to control a group of base stations and transmit multimedia data to a specific base station; the base station establishes an air physical channel for the MBMS service of a certain cell under the control of RNC; user terminal equipment (hereinafter referred to as UE) is Terminal equipment that receives MBMS data.

Figure 4 shows the entire process of the MBMS service from service announcement, user joining, service notification, radio bearer establishment to the final user leaving.

401 Subscription establishes the connection between the user and the service provider, and the authorized user can receive related MBMS services.

402 Service announcement notifies the user of the MBMS service to be provided. For example, the system wants to broadcast a football match in downtown Beijing at 7:00 pm.

403 Join means that the user joins a group, that is, the user tells the network that he or she is willing to receive this multicast service.

404 MBMS session start indicates establishment of network resources for MBMS data transmission.

405 The MBMS notification informs the user of the upcoming MBMS data transmission.

406 Data transmission indicates the process of transmitting MBMS service data to the user.

407 MBMS session end indicates that the network resources are released after the MBMS service data transmission is completed.

408 Leaving corresponds to 403 Joining, indicating that the user wants to leave a group, that is, he no longer wants to receive data from a certain service.

In order to effectively utilize radio resources, the radio unit controller will determine the channel type according to the number of users in each cell. The wireless unit controller saves a critical value for channel type switching between point-to-point and point-to-multipoint. When the number of users subscribing to the MBMS service in the cell exceeds this critical value, the wireless unit controller will convert the channel type to point-to-multipoint, otherwise, it will be point-to-point channel type. However, when the wireless unit controller calculates the number of users, it only accumulates those user equipments in the connected state. That is to say, the RNC will keep the state of some user equipments in the connected state, that is, the PMM_CONNECTED state. Therefore, for a service, the RNC always reserves a certain user equipment in the PMM_CONNECTED state in each cell. When the user equipment is in this state, it means that the user equipment has a radio resource control RRC connection and an Iu signaling connection.

When the MBMS service ends, or the interval between two consecutive sessions is relatively long, or there is no user equipment directly receiving data under the RNC, the SGSN or RNC will decide to connect the Iu signaling connection of these user equipment to the RRC connection Released, so that these user equipments are in the PMM_IDLE state. However, in the prior art, there is only one method for how to remove the Iu signaling connections dedicated to the user equipment: that is, remove them one by one. As shown in Figure 2, when the SGSN requests to tear down the Iu signaling connection of the user equipment, it sends an "Iu release request" message to the RNC. After receiving the message, the RNC releases all resources related to the signaling connection, and then returns an "Iu release complete" message to the SGSN. After receiving the message, the SGSN will actively tear down the underlying signaling connection control part (hereinafter referred to as SCCP connection). Of course, the release of the Iu connection may also be initiated by the RNC. If so, the RNC first sends an "Iu release request" message to the SGSN, requesting the SGSN to tear down the Iu signaling connection of the user equipment. If the SGSN agrees to tear down, then the next process is consistent with the Iu release initiated by the SGSN. Because a dedicated signaling connection is actually an SCCP connection. Therefore, after the signaling interaction is completed, the dismantling of the SCCP must be completed by the SCCP protocol. It can be seen from 205 and 206 that the SGSN sends the SCCP command "release" to the RNC, and then the RNC returns the SCCP command "release complete", thereby completing the release process of the Iu signaling connection.

Meanwhile, in the prior art, when the MBMS service is provided, there is a service Iu signaling connection established for a certain service between the RNC and the SGSN. This signaling connection provides the underlying signaling bearer channel for service-related signaling. The disconnection of this signaling connection may be consistent with the traditional signaling connection disconnection method: that is, the same as the signaling process described in FIG. 2 .

The foregoing solution can complete the release of the signaling connection of the MBMS user equipment, however, the entire release process takes a long time, the signaling load is heavy, and it is easy to cause waste of resources.

Contents of the invention

The purpose of the present invention is to provide a method for dismantling multiple user equipment-specific Iu signaling connections at the same time, and dismantle the dedicated signaling connections of multiple user equipments through MBMS service-specific service signaling connections, so that all Iu signaling connections can be dismantled at one time. Purpose of the MBMS user-specific Iu signaling connection.

In order to achieve the above purpose, a method for simultaneously removing multiple user equipment dedicated signaling connections, comprising steps:

When the session ends, the RNC uses the service signaling connection to send signaling, initiates an 'Iu release request', and notifies the SGSN of the user equipment identity or the corresponding signaling connection identity that it wants to remove;

The SGSN also uses the service signaling connection to send signaling to tell the RNC that the user identifier or the corresponding signaling connection identifier that can be removed from the dedicated signaling connection is available;

The RNC uses the service signaling connection to send signaling to notify the SGSN user equipment that the dedicated signaling connection is to be removed.

The present invention provides a method for dismantling dedicated signaling connections of multiple user equipments at the same time. The effect is to reduce the signaling interaction load between the RNC and the SGSN, and effectively utilize resources.

Description of drawings

Figure 1 is the process of releasing multiple user equipment dedicated signaling connections at the same time:

Figure 2 is the process of releasing the dedicated signaling connection of the user equipment:

FIG. 3 is a schematic structural diagram of the MBMS system;

Fig. 4 is the MBMS multicast service process;

Figure 5 is the node action behavior of RNC:

Figure 6 is the node action behavior of SGSN:

Detailed ways

Figure 1 describes the process of MBMS user equipment dedicated signaling connection release.

When the session ends or the service ends, the SGSN receives the session end instruction from the GGSN and forwards it to the RNC. The SGSN sends a "session end" message 101 to the RNC, which may contain a "release indication". If the "Release Indication" indicates that the user's dedicated connection can be released, then the RNC may initiate 103 an "Iu Release Request". Otherwise, the RNC will continue to reserve the signaling connections of the MBMS service and the signaling connections of these user equipments. The SGSN does not allow these signaling connection releases probably because the interval between sessions is too short. If the service ends, the SGSN shall allow the release of the service signaling connection and user equipment dedicated connection.

If all the connected user equipments under the 102 RNC are moved to other RNCs, it means that the RNC does not provide data transmission to these user equipments. If the resources of the RNC are tight, or because of other radio resource management reasons, it may decide to release the signaling connections of these user equipments, then the RNC can initiate an "Iu release request" and tell the SGSN that it wants to release the dedicated signaling of some user equipments connect. Of course, the RNC can also release the signaling connection for the MBMS service, and the release reason can be "no user equipment" and so on. The RNC includes the "identity of the user equipment or the corresponding signaling connection identity" and the "reason for releasing the service Iu" to be released in the 103 message.

When the SGSN receives 103 "Iu Release Request", the SGSN will check whether the user equipment included in the message has no other services. If not, it indicates that the dedicated signaling connection of the user equipment can be removed. It will include the identities of these user equipments or the corresponding signaling connection identities in 104 "Iu release command". If the SGSN finds that these user equipments have other services, then step 104 cannot contain the identities of these user equipments or the corresponding signaling connection identities. If the RNC requests to release this MBMS service signaling connection, the SGSN will check the reason for the release request by the RNC. If it is because there is no user equipment under the RNC, then the SGSN can release the service signaling connection, and send 104 "Iu Release Command" to the RNC, and the message contains the parameter "Release Reason", indicating that the RNC can release the service signaling order to connect. If the SGSN does not agree to release the service signaling connection, the parameter "Release Reason" cannot be included.

When RNC receives 104 "Iu Release Command", it checks the parameters carried in the message. If it contains "user equipment identification list or corresponding signaling connection identification", it indicates that the SGSN agrees to disconnect the dedicated signaling connections of these user equipments. The RNC releases all resources related to the signaling connection of the UE. If it also carries "Release Reason", it indicates that the SGSN agrees to release the service signaling connection, then the RNC will tear down the resources related to the service signaling connection, and then return 106 "Iu Release Complete" message to the SGSN. At the same time, the RNC sends a "signaling connection release" message to the user equipment that has disconnected the dedicated signaling connection, informing these user equipment that the signaling connection with the SGSN has been disconnected.

When the SGSN receives the 106 "Iu release complete" message, it requires the underlying SCCP layer to tear down the relevant service signaling connection and user equipment dedicated signaling connection. The release of the SCCP connection can be completed by 107 and 108 .

1) Node processing flow of RNC

Stage 501 indicates that the RNC receives messages from the SGSN through the Iu interface.

The 502 stage judges whether the message received by the RNC is "session end", and if so, moves to 503, and if not, moves to 507. At stage 503, the RNC checks whether the "session end" message carries a "release indication". In stage 504, the RNC judges whether the "release indication" is true or false. If it is true, then move to 506, if it is false, then move to 505, since the processing of stage 505 has no close relationship with the present invention, it is omitted here. In stage 506, the RNC waits for further instructions from the SGSN.

The 507 stage judges whether the message received by the RNC is "Iu release order", if yes then moves to 508, if not then moves to 515. In stage 508, it is judged whether the message carries a user equipment identification list or a corresponding signaling connection identification, and the process moves to 509. In stage 509, if 508 carries a user ID, move to 510. Otherwise, move to 511. In stage 510, the RNC deletes the signaling connection resources corresponding to these user equipments. This is consistent with that in the prior art. In stage 511, the RNC checks whether the message carries "reason for release". If there is, move to 512 , otherwise move to 513 . In stage 512 , release the resources related to the service, send an "Iu release complete" message to the SGSN, and move to 514 . And send "Iu release complete" message to SGSN in 513 stage. In stage 514, "signaling connection release" is sent to the user equipment. At stage 515, if the RNC finds that the users of each cell under the RNC are all zero, then turn to 516, otherwise turn to 501. At stage 516, check whether there is a dedicated signaling connection of user equipment that needs to be released, and turn to 517. At stage 517, if there is, turn to 518 , otherwise turn to step 519. In step 518, the RNC sends an "Iu release request" to the SGSN, which contains the user equipment identifier or the corresponding signaling connection identifier. In stage 519, the RNC sends an "Iu release request" to the SGSN, which does not contain the user equipment identity.

2) Node processing flow of SGSN

Stage 601 indicates that the SGSN receives messages from the RNC through the Iu interface or receives messages from the GGSN through the Gn interface.

In stage 602, it is judged whether the message received by the RNC is "session end", if yes, it moves to 603, if not, it moves to 607. In the 603 stage, the SGSN checks whether the service signaling connection corresponding to the service can be removed, and turns to 604 . If yes, turn to 606, otherwise turn to 605. At stage 605, the SGSN sends a "session end" message to the RNC. In stage 606, the SGSN sends a "session end" message to the RNC, and the "release indication" in the message is set to true. Step 607 judges whether the message received by the SGSN is "Iu release request", if yes then moves to 608, if not then moves to 615. In stage 608, it is judged whether the message carries a list of user equipment identifiers or corresponding signaling connection identifiers, and it is checked whether the dedicated signaling connections of these user equipments can be released, and the process moves to 609. In stage 609, if 608 carries a user ID, move to 610. Otherwise, move to 611. At stage 610, the SGSN needs to include these user equipment identities or corresponding signaling connection identities in the "Iu release command". In the 611 stage, the SGSN decides whether the service signaling connection can be released, which can be based on the clock timeout condition, and then turns to 612. In the 612 stage, if the service signaling connection can be released, turns to 613, otherwise turns to 614. In the 613 stage, The SGSN needs to include the "Reason for Release" in the "Iu Release Command". In stage 614, the SGSN sends an "Iu release command" to the RNC. In stage 615, if the SGSN receives "Iu release complete", go to 616, otherwise go to 601. In stage 616, the SGSN releases the service signaling connection and related user equipment dedicated signaling connection according to the situation.

Claims (8)

1, a kind of method of removing a plurality of user equipment specific signalings connections simultaneously comprises step:

RNC utilizes traffic signaling to connect and sends signaling, initiate ' Iu discharges request ', notifies SGSN to want the customer equipment identification of removing;

SGSN also utilizes traffic signaling to connect and sends signaling, tells RNC can remove user ID or corresponding signaling connection identifier that dedicated signaling connects;

RNC utilizes traffic signaling to connect and sends signaling, and notice SGSN user equipment specific signaling connects removes.

2, method according to claim 1 is characterized in that: comprise " discharging indication " in described " conversation end ".

3, method according to claim 1 is characterized in that: comprise " customer equipment identification tabulation or corresponding signaling connection identifier " in described " Iu discharges request ".

4. method according to claim 1 is characterized in that: comprise " customer equipment identification tabulation or corresponding signaling connection identifier " and " release cause " in described " Iu release command ".

5. method according to claim 4 is characterized in that: described " release cause " can be " not having subscriber equipment ".

6. remove the method that a plurality of user equipment specific signalings connect simultaneously for one kind, comprise step: SGSN utilizes traffic signaling to connect and sends signaling, tells RNC can remove user ID or corresponding signaling connection identifier that dedicated signaling connects;

RNC utilizes traffic signaling to connect and sends signaling, and notice SGSN user equipment specific signaling connects removes.

7. method according to claim 6 is characterized in that: comprise " customer equipment identification tabulation or corresponding signaling connection identifier " and " release cause " in described " Iu release command ".

8. method according to claim 7 is characterized in that: described " release cause " comprises " not having subscriber equipment ".

Images