CN106462845B

CN106462845B - Configuration method of non-contact front end and terminal

Info

Publication number: CN106462845B
Application number: CN201580035335.XA
Authority: CN
Inventors: 李国庆; 梅敬青; 赵晓娜
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2015-04-21
Filing date: 2015-04-21
Publication date: 2020-01-17
Anticipated expiration: 2035-04-21
Also published as: CN106462845A; WO2016168989A1

Abstract

A configuration method of a non-contact front end and a terminal are provided. When the management entity determines that one or more target security units on the terminal are in a deactivated state, the management entity can inquire the stored non-contact front-end configuration applicable to the one or more target security units, and configure the non-contact front end by using a group of non-contact protocol parameters in the inquired non-contact front-end configuration without performing conflict detection and non-contact protocol parameter calculation, so that the configuration efficiency of the non-contact front end is greatly improved.

Description

Configuration method of non-contact front end and terminal

Technical Field

The invention relates to the technical field of mobile payment, in particular to a configuration method of a non-contact front end and a terminal.

Background

In recent years, mobile payment based on Near Field Communication (NFC) technology is becoming popular, and a mobile payment terminal supporting NFC communicates with a card reader (e.g., a contactless POS machine deployed in a market) through an NFC interface to complete a payment transaction. The mobile payment terminal generally includes hardware such as a Secure Element (SE), a Contactless Front-End (CLF), and an NFC antenna, and software such as a Contactless application (e.g., a payment application such as a virtual bank card) installed in the SE and a control interface installed in an operating system of the terminal. With the development of the mobile payment industry, terminals supporting multiple SEs are gradually emerging on the market, where the management of multiple SEs and multiple applications in each SE is more complex than a single SE scenario. In order to manage the payment behavior in such a multi-SE scenario, the terminal may integrate a Management Entity (ME) for serving multiple SEs and multiple applications. As shown in fig. 1, the ME has a Graphical User Interface (GUI) Interface and an SE Interface, and may receive and process a control command sent by a User through the GUI, receive messages from the SE, analyze and process the messages, and configure the CLF, so that multiple SEs and multiple payment applications may serve the User at the same time.

The CLF supports non-contact communication technologies such as Type A (ISO/IEC 14443A), Type B (ISO/IEC 14443B) and Type F (ISO/IEC18092), physical layers and link layers of the technologies are different, and a bottom layer link can be provided for non-contact application. The SE is an entity for installing the contactless application, and may install the contactless application based on the above three protocols, and the requirements of the applications on the parameters of the underlying communication protocol are different. Therefore, when a user activates one contactless application or activates one SE, conflict detection needs to be performed by the ME or the SE according to the currently activated SE and the already activated contactless applications on each SE, and the ME compares whether the parameter requirements of the target application to be activated conflict with the parameter requirements of the already activated application (already configured to the CLF), and if there is a conflict, conflict resolution is needed, and then the CLF is configured with the newly calculated parameters after resolution.

According to the prior art, collision detection and non-contact protocol parameter calculation are required when a non-contact application or SE is activated, collision detection is required for N times when N applications are activated, and according to collision detection results, a CLF (common temporary Mobile interface) may need to be reconfigured, so that the efficiency is low.

Disclosure of Invention

The embodiment of the invention provides a configuration method of a non-contact front end and a terminal, which are used for improving the configuration efficiency of the non-contact front end.

In a first aspect, a method for configuring a contactless front-end CLF is provided, where the method includes:

the method comprises the steps that a management entity ME obtains an identification and a state of a first target security element SE, wherein the state comprises an activation state and a deactivation state;

activating the first target SE when the first target SE is in a deactivated state;

the ME querying whether a first CLF configuration is saved, the first CLF configuration comprising a set of contactless protocol parameters applicable to the first target SE;

if the first CLF configuration is inquired, the ME configures the CLF by using the set of non-contact protocol parameters.

In a first possible implementation manner, before activating the first target SE when the first target SE is in the deactivated state, the method further includes: and the ME determines and deactivates the non-target SE in the activated state according to the working mode of the non-target SE in the activated state and/or the working mode of the first target SE.

With reference to the first aspect or the first possible implementation manner of the first aspect, in a second possible implementation manner, before the ME configures the CLF using the set of contactless protocol parameters, the method further includes:

the ME inquires whether the CLF configuration mode of the non-target SE in the current activation state is the CLF configuration mode of the ME;

and if the result of the query is that the ME configures the CLF, the ME generates or updates a second CLF configuration according to all contactless protocol parameters used by the CLF of the non-target SE which is in the activated state currently.

With reference to the first aspect, or the first possible implementation manner of the first aspect, or the second possible implementation manner of the first aspect, in a third possible implementation manner, the obtaining, by the ME, the identifier and the state of the first target SE includes:

the ME receives a request to activate a first SE, the request including an identification of the first target SE,

or the ME receives a request for activating at least one non-contact application, and the ME determines that the SE where the at least one non-contact application is located is the first target SE and obtains the identifier of the first target SE;

and the ME inquires the state of the first target SE according to the identifier of the first target SE.

With reference to the first aspect, or the first possible implementation manner of the first aspect, or the second possible implementation manner of the first aspect, or the third possible implementation manner of the first aspect, in a fourth possible implementation manner, the determining, by the ME, to deactivate the non-target SE currently in the activated state according to the working mode of the SE currently in the activated state and/or the working mode of the first target SE includes:

the ME determines the working mode of the non-target SE which is currently in the activated state;

the ME determines the working mode of the first target SE according to a service policy and/or the attribute of the first target SE;

and if the ME determines that the working mode of the currently activated non-target SE is a non-aggregation mode and/or the working mode of the first target SE is a non-aggregation mode, the ME determines to deactivate the currently activated non-target SE.

With reference to the first aspect, or the first possible implementation manner of the first aspect, or the second possible implementation manner of the first aspect, or the third possible implementation manner of the first aspect, or the fourth possible implementation manner of the first aspect, in a fifth possible implementation manner, the method further includes:

if the first CLF configuration is not inquired, the ME executes conflict detection and non-contact protocol parameter calculation according to the first target SE, and determines a group of non-contact protocol parameters suitable for the first target SE;

the ME configures the CLF using the calculated set of contactless protocol parameters.

With reference to the first aspect, or the first possible implementation manner of the first aspect, or the second possible implementation manner of the first aspect, or the third possible implementation manner of the first aspect, or the fourth possible implementation manner of the first aspect, or the fifth possible implementation manner of the first aspect, in a sixth possible implementation manner, the first or second CLF configuration further includes an identifier of the activated first SE, an identifier of the activated first contactless application, and a priority of the first contactless application.

With reference to the first aspect, or the first possible implementation manner of the first aspect, or the second possible implementation manner of the first aspect, or the third possible implementation manner of the first aspect, or the fourth possible implementation manner of the first aspect, or the fifth possible implementation manner of the first aspect, or the sixth possible implementation manner of the first aspect, in a seventh possible implementation manner, the method further includes:

the ME determines the CLF configuration mode of the first target SE;

and if the CLF configuration mode of the first target SE is non-ME configuration CLF, the ME grants the CLF configuration authority to the first target SE and records the identifier of the first target SE.

With reference to the first aspect, or the first possible implementation manner of the first aspect, or the second possible implementation manner of the first aspect, or the third possible implementation manner of the first aspect, or the fourth possible implementation manner of the first aspect, or the fifth possible implementation manner of the first aspect, or the sixth possible implementation manner of the first aspect, or the seventh possible implementation manner of the first aspect, in an eighth possible implementation manner, the method further includes:

when the first target SE is in an activated state, the ME determines and deactivates a non-target SE which is currently in the activated state, and changes the working mode of the first target SE;

the ME inquires whether a third CLF configuration is saved;

if the third CLF configuration is inquired, the ME configures the CLF by using a set of contactless protocol parameters in the inquired third CLF configuration.

With reference to the first aspect, or the first possible implementation manner of the first aspect, or the second possible implementation manner of the first aspect, or the third possible implementation manner of the first aspect, or the fourth possible implementation manner of the first aspect, or the fifth possible implementation manner of the first aspect, or the sixth possible implementation manner of the first aspect, or the seventh possible implementation manner of the first aspect, or the eighth possible implementation manner of the first aspect, in a ninth possible implementation manner, after the ME queries whether the first/third CLF configuration is stored, and before the ME configures the CLF using the set of non-contact protocol parameters in the queried first/third CLF configuration, the method further includes:

