CN113784419B

CN113784419B - Information sending method, unit and system

Info

Publication number: CN113784419B
Application number: CN202111101844.1A
Authority: CN
Inventors: 许瑞岳; 季莉; 邹兰; 张凯
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2016-11-03
Filing date: 2017-01-04
Publication date: 2023-03-10
Anticipated expiration: 2037-01-04
Also published as: WO2018082574A1; CN113784419A

Abstract

The embodiment of the invention provides an information sending method, and a unit and a system based on the method. The method comprises the following steps: the first unit creates or updates a network slice instance; the first unit sends a first message to the second unit, wherein the first message carries first network slice instance information, the first network slice instance information is first information of a created or updated network slice instance, and the first network slice instance information comprises an identifier of the network slice instance; the second unit saves or configures the first network slice instance information. In the scheme of the embodiment of the invention, after the first unit creates or updates the network slice instance, the first unit can send the information of the created or updated network slice instance to the second unit, and the second unit can store or configure the information of the network slice instance, so that the situation that an unsuitable network slice instance is allocated to the terminal can be avoided.

Description

Information sending method, unit and system

Technical Field

The present invention relates to the field of communications technologies, and in particular, to an information sending method, unit, and system.

Background

The concept of network slicing is introduced when studying future mobile communication systems. A network slice may be understood as an on-demand network. A physical network may be logically divided into multiple network slices, and different network slices may be used to carry different traffic. For example, electric power companies need to provide services for smart meters, which can be implemented by connecting network slices of a series of Machine-to-Machine (M2M) devices. In actual operation, the deployment of the network slice may be accomplished through a network slice instance.

After the terminal accesses the network, the network side device needs to allocate a network slice instance to the terminal based on some manually input network information to provide services for the terminal. For example, the network information includes virtual machine information and the like. However, since the network slice instances may be dynamically added, modified and deleted, the terminal often cannot be allocated a suitable network slice instance based on the above network information.

Disclosure of Invention

The embodiment of the invention describes an information sending method, unit and system, aiming to avoid allocating an improper network slice example to a terminal.

In one aspect, an embodiment of the present invention provides an information sending method, where the method includes: the first unit creates or updates a network slice; the first unit sends a first message to the second unit, wherein the first message carries first network slice instance information, the first network slice instance information is first information of a created or updated network slice instance, and the first network slice instance information comprises an identifier of the network slice instance; the second unit saves or configures the first network slice instance information.

In the scheme of the embodiment of the invention, after the first unit creates or updates the network slice instance, the first unit can send the information of the created or updated network slice instance to the second unit, and the second unit can store or configure the information of the network slice instance, so that the situation that an unsuitable network slice instance is allocated to the terminal can be avoided.

Wherein, creating the network slice instance may be understood as adding or instantiating the network slice instance.

In one possible design, the first message may be an addition notification message of a network slice instance, a configuration message of a network slice instance, an update notification message of a network slice instance, or a reconfiguration message of a network slice instance. For example, in the case where the first unit creates a network slice instance, the first message may be an addition notification message of the network slice instance or a configuration message of the network slice instance; for another example, in case the first unit updates the network slice instance, the first message may be an update notification message of the network slice instance or a reconfiguration message of the network slice instance.

In one possible implementation, the first network slice instance information may further include at least one of: the method comprises the steps of obtaining the state of a network slice instance, the information of the network function instance required by the network slice instance, the information of a tenant supported by the network slice instance or the information of a service provided by the network slice instance, wherein the information of the network function instance comprises the identification of the network function instance and the state of the network function instance. For example, when the first message is an addition notification message of a network slice instance or a configuration message of a network slice instance, the first network slice instance information may be as described above.

In another possible implementation, the first network slice instance information may further include at least one of: the method comprises the steps of updating the state of a network slice instance, the information of the network function instance required by the network slice instance after updating, the information of a tenant supported by the network slice instance after updating, or the information of a service provided by the network slice instance after updating, wherein the information of the network function instance comprises the identification of the network function instance and the state of the network function. For example, when the first message is an update notification message of a network slice instance or a reconfiguration message of a network slice instance, the first network slice instance information may be as described above.

In both possible implementations, the tenant's information and/or the service's information may be used to allocate a target network slice instance for the terminal that satisfies the service request. The tenant information may refer to tenant information supported by the network slice instance, or may refer to tenant information supported by the updated network slice instance; the service information herein may refer to information of a service provided by the network slice instance, or may refer to information of a service provided after the network slice instance is updated.

In one possible design, the first unit may further send a second message to the third unit, where the second message carries second network slice instance information, the second network slice instance information is second information of the created or updated network slice instance, and the second network slice instance information includes an identifier of the network slice instance. Correspondingly, the third unit may save the second network slice instance information.

The second message may be an addition notification message of a network slice instance, a configuration message of the network slice instance, an update notification message of the network slice instance, or a reconfiguration message of the network slice instance. For example, in the case where the first unit creates a network slice instance, the second message may be an addition notification message of the network slice instance or a configuration message of the network slice instance; for another example, in case the first unit updates the network slice instance, the second message may be an update notification message of the network slice instance or a reconfiguration message of the network slice instance.

In one possible implementation, the second network slice instance information may further include a status of the network slice instance and/or information of the network function instance required by the network slice instance, wherein the information of the network function instance may include at least one of: an identification of a network function instance, a status of a network function instance, or a type of network function instance. For example, when the second message is an addition notification message of a network slice instance or a configuration message of a network slice instance, the second network slice instance information may be as described above.

In another possible implementation, the second network slice instance information may further include an updated status of the network slice instance and/or information of a network function instance required after the network slice instance is updated, wherein the information of the network function instance may include at least one of: an identification of an updated network function instance, a status of an updated network function instance, an identification of an newly added network function instance, or an identification of a deleted network function instance. For example, when the second message is an update notification message of a network slice instance or a reconfiguration message of a network slice instance, the second network slice instance information may be as described above.

In one possible design, before the first unit sends the first message to the second unit, the second unit may further send a subscription request to the first unit, where the subscription request is used to subscribe to the first network slice instance information; alternatively, the second unit may further send a query request to the first unit, where the query request is used to query the first network slice instance information.

In one possible design, the second unit may further receive a service request from the terminal, and allocate a target network slice instance satisfying the service request to the terminal according to the first network slice instance information. For example, the first network slice instance information includes information of the tenant and/or information of the service, and the second unit may allocate the target network slice instance to the terminal according to the information of the tenant and/or the information of the service.

In one possible design, the second unit may further send a selection request to the third unit, the selection request requesting a network function instance required to satisfy the target network slice instance of the service request of the terminal. The selection request may carry information of the terminal and an identifier of the network slice instance. In this case, the third unit may select a network function instance required for the target network slice instance according to the above-mentioned second network slice instance information.

In one possible design, the first unit may further send a first deletion notification to the second unit, the first deletion notification being used to notify the second unit to delete the first network slice instance information. Wherein the first deletion notification may carry an identifier of the network slice instance.

In one possible design, the first unit may further send a second deletion notification to the third unit, the second deletion notification being used to notify the third unit to delete the second network slice instance information. Wherein the second deletion notification may carry an identification of the network slice instance.

In the scheme of the present aspect, the first unit may be nsam, or NSO, NSM, NO, NM, or NFVO; the second unit can be NSSF, also can be NF-M/Data Center; the third unit can be Common NF/NF repetition or NF-M/Data Center.

In another aspect, an embodiment of the present invention provides an information sending method, where the method includes: the first unit creates or updates a network slice instance; the first unit sends a message to the fourth unit, wherein the message carries third network slice instance information, the third network slice instance information is third information of a created or updated network slice instance, and the third network slice instance information comprises an identifier of the network slice instance; the third unit stores or configures third network slice instance information.

