KR20180106998A - Communication system optimizing an registration area and registration method of the communication system - Google Patents

Abstract

The present invention relates to a communication system optimizing registration region, and a registration method in the communication system. According to one embodiment, a UE of the communication system, to register the communication system, performs the steps of: transmitting AN messages containing a registration type showing that the UE wants to perform an initial registration to an access network (AN); if receiving an identifier request message from an access and mobility management function (AMF) device selected by the access network, transmitting an identifier response message containing subscription concealed identifier (SUCI) to the AMF device; and receiving a registration approving message indicating that the registration request of the UE is approved from the AMF device.

Description

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a communication system for optimizing a registration area and a registration method in the communication system,

The present invention relates to a mobile communication network.

A Mobile Edge Computing (MEC) technique has been proposed to provide a low-latency data service in a user equipment (UE). The MEC technique is used to minimize the Round Trip Time (RTT) between the UE and the server providing the service requested by the UE. The MEC technique relates to a technique for locating a geographical location of a server close to a UE, as well as reducing the number of routing hops between the UE and the server.

The 5G mobile communication network requires that various services be provided to the UE via 5G network technology. Accordingly, the 5G mobile communication network also supports edge computing technology to provide improved quality of service over existing network schemes.

We propose a communication system that increases the efficiency of terminal and network operation by allocating optimal tracking area.

According to one embodiment, there is provided a method of registering with a user equipment (UE) in a communication system, comprising the steps of: registering, by an access network (AN), a registration type indicating that the UE desires to perform initial registration Transmitting an identifier response message including an SUCI (SUBSCRIPTION CONCEPTED IDENTIFIER) to the AMF device when receiving an identifier request message from an Access and Mobility Management Function (AMF) device selected by the access network; And receiving a registration grant message from the AMF device indicating that the registration request of the UE is approved.

A communication system according to an exemplary embodiment may allocate an optimal tracking area to increase the efficiency of a terminal and a network operation.

1 is a diagram for explaining a communication system based on a non-roaming reference structure according to an embodiment.
2 is a diagram illustrating a structure of a 5G communication system in a non-roaming case according to an embodiment.
3 is a diagram for explaining a communication system based on a roaming reference structure according to an embodiment.
4 is a diagram illustrating the principle of marking and classifying user plane traffic and mapping QoS flows to AN resources.
5 is a flowchart illustrating a registration procedure of a UE in a communication system according to an embodiment.
6 is a flow chart illustrating a procedure for establishing a UE Request PDU session in a communication system according to an embodiment based on a home route roaming scenario.
7 is a flowchart illustrating a registration procedure of a communication system according to an embodiment.
8 is a flow chart illustrating the establishment of a UE Request PDU session for non-roaming and roaming with local breakout according to one embodiment.

It is to be understood that the specific structural or functional descriptions of embodiments of the present invention disclosed herein are presented for the purpose of describing embodiments only in accordance with the concepts of the present invention, May be embodied in various forms and are not limited to the embodiments described herein.

Embodiments in accordance with the concepts of the present invention are capable of various modifications and may take various forms, so that the embodiments are illustrated in the drawings and described in detail herein. However, it is not intended to limit the embodiments according to the concepts of the present invention to the specific disclosure forms, but includes changes, equivalents, or alternatives falling within the spirit and scope of the present invention.

The terms first, second, or the like may be used to describe various elements, but the elements should not be limited by the terms. The terms may be named for the purpose of distinguishing one element from another, for example without departing from the scope of the right according to the concept of the present invention, the first element being referred to as the second element, Similarly, the second component may also be referred to as the first component.

It is to be understood that when an element is referred to as being "connected" or "connected" to another element, it may be directly connected or connected to the other element, . On the other hand, when an element is referred to as being "directly connected" or "directly connected" to another element, it should be understood that there are no other elements in between. Expressions that describe the relationship between components, for example, "between" and "immediately" or "directly adjacent to" should be interpreted as well.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. The singular expressions include plural expressions unless the context clearly dictates otherwise. In this specification, the terms " comprises ", or " having ", and the like, are used to specify one or more of the features, numbers, steps, operations, elements, But do not preclude the presence or addition of steps, operations, elements, parts, or combinations thereof.

Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. Terms such as those defined in commonly used dictionaries are to be interpreted as having a meaning consistent with the meaning of the context in the relevant art and, unless explicitly defined herein, are to be interpreted as ideal or overly formal Do not.

Hereinafter, embodiments will be described in detail with reference to the accompanying drawings. However, the scope of the patent application is not limited or limited by these embodiments. Like reference symbols in the drawings denote like elements.

The terms used in the present invention are as follows.

5G Access Network (5G-AN): may include an NG-RAN or non-3GPP access network connected to a 5G core network.

5G Core Network (5GC): Connected to a 5G access network.

5G QoS flow: Good granularity for QoS forwarding processing in 5G systems. All traffic mapped to the same 5G QoS flow can receive the same forwarding process (e.g., scheduling policy, queue management policy, rate shaping policy, RLC configuration, etc.). Providing different QoS forwarding processing may require separate 5G QoS flows.

5G QoS identifier: Can be used as a reference for specific QoS forwarding behavior (eg, packet loss rate, packet delay budget) to be provided in a 5G QoS flow, May be implemented in the access network by 5QI referencing node specific parameters that control the scheduling weights, tolerance threshold, queue management threshold, link layer protocol configuration, etc.).

5G system (5GS): 5G access network (AN), 5G core network and UE.

Network function: 3GPP adoption or definition processing function in the network with functional operation and 3GPP definition interfaces. Network functionality can be implemented in dedicated hardware, in network elements, in software instances running on dedicated hardware, or as virtualization features instantiated in the appropriate platform (for example, a cloud infrastructure).

Network instance: Information identifying the domain. The network instance may be used by the UPF device for routing and traffic detection in the case of different IP domains or overlapping IP addresses.

Network Slice: A logical network that provides specific network capabilities and network features.

The network slice interface is a collection of required resources (e.g., computation, storage, and networking resources) and network function instances that form the deployed network slice.

Protocol Data Unit Session (PDU Session): An association between a user equipment and a data network to provide PDU connectivity services.

Protocol Data Unit Session Type (PDU Session Type): It refers to the PDU session type and includes IPv4, IPv6, Ethernet, and so on.

(1) Standalone New Radio, (2) New Radio is an anchor with E-UTRA extensions, (3) Standalone E-UTRA, (4) E- UTRA is an anchor with New Radio extensions).

Service Data Flow Filter: A set of packet flow header parameter values / ranges used to identify one or more packet (IP or Ethernet) flows that make up the service data flow.

Service Data Flow Template: A collection of service data flow filters required by an application identifier or policy rule in a policy rule associated with an application detection filter, required to define a service data flow.

Uplink classifier: UPF function for diverting uplink traffic, based on filter rules provided by the SMF device, towards the data network.

The Session Management Function (SMF), the Access and Mobility Management Function (AMF), and the User Plane Function (UPF) described below are software functions, And may be installed or executed on each of a plurality of hardware.

Reference points in the communication system described below are defined as follows.

N1 is a reference point between the UE and the AMF device. N2 is a reference point between the (R) AN and the AMF device. N3 is a reference point between the (R) AN and the UPF device. N4 is a reference point between the SMF device and the UPF device. N6 is a reference point between the UPF and the data network. N9 is a reference point between two UPF devices.

The reference points described below may illustrate the interworking between NF services in the NFs. The following reference points can be implemented by corresponding NF service-based interfaces and specify their interaction as well as identified consumer NF services and producer NF services to implement specific system procedures Can be implemented.

N5 is a reference point between the PCF apparatus and the AF apparatus. N7 is a reference point between the SMF device and the PCF device. N24 is a reference point between the PCF device in the visited network and the PCF device in the home network. N8 is a reference point between the UDM device and the AMF device. N10 is a reference point between the UDM device and the SMF device. N11 is a reference point between the AMF device and the SMF device. N12 is a reference point between the AMF device and the AUSF device. N13 is a reference point between the UDM device and the AUSF device. N14 is a reference point between two AMF devices. N15 is a reference point between the PCF device and the AMF device in a non-roaming scenario, or between the PCF device in the visited network and the PCF device in the home network in the roaming scenario. It is a reference point. N16 is a reference point between two SMF devices (SMF device in the visited network and SMF device in the home network in the roaming case). N17 is a reference point between the AMF device and the 5G-EIR device. N18 is a reference point between any NF and UDSF device. N22 is a reference point between the AMF device and the NSSF device. N27 is a reference point between the NRF device in the visited network and the NRF device in the home network. N31 is a reference point between the NSSF device in the visited network and the NSSF in the home network. N32 is a reference point between the SEPP device in the visited network and the SEPP device in the home network.

In some embodiments, the NFs may be related to one another to serve the UE. In addition to the reference points, there may be interface / reference points between SMF devices and charging systems (CDF and OCS).

<Structure Model and Concepts>

<General Concept>

The 5G system architecture may be defined to support services enabling deployments and data connectivity, for example, to utilize technologies such as network function virtualization and software defined networking. The 5G system architecture can influence service-based interactions between control plane (CP) network functions where they are defined.

Some key concepts of the 5G system architecture are as follows. 5G system architecture separates user plane (UP) functions from Control Plane (CP) functions to provide independent scalability and, for example, a centralized location or Allowing for flexible deployment and evolution, such as distributed (remote) locations. The 5G system architecture can modularize the functional design, for example, to enable flexible and efficient network slicing. Wherever applicable, the 5G system architecture can define the procedures (ie, the set of interactions between network functions) as services to enable reuse of procedures. The 5G system architecture allows each of the network functions to interact directly with other network functions if desired. The 5G system architecture may not interfere with the use of intermediate functionality to aid in routing of control plane messages (e.g., DRA).

5G system architecture can minimize the dependency between an access network (AN) and a core network (CN). 5G system architecture can be defined as a converged core network with a common AN-CN interface that integrates different access types such as 3GPP access and non-3GPP access.

The 5G system architecture can support the unified authentication framework. The 5G system architecture allows "compute" resources to support "stateless" network functions separated from "storage" resources. The 5G system architecture can support capability exposure. The 5G system architecture can support concurrent access to localized and centralized services. In order to support low latency services and access to the local data network, the UP functions can be placed close to the access network. 5G system architecture can support roaming with all of the local breakout traffic in visited PLMN as well as home routed traffic.

<Structure Reference Model>

<General>

The structure for the 5G system is described below. The 5G system architecture is defined on the basis of services, and the interaction between network functions can be represented in two ways. The two ways of expressing the interaction between the network functions are as follows.

(1) In a service-based representation, network functions (e.g., AMF devices) in the control plane may enable other authorized network functions to access their services. The service primitive representation may include a point-to-point reference point if necessary.

(2) The reference point representation is described by a point-to-point reference point (e.g., N11) between any two network functions (e.g., AMF device and SMF device) It can show the interactions existing between NF services in network functions.

The network functions in the 5GC control plane may use only service-based interfaces for their interaction.

<Network Functions and Entities>

The 5G system architecture consists of (1) Authentication Server Function (AUSF), (2) Access and Mobility Management Function (AMF), (3) Data Network (DN) (4) Unstructured Data Storage Function (UDSF), (5) Network Exposure Function (NEF), (6) NF Repository Function (NRF), (7) Network Slice Selection Function (NSSF) PCF), (9) Session Management Function (SMF), (10) Unified Data Management (UDM), Unified Data Repository (UDR), User Plane Function (UPF) 5G-Equipment Identity Register (5G-EIR), (17) Security Edge Protection Proxy (SEPP), (14) User Equipment (UE) And the like.

<Non-roaming reference architecture>

1 is a diagram for explaining a communication system based on a non-roaming reference structure according to an embodiment. Service-based interfaces may be used in the control plane.

The communication system according to one embodiment may include the following service-based interfaces.

Namf is a service - based interface exhibited by the AMF device. Nsmf is the service-based interface represented by the SMF device. Nnef is the service-based interface represented by the NEF device. Npcf is the service-based interface represented by the PCF device. Nudm is the service - based interface represented by the UDM device. Naf is the service-based interface represented by the AF device. Nnrf is the service-based interface represented by the NRF device. Nnssf is the service-based interface represented by the NSSF device. Nausf is the service - based interface represented by the AUSF device. Nudr is the service-based interface represented by the UDR device. Nudsf is a service - based interface represented by a UDSF device. N5g-eir is the service-based interface represented by the 5G-EIR device.

2 is a diagram illustrating a structure of a 5G communication system in a non-roaming case according to an embodiment. Referring to FIG. 2, a structure of a communication system according to an embodiment is illustrated, using a reference point representation that shows how various network functions interact with each other.

