WO2017019118A1

WO2017019118A1 - Network attach process through a combined general packet radio service (gprs) attach message and a packet data protocol (pdp) context activation procedure

Info

Publication number: WO2017019118A1
Application number: PCT/US2015/065895
Authority: WO
Inventors: Ravikumar Balakrishnan; Rath Vannithamby
Original assignee: Intel Corporation
Priority date: 2015-07-28
Filing date: 2015-12-15
Publication date: 2017-02-02

Abstract

Technology for reducing connection setup time with a network is disclosed. In an example, a mobile station including one or more processors and memory can: encapsulate, within a General Packet Radio Service (GPRS) mobility management (GMM) packet data unit (PDU) attach request message, a Session Management (SM) PDU packet data protocol (PDP) context activation request message and a PDP request indication (PRI) using a primitive from an SM layer to a GMM layer from the mobile station; transmit the GMM PDU attach request message to a Serving GPRS Support Node (SGSN); and receive from the SGSN an SM PDU PDP context activation accept or reject message and a PDP response indication (PRSI) encapsulated within a GMM PDU attach accept or reject response message.

Description

NETWORK ATTACH PROCESS THROUGH A COMBINED

GENERAL PACKET RADIO SERVICE (GPRS) ATTACH MESSAGE

AND A PACKET DATA PROTOCOL (PDP) CONTEXT

ACTIVATION PROCEDURE

BACKGROUND

[0001] Wireless mobile communication technology uses various standards and protocols to transmit data between a node (e.g., a transmission station) and a wireless device (e.g., a mobile device). Some wireless devices communicate using orthogonal frequency - division multiple access (OFDMA) in a downlink (DL) transmission and single carrier frequency division multiple access (SC-FDMA) in an uplink (UL) transmission.

Standards and protocols that use orthogonal frequency-division multiplexing (OFDM) for signal transmission include the third generation partnership project (3 GPP) long term evolution (LTE), the Institute of Electrical and Electronics Engineers (IEEE) 802.16 standard (e.g., 802.16e, 802.16m), which is commonly known to industry groups as WiMAX (Worldwide interoperability for Microwave Access), and the IEEE 802.11 standard, which is commonly known to industry groups as WiFi.

[0002] In Within 3rd Generation Partnership Project (3GPP) radio access network (RAN) Long Term Evolution (LTE) systems, a node can be a combination of Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node Bs (also commonly denoted as evolved Node Bs, enhanced Node Bs, eNBs, or eNBs) and Radio Network Controllers (RNCs), which communicates with the wireless device, known as a user equipment (UE). The downlink (DL) transmission can be a communication from the node (e.g., eNB) to the wireless device (e.g., UE), and the uplink (UL) transmission can be a communication from the wireless device to the node.

[0003] In LTE, data can be transmitted from the eNB to the UE via a physical downlink shared channel (PDSCH). A physical uplink control channel (PUCCH) can be used to acknowledge that data was received. Downlink and uplink channels or transmissions can use time-division duplexing (TDD) or frequency-division duplexing (FDD). BRIEF DESCRIPTION OF THE DRAWINGS

[0004] Features and advantages of the disclosure can be apparent from the detailed description which follows, taken in conjunction with the accompanying drawings, which together illustrate, by way of example, features of the disclosure; and, wherein:

[0005] FIG. 1 illustrates an LTE operation zone within a cell having an evolved node B (eNB) with two devices in accordance with an example;

[0006] FIGS. 2 illustrates a diagram for power consumption and byte transmission for connection setup and data transmission for mobile devices (e.g., IoT devices) following a time period of inactivity in accordance with an example;

[0007] FIG. 3 illustrates a diagram of legacy procedures for setting up packet data protocol (PDP) context and data connection for a user equipment (UE) in a general packet radio service (GPRS) Mobility Management (GMM) idle state in accordance with an example;

[0008] FIG. 4 illustrates a diagram of a modified procedure combing packet data protocol (PDP) context and General Packet Radio Service (GPRS) mobility

management (GMM) packet data unit (PDU) attach request for reducing connection setup time with a network in accordance with an example;

[0009] FIG. 5 illustrates a diagram of communication between a system management layer to a GMM layer of a UE for a modified procedure of combing packet data protocol (PDP) context and General Packet Radio Service (GPRS) mobility management (GMM) packet data unit (PDU) attach request for reducing connection setup time with a network in accordance with an example;

[0010] FIG. 6 illustrates a diagram of communication between a system management (SM) layer to a GMM layer of a Serving GPRS Support Node (SGSN) for a modified procedure of combing packet data protocol (PDP) context and General Packet Radio

Service (GPRS) mobility management (GMM) packet data unit (PDU) attach request for reducing connection setup time with a network in accordance with an example;

[0011] FIG. 7 illustrates a diagram of communication between a GMM layer to a system management layer of a Serving GPRS Support Node (SGSN) for a modified procedure of combing packet data protocol (PDP) context and General Packet Radio Service (GPRS) mobility management (GMM) packet data unit (PDU) attach request for reducing connection setup time with a network in accordance with an example;

[0012] FIG. 8 illustrates an additional diagram of communication between a system management (SM) layer to a GMM layer of a Serving GPRS Support Node (SGSN) for a modified procedure of combing packet data protocol (PDP) context and General Packet Radio Service (GPRS) mobility management (GMM) packet data unit (PDU) attach request for reducing connection setup time with a network in accordance with an example;

[0013] FIG. 9 illustrates a diagram of compares a modified procedure of combing packet data protocol (PDP) context and General Packet Radio Service (GPRS) mobility management (GMM) packet data unit (PDU) attach request for reducing connection setup time with a network as compared to a legacy approach, as described in FIG. 2, in accordance with an example;

[0014] FIG. 10 illustrates a diagram comparing signaling overhead for communication between a GMM layer to a system management layer the modified procedure of combing packet data protocol (PDP) context and General Packet Radio Service (GPRS) mobility management (GMM) packet data unit (PDU) attach request as compared to the legacy procedures for setting up packet data protocol (PDP) context and data connection for a user equipment (UE) in a general packet radio service (GPRS) Mobility

Management (GMM) idle state in accordance with an example;

[0015] FIG. 10 depicts a flow chart of an additional method for reducing a connection setup time with a network by a mobile station in accordance with an example;

[0016] FIG. 11 depicts a flow chart of an additional method for reducing a connection setup time with a network by a Serving GPRS support node (SGSN) in accordance with an example;

[0017] FIG. 12 depicts a flow chart of an additional method for reducing a connection setup time with a network by a Serving GPRS support node (SGSN) in accordance with an example;

[0018] FIG. 13 illustrates a diagram of a wireless device (e.g., UE) in accordance with an example; [0019] FIG. 14 illustrates a diagram of a node (e.g., eNB) and wireless device (e.g., UE) in accordance with an example; and

[0020] FIG. 15 illustrates a diagram of example components of a User Equipment (UE) device in accordance with an example.

[0021] Reference can now be made to the exemplary embodiments illustrated, and specific language can be used herein to describe the same. It can nevertheless be understood that no limitation of the scope of the technology is thereby intended.

DETAILED DESCRIPTION

[0022] Before the present technology is disclosed and described, it is to be understood that this technology is not limited to the particular structures, process actions, or materials disclosed herein, but is extended to equivalents thereof as would be recognized by those ordinarily skilled in the relevant arts. It should also be understood that terminology employed herein is used for the purpose of describing particular examples only and is not intended to be limiting. The same reference numerals in different drawings represent the same element. Numbers provided in flow charts and processes are provided for clarity in illustrating actions and operations and do not necessarily indicate a particular order or sequence.

EXAMPLE EMBODIMENTS

[0023] An initial overview of technology embodiments are provided below and then specific technology embodiments are described in further detail later. This initial summary is intended to aid readers in understanding the technology more quickly but is not intended to identify key features or essential features of the technology nor is it intended to limit the scope of the claimed subject matter.

[0024] In one aspect, the technology described herein applies to 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) systems (e.g., cellular wireless communication systems). In one aspect, within the 3GPP LTE systems, user equipment (UE), also known as mobile terminals and/or wireless terminals, can communicate via a Radio Access Network (RAN) to one or more core networks. The UE can be a mobile station or user equipment units such as mobile telephones also known as "cellular" telephones, and other types of mobile computing devices with wireless capability, e.g., mobile terminals, and thus may be, for example, portable, pocket, hand-held, tablet, computer-included, or car-mounted mobile devices which communicate voice and/or data with radio access network.

[0025] The radio access network can cover a geographical area, which can be divided into cell areas, with each cell area being served by a radio network node referred to as a base station, e.g., a Radio Base Station (RBS), which can be referred to as "eNB", "eNodeB", "NodeB" or "B node". The 3 GPP specifications can define the function for reducing location registration procedures when a mobile station makes reselection between different RANs (Radio Access Networks) provided by different RATs (Radio Access Technologies). Specific examples of RAN include UTRAN (Universal Terrestrial Radio Access Network), GERAN (GSM EDGE Radio Access Network) and E-UTRAN (Evolved Universal Terrestrial Radio Access Network).

[0026] A radio network controller (RNC) in the RAN can control radio resources and user mobility. Resource control includes admission control, congestion control, and channel switching which corresponds to changing the data rate of a connection. The base stations, (e.g., the "eNB", "eNodeB", "NodeB" or "B node") can be connected to the RNC and orchestrate radio communications with mobile radio stations over an air interface. The RNC controls what system information the eNodeB can broadcast and can also be the control plane protocol termination point towards the UE. RNCs can also be connected to nodes in the core network, i.e., Serving GPRS Support Node (SGSN), Gateway GPRS Support Node (GGSN), mobile switching center (MSC), etc. The core network can provide various services to mobile radio users who are connected by the radio access network such as authentication, call routing, charging, service invocation, and access to other networks like the Internet, public switched

telephone network (PSTN), Integrated Services Digital Network (ISDN), etc. The base stations can communicate over the air interface operating on radio frequencies with the UE units within range of the base stations. That is, a base station can be located in each cell to provide the radio coverage. A UE in each cell can receive information and data from the base station and transmit information and data to the base station. Information and data transmitted by the base station to the user equipment can occur on channels of radio carriers known as downlink carriers. Information and data transmitted by the UE to the base station can occur on uplink data channels of radio carriers, which can be referred to as uplink carriers. For example, on an initial operation of turning on the UE in a cell, the UE can be in an "idle mode". Once the UE synchronizes and attaches itself to a base station, the UE can gain a radio resource control (RRC) connection, which can be referred to as being in connected mode. The UE in idle mode does not have a Radio Resource Control (RRC) connection.

[0027] The core network can locate the UE within each cell. That is, the core network can keeps track of the location of the UE in units of location registration area. The location registration area can be called RA (Routing Area) or TA (Tracking Area). Moreover, a paging operation can be performed by the core network with the UE, which can include the process of notifying the UE in idle mode according to the Radio Resource Control (RRC) protocol by the core network, about an incoming data session, such as a downlink (DL) packet transmission.

[0028] In one embodiment, a General Packet Radio Service (GPRS) can be used to develop a GERAN based cellular of Internet of things (CIoT) called extended coverage- GSM (EC-GSM). Unlike LTE networks, GERAN networks can involve separate procedures for registering to a network, such as, for example, using a GPRS attach procedure of GPRS Mobility Management (GMM) layer) and for obtaining a data session using a packet data protocol (PDP) context activation procedure of a session management layer. The GPRS attach procedure and the PDP context activation procedure can be performed by a separate GPRS Mobility Management (GMM) and Session Management (SM), respectively. Thus, the PDP context activation procedure can be performed in an SM layer to activate a PDP context. A GPRS service can be registered in a network through a GPRS attach procedure.

[0029] In legacy systems, the Class C GERAN devices, including EC-GSM based CIoT devices, complete the GPRS attach procedure before initiating the PDP context activation. This results in unnecessary computing overhead, especially, for

