CN112188476B

CN112188476B - Communication method, communication device, mobile terminal, and storage medium

Info

Publication number: CN112188476B
Application number: CN202010942726.2A
Authority: CN
Inventors: 张黄燕; 邓敬贤; 胡剑锋; 张国松
Original assignee: Core Semiconductor Technology Beijing Co ltd
Current assignee: Core Semiconductor Technology Beijing Co ltd
Priority date: 2020-09-09
Filing date: 2020-09-09
Publication date: 2023-04-28
Anticipated expiration: 2040-09-09
Also published as: CN112188476A; WO2022052439A1

Abstract

A communication method, a communication apparatus, a mobile terminal, and a storage medium are disclosed. And when the mobile terminal is started, a plurality of preset USIM data packets and corresponding file identifications are obtained, after a reading operation instruction sent by the functional module is received, the corresponding data packets are directly obtained in the file packets according to the target file identifications in the reading operation instruction, and the data packets corresponding to the target file identifications are sent to the functional module. Therefore, the interaction times between the functional module and the USIM can be reduced, the communication efficiency is improved, and the maintenance is convenient.

Description

Communication method, communication device, mobile terminal, and storage medium

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a communication method, a communication device, a mobile terminal, and a storage medium.

Background

LTE is a long term evolution of the third generation partnership project (3GPP,3rd Generation Partnership Project) dominant mobile communication system (UMTS, universal Mobile Telecommunications System) technology, which is an overage of 3G and 4G technologies. NB-IoT (Narrow Band Internet of Things ) is an important branch of the internet of everything. The NB-IoT is built in a cellular network, consumes only about 180kHz bandwidth, and can be directly deployed in a GSM (Global System for Mobile Communications ) network, a UMTS network or an LTE network, so as to reduce deployment cost and realize smooth upgrade.

USIM (Universal Subscriber Identity Module, universal subscriber identity card), also called upgrade SIM, is a component in UMTS 3G networks. Besides supporting multiple applications, the USIM card upgrades the algorithm in terms of security, and increases the authentication function of the card to the network, and the bidirectional authentication can effectively prevent hackers from attacking the card. And USIM is gradually transiting to mobile business platform or even multi-application platform, which can realize other applications such as electronic wallet, electronic credit card, electronic bill, etc., and greatly expands the intellectualization and platfonnization of mobile terminal.

In the prior art, mobile communication systems such as LTE/NB-IOT need to interact with USIM for many times in the communication process, obtain user information, access the network after performing two-way authentication with the network, and communicate with the network. The multiple functional modules of the mobile terminal can query USIM information, each module interacts with the USIM respectively, conflicts can occur, so that commands received by the USIM are disordered, correct file contents cannot be normally processed and returned, the code logic is disordered, maintenance is not good, a certain time can be spent in the interaction process with the USIM, and the system operation efficiency can be reduced if the modules interact with the card for multiple times in the communication process.

Disclosure of Invention

Accordingly, an object of the embodiments of the present invention is to provide a communication method, a communication device, a mobile terminal, and a storage medium, which can reduce the number of interactions between a function module and a USIM, improve communication efficiency, and facilitate maintenance.

In a first aspect, an embodiment of the present invention provides a communication method, where the method includes:

responding to a read operation instruction sent by a functional module, and acquiring a target file identifier according to the read operation instruction;

detecting the target file identifier in a file package, wherein the file package comprises a plurality of preset data packages and corresponding file identifiers, and the file package is acquired when the mobile terminal is started;

responding to the detection of the target file identification in the file package, and acquiring a data package corresponding to the target file identification; and

and sending the data packet corresponding to the target file identifier to a functional module.

Preferably, the method further comprises:

in response to the fact that the target file identifier is not detected in the file package, detecting the existence of a data package corresponding to the target file identifier according to a universal subscriber identity card (USIM) service table, wherein the USIM service table is used for indicating the existence of the data package corresponding to the target file identifier in a USIM, and the USIM service table is acquired when the mobile terminal is started;

in response to detecting that the data packet corresponding to the target file identifier exists according to the USIM service table, interacting with the USIM to acquire the data packet corresponding to the target file identifier; and

Preferably, the interaction with the USIM to obtain the data packet corresponding to the target file identifier includes:

inquiring the consistency of the catalogue of the data packet corresponding to the target file identifier and the currently stored catalogue;

