WO2017174519A1 - Procédé, puce et système pour détecter un échec ou un abandon dans un contexte pdp ou une connexion pdn eps - Google Patents

Procédé, puce et système pour détecter un échec ou un abandon dans un contexte pdp ou une connexion pdn eps Download PDF

Info

Publication number
WO2017174519A1
WO2017174519A1 PCT/EP2017/057872 EP2017057872W WO2017174519A1 WO 2017174519 A1 WO2017174519 A1 WO 2017174519A1 EP 2017057872 W EP2017057872 W EP 2017057872W WO 2017174519 A1 WO2017174519 A1 WO 2017174519A1
Authority
WO
WIPO (PCT)
Prior art keywords
pdp context
pdn connection
chip
eps pdn
type
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/EP2017/057872
Other languages
English (en)
Inventor
Andrei Marian HAGIU
Nieves GARCIA DIEZ
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Thales DIS France SA
Original Assignee
Gemalto SA
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Gemalto SA filed Critical Gemalto SA
Publication of WO2017174519A1 publication Critical patent/WO2017174519A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/60—Subscription-based services using application servers or record carriers, e.g. SIM application toolkits
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/18—Management of setup rejection or failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/183—Processing at user equipment or user record carrier
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/20—Transfer of user or subscriber data
    • H04W8/205—Transfer to or from user equipment or user record carrier