transmitting short data packets (on the order of 20 bytes). As long as a mobile device is in GMM standby or READY states (e.g., a GMM protocol layer is in a standby state when a mobile station is not active in a packet transfer), it is not necessary to perform a GPRS attach procedure again to perform a PDP context activation.

However, most networks expect communication with the mobile device every few hours. For example, a value of a mobile reachable timer device (e.g., a periodic Routing Area Updates (RAU) timer T3312) is typically set to a few minutes greater than a default mobile reachable timer (e.g., 54 minutes). Therefore, if there is no communication from the mobile within the default time period, then the mobile device is considered "not reachable" and detached from the network by being sent to a GMM IDLE state. Legacy networks overcome this by performing periodic Routing Area Updates (RAU) when the T3312 expires (default value of 54 minutes).

[0030] However, there are two major issues with this. First, for CIoT devices that have infrequent small data transmissions (e.g., no traffic for several hours or even days), performing the period RAU every 54 minutes becomes inefficient and consumes excessive computing resources. Furthermore, having the mobile devices remain registered may result in a need to increase in network and computing resources particularly with the vast amount and increasing number of mobile devices.

[0031] On the other hand, if the mobile devices, such as CIoT devices, are pushed to the GMM IDLE state, the mobile devices first perform the GPRS Attach procedure, followed by the PDP Context Activation procedure to be able to transmit data.

Performing the GPRS Attach procedure followed by the PDP Context Activation procedure results in a larger signaling load as compared to a data packet size. One example of the size of the signaling load relative to a data packet size of a CIoT device is illustrated in FIG. 2, which depicts a bytes transmitted and power consumption for connection setup and data transmission for mobile devices (e.g., IoT devices) following a long time period of inactivity. It should be noted that a long time period can be defined as a time period equal to or greater than 60 minutes. A short time period can be defined as a time period less than 60 minutes. However, a CIoT device may experience inactivity period of the order of several hours, days or even weeks. The time period for connection setup and data transmission can increase the mobile device power consumption, signaling load and also the end-to-end communication latency, which can cause problems at the network and reduce a battery life of a CIoT device.

[0032] As such, the present technology provides for reducing connection setup time with a network. In an example, an apparatus of a mobile station is disclosed. The apparatus, under control of one or more processors and memory, can be configured to reduce connection setup time with a network. The apparatus can be configured to: encapsulate, within a General Packet Radio Service (GPRS) mobility management (GMM) packet data unit (PDU) attach request message, a Session Management (SM) PDU packet data protocol (PDP) context activation request message and a PDP request indication (PRI) using a primitive from an SM layer to a GMM layer from the mobile station; transmit the GMM PDU attach request message to a Serving GPRS Support Node (SGSN); and receive from the SGSN an SM PDU PDP context activation accept or reject message and a PDP response indication (PRSI)

encapsulated within a GMM PDU attach accept or reject response message.

[0033] In one aspect, the present technology provides for reducing connection setup time with a network. In an example, a Serving GPRS Support Node (SGSN), under control of one or more processors and memory, can be configured to reduce connection setup time with a mobile station (MS). The SGSN can be configured to: receive, from the MS, a Session Management (SM) PDU packet data protocol (PDP) context activation request message and a PDP request indication (PRI) encapsulated with a General Packet Radio Service (GPRS) mobility management (GMM) packet data unit (PDU) attach request message; encapsulate, within a General Packet Radio Service (GPRS) mobility management (GMM) packet data unit (PDU) attach accept or reject response message, a Session Management (SM) PDU packet data protocol

(PDP) context accept or reject response message and a PDP response indication (PRSI) using a primitive from an SM layer to a GMM layer; and transmit the GMM PDU attach accept or reject response message to the MS.

[0034] In one aspect, the present technology provides for reducing connection setup time with a network. In an example, a Serving GPRS Support Node (SGSN), under control of one or more processors and memory, can be configured to reduce connection setup time with a mobile station (MS)., For example, the SGSN can be configured to: receive, from the MS, a Session Management (SM) PDU packet data protocol (PDP) context activation request message and a PDP request indication (PRI) encapsulated with a General Packet Radio Service (GPRS) mobility management (GMM) packet data unit (PDU) attach request message; encapsulate, within a General Packet Radio Service (GPRS) mobility management (GMM) packet data unit (PDU) attach accept or reject response message, a Session Management (SM) PDU packet data protocol (PDP) context accept or reject response message and a PDP response indication (PRSI) using a primitive from an SM layer to a GMM layer; use a default PDP setup timer at the SM layer to wait for the MS to be authenticated, wherein the expiration of a predetermined time set on the default PDP setup timer indicates an authentication operation of the MS failed and the SM PDU PDP context activation request message failed; and transmit the GMM PDU attach accept or reject response message to the MS.

[0035] In one aspect, the present technology relates to reducing the amount of signaling the mobile devices, such as CIoT devices, need to register and establish packet data connection using an optimized attach procedure combining the registration and PDP context setup. It should be noted that the terms mobile stations, CloT devices, IoT devices, and UE can be used interchangeably within this document unless otherwise noted.

[0036] In another aspect, the present technology enables a modified GPRS GMM PDU attach request procedure where the UE can be jointly registered to a GPRS network and can be allocated a default PDP context activation while also retaining a PDP context during the time the UE devices are registered with the network. As such, the UE devices can be allowed to repeatedly move back to a GMM Idle state for conserving battery saving at the UE device. Simultaneously, when the UEs returns from the GMM Idle state in order to transmit data, signaling overhead can be minimized, thereby reducing a load on the base station and core network.

[0037] In another aspect, the present technology enables a modified GPRS GMM PDU attach request procedure where the UE can be jointly registered to a GPRS network and can be allocated a default PDP context activation while also retaining a PDP context during the time the UE devices are registered with the network. As such, the UE devices can be allowed to repeatedly move back to GMM Idle state for conserving battery saving at the UE device. In addition, when the UEs return from the GMM Idle state in order to transmit data, signaling overhead can be minimized with the network.

[0038] In one aspect, the modified GPRS GMM PDU attach request procedure is provided. In one aspect, a Session Management (SM) layer message "Activate PDP context request" can be piggybacked in the "GPRS attach request" message for UEs attempting to attach to the network. This is indicated by using a new field in the GPRS attach request message. Upon the SGNS receiving the "GPRS attach request", the SGSN can acquire the UE device subscription from the HLR and initiate mutual authentication with the UE. The "Activate PDP Context Request" message can be stored in the SGSN until the authentication and ciphering process are completed. Following the UE and SGSN having authenticated each other and ciphering is activated at the logical link control level (LLC) layers of UE and SGSN, the SGSN can send a "Create PDP context activate" to a gateway GPRS support node (GGSN) to initiate a default PDP context setup for the UE with the default QoS configuration. At the end of a successful default PDP context setup, the SGSN and GGSN can have a TEID corresponding to the PDP context. The "Activate PDP context accept" IE can be retumed by the SGSN in the GPRS attach accept message. This can be indicated by a field in the attach accept message.

[0039] The created default PDP context can be active for the UE as long as the UE is registered to a network unless an explicit PDP Context deactivate is issued by the UE, SGSN or the GGSN. Moreover, it is possible to modify the PDP context including the quality of service (QoS) characteristics, Access Point Name (APN), charging attributes using the existing procedures for modifying PDP contexts.

[0040] It should be noted that, for a mobile station, such as Class C GPRS devices, including the Cellular IoT devices and other small infrequent data transmitting devices, performing the GPRS attach message and PDP Context activation separately results in transmission inefficiency. Performing a combined registration and IP address allocation for the UEs can provide several advantages, such as, for example, minimizing the signaling overhead for packet data communication for devices coming from GMM Idle state. Moreover, on the radio access network side, the UEs only perform a random access channel (RACH) procedure ("one-phase" or "two-phase" access) once instead of performing them twice. This involves avoiding the transmission of "packet channel request" repeatedly on the RACH channel until access is obtained and receiving a UL allocation on a packet common control channel (PCCCH) packet access grant channel (PAGCH). Following this, the transmission of UL higher layer data over a packet data traffic channel (PDTCH) and the temporary block flow. This can result in significant savings on signaling efficiency, especially considering the CIoT devices may be coverage constrained that may use mechanisms such as signal repetition for achieving extended coverage.

[0041] Also, a default IP address can be provided for the UE devices as long as the UE devices are registered with the network to assist with avoiding an on-demand creation of PDP Context when packet data transmission is needed for the devices and therefore minimizing the end-to-end latency. The energy consumption associated with registration and connection setup for UE devices coming from a GMM IDLE state can be minimized due to the modified GPRS GMM PDU attach request procedure. In contrast, in legacy networks, the alternative is to increase the value of the Periodic RAU timer to a value greater than a packet inter-arrival time and using extend discontinuous reception (eDRX). However, the UE device will still consume energy during the eDRX modes.

[0042] FIG. 1 illustrates an LTE operation zone within a cell 100 having an evolved node B (eNB) with two devices. FIG. 1 illustrates an eNB 104 that can be associated with an anchor cell, macro cell or primary cell. Also, the cell 100 can include User equipment (UE or UEs) 108, 110 that are in communication with the eNB 104.

[0043] The eNB 104 can be a high transmission power eNB, such as a macro eNB, for coverage and connectivity. The eNB 104 can be responsible for mobility and can also be responsible for radio resource control (RRC) signaling. User equipment (UE or UEs) 108, 110 can be supported by the macro eNB 104.

[0044] As shown in FIG. 1, the UE1 108 may be located relatively close to the eNB 104 whereas the UE2 110 may be positioned close to the cell edge. When the eNB 104 has knowledge about preferred CP lengths for both UEs 108, 110, it can be possible that the eNB 104 decides to employ a shorter CP for the data packet targeted for the UE1 108, and a longer CP for the data packet of the UE2 110.

[0045] FIG. 3 illustrates a diagram of legacy procedures for setting up packet data protocol (PDP) context and data connection for a user equipment (UE) in a general packet radio service (GPRS) Mobility Management (GMM) idle state in accordance with an example. That is, FIG. 3 illustrates a legacy EC-GSM implementation with a mobile station, such as a Class C UE, in a GMM Idle state first having to perform the GPRS attach process and then setup a data session using a PDP Context Setup procedure. The legacy procedure establishes a radio link connection between a mobile station (MS) (e.g., a UE) and a base station subsystem (BSS) using a random access channel (RACH) process and then forwards the GMM layer message to the SGSN. That is, the legacy procedure at action 1) sends from the mobile station (MS) an uplink GMM PDU attach request. A Packet Channel Request on a physical random access channel (PRACH) channel can be sent. It should be noted that the "packet channel request" can be sent repeatedly on the RACH channel until access is obtained and an uplink (UL) allocation is received on a PCCCH packet access grant channel (PAGCH). The BSS sends the MS a packet associated control channel (PAACH) uplink state flag (USF).

[0046] A packed data traffic channel (PDTCH) can be used and a Temporary Block Flow (TBF) is utilized to send a logical layer unit data request (LLC-UNITDATA- REQ) having a GMM PDU in a radio link control and/or medium access control layer RLC/MAC layers. The RLC/MAC can be used to establish a radio connection with the BSS. A Base station system GPRS protocol (BSSGP) uplink unit data (B S S GS -UL-UNITD ATA) signal can be sent from the BSS and the SGSN.

[0047] At action 2, a downlink (DL) GMM PDU identity request can be sent from the SGSN to the BSS and forwarded to the MS. That is, the identification with the MS can be verified and an international mobile subscriber identity (IMSI) can be obtained if not already available. At action 3, an UL GMM PDU identity response can be sent from the MS to the BSS and to the SGSN. The SGSN can communicates with a home location register (HLR) via a gateway GPRS support node (GGSN) to obtain authentication and ciphering information, in action 4, for the MS. The SGSN can perform a mutual authentication with the UE and ciphering established between LLC layers of UE and SGSN. At action 5, a DL GMM PDU attach accept can be sent from the SGSN to the BSS and the MSS. At action 6, an UL GMM PDU attach accept can be sent from the MS to the BSS and to the SGSN from the BSS.

