KR20190088878A - Apparatus and method for network function profile management - Google Patents

Abstract

The present invention relates to a method of network function profile management comprising: a step that a network function repository function receives a registration request from a management system when a new network function (NF) instance is deployed; a step that the NRF that received the registration request adds an NF profile of the new NF instance; and a step that the NRF transmits a registration response to the management system.

Description

[0001] APPARATUS AND METHOD FOR NETWORK FUNCTION PROFILE MANAGEMENT [0002]

The following description relates to a network function profile management method and apparatus, specifically to registration / update / deregistration of a network function profile.

The 5G mobile communication network requires that various services be provided to the UE via 5G network technology. To this end, 5G network technology is a technology designed to support a variety of devices and various services in an end-to-end convergence network structure. Specifically, the 5G network technology is a high-fidelity end-to-end network in which all objects (eg, technology, domain, layer, equipment / device, user interaction, E2E) system.

The present invention can provide a network function profile management method and apparatus for registering / updating / unregistering an NF profile.

According to the network functional profile management method and apparatus of the present invention, the flexibility of the core network structure can be provided according to the introduction of the network virtualization technology, and the efficiency and cost reduction by the network system and resource management are expected.

According to one embodiment, there is provided a method for managing a network function profile, the method comprising: receiving a registration request from a management function, when a new network function instance (new NF instance) is deployed; Adding the Network Function Profile (NF profile) of the new network function instance to the NRF receiving the registration request; And sending the registration response to the management system by the NRF.

The NRF may include the network function instance information, and the network function profile of the network function instance may be a keep up to date NF profile.

The network function profile includes at least one of a network function instance ID, a network function type (NF type), a fully qualified domain name (FQDN) or an IP address of a network function, a PLMN ID, Identifier (s)), NF capacity information, NF Specific Service authorization information, Identification of stored information, Names of supported services, services and at least one of endpoint information of each of the supported service instances.

The identifier related to the network slice may be a network function profile management method, including NSSAI (Network Slice Selection Assistance Information), S-NSSAI (Single-Network Slice Selection Assistance Information), and NSI ID.

According to one embodiment, there is provided a method for managing a network function profile, wherein when a network function profile (NF profile) of a network function instance (NF instance) is changed, a network function repository function (NRF) ; Updating the network capability profile (NF profile) of the network function instance, the NRF having received the update request; And sending the update response to the management system by the NRF.

The NRF may include the network function instance information (or profile), and the network function profile of the network function instance may be a keep up to date NF profile.

The network function profile includes at least one of a network function instance ID, a network function type (NF type), a fully qualified domain name (FQDN) or an IP address of a network function, a PLMN ID, Identifier (s)), NF capacity information, NF Specific Service authorization information, Identification of stored information, Names of supported services, services and at least one of endpoint information of each of the supported service instances.

The identifier related to the network slice may be a network function profile management method, including NSSAI (Network Slice Selection Assistance Information), S-NSSAI (Single-Network Slice Selection Assistance Information), and NSI ID.

According to one embodiment, there is provided a method for managing a network functional profile, comprising the steps of: when a network function instance (NF instance) is removed, a network function repository function (NRF) from a management system receives a deregistration request ; The NRF having received the deregistration request deletes a network capability profile (NF profile) of the network function instance; And sending the deregistration response to the management system by the NRF.

The NRF may include the network function instance information, and the network function profile of the network function instance may be a keep up to date NF profile.

The network function profile includes at least one of a network function instance ID, a network function type (NF type), a fully qualified domain name (FQDN) or an IP address of a network function, a PLMN ID, Identifier (s)), NF capacity information, NF Specific Service authorization information, Identification of stored information, Names of supported services, services and at least one of endpoint information of each of the supported service instances.

The identifier related to the network slice may be a network function profile management method, including NSSAI (Network Slice Selection Assistance Information), S-NSSAI (Single-Network Slice Selection Assistance Information), and NSI ID.

According to one embodiment, there is provided a communication device for managing a network functional profile, the communication device comprising: a memory including a processor and instructions readable by the computer, wherein when the instruction is executed in the processor, the network function repository function (NRF) receives a registration request from the management system when the new NF instance is deployed, and the NRF, which received the registration request, A function profile, an NF profile), and the NRF transmits a registration response to the management system.

The NRF may include the network function instance information, and the network function profile of the network function instance may be a communication apparatus that manages the network function profile, which is kept up to date in the NF profile.

The network function profile includes at least one of a network function instance ID, a network function type (NF type), a fully qualified domain name (FQDN) or an IP address of a network function, a PLMN ID, Identifier (s)), NF capacity information, NF Specific Service authorization information, Identification of stored information, Names of supported services, services and at least one of endpoint information of each supported service instance. < Desc / Clms Page number 7 >

The identifier related to the network slice may be a communication device that manages a network function profile, including a Network Slice Selection Assistance Information (NSSAI), Single-Network Slice Selection Assistance Information (S-NSSAI), and an NSI ID.

According to one embodiment, there is provided a communication device for managing a network function profile, the communication device comprising: a memory including a processor and instructions readable by the computer, wherein, when the instruction is executed in the processor, When the network function profile (NF profile) of the network function instance (NF instance) is changed, the network function repository function (NRF) receives an update request from the management system, and the NRF, A network function profile (NF profile), and the NRF sends an update response to the management system.

The NRF may include the network function instance information, and the network function profile of the network function instance may be a communication apparatus that manages the network function profile, which is kept up to date in the NF profile.

The network function profile includes at least one of a network function instance ID, a network function type (NF type), a fully qualified domain name (FQDN) or an IP address of a network function, a PLMN ID, Identifier (s)), NF capacity information, NF Specific Service authorization information, Identification of stored information, Names of supported services, services and at least one of endpoint information of each supported service instance. < Desc / Clms Page number 7 >

The identifier related to the network slice may be a communication device that manages a network function profile, including a Network Slice Selection Assistance Information (NSSAI), Single-Network Slice Selection Assistance Information (S-NSSAI), and an NSI ID.

According to one embodiment, there is provided a communication device for managing a network function profile, the communication device comprising: a memory including a processor and instructions readable by the computer, wherein, when the instruction is executed in the processor, The network function repository function (NRF) receives a deregistration request from the management system when the NF instance is removed, and the NRF, which received the deregistration request, (NF profile), and the NRF sends a deregistration response to the management system.

The NRF may include the network function instance information, and the network function profile of the network function instance may be a communication apparatus that manages the network function profile, which is kept up to date in the NF profile.

The network function profile includes at least one of a network function instance ID, a network function type (NF type), a fully qualified domain name (FQDN) or an IP address of a network function, a PLMN ID, Identifier (s)), NF capacity information, NF Specific Service authorization information, Identification of stored information, Names of supported services, services and at least one of endpoint information of each supported service instance. < Desc / Clms Page number 7 >

The identifier related to the network slice may be a communication device that manages a network function profile, including a Network Slice Selection Assistance Information (NSSAI), Single-Network Slice Selection Assistance Information (S-NSSAI), and an NSI ID.

According to an embodiment, a network function profile management method and apparatus for registering / updating / deregistering an NF profile can be provided.

According to one embodiment, the flexibility of the core network structure can be provided by the introduction of the network virtualization technology by the network function profile management method and apparatus, and the efficiency maximization and the cost reduction effect by the network system and resource management are expected .

Figure 1 illustrates a RM (Registration Management) state model of a user terminal according to an embodiment.
FIG. 2 illustrates a CM state transition at a user terminal according to an exemplary embodiment.
3 is a flowchart illustrating a registration procedure of a UE in a communication system according to an exemplary embodiment.
4 is a diagram illustrating a reference architecture for network slicing according to one embodiment.
5 is a diagram illustrating a structure of a network slice according to an embodiment.
6 is a diagram illustrating an example of a network slice instance and a service instance in accordance with one embodiment.
7 is a diagram illustrating an example of configuring a service instance according to one embodiment.
FIG. 8 is a diagram illustrating an example of selecting NSI in the UE registration procedure according to an embodiment.
9 is a diagram illustrating an example of selecting an NSI and an NFI in a PDU session establishment procedure according to an embodiment.
10 is a diagram illustrating an example of a repository in accordance with one embodiment.
11, there is shown an NRF 1110 that performs network function instance selection / discovery functions in accordance with one embodiment.
12 is a diagram illustrating an NF discovery service according to an embodiment of the present invention.
13 is a diagram illustrating an NF discovery service through PLMSs according to an embodiment.
14 illustrates a network service registration procedure according to one embodiment.
15 shows a network functional service update procedure according to one embodiment.
16 illustrates a NF service deregistration procedure, according to one embodiment.
Figure 17 illustrates network capability / network capability service discovery in the same PLMN, according to one embodiment.
18 illustrates network capability / network capability service discovery through PLMNs, in accordance with one embodiment.
19 is a diagram illustrating an NF profile management interface, according to one embodiment.

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.

Various modifications may be made to the embodiments described below. It is to be understood that the embodiments described below are not intended to limit the embodiments, but include all modifications, equivalents, and alternatives to them.

The terms first or second may be used to describe various components, but such terms should be understood only for the purpose of distinguishing one component from another. For example, the first component may be referred to as a second component, and similarly, the second component may also be referred to as a first component.

The terms used in the examples are used only to illustrate specific embodiments and are not intended to limit the embodiments. The singular expressions include plural expressions unless the context clearly indicates otherwise. In this specification, the terms "comprises" or "having" and the like refer to the presence of stated features, integers, steps, operations, elements, components, or combinations thereof, But do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, 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 embodiment belongs. Terms such as those defined in commonly used dictionaries are to be interpreted as having a meaning consistent with the contextual meaning of the related art and are to be interpreted as either ideal or overly formal in the sense of the present application Do not.

In the following description of the present invention with reference to the accompanying drawings, the same components are denoted by the same reference numerals regardless of the reference numerals, and redundant explanations thereof will be omitted. In the following description of the embodiments, a detailed description of related arts will be omitted if it is determined that the gist of the embodiments may be unnecessarily blurred.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

The terms that may be used or used herein according to one embodiment are as follows.

5G Access Network: An access network that includes a 5G-RAN and / or a Non-3GPP AN connecting to a 5G core network.

5G Core Network: Core network. 5G access network.

5G QoS Flow: Best granularity for QoS forwarding processing in 5G systems. All traffic mapped to the same 5G QoS flow can receive the same forwarding process (eg, scheduling policy, queue management policy, rate shaping policy, RLC configuration, etc.). A separate 5G QoS flow may be required to provide different QoS forwarding processing.

5G QoS indicator (5QI): Scala used as a reference for specific QoS forwarding behavior (eg packet loss rate, packet delay budget) provided in 5G QoS flows. This may be implemented in the access network by 5QI reference node specific parameters that control QoS forwarding processing (e.g., scheduling weights, tolerance thresholds, queue management thresholds, link layer protocol configuration, etc.).

5G-RAN: Wireless access network supporting one or more of the following options with common characteristics connected to 5GC:

1) Standalone new radio.

2) The new radio can be an anchor with E-UTRA extension.

3) Stand-alone E-UTRA.

4) E-UTRA can be an anchor with New Radio extension.

5G system: 3GPP system consisting of 5G access network (AN), 5G core network and UE.

