Method and device for near-field data transfer.

Abstract

Title: Method and device for near-field data transfer. The invention relates to a method and device for transferring data from a mobile terminal (TM_E) equipped with a near-field communication (NFC) module. The mobile terminal is capable of positioning itself in NFC mode (M_NFC) or in IBC mode (M_IBC) to perform contactless transactions. The method is characterized in that it comprises, on the mobile terminal (TM_E), the following steps: - selecting (E50) NFC mode or IBC mode; - positioning (E52) the mobile terminal in NFC reader mode; - transmitting (E55) an invitation message (WUP_IBC) according to an IBC near-field communication type (NFC-IBC); - Deactivate (E56) NFC reader mode; - Receive (E57) a pairing message (ACK_IBC) on a return channel (CR) separate from the near-field channel; - Transfer (E58) the data on the return channel (CR). Fig. 8

Description

Description Title of the invention: Method and device for transferring data in close field. Scope of the invention

[0001] = The invention relates generally to telecommunications, and more specifically- specifically for contactless communications using shortwave radio technologies distance, particularly of the NFC (Near Field Communication) type. It applies more specifically to terminals equipped with physical and low- resources software including a microprocessor and a field communication module near field (NF) receiving an electromagnetic field. Previous Art

[0002] — Near field communications, commonly called NFC, based princi- based on the ISO (International Standards Organization) 14443 standard and on the standard ISO / IEC 18092 uses wireless technologies to enable exchange of information between two devices located a short distance apart, typically less than ten centimeters. Communications of this type offer many advantages. plications in the areas of payment or transport, for example.

[0003] Recently in this area, new communication techniques have emerged Wireless communication using the human body as a channel. These technologies are... grouped under the generic term IBC (from English: Zntra-Body Communication) or Furthermore, BCC (for Body Channel Communication) indicates that the human body acts in addition like a conductor to transmit information from one point to another. It is not therefore it is no longer necessary to bring the IBC terminal close to its counterpart to establish a Communication: it can be kept in the wearer's pocket, bag, etc. By bringing their hand close to an NFC reader terminal, the individual carrying the IBC terminal establishes a secure communication between its terminal and the reader terminal. document WO2017 / 093639 describes such a system, for example.

[0004] …— But the carrier may be required to make IBC communications between its a mobile terminal and another mobile terminal, particularly for transferring data. This is not possible today.

[0005] — There is therefore a need to ensure communication between two terminals mobile devices equipped with IBC functionality Description of the invention

[0006] The invention improves upon the state of the art.