[0048] In action 7, a session management (SM) layer of a UE can initiate an Activate PDP Context Request that triggers a RACH procedure to establish a radio resource (RR) communication. Reception of the SM layer message at the SGSN. The SGSN can create a PDP context request, at action 8, and the SGSN can send a "Create PDP Context Request" message to the GGSN and create a tunnel endpoint identification (TEID) toward the GGSN for the MS. In action 9, the GGSN can add an entry to a PDP context table, assigning an IP address for the UE and issuing a "Create PDP Context Response" message back to the SGSN if the PDP Context is accepted, in action 10. The SGSN, in action 11, can send an "Activate PDP Context Accept" to the MS indicating the parameters including the NSAPI, TI and so on corresponding to the PDP Context that has been setup.

[0049] However, the actions and processes of FIG. 3 may need significant energy consumption associated with registration and connection setup for UE devices coming from GMM IDLE state. Thus, in one aspect, the present technology can significantly reduce the energy consumption for mobile stations, such as Class C GPRS UEs, by piggybacking a PDP Context activation request message in the GPRS attach request message when the UE attempts to register to the network for the first time, as depicted in FIG. 4.

[0050] It should be noted the GPRS UE's can be 1) Class A: capable of GPRS and circuit switched services (voice) simultaneously; 2) Class B: can operate on only GPRS services or voice service at a time. However class B GPRS UE's are capable of listening to incoming calls of both GPRS and voice; and/or 3) Class C: only capable of GPRS or circuit switched services. The terminal is either capable of only voice or GPRS or it can only listen to one of these services when it is on.

[0051] As described herein, the present technology procedures can be restricted to GPRS devices (e.g., GPRS-Only Devices) and not applicable to circuit switch enable devices, since IoT devices typically do not need circuit-switched voice services.

[0052] FIG. 4 illustrates a diagram of a modified procedure combing packet data protocol (PDP) context and General Packet Radio Service (GPRS) mobility management (GMM) packet data unit (PDU) attach request for reducing connection setup time with a network in accordance with an example. In one aspects, the present technology relates to reducing the amount of signaling that mobile devices, such as IoT devices, use to register and establish packet data connection using an optimized attach procedure combining the registration and PDP context setup.

[0053] At action 1 in FIG. 4, a Session Management (SM) PDU packet data protocol (PDP) context activation request message and a PDP request indication (PRI) can be encapsulated, within a General Packet Radio Service (GPRS) mobility management (GMM) packet data unit (PDU) attach request message (e.g., an uplink (UL) GMM PDU attach request message), using a primitive from an SM layer to a GMM layer from the mobile station.

[0054] For example, initially, the SM layer of the UE can send an SM PDU PDP Context activation request to the GMM layer of the UE indicating the creation of a default PDP Context for the UE. If the GMM layer of the UE has not previously registered with the network, the GMM layer of the UE can create an attach request message (e.g., GMM PDU attach request message) in a GMM PDU consisting of parameters needed by the SGSN. The GMM layer of the UE can encapsulate the SM layer PDP Context activation request message (consisting of a network service access point identifier (NS API), a transaction identifier (TI), a PDP Type, a PDP Address, an Access Point Name (APN), and a quality of service (QoS) requested= Default) within the GMM PDU and can send an old temporary logic link identifier (TLLI) (e.g., an existing or old TLLI) and a "ciphering off indication in a logical layer unit data request (LL-UNITDATA-REQ) primitive. The presence of the PDP Context Request can be indicated using a new field "PDP Request Indication (PRI)".

[0055] The LLC layer can send a GPRS radio resource data request (GRR-DATA- REQ) message to radio link control and/or medium access control layer RLC/MAC layers. The RLC/MAC may need to establish a radio connection with the BSS. As such, the MAC layer of the UE can send a Packet Channel Request on a physical random access channel (PRACH) channel and obtain an uplink (UL) allocation of a Temporary Block Flow (TBF) for the UE on a packet common control channel (PCCCH) channel. After obtaining the uplink assignment, the UE can utilize the allocated TBF to send the LL-UNITDATA-REQ containing the GMM and SM PDUs to the BSS. The BSS can forward the LLC layer data to the SGSN using a BSS GPRS uplink (UL) data unit (BSSGP-UL-U IT DATA).

[0056] The SGSN can receive the GMM PDU attach request message. At action 2, upon receiving the GMM PDU attach request message, the SGSN can read the PRI field to determine the presence of the SM layer message. The GMM layer can pass the Activate PDP Context Request message to the SM layer. That is, the GMM layer of the SGSN can identify and forward the SM PDU to the SM layer of the SGSN based on the PRI even if the LLC payload carries the existing TLLI and "ciphering off rather than a new TLLI and "ciphering on" indication.

[0057] At action 3, a new timer (e.g., a "Default PDP Setup Timer") at the SM layer of the SGSN is set to wait for the authentication procedure to be completed. That is, the default PDP setup timer at the SM layer can be configured to wait for a mobile station to be authenticated. An expiration of the timer can indicate that the authentication was unsuccessful and the attach process failed. In this case, an Attach Reject message will be issued. That is, the expiration of the predetermined time set on the default PDP setup timer can indicate an authentication operation of a mobile station failed and the SM PDU PDP context activation request message failed. A GMM attach reject response message can be initiated at the SGSN upon an expiration of a predetermined time set on the default PDP setup timer. Upon successful completion of authentication of the mobile station, the timer value can be reset. That is, the default PDP setup timer can be reset upon one of authentication of the mobile station or upon the expiration of a predetermined time.

[0058] At action 4, a downlink (DL) GMM PDU identity request can be sent from the SGSN to the mobile station. At action 5, an UL GMM PDU identity response message can be sent from the mobile station back to the SGSN. At action 6, an authentication operation and ciphering operation can be performed between the mobile station and the SGSN.

[0059] After the authentication operation and ciphering operation is completed, the SGSN can validate the SM PDU PDP context activation request message (e.g., an activate PDP context request) using desired parameters. Functions within the SGSN can handle SM PDU PDP context activation request message even if the GMM PDU attach request message is not complete and only includes an existing TLLI in legacy networks for the mobile station. That is, in legacy systems, if the UE is not registered apriori through a GMM PDU attach request Procedure, the SGSN will not be able to setup a PDP context and a data session for the device. However, the present technology functionality will allow processing the PDP Context Request even if the Attach procedure has yet to be completed.

[0060] A new TLLI (a most recent generated TLLI) can be assigned to a UE if it is attached to the network through a GPRS attach procedure and a P-TMSI is allocated to the device. Next, the PDP Context Request from UE can be transported using the new TLLI to the SGSN. However, we are combining these procedures, so the "new TLLI" is still not available in the initial message. So the "old TLLI" will be used. The SGSN functionality is capable of processing the message even if an "old TLLI" (e.g., previously generated) is used to transport the combined initial message.

[0061] The SGSN can create a TEID for the requested PDP context toward the GGSN. The SGSN can restrict the QoS attributes according to the subscribed QoS profile. Further, a "new TLLI" for UE can be generated and a mapping between the NSAPI and TLLI is maintained.

[0062] At action 7, the SGSN can issue a create PDP context request message to a gateway GPRS support node (GGSN). At action 8, the SGSN can send the create PDP context request message to the GGSN. That is, the SGSN can send to the GGSN the SM PDU create PDP context request message when an authentication operation of the MS is successful. The GGSN can utilize a selection mode to determine if the PPD context can be accepted. In action 9, the GGSN can add an entry to a PDP context table and assign an Internet protocol (IP) address for the mobile station. A downlink TEID can also be created.

[0063] In action 10, the GGSN sends a SM PDU create PDP context response message. In one aspect, the mobile station only requests to activate the PDP context with the subscribed profile and therefore, the GGSN can accept the PDP context based on the QoS attributes, which can be indicated in the SM PDU create PDP context create message sent from the GGSN to the SGSN.

[0064] The SGSN can construct both the Attach Accept message at the GMM layer as well as the Activate PDP Context Accept at the SM layer. The SM layer message can be encapsulated within the GMM Attach Accept message and sent to the UE. In addition, a PDP Response Indicator (PRSI) is included in the Attach Accept message to indicate the presence of PDP Context Accept message. The SGSN still uses the "old TLLI" in the Attach Accept.

[0065] In action 11, the SGSN can send a primitive from the SM layer to the GMM to provide an indication to wait for the SM PDU create PDP context response message to be received from the GGSN before sending the GMM PDU attach accept or reject response message.

[0066] In action 12, the SGSN can transmit to the MS a GMM PDU attach accept response message. The GMM PDU attach accept response message can include new fields; such as an SM PDU PDP context activation accept field and a PDP response indication (PRSI) field. In one aspect, the GMM PDU attach accept response message can indicate the GMM PDU attach request message has been accepted, however a PDP context remains unactivated by encapsulating a SM PDU PDP context activation reject message in the GMM PDU attach accept response message, wherein the MS sends the SM PDU PDP context activation request message to initiate a data session following the GMM PDU attach accept response message. That is, the PDP context is not activated by encapsulating the SM PDU PDP context activation reject message in the GMM attach accept. In this case, a mobile station may send a PDP context activation request in the future to initiate a data session.

[0067] Upon receiving the GMM PDU attach accept response, the GMM layer of the mobile station can read the PRSI field in the GMM PDU attach accept response and can forward the GMM PDU attach accept response to the SM layer of the mobile station. In action 13, the mobile station can generate and send an UL GMM PDU attach complete response to the SGSN. That is, the UL GMM PDU attach complete response can be generated by the GMM layer of the mobile station where a "new TLLI" is indicated on the uplink for the first time and sent to the SGSN.

[0068] As illustrated in table 1 and table 2, a signaling evaluation computation analysis illustrates the benefits of the present technology. For example, consider a mobile station initially in GMM IDLE state needing uplink data transmission while utilizing a traffic type mobile autonomous reporting where the transmission efficiency is only evaluated during one data transmission procedure, but a coverage condition is not reflected in the computation. Rather, the coverage condition can be reflected in a modulation scheme and channel code rate (MCS) selection on PHY. Consequently, the result is irrelevant with coverage condition.

[0069] It should be noted, as describe below the terms can be defined as follows. A "D application" can indicate the amount of application layer data to transmit. H CN is the overhead from protocols below the application layer and above equivalent of subnetwork dependent convergence protocol (SNDCP) layer. H access is the header overhead for user plane data due to radio access network, which can be dependent on the architecture and radio access technology. S_radio is the amount of signalling information exchanged before transfer of the user plane data. H signalling is the header overhead for signaling information. H_access + S_radio + H_signalling represents the overhead related to a specific core network architecture. In a zero overhead architecture, H access, S radio and H signalling can all be equal to "zero", can be used as a baseline for comparison.

[0070] TABLE 1- Existing Legacy for power consumption and byte transmission for connection setup and data transmission for mobile devices (e.g., IoT devices) following a time period of inactivity (e.g., equal to or greater than 60 minutes "min").

3. Authentication and 34

Ciphering

Authentication and 0 0 0 19 13 32

Ciphering

Packet Acknowledge 0 0 0 1 1 2

(DL ACK)

4. GPRS Attach Accept 49

Attach Accept 0 0 0 34 13 47

Packet Acknowledge 0 0 0 1 1 2

(UL ACK)

5. GPRS 8

Attach

Attach Complete 0 0 0 2 4 6

Packet Acknowledge (DL 0 0 0 1 1 2

ACK)

TABLE 1- Continued

Connection Release 0 0 0 1 1 2

[0071] The total number of bytes for a legacy connection setup is 322. That is, the total number of bytes for connection setup connection setup is 61+ 47 + 44 + 59 + 18 + 57 + 86 = 322. The total number of bytes for Data Transmission is equal tol93 (see 8. Uplink Data Transmission in Table 1).