Allowed NSSAI: eg NSSAI provided by the serving PLMN *? *. A registration procedure indicating the NSSAI allowed by the network for the UE in the serving PLMN for the current registration area.

Permissive Area: The area where the UE can initiate communication.

Established NSSAI: NSSAI provisioned to the UE.

Forbidden area: An area where the UE can not initiate communication.

Initial registration: UE registration in RM-DEREGISTERED state.

Mobility pattern: A network concept that determines UE mobility parameters within the NF.

Mobility Registration Update: UE re-enrollment when entering a new TA outside the TAI list.

Network function: 3GPP can adopt the processing function in the network defining the function operation and the 3GPP definition interface or can define it in 3GPP.

Non-allowed area: An area where the UE can initiate the registration process but no other communication can begin.

PDU Connectivity Service: A service that provides PDU exchange between UE and data network.

PDU session: The association between the UE and the data network providing the PDU connection service. The connection type may be IP, Ethernet or unstructured.

Regular registration update: Re-enroll the UE when the periodic registration timer expires.

Requested NSSAI: The NSSAI that the UE can provide to the network.

Service continuity: An uninterrupted user experience, including when IP addresses and / or fixed points change.

Session Continuity: The continuity of the PDU session. For a PDU session of IP type "session continuity ", this may mean that the IP address is maintained for the lifetime of the PDU session.

Non-seamless Non-3GPP offload: offload of user plane traffic through non-3GPP access without passing through N3IWF or UPF and untrusted.

<Abbreviations>

- 5GC: 5G Core Network (5G Core Network)

- AF: Application Function

- 5GS: 5G system (5G System)

- 5G-AN: 5G Access Network (5G access network)

- 5G-GUTI: 5G Globally Unique Temporary Identifier

- AMF: Access and Mobilty Management Function (Access and Mobilty Management Function)

- CP: Control Plane

- DC: Dual Connectivity

- DL: Downlink (Downlink)

- DN: Data Network

- DNN: Data Network Name

- HR: Home Routed (roaming)

- LADN: Local Area Data Network

- MICO: Mobile Initiated Connection Only

- NF: Network function

- NR: New Radio

- NEF: Network Exposure Function

- NOP: Network Operator

- NRF: Network Function Repository Function

- NSaaS: Network Slice as a Service

- NSaaSC: Network Slice as a Service Customer

- NSaaSP: Network Slice as a Service Provider

- NSC: Network Slice Customer

- NSI: Network Slice Instance

- NSP: Network Slice Provider

- OTT: Over The Top

- PCF: Policy Control Function

- (R) AN: (Radio) Access Network (Radio Access Network)

- SSC: Session and Service Continuity

- UDM: Unified Data Management

- UL: Uplink

- UPF: User Plane Function

<Registration Management>

Registration management is used to register or unregister a user terminal / user in the network and is used to establish a user context in the network.

The user terminal / user needs to register in the network in order to receive the service that requires registration. Once registered and applicable, the user terminal may 1) periodically (periodically update the registration) to make it reachable; Or 2) on move (mobility registration update); Or 3) update the registration on the network to update functionality or renegotiate protocol parameters:

The initial registration procedure involves the execution of network access control functions (i.e., user authentication and access authorization based on subscription profiles of the UDM). As a result of the registration procedure, the identifier of the serving AMF device for the UE in the UE registered access will be registered in the UDM.

The registration management procedure is applicable to both 3GPP access and non-3GPP access. 3GPP and non-3GPP registration states are independent of each other.

The following two registration management states reflecting the registration status of the user terminal in the selected PLMN are used in the user terminal and the AMF device:

1. RM-DEREGISTERED 2. RM-REGISTERED

Figure 1 illustrates a RM (Registration Management) state model of a user terminal according to an embodiment.

1. RM-DEREGISTERED state

In RM-DEREGISTERED state, the user terminal is not registered in the network. The user terminal is not reachable by the AMF device because the user terminal context in the AMF device does not have valid location or routing information for the user terminal. However, a portion of the user terminal context may still be stored in the user terminal and the AMF device for the sake of avoiding authentication procedures during all registration procedures.

In the RM-DEREGISTERED state, the user terminal:

I) If it is necessary to receive a service that requires registration, it tries to register with the selected PLMN using the initial registration procedure. Ii) Upon receipt of the registration rejection at the time of initial registration, the RM-DEREGISTERED state is maintained. Iii) Upon receipt of the registration approval, it enters the RM-REGISTERED state.

If the UE RM status of the AMF device is RM-DEREGISED, then the AMF device:

I) accept the initial registration of the user terminal by sending a registration grant to the user terminal, if applicable, and enter the RM-REGISTERED state for the UE; Or ii) rejecting the initial registration of the user terminal by sending a registration rejection to the user terminal, if applicable.

2. RM-REGISTERED state

In the RM-REGISTERED state, the user terminal is registered in the network. In the RM-REGISTERED state, the user terminal can receive services that need to register with the network.

In the RM-REGISTERED state, the user terminal:

I) perform the mobility registration update procedure if there is no current TAI of the serving cell in the list of TAIs received from the network by the user terminal in order to maintain registration and enable the AMF device to page the user terminal; Ii) Perform a periodic registration update procedure triggered by the expiration of the periodic update timer to notify the network that the user terminal is still active. Iii) update the function information by performing a registration information update procedure or renegotiate protocol parameters with the network. Iv) Performs the deregistration procedure and enters RM-DEREGISTERED state when the user terminal should no longer be registered in the PLMN. The user terminal may decide to unsubscribe from the network at any time. V) Enter RM-DEREGISTERED state when receiving registration decline message or deregistration message. The operation of the user terminal depends on the 'cause value' of the registration rejection or de-registration message.

If the UE RM state of the AMF device is RM-REGISTERED, the AMF device shall:

I) Perform the deregistration procedure and enter the RM-DEREGISTERED state when the user terminal should no longer be registered in the PLMN. The network may decide to de-register the user terminal at any time; Ii) implicit deregistration at any time after the expiration of the implicit de-registration timer. After implicit deregistration, the AMF device enters the RM-DEREGISTERED state for the user terminal. Iii) approve or reject a registration request or service request from the user terminal, where applicable;

<Connection Management>

Connection management is used to establish or release a signaling connection between the user terminal and the AMF device. Connection management includes the ability to establish and release a signaling connection between a user terminal and an AMF device via N1. This signaling connection is used to enable the exchange of NAS signaling between the user terminal and the core network. This includes both an AN signaling connection (3GPP access via N3GPP access or RRC connection via UE-N3IWF connection) between the user terminal and the AN and N2 connection to the user terminal between the AN and the AMF device.

Two CM states are used to reflect the NAS signaling connection of the AMF device and the user terminal:

1. CM-IDLE 2. CM-CONNECTED

The CM states for 3GPP access and Non-3GPP access are independent of each other. That is, when one is in the CM-CONNECTED state and the other is in the CM-IDLE state.

FIG. 2 illustrates a CM state transition at a user terminal according to an exemplary embodiment.

1. CM-IDLE state

The user terminal in the CM-IDLE state has no established NAS signaling connection with the AMF device via N1. The user terminal performs cell selection / cell reselection and performs PLMN selection.

The user terminal in the CM-IDLE state has no AN signaling connection, N2 connection and N3 connection.

When the user terminal is in the CM-IDLE state and the RM-REGISTERED state, the user terminal performs the following:

I) If the user terminal is not in the MICO mode, it performs a service request procedure to respond to paging. Ii) Perform a service request procedure when the user terminal has uplink signaling or user data to be transmitted. Certain conditions apply to the LADN.

Whenever an AN signaling connection is established between the user terminal and the AN (whenever the UE enters the RRC connection state via 3GPP access or establishes a UE-N3IWF connection via non-3GPP access), the user terminal enters the CM-CONNECTED state . The transmission of the initial NAS message (Registration Request, Service Request or Deregistration Request) initiates a transition from the CM-IDLE to the CM-CONNECTED state.

If the user terminal status of the AMF device is CM-IDLE and RM-REGISTERED, then the AMF device does the following:

I) If the UE is not prevented from responding, it performs a network triggered service request procedure when it has mobile-terminated data or signaling to be sent to the user terminal by sending a paging request to the user terminal.

Whenever an N2 connection is established for the user terminal between the AN and the AMF device, the AMF device enters the CM-CONNECTED state for the user terminal. Receipt of the initial N2 message (e.g., the user terminal message at the beginning of N2) initiates the transition of the AMF device from the CM-IDLE to the CM-CONNECTED state.

The user terminal and the AMF device can optimize the power efficiency and signaling efficiency of the user terminal when in the CM-IDLE state.

One. CM-CONNECTED state

The user terminal in the CM-CONNECTED state has NAS signaling connection with the AMF device via N1. The NAS signaling connection uses the RRC connection between the UE and the NG-RAN and the NGAP UE association between the AN and AMF devices for 3GPP access. The UE may be in a CM-CONNECTED state with a NGAP UE association not associated with any TNLA between the AN and the AMF device. Upon completion of the NAS signaling procedure, the AMF device may decide to release the NAS signaling connection with the user terminal.

In the CM-CONNECTED state, the UE performs the following:

I) enters the CM-IDLE state whenever the AN signaling connection is released (whenever an RRC idle state entry through 3GPP access or a release of the UE-N3IWF connection via non-3GPP access is detected by the user terminal) .

If the UE CM state of the AMF device is CM-CONNECTED, the AMF device performs the following:

I) Upon completion of the AN release procedure, each time a logical NGAP signaling connection and an N3 user plane connection to the UE are released, the UE enters the CM-IDLE state.

Until the UE is deregistered from the core network, the AMF device may maintain the UE CM state in the AMF device in the CM-CONNECTED state.

A UE in the CM-CONNECTED state may be in an RRC disabled state. When the UE is in the RRC disabled state the following applies:

I) UE reachability is managed by the RAN with assistance information from the core network. Ii) UE paging is managed by the RAN. Iii) The UE monitors paging with the CN's (5G S-TMSI) and RAN identifier.

<Session Management>

The 5G core network supports the PDU connectivity service. The PDU connectivity service provides for the exchange of PDUs between the user terminal and the data network. The PDU connectivity service is supported through PDU sessions established in response to a request from the user terminal.

The subscription information includes a plurality of data network names and a default data network name. If a valid data network name is not provided in the PDU session establishment request transmitted to the 5G core network, the user terminal is assigned to the default data network name

Each PDU session supports one PDU session type. The PDU session supports the exchange of a single type of PDU session requested by the user terminal in the establishment of the PDU session.

The PDU session is established using the NAS SM signaling exchanged between the UE and the SMF device via N1, the PDU session being established upon request of the user terminal, modified according to the request of the user terminal and the 5G core network, , And may be released at the request of the user terminal and the 5G core network. At the request of the application server, the 5G core network can trigger a specific application of the UE. Upon receipt of the trigger message, the user terminal forwards to the identified application. An application identified at the user terminal may establish a PDU session for a particular DNN.

The SMF device may support PDU sessions for LADNs where access to the data network is available only in a particular LADN service area.

The SMF device checks whether the user terminal request is compliant with the user subscription. To do this, it retrieves and requests update notifications for SMF device level subscription data from the UDM. Such data can be represented for each DNN and, where applicable, for each S-NSSAI:

