WO2019034659A1 - Procédure de compte-rendu d'informations d'équipement utilisateur - Google Patents

Procédure de compte-rendu d'informations d'équipement utilisateur Download PDF

Info

Publication number
WO2019034659A1
WO2019034659A1 PCT/EP2018/072038 EP2018072038W WO2019034659A1 WO 2019034659 A1 WO2019034659 A1 WO 2019034659A1 EP 2018072038 W EP2018072038 W EP 2018072038W WO 2019034659 A1 WO2019034659 A1 WO 2019034659A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
ran
request
amf
reporting
Prior art date
Application number
PCT/EP2018/072038
Other languages
English (en)
Inventor
Qian Chen
Paul Schliwa-Bertling
Peter Ramle
Hans Bertil RÖNNEKE
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
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 Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2019034659A1 publication Critical patent/WO2019034659A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/04—Interfaces between hierarchically different network devices
    • H04W92/045—Interfaces between hierarchically different network devices between access point and backbone network device

Definitions

  • the present disclosure relates generally to a method of reporting wireless device information.
  • RRC Radio Resource Control
  • a method of operating a Core Access and Mobility Management Function (AMF) for obtaining information about a User Equipment (UE) includes sending, to a Radio Access Network (RAN), a request for information about the UE and receiving, from the RAN, information about the UE.
  • a method of operating a for reporting information about a UE includes receiving, from a AMF, a request for information about the UE and sending, to the AMF, information about the UE.
  • AMF Core Access and Mobility Management Function
  • the request for information about the UE includes a request for information about where the UE is currently located and/or RRC state transition information of the UE.
  • the request for information about the UE includes a request for information about where the UE is currently located and/or RRC state transition information of the UE.
  • TAI Tracking Area Identity
  • Cell Identity for the UE.
  • the request for information about the UE includes an indication of a reporting type that indicates whether the request is intended to trigger a single standalone report or start the RAN to report whenever a change happens.
  • the method also includes sending to the RAN or receiving from the AMF, a request to cancel UE information reporting.
  • receiving information about the UE includes receiving a UE Information Report reporting that the UE has transitioned into an RRC Inactive state and that location information therefore from now on may be inaccurate.
  • receiving information about the UE includes receiving a UE Information Report reporting that the UE has transitioned into RRC Connected state.
  • the information about the UE also includes information about where the UE is currently located.
  • the AMF and the RAN are part of a Fifth Generation (5G) communications network.
  • the AMF and the RAN are part of a Fifth Generation (5G) communications network.
  • the AMF and the RAN are part of a Fifth Generation (5G) communications network.
  • communications between the RAN and the AMF are over an N2 interface between the RAN and the AMF.
  • the present disclosure proposes to introduce a general UE information reporting procedure at the N2 interface which can either be used by the NR-RAN to report UE location information or the UE RRC state information and its transition, or both.
  • Figure 1 depicts the non-roaming reference architecture for Fifth Generation (5G);
  • Figure 2 illustrates the previous Location Reporting Procedure
  • Figure 3 illustrates a procedure that can be used to report User
  • Equipment information according to some embodiments of the present disclosure
  • Figure 4 illustrates another procedure that can be used to report UE information according to some embodiments of the present disclosure
  • Figures 5 and 6 illustrate example embodiments of a wireless device such as a UE.
  • Figures 7 through 9 illustrate example embodiments of a network node.
  • the Fifth Generation (5G) architecture is defined as service based, and the interaction between Network Functions (NFs) is represented in two ways.
  • One is a service-based representation, where NFs within the control plane enable other authorized NFs to access their services. This representation also includes point-to-point reference points where necessary.
  • the other is a reference point representation, which shows the interaction between the NF services in the NFs, described by point-to-point reference points between any two NFs (e.g., Core Access and Mobility Management Function (AMF) and Session Management Function (SMF)).
  • AMF Core Access and Mobility Management Function
  • SMF Session Management Function
  • Figure 1 depicts the non-roaming reference architecture for 5G.
  • the 5G System architecture consists of the following NFs and entities: Authentication Server Function (AUSF), AMF, Network Exposure Function (NEF), NF Repository Function (NRF), Policy Control Function (PCF), SMF Unified Data Management (UDM), User Plane Function (UPF), Application Function (AF), UE, (Radio) Access Network ((R)AN).
  • AUSF Authentication Server Function
  • AMF Access Management Function
  • NEF Network Exposure Function
  • NRF NF Repository Function
  • PCF Policy Control Function
  • UDM Unified Data Management
  • UPF User Plane Function
  • AF Application Function
  • UE Radio
  • Radio Radio Access Network
  • UE location reporting procedure exists at an N2 interface between RAN and AMF.
  • RRC Radio Resource Control
  • the 5GC is not aware of the UE transitions between CM- CONNECTED with RRC Connected and CM-CONNECTED with RRC Inactive state.
  • Figure 2 illustrates the previous Location Reporting Procedure defined in TS 23.502 vO.5.0. This procedure is used by an AMF to request the RAN to report where the UE is currently located when the target UE is in CM- CONNECTED state. The need for the RAN to continue reporting ceases when the UE transitions to CM-IDLE or the AMF sends a cancel indication. This procedure may be used for services that require accurate cell identification (e.g. emergency services, lawful intercept, charging), or for subscription to the service by other NFs.
  • This procedure may be used for services that require accurate cell identification (e.g. emergency services, lawful intercept, charging), or for subscription to the service by other NFs.
  • the AMF sends a Location Reporting Control message to the RAN (step 100).
  • the Location Reporting Control message shall identify the UE for which reports are requested, the requested location
  • reporting type indicates whether the message is intended to trigger a single standalone report about the current Cell Identity serving the UE or start the RAN to report whenever the UE changes cell.
  • the RAN sends a Location Report message informing the AMF about the location of the UE which shall include the requested location
  • the AMF can send a Cancel Location Reporting message to inform the RAN that it should terminate location reporting for a given UE (step 104). This message is needed only when the reporting was requested for a reporting period. Location reporting is transferred during Xn handover, although new control signaling is not transferred during an active handover.
  • a method of operating an AMF for obtaining information about a UE includes sending, to a RAN, a request for information about the UE and receiving, from the RAN, information about the UE.
  • a method of operating a for reporting information about a UE includes receiving, from a AMF, a request for information about the UE and sending, to the AMF, information about the UE.
  • a general UE information reporting procedure is introduced at the N2 interface which can be used by the RAN to report UE location info, UE RRC state information, and/or RRC state transitions.
  • Figure 3 illustrates a procedure that can be used to report UE information according to some embodiments of the present disclosure.
  • This procedure can be used to report both RRC state and location information.
  • this procedure is used by an AMF to request the RAN to report UE information, i.e., where the UE is currently located or RRC state transition information, when the target UE is in CM-CONNECTED state.
  • the need for the RAN to continue reporting ceases when the UE transitions to CM-IDLE or the AMF sends a cancel indication.
  • This procedure may be used for services that require accurate cell identification (e.g., emergency services, lawful intercept, charging), or for subscription to the service by other NFs.
  • RRC state and its transition notification from RAN to AMF is always performed based on local RAN configuration while in other embodiments it is based on request from AMF.
  • the AMF 310 sends a UE information reporting control message to the RAN 320 (step 200), e.g. a UE information reporting control request message.
  • the UE information reporting control message shall identify the UE for which reports are requested, and the requested information can be location information, RRC state information, or both, and may contain information such as reporting type.
  • the RRC state information includes the RRC state and its transition.
  • requested location information could be Tracking Area Identity (TAI) + cell identity and/or RRC state.
  • TAI Tracking Area Identity
  • Requesting both location information and RRC state information has the advantage of avoiding a separate procedure on N2 interface for each information type, which may introduce extra logic internally in the NF and also extra signaling on the N2 interface.
  • the reporting type indicates whether the message is intended to trigger a single standalone report or start the RAN 320 to report whenever a change happens.
  • the RAN 320 sends a UE information report message informing the AMF 310 about the location of the UE which shall include the requested location information if any, or (and) RRC state and its transition information (i.e., into RRC inactive or into RRC connected state) (step 202).
  • Reporting both location information and RRC state information has the advantage of avoiding separate procedures on N2 interface for each information type, which may introduce extra logic internally in the NF and also extra signaling on the N2 interface.
  • the RAN 320 sends a UE information report to the AMF 310 reporting that the UE has transitioned into RRC inactive state and that location information therefore from now on may be inaccurate and that location information reporting will commence again when the UE transitions into RRC connected state.
  • the RAN 320 sends a subsequent UE information report to the AMF 310 when the UE has transitioned into RRC connected state reporting both the RRC state transition and the location.
  • the AMF 310 can send a cancel UE information reporting message to inform the RAN 320 that it should terminate reporting for a given UE (step 204).
  • a general UE information reporting procedure is introduced at the N2 interface which can be used by the RAN 320 to report UE location info, UE RRC state information, and/or RRC state transitions.
  • Figure 4 illustrates another procedure that can be used to report UE information according to some embodiments of the present disclosure.
  • This procedure is dedicated to report RRC state.
  • this procedure is used by RAN to notify 5GC of the RRC state transition in case no serving RAN node change while the UE is in CM-CONNECTED state.
  • the RAN suspends the RRC connection and performs a RRC connected to RRC inactive state transition or when the RAN resumes the RRC connection and performs a RRC inactive to RRC connected state transition, the RAN notifies the 5GC about the RRC state transition, together with the latest UE location information.
  • the AMF 410 sends a UE state transition notification request message to the RAN 420 (step 300).
  • the UE state transition notification request message may contain a reporting type to indicate whether the message triggers a single standalone report about the current RRC state or triggers the RAN 420 to report during a period whenever the RRC state changes until the UE transitions to CM-IDLE or the AMF 410 sends a cancel UE state notification.
  • this indication can be sent when the UE context is established towards the RAN 420. In some embodiments, this indication can be sent after the UE context is established.
  • the RAN 420 uses the UE notification message to report a transition into a new RRC state (i.e., RRC inactive state or RRC connected state), i.e. the RAN 420 sends a UE notification message to the AMF 410 (step 302).
  • the UE notification message shall include the latest UE location information.
  • the location report message of the location reporting procedure shall not be sent when the UE notification message is already triggered due to RRC state transition.
  • the RAN does not send any location report messages for a UE that is in RRC inactive state.
  • the AMF 410 can send a cancel UE state notification message to inform the RAN 420 that it should terminate notifications for a given UE (step 304).
  • FIG. 5 is a schematic block diagram of the wireless device 12 (e.g., UE) according to some embodiments of the present disclosure.
  • the wireless device 12 includes circuitry 20 comprising one or more processors 22 (e.g., Central Processing Units (CPUs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), Digital Signal Processors (DSPs), and/or the like) and memory 24.
  • the wireless device 12 also includes one or more transceivers 26 each including one or more
  • the functionality of the wireless device 12 described herein may be implemented in hardware (e.g., via hardware within the circuitry 20 and/or within the processor(s) 22) or be implemented in a combination of hardware and software (e.g., fully or partially implemented in software that is, e.g., stored in the memory 24 and executed by the processor(s) 22).
  • a computer program including instructions which, when executed by the at least one processor 22, causes the at least one processor 22 to carry out at least some of the functionality of the wireless device 12 according to any of the embodiments described herein is provided.
  • a carrier containing the aforementioned computer program product is provided.
  • the carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory).
  • FIG. 6 is a schematic block diagram of the wireless device 12 (e.g., UE) according to some other embodiments of the present disclosure.
  • the wireless device 12 includes one or more modules 34, each of which is
  • the module(s) 34 provide the functionality of the wireless device 12 described herein.
  • FIG. 7 is a schematic block diagram of a network node 36 (e.g., a RAN 14 such as, for example, an eNB or gNB or a core network node such as, for example, a AMF) according to some embodiments of the present disclosure.
  • the network node 36 includes a control system 38 that includes circuitry comprising one or more processors 40 (e.g., CPUs, ASICs, DSPs, FPGAs, and/or the like) and memory 42.
  • the control system 38 also includes a network interface 44.
  • the network node 36 is a radio access node 14
  • the network node 36 also includes one or more radio units 46 that each include one or more transmitters 48 and one or more receivers 50 coupled to one or more antennas 52.
  • the functionality of the network node 36 (specifically the functionality of the radio access node 14) described above may be fully or partially implemented in software that is, e.g., stored in the memory 42 and executed by the processor(s) 40.
  • FIG. 8 is a schematic block diagram that illustrates a virtualized embodiment of the network node 36 (e.g., the radio access node 14 or a core network node) according to some embodiments of the present disclosure.
  • a "virtualized" network node 36 is a network node 36 in which at least a portion of the functionality of the network node 36 is implemented as a virtual component (e.g., via a virtual machine(s) executing on a physical processing node(s) in a network(s)).
  • the network node 36 optionally includes the control system 38, as described with respect to Figure 7.
  • the network node 36 is the radio access node 14
  • the network node 36 also includes the one or more radio units 46, as described with respect to Figure 7.
  • the control system 38 (if present) is connected to one or more processing nodes 54 coupled to or included as part of a network(s) 56 via the network interface 44.
  • the one or more radio units 46 are connected to the one or more processing nodes 54 via a network interface(s).
  • all of the parameters are connected to the one or more processing nodes 54 via a network interface(s).
  • functionality of the network node 36 e.g., all of the functionality of the radio access node 14 or the core network node 19 described herein may be
  • Each processing node 54 includes one or more processors 58 (e.g., CPUs, ASICs, DSPs, FPGAs, and/or the like), memory 60, and a network interface 62.
  • processors 58 e.g., CPUs, ASICs, DSPs, FPGAs, and/or the like
  • functions 64 of the network node 36 are implemented at the one or more processing nodes 54 or distributed across the control system 38 (if present) and the one or more processing nodes 54 in any desired manner.
  • some or all of the functions 64 of the network node 36 described herein are implemented as virtual components executed by one or more virtual machines implemented in a virtual environment(s) hosted by the processing node(s) 54.
  • processing node(s) 54 As will be appreciated by one of ordinary skill in the art, additional signaling or communication between the processing node(s) 54 and the control system 38 (if present) or alternatively the radio unit(s) 46 (if present) is used in order to carry out at least some of the desired functions.
  • the control system 38 may not be included, in which case the radio unit(s) 46 (if present) communicates directly with the processing node(s) 54 via an appropriate network interface(s).
  • higher layer functionality e.g., layer 3 and up and possibly some of layer 2 of the protocol stack
  • lower layer functionality e.g., layer 1 and possibly some of layer 2 of the protocol stack
  • a computer program including instructions which, when executed by the at least one processor 40, 58, causes the at least one processor 40, 58 to carry out the functionality of the network node 36 or a processing node 54 according to any of the embodiments described herein is provided.
  • a carrier containing the aforementioned computer program product is provided.
  • the carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as the memory 60).
  • FIG. 9 is a schematic block diagram of the network node 36 (e.g., the RAN 14 or a core network node such as AMF) according to some other embodiments of the present disclosure.
  • the network node 36 includes one or more modules 66, each of which is implemented in software.
  • the module(s) 66 provide the functionality of the network node 36 described herein.
  • AMF Access Management Function for obtaining information about a User Equipment (UE), comprising:
  • Radio Access Network sending, to a Radio Access Network (RAN), a request for information about the UE;
  • the request for information about the UE comprises a request for information about at least one of the group consisting of where the UE is currently located and RRC state and its transition information of the UE.
  • the method of embodiment 2 wherein the information about where the UE is currently located comprises a Tracking Area Identity (TAI) and Cell Identity for the UE.
  • TAI Tracking Area Identity
  • Cell Identity for the UE.
  • receiving information about the UE includes receiving a UE Information Report reporting that the UE has transitioned into RRC Inactive state and that location infornnation therefore from now on may be inaccurate.
  • receiving information about the UE includes receiving a UE Information Report reporting that the UE has transitioned into RRC Connected state.
  • sending the request to the RAN and receiving the information from the RAN comprises sending the request to the
  • AMF Core Access and Mobility Management Function
  • a method of operating a Radio Access Network (RAN) for reporting information about a User Equipment (UE), comprising:
  • AMF Core Access and Mobility Management Function
  • the method of embodiment 12 wherein the request for information about the UE comprises a request for information about at least one of the group consisting of where the UE is currently located and RRC state transition information of the UE. 14. The method of embodiment 13 wherein the information about where the UE is currently located comprises a Tracking Area Identity (TAI) and Cell Identity for the UE.
  • TAI Tracking Area Identity
  • Cell Identity for the UE.
  • the request for information about the UE comprises an indication of a reporting type that indicates whether the request is intended to trigger a single standalone report or start the RAN to report whenever a change happens.
  • sending information about the UE includes sending a UE Information Report reporting that the UE has transitioned into RRC Inactive state and that location information therefore from now on may be inaccurate.
  • sending information about the UE includes sending a UE Information Report reporting that the UE has transitioned into RRC Connected state.
  • sending the request to the RAN and receiving the information from the RAN comprises sending the request to the RAN and receiving the information from the RAN over an N2 interface between the RAN and the AMF.
  • a Radio Access Network configured to operate according to any of embodiments 12 through 21 .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention concerne un procédé de fonctionnement d'une fonction AMF (310, 410) pour obtenir des informations concernant un équipement utilisateur (UE pour User Equipment), par exemple, telles que des informations de transition d'état RRC. Le procédé consiste : à envoyer (200, 300), à un réseau RAN (320, 420), une demande d'informations concernant l'équipement utilisateur ; et à recevoir (202, 302), du réseau RAN, des informations concernant l'équipement utilisateur. L'invention concerne également un procédé correspondant dans le réseau RAN ainsi que la fonction AMF et le réseau RAN correspondants.