[0072] TABLE 2- Present technology for reducing power consumption and byte transmission for connection setup and data transmission for mobile devices (e.g., IoT devices) following a time period of inactivity(e.g., equal to or greater than 60 minutes "min").

6. Uplink Data 193 Transmissio

Channel Request 0 0 0 4 0 4

Immediate Assignment 0 0 0 6 0 6

User Data Transmission 20 65 12 4 1 102

(User Data)

Downlink Data 0 65 12 0 0 77

Transmission (Application

Uplink Data Transmission 0 0 0 1 1 2

(DL ACK)

Connection Release 0 0 0 1 1 2

[0073] The total number of bytes for connection setup in this example is 280. That is, the total number of bytes for connection setup connection setup is 93+47+44+118+18 = 280. The total number of bytes for Data Transmission is equal tol93 (see 6. Uplink Data Transmission in Table 2).

[0074] FIG. 5 illustrates a diagram 500 of communication between a system

management layer to a GMM layer of a UE for a modified procedure of combing packet data protocol (PDP) context and General Packet Radio Service (GPRS) mobility management (GMM) packet data unit (PDU) attach request for reducing connection setup time with a network in accordance with an example. At action 510, an SM layer of UE can send to the GMM layer a unit data request (UNITDATA-REQ) to initiate an GMM PDU attach request message and an SM PDU PDP context activation request message. At action 520, the GMM layer can insert a PRI and a SM PDU PDP context activation request message request in a logical layer unit data request (LL-UNITDATA- REQ). At action 530, the GMM layer can send the logical layer unit data request to the LLC layer.

[0075] FIG. 6 illustrates a diagram 600 of an example communication between a system management (SM) layer to a GMM layer of a Serving GPRS Support Node (SGSN) for a modified procedure of combing packet data protocol (PDP) context and General Packet Radio Service (GPRS) mobility management (GMM) packet data unit (PDU) attach request for reducing connection setup time with a network in accordance with an example. At action 610, an SM layer of SGSN can send to the GMM layer of SGSN a unit data request (UNITDATA-REQ) to having an SM PDU PDP context activation request message and a PRI. At action 620, the GMM layer of the SGSNS can process a PDP PRI in the unit data request (UNITDATA-REQ). At action 630, the GMM layer can send the logical layer unit data request having the GMM) packet data unit (PDU) attach request, the PDP PRI, and the SM PDU PDP context activation request message to the LLC layer.

[0076] FIG. 7 illustrates a diagram 700 of an example communication between a GMM layer to a system management layer of a Serving GPRS Support Node (SGSN) for a modified procedure of combing packet data protocol (PDP) context and General Packet Radio Service (GPRS) mobility management (GMM) packet data unit (PDU) attach request for reducing connection setup time with a network in accordance with an example. At action 710, an SM layer of SGSN can send to the GMM layer of SGSN a unit data indication (UNITDATA-IND) having an SM PDU PDP context activation accept message. At action 720, the GMM layer of the SGSNS can insert a PDP response indication (PRSI) and the SM PDU PDP context activation accept message in a logical layer unit data request (LLC-UNITDATA-REQ). At action 730, the GMM layer can send to the LLC layer the logical layer unit data request (LLC-UNITDATA-REQ) having a GMM PDU attach accept message, a PDP PRI, and the SM PDU PDP context activation accept message.

[0077] FIG. 8 illustrates an additional diagram 800 of communication between a system management (SM) layer to a GMM layer of a Serving GPRS Support Node (SGSN) for a modified procedure of combing packet data protocol (PDP) context and General Packet Radio Service (GPRS) mobility management (GMM) packet data unit (PDU) attach request for reducing connection setup time with a network in accordance with an example. At action 810, an SM layer of the UE can send to the GMM layer of SGSN a unit data indication (UNITDATA-IND) having an SM PDU PDP context activation accept message. At action 820, the GMM layer of the UE can process a PDP response indication (PRSI). At action 830, the GMM layer of the UE can send to the LLC layer a logical layer unit data request (LLC-UNITDATA-REQ) having a GMM PDU attach accept message, a PDP PRI, and the SM PDU PDP context activation accept message.

[0078] FIG. 9 illustrates a diagram of a graph 900 that compares a modified procedure of combing packet data protocol (PDP) context and General Packet Radio Service (GPRS) mobility management (GMM) packet data unit (PDU) attach request for reducing connection setup time with a network as compared to a legacy approach, as described in FIG. 2, in accordance with an example. In one aspect, FIG. 9 illustrates a graph for a total number of bytes transmitted for connection setup and data transmission. The graph depicts an "existing approach" (as described in FIG. 3) and the "proposed approach" for reducing connection setup time (as described in FIGS. 4-8).

[0079] As illustrated, the legacy approach (e.g., the existing approach of FIG. 3) involves transmission of more bytes for connection set up as compared to the "proposed approach" for reduce connection setup time (as described in FIGS. 4-8). For example, the "Connection Setup" related to overheads for the proposed approach" for reducing connection setup time (as described in FIGS. 4-8) is reduces by almost 15%. Moreover, the legacy approach (e.g., the existing approach of FIG. 3) involves transmission of more bytes for connection set up as compared to the "proposed approach" for reducing data transmission (as described in FIGS. 4-8).

[0080] FIG. 10 illustrates a diagram comparing signaling overhead for communication between a GMM layer to a system management layer the modified procedure of combing packet data protocol (PDP) context and General Packet Radio Service (GPRS) mobility management (GMM) packet data unit (PDU) attach request as compared to the legacy procedures for setting up packet data protocol (PDP) context and data connection for a user equipment (UE) in a general packet radio service (GPRS) Mobility

Management (GMM) idle state in accordance with an example. That is, FIG. 10 depicts a flow chart of a method for reducing a connection setup time with a network by a mobile station in accordance with an example. It should be noted that the descriptions and embodiments of FIG. 10 can be used, applied to, provide additional functionality, and/or used in conjunction with the embodiments described herein.

[0081] For example, the functionality of the UE can be implemented as the method 1000 or the functionality can be executed as instructions on a machine, where the instructions are included on one computer readable medium or one non-transitory machine readable storage medium, which can include one or more processors and memory. In one aspect, the one or more processors and memory can be a storage medium (e.g., a non-volatile storage medium). The one or more processors and memory can be configured to encapsulate, within a General Packet Radio Service (GPRS) mobility management (GMM) packet data unit (PDU) attach request message, a Session Management (SM) PDU packet data protocol (PDP) context activation request message and a PDP request indication (PRI) using a primitive from an SM layer to a GMM layer from the mobile station, as in block 1010. The one or more processors can be configured to transmit the GMM PDU attach request message to a Serving GPRS Support Node (SGSN), as in block 1020. The one or more processors can be configured to receive from the SGSN an SM PDU PDP context activation accept or reject message and a PDP response indication (PRSI) encapsulated within a GMM PDU attach accept or reject response message, as in block 1030.

[0082] It should be noted that each of the following may be included in FIG. 10. In other words, each of the following may be included in each of the actions and/or in conjunction with one or more of the actions described in FIG.10.

[0083] For example, in one aspect, the SM PDU PDP context activation request message can include one or more of a network service access point identifier (NSAPI), transaction identifier (TI), PDP Type, PDP Address, Access Point Name (APN), and quality of service (QoS) requested.

[0084] The one or more processors can be configured to send to the logical link control layer an existing temporary logic link identifier (TLLI) and a ciphering off indication in a logical layer unit data request (LL-UNITDATA-REQ) primitive. The one or more processors can be configured to create the GMM PDU attach request message in the GMM PDU for registering the GMM layer with a network. The one or more processors can be configured to indicate using a PRI field within the GMM PDU attach request message that the SM PDU PDP context activation request message is encapsulated. The one or more processors can be configured to send from the SM layer to the GMM layer the SM PDU PDP context activation request indicating a creating of a default PDP context for the UE. The one or more processors can be configured to identify and read the PRSI in encapsulated within a GMM PDU attach accept or reject response message. The one or more processors can be configured to forward the SM PDU PDP context activation accept or reject response message from the GMM layer to the SM layer.

[0085] FIG. 11 depicts a flow chart of an additional method for reducing a connection setup time with a network by a Serving GPRS support node (SGSN) in accordance with an example. It should be noted that the descriptions and embodiments of FIG. 11 can be used, applied to, provide additional functionality, and/or used in conjunction with the embodiments described herein. For example, the functionality of the UE can be implemented as the method 1100 or the functionality can be executed as instructions on a machine, where the instructions are included on one computer readable medium or one non-transitory machine readable storage medium. One or more processors can be configured to receive, from the MS, a Session Management (SM) PDU packet data protocol (PDP) context activation request message and a PDP request indication (PRI) encapsulated with a General Packet Radio Service (GPRS) mobility management

(GMM) packet data unit (PDU) attach request message, as in block 1110. The one or more processors can be configured to encapsulate, within a General Packet Radio Service (GPRS) mobility management (GMM) packet data unit (PDU) attach accept or reject response message, a Session Management (SM) PDU packet data protocol (PDP) context accept or reject response message and a PDP response indication (PRSI) using a primitive from an SM layer to a GMM layer, as in block 1120. The one or more processors can be configured to transmit the GMM PDU attach accept or reject response message to the MS, as in block 1130.

[0086] FIG. 12 depicts a flow chart of an additional method for reducing a connection setup time with a network by a Serving GPRS support node (SGSN) in accordance with an example. It should be noted that the descriptions and embodiments of FIG. 12 can be used, applied to, provide additional functionality, and/or used in conjunction with the embodiments described herein. For example, the functionality of the UE can be implemented as the method 1200 or the functionality can be executed as instructions on a machine, where the instructions are included on one computer readable medium or one non-transitory machine readable storage medium. One or more processors can be configured to receive, from the MS, a Session Management (SM) PDU packet data protocol (PDP) context activation request message and a PDP request indication (PRI) encapsulated with a General Packet Radio Service (GPRS) mobility management (GMM) packet data unit (PDU) attach request message, as in block 1210. The one or more processors can be configured to encapsulate, within a General Packet Radio Service (GPRS) mobility management (GMM) packet data unit (PDU) attach accept or reject response message, a Session Management (SM) PDU packet data protocol (PDP) context accept or reject response message and a PDP response indication (PRSI) using a primitive from an SM layer to a GMM layer, as in block 1220. The one or more processors can be configured to use a default PDP setup timer at the SM layer to wait for the MS to be authenticated, wherein the expiration of a predetermined time set on the default PDP setup timer indicates an authentication operation of the MS failed and the SM PDU PDP context activation request message failed, as in block 1230. The one or more processors can be configured to transmit the GMM PDU attach accept or reject response message to the MS, as in block 1240.

[0087] It should be noted that each of the following can be included in FIG. 11 and/or FIG. 12. In other words, each of the following may be included in each of the actions and/or in conjunction with one or more of the actions described in FIG.11.

[0088] For example, in one aspect, the one or more processors can be configured to read and identify the PRI within a PRI field of the GMM PDU attach request message. The one or more processors can be configured to forward the SM PDU PDP context activation request message from a GMM layer to the SM layer. The one or more processors can be configured to forward the SM PDU PDP context activation request message from a GMM layer to the SM layer even if a logical link control level (LLC) includes an existing temporary logic link identifier (TLLC) and a ciphering off indication based on the PRI. The one or more processors can be configured to perform an authentication operation for the MS when receiving the GMM PDU attach request message from the MS. The one or more processors can be configured to use a default PDP setup timer at the SM layer to wait for the MS to be authenticated. The one or more processors can be configured to initiate a GMM attach reject response message upon an expiration of a predetermined time set on the default PDP setup timer. The expiration of the predetermined time set on the default PDP setup timer can indicate an authentication operation of the MS failed and the SM PDU PDP context activation request message failed. The one or more processors can be configured to reset the default PDP setup timer upon one of authentication of the UE or an expiration of a predetermined time. The one or more processors can be configured to transmit to the MS a GMM attach reject response message indicating the authentication operation of the MS failed and the SM PDU PDP context activation request message failed. The one or more processors can be configured to validate the SM PDU PDP context activation request message upon receiving the GMM PDU attach request message. The one or more processors can be configured to send to a gateway GPRS support node (GGSN) a SM PDU create PDP context request message when an authentication operation of the MS is successful. The one or more processors can be configured to receive from a gateway GPRS support node (GGSN) a SM PDU create PDP context response message. The one or more processors can be configured to receive from a gateway GPRS support node (GGSN) a SM PDU create PDP context response message.

