HK1178361B

HK1178361B - Transmission of the pdp context activation rejection cause codes to the uicc

Info

Publication number: HK1178361B
Application number: HK13105024.4A
Authority: HK
Inventors: 让-菲利普．科米尔
Original assignee: Blackberry Limited
Priority date: 2011-04-26
Filing date: 2013-04-25
Publication date: 2016-08-26

Abstract

A method and system for introducing support for SM rejections in a USAT network rejection event including an APN. The method and system provide the UICC with all PDP Context activation rejection cause codes received by the ME and their respective APNs. Such a method and system allows the UICC to monitor all the rejections to intelligently select an appropriate APN to activate using its Open channel command.

Description

Transmission of PDP context activation rejection reason code to UICC

Priority declaration

This application claims priority to international patent application serial No. PCT/CA2011/050254 filed on month 4 and 26, 2011, which is incorporated herein by reference in its entirety.

Technical Field

The present invention relates generally to communication systems and methods of operating the same, and more particularly to transmission of a PDP context activation rejection cause code and a configuration request error code to a UICC.

Background

In known wireless telecommunication systems, transmission equipment in a base station or access equipment transmits signals in a geographical area which is considered to be a cell. As technology has evolved, higher level devices have been introduced that can provide services not previously possible. Such advanced equipment may include, for example, an E-UTRAN (evolved Universal terrestrial radio Access network) node B (eNB), a base station, or other systems and equipment. Such advanced devices or next generation devices are generally referred to as Long Term Evolution (LTE) devices, and packet-based networks using such devices are generally referred to as Evolved Packet Systems (EPS). Another example of advanced equipment includes evolved high rate packet data (eHRPD) type equipment, such as equipment compliant with the 3gpp2x.s0057v3.0 specification. An access device is any component, such as a legacy base station or an LTE eNB (evolved node B), that can provide a User Agent (UA), such as User Equipment (UE) or Mobile Equipment (ME), with access to other components in a telecommunications system.

In a mobile communication system, such as E-UTRAN, an access device provides wireless access to one or more UAs. The access device includes a packet scheduler for allocating Uplink (UL) and Downlink (DL) data transmission resources among all UAs communicating with the access device. Among other functions, the scheduler includes dividing air interface capacity among UAs, deciding resources (e.g., subcarrier frequency and timing) for packet data transmission for each UA, and monitoring packet allocation and system load. The scheduler allocates physical layer resources for Physical Downlink Shared Channel (PDSCH) and Physical Uplink Shared Channel (PUSCH) data transmissions and transmits scheduling information to the UA over a control channel. The UA refers to scheduling information for modulation and coding of timing, frequency, data block size, uplink and downlink transmissions as follows.

In some mobile communication systems, there is a need for a Universal Integrated Circuit Card (UICC) application, such as a subscriber identity card (SIM), an Internet Protocol (IP) multimedia subsystem (IMS) SIM (isim), and a Universal Terrestrial Radio Access Network (UTRAN) SIM (usim), a Removable User Identity Module (RUIM) or a Code Division Multiple Access (CDMA) user identity module (CSIM).

In some known mobile communication systems, the UICC may use USIM application toolkit (USAT) commands (e.g., open/close channel commands) to trigger a Packet Data Network (PDN) connection request or an activate Packet Data Protocol (PDP) context request on the ME. The use of these commands enables the UICC to send IP data to the network regarding the Access Point Name (APN) it selects. This end-to-end IP data session establishment may be used for features such as Bearer Independent Protocol (BIP) which provides a UICC with an IP interface to perform over-the-air updates. This interface is more efficient and also allows a larger number of updates than, for example, over-the-air (OTA) Short Message Service (SMS) mechanisms. Figure 1, labeled prior art, shows an example of UICC interaction with a network when performing USAT commands.

In some known mobile communication systems, the UICC may use CDMA Card Application Toolkit (CCAT) commands (e.g., open/close channel commands) to trigger a 3GPP2VSNCP configure request on the ME. The use of these commands enables the UICC to send IP data to the network regarding the Access Point Name (APN) it selects. This end-to-end IP data session establishment may be used for features such as Bearer Independent Protocol (BIP) which provides a UICC with an IP interface to perform over-the-air updates. This interface is more efficient and also allows a larger number of updates than, for example, over-the-air (OTA) Short Message Service (SMS) mechanisms.

With the advent of machine-to-machine M2M or Machine Type Communication (MTC), there is a presumption that the processing functions of M2M devices will reside inside the UICC, and thus it is likely that the UICC will require more input related to interaction from the network.

A problem associated with opening and closing channels is that the UICC is unaware of network failures that may occur during the PDP context activation procedure (see e.g. 3GPP TS 24.008) or during the PDN connectivity procedure (see e.g. 3GPP TS 24.301). In some systems, a UICC application implemented at a low level may attempt a PDP context or PDN connection retry that negatively impacts the network. For example, events occur that trigger all cards configured on the network to request a data session for OTA updates. A PDP context or PDN connection may be rejected based on a capacity shortage. If this state occurs, the UICC application should take its retry attempt back to allow the system to recover from this sudden increase in data activity. Figure 2, labeled prior art, shows an example of UICC retries that may affect the PDP context activation procedure or PDN connection procedure of the network.

Disclosure of Invention

A method and a system are provided for introducing support for SM (session management) rejection in a USAT network rejection event comprising an APN. The method and system provide the UICC with all SM causes included in the ACTIVATE PDP CONTEXT REJECT message received by the ME or the Evolved Session Management (ESM) causes included in the PDN connection REJECT message received by the ME and their corresponding APNs. This method and system allows the UICC to monitor all rejections to intelligently select the appropriate APN to include in the ACTIVATE PDP CONTEXT REJECT message or the PDN connectivity REJECT message using its open channel command.

In particular embodiments, the methods and systems include support for an SM cause information element in a USAT network rejection event. This support may be used in MEs without a corresponding APN. In this case, the ME provides the SM reason included in the ACTIVATE PDP CONTEXT REJECT message or the ME provides the ESM reason included in the PDN CONNECTIVITY REJECT message.

In other embodiments, the methods and systems use a terminal response to indicate to the UICC that there is a particular problem with the open channel command. In this embodiment, the ME provides a terminal response to acknowledge (acknowledge) the open channel command during the open channel procedure. In this embodiment, the ME includes the SM cause included in the ACTIVATE PDP CONTEXT REJECT message, or the ME provides the terminal response message with the ESM cause included in the PDN CONNECTIVITY REJECT message received from the network.

In particular embodiments, a method and a system are provided for introducing support for a 3GPP2VSNCP configuration request network reject event including an APN. This support provides the UICC with all error codes and their corresponding APNs included in the 3GPP2VSNCP configure reject message received by the ME. The method and system allows the UICC to monitor all denials to use its open channel command to intelligently select the appropriate APN to include in the 3GPP2VSNCP configure reject message.

In particular embodiments, the methods and systems introduce support for error codes in CCAT or USAT network rejection events. This support may be used for MEs without a corresponding APN. In this case, the ME provides an error code VSNCP configuration option included in the 3GPP2VSNCP configuration reject message.

In other embodiments, the methods and systems use a terminal response to indicate to the UICC that there is a particular problem with the open channel command. In this embodiment, the ME provides a terminal response to reply to the open channel command during the open channel procedure. In this embodiment, the ME includes an error code VSNCP configuration option included in the 3GPP2VSNCP configuration reject message.

Drawings

The invention, together with further objects, features and advantages thereof, may best be understood by reference to the following detailed description when read with the accompanying drawings in which:

figure 1, labeled as prior art, shows a flow diagram of UICC interaction with a network.

Figure 2, labeled prior art, shows a flow diagram of UICC retries that may affect PDP activation of the network.

Figure 3 shows a flow chart for informing the ME of the PDP context activation rejection triggered by the MMS session.

Figure 4 shows a flow diagram of the ME informing the UICC of the PDP context activation rejection after the open channel command.

Figure 5, labeled as prior art, shows a mapping of download profile bytes including a network rejection event bit.

Figure 6 shows a flow diagram of the ME informing the UICC about the PDP context activation rejection triggered by the MMS session.

Fig. 7 shows a flow diagram of the ME informing the UICC about the PDP context activation rejection due to the open channel failure.

Fig. 8 shows a flow chart when the terminal responds to the reason for providing a rejection.

FIG. 9 depicts an exemplary system in which the present invention may be implemented.

Fig. 10 illustrates a wireless communication system including an embodiment of a User Equipment (UE).

Fig. 11 is a simplified block diagram of an exemplary UE including a Digital Signal Processor (DSP).

FIG. 12 shows a simplified block diagram of a software environment that may be implemented by a DSP.

Detailed Description

In other embodiments, the methods and systems use a terminal response to indicate to the UICC that there is a particular problem with the open channel command. In this embodiment, the ME provides a terminal response to reply to the open channel command during the open channel procedure. In this embodiment, the ME includes the SM cause included in the ACTIVATE PDP CONTEXT REJECT message, or the ME provides the terminal response message with the ESM cause included in the PDN CONNECTIVITY REJECT message received from the network.

In particular embodiments, a method and a system are provided for introducing support for a 3GPP2VSNCP configuration request network reject event that includes an APN. This support provides the UICC with all error codes and their corresponding APNs included in the 3GPP2VSNCP configure reject message received by the ME. The method and system allows the UICC to monitor all denials to use its open channel command to intelligently select the appropriate APN to include in the 3GPP2VSNCP configure reject message.

Various illustrative embodiments of the present invention will now be described in detail with reference to the accompanying drawings. While various details are set forth in the following description, it will be appreciated that the present invention may be practiced without these specific details, and that numerous implementation-specific decisions may be made to the invention described herein to achieve the inventors' specific goals, such as compliance with process technology or design-related constraints, which may vary from one implementation to another. While such a development effort might be complex and time-consuming, it would nevertheless be a routine undertaking for those of ordinary skill in the art having the benefit of this disclosure. For example, selected aspects are shown in block diagram and flow diagram form, rather than in detail, in order to avoid limiting or obscuring the present invention. In addition, some portions of the detailed description provided herein are presented in terms of algorithms or operations on data within a computer memory. Such description and representations are used by those skilled in the art to describe and convey the substance of their work to others skilled in the art.

Referring now to fig. 3 and 4, there is shown a flow chart of the ME informing the UICC of the ACTIVATE PDP context request message or PDN CONNECTIVITY request message triggered by an MMS session or due to a failed open channel, respectively. More specifically, in particular embodiments, the USAT network rejection event including the APN further includes support for Session Management (SM) network rejection.

In particular embodiments, the UICC discovers that a network rejection event is supported by reading specific bits (e.g., the 5 th and 7 th bits) in the bytes of the download profile. In a particular embodiment, the bytes of the terminal profile correspond to the 25 th byte of the terminal profile download sent by the ME.

Fig. 5 shows the mapping of bytes of a terminal profile. In this mapping, one bit is used to indicate support for a network rejection event for a GERAN/UTRAN network and one bit is used to indicate support for a network rejection event for an E-UTRAN network.

If the ME indicates that any radio technology is supported, the UICC proceeds to register the network reject event in the SETUP EVENT LIST USAT command to enable receipt of the reject message.

Referring again to fig. 4, when the ME receives ACTIVATE PDP a context message or a PDN CONNECTIVITY REJECT message from the network and the network REJECT event is registered in the REJECT event list, the ME issues the network REJECT event to the UICC. In one embodiment, the event includes the APN included in the original ACTIVATE PDP CONTEXT REJECT message or the PDN CONNECTIVITY REJECT message.

Furthermore, in certain embodiments, all SM cause information elements included in the REJECT message received by the ME are issued to the UICC. In certain other embodiments, the SM cause information element included in the REJECT message received by the ME associated with the UICC is sent to the UICC. These relevant SM cause information elements include SM cause information elements received as part of some UICC open channel BIP/IP activity.

More specifically, the UICC provides the set of events using the SETUP EVENT LIST USAT command. The set of events becomes a current list of events to be monitored by the terminal. Any subsequent SET update LIST command will replace the current event LIST provided in the previous SET UP EVENT LIST command. The SET UP EVENT LIST command may also be used to remove the entire list of events currently in the terminal (see item 6.6.16 of ETSI TS 102223 v9.1.0). If the terminal powers off or removes the UICC or performs a reset, the event list provided by the UICC in the last SET UP EVENT LIST command is removed.

