EP2840856B1 - Unterstützung der übertragung zwischen einheiten mit mobilem internetprotokoll - Google Patents

Unterstützung der übertragung zwischen einheiten mit mobilem internetprotokoll Download PDF

Info

Publication number
EP2840856B1
EP2840856B1 EP14192181.7A EP14192181A EP2840856B1 EP 2840856 B1 EP2840856 B1 EP 2840856B1 EP 14192181 A EP14192181 A EP 14192181A EP 2840856 B1 EP2840856 B1 EP 2840856B1
Authority
EP
European Patent Office
Prior art keywords
iut
wtru
flow
flow1
wtru1
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.)
Not-in-force
Application number
EP14192181.7A
Other languages
English (en)
French (fr)
Other versions
EP2840856A3 (de
EP2840856A2 (de
Inventor
Michelle Perras
Xavier De Foy
Kamel M. Shaheen
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.)
InterDigital Patent Holdings Inc
Original Assignee
InterDigital Patent Holdings Inc
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 InterDigital Patent Holdings Inc filed Critical InterDigital Patent Holdings Inc
Publication of EP2840856A2 publication Critical patent/EP2840856A2/de
Publication of EP2840856A3 publication Critical patent/EP2840856A3/de
Application granted granted Critical
Publication of EP2840856B1 publication Critical patent/EP2840856B1/de
Not-in-force 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/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1083—In-session procedures
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1083—In-session procedures
    • H04L65/1089—In-session procedures by adding media; by removing media
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1083—In-session procedures
    • H04L65/1094—Inter-user-equipment sessions transfer or sharing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/24—Connectivity information management, e.g. connectivity discovery or connectivity update
    • H04W40/30—Connectivity information management, e.g. connectivity discovery or connectivity update for proactive routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/34—Modification of an existing route
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/04—Network layer protocols, e.g. mobile IP [Internet Protocol]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1096—Supplementary features, e.g. call forwarding or call holding

Definitions

  • This application is related to mobile communications.
  • the Internet protocol (IP) multimedia subsystem is an architectural framework for delivering IP-based multimedia services.
  • a wireless transmit/receive unit may connect to an IMS through various access networks, including but not limited to networks based on technology such as universal mobile telecommunications system (UMTS) terrestrial radio access network (UTRAN), long term evolution (LTE), worldwide interoperability for microwave access (WiMax), or wireless local area network (WLAN) technology.
  • UMTS universal mobile telecommunications system
  • UTRAN terrestrial radio access network
  • LTE long term evolution
  • WiMax worldwide interoperability for microwave access
  • WLAN wireless local area network
  • the WTRU may access the IMS through a packet-switched (PS) domain.
  • PS packet-switched
  • ICS IMS centralized services
  • the WTRU may additionally access IMS services via a circuit-switched (CS) domain.
  • an inter-unit transfer (i.e., media mobility) is performed by a WTRU that supports an IMS-session initiation protocol (SIP).
  • An IUT allows a communication session to be transferred from one WTRU to another.
  • non-IMS terminals e.g., packet switched streaming (PSS) services capable terminals, real time streaming protocol (RTSP)/real time control protocol (RTCP) terminals, and/or hyper text transfer protocol (HTTP) streaming terminals.
  • PSS packet switched streaming
  • RTSP real time streaming protocol
  • RTCP real time control protocol
  • HTTP hyper text transfer protocol
  • a home agent may receive registration information for a first device from the first device.
  • the first home agent may receive a plurality of messages from a message source. Each of the plurality of messages may be addressed for a home address.
  • the home agent may receive a first binding update from the first device.
  • the first binding update may include a first traffic selector and a first action.
  • the first action may specify that a first message of the plurality of messages is to be forwarded to the first device if the first message matches the first traffic selector.
  • the home agent may receive a second binding update from the first device.
  • the second binding update may include a second traffic selector and a second action. The second action may specify that a second message of the plurality of messages is to be forwarded to a second device if the second message matches the second traffic selector.
  • the processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102.
  • location information e.g., longitude and latitude
  • the WTRU 102 may receive location information over the air interface 116 from a base station (e.g., base stations 114a, 114b) and/or determine its location based on the timing of the signals being received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by way of any suitable location-determination method while remaining consistent with an embodiment.
  • FIG. 1D is a system diagram of the RAN 104 and the core network 106 according to an embodiment.
  • the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116.
  • the RAN 104 may also be in communication with the core network 106.
  • the core network 106 shown in FIG. 1D may include a mobility management gateway (MME) 162, a serving gateway 164, and a packet data network (PDN) gateway 166. While each of the foregoing elements are depicted as part of the core network 106, it will be appreciated that any one of these elements may be owned and/or operated by an entity other than the core network operator.
  • MME mobility management gateway
  • PDN packet data network
  • the MME 162 may be connected to each of the eNode-Bs 162a, 162b, 162c in the RAN 104 via an S1 interface and may serve as a control node.
  • the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation/deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, and the like.
  • the MME 162 may also provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM or WCDMA.
  • the core network 106 may facilitate communications with other networks.
  • the core network 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices.
  • the core network 106 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the core network 106 and the PSTN 108.
  • IMS IP multimedia subsystem
  • the core network 106 may provide the WTRUs 102a, 102b, 102c with access to the networks 112, which may include other wired or wireless networks that are owned and/or operated by other service providers.
  • the base stations 180a, 180b, 180c may also provide mobility management functions, such as handoff triggering, tunnel establishment, radio resource management, traffic classification, quality of service (QoS) policy enforcement, and the like.
  • the ASN gateway 182 may serve as a traffic aggregation point and may be responsible for paging, caching of subscriber profiles, routing to the core network 106, and the like.
  • the air interface 116 between the WTRUs 102a, 102b, 102c and the RAN 104 may be defined as an R1 reference point that implements the IEEE 802.16 specification.
  • each of the WTRUs 102a, 102b, 102c may establish a logical interface (not shown) with the core network 106.
  • the logical interface between the WTRUs 102a, 102b, 102c and the core network 106 may be defined as an R2 reference point, which may be used for authentication, authorization, IP host configuration management, and/or mobility management.
  • SIP Notify 344 may be sent from UE2 304 to IM CN Subsystem 306.
  • the IM subsystem 306 may forward the request via SIP Notify 346 to SCC 308.
  • SCC 308 may forward the request to IM CN Subsystem 306 via SIP Notify 348, which forwards the request to UE1 302 via SIP Notify 350.
  • UE1 302 may accept the teardown by sending SIP 352 to IM CN Subsystem 306, which forwards the acceptance to SCC 308 via SIP 354, which may forward the acceptance to IM CN Subsystem 306 via SIP 356, which may forward the acceptance to UE2 304 via SIP 358.
  • HA 404 may inform WTRU1 412 of HoA1.
  • WTRU1 412 When establishing a communication session with another device, for example CN 402, WTRU1 412 may indicate that its address is HoA1. Therefore, packets sent during the session that are destined for WTRU1 412 may be addressed for HoA1. Packets addressed for HoA1 may be routed to HA 404.
  • HA 404 may receive a packet addressed for HoA1, may use Binding Table 406 to determine CoA1, and may forward the packet to WTRU1 using CoA1. By registering in this way, WTRU1 412 may move throughout Network 410, which may include changing its CoA, for example to CoA2.
  • the binding reference sub-option may associate a flow with one or more registered BIDs.
  • the HoA1/BID1 pair may be associated with CoA1 in Binding Table 406.
  • HA 404 may create an entry in Flow Table 408 for the flow associated with CN 402 and WTRU1 412.
  • the entry may include FID1, a traffic selector created by HA 404 and the action, in this case forward to CoA1, indicated by WTRU1 412 in the binding update.
  • WTRU1 412 may send the traffic selector to HA 404 as part of the binding update or in a different message. If a packet received by HA 404 matches the created traffic selector, it may be routed using the HoA/BID pair included in the flow table.
  • WTRU1 502 may participate in peer discovery.
  • Peer discovery may be initiated by WTRU1 502 or may be initiated by another device, for example WTRU2 504, HA1 506, HA2 508, and/or Auth/SCC 510.
  • WTRU1 502 may discover WTRU2 504.
  • WTRU1 502 and WTRU2 504 may exchange relevant information, for example addressing information.
  • the addressing information may include HoAs (e.g.
  • FIG. 6 illustrates another example IUT request and authorization scenario.
  • requests and authorizations are sent to and from the WTRUs via the HAs.
  • WTRU1 602, WTRU2 604, HA1 606, HA2 608, Auth/SCC 610, and CN 612 may be involved in the flow routing and/or IUT.
  • WTRU1 602 registers with HA1 606, and at 616 WTRU2 604 registers with HA2 608. The registration may be performed in a manner similar to the methods described above.
  • Flow1 may be established between CN 612 and WTRU1 602.
  • WTRU1 602 may engage in peer discovery.
  • WTRU1 602 may discover WTRU2 604.
  • WTRU1 602 and WTRU2 604 may exchange relevant information, for example addressing information.
  • the addressing information may include HoAs, CoAs, HA information, and the like.
  • WTRU1 602 may send IUT Prep Request 622 to HA1 606 which may request an IUT and/or request authorization for an IUT.
  • IUT Prep Request 622 may contain information regarding the type of or identity of an application utilizing Flow1.
  • IUT Prep Request 622 may include application data from an application associated with Flow1.
  • HA2 608 may modify its binding table and/or flow table.
  • WTRU2 604 may send IUT Prep Response 636 to HA1 606 to inform HA1 606 that WTRU2 604 is ready for the IUT.
  • HA1 606 may send IUT Prep Response 638 to WTRU1 602 to inform WTRU1 602 that IUT has been authorized and/ accepted.
  • IUT Prep Response 638 may also indicate that WTRU2 604 is ready for the IUT.
  • WTRU1 702 may register with HA1 706, and at 716 WTRU2 704 may register with HA2 708. The registration may be performed in a manner similar to the methods described above.
  • Flow1 may be established between CN 712 and WTRU1 702.
  • WTRU1 702, WTRU2 704, HA1 706, HA2 708 and/or Auth/SCC 710 may engage in peer discovery.
  • WTRU1 702 may discover WTRU2 704.
  • WTRU1 702 and WTRU2 704 may exchange relevant information, for example addressing information.
  • the addressing information may include HoAs, CoAs, HA information, and the like.
  • Auth/SCC 710 may be a logical part of HA1 706.
  • IUT Prep Request 724 may be sent to HA2 708 to request authorization for IUT.
  • IUT Prep Request 726 may be a modified SIP message and may include a variety of information such as, but not limited to, information regarding WTRU1 702, information regarding WTRU2 704, the identity of the application utilizing Flow1, data specific to the application utilizing Flow1, etc.
  • Auth/SCC 710 may send IUT Prep Request 726 to HA2 708.
  • IUT Prep Request 728 which may be a modified MIP message, may be sent from HA2 708 to WTRU2 704.
  • IUT Prep Request 728 may contain information regarding the type of or identity of an application utilizing Flow1.
  • IUT Prep Request 728 may include application data from an application associated with Flow1.
  • An example IUT Prep Request 728 may include information regarding the identity or other identifying information for WTRU1 702, for example an IP address, a HoA, and/or a CoA.
  • IUT Prep Request 728 may contain information regarding the identity, address, characteristics, and or the like of CN 712.
  • a unique identifier which may supplement or replace the BID/HoA pair.
  • the unique identifier may be a User Equipment Identification (UEID). If the devices are assigned UEIDs, then binding entries in the binding table of the HA (i.e. , entries that correspond to a unique CoA) may be uniquely identified using a HoA/BID/UEID triplet. For example, if the HoA is different for each WTRU, binding entries may be uniquely identified using either HoA/BID or UEID/BID (for MIP message exchange between the WTRUs and the HAs).
  • the triplet (HoA/BID/UEID) may be used to uniquely identify a binding entry in the case where the HoA is shared between multiple WTRUs.
  • WTRU2 804 may send HA 808 a BID.
  • the BID sent by WTRU2 804 may be the same as BID1 sent by WTRU1 802.
  • each entry in the binding table of HA 808 may be uniquely identified by the HoA/BID pair since WTRU1 802 and WTRU2 804 may be assigned different HoAs.
  • the binding table may optionally include unique UEIDs for WTRU1 and WTRU2 so that the corresponding binding entry for each device may be uniquely identified.
  • a first traffic selector may be created in the flow table for HA 808.
  • WTRU1 802 may send HA 808 a binding update including the traffic selector and a request to forward the packets that match the traffic selector using HoA1/BID1.
  • a traffic selector may be, for example, one or more parameters or filter that may be used to classify a packet.
  • WTRU1 802 may request that HA 808 forward the matching packets using CoA1.
  • WTRU1 802 may also send HA 808 a flow identification (FID) which is unique for the flow.
  • HA 808 may determine the FID and may or may not send the FID to WTRU1 802.
  • the packets for Flow 1 may match the Filter for Flow1 traffic selector as shown in Table 2.
  • HA 808 may then Forward the Packets Using the HoA1/BID1 pair.
  • HA 808 may identify CoA1 as the routing address unique to HoA1/BID1 pair based on its binding table.
  • HA 808 may tunnel the packets to WTRU1 802 located at CoA1.
  • WTRU1 802 may correspond to a smart phone for a subscriber.
  • WTRU2 804 may correspond to a TV for a subscriber.
  • WTRU3 806 may correspond to a sound system for a subscriber.
  • the subscriber may have established Flow1 while located in a different locale than WTRU2 804 and WTRU 806.
  • the subscriber may desire to perform an IUT such that the video data from Flow1 is redirected to WTRU2 804 and the sound data for Flow1 is redirected to WTRU3 806.
  • WTRU1 802 may initiate peer discovery 822 in order to perform an IUT.
  • WTRU1 802 may send WTRU3 806 an audio codec.
  • WTRU1 802 may send WTRU2 804 and WTRU 806 HoA1 such that WTRU2 804 and WTRU3 806 may configure HoA1 on a local port such that WTRU2 804 and WTRU3 806 may continue the download with CN 810 seamlessly.
  • WTRU1 802 may send MIP binding update 834 to HA 808.
  • MIP binding update 834 may create a traffic selector that matches all packets for Flow1 and may create a corresponding action to forward the packets to WTRU1 802.
  • MIP binding update 834 may also delete the traffic selectors or flow entries for WTRU2 804 and WTRU3 806 which correspond to Flow1.
  • HA 808 may update the flow table to reflect the entries shown in Table 2. After updating the flow table, at 836 HA 808 may begin redirecting Flow1 packets to WTRU1 802.
  • FIG. 10 illustrates an example signaling diagram for an IUT sequence flow using double tunneling.
  • WTRU1 1002 and WTRU2 1004 may be device capable of receiving flows.
  • HA1 1006 and HA2 1008 may be HAs that may facilitate an IUT and device mobility.
  • CN 1010 may be a source of a flow.
  • CN 1010 may be a content source, such as a video server.
  • WTRU1 1002 may register with HA1 1006.
  • WTRU1 1002 may send a binding update which may include a CoA and/or a BID.
  • WTRU1 1002 may send CoA1 and BID1 to HA1 1006 in order to register with HA1 1006.
  • CN 1010 may send Flow1 Packet addressed for HoA1 1022, for example as part of Flow1.
  • Flow1 Packet addressed for HoA1 1022 may be routed to HA1 1006.
  • HA1 1006 may receive Flow1 Packet addressed for HoA1 1022 and compare it to entries in the flow table for HoA1.
  • HA1 1006 may compare Flow1 Packet addressed for HoA1 1022 to the traffic selector for FID1. Since Flow1 Packet addressed for HoA1 1022 is part of Flow1 it may match the traffic selector for FID1.
  • HA1 1006 may forward the packet based on the HoA1/BID1 identification contained in the flow table.
  • WTRU1 1002 may de-tunnel the packet and forward the data contained in Flow1 Packet addressed for CoA1/HoA1 1024 to the appropriate application on WTRU1 1002 for processing.
  • CN 1010 may send Flow1 Packet addressed for HoA1 1034.
  • Flow1 Packet addressed for HoA1 1034 may be routed to HA1 1006.
  • HA1 1006 may identify the target address as HoA1.
  • HA1 1006 may compare Flow1 Packet addressed for HoA1 1034 to the traffic selectors included in the flow table for HoA1.
  • Flow1 Packet addressed for HoA1 1034 may match the traffic selector for FID2.
  • HA1 1006 may perform the action for FID2, which may be to forward the packet to HoA2/BID2.
  • HA1 1006 may determine an appropriate destination address for Flow1 Packet addressed for HoA1 1034 based on the HoA2/BID2 pair and the flow binding table for HA1 1006. HA1 1006 may determine that the appropriate destination is HoA2. HA1 1006 may append the HoA2 address to Flow1 Packet addressed for HoA1 1034 or tunnel Flow1 Packet addressed for HoA1 1034 to HoA2. The tunneled packet may be Flow1 Packet addressed for HoA2/HoA1 1036. HA1 1006 may send Flow1 Packet addressed for HoA2/HoA1 1036. Flow1 Packet addressed for HoA2/HoA1 1036 may be routed to HA2 1008.
  • FIG. 11 illustrates an example signaling diagram for an IUT sequence flow using two tunnels.
  • WTRU1 1102 and WTRU2 1104 may be device capable of receiving flows.
  • HA1 1106 and HA2 1108 may be HAs that may facilitate an IUT and device mobility.
  • CN 1110 may be a source of a flow.
  • CN 1110 may be a content source, such as a video server.
  • WTRU1 1102 may register with HA1 1106.
  • WTRU1 1102 may send a binding update which may include a CoA and/or a BID.
  • WTRU1 1102 may send CoA1 and BID1 to HA1 1106 in order to register with HA1 1106.
  • HA2 1108 may send HoA2 to WTRU2 1104, which may act as a HoA for WTRU2 1104.
  • WTRU2 1104 may act as a HoA for WTRU2 1104.
  • HA1 1106 may create a binding entry for WTRU1 1102.
  • An example binding entry for HA1 1106 is shown in Table 9, below.
  • Table 9 Home Address (HoA) Binding ID (BID) Care-of-Address (CoA) HoA1 BID1 CoA1
  • HA2 1108 may create a binding entry for WTRU2 1104.
  • Table 10 Home Address (HoA) Binding ID (BID) Care-of-Address (CoA) HoA2 BID2 CoA2
  • WTRU1 1102 may send MIP Binding Update 1130 to HA1 1102 in order to perform the IUT.
  • WTRU1 1002 may continue to receive part of Flow1, for example the video portion, and an IUT may be performed for other data in Flow1, for example audio data.
  • MIP Binding UPDATE 1130 may be included in multiple messages.
  • MIP Binding Update 1130 may include a an updated traffic selector for Flow1 video packets.
  • MIP Binding Update 1134 may include an traffic selector for Flow1 audio packets and may also include an action for packets which match the traffic selector. The action may be de-tunnel and forward.
  • HA2 1108 may replace the IP header of packets that match the traffic selector and forward the packets to a specified destination with a new IP header.
  • An example flow binding that may be created on the flow table for HoA2 on HA2 1008 is shown in Table 14.
  • Table 14 Flow Identification (FID) Traffic Selector Action FID1 Audio Filter for Flow1 De-Tunnel and Forward to HoA2/BID2
  • HA1 1106 may determine an appropriate destination address for Flow1 Video Packet addressed for HoA1 1138 based on the HoA1/BID1 pair and the flow binding table for HA1 1106. HA1 1106 may determine that the appropriate destination is CoA1. HA1 1106 may append the CoA1 address to Flow1 Video Packet addressed for HoA1 1138 or tunnel Flow1 Video Packet addressed for HoA1 1138 to CoA1. The tunneled packet may be Flow1 Video Packet addressed for CoA1/HoA1 1140. HA1 1106 may send Flow1 Video Packet addressed for CoA1/HoA1 1140. Flow1 Video Packet addressed for CoA1/HoA1 1140 may be routed to WTRU1 1102. At 1142, WTRU1 1002 may de-tunnel the packet and send the data to the appropriate application.
  • HA2 1108 may send Flow1 Audio Packet addressed for CoA2/HoA1 1148 to WTRU2 1104.
  • WTRU2 1104 may de-tunnel Flow1 Audio Packet addressed for CoA2/HoA1 1148 and forward the data to the appropriate application.
  • the IUT of Flow1 Audio data from WTRU1 1102 to WTRU2 1104 may be transparent to CN 1110.
  • HA2 1208 may send HoA2 to WTRU2 1204, which may act as a HoA for WTRU2 1204.
  • WTRU2 1204 may act as a HoA for WTRU2 1204.
  • HA1 1006 may create a binding entry for WTRU1 1202.
  • An example binding entry for HA1 1206 is shown in Table 15, below.
  • HA2 1208 may create a binding entry for WTRU2 1204.
  • An example binding entry for HA2 1208 is shown in Table 16, below.
  • part of the traffic addressed for HoA2 may be forwarded to HoA2/BID1 while some of the traffic may be forwarded to HoA2/BID2.
  • binding entries in Binding Table 1306 it may be determined that traffic forwarded to HoA2/BID1 may be routed to CoA_Y, and traffic forwarded to HoA2/BID2 may be routed to CoA_Z.
  • FIG. 14 illustrates an example modified binding reference sub-option for MIP messages.
  • the modified binding reference sub-option shown in FIG. 14 may be represented in MIPv6, although other formats may be used.
  • the binding reference sub-option may be modified to include HoA 1408 which may allow the binding entry specified for redirection in a flow table to be uniquely identified using an HoA/BID pair.
  • a UEID may be used to uniquely identify a binding entry in the binding table and/or flow table.
  • Sub-opt Type 1402 may specify a sub-option type.
  • Sub-opt Type 1402 may be an 8-bit unsigned integer.
  • Sub-opt Len 1404 may be the length of flow identification sub-option.
  • Sub-opt Len 1404 may be an 8-bit unsigned integer that may specify the sub-option length in octets.
  • BID 1406 and/or BID 1410 may represent binding table entries for an HA.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Multimedia (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Claims (15)

  1. Verfahren zur Übertragung eines Flusses von einer ersten drahtlosen Sende-/Empfangseinheit, WTRU, (502), wobei das Verfahren umfasst:
    Herstellen des Flusses mit einem Knoten (512), wobei der Fluss durch Senden einer ersten Anbindungsaktualisierung an einen Heimatagenten, HA, (506) hergestellt wird, wobei die erste Anbindungsaktualisierung einen ersten Verkehrsselektor zum Identifizieren von Paketen, die mit dem Fluss assoziiert sind, basierend auf einem Paketkopf umfasst;
    Senden einer Einheit-zu-Einheit-Übertragungs, IUT,-Vorbereitungsanforderung (522) an eine zweite WTRU (504);
    Empfangen einer IUT-Vorbereitungsantwort (536), die angibt, ob die zweite WTRU die IUT annimmt oder für die IUT bereit ist; und
    Senden unter der Bedingung, dass die zweite WTRU die IUT annimmt, einer zweiten Anbindungsaktualisierung (538) an den HA (506), wobei die zweite Anbindungsaktualisierung einen zweiten Verkehrsselektor zum Leiten von Paketen, die zum Fluss gehören, zur zweiten WTRU umfasst.
  2. Verfahren nach Anspruch 1, ferner umfassend ein Erkennen (520) der zweiten WTRU.
  3. Verfahren zur Übertragung eines Flusses an eine zwei drahtlose Sende-/Empfangseinheit, WTRU, (504), wobei das Verfahren umfasst:
    Empfangen einer Einheit-zu-Einheit-Übertragungs, IUT,-Vorbereitungsanforderung (522) von einer ersten WTRU (502);
    Durchführen einer Anwendungs-IUT-Vorbereitung (528), die ein Starten einer mit dem Fluss assoziierten Anwendung umfasst;
    Senden einer Anbindungsaktualisierung (530) an einen Heimatagenten, HA2, (508), wobei die Anbindungsaktualisierung einen Verkehrsselektor zum Leiten von Paketen, die zum Fluss gehören, zur zweiten WTRU umfasst, wobei der Verkehrsselektor zum Identifizieren von Paketen, die mit dem Fluss assoziiert sind, basierend auf einem Paketkopf ist; und
    Senden einer IUT-Vorbereitungsantwort (536) an die erste WTRU, die angibt, dass die zwei WTRU die IUT annimmt oder für die IUT bereit ist.
  4. Verfahren nach Anspruch 3, ferner umfassend:
    Senden einer IUT-Autorisierungsanforderung (524) an einen Autorisierungsknoten (510); und
    Empfangen als Antwort auf die IUT-Autorisierungsanforderung einer IUT-Autorisierungsantwort (526) vom Autorisierungsknoten.
  5. Verfahren nach Anspruch 3, ferner umfassend ein Senden eines IUT Ready (534) an einen anderen Heimatagenten, HA1, (506), um den anderen Heimatagenten zu informieren, dass die zweite WTRU für die IUT bereit ist.
  6. Erste drahtlose Sende-/Empfangseinheit, WTRU, (502), umfassend:
    einen Prozessor (118), der wenigstens konfiguriert ist zum:
    Herstellen eines Flusses mit einem Knoten (512), wobei der Fluss durch Senden einer ersten Anbindungsaktualisierung an einen Heimatagenten, HA, (506) hergestellt wird, wobei die erste Anbindungsaktualisierung einen ersten Verkehrsselektor zum Identifizieren von Paketen, die mit dem Fluss assoziiert sind, basierend auf einem Paketkopf umfasst;
    Senden einer Einheit-zu-Einheit-Übertragungs, IUT,-Vorbereitungsanforderung (522) an eine zweite WTRU (504);
    Empfangen einer IUT-Vorbereitungsantwort (536), die angibt, ob die zwei WTRU die IUT annimmt oder für die IUT bereit ist; und
    Senden unter der Bedingung, dass die zweite WTRU die IUT annimmt, einer zweiten Anbindungsaktualisierung (538) an den HA (506), wobei die zweite Anbindungsaktualisierung einen zweiten Verkehrsselektor zum Leiten von Paketen, die zum Fluss gehören, zur zweiten WTRU umfasst.
  7. WTRU nach Anspruch 6, wobei der Prozessor ferner zum Erkennen (520) der zweiten WTRU konfiguriert ist.
  8. Verfahren nach Anspruch 1 oder WTRU nach Anspruch 6, wobei die IUT-Vorbereitungsanforderung eine oder mehrere von Informationen, die mit einer den Fluss nutzenden Anwendung assoziiert sind, Identifikationsinformationen, die mit dem Knoten assoziiert sind, oder Charakteristiken umfasst, die mit dem Knoten assoziiert sind.
  9. Verfahren nach Anspruch 1 oder WTRU nach Anspruch 6, wobei ein Verkehrsselektor einen oder mehrere Parameter umfasst, die mit Feldern in einem Kopf eines Pakets verglichen werden, um ein Paket zu klassifizieren.
  10. Verfahren nach Anspruch 9 oder WTRU nach Anspruch 9, wobei der mindestens eine oder die mehreren Parameter Ursprungs- und/oder Ziel-IP-Adressen, Transportprotokollnummer, Ursprungs- und Zielportnummern, andere Felder in IP- und Köpfen höherer Schichten umfassen.
  11. Zweite drahtlose Sende-/Empfangseinheit, WTRU, (504), umfassend:
    einen Prozessor, der konfiguriert ist zum:
    Empfangen einer Einheit-zu-Einheit-Übertragungs. IUT-, Vorbereitungsanforderung (522) von einer ersten WTRU (502), wobei die IUT-Vorbereitungsanforderung mit der Übertragung eines Flusses assoziiert ist;
    Durchführen einer Anwendungs-IUT-Vorbereitung (528) durch Starten einer mit dem Fluss assoziierten Anwendung;
    Senden einer Anbindungsaktualisierung (530) an einen Heimatagenten, HA2, (508), wobei die Anbindungsaktualisierung einen Verkehrsselektor zum Leiten von Paketen, die zum Fluss gehören, zur zweiten WTRU umfasst, wobei der Verkehrsselektor zum Identifizieren von Paketen, die mit dem Fluss assoziiert sind, basierend auf einem Paketkopf ist; und
    Senden einer IUT-Vorbereitungsantwort (536) an die erste WTRU, die angibt, dass die zweite WTRU die IUT annimmt oder für die IUT bereit ist.
  12. WTRU nach Anspruch 11, wobei der Prozessor ferner konfiguriert ist zum:
    Senden einer IUT-Autorisierungsanforderung (524) an einen Autorisierungsknoten (510); und
    Empfangen als Antwort auf die IUT-Autorisierungsanforderung einer IUT-Autorisierungsantwort (526) vom Autorisierungsknoten.
  13. WTRU nach Anspruch 11, wobei der Prozessor ferner so konfiguriert ist, dass er ein IUT Ready (534) an einen anderen Heimatagenten, HA1, (506) sendet, um den anderen Heimatagenten zu informieren, dass die zweite WTRU für die IUT bereit ist.
  14. Verfahren nach Anspruch 3 oder WTRU nach Anspruch 11, wobei die IUT-Vorbereitungsanforderung eine oder mehrere von Informationen, die mit einer den Fluss nutzenden Anwendung assoziiert sind, Identifikationsinformationen, die mit dem Knoten assoziiert sind, oder Charakteristiken umfasst, die mit dem Knoten assoziiert sind.
  15. Verfahren nach Anspruch 3 oder WTRU nach Anspruch 11, wobei ein Verkehrsselektor einen oder mehrere Parameter umfasst, die mit Feldern in einem Kopf eines Pakets verglichen werden, um ein Paket zu klassifizieren.
EP14192181.7A 2010-04-16 2011-04-15 Unterstützung der übertragung zwischen einheiten mit mobilem internetprotokoll Not-in-force EP2840856B1 (de)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US32516310P 2010-04-16 2010-04-16
US32945610P 2010-04-29 2010-04-29
EP11716749.4A EP2559316B1 (de) 2010-04-16 2011-04-15 Unterstützung der übertragung zwischen einheiten mit mobilem internetprotokoll

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
EP11716749.4A Division EP2559316B1 (de) 2010-04-16 2011-04-15 Unterstützung der übertragung zwischen einheiten mit mobilem internetprotokoll

Publications (3)

Publication Number Publication Date
EP2840856A2 EP2840856A2 (de) 2015-02-25
EP2840856A3 EP2840856A3 (de) 2015-03-25
EP2840856B1 true EP2840856B1 (de) 2017-06-07

Family

ID=44237141

Family Applications (2)

Application Number Title Priority Date Filing Date
EP14192181.7A Not-in-force EP2840856B1 (de) 2010-04-16 2011-04-15 Unterstützung der übertragung zwischen einheiten mit mobilem internetprotokoll
EP11716749.4A Not-in-force EP2559316B1 (de) 2010-04-16 2011-04-15 Unterstützung der übertragung zwischen einheiten mit mobilem internetprotokoll

Family Applications After (1)

Application Number Title Priority Date Filing Date
EP11716749.4A Not-in-force EP2559316B1 (de) 2010-04-16 2011-04-15 Unterstützung der übertragung zwischen einheiten mit mobilem internetprotokoll

Country Status (7)

Country Link
US (2) US8873564B2 (de)
EP (2) EP2840856B1 (de)
JP (2) JP5685642B2 (de)
KR (2) KR20140092885A (de)
CN (1) CN102845125B (de)
TW (1) TWI527479B (de)
WO (1) WO2011130591A1 (de)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7356567B2 (en) 2004-12-30 2008-04-08 Aol Llc, A Delaware Limited Liability Company Managing instant messaging sessions on multiple devices
US8953559B2 (en) * 2011-10-24 2015-02-10 Electronics And Telecommunications Research Institute Method and apparatus for supporting network-based flow mobility
US9088583B2 (en) 2011-10-31 2015-07-21 Interdigital Patent Holdings, Inc. Method and apparatus for enabling multimedia synchronization
CN102497629A (zh) * 2011-12-13 2012-06-13 华为终端有限公司 一种触发lte单卡双待多模终端进行联合注册的方法及终端
EP3690179B1 (de) 2015-04-08 2021-09-08 NOV Canada ULC Bohrlochvibrationsanordnung und verfahren zur verwendung davon
CN114827698B (zh) * 2022-03-22 2024-02-02 北京字跳网络技术有限公司 一种播放信息的同步方法、装置、终端设备和存储介质
US11589104B1 (en) * 2022-06-17 2023-02-21 Userful Corporation Latency compensation for external networks

Family Cites Families (35)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7079499B1 (en) * 1999-09-08 2006-07-18 Nortel Networks Limited Internet protocol mobility architecture framework
US7333482B2 (en) * 2000-12-22 2008-02-19 Interactive People Unplugged Ab Route optimization technique for mobile IP
US7042879B2 (en) * 2001-11-02 2006-05-09 General Instrument Corporation Method and apparatus for transferring a communication session
US7342903B2 (en) * 2002-04-15 2008-03-11 Qualcomm Incorporated Methods and apparatus for the utilization of multiple uplinks in reverse tunneling
US7284068B1 (en) * 2002-06-20 2007-10-16 Cisco Technology, Inc. Technique for providing multi-homing capability in data networks
JP2005537765A (ja) 2002-09-03 2005-12-08 インターディジタル テクノロジー コーポレイション ユーザが開始するデバイス間、システム間、インターネットプロトコルアドレス間のハンドオフを提供する方法およびシステム
US7251496B2 (en) 2002-10-03 2007-07-31 Cisco Technology, Inc. Mobile director
GB0308980D0 (en) * 2003-04-17 2003-05-28 Orange Personal Comm Serv Ltd Telecommunications
GB2405052A (en) * 2003-08-12 2005-02-16 Orange Personal Comm Serv Ltd Packet data communications
FI20031258A0 (fi) * 2003-09-04 2003-09-04 Nokia Corp Sijainnin yksityisyys viestintäjärjestelmässä
EP1524806B1 (de) * 2003-10-18 2015-12-23 Samsung Electronics Co., Ltd. System und Verfahren zum Weiterreichen eines mobilen IP Endgeräts in einem drahtlosen Netzwerk
FI20031832A0 (fi) * 2003-12-15 2003-12-15 Nokia Corp Menetelmä virtojen siirtämiseksi tietoverkoissa
US20070230453A1 (en) * 2004-02-06 2007-10-04 Telecom Italia S.P.A. Method and System for the Secure and Transparent Provision of Mobile Ip Services in an Aaa Environment
US8046829B2 (en) * 2004-08-17 2011-10-25 Toshiba America Research, Inc. Method for dynamically and securely establishing a tunnel
WO2006068557A1 (en) * 2004-12-22 2006-06-29 Telefonaktiebolaget Lm Ericsson (Publ) Methods and mobile routers in a communication system for routing a data packet
GB2422272A (en) * 2005-01-14 2006-07-19 King S College London Network mobility
US7930387B2 (en) 2005-03-07 2011-04-19 National Institute Of Information And Communications Technology Location information server system and wireless communication system using the same
EP1764970A1 (de) * 2005-09-19 2007-03-21 Matsushita Electric Industrial Co., Ltd. Mobile Mehrfachschnittstellen Knoten mit gleichzeitiger Heim und Fremdnetzwerksverbindung
WO2007037016A1 (ja) * 2005-09-29 2007-04-05 Fujitsu Limited 通信システムにおける通信の切り替え方法
US8107448B2 (en) * 2005-10-14 2012-01-31 Panasonic Corporation Apparatus for reducing signalling data bursts in mobile network
JP5163130B2 (ja) * 2006-02-08 2013-03-13 日本電気株式会社 端末間セッションハンドオーバ方法、ネットワークシステムおよびプログラム
CA2641621A1 (en) 2006-02-09 2007-08-23 Telcordia Technologies, Inc. Method for adaptive seamless mobility of multimedia communication sessions
US7633917B2 (en) * 2006-03-10 2009-12-15 Cisco Technology, Inc. Mobile network device multi-link optimizations
US8249086B2 (en) * 2006-06-14 2012-08-21 Panasonic Corporation Apparatus for flow control
JP5031026B2 (ja) 2006-08-24 2012-09-19 パナソニック株式会社 通信管理装置及び位置管理装置
EP1933520A1 (de) * 2006-12-15 2008-06-18 Matsushita Electric Industrial Co., Ltd. Verlagerung eines lokalen Mobilitätsankers und Routenoptimierung während der Weiterreichung eines mobilen Knotens an einen anderen Netzwerkbereich
WO2008087937A1 (ja) * 2007-01-18 2008-07-24 Sharp Kabushiki Kaisha Ｍｏｂｉｌｅ ＩＰを利用した通信システム、移動端末、ホームエージェントおよびその通信方法
JPWO2008126357A1 (ja) * 2007-03-16 2010-07-22 パナソニック株式会社 移動端末及び通信管理装置
US8077686B2 (en) * 2007-07-20 2011-12-13 Marvell World Trade Ltd. Multiple packet data network support over trusted access
CN101369966A (zh) 2007-08-17 2009-02-18 华为技术有限公司 多媒体会话的媒体流转移方法及应用服务器和用户设备
EP3537845B1 (de) * 2007-09-27 2025-02-12 Sun Patent Trust System und verfahren zur auswahl eines vertrauenswürdigen zugangsnetzes
US7839874B2 (en) * 2007-10-31 2010-11-23 Marvell World Trade Ltd. System and method for reselection of a packet data network gateway when establishing connectivity
CN101582878B (zh) * 2008-05-13 2012-09-05 中国科学院声学研究所 一种针对时延敏感数据的传输方法
GB2466226B (en) * 2008-12-15 2012-11-14 King S College London Improvements in or relating to network mobility
US9137705B2 (en) * 2009-04-21 2015-09-15 Futurewei Technologies, Inc. Apparatus and method for home agent initiated flow binding

Also Published As

Publication number Publication date
EP2559316A1 (de) 2013-02-20
KR101539834B1 (ko) 2015-07-27
EP2840856A3 (de) 2015-03-25
US9210199B2 (en) 2015-12-08
EP2559316B1 (de) 2014-11-12
CN102845125B (zh) 2016-06-22
US8873564B2 (en) 2014-10-28
KR20140092885A (ko) 2014-07-24
CN102845125A (zh) 2012-12-26
WO2011130591A1 (en) 2011-10-20
KR20130030752A (ko) 2013-03-27
US20150003438A1 (en) 2015-01-01
US20120093062A1 (en) 2012-04-19
TWI527479B (zh) 2016-03-21
JP5685642B2 (ja) 2015-03-18
JP2015100126A (ja) 2015-05-28
TW201220872A (en) 2012-05-16
JP2013529415A (ja) 2013-07-18
EP2840856A2 (de) 2015-02-25

Similar Documents

Publication Publication Date Title
US9392495B2 (en) Method and apparatus for inter-user device transfer (IUT) in a network based mobility domain
US9210199B2 (en) Inter-unit transfer support using mobile internet protocol
US20120120845A1 (en) Peer discovery, target selection, and flow replication for inter user equipment transfers
EP3285519B1 (de) Transfer zwischen benutzergeräten (ue) für kollaborative sitzungen mit mediensitzungsinformationen
US20120084388A1 (en) Inter ue transfer between mobile internet protocol clients
US20110274041A1 (en) Dynamic peer discovery and inter-unit transfer (iut) using mobile internet protocol (mip)

Legal Events

Date Code Title Description
PUAL Search report despatched

Free format text: ORIGINAL CODE: 0009013

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

17P Request for examination filed

Effective date: 20141107

AC Divisional application: reference to earlier application

Ref document number: 2559316

Country of ref document: EP

Kind code of ref document: P

AK Designated contracting states

Kind code of ref document: A2

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

AK Designated contracting states

Kind code of ref document: A3

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

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 80/04 20090101AFI20150213BHEP

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: 20161128

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

AC Divisional application: reference to earlier application

Ref document number: 2559316

Country of ref document: EP

Kind code of ref document: P

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

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

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: 900073

Country of ref document: AT

Kind code of ref document: T

Effective date: 20170615

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

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

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: 602011038615

Country of ref document: DE

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20170607

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: 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: 20170607

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: 20170607

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: 20170908

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: 20170607

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: 20170907

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: 20170607

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 900073

Country of ref document: AT

Kind code of ref document: T

Effective date: 20170607

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: 20170607

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: 20170607

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: 20170607

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: 20170607

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: 20170907

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

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: 20170607

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: 20170607

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: 20170607

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: 20170607

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: 20170607

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

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: 20170607

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: 20171007

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: 20170607

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: 20170607

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602011038615

Country of ref document: DE

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: 20170607

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

Ref country code: GB

Payment date: 20180321

Year of fee payment: 8

26N No opposition filed

Effective date: 20180308

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: 20170607

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

Ref country code: DE

Payment date: 20180320

Year of fee payment: 8

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: 20170607

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20180430

REG Reference to a national code

Ref country code: IE

Ref legal event code: MM4A

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

Ref country code: LU

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

Effective date: 20180415

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

Ref country code: CH

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

Effective date: 20180430

Ref country code: LI

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

Effective date: 20180430

Ref country code: BE

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

Effective date: 20180430

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

Ref country code: FR

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

Effective date: 20180430

Ref country code: IE

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

Effective date: 20180415

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 602011038615

Country of ref document: DE

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

Effective date: 20190415

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: 20191101

Ref country code: GB

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

Effective date: 20190415

Ref country code: MT

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

Effective date: 20180415

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

Ref country code: TR

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: 20170607

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: 20110415

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: 20170607

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: 20170607

Ref country code: MK

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

Effective date: 20170607

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

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: 20170607