The fourth unit may be a combination unit of the second unit and the third unit described in the above aspect. The fourth unit may perform the actions of the second unit and the third unit involved in the scheme of the above aspect. In this case, the fourth unit does not perform the above-mentioned interaction between the second unit and the third unit; or, the second unit and the third unit may be set as internal modules of the fourth unit, and the interaction between the second unit and the third unit is interaction between different internal modules in the fourth unit.

In some possible designs, the first unit may complete a behavior of the first unit related to each method design in the scheme of the previous aspect, and the fourth unit may complete a behavior of the second unit and a behavior of the third unit related to each method design in the scheme of the previous aspect, which is not described herein again.

The third network slice instance information may further include part or all of the content of the first network slice instance information and/or the second network slice instance information related in the above aspect.

In one possible design, the first unit may further send a deletion notification to the fourth unit, the deletion notification being used to notify the fourth unit to delete the third network slice instance information. Wherein the deletion notification may carry an identification of the network slice instance.

In the scheme of the present aspect, the first unit may be nsam, or NSO, NSM, NO, NM, or NFVO; the fourth unit can be Common NF/NSC, but also NF-M/Data Center.

The Network slice example related to the above two aspects may include at least a Core Network (CN) portion, a Radio Access Network (RAN) portion, and a Transport Network (TN) portion; alternatively, the network slice example involved in the above two aspects may include any two of the CN part, the RAN part, or the TN part; alternatively, the network slice instance involved in the above two aspects may represent a network slice instance of the CN part, a network slice instance of the RAN part, or a network slice instance of the TN part.

In another aspect, the embodiment of the present invention provides a first unit, which has a function of implementing the behavior of the first unit in the above method design. The functions can be realized by hardware, and the functions can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the above-described functions.

In one possible design, the first unit includes a processor configured to support the first unit to perform the corresponding functions of the above method. Further, the first unit may further comprise a communication interface for supporting communication between the first unit and the second unit, the third unit, the fourth unit or other units. Further, the first unit may further comprise a memory for coupling with the processor, which holds the necessary program instructions and data of the first unit.

In another aspect, the embodiment of the present invention provides a second unit, which has a function of implementing the behavior of the second unit in the above method design. The functions can be realized by hardware, and the functions can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the above-described functions.

In one possible design, the second unit includes a processor configured to support the second unit to perform the corresponding functions in the above method. Further, the second unit may further comprise a communication interface for supporting communication between the second unit and the first unit, the third unit or other units. Further, the second unit may further comprise a memory for coupling with the processor, which holds the necessary program instructions and data of the second unit.

In another aspect, the embodiment of the present invention provides a third unit, where the third unit has a function of implementing the behavior of the third unit in the above method design. The functions can be realized by hardware, and the functions can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the above-described functions.

In one possible design, the third unit includes a processor configured to support the third unit to perform the corresponding functions in the above method. Further, the third unit may further comprise a communication interface for supporting communication between the third unit and the first unit, the second unit or other units. Further, the third unit may further comprise a memory for coupling with the processor, which holds program instructions and data necessary for the third unit.

In another aspect, the embodiment of the present invention provides a fourth unit, where the fourth unit has a function of implementing the fourth unit behavior in the above method design. The functions can be realized by hardware, and the functions can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

In one possible design, the fourth unit includes a processor configured to support the fourth unit to perform the corresponding functions in the above method. Further, the fourth unit may further comprise a communication interface for supporting communication between the fourth unit and the first unit or other units. Further, the fourth unit may further comprise a memory for coupling with the processor, which holds program instructions and data necessary for the fourth unit.

In yet another aspect, an embodiment of the present invention provides a computer storage medium for storing computer software instructions for the first unit, which includes a program designed to execute the above aspects.

In yet another aspect, an embodiment of the present invention provides a computer storage medium for storing computer software instructions for the second unit, which includes a program designed to execute the above aspects.

In yet another aspect, an embodiment of the present invention provides a computer storage medium for storing computer software instructions for the third unit, which includes a program designed to execute the above aspects.

In a further aspect, an embodiment of the present invention provides a computer storage medium for storing computer software instructions for the fourth unit, which includes a program designed to execute the above aspects.

In a further aspect, an embodiment of the present invention provides a communication system, where the communication system includes the first unit, the second unit, and the third unit described in the above aspect; alternatively, the system comprises the first unit and the fourth unit as described in the above aspect.

Compared with the prior art, in the scheme of the embodiment of the invention, after the network slice instance is created or updated, the first unit may send information of the created or updated network slice instance to the second unit, and the second unit may store or configure the information of the network slice instance, so that it is possible to avoid allocating an unsuitable network slice instance to the terminal.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on the drawings without creative efforts.

Fig. 1 is a schematic diagram of a possible application scenario provided in an embodiment of the present invention;

fig. 2A is a schematic diagram of a possible network architecture according to an embodiment of the present invention;

fig. 2B is a schematic diagram of another possible network architecture according to an embodiment of the present invention;

fig. 3 is a communication diagram of an information sending method according to an embodiment of the present invention;

fig. 4 is a communication diagram of another information sending method according to an embodiment of the present invention;

fig. 5 is a communication diagram of another information sending method according to an embodiment of the present invention;

fig. 6 is a communication diagram of an information deleting method according to an embodiment of the present invention;

fig. 7 is a communication diagram of another information sending method according to an embodiment of the present invention;

fig. 8 is a communication diagram of another information sending method according to an embodiment of the present invention;

fig. 9 is a communication diagram of another information deletion method according to an embodiment of the present invention;

FIG. 10A is a schematic block diagram of a first unit provided in an embodiment of the present invention;

fig. 10B is a schematic structural diagram of a first unit according to an embodiment of the present invention;

FIG. 11A is a schematic block diagram of a second unit provided in an embodiment of the present invention;

fig. 11B is a schematic structural diagram of a second unit according to an embodiment of the present invention;

fig. 12A is a schematic block diagram of a third unit provided in the embodiment of the present invention;

fig. 12B is a schematic structural diagram of a third unit according to an embodiment of the present invention;

fig. 13A is a schematic block diagram of a co-located unit according to an embodiment of the present invention;

fig. 13B is a schematic structural diagram of a combination unit according to an embodiment of the present invention.

Detailed Description

In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be described below with reference to the drawings in the embodiments of the present invention.

The network architecture and the service scenario described in the embodiment of the present invention are for more clearly illustrating the technical solution of the embodiment of the present invention, and do not form a limitation on the technical solution provided in the embodiment of the present invention, and it can be known by those skilled in the art that the technical solution provided in the embodiment of the present invention is also applicable to similar technical problems along with the evolution of the network architecture and the appearance of a new service scenario.

Some possible application scenarios and network architectures to which the embodiment of the present invention is applicable will be described below with reference to fig. 1, fig. 2A, and fig. 2B.

Fig. 1 is a schematic diagram of a possible application scenario provided in an embodiment of the present invention. The various elements referred to in fig. 1 are briefly described below:

a Service Orchestration (SO) unit, which may also be referred to as a Service orchestration and management unit or a Service management unit, mainly includes: performing life cycle management (such as instantiation, updating, deleting, etc.) on a service (service) according to the service request message; service polymerization; service management, such as Fault, configuration, charging, performance, and Security (FCAPS) management of a service; and mapping between service and network slice, etc. The Service may be a communication Service of a group of Service Level Agreements (SLA) specified by the user, such as a Mobile Broadband (MBB) Service, a voice Service, and an Internet of Things (IOT) Service (e.g., an intelligent parking Service, an intelligent meter reading Service, etc.). For example, the SO unit may manage traffic carried by the network slice.