responding to the fact that the catalogue of the data packet corresponding to the target file identifier is consistent with the currently stored catalogue, and acquiring the data packet corresponding to the target file identifier from the USIM; and

and responding to the inconformity of the catalogue of the data packet corresponding to the target file identifier and the catalogue stored at present, entering the corresponding catalogue step by step according to the file selection authority to obtain the data packet corresponding to the target file identifier.

Preferably, the method further comprises:

determining the type of the update operation in response to receiving an update operation instruction sent by a functional module, wherein the type of the update operation comprises instant update and non-instant update;

updating the content in the file package in response to the type of the update operation being non-instant update; and

and updating the contents in the file package and the USIM in response to the update operation being of the type of instant update.

Preferably, after updating the content in the package, the method further comprises:

and in response to receiving the synchronization instruction, updating the content in the USIM according to the content in the updated file packet.

Preferably, the method further comprises:

and in response to receiving the interaction operation instruction sent by the functional module, interacting with the USIM.

Preferably, the interactive operation instruction includes a synchronization instruction.

In a second aspect, an embodiment of the present invention provides a communication apparatus, the apparatus including:

the receiving unit is used for responding to the received reading operation instruction sent by the functional module and acquiring the target file identification according to the reading operation instruction;

the detection unit is used for detecting the target file identifier in a file packet, wherein the file packet comprises a plurality of preset data packets and corresponding file identifiers, and the file packet is acquired when the mobile terminal is started;

the acquisition unit is used for responding to the detection of the target file identification in the file package and acquiring a data package corresponding to the target file identification; and

and the sending unit is used for sending the data packet corresponding to the target file identifier to the functional module.

In a third aspect, an embodiment of the present invention provides a mobile terminal, including:

at least one card slot for carrying a Universal Subscriber Identity Module (USIM);

a memory;

at least one processor;

wherein the memory is for storing one or more computer program instructions for execution by the processor to implement the method of the first aspect.

In a fourth aspect, embodiments of the present invention provide a computer readable storage medium having stored thereon computer program instructions which, when executed by a processor, implement a method according to the first aspect.

According to the technical scheme, when the mobile terminal is started, a plurality of preset USIM data packets and corresponding file identifications are obtained, after a reading operation instruction sent by the functional module is received, the corresponding data packets are directly obtained in the file packets according to the target file identifications in the reading operation instruction, and the data packets corresponding to the target file identifications are sent to the functional module. Therefore, the interaction times between the functional module and the USIM can be reduced, the communication efficiency is improved, and the maintenance is convenient.

Drawings

The above and other objects, features and advantages of the present invention will become more apparent from the following description of embodiments of the present invention with reference to the accompanying drawings, in which:

FIG. 1 is a schematic diagram of a mobile terminal according to an embodiment of the present invention;

fig. 2 is a schematic diagram of a file structure of a USIM according to an embodiment of the present invention;

FIG. 3 is a schematic diagram of a prior art communication system;

fig. 4 is a flowchart of data interaction of a function module of the related art with a USIM;

FIG. 5 is a schematic diagram of a communication system according to an embodiment of the present invention;

FIG. 6 is a flow chart of a communication method of an embodiment of the present invention;

fig. 7 is a flowchart of acquiring a data packet from a USIM according to an embodiment of the present invention;

FIG. 8 is a schematic diagram of a file structure according to an embodiment of the present invention;

FIG. 9 is a diagram of directory matching relationships according to an embodiment of the present invention;

FIG. 10 is a flow chart of data update according to an embodiment of the present invention.

Detailed Description

The present invention is described below based on examples, but the present invention is not limited to only these examples. In the following detailed description of the present invention, certain specific details are set forth in detail. The present invention will be fully understood by those skilled in the art without the details described herein. Well-known methods, procedures, flows, components and circuits have not been described in detail so as not to obscure the nature of the invention.

Moreover, those of ordinary skill in the art will appreciate that the drawings are provided herein for illustrative purposes and that the drawings are not necessarily drawn to scale.

Unless the context clearly requires otherwise, the words "comprise," "comprising," and the like in the description are to be construed in an inclusive sense as opposed to an exclusive or exhaustive sense; that is, it is the meaning of "including but not limited to".

In the description of the present invention, it should be understood that the terms "first," "second," and the like are used for descriptive purposes only and are not to be construed as indicating or implying relative importance. Furthermore, in the description of the present invention, unless otherwise indicated, the meaning of "a plurality" is two or more.

