Slice creation method and device, related equipment, storage medium and computer program product

Abstract

The invention discloses a slice creation method and device, a terminal, a first function, a second function, a storage medium and a computer program product. The method comprises the following steps: a terminal sends first information to a first function, the first function is at least used for access and mobility management, the first information is used for requesting to create a first network slice, and the first network slice does not belong to a network slice signed by the terminal; and receiving second information sent by the first function, wherein the second information represents that the first network slice is successfully created.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a slice creation method, apparatus, related equipment, storage medium and computer program product. Background Art

[0002] Fifth-generation mobile communication technology (5G) networks provide critical service support for various industries, including manufacturing, finance, services, the Internet of Things, and cloud computing. With the advancement of technology, different industries, businesses, and users have put forward various service quality requirements for networks. Therefore, 5G networks need to build flexible and dynamic networks to achieve massive access, deterministic latency, and extremely high reliability to meet the diverse business needs of users and vertical industries.

[0003] To meet these needs, network slicing technology has emerged. Through network slicing technology, multiple dedicated, virtualized, and isolated logical networks can be built on a common physical network to meet the differentiated network needs of different users.

[0004] In related technologies, the network slice management domain can manually generate the required network slices in advance based on user contract data to support users to quickly access network slices when accessing the network. However, if the network slices generated in advance cannot well support new business requirements, it may lead to poor user business experience. Summary of the Invention

[0005] To solve related technical problems, the embodiments of the present application provide a slice creation method, device, terminal, first function, second function, storage medium and computer program product.

[0006] The technical solution of the embodiment of the present application is implemented as follows:

[0007] This embodiment of the present application provides a slice creation method, which is applied to a terminal and includes:

[0008] Sending first information to a first function, where the first function is at least used for access and mobility management, and the first information is used to request creation of a first network slice, where the first network slice does not belong to the network slice subscribed by the terminal;

[0009] Receive second information sent by the first function, where the second information indicates that the first network slice is successfully created.

[0010] In the above solution, before sending the first information to the first function, the method further includes:

[0011] Sending third information to the first function, where the third information is used to request access to the first network slice;

[0012] Receive the fourth information sent by the first function, where the fourth information is used to notify the terminal to refuse access to the first network slice.

[0013] In the above solution, when receiving the second information sent by the first function, the method further includes:

[0014] Receive the fifth information sent by the first function, where the fifth information is used to request the terminal to access the first network slice.

[0015] An embodiment of the present application further provides a slice creation method, which is applied to a first function, where the first function is at least used for access and mobility management, including:

[0016] receiving first information sent by a terminal, where the first information is used to request creation of a first network slice, where the first network slice does not belong to the network slice to which the terminal has subscribed;

[0017] sending the first information to a second function, and receiving sixth information sent by the second function, where the second function is at least used to manage and configure network slices, and the sixth information is used to indicate that the first network slice is successfully created;

[0018] Sending second information to the terminal, wherein the second information indicates that the first network slice is successfully created.

[0019] In the above solution, before receiving the first information sent by the terminal, the method further includes:

[0020] receiving third information sent by the terminal, where the third information is used to request access to the first network slice;

[0021] Send fourth information to the terminal, where the fourth information is used to notify the terminal to refuse access to the first network slice.

[0022] In the above solution, when sending the second information to the terminal, the method further includes:

[0023] Send fifth information to the terminal, where the fifth information is used to request the terminal to access the first network slice.

[0024] This embodiment of the present application further provides a slice creation method, which is applied to a second function, where the second function is at least used to manage and configure network slices, including:

[0025] receiving first information sent by a first function, where the first information is used to request creation of a first network slice, where the first network slice does not belong to a network slice subscribed to by the terminal, and the first function is at least used for access and mobility management;

[0026] Creating the first network slice;

[0027] Send sixth information to the first function, where the sixth information is used to indicate that the first network slice is successfully created.

[0028] The present application also provides a slice creation device, including:

[0029] A first sending unit is configured to send first information to a first function, where the first function is at least used for access and mobility management, and the first information is used to request creation of a first network slice, where the first network slice does not belong to a network slice subscribed by the terminal;

[0030] The first receiving unit is used to receive second information sent by the first function, where the second information indicates that the first network slice is successfully created.

[0031] The present application also provides a slice creation device, including:

[0032] A second receiving unit is configured to receive first information sent by a terminal, where the first information is used to request creation of a first network slice, where the first network slice does not belong to the network slice to which the terminal has subscribed;

[0033] The second sending unit is used to send the first information to the second function and receive the sixth information sent by the second function, where the second function is at least used to manage and configure network slices, and the sixth information is used to indicate that the first network slice is successfully created; and send the second information to the terminal, where the second information indicates that the first network slice is successfully created.

[0034] The present application also provides a slice creation device, including:

[0035] A third receiving unit is configured to receive first information sent by a first function, where the first information is used to request creation of a first network slice, where the first network slice does not belong to a network slice subscribed to by the terminal, and the first function is used for at least access and mobility management;

[0036] A creating unit, configured to create the first network slice;

[0037] The third sending unit is used to send sixth information to the first function, and the sixth information is used to indicate that the first network slice is successfully created.

[0038] The embodiment of the present application further provides a terminal, comprising: a first processor and a first communication interface; wherein,

[0039] The first communication interface is used to send first information to a first function, where the first function is at least used for access and mobility management, and the first information is used to request the creation of a first network slice, which does not belong to the network slice subscribed to by the terminal; and receive second information sent by the first function, where the second information indicates that the first network slice is successfully created.

[0040] The embodiment of the present application further provides a first function, which is at least used for access and mobility management, including: a second processor and a second communication interface; wherein,

[0041] The second communication interface is used to receive first information sent by the terminal, where the first information is used to request the creation of a first network slice, which does not belong to the network slice subscribed by the terminal; send the first information to the second function, and receive sixth information sent by the second function, where the second function is at least used to manage and configure network slices, and the sixth information is used to indicate that the first network slice is successfully created; and send second information to the terminal, where the second information indicates that the first network slice is successfully created.

[0042] This embodiment of the present application further provides a second function, which is at least used to manage and configure network slices, including:

[0043] The third communication interface is configured to receive first information sent by a first function, where the first information is used to request creation of a first network slice, where the first network slice does not belong to a network slice subscribed to by the terminal; and send sixth information to the first function, where the sixth information is used to indicate that the first network slice is successfully created, where the first function is at least used for access and mobility management.

[0044] The third processor is used to create the first network slice.

[0045] An embodiment of the present application further provides a terminal, comprising: a first processor and a first memory for storing a computer program that can be run on the processor,

[0046] Wherein, the first processor is used to execute the steps of any of the above-mentioned terminal-side methods when running the computer program.

[0047] The embodiment of the present application further provides a first function, comprising: a second processor and a second memory for storing a computer program that can be run on the processor,

[0048] Wherein, the second processor is used to execute the steps of any one of the above-mentioned methods on the first functional side when running the computer program.

[0049] The embodiment of the present application further provides a second function, including: a third processor and a third memory for storing a computer program that can be run on the processor,

[0050] The third processor is configured to execute any one of the steps of the second functional side method when running the computer program.

[0051] An embodiment of the present application also provides a storage medium on which a computer program is stored. When the computer program is executed by a processor, it implements the steps of any of the above-mentioned terminal side methods, or implements the steps of any of the above-mentioned first function side methods, or implements the steps of any of the above-mentioned second function side methods.

[0052] An embodiment of the present application also provides a computer program product, including a computer program, which, when executed by a processor, implements the steps of any of the above-mentioned terminal side methods, or implements the steps of any of the above-mentioned first function side methods, or implements the steps of any of the above-mentioned second function side methods.

[0053] The slice creation method, device, terminal, first function, second function, storage medium and computer program product provided by the embodiments of the present application, the terminal sends first information to the first function, the first function is at least used for access and mobility management, the first information is used to request the creation of a first network slice, the first network slice does not belong to the network slice subscribed by the terminal; and after the first function receives the first information sent by the terminal, it sends the first information to the second function, the second function is at least used to manage and configure network slices; after the second function receives the first information sent by the first function, it creates the first network slice; and sends sixth information to the first function, the sixth information is used to indicate that the first network slice is successfully created; after the first function receives the sixth information sent by the second function, it sends second information to the terminal, the second information indicates that the first network slice is successfully created. The solution provided by the embodiment of the present application is that when the network side has not established the network slice corresponding to the service, the terminal requests the network side to create a network slice, and the network side creates the network slice according to the request. In this way, when the network side has not created the network slice requested by the terminal to access, the terminal can also initiate a request to the network side so that the network side can automatically create the corresponding network slice according to the terminal's request, thereby meeting the terminal's need to access the corresponding network slice; at the same time, the creation process does not require human participation, so the creation speed is fast, which can effectively improve the user's service experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0054] Figure 1 This is a schematic diagram of the network slicing management system structure in related technologies;

[0055] Figure 2 This is a flowchart of the first slice creation method according to an embodiment of the present application;

[0056] Figure 3 This is a flow chart of the second slice creation method according to an embodiment of the present application;

[0057] Figure 4 This is a flowchart of the third slice creation method according to an embodiment of the present application;

[0058] Figure 5 This is a flowchart of the fourth slice creation method according to an embodiment of the present application;

[0059] Figure 6 A flowchart of a sample slice creation method for this application;

[0060] Figure 7 This is a schematic diagram of the structure of the first slice creation device according to an embodiment of the present application;

[0061] Figure 8 This is a schematic diagram of the structure of the second slice creation device according to an embodiment of the present application;

[0062] Figure 9 This is a schematic diagram of the structure of the third slice creation device according to an embodiment of the present application;

[0063] Figure 10 This is a schematic diagram of the terminal structure of an embodiment of the present application;

[0064] Figure 11 This is a schematic diagram of the first functional structure of an embodiment of the present application;

[0065] Figure 12 This is a schematic diagram of the second functional structure of an embodiment of the present application;

[0066] Figure 13 A schematic diagram of the slicing creation system structure for an embodiment of the present application. DETAILED DESCRIPTION

[0067] The present application will be further described in detail below with reference to the accompanying drawings and examples.

[0068] With the development of technology, different industries, businesses, and users have placed diverse quality of service (QoS) requirements on networks. For example, services such as mobile communications, smart homes, environmental monitoring, smart agriculture, and smart metering require networks that can support massive device connections and the frequent transmission of large numbers of small messages. Services such as live streaming, video backhaul, and mobile healthcare place even higher demands on network transmission speeds. Services such as the Internet of Vehicles, smart grids, and industrial control require networks with millisecond-level latency and near-100% reliability. Therefore, 5G networks must be built with flexibility and dynamic capabilities to achieve massive access, deterministic latency, and extremely high reliability to meet the diverse business needs of users and vertical industries.

[0069] Faced with diverse business needs, the traditional network model that uses the same network to implement all businesses (which can also be understood as a "one-size-fits-all" network model) urgently needs to change. In related technologies, network operators use network slicing technology to build multiple dedicated, virtualized, and isolated logical networks on a common physical network to meet the differentiated network needs of different users.

[0070] like Figure 1 As shown, the network slicing architecture can include two main modules. The first module can include the network-side infrastructure layer such as user equipment (UE), access network (AN, Access Network, specifically including radio access network (RAN, Radio Access Network)), transmission network (TN, Transmission Network), core network (CN, Core Network), data network (DN, Data Network), etc. The first module can also be called the network slicing business domain, which is used for the deployment of slices; the second module can include communication service management function (CSMF, Communication Service Management Function), network slice management function (NSMF, Network Slice Management Function) and network slice subnet management function (NSSMF, Network Slice Subnet Management Function), etc. The second module can also be called the network slice management domain (or network slice management system, slice network management system), which is used to control, manage and coordinate multiple network slices.

[0071] Among them, CSMF can be used to convert relevant service requirements into slice-related requirements, and send the slice-related requirements to NSMF. The slice-related requirements may specifically include a service level agreement (SLA); NSMF can be used for the management and orchestration of network slice instances (NSI, Network Slice Instance), and can use the relevant requirements of network NSI to determine (can also be understood as deriving) the relevant requirements of network slice subnet instances (NSSI, Network SliceSubnet Instance), and send the NSSI-related requirements to NSSMF; NSSMF can be used for the management and orchestration of NSSI. NSSMF may specifically include a core network sub-slice management function (CN-NSSMF) for managing network slices of the core network, a transport network sub-slice management function (TN-NSSMF) for managing network slices of the transport network, and an access network sub-slice management function (AN-NSSMF) for managing network slices of the access network.

[0072] In the related technology, operators can usually determine the network slice that the user has signed a contract with (which can also be understood as the network slice required by the user) based on the contract data of the user (which can also be understood as an industry tenant), so that the operator can generate the NSI of the network slice that the user has signed a contract with in advance before the user accesses the network. In this way, when the user accesses the network, it can support rapid access to the corresponding network slice. Among them, the specific implementation steps for the operator to generate the NSI of the network slice may include: the operator's operation and maintenance personnel operate the CSMF through the operator's slice operation management platform, and issue the SLA requirements corresponding to the network slice to be created to the NSMF; after receiving the SLA requirements, the NSMF completes the creation and lifecycle (also understood as survival period) management of the NSI that meets the SLA requirements. Here, if the CSMF is not deployed on the network side, the operator's operation and maintenance personnel need to operate the NSMF to generate the required NSI of the network slice.

[0073] However, in actual applications, users may have new business needs while using the network, and may need to access unsigned network slices. In this case, if the NSI of this network slice has not been created in advance, the network side can connect the user to the default network slice based on the preset default configuration. However, the default network slice may not meet the user's business needs, resulting in a poor user experience. Alternatively, the network side can manually create the corresponding network slice, but manual creation has a low degree of automation and high latency (which can also be understood as a long configuration cycle), requiring users to wait for a long time, resulting in a poor service experience.

[0074] Based on this, in various embodiments of the present application, when the network side has not established a network slice corresponding to the service, the terminal requests the network side to create a network slice, and the network side creates the network slice according to the request. In this way, when the network side has not created the network slice that the terminal requests to access, the terminal can also initiate a request to the network side so that the network side can automatically create the corresponding network slice according to the terminal's request, thereby meeting the terminal's need to access the corresponding network slice; at the same time, the creation process does not require human participation, so the creation speed is fast, which can effectively improve the user's service experience.

[0075] The embodiment of the present application provides a slice creation method, which is applied to a terminal, such as Figure 2 As shown, the method includes:

[0076] Step 201: Sending first information to a first function, where the first function is at least used for access and mobility management, and the first information is used to request creation of a first network slice, where the first network slice does not belong to the network slice subscribed by the terminal;

[0077] Step 202: Receive the second information sent by the first function, where the second information indicates that the first network slice is successfully created.

[0078] Here, in actual application, the terminal can be called UE, terminal equipment, equipment, or user, etc., and the embodiments of the present application do not limit this.

[0079] It should be noted that in the embodiments of the present application, the first function and the second function can be referred to as functional bodies (the first function is called the first functional body, and the second function is called the second functional body), communication nodes (the first function is called the first communication node, and the second function is called the second communication node) or network elements (the first function is called the first network element, and the second function is called the second network element), etc., and the embodiments of the present application do not limit this.

[0080] In actual application, the first function may include an access and mobility management function (AMF).

[0081] In actual application, the terminal can determine the need to access the first network slice based on actual business needs. The types of the first network slice may specifically include enhanced mobile broadband (eMBB, enhanced Mobile BroadBand), ultra-high reliability and low latency communications (uRLLC, ultra-Reliable and Low Latency Communications), massive machine type communications (mMTC, massive Machine Type Communications), etc.

[0082] If the terminal is unable to obtain information about the network slices already created on the network side in advance, before step 201, the terminal may first send information to the first function, the information being used to request access to the first network slice; the first function may use the received information to determine whether the first function can provide slice services to the terminal; if the first function can provide slice services to the terminal, the first function may directly access the terminal to the first network slice; if the first function cannot provide slice services to the terminal, the first function may reject the terminal's request to access the first network slice. The terminal may then execute steps 201-202 to create the first network slice, so that the terminal can access the first network slice, if the first function rejects the terminal's request to access the first network slice.

[0083] Based on this, in one embodiment, before step 201, the method may further include:

[0084] Sending third information to the first function, where the third information is used to request access to the first network slice;

[0085] Receive the fourth information sent by the first function, where the fourth information is used to notify the terminal to refuse access to the first network slice.

[0086] Here, the third information may specifically include identification information of the terminal (which may also be understood as user identification, such as user permanent identifier (SUPI, SUbscription Permanent Identifier), etc.), identification information of the first network slice (which may also be understood as network slice ID or network slice representation, such as network slice selection assistance information (NSSAI, Network Slice Selection Assistance Information), etc.), etc.

[0087] In actual application, the terminal may send the third information to the first function via a non-access stratum (NAS) message, etc. That is, the terminal sends a NAS message, etc. to the first function, and the NAS message, etc. includes the third information.

[0088] In actual application, the first function can use the received third information to determine the identification information of the first network slice that the terminal requests to access, and the first function can further use the identification information of the first network slice and the subscription data of the terminal to determine whether the first network slice belongs to the network slice to which the terminal has subscribed. Among them, the first function can specifically obtain the subscription data of the terminal from the function for data management, and the function for data management can specifically include a unified data management function (UDM, Unified Data Management). If the first network slice belongs to the network slice to which the terminal has subscribed, the first function believes that the first network slice has been created. If the first function supports the first network slice, the first function can directly provide the first network slice for the terminal; if the first function cannot directly provide the first network slice for the terminal, the first function can call the Nnssf-NSSelection-Get service in the Network Slice Selection Function (NSSF) to query whether the network side has created the NSI of the first network slice, and receive the query result returned by NSSF. If the query result indicates that the network side has created the first network slice, the first function can determine that the network side can provide the first network slice for the terminal; if the query result indicates that the network side has not created the first network slice, the first function can determine that the network side cannot provide the first network slice for the terminal. At this time, the first function can send fourth information to the terminal to reject the terminal's request to access the first network slice.

[0089] In actual application, the first function may send a rejection message to the terminal, and the rejection message may include the fourth information. The fourth information may specifically include a numerical value (also referred to as a reason value), which may be used to indicate that the network side has not created the first network slice.

[0090] In actual application, the first function may send the fourth information to the terminal via a NAS message, etc. That is, the first function sends a NAS message, etc. to the terminal, and the NAS message, etc. includes the fourth information.

[0091] After receiving the fourth information, the terminal may learn the reason why the first function rejected the terminal's request to access the first network slice, which may include that the network side has not created the first network slice. In this case, the terminal may create the first network slice on the network side by executing steps 201-202, so that the terminal can access the first network slice.

[0092] In step 201, the terminal may send first information to the first function to request the network side to create the first slice. The first information may specifically include identification information of the terminal (which may also be understood as a user identification, such as a user permanent identifier (SUPI), SUbscription Permanent Identifier, etc.), identification information of the first function (such as AMF ID, etc.), identification information of the first network slice (such as NSSAI, etc.), request priority information (specifically including high priority, medium priority, low priority, etc.), capability requirement information related to the first network slice (which may also be understood as requirement information of the capability of the first network slice, such as SLA requirements, etc.). Among them, the capability requirement information related to the first network slice may specifically include: the maximum number of terminals simultaneously supported by the first network slice, the maximum bandwidth of the first network slice, the slice type of the first network slice, the life cycle of the first network slice, the service area of ​​the first network slice, etc.

[0093] In actual application, the terminal may send the first information to the first function via a NAS message, etc. That is, the terminal sends a NAS message, etc. to the first function, and the NAS message, etc. includes the first information.

[0094] After receiving the first information, the first function may use the first information to create the first network slice. For example, assuming that the first function includes AMF, after receiving the first information, the AMF may send the first information to a function for managing and configuring network slices (such as NSMF); the function for managing and configuring network slices may use the first information to create the first network slice and return a message indicating that the first network slice has been successfully created to the AMF.

[0095] In actual application, after the first network slice is successfully created, the first function may send second information to the terminal to inform the terminal that the first network slice has been successfully created. The first function may send the second information to the terminal via a NAS message, etc. That is, the first function sends a NAS message, etc. to the terminal, and the NAS message, etc. includes the second information.

[0096] When the first device sends the second information to the terminal, it may also send information to the terminal, where the sent information is used to request the terminal to initiate a request to access the first network slice.

[0097] Based on this, in one embodiment, in step 202, the method may further include:

[0098] Receive the fifth information sent by the first function, where the fifth information is used to request the terminal to access the first network slice.

[0099] Here, in actual application, the first function may send the fifth information to the terminal via a NAS message, etc. That is, the first function sends a NAS message, etc. to the terminal, and the NAS message, etc. includes the fifth information.

[0100] After receiving the fifth information, the terminal can determine the first network slice that has been successfully accessed based on actual business needs.

[0101] Based on this, in one embodiment, the method may further include:

[0102] Based on the fifth information, a request to access the first network slice is initiated.

[0103] From the above description, it can be seen that the first function can quickly create the first network slice based on the first information sent by the terminal, thereby meeting the terminal's need to access the first network slice and effectively improving the user's service experience.

[0104] Accordingly, the embodiment of the present application also provides a slice creation method, which is applied to the first function, such as Figure 3 As shown, including:

[0105] Step 301: Receive first information sent by a terminal, where the first information is used to request creation of a first network slice, where the first network slice does not belong to the network slice subscribed by the terminal;

[0106] Step 302: Send the first information to a second function, and receive sixth information sent by the second function, where the second function is at least used to manage and configure network slices, and the sixth information is used to indicate that the first network slice is successfully created;

[0107] Step 303: Send second information to the terminal, where the second information indicates that the first network slice is successfully created.

[0108] Here, when the terminal is unable to obtain in advance the network slice information that has been created on the network side, before step 301, the terminal can send a request message to the first function to request access to the first network slice; the first function can use the received request information to determine whether the first function can provide slice services to the terminal; if the first function can provide slice services to the terminal, the first function can directly access the terminal to the first network slice; if the first function cannot provide slice services to the terminal, the first function can reject the terminal's request to access the first network slice.

[0109] Based on this, in one embodiment, before step 301, the method may further include:

[0110] receiving third information sent by the terminal, where the third information is used to request access to the first network slice;

[0111] Send fourth information to the terminal, where the fourth information is used to notify the terminal to refuse access to the first network slice.

[0112] Here, in actual application, the terminal may send the third information to the first function via a NAS message, etc. That is, the terminal sends a NAS message, etc. to the first function, and the NAS message, etc. includes the third information.

[0113] In actual application, the first function can use the third information and the subscription data of the terminal to determine whether the first network slice belongs to the network slice subscribed by the terminal. This process can also be called authentication. Among them, the first function can specifically obtain the subscription data of the terminal from the function for data management, and the function for data management can specifically include UDM. If the first network slice belongs to the network slice subscribed by the terminal, the first function can consider that the first network slice has been created, and the first function can directly connect the terminal to the first network slice; if the first network slice does not belong to the network slice subscribed by the terminal, the first function can query whether the network side has created the first network slice through the function for network slice selection to obtain a query result, and the function for network slice selection can specifically include NSSF. If the query result indicates that the network side has created the first network slice, the first function can directly connect the terminal to the first network slice; if the query result indicates that the network side has not created the first network slice, the first function can send fourth information to the terminal.

[0114] In actual application, the first function may send the fourth information to the terminal via a NAS message, etc. That is, the first function sends a NAS message, etc. to the terminal, and the NAS message, etc. includes the fourth information.

[0115] After receiving the fourth information, the terminal may determine the reason why the first function rejected the terminal's request to access the first network slice, and the reason may include that the network side has not created the first network slice. In this case, the terminal may send a first message to the first function to request the network side to create the first network slice so that the terminal can access the first network slice.

[0116] In actual application, the terminal may send the first information to the first function via a NAS message, etc. That is, the terminal sends a NAS message, etc. to the first function, and the NAS message, etc. includes the first information.

[0117] After the first function receives the first information, in step 302, the first function may send the first information to the second function so that the second function can create the first network slice using the first information.

[0118] The second function may include an NSMF. The first function may send the first information to the second function via an interface between the first function and the second function.

[0119] In actual application, after the second function successfully creates the first network slice, it can send sixth information to the first function to inform the first function that the first network slice has been successfully created. Specifically, the second function can send the sixth information to the first function through the interface between the second function and the first function. The sixth information can be specifically referred to as slice creation success information.

[0120] After the first function receives the sixth information, the first function may send second information to the terminal to inform the terminal that the first network slice has been successfully created. The first function may send the second information to the terminal via a NAS message, etc. In other words, the first function sends a NAS message, etc. to the terminal, and the NAS message, etc. includes the second information.

[0121] When the first device sends the second information to the terminal, it may also send a request message to the terminal, requesting the terminal to initiate a request to access the first network slice.

[0122] Based on this, in one embodiment, in step 303, the method may further include:

[0123] Send fifth information to the terminal, where the fifth information is used to request the terminal to access the first network slice.

[0124] Accordingly, the embodiment of the present application also provides a slice creation method, which is applied to the second function, such as Figure 4 As shown, including:

[0125] Step 401: Receive first information sent by a first function, where the first information is used to request creation of a first network slice, where the first network slice does not belong to the network slice subscribed by the terminal;

[0126] Step 402: Create the first network slice;

[0127] Step 403: Send sixth information to the first function, where the sixth information is used to indicate that the first network slice is successfully created.

[0128] Here, in actual application, in step 401, the first function may send the first information to the second function through the interface between the first function and the second function.

[0129] After the second function receives the first information, the second function may use the first information to create the first network slice in step 402. Specifically, the second function may create the first network slice by interacting with a function for management and orchestration of NSSI (such as NSSMF) and relevant network elements.

[0130] In actual application, after the second function successfully creates the first network slice, it can send sixth information to the first function to inform the first function that the first network slice has been successfully created. Specifically, the second function can send the sixth information to the first function through the interface between the second function and the first function. The sixth information can be specifically referred to as slice creation success information.

[0131] As can be seen from the above description, the network side can create the first network slice based on the request of the terminal. The creation process does not require manual participation, avoiding the problems of long cycle and poor automation that may exist when the operator's operation and maintenance personnel manually create the first network slice. Therefore, the first network slice can be called a lightweight network slice or a lightweight slice. At the same time, in actual application, the first network slice type should be a type that meets the preset conditions. Among them, the preset conditions can also be understood as preset network constraints. The preset conditions can be set according to actual needs, and the embodiments of this application are not limited to this.

[0132] The present application also provides a method for creating a slice. Figure 5 As shown, the method includes:

[0133] Step 501: The terminal sends first information to a first function, where the first function is at least used for access and mobility management. The first information is used to request creation of a first network slice, where the first network slice does not belong to a network slice subscribed by the terminal.

[0134] Step 502: After receiving the first information sent by the terminal, the first function sends the first information to the second function, where the second function is at least used to manage and configure network slices;

[0135] Step 503: After receiving the first information sent by the first function, the second function creates the first network slice;

[0136] Step 504: The second function sends sixth information to the first function, where the sixth information is used to indicate that the first network slice is successfully created.

[0137] Step 505: After the first function receives the sixth information sent by the second function, it sends second information to the terminal, where the second information indicates that the first network slice is successfully created.

[0138] Here, it should be noted that the specific processing procedures of the terminal, the first function and the second function have been described in detail above and will not be repeated here.

[0139] In the slice creation method provided by the embodiment of the present application, a terminal sends a first message to a first function, the first function is at least used for access and mobility management, the first message is used to request the creation of a first network slice, the first network slice does not belong to the network slice subscribed by the terminal; and after the first function receives the first message sent by the terminal, it sends the first message to the second function, the second function is at least used to manage and configure network slices; after the second function receives the first message sent by the first function, it creates the first network slice; and sends a sixth message to the first function, the sixth message is used to indicate that the first network slice is successfully created; after the first function receives the sixth message sent by the second function, it sends a second message to the terminal, the second message indicates that the first network slice is successfully created. In the solution provided by the embodiment of the present application, when the network side has not established the network slice corresponding to the service, the terminal requests the network side to create a network slice, and the network side creates the network slice according to the request. In this way, when the network side has not created the network slice requested by the terminal to access, the terminal can also initiate a request to the network side so that the network side can automatically create the corresponding network slice according to the terminal's request, thereby meeting the terminal's need to access the corresponding network slice; at the same time, the creation process does not require manual participation, so the creation speed is fast, which can effectively improve the user's service experience.

[0140] The present application is described in further detail below with reference to application examples.

[0141] In this application example, if Figure 6 As shown in the figure, the quick slice creation process includes the following steps:

[0142] Step 601: The UE sends a registration request message to the AMF, requesting access to the network slice;

[0143] Here, in actual application, the UE can specifically send registration request information (i.e., the above-mentioned third information) to the AMF (i.e., the above-mentioned first function) through the RAN. The registration request information (which can also be understood as a registration request message) can specifically include (can also be understood as carrying) parameters such as the request type, terminal identifier (such as SUPI, etc.), and network slice (i.e., the above-mentioned first network slice) identifier (such as NSSAI, etc.).

[0144] Step 602: If the AMF does not have the subscription data information of the terminal, the AMF may send a subscription data request to the UDM and receive the subscription data information sent by the UDM;

[0145] In actual application, the AMF can send a request for contract data information to the UDM through the authentication service function (AUSF, Authentication Server Function), and the request for contract data information can include a terminal identifier (such as SUPI).

[0146] In actual application, AMF can specifically obtain the contract data information of the terminal by calling the Nudm_SDM_Get service in UDM. That is, after UDM receives the information sent by AMF to call the Nudm_SDM_Get service, it returns a response message to AMF, and the response information includes the network slice information signed by the terminal (such as single network slice selection assistance information (S-NSSAI, Single Network Slice Selection Assistance information)).

[0147] Step 603: The AMF determines whether the AMF can provide network slicing services for the terminal based on the terminal's subscription data information, registration request information, and network slice information supported by the AMF.

[0148] When the AMF accessed by the terminal is capable of providing network slicing services for the terminal, the terminal is connected to the network slice requested by the terminal;

[0149] When the AMF accessed by the terminal cannot provide network slicing services for the terminal, the AMF queries the NSSF for the network slice to be accessed;

[0150] Here, in actual application, the terminal can send query (also understood as search) information to NSSF to query whether the network slice requested by the terminal to access has been created on the network side. The query information may specifically include parameters such as the network slice identifier of the network slice requested to access by the terminal and the network slice identifier of the network slice subscribed by the terminal.

[0151] In actual application, AMF can specifically obtain the query results related to the network slice requested for access by calling the Nnssf_NSSelection_Get service in NSSF.

[0152] Step 604: NSSF queries the network slice requested for access and sends the query result to AMF;

[0153] In actual application, after NSSF receives the information sent by AMF to call the Nnssf_NSSelection_Get service, it queries the network slice requested for access and returns the query result information to AMF. Specifically, if the network side has created the network slice requested for access, the query result information may indicate that the network side has found the network slice requested for access; if the network side has not created the network slice requested for access, the query result information may indicate that the network side has not found the network slice requested for access (which can also be understood as there is no network slice in the network that meets the terminal's requirements).

[0154] Step 605: AMF receives the query result sent by NSSF;

[0155] If the query result indicates that the network side has found the requested network slice, the AMF will connect the terminal to the requested network slice;

[0156] If the query result indicates that the network side does not find the network slice requested for access, the AMF sends a registration rejection message to the terminal;

[0157] Here, in actual application, before the AMF sends a registration rejection message to the terminal, it can also cache the relevant information of the terminal (which can also be understood as context information) so that the AMF can inform the corresponding terminal after the network slice requested by the terminal is created. The relevant information of the terminal may specifically include the identification information of the terminal (such as UE ID, etc.), the communication address information of the terminal (such as IP address, etc.), etc.

[0158] In actual application, the registration rejection message (i.e., the fourth information mentioned above) may specifically include a NAS cause value, and the NAS cause value is used to indicate that the network slice requested to access by the terminal has not been created.

[0159] Step 606: After receiving the registration rejection message sent by the AMF, the terminal sends a request message for creating a network slice to the AMF;

[0160] In actual application, the request information for creating a network slice sent by the terminal to the AMF (that is, the above-mentioned first information, which can be sent through a NAS message) may specifically include: network slice identification information (such as NSSAI, etc.), priority information, initiation request type information, initiation request related information (such as terminal ID, AMF ID, etc.), and slice capability requirement information, etc. Among them, the initiation request type information is used to instruct the network side to automatically create a network slice through the NSMF (that is, the above-mentioned second function), or the network side to create a network slice manually in the background; the slice capability requirement information may specifically include: the maximum number of UEs supported by the slice at the same time, the maximum bandwidth, the slice type (such as eMBB, uRLLC, or mMTC, etc.), the slice lifetime, the slice service area and other parameters.

[0161] In actual application, the terminal can use network characteristics to describe the network slice of business requirements according to actual business needs, thereby obtaining the demand information of the slice capability.

[0162] Step 607: AMF receives and parses the request information for creating a network slice sent by the terminal, and sends the information required for creating the network slice to NSMF;

[0163] In actual application, AMF can parse the request information for creating network slices sent by the terminal (specifically including decapsulation). When the initiation request type information contained in the request information for creating network slices indicates that the network side automatically creates network slices through NSMF, AMF can pass the information required for creating network slices contained in the request information for creating network slices to NSMF.

[0164] Step 608: NSMF creates a network slice and returns a slice creation confirmation message to AMF;

[0165] In actual application, NSMF can complete the creation of network slices (which can also be understood as registration or establishment) by interacting with NSSMF and specific network elements. After the network slice is created, NSMF can return a message of successful slice creation to AMF (that is, the sixth information mentioned above).

[0166] Step 609: After AMF receives the slice creation confirmation message sent by NSMF, it sends a network slice creation success message to the terminal.

[0167] In actual application, AMF can use the cached terminal information to determine the terminal's communication address through RAN (which can also be understood as finding the terminal), and return a message to the terminal indicating that the network slice has been successfully created (i.e., the second information mentioned above). At the same time, AMF can also send a registration request message to the terminal (i.e., the fifth information mentioned above) to request the terminal to register the created network slice.

[0168] The solution provided by the application example of this application is that the terminal initiates the process of accessing the network slice and requests AMF to access a network slice instance; AMF can query NSSF whether the network slice requested for access has been created based on the identifier of the network slice requested for access; after AMF receives the query response fed back by NSSF, if the query response indicates that the network slice has not been created (that is, there is no such network slice instance in the network), AMF rejects the terminal's request to access the network slice, sends a registration rejection message to the terminal, and carries the reason for rejecting access in the registration rejection message (for example, the requested slice does not exist, the network has not been created, etc.); after the terminal receives the registration rejection message, it initiates the process of creating a network slice and requests AMF to create a network slice; after AMF receives the request information for creating a network slice sent by the terminal, it parses the request information and transparently transmits the network slice creation request to NSMF; after NSMF completes the creation of the network slice, it returns a network slice establishment confirmation message to AMF; after AMF receives the slice establishment confirmation message, it returns a slice establishment success message to the terminal, thereby completing the network slice creation process. In this way, even if the network side has not pre-created the network slice that the terminal requests to access, the terminal can initiate a request to the network side, which will automatically create the corresponding network slice based on the terminal's request, thereby meeting the terminal's need to access the corresponding network slice. At the same time, no manual intervention is required, the creation speed is fast, and the user's service experience can be effectively improved. In other words, compared with existing solutions, it can achieve faster, more flexible, and more dynamic network slice creation.

[0169] In order to implement the method on the terminal side of the embodiment of the present application, the embodiment of the present application also provides a slice creation device, which is set on the terminal, such as Figure 7 As shown, the device includes:

[0170] A first sending unit 701 is configured to send first information to a first function, where the first function is at least used for access and mobility management, and the first information is used to request creation of a first network slice, where the first network slice does not belong to a network slice subscribed by the terminal;

[0171] The first receiving unit 702 is used to receive second information sent by the first function, where the second information indicates that the first network slice is successfully created.

[0172] In one embodiment, the first sending unit 701 is further configured to:

[0173] Sending third information to the first function, where the third information is used to request access to the first network slice;

[0174] The first receiving unit 702 is further configured to:

[0175] Receive the fourth information sent by the first function, where the fourth information is used to notify the terminal to refuse access to the first network slice.

[0176] In one embodiment, the first receiving unit 702 is further configured to:

[0177] Receive the fifth information sent by the first function, where the fifth information is used to request the terminal to access the first network slice.

[0178] In one embodiment, the apparatus may further include:

[0179] An access unit is configured to initiate a request for accessing the first network slice based on the fifth information.

[0180] In actual application, the first sending unit 701 and the first receiving unit 702 can be implemented by the communication interface in the slice creation device, and the access unit can be implemented by the processor in the slice creation device combined with the communication interface.

[0181] In order to implement the method of the first function side of the embodiment of the present application, the embodiment of the present application also provides a slice creation device, which is set on the first function, and the first function is at least used for access and mobility management, such as Figure 8 As shown, the device includes:

[0182] The second receiving unit 801 is configured to receive first information sent by a terminal, where the first information is used to request creation of a first network slice, where the first network slice does not belong to the network slice to which the terminal has subscribed;

[0183] The second sending unit 802 is used to send the first information to the second function and receive the sixth information sent by the second function, where the second function is at least used to manage and configure network slices, and the sixth information is used to indicate that the first network slice is successfully created; and send the second information to the terminal, where the second information indicates that the first network slice is successfully created.

[0184] In one embodiment, the second receiving unit 801 is further configured to:

[0185] receiving third information sent by the terminal, where the third information is used to request access to the first network slice;

[0186] The second sending unit 802 is further configured to:

[0187] Send fourth information to the terminal, where the fourth information is used to notify the terminal to refuse access to the first network slice.

[0188] In one embodiment, the second sending unit 802 is further configured to:

[0189] Send fifth information to the terminal, where the fifth information is used to request the terminal to access the first network slice.

[0190] In actual application, the second receiving unit 801 and the second sending unit 802 can be implemented by a communication interface in the slice creation device combined with a processor.

[0191] In order to implement the method of the second function side of the embodiment of the present application, the embodiment of the present application also provides a slice creation device, which is set on the second function, and the second function is at least used to manage and configure network slices, such as Figure 9 As shown, the device includes:

[0192] The third receiving unit 901 is configured to receive first information sent by a first function, where the first information is used to request creation of a first network slice, where the first network slice does not belong to a network slice subscribed by the terminal;

[0193] A creating unit 902, configured to create the first network slice;

[0194] The third sending unit 903 is used to send sixth information to the first function, and the sixth information is used to indicate that the first network slice is successfully created.

[0195] In actual application, the third receiving unit 901 and the third sending unit 903 can be implemented by a communication interface in the slice creation device, and the creation unit 902 can be implemented by a processor in the slice creation device.

[0196] It should be noted that the slice creation device provided in the above embodiment only uses the division of the above program units as an example to illustrate slice creation. In actual applications, the above processing can be assigned to different program units as needed, that is, the internal structure of the device can be divided into different program units to complete all or part of the processing described above. In addition, the slice creation device provided in the above embodiment and the slice creation method embodiment are based on the same concept. The specific implementation process is detailed in the method embodiment and will not be repeated here.

[0197] Based on the hardware implementation of the above program modules, and in order to implement the method of the terminal side of the embodiment of the present application, the embodiment of the present application also provides a terminal, such as Figure 10 As shown, the terminal 1000 includes:

[0198] The first communication interface 1001 is capable of exchanging information with other devices;

[0199] A first processor 1002 is connected to the first communication interface 1001 to implement information exchange with other devices, and is used to execute the methods provided by one or more technical solutions on the terminal side when running a computer program;

[0200] The first memory 1003 , on which the computer program is stored.

[0201] Specifically, the first communication interface 1001 is used to:

[0202] Send first information to a first function, where the first function is at least used for access and mobility management, and the first information is used to request the creation of a first network slice, which does not belong to the network slice subscribed to by the terminal; receive second information sent by the first function, where the second information indicates that the first network slice is successfully created.

[0203] In one embodiment, the first communication interface 1001 is further configured to:

[0204] Sending third information to the first function, where the third information is used to request access to the first network slice;

[0205] Receive the fourth information sent by the first function, where the fourth information is used to notify the terminal to refuse access to the first network slice.

[0206] In one embodiment, the first communication interface 1001 is further configured to:

[0207] Receive the fifth information sent by the first function, where the fifth information is used to request the terminal to access the first network slice.

[0208] In one embodiment, the first processor 1002 is configured to:

[0209] Based on the fifth information, a request to access the first network slice is initiated.

[0210] It should be noted that the specific processing process of the first processor 1002 and the first communication interface 1001 can be understood by referring to the above method.

[0211] Of course, in actual application, the various components in the terminal 1000 are coupled together through the bus system 1004. It is understood that the bus system 1004 is used to realize the connection and communication between these components. In addition to the data bus, the bus system 1004 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clarity, Figure 10 Various buses are labeled as bus system 1004.

[0212] The first memory 1003 in the embodiment of the present application is used to store various types of data to support the operation of the first terminal 1000. Examples of such data include: any computer program used to operate on the terminal 1000.

[0213] The methods disclosed in the above embodiments of the present application can be applied to the first processor 1002 or implemented by the first processor 1002. The first processor 1002 may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method can be completed by hardware integrated logic circuits in the first processor 1002 or instructions in software form. The above first processor 1002 may be a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The first processor 1002 can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. A general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium located in the first memory 1003. The first processor 1002 reads the information in the first memory 1003 and completes the steps of the above method in combination with its hardware.

[0214] In an exemplary embodiment, the terminal 1000 may be implemented by one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontrollers (MCUs), microprocessors, or other electronic components to execute the aforementioned method.

[0215] Based on the hardware implementation of the above program modules, and in order to implement the method of the first functional side of the embodiment of the present application, the embodiment of the present application also provides a first function, which is at least used for access and mobility management, such as Figure 11 As shown, the first function 1100 includes:

[0216] The second communication interface 1101 is capable of exchanging information with other devices;

[0217] A second processor 1102 is connected to the second communication interface 1101 to implement information exchange with other devices, and is used to execute the methods provided by one or more technical solutions of the first functional side when running a computer program;

[0218] The second memory 1103 , on which the computer program is stored.

[0219] Specifically, the second processor 1102 is configured to:

[0220] In conjunction with the second communication interface 1101, first information sent by the terminal is received, where the first information is used to request creation of a first network slice, where the first network slice does not belong to the network slice subscribed by the terminal;

[0221] sending the first information to a second function, and receiving sixth information sent by the second function, where the second function is at least used to manage and configure network slices, and the sixth information is used to indicate that the first network slice is successfully created;

[0222] Sending second information to the terminal, wherein the second information indicates that the first network slice is successfully created.

[0223] In one embodiment, the second communication interface 1101 is further configured to:

[0224] receiving third information sent by the terminal, where the third information is used to request access to the first network slice;

[0225] Send fourth information to the terminal, where the fourth information is used to notify the terminal to refuse access to the first network slice.

[0226] In one embodiment, the second communication interface 1101 is further configured to:

[0227] Send fifth information to the terminal, where the fifth information is used to request the terminal to access the first network slice.

[0228] It should be noted that the specific processing process of the second processor 1102 and the second communication interface 1101 can be understood by referring to the above method.

[0229] Of course, in actual application, the various components in the first function 1100 are coupled together through the bus system 1104. It is understood that the bus system 1104 is used to realize the connection and communication between these components. In addition to the data bus, the bus system 1104 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clarity, Figure 11 Various buses are labeled as bus system 1104.

[0230] The second memory 1103 in the embodiment of the present application is used to store various types of data to support the operation of the first function 1100. Examples of such data include: any computer program used to operate on the first function 1100.

[0231] The methods disclosed in the above embodiments of the present application can be applied to or implemented by the second processor 1102. The second processor 1102 may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method can be completed by hardware integrated logic circuits or software instructions in the second processor 1102. The above second processor 1102 may be a general-purpose processor, a DSP, or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, etc. The second processor 1102 can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. A general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of the present application can be directly implemented and executed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The software module may be located in a storage medium located in the second memory 1103. The second processor 1102 reads the information in the second memory 1103 and, in conjunction with its hardware, completes the steps of the above method.

[0232] In an exemplary embodiment, the first function 1100 may be implemented by one or more ASICs, DSPs, PLDs, CPLDs, FPGAs, general-purpose processors, controllers, MCUs, Microprocessors, or other electronic components to perform the aforementioned method.

[0233] Based on the hardware implementation of the above program module, and in order to implement the method of the second functional side of the embodiment of the present application, the embodiment of the present application also provides a second function, which is at least used to manage and configure network slices, such as Figure 12 As shown, the second function 1200 includes:

[0234] The third communication interface 1201 is capable of exchanging information with other devices;

[0235] A third processor 1202 is connected to the third communication interface 1201 to implement information exchange with other devices, and is used to execute the methods provided by one or more technical solutions of the second functional side when running a computer program;

[0236] The third memory 1203 , on which the computer program is stored.

[0237] Specifically, the third communication interface 1201 is used to:

[0238] receiving first information sent by a first function, where the first information is used to request creation of a first network slice, where the first network slice does not belong to a network slice subscribed by the terminal;

[0239] Sending sixth information to the first function, where the sixth information is used to indicate that the first network slice is successfully created;

[0240] The third processor 1202 is configured to:

[0241] Create the first network slice.

[0242] It should be noted that the specific processing process of the third processor 1202 and the third communication interface 1201 can be understood by referring to the above method.

[0243] Of course, in actual application, the various components in the second function 1200 are coupled together through the bus system 1204. It can be understood that the bus system 1204 is used to realize the connection and communication between these components. In addition to the data bus, the bus system 1204 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clarity, Figure 12 Various buses are labeled as bus system 1204.

[0244] The third memory 1203 in the embodiment of the present application is used to store various types of data to support the operation of the second function 1200. Examples of such data include: any computer program used to operate on the second function 1200.

[0245] The methods disclosed in the above embodiments of the present application can be applied to or implemented by the third processor 1202. The third processor 1202 may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method can be completed by hardware integrated logic circuits or software instructions in the third processor 1202. The third processor 1202 may be a general-purpose processor, a DSP, or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, etc. The third processor 1202 can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. A general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of the present application can be directly implemented and executed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The software modules may be located in a storage medium located in the third memory 1203. The third processor 1202 reads the information in the third memory 1203 and, in conjunction with its hardware, completes the steps of the above method.

[0246] In an exemplary embodiment, the second function 1200 may be implemented by one or more ASICs, DSPs, PLDs, CPLDs, FPGAs, general-purpose processors, controllers, MCUs, Microprocessors, or other electronic components to perform the aforementioned method.

[0247] It can be understood that the memory (first memory 1003, second memory 1103, third memory 1203) of the embodiment of the present application can be a volatile memory or a non-volatile memory, and can also include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic random access memory (FRAM), a flash memory, a magnetic surface memory, an optical disc, or a compact disc read-only memory (CD-ROM); the magnetic surface memory can be a magnetic disk memory or a tape memory. The volatile memory can be a random access memory (RAM), which is used as an external cache.By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), synchronous static random access memory (SSRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct rambus random access memory (DRRAM). The memory described in the embodiments of the present application is intended to include, but is not limited to, these and any other suitable types of memory.

[0248] In an exemplary embodiment, the present application also provides a storage medium, namely a computer storage medium, specifically a computer-readable storage medium, which includes, for example, a first memory 1003 storing a computer program, which can be executed by the first processor 1002 of the terminal 1000 to complete the steps of the terminal-side method described above. For another example, it includes a second memory 1103 storing a computer program, which can be executed by the second processor 1102 of the first function 1100 to complete the steps of the first function-side method described above. For another example, it includes a third memory 1203 storing a computer program, which can be executed by the third processor 1202 of the second function 1200 to complete the steps of the second function-side method described above. The computer-readable storage medium can be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface storage, optical disk, or CD-ROM.

[0249] In an exemplary embodiment, the embodiment of the present application also provides a computer program product, including a computer program, which can be executed by the first processor 1002 of the terminal 1000 to complete the steps of the aforementioned terminal-side method, or, the computer program can be executed by the second processor 1102 of the first function 1100 to complete the steps of the aforementioned first-function-side method, or, the computer program can be executed by the third processor 1202 of the second function 1200 to complete the steps of the aforementioned second-function-side method.

[0250] In order to implement the method of the embodiment of the present application, the embodiment of the present application also provides a slice creation system, such as Figure 13 As shown, the system includes: a terminal 1301 , a first function 1302 , and a second function 1303 .

[0251] Here, it should be noted that the specific processing procedures of the terminal 1301, the first function 1302, and the second function 1303 have been described in detail above and will not be repeated here.

[0252] It should be noted that: "first", "second", etc. are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0253] In addition, the technical solutions described in the embodiments of the present application can be arbitrarily combined without conflict.

[0254] The above description is merely a preferred embodiment of the present application and is not intended to limit the scope of protection of the present application.

Claims

1. A slice creation method, characterized in that: Applied to terminals, including: Sending first information to a first function, where the first function is at least used for access and mobility management, and the first information is used to request creation of a first network slice, where the first network slice does not belong to the network slice subscribed by the terminal; Receive second information sent by the first function, where the second information indicates that the first network slice is successfully created.

2. The method according to claim 1, characterized in that Before sending the first information to the first function, the method further includes: Sending third information to the first function, where the third information is used to request access to the first network slice; Receive the fourth information sent by the first function, where the fourth information is used to notify the terminal to refuse access to the first network slice.

3. The method according to claim 1 or 2, characterized in that When receiving the second information sent by the first function, the method further includes: Receive the fifth information sent by the first function, where the fifth information is used to request the terminal to access the first network slice.

4. A slice creation method, characterized in that: Applied to a first function, the first function being at least for access and mobility management, including: receiving first information sent by a terminal, where the first information is used to request creation of a first network slice, where the first network slice does not belong to the network slice to which the terminal has subscribed; sending the first information to a second function, and receiving sixth information sent by the second function, where the second function is at least used to manage and configure network slices, and the sixth information is used to indicate that the first network slice is successfully created; Sending second information to the terminal, wherein the second information indicates that the first network slice is successfully created.

5. The method according to claim 4, characterized in that Before receiving the first information sent by the terminal, the method further includes: receiving third information sent by the terminal, where the third information is used to request access to the first network slice; Send fourth information to the terminal, where the fourth information is used to notify the terminal to refuse access to the first network slice.

6. The method according to claim 4 or 5, characterized in that When sending the second information to the terminal, the method further includes: Send fifth information to the terminal, where the fifth information is used to request the terminal to access the first network slice.

7. A slice creation method, characterized in that: Applied to the second function, the second function is at least used to manage and configure network slices, including: receiving first information sent by a first function, where the first information is used to request creation of a first network slice, where the first network slice does not belong to a network slice subscribed to by the terminal, and the first function is at least used for access and mobility management; Creating the first network slice; Send sixth information to the first function, where the sixth information is used to indicate that the first network slice is successfully created.

8. A slice creation device, characterized in that: include: A first sending unit is configured to send first information to a first function, where the first function is at least used for access and mobility management, and the first information is used to request creation of a first network slice, where the first network slice does not belong to a network slice subscribed by the terminal; The first receiving unit is used to receive second information sent by the first function, where the second information indicates that the first network slice is successfully created.

9. A slice creation device, characterized in that: include: A second receiving unit is configured to receive first information sent by a terminal, where the first information is used to request creation of a first network slice, where the first network slice does not belong to the network slice to which the terminal has subscribed; The second sending unit is used to send the first information to the second function and receive the sixth information sent by the second function, where the second function is at least used to manage and configure network slices, and the sixth information is used to indicate that the first network slice is successfully created; and send the second information to the terminal, where the second information indicates that the first network slice is successfully created.

10. A slice creation device, characterized in that: include: A third receiving unit is configured to receive first information sent by a first function, where the first information is used to request creation of a first network slice, where the first network slice does not belong to a network slice subscribed to by the terminal, and the first function is used for at least access and mobility management; A creating unit, configured to create the first network slice; The third sending unit is used to send sixth information to the first function, and the sixth information is used to indicate that the first network slice is successfully created.

11. A terminal, characterized in that: include: a first processor and a first communication interface; wherein, The first communication interface is used to send first information to a first function, where the first function is at least used for access and mobility management, and the first information is used to request creation of a first network slice, where the first network slice does not belong to a network slice subscribed by the terminal; Receive second information sent by the first function, where the second information indicates that the first network slice is successfully created.

12. A first function, characterized in that The first function is at least used for access and mobility management, including: a second processor and a second communication interface; wherein, The second communication interface is used to receive first information sent by the terminal, where the first information is used to request the creation of a first network slice, which does not belong to the network slice subscribed by the terminal; send the first information to the second function, and receive sixth information sent by the second function, where the second function is at least used to manage and configure network slices, and the sixth information is used to indicate that the first network slice is successfully created; and send second information to the terminal, where the second information indicates that the first network slice is successfully created.

13. A second function, characterized in that The second function is at least used to manage and configure network slices, including: The third communication interface is configured to receive first information sent by a first function, where the first information is used to request creation of a first network slice, where the first network slice does not belong to a network slice subscribed to by the terminal; and send sixth information to the first function, where the sixth information is used to indicate that the first network slice is successfully created, where the first function is at least used for access and mobility management. The third processor is used to create the first network slice.

14. A terminal, characterized in that: include: a first processor and a first memory for storing a computer program capable of being executed on the processor, Wherein, when the first processor is used to run the computer program, it executes the steps of the method according to any one of claims 1 to 3.

15. A first function, characterized in that include: a second processor and a second memory for storing a computer program capable of being executed on the processor, Wherein, when the second processor is used to run the computer program, it executes the steps of the method according to any one of claims 4 to 6.

16. A second function, characterized in that include: a third processor and a third memory for storing a computer program capable of being executed on the processor, Wherein, the third processor is configured to execute the steps of the method according to claim 7 when running the computer program.

17. A storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 3, or implements the steps of the method according to any one of claims 4 to 6, or implements the steps of the method according to claim 7.

18. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 3, or implements the steps of the method according to any one of claims 4 to 6, or implements the steps of the method according to claim 7.

Images