determining that a first target SE included in the first/third CLF configuration is available.

With reference to the first aspect, or the first possible implementation manner of the first aspect, or the second possible implementation manner of the first aspect, or the third possible implementation manner of the first aspect, or the fourth possible implementation manner of the first aspect, or the fifth possible implementation manner of the first aspect, or the sixth possible implementation manner of the first aspect, or the seventh possible implementation manner of the first aspect, or the eighth possible implementation manner of the first aspect, or the ninth possible implementation manner of the first aspect, in a tenth possible implementation manner, the method further includes:

if the ME inquires that the first target SE is in an activated state or the first target SE is in a deactivated state, and the ME determines that the working mode of the first target SE is an aggregation mode, the ME inquires whether the first non-contact application is provided with a quick activation mark or not;

and if the first non-contact application is provided with the quick activation mark, the ME configures the CLF by using the inquired first CLF configuration, and activates a first SE and/or a first non-contact application contained in the first CLF configuration.

In a second aspect, a terminal is provided, which includes: a management entity ME, a contactless frontend CLF and a first security element SE, the ME comprising:

the system comprises a first acquisition unit, a second acquisition unit and a third acquisition unit, wherein the first acquisition unit is used for acquiring the identifier and the state of a first target Security Element (SE), and the state comprises an activation state and a deactivation state;

a first activation unit for activating the first target SE;

a first querying unit, configured to query whether a first CLF configuration is stored, where the first CLF configuration includes a set of contactless protocol parameters applicable to the first target SE;

a first configuration unit, configured to configure the CLF using the set of contactless protocol parameters if the first CLF configuration is queried.

In a first possible implementation manner, the ME further includes:

the first determining unit is used for determining the working mode of the non-target SE and/or the working mode of the first target SE according to the current activated non-target SE when the first target SE is in the deactivated state;

the first activation unit is further configured to deactivate the non-target SE currently in an activated state.

With reference to the second aspect or the first possible implementation manner of the second aspect, in a second possible implementation manner, the ME further includes:

the second query unit is used for querying whether the CLF configuration mode of the non-target SE currently in the activated state is the CLF configuration mode of the ME;

and the generating or updating unit is used for generating or updating a second CLF configuration according to all contactless protocol parameters used by the CLF of the non-target SE which is in the activated state currently if the result of the query is the ME configuration CLF.

With reference to the second aspect or the first possible implementation manner of the second aspect or the second possible implementation manner of the second aspect, in a third possible implementation manner, the first obtaining unit includes:

a receiving unit to receive a request to activate a first SE, the request including an identification of the first target SE,

or the receiving unit is further configured to receive a request to activate at least one contactless application;

a second determining unit, configured to determine an SE in which the at least one non-contact application is located as the first target SE;

the second acquisition unit is used for acquiring the identifier of the first target SE;

and the third query unit is used for querying the state of the first target SE according to the identification of the first target SE.

With reference to the second aspect or the first possible implementation manner of the second aspect, or the second possible implementation manner of the second aspect, or the third possible implementation manner of the second aspect, in a fourth possible implementation manner, the first determining unit includes:

a third determining unit, configured to determine an operating mode of the currently activated non-target SE;

a fourth determining unit, configured to determine, according to a service policy and/or an attribute of the first target SE, an operating mode of the first target SE;

a fifth determining unit, configured to determine to deactivate the currently activated non-target SE if it is determined that the working mode of the currently activated non-target SE is a non-aggregation mode and/or the working mode of the first target SE is a non-aggregation mode.

With reference to the second aspect or the first possible implementation manner of the second aspect, or the second possible implementation manner of the second aspect, or the third possible implementation manner of the second aspect, or the fourth possible implementation manner of the second aspect, in a fifth possible implementation manner, the ME further includes:

a sixth determining unit, configured to, if the first CLF configuration is not queried, perform collision detection and non-contact protocol parameter calculation according to the first target SE, and determine a set of non-contact protocol parameters applicable to the first target SE;

a second configuration unit for configuring the CLF using the calculated set of contactless protocol parameters.

With reference to the second aspect, or the first possible implementation manner of the second aspect, or the second possible implementation manner of the second aspect, or the third possible implementation manner of the second aspect, or the fourth possible implementation manner of the second aspect, or the fifth possible implementation manner of the second aspect, in a sixth possible implementation manner, the first or second CLF configuration further includes an identifier of the activated first SE, an identifier of the activated first contactless application, and a priority of the first contactless application.

With reference to the second aspect, or the first possible implementation manner of the second aspect, or the second possible implementation manner of the second aspect, or the third possible implementation manner of the second aspect, or the fourth possible implementation manner of the second aspect, or the fifth possible implementation manner of the second aspect, or the sixth possible implementation manner of the second aspect, in a seventh possible implementation manner, the ME further includes:

a seventh determining unit, configured to determine a CLF configuration manner of the first target SE;

the granting unit is configured to grant a CLF configuration authority to the first target SE if the CLF configuration mode of the first target SE is a non-ME configuration CLF;

a recording unit for recording an identification of the first target SE.

With reference to the second aspect, or the first possible implementation manner of the second aspect, or the second possible implementation manner of the second aspect, or the third possible implementation manner of the second aspect, or the fourth possible implementation manner of the second aspect, or the fifth possible implementation manner of the second aspect, or the sixth possible implementation manner of the second aspect, or the seventh possible implementation manner of the second aspect, in an eighth possible implementation manner, the ME further includes:

an eighth determining unit, configured to determine to deactivate a non-target SE currently in an activated state when the first target SE is in the activated state;

the second activation unit is used for deactivating the non-target SE which is in the activation state currently;

a changing unit, configured to change a working mode of the first target SE;

a fourth querying unit, configured to query whether a third CLF configuration is stored;

a third configuration unit, configured to configure the CLF using a set of contactless protocol parameters in the queried third CLF configuration if the third CLF configuration is queried.

With reference to the second aspect, or the first possible implementation manner of the second aspect, or the second possible implementation manner of the second aspect, or the third possible implementation manner of the second aspect, or the fourth possible implementation manner of the second aspect, or the fifth possible implementation manner of the second aspect, or the sixth possible implementation manner of the second aspect, or the seventh possible implementation manner of the second aspect, or the eighth possible implementation manner of the second aspect, in a ninth possible implementation manner, the ME further includes:

a ninth determining unit for determining that the first target SE included in the first/third CLF configuration is available.

With reference to the second aspect, or the first possible implementation manner of the second aspect, or the second possible implementation manner of the second aspect, or the third possible implementation manner of the second aspect, or the fourth possible implementation manner of the second aspect, or the fifth possible implementation manner of the second aspect, or the sixth possible implementation manner of the second aspect, or the seventh possible implementation manner of the second aspect, or the eighth possible implementation manner of the second aspect, or the ninth possible implementation manner of the second aspect, in a tenth possible implementation manner, the ME further includes:

a fourth querying unit, configured to query whether the first contactless application is provided with a fast activation flag if it is queried that the first target SE is in an activated state or that the first target SE is in a deactivated state and the ME determines that the working mode of the first target SE is an aggregation mode;

a fourth configuration unit, configured to, if the first contactless application is provided with the quick activation flag, configure the CLF by using the queried first CLF configuration by the ME;

a third activation unit for activating the first SE and/or the first contactless application comprised by the first CLF configuration.

In a third aspect, a terminal is provided, where the terminal includes: memory, a processor, a contactless front-end CLF and at least one security element SE, said processor being adapted to perform the steps of:

obtaining an identifier and a state of a first target Security Element (SE), wherein the state comprises an activation state and a deactivation state;

querying whether a first CLF configuration is saved, the first CLF configuration comprising a set of contactless protocol parameters applicable to the first target SE;

configuring the CLF using the set of contactless protocol parameters if the first CLF configuration is queried.

In a first possible implementation manner, the processor is configured to perform, before the step of activating the first target SE when the first target SE is in the deactivated state, the following steps: determining and deactivating the non-target SE currently in the activated state according to the working mode of the SE currently in the activated state and/or the working mode of the first target SE

