CN114501635A

CN114501635A - Slice resource allocation method, SMF entity, UPF entity and storage medium

Info

Publication number: CN114501635A
Application number: CN202011157798.2A
Authority: CN
Inventors: 包宸曦
Original assignee: Datang Mobile Communications Equipment Co Ltd
Current assignee: Datang Mobile Communications Equipment Co Ltd
Priority date: 2020-10-26
Filing date: 2020-10-26
Publication date: 2022-05-13
Also published as: WO2022088889A1

Abstract

The embodiment of the application provides a slice resource allocation method, an SMF entity, a UPF entity and a storage medium, wherein the method comprises the following steps: determining a target network instance corresponding to the S-NSSAI of the terminal service according to a mapping table acquired in advance, wherein the mapping table is provided with a corresponding relation between the network instance and the S-NSSAI; and sending the parameters of the target network instance to a UPF entity so that the UPF entity performs resource allocation on the target network instance. The embodiment of the application realizes that the UPF entity can simultaneously run a plurality of slices.

Description

Slice resource allocation method, SMF entity, UPF entity and storage medium

Technical Field

The present application relates to the field of communications technologies, and in particular, to a slice resource allocation method, an SMF entity, a UPF entity, and a storage medium.

Background

The slicing technology is a key technology introduced by a fifth generation mobile communication technology (5th generation mobile networks, 5G) network, and can realize the isolation of resources and services and ensure the quality of the services. In the current standard, a Single Network Slice Selection Assistance Information (S-NSSAI) can be carried on a User Plane Function (UPF), indicating the Slice types that can be supported by the User Plane Function (UPF). However, the UPF can only support the operation of one slice at the same time, and the S-NSSAI is only used for performance measurement (performance measurement), namely, the target UPF does not support the operation of a plurality of slices at the same time.

Disclosure of Invention

The embodiment of the application provides a slice resource allocation method, an SMF entity, a UPF entity and a storage medium, so as to solve the problem that the existing UPF does not support simultaneous operation of a plurality of slices.

In a first aspect, an embodiment of the present application provides a slice resource allocation method, applied to a session management function SMF entity, including:

determining a target network instance corresponding to single network slice selection auxiliary information S-NSSAI of a terminal service according to a mapping table acquired in advance, wherein the mapping table is provided with a corresponding relation between the network instance and the S-NSSAI;

and sending the parameters of the target network instance to a User Plane Function (UPF) entity so that the UPF entity performs resource allocation on the target network instance.

In a second aspect, an embodiment of the present application provides a slice resource allocation method, which is applied to a user plane function UPF entity, and includes:

receiving parameters of a target network instance sent by a Session Management Function (SMF) entity, wherein the target network instance corresponds to single network slice selection auxiliary information (S-NSSAI) of a terminal service, the target network instance is determined by the SMF entity according to a pre-acquired mapping table, and the mapping table is provided with a corresponding relation between the network instance and the S-NSSAI;

and carrying out resource allocation on the target network instance corresponding to the parameters of the target network instance.

In a third aspect, an embodiment of the present application provides an SMF entity, including a memory, a transceiver, a processor:

a memory for storing a computer program; a transceiver for transceiving data under control of the processor; a processor for reading the computer program in the memory and performing the following operations:

In a fourth aspect, an embodiment of the present application provides a UPF entity, including a memory, a transceiver, a processor:

In a fifth aspect, an embodiment of the present application provides a slice resource allocation apparatus, which is applied to a session management function SMF entity, and includes:

the system comprises a determining module, a judging module and a judging module, wherein the determining module is used for determining a target network instance corresponding to single network slice selection auxiliary information S-NSSAI of a terminal service according to a mapping table acquired in advance, and the mapping table is provided with a corresponding relation between the network instance and the S-NSSAI;

and the sending module is used for sending the parameters of the target network instance to a User Plane Function (UPF) entity so that the UPF entity can carry out resource allocation on the target network instance.

In a sixth aspect, an embodiment of the present application provides a slice resource allocation apparatus, which is applied to a user plane function UPF entity, and includes:

a receiving module, configured to receive a parameter of a target network instance sent by a session management function SMF entity, where the target network instance corresponds to single network slice selection auxiliary information S-NSSAI of a terminal service, and the target network instance is determined by the SMF entity according to a pre-obtained mapping table, where a correspondence relationship between the network instance and the S-NSSAI is set in the mapping table;

and the resource allocation module is used for allocating resources to the target network instance corresponding to the parameters of the target network instance.

In a seventh aspect, this application provides a processor-readable storage medium, which stores a computer program for causing a processor to execute the method of the first aspect or the second aspect.

According to the slice resource allocation method, the SMF entity, the UPF entity and the storage medium provided by the embodiment of the application, the target network instance corresponding to the S-NSSAI of the terminal service is determined according to the corresponding relation between the network instance and the S-NSSAI in the mapping table, the parameter of the target network instance is sent to the UPF entity, and the UPF entity allocates the resource to the target network instance, so that the S-NSSAI is mapped to the network instance, and the UPF entity performs slice distinguishing and isolating by using the network instance, so that a plurality of slices can be simultaneously operated on one UPF entity, and the problem that the plurality of slices cannot be simultaneously operated due to the fact that the UPF entity cannot distinguish and identify the slices in the prior art is solved.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be 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 application, and other drawings can be obtained by those skilled in the art without creative efforts.

Fig. 1 is a flowchart illustrating steps of a slice resource allocation method applied to an SMF entity in an embodiment of the present application;

fig. 2 is a flowchart illustrating the steps of a slice resource allocation method applied to a UPF entity in an embodiment of the present application;

fig. 3 is one of schematic interaction diagrams between an SMF entity and a UPF entity in an embodiment of the present application;

fig. 4 is a second schematic diagram of interaction between an SMF entity and a UPF entity in the embodiment of the present application;

fig. 5 is a third schematic diagram illustrating interaction between an SMF entity and a UPF entity in an embodiment of the present application;

fig. 6 is a schematic structural diagram of an SMF entity in an embodiment of the present application;

FIG. 7 is a schematic structural diagram of a UPF entity in an embodiment of the present application;

fig. 8 is a block diagram of a slice resource allocation apparatus applied to an SMF entity in the embodiment of the present application;