PCT/EP2018/072038 2017-08-15 2018-08-14 Procédure de compte-rendu d'informations d'équipement utilisateur WO2019034659A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201762545757P 2017-08-15 2017-08-15
US62/545757 2017-08-15

Publications (1)

Publication Number Publication Date
WO2019034659A1 true WO2019034659A1 (fr) 2019-02-21

Family

ID=63207763

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2018/072038 WO2019034659A1 (fr) 2017-08-15 2018-08-14 Procédure de compte-rendu d'informations d'équipement utilisateur

Country Status (1)

Country Link
WO (1) WO2019034659A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020185949A3 (fr) * 2019-03-11 2020-11-05 Ryu Jinsook Radiomessagerie de dispositif sans fil par le biais d'un réseau sans fil

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "RRC Inactive state notification support in TS 23.502", vol. SA WG2, no. Sofia Antipolis, France; 20170821 - 20170825, 15 August 2017 (2017-08-15), XP051334912, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_122BIS_Sophia_Antipolis/Docs/> [retrieved on 20170815] *
HUAWEI ET AL: "TS 23.502: Location Report Procedure", vol. SA WG2, no. San Jose Del Cabo, Mexico; 20170626 - 20170630, 3 July 2017 (2017-07-03), XP051310160, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_122_Cabo/Docs/> [retrieved on 20170703] *
LG ELECTRONICS: "TS 23.502: RRC state reporting procedure", vol. SA WG2, no. San Jose Del Cabo, Mexico; 20170626 - 20170630, 25 June 2017 (2017-06-25), XP051303277, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/SA2/Docs/> [retrieved on 20170625] *
QUALCOMM INCORPORATED: "TS 23.502: Feature specific UE/RAN Radio information and Compatibility Request procedure", vol. SA WG2, no. San Jose Del Cabo, Mexico; 20170626 - 20170630, 3 July 2017 (2017-07-03), XP051310243, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_122_Cabo/Docs/> [retrieved on 20170703] *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020185949A3 (fr) * 2019-03-11 2020-11-05 Ryu Jinsook Radiomessagerie de dispositif sans fil par le biais d'un réseau sans fil
JP2022524122A (ja) * 2019-03-11 2022-04-27 オフィノ， エルエルシー ワイヤレスネットワークによるワイヤレスデバイスのページング
US11412478B2 (en) 2019-03-11 2022-08-09 Ofinno, Llc Wireless device paging by a wireless network
JP7366356B2 (ja) 2019-03-11 2023-10-23 オフィノ， エルエルシー ワイヤレスネットワークによるワイヤレスデバイスのページング
US11889465B2 (en) 2019-03-11 2024-01-30 Ofinno, Llc Paging cause value

