WO2018112745A1

WO2018112745A1 - Method, entity and system for obtaining network slice instance information

Info

Publication number: WO2018112745A1
Application number: PCT/CN2016/111046
Authority: WO
Inventors: 倪慧; 余芳; 李岩
Original assignee: 华为技术有限公司
Priority date: 2016-12-20
Filing date: 2016-12-20
Publication date: 2018-06-28

Abstract

An embodiment of the present invention relates to a method and entity for obtaining network slice instance information, the method comprising: a network slice selection function entity sending a first request message to a network slice instance information management entity, and the first request message being used for querying information of a network slice instance; the network slicing selection function entity receiving the information of at least one network slice instance from the network slice instance information management entity. The embodiment of the present invention solves the problem in the prior art wherein internal functions of a network slice are not well isolated from an external system.

Description

Method, entity and system for obtaining network slice instance information

Technical field

The embodiments of the present invention relate to the field of communications, and in particular, to a method, an entity, and a system for acquiring network slice instance information.

Background technique

The network slicing technology provides a new type of network and service mode. The physical network is divided into multiple network slicing instances. Each network slicing instance performs customized tailoring of network functions and management of corresponding network functions according to the needs of the business scenario. And management, to achieve a variety of services to share a broadband network infrastructure, while maintaining the relative independence of business implementation, so as to better meet the individual needs of consumers and businesses for each service. The network slice instance may be simply referred to as a network slice or slice. Personalized needs include coverage area, duration, capacity, speed, latency, reliability, security, and availability. A network slice can be viewed as an instantiated core network architecture. Currently, network segmentation scenarios considered by the industry include Mobile Broadband, Multimedia, Massive Machine Type Communication, and Critical Machine Class Communication (Critical). Machine Type Communication).

For the core network architecture adopting the network slicing technology, the user equipment (User Equipment, UE) can access a single network slice, and can also access multiple network slices, and simultaneously use different services provided by multiple network slices. For example, a network slice selection function (NSSF) entity selects a core network slice serving the UE according to the UE's auxiliary information, the slice instance information, and the network policy. The NSSF entity may have three locations in the network slicing architecture: the NSSF entity is deployed independently, and the NSSF entity is located in the Common Control Plane (CP) Network Function (NFs), the NSSF entity and the radio access. The network (Radio Access Network, RAN) nodes are jointly deployed.

In the prior art, the lifecycle management operations of the network slice (including instantiation of the network slice, expansion and contraction, etc.) and real-time information maintenance are all performed by the network slice management system. The NSSF entity interacts with the network slice management system to obtain slice instance information (such as slice online notification, slice operation information, etc.). The latter two of the three cases for the location of the NSSF entity in the network slicing architecture: When the NSSF entity is deployed as a shared control plane network function or the NSSF entity is deployed in conjunction with the RAN node, in both cases, the NSSF entity acts as a network An internal function of the slice needs to interact with the network slice management system, which results in complex interaction between the network slice and the network management system, and belongs to cross-layer and cross-system interaction, that is, the business logic function in the network slice interacts with the management entity that generates the network slice, which will affect The isolation between the internal functions of the network slice and the external system.

Summary of the invention

The embodiment of the invention provides a method, an entity and a system for acquiring network slice instance information, which are used to solve the problem of poor isolation between the internal functions of the existing network slice and the external system.

In a first aspect, an embodiment of the present invention provides a method for obtaining network slice instance information. The network slice selection function entity sends a first request message to the network slice instance information management entity, where the first request message is used to query information of the network slice instance; and the network slice selection function entity receives at least one network slice instance from the network slice instance information management entity. information.

In the embodiment of the present invention, the network slice selection function entity does not need to interact with the network slice management system, but interacts with the network slice instance information management entity, thereby avoiding the interaction between the service logic function in the network slice and the management entity generating the network slice. This enhances the isolation between the internal functions of the network slice and the external system.

In a possible implementation, before the network slice selection function entity sends the first request message to the network slice instance information management entity, the network slice selection function entity receives the second request message from the UE, where the second request message is used to trigger the network slice. The selection function entity sends a first request message to the network slice instance information management entity, where the second request message is a session establishment request message or an attach request message or a location update request message. This embodiment provides a possible case where the triggering network slice selection function entity sends a first request message to the network slice instance information management entity.

In a possible implementation manner, after the network slice selection function entity receives the information of the at least one network slice instance from the network slice instance information management entity, the network slice selection function entity performs network slice selection according to the information of the at least one network slice instance. This embodiment gives a specific way for the network slice selection function entity to utilize the information of the network slice instance.

In a possible implementation manner, the network slice selection function entity sends a third request message to the network slice instance information management entity, where the third request message is used to subscribe to the change information of the network slice instance information; the network slice selection function entity is sliced from the network The instance information management entity receives the first notification The first notification message carries the change information of the network slice instance information; the network slice selection function entity performs network slice selection or reselection according to the change information of the network slice instance information. According to this embodiment, the network slice selection function entity subscribes to the change information of the network slice instance information by sending the third request message, thereby avoiding receiving the change information of the network slice instance information of the entire network.

In a possible implementation manner, before the network slice selection function entity sends the third request message to the network slice instance information management entity, the network slice selection function entity receives the second notification message, the second notification message, from the network slice instance information management entity. Information used to indicate the network slice instance and network slice instance of the online. According to this embodiment, after receiving the second notification message, the network slice selection function entity sends a third request message to the network slice instance information management entity according to the online network slice instance, so that the change information of the subscription network slice instance information can be provided. in accordance with.

