WO2016168989A1

WO2016168989A1 - Contactless front-end configuration method and terminal

Info

Publication number: WO2016168989A1
Application number: PCT/CN2015/077113
Authority: WO
Inventors: 李国庆; 梅敬青; 赵晓娜
Original assignee: 华为技术有限公司
Priority date: 2015-04-21
Filing date: 2015-04-21
Publication date: 2016-10-27
Also published as: CN106462845A; CN106462845B

Abstract

A contactless front-end (CLF) configuration method and terminal. When a managing entity (ME) determines that one or more target secure elements (SE) on a terminal are in a deactivated state, the ME queries a stored CLF configuration applicable to the one or more target SEs, and configures the CLF by utilizing a set of contactless protocol parameters in the found CLF configuration without performing conflict detection and contactless protocol parameter calculation, thus greatly improving efficiency of CLF configuration.

Description

Non-contact front end configuration method and terminal

Technical field

The present invention relates to the field of mobile payment technologies, and in particular, to a method and a terminal for configuring a contactless front end.

Background technique

In recent years, mobile payment based on Near Field Communication (NFC) technology has become popular, and NFC-enabled mobile payment terminals use NFC interfaces and card readers (for example, non-contact POS machines deployed in shopping malls). ) The communication completes the payment transaction. The mobile payment terminal generally includes a security unit (English: Secure Element, SE for short), a non-contact front end (English: Contactless Front-End, CLF for short), an NFC antenna, and the like, and a non-contact application installed in the SE (for example, Software such as payment applications such as virtual bank cards and control interfaces installed in the terminal operating system. With the development of the mobile payment industry, terminals supporting multiple SEs have emerged in the market, and management of multiple SEs and multiple applications in each SE is more complicated than a single SE scenario. In order to manage the payment behavior in such a multi-SE scenario, the terminal can integrate a management entity (English: Managing Entity, ME for short) for serving multiple SEs and multiple applications. As shown in Figure 1, the ME interface and function diagram, the ME has a graphical user interface (English: Graphical User Interface, GUI for short) interface and SE interface, which can receive and process the control commands sent by the user through the GUI, and can receive from The SE message analyzes and processes these messages to configure the CLF so that multiple SEs and multiple payment applications can simultaneously serve users.

CLF supports contactless communication technologies such as Type A (ISO/IEC 14443A), Type B (ISO/IEC 14443B), and Type F (ISO/IEC 18092). These technologies have different physical layers and link layers, but they are capable of Provide the underlying link for contactless applications. The SE is a non-contact application installation entity that can install contactless applications based on the above three protocols, which have different parameters for the underlying communication protocol. Therefore, when the user activates a contactless application or activates an SE, according to the currently activated SE and the contactless application activated on each SE, it is necessary to perform collision detection by the ME or SE, and the ME compares the target application to be activated. The parameter requirements are in conflict with the parameter requirements of the activated application (already configured to the CLF). If there is a conflict, the conflict needs to be resolved. After the solution, the CLF is configured with the newly calculated parameters.

According to the prior art, conflict detection and contactless protocols are required when activating a contactless application or SE Parameter calculation. When N applications are activated, the SE needs to perform N collision detection. According to the conflict detection result, the CLF may need to be reconfigured, and the efficiency is low.

Summary of the invention

The embodiment of the invention provides a method and a terminal for configuring a non-contact front end to improve the configuration efficiency of the non-contact front end.

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

The management entity ME obtains an identifier and a state of the first target security unit SE, the state including an activated state and a deactivated state;

When the first target SE is in a deactivated state, the first target SE is activated;

Whether the ME query saves a first CLF configuration, where the first CLF configuration includes a set of contactless protocol parameters applicable to the first target SE;

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

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

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 by using the set of non-contact protocol parameters, the method further includes :

The ME queries whether the CLF configuration mode of the non-target SE that is currently in an active state is an ME configuration CLF;

If the result of the query is that the ME configures the CLF, the ME generates or updates the second CLF configuration according to all contactless protocol parameters applicable to the CLF of the non-target SE that is currently in the active state.

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 ME obtains the identifier of the first target SE and Status, including:

The ME receives a request to activate a first SE, the request including a target of the first target SE knowledge,

Or the ME receives a request to activate at least one contactless application, and the ME determines that the SE where the at least one contactless application is located is the first target SE and obtains an identifier of the first target SE;

The ME queries the status of the first target SE according to the identifier of the first target SE.

In conjunction with the first aspect or the first possible implementation of the first aspect or the second possible implementation of the first aspect or the third possible implementation of the first aspect, in a fourth possible implementation And determining, by the ME according to the working mode of the SE that is currently in an active state and/or the working mode of the first target SE, to deactivate the non-target SE that is currently in an active state, including:

Determining, by the ME, an operating mode of the non-target SE that is currently in an active state;

Determining, by the ME, an operating mode of the first target SE according to a service policy and/or an attribute of the first target SE;

If the ME determines that the working mode of the non-target SE that is currently in an active state is a non-aggregated mode and/or the working mode of the first target SE is a non-aggregated mode, the ME determines to deactivate the current A non-target SE that is active.

Combining the first aspect or the first possible implementation of the first aspect or the second possible implementation of the first aspect or the third possible implementation of the first aspect or the fourth possible implementation of the first aspect In a fifth possible implementation manner, the method further includes:

If the first CLF configuration is not queried, the ME performs a collision detection and a contactless protocol parameter calculation according to the first target SE, and determines a set of contactless protocol parameters applicable to the first target SE;

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

Combining the first aspect or the first possible implementation of the first aspect or the second possible implementation of the first aspect or the third possible implementation of the first aspect or the fourth possible implementation of the first aspect The implementation manner or the fifth possible implementation manner of the first aspect, in the sixth possible implementation manner, the first or second CLF configuration further includes an identifier of the activated first SE, and the activated first non-contact The identity of the application and the priority of the first contactless application.

Combining the first aspect or the first possible implementation of the first aspect or the second possible implementation of the first aspect or the third possible implementation of the first aspect or the fourth possible implementation of the first aspect The implementation may be the fifth possible implementation of the first aspect or the sixth possible implementation of the first aspect. In a seventh possible implementation, the method further includes:

Determining, by the ME, a CLF configuration manner of the first target SE;

If the CLF configuration mode of the first target SE is a 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.

Combining the first aspect or the first possible implementation of the first aspect or the second possible implementation of the first aspect or the third possible implementation of the first aspect or the fourth possible implementation of the first aspect The implementation of the fifth possible implementation of the first aspect or the sixth possible implementation of the first aspect or the seventh possible implementation of the first aspect, in an eighth possible implementation manner, The method also includes:

When the first target SE is in an active state, the ME determines and deactivates a non-target SE that is currently in an active state, and changes an operating mode of the first target SE;

Whether the ME query saves a third CLF configuration;

If the third CLF configuration is queried, the ME configures the CLF using a set of contactless protocol parameters in the queried third CLF configuration.

Combining the first aspect or the first possible implementation of the first aspect or the second possible implementation of the first aspect or the third possible implementation of the first aspect or the fourth possible implementation of the first aspect Implementation or a fifth possible implementation of the first aspect or a sixth possible implementation of the first aspect or a seventh possible implementation of the first aspect or an eighth possible implementation of the first aspect In a ninth possible implementation manner, after the ME query saves the first/third CLF configuration, and the ME uses a set of non-contact in the first/third CLF configuration that is queried Before configuring the CLF, the protocol parameters include:

It is determined that the first target SE included in the first/third CLF configuration is available.

Combining the first aspect or the first possible implementation of the first aspect or the second possible implementation of the first aspect or the third possible implementation of the first aspect or the fourth possible implementation of the first aspect Implementation or a fifth possible implementation of the first aspect or a sixth possible implementation of the first aspect or a seventh possible implementation of the first aspect or an eighth possible implementation of the first aspect Or the ninth possible implementation manner of the first aspect, in the tenth possible implementation manner, the method further includes:

If the ME queries that the first target SE is in an active 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 Querying whether the first contactless application is provided with a quick activation flag;

If the first contactless application is provided with the quick activation flag, the ME configures the CLF using the first CLF configuration that is queried, and activates the first SE and/or included in the first CLF configuration. The first non-contact application.

The second aspect provides a terminal, where the terminal includes: a management entity ME, a contactless front end CLF, and a first security unit SE, where the ME includes:

a first acquiring unit, configured to obtain an identifier and a state of the first target security unit SE, where the state includes an activated state and a deactivated state;

a first activation unit, configured to activate the first target SE;

a first query unit, 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;

And a first configuration unit, configured to configure the CLF by using the set of non-contact protocol parameters if the first CLF configuration is queried.

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

a first determining unit, configured to: when the first target SE is in a deactivated state, according to an operating mode of the non-target SE currently in an activated state and/or an operating mode of the first target SE;

The first activation unit is further configured to deactivate the non-target SE that is currently in an active 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:

a second query unit, configured to query whether the CLF configuration mode of the non-target SE that is currently in an active state is an ME configuration CLF;

Generating or updating a unit for generating or updating a second CLF configuration according to all contactless protocol parameters applicable to the CLF of the non-target SE currently in an active state if the result of the query is a CLF configured by the ME.

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

a receiving unit, configured to receive a request to activate the first SE, where the request includes an identifier 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 that the SE where the at least one non-contact application is located is the first Target SE;

a second acquiring unit, configured to obtain an identifier of the first target SE;

The third query unit is configured to query the status of the first target SE according to the identifier of the first target SE.

With reference to the second aspect or the first possible implementation of the second aspect or the second possible implementation of the second aspect or the third possible implementation 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 non-target SE that is currently in an active state;

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

a fifth determining unit, configured to determine to deactivate the current if the working mode of the non-target SE that is currently in an active state is determined to be a non-aggregating mode and/or the working mode of the first target SE is a non-aggregating mode A non-target SE that is active.

Combining the second aspect or the first possible implementation of the second aspect or the second possible implementation of the second aspect or the third possible implementation of the second aspect or the fourth possible implementation of the second aspect In an implementation manner, in a fifth possible implementation manner, the ME further includes:

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

And a second configuration unit, configured to configure the CLF using the calculated set of non-contact protocol parameters.

Combining the second aspect or the first possible implementation of the second aspect or the second possible implementation of the second aspect or the third possible implementation of the second aspect or the fourth possible implementation of the second aspect The implementation manner or the fifth possible implementation manner of the second aspect, in the sixth possible implementation manner, the first or second CLF configuration further includes an identifier of the activated first SE, and the activated first non-contact The identity of the application and the priority of the first contactless application.

Combining the second aspect or the first possible implementation of the second aspect or the second possible implementation of the second aspect or the third possible implementation of the second aspect or the fourth possible implementation of the second aspect 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;

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

a recording unit, configured to record an identifier of the first target SE.

Combining the second aspect or the first possible implementation of the second aspect or the second possible implementation of the second aspect or the third possible implementation of the second aspect or the fourth possible implementation of the second aspect The implementation of the fifth possible implementation of the second aspect or the sixth possible implementation of the second aspect or the seventh possible implementation of the second aspect, in an eighth possible implementation manner, The ME also includes:

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

a second activation unit, configured to deactivate a non-target SE that is currently in an active state;

a change unit, configured to change an operation mode of the first target SE;

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

And a third configuration unit, configured to configure the CLF by using a set of non-contact protocol parameters in the queried third CLF configuration, if the third CLF configuration is queried.

Combining the second aspect or the first possible implementation of the second aspect or the second possible implementation of the second aspect or the third possible implementation of the second aspect or the fourth possible implementation of the second aspect Implementation or a fifth possible implementation of the second aspect or a sixth possible implementation of the second aspect or a seventh possible implementation of the second aspect or an eighth possible implementation of the second aspect In a ninth possible implementation manner, the ME further includes:

And a ninth determining unit, configured to determine that the first target SE included in the first/third CLF configuration is available.

Combining the second aspect or the first possible implementation of the second aspect or the second possible implementation of the second aspect or the third possible implementation of the second aspect or the fourth possible implementation of the second aspect Implementation or a fifth possible implementation of the second aspect or a sixth possible implementation of the second aspect or a seventh possible implementation of the second aspect or an eighth possible implementation of the second aspect Or the ninth possible implementation manner of the second aspect, in the tenth possible implementation manner, the ME further includes:

a fourth query unit, configured to: if it is found 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 Aggregating mode, querying whether the first contactless application is provided with a quick activation flag;

a fourth configuration unit, configured to configure the CLF by using the first CLF configuration that is queried if the first non-contact application is configured with the quick activation flag;

And a third activation unit, configured to activate the first SE and/or the first contactless application included in the first CLF configuration.

A third aspect provides a terminal, where the terminal includes: a memory, a processor, a contactless front end CLF, and at least one security unit SE, where the processor is configured to perform the following steps:

Obtaining an identifier and a state of the first target security unit SE, the state including an activated state and a deactivated state;

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

If the first CLF configuration is queried, the CLF is configured using the set of contactless protocol parameters.

In a first possible implementation, the processor is configured to perform the step of activating the first target SE when the first target SE is in a deactivated state, and is further configured to perform the following steps: Determining and deactivating the currently active non-target SE by the operating mode of the SE currently active and/or the operating 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 perform the configuring the CLF by using the set of contactless protocol parameters, Also used to perform the following steps:

Query whether the CLF configuration mode of the non-target SE that is currently active is a processor configuration CLF;

If the result of the query is a processor configuration CLF, the second CLF configuration is generated or updated according to all contactless protocol parameters applicable to the CLF of the non-target SE that is currently active, so that the processor activates the second CLF configuration again. Used when the first SE is applied.

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 perform the obtaining the first The steps of the identity of the target SE and its status, including:

Receiving a request to activate a first SE, the request including an identifier of the first target SE,

Or receiving a request to activate the at least one contactless application, determining that the SE where the at least one contactless application is located is the first target SE and obtaining the identifier of the first target SE;

And querying, according to the identifier of the first target SE, a status 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 And the step of determining, by the processor, the deactivating the non-target SE that is currently in an active state according to the working mode of the SE that is currently in an active state and/or the working mode of the first target SE, including:

Determining an operating mode of the non-target SE that is currently in an active state;

Determining an operation mode of the first target SE according to a service policy and/or an attribute of the first target SE;

Determining to deactivate the currently active non-target SE if it is determined that the working mode of the non-target SE currently in an active state is a non-aggregated mode and/or the working mode of the first target SE is a non-aggregating mode .

Combining the third aspect or the first possible implementation of the third aspect or the second possible implementation of the third aspect or the third possible implementation of the third aspect or the fourth possible implementation of the third aspect In a fifth possible implementation manner, the processor is further configured to perform the following steps:

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

The CLF is configured using a calculated set of contactless protocol parameters.

Combining the third aspect or the first possible implementation of the third aspect or the second possible implementation of the third aspect or the third possible implementation of the third aspect or the fourth possible implementation of the third aspect The implementation manner 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, and the activated first non-contact The identity of the application and the priority of the first contactless application.

Combining the third aspect or the first possible implementation of the third aspect or the second possible implementation of the third aspect or the third possible implementation of the third aspect or the fourth possible implementation of the third aspect The implementation of the fifth possible implementation of the third aspect or the sixth possible implementation of the third aspect. In a seventh possible implementation, the processor is further configured to perform the following steps:

Determining a CLF configuration manner of the first target SE;

If the CLF configuration mode of the first target SE is a non-processor configuration CLF, the CLF configuration authority is granted to the first target SE and the identifier of the first target SE is recorded.

Combining the third aspect or the first possible implementation of the third aspect or the second possible implementation of the third aspect or the third possible implementation of the third aspect or the fourth possible implementation of the third aspect 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 the eighth possible implementation manner, The processor is also used to perform the following steps:

Determining and deactivating a non-target SE that is currently in an active state when the first target SE is in an active state, and changing an operating mode of the first target SE;

Whether the query saves the third CLF configuration;

If the third CLF configuration is queried, the CLF is configured using a set of contactless protocol parameters in the queried third CLF configuration.

Combining the third aspect or the first possible implementation of the third aspect or the second possible implementation of the third aspect or the third possible implementation of the third aspect or the fourth possible implementation of the third aspect Implementation or a fifth possible implementation of the third aspect or a sixth possible implementation of the third aspect or a seventh possible implementation of the third aspect or an eighth possible implementation of the third aspect In a ninth possible implementation manner, after the step of the processor for performing whether the query saves the first/third CLF configuration, and the processor is configured to perform the using the query Before the step of configuring the CLF in a set of non-contact protocol parameters in the first/third CLF configuration, the following steps are also performed:

Combining the third aspect or the first possible implementation of the third aspect or the second possible implementation of the third aspect or the third possible implementation of the third aspect or the fourth possible implementation of the third aspect Implementation or a fifth possible implementation of the third aspect or a sixth possible implementation of the third aspect or a seventh possible implementation of the third aspect or an eighth possible implementation of the third aspect Or the ninth possible implementation manner of the third aspect, in the tenth possible implementation manner, the processor is further configured to perform the following steps:

Querying the first non-query if the first target SE is in an activated state, or the first target SE is in a deactivated state, and it is determined that the working mode of the first target SE is an aggregation mode Whether the contact application is provided with a quick activation flag;

If the first contactless application is provided with the quick activation flag, using the queried

The first CLF configuration configures the CLF and activates the first SE and/or the first contactless application included in the first CLF configuration.

It can be seen that, according to an embodiment of the present invention, a method and a terminal for configuring a contactless front end, when the management entity determines that one or more target security units on the terminal are in a deactivated state, the management entity may query and save the applicable one for the one. Or the non-contact front-end configuration of the plurality of target security units, and configuring the non-contact front-end using a set of non-contact protocol parameters in the contactless front-end configuration, without conflict detection and non-contact protocol parameter calculation, greatly improving The efficiency of the configuration of the contactless 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 to be used in the embodiments will be briefly described below. Obviously, the drawings in the following description are only some of the present invention. For the embodiments, those skilled in the art can obtain other drawings according to the drawings without any creative work.

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

2 is a schematic flowchart of a method for configuring a contactless front end according to an embodiment of the present invention;

FIG. 3 is a schematic flowchart diagram of another method for configuring a contactless front end according to an embodiment of the present disclosure;

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

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

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

detailed description

The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, but not all embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

The terminal in the embodiment of the present invention refers to a terminal having an NFC payment function, such as an NFC mobile phone, an NFC tablet, an NFC watch, or the like. The terminal can be connected to one or more SEs, and one SE can be installed. One or more contactless applications, the ME manages the SE and applications on the terminal. SE refers to a tamper-proof operating environment, usually a secure microcontroller chip. The chip can safely store and run applications, save application-related keys, certificates and other data without being tampered with and illegally accessed, and the chip can also save confidential data access rules. SE is a concept in the specification developed by the Global Platform International Standards Organization (GP). In the GP related specifications, SE is related to CEE (Card Emulation Environment) and can refer to each other; SE can also communicate with the near field communication execution environment ( English: NFC Execution Environment, referred to as: NFCEE), HCI host and other concepts refer to each other. NFCEE is a term used in the NCI specification developed by the NFC Forum; the HCI host refers to the universal integrated circuit card in the HCI specification developed by the European Telecommunication Standards Institute (ETSI). English: Universal Integrated Circuit Card (UICC), Embedded Secure Element (English: Embedded Secure Element (eSE), Secure Digital Memory Card (English: Secure Digital Memory Card): Host . CLF refers to a physical module in the terminal, which is used for analog signal processing and transmission protocol processing of near field communication. Through this module, the card reader can exchange data with the SE on the terminal. The CLF is a concept in the relevant specifications developed by ETSI, which is equivalent to the NFC Controller (NFC Controller) in the specifications developed by the NFC Forum. Contactless Application (English: Contactless Application, CL App for short) generally refers to an application installed in the SE and can be exchanged with a card reader using the contactless interface provided by CLF, for example, a universal integrated circuit card installed in a mobile phone. :Universal Integrated Circuit Card, referred to as: UICC) The bus card application and electronic cash card application in SE are non-contact applications. Contactless applications are concepts defined in the specifications developed by the GP and are also referred to as NFC services in the relevant specifications developed by the NFC Forum.

The ME of the embodiment of the present invention has two working modes: an Aggregated mode and a Non-Aggregated mode:

The ME aggregation mode is a working mode when the ME manages multiple SEs. In this mode, users can select multiple applications installed on multiple SEs to activate and use these services at the same time. Users cannot perceive these services from Multiple SEs. In other words, multiple SEs can be activated simultaneously in this mode, and applications on different SEs can be activated simultaneously. In this mode, the ME needs to configure the CLF based on all activated contactless applications.

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

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

The aggregation mode and the non-aggregation mode are for both ME and SE. The SE can be divided according to whether the interface with the ME is supported. If the SE supports the interface with the ME, the SE can work in both the aggregated and non-aggregated modes, and the SE can send a request to the ME through the interface with the ME, and the work is required to be specific. In the mode, the SE that does not support the ME interface cannot use the conflict detection function of the ME. It can only work in the non-aggregation mode and configure the CLF by itself. The working mode of the active SE is consistent with the working mode of the ME.

The management entity ME in the present invention is an entity for multiple SEs and contactless application management on the same terminal. Specifically, the ME can be run on the terminal controller DH (Device Host), and the DH is responsible for the entire Management of equipment, including management of NFC controllers, such as initialization, configuration or power management. In the smartphone, the main controller DH can correspond to the CPU of the mobile phone; DH is a term used in the NCI specification developed by the NFC Forum, and can correspond to the HCI developed by the European Telecommunication Standards Institute (ETSI). The terminal host in the specification (Terminal Host); in addition, the management entity (ME, Managing Entity) in the specification developed by the Global Platform International Standards Organization (GP) can also be called DH if it is implemented on the Terminal Host. Management Host (MH, Managing Host)

The ME can also operate on the Near Field Communication Controller NFCC (NFC Controller), which is the entity responsible for data transmission of the NFC chip, and is usually used directly to refer to the NFC chip. The NFCC is a term used in the NCI specification developed by the NFC Forum to correspond to the Contactless Front-end (CLF, Contactless Front-end) in the HCI specification developed by the European Telecommunication Standards Institute (ETSI). At this time, the host controller of the HCI is implemented on the NFCC.

The ME may even run in the Secure Element SE (Secure Element).

When the ME determines that one or more target security units on the terminal are in a deactivated state, if it is determined that the non-target security unit currently in the active state needs to be deactivated, the management entity may query for protection. A non-contact front-end configuration applicable to the one or more target security units, configured by using a set of non-contact protocol parameters in the contactless front-end configuration, without conflict detection and contactless protocol parameters The calculation greatly improves the configuration efficiency of the non-contact front end.

The configuration method of the non-contact front end provided by the embodiment of the present invention is described in detail below with reference to FIG. 2 to FIG. 3:

FIG. 2 is a schematic flowchart of a method for configuring a contactless front end according to an embodiment of the present invention. The method includes the following steps:

Step S101, the management entity ME obtains the identifier and status of the first target security unit SE, and the status includes an activated state and a deactivated state.

The ME obtains the identifier of the first target SE, and the ME may receive the request for activating one or more SEs from the GUI interface, and the SE corresponding to the SE identifier included in the request is the target SE to be activated, that is, the target SE; After receiving the request for activating the one or more contactless applications, the ME obtains the identifier of the SE where the one or more contactless applications are located, and the SE corresponding to the SE identifier is the target SE; the ME can use the target SE The identity of the query is queried to the status of the target SE.

Step S102: When the first target SE is in a deactivated state, the first target SE is activated.

Before the first target SE is activated, there may be no non-target SE in the active state on the terminal, or a non-target SE in the active state. At this time, the non-target SE needs to be deactivated before the first target SE is activated. The specific scenario of deactivating a non-target SE that is currently active is as follows:

In the scenario of the embodiment, the ME needs to determine to deactivate the currently active SE according to the working mode of the SE currently in the active state or the working mode of the target SE, and activate the target SE. In one scenario, the SE in the active state is in the non-aggregation mode, and the CLF configuration mode is the ME configuration CLF or the non-ME configuration CLF, and the target SE is required to work in the aggregation mode, and the CLF configuration mode is the ME configuration CLF. In the non-aggregated mode, only one SE can be activated, and the target SE is in a deactivated state. Obviously, the currently active SE is not the same SE as the target SE. While the currently active SE works in the non-aggregation mode, there is only one SE that is currently active, and therefore, the SE that is currently active needs to be deactivated. Another scenario is that the target SE is required to work in the non-aggregation mode regardless of the working mode and the CLF configuration mode of the currently active SE, and the CLF configuration mode is configured for the ME by the CLF, because the target SE works in the non-aggregated mode and It is deactivated and does not allow other SEs to be activated at the same time as this target SE, so it is necessary to deactivate the SE that is currently active.

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

Since the currently active SEs are all deactivated, it is not possible to determine that the non-contact protocol parameters currently configured to the CLF are applicable to the new activated target SE. Therefore, the CLF needs to be reconfigured according to the new activated target SE.

In this embodiment, the terminal pre-stores the configuration of the CLF in a specific scenario, and the CLF configurations may be saved as a CLF profile, where the CLF configuration includes one or more SE identifiers activated in a specific scenario, and one or more activated ones. The identity of the contactless applications and the priority of these contactless applications, as well as a set of contactless protocol parameters used in CLF configuration based on these SE and contactless applications.

In this embodiment, when the target SE is configured for CLF, it is queried whether the CLF configuration including the target SE identifier is saved. If the ME receives the request to activate the contactless application, the ME queries the CLF configuration to query whether the target SE identifier and the identifier of the contactless application to be activated are included in the CLF configuration. Since the saved CLF configuration including the target SE identifier may be more than one, when selecting the saved CLF configuration, the CLF configuration is required to include the target SE identifier, and the SE identifiers other than the target SE identifier are included as little as possible.

Step S104: If the first CLF configuration is queried, the ME configures the CLF by using the set of non-contact protocol parameters.

If the saved CLF configuration is queried, the ME configures the CLF using the set of non-contact protocol parameters in the saved CLF configuration, and does not need to perform conflict detection and non-contact protocol parameter calculation, and directly configures to the CLF, which greatly improves the non-contact front end. Configuration efficiency.

According to a method for configuring a contactless front end according to an embodiment of the present invention, when the management entity determines that one or more target security units on the terminal are in a deactivated state, the management entity may query the saved ones for the one or more targets. The non-contact front-end configuration of the security unit configures the non-contact front end by using a set of non-contact protocol parameters in the contactless front-end configuration, without conflict detection and non-contact protocol parameter calculation, which greatly improves the non-contact front end. Configuration efficiency.

FIG. 3 is a schematic flowchart of another method for configuring a non-contact front end according to an embodiment of the present invention. The method includes the following steps:

Step S201, the ME receives a request to activate at least one contactless application, and the ME determines at least one The SE where the contactless application is located is the first target SE and obtains the identifier of the first target SE.

This embodiment is described by taking an activation non-contact application as an example. The contactless application has a unique application identifier (English: Application Identifier, AID for short). The ME receives an activation request of the contactless application through the GUI interface, and the request carries the AID. The contactless application to be activated here may be one or more.

The ME queries the target SE where the contactless application AID is located, and the plurality of contactless applications may be located on one target SE or on multiple target SEs.

Step S202: The ME queries whether the first target SE is in an active state according to the identifier of the first target SE. If not, the process goes to step S203; if yes, the process goes to step S212 or S215.

The ME queries the activation state of the target SE, and performs different processing according to the activation state of the target SE.

In step S203, the ME determines whether the working mode of the first target SE is the non-aggregation mode. If yes, the process goes to step S204; otherwise, the process goes to step S212.

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

The ME may determine the working mode of the target SE according to the service policy and/or the attributes of the target SE:

Service strategies can include:

a) Ensure that as many services as possible provided by the same service provider are available at the same time. In this case, the ME works in a non-aggregated mode corresponding to activating a single SE, which can reduce the impact of other SEs on the target SE;

