KR20170114923A - Method and apparatus for communicating using network slice - Google Patents

Abstract

A communication method and a communication apparatus using a network slice are proposed. A method for performing communication in a control plane of a network system including a proposed access network and a core network includes receiving a connection request from a user terminal, performing mutual authentication with the user terminal based on the connection request, , Searches the subscription profile for the user terminal based on the connection request, and determines the network slice for the user terminal based on the subscription profile.

Description

TECHNICAL FIELD [0001] The present invention relates to a communication method using a network slice,

The following description relates to a communication method and a communication apparatus using a network slice, and more particularly, to a communication method and a communication apparatus related to network functional virtualization and a future network of IMT-2020.

Network Functions Virtualization (NFV) technology has been introduced as a technology to support network openness and virtualization to build future-oriented network and service infrastructure. It realizes a single network service by virtually instantiating, combining, and executing the required network function according to traffic. This enables network services to be configured in a timely manner by virtualizing network functions and actively controlling them according to the situation.

The present invention can provide a network slice management function according to a network slice life cycle such as creation, change, and disappearance of a network slice providing end-to-end network service.

The present invention can provide a user with a customized dynamic service based on a network slice.

The present invention can provide a procedure and a function for receiving a network service by allowing a user to access a network slice, change a network slice, and finally shut down.

A method of performing communications in a control plane of a network system including an access network (AN) and a core network (CN) according to an exemplary embodiment includes receiving an attach request from a user terminal, ; Performing mutual authentication with the user terminal based on the connection request; If the mutual authentication is completed, retrieving a subscription profile for the user terminal based on the connection request; And determining a network slice for the user terminal based on the subscription profile.

In a communication method according to an exemplary embodiment, the network slice may include one or more network functions virtualized to provide end-to-end network service to the user terminal.

In the communication method according to an exemplary embodiment, the connection request includes (a) information on a type of service to be used by the user terminal and information on characteristics of the user terminal, or (b) information on characteristics of the user terminal .

In the communication method according to an exemplary embodiment, the information on the type of the service may include at least one of a service type to be used by the user terminal, an application service distinguisher and a data network name to be connected, And may include information about one.

In a communication method according to an exemplary embodiment, the subscription profile includes information on a network slice allowed by the user terminal, and if the connection request does not include information on a type of service that the user terminal desires to use , And a default network slice.

The communication method according to an exemplary embodiment may further include transmitting the identifier of the determined network slice and the temporary identifier of the user terminal to the user terminal.

The communication method according to an exemplary embodiment may further include transmitting the identifier of the determined network slice and the temporary identifier of the user terminal to the MSLMF-CP.

The communication method according to an exemplary embodiment determines FCCF (Front-end Common Control Functions) suitable for the user terminal based on at least one of the current state of the user terminal, the local situation of the network system, and the policy for the network system The method comprising the steps of:

A communication method according to an exemplary embodiment of the present invention includes: determining the NSLCF based on the connection request when a NS Slot Control Function (NSLCF) corresponding to the user terminal is not found in the access network that received the connection request; And transferring the connection request to the determined NSLCF.

An NSLMF (Network Slice Mapping Functions) for determining a network slice to process a packet on a control plane transmitted from the user terminal based on an identifier of the determined network slice in a communication method according to an exemplary embodiment, And may be located in any one of the user terminals.

A communication method according to an exemplary embodiment of the present invention includes: receiving a control plane message (CP message) from the user terminal, a temporary identifier of the user terminal, and an identifier of the network slice; And determining a network slice to convey the control plane message based on the temporary identifier of the user terminal and the identifier of the network slice.

In the communication method according to an embodiment, the step of determining the network slice may be performed by NSLMF (Network Slice Mapping Functions) disposed in any one of the core network, the access network, and the user terminal.

A method for performing communications in a control plane of a network system including an access network and a core network according to an embodiment includes receiving a new service request from a user terminal; Determining whether the currently selected network slice can provide the corresponding service based on the new service request; Retrieving a subscription profile for the user terminal based on the new service request if the corresponding service is not provided in the currently selected network slice; Adding or changing a new network slice based on the subscription profile; And delivering the identifier of the new network slice to the user terminal.

In a communication method according to an embodiment, the step of changing to the new network slice comprises: determining a new network slice within a range permitted by the subscription profile based on the new service request; And selecting an FCCF or an NSLMF corresponding to the new network slice and setting a user terminal and associated network slice information in the selected FCCF or NSLMF, and transmitting an identifier of the new network slice to the user terminal Transmits the newly selected network slice identifier to the user terminal and may further forward the changed FCCF or NSLMF identifier when the FCCF or NSLMF change occurs.

A communication method according to an exemplary embodiment of the present invention includes: recognizing that a subscription profile for the user terminal has been changed; And paging the change to the subscription profile to the user terminal based on the result of the recognition.

A method for performing communications in a control plane of a network system including an access network and a core network according to an embodiment includes determining a detachment procedure based on a type of service utilized by the user terminal and a network context and policy step; Performing connection termination to the user terminal in a network slice used by the user terminal according to the connection termination procedure; And terminating the connection to the user terminal according to the connection termination procedure in the NSLMF as the connection termination procedure is completed in the network slice.

A communication method according to an exemplary embodiment of the present invention includes: receiving a detach request from the user terminal; Deleting a network slice configuration for the user terminal in a control plane of the network system in response to the connection termination request; And transmitting a response to the connection termination request to the user terminal as the network slice configuration is deleted.

A communication method according to an exemplary embodiment of the present invention includes recognizing an unnotified detachment for the user terminal or receiving a one-way connection termination from all network slices used by the user terminal; And deleting the network slice configuration for the user terminal in the control plane of the network system in response to the recognition or receipt of the random access termination or unilateral connection termination.

A method for performing communication in a user plane of a network system including an access network and a core network according to an embodiment includes receiving a user packet from a user terminal (UP packet); Mapping a network slice corresponding to the user plane packet; Transferring the user plane packet to the network slice; And processing the user plane packet through the network slice.

In the communication method according to an exemplary embodiment, the processing of the user plane packet may further include processing the user plane packet using the BSUF when there is a BSUF in which part or all of the network slice is shared.

The communication method according to an exemplary embodiment may further include completing the configuration of the forwarding table for the user terminal in the NSLMF located in any one of the core network, the access network, and the user terminal.

A method for performing communication in a network system including an access network and a core network according to an exemplary embodiment of the present invention includes selecting a network slice optimized for a service requested from a user terminal among network slices specialized for each service provided in the network system, Providing a user-customized service by providing the service to a user terminal; Configuring a service provided to the user terminal through the selected network slice by modifying the service to be optimized to the user environment and the characteristics of the service on a packet or service stream basis; And if it is not possible to satisfy the service requested from the user through the already executing network slice or if the change of the already executed network slice is required due to the performance limitation of the already executing network slice even if the service is provided, Creating a new network slice to provide a service or modifying the running network slice, wherein the network system comprises: a network slice operating environment provisioning unit configured with a network slice control apparatus and a plurality of network slices; A virtual resource for executing an operating environment of the network slice; A network slice management function for managing a life cycle of the network slice; A most resource management function for managing the life cycle of the virtual resource; A network slice service orchestration function for orchestrating the network slice and orchestrating a configuration of resources; A network slice service BSS / OSS function that provides the network slice with business support, operational management of the network slice, and business and operational management means of the entire network slice to the network slice provider; A network slice control portal function in which the user terminal can manage a network slice; And a network slice connection for the user terminal.

According to one embodiment, a customized service can be provided dynamically. More specifically, through the user-customized services of the three types proposed in the present invention, it is possible to improve the speed of constructing a network slice on a global scale, and to provide a service with a fast response speed.

According to one embodiment, by generalizing the service through the network slice, the physical network configured according to the current service can be integrated into a single network.

According to one embodiment, by implementing the network function in software, the integration of the cloud and the network can be accelerated.