The Network Orchestration (NO) unit mainly includes: management of network slices, such as lifecycle management of network slices, management of network slice templates, etc.; mapping between network slices and network functions; coordination of different types of network resources; network resources provided by different operators and different network providers are coordinated, so that the network resources provided by different network providers can meet the requirements of target services, such as requirements of SLAs, requirements of Key Performance Indicators (KPIs), requirements of Quality of Service (QoS), and the like; unified orchestration of network devices provided by different vendors; providing an external Application Program Interface (API), wherein the API is configured to provide a network function for a third party, so as to implement the deployment across operators.

An Element Manager (EM) unit, which may also be referred to as a network function management unit, mainly includes: lifecycle management (e.g., instantiation, updating, deletion, etc.) of network elements or network functions; FCAPS management of network elements or network functions, etc.

A Core Network (CN), whose functions mainly include: control Plane (CP) network functions (e.g., a function of selecting a network slice, a mobility management function, etc.) and User Plane (UP) network functions (e.g., a network function of a serving gateway, a charging function, etc.). Illustratively, a CP unit and an UP unit may be included in the CN, wherein the CP unit has a CP network function, and the UP unit has an UP network function; alternatively, a Common Network Function (Common NF) unit having a CP Network Function and/or an UP Network Function may be included in the CN.

Radio Access Network (Radio Access Network): RAN is mainly deployed with some radio access Network elements (RAN NEs), such as evolved Node B (evolved Node B, eNodeB or eNB). In addition, some RAN Network Function (RAN NF) entities, such as eNodeB Function, may also be deployed in the RAN.

Wherein, the SO unit is connected with the NO unit, the NO unit is also connected with the EM/NF-M unit, and the EM/NF-M unit is also respectively connected with the CN and the RAN.

It should be understood that the above description of the functions of each unit is only an example, each unit may also have other functions, and the embodiments of the present invention are not limited thereto.

Based on the above application scenarios, fig. 2A shows a possible network architecture provided by the embodiment of the present invention. As shown in fig. 2A, the network architecture may have two different deployments.

In a first deployment, the network architecture comprises: a Network Slice organization and Management (nsama) unit, a Network Slice Selection Function (NSSF) unit, and a Common NF unit. The nsam unit interfaces with the NSSF unit and the Common NF unit, and the connection relationship between these units is shown by a solid line in fig. 2A.

For convenience of description, hereinafter, a certain unit may be denoted by its english abbreviation, for example, a nsaam unit may be denoted by nsaam, and other units are similar and will not be described in detail later.

In a second deployment, the network architecture comprises: NSOAM, network Function Manager (NF-M) unit, NSSF, and Common NF. An interface is arranged between NSOAM and NF-M, and interfaces are arranged between NF-M and NSSF and Common NF respectively, and the connection relationship between these units is shown by a dotted line in FIG. 2A. It should be noted that, in this deployment mode, no interface exists between the nsaoam and the NSSF and Common NF. Wherein, the NF-M can be replaced by a Data Center (Data Center); alternatively, the NF-M may have both its own function and the Data center function. "NF-M/Data Center" shown in FIG. 2A represents a unit having the function of NF-M and/or the function of Data Center.

In the two deployment manners, the Common NF unit may be replaced by a Network Function repository (NF repository) unit; alternatively, the Common NF unit may have both its own function and the function of the NF repetition unit. "Common NF/NF repetition" shown in fig. 2A denotes a unit having the function of a Common NF unit and/or the function of an NF repetition unit.

The following briefly introduces NSOAM, NSSF, common NF, NF repetition, NF-M, and Data Center, respectively.

The nsaoam is responsible for lifecycle management of network slices (e.g., creation, deletion, modification, etc. of network slices), configuration management, fault management, and performance management, among others. In the Network architecture shown in fig. 2A, the nsam may also be replaced by a Network Slice Orchestration (NSO) unit, an NSM (Network Slice Manager) unit, an NO unit, a Network Management (NM) unit, or a Network Function Virtualized Manager (NFVO) unit. Wherein the NSO is responsible for lifecycle management of the network slice (e.g., creation, deletion, modification, etc. of the network slice); the NSM is responsible for configuration management, fault management, performance management and the like of the network slices; NO is responsible for the lifecycle management of the network; NM is responsible for network configuration management, fault management and performance management; the NF-M is responsible for life cycle management, configuration management, fault management, performance management and the like of network functions; the NFVO is responsible for lifecycle management, configuration management, fault management, performance management, etc. of network services and virtual network functions. Optionally, nsams may also be deployed in the NO shown in fig. 1.

NSSF is used to select and allocate available network slice instances for a terminal.

Common NF is used to assign network function instances to terminals. As introduced with respect to Common NF in fig. 1, common NF may be capable of CP network functionality and/or UP network functionality.

NF repetition is used to store information for the network function instance.

NF-M is used to configure or activate NSSF and Common NF. Alternatively, the NF-M may be deployed in the EM shown in FIG. 1.

The Data Center, which may also be referred to as a network slice Data Center, is a database that stores information of network slice instances and information of network function instances. The NSSF and Common NF described above may access the Data Center.

Based on the above application scenarios, fig. 2B shows another possible network architecture provided by the embodiment of the present invention. As shown in fig. 2B, the network architecture may have two different deployments.

In a first deployment, the network architecture comprises: nsaam and Common NF, where there is an interface between the nsaam and Common NF, and the connection relationship between these units is shown by solid lines in fig. 2B.

In a second deployment, the network architecture comprises: NSOAM, NF-M, and Common NF. The NF-M interfaces with nsaam and Common NF, respectively, and the connection relationship between these units is shown by the dashed line in fig. 2B. It should be noted that, in this deployment, no interface exists between nsaam and Common NF.

In the network architecture shown in fig. 2B, common NF here is Common NF having both its own function and the function of NSSF. Wherein the Common NF may be replaced by a Network Slice Controller (NSC) unit. "Common NF/NSC" shown in fig. 2B indicates a unit having the function of Common NF and/or the function of DSC.

In the network architecture shown in FIG. 2B, the details of NSOAM, NSSF, common NF, NF-M, and Data Center are described with reference to FIG. 2A. NSC is briefly described below.

The NSC is used for activating the network slice instance, distributing the network slice instance for the terminal and selecting the network function instance for the terminal.

In the embodiments of the present invention, the terms "network" and "system" are often used interchangeably, but those skilled in the art can understand the meaning. The terminal according to the embodiment of the present invention may include various handheld devices, vehicle-mounted devices, wearable devices, computing devices or other processing devices connected to a wireless modem, and various forms of User Equipment (UE), mobile Stations (MS), terminal devices (terminal device), and the like. For convenience of description, the above-mentioned devices are collectively referred to as a terminal.

The Network slice example related to the embodiment of the present invention may at least include a Core Network (CN) portion, a Radio Access Network (RAN) portion, and a Transport Network (TN) portion; alternatively, the network slice example according to the embodiment of the present invention may include any two of the CN part, the RAN part, or the TN part; alternatively, the network slice instance according to the embodiment of the present invention may represent a network slice instance of a CN part, a network slice instance of a RAN part, or a network slice instance of a TN part. It is to be understood that the network slice example according to the embodiment of the present invention may have other embodiments, and the embodiment of the present invention is not limited thereto.

The embodiments of the present invention will be described in further detail below based on the common aspects related to the embodiments of the present invention described above.

In the existing scheme, after a terminal accesses a network, a network side device needs to allocate a network slice instance to the terminal based on some manually input network information to provide a service for the terminal. For example, the network information includes virtual machine information and the like. However, since the network slice instances may be dynamically added, modified and deleted, the terminal often cannot be allocated a suitable network slice instance based on the above network information.