fig. 9 is a block diagram of a slice resource allocation apparatus applied to a UPF entity in an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

The solution proposed at present for supporting multi-slice sharing for a UPF entity is to pre-configure slice information S-NSSAI on the UPF entity, and register this information on a Network Function database Function (NRF). When a Session Management Function (SMF entity) performs UPF entity selection, the SMF entity queries UPF entity information on the NRF and selects a UPF entity that can support a corresponding slice (S-NSSAI). The SMF entity sends a PFCP Session Establishment Request message to the UPF entity, wherein the message carries slice information (S-NSSAI). And the UPF entity performs operations such as resource allocation and isolation according to the slice information.

However, the solution described above is premised on the requirement that the UPF entity be able to identify the slice information represented by the S-NSSAI. However, in the prior art, the slice information sent by the SMF entity to the UPF entity is only used for the performance measurement and is not used for distinguishing and identifying the slice. That is, the UPF entity does not currently have this identification capability. Therefore, the proposed solution does not solve the problem of multiple slices running simultaneously.

Therefore, the embodiments of the present application provide a slice resource allocation method, an SMF entity, a UPF entity, and a storage medium, so as to solve the problem that the existing UPF entity cannot run multiple slices simultaneously.

The method and the device are based on the same application concept, and because the principles of solving the problems of the method and the device are similar, the implementation of the device and the method can be mutually referred, and repeated parts are not repeated.

The technical scheme provided by the embodiment of the application can be suitable for various systems, particularly 5G systems. For example, the applicable system may be a global system for mobile communication (GSM) system, a Code Division Multiple Access (CDMA) system, a Wideband Code Division Multiple Access (WCDMA) General Packet Radio Service (GPRS) system, a long term evolution (long term evolution, LTE) system, an LTE Frequency Division Duplex (FDD) system, an LTE Time Division Duplex (TDD) system, an LTE-a (long term evolution) system, a universal mobile system (universal mobile telecommunications system, UMTS), a Worldwide Interoperability for Mobile Access (WiMAX) system, a New Radio network (NR 5) system, etc. These various systems include terminal devices and network devices. The System may further include a core network portion, such as an Evolved Packet System (EPS), a 5G System (5GS), and the like.

The terminal device referred to in the embodiments of the present application may refer to a device providing voice and/or data connectivity to a user, a handheld device having a wireless connection function, or another processing device connected to a wireless modem. In different systems, the names of the terminal devices may be different, for example, in a 5G system, the terminal device may be called a User Equipment (UE). A wireless terminal device, which may be a mobile terminal device such as a mobile telephone (or "cellular" telephone) and a computer having a mobile terminal device, for example, a portable, pocket, hand-held, computer-included, or vehicle-mounted mobile device, may communicate with one or more Core Networks (CNs) via a Radio Access Network (RAN). Examples of such devices include Personal Communication Service (PCS) phones, cordless phones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, and Personal Digital Assistants (PDAs). The wireless terminal device may also be referred to as a system, a subscriber unit (subscriber unit), a subscriber station (subscriber station), a mobile station (mobile station), a remote station (remote station), an access point (access point), a remote terminal (remote terminal), an access terminal (access terminal), a user terminal (user terminal), a user agent (user agent), and a user device (user device), which is not limited in this embodiment. Since the terminal device forms a network capable of supporting communication with other network devices (e.g., a core network device, an access network device (i.e., a base station)), the terminal device is also considered as a network device in the present invention.

Furthermore, it should be appreciated that reference throughout this specification to "one embodiment" or "an embodiment" means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present application. Thus, the appearances of the phrases "in one embodiment" or "in an embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

The present application is explained in detail below.

As shown in fig. 1, a flowchart of steps of a slice resource allocation method applied to an SMF entity in the embodiment of the present application is shown, where the method includes the following steps:

step 101: and determining a target network instance corresponding to the S-NSSAI of the terminal service according to a mapping table acquired in advance.

Specifically, the definition of the Network Instance (Network Instance) is "Information identification domain, used by the UPF for traffic detection and routing", that is, the Network Instance is used by the UPF entity for traffic detection and routing, and can be issued to the UPF entity by the SMF entity.

Specifically, a mapping table obtained by the SMF entity in advance is provided with a correspondence between the network instance and the S-NSSAI, and the mapping between the S-NSSAI and the network instance can be realized by the correspondence. Specifically, the correspondence relationship can be shown in the following table:

S-NSSAI	network example
		A	A: access Point 1(APN1), APN2
B	B：APN1，APN2
		C	C：APN1，APN2

In this step, the SMF entity may determine the target network instance corresponding to the S-NSSAI of the terminal service based on the correspondence between the network instance and the S-NSSAI in the mapping table, thereby implementing mapping between the S-NSSAI and the target network instance.

In addition, it should be noted that when the SMF entity acquires the S-NSSAI of the terminal service, the SMF entity determines a target network instance corresponding to the S-NSSAI of the terminal service, that is, if the SMF entity acquires the S-NSSAI of the terminal service, the S-NSSAI of the terminal service is mapped to the target network instance.

Step 102: and sending the parameters of the target network instance to the UPF entity.

In this step, specifically, the SMF entity sends the parameters of the target network instance to the UPF entity, so that the UPF entity performs resource allocation on the target network instance, and mapping, identification, differentiation, and isolation of slices by the UPF entity using the network instance are achieved, thereby achieving that multiple slices can be simultaneously run on one UPF entity.

Specifically, the parameter of the network instance is information of the network instance itself, that is, information used for traffic detection and routing, such as access point information. The parameters of the target network instance at this point are the target network instance's own information.

The SMF entity in this embodiment determines a target network instance corresponding to the S-NSSAI of the terminal service according to a correspondence between the network instance and the S-NSSAI in the mapping table, and sends a parameter of the target network instance to the UPF entity, and the UPF entity performs resource allocation on the target network instance, so that the S-NSSAI is mapped to the network instance, and the UPF entity performs slicing differentiation and isolation using the network instance, thereby implementing that multiple slices can be simultaneously run on one UPF entity, and solving the problem that multiple slices cannot be simultaneously run due to the fact that the UPF entity cannot differentiate and identify the slices in the prior art.

Optionally, in this embodiment, the mapping table further sets a corresponding relationship between the network instance and the required resource configuration of the network instance, and at this time, this embodiment may further determine the required resource configuration of the target network instance according to the mapping table, and then send the required resource configuration of the target network instance to the UPF entity.