When the TERMINAL has successfully accepted or removed the event list, the TERMINAL sends a TERMINAL RESPONSE message to the UICC (command successfully executed). When the TERMINAL is not able to successfully accept or remove the event list, the TERMINAL sends a TERMINAL RESPONSE (command to exceed the TERMINAL's capabilities) message to the UICC. When one of the events in the current list occurs, the terminal uses the event download mechanism to deliver the details of the event to the UICC (see ETSI TS 102223 v9.1.0, article 7.5 and 3GPP 31.111 v.9.1.0).

For event list byte encoding, in addition to these values in ETSI TS 102223v.9.1.0, a number of values are defined. These values include:

11 ═ I-WLAN access state

12 ═ network rejection

15 CSG cell selection

If the network rejection EVENT is part of the current EVENT list (e.g. see ETSI TS 102223 v.9.1.0) (established by the last SET UP EVENT LIST command), then in the case of GERAN/UTRAN, if the terminal receives a LOCATION update REJECT message or GPRS ATTACH REJECT message or a ROUTING area REJECT message or ACTIVATE PDP control REJECT message (defined in TS 24.008), or if the terminal does not register successfully with the IMS, or in the case of E-UTRAN, if the terminal receives an ATTACH REJECT message, a TRACKING area REJECT message, or a PDN CONNECTIVITY REJECT message, the terminal notifies the UICC that the EVENT has occurred by using an EVENT (EVENT downlink-network rejection EVENT) command. The direction of the command is ME to UICC and the command header is specified in 3GPP TS 31.101. The structure of the ENVELOPE (EVENT DOWNLOAD-network rejection EVENT) command is set forth in Table 1.

● Command parameters/data

TABLE 1

Event list: the event list data object will include only one event (value part of 1 byte in length) and the terminal sets the event to:

network rejection event

-a device identity: the terminal shall set the device identity to:

the source: a network;

destination: a UICC.

-location information: this data object should only exist when the ME receives the LOCA TION UPDA TINGREJECT message and will include the identity of the rejecting network (MCC, MNC, and LAC).

-a routing area identification: the data object should only exist when the MC receives the GPRS A TTACHREJECT message, the ROUTING AREAD UPDATE REJECT message, the ACTIVATE PDPCONTEXT REJECT message, and should include the identity of the rejecting network (MCC, MNC, LAC and RAC).

-tracking area identification: the data object should only exist when the ME receives an EMMA TTACHREJECT message, an TRA CKING AREA UPDA TE REJECT message, or a PDNCONNECTIVITY REJECT message, and should include the targets (MCC, MNC, and TAC) that REJECT the network.

-access technology: the data object should include an access technology that denies the network.

Update/attach type/activation: the data object includes an update, attach, or activation type used in the registration request message.

-reject cause code: the data object includes a reason code value received in a registration or reject message.

-PDP context activation parameters: the data object includes NAS signaling messages sent during PDP context activation. The data object exists only as a result of either GERAN or utran pdp context activation rejection.

EPS PDN connection activation parameter: the data object includes NAS signaling messages sent during the PDN activation request. The data object exists only as a result of a rejection of EUTRAN PDN context activation.

Response parameters/data: for this type of ENVELOPE command, none.

The update, attach and activation parameters for the message are set forth in table 2.

Byte(s)	Description of the invention	Length of
			1	Update/attach/activate type flag	1
2	Length of	1
			3	Update/attach/activate type	1

TABLE 2

Content:

in the case of GERAN/UTRAN, the terminal shall take this message as a mechanism to indicate to the UICC the type of LOCATION update sent in the LOCATION update REQUEST message, or the type of update sent in the GPRS attach REQUEST or ROUTING AREA update REQUEST message or PDP CONTEXT activity REQUEST, as specified in TS 24.008.

In the case of E-UTRAN, the terminal shall take this message as a mechanism to indicate to the UICC the EPS ATTACH type sent in ATTACH REQUEST, TRACKING AREA UPDATE REQUEST, PDN connectitvityrequest messages, as specified in TS 24.301.

Coding:

- '00' — "normal LOCATION update" in the case of the LOCATION update REQUEST message,

"01" in the case of a LOCATION update REQUEST message,

- '02' — "IMSI attach" in the case of a LOCA TION uplink timing REQUEST message,

- '03' — "GPRS attach" in case of GPRS ATTACH REQUEST message;

- '04' — a "combined GPRS/IMSI attach" in the case of GPRS ATTACH REQUEST message;

- '05' — "RA UPDATE" in the case of ROUTING AREA UPDATE REQUEST message:

- '06' — a "combined RA/LA UPDATE" in the case of ROUTING AREA UPDATE REQUEST message,

- '07' — "combined RA/LA UPDATE with IMSI attach" in case of ROUTING AREA UPDATE REQUEST message,

"08" — a "periodic UPDATE" in the case of a ROUTINGAREA UPDATE REQUEST message,

- '09' — "EPS attach" in the case of EMMA TTACH REQUEST message,

- '0A' — a "combined EPS/IMSI attach" in the case of the EMMA TTACH REQUEST message,

- '0B' — TA UPDATE in the case of the EMM TRACKING AREA UPDATE REQUEST message,

- '0C' — a "combined TA/LA update" in the case of the EMM TRACKING AREA UPDA TE REQUEST message,

'0D' — a "combined TA/LA UPDATE with IMSI attach" in the case of the EMM TRACKING AREA UPDATE REQUEST message,

- '0E' — a "periodic update" in the case of the EMM TRACKING AREA UPDA TE REQUEST message,

- '0F' -PDP CONTEXT activation REQUEST in the case of ACTIVATE PDP CONTEXT REQUEST message,

- '10' — a "dedicated PDN context activation REQUEST" in case of a PDN CONNECTIVITY REQUEST message,

all other values are reserved for future use

The reject reason code object parameter for the message is set forth in table 3.

Byte(s)	Description of the invention	Length of
			1	Reject reason code marking	1
2	Length of	1
			3	Reject reason code (Note)	1

TABLE 3

For GERAN/UTRAN, in the case of the LOCATION UPDATING REJECT message, the object includes the REJECT cause received in the LOCATION UPDATING REJECT message. The rejection reason is encoded in the same way as the value part of the rejection reason information element specified in TS 24.008.

For GERAN/UTRAN, in the case of GPRS ATTACH REJECT message or ROUTING AREA UPDATE REJECT message, the object includes the GMM cause received in the GPRSATTACH REJECT message or ROUTING AREA UPDATE REJECT message. The GMM cause is encoded in the same way as the value part of the GMM cause information element specified in TS 24.008.

For GERAN/UTRAN, in the case of the ACTIVATE PDP CONTEXT REJECT message, the object includes the SM cause received in the ACTIVATE PDP CONTEXT REJECT message. The SM cause is encoded in the same manner as the value part of the SM cause information element specified in TS 24.008.

For E-UTRAN, in the case of either the EMM ATTACH REJECT message or the EMMTRACKING AREA UPDATE REJECT message, the object includes the EMM reason received in the EMM ATTACH REJECT message, the EMM TRACKING AREA UPDATEREJECT message or the PDN CONNECTION REJECT message. The EMM cause is encoded in the same way as the value part of the EMM cause information element specified in TS 24.301.

Referring to fig. 6, in certain embodiments, the USAT network rejection event includes support for SM rejection. In particular embodiments, the UICC discovers the support network rejection event feature by reading certain bits (e.g., the 5 th and 7 th bits) in the bytes of the download profile. In a particular embodiment, the bytes of the download profile correspond to the 25 th byte of the profile download sent by the ME.

Referring again to fig. 5, a mapping of bytes of the terminal profile. In this mapping, one bit is used to indicate support for a network rejection event for a GERAN/UTRAN network and one bit is used to indicate support for a network rejection event for an E-UTRAN network. More specifically, in this embodiment, the UICC discovers support for the network rejection event feature by reading the 5 th and 7 th bits in the 25 th byte of the profile download sent by the ME.

If event driven information extension is supported in any radio technology, the UICC proceeds to register the network rejection event into the SETUP EVENT LIST USAT command to enable reception of the rejection message.

Referring again to fig. 6, when the ME receives ACTIVATE PDP a context message or a PDN CONNECTIVITY REJECT message from the network and the network REJECT event is registered in the REJECT event list, the ME issues the network REJECT event to the UICC. In particular embodiments, the event includes the APN (or other parameter) included in the original ACTIVATE PDP CONTEXT REQUEST message or the PDN connectitvityrequest message.

Furthermore, in certain embodiments, all SM cause information elements included in the REJECT message received by the ME are issued to the UICC. In certain other embodiments, the SM cause information element included in the UICC related REJECT message received by the ME is sent to the UICC. These relevant SM cause information elements include SM cause information elements received as part of some open channel UICC BIP/IP activity.

For event list byte encoding, in addition to the values in ETSI TS 102223v.9.1.0, a number of values are defined. These values include:

11 ═ I-WLAN access state

12 ═ network rejection

15 CSG cell selection

If the network rejection EVENT is part of the current EVENT list (established by the last SET UP EVENT LIST command) (see, e.g., ETSI TS 102223 v.9.1.0)), then in the case of GERAN/UTRAN, if the terminal receives a LOCATION update request message or GPRS ATTACH REJECT message or a ROUTING area update request message or ACTIVATE PDP control request message (defined in TS 24.008), or the terminal does not successfully register with the IMS, or in the case of E-UTRAN, if the terminal receives an ATTACH request message, a TRACKING area update request message, or a PDN CONNECTIVITY request message, the terminal notifies the UICC that the EVENT has occurred by using an EVENT (EVENT downlink-network rejection EVENT) command. The direction of the command is ME to UICC and the command header is specified in 3GPP TS 31.101. The structure of the ENVELOPE (EVENT DOWNLOAD-network reject EVENT) command is set forth in Table 4.

