EP3319393B1 - Establishing a connection between a remote user equipment, ue, and a telecommunication network via a relay capable ue - Google Patents

Establishing a connection between a remote user equipment, ue, and a telecommunication network via a relay capable ue Download PDF

Info

Publication number
EP3319393B1
EP3319393B1 EP16197546.1A EP16197546A EP3319393B1 EP 3319393 B1 EP3319393 B1 EP 3319393B1 EP 16197546 A EP16197546 A EP 16197546A EP 3319393 B1 EP3319393 B1 EP 3319393B1
Authority
EP
European Patent Office
Prior art keywords
bearer
access node
remote
core network
relay
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
EP16197546.1A
Other languages
German (de)
English (en)
French (fr)
Other versions
EP3319393A1 (en
Inventor
Toni Dimitrovski
Antonius Norp
Miodrag Djurica
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.)
Nederlandse Organisatie voor Toegepast Natuurwetenschappelijk Onderzoek TNO
Koninklijke KPN NV
Original Assignee
Nederlandse Organisatie voor Toegepast Natuurwetenschappelijk Onderzoek TNO
Koninklijke KPN NV
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
Priority to EP16197546.1A priority Critical patent/EP3319393B1/en
Application filed by Nederlandse Organisatie voor Toegepast Natuurwetenschappelijk Onderzoek TNO, Koninklijke KPN NV filed Critical Nederlandse Organisatie voor Toegepast Natuurwetenschappelijk Onderzoek TNO
Priority to CN201780068710.XA priority patent/CN109892003B/zh
Priority to KR1020197016394A priority patent/KR102293786B1/ko
Priority to PCT/EP2017/078308 priority patent/WO2018083293A1/en
Priority to EP17800457.8A priority patent/EP3536113A1/en
Priority to US16/347,447 priority patent/US11076435B2/en
Publication of EP3319393A1 publication Critical patent/EP3319393A1/en
Application granted granted Critical
Publication of EP3319393B1 publication Critical patent/EP3319393B1/en
Priority to US17/355,878 priority patent/US20210321471A1/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/14—Direct-mode setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/04—Terminal devices adapted for relaying to or from another terminal or user
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/18—Interfaces between hierarchically similar devices between terminal devices