[0089] In yet another aspect, the one or more processors can be configured to send a primitive from the SM layer to the GMM to provide an indication to wait for the SM PDU create PDP context response message before sending the GMM PDU attach accept or reject response message. The one or more processors can be configured to create the GMM PDU attach accept response message at the GMM layer and a SM PDU

PDP context accept response at the SM layer. The one or more processors can be configured to transmit to the MS an GMM PDU attach accept response message indicating the GMM PDU attach request message has been accepted, wherein a PDP context remains unactivated by encapsulating a SM PDU PDP context activation reject message in the GMM PDU attach accept response message, wherein the SM PDU PDP context activation request message is sent to initiate a data session following the GMM PDU attach accept response message.

[0090] FIG. 13 illustrates a diagram of a wireless device (e.g., UE) in accordance with an example. FIG. 13 provides an example illustration of the wireless device, such as a user equipment (UE), a mobile station (MS), a mobile wireless device, a mobile communication device, a tablet, a handset, or other type of wireless device. In one aspect, the wireless device can include at least one of an antenna, a touch sensitive display screen, a speaker, a microphone, a graphics processor, an application processor, internal memory, a non-volatile memory port, and combinations thereof.

[0091] The wireless device can include one or more antennas configured to communicate with a node or transmission station, such as a base station (BS), an evolved Node B (eNB), a baseband unit (BBU), a remote radio head (RRH), a remote radio equipment (R E), a relay station (RS), a radio equipment (RE), a remote radio unit (RRU), a central processing module (CPM), or other type of wireless wide area network (WWAN) access point. The wireless device can be configured to communicate using at least one wireless communication standard including 3 GPP LTE, WiMAX, High Speed Packet Access (HSPA), Bluetooth, and WiFi. The wireless device can communicate using separate antennas for each wireless communication standard or shared antennas for multiple wireless communication standards. The wireless device can communicate in a wireless local area network (WLAN), a wireless personal area network (WPAN), and/or a WWAN. The mobile device can include a storage medium. In one aspect, the storage medium can be associated with and/or communication with the application processor, the graphics processor, the display, the non-volitle memory port, and/or internal memory. In one aspect, the application processor and graphics processor are storage mediums.

[0092] FIG. 14 illustrates a diagram of a node 1410 (e.g., eNB and/or a Serving GPRS Support Node) and wireless device (e.g., UE) in accordance with an example. The node can include a base station (BS), a Node B (NB), an evolved Node B (eNB), a baseband unit (BBU), a remote radio head (RRH), a remote radio equipment (RRE), a remote radio unit (RRU), or a central processing module (CPM). In one aspect, the node can be a Serving GPRS Support Node. The node 1410 can include a node device 1412. The node device 1412 or the node 1410 can be configured to communicate with the wireless device 1420. The node device 1412 can be configured to implement the technology described. The node device 1412 can include a processing module 1414 and a transceiver module 1416. In one aspect, the node device 1412 can include the transceiver module 1416 and the processing module 1414 forming a circuitry 1418 for the node 1410. In one aspect, the transceiver module 1416 and the processing module 1414 can form a circuitry of the node device 1412. The wireless device 1420 can include a transceiver module 1424 and a processing module 1422. The wireless device 1420 can be configured to implement the technology described. The node 1410 and the wireless devices 1420 can also include one or more storage mediums, such as the transceiver module 1416, 1424 and/or the processing module 1414, 1422.

[0093] As used herein, the term "circuitry" can refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality. In some aspects, the circuitry can be implemented in, or functions associated with the circuitry can be implemented by, one or more software or firmware modules. In some aspects, circuitry can include logic, at least partially operable in hardware.

[0094] Figure 15 illustrates, for one aspect, example components of a User Equipment (UE) device 1500. In some aspects, the UE device 1500 can include application circuitry 1502, baseband circuitry 1504, Radio Frequency (RF) circuitry 1506, front-end module (FEM) circuitry 1508 and one or more antennas 1510, coupled together at least as shown.

[0095] The application circuitry 1502 can include one or more application processors. For example, the application circuitry 1502 can include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor(s) may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.). The processors may be coupled with and/or may include a storage medium 1512, and may be configured to execute instructions stored in the storage medium 1512 to enable various applications and/or operating systems to run on the system.

[0096] The baseband circuitry 1504 can include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry 1504 can include one or more baseband processors and/or control logic to process baseband signals received from a receive signal path of the RF circuitry 1506 and to generate baseband signals for a transmit signal path of the RF circuitry 1506. Baseband processing circuitry 1504 can interface with the application circuitry 1502 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 1506. For example, in some aspects, the baseband circuitry 1504 can include a second generation (2G) baseband processor 1504a, third generation (3G) baseband processor 1504b, fourth generation (4G) baseband processor 1504c, and/or other baseband processor(s) 1504d for other existing generations, generations in development or to be developed in the future (e.g., fifth generation (5G), 6G, etc.). The baseband circuitry 1504 (e.g., one or more of baseband processors 1504a-d) can handle various radio control functions that enable communication with one or more radio networks via the RF circuitry 1506. The radio control functions can include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc. In some aspects, modulation/demodulation circuitry of the baseband circuitry 1504 can include Fast-Fourier Transform (FFT), precoding, and/or constellation mapping/demapping functionality. In some aspects, encoding/decoding circuitry of the baseband circuitry 1504 can include convolution, tail-biting convolution, turbo, Viterbi, and/or Low Density Parity Check (LDPC) encoder/decoder functionality. Aspects of

modulation/demodulation and encoder/decoder functionality are not limited to these examples and can include other suitable functionality in other aspects.

[0097] In some aspects, the baseband circuitry 1504 can include elements of a protocol stack such as, for example, elements of an evolved universal terrestrial radio access network (EUTRAN) protocol including, for example, physical (PHY), media access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), and/or radio resource control (RRC) elements. A central processing unit (CPU) 1504e of the baseband circuitry 1504 can be configured to run elements of the protocol stack for signaling of the PHY, MAC, RLC, PDCP and/or RRC layers. In some aspects, the baseband circuitry can include one or more audio digital signal processor(s) (DSP) 1504f. The audio DSP(s) 1504f can be include elements for

compression/decompression and echo cancellation and can include other suitable processing elements in other aspects. Components of the baseband circuitry can be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some aspects. In some aspects, some or all of the constituent components of the baseband circuitry 1504 and the application circuitry 1502 can be implemented together such as, for example, on a system on a chip (SOC).

[0098] In some aspects, the baseband circuitry 1504 can provide for

communication compatible with one or more radio technologies. For example, in some aspects, the baseband circuitry 1504 can support communication with an evolved universal terrestrial radio access network (EUTRAN) and/or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN). Aspects in which the baseband circuitry 1504 is configured to support radio communications of more than one wireless protocol can be referred to as multi-mode baseband circuitry.

[0099] RF circuitry 1506 can enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various aspects, the RF circuitry 1506 can include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. RF circuitry 1506 can include a receive signal path which can include circuitry to down-convert RF signals received from the FEM circuitry 1508 and provide baseband signals to the baseband circuitry 1504. RF circuitry 1506 can also include a transmit signal path which can include circuitry to up- convert baseband signals provided by the baseband circuitry 1504 and provide RF output signals to the FEM circuitry 1508 for transmission.

[00100] In some aspects, the RF circuitry 1506 can include a receive signal path and a transmit signal path. The receive signal path of the RF circuitry 1506 can include mixer circuitry 1506a, amplifier circuitry 1506b and filter circuitry 1506c. The transmit signal path of the RF circuitry 1506 can include filter circuitry 1506c and mixer circuitry

1506a. RF circuitry 1506 can also include synthesizer circuitry 1506d for synthesizing a frequency for use by the mixer circuitry 1506a of the receive signal path and the transmit signal path. In some aspects, the mixer circuitry 1506a of the receive signal path can be configured to down-convert RF signals received from the FEM circuitry 1508 based on the synthesized frequency provided by synthesizer circuitry 1506d. The amplifier circuitry 1506b can be configured to amplify the down-converted signals and the filter circuitry 1506c can be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals. Output baseband signals can be provided to the baseband circuitry 1504 for further processing. In some aspects, the output baseband signals can be zero-frequency baseband signals, although this is not a mandate. In some aspects, mixer circuitry 1506a of the receive signal path can comprise passive mixers, although the scope of the aspects is not limited in this respect.

[00101] In some aspects, the mixer circuitry 1506a of the transmit signal path can be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 1506d to generate RF output signals for the FEM circuitry 1508. The baseband signals can be provided by the baseband circuitry 1504 and can be filtered by filter circuitry 1506c. The filter circuitry 1506c can include a low- pass filter (LPF), although the scope of the aspects is not limited in this respect.

[00102] In some aspects, the mixer circuitry 1506a of the receive signal path and the mixer circuitry 1506a of the transmit signal path can include two or more mixers and can be arranged for quadrature downconversion and/or upconversion respectively. In some aspects, the mixer circuitry 1506a of the receive signal path and the mixer circuitry 1506a of the transmit signal path can include two or more mixers and can be arranged for image rejection (e.g., Hartley image rejection). In some aspects, the mixer circuitry 1506a of the receive signal path and the mixer circuitry 1506a can be arranged for direct downconversion and/or direct upconversion, respectively. In some aspects, the mixer circuitry 1506a of the receive signal path and the mixer circuitry 1506a of the transmit signal path can be configured for super-heterodyne operation.

[00103] In some aspects, the output baseband signals and the input baseband signals can be analog baseband signals, although the scope of the aspects is not limited in this respect. In some alternate aspects, the output baseband signals and the input baseband signals can be digital baseband signals. In these alternate aspects, the RF circuitry 1506 can include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 1504 can include a digital baseband interface to communicate with the RF circuitry 1506.

[00104] In some dual-mode embodiments, a separate radio IC circuitry can be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.

[00105] In some embodiments, the synthesizer circuitry 1506d can be a fractional-N synthesizer or a fractional N/N+1 synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers can be suitable. For example, synthesizer circuitry 1506d can be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.

[00106] The synthesizer circuitry 1506d can be configured to synthesize an output frequency for use by the mixer circuitry 1506a of the RF circuitry 1506 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 1506d can be a fractional N/N+1 synthesizer.

[00107] In some embodiments, frequency input can be provided by a voltage controlled oscillator (VCO), although that is not a mandate. Divider control input can be provided by either the baseband circuitry 1504 or the applications processor 1502 depending on the desired output frequency. In some embodiments, a divider control input (e.g., N) can be determined from a look-up table based on a channel indicated by the applications processor 1502.

[00108] Synthesizer circuitry 1506d of the RF circuitry 1506 can include a divider, a delay -locked loop (DLL), a multiplexer and a phase accumulator. In some embodiments, the divider can be a dual modulus divider (DMD) and the phase accumulator can be a digital phase accumulator (DPA). In some embodiments, the DMD can be configured to divide the input signal by either N or N+l (e.g., based on a carry out) to provide a fractional division ratio. In some example embodiments, the DLL can include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip- flop. In these embodiments, the delay elements can be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[00109] In some embodiments, synthesizer circuitry 1506d can be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency can be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other. In some embodiments, the output frequency can be a LO frequency (fLO). In some embodiments, the RF circuitry 1506 can include an IQ/polar converter.

