Universal Integrated Circuit Card (UICC) Phonebook Access
By detecting the UICC's basic file change counter to be readable but not writeable and skipping the synchronization process, using abbreviated dialing number to perform update requests, the problem of UICC blocking phonebook synchronization is solved, and the phonebook for mobile devices is realized Updates and maintenance.
Patent Information
- Application Number
- CN202080093450.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-01-19
- Publication Date
- 2024-12-13
- Estimated Expiration
- 2040-01-19
AI Technical Summary
The problematic universal integrated circuit card (UICC) may not complete the synchronization process when updating the phone book, resulting in the user being unable to add, update, or delete phone book entries.
By detecting the UICC's base file change counter (EFCC) to be readable but not writeable, and skipping the phonebook synchronization process, an abbreviated dial number (EFADN) is used to perform requests to add, delete, or update phonebook contacts.
Solve the problem of UICC preventing phone book synchronization in problematics, and realizes updating and maintaining mobile phone books to ensure that users can manage phone book contacts normally.
Smart Images

Figure CN114982212B_ABST
Abstract
Description
Technical Field
[0001] The present disclosure generally relates to methods and systems for accessing network services on a wireless device. More specifically, the present disclosure relates to accessing a phonebook of a problematic Universal Integrated Circuit Card (UICC) of a device. Background Art
[0002] Some designs of mobile communication devices / wireless devices (e.g., smartphones, tablet computers, and laptop computers) include a single Universal Integrated Circuit Card (UICC), multiple Universal Integrated Circuit Cards, or multiple Subscriber Identity Module (SIM) cards. These cards store user identity information and multiple subscriptions, which enables users to access multiple separate mobile phone networks. Some of the UICCs (e.g., embedded UICCs (eUICCs)) can support remote provisioning of network subscription information. The UICC may be removable or may be implemented in the memory of the mobile communication device.
[0003] The information stored in the UICC enables the mobile communication device to communicate with a variety of different types of mobile phone networks. Examples of mobile phone networks include third generation (3G), fourth generation (4G), long term evolution (LTE), fifth generation (5G), time division multiple access (TDMA), code division multiple access (CDMA), CDMA 2000, wideband CDMA (WCDMA), global system for mobile communications (GSM), single carrier radio transmission technology (1xRTT) and universal mobile telecommunications system (UMTS). The UICC can store the phone book of the user of the mobile communication device. However, in a problematic UICC, updates to the phone book may not be completed. Summary of the invention
[0004] A method for updating a phonebook in a universal integrated circuit (UICC) of a mobile equipment (ME) is described. The method comprises updating an elementary file (EF) change counter (EF) of the UICC of the ME. CC ) is detected as readable but not writable. This detection is performed in response to a request from a user of the ME to add / delete / update a phonebook contact. The method also includes skipping a phonebook synchronization process of the UICC. The method also includes writing an elementary file (EF) abbreviated dialing number (EF ADN ) to perform a request to add / delete / update a phonebook contact.
[0005] A device for updating a phone book in a universal integrated circuit card (UICC) of a mobile equipment (ME) is described. The device comprises a device for updating an elementary file (EF) change counter (EF) of the UICC of the ME. CC) as a component that can be read but not written. This detection is performed in response to a request from a user of the ME to add / delete / update a phonebook contact. The apparatus also includes a component for skipping a phonebook synchronization process of the UICC. The apparatus also includes a component for writing an elementary file (EF) abbreviated dialing number (EF) to the UICC ADN ) to execute requests to add / delete / update phonebook contacts.
[0006] An apparatus for updating a phonebook in a universal integrated circuit card (UICC) of a mobile equipment (ME) is described. The apparatus comprises a memory coupled to a communication interface of the UICC of the ME and a processor (or processors). The processor (or processors) are coupled to the memory and the communication interface of the UICC of the ME. The processor (or processors) are configured to update an elementary file (EF) change counter (EF) of the UICC of the ME. CC ) as readable but not writable. This detection is performed in response to a request from a user of the ME to add / delete / update phonebook contacts. The processor(s) are further configured to skip the phonebook synchronization process of the UICC. The processor(s) are further configured to write an elementary file (EF) abbreviated dialing number (EF ADN ) to perform a request to add / delete / update a phonebook contact.
[0007] This is a fairly broad overview of the features and technical advantages of the present disclosure so that the following detailed description may be better understood. Additional features and advantages of the present disclosure will be described below. It will be appreciated by those skilled in the art that the present disclosure may be easily used as a basis for modifying or designing other structures for performing the same purpose of the present disclosure. It will also be appreciated by those skilled in the art that such equivalent constructions do not depart from the teachings of the present disclosure as set forth in the appended claims. The novel features and further objects and advantages that are considered to be characteristic of the present disclosure in terms of both the organization and the method of operation of the present disclosure will be better understood from the following description when considered in conjunction with the accompanying drawings. However, it is to be clearly understood that each of the accompanying drawings is provided for the purpose of illustration and description only and is not intended to be a definition of the limitations of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS
[0008] For a more complete understanding of the present disclosure, reference is now made to the following description taken in conjunction with the accompanying drawings.
[0009] Figure 1 A wireless device in communication with a wireless communication system is shown.
[0010] Figure 2 According to one aspect of the present disclosure, Figure 1 Block diagram of a wireless device in FIG.
[0011] Figure 3 is a process flow diagram of a method of updating a phonebook within a problematic universal integrated circuit card (UICC) of a mobile equipment (ME) according to aspects of the present disclosure.
[0012] Figure 4 is a process flow diagram of another method of updating a phonebook within a problematic universal integrated circuit card (UICC) of a mobile equipment (ME) according to aspects of the present disclosure.
[0013] Figure 5 is a component block diagram of a wireless device suitable for implementing a method for updating a phonebook within a problematic Universal Integrated Circuit Card (UICC) of the device in accordance with aspects of the present disclosure.
[0014] Figure 6 is a block diagram illustrating an exemplary wireless communication system in which configurations of the present disclosure may be advantageously employed. DETAILED DESCRIPTION
[0015] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configuration in which the concepts described herein can be practiced. The detailed description includes specific details to provide a comprehensive understanding of the various concepts. However, it is apparent to those skilled in the art that these concepts can be practiced without these specific details. In some cases, well-known structures and components are shown in the form of block diagrams to avoid making such concepts difficult to understand. As described herein, the use of the term "and / or" is intended to represent an "inclusive OR", and the use of the term "or" is intended to represent an "exclusive OR".
[0016] The terms "Subscriber Identity Module", "SIM", "Universal Subscriber Identity Module", "USIM", "User Identity Module", "UIM", "Removable User Identity Module" and "RUIM" are used herein to refer to a memory, which may be an integrated circuit or embedded in a removable card, that stores an International Mobile Subscriber Identity (IMSI), related keys and / or other information used to identify and / or authenticate a wireless device on a network. In some networks (e.g., GSM networks), a SIM may store network-specific information used to authenticate and identify a subscriber on the network, the most important of which are the Integrated Circuit Card Identifier (ICCID), the International Mobile Subscriber Identity (IMSI), the Authentication Key (Ki) and the Local Area Identity (LAI). The SIM may also store other operator-specific data, such as the Short Message Service Center (SMSC) number, the Service Provider Name (SPN), the Service Dialing Number (SDN) and Value Added Service (VAS) applications. In various aspects, the USIM and RUIM may be modules in UMTS and CDMA networks, respectively, that provide equivalent functionality to the SIM in a GSM network. However, the terms "SIM," "USIM," and "RUIM" may be used interchangeably to refer to a general module that is not limited to a specific standard or technology.
[0017] The term "SIM" may also be used as a shorthand reference to a communication network associated with a specific SIM, as the information stored in the SIM enables a wireless device to establish a communication link with a specific network. Thus, the SIM and the communication network, and the services and subscriptions supported by the network, are related to each other.
[0018] The terms "smart card", "SIM card", "Universal Integrated Circuit Card" and "UICC" are used interchangeably to refer to a memory chip or integrated circuit used to provide a SIM, USIM and / or RUIM to a wireless device to store the described provisioning and / or other data. Various UICCs may have storage capabilities ranging from 2 to 3 kilobytes up to 1 gigabyte of information.
[0019] The Universal Integrated Circuit Card (UICC) securely stores the phonebook for users of mobile communication devices such as Mobile Equipment (ME). The UICC can perform a phonebook synchronization procedure in response to a user request to update / delete an existing phonebook entry or to add a new phonebook entry. The user request triggers the UICC to update the Elementary File (EF) change counter (EF CC ), as part of the phonebook synchronization process. Although readable, a problematic UICC can prevent access to the EF CCThe update of the mobile device causes the phonebook synchronization process to fail and prevents the user from adding, updating or deleting phonebook entries. According to aspects of the present disclosure, the modified phonebook update process compensates for a problematic (eg, erroneous) UICC of the mobile device.
[0020] Figure 1 A wireless device 110 is shown, which includes a disclosed update of a phone book within a problematic universal integrated circuit card (UICC) of a mobile equipment (ME). The wireless device 110 communicates with a wireless communication system 120. The wireless device 110 includes a multi-band (e.g., dual-band) concurrent millimeter wave (mmW) transceiver. The wireless communication system 120 may be a 5G system, a long term evolution (LTE) system, a code division multiple access (CDMA) system, a global system for mobile communications (GSM), a wireless local area network (WLAN) system, millimeter wave (mmW) technology, or some other wireless system. The CDMA system may implement Wideband CDMA (WCDMA), Time Division Synchronous CDMA (TD-SCDMA), CDMA2000, or some other version of CDMA. In a millimeter wave (mmW) system, multiple antennas are used for beamforming (e.g., in the range of 30 GHz, 60 GHz, etc.). For simplicity, Figure 1 A wireless communication system 120 is shown that includes two base stations 130 and 132 and a system controller 140. In general, a wireless system may include any number of base stations and any number of network entities.
[0021] The wireless device 110 may be referred to as a mobile equipment (ME), a user equipment (UE), a mobile station, a terminal, an access terminal, a subscriber unit, a station, etc. The wireless device 110 may also be a cellular phone, a smart phone, a tablet computer, a wireless modem, a personal digital assistant (PDA), a handheld device, a laptop computer, a smartbook, a netbook, a cordless phone, a wireless local loop (WLL) station, a Bluetooth device, etc. The wireless device 110 may be capable of communicating with the wireless communication system 120. The wireless device 110 may also be capable of receiving signals from a broadcast station (e.g., the broadcast station 134), signals from satellites in one or more global navigation satellite systems (GNSS) (e.g., satellite 150), etc. The wireless device 110 may support one or more radio technologies for wireless communications such as 5G, LTE, CDMA2000, WCDMA, TD-SCDMA, GSM, 802.11, etc.
[0022] The wireless device 110 may support carrier aggregation, which is an operation on multiple carriers. Carrier aggregation may also be referred to as multi-carrier operation. According to one aspect of the present disclosure, the wireless device 110 may be able to operate in a low frequency band from 698 megahertz (MHz) to 960MHz, a mid-frequency band from 1475MHz to 2170MHz, and / or a high frequency band from 2300MHz to 2690MHz, an ultra-high frequency band from 3400MHz to 3800MHz, and a long term evolution (LTE) in an LTE unlicensed band (LTE-U / LAA) from 5150MHz to 5950MHz. Low frequency band, mid-frequency band, high frequency band, ultra-high frequency band, and LTE-U refer to five groups of frequency bands (or frequency band groups), each of which includes several frequency bands (or simply referred to as "frequency bands"). For example, in some systems, each frequency band can cover up to 200MHz and can include one or more carriers. For example, in LTE, each carrier can cover up to 40MHz. Of course, the range of each frequency band is merely exemplary and non-limiting, and other frequency ranges may be used. LTE Release 11 supports 35 frequency bands, which are referred to as LTE / UMTS bands and are listed in 3GPP TS 36.101. In LTE Release 11, wireless device 110 may be configured with up to five carriers in one or two frequency bands.
[0023] Figure 2 According to one aspect of the present disclosure, Figure 1 The wireless device 110 may include a universal integrated circuit card (UICC) interface 202 that may receive an embedded UICC (eUICC) 204 that stores profiles associated with one or more subscriptions from a network provider.
[0024] The UICC used in various examples may include user account information, an International Mobile Subscriber Identity (IMSI), a set of SIM Application Toolkit (SAT) commands, and storage space for phonebook contacts. The UICC may also store home identifiers (e.g., system identification number (SID) / network identification number (NID) pairs, home preferred list of mobile networks (HPLMN) codes, etc.) to indicate each subscribed network operator provider of the UICC. An integrated circuit card identity (ICCID) SIM serial number may be printed on the UICC for identification. In some aspects, the UICC may be implemented within a portion of the memory of the wireless device 110 (e.g., in the memory 214), and thus no separate or removable circuit, chip, or card is required.
[0025] The wireless device 110 may include at least one controller, such as a general purpose processor 206, which may be coupled to a coder / decoder (CODEC) 208. The CODEC 208, in turn, may be coupled to a speaker 210 and a microphone 212. The general purpose processor 206 may also be coupled to a memory 214. The memory 214 may be a non-transitory computer-readable storage medium that stores processor-executable instructions. The memory 214 may store an operating system (OS) and user application software and executable instructions. The memory 214 may also locally store cached profiles of subscriptions supported by the eUICC 204.
[0026] The general processor 206 and the memory 214 may each be coupled to at least one baseband processor or baseband modem processor 216. The eUICC 204 in the wireless device 110 may utilize one or more baseband-RF resources. The baseband-RF resources may include a baseband modem processor 216, which may perform baseband / modem functions to communicate with a radio access technology (RAT) and control the RAT. The baseband-RF resources may include one or more amplifiers and radios, commonly referred to as radio frequency (RF) resources (e.g., RF resources 218). In some examples, the baseband-RF resources may share a baseband modem processor 216 (e.g., a single device that performs baseband / modem functions for all RATs on the wireless device 110). In other examples, each baseband-RF resource may include a physically or logically separate baseband processor (e.g., BB1, BB2).
[0027] The RF resources 218 may be a transceiver that performs transmit / receive functions for the eUICC 204 on the wireless device 110. The RF resources 218 may include separate transmit and receive circuit systems, or may include a transceiver that combines transmitter and receiver functions. In some examples, the RF resources 218 may include multiple receive circuits. The RF resources 218 may be coupled to a wireless antenna (e.g., wireless antenna 220). The RF resources 218 may also be coupled to the baseband modem processor 216.
[0028] In some examples, the general processor 206, memory 214, baseband modem processor(s) 216, and RF resources 218 may be included in the wireless device 110 as a system-on-chip 250. In some examples, the eUICC 204 and its corresponding communication interface (e.g., UICC interface) may be external to the system-on-chip 250. In addition, various input and output devices may be coupled to components, such as interfaces or controllers, on the system-on-chip 250. Exemplary user input components suitable for use in the wireless device 110 may include, but are not limited to, a keypad 224, a touch screen display 226, and a microphone 212.
[0029] In some examples, keypad 224, touch screen display 226, microphone 212, or a combination thereof may perform the function of receiving a request to initiate an outgoing call or receiving a personal identification number. Interfaces may be provided between various devices and modules to implement functions in wireless device 110 to enable communications in the wireless device.
[0030] The eUICC 204, baseband processors BB1, BB2, RF resources 218, and wireless antennas 220 working together may constitute two or more radio access technologies (RATs). For example, the wireless device 110 may be a communication device including a UICC, a baseband processor, and RF resources, and the RF resources are configured to support two different RATs, such as 5G or LTE and GSM. More RATs may be supported on the wireless device 110 by adding multiple RF resources and antennas for connecting to additional mobile networks.
[0031] In some examples (not shown), the wireless device 110 may include, among other things, additional UICCs or SIM cards, UICC or SIM interfaces, multiple RF resources associated with the additional UICCs or SIM cards, and additional antennas for supporting subscription communications with additional mobile networks.
[0032] The eUICC 204 may support multiple mobile network operator profiles or subscription profiles. For example, a user may download multiple profiles to the eUICC 204. Each profile may store static SIM information that is used to support subscriptions with one or more mobile phone networks. Thus, the eUICC 204 may play the role of multiple SIMs, as each SIM supports one profile.
[0033] In various examples, the wireless device 110 can be configured to locally cache one or more subscription profiles associated with or stored in the UICC. The profiles can be cached in the memory 214, a portion of which can be designated as memory for the modem.
[0034] Figure 3 is a process flow diagram of a method 300 for updating a phonebook within a problematic universal integrated circuit card (UICC) of a mobile equipment (ME) according to aspects of the present disclosure. According to aspects of the present disclosure, a modified phonebook update process compensates for a problematic (eg, erroneous) UICC of a mobile equipment.
[0035] At block 302, a mobile device including a subsystem such as a UICC is powered on. For example, a processor of the mobile device (e.g., a baseband processor) powers on the UICC of the mobile device. At block 304, the processor of the wireless device initiates initialization of a phonebook entry within a phonebook of the UICC. At block 306, a determination is made as to whether a UICC phonebook synchronization value is readable. For example, at block 306, the processor determines whether an elementary file (EF) phonebook (P) synchronization counter (EF PSC ), Elementary File (EF) Unique Identifier (EF UID ), Elementary File (EF) Previous Unique Identifier (EF PUID ) and the elementary file (EF) change counter (EF CC ) is readable.
[0036] When the UICC phonebook synchronization value (such as EF PSC EF UID EF PUID EF CC ) is readable, at box 308, the phonebook synchronization support (pb_sync_supported) flag is set to 'yes'. Otherwise, the control flow branches to box 310, in which the pb_sync_supported flag is set to 'no'. At box 312, a request to add / delete / update (one or more) phonebook contacts is received from the user interface (UI) of the mobile device. At box 320, it is determined whether the pb_sync_supported flag is set to 'yes'. If the pb_sync_supported flag is set to 'yes', then at box 330, the basic file (EF) change counter (EF CC ) is writable. When the basic file (EF) changes the counter (EF CC ) is not writable, an alternative UICC phonebook synchronization process is performed in block 322, and the UICC phone synchronization process of block 332 is skipped in block 322. The control flow proceeds to block 334, in which the speed dialing number (EF) of the elementary file (EF) is synchronized. ADN ) performs a write to execute a request to add / delete / update (one or more) phonebook contacts.
[0037] According to aspects of the present disclosure, a modified phonebook update process is implemented by adding blocks 330 and 322 to compensate for a problematic (e.g., erroneous) UICC of a mobile device. Otherwise, when a request to add / delete / update a phonebook contact is triggered from the UI interface at block 312, the EF CC The binary update command is used to update EF in block 334. ADN Previously, mobile devices would traditionally try to convert EF CC The UICC is updated as the first step of the phonebook synchronization at block 332. Conventionally, the problematic UICC will respond to the EF with a '6982' code ("security status not satisfied"). CC In response to the '6982' code, the mobile device conventionally stops the phone synchronization process and does not write EF in block 334. ADN According to this aspect of the present disclosure, the modified phonebook update process for adding new contacts from the UI interface will not fail.
[0038] In this aspect of the disclosure, it is recognized that if phonebook synchronization is supported by the UICC of the mobile device, then EF CC should be readable and writable. However, in traditional fault conditions, EF CC The erroneous card is readable but not writable. As a result, the problematic UICC does not have the ability to support phonebook synchronization. According to other aspects of the present disclosure, in response to a request to add / modify / delete contacts from a UI interface of the mobile device, a modified phonebook update process provides the mobile device with access to the phonebook resident in the erroneous card.
[0039] Figure 4 A simplified flow chart of a method 400 for updating a phonebook in a problematic universal integrated circuit card (UICC) of a mobile equipment (ME) according to aspects of the present disclosure is depicted. At block 402, in response to a request from a user of the ME to add / delete / update phonebook contacts, an elementary file (EF) change counter (EF) of the UICC of the ME is updated. CC ) is detected as readable but not writable. In block 404, the phonebook synchronization process of the UICC is skipped. In block 406, the abbreviated dialing number (EF) of the basic file (EF) of the UICC is ADN ) performs a write to execute a request to add / delete / update a phonebook contact.
[0040] According to another aspect of the present disclosure, an apparatus for updating a phonebook in a problematic universal integrated circuit card (UICC) of a mobile equipment (ME) is described. The apparatus may include a method for updating an elementary file (EF) change counter (EF) of the UICC of the ME in response to a request from a user of the ME to add / delete / update a phonebook contact. CC ) is detected as a component that can be read but not written. The device may include a component for skipping the phonebook synchronization process of the UICC. The device may include a component for writing an elementary file (EF) abbreviated dialing number (EF) of the UICC ADN ) to execute the request to add / delete / update the phonebook contacts. The detection component, skip component and / or write component may be the baseband modem processor 216, the general processor 206 and / or the memory 214. In another aspect, the above components may be any module or device configured to perform the functions described by the above components.
[0041] Figure 5 5 is a block diagram of components of a wireless device 500 suitable for implementing a method for updating a phonebook in a problematic universal integrated circuit card (UICC) of a mobile equipment (ME). Aspects of the present disclosure may be implemented in any of a variety of wireless devices, examples of which (e.g., wireless device 500) are not shown in FIG. Figure 5 The wireless device 500 may be similar to the wireless device 110 and may implement the methods 300 and 400 .
[0042] The wireless device 500 may include a processor 502 coupled to a touch screen controller 504 and an internal memory 506. The processor 502 may be one or more multi-core integrated circuits designated for general or specific processing tasks. The internal memory 506 may be volatile or non-volatile memory, and may also be secure and / or encrypted memory, or non-secure and / or unencrypted memory, or any combination thereof. The touch screen controller 504 and the processor 502 may also be coupled to a touch screen panel 512, such as a resistive sensing touch screen, a capacitive sensing touch screen, an infrared sensing touch screen, etc. In addition, the display of the wireless device 500 need not have touch screen capabilities.
[0043] The wireless device 500 may have one or more cellular network transceivers 508, which are coupled to the processor 502 and one or more antennas 510 and are configured to send and receive cellular communications. The one or more transceivers 508 and one or more antennas 510 may be used together with the above-described circuit system to implement the various example methods described. The wireless device 500 may include one or more UICCs or SIM cards 516, which are coupled to the one or more transceivers 508 and / or the processor 502 and may be configured as described above.
[0044] The wireless device 500 may also include a speaker 514 for providing audio output. The wireless device 500 may also include a housing 520 made of plastic, metal, or a combination of materials, which is used to house all or some of the components discussed herein. The wireless device 500 may include a power supply 522 coupled to the processor 502, such as a disposable battery or a rechargeable battery. The rechargeable battery may also be coupled to a peripheral device connection port to receive a charging current from a source external to the wireless device 500. The wireless device 500 may also include a physical button 524 for receiving user input. The wireless device 500 may also include a power button 526, which is used to turn the wireless device 500 on and off.
[0045] Figure 6 is a block diagram illustrating an exemplary wireless communication system 600 in which the configurations of the present disclosure may be advantageously employed. For purposes of illustration, Figure 6 Three remote units 620, 630, and 650 and two base stations 640 are shown. It will be appreciated that the wireless communication system can have more remote units and base stations. The remote units 620, 630, and 650 include IC devices 625A, 625B, and 625C, which include the disclosed wireless device, which includes a subsystem or a universal integrated circuit card. It will be appreciated that other devices such as base stations, switching equipment, and network equipment may also include the disclosed wireless device. Figure 6 Forward link signals 680 from base station 640 to remote units 620, 630, and 650 and reverse link signals 690 from remote units 620, 630, and 650 to base station 640 are shown.
[0046] exist Figure 6, remote unit 620 is shown as a mobile phone, remote unit 630 is shown as a portable computer, and remote unit 650 is shown as a fixed location remote unit in a wireless local loop system. For example, the remote unit may be a mobile phone, a handheld personal communication system (PCS) unit, a portable data unit (such as a personal digital assistant (PDA)), a GPS-enabled device, a navigation device, a set-top box, a music player, a video player, an entertainment unit, a fixed location data unit (such as a meter reading device), or other communication device that stores or retrieves data or computer instructions, or a combination thereof. Although Figure 6 Remote units according to aspects of the present disclosure are illustrated, but the present disclosure is not limited to these exemplary illustrated units.Aspects of the present disclosure may be suitably employed in many devices, including wireless devices.
[0047] For firmware and / or software implementations, the methods can be implemented with modules (e.g., processes, functions, etc.) that perform the functions described herein. A machine-readable medium that tangibly contains instructions can be used to implement the methods described herein. For example, software code can be stored in a memory and executed by a processor unit. The memory can be implemented within a processor unit or outside a processor unit. As used herein, the term "memory" refers to a type of long-term, short-term, volatile, non-volatile, or other memory, and is not limited to a specific type of memory or the amount of memory, or the type of medium on which the memory is stored.
[0048] If implemented in firmware and / or software, the function may be stored as one or more instructions or codes on a computer-readable medium. Examples include computer-readable media encoded with a data structure and computer-readable media encoded with a computer program. Computer-readable media include physical computer storage media. The storage medium may be an available medium that a computer can access. For example, but not limited to, such a computer-readable medium may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage device, disk storage device or other magnetic storage device, or other media that can be used to store the required program code in the form of an instruction or data structure and can be accessed by a computer. Disks and optical disks used herein include laser discs (CDs), laser discs, optical disks, digital versatile discs (DVDs), floppy disks, and blue-ray discs, wherein disks typically reproduce data magnetically, while optical disks use lasers to optically reproduce data. Combinations of the above items should also be included within the scope of computer-readable media.
[0049] In addition to storage on a computer-readable medium, instructions and / or data may be provided as signals on a transmission medium included in a communication device. For example, the communication device may include standard cell circuits with signals indicating instructions and data. The instructions and data are configured to cause one or more processors to implement the functions outlined in the claims.
[0050] The various illustrative logical blocks, modules, and circuits described in conjunction with the disclosure herein may be implemented or executed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in combination with a DSP core, or any other such configuration.
[0051] Although the present disclosure and its advantages have been described in detail, it should be understood that various changes, substitutions and modifications can be made herein without departing from the technology of the present disclosure defined in the appended claims. For example, relational terms such as "above" and "below" are used relative to a substrate or electronic device. Of course, if the substrate or electronic device is inverted, the above becomes the below, and vice versa. In addition, if it is oriented laterally, the above and the below can refer to the side of the substrate or electronic device. In addition, the scope of the present application is not limited to the specific configurations of the processes, machines, manufactures and material components, parts, methods and steps described in the specification. As will be easily understood by those of ordinary skill in the art from the present disclosure, according to the present disclosure, processes, machines, manufactures, material components, parts, methods or steps that currently exist or will be developed later can be utilized, which perform substantially the same functions as the corresponding configurations described herein or achieve substantially the same results. Therefore, the appended claims are intended to include such processes, machines, manufactures, material components, parts, methods or steps within their scope.
Claims
1. A method for updating a phone book in a universal integrated circuit card (UICC) of a mobile equipment (ME), include: In response to a request from a user of the ME to add / delete / update a phonebook contact, an EF change counter (EF) of the UICC of the ME is set. CC ) is detected as readable but not writable; Skipping the phonebook synchronization process of the UICC; as well as Write the abbreviated dialing number (EF) of the UICC ADN ) to execute the request to add / delete / update the phonebook contact.
2. The method according to claim 1, wherein writing include: The dialed number is stored in the phonebook of the UICC without performing the phonebook synchronization process.
3. The method according to claim 1, further comprising: CC When readable but not writable, it is determined that phonebook synchronization is not supported by the UICC.
4. The method according to claim 1, further comprising: include: When the UICC phonebook synchronization value is readable, determining that phonebook synchronization is supported by the UICC; as well as When the EF CC When not writable, it is determined that phonebook synchronization is not supported by the UICC. 5 . The method of claim 4 , further comprising setting a phonebook synchronization support flag to positive when phonebook synchronization is supported by the UICC.
6. The method according to claim 1, wherein detecting include: When the UICC phonebook synchronization value is not readable, determining that phonebook synchronization is not supported by the UICC; as well as Skip the EF CC The detection of whether writing is possible. 7 . The method of claim 6 , further comprising setting a phonebook synchronization support flag to negative when phonebook synchronization is not supported by the UICC.
8. The method of claim 6, further comprising storing a dialed number in the phonebook of the UICC without performing the phonebook synchronization process.
9. A device for updating a phone book in a universal integrated circuit card (UICC) of a mobile equipment (ME), include: for changing an Elementary File (EF) counter (EF) of the UICC of the ME in response to a request from a user of the ME to add / delete / update a phonebook contact. CC ) is detected as a component that can be read but not written; means for skipping a phonebook synchronization procedure of said UICC; as well as The abbreviated dialing number (EF) for writing into the UICC ADN ) to execute the requested component to add / delete / update the phonebook contacts.
10. The apparatus of claim 9, wherein the means for writing comprises means for storing a dialed number into the phonebook of the UICC without performing the phonebook synchronization process.
11. The apparatus according to claim 9, further comprising a CC A component that can be read but not written determines that phonebook synchronization is not supported by the UICC.
12. The device according to claim 9, further comprising: include: means for determining that phonebook synchronization is supported by said UICC when a UICC phonebook synchronization value is readable; as well as For when the EF CC Not writable when determining that phonebook synchronization is not supported by the UICC component.
13. The apparatus of claim 12, further comprising means for setting a phonebook synchronization support flag to positive when phonebook synchronization is supported by the UICC.
14. The device according to claim 9, wherein the means for detecting include: means for determining that phonebook synchronization is not supported by said UICC when the UICC phonebook synchronization value is not readable; as well as Used to skip the EF CC The component that detects whether it can be written.
15. The apparatus of claim 14, further comprising means for setting a phonebook synchronization support flag to negative when phonebook synchronization is not supported by the UICC.
16. The apparatus of claim 14, further comprising means for storing a dialed number in the phonebook of the UICC without performing the phonebook synchronization process.
17. A device for updating a phone book in a universal integrated circuit card (UICC) of a mobile equipment (ME), include: Memory; a communication interface coupled to the UICC of the ME; as well as at least one processor coupled to the memory and the communication interface of the UICC of the ME, the at least one processor being configured to: In response to a request from a user of the ME to add / delete / update a phonebook contact, an EF change counter (EF) of the UICC of the ME is set. CC ) is detected as readable but not writable; Skipping the phonebook synchronization process of the UICC; as well as Write the abbreviated dialing number (EF) of the UICC ADN ) to execute the request to add / delete / update the phonebook contact.
18. The apparatus of claim 17, wherein the at least one processor is further configured to store a dialed number in the phonebook of the UICC without performing the phonebook synchronization process.
19. The apparatus of claim 17, wherein the at least one processor is further configured to: When the UICC phonebook synchronization value is readable, determining that phonebook synchronization is supported by the UICC; When phonebook synchronization is supported by the UICC, setting a phonebook synchronization support flag to positive; and When the EF CC When not writable, it is determined that phonebook synchronization is not supported by the UICC.
20. The apparatus of claim 17, wherein the at least one processor is further configured to: When the UICC phonebook synchronization value is not readable, determining that phonebook synchronization is not supported by the UICC; When phonebook synchronization is not supported by the UICC, setting a phonebook synchronization support flag to negative; and Skip the EF CC The detection of whether writing is possible.