Specifically, the required resource configuration of the network instance may include CPU, storage, bandwidth, delay, etc., which is not specifically limited herein.

Further, when the correspondence between the network instance and the required resource configuration of the network instance is set in the mapping table, there is a correspondence between the S-NSSAI, the network instance, and the required resource configuration of the network instance in the mapping table.

The mapping table may now be as follows:

S-NSSAI	network example	Required resource allocation
			A	A：APN1，APN2	CPU:30％
B	B：APN1，APN2	CPU:40％
			C	C：APN1，APN2	CPU:30％

Through the corresponding relation in the mapping table, the SMF entity can determine the target network instance corresponding to the S-NSSAI of the terminal service and the required resource configuration of the target network instance, and can send the required resource configuration of the target network instance to the UPF entity, so that the UPF entity can allocate resources to the target network instance based on the required resource configuration of the target network instance, and further, the resource allocation to the target network instance can meet the resource requirement of the target network instance while the slicing differentiation and isolation are realized.

In addition, optionally, in this embodiment, before determining, according to a mapping table obtained in advance, a target network instance corresponding to the S-NSSAI of the terminal service, the SMF entity further needs to obtain the mapping table, that is, in this embodiment, any one of the following operations needs to be performed to obtain the mapping table:

first, the SMF entity configures itself to obtain a mapping table.

In this way, the SMF entity can be preconfigured with the mapping table and stored locally.

It should be noted that, of course, the mapping table may be configured by another platform such as operation, maintenance, administration (OAM) or the like, and this is not particularly limited herein.

Specifically, after the SMF entity configures the mapping table, the mapping table may be sent to the UPF entity through a Packet Forwarding Control Protocol (PFCP) association establishment request message or a PFCP association establishment response message, so that the UPF entity can know the corresponding relationship between the S-NSSAI and the network instance, or the corresponding relationship between the S-NSSAI, the network instance, and the required resource configuration of the network instance.

Specifically, if the SMF entity initiates a PFCP Association Setup Request (PFCP Association Setup Request) message, the mapping table may be included in the PFCP Association Setup Request message and sent to the UPF entity; if the UPF entity initiates a PFCP Association Setup Request message to the SMF entity, the mapping table may be included in a PFCP Association Setup Response (PFCP Association Setup Response) message fed back by the SMF entity and sent to the UPF entity.

Of course, after the UPF entity receives the mapping table, the mapping table may be stored locally; in addition, if the mapping table of the SMF entity is already stored in the UPF entity before, the mapping table corresponding to the stored SMF entity is updated to ensure consistency between the mapping table stored in the UPF entity and the mapping table stored in the SMF entity.

And secondly, receiving terminal IP address pool information parameters sent by the UPF entity, wherein the terminal IP address pool information parameters comprise a mapping table.

Specifically, in this manner, the UPF entity may set the mapping table, and send the mapping table to the SMF entity through a terminal IP address Pool Information parameter (UE IP address Pool Information IE), so that the SMF entity can map the S-NSSAI required by the service to the target network instance through the mapping table.

In addition, specifically, the receiving, by the SMF entity, the terminal IP address pool information parameter sent by the UPF entity may include any one of the following:

(1) the method comprises the steps of sending a first PFCP association establishment request message to a UPF entity, and receiving a PFCP association establishment response message sent by the UPF entity based on the first PFCP association establishment request message.

Specifically, the PFCP association establishment response message carries the terminal IP address pool information parameter.

That is, when the SMF entity initiates a PFCP association establishment request message to the UPF entity, the terminal IP address pool information parameter may be sent to the SMF entity through a PFCP association establishment response message returned by the UPF entity.

(2) And receiving a second PFCP association establishment request message sent by the UPF entity.

Specifically, the second PFCP association establishment request message carries the terminal IP address pool information parameter.

That is, when the UPF entity initiates a PFCP association establishment request message to the SMF entity, the UPF entity may send the terminal IP address pool information parameter to the SMF entity through a second PFCP association establishment request message.

(3) And receiving a PFCP association update request message sent by the UPF entity.

Specifically, a PFCP Association Update request (PFCP Association Update request) message carries a terminal IP address pool information parameter.

That is, when the UPF entity initiates a PFCP association update request message to the SMF entity, the UPF entity may send the terminal IP address pool information parameter to the SMF entity through the PFCP association update request message.

The UPF entity sends the terminal IP address pool information parameter containing the mapping table to the SMF entity through any message, so that the SMF entity can realize the mapping between the S-NSSAI of the terminal service and the network instance.

Thus, the mapping table can be obtained by the SMF entity configuring or receiving the terminal IP address pool information parameter sent by the UPF entity, thereby realizing the mapping between the S-NSSAI and the network instance, or the mapping between the S-NSSAI, the network instance and the required resource configuration of the network instance.

In addition, optionally, in this embodiment, when the SMF entity sends the parameter of the target network instance to the UPF entity, the parameter of the target network instance may be sent to the UPF entity through a PFCP session establishment request message or a PFCP session modification request message.

That is, when a Session needs to be established or modified, the SMF entity sends a PFCP Session Establishment Request (PFCP Session Establishment Request) message or a PFCP Session Modification Request (PFCP Session Modification Request) message to the UPF entity, and includes parameters of a target network instance corresponding to the S-NSSAI of a service in the message and sends the parameters to the UPF entity.

In addition, specifically, when the SMF entity sends the required resource configuration of the target network instance to the UPF entity, the required resource configuration of the target network instance may also be sent to the UPF entity through a PFCP session establishment request message or a PFCP session modification request message.

That is, at this time, the required resource configuration of the target network instance corresponding to the S-NSSAI of the service may be sent to the UPF entity through the PFCP session establishment request message or the PFCP session modification request message, so that the UPF entity may perform resource allocation on the target network instance based on this, and implement slice differentiation and isolation.

In addition, after the UPF entity performs resource allocation on the target network instance, at this time, the SMF entity may further perform any one of the following operations:

first, receiving a PFCP session establishment response message sent by the UPF entity based on the PFCP session establishment request message.

Specifically, if the SMF entity sends a PFCP session establishment request message to the UPF entity, the UPF entity feeds back a PFCP session establishment response message to the SMF entity, and at this time, the SMF entity receives the PFCP session establishment response message.