N9, and N14 may be omitted in some drawings. In order to clarify the point-to-point diagram, the UDSF device, the NEF device and the NRF device may be omitted. However, all of the network functions shown may interact with the UDSF device, the NEF device and the NRF device. The UDM device may use subscription data and authentication data, and the PCF device may use policy data that may be stored in the UDR device.

For clarity, the connection of UDR devices to other NFs, such as UDR devices and PCF devices, is omitted from the point-to-point and service-based architecture diagrams.

<Roaming Reference Structure>

3 is a diagram for explaining a communication system based on a roaming reference structure according to an embodiment. Referring to FIG. 3, a 5G communication system roaming structure is shown having a local breakout with service-based interfaces within the control plane.

In the LBO architecture, in the VPLMN, the PCF device may interact with the AF device to generate PCC rules for services transmitted via the VPLMN. In VPLMN, the PCF device can use locally configured policies as roaming agreements with HPLMN operators as input to PCC rule generation. In the VPLMN, the PCF device can not access the subscriber policy information from the HPLMN.

<Network Functions>

<General>

In the following, the discovery and selection of network functions, principles of network functions and network functional services are described in 5GC.

<Access and Mobility Management Function (AMF) Device>

The AMF device can perform the following functions. All or some of the functions of the AMF device may be supported in a single instance of the AMF device.

The AMF device may terminate the RAN CP interface (N2). The AMF device may terminate the NAS (N1), the NAS operation (NAS ciphering) and the integrity protection. The AMF device may perform at least one of registration management, connection management, reachability management, and mobility management. The AMF device may perform lawful interception (for AMF events and the interface of the LI). The AMF device may provide for the transmission of SM messages between the UE and the SMF device. The AMF device may perform a transparent proxy for routing SM messages. The AMF device may perform at least one of access authentication and access authorization. The AMF device may support the transmission of SMS messages between the UE and the SMF device.

AMF devices can support Security Anchor Functionality (SEAF). The AMF device may interact with the AUSF device and the UE and may receive an intermediate key established as a result of the UE authentication processor. In the case of USIM-based authentication, the AMF device can retrieve security material from the AUSF device.

The AMF device can perform Security Context Management (SCM). An AMF device performing an SCM can receive a key from a Security Anchor Functionality (SEAF) device and use the received key to derive keys unique to the access network.

The AMF device may perform location service management for regulatory services. The AMF device may provide for the transmission of location service messages between the RAN and the LMF device, as well as between the UE and the Location Management Function (LMF) device. The AMF device may perform EPS Bearer ID assignment for interworking with the EPS.

Regardless of the number of network functions, there can be only one NAS interface per access network between the UE and the CN (Core Network). The NAS interface may be suspended at one of the network functions that at least implement NAS security and mobility management.

In addition to the functions of the AMF device described above, the AMF device may include the following functions to support non-3GPP access networks.

The AMF device may support an N2 interface having a Non-3GPP Interworking Function (N3IWF). In this interface, some information (e.g., 3GPP cell identifiers) and procedures (e.g., procedures related to handover) defined in the 3GPP access may not apply and non-3GPP Access-specific information may be applied.

The AMF device can support UE and NAS signaling in N3IWF. Some procedures supported by NAS signaling in 3GPP access may not be applicable to non-3GPP (e.g., Paging) access that is nontrusted.

The AMF device may support authentication of UEs connected through N3IWF. The AMF device may perform or support mobility management, authentication and separate security context states (s) of a terminal concurrently connected through 3GPP and non-3GPP accesses or connected via non-3GPP accesses .

The AMF device may support a co-ordinated RM management context valid in 3GPP and non-3GPP accesses of the registration area management that allocates or reallocates the registration area to the UE. The AMF device may provide CM management contexts for the UE for connectivity in non-3GPP accesses.

In an instance of a network slice, it is not required to support all of the functions of the AMF device described above. In addition to the functions of the AMF device described above, the AMF devices may include functions related to the policies described in Clause 6.2.8 of TS 23.503.

<Session management function (SMF) device>

The SMF device can perform the following functions. All or some of the functions of the SMF device may be supported in a single instance of the SMF device.

The SMF device may perform session establishment, modification and release including session management, e.g., tunnels that maintain UPF devices and AN nodes. The SMF device may perform UE IP address assignment and management (including selective acknowledgment). The SMF device can perform DHCPv4 (server and client) and DHCPv6 (server and client) functions.

The SMF device may perform ARP proxying specified in the IPv6 Neighbor Solicitation Proxying specified in IETF RFC 4861 function and / or IETF RFC 1027 for Ethernet PDUs. The SMF device may respond to an ARP and / or IPv6 Neighbor Solicitation Request by providing a MAC address corresponding to the IP address sent in the request.

The SMF device performs control and selection of the UP function, including forwarding all ARP / IPv6 Neighbor Solicitation traffic to the SMF device for Ethernet PDU sessions, or controlling the UPF device with proxy ARP or IPv6 Neighbor Discovery .

The SMF device may perform traffic steering in the UPF device to route traffic to the appropriate destination. The SMF device may suspend the interfaces to the policy control functions. The SMF device may perform a lawful interception (for SM events and the interface of the LI).

The SMF device may support charging interfaces and support charging data collection. The SMF device may perform control and coordination of the collection of charge data in the UPF device. The SMF device may perform an interruption of the SM parts of the NAS messages. The SMF device may perform Downlink Data Notification. The SMF device may be the initiator of AN specific SM information transmitted over the AMF device from N2 to AN. The SMF device can determine the SSC mode of the session.

The SMF device includes (1) a Handle of Local Enforcement to apply (VPLMN) QoS SLAs, (2) a charging interface and charge data collection (VPLMN), (3) SM events in VPLMN, LU interfacing), and (4) support for interaction with external DNs for transmission of signaling for PDU session authentication / authorization by external DNs.

In an instance of the network slice, it is not required to support all the functions of the SMF device described above. In addition to the functions of the SMF apparatus described above, the SMF apparatuses may include functions related to the policies described in Clause 6.2.2 of TS 23.503.

<UPF device>

The UPF device can perform the following functions. All or some of the functions of the UPF device may be supported in a single instance of the UPF device.

If applicable, the UPF device may function as an anchor point for Intra- / Inter-RAT mobility. The UPF device may perform the function of the external PDU session point of the interconnection to the data network.

The UPF device can perform packet routing and forwarding. For example, the UPF device may support an uplink classifier that routes traffic flows to instances of the data network. The UPF device may support a branching point to support multi-homed PDU sessions.

The UPF device may perform packet inspection. For example, the UPF device may perform application detection based on service data flow templates and additionally additional PFDs received from the SMF device.

The UPF device may perform user plane portions of policy rule enforcement, for example, gating, redirecting, traffic steering, and the like. The UPF device can perform lawful interception (UP collection). The UPF device may perform traffic usage reporting. The UPF device may perform QoS handling for the user plane, e.g., UL / DL rate enforcement, and reflective QoS marking on the DL. The UPF device may perform uplink traffic verification (mapping from the SDF device to the QoS flow). The UPF device may perform downlink packet buffering and downlink data notification triggering. The UPF device may forward or forward one or more "end markers" to the source NG-RAN node.

The UPF device may perform IPv6 Neighbor Solicitation Proxying specified in the IETF RFC 4861 function and / or ARP proxying specified in IETF RFC 1027 for Ethernet PDUs. The UPF device may respond to an ARP and / or IPv6 Neighbor Solicitation Request by providing a MAC address corresponding to the IP address sent in the request.

In the instance of the user plane function of the network slice, it is not required to support all the functions of the UPF device described above.

<QoS flow>

The 5G QoS model is based on QoS flows. The 5G QoS model may support QoS flows (GBR QoS flows) that require a guaranteed flow bit rate and QoS flows (non-GBR QoS flows) that do not require a guaranteed flow bit rate. The 5G QoS model can support reflective QoS.

The QoS flow is a good granularity of QoS differentiation in a PDU session. The QoS flow identifier (QFI) can be used to identify QoS flows in a 5G system. User plane traffic with the same QFI in a PDU session may receive the same traffic forwarding process (e.g., scheduling, admission threshold). The QFI may be sent in the encapsulation header on N3 (and N9). That is, the QFI can be transmitted without any conversion to the e2e packet header. QFI can be used for all PDU session types. A QFI can be unique in a PDU session. The QFI may be the same as 5QI or dynamically allocated.

Policing of user plane traffic (e.g., MFBR enforcement) may not be regarded as QoS discrimination and may be performed by UPF devices on SDF level granularity.

In 5GS, the QoS flow can be controlled by the SMF device and can be configured in advance. The QoS flow may be established through a PDU session establishment procedure or a PDU session modification procedure.

The QoS flow may be provided by (1) a QoS profile provided by the SMF device via the AMF device at the N2 reference point to the AN or a predefined QoS profile at the AN, (2) by the SMF device via the AMF device at the N1 reference point One or more SDF template (s) provided to the UPF device by the SMF device, and / or one or more QoS rules (s) derived by the UE by applying reflective QoS control .

In 5GS, a QoS flow associated with a base QoS rule is required to be established for a PDU session and may remain established over the lifetime of the PDU session. The QoS flow may be a Non-GBR QoS flow.

The QoS flow can provide the UE with connectivity over the lifetime of the PDU session. Possible interworking with EPS may cause the type of QoS flow to be limited to non-GBR.

<QoS profile>

The QoS flow may be 'GBR' or 'Non-GBR' depending on the QoS profile. The QoS profile of the QoS flow may include QoS parameters described below.

In each of the QoS flows, the QoS profile may include a 5G QoS identifier (5QI) and allocation and retention priority (ARP). In each of the Non-GBR QoS flows, the QoS profile may include a Reflective QoS Attribute (RQA). In each of the GBR QoS flows, the QoS profile may include a Guaranteed Flow Bit Rate (GFBR) at UL and DL, and a Maximum Flow Bit Rate (MFBR) at UL and DL. Only in the case of GBR QoS flows, can include notification control and maximum packet loss rate in UL and DL.

The maximum packet loss rate (UL, DL) can only be provided for GBR QoS flows belonging to the voice media.

Each of the QoS profiles may have one corresponding QoS flow identifier (QFI) that is not included in the QoS profile itself. The 5QI value may indicate that the QoS flow has a QoS feature, and if so, the QoS features may be included in the QoS profile.

<QoS Features>

The 5G QoS features associated with 5QI illustrate packet forwarding processing in which a QoS flow receives edge-to-edge between UE and UPF devices in terms of performance characteristics. The performance characteristics include the following: 5QIs with resource type (critical delay in GBR, GBR or Non-GBR), priority level, Packet Delay Budget, average window and maximum data burst volume 5G access network PDB < For example). 5G QoS features can be understood as guidelines for setting node specific parameters for each of the QoS flows (e.g., 3GPP radio access link layer protocol configuration). Standardized or preconfigured 5G QoS features are indicated by a 5QI value and may not be signaled to any interface. The signaled QoS features may be included as part of the QoS profile.

<QoS rules>

The UE may perform classification and marking of UL user plane traffic, i. E., Associating UL traffic with QoS flows, based on the QoS rules. QoS rules may be explicitly provided to the UE (using the PDU session establishment / change procedure), preconfigured in the UE, or may be derived implicitly by the UE applying a Reflective QoS. The QoS rules may include a PDU session except the default QoS rules, a unique QoS rule identifier in the QFI of the associated QoS flow, a UL, and optionally a packet filter set and priority value for the DL. Additionally, for dynamically allocated QFIs, the QoS rules may include QoS parameters (e.g., 5QI, GBR and MBR and average window) associated with the UE. There can be one or more QoS rules with the same QoS flow (ie, with the same QFI).

The default QoS rules are required for all PDU sessions and may relate to the QoS flow of the default QoS rules. The default QoS rule may be the only QoS rule of a PDU session that does not include any packet filter set. In this case, the highest priority value may be used. If the default QoS rule does not include a packet filter set, then the default QoS rule may define the processing of packets not to match another QoS rule in the PDU session.

If the underlying QoS rules do not include any packet filters, then the reflective QoS may not be applied for QoS flows. The QoS flows to which the reflective QoS is not applied may be related to the default QoS rules, and a Reflective QoS Attribute (RQA) may not be transmitted for the QoS flow.

<RQA>

RQA is an optional parameter, which is a parameter indicating that the specific traffic (which may not be all) of the QoS flow is the object of the reflective QoS. Only when the RQA is signaled for the QoS flow, the (R) AN can enable transmission of the RQI for the AN resources corresponding to the QoS flow. The RQA can be signaled to the NG-RAN via the N2 reference point in UE context establishment and QoS flow establishment or change in the NG-RAN.

<QoS flow mapping>

The SMF device may bind Service Data Flows (SDFs) to QoS flows based on QoS and service requirements (e.g., received PCC rules). The SMF device can allocate the QFI for the new QoS flow and derive its QoS profile from the information provided by the PCF. When applicable, the SMF device may provide the QFI with the QoS profile (R) AN and, optionally, the transport layer packet marking value (R) AN for the UL traffic (e.g., The DSCP value of the outer IP header).