[0007] — To this end, it proposes a method for transferring data from a mobile terminal equipped with a near-field communication module, said mobile terminal being capable of operating in NFC or IBC mode to perform contactless transactions The process is characterized in that it comprises the following steps on the mobile terminal: - select NFC mode or IBC mode; - position the mobile device in NFC reader mode; - send an invitation message using an IBC near field communication type; - disable NFC reader mode; - receive a pairing message on a return channel separate from the near-field channel; - transfer the data over the return channel. Advantageously, according to the invention, a specific protocol is established between the transmitting mobile terminal and another receiving mobile terminal operating in IBC mode. The transmitting mobile terminal can be positioned in NFC mode or IBC mode. In IBC mode, it keeps its terminal close to its body, which carries the signal in the near field. To establish communication, its body must be brought close to that of the person holding the receiving terminal. In NFC mode, it holds its terminal in its hand. To establish communication, its terminal must be brought close to the body of the person holding the receiving terminal. In both cases, it transmits an invitation message in IBC format and opens communication on a separate return channel upon receiving the return message from the receiving IBC terminal. It is positioned in NFC reader mode for a limited time at the start of the IBC transaction.Indeed, NFC reader mode consumes a lot of energy, so it is advisable to deactivate it as soon as pre-pairing is complete, either right after the invitation message is sent, or after receiving the pairing request. Advantageously, it is thus possible to carry out a transfer of data which can be voluminous between on the one hand a transmitting terminal positioned in NFC or IBC mode and on the other hand a receiving terminal positioned in IBC mode, that is to say that it is in the pocket, bag, etc. of the user of the receiving terminal. The term "mobile terminal" here refers to a mobile device equipped with an NFC module. This could be, for example, a mobile phone, smartphone, or other connected device. The transmitting mobile terminal can be configured in NFC mode or IBC mode. "IBC" or IBC mode refers to near-field communication that passes through the user's body. This term is used in contrast to "NFC" mode, which is the standard mode of NFC communication, in which the device containing the NFC technology (typically a mobile phone or smartphone) is in close physical proximity to the NFC-enabled device. A "near field communication module" refers to a controller, or NFC component (CLF for Contactless Frontend), that constitutes a near field communication module similar to an electromagnetic transponder and includes software components (firmware, etc.) necessary for implementing NFC communications. Such a component is associated with an antenna, which transmits the received NF signals to the NFC component. By "near field communication type" we mean a standard NFC type communication, or an IBC type communication, that is to say a communication established in the near field according to the standard NFC type or according to the IBC type intended for the transmission of electromagnetic waves via the user's body. By "reader mode" we mean a terminal equipped with an NFC module capable of positioning itself in NFC reader mode as defined by NFC standards. In reader mode, the terminal uses its own RF field to communicate. It is said to be active. Conversely, in card emulation mode, the terminal responds to a command from the initiator / reader in a passive mode using charge modulation. According to a particular embodiment of the invention, the method as described above further comprises, after the step of positioning the mobile terminal in NFC reader mode: - a step to arm a reader mode timer; - a step to deactivate the reader mode if the timeout is exceeded. Advantageously, this method incorporates a timer for the reader mode. This timer, corresponding to the maximum duration the mobile terminal can remain in reader mode, prevents the terminal from staying in this energy-intensive mode for too long and unnecessarily, thus draining its batteries. According to another particular embodiment of the invention, which may be implemented cumulatively or alternatively with the preceding ones, the method as described above is further characterized in that the IBC or NFC mode is selected via a human-machine interface of the mobile terminal. Advantageously, with this mode, the terminal can be set to either mode by default, or temporarily. It is particularly useful to set it to IBC mode by default, as users with IBC may no longer wish to use standard NFC mode, since IBC allows them to keep their terminal in their pocket. Default setting can be configured, for example, through the terminal's settings. The user can exit this default mode by reactivating the other mode (via a menu, a push button, a slider, etc.). The terminal can also be set to either mode temporarily by the user: for a specific duration, or for a set of transactions, or for a single transaction. According to another particular embodiment of the invention, which may be implemented cumulatively or alternatively with the preceding ones, the method as described above is further characterized in that a type of IBC application is selected via a human-machine interface of the mobile terminal. Advantageously, in this mode, an IBC application, for example, for data transfer via IBC, can be set as the default, or temporarily, by the user. An application can be selected, for example, via the terminal's configuration settings (through a menu, a push button, a slider, etc.), or an on-screen menu, etc. Selecting such an application, or option, allows the appropriate program, for example, for content transfer, to launch when such content (a video, a website, an address book, etc.) is selected on the screen by the user. According to another particular embodiment of the invention, which may be implemented cumulatively or alternatively with the preceding ones, the method is characterized in that said invitation message contains one or more pieces of data from among: - a risk factor in establishing the return channel; - an IBC application type; - a type of return channel; - a service parameter. Advantageously, in this mode, randomness, or random data, can be used to enhance security during the establishment of the return channel: if the same randomness is shared by the sending and receiving mobile terminals, communication can be securely established over the return channel. Randomness, also called a "challenge," takes the form of a parameter enabling a calculation using secret cryptographic keys, the result of which is compared by both entities before establishing communication. Advantageously, with this method, the IBC application type (e.g., IBC-S) can also be included in the invitation message. This allows for the definition of several different IBC transactions (transport, payment, gaming, data transfer, etc.) and verification at the receiver level that the application type is indeed the one it expects. The existing NFC standard can be reused, for example, by using a reserved field or a field already defined for proprietary applications. This does not disrupt the operation of a receiver that is solely NFC-enabled and allows for the easy addition of IBC mode and its various applications. Advantageously, with this mode, the return channel can also be specified (Wi-Fi, Bluetooth, 4G cellular channel, 5G, etc.). This allows the transmitter, in particular, to to know on which channel it should listen for the response, and for the receiver to know on which channel it should request pairing. The invention also relates to a data transfer device for a mobile terminal equipped with a near-field communication module, said device being capable of positioning the mobile terminal in NFC mode or in IBC mode to perform contactless transactions, characterized in that it is configured to implement at the mobile terminal level: - select NFC mode or IBC mode; - position the mobile device in NFC reader mode; - send an invitation message using an IBC near field communication type; - disable NFC reader mode; - receive a pairing message on a return channel separate from the near-field channel; - transfer the data over the return channel. The invention also relates to a mobile transmitting terminal comprising such a data transfer device. The invention also relates to a method of receiving data on a mobile terminal equipped with a near-field communication module, said mobile terminal being capable of positioning itself in an IBC mode to perform contactless transactions, the method being characterized in that it comprises the following steps on the mobile terminal: - position the mobile terminal in IBC mode; - receive an invitation message according to an IBC near field communication type; - transmit a pairing message on a return channel separate from the near-field channel; - receive the data on the return channel. Advantageously, according to the invention, the receiving terminal, positioned in IBC mode, receives the data transfer invitation message from the transmitting terminal. If it is correctly positioned in IBC mode and authorizes the data transfer application, it responds on the return channel and receives the data on that channel once communication is established. According to a particular embodiment of the invention, the reception method as described above is further characterized in that the IBC mode is selected via a human-machine interface of the mobile terminal. Advantageously, under this mode, the receiving terminal can be positioned in IBC mode by default, either for a certain duration, or for a set of transactions. or for a single transaction, by the user, as described for the issuing terminal. According to a particular embodiment of the invention, the reception method as described above is further characterized in that a type of IBC application is selected via a human-machine interface of the mobile terminal and / or received in the invitation message. Thus, the user may have selected the IBC-S application type to authorize this application on the receiving mobile terminal and / or read it in the invitation message. According to a particular embodiment of the invention, the reception method as described above is further characterized in that the type of return channel is received in the invitation message. Advantageously, the return channel is specified in the invitation message, which allows the receiving terminal to know on which channel (e.g. Bluetooth) to request pairing. The invention also relates to a device for receiving data from a mobile terminal equipped with a near-field communication module, said device being capable of positioning the mobile terminal in an IBC mode to perform contactless transactions, characterized in that it is configured to implement at the mobile terminal level: - position the mobile terminal in IBC mode; - receive an invitation message according to an IBC near field communication type; - transmit a pairing message on a return channel separate from the near-field channel; - receive the data on the return channel. The invention also relates to a receiving terminal comprising such a receiving device. The invention also relates to a system comprising a transmitting mobile terminal equipped with a transfer device as described above and a receiving mobile terminal equipped with a receiving device as described above, characterized in that the data transfer is triggered when the transmitting mobile terminal positioned in NFC mode comes into proximity with the body of the user of the receiving mobile terminal. The invention also relates to a system comprising a transmitting mobile terminal equipped with a transfer device as described above and a receiving mobile terminal equipped with a receiving device as described above, characterized in that the data transfer is triggered when the body of the user of the transmitting mobile terminal positioned in IBC mode enters proximity to the body of the user of the receiving mobile terminal The invention also relates to computer programs comprising instructions for implementing one of the above methods according to any of the particular embodiments described, when said program is executed by a processor. The method can be implemented in various ways, including in hardwired or software form. This program can use any programming language and be in the form of source code, object code, or code intermediate between source and object code, such as in a partially compiled form, or in any other desirable form. The invention also relates to a computer-readable recording or information medium containing instructions for a computer program as described above. The aforementioned recording media can be any entity or device capable of storing the program. For example, the medium may include a storage means, such as a ROM (e.g., a CD-ROM or a microelectronic circuit ROM), or a magnetic recording means, such as a hard drive. Furthermore, the recording media may be a transmissible medium such as an electrical or optical signal, which can be transmitted via an electrical or optical cable, by radio, or by other means. The programs according to the invention can, in particular, be downloaded from a network such as the Internet. Alternatively, the recording media may correspond to an integrated circuit in which the program is incorporated, the circuit being adapted to execute or to be used in the execution of the process in question. List of figures Other features and advantages of the invention will become clearer upon reading the following description of particular embodiments, given by way of simple illustrative and non-limiting examples, and the accompanying drawings, among which: [fig.1] Fig.1 illustrates the context of the invention according to an IBC mode and an NFC mode. [fig.2] Fig.2 illustrates an architecture of an IBC / NFC mobile terminal according to a particular embodiment of the invention. [fig.3] Fig.3 illustrates an architecture of a reader terminal, or IBC / NFC terminal, according to a particular embodiment of the invention. [fig.4] Fig.4 illustrates the initialization steps of the IBC / NFC communication process according to one embodiment of the invention. [fig.5] Fig.5 illustrates the IBC / NFC communication initialization framework according to a particular embodiment of the invention. [fig.6] Figure [fig.6] illustrates a data transfer between two IBC mobile terminals according to a particular embodiment. [fig.7] Fig.7 illustrates a data transfer between two IBC mobile terminals according to another embodiment. [fig.8] Fig.8 illustrates the steps of a data transfer process between two IBC mobile terminals according to one embodiment. Description of one embodiment of the invention General principle of the invention The general principle of the invention consists of using a specific protocol between the reader terminal and the IBC / NFC mobile terminal to initiate communication in either mode, in the case of a mobile terminal capable of operating in both modes, which is the case for most mobile phones, or smartphones, on the market. Specifically, upon receiving a communication request in IBC mode, the mobile terminal will perform the necessary software and hardware actions to enable the body-to-body transaction, whereas upon receiving an NFC communication request, it will establish standard NFC communication, according to the state of the art. To this end: l. The mobile terminal is positioned in NFC or IBC mode. It commands even- temporarily the NFC-IBC component of the mobile so that it positions itself in the good mode; indeed, the reception of an IBC message can take place in a NFC hardware mode, but the message will be of poor quality if no No adaptation was carried out. Then it performs a "pooling," meaning that it listen until you receive an appropriate message. If it is in one of the two modes and receives an initialization message in that mode, it launches the transaction. However, if it is in one of the two modes and receives the message 1. During initialization in the other mode, it remains waiting for an appropriate message. 2. The reader terminal, which cannot a priori distinguish an NFC transaction of an IBC transaction, periodically emits NFC and IBC messages, thus respecting the "polling" protocol defined by NFC standards. According to From the response he receives, he deduces one of the two modes, and can initiate the transaction. In particular, if it receives a response via NFC, it knows that it has dealing with an NFC mobile terminal, if it receives a message on another channel radio, specifically a pairing request, he knows he's dealing with a IBC mobile terminal. This return channel can be Bluetooth, Wi-Fi, Li-Fi, 4G or 5G cellular, etc., as long as it is a channel of short-range transmission, for example less than 10 meters, different from the near-field channel. Specific embodiments of the invention. Figure [Fig. 1] illustrates the context of the invention, in IBC and NFC modes respectively. In both modes, the user (2) carrying the mobile terminal equipped with an NFC-IBC module approaches the TP reader terminal until it is almost touching it to perform a service, for example, a monetary transaction. The TP and TM terminals are capable of communicating directly in the near field (NFC) or via an electromagnetic field (NF) using the user's body (IBC). The reader terminal (TP) can be, for example, an electronic payment terminal (EPT), a mobile device with an NFC module in reader mode, an IoT device, a personal computer, a computer mouse, a home gateway, etc. It is capable of emitting NFC radio-electrical signals via an NFC antenna. In this example, the reader terminal (TP) includes a surface consisting of the antenna, which may be protected and adapted to react when the user touches it or comes into close proximity in IBC mode, for example, by bringing their hand near it, or when they bring their mobile device near it in NFC mode. The term "surface" is not exhaustive and is used for illustrative purposes only; the antenna is the only essential component for the device to function. In this example, the mobile terminal TM is a mobile device equipped with an NFC-IBC module. An NFC-IBC module is a near-field receiver capable of receiving an electromagnetic wave either directly (NFC mode) or after it has passed through the user's body (IBC mode). A standard NFC component can receive IBC signals with degraded quality, but there are also techniques to improve the quality of the signal received in IBC mode through software and / or hardware modifications to the NFC component and its antenna. It is also capable of establishing a bidirectional return channel (e.g., Bluetooth) with the reading device. In another example, this mobile terminal TM could be a computer, a connected object, a tablet, etc. In the IBC mode shown on the left of [Fig. 1], denoted M_IBC, the IBC module behaves like a portable device naturally capable of receiving radio carrier waves, via an antenna, through the user's body (2). For this purpose, the mobile terminal is located in the immediate vicinity of the user (2), without necessarily being in direct contact with them. For example, the mobile terminal is placed inside the user's pocket. It could also be placed in a bag, or around their neck, etc. In these configurations, it is estimated that the mobile terminal is no more than a few centimeters from the user's body (2). The distance is, for example, less than 5 cm.When the user makes a movement towards the reader terminal, typically by touching or brushing their hand against the receiving surface containing the NFC antenna of the reader terminal, a radio carrier wave is transmitted from the reader terminal through the user's body. Two phases follow. on the mobile terminal transparently to the user, in order to provide the service. First, a contactless phase of the IBC type, which can be considered a pre-pairing, is initiated. The mobile terminal receives an IBC message, and if the message is correct, pairs itself, or connects, on the return channel with the reader terminal to enable bidirectional communication between the two terminals. Indeed, it is not feasible to transmit a large reply message via the user's body from a mobile terminal. Such a dialogue, consisting of a pairing phase followed by the establishment of bidirectional communication using a Bluetooth link, is described in document W0O2017 / 093639, included herein by reference. In the "classic" NFC mode shown in [fig.1], on the right (M_NFC), the wearer completes the transaction by physically bringing the mobile device close to the reader terminal. Communication is naturally bidirectional over the NFC channel, but the volume of data exchanged remains very limited. The use of either mode must be transparent to the user; that is, they must be able to complete the transaction with the reader terminal either in IBC mode by keeping the mobile phone in their pocket, or in NFC mode by removing the mobile phone from their pocket and bringing it close to the reader terminal, without interacting with the mobile phone itself. The embodiments described in more detail below enable this transparency and automate the process. Figure [Fig. 2] illustrates an architecture of the TM mobile terminal according to a particular embodiment of the invention. The TM mobile terminal has the classic architecture of a smartphone-type mobile phone and includes, in particular, a memory module (MEM), a processing unit equipped, for example, with a processor (PROC), and controlled by the computer program (PGR) stored in the MEM. At initialization, the code instructions of the PGR computer program are loaded into memory before being executed by the processor (PROC). The PROC processor of the processing unit (UT) implements, in particular, the steps of the adaptation process according to any of the specific embodiments described in more detail below, based on the instructions of the PGR computer program. The mobile terminal also includes the following modules: An NFC module for managing NFC and IBC communications. This module typically includes a contactless communication integrated circuit (CLF: Contactless Front-End) associated with an ANT antenna initially planned to receive NFC signals; the circuit consisting of the CLF and the antenna can be adapted to receive IBC signals with better quality via the human body. A DNF module for managing IBC / NFC near field communications. This module is notably in charge of the IBC or NFC mode selection steps, either directly (for example from the user via a mobile terminal's HMI) or by a so-called "pooling" mechanism, which consists of the mobile terminal positioning itself in a mode (for example IBC) then listening on the near field communication channel, and validating this mode if a received message corresponds to the selected mode. A PIBC module for the specific management of IBC communications. This module executes, in particular, the steps necessary for decoding the IBC initialization message and establishing the return channel to complete the transaction in IBC mode. Optionally, it is also capable of controlling the adaptation of the NFC circuit (CLF component and its antenna) to improve IBC reception. A PNFC module for managing NFC communications. This module performs the steps typically required to establish and execute an NFC transaction. It positions the mobile terminal in card emulation mode or reader mode, depending on the requirements of the intended application. A separate communication module, distinct from the NFC module, such as Bluetooth (or Wi-Fi, Li-Fi, etc.), labeled CR in the figure, is used to provide the return channel and thus ensure bidirectional communication for the IBC. The CR module is connected to an antenna, either directly or via the mobile phone. In the first case, the CR module is, for example, associated with the NFC component, possibly on the same substrate. For instance, it is connected to the output of the antenna demodulator, possibly via other circuits. It receives the demodulated data, possibly processed by a microprocessor, and establishes a Bluetooth communication channel. In the second case, the CR module is located elsewhere, for example, within the mobile device. The demodulated antenna signals are transmitted to the mobile device's microprocessor, which establishes the return channel (Bluetooth, Wi-Fi, cellular radio, etc.).Advantageously, in this case, the corresponding module natively present on the mobile terminal can be used. A user interface (UI) is a device adapted to transmit instructions or informational messages to the user and receive information from them. For example, the user interface is the smartphone screen. In another example, the interface is an audio interface for receiving messages and instructions. The UI may also include a keyboard, a microphone, etc. For example, it can be arranged to capture the pre-mode the user's IBC or NFC, temporarily, for a transaction or a set of transactions. Figure 3 illustrates an architecture of a reader terminal, or IBC / NFC terminal, according to a particular embodiment of the invention; The TP reader terminal has the classic architecture of a computer, and includes, in particular, a MEM' memory, a processing unit equipped, for example, with a PROC' processor, and controlled by the computer program PGR' stored in MEM' memory. At initialization, the code instructions of the PGR' computer program are, for example, loaded into memory before being executed by the PROC' processor. The PROC' processor of the UT' processing unit implements, in particular, the steps of the adaptation process according to any of the specific implementation modes described, according to the instructions of the PGR' computer program. The reader terminal also includes: an NFC module for managing near-field communications, NFC or IBC. This module typically includes a switching integrated circuit. Contactless Front-End (CLF) and an ANT antenna designed to emit and receive NFC signals. a DNF module for managing IBC near-field communications / NFC. This module is notably responsible for the mode selection steps. IBC or NFC via a mechanism called "pooling", which here means that the terminal reader periodically transmits messages of a certain type (NFC or IBC) and listens for the response on a return channel. If it has transmitted a It receives an IBC frame and a response on the return channel (Bluetooth), it can Initiate IBC communication. Otherwise, if it has sent an NFC frame, and receives a In response to the NFC channel, it then remains, as usual, to verify the NFC message. (the type of emulated card, etc.) according to a well-known pooling mechanism of the state of the art and described in the specification "NFC Activity Technical Speci- "Fication" of the NFC forum (NFC Forum-TS-Activity-1.0 2010-11-18) a PIBC module for managing IBC communications. This module executes, in particular, the steps necessary to establish the message IBC prompt which will be detailed in support of Figure 5, upon insertion of this message in the polling mechanism, in cooperation with the module PNFC', and the establishment of the return channel with the mobile terminal, for complete the transaction in IBC mode. A PNFC* module for managing NFC communications. This module It performs, in particular, the steps typically required for an NFC transaction. according to the state of the art constituted in particular by the NFC 14443 standard and the speci- technical specification mentioned above. The main initialization steps The NFC communication between a transmitter and the card is described in the Part 3 of the standard (ISO 14443-3 - Identification cards — Cards with Contactless integrated circuit(s) — Proximity cards — Part 3: Initia- (scanning and anti-collision). It also positions the reader terminal in mode NFC reader. a CR' module designed to transmit and receive data on the channel of return. The module is specifically designed to implement the steps of receiving / sending transaction-related messages on the return channel. Optionally, a user interface (UI), adapted to transmit to the user of instructions or informational messages. For example, The user interface is a screen on which messages and instructions are displayed. In another example implementation, the interface is an interface Audio playback of messages and instructions. The HMI can also include a keyboard, a microphone, etc. For example, it can be arranged to implement an invitation step in the communication process. It should be noted that any commercially available reader terminal can be advantageously used, provided that it has PIBC modules enabling it, by a simple software update of the reader terminal, to be able to emit a message having the characteristics of the IBC invitation message according to the invention, and to insert it into the polling mechanism, via its NFC antenna. It should also be noted that the TP reader terminal can be a mobile transmitter terminal with an architecture similar to that of the TP device described here. However, a mobile terminal is not suitable for prolonged use in reader mode because this mode drains the batteries. Figures 6 to 8 propose an embodiment that resolves this issue. Figure 4 illustrates steps in the NFC / IBC adaptation process according to one embodiment of the invention. According to this embodiment, a mobile terminal TM seeks to validate an electronic transaction according to one of the two contexts presented respectively in [fig.1], that is to say that the transaction takes place either by NFC if the user 2 brings his mobile terminal close to the reader terminal (M_NFC), or by IBC if he keeps his mobile terminal in his pocket (M_IBC). It is worth noting that NFC communications can cover two types of applications linked to two different operating modes on an NFC device: - The first mode, called reader mode, relates to reading data on transponder-type devices or NFC cards. In this mode, the device is active. It transmits commands to a mobile terminal as it would to a card without a physical connection. Contact according to the ISO 14443 (or Felica) standard. It generates a magnetic field which, upon contact with the passive board's antenna, induces an electric current that powers the board. - The second mode, called emulation mode, implements an emulation of a near-field communication module, typically to secure electronic transactions between an application stored on the device and an external reading terminal; in this mode, the device's NFC equipment is used passively. It simulates the behavior of a passive contactless card. Furthermore, NFC devices compliant with the ISO 14443 standard communicate using a range of technologies with distinct characteristics. The generic NFC standard is subdivided into three substandards: NFC-A, NFC-B, and NFC-F. These three substandards use a 13.56 MHz field. They differ in how this field is modulated in amplitude, in the encoding of the transmitted symbols, and in the bit rate. An NFC-enabled mobile terminal, such as a mobile phone, generally supports several, if not all, of the substandards. Similarly, a commercially available card reader typically supports several types of cards. NFC standards, particularly the aforementioned NFC Activity Technical Specification, define a protocol for determining the technology to use when more than one technology (NFC-A, NFC-B, NFC-F) is available on the reader terminal. This is known as "polling." The protocol requires the reader terminal to send a near-field invitation message, requesting a response using one of the available sub-standards, starting with NFC-A. The listening mobile terminal (or card) will only respond if it is capable of communicating using NFC-A; the reader terminal reacts within a limited time interval to the lack of a response by sending a second invitation signal using a second technology, for example, NFC-B. This process is repeated until the listening mobile terminal responds with an invitation response signal indicating compatibility with an NFC sub-standard. The embodiment described here adds a new NFC-IBC substandard to the existing substandards. This new substandard integrates with the polling mechanism while maintaining compatibility with the existing NFC substandards. Hereafter, "NFC mode" will refer to one of the sub-modes defined by the NFC forum, and "IBC mode" will refer to the additional sub-mode as described in the embodiments of the present invention. We will now describe [fig.5] in support of the following steps EO to E25: During an E20 initialization step, the reader terminal enters reader mode and prepares its WUP (Wake-Up) invitation message for the targeted sub-standard type (NFC-B, NFC-A, NFC-F, or NFC-IBC) in order to initiate a dialogue between the reader terminal and the mobile terminal, in NFC or IBC mode, in accordance with NFC standards, enhanced according to the invention with a new IBC message integrated into the polling mechanism. During an initialization step (EO), the mobile terminal TM activates its NFC module and enters card emulation mode. It then selects either IBC mode (M_IBC) or NFC mode (M_NFC). The mobile terminal TM is then brought near the reader (NFC mode), or the user's hand is brought near the reader (IBC mode), thereby enabling the transmission of the invitation message carrier wave through their body. In both cases, the mobile terminal receives the electromagnetic field generated by the reader, as explained previously. During step E21, the reader terminal enters a polling process as described above; that is, it transmits successively (and cyclically), until it receives a response, an invitation of the type corresponding to the sub-standards it implements (NFC-A, NFC-B, NFC-F, NFC-IBC, etc.). This invitation is denoted in the figure WUP_X, where X takes the values ​​A, B, F, IBC. The messages of the NFC sub-standards are specified by the standard and will not be detailed here. The new IBC initialization message conforms to the standard message format. As illustrated in Figure 5, it is an NFC-B type message, and its fields are reused to indicate the new communication type (IBC) and optionally service data and / or, among other things, a random number generator for subsequent pairing on the return channel, a return channel (RC) type to use (Bluetooth, Wi-Fi, 5G, etc.), and so on. Thus, in NFC mode, the messages exchanged between the reader and the mobile device remain unchanged. In IBC mode, the new initialization message, when received by the mobile device, initiates the IBC communication procedure: pairing and continuation of the transaction on the return channel (e.g., Bluetooth). During an El step, the TM mobile terminal receives the initialization message, WUP_X with X = IBC or NFC-(A, B, F); During an E2 step, it determines the type of message received (X); if X = NFC, it starts the NFC recognition procedure defined from step E10, otherwise it starts the IBC recognition procedure defined from step E3. During step E10 (X = NFC, the received message is an NFC invitation), a test can be performed to determine if the mobile device is actually in NFC mode. If not, the process returns to step EO0; otherwise, the standard NFC procedure begins with step E11. It should be noted that this step is optional because if the TM mobile device receives an NFC message while in IBC mode, it is irrelevant whether it responds to the NFC message, as this response will not be received by the reader terminal. Indeed, such a response signal would be too weak due to the distance. between the mobile terminal, positioned in card emulation mode, and the reader terminal (they are separated in IBC mode by the user's body). Indeed, the mobile terminal operates using charge modulation, i.e., induction. The 14443 standard indicates that, in such a situation, the emulated mobile terminal and the reader terminal can no longer communicate if they are separated by more than approximately 10 cm. Thus, the reader terminal cannot receive such a message and therefore returns to step E20 or E21 after the time defined by the NFC polling mechanism. During steps El1 and E12, a standard NFC transaction is carried out, with in El1, the mobile terminal sending the NFC acknowledgment if the NFC request type corresponds to the capabilities of the mobile terminal (for example ACK-A to confirm operation in NFC-A mode), then, if the reader terminal validates the communication during step E22, upon receipt of the response message, the classic execution of the NFC transaction during steps E12 and E23, for example the validation of a contactless payment. During step E3 (X = IBC, the message received from the reader terminal is a WUP-IBC type IBC invitation), a test can be performed to determine if the mobile device is indeed positioned in IBC mode. If not (it is in NFC mode), it returns to step E0; otherwise, the standard IBC procedure begins with step E4. It should be noted that this step E3 is optional because if the TM mobile device receives an IBC message while positioned in NFC mode, it cannot respond to this message, which does not correspond to an expected NFC format (defined by standard 14443). Thus, the reader terminal does not receive a response and returns to step E20 or E21 after the time defined by the NFC / IBC polling mechanism. If the test is successful in E3 (if X = IBC and the mobile device is in IBC mode), step E3 (or step E2 if step E3 is not implemented) is followed by step E4, during which the mobile terminal decodes the message (random number, service type, etc.) and then initializes the return channel. It may activate the channel (for example, by enabling Bluetooth or Wi-Fi on the terminal if it is not already enabled), and requests pairing with the reader terminal on this channel (Bluetooth, etc.) by transmitting, for example, an IBC transaction confirmation, denoted ACK_IBC, on this channel. This ACK_IBC message may include the encrypted random number used to secure the return channel. These steps are described in document WO2017 / 093639, included here by reference. Then, if the reader terminal validates the communication during step E24 upon receipt of the response message, particularly because it has received a message on the expected return channel with the expected randomness; the communication continues on this return channel during steps E4 and E24, for the reception / sending of messages relating to the IBC transaction (to validate a payment, a ticket balance, or exchange any other message required for the communication, etc.) Figure [Fig. 5] illustrates an IBC initialization message according to one embodiment. The main steps for initializing NFC communication between a transmitter and a card are defined in part 3 of ISO 14443-3. For a type B card, the reader terminal sends an identification request (called “REQB” or “WUPB”) and waits for a response (called “ATQB”) from the mobile terminal. The invention proposes to reuse such a protocol message, so as to insert an "IBC" type indication and optionally a number of data necessary for the subsequent IBC communication (random, request type, IBC application type, return channel type, etc.). As illustrated in [fig.5], and detailed in the aforementioned standard 14443-3, the standardized REQB / WUPB message contains: a start of frame byte, SOF; an APf anti-collision prefix octet (fixed value, in hexadecimal Ox5); an octet called "AFI" indicating the application family representing the type application targeted by the NFC reader (all applications — code 00, transport, finance, telecommunications, etc.) Only proximity cards applications of the type indicated by the AFI are authorized to respond to a REQB / WUPB command with an AFI other than "00". When AFI is equal to "OO", all proximity maps must process REQB / WUPB. Coding rules are specified in Table 12 of the aforementioned ISO 14443 standard. reproduced below; a "param" byte indicating, among other things, the type of request (REQB or WUPB); a two-byte "CRC_B" byte containing a code that allows detect and correct errors. [Table 1] — 2 y “Q N OF y = H + TS w Table 42 — Coding of AFI jar ras | rentree Sentetéen Lee ” ee | eee NE siynticatfde PAR | siynifeatf ds AH [proxtmitévondets «S v + All families and subfamilies | No application preference « + All subfamilies cie family | Broad preference * of sppücations x Y Only the Hth subfamily of the family x © r Private subfamily Ÿ H really + vu Transport Mass transport, Qus, | Airline, = VY 33" yv + 7 We Frances has an identification © Telecommunications Mass transport, Buses, | Overhead line, 'EP, Banks, Retail outlets.... Access control Public telephony. "8 2. + Muiimedia Senices imernet… + TV = q av Portable files… er ï + + vY Mésfioa! 'e v+ Muiimedias = Tv two from Hasant = vY Data storage PTT TE TRS Figure 5 illustrates a possible reuse of these fields, concerning a particular implementation method. The IBC initialization WUP_IBC message contains, as shown in the first example (WUP_IBC (1)), the Start of Frame (SOF) message immediately followed by the data bytes (DATA1, DATA2, DATA3, etc.) necessary to establish the IBC request. Since the AFI field is overwritten, a Type B card or mobile terminal will not respond to this request. The data fields may include, among other things, random number generation, IBC service information, the IBC application type (transport, file transfer, etc.), and so on. The message also contains a two-byte "CRC_IBC" byte with code for detecting and correcting errors. The WUP_IBC IBC initialization message contains, according to the second example (WUP_IBC (2)): an unmodified first octet of the APf anti-collision prefix (although The anti-collision algorithm is of little use in the case of the IBC, because it can differ- there can easily be several users whose hand is present simultaneously (tanément face au terminal lecteur); the "AFI" byte adapted for IBC while maintaining compatibility with the standard. With reference to Table 12 of the aforementioned standard 14443, reproduced below- Above, the Ox0 value of the first half-byte corresponds to a sub-family private of the type specified in the second half-octet. We can therefore use this second half-byte to specify the IBC application type, while preserving the standardized values ​​(e.g. '1' for transport, '2' for finance, etc. (by analogy to the values ​​from '1' to '9' in the first half-byte of the table.) Naturally, these two examples are by no means exhaustive, and a person skilled in the art could imagine any adaptation of this WUPB / REQB message or any other NFC initialization message. For example: the hexadecimal values ​​Ox9 to OxF of the first half-octet of the AFI field are reserved; therefore, one can use one of these without infringing on the standard. reserved values, for example Ox9 for IBC applications, in a way In general, the second half-byte of the field containing the application type IBC; a change in the value of the SOF field would allow the mobile terminal to immediately detect a non-NFC message etc. Figures 6 and 7 illustrate IBC communication according to another implementation method, for a data transfer between two mobile terminals. The receiving mobile terminal TM_R can have the type of architecture shown in [fig.2]. The transmitting mobile terminal TM_E can have the type of architecture shown in [fig.3], that is to say, it is capable of behaving as a reader terminal able to poll invitation messages. According to this embodiment, the user of the receiving mobile terminal TM_R selects IBC mode. For example, they make this selection by checking a box in their mobile terminal's settings, as shown in [Fig. 6] or [Fig. 7]. The user of the transmitting terminal TM_E can choose to position their terminal in NFC or IBC mode. For example, they make this selection by checking a box in the terminal's settings, as shown in [Fig. 6] or [Fig. 7]. In this example, the mobile terminal's settings allow selecting either NFC mode (which is already present on most mobile terminals on the market) or IBC mode for the mobile terminal's connectivity. According to the example, it is also possible to select BT (Bluetooth) mode, which is particularly useful for the IBC return channel.Furthermore, in IBC mode, a new application is authorized, represented in the figure by "IBC-S," which means that the mobile device is authorized to use an IBC data transfer application. This service type indication can also be provided, for example, in the data field or in the "type" field of the invitation message shown in [Fig. 5]. Naturally, many other IBC services could exist, such as [example of services]. example of gaming services, streaming services, etc. Note that in IBC mode, optionally, the user does not need to activate the CR module of the return channel (in the example, Bluetooth - BT) before using their mobile in IBC because the IBC application can take care of it for them, automatically during the IBC connection, and then after the data transfer, the return channel can be deactivated. The two mobile terminals, TM_R and TM_E, seek to communicate and exchange data, including large files that cannot be transmitted using Near Field Communication (NFC) technology, which has limited data transfer capabilities. Indeed, the maximum data rate offered by NFC is 424 kb / s, which is insufficient for transferring large amounts of data. Furthermore, such a transaction using NFC or IBC requires the mobile terminal or the user's hand to remain resting on the reader terminal, which is inconvenient and demands precise positioning. According to this example, user 2' from terminal TM_E wants to transmit a video to terminal TM_R from user 2 (alternatively it could be any document such as sound, web pages, photos, etc.) In the context of [Fig. 6], both users are positioned in IBC. They have both activated the IBC option and the IBC-S application on terminals TM_R and TMLE. When user 2° touches user 2 (or vice versa, it doesn't matter as long as they enter proximity as defined by IBC), their mobile terminal, temporarily in reader mode, transmits the IBC frame. This frame travels through their body, then through user 2's, and reaches user 2's mobile terminal, TM, in emulation mode. Upon recognizing the IBC frame, using the protocol detailed in [Fig. 4], or the simplified protocol proposed in [Fig. 8], user 2's mobile terminal TM_R establishes IBC communication with user 2's terminal, TM_E, by activating the CR return channel, as in the Bluetooth example.The first user can stop touching the second, the P file is transferred and the return channel is optionally closed. In the context of [Fig. 7], user TM_E is in NFC mode and the other is in IBC mode. When user 2 touches user 2 with their mobile device TM_E (or vice versa, it doesn't matter as long as the mobile device TM_E and user 2 are in NFC proximity), this mobile device, temporarily in reader mode, transmits the IBC frame, which travels through user 2's body and reaches user 2's mobile device, TM_R, in emulation mode. By recognizing the IBC frame, using the protocol detailed in [Fig. 4], or the simplified protocol proposed in [Fig. 8], user 2's mobile device establishes IBC communication with user 2's device. 2', TM_E, via activation of the CR return channel, for example via Bluetooth. The first user can stop touching the second, the P file is transferred and the return channel is closed. Optionally, in both cases, the closure of the channel is accompanied by the deactivation of the corresponding means of communication (Bluetooth, Wi-Fi, mobile data), in particular if it was deactivated before the start of data transfer. It should be noted that mobile phones rarely enter reader mode because the power required during polling is high, and therefore prohibitive for the battery. However, if user 2 has selected the IBC-S application, the TMLE mobile terminal can be placed in reader mode in a controlled manner, either for a limited period or only for the duration of sending the IBC invitation message, thus reducing the power consumption and therefore the battery drain. Figure 8 illustrates this. Figure 8 illustrates steps in an IBC mode data transfer process according to one embodiment of the invention. According to this embodiment, a mobile terminal TM_E equipped with NFC and IBC belonging to a user 2' seeks to transmit large amounts of data to another mobile terminal TM_R equipped with IBC belonging to a user 2, according to one of the two contexts presented respectively in figures 6 and 7, that is to say that the transaction takes place when user 2' brings either his mobile terminal TM_E ([fig.7]), or his hand ( [fig.6]), close to user 2 who for his part keeps his mobile terminal TM_R in his pocket. We will now describe [fig.8] in support of the following steps E30 to E58: During the initialization step E30, the receiving mobile terminal TM_R activates its NFC module (CLF and antenna). By default, the "card emulation" mode is generally selected on a mobile terminal. It then switches to IBC mode (M_IBC) and selects the "IBC-S" option, which corresponds to an IBC data transfer application. As shown in Figures 6 and 7, the user checks the two corresponding boxes on their smartphone screen, via the HMI module, for example, in the mobile terminal settings (checkbox in the terminal's connectivity options), or on the screen for the duration of the transaction. The IBC mode and the IBC-S application can therefore be set as the default for the TM_R mobile terminal, meaning it can operate for multiple transactions without user intervention. During an E50 initialization step, the TM_E mobile terminal activated its NFC module (CLF and antenna). By default, the "card emulation" mode is usually selected on a mobile terminal. It then switches to IBC (M_IBC) or NFC (M_NFC) mode and selects the "IBC-S" option, which corresponds to an application of Data transfer via IBC: As shown in Figures 6 and 7, the user selects the corresponding boxes on their smartphone screen, via the HMI module, for example, in the mobile terminal settings (e.g., a checkbox in the terminal's connectivity options), or on the screen for the duration of the transaction. IBC mode (Fig. 6) or NFC mode (Fig. 7), as well as the IBC-S option (Figures 6 and 7), can be set as the default for the TM_E mobile terminal, meaning it can operate for multiple transactions without user intervention. During a transfer initialization step E51, the user decides to use the "IBC-S" option to actually transfer data P to user 2's mobile terminal TML_R, which is in their pocket. User 2 launches an application for this purpose, for example, an APP_IBC-S applet from the PGR program. The applet can be selected by the user (for example, on their smartphone screen) or launched automatically when they select content to transfer, for example, via a menu selection that appears on the screen indicating that the content (P) can be transferred in IBC mode, or any other method to initiate the transfer of the content (P) to user 2 in IBC mode. During step E52, the TM_E mobile terminal switches to NFC reader mode, as previously defined. This switching occurs automatically and cyclically on some NFC mobile terminals on the market during the polling phase, which is preferably very short due to its high energy consumption. On other mobile terminals, the polling phase is only triggered when a contactless card is detected. Therefore, switching to reader mode during step E52 is either automatic or forced. During step E53, the process sets a timeout (T_LEC) for reader mode. This timeout, corresponding to the maximum duration the mobile terminal can remain in reader mode, is also called a "time-out." It is typically monitored in the background by the system processor using a clock. For example, T_LEC can be set to 10 seconds. This is because the mobile terminal TM_E cannot remain in reader mode for extended periods, as this would drain its batteries. This step is optional, as reader mode can be deactivated after the IBC invitation message is sent. However, it is useful in case this message fails, as it prevents the mobile terminal from remaining unnecessarily in reader mode for too long. Throughout the entire process, during step E54, the TM_E mobile terminal checks the time elapsed since the T_LEC timer was armed. It can perform this step in the background. If the time limit is exceeded, it deactivates reader mode and returns, for example, to step E50 or E51. During step E55, the process prepares the WUP_IBC invitation message for the The target sub-standard type, in this case IBC (since even though the TMLE mobile terminal is in M_NFFC mode, its recipient, the TM_R mobile terminal, is in M_IBC mode), is used to transfer content (P video). The WUP_IBC message can contain the IBC application type, here IBC-S (as suggested in the "Type" field of the WUB_IBC(2) message in [Fig. 4]). It can also contain a random value, the type of return channel to use, and / or any other data necessary for the service to function. Then user 2 comes into close proximity with user 2', either by bringing their mobile terminal TM_E close or by bringing part of their body close, thereby allowing the transmission of the carrier wave of the invitation message WUP_IBC through user 2's body. For example, one of the users 2 or 2' puts their hand on the other's shoulder, or they shake hands, etc. The mobile terminal TM_R receives the electromagnetic field, and therefore the WUP_IBC message, generated by the mobile terminal TM_E. According to this embodiment, the process deactivates the reader mode as soon as the message is transferred, during step E56. The TM_E mobile terminal, whether in NFC or IBC mode, is repositioned in card emulation mode. The WUP_IBC invitation message is received by the TM_R mobile terminal at step E31. During step E32, the TM_R mobile terminal decodes the received message (communication type, random number generator, service type, etc.). Specifically, it can verify that it is indeed an IBC invitation message (as explained, for example, in Figures 4 and 5), and that the received IBC application type (IBC-S) matches its configuration. It can also read and encrypt the received random number generator and determine the desired return channel type. If the invitation message is correct, it initializes the return channel (BT, Wi-Fi, etc.) and sends an IBC transaction confirmation, possibly accompanied by the encrypted random number generator, denoted ACK_IBC, over that channel. The TM_E mobile terminal validates or rejects the communication during step E57 upon receipt of the reply message, depending on the content of said reply message (it is indeed an IBC acknowledgment on the correct channel with the correct random number generation, etc.). Then it deactivates reader mode. Communication continues on the return channel during steps E33 and E58, for the reception / sending of messages relating to the transfer of file P. When the transfer is complete, the P file can be displayed, for example, on the screen of the TM_R mobile terminal. Optionally, a text or audio message can be sent to user 2 of the TM_R terminal. Then, optionally, the CR return channel is closed and the IBC-S option can be enabled or disabled. It goes without saying that the embodiments described above have been given for illustrative purposes only and are in no way exhaustive, and that many modifications can be easily provided by a skilled professional without requiring them to be considered an invention.

Claims

Demands

1. Method for transferring data from a mobile terminal (TM_E) equipped of a near field communication (NFC) module, said terminal mobile being capable of positioning itself in NFC mode (M_NFC) or in an IBC mode (M_IBC) for conducting contactless transactions, the The process being characterized in that it comprises, on the mobile terminal (TM_E) the following steps: - Select (E50) NFC mode (M_NFC) or IBC mode (M_IBC); - position (E52) the mobile terminal in NFC reader mode; - issue (E55) an invitation message (WUP_IBC) according to a type of Near field communication IBC (NFC-IBC); - disable (E56) NFC reader mode; - receive (E57) a peering message (ACK_IBC) on a channel of return (CR) distinct from the near-field channel; - transfer (E58) the data on the return channel (CR).

2. Method for transferring data from a mobile terminal (TM_E) according to the previous claim, characterized in that it further comprises, after the step of positioning (E52) the mobile terminal in mode NFC reader: - a step (E53) for arming a timer (T_LEC) mode drive ; - a step (E54) to deactivate reader mode if the timer is outdated.

3. Method for transferring data from a mobile terminal (TM_E) according to one of the preceding claims, characterized in that the IBC mode or NFC is selected (E50) via a human-machine interface (HMI) of the mobile terminal.

4. Method for transferring data from a mobile terminal (TM_E) according to one of the preceding claims, characterized in that a type The IBC application (IBC-S) is selected (E51) via an interface human-machine interface of the mobile terminal.

5. A method according to any one of the preceding claims, characterized in that that the said invitation message (WUP_IBC) contains one or more data from: - a risk factor in establishing the return channel; - an IBC application type (AFI, Type, IBC-S); - a type of return channel (BT, Wi-Fi); - a service parameter,

6. Mobile terminal data transfer device (TM_E) equipped of a near field communication (NFC) module, said device capable of positioning the mobile terminal in NFC mode (M_NFC) or in IBC mode (M_IBC) to perform trans- contactless actions, characterized in that it is configured to put in work at the mobile terminal level: - select (E50) NFC mode (M_NFC) or IBC mode (M_IBC); - position (E52) the mobile terminal in NFC reader mode; - issue (E55) an invitation message (WUP_IBC) according to a type of Near field communication IBC (NFC-IBC); - disable (E56) NFC reader mode; - receive (E57) a peering message (ACK_IBC) on a channel of return (CR) distinct from the near-field channel; - transfer (E58) the data over the return channel (IBC).

7. Method for receiving data on a mobile terminal (TM_R) equipped of a near field communication (NFC) module, said terminal mobile being capable of positioning itself in an IBC mode (M_IBC) for to carry out contactless transactions, the process being characterized in that that it includes the following steps on the mobile terminal (TM_R): - position (E30) the mobile terminal (TM_R) in IBC mode (M_IBC); - receive (E31) an invitation message (WUP_IBC) according to a type of Near field communication IBC (NFC-IBC); - transmit (E32) a peering message (ACK_IBC) on a channel of distinct return of the channel in the near field; - receive (E58) data on the return channel (IBC).

8. Method for receiving data on a mobile terminal according to claim- indication 7, characterized in that the IBC mode is selected (E30) via a human-machine interface (HMI) for the mobile terminal (TM_R).

9. Method for receiving data on a mobile terminal according to claim- indication 7 or 8, characterized in that a type of IBC application (IBC-S) is selected (E30) via a human-machine interface of the terminal mobile el / or received in the invitation message.

10. Method of receiving data on a mobile terminal according to one of the claims 7 to 9, characterized in that the type of return channel is received in the invitation message (WUP_IBC).

11. Mobile terminal data receiving device (TM_R) equipped of a near field communication (NFC) module, said device being able to position the mobile terminal in an IBC mode (M_IBC) to carry out contactless transactions, characterized in that it is configured to implement at the mobile terminal level: - position (E30) the mobile terminal (TM_R) in IBC mode (M_IBC); - receive (E31) an invitation message (WUP_IBC) according to a type of Near field communication IBC (NFC-IBC); - transmit (E32) a peering message (ACK_IBC) on a channel of distinct return of the channel in the near field; - receive (E58) data on the return channel (IBC).

12. System comprising a transmitting mobile terminal (TM_E) equipped with a a transfer device according to claim 6 and a mobile terminal receiver (TM_R) equipped with a receiving device according to the claim- indication 11, characterized in that the data transfer is triggered when the transmitting mobile terminal, positioned in NFC mode, enters proximity to the user's body of the receiving mobile terminal.

13. | System comprising a transmitting mobile terminal (TM_E) equipped with a transfer device according to claim 6 and a mobile terminal receiver (TM_R) equipped with a receiving device according to the claim- indication 11, characterized in that the data transfer is triggered when the body of the user of the transmitting mobile terminal is positioned In IBC mode, it enters the vicinity of the terminal user's body. mobile receiver.

14. Computer program capable of being run on a terminal mobile transmitter equipped with a transfer device according to the resv- Indication 6, the program includes code instructions which, when the program is executed by a processor, performs the steps of the process defined according to any one of claims 1 to 5.

15. Computer program capable of being run on a terminal mobile receiver equipped with a receiving device according to the resv- Indication 11, the program includes code instructions which, when the program is executed by a processor, performs the steps of the process defined according to any one of claims 7 to 10.