When the UPF entity cannot meet the resource configuration requirement of the target network instance, the PFCP session establishment response message includes a cause value, where the cause value is that slice resources are insufficient, so that the SMF entity can know the reason why the resource configuration requested by the SMF entity cannot be implemented on the UPF entity, and at this time, the SMF entity may determine a reason for session establishment failure based on the cause value, or determine to establish a session of another type, or determine to switch the terminal service to a slice corresponding to another S-NSSAI.

And secondly, receiving a PFCP session modification response message sent by the UPF entity based on the PFCP session modification request message.

Specifically, if the SMF entity sends a PFCP session modification request message to the UPF entity, the UPF entity feeds back a PFCP session modification response message to the SMF entity, and at this time, the SMF entity receives the PFCP session modification response message.

When the UPF entity cannot meet the resource configuration requirement of the target network instance, the PFCP session modification response message includes a cause value, where the cause value is that slice resources are insufficient, so that the SMF entity can know the reason why the resource configuration requested by the SMF entity cannot be implemented on the UPF entity, and at this time, the SMF entity may determine the reason for the session modification failure based on the cause value.

In this way, the session establishment or modification process is used to implement sending the target network instance or both the target network instance and the required resource configuration of the target network instance to the UPF entity, so that the UPF entity can perform resource allocation on the target network instance, where the resource allocation may include CPU, storage, bandwidth or delay.

In the slice resource allocation method provided by this embodiment, the SMF entity determines the target network instance corresponding to the S-NSSAI of the terminal service according to the correspondence between the network instance and the S-NSSAI in the mapping table, and sends the parameter of the target network instance to the UPF entity, and the UPF entity performs resource allocation on the target network instance, so that by mapping the S-NSSAI to the network instance, and the UPF entity performs slice differentiation and isolation by using the network instance, multiple slices can be simultaneously run on one UPF entity, and the problem that multiple slices cannot be simultaneously run due to the fact that the UPF entity cannot differentiate and identify the slices in the prior art is solved.

In addition, as shown in fig. 2, a flowchart of the steps of the slice resource allocation method applied to the UPF entity in the embodiment of the present application is shown, where the method includes the following steps:

step 201: and receiving the parameters of the target network instance sent by the SMF entity.

Specifically, the target network instance corresponds to the S-NSSAI of the terminal service, and the target network instance is determined by the SMF entity according to a mapping table obtained in advance, where a correspondence relationship between the network instance and the S-NSSAI is set.

Specifically, the SMF entity obtains a target network instance corresponding to the S-NSSAI of the terminal service according to the correspondence between the network instance and the S-NSSAI in the mapping table, and sends the parameter of the target network instance to the UPF entity, where the UPF entity receives the parameter of the target network instance.

Based on the corresponding relation between the S-NSSAI and the network instance, the network instance and the S-NSSAI are mapped, and the network instance is used for distinguishing and isolating the slices, so that a plurality of slices can be operated on one UPF entity at the same time.

Step 202: and carrying out resource allocation on the target network instance corresponding to the parameters of the target network instance.

Specifically, after obtaining the parameters of the target network instance sent by the SMF entity, the UPF entity may perform resource allocation on the target network instance corresponding to the parameters of the target network instance, that is, may perform resource allocation on the target network instance by referring to the information of the target network instance itself.

Specifically, the resource allocation may include CPU, memory, bandwidth or latency, and the like, which is not specifically limited herein.

Thus, the UPF entity in this embodiment, by receiving the parameters of the target network instance corresponding to the S-NSSAI of the terminal service and performing resource allocation on the target network instance, based on the correspondence between the network instance and the S-NSSAI, realizes that multiple slices can be simultaneously run on one UPF entity by mapping the S-NSSAI to the network instance and using the network instance to distinguish and isolate the slices, and solves the problem that multiple slices cannot be simultaneously run due to the fact that the UPF entity cannot distinguish and identify the slices in the prior art.

Optionally, the mapping table further includes a correspondence between the network instance and the required resource configuration of the network instance; the UPF entity in this embodiment may further receive a required resource configuration of the target network instance sent by the SMF entity, where the required resource configuration of the target network instance is determined by the SMF entity according to the mapping table.

In addition, specifically, the SMF entity may receive a mapping table configured by the UPF entity. At this time, specifically, before receiving the parameter of the target network instance sent by the SMF entity, the UPF entity may send a terminal IP address pool information parameter to the SMF entity, where the terminal IP address pool information parameter includes the mapping table.

Specifically, the sending of the terminal IP address pool information parameter to the SMF entity includes any one of the following:

(1) receiving a first PFCP association establishment request message sent by the SMF entity, and sending a PFCP association establishment response message to the SMF entity based on the first PFCP association establishment request message.

(2) And sending a second PFCP association establishment request message to the SMF entity.

(3) And sending a PFCP association update request message to the SMF entity.

Specifically, the PFCP association update request message carries the terminal IP address pool information parameter.

That is, the sending of the terminal IP address pool information parameter containing the mapping table to the SMF entity is realized by any of the above messages.

In addition, specifically, the SMF entity may be configured by itself to obtain the UPF entity. At this time, before the UPF entity receives the parameter of the target network instance sent by the SMF entity, the UPF entity may also receive a mapping table sent by a PFCP association establishment request message or a PFCP association establishment response message after the SMF entity configures the mapping table.

It should be noted that, for the relevant content of the mapping table, reference may be made to the relevant content of the SMF entity side method embodiment, and details are not described herein again.

In addition, optionally, in this embodiment, when the UPF entity performs resource allocation on the target network instance corresponding to the parameter of the target network instance, and when only the parameter of the target network instance is received, the UPF entity performs resource allocation on the target network instance according to its resource allocation; or when receiving the parameters of the target network instance and the required resource configuration of the target network instance, performing resource allocation on the target network instance according to the required resource configuration of the target network instance.

Specifically, if the UPF entity receives only the parameters of the target network instance and does not receive the required resource configuration of the target network instance, the resource allocation including CPU, storage, bandwidth, delay, etc. may be performed on the target network instance according to the network requirements and the configuration itself, thereby implementing the slice differentiation and isolation; if the UPF entity receives the parameters of the target network instance and the required resource configuration of the target network instance, the resources can be allocated to the target network instance according to the required resource configuration of the target network instance, so that the resources allocated to the target network instance can meet the resource requirement of the target network instance.