b) Ensure that the services provided by multiple service operators are available at the same time. In this case, corresponding to the aggregation mode, services on multiple SEs have opportunities to be used, and at this time, it is possible to ensure the interests of multiple service operators;

The 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 the non-aggregation mode, and the CLF can be configured by the ME;

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

For example, scenario A: The target SE only supports the non-aggregation mode, and the working mode of the SE or the ME can be determined according to the attribute. It should be noted that the working mode of the SE in the activated state is consistent with the working mode of the ME; scenario B: The service policy is that the most required SEs work at the same time. If the SE supports aggregation or non-aggregation, the ME determines that the ME and the SE should work in the aggregation mode. Scenario C: The service policy requires that an application on one SE be used as much as possible. The SE supports aggregation and non-aggregation. Polymerization, then ME and SE should work in non-polymerization Combined mode.

Different processing is performed depending on whether the working mode of the target SE is an aggregation mode or a non-aggregation mode.

Step S204: If the ME determines that the working mode of the non-target SE that is currently in the active 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 that is currently in the active state.

The ME can query the working mode of the SE that is currently active. This step is the same as step S102 of the foregoing embodiment, and details are not described herein again.

Step S205: If the ME queries the CLF configuration mode of the non-target SE that is currently in the active state to configure the CLF for the ME, the ME generates or updates the second according to all non-contact protocol parameters applicable to the CLF of the non-target SE that is currently in the active state. CLF configuration.