The SMF device is a UPF device capable of classifying, bandwidth enforcement and marking of user plane traffic, a set of packet filters associated with the SDF (received from the PCF), an SDF included in the PCC rules defined in TS 23.503, QoS related information and corresponding packet marking information (e.g., QFI), transport layer packet marking values for downlink traffic (e.g., DSCP values of the outer IP header in the N3 tunnel) And, optionally, a reflective QoS indicator. For each SDF, when applicable, the SMF device may generate a QoS rule, each QoS rule comprising a QoS rule identifier, a QFI of the QoS flow, a packet filter set of the UL part of the SDF template, The packet filter set for the DL part, and the QoS rule priority value set as the priority value of the PCC rule from the QoS rule is generated. QoS rules may be provided to the UE.

4 is a diagram illustrating the principle of marking and classifying user plane traffic and mapping QoS flows to AN resources.

On the downlink, the incoming data packets may be classified by the UPF device based on the SDF templates according to the priority value of the PCC rule allowing service data flow (without initiating additional N4 signaling). The UPF device can use QFI to convey the classification of user plane traffic belonging to the QoS flow through N3 (and N9) user plane marking. The AN may bind QoS flows to AN resources (i. E., Data radio bearers in the case of 3GPP RAN). There is no strict 1: 1 relationship between QoS flows and AN resources. It is up to the AN to establish and release the necessary AN resources to which the QoS flows can be mapped. When the AN resources destined for the QoS flow are mapped, the AN can be represented by the SMF device.

If no match is found and all QoS flows are associated with a DL packet filter set, the UPF device may discard the DL data packet.

In the uplink, the UE determines the UL packet (s) for the packet filter set in the QoS rules based on the ascending order of the priority values of the QoS rules until it finds the matching QoS rule (i. E., The QoS rule matching the UL packet) Can be evaluated. The UE may use the QFI in the corresponding matching QoS rule to bind the UL packet to the QoS flow. The UE may bind QoS flows to AN resources.

If no match is found, and the default QoS rule includes a UL packet filter set, the UE may discard the UL data packet.

The MBR per SDF (and applicable GBR) can be signaled on N4 if it is received from the PCF via N7. The information related to MBR and GBR in N7 may be determined based on TS 23.503.

<DL traffic>

The following features may be applied for processing of DL traffic.

The UPF device may map user plane traffic to QoS flows based on SDF templates. The UPF device may perform session-AMBR monitoring and counting of packets for charging.

The UPF device may transmit PDU sessions PDUs in a single tunnel between 5GC and (R) AN, and the UPF device may include a QFI in the encapsulation header. Additionally, the UPF device may include an indication of reflective QoS activation in the encapsulation header.

The UPF device can perform transport layer packet marking in the DL. That is, the DiffServ code point can be set in the external IP header. Transport layer packet marking may be based on the 5QI and ARP of the associated QoS flows.

(R) AN can map QoS flows to access-specific resources, taking into account the QFI, the associated 5G QoS profile, and the N3 tunnel associated with the DL packet. Packet filters are not used for mapping QoS flows from (R) AN to access-specific resources.

When applying the reflective QoS, the UE can generate a new derived QoS rule. In the derived QoS rule, the packet filter may be derived from the header of the DL packet, and the QFI of the UE derived QoS rule may be set to the QFI of the DL packet.

<UL traffic>

The following features may be applied for processing UL traffic.

The UE may use stored QoS rules to determine the mapping between UL user plane traffic and QoS flows. The UE may indicate the UL PDU with the QFI of the QoS rule including the matching packet filter and may transmit UL PDUs using a corresponding access specific resource for the QoS flow based on the mapping provided by the RAN have.

(R) AN can send PDUs in the N3 tunnel towards the UPF device. When transmitting an UL packet from the (R) AN to the CN, the (R) AN may include the QFI value in the encapsulation header of the UL PDU and select the N3 tunnel.

(R) AN can perform transport layer packet marking in the UL. Transport layer packet marking may be based on the 5QI and ARP of the associated QoS flows. When applicable, the (R) AN may use the transport layer packet marking value (e.g., DSCP value), if it is provided by the SMF device during PDU session establishment / modification.

The UPF device can check whether the QoS rules provided from the UE or implicitly derived by the UE in the case of the reflective QoS and the QFIs in the UL PDUs are aligned. The UPF device may perform session-AMBR monitoring and counting of packets for charging.

&Lt; Reflective QoS >

<General>

Reflective QoS may allow a UE to map uplink user plane traffic to QoS flows without SMF provided QoS rules. Reflective QoS can also be applied to IP PDU sessions and Ethernet PDU sessions. In the same PDU session, it is possible to simultaneously apply the reflective QoS and the non-reflective QoS.

For UE-supported reflective QoS functionality, if the reflective QoS function is used by some of the 5GCs for some traffic flows, then the UE may use uplink traffic for uplink traffic based on the received downlink traffic. And can derive derived QoS rules. The UE may use the derived QoS rules to determine the mapping of uplink traffic and QoS flows.

If the 3GPP UE supports the Reflective QoS function, the UE may indicate support of the Reflective QoS during the PDU Session establishment as a network (e.g., an SMF device).

For UEs in idle mode and EPC to 5GC for connected mode mobility, if the UE supports the Reflective QoS function, the UE may send a Reflective QoS (e. G. The PDU session change procedure can be triggered to indicate the support of the PDU session.

<UE derived QoS rules>

 The UE derived QoS rules may include the following parameters.

(1) One Packet Filter: Contains parameters based on an IP packet filter set or an Ethernet packet filter set described later.

(2) QoS Flow Identifier (QFI)

(3) Precedence Value: A QoS rule precedence value and an SDF (Service Data Flow) template priority value for determining an order in QoS rules or SDF (Service Data Flow) Can be evaluated. The evaluation of QoS rules or SDF templates may be performed in increasing order of their priority values.

For an IP type PDU session, an uplink packet filter may be derived based on a received DL packet as follows.

(1) when the protocol ID and / or the next header is set to TCP or UDP, using the source IP address or the destination IP address, based on the source port number, the destination port number, and the protocol ID / next header field itself An uplink packet filter may be derived.

(2) when the protocol ID and / or the next header is set to the Encapsulating Security Payload (ESP), the source IP address or the destination IP address is used to determine the uplink A packet filter can be derived. If the received downlink packet is an IPSec protected packet and there is an uplink IPSec SA corresponding to the downlink IPSec SA of the SPI in the downlink packet, the UP packet filter suppresses the SPI of the uplink IPSec SA You can.

In an IP type PDU session, the use of the reflective QoS may be limited to service data flows for which the protocol ID / next header is set to TCP, UDP or ESP. The UE may not check whether the downlink packets including the RQI indication match the limit of the reflective QoS.

For an Ethernet type PDU session, an uplink packet filter may be derived based on a received DL packet using a source MAC address and a destination MAC address. The Ethernet type in the received downlink packet may be used as the Ethernet type for the uplink packet. If 802.1Q is present, the VID and PCP of the IEEE 802.1Q header (s) of the received downlink packet may also be used as the VID field and the PC field for the uplink packet filter. When double 802.1Q tagging (double 802.1Q tagging) is used, only outer (S-TAG) can be considered for uplink packet filter derivation. In Ethernet type PDU sessions, the use of reflective QoS may be limited to the service data flows for which 802.1Q tagging is used.

The QFI of the derived QoS rule may be set to the value received in the downlink packet. When the reflective QoS is activated, the priority values for all derived QoS rules can be set to a standardized value.

<Reflective QoS control>

Reflective QoS is defined as a Reflective QoS Timer (RQ Timer) value that is signaled to the UE or set to a default value in PDU session establishment, a Reflective QoS Indication in the encapsulation header on the N3 reference point along with QFI , RQI) on a per-packet basis.

When the 5GC determines that the reflective QoS is to be used for a specific SDF belonging to the QoS flow, the SMF device shall notify the NG-RAN on the N2 reference point, if not previously done so, of the Reflective QoS Attribute ). &Lt; / RTI &gt; When the RQA is provided to the NG-RAN for QoS flow and the 5GC decides that the QoS flow no longer has the SDF for the use of the reflective QoS, the SMF device sends the QoS flow to the NG-RAN on the N2 reference point The deletion of the RQA from the QoS profile can be signaled.

The SMF device may have a timer to delay transmission of the RQA deletion. This can prevent signaling to the RAN while new SDFs that are the subject of reflective QoS are tied to the QoS flow.

When the 5GC has decided to use the reflective QoS for a particular SDF, the SMF device sends an indication for use of the reflective QoS for the SDF to the SDF corresponding to the SDF provided to the UPF device via the N4 interface Information can be included in the information.

When the UPF device receives an indicator for the SDF, the UPF device may set the RQI bit in the encapsulation header on the N3 reference point for all of the downlink packets corresponding to the SDF. When the RQI is received in the downlink packet on the N3 reference point by the (R) AN, the (R) AN can indicate the QFI and RQI of the downlink packet to the UE.

During receiving a downlink packet with an RQI, if there is no UE derived QoS rule with a packet filter corresponding to the downlink packet, the UE generates a new UE derived QoS rule with a packet filter corresponding to the downlink packet can do. Then, the UE can start the timer set to the RQ timer value for the generated UE derived QoS rule.

While receiving the downlink packet with the RQI, if there is a UE-derived QoS rule with a packet filter corresponding to the downlink packet and the QFI associated with the downlink packet is different from the QFI associated with the derived QoS rule, You can update the rules with the new QFI. The UE may then restart the timer associated with the UE derived QoS rules.

After the timer associated with the UE derived QoS rules has expired, the UE may remove the corresponding UE derived QoS rules. When the 5GC has decided not to use the reflective QoS for a particular SDF, the SMF device is provided to the UPF device via the N4 interface and removes the indicator for use of the reflective QoS from the SDF information corresponding to the SDF can do. When the UPF device receives the instruction for the SDF, the UPF device may no longer set the RQI bit in the encapsulation header on the N3 reference point.

The UPF device may accept the uplink traffic of the SDF device for the originally recognized QoS flow during the operator configurable time. This means that the detection and QoS enforcement instructions applied before the indicator for use of the reflective QoS removed by the SMF device remain active in the uplink direction while considering the uplink traffic is completed according to the new instructions It can mean. In order to prevent any uplink packets from being dropped while the UE derived QoS rules are removed by the UE, the configurable time may be at least as long as the RQ timer value.

<Packet Filter Set>

<General>

In order to identify the QoS flow, a packet filter set may be used in the QoS rules or the SDF template. The packet filter set may comprise packet filters for uplink or downlink directions or packet filters applicable in both directions. There can be two types of packet filter sets. For example, the two types of packet filter sets may be an IP packet filter set and an Ethernet packet filter set corresponding to PDU session types.

<IP packet filter set>

For the IP PDU session type, the packet filter set includes (1) source / destination IP address or IPv6 prefix, (2) source / destination port number, (3) protocol ID of the IP / Based on any combination of the type of service (TOS) (IPv4) / traffic class (IPv6) and mask, (5) flow level (IPv6), (6) security parameter index, Packet filtering can be supported.

A value not specified in the filter may match any value of the corresponding information in the packet. The IP address or prefix can be combined with the prefix mask. Port numbers can be specified as port ranges.

<Ethernet packet filter set>

For the Ethernet PDU session type, the packet filter set includes (1) a source / destination MAC address, (2) an Ethernet type defined in IEEE 802.3, (3) a Customer- (4) a Customer-VLAN tag (C-TAG) field defined in IEEE 802.1Q and / or a Service-VLAN tag (S-TAG) Field, (5) an IP packet filter set if the Ethernet type represents an IPv4 / IPv6 payload, and (6) packet filter directions.

The MAC address can be specified in the address range. A value not specified in the filter may match any value of the corresponding information in the packet.

<System procedure>

<General>

Hereinafter, network function services and procedures for a communication system according to an embodiment by end-to-end information flows will be described. Such information flows can utilize the NF service operation described below for communication in the 5GC control plane.

<Connection, registration and mobility management procedures>

<General>

The connection management procedure can be used to establish and release a control plane signaling connection between the UE and the AMF device. Registration management may be used to register or unregister a UE / user in a communication system according to an embodiment, and may be used to establish a user context in a communication system according to an embodiment. The mobility management function may be used to continuously track the current location of the UE. The communication system according to one embodiment may provide connection, registration, and mobility management functions described below.

<Registration Procedures>

<General>

The UE needs to register with the network to activate reachability in order to receive authorization to receive services, to activate mobility tracking.

