EP3035634B1 - Système et procédé de telecommunication pour l'établissement d'une connection rtc entre un premier point terminal et un second point terminal - Google Patents
Système et procédé de telecommunication pour l'établissement d'une connection rtc entre un premier point terminal et un second point terminal Download PDFInfo
- Publication number
- EP3035634B1 EP3035634B1 EP15197273.4A EP15197273A EP3035634B1 EP 3035634 B1 EP3035634 B1 EP 3035634B1 EP 15197273 A EP15197273 A EP 15197273A EP 3035634 B1 EP3035634 B1 EP 3035634B1
- Authority
- EP
- European Patent Office
- Prior art keywords
- endpoint
- connection
- quality
- stun
- qos
- 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
Links
- 238000000034 method Methods 0.000 title claims description 44
- 238000004891 communication Methods 0.000 claims description 12
- 238000004590 computer program Methods 0.000 claims description 9
- 230000002452 interceptive effect Effects 0.000 claims description 4
- 230000005540 biological transmission Effects 0.000 description 20
- 230000004044 response Effects 0.000 description 9
- 238000012913 prioritisation Methods 0.000 description 8
- 230000008901 benefit Effects 0.000 description 3
- 238000005457 optimization Methods 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 238000012360 testing method Methods 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000000704 physical effect Effects 0.000 description 2
- 238000013519 translation Methods 0.000 description 2
- 108700023290 Stanford University protocol Proteins 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000009826 distribution Methods 0.000 description 1
- 238000011156 evaluation Methods 0.000 description 1
- 230000002349 favourable effect Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000003780 insertion Methods 0.000 description 1
- 230000037431 insertion Effects 0.000 description 1
- 238000011835 investigation Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000001303 quality assessment method Methods 0.000 description 1
- 230000009467 reduction Effects 0.000 description 1
- 238000007493 shaping process Methods 0.000 description 1
- 230000011664 signaling Effects 0.000 description 1
- 238000003860 storage Methods 0.000 description 1
- 239000013589 supplement Substances 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/50—Allocation or scheduling criteria for wireless resources
- H04W72/56—Allocation or scheduling criteria for wireless resources based on priority criteria
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/46—Interconnection of networks
- H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/46—Interconnection of networks
- H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
- H04L12/4675—Dynamic sharing of VLAN information amongst network nodes
- H04L12/4683—Dynamic sharing of VLAN information amongst network nodes characterized by the protocol used
- H04L12/4695—VTP [VLAN trunking protocol]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
- H04L43/0811—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking connectivity
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/09—Mapping addresses
- H04L61/25—Mapping addresses of the same type
- H04L61/2503—Translation of Internet protocol [IP] addresses
- H04L61/256—NAT traversal
- H04L61/2575—NAT traversal using address mapping retrieval, e.g. simple traversal of user datagram protocol through session traversal utilities for NAT [STUN]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/09—Mapping addresses
- H04L61/25—Mapping addresses of the same type
- H04L61/2503—Translation of Internet protocol [IP] addresses
- H04L61/256—NAT traversal
- H04L61/2589—NAT traversal over a relay server, e.g. traversal using relay for network address translation [TURN]
-
- 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/1069—Session establishment or de-establishment
-
- 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/80—Responding to QoS
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/50—Allocation or scheduling criteria for wireless resources
- H04W72/54—Allocation or scheduling criteria for wireless resources based on quality criteria
- H04W72/542—Allocation or scheduling criteria for wireless resources based on quality criteria using measured or perceived quality
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/09—Mapping addresses
- H04L61/25—Mapping addresses of the same type
- H04L61/2503—Translation of Internet protocol [IP] addresses
- H04L61/2514—Translation of Internet protocol [IP] addresses between local and global IP addresses
Definitions
- the present invention relates to a method for establishing an RTC connection between a first end point and a second end point according to the preamble of claim 1 and a corresponding telecommunications arrangement according to claim 9.
- a typical telecommunications arrangement is based - in terms of real-time communication or RTC - on one of the IETF (Internet Engineering Taskforce) and W3C (World Wide Web Consortium) under the names RTCWeb or WebRTC (hereinafter the term "WebRTC” is synonymous for both Designations used.) Or generalizing under the name RTC standardized multimedia technology, in which a whole series of likewise standardized protocols is used.
- the method ICE Interactive Connectivity Establishment, RFC 5245
- STUN Session Traversal Utilities
- NAT Network Address Translation
- VoIP Voice over Internet Protocol
- RTP Real-time connection
- NAT Network Address & Port Translation
- a direct host-host connection (cf. Fig. 1 ) is of lower quality than one of the other two connections.
- the answer is that the scenarios shown above only show the logical structure, but do not deal with the physical properties.
- Fig. 5 (Logical network view above and two physical forms below) demonstrates this impressively; Although it is logically the same configuration, the quality of the connection via the two VPN routers (R1, R2) will differ significantly from the direct connection shown on the left (via Ethernet): The connection via the two VPN routers has in the Usually significantly lower quality of service or QoS values.
- a VPN can occur in all scenarios without being known to the ICE process. For security reasons, it is always worth taking QoS into account when assigning priorities.
- the STUN connectivity checks mentioned are carried out in the order defined by the above prioritization.
- the prioritization itself is not influenced by STUN or other criteria relevant to QoS.
- the WO 2013/043308 A1 discloses a system and method whereby the transmission path for telephone data packets transmitted during a VoIP telephone call is selected based on a test of the transmission quality of potential transmission paths immediately before the call is set up. The transmission route with the best transmission quality is selected first. If the transmission quality of another transmission path rises above that of the transmission path selected first, the transmission path with the best transmission quality is used for the call instead.
- the US 2014/0136718 A1 discloses simultaneously determining the transmission quality while finding potential transmission paths between two terminals and then taking the transmission quality into account when prioritizing the transmission paths.
- the US 8,484,543 B2 discloses a system and method whereby incoming calls from a first communication subscriber to a second communication subscriber can be controlled automatically based on information regarding the transmission quality.
- the second communication participant receives the information relating to the transmission quality, selects a transmission path based thereon and transmits information relating to the transmission path to the first communication participant.
- the method can be used together with the ICE standard.
- the US 2014/0006604 A1 discloses that a STUN message on a router device on a network is received by a client device on the network along a network path.
- the STUN message is evaluated for information that instructs the router device to change media that is then sent over the network path. If the evaluation indicates that the router device should change the media, the media is changed according to the information in the STUN message that indicates the attributes of the network.
- the object of the invention is to eliminate the disadvantages mentioned at the outset when establishing an RTC connection and to make RTC connections more efficiently in the future.
- the (computer-implemented) method for establishing an RTC connection between a first end point and a second end point in an IP network in which the known STUN connectivity check procedures of an ICE method are used, is carried out in the following manner : First, a list of possible connection routes - or even all possible connection routes - is created between the first end point and the second end point. Then for each of the possible connection paths on the list (also referred to as candidate) a respective priority is specified, which specifies the order in which the connectivity checks of the STUN method to be carried out in succession should be tried, whether a connection can be established between the first end point and the second end point via the connection path in question.
- the RTC connection between the first end point and the second end point is then established in accordance with the defined priority, with the procedure being that an attempt is first made to establish the RTC connection using the best priority connection path. If this succeeds, no further steps are necessary. If this fails for some reason, an attempt is subsequently made to establish the RTC connection with the connection path which has the next best priority. These attempts are made in accordance with the determined or determined order of priorities until an RTC connection is finally established.
- the invention is characterized in that not only the previously known criteria are used for determining the respective priority, but also that its respective service quality value is determined for each possible connection path and in the determination of the priority of this connection path on the relevant list comes in.
- This procedure means that by using the existing statistics on the respective quality of service (also referred to as QoS), which are sometimes taken into account for real-time applications, critical quality of service or QoS values are taken into account, which enables a more efficient establishment of corresponding real-time connections or RTC connections.
- QoS quality of service
- the first end point also transmits the quality of service values of the possible connection paths between the first end point and the second end point to other end points by using STUN messages. Since the expression "first end point" is not intended to be a restriction to a specific end point, all end points thus transmit knowledge of quality of service values to the other end points.
- the QoS data of the respective possible connection paths also as ICE candidate pairs exchanged
- each endpoint is enriched with its own QoS statistics with the corresponding information from the respective partner.
- quality of service values which are only known to network infrastructure elements (for example routers) but not to the end points, are inserted in STUN connectivity check messages (typically “request” and “response”) in order to inform the end points of information that they otherwise (i.e. would not have been available without the inventive method). It is preferably these network infrastructure elements themselves that make this insertion and thus enrich it with their own QoS knowledge.
- a router can use its existing information that the router queue or queue for a payload or user data connection of the "video" type currently has a packet loss rate (also known as a packet loss rate) of 15% for this direction insert what is called traffic shaping into the STUN response message.
- each group corresponds to at least one subnet of the relevant endpoints or a part thereof.
- a central point of the IP network is used to send the quality of service values available to it to the controlling end point (also referred to as an ICE controlling end point). Since such central points have a higher traffic volume, "better" QoS data are obtained for the forecasts.
- a central point of this type is, for example, a gateway, a session border controller or a media server (for example a server-based real-time application).
- CAC Call Admission Control
- a computer program or computer program product for carrying out the aforementioned method and a machine-readable data carrier on which such a computer program is stored are also considered to be part of the present invention.
- the object on which the invention is based is also achieved with a telecommunications arrangement which has a first end point, a second end point (and usually many other end points) and an IP network via which the end points are connected to one another, the end points being designed in this way are that they are suitable for carrying out the described method according to the invention.
- Fig. 4 shows an embodiment of an IP network-based telecommunications arrangement according to the invention using the example of many terminals TE1.1 - TE1.n (here, for example, located in a first subnet SN1) and TE2.1 - TE2.n (here, for example, located in a second subnet SN2 ).
- the end points EP1 and EP2 shown represent the end points of the connection under consideration (cf. Fig. 3 ); they are connected to each other via a NAT server and a TURN server (here, for example, located in a third subnet SN3). These servers are part of an IP network.
- the IP network also includes routers 32, 33, 34 or R1, R2, R3, a gateway 52, a CAC instance (Call Admission Control) 53 (which runs, for example, as software as part of a VoIP switch), one SBC (session border controller) 54, a media server 56 and a software distribution device 20, which is often also referred to as a deployment service. It should be added that other device types as end points of a connection (according to Fig. 1-3 ) can occur, such as a gateway 52 or an SBC 54. The present method is implemented decentrally from all end points.
- CAC instance Call Admission Control
- SBC session border controller
- a CD-ROM is symbolically represented as a data carrier 90 as a storage medium for a computer program 92 implementing the method according to the invention, which can be loaded into the software distribution device 20 for further distribution to the end points.
- a computer program 92 implementing the method according to the invention, which can be loaded into the software distribution device 20 for further distribution to the end points.
- the collective term EP1 - EPn is used for the endpoints in question without further specification.
- terminal includes physical devices, i.e. both hardware devices - such as (Video) telephones - as well as software applications that map the functionalities of these hardware devices, e.g. Telephone clients or WebRTC-based implementations of the various web browsers.
- hardware devices - such as (Video) telephones -
- software applications that map the functionalities of these hardware devices, e.g. Telephone clients or WebRTC-based implementations of the various web browsers.
- the respective assigned addresses are also specified for the various units, namely the host addresses HA1.2 at the endpoints EP1 and EP2, the server-reflective addresses SA1.2 at the NAT servers and the TURN server address TA the side of the TURN server TURN facing the end point EP1 and the relayed address RA on the side of the TURN server TURN facing the end point EP2.
- connection options of the two end points EP 1 and EP2 show two further examples of the connection options of the two end points EP 1 and EP2, namely acc. Fig. 1 direct and acc. Fig. 2 with the interposition of one NAT server NAT, each with the corresponding addresses.
- QoS Quality of service
- connection partner or partner group whereby the selected connection path (i.e. which NAT and possibly which TURN server was used) must also be taken into account.
- address and route groups are formed, for which common QoS criteria apply.
- NAT devices server reflexive address
- TURN servers TURN server and relay address
- connection candidates are started that can be expected to have the best QoS properties within the respective sublist or whose QoS prediction is not possible due to lack of data, there is a legitimate expectation that the cheapest connection will be found with as few attempts as possible.
- the prioritization described in the standard is used unchanged; with each connection, however, the endpoint EP1 - EPn learns and can optimize the prioritization. It should be noted that the statistical data can only be used for predictions for a certain time. Therefore, they should be automatically deleted after a time to be defined (timeout, for example. 30 seconds to a maximum of a few minutes), if no further connection to the same destination or via the same route has been established for a long time and the data is thereby verified and possibly updated could become.
- timeout for example. 30 seconds to a maximum of a few minutes
- the controlling end point is determined by ICE as before.
- Fig. 6 internal processes in endpoint EP1.
- endpoint EP2 only the trigger for the check in the opposite direction is shown in a simplified manner.
- the two shown STUN checks represent a possibly long series of STUN checks (for each of the 40 ICE address candidates, for example).
- the controlling end point EP1 thus leads the above Actions through.
- the controlled end point EP2 remains passive until the first connectivity check gets through to it. He answers him promptly and immediately initiates a connectivity check in the opposite direction ("Triggered Check” according to the standard), using the candidate that has already been unilaterally recognized as working.
- this candidate is selected as the connection, which the controlling endpoint in turn communicates to the controlled endpoint with a STUN message (in which a specific flag is set according to the standard). Then the media stream can flow: Apart from the priority sequence changed according to the invention and the transmission of the subnet identifier (suffix or mask) already described, the sequence shown above thus corresponds to the standard.
- the controlling end point is (if possible) placed on central points.
- the controlling end point EP1-EPn is preferably placed at central points (gateway, session border controller, media server) if one is involved in the current connection establishment. Since a larger volume of traffic is to be expected here, the likelihood that suitable QoS data is available is greater. This is useful, for example, for central conferences.
- QoS information is taken into account in the STUN Connectivity Check messages themselves.
- STUN-QoS checks is used according to the invention.
- ICE endpoint A For an ICE voice endpoint A, with IPv4 and IPv6 for host, server-reflexive and TURN relay addresses, there are already 6 possible receive transport addresses (IP / port) for Voice (S) RTP payload. The same applies to ICE endpoint B, which in the example already results in 36 STUN connectivity checks. If it is a video-enabled ICE endpoint, the number doubles. The same applies to screen sharing (if this is based on RTC video, as is the case with modern communication platforms, for example).
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Multimedia (AREA)
- Business, Economics & Management (AREA)
- General Business, Economics & Management (AREA)
- Quality & Reliability (AREA)
- Computer Security & Cryptography (AREA)
- Environmental & Geological Engineering (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Claims (9)
- Procédé d'établissement d'une connexion Realtime-Communication, RTC, entre un premier point terminal (EP1) et un deuxième point terminal (EP2) dans un réseau Internet Protocol, IP, en utilisant une procédure Interactive Connectivity Establishment for Session Traversal Utilities for Network Address Translator, ICE-STUN, Connectivity-Check comprenant les étapes suivantes réalisées par le premier point terminal (EP1) :- établissement d'une liste de modes de connexion possibles entre le premier point terminal (EP1) et le deuxième point terminal (EP2),- définition d'une priorité respective pour chaque mode de connexion possible figurant sur la liste et- établissement de la connexion RTC entre le premier point terminal (EP1) et le deuxième point terminal (EP2), par le fait que- il est d'abord essayé d'établir la connexion RTC en utilisant le mode de connexion ayant la meilleure priorité,- et si cela n'est pas possible, il est ensuite essayé d'établir la connexion RTC en utilisant le mode de connexion ayant respectivement la prochaine meilleure priorité, jusqu'à ce que le la connexion RTC soit effectivement établie,dans lequel la valeur de qualité de service respective est déterminée pour chaque mode de connexion possible et est prise en compte lors de la définition de sa priorité sur la liste ; et
dans lequel pour les modes de connexion dans la liste des modes de connexion possibles entre le premier point terminal (EP1) et le deuxième point terminal (EP2), des valeurs de qualité de service, qui sont seulement connues des éléments d'infrastructure du réseau comme en particulier les routeurs (32, 33, 34), sont insérées dans des messages STUN-Connectivity-Check afin de communiquer aux points terminaux (EP1, Ep2) des informations dont ils ne disposeraient pas autrement, et ces valeurs de qualité de service sont prises en compte par le premier point terminal (EP1) lors de la définition des priorités des modes de connexion. - Procédé selon la revendication 1,
caractérisé en ce que le premier point terminal (EP1) transmet les valeurs de qualité de service des modes de connexion possibles entre le premier point terminal (EP1) et le deuxième point terminal (EP2) en utilisant des messages STUN à d'autres points terminaux (EP3, ..., EPn). - Procédé selon la revendication 1 ou 2,
caractérisé en ce que des valeurs de qualité de service de connexions établies jusque-là sont prises en compte lors de la définition des priorités des modes de connexion possibles. - Procédé selon l'une quelconque des revendications précédentes,
caractérisé en ce que des groupes sont définis, qui comprennent respectivement au moins une partie des points terminaux (EP1 ; EP2 ; EP3) d'au moins un sous-réseau (SN1 ; SN2 ; SN3) respectif et exactement un mode de connexion à ce sous-réseau, dans lequel il est supposé que pour un mode de connexion défini aux différents points terminaux d'un groupe, la même valeur de qualité de service s'applique que celle qui a déjà été déterminée à partir des connexion précédentes ou existantes. - Procédé selon l'une quelconque des revendications précédentes,
caractérisé en ce qu'un point central du réseau IP, comme en particulier une passerelle (52), un Session Border Controller (54) ou un serveur média (56), est sélectionné en tant que premier point terminal (EP1) afin de fournir les valeurs de qualité de service pour l'exécution des étapes du procédé. - Procédé selon l'une quelconque des revendications précédentes,
caractérisé en ce que les valeurs de qualité de service déterminées pour les modes de connexion possibles sont enregistrées dans une instance centrale (53) et rendues accessibles à tous les points terminaux (EP1, EP2, EP3, ..., EPn). - Produit de programme informatique (92) pour la réalisation du procédé selon l'une quelconque des revendications précédentes.
- Support de données lisible par machine (90) sur lequel est enregistré le produit de programme informatique (92) selon la revendication 7.
- Système de télécommunication pour l'établissement d'une connexion Realtime-Communication, RTC, entre un premier point terminal (EP1) et un deuxième point terminal (EP2) dans un réseau Internet Protocol, IP, en utilisant une procédure Interactive Connectivity Establishment for Session Traversal Utilities for Network Address Translator, ICE-STUN, Connectivity-Check comprenant :le premier point terminal (EP1),le deuxième point terminal (EP2), etle réseau IP, via lequel le premier point terminal (EP1) et le deuxième point terminal (EP2) sont connectés l'un à l'autre par le biais d'éléments d'infrastructure de réseau comme en particulier des routeurs (32, 33, 34),dans lequel pour les modes de connexion dans la liste des modes de connexion possibles entre le premier point terminal (EP1) et le deuxième point terminal (EP2), des valeurs de qualité de service, qui sont seulement connues des éléments d'infrastructure du réseau comme en particulier les routeurs (32, 33, 34), sont insérées dans des messages STUN-Connectivity-Check afin de communiquer aux points terminaux (EP1, EP2) des informations dont ils ne disposeraient pas autrement, et ces valeurs de qualité de service sont prises en compte par le premier point terminal (EP1) lors de la définition des priorités des modes de connexion, etque le premier point terminal (EP1) est réalisé pour exécuter le procédé selon l'une quelconque des revendications 1 à 6.
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
DE102014018873.6A DE102014018873A1 (de) | 2014-12-16 | 2014-12-16 | Telekommunikationsanordnung und Verfahren zum Herstellen einer RTC-Verbindung zwischen einem ersten Endpunkt und einem zweiten Endpunkt |
Publications (2)
Publication Number | Publication Date |
---|---|
EP3035634A1 EP3035634A1 (fr) | 2016-06-22 |
EP3035634B1 true EP3035634B1 (fr) | 2020-05-20 |
Family
ID=54782495
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP15197273.4A Active EP3035634B1 (fr) | 2014-12-16 | 2015-12-01 | Système et procédé de telecommunication pour l'établissement d'une connection rtc entre un premier point terminal et un second point terminal |
Country Status (4)
Country | Link |
---|---|
US (4) | US9883521B2 (fr) |
EP (1) | EP3035634B1 (fr) |
CN (1) | CN105703970B (fr) |
DE (1) | DE102014018873A1 (fr) |
Families Citing this family (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10244003B2 (en) | 2014-09-25 | 2019-03-26 | Microsoft Technology Licensing, Llc | Media session between network endpoints |
US10171511B2 (en) | 2014-09-25 | 2019-01-01 | Microsoft Technology Licensing, Llc | Media session between network endpoints |
DE102014018873A1 (de) * | 2014-12-16 | 2016-06-30 | Unify Gmbh & Co. Kg | Telekommunikationsanordnung und Verfahren zum Herstellen einer RTC-Verbindung zwischen einem ersten Endpunkt und einem zweiten Endpunkt |
US10158679B2 (en) * | 2015-11-18 | 2018-12-18 | Microsoft Technology Licensing, Llc | Media session between network endpoints |
US10079863B2 (en) * | 2015-11-18 | 2018-09-18 | Microsoft Technology Licensing, Llc | Media session between network endpoints |
US10419544B2 (en) * | 2015-12-22 | 2019-09-17 | Ribbon Communications Operating Company, Inc. | Methods and apparatus for managing the use of IP addresses |
US10819755B1 (en) * | 2016-09-16 | 2020-10-27 | Ribbon Communications Operating Company, Inc. | Communications apparatus, systems, and methods for preventing and/or minimizing session data clipping |
US10230771B2 (en) * | 2016-10-27 | 2019-03-12 | Microsoft Technology Licensing, Llc | Media session |
CN108418789B (zh) * | 2018-01-22 | 2021-09-17 | 网宿科技股份有限公司 | 一种基于WebRTC的通信系统及其通信方法、信令服务器 |
EP3588892B1 (fr) * | 2018-06-27 | 2021-11-03 | Unify Patente GmbH & Co. KG | Procédé et système de sélection d'un candidat de connexion de communication pour la transmission d'un flux multimédia |
CN108990137B (zh) * | 2018-07-17 | 2021-06-01 | 广东小天才科技有限公司 | 一种ntp服务器的访问控制方法及可穿戴设备 |
US10939256B1 (en) * | 2020-07-22 | 2021-03-02 | Bandwidth, Inc. | Techniques for routing messages in a communications network |
US11811843B2 (en) * | 2021-08-11 | 2023-11-07 | Qualcomm Incorporated | Supporting quality of service for media communications |
CN113904974B (zh) * | 2021-10-09 | 2023-08-15 | 咪咕文化科技有限公司 | 智能路由方法、装置及设备 |
US20240064190A1 (en) * | 2022-08-19 | 2024-02-22 | Samsung Electronics Co., Ltd. | Method and apparatus for providing media-based qos for real-time communication service in mobile communication systems |
US12074785B2 (en) | 2022-10-25 | 2024-08-27 | Microsoft Technology Licensing, Llc | Logical link redundant paths |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20140006604A1 (en) * | 2012-06-29 | 2014-01-02 | Cisco Technology, Inc. | Resilient Video Encoding Control via Explicit Network Indication |
Family Cites Families (28)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6609002B1 (en) * | 1999-09-15 | 2003-08-19 | Hrl Laboratories, Llc | Method and apparatus for predictive QoS routing for broad band low earth satellite networks |
US8315271B2 (en) * | 2004-03-26 | 2012-11-20 | Qualcomm Incorporated | Method and apparatus for an ad-hoc wireless communications system |
US8401018B2 (en) * | 2004-06-02 | 2013-03-19 | Qualcomm Incorporated | Method and apparatus for scheduling in a wireless network |
US7697421B2 (en) * | 2005-04-21 | 2010-04-13 | Avaya Inc. | Method and apparatus for quality-of-service-based admission control |
US20070133516A1 (en) * | 2005-12-14 | 2007-06-14 | General Instrument Corporation | Method and apparatus for selecting a codec in a packet-switched communication network |
US9049096B2 (en) * | 2006-06-19 | 2015-06-02 | Qualcomm Incorporated | Data routing via lower layers in a communication system |
US8189470B2 (en) * | 2006-07-04 | 2012-05-29 | Sharp Kabushiki Kaisha | Communication apparatus and device, communication apparatus control method |
US7953010B2 (en) * | 2008-07-30 | 2011-05-31 | Avaya Inc. | System and method of controlling in-bound path selection based on historical and continuous path quality monitoring, assessment and predictions |
US8902805B2 (en) * | 2008-10-24 | 2014-12-02 | Qualcomm Incorporated | Cell relay packet routing |
US20100131617A1 (en) * | 2008-11-25 | 2010-05-27 | John Osborne | Method and system for differential transmission of web page structures |
JP5402150B2 (ja) * | 2009-03-27 | 2014-01-29 | 日本電気株式会社 | ルーティング装置、通信システム、及びルーティング方法 |
US8185660B2 (en) * | 2009-05-12 | 2012-05-22 | Cisco Technology, Inc. | Inter-working between network address type (ANAT) endpoints and interactive connectivity establishment (ICE) endpoints |
CN102082596A (zh) * | 2009-11-30 | 2011-06-01 | 中国移动通信集团江苏有限公司 | 一种基于双通道技术进行通信的方法和设备 |
US9264459B2 (en) * | 2010-12-16 | 2016-02-16 | Palo Alto Research Center Incorporated | SIP-based custodian routing in content-centric networks |
US9178917B2 (en) * | 2010-12-16 | 2015-11-03 | Palo Alto Research Center Incorporated | Custodian routing with network address translation in content-centric networks |
US8767716B2 (en) * | 2011-09-19 | 2014-07-01 | Vonage Network, Llc | Systems and methods of routing IP telephony data packet communications |
US8948356B2 (en) * | 2012-10-15 | 2015-02-03 | Twilio, Inc. | System and method for routing communications |
US9413792B2 (en) * | 2012-11-09 | 2016-08-09 | Microsoft Technology Licensing, Llc | Detecting quality of service for unified communication and collaboration (UC and C) on internetworks |
EP2784994A1 (fr) * | 2013-03-28 | 2014-10-01 | British Telecommunications public limited company | Système et procédé de routage multidiffusion |
EP2843875A1 (fr) * | 2013-08-30 | 2015-03-04 | British Telecommunications public limited company | Détermination et utilisation de mesures de performance de liaison |
US10291503B2 (en) * | 2013-09-26 | 2019-05-14 | Taiwan Semiconductor Manufacturing Co., Ltd. | File block placement in a distributed network |
US9325941B2 (en) * | 2014-05-30 | 2016-04-26 | Apple Inc. | Communication channel management for real-time applications |
US9661665B2 (en) * | 2014-09-02 | 2017-05-23 | Apple Inc. | Network connectivity protocol for real-time applications |
US10171511B2 (en) * | 2014-09-25 | 2019-01-01 | Microsoft Technology Licensing, Llc | Media session between network endpoints |
US10244003B2 (en) * | 2014-09-25 | 2019-03-26 | Microsoft Technology Licensing, Llc | Media session between network endpoints |
US9596272B2 (en) * | 2014-09-25 | 2017-03-14 | Microsoft Technology Licensing, Llc | Media session between network endpoints |
DE102014018873A1 (de) * | 2014-12-16 | 2016-06-30 | Unify Gmbh & Co. Kg | Telekommunikationsanordnung und Verfahren zum Herstellen einer RTC-Verbindung zwischen einem ersten Endpunkt und einem zweiten Endpunkt |
US20160269493A1 (en) * | 2015-03-10 | 2016-09-15 | Qualcomm Incorporated | Methods and devices to establish services between service and connectivity strata |
-
2014
- 2014-12-16 DE DE102014018873.6A patent/DE102014018873A1/de not_active Ceased
-
2015
- 2015-12-01 EP EP15197273.4A patent/EP3035634B1/fr active Active
- 2015-12-07 US US14/960,649 patent/US9883521B2/en active Active
- 2015-12-16 CN CN201510943103.6A patent/CN105703970B/zh active Active
-
2017
- 2017-12-12 US US15/838,714 patent/US10455595B2/en not_active Expired - Fee Related
-
2019
- 2019-09-24 US US16/580,109 patent/US10813105B2/en active Active
-
2020
- 2020-09-15 US US17/020,921 patent/US11357019B2/en active Active
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20140006604A1 (en) * | 2012-06-29 | 2014-01-02 | Cisco Technology, Inc. | Resilient Video Encoding Control via Explicit Network Indication |
Also Published As
Publication number | Publication date |
---|---|
US11357019B2 (en) | 2022-06-07 |
US20200413419A1 (en) | 2020-12-31 |
CN105703970B (zh) | 2020-05-15 |
US20200022153A1 (en) | 2020-01-16 |
EP3035634A1 (fr) | 2016-06-22 |
US20180103484A1 (en) | 2018-04-12 |
US10813105B2 (en) | 2020-10-20 |
US10455595B2 (en) | 2019-10-22 |
DE102014018873A1 (de) | 2016-06-30 |
US20160174239A1 (en) | 2016-06-16 |
CN105703970A (zh) | 2016-06-22 |
US9883521B2 (en) | 2018-01-30 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP3035634B1 (fr) | Système et procédé de telecommunication pour l'établissement d'une connection rtc entre un premier point terminal et un second point terminal | |
DE60215117T2 (de) | Mehrbenutzeranwendungen in multimedia-netzwerken | |
DE69927238T2 (de) | Mobil-IP mit Unterstützung für Dienstqualität | |
DE602005002831T2 (de) | Verfahren zur Bereitstellung einer Echtzeitkommunikationsverbindung | |
DE60212511T2 (de) | System und Verfahren zur Ermittlung von Datenflussqualitätsstatistiken für Echtzeitprotokolldatenflüsse | |
DE10301963A1 (de) | Verfahren für eine Klassifizierung von Netzwerk-Komponenten eines paket-orientierten Netzwerks | |
EP3031193B1 (fr) | Procédé, programme informatique, produit de programme informatique et dispositif de télécommunication destinés à transmettre des données de médias comprenant différents types de médias par l'intermédiaire d'un réseau sensible à la qualité du service | |
EP2193649A1 (fr) | Procédé et dispositif pour connecter des terminaux de communication en mode paquet | |
EP2387261B1 (fr) | Préparation d'une connexion de bout en bout d'un terminal à un réseau | |
DE112015007093B4 (de) | Kommunikationsvorrichtung und kommunikationsverfahren | |
EP1317820B1 (fr) | Procede pour etablir des liaisons avec des qualites de service predefinies dans un reseau de communication oriente paquet, a l'aide d'un gestionnaire de ressources | |
DE102005043239B4 (de) | Verfahren zum Aufbau und Verwalten einer Verbindung | |
EP2686995B1 (fr) | Procédé pour mettre en place une connexion de communication | |
EP1227632B1 (fr) | Procédé pour faire fonctionner un réseau de communications multimedia | |
EP2036313B1 (fr) | Procédé de gestion de liaisons de communication par l'intermédiaire de noeuds de traduction d'adresse réseau | |
WO2004100498A1 (fr) | Procede d'echange de donnees entre des elements de reseau dans des reseaux a differentes zones d'adresse | |
EP3959850B1 (fr) | Procédé de fourniture de données d'établissement de connexion ainsi qu'ensemble comprenant une pluralité de serveurs de communication et un intermédiaire | |
EP2649751B1 (fr) | Procédé et système de surveillance d'un système de communication | |
EP2016719B1 (fr) | Procédé, agent de réseau et gestionnaire de bande passante pour la gestion des largeurs de bande disponibles pour des connexions entre des terminaux d'un réseau de communication orienté par paquets | |
EP1319287B1 (fr) | Procede pour etablir des connexions a qualite de service garanti pour un reseau de communication comportant un gestionnaire de ressources | |
DE102005041617B3 (de) | Verfahren zur verbesserten Nutzung eines Schnittstellensystems mit Adresskomponenten | |
WO2004040849A1 (fr) | Procede et dispositif pour echanger des donnees par une liaison tunnel | |
WO2004002061A1 (fr) | Reseau de communication et procede pour faire fonctionner un tel reseau | |
WO2005101754A1 (fr) | Controle relatif aux sorties reseau | |
EP1542423A1 (fr) | Système de communication permettant d'utiliser plusieurs protocoles de communication |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
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 |
|
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 |
|
RAP1 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: UNIFY GMBH & CO. KG |
|
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: 20161214 |
|
RBV | Designated contracting states (corrected) |
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 |
|
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: 20190311 |
|
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: 20191218 |
|
GRAS | Grant fee paid |
Free format text: ORIGINAL CODE: EPIDOSNIGR3 |
|
GRAA | (expected) grant |
Free format text: ORIGINAL CODE: 0009210 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE PATENT HAS BEEN GRANTED |
|
RAP1 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: UNIFY GMBH & CO. KG |
|
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 Free format text: NOT ENGLISH |
|
REG | Reference to a national code |
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: 502015012616 Country of ref document: DE |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: REF Ref document number: 1273373 Country of ref document: AT Kind code of ref document: T Effective date: 20200615 |
|
REG | Reference to a national code |
Ref country code: LT Ref legal event code: MG4D |
|
REG | Reference to a national code |
Ref country code: NL Ref legal event code: MP Effective date: 20200520 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: NO Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20200820 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: 20200920 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: 20200821 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: 20200520 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: 20200520 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: 20200921 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: 20200520 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
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: 20200520 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: 20200520 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: 20200520 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: 20200820 |
|
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: 20200520 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: 20200520 |
|
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: 20200520 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: 20200520 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: 20200520 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: 20200520 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: 20200520 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: 20200520 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: 20200520 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R082 Ref document number: 502015012616 Country of ref document: DE Representative=s name: FRITZSCHE PATENT, DE Ref country code: DE Ref legal event code: R081 Ref document number: 502015012616 Country of ref document: DE Owner name: UNIFY PATENTE GMBH & CO. KG, DE Free format text: FORMER OWNER: UNIFY GMBH & CO. KG, 81739 MUENCHEN, DE |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R097 Ref document number: 502015012616 Country of ref document: DE |
|
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: 20200520 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: 20200520 |
|
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 |
|
26N | No opposition filed |
Effective date: 20210223 |
|
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: 20200520 |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: PL |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MC Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20200520 |
|
REG | Reference to a national code |
Ref country code: BE Ref legal event code: MM Effective date: 20201231 |
|
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: 20201201 Ref country code: LU Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20201201 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R079 Ref document number: 502015012616 Country of ref document: DE Free format text: PREVIOUS MAIN CLASS: H04L0029060000 Ipc: H04L0065000000 |
|
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: 20201231 Ref country code: LI Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20201231 |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: MM01 Ref document number: 1273373 Country of ref document: AT Kind code of ref document: T Effective date: 20201201 |
|
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 NON-PAYMENT OF DUE FEES Effective date: 20201201 |
|
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: 20200520 Ref country code: MT 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: 20200520 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: 20200520 |
|
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: 20200520 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: BE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20201231 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: GB Payment date: 20221227 Year of fee payment: 8 Ref country code: FR Payment date: 20221227 Year of fee payment: 8 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: DE Payment date: 20221228 Year of fee payment: 8 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R119 Ref document number: 502015012616 Country of ref document: DE |
|
GBPC | Gb: european patent ceased through non-payment of renewal fee |
Effective date: 20231201 |