Command parameter/data

Description of the invention	Clause and subclause	M/O	Min	Length of
					Event download tagging	9.1	M	Y	1
Length (A + B + (C or D or I) + E + F + G + H)	-	M	Y	1
					Event list	8.25	M	Y	A
Device identity	8.7	M	Y	B
					Location information	8.19	C	N	C
Routing area identification	8.91	C	N	D
					Tracking area identification	8.99	C	N	I
Access technology	8.62	M	Y	E
					Update/attach/activate type	8.92	M	Y	G
Reject reason code	8.93	M	Y	H

TABLE 4

Event list: the event list object will include only one event (value part of 1 byte in length) and the terminal sets the event to:

network rejection event

-a device identity: the terminal shall set the device identity to:

the source: a network;

destination: a UICC.

-location information: this data object should only exist when the ME receives the LOCA TION UPDATINGREJECT message and will include the identity of the rejecting network (MCC, MNC, and LAC).

-a routing area identification: the data object should only exist when the MC receives the GPRS attach REJECT message, the ROUTING area update message, the ACTIVATE PDPCONTEXT REJECT message, and should include the identity of the REJECT network (MCC, MNC, LAC and RAC).

-tracking area identification: the data object should only exist when the ME receives an EMMA ATTACHROUCT message, a TR4CKING AREA UPDATE REJECT message, or a PDNCONNECTIVITY REJECT message, and should include the identity of the rejecting network (MCC, MNC, and TAC).

Response parameters/data: for this type of ENVELOPE command, none.

The update, attach and activation parameters for the message are set forth in table 5.

TABLE 5

Content:

Coding:

"01" in the case of a LOCATION update REQUEST message,

- '02' — IMSI attach in the case of LOCATION update timing REQUEST message,

- '03' — "GPRS attach" in case of GPRS attach request message;

- '04' — a "combined GPRS/IMSI attach in the case of GPRS ATTACH REQUEST message;

- '05' — "RA UPDATE" in case of ROUTING AREA UPDATE REQUEST message;

- '06' — "combined RA/LA UPDATE" in the case of ROUTING AREA UPDATE REQUEST message;

- '08' — "periodic UPDATE" in the case of ROUTING AREA UPDATE REQUEST message,

- '09' — "EPS attach" in the case of EMMA TTACH REQUEST message,

- '0C' — a "combined TA/LA UPDATE" in the case of the EMM TRACKING AREA UPDATE REQUEST message,

"attach updated integrated TA/LA with IMSI" in the case of EMM TRACKING AREA UPDATE REQUEST message,

- '0E' — a "periodic UPDATE" in the case of the EMM TRACKING AREA UPDATE REQUEST message,

- '0F ═ PDP context activation request', in the case of the ACTIVATE PDP context request message