When the UE performs the initial registration with the communication system according to an embodiment or changes to a new tracking area (TA) outside the registration area of the UE in all of the CM_CONNECTED mode and the CM_IDLE mode, (In accordance with a predetermined period of inactivation) when the UE needs to perform a periodic registration update, it additionally requires that the UE send the negotiated protocol parameters or capabilities in the registration procedure When it is necessary to update, the registration procedure can be used.

The regular registration call flow described below may be applied to all of these registration procedures, but the periodic registration need not include all the parameters used in other registration cases.

The generic registration call flow described below can be used to emergency register UEs that require emergency services to perform but can not obtain general services from the network. These UEs may be limited to limited service situations as defined in TS 23.122.

During initial registration, a Peripheral Equipment Interface (PEI) may be obtained from the UE. The operator of the AMF device can check the PEI with the Equipment Identity Register (EIR). The AMF device can deliver the PEI (IMEISV) to the UDM device, the SMF device and the PCF device, and the UDM device can store this data in the UDR device by Nudr_SDM_Update. The use of an NSI ID in a communication system according to an embodiment may be optional and may depend on the operator's deployment choice.

<General registration>

5 is a flowchart illustrating a registration procedure of a UE in a communication system according to an embodiment.

In step 1, the UE sends an AN message (AN parameters, an RM-NAS registration request (registration type, SUBSCRIPTION CONCEALED IDENTIFIER) or SUPI or 5G-GUTI, last visited TAI (if available) Parameters, the request NSSAI, the mapping of the request NSSAI, the UE 5GC capability, the PDU session state, the PDU session (s) to be reactivated, the Follow on request and the MICO mode selection).

In the case of NG-RAN, the AN parameters may include, for example, SUCI, SUPI or 5G-GUTI, the selected PLMN ID and the request NSSAI. The AN parameters may include the establishment cause. The establishment cause may provide a reason for requesting establishment of an RRC connection.

The registration type indicates whether the UE is in an initial registration (i.e., the UE is in the RM-DEREGISTERED state), a Mobility Registration Update (i.e., the UE is in the RM-REGISTERED state and initiates registration procedures according to mobility) (I.e., the UE is in the RM-REGISTERED state and initiates the registration procedure upon expiration of the periodic registration update timer described above) or emergency registration (i.e., the UE is in a restricted service state) have. If the UE does not yet have a 5G-GUTI, the UE may perform initial registration (i.e., the UE is in the RM-DEREGISTERED state) for the PLMN. The UE may include its SUCI or SUPI in the registration request. A SUCI may only be included (defined in TS 23.501) only if the home network is provisioned with a public key to protect the SUPI at the UE. If the UE has previously received a UE configuration update command indicating that the UE needs to re-register and the 5G-GUTI is available, the UE may perform the initial registration and include the SUPI in the registration request message. For emergency registration, SUPI may be included if the UE does not have a SUPI and a valid 5G-GUTI SUPI. If the UE does not have a SUPI and a valid 5G-GUTI SUPI, a PEI may be included. In other cases, a 5G-GUTI may be included, which may represent the last provided AMF device. If the UE is already registered in the 3GPP access via non-3GPP access in a PLMN that is different from the PLMN (i.e., the same PLMN as the registered PLMN or the registered PLMN) in the 3GPP access, Lt; RTI ID = 0.0 &gt; 5G-GUTI &lt; / RTI &gt; Also, if the UE is already registered via a 3GPP access in a PLMN (i.e., a registered PLMN) different from the new PLMN (i.e., the same PLMN as the unregistered PLMN or the registered PLMN) Gt; 5G-GUTIs &lt; / RTI &gt; registered by the AMF device during non-3GPP access. The UE may provide UE usage settings based on the configuration defined in 5.15.3.7 of TS 23.501. In the case of an initial registration or mobility registration update, in order to ensure that the network can confirm whether the S-NSSAI (s) in the requesting NSSAI has been granted based on the subscribed S-NSSAIs, The mapping of the request NSSAI mapping each of the NSSAIs to the S-NSSAIs of the set NSSAI for the HPLMN.

Where possible, a last visited TAI may be included to assist the UE in registering AMF procedures.

Security parameters may be used for authentication and integrity protection (see TS 33.501). The request NSSAI represents the Network Slice Selection Assistance Information (defined in Section 5.15 of TS 23.501). The PDU session state indicates previously established PDU sessions at the UE. When the UE is connected to two AMF devices belonging to different PLMNs via 3GPP access and non-3GPP access, the PDU session state indicates the establishing PDU session of the current PLMN at the UE. The PDU session (s) to be reactivated may be included to indicate the PDU session (s) for the UE intended to activate UP connections. When the UE is outside the usable area of the LADN, the PDU session corresponding to the LADN may not be included in the PDU session (s) to be reactivated. When the UE has a pending uplink signal and the UE does not include the PDU session (s) to be reactivated, or when the request type indicates that the UE desires to perform emergency registration, . HO attach indication can be added.

In step 2, if the SUPI was included or the 5G-GUTI does not indicate a valid AMF device, the (R) AN may select the AMF device, if possible, based on the (R) AT and the request NSSAI.

(R) AN may select the AMF device based on the description in clause 6.3.5 of TS 23.501. If the UE is in the CM-CONNECTED state, the (R) AN may forward the registration request message to the AMF device based on the N2 connection of the UE. If the (R) AN can not select an appropriate AMF device, it can forward the previously configured registration request from the (R) AN to the AMF device for AMF device selection.

In step 3, the (R) AN sends the N2 message (N2 parameters, RM-NAS registration request (registration type, SUPI or 5G-GUTI, last visited TAI The UE 5GC capability, the PDU session state, the PDU session (s) to be reactivated, the Follow on request, and the MICO mode preference) to the requesting NSSAI.

When the NG-RAN is used, the N2 parameters may include a selected PLMN ID, location information, a cell identifier, and a RAT type associated with the cell where the UE is camped. When the NG-RAN is used, the N2 parameters may include the establishment cause. If the request type indicated by the UE is a Periodic Registration Update, steps 4 through 17 may be omitted.

Step 4 can be performed conditionally and a Namf_Communication_UEContextTransfer (complete registration request) can be sent from the new AMF device to the old AMF device.

If the 5G-GUTI of the UE is included in the registration request and the provided AMF device has changed since the last registration procedure, the new AMF device sends a complete registration request IE, which can be integrity protected, to request the SUPI and MM context of the UE To initiate a Namf_Communication_UEContextTransfer service operation on an old AMF device including The service operation may be performed based on Section 5.2.2.2.2 of TS 23.502. The old AMF device may use the integrity protected full registration request IE to verify that the context transfer service operation start corresponding to the UE has been requested.

The old AMF device is a new AMF device and, for the UE, can transmit event subscription information by each of the NF consumers. After the UE has successfully registered with the new AMF device, NF consumers do not have to subscribe to the event once more with the new AMF device.

Steps 4, 5 and 10 may be omitted if the new AMF device has already received UE contexts from the old AMF device during the handover procedure.

For emergency registration, if the UE has identified itself with an unknown 5G-GUTI to the AMF device, steps 4 and 5 may be omitted and the AMF device may immediately request SUPI from the UE. If the UE identifies itself with the PEI, the SUPI request may be omitted. Accepting emergency requests without user identity may be subject to local regulations.

Step 5 may be performed conditionally and a response to Namf_Communication_UEContextTransfer (SUPI, MM context, SMF information, PCF ID) may be sent from the old AMF device to the new AMF device.

The old AMF device may respond with a new AMF device for the Namf_Communication_UEContextTransfer initiation by including the UE's SUPI and MM contexts. When an old AMF device holds information about established PDU sessions, the old AMF device may contain SMF information including S-NSSAI (s), SMF identifiers and PDU session ID. If the old AMF device holds information about the active NGAP UE-TNLA bound to the N3IWF, then the old AMF device may contain information about the NGAP UE-TNLA bindings.

Step 6 may be performed conditionally and an identifier request may be sent from the new AMF device to the UE. If the SUPI is not provided by the UE, or is not tracked from the old AMF device, the identifier request procedure may be initiated by the AMF device sending an identifier request message to request the SUCI from the UE.

Step 7 may be performed conditionally and an identifier response may be sent from the UE to the new AMF device. The UE may respond with an identifier response message containing the SUCI. The UE derives the SUCI using the provisioned public key of the HPLMN specified in TS 33.501.

In step 8, the AMF device may decide to activate UE authentication by operating the AUSF. In this case, the AMF device may select the AUSF device based on the SUPI or SUCI described in clause 6.3.4 of TS 23.501.

If the AMF device supports emergency registration for unauthorized SUPIs and the UE has indicated a request type emergency registration, the AMF device may omit authentication and security setup, or the AMF device may agree that authentication may fail, You can continue with the procedure.

In step 9a, the AUSF device may perform authentication of the UE.

Authentication can be performed as described in TS 33.501 by the Nudm_UEAuthenticate_Get operation. The AUSF device may find the UDM as described in 6.3.8 of TS 23.501. If the AMF device provides SUCI as an AUSF device, then the AUSF device may return the SUPI to the AMF device after successful authentication.

If network slicing is used, the AMF device may determine that the initial AMF device is to be rerouted, as described in 4.2.2.2.3 of TS 23.502, which represents the AMF device.

In step 9b, the AMF device may initiate NAS security functions. NAS security can be performed as described in TS 33.501.

In step 9c, when the NAS security function setup is completed, the AMF device can start the NGAP procedure as specified in TS 38.413. This is to allow the 5G-AN to use it for security procedures with the UE.

In step 9d, the 5G-AN stores the security context and acknowledges it to the AMF device. The 5G-AN may use the security context to protect messages exchanged with the UE as described in TS 33.502.

Step 10 may be performed conditionally, Namf_Communication_RegistrationCompleteNotify may be sent from the new AMF device to the old AMF device.

When the AMF device is changed, the new AMF device can notify the old AMF device that the registration of the UE in the new AMF device has been completed by operating the Namf_Communication_RegistrationCompleteNotify service operation.

If the authentication / security procedure fails, the registration can be rejected and the new AMF device can activate the Namf_Communication_RegistrationCompleteNotify service operation with the reject indication reason code towards the old AMF device. The old AMF device can continue as if the UE context transfer service operation was not received.

If one or more S-NSSAIs in the old registration area can not be provided in the target registration area, the new AMF device can determine which PDU session can not be provided in the new registration area. The new AMF device may operate a Namf_Communication_RegistrationCompleteNotify service operation that includes a rejection cause (e.g., the S-NSSAI is no longer available) and rejected PDU session ID to the old AMF device. In this case, the new AMF device may change the PDU session state accordingly. The old AMF device may inform the corresponding SMF device (s) to release the SM context of the UE locally by activating the Nsmf_PDUSession_ReleaseSMContext service operation. The Namf_Communication_RegistrationCompleteNotify service operation can be performed based on 5.2.2.2.3 of TS 23.502.

Step 11 may be performed conditionally and an identifier request / response (PEI) may be sent from the new AMF device to the UE.

If the PEI is not provided by the UE or retrieved from the old AMF device, the identifier request procedure may be initiated by sending an identifier request message to the UE by the AMF device to retrieve the PEI. If the UE can not be authenticated without performing emergency registration, the PEI may be encrypted and transmitted. For emergency registration, the UE may include a PEI in the registration request. In this case, PEI recovery may be omitted.

In step 12, the new AMF device can initiate the ME identity check by activating the N5g-eir_EquipmentIdentityCheck_Get service operation. The PEI check can be performed based on clause 4.7 of TS 23.502. For emergency registration, if PEI is blocked, operator policies can decide whether to start or stop the emergency registration procedure.

In step 13, when step 14 is performed, the new AMF device can select a UDM device based on the SUPI. In this case, the UDM device can select the UDR instance.

In steps 14a-b, if the AMF device has changed since the last registration procedure, or if the UE provides a SUPI that does not reference a valid context in the AMF device, or if the UE registers with the same AMF device that is not already registered for non-3GPP access (I.e., the UE is registered in a non-3GPP access and starts this registration procedure to add 3GPP access), the new AMF device registers with Nudm_UECM_Registration and the UDM device releases the registration from the AMF device You can subscribe to receive notifications at the time. The UDM device may store the AMF identity associated with the access type and may not remove the AMF identity associated with the other access type. The UDM device can store the information provided by the registration in the UDR by Nudr_UDM_Update.

The AMF device is capable of retrieving access, mobility subscription data and SMF selective subscription data. This requires the UDM device to retrieve this information from the UDR using Access and Mobility Subscription data (Nudr_UDM_Query). After a successful response is received, the AMF device may be registered to receive notification using Nudm_SDM_Subscribe when the data request is changed, and the UDM may subscribe to the UDR by Nudr_UDM_Subscribe. If GPSI is available in the UE subscription data, GPSI may be provided to the AMF device in the subscription data of the UDM device.

The new AMF device may provide an access type, which may be provided as a UDM device for the UE, and the access type may be set to "3GPP access ". The UDM device can store the associated access type with the provided AMF device in the UDR by Nudr_UDM_Update.

After acquiring the mobility subscription data of the UDM device, the new AMF device may create an MM context for the UE. For emergency registration where the UE is not successfully authenticated, the AMF device may not subscribe to the UDM device. For emergency registration, the AMF device may not check access restrictions, regional restrictions or subscription restrictions. For emergency registration, the AMF device can ignore the unsuccessful registration response of the UDM device and continue the registration procedure.

In step 14c, when there is one, when the UDM device has stored the associated access type with the providing AMF device shown in step 14a, it may cause the UDM device to start Nudm_UECM_DeregistrationNotification with the old AMF device corresponding to 3GPP access There is a cause. The old AMF device may remove the MM context of the UE. If the provided NF cancellation reason indicated by the UDM is an initial registration, the old AMF device can activate the Namf_EventExposure_Notify service operation towards all SMF devices of the UE to signal that the UE has been deregistered from the old AMF device. The SMF device may release the PDU session (s) upon receipt of this notification.

In step 14d, the old AMF device may cancel the subscription to the UDM device for subscription data using Nudm_SDM_unsubscribe.

In step 15, if the AMF device has decided to start the PCF communication, for example, the AMF device has not yet acquired the Access and Mobility policy for the UE, And if the mobility policy is no longer valid, the AMF device may select the PCF device. If the new AMF device receives the PCF ID from the old AMF device in step 5 and successfully connected to the PCF device identified by the PCF ID, the AMF device may select the (V-) PCF device identified by the PCF ID . If the PCF device identified by the PCF ID is unavailable (for example, there is no response from the PCF device), or if there is no PCF ID received from the old AMF device in step 5, the AMF device shall be identified in clause 6.3.7.1 of TS 23.501 You can select a PCF device as described in.

Step 16 may optionally be performed and the new AMF device may perform Policy Association Establishment during the registration procedure defined in Section 4.16.1.2 of TS 23.502. For emergency registration, step 16 may be omitted.

If the new AMF device contacts the PCF device identified by the received (V-) PCF ID during inter-AMF mobility in step 5, the new AMF device may include the PCF-ID in the Npcf_AMPolicyControl Get operation. This indicator may not be included by the AMF device during the initial registration procedure.

If the AMF device informs the PCF device of mobility regulation (e.g., UE location) for adjustment, or if the PCF device updates its mobility regulation by some condition (e.g., application in use, time and date) , The PCF device may provide updated mobility regulation to the AMF device.

In step 17, the PCF device can activate the Namf_EventExposure_Subscribe service operation for UE event subscription.

Step 18 may be selectively performed, and from the AMF apparatus to the SMF apparatus, Nsmf_PDUSession_UpdateSMContext may be transmitted.

For an emergency registered UE, this step may be applied when the registration type is a mobility registration update.

The AMF device can activate Nsmf_PDUSession_UpdateSMContext based on the scenario described below.

If the "PDU Session (s) to be re-activated" is included in the registration request at step 1, the AMF device sends the SMF device (s) associated with the PDU session (s) ) To send an Nsmf_PDUSession_UpdateSMContext Request. The UE Triggered Service Request, which has been executed continuously from Step 5, has completed the activation of the user plane connection without the approval of the MM NAS service transmitted from the AMF device (R) AN described in Step 12 of 4.2.3.2 of TS 23.502 . &Lt; / RTI &gt;