With reference to the third aspect or the first possible implementation manner of the third aspect, in a second possible implementation manner, before the processor is configured to configure the CLF using the set of contactless protocol parameters, the processor is further configured to perform the following steps:

inquiring whether the CLF configuration mode of the non-target SE in the current activated state is the CLF configuration mode of the processor;

and if the processor configures the CLF as a result of the query, generating or updating a second CLF configuration according to all contactless protocol parameters used by the CLF applicable to the non-target SE currently in the activated state, so that the processor can be used when the processor activates the first SE applicable to the second CLF configuration again.

With reference to the third aspect or the first possible implementation manner of the third aspect or the second possible implementation manner of the third aspect, in a third possible implementation manner, the processor is configured to execute the step of obtaining the identifier of the first target SE and the state thereof, and includes:

receiving a request to activate a first SE, the request including an identification of the first target SE,

or receiving a request for activating at least one non-contact application, determining an SE in which the at least one non-contact application is located as the first target SE, and obtaining an identifier of the first target SE;

and inquiring the state of the first target SE according to the identification of the first target SE.

With reference to the third aspect, or the first possible implementation manner of the third aspect, or the second possible implementation manner of the third aspect, or the third possible implementation manner of the third aspect, in a fourth possible implementation manner, the determining, by the processor, to deactivate the currently activated non-target SE according to the working mode of the currently activated SE and/or the working mode of the first target SE includes:

determining the working mode of the non-target SE currently in the activated state;

determining a working mode of the first target SE according to a service policy and/or the attribute of the first target SE;

and if the working mode of the currently activated non-target SE is determined to be a non-aggregation mode and/or the working mode of the first target SE is determined to be a non-aggregation mode, determining to deactivate the currently activated non-target SE.

With reference to the third aspect or the first possible implementation manner of the third aspect, or the second possible implementation manner of the third aspect, or the third possible implementation manner of the third aspect, or the fourth possible implementation manner of the third aspect, in a fifth possible implementation manner, the processor is further configured to execute the following steps:

if the first CLF configuration is not inquired, performing conflict detection and non-contact protocol parameter calculation according to the first target SE, and determining a group of non-contact protocol parameters suitable for the first target SE;

configuring the CLF using the calculated set of contactless protocol parameters.

With reference to the third aspect, or the first possible implementation manner of the third aspect, or the second possible implementation manner of the third aspect, or the third possible implementation manner of the third aspect, or the fourth possible implementation manner of the third aspect, or the fifth possible implementation manner of the third aspect, in a sixth possible implementation manner, the first or second CLF configuration further includes an identifier of the activated first SE, an identifier of the activated first contactless application, and a priority of the first contactless application.

With reference to the third aspect, or the first possible implementation manner of the third aspect, or the second possible implementation manner of the third aspect, or the third possible implementation manner of the third aspect, or the fourth possible implementation manner of the third aspect, or the fifth possible implementation manner of the third aspect, or the sixth possible implementation manner of the third aspect, in a seventh possible implementation manner, the processor is further configured to execute the following steps:

determining a CLF configuration mode of the first target SE;

and if the CLF configuration mode of the first target SE is the non-processor configuration CLF, granting the CLF configuration authority to the first target SE and recording the identifier of the first target SE.

With reference to the third aspect, or the first possible implementation manner of the third aspect, or the second possible implementation manner of the third aspect, or the third possible implementation manner of the third aspect, or the fourth possible implementation manner of the third aspect, or the fifth possible implementation manner of the third aspect, or the sixth possible implementation manner of the third aspect, or the seventh possible implementation manner of the third aspect, in an eighth possible implementation manner, the processor is further configured to execute the following steps:

when the first target SE is in an activated state, determining and deactivating a non-target SE which is currently in the activated state, and changing the working mode of the first target SE;

inquiring whether a third CLF configuration is stored;

and if the third CLF configuration is inquired, configuring the CLF by using a set of non-contact protocol parameters in the inquired third CLF configuration.

With reference to the third aspect, or the first possible implementation manner of the third aspect, or the second possible implementation manner of the third aspect, or the third possible implementation manner of the third aspect, or the fourth possible implementation manner of the third aspect, or the fifth possible implementation manner of the third aspect, or the sixth possible implementation manner of the third aspect, or the seventh possible implementation manner of the third aspect, or the eighth possible implementation manner of the third aspect, in a ninth possible implementation manner, after the step of querying whether the first/third CLF configuration is saved is executed by the processor, and before the step of configuring the CLF by using a set of non-contact protocol parameters in the queried first/third CLF configuration is executed by the processor, the following steps are further executed:

With reference to the third aspect, or the first possible implementation manner of the third aspect, or the second possible implementation manner of the third aspect, or the third possible implementation manner of the third aspect, or the fourth possible implementation manner of the third aspect, or the fifth possible implementation manner of the third aspect, or the sixth possible implementation manner of the third aspect, or the seventh possible implementation manner of the third aspect, or the eighth possible implementation manner of the third aspect, or the ninth possible implementation manner of the third aspect, in a tenth possible implementation manner, the processor is further configured to execute the following steps:

if the first target SE is inquired to be in an activated state or the first target SE is in a deactivated state, and the working mode of the first target SE is determined to be an aggregation mode, inquiring whether the first non-contact application is provided with a quick activation mark;

using the queried fast activation flag if the first contactless application is provided with the fast activation flag

The first CLF configuration configures the CLF and activates a first SE and/or a first contactless application comprised by the first CLF configuration.

Therefore, according to the configuration method of the non-contact front end and the terminal provided by the embodiment of the invention, when the management entity determines that one or more target security units on the terminal are in a deactivated state, the management entity can inquire the stored non-contact front end configuration applicable to the one or more target security units, and configure the non-contact front end by using a group of non-contact protocol parameters in the inquired non-contact front end configuration, without performing conflict detection and non-contact protocol parameter calculation, thereby greatly improving the configuration efficiency of the non-contact front end.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings needed in the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings without creative efforts.

FIG. 1 is a schematic diagram of an interface and functions of a management entity;

fig. 2 is a schematic flowchart of a method for configuring a contactless frontend according to an embodiment of the present invention;

FIG. 3 is a flowchart illustrating another method for configuring a contactless frontend according to an embodiment of the present invention;

fig. 4 is a schematic structural diagram of a terminal according to an embodiment of the present invention;

fig. 5 is a schematic structural diagram of a management entity in another terminal according to an embodiment of the present invention;

fig. 6 is a schematic structural diagram of another terminal according to an embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

The terminal in the embodiment of the invention refers to a terminal with an NFC payment function, such as an NFC mobile phone, an NFC tablet, an NFC watch and the like. The terminal can be connected with one or more SEs, one SE can be provided with one or more non-contact applications, and the ME manages the SE and the applications on the terminal. SE refers to a tamper-resistant operating environment, typically a secure microcontroller chip. The chip can safely store and run the application, and save the data such as the key and the certificate related to the application without being tampered and illegally accessed, and meanwhile, the chip can also save the access rule of confidential data and the like. SE is a concept in a specification set by global platform international standards organization (GP), and SE is related to cee (card Emulation environment) in GP related specification, and may refer to each other; the SE may also refer to concepts such as NFC Execution Environment (NFCEE), HCI host, and the like. NFCEE is a term used in NCI specifications set by the NFC Forum (NFC Forum); the HCI Host refers to a Host (Host) such as a universal integrated Circuit Card (abbreviated as "universal integrated Circuit Card") in the HCI specification set by the European Telecommunications Standards Institute (ETSI), an Embedded Secure element (abbreviated as "eSE"), a Secure Digital Memory Card (abbreviated as "SD Card"), and the like. CLF refers to a physical module in a terminal for analog signal processing and transmission protocol processing for near field communication, through which a card reader can exchange data with an SE on the terminal. CLF is a concept in a related specification formulated by ETSI, and is equivalent to an NFC Controller (NFC Controller) in a specification formulated by NFC forum. A Contactless Application (CL App) generally refers to an Application installed in a SE and capable of performing a transaction with a Card reader using a Contactless interface provided by a CLF, and for example, a public transport Card Application and an electronic cash Card Application installed in a mobile phone Universal Integrated Circuit Card (UICC) SE are Contactless applications. The contactless application is a concept defined in specifications laid down by the GP, and is also called NFC Service (NFC Service) in relevant specifications laid down by the NFC forum.

