Method, terminal, platform, device and storage medium for providing slice service in stages

Abstract

The application provides a method for providing slice services in stages, a user terminal, a service platform, computer equipment and a storage medium, and relates to the technical field of communication. The method comprises the following steps: the user terminal sends a slice subscription request to the service platform, so that the service platform generates corresponding slice service information for an application based on the slice subscription request and delivers the slice service information to the user terminal; the slice service information corresponding to the application is received, and a scenario set for a slice by a user is acquired; in response to the user using the application, a slice identifier conforming to a current scenario is selected from the slice service information based on the current scenario of the application and the scenario set for the slice by the user; and the application is provided with slice services by using the slice corresponding to the slice identifier conforming to the current scenario. The technical scheme provided by the application can realize slice services used in stages by different users in different scenarios of the same application, and meets different network quality requirements of users in different scenarios of the same application.

Description

Technical Field

[0001] This invention relates to the field of communication technology, and in particular to a method for providing tiered slicing services, a user terminal, a service platform, a computer device, and a computer-readable storage medium. Background Technology

[0002] 5G (5th Generation Mobile Communication Technology) slicing is one of the most distinctive innovative capabilities of 5G. It can flexibly allocate network resources and build networks on demand. Based on a unified physical network, it divides the network into multiple logically independent virtual networks. Each network slice is an isolated end-to-end network, which fully meets the differentiated network quality needs of different users and their different applications (APPs).

[0003] Currently, users often have different network quality requirements for different scenarios within the same application, necessitating different network slicing services. For example, in social applications, some of a user's friends are clients, requiring high-quality network communication with them, while the remaining friends are relatives or casual acquaintances, requiring only general-quality network communication. Similarly, in gaming applications, high-quality network communication is needed for battle scenarios, while general-quality network communication is sufficient for daily tasks. However, existing slicing solutions can only provide a single slice service for the same application, failing to offer different slice services based on different scenarios within the same application, thus failing to meet user needs. Summary of the Invention

[0004] This invention was completed in order to at least partially solve the technical problem in the prior art that only a single slice service can be provided for the same application, and that different slice services cannot be provided to users according to different scenarios of the same application.

[0005] According to one aspect of the present invention, a method for providing tiered slicing services is provided, applied to a user terminal, the method comprising:

[0006] A slice ordering request is sent to the service platform. The slice ordering request includes user information, application information, and slice ordering information. The slice ordering information includes the number of slices required by the application, slice performance, and corresponding priority. This enables the service platform to generate corresponding slice service information for the application based on the slice ordering request and send it to the user terminal. The slice service information corresponding to the application includes the application information, the slice identifier of the slice configured for the application based on the slice performance, and the corresponding priority.

[0007] Receive the slice service information corresponding to the application, and obtain the scenario set by the user for the slice identifier in the slice service information;

[0008] In response to a user using the application, a slice identifier matching the current scenario is selected from the slice service information based on the current scenario of the application and the scenario set by the user for the slice identifier in the slice service information; and,

[0009] The application is provided with slicing services using the slice corresponding to the slice identifier that matches the current scenario.

[0010] Optionally, before sending a slice ordering request to the service platform, the following steps are also included:

[0011] Obtain user slice request information and user information. The slice request information includes application information that needs to use the slice service, the number of slices required by the application, slice performance, and corresponding priority; and...

[0012] A slice ordering request is generated based on the slice demand information and user information.

[0013] Optionally, the slice ordering information may also include the number of users in the scene corresponding to the slice performance required by the application; the slice service information corresponding to the application may also include the number of users in the scene corresponding to the slice identifier.

[0014] After receiving the slice service information corresponding to the application, the following is also included:

[0015] The number of scenario users set by a user for a slice identifier in the slice service information is obtained, and the number of scenario users set for the same slice identifier does not exceed the number of scenario users in the slice service information.

[0016] Optionally, after receiving the slice service information corresponding to the application, the method further includes:

[0017] The application sends the slice service information corresponding to the application to the application, so that the application prompts the user to set a scene for the slice identifier in the slice service information based on the slice service information.

[0018] The scenario of obtaining the slice identifier set by the user in the slice service information includes:

[0019] The scenario where the user sets the slice identifier in the slice service information according to the prompts of the application.

[0020] Optionally, after obtaining the scenario where the user sets the slice identifier in the slice service information, the method further includes:

[0021] The scenarios set by the user for the slice identifier in the slice service information are stored in the local database;

[0022] In response to a user using the application, the system retrieves the slice identifier set by the user in the slice service information from the local database.

[0023] Alternatively, after obtaining the scenario where the user sets the slice identifier in the slice service information, the method further includes:

[0024] The scenario set by the user for the slice identifier in the slice service information is stored in the local database and uploaded to the application platform corresponding to the application.

[0025] In response to a user using the application, the system searches the local database for the slice identifier set by the user in the slice service information.

[0026] In response to a scenario where no user-defined slice identifier in the slice service information is found in the local database, a scenario query request is sent to the application platform. This scenario query request includes the slice identifier from the slice service information. The application platform then searches for the scenario set by the user for the slice identifier in the slice service information based on the scenario query request and returns the query result to the user terminal.

[0027] Receive query results sent by the application platform and store them in a local database.

[0028] According to another aspect of the present invention, a method for providing tiered slicing services is provided, applied to a service platform, the method comprising:

[0029] Receive a slice ordering request sent by a user terminal. The slice ordering request includes user information, application information, and slice ordering information. The slice ordering information includes the number of slices required by the application, slice performance, and corresponding priority.

[0030] Based on the slice ordering request, corresponding slice service information is generated for the application. The slice service information for the application includes the application information, the slice identifier and corresponding priority of the slice configured for the application based on the slice performance, and...

[0031] The slice service information is sent to the user terminal so that after receiving the slice service information corresponding to the application, the user terminal can obtain the scenario set by the user for the slice identifier in the slice service information, and in response to the user using the application, select a slice identifier that matches the current scenario from the slice service information based on the current scenario of the application and the scenario set by the user for the slice identifier in the slice service information, and use the slice corresponding to the slice identifier that matches the current scenario to provide slice services for the application.

[0032] According to another aspect of the present invention, a user terminal is provided, comprising:

[0033] The first sending module is configured to send a slice ordering request to the service platform. The slice ordering request includes user information, application information, and slice ordering information. The slice ordering information includes the number of slices required by the application, the slice performance, and the corresponding priority. This enables the service platform to generate corresponding slice service information for the application based on the slice ordering request and send it to the user terminal. The slice service information corresponding to the application includes the application information, the slice identifier of the slice configured for the application based on the slice performance, and the corresponding priority.

[0034] The first receiving module is configured to receive the slice service information corresponding to the application and obtain the scenario set by the user for the slice identifier in the slice service information;

[0035] The selection module is configured to, in response to a user using the application, select a slice identifier from the slice service information that matches the current scenario based on the application's current scenario and the scenario set by the user for the slice identifier in the slice service information; and,

[0036] The service providing module is configured to provide slice services to the application using the slice corresponding to the slice identifier that matches the current scenario.

[0037] According to another aspect of the present invention, a service platform is provided, comprising:

[0038] The second receiving module is configured to receive a slice ordering request sent by a user terminal. The slice ordering request includes user information, application information, and slice ordering information. The slice ordering information includes the number of slices required by the application, slice performance, and corresponding priority.

[0039] An information generation module is configured to generate corresponding slice service information for the application based on the slice ordering request; and,

[0040] The second sending module is configured to send the slice service information to the user terminal. The slice service information corresponding to the application includes the application information, a slice identifier configured for the application based on the slice performance, and the corresponding priority. This allows the user terminal to obtain the scenario set by the user for the slice identifier in the slice service information after receiving the slice service information. In response to the user using the application, the module selects a slice identifier that matches the current scenario from the slice service information based on the current scenario of the application and the scenario set by the user for the slice identifier in the slice service information. The module then uses the slice corresponding to the slice identifier that matches the current scenario to provide slice services to the application.

[0041] According to another aspect of the present invention, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and when the processor runs the computer program stored in the memory, the processor performs the aforementioned method for providing tiered slicing services.

[0042] According to another aspect of the present invention, a computer-readable storage medium is provided having a computer program stored thereon, wherein when the computer program is executed by a processor, the processor performs the aforementioned method for providing tiered slicing services.

[0043] The technical solution provided by this invention may include the following beneficial effects:

[0044] The present invention provides a method for providing tiered slicing services. A user terminal sends a slice subscription request to a service platform, including the number of slices required by a specified application, slice performance, and corresponding priority. The service platform configures corresponding slice service information for the application based on the slice subscription request and returns it to the user terminal. The user terminal then sets corresponding scenarios for slices with different performance levels. Subsequently, when a user uses an application with subscribed slice services, the user terminal can provide the application with slice services of performance corresponding to the current scenario. This allows for tiered use of slice services by users in different scenarios for the same application, satisfying users' varying network quality requirements for the same application in different scenarios.

[0045] Other features and advantages of the invention will be set forth in the description which follows, and will be apparent in part from the description, or may be learned by practicing the invention. The objects and other advantages of the invention may be realized and obtained by means of the structures particularly pointed out in the description, claims, and drawings. Attached Figure Description

[0046] The accompanying drawings are provided to further understand the technical solutions of the present invention and constitute a part of the specification. They are used together with the embodiments of the present invention to explain the technical solutions of the present invention, and do not constitute a limitation on the technical solutions of the present invention.

[0047] Figure 1 A flowchart illustrating a method for providing tiered slicing services according to an embodiment of the present invention;

[0048] Figure 2 A flowchart illustrating another method for providing tiered slicing services according to an embodiment of the present invention;

[0049] Figure 3 A flowchart illustrating another method for providing tiered slicing services according to an embodiment of the present invention;

[0050] Figure 4 This is a schematic diagram of the structure of a user terminal provided in an embodiment of the present invention;

[0051] Figure 5 A schematic diagram of the structure of the service platform provided in an embodiment of the present invention;

[0052] Figure 6 A schematic diagram of the structure of a system for providing hierarchical slicing services according to an embodiment of the present invention;

[0053] Figure 7 This is a schematic diagram of the structure of a computer device provided in an embodiment of the present invention. Detailed Implementation

[0054] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the specific implementation methods of the present invention will be described in detail below with reference to the accompanying drawings. It should be understood that the specific implementation methods described herein are for illustration and explanation only and are not intended to limit the present invention.

[0055] To address the issue that existing technologies can only provide a single slice service for the same application, a solution can be sought from the perspective of identifying the slice used by the application in order to provide different slice services to users based on different scenarios of the same application.

[0056] Currently, the main methods for identifying application slices include APP ID (Application ID), FQDN (Fully Qualified Domain Name), target IP triplet, and DNN (Data Network Name). APP ID is the identity identifier of the application on the terminal, providing APP-level slice services. FQDN is the target server network domain name information requested by the application on the terminal, providing domain address-level slice services. Target IP triplet is the address information of the target server requested by the application on the terminal, providing IP address-level slice services. DNN is the data network gateway name used by the application on the terminal, providing session connection-level slice services. However, the APP ID and DNN-based methods are too coarse-grained, making it difficult to meet the need for further segmentation of application scenarios and corresponding slice services within the same application. The FQDN and target IP triplet-based methods are too fine-grained; for large applications with a huge number of target domain names and target IPs, configuring slices based on this leads to lengthy and difficult slice configuration tables.

[0057] To address the shortcomings of existing methods for identifying slices used in applications, this invention proposes a scheme for users to use slice services in different scenarios within the same application at different levels. This is described in detail below through specific embodiments.

[0058] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence; furthermore, in the absence of conflict, the embodiments and features in the embodiments of this invention can be arbitrarily combined with each other. In the following description, the use of suffixes such as "module," "part," or "unit" to represent elements is only for the convenience of the description of this invention and has no specific meaning in itself. Therefore, "module," "part," or "unit" can be used interchangeably. The slice mentioned in this invention is a dedicated network slice.

[0059] Figure 1 This is a flowchart illustrating a method for providing tiered slicing services according to an embodiment of the present invention. The method is applied to a user terminal, which can be a smartphone or other mobile communication device supporting carrier cards; the present invention does not limit this. Figure 1 As shown, the method includes the following steps S101 to S105.

[0060] S101. Send a slice ordering request to the service platform. The slice ordering request includes user information, application information, and slice ordering information. The slice ordering information includes the number of slices required by the application, slice performance, and corresponding priority, so that the service platform generates corresponding slice service information for the application based on the slice ordering request and sends it to the user terminal. The slice service information corresponding to the application includes the application information, the slice identifier of the slice configured for the application based on the slice performance, and the corresponding priority.

[0061] In this step, user information includes the user's mobile phone number or other information that can identify the user, such as IMSI (International Mobile Subscriber Identity).

[0062] Application information includes the application's identity identifier, such as the application's package name.

[0063] The slice ordering information includes the number of slices required by the application, the performance of each slice, and the priority of each slice's performance. The number of slices refers to the number of slices corresponding to the same application; slice performance includes factors such as speed, latency, and security; and the priority of slice performance refers to the priority assigned to slices with different performance levels when the user orders the slices.

[0064] For example, if user A subscribes to two slices for application B, with the slice performance and corresponding priorities being "high-performance slice 1 - first priority" and "general performance slice 2 - second priority" respectively, then the slice subscription request sent by the user terminal to the service platform includes "user A's mobile phone number - application B's identity identifier - 2 slices - high-performance slice 1 (first priority) - general performance slice 2 (second priority)".

[0065] In the slice service information corresponding to the application generated by the service platform, the number of slice identifiers is the same as the number of slices in the slice ordering request; each slice identifier is a slice identifier configured based on the performance of each slice in the slice ordering request; the priority corresponding to the slice identifier refers to the priority specified for the slice identifier configured for slices with different performance, and should correspond to the priority specified in the slice ordering request.

[0066] For example, the service platform generates slice service information for user A, including "Application B identity identifier - slice identifier of high-performance slice 1 (first priority) - slice identifier of general performance slice 2 (second priority)", and sends it to the user terminal.

[0067] S102. Receive the slice service information corresponding to the application.

[0068] S103. Obtain the scenario where the user sets the slice identifier in the slice service information.

[0069] In this step, if the user has subscribed to multiple slices for the same application, the user needs to set up corresponding scenarios for each slice separately.

[0070] For example, if application B is a social application, the user needs to set application scenarios for the slice identifier of high-performance slice 1 (first priority) and the slice identifier of general performance slice 2 (second priority) corresponding to application B. The user can set the slice identifier of high-performance slice 1 (first priority) for communication with some friends (such as clients), and the slice identifier of general performance slice 2 (second priority) for communication with other friends. As another example, if application B is a game application, the user can set the slice identifier of high-performance slice 1 (first priority) for game battle scenarios, and the slice identifier of general performance slice 2 (second priority) for other game scenarios.

[0071] S104. In response to the user using the application, select a slice identifier that matches the current scenario from the slice service information based on the current scenario of the application and the scenario set by the user for the slice identifier in the slice service information.

[0072] S105. Use the slice corresponding to the slice identifier that matches the current scenario to provide slice services for the application.

[0073] For example, when user A uses application B to request communication with a client, based on the current scenario and the scenario settings set by the user for different slice identifiers, the slice identifier of high-performance slice 1 is selected, and the slice corresponding to the slice identifier of high-performance slice 1 is used to provide services to application B.

[0074] In this embodiment, the slice subscription request sent by the user terminal to the service platform includes the number of slices required by the application, the slice performance, and the corresponding priority. The service platform can then configure a corresponding number of slices for the application based on the number of slices required by the application, and the configured slices meet the slice performance in the request. It also configures corresponding priorities for slices with different performance to distinguish between different slice performances. Then, it generates slice service information corresponding to the application based on the configuration results and returns it to the user terminal to set the corresponding scenario for slices with different performances. When the user uses the application that has subscribed to the slice service, the application can be provided with slice service with slice performance corresponding to the current scenario, so as to realize the hierarchical use of slice service by users of the same application in different scenarios.

[0075] In one specific embodiment, before step S101, the following steps S106 and S107 are further included.

[0076] S106. Obtain user's slice requirement information and user information. The slice requirement information includes application information that needs to use slice services, the number of slices that the application needs to use, slice performance, and corresponding priority.

[0077] S107. Generate a slice ordering request based on the slice demand information and user information.

[0078] In this embodiment, when a user orders a slice, the terminal can display a slice ordering page. The user can directly input their slice request information on the slice ordering page; the page can also display information about all applications that can use the slice service, the number of slices required by each application, the slice performance and priority of each slice required by the same application, and the application information, slice performance, and priority can be selected on the slice ordering page according to the user's needs. After obtaining the user's slice request information, a slice ordering request can be generated based on the user's slice request information and user information.

[0079] In one specific implementation, the slice ordering information further includes the number of scenario users corresponding to the slice performance required by the application; the slice service information corresponding to the application further includes the number of scenario users corresponding to the slice identifier. Here, the number of scenario users refers to the number of users who can use the same slice service in different scenarios for a particular application, such as the number of friends communicating with a user in different scenarios within a social application.

[0080] Accordingly, step S108 is included after step S102.

[0081] S108. Obtain the number of scene users set by the user for the slice identifier in the slice service information, and the number of scene users set for the same slice identifier user does not exceed the number of scene users in the slice service information.

[0082] In this embodiment, when a user orders a slice, in addition to setting the number of slices required by the application, the slice performance and the corresponding priority, the number of scene users corresponding to different slice performances can also be set. Then, when the user sets a scene for the slice identifier in the slice service information corresponding to the application, the number of scene users set for each slice identifier cannot exceed the number of scene users corresponding to the slice performance when the slice is ordered.

[0083] For example, when user A subscribes to a slice, they set the number of users in the scenario corresponding to high-performance slice 1 (first priority) of social application B to 10. Then, when subsequent users set the scenario corresponding to high-performance slice 1, they can only set the slice identifier (first priority) of high-performance slice 1 to be used for communication with no more than N (e.g., 10) friends.

[0084] In one specific embodiment, after step S102, the following step S109 is also included.

[0085] S109. Send the slice service information corresponding to the application to the application, so that the application prompts the user to set a scene for the slice identifier in the slice service information based on the slice service information.

[0086] Accordingly, step S103 specifically includes:

[0087] The scenario where the user sets the slice identifier in the slice service information according to the prompts of the application.

[0088] In this embodiment, after receiving the slice service information corresponding to the application issued by the service platform, the user terminal sends the slice service information to the corresponding application on the terminal. The application then prompts the user to set the scene corresponding to the slice and receives the user's setting result for the scene, thus obtaining the scene set by the user for the slice identifier in the slice service information.

[0089] In one alternative embodiment, step S103 is followed by step S110a.

[0090] S110a. Store the scenario set by the user for the slice identifier in the slice service information in the local database.

[0091] Accordingly, step S104 also includes step A1.

[0092] A1. In response to a user using the application, retrieve the scenario set by the user for the slice identifier in the slice service information from the local database. Then, perform the step of selecting a slice identifier that matches the current scenario.

[0093] In this embodiment, the scenario set by the user for the slice identifier in the slice service information can be stored locally. When the user uses the application later, the scenario corresponding to the slice identifier can be found from the local database, and then the slice identifier that matches the current scenario can be selected.

[0094] In another alternative embodiment, step S103 is followed by step S110b.

[0095] S110b. Upload the scenario set by the user for the slice identifier in the slice service information to the application platform corresponding to the application.

[0096] Accordingly, step S104 also includes steps B1 and B2.

[0097] B1. In response to a user using the application, a scenario query request is sent to the application platform. The scenario query request includes a slice identifier in the slice service information, so that the application platform can find the scenario set by the user for the slice identifier in the slice service information based on the scenario query request, and return the query result to the user terminal.

[0098] B2. Receive the query results sent by the application platform. Then, execute the step of selecting the slice identifier that matches the current scenario.

[0099] In this embodiment, the scenarios set by the user for the slice identifier in the slice service information can also be stored on the application platform. When the user uses the application later, he / she can request the scenario corresponding to the slice identifier from the application platform and then select the slice identifier that matches the current scenario.

[0100] In another alternative embodiment, step S103 is followed by step S110c.

[0101] S110c. Store the scenario set by the user for the slice identifier in the slice service information in the local database and upload it to the application platform corresponding to the application.

[0102] Accordingly, step S104 also includes the following steps C1 to C3.

[0103] C1. In response to a user using the application, a scenario is found in the local database where the user sets a slice identifier for the slice service information;

[0104] C2. In response to the scenario where no user-defined slice identifier in the slice service information is found in the local database, a scenario query request is sent to the application platform. The scenario query request includes the slice identifier in the slice service information, so that the application platform can find the scenario set by the user for the slice identifier in the slice service information based on the scenario query request, and return the query result to the user terminal.

[0105] C3. Receive the query results sent by the application platform and store them in the local database. Then, execute the step of selecting the slice identifier that matches the current scenario.

[0106] In this embodiment, the scenarios set by the user for the slice identifier in the slice service information can be stored simultaneously on both the local machine and the application platform. When the user uses the application later, they can first search for the scenario corresponding to the slice identifier locally. If found, the slice identifier matching the current scenario can be selected based on the search results. If not found, the application platform is requested to select the scenario corresponding to the slice identifier to match the current scenario. Thus, even after the user changes their terminal or clears local storage, the application platform can be requested to retrieve the user's scenario settings.

[0107] Figure 2 This is a flowchart illustrating another method for providing tiered slicing services according to an embodiment of the present invention. The method is applied to a service platform, which includes an operator platform and may also include an application platform. The application platform may be located within the operator platform or independently of it. Figure 2 As shown, the method includes the following steps S201 to S203.

[0108] S201. Receive a slice ordering request sent by a user terminal. The slice ordering request includes user information, application information, and slice ordering information. The slice ordering information includes the number of slices required by the application, slice performance, and corresponding priority.

[0109] In this step, user information includes the user's mobile phone number or other information that can identify the user, such as IMSI. Application information includes the application's identity identifier, such as the application's package name. Slice ordering information includes the number of slices the application needs to use, the slice performance of each slice the application needs, and the priority corresponding to each slice performance. Specifically, the number of slices refers to the number of slices corresponding to the same application; slice performance includes slice speed, latency, security, etc.; and the priority corresponding to slice performance refers to the priority assigned to slices with different performance levels when the user orders slices.

[0110] S202. Generate corresponding slice service information for the application based on the slice ordering request. The slice service information corresponding to the application includes the application information, the slice identifier and corresponding priority of the slice configured for the application based on the slice performance.

[0111] In this step, after receiving a user's slice subscription request, the service platform needs to configure a slice identifier that meets the user's slice performance requirements, and then generate the slice service information corresponding to the application. If the user subscribes to multiple slices for the same application, the slice service information corresponding to the application should include multiple slice identifiers and their corresponding priorities.

[0112] In the slice service information corresponding to the application generated by the service platform, the number of slice identifiers is the same as the number of slices in the user's slice ordering request; each slice identifier is a slice identifier configured based on the slice performance in the user's slice ordering request; the priority corresponding to the slice identifier refers to the priority specified for the slice identifier configured for slices with different performance, and should correspond to the priority specified in the slice ordering request.

[0113] S203. The slice service information is sent to the user terminal so that after receiving the slice service information corresponding to the application, the user terminal obtains the scenario set by the user for the slice identifier in the slice service information, and in response to the user using the application, selects a slice identifier that matches the current scenario from the slice service information based on the current scenario of the application and the scenario set by the user for the slice identifier in the slice service information, and provides slice services to the application using the slice corresponding to the slice identifier that matches the current scenario.

[0114] In this embodiment, after receiving a slice subscription request from a user terminal, the service platform can configure a corresponding number of slices for the application based on the number of slices required by the application, the slice performance, and the corresponding priority, since the slice subscription request includes the number of slices required by the application, the slice performance meets the requirements in the request, and the service platform can configure corresponding priorities for slices with different performance to distinguish between different slice performances. Then, based on the configuration results, the service platform generates slice service information corresponding to the application and returns it to the user terminal to set the corresponding scenario for slices with different performances. When the user uses the application that has subscribed to the slice service, the application can be provided with slice service with the slice performance corresponding to the current scenario, so as to realize the hierarchical use of slice service by users of the same application in different scenarios.

[0115] Figure 3 This is a flowchart illustrating another method for providing tiered slicing services according to an embodiment of the present invention. Figure 3 As shown, the method includes the following steps S301 to S304.

[0116] S301. When a user orders a slice, the user selects the application that needs to use the slice, the number of slices to be used, the slice performance, and the corresponding priority. The user terminal uploads user information, application information, and slice ordering information to the platform.

[0117] In this step, the number of slices refers to the number of slices corresponding to the same application; slice performance includes slice speed, latency, security, etc.; slice performance and corresponding priority refer to the priority that users need to specify for slices with different performance when ordering slices.

[0118] User information can be the user's mobile phone number; application information can be the application's identifier (such as the application's package name); slice ordering information includes the number of slices ordered by the user for the same application, slice performance, and slice priority.

[0119] S302. The platform generates slice service information corresponding to the application for the user and sends it to the user terminal.

[0120] In this step, the application's corresponding slice service information includes at least application information, slice identifier, and corresponding priority. The platform selects a slice identifier that meets the user's requirements based on the slice performance ordered by the user.

[0121] If a user subscribes to multiple slices for the same application, the slice service information for that application should include multiple slice identifiers and their corresponding priorities.

[0122] S303. The user terminal sends slice service information to the corresponding application on the terminal. The application prompts the user to set the scene corresponding to the slice, stores the user's settings locally, and sends them to the application platform for storage.

[0123] In this step, if a user subscribes to multiple slices for the same application, the application prompts the user to set corresponding scenarios for each slice. In step S301, when a user subscribes to a slice, they can select slice performance, the number of users for the corresponding scenario, and the corresponding priority. Therefore, in step S303, when the application prompts the user to set the corresponding scenario for a slice, the number of users the user sets for the corresponding slice cannot exceed the number of users selected during the subscription.

[0124] When user settings are not stored locally, for example, when a user changes their phone or clears local storage, the application platform can request, retrieve, and store the user settings.

[0125] S304. When a user uses an application, the application selects the corresponding slice identifier and sends it to the terminal based on the user's usage scenario and user settings. The terminal then uses the corresponding slice to provide services to the application.

[0126] The method for providing tiered slicing services provided in this invention involves a user terminal sending a slice subscription request to a service platform. The request includes the number of slices required by a specified application, slice performance, and corresponding priorities. The service platform configures a corresponding number of slices for the application based on the subscription request, ensuring the configured slices meet the requested performance specifications. It also assigns different priorities to slices with different performance levels. Then, based on the configuration results, it generates slice service information corresponding to the application and returns it to the user terminal. The user terminal then sets corresponding scenarios for slices with different performance levels. Subsequently, when the user uses an application with subscribed slice services, the user terminal can provide the application with slice services of performance corresponding to the current scenario. This allows for tiered use of slice services for the same application in different scenarios, satisfying users' varying network quality requirements for the same application in different scenarios. Furthermore, for operators, providing different slice services to users in different scenarios of the same application can reduce the maintenance burden on high-quality networks.

[0127] Figure 4 This is a schematic diagram of the structure of a user terminal provided in an embodiment of the present invention. Figure 4 As shown, the user terminal includes: a first sending module 401, a first receiving module 402, a selection module 403, and a service providing module 404.

[0128] The first sending module 401 is configured to send a slice subscription request to the service platform. The slice subscription request includes user information, application information, and slice subscription information. The slice subscription information includes the number of slices required by the application, slice performance, and corresponding priority, so that the service platform generates corresponding slice service information for the application based on the slice subscription request and sends it to the user terminal. The slice service information corresponding to the application includes the application information, the slice identifier of the slice configured for the application based on the slice performance, and the corresponding priority. The first receiving module 402 is configured to receive the slice service information corresponding to the application and obtain the scenario set by the user for the slice identifier in the slice service information. The selection module 403 is configured to, in response to the user using the application, select a slice identifier that matches the current scenario from the slice service information based on the current scenario of the application and the scenario set by the user for the slice identifier in the slice service information. The service providing module 404 is configured to provide slice services to the application using the slice corresponding to the slice identifier that matches the current scenario.

[0129] In one specific embodiment, the user terminal further includes: an acquisition module 405 and a request generation module 406.

[0130] The acquisition module 405 is configured to acquire the user's slice demand information and user information. The slice demand information includes application information that needs to use the slice service, the number of slices required by the application, slice performance, and corresponding priority. The request generation module 406 is configured to generate a slice ordering request based on the slice demand information and user information.

[0131] In one specific implementation, the slice ordering information also includes the number of scenario users corresponding to the slice performance required by the application; the slice service information corresponding to the application also includes the number of scenario users corresponding to the slice identifier.

[0132] The acquisition module 405 is further configured to acquire the number of scene users set by the user for the slice identifier in the slice service information, and the number of scene users set for the same slice identifier user does not exceed the number of scene users in the slice service information.

[0133] In one specific implementation, the first sending module 401 is further configured to send the slice service information corresponding to the application to the application, so that the application prompts the user to set a scenario for the slice identifier in the slice service information based on the slice service information.

[0134] Accordingly, the acquisition module 405 is specifically configured to receive scenarios where the user sets the slice identifier in the slice service information according to the prompts of the application.

[0135] In one specific embodiment, the user terminal further includes a storage module 407 and a query module 408.

[0136] Storage module 407 is configured to store the scenarios set by the user for the slice identifier in the slice service information in a local database. Query module 408 is configured to, in response to the user using the application, retrieve the scenarios set by the user for the slice identifier in the slice service information from the local database.

[0137] In another specific embodiment, the first sending module 401 is further configured to upload the scenario set by the user for the slice identifier in the slice service information to the application platform corresponding to the application, and in response to the scenario set by the user for the slice identifier in the slice service information not being found in the local database, send a scenario query request to the application platform, the scenario query request including the slice identifier in the slice service information, so that the application platform can find the scenario set by the user for the slice identifier in the slice service information based on the scenario query request, and return the query result to the user terminal; the first receiving module 402 is further configured to receive the query result sent by the application platform; the storage module 407 is further configured to store the query result sent by the application platform in the local database.

[0138] The user terminal provided in this embodiment of the invention sends a slice ordering request to a service platform, including the number of slices required by a specified application, slice performance, and corresponding priorities. The service platform then configures a corresponding number of slices for the application based on the slice ordering request, ensuring that the configured slices meet the slice performance specifications in the request. It also assigns corresponding priorities to slices with different performance levels. Based on the configuration results, the service platform generates slice service information corresponding to the application and returns it to the user terminal. The user terminal then sets corresponding scenarios for slices with different performance levels. Subsequently, when a user uses an application with pre-ordered slice services, the user terminal can provide the application with slice services of performance corresponding to the current scenario. This allows for tiered use of slice services by users in different scenarios for the same application, satisfying users' varying network quality requirements for the same application in different scenarios.

[0139] Figure 5 This is a schematic diagram of the structure of the service platform provided in an embodiment of the present invention. Figure 5 As shown, the service platform includes: a second receiving module 501, an information generation module 502, and a second sending module 503.

[0140] The second receiving module 501 is configured to receive a slice ordering request sent by a user terminal. The slice ordering request includes user information, application information, and slice ordering information. The slice ordering information includes the number of slices required by the application, slice performance, and corresponding priority. The information generation module 502 is configured to generate corresponding slice service information for the application based on the slice ordering request. The second sending module 503 is configured to send the slice service information to the user terminal. The slice service information corresponding to the application includes the application information, the slice identifier of the slice configured for the application based on the slice performance, and the corresponding priority. This allows the user terminal to obtain the scenario set by the user for the slice identifier in the slice service information after receiving the slice service information. In response to the user using the application, the user terminal selects a slice identifier that matches the current scenario from the slice service information based on the current scenario of the application and the scenario set by the user for the slice identifier in the slice service information. The user terminal then uses the slice corresponding to the slice identifier that matches the current scenario to provide slice services for the application.

[0141] The service platform provided in this embodiment of the invention, upon receiving a slice ordering request from a user terminal, including the number of slices required by a specified application, slice performance, and corresponding priorities, configures a corresponding number of slices for the application based on the slice ordering request. The configured slices meet the slice performance requirements in the request, and corresponding priorities are configured for slices with different performance levels. Then, slice service information corresponding to the application is generated based on the configuration results and returned to the user terminal. The user terminal sets corresponding scenarios for slices with different performance levels. Subsequently, when the user uses an application with subscribed slice services, the user terminal can provide the application with slice services with slice performance corresponding to the current scenario. This enables users to use slice services in different scenarios for the same application at different levels, satisfying users' different network quality requirements for the same application in different scenarios.

[0142] Figure 6 This is a schematic diagram of the structure of a system providing hierarchical slicing services according to an embodiment of the present invention. Figure 6 As shown, the system that provides tiered slicing services includes: user terminals 601 and service platform 602, with multiple user terminals 601 accessing the service platform 602 via the network.

[0143] The user terminal 601 can be the user terminal described in the foregoing embodiments, and the service platform 602 can be the service platform described in the foregoing embodiments, which will not be described again here.

[0144] Based on the same technical concept, embodiments of the present invention also provide a computer device, such as... Figure 7 As shown, the computer device includes a memory 701 and a processor 702. The memory 701 stores a computer program. When the processor 702 runs the computer program stored in the memory 701, the processor 702 executes the aforementioned method for providing tiered slicing services.

[0145] Based on the same technical concept, embodiments of the present invention also provide a computer-readable storage medium storing a computer program thereon, wherein when the computer program is executed by a processor, the processor executes the aforementioned method for providing tiered slicing services.

[0146] In summary, the method, system, user terminal, service platform, computer equipment, and storage medium for providing tiered slicing services provided in the embodiments of the present invention can enable users to use tiered slicing services in different scenarios of the same application, meet users' different network quality requirements for the same application in different scenarios, and at the same time reduce the maintenance pressure on operators for high-quality networks.

[0147] It will be understood by those skilled in the art that all or some of the steps, systems, or apparatuses disclosed above, and their functional modules / units, can be implemented as software, firmware, hardware, or suitable combinations thereof. In hardware implementations, the division between functional modules / units mentioned in the above description does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may be performed collaboratively by several physical components. Some or all physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit (ASIC). Such software may be distributed on a computer-readable medium, which may include computer storage media (or non-transitory media) and communication media (or transient media). As is known to those skilled in the art, the term computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disc (DVD) or other optical disc storage, magnetic cartridges, magnetic tape, disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and can be accessed by a computer. Furthermore, it is well known to those skilled in the art that communication media typically contain computer-readable instructions, data structures, program modules, or other data in modulated data signals such as carrier waves or other transmission mechanisms, and may include any information delivery medium.

[0148] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for providing tiered slicing services, characterized in that, Applied to a user terminal, the method includes: A slice ordering request is sent to the service platform. The slice ordering request includes user information, application information, and slice ordering information. The slice ordering information includes the number of slices required by the application, slice performance, and corresponding priority. This enables the service platform to generate corresponding slice service information for the application based on the slice ordering request and send it to the user terminal. The slice service information corresponding to the application includes the application information, the slice identifier of the slice configured for the application based on the slice performance, and the corresponding priority. Receive the slice service information corresponding to the application, and obtain the scenario set by the user for the slice identifier in the slice service information. If the user has subscribed to multiple slices for the same application, the corresponding scenario must be set for each slice. In response to a user using the application, a slice identifier matching the current scenario is selected from the slice service information based on the current scenario of the application and the scenario set by the user for the slice identifier in the slice service information; and, The application is provided with slicing services using the slice corresponding to the slice identifier that matches the current scenario.

2. The method according to claim 1, characterized in that, Before sending a slice ordering request to the service platform, the following is also included: Obtain user slice request information and user information. The slice request information includes application information that needs to use the slice service, the number of slices required by the application, slice performance, and corresponding priority; and... A slice ordering request is generated based on the slice demand information and user information.

3. The method according to claim 1 or 2, characterized in that, The slice ordering information also includes the number of users in the scenario corresponding to the slice performance required by the application; the slice service information corresponding to the application also includes the number of users in the scenario corresponding to the slice identifier. After receiving the slice service information corresponding to the application, the following is also included: The number of scenario users set by a user for a slice identifier in the slice service information is obtained, and the number of scenario users set for the same slice identifier does not exceed the number of scenario users in the slice service information.

4. The method according to claim 1, characterized in that, After receiving the slice service information corresponding to the application, the following is also included: The application sends the slice service information corresponding to the application to the application, so that the application prompts the user to set a scene for the slice identifier in the slice service information based on the slice service information. The scenario of obtaining the slice identifier set by the user in the slice service information includes: The scenario where the user sets the slice identifier in the slice service information according to the prompts of the application.

5. The method according to claim 1 or 4, characterized in that, After obtaining the scenario where the user sets the slice identifier in the slice service information, the method further includes: The scenarios set by the user for the slice identifier in the slice service information are stored in the local database; In response to a user using the application, the system retrieves the slice identifier set by the user in the slice service information from the local database.

6. The method according to claim 1 or 4, characterized in that, After obtaining the scenario where the user sets the slice identifier in the slice service information, the method further includes: The scenario set by the user for the slice identifier in the slice service information is stored in the local database and uploaded to the application platform corresponding to the application. In response to a user using the application, the system searches the local database for the slice identifier set by the user in the slice service information. In response to a scenario where no user-defined slice identifier in the slice service information is found in the local database, a scenario query request is sent to the application platform. This scenario query request includes the slice identifier from the slice service information. The application platform then searches for the scenario set by the user for the slice identifier in the slice service information based on the scenario query request and returns the query result to the user terminal. Receive query results sent by the application platform and store them in a local database.

7. A method for providing tiered slicing services, characterized in that, Applied to a service platform, the method includes: Receive a slice ordering request sent by a user terminal. The slice ordering request includes user information, application information, and slice ordering information. The slice ordering information includes the number of slices required by the application, slice performance, and corresponding priority. Based on the slice ordering request, corresponding slice service information is generated for the application. The slice service information for the application includes the application information, the slice identifier and corresponding priority of the slice configured for the application based on the slice performance, and... The slice service information is sent to the user terminal so that after receiving the slice service information corresponding to the application, the user terminal can obtain the scenario set by the user for the slice identifier in the slice service information. If the user has subscribed to multiple slices for the same application, a corresponding scenario must be set for each slice. In response to the user using the application, the slice identifier that matches the current scenario is selected from the slice service information based on the current scenario of the application and the scenario set by the user for the slice identifier in the slice service information. The slice service is then provided to the application using the slice corresponding to the slice identifier that matches the current scenario.

8. A user terminal, characterized in that, include: The first sending module is configured to send a slice ordering request to the service platform. The slice ordering request includes user information, application information, and slice ordering information. The slice ordering information includes the number of slices required by the application, the slice performance, and the corresponding priority. This enables the service platform to generate corresponding slice service information for the application based on the slice ordering request and send it to the user terminal. The slice service information corresponding to the application includes the application information, the slice identifier of the slice configured for the application based on the slice performance, and the corresponding priority. The first receiving module is configured to receive the slice service information corresponding to the application and obtain the scenario set by the user for the slice identifier in the slice service information. If the user has subscribed to multiple slices for the same application, the corresponding scenario must be set for each slice. The selection module is configured to, in response to a user using the application, select a slice identifier from the slice service information that matches the current scenario based on the current scenario of the application and the scenario set by the user for the slice identifier in the slice service information. as well as, The service providing module is configured to provide slice services to the application using the slice corresponding to the slice identifier that matches the current scenario.

9. A service platform, characterized in that, include: The second receiving module is configured to receive a slice ordering request sent by a user terminal. The slice ordering request includes user information, application information, and slice ordering information. The slice ordering information includes the number of slices required by the application, slice performance, and corresponding priority. The information generation module is configured to generate corresponding slice service information for the application based on the slice ordering request. as well as, The second sending module is configured to send the slice service information to the user terminal. The slice service information corresponding to the application includes the application information, the slice identifier of the slice configured for the application based on the slice performance, and the corresponding priority. After receiving the slice service information corresponding to the application, the user terminal obtains the scenario set by the user for the slice identifier in the slice service information. If the user has subscribed to multiple slices for the same application, a corresponding scenario must be set for each slice. In response to the user using the application, the module selects a slice identifier that matches the current scenario from the slice service information based on the current scenario of the application and the scenario set by the user for the slice identifier in the slice service information, and uses the slice corresponding to the slice identifier that matches the current scenario to provide slice services to the application.

10. A computer device, characterized in that, It includes a memory and a processor, wherein the memory stores a computer program, and when the processor runs the computer program stored in the memory, the processor executes the method of providing tiered slicing services according to any one of claims 1 to 6, or the method of providing tiered slicing services according to claim 7.

11. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, the processor performs the method of providing tiered slicing services according to any one of claims 1 to 6, or the method of providing tiered slicing services according to claim 7.

Images