WO2021162535A1 - Procédé et appareil pour définir un comportement d'équipement utilisateur dans une zone de service limitée - Google Patents

Procédé et appareil pour définir un comportement d'équipement utilisateur dans une zone de service limitée Download PDF

Info

Publication number
WO2021162535A1
WO2021162535A1 PCT/KR2021/001951 KR2021001951W WO2021162535A1 WO 2021162535 A1 WO2021162535 A1 WO 2021162535A1 KR 2021001951 W KR2021001951 W KR 2021001951W WO 2021162535 A1 WO2021162535 A1 WO 2021162535A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
5gmm
message
mode
transmitting
Prior art date
Application number
PCT/KR2021/001951
Other languages
English (en)
Inventor
Mahmoud Watfa
Original Assignee
Samsung Electronics Co., Ltd.
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 Samsung Electronics Co., Ltd. filed Critical Samsung Electronics Co., Ltd.
Priority to KR1020237041646A priority Critical patent/KR20230169454A/ko
Priority to EP21753950.1A priority patent/EP4091360A4/fr
Priority to KR1020227032232A priority patent/KR102611379B1/ko
Priority to CN202180014923.0A priority patent/CN115104328A/zh
Publication of WO2021162535A1 publication Critical patent/WO2021162535A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements
    • H04W4/14—Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/02—Access restriction performed under specific conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/02—Access restriction performed under specific conditions
    • H04W48/04—Access restriction performed under specific conditions based on user or terminal location or mobility data, e.g. moving direction, speed
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/25—Maintenance of established connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • 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
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals

Definitions

  • the disclosure relates to methods, apparatuses, and systems for defining user equipment (UE) behavior in restricted service areas of a network. More particularly, the disclosure relates to methods, apparatuses, and systems for defining Cellular Internet of Things (CIoT) UE behavior in restricted service areas in 3 rd generation partnership project (3GPP) 5 th generation system (5GS).
  • UE user equipment
  • CGI Cellular Internet of Things
  • the 5G or pre-5G communication system is also called a 'Beyond 4G Network' or a 'Post long term evolution (LTE) System'.
  • the 5G communication system is considered to be implemented in higher frequency (mmWave) bands, e.g., 60GHz bands, so as to accomplish higher data rates.
  • mmWave millimeter wave
  • FD-MIMO Full Dimensional MIMO
  • array antenna an analog beam forming, large scale antenna techniques are discussed in 5G communication systems.
  • RANs cloud radio access networks
  • D2D device-to-device
  • SWSC sliding window superposition coding
  • ACM advanced coding modulation
  • FBMC filter bank multi carrier
  • NOMA non-orthogonal multiple access
  • SCMA sparse code multiple access
  • the Internet which is a human centered connectivity network where humans generate and consume information
  • IoT Internet of Things
  • IoE Internet of Everything
  • sensing technology “wired/wireless communication and network infrastructure”, “service interface technology”, and “Security technology”
  • M2M machine-to-machine
  • MTC machine type communication
  • IoT Internet technology services
  • IoT may be applied to a variety of fields including smart home, smart building, smart city, smart car or connected cars, smart grid, health care, smart appliances and advanced medical services through convergence and combination between existing information technology (IT) and various industrial applications.
  • IT information technology
  • technologies such as a sensor network, machine type communication (MTC), and machine-to-machine (M2M) communication may be implemented by beamforming, MIMO, and array antennas.
  • MTC machine type communication
  • M2M machine-to-machine
  • Application of a cloud radio access network (RAN) as the above-described Big Data processing technology may also be considered to be as an example of convergence between the 5G technology and the IoT technology.
  • RAN cloud radio access network
  • Service area restrictions define the rules to restrict access to services and where applicable the exceptions to these rules.
  • services for CIoT 5GS optimization were not considered for service area restrictions.
  • how the UE behaves when CIoT 5GS optimizations are used and when the UE is in a restricted service area was not at all defined.
  • an aspect of the disclosure is to provide an apparatus and method for defining UE behavior when CIoT optimization is being used and the UE is in a restricted service area.
  • Another aspect of the disclosure is to set conditions for transmitting different types of non-access stratum (NAS) messages based on the type of data or service required when the UE is in a restricted service area.
  • NAS non-access stratum
  • a method of a user equipment (UE) in a network wherein the UE is using control plane cellular internet of things (CIoT) 5G system (5GS) optimization and is in a restricted service area is provided.
  • the method includes identifying one or more of a mode of the UE, a type of data required, and a service requested, and setting a UE behavior for initiating a NAS procedure based on the one or more of the mode of the UE, the type of data required, and the service requested.
  • CIoT control plane cellular internet of things
  • a UE using control plane CIoT 5GS optimization and being in a restricted service area including a transceiver, and at least one processor coupled with the transceiver and configured to identify one or more of a mode of the UE, a type of data required, and a service requested, and set a UE behavior for initiating a NAS procedure based on the one or more of the mode of the UE, the type of data required, and the service requested.
  • a network comprising a UE, wherein the UE is using control plane CIoT 5GS optimization and is in a restricted service area.
  • the network including a transceiver, and at least one processor coupled with the transceiver and configured to identify one or more of a mode of the UE, a type of data required, and a service requested, and set a UE behavior for initiating a NAS procedure based on the one or more of the mode of the UE, the type of data required, and the service requested.
  • the UE may operate efficiently in a restricted service area.
  • Figure 1 is a flowchart illustrating setting of a UE behavior for initiating a non-access stratum (NAS) procedure according to an embodiment of the disclosure
  • Figure 2 is a flowchart illustrating setting of a UE behavior for initiating a NAS procedure according to an embodiment of the disclosure
  • Figure 3 is a flowchart illustrating setting of a UE behavior for initiating a NAS procedure according to an embodiment of the disclosure.
  • Figure 4 is a block diagram of a network entity according to an embodiment of the disclosure.
  • X for Y (where Y is some action, process, operation, function, or activity and X is some means for carrying out that action, process, operation, function, or activity) encompasses means X adapted, configured or arranged specifically, but not necessarily exclusively, to do Y.
  • 5GS defines the concept of service area restrictions which determine where, i.e., which tracking areas (TAs) or TA identities (TAIs) the UE can request a service.
  • the service area can either be defined to be of type "allowed tracking areas” or “non-allowed tracking areas”.
  • the UE can request normal service when it is in TAs that are considered to be “allowed tracking areas” or when it is not in TAs that are considered to be “non-allowed tracking areas", and vice versa as described below from section 5.3.5 of TS 24.501 [1]:
  • the service area restrictions consist of tracking areas forming either an allowed area, or a non-allowed area.
  • the tracking areas belong to either the registered Public Land Mobile Network (PLMN) or its equivalent PLMNs in the registration area.
  • PLMN Public Land Mobile Network
  • the allowed area can contain up to 16 tracking areas or include all tracking areas in the registered PLMN and its equivalent PLMN(s) in the registration area.
  • the non-allowed area can contain up to 16 tracking areas.
  • the network conveys the service area restrictions to the UE by including either an allowed area, or a non-allowed area, but not both, in the Service area list IE of a REGISTRATION ACCEPT message or a CONFIGURATION UPDATE COMMAND message.
  • the UE shall treat all tracking areas in the registered PLMN and its equivalent PLMN(s) in the registration area as allowed area and delete the stored list of "allowed tracking areas" or the stored list of "non-allowed tracking areas"
  • the UE shall delete the old list of "allowed tracking areas” and store the tracking areas in the allowed area as the list of "allowed tracking areas". If the UE has a stored list of "non-allowed tracking areas", the UE shall delete that list; or
  • the UE shall treat all tracking areas in the registered PLMN and its equivalent PLMN(s) as allowed area and delete the stored list of "allowed tracking areas" or the stored list of "non-allowed tracking areas”.
  • the UE When the UE receives a Service area list IE with a non-allowed area indication during a registration procedure or a generic UE configuration update procedure, the UE shall delete the old list of "non-allowed tracking areas" and store the tracking areas in the non-allowed area as the list of "non-allowed tracking areas". If the UE has a stored list of "allowed tracking areas", the UE shall delete that list.
  • the UE while camped on a cell whose TAI is in the list of "allowed tracking areas", the UE shall stay or enter the state 5GMM-REGISTERED.NORMAL-SERVICE and is allowed to initiate any 5GMM and 5GSM procedures; and
  • the UE while camped on a cell which is in the registered PLMN or a PLMN from the list of equivalent PLMNs and whose TAI is in the registration area and is not in the list of "allowed tracking areas", the UE shall enter the state 5GMM-REGISTERED.NON-ALLOWED-SERVICE, and:
  • i) shall not perform the registration procedure for mobility and periodic registration update with Uplink data status IE except for emergency services or for high priority access;
  • ii) shall not initiate a service request procedure except for emergency services, high priority access, responding to paging or notification or indicating a change of 3GPP packet switched (PS) data off UE status; and
  • PS packet switched
  • the UE 1) if the UE is in 5GMM-CONNECTED mode or 5GMM-CONNECTED mode with radio resource control (RRC) inactive indication over 3GPP access, the UE:
  • RRC radio resource control
  • i) shall not perform the registration procedure for mobility and periodic registration update with Uplink data status IE except for emergency services or for high priority access;
  • ii) shall not initiate a service request procedure except for emergency services, high priority access or for responding to paging or notification over non-3GPP access;
  • iii) shall not initiate a 5GSM procedure except for emergency services, high priority access or indicating a change of 3GPP PS data off UE status.
  • the UE while camped on a cell which is in the registered PLMN or a PLMN from the list of equivalent PLMNs and whose TAI is not in the list of "non-allowed tracking areas", the UE shall stay or enter the state 5GMM-REGISTERED.NORMAL-SERVICE and is allowed to initiate any 5GMM and 5GSM procedures; and
  • the UE while camped on a cell whose TAI is in the list of "non-allowed tracking areas", the UE shall enter the state 5GMM-REGISTERED.NON-ALLOWED-SERVICE, and:
  • i) shall not perform the registration procedure for mobility and periodic registration update with Uplink data status IE except for emergency services or for high priority access;
  • ii) shall not initiate a service request procedure except for emergency services, high priority access, responding to paging or notification or indicating a change of 3GPP PS data off UE status;
  • the UE 1) if the UE is in 5GMM-CONNECTED mode or 5GMM-CONNECTED mode with RRC inactive indication over 3GPP access, the UE:
  • i) shall not perform the registration procedure for mobility and registration update with the Uplink data status IE except for emergency services or for high priority access;
  • ii) shall not initiate a service request procedure except for emergency services, high priority access or for responding to paging or notification over non-3GPP access;
  • iii) shall not initiate a 5GSM procedure except for emergency services, high priority access or indicating a change of 3GPP PS data off UE status.
  • the tracking area When a tracking area is added to the list of "5GS forbidden tracking areas for roaming" or to the list of "5GS forbidden tracking areas for regional provision of service” as specified in the subclauses 5.5.1.2.5 or 5.5.1.3.5, the tracking area shall be removed from the list of "allowed tracking areas” if the tracking area is already present in the list of "allowed tracking areas” and from the list of "non-allowed tracking areas” if the tracking area is already present in the list of "non-allowed tracking areas”.
  • CIoT small data rate control
  • UE i.e., UE in narrowband (NB)-N1 mode or wideband (WB)-N1 mode
  • Small data rate control also defines the total number of so called exception data that the UE can send in a certain time interval.
  • Exception data is a form of high priority data hence the term "exception data" and is used for exception data reporting.
  • RRC establishment cause is used to differentiate connections that are initiated for exception data reporting for UEs in NB-N1 mode as described in section 5.31.14.3 of TS 23.501 [2].
  • the small data rate control parameters are provided to the UE during protocol data unit (PDU) session establishment in the (extended) protocol configuration options (e)PCO parameter.
  • PDU protocol data unit
  • e extended protocol configuration options
  • the home session management function may consider, e.g., operator policy, subscription, data network name (DNN), single network slice selection assistance information (S-NSSAI), radio access technology (RAT) type or the like, to determine whether to apply Small Data Rate Control or not.
  • the (H-)SMF can send a Small Data Uplink Rate Control command to the UE using the PCO information element.
  • the (H-)SMF informs the user plane function (UPF) or network exposure function (NEF) of any Small Data Rate Control that shall be enforced.
  • UPF user plane function
  • NEF network exposure function
  • the Small Data Uplink Rate Control applies to data PDUs sent on that PDU Session by either Data Radio Bearers or Signaling Radio Bearers (NAS Data PDUs).
  • NAS Data PDUs Signaling Radio Bearers
  • the rate control information is separate for uplink and downlink and in the form of:
  • the UE shall comply with this uplink rate control instruction. If the UE exceeds the uplink 'number of packets per time unit', the UE may still send uplink exception reports if allowed and the 'number of additional allowed exception reports per time unit' has not been exceeded. The UE shall consider this rate control instruction as valid until it receives a new one from (H-)SMF.
  • the (H-)SMF may provide the configured Small Data Rate Control parameters to the UE and UPF or NEF.
  • the Small Data Rate Control Status (including the number of packets still allowed in the given time unit, the number of additional exception reports still allowed in the given time unit and the termination time of the current Small Data Rate Control validity period) may be stored in the access and mobility management function (AMF) so that it can be retrieved for a subsequent re-establishment of a new PDU Session.
  • AMF access and mobility management function
  • the (H-)SMF may receive the previously stored Small Data Rate Control Status and if the validity period has not expired, it provides the parameters to the UE in the PCO and to the UPF/NEF as the initially applied parameters, in addition to the configured Small Data Rate Control parameters. If the initially applied parameters are provided, the UE and UPF or NEF use the configured Small Data Rate Control parameters once the initially applied Small Data Rate Control validity period expires.
  • Small Data rate control is based on a 'maximum allowed rate' per direction. If (H-)SMF provided the 'number of additional allowed exception report packets per time unit' to the UE, then the 'maximum allowed rate' is equal to the 'number of packets per time unit' plus the 'number of additional allowed exception report packets per time unit'. Otherwise, the 'maximum allowed rate' is equal to the 'number of packets per time unit'.
  • the UPF or NEF may enforce the uplink rate by discarding or delaying packets that exceed the 'maximum allowed rate'.
  • the UPF or NEF shall enforce the downlink rate by discarding or delaying packets that exceed the downlink part of the 'maximum allowed rate'.
  • the AMF maintains an "MO Exception Data Counter” which is incremented when RRC establishment cause "MO exception data” is received from 5G RAN (NG-RAN).
  • the AMF reports the "MO Exception Data Counter” to all (H-)SMFs which have PDU Sessions that are subject to Small Data Rate Control and informs the SMF when UE is accessing with "MO exception data” RRC establishment cause.
  • each (H-)SMF reports the "MO Exception Data Counter” to each UPF and NEF for each PDU Session to which Small Data Rate Control applies.
  • each NEF and UPF After receiving the "MO Exception Data Counter", each NEF and UPF consider PDUs transferred during an RRC Connection established for "MO Exception data” to be exception data for Small Data Rate Control purposes.
  • the UPF indicates each use of the RRC establishment cause "MO Exception Data” by the related counter on its charging data record (CDR).
  • the UE and the user plane component of PGW (PGW-U)+UPF store the current Small Data Rate Control Status for all PDU Sessions that are not released. If the UE moves back to 5G Core (5GC) the stored Small Data Rate Control Status is restored and continues to apply to PDU Session(s) that are moved from EPC to 5GC, taking into account remaining validity period of the stored Small Data Rate Control Status.
  • EPC evolved packet core
  • PGW-U user plane component of PGW
  • 5GC 5G Core
  • the Small Data Rate Control Status for all PDU Session(s) may also be stored in the AMF if the PDU Session is released while the UE is connected to EPC and re-established when the UE moves to 5GC.
  • the time to store the Small Data Rate Control Status information is implementation specific.
  • small data rate control applies to both CIoT data that is sent over the user plane or the control plane as stated in the quoted text above.
  • Certain examples of the disclosure provide methods, apparatus and systems for defining UE behavior in restricted service areas of a network.
  • certain examples of the disclosure provide methods, apparatus and systems for defining CIoT UE behavior in restricted service areas in 3GPP 5GS.
  • the disclosure is not limited to these examples, and may be applied in any suitable system or standard, for example one or more existing and/or future generation wireless communication systems or standards.
  • 3GPP 5G 3rd Generation Partnership Project 5G
  • the techniques disclosed herein are not limited to 3GPP 5G.
  • the functionality of the various network entities and messages disclosed herein may be applied to corresponding or equivalent entities and messages in other communication systems or standards.
  • Corresponding or equivalent entities and messages may be regarded as entities and messages that perform the same or similar role within the network.
  • the transmission of information between network entities is not limited to the specific form, type or order of messages described in relation to the examples disclosed herein.
  • a particular network entity may be implemented as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, and/or as a virtualized function instantiated on an appropriate platform, e.g., on a cloud infrastructure.
  • One or more of the messages in the examples disclosed herein may be replaced with one or more alternative messages, signals or other type of information carriers that communicate equivalent or corresponding information.
  • One or more non-essential elements or entities may be omitted in certain examples.
  • ⁇ Information carried by a particular message in one example may be carried by two or more separate messages in an alternative example.
  • ⁇ Information carried by two or more separate messages in one example may be carried by a single message in an alternative example.
  • Certain examples of the disclosure may be provided in the form of an apparatus/device/network entity configured to perform one or more defined network functions and/or a method therefor. Certain examples of the disclosure may be provided in the form of a system comprising one or more such apparatuses/devices/network entities, and/or a method therefor.
  • a UE will use the uplink (UL) NAS TRANSPORT message to send data over NAS (referred to as CIoT user data) when the UE is in 5GMM-CONNECTED mode.
  • CIoT user data data over NAS
  • the UE is not allowed to send data unless it is for emergency services, or if the UE is a high priority access UE.
  • the UE's behavior when using CIoT 5GS optimization should be defined for the cases when the UE is in restricted service areas.
  • Certain examples of the disclosure address the above problems. For example, certain examples of the disclosure define UE behavior when CIoT optimization is being used and the UE is in a restricted service area. Certain examples of the disclosure set conditions for sending different types of NAS messages based on the type of data or service required when the UE is in a restricted service area.
  • Certain examples of the disclosure provide a method, for a UE in a network, wherein the UE is using control plane CIoT 5GS optimization and is in a restricted service area, the method comprising: determining one or more of a mode of the UE, a type of data required, and a service requested; and setting a UE behavior for initiating a NAS procedure based on one or more of the mode of the UE, the type of data required, and the service requested.
  • the UE behavior may comprise one or more of: an allowed behavior; a prohibited behavior; and a required behavior.
  • the UE behavior comprises UE behavior according to one or more of the examples disclosed herein.
  • Certain examples of the disclosure provide a UE configured to operate according to a method according to any of the examples disclosed herein.
  • setting the behavior may comprise:
  • the UE shall not request lower layers to resume a suspended connection
  • the one or more predefined types of operation may comprise sending an UL NAS TRANSPORT message comprising one or more predefined types of data.
  • the one or more predefined types of operation may comprise one or more of an SMS and a sending a location service message.
  • the one or more predefined types of operation may comprise one or more of responding to notification received (e.g., over non-3GPP access); sending an SOR transport container; sending a UE policy container; and sending a UE parameters update transport container.
  • setting the behavior may comprise:
  • the UE is in 5GMM-CONNECTED mode or 5GMM-CONNECTED mode with RRC inactive indication (e.g., over 3GPP access),
  • the UE shall not perform a NAS transport procedure
  • the data may comprise one or more of an SMS, an LPP message, a location services message, an SOR transport container, a UE policy container, a UE parameters update transport container, and a CIoT user data container.
  • setting the behavior may comprise:
  • the UE shall not request lower layers to resume a suspended connection
  • the one or more predefined types of operation may comprise one or more of: emergency services, high priority access, and responding to paging or responding to notification received (e.g., over non-3GPP access).
  • setting the behavior may comprise:
  • the UE should not send an UL NAS TRANSPORT with the Payload type set to "CIoT user data container"
  • setting the behavior may comprise:
  • the UE can send an UL NAS TRANSPORT message with the Payload type set to "CIoT user data container"
  • setting the behavior may comprise:
  • the UE should send the UL NAS TRANSPORT message with the Payload type set to "CIoT user data container"
  • setting the behavior may comprise:
  • the UE can send the UL NAS TRANSPORT message with the Payload type set to "CIoT user data container"
  • setting the behavior may comprise:
  • the UE should send a PDU Session Establishment Request message in the UL NAS TRANSPORT message.
  • the UE should (be allowed to) send a PDU Session Release Request message in the UL NAS TRANSPORT message to release a PDU session in order to establish another PDU session for exception data reporting.
  • setting the behavior may comprise:
  • the UE is not allowed to initiate a service request procedure
  • setting the behavior may comprise:
  • the UE is not allowed to initiate a service request procedure
  • setting the behavior may comprise:
  • the UE should not request the lower layers to resume the connection
  • Certain examples of the disclosure provide a network comprising a UE according to any of the examples disclosed herein.
  • Certain examples of the disclosure provide a computer program comprising instructions which, when the program is executed by a computer or processor, cause the computer or processor to carry out a method according to any of the examples disclosed herein.
  • Certain examples of the disclosure provide a computer or processor-readable data carrier having stored thereon a computer program according to any of the examples disclosed herein.
  • This section proposes the UE behavior when the UE is using CIoT optimizations and is in a restricted service area.
  • restricted service area can mean that the UE is in a TA that is set to "non-allowed tracking area” in the Service area list IE, or the UE is not in a TA that is set to be “allowed tracking area” in the Service area list IE.
  • the UE behavior should be as follows:
  • the default behavior should be that the UE, which is using control plane CIoT 5GS optimization, that is in 5GMM-CONNECTED mode, or in 5GMM-CONNECTED mode with RRC inactive indication should not send an UL NAS TRANSPORT with the Payload type set to "CIoT user data container". However, the if the UE receives a DL NAS TRANSPORT message with the Payload type set to "CIoT user data container", the UE is allowed to send an UL NAS TRANSPORT message with the Payload type set to "CIoT user data container".
  • the UE can send an UL NAS TRANSPORT message with the Payload type set to "CIoT user data container"
  • the UE should send the UL NAS TRANSPORT message with the Payload type set to "CIoT user data container" even if the UE is in a restricted service area.
  • the UE can send the UL NAS TRANSPORT message with the Payload type set to "CIoT user data container” if the RRC connection was established with the RRC establishment cause set to mo-ExceptionData.
  • the UE should, even if the UE is in a restricted service area, send the PDU Session Establishment Request message in the UL NAS TRANSPORT message. If the maximum number of active user-plane resources is reached and the upper layers of the UE request user-plane resources for exception data reporting, the UE should (be allowed to) send a PDU Session Release Request message in the UL NAS TRANSPORT message to release a PDU session in order to establish another PDU session for exception data reporting.
  • the UE is not allowed to initiate the service request procedure, or registration procedure for mobility and periodic registration update with Uplink data status IE, except if the UE needs to establish a PDU session for exception data reporting, or to request user-plane resource establishment for sending data for exception data reporting, or to send exception data reporting using the Control Plane Service Request message.
  • the UE is not allowed to initiate the service request procedure, or a registration procedure for mobility and periodic registration update with Uplink data status IE, except if the UE needs to request user-plane resource establishment for sending data for exception data reporting.
  • the UE should not request the lower layers to resume the connection except if the UE needs to send exception data for exception data reporting, or if the UE needs to send a PDU Session Establishment Request message for sending exception data for exception data reporting, or if the UE needs to release a PDU session (after the maximum number of active user-plane resources is reached and the upper layers of the UE request user-plane resources for exception data reporting) in order to establish another PDU session for exception data reporting.
  • the UE behavior for initiating NAS procedures when CIoT 5GS optimization is being used and the UE is in a restricted area is not defined thereby leaving the UE behavior unpredictable and possible incompatible with the network expectation.
  • the present application proposes standardized UE behavior for the identified scenario such that a CIoT device can predictably operate when it is in a restricted service area.
  • Figure 1 illustrates a flowchart illustrating setting of a UE behavior for initiating a NAS procedure according to an embodiment of the disclosure.
  • Figure 1 illustrates a technique for determining whether to send data for a UE capable of operating in a certain mode (e.g., using control plane CIoT 5GS optimization).
  • the UE determines if it is operating in a certain mode. For example, the UE may determine if it is using control plane CIoT 5GS optimization. If the UE is using control plane CIoT 5GS optimization, the flow proceeds to a next operation 102, otherwise the UE operates according to another mode.
  • the UE receives a request to send data over the control plane.
  • the request may come from upper layers and/or the data may be CIoT user data.
  • the UE performs a first check. For example, the UE may check if it is in a restricted service area. In certain examples, the UE may check if it is in a non-allowed area and/or if it is outside of an allowed area. The UE may decide whether or not to send the data based on a result of the first check. For example, if the UE is not in a restricted service area then the UE sends the data. On the other hand, if the UE is in a restricted service area then the flow proceeds to a next operation 104.
  • the UE performs a second check. For example, the UE may check if it is in a certain mode. In certain examples, the UE may check if it is in 5GMM-CONNECTED mode or in 5GMM-CONNECTED mode with RRC inactive indication. The UE may decide whether or not to send the data based on a result of the second check. For example, if the UE is in 5GMM-CONNECTED mode or in 5GMM-CONNECTED mode with RRC inactive indication then the UE sends the data, otherwise the UE does not send the data.
  • Figure 1 may be performed in a different order in alternative examples.
  • the second check may be performed by the first check to achieve the same overall UE behavior in dependence on the results of the first and second checks.
  • Figure 2 illustrates a flowchart illustrating setting of a UE behavior for initiating a NAS procedure according to an embodiment of the disclosure.
  • Figure 2 illustrates a technique for determining whether to send a NAS message for a UE capable of operating in a certain mode (e.g., using control plane CIoT 5GS optimization).
  • the UE determines if it is operating in a certain mode. For example, the UE may determine if it is using control plane CIoT 5GS optimization. If the UE is using control plane CIoT 5GS optimization, the flow proceeds to a next operation 202, otherwise the UE operates according to another mode.
  • the UE receives a request to send a NAS message.
  • the request may come from upper layers.
  • the UE performs a first check. For example, the UE may check if it is in a restricted service area. In certain examples, the UE may check if it is in a non-allowed area and/or if it is outside of an allowed area. The UE may decide whether or not to send the NAS message based on a result of the first check. For example, if the UE is not in a restricted service area then the UE sends the NAS message. On the other hand, if the UE is in a restricted service area then the flow proceeds to a next operation 204.
  • the UE performs a second check. For example, the UE may check if it is in a certain mode. In certain examples, the UE may check if it is in 5GMM-CONNECTED mode or in 5GMM-CONNECTED mode with RRC inactive indication. The UE may decide whether or not to send the NAS message based on a result of the second check. For example, if the UE is not in 5GMM-CONNECTED mode or not in 5GMM-CONNECTED mode with RRC inactive indication then the UE does not send the NAS message, otherwise the flow proceeds to a next operation 205.
  • a further check may be applied, for example based on the type of data or content of the NAS message, to determine whether or not to send the NAS message. For example, if the UE is not in 5GMM-CONNECTED mode or not in 5GMM-CONNECTED mode with RRC inactive indication then the UE does not send the NAS message unless the data or content of the NAS message is of a certain type, for example SMS or LPP.
  • the UE performs a third check. For example, the UE may check if the request is for sending data over control plane (e.g., CIoT user data) or a location services message. The UE may decide whether or not to send the NAS message based on a result of the third check. For example, if the request is for sending data over control plane (e.g., CIoT user data) or a location services message then the UE sends the NAS message, otherwise the UE does not send the NAS message.
  • control plane e.g., CIoT user data
  • a location services message e.g., a location services message
  • a further check may be applied, for example based on the type of data or content of the NAS message, to determine whether or not to send the NAS message. For example, if the request is for sending neither data over control plane nor a location services message then the UE does not send the NAS message unless the data or content of the NAS message is of a certain type, for example SMS or LPP.
  • Figure 2 may be performed in a different order in alternative examples.
  • the first to third checks may be performed in an alternative order to achieve the same overall UE behavior in dependence on the results of the first to third checks.
  • Figure 3 illustrates a flowchart illustrating setting of a UE behavior for initiating a NAS procedure according to an embodiment of the disclosure.
  • Figure 3 illustrates a technique for determining whether to send data and/or resume a connection for a UE capable of operating in a certain mode (e.g., using user plane CIoT 5GS optimization).
  • the UE determines if it is operating in a certain mode. For example, the UE may determine if it is using user plane CIoT 5GS optimization. If the UE is using user plane CIoT 5GS optimization, the flow proceeds to a next operation 302, otherwise the UE operates according to another mode.
  • the UE receives a request to send data.
  • the request may come from upper layers.
  • the UE performs a first check. For example, the UE may check if it is in a restricted service area. In certain examples, the UE may check if it is in a non-allowed area and/or if it is outside of an allowed area. The UE may decide whether or not to request the lower layers to resume the RRC connection and/or whether or not to send data based on a result of the first check. For example, if the UE is not in a restricted service area then the UE requests the lower layers to resume the RRC connection and/or sends the data. On the other hand, if the UE is in a restricted service area then the flow proceeds to a next operation 304.
  • the UE performs a second check. For example, the UE may check if it is in a certain mode. In certain examples, the UE may check if it is in 5GMM-IDLE mode with suspend indication. The UE may decide whether or not to request the lower layers to resume the RRC connection and/or whether or not to send the data based on a result of the second check. For example, if the UE is not in 5GMM-IDLE mode with suspend indication then the UE sends the data if the UE has sufficient radio resources, and/or the UE requests the lower layers to resume the RRC connection (to send the data), otherwise the flow proceeds to a next operation 305.
  • the UE performs a third check. For example, the UE may check if the request is for sending exception data or other data. The UE may decide whether or not to request lower layers to resume a suspended connection and send the data based on a result of the third check. For example, if the request is for sending exception data then the UE requests lower layers to resume the suspended connection and sends the data. On the other hand, if the request is for sending other data then the UE does not request lower layers to resume the suspended connection and does not send the data.
  • Figure 3 may be performed in a different order in alternative examples.
  • the first to third checks may be performed in an alternative order to achieve the same overall UE behavior in dependence on the results of the first to third checks.
  • a request to send data is one example of an operation in which a NAS procedure may need to be initiated.
  • a request to send data may result in the sending of a NAS message by initiating a NAS transport procedure in which the UE sends the UL NAS TRANSPORT message.
  • Figure 4 is a block diagram of a network entity according to an embodiment of the disclosure.
  • a network entity may be implemented, for example, as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, and/or as a virtualized function instantiated on an appropriate platform, e.g., on a cloud infrastructure.
  • an entity or UE 400 comprises a processor (or controller) 401, a transmitter 403 and a receiver 405.
  • the receiver 105 is configured for receiving one or more messages from one or more other network entities, for example as described above.
  • the transmitter 403 is configured for transmitting one or more messages to one or more other network entities, for example as described above.
  • the processor 401 is configured for performing one or more operations, for example according to the operations as described above.
  • Such an apparatus and/or system may be configured to perform a method according to any aspect, embodiment, example or claim disclosed herein.
  • Such an apparatus may comprise one or more elements, for example one or more of receivers, transmitters, transceivers, processors, controllers, modules, units, and the like, each element configured to perform one or more corresponding processes, operations and/or method operations for implementing the techniques described herein.
  • an operation/function of X may be performed by a module configured to perform X (or an X-module).
  • the one or more elements may be implemented in the form of hardware, software, or any combination of hardware and software.
  • examples of the disclosure may be implemented in the form of hardware, software or any combination of hardware and software. Any such software may be stored in the form of volatile or non-volatile storage, for example a storage device like a read only memory (ROM), whether erasable or rewritable or not, or in the form of memory, such as, for example, RAM, memory chips, device or integrated circuits or on an optically or magnetically readable medium, such as, for example, a compact disc (CD), digital versatile disc (DVD), magnetic disk or magnetic tape or the like.
  • ROM read only memory
  • the storage devices and storage media are embodiments of machine-readable storage that are suitable for storing a program or programs comprising instructions that, when executed, implement certain examples of the disclosure. Accordingly, certain example provides a program comprising code for implementing a method, apparatus or system according to any example, embodiment, aspect and/or claim disclosed herein, and/or a machine-readable storage storing such a program. Still further, such programs may be conveyed electronically via any medium, for example a communication signal carried over a wired or wireless connection.

Landscapes

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

Abstract

La présente invention se rapporte à un procédé et à un système de communication permettant de fusionner un système de communication de 5ème génération (5G) avec une technologie associée à l'Internet des objets (IdO) pour qu'il prenne en charge des débits de données supérieurs à ceux d'un système de 4ème génération (4G). La présente invention peut être appliquée à des services intelligents basés sur la technologie de communication 5G et sur la technologie liée à IdO, tels que la maison intelligente, le bâtiment intelligent, la ville intelligente, la voiture intelligente, la voiture connectée, les soins de santé, l'enseignement numérique, le commerce de détail intelligent, les services liés à la sûreté et à la sécurité. La présente invention concerne un procédé pour un équipement d'utilisateur (UE) dans un réseau. L'UE utilise une optimisation de plan de commande CIoT 5GS et se trouve dans une zone de service limitée. Le procédé comprend la détermination d'un ou de plusieurs éléments parmi le mode de l'UE, le type de données requises et le service demandé, et l'établissement d'un comportement de l'UE pour initier une procédure NAS sur la base d'un ou de plusieurs éléments parmi le mode de l'UE, le type de données requises et le service demandé.
PCT/KR2021/001951 2020-02-16 2021-02-16 Procédé et appareil pour définir un comportement d'équipement utilisateur dans une zone de service limitée WO2021162535A1 (fr)