all other values are reserved for future use

The reject reason code object parameter for the message is set forth in table 6.

Byte(s)	Description of the invention	Length of
			1	Reject reason code marking	1
2	Long and longDegree of rotation	1
			3	Reject reason code (Note)	1

TABLE 6

Referring to fig. 8, a flow chart when the terminal responds to the reason for providing a rejection is shown. More specifically, in certain embodiments, the terminal response may be used to indicate to the UICC via the channel status that there is a particular problem with the open channel command.

More specifically, the UICC sends an open channel command to trigger the PDP context activation procedure or PDN connectivity procedure, the ME attempts to activate but is rejected by the network. The ME then sends a terminal response including an indication that the network is currently unable to process the command, and the SM cause value or EMM cause value included in the channel state as described in table 6. In other embodiments, the reject reason code TLV described above may be used as another container in the terminal response.

When the TERMINAL issues a successful TERMINAL RESPONSE for the GET CHANNEL STATUS proactive command, the TERMINAL RESPONSE includes as many channel state data objects as there are available channels. When the TERMINAL issues a successful TERMINAL RESPONSE for the OPENCHANNEL command, the TERMINALRESPONSE includes a channel state data object for the opened channel. When the TERMINAL issues an unsuccessful TERMINAL RESPONSE for the OPEN CHANNEL command due to the ME receiving ACTIVATE PDP a CONTEXT RESPONSE message or a PDN connectivity RESPONSE message, the TERMINAL RESPONSE includes a CHANNEL state data object for the opened CHANNEL indicating the type of failure and the SM cause value or EMM cause value included in the ACTIVATE PDP CONTEXT RESPONSE message or the PDN connectivity RESPONSE message received by the network. The structure of the channel state clauses is set forth in table 7.

Byte(s)	Description of the invention	Length of
			1	Channel state marking	1
2	Length (3)	1
			3 to 5	Channel state	3

TABLE 7

Content:

-the channel state is a binary coded string

Coding:

-byte 3:

■ bits 1 to 3: channel identifiers 1 to 7;

channel identifier 0 means "no channel available".

For CS, packet data service, local and default (network) bearers:

■ bits 4 to 7: RFU.

■ bit 8: 0 ═ no link established or no packet data service activated;

1-established link or activated packet data service.

For UICC server mode:

■ bits 4 to 6: RFU.

■ bits 7, 8: TCP in CLOSED state 00;

TCP in LISTEN state 01;

TCP in the ESTABLISHED state 10 ═ ESTABLISHED;

and 11 is reserved.

For terminal server mode and TCP:

■ bits 4 to 6: RFU.

■ bits 7, 8: TCP in CLOSED state 00;

01 ═ retention;

TCP with 10 ═ ESTABLISHED state

And 11 is reserved.

For terminal server mode and UDP:

■ bits 4 to 8: REU.

Byte 4:

■ '00' no further information can be given;

■' 01 ═ unused;

■ '02' unused;

■ '03' — unused;

■ '04' unused;

■' 05 ═ link drop (network failure or user cancellation);

■ '06' — network rejected PDP/PDN activation

■ retain all other values.

Byte 5 (see comments):

■ rejecting reason codes

Note that: only when byte 4 is set to '06', byte 5 should be set. For all other values of byte 4, it should be set to 0 xFF.

Fig. 9 illustrates an example of a system 900 suitable for implementing one or more embodiments disclosed herein. In various embodiments, system 900 includes a processor 910, which may be referred to as a Central Processing Unit (CPU) or Digital Signal Processor (DSP), a network connectivity devices 920, a Random Access Memory (RAM)930, a Read Only Memory (ROM)940, a secondary storage 950 and input/output (I/O) devices 960. In some embodiments, some of these components may not be present, or may be combined in various combinations with each other or with other components not shown. These components may be located in a single physical entity or in a plurality of one physical entities. Any of the actions described herein that are taken by processor 910 may be performed solely by processor 910, or may be performed by processor 910 in conjunction with one or more components shown or not shown in fig. 9.

The processor 910 executes instructions, code, computer programs, or scripts that are accessible from the network connectivity devices 920, RAM930, or ROM 940. Although only one processor 910 is shown, multiple processors may be present. Thus, although instructions may be described as being executed by the processor 910, instructions may be executed concurrently, serially, etc., by one or more processors 910 implemented as one or more CPU chips.

In various embodiments, the network connection device 920 may take the form of: modems, modem banks, Ethernet devices, Universal Serial Bus (USB) interface devices, serial interfaces, token ring devices, Fiber Distributed Data Interface (FDDI) devices, Wireless Local Area Network (WLAN) devices, radio transceiver devices such as Code Division Multiple Access (CDMA) devices, global system for mobile communications (GSM) radio transceiver devices (e.g., WCDMA, HSPA, and LTE type devices), Worldwide Interoperability for Microwave Access (WiMAX) devices, and/or other well-known devices for connecting to networks. These network connectivity devices 920 may enable the processor 910 to communicate with the internet, or one or more telecommunications networks, or other networks, from which the processor 910 may receive information or to which the processor 910 may output information.

The network connection device 920 may also be capable of wirelessly transmitting or receiving data in the form of electromagnetic waves (e.g., radio frequency signals or microwave frequency signals). The information transmitted or received by the network connection device 920 may include data that has been processed by the processor 910 or instructions to be executed by the processor 910. The data may be ordered according to different sequences as may be desired for processing or generating the data, or transmitting or receiving the data.

In various embodiments, RAM930 may be used to store volatile data and instructions that are executed by processor 910. The ROM 1040 shown in figure 9 may be used to store instructions and perhaps data that are read during execution of the instructions. Typically, access to RAM930 and ROM940 is faster than to secondary storage 950. Secondary storage 950 typically includes one or more hard disk drives or tape drives and may be used for non-volatile storage of data, or secondary storage 950 may be used as an over-flow data storage device if RAM930 does not hold all working data large enough. Secondary storage 1050 may be used to store programs that are loaded into RAM930 when such programs are selected for execution. The I/O devices 960 may include a Liquid Crystal Display (LCD), touch screen display, keyboard, keypad, switch, dial, mouse, trackball, voice recognizer, card reader, paper tape reader, printer, video monitor, or other well-known input/output devices.

