CN111447319A - Terminal number book management method, terminal and user identification module - Google Patents
Terminal number book management method, terminal and user identification module Download PDFInfo
- Publication number
- CN111447319A CN111447319A CN202010220292.5A CN202010220292A CN111447319A CN 111447319 A CN111447319 A CN 111447319A CN 202010220292 A CN202010220292 A CN 202010220292A CN 111447319 A CN111447319 A CN 111447319A
- Authority
- CN
- China
- Prior art keywords
- terminal
- command
- record
- type
- terminal directory
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
- H04W8/183—Processing at user equipment or user record carrier
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
Abstract
The present disclosure provides a terminal directory management method, including: receiving a terminal number book management command sent by a user identification module; determining the operation type of the command according to the terminal directory management command; acquiring corresponding operation contents in the terminal directory management command according to the operation type; and performing corresponding operation on the terminal directory according to the operation type and the operation content. The disclosure also provides a terminal and a subscriber identity module.
Description
Technical Field
The disclosed embodiment relates to the technical field of communication, in particular to a terminal number book management method, a terminal and a user identification module.
Background
The directory function of a mobile terminal (e.g., a cell phone, etc.) is one of the basic functions of a mobile terminal that provides a record to the end user regarding the names, telephones, groupings, etc. of contacts.
Information interaction related to basic capability is relatively concerned in a current USAT (USIM Application Toolkit) mechanism, consideration on the directory related function of a terminal is usually lacked, and the interaction requirement of the USIM card Application on the directory of the terminal is not supported.
Disclosure of Invention
The disclosed embodiment aims to solve at least one of technical problems in the prior art, and provides a terminal number book management method, a terminal and a user identification module.
In a first aspect, an embodiment of the present disclosure provides a terminal directory management method, which is applied to a terminal, and the terminal directory management method includes:
receiving a terminal number book management command sent by a user identification module;
determining the operation type of the command according to the terminal directory management command;
acquiring corresponding operation contents in the terminal directory management command according to the operation type;
and performing corresponding operation on the terminal directory according to the operation type and the operation content.
In some embodiments, the terminal directory management command includes a command qualifier, and the determining an operation type of the command according to the terminal directory management command includes: and identifying the operation type of the command according to the command qualifier.
In some embodiments, the operation type includes an add number record type; the obtaining of the corresponding operation content in the terminal directory management command according to the operation type includes:
reading number information to be added from the terminal directory management command according to the number record adding type, wherein the number information comprises a number string and a number name;
and generating a corresponding number record according to the number information, wherein the operation content comprises the number record.
In some embodiments, the performing, according to the operation type and the operation content, a corresponding operation on the terminal directory includes:
adding the number record into the terminal directory according to the operation type and the operation content;
acquiring a record identifier of the number record newly added in the terminal directory;
after the corresponding operation is performed on the terminal directory according to the operation type and the operation content, the method further includes:
and returning a command response message to the user identification module, wherein the command response message comprises the record identification.
In some embodiments, the operation type comprises a delete number record type; the obtaining of the corresponding operation content in the terminal directory management command according to the operation type includes:
and reading the record identifier of the number record to be deleted from the terminal directory management command according to the deletion number record type, wherein the operation content comprises the record identifier.
In some embodiments, the performing, according to the operation type and the operation content, a corresponding operation on the terminal directory includes:
deleting the number records corresponding to the record identifiers in the terminal directory according to the operation types and the operation contents;
after the corresponding operation is performed on the terminal directory according to the operation type and the operation content, the method further includes:
and returning a command response message to the subscriber identification module, wherein the command response message comprises information that the number record is deleted successfully.
In some embodiments, the operation type comprises a change number record type; the obtaining of the corresponding operation content in the terminal directory management command according to the operation type includes:
reading a record identifier of a number record to be changed and number information to be changed from the terminal directory management command according to the type of the changed number record, wherein the number information comprises a number string and a number name;
and generating a corresponding new number record according to the number information to be changed, wherein the operation content comprises the record identifier and the new number record.
In some embodiments, the performing, according to the operation type and the operation content, a corresponding operation on the terminal directory includes:
changing the number record corresponding to the record identifier in the terminal directory into the new number record according to the operation type and the operation content;
after the corresponding operation is performed on the terminal directory according to the operation type and the operation content, the method further includes:
and returning a command response message to the subscriber identification module, wherein the command response message comprises information that the number record is changed successfully.
In a second aspect, an embodiment of the present disclosure further provides a terminal directory management method, which is applied to a subscriber identity module, and the terminal directory management method includes:
receiving a terminal number book management request of an application end of a user identification module;
generating a terminal directory management command according to the terminal directory management request;
and sending the terminal number book management command to the terminal so that the terminal can perform corresponding terminal number book management operation based on the terminal number book management command.
In a third aspect, an embodiment of the present disclosure provides a terminal, including:
the first receiving module is used for receiving the terminal number book management command sent by the user identification module;
the command analysis module is used for determining the operation type of the command according to the terminal directory management command; acquiring corresponding operation contents in the terminal directory management command according to the operation type;
and the command execution module is used for carrying out corresponding operation on the terminal directory according to the operation type and the operation content.
In a fourth aspect, an embodiment of the present disclosure provides a subscriber identity module, including:
the second receiving module is used for receiving a terminal directory management request of an application end of the user identification module;
the command generation module is used for generating a terminal directory management command according to the terminal directory management request;
and the sending module is used for sending the terminal number book management command to the terminal so that the terminal can perform corresponding terminal number book management operation based on the terminal number book management command.
The terminal number book management method, the terminal and the user identification module provided by the embodiment of the disclosure extend the active command and the operation type of the user identification module (USIM), so that the USIM card application can perform the required management operation (such as adding number records, deleting number records, changing number records or reading number records and the like) on the terminal number book by sending the terminal number book management command through the user identification module (USIM card) when the service is required (such as adding, deleting, changing or reading the number records in the terminal number book) under the condition of obtaining user permission and authorization, the operation of the user can be simplified on the premise of fully ensuring the privacy and information safety of the user, more convenient experience is provided for the user, meanwhile, the requirement of adding corresponding functions to the USIM card application is met, the service capability of a USAT mechanism is enhanced, and the corresponding machine-card interaction capability is enhanced, efficient implementation of operator services can be better supported.
Drawings
Fig. 1 is a flowchart of a terminal directory management method according to an embodiment of the present disclosure;
FIG. 2 is a flow chart of one embodiment of step 13 in FIG. 1;
FIG. 3 is a flow chart of another specific implementation of step 13 in FIG. 1;
FIG. 4 is a flow chart of yet another embodiment of step 13 in FIG. 1;
FIG. 5 is a flow chart of one embodiment of step 14 of FIG. 1;
FIG. 6 is a flow chart of another specific implementation of step 14 in FIG. 1;
FIG. 7 is a flow chart of yet another embodiment of step 14 of FIG. 1;
fig. 8 is a flowchart of another terminal directory management method according to an embodiment of the disclosure;
fig. 9 is a flowchart of another terminal directory management method according to an embodiment of the disclosure;
fig. 10 is a schematic structural diagram of a terminal according to an embodiment of the present disclosure;
fig. 11 is a schematic structural diagram of a subscriber identity module according to an embodiment of the present disclosure.
Detailed Description
In order to make those skilled in the art better understand the technical solution of the present disclosure, the terminal directory management method, the terminal and the subscriber identity module provided in the present disclosure are described in detail below with reference to the accompanying drawings.
Unless otherwise defined, technical or scientific terms used herein shall have the ordinary meaning as understood by one of ordinary skill in the art to which this disclosure belongs. The use of "first," "second," and similar terms in this disclosure is not intended to indicate any order, quantity, or importance, but rather is used to distinguish one element from another. Also, the use of the terms "a," "an," or "the" and similar referents do not denote a limitation of quantity, but rather denote the presence of at least one. The word "comprising" or "comprises", and the like, means that the element or item listed before the word covers the element or item listed after the word and its equivalents, but does not exclude other elements or items. The terms "connected" or "coupled" and the like are not restricted to physical or mechanical connections, but may include electrical connections, whether direct or indirect. "upper", "lower", "left", "right", and the like are used merely to indicate relative positional relationships, and when the absolute position of the object being described is changed, the relative positional relationships may also be changed accordingly.
Fig. 1 is a flowchart of a terminal directory management method provided in an embodiment of the present disclosure, as shown in fig. 1, the method may be performed by a terminal directory management apparatus, the apparatus may be implemented in a software and/or hardware manner, the apparatus may be integrated in a terminal, the terminal directory management method may be applied to the terminal, and the terminal directory management method includes:
and step 11, receiving a terminal number book management command sent by the user identification module.
In the embodiment of the present disclosure, the terminal is a User Equipment (UE), for example, the terminal is a mobile phone. A terminal (UE) generally includes a subscriber identity module (sim) and a Mobile Equipment (ME). The Subscriber Identity Module may be a Universal Subscriber Identity Module (USIM) card.
It should be understood that the USIM card is Integrated on a Universal Integrated Circuit Card (UICC), which is a continuation and improvement of the SIM card used in the mobile network, and is used to store the user identity information and personal data, thereby securing access to the mobile network services. The USIM can perform user identification and user authentication when a user accesses a mobile network service using necessary functions and data, and is a basic device for the user to access the mobile network.
The relationship between the USIM and the mobile terminal has undergone a certain evolution process, and the USIM is only used as a passive device to accept a command of the terminal at the earliest and provides data or content according to a terminal command request. The method can only meet the basic requirements of machine-card interaction, but cannot support the realization of USIM application, namely, the USIM actively requires the terminal to execute corresponding functions according to application requirements. In order to solve the problem, the USIM card can actively request the mobile device of the terminal to execute a corresponding function according to an Application requirement by introducing a USIM Application Toolkit (USAT) mechanism. Wherein, USAT is one of the basic capabilities of a telecommunication smart card represented by a USIM card, and refers to a USAT protocol layer introduced in a protocol stack of a Cu interface (a mobile device of a terminal and an interface of the USIM card), and the USAT protocol layer provides a service mechanism on the basis of a service provided by a transport layer, which allows a USIM application to interact and operate with a mobile device of the terminal supporting such a mechanism, so that the USIM can actively request the mobile device of the terminal to perform a certain operation, and in USAT, a USAT instruction set is the basis and main manner for the telecommunication smart card to implement a service through the mobile device of the terminal.
The terminal directory function is one of the basic functions of a terminal, and the terminal directory can provide a user with records on names, telephones, groups, and the like of contacts. With the continuous development of mobile services and USIM card application functions, the requirements of USIM to call and interact with the basic functions of the terminal are gradually increased, however, in the current USAT mechanism, information interaction related to basic capabilities is concerned, consideration on the directory related functions of the terminal is lacked, and the requirement of USIM card application on the interaction with the directory of the terminal is not supported. In order to effectively solve the problem, in the embodiment of the present disclosure, the subscriber identity module adds a terminal number book management command by extension on the basis of the existing USAT mechanism, so as to require the terminal to set and manage the number records of the terminal number book, thereby satisfying the interaction requirement of the USIM card application on the terminal number book.
In the embodiment of the present disclosure, when a USIM card application generates a demand for managing a terminal number book, a subscriber identity module (USIM) generates a terminal number book management command to request the terminal to set and manage a number record of the terminal number book. Therefore, in step 11, a terminal directory management command sent by the subscriber identity module is first received, where the terminal directory management command is an active command that is expanded and added in advance by the subscriber identity module.
Table 1 shows a structure of a Terminal directory Management command (Terminal directory Management command), and as shown in table 1, the Terminal directory Management command includes a command qualifier for indicating an operation type of the command, where the command qualifier is denoted by "b 3b2b 1", and b3b2b1 may have multiple value encodings, and different value encodings respectively indicate different operation types, i.e. different Management operation requirements for the Terminal directory. For example, the value of the command qualifier b3b2b1 is encoded as 001, "001" indicates that the operation type of the command is the add number record type; the value of the command qualifier b3b2b1 is encoded to 010, "010" indicates that the operation type of the command is the deletion number record type; the value code of the command qualifier b3b2b1 is 011, where 011 indicates that the operation type of the command is change number record type. In this disclosure, the value encoding and the corresponding operation type of the command qualifier b3b2b1 may be set according to actual needs, which is not limited in this disclosure.
As shown in table 1, in the embodiment of the present disclosure, a text string is a data object that is conditionally required, and when the operation type of the current terminal directory management command is an add-number record type (i.e., the command qualifier b3b2b1 is 001), the text string is required to be selected, that is, the content of a number text string is included in the terminal directory management command, and the text string is used to indicate the name of a number that needs to be added to the terminal directory. The number string is a data object that is conditionally selected, and when the operation type of the current terminal directory management command is an add number record type (i.e. command qualifier b3b2b1 is 001), the number string is selected as a mandatory state, i.e. the terminal directory management command includes the content of the number string, and the number string is used to indicate the number that needs to be added to the terminal directory. The record identifier is a data object with a condition of being selected, and when the operation type of the current terminal directory management command is a delete number record type (namely, the command qualifier b3b2b1 is 010), the record identifier is selected, namely, the terminal directory management command contains the content of the record identifier, and the record identifier represents the record identifier of the number record to be deleted from the terminal directory. When the operation type of the current terminal directory management command is a change number record type (that is, the command qualifier b3b2b1 is 011), a text string, a number string and a record identifier are selected as necessary, at this time, the text string represents the name of a new number to be changed, the number string represents the new number to be changed, and the record identifier represents a record identifier in the terminal directory which needs to be changed.
TABLE 1
And step 12, determining the operation type of the command according to the terminal directory management command.
In the disclosed embodiment, step 12 includes: and identifying the operation type of the command according to the command qualifier in the terminal number book management command.
Specifically, after receiving the terminal directory management command, the command is parsed and the command qualifier is analyzed to determine the operation type of the command. In the embodiment of the present disclosure, the operation type of the command may be one of an add number record type, a delete number record type, and a change number record type. For example, when the command qualifier b3b2b1 is 001, it indicates that the operation type of the terminal number book management command received this time is the add number record type, when the command qualifier b3b2b1 is 010, it indicates that the operation type of the terminal number book management command received this time is the delete number record type, and when the command qualifier b3b2b1 is 011, it indicates that the operation type of the terminal number book management command received this time is the change number record type.
And step 13, acquiring corresponding operation contents in the terminal number book management command according to the operation type.
Fig. 2 is a flowchart of a specific implementation manner of step 13 in fig. 1, and in some embodiments, as shown in fig. 2, when the operation type of the command determined in step 12 includes an add number record type, step 13 includes:
When the operation type of the current terminal directory management command is determined to be the number adding record type, it indicates that the terminal directory management command further includes a number string and a text string to be added, so in step 1311, number information to be added is read from the terminal directory management command, where the number information includes the number string and a number name, and the number name is determined by the content of the text string in the read command.
The number records comprise numbers to be added and corresponding number names. For example, in the number record to be added, the number to be added is "10010", and the name of the number to be added is "unicom customer service telephone".
Fig. 3 is a flowchart of another specific implementation manner of step 13 in fig. 1, and in some embodiments, as shown in fig. 3, when the operation type of the command determined in step 12 includes a delete number record type, step 13 includes:
When the operation type of the current terminal directory management command is determined to be the delete number record type, it indicates that the terminal directory management command further includes a record identifier of a number record to be deleted, and therefore, in step 1321, the record identifier of the number record to be deleted is read from the terminal directory management command.
Fig. 4 is a flowchart of another specific implementation manner of step 13 in fig. 1, and in some embodiments, as shown in fig. 4, when the operation type of the command determined in step 12 includes a change number record type, step 13 includes:
When the operation type of the current terminal directory management command is determined to be a change number record type, it indicates that the terminal directory management command further includes a record identifier of a number record to be changed, a number string to be changed, and a text string to be changed, so in step 1321, the record identifier of the number record to be changed and number information to be changed are read from the terminal directory management command, where the number information includes the number string and a number name, and the number name may be determined by contents of the text string in the read command.
The new number records comprise new number names and/or new numbers, when the new number records comprise the new number names, the number names of the corresponding number records in the terminal number book need to be changed are indicated, and when the new number records comprise the new numbers, the number of the corresponding number records in the terminal number book need to be changed is indicated.
And 14, performing corresponding operation on the terminal directory according to the operation type and the operation content.
Fig. 5 is a flowchart of a specific implementation manner of step 14 in fig. 1, and as shown in fig. 5, in some embodiments, in a case that the operation type of the command determined in step 12 includes an add number record type, step 14 includes:
and step 1411, adding the number records to the terminal number book according to the operation types and the operation contents.
As described in the foregoing steps 1311, 1312, in the case where the operation type of the command determined in step 12 includes the add number record type, the acquired operation content includes the number record to be added, and therefore, in step 1411, the number record to be added is added to the terminal directory in accordance with the operation type of the command (the add number record type) and the operation content (the number record to be added).
And step 1412, acquiring the record identifier of the newly added number record in the terminal number book.
In step 1412, after the number record to be added is successfully added to the terminal directory, the identifier of the added number record in the terminal directory, that is, the record identifier of the newly added number record in the terminal directory, is obtained.
Fig. 6 is a flowchart of another specific implementation manner of step 14 in fig. 1, and as shown in fig. 6, in some embodiments, in a case that the operation type of the command determined in step 12 includes a delete number record type, step 14 includes:
and step 1421, deleting the number record corresponding to the record identifier to be deleted in the terminal number book according to the operation type and the operation content.
As described in the foregoing step 1321, in the case where the operation type of the command determined in step 12 includes the deletion number record type, the acquired operation content includes the record identifier to be deleted, and therefore, in step 1421, the number record corresponding to the record identifier to be deleted is deleted from the terminal directory according to the operation type (deletion number record type) and the operation content (record identifier to be deleted) of the command.
Fig. 7 is a flowchart of another specific implementation manner of step 14 in fig. 1, and as shown in fig. 7, in some embodiments, in a case that the operation type of the command determined in step 12 includes a change number record type, step 14 includes:
As described in the foregoing steps 1331 and 1332, in the case where the operation type of the command determined in step 12 includes a change number record type, the acquired operation content includes a record identifier to be changed and a new number record to be changed, and therefore, in step 1431, the number record corresponding to the record identifier to be changed in the terminal directory is changed to the new number record according to the operation type (change number record type) and the operation content (record identifier to be changed and new number record) of the command.
And step 15, returning a command response message to the user identification module.
In some embodiments, in the case that the operation type of the command determined in step 12 includes an add number record type, after adding a number record to be added to the terminal directory and acquiring a corresponding record identifier, a command response message is generated according to a command execution result and the acquired newly added record identifier, and then, the command response message is returned to the subscriber identity module. Wherein, the command response message comprises a record identifier of the number recorded in the terminal number book after adding the number record.
In some embodiments, in the case that the operation type of the command determined in step 12 includes a delete number record type, after deleting the number record corresponding to the record identifier to be deleted from the terminal directory, a command response message is generated according to the command execution result, and then, the command response message is returned to the subscriber identity module. The command response message comprises a command execution result, and the command execution result is information that the number record is deleted successfully.
In some embodiments, in the case that the operation type of the command determined in step 12 includes a change number record type, after the number record corresponding to the record identifier to be changed in the terminal directory is changed to a new number record, a command response message is generated according to the command execution result, and then, the command response message is returned to the subscriber identity module. The command response message comprises a command execution result, and the command execution result is information that the number record has been successfully changed.
Table 2 shows a structure of a command Response (Terminal Response) message, as shown in table 2, in the command Response message, the command qualifier is consistent with the requirement of the Terminal directory management command, and specifically, refer to the description of the command qualifier in the foregoing; and when the operation type of the terminal directory management command corresponding to the response message is an add number record type (that is, the command qualifier b3b2b1 is 001), the record identifier is optional and indicates a corresponding record identifier after the number record is added to the terminal directory.
TABLE 2
In some embodiments, the operation type of the command may also be a read number record type, in this case, in the terminal directory management command, the record identifier is a mandatory data object, and in this case, in step 13, the obtained operation content includes a record identifier of a number record to be read; in step 14, according to the operation type (read number record type) and the operation content (record identifier of the number record to be read), the number record corresponding to the record identifier to be read is read from the terminal directory, and in step 15, a command response message is generated according to the command execution result and the read number record and fed back to the subscriber identity module.
The terminal number book management method provided by the embodiment of the disclosure, by expanding the active command of the user identification module (USIM) and the operation type thereof, under the condition of obtaining user permission and authorization, when the USIM card application needs service (such as number records in the terminal number book need to be added, deleted, changed or read), the USIM card application can send the terminal number book management command through the USIM card to perform required management operations (such as number record addition, number record deletion, number record change or number record reading and the like) on the terminal number book, on the premise of fully ensuring the user privacy and information security, the operation of the user can be simplified, more convenient experience can be provided for the user, meanwhile, the requirement of adding corresponding functions to the USIM card application is met, the service capability of a USAT mechanism is enhanced, and the corresponding machine-card interaction capability is enhanced, efficient implementation of operator services can be better supported.
Fig. 8 is a flowchart of another terminal directory management method provided in the embodiment of the present disclosure, where the terminal directory management method is applied to a subscriber identity module and implemented based on the subscriber identity module, as shown in fig. 8, the terminal directory management method includes:
and step 21, receiving a terminal number book management request of an application end of the user identification module.
In step 21, when the application side (USIM card application) of the subscriber identity module generates a request for managing the terminal number book (e.g. a request for adding a service phone to the terminal number book for the convenience of the user), a terminal number book management request is sent to the subscriber identity module, and the specific type of the request may include, but is not limited to, an add number record type, a delete number record type, a change number record type, or a read number record type.
When the type of the terminal directory management request is an added number record type, the terminal directory management request comprises a number string to be added and a text string to be added; when the type of the terminal directory management request is a deleted number record type, the terminal directory management request comprises a record identifier to be deleted; when the type of the terminal directory management request is a change number record type, the terminal directory management request comprises a number string to be changed, a text string to be changed and a record identifier to be changed; when the type of the terminal directory management request is a read number record type, the terminal directory management request includes a record identifier to be read.
And step 22, generating a terminal number book management command according to the terminal number book management request.
In step 22, the description of the terminal directory management command can refer to the description of the foregoing embodiment, and is not repeated here.
And step 23, sending a terminal number book management command to the terminal so that the terminal can perform corresponding terminal number book management operation based on the terminal number book management command.
In step 23, after receiving the terminal number book management command, the terminal may perform a corresponding terminal number book management operation, such as the operations in step 12 to step 15.
In some embodiments, after the terminal returns the command response message, the application terminal (USIM card application) of the subscriber identity module returns a request response message, where the request response message may include a command response message fed back by the terminal, and when the command response message includes an added record identifier, the application terminal (USIM card application) of the subscriber identity module may perform record storage on the record identifier, so as to perform subsequent management operations such as changing, reading, and the like.
In the embodiment of the present disclosure, in practical applications, by adding a USAT proactive command and an operation type, in the case of obtaining user permission and authorization, the USIM card application may send a terminal number book management command through a subscriber identity module (USIM card) to perform a required management operation on the terminal number book, such as reading a contact (reading a number record) in the number book, adding a contact (adding a number record), modifying (changing a number record) and deleting (deleting a number record) the contact, and the like. On the premise of fully ensuring the privacy and information security of the user, the operation of the user can be simplified, and more convenient experience is provided for the user, for example, the USIM application can add the contact records (such as a customer service telephone) related to the application required by the user into a terminal directory, so that the user can conveniently contact as required, and in addition, a certain popularization effect can be brought to an operator to which the USIM application belongs. Meanwhile, the requirement that the USIM card application increases corresponding functions is met, and the service capability of a USAT mechanism is enhanced while the user experience is improved.
Fig. 9 is a flowchart of another terminal directory management method provided in the embodiment of the present disclosure, and as shown in fig. 9, the terminal directory management method includes:
For the description of step 31, reference is made to the above description of step 21, which is not repeated here.
And step 32, the user identification module generates a terminal number book management command according to the terminal number book management request.
For the description of step 32, reference is made to the above description of step 22, which is not repeated here.
And step 33, the user identification module sends a terminal number book management command to the terminal.
For the description of step 33, reference may be made to the above description of step 23 and step 11, which is not repeated here.
And step 34, the terminal determines the operation type of the command according to the terminal number book management command.
For the description of step 34, reference is made to the above description of step 12, which is not repeated here.
And step 35, the terminal acquires corresponding operation contents in the terminal number book management command according to the operation type.
For the description of step 35, reference is made to the above description of step 13, which is not repeated here.
And step 36, the terminal performs corresponding operation on the terminal number book according to the operation type and the operation content.
For the description of step 36, reference may be made to the above description of step 14, which is not repeated herein.
For the description of step 37, reference is made to the above description of step 15, which is not repeated here.
The request response message may include a command response message fed back by the terminal, and when the command response message includes an added record identifier, an application terminal (USIM card application) of the subscriber identity module may perform record storage on the record identifier, so as to perform subsequent management operations such as changing and reading.
Fig. 10 is a schematic structural diagram of a terminal according to an embodiment of the present disclosure, and as shown in fig. 10, the terminal includes: a first receiving module 401, a command analyzing module 402, and a command executing module 403.
The first receiving module 401 is configured to receive a terminal directory management command sent by the subscriber identity module.
The command analysis module 402 is configured to determine an operation type of a command according to the terminal directory management command; and acquiring corresponding operation contents in the terminal number book management command according to the operation type.
The command executing module 403 is configured to perform corresponding operations on the terminal directory according to the operation type and the operation content.
In some embodiments, the terminal directory management command includes a command qualifier, and the command analysis module 402 is specifically configured to identify an operation type of the command according to the command qualifier.
In some embodiments, the operation type includes an add number record type. The command analysis module 402 is specifically configured to read number information to be added from a terminal directory management command according to an add number record type, where the number information includes a number string and a number name; and generating a corresponding number record according to the number information, wherein the operation content comprises the number record.
In some embodiments, in the case that the operation type includes an add number record type, the command execution module 403 is specifically configured to add a number record to the terminal directory according to the operation type and the operation content; and acquiring the record identification of the newly added number record in the terminal number book.
In some embodiments, the operation type includes a delete number record type. The command analysis module 402 is specifically configured to read, according to the type of the deleted number record, a record identifier of the number record to be deleted from the terminal directory management command, where the operation content includes the record identifier.
In some embodiments, in a case that the operation type includes a delete number record type, the command executing module 403 is specifically configured to delete a number record corresponding to a record identifier to be deleted in the terminal directory according to the operation type and the operation content.
In some embodiments, the operation type includes a change number record type. The command analysis module 402 is specifically configured to read, according to the change number record type, a record identifier of a number record to be changed and number information to be changed from the terminal directory management command, where the number information includes a number string and a number name; and generating a corresponding new number record according to the number information to be changed, wherein the operation content comprises the record identifier and the new number record.
In some embodiments, in a case that the operation type includes a change number record type, the command executing module 403 is specifically configured to change, according to the operation type and the operation content, a number record corresponding to a record identifier to be changed in the terminal directory to a new number record.
In some embodiments, the terminal further comprises a command response module 404, and the command response module 404 is configured to return a command response message to the subscriber identity module. Wherein, under the condition that the operation type comprises an added number record type, the command response message comprises a record identifier of the added number record; in the case where the operation type includes a delete number record type, the command response message includes information that the number record has been successfully deleted; in case the operation type includes a change number record type, the command response message includes information that the number record has been successfully changed.
In addition, the terminal provided in the embodiment of the present disclosure is configured to implement the corresponding terminal directory management method, and specific relevant descriptions may refer to the description of the terminal directory management method in the foregoing embodiment, which is not described herein again.
Fig. 11 is a schematic structural diagram of a subscriber identity module according to an embodiment of the present disclosure, and as shown in fig. 11, the subscriber identity module includes: a second receiving module 501, a command generating module 502 and a sending module 503.
The second receiving module 501 is configured to receive a terminal directory management request of an application terminal of the subscriber identity module; the command generating module 502 is configured to generate a terminal directory management command according to the terminal directory management request; the sending module 503 is configured to send a terminal directory management command to the terminal, so that the terminal performs a corresponding terminal directory management operation based on the terminal directory management command.
In addition, the subscriber identity module provided in the embodiment of the present disclosure is configured to implement the corresponding terminal directory management method, and specific relevant descriptions may refer to the description of the terminal directory management method in the foregoing embodiment, which is not described herein again.
One of ordinary skill in the art will appreciate that all or some of the steps of the methods, systems, apparatuses, functional modules/units in the devices disclosed above may be implemented as software, firmware, hardware, and suitable combinations thereof. In a hardware implementation, the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be performed by several physical components in cooperation. Some or all of the physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit. Such software may be distributed on computer readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media). The term computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data, as is well known to those of ordinary skill in the art. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, Digital Versatile Disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can accessed by a computer. In addition, communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media as known to those skilled in the art.
It is to be understood that the above embodiments are merely exemplary embodiments that are employed to illustrate the principles of the present disclosure, and that the present disclosure is not limited thereto. It will be apparent to those skilled in the art that various changes and modifications can be made therein without departing from the spirit and scope of the disclosure, and these are to be considered as the scope of the disclosure.
Claims (11)
1. A terminal directory management method is applied to a terminal, and is characterized in that the terminal directory management method comprises the following steps:
receiving a terminal number book management command sent by a user identification module;
determining the operation type of the command according to the terminal directory management command;
acquiring corresponding operation contents in the terminal directory management command according to the operation type;
and performing corresponding operation on the terminal directory according to the operation type and the operation content.
2. The terminal directory management method according to claim 1, wherein the terminal directory management command includes a command qualifier, and the determining the operation type of the command from the terminal directory management command includes:
and identifying the operation type of the command according to the command qualifier.
3. The terminal directory management method according to claim 1 or 2, wherein the operation type includes an add number record type; the obtaining of the corresponding operation content in the terminal directory management command according to the operation type includes:
reading number information to be added from the terminal directory management command according to the number record adding type, wherein the number information comprises a number string and a number name;
and generating a corresponding number record according to the number information, wherein the operation content comprises the number record.
4. The terminal directory management method according to claim 3, wherein said performing a corresponding operation on the terminal directory according to the operation type and the operation content comprises:
adding the number record into the terminal directory according to the operation type and the operation content;
acquiring a record identifier of the number record newly added in the terminal directory;
after the corresponding operation is performed on the terminal directory according to the operation type and the operation content, the method further includes:
and returning a command response message to the user identification module, wherein the command response message comprises the record identification.
5. The terminal directory management method according to claim 1 or 2, wherein the operation type includes a delete number record type; the obtaining of the corresponding operation content in the terminal directory management command according to the operation type includes:
and reading the record identifier of the number record to be deleted from the terminal directory management command according to the deletion number record type, wherein the operation content comprises the record identifier.
6. The terminal directory management method according to claim 5, wherein said performing a corresponding operation on the terminal directory according to the operation type and the operation content comprises:
deleting the number records corresponding to the record identifiers in the terminal directory according to the operation types and the operation contents;
after the corresponding operation is performed on the terminal directory according to the operation type and the operation content, the method further includes:
and returning a command response message to the subscriber identification module, wherein the command response message comprises information that the number record is deleted successfully.
7. The terminal directory management method according to claim 1 or 2, wherein the operation type includes a change number record type; the obtaining of the corresponding operation content in the terminal directory management command according to the operation type includes:
reading a record identifier of a number record to be changed and number information to be changed from the terminal directory management command according to the type of the changed number record, wherein the number information comprises a number string and a number name;
and generating a corresponding new number record according to the number information to be changed, wherein the operation content comprises the record identifier and the new number record.
8. The terminal directory management method according to claim 7, wherein said performing a corresponding operation on the terminal directory according to the operation type and the operation content includes:
changing the number record corresponding to the record identifier in the terminal directory into the new number record according to the operation type and the operation content;
after the corresponding operation is performed on the terminal directory according to the operation type and the operation content, the method further includes:
and returning a command response message to the subscriber identification module, wherein the command response message comprises information that the number record is changed successfully.
9. A terminal directory management method is applied to a user identification module, and is characterized in that the terminal directory management method comprises the following steps:
receiving a terminal number book management request of an application end of a user identification module;
generating a terminal directory management command according to the terminal directory management request;
and sending the terminal number book management command to the terminal so that the terminal can perform corresponding terminal number book management operation based on the terminal number book management command.
10. A terminal, comprising:
the first receiving module is used for receiving the terminal number book management command sent by the user identification module;
the command analysis module is used for determining the operation type of the command according to the terminal directory management command; acquiring corresponding operation contents in the terminal directory management command according to the operation type;
and the command execution module is used for carrying out corresponding operation on the terminal directory according to the operation type and the operation content.
11. A subscriber identity module, comprising:
the second receiving module is used for receiving a terminal directory management request of an application end of the user identification module;
the command generation module is used for generating a terminal directory management command according to the terminal directory management request;
and the sending module is used for sending the terminal number book management command to the terminal so that the terminal can perform corresponding terminal number book management operation based on the terminal number book management command.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010220292.5A CN111447319A (en) | 2020-03-25 | 2020-03-25 | Terminal number book management method, terminal and user identification module |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010220292.5A CN111447319A (en) | 2020-03-25 | 2020-03-25 | Terminal number book management method, terminal and user identification module |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111447319A true CN111447319A (en) | 2020-07-24 |
Family
ID=71654564
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010220292.5A Pending CN111447319A (en) | 2020-03-25 | 2020-03-25 | Terminal number book management method, terminal and user identification module |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111447319A (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1946235A (en) * | 2006-11-09 | 2007-04-11 | 中国移动通信集团江苏有限公司 | User identifying module service and method and system for using personalized tailered issuing |
| CN101111025A (en) * | 2007-08-27 | 2008-01-23 | 大唐微电子技术有限公司 | Method for playing multimedia information using user recognizing module |
| CN101415164A (en) * | 2007-10-19 | 2009-04-22 | 凤凰微电子（中国）有限公司 | Smart card and method for implementing incoming call display information |
| CN101692746A (en) * | 2009-09-18 | 2010-04-07 | 中兴通讯股份有限公司 | Method and device for operating telephone directory |
| US20100159905A1 (en) * | 2007-06-01 | 2010-06-24 | France Telecom | Method of selecting an application installed on a secured module, an associated terminal and an associated security module |
| CN101789987A (en) * | 2010-02-02 | 2010-07-28 | 华为终端有限公司 | Telephone directory processing method and user equipment |
| CN108848497A (en) * | 2018-06-01 | 2018-11-20 | 中国联合网络通信集团有限公司 | Acquisition methods, device, terminal and the computer readable storage medium of list of application |
| CN110719581A (en) * | 2018-07-12 | 2020-01-21 | 中兴通讯股份有限公司 | Control method, device and system for terminal application |
-
2020
- 2020-03-25 CN CN202010220292.5A patent/CN111447319A/en active Pending
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1946235A (en) * | 2006-11-09 | 2007-04-11 | 中国移动通信集团江苏有限公司 | User identifying module service and method and system for using personalized tailered issuing |
| US20100159905A1 (en) * | 2007-06-01 | 2010-06-24 | France Telecom | Method of selecting an application installed on a secured module, an associated terminal and an associated security module |
| CN101111025A (en) * | 2007-08-27 | 2008-01-23 | 大唐微电子技术有限公司 | Method for playing multimedia information using user recognizing module |
| CN100534211C (en) * | 2007-08-27 | 2009-08-26 | 大唐微电子技术有限公司 | Method for playing multimedia information using user recognizing module |
| CN101415164A (en) * | 2007-10-19 | 2009-04-22 | 凤凰微电子（中国）有限公司 | Smart card and method for implementing incoming call display information |
| CN101692746A (en) * | 2009-09-18 | 2010-04-07 | 中兴通讯股份有限公司 | Method and device for operating telephone directory |
| CN101789987A (en) * | 2010-02-02 | 2010-07-28 | 华为终端有限公司 | Telephone directory processing method and user equipment |
| CN108848497A (en) * | 2018-06-01 | 2018-11-20 | 中国联合网络通信集团有限公司 | Acquisition methods, device, terminal and the computer readable storage medium of list of application |
| CN110719581A (en) * | 2018-07-12 | 2020-01-21 | 中兴通讯股份有限公司 | Control method, device and system for terminal application |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8996065B2 (en) | Method for automatically transferring an application in a mobile communication terminal of telecommunication networks | |
| CN111787521B (en) | Terminal application permission obtaining method, terminal equipment and USIM | |
| EP2461640A1 (en) | Method and integrated circuit card for managing the database by interacting with the mobile equipment | |
| US6178336B1 (en) | Subscriber identity module for a mobile telecommunications terminal, and a mobile telecommunications terminal | |
| US20130310014A1 (en) | Method and Mobile Terminal for Storing Memo During Call | |
| CN102082873B (en) | Starting method, mobile terminal and user identification card | |
| CN109246280B (en) | Address book cloud processing method and device, computer equipment and readable storage medium | |
| US10616418B2 (en) | Dynamically generated call triggers | |
| CN101997977B (en) | Method and device for enabling mobile terminal and smart card to be compatible with different network systems | |
| CN111741462A (en) | Terminal application permission change acquisition method, terminal and USIM | |
| CN111447319A (en) | Terminal number book management method, terminal and user identification module | |
| CN102572800A (en) | Method for SIM (subscriber identity module) card to automatically read information of IMEI (international mobile equipment identity) information of terminal on basis of STK (SIM application tool kit) technology | |
| CN115795544A (en) | File security attribute storage method and related device | |
| CN102223399B (en) | Contact person session presentation method based on intelligent terminal and system thereof | |
| CN106101193B (en) | Information backup method, terminal equipment, operator server and backup system | |
| CN111367476B (en) | Data reading method and device of SIM card | |
| CN111339173A (en) | Data sharing method, server and readable storage medium | |
| CN113950035A (en) | Method and terminal for dynamically updating NFC (near field communication) capability and UICC (Universal Integrated Circuit card) | |
| CN113301203A (en) | Method and device for updating historical information data based on address book | |
| CN103067850B (en) | Mobile communication service cost inquiry method and device and system | |
| CN113542350B (en) | Browsing state event downloading method, USIM, terminal and storage medium | |
| CN102542306A (en) | Method for accessing user identification card file by using mobile terminal application sub system | |
| CN113556714B (en) | Method and device for UICC to require terminal to search NFC equipment | |
| CN111050312B (en) | eSIM card operator file management method and device | |
| CN113950036B (en) | NFC capability synchronization method, UICC, terminal, equipment and medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200724 |
|
| RJ01 | Rejection of invention patent application after publication |