Definitions

  • the present invention is generally related to User Equipments, UEs, that are connected to a telecommunication network via a relay capable UE. More specifically, the invention relates to a method of establishing a connection between a remote UE and the telecommunication network via a relay capable UE.
  • Telecommunication networks enable User Equipments, UEs, to communicate with each other via one of a number of access nodes and via one or more core networks.
  • the UE's are mobile terminals designed to be used by human users, such as mobile smart phones, tablets, Virtual Reality, VR, headsets, or anything alike.
  • the term UE may also refer to equipment designed to be used in a Machine-to-Machine or Internet of Things context, such as devices, wearables, sensors, actuators, cameras, cars, media devices, or anything alike.
  • the term UE may also refer to generally stationary communication devices, such as fixed phones, computers, or stationary Internet of Things, IOT, devices, smart meters or anything alike.
  • the term User Equipment is used, which is intended to cover any of the above identified use cases.
  • a telecommunication network comprises the access network, for example the evolved UMTS Terrestrial Radio Access, E-UTRAN, access network as well as the core network, for example the Evolved Packet Core, EPC, network.
  • the access node is typically the node in the access network to which a UE directly communicates, for example the Evolved Node B, the radio base station or anything alike.
  • ProSe proximity-based services
  • a ProSe capable UE may perform a ProSe discovery to identify ProSe-enabled UEs in its proximity.
  • Direct Communication enables the establishment of a direct communication connection between ProSe-enabled UEs that are in direct communication range.
  • the ProSe Direct Communication path could use different radio technologies, for example, E-UTRAN or Wireless Local Area Network, WLAN, or anything alike.
  • ProSe Direct communication also facilitates the use of a ProSe UE-to-Network relay, which acts as a relay between the access network and a remote UE.
  • the ProSe UE-to-Network relay entity thus provides the functionality to support connectivity to the telecommunication network for remote UE's.
  • a UE is considered to be a remote UE for a certain ProSe UE-to-Network relay if it has successfully established a direct communication path to the UE-to-Network relay.
  • a remote UE can be located within, or outside, the coverage area of the access node.
  • the ProSe UE-to-Network Relay relays unicast traffic, uplink as well as downlink, between the Remote UE and the telecommunication network.
  • the ProSe UE-to-Network Relay provides generic functions that can relay any Internet Protocol, IP, traffic.
  • ProSe Direct Communication is used between Remote UEs and the ProSe UE-to-Network Relays for the unicast traffic.
  • One of the drawbacks of the above identified known methods of relaying traffic by the UE-to-Network relay is that the network is not able to determine whether traffic is related to the UE-to-Network Relay or related to the remote UE using the UE-to-Network Relay for its connection to the telecommunication network.
  • a method of establishing a connection between a remote User Equipment, UE, and a telecommunication network via a relay capable UE wherein said telecommunication network comprises a core network and an access network, said access network comprising an access node, wherein said relay capable UE has an established Radio Access Bearer between said relay capable UE and said core network wherein said established Radio Access Bearer comprises:
  • said command is also directed to the establishment of the second UE-to-access node bearer.
  • the access node is able to distinguish between traffic associated with said relay capable UE via said Radio Access Bearer and traffic associated with said remote UE over said Remote Radio Access Bearer. That is, the traffic from the remote UE and the traffic from the relay capable UE are carried over different connections.
  • the access node is able to use conventional mobility management procedures for, e.g., performing handovers.
  • the Remote Radio Access Bearer may have its own encryption and security context. For the remote UE, it will look like a conventional security context. The telecommunication network may see two different security contexts, one for the remote UE and one for the relay capable UE.
  • the access node as well as the core network have separate representations for the remote UE and the relay capable UE, respectively, as well as their state.
  • the relaying is performed in such a way that the access node and the core network are able to distinguish the traffic associated with the relay capable UE from the traffic associated with the remote UE, and are able to manage the connections thereof separately. This includes, for example, standard mobility and session management procedures.
  • the core network can perform Quality-of-Service, QoS, control and charging for each of the UE's separately.
  • said remote UE is directly made visible to the access node by introducing the second UE-to-access node bearer, which is established between the relay capable UE and the access node.
  • the relay capable UE may thus act as a relay of signalling and user plane traffic between the remote UE and the radio access network, i.e. the access node.
  • each of the nodes involved in the establishing process may store information required to forward traffic in both directions.
  • This information may, for example, be an identification of the UE-to-UE bearer, the second UE-to-access node bearer, the access node-to-core network bearer and/or an identification of the remote UE and the relay capable UE.
  • the relay capable UE may store identifications of the UE-to-UE bearer as well as the second UE-to-access node bearer.
  • the access node may store identifications of the second UE-to-access node bearer as well as the access node-to-core network bearer.
  • the Request Relay message comprises an identifier for identifying said remote UE at the access node, wherein said method further comprises the steps of:
  • the above described embodiment is directed to the scenario that the remote UE, initially, has a direct, i.e. non-relayed connection to the core network. That is, the remote UE may be connected to the core network in a conventional manner by, for example, an established Radio Access Bearer between itself and the core network.
  • the remote UE may decide that it would be beneficial to have a relayed connection to the core network. Such a decision may, for example, be based on a non-reliable non-relayed connection, or the desire to save battery power by using a nearby device as relay. As such, using a relayed connection, the remote UE may be connected to the core network in a more stable, reliable and more battery power efficient manner.
  • the remote UE may perform a ProSe discovery method as described in, for example, TS 23.303, chapter 5.3 ProSe Direct Discovery.
  • the result of such a discovery method is finding a relay capable UE that may act as a relay for the remote UE towards the telecommunication network.
  • the same access node is used for both the connection of the relay capable UE to the network and the direct, i.e. non-relayed, connection of the remote UE to the network.
  • a non-relayed connection to the core network of the remote UE is already established via that same access node.
  • an identifier may be provided in the Request Relay message for identifying the remote UE at the access node.
  • the identifier is, for example, a Cell Radio Network Temporary Identifier, or other similar identifier that identifies the UE at the access node.
  • the access node may thus be able to determine whether it already has a connection to the remote UE using the identifier in the Request Relay message.
  • the non-relayed connection between the remote UE and the core network may be released, i.e. the underlying bearers for the RAB may be released.
  • This action may be performed upon receipt of an acknowledgement message from the relay capable UE indicating that the requested bearers between the remote UE and the relay capable UE and between the relay capable UE and the access node are established and/or upon receipt of an acknowledgement message from the core network that a new access node to core network node bearer has been established, or upon receipt of both acknowledgement messages. It might also be possible that one of the bearers of the RAB is re-used and not released.
  • a Radio Access Bearer was established between the remote UE and the core network.
  • This Radio Access Bearer comprised a UE-to-access node bearer and an access node-to-core network bearer.
  • This Radio Access Bearer becomes the Remote Radio Access Bearer once the decision has been made, for example by the remote UE, to start relaying via the relay capable UE.
  • a new UE-to-UE bearer i.e. between the remote UE and the relay capable UE may be added to the already existing Radio Access Bearer
  • a new UE-to-access node bearer i.e. between the relay capable UE and the access node, may be established.
  • the above described embodiment is, for example, an embodiment directed to a remote UE being in EPS Connection Management, ECM, connected mode.
  • the step of receiving the Request Relay message further comprises:
  • a service request for example a Non-Access Stratum, NAS, service request
  • NAS Non-Access Stratum
  • MME Mobility Management Entity
  • a Mobility Management Entity sends an initial Context Setup Request to the access node in reply to the received service request.
  • the advantage of the above described embodiment is that the remote UE can be connected to the telecommunication network via the relay capable UE, even in the situation when the remote UE does not have a separate, non-relayed connection established to the telecommunication network.
  • the remote UE may be connected in the same way as a UE that is connected directly, i.e. non-relayed.
  • the method comprises the step of:
  • said acknowledgement message comprises an indication that said second UE-to-access node bearer has also been established.
  • the advantage of this embodiment is that the access node is made aware of the fact that the UE-to-UE bearer and the second UE-to-access node bearer have been established.
  • the access node is a base station in a cellular network, for example an evolved node B, eNB.
  • eNB evolved node B
  • a method of establishing a connection between a remote User Equipment, UE, and a telecommunication network via a relay capable UE wherein said telecommunication network comprises a core network and an access network, said access network comprising an access node, wherein said relay capable UE has an established Radio Access Bearer between said relay capable UE and said core network, wherein said established Radio Access Bearer comprises:
  • said command is also directed to the establishment of the second UE-to-access node bearer.
  • the method further comprises the step of:
  • said acknowledgement message comprises an indication that said second access node-to-core network bearer has also been established.
  • the invention provides for a method of establishing a connection between a remote User Equipment, UE, and a telecommunication network via a relay capable UE, wherein said telecommunication network comprises a core network and an access network, said access network comprising an access node, wherein said relay capable UE has an established Radio Access Bearer between said relay capable UE and said core network, wherein said established Radio Access Bearer comprises:
  • the method further comprises the steps of:
  • the method further comprises the step of:
  • the invention provides for a non-transitory computer-readable storage medium, comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to any of the embodiments as described above.
  • the computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory, RAM, a read-only memory, ROM, an erasable programmable read-only memory, a portable compact disc read-only memory, an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
  • the invention provides for an access node arranged for establishing a connection between a remote User Equipment, UE, and a telecommunication network via a relay capable UE, wherein said telecommunication network comprises a core network and an access network, said access network comprising an access node, wherein said relay capable UE has an established Radio Access Bearer between said relay capable UE and said core network wherein said established Radio Access Bearer comprises:
  • the invention provides for a relay capable User Equipment, UE, arranged for establishing a connection between a remote User Equipment, UE, and a telecommunication network via a relay capable UE, wherein said telecommunication network comprises a core network and an access network, said access network comprising an access node, wherein said relay capable UE has an established Radio Access Bearer between said relay capable UE and said core network, wherein said established Radio Access Bearer comprises:
  • a remote User Equipment, UE arranged for establishing a connection between a remote User Equipment, UE, and a telecommunication network via a relay capable UE, wherein said telecommunication network comprises a core network and an access network, said access network comprising an access node, wherein said relay capable UE has an established Radio Access Bearer between said relay capable UE and said core network, wherein said established Radio Access Bearer comprises:
  • NAS Non-Access Stratum
  • MME Mobility Management Entity
  • Fig. 1 shows a schematic illustration 1 of an established Remote Radio Access Bearer 6 between the remote User Equipment, UE, 2 and the core network as indicated with reference numeral 5.
  • the Remote Radio Access Bearer 6 is established between the remote UE 2 and any of a Mobility Management Function, such as a Mobility Management Entity, MME, or a gateway function, such as the serving gateway, SGW.
  • MME Mobility Management Entity
  • SGW serving gateway
  • the core network 5 could be the Evolved Packet Core, EPC.
  • the SGW anchors user-plane mobility in a SGW serving area and functions as a termination point of the packet data network interface towards the access network, i.e. the access node 4.
  • the MME is involved in the bearer activation and deactivation process and is responsible for choosing the SGW for the remote UE 2 at the initial attach thereof to the network. Further, the MME is responsible for authenticating the remote UE 2, for example by interacting with the Home Subscriber Server, HSS.
  • the Non Access Stratum, NAS, signalling terminates at the MME and it is also responsible for generation and allocation of temporary identities to UE's.
  • the schematic illustration 1 of figure 1 shows that the Remote Radio Access Bearer 6 is established via the relay capable UE 3 and the access node 4.
  • the access node 4 is, for example, a base station in a cellular network. More specifically, the access node 4 may be an Evolved Node B, eNB in an LTE network or a NodeB in an UMTS network. In case of a centralized Radio Access Network an access node 4 may be a combination of a radio function unit, referred to as Remote Radio Head, and a processor function, referred to as the Base Band Unit. Other splits of functionality of an access node may also be possible.
  • the Remote Radio Access Bearer 6 is considered a logical bearer established between the remote UE 2 and the core network 5.
  • the Remote Radio Access Bearer 6 actually comprises three separate bearers.
  • a first of these three bearers is indicated with reference numeral 7.
  • This bearer is a UE-to-UE bearer 7 and is established between the remote UE 2 and the relay capable UE 3. Such a bearer is thus established to support device to device communication, or ProSe communication.
  • the UE-to-UE bearer 7 would be considered to be established over the PC5 interface.
  • a second of these three bearers is indicated with reference numeral 8 and is referenced to as the second UE-to-access node bearer 8.
  • This bearer may be a radio bearer 8 and is established between the relay capable UE 3 and the access node 4.
  • This radio bearer 8 is intended to carry traffic to, and from, the remote UE 2 only.
  • the UE-to-access node bearer 8 would be considered to be established over the Uu interface.
  • a third of these three bearers is indicated with reference numeral 9 and is referenced to as an access node-to-core network bearer 9.
  • This bearer is established between the access node 4 and the core network 5.
  • the access node-to-core network bearer 9 would be considered to be established over the S1 interface.
  • an “in coverage” scenario the remote UE 2 as well as the relay capable UE 3 are within coverage range of the access node 4, and the network may control the resources used for ProSe communication.
  • the remote UE 2 is not in direct coverage of the access node 4 and the relay capable UE 3 is in direct coverage of the access node 4.
  • the schematic illustration 1 of figure 1 further shows an established Radio Access Bearer 10 between the relay capable UE 3 and the core network 5.
  • This specific Radio Access Bearer 10 is a dedicated bearer for the relay capable UE 3. As such, this bearer is not used for communication to, and from, the remote UE 2.
  • the Radio Access Bearer 10 comprises two separate bearers which are associated to the Radio Access Bearer 10.
  • the first bearer is referenced to as a first UE-to-access node bearer 11 and is established between the relay capable UE 3 and the access node 4.
  • the second bearer is referenced to as an access node-to-core network bearer 12 and is established between the access node 4 and the core network 5.
  • the Remote Radio Access Bearer 6 represents the connection of the remote UE 2 to the core network 5 and may be used for data transfer.
  • Each of the nodes over which the Remote Radio Access Bearer 6 is established may store information required to forward the traffic in both directions. This type of information may be the bearer or connection identifications used to create associations which a node accesses to find where to forward packets belonging to the Remote Radio Access Bearer 6. These associations may be saved during the establishment of the Remote Radio Access Bearer 6.
  • the access node 4 is thus able to distinguish between traffic with said relay capable UE 3 over said first UE-to-access node bearer 11 and traffic with said remote UE over said second UE-to-access node bearer 8.
  • Fig. 2 shows a signalling diagram 101 in which a UE-to-UE bearer as well as a second UE-to-access node bearer is established for a remote UE in connected mode.
  • the remote UE is indicated with reference numeral 102
  • the relay capable UE is indicated with reference numeral 103
  • the access node is indicated with reference numeral 104
  • the core network is indicated with reference numeral 105
  • the ProSe Function is indicated with reference numeral 106.
  • reference numeral 107 indicates that the remote UE 102 has already attached a non-relayed, direct connection to the core network 105. As such, the remote UE 102 is within the coverage area of the access node 104. The remote UE 102 has thus connected to the network in a standard, conventional manner.
  • the remote UE 102 may decide that it would like a relayed connection towards the network. In order to discover potential UEs that could serve as a relay for the remote UE 102, the remote UE 102 may initiate a proximity-based applications and services, ProSe, discovery process 108.
  • ProSe proximity-based applications and services
  • a ProSe discovery process 108 is a process that identifies a UE that is ProSe-enabled in the proximity of another, using evolved UMTS Terrestrial Radio Access, E-UTRA or the evolved packet core, EPC.
  • the depicted ProSe discovery process 108 may result in the discovery of the relay capable UE 103, i.e. a UE that is capable to act as a relay for the remote UE 102.
  • the remote UE 102 sends 109 a Request Relay message to the discovered relay capable UE 103 via a PC5 connection.
  • the message is a request from the remote UE 102 for using the relay capable UE 103 as a relay to the core network 105.
  • This Request Relay message may include an identifier, for example the temporary Cell Radio Network Temporary Identifier, C-RNTI, for identifying said remote UE 102 at the access node 104.
  • the message may further comprise information with respect to Quality-of-Service, QoS, requirements that the remote UE 102 needs or already has on existing Radio Bearers.
  • QoS Quality-of-Service
  • the relay capable UE 103 may perform checks 110, i.e. processing constraints, QoS parameters, allowed UE's to be relayed, etc., whether to authorize the relaying of the remote UE 102. In case of a positive outcome, the relay capable UE 103 sends 111 the Request Relay message towards the access node 104. In another embodiment, the relay capable UE 103 sends 111 the Request Relay message towards the access node 104 without performing checks 110.
  • checks 110 i.e. processing constraints, QoS parameters, allowed UE's to be relayed, etc.
  • the access node 104 will then find, if available, the connection 107 it already has to the remote UE 102 based on the identifier, i.e. the temporary Cell Radio Network Temporary Identifier, present in the Request Relay message. If it is determined 112 that the initial connection 107 of the remote UE 102 to the core network 105 is not established via the same access node 104 as the connection of the relay capable UE 103 to the core network 105, a Request Relay Complete message is sent 124, 125 from the access node 104, via the relay capable UE 103 to the remote UE 102. This message indicates that relay is currently not possible.
  • the identifier i.e. the temporary Cell Radio Network Temporary Identifier
  • An alternative to sending the Request Relay Complete message is to perform a handover such that the remote UE is serviced by the same access node as the relay capable UE.
  • the block indicated with reference numeral 126 depicts the situation that the remote UE 102 is to release its connection 107 to the core network 105, and is to initiate the start of the relaying process from the ECM-ldle state as will be elucidated with respect to figure 3 .
  • the access node 104 sends 113 a command for establishing the UE-to-UE bearer and the second UE-to-access node bearer.
  • This command is, for example, coupled to an RRC Radio Bearer Setup procedure message having embedded therein an PC5 bearer setup flag.
  • the relay capable UE 103 receives the command and uses, for example, PC5 signalling 114 to invoke a UE-to-UE bearer setup between the remote UE 102 and the relay capable UE 103, for example the PC5 bearer setup.
  • the relay capable UE 103 may acknowledge 117 the establishment of both bearers to the access node 104.
  • the relay capable UE 103 may further save 116 any information necessary to relay Packet Data Convergence Protocol, PDCP, data between the remote UE 102 and the access node 104.
  • the access node 104 may store 118 the information related to the underlying bearers of the Remote Radio Access Bearer, i.e. the established UE-to-UE bearer, the established UE-to-access node bearer and an access node-to-core network bearer.
  • the access node-to-core network bearer may be the same bearer as was previously used for the connection of the remote UE to the network or it may also be a different bearer. Typically, such a bearer is the S1 bearer.
  • the access node 104 sends 120 a Request Relay Complete message to the relay capable UE 103, which, in turn, sends 121 this message to the remote UE 102 indicating that the Remote Radio Access Bearer has been established. Further, the access node 104 may send a command 122 to the remote UE 102 to release its initial connection 107 to the core network. Alternatively, the access node 104 could release the connection 107 by itself and acknowledge this to the remote UE. The procedure is then completed by the remote UE 102 updating its tracking area 123 to the core network 105, using a Non Access Stratum, NAS, connection.
  • NAS Non Access Stratum
  • Fig. 3 shows a signalling diagram 201 in which a UE-to-UE bearer as well as a second UE-to-access node bearer is established for a remote UE in idle mode.
  • the remote UE is indicated with reference numeral 202
  • the relay capable UE is indicated with reference numeral 203
  • the access node is indicated with reference numeral 204
  • the core network is indicated with reference numeral 205
  • the ProSe function is indicated with reference numeral 206.
  • the signalling diagram 201 depicted in figure 3 discloses the situation in which the remote UE 202 does not have a Radio Access Bearer established to the core network 205, or in the situation that the remote UE 202 has lost its connection, but is still known in the network. In these kinds of situations, the procedure is supplemented with an additional service request message which will be explained in more detail here below.
  • the remote UE 202 attaches 207 to the core network 205 in a conventional manner.
  • the remote UE 202 performs a ProSe discovery process 208 to determine whether there are UE's in its proximity that could serve as a relay for a connection to the core network 205.
  • the remote UE is in idle mode 209, which is for example indicated with the ECM-IDLE state in a Long Term Evolution, LTE, network.
  • the remote UE 202 sends 210 a Request Relay message towards the relay capable UE 203 for using the relay capable UE 203 as a relay to the core network 205.
  • the Request Relay message also comprises a Service Request for requesting services from the telecommunication network.
  • the service request may, alternatively, also be sent in a separate message.
  • Such a service request is, for example, an LTE Service Request message directed to the MME.
  • the relay capable UE 203 may again perform checks 211 to determine whether it can serve as a relay for the remote UE 202, and, if approved, it forwards 212 the Request Relay message, comprising the service request, to the access node 204.
  • the relay capable UE 203 sends 212 the Request Relay message towards the access node 204 without performing checks 211.
  • the access node 204 Upon receipt of the Request Relay message, the access node 204 forwards 213 the service request to the core network 205, and receives 214 a context setup procedure from the core network 205, for example from the Mobility Management Entity.
  • step 215 corresponds to step 113
  • step 216 corresponds to step 114
  • step 217 corresponds to step 115
  • step 218 corresponds to step 116
  • step 219 corresponds to step 117
  • step 220 corresponds to 118
  • step 222 corresponds to step 120
  • step 223 corresponds to step 121
  • step 224 corresponds to step 123.
  • the access node 204 confirms 221 to the core network 205 that the context setup procedure is completed.
  • Fig. 4 shows a signalling diagram 301 in which the relaying for the remote UE is stopped.
  • the remote UE is indicated with reference numeral 302
  • the relay capable UE is indicated with reference numeral 303
  • the access node is indicated with reference numeral 304
  • the core network is indicated with reference numeral 305.
  • a Remote Radio Access Bearer 306 is established between the remote UE 302 and the core network 305 via the relay capable UE 303 and the access node 304.
  • the remote UE 302 decides to cancel the relaying of traffic via the relay capable UE 303 (e.g. because the remote UE 302 notices that the connection with the relay capable UE 303 is deteriorating) and sends 307 a Request Relay Cancel message to the access node 304 via, for example, Access Stratum signalling.
  • the access node 304 is able to determine 308 that the connection from the remote UE 302 is being relayed via the relay capable UE 303 using an identification of the remote UE 302 or a direct identification of the UE-to-UE bearer established between the remote UE 302 and the relay capable UE 303.
  • the Request Relay Cancel message sent 307 comprises an identification of the Remote Radio Access Bearer for which relaying needs to be cancelled.
  • the access node 304 may have the context information stored to determine that this particular Radio Access Bearer is in fact a Remote Radio Access Bearer.
  • a Radio Bearer Setup message is then sent 309 by the access node 304 to the remote UE 302 to initiate the establishment of a radio bearer directly between the remote UE 302 and the access node 304.
  • This new radio bearer is not to be established via the relay capable UE 303.
  • the remote UE 302 then confirms 310 the establishment of the Radio Bearer, and the remote UE 302 starts using 311 the bearer for, for example, uplink data. Then, the access node 304 confirms 312 cancelling of the relay, changes 313 the specific Remote Radio Access Bearer into a normal Radio Access Bearer 306 and starts using 314 the direct radio bearer to the remote UE 302 for downlink traffic.
  • the access node 304 orders the relay capable UE 303 to release all relay resources by sending 315, 316 a Radio Bearer Release message comprising a UE-to-UE bearer release Flag. This triggers the release procedure to the remote UE 302, and is acknowledged, by the remote UE 302, in an acknowledgement message 317, 318 towards the access node 304.
  • a timeout mechanism may be used to release the resources in the remote UE.
  • the access node removes 319 all information with respect to the relaying connection of the remote UE 302 to the core network 304 and the remote UE 302 updates 320 its tracking area to the core network 304.
  • Fig. 5 shows a signalling diagram 401 in which the remote UE switches from an idle mode to a connected mode during relaying by the relay capable UE.
  • the remote UE is indicated with reference numeral 402
  • the relay capable UE is indicated with reference numeral 403
  • the access node is indicated with reference numeral 404
  • the core network is indicated with reference numeral 405.
  • the remote UE 402 may use the relay capable UE 403 as a relay and its connectivity states are the same as when its connection to the network is direct, i.e. not relayed. Moving from an idle state to a connected state may then be performed as shown in figure 5 . That is, a service request message, for example an NAS service request message, is sent 406 over the UE-to-UE signalling connection to the relay capable UE 403, which relay capable UE 403, in turn, forwards 407 that request to the access node 404, which access node 404, in turn, forwards 408 the request to the core network 405.
  • a service request message for example an NAS service request message
  • a confirmation is sent 409, 410, 411 by the core network 405 and is forwarded by each of the intermediate nodes 404, 403 to the remote UE 402, wherein the confirmation comprises an UE-to-UE bearer setup flag for indicating that the UE-to-UE bearer should be established.
  • the remote UE 402 then sends 412 a confirmation to the relay capable UE 403 that the UE-to-UE bearer is established, and the relay capable UE 403 stores 413 any information related to the relayed connection.
  • An identification of the UE-to-UE bearer is then sent 414 to the access node, and the access node saves 415 any information, i.e. information related to the Remote Radio Access Bearer, with respect to the remote UE 402 as a relayed connection from the remote UE 402 to the core network 405 via the relay capable UE 403.
  • a confirmation is sent 416 to the core network for indicating that the bearers have been established.
  • Fig. 6 shows an example of a control plane stack 501 between the remote UE, the relay capable UE, the access node as well as the core network.
  • the remote UE is indicated with reference numeral 502
  • the relay capable UE is indicated with reference numeral 503
  • the access node is indicated with reference numeral 504
  • the core network more specifically the MME, is indicated with reference numeral 505.
  • the remote UE 502 is arranged for establishing a connection between a remote UE and a telecommunication network via the relay capable UE 503.
  • the remote UE comprises a transmitter arranged for sending to the relay capable UE 503, a Request Relay message, wherein the Request Relay message comprises a request for using the relay capable UE 503 as a relay to the core network.
  • the request is associated with establishment of a Remote Radio Access Bearer, wherein said Remote Radio Access Bearer comprises a UE-to-UE bearer between said remote UE and said relay capable UE, a second UE-to-access node bearer between said relay capable UE and said access node, wherein said second UE-to-access node bearer is different from said first UE-to-access node bearer, and an access node-to-core network bearer between said access node and said core network.
  • said Remote Radio Access Bearer comprises a UE-to-UE bearer between said remote UE and said relay capable UE, a second UE-to-access node bearer between said relay capable UE and said access node, wherein said second UE-to-access node bearer is different from said first UE-to-access node bearer, and an access node-to-core network bearer between said access node and said core network.
  • the remote UE 502 further comprises a processor arranged for establishing said UE-to-UE signalling connection, and for establishing a Non-Access Stratum, NAS, connection 506 between said remote UE and said core network over said established UE-to-UE signalling connection.
  • NAS Non-Access Stratum
  • the NAS connection 506 is established over the PC5 signalling connection.
  • a computer program may be stored/distributed on a suitable medium, such as an optical storage medium or a solid-state medium supplied together with or as part of other hardware, but may also be distributed in other forms, such as via the Internet or other wired or wireless telecommunication systems. Any reference signs in the claims should not be construed as limiting the scope thereof.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)