Fig. 10 shows a wireless communication system including an embodiment of a User Equipment (UE) 1102. Although the UE1002 is illustrated as a mobile telephone, the UE1002 may take many forms, including a wireless handset, a pager, a Personal Digital Assistant (PDA), a portable computer, a tablet computer, or a laptop computer. A number of suitable devices combine some or all of these functions. In some embodiments, the UE1002 is not a general purpose computing device such as a portable computer, laptop computer, or tablet computer, but is a special purpose communication device such as a mobile phone, wireless handset, pager, PDA, or vehicle-mounted telecommunication device. Likewise, the UE1002 may be a device, may include a device, or may be included in a device with similar capabilities but that is not transportable (e.g., a desktop computer, a set-top box, or a network node). In these and other embodiments, the UE1002 may support specific activities such as gaming, inventory control, job control, and/or task management functions, among others.

In various embodiments, the UE1002 includes a display 1004. Likewise, the UE1002 includes a touch-sensitive surface, keyboard, or other input keys 1006 that a user typically uses for input. In these and other environments, the keyboard may be a full or reduced alphanumeric keyboard such as QWERTY, Dvorak, AZERTY, and sequential-keypad types, or a traditional numeric keyboard with alphabet letters associated with a telephone keypad. Likewise, the input keys may include a track wheel, an exit or space key, a trackball, and other navigation or function keys that may be pressed inward to provide another input function. Likewise, the UE1002 may present options for user selection, for user-initiated controls, for a cursor or other indicator pointed to by the user.

The UE1002 may also accept data input from a user, including dialing numbers or various parameter values for configuring the operation of the UE 1002. The UE1002 may also execute one or more software or firmware applications in response to user commands. In response to user interaction, these applications may configure the UE1002 to perform a variety of customized functions. UE1002 may also be programmed or configured via over-the-air (OTA), e.g., originating from wireless base station 1010, server 1016, wireless network access node 1008, or peer UE 1002.

Among the various applications that may be executed by the UE1000 is a web browser, which enables the display 1004 to display web pages. The web page may be obtained by wirelessly communicating with a wireless network access node 1008 (e.g., a cell tower, a peer UE 1102, or any other wireless communication network 1012 or system). In various embodiments, wireless network 1012 is coupled with a wired network 1014, such as the internet. The UE 1102 accesses information on various servers, such as the server 1016, through the wireless network 1012 and the wired network 1114. The server 1016 may provide content that may be displayed on the display 1004. Alternatively, the UE1002 may access the wireless network 1012 through the peer UE1002 acting as an intermediary in a relay-type or hop-type connection. Those skilled in the art will recognize that many such embodiments are possible, and that the preceding embodiments are not intended to limit the spirit, scope, or purpose of the present disclosure.

FIG. 11 depicts a block diagram of an exemplary User Equipment (UE) in which the present invention may be implemented. Although various components of the UE1002 are described, various embodiments of the UE1002 may include a subset of the listed components or additional components not listed. As shown in fig. 11, the UE1002 includes a Digital Signal Processor (DSP)1002 and a memory 1104. As shown, the UE1002 may also include an antenna and front end unit 1106, a Radio Frequency (RF) transceiver 1108, an analog baseband processing unit 1110, a microphone 1112, an earpiece speaker 1114, a headset port 1116, an input/output (I/O) interface 1118, a removable memory card 1220, a Universal Serial Bus (USB) port 1122, a short-range wireless communication subsystem 1124, an alarm 1126, a keypad 1128, a Liquid Crystal Display (LCD)1130, which may include a touch-sensitive surface, an LCD controller 1132, a charge-coupled device (CCD) camera 1134, a camera controller 1136, and a Global Positioning System (GPS) sensor 1138. In various embodiments, the UE1002 may include another display that does not provide a touch sensitive screen. In an embodiment, the DSP1202 may communicate directly with the memory 1104 without passing through the input/output interface 1118.

In various embodiments, the DSP1102, or some other form of controller or Central Processing Unit (CPU), operates to control the various components of the UE1002 in accordance with embedded software or firmware stored in the memory 1104, or stored in memory included in the DSP1102 itself. In addition to the embedded software or firmware, the DSP1102 may execute other applications stored in the memory 1104 or made available through information carrier media such as portable data storage media like the removable memory card 1120 or through wired or wireless network communications. The application software may comprise a compiled set of machine-readable instructions that configure the DSP1102 to provide the desired functionality, or the application software may be high-level software instructions that are processed by an interpreter or compiler to indirectly configure the DSP 1102.

An antenna and front end unit 1106 is provided to convert between wireless signals and electrical signals, enabling the UE1002 to send information to, or receive information from, a cellular network or some other available wireless communication network or peer UE 1002. In an embodiment, the antenna and front end unit 1106 may include multiple antennas to support beamforming and/or Multiple Input Multiple Output (MIMO) operations. Those skilled in the art will appreciate that MIMO operation may provide spatial diversity, which may be used to overcome difficult channel conditions or improve channel throughput. Likewise, the antenna and front end unit 1106 may include antenna tuning or impedance matching components, RF power amplifiers, or low noise amplifiers.

In various embodiments, RF transceiver 1108 provides frequency shifting, converts received RF signals to baseband, and converts baseband transmit signals to RF. In some descriptions, a radio transceiver or RF transceiver may be understood to include other signal processing functions such as modulation/demodulation, encoding/decoding, interleaving/deinterleaving, spreading/despreading, Inverse Fast Fourier Transform (IFFT)/Fast Fourier Transform (FFT), cyclic prefix addition/removal, and other signal processing functions. For clarity, the description herein separates the description of such signal processing from the RF and/or radio stages and conceptually distributes the signal processing to the analog baseband processing unit 1110 or the DSP1102 or other central processing unit. In some embodiments, the RF transceiver 908, a portion of the antenna and front end 1106, and the analog baseband processing unit 1110 may be combined in one or more processing units and/or Application Specific Integrated Circuits (ASICs).