Before deactivating a non-target SE that is currently active, if the ME queries that the CLF configuration mode of the non-target SE that is currently active is the ME configuration CLF, the ME is used according to the CLF applicable to the non-target SE that is currently active. All of the contactless protocol parameters generate or update the second CLF configuration, ie, if the second CLF configuration does not exist, generate a second CLF configuration according to all contactless protocol parameters applicable to the CLF of the non-target SE that is currently active. If the second CLF configuration already exists, the corresponding configuration parameters in the second CLF configuration are updated according to all contactless protocol parameters applicable to the CLF of the non-target SE that is currently active. This can be used directly when activating the first SE to which this CLF configuration applies. The saved CLF configuration includes an identifier of one or more SEs currently activated, one or more contactless application identifiers currently activated, priorities of these contactless applications, and usage of CLF configurations according to these SEs and contactless applications. A set of contactless protocol parameters.

In step S206, the ME queries whether the first target SE uses the ME to configure the CLF, and if yes, proceeds to step S207; otherwise, proceeds to step S211.

Since the ME has determined that the working mode of the target SE is the non-aggregation mode in the step S204, the CEF configuration mode of the target SE may be two, that is, the ME configuration CLF or the non-ME configuration CLF, and the non-ME configuration CLF generally refers to the configuration by the SE. CLF. There are two different ways of processing depending on the configuration of the target SE's CLF.

