EP0993718B1 - Bestimmung von trägerdiensten in einem funkzugriffsnetz - Google Patents

Bestimmung von trägerdiensten in einem funkzugriffsnetz Download PDF

Info

Publication number
EP0993718B1
EP0993718B1 EP98929456A EP98929456A EP0993718B1 EP 0993718 B1 EP0993718 B1 EP 0993718B1 EP 98929456 A EP98929456 A EP 98929456A EP 98929456 A EP98929456 A EP 98929456A EP 0993718 B1 EP0993718 B1 EP 0993718B1
Authority
EP
European Patent Office
Prior art keywords
tcp
network
radio access
access network
service
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.)
Expired - Lifetime
Application number
EP98929456A
Other languages
English (en)
French (fr)
Other versions
EP0993718A2 (de
Inventor
Sami Huusko
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.)
Nokia Oyj
Original Assignee
Nokia Oyj
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 Nokia Oyj filed Critical Nokia Oyj
Publication of EP0993718A2 publication Critical patent/EP0993718A2/de
Application granted granted Critical
Publication of EP0993718B1 publication Critical patent/EP0993718B1/de
Anticipated expiration legal-status Critical
Expired - Lifetime legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/18—Negotiating wireless communication parameters
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
    • H04L69/168—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP] specially adapted for link layer protocols, e.g. asynchronous transfer mode [ATM], synchronous optical network [SONET] or point-to-point protocol [PPP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2101/00—Indexing scheme associated with group H04L61/00
    • H04L2101/60—Types of network addresses
    • H04L2101/618—Details of network addresses
    • H04L2101/663—Transport layer addresses, e.g. aspects of transmission control protocol [TCP] or user datagram protocol [UDP] ports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/26—Resource reservation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/04—Network layer protocols, e.g. mobile IP [Internet Protocol]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/06—Transport layer protocols, e.g. TCP [Transport Control Protocol] over wireless
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/02—Inter-networking arrangements

Definitions

  • the invention relates generally to cordless telecommunications systems, and particularly to supporting TCP/IP services in a cellular radio access network connected to a telecommunications network offering TCP/IP services.
  • WO-A1-9710684 discloses a messaging system for providing teleservices for facsimile and short massages in a DECT system.
  • UMTS Universal Mobile Communication System
  • FPLMTS Future Public Land Mobile Telecommunication System
  • IMT-2000 International Mobile Telecommunication 2000
  • ETSI European Telecommunications Standards Institute
  • ITU International Telecommunication Union
  • UMTS Like all mobile communications systems, UMTS produces cordless data transmission services to mobile users.
  • the system supports roaming, in other words, UMTS users can be reached and they can make calls anywhere, as long as they are located within the UMTS coverage area.
  • UMTS is anticipated to satisfy a wide variety of future service needs, such as high-speed data services (multimedia), and video services, such as video calls. Many future services that will be needed are difficult to envision; therefore it is not possible to optimize UMTS to one group of services only.
  • UMTS must be constructed to be versatile and to permit further development. For this reason, a modular approach for the network architecture has been adopted, making it possible to implement UMTS effectively in different environments.
  • UMTS is built up of two or three parts that are illustrated in Figures 1 and 2: UMTS access network 1 (or UMTS base station system, UMTS-BSS) and a core network 2, 3, 4 and 5.
  • the UMTS access network will also be generally termed a radio access network in the following.
  • the UMTS access network 1 is mainly responsible for things related to the radio path, i.e., it offers to the core network radio access that is needed for cordless operation.
  • the core network 2, 3, 4 or 5 is a conventional or future telecommunications network modified to effectively utilize the UMTS access network in cordless communication.
  • Telecommunications networks that have been contemplated as suitable core networks include the ISDN (Integrated Services Digital Network), B-ISDN (Broadband Integrated Services Digital Network), packet data networks PDN, Asynchronous Transfer Mode (ATM) networks etc., and second generation mobile communications systems, such as GSM (Global System for Mobile Communication).
  • ISDN Integrated Services Digital Network
  • B-ISDN Broadband Integrated Services Digital Network
  • packet data networks PDN packet data networks
  • ATM Asynchronous Transfer Mode
  • GSM Global System for Mobile Communication
  • the UMTS access network must be capable of providing support to various core networks, also those evolving in the future.
  • UMTS access networks should permit connection of various radio interfaces to the core network (narrowband, broadband, CDMA, TDMA etc.).
  • the UMTS access network is typically simultaneously connected to several core networks, and hence must be capable of simultaneously supporting different core networks and their subscribers and services.
  • the protocol controlling the bearer services of the radio access network should be capable of setting up through the network bearer services that would best satisfy different services in each core network.
  • the bearer services may comprise several parameters wherewith the service quality and the efficiency of the radio network may be enhanced service-specifically.
  • a conceivable core network is the Transmission Control Protocol/Internet Protocol (TCP/IP) data network, the so-called Internet network. It is also possible that access to the Internet is provided through another core network, such as the General Packet Radio Service (GPRS) network.
  • GPRS General Packet Radio Service
  • the Internet makes use of a number of TCP/IP application protocols. These include:
  • FIG. 3 illustrates the structure of the TCP/IP protocol.
  • the application protocols are accessed through the local operating system either by a user application process or, more usually, by a user at a terminal.
  • the application protocols are connected to the IP protocol layer by means of a transport layer comprising either UDP (User Datagram Protocol) or TCP (Transmission Control Protocol).
  • UDP User Datagram Protocol
  • TCP Transmission Control Protocol
  • a feature common to all client-server interactions is the establishment of a traffic route between two application protocols or processes. All server application processes have an associated name which translates into a corresponding network-wide address.
  • the translation procedure is carried out by a process known as the domain name server.
  • the network-wide address consists of two parts: the network-wide IP address of the host in which the process is running and a local port number.
  • the IP address is used by the IP protocol to route datagrams across the Internet to the required destination host.
  • the port number is then used by the TCP protocol within the host - or UDP, if this is being used - to identify the specific process within that host to which a received message should be sent.
  • An open system will include multiple clients and servers both of different types and of the same type. All servers of the same type, however, are assigned the same system-wide port number.
  • the port numbers of the above-described application protocols are as follows: FTP 21, TELNET 23, SMTP 25, and WWW 80.
  • a client process When a client process initiates a call to a correspondent server process, it uses as a destination address the IP address of the host in which the server is running coupled with the appropriate well-known port number of that server. As a source address it uses the IP address of its own host together with the free (unused) port number on that host. If TCP is being used, the local TCP protocol entity will then establish a transport connection between the client and server processes (using these addresses) over which the appropriate message exchanges can take place.
  • the method is characterized by identifying the TCP/IP service to which the IP packet relates on the basis of the content of the IP packet, maintaining in the radio access network information on the bearer service parameters required by each TCP/IP service, setting the bearer service parameters in accordance with the identified TCP/IP service in the radio access network.
  • the invention also relates to an arrangement for setting bearer service parameters in a cellular radio access network connected to a core network which is an IP/TCP network or offers a connection to an IP/TCP network, the arrangement comprising resource control means for the radio access network by means of which bearer services are reserved for the connections, and first means located at the boundary of the radio access network, initiating reservation of a bearer service for a given connection upon receipt of a first IP packet relating to the connection-
  • the arrangement is characterized in that it further comprises second means maintaining information on the bearer service parameters required by each TCP/IP service in the radio accuse network, said first means being adapted to identify the TCP/IP service on the- basis of the content of the IP packet received from the core network and requesting from the resource control means a bearer service having the bearer service parameters required by the identified TCP/IP service, obtained from the second means.
  • the invention further relates to a mobile station and a network unit as claimed in claims 16 and 17, respectively.
  • the basic idea of the invention is that the bearer service parameters required by different TCP/IP services are predetermined in the radio access network the correct parameters for a given connection being selected by identifying the TCP/IP service on the basis of the content of the first IP packet received.
  • different TCP/IP services can be handled in different ways in the radio access network and a bearer service that best corresponds to the actual needs can be established through the radio access network- This avoids any collapse in service quality that the user might experience when data is transferred through the radio access network, as can happen if all services are given the same treatment.
  • the invention not only can service quality as experienced by the user be improved, but optimization of the capacity of the radio access network is also enabled when only correct-type capacity is reserved for each connection.
  • the TCP/IP service is identified on the basis of the port number in the destination port field in the TCP or UDP packet in the user data field of the IP packet.
  • the service quality required by the TCP/IP service can also be interpreted from the protocol field of the IP packet, which indicates whether the overlaying transport protocol is TCP or UDP, for instance. Since the protocols of the different transport layers may have completely different requirements, this information can be used for setting the bearer service parameters in the radio access network.
  • the service type field of the IP packet may also be used in the same way.
  • the different subscription-specific conditions in the radio access network can be taken into account in setting the bearer service parameters. An upper limit for the bit rate or price may be defined for the subscriber, for instance.
  • the identifying and selection of bearer service parameters on the border of the radio access network may be carried out at the mobile station when a mobile originated connection (call) is concerned, and in the boundary region of the core network and the radio access network when a mobile terminated connection (call) is concerned.
  • the primary embodiments of the invention will be described in the following as implemented in a radio access network in accordance with the precepts of the UMTS system, but the invention is not intended to be limited to the UMTS system.
  • the invention is suitable for use in any radio access network that is connected to one or more core networks (telecommunications system) which is a TCP/IP network or offers a connection to a TCP/IP network.
  • core networks telecommunications system
  • FIG. 2 illustrates a network architecture for a UMTS access network in detail. It is to be noted, however, that this network architecture is only one of several possible alternatives.
  • the network architecture shown in Figure 2 is based on a scenario according to which the functions of the UMTS access network are closely limited to radio access functions. Thus, it mainly comprises functions for radio resource control (handover, paging) and for controlling the bearer service (control of radio bearer service). More complicated modes of function, such as registers, registering functions and mobility and location management, are located in each core network.
  • GRAN generic radio access network
  • RAN radio access network
  • IWU interworking unit
  • IWU interworking unit
  • the interface IWU-CN is core network-specific. This enables development of core networks and the RAN independently of one another.
  • IWU may be connected to the base station subsystem BSS of a GSM network.
  • IWU2 may be connected to a local exchange of an ISDN network, for instance.
  • the radio access network RAN comprises a transport network TN, a radio network controller RNC, and a base station BS.
  • the base stations are connected to the transport network TN, which transports the user data to the IWUs and the control signalling to the radio network controller RNC.
  • All intelligence controlling the GRAN is located at the base stations (BS) and the radio network controller (RNC). As stated previously, this control is typically limited to control functions pertaining to radio access as well as to switching of connections through the transport network TN.
  • the transport network TN may be an ATM network, for example.
  • radio access network in this application generally refers to any radio access network and network structure that is connected to a core network.
  • radio bearer service protocol (RBC).
  • the bearer service is represented by means of various bearer service parameters, examples of which will be given below.
  • the bearer service parameters comprise four main classes: 1) traffic parameters, 2) quality of service (QoS) parameters, 3) information parameters, and 4) content parameters.
  • Peak Bit Rate PBR bit/s. The maximum instantaneous bit rate in connection with maximum burst size. Indicates the constant bit rate in the absence of other traffic parameters.
  • Maximum burst size MBS bits. Gives an estimation of the maximum burst size that may be transmitted at peak bit rate.
  • Frame size specification number of entries, minimum size, intermediate size(s), maximum size.
  • a frame may have any size between minimum and maximum.
  • requested intermediate sizes may be defined and the list defines the discrete frame sizes used, corresponding to discrete bit rates.
  • Minimum bit rate MBR bit/s. The minimum bit rate required for URAN ABR traffic.
  • Bit error rate BER Bit error rate of the connection.
  • point-to-point/point-to-multipoint Gives the configuration of the connection in terms of point-to-point or point-to-multipoint service.
  • Control the traffic consists of signalling.
  • Unsynchronized traffic the traffic is not synchronized with the radio interface timing.
  • Synchronized traffic Radio interface timing information is required.
  • Coding Indicates the speech codec used.
  • the core network 4 is a TCP/IP network or a network offering a transparent connection to a TCP/IP network.
  • a network element or function e.g. IWU3
  • the connection set up through GRAN is a transparent "tube" that transfers the IP packets from the boundary of GRAN (e.g. IWU3) to a MS and vice versa.
  • the actual client host machine is thus connected to the MS.
  • the adaptation function or network element e.g.
  • the adaptation function IWU3 inserts the IP packets into the user data field of the protocol data units (e.g. ATM cell) used on the GRAN connection and sends them across the GRAN.
  • protocol data units e.g. ATM cell
  • Such a function or network element at the boundary of GRAN is furnished with a feature wherewith it can identify TCP/IP service on the basis of the content of the IP packet and, on the basis of the identification, request from the RNC a bearer service that meets predetermined bearer service parameters.
  • Various information in the IP packet may be employed for identification of TCP/IP service.
  • Value 6 in the IP protocol field in the IP packet indicates that the protocol of the overlaying transport layer is TCP.
  • value 17 in the protocol field in the IP packet indicates that the protocol of the overlaying transport layer is UDP. It is possible to use this information as such for selecting the bearer service parameters. For example, it can be deduced from the fact that UDP is identified that the user does not require reliable transport (as there are no retransmissions on the transport layer). For this reason, the bearer service parameters predetermined for UDP could for example contain a lower frame loss ratio (FLR) and lower delay than TCP parameters. Identifying of UDP and TCP is not sufficient, however, for optimizing higher level services.
  • FLR frame loss ratio
  • the type of service field in the IP packet defines various properties required of the connection: high reliability, high throughput, short delay, and low priority level. This information can also be used for selecting bearer service parameters for the GRAN connection.
  • the user data field in the IP packet contains a TCP or UDP packet. Both a TCP packet and a UDP packet contain a destination port field; the port number contained in this field may be used for identifying the most common services.
  • the port numbers of the above-described application protocols are the following: FTP 21, TELNET 23, SMTP 25, and WWW 80.
  • mapping of TCP/IP services to GRAN bearer service parameters will, however, be described by means of examples utilizing several of the above-described methods simultaneously, thus enabling better optimization.
  • TCP protocol field of the IP packet
  • IP service type field high throughput.
  • predetermined GRAN bearer service parameters are selected for the identified FTP service:
  • PBR 64000 bit/s
  • SBR 32000 bit/s
  • MBR 16000 bit/s
  • PBR 1000 bit/s
  • SBR 500 bit/s
  • MBS 2000 bit/s
  • MBR 0 bit/s
  • TCP protocol field in the IP packet
  • IP service type field low priority/maximize throughput.
  • predetermined GRAN bearer service parameters are selected for the identified WWW service:
  • any other appropriate mapping of the bearer service parameters to the TCP/IP services may naturally be used.
  • subscriber-associated data relating to the subscription
  • subscriber data may be used to determine the bearer service parameters. For example an upper limit for the price or bit rate may be defined in the subscriber data.
  • the subscriber data is checked and taken into account in setting up the bearer service.
  • the subscriber data may be available from an internal database of GRAN, but typically it must be requested from an external database located for example in the core network, such as a GSM home location register HLR.
  • a first IP packet relating to a given connection is received by a function, device, or network element located at the boundary of GRAN (step 40, Figure 4) and having the feature in accordance with the present invention.
  • the invention can be implemented from the mobile station MS, which receives the packets from a peripheral device or from its user application.
  • a mobile terminated connection is involved, the invention can be implemented in the boundary region of the core network and the radio access network. Let such an element or function be IWU3 in Figure 2, in which situation the first packet relating to the terminating connection is received from a TCP/IP core network.
  • IWU3 analyzes the IP protocol field of the IP packet, step 41. If the value of the IP protocol field is not 6, IWU3 identifies UDP as the protocol of the transport layer and fetches from its database the GRAN bearer service parameters defined and stored for UDP, step 45. If the value of the IP protocol field is 6, IWU 3 identifies TCP as the protocol of the transport layer. Thereafter, IWU3 examines whether the value of the destination port field of the TCP packet, which is in the user data field of the IP packet, is 21, step 42. If this is the case, IWU3 identifies FTP as the application protocol and fetches from its database the GRAN bearer service parameters defined and stored for FTP, step 46. If the value of the destination port is not 21, the routine proceeds to step 43.
  • IWU3 examines whether the value of the destination port field of the TCP packet is 23. If this is the case, IWU3 identifies Telnet as the application protocol and fetches from its database the GRAN bearer service parameters defined and stored for Telnet, step 47. If the value of the destination port is not 23, the routine proceeds to step 44.
  • IWU3 examines whether the value of the destination port field of the TCP packet is 25. If this is the case, IWU3 identifies SMTP as the application protocol and fetches from its database the GRAN bearer service parameters defined and stored for SMTP, step 48. If the value of the destination port is not 25, the routine proceeds to step 49. In step 49, IWU3 presumes the application protocol to be WWW and fetches from its database the GRAN bearer service parameters defined and stored for WWW, step 48.
  • IWU3 forms a connection establishment message in accordance with the RBC protocol, containing the fetched bearer service parameters.
  • the message is sent over GRAN to RNC.
  • RNC sets up the requested bearer service across GRAN between IWU3 and the called MS.