The ME of the embodiment of the present invention has two operation modes, an Aggregated (Aggregated) mode and a Non-Aggregated (Non-Aggregated) mode:

the ME's aggregation mode is a mode of operation when the ME manages multiple SEs in which a user may select multiple applications installed on multiple SEs to activate and use these services simultaneously, without the user perceiving that these services are from multiple SEs. In other words, multiple SEs may be activated simultaneously in this mode, as may applications on different SEs. The ME in this mode needs to configure the CLF according to all activated contactless applications.

The non-aggregated mode of the ME is another mode of operation when the ME manages multiple SEs. In this mode, the user can only select and activate a group of applications from the same SE. In other words, multiple SEs may not be activated at the same time in this mode, only one SE may be activated, and only the applications on the activated SE may be selected, activated, and serviced by the user.

In the Aggregated mode, the CLF can only be configured by the ME, and in this mode only the ME entity can collect the Contactless Protocol Parameter (contact Protocol Parameter) requirements from multiple SEs. In Non-Aggregated mode, however, the CLF may be configured by the ME or by the SE, since only one SE may be activated.

While the aggregation mode and non-aggregation mode are for both ME and SE. The SE can be divided according to whether the interface with the ME is supported or not, if the SE supports the interface with the ME, the SE can work in both aggregation and non-aggregation modes, and the SE can send a request to the ME through the interface with the ME to request to work in a specific mode; and the SE which does not support the ME interface cannot utilize the conflict detection function of the ME, and only can work in a non-aggregation mode and configure the CLF by itself. The operating mode of the SE in the active state is consistent with the operating mode of the ME.

The management entity ME in the present invention is an entity for managing multiple SEs and non-contact applications on the same terminal, and specifically, the ME may be run in a host controller DH (device host) of the terminal, where the DH is responsible for managing the entire device, including management of an NFC controller, such as initialization, configuration, or power management. In the smart phone, the master controller DH may correspond to a CPU of the phone; DH is a term used in NCI specifications formulated by the NFC Forum (NFC Forum), and may correspond to an end Host (Terminal Host) in HCI specifications formulated by the European Telecommunications Standards Institute (ETSI); in addition, if the Management Entity (ME) in the specification established by the Global Platform international standard organization (GP) is implemented in the Terminal Host, DH may be called a Management Host (MH)

The ME may also run on a near field communication controller NFCC (NFC controller), which is an entity responsible for data transmission of the NFC chip and is usually directly referred to as the NFC chip. NFCC is a term used in NCI specifications set by the NFC Forum (NFC Forum), and may correspond to a Contactless Front-end (CLF) in HCI specifications set by the European Telecommunications Standards Institute (ETSI), when a Host Controller (Host Controller) in HCI is to be implemented on the NFCC.

The ME may even run within the security element se (secure element).

When the ME determines that one or more target security units on the terminal are in a deactivation state, if the ME determines that the non-target security unit in the activation state is required to be deactivated, the management entity can inquire the stored non-contact front-end configuration suitable for the one or more target security units, and configure the non-contact front-end by using a group of non-contact protocol parameters in the inquired non-contact front-end configuration without collision detection and non-contact protocol parameter calculation, thereby greatly improving the configuration efficiency of the non-contact front-end.

The following describes in detail a configuration method of a contactless frontend according to an embodiment of the present invention with reference to fig. 2 to 3:

referring to fig. 2, a schematic flow chart of a method for configuring a contactless front end according to an embodiment of the present invention is shown, where the method includes the following steps:

step S101, a management entity ME obtains an identifier and a state of a first target security element SE, wherein the state comprises an activation state and a deactivation state.

The ME obtains the identifier of the first target SE, which may be that the ME receives a request for activating one or more SEs from a GUI interface, and the SE corresponding to the SE identifier contained in the request is the SE to be activated, namely the target SE; or after the ME receives a request for activating one or more non-contact applications from the GUI interface, the ME obtains an identifier of an SE in which the one or more non-contact applications are located, where the SE corresponding to the identifier of the SE is a target SE; the ME may query the state of the target SE using the identification of the target SE.

Step S102, when the first target SE is in a deactivation state, activating the first target SE.

Before the first target SE is activated, the terminal may not have the non-target SE in the activated state, or may have the non-target SE in the activated state, and at this time, before the first target SE is activated, the non-target SE needs to be deactivated. The specific scenario for deactivating the currently activated non-target SE is as follows:

in the scenario of this embodiment, the ME needs to determine to deactivate the SE currently in the activated state and activate the target SE according to the working mode of the SE currently in the activated state or the working mode of the target SE. One scenario is that the currently active SE is operating in non-aggregation mode with CLF configured in ME configuration CLF or non-ME configuration CLF, and the target SE is required to operate in aggregation mode with CLF configured in ME configuration CLF. In the non-aggregation mode, only one SE may be activated, and the target SE is in a deactivated state, and obviously, the SE currently in the activated state is not the same SE as the target SE. However, when the SE currently in the active state operates in the non-aggregation mode, only one SE currently in the active state is needed, and thus the SE currently in the active state needs to be deactivated. The other scenario is that no matter what kind of working mode and CLF configuration mode the currently activated SE is, the target SE is required to work in the non-aggregation mode, the CLF configuration mode configures the CLF for ME, and since the target SE works in the non-aggregation mode and is in the deactivation state, other SEs are not allowed to be activated at the same time as the target SE, the currently activated SE needs to be deactivated.

Step S103, the ME queries whether a first CLF configuration is saved, where the first CLF configuration includes a set of contactless protocol parameters applicable to the first target SE.

Since all currently activated SEs are deactivated, it cannot be determined that the contactless protocol parameters currently configured to the CLF are applicable to the newly activated target SE, and therefore, the CLF needs to be reconfigured according to the newly activated target SE.

In this embodiment, the terminal may pre-store configurations of CLFs in a specific scene, where the CLF configurations may be stored as CLF configuration files (profiles), and the CLF configurations include an identifier of one or more SEs activated in the specific scene, an identifier of one or more activated contactless applications, priorities of the contactless applications, and a set of contactless protocol parameters used when performing CLF configuration according to the SEs and the contactless applications.

In this embodiment, when the CLF configuration is to be performed on the target SE, whether the CLF configuration including the target SE identifier is stored is queried. If the ME receives a request for activating the non-contact application, the ME queries whether the CLF configuration contains the target SE identifier and the identifier of the non-contact application to be activated when querying the CLF configuration. Since there may be more than one CLF configuration saved containing the target SE identifier, when the CLF configuration is selected, the CLF configuration is required to contain the target SE identifier and the number of SE identifiers other than the target SE identifier is as small as possible.

Step S104, if the first CLF configuration is queried, the ME configures the CLF using the set of contactless protocol parameters.

If the stored CLF configuration is inquired, the ME configures the CLF by using the group of non-contact protocol parameters in the stored CLF configuration, collision detection and non-contact protocol parameter calculation are not needed, and the CLF is directly configured to the CLF, so that the configuration efficiency of the non-contact front end is greatly improved.

According to the configuration method of the non-contact front end provided by the embodiment of the invention, when the management entity determines that one or more target security units on the terminal are in a deactivated state, the management entity can inquire the stored non-contact front end configuration suitable for the one or more target security units, and configure the non-contact front end by using a group of non-contact protocol parameters in the inquired non-contact front end configuration without collision detection and non-contact protocol parameter calculation, so that the configuration efficiency of the non-contact front end is greatly improved.

Referring to fig. 3, a schematic flow chart of another non-contact front end configuration method according to an embodiment of the present invention is shown, where the method includes the following steps:

in step S201, the ME receives a request for activating at least one contactless application, and the ME determines that the SE in which the at least one contactless application is located is the first target SE and obtains an identifier of the first target SE.

The present embodiment is described by taking activation of a non-contact application as an example. The contactless Application has a unique Application Identifier (AID for short). And the ME receives an activation request of the non-contact application through the GUI interface, wherein the request carries the AID. The number of the contactless applications to be activated may be one or plural.

The ME queries a target SE where the non-contact application AID is located, and a plurality of non-contact applications can be located on one target SE or a plurality of target SEs.

Step S202, the ME inquires whether the first target SE is in an activated state or not according to the identifier of the first target SE, and if not, the ME returns to the step S203; if yes, go to step S212 or S215.

And the ME inquires the activation state of the target SE and performs different processing according to the different activation states of the target SE.

Step S203, the ME determines whether the working mode of the first target SE is a non-aggregation mode, if so, the ME goes to step S204; otherwise, go to step S212.

When the ME inquires that the target SE is in the deactivation state, the ME further determines the working mode of the target SE.

The ME may determine the operating mode of the target SE based on the service policy and/or the attributes of the target SE:

the service policies may include:

a) ensuring that the services provided by the same service operator as much as possible are available at the same time, corresponding to the activation of a single SE, the ME works in a non-aggregation mode, thus reducing the influence of other SEs on a target SE;

b) ensuring that services provided by a plurality of service operators are available at the same time, wherein the services on a plurality of SEs are all used at the time corresponding to the aggregation mode, and the benefits of the plurality of service operators can be ensured to be taken into account;

attributes of the target SE, including:

a) the target SE only supports the non-aggregation mode, and the CLF is configured by the SE;

b) the target SE only supports a non-aggregation mode, and the CLF can be configured by the ME;

c) the target SE supports the aggregation and non-aggregation modes, and the CLF can be configured using ME.

For example, scenario a: the target SE only supports the non-aggregation mode, the working mode of the SE or the ME can be determined according to the attributes, and it needs to be explained that the working mode of the SE in the activated state is consistent with the working mode of the ME; scene B: the service strategy is that the most SEs are required to work simultaneously, the SE supports aggregation or non-aggregation, and the ME determines that the ME and the SE work in an aggregation mode at the moment; scene C: the service policy requires that applications on one SE be used as much as possible, the SE supports aggregation and non-aggregation, and the ME and SE should operate in non-aggregation mode.

Different processes are performed depending on whether the operation mode of the target SE is the aggregation mode or the non-aggregation mode.

Step S204, if the ME determines that the working mode of the non-target SE currently in the activated state is the non-aggregation mode and/or the working mode of the first target SE is the non-aggregation mode, the ME determines to deactivate the non-target SE currently in the activated state.

The ME may query the operating mode of the SE currently in the active state. This step is the same as step S102 of the previous embodiment, and is not repeated here.

Step S205, if the ME queries that the CLF configuration mode of the currently activated non-target SE is ME configuration CLF, the ME generates or updates the second CLF configuration according to all the contactless protocol parameters used by the CLF of the currently activated non-target SE.

Before deactivating the non-target SE currently in the activated state, if the ME queries that the CLF configuration mode of the non-target SE currently in the activated state is the ME configuration CLF, the ME generates or updates a second CLF configuration according to all non-contact protocol parameters used by the CLF of the non-target SE currently in the activated state, namely, if the second CLF configuration does not exist, the ME generates the second CLF configuration according to all non-contact protocol parameters used by the CLF of the non-target SE currently in the activated state; and if the second CLF configuration already exists, updating the corresponding configuration parameters in the second CLF configuration according to all contactless protocol parameters used by the CLF which is suitable for the non-target SE in the activated state. And can thus be used directly when activating the first SE for which this CLF configuration is applicable. The CLF configuration that is saved includes an identification of the currently active SE or SEs, an identification of the currently active contactless application or SEs, a priority of the contactless applications, and a set of contactless protocol parameters used in CLF configuration according to the SEs and contactless applications.

Step S206, the ME inquires whether the first target SE uses the ME configuration CLF, if yes, the process goes to step S207; otherwise, go to step S211.

Since the ME has determined in step S204 that the working mode of the target SE is the non-aggregation mode, there may be two CLF configuration modes for the target SE, i.e. ME configuration CLF or non-ME configuration CLF, where non-ME configuration CLF generally refers to the configuration of CLF by SE. There may be two different processing modes according to the different CLF configuration modes of the target SE.

Step S207, the ME queries whether the first CLF configuration is saved, and if so, goes to step S208; otherwise, go to step S213.

In step S208, the ME determines that the first target SE included in the first CLF configuration is available.

The ME inquires that there may be a plurality of CLF configurations stored with the identification of the target SE, and when the ME selects the stored CLF configuration, the principle that the CLF configuration contains the least identification of other SEs except the identification of the target SE is taken as the principle. The ME then needs to determine that every SE contained in this CLF configuration to be used is available, i.e. can be activated.

In step S209, the ME configures the CLF using a set of contactless protocol parameters.

If the ME inquires that the target SE uses the ME configuration CLF, the ME performs CLF configuration on the target SE. Steps S207 and S209 are the same as steps S103 and S104 of the foregoing embodiment, respectively, and are not described again here.

In step S210, the ME activates the first SE and the first contactless application comprised by the first CLF configuration.

After determining that each SE included in the CLF configuration is available, the ME configures the CLF using the parameters of the contactless protocol in the CLF configuration and activates all SEs included in the CLF configuration, or activates the contactless application that requests activation if all SEs included in the CLF configuration are in an activated state.

In step S211, the ME grants the CLF configuration authority to the first target SE and records the identifier of the first SE.

When the ME inquires that the target SE uses the non-ME configuration CLF, namely the SE configures the CLF, the ME grants the CLF configuration authority to the target SE, the SE configures the CLF and records the identification of the target SE.

Step S212, the ME queries whether the first non-contact application has the quick activation flag, if so, go to step S213; otherwise, go to step S210.

If the ME inquires that the target SE is in the activated state or the target SE is in the deactivated state in step S202, and the ME determines that the working mode of the target SE is the aggregation mode, at this time, the ME inquires whether the contactless application to be activated is provided with the fast activation flag, that is, for the scenario that the target SE is in the activated state, the target SE does not need to be deactivated any more, and for the scenario that the working mode of the target SE is the aggregation mode, the target SE may coexist with the SE currently in the activated state, and then the contactless application and/or the target SE may be considered to be fast activated. Of course, if the contactless application does not set the fast active flag, then the process goes to step S213, and the ME performs conventional collision detection and contactless protocol parameter calculation on the target SE.

Under the condition that certain conditions are met, the non-contact application is quickly activated, and the CLF is configured by adopting the stored CLF configuration, so that the CLF configuration efficiency can be further improved.

In step S213, the ME performs collision detection and contactless protocol parameter calculation according to the first target SE, and determines a set of contactless protocol parameters applicable to the first target SE.

In step S214, the ME configures the CLF using the calculated set of contactless protocol parameters.

If the ME does not inquire that the CLF configuration applicable to the target SE is stored in step S207, the ME performs conflict detection and non-contact protocol parameter calculation according to the target SE and the application to be activated, where the conflict detection means whether the AID of the application on the activation target SE conflicts or whether the AID of the application that is currently activated conflicts or whether the protocol parameter conflicts; the contactless protocol parameter calculation refers to a set of contactless protocol parameters calculated by the ME that are suitable for all SEs and contactless applications that are currently active. And after the ME calculates a group of non-contact protocol parameters, the CLF is configured by adopting the group of non-contact protocol parameters. In step S215, the ME determines and deactivates the non-target SE currently in the activated state, and changes the operating mode of the first target SE.

If the ME inquires in step S202 that the target SE is in the active state, but the ME receives a request to change the operating mode of the target SE (e.g., change the aggregation mode to the non-aggregation mode), at which point the active SE may not be the target SE, the ME deactivates the currently active non-target SE.

In step S216, if the ME inquires that the third CLF configuration is stored, the ME configures the CLF by using a set of contactless protocol parameters in the inquired third CLF configuration. The third CLF configuration is one CLF configuration applicable to the target SE.

After the ME deactivates the non-target SE currently in the activated state, only the target SE in the activated state remains, the ME queries the CLF configuration containing the target SE, and the CLF is configured by adopting a group of non-contact protocol parameters in the queried CLF configuration, so that the CLF can be rapidly configured.

In addition to the above situation, if the working mode of the currently active SE is aggregation mode, the CLF configuration mode is ME configuration CLF, and the working mode of the target SE is non-aggregation mode, and the CLF configuration mode is non-ME configuration CLF, or the working mode of the currently active SE is non-aggregation mode, the CLF configuration mode is ME configuration CLF, and the working mode of the target SE is non-aggregation mode, and the CLF configuration mode is non-ME configuration CLF, the CLF may also be configured by using the saved CLF configuration.

According to the non-contact front end configuration method provided by the embodiment of the invention, according to the working modes of the non-target SE and the target SE which are currently in an activated state and the CLF configuration mode thereof, when the non-target safety unit which is currently in the activated state is determined to be deactivated and the CLF can be configured by adopting the stored non-contact front end configuration which is suitable for the target SE, the non-contact front end is configured by adopting a group of non-contact protocol parameters in the non-contact front end configuration, collision detection and non-contact protocol parameter calculation are not required, and the configuration efficiency of the non-contact front end can be greatly improved.

The following describes in detail a terminal implementing the configuration method of the contactless front end according to an embodiment of the present invention with reference to fig. 4 to 6:

referring to fig. 4, a schematic structural diagram of a terminal according to an embodiment of the present invention is shown, where the terminal 1000 includes a management entity ME11, a security unit SE12 and a contactless front-end CLF13, where the security unit SE12 and the contactless front-end CLF13 are respectively connected to an ME11, and the SE12 is connected to a CLF 13. Wherein the ME11 includes:

the first obtaining unit 111 is configured to obtain an identifier and a state of the first target security element SE, where the state includes an activation state and a deactivation state.

The first obtaining unit 111 obtains an identifier of a first target SE, where the identifier may be that an ME receives a request for activating one or more SEs from a GUI interface, and an SE corresponding to an SE identifier included in the request is an SE to be activated, that is, a target SE; or after the ME receives a request for activating one or more non-contact applications from the GUI interface, the ME obtains an identifier of an SE in which the one or more non-contact applications are located, where the SE corresponding to the identifier of the SE is a target SE; the first obtaining unit 111 may use the identification of the target SE to query the status of the target SE.

A first activation unit 112 for activating the first target SE.

Before the first activating unit 112 activates the first target SE, there may be no non-target SE in the activated state on the terminal, or there may be a non-target SE in the activated state, and at this time, before the first target SE is activated, the non-target SE needs to be deactivated. The specific scenario for deactivating the currently activated non-target SE is as follows:

in the scenario of this embodiment, it is necessary to determine to deactivate the currently activated SE and activate the target SE according to the operating mode of the currently activated SE or the operating mode of the target SE. One scenario is that the currently active SE is operating in non-aggregation mode with CLF configured in ME configuration CLF or non-ME configuration CLF, and the target SE is required to operate in aggregation mode with CLF configured in ME configuration CLF. In the non-aggregation mode, only one SE may be activated, and the target SE is in a deactivated state, and obviously, the SE currently in the activated state is not the same SE as the target SE. However, if the SE currently in the active state is operating in the non-aggregation mode, there is only one SE currently in the active state, and therefore, the first activation unit 112 needs to deactivate the SE currently in the active state. Another scenario is that, no matter what kind of working mode and CLF configuration mode the currently activated SE is, the target SE is required to work in the non-aggregation mode, and the CLF configuration mode configures the CLF for ME, and since the target SE works in the non-aggregation mode and is in the deactivation state, other SEs are not allowed to be activated at the same time as the target SE, the first activation unit 113 needs to deactivate the currently activated SE.

A first querying unit 113, configured to query whether a first CLF configuration is stored, where the first CLF configuration includes a set of contactless protocol parameters applicable to the first target SE.

In this embodiment, when the CLF configuration is to be performed on the target SE, the first querying unit 114 queries whether the CLF configuration containing the target SE identifier is stored. If the ME receives a request for activating the non-contact application, the ME queries whether the CLF configuration contains the target SE identifier and the identifier of the non-contact application to be activated when querying the CLF configuration. Since there may be more than one CLF configuration saved containing the target SE identifier, when the CLF configuration is selected, the CLF configuration is required to contain the target SE identifier and the number of SE identifiers other than the target SE identifier is as small as possible.

A first configuration unit 114, configured to configure the CLF using the set of contactless protocol parameters if the first CLF configuration is queried.

If the stored CLF configuration is found, the first configuration unit 115 configures the CLF using the set of contactless protocol parameters in the stored CLF configuration, and directly configures the CLF without performing collision detection and contactless protocol parameter calculation, thereby greatly improving the configuration efficiency of the contactless front end.

According to the terminal provided by the embodiment of the invention, when the management entity determines that one or more target security units on the terminal are in a deactivated state, the management entity can inquire the stored non-contact front-end configuration suitable for the one or more target security units, and configure the non-contact front-end by using a group of non-contact protocol parameters in the inquired non-contact front-end configuration without collision detection and non-contact protocol parameter calculation, so that the configuration efficiency of the non-contact front-end is greatly improved.

Referring to fig. 5, a schematic structural diagram of a management entity in another terminal according to an embodiment of the present invention is shown, where the terminal also includes a management entity ME21, a security element SE and a contactless front-end CLF, where the security element SE and the contactless front-end CLF are respectively connected to an ME21, and the SE is further connected to the CLF. Wherein, the management entity 21 includes:

the first obtaining unit 211 is configured to obtain an identifier and a state of the first target security element SE, where the state includes an activation state and a deactivation state.

In the present embodiment, the first acquisition unit 211 includes a receiving unit 2111, a second determination unit 2112, a second acquisition unit 2113, and a third inquiry unit 2114.

A receiving unit 2111 for receiving a request to activate at least one contactless application.

The present embodiment is described by taking activation of a non-contact application as an example. The contactless Application has a unique Application Identifier (AID for short). The receiving unit 2111 receives, through the GUI interface, an activation request of the contactless application, the AID being carried in the request. The number of the contactless applications to be activated may be one or plural.

A second determining unit 2112, configured to determine that the SE in which the at least one contactless application is located is the target SE.

A second obtaining unit 2113, configured to obtain an identification of the target SE.

The second determining unit 2112 determines a target SE in which the contactless application AID is located, and a plurality of contactless applications may be located on one target SE or a plurality of target SEs.

A third querying unit 2114, configured to query the status of the first target SE according to the identifier of the first target SE.

The third query unit 2114 queries the activation state of the target SE, and performs different processing according to the activation state of the target SE.

In another embodiment, the receiving unit 2111 is further configured to receive a request for activating a first SE, where the request includes an identification of the first target SE.

The receiving unit 2111 directly connects to the third inquiring unit 2114.

A first determining unit 212, configured to determine to deactivate the non-target SE currently in the activated state according to an operating mode of the SE currently in the activated state and/or an operating mode of the first target SE when the first target SE is in the deactivated state.

In the present embodiment, the first determination unit 212 includes a third determination unit 2121, a fourth determination unit 2122, and a fifth determination unit 2123.

A third determining unit 2121, configured to determine an operating mode of the currently activated non-target SE.

The ME may query the operating mode of the SE currently in the active state.

A fourth determining unit 2122, configured to determine, according to a service policy and/or an attribute of the first target SE, an operating mode of the first target SE.

When the third inquiring unit 2114 inquires that the target SE is in the deactivated state, the fourth determining unit 2122 further determines the operation mode of the target SE.

The fourth determining unit 2122 may determine, according to the service policy and/or the attribute of the target SE, an operating mode of the target SE:

the service policies may include:

attributes of the target SE, including:

A fifth determining unit 2123, configured to determine to deactivate the currently activated non-target SE if it is determined that the working mode of the currently activated non-target SE is a non-aggregation mode and/or the working mode of the first target SE is a non-aggregation mode.

A first activating unit 213, configured to deactivate the non-target SE currently in the activated state and activate the first target SE.

A first querying unit 214, configured to query whether a first CLF configuration is saved, where the first CLF configuration includes a set of contactless protocol parameters applicable to the first target SE.

The first querying unit 214 queries that there may be multiple CLF configurations stored with identifiers including the target SE, and when the ME selects a stored CLF configuration, the principle that the CLF configuration includes the least SE identifiers other than the target SE identifier is used.

A ninth determining unit 215 for determining that the first target SE comprised in the first/third CLF configuration is available.

The ninth determining unit 215 needs to determine that each SE included in the CLF configuration to be used is available, i.e., is activated.

A first configuration unit 216, configured to configure the CLF using the set of contactless protocol parameters if the first CLF configuration is queried.

