WO2022176445A1 - 情報処理装置、及び、プログラム - Google Patents
情報処理装置、及び、プログラム Download PDFInfo
- Publication number
- WO2022176445A1 WO2022176445A1 PCT/JP2022/000816 JP2022000816W WO2022176445A1 WO 2022176445 A1 WO2022176445 A1 WO 2022176445A1 JP 2022000816 W JP2022000816 W JP 2022000816W WO 2022176445 A1 WO2022176445 A1 WO 2022176445A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- service
- allocated
- area
- state
- information processing
- Prior art date
Links
- 230000010365 information processing Effects 0.000 title claims abstract description 75
- 238000000034 method Methods 0.000 claims abstract description 103
- 238000012545 processing Methods 0.000 claims description 41
- 238000004891 communication Methods 0.000 claims description 19
- 238000005516 engineering process Methods 0.000 abstract description 23
- 238000010586 diagram Methods 0.000 description 31
- 230000006870 function Effects 0.000 description 16
- 230000004044 response Effects 0.000 description 16
- 230000005540 biological transmission Effects 0.000 description 9
- 230000000694 effects Effects 0.000 description 6
- 238000007726 management method Methods 0.000 description 5
- 238000013459 approach Methods 0.000 description 2
- 238000009434 installation Methods 0.000 description 2
- 238000004364 calculation method Methods 0.000 description 1
- 239000000969 carrier Substances 0.000 description 1
- 238000012790 confirmation Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000011900 installation process Methods 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 230000000717 retained effect Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06K—GRAPHICAL DATA READING; PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS
- G06K19/00—Record carriers for use with machines and with at least a part designed to carry digital markings
- G06K19/06—Record carriers for use with machines and with at least a part designed to carry digital markings characterised by the kind of the digital marking, e.g. shape, nature, code
- G06K19/067—Record carriers with conductive marks, printed circuits or semiconductor circuit elements, e.g. credit or identity cards also with resonating or responding marks without active components
- G06K19/07—Record carriers with conductive marks, printed circuits or semiconductor circuit elements, e.g. credit or identity cards also with resonating or responding marks without active components with integrated circuit chips
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06K—GRAPHICAL DATA READING; PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS
- G06K19/00—Record carriers for use with machines and with at least a part designed to carry digital markings
- G06K19/06—Record carriers for use with machines and with at least a part designed to carry digital markings characterised by the kind of the digital marking, e.g. shape, nature, code
- G06K19/067—Record carriers with conductive marks, printed circuits or semiconductor circuit elements, e.g. credit or identity cards also with resonating or responding marks without active components
- G06K19/07—Record carriers with conductive marks, printed circuits or semiconductor circuit elements, e.g. credit or identity cards also with resonating or responding marks without active components with integrated circuit chips
- G06K19/073—Special arrangements for circuits, e.g. for protecting identification code in memory
Definitions
- the present technology relates to an information processing device and a program, and in particular, an information processing device capable of effectively using a memory area for storing execution data necessary for executing a service in an allocation area allocated for each service, and , about the program.
- Patent Document 1 describes a technology related to a multi-application IC chip that stores applications corresponding to multiple services.
- an allocation area allocated to a deleted service remains to store implementation data corresponding to a new service. may not be possible. In this case, the memory area cannot be used effectively.
- This technology has been developed in view of this situation, and enables effective use of memory areas for storing implementation data necessary for implementing services in allocation areas allocated for each service.
- the information processing device or program according to the first aspect of the present technology is an allocation area allocated for each service in a memory area in which implementation data necessary for implementing each of one or more services is stored, A service undetermined state in which no service is assigned to the assigned area remaining in a state in which at least part of the implementation data is deleted and in a state assigned to a predetermined service.
- An information processing device having a processing unit that performs a service issuing process of storing the implementation data corresponding to the new service in the service undetermined allocation area after performing the process of changing the allocation area, or It is a program for making a computer function as an information processing device.
- the information processing device stores implementation data necessary for implementing each of one or a plurality of services, among allocation areas allocated for each service in a memory area that stores the implementation data.
- the allocation area remaining in a state in which at least part of it has been deleted and has been allocated to a predetermined service is changed to an allocation area in a service undetermined state in which no service has been allocated.
- a command generation unit for transmitting a command for executing the service issuing process to a terminal device executing the service issuing process for storing the implementation data corresponding to the new service in the service undetermined allocation area. It is an information processing device having
- FIG. 1 is a block diagram showing a configuration example of an embodiment of an information processing system to which the present technology is applied;
- FIG. FIG. 10 is a diagram for explaining management by the TSM server of the SE of the non-contact IC chip of the information processing device;
- FIG. 4 is a diagram illustrating the logical configuration of the SE memory area of the contactless IC chip;
- FIG. 2 is a diagram for explaining a case where a service installed in a contactless IC chip is deleted by a GP-compatible TSM server in FIG. 1;
- FIG. 10 is a diagram for explaining a case where a GP-incompatible TSM server deletes a service installed in a contactless IC chip;
- FIG. 10 is a diagram showing an outline of service issuing processing performed by the TSM server of the present embodiment for an Applet instance in an empty personalized state; 2 is a diagram showing a configuration related to issuing a service to a contactless IC chip of an information processing device in the information processing system of FIG. 1;
- FIG. FIG. 10 is a diagram showing a service issuance procedure when a memory area for adding a new service remains in the SE of the contactless IC chip;
- FIG. 10 is a diagram showing a service issuance procedure when a memory area for adding a new service remains in the SE of the contactless IC chip;
- FIG. 10 is a diagram showing a service issuance procedure when a memory area for adding a new service remains in the SE of the contactless IC chip;
- FIG. 10 is a diagram showing a service issuance procedure when a memory area for adding a new service remains in the SE of the contactless IC chip;
- FIG. 10 is a diagram showing a service issuance procedure when a memory area
- FIG. 10 is a diagram showing a procedure for issuing a service to an Applet instance in an empty personalized state when there is no memory area left to add a new service to the SE of the contactless IC chip.
- FIG. 10 is a diagram showing a procedure for issuing a service to an Applet instance in an empty personalized state when there is no memory area left to add a new service to the SE of the contactless IC chip.
- FIG. 10 is a diagram showing a procedure for issuing a service to an Applet instance in an empty personalized state when there is no memory area left to add a new service to the SE of the contactless IC chip.
- FIG. 10 is a diagram showing a procedure for issuing a service to an Applet instance in an empty personalized state when there is no memory area left to add a new service to the SE of the contactless IC chip.
- FIG. 10 is a diagram showing a procedure for issuing a service to an Applet instance in an empty personalized state when there is no memory area left to add a new service to the SE of the contactless IC chip.
- FIG. 10 is a diagram showing a procedure for issuing a service to an Applet instance in an empty personalized state when there is no memory area left to add a new service to the SE of the contactless IC chip.
- FIG. 10 is a sequence diagram showing the procedure of service issuing processing in the information processing system;
- FIG. 10 is a sequence diagram showing the procedure of service issuing processing in the information processing system;
- FIG. 2 is a block diagram showing a configuration example of hardware of a computer that executes a series of processes by a program;
- FIG. 1 is a block diagram showing a configuration example of an embodiment of an information processing system to which the present technology is applied.
- an information processing system 1 which is an embodiment of an information processing system to which the present technology is applied, includes an information processing device 11, a TSM (Trusted Service Manager) server 12, a service provider server 13, and a reader/writer. It has a terminal 14 .
- TSM Trusted Service Manager
- the information processing device 11, TSM server 12, and service provider server 13 are communicably connected through a network such as a local area network, the Internet, or a mobile communication network.
- the information processing device 11 and the reader/writer terminal 14 are communicably connected by near field communication (NFC).
- NFC near field communication
- the information processing device 11 is a terminal device compatible with NFC, such as a smart phone or mobile phone.
- the information processing device 11 has a controller 31 , a contactless IC chip 32 and an RF (radio frequency) interface 33 .
- the controller 31 has the same configuration as the computer in FIG. Specifically, CPU (Central Processing Unit), non-volatile memory (e.g. flash memory) that stores various programs and data, RAM that temporarily stores data, communication circuit that connects to the network for communication, and contactless IC chip 32 and an I/O port for data transmission.
- CPU Central Processing Unit
- non-volatile memory e.g. flash memory
- RAM random access memory
- the contactless IC chip 32 has a CPU, RAM, ROM, non-volatile memory, I/O ports, and the like.
- the I/O port performs data transmission with the controller 31 and with the RF interface 33 .
- the nonvolatile memory stores the OS, various applications, and data used by them.
- the RF interface 33 receives and demodulates electromagnetic waves (modulated waves) from the reader/writer terminal 14 in the HF band (short wave band 13.56 MHz) with an antenna (not shown), and transmits data transmitted by the modulated waves. It is supplied to the non-contact IC chip 32 .
- the RF interface 33 modulates a carrier wave of 13.56 MHz according to data from the contactless IC chip 32 to generate a modulated wave, and transmits an HF band electromagnetic wave (modulated wave) from an antenna (not shown) to the reader/writer terminal 14. Send.
- the RF interface 33 complies with, for example, the NFC Forum specifications. That is, the RF interface 33 is based on the Type-A/B communication technology specified in the international standard ISO/IEC 14443 for non-contact IC cards and the international standard ISO/IEC 18092 (NFCIP-1) for the communication protocol. It performs modulation and demodulation compatible with FeliCa (registered trademark) communication technology, which is a Type-F communication technology that is a technology for contactless IC cards.
- FeliCa registered trademark
- NFC near field communication
- a portion of the RF interface 33 other than the antenna may be incorporated in the non-contact IC chip 32.
- the information processing device 11 is an NFC-compatible terminal device, and has, for example, a card emulation function, a card reader/writer function, and a peer-to-peer function.
- the card emulation function is a function that realizes the function of an IC card (electronic money card, credit card, etc.) with an information processing device that is a device different from the IC card.
- the card reader/writer function is a function that reads and writes data contained in an IC card.
- the peer-to-peer function is a function for performing NFC communication between NFC-compatible devices.
- the information processing device 11 is equipped with an analog front-end block (CLF: Contact-Less Frontend) and a secure element (SE: Secure Element) in addition to the controller 31 .
- CLF analog front-end block
- SE secure element
- the CLF and SE are constructed with a contactless IC chip 32 and an RF interface 33 .
- the CLF performs short-range wireless communication with the NFC-compatible device, and also performs data transmission between the NFC-compatible device and the SE, data transmission between the NFC-compatible device and the controller 31, and data transmission between the controller 31 and the SE. data transmission.
- the SE has a highly confidential memory area (non-volatile memory) and a calculation function (processor, etc.) specialized for encryption, and performs data storage, data encryption and decryption, etc.
- SE mounting methods include an embedded method, a SIM method, an SD card method, and the like.
- the embedded system is a system in which an SE is built into an IC chip built into a terminal.
- the SIM method is a method in which SE is implemented in a UICC (Universal Integrated Circuit Card: SIM card) provided by mobile carriers.
- the SD card method is a method in which the SE is mounted on an external medium such as an SD card. This embodiment exemplifies the case where the embedded method in which the SE is incorporated in the contactless IC chip 32 is adopted as the SE mounting method, but any other method may be used.
- the TSM server 12 is a server owned by an area management business that manages the SE memory area of the information processing device 11 .
- the TSM server 12 allocates an SE memory area to a service provider (SP: Service Provider) that provides services using the SE, and stores the SE memory area of an application (Applet) necessary for providing services. Perform SE management such as installation to.
- SP Service Provider
- the term "service” refers to services that can be provided by IC cards such as transportation tickets, electronic money, credit cards, student ID cards, membership cards, point cards, coupons, apartment keys, etc., or such services. Including what you provide (applications, etc.).
- the unit is the business operator that provides the service or the purpose of using the service. In other words, even if the services have the same content, if the service provider is different, they are treated as separate services.
- the service provider server 13 is a server owned by the SP.
- the service provider server 13 accesses (reads or writes data, etc.) the memory area of the SE assigned to the service it provides, and accepts a request to issue a new service from a user using an application. .
- the reader/writer terminal 14 is an NFC compatible device.
- the reader/writer terminal 14 is communicably connected to the information processing device 11 by short-range wireless communication (NFC) in the same way as when an NFC-compatible IC card approaches. accesses the memory area of the SE (reading and writing data in the memory area by commands, etc.).
- NFC short-range wireless communication
- FIG. 2 is a diagram explaining management by the TSM server of the SE of the contactless IC chip 32 of the information processing device 11.
- FIG. 2 is a diagram explaining management by the TSM server of the SE of the contactless IC chip 32 of the information processing device 11.
- the non-contact IC chip 32 of the information processing device 11 conforms to the technical specifications defined in GlobalPlatform card specification versions 2.1.1 and 2.2.
- GlobalPlatform (GP) is an industry standardization organization for multi-application smart card management systems.
- technical specifications formulated by GP are simply referred to as GP.
- the GP-compatible contactless IC chip 32 can be used in multi-application platforms.
- the multi-application platform can load multiple services that emulate IC cards in the memory area of one SE, and users can add or delete services at their will.
- the GP-compatible contactless IC chip 32 uses ISO/IEC 14443 Type-a/b technology in addition to FeliCa (registered trademark)-compatible services provided using FeliCa (registered trademark) technology.
- the provided service can be installed (registered) and used by the user.
- the GP-incompatible TSM server 51 in FIG. 2 is a TSM server that manages the SE of the non-contact IC chip compatible only with FeliCa (registered trademark).
- the GP-compatible TSM server 12 of the present embodiment is a TSM server that manages the SE of the GP-compatible non-contact IC chip 32 .
- an FC command from the TSM server 51 not compatible with GP, or from the TSM server 12 compatible with GP of this embodiment can be managed using GP commands.
- An FC command is a command defined by FeliCa (registered trademark)
- a GP command is a command defined by GP.
- services other than FeliCa (registered trademark) installed in the SE of the GP-compatible non-contact IC chip 32 may not be managed by FC commands from the GP-incompatible TSM server 51 .
- FIG. 3 is a diagram exemplifying the logical configuration of the SE memory area of the contactless IC chip 32.
- State A in FIG. 3 is a state in which no service is installed in the SE of the contactless IC chip 32 .
- State B is a state in which an application (applet) corresponding to the service is installed in the contactless IC chip 32 .
- an application applet
- a memory area allocated in the memory area of the SE.
- the allocation area stores an Applet instance generated by Applet installation processing.
- An applet instance is also called an application because the function of the application corresponding to the service is realized by executing the applet instance.
- three Applet instances 71-1, 71-2, and 71-3 corresponding to FeliCa (registered trademark) services are stored in their assigned memory areas.
- the allocation area when the Applet instance is in the non-personalized state is referred to as the allocation area in the service undetermined state.
- the allocated area when the Applet instance is in the personalized state is allocated to a predetermined service, so it is called the allocated area in the service fixed state or simply the allocated area.
- the allocated area in which the Applet instance is stored is also referred to as the allocated area or memory area allocated to the Applet instance.
- Applet instances 71-1, 71-2, and 71-3 are all in the non-personalized state, so the allocations assigned to Applet instances 71-1, 71-2, and 71-3 respectively All of the areas are allocation areas in a service undetermined state.
- State C is a state in which part of the Applet instance stored in the SE of the contactless IC chip 32 is personalized.
- user-specific data business data supplied from the TSM server 12 is written (retained) in the Applet instance 71-3 as internal data, and the Applet instance 71-3 is personalized. (personalized state).
- the service corresponding to the applet instance 71-3 becomes available.
- the allocated area assigned to the Applet instance 71-3 in the personalized state becomes the allocated area in the service determined state.
- the allocation area allocated to the Applet instance 71-3 contains business data (various data) in FeliCa (registered trademark) is simplified and exemplified.
- the system of the highest hierarchy indicates a logical IC card unit, and stores a system code specifying the system and a key for accessing data below the shift hierarchy as system data.
- the area of the lower hierarchy of the system stores data indicating the number of remaining usable blocks in the memory area, the allocation of the number of blocks to each data of the lower hierarchy, and a key for accessing the data of the area hierarchy and below.
- a block is a unit for reading and writing data.
- the data in the lower layer of the area stores data for each type of service information (for example, user information, history information, etc.) and keys for accessing data for each service information.
- IDm for identifying the communication partner and PMm for identifying the performance of the communication partner are stored in the memory area assigned to the service corresponding to the Applet instance 71-3.
- the Applet instance generated by the installation process of the application corresponding to the service is written to the memory area (allocated area) of the SE, and the user-specific data (business data) is held as the internal data of the Applet instance to be personalized. This is also referred to as issuing a service or issuing a service (service issuing).
- FIG. 3 illustrates a case where three allocated areas are generated in the SE memory area.
- the number of allocated areas may be determined in advance according to the capacity of the memory area, etc., or may be added or deleted according to the free space of the memory area.
- State A in FIG. 4 is the same state as state C in FIG. 3, and Applet instance 71-3 is in the personalized state.
- the allocation area allocated to Applet instance 71-3 is the allocation area in the service defined state.
- State B is a state in which the service corresponding to Applet instance 71-3 has been deleted due to card cancellation or the like.
- the GP-compatible TSM server 12 deletes the business data held in the Applet instance 71-3 and puts the Applet instance 71-3 in a non-personalized state. . That is, the GP-compatible TSM server 12 sets the allocation area allocated to the Applet instance 71-3 as an allocation area in a service undetermined state.
- FIG. 5 is a diagram explaining a case where the service loaded on the non-contact IC chip 32 is deleted by the TSM server 51 that does not support GP.
- State A in FIG. 5 is the same state as state C in FIG. 3 and state A in FIG. 4, and Applet instance 71-3 is in the personalized state.
- the allocation area allocated to Applet instance 71-3 is the allocation area in the service defined state.
- State B is a state in which the service corresponding to Applet instance 71-3 has been deleted due to card cancellation or the like.
- the GP-incompatible TSM server 51 deletes the business data held in the Applet instance 71-3 when deleting the service corresponding to the Applet instance 71-3.
- the GP-incompatible TSM server 51 cannot perform processing up to the allocation of memory areas for GP-compatible SEs, so the applet instance 71-3 cannot be returned (changed) to the non-personalized state. That is, the allocation area allocated to the Applet instance 71-3 remains as the allocation area in the service defined state.
- the GP-compatible TSM server spreads.
- the server 12 may be changed. If this technology is not applied to the GP-compatible TSM server 12, the TSM server 12 will issue a new service to the Applet instance 71-3 in the personalized state even if the business data is empty. I can't. That is, the TSM server 12, even if the allocation area is in a state in which at least a part of the implementation data necessary for implementing the service is deleted, if the service is in the confirmed state, the TSM server 12 creates a new allocation area in the service confirmed state. services cannot be issued.
- the non-contact IC chip 32 will continue to have allocated areas allocated to services that will not be implemented in the future. As a result, a part of the memory area of the SE may not be used effectively, and the number of services that can be issued may be limited to a smaller number than it should.
- the TSM server 12 of the present embodiment to which this technology is applied prevents such a situation from occurring.
- an Applet instance in which business data is empty and in a personalized state is referred to as an Applet instance in an empty personalized state.
- a personalized Applet instance that holds business data is simply called a personalized Applet instance.
- the case in which the business data is empty is an example of a state in which at least a part of the execution data required to implement the service has been deleted. It can be applied when a new service is issued to an allocation area in the service defined state with at least part of the implementation data deleted.
- FIG. 6 is a diagram showing an outline of service issuing processing performed by the TSM server 12 of the present embodiment for Applet instances in the empty personalized state.
- the Applet instance 71-3 of the contactless IC chip 32 is in an empty personalized state, like state A of FIG.
- Applet instances 71-1 and 71-2 are in the personalized state, unlike state A of FIG. It is assumed that the SE of the non-contact IC chip 32 in state A does not have a memory area (Applet instance in non-personalized state) for storing a new Applet instance corresponding to a new service.
- the TSM server 12 of this embodiment first changes the empty personalized state Applet instance 71-3 to the non-personalized state when issuing a new service. That is, the allocated area allocated to the Applet instance 71-3 is returned to the undefined service allocated area.
- State B represents the contactless IC chip 32 after the empty personalized state Applet instance 71-3 has been changed to the non-personalized state.
- the TSM server 12 issues a new service to the contactless IC chip 32 in state B, causes the Applet instance 71-3 in the non-personalized state to hold the business data of the new service, and changes to the personalized state. do.
- State C represents the contactless IC chip 32 after the empty personalized state Applet instance 71-3 has been changed to the personalized state.
- the application 91 is software executed in the controller 31 of FIG. 1, and mainly exchanges between the user and the service provider server 13.
- the TSM server 12 exchanges data with the middleware 92 and with the service provider server 13.
- the TSM server 12 has a command generator 12A that executes service issuing processing as shown in FIG. 6 by executing a program for service issuing processing by a CPU (not shown). That is, the TSM server 12 functions as an information processing device having a command generator 12A.
- the command generation unit 12A of the TSM server 12 as an information processing device sends the information processing device 11 as a terminal device a service confirmation assigned to an empty personalized state Applet instance in the SE of the non-contact IC chip 32.
- Service issuance processing in the information processing device 11, such as a process of changing the state allocation area to a service undetermined allocation area, and a process of storing implementation data corresponding to a new service in the service undetermined allocation area. is generated, and the generated command and the like are supplied (transmitted) to the information processing apparatus 11 .
- the processing of the command generation unit 12A is omitted because the processing of the command generation unit 12A is the processing of the TSM server 12.
- FIGS. 8 to 10 show service issuance when there remains a memory area for adding a new service to the SE of the contactless IC chip 32 (a service-undefined allocation area allocated to an Applet instance in a non-personalized state). It is a diagram showing the procedure of. 8 to 10 corresponds to a service issuing procedure in a GP-compatible TSM server to which the present technology is not applied.
- the application 91 instructs the service provider server 13 to issue a service, for example, when the user performs a service issuing request operation (procedure 1). Specifically, the application 91 requests the service provider server 13 to acquire an authentication ticket necessary for service issuance.
- the service provider server 13 transmits business data necessary for service issuance to the TSM server 12, requests service issuance, and acquires an authentication ticket. is requested (step 2).
- the TSM server 12 When the TSM server 12 receives a service issuance request from the service provider server 13 in step 2, it authenticates that the communication partner of the request is not the camouflaged server but the service provider server 13, and then accepts the service issuance request. and stores business data (issuance data necessary for service issuance) acquired from the service provider server 13 .
- the TSM server 12 generates an authentication ticket and transmits it to the service provider server 13 (procedure 3).
- An authentication ticket is data signed with an authentication key held by the TSM server 12 .
- the middleware 92 transmits the authentication ticket obtained from the application 91 to the TSM server 12 and requests a command to personalize the Applet instance 71 (step 10). ).
- the middleware 92 acquires the command from the TSM server 12 in procedure 11, it sends the acquired command to the applet instance 71 to personalize the applet instance 71 (procedure 12).
- the implementation data for implementing the newly added service is stored in the service undetermined allocation area, and the new service is issued.
- 11 to 16 show the procedure for issuing a service to the Applet instance 71 in the empty personalized state when there is no memory area left to add a new service to the SE of the contactless IC chip 32. It is a diagram. The same procedure numbers as the procedures shown in FIGS. 8 to 10 are given the same procedure numbers, and the explanation thereof will be omitted as appropriate.
- the application 91 instructs the service provider server 13 to issue a service, for example, when the user performs a service issuing request operation (procedure 1).
- the application 91 acquires the authentication ticket 1 from the TSM server 12 through the service provider server 13 (procedures 2 to 4).
- the authentication ticket that the application 91 acquires from the TSM server 12 in steps 1 to 4 is referred to as authentication ticket 1 in order to avoid confusion with the authentication ticket generated by the middleware 92 in step 7, which will be described later.
- the middleware 92 checks the state of the contactless IC chip 32 and selects an empty personalized applet instance 71 ( hereinafter referred to as unnecessary instances) is detected (procedure 6).
- unnecessary instance is also an Applet instance of the allocated area in the service defined state from which at least a part of the implementation data required to implement the service has been deleted.
- the middleware 92 when the middleware 92 detects in step 6 that only the unnecessary instance area remains as the memory area that can be used for service issuance, the middleware 92 requests a command to return the unnecessary instance to the non-personalized state (step 7). ).
- the middleware 92 generates an authentication ticket 2 in procedure 7 and transmits it to the TSM server 12 .
- the authentication ticket 2 is data signed with an authentication key held by the middleware 92 .
- the TSM server 12 verifies the authentication ticket 2 obtained from the middleware 92 in procedure 7, generates a command for returning the unnecessary instance to a non-personalized state, and sends it to the middleware 92 (procedure 8).
- the middleware 92 acquires the command from the TSM server 12 in procedure 8, it sends the acquired command to the Applet instance 71, which is an unnecessary instance, and restores the Applet instance 71 to the non-personalized state (procedure 9).
- the middleware 92 sends the authentication ticket 1 obtained from the application 91 in procedure 5 to the TSM server 12, and requests a command to personalize the Applet instance 71 in the non-personalized state (procedure 10). As a result, the middleware 92 acquires a command for personalizing the Applet instance 71 from the TSM server 12 (procedure 11).
- the middleware 92 personalizes the Applet instance 71 by sending the command obtained from the TSM server 12 in Procedure 11 to the Applet instance 71 (Procedure 12). As a result, the service is issued.
- FIG. 17 and 18 are sequence diagrams showing the procedure of service issuing processing in the information processing system 1.
- FIG. 17 and 18 are sequence diagrams showing the procedure of service issuing processing in the information processing system 1.
- step S51 the application 91 instructs the service provider server 13 to issue a service, for example, when the user performs a service issuing request operation. That is, the application 91 requests the service provider server 13 to acquire an authentication ticket necessary for service issuance.
- Step S51 corresponds to procedure 1 in FIG.
- the service provider server 13 accepts a request for obtaining an authentication ticket from the application 91 at step S51.
- step S102 the service provider server 13 transmits business data necessary for service issuance to the TSM server 12, requests service issuance, and requests an authentication ticket.
- Step S102 corresponds to procedure 2 in FIG.
- the TSM server 12 accepts a service issue request from the service provider server 13 at step S102.
- the TSM server 12 verifies the service provider server 13 that requested the authentication ticket at step S102. That is, the TSM server 12 verifies the signature of the request from the service provider server 13 .
- step S73 the TSM server 12 generates an authentication ticket 1. Note that steps S72 and S73 correspond to procedure 3 in FIG.
- step S74 the TSM server 12 transmits the authentication ticket 1 generated in step S73 to the service provider server 13.
- step S103 the service provider server 13 acquires the authentication ticket 1 transmitted by the TSM server 12 in step S74.
- step S104 the service provider server 13 transmits the authentication ticket 1 acquired from the TSM server 12 in step S103 to the application 91.
- Step S104 corresponds to procedure 4 in FIG.
- the application 91 acquires the authentication ticket 1 transmitted from the service provider server 13 at step S104.
- step S53 the application 91 supplies the middleware 92 with the authentication ticket 1 obtained from the service provider server 13 in step S52.
- Step S53 corresponds to procedure 5 in FIG.
- the middleware 92 acquires the authentication ticket 1 supplied from the application 91 at step S53.
- the middleware 92 requests the contactless IC chip 32 to confirm the state of the Applet instance.
- step S11 the non-contact IC chip 32 accepts the request to confirm the status of the Applet instance from the middleware 92 in step S32.
- step S12 the contactless IC chip 32 notifies the middleware 92 of the state of the Applet instance of the SE.
- step S33 the middleware 92 acquires the state of the Applet instance from the contactless IC chip 32 at step S12.
- step S32 when the middleware 92 is notified that there is no Applet instance in the unpersonalized state and only Applet instances in the empty personalized state (unnecessary instances) remain corresponds to step 6 in FIG.
- the processing of the middleware 92 proceeds to step S34. If there is an Applet instance in a non-personalized state, the process of the middleware 92 skips steps S34 to S42 and proceeds to step S43.
- the processing in the range enclosed by the dashed line in FIG. 17 is not performed when there is an Applet instance in a non-personalized state.
- step S35 the middleware 92 sends to the TSM server 12, together with the authentication ticket 2 generated in step S34, a request for an authentication ticket for returning the unnecessary instance to the non-personalized state.
- the TSM server 12 acquires the authentication ticket 2 and the authentication ticket request sent from the middleware 92 at step S35.
- the TSM server 12 verifies the authentication ticket 2 obtained from the middleware 92 at step S77. That is, it verifies whether the source that has transmitted the request for the authentication ticket 2 is a genuine source.
- the TSM server 12 generates an authentication ticket 3.
- the authentication ticket 3 is signed by the TSM server 12 .
- the TSM server 12 transmits the authentication ticket 3 generated at step S79 to the middleware 92.
- the middleware 92 acquires the authentication ticket 3 transmitted from the TSM server 12 at step S79.
- step S37 the middleware 92 sends to the TSM server 12 a request for a command to return the unnecessary instance to the non-personalized state together with the authentication ticket 3 obtained from the TSM server 12 in step S36.
- the TSM server 12 acquires the authentication ticket 3 and command request sent from the middleware 92 at step S36.
- the TSM server 12 generates a command to return the unnecessary instance to the non-personalized state.
- the TSM server 12 sends the command generated at step S83 to the middleware 92.
- steps S35 to S37 by the middleware 92 and the processing of steps S77 to S83 by the TSM server 12 represent the details of the processing of steps 7 and 8 in FIG.
- the middleware 92 acquires the command sent from the TSM server 12 at step S83.
- step S39 the middleware 92 instructs the contactless IC chip 32 (unnecessary instance) to execute the command acquired in step S38.
- Step S39 corresponds to procedure 9 in FIG.
- step S13 the non-contact IC chip 32 (unnecessary instance) accepts a command execution instruction from the middleware 92 in step S39.
- step S14 the non-contact IC chip 32 (unnecessary instance) executes the command received in step S38. This returns the unwanted instance to the non-personalized state.
- step S15 the non-contact IC chip 32 notifies the middleware 92 of a response to the effect that the command instructed in step S39 has been executed.
- the middleware 92 acquires the response from the contactless IC chip 32 at step S15.
- step S41 the middleware 92 notifies the TSM server 12 of a response to the effect that execution of the command transmitted from the TSM server 12 in step S84 has ended.
- the TSM server 12 acquires the response notified from the middleware 92 at step S41.
- the TSM server 12 notifies the middleware 92 of a response to the effect that the response notified from the middleware 92 at step S84 has been received.
- the middleware 92 accepts the response notified from the TSM server 12 at step S86.
- step S43 the middleware 92 sends a command request for issuing a service (personalizing the Applet instance 71) to the TSM server 12 together with the authentication ticket 1 obtained from the application 91 in step S31. do.
- Step S43 corresponds to procedure 10 in FIG.
- the TSM server 12 verifies the authentication ticket 1 obtained from the middleware 92 at step S84.
- the TSM server 12 generates a command corresponding to the request obtained from the middleware 92 at step S84. That is, the TSM server 12 generates commands for personalizing the Applet instance 71 .
- Steps S88 and S89 correspond to procedure 11 in FIG.
- step S90 the TSM server 12 transmits the command generated in step S89 to the middleware 92.
- the middleware 92 acquires the command sent from the TSM server 12 at step S90.
- step S45 the middleware 92 instructs the non-contact IC chip 32 (Applet instance in the non-personalized state) to execute the command obtained in step S44.
- Step S45 corresponds to procedure 12 in FIG.
- step S16 the non-contact IC chip 32 (Applet instance in non-personalized state) accepts a command execution instruction from the middleware 92 in step S45.
- step S17 the contactless IC chip 32 (Applet instance in non-personalized state) executes the command accepted in step S16. As a result, the non-personalized Applet instance becomes personalized and the service is issued.
- step S18 the non-contact IC chip 32 notifies the middleware 92 of a response to the effect that the command instructed in step S45 has been executed.
- the middleware 92 acquires the response from the contactless IC chip 32 at step S18.
- step S47 the middleware 92 notifies the TSM server 12 of a response to the effect that execution of the command transmitted from the TSM server 12 in step S90 has ended.
- the TSM server 12 acquires the response notified from the middleware 92 at step S47.
- step S92 the TSM server 12 notifies the service provider server 13 of the result of service issuance.
- the service provider server 13 acquires the result of service issuance notified from the TSM server 12 at step S92.
- step S108 the service provider server 13 notifies the TSM server 12 of a response to the effect that the result of issuing the service notified by the TSM server 12 in step S92 has been received.
- the TSM server 12 acquires the response notified from the service provider server 13 at step S93.
- step S94 the TSM server 12 notifies the middleware 92 of a response indicating that it has received the response notified from the middleware 92 in step S91.
- the middleware 48 acquires the response notified from the TSM server 12 at step S94.
- the unnecessary instance in the empty personalized state is returned to the non-personalized state, and a new service is issued to the unnecessary instance. That is, a service-determined allocation area from which at least part of the implementation data necessary for implementing the service has been deleted is changed to a service-undetermined allocation area, and a new service-undetermined allocation area is created. Service is issued. Therefore, the memory area of the SE can be effectively used without leaving an allocated area in which no service is performed. A situation in which the number of services that can be issued is limited to a smaller number than the original is also prevented.
- the Applet in the empty personalized state A new service is issued to an instance, that is, to an allocation area in a service defined state from which at least part of the implementation data has been deleted.
- the present technology is not limited to this, but when there is an Applet instance in an empty personalized state, that is, when there is an allocation area in a service defined state in which at least part of the implementation data has been deleted, an empty personalized state It may be the case that a new service is issued to an Applet instance, ie to a service defined allocation area with at least part of the implementation data deleted.
- a series of processes in the information processing system 1, the contactless IC chip 32, the middleware 92, the TSM server 12, or the service provider server 13 described above can be executed by hardware or by software.
- a program that constitutes the software is installed in the computer.
- the computer includes, for example, a computer built into dedicated hardware and a general-purpose personal computer capable of executing various functions by installing various programs.
- FIG. 19 shows the hardware configuration of the computer when the computer executes each process executed by the information processing system 1, the contactless IC chip 32, the middleware 92, the TSM server 12, or the service provider server 13 by a program.
- FIG. 4 is a block diagram showing an example
- a CPU Central Processing Unit
- ROM Read Only Memory
- RAM Random Access Memory
- An input/output interface 205 is further connected to the bus 204 .
- An input unit 206 , an output unit 207 , a storage unit 208 , a communication unit 209 and a drive 210 are connected to the input/output interface 205 .
- the input unit 206 consists of a keyboard, mouse, microphone, and the like.
- the output unit 207 includes a display, a speaker, and the like.
- the storage unit 208 is composed of a hard disk, a nonvolatile memory, or the like.
- a communication unit 209 includes a network interface and the like.
- a drive 210 drives a removable medium 211 such as a magnetic disk, optical disk, magneto-optical disk, or semiconductor memory.
- the CPU 201 loads, for example, a program stored in the storage unit 208 into the RAM 203 via the input/output interface 205 and the bus 204 and executes the above-described series of programs. is processed.
- the program executed by the computer (CPU 201) can be provided by being recorded on removable media 211 such as package media, for example. Also, the program can be provided via a wired or wireless transmission medium such as a local area network, the Internet, or digital satellite broadcasting.
- the program can be installed in the storage section 208 via the input/output interface 205 by loading the removable medium 211 into the drive 210 . Also, the program can be received by the communication unit 209 and installed in the storage unit 208 via a wired or wireless transmission medium. In addition, programs can be installed in the ROM 202 and the storage unit 208 in advance.
- the program executed by the computer may be a program that is processed in chronological order according to the order described in this specification, or may be executed in parallel or at a necessary timing such as when a call is made. It may be a program in which processing is performed.
- the present technology can also take the following configurations.
- (1) A state in which at least part of the implementation data is deleted from an allocation area allocated for each service in a memory area in which implementation data necessary for implementing each of one or more services is stored; and After performing a process of changing the allocation area remaining in a state of being allocated to a predetermined service to an allocation area in a service undetermined state in which no service is allocated, the new service is handled.
- An information processing device comprising: a processing unit that performs a service issuing process for storing the implementation data in the allocated area in the service undetermined state.
- (2) The information processing apparatus according to (1), wherein the processing unit performs the service issuing process when the allocated area in the service undetermined state does not exist in the memory area.
- the information processing apparatus wherein the middleware manages the memory area based on a command from a server device communicably connected to the middleware.
- (13) A state in which at least part of the implementation data is deleted from an allocation area allocated for each service in a memory area in which implementation data necessary for implementing each of one or more services is stored; and After changing the allocation area remaining in a state of being allocated to a predetermined service to an allocation area in a service undetermined state in which no service is allocated, the implementation data corresponding to the new service is changed.
- a command generation unit configured to transmit a command for executing the service issuing process to a terminal apparatus executing the service issuing process to be stored in the allocation area in the service undetermined state.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- General Engineering & Computer Science (AREA)
- Microelectronics & Electronic Packaging (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
Description
図1は、本技術が適用された情報処理システムの実施の形態の構成例を示すブロック図である。
状態Bは、空パーソナライズド状態のAppletインスタンス71-3が未パーソナライズ状態に変更された後の非接触ICチップ32を表す。
上述した情報処理システム1、非接触ICチップ32、ミドルウェア92、TSMサーバ12、又は、サービス事業者サーバ13における一連の処理は、ハードウエアにより実行することもできるし、ソフトウェアにより実行することもできる。一連の処理をソフトウェアにより実行する場合には、そのソフトウェアを構成するプログラムが、コンピュータにインストールされる。ここで、コンピュータには、専用のハードウエアに組み込まれているコンピュータや、各種のプログラムをインストールすることで、各種の機能を実行することが可能な、例えば汎用のパーソナルコンピュータなどが含まれる。
(1)
1又は複数のサービスの各々の実施に必要な実施データが記憶されるメモリ領域の前記サービスごとに割り当てられた割当領域のうち、前記実施データのうちの少なくとも一部が削除された状態、かつ、所定のサービスに割り当てられた状態で残存している前記割当領域に対して、いずれのサービスも割り当てられていないサービス未確定状態の割当領域に変更する処理を実施した後、新たなサービスに対応する前記実施データを前記サービス未確定状態の割当領域に記憶させるサービス発行処理を実施する処理部
を有する情報処理装置。
(2)
前記処理部は、前記メモリ領域に前記サービス未確定状態の割当領域が存在しない場合に前記サービス発行処理を実施する
前記(1)に記載の情報処理装置。
(3)
前記サービスは、ICカードにより提供され得るサービスである
前記(1)又は(2)に記載の情報処理装置。
(4)
前記サービスは、提供する事業者又は使用する目的を単位とする
前記(1)乃至(3)のいずれかに記載の情報処理装置。
(5)
前記実施データは、ユーザ固有のデータを含む
前記(1)乃至(4)のいずれかに記載の情報処理装置。
(6)
前記メモリ領域は、セキュアエレメントにおけるメモリ領域である
前記(1)乃至(5)のいずれかに記載の情報処理装置。
(7)
前記メモリ領域は、近距離無線通信により通信可能に接続された器機によりアクセス可能なメモリ領域である
前記(1)乃至(6)のいずれかに記載の情報処理装置。
(8)
前記メモリ領域は、非接触ICチップに組み込まれた不揮発性メモリのメモリ領域である
前記(1)乃至(7)のいずれかに記載の情報処理装置。
(9)
前記メモリ領域は、GlobalPlatformで定義された仕様で管理された
前記(1)乃至(8)のいずれかに記載の情報処理装置。
(10)
所定のサービスに割り当てられた状態で残存している前記割当領域は、FeliCa(登録商標)の技術仕様で削除されたサービスに割り当てられていたメモリ領域である
前記(9)に記載の情報処理装置。
(11)
前記処理部はミドルウェアの処理を実行する処理部であり、前記メモリ領域は、前記ミドルウェアにより管理可能なメモリ領域である
前記(1)乃至(10)のいずれかに記載の情報処理装置。
(12)
前記ミドルウェアは、前記ミドルウェアに通信可能に接続されたサーバ装置からのコマンドに基づいて前記メモリ領域の管理を行う
前記(11)に記載の情報処理装置。
(13)
1又は複数のサービスの各々の実施に必要な実施データが記憶されるメモリ領域の前記サービスごとに割り当てられた割当領域のうち、前記実施データのうちの少なくとも一部が削除された状態、かつ、所定のサービスに割り当てられた状態で残存している前記割当領域に対して、いずれのサービスも割り当てられていないサービス未確定状態の割当領域に変更した後、新たなサービスに対応する前記実施データを前記サービス未確定状態の割当領域に記憶させるサービス発行処理を実施する端末装置に対して、前記サービス発行処理を実施させるコマンドを送信するコマンド生成部
を有する情報処理装置。
(14)
前記コマンド生成部は、前記メモリ領域に前記サービス未確定状態の割当領域が存在しない場合に前記サービス発行処理を実施させる前記コマンドを送信する
前記(13)に記載の情報処理装置。
(15)
コンピュータを
1又は複数のサービスの各々の実施に必要な実施データが記憶されるメモリ領域の前記サービスごとに割り当てられた割当領域のうち、前記実施データのうちの少なくとも一部が削除された状態、かつ、所定のサービスに割り当てられた状態で残存している前記割当領域に対して、いずれのサービスも割り当てられていないサービス未確定状態の割当領域に変更する処理を実施した後、新たなサービスに対応する前記実施データを前記サービス未確定状態の割当領域に記憶させるサービス発行処理を実施する処理部
として機能させるためのプログラム。
Claims (15)
- 1又は複数のサービスの各々の実施に必要な実施データが記憶されるメモリ領域の前記サービスごとに割り当てられた割当領域のうち、前記実施データのうちの少なくとも一部が削除された状態、かつ、所定のサービスに割り当てられた状態で残存している前記割当領域に対して、いずれのサービスも割り当てられていないサービス未確定状態の割当領域に変更する処理を実施した後、新たなサービスに対応する前記実施データを前記サービス未確定状態の割当領域に記憶させるサービス発行処理を実施する処理部
を有する情報処理装置。 - 前記処理部は、前記メモリ領域に前記サービス未確定状態の割当領域が存在しない場合に前記サービス発行処理を実施する
請求項1に記載の情報処理装置。 - 前記サービスは、ICカードにより提供され得るサービスである
請求項1に記載の情報処理装置。 - 前記サービスは、提供する事業者又は使用する目的を単位とする
請求項1に記載の情報処理装置。 - 前記実施データは、ユーザ固有のデータを含む
請求項1に記載の情報処理装置。 - 前記メモリ領域は、セキュアエレメントにおけるメモリ領域である
請求項1に記載の情報処理装置。 - 前記メモリ領域は、近距離無線通信により通信可能に接続された器機によりアクセス可能なメモリ領域である
請求項1に記載の情報処理装置。 - 前記メモリ領域は、非接触ICチップに組み込まれた不揮発性メモリのメモリ領域である
請求項1に記載の情報処理装置。 - 前記メモリ領域は、GlobalPlatformで定義された仕様で管理された
請求項1に記載の情報処理装置。 - 所定のサービスに割り当てられた状態で残存している前記割当領域は、FeliCa(登録商標)の技術仕様で削除されたサービスに割り当てられていたメモリ領域である
請求項9に記載の情報処理装置。 - 前記処理部はミドルウェアの処理を実行する処理部であり、前記メモリ領域は、前記ミドルウェアにより管理可能なメモリ領域である
請求項1に記載の情報処理装置。 - 前記ミドルウェアは、前記ミドルウェアに通信可能に接続されたサーバ装置からのコマンドに基づいて前記メモリ領域の管理を行う
請求項11に記載の情報処理装置。 - 1又は複数のサービスの各々の実施に必要な実施データが記憶されるメモリ領域の前記サービスごとに割り当てられた割当領域のうち、前記実施データのうちの少なくとも一部が削除された状態、かつ、所定のサービスに割り当てられた状態で残存している前記割当領域に対して、いずれのサービスも割り当てられていないサービス未確定状態の割当領域に変更した後、新たなサービスに対応する前記実施データを前記サービス未確定状態の割当領域に記憶させるサービス発行処理を実施する端末装置に対して、前記サービス発行処理を実施させるコマンドを送信するコマンド生成部
を有する情報処理装置。 - 前記コマンド生成部は、前記メモリ領域に前記サービス未確定状態の割当領域が存在しない場合に前記サービス発行処理を実施させる前記コマンドを送信する
請求項13に記載の情報処理装置。 - コンピュータを
1又は複数のサービスの各々の実施に必要な実施データが記憶されるメモリ領域の前記サービスごとに割り当てられた割当領域のうち、前記実施データのうちの少なくとも一部が削除された状態、かつ、所定のサービスに割り当てられた状態で残存している前記割当領域に対して、いずれのサービスも割り当てられていないサービス未確定状態の割当領域に変更する処理を実施した後、新たなサービスに対応する前記実施データを前記サービス未確定状態の割当領域に記憶させるサービス発行処理を実施する処理部
として機能させるためのプログラム。
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2023500621A JPWO2022176445A1 (ja) | 2021-02-19 | 2022-01-13 |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2021024926 | 2021-02-19 | ||
JP2021-024926 | 2021-02-19 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2022176445A1 true WO2022176445A1 (ja) | 2022-08-25 |
Family
ID=82930737
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2022/000816 WO2022176445A1 (ja) | 2021-02-19 | 2022-01-13 | 情報処理装置、及び、プログラム |
Country Status (2)
Country | Link |
---|---|
JP (1) | JPWO2022176445A1 (ja) |
WO (1) | WO2022176445A1 (ja) |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2005124560A1 (ja) * | 2004-06-15 | 2005-12-29 | Sony Corporation | 情報管理装置及び情報管理方法 |
JP2015533236A (ja) * | 2013-01-25 | 2015-11-19 | グーグル・インコーポレーテッド | データの再インストールを管理するためのシステム、方法、およびコンピュータプログラム製品 |
JP2018136835A (ja) * | 2017-02-23 | 2018-08-30 | 凸版印刷株式会社 | Icカード及びicカード発行システム、icカード発行方法 |
-
2022
- 2022-01-13 WO PCT/JP2022/000816 patent/WO2022176445A1/ja active Application Filing
- 2022-01-13 JP JP2023500621A patent/JPWO2022176445A1/ja active Pending
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2005124560A1 (ja) * | 2004-06-15 | 2005-12-29 | Sony Corporation | 情報管理装置及び情報管理方法 |
JP2015533236A (ja) * | 2013-01-25 | 2015-11-19 | グーグル・インコーポレーテッド | データの再インストールを管理するためのシステム、方法、およびコンピュータプログラム製品 |
JP2018136835A (ja) * | 2017-02-23 | 2018-08-30 | 凸版印刷株式会社 | Icカード及びicカード発行システム、icカード発行方法 |
Also Published As
Publication number | Publication date |
---|---|
JPWO2022176445A1 (ja) | 2022-08-25 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8215547B2 (en) | Data communicating apparatus and method for managing memory of data communicating apparatus | |
US8799574B2 (en) | Method and devices for installing and retrieving linked MIFARE applications | |
EP1770533A1 (en) | Information management device and information management method | |
EP2183728B1 (en) | Method, system and trusted service manager for securely transmitting an application to a mobile phone | |
US8621168B2 (en) | Partitioning the namespace of a contactless smart card | |
US9608989B2 (en) | Method, system, trusted service manager, service provider and memory element for managing access rights for trusted applications | |
US8811971B2 (en) | Mobile communication device and method for disabling applications | |
US8335932B2 (en) | Local trusted services manager for a contactless smart card | |
EP2406712B1 (en) | Method for transmitting an nfc application and computer device | |
US20100043016A1 (en) | Application management device and application management method | |
US20150029003A1 (en) | Mifare push | |
US20060086785A1 (en) | Portable electronic apparatus and method of updating application in portable electronic apparatus | |
US7516479B2 (en) | Data communicating apparatus and method for managing memory of data communicating apparatus | |
US9785780B2 (en) | Information processing apparatus and method, recording medium, and program | |
US20060218196A1 (en) | Information management device and information management method | |
WO2009147548A2 (en) | Method for storing nfc applications in a secure memory device | |
WO2022176445A1 (ja) | 情報処理装置、及び、プログラム | |
US20100199059A1 (en) | Mobile communication device and method for defragging mifare memory | |
KR20120029521A (ko) | 보안 메모리 카드 | |
US20100200650A1 (en) | Mobile communication device and method for recovering mifare memory | |
Sugano et al. | Advances with Osaifu Keitai—Starting Services Supporting NFC (Type A/B) on NTT DOCOMO UIM Cards— | |
KR20070022737A (ko) | 정보 관리 장치 및 정보 관리 방법 | |
JP2005196413A (ja) | データ通信装置及びデータ通信装置のメモリ管理方法 | |
JP2006260550A (ja) | 非接触型端末装置 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 22755770 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2023500621 Country of ref document: JP Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 18546253 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 22755770 Country of ref document: EP Kind code of ref document: A1 |