Slice resource allocation method, smf entity, upf entity, and storage medium

Abstract

The embodiment of the application provides a slice resource allocation method, an SMF entity, a UPF entity and a storage medium, the method comprising: determining a target network instance corresponding to S-NSSAI of a terminal service according to a mapping table acquired in advance, wherein a corresponding relationship between a network instance and S-NSSAI is arranged in the mapping table; and sending 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 run multiple slices simultaneously.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of communication, and particularly relates to a slice resource allocation method, an SMF entity, a UPF entity and a storage medium. BACKGROUND

[0002] Slice technology is a key technology introduced by a 5th generation mobile networks (5G) network, which can realize resource and service isolation and guarantee service quality. In the current standard, a User Plane Function (UPF) can carry single network slice selection assistance information (S-NSSAI), which indicates the slice type that the UPF can support. However, the UPF can only support the running of one slice at the same time, and the S-NSSAI is only used for performance measurement, that is, the target UPF does not support the simultaneous running of multiple slices. SUMMARY

[0003] Embodiments of the present application provide a slice resource allocation method, an SMF entity, a UPF entity and a storage medium, to solve the problem that the existing UPF does not support the simultaneous running of multiple slices.

[0004] In a first aspect, embodiments of the present application provide a slice resource allocation method applied to a Session Management Function (SMF) entity, comprising:

[0005] determining a target network instance corresponding to single network slice selection assistance information (S-NSSAI) of a terminal service according to a mapping table, wherein the mapping table sets a corresponding relationship between a network instance and the S-NSSAI;

[0006] sending a 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.

[0007] In a second aspect, embodiments of the present application provide a slice resource allocation method applied to a UPF entity, comprising:

[0008] receiving a parameter of a target network instance sent by an SMF entity, wherein the target network instance corresponds to single network slice selection assistance information (S-NSSAI) of a terminal service, and the target network instance is determined by the SMF entity according to a mapping table, and the mapping table sets a corresponding relationship between a network instance and the S-NSSAI;

[0009] allocating resources to the target network instance corresponding to the parameters of the target network instance.

[0010] In a third aspect, an embodiment of the present application provides an SMF entity, comprising a memory, a transceiver, and a processor:

[0011] The memory is configured to store a computer program; the transceiver is configured to transceive data under control of the processor; and the processor is configured to read the computer program in the memory and perform the following operations:

[0012] According to a pre-acquired mapping table, determining a target network instance corresponding to single network slice selection assistance information S-NSSAI of a terminal service, wherein the mapping table sets a corresponding relationship between a network instance and the S-NSSAI;

[0013] Sending parameters of the target network instance to a user plane function UPF entity, so that the UPF entity allocates resources to the target network instance.

[0014] In a fourth aspect, an embodiment of the present application provides a UPF entity, comprising a memory, a transceiver, and a processor:

[0015] The memory is configured to store a computer program; the transceiver is configured to transceive data under control of the processor; and the processor is configured to read the computer program in the memory and perform the following operations:

[0016] 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 assistance information S-NSSAI of a terminal service, and the target network instance is determined by the SMF entity according to a pre-acquired mapping table, and the mapping table sets a corresponding relationship between a network instance and the S-NSSAI;

[0017] Allocating resources to the target network instance corresponding to the parameters of the target network instance.

[0018] In a fifth aspect, an embodiment of the present application provides a slice resource allocation apparatus, applied to a session management function SMF entity, comprising:

[0019] A determining module is configured to determine, according to a pre-acquired mapping table, a target network instance corresponding to single network slice selection assistance information S-NSSAI of a terminal service, wherein the mapping table sets a corresponding relationship between a network instance and the S-NSSAI;

[0020] A sending module is configured to send parameters of the target network instance to a user plane function UPF entity, so that the UPF entity allocates resources to the target network instance.

[0021] In a sixth aspect, an embodiment of the present application provides a slice resource allocation apparatus, applied to a user plane function (UPF) entity, comprising:

[0022] a receiving module configured to receive 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 assistance information (S-NSSAI) of a terminal service, and the target network instance is determined by the SMF entity according to a pre-acquired mapping table in which a correspondence between network instances and S-NSSAIs is set;

[0023] a resource allocation module configured to allocate resources to a target network instance corresponding to the parameters of the target network instance.

[0024] In a seventh aspect, an embodiment of the present application provides a processor-readable storage medium, which stores a computer program for causing a processor to execute the method in the first aspect or the second aspect.

[0025] The slice resource allocation method, the SMF entity, the UPF entity and the storage medium provided by the embodiments of the present application determine a target network instance corresponding to S-NSSAI of a terminal service according to the correspondence between network instances and S-NSSAIs in a mapping table, and send parameters of the target network instance to a UPF entity, so that the UPF entity allocates resources to the target network instance, which realizes mapping of S-NSSAI to network instances, and the UPF entity uses network instances to distinguish and isolate slices, thereby realizing that multiple slices can run on one UPF entity, and solving the problem that multiple slices cannot run simultaneously due to the inability of UPF entities to distinguish and identify slices in the prior art. BRIEF DESCRIPTION OF DRAWINGS

[0026] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the drawings needed in the embodiments or the prior art description will be briefly introduced. Obviously, 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 labor.

[0027] Figure 1 A step flow chart of the slice resource allocation method applied to the SMF entity in the embodiments of the present application;

[0028] Figure 2 A step flow chart of the slice resource allocation method applied to the UPF entity in the embodiments of the present application;

[0029] Figure 3Fig. 1 is a schematic diagram of interaction between an SMF entity and a UPF entity in an embodiment of the present application;

[0030] Figure 4 Fig. 2 is a schematic diagram of interaction between an SMF entity and a UPF entity in another embodiment of the present application;

[0031] Figure 5 Fig. 3 is a schematic diagram of interaction between an SMF entity and a UPF entity in still another embodiment of the present application;

[0032] Figure 6 Fig. 4 is a schematic diagram of structure of an SMF entity in an embodiment of the present application;

[0033] Figure 7 Fig. 5 is a schematic diagram of structure of a UPF entity in an embodiment of the present application;

[0034] Figure 8 Fig. 6 is a module block diagram of a slice resource allocation apparatus applied to an SMF entity in an embodiment of the present application;

[0035] Figure 9 Fig. 7 is a module block diagram of a slice resource allocation apparatus applied to a UPF entity in an embodiment of the present application. DETAILED DESCRIPTION