Similar Documents

Publication Publication Date Title
US20230093339A1 (en) Session Management Method, Apparatus, and System
US12015682B2 (en) Service subscription method and system for reporting service change in communication system
US20210092634A1 (en) Method Of Processing Network Slice Based Congestion, Device And System Thereof
CN112335285B (zh) 在管理功能移动性间的上下文中的网络功能处理
CN113632512B (zh) 在移动性过程期间传输监视事件信息
JP2023504228A (ja) アプリケーションプログラミングインタフェース（ａｐｉ）フィルタに基づくａｐｉ能力変更の報告
WO2017193293A1 (fr) Procédé et dispositif d&#39;émission de données
US20240031986A1 (en) Nodes and methods for handling paging
WO2020074542A1 (fr) Nssai configurées pour d&#39;autres plmn
US20230388909A1 (en) Ensuring network control of simultaneous access to network slices with application awareness
US20220286953A1 (en) Slice selection subscription data enhancement
WO2019034659A1 (fr) Procédure de compte-rendu d&#39;informations d&#39;équipement utilisateur
US20240323708A1 (en) Network slice quotas in the presence of interworking
US12108284B2 (en) Enhanced PFCP association procedure for session restoration
US12101851B2 (en) Methods, network function nodes and computer readable media for contents communication management
WO2022154718A1 (fr) Systèmes et procédés de récupération de contexte d&#39;ue et de transfert de données pour prendre en charge une transmission de petites données
WO2021201729A1 (fr) Libération ou reprise plus rapide pour un ue dans un état inactif
US20240023182A1 (en) Handling the unknown rrc establishment cause value in nr
EP3869867A1 (fr) Procédé de communication et appareil de communication
US20230156653A1 (en) Network requested registration procedure initiation
CN114642079B (zh) 通信方法及装置
EP4429340A2 (fr) Commande de debit plmn
WO2023170636A1 (fr) Commande de réseau d&#39;utilisation de tranche

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18755197

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18755197

Country of ref document: EP

Kind code of ref document: A1