WO2014172867A1

WO2014172867A1 - Simple and efficient way to update and acknowledge preferred gsm/lte plmn roaming list inside handset

Info

Publication number: WO2014172867A1
Application number: PCT/CN2013/074702
Authority: WO
Inventors: Wentao Zhang; Kang Wang; Grace Wang
Original assignee: Qualcomm Incorporated
Priority date: 2013-04-25
Filing date: 2013-04-25
Publication date: 2014-10-30

Abstract

A method, an apparatus, and a computer program product for wireless communication are provided. The apparatus detects an update of a preferred information list, connects to an information list server when the update is detected, determines that a preferred information list stored at the UE is not current with an updated preferred information list stored at the information list server, receives the updated preferred information list from the information list server, and sends a status of the update to the information list server. The status of the update may be sent via an HTTP POST message or a (200) OK message. The status of the update may also be sent via an Internet protocol (IP) packet to a destination having a transport control protocol (TCP) port number or a user datagram protocol (UDP) port number dedicated to receiving status information.

Description

SIMPLE AND EFFICIENT WAY TO UPDATE AND ACKNOWLEDGE PREFERRED GSM/LTE PLMN ROAMING LIST INSIDE HANDSET

BACKGROUND

Field

The present disclosure relates generally to communication systems, and more particularly, to updating a preferred roaming list (PRL), a preferred public land mobile network (PLMN) list, or multimode system selection (MMSS) records stored in a mobile device.

Background

Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power). Examples of such multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

A UMTS Terrestrial Radio Access Network (UTRAN) is a radio access network (RAN) defined as a part of the Universal Mobile Telecommunications System (UMTS), a third generation (3G) mobile phone technology supported by the 3rd Generation Partnership Project (3GPP). The UMTS, which is the successor to Global System for Mobile Communications (GSM) technologies, currently supports various air interface standards, such as wideband-code division multiple access (W- CDMA), time division-code Division multiple access (TD-CDMA), and TD- SCDMA. The UMTS also supports enhanced 3G data communications protocols, such as high speed packet access (HSPA), which provides higher data transfer speeds and capacity to associated UMTS networks.

Multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate on a municipal, national, regional, and even global level. An example of an emerging telecommunication standard is Long Term Evolution (LTE). LTE is a set of enhancements to the UMTS mobile standard promulgated by 3GPP. It is designed to better support mobile broadband Internet access by improving spectral efficiency, lowering costs, improving services, making use of new spectrum, and better integrating with other open standards using OFDM A on the downlink (DL), SC-FDMA on the uplink (UL), and multiple-input multiple-output (MEVIO) antenna technology.

[0005] Another example of a telecommunication standard is CDMA2000 (also known as IMT Multi-Carrier (IMT-MQ). CDMA2000 is a family of mobile technology standards, which use CDMA channel access, to send voice, data, and signaling data between mobile phones and cell sites.

[0006] As the demand for mobile broadband access continues to increase, there exists a need for further improvements in telecommunication technology. Preferably, these improvements should be applicable to multi-access technologies and the telecommunication standards that employ these technologies.

SUMMARY

[0007] In an aspect of the disclosure, a method, a computer program product, and an apparatus are provided. The apparatus detects an update of a preferred information list and connects to an information list server when the update is detected. When connected to the information list server, the apparatus determines whether a preferred information list stored at the apparatus is current with an updated preferred information list stored at the information list server. If not current, the apparatus receives the updated preferred information list from the information list server and sends a status of the update to the information list server. The status of the update may be sent via an HTTP POST message or a 200 OK message. The status of the update may also be sent via an Internet protocol (IP) packet to a destination having a transport control protocol (TCP) port number or a user datagram protocol (UDP) port number dedicated to receiving status information. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] FIG. 1 is a diagram illustrating an example of a network architecture.

[0009] FIG. 2 is a diagram illustrating an example of an access network.

[0010] FIG. 3 is a diagram illustrating an example of an evolved Node B and user equipment in an access network.

[0011] FIG. 4 is a diagram illustrating a method of updating a preferred information list.

[0012] FIG. 5 is a diagram illustrating a method of updating a preferred information list.

[0013] FIG. 6 is a diagram illustrating a method of updating a preferred information list.

[0014] FIG. 7 is a diagram illustrating a method of updating a preferred information list.

[0015] FIG. 8 is a flow chart of a method of wireless communication.

[0016] FIG. 9 is a conceptual data flow diagram illustrating the data flow between different modules/means/components in an exemplary apparatus.

[0017] FIG. 10 is a diagram illustrating an example of a hardware implementation for an apparatus employing a processing system.

DETAILED DESCRIPTION

[0018] The detailed description set forth below in connection with the appended drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well known structures and components are shown in block diagram form in order to avoid obscuring such concepts.

[0019] Several aspects of telecommunication systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. [0020] By way of example, an element, or any portion of an element, or any combination of elements may be implemented with a "processing system" that includes one or more processors. Examples of processors include microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure. One or more processors in the processing system may execute software. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0021] Accordingly, in one or more exemplary embodiments, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or encoded as one or more instructions or code on a computer-readable medium. Computer- readable media includes computer storage media. Storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. Disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), and floppy disk where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer- readable media.

[0022] FIG. 1 is a diagram illustrating an LTE network architecture 100. The LTE network architecture 100 may be referred to as an Evolved Packet System (EPS) 100. The EPS 100 may include one or more user equipment (UE) 102, an Evolved UMTS Terrestrial Radio Access Network (E-UTRAN) 104, an Evolved Packet Core (EPC) 110, a Home Subscriber Server (HSS) 120, and an Operator's Internet Protocol (IP) Services 122. The EPS can interconnect with other access networks, but for simplicity those entities/interfaces are not shown. As shown, the EPS provides packet- switched services, however, as those skilled in the art will readily appreciate, the various concepts presented throughout this disclosure may be extended to networks providing circuit- switched services.