In addition, optionally, in this embodiment, when the PDF entity receives the parameters of the target network instance sent by the SMF entity, the PDF entity may receive the parameters of the target network instance sent by the SMF entity through the PFCP session establishment request message or the PFCP session modification request message.

In addition, when the PDF entity receives the required resource configuration of the target network instance sent by the SMF entity, the required resource configuration of the target network instance sent by the SMF entity through the PFCP session establishment request message or the PFCP session modification request message may be received.

In addition, after the PDF entity allocates resources to the target network instance, any one of the following operations may be performed:

sending a PFCP session establishment response message to the SMF entity based on the PFCP session establishment request message, wherein when the UPF entity cannot meet the resource configuration requirement of the target network instance, the PFCP session establishment response message contains a cause value, and the cause value is that slice resources are insufficient; alternatively, the first and second electrodes may be,

and sending a PFCP session modification response message to the SMF entity based on the PFCP session modification request message, wherein when the UPF entity cannot meet the resource configuration requirement of the target network instance, the PFCP session modification response message contains a cause value, and the cause value is that the slice resources are insufficient.

It should be noted that, for specific descriptions of the above, reference may be made to relevant contents of the SMF entity side method embodiment, and detailed descriptions are not repeated herein.

Thus, the slice resource allocation method provided in this embodiment implements mapping S-NSSAI to a network instance and performing slice differentiation and isolation using the network instance based on the correspondence between the network instance and S-NSSAI by receiving parameters of a target network instance corresponding to S-NSSAI of a terminal service and performing resource allocation on the target network instance, thereby implementing that multiple slices can be simultaneously run on one UPF entity, and solving the problem that multiple slices cannot be simultaneously run due to the inability of distinguishing and identifying slices by the UPF entity in the prior art.

The present application will be specifically described below with reference to specific examples.

In the first embodiment, the SMF entity configures a mapping table, and the mapping table has a correspondence relationship between the network instance and the S-NSSAI:

as shown in fig. 3, the overall process of slice resource allocation is as follows:

step 1, the SMF entity pre-configures the corresponding relation between the Network Instance and the S-NSSAI, obtains a mapping table and stores the mapping table in the local. Specifically, the configuration operation of the mapping table may be directly performed on the SMF entity, or may be performed through other platforms such as OAM, which is not specifically limited herein.

Step 2, optionally, the SMF entity may send the mapping table to the UPF entity through a PFCP Association Setup Request message or a PFCP Association Setup Response message. Specifically, if the message is a PFCP Association Setup Request message initiated by the SMF entity, the mapping table is included in the message; if the message is the PFCP Association Setup Request message initiated by the UPF entity, the mapping table is included in the PFCP Association Setup Response message returned by the SMF entity to the UPF entity.

Step 3, the UPF entity stores the mapping table in the local; and if the UPF entity has the mapping table of the SMF entity which is stored previously, updating the stored mapping table.

And step 4, when the Session needs to be established or modified, the SMF entity sends a PFCPSession Establishment Request message or a PFCP Session Modification Request message to the UPF entity, maps the S-NSSAI required by the service into a target network instance according to the mapping table, and includes the target network instance in the message.

And 5, the UPF entity performs resource allocation including CPU, storage, bandwidth, delay and the like on the target network instance according to the network requirement and self configuration.

And 6, the UPF entity returns a PFCP Session Establishment Response message or a PFCP Session Modification Response message to the SMF entity.

Therefore, the resource allocation of the target network instance is completed, so that the slicing differentiation and isolation are realized by using the network instance, and a plurality of slices can be simultaneously operated on one UPF entity.

In a second embodiment, the SMF entity configures a mapping table, and the mapping table is provided with a correspondence relationship between the network instance, the S-NSSAI, and the required resource configuration of the network instance:

as shown in fig. 4, the overall process of slice resource allocation is as follows:

step 1, the SMF entity pre-configures the corresponding relation among the network instance, the S-NSSAI and the required resource configuration of the network instance, obtains a mapping table and stores the mapping table in the local. Specifically, the configuration operation of the mapping table may be directly performed on the SMF entity, or may be performed through other platforms such as OAM, which is not specifically limited herein.

And step 4, when the Session needs to be established or modified, the SMF entity sends a PFCP Session Establishment Request message or a PFCP Session Modification Request message to the UPF entity, maps the S-NSSAI required by the service into a target network instance according to the mapping table, and includes the target network instance in the message. Optionally, the message may also include the required resource configuration of the target network instance.

And step 5, the UPF entity performs resource allocation including CPU, storage, bandwidth, delay and the like on the target network instance according to the target network instance sent by the SMF entity and the required resource allocation of the target network instance.

And 6, the UPF entity returns a PFCP Session Establishment Response message or a PFCP Session Modification Response message to the SMF entity. If the resource configuration requested by the SMF entity cannot be implemented on the UPF entity due to resource restriction and the like, the UPF entity needs to carry a Cause value of "insufficient slice resources" in the Cause in the message. It should be noted that this Cause value is merely an example, and other expression Cause values indicating that slice resources are insufficient may also be carried in the Cause, which is not specifically limited herein.

In a third embodiment, a mapping table is configured for a UPF entity, and the mapping table is provided with a corresponding relationship between a network instance and an S-NSSAI, or a corresponding relationship between the network instance, the S-NSSAI, and a required resource configuration of the network instance:

as shown in fig. 5, in this case, the overall process of slice resource allocation is as follows:

step 1, the UPF entity pre-configures the corresponding relationship between the network instance and the S-NSSAI, or the corresponding relationship between the network instance, the S-NSSAI and the required resource configuration of the network instance, obtains a mapping table and stores the mapping table locally. Specifically, the configuration operation of the mapping table may be directly performed on the UPF entity, or may be performed through other platforms such as OAM, which is not specifically limited herein.

And step 2, sending the mapping table to the SMF entity through a terminal IP address Pool Information parameter (UE IP address Pool Information IE).

Specifically, the existing UE IP address Pool Information IE Information is shown in the following table:

the existing UE IP address Pool Information IE does not consider the corresponding relationship in the mapping table, but in the present application, each UE IP address Pool Information IE may include the mapping table. Certainly, the UE IP address Pool Information IE further includes the UE IP address Pool divided into the SMF entity.

In addition, when a PFCP Association Setup or a PFCP Association Update procedure initiated by an UPF entity is performed between an SMF entity and an UPF entity, the UPF entity may carry a UE IP address Pool Information IE (may carry multiple) in any of the following messages:

(1) the UPF entity returns a PFCP Association Setup response message after the SMF entity initiates the PFCP Association Setup request;

(2) a PFCP Association Setup request message initiated by the UPF entity;

(3) the PFCP Association Update request message initiated by the UPF entity.

And step 3, when the Session needs to be established or modified, the SMF entity sends a PFCP Session Establishment Request message or a PFCP Session Modification Request message to the UPF entity, maps the S-NSSAI required by the service into a target network instance according to the mapping table, and includes the target network instance in the message. Optionally, the message may also include the required resource configuration of the target network instance.

And 4, the UPF entity performs resource allocation including CPU, storage, bandwidth, delay and the like on the target network instance according to the target network instance sent by the SMF entity. If the SMF entity simultaneously sends the required resource configuration of the target network instance, the resource allocation can be carried out on the target network instance according to the configuration; specifically, if the required resource configuration of the target network instance is not configured or the available resource is insufficient in the UPF entity at this time, the UPF entity may perform resource allocation according to the network condition and the configuration itself.

And step 5, the UPF entity returns a PFCP Session Establishment Response message or a PFCP Session Modification Response message to the SMF entity. If the resource configuration requested by the SMF entity cannot be implemented on the UPF entity due to resource restriction and the like, the UPF entity needs to carry a Cause value of "insufficient slice resources" in the Cause in the message.

Therefore, the resource allocation of the target network instance is completed, and the slicing differentiation and isolation are realized by using the network instance, so that a plurality of slices can be simultaneously operated on one UPF entity.

Fig. 6 is a schematic structural diagram of a slice resource allocation apparatus according to an embodiment of the present disclosure, which includes a memory 620, a transceiver 600, and a processor 610.

Wherein in fig. 6, the bus architecture may include any number of interconnected buses and bridges, with one or more processors, represented by processor 610, and various circuits, represented by memory 620, being linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 600 may be a number of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium including wireless channels, wired channels, fiber optic cables, and the like. The processor 610 is responsible for managing the bus architecture and general processing, and the memory 620 may store data used by the processor 610 in performing operations.

The processor 610 may be a Central Processing Unit (CPU), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), or a Complex Programmable Logic Device (CPLD), and may also have a multi-core architecture.

A memory 620 for storing a computer program; a transceiver 600 for transceiving data under the control of the processor; a processor 610 for reading the computer program in the memory and performing the following operations:

Optionally, the mapping table further includes a correspondence between the network instance and the required resource configuration of the network instance;

the slice resource allocation method further comprises:

determining the required resource configuration of the target network instance according to the mapping table;

and sending the required resource configuration of the target network instance to the UPF entity.

Optionally, the method further comprises:

the SMF entity configures the mapping table; or receiving a terminal IP address pool information parameter sent by the UPF entity, wherein the terminal IP address pool information parameter comprises the mapping table.

Optionally, the receiving of the terminal IP address pool information parameter sent by the UPF entity includes any one of the following:

sending a first message forwarding control protocol (PFCP) association establishment request message to the UPF entity, and receiving a PFCP association establishment response message sent by the UPF entity based on the first PFCP association establishment request message, wherein the PFCP association establishment response message carries the terminal IP address pool information parameter;

receiving a second PFCP association establishment request message sent by the UPF entity, wherein the second PFCP association establishment request message carries the terminal IP address pool information parameter;

and receiving a PFCP association update request message sent by the UPF entity, wherein the PFCP association update request message carries the terminal IP address pool information parameter.

Optionally, after the configuring obtains the mapping table, the method further includes:

and sending the mapping table to the UPF entity through a PFCP association establishment request message or a PFCP association establishment response message.

Optionally, the sending the parameter of the target network instance to a user plane function UPF entity includes:

and sending the parameters of the target network instance to the UPF entity through a PFCP session establishment request message or a PFCP session modification request message.

Optionally, the sending the required resource configuration of the target network instance to the UPF entity includes:

and sending the required resource configuration of the target network instance to the UPF entity through the PFCP session establishment request message or the PFCP session modification request message.

Optionally, the method further comprises:

receiving a PFCP session establishment response message sent by the UPF entity based on the PFCP session establishment request message, wherein the PFCP session establishment response message contains a cause value, and the cause value is that slice resources are insufficient; alternatively, the first and second electrodes may be,

receiving a PFCP session modification response message sent by the UPF entity based on the PFCP session modification request message, wherein the PFCP session modification response message contains a cause value, and the cause value is that slice resources are insufficient.

It should be noted that the SMF entity can implement all method steps of the embodiment of the SMF entity method side, and can achieve the same technical effect, which is not described herein again.

Fig. 7 is a schematic structural diagram of a UPF entity according to an embodiment of the present application, which includes a memory 720, a transceiver 700, and a processor 710.

Wherein in fig. 7 the bus architecture may comprise any number of interconnected buses and bridges, with one or more processors, represented by processor 710, and various circuits, represented by memory 720, being linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 700 may be a number of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium including wireless channels, wired channels, fiber optic cables, and the like. The processor 710 is responsible for managing the bus architecture and general processing, and the memory 720 may store data used by the processor 710 in performing operations.

The processor 710 may be a Central Processing Unit (CPU), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), or a Complex Programmable Logic Device (CPLD), and may also have a multi-core architecture.

A memory 720 for storing a computer program; a transceiver 700 for transceiving data under the control of the processor; a processor 710 for reading the computer program in the memory and performing the following operations:

the slice resource allocation method further comprises:

receiving a required resource configuration of the target network instance sent by the SMF entity, wherein the required resource configuration of the target network instance is determined by the SMF entity according to the mapping table.

Optionally, the resource allocation for the target network instance corresponding to the parameter of the target network instance includes:

when only the parameters of the target network instance are received, the UPF entity carries out resource allocation on the target network instance according to self resource configuration; alternatively, the first and second electrodes may be,