[00110] FEM circuitry 1508 can include a receive signal path which can include circuitry configured to operate on RF signals received from one or more antennas 1510, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 1506 for further processing. FEM circuitry 1508 can also include a transmit signal path which can include circuitry configured to amplify signals for transmission provided by the RF circuitry 1506 for transmission by one or more of the one or more antennas 1510.

[00111] In some embodiments, the FEM circuitry 1508 can include a TX/RX switch to switch between transmit mode and receive mode operation. The FEM circuitry can include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry can include a low-noise amplifier (LNA) to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 1506). The transmit signal path of the FEM circuitry 1508 can include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 1506), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 1510.

[00112] In some embodiments, the UE device 1500 can include additional elements such as, for example, memory /storage, display, camera, sensor, and/or input/output (I/O) interface.

Examples

[00113] The following examples pertain to specific invention embodiments and point out specific features, elements, or steps that can be used or otherwise combined in achieving such embodiments.

[00114] Example 1 includes an apparatus of a mobile station, the apparatus, under control of one or more processors and memory, to reduce connection setup time with a network, the apparatus configured to: encapsulate, within a General Packet Radio Service (GPRS) mobility management (GMM) packet data unit (PDU) attach request message, a Session Management (SM) PDU packet data protocol (PDP) context activation request message and a PDP request indication (PRI) using a primitive from an SM layer to a GMM layer from the mobile station; transmit the GMM PDU attach request message to a Serving GPRS Support Node (SGSN); and receive from the SGSN an SM PDU PDP context activation accept or reject message and a PDP response indication (PRSI) encapsulated within a GMM PDU attach accept or reject response message.

[00115] Example 2 includes the apparatus of example 1, wherein the SM PDU PDP context activation request message includes one or more of a network service access point identifier (NSAPI), transaction identifier (TI), PDP Type, PDP Address, Access Point Name (APN), and quality of service (QoS) requested.

[00116] Example 3 includes the apparatus of example 1, wherein the apparatus is further configured to send to the logical link control layer an existing temporary logic link identifier (TLLI) and a ciphering off indication in a logical layer unit data request (LL- UMTDATA-REQ) primitive.

[00117] Example 4 includes the apparatus of example 1, wherein the apparatus is further configured to create the GMM PDU attach request message in the GMM PDU for registering the GMM layer with a network.

[00118] Example 5 includes the apparatus of example 1, wherein the apparatus is further configured to indicate using a PRI field within the GMM PDU attach request message that the SM PDU PDP context activation request message is encapsulated.

[00119] Example 6 includes the apparatus of example 1, wherein the apparatus is further configured to send from the SM layer to the GMM layer the SM PDU PDP context activation request indicating a creating of a default PDP context for the UE.

[00120] Example 7 includes the apparatus of example 1, wherein the apparatus is further configured to identify and read the PRSI in encapsulated within a GMM PDU attach accept or reject response message.

[00121] Example 8 includes the apparatus of example 1, wherein the apparatus is further configured to forward the SM PDU PDP context activation accept or reject response message from the GMM layer to the SM layer, wherein the apparatus includes at least one of an antenna, a touch sensitive display screen, a speaker, a microphone, a graphics processor, an application processor, internal memory, a non-volatile memory port, and combinations thereof.

[00122] Example 9 includes a Serving GPRS Support Node (SGSN), under control of one or more processors and memory, operable to reduce connection setup time with a mobile station (MS), the one or more processors and memory configured to: receive, from the MS, a Session Management (SM) PDU packet data protocol (PDP) context activation request message and a PDP request indication (PRI) encapsulated with a General Packet Radio Service (GPRS) mobility management (GMM) packet data unit (PDU) attach request message; encapsulate, within a General Packet Radio Service (GPRS) mobility management (GMM) packet data unit (PDU) attach accept or reject response message, a Session Management (SM) PDU packet data protocol

(PDP) context accept or reject response message and a PDP response indication (PRSI) using a primitive from an SM layer to a GMM layer; and transmit the GMM PDU attach accept or reject response message to the MS. [00123] Example 10 includes the SGSN of example 9, further configured to read and identify the PRI within a PRI field of the GMM PDU attach request message.

[00124] Example 11 includes the SGSN of example 9, further configured to forward the SM PDU PDP context activation request message from a GMM layer to the SM layer.

[00125] Example 12 includes the SGSN of example 9, further configured to forward the SM PDU PDP context activation request message from a GMM layer to the SM layer even if a logical link control level (LLC) includes an existing temporary logic link identifier (TLLC) and a ciphering off indication based on the PRI.

[00126] Example 13 includes the SGSN of example 9, further configured to perform an authentication operation for the MS when receiving the GMM PDU attach request message from the MS.

[00127] Example 14 includes the SGSN of example 9, wherein the SGSN is further configured to use a default PDP setup timer at the SM layer to wait for the MS to be authenticated.

[00128] Example 15 includes the SGSN of example 14, further configured to initiate a GMM attach reject response message upon an expiration of a predetermined time set on the default PDP setup timer.

[00129] Example 16 includes the SGSN of example 15, wherein the expiration of the predetermined time set on the default PDP setup timer indicates an authentication operation of the MS failed and the SM PDU PDP context activation request message failed.

[00130] Example 17 includes the SGSN of example 14, further configured to reset the default PDP setup timer upon one of authentication of the UE or an expiration of a predetermined time.

[00131] Example 18 includes the SGSN of example 9, wherein the SGSN is further configured to transmit to the MS a GMM attach reject response message indicating the authentication operation of the MS failed and the SM PDU PDP context activation request message failed.

[00132] Example 19 includes the SGSN of example 9, further configured to validate the SM PDU PDP context activation request message upon receiving the GMM PDU attach request message.

[00133] Example 20 includes the SGSN of example 9, further configured to send to a gateway GPRS support node (GGSN) a SM PDU create PDP context request message when an authentication operation of the MS is successful.

[00134] Example 21 includes the SGSN of example 9, further configured to receive from a gateway GPRS support node (GGSN) a SM PDU create PDP context response message.

[00135] Example 22 includes the SGSN of example 9, further configured to receive from a gateway GPRS support node (GGSN) a SM PDU create PDP context response message.

[00136] Example 23 includes the SGSN of example 9, further configured to send a primitive from the SM layer to the GMM to provide an indication to wait for the SM PDU create PDP context response message before sending the GMM PDU attach accept or reject response message.

[00137] Example 24 includes the SGSN of example 9, wherein the SGSN is further configured to create the GMM PDU attach accept response message at the GMM layer and a SM PDU PDP context accept response at the SM layer.

[00138] Example 25 includes the SGSN of example 9, wherein the SGSN is further configured to transmit to the MS an GMM PDU attach accept response message indicating the GMM PDU attach request message has been accepted, wherein a PDP context remains unactivated by encapsulating a SM PDU PDP context activation reject message in the GMM PDU attach accept response message, wherein the SM PDU PDP context activation request message is sent to initiate a data session following the GMM PDU attach accept response message.

[00139] Example 26 includes a Serving GPRS Support Node (SGSN), under control of one or more processors and memory, operable to reduce connection setup time with a mobile station (MS), the one or more processors and memory configured to: receive, from the MS, a Session Management (SM) PDU packet data protocol (PDP) context activation request message and a PDP request indication (PRI) encapsulated with a General Packet Radio Service (GPRS) mobility management (GMM) packet data unit (PDU) attach request message; encapsulate, within a General Packet Radio Service (GPRS) mobility management (GMM) packet data unit (PDU) attach accept or reject response message, a Session Management (SM) PDU packet data protocol

(PDP) context accept or reject response message and a PDP response indication (PRSI) using a primitive from an SM layer to a GMM layer; use a default PDP setup timer at the SM layer to wait for the MS to be authenticated; and transmit the GMM PDU attach accept or reject response message to the MS.

[00140] Example 27 includes the SGSN of example 26, further configured to initiate a GMM attach reject response message upon an expiration of a predetermined time set on the default PDP setup timer, wherein an expiration of a predetermined time set on the default PDP setup timer indicates an authentication operation of the MS failed and the SM PDU PDP context activation request message failed.

[00141] Example 28 includes the SGSN of example 26, further configured to receive from a gateway GPRS support node (GGSN) a SM PDU create PDP context response message; and send a primitive from the SM layer to the GMM to provide an indication to wait for the SM PDU create PDP context response message before sending the GMM PDU attach accept or reject response message.

[00142] Example 29 includes the SGSN of example 28, wherein the SGSN is further configured to: create the GMM PDU attach accept response message at the GMM layer and a SM PDU PDP context accept response at the SM layer; and transmit a GMM attach accept response message.

[00143] Example 30 includes an apparatus of a mobile station, the apparatus, under control of one or more processors and memory, to reduce connection setup time with a network, the apparatus configured to: encapsulate, within a General Packet Radio

Service (GPRS) mobility management (GMM) packet data unit (PDU) attach request message, a Session Management (SM) PDU packet data protocol (PDP) context activation request message and a PDP request indication (PRI) using a primitive from an SM layer to a GMM layer from the mobile station; transmit the GMM PDU attach request message to a Serving GPRS Support Node (SGSN); and receive from the SGSN an SM PDU PDP context activation accept or reject message and a PDP response indication (PRSI) encapsulated within a GMM PDU attach accept or reject response message.

[00144] Example 31 includes the apparatus of example 30, wherein the SM PDU PDP context activation request message includes one or more of a network service access point identifier (NSAPI), transaction identifier (TI), PDP Type, PDP Address, Access Point Name (APN), and quality of service (QoS) requested. [00145] Example 32 includes the apparatus of examples 30 or 31, wherein the apparatus is further configured to send to the logical link control layer an existing temporary logic link identifier (TLLI) and a ciphering off indication in a logical layer unit data request (LL-U ITDATA-REQ) primitive.

[00146] Example 33 includes the apparatus of example 30, wherein the apparatus is further configured to create the GMM PDU attach request message in the GMM PDU for registering the GMM layer with a network.

[00147] Example 34 includes the apparatus of examples 30 or 33, wherein the apparatus is further configured to indicate using a PRI field within the GMM PDU attach request message that the SM PDU PDP context activation request message is encapsulated.

[00148] Example 35 includes the apparatus of example 30, wherein the apparatus is further configured to send from the SM layer to the GMM layer the SM PDU PDP context activation request indicating a creating of a default PDP context for the UE.

[00149] Example 36 includes the apparatus of examples 30 or 35, wherein the apparatus is further configured to identify and read the PRSI in encapsulated within a GMM PDU attach accept or reject response message.

[00150] Example 37 includes the apparatus of example 30, wherein the apparatus is further configured to forward the SM PDU PDP context activation accept or reject response message from the GMM layer to the SM layer, wherein the apparatus includes at least one of an antenna, a touch sensitive display screen, a speaker, a microphone, a graphics processor, an application processor, internal memory, a non-volatile memory port, and combinations thereof.

[00151] Example 38 includes a Serving GPRS Support Node (SGSN), under control of one or more processors and memory, operable to reduce connection setup time with a mobile station (MS), the one or more processors and memory configured to: receive, from the MS, a Session Management (SM) PDU packet data protocol (PDP) context activation request message and a PDP request indication (PRI) encapsulated with a General Packet Radio Service (GPRS) mobility management (GMM) packet data unit (PDU) attach request message; encapsulate, within a General Packet Radio Service (GPRS) mobility management (GMM) packet data unit (PDU) attach accept or reject response message, a Session Management (SM) PDU packet data protocol

[00152] Example 39 includes the SGSN of example 38, further configured to read and identify the PRI within a PRI field of the GMM PDU attach request message.

[00153] Example 40 includes the SGSN of examples 38 or 39, further configured to forward the SM PDU PDP context activation request message from a GMM layer to the SM layer.