[0036] The technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, but not all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative work fall within the scope of protection of the present application.

[0037] The solution currently proposed for supporting multi-slice sharing of 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) selects a UPF entity, the SMF entity queries UPF entity information on the NRF and selects a UPF entity that can support the corresponding slice (S-NSSAI). The SMF entity sends a PFCP Session Establishment Request message to the UPF entity, which carries the slice information (S-NSSAI). The UPF entity performs resource configuration and isolation operations according to the slice information.

[0038] However, the premise of the above solution is that the UPF entity can 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 performance measurement and is not used for distinguishing and identifying slices. That is, the UPF entity does not have this identification capability at present. Therefore, the above proposed solution cannot solve the problem of simultaneous operation of multiple slices.

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

[0040] Among them, the method and the device are based on the same application concept. Since the principles of the method and the device for solving problems are similar, the implementation of the device and the method can be mutually referred to, and the repeated parts will not be described again.

[0041] The technical solutions provided by the embodiments of the present application can be applied to various systems, especially 5G systems. For example, the applicable systems can be global system of mobile communication (GSM) system, code division multiple access (CDMA) system, wideband code division multiple access (WCDMA) general packet radio service (GPRS) system, long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD) system, long term evolution advanced (LTE-A) system, universal mobile system (UMTS), worldwide interoperability for microwave access (WiMAX) system, 5G new radio (NR) system, etc. Among these various systems, there are terminal devices and network devices. The system can also include a core network part, such as an evolved packet system (EPS), a 5G system (5GS), etc.

[0042] The terminal device referred to in the embodiments of the present application can be a device providing voice and / or data connectivity to a user, a handheld device having wireless connection capability, or other processing devices connected to a wireless modem, etc. In different systems, the name of the terminal device can also be different, for example, in a 5G system, the terminal device can be referred to as a user equipment (UE). The wireless terminal device can communicate with one or more core networks (CN) via a radio access network (RAN). The wireless terminal device can be a mobile terminal device, such as a mobile phone (or called "cellular" phone) and a computer with a mobile terminal device, for example, it can be a portable, pocket, handheld, built-in or vehicle-mounted mobile device, which exchanges language and / or data with the radio access network. For example, personal communication service (PCS) phones, cordless phones, session initiated protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), etc. The wireless terminal device can also be referred to as a system, a subscriber unit, a subscriber station, a mobile station, a mobile, a remote station, an access point, a remote terminal, an access terminal, a user terminal, a user agent, a user device, which is not limited in the embodiments of the present application. Since the terminal device and other network devices (for example, core network devices, access network devices (i.e. base stations)) together constitute a network that can support communication, in the present application, the terminal device is also regarded as a kind of network device.

[0043] In addition, it should be understood that the "one embodiment" or "an embodiment" mentioned throughout the specification means that the specific features, structures or characteristics related to the embodiment are included in at least one embodiment of the present application. Therefore, "in one embodiment" or "in an embodiment" appearing throughout the specification does not necessarily refer to the same embodiment. In addition, these specific features, structures or characteristics can be combined in one or more embodiments in any suitable manner.

[0044] The present application will be described in detail below.

[0045] As Figure 1 shown, a step flow chart of a slice resource allocation method applied to an SMF entity in an embodiment of the present application is shown, and the method comprises the following steps:

[0046] Step 101: According to the mapping table obtained in advance, the target network instance corresponding to the S-NSSAI of the terminal service is determined.

[0047] Specifically, the definition of the network instance (Network Instance) is "Information identifying a 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.

[0048] Specifically, the mapping table obtained in advance by the SMF entity sets the correspondence relationship between the network instance and the S-NSSAI, and the mapping between the S-NSSAI and the network instance can be realized through the correspondence relationship. Specifically, the correspondence relationship can be as shown in the following table:

[0049] S-NSSAI Network instance A A: Access Point 1 (APN1), APN2 B B: APN1, APN2 C C: APN1, APN2

[0050] In this step, the SMF entity can determine the target network instance corresponding to the S-NSSAI of the terminal service based on the correspondence relationship between the network instance and the S-NSSAI in the mapping table, so as to realize the mapping between the S-NSSAI and the target network instance.

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

[0052] Step 102: Send the parameters of the target network instance to the UPF entity.

[0053] In this step, specifically, the SMF entity sends the parameters of the target network instance to the UPF entity, so that the UPF entity allocates resources to the target network instance, realizes the mapping identification, distinction and isolation of the network instance by the UPF entity, and thus realizes that multiple slices can run on one UPF entity.

[0054] Specifically, the parameter of the network instance is the network instance itself information, that is, information used for traffic detection and routing, such as access point information and the like. At this time, the parameter of the target network instance is the target network instance itself information.

[0055] The SMF entity in this embodiment 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, so that the UPF entity allocates resources to the target network instance, thereby realizing the mapping of the S-NSSAI to the network instance, and the UPF entity distinguishing and isolating the slices by using the network instance, so that multiple slices can run on one UPF entity, and the problem that multiple slices cannot run simultaneously due to the UPF entity being unable to distinguish and identify the slices in the prior art is solved.

[0056] Optionally, in this embodiment, the mapping table further has a correspondence between the network instance and the required resource configuration of the network instance, and at this time, the embodiment can 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.

[0057] Specifically, the required resource configuration of the network instance can include CPU, storage, bandwidth, delay and the like, which are not limited here.

[0058] In addition, when the correspondence between the network instance and the required resource configuration of the network instance is set in the mapping table, the mapping table has a correspondence between the S-NSSAI, the network instance and the required resource configuration of the network instance.

[0059] At this time, the mapping table can be as shown in the following table:

[0060] S-NSSAI Network instance Required resource configuration A A: APN1, APN2 CPU: 30% B B: APN1, APN2 CPU: 40% C C: APN1, APN2 CPU: 30%

[0061] Through the correspondence in the above 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 make the resource allocation for the target network instance meet the resource requirement of the target network instance while realizing the distinguishing and isolation of the slices.

[0062] Further, optionally, in the embodiment, the SMF entity needs to acquire the mapping table before determining the target network instance corresponding to the S-NSSAI of the terminal service according to the pre-acquired mapping table, that is, the embodiment also needs to perform any of the following operations to obtain the mapping table:

[0063] Firstly, the SMF entity configures the mapping table by itself.

[0064] In this way, the SMF entity can pre-configure the mapping table and save it locally.