[0023] The E-UTRAN includes the evolved Node B (eNB) 106 and other eNBs 108.

The eNB 106 provides user and control planes protocol terminations toward the UE 102. The eNB 106 may be connected to the other eNBs 108 via a backhaul (e.g., an X2 interface). The eNB 106 may also be referred to as a base station, a Node B, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), or some other suitable terminology. The eNB 106 provides an access point to the EPC 110 for a UE 102. Examples of UEs 102 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, a tablet, or any other similar functioning device. The UE 102 may also be referred to by those skilled in the art as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.

[0024] The eNB 106 is connected to the EPC 110. The EPC 110 includes a Mobility

Management Entity (MME) 112, other MMEs 114, a Serving Gateway 116, a Multimedia Broadcast Multicast Service (MBMS) Gateway 124, a Broadcast Multicast Service Center (BM-SC) 126, and a Packet Data Network (PDN) Gateway 118. The MME 112 is the control node that processes the signaling between the UE 102 and the EPC 110. Generally, the MME 112 provides bearer and connection management. All user IP packets are transferred through the Serving Gateway 116, which itself is connected to the PDN Gateway 118. The PDN Gateway 118 provides UE IP address allocation as well as other functions. The PDN Gateway 118 is connected to the Operator's IP Services 122. The Operator's IP Services 122 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), and a PS Streaming Service (PSS). The BM-SC 126 may provide functions for MBMS user service provisioning and delivery. The BM-SC 126 may serve as an entry point for content provider MBMS transmission, may be used to authorize and initiate MBMS Bearer Services within a PLMN, and may be used to schedule and deliver MBMS transmissions. The MBMS Gateway 124 may be used to distribute MBMS traffic to the eNBs (e.g., 106, 108) belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service, and may be responsible for session management (start/stop) and for collecting eMBMS related charging information.

[0025] FIG. 2 is a diagram illustrating an example of an access network 200 in an LTE network architecture. In this example, the access network 200 is divided into a number of cellular regions (cells) 202. One or more lower power class eNBs 208 may have cellular regions 210 that overlap with one or more of the cells 202. The lower power class eNB 208 may be a femto cell (e.g., home eNB (HeNB)), pico cell, micro cell, or remote radio head (RRH). The macro eNBs 204 are each assigned to a respective cell 202 and are configured to provide an access point to the EPC 110 for all the UEs 206 in the cells 202. There is no centralized controller in this example of an access network 200, but a centralized controller may be used in alternative configurations. The eNBs 204 are responsible for all radio related functions including radio bearer control, admission control, mobility control, scheduling, security, and connectivity to the serving gateway 116. An eNB may support one or multiple (e.g., three) cells (also referred to as a sector). The term "cell" can refer to the smallest coverage area of an eNB and/or an eNB subsystem serving are particular coverage area. Further, the terms "eNB," "base station," and "cell" may be used interchangeably herein.

[0026] The modulation and multiple access scheme employed by the access network