[00154] Example 41 includes the SGSN of example 38, further configured to forward the

SM PDU PDP context activation request message from a GMM layer to the SM layer even if a logical link control level (LLC) includes an existing temporary logic link identifier (TLLC) and a ciphering off indication based on the PRI.

[00155] Example 42 includes the SGSN of examples 38 or 41, further configured to perform an authentication operation for the MS when receiving the GMM PDU attach request message from the MS.

[00156] Example 43 includes the SGSN of example 38, wherein the SGSN is further configured to use a default PDP setup timer at the SM layer to wait for the MS to be authenticated.

[00157] Example 44 includes the SGSN of example 38, further configured to initiate a GMM attach reject response message upon an expiration of a predetermined time set on the default PDP setup timer.

[00158] Example 45 includes the SGSN of examples 38 or 44, wherein the expiration of the predetermined time set on the default PDP setup timer indicates an authentication operation of the MS failed and the SM PDU PDP context activation request message failed.

[00159] Example 46 includes the SGSN of example 45, further configured to reset the default PDP setup timer upon one of authentication of the UE or an expiration of a predetermined time.

[00160] Example 47 includes the SGSN of examples 38 or 46, wherein the SGSN is further configured to transmit to the MS a GMM attach reject response message indicating the authentication operation of the MS failed and the SM PDU PDP context activation request message failed.

[00161] Example 48 includes the SGSN of example 38, further configured to validate the SM PDU PDP context activation request message upon receiving the GMM PDU attach request message.

[00162] Example 49 includes the SGSN of examples 38 or 48, further configured to send to a gateway GPRS support node (GGSN) a SM PDU create PDP context request message when an authentication operation of the MS is successful.

[00163] Example 50 includes the SGSN of example 38, further configured to receive from a gateway GPRS support node (GGSN) a SM PDU create PDP context response message.

[00164] Example 51 includes the SGSN of examples 38 or 50, further configured to receive from a gateway GPRS support node (GGSN) a SM PDU create PDP context response message.

[00165] Example 52 includes the SGSN of example 38, further configured to send a primitive from the SM layer to the GMM to provide an indication to wait for the SM PDU create PDP context response message before sending the GMM PDU attach accept or reject response message.

[00166] Example 53 includes the SGSN of example 38, wherein the SGSN is further configured to create the GMM PDU attach accept response message at the GMM layer and a SM PDU PDP context accept response at the SM layer.

[00167] Example 54 includes the SGSN of examples 38 or 53, wherein the SGSN is further configured to transmit to the MS an GMM PDU attach accept response message indicating the GMM PDU attach request message has been accepted, wherein a PDP context remains unactivated by encapsulating a SM PDU PDP context activation reject message in the GMM PDU attach accept response message, wherein the SM PDU PDP context activation request message is sent to initiate a data session following the GMM PDU attach accept response message.

[00168] Example 55 includes a Serving GPRS Support Node (SGSN), under control of one or more processors and memory, operable to reduce connection setup time with a mobile station (MS), the one or more processors and memory configured to: receive, from the MS, a Session Management (SM) PDU packet data protocol (PDP) context activation request message and a PDP request indication (PRI) encapsulated with a General Packet Radio Service (GPRS) mobility management (GMM) packet data unit (PDU) attach request message; encapsulate, within a General Packet Radio Service (GPRS) mobility management (GMM) packet data unit (PDU) attach accept or reject response message, a Session Management (SM) PDU packet data protocol

[00169] Example 56 includes the SGSN of example 55, further configured to initiate a GMM attach reject response message upon an expiration of a predetermined time set on the default PDP setup timer, wherein an expiration of a predetermined time set on the default PDP setup timer indicates an authentication operation of the MS failed and the SM PDU PDP context activation request message failed.

[00170] Example 57 includes the SGSN of examples 55 or 56, further configured to: receive from a gateway GPRS support node (GGSN) a SM PDU create PDP context response message; and send a primitive from the SM layer to the GMM to provide an indication to wait for the SM PDU create PDP context response message before sending the GMM PDU attach accept or reject response message.

[00171] Example 58 includes the SGSN of example 55, wherein the SGSN is further configured to: create the GMM PDU attach accept response message at the GMM layer and a SM PDU PDP context accept response at the SM layer; and transmit a GMM attach accept response message.

[00172] Example 59 includes a device for reducing connection setup time with a network, the device comprising: means for encapsulating, within a General Packet Radio Service (GPRS) mobility management (GMM) packet data unit (PDU) attach request message, a Session Management (SM) PDU packet data protocol (PDP) context activation request message and a PDP request indication (PRI) using a primitive from an SM layer to a GMM layer from the mobile station; means for transmitting the GMM PDU attach request message to a Serving GPRS Support Node (SGSN); and means for receiving from the SGSN an SM PDU PDP context activation accept or reject message and a PDP response indication (PRSI) encapsulated within a GMM PDU attach accept or reject response message.

[00173] Example 60 includes a device for reducing connection setup time with a mobile station (MS), the device comprising: means for receiving, from the MS, a Session Management (SM) PDU packet data protocol (PDP) context activation request message and a PDP request indication (PRI) encapsulated with a General Packet Radio Service (GPRS) mobility management (GMM) packet data unit (PDU) attach request message; means for encapsulating, within a General Packet Radio Service (GPRS) mobility management (GMM) packet data unit (PDU) attach accept or reject response message, a Session Management (SM) PDU packet data protocol (PDP) context accept or reject response message and a PDP response indication (PRSI) using a primitive from an SM layer to a GMM layer; and means for transmitting the GMM PDU attach accept or reject response message to the MS.

[00174] Example 61 includes a device for reducing connection setup time with a mobile station (MS), the device comprising: means for receiving, from the MS, a Session Management (SM) PDU packet data protocol (PDP) context activation request message and a PDP request indication (PRI) encapsulated with a General Packet Radio Service (GPRS) mobility management (GMM) packet data unit (PDU) attach request message; means for encapsulating, within a General Packet Radio Service (GPRS) mobility management (GMM) packet data unit (PDU) attach accept or reject response message, a Session Management (SM) PDU packet data protocol (PDP) context accept or reject response message and a PDP response indication (PRSI) using a primitive from an SM layer to a GMM layer; means for using a default PDP setup timer at the SM layer to wait for the MS to be authenticated; and means for transmitting the GMM PDU attach accept or reject response message to the MS.

[00175] Example 62 includes an apparatus of a mobile station, the apparatus, under control of one or more processors and memory, to reduce connection setup time with a network, the apparatus configured to: encapsulate, within a General Packet Radio Service (GPRS) mobility management (GMM) packet data unit (PDU) attach request message, a Session Management (SM) PDU packet data protocol (PDP) context activation request message and a PDP request indication (PRI) using a primitive from an SM layer to a GMM layer from the mobile station; transmit the GMM PDU attach request message to a Serving GPRS Support Node (SGSN); and receive from the SGSN an SM PDU PDP context activation accept or reject message and a PDP response indication (PRSI) encapsulated within a GMM PDU attach accept or reject response message. [00176] Example 63 includes the apparatus of example 62, wherein the apparatus is further configured to send to the logical link control layer an existing temporary logic link identifier (TLLI) and a ciphering off indication in a logical layer unit data request (LL-UNITDATA-REQ) primitive, wherein the SM PDU PDP context activation request message includes one or more of a network service access point identifier (NSAPI), transaction identifier (TI), PDP Type, PDP Address, Access Point Name (APN), and quality of service (QoS) requested.

[00177] Example 64 includes the apparatus of example 62 or 63, wherein the apparatus is further configured to: create the GMM PDU attach request message in the GMM PDU for registering the GMM layer with a network; indicate using a PRI field within the GMM PDU attach request message that the SM PDU PDP context activation request message is encapsulated; send from the SM layer to the GMM layer the SM PDU PDP context activation request indicating a creating of a default PDP context for the UE; or identify and read the PRSI in encapsulated within a GMM PDU attach accept or reject response message.

[00178] Example 65 includes the apparatus of any of the examples 62-64, wherein the apparatus is further configured to forward the SM PDU PDP context activation accept or reject response message from the GMM layer to the SM layer, wherein the apparatus includes at least one of an antenna, a touch sensitive display screen, a speaker, a microphone, a graphics processor, an application processor, internal memory, a nonvolatile memory port, and combinations thereof.

[00179] Example 66 includes a Serving GPRS Support Node (SGSN), under control of one or more processors and memory, operable to reduce connection setup time with a mobile station (MS), the one or more processors and memory configured to: receive, from the MS, a Session Management (SM) PDU packet data protocol (PDP) context activation request message and a PDP request indication (PRI) encapsulated with a General Packet Radio Service (GPRS) mobility management (GMM) packet data unit (PDU) attach request message; encapsulate, within a General Packet Radio Service (GPRS) mobility management (GMM) packet data unit (PDU) attach accept or reject response message, a Session Management (SM) PDU packet data protocol

[00180] Example 67 includes the SGSN of example 66, further configured to: read and identify the PRI within a PRI field of the GMM PDU attach request message; forward the SM PDU PDP context activation request message from a GMM layer to the SM layer; forward the SM PDU PDP context activation request message from a GMM layer to the SM layer even if a logical link control level (LLC) includes an existing temporary logic link identifier (TLLC) and a ciphering off indication based on the PRI; perform an authentication operation for the MS when receiving the GMM PDU attach request message from the MS; or use a default PDP setup timer at the SM layer to wait for the MS to be authenticated.

[00181] Example 68 includes the SGSN of examples 66 or 67, further configured to initiate a GMM attach reject response message upon an expiration of a predetermined time set on the default PDP setup timer, wherein the expiration of the predetermined time set on the default PDP setup timer indicates an authentication operation of the MS failed and the SM PDU PDP context activation request message failed.

[00182] Example 69 includes the SGSN of any of the examples 66-68, further configured to: reset the default PDP setup timer upon one of authentication of the UE or an expiration of a predetermined time: transmit to the MS a GMM attach reject response message indicating the authentication operation of the MS failed and the SM PDU PDP context activation request message failed; validate the SM PDU PDP context activation request message upon receiving the GMM PDU attach request message; send to a gateway GPRS support node (GGSN) a SM PDU create PDP context request message when an authentication operation of the MS is successful; or receive from a gateway GPRS support node (GGSN) a SM PDU create PDP context response message.

[00183] Example 70 includes the SGSN of any of the examples 66-69, further configured to receive from a gateway GPRS support node (GGSN) a SM PDU create PDP context response message.

[00184] Example 71 includes the SGSN of any of the examples 66-70, further configured to receive from a gateway GPRS support node (GGSN) a SM PDU create PDP context response message.

[00185] Example 72 includes the SGSN of any of the examples 66-71, further configured to: send a primitive from the SM layer to the GMM to provide an indication to wait for the SM PDU create PDP context response message before sending the GMM PDU attach accept or reject response message; or create the GMM PDU attach accept response message at the GMM layer and a SM PDU PDP context accept response at the SM layer.

[00186] Example 73 includes the SGSN of any of the examples 66-72, wherein the

SGSN is further configured to transmit to the MS an GMM PDU attach accept response message indicating the GMM PDU attach request message has been accepted, wherein a PDP context remains unactivated by encapsulating a SM PDU PDP context activation reject message in the GMM PDU attach accept response message, wherein the SM PDU PDP context activation request message is sent to initiate a data session following the GMM PDU attach accept response message.

[00187] Example 74 includes a Serving GPRS Support Node (SGSN), under control of one or more processors and memory, operable to reduce connection setup time with a mobile station (MS), the one or more processors and memory configured to: receive, from the MS, a Session Management (SM) PDU packet data protocol (PDP) context activation request message and a PDP request indication (PRI) encapsulated with a General Packet Radio Service (GPRS) mobility management (GMM) packet data unit (PDU) attach request message; encapsulate, within a General Packet Radio Service (GPRS) mobility management (GMM) packet data unit (PDU) attach accept or reject response message, a Session Management (SM) PDU packet data protocol