Fig. 1 is a schematic diagram of a mobile terminal according to an embodiment of the present invention. As shown in fig. 1, the communication system of the embodiment of the present invention includes a mobile terminal including at least one processor 11; and a memory 12 communicatively coupled to the at least one processor 11; and a communication module 13 communicatively connected to the scanning device; and at least one card slot for carrying a universal subscriber identity card 14 (USIM, universal Subscriber Identity Module); the communication component 13 interacts with the USIM under the control of the processor 11; the memory 12 stores instructions executable by the at least one processor 11, and the instructions are executed by the at least one processor 11 to implement the communication method according to the embodiment of the present invention.

Further, the mobile terminal is any other type of electronic computing device that can carry a USIM, as well as smart phones, tablet computers, wearable devices, and others.

Further, USIM is an application on UICC (Universal Integrated Circuit Card ). The USIM includes subscriber subscription information, authentication information, pay mode, subscriber short message, etc. USIM is used in universal mobile telecommunications system (UMTS, universal Mobile Telecommunication System) networks, i.e. WCDMA (Wideband Code Division Multiple Access ) networks. When a terminal (including a circuit switching function and a packet switching function) is to use a WCDMA service, a USIM is required to be used.

Further, the USIM mainly includes the following information:

international mobile subscriber identity (IMSI, international Mobile Subscriber Identity). An IMSI is a unique identification assigned to each subscriber that is not visible to the subscriber but is visible to the network. IMSI is used as a subscriber identity for authentication purposes. Its private user identity is equivalent to IMSI in IP multimedia subsystem (IMS, IP Multimedia Subsystem).

Mobile subscriber ISDN number (MSISDN, mobile Subscriber ISDN Number): in which one or more telephone numbers assigned to the user are stored.

Encryption Key (CK, cipher Key) and Integrity Key (IK, integrity Key): these keys are used for encryption and integrity protection of data in the air interface. The USIM separately stores keys used in the circuit domain and the packet domain.

Short message (SMS, short Message Service): the USIM may store short messages and related data such as sender, receiver, status, etc.

Short message parameters: the field is used to store configuration data related to the SMS service, such as SMS centre address, supported protocols etc.

Multimedia messaging service (MMS, multimedia Message Service) user connectivity parameters: the field is used to store configuration data associated with the MMS service, e.g. an MMS server address, an MMS gateway address.

MMS user preference information: the field is used to store subscriber preference information related to the MMS service, such as a send report flag, priority, expiration information, etc.

Further, fig. 2 is a schematic diagram of a file structure of the USIM according to an embodiment of the present invention. As shown in fig. 2, the File structure of the USIM is a tree structure including MF (Master File), EF (Elementary File), EF _PL (language preference EF, language selection file), DF _TELECOM (Telecom EF, TELECOM directory), EF _ICCID (Integrate circuit card identity EF, unique identification number of IC card), EF _DIR Directory File (DF) and ADF ApplicationA dedicated file).

Where MF is the root directory, and all application files specified in the non-ETSI (European Telecommunications Standards Institute, european telecommunications standardization institute) GSM (Global System for Mobile Communications ) protocol are defined under the root directory by the respective manufacturer (e.g., PIN1, PIN2 …). Each USIM card has only one unique main file, all other files are descendants thereof, and the main file has only a file header for storing control and management information of the USIM card.

DF is a special file, and only has a file header for storing management control information of the whole directory, and the special file is equivalent to the root of a directory.

ADFs are special dedicated file directories that include all dedicated directory files and basic files that are applied.

EF is a basic file in an integrated circuit card file system for storing data, corresponding to a file in a computer. The file header stores the position and control information of the file, the file body stores real data, and only basic files in the USIM have the file body and are also used for storing data.

EF _PL Including codes in one or more languages. This information is determined by the user/operator and defines the preferred language in order of priority.

EF _ICCID Is the unique identification number of USIM and contains information of operator, card vendor, card issuing time and provincial code.

DF _TELECOM Including test files (EF _TEST ) Abbreviated dialing (EF) _ADN ) And short message (EF _SMS ) Etc. Wherein, the number of abbreviated dialing and short message records is the minimum configuration requirement.

EF _DIR An application identifier (AID, application identifier) and an application tag are included as necessary options. The USIM application selects through an AID selection mode.