Claims (17)

  1. Verfahren zum Einstellen von Trägerdienstparametern für ein Funknetz in einem Funkzugriffsnetz (1), das mit einem Kernnetz (2, 3, 4, 5) verbunden ist, das ein IP/TCP-Netz ist oder eine Verbindung zu einem IT/TCP-Netz anbietet, wobei das Verfahren die Schritte umfasst
    Empfangen (40) eines ersten IP-Pakets, das auf eine gegebene Verbindung bezogen ist, an der Grenze (MS, IWU3) des Funkzugriffsnetzes (1),
    Reservieren eines Trägerdienstes für die Verbindung in dem Funkzugriffsnetz (1), gekennzeichnet durch
    Identifizieren (41-44) des TCP/IP-Dienstes, zu dem das IP-Paket gehört, auf Grundlage des Inhalts des IP-Pakets,
    Aufrechterhalten einer Information über die durch jeden TCP/IP-Dienst geforderten Dienstparameter in dem Funkzugriffsnetz (1),
    Einstellen (45 - 50) der Trägerdienstparameter in Übereinstimmung mit dem identifizierten TCP/IP-Dienst in dem Funkzugriffsnetz (1).
  2. Verfahren nach Anspruch 1, gekennzeichnet durch
    Identifizieren des TCP/IP-Dienstes auf Grundlage des Inhalts des TCP- oder UDP-Pakets in dem Nutzerdatenfeld des IP-Pakets.
  3. Verfahren nach Anspruch 2, gekennzeichnet durch
    Identifizieren des TCP/IP-Dienstes auf Grundlage der Portnummer in dem Zielportfeld in dem TCP- oder UDP-Paket.
  4. Verfahren nach einem der Ansprüche 1 - 3, dadurch gekennzeichnet, dass die zu identifizierenden TCP/IP-Dienste zumindest eines der nachfolgenden Anwendungsprotokolle aufweisen: Telnet, FTP, SMTP, SNMP und WWW.
  5. Verfahren nach Anspruch 4, gekennzeichnet durch
    ldentifizieren von FTP, wenn das Zielportfeld des TCP-Pakets den Wert 21 aufweist,
    ldentifizieren von Telnet, wenn das Zielportfeld des TCP-Pakets den Wert 23 aufweist,
    Identifizieren von SMTP, wenn das Zielportfeld des TCP-Pakets den Wert 25 aufweist,
    ldentifizieren von WWW, wenn das Zielportfeld des TCP-Pakets den Wert 80 aufweist.
  6. Verfahren nach einem der vorgenannten Ansprüche, gekennzeichnet durch Identifizieren anhand des Protokollidentifikationsfelds des IP-Pakets, ob das Protokoll der Transportschicht TCP oder UDP ist,
    Berücksichtigen des identifizierten Protokolls der Transportschicht beim Einstellen der Trägerdienstparameter.
  7. Verfahren nach einem der vorgenannten Ansprüche, gekennzeichnet durch Prüfen des Diensttypfelds in dem IP-Paket,
    Berücksichtigen des Inhalts des Diensttypfelds beim Einstellen der Trägerdienstparameter.
  8. Verfahren nach einem der vorgenannten Ansprüche, dadurch gekennzeichnet, dass die Trägerdienstparameter des Funkzugriffsnetzes (1) zumindest eines des Nachfolgenden enthalten: Spitzenbitrate, aufrechterhaltbare Bitrate, maximale Burstgröße, Rahmengröße, minimale Bitrate, Bitfehlerrate, Verzögerung, Rahmenverlustrate, Priorität.
  9. Verfahren nach einem der vorgenannten Ansprüche, gekennzeichnet durch Einstellen von Trägerdienstparametern für FTP, die eine größtmögliche mittlere Bitrate ergeben.
  10. Verfahren nach einem der vorgenannten Ansprüche, gekennzeichnet durch Einstellen von Trägerdienstparametern für Telnet, die eine kürzestmögliche Verzögerung ergeben.
  11. Verfahren nach Anspruch 1, gekennzeichnet durch
    Durchführen der Schritte des Empfangens, Identifizierens, Aufrechterhaltens und Einstellens an der Grenze des Funkzugriffsnetzes (1) an einer Mobilstation (MS), wenn eine Verbindung mit mobilem Ursprung betroffen ist.
  12. Verfahren nach Anspruch 1, gekennzeichnet durch
    Durchführen der Schritte des Empfangens, ldentifizierens, Aufrechterhaltens und Einstellens in dem Grenzbereich (IWU3) des Funkzugriffsnetzes (1) und des Kernnetzes, wenn eine Verbindung mit mobilem Abschluss betroffen ist.
  13. Anordnung zum Einstellen von Trägerdienstparametern in einem zellularen Funkzugriffsnetz (1), das mit einem Kernnetz (2, 3, 4, 5) verbunden ist, das ein IP/TCP-Netz ist oder eine Verbindung zu einem IP/TCP-Netz anbietet, wobei die Anordnung umfasst
    Ressourcensteuermittel (RNC) für das Funkzugriffsnetz, ausgestaltet zum Reservieren von Trägerdiensten für die Verbindungen,
    erste Mittel (IWU3, MS), die an der Grenze des Funkzugriffsnetzes angeordnet sind, ausgestaltet zum Initiieren einer Reservierung eines Trägerdienstes für eine gegebene Verbindung beim Empfang eines auf die Verbindung bezogenen ersten IP-Pakets, dadurch gekennzeichnet, dass die Anordnung des Weiteren aufweist
    zweite Mittel (IWU3, MS) ausgestaltet zum Aufrechterhalten einer Information über die von jedem TCP/IP-Dienst in dem Funkzugriffsnetz geforderten Trägerdienstparameter,
    wobei die ersten Mittel (IWU3, MS) ausgestaltet sind zum Identifizieren des TCP/IP-Dienstes auf Grundlage des Inhalts des empfangenen IP-Pakets, und zum Anfordern eines Trägerdienstes mit den durch den identifizierten TCP/IP-Dienst geforderten, von den zweiten Mitteln erhaltenen Trägerdienstparametern von dem Ressourcensteuermittel (RNC).
  14. Anordnung nach Anspruch 13, dadurch gekennzeichnet, dass
    die ersten Mittel eine Mobilstation (MS) aufweisen, wenn eine Verbindung mit mobilem Ursprung betroffen ist.
  15. Anordnung nach Anspruch 13, dadurch gekennzeichnet, dass
    die ersten Mittel (IWU3) in dem Grenzbereich des Funkzugriffsnetzes und des Kernnetzes angeordnet sind, wenn eine Verbindung mit mobilem Abschluss betroffen ist.
  16. Mobilstation für ein zellulares Funkzugriffsnetz (1), das Ressourcensteuermittel (RNC) enthält zum Reservieren von Trägerdiensten für Verbindungen und verbunden ist mit einem Kernnetz (2, 3, 4, 5), das ein IP/TCP-Netz oder eine Verbindung zu einem IP/TCP-Netz anbietet, wobei die Mobilstationseinheit (MS) an einer Luftschnittstelle des Funkzugriffsnetzes angeordnet ist und ausgestaltet ist zum Initiieren einer Reservierung eines Trägerdienstes für eine gegebene Verbindung mit mobilem Ursprung beim Empfang eines ersten auf die Verbindung bezogenen IP-Pakets, dadurch gekennzeichnet, dass die Mobilstation (MS) ausgestaltet ist zum Identifizieren des TCP/IP-Dienstes auf Grundlage des Inhalts des empfangenen IP-Pakets und zum Anfordern eines Trägerdienstes mit den für den identifizierten TCP/lP-Dienst in dem Funkzugriffsnetz vordefinierten Trägerdienstparametern, basierend auf einer in der Mobilstation aufrechterhaltenen Information, von den Ressourcensteuermitteln (RNC).
  17. Netzeinheit für ein zellulares Funkzugriffsnetz (1), das Ressourcensteuermittel (RNC) zum Reservieren von Trägerdiensten für Verbindungen enthält und mit einem Kernnetz (2, 3, 4, 5) verbunden ist, das ein IP/TCP-Netz ist oder eine Verbindung zu einem IP/TCP-Netz anbietet, wobei die Netzeinheit (IWU3) in dem Grenzbereich des Funkzugriffsnetzes und des Kernnetzes angeordnet ist und ausgestaltet ist zum Initiieren einer Reservierung eines Trägerdienstes für eine gegebene Verbindung mit mobilem Ursprung beim Empfang eines ersten auf die Verbindung bezogenen IP-Pakets, dadurch gekennzeichnet, dass die Netzeinheit (IWU3) ausgestaltet ist zum Identifizieren des TCP/lP-Dienstes auf Grundlage des Inhalts des von dem Kernnetz empfangenen lP-Pakets und zum Anfordem eines Trägerdienstes mit den für den identifizierten TCP/IP-Dienst in dem Funkzugriffsnetz vordefinierten Trägerdienstparametern, basierend auf einer aufrechterhaltenen Information, von dem Ressourcensteuermittel (RNC).