In a possible implementation manner, the third request message includes at least one of the following: a usage type of the UE supported by the subscribed network slice instance, a UE capability supported by the subscribed network slice instance, and a service supported by the subscribed network slice instance. Type, the type of the subscribed network tile instance, the tenant ID of the subscribed network tile instance, and the identity of the subscribed network tile instance.

In a possible implementation manner, the first request message carries at least one of the following information: a type of use of the UE supported by the queried network slice instance, a UE capability supported by the queried network slice instance, and a service supported by the queried network slice instance. Type, type of the network slice instance to be queried, tenant ID of the network slice instance of the query, and ID of the network slice instance of the query.

In a possible implementation manner, the information of the network slice instance includes an identifier of the network slice instance and at least one of the following: a usage type of the UE supported by the network slice instance, a UE capability supported by the network slice instance, and a network slice instance support. Service type, type of network slice instance, access point name of network slice instance, tenant ID of network slice instance, whether network slice instance supports roaming user, location of network slice instance, available capacity of network slice instance, network slice instance Service-Level Agreement (SLA) parameters, status of network slicing instances.

In a second aspect, a method of obtaining network slice instance information is provided. The network slice instance information management entity receives the first request message from the network slice selection function entity; the network slice instance information management entity queries the network slice instance information according to the first request message; the network slice instance information management entity selects the function entity from the network slice Send information about at least one network slice instance.

In a possible implementation manner, before the network slice instance information management entity receives the first request message from the network slice selection function entity, the network slice instance information management entity removes the network slice from the network The system receives the second request message and updates the information of the network slice instance according to the second request message.

In a possible implementation manner, the network slice instance information management entity receives a third request message from the network slice selection function entity, where the third request message is used to subscribe to the change information of the network slice instance information; and the network slice instance information management entity is configured according to the The third request message sends a first notification message to the network slice selection function entity, where the first notification message carries the change information of the network slice instance information, where the network slice instance information management entity sends the first message to the network slice selection function entity according to the third request message. Before the notification message, the network slice management system receives the change information of the network slice instance information.

In a possible implementation manner, before the network slice instance information management entity receives the third request message from the network slice selection function entity, the network slice instance information management entity receives the second notification message from the network slice management system, where the second notification message is used. The information indicating the uplink network slice instance and the network slice instance; the network slice instance information management entity sends a second notification message to the network slice selection function entity.

In a third aspect, a method of obtaining network slice instance information is provided. The network slice management system sends a first notification message to the network slice instance information management entity, where the first notification message carries the change information of the network slice instance information.

In a possible implementation, the network slice management system sends a second notification message to the network slice instance information management entity, where the second notification message is used to indicate the information of the online network slice instance and the network slice instance.

On the other hand, the embodiment of the present invention provides a network slice selection function entity, which can implement the functions performed by the network slice selection function entity in the method design of the first aspect, and the function can be implemented by hardware. The corresponding software implementation can also be performed by hardware. The hardware or software includes one or more modules corresponding to the above functions.

In one possible design, the structure of the network slice selection function entity includes a processor and a communication interface configured to support the network slice selection function entity to perform a corresponding function in the above method. The communication interface is used to support communication between the network slice selection function entity and a network slice instance information management entity or other entity. The network slice selection function entity can also include a memory for coupling with the processor that holds program instructions and data necessary for the network slice selection function entity.

In another aspect, the embodiment of the present invention provides a network slice instance information management entity, where the network slice instance information management entity can implement the network slice instance information in the foregoing method design. The function performed by the entity management entity, the function may be implemented by hardware, or may be implemented by hardware corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

In one possible design, the structure of the network slice instance information management entity includes a processor and a communication interface configured to support the network slice instance information management entity to perform a corresponding function in the above method. The communication interface is configured to support communication between the network slice instance information management entity and a network slice selection function entity or a network slice management system or other entity. The network slice instance information management entity may also include a memory for coupling with the processor that holds program instructions and data necessary for the network slice instance information management entity.

In another aspect, the embodiment of the present invention provides a network slice management system, which can implement the functions performed by the network slice management system in the method design of the third aspect, and the function can be implemented by hardware, or The corresponding software implementation is performed by hardware. The hardware or software includes one or more modules corresponding to the above functions.

In one possible design, the network slice management system includes a processor and a communication interface configured to support the network slice management system to perform corresponding functions in the above methods. The communication interface is used to support communication between the network slice management system and a network slice instance information management entity or other entity. The network slice management system can also include a memory for coupling with the processor that holds program instructions and data necessary for the network slice management system.

In another aspect, an embodiment of the present invention provides a communication system, where the system includes the network slice selection function entity, the network slice instance information management entity, and the network slice management system.

In still another aspect, an embodiment of the present invention provides a computer storage medium for storing computer software instructions for the network slice selection function entity, which includes a program designed to execute the above first aspect.

In still another aspect, an embodiment of the present invention provides a computer storage medium for storing computer software instructions used by the network slice instance information management entity, including a program designed to execute the second aspect.

In still another aspect, an embodiment of the present invention provides a computer storage medium for storing computer software instructions used by the network slice management system, including a program designed to execute the third aspect.

In still another aspect, an embodiment of the present invention provides a computer program product, including instructions, when the program is executed by a computer, the instruction causes a computer to perform the method design of the first aspect The network slice selects the function performed by the functional entity.

In still another aspect, an embodiment of the present invention provides a computer program product, including instructions, when the program is executed by a computer, the instruction causes a computer to execute the network slice instance information management entity executed in the method design of the second aspect The function.

In still another aspect, an embodiment of the present invention provides a computer program product, comprising instructions, when executed by a computer, causing a computer to perform the functions performed by the network slice management system in the method design of the third aspect above. .