If the first query unit 214 queries that the target SE uses the ME configuration CLF, the first configuration unit 216 performs CLF configuration on the target SE. After determining that each SE included in the CLF configuration is available, the ME configures the CLF using the parameters of the contactless protocol in the CLF configuration and activates all SEs included in the CLF configuration, or activates the contactless application that requests activation if all SEs included in the CLF configuration are in an activated state.

A fourth querying unit 217, configured to query whether the first contactless application is set with a fast activation flag if the ME queries that the first target SE is in an activated state or that the first target SE is in a deactivated state, and the ME determines that the working mode of the first target SE is an aggregation mode.

A fourth configuration unit 218, configured to, if the first contactless application is provided with the quick activation flag, configure the CLF by using the queried first CLF configuration by the ME.

A third activating unit 219, configured to activate the first SE and/or the first contactless application included in the first CLF configuration.

If the ME inquires that the target SE is in the activated state or the target SE is in the deactivated state, and the ME determines that the working mode of the target SE is the aggregation mode, at this time, the ME inquires whether the non-contact application to be activated is provided with a quick activation flag, that is, for the situation that the target SE is in the activated state, the target SE does not need to be deactivated any more, and for the situation that the working mode of the target SE is the aggregation mode, the target SE can coexist with the SE which is currently in the activated state, and the quick activation of the non-contact application and/or the target SE can be considered. Of course, if the contactless application does not set the fast active flag, the ME performs conventional collision detection and contactless protocol parameter calculation on the target SE.

A second querying unit 220, configured to query whether the CLF configuration mode of the currently activated non-target SE is a CLF configuration for the ME.

And a generating or updating unit 221, configured to generate or update a second CLF configuration according to all contactless protocol parameters used by the current CLF if the result of the query is that the ME configures the CLF, so that the ME can be used when activating the applicable first SE of the second CLF configuration again.

Before deactivating the non-target SE currently in the activated state, if the ME queries that the CLF configuration mode of the non-target SE currently in the activated state is the ME configuration CLF, the ME generates or updates a second CLF configuration according to all non-contact protocol parameters used by the current CLF, namely, if the second CLF configuration does not exist, the ME generates the second CLF configuration according to all non-contact protocol parameters used by the current CLF; and if the second CLF configuration already exists, updating the corresponding configuration parameters in the second CLF configuration according to all the non-contact protocol parameters used by the current CLF. And can thus be used directly when activating the first SE for which this CLF configuration is applicable. The CLF configuration that is saved includes an identification of the currently active SE or SEs, an identification of the currently active contactless application or SEs, a priority of the contactless applications, and a set of contactless protocol parameters used in CLF configuration according to the SEs and contactless applications.

A seventh determining unit 222, configured to determine a CLF configuration manner of the first target SE.

An granting unit 223, configured to grant a CLF configuration authority to the first target SE if the CLF configuration mode of the first target SE is non-ME configuration CLF.

A recording unit 224 for recording an identification of the first target SE.

Since the ME has determined that the operating mode of the target SE is the non-aggregation mode, the CLF configuration of the target SE may be in two ways, i.e., ME configuration CLF or non-ME configuration CLF, which generally means the CLF is configured by the SE. There may be two different processing modes according to the different CLF configuration modes of the target SE.

An eighth determining unit 225, configured to determine to deactivate a non-target SE currently in an activated state when the first target SE is in the activated state.

A second activating unit 226, configured to deactivate the non-target SE currently in an activated state.

A changing unit 227, configured to change an operating mode of the first target SE.

A fourth querying unit 228, configured to query whether the third CLF configuration is saved.

A third configuration unit 229, configured to configure the CLF using a set of contactless protocol parameters in the queried third CLF configuration, if the third CLF configuration is queried.

If the ME queries that the target SE is in the active state, but the ME receives a request to change the operating mode of the target SE (e.g., change from the aggregation mode to the non-aggregation mode), at which point the active SE may be more than the target SE, the ME deactivates the currently active non-target SE.

A sixth determining unit 230, configured to, if the first CLF configuration is not queried, perform collision detection and non-contact protocol parameter calculation according to the first target SE, and determine a set of non-contact protocol parameters applicable to the first target SE;

a second configuration unit 231 for configuring the CLF using the calculated set of contactless protocol parameters.

If the ME does not inquire that the CLF configuration suitable for the target SE is stored, the ME executes conflict detection and non-contact protocol parameter calculation according to the target SE and the application to be activated, wherein the conflict detection means whether the AID of the application on the activated target SE conflicts or whether the AID conflicts with the AID of the currently activated application and whether the protocol parameters conflict or not; the contactless protocol parameter calculation refers to a set of contactless protocol parameters calculated by the ME that are suitable for all SEs and contactless applications that are currently active. And after the ME calculates a group of non-contact protocol parameters, the CLF is configured by adopting the group of non-contact protocol parameters.

According to the terminal provided by the embodiment of the invention, according to the non-target SE and the working mode of the target SE which are currently in the activated state and the CLF configuration mode thereof, when the non-target safety unit which is currently in the activated state is determined to be deactivated and the CLF can be configured by adopting the stored non-contact front-end configuration which is suitable for the target SE, the non-contact front end is configured by adopting a group of non-contact protocol parameters in the non-contact front-end configuration without collision detection and non-contact protocol parameter calculation, so that the configuration efficiency of the non-contact front end can be greatly improved.

Referring to fig. 6, a schematic structural diagram of another terminal according to an embodiment of the present invention is shown, where the terminal 3000 includes a memory 31, a processor 32, a security unit SE33 and a contactless front-end CLF34, and the processor 32 is connected to the memory 31, the security unit SE33 and the contactless front-end CLF34, respectively.

The processor 32 may be a DH or NFCC or even a microprocessor internal to the SE.

Wherein the processor 32 is configured to perform the following steps:

In one embodiment, the processor 32 is configured to perform the step of activating the first target SE when the first target SE is in the deactivated state, and further configured to perform the steps of:

and determining and deactivating the non-target SE currently in the activated state according to the working mode of the non-target SE currently in the activated state and/or the working mode of the first target SE.

In another embodiment, the processor 32 is configured to perform the following steps before the CLF is configured with the set of contactless protocol parameters:

In another embodiment, the processor 32 is configured to execute the step of obtaining the identity of the first target SE and the state thereof, including:

or receiving a request for activating at least one non-contact application, determining the SE where the at least one non-contact application is located as the first target SE, and obtaining the identifier of the first target SE;

In yet another embodiment, the processor 32 is configured to execute the determining to deactivate the currently activated non-target SE according to the operating mode of the currently activated SE and/or the operating mode of the first target SE, and includes:

In yet another embodiment, the processor 32 is further configured to perform the following steps:

if the first CLF configuration is not inquired, determining a group of non-contact protocol parameters suitable for the first target SE according to the first target SE for executing conflict detection and non-contact protocol parameter calculation;

In yet another embodiment, the first or second CLF configuration further includes an identification of the activated first SE, an identification of the activated first contactless application, and a priority of the first contactless application.

determining a CLF configuration mode of the first target SE;

inquiring whether a third CLF configuration is stored;

In another embodiment, after the step of querying whether the first/third CLF configuration is saved and before the step of configuring the CLF by using the set of contactless protocol parameters in the queried first/third CLF configuration, the processor 32 is further configured to perform the following steps:

According to the terminal provided by the embodiment of the invention, according to the non-target SE in the current activation state, the working mode of the target SE and the CLF configuration mode thereof, when the CLF can be configured by adopting the stored non-contact front-end configuration suitable for the target SE, the non-contact front end is configured by adopting a group of non-contact protocol parameters in the non-contact front-end configuration, collision detection and non-contact protocol parameter calculation are not needed, and the configuration efficiency of the non-contact front end can be greatly improved.

It should be noted that, for simplicity of description, the above-mentioned method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the present invention is not limited by the order of acts, as some steps may occur in other orders or concurrently in accordance with the invention. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required by the invention.

In the foregoing embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.

The steps in the method of the embodiment of the invention can be sequentially adjusted, combined and deleted according to actual needs.

The units in the device of the embodiment of the invention can be merged, divided and deleted according to actual needs. Those skilled in the art may combine or combine features of different embodiments and features of different embodiments described in this specification.

