EP3406058B1 - Verfahren zur handhabung von kommunikation zwischen einem telekommunikationsnetzwerk und einem nutzerendgerät - Google Patents

Verfahren zur handhabung von kommunikation zwischen einem telekommunikationsnetzwerk und einem nutzerendgerät Download PDF

Info

Publication number
EP3406058B1
EP3406058B1 EP17700251.6A EP17700251A EP3406058B1 EP 3406058 B1 EP3406058 B1 EP 3406058B1 EP 17700251 A EP17700251 A EP 17700251A EP 3406058 B1 EP3406058 B1 EP 3406058B1
Authority
EP
European Patent Office
Prior art keywords
user equipment
service data
data flow
label information
telecommunications network
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
EP17700251.6A
Other languages
English (en)
French (fr)
Other versions
EP3406058A1 (de
Inventor
Karl-Heinz Nenner
Dieter GLUDOVACZ
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.)
Deutsche Telekom AG
Original Assignee
Deutsche Telekom AG
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 Deutsche Telekom AG filed Critical Deutsche Telekom AG
Publication of EP3406058A1 publication Critical patent/EP3406058A1/de
Application granted granted Critical
Publication of EP3406058B1 publication Critical patent/EP3406058B1/de
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2408—Traffic characterised by specific attributes, e.g. priority or QoS for supporting different services, e.g. a differentiated services [DiffServ] type of service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/50—Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]
    • H04L45/507—Label distribution
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2483—Traffic characterised by specific attributes, e.g. priority or QoS involving identification of individual flows
    • 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/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]