Compared with the prior art, in the solution provided by the embodiment of the present invention, a network slice instance information management entity is configured in the network, and the network slice instance information management entity is configured to store network slice instance information, and the network slice selection function entity is to the network. The slice instance information management entity sends a network slice information query request message, and receives information of at least one network slice instance returned by the network slice instance information management entity according to the network slice information query request message. Because the network slice instance information management entity is deployed, the network slice selection function entity does not need to interact with the network slice management system, but interacts with the network slice instance information management entity, thereby avoiding the service logic function in the network slice and generating the network slice. The management entity interacts to enhance the isolation between the internal functions of the network slice and the external system.

DRAWINGS

FIG. 1 is a schematic diagram of a network slice deployment scenario according to an embodiment of the present disclosure;

2 is a schematic diagram of communication of a method for acquiring network slice instance information according to an embodiment of the present invention;

FIG. 3 is a schematic diagram of communication of another method for obtaining network slice instance information according to an embodiment of the present disclosure;

FIG. 4 is a schematic diagram of communication of a method for acquiring network slice instance information according to an embodiment of the present disclosure;

FIG. 5 is a schematic diagram of communication of a method for acquiring network slice instance information according to an embodiment of the present invention;

FIG. 6 is a schematic structural diagram of a network slice selection function entity according to an embodiment of the present disclosure;

FIG. 7 is a schematic diagram of another possible structure of a network slice selection function entity according to an embodiment of the present disclosure;

FIG. 8 is a schematic structural diagram of a network slice instance information management entity according to an embodiment of the present disclosure;

FIG. 9 is a schematic diagram of another possible structure of a network slice instance information management entity according to an embodiment of the present disclosure;

FIG. 10 is a schematic structural diagram of a network slice management system according to an embodiment of the present disclosure;

FIG. 11 is a schematic diagram of another possible structure of a network slice management system according to an embodiment of the present invention.

detailed description

The technical solutions in the embodiments of the present invention will be described below in conjunction with the accompanying drawings in the embodiments of the present invention.

In the existing network segmentation scenario, when multiple NSSF entities in the network need to obtain information about the network sharding instance, they need to interact with the network snippet management system. The NSSF entity is the internal network function of the network slice, the NSSF entity and the network slice. The interaction between the management systems is complex, resulting in poor isolation between the internal functions of the network slice and the external system. For the above problem, the embodiment of the present invention adds a network slice instance information management entity based on the existing network architecture, and the network slice instance information management entity is configured to store network slice instance information in the network, and is an NSSF entity in the network. The network slice instance information is provided to avoid interaction between the NSSF entity and the network slice management system, thereby enhancing the isolation between the internal functions of the network slice and the external system.

FIG. 1 is a schematic diagram of a network segment deployment scenario according to an embodiment of the present invention, where a UE can simultaneously access multiple slices. For example, the UE can simultaneously access Network Slice A, Network Slice B, and Network Slice C. The NSSF entity selects a network slice for the UE according to the indication of the UE, and needs to interact with a Home Subscriber Server (HSS) to obtain network slice selection assistance information of the UE, such as subscription information of the UE; and interact with the network slice instance information management entity. Get the slice instance information (such as slice online notification, slice run information, etc.). The NSSF entity performs the network slice selection function according to the acquired UE network slice selection auxiliary information and the slice instance information, and selects an appropriate slice to provide services for the UE. The NSSF entity can be deployed in the RAN or shared control plane network function. For example, it is deployed in an access and mobility management function (AMF) device as a logical function of the AMF device. The network slice instance information management entity stores the information of the slice instance in the network, and the network slice instance information management entity decouples the life cycle management of the network slice management system and the business logic of the slice internal network element.

The network slice management system is an existing entity, and is responsible for lifecycle management of network slices, such as instantiation of network slices, expansion and contraction operations, and operation status monitoring. The network slice instance information management entity is a new entity, which may be a database. Both can be deployed independently.

In one example, the network slice management system synchronizes the slice instance information to the network slice instance information management entity. The network slice instance information management entity stores the slice instance information in the network. The slice instance information includes at least one of a network slice instance identifier and the following information: a UE usage type (specifically used to indicate a type of the UE, such as a Care UE usage type, a smartphone) UE usage type), service type, slice type, access network, tenant, whether to support roaming users, slice instance location (for example, location of a specific network element in a slice instance), slice instance available capacity (for example, simultaneously accommodate users) , Slice Service Level Agreement (SLA) parameters (for example, parameters such as bandwidth and delay), and slice instance status.

In the embodiment of the present invention, the UE includes an intelligent terminal (such as a mobile phone), a multimedia device, a streaming media device, and the like. The RAN is a part of the mobile communication system, establishes a wireless connection with the UE, and realizes interworking between the user equipment and the core network. The RAN includes a number of base stations and other network entities for supporting a number of UEs for communication. The base station may be an evolved NodeB (eNB) in Long Term Evolution (LTE). A base station 110 may support/manage one or more cells, and when the UE needs to communicate with the network, it will select a cell to initiate access. Corresponding to different communication systems, the specific equipment of the base station is also different, and specifically may be a base station controller (BSC), a radio network controller (RNC), an evolved base station (eNB), or a base station. (Node B). A network slice instance (NetworkSlice Instance) flexibly provides one or more network services according to the needs of the slice demand side.

In addition, each network slice in Figure 1 can be divided into a control plane network function and a user plane network function.

FIG. 2 is a schematic diagram of communication of a method for acquiring network slice instance information according to an embodiment of the present invention. The method may be based on the deployment scenario shown in FIG. 1 , where the method includes:

Step 201: The network slice selection function entity sends a request message to the network slice instance information management entity, where the request message is used to query information of the network slice instance.