EP98929456A 1997-06-30 1998-06-23 Bestimmung von trägerdiensten in einem funkzugriffsnetz Expired - Lifetime EP0993718B1 (de)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
FI972815A FI107498B (fi) 1997-06-30 1997-06-30 Verkkopalveluiden määrittäminen radioaccessverkossa
FI972815 1997-06-30
PCT/FI1998/000549 WO1999001991A2 (en) 1997-06-30 1998-06-23 Determining bearer services in a radio access network

Publications (2)

Publication Number Publication Date
EP0993718A2 EP0993718A2 (de) 2000-04-19
EP0993718B1 true EP0993718B1 (de) 2006-01-04

Family

ID=8549167

Family Applications (1)

Application Number Title Priority Date Filing Date
EP98929456A Expired - Lifetime EP0993718B1 (de) 1997-06-30 1998-06-23 Bestimmung von trägerdiensten in einem funkzugriffsnetz

Country Status (9)

Country Link
US (1) US6674733B1 (de)
EP (1) EP0993718B1 (de)
AT (1) ATE315295T1 (de)
AU (1) AU7920798A (de)
DE (1) DE69833111T2 (de)
ES (1) ES2253820T3 (de)
FI (1) FI107498B (de)
TW (1) TW352496B (de)
WO (1) WO1999001991A2 (de)