Further, EF1-EFz under ADF1 and ADF2, and EF1-EFy may be EF _LI (language indication), EF _IMSI (International Mobile subscriber)Identifier, EF _keys (encryption key and integrity key), EF _UST (USIM service Table), EF _ACM (call accumulation table), etc.

Further, the USIM performs File access through a File Identifier (FID).

Specifically, the FID is used to locate or identify a particular file. The FID of the file is set at the time of the file establishment. The child file of the current directory and the parent file of the current directory and the direct child directory cannot have the same FID value. The series connection of the FID is a path. The path starts with the MF or the current DF and ends with the identifier of the file itself. The order of FIDs is always from the upper directory to the subdirectories.

Further, after the UICC activates and returns a reset answer (ATR, answer To Request), the root directory is defaulted to the current directory. The file is selected using the SELECT function.

The dedicated command for any application should only be operable if the application is the current directory.

The following files may be selected from the last selected file by FID reference: any direct subfiles of the current directory; a direct child of the parent of any current DF; a parent directory of the current directory; current DF or ADF; MF (MF).

Fig. 3 is a schematic diagram of a prior art communication system. As shown in fig. 3, the related art communication system includes a plurality of functional modules and USIMs. The present embodiment is illustrated with four functional modules 31a-31d as an example.

Specifically, mobile terminals such as LTE/NB-IOT need to interact with USIM for many times in the communication process, user information is obtained, and after mutual authentication is performed with the network, the mobile terminals are accessed to the network and communicate with the network. Multiple functional modules may query for USIM information, each module interacting with the USIM individually to obtain USIM information.

Specifically, the description is given by taking the example that the functional module needs to perform read-write operation. As shown in fig. 2, the file structure directory in USIM application is generally MF-DF-EF, and some EF exists directly under the MF root directory. For USIM applications, EF is typically present under the ADF directory. To acquire or update the content of an EF file, the content of the EF file is first entered into the directory where the file is located, and then the EF is operated accordingly. The directories are different, and the selectable file rights are different. The following files may be selected from the last selected file by FID reference: any direct subfiles of the current directory; a direct child of the parent of any current DF; a parent directory of the current directory; current DF or ADF; MF (MF). Other cases require re-entry into the corresponding directory to select the file.

Specifically, fig. 4 is a flowchart of data interaction of a function module of the related art with the USIM. As shown in fig. 4, the function module in the prior art includes the following steps when performing a file writing operation:

step S401, a function module SELECTs MF (SELECT MF).

Step S402, USIM sends status bytes.

In step S403, the function module transmits a GET RESPONSE (GET RESPONSE).

Step S404, the USIM replies file content and status bytes to the function module.

Step S405, the function module SELECTs DF/ADF (SELECT DF/ADF).

Step S406, the USIM sends status bytes.

Step S407, the functional module sends an acquisition response.

In step S408, the USIM replies the file content and status bytes to the function module.

Step S409, function module selection EF (SELECT EF).

Step S410, the USIM sends status bytes.

Step S411, the function module sends an acquisition response.

Step S412, the USIM replies the file content and status bytes to the function module.

Step S413, the function module reads and writes the file.

Step S414, the USIM sends a status byte.

Thus, the writing of the file can be completed through the above steps S401 to S414.

Further, in addition to the above steps S401 to S414, the file reading operation includes the following steps:

step S415, the function module sends an acquisition response.

Step S416, the USIM replies the file content and status bytes to the function module.

Thus, the file reading operation can be completed through the above steps S401 to S416.

Further, a general command format in which the functional module interacts with the USIM is a 5-byte command header, followed by whether or not data is appended. The 5 byte command headers are CLA, INS, P1, P2 and Lc, respectively. Wherein CLA is instruction category; INS is instruction code; p1 and P2 are parameters; lc is the length of the data. For LTE, cla=0. The INS is used to distinguish between commands, e.g., SELECT FILE (select file) INS is 0xa4,GET RESPONSE command INS is 0xc0, read BINARY (read BINARY) INS is 0xb0; p1 and P2 need to be determined according to the command type, lc represents the data length to be transferred to the USIM application. The function module sends the 5-byte command header to the USIM, after the USIM replies with an INS byte, the subsequent data is sent to the USIM, the USIM returns status bytes, and the terminal performs subsequent operations according to the status bytes. If status bytes is 0x61 x 0xXX, the terminal needs to acquire file information of 0xXX bytes through a GET RESPONSE command, and acquire EF file type and length information from the information for subsequent file reading/updating; if a status word 0x90 0x00 is received, it represents command completion.