The request message may carry at least one of the following types: usage type of the UE supported by the slice, UE capability information, service type of the slice support, slice type, tenant identity, and network slice instance identifier.

The UE capability may specifically include a radio access related capability of the UE and a core network related capability. For example, does the UE support the circuit-based fallback (CSFB) to initiate joint attach, and whether to support the mobility of the radio access technology (RAT).

The relationship between a tenant and a network slicing instance can be understood as a network slicing instance that may serve a UE of a tenant.

Step 202: The network slice instance information management entity queries the information of the network slice instance according to the request message.

Specifically, the network shard instance information management entity may obtain, according to the information carried in the request message, information that satisfies the network slice instance that matches the information carried by the request message.

The information of the network slice instance may include the network slice instance identifier and at least one of the following information: the type of use of the slice supported UE, the service type of the slice support, the slice type, the access point name, the tenant identity, whether the roaming user is supported, the slice instance Location, slice instance available capacity, slice SLA parameters, slice instance status.

When the request message carries the network slice instance identifier, the network slice instance information management entity may obtain the information of the matched network slice instance according to the network slice instance identifier. The first request message may also carry some other information, such as a slice type. In this case, the network slice instance information management entity may obtain information about multiple network slice instances that match the information, and the information of each network slice instance includes The ID of the network slice instance.

Step 203: The network slice instance information management entity sends information of at least one network slice instance to the network slice selection function entity.

Wherein, before or after step 201, the network slice instance information management entity receives the request message from the network slice management system, and updates the information of the network slice instance according to the request message.

In one example, prior to step 201, the network slice selection function entity receives a request message from the UE, and triggers execution of step 201 by the request message. The request message is a session establishment request message or an attach request message or a location update request message, and the location update request message may be a Tracking Area Update (TAU) request message.

In an example, after step 203, the method further includes:

Step 204: The network slice selection function entity performs network slice selection according to the information of the at least one network slice instance.

Specifically, if the network slice instance information management entity selects work from the network slice in step 203 The energy entity can only send information of one network slice instance, and the network slice selection function entity selects the network slice instance to provide services for the UE. If the network slice instance information management entity sends multiple network slice instances to the network slice selection function entity in step 203 The information, the network slice selection function entity selects a network slice instance to provide a service for the UE, and the specific selection principle may be selected according to the principles of load balancing, geographical location, and the like, which are not limited in the embodiment of the present invention.

In one example, the method further includes:

Step 205: The network slice selection function entity sends a request message to the network slice instance information management entity, where the request message is used to subscribe to the change information of the network slice instance information.

The request message may include at least one of the following: a usage type of the UE supported by the slice, a UE capability, a service type supported by the slice, a slice type, a tenant identity, and a network slice instance identifier.

In the embodiment of the present invention, the sequence of the execution of the step 205 and the step 201 to the step 204 is not specifically limited. The step 201 to the step 204 may be performed before the step 205 is performed, or the step 205 may be performed first, and then the step 201 to the step 204 are performed. Step 205 may also be performed between step 201 and step 204.

When the step 201 is performed to perform the step 205, the network slice selection function entity may first obtain the information of the at least one network slice instance from the network slice instance information management entity according to the step 201 to the step 204, and then manage the network slice instance information. The entity sends a subscription slice instance message, and the subscription slice instance message carries a specific network slice instance identifier.

When step 205 is performed to perform step 201 to step 204 or step 205 is performed between step 201 and step 204, the subscribed slice instance message in step 205 may not carry a specific network slice instance identifier, and carries other information, such as slice support. Type of use of the UE, UE capability, service type supported by the slice, slice type, and the like.

Step 206: The network slice selection function entity receives a notification message from the network slice instance information management entity, where the notification message carries change information of the network slice instance information.

In an example, the network slice instance information management entity first receives the network slice instance information change notification message from the network slice management system according to the subscription slice instance message, and then the network slice instance information management entity sends the network slice instance information to the network slice selection function entity. Change notification message.

In one example, the method further includes:

Step 207: The network slice selection function entity performs network slice selection or reselection according to the change information of the network slice instance information.

In an example, before the step 205, the method further includes: Step 2051, the network slice selection function entity receives a notification message from the network slice instance information management entity, where the notification message is used to indicate the online network slice instance and the network slice instance information. . The notification message may carry one or more of the following: a network slice instance identifier, a tenant ID, and information of other network slice instances. The information of the network slice instance may include the network slice instance identifier and at least one of the following: the type of use of the slice supported UE, the service type of the slice support, the slice type, the access point name, the tenant identity, whether the roaming user is supported, the slice instance location , slice instance available capacity, slice SLA parameters, slice instance status.

For example, in step 205, the network slice selection function entity sends a request message to the network slice instance information management entity according to the notification message, and the request message is used to subscribe to the online slice instance related information change notification message.

In one example, step 2051 receives a slice online notification message from the network slice management system for the network slice instance information management entity; the network slice instance information management entity sends a slice online notification message to the network slice selection function.

In another example, in step 205, the network slice selection function entity may send a subscription slice instance message to the network slice instance information management entity without receiving the slice online notification message, and the subscription slice instance message is used to subscribe to a certain type of slice. Instance information. In the embodiment of the present invention, steps 205, 206 and step 2051 may independently constitute a solution, and the descriptions of steps 401 to 404 in FIG. 4 are described in detail.

FIG. 3 is a schematic diagram of communication of another method for obtaining network slice instance information according to an embodiment of the present invention. This embodiment describes a network slice instance information query process. When an NSSF entity receives a request from a UE, it actively slices to the network. The instance information management entity sends a slice information query request, and the method includes:

Step 301, the network slice management system instantiates one or more slices, and instantiates one or more NSSF entities.