and when the parameters of the target network instance and the required resource configuration of the target network instance are received, carrying out resource allocation on the target network instance according to the required resource configuration of the target network instance.

Optionally, before the receiving the target network instance sent by the session management function SMF entity, the method further includes:

and sending a terminal IP address pool information parameter to the SMF entity, wherein the terminal IP address pool information parameter comprises the mapping table.

Optionally, the sending the terminal IP address pool information parameter to the SMF entity includes any one of:

receiving a first Packet Forwarding Control Protocol (PFCP) association establishment request message sent by the SMF entity, and sending a PFCP association establishment response message to the SMF entity based on the first PFCP association establishment request message, wherein the PFCP association establishment response message carries the terminal IP address pool information parameter;

sending a second PFCP association establishment request message to the SMF entity, wherein the second PFCP association establishment request message carries the terminal IP address pool information parameter;

and sending a PFCP association update request message to the SMF entity, wherein the PFCP association update request message carries the terminal IP address pool information parameter.

and receiving the mapping table sent by a PFCP association establishment request message or a PFCP association establishment response message after the SMF entity configures the mapping table.

Optionally, the receiving a target network instance sent by the session management function SMF entity includes:

receiving parameters of the target network instance sent by the SMF entity through a PFCP session establishment request message or a PFCP session modification request message.

Optionally, the receiving the required resource configuration of the target network instance sent by the SMF entity includes:

receiving the required resource configuration of the target network instance sent by the SMF entity through a PFCP session establishment request message or a PFCP session modification request message.

Optionally, the method further comprises:

sending a PFCP session establishment response message to the SMF entity based on the PFCP session establishment request message, wherein when the UPF entity cannot meet the resource configuration requirement of the target network instance, the PFCP session establishment response message contains a cause value, and the cause value is that slice resources are insufficient; alternatively, the first and second liquid crystal display panels may be,

and sending a PFCP session modification response message to the SMF entity based on the PFCP session modification request message, wherein when the UPF entity cannot meet the resource configuration requirement of the target network instance, the PFCP session modification response message contains a cause value, and the cause value is that slice resources are insufficient.

It should be noted that the UPF entity can implement all method steps of the UPF entity method side embodiment, and can achieve the same technical effect, and details are not described herein again.

Fig. 8 is a block diagram of a slice resource allocation apparatus according to an embodiment of the present application, where the apparatus includes:

a determining module 801, configured to determine, according to a mapping table obtained in advance, a target network instance corresponding to single network slice selection auxiliary information S-NSSAI of a terminal service, where a correspondence relationship between a network instance and the S-NSSAI is set in the mapping table;

a sending module 802, configured to send the parameter of the target network instance to a user plane function UPF entity, so that the UPF entity performs resource allocation on the target network instance.

the determining module is further configured to determine a required resource configuration of the target network instance according to the mapping table;

the sending module is further configured to send the required resource configuration of the target network instance to the UPF entity.

Optionally, the method further comprises:

the configuration module is used for configuring the mapping table; alternatively, the first and second electrodes may be,

and the first receiving module is used for receiving the terminal IP address pool information parameter sent by the UPF entity, wherein the terminal IP address pool information parameter comprises the mapping table.

Optionally, the first receiving module is configured to perform any one of the following:

Optionally, after the SMF entity configures the mapping table, the method further includes:

a sending unit, configured to send the mapping table to the UPF entity through a PFCP association establishment request message or a PFCP association establishment response message.

Optionally, the sending module is specifically configured to send the parameter of the target network instance to the UPF entity through a PFCP session establishment request message or a PFCP session modification request message.

Optionally, the sending module is specifically configured to send the required resource configuration of the target network instance to the UPF entity through the PFCP session establishment request message or the PFCP session modification request message.

Optionally, the method further comprises:

a second receiving module, configured to receive a PFCP session establishment response message sent by the UPF entity based on the PFCP session establishment request message, where the PFCP session establishment response message includes a cause value, and the cause value is that slice resources are insufficient; alternatively, the first and second electrodes may be,

a third receiving module, configured to receive a PFCP session modification response message sent by the UPF entity based on the PFCP session modification request message, where the PFCP session modification response message includes a cause value, and the cause value is that slice resources are insufficient.

Fig. 9 is a block diagram of a slice resource allocation apparatus according to an embodiment of the present application, where the apparatus includes:

a receiving module 901, configured to receive a parameter of a target network instance sent by a session management function SMF entity, where the target network instance corresponds to single network slice selection auxiliary information S-NSSAI of a terminal service, and the target network instance is determined by the SMF entity according to a pre-obtained mapping table, where a corresponding relationship between the network instance and the S-NSSAI is set in the mapping table;

a resource allocation module 902, configured to allocate resources to the target network instance corresponding to the parameter of the target network instance.

the receiving module is configured to receive the required resource configuration of the target network instance sent by the SMF entity, where the required resource configuration of the target network instance is determined by the SMF entity according to the mapping table.

Optionally, the resource allocation module is configured to,

when only the parameters of the target network instance are received, the UPF entity carries out resource allocation on the target network instance according to self resource configuration; or when receiving the parameters of the target network instance and the required resource configuration of the target network instance, performing resource allocation on the target network instance according to the required resource configuration of the target network instance.

Optionally, before receiving the parameter of the target network instance sent by the session management function SMF entity, the method further includes:

a first sending module, configured to send a terminal IP address pool information parameter to the SMF entity, where the terminal IP address pool information parameter includes the mapping table.

Optionally, the first sending module is configured to perform any one of:

Optionally, the method further comprises:

a receiving unit, configured to receive the mapping table sent by a PFCP association establishment request message or a PFCP association establishment response message after the SMF entity configures the mapping table.

Optionally, the receiving module is specifically configured to receive the parameter of the target network instance sent by the SMF entity through a PFCP session establishment request message or a PFCP session modification request message.

Optionally, the receiving module is specifically configured to receive the required resource configuration of the target network instance, where the required resource configuration is sent by the SMF entity through a PFCP session establishment request message or a PFCP session modification request message.

Optionally, the method further comprises:

a second sending module, configured to send a PFCP session establishment response message to the SMF entity based on the PFCP session establishment request message, where when the UPF entity cannot meet the resource configuration requirement of the target network instance, the PFCP session establishment response message includes a cause value, and the cause value is that slice resources are insufficient; alternatively, the first and second electrodes may be,