Specifically, the function module sends a command for selecting the MF file to the USIM application, the command is sent to the USIM in two times according to the command, the USIM replies a status byte after receiving the command, and the terminal judges whether to perform GET RESPONSE according to the status byte. And similarly, selecting a DF file to enter a DF file directory, selecting EF, and performing read-write operation on EF. If the directories of two continuous EF are the same, the EF can be directly selected when the EF file is operated for the second time, and the MF and the DF do not need to be repeatedly entered.

However, as can be seen from fig. 3 and fig. 4, the multiple functional modules interact with the USIM respectively, so that the command received by the USIM is disordered, the correct file content cannot be normally processed and returned, and the code logic is disordered and is not easy to maintain; meanwhile, each interaction process with the card takes a certain time, and if the card interacts with the USIM for many times in the communication process, the system operation efficiency can be reduced.

Fig. 5 is a schematic diagram of a communication system according to an embodiment of the present invention. As shown in fig. 5, the communication system of the present method embodiment includes a plurality of functional modules, a control module 52, and USIMs. The present embodiment is illustrated with four functional modules 51a-51d as an example. The functional module may interact with the control module 52, and the control module 52 may interact with the USIM.

Further, each functional module may be each Application (APP) of the mobile terminal, or a subroutine of a different function in the same application.

Further, after each power-on of the mobile terminal, the control module 52 performs data interaction with the USIM to obtain a plurality of predetermined data packets and corresponding file identifiers.

Further, the data packet is a USIM file, for example, EF _DIR ，EF _ICCID And EF _PL Etc.

Further, the file identifier may be a file identifier FID, or may be a new file identifier in another format.

Further, each data packet has a corresponding file identifier, and the file identifiers corresponding to different data packets are different.

Further, after each power-on of the mobile terminal, the control module 52 performs data interaction with the USIM to obtain a USIM service table (EF _UST ) The USIM service table is used for indicating the existence condition of the data packet corresponding to the target file identification in the USIM.

Further, the data packet is a USIM file.

Specifically, taking an LTE communication system as an example, a file to be saved by the control module is preset. When the system is started, after the control module enters the MF and the ADF, the current file catalogue is recorded. First read EF _UST Files, each bit of the file identifying whether a corresponding file exists, e.g., bit85 identifying EF _epsloci (EPS location information, ESP position information) is present, bit20 identifies EF _plmnwact (User controlled PLMN selector with Access Technology, the user controls the PLMN selector and access technology) whether it is present. Thereafter, other files required in the communication system, e.g. EF, are read continuously _imsi ，EF _epsloci And EF _plmnwact And the like, wherein the catalogues of all files are the same, so that the subsequent file reading does not need to enter the MF-ADF process, and the EF is queried _UST After finding that the file exists, directly selecting the EF file to read, steps S401 to S408 in fig. 4 may be omitted multiple times, reducing the number of interactions with the USIM.

In addition, for a file of a fixed length, steps S411-S412 in FIG. 4, such as EF, may be omitted _imsi Is a binary file of fixed length 9 bytes, and EF is selected _imsi The command is set with p2=0x0c, that is, the file length and type are not required to be obtained through the GET RESPONSE command without returning data, and the ReadBinary command can be directly used for reading 9 bytes of file information.

Further, as shown in fig. 6, the communication method of the control module includes the following steps:

step S610, receiving a transmitted operation instruction of the functional module.

In this embodiment, the control module receives an operation instruction sent by the functional module.

Step S620, determine whether the operation instruction is a read operation instruction.

In this embodiment, the control module determines whether the received operation instruction is a read operation instruction, where the read operation instruction is used to read a file.

Further, in response to the operation instruction being a read operation instruction, step S630 is entered.

Further, in response to the operation instruction not being a read operation instruction, step S1010 is entered.

Step S630, the target file identification is obtained.

In this embodiment, in response to receiving the operation instruction sent by the functional module as a read operation instruction, the target file identifier is obtained according to the read operation instruction.

Step S640, detecting the target file identifier in the file package.

In this embodiment, the control module detects the target file identifier in the file packet.

Further, as described above, when the mobile terminal is powered on, the control module performs data interaction with the USIM to obtain the file packet, where the file packet includes a plurality of predetermined data packets and corresponding file identifiers.

Further, the predetermined data packet may be a USIM file with a higher frequency of use in the read/write operation.