The NSSF entity may be a slice internal functional entity or a functional entity independent of the slice.

When the NSSF entity is a slice internal functional entity, the specific NSSF entity may be deployed in the RAN or shared control plane network function. For example, it is deployed in an access and mobility management function (AMF) device as a logical function of the AMF device. When the NSSF entity is a functional entity independent of the slice, there may be only one NSSF entity in the network. Take the information of each slice instance in the network and perform the slice selection function.

Step 302: When the network slice instance information changes, the network slice management system updates the slice instance information in the network slice instance information management entity.

The change of the network slice instance information may be, but is not limited to, the following situation: for example, the network slice management system instantiates a new network slice instance, or performs other lifecycle management operations on a network slice instance or network function therein (such as expansion) Shrinkage, software upgrades, etc.).

Step 303: The NSSF entity receives the request message sent by the UE. The request message can be used to trigger the NSSF entity to perform network slice selection. For example, the request message is a session establishment request message.

Step 304: The NSSF entity sends a network slice information query request message to the network slice instance information management entity.

The network slice information query request message may carry one or more of the following: a UE usage type supported by the slice, a UE capability, a service type supported by the slice, a slice type, a tenant identifier, and a network slice instance identifier.

Step 305: The network slice instance information management entity returns information of one or more network slice instances corresponding to the information carried in the query request message to the NSSF entity.

Step 306: The NSSF entity performs network slice selection according to the information of the network slice instance and the network slice selection policy.

The embodiment of the present invention provides that when the NSSF entity receives the request of the UE and triggers the execution of the slice selection in the network slice deployment scenario, the NSSF entity first queries the slice instance information database for the network slice instance information, and then performs the network slice selection according to the policy. Thereby enhancing the isolation between the internal functions of the network slice and the external system.

FIG. 4 is a schematic diagram of communication of a method for acquiring network slice instance information according to an embodiment of the present invention. This embodiment describes a network slice instance information subscription and notification method, and the NSSF entity subscribes to the network slice instance information management entity. The slice instance information, the network slice instance information management entity pushes the information of the network slice instance according to the network slice instance range subscribed by the NSSF entity, and the method includes:

Step 401: The NSSF entity subscribes to the slice instance message to the network slice instance information management entity.

The subscription slice instance message may carry one or more of the following: the UE usage type supported by the network slice, the UE capability, the service type supported by the network slice, the slice type, the tenant identity, and the network slice instance identifier.

Step 402: The information carried by the network slice instance information management entity according to the subscription slice instance message Determine the corresponding one or more network slice instance IDs.

In one example, the network slice instance information management entity looks up one or more network slice instance identifiers that it stores that match the information carried by the subscription message.

Step 403: The network slice instance information management entity acquires a network slice instance information change notification message from the network slice management system.

For example, the network slice instance information change may include a network slice instance information change caused by the network slice instance management system performing a lifecycle management operation on the network slice instance, or a network slice caused by the network slice instance management system performing a modification configuration on the network slice. The instance information changes.

Step 404: The network slice instance information management entity sends a corresponding network slice instance information change notification message to the corresponding NSSF entity according to the network slice instance identifier determined in step 402.

For example, when a network slice instance is ready to go offline, the network slice management system sends a network slice instance offline pre-notification to the network slice instance information management entity, and the network slice instance information management entity forwards the notification to the corresponding NSSF entity, and the NSSF entity no longer Assign a new service to the network slice instance.

The embodiment of the present invention provides a method for the NSSF entity to subscribe to and obtain the network slice instance information from the network slice instance information management entity, so that the network slice information management entity network slice instance information management entity can provide corresponding according to the requirements of the NSSF entity. The information of the network splicing instance avoids pushing network fragmentation instance information of the entire network to all NSSF entities.

At the same time, when the network is deployed, the network slice management system belongs to the network management system. The NSSF entity belongs to the network element function of the service layer or the internal logic function of the network element function entity. The direct interaction between the two belongs to the cross-subsystem interaction. Improvement, interaction time is also not guaranteed. The network slice information management entity obtains the information of the network slice instance from the network slice management information system in advance, and provides the information to the corresponding NSSF entity, thereby avoiding interaction between the internal functions of the network slice and the external system, and ensuring the isolation of the slice.

FIG. 5 is a schematic diagram of communication of a method for obtaining network slice instance information according to an embodiment of the present invention. This embodiment describes a new network slice instance online notification method. When a new slice instance is online, the network slice management system sends a slice online notification to the network slice instance information management entity. The method includes:

Step 501: The network slice management system sends a slice online notification message to the network slice instance information management entity, where the slice online notification message includes information of the network slice instance.

The information of the network slice instance may include a network slice instance identifier and at least one of the following information: The type of usage of the UE supported by the slice, the service type supported by the slice, the slice type, the access point name, the tenant identity, whether the roaming user is supported, the slice instance location, the slice instance available capacity, the slice SLA parameter, and the slice instance state.

Step 501 is to implement a network slice management system to synchronously update the network slice instance information management entity.

Step 502: The network slice instance information management entity pushes a slice online notification message to the NSSF entity in the network.

The network slice instance online notification message includes a network slice instance identifier and a tenant identification, and/or other network slice instance information.

Step 503: Each NSSF entity determines, according to the newly-online network slice instance information, whether the network slice instance information management entity needs to subscribe to the network slice instance information to receive the network slice instance-related change notification. When the NSSF entity determines that the network slice instance information needs to be subscribed to the network slice instance information management entity, the NSSF entity sends a subscription slice instance message to the network slice instance information management entity. The identifier of the network slice instance is included in the subscription slice instance message.

In an example, the NSSF entity can determine whether it needs to subscribe to the network slice instance information according to its association with the network slice instance, such as whether the network slice instance is within the service scope of the NSSF entity, or the tenant identifier corresponding to the network slice instance. Whether the (tenant ID) matches the tenant ID supported by the NSSF entity.

The embodiment of the present invention provides a method for online notification of a network splicing instance, which is convenient for updating a newly-online network snippet instance in the network to a network shard instance information management entity, and further notifying the NSSF entity, so that the NSSF entity subsequently performs network segmentation. When selected, you can select a new online network slice instance based on the policy.

The foregoing describes the solution of the embodiment of the present invention mainly from the perspective of interaction between the network elements. It can be understood that each network element, such as a network slice selection function entity, a network slice instance information management entity, a network slice management system, etc., in order to implement the above functions, includes hardware structures and/or software modules corresponding to each function. Those skilled in the art will readily appreciate that the present invention can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.

The embodiment of the present invention may select a function entity and a network cut for a network slice according to the foregoing method example. The slice instance information management entity, the network slice management system, and the like divide the function modules. For example, each function module may be divided according to each function, or two or more functions may be integrated into one processing module. The above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of the module in the embodiment of the present invention is schematic, and is only a logical function division, and the actual implementation may have another division manner.

In the case of employing an integrated module, FIG. 6 shows a possible structural diagram of the network slice selection function entity involved in the above embodiment. The network slice selection function entity 600 includes a processing module 602 and a communication module 603. The processing module 602 is configured to control and manage the action of the network slice selection function entity. For example, the processing module 602 is configured to support the network slice selection function entity to perform the processes 201, 204, 205, and 207 in FIG. 2, and the process 304 in FIG. And 306, process 401 in FIG. 4, process 503 in FIG. 5, and/or other processes for the techniques described herein. The communication module 603 is configured to support communication between the network slice selection function entity and other network entities, such as communication with the network slice instance information management entity. For example, the communication module 603 is configured to support the network slice selection function entity to perform the processes 201 and 205 of FIG. 2, the process 304 of FIG. 3, the process 401 of FIG. 4, the process 503 of FIG. 5, and/or for the purposes of this document. Other processes of the described techniques. The network slice selection function entity may further include a storage module 601 for storing program codes and data of the network slice selection function entity.

The processing module 602 can be a processor or a controller, for example, a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), and an application-specific integrated circuit (Application-Specific). Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA) or other programmable logic device, transistor logic device, hardware component, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure. The processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like. The communication module 603 can be a communication interface, a transceiver, a transceiver circuit, etc., wherein the communication interface is a collective name and can include one or more interfaces. The storage module 601 can be a memory.

When the processing module 602 is a processor, the communication module 603 is a communication interface, and the storage module 601 is a memory, the network slice selection function entity involved in the embodiment of the present invention may be a network slice selection function entity as shown in FIG. 7.

Referring to FIG. 7, the network slice selection function entity 700 includes: a processor 702, a communication interface Port 703, memory 701. Optionally, the network slice selection function entity 700 may further include a bus 704. The communication interface 703, the processor 702, and the memory 701 may be connected to each other through a bus 704. The bus 704 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (abbreviated). EISA) bus and so on. The bus 704 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 7, but it does not mean that there is only one bus or one type of bus.

In the case of adopting an integrated module, FIG. 8 shows a possible structural diagram of the network slice instance information management entity involved in the above embodiment. The network slice instance information management entity 800 includes a processing module 802 and a communication module 803. The processing module 802 is configured to control and manage the actions of the network slice instance information management entity. For example, the processing module 802 is configured to support the network slice instance information management entity to perform the processes 202, 203, 2051, and 206 in FIG. 2, in FIG. Process 305, processes 402 and 404 in FIG. 4, process 502 in FIG. 5, and/or other processes for the techniques described herein. The communication module 803 is configured to support communication between the network slice instance information management entity and other network entities, such as communication with a network slice selection function entity. For example, the communication module 803 is configured to support the network slice instance information management entity to perform the processes 203, 2051, and 206 in FIG. 2, the process 305 in FIG. 3, the process 404 in FIG. 4, the process 502 in FIG. 5, and/or Other processes for the techniques described herein. The network slice instance information management entity may further include a storage module 801 for storing program codes and data of the network slice instance information management entity.

The processing module 802 can be a processor or a controller, and can be, for example, a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), and an application-specific integrated circuit (Application-Specific). Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA) or other programmable logic device, transistor logic device, hardware component, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure. The processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like. The communication module 803 can be a communication interface, a transceiver, a transceiver circuit, etc., wherein the communication interface is a collective name and can include one or more interfaces. The storage module 801 can be a memory.

When the processing module 802 is a processor, the communication module 803 is a communication interface, and the storage module 801 is a memory, the network slice instance information management entity involved in the embodiment of the present invention may be as shown in FIG. The network slice instance information management entity shown.

Referring to FIG. 9, the network slice instance information management entity 900 includes a processor 902, a communication interface 903, and a memory 901. Optionally, the network slice instance information management entity 900 may further include a bus 904. The communication interface 903, the processor 902, and the memory 901 may be connected to each other through a bus 904. The bus 904 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (abbreviated). EISA) bus and so on. The bus 904 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 9, but it does not mean that there is only one bus or one type of bus.

In the case of using an integrated module, FIG. 10 shows a possible structural diagram of the network slice management system involved in the above embodiment. The network slice management system 1000 includes a processing module 1002 and a communication module 1003. The processing module 1002 is configured to control and manage the actions of the network slice management system. For example, the processing module 1002 is configured to support the network slice management system to perform the processes 301 and 302 in FIG. 3, the process 403 in FIG. 4, and the process in FIG. 501, and/or other processes for the techniques described herein. The communication module 1003 is configured to support communication between the network slice management system and other network entities, such as communication with the network slice instance information management entity. For example, the communication module 1003 is configured to support the network slice management system to perform the processes 301 and 302 of FIG. 3, the process 403 of FIG. 4, the process 501 of FIG. 5, and/or other processes for the techniques described herein. The network slice management system may further include a storage module 1001 for storing program codes and data of the network slice management system.

The processing module 1002 may be a processor or a controller, such as a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), and an application-specific integrated circuit (Application-Specific). Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA) or other programmable logic device, transistor logic device, hardware component, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure. The processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like. The communication module 1003 may be a communication interface, a transceiver, a transceiver circuit, etc., wherein the communication interface is a collective name and may include one or more interfaces. The storage module 1001 may be a memory.

When the processing module 1002 is a processor, the communication module 1003 is a communication interface, and the storage module 1001 When it is a memory, the network slice management system according to the embodiment of the present invention may be the network slice management system shown in FIG.

Referring to FIG. 11, the network slice management system 1100 includes a processor 1102, a communication interface 1103, and a memory 1101. Optionally, the network slice management system 1100 may further include a bus 1104. The communication interface 1103, the processor 1102, and the memory 1101 may be connected to each other through a bus 1104. The bus 1104 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (abbreviated). EISA) bus and so on. The bus 1104 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 11, but it does not mean that there is only one bus or one type of bus.

The steps of a method or algorithm described in connection with the present disclosure may be implemented in a hardware, or may be implemented by a processor executing software instructions. The software instructions may be composed of corresponding software modules, which may be stored in a random access memory (RAM), a flash memory, a read only memory (ROM), an erasable programmable read only memory ( Erasable Programmable ROM (EPROM), electrically erasable programmable read only memory (EEPROM), registers, hard disk, removable hard disk, compact disk read only (CD-ROM) or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor to enable the processor to read information from, and write information to, the storage medium. Of course, the storage medium can also be an integral part of the processor. The processor and the storage medium can be located in an ASIC. Additionally, the ASIC can be located in a core network interface device. Of course, the processor and the storage medium may also exist as discrete components in the core network interface device.

Those skilled in the art will appreciate that in one or more examples described above, the functions described herein can be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, the functions may be stored in a computer readable medium or transmitted as one or more instructions or code on a computer readable medium. Computer readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another. A storage medium may be any available media that can be accessed by a general purpose or special purpose computer.

The specific embodiments of the present invention have been described in detail with reference to the preferred embodiments of the present invention. The scope of the protection, any modifications, equivalent substitutions, improvements, etc., which are made on the basis of the technical solutions of the present invention, are included in the scope of the present invention.

Claims

A method for obtaining network slice instance information, where the method includes:

The network slice selection function entity sends a first request message to the network slice instance information management entity, where the first request message is used to query information of the network slice instance;

The network slice selection function entity receives information of at least one network slice instance from the network slice instance information management entity.
The method of claim 1, wherein before the sending, by the network slice selection function entity, the first request message to the network slice instance information management entity, the method further comprises:

The network slice selection function entity receives a second request message from the user equipment UE, where the second request message is used to trigger the network slice selection function entity to send the first request message to the network slice instance information management entity, The second request message is a session establishment request message or an attach request message or a location update request message.
The method according to claim 1 or 2, wherein after the network slice selection function entity receives the information of the at least one network slice instance from the network slice instance information management entity, the method further includes:

The network slice selection function entity performs network slice selection according to information of the at least one network slice instance.
The method of any of claims 1 to 3, further comprising:

The network slice selection function entity sends a third request message to the network slice instance information management entity, where the third request message is used to subscribe to change information of the network slice instance information;

The network slice selection function entity receives a first notification message from the network slice instance information management entity, where the first notification message carries change information of network slice instance information;

The network slice selection function entity performs network slice selection or reselection according to the change information of the network slice instance information.
The method of claim 4, wherein before the sending, by the network slice selection function entity, the third request message to the network slice instance information management entity, the method further comprises:

The network slice selection function entity receives a second notification message from the network slice instance information management entity, where the second notification message is used to indicate information of the online network slice instance and the network slice instance.
The method according to claim 4 or 5, wherein the third request message comprises at least one of the following: a usage type of the user equipment UE supported by the subscribed network slice instance, and a UE supported by the subscribed network slice instance. The capability, the type of service supported by the subscribed network slice instance, the type of the subscribed network slice instance, the tenant ID of the subscribed network slice instance, and the identity of the subscribed network slice instance.
The method according to any one of claims 1 to 6, wherein the first request message carries at least one of the following information: a type of use of the user equipment UE supported by the network slice instance of the query, and a network slice of the query The UE capability supported by the instance, the service type supported by the queried network slice instance, the type of the network slice instance that is queried, the tenant ID of the queried network slice instance, and the identifier of the queried network slice instance.
The method according to any one of claims 1 to 7, wherein the information of the network slice instance comprises an identifier of a network slice instance and at least one of the following: a user equipment UE supported by the network slice instance a usage type, a UE capability supported by the network slice instance, a service type supported by the network slice instance, a type of the network slice instance, an access point name of the network slice instance, a tenant identity of the network slice instance Whether the network slice instance supports a roaming user, a location of the network slice instance, an available capacity of the network slice instance, a service level agreement SLA parameter of the network slice instance, and a state of the network slice instance.
A method for obtaining network slice instance information, where the method includes:

The network slice instance information management entity receives the first request message from the network slice selection function entity;

The network slice instance information management entity queries information of the network slice instance according to the first request message;

The network slice instance information management entity sends information of at least one network slice instance to the network slice selection function entity.
The method according to claim 9, wherein before the network slice instance information management entity receives the first request message from the network slice selection function entity, the method further includes:

The network slice instance information management entity receives a second request message from the network slice management system, and updates information of the network slice instance according to the second request message.
The method of claim 9 or 10, wherein the method further comprises:

The network slice instance information management entity receives a third request message from the network slice selection function entity, where the third request message is used to subscribe to change information of the network slice instance information;

The network slice instance information management entity sends a first notification message to the network slice selection function entity according to the third request message, where the first notification message carries change information of network slice instance information, where the network slice The instance information management entity receives the change information of the network slice instance information from the network slice management system before sending the first notification message to the network slice selection function entity according to the third request message.
The method according to claim 11, wherein before the network slice instance information management entity receives the third request message from the network slice selection function entity, the method further includes:

The network slice instance information management entity receives a second notification message from the network slice management system, where the second notification message is used to indicate information of the online network slice instance and the network slice instance;

The network slice instance information management entity sends the second notification message to the network slice selection function entity.
A network slice selection function entity, wherein the network slice selection function entity comprises: a processing module and a communication module;

The processing module is configured to send, by using the communication module, a first request message to a network slice instance information management entity, where the first request message is used to query information of a network slice instance, and from the network by using the communication module The slice instance information management entity receives information of at least one network slice instance.
The network slice selection function entity according to claim 13, wherein the processing module is further configured to pass the communication module before sending the first request message to the network slice instance information management entity by using the communication module. Receiving, by the user equipment UE, a second request message, where the second request message is used to trigger sending, by the communication module, the first request message to the network slice instance information management entity, where the second request message is A session establishment request message or an attach request message or a location update request message.
The network slice selection function entity according to claim 13 or 14, wherein the processing module is further configured to receive, by the communication module, information of at least one network slice instance from the network slice instance information management entity. Thereafter, network slice selection is performed based on the information of the at least one network slice instance.
A network slice selection function entity according to any one of claims 13 to 15, The processing module is further configured to send, by using the communication module, a third request message to the network slice instance information management entity, where the third request message is used to subscribe to change information of network slice instance information; The communication module receives a first notification message from the network slice instance information management entity, where the first notification message carries change information of network slice instance information; and performs network slice selection according to change information of the network slice instance information or Re-election.
The network slice selection function entity according to claim 16, wherein the processing module is further configured to: before sending the third request message to the network slice instance information management entity by using the communication module, The communication module receives a second notification message from the network slice instance information management entity, where the second notification message is used to indicate information of the online network slice instance and the network slice instance.
The network slice selection function entity according to claim 16 or 17, wherein the third request message comprises at least one of the following: a usage type of the user equipment UE supported by the subscribed network slice instance, and a subscribed network slice. The UE capabilities supported by the instance, the type of service supported by the subscribed network slice instance, the type of the subscribed network slice instance, the tenant identity of the subscribed network slice instance, and the identity of the subscribed network slice instance.
The network slice selection function entity according to any one of claims 13 to 18, wherein the first request message carries at least one of the following types: a usage type of the user equipment UE supported by the queried network slice instance, The UE capability supported by the queried network snippet instance, the service type supported by the queried network snippet instance, the type of the network snippet instance that is queried, the tenant ID of the queried network snippet instance, and the identifier of the queried network snippet instance.
The network slice selection function entity according to any one of claims 13 to 19, wherein the information of the network slice instance includes an identifier of a network slice instance and at least one of the following information: supported by the network slice instance a usage type of the user equipment UE, a UE capability supported by the network slice instance, a service type supported by the network slice instance, a type of the network slice instance, an access point name of the network slice instance, and the network slice a tenant identifier of the instance, whether the network slice instance supports a roaming user, a location of the network slice instance, an available capacity of the network slice instance, a service level agreement SLA parameter of the network slice instance, and a network slice instance status.
A network slice instance information management entity, where the network slice instance information management entity includes: a processing module and a communication module;

The processing module is configured to receive, by the communication module, a first request message from a network slice selection function entity; and query information of a network slice instance according to the first request message; and slice the network by using the communication module Select the functional entity to send information about at least one network slice instance.
The network slice instance information management entity according to claim 21, wherein the processing module is further configured to pass the communication module before receiving the first request message from the network slice selection function entity by using the communication module. Receiving a second request message from the network slice management system, and updating information of the network slice instance according to the second request message.
The network slice instance information management entity according to claim 21 or 22, wherein the processing module is further configured to receive, by the communication module, a third request message from the network slice selection function entity, where the And the third request message is used to subscribe to the change information of the network slice instance information; and send, by using the communication module, the first notification message to the network slice selection function entity according to the third request message, where the first notification message carries a network slice Change information of the instance information, wherein the network slice instance information management entity sends the first notification message to the network slice selection function entity according to the third request message, and the network slice management system is used by the communication module Receiving change information of the network slice instance information.
The network slice instance information management entity according to claim 23, wherein the processing module is further configured to: before receiving the third request message from the network slice selection function entity by using the communication module, The communication module receives a second notification message from the network slice management system, where the second notification message is used to indicate information of an online network slice instance and the network slice instance; and to the network by using the communication module The slice selection function entity sends the second notification message.
A communication system, characterized in that the system comprises: the network slice selection function entity according to any one of claims 13 to 20, the network slice instance information management entity according to any one of claims 21 to .
The communication system of claim 25, wherein the system further comprises: a network slice management system;

The network slice management system is configured to send a first notification message to the network slice instance information management entity, where the first notification message carries change information of network slice instance information; and/or, Sending a second notification message to the network slice instance information management entity, where the second notification message is used to indicate information of the online network slice instance and the network slice instance.