From the above description of the embodiments, it is clear to those skilled in the art that the present invention can be implemented by hardware, firmware, or a combination thereof. When implemented in software, the functions described above may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a computer. Taking this as an example but not limiting: the computer-readable medium may include Random Access Memory (RAM), Read-Only Memory (ROM), electrically erasable Programmable Read-Only Memory (EEPROM), Compact Disc Read-on Memory (CD-ROM) or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. Furthermore, the method is simple. Any connection is properly termed a computer-readable medium. For example, if software is transmitted from a website, a server, or other remote source using a coaxial cable, a fiber optic cable, a twisted pair, a Digital Subscriber Line (DSL), or wireless technologies such as infrared, radio, and microwave, the coaxial cable, the fiber optic cable, the twisted pair, the DSL, or the wireless technologies such as infrared, radio, and microwave are included in the fixation of the medium. Disk and disc, as used herein, includes Compact Disc (CD), laser disc, optical disc, Digital Versatile Disc (DVD), floppy Disk and blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

In short, the above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, or improvement 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 for configuring a contactless front-end CLF, the method comprising:

the method comprises the steps that a management entity ME obtains an identification and a state of a first target SE, wherein the state comprises an activation state and a deactivation state;

if the first CLF configuration is inquired, the ME configures the CLF by using the set of non-contact protocol parameters;

wherein, still include:

the ME determines and deactivates the non-target SE in the activated state according to the working mode of the non-target SE in the activated state and/or the working mode of the first target SE;

wherein before the ME configures the CLF using the set of contactless protocol parameters, the method further comprises:

2. The method of claim 1, wherein the ME obtaining the identity and state of the first target SE comprises:

3. The method as claimed in any of claims 1-2, wherein the determining, by the ME, to deactivate the currently active non-target SE according to the operating mode of the currently active non-target SE and/or the operating mode of the first target SE, comprises:

4. A method of configuring a contactless front-end CLF, characterized in that it has all the features of the method of any of claims 1 to 3, and in that it further comprises:

5. A method of configuration of a contactless front-end CLF, characterized in that it has all the features of the method of any of claims 1 to 4, and in that said first or second CLF configuration further comprises an identification of the activated first SE, an identification of the activated first contactless application and a priority of said first contactless application.

6. A method of configuring a contactless frontend CLF, characterized in that it has all the features of the method of any of claims 1 to 5, and in that it further comprises:

the ME determines the CLF configuration mode of the first target SE;

7. A method of configuring a contactless frontend CLF, characterized in that it has all the features of the method of any of claims 1 to 6, and in that it further comprises:

the ME inquires whether a third CLF configuration is saved;

8. A method for configuring a non-contact front-end CLF, wherein the method for configuring a non-contact front-end CLF has all the features of the method of any one of claims 1 to 7, and wherein, after the ME queries whether a first/third CLF configuration is saved and before the ME configures the CLF using a set of non-contact protocol parameters in the queried first/third CLF configuration, the method further comprises:

9. A method of configuring a contactless front-end CLF, characterized in that it has all the features of the method of any of claims 1 to 8, and in that it further comprises:

10. A terminal, the terminal comprising: management entity ME, contactless frontend CLF and first security element SE, characterized in that said ME comprises:

a first activation unit configured to activate the first target SE when the first target SE is in a deactivated state;

a first configuration unit, configured to configure the CLF using the set of contactless protocol parameters if the first CLF configuration is queried;

wherein the ME further comprises:

the first determining unit is used for determining to deactivate the non-target SE currently in the activated state according to the working mode of the non-target SE currently in the activated state and/or the working mode of the first target SE;

the first activation unit is further used for deactivating the non-target SE currently in the activation state;

wherein the ME further comprises:

11. The terminal of claim 10, wherein the first obtaining unit comprises:

12. The terminal according to any of claims 10-11, wherein the first determining unit comprises:

a fifth determining unit, configured to determine to deactivate the currently activated non-target SE if the working mode of the currently activated non-target SE is a non-aggregation mode and/or the working mode of the first target SE is a non-aggregation mode.

13. A terminal, characterized in that it has all the features of a terminal according to any of claims 10 to 12, and in that the ME further comprises:

14. A terminal characterized in that it has all the features of the terminal of any of claims 10 to 13 and in that said first or second CLF configuration further comprises an identification of the activated first SE, an identification of the activated first contactless application and a priority of said first contactless application.

15. A terminal, characterized in that it has all the features of a terminal according to any of claims 10 to 14, and in that the ME further comprises:

a recording unit for recording an identification of the first target SE.

16. A terminal, characterized in that it has all the features of a terminal according to any of claims 10 to 15, and in that the ME further comprises:

a changing unit, configured to change a working mode of the first target SE;

17. A terminal, characterized in that it has all the features of a terminal according to any of claims 10 to 16, and in that the ME further comprises: a ninth determining unit for determining that the first target SE included in the first/third CLF configuration is available.

18. A terminal, characterized in that it has all the features of a terminal according to any of claims 10 to 17, and in that the ME further comprises:

19. A method for configuring a contactless front-end CLF, the method comprising:

wherein, the ME obtaining the identity and the state of the first target SE comprises:

20. A method for configuring a contactless front-end CLF, the method comprising:

the ME determines to deactivate the non-target SE currently in the activated state according to the working mode of the non-target SE currently in the activated state and/or the working mode of the first target SE, and the method comprises the following steps:

21. A method for configuring a contactless front-end CLF, the method comprising:

wherein the content of the first and second substances,

the method further comprises the following steps:

22. A method for configuring a contactless front-end CLF, the method comprising:

wherein the content of the first and second substances,

the first or second CLF configuration further comprises an identification of the activated first SE, an identification of the activated first contactless application and a priority of the first contactless application.

23. A method for configuring a contactless front-end CLF, the method comprising:

wherein the content of the first and second substances,

the method further comprises the following steps:

the ME determines the CLF configuration mode of the first target SE;

24. A method for configuring a contactless front-end CLF, the method comprising:

wherein the content of the first and second substances,

the method further comprises the following steps:

the ME inquires whether a third CLF configuration is saved;

25. A method for configuring a contactless front-end CLF, the method comprising:

wherein the content of the first and second substances,

after the ME queries whether the first/third CLF configuration is saved and before the ME configures the CLF using a set of contactless protocol parameters in the queried first/third CLF configuration, the method further includes:

26. A method for configuring a contactless front-end CLF, the method comprising:

wherein the content of the first and second substances,

the method further comprises the following steps:

27. A terminal, the terminal comprising: management entity ME, contactless frontend CLF and first security element SE, characterized in that said ME comprises:

wherein the content of the first and second substances,

the first acquisition unit includes:

28. A terminal, the terminal comprising: management entity ME, contactless frontend CLF and first security element SE, characterized in that said ME comprises:

wherein the content of the first and second substances,

the first determination unit includes:

29. A terminal, the terminal comprising: management entity ME, contactless frontend CLF and first security element SE, characterized in that said ME comprises:

wherein the content of the first and second substances,

the ME further comprises:

30. A terminal, the terminal comprising: management entity ME, contactless frontend CLF and first security element SE, characterized in that said ME comprises:

wherein the content of the first and second substances,

31. A terminal, the terminal comprising: management entity ME, contactless frontend CLF and first security element SE, characterized in that said ME comprises:

wherein the content of the first and second substances,

the ME further comprises:

a recording unit for recording an identification of the first target SE.

32. A terminal, the terminal comprising: management entity ME, contactless frontend CLF and first security element SE, characterized in that said ME comprises:

wherein the content of the first and second substances,

the ME further comprises:

a changing unit, configured to change a working mode of the first target SE;

33. A terminal, the terminal comprising: management entity ME, contactless frontend CLF and first security element SE, characterized in that said ME comprises:

wherein the content of the first and second substances,

the ME further comprises: a ninth determining unit for determining that the first target SE included in the first/third CLF configuration is available.

34. A terminal, the terminal comprising: management entity ME, contactless frontend CLF and first security element SE, characterized in that said ME comprises:

the ME further comprises:

35. A terminal, the terminal comprising: memory, processor, contactless front-end CLF and at least one security element SE, characterized in that the processor is configured to perform the method of any of claims 1 to 9 or 19 to 26.

36. A computer-readable storage medium, characterized in that it stores a computer program which, when executed by associated hardware, performs the method of any one of claims 1 to 9 or 19 to 26.