In view of the above, the embodiments of the present invention provide an information sending method, and a unit and a system based on the method. The method comprises the following steps: the first unit creates or updates a network slice instance; then, the first unit sends a first message to the second unit, wherein the first message carries first network slice instance information, the first network slice instance information is first information of a created or updated network slice instance, and the first network slice instance information comprises an identifier of the network slice instance; the second unit saves or configures the first network slice instance information. In the scheme of the embodiment of the invention, after the network slice instance is created or updated by the first unit, the information of the created or updated network slice instance can be sent to the second unit, and the second unit can store or configure the information of the network slice instance, so that the situation that an improper network slice instance is allocated to the terminal can be avoided.

It should be noted that, in the above method, the embodiment of the present invention is not limited to the timing or the condition for the first unit to send the first message to the second unit. For example, the first unit may send the first message to the second unit immediately after the network slice instance is created or updated, or may send the first message to the second unit after a period of time; for another example, the first unit may actively send the first message to the second unit, or may send the first message to the second unit at the request of the second unit or in other cases.

The following describes the scheme provided by the embodiment of the present invention with reference to fig. 3. The method shown in fig. 3 is described by taking the network architecture of the application as the network architecture shown in fig. 2A. The method shown in fig. 3 comprises: 301-303.

In section 301, the first unit creates or updates a network slice instance.

In one example, the first unit creating a network slice instance may add or instantiate a network slice instance for the first unit. For example, the first unit may create one network slice instance by way of instantiation.

The first unit may be nsaoam in fig. 2A, or NSO, NSM, NO, NM, or NFVO.

In part 302, a first unit sends a first message to a second unit, the first message carrying first network slice instance information, the first network slice instance information being first information of a created or updated network slice instance.

Wherein the first network slice instance information comprises an identification of the network slice instance.

In one example, the first message may be an add notification message of a network slice instance, a configuration message of a network slice instance, an update notification message of a network slice instance, or a reconfiguration message of a network slice instance. For example, if the first unit creates a network slice instance in section 301, the first message may be an add-new notification message for the network slice instance or a configuration message for the network slice instance; if the first unit updates the network slice instance in section 301, the first message may be an update notification message of the network slice instance or a reconfiguration message of the network slice instance.

In one possible embodiment, when the first message is an addition notification message of a network slice instance or a configuration message of a network slice, the first network slice instance information may further include at least one of: the network slice instance comprises a status of the network slice instance, a type of the network slice, information of the network function instance required by the network slice instance, information of tenants supported by the network slice instance (e.g., an identification of the tenant, a priority of the tenant, etc.), or information of services provided by the network slice instance (e.g., a type of the service, an identification of the service instance, etc.), wherein the information of the network function instance comprises the identification of the network function instance and the status of the network function instance. Or, when the first message is an update notification message of a network slice instance or a reconfiguration message of the network slice instance, the first network slice instance information may further include at least one of: the network slice instance comprises an updated state of the network slice instance, information of the network function instance required after the network slice instance is updated, information of a tenant supported after the network slice instance is updated (for example, an identifier of the tenant, a priority of the tenant, and the like), or information of a service provided after the network slice instance is updated (for example, a type of the service, an identifier of the service instance, and the like), wherein the information of the network function instance comprises the identifier of the network function instance and the state of the network function instance.

Wherein, the state of the network slice instance may include at least one of the following: active, inactive, available, or unavailable. Of course, the state of the network slice example may have other forms, and the embodiment of the present invention does not limit this.

The tenant information supported by the network slice instance and/or the service information provided by the network slice instance can be used for allocating a target network slice instance satisfying the service request to the terminal. Or, the tenant information supported by the updated network slice instance and/or the service information provided by the updated network slice instance may be used to allocate a target network slice instance satisfying the service request to the terminal.

In one example, before the first unit sends the first message to the second unit, the second unit may send a subscription request to the first unit, the subscription request for subscribing to the first network slice instance information; alternatively, the second unit may send a query request to the first unit, the query request for querying the first network slice instance information.

The second unit may be NSSF in FIG. 2A, or NF-M/Data Center in FIG. 2A. For example, if the second unit is an NSSF, the first message may be an update notification message of a network slice instance or an update notification message of a network slice instance; or, if the second unit is an NF-M/Data Center, the first message may be a configuration message of a network slice instance or a reconfiguration message of the network slice instance. When the first message is a message of a different type, the content that the carried first network slice instance information may also include may refer to the detailed description in the foregoing example, which is not described herein again.

In one example, the first unit may further send a second message to the third unit, where the second message carries second network slice instance information, and the second network slice instance information is second information of the created or updated network slice instance, where the second network slice instance information includes an identifier of the network slice instance. It should be noted that the scheme of this example may be executed before the portion 302 is executed, or may be executed after the portion 302 is executed, or the scheme and the portion 302 of this example may be executed simultaneously, and the embodiment of the present invention is not limited.

The third unit may be Common NF/NF repetition in FIG. 2A, or NF-M/Data Center in FIG. 2A.

The second message may be an addition notification message of a network slice instance, a configuration message of the network slice instance, an update notification message of the network slice instance, or a reconfiguration message of the network slice instance. For example, if the first unit creates a network slice instance in section 301, the second message may be an add-new notification message for the network slice instance or a configuration message for the network slice instance; if the first unit updates the network slice instance in section 301, the second message may be an update notification message for the network slice instance or a reconfiguration message for the network slice instance.

In one possible embodiment, the second network slice instance information may further include a status of the network slice instance and/or information of the network function instance required by the network slice instance, wherein the information of the network function instance includes at least one of: an identification of a network function instance, a status of a network function instance, or a type of network function instance. For example, if the first unit creates a network slice instance in section 301, the second network slice instance information may also include the above.

In another possible implementation, the second network slice instance information may further include an updated status of the network slice instance and/or information of a network function instance required after the network slice instance is updated, wherein the information of the network function instance includes at least one of: an identification of an updated network function instance, a status of an updated network function instance, an identification of an newly added network function instance, or an identification of a deleted network function instance. For example, if the first unit updates the network slice instance in section 301, the second network slice instance information may also include the above.

The third unit may save the second network slice instance information after receiving the second message from the first unit. Further, the second unit may also activate the network slice instance according to the second network slice instance information.

In one example, the first unit may further send a second deletion notification to the third unit, the second deletion notification for notifying the third unit to delete the second network slice instance information. Wherein the second deletion notification may carry an identification of the network slice instance.

The second unit saves or configures the first network slice instance information, at 303.

In one example, if the second unit is an NSSF or Data Center, the second unit may save the first network slice instance information; alternatively, if the second unit is NF-M, the second unit may configure the first network slice instance information. For example, the second unit configuring the first network slice instance information means that the NF-M configures the first network slice instance information on the NSSF or Data Center.

In one example, the second unit may further activate the network slice instance according to the first network slice instance information.

In one example, the second unit may further receive a service request from the terminal, and allocate a target network slice instance satisfying the service request to the terminal according to the first network slice instance information. For convenience of description, hereinafter, the target network slice example is described as a target slice example. It should be noted that, if the term "network slice instance" appears hereinafter, the term refers to a non-target slice instance. For example, if the second unit is an NSSF, the second unit may receive a service request of the terminal, and allocate the target slice instance to the terminal according to the stored first network slice instance information and the service request. The service request may carry information of the terminal, and the second unit may further associate the network slice instance with the terminal. For example, the information of the terminal may comprise an identification of the terminal, and the second unit may associate the identification of the network slice instance and the identification of the terminal.

In another example, the second unit may also provide the first network slice instance information to other units. For example, if the second unit is a Data Center, the NSSF may receive a service request of the terminal, query the Data Center for first network slice instance information, and then allocate a target slice instance to the terminal according to the first network slice instance information and the service request.

The information of the terminal may include at least one of the following: a tenant identity associated with the terminal, a type of service requested by the terminal, or a type of network slice instance required by the terminal. The tenant identity associated with the terminal may be referred to as a second tenant identity, the service type requested by the terminal may be referred to as a second service type, and the type of the network slice instance required by the terminal may be referred to as a second instance type.

In one possible implementation, the first network slice instance information includes at least one of: the tenant information, the service information, the state of the network slice instance, or the type of the network slice instance. The second unit may allocate the target slicing instance to the terminal according to at least one of the tenant information, the service information, the state of the network slicing instance, or the type of the network slicing instance. It should be noted that, in section 301, if the first unit creates a network slice instance, the tenant information and/or service information described herein refers to tenant information supported by the network slice instance and/or service information provided by the network slice instance; alternatively, if the first unit updates the network slice instance in section 301, the tenant information and/or service information described herein refers to tenant information supported by the updated network slice instance and/or service information provided by the updated network slice instance.

The second unit allocates a target slicing instance to the terminal according to at least one of the tenant information, the service information, the state of the network slicing instance, and the type of the network slicing instance, and the allocation may be performed in one or at least two of the following manners:

the first mode is as follows: the first network slice instance information includes tenant information and service information, where the tenant information is a first tenant identifier, the service information is a first service identifier, and an implementation process of the second unit allocating a target slice instance to the terminal may be one of the following cases:

(1) The service request of the terminal only carries the second tenant identification, and the second unit can search the first tenant identification which is the same as the second tenant identification, so that the network slice instance corresponding to the first tenant identification is determined as the target slice instance, and the target slice instance is distributed to the terminal.

(2) The service request of the terminal only carries the second service type, and the second unit can search the first service type which is the same as the second service type, so that the network slice example corresponding to the first service type is determined as the target slice example, and the target slice example is distributed to the terminal.

(3) The service request of the terminal carries a second tenant identity and a second service type, the second unit can search a network slice instance in which the first tenant identity is the same as the second tenant identity and the first service type is the same as the second service type, determine the network slice instance as a target slice instance, and allocate the target slice instance to the terminal.

The second mode is as follows: the first network slice instance information comprises the state of the network slice instance, the second unit searches the network slice instance with the state available according to the service request of the terminal, determines the network slice instance as a target slice instance, and distributes the target slice instance for the terminal.

The third mode is as follows: the first network slice instance information includes a type of a network slice instance, the type of the network slice instance may be referred to as a first instance type, a service request of the terminal carries a second instance type, and the second unit may search for the first instance type that is the same as the second instance type, thereby determining the network slice instance corresponding to the first instance type as a target slice instance, and allocating the target slice instance to the terminal.

It should be noted that one or at least two network slice instances can be screened out by one or at least two of the three ways described above. And if one network slice example is screened out, determining the network slice example as the target slice example. If at least two network slice instances are screened out, one network slice instance can be further determined from the at least two network slice instances according to other information to serve as a target slice instance. For example, the target slice instance may be further determined according to a type of the terminal, an identification of the terminal (e.g., international Mobile Subscriber Identity (IMSI), temporary Mobile Subscriber Identity (TMSI), etc.), and the like.

In one example, the second unit may further send a selection request to the third unit, the selection request requesting a network function instance required by the target slice instance. Optionally, the selection request may carry information of the terminal and an identifier of the network slice instance, where the information of the terminal may include the identifier of the terminal.

After receiving the selection request from the second unit, the third unit may select a network function instance required by the target slice instance according to the selection request and the second network slice instance information.

In one example, the second unit may also receive a first deletion notification from the first unit, the first deletion notification to notify the second unit to delete the first network slice instance information. Wherein the first deletion notification may carry an identifier of the network slice instance.

The scheme provided by the embodiment of the present invention is further explained below with reference to fig. 4-fig. 6 on the basis of the method shown in fig. 3. In the method shown in fig. 4-fig. 6, the same or similar contents as those in the method shown in fig. 3 can refer to the detailed description in fig. 3, and are not repeated herein.

Fig. 4-fig. 6 shows a network architecture applied by the method shown in fig. 2A, wherein the scheme of the embodiment of the present invention is described by taking the first unit as nsam, the second unit as NSSF, and the third unit as Common NF/NF repetition.

Fig. 4 is an information sending method in a scenario of creating a network slice example according to an embodiment of the present invention. The method illustrated in FIG. 4 includes portions 401-414, where portions 401, 406, and 410 are optional.

In part 401, the NSSF sends a subscription request or a query request to the nsaam.

Wherein the subscription request or the query request is for requesting first network slice instance information.

At part 402, the nsaam creates a network slice instance.

It should be noted that the embodiment of the present invention does not limit the execution sequence of the parts 401 and 402. For example, part 401 may be executed first, and part 402 may be executed later; or execute part 402 first and then part 401; alternatively, the 401 and 402 parts may also be performed simultaneously.

In part 403, the nsaam sends an addition notification of the network slice instance to the NSSF, where the addition notification carries information of the first network slice instance.

Wherein the first network slice instance information is first information of the created network slice instance. The introduction of the information about the first network slice example can refer to the detailed description in section 302 of fig. 3, and is not described herein again.

The NSSF stores the first network slice instance information, at 404.

The NSSF activates the network slice instance based on the first network slice instance information, at 405.

In part 406, the NSSF sends a response message to the nsaam to inform the nsaam of: the NSSF has saved the first network slice instance information and activated the network slice instance.

In part 407, the nsaam sends an addition notification of the network slice instance to Common NF/NF repetition, the addition notification carrying second network slice instance information.

Wherein the second network slice instance information is second information of the created network slice instance. The introduction of the second network slice example information may refer to the detailed description in section 302 of fig. 3, which is not repeated herein.

In part 408, common NF/NF repetition stores second network slice instance information.

At part 409, common NF/NF replication activates the network slice instance in accordance with the second network slice instance information.

In part 410, common NF/NF repetition sends a response message to the nsaam to inform the nsaam of: common NF/NF replication has saved the second network slice instance information and activated the network slice instance.

It should be noted that the execution sequence of the 403-406 part and the 407-410 part is not limited in the embodiment of the present invention. For example, the-403 portion 406 may be executed first, and the-410 portion 407; it is also possible to execute 407-410 first and then 403-406; alternatively, the execution 403-406 portion and 407-410 portion may also be notified.

The NSSF receives a service request from a terminal at 411.

In an example, the service request may carry information of the terminal, and the introduction of the information about the terminal may refer to the detailed description of part 303 in fig. 3, which is not described herein again.

Note that, if the request sent by the NSSF to the nsaam in the portion 401 is an inquiry request, in the method shown in fig. 4, the portions 401 and 403-410 may not be executed first, but the portions 401 and 403-410 may be executed after the portion 411. That is, after receiving a service request from a terminal, the NSSF sends an inquiry request to the nsaam and performs subsequent steps.

In part 412, the NSSF assigns a target slice instance to the terminal that satisfies the service request according to the first network slice instance information.

For a specific implementation process of allocating a target slice to a terminal by using NSSF, reference may be made to detailed description of an example of allocating a target slice to a terminal by using a second unit in section 303 of fig. 3, which is not described herein again.

In part 413, the NSSF sends a selection request to Common NF/NF repetition requesting the network function instance required by the target slice instance.

Part 414, common NF/NF repetition selects the network function instance required by the target slice instance based on the selection request and the second network instance information.

In the method shown in FIG. 4, NSSF may be replaced with NF-M. If the NSSF is replaced with NF-M, the new addition notification of the network slice instance in section 403 is replaced with a configuration message of the network slice instance; the saved first network slice instance information in section 404 is replaced with configured first network slice instance information; the saved second network slice instance information in section 408 is replaced with configured second network slice instance information. Furthermore, if NSSF is replaced with NF-M, the above-mentioned portion 411-414 is not performed.