Families Citing this family (38)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FI106172B (fi) * 1998-01-29 2000-11-30 Nokia Networks Oy Menetelmä uudelleenkonfiguroida solukkoradioverkossa yhteys
FI982854A (fi) * 1998-12-31 2000-07-01 Nokia Networks Oy Datasiirto tietoliikennejärjestelmässä
US6584321B1 (en) * 1999-05-07 2003-06-24 At&T Wireless Services, Inc. Method and apparatus for wireless data services over a selected bearer service
AU4966900A (en) * 1999-05-17 2000-12-05 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for providing radio access bearer services
SE522068C2 (sv) 1999-07-15 2004-01-13 Ericsson Telefon Ab L M Metod och anordning för att åstadkomma radioaccessbärartjänster
DE19933222A1 (de) * 1999-07-26 2001-02-08 Siemens Ag Verfahren und Kommunikationssystem zur Behandlung eines Paketdienstes
FI114371B (fi) 1999-08-09 2004-09-30 Nokia Corp Menetelmä kantopalvelun valitsemiseksi palvelulle langattomassa matkaviestinjärjestelmässä, tiedonsiirtojärjestelmä ja matkaviestinpäätelaite
GB9919851D0 (en) 1999-08-20 1999-10-27 Lucent Technologies Inc Core network allocation for gsm/umts
GB9919853D0 (en) * 1999-08-20 1999-10-27 Lucent Technologies Inc Parallel core networks for gsm/umts
GB2355362B (en) * 1999-10-12 2003-08-06 Ericsson Telefon Ab L M Media gateway control
FI112427B (fi) * 1999-11-05 2003-11-28 Nokia Corp Menetelmä langattoman päätelaitteen ominaisuuksien määrittämiseksi multimediasanoman välityspalvelussa, multimediasanoman välityspalvelu ja multimediapäätelaite
FI111314B (fi) 1999-11-05 2003-06-30 Nokia Corp Multimediasanomanvälityspalvelu
KR100519612B1 (ko) * 2000-04-07 2005-10-07 노키아 코포레이션 투과 ｒｌｃ를 통한 고정 크기 ｐｄｕ들의 전송
GB0009167D0 (en) * 2000-04-14 2000-05-31 Univ Strathclyde Wireless networks
US7072329B2 (en) * 2000-05-22 2006-07-04 Telefonaktiebolaget Lm Ericsson (Publ) Combining differing transport technologies in a telecommunications system
EP1168754B1 (de) * 2000-06-26 2005-03-16 Alcatel Adressierungsschema für ein IP basiertes funkzugriffsnetz
FI112307B (fi) 2000-08-02 2003-11-14 Nokia Corp Viestintäpalvelu
US6763004B1 (en) 2000-09-27 2004-07-13 Telefonaktiebolaget L M Ericsson (Publ) System and method for paging mobile stations in a radio telecommunications network
US7796524B1 (en) * 2000-10-06 2010-09-14 O'connell David Monitoring quality of service in packet-based communications
DE20018926U1 (de) * 2000-11-07 2001-02-01 Walter Andre Universelle Plattform für GPRS/UMTS Dienste
US7333505B2 (en) * 2000-12-18 2008-02-19 Nortel Networks Limited Transaction management for interworking between disparate networks
ATE425647T1 (de) * 2001-02-22 2009-03-15 Ericsson Telefon Ab L M Verfahren zum anpassen einer anzahl von trägern an einen dienst
FI111506B (fi) * 2001-03-14 2003-07-31 Nokia Corp Menetelmä palvelun laatutason valitsemiseksi langattomassa tiedonsiirtojärjestelmässä
US6973502B2 (en) 2001-03-29 2005-12-06 Nokia Mobile Phones Ltd. Bearer identification tags and method of using same
WO2002084859A1 (en) * 2001-04-18 2002-10-24 Nokia Corporation Balanced circuit arrangement and method for linearizing such an arrangement
US6978144B1 (en) * 2001-04-19 2005-12-20 Cisco Technology, Inc. Method and system for managing real-time bandwidth in a wireless network
GB2375023B (en) * 2001-04-26 2003-07-16 Marconi Comm Ltd Improvements in and relating to telecommunications networks
FI20010979A (fi) * 2001-05-09 2002-11-10 Nokia Corp Puhelunohjausmenetelmä
DE10125390A1 (de) * 2001-05-23 2002-12-12 Siemens Ag Mobilfunk-Kommunikationssystem mit Referenzsignalgeber
KR100422133B1 (ko) * 2001-07-27 2004-03-12 엘지전자 주식회사 광대역 무선가입자망 시스템의 패킷데이터 처리장치 및 그방법
US6717927B2 (en) 2002-04-05 2004-04-06 Interdigital Technology Corporation System for efficient recovery of node B buffered data following serving high speed downlink shared channel cell change
US20030225887A1 (en) * 2002-05-28 2003-12-04 Rene Purnadi Establishing IP level connectivity by use of L-2 dormant mobile node activation
US7706405B2 (en) 2002-09-12 2010-04-27 Interdigital Technology Corporation System for efficient recovery of Node-B buffered data following MAC layer reset
US20050064821A1 (en) * 2003-09-22 2005-03-24 Telefonaktiebolaget Lm Ericsson (Publ) Alternative service management
EP1564908A1 (de) * 2003-12-23 2005-08-17 Telefonaktiebolaget LM Ericsson (publ) Verbesserte Verarbeitung mit mehreren Empfängern
DE102006029878A1 (de) * 2006-06-28 2008-01-17 T-Mobile International Ag & Co. Kg Verfahren zur Funkträgerauswahl bei Funkübertragungssystemen
US8774207B2 (en) * 2010-07-31 2014-07-08 Motorola Solutions, Inc. Methods for bearer reservation, maintenance, and use in a communication system
US8838156B2 (en) 2010-10-22 2014-09-16 Motorola Solutions, Inc. Multi-bearer rate control for transporting user plane data

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5181200A (en) * 1990-10-29 1993-01-19 International Business Machines Corporation Handoff method and apparatus for mobile wireless workstation
JPH06318951A (ja) * 1993-01-07 1994-11-15 Toshiba Corp セル転送方法およびセル転送システム
US6167248A (en) * 1993-09-06 2000-12-26 Nokia Mobile Phones Ltd. Data transmission in a radio telephone network
EP0660569A1 (de) * 1993-12-22 1995-06-28 International Business Machines Corporation Verfahren und System zum Verbessern der Verarbeitungszeit der Wegeauswahl in einem Hochgeschwindigkeits-Paketvermittlungsnetz
EP0824834A1 (de) * 1995-05-05 1998-02-25 Telefonaktiebolaget Lm Ericsson Mobiles funksystem mit bcie übersetzung
GB9518540D0 (en) * 1995-09-11 1995-11-08 Nokia Mobile Phones Ltd Radio telephones and methods of operation
FI101337B (fi) * 1995-09-25 1998-05-29 Nokia Telecommunications Oy Matkaviestinjärjestelmä ja menetelmä datapuhelun muodostamiseksi
US5841764A (en) * 1995-10-30 1998-11-24 Ericsson Inc. Method and apparatus for permitting a radio to originate and receive data messages in a data communications network
FI101581B1 (fi) 1995-11-07 1998-07-15 Nokia Telecommunications Oy Kiinteän verkon protokollien sovittaminen matkaviestinverkkoon signalointituen puuttuessa
US5629974A (en) * 1995-11-16 1997-05-13 Nokia Telecommunications Oy Communication system providing mobility management internetworking between a C-interface radio system and an overlay mobile radio network
WO1997047119A1 (en) * 1996-06-04 1997-12-11 Telefonaktiebolaget Lm Ericsson (Publ) An access network over a shared medium
US6097733A (en) * 1997-06-13 2000-08-01 Nortel Networks Corporation System and associated method of operation for managing bandwidth in a wireless communication system supporting multimedia communications