[0065] Of course, it should be noted that the mapping table can also be configured by other platforms such as operation maintenance management (OAM), which is not limited here.

[0066] Specifically, after the SMF entity configures the mapping table, the mapping table can 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 correspondence between the S-NSSAI and the network instance, or the correspondence between the S-NSSAI, the network instance and the required resource configuration of the network instance.

[0067] Specifically, if the SMF entity initiates a PFCP Association Setup Request message, the mapping table can be sent to the UPF entity by being contained in the PFCP Association Setup Request message; if the UPF entity initiates a PFCP Association Setup Request message to the SMF entity, the mapping table can be sent to the UPF entity by being contained in the PFCP Association Setup Response message fed back by the SMF entity.

[0068] Of course, after the UPF entity receives the mapping table, the mapping table can be saved locally; in addition, if the UPF entity has saved the mapping table of this SMF entity before, the saved mapping table corresponding to the SMF entity is updated to ensure the consistency between the mapping table saved by the UPF entity and the mapping table saved by the SMF entity.

[0069] Secondly, the terminal IP address pool information parameter sent by the UPF entity is received, wherein the terminal IP address pool information parameter contains the mapping table.

[0070] Specifically, in this way, the UPF entity can set the mapping table and send the mapping table to the SMF entity through the 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.

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

[0072] (1) sending a first 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.

[0073] Specifically, the terminal IP address pool information parameter is carried in the PFCP association establishment response message.

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

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

[0076] Specifically, the terminal IP address pool information parameter is carried in the second PFCP association establishment request message.

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

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

[0079] Specifically, the terminal IP address pool information parameter is carried in the PFCP association update request (PFCP Association Update request) message.

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

[0081] Through any of the above messages, the UPF entity sends the terminal IP address pool information parameter containing the mapping table to the SMF entity, so that the SMF entity can realize the mapping between the S-NSSAI of the terminal service and the network instance.

[0082] In this way, by configuring the terminal IP address pool information parameter by the SMF entity itself or receiving the terminal IP address pool information parameter sent by the UPF entity, the mapping table can be obtained, 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.

[0083] In addition, optionally, in the present embodiment, when the SMF entity sends the parameters of the target network instance to the UPF entity, the parameters of the target network instance can be sent to the UPF entity through a PFCP session establishment request message or a PFCP session modification request message.

[0084] 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 the parameters of the target network instance corresponding to the S-NSSAI of the service in the above message and sends them to the UPF entity.

[0085] 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 can also be sent to the UPF entity through a PFCP session establishment request message or a PFCP session modification request message.

[0086] That is, at this time, the required resource configuration of the target network instance corresponding to the S-NSSAI of the service can be sent to the UPF entity through a PFCP session establishment request message or a PFCP session modification request message, so that the UPF entity can allocate resources to the target network instance based on this, and realize the differentiation and isolation of slices.

[0087] In addition, after the UPF entity allocates resources to the target network instance, at this time, the SMF entity can also perform any of the following operations:

[0088] First, receiving a PFCP session establishment response message sent by the UPF entity based on the PFCP session establishment request message.

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

[0090] When the UPF entity cannot meet the resource configuration requirement of the target network instance, the PFCP session establishment response message contains a reason value, which is a slice resource shortage, 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, at this time, the SMF entity can determine the session establishment failure reason based on the reason value, or determine to establish other types of sessions, or determine to switch the terminal service to a slice corresponding to another S-NSSAI.

[0091] Secondly, the PFCP session modification response message sent by the UPF entity based on the PFCP session modification request message is received.

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

[0093] When the UPF entity cannot meet the resource configuration requirement of the target network instance, the PFCP session modification response message contains a reason value, which is a slice resource shortage, 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, at this time, the SMF entity can determine the session modification failure reason based on the reason value.

[0094] In this way, through the session establishment or modification process, the target network instance or the target network instance and the required resource configuration of the target network instance are sent to the UPF entity, so that the UPF entity can perform resource allocation on the target network instance, which can include CPU, storage, bandwidth or delay, etc.

[0095] The slice resource allocation method provided in the embodiment determines the target network instance corresponding to the S-NSSAI of the terminal service according to the corresponding relationship between the network instance and the S-NSSAI in the mapping table, and 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, which realizes the mapping of S-NSSAI to network instance, and the UPF entity uses the network instance to distinguish and isolate the slices, so that multiple slices can run on one UPF entity, solving the problem that multiple slices cannot run simultaneously due to the inability of the UPF entity to distinguish and identify the slices in the prior art.

[0096] Further, as Figure 2 Fig. 2 shows a flow chart of a slice resource allocation method applied to a UPF entity in an embodiment of the present application, which comprises the following steps:

[0097] Step 201: receiving the parameters of the target network instance sent by the SMF entity.

[0098] 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 pre-obtained mapping table, which sets the correspondence between the network instance and the S-NSSAI.

[0099] Specifically, the SMF entity obtains 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 parameters of the target network instance to the UPF entity, at which time the UPF entity receives the parameters of the target network instance.

[0100] Based on the correspondence between the S-NSSAI and the network instance, the network instance is mapped with the S-NSSAI, the network instance is used for slice differentiation and isolation, and thus multiple slices can be simultaneously run on one UPF entity.

[0101] Step 202: allocating resources to the target network instance corresponding to the parameters of the target network instance.

[0102] Specifically, after obtaining the parameters of the target network instance sent by the SMF entity, the UPF entity can allocate resources to the target network instance corresponding to the parameters of the target network instance, i.e., the target network instance can be allocated resources by referring to the information of the target network instance itself.

[0103] Specifically, the resource allocation can include CPU, storage, bandwidth, or delay, etc., which is not specifically limited here.

[0104] In this way, the UPF entity in the embodiment receives the parameters of the target network instance corresponding to the S-NSSAI of the terminal service, and allocates resources to the target network instance, based on the correspondence between the network instance and the S-NSSAI, the S-NSSAI is mapped to the network instance and the network instance is used for slice differentiation and isolation, so that multiple slices can be simultaneously run on one UPF entity, solving the problem that multiple slices cannot be simultaneously run due to the inability of the UPF entity to differentiate and identify slices in the prior art.

[0105] Optionally, the mapping table further comprises a correspondence between the network instance and a required resource configuration of the network instance; the UPF entity in this embodiment can further receive a required resource configuration of a 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.

[0106] In addition, specifically, the SMF entity can receive the mapping table configured by the UPF entity. At this time, specifically, the UPF entity can send terminal IP address pool information parameters to the SMF entity before receiving the parameters of the target network instance sent by the SMF entity, wherein the terminal IP address pool information parameters comprise the mapping table.

[0107] Specifically, sending the terminal IP address pool information parameters to the SMF entity comprises any one of the following:

[0108] (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.

[0109] Specifically, the PFCP association establishment response message carries the terminal IP address pool information parameters.

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

[0111] Specifically, the second PFCP association establishment request message carries the terminal IP address pool information parameters.

[0112] (3) sending a PFCP association update request message to the SMF entity.

[0113] Specifically, the PFCP association update request message carries the terminal IP address pool information parameters.

[0114] That is, any of the above messages realizes sending the terminal IP address pool information parameters comprising the mapping table to the SMF entity.

[0115] In addition, specifically, the SMF entity can itself configure the UPF entity. At this time, before the UPF entity receives the parameters of the target network instance sent by the SMF entity, the SMF entity can further receive the mapping table sent by the SMF entity through the PFCP association establishment request message or the PFCP association establishment response message after the SMF entity itself configures the mapping table.

[0116] It should be noted that the above mapping table can refer to the related content of the SMF entity side method embodiment, which will not be described in detail here.

[0117] In addition, in this embodiment, the UPF entity, when only receiving the parameter of the target network instance, allocates resources to the target network instance according to the resource configuration of the UPF entity itself; or, when receiving the parameter of the target network instance and the required resource configuration of the target network instance, allocates resources to the target network instance according to the required resource configuration of the target network instance.

[0118] Specifically, if the UPF entity only receives the parameter of the target network instance but does not receive the required resource configuration of the target network instance, the UPF entity can allocate resources to the target network instance according to network requirements and the resource configuration of the UPF entity itself, including CPU, storage, bandwidth, and delay, so as to realize the differentiation and isolation of slices; if the UPF entity receives the parameter of the target network instance and the required resource configuration of the target network instance, the UPF entity can allocate resources 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 requirements of the target network instance.

[0119] In addition, in this embodiment, when the UPF entity receives the parameter of the target network instance sent by the SMF entity, the UPF entity can receive the parameter of the target network instance sent by the SMF entity through the PFCP session establishment request message or the PFCP session modification request message.

[0120] In addition, in this embodiment, when the UPF entity receives the required resource configuration of the target network instance sent by the SMF entity, the UPF entity can receive 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.

[0121] In addition, after the UPF entity allocates resources to the target network instance, the UPF entity can perform any of the following operations:

[0122] sending, to the SMF entity, a PFCP session establishment response message based on the PFCP session establishment request message, wherein when the UPF entity cannot meet the resource configuration requirements of the target network instance, the PFCP session establishment response message contains a reason value, and the reason value is slice resource shortage; or,

[0123] sending, to the SMF entity, a PFCP session modification response message based on the PFCP session modification request message, wherein when the UPF entity cannot meet the resource configuration requirements of the target network instance, the PFCP session modification response message contains a reason value, and the reason value is slice resource shortage.

[0124] It should be noted that the specific introduction of the above content can refer to the related content of the method embodiment of the SMF entity, and will not be described in detail here.

[0125] Thus, the slice resource allocation method provided by the embodiment realizes the mapping of S-NSSAI to network instance and the differentiation and isolation of slices by using network instance, so that multiple slices can run simultaneously on one UPF entity, and solves the problem that multiple slices cannot run simultaneously due to the inability of UPF entity to differentiate and identify slices in the prior art.

[0126] The present application will be described in detail below through specific embodiments.

[0127] In a first embodiment, the SMF entity configures a mapping table, and the mapping table is provided with the correspondence between the network instance and the S-NSSAI:

[0128] As shown in the figure, the overall process of slice resource allocation is as follows: Figure 3

[0129] Step 1: The SMF entity pre-configures the correspondence between the Network Instance and the S-NSSAI, obtains the mapping table and saves it locally. Specifically, the configuration operation of the mapping table can be directly operated on the SMF entity, or operated through other platforms such as OAM, and this is not specifically limited here.

[0130] Step 2: Optionally, the SMF entity can send the mapping table to the UPF entity through the PFCP Association Setup Request message or the PFCP Association Setup Response message. Specifically, if the SMF entity initiates the PFCP Association Setup Request message, the mapping table is included in the message; if the UPF entity initiates the PFCP Association Setup Request message, the mapping table is included in the PFCP Association Setup Response message returned by the SMF entity to the UPF entity.

[0131] Step 3: The UPF entity saves the mapping table locally; if the UPF entity has previously saved the mapping table of this SMF entity, the saved mapping table is updated.

[0132] ​Step 4, when it is needed to establish or modify a session, the SMF entity sends a PFCP Session Establishment Request message or a PFCP Session Modification Request message to the UPF entity, and 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 above message.

[0133] Step 5, the UPF entity allocates resources for the target network instance according to network requirements and its own configuration, including CPU, storage, bandwidth, delay, etc.

[0134] Step 6, the UPF entity returns a PFCP Session Establishment Response message or a PFCP Session Modification Response message to the SMF entity.

[0135] So far, the resource allocation of the target network instance is completed, thereby realizing the differentiation and isolation of the slices by utilizing the network instance, so that multiple slices can run simultaneously on one UPF entity.

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

[0137] As shown in Figure 4 , the overall process of slice resource allocation is as follows:

[0138] Step 1, the SMF entity pre-configures the corresponding relationship between the network instance, the S-NSSAI and the required resource configuration of the network instance, obtains the mapping table and saves it locally. Specifically, the configuration operation of the mapping table can be directly operated on the SMF entity, or operated through other platforms such as OAM, and this does not make specific limitation here.

[0139] Step 2, optionally, the SMF entity can 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 SMF entity initiates the PFCP Association Setup Request message, the mapping table is included in this message; if the UPF entity initiates the PFCP Association Setup Request message, the mapping table is included in the PFCP Association Setup Response message returned by the SMF entity to the UPF entity.

[0140] Step 3, the UPF entity saves the mapping table locally; if the UPF entity has previously saved a mapping table of this SMF entity, the saved mapping table is updated.

[0141] Step 4, when a 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, and according to the mapping table, maps the required S-NSSAI of the service to the target network instance, and includes the target network instance in the above message. Optionally, the required resource configuration of the target network instance can also be included in the above message.

[0142] Step 5, the UPF entity allocates resources to the target network instance according to the target network instance and the required resource configuration of the target network instance sent by the SMF entity, including CPU, storage, bandwidth, delay, etc.

[0143] Step 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 limitations or other reasons, the UPF entity needs to carry the cause value of "slice resource shortage" in the Cause in the message. It should be noted that the cause value is only an example, and other expression cause values indicating slice resource shortage can also be carried in the Cause, which is not specifically limited here.

[0144] At this point, the resource allocation of the target network instance is completed, thereby realizing the differentiation and isolation of slices by using network instances, so that multiple slices can run simultaneously on one UPF entity.

[0145] In the third embodiment, the UPF entity configures a mapping table, and the mapping table sets the corresponding relationship between the network instance and the S-NSSAI, or sets the corresponding relationship between the network instance, the S-NSSAI and the required resource configuration of the network instance:

[0146] As shown in Figure 5 In this case, the overall process of slice resource allocation is as follows:

[0147] Step 1, the UPF entity pre-configures the correspondence between the network instance and the S-NSSAI, or the correspondence between the network instance, the S-NSSAI and the required resource configuration of the network instance, obtains a mapping table and saves it locally. Specifically, the configuration operation of the mapping table can be directly operated on the UPF entity, or operated through other platforms such as OAM, and this does not make specific limitations here.

[0148] Step 2, send the mapping table to the SMF entity through the terminal IP address pool information parameter (UE IP address Pool Information IE).

[0149] Specifically, the existing UE IP address Pool Information IE information is as shown in the following table:

[0150]

[0151]

[0152] The existing UE IP address Pool Information IE information does not consider the correspondence in the mapping table, but in the present application, the mapping table can be contained in each UE IP address Pool Information IE. Of course, the UE IP address Pool Information IE also contains the UE IP address Pool allocated to the SMF entity.

[0153] In addition, when the PFCP Association Setup or the PFCP Association Update process initiated by the UPF entity is performed between the SMF entity and the UPF entity, the UPF entity can carry the UE IP address Pool Information IE (which can carry multiple) in any of the following messages:

[0154] (1) in the PFCP Association Setup response message returned by the UPF entity after the PFCP Association Setup request initiated by the SMF entity;

[0155] (2) in the PFCP Association Setup request message initiated by the UPF entity;

[0156] (3) in the PFCP Association Update request message initiated by the UPF entity.

[0157] Step 3, when a 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, and maps the required S-NSSAI of the service to the target network instance according to the mapping table, and includes the target network instance in the above message. Optionally, the required resource configuration of the target network instance can also be included in the above message at the same time.

[0158] Step 4, the UPF entity allocates resources to the target network instance according to the target network instance sent by the SMF entity, including CPU, storage, bandwidth and delay, etc. If the SMF entity also sends the required resource configuration of the target network instance, the target network instance can be allocated resources according to the configuration; specifically, if there is no required resource configuration of the target network instance in the UPF entity at this time or the available resources are insufficient, the UPF entity can allocate resources according to the network situation and its own configuration.

[0159] 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 limitations or other reasons, the UPF entity needs to carry the reason value of "slice resource insufficient" in the Cause in the message.

[0160] At this point, the resource allocation of the target network instance is completed, thereby realizing the differentiation and isolation of the slices by using the network instance, so that multiple slices can run on one UPF entity at the same time.

[0161] Figure 6 is a structure diagram of a slice resource allocation device provided by an embodiment of the present application, which includes a memory 620, a transceiver 600, and a processor 610.

[0162] Among them, in Figure 6In particular embodiments, the bus architecture can include any number of interconnecting buses and bridges, depending on the specific application of the processor 610 and the memory 620 that are linked together by the various circuits of the bus architecture. The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described further. The bus interface provides an interface to the transceiver 600. The transceiver 600 can be a number of elements, including a transmitter that can be configured to transmit to various other apparatuses on a transmission medium, and a receiver that can be configured to receive from various other apparatuses on a transmission medium. The transmission medium can include a wireless channel, a wired channel, optical cable, or other transmission media. The processor 610 is responsible for managing the bus architecture and general processing, and the memory 620 can store data for use by the processor 610 in executing its operations.

[0163] The processor 610 can 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), or the processor can be a multi-core architecture.

[0164] The memory 620 is configured to store a computer program; the transceiver 600 is configured to transceive data under control of the processor; and the processor 610 is configured to read the computer program in the memory and perform the following operations:

[0165] According to a pre-acquired mapping table, a target network instance corresponding to single network slice selection assistance information (S-NSSAI) of a terminal service is determined, wherein the mapping table is provided with a corresponding relationship between a network instance and S-NSSAI;

[0166] Parameters of the target network instance are sent to a user plane function (UPF) entity, so that the UPF entity allocates resources to the target network instance.

[0167] Optionally, the mapping table is further provided with a corresponding relationship between a network instance and a required resource configuration of the network instance;

[0168] The slice resource allocation method further includes:

[0169] According to the mapping table, a required resource configuration of the target network instance is determined;

[0170] The required resource configuration of the target network instance is sent to the UPF entity.

[0171] Optionally, the method further includes:

[0172] The SMF entity configures the mapping table itself, or receives a terminal IP address pool information parameter sent by the UPF entity, wherein the terminal IP address pool information parameter contains the mapping table.

[0173] Optionally, the receiving the terminal IP address pool information parameter sent by the UPF entity comprises any one of the following:

[0174] sending a first packet 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;

[0175] 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;

[0176] 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.

[0177] Optionally, after the mapping table is configured, the method further comprises:

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

[0179] Optionally, the sending the parameters of the target network instance to the UPF entity comprises:

[0180] 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.

[0181] Optionally, the sending the required resource configuration of the target network instance to the UPF entity comprises:

[0182] 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.

[0183] Optionally, the method further comprises:

[0184] Receive the 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 reason value, the reason value being insufficient slice resources; or,

[0185] Receive the 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 reason value, the reason value being insufficient slice resources.

[0186] It should be noted that the above-mentioned SMF entity can implement all the method steps of the SMF entity method side embodiment and achieve the same technical effect, which will not be repeated here.

[0187] Figure 7 This is a schematic diagram of the structure of a UPF entity provided in an embodiment of this application, including a memory 720, a transceiver 700, and a processor 710.

[0188] Among them, Figure 7 In this context, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits together, represented by one or more processors (processor 710) and memory (memory 720). The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. The transceiver 700 can be multiple elements, including transmitters and receivers, providing units for communicating with various other devices over transmission media, including wireless channels, wired channels, optical fibers, etc. The processor 710 is responsible for managing the bus architecture and general processing, and the memory 720 can store data used by the processor 710 during operation.

[0189] The processor 710 can 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). The processor can also adopt a multi-core architecture.

[0190] The memory 720 is used to store computer programs; the transceiver 700 is used to send and receive data under the control of the processor; the processor 710 is used to read the computer programs in the memory and perform the following operations:

[0191] receiving a parameter of a target network instance sent by a session management function (SMF) entity, wherein the target network instance corresponds to a single network slice selection assistance information (S-NSSAI) of a terminal service, and the target network instance is determined by the SMF entity according to a mapping table pre-acquired by the SMF entity, and the mapping table sets a corresponding relationship between a network instance and an S-NSSAI;

[0192] allocating resources to the target network instance corresponding to the parameter of the target network instance.

[0193] Optionally, the mapping table further sets a corresponding relationship between a network instance and a required resource configuration of a network instance.

[0194] The slice resource allocation method further includes:

[0195] 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.

[0196] Optionally, the allocating resources to the target network instance corresponding to the parameter of the target network instance includes:

[0197] when only the parameter of the target network instance is received, the UPF entity allocates resources to the target network instance according to a resource configuration of the UPF entity; or

[0198] when the parameter of the target network instance and the required resource configuration of the target network instance are received, the UPF entity allocates resources to the target network instance according to the required resource configuration of the target network instance.

[0199] Optionally, before the receiving the parameter of the target network instance sent by the SMF entity, the method further includes:

[0200] sending a terminal IP address pool information parameter to the SMF entity, wherein the terminal IP address pool information parameter contains the mapping table.

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

[0202] 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;

[0203] sending a second PFCP association establishment request message to the SMF entity, wherein the terminal IP address pool information parameter is carried in the second PFCP association establishment request message;

[0204] sending a PFCP association update request message to the SMF entity, wherein the terminal IP address pool information parameter is carried in the PFCP association update request message.

[0205] Optionally, before the receiving the target network instance sent by the session management function, SMF, entity, the method further comprises:

[0206] receiving the mapping table sent by the SMF entity through a PFCP association establishment request message or a PFCP association establishment response message after the SMF entity configures the mapping table by itself.

[0207] Optionally, the receiving the target network instance sent by the session management function, SMF, entity comprises:

[0208] receiving 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.

[0209] Optionally, the receiving the required resource configuration of the target network instance sent by the SMF entity comprises:

[0210] 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.

[0211] Optionally, the method further comprises:

[0212] 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, a reason value is contained in the PFCP session establishment response message, and the reason value is slice resource shortage; or,

[0213] 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, a reason value is contained in the PFCP session modification response message, and the reason value is slice resource shortage.

[0214] It should be noted that the UPF entity can implement all method steps of the UPF entity method side embodiment and achieve the same technical effects, and thus will not be described here.

[0215] Figure 8A module block diagram of a slice resource allocation apparatus provided by an embodiment of the present application is shown in FIG. 1. The apparatus includes:

[0216] A determining module 801 is configured to determine a target network instance corresponding to single network slice selection assistance information (S-NSSAI) of a terminal service according to a mapping table obtained in advance, wherein the mapping table is provided with a corresponding relationship between a network instance and S-NSSAI.

[0217] A sending module 802 is configured to send a parameter of the target network instance to a user plane function (UPF) entity, so that the UPF entity allocates resources to the target network instance.

[0218] Optionally, the mapping table is further provided with a corresponding relationship between a network instance and a required resource configuration of the network instance.

[0219] The determining module is further configured to determine the required resource configuration of the target network instance according to the mapping table.

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

[0221] Optionally, the apparatus further includes:

[0222] A configuration module is configured to obtain the mapping table by self-configuration; or

[0223] A first receiving module is configured to receive a terminal IP address pool information parameter sent by the UPF entity, wherein the terminal IP address pool information parameter contains the mapping table.

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

[0225] Send a first packet forwarding control protocol (PFCP) association establishment request message to the UPF entity and receive 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;

[0226] Receive 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;

[0227] Receive 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.

[0228] Optionally, after the SMF entity configures the mapping table itself, the method further comprises:

[0229] 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.

[0230] Optionally, the sending module is specifically configured to send 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.

[0231] 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.

[0232] Optionally, the method further comprises:

[0233] 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, wherein the PFCP session establishment response message contains a cause value, and the cause value is slice resource insufficient; or

[0234] 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, wherein the PFCP session modification response message contains a cause value, and the cause value is slice resource insufficient.

[0235] It should be noted that the SMF entity can implement all method steps of the SMF entity method side embodiment and achieve the same technical effects, and thus will not be described here.

[0236] Figure 9 is a module block diagram of a slice resource allocation device provided by the embodiment of the application, and the device comprises:

[0237] a receiving module 901, configured to receive 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 assistance information S-NSSAI of a terminal service, and the target network instance is determined by the SMF entity according to a mapping table obtained in advance, and the mapping table sets a corresponding relationship between a network instance and S-NSSAI;

[0238] a resource allocation module 902, configured to perform resource allocation on a target network instance corresponding to the parameters of the target network instance.

[0239] Optionally, the mapping table further comprises a correspondence between a network instance and a required resource configuration of the network instance.

[0240] The receiving module is configured to receive the 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.

[0241] Optionally, the resource allocation module is configured to,

[0242] When only the parameters of the target network instance are received, the UPF entity allocates resources to the target network instance according to its own resource configuration; or when the parameters of the target network instance and the required resource configuration of the target network instance are received, the UPF entity allocates resources to the target network instance according to the required resource configuration of the target network instance.

[0243] Optionally, before receiving the parameters of the target network instance sent by the session management function (SMF) entity, the method further comprises:

[0244] The first sending module is configured to send terminal IP address pool information parameters to the SMF entity, wherein the terminal IP address pool information parameters comprise the mapping table.

[0245] Optionally, the first sending module is configured to perform any one of the following:

[0246] Receive a first packet forwarding control protocol (PFCP) association establishment request message sent by the SMF entity, and send 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 parameters.

[0247] Send 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 parameters.

[0248] Send a PFCP association update request message to the SMF entity, wherein the PFCP association update request message carries the terminal IP address pool information parameters.

[0249] Optionally, the method further comprises:

[0250] The receiving unit is configured to receive the mapping table sent by the SMF entity through a PFCP association establishment request message or a PFCP association establishment response message after the SMF entity configures the mapping table.

[0251] 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.

[0252] Optionally, the receiving module is specifically configured to receive 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.

[0253] Optionally, the method further comprises:

[0254] The second sending module is configured to send 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 reason value, and the reason value is slice resource shortage; or,

[0255] The third sending module is configured to send 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 reason value, and the reason value is slice resource shortage.

[0256] It should be noted that the UPF entity can implement all method steps of the UPF entity method side embodiment and achieve the same technical effects, and thus will not be described here.

[0257] It should be noted that the division of units in the embodiments of the present application is illustrative, and is only a logical function division. Actual implementation can have another division manner. In addition, each functional unit in each embodiment of the present application can be integrated in one processing unit, or each unit can be physically present alone, or two or more units can be integrated in one unit. The integrated unit can be realized in the form of hardware or in the form of a software functional unit.

[0258] The integrated unit, if implemented in the form of a software function unit and sold or used as an independent product, can be stored in a processor-readable storage medium. Based on such understanding, the technical solutions of the present application essentially or the part that contributes to the prior art or the whole or part of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium, and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor to perform all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and various media that can store program codes.

[0259] It should be noted that the above-mentioned device provided by the embodiments of the present application can realize all the method steps realized by the above-mentioned method embodiments, and achieve the same technical effects. Therefore, the same parts and beneficial effects of the method embodiments will not be described in detail.

[0260] On the other hand, the embodiments of the present application also provide a processor-readable storage medium, which stores a computer program for causing the processor to execute the method described in the above-mentioned embodiments.

[0261] The processor-readable storage medium can be any available medium or data storage device that the processor can access, including but not limited to a magnetic storage (such as a floppy disk, a hard disk, a magnetic tape, a magneto-optical disk (MO), etc.), an optical storage (such as a CD, a DVD, a BD, a HVD, etc.), and a semiconductor memory (such as a ROM, an EPROM, an EEPROM, a non-volatile memory (NAND FLASH), a solid-state disk (SSD)), etc.

[0262] As can be seen from the above-mentioned embodiments, the processor-readable storage medium stores a computer program, which is used to cause the processor to execute the above-mentioned slice resource allocation method.

[0263] Those skilled in the art should understand that the embodiments of the present application can be provided as a method, a system, or a computer program product. Therefore, the present application can take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present application can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage and optical storage, etc.) containing computer-usable program codes.

[0264] The computer executable instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operations 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 block or blocks. Figure 1 one or more flow or blocks. Figure 1 one or more flow or blocks.

[0265] These processor-executable instructions can 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 instructions which implement the function specified in the flowchart block or blocks. Figure 1 one or more flow or blocks. Figure 1 one or more flow or blocks.

[0266] These processor-executable instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operations 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 block or blocks. Figure 1 one or more flow or blocks. Figure 1 one or more flow or blocks.

[0267] Obviously, numerous modifications and variations of the present application are possible in light of the above teachings. It is therefore to be understood that within the scope of the claims and their equivalents, the application can be practiced otherwise than as specifically described.

Claims

1. A method for allocating slice resources, applied to a Session Management Function (SMF) entity, characterized in that, include: Based on the pre-acquired mapping table, the target network instance corresponding to the single network slice selection auxiliary information S-NSSAI of the terminal service is determined, wherein the mapping table sets the correspondence between the network instance and S-NSSAI. The parameters of the target network instance are sent to the User Plane Function (UPF) entity so that the UPF entity can allocate resources to the target network instance. The mapping table also includes a correspondence between network instances and the required resource configurations of those network instances. The slice resource allocation method further includes: Based on the mapping table, determine the required resource configuration of the target network instance; Send the required resource configuration of the target network instance to the UPF entity.

2. The slice resource allocation method according to claim 1, characterized in that, Also includes: The SMF entity itself configures to obtain the mapping table; or... The terminal IP address pool information parameters sent by the UPF entity are received, wherein the terminal IP address pool information parameters contain the mapping table.

3. The slice resource allocation method according to claim 2, characterized in that, The terminal IP address pool information parameter received from the UPF entity includes any one of the following: Send a first Message Forwarding Control Protocol (PFCP) association establishment request message to the UPF entity, and receive 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 parameters. Receive 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; Receive the 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.

4. The slice resource allocation method according to claim 2, characterized in that, After the SMF entity obtains the mapping table through its own configuration, it also includes: The mapping table is sent to the UPF entity via a PFCP association establishment request message or a PFCP association establishment response message.

5. The slice resource allocation method according to claim 1, characterized in that, Sending the parameters of the target network instance to the User Plane Function (UPF) entity includes: The parameters of the target network instance are sent to the UPF entity through a PFCP session establishment request message or a PFCP session modification request message.

6. The slice resource allocation method according to claim 1, characterized in that, Sending the required resource configuration of the target network instance to the UPF entity includes: The required resource configuration of the target network instance is sent to the UPF entity through a PFCP session establishment request message or a PFCP session modification request message.

7. The slice resource allocation method according to claim 5 or 6, characterized in that, Also includes: Receive the 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 reason value, and the reason value is insufficient slice resources; or, Receive the 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 reason value, the reason value being insufficient slice resources.

8. A method for allocating sliced ​​resources, applied to user-plane functional UPF entities, characterized in that, include: The target network instance is sent by the Session Management Function (SMF) entity, wherein the target network instance corresponds to the Single Network Slice Selection Auxiliary Information (S-NSSAI) of the terminal service, and the target network instance is determined by the SMF entity according to a pre-acquired mapping table, wherein the mapping table contains the correspondence between network instances and S-NSSAI. Resource allocation is performed on the target network instance corresponding to the parameters of the target network instance; The mapping table also includes a correspondence between network instances and the required resource configurations of those network instances. The slice resource allocation method further includes: The SMF entity receives the 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.

9. The slice resource allocation method according to claim 8, characterized in that, The resource allocation for the target network instance corresponding to the parameters of the target network instance includes: When only parameters of the target network instance are received, the UPF entity allocates resources to the target network instance according to its own resource configuration; or, When the parameters of the target network instance and the required resource configuration of the target network instance are received, the resources of the target network instance are allocated according to the required resource configuration of the target network instance.

10. The slice resource allocation method according to claim 8, characterized in that, Before receiving the parameters of the target network instance sent by the Session Management Function (SMF) entity, the method further includes: The terminal IP address pool information parameter is sent to the SMF entity, wherein the terminal IP address pool information parameter contains the mapping table.

11. The slice resource allocation method according to claim 10, characterized in that, The parameter for sending the terminal IP address pool information to the SMF entity includes any one of the following: The system receives a first Message Forwarding Control Protocol (PFCP) association establishment request message sent by the SMF entity, and sends 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. Send 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; Send 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.

12. The slice resource allocation method according to claim 8, characterized in that, Before receiving the parameters of the target network instance sent by the Session Management Function (SMF) entity, the method further includes: After receiving the mapping table from the SMF entity's own configuration, the mapping table is sent via a PFCP association establishment request message or a PFCP association establishment response message.

13. The slice resource allocation method according to claim 8, characterized in that, The parameters of the target network instance sent by the Receive Session Management Function (SMF) entity include: Receive the 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.

14. The slice resource allocation method according to claim 9, characterized in that, The required resource configuration for receiving the target network instance sent by the SMF entity includes: Receive 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.

15. The slice resource allocation method according to claim 13 or 14, characterized in that, Also includes: Based on the PFCP session establishment request message, a PFCP session establishment response message is sent to the SMF entity. When the UPF entity cannot meet the resource configuration requirements of the target network instance, the PFCP session establishment response message includes a reason value, where the reason value is insufficient slice resources; or... Based on the PFCP session modification request message, a PFCP session modification response message is sent to the SMF entity. When the UPF entity cannot meet the resource configuration requirements of the target network instance, the PFCP session modification response message contains a reason value, which is insufficient slice resources.

16. An SMF entity, characterized in that, Includes memory, transceiver, and processor: A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations: Based on the pre-acquired mapping table, the target network instance corresponding to the single network slice selection auxiliary information S-NSSAI of the terminal service is determined, wherein the mapping table sets the correspondence between the network instance and S-NSSAI. The parameters of the target network instance are sent to the User Plane Function (UPF) entity so that the UPF entity can allocate resources to the target network instance. The mapping table also includes a correspondence between network instances and the required resource configurations of those network instances. Slice resource allocation methods also include: Based on the mapping table, determine the required resource configuration of the target network instance; Send the required resource configuration of the target network instance to the UPF entity.

17. The SMF entity according to claim 16, characterized in that, Also includes: The SMF entity itself configures to obtain the mapping table; or... The terminal IP address pool information parameters sent by the UPF entity are received, wherein the terminal IP address pool information parameters contain the mapping table.

18. The SMF entity according to claim 17, characterized in that, The terminal IP address pool information parameter received from the UPF entity includes any one of the following: Send a first Message Forwarding Control Protocol (PFCP) association establishment request message to the UPF entity, and receive 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 parameters. Receive 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; Receive the 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.

19. The SMF entity according to claim 16, characterized in that, Sending the parameters of the target network instance to the User Plane Function (UPF) entity includes: The parameters of the target network instance are sent to the UPF entity through a PFCP session establishment request message or a PFCP session modification request message.

20. A UPF entity, characterized in that, Includes memory, transceiver, and processor: A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations: The target network instance is sent by the Session Management Function (SMF) entity, wherein the target network instance corresponds to the Single Network Slice Selection Auxiliary Information (S-NSSAI) of the terminal service, and the target network instance is determined by the SMF entity according to a pre-acquired mapping table, wherein the mapping table contains the correspondence between network instances and S-NSSAI. Resource allocation is performed on the target network instance corresponding to the parameters of the target network instance; The mapping table also includes a correspondence between network instances and the required resource configurations of those network instances. Slice resource allocation methods also include: The SMF entity receives the 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.

21. The UPF entity according to claim 20, characterized in that, Before receiving the parameters of the target network instance sent by the Session Management Function (SMF) entity, the method further includes: The terminal IP address pool information parameter is sent to the SMF entity, wherein the terminal IP address pool information parameter contains the mapping table.

22. The UPF entity according to claim 20, characterized in that, The parameters of the target network instance sent by the Receive Session Management Function (SMF) entity include: Receive the 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.

23. The UPF entity according to claim 20, characterized in that, The required resource configuration for receiving the target network instance sent by the SMF entity includes: Receive 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.

24. The UPF entity according to claim 22 or 23, characterized in that, Also includes: Based on the PFCP session establishment request message, a PFCP session establishment response message is sent to the SMF entity. When the UPF entity cannot meet the resource configuration requirements of the target network instance, the PFCP session establishment response message includes a reason value, where the reason value is insufficient slice resources; or... Based on the PFCP session modification request message, a PFCP session modification response message is sent to the SMF entity. When the UPF entity cannot meet the resource configuration requirements of the target network instance, the PFCP session modification response message contains a reason value, which is insufficient slice resources.

25. A slice resource allocation device, applied to a Session Management Function (SMF) entity, characterized in that, include: The determination module is used to determine the target network instance corresponding to the single network slice selection auxiliary information S-NSSAI of the terminal service according to the pre-acquired mapping table, wherein the mapping table sets the correspondence between network instances and S-NSSAI. The sending module is used to send the parameters of the target network instance to the User Plane Function (UPF) entity, so that the UPF entity can allocate resources to the target network instance. The mapping table also includes a correspondence between network instances and the required resource configurations of those network instances. The determining module is further configured to determine the required resource configuration of the target network instance based on the mapping table; The sending module is also used to send the required resource configuration of the target network instance to the UPF entity.

26. A slice resource allocation device, applied to a User Face Function (UPF) entity, characterized in that, include: The receiving module is used to receive parameters of the target network instance sent by the Session Management Function (SMF) entity, wherein the target network instance corresponds to the Single Network Slice Selection Auxiliary Information (S-NSSAI) of the terminal service, and the target network instance is determined by the SMF entity according to a pre-acquired mapping table, wherein the mapping table contains the correspondence between network instances and S-NSSAI. The resource allocation module is used to allocate resources to the target network instance corresponding to the parameters of the target network instance; The mapping table also includes a correspondence between network instances and the required resource configurations of those network instances. The receiving module is configured to receive the 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.

27. A processor-readable storage medium, characterized in that, The processor-readable storage medium stores a computer program that causes the processor to execute the slice resource allocation method according to any one of claims 1 to 7, or to execute the slice resource allocation method according to any one of claims 8 to 15.

Images