200 may vary depending on the particular telecommunications standard being deployed. In LTE applications, OFDM is used on the DL and SC-FDMA is used on the UL to support both frequency division duplex (FDD) and time division duplex (TDD). As those skilled in the art will readily appreciate from the detailed description to follow, the various concepts presented herein are well suited for LTE applications. However, these concepts may be readily extended to other telecommunication standards employing other modulation and multiple access techniques. By way of example, these concepts may be extended to Evolution-Data Optimized (EV-DO) or Ultra Mobile Broadband (UMB). EV-DO and UMB are air interface standards promulgated by the 3rd Generation Partnership Project 2 (3GPP2) as part of the CDMA2000 family of standards and employs CDMA to provide broadband Internet access to mobile stations. These concepts may also be extended to Universal Terrestrial Radio Access (UTRA) employing Wideband-CDMA (W- CDMA) and other variants of CDMA, such as TD-SCDMA; Global System for Mobile Communications (GSM) employing TDMA; and Evolved UTRA (E-UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, and Flash-OFDM employing OFDM A. UTRA, E-UTRA, UMTS, LTE and GSM are described in documents from the 3GPP organization. CDMA2000 and UMB are described in documents from the 3GPP2 organization. The actual wireless communication standard and the multiple access technology employed will depend on the specific application and the overall design constraints imposed on the system.

[0027] The eNBs 204 may have multiple antennas supporting MIMO technology. The use of MIMO technology enables the eNBs 204 to exploit the spatial domain to support spatial multiplexing, beamforming, and transmit diversity. Spatial multiplexing may be used to transmit different streams of data simultaneously on the same frequency. The data streams may be transmitted to a single UE 206 to increase the data rate or to multiple UEs 206 to increase the overall system capacity. This is achieved by spatially precoding each data stream (i.e., applying a scaling of an amplitude and a phase) and then transmitting each spatially precoded stream through multiple transmit antennas on the DL. The spatially precoded data streams arrive at the UE(s) 206 with different spatial signatures, which enables each of the UE(s) 206 to recover the one or more data streams destined for that UE 206. On the UL, each UE 206 transmits a spatially precoded data stream, which enables the eNB 204 to identify the source of each spatially precoded data stream.

[0028] Spatial multiplexing is generally used when channel conditions are good. When channel conditions are less favorable, beamforming may be used to focus the transmission energy in one or more directions. This may be achieved by spatially precoding the data for transmission through multiple antennas. To achieve good coverage at the edges of the cell, a single stream beamforming transmission may be used in combination with transmit diversity.

[0029] In the detailed description that follows, various aspects of an access network will be described with reference to a MIMO system supporting OFDM on the DL. OFDM is a spread- spectrum technique that modulates data over a number of subcarriers within an OFDM symbol. The subcarriers are spaced apart at precise frequencies. The spacing provides "orthogonality" that enables a receiver to recover the data from the subcarriers. In the time domain, a guard interval (e.g., cyclic prefix) may be added to each OFDM symbol to combat inter-OFDM-symbol interference. The UL may use SC-FDMA in the form of a DFT-spread OFDM signal to compensate for high peak- to-average power ratio (PAPR).

[0030] FIG. 3 is a block diagram of an eNB 310 in communication with a UE 350 in an access network. In the DL, upper layer packets from the core network are provided to a controller/processor 375. The controller/processor 375 implements the functionality of an L2 layer. In the DL, the controller/processor 375 provides header compression, ciphering, packet segmentation and reordering, multiplexing between logical and transport channels, and radio resource allocations to the UE 350 based on various priority metrics. The controller/processor 375 is also responsible for HARQ operations, retransmission of lost packets, and signaling to the UE 350.

[0031] The transmit (TX) processor 316 implements various signal processing functions for an LI layer (i.e., physical layer). The signal processing functions include coding and interleaving to facilitate forward error correction (FEC) at the UE 350 and mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols are then split into parallel streams. Each stream is then mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and/or frequency domain, and then combined together using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimate may be derived from a reference signal and/or channel condition feedback transmitted by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX may modulate an RF carrier with a respective spatial stream for transmission.

[0032] At the UE 350, each receiver 354RX receives a signal through its respective antenna 352. Each receiver 354RX recovers information modulated onto an RF carrier and provides the information to the receive (RX) processor 356. The RX processor 356 implements various signal processing functions of an LI layer. The RX processor 356 may perform spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, they may be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 then converts the OFDM symbol stream from the time-domain to the frequency domain using a Fast Fourier Transform (FFT). The frequency domain signal comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, and the reference signal, are recovered and demodulated by determining the most likely signal constellation points transmitted by the eNB 310. These soft decisions may be based on channel estimates computed by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the eNB 310 on the physical channel. The data and control signals are then provided to the controller/processor 359.

[0033] The controller/processor 359 implements an L2 layer. The controller/processor can be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer-readable medium. In the UL, the controller/processor 359 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover upper layer packets from the core network. The upper layer packets are then provided to a data sink 362, which represents all the protocol layers above an L2 layer. Various control signals may also be provided to the data sink 362 for L3 processing. The controller/processor 359 is also responsible for error detection using an acknowledgement (ACK) and/or negative acknowledgement (NACK) protocol to support HARQ operations.

[0034] In the UL, a data source 367 is used to provide upper layer packets to the controller/processor 359. The data source 367 represents all protocol layers above an L2 layer. Similar to the functionality described in connection with the DL transmission by the eNB 310, the controller/processor 359 implements an L2 layer for the user plane and the control plane by providing header compression, ciphering, packet segmentation and reordering, and multiplexing between logical and transport channels based on radio resource allocations by the eNB 310. The controller/processor 359 is also responsible for HARQ operations, retransmission of lost packets, and signaling to the eNB 310.

[0035] Channel estimates derived by a channel estimator 358 from a reference signal or feedback transmitted by the eNB 310 may be used by the TX processor 368 to select the appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antenna 352 via separate transmitters 354TX. Each transmitter 354TX may modulate an RF carrier with a respective spatial stream for transmission.

[0036] The UL transmission is processed at the eNB 310 in a manner similar to that described in connection with the receiver function at the UE 350. Each receiver 318RX receives a signal through its respective antenna 320. Each receiver 318RX recovers information modulated onto an RF carrier and provides the information to a RX processor 370. The RX processor 370 may implement an LI layer.

[0037] The controller/processor 375 implements an L2 layer. The controller/processor

375 can be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer-readable medium. In the UL, the control/processor 375 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover upper layer packets from the UE 350. Upper layer packets from the controller/processor 375 may be provided to the core network. The controller/processor 375 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.

[0038] A preferred information list (e.g., a preferred roaming list (PRL), a preferred public land mobile network (PLMN) list, or a multimode system selection (MMSS) record) is a database residing in a wireless device that contains information used during a system selection and acquisition process. In the case of removable user identity module (R-UIM)-based CDMA devices, the PRL may resides on the R- UIM. In the case of universal integrated circuit card (UlCC)-based GSM devices, the preferred PLMN list and MMSS record may reside on the UICC. The PRL/preferred PLMN list/MMSS record indicates which bands, sub-bands and service provider identifiers will be scanned and in what priority order. Without a PRL/preferred PLMN list/MMSS record, the wireless device may not be able to roam, i.e., obtain service outside of a home area. A missing or corrupt PRL/preferred PLMN list/MMSS record can lead to a device user not having service at all.

[0039] On many networks, regularly updating the PRL/preferred PLMN list/MMSS record is desirable when the device user uses the device outside the home area frequently, particularly if the device is used in multiple different areas. This allows the device to choose the best roaming carriers, particularly "roaming partners" with whom a home carrier has a cost-saving roaming agreement, rather than using nonaffiliated carriers. PRL/preferred PLMN list/MMSS record files can also be used to identify home networks along with roaming partners, thus making the PRL/preferred PLMN list/MMSS record an actual list that determines the total coverage of the device user, both home and roaming coverage.

[0040] In an aspect, a roaming carrier providing roaming services to a device may set different priorities for different networks. For example, the roaming carrier may designate a number of PLMNs as preferred PLMNs. Non-designated PLMNs may be considered as non-preferred PLMNs. When a mobile device roams to a non- preferred PLMN (e.g., non-preferred GSM network), a location update request may be rejected several times before being accepted. This leads to a longer registration period. To accelerate a network search time, a home carrier may require mobile devices/UE/handsets to timely update and store new roaming carrier preferred information lists (e.g., new PRLs/new preferred PLMN lists/new MMSS records). The roaming carrier may update the preferred information lists periodically (e.g., twice a year). Whenever a PRL/preferred PLMN list/MMSS record changes, a version number of the PRL/preferred PLMN list/MMSS record may change. In an aspect, a UE may be equivalent to the combination of a UE and a R-UIM/UICC inserted in the UE. The UE may perform the update by connecting to an information list server (e.g., PRL/PLMN list/MMSS record server) to acquire an updated PRL/preferred PLMN list/MMSS record.

[0041] In roaming scenarios, the UE may select a preferred system based on the updated PRL/preferred PLMN list/MMSS record. Once the UE completes the update, the UE may report a status/acknowledgment of the update to the information list server (e.g., PRL/PLMN list/MMSS list server). For example, the reported status/acknowledgment may indicate whether the updated PRL/preferred PLMN list/MMSS record was successfully received.

[0042] In an aspect, the UE may report the status/acknowledgment of the update to the

PRL/PLMN list/MMSS record server by sending a lx SMS message (e.g., CDMA 2000 message) carrying the status/acknowledgment. For example, the UE may trigger the R-UIM/UICC to send the lx SMS message carrying the status/acknowledgment. Alternatively, the UE may generate and send the lx SMS message without using the R-UIM/UICC. FIG. 4 is a diagram 400 illustrating a method of updating a preferred information list (e.g., PRL/preferred PLMN list/MMSS record). At step 402, a UE may detect a command to initiate an update of a preferred information list. For example, the UE detects the command when a user selects a UE input key or display screen icon initiating the update.

At step 404, once the update is initiated, the UE may set up a data connection with an information list server (e.g., PRL/preferred PLMN list/MMSS record server). When the data connection is established, the UE may acquire an updated preferred information list version number from the information list server. Notably, whenever the updated preferred information list is updated, the information list server incrementally increases the version number. The UE may also acquire other information, such as cyclic redundancy check (CRC) information.

At step 406, the UE compares a preferred information list version number stored at the UE with the updated preferred information list version number acquired from the information list server. When the UE determines that the preferred information list stored at the UE is not current with the updated preferred information list stored at the information list server, the UE downloads the updated preferred information list (e.g., updated PRL/preferred PLMN list/MMSS record) from the information list server. In one example, the UE may download the updated preferred information list via a hyper text transport protocol (HTTP).

At step 408, the UE triggers a R-UIM/UICC inserted in the UE to generate a status report (or acknowledgment). The status report may indicate whether the update was successful or not (e.g., whether the updated preferred information list was successfully received or not at the UE).

At step 410, the R-UIM/UICC inserted in the UE sends the status report to the information list server. In one example, the R-UIM/UICC sends the status report via a cdma2000 lx SMS message.

FIG. 5 is a diagram 500 illustrating a method of updating a preferred information list (e.g., PRL/preferred PLMN list/MMSS record). At step 502, a UE may detect a command to initiate an update of a preferred information list. For example, the UE detects the command when a user selects a UE input key or display screen icon initiating the update.

At step 504, once the update is initiated, the UE may set up a data connection with an information list server (e.g., PRL/preferred PLMN list/MMSS record server). When the data connection is established, the UE may acquire an updated preferred information list version number from the information list server. Notably, whenever the updated preferred information list is updated, the information list server incrementally increases the version number. The UE may also acquire other information, such as cyclic redundancy check (CRC) information.

At step 506, the UE compares a preferred information list version number stored at the UE with the updated preferred information list version number acquired from the information list server. When the UE determines that the preferred information list stored at the UE is not current with the updated preferred information list stored at the information list server, the UE downloads the updated preferred information list (e.g., updated PRL/preferred PLMN list/MMSS record) from the information list server. In one example, the UE may download the updated preferred information list via a hyper text transport protocol (HTTP).

At step 508, the UE generates a status report (acknowledgment) without communicating with a R-UIM/UICC inserted in the UE. The status report may indicate whether the update was successful or not (e.g., whether the updated preferred information list was successfully received or not at the UE). Thereafter, the UE sends the status report to the information list server. In one example, the UE sends the status report via a cdma2000 lx SMS message.

With respect to cdma2000 UEs, cdma2000 lx SMS messages are sent via the R- UIM/UICC card inserted in the UE because generating a cdma2000 lx SMS message requires special cdma2000 lx protocols and stacks, which are only available in the R-UIM/UICC. Thus, because it is difficult for the UE to support the special lx protocols and stacks, the UE will have difficulty generating a lx SMS message without communicating with the R-UIM/UICC.

In an aspect, the UE may send commands through a UE-card interface to trigger the R-UIM/UICC card to send the lx SMS message. However, no such commands currently exist between the UE-card interface and R-UIM/UICC for this purpose. Moreover, adding new UE-card interface commands for triggering the R- UIM/UICC would be difficult to implement.

Referring to FIGs. 4 and 5, issues arise with respect to the R-UIM/UICC or the UE (without communicating with the R-UEVI/UICC) sending the lx SMS message carrying the status report/acknowledgment of the update to the information list server. For example, regarding the UE triggering the R-UIIM/UICC to send the lx SMS message (FIG. 4), an issue arises in that new ME-SIM card interface commands need to be designed so that the UE can trigger the R-UIM/UICC to send the lx SMS message. Both the UE and the R-UIM/UICC would need to be modified to support the triggering. Also, the triggering solution depicted in FIG. 4 would not work for previously existing R-UIMs/UICCs.

[0055] In another example, regarding the UE sending the lx SMS message directly to the information list server without communicating with the R-UIM/UICC (FIG. 5), an issue arises in that current lx SMS messages are configured to be sent by the R- UIM/UICC. Due to the different lx stacks supported in the UE and the R- UIM/UICC, it would be difficult to configure the UE to send the lx SMS message without utilizing the R-UIM/UICC.

[0056] As mentioned above, it is difficult for either the UE or R-UIM/UICC to send lx

SMS messages for sending a status report/acknowledgment of a PRL/preferred PLMN list/MMSS record update. To overcome the above-described issues, in an aspect, the UE may send the status report/acknowledgment of the PRL/preferred PLMN list/MMSS record update via HTTP, or HTTP with XML. XML is a high- level description data structure, amenable to extensions and implementation, and convenient for self-defined parameters (e.g., UE identifier, PRL/preferred PLMN list/MMSS record version, etc.). HTTP with XML is widely used in various Internet services. In another aspect, the UE may send the status report/acknowledgment of the PRL/preferred PLMN list/MMSS record update via an IP packet to a dedicated TCP/UDP port number.

[0057] FIG. 6 is a diagram 600 illustrating a method of updating a preferred information list (e.g., PRL/preferred PLMN list/MMSS record). At step 602, a UE may detect a command to initiate an update of a preferred information list (e.g., PRL/preferred PLMN list/MMSS record). For example, the UE detects the command when a user selects a UE input key or display screen icon initiating the update.

[0058] At step 604, once the update is initiated, the UE may set up a data connection with an information list server (e.g., PRL/preferred PLMN list/MMSS record server). When the data connection is established, the UE may acquire an updated information list version number from the information list server. Notably, whenever the updated preferred information list is updated, the information list server incrementally increases the version number. The UE may also acquire other information, such as cyclic redundancy check (CRC) information. [0059] At step 606, the UE compares an information list version number stored at the

UE with the updated information list version number acquired from the information list server. When the UE determines that the information list stored at the UE is not current with the updated information list stored at the information list server, the UE downloads the updated information list (e.g., updated PRL/preferred PLMN list/MMSS record) from the information list server. In one example, the UE may download the updated information list via a hyper text transport protocol (HTTP).

[0060] At step 608, the UE generates a status report (acknowledgment) without communicating with a R-UIM/UICC inserted in the UE. The status report may indicate whether the update was successful or not (e.g., whether the updated preferred information list was successfully received or not at the UE). Thereafter, the UE sends the status report to the information list server. In one example, the UE sends the status report via an HTTP POST message or a 200 OK message. The sent message may utilize XML and include at least one UE international mobile security identity (IMSI) associated with the updated preferred information list, an indication of whether the updated preferred information list was successfully received by the UE, a preferred information list version number currently stored at the UE, and/or an electronic serial number (ESN) or a mobile equipment identifier (MEID) of the UE, wherein the ESN or MEID is associated with the at least one UE IMSI. In an example, the indication of whether the updated preferred information list was successfully received may be a 1-bit signal, wherein a "0" value corresponds to a successful update and a "1" value corresponds to a failed update.

[0061] The algorithm below depicts an exemplary algorithm for sending the status report/acknowledgment via an HTTP POST message.

HTTP PRL/PLMN/MMSS version Notify from UE

POST /PRL_PLMN_MMSSlistinfo HTTP/1.1

Host: PRL_PLMN_MMSS Roaming List Server IP address or FQDN

Content-Type: application/PRL_PLMN_MMSSlist+XML

Content- Length:nnn

<?xml version="1.0"?>

<IMSI1>XXXXXX</IMSI1> <Current_PLMN_version>current PLMN list version</Current_PLMN_version> <IMSI2>XXXXXX</IMSI2>

<Current_PRL_version>current PRL list version </Current_PRL_version> <IMSI3>XXXXXX</IMSI3>

<Current_MMSS_version>current MMSS list version </Current_MMSS_version>

<MEID>XXXXXX</MEID>

<ESN>XXXXXX</ESN>

<PLMNListUpdate_result>resultvalue</PLMNListUpdate_result>

<PRLListUpdate_result>resultvalue</PRLListUpdate_result>

<MMSSListUpdate_result>resultvalue</MMSSListUpdate_result>

</request>

</PreferredPRL_PLMN_MMSSList>

[0062] FIG. 7 is a diagram 700 illustrating a method of updating a preferred information list (e.g., PRL/preferred PLMN list/MMSS record). At step 702, a UE may detect a command to initiate an update of an information list (e.g., PRL/preferred PLMN list/MMSS record). For example, the UE detects the command when a user selects a UE input key or display screen icon initiating the update.

[0063] At step 704, once the update is initiated, the UE may set up a data connection with an information list server (e.g., PRL/preferred PLMN list/MMSS record server). When the data connection is established, the UE may acquire an updated preferred information list version number from the information list server. Notably, whenever the updated preferred information list is updated, the information list server incrementally increases the version number. The UE may also acquire other information, such as cyclic redundancy check (CRC) information.

[0064] At step 706, the UE compares a preferred information list version number stored at the UE with the updated preferred information list version number acquired from the information list server. When the UE determines that the preferred information list stored at the UE is not current with the updated preferred information list stored at the information list server, the UE downloads the updated preferred information list (e.g., updated PRL/preferred PLMN list/MMSS record) from the information list server. In one example, the UE may download the updated preferred information list via a hyper text transport protocol (HTTP). [0065] At step 708, the UE generates a status report (acknowledgment) without communicating with a R-UIM/UICC inserted in the UE. The status report may indicate whether the update was successful or not (e.g., whether the updated preferred information list was successfully received or not at the UE). Thereafter, the UE sends the status report to the information list server. In one example, the UE sends the status report via an Internet protocol (IP) packet. The IP packet may be sent to a destination having a transport control protocol (TCP) port number or a user datagram protocol (UDP) port number dedicated to receiving status information. The IP packet may include a source IP address (e.g., IP address of the UE), a destination IP address (e.g., IP address of the information list server), a destination TCP/UDP port number (which may be dedicated to receiving status information), a UE identifier (e.g., at least one UE international mobile security identity (IMSI) associated with the updated preferred information list), an indication of whether the updated preferred information list was successfully received by the UE, a preferred information list version number currently stored at the UE, and/or an electronic serial number (ESN) or a mobile equipment identifier (MEID) of the UE, wherein the ESN or MEID associated with the at least one UE EVISI. In an example, the indication of whether the updated preferred information list was successfully received may be a 1-bit signal, wherein a "0" value corresponds to a successful update and a "1" value corresponds to a failed update.

[0066] FIG. 8 is a flow chart 800 of a method of wireless communication. The method may be performed by a UE. At step 802, the UE detects an update of a preferred information list. For example, the preferred information list may be a preferred roaming list (PRL), a preferred public land mobile network (PLMN) list, or a multimode system selection (MMSS) record. In an aspect, the update may be detected by the UE when a user inputs a command into the UE.

[0067] At step 804, when the update is detected, the UE connects to an information list server (e.g., PRL/preferred PLMN list/MMSS record server). Thereafter, at step 806, the UE determines whether a preferred information list stored at the UE is current with an updated preferred information list stored at the information list server. For example, the UE may perform the determination by comparing a version number of the preferred information list stored at the UE with a version number of the updated preferred information list stored at the information list server. Based on a positive result at step 806, the UE may end the update operation as the UE possesses the most current preferred information list. However, based on a negative result at step 806, the UE may proceed to step 808.

At step 808, the UE receives the updated preferred information list from the information list server. For example, the UE may receive the updated preferred information list by downloading the updated preferred information list from the information list server via HTTP.

At step 810, the UE sends a status of the update to the information list server. The status of the update may include an indication of whether the updated preferred information list was successfully received.

In an aspect, the UE sends the status of the update via an HTTP POST message and/or a 200 OK message. The HTTP POST message and/or 200 OK message may include at least one UE international mobile security identity (IMSI) associated with the updated preferred information list, an indication of whether the updated preferred information list was successfully received, a preferred information list version number currently stored at the UE, and/or an electronic serial number (ESN) or a mobile equipment identifier (MEID) of the UE, wherein the ESN or MEID is associated with the at least one UE IMSI.

In another aspect, the UE sends the status of the update via an Internet protocol (IP) packet. The IP packet may be sent to a destination having a transport control protocol (TCP) port number or a user datagram protocol (UDP) port number dedicated to receiving status information. The IP packet may include an IP address of the UE, an IP address of the information list server, a destination TCP/UDP port number, at least one UE international mobile security identity (IMSI) associated with the updated preferred information list, an indication of whether the updated preferred information list was successfully received, a preferred information list version number currently stored at the UE, and/or an electronic serial number (ESN) or a mobile equipment identifier (MEID) of the UE, wherein the ESN or MEID is associated with the at least one UE IMSI.

FIG. 9 is a conceptual data flow diagram 900 illustrating the data flow between different modules/means/components in an exemplary apparatus 902. The apparatus may be a UE. The apparatus includes a receiving module 904, an update module 906, a connection module 908, a memory 910, and a transmission module 912.

The update module 906 detects an update of a preferred information list. For example, the preferred information list may be a preferred roaming list (PRL), a preferred public land mobile network (PLMN) list, or a multimode system selection(MMSS) record. In an aspect, the update module 906 may detect that an update is initiated when a user inputs a command into the apparatus 902.

When the update is detected, the connection module 908 is prompted to set up a data connection with an information list server (e.g., PRL/preferred PLMN list/MMSS record server) 950. The information list server 950 may be accessed through the transmission module 912 via an eNB (not shown), for example. Thereafter, the update module 906 determines whether a preferred information list stored in the memory 910 is current with an updated preferred information list stored at the information list server 950. For example, the update module 906 may perform the determination by comparing a version number of the preferred information list stored in the memory 910 with a version number of the updated preferred information list received (via the receiving module 904) from the information list server 950. Based on a positive result of the determination, the update module 906 may end the update operation as the memory 910 possesses the most current preferred information list. However, based on a negative result of the determination, the update module may proceed with the update operation.

As the update proceeds, the update module 906 receives (via the receiving module 904) the updated preferred information list from the information list server 950. For example, the update module 906 may receive the updated preferred information list by downloading the updated preferred information list from the information list server 950 via HTTP.

The update module 906 may also send (via the transmission module 912) a status of the update to the information list server 950. The status of the update may include an indication of whether the updated preferred information list was successfully received.

In an aspect, the update module 906 sends the status of the update via an HTTP POST message and/or a 200 OK message. The HTTP POST message and/or 200 OK message may include at least one international mobile security identity (IMSI) of the apparatus 902 associated with the updated preferred information list, an indication of whether the updated preferred information list was successfully received, a preferred information list version number currently stored in the memory 910, and/or an electronic serial number (ESN) or a mobile equipment identifier (MEID) of the apparatus 902, wherein the ESN or MEID is associated with the at least one IMSI.

[0078] In another aspect, the update module 906 sends the status of the update via an

Internet protocol (IP) packet. The IP packet may be sent to a destination having a transport control protocol (TCP) port number or a user datagram protocol (UDP) port number dedicated to receiving status information. The IP packet may include an IP address of the apparatus 902, an IP address of the information list server 950, a destination TCP/UDP port number, at least one international mobile security identity (IMSI) of the apparatus 902 associated with the updated preferred information list, an indication of whether the updated preferred information list was successfully received, a preferred information list version number currently stored in the memory 910, and/or an electronic serial number (ESN) or a mobile equipment identifier (MEID) of the apparatus 902, wherein the ESN or MEID is associated with the at least one IMSI.

[0079] The apparatus may include additional modules that perform each of the steps of the algorithm in the aforementioned flow charts of FIGs. 4-8. As such, each step in the aforementioned flow charts of FIGs. 4-8 may be performed by a module and the apparatus may include one or more of those modules. The modules may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by a processor configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by a processor, or some combination thereof.

[0080] FIG. 10 is a diagram 1000 illustrating an example of a hardware implementation for an apparatus 902' employing a processing system 1014. The processing system 1014 may be implemented with a bus architecture, represented generally by the bus 1024. The bus 1024 may include any number of interconnecting buses and bridges depending on the specific application of the processing system 1014 and the overall design constraints. The bus 1024 links together various circuits including one or more processors and/or hardware modules, represented by the processor 1004, the modules 904, 906, 908, 910, 912 and the computer-readable medium 1006. The bus 1024 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described any further. [0081] The processing system 1014 may be coupled to a transceiver 1010. The transceiver 1010 is coupled to one or more antennas 1020. The transceiver 1010 provides a means for communicating with various other apparatus over a transmission medium. The transceiver 1010 receives a signal from the one or more antennas 1020, extracts information from the received signal, and provides the extracted information to the processing system 1014, specifically the receiving module 904. In addition, the transceiver 1010 receives information from the processing system 1014, specifically the transmission module 912, and based on the received information, generates a signal to be applied to the one or more antennas 1020. The processing system 1014 includes a processor 1004 coupled to a computer-readable medium 1006. The processor 1004 is responsible for general processing, including the execution of software stored on the computer-readable medium 1006. The software, when executed by the processor 1004, causes the processing system 1014 to perform the various functions described supra for any particular apparatus. The computer-readable medium 1006 may also be used for storing data that is manipulated by the processor 1004 when executing software. The processing system further includes at least one of the modules 904, 906, 908, 910, and 912. The modules may be software modules running in the processor 1004, resident/stored in the computer readable medium 1006, one or more hardware modules coupled to the processor 1004, or some combination thereof. The processing system 1014 may be a component of the UE 350 and may include the memory 360 and/or at least one of the TX processor 368, the RX processor 356, and the controller/processor 359.

[0082] In one configuration, the apparatus 902/902' for wireless communication includes means for detecting an update of a preferred information list, means for connecting to an information list server when the update is detected, means for determining that a preferred information list stored at the UE is not current with an updated preferred information list stored at the information list server, means for receiving the updated preferred information list from the information list server, and means for sending a status of the update to the information list server.

[0083] The aforementioned means may be one or more of the aforementioned modules of the apparatus 902 and/or the processing system 1014 of the apparatus 902' configured to perform the functions recited by the aforementioned means. As described supra, the processing system 1014 may include the TX Processor 368, the RX Processor 356, and the controller/processor 359. As such, in one configuration, the aforementioned means may be the TX Processor 368, the RX Processor 356, and the controller/processor 359 configured to perform the functions recited by the aforementioned means.

[0084] It is understood that the specific order or hierarchy of steps in the processes disclosed is an illustration of exemplary approaches. Based upon design preferences, it is understood that the specific order or hierarchy of steps in the processes may be rearranged. Further, some steps may be combined or omitted. The accompanying method claims present elements of the various steps in a sample order, and are not meant to be limited to the specific order or hierarchy presented.

[0085] The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but is to be accorded the full scope consistent with the language claims, wherein reference to an element in the singular is not intended to mean "one and only one" unless specifically so stated, but rather "one or more." Unless specifically stated otherwise, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C," "at least one of A, B, and C," and "A, B, C, or any combination thereof include any combination of A, B, and/or C, and may include multiples of A, multiples of B, or multiples of C. Specifically, combinations such as "at least one of A, B, or C," "at least one of A, B, and C," and "A, B, C, or any combination thereof may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, where any such combinations may contain one or more member or members of A, B, or C. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. No claim element is to be construed as a means plus function unless the element is expressly recited using the phrase "means for."

WHAT IS CLAIMED IS:

Claims

1. A method of wireless communication at a user equipment (UE), comprising:

detecting an update of a preferred information list;

connecting to an information list server when the update is detected;

determining that a preferred information list stored at the UE is not current with an updated preferred information list stored at the information list server;

receiving the updated preferred information list from the information list server; and

sending a status of the update to the information list server.

2. The method of claim 1, wherein the preferred information list is at least one of a preferred roaming list (PRL), a preferred public land mobile network (PLMN) list, or a multimode system selection (MMSS) record.

3. The method of claim 1, wherein the sending the status of the update comprises sending the status via at least one of an HTTP POST message or a 200 OK message.

4. The method of claim 3, wherein the HTTP POST message or 200 OK message comprises at least one of:

at least one UE international mobile security identity (IMSI) associated with the updated preferred information list;

an indication of whether the updated preferred information list was successfully received;

a preferred information list version number currently stored at the UE; or an electronic serial number (ESN) or a mobile equipment identifier (MEID) of the UE, the ESN or MEID associated with the at least one UE IMSI.

5. The method of claim 1, wherein the sending the status of the update comprises sending the status via an Internet protocol (IP) packet.

6. The method of claim 5, wherein the IP packet is sent to a destination having a transport control protocol (TCP) port number or a user datagram protocol (UDP) port number dedicated to receiving status information.

7. The method of claim 6, wherein the IP packet comprises at least one of: an IP address of the UE;

an IP address of the information list server;

a destination TCP/UDP port number;

8. The method of claim 1, wherein the status of the update comprises an indication of whether the updated preferred information list was successfully received.

9. The method of claim 1, wherein the update is detected via a user inputting a command into the UE.

10. The method of claim 1, wherein the receiving the updated preferred information list comprises downloading the updated preferred information list from the information list server via HTTP.

11. A user equipment (UE), comprising:

means for detecting an update of a preferred information list;

means for connecting to an information list server when the update is detected; means for determining that a preferred information list stored at the UE is not current with an updated preferred information list stored at the information list server; means for receiving the updated preferred information list from the information list server; and

means for sending a status of the update to the information list server.

12. The UE of claim 11, wherein the preferred information list is at least one of a preferred roaming list (PRL), a preferred public land mobile network (PLMN) list, or a multimode system selection (MMSS) record.

13. The UE of claim 11, wherein the means for sending the status of the update is configured to send the status via at least one of an HTTP POST message or a 200 OK message.

14. The UE of claim 13, wherein the HTTP POST message or 200 OK message comprises at least one of:

15. The UE of claim 11, wherein the means for sending the status of the update is configured to send the status via an Internet protocol (IP) packet.

16. The UE of claim 15, wherein the IP packet is sent to a destination having a transport control protocol (TCP) port number or a user datagram protocol (UDP) port number dedicated to receiving status information.

17. The UE of claim 16, wherein the IP packet comprises at least one of: an IP address of the UE;

an IP address of the information list server;

a destination TCP/UDP port number;

18. The UE of claim 11, wherein the status of the update comprises an indication of whether the updated preferred information list was successfully received.

19. The UE of claim 11, wherein the update is detected via a user inputting a command into the UE.

20. The UE of claim 11, wherein the means for receiving the updated preferred information list is configured to download the updated preferred information list from the information list server via HTTP.

21. A user equipment (UE), comprising:

a processing system configured to:

detect an update of a preferred information list;

connect to an information list server when the update is detected;

determine that a preferred information list stored at the UE is not current with an updated preferred information list stored at the information list server;

receive the updated preferred information list from the information list server; and

send a status of the update to the information list server.

22. The UE of claim 21, wherein the preferred information list is at least one of a preferred roaming list (PRL), a preferred public land mobile network (PLMN) list, or a multimode system selection (MMSS) record.

23. The UE of claim 21, wherein the processing system configured to send the status of the update is configured to send the status via at least one of an HTTP POST message or a 200 OK message.

24. The UE of claim 23, wherein the HTTP POST message or 200 OK message comprises at least one of:

25. The UE of claim 21, wherein the processing system configured to send the status of the update is configured to send the status via an Internet protocol (IP) packet.

26. The UE of claim 25, wherein the IP packet is sent to a destination having a transport control protocol (TCP) port number or a user datagram protocol (UDP) port number dedicated to receiving status information.

27. The UE of claim 26, wherein the IP packet comprises at least one of: an IP address of the UE;

an IP address of the information list server;

a destination TCP/UDP port number; at least one UE international mobile security identity (IMSI) associated with the updated preferred information list;

28. The UE of claim 21, wherein the status of the update comprises an indication of whether the updated preferred information list was successfully received.

29. The UE of claim 21, wherein the update is detected via a user inputting a command into the UE.

30. The UE of claim 21, wherein the processing system configured to receive the updated preferred information list is configured to download the updated preferred information list from the information list server via HTTP.

31. A computer program product, comprising:

a computer-readable medium comprising code for:

detecting an update of a preferred information list;

connecting to an information list server when the update is detected;

determining that a preferred information list stored at a user equipment (UE) is not current with an updated preferred information list stored at the information list server;

sending a status of the update to the information list server.

32. The computer program product of claim 31, wherein the preferred information list is at least one of a preferred roaming list (PRL), a preferred public land mobile network (PLMN) list, or a multimode system selection (MMSS) record.

33. The computer program product of claim 31, wherein the code for sending the status of the update is configured to send the status via at least one of an HTTP POST message or a 200 OK message.

34. The computer program product of claim 33, wherein the HTTP POST message or 200 OK message comprises at least one of:

35. The computer program product of claim 31, wherein the code for sending the status of the update is configured to send the status via an Internet protocol (IP) packet.

36. The computer program product of claim 35, wherein the IP packet is sent to a destination having a transport control protocol (TCP) port number or a user datagram protocol (UDP) port number dedicated to receiving status information.

37. The computer program product of claim 36, wherein the IP packet comprises at least one of:

an IP address of the UE;

an IP address of the information list server;

38. The computer program product of claim 31, wherein the status of the update comprises an indication of whether the updated preferred information list was successfully received.

39. The computer program product of claim 31, wherein the update is detected via a user inputting a command into the UE.

40. The computer program product of claim 31, wherein the code for receiving the updated preferred information list is configured to download the updated preferred information list from the information list server via HTTP.