Also Published As

Publication number Publication date
WO1999001991A2 (en) 1999-01-14
FI972815A0 (fi) 1997-06-30
EP0993718A2 (de) 2000-04-19
FI107498B (fi) 2001-08-15
WO1999001991A3 (en) 1999-03-25
DE69833111D1 (de) 2006-03-30
US6674733B1 (en) 2004-01-06
TW352496B (en) 1999-02-11
AU7920798A (en) 1999-01-25
ES2253820T3 (es) 2006-06-01
FI972815A (fi) 1998-12-31
DE69833111T2 (de) 2006-08-31
ATE315295T1 (de) 2006-02-15

Similar Documents

Publication Publication Date Title
EP0993718B1 (de) Bestimmung von trägerdiensten in einem funkzugriffsnetz
US6658011B1 (en) Use of wireless application protocol in a packet-switched radio telecommunication system
JP4230106B2 (ja) Ｇｐｒｓ加入者による多数のインタネットサービスプロバイダの選択
JP4307709B2 (ja) 移動体通信ネットワークにおける選択可能なパケット交換及び回線交換サービス
US7042855B1 (en) Method for routing data in a communication system
EP1049339B1 (de) System zum Aufbau einer Datenverbindung in drahtlosen Netzwerken
US6473411B1 (en) Router device, datagram transfer method and communication system realizing handoff control for mobile terminals
US6600732B1 (en) Method and arrangement for transmitting multimedia-related information in a packet-switched cellular radio network
US7539499B2 (en) Method and system for managing wireless bandwidth resources
US20040246962A1 (en) Dynamically assignable resource class system to directly map 3GPP subscriber communications to a MPLS-based protocol
EP1133205A2 (de) Hardware-Konfiguration,Unterstützungsknoten und Verfahren zur Durchführung von GPRS General Packet Radio Services in GSM
EP1095489A2 (de) Verfahren und system zum trägermanagement in einem mobilen fernmeldenetz der dritten generation
GB2341059A (en) Internet protocol flow detection
US6747989B1 (en) Method and arrangement for transmitting multimedia-related information in a packet-switched cellular radio network with external connection
JP4418136B2 (ja) 通信システム
JP4213344B2 (ja) 移動体データ・サービス用のシステムおよび方法
US9204491B2 (en) Method of managing quality of service in a mobile radio system
US20040218587A1 (en) Private EV-DO system sharing public network data location register and data service method
EP1440589A1 (de) Multicast-übertragung zu einem funkzugriffsnetzwerk
KR100436139B1 (ko) 아이엠티-2000 에스지에스엔에서 패킷 서비스 시스템 및방법
JP4079677B2 (ja) 無線通信システム、経路制御方法及び記録媒体
JP3325537B2 (ja) 無線通信システム
KR100287802B1 (ko) 디지털이동통신망에서무선데이터통신연동장치의팩스발신호제어방법
Baumann et al. From GPRS to UMTS

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

17P Request for examination filed

Effective date: 19991227

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: NOKIA CORPORATION

17Q First examination report despatched

Effective date: 20040423

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE

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

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

Ref country code: BE

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

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REF Corresponds to:

Ref document number: 69833111

Country of ref document: DE

Date of ref document: 20060330

Kind code of ref document: P

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

Ref country code: DK

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

Effective date: 20060404

REG Reference to a national code

Ref country code: CH

Ref legal event code: NV

Representative=s name: ICB INGENIEURS CONSEILS EN BREVETS SA

REG Reference to a national code

Ref country code: SE

Ref legal event code: TRGR

REG Reference to a national code

Ref country code: ES

Ref legal event code: FG2A

Ref document number: 2253820

Country of ref document: ES

Kind code of ref document: T3

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

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

ET Fr: translation filed
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 NON-PAYMENT OF DUE FEES

Effective date: 20060630

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

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

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

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

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

Ref country code: CY

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

Effective date: 20060104

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

Ref country code: IE

Payment date: 20100614

Year of fee payment: 13

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

Ref country code: AT

Payment date: 20100610

Year of fee payment: 13

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

Ref country code: ES

Payment date: 20100713

Year of fee payment: 13

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

REG Reference to a national code

Ref country code: AT

Ref legal event code: MM01

Ref document number: 315295

Country of ref document: AT

Kind code of ref document: T

Effective date: 20110623

REG Reference to a national code

Ref country code: IE

Ref legal event code: MM4A

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

Ref country code: IE

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

Effective date: 20110623

REG Reference to a national code

Ref country code: ES

Ref legal event code: FD2A

Effective date: 20121116

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 NON-PAYMENT OF DUE FEES

Effective date: 20110624

REG Reference to a national code

Ref country code: GB

Ref legal event code: 732E

Free format text: REGISTERED BETWEEN 20150910 AND 20150916

REG Reference to a national code

Ref country code: DE

Ref legal event code: R082

Ref document number: 69833111

Country of ref document: DE

Representative=s name: EISENFUEHR SPEISER PATENTANWAELTE RECHTSANWAEL, DE

Ref country code: DE

Ref legal event code: R081

Ref document number: 69833111

Country of ref document: DE

Owner name: NOKIA TECHNOLOGIES OY, FI

Free format text: FORMER OWNER: NOKIA CORP., 02610 ESPOO, FI

REG Reference to a national code

Ref country code: CH

Ref legal event code: PUE

Owner name: NOKIA TECHNOLOGIES OY, FI

Free format text: FORMER OWNER: NOKIA CORPORATION, FI