Further, in response to detecting the target file identification in the file package, step S650 is entered.

Further, in response to detecting the target file identification in the file package, step S670 is entered.

Step S650, acquiring a data packet.

In this embodiment, the control module responds to the detection of the target file identifier in the file packet, and obtains a data packet corresponding to the target file identifier.

Step S660, the data packet is sent.

In this embodiment, the control module sends the data packet corresponding to the target file identifier to the function module.

Further, in step S640, the control module, in response to not detecting the target file identifier in the file package, further includes the following steps:

step S670, detecting whether a data packet exists in the USIM.

In this embodiment, the control module detects, according to a USIM service table, whether a data packet corresponding to the target file identifier exists in the USIM or not in response to the target file identifier not being detected in the file packet, where the USIM service table is used to indicate the existence of the data packet corresponding to the target file identifier in the USIM.

Further, as described above, the USIM service table is obtained interactively with the USIM when the mobile terminal is powered on.

Further, in response to detecting that the data packet corresponding to the destination file identifier exists according to the USIM service table, step S680 is entered.

Further, in response to detecting that the data packet corresponding to the destination file identifier does not exist according to the USIM service table, step S690 is performed.

Step S680, obtain the data packet from USIM.

In this embodiment, the control module, in response to detecting that the data packet corresponding to the target file identifier exists according to the USIM service table, interacts with the USIM to obtain the data packet corresponding to the target file identifier.

Further, after acquiring the data packet from the USIM, the data packet is sent to the functional module.

Step S690, sending operation failure information.

In this embodiment, in response to detecting, according to the USIM service table, that the data packet corresponding to the target file identifier does not exist, operation failure information is returned to the functional module.

Therefore, when the function module reads the file, the control module preferentially traverses and searches the stored file information, if the stored file information exists, the stored content is directly returned to the function module, and interaction with the USIM is not needed. For example, in the LTE system, the NAS (Network Attached Storage ) may read the EFimsi content, and the AT (Attention) command may also query the EFimsi content, and the two modules send request messages to the USIM control module, so that the USIM control module does not need to actually interact with the USIM, and directly replies the stored EFimsi file content, thereby saving time.

Further, as shown in fig. 7, a flow of interacting with the USIM to obtain a data packet corresponding to the target file identifier includes the following steps:

step S710, obtaining the currently stored catalogue.

In this embodiment, the control module obtains the currently stored directory.

Step S720, inquiring the consistency of the catalogue of the data packet corresponding to the target file identifier and the catalogue stored currently.

In this embodiment, the control module queries whether the directory of the data packet corresponding to the target file identifier is consistent with the directory currently stored.

Optionally, the directory of the data packet corresponding to the target file identifier is consistent with the currently stored directory when the following conditions are met:

and when the data packet corresponding to the target file identifier is a direct subfile of any current directory.

And when the data packet corresponding to the target file identifier is a direct child directory of the parent directory of any current DF.

And the data packet corresponding to the target file identifier is a parent directory of the current directory.

And the data packet corresponding to the target file identifier is the current DF or ADF.

And the data packet corresponding to the target file identifier is MF.

Further, taking the file structure shown in fig. 8 as an example, the correspondence between the saved current directory and the matched file is shown in fig. 9.

Step S730, acquiring a data packet corresponding to the target file identifier from the USIM.

In this embodiment, the control module obtains the data packet corresponding to the target file identifier from the USIM in response to the fact that the directory of the data packet corresponding to the target file identifier is consistent with the directory currently stored.

Further, the control module proceeds to step S640 in response to the directory of the data packet corresponding to the target file identifier not being consistent with the currently stored directory.

Step 740, entering a corresponding catalogue to obtain a data packet corresponding to the target file identifier.

In this embodiment, the control module responds to the fact that the directory of the data packet corresponding to the target file identifier is inconsistent with the directory stored currently, and enters the corresponding directory step by step according to the file selection authority to obtain the data packet corresponding to the target file identifier.

Thus, the reading operation of the control module and the USIM can be completed.

Further, in the step S730 or the step S740, after the control module obtains the corresponding data packet from the USIM, the process proceeds to the step S660, and the control module sends the data packet corresponding to the target file identifier to the function module.

