WO2015184591A1 - 一种路由设置方法及终端设备 - Google Patents
一种路由设置方法及终端设备 Download PDFInfo
- Publication number
- WO2015184591A1 WO2015184591A1 PCT/CN2014/079103 CN2014079103W WO2015184591A1 WO 2015184591 A1 WO2015184591 A1 WO 2015184591A1 CN 2014079103 W CN2014079103 W CN 2014079103W WO 2015184591 A1 WO2015184591 A1 WO 2015184591A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- routing
- exclusive
- default
- further configured
- routing table
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/74—Address processing for routing
- H04L45/745—Address table lookup; Address filtering
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/54—Organization of routing tables
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/02—Topology update or discovery
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/08—Access security
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/80—Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/06—Authentication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/40—Security arrangements using identity modules
- H04W12/45—Security arrangements using identity modules using multiple identity modules
Definitions
- the present invention relates to the field of communications, and in particular, to a route setting method and a terminal device.
- SE Secure Element
- NFCC Near Field Communication Controller
- the terminal may wish to have one SE of multiple SEs as an exclusive SE.
- the NFC (Near Field Communication) communication peer selects only the application of the SE on the UICC according to the NFC routing mechanism, so in other SEs or HCEs.
- the application cannot be selected by the NFC communication peer. Therefore, the terminal may be required to only allow the activation of the exclusive SE and the activation of the non-exclusive SE.
- the SE setting command is sent by the CPU to the NFCC to control the activation/deactivation of the SE.
- the SE setting instruction includes an ID of the SE that needs to be controlled.
- the HCE can be regarded as a non-exclusive SE, and the terminal should stop routing information received through the NFC technology to the HCE.
- the terminal can control the SE through a mode setting instruction. Since the target ID of the mode setting instruction cannot be the ID of the HCE, the mode setting instruction cannot be used to deactivate the H C E, and the exclusive requirement of the exclusive access exclusive E cannot be guaranteed. Summary of the invention
- Embodiments of the present invention provide a route setting method and a terminal device, which can be avoided Use HCE to correctly configure the routing table to ensure the normal operation of the exclusive SE accessed by the terminal.
- the embodiment of the present invention uses the following technical solutions:
- a routing setting method including:
- the routing table containing only the routing items corresponding to the exclusive SE is constructed; if the default routing entry is supported, the newly accessed SE is set as the default routing target SE, and the constructed
- the routing table may or may not contain routing entries corresponding to the exclusive SE.
- the method further includes: if the newly accessed SE is not Excluding SE, the SE identifier is set to a first value; if the newly accessed SE is an exclusive SE, the SE identifier is set to a second value and the ID of the newly accessed SE is recorded; The first value indicates that the exclusive SE is not currently accessed in the terminal, and the second value indicates that the exclusive SE is currently accessed in the terminal.
- the method further includes:
- the method further includes:
- the routing entry corresponding to the newly-accessed SE is added to the current routing table to construct a routing table; when the default routing entry is supported, it is determined whether a re-designation is required.
- the default route target SE, and the constructed routing table may or may not include a routing entry corresponding to the default route target SE.
- the corresponding routing entry constructs a routing table. If the default routing entry is supported, the constructed routing table may or may not include the routing entry corresponding to the newly accessed exclusive SE.
- the routing entry includes a route entry that is the HCE; if the routing table does not include a route entry that is the HCE, the default is not supported.
- the routing entry the routing entry corresponding to the newly-accessed exclusive SE is added to the current routing table to construct a routing table. If the default routing entry is supported, the constructed routing table may or may not include the new access.
- the exclusive routing entry corresponding to the SE is not supported.
- routing table includes a routing entry whose target is the HCE, if it is detected that the default routing entry is not supported, the routing entry corresponding to the HCE and the non-exclusive SE in the routing table is deleted and written into the routing entry.
- a routing entry corresponding to the newly-accessed SE constructing a routing table including only the routing entries corresponding to the exclusive accessing exclusive SE; if the default routing entry is supported, the constructed routing table may or may not include the new routing The routing entry corresponding to the exclusive SE.
- the method further includes:
- the SE identifier is the second value, determining whether the ID of the currently removed SE is the same as the ID of the exclusive SE recorded in the terminal;
- the routing entry corresponding to the SE in the connected state and the routing information included in the HCE are configured to construct a routing table. Check whether the default routing entry is supported. If yes, specify an SE as the default routing target SE. And the constructed routing table may or may not include a routing entry corresponding to the default route target SE;
- the method further includes:
- the SE identifier is not the second value, delete the routing entry corresponding to the currently removed SE in the current routing table, and determine whether the currently removed SE is supported when the default routing entry is supported. For the default route target SE, if yes, then re-designate an SE as the default route target SE.
- the method further includes:
- the routing table is constructed according to the routing item corresponding to the SE in the connected state; detecting whether the default routing entry is supported, and if yes, re-designating an SE as the default routing target SE And the constructed routing table may or may not include a routing entry corresponding to the default route target SE;
- the HCE exists in the terminal device, detecting whether the current routing table includes a routing entry whose target is the HCE;
- the routing table is constructed according to the routing entry corresponding to the SE in the connected state and the routing entry corresponding to the HCE; detecting whether the default routing entry is supported, if supported Re-designating an SE as the default route target SE, and the constructed routing table may or may not include a routing entry corresponding to the default route target SE;
- the current routing table does not include a routing entry that is the HCE, the current routing table is configured to include any routing entry corresponding to the non-exclusive SE; if the current routing table includes any non-exclusive The routing entry corresponding to the SE deletes the routing entry corresponding to the currently excluded exclusive SE to construct a routing table; detects whether the default routing entry is supported, and if so, re-specifies an SE as the default routing target SE, and The constructed routing table may or may not include a routing entry corresponding to the default routing target SE;
- the routing table is constructed according to the routing item corresponding to the SE in the connected state and the routing information included in the HCE; And if yes, re-designating an SE as the default route target SE, and the constructed routing table may or may not include a routing item corresponding to the default route target SE;
- a terminal device including:
- a detecting unit configured to detect whether the newly accessed security unit SE is an exclusive SE; the detecting unit is further configured to: after detecting that the newly accessed SE is an exclusive SE, detecting whether to support setting a default routing item;
- a building unit configured to: after the detecting unit detects that the default routing item is not supported, construct a routing table that only includes the routing item corresponding to the exclusive SE;
- a setting unit configured to: after the detecting unit detects that the setting default routing item is supported, set the newly accessed SE as a default routing target SE, and the constructed routing table may or may not include a routing item corresponding to the exclusive SE. .
- the setting unit is further configured to:
- the SE identifier is set to a first value; if the newly accessed SE is an exclusive SE, the SE identifier is set to a second value and the record is recorded The ID of the newly accessed SE; the first value indicates that the exclusive SE is not currently accessed in the terminal, and the second value indicates that the exclusive SE is currently accessed in the terminal.
- the setting unit is further configured to:
- an initial value of the SE identifier is the first value
- the terminal device further includes:
- a determining unit configured to determine whether the SE identifier is the first value
- an acquiring unit configured to acquire a current routing table if the determining unit determines that the SE identifier is a first value.
- the constructing unit is further configured to: after the detecting unit detects that the newly accessed SE is not an exclusive SE, add a routing item corresponding to the newly accessed SE in the current routing table, and construct a routing table. ;
- the determining unit is further configured to: when the detecting unit detects that the setting default routing item is supported, determine whether the default routing target SE needs to be re-specified, and the constructed routing table may or may not include the default routing target SE. Corresponding routing entry.
- the detecting unit is further configured to detect the terminal device Whether there is a host card simulator HCE;
- the constructing unit is further configured to: if the detecting unit detects that the HCE does not exist in the terminal device, add an exclusive SE corresponding to the new access in the current routing table when the default routing entry is not supported.
- the routing entry constructs a routing table. If the default routing entry is supported, the constructed routing table may or may not include the routing entry corresponding to the newly accessed exclusive SE.
- the detecting unit is further configured to: if the detecting unit detects that the HCE exists in the terminal device, detecting whether the routing table includes a routing item whose target is the HCE; the building unit is further configured to: The detecting unit detects that the routing entry does not include the routing entry whose target is the HCE, and adds the routing entry corresponding to the newly accessed exclusive SE in the current routing table when the default routing entry is not supported.
- the routing table is constructed. If the default routing entry is supported, the constructed routing table may or may not include the routing entry corresponding to the newly accessed exclusive SE.
- the constructing unit is further configured to: if the detecting unit detects that the routing table includes a routing entry whose target is the HCE, delete the routing table when the detecting unit detects that the default routing entry is not supported.
- the routing entry corresponding to the HCE and the non-exclusive SE is written into the routing entry corresponding to the newly accessed SE, and a routing table including only the routing entry corresponding to the exclusive accessing exclusive SE is constructed; Routing item, the constructed routing table may or may not include the route corresponding to the exclusive accessing exclusive SE Item.
- the detecting unit is further configured to detect whether a SE is removed
- the obtaining unit is further configured to: after the detecting unit detects that the SE is removed, acquire an ID of the currently removed SE;
- the determining unit is further configured to: determine whether the SE identifier is the second value
- the determining unit is further configured to: if the SE identifier is the second value, determine whether the ID of the currently removed SE is the same as the ID of the exclusive SE recorded in the terminal;
- the constructing unit is further configured to: if the determining unit determines that the ID of the currently removed SE is the same as the ID of the exclusive SE recorded in the terminal, the routing item corresponding to the SE in the connected state, the HCE
- the routing information is configured to construct a routing table.
- the detecting unit is further configured to: detect whether a default routing entry is supported.
- the building unit is further configured to: if the detecting unit detects that a default routing entry is supported, the construct includes or does not include a routing table of the routing item corresponding to the default route target SE;
- the setting unit is further configured to: after the detecting unit detects that the setting default routing item is supported, re-designating an SE as the default routing target SE;
- the terminal device further includes an obtaining unit, configured to acquire a configuration success message, where the setting unit is further configured to: set the SE identifier to the first value, and select an exclusive SE of the current record in the terminal.
- the ID is updated to be invalid.
- the constructing unit is further configured to: if the determining unit determines that the SE identifier is not the second value, delete a routing item corresponding to the currently removed SE in the current routing table;
- the determining unit is further configured to determine the current when supporting setting a default routing item Whether the removed SE is the default route target SE;
- the determining unit is further configured to: determine, when the setting of the default routing item is supported, whether the currently removed SE is the default routing target SE;
- the setting unit is further configured to: after the determining unit determines that the currently removed SE is the default route target SE, re-designate an SE as the default routing target SE.
- the detecting unit is further configured to: detect whether the HCE exists in the terminal device;
- the building unit is further configured to: construct a routing table according to a routing item corresponding to the SE in the connected state;
- the detecting unit is further configured to: detect whether to support setting a default routing item; the setting unit is further configured to: after detecting to support setting a default routing item, re-designating an SE as the default routing target SE, and the constructed routing table may be The routing item corresponding to the default route target SE is included or not included;
- the obtaining unit is further configured to: obtain a configuration success message
- the setting unit is further configured to: set the SE identifier to the first value, and update the ID of the exclusive SE currently recorded in the terminal to be invalid.
- the detecting unit is further configured to: if the HCE exists in the terminal device, detect whether a routing entry whose target is the HCE is included in the current routing table;
- the constructing unit is further configured to: after the detecting unit detects that the current routing table includes a routing entry that is the HCE, construct the routing entry corresponding to the SE in the connected state, and the routing entry corresponding to the HCE Routing table
- the detecting unit is further configured to: detect whether to support setting a default routing item; the setting unit is further configured to: if the detecting unit detects that a default routing item is supported, re-designate an SE as the default routing target SE, and Build route
- the table may or may not include a routing entry corresponding to the default route target SE; the obtaining unit is further configured to: obtain a configuration success message;
- the setting unit is further configured to: set the SE identifier to the first value, and update the ID of the exclusive SE currently recorded in the terminal to be invalid.
- the detecting unit is further configured to: after detecting, by the detecting unit, that the current routing table does not include a routing entry whose target is the HCE, detecting whether the current routing table includes any routing entry corresponding to the non-exclusive SE ;
- the constructing unit is further configured to: after the detecting unit detects that the current routing table includes a routing item corresponding to any non-exclusive SE, delete the routing item corresponding to the currently excluded exclusive item to construct a routing table;
- the detecting unit is further configured to: detect whether to support setting a default routing item; the setting unit is further configured to: if the detecting unit detects that a default routing item is supported, re-designate an SE as the default routing target SE, and The constructed routing table may or may not include a routing entry corresponding to the default routing target SE;
- the obtaining unit is further configured to: obtain a configuration success message
- the setting unit is further configured to: set the SE identifier to the first value, and update the ID of the exclusive SE currently recorded in the terminal to be invalid.
- the constructing unit is further configured to: if the current routing table does not include any routing item corresponding to the non-exclusive SE, the routing item corresponding to the SE in the connected state, and the routing information included in the HCE, construct a routing table. ;
- the detecting unit is further configured to: detect whether to support setting a default routing item; the setting unit is further configured to: if the detecting unit detects that a default routing item is supported, re-designate an SE as the default routing target SE, and The constructed routing table may or may not include a routing entry corresponding to the default routing target SE;
- the obtaining unit is further configured to: obtain a configuration success message;
- the setting unit is further configured to: set the SE identifier to the first value, and update an ID of an exclusive SE currently recorded in the terminal to be invalid.
- a terminal device including:
- the device host DH is configured to detect whether the newly accessed security unit SE is an exclusive SE; the DH is further configured to: after detecting that the newly accessed SE is an exclusive SE, detecting whether to support setting a default routing item;
- the DH is configured to, after detecting that the default routing entry is not supported, construct a routing table that only includes routing entries corresponding to the exclusive SE;
- the DH is configured to set the newly accessed SE as a default route target SE after detecting that the default route entry is supported, and the constructed routing table may or may not include a routing entry corresponding to the exclusive SE.
- the DH is further configured to:
- the SE identifier is set to a first value; if the newly accessed SE is an exclusive SE, the SE identifier is set to a second value and the record is recorded The ID of the newly accessed SE; the first value indicates that the exclusive SE is not currently accessed in the terminal, and the second value indicates that the exclusive SE is currently accessed in the terminal.
- the method further includes:
- an initial value of the SE identifier is the first value
- the DH is configured to determine whether the SE identifier is the first value, and the DH is configured to obtain a current routing table if the SE identifier is determined to be the first value.
- the DH is further configured to: after detecting that the newly accessed SE is not an exclusive SE, add a routing entry corresponding to the newly accessed SE in the current routing table, and construct a routing table;
- the DH is further configured to: when it is detected that the default routing entry is supported, determine whether the default routing target SE needs to be re-specified, and the configured routing table may or may not include the routing entry corresponding to the default routing target SE.
- the DH is further configured to detect whether a host card emulator HCE exists in the terminal device;
- the DH is further configured to: if the HCE is not detected in the terminal device, add a route entry corresponding to the exclusive accessing SE of the newly accessed routing entry in the current routing table when the default routing entry is not supported. If the default routing entry is supported, the configured routing table may or may not include the routing entry corresponding to the newly accessed exclusive SE.
- the DH is further configured to: if it is detected that the HCE exists in the terminal device, detect whether a routing entry whose target is the HCE is included in the routing table;
- the DH is further configured to: if it is detected that the routing entry does not include a routing entry that is the HCE, add the exclusive access of the new access to the current routing table when the default routing entry is not supported.
- the routing entry corresponding to the SE constructs a routing table. If the default routing entry is supported, the constructed routing table may or may not include the routing entry corresponding to the newly accessed exclusive SE.
- the DH is further configured to: if it is detected that the routing table includes a routing entry whose target is the HCE, delete the HCE and the non-exclusive SE corresponding to the routing table when detecting that the default routing entry is not supported.
- the routing entry is written to the routing entry corresponding to the newly accessed SE, and a routing table containing only the routing entries corresponding to the exclusive accessing exclusive SE is constructed; if the default routing entry is supported, the constructed routing table may be configured.
- a routing entry corresponding to the exclusive accessing SE of the new access is included or not included.
- the DH is further configured to detect whether a SE is removed
- the DH is further configured to: after detecting that the SE is removed, obtain an ID of the SE that is currently removed;
- the DH is further configured to: determine whether the SE identifier is the second value; the DH is further configured to: if the SE identifier is the second value, determine the currently removed Whether the ID of the SE is the same as the ID of the exclusive SE recorded in the terminal;
- the DH is further configured to: if it is determined that the ID of the currently deleted SE is the same as the ID of the exclusive SE recorded in the terminal, according to the routing item corresponding to the SE in the connected state, and the routing information included in the HCE, Building a routing table;
- the DH is further configured to: detect whether a default routing entry is supported.
- the DH is further configured to: if the detection supports setting a default routing entry, construct a routing table that includes or does not include a routing entry corresponding to the default routing target SE;
- the DH is further configured to: after detecting that the setting default routing item is supported, re-designating an SE as the default routing target SE;
- the DH is further configured to: obtain a configuration success message
- the DH is further configured to set the SE identifier to the first value, and update the ID of the exclusive SE currently recorded in the terminal to be invalid.
- the DH is further configured to, if it is determined that the SE identifier is not the second value, delete a routing entry corresponding to the currently removed SE in the current routing table;
- the DH is further configured to: determine, when setting a default routing item, whether the currently removed SE is the default routing target SE;
- the DH is further configured to: determine, when the setting of the default routing item is supported, whether the currently removed SE is the default routing target SE;
- the DH is further configured to: after determining that the currently removed SE is the default route target SE, re-designate an SE as the default route target SE.
- the DH is configured to detect whether the HCE exists in the terminal device, and the DH is further configured to: construct a routing table according to a routing item corresponding to the SE in the connected state;
- the DH is further configured to: detect whether a default routing entry is supported.
- the DH is further configured to: after detecting the setting of the default routing entry, re-designating an SE as the default routing target SE, and the configured routing table may or may not include the routing entry corresponding to the default routing target SE;
- the DH is further configured to: obtain a configuration success message
- the DH is further configured to set the SE identifier to the first value, and update the ID of the exclusive SE currently recorded in the terminal to be invalid.
- the DH is configured to: if the HCE exists in the terminal device, detect whether a routing entry whose target is the HCE is included in the current routing table;
- the DH is further configured to: after detecting that the current routing table includes a routing entry that is the HCE, construct a routing table according to the routing entry corresponding to the SE in the connected state and the routing entry corresponding to the HCE;
- the DH is further configured to: detect whether a default routing entry is supported.
- the DH is further configured to: if the detection supports setting a default routing entry, re-designating an SE as the default routing target SE, and the constructed routing table may or may not include a routing entry corresponding to the default routing target SE;
- the DH is further configured to: obtain a configuration success message
- the DH is further configured to set the SE identifier to the first value, and update the ID of the exclusive SE currently recorded in the terminal to be invalid.
- the DH is configured to: when the detecting the current routing table does not include a target, After the routing entry of the HCE, detecting whether the current routing table includes any routing entry corresponding to the non-exclusive SE;
- the DH is further configured to: after detecting the routing item corresponding to any non-exclusive SE in the current routing table, delete the routing item construction routing table corresponding to the currently excluded exclusive SE;
- the DH is further configured to: detect whether a default routing entry is supported.
- the DH is further configured to: if the detection supports setting a default routing entry, re-designating an SE as the default routing target SE, and the constructed routing table may or may not include a routing entry corresponding to the default routing target SE;
- the DH is further configured to: obtain a configuration success message
- the DH is further configured to set the SE identifier to the first value, and update the ID of the exclusive SE currently recorded in the terminal to be invalid.
- the DH is configured to: if the current routing table does not include any routing item corresponding to the non-exclusive SE, construct a routing table according to the routing item corresponding to the SE in the connected state and the routing information included in the HCE;
- the DH is further configured to: detect whether a default routing entry is supported.
- the DH is further configured to: if the detecting unit detects that the default routing entry is supported, re-designate an SE as the default routing target SE, and the constructed routing table may or may not include the default routing target SE. Routing item
- the DH is further configured to: obtain a configuration success message
- the DH is further configured to set the SE identifier to the first value, and update the ID of the exclusive SE currently recorded in the terminal to be invalid.
- the routing setting method and the terminal device provided by the embodiments of the present invention may terminate the operation of all non-exclusive SEs including the HCE by setting a routing table after the terminal accesses the exclusive SE.
- the method and the terminal device provided by the present invention can avoid using the HCE, thereby ensuring the normal operation of the newly accessed exclusive SE.
- FIG. 1 is a schematic flowchart of a route setting method according to Embodiment 1 of the present invention
- FIG. 2 is a schematic flowchart of a route setting method according to Embodiment 2 of the present invention
- FIG. 3 is a schematic flow chart of a route setting method according to Embodiment 3 of the present invention.
- FIG. 4 is a schematic flow chart of a route setting method according to Embodiment 4 of the present invention.
- FIG. 5 is a schematic flow chart of a route setting method according to Embodiment 5 of the present invention.
- FIG. 6 is a structural block diagram of a terminal device according to Embodiment 6 of the present invention.
- FIG. 7 is a structural block diagram of a terminal device according to Embodiment 7 of the present invention.
- the SE can provide a secure and reliable environment for the mobile payment of the terminal. Therefore, as long as the terminal has mastered the control of the SE, the terminal has mastered the entry of the mobile payment application to the terminal.
- the operator hopes that the terminal manufacturer can provide the technical solution, so that after the UICC card of the SE released by the operator is installed on the terminal, only the SE on the UICC card is allowed to work normally, and the SE controlled by the non-mobile operator on other media is required to be Shielded off.
- the SE on the UICC card can be referred to as an exclusive SE, and the SEs controlled by non-mobile operators on other media are referred to as non-exclusive SEs.
- the terminal needs to terminate the operation of the non-exclusive SE to ensure the normal operation of the exclusive SE.
- the current terminal can also implement the HCE through software simulation.
- the HCE is non-exclusive, and the terminal needs to terminate the operation of the HCE after the SE access on the UICC card.
- some NFC routing mechanisms also support a silent To identify the route, only one SE/HCE can be configured as the default route target SE. The technical idea is that after all processing, the routing request that cannot find the matching processing item will be forwarded to the default routing target SE/HCE for processing. Therefore, when constructing the routing table, the terminal may include or not include the routing item corresponding to the default route target SE/HCE in the routing table.
- the embodiment of the invention provides a route setting method. As shown in FIG. 1, the method includes the following steps:
- the macro terminal includes a DH (Device Host), an NFCC, and a CPU (Central Processing Unit).
- the NFCC may have the ability to delete routing entries or may not delete routing entries.
- the DH needs to determine whether the newly accessed SE is an exclusive SE or a non-exclusive SE. If the newly accessed SE is an exclusive SE, step 102 is performed.
- the DH of the terminal device is set with the SE identifier.
- the initial value of the SE identifier is the first value.
- the first value indicates that the exclusive SE is not currently accessed in the terminal.
- the DH of the terminal device detects that the SE identifier is the second value, it does not need to perform configuration processing and does not change the current routing table.
- the second value indicates that the exclusive SE is currently accessed in the terminal. This is because, depending on the commercial needs of the operator, terminal equipment is usually only allowed to guarantee the normal operation of an exclusive SE. That is to say, if the current terminal device has access to the exclusive SE, no configuration processing is performed regardless of whether the newly accessed SE is an exclusive SE.
- the SE identifier is set to a first value; if the newly accessed SE is an exclusive SE, the DH of the terminal device identifies the SE identifier The sign is set to the second value and the ID of the newly accessed SE is recorded.
- the ID of the newly accessed SE is recorded as the ID of the exclusive SE currently accessed in the terminal, so as to determine whether the exclusive SE is currently accessed in the terminal when the SE is removed. Then the corresponding configuration processing is performed to save system overhead.
- the routing entry corresponding to the newly accessed SE is added to the current routing table to construct a routing table.
- the default routing entry is supported, it is determined whether the default routing target SE needs to be re-specified, and the constructed routing table may or may not include the routing entry corresponding to the default routing target SE.
- DH can always delete a specific routing item by constructing a new routing table.
- the NFCC may or may not have the ability to delete the routing table. Therefore, it is necessary to distinguish between the case where the NFCC can delete the routing table or the case where the routing table cannot be deleted.
- the NFCC of the terminal can delete the routing table, after the DH of the terminal device detects whether the newly accessed security unit SE is an exclusive SE, it is also required to detect whether the host card simulator HCE exists in the terminal device. . If the HCE does not exist in the terminal device, if the default routing entry is not supported, the routing entry corresponding to the exclusive access SE of the newly accessed routing table is added to the current routing table to construct a routing table.
- the routing table constructed may or may not include a routing entry corresponding to the newly accessed exclusive SE.
- the terminal After detecting the presence of the HCE in the terminal, it is also necessary to detect whether the routing entry contains the routing entry corresponding to the HCE, because if there is an HCE in the terminal but there is no routing entry corresponding to the HCE in the routing table, the HCE cannot be operated. In this way, after accessing the exclusive SE, the terminal activates the non-exclusive SE through the SE setting command, activates the exclusive SE, and thus ensures the normal operation of the exclusive SE.
- the routing entry includes a route entry that is the HCE; if the routing table does not include a route entry that is the HCE, the default is not supported.
- the routing entry the routing entry corresponding to the newly-accessed exclusive SE is added to the current routing table to construct a routing table. If the default routing entry is supported, the constructed routing table may or may not include the new access.
- the exclusive routing entry corresponding to the SE is not supported.
- routing table includes a routing entry whose destination is the HCE, when detecting that the default routing entry is not supported, deleting the HCE and the non-exclusive in the routing table
- the routing entry corresponding to the SE is written to the routing entry corresponding to the newly accessed SE, and a routing table including only the routing entries corresponding to the exclusive accessing exclusive SE is constructed; if the default routing entry is supported, the constructed routing is performed.
- the table may or may not contain a routing entry corresponding to the newly accessed exclusive SE.
- Whether the terminal supports the default route setting determines whether the terminal can include or exclude the routing entry corresponding to the default route target SE/HCE in the routing table when constructing the routing table. Therefore, it is necessary to detect whether the terminal has the capability of setting default routing entries.
- the DH of the terminal device constructs a routing table containing only the routing entries corresponding to the exclusive SE according to the newly accessed exclusive SE. It should be noted that the routing table here is different from the routing entries constructed by adding the new access exclusive SE in the current routing table. A detailed distinction will be made in the following examples.
- the terminal since the terminal does not support setting the default routing entry, the routing request that cannot find the matching processing item cannot be solved by the processing of the default routing item target SE, so this is that the constructed routing table cannot contain other non-exclusive SE corresponding A routing entry that only contains routing entries for exclusive SEs.
- the NFC routing mechanism also supports a default route setting, all route requests that cannot be found to match the processing items after processing are forwarded to the default route target SE/HCE for processing.
- the new access exclusive SE may be set as the default route item target SE, and the new SE request is processed by the default route. Therefore, when constructing the routing table, the terminal may include or not include the routing item corresponding to the default route target SE/HCE in the routing table. In fact, the routing table may be empty after step 104 because the newly accessed exclusive SE is treated as a default route, so the routing table may not contain any routing entries.
- the present invention also provides a route setting method, and when the SE is removed, the route is correctly configured according to whether there is an exclusive SE currently in the terminal.
- the DH (or NFCC) of the terminal device detects that the SE is removed.
- the DH of the terminal device then obtains the ID of the currently removed SE by receiving an instruction from the NFCC of the terminal device.
- the DH obtains the ID corresponding to the SE with the NFCEE Status value of 0x02 from the NFCEE_DISCOVER_NTF (Near Field Communication Discovery Message) sent by the NFCC (that is, the NFCEE ID of the currently removed SE). ).
- the DH of the terminal device determines whether the current SE identifier is the second value, because whether the exclusive SE in the terminal has affected the routing configuration when the SE is removed. By distinguishing, the routing table can be correctly configured. The DH of the terminal device does not need to reset the routing table every time the SE is removed, which greatly saves system overhead.
- the current routing table needs to be emptied only to the routing item of the exclusive SE. Therefore, when the exclusive SE is removed, the routing item of the non-exclusive SE that was previously terminated needs to be re-re-routed. Write to the routing table.
- the route table of the non-exclusive SE is directly written without clearing the routing table, and only the routing items of the non-exclusive SE need to be deleted. Since the terminal cannot recognize whether the exclusive SE has been accessed, it is impossible to determine whether the current routing table includes only the routing entries of the exclusive SE or the routing entries of the non-exclusive SEs. Therefore, each time an SE is removed, the terminal will use the routing table. Clearing and rewriting the routing entries of each non-exclusive SE leads to a large overhead of the terminal system.
- the SE identifier is not the second value, delete the routing entry corresponding to the currently removed SE in the current routing table, and determine whether the currently removed SE is supported when the default routing entry is supported. For the default route target SE, if yes, then re-designate an SE as the default route target SE. A4. If the same, the routing entry corresponding to the SE in the connected state, and the routing information included in the HCE, construct a routing table; detect whether the default routing entry is supported, and if yes, re-designate an SE as the default route.
- the target SE and the constructed routing table may or may not include a routing entry corresponding to the default routing target SE.
- A5. Acquire a configuration success message, set the SE identifier to the first value, and update the ID of the exclusive SE currently recorded in the terminal to be invalid.
- NFCC may or may not have the ability to delete routing tables. Therefore, it is necessary to distinguish between the fact that the NFCC can delete the routing table or the routing table cannot be deleted.
- the terminal device In order for the terminal device to correctly construct the routing table. For example, if the NFCC may have the ability to delete the routing table, the terminal needs to detect whether there is an HCE. After the SE is removed, the routing entry destined for the HCE needs to be rewritten in the presence of the HCE.
- the NFCC of the terminal device can delete the routing item, after determining that the ID of the currently removed SE is the same as the ID of the exclusive SE recorded in the terminal, it is also required to detect whether the terminal device exists.
- the HCE The HCE.
- the routing table is constructed according to the routing item corresponding to the SE in the connected state; detecting whether the default routing entry is supported, and if yes, re-designating an SE as the default routing target SE And the constructed routing table may or may not include a routing entry corresponding to the default routing target SE. Then, a configuration success message is obtained, the SE identifier is set to the first value, and the ID of the exclusive SE currently recorded in the terminal is updated to be invalid. In addition, a SE mode setting command is generated to activate or deactivate the SE according to the SE mode setting command.
- the HCE exists in the terminal device, it is detected whether the current routing table includes a routing entry whose target is the HCE; if the current routing table includes a routing entry whose target is the HCE, Constructing a routing table according to the routing entry corresponding to the SE in the connected state; detecting whether the default routing entry is supported, and if yes, re-designating an SE as the default routing target SE, and the constructed routing table may or may not include the The routing entry corresponding to the default route target SE. Get configuration successfully And setting the SE identifier to the first value, and updating the ID of the exclusive SE currently recorded in the terminal to be invalid.
- the current routing table is configured to include any routing entry corresponding to the non-exclusive SE; if the current routing table includes any non-exclusive
- the routing entry corresponding to the SE constructs a routing table according to the routing entry corresponding to the SE in the connected state; detects whether the default routing entry is supported, and if so, re-specifies an SE as the default routing target SE, and constructs the routing table.
- the route item corresponding to the default route target SE may be included or not included; the configuration success message is obtained, the SE identifier is set to the first value, and the ID of the exclusive SE currently recorded in the terminal is updated to invalid.
- the routing table is constructed according to the routing item corresponding to the SE in the connected state and the routing information included in the HCE; And if yes, re-designating an SE as the default route target SE, and the constructed routing table may or may not include a routing item corresponding to the default route target SE; obtain a configuration success message, and set the SE identifier For the first value, the ID of the exclusive SE currently recorded in the terminal is updated to be invalid.
- the routing setting method and the terminal device provided by the embodiments of the present invention may terminate the operation of all non-exclusive SEs including the HCE by setting a routing table after the terminal accesses the exclusive SE.
- the method and the terminal device provided by the present invention can avoid the use of the HCE, thereby ensuring the normal operation of the newly accessed exclusive SE.
- the embodiment of the present invention provides a route setting method, which is applied to a terminal device that has the capability of deleting a routing table by the NFCC. As shown in FIG. 2, the method includes the following steps: 201. Set the SE identifier; The initial value of the character is the first value.
- the macro terminal includes DH and NFCC.
- the NFCC may have the ability to delete routing entries or may not delete routing entries.
- the DH of the terminal device sets the SE identifier. Initially, there is no access to the exclusive SE in the terminal, and the status is indicated by the first value.
- the value of the SE identifier may be a first value or a second value, where the first value indicates that the exclusive SE is not currently accessed in the terminal, and the first value indicates that the exclusive SE is currently accessed in the terminal.
- a Flag flag is added to the DH, and the initial value is 0, 0 means false (the terminal does not currently have access to the exclusive SE), and 1 means true (the terminal has currently accessed the exclusive SE).
- the SE identifier is the first value
- the current routing table is obtained.
- the SE identifier is the second value, no configuration processing is necessary.
- the DH of the terminal device determines whether the current SE identifier is the second value, because whether the exclusive SE in the terminal has affected the routing configuration when the SE is removed. By distinguishing, the routing table can be correctly configured.
- the DH of the terminal device does not need to reset the routing table every time the SE is removed, which greatly saves system overhead.
- the current routing table needs to be emptied only to the routing entry of the exclusive SE. Therefore, when the exclusive SE is removed, the routing entry of the non-exclusive SE that was previously terminated needs to be rewritten to the routing. table.
- the route table of the non-exclusive SE is directly written without clearing the routing table, and only the routing item of the non-exclusive SE is deleted.
- the terminal cannot recognize whether the exclusive SE is currently accessed, it cannot be determined whether the current routing table is a routing item including only the exclusive SE or a routing item including each non-exclusive SE. Therefore, each time an SE is removed, the terminal will use the routing table. Clearing and rewriting the routing entries of each non-exclusive SE leads to a large overhead of the terminal system.
- the DH sends the RF_GET_LISTEN_MODE_ROUTING_CMD to the NFCC after determining that the SE state identifier is the first value, and obtains the current routing table RT01. Or DH itself backs up the routing table that was last configured to NFCC. RT0
- step 204 If the accessed security unit SE is not an exclusive SE, proceed to step 204; if the newly accessed security unit SE is an exclusive SE, proceed to step 205.
- the DH of the terminal device it is determined by the DH of the terminal device whether the newly accessed security unit SE is an exclusive SE. 204. Set the SE identifier to a first value, add a routing entry corresponding to the newly accessed SE in the current routing table, and construct a routing table. When the default routing entry is supported, determine whether the re-assignment needs to be re-specified.
- the default route target SE is described, and the constructed routing table may or may not include a routing entry corresponding to the default route target SE.
- the DH of the terminal device sets the SE identifier to the first value. On the basis of the content of the obtained routing table RT01, the legal routing entry corresponding to the newly accessed SE is added to form a new routing table RT02. If the terminal device's NFCC supports setting a default route entry, it is determined whether a new default route target needs to be reassigned. RT02 may or may not contain a routing entry corresponding to the default route destination (the default routing settings are supported on the terminal device).
- DH sends RF_SET_LISTEN_MODE_ROUTING_CMD to NFCC, and configures routing table RT02 to NFCC. If NFCC supports setting the default route target and updates the default route target, it also specifies a new default route target. DH sends NFCEE_MODE_SET_CMD to the NFCC to deactivate the non-exclusive SE of all active states except HCE, and activates the exclusive SE. It should be noted that the foregoing DH configuration routing table and the deactivation/activation of the SE are in no particular order, and the embodiment of the present invention does not limit this.
- step 206 is performed. If the host card emulator HCE exists in the terminal device, step 207 is performed.
- the constructed routing table may or may not include the exclusive access corresponding to the new access. Routing item.
- the interaction between the DH and the NFCC includes: 1.
- the DH sends the RF_SET_LISTEN_MODE_ROUTING_CMD to the NFCC, and configures the routing table to the NFCC; if the NFCC supports the setting of the default route target, the default route target is also set to the exclusive SE.
- DH When RH is received at DH, DH sets the Flag value to 1 and records the NFCEE ID of the exclusive SE: PT_SE_ID. DH sends NFCEE_MODE_SET_CMD to the NFCC to deactivate the non-exclusive SE of all active states except HCE, and activates the exclusive SE.
- routing entry does not include the routing entry whose destination is the HCE, go to step 208. If the routing entry does not contain the routing entry whose destination is the HCE, go to step 209.
- the DH detection system of the terminal device has a routing table that can be written, and the routing destination is the routing information of the HCE.
- the routing entry corresponding to the newly accessed exclusive SE is added to the current routing table to construct a routing table. If the default routing entry is supported, the constructed routing table may include or not. A routing entry corresponding to the exclusive accessing SE of the new access.
- RT03 may or may not contain the routing entry corresponding to the exclusive SE.
- the interaction between the DH and the NFCC includes: 1.
- the DH sends the RF_SET_LISTEN_MODE_ROUTING_CMD to the NFCC, and configures the routing table to the NFCC; if the NFCC supports the setting of the default route target, the default routing target is also set to the exclusive SE.
- DH When RSP is received in DH, DH sets Flag value to 1, and records exclusive SE. NFCEE ID: PT_SE_ID. DH sends NFCEE_MODE_SET_CMD to the NFCC to deactivate the non-exclusive SE of all active states except HCE, and activates the exclusive SE.
- the constructed routing table may or may not include the routing entry corresponding to the newly accessed exclusive SE.
- the NFCC if the NFCC does not support the setting of the default route, the NFCC deletes the routing entry corresponding to the HCE and the non-exclusive SE in the routing table, and writes the routing entry corresponding to the newly accessed SE, and the The routing item RT04 corresponding to the exclusive SE; if the NFCC supports the setting of the default route target, RT03 may or may not contain the corresponding routing item in the exclusive SE.
- DH sends RF_SET_LISTEN_MODE_ROUTING_CMD to NFCC to configure the above routing table to NFCC; if NFCC supports setting the default route destination, it also sets the default route target to exclusive SE.
- the Flag ie, the SE identifier described in the embodiment of the present invention
- the ID of the exclusive SE is recorded: PT_SE_ID.
- DH sends NFCEE_MODE_SET_CMD to the NFCC to deactivate the non-exclusive SE of all active states except HCE, and activates the exclusive SE. It should be noted that these two steps are in no particular order, and are not limited in the implementation of the present invention.
- the routing setting method and the terminal device provided by the embodiments of the present invention may terminate the operation of all non-exclusive SEs including the HCE by setting a routing table after the terminal accesses the exclusive SE.
- the method and the terminal device provided by the present invention can avoid the use of the HCE, thereby ensuring the normal operation of the newly accessed exclusive SE.
- Example 3 The embodiment of the present invention provides a route setting method, which is applied to a terminal device of the NFCC having the capability of deleting a routing table. As shown in FIG. 3, the method includes the following steps:
- the DH or NFCC of the terminal device can detect whether there is any
- DH obtains the NFCEE ID corresponding to the SE with the NFCEE Status value of 0x02 from the NFCEE_DISCOVER_NTF sent by the NFCC (that is, the NFCEE ID of the currently removed SE).
- step 303 is performed. If the SE identifier is not the second value, then step 304 is performed.
- Delete the routing entry corresponding to the currently removed SE in the current routing table and determine whether the currently removed SE is the default routing target SE when the default routing entry is supported, and if yes, re Specify an SE as the default route target SE.
- the NFCC deletes the routing entry corresponding to the SE. If the NFCC supports setting the default route entry, the DH determines whether the removed SE is the current default route entry SE, and if so, reassigns a SE as the default route entry target SE and configures it to the NFCC.
- DH determines whether the NFCEE ID of the removed SE is equal to PT_SE_ID (the ID of the exclusive SE currently recorded in the terminal). Since usually only one exclusive SE can be guaranteed in the terminal, it can be judged whether the current SE is an exclusive SE by judging whether the NFCEE ID of the removed SE is equal to PT_SE_ID. If they are the same, it proves that the current removal SE is an exclusive SE.
- the DH detection system service registration of the terminal device determines whether there is an HCE. 306. Construct a routing table according to the routing entry corresponding to the SE in the connected state. Check whether the default routing entry is supported. If yes, re-specify an SE as the default routing target SE, and the configured routing table may or may not include The routing item corresponding to the default route target SE.
- DH simultaneously selects and sets a new default route target.
- the NFCC deletes the routing entries corresponding to the exclusive SE.
- DH sends the NFCEE_MODE_SET_CMD instruction to the NFCC to activate some/all non-exclusive SEs as needed.
- the DH sets the Flag value to 0 and sets the PT_SE_ID value to N/A (that is, the SE identifier is set to the first in the embodiment of the present invention. a value, and updating the ID of the exclusive SE currently recorded in the terminal to be invalid).
- step 307 Detect whether the routing entry with the target is the HCE is included in the current routing table. If yes, proceed to step 308. If not, proceed to step 309.
- the routing entry corresponding to the SE in the connected state and the routing entry corresponding to the HCE construct a routing table. Check whether the default routing entry is supported. If yes, re-specify an SE as the default routing target SE, and construct The routing table may or may not include a routing entry corresponding to the default route target SE.
- the SE identifier is set to the first value, and the ID of the exclusive SE currently recorded in the terminal is updated to be invalid.
- the DH constructs a routing table RT05 according to the routing information contained in the SE and the HCE in the connected state. If the NFCC supports the default route, then reselect one SE as the default route target SE, and RT05 can include/exclude its route.
- DH sends RF_SET_LISTEN_MODE_ROUTING_CMD to the NFCC, and configures the above routing table to the NFCC. If the NFCC supports the setting of the default route target, then the new default route target is set at the same time. DH sends NFCEE_MODE_SET_CMD to the NFCC to activate some/all non-exclusive SEs as required. After receiving the RSP with the feedback configuration succeeded, the DH sets the Flag value to 0 and sets the PT_SE_ID value to N/A (that is, the ID of the exclusive SE currently recorded by the terminal device is updated to be invalid according to the embodiment of the present invention) . 309. Detect whether the current routing table includes any routing entry corresponding to the non-exclusive SE.
- step 310 If yes, proceed to step 310; if not, proceed to step 308.
- Delete the route item corresponding to the currently excluded exclusive SE to construct a routing table detect whether to support setting a default routing item, and if so, re-designate an SE as the default route target SE, and construct a routing table.
- the routing entry corresponding to the default route target SE may or may not be included.
- DH simultaneously selects and sets a new default route target.
- the NFCC deletes the routing entries corresponding to the exclusive SE.
- DH sends the NFCEE_MODE_SET_CMD instruction to the NFCC to activate some/all non-exclusive SEs as needed.
- DH sets the Flag value to 0 and sets the PT_SE_ID value to N/A.
- the routing setting method provided by the embodiment of the present invention may terminate the operation of all non-exclusive S E including H C E by setting a routing table after the terminal accesses the exclusive SE.
- the method and the terminal device provided by the present invention can avoid the use of the HCE, thereby ensuring the normal operation of the newly accessed exclusive SE.
- the embodiment of the present invention provides a route setting method, which is applied to a terminal device that does not have the capability of deleting a routing table by the NFCC. As shown in FIG. 4, the method includes the following steps: 401. Set the SE identifier; The initial value of the identifier is the first value.
- Macro terminals include DH and NFCC, where NFCC may have the ability to delete routing items or may not delete routing items. In this embodiment, it is specified that the NFCC does not have the capability of deleting routing entries.
- the DH of the terminal device sets the SE identifier. Initially, there is no access to the exclusive SE in the terminal, and the status is indicated by the first value.
- the value of the SE identifier may be a first value or a second value, the first value indicating that the terminal is not currently connected to the exclusive
- the first value indicates that the exclusive SE is currently accessed in the terminal. Specifically, a flag is added to the DH, the initial value is 0, 0 is false (the terminal does not currently have an exclusive access SE), and 1 is true (the terminal has currently accessed the exclusive SE).
- the current routing table is obtained.
- the DH of the terminal device determines whether the current SE identifier is the second value, because whether the exclusive SE in the terminal has affected the routing configuration when the SE is removed. By distinguishing, the routing table can be correctly configured.
- the DH of the terminal device does not need to reset the routing table every time the SE is removed, which greatly saves system overhead.
- the current routing table needs to be emptied only to the routing entry of the exclusive SE. Therefore, when the exclusive SE is removed, the routing entry of the non-exclusive SE that was previously terminated needs to be rewritten to the routing. table.
- the route table of the non-exclusive SE is directly written without clearing the routing table, and only the routing item of the non-exclusive SE is deleted.
- the terminal cannot recognize whether the exclusive SE is currently accessed, it cannot be determined whether the current routing table is a routing item including only the exclusive SE or a routing item including each non-exclusive SE. Therefore, each time an SE is removed, the terminal will use the routing table. Clearing and rewriting the routing entries of each non-exclusive SE leads to a large overhead of the terminal system.
- the DH sends the RF_GET_LISTEN_MODE_ROUTING_CMD to the NFCC after determining that the SE state identifier is the first value, and obtains the current routing table RT01. Or DH itself backs up the routing table that was last configured to the NFCC.
- RT0 403 Detects whether the newly accessed security unit SE is an exclusive SE.
- step 404 is performed; if the newly accessed security unit SE is an exclusive SE, then step 405 is performed.
- the DH of the terminal device it is determined by the DH of the terminal device whether the newly accessed security unit SE is an exclusive SE.
- the SE identifier may or may not include a routing entry corresponding to the default route target SE.
- the DH of the terminal device sets the SE identifier to the first value.
- the legal routing entry corresponding to the new access SE is added to form a new routing table RT02. If the terminal device's NFCC supports setting a default route entry, it is determined whether it is necessary to re-specify the new default route target.
- RT02 may or may not contain a routing entry corresponding to the default route target (the default routing settings are supported on the terminal device).
- DH sends RF_SET_LISTEN_MODE_ROUTING_CMD to NFCC, and configures routing table RT02 to NFCC. If NFCC supports setting the default route target and updates the default route target, it also specifies a new default route target. DH sends NFCEE_MODE_SET_CMD to the NFCC to deactivate the non-exclusive SE of all active states except HCE, and activates the exclusive SE. It should be noted that the foregoing DH configuration routing table and the deactivation/activation of the SE are in no particular order, and the embodiment of the present invention does not limit this.
- step 406 If not, proceed to step 406; if yes, proceed to step 407.
- the DH of the terminal device constructs a new routing table, in which only the routing entries corresponding to the applications in the exclusive SE are configured, and the routing entries corresponding to the applications in other SEs and HCEs are not included.
- DH sends RF_SET_LISTEN_MODE_ROUTING_CMD to NFCC to configure the above routing table to NFCC; if NFCC supports setting the default route destination, it also sets the default route target to exclusive SE.
- RH receives RSP, DH sets the Flag value to 1 and records the NFCEE ID of the non-other SE: PT_SE_ID.
- DH sends NFCEE_MODE_SET_CMD to the NFCC to deactivate the non-exclusive SE of all active states except HCE, and activates the exclusive SE.
- the DH constructs a new routing table, where only the routing entries corresponding to the applications in the exclusive SE are configured, or no routing entries are included.
- DH sends RF_SET_LISTEN_MODE_ROUTING_CMD to NFCC to configure the above routing table to NFCC; if NFCC supports setting the default route destination, it also sets the default route target to exclusive SE.
- RH receives RSP, DH sets the Flag value to 1 and records the NFCEE ID of the non-other SE: PT_SE_ID.
- DH sends NFCEE_MODE_SET_CMD to the NFCC to deactivate the non-exclusive SE of all active states except HCE, and activates the exclusive SE.
- the routing setting method and the terminal device provided by the embodiments of the present invention may terminate the operation of all non-exclusive SEs including the HCE by setting a routing table after the terminal accesses the exclusive SE.
- the method and the terminal device provided by the present invention can avoid the use of the HCE, thereby ensuring the normal operation of the newly accessed exclusive SE.
- the embodiment of the present invention provides a route setting method, which is applied to a terminal device that does not have the capability of deleting a routing table by the NFCC. As shown in FIG. 5, the method includes the following steps:
- the DH or NFCC of the terminal device detects that the SE is removed, the DH obtains the ID corresponding to the SE with the NFCEE Status value of 0x02 from the NFCEE_DISCOVER_NTF sent by the NFCC (that is, the NFCEE ID of the currently removed SE).
- step 503 If not, proceed to step 503; if yes, proceed to step 504.
- the DH of the terminal device determines whether the SE's NFCEE ID is equal to PT_SE_ID.
- the DH deletes the routing entry corresponding to the SE in the routing table, constructs a new routing table, and configures the routing table to the NFCC; If the NFCC supports the default route SE setting, it is determined whether the default route SE needs to be reset, and the new routing table may or may not contain the routing entry corresponding to the default route SE.
- step 507 If yes, go to step 507; if not, go to step 506.
- the DH constructs a routing table according to the routing information included in the SE and the HCE still in the connected state, including the routing information corresponding to the SE and the HCE in the connected state.
- DH sends RF_SET_LISTEN_MODE_ROUTING_CMD to the NFCC to configure the constructed routing table to the NFCC. If the NFCC supports the setting of the default route destination, an additional default destination is set. DH sends NFCEE_MODE_SET_CMD to the NFCC to activate some/all non-exclusive SEs as required.
- Re-designating an SE as the default route target SE, and the constructed routing table may or may not include a routing entry corresponding to the default route target SE.
- DH sends NFCEE_MODE_SET_CMD to the NFCC to activate some/all non-exclusive SEs as needed.
- DH After receiving the RSP with successful feedback configuration, DH sets the Flag value to 0 and sets the PT_SE_ID value to N/A.
- the routing setting method provided by the embodiment of the present invention may terminate the operation of all non-exclusive SEs including the HCE by setting a routing table after the terminal accesses the exclusive SE.
- the method and the terminal device provided by the present invention can avoid using the HCE, thereby ensuring the exclusive access of the new access.
- the embodiment of the present invention provides a terminal device.
- the terminal device includes: a detecting unit 601, a building unit 602, and a setting unit 603.
- the detecting unit 601 is configured to detect whether the newly accessed security unit SE is an exclusive SE.
- the detecting unit 601 is further configured to: after detecting that the newly accessed SE is an exclusive SE, detecting whether to support setting a default routing item .
- the construction unit 602 is configured to construct a routing table including only the routing items corresponding to the exclusive SE after the detecting unit 601 detects that the setting of the default routing item is not supported.
- the setting unit 603 is configured to: after the detecting unit 601 detects that the setting default routing item is supported, set the newly accessed SE as a default routing target SE, and the constructed routing table may or may not include an exclusive SE corresponding to the SE. Routing item.
- the setting unit 603 is further configured to: if the newly accessed SE is not an exclusive SE, set the SE identifier to a first value; if the newly accessed SE is an exclusive SE, then the SE identifier The second value is set and the ID of the newly accessed SE is recorded; the first value indicates that the exclusive SE is not currently accessed in the terminal, and the second value indicates that the exclusive SE is currently accessed in the terminal.
- the setting unit 603 is further configured to: set the SE identifier; an initial value of the SE identifier is the first value.
- the terminal device further includes: a determining unit, configured to determine whether the SE identifier is the first value.
- an obtaining unit configured to acquire a current routing table if the determining unit determines that the SE identifier is the first value.
- the constructing unit 602 is further configured to: after the detecting unit 601 detects that the newly accessed SE is not an exclusive SE, add a routing item corresponding to the newly accessed SE in the current routing table, and construct Routing table.
- the determining unit is further configured to: when the detecting unit 601 detects that the default routing item is supported, determine whether the default routing target SE needs to be re-specified, and the constructed routing table may or may not include the default routing target. SE corresponding route Item.
- the detecting unit 601 is further configured to detect whether the host card emulator HCE exists in the terminal device.
- the constructing unit 602 is further configured to: if the detecting unit 601 detects that the HCE does not exist in the terminal device, add an exclusive access of the new access to the current routing table when the default routing entry is not supported.
- the routing entry corresponding to the SE constructs a routing table. If the default routing entry is supported, the constructed routing table may or may not include the routing entry corresponding to the newly accessed exclusive SE.
- the detecting unit 601 is further configured to: if it is detected that the HCE exists in the terminal device, detect whether a routing entry whose target is the HCE is included in the routing table;
- the constructing unit 602 is further configured to: if the detecting unit 601 detects that the routing entry does not include a routing entry that is the HCE, add the default routing entry in the current routing table when the default routing entry is not supported.
- the routing entry corresponding to the newly-accessed exclusive SE constructs a routing table. If the default routing entry is supported, the constructed routing table may or may not include the routing entry corresponding to the newly accessed exclusive SE.
- the constructing unit 602 is further configured to: if the detecting unit 601 detects that the routing table includes a routing entry whose target is the HCE, delete the location when the detecting unit 601 detects that the default routing entry is not supported. a routing entry corresponding to the HCE and the non-exclusive SE in the routing table, and a routing entry corresponding to the newly-accessed SE, and a routing table including only the routing entries corresponding to the newly-accessed exclusive SE; If the default routing entry is set, the configured routing table may or may not include the routing entry corresponding to the newly accessed exclusive SE.
- the detecting unit 601 is further configured to detect whether an SE is removed.
- the obtaining unit is further configured to: after the detecting unit detects that the SE is removed, acquire an ID of the currently removed SE.
- the determining unit is further configured to determine whether the SE identifier is the second value.
- the determining unit is further configured to: if the SE identifier is the second value, It is determined whether the ID of the currently removed SE is the same as the ID of the exclusive SE recorded in the terminal.
- the constructing unit 602 is further configured to: if the determining unit determines that the ID of the currently removed SE is the same as the ID of the exclusive SE recorded in the terminal, the routing item corresponding to the SE in the connected state, The routing information included in the HCE is used to construct a routing table.
- the detecting unit 601 is further configured to detect whether a default routing entry is supported.
- the constructing unit 602 is further configured to: if the detecting unit 601 detects a setting default routing entry, construct a routing table that includes or does not include a routing entry corresponding to the default routing target SE.
- the setting unit 603 is further configured to: after the detecting unit 601 detects that the setting default routing item is supported, re-designate an SE as the default routing target SE.
- the obtaining unit is further configured to obtain a configuration success message.
- the setting unit 603 is further configured to: set the SE identifier to the first value, and update the ID of the exclusive SE currently recorded in the terminal to be invalid.
- the constructing unit 602 is further configured to: if the determining unit determines that the SE identifier is not the second value, delete a routing entry corresponding to the currently removed SE in the current routing table.
- the determining unit is further configured to determine, when the setting of the default routing item is supported, whether the currently removed SE is the default routing target SE.
- the determining unit is further configured to determine, when determining to support setting a default routing item, whether the currently removed SE is the default routing target SE.
- the setting unit 603 is further configured to: after the determining unit determines that the currently removed SE is the default routing target SE, re-designate an SE as the default routing target SE.
- the detecting unit 601 is further configured to detect whether the HCE exists in the terminal device.
- the building unit 602 is further configured to construct a routing table according to a routing item corresponding to the SE in the connected state.
- the detecting unit 601 is further configured to detect whether a default routing entry is supported.
- the setting unit 603 is further configured to: after detecting the setting of the default routing item, re-designating an SE as the default routing target SE, and the configured routing table may or may not include the routing item corresponding to the default routing target SE.
- the obtaining unit is further configured to obtain a configuration success message.
- the setting unit 603 is further configured to: set the SE identifier to the first value, and update the ID of the exclusive SE currently recorded in the terminal to be invalid.
- the detecting unit 601 is further configured to: if the HCE exists in the terminal device, detect whether the current routing table includes a routing entry whose target is the HCE.
- the constructing unit 602 is further configured to: after the detecting unit 601 detects that the current routing table includes a routing entry whose target is the HCE, according to the routing entry corresponding to the SE in the connected state, and the route corresponding to the HCE Item build routing table.
- the detecting unit 601 is further configured to detect whether a default routing entry is supported.
- the setting unit 603 is further configured to: if the detecting unit 601 detects that the default routing entry is supported, re-designate an SE as the default routing target SE, and the constructed routing table may or may not include the default routing target.
- the routing entry corresponding to SE is further configured to: if the detecting unit 601 detects that the default routing entry is supported, re-designate an SE as the default routing target SE, and the constructed routing table may or may not include the default routing target.
- the obtaining unit is further configured to: obtain a configuration success message
- the setting unit 603 is further configured to: set the SE identifier to the first value, and update the ID of the exclusive SE currently recorded in the terminal to be invalid.
- the detecting unit 601 is further configured to: after detecting that the current routing table does not include a routing entry that is the HCE, whether the current routing table includes any routing entry corresponding to the non-exclusive SE.
- the constructing unit 602 is further configured to: after the detecting unit 601 detects that the current routing table includes a routing item corresponding to any non-exclusive SE, delete the routing item corresponding to the currently excluded exclusive SE to construct a route. table.
- the detecting unit 601 is further configured to detect whether a default routing entry is supported.
- the setting unit 603 is further configured to: if the detecting unit 601 detects that the default routing item is supported, re-designate an SE as the default routing target SE, and construct The created routing table may or may not contain a routing entry corresponding to the default route target SE.
- the obtaining unit is further configured to obtain a configuration success message.
- the setting unit 603 is further configured to: set the SE identifier to the first value, and update the ID of the exclusive SE currently recorded in the terminal to be invalid.
- the constructing unit 602 is further configured to: if the current routing table does not include any routing item corresponding to the non-exclusive SE, the routing item corresponding to the SE in the connected state, and the routing information included in the HCE, construct a route table.
- the detecting unit 601 is further configured to detect whether a default routing entry is supported.
- the setting unit 603 is further configured to: if the detecting unit 601 detects that the default routing entry is supported, re-designate an SE as the default routing target SE, and the constructed routing table may or may not include the default routing target.
- the routing entry corresponding to SE is further configured to: if the detecting unit 601 detects that the default routing entry is supported, re-designate an SE as the default routing target SE, and the constructed routing table may or may not include the default routing target.
- the obtaining unit is further configured to obtain a configuration success message.
- the setting unit 603 is further configured to: set the SE identifier to the first value, and update the ID of the exclusive SE currently recorded in the terminal to be invalid.
- the terminal device provided by the embodiment of the present invention can terminate the operation of all non-exclusive SEs including the HCE by setting a routing table after the terminal accesses the exclusive SE. Compared with the prior art, the method and the terminal device provided by the present invention can avoid the use of the HCE, thereby ensuring the normal operation of the newly accessed exclusive SE.
- the embodiment of the present invention provides a terminal device.
- the terminal device includes: DH (Device Host) 701.
- the terminal device further includes an NFCC (Near Field Communication Manager) 702, an SE interface (Secure Unit Interface) 703, and a memory 704.
- a routing table is stored in the memory.
- DH701 used to detect whether the newly accessed security unit SE is an exclusive SE.
- the DH 701 is further configured to: after detecting that the newly accessed SE is an exclusive SE, detecting whether to support setting a default routing item.
- the DH 701 is further configured to: after detecting that the default routing entry is not supported, construct a routing table that only includes routing entries corresponding to the exclusive SE.
- the DH701 is configured to: after detecting that the default routing entry is supported, set the newly accessed SE as a default routing target SE, and the constructed routing table may or may not include a routing entry corresponding to the exclusive SE.
- the DH 701 is further configured to: if the newly accessed SE is not an exclusive SE, set the SE identifier to a first value; if the newly accessed SE is an exclusive SE, set the SE identifier The second value is used to record the ID of the newly accessed SE; the first value indicates that the exclusive SE is not currently accessed in the terminal, and the second value indicates that the exclusive SE is currently accessed in the terminal.
- the DH 701 is further configured to: set the SE identifier; an initial value of the SE identifier is the first value.
- the B' is configured to obtain a current routing table if the SE identifier is determined to be the first value.
- the DH 701 is further configured to: after detecting that the newly accessed SE is not an exclusive SE, add a routing entry corresponding to the newly accessed SE in the current routing table, and construct a routing table.
- the DH701 is further configured to: when it is detected that the default routing entry is supported, determine whether the default routing target SE needs to be re-specified, and the configured routing table may or may not include the routing entry corresponding to the default routing target SE.
- the DH 701 is further configured to detect whether the host card emulator HCE exists in the terminal device.
- the DH 701 is further configured to: when detecting that the HCE does not exist in the terminal device, add a routing entry corresponding to the newly accessed exclusive SE in the current routing table when the default routing entry is not supported. If the default routing entry is supported, the configured routing table may or may not include the routing entry corresponding to the newly accessed exclusive SE.
- the DH 701 is further configured to: if detecting the presence of the HCE in the terminal device, And detecting, in the routing table, whether the routing entry whose target is the HCE is included;
- the DH 701 is further configured to: if it is detected that the routing entry does not include a routing entry that is the HCE, add the exclusive access of the new access to the current routing table when the default routing entry is not supported.
- the routing entry corresponding to the SE constructs a routing table. If the default routing entry is supported, the constructed routing table may or may not include the routing entry corresponding to the newly accessed exclusive SE.
- the DH 701 is further configured to: if it is detected that the routing entry includes a routing entry whose target is the HCE, delete the HCE and the non-exclusive SE corresponding to the routing table when detecting that the default routing entry is not supported.
- the routing entry is written to the routing entry corresponding to the newly accessed SE, and a routing table including only the routing entries corresponding to the newly-accessed exclusive SE is constructed; if the default routing entry is supported, the constructed routing table may be configured.
- a routing entry corresponding to the exclusive accessing SE of the new access is included or not included.
- the DH701 is further configured to detect whether an SE is removed.
- the DH 701 is further configured to: after detecting that the SE is removed, obtain an ID of the currently removed SE.
- the DH 701 is further configured to determine whether the SE identifier is the second value.
- the DH 701 is further configured to determine, if the SE identifier is the second value, whether the ID of the currently removed SE is the same as the ID of the exclusive SE recorded in the terminal.
- the DH 701 is further configured to: if the determining unit determines that the ID of the currently removed SE is the same as the ID of the exclusive SE recorded in the terminal, the routing entry corresponding to the SE in the connected state, the HCE includes Routing information, build a routing table.
- the DH701 is further configured to detect whether a default routing entry is supported.
- the DH701 is further configured to: if the detection supports setting a default routing entry, construct a routing table that includes or does not include a routing entry corresponding to the default routing target SE.
- the DH701 is further configured to: after detecting the support setting default routing entry, re-designating an SE as the default routing target SE.
- the DH701 is further configured to obtain a configuration success message.
- the DH 701 is further configured to: set the SE identifier to the first value, and The ID of the exclusive SE currently recorded in the terminal is updated to be invalid.
- the NFCC 702 is configured to: if it is determined that the SE identifier is not the second value, delete a routing entry corresponding to the currently removed SE in the current routing table.
- the DH 701 is further configured to: if it is determined that the SE identifier is not the second value, and the NFCC 702 of the terminal does not have the capability of deleting a route, delete the route corresponding to the currently removed SE in the current routing table. item.
- the DH701 is further configured to determine, when the setting of the default routing item is supported, whether the currently removed SE is the default routing target SE.
- the DH701 is further configured to determine, when determining that the default routing entry is supported, whether the currently removed SE is the default routing target SE.
- the DH 701 is further configured to: after determining that the currently removed SE is the default route target SE, re-designate an SE as the default route target SE.
- the DH 701 is further configured to detect whether the HCE exists in the terminal device.
- the DH701 is further configured to construct a routing table by using a routing item corresponding to the SE in the connected state.
- the DH701 is further configured to detect whether a default routing entry is supported.
- the DH701 is further configured to: after detecting the setting of the default routing entry, re-designating an SE as the default routing target SE, and the constructed routing table may or may not include the routing entry corresponding to the default routing target SE.
- the DH701 is further configured to obtain a configuration success message.
- the DH 701 is further configured to: set the SE identifier to the first value, and update an ID of an exclusive SE currently recorded in the terminal to be invalid.
- the DH 701 is further configured to: if the HCE exists in the terminal device, detect whether a routing entry whose target is the HCE is included in the current routing table.
- the DH 701 is further configured to: after detecting that the current routing table includes a routing entry that is the HCE, construct a routing table according to the routing entry corresponding to the SE in the connected state and the routing entry corresponding to the HCE.
- the DH 701 is further configured to: detect whether a default routing entry is supported. The DH 701 is further configured to: if the detection supports setting a default routing entry, re-designating an SE as the default routing target SE, and the constructed routing table may or may not include a routing entry corresponding to the default routing target SE.
- the DH701 is further configured to: obtain a configuration success message
- the DH 701 is further configured to: set the SE identifier to the first value, and update an ID of an exclusive SE currently recorded in the terminal to be invalid.
- the DH 701 is further configured to: after detecting that the current routing table does not include the routing entry that is the HCE, check whether the current routing table includes any routing entry corresponding to the non-exclusive SE.
- the DH 701 is further configured to: after the detecting unit 601 detects that the current routing table includes a routing item corresponding to any non-exclusive SE, delete the routing item construction routing table corresponding to the currently deleted exclusive SE.
- the DH701 is further configured to detect whether a default routing entry is supported.
- the DH 701 is further configured to: if the detecting unit 601 detects that the default routing entry is supported, re-designate an SE as the default routing target SE, and the constructed routing table may or may not include the default routing target SE corresponding. Routing item.
- the DH701 is further configured to obtain a configuration success message.
- the DH 701 is further configured to: set the SE identifier to the first value, and update an ID of an exclusive SE currently recorded in the terminal to be invalid.
- the DH 701 is further configured to: if the current routing table does not include any routing item corresponding to the non-exclusive SE, the routing entry corresponding to the SE in the connected state, and the routing information included in the HCE, construct a routing table.
- the DH701 is further configured to detect whether a default routing entry is supported.
- the DH 701 is further configured to: if the detection supports setting a default routing entry, re-designating an SE as the default routing target SE, and the constructed routing table may or may not include a routing entry corresponding to the default routing target SE.
- the DH701 is further configured to obtain a configuration success message.
- the DH 701 is further configured to: set the SE identifier to the first value, and update an ID of an exclusive SE currently recorded in the terminal to be invalid.
- the terminal device provided by the embodiment of the present invention can terminate the operation of all non-exclusive SEs including the HCE by setting a routing table after the terminal accesses the exclusive SE. Compared with the prior art, the method and the terminal device provided by the present invention can avoid using the HCE, thereby ensuring the normal operation of the newly accessed exclusive SE.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Mobile Radio Communication Systems (AREA)
- Telephone Function (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Description
Claims
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US15/035,525 US10142232B2 (en) | 2014-06-03 | 2014-06-03 | Route setting method and terminal device |
EP14893768.3A EP3013087B1 (en) | 2014-06-03 | 2014-06-03 | Route setting method and terminal device |
JP2016570270A JP6292595B2 (ja) | 2014-06-03 | 2014-06-03 | ルート設定方法及び端末デバイス |
PCT/CN2014/079103 WO2015184591A1 (zh) | 2014-06-03 | 2014-06-03 | 一种路由设置方法及终端设备 |
CN201480003374.7A CN105453622B (zh) | 2014-06-03 | 2014-06-03 | 一种路由设置方法及终端设备 |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2014/079103 WO2015184591A1 (zh) | 2014-06-03 | 2014-06-03 | 一种路由设置方法及终端设备 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2015184591A1 true WO2015184591A1 (zh) | 2015-12-10 |
Family
ID=54765932
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2014/079103 WO2015184591A1 (zh) | 2014-06-03 | 2014-06-03 | 一种路由设置方法及终端设备 |
Country Status (5)
Country | Link |
---|---|
US (1) | US10142232B2 (zh) |
EP (1) | EP3013087B1 (zh) |
JP (1) | JP6292595B2 (zh) |
CN (1) | CN105453622B (zh) |
WO (1) | WO2015184591A1 (zh) |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105659507B (zh) | 2014-09-30 | 2019-02-26 | 华为技术有限公司 | 路由的方法、近场通信控制器、主控制器和终端 |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN103222291A (zh) * | 2010-11-17 | 2013-07-24 | 捷讯研究有限公司 | 用于支持多个nfc执行环境nfcee的nfc控制器的应用路由配置 |
CN103765791A (zh) * | 2013-01-24 | 2014-04-30 | 华为终端有限公司 | 近场通信射频发现控制方法、装置和终端设备 |
Family Cites Families (29)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
FR2904741B1 (fr) * | 2006-08-04 | 2009-10-02 | Inside Contactless Sa | Procede de routage de donnees d'application entrantes dans un chipset nfc, par identification de l'application. |
JP4462341B2 (ja) | 2007-12-18 | 2010-05-12 | ソニー株式会社 | 情報処理装置および方法、並びにプログラム |
ES2386164T3 (es) * | 2008-03-27 | 2012-08-10 | Motorola Mobility, Inc. | Método y aparato para la selección automática de una aplicación de comunicación de campo cercano en un dispositivo electrónico |
US9715681B2 (en) * | 2009-04-28 | 2017-07-25 | Visa International Service Association | Verification of portable consumer devices |
US9038886B2 (en) * | 2009-05-15 | 2015-05-26 | Visa International Service Association | Verification of portable consumer devices |
JP2012039257A (ja) | 2010-08-04 | 2012-02-23 | Sony Corp | 携帯端末、情報処理方法及びコンピュータプログラム |
US20120239560A1 (en) * | 2011-03-04 | 2012-09-20 | Pourfallah Stacy S | Healthcare payment collection portal apparatuses, methods and systems |
FR2985063B1 (fr) | 2011-12-21 | 2014-07-04 | Morpho | Procede de routage au sein d'un terminal mobile emulant une carte de paiement sans contact |
US8923763B2 (en) * | 2012-02-28 | 2014-12-30 | Qualcomm Incorporated | Methods and apparatuses for reducing the nonvolatile memory used to support application identifier routing in an NFC controller |
US9495524B2 (en) | 2012-10-01 | 2016-11-15 | Nxp B.V. | Secure user authentication using a master secure element |
US20160019536A1 (en) * | 2012-10-17 | 2016-01-21 | Royal Bank Of Canada | Secure processing of data |
CA2830260C (en) * | 2012-10-17 | 2021-10-12 | Royal Bank Of Canada | Virtualization and secure processing of data |
US9911118B2 (en) * | 2012-11-21 | 2018-03-06 | Visa International Service Association | Device pairing via trusted intermediary |
CA2874729C (en) * | 2013-01-25 | 2021-01-05 | Jvl Ventures, Llc | Systems, methods, and computer program products for managing data re-installation |
AU2014266860B2 (en) * | 2013-05-15 | 2017-07-13 | Visa International Service Association | Methods and systems for provisioning payment credentials |
WO2014189748A1 (en) * | 2013-05-21 | 2014-11-27 | Jvl Ventures, Llc | Systems, methods and computer program products for managing disabling of services |
US10108924B2 (en) * | 2013-09-26 | 2018-10-23 | At&T Mobility Ii Llc | Methods and apparatus to emulate a toy |
EP3078156A4 (en) * | 2013-10-11 | 2017-07-12 | Visa International Service Association | Network token system |
FR3012236B1 (fr) * | 2013-10-17 | 2017-04-14 | Proton World Int Nv | Procede de routage nfc |
SG11201604906QA (en) * | 2013-12-19 | 2016-07-28 | Visa Int Service Ass | Cloud-based transactions methods and systems |
WO2015116309A1 (en) * | 2014-02-03 | 2015-08-06 | Jvl Ventures, Llc | Systems, methods, and computer program products for providing data use options |
US20150262164A1 (en) * | 2014-03-13 | 2015-09-17 | Google Inc. | Cloud-based secure storage |
ES2545974B1 (es) * | 2014-03-17 | 2016-04-27 | Bankinter, S.A. | Sistema de protección automático y personalizado para aplicaciones móviles |
FR3018972B1 (fr) * | 2014-03-18 | 2016-04-15 | Proton World Int Nv | Secure nfc routing |
WO2015147413A1 (en) * | 2014-03-27 | 2015-10-01 | Lg Electronics Inc. | Mobile terminal and method for controlling the same |
KR20150123551A (ko) * | 2014-04-25 | 2015-11-04 | 모지도코화이어코리아 유한회사 | Hce를 활용한 모바일 카드 서비스 방법 및 이를 적용한 모바일 단말 |
US9767265B2 (en) * | 2014-05-06 | 2017-09-19 | Anchor Id, Inc. | Authentication with parental control functionality |
US10380588B2 (en) * | 2014-05-13 | 2019-08-13 | Mastercard International Incorporated | Passive cardholder verification method in mobile device |
WO2015179637A1 (en) * | 2014-05-21 | 2015-11-26 | Visa International Service Association | Offline authentication |
-
2014
- 2014-06-03 EP EP14893768.3A patent/EP3013087B1/en active Active
- 2014-06-03 CN CN201480003374.7A patent/CN105453622B/zh active Active
- 2014-06-03 WO PCT/CN2014/079103 patent/WO2015184591A1/zh active Application Filing
- 2014-06-03 JP JP2016570270A patent/JP6292595B2/ja active Active
- 2014-06-03 US US15/035,525 patent/US10142232B2/en active Active
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN103222291A (zh) * | 2010-11-17 | 2013-07-24 | 捷讯研究有限公司 | 用于支持多个nfc执行环境nfcee的nfc控制器的应用路由配置 |
CN103765791A (zh) * | 2013-01-24 | 2014-04-30 | 华为终端有限公司 | 近场通信射频发现控制方法、装置和终端设备 |
Non-Patent Citations (1)
Title |
---|
See also references of EP3013087A4 * |
Also Published As
Publication number | Publication date |
---|---|
JP6292595B2 (ja) | 2018-03-14 |
EP3013087A4 (en) | 2016-08-31 |
JP2017531331A (ja) | 2017-10-19 |
EP3013087A1 (en) | 2016-04-27 |
CN105453622B (zh) | 2019-05-28 |
US10142232B2 (en) | 2018-11-27 |
CN105453622A (zh) | 2016-03-30 |
EP3013087B1 (en) | 2017-09-06 |
US20160301606A1 (en) | 2016-10-13 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20220197575A1 (en) | Communication system, communication device, and non-transitory computer-readable storage medium storing instructions for information processing device | |
US11115081B2 (en) | Routing method for multiple security elements, NFC controller and NFC device | |
US10440557B2 (en) | Electronic device for providing service using secure element and method thereof | |
US9703995B2 (en) | Portable terminal, imaging apparatus, communication system, communication method of portable terminal, communication method of imaging apparatus, and computer readable storage device | |
KR102474437B1 (ko) | 임베디드 가입자 식별 모듈에서의 프로파일의 설치 | |
JP6923582B2 (ja) | 情報処理装置、情報処理方法、およびプログラム | |
US11800575B2 (en) | Just in time connection configuration stored in SIM profile | |
WO2023160203A1 (zh) | 交换机配置管理方法、装置、电子设备及存储介质 | |
JP6613653B2 (ja) | 中継装置、通信制御方法、及び通信制御システム | |
US9720755B2 (en) | Information processing device | |
US9380626B2 (en) | Communication apparatus, information processing apparatus, and control method for the same | |
US10122417B2 (en) | Communicating via near field communications | |
WO2015184591A1 (zh) | 一种路由设置方法及终端设备 | |
WO2016172948A1 (zh) | 路由信息配置方法及装置 | |
JP6306992B2 (ja) | アカウント管理方法、アカウント管理サーバ、及びアカウント管理システム | |
JP6372134B2 (ja) | 配信装置、配信方法および配信プログラム | |
CN106507434B (zh) | 一种数据处理方法及装置 | |
CN106462845B (zh) | 一种非接触前端的配置方法及终端 | |
US11494218B2 (en) | Server and method for controlling packet transmission | |
KR102362699B1 (ko) | 복수의 스토리지 장치를 이용한 파일 관리 서비스의 제공 방법 및 그 장치 | |
KR20200089491A (ko) | 공유된 디지털 키를 관리하기 위한 장치 및 방법 | |
US11588861B2 (en) | Electronic device and operating method for registering IP multimedia subsystem | |
EP4184317A1 (en) | Upgradable electronic device, server for upgrdading electronic device, and method for upgrading electronic device | |
JPWO2020170296A1 (ja) | 情報処理装置および情報処理装置と通信端末との自動接続方法 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 201480003374.7 Country of ref document: CN |
|
REEP | Request for entry into the european phase |
Ref document number: 2014893768 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2014893768 Country of ref document: EP |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 14893768 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 15035525 Country of ref document: US |
|
ENP | Entry into the national phase |
Ref document number: 2016570270 Country of ref document: JP Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |