WO2019216522A1

WO2019216522A1 - Method for supporting and providing ladn service in wireless communication system, and apparatus therefor

Info

Publication number: WO2019216522A1
Application number: PCT/KR2019/001296
Authority: WO
Inventors: 김현숙; 김래영; 류진숙; 윤명준
Original assignee: 엘지전자 주식회사
Priority date: 2018-05-11
Filing date: 2019-01-30
Publication date: 2019-11-14

Abstract

One aspect of the present invention comprises the steps of: displaying a configuration picture for configuring whether access by a terminal to an LADN service is permitted; receiving, through the configuration picture, the input of a configuration related to whether access to the LADN service is permitted and storing the inputted configuration; receiving LADN information for the LADN service; and determining, on the basis of the stored configuration and/or position information of the terminal, whether to establish a PDU session for providing the LADN service, and can further comprise, when the establishment of the PDU session is determined, the steps of: receiving, from an AMF, a preset message including a request for the establishment of the PDU session; and transmitting, to a network node, a request message for initiating the establishment of the PDU session.

Description

LADN service support and provision method in wireless communication system and apparatus therefor

The present invention relates to a wireless communication system, and more particularly, to a method and apparatus for supporting and providing a LADN service.

Mobile communication systems have been developed to provide voice services while ensuring user activity. However, the mobile communication system has expanded not only voice but also data service.As a result of the explosive increase in traffic, a shortage of resources and users are demanding higher speed services, a more advanced mobile communication system is required. have.

The requirements of the next generation of mobile communication systems will be able to accommodate the explosive data traffic, dramatically increase the data rate per user, greatly increase the number of connected devices, very low end-to-end latency, and high energy efficiency. It should be possible. Dual connectivity, Massive Multiple Input Multiple Output (MIMO), In-band Full Duplex, Non-Orthogonal Multiple Access (NOMA), Super Various technologies such as wideband support and device networking have been studied.

In particular, recently, various devices for reducing power consumption have been actively studied for devices in which power consumption greatly affects the life of the device.

An object of the present invention is to propose a method for efficiently supporting and providing a LADN service of a terminal.

Another object of the present invention is to propose a method for efficiently supporting and indicating a LADN PDU session establishment for a LADN service of a UE.

In addition, according to the related art, the PDU session establishment for receiving the LADN service may be triggered / started / started from the UE, but it is not known when the UE establishes the PDU session in detail. That is, even though the network is ready to provide LADN service, utilization of LADN service usage is not available because the UE is not forced to establish a PDU session (and / or when it is specifically defined when to initiate). Can be low.

In addition, an object of the present invention is to provide a variety of UX / UI so that the user can properly receive and effectively control the LADN service of the terminal.

An embodiment of a method and apparatus for solving the above technical problem is proposed. The technical problems to be achieved in the present invention are not limited to the technical problems mentioned above, and other technical problems not mentioned above will be clearly understood by those skilled in the art from the following description. Could be.

According to an aspect of the present invention, a method of receiving a local access data network (LADN) service of a terminal in a wireless communication system, the method comprising: displaying a setting screen for setting whether the terminal is allowed to access the LADN service; Receiving a setting regarding whether to allow access to the LADN service through the setting screen, and storing the input setting; Receiving LADN information for the LADN service, wherein the LADN information includes LADN service area information and LADN data network name (DNN) information; And determining whether to establish a packet data unit (PDU) session for providing the LADN service based on the stored configuration and / or location information of the terminal. If it is determined that the establishment of the PDU session is determined: Receiving a predetermined message from the Access and Mobility Management Function (AMF) including a request for establishing the PDU session; And sending a request message to a network node to initiate establishment of the PDU session. It may further include.

In addition, when the establishment of the PDU session is determined, the stored setting indicates the access permission to the LADN service, and / or the location of the terminal is inside a LADN service area included in the LADN service area information. It may be the case.

In addition, the network node may be the AMF, PCF (Policy Control function), Network Exposure Function (NEF) and / or Data Network (DN) / Application Function (AF).

The receiving of the preset message may include: receiving, via the AMF, an application trigger request message for triggering the LADN service from the DN / AF as the preset message; It may include.

The receiving of the preset message may include: when the AMF receives a LADN PDU initiation message requesting initiation of the PDU session establishment from the PCF, a paging message as the preset message from the AMF. Receiving; It may include.

In the receiving of the preset message, the AMF receives an initiation message requesting the PDU session establishment initiation from the PCF, wherein the initiation message includes priority information of the PDU session establishment. Receiving a non-access stratum (NAS) message including the priority information as the predetermined message from the AMF, if any; It may include.

The LADN service receiving method may further include an indicator indicating that the terminal is currently accessing the LADN service when the PDU session for the LADN service is successfully established as the request message is approved by the network node. Displaying; It may further include.

In addition, the indicator may correspond to an icon, a notification window, a message, and / or a pop-up window of a predefined state, color, and / or shape to indicate that the LADN service is being accessed.

In addition, the indicator may be displayed in the status bar to inform the user of the current setting status of the terminal.

In addition, the LADN service receiving method, if the establishment of the PDU session is not determined and / or the request message is rejected by the network node, the establishment of the PDU session for the LADN service failed, the LADN Displaying a notification window informing that the connection of the service has failed; It may further include.

In addition, another aspect of the present invention is a terminal for receiving a Local Access Data Network (LADN) service in a wireless communication system, comprising: a communication module for transmitting and receiving a signal; A display unit for displaying a screen; A memory for storing data; A processor controlling the communication module, the display unit, and the memory; The processor may include: a setting screen for receiving the setting of whether the terminal permits access to the LADN service on the display unit, and setting a setting regarding whether to allow access to the LADN service through the setting screen. Receive the input, store the input setting in the memory, and receive LADN information for the LADN service, wherein the LADN information includes LADN service area information and LADN data network name (DNN) information; And / or determine whether to establish a packet data unit (PDU) session for providing the LADN service based on the location information of the terminal, and if establishment of the PDU session is determined: requesting the establishment of the PDU session A request message for receiving a predetermined message from an access and mobility management function (AMF), and initiating establishment of the PDU session. It can be transferred if a network node.

In addition, when receiving the predetermined message, the processor may receive an application trigger request message for triggering the LADN service from the DN / AF through the AMF as the predetermined message.

Further, when the AMF receives the preset message, the AMF receives a LADN PDU initiation message requesting the initiation of the PDU session establishment from the PCF as the predetermined message from the AMF. A paging message can be received.

In addition, when the processor receives the predetermined message, the AMF receives an initiation message requesting the PDU session establishment initiation from the PCF, wherein the initiation message is priority information of the PDU session establishment. In the case of including a, a non-access stratum (NAS) message including the priority information may be received from the AMF as the predetermined message.

In addition, when the PDU session for the LADN service is successfully established as the request message is approved by the network node, the processor may display an indicator indicating that the terminal is currently accessing the LADN service. Can be displayed on.

In addition, if the establishment of the PDU session is not determined and / or the establishment of the PDU session for the LADN service fails because the request message is rejected by the network node, the processor may access the LADN service. A notification window indicating that the failure may be displayed on the display unit.

According to an embodiment of the present invention, it becomes clear when a PDU session for receiving LADN service is established, and since the PDU session establishment command / instruction is directly enabled by the network, the effect of increasing LDAN service utilization and flexibility occurs. do.

The effects obtainable in the present invention are not limited to the above-mentioned effects, and other effects not mentioned will be clearly understood by those skilled in the art from the following description. .

BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, included as part of the detailed description in order to provide a thorough understanding of the present invention, provide embodiments of the present invention and together with the description, describe the technical features of the present invention.

1 illustrates a 5G system architecture using a reference point representation.

2 is a diagram illustrating a wireless protocol stack to which the present invention can be applied.

3 is a diagram illustrating a LADN deployment (deployment) that can be applied to the present invention.

4 illustrates a general registration procedure according to an embodiment of the present invention.

5 is a diagram illustrating a preparation phase in handover according to an embodiment of the present invention.

FIG. 6 is a diagram illustrating execution phase in inter NG-RAN node N2-based handover according to an embodiment of the present invention.

7 is a diagram illustrating a method of providing LADN information according to an embodiment of the present invention.

8 is a diagram illustrating a method of operating AMF for reporting whether a UE is located in a LADN service area according to an embodiment of the present invention.

9 is a diagram illustrating an AMF operation method for determining whether a UE is located in an area of interest according to an embodiment of the present invention.

10 is a flowchart illustrating a LADN indication method for a UE according to an embodiment of the present invention.

11 is a diagram illustrating a display unit screen of the UE according to an embodiment of the present invention.

12 and 13 illustrate screens of a display unit of a UE according to an embodiment of the present invention.

14 and 15 illustrate screens of a display unit of a UE according to an embodiment of the present invention.

16 and 17 illustrate screens of a display unit of a UE according to an embodiment of the present invention.

18 is a diagram illustrating a UE positioning method based on interaction with an NEF / UDM according to an embodiment of the present invention.

19 is a flowchart illustrating a method of receiving a LADN service of a terminal according to an embodiment of the present invention.

20 is a block diagram of a terminal receiving a LADN service according to an embodiment of the present invention.

21 illustrates a block diagram of a communication device according to an embodiment of the present invention.

22 illustrates a block diagram of a communication device according to an embodiment of the present invention.

23 is a block diagram illustrating a mobile terminal according to the present invention.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. The detailed description, which will be given below with reference to the accompanying drawings, is intended to explain exemplary embodiments of the present invention and is not intended to represent the only embodiments in which the present invention may be practiced. The following detailed description includes specific details in order to provide a thorough understanding of the present invention. However, one of ordinary skill in the art appreciates that the present invention may be practiced without these specific details.

In some instances, well-known structures and devices may be omitted or shown in block diagram form centering on the core functions of the structures and devices in order to avoid obscuring the concepts of the present invention.

In this specification, a base station has a meaning as a terminal node of a network that directly communicates with a terminal. The specific operation described as performed by the base station in this document may be performed by an upper node of the base station in some cases. That is, it is obvious that various operations performed for communication with a terminal in a network composed of a plurality of network nodes including a base station may be performed by the base station or other network nodes other than the base station. A 'base station (BS)' may be replaced by terms such as a fixed station, a Node B, an evolved-NodeB (eNB), a base transceiver system (BTS), an access point (AP), and the like. . In addition, a 'terminal' may be fixed or mobile, and may include a user equipment (UE), a mobile station (MS), a user terminal (UT), a mobile subscriber station (MSS), a subscriber station (SS), and an AMS ( Advanced Mobile Station (WT), Wireless Terminal (WT), Machine-Type Communication (MTC) Device, Machine-to-Machine (M2M) Device, Device-to-Device (D2D) Device, etc.

Hereinafter, downlink (DL) means communication from a base station to a terminal, and uplink (UL) means communication from a terminal to a base station. In downlink, a transmitter may be part of a base station, and a receiver may be part of a terminal. In uplink, a transmitter may be part of a terminal and a receiver may be part of a base station.

Specific terms used in the following description are provided to help the understanding of the present invention, and the use of such specific terms may be changed to other forms without departing from the technical spirit of the present invention.

The following techniques are code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA), and NOMA It can be used in various radio access systems such as non-orthogonal multiple access. CDMA may be implemented by a radio technology such as universal terrestrial radio access (UTRA) or CDMA2000. TDMA may be implemented with wireless technologies such as global system for mobile communications (GSM) / general packet radio service (GPRS) / enhanced data rates for GSM evolution (EDGE). OFDMA may be implemented in a wireless technology such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, evolved UTRA (E-UTRA). UTRA is part of a universal mobile telecommunications system (UMTS). 3rd generation partnership project (3GPP) long term evolution (LTE) is a part of evolved UMTS (E-UMTS) using E-UTRA, and employs OFDMA in downlink and SC-FDMA in uplink. LTE-A (advanced) is the evolution of 3GPP LTE.

Embodiments of the present invention may be supported by standard documents disclosed in at least one of the wireless access systems IEEE 802, 3GPP and 3GPP2. That is, steps or parts which are not described to clearly reveal the technical spirit of the present invention among the embodiments of the present invention may be supported by the above documents. In addition, all terms disclosed in the present document can be described by the above standard document.

For clarity, the following description focuses on 3GPP LTE / LTE-A, but the technical features of the present invention are not limited thereto.

Terms that can be used in this document are defined as follows.

UMTS (Universal Mobile Telecommunications System): A third generation mobile communication technology based on Global System for Mobile Communication (GSM) developed by 3GPP

Evolved Packet System (EPS): A network system consisting of an Evolved Packet Core (EPC), which is a packet switched core network based on Internet Protocol (IP), and an access network such as LTE and UTRAN. UMTS is an evolutionary network.

NodeB: base station of UMTS network. It is installed outdoors and its coverage is macro cell size.

eNodeB: base station of EPS network. It is installed outdoors and its coverage is macro cell size.

-Home NodeB: Base station of UMTS network installed indoors, coverage of micro cell size

-Home eNodeB: Base station of EPS network installed indoors and coverage is micro cell size

User Equipment: User Equipment. A terminal may be referred to in terms of terminal, mobile equipment (ME), mobile station (MS), and the like. In addition, the terminal may be a portable device such as a laptop, a mobile phone, a personal digital assistant (PDA), a smartphone, a multimedia device, or the like, or may be a non-portable device such as a personal computer (PC) or a vehicle-mounted device. The term "terminal" or "terminal" in the MTC related content may refer to an MTC terminal.

Machine Type Communication (MTC): Communication performed by a machine without human intervention. It may also be referred to as M2M (Machine to Machine) communication.

MTC terminal (MTC UE or MTC device or MTC device): a terminal (eg, vending machine, etc.) having a function of communicating via a mobile communication network (for example, communicating with an MTC server via a PLMN) and performing an MTC function; Meter reading, etc.).

RAN (Radio Access Network): a unit including a Node B, a Radio Network Controller (RNC), and an eNodeB controlling the Node B in a 3GPP network. It exists at the terminal end and provides connection to the core network.

Home Location Register (HLR) / Home Subscriber Server (HSS): A database containing subscriber information in the 3GPP network. The HSS may perform functions such as configuration storage, identity management, and user state storage.

Public Land Mobile Network (PLMN): A network composed for the purpose of providing mobile communication services to individuals. It may be configured separately for each operator.

Non-Access Stratum (NAS): A functional layer for transmitting and receiving signaling and traffic messages between a terminal and a core network in a UMTS and EPS protocol stack. The main function is to support the mobility of the terminal and to support the session management procedure for establishing and maintaining an IP connection between the terminal and the PDN GW.

Service Capability Exposure Function (SCEF): An entity in the 3GPP architecture for service capability exposure that provides a means for securely exposing the services and capabilities provided by the 3GPP network interface.

Mobility Management Entity (MME): A network node of an EPS network that performs mobility management and session management functions.

-PDN-GW (Packet Data Network Gateway): Network node of EPS network that performs UE IP address allocation, packet screening and filtering, charging data collection

Serving GW (Serving Gateway): A network node of an EPS network that performs mobility anchor, packet routing, Idle mode packet buffering, and triggers paging for a UE of an MME.

-PCRF (Policy and Charging Rule Function): A node in the EPS network that performs policy decision to dynamically apply differentiated QoS and charging policies for each service flow.

PDN (Packet Data Network): A network where servers (eg, MMS server, WAP server, etc.) supporting a specific service are located.

-PDN connection: connection from the terminal to the PDN, that is, association (connection) of the terminal represented by the IP address with the PDN represented by the APN

Hereinafter, the present invention will be described based on the terms defined above.

본 발명이 적용될 수 있는 5G 시스템 아키텍처5G system architecture to which the present invention can be applied

The 5G system is an advanced technology from the 4th generation LTE mobile communication technology, and is a new radio access technology (RAT) and long-term LTE (Lvolution) through the evolution or clean-state structure of the existing mobile communication network structure. Term Evolution (Extended LTE) technology supports extended LTE (eLTE), non-3GPP (eg WLAN) access, and the like.

The 5G system is defined as service-based, and the interaction between network functions (NF) in the architecture for the 5G system can be expressed in two ways as follows.

Reference Point Representation: The interaction between NF services in NFs described by a point-to-point reference point (eg N11) between two NFs (eg AMF and SMF). Indicates.

Service-Based Representation: Network functions (eg AMF) in the Control Plane (CP) allow other authorized network functions to access their services. This expression also includes a point-to-point reference point if necessary.

1 illustrates a 5G system architecture using a reference point representation.

Referring to FIG. 1, the 5G system architecture may include various components (ie, a network function (NF)), and in this figure, some of them correspond to an authentication server function (AUSF). Function), Access and Mobility Management Function (AMF), Session Management Function (SMF), Policy Control Function (PCF), Application Function (AF) ), Unified Data Management (UDM), Data Network (DN), User Plane Function (UPF), (Wireless) Access Network ((R) AN: (Radio) Access Network ) Illustrates a user equipment (UE).

Each NF supports the following functions.

AUSF stores data for authentication of the UE.

AMF provides a function for UE-level access and mobility management and can be connected to one AMF basically per UE.

Specifically, AMF includes CN inter-node signaling for mobility between 3GPP access networks, termination of Radio Access Network (RAN) CP interface (ie, N2 interface), termination of NAS signaling (N1), NAS signaling security (NAS ciphering and integrity protection), AS security control, registration management (registration area management), connection management, idle mode UE reachability (control of paging retransmission and Mobility management controls (subscription and policy), intra-system mobility and inter-system mobility support, network slicing support, SMF selection, Lawful Intercept (AMF events and LI systems) Interface), providing delivery of session management (SM) messages between the UE and the SMF, transparent proxy for routing SM messages, access Access Authentication, access authorization including roaming authorization checks, delivery of SMS messages between the UE and the Short Message Service (SMSF) function, Security Anchor Function (SEA) and / or It supports functions such as Security Context Management (SCM).

Some or all functions of AMF may be supported within a single instance of one AMF.

DN means, for example, an operator service, an Internet connection, or a third party service. The DN transmits a downlink protocol data unit (PDU) to the UPF or receives a PDU transmitted from the UE from the UPF.

-PCF receives the packet flow information from the application server and provides the function to determine the policy of mobility management, session management, etc. Specifically, PCF supports a unified policy framework for controlling network behavior, providing policy rules for CP function (s) (eg, AMF, SMF, etc.) to enforce policy rules, and user data store (UDR). Supports functions such as front end implementation to access related subscription information for policy decision in User Data Repository.

-The SMF provides a session management function, and when the UE has a plurality of sessions, the SMF can be managed by different SMFs for each session.

Specifically, the SMF is responsible for session management (eg, establishing, modifying, and tearing down sessions, including maintaining tunnels between UPF and AN nodes), assigning and managing UE IP addresses (optionally including authentication), and selecting UP functionality. And control, setting traffic steering to route traffic to the appropriate destination in the UPF, terminating the interface towards policy control functions, enforcing the control portion of policy and QoS, and lawful intercept ( For SM events and interfaces to the LI system), termination of the SM portion of NAS messages, downlink data notification, initiator of AN specific SM information (delivered to the AN via N2 via AMF), It supports functions such as determining the SSC mode of the session and roaming functions.

Some or all functions of an SMF may be supported within a single instance of one SMF.

-UDM stores user subscription data, policy data, etc. The UDM includes two parts: an application front end (FE) and a user data repository (UDR).

The FE includes a UDM FE responsible for location management, subscription management, credential processing, and the PCF responsible for policy control. The UDR stores the data required for the functions provided by the UDM-FE and the policy profile required by the PCF. Data stored in the UDR includes user subscription data and policy data, including subscription identifiers, security credentials, access and mobility related subscription data, and session related subscription data. UDM-FE accesses subscription information stored in the UDR and supports features such as Authentication Credential Processing, User Identification Handling, Access Authentication, Registration / Mobility Management, Subscription Management, and SMS Management. do.

The UPF delivers the downlink PDU received from the DN to the UE via the (R) AN and the uplink PDU received from the UE via the (R) AN to the DN.

Specifically, the UPF includes anchor points for intra / inter RAT mobility, external PDU session points of the interconnect to the Data Network, packet routing and forwarding, packet inspection and User plane part of policy rule enforcement, lawful intercept, traffic usage reporting, uplink classifier and multi-homed PDU sessions to support routing of traffic flow to data network. Branching point to support, QoS handling for user plane (e.g. packet filtering, gating, uplink / downlink rate enforcement), uplink traffic verification (service data flow (SDF) : SDF mapping between service data flow and QoS flow), uplink and downlink transport level packet marking, downlink packet buffering and downlink data notification Functions such as triggering function are supported. Some or all of the functions of the UPF may be supported within a single instance of one UPF.

AF interacts with the 3GPP core network to provide services (e.g. application impact on traffic routing, access to Network Capability Exposure, and interaction with policy frameworks for policy control). It works.

-(R) AN is a new radio that supports both evolved E-UTRA (e-UTRA) and New Radio (NR) (e.g. gNB), an evolution of the 4G radio access technology. Collectively, the access network.

In the 5G system, the network node responsible for transmitting and receiving radio signals with the terminal is gNB and performs the same role as an eNB in EPS.

The gNB is capable of dynamic resource allocation to the UE in functions for radio resource management (ie, radio bearer control, radio admission control, connection mobility control, uplink / downlink). Dynamic allocation of resources (i.e., scheduling), IP (Internet Protocol) header compression, encryption and integrity protection of user data streams, and routing from the information provided to the UE to the AMF is not determined. The selection of AMF, UE plane data routing to UPF (s), control plane information routing to AMF, connection setup and release, scheduling and transmission of paging messages (from AMF), system broadcast Scheduling and transmission of cast information (from AMF or O & M), measurement and measurement reporting setup for mobility and scheduling, upstream Transport level packet marking on the link, session management, support for network slicing, QoS flow management and mapping to data radio bearers, support for UEs in inactive mode, NAS messages Features such as network distribution, NAS node selection, radio access network sharing, dual connectivity, and tight interworking between NR and E-UTRA.

UE means user equipment. The user device may be referred to in terms of terminal, mobile equipment (ME), mobile station (MS), and the like. In addition, the user device may be a portable device such as a laptop, a mobile phone, a personal digital assistant (PDA), a smartphone, a multimedia device, or the like, or may be a non-portable device such as a personal computer (PC) or a vehicle-mounted device.

In the drawings, for the sake of clarity, Unstructured Data Storage Network Function (UDSF), Structured Data Storage Network Function (SDSF), Network Exposure Function (NEF) ) And an NF Repository Function (NRF) are not shown, but all NFs shown in this figure may interoperate with UDSF, NEF, and NRF as needed.

NEF is provided by 3GPP network functions, for example, for 3rd party, internal exposure / re-exposure, application function, edge computing It provides a means to securely expose services and capabilities. The NEF receives information (based on the exposed capability (s) of the other network function (s)) from the other network function (s). The NEF may store the received information as structured data using a standardized interface to the data storage network function. The stored information is re-exposed to other network function (s) and application function (s) by the NEF and may be used for other purposes such as analysis.

NRF supports service discovery. Receives an NF discovery request from an NF instance and provides the NF instance with information about the found NF instance. It also maintains the available NF instances and the services they support.

-SDSF is an optional feature to support the ability to store and retrieve information as structured data by any NEF.

-UDSF is an optional feature to support the ability to store and retrieve information as unstructured data by any NF.

In the 5G system, the node and the node in charge of wireless transmission / reception are gNBs and perform the same role as the eNB in EPS. When the terminal is simultaneously connected to the 3GPP connection and the non-3GPP connection, the terminal receives a service through one AMF. In the case of accessing through a non-3GPP access and in the case of accessing through a 3GPP access, one may be connected to the same UPF, but it is not necessarily required, and may be connected to a plurality of different UPFs.

However, when the UE selects N3IWK (also referred to as 'N3IWF (Non-3GPP InterWorking Function)') in the HPLMN in a roaming scenario and is connected to a non-3GPP connection, the AMF managing the 3GPP connection is located in the VPLMN and the non-3GPP. The AMF managing the connection can be located in the HPLMN.

The non-3GPP access network is connected to the 5G core network via N3IWK / N3IWF. The N3IWK / N3IWF interfaces 5G core network control plane functions and user plane functions, respectively, via the N2 and N3 interfaces.

A representative example of a non-3GPP connection referred to herein may be a WLAN connection.

Meanwhile, in the figure, for convenience of description, a reference model for the case where the UE accesses one DN using one PDU session is illustrated, but the present invention is not limited thereto.

The UE may simultaneously access two (ie, local and central) data networks using multiple PDU sessions. In this case, two SMFs may be selected for different PDU sessions. However, each SMF may have the ability to control both the local UPF and the centralized UPF in the PDU session. It can be activated independently for each PDU session.

In addition, the UE may simultaneously access two (ie, local and central) data networks provided within a single PDU session.

In the 3GPP system, a conceptual link connecting NFs in a 5G system is defined as a reference point. The following illustrates reference points included in the 5G system architecture represented in this figure.

N1: reference point between UE and AMF

N2: reference point between (R) AN and AMF

N3: reference point between (R) AN and UPF

N4: reference point between SMF and UPF

N5: reference point between PCF and AF

N6: reference point between UPF and data network

N7: reference point between SMF and PCF

N24: reference point between PCF in visited network and PCF in home network

N8: reference point between UDM and AMF

N9: reference point between two core UPFs

N10: reference point between UDM and SMF

N11: reference point between AMF and SMF

N12: reference point between AMF and AUSF

N13: reference point between UDM and Authentication Server function (AUSF)

N14: reference point between two AMFs

N15: reference point between PCF and AMF in non-roaming scenario, reference point between PCF and AMF in visited network in roaming scenario

N16: reference point between two SMFs (in a roaming scenario, a reference point between an SMF in a visited network and an SMF in a home network)

N17: reference point between AMF and EIR

N18: reference point between any NF and UDSF

N19: reference point between NEF and SDSF

무선 프로토콜 아키텍처Wireless protocol architecture

2 is a diagram illustrating a wireless protocol stack to which the present invention can be applied. In particular, FIG. 2 (a) illustrates the air interface user plane protocol stack between the UE and the gNB, and FIG. 2 (b) illustrates the air interface control plane protocol stack between the UE and the gNB.

The control plane means a path through which control messages used by the UE and the network to manage a call are transmitted. The user plane refers to a path through which data generated at an application layer, for example, voice data or Internet packet data, is transmitted.

Referring to FIG. 2A, a user plane protocol stack may be divided into a first layer (Layer 1) (ie, a physical layer (PHY) layer) and a second layer (Layer 2).

Referring to FIG. 2 (b), the control plane protocol stack includes a first layer (ie, PHY layer), a second layer, and a third layer (ie, radio resource control (RRC) layer), It may be divided into a non-access stratum (NAS) layer.

The second layer includes a medium access control (MAC) sublayer, a radio link control (RLC) sublayer, a packet data convergence protocol (PDC) sublayer, a service data adaptation protocol ( SDAP: Service Data Adaptation Protocol (SDAP) sublayer (in case of user plane).

Radio bearers are classified into two groups: a data radio bearer (DRB) for user plane data and a signaling radio bearer (SRB) for control plane data.

Hereinafter, each layer of the control plane and the user plane of the radio protocol will be described.

1) The first layer, the PHY layer, provides an information transfer service to a higher layer by using a physical channel. The physical layer is connected to a MAC sublayer located at a higher level through a transport channel, and data is transmitted between the MAC sublayer and the PHY layer through the transport channel. Transport channels are classified according to how and with what characteristics data is transmitted over the air interface. In addition, data is transmitted between different physical layers through a physical channel between a PHY layer of a transmitter and a PHY layer of a receiver.

2) the MAC sublayer includes a mapping between a logical channel and a transport channel; Multiplexing / demultiplexing of MAC Service Data Units (SDUs) belonging to one or different logical channels to / from a transport block (TB) delivered to / from the PHY layer via the transport channel; Reporting scheduling information; Error correction through hybrid automatic repeat request (HARQ); Priority handling between UEs using dynamic scheduling; Priority handling between logical channels of one UE using logical channel priority; Padding is performed.

Different kinds of data carry the services provided by the MAC sublayer. Each logical channel type defines what type of information is conveyed.

Logical channels are classified into two groups: Control Channel and Traffic Channel.

i) The control channel is used to convey only control plane information and is as follows.

Broadcast Control Channel (BCCH): A downlink channel for broadcasting system control information.

Paging Control Channel (PCCH): A downlink channel that conveys paging information and system information change notification.

Common Control Channel (CCCH): A channel for transmitting control information between a UE and a network. This channel is used for UEs that do not have an RRC connection with the network.

Dedicated Control Channel (DCCH): A point-to-point bidirectional channel for transmitting dedicated control information between a UE and a network. Used by UE with RRC connection.

ii) The traffic channel is used to use only user plane information:

Dedicated Traffic Channel (DTCH) A point-to-point channel dedicated to a single UE for carrying user information, which may exist in both uplink and downlink. .

In downlink, the connection between a logical channel and a transport channel is as follows.

BCCH may be mapped to BCH. BCCH may be mapped to the DL-SCH. PCCH may be mapped to PCH. CCCH may be mapped to the DL-SCH. DCCH may be mapped to DL-SCH. DTCH may be mapped to the DL-SCH.

In uplink, a connection between a logical channel and a transport channel is as follows. CCCH may be mapped to UL-SCH. DCCH may be mapped to UL-SCH. DTCH may be mapped to UL-SCH.

3) The RLC sublayer supports three transmission modes: transparent mode (TM), unacknowledged mode (UM), and acknowledgment mode (AM).

The RLC configuration may be applied for each logical channel. TM or AM mode is used for SRB, while UM or AM mode is used for DRB.

The RLC sublayer is a delivery of higher layer PDUs; Sequence numbering independent of PDCP; Error correction through automatic repeat request (ARQ); Segmentation and re-segmentation; Reassembly of SDUs; RLC SDU discard; RLC re-establishment is performed.

4) PDCP sublayer for user plane includes sequence numbering; Header compression and decompression (only for Robust Header Compression (RoHC)); User data delivery; Reordering and duplicate detection (if delivery to a layer higher than PDCP is required); PDCP PDU routing (for split bearer); Retransmission of PDCP SDUs; Ciphering and deciphering; Discarding PDCP SDUs; PDCP re-establishment and data recovery for RLC AM; Perform replication of PDCP PDUs.

The PDCP sublayer for the control plane additionally includes sequence numbering; Ciphering, decryption, and integrity protection; Control plane data transfer; Replication detection; Perform replication of PDCP PDUs.

When duplication for a radio bearer is established by the RRC, an additional RLC entity and an additional logical channel are added to the radio bearer to control the replicated PDCP PDU (s). Replication in PDCP involves sending the same PDCP PDU (s) twice. One is delivered to the original RLC entity, the second to an additional RLC entity. At this time, the original PDCP PDU and the corresponding copy are not transmitted in the same transport block. Two different logical channels may belong to the same MAC entity (for CA) or may belong to different MAC entities (for DC). In the former case, logical channel mapping restrictions are used to ensure that the original PDCP PDU and its copy are not transmitted in the same transport block.

5) The SDAP sublayer performs i) mapping between QoS flows and data radio bearers, ii) QoS flow identifier (ID) marking in downlink and uplink packets.

A single protocol entity of SDAP is configured for each individual PDU session. However, two SDAP entities may be configured in the case of dual connectivity (DC).

6) The RRC sublayer is a broadcast of system information related to an access stratum (AS) and a non-access stratum (NAS); Paging initiated by 5GC or NG-RAN; Establishing, maintaining, and releasing RRC connections between the UE and the NG-RAN (in addition, modifying and releasing carrier aggregation), and additionally, dual connectivity between the E-UTRAN and the NR or within the NR (Dual). Connectivity); Security functions, including key management; Establishment, establishment, maintenance, and release of SRB (s) and DRB (s); Handover and context transfer; Control of UE cell selection and disaster recovery and cell selection / reselection; Mobility functionality including inter-RAT mobility; QoS management functions, UE measurement reporting and report control; Detection of radio link failures and recovery from radio link failures; NAS message delivery from NAS to UE and NAS message delivery from UE to NAS are performed.

PDUPDU 세션 관리 방법 Session management method

The AMF may give LADN information to the terminal when the terminal enters an area where the terminal can access a local access data network (LADN), and based on this, the terminal may create a PDU session in the LADN. LADN information in the AMF is stored by the network configuration. When the AMF gives LADN area information to the UE, the AMF may give only the area information intersected between the registration area and the LADN area to be allocated to the UE, rather than giving the entire LADN area information. For example, if the LADN area is TA2, TA3, TA4, TA5, and AMF allocates TA1, TA2, TA3, TA4 as a registration area to the terminal, TA2, TA3, Only TA4 is delivered, TA5 is not. According to the current standard, it is not clear whether the AMF knows all LADN area information as the information about the LADN area or whether only the LADN area information on the area managed by AMF among the LADN areas is known.

Referring to FIG. 3, when the network configures TA1, TA2, TA3, TA4 as the LADN area, it is not clear in the current standard whether AMF knows only TA1, TA2 or only TA3, TA4 as the LADN area. .

On the other hand, according to the current standard, when the terminal leaves or enters the LADN area, the AMF is configured to send an indication to the SMF whether the terminal leaves or enters the LADN area. In the example of FIG. 3, when the terminal moves only in the AMF1 region, the AMF1 may know whether the terminal leaves the LADN regions TA1 and TA2 and may inform the SMF. However, if you leave the AMF1 area and move to another AMF area, if the AMF does not know all the information about the LADN area, it is not possible to know whether it is out of the LADN area or in the LADN area. In addition, even if the AMF has information on the entire LADN area, the AMF may not be aware of this when it moves to another area due to idle mode mobility. In addition, even in the connected mode, when the TA is allocated on a cell basis, the AMF does not know the exact target cell information during the handover process and thus does not know exactly whether it is out of the LADN region. The present invention proposes a method for solving this problem.

When the LADN PDU session is created, the SMF may configure a service to notify the AMF when the terminal leaves or enters the LADN area. This service is requested by the SMF during the creation of a PDU session, which is either a UE context or a service context (e.g., the last indication sent last) that receives this request and stores the last information AMF sent to the SMF. sent indication). When the AMF informs the SMF of the UE out of the LADN area, the AMF sets the last transmitted indication to "moved out", and sets the last transmitted indication to "moved in" when notifying that the UE enters the LADN area. Since the first service is generated when the terminal is in the LADN region, the last transmitted indication is set to "moved in." This information is sent together as part of the UE context (or together as part of the service context) to the new AMF if the AMF changes, and new AMF sends it to the SMF based on the last transfer indication if it determines that it has left or entered the LADN area. Let me know

For example, if the last transmission instruction received by new AMF was "moved in" and the terminal remains in the LADN area, the terminal does not send an instruction to the SMF. If the terminal is not in the LADN region, the last transmission instruction is sent to the SMF. moved out ".

Since the terminal may have a plurality of LADN PDU sessions, the terminal should have a final transmission indication for each LADN Data Network Name (DNN) of the LADN PDU session that the terminal has.

This invention is generally applicable when using a location reporting service in a general PDU session in addition to a PDU session for LADN. For example, in order to determine whether the SMF is out of the UPF service area while creating a PDU session, the AMF may be informed of the location of interest, and the location report may be received. It can be solved by the present invention proposed in the.

The last transmitted indication may also be stored in a form indicating whether it is in the LADN area of the terminal. For example, when the last transmission indication is "moved in", the terminal is the same as being in the LADN, and when it is "moved out", the terminal is the same as being outside the LADN. Therefore, the state of the terminal may be stored, for example, in the form of "in" or "out".

According to the related art, when the terminal enters the idle mode outside the LADN region while the terminal has a LADN PDU session, an indication to the SMF is sent to the idle mode. In idle mode, since the exact location of the terminal cannot be determined, it is not known whether it is in the LADN region or outside. Therefore, this operation is performed to allow paging to be sent to the terminal when downlink data occurs. When the AMF performs this operation, it can set the last transfer indication to "moved in." This is because when the UE is in idle mode, the SMF does not need to send an additional "moved in" instruction because the UE operates in the same manner as in the LADN.

In the case of LADN, the SMF provides the LAMF DNN to the AMF only to subscribe to the notification when the UE enters the LADN service area. The AMF informs the SMF when the AMF detects that the UE has entered and exited the LADN-enabled area. Upon receiving a notification from the AMF that the UE has moved into or out of the LADN area, the SMF determines how to handle the PDU session (eg, PDU session release, user plane connection deactivation for the PDU session, etc.). The AMF may send the UE location to the SMF with a notification (for UPF relocation).

AMF notifies the SMF of "moved in" or "moved out" events. In order to detect a "moved in" or "moved out" state, AMF needs to have the last notified LADN state (eg, Inside LADN Zone or Outside LADN Zone).

Observation 1: The AMF must have the last notified LADN state (eg, inside LADN zone or outside LADN zone) to report a "moved in" or "moved out" event.

Proposal 1: If the AMF subscribes to report LADN areas, it is proposed to clarify that AMF stores the last notified LADN state (eg, Inside LADN area or Outside LADN area).

According to TS 23.502 clause 4.2.2.2.2 (Registration Procedure), the sentence reads:

4. [conditional] From new AMF to old AMF: Namf_Communication_UEContextTransfer (complete registration request).

If the 5G-GUTI (Globally Unique Temporary Identity) of the UE is included in the registration request and the serving AMF has changed since the last registration procedure, then the new AMF will be applied to the old AMF that contains a complete registration request IE (IE) that can be integrity protected. The Namf_Communication_UEContextTransfer service operation can be invoked to request a subscription permanent identifier (SUPI) and MM context of the UE. See Section 5.2.2.2.2 for details of this service operation. The old AMF uses an integrity protected complete registration request IE to verify that the context transfer service action call corresponds to the requested UE.

The old AMF also forwards event subscription information by each consumer NF for the UE to the new AMF.

Note 1: The consumer NF does not need to register the event again with new AMF after the UE has successfully registered with the new AMF.

If new AMF has already received the UE context from old AMF during the handover procedure, steps 4, 5 and 10 can be skipped.

Event subscriptions are sent between old AMF and new AMF, so the consumer NF does not need to subscribe to the event again. However, it is not clear which AMF (for example, old or new AMF) informs SMF of the location reporting event.

Observation 2: It is not clear which AMF (eg, old AMF or new AMF) announces a location reporting event when the AMF changes.

If the AMF is changed, the old AMF may not have enough information about the UE location. For example, if the UE is in the CM-IDLE state and out of the registration area, the UE performs a registration procedure. Then, the new AMF knows the exact UE location, and the old AMF does not have the UE location information. Therefore, the present specification proposes to notify the SMF of the event to which the new AMF subscribed.

Proposal 2: When AMF changes, new AMF notifies the location reporting event.

LADN location reporting is performed when the AMF detects a "moved in" or "moved out" condition. To detect the condition, new AMF must know the last LADN UE state (eg, Inside LADN area or Outside LADN area). Therefore, the present specification proposes that the last LADN UE status is transmitted to new AMF with event subscription.

Proposal 3: The last notified LADN state (for example, inside LADN area or outside LADN area) is transferred between old AMF and new AMF.

According to TS 23.501 Section 5.6.5, the AMF is configured with LADN information as follows:

The LADN information is set in units of DNs in the AMF, and the set LADN service area is the same regardless of other elements (for example, a registration area of the UE).

When the AMF provides LADN service area information, the AMF provides a set of tracking areas that belong to the UE's current registration areas (ie, the intersection of the LADN service area and the current registration area).

However, it is not clear whether the AMF knows the entire LADN service area or part of the LADN service area (that is, the intersection of the LADN service area and the AMF service area) belonging to the AMF service area.

Observation 3: It is not clear whether AMF knows the whole LADN service area or part of the LADN service area belonging to the AMF service area.

Under

proposals

2 and 3, the AMF does not need to know the entire LADN coverage area. Therefore, this specification proposes to clarify that AMF does not need to know the entire LADN service area.

Proposition 4: It is proposed to clarify that the AMF does not need to know the entire LADN coverage area.

Access to DNs via PDU sessions to LADNs is only available in certain LADN service areas. The LADN service area is a set of tracking areas. 5GC should support UE to be aware of the availability of LADN based on UE location.

In the case of LADN, the AMF provides LADN information about the LADN availability to the UE, and the AMF informs the SMF by tracking whether the UE is located in the LADN service area (ie, the LADN availability area).

The LADN service area set in the AMF should not be the entire LADN service area and may be limited to the service area of the AMF.

The LADN information provided to the UE by the AMF consists of LADN DNN and LADN service area information availability for the UE. The LADN service area information provided to the UE during the registration procedure includes a set of tracking areas belonging to the current registration area (ie, the intersection area of the LADN service area and the current registration area) of the UE. AMF does not create a registration area based on the availability of LADN.

Note 1: Since the LADN service area may include TA (s) outside the registration area of the UE, the LADN service area information sent to the UE by the AMF may include only a subset of the full LADN service area. .

When a UE performs a successful (re) registration procedure, the AMF may provide local configuration information (e.g., LADN information, UE location, UE subscription information received from the UDM for a DNN subscribed as a LADN, or policies provided by the PCF). For example, based on OAM (Orbital Angular Momentum)) may provide LADN information on the LADN that can be used by the UE to the RA in the registration approval message. During the subsequent registration update procedure except for the periodic registration update procedure, if the network does not provide LADN information, the UE deletes the LADN information.

If the LADN information for the UE in the 5GC is changed, the AMF may update the LADN information with the UE through the UE configuration update procedure described in Section 4.2.4 of TS 23.502 [3].

Based on the LADN information in the UE, the UE may request to establish a PDU session for the LADN available when the UE is located in the LADN service area. When the UE is outside of the LADN service area, the UE shall not request a PDU session for LADN and the SMF shall reject such request. When a UE is located outside of the LADN service area, it should not trigger service requests for activating User Plane (UP) connections of LADN PDU sessions, establishing / modifying UE initiated PDU sessions, and activating UP connections for LADN PDU sessions during the re-registration process No, the SMF must deny establishment / modification of the LADN PDU session and activation of the UP connection.

The SMF subscribes to the "UE Location Change Notification" as described in Section 5.6.11. Based on the notification that the UE enters and exits the LADN received from the AMF, the SMF may determine the following:

Whether a network trigger service request should be triggered for a LADN PDU session with user plane connection disabled.

-Release the PDU session, or

-Disable user plane connections for PDU sessions and maintain PDU sessions. The network may release the PDU session later at any time in accordance with network policy. The SMF may request that the UPF not discard the downlink data for the PDU session or send a data notification message to the SMF.

This decision may be influenced by local policy.

In a network deployment where the UE may leave or enter the LADN service area without notifying the 5GC in the CM-CONNECTED state, the AMF initiates location reporting as described in 5.6.11 to associate the UE with the LADN service area in the CM-CONNECTED state. You need to track the exact location of.

When leaving the LADN service area, the UE does not need to release the LADN PDU session unless it receives an explicit PDU session release request from the network.

The SMF must not trigger user plane connection activation for a PDU session corresponding to the LADN if the SMF knows that the UE is outside the available area of the LADN.

When the AMF detects that the UE has entered the LADN service area, the AMF based on the SMF subscription to the area of interest corresponding to the LADN notifies the SMF. If there is pending DL data in the SMF or UPF, the SMF performs a network trigger service request to activate the UP connection for the PDU session. Otherwise, SMF should prompt UPF to resend DL data notification to SMF in case of DL data.

When the NAS signaling connection is released, after receiving an N2 UE Context Release Complete for the PDU session corresponding to the LADN, the AMF sends a LADN event ("moved in" or "moved out") to the SMF with an indication of the NAS signaling connection release. And notify the UPF that the SMF previously discarded downlink data for PDU sessions and / or not providing an additional downlink data notification message. Once the NAS signaling connection is established, the AMF notifies the SMF of the LADN event (“moved in” or “moved out”) with the NAS signaling connection establishment indication, and the SMF can request the UPF to discard the downlink data for the PDU session. And / or do not send data notification messages to the SMF.

In this embodiment, LADN may be applied only to 3GPP access.

When a PDU session is established or modified, or when a user plane path has changed (eg, UPF reallocation), the SMF determines the area of interest (eg, based on the UPF service area) and informs the AMF. You can join. When the AMF detects that the UE has moved into or out of its area, it is necessary to inform the SMF of the new location of the UE.

For 3GPP access, the region of interest is defined by a tracking region list.

SMF subscribes to the "UE mobility event Notification" service provided by AMF. During the subscription, the SMF provides the area of interest to the AMF. When the AMF detects that the UE has moved into or out of its area, the AMF sends the SMF the new location of the UE. Upon receiving a new UE location notification from the AMF, the SMF determines how to handle the PDU session (eg, relocate the UPF).

If the AMF is subscribed to the region of interest by the SMF and this region of interest is smaller than the registration region sent to the UE, the AMF may provide the region of interest to the NG-RAN via a designated location reporting procedure (TS 23.502 [3] ). If the NG-RAN detects that the UE moves out of or out of the region of interest provided by the AMF, the NG-RAN notifies the AMF of the latest UE location.

In the case of LADN, the SMF provides a LADN DNN to the AMF to subscribe to the notification when the UE enters the LADN service area. The AMF informs the SMF when the AMF detects that the UE has entered and exited the LADN-enabled area. AMF stores the last / last notified LADN state (eg, "inside LADN area" or "Outside LADN area") and is sent between AMFs with service subscriptions. When the AMF receives a notification from the AMF that the UE has moved into or out of the LADN area, the SMF determines how to handle the PDU session (eg, releases the PDU session and deactivates the user plane connection to the PDU session). . The AMF may send the UE location to the SMF with the notification (eg for UPF relocation).

The subscription (or subscription information) may be maintained for the life of the PDU session regardless of the UP activation state (eg, PDU session UP connection activation or deactivation) of the PDU session.

The SMF determines the new area of interest and sends a new subscription to the AMF with the area of interest.

The SMF unsubscribes from the "UE mobility event notification" service when the PDU session is released.

The UE location change notification may also be subscribed to by another NF.

The AMF notifies the SMF of the "moved in" or "moved out" event. To detect a "moved in" or "moved out" state, AMF needs to know the last / last notified LADN state (eg, inside LADN area or outside LADN area).

1. UE to (R) AN: AN message (AN parameter, RM-NAS registration request (registration type, SUPI or 5G-GUTI, last visited Tracking Area Identifier (if available)), security parameters, requested NSSAI, UE 5GC function, PDU session state, PDU session to be reactivated, Follow on request, Mobile Initiated Connection Only (MICO) mode preference).

For NG-RAN, the AN parameter includes, for example, SUPI or 5G-GUTI, the selected PLMN ID and the requested NSSAI, and the AN parameter also includes the cause of establishment. The cause of establishment provides a reason for requesting establishment of an RRC connection.

The registration type may be defined by the UE as "initial registration (ie, UE is in RM-DEREGISTERED state)", "mobility registration update (ie, UE is in RM-REGISTERED state and initiates registration procedure because of mobility)" or "cyclic Indicates whether or not you want to perform a registration update (ie, the UE is in the RM-REGISTERED state and starts the registration process due to the periodic registration update timer expiration). A UE performing registration (ie, the UE is in the RM-DEREGISTERED state) must include its SUPI in the registration request, in other cases a 5G-GUTI, indicating the last serving AMF. If a new PLMN (i.e. not a registered PLMN or an equivalent PLMN of a registered PLMN) and another PLMN has already been registered through non-3GPP access, the UE will be able to access the non-3GPP connection via 5G-GUTI via 3GPP access. Through the AMF during the registration process In addition, if the UE is already registered via 3GPP access in a different PLMN (ie, a registered PLMN) than a new PLMN (ie, a registered PLMN or an equivalent PLMN of a registered PLMN) of a non-3GPP access, The UE shall not provide, via non-3GPP access, the 5G-GUTI assigned by AMF during the registration process via 3GPP access, based on its configuration as defined in TS 23.501 [2] Section 5.16.3.7. Can provide a usage setting.

If possible, the last visited TAI should be included to help the AMF create the registration area for the UE.

Security parameters are used for authentication and integrity protection. The requested NSSAI indicates network slice selection support information (as defined in section 5.15 of TS 23.501 [2]). The PDU session state indicates a PDU session previously established at the UE. The PDU session (s) to be reactivated is included to indicate the PDU session (s) for which the UE wishes to activate the UP connection. The PDU session corresponding to the LADN should not be included in the PDU session to be reactivated when the UE is outside the available area of the LADN. Follow on request is included when the UE has pending uplink signaling and the UE does not include a PDU session to be reactivated.

2. If SUPI is included or 5G-GUTI does not indicate a valid AMF, then select AMF according to (R) AT and the requested NSSAI (if available).

(R) AN selects AMF as described in clause 6.3.5 of TS 23.501 [2].

If the (R) AN cannot select the appropriate AMF, it sends a registration request to the AMF set in the (R) AN to perform the AMF selection.

3. From (R) AN to new AMF: N2 message (N2 parameter, RM-NAS registration request (registration type, SUPI or 5G-GUTI, last visited TAI, if available), security parameter, requested NSSAI, UE 5GC function, PDU session status, PDU session to be reactivated, Follow on request, MICO mode preferred).

When NG-RAN is used, the N2 parameter includes the selected PLMN ID, location information, cell identifier and RAT type related to the cell the UE is camping on.

When NG-RAN is used, the N2 parameter also includes the cause of establishment.

If the registration type indicated by the UE is a periodic registration update, step 4 to step 17 may be omitted.

4. [conditional] new AMF to old AMF: Namf_Communication_UEContextTransfer (complete registration request).

If the UE's 5G-GUTI is included in the registration request and the serving AMF has changed since the last registration procedure, then the new AMF will invoke the Namf_Communication_UEContextTransfer service behavior for the old AMF containing the complete registration request IE that can be integrity protected. Can be called to request See Section 5.2.2.2.2 for details of this service operation. The old AMF uses an integrity protected complete registration request IE to verify that the context transfer service action call corresponds to the requested UE.

5. [conditional] From old AMF to new AMF: Response to Namf_Communication_UEContextTransfer (SUPI, UE context, SMF information, PCF ID, event subscription).

The old AMF responds to the new AMF for the Namf_Communication_UEContextTransfer call by including the UE's SUPI and UE / MM context.

Event subscriptions include subscribed service actions with an associated context.

If old AMF holds information about established PDU sessions, old AMF includes SMF information including S-NSSAI, SMF identifier and PDU session ID.

If old AMF holds information about an active NGAP (NG Application Protocol) UE-TNLA binding for N3IWF, old AMF includes information about NGAP UE-TNLA binding.

The consumer NF does not need to subscribe to the event again with new AMF after the UE has successfully registered with new AMF.

6. [conditional] new AMF to UE: identification request ().

If the SUPI is not provided by the UE or retrieved from the old AMF, the identification request procedure is initiated by the AMF sending an identification request message to the UE.

7. [conditional] new AMF: Identification response () at UE.

The UE responds with an identification response message containing SUPI.

8. The AMF may decide to start the UE authentication by calling AUSF. In this case, the AMF shall select the AUSF described in Section 6.3.4 of TS 23.501 [2] based on SUPI.

9a. The AUSF must execute authentication of the UE.

Authentication is performed as defined in the standard and requires UDM. The AUSF discovers UDM as described in TS 23.501 [2], section 6.3.8.

If network slicing is used, the AMF determines whether the initial AMF should re-route the registration request as described in Section 4.2.2.2.3, which references the AMF.

9b. AMF should initiate NAS security.

NAS security can be performed as defined in the standard.

10. [conditional] From new AMF to old AMF: Namf_Communication_RegistrationCompleteNotify ().

If AMF is changed, new AMF notifies old AMF by invoking Namf_Communication_RegistrationCompleteNotify service operation that the registration of UE is completed in new AMF.

If the authentication / security procedure fails, registration is rejected and new AMF invokes the Namf_Communication_RegistrationCompleteNotify service action with a rejection indication reason code for old AMF. The old AMF continues as if no UE context transfer service operation was received.

If one or more S-NSSAIs used in the previous registration area cannot be serviced in the target registration area, new AMF determines a PDU session that cannot be supported in the new registration area. The new AMF invokes the Namf_Communication_RegistrationCompleteNotify service operation to the old AMF, which includes the rejected PDU session ID and the reason for rejection (eg, S-NSSAI is no longer available). New AMF then modifies the PDU session state accordingly. old AMF tells the SMF to release the UE's SM context locally by calling the Nsmf_PDUSession_ReleaseSMContext service operation.

The details of Namf_Communication_RegistrationCompleteNotify service operation are described in Section 5.2.2.2.3.

11. [conditional] new AMF to UE: identification request / response (Permanent Equipment Identifier).

If the PEI has not been provided by the UE or has not been retrieved from the old AMF, the identification request procedure is initiated by the AMF sending an identification request message to the UE to retrieve the PEI.

12. Optionally, new AMF invokes the N5g-eir_MEquipmentIdentityCheck_Get service action (see Section 5.2.4.2.2) to start the ME identity check.

PEI verification is performed as described in Section 4.7.

When step 14 is performed, new AMF selects the UDM based on SUPI.

The AMF selects the UDM as described in TS 23.501 [2], section 6.3.8.

14a-b. If the AMF has changed since the last registration procedure, or if the UE provides SUPI that does not reference a valid context in the AMF, or if the UE registers with the same AMF and is already registered for non-3GPP access (i.e., the UE is non- The new AMF registers with the UDM using Nudm_UECM_Registration and registers to be notified when the UDM unregisters this AMF, registered via 3GPP access and starting this registration procedure to add 3GPP access. AMF retrieves mobility subscription data using Nudm_SDM_Get and subscribes to notifications using Nudm_SDM_Subscribe when mobility subscription data is modified. If a generic public subscription identifier (GPSI) is available in the UE subscription data, the GPSI is provided from the UDM to the AMF of the subscription data.

PEI is provided to the UDM in the update location procedure.

New AMF provides the type of access provided to the UDM for the UE, and the access type is set to "3GPP access". UDM stores the associated access type with the serving AMF.

14c. As indicated in step 14a, the UDM stores the access type associated with the serving AMF, and if present, the UDM initiates Nudm_UECM_DeregistrationNotification (see section 5.2.3.2.2) for the old AMF corresponding to the 3GPP access. It can be done. old AMF removes the MM context of the UE. If the serving NF removal reason indicated by the UDM is "initial registration", old AMF invokes the Namf_EventExposure_Notify service operation on all relevant SMFs of the UE to notify that the UE has been deregistered from old AMF. The SMF must release the PDU session upon receiving this notification.

14d. Old AMF can use Nudm_SDM_unsubscribe to unsubscribe from UDM for subscription data.

15. When new AMF receives the PCF ID from old AMF in step 5 and successfully contacts the PCF identified by the PCF ID, new AMF retrieves the dynamic policy from the PCF.

If the PCF identified by the PCF ID is not available (for example, no response from the PCF), or if there is no PCF ID received from the old AMF in step 5, then the AMF will perform as described in TS 23.501 [2], section 6.3.7.1. Select PCF.

16. [Optional] From AMF to PCF: Npcf_AMPolicyControl_Get (SUPI, GPSI).

If AMF has not yet obtained an access and mobility policy for the UE, or if AMF's access and mobility policy is no longer valid, AMF requests the PCF to enforce the operator policy for the UE from the PCF through the Npcf_AMPolicyControl_Get service action. (See section 5.2.5.2.2). GPSI is included if possible in the AMF. In the case of roaming, the interaction between H (Home) -PCF and V (Visited) -PCF is necessary for the provision of access and mobility policies.

From PCF to new AMF: Response to Npcf_AMPolicyControl_Get (access and mobility policy data).

The PCF responds to the Npcf_AMPolicyControl_Get service operation and provides the AMF with access and mobility policy data for the UE.

17. [conditional] AMF to SMF: Namf_EventExposure_Notify () or Nsmf_PDUSession_UpdateSMContext ().

AMF calls Namf_EventExposure_Notify (see Section 5.2.2.3.4) or Nsmf_PDUSession_UpdateSMContext (see Section 5.2.8.2.6) in one or more of the following scenarios:

If the AMF changes, the new AMF notifies each SMF of the new AMF serving the UE by informing the UE reachability status. If AMF is changed, it is assumed that old AMF provides the SMF information available. If any PDU session state indicates that the PDU session is released at the UE, the AMF calls the Nsmf_PDUSession_ReleaseSMContext service action towards the SMF to release any network resources associated with the PDU session.

If the "PDU session to be reactivated" is included in the registration request of step 1, the AMF sends an Nsmf_PDUSession_UpdateSMContext request to the SMF associated with the PDU session to activate the user plane connection of the PDU session. PDU session. After step 4 described in section 4.2.3.3, the AMF is executed to complete the activation of the user plane connection without sending the MM NAS service authorization to (R) AN described in step 8 of section 4.2.3.3.

If the UE is in MICO mode and the AMF cannot reach the UE and the SMF does not need to send a DL data notification to the AMF, the AMF informs the SMF that the UE is reachable.

If the AMF notifies the SMF that it can only reach the regulatory prioritized service and the UE enters the allowed zone, it informs the SMF that the UE is reachable.

If the UE is in the disallowed zone and the PDU session to be reactivated is included in the registration request, the AMF informs that all relevant SMF (s) of the UE are reachable only for regulatory priority services.

The AMF also notifies the NF (s) that subscribed to the UE reachability of the UE reachability change.

If the AMF subscribes to the UE location change notification via the Namf_EventExposure_Subscribe service operation and AMF detects that it has left the region of interest subscribed to by the SMF serving the UE, the AMF calls the Namf_EventExposure_Notify service action to tell the SMF the new location of the UE. Can inform information. For LADN location change notifications, the AMF only invokes the Namf_EventExposure_Notify service behavior if the detected LADN status (eg, "inside LADN zone" or "outside LADN zone") is different from the last / last notified LADN status. Call When an event is notified to the SMF, the last / last notified LADN state is updated to the detected LADN state.

Whether the notification Ack needs a separate message or is implemented in the transport layer is determined in TS 29.518 [18].

The SMF may, for example, determine the trigger of a new intermediate UPF insertion, removal, relocation or UPF relocation (as described in step 5 of section 4.2.3.2).

If the registration type indicated by the UE is a periodic registration update, step 20 may be omitted.

If the serving AMF is changed, the new AMF must wait until step 17 is completed with all SMFs associated with the UE. Otherwise, steps 18 through 22 can continue in parallel with this step.

18. New AMF for N3IWF: N2 Request ().

The AMF may decide to modify the NGAP UE-TNLA-binding towards N3IWF as described in 4.2.7.2. This is done if the AMF is changed and the old AMF has an existing NGAP UE-TNLA-binding for N3IWF for the UE.

19. From N3IWF to new AMF: N2 Response ().

20. [conditional] old AMF to PCF: Npcf_AMPolicyControl_Delete ().

If old AMF has previously requested to establish a UE context in the PCF, old AMF terminates the UE context in the PCF using the Npcf_AMPolicyControl_Delete service action (see section 5.2.5.2.4). From PCF to old AMF: Response to Npcf_AMPolicyControl_Delete ().

21.New AMF to UE: Registration Acknowledgment (5G-GUTI, Registration Area, Mobility Restriction, PDU Session Status, Allowed NSSAI, Periodic Registration Update Timer, LADN Information and Allowed MICO Modes, Packet Switched Session Instruction Support) ).

The AMF sends a registration grant message to the UE indicating that the registration request has been approved. If AMG assigns a new 5G-GUTI, it includes 5G-GUTI. When the AMF allocates a new registration area, the registration area should be transmitted to the UE through a registration approval message. If the registration approval message does not include a registration area, the UE should consider the previous registration area as valid. Mobility restrictions are included where mobility restrictions apply to the UE. The AMF indicates the PDU session established for the UE in the PDU session state. The UE locally removes any internal resources associated with the PDU session that are not marked as established in the received PDU session state and the UE has requested a PDU session establishment but is not yet a received SMF response. If the PDU session state information is in the registration request, the AMF should indicate the PDU session state to the UE. NSSAI includes allowed S-NSSAI. If the UE subscription data includes subscribed LADN identification information, then the AMF is available for the UE within the registration area determined by the AMF in the registration grant message, and the LADN for the LADN defined in TS 23.501 [2] 5.6.5. You must include the information. If the UE includes the MICO mode in the request, the AMF responds whether the MICO mode should be used. The AMF establishes an IMS (IT Multimedia Service) Voice over PS session support indication as described in Section 5.16.3.2 [2] of TS 23.501. In order to establish the IMS Voice over PS session support indication, the AMF needs to perform the UE / RAN radio information and compatibility request procedure in Section 4.2.8 to check the compatibility of UE and RAN radio functions related to IMS Voice over PS. If the AMF has not yet received a voice support match indicator from the NG-RAN, then the AMF may set the PS session support indication to IMS voice and update it in subsequent steps, depending on the implementation.

In this step, the handover restriction list is provided to the NG-RAN by the AMF.

If a 'Follow on request' is included, the AMF shall not release the signaling connection immediately after the registration process is completed.

22. [conditional] UE to new AMF: registration completed ().

The UE sends a registration complete message to the AMF to confirm whether a new 5G-GUTI has been assigned.

When the "PDU session to be reactivated" is not included in the registration request, the AMF releases the signaling connection with the UE according to section 4.2.6. If a subsequent request is included in the registration request, the AMF shall not release the signaling connection immediately after the registration procedure is completed.

5 is a diagram illustrating a handover preparation phase according to an embodiment of the present invention. In particular, FIG. 5 is a diagram illustrating a preparation step in inter NG-RAN node N2-based handover.

1. From S (source) -RAN to S-AMF: handover required (target ID, source to target transparent container, SM N2 information list, PDU session ID).

The target ID includes the selected PLMN ID.

The source to target transparent container contains RAN information generated by S-RAN to be used by T (Target) -RAN and is transparent to 5GC.

All PDU sessions handled by the S-RAN (i.e., all existing PDU sessions with an active UP connection) are included in a handover required message indicating which of the PDU sessions were requested to be handed over by the S-RAN. Included. In SM N2 information, direct forwarding path validity and QoS flow are subject to data delivery.

Direct delivery path validity indicates whether direct forwarding can be used from the S-RAN to the T-RAN. This indication from the S-RAN includes, for example, the presence of IP connectivity and secure connection (s) between the S-RAN and the T-RAN.

2. T (Target) -AMF selection: If the S (Source) -AMF can no longer provide UE services, the S-AMF is described in Section 6.4.5 of “AMF Selection Function” of TS 23.501 [2]. Select T-AMF as shown.

3. [conditional] From S-AMF to T-AMF: Namf_Communication_CreateUEContext Request (N2 information (target ID, source to target transparent container, SM N2 information list, service area limitation), UE context information including SUPI, event subscription information And a list of PDU session IDs with associated context and corresponding SMF information.

The S-AMF initiates the handover resource allocation procedure by invoking the Namf_Communication_CreateUEContext service operation towards the T-AMF.

If the S-AMF can still serve the UE, this step and step 12 are not necessary.

If service area restrictions are available in the S-AMF, they may be forwarded to the T-AMF as described in section 5.3.4.1.2 of 3GPP TS 23.501.

4. [conditional] T-AMF to SMF: Nsmf_PDUSession_UpdateSMContext (PDU session ID, target ID, T-AMF ID).

For each PDU session indicated by the S-RAN as an N2 handover candidate, the AMF invokes a PDU session specific Nsmf_PDUSession_UpdateSMContext request for the associated SMF.

The PDU session ID indicates a PDU session candidate for N2 handover. Target ID as UE location information.

If the (T-) AMF detects that the UE moves to an unlicensed area based on the service area restriction, the (T-) AMF sends a UE to each SMF corresponding to the list of PDU sessions received from the handover request message. Notifies that only regulatory priority services are reachable.

5. [conditional] Based on the target ID, the SMF checks whether N2 handover for the indicated PDU session can be accepted. The SMF checks the UPF Selection Criteria in accordance with Section 6.3.3 of TS 23.501 [6]. If the UE leaves the service area of the UPF connecting to the RAN, the SMF selects a new intermediate UPF. If the PDU session corresponds to the LADN and the UE is outside the available area of the LADN, the SMF moves to step 6c.

6a. [Conditional] SMF in TMF (intermediate): request to establish N4 session

If the SMF selects a new intermediate UPF (ie, target UPF (T-UPF)) for the PDU session, and CN tunnel information is allocated by the T-UPF, an N4 session establishment request message is sent to the T-UPF, Provides packet detection, enforcement, and reporting rules installed in the T-UPF. PDU session anchor tunnel information for this PDU session is also provided to the T-UPF.

6b. T-UPF (Medium) to SMF: N4 Session Establishment Response

The T-UPF sends an N4 session establishment response message to the SMF with DL CN tunnel information and UL CN tunnel information (ie, N3 tunnel information). The SMF starts a timer to release resources of the S-UPF to be used in step 12a of the execution step.

If

steps

6a and 6b are performed for the PDU session, steps 6c and 6d are skipped.

6c, d. [Conditional] SMF to S-UPF: N4 session modification request / response

If the PDU session corresponds to the LADN and the UE is outside the available area of the LADN, the SMF updates the N4 session of the UPF (s) corresponding to the PDU session to deactivate the corresponding UP connection. The SMF may notify the UPF that sent the data notification to discard the downlink data for the PDU session and no longer provide a data notification message.

7. From SMF to T-AMF: Nsmf_PDUSession_UpdateSMContext Response (PDU Session ID, SM N2 Information).

If N2 handover is granted for the PDU session, the SMF sends a SM N2 information including the N3 UP address and the UP CN tunnel ID of the UP CN and a QoS parameter indicating that the SM N2 information is for the target NG-RAN in the Nsmf_PDUSession_UpdateSMContext response. Include it.

If N2 handover is not approved for the PDU session as described in step 4, the SMF does not include SM N2 information about the PDU session to avoid establishing radio resources in the target RAN. If the SMF notifies that the UE can only reach for regulatory priority service, the SMF does not contain any SM N2 information about the PDU session for the unregulated priority service to avoid the establishment of radio resources in the target RAN.

The SMF sends the Nsmf_PDUSession_UpdateSMContext response without including CN tunnel information in the AMF for the PDU session to be released and then releases the PDU session in a separate procedure as defined in Section 4.3.4.

8. The AMF supervises the Nsmf_PDUSession_UpdateSMContext response message in the associated SMF. The lowest value of the maximum delay indication for the PDU session that is a candidate for handover provides the maximum time the AMF waits for an Nsmf_PDUSession_UpdateSMContext response message before continuing with the N2 handover procedure. When the maximum wait time expires or all Nsmf_PDUSession_UpdateSMContext response messages are received, the AMF continues the N2 handover procedure (handover request message in step 9).

The delay value for each PDU session is configured locally in AMF and is implementation dependent.

9. From T-AMF to T-RAN: Handover request (Source to Target transparent container, MM N2 information, SM N2 information list, handover restriction list).

The T-AMF determines the T-RAN based on the target ID. The T-AMF may assign a valid 5G-GUTI for the UE in AMF and target TAI.

Source to Target Transparent containers are delivered as they are received from S-RAN. The MM N2 information includes, for example, security information and a handover restriction list when available in the T-AMF.

SM N2 information list includes SM N2. The SM N2 information list may include SM N2 information received from the SMFs for the T-RAN in Nsmf_PDUSession_UpdateSMContext response messages received within the allowed maximum delay supervised by the T-AMF mentioned in step 8. SM N2 information also indicates which QoS flows are subject to data transfer.

If available in the target AMF, a handover restriction list is sent.

10. T-RAN to T-AMF: Acknowledgment of handover request (Target to Source transparent container, SM N2 response list, PDU sessions failed to be setup list, T-RAN SM N3 forwarding information list).

The Target to Source transparent container includes a UE container with an access layer part and a NAS part. The UE container is transparently sent to the UE via the T-AMF, S-AMF and S-RAN.

The information provided to the S-RAN also includes a list of PDU session IDs where the PDU session indicates a setup failure and the reason for the failure (SMF decision, SMF response too late or T-RAN decision).

The SM N2 response list includes the SM N2 response indicating the PDU session ID and the PDU session ID and the N2 handover request for the PDU session, for each SM N2 information received and PDU session approved by the SMF for N2 handover. Includes whether it has been approved by the T-RAN. For each PDU session approved by the T-RAN for N2 handover, the SM N2 response includes the T-RAN's N3 UP address and tunnel ID.

The T-RAN SM N3 forwarding information list is included for each PDU session approved by the T-RAN and, if necessary, at least one QoS flow subject, N3 UP address and T- for data forwarding to receive the forwarded data. Contains the tunnel ID of the RAN.

[Conditional] T-AMF to SMF: Nsmf_PDUSession_UpdateSMContext request (PDU session ID, cause).

If the Nsmf_PDUSession_UpdateSMContext response message arrives too late (see Step 8), or if an SMF-related PDU session is not accepted by the T-RAN, this message is sent to that SMF to indicate the N3 UP address to which the SMF is assigned and the tunnel ID of the selected UPF. Allow to deallocate. PDU sessions processed by the SMF are considered inactive and the handover attempt for that PDU session is terminated.

12a. From AMF to SMF: Nsmf_PDUSession_UpdateSMContext Request (PDU Session ID, SM N2 Response, T-RAN SM N3 Delivery Information List).

For each SM N2 response (included in the SM N2 response list) received from the T-RAN, the AMF sends the received SM N2 response to the SMF indicated by each PDU session ID.

If a new T-UPF is not selected, the SMF stores N3 tunnel information of the T-RAN from the SM N2 response if the N2 handover is approved by the T-RAN.

12b. [Conditional] SMF to T-UPF: N4 session modification request (T-RAN SM N3 forwarding information list, DL forwarding tunnel allocation indication for indirect delivery)

If the SMF selects the T-UPF in step 6a, the SMF updates the T-UPF by sending an N4 session modification request to the T-UPF and providing a list of T-RAN SM N3 delivery information.

If indirect delivery is applied based on the indication from the NG-RAN and the UPF is relocated, and the SMF decides to establish an indirect delivery tunnel to the same T-UPF, the SMF also sends a DL for indirect delivery in the N4 session modification request message. Ask the T-UPF to allocate the transport tunnel.

Indirect delivery may be performed via a different UPF than the T-UPF, in which case the SMF selects the T-UPF for indirect delivery.

12c. [Conditional] T-UPF to SMF: N4 Session Modification Response (T-UPF SM N3 Delivery Information List)

T-UPF allocates tunnel information and returns an N4 session modification response message to the SMF.

The T-UPF SM N3 forwarding information list includes a T-UPF N3 address and a T-UPF N3 tunnel identifier for forwarding data.

12d. [Conditional] SMF to S-UPF: N4 session modification request (T-RAN SM N3 forwarding information list or T-UPF SM N3 forwarding information list, instructions for allocating DL forwarding tunnel for indirect forwarding)

If the UPF is relocated, this message contains a T-UPF SM N3 delivery information list. If the UPF is not relocated, this message includes a list of T-RAN SM N3 forwarding information.

If indirect delivery is applied based on the indication from the NG-RAN, the SMF indicates to the S-UPF in the N-4 session modification request message to allocate a DL delivery tunnel for indirect delivery.

Indirect delivery may be performed via a different UPF than the S-UPF.

12e. [Conditional] S-UPF to SMF: N4 Session Modification Response (S-UPF SM N3 Delivery Information List)

The S-UPF allocates tunnel information and returns an N4 session establishment response message to the SMF.

The S-UPF SM N3 forwarding information list includes an S-UPF N3 address and an S-UPF N3 tunnel identifier for data transmission for both UL and DL.

12f. SMF to T-AMF: Nsmf_PDUSession_UpdateSMContext Response (N2 SM Information)

The SMF sends an Nsmf_PDUSession_UpdateSMContext response message to the T-AMF for each PDU session.

The SMF generates N2 SM information including DL forwarding tunnel information to be transmitted to the S-RAN by the AMF. SMF includes this information in the Nsmf_PDUSession_UpdateSMContext response. DL forwarding tunnel information may be one of the following information:

If direct delivery is applied, the SMF includes the T-RAN N3 delivery information received by the SMF in step 12a.

If the indirect forwarding tunnel is established in step 12b or 12d, the SMF includes T-UPF or S-UPF DL forwarding information including the N3 UP address and DL tunnel ID of the UPF.

The SMF starts an indirect data propagation timer that is used to release resources in the indirect data propagation tunnel.

13. [conditional] T-AMF to S-AMF: Namf_Communication_CreateUEContext response (N2 information, N2 SM information required for S-AMF to send handover command to S-RAN containing Target to Source transparent container) to be setup list, and N3 DL delivery information))

AMF supervises the Nsmf_PDUSession_UpdateSMContext response message in the relevant SMF. When the maximum wait time expires or all Nsmf_PDUSession_UpdateSMContext response messages are received, the T-AMF sends a Namf_Communication_CreateUEContext response to the S-AMF.

A target to source transport container is received from the T-RAN. N2 SM information is received from the SMF in step 12f.

FIG. 6 is a diagram illustrating execution phase in inter NG-RAN node N2-based handover according to an embodiment of the present invention. Providing AMF with UDM in this figure is not shown for simplicity.

1. From S-AMF to S-RAN: handover command (target to source transparent container, PDU sessions failed to be setup list, SM forwarding information list).

Target to Source Transparent containers are delivered as they are received from S-AMF.

The SM delivery information list includes a T-RAN SM N3 delivery information list for direct delivery or an S-UPF SM N3 delivery information list for indirect data delivery.

The S-RAN uses the indicated reasons for the PDU sessions failed to be setup list and the decision to fail the N2 handover procedure.

2. From S-RAN to UE: handover command (UE container).

The UE container is the UE portion of the Target to Source transparent container that is transparently transmitted from the T-RAN to the S-RAN via AMF and provided to the UE by the S-RAN.

3. The uplink packet is sent from the T-RAN to the T-UPF and UPF (PSA: PDU Session Anchor). Downlink packets are sent from the UPF (PSA) to the S-RAN via the S-UPF. The S-RAN must initiate the transmission of downlink data from the S-RAN to the T-RAN for the QoS flow requiring data forwarding. This can be either direct (step 3a) or indirect delivery (step 3b).

4. UE to T-RAN: handover confirm.

After the UE has successfully synchronized to the target cell, it sends a handover confirmation message to the T-RAN. Handover is considered successful by the UE by this message.

5. From T-RAN to T-AMF: Handover Notify.

Handover by this message is considered successful in the T-RAN.

6a. [Conditional] T-AMF to S-AMF: Namf_Communication_N2InfoNotify

The T-AMF notifies the S-AMF about the N2 handover notification received from the T-RAN by calling Namf_Communication_N2InfoNotify.

The timer of the S-AMF starts supervision when the resources of the S-RAN are released.

6b. [Conditional] From S-AMF to T-AMF: Namf_Communication_N2InfoNotify ACK.

The S-AMF acknowledges by sending a Namf_Communication_N2InfoNotify ACK to the T-AMF.

7a. [Conditional] T-AMF to SMF: Namf_EventExposure_Notify

The T-AMF invokes the Namf_EventExposure_Notify service operation when the detected LADN state (eg, "inside LADN area" or "outside LADN area") is different from the last notified LADN state. When an event is notified to the SMF, the last notified LADN state is updated to the detected LADN state.

7b. T-AMF to SMF: Nsmf_PDUSession_UpdateSMContext Request (Handover Complete indication for PDU Session ID).

For each PDU session, handover completion is sent to the SMF to indicate the success of the N2 handover.

T-AMF also uses Nudm_UECM_Registration to register itself with the UDM as a serving AMF.

8a. [Conditional] SMF to T-UPF (intermediate): request to modify N4 session

When a new T-UPF is inserted or an existing intermediate S-UPF is relocated, the SMF should send an N4 session modification request to the T-UPF indicating the DL AN tunnel information of the T-RAN.

8b. [Conditional] From T-UPF to SMF: N4 session fix response

The T-UPF sends an acknowledgment by sending an N4 Session Modification Response message to the SMF.

9a. [Conditional] S-UPF (Medium): Request to modify N4 session in SMF

If the UPF is not relocated, the SMF should send an N4 session modification request indicating the DL AN tunnel information of the T-RAN to the S-UPF.

9b. [Conditional] S-UPF: N4 session fix response to SMF

The S-UPF sends an acknowledgment by sending an N4 Session Modification Response message to the SMF.

10a. [Conditional] SMF to UPF (PSA): request to modify N4 session

For non-roaming or local breakout roaming scenarios, the SMF sends an N4 session modification request message to the PDU session anchors UPF, UPF (PSA), and the T-RAN's N3 AN tunnel information or T-RAN. Provides DL CN tunnel information of the UPF. A new T-UPF is inserted or an existing intermediate S-UPF is relocated. V (visited) -SMF operates Nsmf_PDUSession_Update request service towards H (Home) -SMF when an existing intermediate S-UPF terminating with N9 towards H-UPF (PDU session anchor) is relocated to the home routed roaming scenario. Call

If no T-UPF is inserted or no existing intermediate S-UPF is relocated, steps 10a and 10b are skipped.

10b. [Conditional] UPF (PSA) to SMF: N4 session modification response

UPF (PSA) sends an N4 session modification response message to the SMF. To aid the reordering function in the T-RAN, the UPF (PSA) sends one or more "end marker" packets to each QoS flow requiring reordering on the previous path immediately after switching the path. The source UPF sends an "end marker" packet to the source RAN. At this point, when a new T-UPF is inserted or an existing intermediate S-UPF is relocated, the UPF (PSA) starts sending downlink packets to the T-RAN via the T-UPF. In the home routed roaming scenario, the H-SMF responds with an Nsmf_PDUSession_Update response service operation when the H-UPF (PDU session anchor) is updated with the UL tunnel information of the T-UPF.

If there are multiple UPFs (PSAs), steps 10a and 10b are performed for each UPF (PSA).

11. From T-AMF to SMF: Nsmf_PDUSession_UpdateSMContext Response (PDU Session ID).

The SMF confirms receipt of the handover completion.

12. The UE may begin the mobility registration procedure.

Since the target AMF knows that this is a handover procedure, the target AMF performs only a subset of the registration procedure, in

particular steps

5, 6, and 10 for context transfer between the source AMF and the target AMF are skipped.

13a. [Conditional] SMF to S-UPF (intermediate): request to release N4 session

If there is a source intermediate UPF, the SMF sends an N4 session release request (cause of release) to the source UPF to start resource release after the seven-step timer or indirect data transfer timer expires. This message is also used to release the indirect data transfer resources of the S-UPF.

13b. SMF to S-UPF: N4 Session Release Response

The S-UPF acknowledges the release of resources using the N4 Session Release Response message.

Indirect data delivery also frees resources for indirect data delivery.

14a. AMF to S-RAN: UE context release command ().

After the timer in step 6a expires, the AMF sends a UE context release command.

14b. S-RAN to AMF: UE Context Release Complete ().

The source RAN releases resources associated with the UE and responds with a UE Context Release Complete () message.

15a. [Conditional] SMF to T-UPF: request to modify N4 session

If indirect delivery is applied and UPF is relocated, after the indirect data delivery timer expires, the SMF sends an N4 session modification request to the T-UPF to release the indirect data delivery resource.

15b. [Conditional] From T-UPF to SMF: N4 session fix response

The T-UPF acknowledges the release of the indirect data transfer resource via an N4 session modification response message.

LADNLADN 서비스 지원 및 지시 방법 How to Service and Instruction

1. The terminal may perform a registration procedure by sending a registration request message to the AMF. In this case, the AMF may be an AMF in which the DNN1 to which the terminal is subscribed is set. The DNN subscription information of the terminal may be provided / configured to the AMF by the UDM.

2. When the AMF approves the registration request of the terminal, the AMF may transmit a registration approval message. At this time, if the DNN1 to which the terminal is subscribed includes the LADN, the LADN information may be included in the registration approval message and transmitted. The LADN information may include a LADN service area (that is, an intersection area between the LADN service area and the recently registered area) and / or the LADN DNN where the LADN service is provided.

If the LADN information is updated, the AMF may provide the LADN information to the terminal through a UE configuration update message / procedure.

1-2. The SMF may subscribe to the UE mobility event notification for the LADN DNN. In this case, the AMF may notify the SMF of "UE Mobility Event Notification" if the UE is located in the LADN service area. In addition, the AMF may optionally notify the SMF of specific location information of the terminal.

To this end, the AMF may query / request the NG-RAN whether the UE exists at the UE location or region of interest. The NG-RAN may transmit, to the AMF, whether the UE exists in the region of interest and / or the current UE location information (or recently known UE location information with a time stamp) according to the inquiry / request.

Alternatively, the UE may transmit the location information of the UE, which has been set / stored in the AMF, directly to the SMF without such a request.

The AMF can determine whether the UE is located in the region of interest ('IN', 'OUT' or 'UNKOWN') as follows:

1) If you determine "IN":

When the UE is located inside the area of interest and the terminal is in a CM-CONNECTED state; or

The UE is located in a registration area included in the region of interest.

2) If you determine "OUT":

The UE is located outside the region of interest but the region of interest is located within an available registration area, and the UE is in CM-CONNECTED state; or

The UE is located in a registration area for which the region of interest is not valid.

3) If you determine "UNKOWN":

The UE is located within a valid area of interest, the area of interest does not include the entire area of registration, and the UE is in CM-IDLE state.

According to the determination result, the AMF may transmit a Namf_EventExposure_Notify message to the SMF.

Access to DNs via PDU sessions to LADNs is only available in certain LADN service areas. The LADN service area is a set of tracking areas. LADN is a service provided by the serving PLMN of the UE:

LADN service only applies to 3GPP access, not Home Routed.

-LADN DNNs require an explicit subscription to this DNN or a subscription to a wildcard DNN.

Whether the DNN corresponds to a LADN service is an attribute of the DNN.

The UE is configured to know whether the DNN is a LADN DNN.

LADN information (ie, LADN service area information and / or LADN DNN) is set in units of DNs in the AMF (ie, for each other UE accessing the same LADN). The established LADN service area is independent of other elements (eg, UE's registration area or UE subscription).

If LADN is not available in the TA in the AMF service area, AMF does not need to receive any LADN information for the DNN.

The LADN information is provided to the UE by the AMF during the registration procedure or the UE configuration update procedure. For each LADN DNN set up in the AMF, the corresponding LADN service area information includes a set of tracking areas belonging to the UE's current registration area (ie, the intersection of the LADN service area and the current registration area). AMF does not create a registration area according to the availability of LADN.

Therefore, since the LADN service area may include a TA (s) outside the registration area of the UE or an external area served by the AMF, the LADN service area information transmitted to the UE by the AMF is only a subset of the entire LADN service area. It may include.

When the UE performs a successful (re) registration procedure, the AMF is informed of the UE based on the local settings (eg, via OAM), UE location, and UE subscription information received from the UDM about the subscribed DNN. In the registration approval message, the LADN information for the LADN available to the UE in the corresponding registration area may be provided. During the subsequent registration update procedure, if the network does not provide LADN information for the DNN, the UE deletes any LADN information for that DNN.

If the LADN information for the UE is changed in 5GC, the AMF must update the LADN information to the UE through the UE configuration update / registration procedure.

Based on the LADN information in the UE, the UE takes the following actions:

a) When the UE is outside the LADN service area, the UE:

-Do not request to activate UP connection of PDU session to LADN DNN.

-Do not approve or change PDU sessions to LADN DNNs.

Unless the UE receives an explicit SM PDU Session Release Request message from the network, there is no need to release the existing PDU session for the LADN DNN.

b) When the UE is in the LADN service area, the UE:

Can request PDU session establishment / modification for LADN DNN.

A request may be made to activate an UP connection of an existing PDU session to a LADN DNN.

The SMF supporting the DNN is configured to determine whether the DNN is a LADN DNN. The SMF may subscribe to "UE mobility event notification" to provide the LAMF DNN to the AMF to report UE presence in the region of interest.

Based on the notification of the UE presence in the LADN service area (ie IN, OUT, UNKNOWN) notified by the AMF, the SMF takes the following actions based on the operator's policy:

a) When notifying the SMF that a UE exists in the LADN service area, the SMF shall:

Immediate release of the PDU session; or

-Disable the user plane connection to the PDU session and maintain downlink data notifications while maintaining the PDU session. The SMF may release the PDU session later.

b) When the SMF is notified that the LADN service area exists, the SMF must:

Verifying that downlink data notification is available;

When the SMF receives downlink data or data notification from the UPF, it triggers a network trigger service request procedure for the LADN PDU session to activate the UP connection.

c) When notifying the SMF that the UE presence in the LADN service area is UNKNOWN, the SMF may:

Verifying that downlink data notification is available;

According to the prior art, the PDU session establishment for receiving the LADN service may be triggered / started / started from the UE, but it is not known when the PDU session establishment of the UE will specifically occur. That is, even though the network is ready to provide LADN service, utilization of LADN service usage is not available because the UE is not forced to establish a PDU session (and / or when it is specifically defined when to initiate). Can be low.

Therefore, the present specification proposes a method for increasing the utilization of a specific service (particularly, LADN service) desired by the operator.

The present invention proposed below may be composed of a combination of at least one or more of the following embodiments, and each individual embodiment will be described below for convenience of description.

10 is a flowchart illustrating a LADN indication method for a UE according to an embodiment of the present invention. Detailed description of the operation of the terminal in this flowchart will be described using reference numerals of FIG. 25.

0. The UE (for example, the terminal Y100) displays a setting screen for setting whether the user allows the LADN connection of the UE Y100 (or whether the user wants the LADN connection) on the display unit Y151. can do. In addition, in the setting screen, the UE Y100 may receive input from the user through the user input unit Y173 whether the LADN connection of the UE Y100 is allowed (or whether the LADN connection is desired). When the display unit Y151 is implemented as a touch screen and functions as a user input unit Y173 and provides an output interface between the UE Y100 and the user, the display unit Y151 may display a touch input or the like on a setting screen. By the user, whether to allow the LADN connection of the UE (Y100) (or whether the LADN connection is desired) can be input. The UE Y100 may store a setting input from the user (that is, whether to allow LADN connection (or whether a LADN connection is desired)) in the memory Y130. The setting of whether to allow the LADN connection (or whether the user wants to connect to the LADN) may be maintained until the user's input is changed (that is, the permission is changed to disallowed or disallowed). . And while the setting for whether to allow LADN access (or whether to want LADN access) is maintained, when entering the LADN service area, the UE Y100 determines whether to generate a PDU session of the LADN according to the setting. Can be. That is, when the UE Y100 is set to not allow (or do not want to connect to) LADN of the UE Y100 by the user, the UE Y100 may establish a PDU session of the LADN even when entering the LADN service area. The PDU session establishment procedure for generating may not be performed. On the other hand, if the UE Y100 is configured to allow LADN access of the UE Y100 from the user (or want LADN access), the UE Y100 creates a PDU session of the LADN when entering the LADN service area. A PDU session establishment procedure may be performed. A specific operation embodiment of the UE Y100 relating to this will be described later in detail with reference to FIG. 11.

1. The UE (Y100) may acquire LADN information (LADN DNN and / or LADN DNN service area information for each LADN DNN) provided by the serving network node / AMF through an attach / registration process on the network. have. Optionally, the UE Y100 may be serviced by establishing a general PDU session (eg, an IMS PDU session for voice service and / or an Internet PDU session for Internet service).

The UE Y100 displays a map on the display unit Y151 (for example, displays a map with a predetermined radius based on the location of the user / terminal Y100), and uses the boundary line and / or the color to display the map. This possible service area can be displayed on a map for the user to recognize. In this case, the UE (Y100) may provide brief information about the service provided by the corresponding LADN when the LADN capable service area displayed on the map or when the LADN capable service area is selected by the user (for example, a touch input). Can also be displayed. Specific operation embodiments of the UE Y100 will be described later in detail with reference to FIGS. 12 and 13.

2 ~ 4. Through interactions between network nodes, the LADN DN / AF may perform various operations for determining the location of the terminal Y100.

If not roaming, the LADN DN / AF may attempt to locate a UE (Y100) / user subscribed to receive the LADN service provided by the operator. In case of roaming, the LADN DN / AF does not determine the location of all roaming terminals (Y100), but is a UE (Y100) / user subscribed to receive LADN service provided by a visited network while roaming according to a roaming agreement. The location can be determined based on the recognition number for.

If the UE Y100 enters a LADN-capable service area where access is allowed in advance, the UE Y100 enters a specific status screen (for example, an icon, a notification window, etc.) to inform the user that the LADN has entered the service area. ) Can be displayed on the display unit Y151.

Such a status screen (for example, an icon, a notification window, etc.) may have a different shape, display type (for example, blinking), color, and the like compared to a status screen indicating whether the LADN is being accessed. In addition, depending on the number of LADNs to which the UE Y100 can connect in the region, the shape, display form (for example, blinking), color, and the like of a state display (for example, an icon and a notification window) may be different.

In addition, when there are a plurality of LADNs that can be connected to the UE Y100, each status screen (eg, an icon, a notification window, etc.) may be displayed on the display unit Y151 according to the number of LADNs that can be connected. In this case, the UE Y100 may display the display unit Y151 in the form of a list for each LADN (or services that can be provided by each LADN). In addition, the UE Y100 may receive a selection as to which LADN a PDU session wants to be connected to (ie, which LADN is desired to be serviced) from the user through the user input unit Y173. For example, activation (ie acknowledgment of PDU session setup for that LADN from the user's point of view) / inactivity (ie, corresponding LADN from the user's point of view) based on input from the user via user input (Y173). PDU session setup rejection for) may be selected.

In addition, the UE Y100 displays a map on the display unit Y151 (for example, displays a map with a constant radius based on the location of the user / UE Y100), and the boundary line and / or color on the map. Using LA, it is possible to indicate the service area where the user can recognize the LADN. In this case, the UE (Y100) may provide brief information about the service provided by the corresponding LADN when the LADN capable service area displayed on the map or when the LADN capable service area is selected by the user (for example, a touch input). Can also be displayed.

Specific operation embodiments of the UE Y100 according to the embodiments described above will be described later in detail with reference to FIGS. 14 to 17.

5. The network node may request the UE Y100 to set up / establish a PDU session based on the acquired location information of the UE Y100 (in particular, when the UE Y100 enters the LADN service area). Specific embodiments for this may be divided into the following 5a, 5b and 5c according to the network operation subject, at least one of the following embodiments can be combined and applied.

5a. As an embodiment, using the device triggering method, the LADN DN / AF may request the terminal Y100 to set up / establish a PDU session for starting a corresponding service. In more detail, the DN / AF may transmit an application trigger request message for triggering a specific application / service provision to the UE Y100 through NEF and AMF. In this case, the terminal Y100 may start a procedure for requesting PDU session setup / establishment without user interaction based on the LADN access permission information that is set in advance. In this case, a pop-up window for receiving an explicit input for actual access / service start from the user may be provided / viewed through the terminal Y100 according to the operator's setting / policy. For example, a pop-up window asking whether to agree to provide / use a specific service or a Uniform Resource Locator (URL) address for connecting to a service may be provided. Such explicit input may be received at the application layer via a LADN application (or app).

The UE Y100 may display a pop-up window on the display unit Y151 so that a user may receive an input for actually accessing the LADN or starting the service of the LADN. At this time, upon input of the user's approval in the pop-up window, the UE Y100 displays the display unit Y151 together with a notification message indicating that actual connection to the LADN requesting setup / establishment of the corresponding PDU session and / or service provided by the LADN is started. can do. In this case, the UE Y100 may also display information on the LADN (and / or services provided by the LADN) requesting the PDU session setup / establishment in a popup window.

If the UE (Y100) starts the LADN service from the LADN DN / AF even if it receives an input of not allowing the LADN connection (or does not want the LADN connection) by the user in the setting screen of step 0. If the PDU session setup / establishment request is requested, the UE Y100 may display the above popup window. In this case, the terminal Y100 may be restricted by using information and / or precautions (eg, using such LADN service) for a LADN (and / or a service provided by the LADN) requesting a PDU session setup / establishment in a popup window. Can be displayed together). In this case, the terminal Y100 may also display the billing information together in a popup window when accessing the LADN (or the start of a service provided by the LADN) requesting PDU session setup / establishment. In this case, the charging information may be charging information limited to the corresponding service or may be comprehensive charging information linked to other services.

Upon receiving the PDU session setup / establishment request from the LADN DN / AF, the UE Y100 may notify the notification window D100 as shown in FIG. 14 or the notification message E100 as shown in FIG. 15 to notify that a request for a specific LADN service has been received. ) Can be displayed on the display unit Y151.

As described above, the notification window D100 may display information on the LADN service (for example, the LADN service name, the provided LADN service (s), and / or billing information of the provided LADN service of the provided LADN). Can be. In addition, a button D101 may be displayed in the notification window D100 for selecting a user from the user (ie, allowing the corresponding LADN service). Here, the button D101 may be an allow (or active) button and a block (or inactive) button as shown in FIG. 14, or may be a toggle button or a flip-flop button. It is merely an example and may be displayed as another type of button for user selection.

And / or, a hyperlink E101 may be displayed for selection from a user who wants to receive the corresponding LADN service in the notification message E100 (ie, permits the corresponding LADN service). When the hyperlink E101 is selected (for example, when the hyperlink E101 is touched by the user), a website for the corresponding LADN service service is displayed on the display unit Y151 and the user can select the corresponding LADN service. You can also choose whether to allow on your website. Alternatively, such a hyperlink E101 may not be displayed, and when the UE Y100 transmits a predetermined number (or text determined on the notification message E100) as a response message in response to the notification message E100, the response message. In addition, the user may transmit a message to the LADN service server that the user allows the corresponding LADN service.

5b. Or 5c. In one embodiment, the network node may determine / initiate / trigger setup / establishment / use / creation of a LADN PDU session, and if necessary, transmit a LADN PDU session creation / establishment / setup instruction to the UE (Y100). By doing so, we propose a method to increase the utilization of LADN service. Such determination / initiation / triggering / instruction may be performed in PCF, NEF, AF and / or AMF, and based on one or more of the following information, LADN PDU session setup / establishment / use / creation determination / initiation / Triggering / Instructions can be:

Whether to allow / disallow LADN DN access according to the subscriber information of the UE Y100 / user;

Whether to allow / disallow the use of the LADN service per UE (Y100) / user;

Location and / or LADN service area information of the UE Y100 / user; And / or

Roaming status / whether and / or policies for roaming UE Y100 / user, etc.

Such information may be conveyed together when the LADN information is conveyed in step 1 or separately / independently in other steps to the network node.

The specific method of transmitting the network indication (LADN PDU session setup / establishment / use / generation indication) to the UE Y100 may vary depending on an optional path, a network operating entity, and / or a message type, such as 5b / 5c.

In embodiment 5b, if LADN PDU session setup / establishment / use / creation is determined, the PCF may send a LADN PDU initiation message for initiation / triggering of LADN PDU session setup / establishment / use / creation to AMF. have. In this case, the AMF may transmit a paging / notification message including the LADN setup flag / bit / information indicating the LADN PDU session setup / establishment / use / creation to the UE Y100 to the UE Y100. In this case, the LADN PDU initiation message and / or paging / notification message may include information regarding a reason for the LADN PDU session setup / establishment / use / generation.

In Example 5c, when the LADN PDU session setup / establishment / use / creation is determined, the PCF sends an LADN PDU initiation message for initiation / triggering of the LADN PDU session setup / establishment / use / creation to the AMF via the SMF. Can be transmitted. In this case, the LADN PDU initiation message may include 'request level / priority' information. Here, the 'request level / priority' information refers to priority information for setting up / establishing / using / creating a LADN PDU session. In this case, the AMF is a NAS command / message containing LADN setup flags / bits / information and / or 'request level / priority' information instructing the AMF to setup / establish / use / create a LADN PDU session to the UE (Y100). May be transmitted to the UE Y100.

In particular, in the above embodiments, the information delivered to the UE Y100 for setup / establishment / use / creation of a LADN PDU session may include information indicating setup / establishment / use / creation of a UE-initiated PDU session and setup / It may contain information needed to establish / use / create (e.g. priority / importance / force level information such as 'shall / should / may' for a specific DNN, setup / build / use / create indication, etc.). . In addition, the information may additionally explicitly / implicitly indicate that the setup / establishment / use / creation of a UE-initiated PDU session is indicated for some LADN service.

Between

steps

5 and 6, a step for receiving explicit input of the above-described UE Y100 / user may be inserted / included.

6. The UE (Y100) and the network node may perform a procedure for setting up / establishing / using / creating a UE-initiated PDU session, and since the procedure is initiated according to the network instruction, the UE (Y100) and the network node may perform the procedure at the network node such as checking the LADN subscriber information. Some steps that need to be performed may be omitted.

The UE Y100 may display a status screen (eg, an icon, a notification window, etc.) indicating whether the UE Y100 is currently accessing the LADN on the display unit Y151. When the PDN session creation request of the LADN is approved by the network node, and successfully creating the PDU session of the LADN, the UE Y100 displays a status screen (for example, an icon or a notification window) indicating that the LADN is connecting to the LADN. Y151). On the other hand, when the PDU session of the LADN is released, the UE Y100 may display a status screen (eg, an icon, a notification window, etc.) indicating that the LADN is not connected to the display unit Y151.

After a successful PDU session establishment, an essential message such as a warning message or the like may be transmitted to the UE Y100 in the network LADN DN / AF, and the popup message may be displayed on the display unit Y151.

When the UE Y100 starts to provide a specific LADN service (ie, when connected to the LADN), the UE Y100 is accessing the LADN (or receiving the LADN service) on the display unit Y151 status bar as shown in FIG. 16. An icon F101 may be displayed to indicate that. In this case, the displayed icon F101 may have a different shape from the icon displayed when entering the service area capable of LADN service as described above, or may have the same shape but different display forms. For example, the icon blinks when the user enters the LADN service area, but the icon may be displayed without blinking when accessing the LADN. In addition, as described above, depending on the number of LADNs to which the UE Y100 is connected, the shape of the status display (for example, an icon, a notification window, etc.), a display type / method / status (for example, blinking), color, etc. It may be different.

In addition, as shown in FIG. 17 (for example, such a status window may be displayed by the user dragging from the upper state bar toward the lower side), the one currently provided by the UE Y100 in the G100. The service name G101 for the above LADN service may be displayed. In this case, the LADN service name may be different from the LADN service name display that may be provided at the location of the UE Y100 and color and / or display form. For example, the service name text for the LADN service that can be provided at the location of the UE Y100 is displayed blinking, but the service name text for the LADN service currently provided by the UE Y100 is displayed without blinking. May be At this time, each service name G101 may have a function of a toggle button. For example, each time a service name is selected, the state of allowing / blocking of the corresponding LADN service may be switched. And / or, the color of the service name text may be changed according to the allow / block state so that the user can check the allow / block state. For example, in the allowed state, the service name text may be displayed in black, but in the blocked state, the corresponding service name text may be displayed in gray / red.

When the PDU session creation request of the LADN is rejected by the network node because the PDU session creation request of the LADN fails, the UE Y100 displays an alert window (or a notification message) indicating that the LADN connection has failed (or has been rejected). It can be displayed in the unit Y151.

If the AMF determines that the UE (Y100) has left the established LADN service area, the AMF notifies that the UE (Y100) has left the LADN service area, and the UE (Y100) notifies the user that the user has left the LADN service area. The window (or a notification message) may be displayed on the display unit Y151. And / or the UE Y100 may recognize its own location to recognize the departure of the LADN service area, and then display a notification window (or a notification message) for notifying the user on the display unit Y151.

In addition, when the SMF decides to release or deactivate the LADN session, the SMF may notify the UE Y100 that the LADN session has been released or deactivated via the AMF. After recognizing that the LADN session is released or deactivated, the UE Y100 may display a notification window (or a notification message) for notifying the user on the display unit Y151. In this case, the terminal Y100 may distinguish between the LADN session release and the deactivation, and may display a notification window (or a notification message) on the display unit 151 for notifying the user of two cases in different forms.

If the prior art procedure is deactivated, the deactivation of the PDU session may not be delivered to the UE Y100 explicitly as a NAS message informing of the release of the PDU session, and a specific radio period in the AS layer of the UE Y100 may be used. Recognize release of resources. Accordingly, the NAS layer of the terminal Y100 may recognize a temporary PDU session deactivation implicitly without an explicit NAS message after reporting and receiving an event regarding a specific radio duration resource release received from the AS layer. Even in this case, since the terminal Y100 may distinguish between the LADN session release and the deactivation, the display unit Y151 may display a notification window (or a notification message) for notifying the user of the two cases in different forms.

If the PDU session creation request of the LADN is rejected by the network node, the UE Y100 leaves the LADN coverage area, and / or the LADN session is released or deactivated, the UE Y100 In order to notify the user of such a situation, the notification window D100 as shown in FIG. 14 and / or the notification message E100 as shown in FIG. 15 may be displayed on the display unit Y151. At this time, when the request for creating a PDU session of the LADN is rejected by the network node, when the UE Y100 leaves the LADN service area, when the LADN session is released, and / or the LADN session is deactivated. In order to allow the user to distinguish the case, the contents of the message displayed on the notification window D100 or the notification message E100 may be different.

And / or, when leaving the LADN service area, or when the LADN session is released (released) or deactivated (deactivation), the icon or LADN service name for the corresponding LADN may disappear in the status window (G100) of FIG. have.

And / or when the UE Y100 moves to an area where no LADN service is provided, or when the LADN session for all LADNs to which the UE Y100 is connecting is released or deactivated. In the status window G100 as shown in FIG. 17, the icon or LADN service name for all LADNs may disappear. In addition, in the status bar of FIG. 16, the icon F101 indicating that the LADN is being accessed (or being provided with the LADN service) may disappear.

11 is a diagram illustrating a display unit screen of the UE according to an embodiment of the present invention. In particular, this figure illustrates a screen of the display unit Y151 of the UE Y100 performing step 0 in the flowchart of FIG. 10.

As shown in FIG. 11A, in the setting screen of the UE Y100, a setting menu A001 for enabling / disabling (or allowing) a service (eg, LADN service) is displayed on the display unit Y151. In addition, a button A002 for selecting activation / deactivation from the user may be displayed. The button A002 may be a toggle button or a flip-flop button as shown in FIG. 11, or may be an allow (or active) button and a block (or inactive) button. This is only an example and may be displayed as other / various types of buttons for user selection. In addition to the service, the setting screen may also display a setting menu for allowing (activating) such as WiFi, Bluetooth, and mobile data, and may be displayed in each setting menu such as WiFi, Bluetooth, and mobile data. A button for selecting whether to activate or deactivate the user may be displayed.

When the service setting menu A001 is selected from the user instead of the button A002 input (for example, a touch other than the button A002), the setting screen of the UE Y100 is shown in FIG. 11 (b). Can be moved / changed together. In this case, as shown in FIG. 11B, a setting screen A100 for setting whether to allow LADN access individually for each service (or whether LADN access is desired) may be displayed on the display unit Y151. have. One or more LADN service names (A101) are displayed on the setting screen (A100), and each LADN service may include a button (A102) for selecting whether or not to allow access to the corresponding LADN service from the user. The setting screen A100 may be displayed on the display unit Y151. The button A102 may be a toggle button or a flip-flop button as shown in FIG. 11, or may be an allow (or active) button and a block (or inactive) button. This is only an example and may be displayed as other / various types of buttons for user selection.

On the above setting screen A100, a preset LADN service in the UE Y100 may be displayed according to a policy of an operator to which the UE Y100 is subscribed. Alternatively, the LADN service that the UE Y100 has experienced so far may be displayed. Alternatively, if an application (App: application) is provided for each LADN service, the LADN service for the App stored in the UE Y100 may be displayed. As such, when an App is provided for each LADN service, the setting screen A100 may be individually / differentially / independently configured for each App. In this case, the user may select whether to allow / block access of the corresponding LADN service through the button A102 on the setting screen A100 for each app.

Alternatively, after completing the attach / registration process to the network as shown in step 1 of FIG. 10, the LADN service provided by the serving network node / AMF may also be displayed on the configuration screen A100.

12 and 13 illustrate screens of a display unit of a UE according to an embodiment of the present invention. In particular, this figure illustrates a screen of the display unit Y151 of the UE Y100 performing step 1 in the flowchart of FIG. 10.

When the service application is executed by the user input or when the UE Y100 moves to the LADN serviceable area, the UE Y100 may display a map on the display unit Y151 as shown in FIG. 12. In this case, the UE Y100 may display the location of the user (that is, the location of the UE Y100) B104 on the map. In addition, the UE Y100 moves the map displayed on the display unit Y151 in a direction of up, down, left, right, etc. according to a user's touch and / or drag input on the display unit Y151. It can be moved, and the scale of the map can be changed big or small. In addition, the UE Y100 may display the service area (that is, the area where the LADN service is provided) B101, B102, and B103 of the LADN on a map. At this time, the color of the service area may be displayed differently for each LADN service.

In addition, as shown in FIG. 12, while the UE Y100 displays a map on the display unit Y151, whether the user individually allows LADN access for one or more LADN services available in the region where the UE Y100 is located. A setting screen for setting (or whether or not a LADN connection is desired) may be displayed on the display unit Y151. One or more LADN service names (B201) are displayed on the setting screen, and a button (B202) is displayed on the display unit (Y151) for receiving (selection) whether or not to allow access to the corresponding LADN service for each LADN service. Can be. Button B202 may be a toggle button or a flip-flop button as shown in FIG. 12, or may be an allow (or active) button and a block (or inactive) button. This is merely an example and may be displayed as another type of button for user selection.

In addition, as shown in FIG. 13, when the UE Y100 receives a service area of a specific LADN from a user (for example, receives a touch input from the user), information about the LADN service provided in the selected LADN service area (eg, For example, the LADN service name, the provided LADN service (s), billing information of the provided LADN service of the provided LADN, etc.) C100 may be displayed. In addition, a button C101 for selecting a user from a user who wants to receive LADN service provided in the selected LADN service area (that is, whether to allow the corresponding LADN service) may be displayed. Here, the button C101 may be an allow (or active) button and a block (or inactive) button as shown in FIG. 13, or may be a toggle button or a flip-flop button. It is merely an example and may be displayed as another type of button for user selection.

14 and 15 illustrate screens of a display unit of a UE according to an embodiment of the present invention. In particular, this figure illustrates a screen of the display unit Y151 of the UE Y100 performing steps 2 to 4 in the flowchart of FIG. 10.

As the UE Y100 moves into a service area capable of a specific LADN service, as shown in FIG. 14, the UE Y100 displays a notification window indicating that the service area has entered a service area capable of specific LADN service (see FIG. 14). D100) may be displayed. In this case, the notification window D100 may display information about the LADN service (for example, the LADN service name, the provided LADN service (s), and / or billing information of the provided LADN service of the provided LADN). . And / or, a button D101 may be displayed for selecting from the user whether the user wants to receive the corresponding LADN service in the notification window D100 (that is, whether to allow the corresponding LADN service). Here, the button D101 may be an allow (or active) button and a block (or inactive) button as shown in FIG. 14, or may be a toggle button or a flip-flop button. This is merely an example and may be displayed as other / various types of buttons for user selection.

And / or, when the UE (Y100) moves to enter a service area capable of a specific LADN service, as shown in FIG. 15, the UE (Y100) enters a service area capable of specific LADN service on the display unit (Y151). Short message service (SMS) notification message (E100) for notifying may also be displayed. That is, the UE Y100 may display the notification message E100 received from the SMS server on the display unit Y151. In this case, the notification message E100 may display information about the LADN service (for example, the LADN service name, the provided LADN service (s), and billing information of the provided LADN service of the provided LADN). In this case, the notification message E100 may display a hyperlink E101 for receiving input / selection from the user as to whether the corresponding LADN service is desired (ie, allowing the corresponding LADN service). When the hyperlink E101 is selected (for example, when the hyperlink E101 is touched by the user), a website for the corresponding LADN service service is displayed on the display unit Y151 and the user can select the corresponding LADN service. You can also choose whether to allow it on the website. Alternatively, the hyperlink E101 may not be displayed, and when the user transmits a predetermined number (or predetermined message on the notification message E100) as a response message in response to the notification message E100, the user corresponds to the corresponding message. A message indicating that the LADN service is allowed may be sent to the LADN service server.

16 and 17 illustrate screens of a display unit of a UE according to an embodiment of the present invention. In particular, this figure illustrates a screen of the display unit Y151 of the UE Y100 performing steps 2 to 4 in the flowchart of FIG. 10.

As shown in FIG. 16, when the UE Y100 moves to a service area in which a specific LADN service is available, an icon F101 indicating that the LADN service area has been entered in the status bar of the display unit Y151 is displayed. Can be displayed. In this case, the icon F101 may have a different shape from the icon displayed when the LADN is being connected (that is, receiving LADN service). Alternatively, the display may be the same shape but different display forms. For example, when the user enters the LADN service area, the icon blinks, but the icon does not blink when connected to LADN. In addition, as described above, the shape, display form (eg, blinking), and / or color of the status display (eg, icon, notification window, etc.) according to the number of LADNs that can be connected at the location of the UE Y100. Etc. may differ.

Alternatively, as shown in FIG. 17, the current UE may be displayed in the status window (for example, such a status window may be displayed by a user dragging from the top (or bottom) status bar to the bottom (or top)) G100. The service name G101 for one or more LADN services that may be provided at the location of Y100 may be displayed. At this time, each service name G101 may have a function of a toggle button. For example, each time a service name is selected, the state of allowing / blocking of the corresponding LADN service may be switched. And / or, the color of the service name text may be changed according to the allow / block state so that the user can check the allow / block state. For example, the service name text may be displayed in black in the allowed state, but the service name text may be displayed in light gray in the blocked state.

Since the LADN service that can be provided by the UE Y100 may change as the UE Y100 moves, the LADN icon or LADN service name G101 displayed in the status window G100 of FIG. 17 may be changed to the UE Y100. Depending on the position of may be displayed or disappear in the status window (H100).

And / or, the UE Y100 displays a map on the display unit Y151 as described above (for example, displays a map with a constant radius based on the location of the user / terminal Y100), and on the map. The border and / or color may be used to indicate a service area where a LADN is possible so that the user can recognize it. In this case, the UE (Y100) may provide brief information about the service provided by the corresponding LADN when the LADN capable service area displayed on the map or when the LADN capable service area is selected by the user (for example, a touch input). Can also be displayed.

Hereinafter, the UE positioning method based on the interaction with the NEF and the UDM and the detailed operation of the UDM, as well as the UE positioning method based on the interaction with the NEF and the PCF described above will be described.

In the following FIG. 18, the NEF service operation information flow embodiment of Section 4.15.3.2.3 in TS23.502 (v15.1.0) may be merged.

1. A requester (AS (LADN DN / AF) in this embodiment) may subscribe to one or more monitoring events by sending a Nnef_EventExposure_Subscribe request.

Event reporting information defines the type of reporting requested (eg, one-time reporting, periodic reporting or event based reporting on monitoring events). If the reporting event subscription is approved by the NEF, the NEF may record / store the association between the event trigger and the requester ID.

The AS (LADN DN / AF) may subscribe to location related events (network service operation, location detection event of a specific terminal) with the NEF to determine the location of the UE to provide the LADN service. In this process, not only the UE but also UEs subscribed to a specific PLMN (for example, all inbound romers from a specific PLMN having a roaming agreement if the roaming subscriber wants to know the location of a roaming subscriber). Subscribe to an event (network service operation). For example, when an AS subscribes to an event (network service operation) with NEF, the parameter can be informed by including a parameter in a specific message (for example, a Nnef_EventExposure_Subscribe request) that can explicitly / implicitly identify / identify the PLMN. (For example, use wildcard to include specific PLMN (identification) information, such as * @ PLMN-A).

In addition, the AS (LADN DN / AF) may explicitly or implicitly inform the information indicating that the purpose of subscribing to the event is to provide a LADN service. For example, the AS (LADN DN / AF) may include this information as a separate parameter in a specific message (for example, a Nnef_EventExposure_Subscribe request) or implicit information (eg, for a terminal's recognizer) to confirm an event. For example, UE @ LADN_PLMN-A or * @ LADN_PLMN-A may be included. The purpose of including this information is to inform the result of the event by selecting the UE that is available / licensed for the LADN service based on the LADN subscriber information in a later procedure.

2. The NEF may subscribe the received event to the UDM by sending a Nudm_EventExposure_Subscribe request.

If the reporting event subscription is authorized by the UDM, the UDM / AMF may record / store the association between the event trigger and the requestor ID. If not, the UDM may continue to indicate failure in step 4.

The NEF finds and contacts / accesses the UDM including the subscriber information of the UE received from the AS. That is, the NEF may contact / connect to the ULM of the HPLMN based on the information received from the AS, and as described in step 1, location related events (network service operation, in this case) for all UEs of a specific UE and / or a specific PLMN. A specific terminal location event) can be subscribed to. The parameters included / required in the event subscription are as described above.

3a. [Conditional] If AMF support is required for the requested event (eg, monitoring of loss of connectivity), the UDM may send a Namf_EventExposure_Subscribe to the AMF serving the requested user.

The UDM checks the LADN service authorization for the requested UE (s) based on the subscriber information. The UDM may subscribe to a location-related event (network service operation, in this case, a location event of a specific terminal) with a serving AMF to locate the selected UE (s).

Since LADN may be a service provided only in a 3GPP access network according to the assumption of the prior art, the UDM may additionally identify an access network registered and perform location-related events (network service operation, in this case, a location detection event of a specific UE) by serving AMF ) Can join. For example, in the case of a terminal previously registered in a non-3GPP access network, the UDM does not need to subscribe to a location related event with the current serving AMF. Subsequently, when the UE recognizes that it is registered with the 3GPP access network, the UDM may subscribe to a location related event (network service operation, in this case, a location event of a specific UE) with the serving AMF. To this end, the UDM can maintain / manage a specific record (relative to the access network to which the terminal is registered) (the registration status record of the terminal). That is, the UDM does not need to subscribe to an event with the serving AMF currently registered to the non-3GPP access terminal, but if the terminal is registered with the 3GPP access network later, information for initiating / performing an event subscription with the serving AMF is recorded / You need to keep it.

3b. [Conditional] AMF acknowledges the execution of Namf_EventExposure_Subscribe.

4. The UDM acknowledges the execution of Nudm_EventExposure_Subscribe.

5. The NEF acknowledges the execution of Nnef_EventExposure_Subscribe to the requester who initiated the request.

6a. The UDM detects the occurrence of an event (based on the event) and sends an event report via the Nudm_EventExposure_Notify message to the NEF that previously subscribed to the event.

6b. [Conditional-event dependent] AMF detects the occurrence of an event and sends an event report via the Namf_EventExposure_Notify message to the NEF that previously subscribed to the event.

7. The NEF forwards the reporting event received by Nudm_EventExposure_Notify and / or Namf_EventExposure_Notify to the AS.

19 is a flowchart illustrating a method of receiving a LADN service of a terminal according to an embodiment of the present invention. The above-described embodiments and descriptions with respect to this flowchart may be applied in the same or similar manner, and redundant descriptions are omitted.

First, the terminal may display a setting screen for receiving whether to set whether the terminal is allowed to access the LADN service (S1910).

Next, the terminal may receive a setting regarding whether to allow access to the LADN service through the setting screen and store the input setting (S1920).

Next, the terminal may receive the LADN information for the LADN service (S1930). The LADN information at this time may include LADN service area information and LADN DNN information.

Next, the terminal may determine whether to establish a PDU session for providing the LADN service based on the stored configuration and / or location information of the terminal (S1940).

If the establishment of the PDU session is determined in step S1940, the UE may receive a predetermined message from the AMF including a request for establishing the PDU session (S1950). Next, the terminal may transmit a request message for initiating establishment of the PDU session to the network node (S1960). Here, the case where the establishment of the PDU session is determined may include a case where the stored setting indicates the access permission to the LADN service and / or the location of the terminal is inside the LADN service area included in the LADN service area information. have. Further, the network node may be AMF, PCF, NEF and / or DN / AF.

Receiving the predetermined message, step S1950, receiving an application trigger request message for triggering a LADN service from the DN / AF as a predetermined message through the AMF; It may include. Or, in step S1950 of receiving the preset message, when the AMF receives a LADN PDU initiation message requesting initiation of PDU session establishment from the PCF, receiving a paging message as a preset message from the AMF. It may include. In step S1950 of receiving the preset message, if the AMF receives an initiation message requesting PDU session establishment initiation from the PCF, and if the initiation message includes priority information of PDU session establishment, The method may include receiving a NAS message including the priority information as a set message.

If the PDU session for the LADN service is successfully established as the request message is approved by the network node in step S1960, the terminal may display an indicator indicating that the UE is currently accessing the LADN service. In this case, the indicator may correspond to an icon, a notification window, a message, and / or a pop-up window of a predefined state, color, and / or shape to indicate that the LADN service is being accessed. In addition, the indicator may be displayed in the status bar (top or hidden in the display unit) to inform the user of the current setting status of the terminal.

On the contrary, if the establishment of the PDU session is not determined in step S1940 and / or the establishment of the PDU session for the LADN service fails because the request message is rejected by the network node, the UE may determine that the LADN service is not established. A notification window may be displayed indicating that the connection has failed (S1970).

20 is a block diagram of a terminal receiving a LADN service according to an embodiment of the present invention. The description of FIG. 19 may be applied in the same or similar manner with respect to the flowchart, and a redundant description will be omitted.

The terminal 2000 determines whether the LADN service setting screen display configuration / unit 2010, LADN service access permission is allowed and stored configuration / unit 2020, configuration / unit 2030 receiving LADN information, and whether to establish a PDU session. Configuration / unit 2040. Further, for the case where it is determined by the 2040 configuration / unit to establish a PDU session, the terminal 2000 initiates the establishment of the reception configuration / unit 2050 of the predetermined message including the PDU session establishment request, the establishment of the PDU session. May include a send configuration / unit 2060 of the request message. In addition, for the case where it is determined by the 2070 configuration / unit not to establish a PDU session, the terminal 2000 may include a configuration / unit 2070 displaying a notification window indicating that the connection of the LADN service has failed.

2010 to 2070 components / units of the terminal 2000 may be components / units configured to perform steps S1910 to S1970 of FIG. 19, respectively. Each configuration / unit may be configured as a hardware configuration / component, and may correspond to at least one configuration / unit (for example, a processor, a memory, and / or a communication module or a combination thereof) described below with reference to FIGS. 21 and 23. have.

본 발명이 적용될 수 있는 장치 일반General apparatus to which the present invention can be applied

Referring to FIG. 21, a wireless communication system includes a network node 2110 and a plurality of terminals (UEs) 2120.

The network node 2110 includes a processor 2111, a memory 2112, and a communication module 2113. The processor 2111 may implement the functions, processes, embodiments, and / or methods proposed above, and may be described in the present specification with the network node 2110 for convenience of description. Layers of the wired / wireless interface protocol may be implemented by the processor 2111. The memory 2112 is connected to the processor 2111 and stores various information for driving the processor 2111. The communication module 2113 is connected to the processor 2111 to transmit and / or receive wired / wireless signals. As an example of the network node 2110, a base station, an MME, an HSS, an SGW, a PGW, an application server, and the like may correspond thereto. In particular, when the network node 2110 is a base station, the communication module 2113 may include a radio frequency unit (RF) for transmitting / receiving a radio signal.

The terminal 2120 includes a processor 2121, a memory 2122, and a communication module (or RF unit) 2123. The processor 2121 may implement the functions, processes, embodiments, and / or methods proposed above, and may be described with the terminal 2120 for convenience of description. Layers of the air interface protocol may be implemented by the processor 2121. The memory 2122 is connected to the processor 2121 and stores various information for driving the processor 2121. The communication module 2123 is connected to the processor 2121 to transmit and / or receive a radio signal.

The

memories

2112 and 2122 may be inside or outside the

processors

2111 and 2121, and may be connected to the

processors

2111 and 2121 by various well-known means. In addition, the network node 2110 (if the base station) and / or the terminal 2120 may have a single antenna (multiple antenna) or multiple antenna (multiple antenna).

In particular, FIG. 22 is a diagram illustrating the terminal of FIG. 21 in more detail.

Referring to FIG. 22, a terminal may include a processor (or a digital signal processor (DSP) 2210, an RF module (or RF unit) 2235, and a power management module 2205). ), Antenna 2240, battery 2255, display 2215, keypad 2220, memory 2230, SIM card Subscriber Identification Module card) 2225 (this configuration is optional), a speaker 2245 and a microphone 2250. The terminal may also include a single antenna or multiple antennas. Can be.

The processor 2210 implements the functions, processes, and / or methods proposed above. The layer of the air interface protocol may be implemented by the processor 2210.

The memory 2230 is connected to the processor 2210 and stores information related to the operation of the processor 2210. The memory 2230 may be inside or outside the processor 2210 and may be connected to the processor 2210 by various well-known means.

The user enters command information, such as a telephone number, for example by pressing (or touching) a button on keypad 2220 or by voice activation using microphone 2250. The processor 2210 receives the command information, processes the telephone number, and performs a proper function. Operational data may be extracted from the SIM card 2225 or the memory 2230. In addition, the processor 2210 may display command information or driving information on the display 2215 for the user's knowledge and convenience.

The RF module 2235 is connected to the processor 2210 to transmit and / or receive an RF signal. The processor 2210 passes command information to the RF module 2235 to transmit, for example, a radio signal constituting voice communication data to initiate communication. The RF module 2235 is composed of a receiver and a transmitter for receiving and transmitting a radio signal. The antenna 2240 functions to transmit and receive a radio signal. Upon receiving the wireless signal, the RF module 2235 may forward the signal and convert the signal to baseband for processing by the processor 2210. The processed signal may be converted into audible or readable information output through the speaker 2245.

The mobile terminal (or terminal, UE) described in the present specification includes a mobile phone, a smart phone, a laptop computer, a digital broadcasting terminal, a personal digital assistant (PDA), a portable multimedia player (PMP), navigation, Slate PCs, tablet PCs, ultrabooks, wearable devices, such as smartwatches, glass glasses, head mounted displays )) May be included. Furthermore, it may be used for controlling at least one device in an IoT (Internet of Things) environment or a smart greenhouse.

However, it will be readily apparent to those skilled in the art that the configuration according to the embodiments described herein may also be applied to fixed terminals such as digital TVs, desktop computers, digital signages, etc., except when applicable only to mobile terminals. will be.

The mobile terminal Y100 is a transceiver Y110, a processor Y120, a memory Y130, a sensing unit Y140, an output unit Y150, an interface unit Y160, an input unit Y170, and a power supply unit Y190. And the like. The components shown in this figure are not essential to implementing a mobile terminal, so the mobile terminal described herein may have more or fewer components than those listed above.

The transceiver Y110 is one that enables wireless communication between the mobile terminal Y100 and the wireless communication system, between the mobile terminal Y100 and another mobile terminal Y100, or between the mobile terminal Y100 and an external server. It may include more than one module. In addition, the transceiver Y110 may include one or more modules for connecting the mobile terminal Y100 to one or more networks.

The transceiver Y110 may include at least one of a broadcast receiving module Y111, a mobile communication module Y112, a wireless internet module Y113, a short range communication module Y114, and a location information module Y115. .

The input unit Y170 may include a camera Y171 or an image input unit for inputting an image signal, a microphone Y172 for inputting an audio signal, an audio input unit, or a user input unit Y173 for receiving information from a user. , Touch keys, mechanical keys, and the like. The voice data or the image data collected by the input unit Y170 may be analyzed and processed by the user's control command.

The sensing unit Y140 may include one or more sensors for sensing at least one of information in the mobile terminal, surrounding environment information surrounding the mobile terminal, and user information. For example, the sensing unit Y140 may include a proximity sensor 1410, an illumination sensor 1420, an illumination sensor, a touch sensor, an acceleration sensor, a magnetic sensor, and gravity. G-sensor, Gyroscope Sensor, Motion Sensor, RGB Sensor, Infrared Sensor, Infrared Sensor, Finger Scan Sensor, Ultrasonic Sensor Optical sensors (e.g. cameras (see 1710)), microphones (see 1720), battery gauges, environmental sensors (e.g. barometers, hygrometers, thermometers, radiation detection sensors, Thermal sensors, gas sensors, etc.), chemical sensors (eg, electronic noses, healthcare sensors, biometric sensors, etc.). Meanwhile, the mobile terminal disclosed herein may use a combination of information sensed by at least two or more of these sensors.

The output unit Y150 is used to generate an output related to sight, hearing, or tactile sense, and includes at least one of a display unit Y151, a sound output module Y152, a hap tip module Y153, and an optical output unit Y154. can do. The display unit Y151 may form a layer structure or an integrated structure with the touch sensor, thereby implementing a touch screen. The touch screen may function as a user input unit Y173 that provides an input interface between the mobile terminal Y100 and the user, and may also provide an output interface between the mobile terminal Y100 and the user.

The interface unit Y160 serves as a path to various types of external devices connected to the mobile terminal Y100. The interface unit Y160 may connect a device equipped with a wired / wireless headset port, an external charger port, a wired / wireless data port, a memory card port, and an identification module. It may include at least one of a port, an audio input / output (I / O) port, a video input / output (I / O) port, and an earphone port. The mobile terminal Y100 may perform appropriate control related to the connected external device in response to the connection of the external device to the interface unit Y160.

In addition, the memory Y130 stores data supporting various functions of the mobile terminal Y100. The memory Y130 may store a plurality of application programs or applications that are driven in the mobile terminal Y100, data for operating the mobile terminal Y100, and instructions. At least some of these applications may be downloaded from an external server via wireless communication. In addition, at least some of these application programs may exist on the mobile terminal Y100 from the time of shipment for basic functions (for example, a call forwarding, a calling function, a message receiving, and a calling function) of the mobile terminal Y100. The application program may be stored in the memory Y130 and installed on the mobile terminal Y100 to be driven by the processor Y120 to perform an operation (or function) of the mobile terminal.

The processor Y120 generally controls the overall operation of the mobile terminal Y100 in addition to the operation related to the application program. The processor Y120 may provide or process information or a function appropriate to a user by processing signals, data, information, etc. input or output through the above-described components, or by running an application program stored in the memory Y130.

In addition, the processor Y120 may control at least some of the above-described components in order to drive an application program stored in the memory Y130. In addition, the processor Y120 may operate at least two or more of the components included in the mobile terminal Y100 in combination with each other to drive the application program.

The power supply unit Y190 receives power from an external power source and an internal power source under the control of the processor Y120 to supply power to each component included in the mobile terminal Y100. The power supply unit Y190 includes a battery, and the battery may be a built-in battery or a replaceable battery.

At least some of the components may operate in cooperation with each other to implement an operation, control, or control method of the mobile terminal according to various embodiments described below. In addition, the operation, control, or control method of the mobile terminal may be implemented on the mobile terminal by driving at least one application program stored in the memory Y130.

Hereinafter, the components listed above will be described in more detail with reference to FIG. 1 before looking at various embodiments implemented through the mobile terminal Y100 described above.

First, referring to the transceiver Y110, the broadcast reception module Y111 of the transceiver Y110 receives a broadcast signal and / or broadcast related information from an external broadcast management server through a broadcast channel. The broadcast channel may include a satellite channel and a terrestrial channel. Two or more broadcast reception modules may be provided to the mobile terminal Y100 for simultaneous broadcast reception or broadcast channel switching for at least two broadcast channels.

The mobile communication module Y112 may include technical standards or communication methods (for example, Global System for Mobile communication (GSM), Code Division Multi Access (CDMA), Code Division Multi Access 2000 (CDMA2000), and EV). Enhanced Voice-Data Optimized or Enhanced Voice-Data Only (DO), Wideband CDMA (WCDMA), High Speed Downlink Packet Access (HSDPA), High Speed Uplink Packet Access (HSUPA), Long Term Evolution (LTE), LTE-A It transmits and receives wireless signals with at least one of a base station, an external terminal, and a server on a mobile communication network constructed according to Long Term Evolution-Advanced (3GPP) and 3GPP NR (New Radio access technology).

The wireless signal may include various types of data according to transmission and reception of a voice call signal, a video call call signal, or a text / multimedia message.

The wireless internet module Y113 refers to a module for wireless internet access and may be built in or external to the mobile terminal Y100. The wireless internet module Y113 is configured to transmit and receive wireless signals in a communication network according to wireless internet technologies.

Examples of wireless Internet technologies include Wireless LAN (WLAN), Wireless-Fidelity (Wi-Fi), Wireless Fidelity (Wi-Fi) Direct, Digital Living Network Alliance (DLNA), Wireless Broadband (WiBro), and WiMAX (World). Interoperability for Microwave Access (HSDPA), High Speed Downlink Packet Access (HSDPA), High Speed Uplink Packet Access (HSUPA), Long Term Evolution (LTE), Long Term Evolution-Advanced (LTE-A), 3GPP NR, and the like. The internet module Y113 transmits and receives data according to at least one wireless internet technology in a range including the internet technologies not listed above.

In view of the fact that the wireless Internet access by WibroWiBro, HSDPA, HSUPA, GSM, CDMA, WCDMA, LTE, LTE-A, 3GPP NR, etc. is made through a mobile communication network, the wireless Internet performing wireless internet access through the mobile communication network The module Y113 may be understood as a kind of the mobile communication module Y112.

The short range communication module (Y114) is for short range communication, and includes Bluetooth ™, Radio Frequency Identification (RFID), Infrared Data Association (IrDA), Ultra Wideband (UWB), ZigBee, NFC (Near Field Communication), at least one of Wi-Fi (Wireless-Fidelity), Wi-Fi Direct, Wireless USB (Wireless Universal Serial Bus) technology can be used to support short-range communication. Such a short-range communication module Y114 is provided between a mobile terminal Y100 and a wireless communication system, between a mobile terminal Y100 and another mobile terminal Y100, or through a wireless area network. ) And a wireless communication between a network in which another mobile terminal 1000 or an external server is located. The short range wireless communication network may be short range wireless personal area networks.

Here, the other mobile terminal (Y100) is a wearable device (e.g., smartwatch, smart glasses, etc.) capable of exchanging (or interworking) data with the mobile terminal (Y100) according to the present invention. (smart glass), neckband, head mounted display (HMD). The short range communication module Y114 may detect (or recognize) a wearable device that can communicate with the mobile terminal Y100 around the mobile terminal Y100. Further, when the detected wearable device is a device that is authenticated to communicate with the mobile terminal Y100 according to the present invention, the processor Y120 may include at least a portion of data processed by the mobile terminal Y100 in the short-range communication module ( Y114) may be transmitted to the wearable device. Therefore, the user of the wearable device can use the data processed by the mobile terminal Y100 through the wearable device. For example, according to this, when the user receives a phone call from the mobile terminal Y100, the user performs a phone call through the wearable device, or if a message is received from the mobile terminal Y100, the user receives the received call through the wearable device. It is possible to check the message.

Furthermore, screen mirroring is performed with the local area TV or a display inside a vehicle through the short range communication module Y114, and a corresponding function is performed based on, for example, a MirrorLink or Miracast standard. In addition, it is also possible to directly control the display inside the TV or the vehicle by using the mobile terminal Y100.

The location information module Y115 is a module for obtaining the location (or current location) of the mobile terminal, and a representative example thereof is a Global Positioning System (GPS) module or a Wireless Fidelity (WiFi) module. For example, when the mobile terminal utilizes the GPS module, the mobile terminal may acquire the location of the mobile terminal using a signal transmitted from a GPS satellite. As another example, when the mobile terminal utilizes the Wi-Fi module, the mobile terminal may acquire the location of the mobile terminal based on information of the wireless access point (AP) transmitting or receiving the Wi-Fi module and the wireless signal. If necessary, the location information module Y115 may perform any function of other modules of the transceiver Y110 in order to alternately or additionally obtain data regarding the location of the mobile terminal. The location information module Y115 is a module used to obtain the location (or current location) of the mobile terminal, and is not limited to a module that directly calculates or obtains the location of the mobile terminal.

Each of the broadcast receiving module Y111, the mobile communication module Y112, the short range communication module Y114, and the location information module Y115 may be implemented as a separate module for performing a corresponding function, and the broadcast receiving module Y111, Functions corresponding to two or more of the mobile communication module Y112, the short range communication module Y114, and the location information module Y115 may be implemented by one module.

Next, the input unit Y170 is for inputting image information (or signal), audio information (or signal), data, or information input from a user, and for inputting image information, the mobile terminal Y100 is one. Alternatively, a plurality of cameras Y171 may be provided. The camera Y171 processes image frames such as still images or moving images obtained by the image sensor in the video call mode or the shooting mode. The processed image frame may be displayed on the display unit Y151 or stored in the memory Y130. Meanwhile, the plurality of cameras Y171 included in the mobile terminal Y100 may be arranged to form a matrix structure, and through the camera Y171 forming the matrix structure, various angles or focuses may be provided to the mobile terminal Y100. The plurality of pieces of image information may be input. In addition, the plurality of cameras Y171 may be arranged in a stereo structure to acquire a left image and a right image for implementing a stereoscopic image.

The microphone Y172 processes an external sound signal into electrical voice data. The processed voice data may be variously used according to a function (or an application program being executed) performed by the mobile terminal Y100. Meanwhile, various noise reduction algorithms may be implemented in the microphone Y172 to remove noise generated while receiving an external sound signal.

The user input unit Y173 is for receiving information from a user. When information is input through the user input unit Y173, the processor Y120 may control an operation of the mobile terminal Y100 to correspond to the input information. . The user input unit Y173 may be a mechanical input unit (or a mechanical key, for example, a button, a dome switch, a jog wheel, or the like located at the front or rear or side of the mobile terminal Y100). Jog switch, etc.) and touch input means. As an example, the touch input means may include a virtual key, a soft key, or a visual key displayed on the touch screen through a software process, or a portion other than the touch screen. It may be made of a touch key disposed in the. The virtual key or the visual key may be displayed on the touch screen while having various forms, for example, graphic, text, icon, video, or the like. It can be made of a combination of.

Meanwhile, the sensing unit Y140 senses at least one of information in the mobile terminal, surrounding environment information surrounding the mobile terminal, and user information, and generates a sensing signal corresponding thereto. The processor Y120 may control driving or operation of the mobile terminal Y100 or perform data processing, function, or operation related to an application program installed in the mobile terminal Y100 based on the sensing signal. Representative sensors among various sensors that may be included in the sensing unit Y140 will be described in more detail.

First, the proximity sensor Y141 refers to a sensor that detects the presence or absence of an object approaching a predetermined detection surface or an object present in the vicinity without using a mechanical contact by using an electromagnetic force or infrared rays. In the proximity sensor Y141, the proximity sensor Y141 may be disposed in an inner region of the mobile terminal covered by the touch screen described above or near the touch screen.

Examples of the proximity sensor Y141 include a transmission photoelectric sensor, a direct reflection photoelectric sensor, a mirror reflection photoelectric sensor, a high frequency oscillation proximity sensor, a capacitive proximity sensor, a magnetic proximity sensor, and an infrared proximity sensor. In the case where the touch screen is capacitive, the proximity sensor Y141 may be configured to detect the proximity of the object by the change of the electric field according to the proximity of the conductive object. In this case, the touch screen (or touch sensor) itself may be classified as a proximity sensor.

On the other hand, for convenience of explanation, an action of allowing the object to be recognized without being in contact with the touch screen so that the object is located on the touch screen is referred to as a "proximity touch", and the touch The act of actually touching an object on a screen is called a "contact touch." The position at which the object is in close proximity touch on the touch screen means a position where the object is perpendicular to the touch screen when the object is in close proximity touch. The proximity sensor Y141 may detect a proximity touch and a proximity touch pattern (for example, a proximity touch distance, a proximity touch direction, a proximity touch speed, a proximity touch time, a proximity touch position, and a proximity touch movement state). have. Meanwhile, the processor Y120 processes data (or information) corresponding to the proximity touch operation and the proximity touch pattern detected through the proximity sensor Y141 as described above, and further, provides visual information corresponding to the processed data. It can be output on the touch screen. Furthermore, the processor Y120 may control the mobile terminal Y100 to process different operations or data (or information) according to whether the touch on the same point on the touch screen is a proximity touch or a touch touch. .

The touch sensor detects a touch (or touch input) applied to the touch screen (or display unit Y151) using at least one of various touch methods such as a resistive film type, a capacitive type, an infrared type, an ultrasonic type, and a magnetic field type. do.

As an example, the touch sensor may be configured to convert a change in pressure applied to a specific portion of the touch screen or capacitance generated at the specific portion into an electrical input signal. The touch sensor may be configured to detect a position, an area, a pressure at the touch, a capacitance at the touch, and the like, when the touch object applying the touch on the touch screen is touched on the touch sensor. Here, the touch object is an object applying a touch to the touch sensor and may be, for example, a finger, a touch pen or a stylus pen, a pointer, or the like.

As such, when there is a touch input to the touch sensor, the corresponding signal (s) is sent to the touch controller. The touch controller processes the signal (s) and then sends the corresponding data to processor Y120. As a result, the processor Y120 may determine which area of the display unit Y151 is touched. Here, the touch controller may be a separate component from the processor Y120 or may be the processor Y120 itself.

Meanwhile, the processor Y120 may perform different control or may perform the same control according to the type of the touch object, which touches the touch screen (or a touch key provided in addition to the touch screen). Whether to perform different control or the same control according to the type of touch object may be determined according to the operation state of the mobile terminal Y100 or an application program being executed.

Meanwhile, the touch sensor and the proximity sensor described above may be independently or combined, and may be a short (or tap) touch, a long touch, a multi touch, a drag touch on a touch screen. ), Flick touch, pinch-in touch, pinch-out touch, swipe touch, hovering touch, etc. A touch can be sensed.

The ultrasonic sensor may recognize location information of a sensing object using ultrasonic waves. Meanwhile, the processor Y120 may calculate the position of the wave generation source based on information detected by the optical sensor and the plurality of ultrasonic sensors. The position of the wave source can be calculated using the property that the light is much faster than the ultrasonic wave, that is, the time that the light reaches the optical sensor is much faster than the time when the ultrasonic wave reaches the ultrasonic sensor. More specifically, the position of the wave generation source may be calculated using a time difference from the time when the ultrasonic wave reaches the light as the reference signal.

On the other hand, the camera Y171, which has been described as the configuration of the input unit Y170, includes at least one of a camera sensor (eg, CCD, CMOS, etc.), a photo sensor (or an image sensor), and a laser sensor.

The camera Y171 and the laser sensor may be combined with each other to detect a touch of a sensing object on a 3D stereoscopic image. The photo sensor may be stacked on the display element, which is configured to scan the movement of the sensing object in proximity to the touch screen. More specifically, the photo sensor mounts a photo diode and a transistor (TR) in a row / column and scans contents mounted on the photo sensor by using an electrical signal that varies according to the amount of light applied to the photo diode. That is, the photo sensor calculates coordinates of the sensing object according to the amount of light change, and thus, the position information of the sensing object can be obtained.

The display unit Y151 displays (outputs) information processed by the mobile terminal Y100. For example, the display unit Y151 may display execution screen information of an application program driven by the mobile terminal Y100, or UI (User Interface) or GUI (Graphic User Interface) information according to the execution screen information. .

In addition, the display unit Y151 may be configured as a stereoscopic display unit for displaying a stereoscopic image.

The stereoscopic display unit may be a three-dimensional display method such as a stereoscopic method (glasses method), an auto stereoscopic method (glasses-free method), a projection method (holographic method).

The sound output module Y152 may output audio data received from the transceiver Y110 or stored in the memory Y130 in a call signal reception, a call mode or a recording mode, a voice recognition mode, a broadcast reception mode, and the like. The sound output module Y152 may also output a sound signal related to a function (for example, a call signal reception sound and a message reception sound) performed in the mobile terminal Y100. The sound output module Y152 may include a receiver, a speaker, a buzzer, and the like.

The haptic module Y153 generates various tactile effects that a user can feel. A representative example of the tactile effect generated by the haptic module Y153 may be vibration. The intensity and pattern of vibration generated in the haptic module Y153 may be controlled by user selection or processor setting. For example, the haptic module Y153 may output different synthesized vibrations or sequentially output them.

In addition to vibration, the haptic module (Y153), in addition to the vibration, the pin array vertically moving with respect to the contact skin surface, the blowing force or suction force of the air through the injection or inlet, grazing to the skin surface, contact of the electrode (electrode), electrostatic force, etc. Various tactile effects can be generated, such as effects by the endothermic and the reproduction of a sense of cold using the elements capable of endotherm or heat generation.

The haptic module Y153 may not only deliver a tactile effect through direct contact, but also may allow a user to feel the tactile effect through a muscle sense such as a finger or an arm. Two or more haptic modules Y153 may be provided according to a configuration aspect of the mobile terminal Y100.

The light output unit Y154 outputs a signal for notifying occurrence of an event by using light of a light source of the mobile terminal Y100. Examples of events generated in the mobile terminal Y100 may include message reception, call signal reception, missed call, alarm, schedule notification, email reception, and information reception through an application.

The signal output from the light output unit Y154 is implemented as the mobile terminal emits light of a single color or a plurality of colors to the front or the rear. The signal output may be terminated by the mobile terminal detecting the user's event confirmation.

The interface unit Y160 serves as a path with all external devices connected to the mobile terminal Y100. The interface unit Y160 receives data from an external device, receives power, transfers the power to each component inside the mobile terminal Y100, or transmits data inside the mobile terminal Y100 to an external device. For example, a port connecting a device equipped with a wired / wireless headset port, an external charger port, a wired / wireless data port, a memory card port, and an identification module. The port, an audio input / output (I / O) port, a video input / output (I / O) port, an earphone port, and the like may be included in the interface unit Y160.

On the other hand, the identification module is a chip that stores a variety of information for authenticating the usage rights of the mobile terminal (Y100), a user identification module (UIM), subscriber identity module (SIM), universal user authentication And a universal subscriber identity module (USIM). A device equipped with an identification module (hereinafter referred to as an 'identification device') may be manufactured in the form of a smart card. Therefore, the identification device may be connected to the terminal Y100 through the interface unit Y160.

In addition, the interface unit Y160 may be a passage for supplying power from the cradle to the mobile terminal Y100 when the mobile terminal Y100 is connected to an external cradle, or inputted from the cradle by a user. Various command signals may be a passage through which the mobile terminal Y100 is transmitted. Various command signals or power input from the cradle may operate as signals for recognizing that the mobile terminal Y100 is correctly mounted on the cradle.

The memory Y130 may store a program for operating the processor Y120, and may temporarily store input / output data (for example, a phone book, a message, a still image, a video, etc.). The memory Y130 may store data relating to various patterns of vibration and sound output when a touch input on the touch screen is performed.

The memory Y130 may be a flash memory type, a hard disk type, a solid state disk type, an SSD type, a silicon disk drive type, or a multimedia card micro type. ), Card-type memory (e.g., SD or XD memory), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read It may include at least one type of storage medium of -only memory (PROM), programmable read-only memory (PROM), magnetic memory, magnetic disk and optical disk. The mobile terminal Y100 may be operated in connection with a web storage that performs a storage function of the memory Y130 on the Internet.

On the other hand, as described above, the processor (Y120) controls the operation related to the application program, and generally the overall operation of the mobile terminal (Y100). For example, if the state of the mobile terminal satisfies a set condition, the processor Y120 may execute or release a lock state that restricts input of a user's control command to applications.

In addition, the processor Y120 may perform control and processing related to voice call, data communication, video call, or the like, or may perform pattern recognition processing for recognizing handwriting input or drawing input performed on a touch screen as text and images, respectively. Can be. Further, the processor Y120 may control any one or a plurality of components described above in order to implement various embodiments described below on the mobile terminal Y100 according to the present invention.

The power supply unit Y190 receives an external power source and an internal power source under the control of the processor Y120 to supply power for operation of each component. The power supply unit Y190 includes a battery, and the battery may be a built-in battery configured to be rechargeable, and may be detachably coupled to the terminal body for charging.

In addition, the power supply unit Y190 may include a connection port, and the connection port may be configured as an example of the interface Y160 to which an external charger for supplying power for charging the battery is electrically connected.

As another example, the power supply unit Y190 may be configured to charge the battery in a wireless manner without using the connection port. In this case, the power supply unit Y190 may use at least one of an inductive coupling based on a magnetic induction phenomenon or a magnetic resonance coupling based on an electromagnetic resonance phenomenon from an external wireless power transmitter. Power can be delivered.

Meanwhile, various embodiments of the present disclosure may be implemented in a recording medium readable by a computer or a similar device using, for example, software, hardware, or a combination thereof.

On the other hand, the mobile terminal can be extended to a wearable device that can be worn on the body beyond the user mainly holding in the hand. Such wearable devices include a smart watch, a smart glass, a head mounted display (HMD), and the like. Hereinafter, examples of the mobile terminal extended to the wearable device will be described.

The wearable device may be configured to exchange (or interlock) data with another mobile terminal Y100. The short range communication module Y114 may detect (or recognize) a wearable device that can communicate around the mobile terminal Y100. Further, when the detected wearable device is a device authorized to communicate with the mobile terminal Y100, the processor Y120 may wear at least a portion of data processed by the mobile terminal Y100 through the short range communication module Y114. Can be sent to. Therefore, the user may use data processed by the mobile terminal Y100 through the wearable device. For example, when a call is received by the mobile terminal Y100, a phone call may be performed through the wearable device, or when the message is received by the mobile terminal Y100, the received message may be confirmed through the wearable device. .

In the above, embodiments related to a control method that can be implemented in the mobile terminal configured as described above have been described with reference to the accompanying drawings. It is apparent to those skilled in the art that the present invention can be embodied in other specific forms without departing from the spirit and essential features of the present invention.

The present invention described above can be embodied as computer readable codes on a medium in which a program is recorded. The computer-readable medium includes all kinds of recording devices in which data that can be read by a computer system is stored. Examples of computer-readable media include hard disk drives (HDDs), solid state disks (SSDs), silicon disk drives (SDDs), ROMs, RAMs, CD-ROMs, magnetic tapes, floppy disks, optical data storage devices, and the like. This also includes implementations in the form of carrier waves (eg, transmission over the Internet). The computer may also include a processor Y120 of the terminal. Accordingly, the above detailed description should not be construed as limiting in all aspects and should be considered as illustrative. The scope of the invention should be determined by reasonable interpretation of the appended claims, and all changes within the equivalent scope of the invention are included in the scope of the invention.

The embodiments described above are the components and features of the present invention are combined in a predetermined form. Each component or feature is to be considered optional unless stated otherwise. Each component or feature may be embodied in a form that is not combined with other components or features. It is also possible to combine some of the components and / or features to form an embodiment of the invention. The order of the operations described in the embodiments of the present invention may be changed. Some components or features of one embodiment may be included in another embodiment or may be replaced with corresponding components or features of another embodiment. It is obvious that the claims may be combined to form an embodiment by combining claims that do not have an explicit citation relationship in the claims or as new claims by post-application correction.

Embodiments according to the present invention may be implemented by various means, for example, hardware, firmware, software, or a combination thereof. In the case of a hardware implementation, an embodiment of the present invention may include one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), FPGAs ( field programmable gate arrays), processors, controllers, microcontrollers, microprocessors, and the like.

In the case of implementation by firmware or software, an embodiment of the present invention may be implemented in the form of a module, procedure, function, etc. that performs the functions or operations described above. The software code may be stored in memory and driven by the processor. The memory may be located inside or outside the processor, and may exchange data with the processor by various known means.

In the present specification, 'A and / or B' may mean at least one of A and / or B.

It will be apparent to those skilled in the art that the present invention may be embodied in other specific forms without departing from the essential features of the present invention. Accordingly, the above detailed description should not be construed as limiting in all aspects and should be considered as illustrative. The scope of the invention should be determined by reasonable interpretation of the appended claims, and all changes within the equivalent scope of the invention are included in the scope of the invention.

Although the present invention has been described with reference to the example applied to the 3GPP LTE / LTE-A / NR (5G) system, it is possible to apply to various wireless communication systems in addition to the 3GPP LTE / LTE-A / NR (5G) system.

Claims

In the method of receiving a local access data network (LADN) service of a terminal in a wireless communication system,

Displaying a setting screen for setting whether the terminal permits access to the LADN service;

Receiving a setting regarding whether to allow access to the LADN service through the setting screen, and storing the input setting;

Receiving LADN information for the LADN service, wherein the LADN information includes LADN service area information and LADN data network name (DNN) information; And

Determining whether to establish a packet data unit (PDU) session for providing the LADN service based on the stored configuration and / or location information of the terminal; Including,

If the establishment of the PDU session is determined:

Receiving a predetermined message from an access and mobility management function (AMF) including a request for establishing the PDU session; And

Sending a request message to a network node to initiate establishment of the PDU session; Further comprising, LADN service receiving method.
The method of claim 1,

If the establishment of the PDU session is determined,

Wherein the stored setting indicates access permission to the LADN service, and / or the location of the terminal is inside a LADN service area included in the LADN service area information.
The method of claim 2,

The network node is the AMF, PCF (Policy Control function), Network Exposure Function (NEF) and / or Data Network (DN) / Application Function (DN), LADN service receiving method.
The method of claim 3, wherein

Receiving the preset message,

Receiving an application trigger request message for triggering the LADN service from the DN / AF via the AMF as the predetermined message; Including, LADN service receiving method.
The method of claim 3, wherein

Receiving the preset message,

Receiving a paging message from the AMF as the predetermined message when the AMF receives a LADN PDU initiation message requesting initiation of the PDU session establishment from the PCF; Including, LADN service receiving method.
The method of claim 3, wherein

Receiving the preset message,

If the AMF receives an initiation message requesting the PDU session establishment initiation from the PCF, and the initiation message includes the priority information of the PDU session establishment, the AMF as the predetermined message from the AMF. Receiving a Non-Access Stratum (NAS) message including priority information; Including, LADN service receiving method.
The method according to any one of claims 4 to 6,

Displaying an indicator indicating that the terminal is currently accessing the LADN service when the PDU session for the LADN service is successfully established as the request message is approved by the network node; Further comprising, LADN service receiving method.
The method of claim 7, wherein

The indicator corresponds to an icon, a notification window, a message, and / or a pop-up window of a predefined state, color and / or shape to indicate that the LADN service is being accessed.
The method of claim 8,

The indicator is displayed in the status bar for informing the user of the current configuration of the terminal, LADN service receiving method.
The method of claim 9,

If the establishment of the PDU session is not determined and / or the request message is rejected by the network node, and the establishment of the PDU session for the LADN service fails, a notification window indicating that the connection of the LADN service failed. Displaying; Further comprising, LADN service receiving method.
In a terminal receiving a Local Access Data Network (LADN) service in a wireless communication system,

A communication module for transmitting and receiving a signal;

A display unit for displaying a screen;

A memory for storing data; And

A processor controlling the communication module, the display unit, and the memory; Including,

The processor,

Displaying a setting screen on the display to receive the setting of whether the terminal permits access to the LADN service;

Receives a setting regarding whether to allow access to the LADN service through the setting screen, stores the input setting in the memory,

Receive LADN information for the LADN service,

The LADN information includes LADN service area information and LADN data network name (DNN) information.

It is determined whether to establish a packet data unit (PDU) session for providing the LADN service based on the stored configuration and / or location information of the terminal.

If the establishment of the PDU session is determined:

Receive a preset message from the Access and Mobility Management Function (AMF) including the request for establishing the PDU session,

And a request message for initiating establishment of the PDU session to a network node.
The method of claim 11,

If the establishment of the PDU session is determined,

Wherein the stored setting indicates permission to access the LADN service, and / or the location of the terminal is inside a LADN service area included in the LADN service area information.
The method of claim 12,

The network node is the AMF, PCF (Policy Control function), Network Exposure Function (NEF) and / or Data Network (DN) / Application Function (AF).
The method of claim 13,

When the processor receives the preset message,

And receiving an application trigger request message for triggering the LADN service from the DN / AF through the AMF as the predetermined message.
The method of claim 13,

When the processor receives the preset message,

And when the AMF receives a LADN PDU Initiation message requesting initiation of the PDU session establishment from the PCF, receives a paging message as the predetermined message from the AMF.
The method of claim 13,

When the processor receives the preset message,

If the AMF receives an initiation message requesting the PDU session establishment initiation from the PCF, and the initiation message includes the priority information of the PDU session establishment, the AMF as the predetermined message from the AMF. A terminal for receiving a non-access stratum (NAS) message including priority information.
The method according to any one of claims 14 to 16,

If the PDU session for the LADN service is successfully established as the request message is approved by the network node, the processor displays, on the display, an indicator indicating that the terminal is currently accessing the LADN service. Terminal.
The method of claim 17,

The indicator corresponds to an icon, notification window, message, and / or pop-up window of a predefined state, color and / or shape to indicate that the LADN service is being accessed.
The method of claim 18,

The indicator is displayed in the status bar for informing the user of the current setting status of the terminal.
The method of claim 19,

If the establishment of the PDU session is not determined and / or the request message is rejected by the network node, the establishment of the PDU session for the LADN service fails, the processor fails to connect to the LADN service. And displaying a notification window on the display unit.