The SMF device may decide to cause a change or deletion of the PSA (eg, intermediate UPF insertion) as described in step 5 of Section 4.2.3.2 of TS 23.502. An intermediary UPF device insertion, deletion or relocation may be performed for PDU session (s) not included in "PDU Session (s) to be re-activated ". The procedure may be performed without N11 and N2 interaction to update the N3 user plane between (R) AN and 5GC.

The AMF device can activate the Nsmf_PDUSession_ReleaseSMContext service operation with the SMF device in the scenario described below.

If it indicates that a PDU session state has been released at the UE, the AMF device may activate the Nsmf_PDUSession_ReleaseSMContext service operation with the SMF device to release the network resources associated with the PDU session.

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

If the provisioning AMF device has changed, the new AMF device may wait with step 17 complete with all the SMF devices associated with the UE. Otherwise, steps 18 to 22 may continue in parallel with step 18.

Mobility related event notifications to NF consumers may be triggered at the end of this procedure for cases described in Section 4.15.4 of TS 23.502.

In step 19, an N2 AMF mobility request may be sent from the AMF device to N3IWF. If the AMF device is changed, the new AMF device may create a NGAP UE association towards the N3IWF to which the UE is connected.

In step 20, from the N3IWF to the new AMF device, the N2 AMF maneuver response can be sent.

In step 21, a new AMF device sends a registration grant (5G-GUTI, registration area, mobility constraints, PDU session state, allowed NSSAI, [mapping of allowed NSSAI], periodic registration update timer, LADN information, , IMS voice by indicator supported by PS session, Emergency Service Support Indicator).

The AMF device may send a registration acknowledgment message to the UE indicating that the registration request has been approved. If the AMF device has assigned a new 5G-GUTI, a 5G-GUTI may be included. If the AMF device has assigned a new registration area, it can transmit the registration area to the UE via a registration grant message. If no registration area is included in the registration approval message, the UE can regard the old registration area as valid. Mobility regulations may be included when mobility regulations are applied for the UE and when the registration type is not emergency registration. The AMF device may indicate establishment PDU sessions to the UE in the PDU session state. The UE may locally remove internal resources associated with PDU sessions not marked as established in the received PDU session state. When the UE is connected to two AMF devices belonging to different PLMNs via 3GPP access and non-3GPP access, the UE locally removes the internal resources associated with the PDU session of the current PLMN not marked as established in the received PDU session state can do. If the PDU session state information is in the registration request, the AMF device can indicate the PDU session state to the UE. The mapping of the allowed NSSAI is the mapping of each of the allowed NSSAI's S-NSSAIs to the S-NSSAIs of the configured NSSAI for HPLMN. The AMF device may include the LADN information for the LADNs defined in clause 5.6.5 of TS 23.501 in the registration acknowledgment message. The LADN information for the LADNs is available in the registration area determined by the AMF device for the UE. If the request includes a UE-included MICO mode, the AMF device may respond whether the MICO mode is to be used. The AMF device may set the IMS voice on the PS session support indicator as described in clause 5.16.3.2 of TS 23.501. In order to set up the IMS voice on the PS session support indicator, the AMF device requests the compatibility request procedure of TS 23.502, 4.2.8, to check the UE / RAN radio information and the RAN radio capability associated with the IMS voice on the PS and UE. You need to do it. If the AMF device fails to receive a Voice Support Match Indicator from the NG-RAN on time, based on the implementation, the AMF device can set the IMS voice on the PS session support indicator and update it at a later stage can do. The Emergency Service Support Indicator may inform the UE that emergency services are supported (e.g., the UE is allowed to request a PDU session for emergency services).

At this stage, the handover restriction list and the UE-AMBR may be provided by the AMF device to the NG-RAN.

For an emergency registered UE, the AS security context information is not included in the N2 control message, and there may be no NAS level security when the UE can not be authenticated.

Step 22 may optionally be performed and a registration complete message may be sent from the UE to the AMF device.

If a new 5G-GUTI is assigned, the UE may send a registration completion message to the AMF device to respond. When "PDU Session (s) to be re-activated" is not included in the registration request, the AMF device may release the signaling connection with the UE according to Section 4.2.6. If the AMF device determines that some signaling is pending between the AMF device or between the UE and the 5GC, the AMF device may not release the signaling connection immediately after the registration procedure is completed.

<UE Request PDU Session Establishment>

<Non-Roaming and Roaming with Local Breakout>

The following describes the establishment of PDU sessions in roaming and non-roaming with local breakout cases. The PDU session establishment procedure described below is used for (1) establishing a new PDU session, (2) handing over a PDN connection in EPS from a 5GS to a PDU session without an N26 interface, (3) To switch an existing PDU session between accesses, and (4) to request a PDU session for emergency services.

In the case of roaming, the AMF device can determine if a PDU session is established in LBO or home routing. For the LBO, the PDU session establishment procedure may be the same as in the case of non-roaming with the difference that the AMF, SMF, UPF and PCF devices are located in the visited network. PDU sessions for emergency services may not be established in home route mode.

6 is a flow chart illustrating a procedure for establishing a UE Request PDU session in a communication system according to an embodiment. In the procedure of FIG. 6, it is assumed that the AMF device has already retrieved user subscription data from the UDM device, unless the UE has already been registered with the AMF device and the UE is not urgently registered.

In step 1, the UE may send a NAS message containing a PDU session establishment request to the AMF device. The NAS message transmitted from the UE to the AMF device may include at least one of S-NSSAI (s), DNN, PDU session ID, request type, old PDU session ID and N1 SM container (PDU session establishment request). In order to establish a new PDU session, the UE may generate a new PDU session ID.

The UE initiates a UE Request PDU Session Establishment Procedure by sending a NAS message that includes a PDU Session Establishment Request in the N1 SM container. The PDU session establishment request may include at least one of a requested PDU type, a requested SSC mode, protocol configuration options, and an SM PDU DN request container.

If the PDU session establishment is a request to establish a new PDU session, the request type may indicate an "Initial request ", PDU session establishment associated with existing PDU session switching between 3GPP access or non-3GPP access, The request type may indicate an "Existing PDU Session " if it is associated with a PDU session handover from an existing PDN connection. If the PDU session establishment request is associated with an existing PDN connection in the EPC, the S-NSSAI may be established based on the S-NSSAI received from the PCO sent by the PGW-C + SMF during the PDN connection establishment procedure. If an emergency service is required and an emergency PDU session has not been established previously, the UE may initiate a UE Request PDU Session Establishment procedure with a request type indicating "Emergency Request ".

If the PDU session establishment is a request to establish a PDU session for emergency services, the request type may indicate "Emergency Request ". If the PDU session establishment request is associated with an existing PDU session for emergency service switching between 3GPP access and non-3GPP access, the request type may indicate an "Existing Emergency PDU Session ".

The NAS message sent by the UE may be encapsulated by the AN in an N2 message destined for the AMF device, and may include user location information and access technology type information. The PDU Session Establishment Request message may comprise an SM PDU DN Request Container containing information for PDU session authentication by an external DN. The UE may include an S-NSSAI from an authorized NSSAI (Allowed NSSAI). If a mapping of an authorized NSSAI is provided to the UE, the UE may provide both the S-NSSAI from the authorized NSSAI and the corresponding S-NSSAI from the NSSAI configured for the HPLMN.

When the procedure is triggered for SSC mode 3 operation, the UE includes an old PDU session ID (Old PDU Session ID) indicating the PDU session ID of the on-going PDU session to be released in the NAS message . The old PDU session ID may be an optional parameter included only in this case.

The AMF device may receive an NAS SM message (generated in step 1) from the AN with user location information (e.g., a cell ID in the case of a RAN). If the UE is outside the available area of the LADN, the UE may not initiate PDU session establishment for the PDU session corresponding to the LADN.

In step 2, the AMF device may determine whether the message corresponds to a request for a new PDU session based on whether the request type indicates "initial request ". The AMF device may determine which PDU session ID is not used for which existing PDU session (s) of the UE. If the NAS message does not include the S-NSSAI, the AMF device may request the requested PDU session according to the UE subscription, or, in accordance with the operator policy, if the NAS message includes only one default S-NSSAI. Lt; RTI ID = 0.0 &gt; S-NSSAI &lt; / RTI &gt;

The AMF device may select an SMF device based on clause 4.3.2.2.3 of TS 23.502. The AMF device may store the relationship of the S-NSSAI (s), the DNN, the PDU session ID and the SMF ID if the request type indicates an "Initial request ", or if the request originates from a handover from the EPS.

 If the request type is "Initial request" and the old PDU session ID indicates that an existing PDU session is also included in the message, then the AMF device may select an SMF device based on Section 4.3.5.2 of TS 23.502, ID, S-NSSAI, and the selected SMF ID.

If the request type is an "Existing PDU Session ", the AMF device can select an SMF device based on the SMF-ID received from the UDM device. If the request type is "Existing PDU Session ", the AMF device does not recognize the PDU session ID, or the subscription context received by the AMF device from the UDM device during the registration or subscription profile update notification procedure is the SMF ID Can be used to construct an error case.

Indicates the "Existing PDU Session" associated with an existing PDU session in which the request type is moved between 3GPP access and non-3GPP access, and the SMF ID (H-SMF for home route) corresponding to the PDU session ID and AMF device is the same PLMN The PDU session establishment procedure can be performed. Otherwise, the AMF device may reject the request to establish a PDU session with the cause of the appropriate rejection.

