KR20070111398A - Method and system for signaling release cause indication in a umts network - Google Patents

Abstract

A method for processing a signaling release indication cause in a UMTS(Universal Mobile Telecommunications System) network and a system are provided to convert an RRC(Radio Resource Control) connection mode into an efficient battery state or mode and to ensure that a network does not consider a signaling release indication as an alarm if a cause of the signaling release indication is a UE(User Equipment) idle conversion request. A UE checks whether an abnormal state exists(912). If so, the UE transmits a signaling connection release indication(914). If the abnormal state does not exist, the UE decides whether data transmission is terminated(920). If so, a cause field for the signaling release indication is added, and the UE transmits a signaling connection release indication which includes a request for idle conversion(922). The UE completes the procedure(930).

Description

METHOD AND SYSTEM FOR SIGNALING RELEASE CAUSE INDICATION IN A UMTS NETWORK}

1 is a block diagram illustrating RRC states and transitions.

2 is a schematic diagram of a UMTS network showing various UMTS cells and URAs.

3 is a block diagram illustrating various steps of RRC connection establishment.

4A is a block diagram of an exemplary switch between CELL_DCH connected mode state and an idle mode initiated by UTRAN in accordance with current methods.

4B is an exemplary block diagram illustrating a transition from CELL_DCH connected mode state to idle mode using a signaling release indication.

FIG. 5A is an exemplary block diagram illustrating the transition from CELL_DCH inactivity to CELL_FACH inactivity, and to the idle mode initiated by the UTRAN. FIG.

5B is a block diagram of an example switch between CELL_DCH inactive state and idle mode using signaling release indication.

6 is a block diagram of a UMTS protocol stack.

7 is an exemplary UE that may be used in connection with the method of the present invention.

8 is an exemplary network utilized in connection with the method and system of the present invention.

9 is a flow diagram illustrating steps of adding a cause for a signaling connection release indication at a UE.

10 is a flow diagram illustrating steps taken by a UE upon receiving a causal signaling disconnection indication.

TECHNICAL FIELD The present invention relates to radio resource control between a user equipment (UE) and a universal terrestrial radio access network (UTRAN), and in particular, to the release of existing signaling connections in a UMTS network.

Universal Mobile Telecommunications System (UMTS) is a broadband packet-based system for the transmission of text, digitized voice, video and multimedia. This is a major contribution to third generation standards and is generally based on wideband code division multiple access (W-CDMA).

In a UMTS network, the radio resource control (RRC) portion of the protocol stack is responsible for the allocation, configuration and release of radio resources between the UE and the UTRAN. This RRC protocol is described in detail in the 3GPP TS 25.331 standard. Two basic modes in which a UE can be defined are defined as "idle mode" and "UTRA connected mode". UTRA stands for UMTS Terrestrial Radio Access. In idle mode, whenever a UE wants to send any user data, or whenever the UTRAN or Packet Switching Support Node (SGSN) pages the UE to receive data from an external data network such as a push server, In response, the UE is required to request an RRC connection. The behavior of idle mode and connected mode is described in detail in 3GPP specifications TS 25.304 and TS 25.331.

When in the UTRA RRC connected mode, the device may be in one of four states:

CELL_DCH: In this state, dedicated channels are allocated to the UE in the uplink and the downlink for exchanging data.

CELL FACH: In this state, no dedicated channel is assigned to the user device. Instead, common channels are used to exchange small amounts of burst data. The UE must perform an action as outlined in 3GPP T2 25.331, which includes cell selection processing as defined in 3GPP TS 25.304.

CELL_PCH: The UE uses Discontinuous Reception (DRX) to monitor broadcast messages and pages over the Paging Indication Channel (PICH). No uplink activity is possible. The UE must perform an action as outlined in 3GPP T2 25.331, which includes cell selection processing as defined in 3GPP TS 25.304. After cell reselection, the UE must perform a cell update (CELL UPDATE).

URA_PCH: The UE uses discontinuous reception (DRX) to monitor broadcast messages and pages over a paging indication channel (PICH). No uplink activity is possible. The UE must perform an action as outlined in 3GPP TS 25.331, which includes cell selection processing as defined in 3GPP TS 25.304. This state is similar to CELL_PCH except that the URA UPDATE procedure is only triggered through UTRAN registration area (URA) reselection.

The transition from idle mode to connected mode and from connected mode to idle mode are controlled by the UTRAN. When the UE in idle mode requests an RRC connection, the network determines whether to move the UE to CELL_DCH state or CELL_FACH state. If the UE is in the RRC connected mode, the network determines when to release the RRC connection again. In addition, the network may, in some cases, move the UE from one RRC state to another RRC state before or instead of disconnecting the connection. Typically, state transitions are triggered by data activation or data inactivity between the UE and the network. Since the network does not know when the UE completes the data exchange in a given application, the RRC connection is typically maintained for some time when more data is expected from / to the UE. Typically this is done to reduce delays in call setup and subsequent radio bearer setup. The RRC connection release message can only be sent by the UTRAN. This message releases the signal link connection and all radio bearers between the UE and the UTRAN.

The problem with the above is that even if the application on the UE completes its data exchange and does not expect any further data exchange, the application on the UE is still waiting for the network to move itself to the correct state. The network may not even know that the application on the UE has completed its data exchange. For example, an application on a UE may exchange data with a server of its application connected to the UMTS core network using an acknowledgment-based protocol. Examples are applications that run over UDP / IP, where the applications themselves implement protected delivery. In this case, the UE knows whether the application server is sending or receiving all data packets, determines whether any further data exchange has occurred, so that the RRC connection associated with the packet service (PS) domain is terminated. You are in a better position to determine your point of view. The UTRAN controls when the RRC connection state changes to another state, or changes to the idle mode, and because of the fact that the UTRAN does not know the state of the data transfer between the UE and the external server, the UE is better than the required state or mode. High data rates and strong battery conditions are required to waste battery life. This also wastes radio resources due to the fact that radio bearer resources remain unnecessarily occupied.

The solution to the above-described problem is to include a UE for transmitting a signaling release indication to the UTRAN when the UE recognizes that data conversion is complete. According to section 8.1.14.3 of the 3GPP TS 25.331 specification, the UTRAN releases the signaling connection when receiving a signaling release indication from the UE, causing the UE to switch to idle mode. A problem with the foregoing is that the signaling release indication may be considered an alarm. Typically, the network expects a signaling release indication only when a GMM service request failure, a RAU failure, or a connection failure occurs. Raising an alarm when the UE requests to release signaling leads to inefficient performance monitoring and alarm monitoring in the network.

Reference will be made to the drawings to aid in understanding the invention.

The present invention provides a system and method for switching from an RRC connected mode to a more efficient battery state or mode and ensuring that the network does not consider the signaling release indication to be an alarm if the cause of the signaling release indication is a UE idle switch request. In particular, the present invention provides a method and apparatus for switching based on either the UE initial termination of the signaling connection in the designated core network domain or an indication to the UTRAN where the transition from one connected state to another occurs. The following description will describe an exemplary implementation of UMTS. However, it should be noted that the teachings of the present invention are similarly applicable to other wireless communication systems.