EP16197546.1A 2016-11-07 2016-11-07 Establishing a connection between a remote user equipment, ue, and a telecommunication network via a relay capable ue Active EP3319393B1 (en)

Priority Applications (7)

Application Number Priority Date Filing Date Title
EP16197546.1A EP3319393B1 (en) 2016-11-07 2016-11-07 Establishing a connection between a remote user equipment, ue, and a telecommunication network via a relay capable ue
KR1020197016394A KR102293786B1 (ko) 2016-11-07 2017-11-06 릴레이 가능 사용자 장비(ue)를 통하여 원격 ue 및 통신 네트워크 사이의 접속을 확립하는 방법 및 시스템
PCT/EP2017/078308 WO2018083293A1 (en) 2016-11-07 2017-11-06 A method of, and systems for, establishing a connection between a remote user equipment, ue, and a telecommunication network via a relay capable ue
EP17800457.8A EP3536113A1 (en) 2016-11-07 2017-11-06 A method of, and systems for, establishing a connection between a remote user equipment, ue, and a telecommunication network via a relay capable ue
CN201780068710.XA CN109892003B (zh) 2016-11-07 2017-11-06 经由具有中继能力的用户装备ue在远程ue和电信网络之间建立连接的方法和系统
US16/347,447 US11076435B2 (en) 2016-11-07 2017-11-06 Method of, and systems for, establishing a connection between a remote user equipment, UE, and a telecommunication network via a relay capable UE
US17/355,878 US20210321471A1 (en) 2016-11-07 2021-06-23 Method of, and Systems for, Establishing a Connection Between a Remote User Equipment, UE, and a Telecommunication Network Via a Relay Capable UE

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
EP16197546.1A EP3319393B1 (en) 2016-11-07 2016-11-07 Establishing a connection between a remote user equipment, ue, and a telecommunication network via a relay capable ue