Definitions

  • the invention relates generally to a method for detecting a failure or a drop in a Packet Data Protocol (or PDP) context or an Evolved Packet System (or EPS) Packet Data Network (or PDN) connection.
  • PDP Packet Data Protocol
  • EPS Evolved Packet System
  • PDN Packet Data Network
  • the invention also pertains to a chip for detecting a failure or a drop in a PDP context or an EPS PDN connection.
  • the invention relates to a system for detecting a failure or a drop in a PDP context or an EPS PDN connection as well.
  • a chip may be either embedded, such as an embedded Universal Integrated Circuit Card (or eUICC) within a device, or removable, such as a chip included within a smart card termed Subscriber Identity Module (or SIM) type card or the like, as a Secure Element (or SE), from a chip host device.
  • eUICC embedded Universal Integrated Circuit Card
  • SIM Subscriber Identity Module
  • SE Secure Element
  • an SE is a smart object that includes a chip that protects access to stored data and is intended to communicate data with an SE host device, like e.g. a mobile (tele)phone, a Machine to Machine (or M2M) or an Internet of Things (or loT) device.
  • an SE host device like e.g. a mobile (tele)phone, a Machine to Machine (or M2M) or an Internet of Things (or loT) device.
  • a mobile phone is able to open a PDP context or an EPS PDN connection.
  • PDP context or an EPS PDN connection as a tunnel to a Packet Data Service (or PDS) network, is opened, the phone accesses, through a connected mobile (radio-communication) network, the PDS network.
  • PDS Packet Data Service
  • the phone or the mobile network may fail or drop a PDP context or an EPS PDN connection and therefore loose a data connectivity to the PDS network.
  • the phone or the mobile network may fail or drop a PDP context or an EPS PDN connection and therefore loose a data connectivity to the PDS network.
  • the data connectivity is lost, i.e. not established (or failed) or dropped, there is a huge negative impact on a user experience.
  • the invention proposes a solution for satisfying the just herein above specified need by providing a method for detecting a failure or a drop in a PDP context or an EPS PDN connection.
  • a chip is incorporated within or coupled to a device.
  • the method comprises the following steps.
  • the chip receives from the device a call control PDP context activation type event or a call control EPS PDN connection activation type event.
  • the chip sends to the device an Open Channel type command.
  • the chip receives from the device a Terminal Response type response.
  • the chip detects whether the device does or does not fail in activating a PDP context or an EPS PDN connection. If the Terminal Response type response includes at least one predetermined error, then the chip detects that the device has failed in activating a PDP context or an EPS PDN connection. If the Terminal Response type response does not include at least one predetermined error, then the chip detects that the device has succeeded in activating a PDP context or an EPS PDN connection.
  • the chip detects that the device has succeeded in activating the PDP context or the EPS PDN connection, then the chip receives from the device a channel status type event. The chip detects whether the PDP context or the EPS PDN connection has or has not been dropped. If the channel status type event matches at least one predetermined channel status relating to a dropped PDP context or a dropped EPS PDN connection, then the chip detects that the PDP context or the EPS PDN connection has been dropped.
  • the principle of the invention consists in that a chip that cooperates with a device receives, firstly, from the device a call control PDP context activation type event or a call control EPS PDN connection activation type event. Then, the chip sends to the device an Open Channel (or OC) type command. Once the OC type command is sent, the chip determines, based on a Terminal Response (or TR) type event to be received from the device, whether the device has or has not failed in activating a PDP context or an EPS PDN connection. If the received TR type response includes or not one or several predefined errors, then the chip detects that the device has failed or succeeded in activating a PDP context or an EPS PDN connection respectively. If the PDP context or the EPS PDN connection has been activated, then the chip determines, based on a Channel Status (or CS) type event to be received from the device, whether the PDP context or the EPS PDN connection has or has not been dropped.
  • TR Terminal Response
  • PDN connection at a chip side is a reception of a call control PDP context activation type event or a call control EPS PDN connection activation type event.
  • the invention method is automatically implemented.
  • a user of the chip that implements the invention method is not involved to detect a possible failure or drop in a PDP context or an EPS PDN connection.
  • the invention method is therefore convenient for the user.
  • the user has neither to go to an office of a Mobile Network Operator (or MNO), a Mobile Network Virtual
  • MVNO Mobility Management Entity
  • the invention method allows determining, in a reliable manner, a failure or a drop in a PDP context or an EPS PDN connection.
  • the chip may also detect one or several reasons why the failure or the drop has occurred. The chip may then let re-configure or re-configure the device by using a right configuration parameter(s) for configuring an access to a Packet Data Service (or
  • PDS PDS type network that is(are) loaded from a remote server or the chip.
  • Such a device re-configuration operation with the right configuration parameter(s) may be launched immediately and automatically after a detection of a failure or a drop in a PDP context or an EPS PDN connection.
  • the proposed invention solution allows being able to quickly enhance a user experience who benefits, after a device (re-)configuration operation, from an access to the Packet Data Services.
  • the invention is a chip for detecting a failure or a drop in a PDP context or an EPS PDN connection.
  • the chip is likely to be incorporated within or coupled to a device.
  • the chip is configured to receive a call control PDP context activation type event or a call control EPS PDN connection activation type event, send an Open
  • the Chip is configured to detect, if the Terminal Response type response includes at least one predetermined error, that the device has failed in activating a PDP context or an EPS PDN connection, detect, if the Terminal Response type response does not include at least one predetermined error, that the device has succeeded in activating a PDP context or an EPS PDN connection.
  • the chip is configured to receive, if the chip detects that the device has succeeded in activating the PDP context or the EPS PDN connection, a channel status type event and detect whether the PDP context or the EPS PDN connection has or has not been dropped, detect, if the channel status type event matches at least one predetermined channel status relating to a dropped PDP context or a dropped EPS PDN connection, that the PDP context or the EPS PDN connection has been dropped.
  • the chip may be fixed to or removable from a host device.
  • the chip is preferably included within an SE.
  • the invention does not impose any constraint as to a kind of the SE type.
  • a removable SE it may be a SIM type card, a Machine Identification Module (or
  • MIM Secure Removable Module
  • SRM Secure Removable Module
  • smart dongle of the USB (acronym for "Universal Serial Bus") type a (micro-) Secure Digital (or SD) type card or a Multi-Media type Card (or MMC) or any format card (or another medium) to be coupled or connected to a chip host device.
  • USB Universal Serial Bus
  • micro- Secure Digital
  • MMC Multi-Media type Card
  • the chip host device may be constituted by any electronic device, like e.g. a user terminal, a terminal or a M2M or loT device, comprising data processing means, data storing means and one or several Input/Output (or I/O) communication interfaces.
  • the invention is a system for detecting a failure or a drop in a PDP context or an EPS PDN connection.
  • the system comprises a device and a chip.
  • the chip is incorporated within or coupled to the device.
  • the chip is configured to receive from the device a call control PDP context activation type event or a call control EPS PDN connection activation type event, send to the device an Open Channel type command, receive from the device a Terminal Response type response, detect whether the device does or does not fail in activating a PDP context or an EPS PDN connection, detect, if the Terminal Response type response includes at least one predetermined error, that the device has failed in activating a PDP context or an EPS PDN connection, detect, if the Terminal Response type response does not include at least one predetermined error, that the device has succeeded in activating a PDP context or an EPS PDN connection, receive, if the chip detects that the device has succeeded in activating the PDP context or the EPS PDN connection, from the device a channel status type event and detect whether the PDP context or the EPS PDN connection has or has not been dropped.
  • the chip is configured to detect,
  • FIG. 1 is a simplified diagram of a terminal equipment, a (mobile) network and a PDS type network, the terminal equipment comprising a phone and a chip being arranged to detect a failure or a drop in a PDP context with possibly a reason(s) why the failure or the drop occurs, according to the invention; and
  • FIG. 2 illustrates an example of a flow of messages exchanged between notably the phone and the chip of figure 1 , so that the chip detects whether the phone does or does not fail in activating a PDP context, and if successful, then detect whether the PDP context has or has not been dropped.
  • a chip like e.g. an eUICC, as a chip incorporated, possibly in a removable manner, on a Printed Circuit Board (or PCB) of a terminal, as a chip host device.
  • a chip like e.g. an eUICC, as a chip incorporated, possibly in a removable manner, on a Printed Circuit Board (or PCB) of a terminal, as a chip host device.
  • PCB Printed Circuit Board
  • the chip may also incorporate at least part of the terminal component(s), like e.g. a baseband processor, an application processor and/or other electronic component(s).
  • the chip may be a Trusted Execution Environment (or TEE), as a secure area of a terminal processor and a secured runtime environment.
  • TEE Trusted Execution Environment
  • the chip is preferably included within an SE.
  • the SE may nevertheless have different form factors.
  • the chip may be carried by a medium, such as a smart card or a dongle, like e.g. a USB type dongle.
  • a medium such as a smart card or a dongle, like e.g. a USB type dongle.
  • Figure 1 shows schematically a Terminal Equipment (or TE) 10, a visited mobile network 16 and a PDS network 18.
  • Terminal Equipment or TE
  • FIG. 1 shows schematically a Terminal Equipment (or TE) 10, a visited mobile network 16 and a PDS network 18.
  • the TE 10 includes a chip 12 and a mobile phone 14, as a (user) terminal and a chip host device.
  • the chip 12, the mobile phone 14, the visited mobile network 16 and the PDS network 18 are termed infra the SE 12, the host 14, the visited network 16 and the PDS 18 respectively.
  • the TE 10 is under a radio coverage of the network 16.
  • a TE 10 user benefits preferably from one or several subscriptions to access the network 16.
  • the (user) terminal, the terminal or a machine in an M2M as a terminal may be fixed (i.e. not mobile) or mobile.
  • the (user) terminal may be a Personal Digital Assistant (or PDA), a vehicle, a personal digital Assistant (or PDA), a personal digital Assistant (or PDA), a vehicle, a personal digital Assistant (or PDA), a personal digital Assistant (or PDA), a vehicle, a personal digital Assistant (or PDA), a personal digital Assistant (or PDA), a vehicle, a personal digital Assistant (or PDA), a personal digital Assistant (or PDA), a vehicle,
  • Point Of Sale an electricity meter, a water meter, a gas meter, any meter, a set-top box, a tablet computer, a desktop computer, a laptop computer, a video player, an audio player, a portable Television (or TV), a media-player, a game console, a netbook, an electronic mobile equipment or accessory (e.g.: glasses, a watch or a jewel) or an loT device.
  • POS Point Of Sale
  • an electricity meter a water meter, a gas meter, any meter, a set-top box, a tablet computer, a desktop computer, a laptop computer, a video player, an audio player, a portable Television (or TV), a media-player, a game console, a netbook, an electronic mobile equipment or accessory (e.g.: glasses, a watch or a jewel) or an loT device.
  • the user terminal or the terminal may be any other computer device including means for processing data, comprising (or being connected to) wireless communication means for exchanging data with outside, and comprising (or being connected to) means for storing data.
  • wireless communication means denotes notably that the communication means communicates via one or several Long Range (or LR) Radio-Frequency (or RF) links.
  • the LR RF may be fixed at several hundreds of MHz, for instance, around 850, 900, 1800, 1900 and/or 2100 MHz.
  • the host 14 is used for accessing one or several mobile (radio-communication) networks, namely at least the network 16.
  • the host 14 is used for accessing, through the (mobile) network(s) 16, the PDS
  • the host 14 stores one or several configuration parameters, among which one or several configuration parameters may be selected by the host 14 or the user.
  • the host 14 is coupled or connected, through a bi-directional link 13, to the SE 12, as a chip embedded within (or coupled to) the host 14.
  • the SE 12 is under control of a host 14 (micro)processor(s) (or (micro)controler(s)) (not represented), as data processing means.
  • a host 14 microprocessor(s) (or (micro)controler(s)) (not represented), as data processing means.
  • the SE 12 is preferably associated with or tied to a Network Access Server (or NAS) (not represented).
  • NAS Network Access Server
  • the NAS is included within (or connected to) the network 16.
  • the SE 12 belongs to a user, as a subscriber to a wireless service(s).
  • the SE 12 includes a (micro)processor(s) 122, as data processing means, a memory(ies) 124, as data storing means, and one or several I/O interfaces 126 that are internally all connected, through an internal bidirectional data bus 1 23, to each other.
  • a (micro)processor(s) 122 as data processing means
  • a memory(ies) 124 as data storing means
  • I/O interfaces 126 that are internally all connected, through an internal bidirectional data bus 1 23, to each other.
  • the I/O interface(s) 126 allow(s) communicating data from the internal SE 12 components to the chip exterior and conversely.
  • the memory 124 stores an Operating System (or OS).
  • OS Operating System
  • the memory 124 stores preferably one or several SIM type applications.
  • the SIM type application(s) allow(s) the host 14 to identify and authenticate to one or several mobile networks, like e.g. the network 16.
  • the memory 124 stores, preferably in a secure manner, preferably a plurality of sets of data relating, each, to a subscription, as a wireless service(s).
  • Each set of data relating to one subscription includes preferably:
  • an IMSI as a subscriber and a (service) subscription identifier for accessing a mobile network
  • Ki a Key Ki, as a Network Authentication Key (or NAK), allowing to authenticate the concerned subscriber to the concerned mobile network;
  • Milenage (or the like), as a network authentication algorithm, allowing to authenticate the concerned subscriber to the concerned mobile network; - a file system including one or several Elementary Files (or EF);
  • - one or several security keys like e.g. a key(s) for encrypting/decrypting data and/or a key(s) for signing data, as secret data; and/or
  • one or several credentials like e.g. a user name and/or an IDentifier (or ID) of the subscriber, as data relating to the user.
  • the memory 124 may store data relating to a Uniform Resource Identifier (or URI), a Uniform Resource Locator (or URL), an Internet Protocol (or IP) address and/or other data relating to an external entity to be addressed, like e.g. a remote server accessible within or through the network 16 and the PDS 18.
  • a Uniform Resource Identifier or URI
  • a Uniform Resource Locator or URL
  • IP Internet Protocol
  • the processor 122 processes, controls and communicates internally data with all the other components incorporated within the SE 12 and, through the I/O interface(s) 126, with the chip exterior.
  • the processor 122 executes or runs one or several applications, like e.g. an application for detecting a failure/drop in a PDP context (and/or a PDN connection) that is termed applet (in the Java programming language) infra.
  • applications like e.g. an application for detecting a failure/drop in a PDP context (and/or a PDN connection) that is termed applet (in the Java programming language) infra.
  • the applet is a small size applet, like e.g. between 1 kb and 3 or 4 kb.
  • the SE 12, and more exactly the applet is configured to detect (from the SE 12) a failure or a drop in a PDP context (and/or a PDN connection), in order to have an image of the user's data availability.
  • the SE 12 is triggered when the SE 12 receives a Call Control (or CC) PDP context activation type event (and/or a CC PDN connection activation type event).
  • the SE 12 is previously preferably registered to the host 14, so as to receive such a CC PDP context activation type event (and/or a CC PDN connection activation type event) by providing the host 14 with an event set, like e.g. CC, Channel Status (or CS), as an event(s).
  • an event set like e.g. CC, Channel Status (or CS), as an event(s).
  • the CC PDP context activation type event (and/or a CC PDN connection activation type event) may comprise or be accompanied with one or several configuration parameters for configuring an access to the PDS 18.
  • the SE 12 and more exactly the applet stores a (current) value of the configuration parameter(s) received from the host 14, when applicable.
  • the SE 12 stores a previous value of the configuration parameter(s) received from the host 14.
  • the SE 12 is preferably adapted to detect whether the (last received and stored) value of the configuration parameter(s) that may be associated with an unsuccessful access to the PDS 18 is or is not different from the (stored) previous value of the configuration parameter(s) that may be associated with a successful access to the PDS 18. If the current and the previous value are different from each other, then such a change of the value of the configuration parameter(s) may be a reason for the PDS access failure.
  • the processor 122 executes, in a preferred manner, one or several security functions.
  • the security functions include preferably a user authentication process to be used prior to continuing to access the SE 12, notably at a boot, i.e. a power on, of the SE 12.
  • a user authentication process to be used prior to continuing to access the SE 12, notably at a boot, i.e. a power on, of the SE 12.
  • the user has to provide a Personal Identity Number (or PIN) or biometric data, as user reference data, that is stored, preferably in a secure manner, within the memory 124.
  • biometric data it may include one or several fingerprints, one or several iris prints, one or several voiceprints relating to one or several authorized users.
  • the processor 122 is preferably able to initiate an action(s), in order to interact directly with the outside world, in an independent manner of the host 14.
  • Such a capacity of interaction at the initiative of the SE 12 is also known as being a proactive capacity in which the SE 12 plays a role of a master while the SE host device plays a role of a slave.
  • the SE 12 is able to use SIM
  • ToolKit (or STK) type commands, as proactive commands.
  • the SE 12 is thus able to send, at its own initiative, through the host 14 (to any device, like e.g. a remote server, connected to the host 14) or to the host 14, a message by using a proactive command, like e.g. an "Open Channel (or OC) type command", for establishing a connection, like e.g. "create a PDP context” (and/or a PDN connection).
  • a proactive command like e.g. an "Open Channel (or OC) type command
  • establishing a connection like e.g. "create a PDP context" (and/or a PDN connection).
  • the OC type command may include or be accompanied with a (current) configuration parameter(s) that is(are) previously provided by the host 14 through a CC
  • PDP context activation type event (and/or a CC PDN connection activation type event).
  • the OC type command like e.g. a Bearer Independent Protocol (or BIP) OC, an
  • OC related to PDS bearer or an "OC related to Default (network) Bearer” command, relates to a PDS bearer.
  • the OC type command is used in a Transmission Control Protocol (or TCP) mode or preferably in a User Datagram Protocol (or UDP), so as to save battery energy consumption (and thus preserve e.g. the host 14 battery life).
  • TCP Transmission Control Protocol
  • UDP User Datagram Protocol
  • the memory 124 stores an (invention) applet that the processor 122 executes.
  • the applet allows carrying out a detection of a failure of an access (i.e. a PDP context (and/or a PDN connection)) attempt to the PDS 18 with possibly a current configuration parameter(s) registered within the host 14 after a PDS access request initiated by the SE 12.
  • a failure of an access i.e. a PDP context (and/or a PDN connection)
  • PDS 18 with possibly a current configuration parameter(s) registered within the host 14 after a PDS access request initiated by the SE 12.
  • the PDS access failure is preferably detected by a Terminal Response (or TR) type event and/or an Error Status (or ES) type word to be received from the host 14.
  • TR Terminal Response
  • ES Error Status
  • the applet may allow providing one or several reasons for the PDS access failure.
  • the reason may be that the configuration parameter(s) that is(are) currently stored or absent at the host 14 is(are) not the right one(s), i.e. is(are) corrupted, so as to access the PDS 18.
  • the applet requests preferably the host 14 to access from the host 14 to the PDS 18 by using a particular command that forces the host 14 to use the configuration parameter(s) that the host 14 stores and further analyses whether the SE 12 does or does not receive from the host 14 a corresponding access failure error.
  • the SE 12 may have found out a presence of a corrupted configuration parameter(s), i.e. an absence of any stored configuration parameter(s) or an erroneous configuration parameter(s).
  • the applet detects that the host 14 has succeeded in establishing an access to the PDS 18, i.e. by activating a PDP context (and/or an EPS PDN connection), then the applet allows carrying out a detection of a drop of the access (i.e. the PDP context (and/or the PDN connection)) to the PDS 18 after the PDS access request initiated by the SE 12.
  • the PDS access drop is preferably detected by a CS type event to be received from the host 14.
  • the applet may allow providing one or several reasons for the drop.
  • the reason for the PDS access drop may be provided by the CS type event that includes or is accompanied with a provided reason, like e.g. "Link dropped".
  • the PDP context (and/or the PDN connection)) may have been dropped due to a network 16 issue, a host 14 issue, a PDS 18 issue, a change of the PDS 18 configuration parameter(s), like e.g. an Access Point Name (or APN), and/or a change of the network 16 access conditions, like e.g. a bad quality of (received) signal .
  • the SE 12 may thus have found out a presence of a corrupted configuration parameter(s), i.e. an absence of any stored configuration parameter(s) or an erroneous configuration parameter(s).
  • the SE 12 is preferably able to let the host 14 recover the right configuration parameter(s) relating to the concerned host 14 and that allow(s) accessing, through the network(s) 16, the PDS 18.
  • the SE 12 is incorporated or coupled to the host 14, as an SE host device.
  • the host 14 comprises the chip 12 that is removable from the host 14.
  • the host I/O interfaces include one or several I/O interfaces for exchanging data with the SE 12.
  • the host I/O interface with the SE 12 may be an International Organization for Standardization (or ISO) 7816 interface, as a contact interface, when the SE 12 is inserted, in a removable manner, within the host 14.
  • ISO International Organization for Standardization
  • the host I/O interface with the SE 12 is connected to or includes a contact-less interface.
  • the host 14 is connected to or includes means for communicating data while using preferably a Short Range (or SR) RF link.
  • the SR RF link may be related to any technology that allows the host 14 to exchange data, through a so-termed contact-less link with the SE 12.
  • the SR RF may be fixed at 13,56 MHz and related to a Near Field Communication (or NFC) type technology, or ISO 14443, as a contact-less technology.
  • NFC Near Field Communication
  • the host 14 includes data processing means, such as one (micro)processor (not represented), data storing means (not represented), as a phone memory, and one or several I/O interfaces that are linked all together through a control and data bus (not represented).
  • data processing means such as one (micro)processor (not represented), data storing means (not represented), as a phone memory, and one or several I/O interfaces that are linked all together through a control and data bus (not represented).
  • the phone 14 plays, in a preferential manner, a role of a modulator-demodulator
  • the host memory may comprise one or several memories including one or several volatile memories and one or several non-volatile memories.
  • the host memory be it either volatile or non volatile, stores, at least in a temporary manner, data relating to a configuration parameter(s) that allow(s) configuring an access, through a connected mobile network(s) 16, to the PDS 18.
  • the configuration parameter(s) may include one or several user names, one or several passwords, one or several user credentials, one or several APNs, one or several URLs, one or several IP addresses, one or several address types, like e.g. IPv4 or IPv6, and/or one or several Quality of Service (or QoS).
  • the configuration parameter(s) may include one or several user names, one or several passwords, one or several user credentials, one or several APNs, one or several URLs, one or several IP addresses, one or several address types, like e.g. IPv4 or IPv6, and/or one or several Quality of Service (or QoS).
  • the APN as a configuration parameter, is the name of a gateway between a mobile network 16 and a computer network 18.
  • the APN is used by a terminal device, like e.g., the phone 14, to open a PDP context (and/or a PDN connection), through at least one gateway, as described infra in more details.
  • An APN structure comprises an identifier of a network, like e.g a network identifier, which the gateway is connected to.
  • the APN structure may comprise the service, like e.g., a Wireless Application Protocol (or WAP) server or a Multimedia
  • MMS Messaging Service
  • the APN structure may comprise an identifier of an MNO, like e.g., mnc ⁇ MNC>.mcc ⁇ MCC>.gprs, in which mnc is a Mobile Network Code and mcc is
  • the APN may be absent, further to e.g., a previous erasure, or present, while being not right within the host memory, and therefore corrupted.
  • the configuration parameter stored within the host 14 memory does not allow accessing, through a connected mobile network(s) 16, the PDS 18.
  • the host memory may be constituted by one or several EEPROMs (acronym for "Electrically Erasable Programmable Read-Only Memory"), one or several ROMs
  • the host memory stores e.g. an International Mobile Equipment Identity (or IMEI) and/or an email address, as an identifier(s) relating to the host 14.
  • IMEI International Mobile Equipment Identity
  • email address e.g. an identifier(s) relating to the host 14.
  • the host memory stores an OS and one or several applications.
  • the host 14 includes a display screen 142 and a keyboard 144, as Man Machine Interface (or MMI).
  • MMI Man Machine Interface
  • the host 14 carries out the following operations: - a modulation of an analogical carrier signal to encode digital information to be transmitted, over an antenna 146, to one (or several) network(s) 16; and
  • the antenna 146 allows communicating data, Over-The-Air (or OTA), through an
  • the network 16 is a visited network.
  • the network 16 is related to a home or foreign country with respect to the subscriber.
  • the network 16 includes a base station 162 (or the like) that is used for communicating with an LR RF enabled device(s), like e.g. the host 14.
  • the base station 162 covers at least in part a geographical area in which the host 14 is located.
  • the network 16 includes a Gateway (or GW) 164.
  • the network 16 may be a Gateway GPRS Support Node (or GGSN) in a second Generation (or 2G) and a third Generation (or 3G) type network, a Mobility Management Entity (or MME) in a fourth Generation (or 4G) type network or any other network entity connected to the PDS 18.
  • GGSN Gateway GPRS Support Node
  • 3G Third Generation
  • MME Mobility Management Entity
  • 4G fourth Generation
  • the GW 164 is connected, indirectly through internal network links 163, to the base station 162.
  • the GW 164 is connected, through a wire link(s) 17, to the PDS 18.
  • the base station 162 is also connected, through network link(s), to a (remote) server (not represented).
  • the server is hosted by a computer with data processing means and data storing means.
  • the server allows getting a right configuration parameter(s), like e.g. an APN, for configuring an access (from the host 14) to the PDS 18.
  • a right configuration parameter(s) like e.g. an APN
  • the server accesses a database stored in a memory (not represented) that is present within or connected to the server.
  • the database includes a correspondence table that includes, for at least one identifier, like e.g. an IMEI, of an SE host device, an associated configuration parameter(s), like e.g. an APN, to be used by the concerned SE host device, in order to access PDS 18.
  • a correspondence table that includes, for at least one identifier, like e.g. an IMEI, of an SE host device, an associated configuration parameter(s), like e.g. an APN, to be used by the concerned SE host device, in order to access PDS 18.
  • the associated configuration parameter(s) may depend on at least the host 14. If the (right) configuration parameter, like e.g. APN1 , to be injected into the SE host device is related to the network 16 and, if the TE 10 is not under a radio-coverage of the network that is associated with the (current) configuration parameter, then the TE 10, once (re-)configured, gets access, through the (right) gateway relating to the network 16, the PDS 18.
  • the (right) configuration parameter like e.g. APN1
  • the server is able to restore a corresponding right configuration parameter(s) to be stored within an SE host device, like e.g. the host 14, and to launch preferably a PDS access request once the right configuration parameter(s) is(are) restored.
  • the server is thus able to provide a requesting device, like e.g. the SE 12, that identifies at least its host by using an identifier(s), like e.g. an IMEI, a Mobile Station International Subscriber Directory Number (or MSISDN) and/or other input(s), so as to get a corresponding predetermined configuration parameter(s), as a corresponding output(s).
  • a requesting device like e.g. the SE 12
  • an identifier(s) like e.g. an IMEI, a Mobile Station International Subscriber Directory Number (or MSISDN) and/or other input(s)
  • the network 16 has its own APN denoted APN1 , as a name of a gateway to the PDS 18, and is specific to only the network 16.
  • Figure 2 depicts an exemplary embodiment of a message flow 20 that involves the SE 12 and the host 14, so that the SE 12 detects a failure or a drop in a PDP context.
  • the SE 12 instead of a PDP context, the SE 12 detects a failure or a drop in an EPS PDN connection by using, instead of a CC PDP context activation type event, a CC EPS PDN connection activation type event while the other messages of the message flow 20 remain the same by referring to the EPS PDN connection instead of the PDP context.
  • the host 14 has previously, in a successful manner, accessed the PDN 18 by using an APN1 , as a previous value of the configuration parameter, that the host 14 stores.
  • the SE 12 further to a successful access to the PDS 18, also stores the APN1 .
  • an APN2 (different from the APN1 ) relating to the network 16 constitutes a (right) single configuration parameter to be used to access, over the network 16, the PDS 18.
  • the host 14 user browses on the host browser and requests thus an access to the PDS 18.
  • the host 14 initiates a PDS connection procedure, so as to establish a PDP context with the network 16.
  • the SE 12 receives from the host 14 a CC PDP context activation type event 22.
  • the CC PDP context activation type event 22 includes (or is accompanied with) an APN3, as a value of one configuration parameter for configuring an access to the PDS 18.
  • the APN3 is different from the APN1 and the APN2.
  • the SE 12 applet determines 24 whether the CC PDP context activation type event 22 does or does not include (or is or is not accompanied with) a configuration parameter(s).
  • the SE 12 applet collects and stores 26 at least temporarily (in a RAM or the like) the (received) APN3 configuration parameter(s) to be used to send an OC type command.
  • the SE 12 applet does not store any configuration parameter(s) or stores temporary data, like e.g. as "length" 0 and goes to the next step 28.
  • the SE 12 transmits preferably to the host 14 a message (not represented), like e.g. "91 XX", for informing the host 14 that the SE 12 has well received the CC PDP context activation type event 22.
  • a message (not represented), like e.g. "91 XX"
  • the host 14 launches an attachment request procedure to the network 16 and, when successful, i.e. identified and preferably authenticated to the network 16, the host 14 launches a PDP context activation procedure.
  • the SE 12 receives preferably from the host 14 a message (not represented), like e.g. "Fetch", for informing the SE 12 that the SE 12 may send a message to the host 14.
  • a message not represented, like e.g. "Fetch”
  • the SE 12 sends to the host 14 an OC type command 28 relating to the PDS 18 bearer.
  • the OC type command is compliant preferably with standard technical specifications, like e.g. the 3GPP TS 31 .1 1 1 (such as the V12.5.0 (September 2014)) and/or ETSI TS 102.223 (such as the V12.0.0 (May 2014)).
  • standard technical specifications like e.g. the 3GPP TS 31 .1 1 1 (such as the V12.5.0 (September 2014)) and/or ETSI TS 102.223 (such as the V12.0.0 (May 2014)).
  • the OC type command 28 includes (or is accompanied with) preferably the APN3, as the value of the configuration parameter(s) that has(have) been received from the host 14 along with the CC PDP context activation type event 22.
  • the host 14 gets (not represented) the stored APN3, as the value of the received configuration parameter(s), when present in the received OC type command 28.
  • the host 14 sends to the GW 164 a Signalling System Number 7 (or SS7) type message (or the like) including a request, like e.g. "create PDP context", for establishing a connection to the PDS 18 and the stored APN3, when applicable.
  • a Signalling System Number 7 or SS7 type message (or the like) including a request, like e.g. "create PDP context", for establishing a connection to the PDS 18 and the stored APN3, when applicable.
  • the SE 12 receives from the host 14 a TR type response 210.
  • the TR type response is compliant preferably with standard technical specifications, like e.g. the 3GPP TS 31 .1 1 1 (such as the V12.5.0 (September 2014)) and/or ETSI TS 102.223 (such as the V12.0.0 (May 2014)).
  • standard technical specifications like e.g. the 3GPP TS 31 .1 1 1 (such as the V12.5.0 (September 2014)) and/or ETSI TS 102.223 (such as the V12.0.0 (May 2014)).
  • the TR type response 210 includes preferably an identifier relating to the channel that the host 14 attempts to open further to a reception of the OC type command 28 by the host 14.
  • the TR type response 210 includes (or is accompanied with) additional data.
  • the TR type response 210 provides the SE 12 with information relating to a success or a failure in activating a PDP context by using the configuration parameter(s) that has(have) been sent to the host 14 with the OC type command.
  • the SE 12 applet detects 212 whether the host 14 has or has not failed in activating a PDP context, i.e. establishing an access to the PDS 18.
  • TR type response 210 does not include (or is not accompanied with) one or several predetermined errors, like e.g. a "Command performed successfully", then the SE 12 applet detects that the host 14 has succeeded in activating a PDP context and goes to a next step 216.
  • predetermined errors like e.g. a "Command performed successfully
  • the SE 12 applet detects 214 that the host 14 has failed in activating a PDP context.
  • the PDS access failure may be a connection or link that has not been established, the PDP context is not created and/or the like.
  • the TR type response 210 may further include (or be accompanied with) additional information, like e.g. a reason or a cause of the concerned error(s), like e.g. "Security error (unsuccessful authentication)".
  • the SE 12 detects (not represented) whether the current value APN3 is or is not different from the stored previous value APN1 . To do this, the SE 12 compares the current value to the stored previous value (associated with a successful attempt to access the PDS 18).
  • the reason why such a PDS access failure occurs may be a change of the value of the APN (since there was a "switch" from the APN1 to APN3).
  • a right configuration parameter(s), like e.g . the APN2, may be recovered by the host 14 e.g. at the SE 12 initiative.
  • the host 14 stores the APN2.
  • the SE 12 (or another device, like e.g. a server) triggers a restoration (not represented) of the right APN2 into the host 14 either from a remote server or the SE 12, so as to access successfully the PDS 18 after an additional attempt to create a PDP context.
  • the SE 12 receives from the host 14 another CC PDP context activation type event.
  • the CC PDP context activation type event includes preferably the APN2.
  • the SE 12 applet determines whether the CC PDP context activation type event does or does not include a configuration parameter(s). If the CC PDP context activation type event includes the APN2, as one configuration parameter, then the SE 12 applet collects and stores at least temporarily the APN2 configuration parameter(s) to be used to send another OC type command.
  • the SE 12 sends to the host 14 an OC type command relating to the PDS 18 bearer.
  • the OC type command includes preferably the APN2, as the value of the configuration parameter(s) that has(have) been received from the host 14 along with the CC PDP context activation type event.
  • the host 14 gets the stored APN2, as the value of the received configuration parameter(s).
  • the host 14 sends to the GW 1 64 a SS7 type message (or the like) including a request for establishing a connection to the PDS 18 and the stored APN2, when applicable.
  • the SE 12 receives from the host 14 a TR type response.
  • the TR type response includes preferably an identifier relating to the channel that the host 14 attempts to open further to a reception of the OC type command by the host 14.
  • the TR type response provides the SE 12 with information relating to a success, like e.g.
  • the SE 12 applet detects whether the host 14 has or has not failed in activating a PDP context, i.e. establishing an access to the PDS 18, based on the TR type response.
  • the SE applet detects that the host 14 has succeeded in activating a PDP context and stores the APN2, as the value of the configuration parameter associated with a successful attempt to access the PDS 18.
  • the SE 12 waits until receiving from the host 14 a CS type event 216.
  • the SE 12 detects 218 whether the PDP context has or has not been dropped.
  • the CS type event is compliant preferably with standard technical specifications, like e.g. the 3GPP TS 31 .1 1 1 (such as the V12.5.0 (September 2014)) and/or ETSI TS 102.223 (such as the V12.0.0 (May 2014)).
  • standard technical specifications like e.g. the 3GPP TS 31 .1 1 1 (such as the V12.5.0 (September 2014)) and/or ETSI TS 102.223 (such as the V12.0.0 (May 2014)).
  • the CS type event 216 includes (or is accompanied with) additional data, like e.g. a reason(s) for the drop, when applicable.
  • the SE 12 While the SE 12 detects 218 that the PDP context has not been dropped, i.e. if the CS type event does not match any predetermined channel status relating to a dropped PDP context, the SE 12 waits until receiving from the host 14 an additional CS type event 216.
  • the SE 12 detects 220 that the PDP context has been dropped.
  • the SE 12 may further know based on additional data provided through the CS type event 216 a reason(s) for the drop, such as a PDP context release, a PDP context timer expiry (i.e. an expiry of a predetermined time delay, like e.g. a few minutes), when applicable.
  • the invention solution does not need to involve a phone user, except for submitting user authentication data, when applicable.
  • the invention solution is therefore transparent to the user (no need of any MM I), apart from a possible user authentication operation.
  • the invention solution is compatible with the existing network infrastructure.
  • the invention solution allows detecting a failure or a drop in a PDP context or an EPS PDN connection possibly with a reason(s) or a cause(s).
  • the invention solution may allow finding a wrong or spurious configuration parameter(s), like e.g. an APN, resident in the host. Then, a recovery of a right configuration parameter(s) to be injected into the host may be carried out under the chip control as soon as the configuration parameter(s) is(are) detected as being corrupted.
  • a wrong or spurious configuration parameter(s) like e.g. an APN
  • the right configuration parameter recovery or restoration may be on-line and secure.
  • the host user benefits from a good user experience.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un procédé (20) pour détecter un échec ou un abandon dans un contexte PDP ou une connexion PDN. Selon l'invention, une puce (12) est incorporée dans un dispositif (14) ou lui est couplée, et la puce reçoit du dispositif un événement de type activation de contexte PDP de commande d'appel (22) ou un événement de type activation de connexion PDN EPS de commande d'appel. La puce envoie au dispositif une instruction de type canal ouvert (28). La puce reçoit du dispositif une réponse de type réponse de terminal (210). La puce détecte (212) si le dispositif échoue ou non à activer un contexte PDP ou une connexion PDN EPS. Si la réponse de type réponse de terminal comprend au moins une erreur prédéterminée, alors la puce détecte (214) que le dispositif a échoué à activer un contexte PDP ou une connexion PDN EPS. Si la réponse de type réponse de terminal ne comprend pas au moins une erreur prédéterminée, alors la puce détecte que le dispositif a réussi à activer un contexte PDP ou une connexion PDN EPS. Si la puce détecte que le dispositif a réussi à activer le contexte PDP ou la connexion PDN EPS, alors la puce reçoit du dispositif un événement de type état de canal (216). La puce détecte (218) si le contexte PDP ou la connexion PDN EPS a ou n'a pas été abandonné. Si l'événement de type état de canal correspond à au moins un état de canal prédéterminé concernant un contexte PDP abandonné ou une connexion PDN EPS abandonnée, alors la puce détecte (220) que le contexte PDP ou la connexion PDN EPS a été abandonné.
PCT/EP2017/057872 2016-04-04 2017-04-03 Procédé, puce et système pour détecter un échec ou un abandon dans un contexte pdp ou une connexion pdn eps Ceased WO2017174519A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
EP16380016 2016-04-04
EP16380016.2 2016-04-04

Publications (1)

Publication Number Publication Date
WO2017174519A1 true WO2017174519A1 (fr) 2017-10-12

Family

ID=55755540

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2017/057872 Ceased WO2017174519A1 (fr) 2016-04-04 2017-04-03 Procédé, puce et système pour détecter un échec ou un abandon dans un contexte pdp ou une connexion pdn eps

Country Status (1)

Country Link
WO (1) WO2017174519A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109936518A (zh) * 2017-12-18 2019-06-25 迈普通信技术股份有限公司 交换芯片通道故障的检测方法和分布式机架交换机
CN111183705A (zh) * 2018-11-12 2020-05-19 联发科技股份有限公司 移动通信中用于系统间切换的遗失配置错误处理技术
CN117177383A (zh) * 2022-05-27 2023-12-05 深圳传音控股股份有限公司 控制方法、智能终端及存储介质

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2519040A1 (fr) * 2011-04-26 2012-10-31 Research In Motion Limited Méthodes et appareils pour la transmission des codes de cause de rejet d'activation de contexte PDP à l'UICC

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2519040A1 (fr) * 2011-04-26 2012-10-31 Research In Motion Limited Méthodes et appareils pour la transmission des codes de cause de rejet d'activation de contexte PDP à l'UICC

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Universal Subscriber Identity Module (USIM) Application Toolkit (USAT) (3GPP TS 31.111 version 13.2.0 Release 13)", TECHNICAL SPECIFICATION, EUROPEAN TELECOMMUNICATIONS STANDARDS INSTITUTE (ETSI), 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS ; FRANCE, vol. 3GPP CT 6, no. V13.2.0, 31 January 2016 (2016-01-31), XP014266270 *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109936518A (zh) * 2017-12-18 2019-06-25 迈普通信技术股份有限公司 交换芯片通道故障的检测方法和分布式机架交换机
CN109936518B (zh) * 2017-12-18 2022-02-11 迈普通信技术股份有限公司 交换芯片通道故障的检测方法和分布式机架交换机
CN111183705A (zh) * 2018-11-12 2020-05-19 联发科技股份有限公司 移动通信中用于系统间切换的遗失配置错误处理技术
CN111183705B (zh) * 2018-11-12 2023-10-13 联发科技股份有限公司 用于系统间切换的遗失配置错误处理方法及其装置
CN117177383A (zh) * 2022-05-27 2023-12-05 深圳传音控股股份有限公司 控制方法、智能终端及存储介质

Similar Documents

Publication Publication Date Title
EP3446502B1 (fr) Procédé, serveurs et système permettant de télécharger un profil mis à jour
US8407769B2 (en) Methods and apparatus for wireless device registration
EP2887702B1 (fr) Procédé et dispositif pour fournir un élément sécurisé avec un profil d'abonnement
EP3347849B1 (fr) Procédé, dispositif et système d'authentification dans un réseau mobile et serveur d'authentification de dispositifs dans un réseau mobile
US20200351761A1 (en) System and method for monitoring mobile data configuration access point names
US9197719B2 (en) Method for communicating data between a system and a mobile network through an IP channel, corresponding portable object and system
WO2017174519A1 (fr) Procédé, puce et système pour détecter un échec ou un abandon dans un contexte pdp ou une connexion pdn eps
US10779220B2 (en) Method and chip for detecting a corruption of at least one configuration parameter
US10251122B2 (en) Method for switching from a first to a second mobile network operator and corresponding device
EP3523999B1 (fr) Procédé, dispositif, serveur et système pour sécuriser un accès à au moins un service
US11019672B2 (en) Method, chip and system for detecting a failure in a PDP context or an EPS PDN connection
EP3133849A1 (fr) Procédé, jeton et système de commutation d'un premier à un second opérateur mobile selon une technologie d'accès à un réseau
EP3113525A1 (fr) Procédé, jeton et système de commutation d'un premier à un second opérateur de réseau mobile
EP2890164A1 (fr) Procédé permettant d'accéder à un service, dispositif et système correspondants

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17714793

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 17714793

Country of ref document: EP

Kind code of ref document: A1