I) Allowed PDU session type and default PDU session type. Ii) Allowed SSC mode and default SSC mode. Iii) QoS information: Subscribed Session-AMBR, Default 5QI, and Default ARP. Iv) Fixed IP address / prefix.

A user terminal registered through a plurality of accesses selects access to establish a PDU session. The HPLMN may send a policy to the user terminal to guide the selection of access to establish a PDU session to the user terminal.

The user terminal may request to move the PDU session between the 3GPP access and the non-3GPP access. The decision to move the PDU session between 3GPP access and non-3GPP access is done on a per-PDU session basis. That is, the user terminal may have some PDU sessions using 3GPP access at a given time, and other PDU sessions may use non-3GPP access.

In a PDU session establishment request sent over the network, the user terminal provides a PDU session identifier. The PDU session ID is unique to each user terminal and is an identifier used to uniquely identify one of the user terminal's PDU sessions. The PDU session ID is stored in the UDM to support handover between 3GPP and non-3GPP access when different PLMNs are used for both accesses. The UE may also provide:

I) PDU session type. Ii) S-NSSAI. Iii) DNN (Data Network Name). Iv) SSC mode.

The user terminal may establish a plurality of PDU sessions to the same data network or another data network at the same time through the 3GPP and non-3GPP access networks.

The user terminal is served by another UPF device that establishes multiple PDU sessions for the same data network and terminates N6.

A user terminal having a plurality of established PDU sessions may be served by another SMF device.

The SMF device can be registered and unregistered in PDU session granularity of the UDM.

The user plane path of different PDU sessions (for the same or different data network names) belonging to the same user terminal may be completely disjoint between the UPF device and the AN that interfaces with the data network.

<Registration Management Procedures>

<General>

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

When a user terminal performs initial registration with a communication system according to an exemplary embodiment or changes from a CM_CONNECTED mode and a CM_IDLE mode to a new tracking area (TA) outside the registration area of the user terminal, Update), when the user terminal needs to perform a periodic registration update (in accordance with a time period of predetermined deactivation), the user terminal additionally requests the negotiated protocol parameters or performance When there is a need to update capabilities, a registration procedure may be used.

The generic 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 user terminal. 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 be subject to operator &apos; s placement selection.

<Registration General>

3 is a flowchart illustrating a registration procedure of a UE in a communication system according to an exemplary 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 that the UE is in the initial registration (i.e., the UE is in the RM-DEREGISTERED state), the Mobility Registration Update (i.e., the UE is in the RM-REGISTERED state and initiates the 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) . If the UE has not yet 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. Only when the home network is provisioned with a public key to protect the SUPI at the UE, the SUCI may be included. 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 3GPP access via a non-3GPP access in a PLMN other than the unregistered PLMN or the registered PLMN (i.e., the same PLMN as the registered PLMN), then the UE may notify the AMF device Lt; RTI ID = 0.0 &gt; 5G-GUTI &lt; / RTI &gt; Further, if the UE is different from the new PLMN (i.e., the same PLMN as the unregistered PLMN or the registered PLMN) and has already been registered through the 3GPP access in the PLMN (i.e., 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 verify whether the S-NSSAI (s) in the requesting NSSAI has been granted based on the subscribed S-NSSAIs, -NSSAI mapping to the S-NSSAIs of the set NSSAI for HPLMN, respectively.

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. 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 can select the AMF device. 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 Namf_Communication_UEContextTransfer (complete registration request) can be sent from the new AMF device to the existing 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 &lt; RTI ID = 0.0 &gt; To initiate the Namf_Communication_UEContextTransfer service operation on an existing AMF device including the &lt; RTI ID = 0.0 &gt; The existing AMF apparatus can use the integrity-protected complete registration request IE to confirm whether the context transfer service operation start corresponding to the UE is requested.

The existing 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 a new AMF device has already received UE contexts from an existing 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 existing AMF device to the new AMF device.

An existing 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 existing AMF device holds information about established PDU sessions, the existing AMF device may include SMF information including S-NSSAI (s), SMF identifiers and PDU session ID . If an existing AMF device holds information about the active NGAP UE-TNLA bound to the N3IWF, then the existing 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 an existing 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 specified HPLMN.

In step 8, the AMF device may decide to activate UE authentication by operating the AUSF. In this case, the AMF device can select an AUSF device based on SUPI or SUCI.

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 by the Nudm_UEAuthenticate_Get operation. The AUSF device can detect the UDM. 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.

When network slicing is used, the AMF device can determine whether the initial AMF device is to be rerouted for the registration request.

In step 9b, the AMF device may initiate NAS security functions.

In step 9c, when the NAS security function setup is completed, the AMF device can start the NGAP procedure. 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 a security context to protect messages exchanged with the UE.

Step 10 may be performed conditionally and Namf_Communication_RegistrationCompleteNotify may be sent from the new AMF device to the existing AMF device.

When the AMF device is changed, the new AMF device can notify the existing 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 may be rejected and the new AMF device may activate the Namf_Communication_RegistrationCompleteNotify service operation with the reject indication reason code towards the existing AMF device. The existing AMF device can continue as if the UE context transfer service operation was not received.

If one or more S-NSSAIs in the existing 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 activate a Namf_Communication_RegistrationCompleteNotify service operation that includes a rejection cause (e.g., S-NSSAI is no longer available) and a reject PDU session ID to an existing AMF device. In this case, the new AMF device may change the PDU session state accordingly. The existing 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.

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 an existing 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. For emergency registration, if the PEI is blocked, operator policies can decide whether to start or stop the emergency registration process.

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 refer to 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 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 may retrieve 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 obtaining 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 may ignore the unsuccessful registration response of the UDM device and continue the registration procedure.

In step 14c, if one exists, when the UDM device stores the associated access type with the providing AMF device shown in step 14a, it will cause the UDM device to start Nudm_UECM_DeregistrationNotification with the existing AMF device corresponding to 3GPP access Cause. The existing AMF device can remove the MM context of the UE. If the provided NF cancellation reason indicated by the UDM is an initial registration, the existing 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 existing AMF device. The SMF device may release the PDU session (s) upon receipt of this notification.

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

In step 15, if the AMF device has decided to start the PCF communication, for example, if the AMF device has not yet acquired an Access and Mobility policy for the UE, And 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 existing AMF device in step 5 and is 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 have. If the PCF device identified by the PCF ID is not available (e.g., no response from the PCF device), or if there is no PCF ID received from the existing AMF device in step 5, the AMF device may select the PCF device .

Step 16 may optionally be performed and the new AMF device may perform Policy Association Establishment during the registration procedure. 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 restriction (e.g., UE location) for adjustment, or if the PCF device updates its mobility restriction 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 that has been continuously executed from Step 5 can be executed to complete the user plane connection activation without acknowledgment of the MM NAS service transmitted from the AMF device to the (R) AN.

The SMF device may decide to cause a PSA to change or delete (e.g., intermediate UPF insertion). 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 ". This procedure can 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 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 can be triggered at the end of this procedure.

In step 19, the 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, an N2 AMF mobility response may be sent.

In step 21, a new AMF device sends a registration grant (5G-GUTI, registration domain, mobility constraints, PDU session state, allowed NSSAI, [mapping of allowed NSSAIs], 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 existing 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 that are 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 LADN information for the LADNs 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. In order to set up the IMS voice on the PS session support indicator, the AMF device needs to perform a compatibility request procedure to check the UE / RAN radio information and the RAN radio capability associated with the IMS voice on the PS and UE compatibility. 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 can release the signaling connection with the UE. 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 complete.

<Network Sharing>

1. General Concepts

A network sharing architecture may allow multiple participating operators to share resources on a single shared network according to an agreed upon allocation scheme. The shared network includes a radio access network. Shared resources include radio resources.

A shared network operator can allocate shared resources to participating operators based on planned current requirements and service level agreements.

In a 5G system, a 5G Multi-Operator Core Network (MOCN) network share architecture with shared RANs can be supported. A 5G MOCN, including UE, RAN and AMF, may support the ability for an operator to use at least one PLMN ID.

2. Network selection

A UE subscribing to one of the shared core network operators may select the core network operator while receiving the subscribed service from the core network operator while in the coverage area of the shared network.

Each cell of the shared NG-RAN may include PLMN-IDs for the core network operator available in the shared network.

When the UE performs initial registration to the network, one of the available PLMNs may be selected to service the UE. The UE may use all broadcast PLMN-IDs received in the PLMN (re) selection procedure. The UE may inform the NG-RAN of the selected PLMN so that the NG-RAN can correctly route. The NG-RAN can inform the core network of the selected PLMN.

The UEs that are available for servicing the location of the selected PLMN do not change to other available PLMNs while being initially serviced by the shared network after first registering with the shared network according to any network. The network selection procedure may cause the UE to perform reselection of another available PLMN. In addition, the network can not move the UE to another available PLMN as long as there is a selected PLMN available to service the location of the UE.

3. Network Sharing and Network Slicing

The network slice is defined within the PLMN. Network shares are performed between different PLMNs. In the case of a network share, each PLMN sharing an NG-RAN defines and supports a set of PLMN-specific slices supported by a common NG-RAN.

The network slicing introduced herein in accordance with one embodiment may be as follows.

The network slice may include the following:

- Core network control plane and user plane network function

- 5G wireless access network

- N3IWF can function for non-3GPP access networks.

The network slice may vary depending on the features supported and network function optimization. The operator may provide exactly the same functionality but place the same network slice instance for different groups of UEs. This may be because the customer is able to provide other dedicated services or devote to the customer.

A single UE may be able to be serviced simultaneously by more than one network slice instance via 5G-AN. The AMF instance serving the UE may logically belong to each network slice instance serving the UE. That is, this AMF instance may be common to the network slice instance serving the UE.

A PDU session may belong to one specific network slice instance per PLMN. Other network slice instances may not share PDU sessions, but other slices may have slice-specific PDU sessions that use the same DNN.

Identification and selection of network slices: S-NSSAI and NSSAI

The S-NSSAI (single network slice selection support information) can identify the network slice.

The S-NSSAI can consist of:

- Slice / Service type (SST): It can indicate expected network slice operation in terms of function and service.

Slice Differentiator (SD), which is optional information to supplement the Slice / Service type - allows differentiation in selecting network slice instances from potential multiple network slice instances that comply with all Slice / Service types shown. This information can be called SD.

The S-NSSAI may have a standard value or a PLMN specific value. The S-NSSAI with a PLMN unique value is associated with the PLMN ID of the PLMN to which it is assigned. The S-NSSAI shall not be used by the UE in an access-stratum procedure in a PLMN other than the PLMN to which the S-NSSAI is associated.

The NSSAI may be a collection of S-NSSAI (Single Network Slice Selection Support Information). Each S-NSSAI can support the network when selecting a particular network slice instance. The CN portion of the network slice instance (s) serving the UE is selected by the CN.

(R) AN may use the NSSAI requested in the access layer signaling to process the UE control plane connection before informing the (R) AN of the NSSAI that the 5GC is allowed. The requested NSSAI is not used by the RAN for routing when the UE also provides a temporary user ID.

Once the UE is successfully registered, the CN informs the (R) AN by providing the entire NSSAI allowed for the control plane side.

Once a PDU session is established for a particular slice instance, the CN can provide the R-AN with an S-NSSAI corresponding to the slice instance to which this PDU session belongs so that the RAN can perform the access-specific function.

Subscription aspects

The subscription data may include the S-NSSAI of the network slice to which the UE subscribes. One or more S-NSSAIs may be marked as primary S-NSSAIs. If the S-NSSAI is indicated by default, the UE is expected to serve the UE with the relevant network slice in the registration request even if the UE does not transmit any S-NSSAI to the network.

The UE subscription data may include a default DNN value for a given S-NSSAI.

The NSSAI provided by the UE in the registration request is verified against the subscription data of the user.

UE NSSAI configuration and NSSAI storage aspects

The UE may be configured by the HPLMN with an NSSAI configured per PLMN *? *. The configured NSSAI may be specific to the PLMN and the HPLMN indicates which PLMN (s) each configured NSSAI applies, including whether the configured NSSAI is applied to all PLMNs. E. The configured NSSAI conveys the same information regardless of the PLMN the UE is accessing (e.g., this may be possible for NSSAI including only standardized S-NSSAI). When providing the requested NSSAI to the network upon registration, the UE of the given PLMN may only use the S-NSSAI belonging to the configured NSSAI if the corresponding PLMN is present.

If the registration procedure of the UE is successfully completed, the UE may obtain from the AMF an allowed NSSAI for this PLMN that may include one or more S-NSSAIs. The allowed NSSAI may take precedence over the NSSAI configured for this PLMN. The UE may only need to use the allowed NSSAI S-NSSAI corresponding to the network slice for the subsequent nNtwork Slice selection procedure of the serving PLMN.

For each PLMN, the UE may store the configured NSSAI and store the NSSAI if allowed. When the UE receives the allowed NSSAI for the PLMN, the UE may have to store the PLMN and override the previously stored allowed NSSAI for this PLMN.

Setting up a user plane connection to a data network via a network slice instance can be configured in two steps.

- Perform RM procedures to select AMFs that support the required network fragments

Establishing one or more PDU sessions in the requested data network via the network slice instance (s)

Serving AMF Selection to Support Network Slice

Enroll in a network engraving set

UE with NSSAI configured or allowed for PLMN

When the UE registers with the PLMN, if the UE for this PLMN has a configured NSSAI or allowed NSSAI f, the UE sends a request (for example, for the UE) to the network of the RRC and the NAS layer NSSAI may be required. If a temporary user ID has been assigned to the UE, in addition to the temporary user ID, it may include the slice (s) the UE wishes to register.

The requested NSSAI may be one of the following:

A configured NSSAI or a subset thereof if the UE does not have an NSSAI granted to the current PLMN; or

- if the UE has an NSSAI allowed for the current PLMN, the allowed NSSAI or a subset thereof,

- the permitted NSSAI or a subset thereof as described below and one or more S-NSSAIs of the NSSAI that have not been previously permanently denied (as defined below) and have no corresponding S-NSSAI in the accepted NSSAI Can be selected by the network.

The subset of NSSAIs that are configured may consist of a combination of S-NSSAIs, including one or more S-NSSAI (s) of configured NSSAIs to which S-NSSAIs are applied to this PLMN. And may have been previously added by the UE in the requested NSSAI.

The subset of allowed NSSAIs may consist of a combination of S-NSSAIs containing one or more S-NSSAIs in the last allowed NSSAI for this PLMN.

The UE may provide the requested NSSAI with the S-NSSAI from the Configured NSSAI that the UE previously provided for the serving PLMN in the current registration area.

The UE may need to include the requested NSSAI in the RRC connection setup and the NAS message. The RAN may need to route the NAS signal between the selected AMF using the requested NSSAI obtained during the UE and RRC connection establishment. If the RAN can not select the AMF based on the requested NSSAI, the NAS signal can be routed from the set to the AMF.

Upon successful registration, the UE is provided with a temporary ID by the serving AMF. The UE may include this temporary ID in all RRC connection establishment during subsequent initial access so that the RAN can route the NAS signaling between the UE and the appropriate AMF.

The serving PLMN may also return a new granted NSSAI that identifies the network slice allowed by the serving PLMN for the UE. The UE may store this new allowed NSSAI and ignore the previously stored allowed NSSAI for this PLMN.

The network may individually reject the S-NSSAI provided by the UE in the NSSAI requested for the rejected reason. The network may also determine whether the rejection is permanent (e.g., S-NSSAI is not supported by PLMN *? * At least in the current registration area) or transient (e.g., the nNetwork slide corresponding to S- Not possible).

Upon receiving a Requested NSSAI and a Temporary ID in the RRC from the UE, the RAN can send a request to the AMF if the RAN can reach the AMF corresponding to the Temporary ID. Otherwise, the RAN may select the appropriate AMF based on the requested NSSAI provided by the UE and send the request to the selected AMF. If the RAN can not select an AMF based on the requested NSSAI, the request is sent in the default AMF.

UE without NSSAI for PLMN

When the UE registers with the PLMN, the RAN may have to route all of this UE signaling to / from the default AMF from the UE if the UE does not have a configured NSSAI or allowed NSSAI for this PLMN. The UE MUST NOT indicate the NSSAI in the RRC connection establishment or initial NAS message unless there is an NSSAI configured for that PLMN or an allowed NSSAI. If registration is successful, the UE is provided with a temporary ID by the AMF in the subscriber PLMN and an allowed NSSAI that identifies the slice allowed by the serving PLMN for the UE that is part of the subscribed default S-NSSAI (s). . &Lt; / RTI &gt; The UE may have to include this temporary ID in all RRC connection settings during subsequent initial access so that the RAN can route the NAS signaling between the UE and the appropriate AMF.

Modification of the network slice set for the UE

The set of network slices for the UE may be changed at any time while the UE is registered in the network and may be initiated by the network or UE, which is done under certain conditions as described below.

A network based on local policies, subscription changes, and / or UE mobility may change the set of allowed network slice (s) to which the UE is registered. The network may trigger such a change during the registration procedure or trigger a notification to the UE about a change in the supported network slice using an RM procedure (which may trigger the registration procedure). The network may provide a new allowed NSSAI and a list of tracking areas to the UE.

It may be necessary to define the details of the RM procedure used to inform the UE of a change in the supported NSSAI.

In order to change the set of S-NSSAIs used, the UE may have to start the registration procedure.

The change in the S-NSSAI set in which the UE is registered (UE or network initiated) may result in an AMF change in accordance with the operator policy.

Support for AMF relocation due to network slice

During the registration process of the PLMN, if the network determines that the network should be serviced by a different AMF based on the network slice aspect, the AMF that received the registration request first must retransmit the registration request to the other AMF. AMF &lt; / RTI &gt; The redirection message sent by the AMF over the RAN may need to include information for selecting a new AMF to serve the UE.

For UEs already registered, the system may have to support redirection initiated from the serving AMF to the target AMF by the UE &apos; s network due to network slice considerations. The operator policy can determine whether redirection between AMFs is allowed.

Establish a connection PDU session for the required network slice instance

Setting up a PDU session for a DN on a network slice may allow data to be sent over a network slice. The data network may be connected to S-NSSAI and DNN.

The network operator may provide a network slice selection policy (NSSP) to the UE. The NSSP may include one or more NSSP rules each associating an application with one S-NSSAI. Basic rules may also be included to match all applications with the S-NSSAI. When a UE application associated with a particular S-NSSAI requests data transmission,

If the UE has one or more PDU sessions established in response to a particular S-NSSAI, the UE may route user data of this application in one of these PDU sessions, as long as the other conditions of the UE do not prohibit the use of these PDU sessions . If the application provides a DNN, the UE may also decide which PDU session to use considering this DNN. If the UE does not have a PDU session established with this particular S-NSSAI, the UE may request a new PDU session corresponding to this S-NSSAI and a DNN that can be provided by the application. In order for the RAN to select the appropriate resources to support network slicing in the RAN, the RAN needs to recognize the network slice used by the UE.

AMF can choose SMF from the network slice instance based on S-NSSAI, DNN and other information. When the UE triggers the establishment of a PDU session, it may include a UE subscription and a local operator policy. The selected SMF can establish a PDU session based on the S-NSSAI and DNN.

4 is a diagram illustrating a reference architecture for network slicing according to one embodiment.

Referring to FIG. 4, a core part 400 of a network slice in a reference architecture according to one embodiment is shown.

In the case of network slicing, the control plane of the core part 400 of the network slice may be composed of two parts (e.g., a common control part and a slice specific part). Network functions in a common control part (NF) are shared by multiple slice instances, while network functions within a slice-specific part can be dedicate to a particular target slice instance.

In FIG. 1 according to an embodiment, a network slicing non-roaming service-based architecture may be illustrated. Due to network slicing, a Network Slice Selection Function (NSSF) 410, corresponding to additional network functionality, is added to the architecture associated with network slicing deployment to support network slice selection . A more detailed description of the functions of the NSSF 410 will be given later.

A control plane network function with darker shadows may be candidates reside in a common control part or slice specific part. Control plane network functions without darker shadows can only be included in a common control part. The darker shadow control plane The ability to include network functionality in a common control part or in a specific part, depending on the target network services supported in the network slice instance, may be subject to the decision of the operator.

Here, the network function may be implemented as a network element on dedicated hardware or as a software instance running on dedicated hardware, or as a virtualised function instantiated on a suitable platform (e.g., a cloud infrastructure) have.

The Access and Mobility Management Function (AMF) 420 may include the following functions. Some or all AMF 420 functionality may be supported in a single instance of AMF 420.

- Termination of RAN CP interface (N2)

- Termination of the NAS (N1), NAS encryption and integrity protection (Termination of NAS (N1), NAS ciphering and integrity protection)

- Registration management

- Connection management

- Reachability management.

- Mobility Management

- Lawful interception (AMF 420 event and interface with LI system) (Lawful intercept for AMF events and interface to LI System)

- Transparent proxy for routing SM messages for SM message routing.

- Access Authentication

- Access Authorization

- Security Anchor Function (SEA). The SEA may interact with the AUSF and the UE and receive the intermediate key set as a result of the UE authentication process. In the case of USIM-based authentication, the AMF 120 may retrieve security data from the AUSF.

- Security Context Management (SCM). The SCM can receive the key from the SEA used to derive the access network unique key.

Here, there is only one instance of the NAS interface per RAN between the UE and the CN regardless of the number of network functions, and at least one of the network functions that implements NAS security and mobility management is terminated.

When the network slicing is deployed, the AMF 420 interacts with the NSSF 410 via the NS interface so that the network slice instance can be selected. A more detailed description of the selection of the network slice instance will be given later.

Here, the network slicing technology refers to a technology that enables network isolation and customization attributes to be applied to a mobile communication core network structure by bundling network resources and network functions into one independent slice according to services can do. The network slicing technology is a new concept of the 5G core network that has not been used in the existing mobile communication network technology. It is a technology that bundles the network resources and the network functions necessary for the service requested by the mobile terminal into one independent slice.

This allows network operators to independently allocate network resources that are specific to each service and user, and by securing the flexibility of the network through resource virtualization based on Software Defined Networking (SDN) / Network Function Virtualization (NFV) And the scalability and reliability of network resource management can be ensured.

This network slicing technique will be described later with reference to FIG.

5 is a diagram illustrating a structure of a network slice according to an embodiment.

Referring to FIG. 5, network slice instances assigned to a UE according to an embodiment are shown.

The network slice may be a complete logical network consisting of a set of network functions and corresponding resources required to provide specific network performance and network characteristics. The network slice may reside on a RAN (Radio Access Network) 520 and a CN (Core Network) 530. A network slice instance may be an instantiation of a network slice, i. E., A deployed set of network functions that delivers an intended network slice service (intended Network Slice Services) according to a network slice template.

The AN may be common to multiple network slices. For example, the AN may be a Non-3GPP access network or a 5G RAN.

The network slice can be configured differently depending on the supported functions and network function optimization. Operators can deliver exactly the same optimization and characteristics, but multiple NSIs can be deployed that are dedicate to different groups depending on the nature of the UE.

In FIG. 5, which is illustratively shown, UE 510 may be assigned a plurality of network slice instances 540, 550. Network slice instances 540 and 550 may be defined on RAN 520 and CN 530. For example, the network slice instance 540 may comprise a RAN part 541 and a CN part 543. The CN part 543 may be classified into a Common Control Network Function (CCNF), a Slice-Specific Control Network Function (SCNF), a User Plane Functions (UPFs), and others.

Each network slice instance may include one or more network function instances for providing network services required for that network slice instance. For example, the network slice instance 540 may be for a multimedia service, and the network slice instance 550 may be for an Internet of Things (IoT) service.

UE 510 may access multiple network slice instances 540 and 550 simultaneously via a single RAN 520. [ In this case, network slice instances 540 and 550 may share some control plane functionality (e.g., AMF 560 and NSSF 570). As such, a control plane function shared by a plurality of network slice instances 540 and 550 assigned to the same UE 510 may be referred to as CCNF.

For example, the UE 510 may use only one AMF 560. In other words, one UE 510 can not use more than one AMF. Conversely, one AMF 560 may be assigned to one or more UEs. FIG. 2 exemplarily shows a case where one AMF is allocated to one UE.

The AMF 560, NSSF 570 included in the CCNF may be NF shared among a plurality of network slice instances 540 and 550. In addition, the AUF and PCF may be NF shared among one or more network slice instances according to an operator's policy.

The NSSF 570, like the AMF 560, is a function included in the CCNF and is used to select a network slice instance corresponding to the UE.

The NSSF 570 is a network function having an overview and an overview of the NSI topology for a given Public Land Mobile Network (PLMN) (e.g., a set of active NSIs (E. G., AMF 560) that recognizes availability and has access to a particular NSI (e. G., AMF 560) AMF) that is accessible to the specific NSI). The NSSF 570 may also receive the target NSI based on at least one of a serving MVNO, a service or an OTT provider (OTT), a location of the UE, or a time window. Level service mapping for a given Single-Network Slice Selection Assistance Information (S-NSSAI). Here, the network slice instance may be selected from a pool of network slice instances for a particular S-NSSAI for load balancing and redundancy.

NSSF 570 may allow the operator to configure slice-level control rules. For example, to provide mission-critical services such as autonomous navigation or remote industrial robot control, a network slice instance with guaranteed low-latency access should be acquired.

NSSF 570 may support statistic collection for slice selection for the management system of the serving PLMN.

Based on the understanding of the NSSF 570 described above, the following parameters may be considered when communicating with the AMF 560.

The input parameters of the NSSF 570 may include an accepted Accepted S-NSSAI (S-NSSAI). In addition, in some cases, at least one of the past associated NSI list of UE 510 and the serving registration area of UE 510 may be further considered as an input parameter of NSSF 570.

The output parameter of NSSF 570 may include information (e.g., an NSI ID) for the newly selected serving network slice instance corresponding to the accepted S-NSSAI. Additionally, in some cases, at least one of the IP address or Fully Qualified Domain Name (FQDN) of the selected new serving AMF and the IP address or FQDN of the Selected Serving NRF (NF Repository Function) for the selected NSI is stored in the NSSF 570). &Lt; / RTI &gt;

For a network share, each PLMN may include a self-provisioned NSI and corresponding NRF for NF discovery and selection within the network slice instance. In addition to the type of network function, a "logical network identifier" is provided as an input parameter to the NRF for NF discovery and selection so that the NRF can support network function discovery and selection operations with or without network slicing . In the case of network slicing, the logical network identifier represents the NSI ID, and in other cases the logical network identifier may represent the serving PLMN.

6 is a diagram illustrating an example of a network slice instance and a service instance in accordance with one embodiment.

6, a network slice instance 610 and a service instance 620 are illustrated in accordance with one embodiment.

One or more network slice instances 610 may be defined in the network system. One or more of the one or more network slice instances 610 may be selected to provide the service required by the UE. The concrete operation concerning the selection of the network slice instance will be described later.

The network slice instance 610 may be a set of network function instances prepared to support the network service required by the UE. One or more network function instances may provide the same network functionality (e.g., Session Management Function (SMF)) within the network slice instance 610. If there are a plurality of network function instances providing the same network function in the same network slice instance 610, any one of a plurality of network function instances may be selected. Concrete operations relating to network function instance selection will be described later.

One network slice instance 610 may be assigned to one or more UEs and may be assigned to one or more services. The network slice instance 610 may correspond to an operator's service resource group.

The service instance 620 may be a collection of serving network function instances supporting the service required by the UE. The service instance 620 may include all the network functions required for the corresponding service. The service instance 620 may refer to a network slice instance assigned to the actual UE.

7 is a diagram illustrating an example of configuring a service instance according to one embodiment.

Referring to FIG. 7, an example is illustrated to illustrate the process of configuring a service instance 730 through NSI selection 710 and NFI selection 720 according to one embodiment.

In the NSI selection 710, any one of a plurality of network slice instances defined in the network system may be selected. At this time, the network slice instance can be selected based on the NSSAI. Additionally, at least one of the previously assigned network slice instance of the UE and the serving registration area of the UE may be further considered and the network slice instance may be selected. As a result of selection, an available NSI ID can be output. Additionally, at least one of the new AMF and the IP address of the serving NRF for the selected NSI may be further output. A more detailed description thereof will be described later.

At the NFI selection 720, any one of a plurality of network function instances in the selected network slice instance may be selected. At this time, the network function instance can be selected based on the logical network identifier and the type of network function. The logical network identifier may represent an NSI ID if network slicing is used and a serving PLMN if network slicing is not used. The type of the network function may be, for example, AMF, NSSF, SMF, UPF, AUF, PCF and the like. One network function instance may be selected for each type of network function required to provide the network service requested by the UE.

In FIG. 7, which is illustratively shown, there may be a plurality of SMFs in the selected network slice instance. A situation may arise where one network function instance can not be selected even though the logical network identifier (i.e., the selected NSI ID) and the type of network function (i.e., SMF) are taken into account. In this case, an operator policy may be additionally considered. An operator policy is a policy set by a network operator and may include, for example, load balancing, resource optimization, energy efficiency, traffic optimization, and the like.

For example, an SMF having a small number of currently used UEs among two SMFs may be selected. Alternatively, one of the two SMFs may be selected with a better quality of service (QoS). Alternatively, the SMF corresponding to the charging plan of the corresponding UE among the two SMFs (for example, the basic charging rate and the premium charging rate) may be selected. Alternatively, the SMF corresponding to the serving registration area of the corresponding UE among the two SMFs may be selected. In some cases, one or more of the various criteria described above may be considered to select a network function instance.

Service instance 730 may refer to a selected network slice instance that includes a selected network function instance. The service instance 730 may refer to a network slice instance that is capable of fully providing the network service requested by the UE.

Hereinafter, the NSI selection 710 and the NFI selection 720 will be described in more detail. The NSI selection 710 may be performed in the UE registration procedure and the PDU session establishment procedure, and the NFI selection 720 may be performed in the PDU session establishment procedure.

If the network supports network slicing, one or more network slice instances may be selected using Network Slice Selection Assistance Information (NSSAI) provided from the UE. NSSAI is a set of S-NSSAIs. Each S-NSSAI may be used to select a particular network slice instance. In addition, UE capabilities and UE subscription data may be used to select a network slice instance.

The S-NSSAI may include Slice / Service type (SST) and Slice Differentiator (SD). Slice / service type indicates expected network behavior in terms of characteristics and services. The SD is optional information that complements the slice / service type and can differentiate a plurality of network slice instances satisfying the SST.

The UE subscription data may include information about the network slice instances to which the UE is allowed to access. The information in the UE subscription data may include an S-NSSAI allowed for use by the UE.

In addition, the UE subscription data may include information about whether the corresponding S-NSSAI is the default S-NSSAI. The default S-NSSAI may indicate a network slice instance that the UE should use when connecting to the network system. In other words, if the UE initially registers with the network system without providing any NSSAI in the registration request, the CN may use the default initial NSI to service the UE, It should use the default NSSAI configured with S-NSSAIs stored in the UE subscription data with a flag indicating that it should be considered. In addition, the UE subscription data may include a default DNN (Data Network Name) value for the S-NSSAI.

The CN part of the network slice instance serving the UE may be selected by the CN rather than the RAN *? *. The UE can simultaneously access multiple network slice instances via a single RAN. In this case, the network slice instances that are simultaneously accessed by the UE may share some control plane functionality including the AMF in the core network.

The AMF selection for the set of network slice instances for the UE may be triggered by the first contacted AMF in the Registration Procedure and may lead to a change in AMF. Once a target network slice instance is selected and a Session Management (SM) message for establishing a PDU session is received from the UE, subsequent SMF network capability discovery and selection may be initiated by the AMF . NRF can be used to perform this selection task.

A PDU session may belong to a particular network slice instance. Other NSIs do not share PDU sessions, but other network slice instances may contain slice-specific PDU sessions for the same DNN.

The S-NSSAI may include standard values or a PLMN-specific value. The S-NSSAIs with PLMN-specific values may be associated with the PLMN IDs of PLMNs that allocate S-NSSAIs at the UE. One S-NSSAI shall not be used by the UE in the access stratum procedures in PLMN other than the PLMN associated with the S-NSSAI (AS-NSSAI shall not be used by the UE in the access stratum procedures in any PLMN other than the one to which the S-NSSAI is associated).

The NSSAI is used to select a set of AMF and network slice instances (a set of NSIs), while the S-NSSAI can be used to select a network slice instance. Each S-NSSAI included in the NSSAI may include (a) slice / service type or (b) slice / service type and SD.

The UE may store Configured and / or Accepted NSSAI (NSSAI) configured and / or approved for each PLMN. The configured NSSAI may be an NSSAI configured by an HPLMN (Home PLMN) in the UE to be used in the PLMN if no PLMN-specific approved NSSAI is stored in the UE.

The approved NSSAI is the NSSAI provided to the UE from the PLMN and the UE shall use the approved NSSAI after the PLMN has successfully registered the UE. A Registration Accept message may include an approved NSSAI. The approved NSSAI may be updated in a subsequent Registration Procedure.

If a configured or accepted NSSAI for the PLMN to which the UE is accessing is provided to the UE then the UE shall establish such an NSSAI in the RRC Connection Establishment (RRC) and Non-access stratum (NAS) . The RAN can route the initial access to the AMF using the provided NSSAI.

If the UE does not receive any approved NSSAI for the PLMN that it is accessing and is provided with a configured NSSAI, the UE may establish an RRC connection and provide the NSSAI configured in the NAS to the RAN. The RAN may use the NSSAI to route the initial access to the AMF. Alternatively, if no approved NSSAI or configured NSSAI is provided for the PLMN that the UE is accessing, the UE does not provide the NSSAI in RRC connection establishment and NAS, and the RAN can send NAS signaling to the default AMF.

A network operator may provide a Network Slice Selection Policy (NSSP) to the UE. An NSSP may include one or more NSSP rules that associate an application with a particular S-NSSAI. The NSSP may also include a default rule that matches all applications and includes a default S-NSSAI. The UE may use the NSSP to associate the UE application with the S-NSSAI.

When a UE application associated with a particular S-NSSAI requires data transmission, and the UE has more than one PDU session established with this particular S-NSSAI, the UE Lt; / RTI &gt; may route the user data of the application in any one of these PDU sessions. If the application provides a DNN, the UE can determine which PDU session to use considering this DNN.

When a UE application associated with a particular S-NSSAI requests a data transfer, if the UE does not have a PDU session established with this particular S-NSSAI, the UE sends a new PDU session. (The UE requests a new PDU session with this S-NSSAI and with the DNN that may be provided by the application).

FIG. 8 is a diagram illustrating an example of selecting NSI in the UE registration procedure according to an embodiment.

Referring to Fig. 8, a communication method performed by a user terminal and a communication device is shown. The UE shown in FIG. 8 denotes a user terminal, and AMF, NSSF, UDM, and new AMF may denote network function instances included in a communication device.

At step 801, the UE sends a registration request to the AMF. The UE may send a registration request to the AMF along with either the default NSSAI, the configured NSSAI, and the approved NSSAI via the RAN. Here, AMF may be initial AMF.

In step 803, a general registration procedure may be performed.

In step 805, the AMF may send an Authorization / Subscription Check Request with the NSSAI to the UDM.

In step 807, the UDM may check whether the NSI requested by the NSSAI is usable by the UE.

In step 809, the UDM may send an authentication / subscription check response with the approved NSSAI to the AMF. That is, the AMF can obtain an authenticated NSSAI from the UDM and thereby determine a potentially accepted S-NSSAI (potential accepted S-NSSAI).

In step 811, the AMF may send an NSI Selection Request to the NSSF along with the approved NSSAI.

In step 813, the NSSF may determine the availability of the NSI requested by the authorized NSSAI. If a more appropriate AMF that can provide the NSI selected in the NSSF is detected than the current AMF (i.e., the AMF that sent the NSI selection request to the NSSF), then the NSSF provides information about the new AMF to the current AMF can do.

At step 815, the NSSF may pass information about the selected NSI to the AMF in an NSI selection response. The NSSF may also pass information about the new AMF to the AMF in an NSI selective response.

If the current AMF has decided to relocate the serving AMF for the UE, then in step 817, the AMF may trigger the AMF relocation procedure using information about the new AMF provided from the NSSF.

At step 819, a generic registration procedure may be performed.

In step 821, the AMF may send a Registration Accept message to the UE along with the approved NSSAI.

That is, in the UE registration procedure, the AMF may obtain an approved NSSAI from the UDM and determine a set of potentially accepted S-NSSAs (S-NSSAIs). And, by verifying the set of potentially approved S-NSSAIs through the NSSF, the availability of the NSI along with the serving registration area of the UE can be determined.

The approved NSSAI may be configured to perform the following functions: (a) an authentication / subscription check performed in consultation with a UDM providing a list of authenticated NSSAIs, (2) a request for registration of the UE based on the availability checking of the NSI performed by negotiating with the NSSF provided by OA & As shown in FIG. In addition, the approved NSSAI may change depending on the result of the NSI availability check in the NSSF as well as the Subscription Check.

Upon initial slice selection or successful Attachment Registration, the UE may be provisioned with a temporary ID in RRC connection establishment of the subsequent initial access so that the RAN can route the NAS message to the appropriate AMF as long as the Temp ID is valid . In addition, the serving PLMN may return an approved NSSAI including the PLMN ID of the serving PLMN. The approved NSSAI may include the S-NSSAI of the network slice instance approved by the PLMN for use by the UE. Here, it is assumed that the RAN and core slicing-related configuration are not changed within the registration area of the UE.

In order to route the NAS signaling with correct CN functions, the UE may include a complete Temp ID (complete Temp ID) in the NSSAI and RRC stored for the PLMN. If the RAN can recognize and reach the AMF associated with the Temp ID, the RAN can forward the request to this AMF. Otherwise, the RAN may select an appropriate AMF (suitable AMF) based on the NSSAI provided by the UE and send the request to the selected AMF. If the RAN can not select an AMF based on the approved NSSAI, the request is sent in the default AMF.

The UE must include the DNN of the data network for the PDU session and the S-NSSAI enabling the selection of the SMF in the PDU session establishment request NAS message.

The RAN needs to recognize the network slice used by the UE so that the RAN can select the proper resources to support network slicing in the RAN.

The UE may change the set of network slice instances in use by the network by submitting a new value of the NSSAI to the Registration Request procedure. The final decision of the set of network slices assigned to the UE may be performed by the network.

The network may be used by the UE by providing the UE with a notification of Accepted NSSAI change of the approved NSSAI change based on local policies, subscription changes and / or UE mobility. You can change the set of NSIs to be. This may trigger a UE initiation registration procedure including an RRC and NAS signaling a new approved NSSAI (New Accepted NSSAI) provided by the network (This is a UE initiated Registration procedure including in RRC and NAS Signaling the value of the new Accepted NSSAI the network has provided).

Alteration of a set of network slice instances initiated by the UE or network may result in an AMF change in accordance with an operator policy. The change in the set of network slice instances that the UE can access is such that if these network slice instances are no longer used (at this time, the other slices may still be available), a PDU in progress with the original set of network slices Termination of the ongoing PDU session may result.

If it is determined by the network that the UE should be serviced by another AMF during the initial registration procedure, the AMF that has received the initial registration request previously receives the initial registration request via the RAN or through the direct signaling between the initial AMF and the target AMF, To be redirected. A redirection message sent by the AMF over the RAN may contain information about the target AMF for servicing the UE.

For UEs already registered, the network system must support retransmission of the UE from the serving AMF to the target AMF. The operator policy can determine whether retransmission between AMFs is allowed.

If the network has decided to retransmit the UE due to a change in NSSAI, then the network will either (a) update / new NSSAI with the UE using a Registration Update Required Procedure and (b) May send an indication to the UE to initiate the registration update procedure with the updated / new NSSAI.

The AMF may select the SMF in the network slice instance based on the S-NSSAI, DNN and other information (e.g., UE subscription and local operator policy). The selected SMF can establish a PDU session based on the S-NSSAI and DNN.

9 is a diagram illustrating an example of selecting an NSI and an NFI in a PDU session establishment procedure according to an embodiment.

Referring to FIG. 9, a communication method performed by a user terminal and a communication device is shown. The UE shown in FIG. 9 denotes a user terminal, and AMF, NSSF, NRF, and SMF may refer to network function instances included in a communication device.

In step 901, the UE may send a PDU Session Establishment Request with the S-NSSAI approved as AMF over the RAN.

At step 902, the AMF may send an NSI selection request to the NSSF along with the approved S-NSSAI and the active NSI accessed by the UE.

In step 905, the NSSF may select the corresponding NSI according to the serving registration area of the UE.

In step 907, the NSSF may respond to the AMF with a serving NRF corresponding to the selected serving NSI and the selected NSI.

In step 909, the AMF may select the SMF by interacting with the serving NRF corresponding to the selected NSI.

In step 911, UE Request PDU session establishment can be performed.

That is, upon establishing a PDU session, the AMF may verify through the NSSF a set of potentially approved S-NSSAIs to determine the availability of the NSI along with the UE's serving registration area. The AMF may also provide the NSSF with active NSI information accessed by the UE. The NSSF may provide the serving NRF information corresponding to the selected serving NSI and the selected NSI to the AMF in response.

10 is a diagram illustrating an example of a repository in accordance with one embodiment.

Referring to FIG. 10, an NFI repository 1010 and a serving NF repository 1020 are shown.

The NRF may manage the NFI repository 1010 and the serving NF repository 1020. The NFI repository 1010 may include information about network function instances in the network system. For example, the NFI repository 1010 may include an NFI ID, an NF type, an NSI ID, and a FQDN / IP. The NFI ID is an identifier for the network function instance, and the NSI ID can be an identifier for the network slice instance including the network function instance.

The NFI repository 1010 may be updated by Operations, Administration and Management (OAM). Specifically, an NSI orchestration included in the OAM can instantiate a network slice, update and terminate a network slice instance. In addition, the NFI orchestrations included in the OAM can instantiate network functions, update and terminate network function instances, and scale and migrate.

The NFI selection may be performed using the information contained in the NFI repository 1010. When an NFI selection occurs, the NRF may store information about the selected NFI in the serving NF repository 1020. In other words, the serving NF repository 1020 may include information about the serving NFI selected for the UE. The NFI included in the serving NF repository 1020 may constitute a service instance.

The NRF can support the service discovery function. When an NF discovery request is received from the network function instance, the NRF may provide information about the discovered network function instance to the NF discovery requested network function instance.

In addition to the network function type, a logical network identifier may be provided to the NRF so that the NRF can support network function selection and discovery operations with or without network slicing. In the case of network slicing, the logical network identifier represents the NSI ID, and in other cases the logical network identifier represents the serving PLMN.

11, there is shown an NRF 1110 that performs network function instance selection / discovery functions in accordance with one embodiment.

The NRF 1110 may manage selection results for network function instances and, if requested from the network function instances, perform discovery for selected network function instances.

Within the network slice instance, multiple instances of network functionality may be provided for redundancy, scalability, and the like. That is, different instances of the same network function may have different QoS attributes such as capability, performance, and so on. Depending on the QoS attribute of the network function instance, it may be possible to select an appropriate network function instance within the network slice instance, or to reselect the network function instance so that the specific QoS attribute is satisfied.

The selection of these network function instances can be based on the following principles.

A network slice instance can consist of multiple network function instances for a particular service with network capability. The requested network slice instance per UE service may be selected using 'network slice selection support information' (NSSAI). More than one network function instance may be provided for each of the various network function types for performance, redundancy, scalability, etc. within the network slice instance. A set of network function instances may be selected for each UE service request for binding. The selection of a network function instance may be performed according to the policy of the network operator (e.g., energy efficiency, load balancing, resource optimization, etc.). The binding information of the selected NFI may be further provided to the NRF 1110. At the time of roaming, the set of network function instances can be updated by reselecting the network function instance or by changing the QoS attribute of the network function instance, the network operator's policy, roaming, and the like.

The NSSF may select an appropriate network slice instance based on the NSSAI. Specifically, the NSSF may determine a target network slice instance classified into the service type requested by the UE, and may select a network slice instance based on the various UEs and the network-provided NSSAI. For example, the NSSAI may include UE subscription data, policies of network operators, and the like.

The NRF may select an appropriate network function instance using the network operator's resource operational policies (e.g., load balancing, resource optimization, etc.). Specifically, the NRF identifies the NF (or NF type) of a given network slice, determines any one of multiple instances of each NF (or NF type) within a given NSI, and binds the binding information of the selected NFIs to the NRF 1110 ) &Lt; / RTI &gt; in the serving NF repository.

NRF

According to one embodiment, the NF storage function (NRF) may support the following functions.

- It can support service search function. An NF discovery request may be received from the NF instance and information of the discovery NF instance may be provided to the NF instance.

Network feature discovery and selection

NF Discovery can allow one NF to discovery a particular target NF type.

Unless the expected NF information is locally configured in the requestor NF, for example. The expected NF may be in the same PLMN where NF discovery is implemented via the NRF. The NF repository function (NRF) can be a logical function used to support the functionality of NF discovery.

The requestor NF may initiate NF discovery by providing the type of NF (e.g., SMF, PCF) and other service parameters in order to avoid accessing the associated NF stored in the requested type NF and the requestor NF. The target NF can be disassembled by slicing the related information.

The NRF may provide the IP address or FQDN of the NF instance to the requestor NF for selection of the target NF instance. Based on this information, the requestor NF may be able to select one NF instance.

The requestor NF may provide the NRF with the PLMN ID of the NF for the NF discovery via the PLMN. The local PLMN may interact with the NRF of the target PLMN to retrieve the IP address or FQDN of the target NF instance.

NRF Service

"NF Discovery" service

Service Description: The requestor NF can provide the IP address or FQDN of the expected NF instance.

Input: The NF type of the target NF, the NF type of the requestor NF, the PLMN ID of the PLMN target to which the NF belongs, and the service-related information.

Output: A set of target NF instances.

According to one embodiment, the service procedure may be as shown in FIG.

At step 1210, Requester-A may discovery the expected NF instance. For example, the AMF may request to retrieve an SMF instance from the same PLMN. Requester-A sends an NF Discovery Request to the NRF of the same PLMN. Expected NF The NF type of the instance, the NF type of the requestor, information about the network slice (optional), and other service-related parameters.

In step 1220, the NRF may grant an NF Discovery Request. Depending on the expected NF profile and the type of requestor NF, the NRF may determine whether the requestor NF is able to discovery the expected NF instance. Once the expected NF instance (s) are placed on one network slice, the NRF can accept the discovery request according to the discovery configuration of the network slice. The expected NF instance can only be retrieved by the NF of the same network slice.

At step 1230, if allowed, the NRF may determine the discovery NF instance and provide the applicant with information about the set of discovery NF instances via the NF Discovery Response message. The information of the discovery NF instance may include the following: The FQDN or IP address of the expected NF instance.

If the requester needs to discovery the NF in another PLMN, the NRF providing the PLMN may have to request the "NF Discovery" service from the NRF of the remote PLMN. The procedure, according to one embodiment, can be shown in FIG.

At step 1310, the Requester-B NF may need to discovery the NF instance in the remote PLMN. For example, the AMF may request to retrieve the SMF instance from the remote PLMN. The requestor may send an NF Discovery Request to the NRF and the expected NF of the NF type, remote PLMN ID may be included in the NF Discovery Request.

At step 1320, the NRF providing the PLMN service identifies the NRF at the remote PLMN based on the remote PLMN ID and requests the "NF Discovery" service at the NRF of the remote PLMN according to the procedure of FIG. 14 to obtain the expected NF instance ) To the remote PLMN. Since the NRF in the serving PLMN triggers "NF Discovery" on behalf of the Requester-B NF, the NRF of the serving PLMN does not replace the information of the service requestor NF, ie Requester-B NF, in the Discovery Request message. have.

In step 1330, the NRF serving the PLMN may provide information of the disjoint NF instance set in the NF Discovery Response message.

14 illustrates a network service registration procedure according to one embodiment.

In step 1410, the NF service consumer (e.g., AMF instance) sends an Nnrf_NFManagement_NFRegister request message to the NRF to inform the NRF of the NF profile when the NF service consumer first runs. The NF profile of the NF service consumer may include the IP address of the NF type, the FQDN or the NF, the name of the supported service, the endpoint information of each supported service instance (s), and other service parameters.

In the case of a UDR, the Nnrf_NFManagement_NFRegister request message may include the data set identifier (s) served by the UDR instance and / or the range (s) of the SUPIs. At this time, the NF profile of the NF service consumer interacting with the NRF can be configured by the OAM system.

At step 1420, the NRF stores the NF profile of the NF service consumer and can mark that the NF service consumer is available. Whether the NF profile sent by the NF service consumer to the NRF is integrity protected by the NF service consumer and verified by the NRF can be determined by SA3.

In step 1430, the NRF may send an Nnrf_NFManagement_NF Register response message indicating that the NF registration has been approved.

15 shows a network functional service update procedure according to one embodiment.

In step 1510, the NF service consumer (e.g., an AMF instance) is added to the NRF to inform the NRF of the updated NF profile (e.g., updated capacity), for example, as triggered after a scaling operation. Transmits an Nnrf_NFManagement_NF Update Request message to the NRF. At this time, the updated NF profile of the NF instance is configured by the OAM system.

At step 1520, the NRF may update the NF profile of the NF service consumer.

In step 1530, the NRF may send an Nnrf_NFManagement_NF Update response message indicating that the NF update has been approved.

16 illustrates a NF service deregistration procedure, according to one embodiment.

In step 1610, the NF service consumer (e.g., AMF instance) may send an Nnrf_NFManagement_NFDeregister request message to the NRF to inform the NRF that it is not available when shutting down the network or disconnecting the connection.

At step 1620, the NRF may mark an NF service consumer that is not available. According to the NF management policy, the NRF can remove the NF profile of the NF service consumer.

At step 1630, the NRF may send an Nnrf_NFManagement_NF Deregister response message indicating that the NF deregistration is authorized.

Figure 17 illustrates network capability / network capability service discovery in the same PLMN, according to one embodiment.

At step 1710, the NF service consumer may retrieve available services in the network based on the service name and the target NF type. The NF service consumer can call Nnrf_NFDiscovery_Request (NF service name, NF type of expected NF instance, NF type of NF consumer) from the appropriate NRF of the same PLMN. The parameters may optionally include SUPI, data set identifier (s), S-NSSAI, NSI ID, and other service-related parameters, if available.

Here, the use of the NSI ID in the PLMN depends on the network deployment. The need for other service related parameters depends on the NF type of the expected NF instance (s). Whether one or more NF service instances are registered with the NRF depends on the NF implementation.

In step 1720, the NRF may authorize the Nnrf_NFDiscovery_Request. Based on the profile of the expected NF / NF service and the type of NF service consumer, the NRF may determine whether the NF service consumer is allowed to search for the expected NF instance (s). If the expected NF instance (s) or NF service instance (s) are placed on a particular network slice, the NRF can accept the search request according to the search configuration of the network slice. The expected NF instance (s) can be retrieved by the NF of the same network slice.

In step 1730, the NRF may determine the NF instance (s) or NF service instance (s) retrieved and determine the set of NF instance (s) or NF service instance (s) retrieved to the NF service consumer via the Nnrf_NFDiscovery_Request response message Can be provided.

If the target NF is a UDR, then if the SUPI is used, the NRF can provide the UDR instance (s) matching the SUPI. Otherwise, the NRF may return all applicable UDR instance (s) if SUPI is not provided.

18 illustrates network capability / network capability service discovery through PLMNs, in accordance with one embodiment.

If the NF service consumer wants to retrieve the NF / NF service from the home PLMN, the NRF serving the PLMN may request the "NF Discovery" service from the NRF of the home PLMN.

At step 1810, the NF service consumer may invoke Nnrf_NFDiscovery_Request (expected service name, NF type of expected NF, home PLMN ID, serving PLMN ID, NF type of NF service consumer). The Nnrf_NFDiscovery_Request may optionally include an S-NSSAI, an NSI ID if available, and other service-related parameters.

At this time, the use of the NSI ID in the PLMN depends on the network deployment.

In step 1820, the NRF in the serving PLMN identifies the NRF in the home PLMN (hNRF) based on the home PLMN ID, requests the "NF Discovery" service in the NRF of the home PLMN according to the procedure of FIG. 17, To obtain the deployed anticipated NF instance (s) or NF service instance (s). Since the NRF of the serving PLMN triggers "NF Discovery" on behalf of the NF service consumer, the NRF of the serving PLMN does not replace the information of the service requestor NF, namely the NF consumer ID, in the Discovery Request message.

The hNRF may further query the appropriate local NRF in the home PLMN based on the input information received from the NRF of the serving PLMN. The FQDN or IP address of the local NRF in the home PLMN may be configured in the hNRF or needs to be retrieved based on the input information.

Here, the hNRF may retrieve the appropriate local NRF in the home PLMN through support from the NSSF in the home PLMN. Due to the network topology hiding or network configuration, the home NRF may provide the serving NRF with information about the IP address or FQDN of the proxy function of the retrieved NF / NF service.

At step 1830, the NRF serving the PLMN receives information such as, for example, the FQDN, IP address or endpoint address (i.e., URL) of the set of NF or NF service instance (s) retrieved in the NF Discovery Response message .

<NRF Services>

Table 1 below shows NRF services and service operations.

Service Name Service Operations Operation
Semantics Example Consumer (s) Nnrf_NFManagement
NFRegister Request / Response AMF, SMF, UDM, AUSF, NEF, PCF, SMSF, NSSF NFUpdate Request / Response AMF, SMF, UDM, AUSF, NEF, PCF, SMSF, NSSF NFDeregister Request / Response AMF, SMF, UDM, AUSF, NEF, PCF, SMSF, NSSF NFStatusSubscribe Subscribe / Notify AMF, SMF, PCF, NEF, NSSF, SMSF, AUSF NFStatusNotify AMF, SMF, PCF, NEF, NSSF, SMSF, AUSF NFStatusUnSubscribe AMF, SMF, PCF, NEF, NSSF, SMSF, AUSF Nnrf_NFDiscovery Request Request / Response AMF, SMF, PCF, NEF, NSSF, SMSF, AUSF

As an example, the Nnrf_NFManagement_NFRegister service operation is as follows.

I) Service action name: Nnrf_NFManagement_NFRegister.

Ii) Description: Registers the consumer NF with the NRF by providing the NRF with the NF profile of the consumer NF and marks that the consumer can use the NRF.

Iii) Mandatory input: NF profile of the NF consumer (NF type, NF ID, NF services)

Iv) Selection input: NF If the consumer stores the data set (s) (eg UDR): range (s) of SUPIs, data set identifier (s)

V) Required output: display result

Vi) Optional output: none

As an example, the Nnrf_NFManagement_NFUpdate service operation is as follows.

I) Service action name: Nnrf_NFManagement_NF Update.

Ii) Description: Provide the NRF with an updated NF profile of the NF consumer

Iii) Required input:

Iv) Optional inputs: NF profile of NF consumers

V) Required output: display result

Vi) Optional output: none

As an example, the Nnrf_NFManagement_NFDeregister service operation is as follows.

I) Service action name: Nnrf_NFManagement_NFDeregister

Ii) Description: Informs the NRF that the NF consumer is unavailable.

Iii) Required input: NF Instance ID, Reason Indication.

Iv) Mandatory output: display result

Ⅴ) Selective output: none

<Management Support of NRF>

The operator wants to keep the NF profile (e.g., NF type, NF ID, NF service) of the 5GC NF instances of the NRF instance used for NF instance and service discovery up to date.

The NF profiles that need to be managed by the NRF are:

I) NF Instance ID ii) NF Type iii) PLMN ID iv) Network Slice Relevant Identifier (s) eg S-NSSAI, NSI ID v) Fully Qualified Domain Name (FQDN) Information ⅶ) NF specific service entitlement information ⅷ) Name of supported services ⅸ) Endpoint information of the instance (s) of each supported service ⅹ) ID of stored data / information

The NF profile can be registered / updated / deregistered to the NRF by two different types of 3GPP entities:

Ⅰ) NF instance itself ⅱ) NF instance lifecycle management entity of 3GPP management system

The details of registering / updating / unregistering NF profiles by the 3GPP management system are as follows:

I) NF profile registration: When a new 5GC NF instance is deployed, the 3GPP management system requests the NRF instance to add the NF profile of the new 5GC NF instance.

Ii) NF profile update: If the NF profile of the 5GC NF instance is changed, the 3GPP management system can request the NRF instance to update the NF profile of the 5GC NF instance.

Iii) De-registering the NF profile: When the 5GC NF instance is removed, the 3GPP management system may request the NRF instance to delete the NF profile of the 5GC NF instance.

19 illustrates an NF profile management interface, according to one embodiment.

The management system can manage the NF profile using the interface between NRF-NFMF (network function management function (s)). The management system may include at least one of NFMF, NSMFS (network slicing management function (s) set).

<NRF>

NRF can support the following functions:

I) Support service search function. Receive an NF discovery request from the NF instance, and provide information of the retrieved NF instance to the NF instance. Ii) Maintain the NF profile of the available NF instances and the supported services.

The NF profile of the NF instance maintained in the NRF may include the following information:

I) NF Instance ID ii) NF Type iii) PLMN ID iv) Network Slice Relevant Information (eg S-NSSAI, NSI ID) v) FQDN or NF's IP Address vi) NF Performance Information Information on the endpoint of the instance (s) of each supported service. X) ID of the stored data / information. Xi) Other service parameters (eg, Endpoint notification for each type, DNN)

With respect to network slicing based on network implementation, a plurality of NRFs can be placed at several levels:

Ii) a shared slice level (NRF is made up of information pertaining to a set of network slices); iii) a slice specific level (NRF is the information pertaining to the S-NSSAI); i) a PLMN level Lt; / RTI &

With respect to roaming, a plurality of NRFs may be placed in different networks.

I) The NRF (s) in the visited PLMN consists of the information for the visited PLMN. Ii) The NRF (s) in the home PLMN consists of information for the home PLMN and is referenced by vNRF via the N27 interface.

<Network Function and Network Function Service registration and deregistration>

To ensure that the NRF maintains information about the available NF instances and supported services, each NF instance notifies the NRF of the list of NF services it supports.

The NF instance may make the information available to the NRF when the NF instance first operates (registering operation) or when an individual NF service instance is activated / deactivated in the NF instance (update operation). During registration of the list of NF services that are supported for each NF service, the NF instance may provide notification endpoint information for each notification service type that the NF service is ready to consume to the NRF during NF instance registration. The NF instance may also update or delete NF service related parameters (e.g., to delete notification endpoint information). Alternatively, other authenticated entities (such as OA & M functions) can inform NRF on behalf of NF instance instances triggered by NF service instance lifecycle events (instance registration, deactivation, activation, or deactivation) have). The NRF registration includes performance and configuration information during instance creation.

NF instances can be unregistered from the NRF when they shut down or disconnect the network in a controlled manner.

If an NF instance is unavailable or unreachable due to an unplanned error (such as an NF crash or a network problem), the authenticated entity can unregister the NF instance with the NRF.

<Management support for NRF>

1. Goal

The operator can keep the retrieval information (e.g., NF ID, IP address) of the 5GC NF instance of the NRF instance used for NF instance and service discovery up to date.

2. Pre-conditions

An NRF instance is placed that stores search information for the available 5GC NFs.

3. Steps

I) Once a new 5GC NF instance is deployed, the 3GPP management system or a new 5GC NF instance can be made aware of the NRF instance of the retrieval information (e.g., NF ID, IP address) of the new 5GC NF instance.

Ii) If the search information of the 5GC NF instance is changed, the 3GPP management system or the 5GC NF instance may be allowed to update the 5GC NF search information maintained by the NRF instance.

Iii) Once the 5GC NF instance is removed, the 3GPP management system can make the NRF aware that the 5GC NF is removed.

<5GC management requirements>

REQ-5GCN-CON-1: The 3GPP management system can support configuration management (eg CRUD MOI) in 5GC NF / NE.

REQ-5GCN-CON-2: The 3GPP management system can collect performance data from the 5GC NF / NE.

REQ-5GCN-CON-3: 3GPP management system can support error management in 5GC NF / NE.

REQ-5GCN-CON-4: The 3GPP management system can reflect service-oriented architecture characteristics in NRF of 5GC NF / NE.

REQ-5GCN-CON-5: The 3GPP management system can establish the relationship between DSF and related 5GC NFs.

REQ-5GCN-CON-6: The 3GPP management system can support coordination between lifecycle management operations of related 5GC NFs and lifecycle management operations of DSF.

REQ-5GCN-CON-7: The 3GPP management system or the 5GC NF instance can register / unregister the retrieval information of the 5GC NF instance to the NRF instance.

REQ-5GCN-CON-8: The 3GPP management system can support configuration management of the AMF set.

REQ-5GCN-CON-9: The 3GPP management system can support AMF set related performance management such as AMF set performance report or alarm.

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 array (FPA) A programmable logic unit (PLU), a microprocessor, or any other device capable of executing and responding to instructions. The processing device may execute one or more software applications that are executed on an operating system (OS) and an 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. Program instructions to be recorded on the medium may be those specially designed and constructed 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.

Although the embodiments have been described with reference to the drawings, various technical modifications and variations may be applied to those skilled in the art. 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.

Claims (20)

A network function profile management method comprising:
When a new network function instance (new NF instance) is deployed, a network function repository function (NRF) receives a registration request from the management system;
Adding the Network Function Profile (NF profile) of the new network function instance to the NRF receiving the registration request; And
Wherein the NRF sends a registration response to the management system
The network capability profile management method comprising:
The method according to claim 1,
The NRF includes the network function instance information,
Wherein the network function profile of the network function instance is kept up to date.
The method according to claim 1,
The network function profile comprises:
An NF instance ID, a NF type, a Fully Qualified Domain Name (FQDN) or an IP address of a network function, a PLMN ID, an identifier related to a network slice (Network Slice related Identifier (s)), NF capacity information, network specific service authorization information, identification of stored information, Names of supported services, and respective support (S) of each supported service. &Lt; Desc / Clms Page number 21 &gt;
The method of claim 3,
Wherein the identifier associated with the network slice includes an NSSAI (Network Slice Selection Assistance Information), an S-NSSAI (Single-Network Slice Selection Assistance Information), and an NSI ID.
A network function profile management method comprising:
Receiving an update request from a management function, when a network function profile (NF profile) of a network function instance (NF instance) is changed;
Updating the network capability profile (NF profile) of the network function instance, the NRF having received the update request; And
Wherein the NRF sends an update response to the management system
The network capability profile management method comprising:
6. The method of claim 5,
The NRF includes the network function instance information,
Wherein the network function profile of the network function instance is kept up to date.
6. The method of claim 5,
The network function profile comprises:
An NF instance ID, a NF type, a Fully Qualified Domain Name (FQDN) or an IP address of a network function, a PLMN ID, an identifier related to a network slice (Network Slice related Identifier (s)), NF capacity information, network specific service authorization information, identification of stored information, Names of supported services, and respective support (S) of each supported service. &Lt; Desc / Clms Page number 21 &gt;
8. The method of claim 7,
Wherein the identifier associated with the network slice includes an NSSAI (Network Slice Selection Assistance Information), an S-NSSAI (Single-Network Slice Selection Assistance Information), and an NSI ID.
A network function profile management method comprising:
When a network function instance (NF instance) is removed, a network function repository function (NRF) from the management system receives a deregistration request;
The NRF having received the deregistration request deletes a network capability profile (NF profile) of the network function instance; And
Wherein the NRF sends a deregistration response to the management system
The network capability profile management method comprising:
10. The method of claim 9,
The NRF includes the network function instance information,
Wherein the network function profile of the network function instance is kept up to date.
10. The method of claim 9,
The network function profile comprises:
An NF instance ID, a NF type, a Fully Qualified Domain Name (FQDN) or an IP address of a network function, a PLMN ID, an identifier related to a network slice (Network Slice related Identifier (s)), NF capacity information, network specific service authorization information, identification of stored information, Names of supported services, and respective support (S) of each supported service. &Lt; Desc / Clms Page number 21 &gt;
12. The method of claim 11,
Wherein the identifier associated with the network slice includes an NSSAI (Network Slice Selection Assistance Information), an S-NSSAI (Single-Network Slice Selection Assistance Information), and an NSI ID.
A communication device for managing a network function profile,
A processor and a memory containing instructions readable by the computer
Lt; / RTI &gt;
If the instruction is executed in the processor,
When a new NF instance is deployed, a network function repository function (NRF) receives a registration request from the management system,
The NRF receiving the registration request adds a network function profile (NF profile) of the new network function instance,
Wherein the NRF sends a registration response to the management system,
A communication device that manages a network capability profile.
14. The method of claim 13,
The NRF includes the network function instance information,
Wherein the network function profile of the network function instance is kept up to date.
14. The method of claim 13,
The network function profile comprises:
An NF instance ID, a NF type, a Fully Qualified Domain Name (FQDN) or an IP address of a network function, a PLMN ID, an identifier related to a network slice (Network Slice related Identifier (s)), NF capacity information, network specific service authorization information, identification of stored information, Names of supported services, and respective support And endpoint information of each of the supported service instances. &Lt; RTI ID = 0.0 &gt; [0002] &lt; / RTI &gt;
16. The method of claim 15,
Wherein the identifier associated with the network slice includes Network Slice Selection Assistance Information (NSSAI), Single-Network Slice Selection Assistance Information (S-NSSAI), and NSI ID.
A communication device for managing a network function profile,
A processor and a memory containing instructions readable by the computer
Lt; / RTI &gt;
If the instruction is executed in the processor,
When a network function profile (NF profile) of a network function instance (NF instance) is changed, a network function repository function (NRF) receives an update request from the management system,
The NRF receiving the update request updates the network capability profile (NF profile) of the network function instance,
Wherein the NRF sends an update response to the management system,
A communication device that manages a network capability profile.
18. The method of claim 17,
The NRF includes the network function instance information,
Wherein the network function profile of the network function instance is kept up to date.
18. The method of claim 17,
The network function profile comprises:
An NF instance ID, a NF type, a Fully Qualified Domain Name (FQDN) or an IP address of a network function, a PLMN ID, an identifier related to a network slice (Network Slice related Identifier (s)), NF capacity information, network specific service authorization information, identification of stored information, Names of supported services, and respective support And endpoint information of each of the supported service instances. &Lt; RTI ID = 0.0 &gt; [0002] &lt; / RTI &gt;
A communication device for managing a network function profile,
A processor and a memory containing instructions readable by the computer
Lt; / RTI &gt;
If the instruction is executed in the processor,
When a network function instance (NF instance) is removed, the network function repository function (NRF) receives a deregistration request from the management system,
The NRF having received the deregistration request deletes the network capability profile (NF profile) of the network function instance,
Wherein the NRF sends a deregistration response to the management system,
A communication device that manages a network capability profile.

Images