Therefore, if the requested file does not exist in the stored information, inquiring that the file exists according to EFust, the USIM control module interacts with the USIM, inquires whether the catalog of the requested file is consistent with the catalog stored currently, directly selects the target file if the catalog is consistent with the catalog stored currently, and then performs read/write operation; if the file lists are inconsistent, the new file directories are gradually entered according to the file selection authority, and the reading/writing operation is carried out on the target EF.

Further, for step S620 in fig. 6, it is determined whether the operation instruction is a read operation instruction, and in response to the operation instruction not being a read operation instruction, the method proceeds to step shown in fig. 10, and specifically includes:

step S1010, determine whether it is an update operation instruction.

In this embodiment, in step S620, the control module determines whether the operation instruction is a read operation instruction, and in response to the operation instruction not being a read operation instruction, determines whether the operation instruction is an update operation instruction, where the update operation instruction is a write file operation.

Further, in response to the operation instruction being an update operation instruction, the process advances to step S1020.

Further, in response to the operation instruction not being an update operation instruction, the process advances to step S1110.

Step S1020, determining whether the update is immediate.

In this embodiment, in response to the operation instruction being an update operation instruction, the control module determines whether the update instruction is an immediate update instruction.

Further, the types of update operations include both instant updates and non-instant updates.

Further, in response to the type of the update operation being an immediate update, step S1030 is entered.

Further, in response to the type of the update operation being a non-instant update, step S1040 is entered.

Step S1030, updating the contents in the file packet and USIM.

In this embodiment, in response to the update operation being of the type of instant update, the control module updates the content in the file package and updates the content in the USIM.

Step S1040, updating the content in the file package.

In this embodiment, only the content in the package is updated in response to the type of the update operation being a non-instant update.

Step S1050, send notification message.

In this embodiment, after the function module performs the update operation, a notification message is sent to the function module.

Thus, the update operation of the USIM and the control module can be completed.

Further, for step S1010 in fig. 10, it is determined whether the operation instruction is an update operation instruction, and in response to the operation instruction not being an update operation instruction, it is indicated that the operation instruction is an interactive operation instruction, the process proceeds to step S1110.

Step S1110, interaction with USIM is performed.

In this embodiment, in response to the operation instruction not being a read operation instruction and not being an update operation instruction, the instruction is classified as an interactive operation instruction including an instruction to verify a PIN (Personal Identification Number, personal identification password of a SIM card) code, query for USIM status, or the like.

Further, in response to the operation instruction being an interactive operation instruction, the interactive operation instruction is converted into a corresponding USIM command to interact with the USIM.

Therefore, for other command requests, such as verification of PIN codes, inquiry of USIM states and the like, the control module directly converts the command requests into corresponding USIM commands to interact with the USIM.

Optionally, the interaction instruction includes a synchronization instruction.

Further, the method comprises the following steps:

step S1111, in response to receiving the synchronization instruction, updating the content in the USIM according to the content in the updated file packet.

In this embodiment, after the above step S1040, when the system is idle or is about to be turned off, a synchronization instruction is sent to the control module. The synchronization instruction is used for instructing the control module to synchronously update the content updated in the file packet into the USIM, or instructs the USIM control module to update the file information which is not updated in the data packet into the USIM card into the card.

Further, if the USIM control module is instructed to update the file information which is not updated in the USIM card in the data packet into the card, the card is written one file by one file according to the file information in the data packet.

Therefore, when updating the USIM file, if the file is not required to be updated immediately, only the information stored by the control module is updated, the file in the USIM is not updated truly, the USIM is updated truly again when the system is idle, and the system operation efficiency is improved; if the control module needs to be updated immediately, the storage information of the control module and the file information in the USIM are updated at the same time.

The embodiment of the invention designs a part for controlling interaction with the USIM into a single control module, processes and analyzes the information for acquiring or updating the USIM information sent by other functional modules, converts the information into a command which can be identified by the USIM card to inform the USIM application, and then acquires the reply information of the USIM card and forwards the reply information to a requester to realize interaction with the USIM card. Therefore, the coupling of other codes is avoided, and other modules directly interact with the functional module, so that the functional distinction and the code logic of the whole system are clearer, and the management and the maintenance are convenient.

The embodiment of the invention reads the file known to be needed in the communication process at one time when the computer is started, and preferentially reads EF _ust From the file content, it can be determined whether other files are present on the USIM card, and no interaction with the card is required for files that are not present. The read file information is saved, and other tasks can be directly obtained from the saved information when the file information is obtained, so that the number of cards is reducedThe interaction times of the system are saved.