Definitions

  • the present invention relates to a method for handling communication between a telecommunications network and a user equipment, wherein the communication between the telecommunications network and the user equipment comprises at least one service data flow between, on the one hand, the user equipment and, on the other hand, the telecommunications network or a gateway node of the telecommunications network.
  • the present invention relates to a telecommunications network for handling communication between a telecommunications network and a user equipment, wherein the communication between the telecommunications network and the user equipment comprises at least one service data flow between, on the one hand, the user equipment and, on the other hand, the telecommunications network or a gateway node of the telecommunications network.
  • the present invention relates to a gateway node and a user equipment for handling communication between a telecommunications network and a user equipment, wherein the communication between the telecommunications network and the user equipment comprises at least one service data flow between, on the one hand, the user equipment and, on the other hand, the telecommunications network or a gateway node of the telecommunications network.
  • the present invention relates to a program and to a computer program product for handling communication between a telecommunications network and a user equipment.
  • the packet data network is identified by an Access Point Name (APN) which may be provided by the user equipment but can also be determined by the mobile communication network.
  • APN Access Point Name
  • IP address Internet Protocol address
  • the activation of a PDN connection comprises the creation of a primary PDP context (Packet Data Protocol context).
  • PDP context Packet Data Protocol context
  • EPC evolved packet core
  • a (possibly default) Quality of Service (QoS) profile is also assigned to the default bearer and to the primary PDP context upon its establishment. It is also possible to assign a packet filter to the bearer / context so that only packets matching the filter are allowed to flow through the corresponding bearer / context.
  • either the existing quality-of-service profile and/or packet filter on the already established bearer / context may be modified, or an additional bearer / context sporting the new quality-of-service profile and/or packet filter is created.
  • this is called a secondary PDP context
  • a dedicated bearer While there may be only one default bearer / primary PDP context, more than one dedicated bearer / secondary PDP context are allowed to operate on the same packet data network connection.
  • the quality-of-service profile and/or packet filter might be different between the default bearer and the dedicated bearer(s) / the primary PDP context and the secondary PDP context(s), they all connect to the same packet data network (i.e. use the same APN), and they all use the same IP address of the user equipment.
  • a user equipment When it is necessary that a user equipment connects to another packet data network, it may open an additional packet data network connection.
  • the packet data network connection terminates in the user equipment (downstream) and in a so-called Packet Data Network Gateway (upstream).
  • the packet data networks that can be accessed on a given mobile communication network are then connected to the PDN Gateway, and it is the responsibility of the PDN Gateway to route the upstream packets to the proper packet data network. It can do this by mapping the bearer on which it receives the upstream packet to the packet data network - this mapping is established upon opening a default or dedicated bearer, or primary or secondary PDP context, respectively.
  • Downstream data packets received from a given packet data network are mapped onto the appropriate bearer in order to apply the desired quality-of-service profile (i.e. the quality-of-service profile assigned to that bearer) to the data packet.
  • US 2006/274706 A1 discloses a telecommunications system, which communicates internet packet data, carrying payload data including a plurality of different data types, with a mobile communications user equipment.
  • the system comprises a gateway support node (GGSN), a service support node (SGSN) and a radio network controller (RNC).
  • GGSN gateway support node
  • SGSN service support node
  • RNC radio network controller
  • At least one of the gateway support node (GGSN) and the user equipment (UE) are operable to: parse the payload data in each data packet; generate a radio access bearer sub-flow indicator indicating the number of different types of data in the payload and the number of symbols in each different data type; and form a transport frame including the sub-flow indicator.
  • the data packets are communicated between the radio network controller and the user equipment by detecting the sub-flow indicator, and in accordance with the sub-flow indicator arranging for the data from each of the different data fields to be communicated via a different radio access bearer providing different quality of service parameters appropriate for the different data type.
  • An object of the present invention is to provide a technically simple, and effective solution for flexibly handling communication between a telecommunications network and a user equipment, wherein the communication between the telecommunications network and the user equipment comprises at least one service data flow between, on the one hand, the user equipment (the user equipment being typically the termination point of the service data flow for downlink data packets), and, on the other hand, a gateway node of the telecommunications network (this gateway node - typically the packet data network gateway node - being typically the termination point of the service data flow for uplink data packets).
  • the object of the present invention is achieved by a method for handling communication between a telecommunications network and a user equipment according to claim 1.
  • an EPC bearer is no longer needed for providing the communication service of transmitting the service data flow between the user equipment and the telecommunications network (especially being a mobile communication network).
  • a bearer or a PDP context
  • such a bearer is typically associated with a specific quality-of-service profile and/or with a specific packet data network.
  • the different service data flows are able to be assigned a specific quality-of-service profile and/or a specific packet data network and hence can be handled independently from each other (in contrast to the case that such different service data flows would be transported within a bearer).
  • the PDN Gateways In a telecommunications network focused on the bearer concept, the PDN Gateways typically form the endpoints of the EPC bearers. However, not all packet data networks may be reachable from all PDN Gateways, depending on the configuration of the telecommunications network. Hence an appropriate PDN Gateway (one that connects to the desired packet data network as specified by the APN) is selected upon establishment of a PDN connection. It is therefore advantageously possible according to the present invention to simplify the handling of data transmissions between the telecommunications network, on the one hand, and the user equipment, on the other hand.
  • the data packets of the different service data flows are provided with a label information such that it is comparatively easily possible for any network node (that is aware of such label information) to apply the correct treatment (especially with respect to the transmission parameters to apply such as the quality-of-service profile and/or the endpoints (or destinations) of the data packets) to all data packets of a plurality of different service data flows.
  • the data packets typically comprise data packets being sent, by the user equipment, towards the telecommunications network (i.e. uplink or upstream data packets), and data packets being sent, by the gateway node of the telecommunications network, towards the user equipment (i.e. downlink or downstream data packets).
  • the label information is used for indicating the at least one service data flow such that any data packet belonging to the at least one service data flow and being transmitted either uplink (i.e. upstream) or downlink (i.e. downstream) (i.e. either in the direction from the user equipment to the gateway node or in the direction from the gateway node to the user equipment) are associated with the respective label information (identifying the service data flow).
  • the data packets of the service data flow comprise the respective label information, i.e. as a part of the data packets, especially as part of the header portion of the data packets.
  • the data packets of the service data flow are transmitted with the label information, i.e.
  • the label information is, strictly speaking, not part of the data packets. According to the present invention, it is likewise possible that these two variants (of the transportation of the label information) can be mixed in that for a first service data flow (to be transported between the user equipment and the telecommunications network), the label information is transmitted as part of the data packets, and for a second service data flow (to be transported between the user equipment and the telecommunications network), the data packets of the service data flow are transmitted with the label information.
  • the label information is indicative of at least one out of
  • any data packet belonging to the at least one service data flow and being transmitted either uplink or downlink comprises - at some point between the user equipment and the gateway node - the use of the label information
  • it is - at least for uplink data packets - not necessarily the user equipment that provides the upstream marking (label information) of the data packets for the identification of the packet data network and/or the quality-of-service profile.
  • the label information would be removed also in the downlink data packets, e.g. by the eNodeB, prior to forwarding the data packet to the user equipment.
  • a user equipment typically uses (or at least a user equipment is able to use) a plurality of different service data flows. Therefore, it is referred in the context of the present invention to "at least one service data flow".
  • at least one service data flow In situations where different service data flows are considered, in order to differentiate these different service data flows, the present document refers to the terms “first service data flow”, "second service data flow”, etc. However, typically the "at least one service data flow" can be identified with the "first service data flow”.
  • the label information is indicative of a quality-of-service level to be applied to the service data flow, and of at least one out of
  • the label information being indicative of a quality-of-service level, or quality-of-service profile, (of the (first) service data flow)
  • the communication between the telecommunications network and the user equipment comprises, besides the first service data flow, a second service data flow between the user equipment and the gateway node, wherein the label information for indicating the first service data flow corresponds to a first label information and a second label information is used for indicating the second service data flow such that any data packet belonging to the second service data flow and being transmitted in the direction from the user equipment to the gateway node or in the direction from the gateway node to the user equipment either comprises the second label information or is transmitted with the second label information, wherein preferably the first service data flow comprises first uplink data packets and first downlink data packets, wherein the second service data flow comprises second uplink data packets and second downlink data packets.
  • the different service data flows can be easily differentiated by the network nodes involved in transmitting these data packets.
  • the first label information forms meta information with respect to the data packets of the first service data flow and/or wherein the second label information forms meta information with respect to the data packets of the second service data flow, wherein preferably at least one of the data packets of the first service data flow and the data packets of the second service data flow are Internet Protocol (IP) data packets, and wherein preferably the first and/or second label information are part of custom or option fields in the header portion of the IP data packets or are part of the payload portion of the IP data packets.
  • IP Internet Protocol
  • an exchange of signaling information is performed such that the network nodes involved are made aware that the (first) label information is indicative of at least one termination point of the (first) service data flow and/or of a quality-of-service level to be applied to the (first) service data flow and/or that the second label information is indicative of at least one termination point of the second service data flow and/or of a quality-of-service level to be applied to the second service data flow.
  • the data packets of the first service data flow are matching a first packet filter
  • the data packets of the second service data flow are matching a second packet filter such that using the first label information with respect to data packets belonging to the first service data flow and being transmitted in the direction from the user equipment to the gateway node or in the direction from the gateway node to the user equipment corresponds to applying the first packet filter and/or such that using the second label information with respect to data packets belonging to the second service data flow and being transmitted in the direction from the user equipment to the gateway node or in the direction from the gateway node to the user equipment corresponds to applying the second packet filter.
  • the present invention relates to a telecommunications network according to claim 6.
  • an EPC bearer is no longer needed for providing the communication service of transmitting the service data flow between the user equipment and the telecommunications network (especially being a mobile communication network).
  • a specific quality-of-service profile and/or a specific packet data network is able to be assigned, hence making the handling of such data transmissions more flexible.
  • the gateway node corresponds to a packet gateway node, wherein especially the telecommunications network comprises additional network nodes between the user equipment and the gateway node, wherein the additional network nodes especially comprise a serving gateway and/or an eNodeB node responsible for the user equipment.
  • the different service data flows can be easily differentiated by network nodes such as additional network nodes between the user equipment and the gateway node, especially a serving gateway and/or an eNodeB node responsible for the user equipment.
  • the present invention relates to a gateway node of a telecommunications network according to claim 9.
  • the present invention relates to a user equipment according to claim 10.
  • each service data flow can be associated with or be assigned with a specific quality-of-service profile and/or a specific packet data network, hence making the handling of such data transmissions more flexible.
  • the present invention relates to a program comprising a computer readable program code which, when executed on a computer and/or on a network node of a telecommunications network, causes the computer and/or the network node of the telecommunications network to perform the inventive method.
  • the present invention relates to a computer program product for handling communication between a telecommunications network and a user equipment, the computer program product comprising a computer program stored on a storage medium, the computer program comprising program code which, when executed on a computer and/or on a network node of a telecommunications network, causes the computer and/or the network node of the mobile communication network to perform the inventive method.
  • a mobile communication network 100 is schematically shown as an example of a telecommunications network 100.
  • the term "telecommunications network” is mostly used in order to stress that the telecommunications network 100 is not necessarily a mobile communication network.
  • the invention is mostly explained based on the example of the telecommunications network 100 being a mobile communication network 100.
  • a fixed line telecommunications network 100 can be considered, e.g.
  • user equipments either in the form where user equipments (at least partly) have a wireline connection to the telecommunications network 100 and/or in the form where user equipments (at least partly) are wirelessly connected (at least regarding one meter or a couple of meters or 10 meters or a couple of 10 meters or 100 meters or a couple of 100 meters) to the telecommunications network 100 such as, e.g., using a WLAN or WIFI access to the telecommunications network.
  • the mobile communication network 100 - as an example of the telecommunications network 100 according to the present invention - comprises an access network 110 and a core network 120.
  • the telecommunications network 100 / mobile communication network 100 is preferably a cellular telecommunications network comprising typically a plurality of network cells (or radio cells), one of which is represented in Figure 1 by means of a solid line and reference sign 10.
  • typically a plurality of user equipments are camping on the telecommunications network 100 within the plurality of network cells or radio cells such as network cell 10 represented in Figure 1 , i.e. the user equipments are connected or are camping on a base station entity 111 that serves the radio cell 10.
  • the base station entity 111 is typically a base station, e.g. BTS (base transceiver station), NodeB or an eNodeB base station.
  • the mobile communication network 100 generally serves a certain number of user equipments.
  • a first user equipment 20, a second user equipment 21, and a third user equipment 22 are schematically represented.
  • the mobile communication network 100 comprises at least one network node providing a gateway functionality for the exchange of packet data from and to the user equipments 20, 21, 22.
  • typically only one user equipment is considered; therefore, the user equipment is typically referred to by means of reference sign 20, i.e. regarding the first user equipment 20.
  • a double-sided arrow, representing a connection with packet data exchange between the first user equipment 20 and the telecommunications network 100 is schematically shown in Figure 1 only with respect to the first user equipment 20.
  • the other user equipments 21, 22 are supporting a connection with packet data exchange towards the telecommunications network 100.
  • the network node providing the gateway functionality is also called gateway node 130 of the telecommunications network 100, and typically (or preferably) provides the functionality of the packet data network gateway or P-gateway.
  • the packet gateway or packet data network gateway is responsible to act as a sort of anchor of mobility between 3GPP and non-3GPP technologies, and provides connectivity from the respective user equipment (such as the first user equipment 20) to external packet data networks (not represented in Figure 1 ) by being the point of entry or exit of traffic for the respective user equipment (such as the first user equipment 20).
  • the packet gateway typically manages policy enforcement, packet filtration for users, charging support and legal interception.
  • the packet gateway typically provides packet filtering on a per-user basis, e.g. by deep packet inspection.
  • the additional network nodes typically comprise a serving gateway and/or an eNodeB node responsible for the user equipment 20.
  • the additional intermediate network node of the serving gateway is not explicitly represented (and designated by a reference sign) in Figure 1 .
  • the additional intermediate network node of the base station entity (or eNodeB) is represented by means of the exemplarily base station entity 111 that serves the radio cell 10.
  • the efforts for necessarily conducting the repeated packet filtering can advantageously be avoided - especially in case that the user equipment 20 requires a plurality of different service data flows - by means of using a label information (i.e. a first label information indicating a first service data flow of a plurality of service data flows) for indicating the at least one service data flow (i.e.
  • any data packet belonging to the at least one service data flow and being transmitted in the direction from the user equipment 20 to the gateway node 130 or in the direction from the gateway node 130 to the user equipment 20 either comprises the (first) label information or is transmitted with the (first) label information (i.e. in addition to the (first) label information), wherein the (first) label information is indicative of at least one out of
  • the label information indicative of the respective service data flow (i.e. the first label information indicating the first service data flow, the second label information indicating the second service data flow, etc.) needs to be shared or exchanged among or distributed to the concerned network nodes, i.e. the gateway node 130, the user equipment 20, as well as any additional intermediate network node, especially by means of exchanging signaling information such that the network nodes 20, 130 involved are made aware that the corresponding label information regarding each of the service data flows.
  • FIG. 2 the general communication diagram according to the present invention between the user equipment 20, the base station entity 111 (as an example of an additional intermediate network node between the user equipment 20 and the gateway node 130) and the gateway node 130 of the mobile communication network 100 is schematically shown.
  • Two service data flows are schematically shown: A first service data flow 201, and a second service data flow 202.
  • All service data flows 201, 202 comprise, over a certain period of time of their existence, a plurality of data packets, i.e. a plurality of data packets are associated to each of the different service data flows 201, 202 considered.
  • All service data flows, 201, 202 typically comprise both uplink data packets (i.e. upstream data packets, being directed from the user equipment 20 to the gateway node 130) and downlink data packets (i.e. downstream data packets, being directed from the gateway node 130 to the user equipment 20).
  • uplink data packets i.e. upstream data packets, being directed from the user equipment 20 to the gateway node 130
  • downlink data packets i.e. downstream data packets, being directed from the gateway node 130 to the user equipment 20.
  • this is not necessarily the case for each and every service data flow (i.e. a service data flow could also comprise (or at least within a certain time window or time interval comprise) only upstream data packets or only downstream data packets).
  • the uplink data packets of the first service data flow 201 are indicated by means of reference sign 311 and referred to a first uplink data packets; the downlink data packets of the first service data flow 201 are indicated by means of reference sign 312 and referred to a first downlink data packets.
  • the uplink data packets of the second service data flow 202 are indicated by means of reference sign 321 and referred to a second uplink data packets; the downlink data packets of the second service data flow 202 are indicated by means of reference sign 322 and referred to a second downlink data packets.
  • the data packets of the first service data flow 201 either comprise or are transmitted with the first label information 301
  • the data packets of the second service data flow 202 either comprise or are transmitted with the second label information 302.
  • Figure 2 also schematically shows a termination point 190 of the first service data flow 201 (also called first termination point 190), as well as a second termination point 191 of the second service data flow 202.
  • the termination points 190, 191 indicate the packet data networks the user equipment 20 is exchanging data with by using the first service data flow 201 and the second service data flow 202, respectively.
  • (EPC) bearers further include that there is no reason why a user equipment should use multiple IP addresses if it connects to multiple packet data networks, unless this is required by a particular packet data network (e.g. depending on the authority that assigns the IP address). Furthermore, the concept of bearers is specific to mobile networks and, hence, makes convergent networks that use other access systems difficult to achieve.
  • Another aspect of the use of (EPC) bearers (or PDP contexts) is that, in the uplink direction, it is the user equipment that decides to which packet data network (or termination point) a certain data packet is directed to. When using bearers, the data packet is transmitted using the corresponding bearer, and there is no possibility for the telecommunications network to make the decision on behalf of the user equipment, or to change / override the decision of the user equipment.
  • the use of bearers is replaced by an approach where service data flows are defined and then a quality-of-service profile information and/or an information about termination points of the service data flow is assigned to the service data flow. This is performed by using label information assigned to each of different service data flows.
  • a quality-of-service profile for the IMS signaling flow (first service data flow 201) is assigned and this quality-of-service profile is applied to all SIP packets that flow to and from the user equipment (identified by its IP address).
  • RTP packets i.e.
  • Second service data flow 202 Another service data flow (second service data flow 202) with another quality-of-service profile. Furthermore, when the user equipment connects to the internet, yet another service data flow (third service data flow) needs to be defined.
  • the manner how to send uplink packets to the correct PDN in conventional mobile communication networks is no longer usable, as the user equipment might use the same IP address for communication with multiple packet data networks (and there are no bearers by which to identify the desired packet data network), and there would - in conventional mobile communication networks - be no way to differentiate the data packets of different service data flows and to know the correct packet data network (e.g. in the example mentioned above with aspects such as packet filter overlap between packet flows (service data flows) destined for different packet data networks).
  • the present invention proposes to avoid such drawbacks of conventional telecommunications networks, especially mobile communication networks, by means of a "bearer-less" network architecture (and a bearer-less treatment of data packets) such that all data packets belonging to the same service data flow get the same quality-of-service treatment, and are directed to the same packet data network (e.g. all SIP signaling packets to/from a given user equipment).
  • Data packets that belong to another service data flow e.g. "normal" Internet traffic
  • Both the user equipment and the telecommunications network know the service data flow and the associated quality-of-service profile.
  • the present invention it is proposed to solve the issue of how to know which data packets to route to which packet data network by means of adding a marking (i.e. the label information) to (the data packets of) each service data flow, i.e. the packets of this service data flow are marked with an service data flow-specific label, hence the label information specific for that service data flow.
  • a marking i.e. the label information
  • this marking or label information it is advantageously possible according to the present invention that even network elements on the flow path that do not know the service data flow description, can still differentiate the service data flows and assign each data packet to a given service data flow (of typically a plurality of service data flows associated with a typical user equipment); this allows such network nodes to both apply the correct quality-of-service treatment (without knowing or negotiating quality-of-service profiles with other elements), and it allows them to identify the packet data network (associated to the respective service data flow) in question by virtue of the label information assigned or related to the service data flow.
  • a network element or a network node within the packet flow (i.e. typically between the gateway nodes 130 and the user equipment 20) that is responsible for flow policing may change the marking (i.e. the label information for the respective service data flow), for reasons of at least one out of the following:
  • such other network elements including the user equipment - except the gateway node -, do not need to have a concept of a (or the correct) packet data network, as this is inherently and indirectly specified by the marking label, i.e. the respective label information.
  • the service data flow label (i.e. the label information) can also be used to select / identify a specific gateway node 130 of the telecommunications network 100 (such as a PDN Gateway) that can serve the packet data network specified by the label information of the considered service data flow 201, 202.
  • a specific gateway node 130 of the telecommunications network 100 such as a PDN Gateway
  • the APN access point name

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Claims (12)

  1. Verfahren zur Handhabung von Kommunikation zwischen einem Telekommunikationsnetz (100) und einer Benutzerausrüstung (20),
    wobei die Kommunikation zwischen dem Telekommunikationsnetz (100) und der Benutzerausrüstung (20) mindestens einen Dienstdatenfluss (201) zwischen einerseits der Benutzerausrüstung (20) und andererseits einem Gateway-Knoten (130) des Telekommunikationsnetzes (100) umfasst,
    wobei der mindestens eine Dienstdatenfluss (201) Datenpakete umfasst,
    wobei die Datenpakete Datenpakete umfassen, die durch die Benutzerausrüstung (20) an das Telekommunikationsnetz (100) gesendet werden, sowie Datenpakete umfassen, die durch den Gateway-Knoten (130) des Telekommunikationsnetzes (100) an die Benutzerausrüstung (20) gesendet werden,
    wobei das Verfahren den Schritt des Verwendens einer Bezeichner-Information (301) zum Anzeigen des mindestens einen Dienstdatenflusses (201) umfasst, dergestalt, dass jedes Datenpaket, das dem mindestens einen Dienstdatenfluss (201) zugehörig ist und in der Richtung von der Benutzerausrüstung (20) zu dem Gateway-Knoten (130) oder in der Richtung von dem Gateway-Knoten (130) zu der Benutzerausrüstung (20) übertragen wird, entweder die Bezeichner-Information (301) umfasst oder mit der Bezeichner-Information (301) übertragen wird,
    wobei die Bezeichner-Information (301) ein auf den Dienstdatenfluss (201) anzuwendendes Dienstqualitätsniveau angibt, sowie mindestens eines von
    - einem Terminierungspunkt (190) des mindestens einen Dienstdatenflusses (201) und
    - beiden Terminierungspunkten (20, 190) des mindestens einen Dienstdatenflusses (201),
    wobei die Verwendung von Trägern durch die Verwendung der Bezeichner-Information (301) vermieden wird.
  2. Verfahren nach Anspruch 1,
    wobei die Kommunikation zwischen dem Telekommunikationsnetz (100) und der Benutzerausrüstung (20) neben dem ersten Dienstdatenfluss (201) noch einen zweiten Dienstdatenfluss (202) zwischen der Benutzerausrüstung (20) und dem Gateway-Knoten (130) umfasst,
    wobei die Bezeichner-Information (301) zum Anzeigen des ersten Dienstdatenflusses (201) einer ersten Bezeichner-Information (301) entspricht und eine zweite Bezeichner-Information (302) zum Anzeigen des zweiten Dienstdatenflusses (202) verwendet wird, dergestalt, dass jedes Datenpaket, das dem zweiten Dienstdatenfluss (202) zugehörig ist und in der Richtung von der Benutzerausrüstung (20) zu dem Gateway-Knoten (130) oder in der Richtung von dem Gateway-Knoten (130) zu der Benutzerausrüstung (20) übertragen wird, entweder die zweite Bezeichner-Information (302) umfasst oder mit der zweiten Bezeichner-Information (302) übertragen wird,
    wobei der erste Dienstdatenfluss (201) erste Uplink-Datenpakete (311) und erste Downlink-Datenpakete (312) umfasst,
    wobei der zweite Dienstdatenfluss (202) zweite Uplink-Datenpakete (321) und zweite Downlink-Datenpakete (322) umfasst.
  3. Verfahren nach einem der vorangehenden Ansprüche,
    wobei die erste Bezeichner-Information (301) Meta-Informationen in Bezug auf die Datenpakete des ersten Dienstdatenflusses (201) bildet und/oder wobei die zweite Bezeichner-Information (302) Meta-Informationen in Bezug auf die Datenpakete des zweiten Dienstdatenflusses (202) bildet,
    wobei mindestens eines der Datenpakete des ersten Dienstdatenflusses (201) und der Datenpakete des zweiten Dienstdatenflusses (202) Internet Protocol (IP)-Datenpakete sind, und
    wobei die erste und/oder die zweite Bezeichner-Information (301, 302) Teil von benutzerdefinierten oder Optionsfeldern im Header-Abschnitt der IP-Datenpakete sind oder Teil des Nutzdatenabschnitts der IP-Datenpakete sind.
  4. Verfahren nach einem der vorangehenden Ansprüche,
    wobei vor der Verwendung der Bezeichner-Information (301) zum Anzeigen des mindestens einen ersten Dienstdatenflusses (201) und/oder der zweiten Bezeichner-Information (302) zum Anzeigen des mindestens einen zweiten Dienstdatenflusses (202) ein Austausch von Zeichengabeinformationen durchgeführt wird, dergestalt, dass die beteiligten Netzknoten (20, 130) darüber in Kenntnis gesetzt werden, dass die Bezeichner-Information (301) mindestens einen Terminierungspunkt (190, 20) des ersten Dienstdatenflusses (201) und/oder ein auf den ersten Dienstdatenfluss (201) anzuwendendes Dienstqualitätsniveau anzeigt und/oder dass die zweite Bezeichner-Information (302) mindestens einen Terminierungspunkt (190, 20) des zweiten Dienstdatenflusses (202) und/oder ein auf den zweiten Dienstdatenfluss (202) anzuwendendes Dienstqualitätsniveau anzeigt.
  5. Verfahren nach einem der vorangehenden Ansprüche,
    wobei die Datenpakete des ersten Dienstdatenflusses (201) mit einem ersten Paketfilter übereinstimmen, und die Datenpakete des zweiten Dienstdatenflusses (202) mit einem zweiten Paketfilter übereinstimmen, dergestalt, dass unter Verwendung der ersten Bezeichner-Information (301) in Bezug auf Datenpakete, die zu dem ersten Dienstdatenfluss (201) gehören und in der Richtung von der Benutzereinrichtung (20) zu dem Gateway-Knoten (130) oder in der Richtung von dem Gateway-Knoten (130) zu der Benutzereinrichtung (20) übertragen werden, der Anwendung des ersten Paketfilters entspricht, und/oder dergestalt, dass die Verwendung der zweiten Bezeichner-Information (302) in Bezug auf Datenpakete, die zu dem zweiten Dienstdatenfluss (202) gehören und in der Richtung von der Benutzereinrichtung (20) zu dem Gateway-Knoten (130) oder in der Richtung von dem Gateway-Knoten (130) zu der Benutzereinrichtung (20) übertragen werden, der Anwendung des zweiten Paketfilters entspricht.
  6. Telekommunikationsnetz (100) zur Handhabung von Kommunikation zwischen dem Telekommunikationsnetz (100) und einer Benutzerausrüstung (20),
    wobei die Kommunikation zwischen dem Telekommunikationsnetz (100) und der Benutzerausrüstung (20) mindestens einen Dienstdatenfluss (201) zwischen einerseits der Benutzerausrüstung (20) und andererseits einem Gateway-Knoten (130) des Telekommunikationsnetzes (100) umfasst,
    wobei der mindestens eine Dienstdatenfluss (201) Datenpakete umfasst,
    wobei die Datenpakete Datenpakete umfassen, die durch die Benutzerausrüstung (20) an das Telekommunikationsnetz (100) gesendet werden, sowie Datenpakete umfassen, die durch den Gateway-Knoten (130) des Telekommunikationsnetzes (100) an die Benutzerausrüstung (20) gesendet werden,
    wobei das Telekommunikationsnetz so eingerichtet ist, dass eine Bezeichner-Information (301) zum Anzeigen des mindestens einen Dienstdatenflusses (201) verwendet wird, dergestalt, dass jedes Datenpaket, das dem mindestens einen Dienstdatenfluss (201) zugehörig ist und in der Richtung von der Benutzerausrüstung (20) zu dem Gateway-Knoten (130) oder in der Richtung von dem Gateway-Knoten (130) zu der Benutzerausrüstung (20) übertragen wird, entweder die Bezeichner-Information (301) umfasst oder mit der Bezeichner-Information (301) übertragen wird,
    wobei die Bezeichner-Information (301) ein auf den Dienstdatenfluss (201) anzuwendendes Dienstqualitätsniveau angibt, sowie mindestens eines von
    - einem Terminierungspunkt (190) des mindestens einen Dienstdatenflusses (201) und
    - beiden Terminierungspunkten (20, 190) des mindestens einen Dienstdatenflusses (201),
    wobei das Telekommunikationsnetz so eingerichtet ist, dass die Verwendung von Trägern durch die Verwendung der Bezeichner-Information (301) vermieden wird.
  7. Telekommunikationsnetz (100) nach Anspruch 6,
    wobei die Kommunikation zwischen dem Telekommunikationsnetz (100) und der Benutzerausrüstung (20) neben dem ersten Dienstdatenfluss (201) noch einen zweiten Dienstdatenfluss (202) zwischen der Benutzerausrüstung (20) und dem Gateway-Knoten (130) umfasst,
    wobei das Telekommunikationsnetz (100) so eingerichtet ist, dass die Bezeichner-Information (301) zum Anzeigen des ersten Dienstdatenflusses (201) einer ersten Bezeichner-Information (301) entspricht und eine zweite Bezeichner-Information (302) zum Anzeigen des zweiten Dienstdatenflusses (202) verwendet wird, dergestalt, dass jedes Datenpaket, das dem zweiten Dienstdatenfluss (202) zugehörig ist und in der Richtung von der Benutzerausrüstung (20) zu dem Gateway-Knoten (130) oder in der Richtung von dem Gateway-Knoten (130) zu der Benutzerausrüstung (20) übertragen wird, entweder die zweite Bezeichner-Information (302) umfasst oder mit der zweiten Bezeichner-Information (302) übertragen wird,
    wobei der erste Dienstdatenfluss (201) erste Uplink-Datenpakete (311) und erste Downlink-Datenpakete (312) umfasst,
    wobei der zweite Dienstdatenfluss (202) zweite Uplink-Datenpakete (321) und zweite Downlink-Datenpakete (322) umfasst.
  8. Telekommunikationsnetz (100) nach einem der Ansprüche 6 und 7,
    wobei der Gateway-Knoten (130) einem Paket-Gateway-Knoten entspricht,
    wobei insbesondere das Telekommunikationsnetz (100) zusätzliche Netzknoten zwischen der Benutzerausrüstung (20) und dem Gateway-Knoten (130) umfasst,
    wobei die zusätzlichen Netzknoten insbesondere einen bedienenden Gateway und/oder einen eNodeB-Knoten umfassen, die für die Benutzerausrüstung (20) verantwortlich sind.
  9. Gateway-Knoten (130) eines Telekommunikationsnetzes (100) zur Handhabung von Kommunikation zwischen dem Telekommunikationsnetz (100) und einer Benutzerausrüstung (20),
    wobei die Kommunikation zwischen dem Telekommunikationsnetz (100) und der Benutzerausrüstung (20) mindestens einen Dienstdatenfluss (201) zwischen einerseits der Benutzerausrüstung (20) und andererseits dem Gateway-Knoten (130) des Telekommunikationsnetzes (100) umfasst,
    wobei der mindestens eine Dienstdatenfluss (201) Datenpakete umfasst,
    wobei die Datenpakete Datenpakete umfassen, die durch die Benutzerausrüstung (20) an das Telekommunikationsnetz (100) gesendet werden, sowie Datenpakete umfassen, die durch den Gateway-Knoten (130) des Telekommunikationsnetzes (100) an die Benutzerausrüstung (20) gesendet werden,
    wobei der Gateway-Knoten (130) so eingerichtet ist, dass er eine Bezeichner-Information (301) erzeugt und/oder interpretiert,
    wobei die Bezeichner-Information (301) zum Anzeigen des mindestens einen Dienstdatenflusses (201) verwendet wird, dergestalt, dass jedes Datenpaket, das dem mindestens einen Dienstdatenfluss (201) zugehörig ist und in der Richtung von der Benutzerausrüstung (20) zu dem Gateway-Knoten (130) oder in der Richtung von dem Gateway-Knoten (130) zu der Benutzerausrüstung (20) übertragen wird, entweder die Bezeichner-Information (301) umfasst oder mit der Bezeichner-Information (301) übertragen wird,
    wobei die Bezeichner-Information (301) ein auf den Dienstdatenfluss (201) anzuwendendes Dienstqualitätsniveau angibt, sowie mindestens eines von
    - einem Terminierungspunkt (190) des mindestens einen Dienstdatenflusses (201) und
    - beiden Terminierungspunkten (20, 190) des mindestens einen Dienstdatenflusses (201),
    wobei der Gateway-Knoten (130) so eingerichtet ist, dass die Verwendung von Trägern durch Verwendung der Bezeichner-Information (301) vermieden wird.
  10. Benutzerausrüstung (20) eines Telekommunikationsnetzes (100) zur Handhabung von Kommunikation zwischen dem Telekommunikationsnetz (100) und der Benutzerausrüstung (20), wobei die Kommunikation zwischen dem Telekommunikationsnetz (100) und der Benutzerausrüstung (20) mindestens einen Dienstdatenfluss (201) zwischen einerseits der Benutzerausrüstung (20) und andererseits dem Gateway-Knoten (130) des Telekommunikationsnetzes (100) umfasst,
    wobei der mindestens eine Dienstdatenfluss (201) Datenpakete umfasst,
    wobei die Datenpakete Datenpakete umfassen, die durch die Benutzerausrüstung (20) an das Telekommunikationsnetz (100) gesendet werden, sowie Datenpakete umfassen, die durch den Gateway-Knoten (130) des Telekommunikationsnetzes (100) an die Benutzerausrüstung (20) gesendet werden,
    wobei die Benutzerausrüstung (20) so eingerichtet ist, dass sie eine Bezeichner-Information (301) erzeugt und/oder interpretiert,
    wobei die Bezeichner-Information (301) zum Anzeigen des mindestens einen Dienstdatenflusses (201) verwendet wird, dergestalt, dass jedes Datenpaket, das dem mindestens einen Dienstdatenfluss (201) zugehörig ist und in der Richtung von der Benutzerausrüstung (20) zu dem Gateway-Knoten (130) oder in der Richtung von dem Gateway-Knoten (130) zu der Benutzerausrüstung (20) übertragen wird, entweder die Bezeichner-Information (301) umfasst oder mit der Bezeichner-Information (301) übertragen wird,
    wobei die Bezeichner-Information (301) ein auf den Dienstdatenfluss (201) anzuwendendes Dienstqualitätsniveau angibt, sowie mindestens eines von
    - einem Terminierungspunkt (190) des mindestens einen Dienstdatenflusses (201), und
    - beiden Terminierungspunkten (20, 190) des mindestens einen Dienstdatenflusses (201),
    wobei die Benutzerausrüstung (20) so eingerichtet ist, dass die Verwendung von Trägern durch die Verwendung der Bezeichner-Information (301) vermieden wird.
  11. Programm, das einen computerlesbaren Programmcode umfasst, der, wenn er auf einem Computer und/oder in einem Netzknoten eines Telekommunikationsnetzes (100) ausgeführt wird, den Computer und/oder den Netzknoten des Telekommunikationsnetzes (100) veranlasst, das Verfahren nach einem der Ansprüche 1 bis 5 durchzuführen.
  12. Computerprogrammprodukt zur Handhabung von Kommunikation zwischen einem Telekommunikationsnetz (100) und einer Benutzerausrüstung (20), wobei das Computerprogrammprodukt ein auf einem Speichermedium gespeichertes Computerprogramm umfasst, wobei das Computerprogramm Programmcode umfasst, der, wenn er auf einem Computer und/oder in einem Netzknoten eines Telekommunikationsnetzes (100) ausgeführt wird, den Computer und/oder den Netzknoten des mobilen Kommunikationsnetzes (100) veranlasst, das Verfahren nach einem der Ansprüche 1 bis 5 auszuführen.
EP17700251.6A 2016-01-19 2017-01-11 Verfahren zur handhabung von kommunikation zwischen einem telekommunikationsnetzwerk und einem nutzerendgerät Active EP3406058B1 (de)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
EP16151833 2016-01-19
PCT/EP2017/050483 WO2017125295A1 (en) 2016-01-19 2017-01-11 Method for handling communication between a telecommunications network and a user equipment

Publications (2)

Publication Number Publication Date
EP3406058A1 EP3406058A1 (de) 2018-11-28
EP3406058B1 true EP3406058B1 (de) 2021-03-03

Family

ID=55182237

Family Applications (1)

Application Number Title Priority Date Filing Date
EP17700251.6A Active EP3406058B1 (de) 2016-01-19 2017-01-11 Verfahren zur handhabung von kommunikation zwischen einem telekommunikationsnetzwerk und einem nutzerendgerät

Country Status (6)

Country Link
US (1) US10897425B2 (de)
EP (1) EP3406058B1 (de)
JP (1) JP6649496B2 (de)
KR (1) KR102165163B1 (de)
CN (1) CN108370351B (de)
WO (1) WO2017125295A1 (de)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11178706B2 (en) * 2020-01-29 2021-11-16 Microsoft Technology Licensing, Llc Just in time connection configuration stored in SIM profile
ES2970528T3 (es) * 2021-06-18 2024-05-29 Deutsche Telekom Ag Método para el enrutamiento de paquetes de datos, entre una pluralidad de nodos de red de una red de telecomunicaciones, mientras se tiene en cuenta la intensidad de energía con respecto a la transmisión de tales paquetes de datos, red de telecomunicaciones o nodo de red, programa y medio legible por ordenador

Family Cites Families (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6865185B1 (en) * 2000-02-25 2005-03-08 Cisco Technology, Inc. Method and system for queuing traffic in a wireless communications network
US7106718B2 (en) 2001-02-09 2006-09-12 Telefonaktiebolaget Lm Ericsson (Publ) Signaling quality of service class for use in multimedia communicatations
US7383048B2 (en) 2002-12-04 2008-06-03 Nokia Corporation Transmission of data packets by a node
GB2399712A (en) * 2003-03-17 2004-09-22 Orange Personal Comm Serv Ltd Telecommunications apparatus and method for multiple data type packets
EP1869929B1 (de) * 2005-04-13 2015-11-11 Vringo Infrastructure Inc. Techniken zur funkstrecken-betriebsmittelverwaltung in paketverkehr führenden drahtlosen netzwerken
CN101326845B (zh) 2005-12-12 2012-06-27 艾利森电话股份有限公司 规定数据分组的传输中的服务质量的方法和装置
JP4867806B2 (ja) 2007-06-15 2012-02-01 株式会社日立製作所 通信システム、サーバ、制御装置および通信装置
US8428063B2 (en) * 2009-03-31 2013-04-23 Comcast Cable Communications, Llc Access network architecture having dissimilar access sub-networks
WO2010112077A1 (en) * 2009-04-02 2010-10-07 Telefonaktiebolaget Lm Ericsson (Publ) Techniques for handling network traffic
US20120281536A1 (en) * 2009-06-12 2012-11-08 Cygnus Broadband, Inc. Systems and methods for detection for prioritizing and scheduling packets in a communication network
US8537829B2 (en) * 2010-09-15 2013-09-17 Cisco Technology, Inc. Paging control in communication networks
US9344874B2 (en) * 2011-03-15 2016-05-17 Nec Corporation Mobility management system, mobility management method, access GW apparatus, mobility management control apparatus, and computer-readable medium
JP5841269B2 (ja) * 2012-01-20 2016-01-13 ▲ホア▼▲ウェイ▼技術有限公司 サービス品質を制御するための方法、デバイスおよびシステム
US8989207B2 (en) * 2012-09-27 2015-03-24 Intel Corporation System and method for resource allocation priority in multiple-persona cellular devices
JP6115961B2 (ja) 2014-10-24 2017-04-19 テレフオンアクチーボラゲット エルエム エリクソン（パブル） ネットワークトラヒックを処理するための技術
US9716653B2 (en) * 2014-11-18 2017-07-25 Hauwei Technologies Co., Ltd. System and method for flow-based addressing in a mobile environment
CN105227396B (zh) 2015-09-01 2018-09-18 厦门大学 一种面向移动通信网络的次等内容推荐分发系统及其方法

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
US10897425B2 (en) 2021-01-19
WO2017125295A1 (en) 2017-07-27
JP6649496B2 (ja) 2020-02-19
CN108370351B (zh) 2022-09-20
US20190028395A1 (en) 2019-01-24
EP3406058A1 (de) 2018-11-28
KR20180113986A (ko) 2018-10-17
CN108370351A (zh) 2018-08-03
JP2019505123A (ja) 2019-02-21
KR102165163B1 (ko) 2020-10-14

Similar Documents

Publication Publication Date Title
US11317314B2 (en) Techniques for handling network traffic
EP2441211B1 (de) Leistungsüberwachung in einem kommunikationsnetz
KR101792378B1 (ko) 모바일 통신 시스템에서 서비스 품질 제어의 지원
US8467291B2 (en) Policy control with predefined rules
CN114698022A (zh) 获取数据包延迟参数的方法、系统和装置
EP2933964A1 (de) Verfahren und vorrichtung zur übertragung von datenverkehr
EP3406058B1 (de) Verfahren zur handhabung von kommunikation zwischen einem telekommunikationsnetzwerk und einem nutzerendgerät
WO2018167254A1 (en) Unique qos marking ranges for smfs in a 5g communications network
EP2740310B1 (de) Implementierung von paketdatendiensten in einem mobilen kommunikationsnetz

Legal Events

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

Free format text: STATUS: UNKNOWN

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

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)
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20190719

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

GRAJ Information related to disapproval of communication of intention to grant by the applicant or resumption of examination proceedings by the epo deleted

Free format text: ORIGINAL CODE: EPIDOSDIGR1

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

Free format text: STATUS: EXAMINATION IS IN PROGRESS

INTG Intention to grant announced

Effective date: 20200909

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

INTC Intention to grant announced (deleted)
INTG Intention to grant announced

Effective date: 20201014

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

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

Free format text: STATUS: GRANT OF PATENT IS INTENDED

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

Ref legal event code: REF

Ref document number: 1368458

Country of ref document: AT

Kind code of ref document: T

Effective date: 20210315

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602017033743

Country of ref document: DE

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG9D

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

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

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

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

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

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

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20210303

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1368458

Country of ref document: AT

Kind code of ref document: T

Effective date: 20210303

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

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

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

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

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

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

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

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

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

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

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

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602017033743

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04L0012801000

Ipc: H04L0047100000

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

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

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

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

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602017033743

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

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

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

26N No opposition filed

Effective date: 20211206

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

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

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

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

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

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

Effective date: 20220111

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20220131

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

Ref country code: GB

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

Effective date: 20220111

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

Ref country code: BE

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

Effective date: 20220131

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

Ref country code: CH

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

Effective date: 20220131

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

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

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

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

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

Ref country code: DE

Payment date: 20231212

Year of fee payment: 8