Priority Applications (4)

Application Number Priority Date Filing Date Title
KR1020237041646A KR20230169454A (ko) 2020-02-16 2021-02-16 제한된 서비스 영역에서 ue 작동을 정의하는 방법 및 장치
EP21753950.1A EP4091360A4 (fr) 2020-02-16 2021-02-16 Procédé et appareil pour définir un comportement d'équipement utilisateur dans une zone de service limitée
KR1020227032232A KR102611379B1 (ko) 2020-02-16 2021-02-16 제한된 서비스 영역에서 ue 작동을 정의하는 방법 및 장치
CN202180014923.0A CN115104328A (zh) 2020-02-16 2021-02-16 用于定义受限服务区域中的ue行为的方法和装置

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
GB2002111.9 2020-02-16
GB2002111.9A GB2592065A (en) 2020-02-16 2020-02-16 UE in restricted service area
GB2100749.7A GB2593039B (en) 2020-02-16 2021-01-20 UE in restricted service area
GB2100749.7 2021-01-20

Publications (1)

Publication Number Publication Date
WO2021162535A1 true WO2021162535A1 (fr) 2021-08-19

Family

ID=69956572

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2021/001951 WO2021162535A1 (fr) 2020-02-16 2021-02-16 Procédé et appareil pour définir un comportement d'équipement utilisateur dans une zone de service limitée