When the embodiment of the invention is used for realizing the reading and writing of the file, the reading and writing are directly carried out on the known or fixed file length without acquiring the file information through a GET RESPONSE command, so that the step of interacting with the USIM is reduced.

When updating USIM files, the embodiment of the invention can update the files to be updated except the files required to be updated in the protocol stipulated time, and other files can be updated to the file information stored by the USIM control module at first, and then are really updated to the USIM card when the USIM control module is idle, thereby improving the operation efficiency of the system.

The embodiment of the invention stores the current file catalog information, when the next file reading and writing request comes, the file catalog is compared first, if the catalogues are the same, the file can be selected directly, the step of interaction with the card is reduced, otherwise, the file operation is performed after the catalog of the current file is reselected.

According to the embodiment of the invention, a plurality of preset USIM data packets and corresponding file identifications are obtained when the mobile terminal is started, after a reading operation instruction sent by the functional module is received, the corresponding data packets are directly obtained in the file packets according to the target file identifications in the operation instruction, and the data packets corresponding to the target file identifications are sent to the functional module. Therefore, the interaction times between the functional module and the USIM can be reduced, the communication efficiency is improved, and the maintenance is convenient.

Further, the mobile terminal of the embodiment of the invention comprises: one or more processors 11 and a memory 12, one processor 11 being illustrated in fig. 1. The processor 11, the memory 12 may be connected by a bus or other means. The memory 12 serves as a non-volatile computer-readable storage medium for storing non-volatile software programs, non-volatile computer-executable programs, and modules. The processor 11 executes various functional applications of the device and data processing, i.e. implements the above-described communication methods, by running non-volatile software programs, instructions and modules stored in the memory 12.

The memory 12 may include a storage program area that may store an operating system, at least one application program required for functions, and a storage data area; the storage data area may store a list of options, etc. In addition, memory 12 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid-state storage device. In some embodiments, memory 12 may optionally include memory located remotely from processor 11, which may be connected to an external device via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

One or more modules are stored in the memory 12 that, when executed by the one or more processors 11, perform the communication methods in embodiments of the present invention.

The product may perform the method provided by the embodiment of the present application, and have corresponding functional modules and beneficial effects of the performing method, and technical details not described in detail in the embodiment of the present application may be referred to the method provided by the embodiment of the present application.

Another embodiment of the present invention is directed to a non-volatile storage medium storing a computer readable program for causing a computer to perform some or all of the method embodiments described above.

That is, it will be understood by those skilled in the art that all or part of the steps in implementing the methods of the embodiments described above may be implemented by a program stored in a storage medium, where the program includes several instructions for causing a device (which may be a single-chip microcomputer, a chip or the like) or a processor (processor) to perform all or part of the steps in the methods of the embodiments described herein. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

The above description is only of the preferred embodiments of the present invention and is not intended to limit the present invention, and various modifications and variations may be made to the present invention by those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A method of communication, the method comprising:

detecting the target file identifier in a file package, wherein the file package comprises a plurality of preset data packages and corresponding file identifiers, and the file package is obtained by carrying out data interaction with a USIM when the mobile terminal is started;

and sending the data packet corresponding to the target file identifier to a functional module, wherein the functional module is an application program or a subprogram of the mobile terminal.

2. The method according to claim 1, wherein the method further comprises:

3. The method of claim 2, wherein interacting with the USIM to obtain the data packet corresponding to the destination file identity comprises:

4. The method according to claim 1, wherein the method further comprises:

5. The method according to claim 4, wherein the method further comprises:

6. The method of claim 5, wherein the interoperation instruction comprises a synchronization instruction.

7. The method of claim 6, wherein after updating the content in the package, the method further comprises:

8. A communication device, the device comprising:

the detection unit is used for detecting the target file identifier in a file packet, wherein the file packet comprises a plurality of preset data packets and corresponding file identifiers, and the file packet is obtained by carrying out data interaction with the USIM when the mobile terminal is started;

and the sending unit is used for sending the data packet corresponding to the target file identifier to a functional module, wherein the functional module is an application program or a subprogram of the mobile terminal.

9. A mobile terminal, the mobile terminal comprising:

a memory;

at least one processor;

wherein the memory is for storing one or more computer program instructions for execution by the processor to implement the method of any one of claims 1-7.

10. A computer readable storage medium, on which computer program instructions are stored, which computer program instructions, when executed by a processor, implement the method of any of claims 1-7.