Publications (2)

Publication Number Publication Date
EP3319393A1 EP3319393A1 (en) 2018-05-09
EP3319393B1 true EP3319393B1 (en) 2019-08-07

Family

ID=57288158

Family Applications (2)

Application Number Title Priority Date Filing Date
EP16197546.1A Active EP3319393B1 (en) 2016-11-07 2016-11-07 Establishing a connection between a remote user equipment, ue, and a telecommunication network via a relay capable ue
EP17800457.8A Pending EP3536113A1 (en) 2016-11-07 2017-11-06 A method of, and systems for, establishing a connection between a remote user equipment, ue, and a telecommunication network via a relay capable ue

Family Applications After (1)

Application Number Title Priority Date Filing Date
EP17800457.8A Pending EP3536113A1 (en) 2016-11-07 2017-11-06 A method of, and systems for, establishing a connection between a remote user equipment, ue, and a telecommunication network via a relay capable ue

Country Status (5)

Country Link
US (2) US11076435B2 (ko)
EP (2) EP3319393B1 (ko)
KR (1) KR102293786B1 (ko)
CN (1) CN109892003B (ko)
WO (1) WO2018083293A1 (ko)

Families Citing this family (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3319393B1 (en) * 2016-11-07 2019-08-07 Koninklijke KPN N.V. Establishing a connection between a remote user equipment, ue, and a telecommunication network via a relay capable ue
WO2020011907A1 (en) 2018-07-12 2020-01-16 Koninklijke Kpn N.V. Multi-hop relaying in a mobile communication network
CN112153708A (zh) * 2019-06-29 2020-12-29 华为技术有限公司 一种通信方法及相关设备
CA3163267A1 (en) 2020-02-21 2021-08-26 Jianhua Liu Method for qos control, apparatus, and readable storage medium
CN113556709A (zh) * 2020-04-23 2021-10-26 华为技术有限公司 一种通信方法及装置
US11849382B2 (en) * 2020-05-28 2023-12-19 Huawei Technologies Co., Ltd. Methods, apparatus, and systems for fast path switching in wireless communications with user equipment (UE) cooperation
CN115428578A (zh) * 2020-06-01 2022-12-02 上海诺基亚贝尔股份有限公司 经由中继的远程设备的初始接入
CN114071796A (zh) * 2020-07-31 2022-02-18 大唐移动通信设备有限公司 一种中继链路连接控制方法及装置
WO2021195646A2 (en) * 2020-08-05 2021-09-30 Futurewei Technologies, Inc. Methods and apparatus for connection setup of sidelink relays
WO2022040828A1 (en) * 2020-08-23 2022-03-03 Qualcomm Incorporated Layer 2 relay initial configuration
WO2022052092A1 (en) * 2020-09-14 2022-03-17 Mediatek Singapore Pte. Ltd. Connection establishment for a layer 2 ue-to-network relay
KR102488700B1 (ko) * 2020-09-15 2023-01-17 한국전자통신연구원 단말 릴레이 지원 방법 및 장치
KR20230104633A (ko) * 2020-10-20 2023-07-10 프라운호퍼 게젤샤프트 쭈르 푀르데룽 데어 안겐반텐 포르슝 에. 베. 중계 시나리오에서의 사용자 평면 데이터 핸들링
WO2023004529A1 (en) * 2021-07-26 2023-02-02 Qualcomm Incorporated Techniques for performing quality of service management for sidelink communications

Family Cites Families (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2010019970A1 (en) * 2008-08-15 2010-02-18 Kineto Wireless, Inc. Method and apparatus for inter home node b cell update handling
JP4704482B2 (ja) 2009-06-08 2011-06-15 株式会社エヌ・ティ・ティ・ドコモ 移動通信システム、リレーノード、無線基地局及びゲートウェイ装置
CN101998671B (zh) 2009-08-18 2013-10-09 财团法人资讯工业策进会 演进型nodeB、中继节点及其连接初始化方法
EP2550834A1 (en) * 2010-03-25 2013-01-30 Qualcomm Incorporated Radio bearer management at a donor base station in a wireless network with relays
US9386618B2 (en) * 2012-08-03 2016-07-05 Futurewei Technologies, Inc. System and method to support multiple radio access technology relays with a unified backhaul transport network
CN105009610B (zh) * 2013-02-28 2018-07-27 Lg电子株式会社 提供邻近服务的组通信方法和装置
GB2523328A (en) * 2014-02-19 2015-08-26 Nec Corp Communication system
EP3183865B1 (en) * 2014-08-22 2022-06-22 Telefonaktiebolaget LM Ericsson (publ) A method, system and device for accessing data storage in a telecommunications network.
EP3216259A2 (en) * 2014-11-07 2017-09-13 Interdigital Patent Holdings, Inc. Optimizations for relay communications
JP6337198B2 (ja) * 2015-04-10 2018-06-06 京セラ株式会社 無線端末、プロセッサ及び制御方法
WO2016167550A1 (ko) * 2015-04-13 2016-10-20 삼성전자 주식회사 D2d 통신을 지원하는 무선 통신 시스템에서 중계 트래픽 제어 방법 및 장치
WO2017026872A1 (ko) * 2015-08-13 2017-02-16 엘지전자 주식회사 무선 통신 시스템에서 리모트 ue의 신호 송수신 방법 및 이를 위한 장치
US10433286B2 (en) * 2016-07-14 2019-10-01 Nokia Of America Corporation Layer 2 relay to support coverage and resource-constrained devices in wireless networks
CN109644388B (zh) * 2016-08-08 2021-06-15 Lg 电子株式会社 使用中继ue的接入控制的方法及其装置
US20190230723A1 (en) * 2016-09-05 2019-07-25 Lg Electronics Inc. Method for performing service request procedure in wireless communication system and device therefor
US10477608B2 (en) * 2016-09-29 2019-11-12 Futurewei Technologies, Inc. System and method for network access using a relay
WO2018063081A1 (en) * 2016-09-30 2018-04-05 Telefonaktiebolaget Lm Ericsson (Publ) Relaying between a user equipment and a network
WO2018063082A1 (en) * 2016-09-30 2018-04-05 Telefonaktiebolaget Lm Ericsson (Publ) Radio resource control connection establishment
US11903085B2 (en) * 2016-11-02 2024-02-13 Telefonaktiebolaget Lm Ericsson (Publ) Mobility management for relaying
EP3319393B1 (en) * 2016-11-07 2019-08-07 Koninklijke KPN N.V. Establishing a connection between a remote user equipment, ue, and a telecommunication network via a relay capable ue
WO2018155908A1 (ko) * 2017-02-22 2018-08-30 엘지전자(주) 무선 통신 시스템에서 릴레이를 통한 데이터 송수신 방법 및 이를 위한 장치
US11184936B2 (en) * 2017-05-05 2021-11-23 Lg Electronics Inc. Method and apparatus for managing a bearer configuration of a relay user equipment
US10631346B2 (en) * 2017-08-08 2020-04-21 Qualcomm Incorporated Communicating remote and local data in a wireless fronthaul

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
KR20190082869A (ko) 2019-07-10
US20190335518A1 (en) 2019-10-31
CN109892003B (zh) 2022-07-19
US20210321471A1 (en) 2021-10-14
EP3319393A1 (en) 2018-05-09
EP3536113A1 (en) 2019-09-11
CN109892003A (zh) 2019-06-14
WO2018083293A1 (en) 2018-05-11
US11076435B2 (en) 2021-07-27
KR102293786B1 (ko) 2021-08-25

Similar Documents

Publication Publication Date Title
US20210321471A1 (en) Method of, and Systems for, Establishing a Connection Between a Remote User Equipment, UE, and a Telecommunication Network Via a Relay Capable UE
JP7189126B2 (ja) 無線通信システムにおけるサービス要求手順の実行方法とそのための装置
US11758609B2 (en) Radio resource control RRC message processing method, apparatus, and system
US9769709B2 (en) Handover method, communication device and communication system
US11477633B2 (en) Method and apparatus for managing packet data network connection on basis of local area in wireless communication system
US9973976B2 (en) Efficient session management method and apparatus guaranteeing terminal mobility
EP3729844B1 (en) A method of, and devices for, establishing a signalling connection between a remote user equipment, ue, and a telecommunication network via a relay capable ue
CN109151932B (zh) 处理双连接中交递的装置及方法
US10455459B2 (en) Method and apparatus for establishing session for data transmission and reception in wireless communication system
US11330479B2 (en) Method for supporting data forwarding during conditional handover and dual stack protocol handover in next-generation mobile communication system
US20230388891A1 (en) Managing ue information after preparing a conditional mobility procedure

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

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

Free format text: STATUS: THE APPLICATION HAS BEEN PUBLISHED

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: KONINKLIJKE KPN N.V.

Owner name: NEDERLANDSE ORGANISATIE VOOR TOEGEPAST- NATUURWETE

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

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

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 76/02 20090101AFI20170420BHEP

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602016018023

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04W0076020000

Ipc: H04W0076140000

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

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 76/14 20180101AFI20190304BHEP

INTG Intention to grant announced

Effective date: 20190326

RIN1 Information on inventor provided before grant (corrected)

Inventor name: NORP, ANTONIUS

Inventor name: DIMITROVSKI, TONI

Inventor name: DJURICA, MIODRAG

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

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

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

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

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

Ref country code: AT

Ref legal event code: REF

Ref document number: 1165848

Country of ref document: AT

Kind code of ref document: T

Effective date: 20190815

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602016018023

Country of ref document: DE

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: SE

Ref legal event code: TRGR

REG Reference to a national code

Ref country code: NL

Ref legal event code: FP

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

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

Ref country code: 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: 20190807

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

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

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

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

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

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1165848

Country of ref document: AT

Kind code of ref document: T

Effective date: 20190807

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

Ref country code: AL

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

Effective date: 20190807

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

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

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

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

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

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

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

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

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

Ref country code: AT

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

Effective date: 20190807

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

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

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

Ref country code: CZ

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

Effective date: 20190807

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

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

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

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602016018023

Country of ref document: DE

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

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

PG2D Information on lapse in contracting state deleted

Ref country code: IS

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

Ref country code: LI

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

Effective date: 20191130

Ref country code: LU

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

Effective date: 20191107

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

26N No opposition filed

Effective date: 20200603

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20191130

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

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

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

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

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

Ref country code: HU

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

Effective date: 20161107

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

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

P01 Opt-out of the competence of the unified patent court (upc) registered

Effective date: 20230517

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

Ref country code: NL

Payment date: 20231120

Year of fee payment: 8

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

Ref country code: GB

Payment date: 20231123

Year of fee payment: 8

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

Ref country code: SE

Payment date: 20231120

Year of fee payment: 8

Ref country code: IT

Payment date: 20231124

Year of fee payment: 8

Ref country code: FR

Payment date: 20231120

Year of fee payment: 8

Ref country code: DE

Payment date: 20231121

Year of fee payment: 8