1 is a diagram illustrating high level functions of network slicing according to one embodiment.
2 is a diagram illustrating a structure of a network slice system according to an embodiment.
3 is a diagram illustrating a service communication method using a network slice according to an exemplary embodiment of the present invention.
4 illustrates a functional structure in a control plane of a network slice according to an embodiment.
5 is a diagram illustrating an initial access procedure and a control message processing procedure for a network slice according to an embodiment.
6 is a diagram illustrating an additional procedure for a network slice according to an embodiment.
7 is a diagram illustrating a connection termination procedure for a network slice according to an exemplary embodiment of the present invention.
8 is a diagram illustrating a functional structure in a control plane of a network slice according to another embodiment.
9 is a diagram illustrating an initial access procedure and a message processing procedure for a network slice according to another embodiment.
10 is a diagram illustrating an additional procedure for a network slice according to another embodiment.
11 is a diagram illustrating a connection termination procedure for a network slice according to another embodiment.
12 illustrates a functional structure in a user plane of a network slice according to an exemplary embodiment.
13 is a diagram illustrating a functional processing procedure in a user plane of a network slice according to an embodiment.
FIG. 14 is a diagram showing an example of a functional structure in the case where the functions shown in FIG. 4 are arranged in a network system according to an embodiment.
FIG. 15 is a diagram illustrating an initial connection procedure in the functional structure shown in FIG. 14 according to an embodiment.
FIG. 16 is a diagram showing an example of a functional structure when arranging the functions shown in FIG. 8 in a network system according to an embodiment.
FIG. 17 is a diagram illustrating an initial connection procedure in the functional structure shown in FIG. 16 according to an embodiment.
FIG. 18 is a diagram showing another example of a functional structure when arranging the functions shown in FIG. 8 in a network system according to an embodiment.
FIG. 19 is a diagram illustrating an initial connection procedure in the functional structure shown in FIG. 18 according to an embodiment.
20 is a diagram showing another example of a functional structure when arranging the functions shown in FIG. 8 in a network system according to an embodiment.
FIG. 21 is a diagram illustrating an initial connection procedure in the functional structure shown in FIG. 20 according to an embodiment.
22 is a diagram showing another example of a functional structure in the case where the functions shown in FIG. 8 are arranged in a network system according to an embodiment.
FIG. 23 is a diagram illustrating an initial connection procedure in the functional structure shown in FIG. 22 according to an embodiment.
24 is a diagram showing an example of a functional structure in the case where the functions shown in FIG. 12 are arranged in a network system according to an embodiment.
FIG. 25 is a diagram illustrating a CP packet processing procedure in the functional structure shown in FIG. 24 according to an embodiment.
FIG. 26 is a diagram showing another example of the functional structure in the case where the functions shown in FIG. 12 are arranged in a network system according to an embodiment.
FIG. 27 is a diagram showing another example of a functional structure in the case where the functions shown in FIG. 12 are arranged in a network system according to an embodiment.
FIG. 28 is a diagram illustrating a CP packet processing procedure in the functional structure shown in FIG. 26 or 27 according to an embodiment.
29 is a diagram showing another example of a functional structure in the case where the functions shown in FIG. 12 are arranged in a network system according to an embodiment.
FIG. 30 is a diagram illustrating a CP packet processing procedure in the functional structure shown in FIG. 29 according to an embodiment.
31 is a diagram illustrating an electronic device that performs communication according to one embodiment.

Specific structural or functional descriptions of embodiments are set forth for illustration purposes only and may be embodied with various changes and modifications. Accordingly, the embodiments are not intended to be limited to the particular forms disclosed, and the scope of the disclosure includes changes, equivalents, or alternatives included in the technical idea.

The terms first or second, etc. may be used to describe various elements, but such terms should be interpreted solely for the purpose of distinguishing one element 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.

It is to be understood that when an element is referred to as being "connected" to another element, it may be directly connected or connected to the other element, although other elements may be present in between.

The singular expressions include plural expressions unless the context clearly dictates otherwise. In this specification, the terms "comprises ", or" having ", and the like, are used to specify one or more of the described features, numbers, steps, operations, elements, But do not preclude the presence or addition of steps, operations, elements, parts, or combinations thereof.

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

The embodiments described below may be used to perform communications. Hereinafter, an operation for performing communication is performed between UE (User Equipment), RAN (Radio Access Network), and CN (Core Network) by using functions defined in the control plane and user plane of the network slice Operation. Embodiments may be implemented in various forms of computing devices and / or systems, such as a smart phone, a smart home appliance, a personal computer, a laptop computer, a tablet computer, a wearable device, or a server constituting a RAN / CN. Hereinafter, embodiments will be described in detail with reference to the accompanying drawings. Like reference symbols in the drawings denote like elements.

1 is a diagram illustrating high-level functions of network slicing according to an exemplary embodiment.

Referring to FIG. 1, the communication functions between the UE, the RAN, and the CN may be divided into a network slice control plane 110 and a network slice user plane 120.

A high-level functional architecture for network slicing according to one embodiment is proposed as shown in FIG. This architecture can be used as a basic architecture for network slices and can be used to build more detailed architectures.

Here, a network slice is a combination of virtualized network functions for providing end-to-end network services, and can be configured on virtual resources. These network slices can have a certain level of isolation independence so that they do not affect each other.

The virtual network function may mean a network function (e.g., a virtual network function, a software network function, etc.) implemented by software. The physical network function may refer to a network function (physical network function) that is implemented depending on hardware. A virtualized network function means a network function capable of independently separating a plurality of logical network functions by virtualizing and abstracting physical network functions, or may mean a virtual network function.

The high-level functions may be defined to include all necessary functional elements to address network slicing requirements. In particular, the following requirements can be considered when defining the high-level functionality of the architecture, and other requirements can be supported through additional detail work on the functions defined in the architecture.

- Isolation and separation between network slice instances (NSLI)

- Resource and network function sharing between network slice implementers.

- allowing the UE to simultaneously obtain services from one or more specific network slice implementers

Selection procedure of a specific network slice for the UE (procedure (s) for selection)

Supporting Network Slicing Roaming

A network slice that efficiently supports multiple third parties requiring similar network characteristics.

With respect to the network slicing control plane 110, network slicing is a function for providing network services of various types of special purpose networks utilizing the underlying network + IT resources Can be defined. The network slicing control plane can be defined as a management function through the life cycle of the network slice, a control function in the process of using the network slice by the user such as selection, change, and termination of the network slice.

The network slicing user plane 120 is defined as the entirety of functions associated with network services provided through a network slice, and may specifically include functions for controlling the delivery of packets on a network slice and the delivery of packets on a network slice.

The service request / termination is a function in which the UE exchanges control signals related to the request and termination of the service to the network. The UE can directly request a specific service from the network or the network can determine the service considering the profile set for the UE or the context to which the UE belongs. The service request / termination function may be performed on an application basis or a UE device basis.

Service Classification is a network side function that classifies a service class using information transmitted from a UE or information managed by the network for the UE.

Slice Selection Control is a network-side function that selects a network slice implementation best suited to the service class and authorizes the UE to access the network slice according to the UE / user's access right. (network-side function). The network slice implementations may reside in CN and RAN, respectively, or may reside in an integrated domain of CN and RAN. The Slice Selection Control function can send a control signal to a network slice implement and a slice switch to configure a new service.

Service-to-Slice Mapping is a UE-side function that configures the required mapping relationship between a service and a network slice implementation in a UE.

A slice switch is a function that delivers a packet to the appropriate network slice implement. The slice switch may be located at the CN or RAN or UE depending on the defined area of the network slice implement. When a packet having no forwarding information arrives at the slice switch, the slice switch can request a service classification to determine a service class of the packet and acquire forwarding information as a result of classification of the service.

The CN Slice Instance can refer to a network slice implement defined on CN. The CN slice executable can be composed of virtualized resources of computing, storage and CN network elements and a CN virtual network function assigned to be used for a specific CN slice implementation.

The RAN slice implement can refer to a network slice implement defined on the RAN. RAN slice implementations may be comprised of virtualized resources of computing, storage, and RAN network elements and RAN virtual network functions assigned to be used for a specific RAN slice implementation.

The service context management at the RAN (Service Context Management at RAN) manages the service context from the viewpoint of the UE and the application basis, and the service context is managed by the RAN (Unsolicited RAN) Is a RAN function that controls the network parameters of the network.

Slice termination in a UE means a slice function including a mapping service to a network slice, generation or termination of network slice specific signals, and a UE function terminating a characteristic. do.

Common CN Functions / Resources may refer to functions or resources that are shared among multiple CN slice implementers.

Common RAN functions / resources may refer to functions or resources that are shared among multiple RAN slice implementers.

Function / Resource Sharing can mean the sharing of common functions and resources through unified interfaces. Function / resource sharing is a single integrated interface or function used to share functions and resources. Two interfaces defined for each of the shared and resource shares, or more interfaces defined by resource types such as database, storage, computing, . ≪ / RTI >

Slice Lifecycle Management Control (SLMC) can refer to the ability to manage and control network slices and network slice implementations during the whole lifecycle of a network slice. SLMC can be used to create, duplicate, modify, scale-in / out, status monitoring and deletion of network slices and network slice implementations. .

The Internal Function / Resource Interface may refer to the ability to access CN and RAN functions and resources in the operator's administration domain. The internal function / resource interface may include selection and return of functions and resources used in the network slice implementation.

Function / Resource Import / Export may mean the function of importing or exporting functions / resources with third parties or other operators.

Third-party access to networks slices ^{(3 rd Party Access to Network Slice} ) is a third-party access to the SLMC to create a third-party network Slice run body in a network slices generated by creating its own network slices or operator It may mean the function of opening and controlling.

SLMC's capabilities can create, duplicate, modify, scale, and delete network slices during the entire lifecycle of a network slice using the network functions and resources of computing, storage, and network elements. Resources are provided as virtualized network slices to ensure isolation between network slices and efficient sharing of physical resources. In addition, the SLMC can measure and monitor the state of the network slice, process state data, and perform appropriate control over the network slice.

Since a network slice can be realized with a plurality of execution objects, there can be many network slice execution objects having the same characteristics. These network slice implementations can evolve themselves through modifications and scaling. The SLIC controlled network slice can be placed in any network area including the CN and the RAN.

SLMC can create or modify network slices using network functions or resources provided by third parties or other operators. The function / resource import / export function can control the import and export process. Exchange of functions and resources may enable resource sharing among operators, network slice roaming between different operator domains, and third party specialized network slice creation.

In particular, the specialized network slice of a third party can play an important role in verticals market such as network industry, smart city IT infrastructure. A network slice that satisfies a service requirement may be deployed in different operator networks by exchanging necessary functions or resources among the operators. Because the same network slice is deployed in different operator networks, UEs visiting different operator networks can experience the same user experience.

By allowing a third party to access the SLMC, the SLMC can create / manage its own network slice or replicate existing network slices. The third party access function to the network slice can control access to the SLMC of the third party for this purpose.

Although each network slice implementor is isolated from each other by utilizing its own slice specific functionality and resources, there may be a function or resource that needs to be shared between network slice implementors. For example, there is an authentication function that must be shared among network slice implementers considering a single sign-on service or certification-as-a-service. Shared functions and resources can be accessed by multiple network slice implementors through some unified interfaces.

The unified interface can ensure flexibility and future proofness in independent evolution of functions, resources and network slices. A unified sharing interface should be designed to fairly share functions and resources between slice network implementations and at the same time be designed not to deteriorate isolation between network slice implementations. An integrated interface can be defined as a single interface valid for all functions and resources, or multiple interfaces specific to each group of functions and resources.

The network slice may be selected based on a UE request or a network decision. The UE may request a service on the network on a session basis, an application basis, or a UE connection basis. Upon receiving the request of the UE, the network may classify the service according to a service classification policy designed in advance by the operator. In addition, the network may classify services into a current context in which the user / UE profile and the user / UE reside.

The result of the service classification can be passed to the Slice Selection Control (SSC) function. The SSC can determine a network slice implement that is appropriate for the requested service class from the available network slice implementation list generated by the SLMC and the slice status report. In addition, the SSC can confirm the UE's access rights to the corresponding network slice implementation and thus complete the decision.

After selecting a network slice implement, the UE may receive information about the selected network slice implementation from the SSC, configure the parameters, and process the relevant network slice at the UE. In addition, the slice switch can configure a forwarding table to transmit packets to the selected network slice implement. The slice switch can locate the CN, RAN, or UE according to the placement area of the network slice. The three slice switches shown in Fig. 1 can represent this position change.

Slice-related functions in UEs such as Service-to-Slice Mapping, Slice Termination, Slice Switches can all be used to support simultaneous access to multiple network slices by a UE for single or multiple applications.

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

The network slice may be a combination of one or more virtual networked functions for providing end-to-end network services. The network slice system structure proposed in the present invention is as shown in FIG. The network slice 233 may be configured on virtualized resources 240 such as computing, storage, network, and the like. There is a network slice control function (NSLCF) 231 for controlling the operation of the network slice. A network slice operation environment 230 may include a network slice control function 231 and a plurality of network slices. Here, the network slice control function 231 may include functions such as operation management for network slice units, failure management, network slice access control, and the like.

The network slice management (NSLM) 270 may directly control the virtualized network functions constituting the network slice and the network slice to manage the life cycle such as creation, change, and termination of the network slice have.

Resource management (RM) 280 may refer to the ability to directly control resources for life cycle management such as creation, modification, and termination of a virtualized resource 240 for execution of a network slice have.

A network slice service orchestration (NSLO) 260 can create a network service (NS) provided on a network slice and control an execution environment. The execution environment control may mean constituting a virtual resource for executing the network service. For example, when the NSLO 260 makes a corresponding virtual resource request to the RM 280, the RM 280 may control and manage the associated resource to configure the resource for which the network slice can be executed and provide the configured resource. The NSLO 260 may transmit the network slice configuration information according to the created network service to the NSLM 270 so that a network slice that is a combination of virtual network functions can be configured.

When a network slice is changed or terminated such as expansion (scale-out) or reduction (scale-in) of a network slice, the NSLM 270 directly manages change control of the corresponding resource to the RM 280 Can be requested.

The NSLO 260, the NSLM 270 and the RM 280 are connected to the NFVO (NFVO Orchestrator), the VNFM (VNF Manager) and the VIM (Virtualized Infrastructure Manager) of the Network Function Virtualization Management & Orchestration (ETSI) Respectively. In this specification, a network slice architecture is defined to conform to the ETSI NFV architecture and related operations are proposed.

The network slice operator 210 operates and manages the network slice through the BSS / OSS 250 for the network slice of the network slice provider, 220 and the user-side network slice operator 221. [ The BSS / OSS 250 may define a network slice at a higher level desired by the user and request the NSLO 260 to realize the defined network slice. The BSS / OSS 250 also measures and analyzes the operational and fault conditions of the network slice operating environment 230, the virtual resources 240, and the like, and provides the NSLO 260 / NSLM 270) / RM 280 and the like.

The user 220 refers to a UE connected to the network slice 233 to receive a network service and may include, for example, an end user and an enterprise user. At this time, if the desired network service is not provided or if the desired network service is provided, the user can not receive the desired service through the currently executed network slice due to lack of resources spatially or performance, May request the user side network slice operator 221 to take the relevant action. In response, the user-side network slice operator 221 requests a change of a new network slice or a network slice being executed through the network slice control portal provided by the BSS among the BSS / OSS 250 of the network slice operator 210 .

The user 220 can be provided with the dynamic service through the network slice in three aspects. The first dynamic service can be created by creating a new network slice or by changing a running network slice. This dynamic service can be performed through the network slice management portal described above, and can be performed by a completely new network slice configuration or by selecting a network slice in the catalog. This allows creation or modification of network slices on a global scale within minutes.

The second is the selection of the network slice. When the user initially accesses the network while the service-specific network slice is running, a network slice providing the service desired by the user can be selected and provided to the user. If the user 220 desires a new service even after the user 220 initially connects, another network slice corresponding thereto may be additionally provided. The user 220 may use multiple network slices at the same time.

The third dynamic service is done inside the selected network slice. Even for the same kind of service, the service can be optimized and provided according to the user environment. The dynamic service can be provided in the smallest unit such as a packet unit or a service stream unit, and the response to the service request can be performed most quickly in this level of dynamic service. For example, reaction time within 1 millisecond can be satisfied.

3 is a diagram illustrating a service communication method using a network slice according to an exemplary embodiment of the present invention.

Referring to Figure 3, a usage flow diagram of a network slice at the user side is shown. Operation procedures for service provision through a running network slice are described below.

Step 301 may be performed according to the start of the network use of the user terminal.

At step 301, the user terminal may be determined whether it needs to create a new network slice. If it is necessary to create a new network slice, the user terminal can access the network slice management portal at step 303. Then, in step 305, the user terminal may establish a new network slice. Then, step 313 may be performed.

If it is not necessary to create a new network slice, at step 307, the user terminal may determine whether it needs to extend the network slice resource. If it is necessary to extend the network slice resources, the user terminal can access the network slice management portal at step 309. [ Then, in step 311, the user terminal can scale or scale down (scaling out / scaling in) the current network slice. Then, step 313 may be performed. Step 313 may be performed even if it is determined in step 307 that there is no need to create a new network slice.

In step 313, the user terminal may connect to a network slice that provides the requested service. Then, in step 315, the user terminal may use an on-demand service provided in the network slice. Then, in step 317, the user terminal can finish using all services.

In step 319, the user terminal may determine whether to turn off the UE without a connection termination procedure. If the UE is turned off after the connection is terminated, the user terminal may terminate the UE connection from the network slice in step 321.

Then, in step 323, the UE can turn off the power.

It is assumed that the network function is separated into the control plane function and the user plane function. The control plane may include functions for controlling delivery / processing procedures for user packets that are delivered to and processed by the user plane. In this specification, the control plane function and the user plane function can be completely separated. That is, assuming that there is no correlation between the network functional structures of the control plane and the user plane, the control plane function and the user plane function can be designed to be separated from each other. Thus, when there are a plurality of schemes, respectively, in separate control plane and user plane functional configurations and procedures, any plan of each plane can be selected and applied.

The connection lines connecting the functions shown in the drawings may be logical connection lines unless otherwise explicitly mentioned. If there is a physical meaning, it will be explicitly mentioned. An embodiment for physically implementing a logical connection line is also proposed in the present invention.

4 illustrates a functional structure in a control plane of a network slice according to an embodiment.

Referring to FIG. 4, there is shown the network functions of the control plane required in the process of the user accessing the currently executing network slice 450 to receive network services. When a user uses a plurality of network slices 450 at the same time, there may be network control functions shared by some or all of the constituent network slices 450.

Some of the shared network control functions need to be executed before executing the functions inside the network slice 450 and need to be shared with all of the network slices 450. [ This function is referred to as a front-end common control function (FCCF) 430.

An example of an FCCF may be mobility management functionality among the mobile communication network functions. In the case of mobility management functions, it may be appropriate for all network slices 450 to share the results because they are related to the location of the terminal, so they are managed as common functions rather than being managed per network slice 450.

There is a function that only a part of the network slice 450 among the shared network control functions share. This function is referred to as a back-end shared control function (BSCF) 460. [ In the case of FIG. 4 exemplarily shown, there may be a function shared only by the network slice # 1 control plane function and the network slice # 2 control plane function.

4 according to one embodiment shows functions related to the network slice connection procedure in the case where the FCCF 430 and the BSCF 460 are present. The NSLCF 420 may perform network slice selection, user authentication, and the like. As a result of the user authentication, a temporary identifier for the user terminal can be generated and transmitted to the related network function. The NSLCF 420 may include functions such as FCAPS (Fault, Configuration, Accounting, Performance, and Security) for each network slice, i.e., EM (Element Management) function for each network slice.

A Network Slice Mapping Function (CP) 440 for a control plane message (CP message) is a forwarding table for a network slice implementing entity for processing control plane messages. And transmits the control plane message to the retrieved network slice execution object.

The network slice implement can be changed by management of the network slice operator. In order to allow the network slice execution entity to be changed without affecting the user, the user needs to indirectly access the network execution entity. That is, only the network slice ID is informed to the user, and the relationship between the network slice ID and the execution object of the actual network slice is managed in the forwarding table, so that even if the network slice execution object is changed, only the forwarding table is updated, It may be possible to connect to the executing entity. In order to perform such a function, the NSLMF-CP 440 can search for the network slice executing entity from the forwarding table based on the temporary identifier and the network slice ID of the user terminal received from the user. Here, the user may refer to UE control plane function 410.

5 is a diagram illustrating an initial access procedure and a control message processing procedure for a network slice according to an embodiment.

Referring to FIG. 5, a procedure is shown in which a user initially accesses a network slice and performs a network control function using the functions defined in FIG.

For the connection and network slice selection process 510, an initial connection request may be sent to the NSLCF of the network at the control plane function (UE-CP) of the user terminal. The connection request may include a type of service desired by the user, characteristics of the user terminal, and the like.

Here, the service type may be a desired service type (e.g., enhanced mobile broadband (eMBB), massive machine type communication (mMTC), ultra-reliable low latency communication (uRLLC) Etc.), a data network name to be connected (e.g., Internet, IMS (IP Multimedia Subsystem), etc.). If the network was previously connected, the specification of the network slices that were allowed to connect in the previous connection may also be included in the connection request.

The NSLCF retrieves the authentication information for the UE from the subscriber information storage based on the connection request, performs mutual authentication in an encrypted environment for security with the UE, and confirms that the UE-CP is a network slice access permitted subscriber .

Once the mutual authentication is successfully completed, the NSLCF may retrieve the subscription profile from the subscriber information store. The retrieved subscription profile may include a specification of allowed network slices for the subscriber.

The subscription profile may define a network slice that must be provided to that subscriber by default. The default network slice is basically a network slice that allows users to connect even if they do not provide any information about the service they are requesting. For example, when a user terminal is a sensor terminal, a network slice that provides a sensor network service may be defined as a basic network slice. If the user terminal is a TV, a network slice providing a multimedia service may be defined as a basic network slice. If the user terminal is a smart phone, a network slice that provides a mobile communication network service may be defined as a basic network slice.

The NSLCF may select a network slice according to the UE-CP request message, taking into account the subscription profile and the connection request (e.g., the type of service the subscriber is sending, the terminal type, and previously allowed network slice information, etc.). In other words, the NSLCF can determine the specification of the network slice according to the request message from the UE-CP. At this time, the FCCF that can best provide the service to the user can be determined by the current state of the UE (e.g., service and spatial situation) and the local situation of the network and related policies.

The NSLCF may send the determined network slice specification, the FCCF identifier, and the UE's newly assigned temporary identifier to the UE-CP in a connection response to the connection request. The NSLCF may then send the new user's temporary identifier and the selected network slice information to the determined FCCF and the NSLMF-CP connected to the FCCF so that the associated functions are set in the FCCF and the NSLMF-CP. At this time, when transmitting the corresponding information to the NSLMF-CP, the NSLCF may transmit the corresponding information via the FCCF using the access point 480 instead of the access point 470 shown in FIG.

The UE-CP may store a network slice specification received via a connection response, an FCCF identifier, and a temporary identifier for itself assigned from the network. In this way, the UE-CP can transmit some or all of the stored information together with the control signal as needed.

The initial access procedure for the network slice of the UE-CP of the user can be completed through the above-described processes. The UE-CP may then send a control message associated with the service to the network slice to receive the network service. Here, the control message may include a protocol data unit (PDU) session establishment request for the service, a UE location update message, and the like. This procedure will be described with reference to the UE-initiated CP message processing 520. [

The UE-CP may send the CP message to the FCCF. Here, the CP message may also include an FCCF ID (FCCF ID), a UE temporary ID (UE temp ID), and an identifier (NSLs IDs) of a network slice to which a CP message is to be transmitted. These CP messages can be forwarded to the FCCF and NSLMF-CP for processing.

The FCCF can handle functions corresponding to the common control function among the functions required in the CP message. In addition, the FCCF may transmit a CP message to the NSLMF-CP such that the CP message is transmitted to the network slice, if necessary, depending on the type of the CP message.

The NSLMF-CP can search for the network slice execution entity corresponding to the identifier of the network slice from the forwarding table managed by the NSLMF-CP based on the temporary identifier of the UE and the identifier of the network slice. Then, the NSLMF-CP can forward the CP message to the retrieved network slice executables. The delivered CP message is processed in the BSCF and the corresponding network slice implement, and the processing result can be delivered to the UE-CP via the NSLMF-CP, FCCF in response to the CP message.

6 is a diagram illustrating an additional procedure for a network slice according to an embodiment.

A new network slice can be additionally allocated to the user terminal in addition to the currently allowed network slice by changing the subscription profile of the user, requesting a new service of the user, and the like. The FCCF allocated to the user terminal in the additional procedure can be changed from the pre-assigned FCCF # 1 to the new FCCF # 2.

In Fig. 6, a network slice addition procedure starting with two causes is shown. For example, the procedure for adding a network slice may include the case of a network initiated NSL change 610 and the case of adding a new network slice. In the additional procedure, the FCCF change and thus the change of the NSLMF-CP can be performed.

Specifically, if a change to a user's subscription profile results in the addition of a new network slice (i.e., network-initiated network slice change 610), then the NSLCF may recognize the change via an intra-network function. That is, the NSLCF may recognize a change in the subscription profile for the UE. The NSLF may then forward a paging request to the FCCF # 1 to inform the UE of the change. Then, the FCCF # 1 can page change to the UE-CP. That is, the FCCF # 1 can notify the UE-CP of the change of the subscription profile. The UE-CP notified of the change of the subscription profile can perform preparation for requesting a new service corresponding to the subscription profile change.

In the case of a new network slice addition or FCCF change 620, the UE-CP may send a new service request that is not supported in the allowed network slice to the FCCF # 1. Then, the FCCF # 1 recognizes the new service request and can forward the user's new service request to the NSLCF. The NSLCF can then retrieve the subscription profile for the UE and select a new network slice or a new FCCF. The NSLCF may then send a response containing the identifier of the new network slice list or FCCF to the FCCF # 1. In addition, NSLCF can update its contents to FCCF and NSLNF-CP to reflect the changed contents to FCCF and NSLMF-CP. There may be changes to the FCCF (FCCF # 1) and NSLMF-CP (NSLMF-CP 1) depending on the new network slice. In this case, the contents can be deleted from the FCCF (FCCF # 2) and the NSLMF-CP (NSLMF-CP 2) before the change, and the changed contents can be set to the FCCF and NSLMF-CP after the change. Then, the FCCF # 1 can transmit a response including the identifier of the new network slice and the identifier of the FCCF to the UE-CP. Then, the UE-CP may store the identifier of the newly changed network slices, the identifier of the FCCF, and the temporary identifier of the UE in order to transmit the UE-CP message to the network slice.

7 is a diagram illustrating a connection termination procedure for a network slice according to an exemplary embodiment of the present invention.

In the end of the network slice, there may be a request termination by a user terminal, an unsubscription termination (for example, power off of a user terminal that is not anticipated), and in FIG. 7, do.

First, in case of a detachment initiated by UE 710 initiated by the UE, the UE-CP may send a connection termination request to the FCCF. Then, deletion of the network slice configuration for the UE can be performed. The FCCF may then send a connection termination response to the UE-CP. The UE-CP may then store the identifier of the network slice, the identifier of the FCCF, and the UE's temporary identifier for subsequent reconnection.

Next, in the case of a detachment initiated by network 720 initiated by the network, an unnotified detachment of UE can be recognized from the UE. The network slice configuration for the UE may then be deleted.

If either the UE-initiated connection termination 710 or the network-initiated termination 720 is performed, then the network slice configuration for UE UE 730 is performed . Specifically, the FCCF may inform the NSLCF of the UE's connection termination with the UE's identifier and connection termination type. Then, the NSLCF can determine the connection termination procedure in consideration of the connection termination type, the network context, and the policy. Then, the NSLCF can inform the FCCF, NSLMF-CP, and all NSL-CPs of the connection end with the UE identifier, connection termination type, and connection termination procedure. And, in all NSL-CPs and BSCFs, a connection termination procedure for the UE can be executed. Then, the response to the connection termination notification along with the UE's identifier can be transferred from all the NSL-CPs to the NSLCF via the NSLMF-CP and the FCCF. Then, the NSLCF can inform the FCCF of the response with the connection termination procedure. Then, the connection termination procedure by the NSLCF can be executed. At this time, the UE may store the identifiers of the network slices, the FCCFs, the temporary identifiers allocated to the UEs, and the like, which are permitted to be used before the final termination, for reuse in the subsequent reconnection process.

8 is a diagram illustrating a functional structure in a control plane of a network slice according to another embodiment.

The descriptions in FIGS. 4 to 7 above are all for the case where the FCCF is required. On the other hand, FIG. 8 shows a case where the FCCF does not exist, that is, the control functions of the network slices used by one user do not have a function commonly used before reaching the network slice. For example, the user terminal may correspond to a wired terminal or a fixed wireless terminal.

In other words, FIG. 8 shows a case where the FCCF 430 does not exist in FIG. 4, and the functions shown in FIG. 8 are the same as those in FIG. 4, so that a detailed description will be omitted. However, the FCCF identifier that the UE stores and sends together when sending the CP message may be replaced with the NSLMF-CP identifier.

9 is a diagram illustrating an initial access procedure and a message processing procedure for a network slice according to another embodiment

Referring to FIG. 9, an initial connection procedure and a processing procedure of a post-connection CP message are shown. The overall operation except for the operation of the FCCF is the same as in Fig. However, if the location where the NSLMF-CP is realized is the core or access network, the ID of the NSLMF-CP is transferred to the UE-CP. However, if the location where the NSLMF- It need not be delivered to the UE-CP.

In other words, the Attachment & NSL Selection Process 910 and the UE-initiated Control Plane Message Processing (FEC) 920, shown in FIG. 9, 5, the detailed description will be omitted.

10 is a diagram illustrating an additional procedure for a network slice according to another embodiment.

Referring to FIG. 10, a network initiated NSL Change 1010 and a new network slice addition, and thus an NSLMF change (Add New NSLs or Change NSLMF) 1020, are shown.

The addition of the network slice may be performed network-initiated by changing the subscription profile, or may be performed at the request of the user. The NSLCF may notify the UE of the change of the subscription profile through any one of the network slices in use by the user so that a change request of the network slice may be made through the service request message transmitted from the UE.

Specifically, in the case of a network initiated network slice change 1010, the NSLCF may recognize a change in the subscription profile of the UE. The NSLCF may then send a page request to NSLMF-CP1 to notify the UE of the change to NSL #i. Then, NSL #i can page change to UE-CP. Then, the UE-CP can perform preparation for requesting a new service after changing the subscription.

Thereafter, if the UE's service change request (e.g., CP message) is sent to one of the active network slices, the corresponding network slice may send the corresponding CP message to the NSLCF to cause the network slice to change to match the service change request. Then, the network slice change or addition is completed by reflecting the identifier (new network slice ID) of the new network slice to the UE and the NSLMF. At this time, the NSLMF-CP may be changed according to the new or changed network slice. In this case, the content can be deleted from the NSLMF-CP (NSLMF-CP 1) before the change, and changed to the NSLMF-CP (NSLMF-CP 2) after the change.

Specifically, in the case of adding a new network slice or changing NSLMF 1020, the UE-CP may send a new service request not supported in the allowed network slice to NSL # i via NSLMF-CP 1. The NSL #i may then send a network slice addition or an NSLMF change request to the NSLCF via NSLMF-CP 1. The NSLCF can then retrieve the subscription profile for the UE, add a new network, or select a new NSLMF. The NSLCF can then respond with a new network slice list or NSLMF. This response can be sent to NSL #i via NSLMF-CP 1. Then, reconfiguration for UE-CP message processing can be performed. Then, the NSL #i may transmit the identifier of the new network slice and the identifier of the NSLMF to the UE-CP in response. At this time, the response may be forwarded to the UE-CP via NSLMF-CP 1. The UE-CP may store an identifier of the network slice, an identifier of the NSLMF, and a temporary identifier of the UE in order to transmit the CP message to the network slice at a later time.

In FIG. 10, which is illustratively shown, NSLMF-CP 1 represents an existing NSLMF and NSLMF-CP 2 can represent a newly assigned NSLMF with a change.

11 is a diagram illustrating a connection termination procedure for a network slice according to another embodiment.

The termination procedure of the network slice may include termination by a termination request from the user terminal and termination by termination of the connection regardless of the request of the user terminal perceived in each of the active network slices. Here, termination of the connection may mean termination of use of all network slices because the user terminal terminates the connection to the network.

First, the termination by the connection termination request from the user terminal may mean a detachment initiated by UE 1110 initiated by the UE. Specifically, the UE-CP can transmit a detach request to NSL # 1. Then, NSL # 1 can forward the connection termination request to NSLCF. The network slice configuration for the UE may then be deleted. The NSLCF can then send a connection termination response to NSL # 1. NSL # 1 can forward the connection termination response to the UE-CP. Then, the UE-CP can store the identifier of the network slice, the identifier of the NSLMF, and the temporary identifier of the UE, for later reconnection. Further, in NSL # 1, a connection termination procedure for the UE can be executed.

That is, in the case of the end request of the user terminal, when the end request is transmitted to one of the active network slices, the network slice that has received the corresponding message (i.e., end request) transmits the corresponding message to the NSLCF, Lt; / RTI >

In addition, the termination by termination of the connection of the user terminal recognized in each of the active network slices may refer to a detachment initiated by network 1120 initiated by the network. Specifically, NSL # 1 may inform the NSLCF of an unnotified detachment with the UE's temporary identifier. NSL # 2 can also inform the NSLCF of an unexpected connection termination with the UE's temporary identifier. In other words, NSLCF can be informed of all unacknowledged connection terminations from all network slices. In this case, the NSLCF may delete the network slice configuration for the UE.

That is, in the case of termination due to connection termination of the user terminal recognized in each of the network slices being used (for example, when the user terminal is terminated by power off), the connection blocking of the user terminal is recognized in all network slices in use , The corresponding information may be transmitted to the NSLCF. The NSLCF can confirm that the user terminal is disconnected from all network slices allowed to the UE and can execute the network slice termination procedure.

If a connection termination 1110 initiated by the UE or a connection termination 1120 initiated by the network is performed, then a network slice configuration deletion 1130 for the UE may be performed. Specifically, the NSLCF can determine the connection termination procedure in consideration of the connection termination type, the network context, and the policy. Then, the NSLCF can inform the NSLM # 1 and the NSL # 2 of the connection termination through the NSLMF-CP together with the UE identifier, the connection termination type, and the connection termination procedure. Then, NSL # 1 and NSL # 2 notified of termination of the connection can execute the connection termination procedure for the UE. The NSL # 1 and the NSL # 2 can transmit the response to the NSLMF-CP to the NSLCF together with the identifier of the UE and the notification of termination of the connection. Then, the NSLCF can transmit the deletion information upon termination of the connection to the NSLMF-CP. Then, the NSLMF-CP can execute the connection termination procedure by the NSLCF by deleting the information related to the connection termination.

At this time, in the case of the connection termination 1110 initiated by the UE, the network slice (i.e., NSL # 1) from which the termination request of the user terminal is received sends a network slice use termination completion response to the user terminal, Lt; RTI ID = 0.0 > network < / RTI > Accordingly, the portion indicated by the dotted line in the deletion of the network slice configuration 1130 for the UE may be omitted when the connection termination 1110 initiated by the UE is started.

12 illustrates a functional structure in a user plane of a network slice according to an exemplary embodiment.

Referring to Fig. 12, a user plane function relating to connection of a network slice is shown.

The network slice mapping function (NSLMF-UP) 1220 performs the same function as the NSLMF-CP 440 of FIG. 4, except that the user plane packet is processed. The main function of the NSLMF-UP 1220 is to search for a network slice executing entity that the user wants to access based on the identifier (NSL ID) of the network slice provided by the user and the temporary identifier (UE Temp-ID) . Since the description of the NSLMF-CP 440 can be applied to these functions, a detailed description will be omitted.

The Backend Shared User Plane Function (BSUF) 1240 may refer to a network function of a user plane shared by some or all of the network slices assigned to the user terminal. For example, the post-shared user plane function may include a database that may be required in processing a function in the user plane. The network slice 1230 may be combined with the network slice 450 described in the control plane of Figure 4 to configure one network slice, respectively.

The UE user plane function (UE-UP) 1210 may refer to the user plane functionality of the user terminal. The UE-UP 1210 may also combine with the UE-CP 410 of FIG. 4 to configure the UE.

13 is a diagram illustrating a functional processing procedure in a user plane of a network slice according to an embodiment.

Referring to FIG. 13, a procedure for accessing a network slice in a user plane to provide a service is shown.

Data / packets in the user plane may be forwarded to the corresponding network slice via the NSLMF-UP. The data / packet is processed in the corresponding network slice and the BSUF so that the service can be completed. In FIG. 13, which is illustratively shown, network slice 1 and network slice 2 (NSL # 3-UP) use BSUF.

Specifically, in the case of the NSL # 1 UP packet processing 1310, the UE-CP can transmit the UP packet in the NSLMP-UP. The NSLMP-UP may then select an appropriate network slice (i.e., NSL # 1) based on the UE identifier in the UP packet, the network slice identifier. Then, the NSLMP-UP can forward the UP packet to the selected NSL # 1. Then, the UP packet can be processed in NSL # 1 and BSUP.

Similarly, in the case of the NSL # 2 UP packet process 1320 and the NSL # 3 UP packet process 1330, the corresponding UP packet can be processed as in the NSL # 1 UP packet process 1310. However, in the case of the NSL # 3 UP packet processing 1330, since the NSL # 3 does not use the BSUF, the UP packet can be processed only in the NSL # 3.

Thus, the present invention has been described in terms of functionally connecting, changing, and terminating a network slice. Hereinafter, a method of deploying such a function in a real network composed of (R) AN (Radio Access network) and CN (Core Network) will be described. Additional functions such as NSLCFS Selection (NSLCFS Selection) and FF (Forwarding Function) for operating the above-described functions can be newly defined in the (R) AN area.

In the case of the functional layout, all procedures such as connection, modification, and termination of the network slice can be applied as described above. Therefore, only the contents added due to the feature placement disposition, the procedures related to the NSLCFS and the FF will be described.

Depending on the placement of the NSLMF and the realization of the network slice in the RAN, various functional arrangements may exist. This functional arrangement is divided into a control plane and a user plane, which are individually described. The arrangement of the actual functions is possible in any combination.

FIG. 14 is a diagram showing an example of a functional structure in the case where the functions shown in FIG. 4 are arranged in a network system according to an embodiment.

NSLCFS 1420 may refer to the ability to select an NSLCF 1450 that is optimal for the UE to forward the connection request forwarded to the RAN to the NSLCF 1450 located at the CN. Also, the FF 1430 may be located in the RAN and may refer to a function for routing the CP message of the UE to the FCCF 1460 or NSLCF 1450 of the CN.

Referring to Fig. 14, the functional arrangement when the control plane function of Fig. 4 is arranged in an actual network is shown.

The NSLCF 1450, the FCCF 1460, the NSLMF-CP 1470, the network slice 1480, and the BSCF 1490 may be located at the CN. The CP message of the UE is transmitted to the CN via the RAN. Since there is no location information of each function in the initial connection, the location of each function can be determined by analyzing in the RAN. That is, the NSLCF 1450, which can best respond to the service request of the UE, must be determined, and the NSLCF 1450 can then be determined based on the information provided by the UE. As described above, the selection of the NSLCF 1450 can be performed in the NSLCFS 1420, the location information of the selected NSLCF is set in the FF_CP, and the routing for the actual CP message can be performed in the FF-CP 1430 .

Since the operations described in FIG. 4 can be directly applied to the functions shown in FIG. 14, a detailed description will be omitted.

FIG. 15 is a diagram illustrating an initial connection procedure in the functional structure shown in FIG. 14 according to an embodiment.

Referring to FIG. 15, there is shown a procedure for initial connection to a network slice using the above-described functional arrangement and two additional functions (NSLCFS and FF).

An area 1510 indicated by a dotted line can be executed when the NSLCF for the information provided by the FF-CP from the UE is not retrieved from the forwarding table. That is, the area 1510 indicated by the dotted line can be executed when the FF-CP can not route the packet using only the information provided from the UE. In this case, the FF-CP may transmit the CP message received from the UE to the NSLCFS so that the appropriate NSLCF is selected. NSLCFS can select NSLCF considering service type and local policy. Then, NSLCFS can transmit the selected result (position information of the selected NSLCF) to the FF-CP. Then, the FF-CP can update the forwarding table using the selected result. The FF-CP can then forward the connection request to the selected NSLCF.

If the FF-CP is able to route packets using only the information provided by the UE, the area 1510 indicated by the dotted line may be omitted.

Since the subsequent steps are the same as those described in Fig. 5, a detailed description will be omitted. Finally, the FF-CP can update the forwarding table using the identifier of the NSLCF, the identifier of the FCCF, and the temporary identifier of the UE to prepare for future routing of user packets (including control plane and user plane).

FIG. 15 shows a procedure for updating the routing table using the connection response transmitted from the NSLCF to the UE-CP. However, the present invention can also be applied to a case where the NSLCF directly sends a message for updating the corresponding information to the FF.

FIG. 16 is a diagram showing an example of a functional structure when arranging the functions shown in FIG. 8 in a network system according to an embodiment.

Referring to Fig. 16, the functional arrangement for the case where there is no FCCF is shown in Fig. The NSLMF-CP 1620 may be placed at the CN and information may be required for the FF-CP 1610 to route the packet to the NSLMF-CP 1620. 14, except that the identifier of the NSLMF-CP 1620 is used instead of the identifier of the FCCF, and that there is no FCCF, and therefore a detailed description will be omitted.

FIG. 17 is a diagram illustrating an initial connection procedure in the functional structure shown in FIG. 16 according to an embodiment.

The connection and network slice selection process 1710 shown in FIG. 17 can be applied with the operations described in FIG. 15, except that the FCCF does not exist. Therefore, a detailed description will be omitted.

FIG. 18 is a diagram showing another example of a functional structure when arranging the functions shown in FIG. 8 in a network system according to an embodiment.

The functional arrangement shown in Fig. 18 is the same as that of Fig. 15 except that the NSLMF is placed in the (R) AN. That is, the NSLMF may be placed in the (R) AN with the FF / NSLMF-CP 1810. This does not require routing information for delivery to the NSLMF-CP. That is, NSLMF-CP is installed for each (R) AN, and (R) AN can switch directly to the CN's network slice.

FIG. 19 is a diagram illustrating an initial connection procedure in the functional structure shown in FIG. 18 according to an embodiment.

The connection and network slice selection process 1910 shown in FIG. 19 is the same as FIG. 17 except that the NSLMF is placed in the (R) AN in the form of FF / NSLMF-CP, and a detailed description will be omitted.

20 is a diagram showing another example of a functional structure when arranging the functions shown in FIG. 8 in a network system according to an embodiment.

The functional arrangement shown in FIG. 20 may indicate the case where the NSLMF is placed in the (R) AN with FF / NSLMF-CP 2010 and the network slice 2020 is also configured in the RAN. In this case, a RAN network slice control plane function (RN-NSLCF) 2030 can be defined to control the network slice 2020 in the RAN area. For the remaining functions, the above-described operations can be applied as they are, so that a detailed description will be omitted.

FIG. 21 is a diagram illustrating an initial connection procedure in the functional structure shown in FIG. 20 according to an embodiment.

In the case of the connection and network slice selection process 2110 shown in FIG. 21, after the network slice selection, the network slice selection related information may be transferred from the NSLCF to the RN-NSLCF to control the network slice of the (R) AN area.

That is, after selecting a network slice for the UE, the NSLCF may send information about the UE and the network slice to the RN-NSLCF. The RN-NSLCF can then store the configuration data.

Other operations of FIG. 19 may be applied as they are.

22 is a diagram showing another example of a functional structure in the case where the functions shown in FIG. 8 are arranged in a network system according to an embodiment.

The functional arrangement shown in Fig. 22 shows the case where the NSLMF-CP 2220 is arranged in the UE. Since the NSLMF-CP 2220 is placed in the UE, the identifier of the network slice determined in the NSLCF 2240 and the UE's temporary identifier may be transmitted to the UE-CP 2210 via the FF-CP 2230. [ The UE-CP 2210 may update the relevant variables of the NSLMF-CP 2220 using the identifier of the network slice and the temporary identifier of the UE. Through this, messages generated at the UE can be transmitted to the corresponding network slice through the NSLMF-CP 2220 at a later time. The description of FIG. 20 can be applied to the remaining functions as they are, and a detailed description thereof will be omitted.

FIG. 23 is a diagram illustrating an initial connection procedure in the functional structure shown in FIG. 22 according to an embodiment.

The connection and network slice selection process 2310 shown in FIG. 23 can be applied to the operations described above except that the NSLMF-CP is located in the UE, and therefore, a detailed description will be omitted.

The function allocation for the network slice operation of the control plane has been described above. Hereinafter, the function layout of the user plane for network slice operation will be described.

24 is a diagram showing an example of a functional structure in the case where the functions shown in FIG. 12 are arranged in a network system according to an embodiment.

Referring to FIG. 24, a case in which the NSLMF-UP 2430 is located at the CN is shown. As the NSLMF-UP 2430 is placed in the CN, information for routing from the (R) AN to the NSLMF-UP 2430 must be recorded in the FF-UP 2420.

In the above-described control plane function, the FF-CP monitors and updates the forwarding table (or the routing table) in the process of transmitting the connection response from the NSLCF-CP to the UE-CP. In addition, it does not exclude that the related information is transmitted from the NSLCF through the separate RAN control, thereby updating the forwarding table.

24 shows a functional arrangement in the case where the RN control 2410 updates the routing information of the FF-UP 2420. FIG. For the remaining functions, the foregoing description may be applied, so that a more detailed description will be omitted.

FIG. 25 is a diagram illustrating a CP packet processing procedure in the functional structure shown in FIG. 24 according to an embodiment.

Referring to FIG. 25, a network slice # 1 UP packet processing (NSL # 1 UP Packet Processing) 2510 is shown. Specifically, the configuration of forwarding tables of FF-UP and NSLMF-UP can be performed with the UE and the selected network slice in the UE connection procedure. Then, the UE-UP can transmit the UP packet to be transmitted to the NSL # 1 through the FF-UP. Then, the FF-UP can forward the UP packet to the NSLMF-UP. Then, the NSLMF-UP can forward the UP packet to NSL # 1. And UP packet can be processed in NSL # 1 including BSUP.

Here, the routing information of the FF-UP can be configured in the connection procedure.

FIG. 26 is a diagram showing another example of the functional structure in the case where the functions shown in FIG. 12 are arranged in a network system according to an embodiment. The functional arrangement shown in FIG. 26 may indicate the case where the NSLMF-UP 2610 is placed in the (R) AN.

FIG. 27 is a diagram showing another example of a functional structure in the case where the functions shown in FIG. 12 are arranged in a network system according to an embodiment. 27 may indicate the case where the NSLMF-UP 2710 is placed in the (R) AN and the network slice 2720 is extended to the (R) AN.

FIG. 28 is a diagram illustrating a CP packet processing procedure in the functional structure shown in FIG. 26 or 27 according to an embodiment.

The network slice # 1 UP packet process 2810 shown in FIG. 28 may represent the UP data / packet process procedure in the functional arrangement of FIG. 26 and FIG. At this time, the NSLMF-UP can perform the function of transmitting the UP data / packet to the corresponding network slice.

29 is a diagram showing another example of a functional structure in the case where the functions shown in FIG. 12 are arranged in a network system according to an embodiment.

The functional arrangement shown in FIG. 29 may indicate when the NSLMF-UP 2910 is deployed at the UE. For example, the functional arrangement of FIG. 29 can be applied when the UE corresponds to a dedicated terminal of a specific network slice.

The remaining functions can be applied as described above, so that detailed description is omitted.

FIG. 30 is a diagram illustrating a CP packet processing procedure in the functional structure shown in FIG. 29 according to an embodiment.

The network slice # 1 UP packet process 3010 shown in FIG. 30 is different from the above description in that the NSLMF-UP is installed in the UE, and the basic operation is the same as described above. Therefore, a detailed description will be omitted.

31 is a diagram illustrating an electronic device that performs communication according to one embodiment.

31, a communication device 3100 according to an embodiment includes a memory 3110 and a processor 3120. [ The memory 3110 and the processor 3120 can communicate with each other via a bus 3130.

Memory 3110 may include instructions readable by a computer. The processor 3120 can perform the aforementioned operations as the instructions stored in the memory 3110 are executed in the processor 3120. [ The memory 3110 may be a volatile memory or a non-volatile memory.

The processor 3120 may execute instructions or programs, or may control the communication device 3100. The communication device 3100 may be implemented as part of various computing devices. In addition, the communication apparatus 3100 can process the above-described operation.

The processor 3120, which performs communication in the control plane of the network system including the access network and the core network, receives the connection request from the user terminal, performs mutual authentication with the user terminal based on the connection request, Retrieves a subscription profile for the user terminal based on the connection request, and determines a network slice for the user terminal based on the subscription profile.

Here, the network slice may include one or more network functions virtualized to provide end-to-end network services to the user terminal.

The access request may include information on the type of service the user terminal desires to use and the characteristics of the user terminal. The information on the type of service may include information about at least one of a type of service desired by the user terminal, an application service distinguisher, a data network name to be connected, and a network slice to which the user terminal has connected in the past. The subscription profile may include information about network slices allowed for the user terminal.

In addition, the communication device may forward the identifier of the determined network slice and the temporary identifier of the user terminal to the user terminal.

In addition, the communication device may forward the identifier of the determined network slice and the temporary identifier of the user terminal to the MSLMF-CP.

In addition, the processor 3120, which performs communications in the control plane of the network system including the access network and the core network, receives a new service request from the user terminal, retrieves a subscription profile for the user terminal based on the new service request Adds a new network slice or changes to a new network slice based on the subscription profile, and delivers the identifier of the new network slice to the user terminal.

In addition, the processor 3120, which performs communication in the control plane of the network system including the access network and the core network, determines the connection termination procedure based on the type of service utilized by the user terminal and the network context and policy, And terminates the connection to the user terminal according to the connection termination procedure in the NSLMF as the connection termination procedure is completed in the network slice.

In addition, the processor 3120, which performs communications in a user plane of a network system including an access network and a core network, receives a user plane packet (UP packet) from a user terminal, Maps the slice, passes the user plane packet to the network slice, and processes the user plane packet through the network slice.

31 are applied as they are through the FIG. 1 to FIG. 30 as they are, the detailed description will be omitted.

The embodiments described above may be implemented in hardware components, software components, and / or a combination of hardware components and software components. For example, the devices, methods, 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, such as an array, a programmable logic unit (PLU), a microprocessor, or any other device capable of executing and responding to instructions. The processing device may execute an operating system (OS) and one or more software applications running on the operating system. The processing device may also access, store, manipulate, process, and generate data in response to execution of the software. For ease of understanding, the processing apparatus may be described as being used singly, but those skilled in the art will recognize that the processing apparatus may have a plurality of processing elements and / As shown in FIG. For example, the processing unit may comprise a plurality of processors or one processor and one controller. Other processing configurations are also possible, such as a parallel processor.

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

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

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

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 > or equivalents, even if it is replaced or replaced.

Claims (20)

1. A method for performing communications in a control plane of a network system including an access network (AN) and a core network (CN)
Receiving an attach request from a user terminal;
Performing mutual authentication with the user terminal based on the connection request;
If the mutual authentication is completed, retrieving a subscription profile for the user terminal based on the connection request; And
Determining a network slice for the user terminal based on the subscription profile;
/ RTI > The method according to claim 1,
The network slice
And one or more network functions virtualized to provide end-to-end network services to the user terminal. The method according to claim 1,
The connection request
(a) information on a type of a service to be used by the user terminal and information on characteristics of the user terminal, or (b) information on characteristics of the user terminal. The method of claim 3,
Information about the type of service
Wherein the user terminal includes information on at least one of a service type to be used by the user terminal, an application service distinguisher, a data network name to be connected, and a network slice to which the user terminal has connected in the past. The method according to claim 1,
The subscription profile
Information about a network slice allowed for the user terminal, and if information on a type of service to be used by the user terminal is not included in the connection request, information about a default network slice . The method according to claim 1,
Transmitting the identifier of the determined network slice and the temporary identifier of the user terminal to the user terminal
Lt; / RTI > The method according to claim 1,
Transmitting the identifier of the determined network slice and the temporary identifier of the user terminal to the MSLMF-CP
Lt; / RTI > The method according to claim 1,
Determining a FCCF (Front-end Common Control Functions) suitable for the user terminal based on at least one of a current status of the user terminal, a local situation of the network system, and a policy for the network system
Lt; / RTI > The method according to claim 1,
If the NSLCF corresponding to the user terminal is not found in the access network that received the access request, determining the NSLCF based on the access request; And
Forwarding the connection request to the determined NSLCF
Lt; / RTI > The method according to claim 1,
The NSLMF (Network Slice Mapping Functions) for determining a network slice to process a packet on the control plane transmitted from the user terminal based on the determined identifier of the network slice
The access network, and the user terminal. The method according to claim 1,
Receiving a control plane message (CP message), a temporary identifier of the user terminal and an identifier of the network slice from the user terminal; And
Determining a network slice to convey the control plane message based on the temporary identifier of the user terminal and the identifier of the network slice
Further comprising: A method for performing communication in a control plane of a network system including an access network and a core network,
Receiving a new service request from a user terminal;
Determining whether the currently selected network slice can provide the corresponding service based on the new service request;
Retrieving a subscription profile for the user terminal based on the new service request if the corresponding service is not provided in the currently selected network slice;
Adding or changing a new network slice based on the subscription profile; And
Transmitting an identifier of the new network slice to the user terminal
/ RTI > 13. The method of claim 12,
The step of changing to the new network slice
Determining a new network slice within a range permitted by the subscription profile based on the new service request; And
Selecting a new FCCF or NSLMF corresponding to the new network slice and setting the user terminal and related network slice information in the selected FCCF or NSLMF
Lt; / RTI >
The step of delivering the identifier of the new network slice to the user terminal
Transfers the newly selected network slice identifier to the user terminal, and further communicates the changed FCCF or NSLMF identifier when a change of the FCCF or the NSLMF occurs. 13. The method of claim 12,
Recognizing that the subscription profile for the user terminal has changed; And
Paging a change to the subscription profile to the user terminal based on a result of the recognition
Lt; / RTI > A method for performing communication in a control plane of a network system including an access network and a core network,
Determining a detachment procedure based on the type of service utilized by the user terminal and the network context and policy;
Performing connection termination to the user terminal in a network slice used by the user terminal according to the connection termination procedure; And
Performing deletion of information on the user terminal according to the connection termination procedure in the NSLMF as the connection termination procedure is completed in the network slice
/ RTI > 16. The method of claim 15,
Receiving a detach request from the user terminal;
Deleting a network slice configuration for the user terminal in a control plane of the network system in response to the connection termination request; And
Transmitting a response to the connection termination request to the user terminal as the network slice configuration is deleted;
/ RTI > 16. The method of claim 15,
Recognizing a random access termination to the user terminal or receiving a one-way connection termination from all network slices used by the user terminal; And
Deleting a network slice configuration for the user terminal in a control plane of the network system in response to the recognition or receipt of the random access termination or unilateral termination;
Lt; / RTI > A method of performing communications in a user plane of a network system including an access network and a core network,
Receiving a user plane packet (UP packet) from a user terminal;
Mapping a network slice corresponding to the user plane packet;
Transferring the user plane packet to the network slice; And
Processing the user plane packet through the network slice
/ RTI > 19. The method of claim 18,
The step of processing the user plane packet
If there is a BSUF in which part or all of the network slice is shared, further processing the user plane packet using the BSUF. A method for performing communications in a network system including an access network and a core network,
Providing a user-customized service by selecting a network slice optimized for a service requested from the user terminal among the network slices specific to the service provided by the network system and providing the network slice to the user terminal;
Configuring a service provided to the user terminal through the selected network slice by modifying the service to be optimized to the user environment and the characteristics of the service on a packet or service stream basis; And
If the service requested by the user can not be satisfied through the already executing network slice or if the change of the already executed network slice is required due to the performance limitation of the already executing network slice even if the service is provided, Creating a new network slice to provide, or changing the running network slice
Lt; / RTI >
The network system
Providing a network slice operating environment consisting of a network slice control device and a plurality of network slices;
A virtual resource for executing an operating environment of the network slice;
A network slice management function for managing a life cycle of the network slice;
A most resource management function for managing the life cycle of the virtual resource;
A network slice service orchestration function for orchestrating the network slice and orchestrating a configuration of resources;
A network slice service BSS / OSS function that provides the network slice with business support, operational management of the network slice, and business and operational management means of the entire network slice to the network slice provider;
A network slice control portal function in which the user terminal can manage a network slice; And
The network slice connection for the user terminal
/ RTI >

Images