Country Status (6)

Country Link
US (3) US11558807B2 (fr)
EP (1) EP4091360A4 (fr)
KR (2) KR102611379B1 (fr)
CN (1) CN115104328A (fr)
GB (2) GB2592065A (fr)
WO (1) WO2021162535A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2621931A (en) * 2022-08-10 2024-02-28 Samsung Electronics Co Ltd Methods for handling NAS Messages for UEs using Satellite Access from a Non-allowed Location

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023132603A1 (fr) * 2022-01-06 2023-07-13 Samsung Electronics Co., Ltd. Réseau sans fil et procédé pour gérer une zone nssai rejetée dans un réseau sans fil

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017170123A1 (fr) * 2016-04-01 2017-10-05 Nec Corporation Contrôle de charge à partir d'une optimisation eps ciot sur le plan de commande
WO2018226072A2 (fr) * 2017-06-08 2018-12-13 엘지전자(주) Procédé de contrôle de surcharge dans un système de communications sans fil, et dispositif associé

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7860025B2 (en) * 2005-06-28 2010-12-28 Cisco Technology, Inc. Directed acyclic graph discovery and network prefix information distribution relative to a clusterhead in an ad hoc mobile network
US7693064B2 (en) * 2005-10-24 2010-04-06 Cisco Technology, Inc. Forwarding packets to a directed acyclic graph destination using link selection based on received link metrics
US7978632B2 (en) * 2008-05-13 2011-07-12 Nortel Networks Limited Wireless mesh network transit link topology optimization method and system
WO2017172912A1 (fr) * 2016-03-29 2017-10-05 Alcatel-Lucent Usa Inc. Procédé et appareil de transfert de données de dispositif de l'internet des objets cellulaire (ciot)
US11116006B2 (en) * 2016-12-16 2021-09-07 Qualcomm Incorporated Uplink transmission parameter selection for random access initial message transmission and retransmission
US11528749B2 (en) * 2017-06-08 2022-12-13 Qualcomm Incorporated Techniques and apparatuses for random access procedure in a wireless backhaul network
US10932270B2 (en) * 2017-06-15 2021-02-23 Qualcomm Incorporated Techniques and apparatuses for user equipment-requested beam pair link procedure
EP3547770B1 (fr) * 2017-09-14 2021-12-01 LG Electronics Inc. Procédé pour exécuter une communication v2x dans un système de communication sans fil, et appareil associé
US11190989B2 (en) * 2018-05-22 2021-11-30 Apple Inc. Mobility management for inter-gNB (next generation node-b) handover in new radio (NR) systems
US10986527B2 (en) * 2018-06-22 2021-04-20 Sharp Laboratories Of America, Inc. Method and apparatus for indicating restricted resources of wireless terminal and for indicating access node capability to support connection with a wireless terminal with restricted capabilities
US11503662B2 (en) * 2019-06-14 2022-11-15 Samsung Electronics Co., Ltd. Method and system for handling of closed access group related procedure
US11490447B2 (en) * 2020-04-28 2022-11-01 Apple Inc. Intelligent 5G NR RRC state transitions

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017170123A1 (fr) * 2016-04-01 2017-10-05 Nec Corporation Contrôle de charge à partir d'une optimisation eps ciot sur le plan de commande
WO2018226072A2 (fr) * 2017-06-08 2018-12-13 엘지전자(주) Procédé de contrôle de surcharge dans un système de communications sans fil, et dispositif associé

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 (Release 16)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 24.501, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. CT WG1, no. V16.3.0, 20 December 2019 (2019-12-20), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, pages 1 - 645, XP051840838 *
"3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (SGS); Stage 3 (Release 16", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 24.501, 20 December 2019 (2019-12-20)
BLACKBERRY UK LTD.: "Correct EPS SRVCC support indication when registering with 5GS", 3GPP DRAFT; C1AH-200012, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. CT WG1, no. 20200116 - 20200122, 11 January 2020 (2020-01-11), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051843172 *
ERICSSON: "Clarification and abnormal case for NAS message container IE contents", 3GPP DRAFT; C1AH-200102, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. CT WG1, no. 20200116 - 20200122, 13 January 2020 (2020-01-13), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051843435 *
See also references of EP4091360A4

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2621931A (en) * 2022-08-10 2024-02-28 Samsung Electronics Co Ltd Methods for handling NAS Messages for UEs using Satellite Access from a Non-allowed Location