a third sending module, configured to send a PFCP session modification response message to the SMF entity based on the PFCP session modification request message, where when the UPF entity cannot meet the resource configuration requirement of the target network instance, the PFCP session modification response message includes a cause value, and the cause value is that slice resources are insufficient.

It should be noted that the division of the unit in the embodiment of the present application is schematic, and is only a logic function division, and there may be another division manner in actual implementation. In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented as a software functional unit and sold or used as a stand-alone product, may be stored in a processor readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, a network device, or the like) or a processor (processor) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

It should be noted that the apparatus provided in the embodiment of the present application can implement all the method steps implemented by the method embodiment and achieve the same technical effect, and detailed descriptions of the same parts and beneficial effects as the method embodiment in this embodiment are omitted here.

On the other hand, the embodiment of the present application further provides a processor-readable storage medium, where a computer program is stored, and the computer program is used to enable the processor to execute the method described in the foregoing embodiment.

The processor-readable storage medium can be any available medium or data storage device that can be accessed by a processor, including, but not limited to, magnetic memory (e.g., floppy disks, hard disks, magnetic tape, magneto-optical disks (MOs), etc.), optical memory (e.g., CDs, DVDs, BDs, HVDs, etc.), and semiconductor memory (e.g., ROMs, EPROMs, EEPROMs, non-volatile memory (NAND FLASH), Solid State Disks (SSDs)), etc.

As seen from the above embodiments, a processor-readable storage medium stores a computer program for causing the processor to execute the above slice resource allocation method.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer-executable instructions. These computer-executable instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These processor-executable instructions may also be stored in a processor-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the processor-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These processor-executable instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims

1. A slice resource allocation method is applied to a Session Management Function (SMF) entity, and is characterized by comprising the following steps:

2. The slice resource allocation method according to claim 1, wherein the mapping table further has a correspondence between network instances and required resource configurations of the network instances;

the slice resource allocation method further comprises:

3. The slice resource allocation method according to claim 1 or 2, further comprising:

the SMF entity configures to obtain the mapping table; alternatively, the first and second electrodes may be,

and receiving a terminal IP address pool information parameter sent by the UPF entity, wherein the terminal IP address pool information parameter comprises the mapping table.

4. The slice resource allocation method according to claim 3, wherein the receiving of the terminal IP address pool information parameter sent by the UPF entity includes any one of:

5. The slice resource allocation method according to claim 3, wherein after the SMF entity configures the mapping table, the method further comprises:

6. The method according to claim 1, wherein the sending the parameters of the target network instance to a User Plane Function (UPF) entity comprises:

7. The method according to claim 2, wherein the sending the required resource configuration of the target network instance to the UPF entity comprises:

8. The slice resource allocation method according to claim 6 or 7, further comprising:

9. A slice resource allocation method is applied to a User Plane Function (UPF) entity, and is characterized by comprising the following steps:

10. The slice resource allocation method according to claim 9, wherein the mapping table further has a correspondence between network instances and required resource configurations of the network instances;

the slice resource allocation method further comprises:

11. The slice resource allocation method according to claim 9 or 10, wherein the allocating resources to the target network instance corresponding to the parameter of the target network instance comprises:

12. The slice resource allocation method according to claim 9 or 10, wherein the receiving the parameter of the target network instance sent by the session management function SMF entity further comprises:

13. The slice resource allocation method of claim 12, wherein the sending of the terminal IP address pool information parameter to the SMF entity comprises any one of:

14. The slice resource allocation method according to claim 9 or 10, wherein the receiving the parameter of the target network instance sent by the session management function SMF entity further comprises:

15. The slice resource allocation method of claim 9, wherein the receiving parameters of the target network instance sent by the Session Management Function (SMF) entity comprise:

16. The method of claim 10, wherein the receiving the required resource configuration of the target network instance sent by the SMF entity comprises:

17. The slice resource allocation method according to claim 15 or 16, further comprising:

18. An SMF entity, comprising a memory, a transceiver, a processor:

a memory for storing a computer program; a transceiver for transceiving data under control of the processor; a processor for reading the computer program in the memory and performing the following:

determining a target network instance corresponding to single network slice selection auxiliary information S-NSSAI of a terminal service according to a pre-acquired mapping table, wherein the mapping table is provided with a corresponding relation between the network instance and the S-NSSAI;

19. The SMF entity of claim 18, wherein the mapping table further comprises a correspondence between network instances and required resource configurations of the network instances;

the slice resource allocation method further comprises:

20. The SMF entity of claim 18 or 19, further comprising:

the SMF entity configures the mapping table; alternatively, the first and second electrodes may be,

21. The SMF entity of claim 20, wherein the receiving of the terminal IP address pool information parameter sent by the UPF entity comprises any one of:

22. The SMF entity of claim 18, wherein sending the parameters of the target network instance to a user plane function, UPF, entity comprises:

23. A UPF entity, comprising a memory, a transceiver, a processor:

24. The UPF entity of claim 23, wherein the mapping table further comprises a correspondence between network instances and required resource configurations of the network instances;

the slice resource allocation method further comprises:

25. The UPF entity according to claim 23 or 24, wherein the receiving the parameters of the target network instance sent by the session management function, SMF, entity further comprises:

26. The UPF entity of claim 23, wherein the parameters of the target network instance sent by the receiving session management function, SMF, entity comprise:

27. The UPF entity of claim 24, wherein the receiving the required resource configuration for the target network instance sent by the SMF entity comprises:

28. The UPF entity of claim 26 or 27, further comprising:

29. A slice resource allocation device applied to a Session Management Function (SMF) entity is characterized by comprising:

30. A slice resource allocation device applied to a User Plane Function (UPF) entity comprises:

a receiving module, configured to receive a parameter of a target network instance sent by a session management function SMF entity, where the target network instance corresponds to single network slice selection auxiliary information S-NSSAI of a terminal service, and the target network instance is determined by the SMF entity according to a pre-obtained mapping table, where a correspondence between the network instance and the S-NSSAI is set in the mapping table;

31. A processor-readable storage medium, characterized in that the processor-readable storage medium stores a computer program for causing a processor to execute the slice resource allocation method of any one of claims 1 to 8 or the slice resource allocation method of any one of claims 9 to 17.