REG Reference to a national code

Ref country code: NL

Ref legal event code: PD

Owner name: NOKIA TECHNOLOGIES OY; FI

Free format text: DETAILS ASSIGNMENT: VERANDERING VAN EIGENAAR(S), OVERDRACHT; FORMER OWNER NAME: NOKIA CORPORATION

Effective date: 20151111

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 19

REG Reference to a national code

Ref country code: FR

Ref legal event code: TP

Owner name: NOKIA TECHNOLOGIES OY, FI

Effective date: 20170109

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 20

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

Ref country code: FR

Payment date: 20170511

Year of fee payment: 20

Ref country code: GB

Payment date: 20170621

Year of fee payment: 20

Ref country code: CH

Payment date: 20170613

Year of fee payment: 20

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

Ref country code: NL

Payment date: 20170614

Year of fee payment: 20

Ref country code: IT

Payment date: 20170619

Year of fee payment: 20

Ref country code: SE

Payment date: 20170613

Year of fee payment: 20

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

Ref country code: DE

Payment date: 20170621

Year of fee payment: 20

REG Reference to a national code

Ref country code: DE

Ref legal event code: R071

Ref document number: 69833111

Country of ref document: DE

REG Reference to a national code

Ref country code: NL

Ref legal event code: MK

Effective date: 20180622

REG Reference to a national code

Ref country code: GB

Ref legal event code: PE20

Expiry date: 20180622

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

Ref country code: GB

Free format text: LAPSE BECAUSE OF EXPIRATION OF PROTECTION

Effective date: 20180622