[00188] Example 75 includes the SGSN of example 74, further configured to: initiate a GMM attach reject response message upon an expiration of a predetermined time set on the default PDP setup timer, wherein an expiration of a predetermined time set on the default PDP setup timer indicates an authentication operation of the MS failed and the SM PDU PDP context activation request message failed; receive from a gateway GPRS support node (GGSN) a SM PDU create PDP context response message; or send a primitive from the SM layer to the GMM to provide an indication to wait for the SM PDU create PDP context response message before sending the GMM PDU attach accept or reject response message.

[00189] Example 76 includes the SGSN of examples 74 or 75, wherein the SGSN is further configured to: create the GMM PDU attach accept response message at the GMM layer and a SM PDU PDP context accept response at the SM layer; and transmit a GMM attach accept response message.

[00190] Example 78 can include a wireless device (e.g., a user equipment), such as the apparatus of Example 1, that includes at least one of an antenna, a touch sensitive display screen, a speaker, a microphone, a graphics processor, an application processor, internal memory, a non-volatile memory port, and combinations thereof.

[00191] Various techniques, or certain aspects or portions thereof, may take the form of program code (i.e., instructions) embodied in tangible media, such as floppy diskettes, compact disc-read-only memory (CD-ROMs), hard drives, non-transitory computer readable storage medium, or any other machine-readable storage medium wherein, when the program code is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the various techniques. Circuitry can include hardware, firmware, program code, executable code, computer instructions, and/or software. A non-transitory computer readable storage medium can be a computer readable storage medium that does not include signal. In the case of program code execution on programmable computers, the computing device may include a processor, a storage medium readable by the processor (including volatile and non-volatile memory and/or storage elements), at least one input device, and at least one output device. The volatile and non-volatile memory and/or storage elements may be a random-access memory (RAM), erasable programmable read only memory (EPROM), flash drive, optical drive, magnetic hard drive, solid state drive, or other medium for storing electronic data. The node and wireless device may also include a transceiver module (i.e., transceiver), a counter module (i.e., counter), a processing module (i.e., processor), and/or a clock module (i.e., clock) or timer module (i.e., timer). One or more programs that may implement or utilize the various techniques described herein may use an application programming interface (API), reusable controls, and the like. Such programs may be implemented in a high level procedural or object oriented programming language to communicate with a computer system. However, the program(s) may be implemented in assembly or machine language, if desired. In any case, the language may be a compiled or interpreted language, and combined with hardware

implementations.

[00192] As used herein, the term processor can include general purpose processors, specialized processors such as VLSI, FPGAs, or other types of specialized processors, as well as base band processors used in transceivers to send, receive, and process wireless communications.

[00193] It should be understood that many of the functional units described in this specification have been labeled as modules, in order to more particularly emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising custom very-large-scale integration (VLSI) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.

[00194] Modules may also be implemented in software for execution by various types of processors. An identified module of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions, which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together, but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the module and achieve the stated purpose for the module.

[00195] Indeed, a module of executable code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different storage devices, and may exist, at least partially, merely as electronic signals on a system or network. The modules may be passive or active, including agents operable to perform desired functions.

[00196] Reference throughout this specification to "an example" or "exemplary" means that a particular feature, structure, or characteristic described in connection with the example is included in at least one embodiment of the present invention. Thus, appearances of the phrases "in an example" or the word "exemplary" in various places throughout this specification are not necessarily all referring to the same embodiment.

[00197] As used herein, a plurality of items, structural elements, compositional elements, and/or materials may be presented in a common list for convenience. However, these lists should be construed as though each member of the list is individually identified as a separate and unique member. Thus, no individual member of such list should be construed as a de facto equivalent of any other member of the same list solely based on their presentation in a common group without indications to the contrary. In addition, various embodiments and example of the present invention may be referred to herein along with alternatives for the various components thereof. It is understood that such embodiments, examples, and alternatives are not to be construed as defacto equivalents of one another, but are to be considered as separate and autonomous representations of the present invention.

[00198] Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided, such as examples of layouts, distances, network examples, etc., to provide a thorough understanding of embodiments of the invention. One skilled in the relevant art will recognize, however, that the invention can be practiced without one or more of the specific details, or with other methods, components, layouts, etc. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the invention.

While the forgoing examples are illustrative of the principles of the present invention in one or more particular applications, it will be apparent to those of ordinary skill in the art that numerous modifications in form, usage and details of implementation can be made without the exercise of inventive faculty, and without departing from the principles and concepts of the invention. Accordingly, it is not intended that the invention be limited, except as by the claims set forth below.

Claims

CLAIMS What is claimed is:

1. An apparatus of a mobile station, the apparatus, under control of one or more processors and memory, to reduce connection setup time with a network, the apparatus configured to:

encapsulate, within a General Packet Radio Service (GPRS) mobility management (GMM) packet data unit (PDU) attach request message, a Session Management (SM) PDU packet data protocol (PDP) context activation request message and a PDP request indication (PRI) using a primitive from an SM layer to a GMM layer from the mobile station;

transmit the GMM PDU attach request message to a Serving GPRS Support Node (SGSN); and

receive from the SGSN an SM PDU PDP context activation accept or reject message and a PDP response indication (PRSI) encapsulated within a GMM PDU attach accept or reject response message.

2. The apparatus of claim 1, wherein the SM PDU PDP context activation request message includes one or more of a network service access point identifier (NSAPI), transaction identifier (TI), PDP Type, PDP Address, Access Point Name (APN), and quality of service (QoS) requested.

3. The apparatus of claim 1 or 2, wherein the apparatus is further configured to send to the logical link control layer an existing temporary logic link identifier (TLLI) and a ciphering off indication in a logical layer unit data request (LL- UNITDATA-REQ) primitive.

4. The apparatus of claim 1, wherein the apparatus is further configured to create the GMM PDU attach request message in the GMM PDU for registering the GMM layer with a network.

5. The apparatus of claim 1 or 4, wherein the apparatus is further configured to indicate using a PRI field within the GMM PDU attach request message that the SM PDU PDP context activation request message is encapsulated.

6. The apparatus of claim 1, wherein the apparatus is further configured to send from the SM layer to the GMM layer the SM PDU PDP context activation request indicating a creating of a default PDP context for the UE.

7. The apparatus of claim 1 or 6, wherein the apparatus is further configured to identify and read the PRSI in encapsulated within a GMM PDU attach accept or reject response message.

8. The apparatus of claim 1, wherein the apparatus is further configured to forward the SM PDU PDP context activation accept or reject response message from the GMM layer to the SM layer.

9. The apparatus of claim 1, wherein the apparatus includes at least one of an antenna, a touch sensitive display screen, a speaker, a microphone, a graphics processor, an application processor, internal memory, a non-volatile memory port, and combinations thereof.

10. An Serving GPRS Support Node (SGSN), under control of one or more processors and memory, operable to reduce connection setup time with a mobile station (MS), the one or more processors and memory configured to: receive, from the MS, a Session Management (SM) PDU packet data protocol (PDP) context activation request message and a PDP request indication (PRI) encapsulated with a General Packet Radio Service (GPRS) mobility management (GMM) packet data unit (PDU) attach request message; encapsulate, within a General Packet Radio Service (GPRS) mobility management (GMM) packet data unit (PDU) attach accept or reject response message, a Session Management (SM) PDU packet data protocol (PDP) context accept or reject response message and a PDP response indication (PRSI) using a primitive from an SM layer to a GMM layer; and

transmit the GMM PDU attach accept or reject response message to the

MS.

11. The SGSN of claim 10, further configured to read and identify the PRI within a PRI field of the GMM PDU attach request message.

12. The SGSN of claim 10 or 11, further configured to forward the SM PDU PDP context activation request message from a GMM layer to the SM layer.

13. The SGSN of claim 10, further configured to forward the SM PDU PDP context activation request message from a GMM layer to the SM layer even if a logical link control level (LLC) includes an existing temporary logic link identifier (TLLC) and a ciphering off indication based on the PRI.

14. The SGSN of claim 10 or 13, further configured to perform an authentication operation for the MS when receiving the GMM PDU attach request message from the MS.

15. The SGSN of claim 10, wherein the SGSN is further configured to use a default PDP setup timer at the SM layer to wait for the MS to be authenticated.

16. The SGSN of claim 10, further configured to initiate a GMM attach reject response message upon an expiration of a predetermined time set on the default PDP setup timer.

17. The SGSN of claim 10 or 16, wherein the expiration of the

predetermined time set on the default PDP setup timer indicates an authentication operation of the MS failed and the SM PDU PDP context activation request message failed.

18. The SGSN of claim 15, further configured to reset the default PDP setup timer upon one of authentication of the UE or an expiration of a predetermined time.

19. The SGSN of claim 10 or 18, wherein the SGSN is further configured to transmit to the MS a GMM attach reject response message indicating the authentication operation of the MS failed and the SM PDU PDP context activation request message failed.

20. The SGSN of claim 10, further configured to validate the SM PDU PDP context activation request message upon receiving the GMM PDU attach request message.

21. The SGSN of claim 10 or 20, further configured to send to a gateway GPRS support node (GGSN) a SM PDU create PDP context request message when an authentication operation of the MS is successful.

22. The SGSN of claim 10, further configured to receive from a gateway GPRS support node (GGSN) a SM PDU create PDP context response message.

23. The SGSN of claim 10 or 22, further configured to receive from a gateway GPRS support node (GGSN) a SM PDU create PDP context response message.

24. The SGSN of claim 10, further configured to send a primitive from the SM layer to the GMM to provide an indication to wait for the SM PDU create PDP context response message before sending the GMM PDU attach accept or reject response message.

25. The SGSN of claim 10, wherein the SGSN is further configured to create the GMM PDU attach accept response message at the GMM layer and a SM PDU PDP context accept response at the SM layer.

26. The SGSN of claim 10 or 25, wherein the SGSN is further configured to transmit to the MS an GMM PDU attach accept response message indicating the GMM PDU attach request message has been accepted, wherein a PDP context remains unactivated by encapsulating a SM PDU PDP context activation reject message in the GMM PDU attach accept response message, wherein the SM PDU PDP context activation request message is sent to initiate a data session following the GMM PDU attach accept response message.

27. A Serving GPRS Support Node (SGSN), under control of one or more processors and memory, operable to reduce connection setup time with a mobile station (MS), the one or more processors and memory configured to: receive, from the MS, a Session Management (SM) PDU packet data protocol (PDP) context activation request message and a PDP request indication (PRI) encapsulated with a General Packet Radio Service (GPRS) mobility management (GMM) packet data unit (PDU) attach request message;

encapsulate, within a General Packet Radio Service (GPRS) mobility management (GMM) packet data unit (PDU) attach accept or reject response message, a Session Management (SM) PDU packet data protocol (PDP) context accept or reject response message and a PDP response indication (PRSI) using a primitive from an SM layer to a GMM layer;

use a default PDP setup timer at the SM layer to wait for the MS to be authenticated; and

transmit the GMM PDU attach accept or reject response message to the MS.

28. The SGSN of claim 27, further configured to initiate a GMM attach reject response message upon an expiration of a predetermined time set on the default PDP setup timer, wherein an expiration of a predetermined time set on the default PDP setup timer indicates an authentication operation of the MS failed and the SM PDU PDP context activation request message failed.

29. The SGSN of claim 27 or 28, further configured to

receive from a gateway GPRS support node (GGSN) a SM PDU create PDP context response message; and

send a primitive from the SM layer to the GMM to provide an indication to wait for the SM PDU create PDP context response message before sending the GMM PDU attach accept or reject response message.

30. The SGSN of claim 29, wherein the SGSN is further configured to: create the GMM PDU attach accept response message at the GMM layer and a SM PDU PDP context accept response at the SM layer; and

transmit a GMM attach accept response message.