The analog baseband processing unit 1110 may provide various analog processing of inputs and outputs, such as analog processing of inputs from the microphone 1112 and the headset 1116 and analog processing of outputs to the headset 1114 and the headset 1116. To this end, the analog baseband processing unit 1110 may have a port for connecting to the earpiece speaker 1114, where the built-in microphone 1212 and the earpiece speaker 1114 enable the UE1002 to be used as a mobile phone. The analog baseband processing unit 1110 may also include a port for connection to a headset or other hands-free microphone and speaker configuration. The analog baseband processing unit 1110 may provide digital-to-analog conversion of one signal direction and analog-to-digital conversion of the opposite signal direction. In various embodiments, at least some of the functionality of the analog baseband processing unit 1110 may be provided by digital processing components, such as by the DSP1102 or other central processing unit.

The DSP1102 may perform modulation/demodulation, encoding/decoding, interleaving/deinterleaving, spreading/despreading, Inverse Fast Fourier Transform (IFFT)/Fast Fourier Transform (FFT), cyclic prefix addition/removal, and other signal processing functions associated with the wireless communication. In an embodiment, for example, in a Code Division Multiple Access (CDMA) technology application, the DSP1102 may perform modulation, coding, interleaving, and spreading for transmitter functions and despreading, deinterleaving, decoding, and demodulation for receiver functions. In another embodiment, for example in an Orthogonal Frequency Division Multiple Access (OFDMA) technology application, for a transmitter function the DSP1102 may perform modulation, coding, interleaving, inverse fast fourier transform, and cyclic prefix addition, and for a receiver function the DSP1102 may perform cyclic prefix removal, fast fourier transform, deinterleaving, decoding, and demodulation. In other wireless technology applications, the DSP1102 may perform other signal processing functions, as well as combinations of signal processing functions.

The DSP1102 may communicate with a wireless network via the analog baseband processing unit 1110. In some embodiments, the communication may provide Internet connectivity, enable a user to access content on the Internet, and send and receive e-mail or text messages. The input/output interface 1118 is interconnected to the DSP1102 and various memories and interfaces. The memory 1104 and the removable memory card 1120 may provide software and data to configure the operation of the DSP 1102.

The interfaces may be a USB interface 1122 and a short-range wireless communication subsystem 1124. The USB interface 1122 may be used to charge the UE1002 and may also enable the UE1002 to function as a peripheral device to exchange information with a personal computer or other computer system. The short-range wireless communication subsystem 1124 may include an infrared port, a bluetooth interface, an IEEE 802.11 compliant wireless interface, or any short-range wireless communication subsystem that may enable the UE1002 to communicate with other nearby mobile devices and/or wireless base stations.

The input/output interface 1218 may also connect the DSP1102 to an alert 1126, wherein when triggered, the alert 1126 causes the UE1002 to provide a notification to the user, for example, by ringing, playing music, or vibrating. The alert 1126 may serve as a mechanism for alerting the user to any of a variety of events, such as an incoming call, a new text message, and an appointment reminder, by silently vibrating, or by playing a particular pre-arranged music for a particular caller.

The keypad 1128 couples to the DSP1102 through the I/O interface 1118 to provide a mechanism for the user to select, enter information, and provide input to the UE 1002. The keyboard 1128 may be a full or reduced alphanumeric keyboard such as QWERTY, Dvorak, AZERTY, and sequential type, or a traditional numeric keyboard with alphabet letters associated with a telephone keypad. Likewise, the input keys may include a track wheel, an exit or space key, a trackball, and other navigation or function keys that may be pressed inward to provide another input function. Another input mechanism may be the LCD 1130, which may include touch screen capabilities, and also display text and/or images to the user. An LCD controller 1132 couples the DSP1102 to the LCD 1130.

If a CCD camera 1134 is provided, the CCD camera 1134 enables the UE1002 to take digital pictures. The DSP1102 communicates with the CCD camera 1134 through a camera controller 1136. In another embodiment, a camera operating according to a different technology than a CCD camera may be employed. The GPS sensor 1138 is coupled to the DSP1102 to decode global positioning system signals to enable the UE1002 to determine its location. Various other peripheral devices may also be included to provide additional functionality, such as radio and television reception.

Fig. 12 illustrates a software environment 1202 that may be implemented by the DSP 1102. The DSP1102 executes an operating system driver 1204, which operating system driver 1204 provides a platform for the rest of the software to work on. The operating system drivers 1204 provide drivers of the UE 1202 hardware with a standardized interface that can access application software. The operating system drivers 1204 include an Application Management Service (AMS)1206 for passing control between applications running on the UE 1202. Further, FIG. 12 shows a web browser application 1208, a media player application 1210, and a Java applet 1212. The web browser application 1208 configures the UE1002 to function as a web browser to allow a user to enter information into forms and select links to retrieve and view web pages. The media player application 1210 configures the UE1002 to retrieve and play audio or audio-visual media. The Java applet 1212 configures the UE1002 to provide games, utilities, and other functions. The assembly 1214 may provide the functionality described herein. UE1002, base station 1010, and other components described herein may include a processing component capable of executing instructions related to the actions described above.

While several embodiments have been provided in the present disclosure, it should be understood that the disclosed systems and methods may be embodied in many other specific forms without departing from the spirit or scope of the present disclosure. The present examples are to be considered as illustrative and not restrictive, and the intention is not to be limited to the details given herein. For example, various elements or components may be combined or integrated into another system or certain features may be omitted, or not implemented.

As used herein, the terms "component," "system," and the like are intended to refer to a computer-related entity, either hardware, a combination of hardware and software, or software in execution. For example, a component may be, but is not limited to being, a process running on a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a computer and the computer can be a component. One or more components can reside within a process and/or thread of execution and a component can be localized on one computer and/or distributed between two or more computers.

As used herein, the terms "user equipment" and "UE" may refer to wireless devices such as mobile telephones, Personal Digital Assistants (PDAs), handheld or laptop computers, and similar devices or other user agents ("UAs") having telecommunications capabilities. In some embodiments, a UE may refer to a mobile, wireless device. The term "UE" may also refer to devices with similar capabilities but which are generally not mobile, such as a desktop computer, a set-top box, or a network node. Further, as used herein, the term UE refers to a device that includes a memory card, however, a device that does not include a memory card is generally referred to as an ME. In other words, the UE is a combination of the ME and the memory card.