In particular, if an application on the UE determines that the exchange of data has been completed, this may send a "complete" indication to the "RRC Connection Manager" element of the UE software. The RRC connection manager is responsible for all existing applications (including those that provide services over one or multiple protocols), associated packet data protocol (PDP) contexts, associated packet switched (PS) radio bearers, and associated circuit switched (CS). Tracks radio bearers. The PDP context is a logical relationship between the UE and the PDN (public data network) running across the UMTS core network. One or multiple applications (eg, email application and browser application) on the UE may be associated with one PDP context. In some cases, one application on the UE may be associated with one first PDP context and multiple applications may be related to second PDP contexts. The RRC Connection Manager receives "complete" indications from different applications on the UE that are simultaneously active. For example, a user may receive an email from a push server while doing web browsing. After sending an acknowledgment, the email application may indicate that it has completed its data transaction, but the browser application may not be able to send such an indication. Based on the composite state of such indications from active applications, the UE software can determine how long to wait before being able to initiate signaling disconnection of the core network packet service domain. In this case a delay can be introduced to ensure that the application ends the data exchange correctly and does not require an RRC connection. The delay can be dynamic based on traffic history and / or application profile. Whenever an RRC connection manager uses a probability to determine that no application is expecting a data exchange, it can send a signaling disconnection indication procedure to the appropriate domain (eg, PS domain). Alternatively, the RCC connection manager may send a request for state transition to the UTRAN within the connected mode.

In addition, the foregoing decision may take into account whether the network supports the URA_PCH state and transition to this state.

The UE-initiated transition to idle mode may occur from any state of the RRC connected mode, with the network releasing the RRC connection going to idle mode and ending. As will be clear to those skilled in the art, the battery of the UE in idle mode is much less powerful than the battery of the UE in the connected state.

However, by sending a signaling release indication, the network may consider that an alarm has occurred. If the signaling release indication is the result of an RRC that determines that no traffic is expected, in a preferred embodiment, the network can distinguish that the signaling release indication is the result of the requested idle switch as opposed to an abnormal condition. . This distinction makes indicators such as key performance indicators (KPIs) more accurate, improving performance monitoring and alarm monitoring.

The method of the present invention makes it possible for the UE to add a field to the existing signaling release indication which provides the cause for the signaling release indication. The network may then use the added field to filter out the exact alarm conditions from the situation that the UE is requesting to inject into the idle state because the UE does not expect any subsequent data. This improves the efficiency of alarm monitoring and performance monitoring, and by moving faster to idle mode, the UE continues to save battery resources.

Therefore, the application of the present invention provides a method for processing a cause of a signaling release indication between a user device and a wireless network, comprising: monitoring at the user device whether a signaling connection release indication should be sent to the wireless network; ; At the user device, adding a cause for the signaling disconnection indication to the signaling disconnection indication; Sending the added signaling ring release indication to the wireless network; Receiving the signaling disconnection indication in the wireless network; Filtering the cause of the signaling release indication to determine whether to generate an alarm.

The application of the present invention further includes a system adapted to process a cause for signaling release indication, comprising: a user device having a wireless subsystem comprising wireless communication adapted to communicate with a UMTS network; A wireless processor having a digital signal processor and adapted to interact with the wireless subsystem; Memory; A user interface; A processor adapted to execute the user application and to interact with the memory, the wireless communication and the user interface, and adapted to execute the application, wherein the user device monitors whether signaling disconnection indication instructions should be sent to the wireless network; ; Adding a cause for the signaling disconnection indication to the signaling disconnection indication; Receiving means for transmitting a signaling disconnection indication added to a wireless network adapted to communicate with the user device, receiving the signaling disconnection indication; And means for filtering said cause to determine whether an alarm will occur.

The application of the present invention further includes a method of processing the cause of the signaling release indication at the user device for improved alarm tracking in the wireless network, comprising: monitoring whether the signaling connection release indication should be sent to the wireless network; Adding a cause for the signaling connection release indication to the signaling connection release indication; Sending a signaling disconnection indication added to the wireless network, wherein the wireless network is provided in accordance with an indication of the cause of the signaling disconnection indication.

The application of the present invention further includes an apparatus for a user device that facilitates the release of the signaling connection. The checker is configured to check whether the signaling disconnection indication has been sent. The signaling disconnection indication transmitter is configured to send a signaling disconnection indication in response to an indication by the checker whether a signaling disconnection indication instruction has been sent. The signaling connection release indication includes a signaling release indication cause field.

The application of the present invention further includes a network device operating with signaling disconnection indication. The investigator is configured to examine the signaling release indication cause field of the signaling connection release indication. The investigator checks whether the signaling release indication cause field indicates an abnormal state. The alarm generator is optionally configured to generate an alarm upon determining by the investigator that the signal release indication cause field indicates an abnormal condition.

The application of the present invention further comprises a user device suitable for providing a cause of a signal release indication in a UMTS network, comprising: a wireless subsystem comprising wireless communication adapted to communicate with a UMTS network; A wireless processor having a digital signal processor and adapted to interact with the wireless subsystem; Memory; A user interface; A processor adapted to execute the user application and to interact with the memory, the wireless communication and the user interface, and adapted to execute the application, wherein the user device monitors whether signaling disconnection indication instructions should be sent to the wireless network; ; Adding a cause for the signaling disconnection indication to the signaling disconnection indication; Means for transmitting a signaling disconnection indication added to the wireless network, wherein the wireless network is provided according to an indication of the cause of the signaling disconnection indication.

Next, reference is made to FIG. 1. 1 is a block diagram illustrating various modes and states for a radio resource control portion of a protocol stack in a UMTS network. In particular, the RRC may be either the RRC idle state 110 or the RRC connected state 120.

As will be apparent to one skilled in the art, a UMTS network includes two land based network segments. These are the core network (as shown in FIG. 8) and the universal terrestrial radio access network (UTRAN). While the UTRAN coordinates all radio related functions, the core network is responsible for switching and routing data calls and data connections to external networks.

In idle mode 110, the UE must request an RRC connection to establish radio resources whenever data needs to be exchanged between the UE and the network. This is either the result of an application on the UE that requires a connection to send data or the result of the UE monitoring the paging channel indicating whether the UTRAN or SGSN pages the UE to receive data from an external data network such as a push server. It can be either result. In addition, the UE also requests an RRC connection whenever it needs to send a mobility management signaling message such as location area update.

Once the UE sends a request to the UTRAN to establish a wireless connection, the UTRAN selects the state for the RRC connection therein. In particular, RRC connected mode 120 includes four distinct states. These are CELL_DCH state 122, CELL_FACH state 124, CELL_PCH state 126, and URA_PCH state 128.

The RRC connected state from the idle mode 110 may proceed to either the cell dedicated channel (CELL_DCH) state 122 or the cell forward access channel (CELL_FACH) state 124.

In CELL_DCH state 122, a dedicated channel is assigned to the UE to exchange data in both uplink and downlink. Since the channel assigned to the UE is a dedicated physical channel, this state usually requires the highest battery power from the UE.

Alternatively, the UTRAN may move from idle mode 110 to CELL FACH state 124. In the CELL FACH state, no dedicated channel is assigned to the UE. Instead, common channels are used to send signaling on small amounts of burst data. However, the UE still monitors the FACH continuously, thus consuming battery power.

Within RRC connected mode 120, the RRC state can be changed at the decision of the UTRAN. In particular, if data inactivity is detected for a certain time or a data throughput below a certain threshold is detected, the UTRAN changes the RRC state from CELL_DCH state 122 to CELL_FACH state 124, CELL_PCH state 126, or URA_PCH state 128. You can also move to. Similarly, if a payload is detected that exceeds a certain threshold, the RRC state may be moved from CELL FACH state 124 to CELL DCH state 122.

From the CELL FACH state 124, if data inactivity is detected for a predetermined time in some networks, the UTRAN may move the RRC state from the CELL FACH state 124 to a paging channel (PCH) state. This may be either the CELL_PCH state 126 or the URA_PCH state 128.