The SMF ID may include the PLMN ID to which the SMF belongs.

When the UE is registered for emergency service and the request type does not indicate either "Emergency Request" or "Existing Emergency PDU Session", the AMF device may deny the request from the UE. If the request type indicates an "Emergency Request ", the AMF device may use locally configured values instead of expecting the DNN value and any S-NSSAI provided by the UE.

If the request type indicates "Emergency Request" or "Existing Emergency PDU Session", the AMF device may select the SMF device based on Section 5.16.4 of the TS 23.501 document.

In step 3, the AMF device transmits, to the SMF device, Nsmf_PDUSession_CreateSMContext Request (SUPI, DNN, S-NSSAI, PDU session ID, AMF ID, request type, N1 SM container (PDU session establishment request) , GPSI, PDU session state notification, or Nsmf_PDUSession_UpdateSMContext Request (SUPI, DNN, S-NSSAI, PDU session ID, AMF ID, request type, N1 SM container (PDU session establishment request) Type, PEI).

If the AMF device does not have a relationship with the SMF device for the PDU session ID provided by the UE (e.g., the request type indicates "initial request"), the AMF device may apply the Nsmf_PDUSession_CreateSMContext Request. However, if the AMF device is already associated with the SMF device for the PDU session ID provided by the UE (e.g., when the request type indicates an "existing PDU Session"), the AMF device can apply the Nsmf_PDUSession_UpdateSMContext request have.

The AMF ID is the GUAMI of the UE that uniquely identifies the AMF device serving the UE. The AMF device may forward the PDU session ID with an Nl SM container containing a PDU session establishment request received from the UE. If available in the AMF device, GPSI may be included.

When the UE is registered for emergency service without providing SUPI, the AMF device may provide PEI instead of SUPI. PEI is defined in section 5.9.3 of the TS 23.501 document. If the UE is registered for emergency services with SUPI but is not authenticated, the AMF device may indicate that the SUPI is not authenticated. When the SUPI for the UE has not been received or the AMF device indicates that the SUPI is not authenticated, the SMF device may determine that the UE is not authenticated.

If the old PDU session ID is included in step 1 and the SMF device is not reassigned, the AMF device may include the old PDU session ID in the Nsmf_PDUSession_CreateSMContext request.

In local breakout, if the V-SMF can not handle some of the Nl SM information, home routed roaming may be required. The V-SMF may apply the Nsmf_PDUSession_CreateSM response service operation and reply with the AMF device that it is not the correct SMF device to process the N1 SM message. The V-SMF may include an appropriate N11 inducing code to cause the AMF device to proceed to the home route case. It is possible to start again from step 2 of FIG.

In step 4, if step 3 does not indicate either "Emergency Request" and "Existing Emergency PDU Session" and the SMF device is not yet registered for this PDU session ID, the SMF device sends Nudm_UECM_Registration (SUPI, DNN, PDU session ID). Consequently, the UDM device can store information such as SUPI, SMF identity, SMF address and associated DNN and PDU session ID. If the session management subscription data corresponding to SUPI, DNN and N-NSSAI is not available, the SMF device can retrieve the session management subscription data using Nudm_SDM_Get (SUPI, DNN, S-NSSAI) And can subscribe to receive notifications when this subscription data is changed using Nudm_SDM_Subscribe (SUPI, DNN, S-NSSAI).

If the request type received in step 3 indicates "Emergency Request ", then for an authenticated non-roaming UE the operator configuration (e.g., whether the operator uses a fixed SMF device for emergency calls, etc.) , The SMF device can register with the UDM device using Nudm_UECM_Registration (SUPI, PDU Session ID, Indication of Emergency Services) for a given PDU session available for emergency services. Consequently, the UDM device can store an SMF device address and an applicable PDU session for emergency services.

If the request type received in step 3 indicates "Emergency Request ", for an unauthenticated UE or roaming UE, the SMF device may not register in the UDM in a given PDU session.

If the request type indicates an "Existing PDU Session" or an "Existing Emergency PDU Session" in step 3, the SMF device may determine that the request originated from switching between 3GPP access and non-3GPP access, Can be determined. The SMF device may identify an existing PDU session based on the PDU session ID. In this case, instead of creating a new SM context, the SMF device may update the existing SM context and provide an indication of the updated SM context to the AMF device in the response.

If the request type is "Initial request ", and the old PDU session ID is included in the Nsmf_PDUSession_CreateSMContext request, the SMF device can identify an existing PDU session to be released based on the old PDU session ID.

The subscription data may include at least one of an authenticated PDU type (s), authenticated SSC mode (s), default 5QI and ARP, and a subscribed session-AMBR.

If the UE is not subscribed to it, a static IP address / prefix may be included in the subscription data.

The SMF device can check the validity of the UE request. The SMF device determines whether the UE is compliant with the user subscription and local policies, and (2) if the UE request corresponds to a LADN, based on the UE location reported from the AMF device, It can be checked whether it is located within the service area.

If the UE request is deemed invalid, the SMF device may decide not to consent to establishing a PDU session.

In step 5, an Nsmf_PDUSession_UpdateSMContext request that depends on the Nsmf_PDUSession_CreateSMContext request (cause, SM context ID or N1 SM container (PDU session rejection (cause)) or the request received in step 3 may be sent from the SMF device to the AMF device.

When the SMF device receives the Nsmf_PDUSession_CreateSMContext request in FIG. 3 and the SMF device is able to process the PDU session establishment request, the SMF device may respond to the AMF device by providing the SM context identifier.

When the SMF device decides not to accept a PDU session, the SMF device may respond to the AMF device with a Nsmf_PDUSession_CreateSMContext response to reject the UE request via NAS SM signaling, including the associated SM rejection cause. The SMF device may indicate to the AMF device that the PDU session ID is considered to be released, cancel the registration from the UDM device for this PDU session, and the remainder of the procedure may be omitted.

In step 6, optional secondary authorization / authentication may be performed.

If the request type indicates "Existing PDU Session" in step 3, the SMF device may not perform the secondary acknowledgment / authentication.

If the request type received in step 3 is "Emergency Request" or "Existing Emergency PDU Session ", then the SMF device may not perform the secondary authorization / authentication.

If the SMF device needs to perform secondary authentication / authorization while establishing a PDU session by the DN-AAA server described in clause 5.6.6 of the TS 23.501 document, PDU session establishment authentication / authorization described in &lt; / RTI &gt;

PDU Session Establishment If authentication / authorization fails, the SMF device may proceed to step 19 and the PDU session establishment procedure may be interrupted.

In step 7a, if a dynamic PCC is deployed, the SMF device can perform PCF device selection. If the request type indicates an "Existing PDU Session" or an "Existing Emergency PDU Session", the SMF device may use the PCF already selected for the PDU session. If no dynamic PCC is deployed, the SMF device can apply local policies.

In step 7b, the SMF device may perform the session management policy establishment procedure described in section 4.16.4 of the TS 23.502 document to establish a PDU session to the PCF device and obtain default PCC rules for the PDU session. Where possible in the SMF device, GPSI may be included. If the request type indicates an "Existing PDU Session" in step 3, the SMF device may notify the event previously subscribed by the PCF by the session management policy change procedure defined in section 4.16.5 of the TS 23.502 document, and the PCF The device can update the policy information in the SMF device. The PCF device may provide the authenticated session-AMBR and authenticated 5QI and ARP to the SMF device. The PCF device can subscribe to IP allocation / release events (and subscribe to other events) in the SMF device.

The PCF device may set the ARP of the PCC rules to a value reserved for the emergency services described in TS 23.503, based on the emergency DNN.

The purpose of step 7 is to receive the PCC rules before selecting the UPF device. If the PCC rules are not required as input to the UPF device selection, step 7 may be performed after step 8.

In step 8, if the request type indicates an "Initial request ", the SMF device may select the SSC mode for the PDU session, as described in section 5.6.9.3 of the TS 23.501 document. The SMF device may select one or more UPF devices as required, as described in Section 6.3.3 of the TS 23.501 document. For IPv4 or IPv6 PDU types, the SMF device may assign an IP address / prefix for the PDU session as described in clause 5.8.1 of the TS 23.501 document. For the PDU type of IPv6, the SMF device may assign an interface identifier to the UE to make its link-local address. For an unstructured PDU type, the SMF device may allocate N6 point-to-point tunneling (based on UDP / IPv6) and an IPv6 prefix for a PDU session with reference to 5.6.10.3 of the TS 23.501 document. For an Ethernet PDU type PDU session, all of the MAC and IP addresses may not be allocated to the UE by the SMF device in this PDU session.

If the request type is "Existing PDU Session" in step 3, the SMF device may maintain the IP address / prefix already assigned to the UE in the source network.

In step 3, if the request type is an "Existing PDU Session" associated with an existing PDU session that has been moved between 3GPP access and non-3GPP access, then the SMF device is in the SSC mode of the PDU session, the current PDU Session Anchor, IP address can be maintained.

The SMF device may, for example, decide to initiate the allocation of a new UPF device or the insertion of a new intermediate UPF device as described in step 5 in section 4.2.3.2 of the TS 23.502 document.

If the request type is "Emergency Request", the SMF device can select the UPF device and select SSC mode 1 by referring to the description in section 5.16.4 of the TS 23.501 document.

In step 9, the SMF device may perform the session management policy change procedure defined in section 4.16.5 of the TS 23.502 document to report some already subscribed events to the PCF device. If the request type is "initial request ", the dynamic PCC is placed, and the PDU type is IPv4 or IPv6, the SMF device can notify the (already subscribed) PCF device of the assigned UE IP address / prefix.

If the IP address / prefix is assigned before step 7 (e.g., a static IP address / prefix joined in the UDM device) or step 7 is performed after step 8, the IP address / prefix is provided to the PCF device in step 7 And the IP address / prefix notification of step 9 may be omitted.

In step 9, the PCF device may notify the SMF device of the updated policies. The PCF device may provide the authenticated session-AMBR and authenticated 5QI and ARP to the SMF device.

In step 10, if the request type indicates an "initial request ", the SMF device may start the N4 session establishment procedure with the selected UPF device, or otherwise initiate the N4 session modification procedure with the selected UPF device.

In step 10a, the SMF device may send an N4 session establishment / change request to the UPF device and provide packet detection, monitoring and reporting rules to be installed in the UPF device for this PDU session. If the CN tunnel information is allocated by the SMF device, the CN tunnel information can be provided to the UPF device at this stage. If the selective user plane deactivation is required for this PDU session, the SMF device may determine the inactivity timer and provide it to the UPF device.

In step 10b, the UPF device may respond by sending an N4 session establishment / change response. If CN tunnel information is assigned by the UPF device, CN tunnel information may be provided to the SMF device at this stage.

If multiple UPF devices are selected for the PDU session, then the SMF device can start the N4 session establishment / change procedure with each UPF device of the PDU session at this stage.

If the request type indicates "Existing PDU Session" and the SMF device generates CN tunnel information, step 10b may be omitted. Otherwise, step 10b may be performed to obtain CN tunnel information from the UPF device using the N4 session change procedure.

In step 11, the SMF device transmits to the AMF device Namf_Communication_N1N2MessageTransfer (PDU session ID, access type, N2 SM information (PDU session ID, QFI (s), QoS Profile (s), CN tunnel information, S-NSSAI, , The PDU session type), N1 SM container (PDU session establishment acknowledgment (QoS Rule (s), selected SSC mode, S-NSSAI, assigned IPv4 address, interface identifier, session-AMBR, selected PDU session type) . When a plurality of UPF devices are used for a PDU session, the CN tunnel information may include UPF device related tunnel information for stopping N3.

N2 SM information can be transmitted by the AMF device to forward the information to be forwarded to the (R) AN, which information includes (1) CN tunnel information corresponding to the core network address of the N3 tunnel corresponding to the PDU session, (2) One or more QoS profiles and corresponding QFIs to be provided in the AN (as described in section 5.7 of the TS 23.501 document), (3) UEs to indicate the relationship between the AN resources and the PDU session for the UE, Lt; RTI ID = 0.0 &gt; PDU &lt; / RTI &gt;

The PDU session may be associated with an S-NSSAI and a DNN. The Nl SM container may include a PDU session establishment acknowledgment that the AMF device will be provided to the UE. Multiple QoS rules and QoS profiles may be included in the Nl SM and N2 SM information in PDU session establishment acknowledgments. The Namf_Communication_N1N2MessageTransfer may include a PDU session ID and information to know what the AMF device is to be accessed towards the UE for use. The access information is for processing when the UE is concurrently connected in 3GPP and Non 3GPP accesses.

In step 12, an N2 PDU session request (N2 SM information, NAS message (PDU session ID, N1 SM container (PDU session establishment acknowledgment)) may be transmitted from the AMF device to the (R) ID, N2 SM information received from the SMF device in a PDU session establishment acknowledgment directed to the UE and an N2 PDU session request directed to the (R) AN.

In step 13, the (R) AN may issue an AN specific signaling to the UE that is exchanged with the UE associated with the information received from the SMF device. For example, in the case of a 3GPP RAN, an RRC connection reconfiguration may be generated with the UE establishing the required RAN resources associated with the QoS rules for the PDU session request received in step 12.

(R) AN can allocate (R) AN N3 tunnel information for PDU session. For dual connectivity, the master RAN node may allocate some (zero or more) QFIs to be installed in the master RAN node and another QFI to the secondary RAN node. The AN tunnel information may include tunnel endpoints for each of the associated RAN nodes, and QFIs allocated to each of the tunnel endpoints. The QFI may be assigned to either the master RAN node or the secondary RAN node, but is not allocated to all of the master RAN node and the secondary RAN node.

(R) AN may forward the NAS message provided in step 12 (PDU Session ID, N1 SM container (PDU Session Establishment Accept)) to the UE. If the required RAN resources are established and the assignment of (R) AN tunnel information is successful, (R) AN can provide only the NAS message to the UE.

In step 14, an N2 PDU session response (PDU session ID, cause, N2 SM information (PDU session ID, AN tunnel information, list of QFI (s) that have been acknowledged or rejected)) from the (R) AN to the AMF device Lt; / RTI &gt; The AN tunnel information may correspond to the access network address of the N3 tunnel corresponding to the PDU session.

In step 15, an Nsmf_PDUSession_UpdateSMContext request (N2 SM information, request type) may be transmitted from the AMF apparatus to the SMF apparatus. The AMF device may forward the N2 SM information received from the (R) AN to the SMF device. If the list of rejected QFI (s) is included in the N2 SM information, the SMF device may release the QoS profiles associated with the rejected QFI (s).

In step 16a, the SMF device may start the N4 session change procedure with the UPF device. The SMF device may provide AN tunnel information to the UPF device as well as corresponding forwarding rules.

If the PDU session request originates from mobility between 3GPP and non-3GPP access or from mobility from the EPC, the downlink data path may be switched towards the target access at this stage.

In step 16b, the UPF device may provide an N4 session change response to the SMF device.

When a plurality of UPF apparatuses are used in the PDU session, the UPF apparatus of step 16 represents a UPF apparatus that interrupts N3.

In step 17, a Nsmf_PDUSession_UpdateSMContext response (cause) may be sent from the SMF device to the AMF device.

The SMF device may subscribe to UE mobility event notification from the AMF device by applying the Namf_EventExposure_Subscribe service operation specified in section 5.2.2.3.2 of the TS 23.502 document after this step (for example, Location report, UE entering or leaving area of interest). For the LADN, the SMF device may subscribe to an event notification that the UE enters or exits the LADN service area by providing the LADN DNN as an indicator for the area of interest. The above operation can be performed with reference to sections 5.6.5 and 5.6.11 of the TS 23.501 document.

After this step, the AMF device can forward related events subscribed by the SMF device.

Step 18 may be performed conditionally and Nsmf_PDUSession_SMContextStatusNotify (release) may be sent from the SMF device to the AMF device.

While the procedure is being performed, at some point after the step 5 has been performed, if the PDU session establishment is not successful, the SMF device can inform the AMF device by applying Nsmf_PDUSession_SMContextStatusNotify (release). The SMF device may release the generated N4 session (s) and the assigned PDU session address (e.g., IP address) and release the association with the PCF device.

In step 19, from the SMF device to the UE, if the PDU type is IPv6, the SMF device can generate an IPv6 Router Advertisement and transmit it to the UE via the UPF device and N4.

In step 20, if a PDU session can not be established, the SMF device may perform at least one of the following operations.

(a) If the SMF device can no longer handle the PDU session of this (DNN, S-NSSAI), then the SMF device uses the Nudm_SDM_Unsubscribe (SUPI, DNN, S-NSSAI) , DNN, S-NSSAI), the subscription can be canceled to change the session management subscription data.

(b) The SMF device can cancel the registration in a given PDU session using Nudm_UECM_Deregistration (SUPI, DNN, PDU Session ID).

<Registration area optimization by MM-SM coordination>

A communication system according to one embodiment may support PDU sessions requiring different quality of service and SSC modes. In PDU sessions using SSC mode 2 or 3, if the UE leaves the service area of the UPF device without mobility based registration, a non-coordinated TAI list immediately after the user plane is activated, May cause the UPF reallocation for the PDU session, the quality of service may be affected by the allocated registration area (i.e., the TAI list).

Thus, some types of PDU sessions may require coordination between the AMF device and the SMF device to reflect SM / UPF related information to the registration area assignment. The communication system according to one embodiment may reflect the interaction between the AMF device and the SMF device for a registration area (TAI list) allocation optimized at a higher level in TS 23.501.

The AMF device may interact with the SMF device (s) to determine the TAI list assigned to the UE in consideration of the SM information. The SMF device may indicate a requirement for interaction during PDU session establishment and each time the AMF device allocates a new TAI list to the UE, the AMF device activates the interaction with the request SMF device (s) .

<General registration>

7 is a flowchart illustrating a registration procedure of a communication system according to an embodiment.

(AN parameters, registration request (registration type, Subscriber Permanent Identifier) or temporary user ID, security parameters, NSSAI, UE 5GCN capability, PDU session state) from the UE to the (R) Lt; / RTI &gt;

In the case of a 5G-RAN, the AN parameters may include, for example, a SUPI or temporary user ID, a selected network and an NSSAI.

The registration type indicates whether the UE is in an "initial registration" (i.e., the UE is in an unregistered state), a mobility registration update (i.e., the UE is registered and initiates registration procedures based on mobility) Quot; (i. E., The UE is in the registered state and initiates the registration procedure in accordance with the above-mentioned periodic registration update timer expiration). If included, the temporary user ID may indicate the last provided AMF device. If the UE is already registered via a non-3GPP access in a PLMN different from the PLMN of the 3GPP access, the UE may not provide the UE with the temporary ID registered by the AMF device during the registration procedure in non-3GPP access.

Security parameters can be used for authentication and integrity protection. NSSAI stands for Network Slice Selection Assistance Information (defined in Section 5.15 of TS 23.501). The PDU session state represents the (previously established) PDU sessions available at the UE. The PDU session establishment request may be piggybacked at the same time as the registration request is transmitted. A HO attach indication can be added, and a flag / bitmap can be activated.

In step 2, if the SUPI was included or the temporary user ID does not indicate a valid AMF device, the (R) AN may select the AMF device, if possible, based on (R) AT and NSSAI.

(R) If the AN can not select the appropriate AMF device, it can forward the registration request to the underlying AMF device. The primary AMF device is responsible for selecting the appropriate AMF device for the UE. The reassignment between the primary AMF device and the selected AMF device may be performed based on 4.2.2.2.3 of TS 23.501, wherein the initial AMF device refers to the base AMF device and the target AMF device refers to the selected AMF device.

In step 3, the (R) AN may send an N2 message (N2 parameters, registration request (registration type, SUPI or temporary user ID, security parameters, NSSAI) to the AMF device.

When the 5G-RAN is used, the N2 parameters may include the location information, the cell identifier, and the RAT type associated with the cell where the UE is camped. If the request type indicated by the UE is a Periodic Registration Update, steps 4 through 17 may be omitted.

Step 4 can be performed conditionally and an information request (complete registration request) can be sent from the new AMF device to the old AMF device.

If the UE's temporary user ID is included in the registration request and the provided AMF device has changed since the last registration procedure, then the new AMF device sends an information request including a complete registration request IE to the UE in order to request the SUPI and MM context of the UE To the old AMF device.

Step 5 can be performed conditionally and an information response (SUPI, MM context, SMF information) can be sent from the old AMF device to the new AMF device.

The old AMF device may respond to the new AMF device with an information response that includes the UE's SUPI and MM context. If the old AMF device holds information about activated PDU sessions, the old AMF device may contain SMF information including SMF identifiers and PDU session identifiers.

Step 6 may be performed conditionally, and an identifier request may be sent from the AMF device to the UE. If the SUPI is not provided by the UE or is not tracked from the old AMF device, the identifier request procedure may be initiated by sending an identifier request message to the UE by the AMF device.

Step 7 may be performed conditionally and an identifier response may be sent from the UE to the AMF device. The UE may respond with an identifier response message including the SUPI.

In step 8, the AMF device may decide to activate the AUSF. In this case, the AMF apparatus can select the AUSF apparatus based on the SUPI.

In step 9, the AUSF device may initiate authentication of UE and NAS security functions. The AUSF device or AMF device can initiate authentication. A procedure including AMF reassignment (e.g., due to network reassignment) may be performed at step 9.

Step 10 may be performed conditionally, and Information Acknowledged may be sent from the new AMF device to the old AMF device. If the AMF device is changed, the new AMF device acknowledges the transmission of the UE MM context. If the authentication / security procedure fails, the registration can be rejected and the new AMF device can send a rejection indicator to the old AMF device. The old AMF device can continue as if it did not receive the information request.

Step 11 may be performed conditionally, and an identifier request may be sent from the AMF device to the UE.

If the PEI is not provided by the UE or retrieved from the old AMF device, the identifier request procedure may be initiated by sending an identifier request message to the UE by the AMF device to retrieve the PEI.

In step 12, optionally, the AMF device may initiate an ME identity check. The PEI check can be performed based on clause 4.7 of TS 23.502.

In step 13, when step 14 is performed, the AMF apparatus can select the UDM apparatus based on the SUPI. The AMF device may select a UDM device based on TS 23.501.

In step 14, if the AMF device has been changed since the last registration procedure, or if a valid subscriber context for the UE is not present in the AMF device, or if the UE has provided a SUPI that does not reference a valid context in the AMF device, Update Location procedure). If so, this may include that the UDM device has initiated a Cancel Location with the old AMF device. The old AMF device can remove the MM context and inform all associated SMF device (s). The new AMF device may generate an MM context for the UE after receiving the AMF-related subscription data from the UDM device.

The interaction of the UDM device and the PCF device may include information related to mobility regulation. PEI may be provided to the UDM device in the update location procedure.

In step 15, conditionally, the AMF device can select a PCF device based on the SUPI. The AMF device may select a PCF device based on TS 23.501. A permanent user ID may be used for PCF device selection.

Step 16 may optionally be performed. In step 16, from the AMF device to the PCF device, a UE context establishment request may be sent. The AMF device may request the PCF device to apply operator policies for the UE.

In step 17, the UE context establishment response may be sent from the PCF device to the AMF device. The PCF device may respond with a UE context establishment request message.

Step 18 can be performed conditionally. In step 18, an N11 request may be sent from the AMF device to the SMF device.

If the AMF device is changed, the new AMF device can inform each of the SMF devices of the new AMF device provided to the UE. The AMF device may check the PDU session state from the UE with the available SMF information. When the AMF device is changed, the available SMF information can be received from the old AMF device. The AMF device may request the SMF device to release any network resources associated with PDU sessions that are not activated at the UE.

When the activated PDU session (s) in the SMF device is requested to be coordinated registration area assignment during PDU session establishment described in < Non-Roaming with Roaming & Roaming &gt;, the AMF device generates a candidate TAI list And can include it in the message. PDU session state logic may be performed by each of the AMF device or the SMF device.

In step 19, an N11 response may be sent from the SMF device to the AMF device. The SMF device may decide to cause UPF reassignment. The SMF device may include the proposed TAI list (s) and the priority (s) for assisting the registration area assignment by the AMF device if the UE's candidate TAI list received in step 18 can not be approved for the PDU session . The proposed TAI list can be derived in an implementation-specific manner based on various information available in the SMF device, for example, information related to PDU session, UPF device (s), policies. The priority may indicate how important the proposed TAI list should be considered.

The SMF device may derive the proposed TAI list by adjusting the candidate TAI list received in step 18. The proposed TAI list may be derived in an implementation-specific manner based on information associated with the activated PDU session (s) and UPF device (s) and SM policies available in the SMF device. The SMF device may transmit the proposed TAI list along with the priority to help the registration area allocation by the AMF device.

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

Step 20 can be performed conditionally. In step 20, a UE context abort request may be sent from the AMF device to the PCF device. If the old AMF device establishes a previously requested UE context in the PCF device, then the old AMF device can abort the UE context in the PCF device.

In step 21, a UE context abort response may be sent from the PCF device to the AMF device.

In step 22, a registration acknowledgment (temporary user ID, registration area, mobility constraints, PDU session state, NSSAI, periodic registration update timer) may be transmitted from the AMF device to the UE. The AMF device may send a Registration Acknowledgment message to the UE indicating that the registration has been approved. If the AMF device has assigned a new temporary user ID, a temporary user ID may be included. If mobility constraints are applied for the UE, mobility constraints may be included. The AMF device may indicate the PDU session state to the UE. The UE may remove internal resources associated with PDU sessions not marked as active in the received PDU session state. If the PDU session state information is in the registration request, the AMF device can indicate the PDU session state to the UE. The NSSAI may include approved S-NSSAIs.

Step 23 can be performed conditionally. In step 23, a registration completion message may be sent from the UE to the AMF device. If a new temporary user ID is assigned, the UE may send a registration completion message to the AMF device.

<Non-Roaming and Roaming with Local Breakout>

In case of roaming, the AMF device may determine whether a PDU session is established in LBO or home routing. In the case of LBO, the procedure described below is the same as the non-roaming case with the difference that the SMF device, UPF device and PCF device are placed in the visited network.

8 is a flow chart illustrating the establishment of a UE Request PDU session for non-roaming and roaming with local breakout according to one embodiment.

The procedure described below assumes that the UE is already registered with the AMF device. Thus, the AMF device has already retrieved user subscription data from the UDM device.

In step 1, the UE may send a NAS message (S-NSSAI, DNN, PDU session ID, N1 SM information) to the AMF device. In order to establish a new PDU session, the UE may generate a new PDU session ID.

The UE initiates a UE Request PDU Session Establishment Procedure by sending a NAS message including a PDU Session Establishment Request in the N1 SM information. The PDU session establishment request may include PDU type, SSC mode, and protocol configuration options.

The NAS message sent by the UE may be encapsulated by the AN in an N2 message including user location information and access technology type information. The SM information may include an SM PDU DN request container that contains information for PDU session authentication by an external DN.

In step 2, the AMF device may determine a message corresponding to a request for a new PDU session based on the PDU session ID used for the existing PDU session (s) of the UE. The AMF device can select an SMF device based on clause 6.3.2 of TS 23.501.

In step 3, the AMF device may send an SM request (SUPI, DNN, S-NSSAI, PDU session ID, AMF ID, N1 SM information, user location information, access technology type) to the SMF device.

The AMF ID may uniquely represent the AMF device provided to the UE. The Nl SM information may include a PDU session establishment request received from the UE. If the AMF device desires to optimize the registration area allocation based on coordination with the SMF device, the AMF device may include the current registration area of the UE.

In step 4a, a subscriber data request (subscriber permanent ID, DNN) may be sent from the SMF device to the UDM device. If the SMF device has not yet retrieved the SM related subscriber data for the UE-related DNN, the SMF device may request the subscriber data.

In step 4b, a subscriber data response may be sent from the UDM device to the SMF device. The subscriber data may include an approved PDU type (s), an approved SSC mode (s), a default QoS profile.

The SMF device may check whether the UE request is compliant with user subscription and local rules. The SMF device indicates to the AMF device that the PDU session ID will be considered released, unless the SMF device has rejected the UE request via the NAS SM signal (including the associated SM rejection cause) relayed by the AMF device, The remaining procedures may be omitted.

In step 5, a PDU session creation request may be sent from the SMF device to the DN via the UPF device.

If the SMF device needs to approve / authenticate the establishment of a PDU session based on TS 23.501 5.6.6, the SMF device shall select the UPF device based on 6.3.3 of TS 23.501, .

If PDU session establishment approval / authentication fails, the SMF device can abort the PDU session establishment procedure and indicate a rejection to the UE.

In step 6a, if a dynamic PCC is deployed, the SMF device may perform PCF device selection.

In step 6b, the SMF device may begin establishing a PDU-CAN session to the PCF device to obtain basic PCC rules for the PDU session.

The purpose of step 5 is to receive the PCC rules before selecting the UPF device. If PCC rules are not required as input for UPF device selection, step 5 may be omitted.

In step 7, the SMF device may select the SSC mode for the PDU session. If step 5 is not performed, the SMF device may select a UPF device based on clause 6.3.3 of TS 23.501. If the PDU type is IPv4 or IPv6, the SMF device may assign an IP address / prefix based on TS 23.501, 5.8.1.

In step 8, if the dynamic PCC device is deployed and PDU-CAN session establishment is not complete in step 5, the SMF device may initiate establishing a PDU-CAN session to the PCF device to obtain basic PCC rules for the PDU session . Otherwise, if the dynamic PCC device is deployed and the PDU type is IPv4 or IPv6, the SMF device may initiate a PDU-CAN session change and provide the assigned UE IP address / prefix to the PCF device.

In step 9, if step 5 is not performed, the SMF device may start the N4 session establishment procedure with the selected UPF device. Otherwise, it can start the N4 session change procedure with the selected UPF device.

In step 9a, the SMF device may send an N4 session establishment / change request to the UPF device and may provide packet detection, regulation and reporting rules to be established for this PDU session. If the CN tunnel information is allocated by the SMF device, the CN tunnel information can be provided to the UPF device at this stage.

In step 9b, the UPF device may respond by sending an N4 session establishment / change response. If CN tunnel information is assigned by the UPF device, CN tunnel information may be provided to the SMF device at this stage.

In step 10, the SM request Ack (N2 SM information (PDU session ID, QoS profile, CN tunnel information), N1 SM information (PDU session establishment acknowledgment (authenticated QoS rule, SSC mode)) is transmitted from the SMF device to the AMF device. Lt; / RTI &gt;

N2 SM information can have information that the AMF device will provide (R) AN (carries). The CN tunnel information may correspond to the core network address of the N3 tunnel corresponding to the PDU session. The QoS profile may provide a mapping between QoS parameters and QoS flow identifiers to the AN. The PDU session ID may be used by the AN signal to the UE to indicate the relationship between the AN resources and the PDU session for the UE to the UE. The Nl SM information may include an acknowledgment of the PDU session to be provided by the AMF device to the UE. A plurality of authentication QoS rules may be included in the PDU session establishment acknowledgment in the N1 SM information and the N2 SM information. The SM request Ack may further include information for determining which UE is to be accessed for use as well as knowing which UE is the subject of the SMF device request by the AMF device. The access information is intended to cover the case where the UE is concurrently connected to 3GPP and non-3GPP accesses.

In order to request interaction between the AMF device and the SMF device for registration area allocation while the PDU session is active, the SMF device may include a Coordinated RA Required in the N11 SM request.

If the candidate TAI list of the UE received in step 18 is not acceptable for the PDU session, the SMF device may include the proposed TAI list (s) and priority (s) to aid in the registration area allocation by the AMF device have. The proposed TAI list can be derived in an implementation-specific manner based on information related to the PDU session, UPF device (s), policies based on various information available in the SMF device, for example. The priority may indicate how important the proposed TAI list should be considered.

 In step 11, an N2 PDU session request (N2 SM information, PDU session establishment acknowledgment) may be sent from the AMF device to the (R) AN. The AMF device may transmit the N2 SM information received from the SMF device in the PDU session establishment acknowledgment and the N2 PDU session request to the (R) AN.

In step 12, from the (R) AN to the UE, the (R) AN issues an AN specific signaling exchange with the UE associated with the information received from the SMF device. For example, in the case of a 3GPP RAN, an RRC connection reconfiguration may occur with the UE establishing the required RAN resources associated with the acknowledged QoS rules for the PDU session request received in step 10.

(R) AN can allocate (R) AN tunnel information for a PDU session. (R) AN may forward the NAS message (PDU session establishment acknowledgment) provided in step 10 to the UE.

If the required RAN resources have been established and the (R) AN tunnel information has been successfully allocated, the (R) AN can only provide the NAS message to the UE.

In step 13, the (R) AN can send an N2 PDU session request Ack ((R) AN tunnel information) to the AMF device.

(R) AN tunnel information may correspond to the access network address of the N3 tunnel corresponding to the PDU session.

In step 14, an SM request (N2 SM information) may be sent from the AMF device to the SMF device. The AMF device may forward the N2 SM information received from the (R) AN to the SMF device.

The UE may indicate to the core network that it has successfully established a PDU session. Using the successful establishment in the (R) AN indicated in step 12, the UE can indicate to the core network that it has successfully established a PDU session. The UE can indicate that the UE has successfully established a PDU session by transmitting a NAS PDU session establishment completion message.

In step 15a, if an N4 session for this PDU session has not already been established, the SMF device may start the N4 session establishment procedure with the UPF device. Otherwise, the SMF device can start the N4 session change procedure with the UPF device. The SMF device can provide AN tunnel information and CN tunnel information. If the SMF device selected CN tunnel information in step 8, then only CN tunnel information needs to be provided.

In step 15b, the UPF device may provide an N4 session establishment / change response to the SMF device.

After step 16, the AMF device may forward the relevant event to the SMF device (e.g., in handover where the (R) AN tunnel information has been changed or the reassignment of the AMF device).

In step 17, if the SMF device to the UE, through the UPF device, PDU type IPv6, the SMF device can generate an IPv6 Router Advertisement and transmit it to the UE via the N4 and the UPF device. During the lifetime of the PDU session, the AMF device may store the relationship of the PDU session ID and the SMF device ID.

A communication system according to an exemplary embodiment may allocate an optimal tracking area to increase the efficiency of a terminal and a network operation. Thus, the degradation of the quality of service can be prevented and the increase of the signaling load can be suppressed. The communication system according to the embodiment may separate the mobility management entity and the session management entity instead of performing the tracking area allocation alone in the mobility management entity or in consideration of the session information and the mobility information together in the merging entity, It is possible to optimize the allocation of the tracking area of the terminal using an efficient signaling exchange.

The components described in the embodiments may be implemented by a programmable logic device such as one or more DSP (Digital Signal Processor), a processor, a controller, an application specific integrated circuit (ASIC), and a field programmable gate array Logic Element, other electronic devices, and combinations thereof. &Lt; RTI ID = 0.0 &gt; At least some of the functions or processes described in the embodiments may be implemented by software, and the software may be recorded in a recording medium. The components, functions and processes described in the embodiments may be implemented by a combination of hardware and software.

The apparatus described above may be implemented as a hardware component, a software component, and / or a combination of hardware components and software components. For example, the apparatus and components described in the embodiments may be implemented within a computer system, such as, for example, a processor, a controller, an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field programmable gate array (FPGA) , A programmable logic unit (PLU), a microprocessor, or any other device capable of executing and responding to instructions. The processing device may execute an operating system (OS) and one or more software applications running on the operating system. The processing device may also access, store, manipulate, process, and generate data in response to execution of the software. For ease of understanding, the processing apparatus may be described as being used singly, but those skilled in the art will recognize that the processing apparatus may have a plurality of processing elements and / As shown in FIG. For example, the processing unit may comprise a plurality of processors or one processor and one controller. Other processing configurations are also possible, such as a parallel processor.

The software may include a computer program, code, instructions, or a combination of one or more of the foregoing, and may be configured to configure the processing device to operate as desired or to process it collectively or collectively Device can be commanded. The software and / or data may be in the form of any type of machine, component, physical device, virtual equipment, computer storage media, or device , Or may be permanently or temporarily embodied in a transmitted signal wave. The software may be distributed over a networked computer system and stored or executed in a distributed manner. The software and data may be stored on one or more computer readable recording media.

The method according to an embodiment may be implemented in the form of a program command that can be executed through various computer means and recorded in a computer-readable medium. The computer-readable medium may include program instructions, data files, data structures, and the like, alone or in combination. The program instructions to be recorded on the medium may be those specially designed and configured for the embodiments or may be available to those skilled in the art of computer software. Examples of computer-readable media include magnetic media such as hard disks, floppy disks and magnetic tape; optical media such as CD-ROMs and DVDs; magnetic media such as floppy disks; Magneto-optical media, and hardware devices specifically configured to store and execute program instructions such as ROM, RAM, flash memory, and the like. Examples of program instructions include machine language code such as those produced by a compiler, as well as high-level language code that can be executed by a computer using an interpreter or the like. The hardware devices described above may be configured to operate as one or more software modules to perform the operations of the embodiments, and vice versa.

While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it is to be understood that the invention is not limited to the disclosed exemplary embodiments. For example, it is to be understood that the techniques described may be performed in a different order than the described methods, and / or that components of the described systems, structures, devices, circuits, Lt; / RTI &gt; or equivalents, even if it is replaced or replaced.

Therefore, other implementations, other embodiments, and equivalents to the claims are also within the scope of the following claims.

Claims (1)

A method of registering a user equipment (UE) in a communication system,
Transmitting, by an access network (AN), an AN message including a registration type indicating that the UE desires to perform initial registration;
Transmitting an identifier response message including an SUCI (SUBSCRIPTION CONCEPTED IDENTIFIER) to the AMF device when receiving an identifier request message from an Access and Mobility Management Function (AMF) device selected by the access network; And
Receiving a registration approval message indicating that the registration request of the UE is approved from the AMF device
The method comprising the steps of:

Images