Furthermore, the disclosed subject matter may be implemented as a system, method, apparatus, or article of manufacture by: software, firmware, hardware, or any combination thereof, is generated using standard programming and/or engineering techniques to control a computer or processor based device to implement aspects described in detail herein. The term "article of manufacture" (or alternatively, "computer program product") as used herein is intended to encompass a computer program accessible from any computer-readable device, carrier, or media. For example, computer-readable media may include, but are not limited to, magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips.), optical disks (e.g., Compact Disk (CD), Digital Versatile Disk (DVD)), smart cards, and flash memory devices (e.g., card, stick). Of course, those skilled in the art will recognize many modifications may be made to this configuration without departing from the scope or spirit of the claimed subject matter.

The word "exemplary" is used herein to mean serving as an example, instance, or illustration. Any aspect or design described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other aspects or designs. Those skilled in the art will recognize many modifications may be made to this configuration without departing from the scope, spirit or intent of the claimed subject matter. Furthermore, the disclosed subject matter may be implemented as a system, method, apparatus, or article of manufacture by: software, firmware, hardware, or any combination thereof, is generated using standard programming and/or engineering techniques to control a computer or processor based device to implement aspects described in detail herein.

Moreover, techniques, systems, subsystems, and methods described and illustrated in the various embodiments as discrete or separate may be combined or integrated with other systems, modules, techniques, or methods without departing from the scope of the present disclosure. Other items shown or discussed as coupled or directly coupled or communicating with each other may be indirectly coupled or communicating through some interface, device, or intermediate component whether electrically, mechanically, or otherwise. Other examples of changes, substitutions, and alterations are ascertainable by one skilled in the art and could be constructed without departing from the spirit and scope disclosed herein. Although the present invention has been described in detail, it should be understood that various changes, substitutions and alterations can be made hereto without departing from the spirit and scope of the invention as defined by the appended claims.

Claims

1. A method of providing support for a session management, SM, reason code in a universal terrestrial radio access network user identity module application toolkit, USAT, network rejection event, the method comprising:

receiving an open channel command from a universal integrated circuit card UICC to trigger a packet data protocol PDP context activation procedure;

receiving, by the mobile equipment ME, an activate packet data protocol PDP context reject message including the SM cause; and

providing the UICC with the SM reason received by the ME.

2. The method of claim 1, wherein

The USAT network rejection event comprises an Access Point Name (APN); and

the method further comprises the following steps:

providing the UICC with an activate PDP context reject cause and a corresponding APN received by the ME.

3. The method of claim 2, further comprising:

monitoring all rejections by UICC; and

selecting an alternative APN by an open channel command to activate based on the monitoring.

4. The method of claim 1, further comprising:

providing, by the ME, a reason to receive with the activate PDP context reject.

5. The method of claim 1, further comprising:

indicating to the UICC using the terminal response: there are particular problems with the open channel command.

6. The method of claim 5, further comprising:

providing, by the ME, a terminal response to the open channel command during an open channel procedure.

7. The method of claim 6, further comprising:

adding, by the ME, the activate PDP context reject cause received from the network to a terminal response message.

8. An apparatus for providing support for a session management, SM, reason code in a universal terrestrial radio access network, user identity module, USAT, network rejection event, the apparatus comprising:

means for receiving an open channel command from a universal integrated circuit card, UICC, to trigger a packet data protocol, PDP, context activation procedure;

means for receiving, by the mobile equipment ME, an activate packet data protocol PDP context reject message including the SM reason; and

means for providing the UICC with the SM reason received by the ME.

9. The apparatus of claim 8, wherein

The USAT network rejection event comprises an Access Point Name (APN); and

the apparatus further comprises:

means for providing the UICC with an activate PDP context reject cause and a corresponding APN received by the ME.

10. The apparatus of claim 9, further comprising:

means for monitoring all rejections by the UICC; and

means for selecting an alternative APN to activate based on the monitoring by an open channel command.

11. The apparatus of claim 8, further comprising:

means for providing, by the ME, a reason for receipt with the activate PDP context rejection.

12. The apparatus of claim 8, further comprising:

means for indicating to the UICC that there is a particular problem with the open channel command using the terminal response.

13. The apparatus of claim 12, further comprising:

means for providing a terminal response by the ME to reply to the open channel command during an open channel procedure.

14. The apparatus of claim 13, further comprising:

means for adding, by the ME, the activate PDP context reject cause received from the network to a terminal response message.

15. A method of providing support for evolved session management, ESM, reason codes in a universal terrestrial radio access network user identity module application toolkit, USAT, network rejection event, the method comprising:

receiving an open channel command from a Universal Integrated Circuit Card (UICC) to trigger a Packet Data Protocol (PDP) context attach procedure;

receiving, by the mobile equipment ME, a packet data network PDN connection reject message including an ESM cause; and

providing the UICC with the ESM reason received by the ME.

16. The method of claim 15, wherein

The USAT network rejection event includes an access point name APN; and

the method further comprises the following steps:

providing the UICC with the PDN connection rejection cause and the corresponding APN received by the ME.

17. The method of claim 16, further comprising:

monitoring all rejections by UICC; and

18. The method of claim 15, further comprising:

providing, by the ME, a reason to receive with the PDN connection rejection.

19. The method of claim 15, further comprising:

20. The method of claim 19, further comprising:

21. The method of claim 20, further comprising:

adding the PDN connection rejection reason received from a network to a terminal response message through the ME.

22. An apparatus for providing support for evolved session management, ESM, reason codes in universal terrestrial radio access network, user identity module, USAT, network rejection events, the apparatus comprising:

means for receiving an open channel command from a universal integrated circuit card, UICC, to trigger a packet data protocol, PDP, context attach procedure;

means for receiving, by the mobile equipment ME, a packet data network, PDN, connection rejection message including an ESM reason; and

means for providing the UICC with the ESM cause received by the ME.

23. The apparatus of claim 22, wherein

The USAT network rejection event includes an access point name APN; and

the apparatus further comprises:

means for providing the UICC with a PDN connection rejection cause received by the ME and a corresponding APN.

24. The apparatus of claim 23, further comprising:

means for monitoring all rejections by the UICC; and

25. The apparatus of claim 22, further comprising:

means for providing, by the ME, a reason for receipt with the PDN connection rejection.

26. The apparatus of claim 22, further comprising:

for indicating to the UICC using the terminal response: devices that have a particular problem on the open channel command.

27. The apparatus of claim 26, further comprising:

28. The apparatus of claim 27, further comprising:

means for adding the PDN connection rejection reason received from a network to a terminal response message through the ME.