From CELL_PCH state 126 or URA_PCH state 128, the UE must move to CELL_FACH state 124 to initiate the update procedure to request a dedicated channel. This is the only state transition controlled by the UE.

CELL_PCH state 126 and URA_PCH state 128 monitor the broadcast messages and pages by the paging indication channel (PICH) using a discontinuous receive cycle (DRX). No uplink execution is possible.

The difference between CELL_PCH state 126 and URA_PCH state 128 is that if the current UTRAN registration area URA of the UE does not belong to the URA identification list present in the current cell, only the URA_PCH state triggers the URA update procedure. In particular, reference is made to FIG. 2. 2 illustrates an example of various UMTS cells 210, 212, and 214. All these cells require a cell update procedure if they are reselected in the CELL_PCH state. However, in the UTRAN registration area, each cell will be in the same UTRAN registration area 220, so for the URA_PCH mode, when moving between cells 210, 212 and 214, the URA update procedure is not triggered.

As shown in FIG. 2, the other cells 218 are external to the URA 220 and may or may not be part of a separate URA.

As will be appreciated by those skilled in the art, from a battery life perspective, the idle state provides the lowest battery usage compared to the above-mentioned states. In particular, since the UE is only required to monitor the paging channel only intermittently, the wireless communication does not need to be turned on continuously but instead will have to wake up periodically. The trade off for this is the delay in data transfer. However, if this delay is not very large, the benefits of being in idle mode and saving battery power outweigh the drawbacks of connection delays.

Again, reference is made to FIG. 1. Various UMTS infrastructure vendors move between states 122, 124, 126, and 128 based on various criteria. Exemplary infrastructure is summarized below.

In the first example infrastructure, the RRC moves directly between the idle mode and the CELL_DCH state. In the CELL_DCH state, if inactivity is detected for two seconds, the RRC state is changed to the CELL_FACH state 124. In CELL FACH state 124, if inactivity is detected for 10 seconds, the RRC state changes to CELL PCH state 126. In CELL PCH state 126, 45 minutes of inactivity will move the RRC state back to idle mode 110.

In a second example infrastructure, RRC switching may occur between idle mode 110 and connected mode 120 in accordance with the payload threshold. In the second infrastructure, if the payload is below a certain threshold, the UTRAN moves the RRC state to the CELL FACH state 124. Conversely, if the data exceeds a particular payload threshold, the UTRAN moves the RRC state to CELL_DCH state 122. In the second infrastructure, if 2 minutes of inactivity is detected in the CELL_DCH state 122, the UTRAN moves the RRC state to the CELL_FACH state 124. After 5 minutes of inactivity in CELL_FACH state 124, the UTRAN moves the RRC state to CELL_PCH state 126. In CELL PCH state 126, two hours of inactivity are required before returning to idle mode 100 again.

In the third exemplary infrastructure, the movement between idle mode 110 and connected mode 120 is always done in CELL_DCH state 122. After 5 seconds of inactivity in CELL_DCH state 122, the UTRAN moves the RRC state to CELL_FACH state 124. In CELL_FACH state 124, the device goes back to idle mode 100 with 30 seconds of inactivity.

In a fourth exemplary infrastructure, the RRC switches directly from idle mode to connected mode in the CELL_DCH state 122. In a fourth exemplary infrastructure, the CELL_DCH state 122 includes two substates. The first substate includes the high data rate and the second substate includes the low data rate, but is still in the CELL_DCH state. In a fourth exemplary infrastructure, the RRC transitions from the idle mode 110 directly to the fast data rate CELL_DCH substate. After 10 seconds of inactivity, the RRC state transitions to the low data rate CELL_DCH substate. With 17 seconds of inactivity from CELL_DCH state 122, the RRC state changes its state to idle mode 110.

The four example infrastructures described above illustrate how various UMTS infrastructure vendors implement states. As will be clear to those skilled in the art, in each case, if the time it takes to exchange the actual data (such as email) is significantly short compared to the time required to sustain the CELL_DCH state or CELL_FACH state, this is an unnecessary current release. draining the user experience in new generation networks such as UMTS, worse than the user experience in conventional generation networks such as GPRS.

In addition, the CELL_PCH state is more suitable than the CELL_FACH state from a battery life perspective, but the DRX cycle of the CELL_PCH state is typically set to a lower value than the idle mode 110. As a result, the UE requires a wake up more frequently in the CELL_PCH state than in the idle mode.

The URA PCH state with a DRX cycle similar to the idle mode DRX cycle is likely to make an optimal tradeoff between battery life and connection delay. However, URA_PCH is not currently supported in UTRAN. Therefore, it is desirable to switch to idle mode as soon as possible after the application has finished exchanging data from a battery life perspective.

Next, reference is made to FIG. 3. When switching from idle mode to connected mode, various signaling and data connections need to be made. Referring to FIG. 3, a first item that needs to be performed is RRC connection establishment. As mentioned above, this RRC connection setup can only be removed by the UTRAN.

Once the RRC connection establishment 310 is made, the signaling connection establishment 312 begins.

Once signaling setup 312 is complete, encryption and integrity setup 314 begins. After encryption and integrity setup 314 is complete, radio bearer setup 316 is made. At this point, data may be exchanged between the UE and the UTRAN.

In general, disconnecting is done similarly in reverse order. RRC connection setup 310 is released after radio bearer setup 316 is released. At this point, the RRC moves to idle mode 110 as shown in FIG.

The current 3GPP specification does not allow a UE to release an RRC connection or indicate a UE's preference for RRC state, and the UE is still a designated core network domain such as a packet switched (PS) domain used by packet-switched applications. It may indicate only the termination of the signaling connection for. According to section 8.1.14.1 of 3GPP TS 25.331, a signaling connection release indication procedure is used by the UE to instruct the UTRAN to release one of its signaling connections. This procedure may in turn initiate the RRC disconnection procedure.

Thus, without departing from the current 3GPP specification, the signaling connection release may be initiated once the signaling connection establishment 312 is released. Since releasing signaling connection establishment 312 depends on the capability of the UE, this may initiate RRC disconnection in order according to the specification.

As will be apparent to those skilled in the art, if signaling connection establishment 312 is released, the UTRAN also needs to release encryption and integrity establishment 314 and radio bearer establishment 316 after signaling connection establishment 312 is released. There will be.

Once signaling connection establishment 312 is released, RRC connection establishment is typically released by the network for the current vendor's infrastructure.

Using the above, when the UE determines that the data exchange is complete, for example, if an indication that the exchange of data is complete is provided to the "RRC connection manager" element of the UE software, the RRC connection manager establishes a signal connection establishment 312. It may be determined whether or not this has been released. For example, an email application on the device sends an indication that the email actually received a positive response from the push email server that is received by the push server. The RRC manager keeps track of all existing applications, associated PDP contexts, associated PS radio bearers and associated circuit switched (CS) radio switched bearers. In this case, a delay can be introduced to ensure that after the application has correctly terminated the data exchange and sent the "complete" indication, it no longer requires an RRC connection. This delay is the same as the inactivity timeout associated with the application. Each application can have its own inactivity timeout. For example, an email application may have a 5 second inactivity timeout, while an active browser application may have a 60 second timeout. Based on the composite state of such indications from active applications, the UE software can determine how long to wait before being able to initiate signaling disconnection of the appropriate core network (eg, PS domain).

Inactivity timeouts may be made dynamically based on traffic pattern history and / or application profiles.

Whenever an RRC connection manager uses a probability to determine that no application is expecting a data exchange, it can send a signaling connection release indication procedure to the appropriate domain.

 The UE-initiated transition to idle mode described above may occur from any state of the RRC connected mode 120 as shown in FIG. 1, and may be in idle mode with a network that releases the RRC connection as shown in FIG. 1. Go to 110) to finish. This is also applicable to the case where the UE performs any packet data service during a voice call. In this case, as well as releasing the PS domain, the CS domain maintains the connection.

A problem from the network perspective described above is that the signaling release indication sent by the UE is considered an alarm. If the signaling network release is not expecting any subsequent data as a result of explicit action by the UE due to expiration of the application timer, the alarm due to the indication distorts the performance and alarm indication. This may change key performance indicators, leading to lower efficiency.

Preferably, a cause may be added to the signaling connection release indication to indicate to the UTRAN the reason for the indication. In a preferred embodiment, the cause may be an indication that the indication is in an abnormal state or that the indication is initiated by the UE as a result of the required idle transition. Another normal (ie not abnormal) transition may also be the result of the transmission of the signaling disconnection indication.

In a more preferred embodiment, various timeouts may indicate that the signaling connection indication should be sent in an abnormal state. The example timers below are not perfect, other timers or abnormal conditions are possible. For example, 10.2.47 3GPP TS 24.008 defines the timer T3310 as follows.

[table]

Timer number Timer value condition Cause of start Normal stop 1st, 2nd, 3rd, and 4th expiration note 3 T3310 15 seconds GMM- REG- INIT ATTACH REQ Sent ATTACH ACCEPT received ATTACH REJECT received ATTACH REQ retransmission

Timer T3310

This timer is used to indicate a connection failure. Failure to connect may be the result of a network, or may be a radio frequency (RF) problem such as a collision or poor RF.

Connection attempts can occur at multiple times, and connection failures occur as a result of either a predetermined number of failures or an explicit rejection.

The second timer of 10.2.47 of 3GPP is T3330, which is defined as follows.

 [table]

Timer number Timer value condition Cause of start Normal stop 1st, 2nd, 3rd, and 4th expiration note 3 T3310 15 seconds GMM- ROUTING- UPDATING- INITIATED ROUTING AREA UPDATE REQUEST Sent ROUTING AREA UPDATE ACC received ROUTING AREA UPDATE REJ received Resending a ROUTING AREA UPDATE REQUEST Message

Timer T3330

This timer is used to indicate a routing area update failure. Upon expiration of the timer, subsequent routing area updates may be made at the required multiple times, with routing area update failures occurring as a result of either a predetermined number of failures or an explicit rejection.

The third timer of 10.2.47 of 3GPP is T3340, which is defined as follows.

[table]

Timer number Timer value condition Cause of start Normal stop 1st, 2nd, 3rd, and 4th expiration note 3 T3340 (Iu mode only) 10 sec GMM- REG-INIT GMM-DEREG-INIT GMM-RA- UPDATING-INT GMM-SERV- REQ-INIT (Iu mode only) GMM- ATTEMPTING- TO-UPDATE- MM GMM-REG- NORMAL- SERVICE ATTACH REJ, DETACH REQ, ROUTING AREA UPDATE REJ or any of Cause # 11, # 12, # 13, or # 15. ATTACH ACCEPT or ROUTING AREA UPDATE ACCEPT received with "no follow-up" indication. PS signaling disconnected PS signaling disconnection and processing as described in subclause 4.7.1.9

Timer T3340

This timer is used to indicate failure of a GMM service request. Upon expiration of the timer, subsequent GMM service requests may be made at the required multiple times, where a GMM service request failure occurs as a result of either a predetermined number of failures or an explicit rejection.

In this manner, instead of the signaling release indication condition limited to the abnormal state and the release by the UE, the cause of the signaling release indication may further include information about a timer that fails in the abnormal state. The signaling connection release indication may be structured as follows.

[table]

Information element / Group name Necessity Multiplexing IE  Form and Reference Meaning Description Message form MP Message form UE  Information element Integrity check information CH Integrity Check Information 10.3.3.16 CN  Information element CN domain identification MP CN domain identification 10.3.1.1 Signaling Instruction Cause OP Signaling Instruction Cause t3310 Timeout t3330 Timeout t3340 Timeout UE Request Idle Switch

Instruction for disconnecting signaling

This message is used by the UE to instruct the UTRAN to release an existing signaling connection. The addition of the signaling release indication cause enables the UTRAN or other network element to receive the cause of the signaling release indication, whether the signaling release indication is due to an abnormal state, and what the abnormal state is. Thus, the RRC disconnection procedure is allowed to be initialized in turn.

In one embodiment, upon receiving a request for releasing or stopping a signaling connection from a higher layer of a particular CN (core network) domain, a variable (eg, for a particular CN domain) identified as an IE (information element) "CN domain identification" (eg If there is a signaling connection as identified by the variable ESTABLISHED_SIGNALING_CONNECTIONS), the UE initiates the signaling connection release indication procedure. If the variable does not identify any existing signaling connection, any progress establishment of the signaling connection for the particular CN domain is stopped in another way. And, upon initialization of the signaling connection release indication procedure in the CELL_PCH state or the URA_PCH state, the UE performs a cell update procedure using the cause "send update data". If the cell update procedure is successfully completed, the UE continues the signaling connection release indication procedure as follows.

That is, the UE sets the IE "CN domain identification" to the value indicated by the higher logical layer. The value of the IE indicates the CN domain, and the signaling connection associated with the CN domain is the signaling related to the associated signaling connection indicating that the upper layer is to be released. If the CN domain identification is set in the PS domain, and the upper layer indicates the cause and initiates this request, the IE "signal release indication cause" is set appropriately. In addition, the UE moves the signaling connection using the identity indicated by the higher layer from the variable "ESTABLISHED_SIGNALING_CONNECTION". Then, the UE transmits a signaling connection release indication message on the DCCH, for example, using AM RLC. If the RLC confirms successful delivery of the release indication message, the procedure ends.

IE "causes signaling release indication" is also used in accordance with an embodiment of the present invention. For example, the cause of the release is sorted using existing message definitions. The upper layer release cause message is structured as follows.

[table]

Information element / Group name Necessity Multiplexing IE  Form and Reference Meaning Description Signaling Instruction Cause MP Listed (UE Requested PS Data Session End, T3310 Expired, T3330 Expired, T3340 Expired)

In this example, the T3310, T3330, and T3340 expirations correspond to expiration of previously identified and correspondingly numbered timers. In one embodiment, the cause value can be set as "UE requested PS data session termination" instead of "UE requested idle switch" so that the UTRAN determines the state transition, but the expected result is identified by the cause value. Corresponds to It is desirable to extend the signaling disconnection indication, but reference extension is not necessary.

Next, reference is made to FIG. 9. 9 is a flow diagram of an example UE for monitoring whether to send a signaling connection release indication for various domains (eg, PS or CS). Processing begins at step 910.

The UE switches to step 912 where the UE checks to see if an abnormal condition exists. Such an abnormal state may include, for example, a timer T3310, a timer T3320, or a timer T3340 that expires as described above. If these timers expire a certain predetermined number of times, or if an explicit rejection is received based on the expiration of any of these timers, the UE proceeds to step 914 of sending a signaling connection release indication. The signaling connection release indication message is added to the signaling release indication cause field. The signaling release indication cause field includes at least that the signaling release indication is based on an abnormal condition or state, and the preferred embodiment includes a specific timer that is timed out and becomes an abnormal state.

Conversely, if the UE finds that there is no abnormal condition at step 912, the UE proceeds to step 920 to check whether additional data is expected at the UE. As mentioned above, this may include the case where an email is sent and confirmation of the sending of the email is received back at the UE. Those skilled in the art will also know other examples of determining that the UE is not expecting any additional data.

In step 920, if the UE determines that data delivery has ended (or determines that the call has ended in the case of a circuit switched domain), the UE adds a signaling release indication cause field and includes signaling that the UE requires an idle switch. Proceed to step 922 to send a disconnect indication.

In step 920, if the data does not end, the UE loops back and continues checking whether an abnormal condition exists in step 912 and whether the data ends in step 920.

Once the signaling disconnection indication is sent to step 914 or 922, processing proceeds to step 930 and ends.

The UE comprises a functional element that may be implemented, for example, by applications or algorithms performed through the operation of the UE microprocessor, or by a hardware implementation forming an inspector signaling disconnection indication transmitter. The checker is configured to check whether the signaling disconnection indication has been sent. And, the signaling connection release indication transmitter is configured to send the signaling connection release indication in response to the indication by the checker whether the signaling connection release indication has been sent. The signaling connection release indication includes a signaling release indication cause field.

In one implementation, instead of the network implicitly knowing the timeout of the timer, the UE does not need to send a cause value indicating the timeout of the timer. In other words, the timer starts synchronizing with the network. A reason code is defined, and the reason code is provided to the UE by the network. This cause code is used by the UE to initialize the timer. The network implicitly recognizes the reason for the subsequent timeout of the timer, because the reason code sent initially by the network causes the timer to time out. So, as a result, the UE does not need to send a cause value indicating the timeout of the timer.

Referring to FIG. 10, the network element receives the signaling disconnection indication instruction in step 1010, the network element examines the signaling release indication cause field in step 1014, and requests whether the cause is an abnormal cause or an idle transition in step 1016. Whether or not by the UE. If the signaling disconnection indication in step 1016 is due to an abnormal cause, the network node proceeds to step 1020 where the alarm is being used for the purpose of monitoring performance and monitoring the alarm. Key performance indicators can be updated as appropriate.

Conversely, in step 1016, if the cause of the signaling disconnection indication is not the result of an abnormal condition or, in other words, the result of the UE requesting the idle switch, the network node does not generate any alarm and the indication is from the performance statistics. Proceed to step 1030, which may be filtered to prevent distortion of performance statistics. In step 1020 or step 1030, the network node proceeds to step 1040 where processing ends.

Initialized by the network element of the RRC connection release procedure as a result of receiving and checking the signaling release indication cause field. The packet switched data connection is then terminated.

As will be apparent to one skilled in the art, step 1020 may further be used to distinguish between various alarm conditions. For example, the T3310 timeout may be used to maintain a first set of statistics, and the T3330 timeout may be used to maintain a second set of statistics. Step 1020 can distinguish between causes of abnormal conditions, allowing the network operator to track more efficient performance.

The network includes functional elements that may be implemented, for example, by applications or algorithms performed through the operation of the processor, or by hardware implementations forming the checker and alarm generator. The checker is configured to check the signaling indication release cause field of the signaling connection release indication. The checker checks whether the signaling release indication cause field indicates an abnormal state. The alarm generator is optionally configured to generate an alarm if the inspection by the inspector determines that the signal release indication cause field indicates an abnormal condition.

In one implementation, upon receiving a signaling connection release indication, the UTRAN is received from a higher layer and conveys a cause for requesting the release of the signaling connection. The higher layer may then initiate the release of the signaling connection. The cause of the IE signaling release indication triggers the RRC of the UE to transmit a message including the higher layer cause of the UE. The cause may be the result of an abnormal higher layer procedure. The difference in message cause is ensured by successful reception of IE.

Possible scenarios include scenarios in which the resetting of the transmitting side of the RLC input on the signaling radio bearer RB2 occurs before confirmation by the RLC of the successful delivery of the signaling connection release indication message. In this case, the UE retransmits the signaling connection release indication message on the uplink DCCH using AM RLC on signaling radio bearer RB2, for example. If an input-RAT handover from the capability of the UTRAN procedure occurs before successful delivery of confirmation of successful delivery of the signaling disconnection indication message by the RLC, the UE stops signaling connection during the new RAT.

Referring back to FIG. 1, in some cases, it is more desirable to be in URA_PCH connected mode rather than idle mode. For example, the delay for the connection in the CELL_DCH or CELL_FACH connected mode state is required to be short and is preferably in the connected mode PCH state. There are two ways to accomplish this. One way is by changing the 3GPP specification so that the UTRAN can request the UE to move to a specific state, in this case URA_PCH state 128.

Another way may be that the RRC connection manager consider other factors such as what state the RRC connection is accurate in. For example, if the RRC connection is in the URA_PCH state, moving to idle mode 110 is determined to be unnecessary and no signaling disconnection procedure is initiated.

Reference is made to FIGS. 4A and 4B. 4A shows a current UMTS implementation in accordance with the infrastructure "4" of the foregoing example. As shown in Figures 4A and 4B, the horizontal axis is time.

The UE starts in RRC idle state 110 and begins to establish an RRC connection based on local data that needs to be transmitted or a page received from the UTRAN.

As shown in FIG. 4A, an RRC connection setup 310 first occurs, during which time the RRC state is a connected state 410.

Next, signaling connection establishment 312, encryption and integrity establishment 314, and radio bearer establishment 316 occur. The RRC state is CELL_DCH state 122 during this time. As shown in FIG. 4A, in this example, the time to move from the RRC idle mode to the time when the radio bearer is established is approximately 2 seconds.

Next, data is exchanged. In the example of FIG. 4A, data exchange is accomplished in approximately 2 to 4 seconds, shown in step 420.

After the data has been exchanged at step 420, the radio bearer is reconfigured by the network to move to the low data rate DCH state after approximately 10 seconds since no data is exchanged except for the intermittent RLC signaling PDUs required. This is shown in steps 422 and 424.

In the low data rate DCH state, nothing is received for 17 seconds, at which point the RRC connection is released by the network at step 428.

Once the RRC connection is initiated at step 428, the RRC state proceeds to disconnected state 430 for approximately 40 milliseconds, after which the UE is in RRC idle state 110.

In addition, as shown in FIG. 4A, UE current consumption during the period in which the RRC is in the CEL_DCH state 122 is shown. As shown, the current consumption is approximately 200 milliamps to 300 milliamps for the entire duration of the CELL_DCH state. During the disconnection and idle periods, approximately 3 milliamps are utilized, assuming a DRX cycle of 1.28 seconds. However, in 35 seconds, 200 to 300 milliamps of current are discharged from the battery.

Next, reference is made to FIG. 4B. 4B utilizes the same example infrastructure “4” as described above, and implements only signaling disconnection.

As shown in FIG. 4B, the same setup steps 310, 312, 314 and 316 occur and these setup steps take the same time when moving between the RRC idle state 110 and the RRC CELL_DCH state 122. Take it.

In addition, the RRC data PDU exchange for the example email of FIG. 4A is also done in FIG. 4B, which takes approximately 2 to 4 seconds.

In the example of FIG. 4B the UE has an application specific inactivity timeout, which is 2 seconds in the example of FIG. 4B, and is indicated by step 440. After the RRC connection manager determines that there is inactivity for a certain time, in step 422 the UE releases the signaling connection establishment and in step 428 the RRC connection is released by the network.

As shown in FIG. 4B, the current consumption during the CELL DCH step 122 is still approximately 200 milliamps to 300 milliamps. However, the connection time is only about 8 seconds. As will be clear to those skilled in the art, the fairly short time that the mobile terminal stays in the cell DCH state 122 can always save significant battery on the UE device.

Next, reference is made to FIGS. 5A and 5B. 5A and 5B show a second example using the aforementioned infrastructure, such as infrastructure “3”. As with Figures 4A and 4B, a connection setup takes place, which takes approximately 2 seconds. This requires RRC connection establishment 310, signaling connection establishment 312, encryption and integrity establishment 314, and radio bearer establishment 316.

During this setup, the UE moves from RRC idle mode 110 to CELL_DCH state 122 using an intermittent RRC state connection step 410.

As in FIG. 4A, an RLC data PDU exchange occurs in FIG. 5A, taking 2-4 seconds in the example of FIG. 5A.

According to infrastructure 3, since no data is exchanged except for the intermittent RLC signaling PDUs required, the RLC signaling PDU exchange does not receive any data and is idle for a period of 5 seconds at step 422, at which point the radio bearer Reconfigures the network to move from CELL_DCH state 122 to CELL_FACH state 124. This is completed by step 450.

In CELL_FACH state 124, the RLC signaling PDU exchange finds that there is no data exchange except for the intermittent RLC signaling PDU that is required for a predetermined time, in this case 30 seconds, at which point by the network RRC disconnection is performed at step 428.

As shown in FIG. 5A, this moves the RRC state to idle mode 110.

As further shown in FIG. 5A, current consumption during DCH mode is between 200 and 300 milliamps. When moving to CELL FACH state 124, the current consumption is lowered to approximately 120-180 milliamps. After the RRC connection is released and the RRC moves to idle mode 110, the power consumption is approximately 3 milliamps.

The UTRA RRC connected mode state, which is either CELL_DCH state 122 or CELL_FACH state 124, persists for approximately 40 seconds in the example of FIG. 5A.

Next, reference is made to FIG. 5B. FIG. 5B shows the same infrastructure “3” as FIG. 5A and uses the same connection time of approximately 2 seconds to establish RRC connection 310, signaling connection establishment 312, encryption and integrity establishment 314, and radio bearer establishment. 316 is performed. In addition, the RLC data PDU exchange 420 takes approximately 2-4 seconds.

As in FIG. 4B, the UE application detects a specific inactivity timeout at step 440, and the signaling connection release indication procedure is initiated by the UE, so that the RRC connection is released by the network at step 448.

As further shown in FIG. 5B, the RRC starts in idle mode 110 and moves to CELL_DCH state 122 without passing through the CELL_FACH state.

As further shown in FIG. 5B, the current consumption is about 200 to 300 milliamps at the time the RRC state is in CELL_DCH state 122, which is about 8 seconds according to the example of FIG. 5B.

Therefore, the comparison between FIGS. 4A and 4B and FIGS. 5A and 5B eliminates a significant amount of current consumption, greatly extending the battery life of the UE. As will be apparent to one skilled in the art, the foregoing may be further utilized in the context of the current 3GPP specification.

Next, reference is made to FIG. 6. The UMTS includes a CS control plane 610, a PS control plane 611, and a PS user plane 630.

Within these three planes, there is a non-access stratum (NAS) portion 614 and an access stratum portion 616.

NAS portion 614 in CS control plane 610 includes call control (CC) 618, supplementary services (SS) 620, and short message service (SMS) 622.

The NAS portion 614 in the PS control plane 611 includes mobility management (MM) and GPRS mobility management (GMM) 626. It further includes SM / RABM 624 and GSMS 628.

CC 618 provides call management signaling for circuit switched services. The session management portion of SM / RABM 624 provides for PDP context activation, deactivation, and change. SM / RABM 624 provides the quality of service negotiation.

The main function of the RABM portion of the SM / RABM 624 is to connect the PDP context to the radio access bearer. Thus, SM / RABM 624 is responsible for the setup, modification and release of radio bearers.

In the access layer portion 616, the CS control plane 610 and the PS control plane 611 are over radio resource control (RRC).

The NAS portion 614 in the PS user plane 630 includes an application layer 368, a TCP / U layer 636, and a PDP layer 364. PDP layer 364 may include, for example, Internet Protocol (IP).

The access layer portion 616 in the PS user plane 630 includes a packet data convergence protocol (PDCP) 632. PDCP 632 is designed to create a WCDMA protocol suitable for carrying the TCP / IP protocol between the UE and the RNC (as shown in FIG. 8) and optionally for compression and decompression of the IP traffic stream protocol header. will be.

UMTS radio link control (RLC) 640 and media access control (MAC) layer 650 form the data link sublayer of the UMTS radio interface and reside on the RNC node and the user equipment.

The layer 1 (L1) UMTS layer (physical layer 660) is below the RLL / MAC layers 640 and 650. This layer is the physical layer for communication.

Although the foregoing may be implemented on a variety of mobile devices, examples of child devices are summarized in FIG. 7. Next, reference is made to FIG. 7.

Preferably, the UE 1100 is a bidirectional communication device having at least voice communication capability and data communication capability. Preferably, UE 1100 has the ability to communicate with other computer systems on the Internet. Depending on the exact functionality provided, the wireless device may be referred to as a data messaging device, a two-way pager, a wireless email device, a cell phone with data messaging capability, a wireless internet application, a data communication device, or the like.

If the UE 1100 is capable of bi-directional communication, this includes both the receiver 1112 and the transmitter 1114, as well as preferably embedded or internal antenna elements 1116 and 1118, local oscillators (LOs) ( 1113, and a communication subsystem 1111 including one or more related components, such as a processing module, such as a digital signal processor (DSP) 1120. As will be apparent to one skilled in the art, the particular design of the communication subsystem 1111 depends on the communication network in which the mobile device is intended to operate. For example, the UE 1100 may include a communication subsystem 1111 designed to operate within a GPRS network or a UMTS network.

Network access requirements will also vary depending on the type of network 1119. For example, in UMTS and GPRS networks, network access is related to subscribers or users of UE 1100. Therefore, a GPRS mobile device requires a subscriber identity module (SIM), for example, to operate on a GPRS network. UMTS requires a USIM or SIM module. CDMA requires a RUIM card or module. In the present invention they will be called UIM interfaces. Without a valid UIM interface, the mobile device may not work sufficiently. Legally required functions such as local or non-network communication functions as well as emergency calls may be available, but mobile device 1100 may not perform any other functions, including communication over network 1119. In general, UIM interface 1144 is similar to a card slot into which a card can be inserted and extracted, such as a diskette or PCMCIA card. The UIM card has approximately 64K of memory and can hold many key configurations 1151 and other information 1153 and subscriber related information such as identification.

After the required network registration or activation procedure is completed, the mobile device 1100 may transmit and receive communication signals through the network 1119. Signals received by the antenna 1116 via the communication network 1119 are input to the receiver 1112, which in the example system shown in FIG. 7 is capable of signal amplification, frequency downconversion, filtering, and channel. It may also perform common receiver functions such as selection, and analog-to-digital (A / D) conversion. A / D conversion of the received signal enables more complex communication functions such as demodulation and decoding performed in the DSP 1120. In a similar manner, transmitted signals are processed by the DSP 1120 (including, for example, modulation and encoding), and such DSP processed signals are digital-to-analog (D / A) conversion, frequency up-conversion, filtering Input to transmitter 1114 for amplification and transmission via communication network 200 via antenna 1118. The DSP 1120 not only processes communication signals but also provides control signals for transceiver control. For example, the gain applied to the communication signals at the receiver 1112 and transmitter 1114 may be adaptively controlled through an automatic gain control algorithm implemented in the DSP 1120.

The network 1119, including the server 1160 and other elements (not shown), may further communicate with multiple systems. For example, the network 1119 may communicate with both enterprise systems and web client systems to accommodate various clients using various service levels.

Preferably, UE 1100 includes a microprocessor 1138 that controls the overall operation of the mobile device. Communication functions, including at least data communication, are performed through the communication subsystem 1111. The microprocessor 1138 also includes a display 1122, flash memory 1124, random access memory (RAM) 1126, auxiliary input / output (I / O) subsystem 1128, serial port 1130, keyboard ( It may also interact with additional device subsystems, such as 1132, speaker 1134, microphone 1136, near field communication subsystem 1140, and any other device subsystems generally indicated as 1142.

Some of the subsystems shown in FIG. 7 perform communication-related functions, while other subsystems may provide a “resident” or on-device function. Among them, some subsystems, such as keyboard 1132 and display 1122, for example, communicate with communication-related functions, such as entering text messages, and device-resident, such as calculators or task lists, for transmission over a communication network. It may be used for both functions.

 Operating system (OS) software used by microprocessor 1138 is preferably stored in permanent storage, such as flash memory 1124, and instead of flash memory 1124 read-only memory (ROM) or similar storage elements. (Not shown). Those skilled in the art will appreciate that operating systems, specific device applications, or portions thereof may be temporarily loaded into volatile memory, such as RAM 1126. In addition, the received communication signals may be stored in the RAM 1126. In addition, the unique identifier is also preferably stored in the ROM.

As shown, flash memory 1124 may be divided into different areas, for example, different areas including both computer program 1158 and program data storage 1150, 1152, 1154 and 1156. . These different storage forms indicate that each program may be assigned to a portion of flash memory 1124 for their own data storage requirements. Microprocessor 1138 preferably enables execution of software applications on mobile devices in addition to its operating system functions. A predetermined set of applications (eg, including at least data communication and voice communication applications) that control basic device operation will generally be installed on the UE 1100 while the UE 1100 is being manufactured. A preferred software application may be a personal information management (PIM) application, which has the ability to organize and manage data items about a user of a mobile device such as email, calendar events, voice mail, appointment schedules, and work items. Have, but are not limited to, these. In practice, one or more memory storage devices will be available on the mobile device to facilitate storage of PIM data items. Such a PIM application has the ability to send and receive data items via wireless network 1119. In a preferred embodiment, the PIM data items are seamlessly integrated, synchronized, and updated over the wireless network 1119 with the corresponding data items of the mobile device user stored in or associated with the host computer system. In addition, additional applications may also be transferred to the mobile device through the network 1119, auxiliary I / O subsystem 1128, serial port 1130, local area communication subsystem 1140, or any other suitable subsystem 1142. It may be loaded on 1100 and installed in RAM 1126 or preferably non-volatile memory (not shown) by the user for execution by microprocessor 1138. Such flexibility in application installation may increase the functionality of the device and provide improved on-device functionality, communication-related functionality, or both. For example, applications for secure communication may enable other functions such as electronic commerce functionality and financial transactions performed using the UE 1100. However, such applications as described above will in many cases need to be approved by the carrier.

In the data communication mode, a received signal, such as a text message or web page download, will be processed by the communication subsystem 1111 and entered into the microprocessor 1138, which is preferably a display 1122, Or alternatively further process the received signals to output to the auxiliary I / O device 1128. The user of the UE 1100 may configure data items, such as an email message, using the keyboard 1132, for example with the display 1122 and a possible secondary I / O subsystem 1128, and the keyboard 1132 Is preferably a full alphanumeric keyboard or a telephone-type keypad. The item configured as such may be transmitted through the communication network via the communication subsystem 1111.

For voice communication, the overall operation of the UE 1100 is similar except that the received signals are preferably output to the speaker 1134 and the signals for transmission are generated by the microphone 1136. In addition, alternative voice or audio I / O subsystems, such as a voice message recording subsystem, may be implemented on the UE 1100. Originally, the voice or audio signal output is preferably via the speaker 1134, but the display 1122 also provides for the identification of the duration of the calling party, voice call, or other voice call related information. It may also be used to provide instructions.

In general, the serial port 1130 of FIG. 7 is implemented in a mobile device in the form of a personal digital assistant (PDA), which is preferably synchronized with a user's desktop computer (not shown). This serial port 1130 allows subscribers to set preferences via external devices or software applications, and provide information or download software to the UE 1100 in addition to via a wireless communications network. Thereby expanding the capabilities of the mobile device 1100. Other download paths may be used, for example, to enable secure device communication by loading an encryption key on a mobile device via a direct, trusted and trusted connection.

Alternatively, serial port 1130 may be used for other communications and may be included in a universal serial bus (USB) port. The interface is related to the serial port 1130.

Another communication subsystem 1140, such as a near field communication subsystem, is an additional optional component that may provide communication between the UE 1100 and other systems or devices, where the other systems or devices are similar devices. no need. For example, subsystem 140 may include an infrared device and associated circuits and components or a Bluetooth ^™ communication module to provide for communication with similarly possible systems and devices.

Next, reference is made to FIG. 8. 8 is a block diagram of a communication system 800 that includes a UE 802 communicating over a wireless network.

The UE 802 communicates wirelessly with one of the multiple Node Bs 806. Each Node B 806 is responsible for air interface processing and some radio resource management functions. Node B 806 provides functionality similar to a base transceiver station in a GSM / GPRS network.

The radio link shown in the communication system 800 of FIG. 8 represents one or more different channels, typically different radio frequency (RF) channels, and related protocols used between the wireless network and the UE 802. The Uu air interface is used between the UE 802 and the Node B 806.

The RF channel is typically a limited resource that must be saved due to the limitation of the overall bandwidth and the limited battery power of the UE 802. Those skilled in the art may, in practical implementations, include a few hundred cells depending on the overall area required of the network coverage. All related components may be connected by multiple switches and routers (not shown) controlled by multiple network controllers.

Each Node B 806 is in communication with a Radio Network Control (RNC) 810. The RNC 810 is responsible for the control of radio resources in that area. One RNC 810 controls a number of Node Bs 806.

The RNC 810 of the UMTS network provides the same functionality as the base station controller (BSC) of the GSM / GPRS network. However, the RNC 810 includes better intelligence, such as voluntary handover management, without MSC and SGSN, for example.

The interface used between Node B 806 and RNC 810 is Iub interface 808. The NBAP (Node B Application Part) signaling protocol is preferentially used as defined in 3GPP TS 25.433 V3.11.0 (2002-09) and 3GPP TS 25.433 V5.7.0 (2004-01).

Universal Terrestrial Radio Access Network (UTRAN) 820 includes an RNC 810, a Node B 806 and a Uu air interface 804.

Circuit switched traffic is routed to the mobile switching center (MSC) 830. MSC 830 is a computer that recognizes calls and takes and receives data from subscribers or from a PSTN (not shown).

Traffic between RNC 810 and MSC 830 utilizes Iu-CS interface 828. The Iu-CS interface 828 is a circuit switched connection to carry voice traffic (typical) and signaling between the UTRAN 820 and the core voice network. The main signaling protocol used is RANAP (Radio Access Network Application Part). The RANAP protocol is used for UMTS signaling between the core network 821 and the UTRAN 820, which may be MSC 830 or SSGN 850 (defined in more detail below). The RANAP protocol is defined in 3GPP TS 25.413 V3.11.1 (2002-09) and 3GPP TS 25.413 V5.7.0 (2004-01).

Permanent data (such as the UE 102's current location) as well as permanent data (such as the UE 102's user profile) for all UEs 802 registered with the network operator are stored in the Home Location Register (HLR) ( 838). For voice calls to the UE 802, the HLR 838 may be queried to determine the current location of the UE 802. The visitor location register (VLR) 836 of the MSC 830 is responsible for the group of location areas, thus storing the data of the mobile stations currently in their area of responsibility. The data of the mobile stations includes a portion of the permanent data of the mobile station transmitted from the HLR 838 to the VLR 836 for high speed access. However, the VLR 836 of the MSC 830 may allocate and store local data, such as temporary identification. In addition, the UE 802 is authenticated on system access by the HLR 838.

Packet data is routed through a packet switched support node (SGSN) 850. SGSN 850 is the gateway of the RNC and the core network in the GPRS / UMTS network and is responsible for the delivery of data packets from and to the UE within the geographic service area of the SGSN. The Iu-PS interface 848 is used between the RNC 810 and the SGSN 850 and is a packet switched connection for carrying data traffic (typical) and signaling between the UTRAN 820 and the core data network. The main signaling protocol used is RANAP (described above).

SGSN 850 communicates with a Packet Gateway Support Node (GGSN) 860. GGSN 860 is an interface between a UMTS / GPRS network and another network, such as the Internet or a private network. GGSN 860 is connected to a Public Switched Network (PDN) 870 via a Gi interface.

Those skilled in the art will appreciate that the network may be connected to other systems capable of including other networks not explicitly shown in FIG. 8. In general, the network will transmit at least a portion of the paging and system information types on an ongoing basis even if there is no packet data actually exchanged. Although the network contains many parts, all of these parts work together to perform specific actions on the wireless link.

Embodiments described herein are examples of structures, systems or methods having elements corresponding to elements of the techniques of the application of the invention. The written description thus enables a person skilled in the art to make and use embodiments with other elements as well as to correspond to the elements of the techniques of the application of the invention. Thus, the intended scope of the techniques of the application of the present invention includes other structures, systems or methods that are not different from the techniques of the applications as described herein, and the techniques of the application as described herein. Further includes substantially different other structures, systems or methods.

As described above, according to the present invention, when switching from an RRC connected mode to a more efficient battery state or mode, and if the cause of the signaling release indication is a UE idle switching request, the network can guarantee not to consider the signaling release indication as an alarm. have. In addition, the UE may switch based on one of the UE initial termination of the signaling connection in the designated core network domain or an indication of the UTRAN in which a switch from one connection state to another connection state occurs.

Claims (25)

 A method of processing a cause for signaling release indication between a user device and a wireless network, the method comprising: a. Monitoring, at the user device, whether a signaling disconnection indication should be sent to the wireless network; b. At the user device, adding a cause for the signaling disconnection indication to the signaling disconnection indication; c. Sending the added signaling connection release indication to the wireless network; d. Receiving the signaling disconnection indication in the wireless network; e. Filtering the signaling release indication cause to determine whether to generate an alarm. The method of claim 1, wherein the cause is an abnormal state. 3. The method of claim 2, wherein the abnormal state is expiration of a timer. 4. The method of claim 3 wherein the timer is selected from the group comprising an attachment failure timer, a routing area update timer, and a GMM service request timer. 2. The method of claim 1 wherein the cause is a request by the user equipment to terminate a PS data session to switch to idle mode. The method of claim 1, wherein the filtering step generates an alarm when the cause is in an abnormal state. 2. The method of claim 1, wherein the filtering step ignores the signaling connection release indication when the cause is an idle switch request by the user device. A system configured to handle a cause of signaling release indication, a. A wireless subsystem comprising wireless communication configured to communicate with a network; A wireless processor having a digital signal processor and configured to interact with the wireless subsystem; Memory; A user interface; A user device comprising a processor configured to execute user applications and to interact with the memory, the wireless communication and the user interface, the processor configured to execute applications; b. A wireless network configured to communicate with the user device Including; The user device is Iii. Means for monitoring whether a signaling disconnection indication should be sent to the wireless network; Ii. Means for adding a cause for the signaling disconnection indication to the signaling disconnection indication; Iii. Means for sending the added signaling connection release indication to the wireless network Characterized in having The wireless network Iii. Means for receiving the signaling disconnection indication; Ii. Means for filtering the cause of the signaling release indication to determine whether to generate an alarm And a signaling release processing cause cause. The system of claim 8, wherein the cause is an abnormal state. 10. The system of claim 9, wherein the abnormal state is expiration of a timer. 11. The system of claim 10 wherein the timer is selected from the group comprising a connection failure timer, a routing area update timer, and a GMM service request timer. 12. The system of claim 11 wherein the cause is a request by the user device to terminate a PS data session to switch to idle mode. 9. The system of claim 8 wherein the means for filtering is configured to generate an alarm if the cause is an abnormal condition. 9. The system of claim 8 wherein the means for filtering is configured to ignore the signaling connection release indication when the cause is an idle switch request by the user device. A method of handling signaling release indication cause at a user device for improved alarm tracking in a wireless network, the method comprising: a. Monitoring whether a signaling disconnection indication should be sent to the wireless network; b. Adding a cause for the signaling disconnection indication to the signaling disconnection indication; c. Requesting the signaling disconnection release identifying the cause of the signaling connection release indication by transmitting the added signaling connection release indication with the cause added. The method of claim 15, wherein the cause is an abnormal state. 17. The method of claim 16, wherein the abnormal state is expiration of a timer. 18. The method of claim 17, wherein the timer is selected from the group comprising a connection failure timer, a routing area update timer, and a GMM service request timer. 16. The method of claim 15, wherein the cause is a request by the user equipment to terminate a PS data session to switch to idle mode. A user device configured to provide a signaling release indication cause to a network, the user device comprising: a wireless subsystem comprising wireless communication configured to communicate with the network; A wireless processor having a digital signal processor and configured to interact with the wireless subsystem; Memory; A user interface; A processor configured to execute user applications and to interact with the memory, the wireless communication and the user interface, the processor configured to execute applications, a. Means for monitoring whether a signaling disconnection indication should be sent to the wireless network; b. Means for adding a cause for the signaling disconnection indication to the signaling disconnection indication; c. Means for sending an added signaling disconnection indication including the cause to identify a cause for the signaling disconnection indication together with the signaling disconnection indication. And a user device having a. An apparatus for a user device that facilitates release of a signaling connection, the apparatus comprising: a. A checker configured to check whether a signaling disconnection indication should be sent; b. A signaling disconnection indication transmitter configured to send the signaling disconnection indication instruction in response to an indication by the checker whether the signaling disconnection indication instruction should be transmitted, And the signaling disconnection indication instruction comprises a signaling release indication including a signaling release indication cause field. 22. The user of claim 21, wherein the checker is further configured to check whether signaling connection of the user device is necessary after sending the signaling disconnection indication and before confirming delivery of the signaling disconnection indication. Apparatus for the device. 23. The apparatus of claim 22 wherein the signaling disconnection indication transmitter is further configured to retransmit the signaling disconnection indication. A network device operated by a signaling disconnection indication, a. An investigator configured to examine a signaling release indication cause field of the signaling connection release indication and to determine whether the signaling release indication cause field indicates an abnormal state; b. An alarm generator optionally configured to generate an alarm if the investigation by the irradiator determines that the signal release instruction cause field indicates an abnormal state Network device comprising a. 25. The network device of claim 24, wherein the network device comprises a logical layer, the irradiator is implemented at a first layer of the logical layer, and the irradiator is further configured to request signaling disconnection from a second layer of the logical layer. Network device.

Images