In step S207, the ME queries whether the first CLF configuration is saved. If yes, the process goes to step S208; otherwise, the process goes to step S213.

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

The ME may query that there are multiple CLF configurations that contain the target SE identifier. When the ME selects the saved CLF configuration, the ME includes the least SE identifiers other than the target SE identifier. Then, the ME needs to determine that each SE included in the CLF configuration to be used is available, and can be activated.

In step S209, the ME configures the CLF using a set of non-contact protocol parameters.

If the ME queries the target SE to configure the CLF using the ME, 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, and details are not described herein again.

Step S210, the ME activates the first SE and the first contactless application included in the first CLF configuration.

After the ME determines that each SE included in the CLF configuration is available, configure the CLF by using the non-contact protocol parameters in the CLF configuration, and activate all SEs included in the CLF configuration, or if all SEs included in the CLF configuration are activated, Then activate the contactless application that requested activation.

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 queries the target SE to use the non-ME configuration CLF, that is, the SE configures the CLF, the ME grants the CLF configuration authority to the target SE, performs the CLF configuration by the SE itself, and records the identity of the target SE.

In step S212, the ME queries whether the first contactless application is provided with a quick activation flag, and if yes, proceeds to step S213; otherwise, proceeds to step S210.

If the ME finds that the target SE is in the active 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, the ME queries whether the contactless application to be activated is set to be activated quickly. Marking, that is, for the scenario in which the target SE is in an active state, there is no need to deactivate the target SE. For the scenario in which the working mode of the target SE is the aggregation mode, the target SE can coexist with the SE currently in the active state, then the non-contact can be considered. The application and/or target SE performs a quick activation. Of course, if the non-contact application does not set the quick activation flag, then go to step S213, and the ME performs regular collision detection and non-contact protocol parameter calculation on the target SE.

When a certain condition is met, the non-contact application is quickly activated, and the CLF configuration is configured by using the saved CLF configuration, which can further improve the CLF configuration efficiency.

Step S213, the ME performs conflict 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 non-contact protocol parameters.

If the ME does not query to save the CLF configuration applicable to the target SE in step S207, the ME performs collision detection and contactless protocol parameter calculation according to the target SE and the application to be activated, and the conflict detection refers to activating the AID of the application on the target SE. Whether it conflicts or conflicts with the AID of the currently activated application, and whether the protocol parameters conflict; the contactless protocol parameter calculation refers to a set of contactless protocol parameters calculated by the ME for all SEs and contactless applications currently activated. . After the ME calculates a set of non-contact protocol parameters, the CLF is configured using the set of non-contact protocol parameters. In step S215, the ME determines and deactivates the non-target SE that is currently in the active state, and changes the working mode of the first target SE.

If the ME queries the target SE to be in an active state in step S202, but the ME receives a request to change the working mode of the target SE (for example, the aggregation mode is changed to the non-aggregation mode), at this time, the SE in the active state may be more than the target. SE, then the ME deactivates the non-target SE that is currently active.

Step S216: If the ME queries to save the third CLF configuration, the ME configures the CLF by using a set of non-contact protocol parameters in the queried third CLF configuration. The third CLF configuration is a CLF configuration suitable for the target SE.

After the ME deactivates the non-target SE that is currently active, only the target SE in the active state remains, and the ME query saves the CLF configuration including the target SE, and uses a set of non-contact protocol parameter configurations in the queried CLF configuration. CLF, you can quickly configure the CLF.

In addition to the above scenario, if the working mode of the currently active SE is the aggregation mode, the CLF configuration mode is the ME configuration CLF, and the target SE working mode is the non-aggregation mode, the CLF configuration mode is the non-ME configuration CLF, or, the current The active mode of the SE is in the non-aggregation mode. The CLF configuration mode is that the ME is configured with the CLF, and the target SE is in the non-aggregation mode. The CLF configuration mode is the non-ME configuration CLF, or the saved CLF configuration. To configure the CLF.

According to an embodiment of the present invention, a method for configuring a contactless front end, according to an active mode of a non-target SE and a target SE currently in an active state, and a CLF configuration manner thereof, when it is determined that the non-target security currently in an active state needs to be deactivated When the unit is configured, and the CLF can be configured by using the saved non-contact front-end configuration applicable to the target SE, the non-contact front end is configured by a set of non-contact protocol parameters in the non-contact front-end configuration, and no conflict detection and contactless protocol is required. Parameter calculation can greatly improve the configuration efficiency of the non-contact front end.

The terminal for implementing the configuration method of the non-contact front end provided by the embodiment of the present invention is described in detail below with reference to FIG. 4-6.

FIG. 4 is a schematic structural diagram of a terminal according to an embodiment of the present invention. The terminal 1000 includes a management entity ME11, a security unit SE12 and a non-contact front end CLF13 respectively connected to the ME11, and the SE12 is connected to the CLF13. Among them, the ME11 includes:

The first obtaining unit 111 is configured to obtain an identifier and a state of the first target security unit SE, where the state includes an activated state and a deactivated state.

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

The first activation unit 112 is configured to activate the first target SE.

Before the first activation unit 112 activates the first target SE, the non-target SE in the active state may not be present on the terminal, or may have the non-target SE in the active state. At this time, before the activation of the first target SE, it is necessary to deactivate the non-target SE. Target SE. The specific scenario of deactivating a non-target SE that is currently active is as follows:

In the scenario of the embodiment, it is required to deactivate the currently active SE according to the working mode of the SE currently in the active state or the working mode of the target SE, and activate the target SE. In one scenario, the SE in the active state is in the non-aggregation mode, and the CLF configuration mode is the ME configuration CLF or the non-ME configuration CLF, and the target SE is required to work in the aggregation mode, and the CLF configuration mode is the ME configuration CLF. In the non-aggregated mode, only one SE can be activated, and the target SE is in a deactivated state. Obviously, the currently active SE is not the same SE as the target SE. While the currently active SE works in the non-aggregation mode, there is only one SE currently active, and therefore, the first activation unit 112 needs to deactivate the SE that is currently in the active state. Another scenario is that the target SE is required to work in the non-aggregation mode regardless of the working mode and the CLF configuration mode of the currently active SE, and the CLF configuration mode is configured for the ME by the CLF, because the target SE works in the non-aggregated mode and In the deactivated state, other SEs are not allowed to be activated simultaneously with this target SE, so the first activation unit 113 needs to deactivate the SE that is currently active.

The first query unit 113 is configured to query whether a first CLF configuration is saved, and the first CLF configuration includes a set of contactless protocol parameters applicable to the first target SE.

Since the currently active SEs are deactivated, it is not possible to determine the current configuration to the CLF. The contact protocol parameters apply to the new activated target SE, so the CLF needs to be reconfigured according to the new activated target SE.

In the embodiment, when the target SE is configured for CLF, the first query unit 114 queries whether the CLF configuration including the target SE identifier is saved. If the ME receives the request to activate the contactless application, the ME queries the CLF configuration to query whether the target SE identifier and the identifier of the contactless application to be activated are included in the CLF configuration. Since the saved CLF configuration including the target SE identifier may be more than one, when selecting the saved CLF configuration, the CLF configuration is required to include the target SE identifier, and the SE identifiers other than the target SE identifier are included as little as possible.

