Where is prl stored on phone

Free phones. My offers. Fios Home Internet. Bring your own device. Certified pre-owned. Featured smartphones. Other phones.

Trade in your device. Shop all accessories. Phone accessories. Tablet accessories. Watch accessories. Shop all plans. Shared data. International services. Connected devices. Those who serve. Kids plans. Student plans. Other plans. Shop all home solutions. LTE Home Internet. Fios TV. Prepaid overview.

Shop all entertainment. Apple Arcade. Google Play Pass. Apple Music. YouTube TV. Financial services. Why Verizon. Why Verizon overview. Wireless coverage map. Network awards. Global coverage. Get more. Verizon Up. Device protection. Verizon Cloud. Health discounts. Social impact. Support Support Support Close. Support overview. Mobile support overview. The server could reuse this data information if updates are those stored in this file.

In this embodiment, the operator would only have to send a command including a "commit" command without data information updates. This avoids the server to download a new time data information updates over the air. Each file could be used in target regions where the operator has agreement with a respective partners list.

These files could be loaded during personalization step or later. This solution could permit the operator to download data information updates one time. In particular, the data processing system is a SIM card of a mobile phone and said files comprise preferred roaming list, PRL.

The present invention relates generally to handling roaming lists in a wireless communication system, and more specifically to updating a preferred roaming list PRL Preferred Roaming List. These two documents are incorporated by reference to the description. The relevant files are described in the [S] specification. It lists the frequency bands the phone can use in various parts of a country. This is a process of provisioning mobile station operational parameters over the air interface.

So, a list PRL is stored in a temporary storage until reception of a "commit" command received from the server requesting the PRL list update.

When the server sends a 'Commit APDU', all the data stored in said temporary storage is copied into the file EF prl file itself in a permanent memory.

The process is very long due to limited resources in the smart card. The problem becomes worse as the size of the PRL increases. Today, the size of a PRL update is about bytes. When the PRL is of a greater size, the processor of the card is engaged in an update process for a long period of time.

This is unacceptable in a GSM context as it is stated that each command should take no longer than 2 seconds in order to allow 'authentication' during a session. So, the step of updating the PRL list is largely reduced in time. In our example, this time is reduced to the time of modifying the file header.

Card and ME actions. Figure 3 is a view of a part of a file storing a list of partners PRL; Figure 4 is a view of a part of a file storing a list of partners PRL, this file being updates and being stored in said permanent memory according to the invention. In our example, this server is the home network operator. Downloading can be performed for example by means of over the air OTA technics.

This list is stored in a file EF prl which can be updated. The structure of EF prl includes parameters blocks. In our example, parameters blocks are: A file ID block defines the file name. A file ID is used to address or identify each specific file. In our example this file ID includes two bytes. Access conditions block defining access rights on Read command, Update command, Invalidate command, Rehabilitate command.

The Access conditions are set for administrator use only. For the correct vocabulary, and the correct structure, we will refer to the above-identified standards, which will define exactly the additional blocks. The only person allowed to use this file is the administrator ADM.