Fig. 5 is an information sending method in a scenario of updating a network slice example according to an embodiment of the present invention. The method shown in fig. 5 is similar to the method shown in fig. 4, and in the method shown in fig. 5, the details similar to those in fig. 4 may refer to the detailed description in fig. 4, and only the differences are explained here, and the other contents are not repeated. The method shown in fig. 5 mainly differs from the method shown in fig. 4 in that:

(1) In section 502, the nsaam updates the network slice instance; and in part 402, the nsaam creates a network slice instance.

(2) What is involved in the method shown in fig. 5 is a notification of the addition of a network slice instance; while the method shown in fig. 4 involves notification of updates to network slice instances.

(3) The first network slice instance information and the second network slice instance information involved in the method shown in fig. 5 are different from the first network slice instance information and the second network slice instance information involved in the method shown in fig. 4, the former is for a scenario of creating a network slice instance, and the latter is for a scenario of updating a network slice instance. Specifically, the difference between these information can be found from the detailed description of the portion 302 in fig. 3, and is not described herein again.

In the method shown in FIG. 5, NSSF may be replaced with NF-M. If the NSSF is replaced with NF-M, then the update notification for the network slice instance in section 503 is replaced with a reconfiguration message for the network slice instance; the saved first network slice instance information in section 504 is replaced with configured first network slice instance information; the saved second network slice instance information in section 508 is replaced with the configured second network slice instance information. Further, if NSSF is replaced with NF-M, the above-mentioned portion 511-514 is not performed.

Fig. 6 is a method for deleting information according to an embodiment of the present invention. The method shown in fig. 6 may be performed on the basis of the methods shown in fig. 3, 4 or 5. The method shown in fig. 6 includes a 601-608 portion, wherein the 601 portion, the 605 portion and the 608 portion are optional portions.

In part 601, the NSSF sends a subscription request or a query request to the nsaam.

Wherein the subscription request or query request is for requesting information regarding deletion of a network slice instance.

At part 602, the nsaam deletes the network slice instance.

It should be noted that the embodiment of the present invention does not limit the execution sequence of the sections 601 and 602. For example, portion 601 may be performed first, followed by portion 602; or the 602 part can be executed first, and then the 601 part can be executed; alternatively, portions 601 and 602 may also be performed simultaneously.

In part 603, the nsaam sends a deletion notification of the network slice instance to the NSSF, the deletion notification carrying an identifier of the network slice instance.

The NSSF deletes the first network slice instance information based on the identification of the network slice instance, at portion 604.

The first network slice instance information is first information of a created or updated network slice instance, and reference may be made to detailed description in section 302 of fig. 3 for introduction of the first network slice instance information, which is not described herein again.

In part 605, the NSSF sends a response message to the nsaam to inform the nsaam of: the NSSF has deleted the first network slice instance information.

In part 606, the nsaam sends a deletion notification of the network slice instance to Common NF/NF replication, the deletion notification carrying an identification of the network slice instance.

In part 607, common NF/NF repetition deletes the second network slice instance information based on the identification of the network slice instance.

The second network slice instance information is second information of a created or updated network slice instance, and reference may be made to detailed description in section 302 of fig. 3 for introduction of the second network slice instance information, which is not described herein again.

In part 608, common NF/NF repetition sends a response message to the nsam to inform the nsam of: common NF/NF repetition has deleted the second network slice instance information.

In the method shown in FIG. 6, NSSF may be replaced with NF-M/Data Center.

The method shown in fig. 3-fig. 6 is described by taking the applied network architecture as the network architecture shown in fig. 2A, and it should be noted that the solution of the embodiment of the present invention can also be applied to the network architecture shown in fig. 2B. When the network architecture shown in fig. 2B is applied, the functions of the second unit and the third unit are performed by one co-located unit in the method shown in fig. 3-6. In this case, the interaction between the second unit and the third unit may not be performed; or the second unit and the third unit may be set as internal modules in the combination unit, and the interaction between the second unit and the third unit is the interaction between different internal modules in the combination unit. The combination unit may be Common NF/NSC shown in fig. 2B. For convenience of description, the above-mentioned combination unit may also be referred to as a fourth unit.

Referring to fig. 7-fig. 9, a Common NF is taken as an example to explain a scheme of the embodiment of the present invention when the network architecture shown in fig. 2B is applied. In the method shown in FIG. 7-FIG. 9, similar contents to those in the method shown in FIG. 3-FIG. 7 can refer to the detailed description in FIG. 3-FIG. 7, which is not repeated herein.

Fig. 7 is another information sending method in a scenario of creating a network slice example according to an embodiment of the present invention. The method shown in FIG. 7 includes portions 701-709 where portions 701 and 706 are optional.

In part 701, common NF sends a subscription request or a query request to nsam.

Wherein the subscription request or the query request is for requesting third network slice instance information. The third network slice instance information is third information of the created network slice instance, the third network slice instance information including an identification of the network slice instance. Further, the third network slice example information may also include part or all of the content of the first network slice example information and/or the second network slice example related in the method shown in fig. 3 or fig. 4, which may specifically refer to the description about the first network slice example information and the second network slice example information, and is not described herein again.

At 702, the nsaam creates a network slice instance.

It should be noted that the embodiment of the present invention does not limit the execution sequence of the part 701 and the part 702. For example, part 701 may be performed first, and part 702 may be performed later; or the 702 part can be executed first, and then the 701 part can be executed; alternatively, the 701 and 702 portions may also be performed simultaneously.

In part 703, the nsaam sends an addition notification of the network slice instance to Common NF, the addition notification carrying third network slice instance information.

The Common NF maintains third network slice instance information, at 704.

In part 705, the Common NF activates the network slice instance in accordance with the third network slice instance information.

Part 706, common NF sends a response message to nsaam to inform nsaam of: common NF has saved the third network slice instance information and activated the network slice instance.

At 707, common NF receives a service request of the terminal.

In an example, the service request may carry information of the terminal, and the description of the information about the terminal may refer to detailed description of part 303 in fig. 3, which is not described herein again.

Note that, if the request from the Common NF to the nsaam is an inquiry request in the 701 portion, the 701 portion and the 703-706 portion may not be executed first, and the 701 portion and the 703-706 portion may be executed after the 707 portion is executed in the method shown in fig. 7. That is, after receiving the service request of the terminal, the Common NF sends an inquiry request to the nsaam, and performs the subsequent steps.

At 708, the Common NF assigns a target slice instance satisfying the service request to the terminal according to the third network slice instance information.

A specific implementation process of the Common NF allocating a target slice example to the terminal is similar to the specific implementation process of the NSSF allocating a target slice example to the terminal in the part 412 of fig. 4, and reference may be made to the detailed description of the part 412, which is not described herein again.

In section 709, common NF selects the network function instance required for the target slice instance according to the third network slice instance information.

In the method shown in FIG. 7, common NF may be replaced by NF-M. If Common NF is replaced with NF-M, then the new addition notification of the network slice instance in section 703 is replaced with a configuration message for the network slice instance; the saved third network slice instance information in section 704 is replaced with the configured third network slice instance information. Further, if Common NF is replaced with NF-M, the above-mentioned portion 707-709 is not executed.

Fig. 8 is another information sending method in a scenario of creating a network slice example according to an embodiment of the present invention. The method shown in fig. 8 is similar to the method shown in fig. 7, and in the method shown in fig. 8, the details similar to those in the method shown in fig. 7 may refer to the details in fig. 7, and only the differences are explained here, and the other contents are not described again. The main differences between the method shown in fig. 8 and that shown in fig. 7 are:

(1) In part 802, the nsaam updates the network slice instance; whereas in section 702, the nsaam creates a network slice instance.

(2) FIG. 8 illustrates a method involving notification of an addition to a network slice instance; while the method shown in fig. 7 involves notification of updates to network slice instances.

(3) The third network slice instance information involved in the method shown in fig. 8 is different from the third network slice instance information involved in the method shown in fig. 7, the former being for a scenario in which a network slice instance is created, and the latter being for a scenario in which a network slice instance is updated. Specifically, the difference of the information can be found from the detailed description of the portion 302 in fig. 3, and is not described herein again.

It should be noted that Common NF may be replaced by NF-M in the method shown in FIG. 8. If Common NF is replaced with NF-M, then the update notification for the network slice instance in section 803 is replaced with a reconfiguration message for the network slice instance; the saved third network slice instance information in section 804 is replaced with the configured third network slice instance information. Further, if Common NF is replaced with NF-M, the above-mentioned portion 807-809 is not performed.

Fig. 9 is another information deleting method according to an embodiment of the present invention. The method shown in fig. 9 may be performed on the basis of the method shown in fig. 7 or fig. 8. Among them, the method shown in FIG. 9 includes the 901 portion-905 portions, in which the 901 portion and 905 portions are optional portions.

In 901, common NF sends a subscription request or a query request to nsam.

In section 902, the nsaam deletes the network slice instance.

It should be noted that the embodiment of the present invention does not limit the execution sequence of the 901 part and the 902 part. For example, the 901 part may be executed first, and then the 902 part may be executed; or, the 902 part may be executed first, and then the 901 part may be executed; alternatively, the 901 part and the 902 part may also be performed simultaneously.

In part 903, the nsaam sends a deletion notification of the network slice instance to Common NF, which carries the identity of the network slice instance.

In part 904, common NF deletes the third network slice instance information according to the identification of the network slice instance.

The third network slice instance information is third information of a created or updated network slice instance, and reference may be made to detailed description of the third network slice instance information in the method shown in fig. 7 or fig. 8 for introduction of the third network slice instance information, which is not described herein again.

In part 905, common NF sends a response message to nsaam to inform nsaam of: common NF has deleted the third network slice instance information.

It should be noted that Common NF may be replaced by NF-M/Data Center in the method shown in FIG. 9.

The above description mainly introduces the solution provided by the embodiment of the present invention from the perspective of interaction between different units. It is understood that the first unit, the second unit, the third unit and the combination unit include hardware structures and/or software modules for performing the functions. The elements and algorithm steps of the various examples described in connection with the embodiments disclosed herein may be embodied in hardware or in a combination of hardware and computer software. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present teachings.

In the embodiment of the present invention, the first unit, the second unit, the third unit, the combining unit, and the like may be divided into the functional modules according to the above method examples, for example, each functional module may be divided according to each function, or two or more functions may be integrated into one processing module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. It should be noted that, the division of the modules in the embodiment of the present invention is schematic, and is only a logic function division, and there may be another division manner in actual implementation.

In case an integrated unit is employed, fig. 10A shows a possible schematic block diagram of the first unit involved in an embodiment of the present invention. The first unit 1000 includes: a processing module 1002 and a communication module 1003. Processing module 1002 is configured to control and manage the actions of the first unit, for example, processing module 1002 is configured to support the first unit to perform processes 301 and 302 in fig. 3, processes 402, 403, and 407 in fig. 4, processes 502, 503, and 507 in fig. 5, processes 602, 603, and 606 in fig. 6, processes 702 and 703 in fig. 7, processes 802 and 803 in fig. 8, processes 902 and 903 in fig. 9, and/or other processes for the techniques described herein. The communication module 1003 is used for supporting the communication between the first unit and the second unit, the third unit or the co-located unit. The first unit may further comprise a storage module 1001 for storing program codes and data of the first unit.

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), an Application-Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, a transistor logic device, a hardware component, or any combination thereof. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. The processor may also be a combination of computing functions, e.g., comprising one or more microprocessors, DSPs, and microprocessors, among others. The communication module 1303 may be a communication interface, a transceiver circuit, or the like, where the communication interface is generally referred to, and in a specific implementation, the communication interface may include a plurality of interfaces, which may include, for example: an interface between the first unit and the second unit, the third unit or a combination unit and/or other 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 is a memory, the first unit according to the embodiment of the present invention may be the first unit shown in fig. 10B.

Referring to fig. 10B, the first cell 1010 includes: processor 1012, communication interface 1013, and memory 1011. Optionally, the first unit 1010 may further include a bus 1014. Wherein, the communication interface 1013, the processor 1012, and the memory 1011 may be connected to each other by a bus 1014; the bus 1014 may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The bus 1014 may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 10B, but this is not intended to represent only one bus or type of bus.

The first unit shown in fig. 10A and 10B may be the nsam or other unit in fig. 2A or 2B, such as NSO, NSM, NO, NM, or NFVO.

In case an integrated unit is employed, fig. 11A shows a possible schematic block diagram of the second unit involved in an embodiment of the present invention. The second unit 1100 includes: a processing module 1102 and a communication module 1103. The processing module 1102 is used to control and manage the actions of the second unit, e.g., the processing module 1102 is used to support the second unit in performing the process 303 of FIG. 3, the processes 401, 404-406, and 411-413 of FIG. 4, the processes 501, 504-506, and 511-513 of FIG. 5, the processes 601, 604, and 605 of FIG. 6, and/or other processes for the techniques described herein. The communication module 1103 is used to support the communication between the second unit and the first unit or the third unit. The second unit may further comprise a storage module 1101 for storing program codes and data of the second unit.

The processing module 1102 may be a processor or controller, such as a CPU, general purpose processor, DSP, ASIC, FPGA or other programmable logic device, transistor logic device, hardware component, or any combination thereof. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. The processor may also be a combination of computing functions, e.g., comprising one or more microprocessors, DSPs, and microprocessors, among others. The communication module 1303 may be a communication interface, a transceiver, or a transceiver circuit, etc., where the communication interface is generically referred to, and in a specific implementation, the communication interface may include a plurality of interfaces, which may include, for example: an interface between the second unit and the first unit or the third unit and/or other interfaces. The storage module 1101 may be a memory.

When the processing module 1102 is a processor, the communication module 1103 is a communication interface, and the storage module 1101 is a memory, the second unit according to the embodiment of the present invention may be the second unit shown in fig. 11B.

Referring to fig. 11B, the second unit 1110 includes: processor 1112, communication interface 1113, memory 1111. Optionally, the second unit 1110 may also include a bus 1114. The communication interface 1113, the processor 1112, and the memory 1111 may be connected to each other by a bus 1114; bus 1114 may be a PCI bus or EISA bus, etc. The bus 1114 may be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, only one thick line is shown in FIG. 11B, but this is not intended to represent only one bus or type of bus.

The second unit shown in FIGS. 11A and 11B may be NSSF or NF-M/Data Center in FIG. 2A.

In case an integrated unit is employed, fig. 12A shows a possible schematic block diagram of a third unit involved in an embodiment of the present invention. The third unit 1200 includes: a processing module 1202 and a communication module 1203. The processing module 1202 is used to control and manage the actions of the third unit, e.g., the processing module 1202 is used to support the third unit in performing processes 408-410 and 414 in FIG. 4, processes 508-510 and 514 in FIG. 5, processes 607 and 608 in FIG. 6, and/or other processes for the techniques described herein. The communication module 1203 is used for supporting the communication between the third unit and the first unit or the second unit. The third unit may further comprise a storage module 1201 for storing the program code and data of the third unit.

The processing module 1202 may be a processor or controller, such as a CPU, general purpose processor, DSP, ASIC, FPGA or other programmable logic device, transistor logic device, hardware component, or any combination thereof. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. The processor may also be a combination of computing functions, e.g., comprising one or more microprocessors, DSPs, and microprocessors, among others. The communication module 1303 may be a communication interface, a transceiver circuit, or the like, where the communication interface is generally referred to, and in a specific implementation, the communication interface may include a plurality of interfaces, which may include, for example: an interface between the third unit and the first unit or the second unit and/or other interfaces. The storage module 1201 may be a memory.

When the processing module 1202 is a processor, the communication module 1203 is a communication interface, and the storage module 1201 is a memory, the third unit according to the embodiment of the present invention may be the third unit shown in fig. 12B.

Referring to fig. 12B, the third unit 1210 includes: a processor 1212, a communication interface 1213, and a memory 1211. Optionally, the third unit 1210 may further include a bus 1214. The communication interface 1213, the processor 1212 and the memory 1211 may be connected to each other via the bus 1214; bus 1214 may be a PCI bus, EISA bus, or the like. The bus 1214 may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 12B, but this is not intended to represent only one bus or type of bus.

The third unit shown in FIG. 12A and FIG. 12B may be Common NF/NF repetition or NF-M/Data Center in FIG. 2A.

In case of integrated units, fig. 13A shows a possible schematic block diagram of a co-located unit involved in an embodiment of the invention. The combining unit 1300 includes: a processing module 1302 and a communication module 1303. The processing module 1302 is used for controlling and managing the actions of the setting unit, for example, the processing module 1302 is used for supporting the setting unit to execute the process 303 in FIG. 3, the processes 401, 404-406, 408-412 and 414 in FIG. 4, the processes 501, 504-506, 508-512 and 514 in FIG. 5, the processes 601, 604, 605, 607 and 608 in FIG. 6, the processes 701 and 704 709 in FIG. 7, the processes 801 and 804-809 in FIG. 8, the processes 901, 904 and 905 in FIG. 9, and/or other processes for the techniques described herein. The communication module 1303 is used for supporting the communication between the co-located unit and the first unit. The collocation unit may further comprise a storage module 1301 for storing program codes and data of the collocation unit.

The processing module 1302 may be a processor or a controller, such as a CPU, general purpose processor, DSP, ASIC, FPGA or other programmable logic device, transistor logic device, hardware component, or any combination thereof. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. The processor may also be a combination of computing functions, e.g., comprising one or more microprocessors, DSPs, and microprocessors, among others. The communication module 1303 may be a communication interface, a transceiver, or a transceiver circuit, etc., where the communication interface is generically referred to, and in a specific implementation, the communication interface may include a plurality of interfaces, which may include, for example: an interface between the co-located unit and the first unit and/or other interfaces. The storage module 1301 may be a memory.

When the processing module 1302 is a processor, the communication module 1303 is a communication interface, and the storage module 1301 is a memory, the combining unit according to the embodiment of the present invention may be the combining unit shown in fig. 13B.

Referring to fig. 13B, the co-setting unit 1310 includes: a processor 1312, a communication interface 1313, and a memory 1311. Optionally, the co-location unit 1310 may also include a bus 1314. Wherein, the communication interface 1313, the processor 1312, and the memory 1311 may be connected to each other through a bus 1314; the bus 1314 may be a PCI bus or an EISA bus, etc. The bus 1314 may be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, only one thick line is shown in FIG. 13B, but that does not indicate only one bus or one type of bus.

The co-located units shown in FIGS. 13A and 13B may be Common NF/NSC or NF-M/Data Center in FIG. 2B.

The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied in hardware or in software executed by a processor. The software instructions may be comprised of corresponding software modules that may be stored in Random Access Memory (RAM), flash Memory, read Only Memory (ROM), erasable Programmable ROM (EPROM), electrically Erasable Programmable ROM (EEPROM), registers, a hard disk, a removable disk, a compact disc Read Only Memory (CD-ROM), or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. Of course, the storage medium may also be integral to the processor. The processor and the storage medium may reside in an ASIC. In addition, the ASIC may be located in the first unit, the second unit, the third unit, or a combination unit. Of course, the processor and the storage medium may reside as discrete components in the first unit, the second unit, the third unit, or a combination unit.

Those skilled in the art will recognize that the functionality described in embodiments of the invention may be implemented in hardware, software, firmware, or any combination thereof, in one or more of the examples described above. When implemented in software, the functions may be stored on or transmitted over 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 place to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer.

The above-mentioned embodiments are intended to illustrate the objects, technical solutions and advantages of the embodiments of the present invention in further detail, and it should be understood that the above-mentioned embodiments are only specific embodiments of the present invention, and are not intended to limit the scope of the embodiments of the present invention.

Claims

1. An information transmission method, comprising:

the first unit creates or updates a network slice instance;

the first unit sends a first message to a second unit, the first message carries first network slice instance information, the first network slice instance information includes an identifier of the network slice instance, and the first network slice instance information is used for the second unit to configure a network slice selection function unit, so that the network slice selection function unit allocates a target slice instance to a terminal.

2. The method of claim 1, wherein the first message is a configuration message of a network slice instance, and wherein the first network slice instance information further comprises at least one of:

a status of the network slice instance, a type of the network slice instance, information of a tenant supported by the network slice instance, or information of a service provided by the network slice instance.

3. The method of claim 1 or 2, further comprising:

the first unit sends a second message to a third unit, wherein the second message carries second network slice instance information, the second network slice instance information comprises an identifier of the network slice instance and information of a network function instance required by the network slice instance, and the third unit is used for storing the second network slice instance information; the information of the network function instance comprises at least one of: an identification of the network function instance, a status of the network function instance, or a type of the network function instance.

4. The method according to any of claims 1 to 3, wherein the first unit is a network slicing orchestration domain management unit and the second unit is a network function management unit.

5. An information transmission method, comprising:

a second unit receives a first message from a first unit, wherein the first message carries network slice instance information, and the network slice instance information comprises an identifier of a network slice instance;

and the second unit configures a network slice selection functional unit according to the network slice instance information so that the network slice selection functional unit allocates a target slice instance to the terminal.

6. The method of claim 5, further comprising:

the second unit saves the network slice instance information.

7. The method according to claim 6, wherein the second unit configures a network slice selection functional unit according to the network slice instance information, so that the network slice selection functional unit allocates a target slice instance to a terminal, including:

the second unit transmits the network slice instance information to the network slice selection function unit so that

And the network slice selection functional unit distributes a target slice example meeting the service request of the terminal to the terminal according to the network slice example information.

8. The method of claim 5, wherein the first message is a configuration message of a network slice instance, and wherein the network slice instance information further comprises at least one of: a status of the network slice instance, a type of the network slice instance, information of tenants supported by the network slice instance, or information of services provided by the network slice instance.

9. The method according to claim 8, wherein the network slice instance information includes information of a tenant and/or information of the service, and the second unit configures a network slice selection function unit according to the network slice instance information, so that the network slice selection function unit allocates a target slice instance to a terminal, including:

the second unit configures the network slice selection functional unit according to the network slice instance information, so that the network slice selection functional unit allocates a target slice instance to the terminal according to the tenant information and/or the service information.

10. The method according to any of claims 5 to 9, wherein the first unit is a network slice orchestration domain management unit and the second unit is a network function management unit.

11. An information management unit comprising a processor and a memory, wherein:

the memory to store program instructions;

the processor is configured to call and execute program instructions stored in the memory to cause the information management unit to execute the information transmission method according to any one of claims 1 to 4.

12. An information management unit comprising a processor and a memory, wherein:

the memory to store program instructions;

the processor is configured to call and execute the program instructions stored in the memory, so as to cause the information management unit to execute the information transmission method according to any one of claims 5 to 10.

13. A communication system, comprising: an information management unit according to claim 11 and an information management unit according to claim 12.

14. A computer-readable storage medium characterized by comprising instructions that, when executed on a computer, cause the computer to perform the information transmission method according to any one of claims 1 to 10.