The first configuration unit 114 is configured to configure the CLF by using the set of non-contact protocol parameters if the first CLF configuration is queried.

If the saved CLF configuration is queried, the first configuration unit 115 configures the CLF using the set of non-contact protocol parameters in the saved CLF configuration, and does not need to perform conflict detection and non-contact protocol parameter calculation, and directly configures to the CLF, which greatly improves the configuration. The efficiency of the configuration of the contactless front end.

According to an embodiment of the present invention, when the management entity determines that one or more target security units on the terminal are in a deactivated state, the management entity may query the saved non-contact applicable to the one or more target security units. The front-end configuration configures the non-contact front end by using a set of non-contact protocol parameters in the contactless front-end configuration, and does not need to perform collision detection and non-contact protocol parameter calculation, thereby greatly improving the configuration efficiency of the non-contact front end.

FIG. 5 is a schematic structural diagram of a management entity in another terminal according to an embodiment of the present invention. The terminal also includes a management entity ME21, a security unit SE connected to the ME21, and a non-contact front end CLF, and the SE and the CLF. connection. The management entity 21 includes:

The first obtaining unit 211 is configured to obtain an identifier and a state of the first target security unit SE, where the state includes an activated state and a deactivated state.

In this embodiment, the first obtaining unit 211 includes a receiving unit 2111 and a second determining unit 2112. The second obtaining unit 2113 and the third query unit 2114.

The receiving unit 2111 is configured to receive a request to activate at least one contactless application.

This embodiment is described by taking an activation non-contact application as an example. The contactless application has a unique application identifier (English: Application Identifier, AID for short). The receiving unit 2111 receives an activation request of the contactless application through the GUI interface, and the request carries the AID. The contactless application to be activated here may be one or more.

The second determining unit 2112 is configured to determine that the SE where the at least one non-contact application is located is the target SE.

The second obtaining unit 2113 is configured to obtain an identifier of the target SE.

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

The third query unit 2114 is 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 implementation, the receiving unit 2111 is further configured to receive a request to activate the first SE, where the request includes an identifier of the first target SE.

Then, the receiving unit 2111 directly connects to the third query unit 2114.

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

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

The third determining unit 2121 is configured to determine an operating mode of the non-target SE that is currently in an active state.

The ME can query the working mode of the SE that is currently active.

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

When the third query unit 2114 queries that the target SE is in the deactivated state, the fourth determining unit 2122 further determines the working mode of the target SE.

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

Service strategies can include:

The attributes of the target SE, including:

For example, scenario A: The target SE only supports the non-aggregation mode, and the working mode of the SE or the ME can be determined according to the attribute. It should be noted that the working mode of the SE in the activated state is consistent with the working mode of the ME; scenario B: The service policy is that the most required SEs work at the same time. If the SE supports aggregation or non-aggregation, the ME determines that the ME and the SE should work in the aggregation mode. Scenario C: The service policy requires that an application on one SE be used as much as possible. The SE supports aggregation and non-aggregation. For aggregation, ME and SE should work in non-aggregate mode.

a fifth determining unit 2123, configured to: if it is determined that the working mode of the non-target SE that is currently in an active state is a non-aggregating mode and/or the working mode of the first target SE is a non-aggregating mode, determining to deactivate the A non-target SE that is currently active.

The first activation unit 213 is configured to deactivate the non-target SE that is currently in an active state, and activate the first target SE.

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

The first query unit 214 queries that there may be multiple CLF configurations that contain the target SE identifier. When the ME selects the saved CLF configuration, the ME includes the least SE identifiers other than the target SE identifier.

The ninth determining unit 215 is configured to determine that the first target SE included 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, that is, can be activated.

The first configuration unit 216 is configured to configure the CLF by using the set of non-contact protocol parameters if the first CLF configuration is queried.

If the first query unit 214 queries the target SE to use the ME configuration CLF, the first configuration unit 216 performs CLF configuration on the target SE. After the ME determines that each SE included in the CLF configuration is available, configure the CLF by using the non-contact protocol parameters in the CLF configuration, and activate all SEs included in the CLF configuration, or if all SEs included in the CLF configuration are activated, Then activate the contactless application that requested activation.

The fourth query unit 217 is configured to: if the ME queries that the first target SE is in an activated state, or the first target SE is in a deactivated state, and the ME determines an operating mode of the first target SE In the aggregation mode, it is queried whether the first contactless application is provided with a quick activation flag.

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

The third activation unit 219 is configured to activate the first SE and/or the first contactless application included in the first CLF configuration.

If the ME queries that the target SE is in the active 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 queries whether the contactless application to be activated is set with the quick activation flag, that is, The target SE is in an active state, and the target SE does not need to be activated. For the scenario where the target SE works in the aggregation mode, the target SE can coexist with the currently active SE, then the contactless application and/or The target SE performs a quick activation. Of course, if the non-contact application does not set the quick activation flag, the ME performs regular collision detection and contactless protocol parameter calculation on the target SE.

The second query unit 220 is configured to query whether the CLF configuration mode of the non-target SE that is currently in an active state is an ME configuration CLF.

The generating or updating unit 221 is configured to: if the result of the query is a CLF configured by the ME, generate or update the second CLF configuration according to all the contactless protocol parameters used by the current CLF, so that the ME activates the second again. Used when the first SE is applied to the CLF configuration.

Before deactivating the non-target SE that is currently in the active state, if the ME queries the CLF configuration mode of the non-target SE that is currently active, the ME configures the CLF, and the ME generates or updates according to all the non-contact protocol parameters used by the current CLF. The second CLF configuration, that is, if the second CLF configuration does not exist, the second CLF configuration is generated according to all the non-contact protocol parameters used by the current CLF; if the second CLF configuration already exists, all the non-contact protocol parameters used by the current CLF are updated. Corresponding configuration parameters in the second CLF configuration. This can be used directly when activating the first SE to which this CLF configuration applies. The saved CLF configuration includes an identifier of one or more SEs currently activated, one or more contactless application identifiers currently activated, priorities of these contactless applications, and usage of CLF configurations according to these SEs and contactless applications. A set of contactless protocol parameters.

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

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

The recording unit 224 is configured to record the identifier of the first target SE.

Since the ME has determined that the working mode of the target SE is the non-aggregation mode, the CEF configuration mode of the target SE may be two, that is, the ME configuration CLF or the non-ME configuration CLF, and the non-ME configuration CLF generally refers to the CLF configured by the SE. There are two different ways of processing depending on the configuration of the target SE's CLF.

The eighth determining unit 225 is configured to determine to deactivate the non-target SE that is currently in an active state when the first target SE is in an active state.

The second activation unit 226 is configured to deactivate the non-target SE that is currently in an active state.

The changing unit 227 is configured to change the working mode of the first target SE.

The fourth query unit 228 is configured to query whether a third CLF configuration is saved.

The third configuration unit 229 is configured to configure the CLF by using a set of non-contact 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 working mode of the target SE (for example, the aggregation mode is changed to the non-aggregation mode), at this time, the SE in the active state may be more than the target SE, then the ME Deactivate the non-target SE that is currently active.

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

The second configuration unit 231 is configured to configure the CLF using the calculated set of non-contact protocol parameters.

If the ME does not query to save the CLF configuration applicable to the target SE, the ME performs collision detection and contactless protocol parameter calculation according to the target SE and the application to be activated, and the conflict detection refers to whether the AID of the application on the target SE is activated or not Whether there is a conflict with the AID of the currently activated application, and whether the protocol parameters conflict; the contactless protocol parameter calculation refers to a set of contactless protocol parameters calculated by the ME suitable for all currently activated SE and contactless applications. After the ME calculates a set of non-contact protocol parameters, the CLF is configured using the set of non-contact protocol parameters.

According to an embodiment of the present invention, a terminal is configured to deactivate a non-target security unit that is currently in an active state according to an active mode of a non-target SE and a target SE that is currently in an active state and a CLF configuration manner thereof, and may When the CLF is configured by using the saved non-contact front-end configuration for the target SE, the non-contact front end is configured by using a set of non-contact protocol parameters in the non-contact front-end configuration, and the conflict detection and non-contact protocol parameter calculation are not required, and the CLF can be extremely The earth improves the efficiency of the configuration of the non-contact front end.

FIG. 6 is a schematic structural diagram of still another terminal according to an embodiment of the present invention. The terminal 3000 includes a memory 31, a processor 32, a security unit SE33, and a non-contact front end CLF34. The processor 32 is respectively connected to the memory 31 and the security unit. The SE33 is connected to the non-contact front end CLF34.

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

The processor 32 is configured to perform the following steps:

In an embodiment, the processor 32 is configured to perform the following steps before the step of activating the first target SE when the first target SE is in a deactivated state:

The non-target SE that is currently active is determined and deactivated according to an operating mode of the non-target SE currently in an active state and/or an operating mode of the first target SE.

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

In another embodiment, the processor 32 is configured to perform the step of obtaining the identifier of the first target SE and its status, including:

In still another embodiment, the processor 32 is configured to perform the deactivating the currently active state according to an operating mode of an SE that is currently in an active state and/or an operating mode of the first target SE. Non-target SE, including:

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

If the first CLF configuration is not queried, determining, according to the first target SE, a collision detection and a contactless protocol parameter calculation, determining a set of contactless protocol parameters applicable to the first target SE;

In still another embodiment, 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.

Determining a CLF configuration manner of the first target SE;

Whether the query saves the third CLF configuration;

In still another embodiment, the processor 32 is configured to perform the step of whether the query saves the first/third CLF configuration, and the processor is configured to perform the first using the query Before the step of configuring the CLF by a set of non-contact protocol parameters in the third CLF configuration, the following steps are also performed:

Querying whether the first non-contact application is queried if the first target SE is in an activated state, or the first target SE is in a deactivated state, and it is determined that the working mode of the first target SE is an aggregation mode Set with a quick activation tag;

According to the embodiment of the present invention, according to the working mode of the non-target SE and the target SE that are currently in the active state and the CLF configuration mode, the saved non-target SE may be used. When the front-end configuration is configured to configure the CLF, the non-contact front end is configured by using a set of non-contact protocol parameters in the non-contact front-end configuration, and collision detection and non-contact protocol parameter calculation are not required, which can greatly improve the configuration efficiency of the non-contact front end.

It should be noted that, for the foregoing method embodiments, for the sake of simple description, they are all expressed as a series of action combinations, but those skilled in the art should understand that the present invention is not limited by the described action sequence. Because certain steps may be performed in other sequences or concurrently in accordance with the present invention. In addition, those skilled in the art should also understand that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the present invention.

In the above embodiments, the descriptions of the various embodiments are different, and the details that are not detailed in a certain embodiment can be referred to the related descriptions of other embodiments.

The steps in the method of the embodiment of the present invention may be sequentially adjusted, merged, and deleted according to actual needs.

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

Through the description of the above embodiments, those skilled in the art can clearly understand that the present invention can be implemented in hardware, firmware implementation, or a combination thereof. When implemented in software, the functions described above may be stored in or transmitted 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 location to another. A storage medium may be any available media that can be accessed by a computer. For example, but not limited to, the computer readable medium may include a random access memory (RAM), a read-only memory (ROM), and an electrically erasable programmable read-only memory (Electrically Erasable Programmable). Read-Only Memory (EEPROM), Compact Disc Read-Only Memory (CD-ROM) or other optical disc storage, disk storage media or other magnetic storage devices, or can be used to carry or store an instruction or data structure. The desired program code and any other medium that can be accessed by the computer. Also. Any connection may suitably be a computer readable medium. For example, if the software uses coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL), or wireless such as infrared, radio, and microwave Where technology is transmitted from a website, server or other remote source, then coaxial cable, fiber optic cable, twisted pair, DSL or wireless technologies such as infrared, wireless and microwave are included in the fixing of the associated medium. As used in the present invention, a disk and a disc include a compact disc (CD), a laser disc, a compact disc, a digital versatile disc (DVD), a floppy disk, and a Blu-ray disc, wherein the disc is usually magnetically copied, and the disc is The laser is used to optically replicate the data. Combinations of the above should also be included within the scope of the computer readable media.

In summary, the above description is only a preferred embodiment of the technical solution of the present invention, and is not intended to limit the scope of the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Claims

A method for configuring a non-contact front-end CLF, the method comprising:

The management entity ME obtains an identifier and a state of the first target security unit SE, the state including an activated state and a deactivated state;

When the first target SE is in a deactivated state, the first target SE is activated;

Whether the ME query saves a first CLF configuration, where the first CLF configuration includes a set of contactless protocol parameters applicable to the first target SE;

If the first CLF configuration is queried, the ME configures the CLF using the set of contactless protocol parameters.
The method of claim 1 further comprising:

The ME determines and deactivates the non-target SE that is currently in an active state according to an operating mode of the non-target SE that is currently in an active state and/or an operating mode of the first target SE.
The method of claim 2, wherein before the ME configures the CLF using the set of contactless protocol parameters, the method further comprises:

The ME queries whether the CLF configuration mode of the non-target SE that is currently in an active state is an ME configuration CLF;

If the result of the query is that the ME configures the CLF, the ME generates or updates the second CLF configuration according to all contactless protocol parameters applicable to the CLF of the non-target SE that is currently in the active state.
The method according to any one of claims 1-3, wherein the ME obtains the identifier and status of the first target SE, including:

Receiving, by the ME, a request to activate a first SE, where the request includes an identifier of the first target SE,

Or the ME receives a request to activate at least one contactless application, and the ME determines that the SE where the at least one contactless application is located is the first target SE and obtains an identifier of the first target SE;

The ME queries the status of the first target SE according to the identifier of the first target SE.
The method according to any one of claims 1 to 4, wherein the ME determines the deactivation according to an operation mode of the non-target SE currently in an activated state and/or an operation mode of the first target SE. The non-target SE that is currently active, including:

Determining, by the ME, an operating mode of the non-target SE that is currently in an active state;

Determining, by the ME, an operating mode of the first target SE according to a service policy and/or an attribute of the first target SE;

If the ME determines that the working mode of the non-target SE that is currently in an active state is a non-aggregated mode and/or the working mode of the first target SE is a non-aggregated mode, the ME determines to deactivate the current A non-target SE that is active.
The method of any of claims 1-5, wherein the method further comprises:

If the first CLF configuration is not queried, the ME performs a collision detection and a contactless protocol parameter calculation according to the first target SE, and determines a set of contactless protocol parameters applicable to the first target SE;

The ME configures the CLF using a calculated set of contactless protocol parameters.
The method of any of claims 1-6, wherein the first or second CLF configuration further comprises an identification of the activated first SE, an identification of the activated first contactless application, and the The priority of a contactless application.
The method of any of claims 1-7, wherein the method further comprises:

Determining, by the ME, a CLF configuration manner of the first target SE;

If the CLF configuration mode of the first target SE is a 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.
The method of any of claims 1-8, wherein the method further comprises:

When the first target SE is in an active state, the ME determines and deactivates a non-target SE that is currently in an active state, and changes an operating mode of the first target SE;

Whether the ME query saves a third CLF configuration;

If the third CLF configuration is queried, the ME configures the CLF using a set of contactless protocol parameters in the queried third CLF configuration.
The method according to any one of claims 1-9, wherein the ME query whether the first/third CLF configuration is saved, and the ME uses the queried first/third CLF Before configuring a set of contactless protocol parameters in the configuration, the CLF also includes:

It is determined that the first target SE included in the first/third CLF configuration is available.
The method of any of claims 1-10, wherein the method further comprises:

If the ME queries that the first target SE is in an active 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 Querying whether the first contactless application is provided with a quick activation flag;

If the first contactless application is provided with the quick activation flag, the ME configures the CLF using the first CLF configuration that is queried, and activates the first SE and/or included in the first CLF configuration. The first non-contact application.
A terminal, the terminal includes: a management entity ME, a contactless front end CLF, and a first security unit SE, wherein the ME includes:

a first acquiring unit, configured to obtain an identifier and a state of the first target security unit SE, where the state includes an activated state and a deactivated state;

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

a first query unit, 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;

And a first configuration unit, configured to configure the CLF by using the set of non-contact protocol parameters if the first CLF configuration is queried.
The terminal of claim 12, wherein the ME further comprises:

a first determining unit, configured to determine to deactivate the non-target SE that is currently in an active state according to an operating mode of the non-target SE that is currently in an active state and/or an operating mode of the first target SE;

The first activation unit is further configured to deactivate the non-target SE that is currently in an active state.
The terminal of claim 13, wherein the ME further comprises:

a second query unit, configured to query whether the CLF configuration mode of the non-target SE that is currently in an active state is an ME configuration CLF;

Generating or updating a unit for generating or updating a second CLF configuration according to all contactless protocol parameters applicable to the CLF of the non-target SE currently in an active state if the result of the query is a CLF configured by the ME.
The terminal according to any one of claims 12 to 14, wherein the first obtaining unit comprises:

a receiving unit, configured to receive a request to activate the first SE, where the request includes an identifier 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 that the SE where the at least one non-contact application is located is the first target SE;

a second acquiring unit, configured to obtain an identifier of the first target SE;

The third query unit is configured to query the status of the first target SE according to the identifier of the first target SE.
The terminal according to any one of claims 12-15, wherein the first determining unit comprises:

a third determining unit, configured to determine an operating mode of the non-target SE that is currently in an active state;

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

a fifth determining unit, configured to determine, if the working mode of the non-target SE that is currently in an active state is a non-aggregating mode, and/or the working mode of the first target SE is a non-aggregating mode, determine to deactivate the A non-target SE that is currently active.
The terminal according to any one of claims 12-16, wherein the ME further comprises:

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

And a second configuration unit, configured to configure the CLF using the calculated set of non-contact protocol parameters.
The terminal according to any one of claims 12-17, wherein the first or second CLF configuration further comprises an identifier of the activated first SE, an identifier of the activated first contactless application, and the The priority of a contactless application.
The terminal according to any one of claims 12 to 18, wherein the ME further comprises:

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

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

a recording unit, configured to record an identifier of the first target SE.
The terminal according to any one of claims 12 to 19, wherein the ME further comprises:

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

a second activation unit, configured to deactivate a non-target SE that is currently in an active state;

a change unit, configured to change an operation mode of the first target SE;

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

And a third configuration unit, configured to configure the CLF by using a set of non-contact protocol parameters in the queried third CLF configuration, if the third CLF configuration is queried.
The terminal according to any one of claims 12 to 20, wherein the ME further comprises:

And a ninth determining unit, configured to determine that the first target SE included in the first/third CLF configuration is available.
The terminal according to any one of claims 12 to 20, wherein the ME further comprises:

a fourth query unit, configured to: if it is queried 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, Then querying whether the first contactless application is provided with a quick activation flag;

a fourth configuration unit, configured to configure the CLF by using the first CLF configuration that is queried if the first non-contact application is configured with the quick activation flag;

And a third activation unit, configured to activate the first SE and/or the first contactless application included in the first CLF configuration.
A terminal, comprising: a processor memory, a processor, a contactless front end CLF and at least one security unit SE, wherein the processor is configured to perform the following steps:

Obtaining an identifier and a state of the first target security unit SE, the state including an activated state and a deactivated state;

When the first target SE is in a deactivated state, the first target SE is activated;

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

If the first CLF configuration is queried, the CLF is configured using the set of contactless protocol parameters.
The terminal according to claim 23, wherein the processor is configured to perform the step of activating the first target SE when the first target SE is in a deactivated state, and is further configured to perform the following step:

The non-target SE that is currently active is determined and deactivated according to an operating mode of the non-target SE currently in an active state and/or an operating mode of the first target SE.
The terminal according to claim 24, wherein the processor is further configured to perform the following steps before the performing the using the set of contactless protocol parameters to configure the CLF:

Query whether the CLF configuration mode of the non-target SE that is currently active is a processor configuration CLF;

If the result of the query is a processor configuration CLF, the second CLF configuration is generated or updated according to all contactless protocol parameters applicable to the CLF of the non-target SE that is currently active.
The terminal according to any one of claims 23-25, wherein the processor is configured to perform the step of obtaining the identifier of the first target SE and its status, including:

Receiving a request to activate a first SE, the request including an identifier of the first target SE;

Or receiving a request to activate the at least one contactless application, determining that the SE where the at least one contactless application is located is the first target SE and obtaining the identifier of the first target SE;

And querying, according to the identifier of the first target SE, a status of the first target SE.
The terminal according to any one of claims 23-26, wherein the processor is configured to perform the determining according to an operating mode of an SE currently in an active state and/or an operating mode of the first target SE, The step of deactivating the non-target SE that is currently active includes:

Determining an operating mode of the non-target SE that is currently in an active state;

Determining an operation mode of the first target SE according to a service policy and/or an attribute of the first target SE;

Determining to deactivate the currently active non-target SE if it is determined that the working mode of the non-target SE currently in an active state is a non-aggregated mode and/or the working mode of the first target SE is a non-aggregating mode .
The terminal according to any one of claims 23-27, wherein the processor is further configured to perform the following steps:

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

The CLF is configured using a calculated set of contactless protocol parameters.
The terminal according to any one of claims 23 to 28, wherein the first or second CLF configuration further comprises an identifier of the activated first SE, an identifier of the activated first contactless application, and the The priority of a contactless application.
The terminal according to any one of claims 23 to 29, wherein the processor is further configured to perform the following steps:

Determining a CLF configuration manner of the first target SE;

If the CLF configuration mode of the first target SE is a non-processor configuration CLF, the CLF configuration authority is granted to the first target SE and the identifier of the first target SE is recorded.
The terminal according to any one of claims 23-30, wherein the processor is further configured to perform the following steps:

Determining and deactivating a non-target SE that is currently in an active state when the first target SE is in an active state, and changing an operating mode of the first target SE;

Whether the query saves the third CLF configuration;

If the third CLF configuration is queried, the CLF is configured using a set of contactless protocol parameters in the queried third CLF configuration.
The terminal according to any one of claims 23 to 31, wherein the processor is configured to perform a step of whether the query has a first/third CLF configuration, and the processor is configured to perform the The step of configuring the CLF using a set of contactless protocol parameters in the first/third CLF configuration that is queried is also used to perform the following steps:

It is determined that the first target SE included in the first/third CLF configuration is available.
The terminal according to any one of claims 23 to 32, wherein the processor is further configured to perform the following steps:

Querying whether the first non-contact application is queried if the first target SE is in an activated state, or the first target SE is in a deactivated state, and it is determined that the working mode of the first target SE is an aggregation mode Set with a quick activation tag;

If the first contactless application is provided with the quick activation flag, using the queried The first CLF configuration configures the CLF and activates the first SE and/or the first contactless application included in the first CLF configuration.