Also Published As

Publication number Publication date
US20230142334A1 (en) 2023-05-11
EP4091360A1 (fr) 2022-11-23
KR20230169454A (ko) 2023-12-15
GB2592065A (en) 2021-08-18
GB202100749D0 (en) 2021-03-03
KR102611379B1 (ko) 2023-12-08
US11844011B2 (en) 2023-12-12
US20210258859A1 (en) 2021-08-19
GB2593039B (en) 2023-07-19
GB2593039A (en) 2021-09-15
KR20220143727A (ko) 2022-10-25
EP4091360A4 (fr) 2023-07-19
GB202002111D0 (en) 2020-04-01
CN115104328A (zh) 2022-09-23
US20240049111A1 (en) 2024-02-08
US11558807B2 (en) 2023-01-17

Similar Documents

Publication Publication Date Title
WO2020209620A1 (fr) Procédé et ue de gestion de procédure de radiomessagerie dans un réseau de communication sans fil
WO2021091285A1 (fr) Procédé et appareil pour commander une tranche de réseau dans un système de communication sans fil
WO2021066562A1 (fr) Procédé et système permettant de fournir une cause de radiomessagerie à un équipement utilisateur musim
WO2019074347A1 (fr) Équipement d'utilisateur (ue) et réseau central permettant de gérer une congestion de tranche de réseau dans un système de communication sans fil
WO2018164498A1 (fr) Procédé pour maintenir un équipement d'utilisateur en mode connexion initiée par mobile uniquement dans un mode connecté
WO2020204530A1 (fr) Appareil et procédé de prise en charge d'un service de communication biunivoque dans un système de communication sans fil
EP3935897A1 (fr) Procédé et système d'ue permettant de commuter entre une pluralité de réseaux sim
WO2019031874A1 (fr) Procédé et système de traitement de gestion d'enregistrement et de session dans un système de communication sans fil
WO2020071704A1 (fr) Procédé et dispositif pour fournir des informations pour des services de communication de véhicule
WO2017007193A1 (fr) Procédé et appareil pour un accès à un réseau dans un système de communication sans fil prenant en charge une opération de réseau d'accès radio terrestre de système universel de télécommunication mobile e-utran isolée pour la sécurité publique
WO2019194538A1 (fr) Procédé et appareil pour la fourniture d'un service de notification d'événement de mobilité de terminal dans un système de communications sans fil
WO2020251240A1 (fr) Procédé et appareil pour améliorer la fiabilité de service dans un système de communications sans fil
WO2021162535A1 (fr) Procédé et appareil pour définir un comportement d'équipement utilisateur dans une zone de service limitée
WO2022060147A1 (fr) Procédé et appareil destinés à des opération multi-usim
WO2021162395A1 (fr) Procédé et appareil de sécurité de réseau
WO2021137624A1 (fr) Procédé et appareil pour s'enregistrer avec une tranche de réseau dans un système de communication sans fil
WO2021201648A1 (fr) Procédé et appareil de gestion de procédure liée à un cag dans un réseau de communication sans fil
WO2021034105A1 (fr) Procédé et appareil pour fournir un service d'abonnement multiple dans un système de communication sans fil
WO2021206295A1 (fr) Procédé et appareil pour fournir un service d'urgence dans un réseau
WO2021020834A1 (fr) Procédé d'accès à un réseau par un terminal
WO2017171296A1 (fr) Procédé et équipement pour commander un ciot pour un ue
WO2021153982A1 (fr) Procédé et appareil pour aviser de changements d'utilisation d'amélioration de couverture dans un réseau
WO2021154040A1 (fr) Procédé et appareil de rétablissement à partir d'un redémarrage après défaillance pour un dispositif de l'internet des objets cellulaire
WO2022071783A1 (fr) Améliorations apportées ou relatives à la gestion de sessions pdu dans un système de télécommunication
WO2021242076A1 (fr) Procédé et dispositif de transmission et de réception de données dans un système de communication sans fil

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021753950

Country of ref document: EP

Effective date: 20220815

ENP Entry into the national phase

Ref document number: 20227032232

Country of ref document: KR

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE