EP3354113B1 - Kommunikationsendgerät und verfahren zur kommunikation von daten - Google Patents

Kommunikationsendgerät und verfahren zur kommunikation von daten Download PDF

Info

Publication number
EP3354113B1
EP3354113B1 EP16849249.4A EP16849249A EP3354113B1 EP 3354113 B1 EP3354113 B1 EP 3354113B1 EP 16849249 A EP16849249 A EP 16849249A EP 3354113 B1 EP3354113 B1 EP 3354113B1
Authority
EP
European Patent Office
Prior art keywords
application
communication
communication terminal
request received
layer data
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.)
Active
Application number
EP16849249.4A
Other languages
English (en)
French (fr)
Other versions
EP3354113A1 (de
EP3354113B8 (de
EP3354113A4 (de
Inventor
Herbert Dawid
Tobias Scholand
Michael Speth
Roland Hellfajer
Markus Jordan
Edgar Bolinth
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.)
Apple Inc
Original Assignee
Intel IP Corp
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 Intel IP Corp filed Critical Intel IP Corp
Publication of EP3354113A1 publication Critical patent/EP3354113A1/de
Publication of EP3354113A4 publication Critical patent/EP3354113A4/de
Publication of EP3354113B1 publication Critical patent/EP3354113B1/de
Application granted granted Critical
Publication of EP3354113B8 publication Critical patent/EP3354113B8/de
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • 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
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/10—Flow control between communication endpoints
    • H04W28/14—Flow control between communication endpoints using intermediate storage
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/02—Buffering or recovering information during reselection ; Modification of the traffic flow during hand-off
    • H04W36/023—Buffering or recovering information during reselection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H04W76/34—Selective release of ongoing connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals

Definitions

  • Embodiments described herein generally relate to communication terminals and methods for communicating data.
  • a subscriber terminal of a cellular communication network may have two SIM cards.
  • a subscriber terminal having two SIM cards may be equipped with only a single radio transmitter which thus needs to be shared by the two SIM cards. Accordingly, efficient approaches which allow communication via both SIM cards in such a scenario are desirable.
  • US 2015/0023258 discloses a device configured to establish a first call with a first subscription and accept a second call with a second subscription while maintaining the first call.
  • a single transmit chain is used to transmit uplink traffic with both calls, and a timesharing scheduler for the transmit chain may determine when uplink traffic associated with either call is transmitted.
  • US 2014/0220981 discloses a method wherein a dual SIM device may establish an RRC connection for data transmission, then detect a suspension event and send a connection release indication in order to alert the network that the device may not be able to receive a downlink signal.
  • US 2013/0272251 discloses a communication terminal with a first determiner configured to determine a desired communication behavior for the exchange of data for a software application and a second determiner configured to determine a time for the exchange of data between the communication terminal and the network depending on the desired communication behavior.
  • Figure 1 shows a communication system 100, e.g. an LTE (Long Term Evolution) communication system.
  • LTE Long Term Evolution
  • the communication system 100 includes a radio access network (e.g. an E-UTRAN, Evolved UMTS (Universal Mobile Communications System) Terrestrial Radio Access Network according to LTE) 101 and a core network (e.g. an EPC, Evolved Packet Core, according LTE) 102.
  • the radio access network 101 may include base (transceiver) stations (e.g. eNodeBs, eNBs, according to LTE) 103. Each base station 103 provides radio coverage for one or more mobile radio cells 104 of the radio access network 101.
  • a mobile terminal (also referred to as UE, user equipment, or MS, mobile station) 105 located in a mobile radio cell 104 may communicate with the core network 102 and with other mobile terminals 105 via the base station providing coverage in (in other words operating) the mobile radio cell.
  • UE user equipment
  • MS mobile station
  • Control and user data are transmitted between a base station 103 and a mobile terminal 105 located in the mobile radio cell 104 operated by the base station 103 over the air interface 106 on the basis of a multiple access method.
  • the base stations 103 are interconnected with each other by means of a first interface 107, e.g. an X2 interface.
  • the base stations 103 are also connected by means of a second interface 108, e.g. an S1 interface, to the core network, e.g. to an MME (Mobility Management Entity) 109, and a Serving Gateway (S-GW) 110.
  • MME Mobility Management Entity
  • S-GW Serving Gateway
  • the MME 109 is responsible for controlling the mobility of mobile terminals located in the coverage area of E-UTRAN
  • the S-GW 110 is responsible for handling the transmission of user data between mobile terminals 105 and core network 102.
  • the radio access network 101 and the core network may support communication according to various communication technologies, e.g. mobile communication standards.
  • each base station 103 may provide a radio communication connection via the air interface between itself and the mobile terminal 105 according to LTE, UMTS, GSM (Global System for Mobile Communications), EDGE (Enhanced Data Rates for GSM Evolution) radio access.
  • the radio access network 102 may operate as an E-UTRAN, a UTRAN, a GSM radio access network, or a GERAN (GSM EDGE Radio Access Network).
  • the core network 102 may include the functionality of an EPC, a UMTS core network or a GSM core network.
  • the mobile terminal 105 For uplink radio communication via the air interface 106, the mobile terminal 105 includes a radio transmitter (TX RF) 111.
  • TX RF radio transmitter
  • Data transmission between the mobile terminal 105 and the corresponding base station 103 is carried out in accordance with a (radio) frame structure.
  • a (radio) frame structure An example of a frame structure is shown in Figure 2 .
  • Figure 2 shows a frame 200 of an exemplary frame structure.
  • the frame 200 may be used for both full-duplex and half-duplex FDD.
  • the frame 200 is 10 ms long and consists of 20 slots 201 of length 0.5 ms, numbered from 0 to 19.
  • a subframe 202 is defined as two consecutive slots 201. In each 10 ms interval ten subframes 202 are available for downlink transmissions or uplink transmissions, i.e. as time transmission intervals (TTI).
  • TTI time transmission intervals
  • a frame may have a different number of subframes than ten and a subframe may include more than two slots.
  • Uplink and downlink transmissions are separated in the frequency domain.
  • a subframe 202 may include 12 or 14 OFDM (orthogonal frequency division multiple access) symbols in DL (downlink) and 12 or 14 SC-FDMA symbols in UL (uplink), respectively.
  • the mobile terminal 105 may include an identity module 112 (e.g. implemented by a chip card) that allows the mobile terminal 105 to identify itself as a subscriber of the communication network (e.g. as an LTE subscriber) formed by the radio access network 101 and the core network 102 and thus to use the communication network as a home network.
  • an identity module 112 e.g. implemented by a chip card
  • the mobile terminal 105 may include a further identity module 113, i.e. may be a multi-SIM device that allows the mobile terminal 105 also to use another communication network (e.g. WCDMA (Wideband Code Division Multiple Access) network such as a UMTS network) since in practice, a plurality of cellular communication networks are provided by different operators and according to different radio access technologies (e.g. LTE and UMTS) such that the coverage areas of the communication networks overlap, i.e. a mobile terminal may be located within a radio cell 104 operated by a base station 103 belonging to a first communication network of a first operator according to a first radio access technology (e.g. LTE) and at the same time be located within a radio cell operated by a base station 03 belonging to a second communication network of a second operator according to a second radio access technology (e.g. UMTS).
  • WCDMA Wideband Code Division Multiple Access
  • UMTS Universal Mobile Broadband Code Division Multiple Access
  • Figure 3 shows a radio cell arrangement 300 according to an embodiment.
  • the radio cell arrangement 300 includes a first plurality of radio cells 301 (shown without hatching) operated by a plurality of first base stations 302 of a first communication network (e.g. LTE base stations eNB), and a second plurality of radio cells 303 indicated by a hatching 304 operated by a plurality of second base stations 305 of a second communication network (e.g. UMTS base stations NB).
  • a first communication network e.g. LTE base stations eNB
  • second plurality of radio cells 303 indicated by a hatching 304 operated by a plurality of second base stations 305 of a second communication network e.g. UMTS base stations NB
  • the second plurality of radio cells 303 overlaps the first plurality of radio cells 304 such that a mobile terminal 306, e.g. corresponding to mobile terminal 105, located in the overlapping area may connect to both the first communication network and the second communication network, e.g. may both register with a base station 302 of the first communication network and a base station 305 of the second communication network.
  • the mobile terminal 306 may communicate with the first communication network by means of its LTE identity module 112, i.e. under the subscription of its first identity module 112, and may communicate with the second communication network by means of its UMTS identity module 113, i.e. under the subscription of its second identity module 113.
  • Dual-SIM devices such as the mobile terminal 306 or even Multi-SIM devices with more than two SIMs are gaining considerable market traction.
  • RAT Radio Access Technology
  • More advanced schemes include from DR-DSDS (Dual Receive DSDS which require the mobile terminal to have two independent receive chains) up to DSDA (Dual SIM Dual Active) where both SIMs can even run two calls simultaneously (which usually implies that the mobile terminal includes two independent transmit chains as well). Since multiple voice calls in parallel are hard to imagine as a common use case, one might argue that DSDA will not considerably improve user experience over DR-DSDS. However, two times packed switched (PS) data on both SIMs, or even packed switched voice (VoIP, VoLTE) on one SIM and PS data on the other SIM represent quite common use cases in Multi-SIM capable mobile phones, which makes DSDA an important feature. As illustrated in figure 4 , different sets of applications using packed switched data transfer may be running in parallel on two SIMs.
  • PS packed switched
  • VoIP packed switched voice
  • Figure 4 shows a dual-SIM mobile terminal 400 with a dual (RF) transmit and receive chain.
  • the mobile terminal 400 includes a first SIM 401 for usage of a first communication network of a first operator including a first base station 403, e.g. corresponding to one of the base stations 305 (e.g. a UMTS SIM) and a second SIM 402 for usage of a second communication network of a second operator including a second base station 404, e.g. corresponding to one of the base stations 302 (e.g. an LTE SIM).
  • a first SIM 401 for usage of a first communication network of a first operator including a first base station 403, e.g. corresponding to one of the base stations 305 (e.g. a UMTS SIM) and a second SIM 402 for usage of a second communication network of a second operator including a second base station 404, e.g. corresponding to one of the base stations 302 (e.g. an LTE SIM).
  • a first base station 403 e.g. corresponding to one of the base stations 305 (e.g. a
  • a first set of applications 405 communicates via the first SIM 401, i.e. communicates via the first communication network under the subscription of the first SIM 401.
  • a second set of applications 406 communicates via the second SIM 402, i.e. communicates via the second communication network under the subscription of the second SIM 402.
  • the applications 405, 406 are located on the application layer, e.g. according to the ISO/OSI reference model.
  • the SIMs 401, 402 can be seen to be part of the protocol stack, which also provides a respective MAC layer 407, 408.
  • the mobile terminal 400 includes a baseband circuit 409 which includes a receive (RX) baseband unit 410 and a transmit (TX) baseband unit 411 for the first SIM as well as a receiver baseband unit 412 and a transmit baseband unit 413 for the second SIM.
  • RX receive
  • TX transmit
  • the mobile terminal 400 includes an RF unit 414 which includes a receive RF path 415 and a transmit RF path 416 for the first SIM as well as a receive RF path 417 and a transmit RF path 418 for the second SIM.
  • the mobile terminal 400 is equipped with an RF transmit chain and a TX transmit chain for each SIM and can thus handle RF RX and TX processing for both SIMs 401, 402 in parallel.
  • the RF TX/RX paths 414 to 418 are connected to the respective baseband units 410 to 413 and (e.g. via a Quadplexer 419) to an antenna 420 for radio communication with the base stations 403, 404.
  • the SIMs 401, 402 do not need to share the RF transmitter or the RF receiver.
  • single receiver and/or transmitter sharing is of particular importance in the implementation of dual SIM devices due to the relatively high cost involved with providing two independent RF receiver and/or RF transmitter chains.
  • the single receive and/or transmit resource needs to be shared between the activities of the involved SIM cards which are typically completely asynchronous.
  • Figure 5 shows a dual-SIM mobile terminal 500 with a single (RF) transmit and receive chain.
  • the mobile terminal 500 includes a first SIM 501 for usage of a first communication network of a first operator including a first base station 503, e.g. corresponding to one of the base stations 305 (e.g. a UMTS SIM) and a second SIM 502 for usage of a second communication network of a second operator including a second base station 504, e.g. corresponding to one of the base stations 302 (e.g. an LTE SIM).
  • a first SIM 501 for usage of a first communication network of a first operator including a first base station 503, e.g. corresponding to one of the base stations 305 (e.g. a UMTS SIM) and a second SIM 502 for usage of a second communication network of a second operator including a second base station 504, e.g. corresponding to one of the base stations 302 (e.g. an LTE SIM).
  • a first base station 503 e.g. corresponding to one of the base stations 305 (e.g. a UM
  • a first set of applications 505 communicates via the first SIM 501, i.e. communicates via the first communication network under the subscription of the first SIM 501.
  • a second set of applications 506 communicates via the second SIM 502, i.e. communicates via the second communication network under the subscription of the second SIM 502.
  • the applications 505, 506 are located on the application layer, e.g. according to the ISO/OSI reference model.
  • the SIMs 501, 502 can be seen to be part of the protocol stack, which also provides a respective MAC layer 507, 508.
  • the mobile terminal 500 includes a baseband circuit 509 which includes a receive (RX) baseband unit 510 and a transmit (TX) baseband unit 511 for the first SIM as well as a receiver baseband unit 512 and a transmit baseband unit 513 for the second SIM. This means that the mobile terminal can handle baseband RX and TX processing for both SIMs 501, 502 in parallel.
  • RX receive
  • TX transmit
  • the mobile terminal 500 includes an RF unit 514 which includes a single receive RF path 515 and a single transmit RF path 516 for both SIMs 501, 502.
  • the mobile terminal 500 is equipped with a single RF transmit chain and a single TX transmit chain for both SIMs 501, 502 and can therefore not handle RF RX and TX processing for both SIMs 501, 502 in parallel.
  • the RF RX/TX paths 515, 516 are connected via a multiplexer 517 to the respective baseband units 510 to 513 and (e.g. via a Diplexer 518) to an antenna 520 for radio communication with the base stations 503, 504.
  • the control of multiple concurrent accesses to a commonly used radio channel is usually handled by the media access control (MAC) layer in communication systems (which belongs to Layer 2 in the OSI/ISO model).
  • MAC media access control
  • the RATs typically share a single receive and transmit chain due to cost and coexistence reasons.
  • the corresponding MAC layers of the involved RATs are then designed to be multi-RAT aware and include mechanisms to schedule and coordinate concurrent access of the involved RATs.
  • today's mobile terminals with multiple SIMs, such as mobile terminal 500 are standardized without introducing Multi-SIM aware functionality in the involved MAC layers 507, 508.
  • a scheduling can usually be found that allows for simple alternating usage of the single receiver chain 515 and transmitter chain 516 and collision resolution, e.g. by simple priority based assignment of the available resources to the two SIMs 501, 502 by the protocol stack software and the physical layer firmware, e.g. represented by the multiplexer 517.
  • this SIM 501 usually occupies at least a large fraction or even 100% of the single receiver chain 515 and/or transmitter chain 516. Then, simple alternating usage of single receiver/transmitter resources and priority based collision resolution might still be possible when only one SIM enters a call as long as the other SIM stays in idle/paging since in idle/paging mode only receive resources are required and the allocation times are typically short.
  • applications of both applications sets 505, 506 and both SIMs 501, 502 may be in a call (or more generally a dedicated connection) simultaneously and alternating usage and priority based collision resolution are no longer feasible.
  • Figure 6 shows a state diagram 600 showing E-UTRA RRC states and inter-RAT mobility procedures related to UMTS, LTE and GSM.
  • the state diagram 600 includes the UMTS (UTRA, 3G) mobile terminal states CELL_DCH 601, CELL_FACH 602, CELL_PCH/URA_PCH 603, and UTRA_Idle 604, the LTE (E-UTRA) mobile terminal states RRC CONNECTED 605 and RRC IDLE 606 and the GSM (GERAN, 2G and 2.5G) mobile terminal states GSM_Connected 607, GPRS Packet Transfer Mode 608, and GSM_Idle/GPRS Packet_Idle 609. Contrary to UMTS, there are only two E-UTRA RRC states defined for the mobile terminal 105. Figure 6 can be seen to illustrate the mobility support between E-UTRA, UTRA and GERAN.
  • a handover may be carried out between E-UTRA (i.e. a base station 103 operating according to LTE) and UTRAN (i.e. a base station 103 operating according to UTMS).
  • E-UTRA i.e. a base station 103 operating according to LTE
  • UTRAN i.e. a base station 103 operating according to UTMS
  • a handover may be carried out between E-UTRA (i.e. a base station 103 operating according to LTE) and GERAN (i.e. a base station 103 operating according to GSM).
  • E-UTRA i.e. a base station 103 operating according to LTE
  • GERAN i.e. a base station 103 operating according to GSM
  • Third state transitions 612 may occur between states of the UTRAN, the GERAN, and the E-UTRAN, e.g. in case of cell reselection without the handover of an active call. It should be noted that state transitions between states of the UTRAN and GERAN are omitted for simplicity but may also be possible.
  • Fourth state transitions 613 may occur between states of the same radio access technology, e.g. when a connection is released or a connection is established.
  • the mobile terminal 105 is in RRC_CONNECTED when an RRC connection has been established. If this is not the case, i.e. no RRC connection is established, the mobile terminal 105 is in RRC_IDLE state.
  • Figure 7 shows another state diagram 700 showing E-UTRA RRC states and inter-RAT mobility procedures related to UMTS, LTE and GSM.
  • the state diagram 700 can be seen as an alternative representation of the UMTS, LTE and GSM states and transitions between them.
  • the state diagram 700 includes the UMTS (UTRA, 3G) mobile terminal states CELL_DCH 701, CELL_FACH 702, CELL_PCH/URA_PCH 703, and UTRA_Idle 704, the LTE (E-UTRA) mobile terminal states RRC CONNECTED 705 and RRC IDLE 706 and the GSM (GERAN, 2G and 2.5G) mobile terminal states GSM_Connected 707, GPRS Packet Transfer Mode 708, and GSM_Idle/GPRS Packet_Idle 709 with transitions between them as explained with reference to figure 6 .
  • UTRA Universal Terrestriality
  • starting a call means entering the RRC (Radio Resource Control) state RRC Connected 605, 705.
  • RRC Radio Resource Control
  • starting a call means entering the RRC states CELL_FACH 602, 702 or CELL_DCH 601, 701. State transitions within LTE or 3G from idle mode 604, 704, 606. 706 to connected mode requires RRC connection establishment which involves random access to the network in the uplink and hence corresponding uplink resources.
  • the mobile terminal In 3G cell-FACH state, the mobile terminal (UE) is required to receive the FACH transport channel continuously, hence to occupy an RX receive chain continuously. Uplink accesses to the network are handled via Random Accesses in cell-FACH which leads to some specific pattern regarding the utilization of an TX uplink transmission chain.
  • 3G enhanced cell-FACH (eFACH) state the (UE) is required to occupy an RX receive chain continuously (with potential gaps for power saving) for HS-PDSCH reception. Uplink accesses to the network are still handled via Random Accesses in cell-FACH which leads to some specific pattern regarding the utilization of an TX uplink transmission chain.
  • eFACH enhanced cell-FACH
  • the (UE) In 3G enhanced uplink in cell-FACH (eRACH) state, the (UE) is required to occupy an RX receive chain continuously (with potential gaps for power saving) for HS-PDSCH and FDPCH reception and to occupy a TX chain continuously for uplink DPCCH transmission plus E-DCH transmission.
  • eRACH enhanced uplink in cell-FACH
  • the UE In 3G cell-DCH state, the UE is required to occupy both uplink and downlink TX and RX resources continuously for uplink DPCCH/DPDCH and E-DCH transmissions and downlink DPCH, F-DPCH reception and HS-SCCH/HS_PDSCH reception.
  • a communication terminal which may for example provide DSDA in case that a 3G connection is involved even if it includes a single receiver chain and a single transmitter chain.
  • Figure 8 shows a communication terminal 800.
  • the communication terminal 800 includes a communication circuit 801 for communicating over different communication networks 804, 805 and an application processor 802 configured to execute a plurality of applications.
  • the communication terminal 800 further includes a controller 803 configured to receive, from each application of the plurality of applications, a respective request for an exchange of application layer data over a communication network 804, 805 associated with the respective application, to select, based on a predetermined criterion, a first application of the plurality of applications and to control the communication circuit 801 to perform an exchange according to the request received from the first application over a first network layer communication connection 806 to a communication network 804 associated with the first application; to initiate, for a second application of the plurality of applications, a buffering, during the first network layer communication connection 806, of application layer data requested to be exchanged according to the request received from the second application; to control the communication circuit to release the first network layer communication connection 806 based on a duration of the buffering and to control the communication circuit to establish a second network layer communication connection 807 to a communication network 805 associated with the second application which is different from the communication network 804 associated with the first application and perform an exchange according to the request received from the second application over the second network layer
  • a communication terminal exchanges first application layer data to be exchanged with a first communication network (e.g. used by means of a first SIM) via a first communication connection (e.g. a data call) while the communication terminal lets second application layer data to be exchanged with a second communication network (e.g. used via a second SIM) be buffered. Then, the communication terminal releases the first communication connection and establishes a second communication connection (e.g. a data call) to exchange the buffered second application layer data.
  • a first communication network e.g. used by means of a first SIM
  • a second communication network e.g. used via a second SIM
  • the network layer communication connections are for example IP (Internet Protocol) connections.
  • the communication circuit may for example include two modems, wherein the first modem is configured to communication with the first communication network and the second modem is configured for communication with the second communication network.
  • the two modems may for example share a single RF chain.
  • the first modem may include a baseband circuit according to a first RAT and the second modem may include a baseband circuit according to a second RAT.
  • Two communication networks being different may for example mean that the communication networks are configured according to different RATs or are operated by different operators or both. Two communication networks being different may also mean that the communication networks are independent communication networks, e.g. with an independent network infrastructure or for example each requiring its own subscription (to be a home network rather than a visited network for roaming).
  • the communication connections are network layer communication connections, i.e. layer 3 communication connections according to the OSI (Open Systems Interconnection Model) reference model.
  • OSI Open Systems Interconnection Model
  • having a network layer communication connection e.g. by means of a SIM, means that the communication terminal is in a layer 3 connected mode (e.g. a E-UTRA or UTRA RRC connected mode), e.g. for that SIM.
  • a layer 3 connected mode e.g. a E-UTRA or UTRA RRC connected mode
  • the components of the communication terminal may for example be implemented by one or more circuits.
  • a “circuit” may be understood as any kind of a logic implementing entity, which may be special purpose circuitry or a processor executing software stored in a memory, firmware, or any combination thereof (e.g. an operating system).
  • a “circuit” may be a hard-wired logic circuit or a programmable logic circuit such as a programmable processor, e.g. a microprocessor.
  • a “circuit” may also be a processor executing software, e.g. any kind of computer program. Any other kind of implementation of the respective functions which will be described in more detail below may also be understood as a "circuit".
  • the communication terminal for example performs a method as illustrated in figure 9 .
  • Figure 9 shows a flow diagram 900 illustrating a method for communicating data, e.g. performed by a communication terminal.
  • a component of the communication terminal receives, from each application of a plurality of applications executed on the communication terminal, a respective request for an exchange of application layer data over a communication network associated with the respective application.
  • the communication terminal selects, based on a predetermined criterion, a first application of the plurality of applications.
  • the communication terminal performs an exchange according to the request received from the first application over a first network layer communication connection to a communication network associated with the first application.
  • the communication terminal (or another communication device) buffers, for a second application of the plurality of applications, during the first network layer communication connection, application layer data requested to be exchanged according to the request received from the second application.
  • the communication terminal releases the first network layer communication connection based on a duration of the buffering.
  • the communication terminal establishes a second network layer communication connection to a communication network associated with the second application which is different from the communication network associated with the first application.
  • the communication terminal performs an exchange according to the request from the second application over the second network layer communication connection after release of the first network layer communication connection.
  • A-MAC Multi-SIM aware media access control mechanism
  • Figure 10 shows a dual-SIM mobile terminal 1000 with a single (RF) transmit and receive chain managed by an Multi-SIM aware media access control mechanism.
  • the mobile terminal 1000 includes a first SIM 1001 for usage of a first communication network of a first operator including a first base station 1003, e.g. corresponding to one of the base stations 305 (e.g. a UMTS SIM) and a second SIM 1002 for usage of a second communication network of a second operator including a second base station 1004, e.g. corresponding to one of the base stations 302 (e.g. an LTE SIM).
  • a first SIM 1001 for usage of a first communication network of a first operator including a first base station 1003, e.g. corresponding to one of the base stations 305 (e.g. a UMTS SIM) and a second SIM 1002 for usage of a second communication network of a second operator including a second base station 1004, e.g. corresponding to one of the base stations 302 (e.g. an LTE SIM).
  • a first base station 1003 e.g. corresponding to one of the base stations 305 (e.g. a UM
  • a first set of applications 1005 communicates via the first SIM 1001, i.e. communicates via the first communication network under the subscription of the first SIM 1001.
  • a second set of applications 1006 communicates via the second SIM 1002, i.e. communicates via the second communication network under the subscription of the second SIM 1002.
  • the applications 1005, 1006 are located on the application layer 1019, e.g. according to the ISO/OSI reference model.
  • the SIMs 1001, 1002 can be seen to be part of the protocol stack 1020, which also provides a respective MAC layer 1007, 1008.
  • an A-MAC 1021 is provided (e.g. corresponding to the controller 803), e.g. implemented by a processor running the applications of application sets 1005, 1006.
  • the mobile terminal 1000 includes a baseband circuit 1009 which includes a receive (RX) baseband unit 1010 and a transmit (TX) baseband unit 1011 for the first SIM as well as a receiver baseband unit 1013 and a transmit baseband unit 1012 for the second SIM. This means that the mobile terminal can handle baseband RX and TX processing for both SIMs 1001, 1002 in parallel.
  • RX receive
  • TX transmit
  • the mobile terminal 1000 includes an RF unit 1014 which includes a single receive RF path 1015 and a single transmit RF path 1016 for both SIMs 1001, 1002. This means that the mobile terminal 1000 is equipped with a single RF transmit chain and a single TX transmit chain for both SIMs 1001, 1002 and can therefore not handle RF RX and TX processing for both SIMs 1001, 1002 in parallel.
  • the RF RX/TX paths 1015, 1016 are connected via a multiplexer 1017 to the respective baseband units 1010 to 1013 and (e.g. via a Diplexer 1018) to an antenna 1020 for radio communication with the base stations 1003, 1004.
  • the A-MAC 1021 manages the single transmitter/receiver resource (i.e. the single receive chain 1015 and the single transmit chain 1016 shared between the SIMs 1001, 1002) as shared resource.
  • the A-MAC 1020 performs application layer scheduling of the data transfers and activities of the SIMs 1001, 1002 with the goal of collision avoidance with respect to the shared transmitter/receiver resources (e.g. to the largest possible extent). Since even the application layer 1019 does typically not have complete control over the data transfers and activities of the SIMs 1001, 1002 it may not be possible to completely avoid collisions. In case of such a collision, the priority based collision resolution functionality in the UE protocol stack and/or physical layer mentioned above may be activated.
  • radio access bearers are defined for different service types.
  • the mobile terminal 100 distinguishes the five service classes as indicated in the first column of table 1 and manages the sharing of the single receiver/transmitter resource as indicated in the fifth column of table 1.
  • Table 1 Service Class Latency Requirements Data rate Nature of Access RX/TX resource sharing I.
  • Conversational e.g. VoIP/VoLTE/Video Call Very high Low One long call with fixed periodic activity pattern
  • Short Background e.g.
  • the A-MAC 1020 for example performs collection/aggregation of latency uncritical packet transmissions for each SIM 1001, 1002 with the goal to perform bursty transmission/reception for each SIM 1001, 1002 in an alternating manner.
  • the A-MAC 1020 for example tries to achieve a pattern of Data Call Setups and Data Call Releases from the two SIM cards 1001, 1002 such that the actual calls of the two SIM cards 1001, 1002 are mutually exclusive in time, i.e. that they appear sequentially on the physical layer.
  • Service Class I is an exception, since the data traffic resulting here cannot be delayed, and the resulting long call cannot be interrupted.
  • MO mobile originated
  • MT mobile terminated
  • MT call setups for a SIM 1001, 1002 are further exceptions where the A-MAC 1020 cannot delay (i.e. buffer) the resulting data traffic.
  • the A-MAC 1020 can schedule less latency critical services from the other SIM 1001, 1002 (i.e. Service Class 2 and higher) around the fixed scheduling grid occupied by service class I communications and MT calls.
  • the applications 1005, 1006 may rely on MO call setups for initiating keep alive messages, mail access, instant messaging etc. to the largest possible extent, such that MT call setups are ideally restricted to real phone calls (i.e. voice communication).
  • the mobile terminal 1000 can, however, for both MO and MT calls, autonomously initiate an RRC connection release by the network (and hence a call release) by sending a Signaling Connection Release Indicator (SCRI) message to the network, e.g. in accordance with the Fast Dormancy mechanism of 3GPP REL-8.
  • SCRI Signaling Connection Release Indicator
  • the inactivity timer T323 may be set to 0 seconds in the network in order to work efficiently when the network supports Fast Dormancy.
  • Figure 11 illustrates the buffering of data and alternating communication of buffered data for two SIMs over a single RX/TX chain.
  • the third diagram 1103 shows the buffered data 1112 of the second application set 1006 as they are given to the physical layer for exchange with a further communication device (in the mobile terminal 1000 in case of upload or in the further communication device in case of download).
  • the mobile terminal 1000 performs a first MO Call Setup 1113 of the first SIM with a following first MO Call 1114 for exchange of the buffered data of the first application set 1005 and (when the buffered data of the first application set 1005 have been exchanged) a first MO Call release 1115 of the first MO Call 1114 and, subsequently, a second MO Call 1116 Setup of the second SIM with a following second MO Call 1117 for exchange of the buffered data of the second application set 1006 and (when the buffered data of the second application set 1006 have been exchanged) a second MO Call release 1118 of the second MO Call 1117.
  • the A-MAC 1020 for example gives highest priority to an application using a communication service in this service class.
  • a communication service requests physical layer (PHY) resources only periodically (using a fixed known scheduling grid).
  • the A-MAC 1020 may immediately use the approach described with reference to figure 11 for Service Classes II and III, i.e. collect or aggregate (or buffer) data for a SIM while there is a data call for the other SIM, release the call for the other SIM and setup a data call for the SIM to transmit the collected data .
  • the A-MAC 1020 may apply this approach as follows.
  • the mobile terminal 1000 maintains the PDP context in the application layer software.
  • the application layer 1019 (on the UE side for uploads, or on the serving side for downloads or streaming services) can split large files into smaller chunks and transmit (or receive in case of download) these chunks sequentially, resulting in short bursts of activity rather than one long download or upload. This file splitting and re-assembly can be done without the end user (i.e. the user of the mobile terminal 1000) noticing it.
  • the UE 1000 may for example convey the requirement for file splitting to the other communication party (e.g. another communication device such as a server) before initiating the upload, download or streaming application. Since file uploads and downloads and streaming services are initiated by the UE application layer SW, the UE 1000 is in charge of controlling the applications in these two service classes.
  • the A-MAC 1020 prevents both SIMs to enter an active call that cannot be arbitrated later on by the physical layer.
  • the A-MAC 1020 can use a round robin scheduling of the involved SIMs 1001, 1002 to sequentially activate the SIMs for a particular time.
  • the duty cycle of the activation may be fixed or may depend on the RATs capabilities or required data rates of the involved applications.
  • the application layer scheduling of multiple SIMs for the usage of a single RX/TX chain e.g. as performed by A-MAC 1020 for SIMs 1001, 1002, in other words, the application layer of multi SIM media access is described in the following in more detail for a communication system as illustrated in figure 1 .
  • FIG 12 illustrates the control plane of the Evolved Packet System (EPS).
  • EPS Evolved Packet System
  • PS connections are based on the EPS.
  • the various layers i.e. the components of the various layers involved in a PS connection (e.g. a call) in the UE 1201 (e.g. corresponding to mobile terminal 105) and the network 1202 including a base station 1203 (e.g. corresponding to one of the eNBs 103) and further components such as an MME etc. are shown.
  • the mobile device (UE) 1201 has a connection to the network (NW) 1202.
  • NW network
  • the network side communication units and layers are distributed among multiple devices like the base station 1203 and the MME etc. and the UE 1201 is only in direct connection to the base station 1203.
  • An application 1204, 1212 of layer 7 can perform a PS connection either by originating the connection from the mobile side (mobile originated, MO) or from the network side (MT, mobile terminated).
  • the PS data is routed on layer 3 or 4 to the IP protocol on layer 3. Routing takes into account by what 'route' the application 1204 can reach the corresponding application 1212 on the network side.
  • IP Internet Protocol
  • Different IP units may use different and exclusive lower layers consisting of Packet Data Convergence Protocol (PDCP) 1206, Radio Link Control (RLC) 1207, Medium Access Control (MAC) 1208 and the physical layer (PHY) 1209.
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • MAC Medium Access Control
  • PHY physical layer
  • the PHY 1209 is using radio frequency (RF) connection with corresponding RX and TX signal processing paths (e.g. corresponding to RX chain 515 and TX chain 516).
  • RF radio frequency
  • the various layers typically contain data buffers to improve data throughput experience even when involved lower layers connection is stuttering e.g. due to bad reception conditions in the PHY or lost or disordered IP Protocol Data Units (PDUs).
  • PDU IP Protocol Data Unit
  • the Non-Access Stratum (NAS) 1210 and the Radio Resource Control (RRC) 1211 are shown in figure 12 . It is task of the NAS 1210 at the UE side and the NW side to handle the Packed Data Protocol (PDP) context activation and deactivation when upper layers have data available for the IP connection.
  • the NAS 1210 uses the services of the RRC 1211 to control lower layer connections by triggering the RRC 1211 for RRC state transitions e.g. CELL_FACH to CELL_DCH.
  • the RRC 1211 is also a distributed functionality between the UE side and the NW side. As an example the UE side RRC might only provide measurements like buffer occupancy to the NW and the NW side RRC configures the UE's RRC connection states based on the measurements.
  • the RRC 1211 configures lower layers based on its RRC state which finally initiates RX and TX activity in the PHY 1209.
  • RRC Radio Resource Control
  • the RRC 1211 configures lower layers based on its RRC state which finally initiates RX and TX activity in the PHY 1209.
  • modern wireless systems typically use NAS/RRC functionality to adapt the connection state to the availability of PS data packets and thus try to power optimize the lower layers connection states.
  • a 3G system is considered (without loss of generality). While PS data is available the RRC states are changed between CELL_FACH for very low data rates and CELL_DCH if sufficient data is available on the UE side or the NW side. As mentioned above the state changes are not autonomously done by the UE 1201 but triggered by UE's measurements signaled to the NW 1202. Since CELL_FACH has seamless RX and some TX activity further power savings for always on IP connectivity is preferred.
  • the UE's NAS 1210 can request lower power RRC states like IDLE, CELL_PCH or URA_PCH by sending Signaling Connection Release Indication (SCRI) to the NW 1202 if no PS data is to be transmitted from UE side any more. Mechanisms like fast dormancy may be used to optimize these RRC state transitions further more while having an active PDP context.
  • SCRI Signaling Connection Release Indication
  • Today's multi-SIM enabled UEs are typically using operating systems (OS) based on Linux (Android, iOS) or mobile windows etc.
  • OS operating systems
  • iOS Linux
  • the applications as well as parts of the lower layers as illustrated in figure 12 are typically part of the UE's OS as illustrated in figure 13 .
  • Figure 13 illustrates the communication flow of applications running on a UE with wireless modems of the UE.
  • a first application 1301 and a second application 1302 are running on the UE's operating system 1303. They communicate, via a respective socket 1304 and per application routing 1305, with a first wireless IP unit 1306 and a second wireless IP unit 1307, respectively.
  • the first application 1301 may access a first wireless modem 1308 (e.g. associated with a first SIM, e.g. corresponding to (RX) baseband unit 510 and transmit (TX) baseband unit 511) and via the second wireless IP unit 1307 the second application 1302 may access a second wireless modem 1309 (e.g. associated with a second SIM, e.g. corresponding to receiver baseband unit 512 and transmit baseband unit 513).
  • a first wireless modem 1308 e.g. associated with a first SIM, e.g. corresponding to (RX) baseband unit 510 and transmit (TX) baseband unit 51
  • TX transmit
  • IP routing 1305 may be implemented by modern Linux functionalities cgroups, iptables and policy routing or namespace. As a result any traffic related to the first application uses the IP connection of the first SIM and any traffic related to the second application uses the IP connection of the second SIM.
  • both modems 1308, 1309 have independent RF paths implemented both applications 1301, 1302 can exchange information with the network at the same time.
  • RF resources may need to be shared, e.g. because of bill of material (BOM) and it may be desired that collision resolution mechanisms at the PHY layer which typically degrade overall system performance are avoided.
  • BOM bill of material
  • an A-MAC may be provided to avoid or lower the likelihood of above mentioned simultaneous activation of the wireless modems 1308, 1309.
  • Figure 14 illustrates the communication flow of applications running on a UE with wireless modems of the UE when an A-MAC is included.
  • a first application 1401 and a second application 1402 are running on the UE's operating system1403. They communicate, via a respective socket 1404 and per application routing 1405 and, in contrast to figure 13 , via an A-MAC 1410 with a first wireless IP unit 1406 and a second wireless IP unit 1407, respectively.
  • the first application 1401 may access a first wireless modem 1408 (e.g. associated with a first SIM, e.g. corresponding to (RX) baseband unit 510 and transmit (TX) baseband unit 511) and via the second wireless IP unit 1407 the second application 1402 may access a second wireless modem 1409 (e.g. associated with a second SIM, e.g. corresponding to receiver baseband unit 512 and transmit baseband unit 513).
  • a first wireless modem 1408 e.g. associated with a first SIM, e.g. corresponding to (RX) baseband unit 510 and transmit (TX) baseband unit 51
  • TX transmit
  • the routing 1405 is extended by the A-MAC functionality that tries to exclusively schedule IP data to the wireless IP connections. While the first application 1401 has traffic routed to a first wireless IP connection via the first modem 1408 a second wireless IP connection via the second modem 1409 is stalled (or delayed). To the application 1402 a stalled connection looks as if no IP throughput is available and to the RRC 1211 and lower layers it looks like the application has no more data to be transmitted.
  • the OS 1403 might exclusively give its CPU resource to one of the involved applications 1401, 1402 to prevent simultaneous usage of the IP connections.
  • the functionality of the NAS/RRC discussed in context of figure 12 results in RRC state transitions of the stalled connection to low power states when the corresponding IP connection is stalled.
  • lower layer activity down to the PHY 1209 is reduced resulting in less RX and TX RF activity requested from the second wireless modem 1402 and thus less disturbance to the ongoing first IP connection.
  • the functionality may be used that when no data is transmitted and received for a certain time the PHY link is released by the NAS/RRC.
  • A-MAC scheduler 1410 may be used:
  • Figure 15 shows a flow diagram 1500 giving an example for a RF resource access scheduling by the A-MAC 1410.
  • the first connection (by the first application 1401) is active, while the second connection (by the second application 1402) is stalled (or its establishment is delayed).
  • the A-MAC 1410 decides that the second application 1402 can resume (or start) data transmission (when the RF resource is free).
  • the A-MAC 1410 stalls data transmission of the first application (i.e. data from the first application is not forwarded to lower layers).
  • the NAS/RRC of the first wireless modem 1408 releases the physical link of the first connection such that the RF resource is free to use for the second application/connection.
  • the wireless modems' 1408, 1409 NAS/RRC or the PHY may optionally signal to the A-MAC 1410 that the RF resource is free.
  • the A-MAC 1410 resumes the data transmission for the second application 1402.
  • the data transmitted from the second application 1402 triggers that a physical link for a new second connection is set up by the NAS/RRC.
  • the procedure returns to 1501 with the roles exchanged (i.e. second connection for second application 1402 is active, data transmission by the first application is stalled).

Landscapes

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

Claims (15)

  1. Kommunikationsendgerät (800), umfassend:
    eine erste Anmeldung (501) und eine zweite Anmeldung (502);
    eine Kommunikationsschaltung (801) zum Kommunizieren über verschiedene Kommunikationsnetzwerke (804, 805), wobei die Kommunikationsschaltung eine Übertragungskette (516) umfasst, die von der ersten Anmeldung (501) und der zweiten Anmeldung (502) gemeinsam genutzt wird;
    einen Anwendungsprozessor (802), der konfiguriert ist, um eine Vielzahl von Anwendungen auszuführen;
    eine Steuereinheit (803), die konfiguriert ist,
    um von jeder Anwendung der Vielzahl von Anwendungen eine jeweilige Anfrage für einen Austausch von Anwendungsschichtdaten über ein Kommunikationsnetzwerk (804) zu empfangen, die mit der jeweiligen Anwendung verknüpft ist;
    um basierend auf einem vorbestimmten Kriterium eine erste Anwendung aus der Vielzahl von Anwendungen auszuwählen;
    um die Kommunikationsschaltung zum Durchführen eines Austauschs gemäß der von der ersten Anwendung empfangenen Anfrage über eine erste Radio Resource Control, RRC, Verbindung zu einem Kommunikationsnetzwerk (804), das mit der ersten Anmeldung (501) verknüpft ist, zu steuern;
    um für eine zweite Anwendung der Vielzahl von Anwendungen eine Pufferung von Anwendungsschichtdaten, die gemäß der von der zweiten Anwendung empfangenen Anfrage zum Austausch angefordert wurden, während der ersten RRC-Verbindung zu initiieren; um die Kommunikationsschaltung zu steuern, um die erste RRC-Verbindung basierend auf einer Dauer der Pufferung freizugeben; und
    um die Kommunikationsschaltung zu steuern, um eine zweite RRC-Verbindung zu einem Kommunikationsnetzwerk (805) herzustellen, das mit der zweiten Anmeldung (502) verknüpft ist, die sich von dem Kommunikationsnetzwerk (804) unterscheidet, das mit der ersten Anmeldung (501) verknüpft ist, und um einen Austausch gemäß der von der zweiten Anmeldung über die zweite RRC-Verbindung empfangenen Anfrage durchzuführen, nachdem die erste RRC-Verbindung freigegeben wurde.
  2. Kommunikationsendgerät (800) nach Anspruch 1, wobei die Steuereinheit (803) konfiguriert ist, um die Kommunikationsschaltung (801) zu steuern, um die erste RRC-Verbindung basierend auf einem Pegel eines Puffers, der die Anwendungsschichtdaten puffert, die gemäß der von der zweiten Anwendung empfangenen Anfrage ausgetauscht werden sollen, freizugeben.
  3. Kommunikationsendgerät (800) nach Anspruch 1 oder 2, wobei die Steuereinheit (803) konfiguriert ist, um die Kommunikationsschaltung (801) zu steuern, um die erste RRC-Verbindung basierend darauf freizugeben, ob die Dauer der Pufferung der Anwendungsschichtdaten eine vorbestimmte Schwelle erreicht hat.
  4. Kommunikationsendgerät (800) nach Anspruch 3, wobei die Steuereinheit (803) konfiguriert ist, um die vorbestimmte Schwelle basierend auf einer zulässigen Latenzzeit der Anwendungsschichtdaten, deren Austausch gemäß der von der zweiten Anwendung empfangenen Anfrage angefordert wird, einzustellen.
  5. Kommunikationsendgerät (800) nach einem der Ansprüche 1 bis 4, wobei die Anwendungsschichtdaten, die gemäß der von der ersten Anwendung empfangenen Anfrage ausgetauscht werden sollen, Daten sind, die durch das Kommunikationsendgerät (800) zu übertragen sind, und wobei der Austausch der Anwendungsschichtdaten, die gemäß der von der ersten Anwendung empfangenen Anfrage ausgetauscht werden sollen, die Anwendungsschichtdaten sendet, die gemäß der von der ersten Anwendung empfangenen Anfrage ausgetauscht werden sollen.
  6. Kommunikationsendgerät (800) nach einem der Ansprüche 1 bis 5, wobei die Anwendungsschichtdaten, die gemäß der von der zweiten Anwendung empfangenen Anfrage ausgetauscht werden sollen, Daten sind, die durch das Kommunikationsendgerät (800) zu übertragen sind, und wobei der Austausch der Anwendungsschichtdaten, die gemäß der von der zweiten Anwendung empfangenen Anfrage ausgetauscht werden sollen, die Anwendungsschichtdaten sendet, die gemäß der von der zweiten Anwendung empfangenen Anfrage ausgetauscht werden sollen.
  7. Kommunikationsendgerät (800) nach Anspruch 6, wobei das Kommunikationsendgerät einen Puffer umfasst und die Steuereinheit (803) konfiguriert ist, um das Puffern der Anwendungsschichtdaten, deren Austausch gemäß der von der zweiten Anwendung empfangenen Anfrage angefordert wird, in dem Puffer zu initiieren.
  8. Kommunikationsendgerät (800) nach Anspruch 7, wobei der Puffer ein Anwendungsschichtpuffer ist.
  9. Kommunikationsendgerät (800) nach einem der Ansprüche 1 bis 4, wobei die Anwendungsschichtdaten, die gemäß der von der ersten Anwendung empfangenen Anfrage ausgetauscht werden sollen, Daten sind, die von dem Kommunikationsendgerät (800) empfangen werden sollen, und wobei der Austausch der Anwendungsschichtdaten, die gemäß der von der ersten Anwendung empfangenen Anfrage ausgetauscht werden sollen, die Anwendungsschichtdaten empfängt, die gemäß der von der ersten Anwendung empfangenen Anfrage ausgetauscht werden sollen.
  10. Kommunikationsendgerät (800) eines der Ansprüche 1 bis 4, wobei die Anwendungsschichtdaten, die gemäß der von der zweiten Anwendung empfangenen Anforderung ausgetauscht werden sollen, Daten sind, die von dem Kommunikationsendgerät (800) empfangen werden sollen, und wobei der Austausch der Anwendungsschichtdaten, die gemäß der von der zweiten Anwendung empfangenen Anfrage ausgetauscht werden sollen, die Anwendungsschichtdaten, die gemäß der von der zweiten Anwendung empfangenen Anforderung ausgetauscht werden sollen, von einer Kommunikationsvorrichtung empfängt.
  11. Kommunikationsendgerät (800) nach einem der Ansprüche 1 bis 10, wobei die Kommunikationsschaltung (801) mindestens eine Funkfrequenz-Transceiver (515, 516) -Kette und/oder einen Basisbandprozessor (509) umfasst, der die Kommunikation für eine Vielzahl von Teilnehmeridentitätsmodulen (501, 502) unterstützt, die in dem Kommunikationsendgerät (800) installiert sind, wobei die Vielzahl von Teilnehmeridentitätsmodulen (501, 502) eine erste Anmeldung (501) und eine zweite Anmeldung (502) umfasst.
  12. Kommunikationsendgerät (800) nach Anspruch 1, wobei die Kommunikationsschaltung (801) konfiguriert ist, um die Steuereinheit (803) zu benachrichtigen, wenn die erste RRC-Verbindung und eine entsprechende Nutzung einer Funkfrequenzressource des Kommunikationsendgerätes (800) freigegeben worden ist und eine RRC-Verbindung zu dem zweiten Kommunikationsnetzwerk (805) verfügbar geworden ist.
  13. Kommunikationsendgerät (800) nach Anspruch 1, wobei die Kommunikationsschaltung (801) konfiguriert ist, um die zweite RRC-Verbindung herzustellen, nachdem ein vorbestimmtes Schutzintervall seit der Freigabe der ersten RRC-Verbindung abgelaufen ist.
  14. Verfahren (900) für ein Kommunikationsendgerät mit einer ersten Anmeldung, einer zweiten Anmeldung und einer Übertragungskette, die von der ersten Anmeldung und der zweiten Anmeldung gemeinsam genutzt wird, um Daten zu kommunizieren, wobei das Verfahren folgendes umfasst:
    Empfangen, von jeder Anwendung einer Vielzahl von Anwendungen, die auf einem Kommunikationsendgerät ausgeführt werden, einer jeweiligen Anfrage für einen Austausch von Anwendungsschichtdaten über ein Kommunikationsnetzwerk, die mit der jeweiligen Anwendung (901) verknüpft ist;
    Auswählen, basierend auf einem vorbestimmten Kriterium, einer ersten Anwendung aus der Vielzahl von Anwendungen (902),
    Durchführen eines Austausches gemäß der von der ersten Anmeldung empfangenen Anfrage über eine erste Radio Resource Control, RRC, Verbindung zu einem mit der ersten Anmeldung verknüpften Kommunikationsnetzwerk (903);
    Puffern, für eine zweite Anwendung der Vielzahl von Anwendungen, während der ersten RRC-Verbindung, von Anwendungsschichtdaten, die gemäß der von der zweiten Anwendung (904) empfangenen Anfrage ausgetauscht werden sollen;
    Freigeben der ersten RRC-Verbindung basierend auf einer Dauer der Pufferung (905); Herstellen einer zweiten RRC-Verbindung zu einem Kommunikationsnetzwerk, das mit der zweiten Anmeldung verknüpft ist und sich von dem Kommunikationsnetzwerk unterscheidet, das mit der ersten Anmeldung (906) verknüpft ist; und
    Durchführen eines Austauschs gemäß der von der zweiten Anwendung empfangenen Anfrage über die zweite RRC-Verbindung nach Freigabe der ersten RRC-Verbindung (907).
  15. Computerlesbares Medium, das darauf aufgezeichnete Anweisungen aufweist, die, wenn sie von einem Prozessor ausgeführt werden, den Prozessor veranlassen, ein Verfahren zum Kommunizieren von Daten gemäß Anspruch 14 durchzuführen.
EP16849249.4A 2015-09-25 2016-08-24 Kommunikationsendgerät und verfahren zur kommunikation von daten Active EP3354113B8 (de)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
DE102015116288 2015-09-25
PCT/US2016/048248 WO2017052906A1 (en) 2015-09-25 2016-08-24 Communication terminal and method for communicating data

Publications (4)

Publication Number Publication Date
EP3354113A1 EP3354113A1 (de) 2018-08-01
EP3354113A4 EP3354113A4 (de) 2019-05-15
EP3354113B1 true EP3354113B1 (de) 2020-10-07
EP3354113B8 EP3354113B8 (de) 2021-02-24

Family

ID=58387212

Family Applications (1)

Application Number Title Priority Date Filing Date
EP16849249.4A Active EP3354113B8 (de) 2015-09-25 2016-08-24 Kommunikationsendgerät und verfahren zur kommunikation von daten

Country Status (4)

Country Link
US (1) US10405171B2 (de)
EP (1) EP3354113B8 (de)
CN (1) CN107926077A (de)
WO (1) WO2017052906A1 (de)

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10757667B2 (en) * 2017-07-21 2020-08-25 Samsung Electronics Co., Ltd. Method and user equipment for managing synchronization with network
CN113228719A (zh) * 2019-01-04 2021-08-06 三星电子株式会社 用于管理具有多个用户标识模块的用户设备中的通信的方法和系统
CN111836251B (zh) * 2019-04-16 2023-04-18 华硕电脑股份有限公司 无线通信系统中用于连接控制的方法和设备
WO2020243943A1 (en) * 2019-06-06 2020-12-10 Qualcomm Incorporated Service priority information for multi-sim user equipment paging
EP4082247A4 (de) * 2020-01-21 2024-01-31 Fg innovation co ltd Benutzergerät und verfahren für multi-sim-betrieb
CN111586893B (zh) * 2020-04-15 2022-03-18 中国联合网络通信集团有限公司 一种终端rrc状态切换方法及装置
CN111555825B (zh) * 2020-05-08 2022-10-18 Oppo广东移动通信有限公司 射频资源分配方法及装置
CN115669216A (zh) * 2020-09-11 2023-01-31 北京小米移动软件有限公司 连接控制方法、连接控制装置
EP4221323A4 (de) * 2020-09-28 2023-11-15 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Verfahren und vorrichtung zur kommunikationsaushandlung und endgerätevorrichtung
US20230117026A1 (en) * 2021-10-19 2023-04-20 Qualcomm Incorporated Subscriber identification module prioritization techniques based on service priority and quality of service parameters

Family Cites Families (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8559298B2 (en) * 2008-06-30 2013-10-15 Qualcomm Incorporated Method and apparatus for automatic handover optimization
US8121601B2 (en) * 2009-04-01 2012-02-21 Mediatek Inc. Methods for integrating cell measurement procedures of a communication apparatus and communication apparatuses utilizing the same
US9565715B2 (en) 2010-05-13 2017-02-07 Mediatek Inc. Apparatuses and methods for coordinating operations between circuit switched (CS) and packet switched (PS) services with different subscriber identity cards, and machine-readable storage medium
CN101977437A (zh) * 2010-07-23 2011-02-16 展讯通信（上海）有限公司 多卡移动终端及其系统消息接收方法
US8725145B2 (en) 2011-01-25 2014-05-13 Qualcomm Incorporated Mobile device requests of non-communication time periods to a wireless communication network
EP2512184B1 (de) * 2011-04-13 2017-07-19 OCT Circuit Technologies International Limited Verfahren und vorrichtung zur handhabung einer abwärtsverbindungsübertragung während des netzwerkumschaltens
US8725101B2 (en) 2011-07-06 2014-05-13 Broadcom Corporation Wireless device and method of operation
WO2013044999A1 (en) 2011-09-30 2013-04-04 Intel Mobile Communications GmbH Communication terminal, network component, base station and method for communicating
WO2013110284A1 (en) * 2012-01-23 2013-08-01 Deutsche Telekom Ag Method for using a user equipment with a first public land mobile network and with a second public land mobile network, user equipment, program and computer program product
US20130210484A1 (en) 2012-02-14 2013-08-15 Qualcomm Incorporated Method and apparatus for supporting tune-away in dual-sim dual-standby mobile devices
US20150017968A1 (en) * 2012-02-23 2015-01-15 Nokia Corporation Method and apparatus for communicating information regarding multiple subscriptions
EP2859760A1 (de) * 2012-06-12 2015-04-15 Qualcomm Incorporated Dynamische multibetreiberauswahl bei einem multi-sims-benutzergerät
CN103517454A (zh) * 2012-06-27 2014-01-15 联发科技股份有限公司 增强信令连接释放指示处理方法
US9025576B2 (en) 2012-11-01 2015-05-05 Qualcomm Incorporated Apparatus and method for employing a tune-away operation to communicate simultaneously with a plurality of channels
US9204353B2 (en) * 2013-03-15 2015-12-01 Qualcomm Incorporated Receiver-only tune-away
CN103326749B (zh) * 2013-06-17 2016-01-13 华为终端有限公司 一种nfc射频通信的控制方法、装置及系统
US20150023258A1 (en) * 2013-07-19 2015-01-22 Qualcomm Incorporated Dual sim dual active subscriber identification module with a single transmit chain and dual or single receive chain
US20150023230A1 (en) * 2013-07-19 2015-01-22 Qualcomm Incorporated Dual sim dual active subscriber identification module with a single transmit chain and dual or single receive chain
US20150031408A1 (en) 2013-07-25 2015-01-29 Qualcomm Incorporated System and Methods for Controlling Transmit Power on Multi-SIM Devices in Compliance with Specific Absorption Rate Limits
CN104684023B (zh) * 2013-12-03 2018-11-20 联芯科技有限公司 一种解决移动终端中双卡双待业务冲突的方法及装置
US9730149B2 (en) * 2014-03-12 2017-08-08 Marvell World Trade Ltd. Device and method for mobile communication
US20150373667A1 (en) * 2014-06-20 2015-12-24 Qualcomm Incorporated Method to reduce page misses in multi-sim user equipment by split acquisition
CN104536869B (zh) * 2014-12-12 2017-09-12 华为技术有限公司 移动终端及其资源管理方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None *

Also Published As

Publication number Publication date
EP3354113A1 (de) 2018-08-01
EP3354113B8 (de) 2021-02-24
US10405171B2 (en) 2019-09-03
CN107926077A (zh) 2018-04-17
WO2017052906A1 (en) 2017-03-30
US20190037386A1 (en) 2019-01-31
EP3354113A4 (de) 2019-05-15

Similar Documents

Publication Publication Date Title
EP3354113B1 (de) Kommunikationsendgerät und verfahren zur kommunikation von daten
EP3219168B1 (de) Verbesserte verbindungsverwaltung für mehrfachzugangsnetze
CN109923936B (zh) 用于改进的连通模式非连续接收的唤醒技术
CN105472695B (zh) 用于执行通信的通信终端和方法
EP3689094B1 (de) Verfahren und vorrichtung zur verwaltung von doppelregistrierung mit mehreren netzwerken in einem oder mehreren funkkommunikationssystemen
AU2017252265B2 (en) Techniques for transmission control protocol aware handover type determination
EP2901803B1 (de) Zeitgeber für leistungspräferenzindikator
WO2011085802A1 (en) Apparatus and method to indicate power saving mode of a network element
WO2016043989A1 (en) Reducing switching between networks to conserve power and reduce costs
EP2982175B1 (de) Verwaltung der kommunikation mit mehreren zugangspunkten auf basis von kommunikationen zwischen zugangspunkten
US9565631B2 (en) Method and arrangement for controlling discontinuous reception by a user equipment
EP2987383B1 (de) Verbessertes rekonfigurationsverfahren bei einem mobilen endgerät zur reduzierung von signalisierungs- und leistungsverbrauchs-overhead
US20180288824A1 (en) Communication terminal and method for transmitting a signaling message
US20230396984A1 (en) Gap configuration for ue comprising a plurality of sims in wireless network
CN114175843A (zh) 通信系统、通信终端以及网络
US20220256630A1 (en) Method and apparatus for handling connection with multi-sim
KR20230129408A (ko) 셀룰러 네트워크에서 복수의 rat 네트워크와 sim을포함하는 ue에 의한 페이징 충돌 회피
CN116982400A (zh) 多用户订户标识模块用户设备在网络之间的切换连接
WO2014112918A1 (en) Method and arrangement in a telecommunication system

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20180219

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 28/14 20090101ALI20170411BHEP

Ipc: H04W 68/00 20090101ALI20170411BHEP

Ipc: H04W 88/06 20090101AFI20170411BHEP

Ipc: H04W 76/02 20090101ALI20170411BHEP

Ipc: H04W 76/06 20090101ALI20170411BHEP

A4 Supplementary search report drawn up and despatched

Effective date: 20190415

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 88/06 20090101ALN20190409BHEP

Ipc: H04W 76/20 20180101AFI20190409BHEP

Ipc: H04W 76/15 20180101ALN20190409BHEP

Ipc: H04W 76/34 20180101ALN20190409BHEP

Ipc: H04W 28/14 20090101ALI20190409BHEP

Ipc: H04W 8/18 20090101ALI20190409BHEP

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602016045564

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04W0088060000

Ipc: H04W0076200000

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20200421

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 8/18 20090101ALI20200406BHEP

Ipc: H04W 88/06 20090101ALN20200406BHEP

Ipc: H04W 76/20 20180101AFI20200406BHEP

Ipc: H04W 76/15 20180101ALN20200406BHEP

Ipc: H04W 76/34 20180101ALN20200406BHEP

Ipc: H04W 28/14 20090101ALI20200406BHEP

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

Ref country code: AT

Ref legal event code: REF

Ref document number: 1322590

Country of ref document: AT

Kind code of ref document: T

Effective date: 20201015

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602016045564

Country of ref document: DE

GRAT Correction requested after decision to grant or after decision to maintain patent in amended form

Free format text: ORIGINAL CODE: EPIDOSNCDEC

REG Reference to a national code

Representative=s name: BARDEHLE PAGENBERG PARTNERSCHAFT MBB PATENTANW, DE

Ref country code: DE

Ref legal event code: R082

Ref document number: 602016045564

Country of ref document: DE

Ref country code: DE

Ref legal event code: R081

Ref document number: 602016045564

Country of ref document: DE

Owner name: APPLE INC., CUPERTINO, US

Free format text: FORMER OWNER: INTEL IP CORPORATION, SANTA CLARA, CA, US

RAP2 Party data changed (patent owner data changed or rights of a patent transferred)

Owner name: APPLE INC.

REG Reference to a national code

Ref country code: DE

Ref legal event code: R082

Ref document number: 602016045564

Country of ref document: DE

Representative=s name: BARDEHLE PAGENBERG PARTNERSCHAFT MBB PATENTANW, DE

REG Reference to a national code

Ref country code: CH

Ref legal event code: PK

Free format text: BERICHTIGUNG B8

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20201007

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1322590

Country of ref document: AT

Kind code of ref document: T

Effective date: 20201007

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210107

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210208

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201007

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201007

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210108

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201007

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201007

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201007

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210207

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210107

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201007

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201007

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201007

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201007

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602016045564

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201007

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201007

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201007

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201007

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201007

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201007

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201007

26N No opposition filed

Effective date: 20210708

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201007

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201007

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201007

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20210713

Year of fee payment: 6

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201007

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20210831

GBPC Gb: european patent ceased through non-payment of renewal fee

Effective date: 20210824

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210831

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210831

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210207

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210824

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210824

Ref country code: GB

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210824

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210831

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210831

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 602016045564

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20160824

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201007

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20230301

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201007