Method, terminal, platform, device and medium for multi-user shared slice service

Abstract

The application provides a multi-user shared slice service method, terminal, platform, device and medium, and relates to the technical field of communication. The method comprises the following steps: sending an application login request carrying a first identifier to a service platform, the first identifier comprising a user identifier, so that the service platform queries an application account corresponding to the user identifier, a first user number of simultaneously allowed slice service under the application account, and a second user number of currently using a dedicated network slice under the application account; in response to the two numbers being equal, querying and judging whether the priority of the user identifier is higher than the priority of one of all user identifiers currently using the dedicated network slice; if yes, generating a first dedicated network slice use request carrying the user identifier and providing a dedicated network slice service for a corresponding user terminal. The technical scheme provided by the application can realize simultaneous use of slice services by multiple user terminals under the same application account, without the need for each user to separately subscribe to a slice.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of communication technology, in particular to a method for sharing slice services by multiple users, a user terminal, a service platform, a computer device and a computer readable storage medium. BACKGROUND

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

[0003] However, the existing slice solution uses a user's mobile phone number as the user identifier for subscribing to and using slice services. This results in the need for each of multiple user terminals (corresponding to multiple mobile phone numbers) under the same application account to subscribe to a slice separately in order to use the slice service, which is not a good user experience. SUMMARY

[0004] The present application is completed in order to at least partially solve the technical problem in the prior art that multiple user terminals under the same application account need to subscribe to a slice separately in order to use the slice service.

[0005] According to an aspect of the present application, a method for sharing slice services by multiple users is provided, applied to a user terminal, and the method comprises:

[0006] sending an application login request carrying a first identifier to a service platform, the first identifier including a user identifier, so that the service platform receives the application login request, queries an application account corresponding to the user identifier according to a corresponding relationship between the user identifier and the application account pre-stored therein, queries a first user number of users allowed to use slice services simultaneously under the corresponding application account, and queries a second user number of users currently using a dedicated network slice under the corresponding application account, in response to the first user number being equal to the second user number, queries a priority of the user identifier and priorities of all user identifiers of users currently using the dedicated network slice under the corresponding application account, judges whether the priority of the user identifier is higher than a priority of one of all user identifiers of users currently using the dedicated network slice under the corresponding application account, and if so, generates a first dedicated network slice usage request carrying the user identifier, and provides a dedicated network slice service for the corresponding user terminal based on the first dedicated network slice usage request.

[0007] Optionally, before sending the application login request carrying the first identifier to the service platform, the method further comprises:

[0008] sending slice subscription information to the service platform, the slice subscription information comprising an application account, a number of users under the application account that are allowed to use slice services simultaneously, user identifiers that need to use slice services and respective priorities, and subscription requirements, so that the service platform subscribes to a dedicated network slice that meets the subscription requirements for each user under the application account that needs to use slice services based on the slice subscription information, and generates and stores a user-slice correspondence table based on the slice subscription information, the user-slice correspondence table comprising the application account, the number of users under the application account that are allowed to use slice services simultaneously, and the user identifiers that need to use slice services and respective priorities.

[0009] Optionally, after sending the application login request carrying the first identifier to the service platform, the method further comprises:

[0010] receiving a network state switching request sent by the service platform, wherein the service platform queries whether the current network state of the corresponding user terminal supports a dedicated network slice before providing a dedicated network slice service for the corresponding user terminal based on the first dedicated network slice use request, and sends a network state switching request to the corresponding user terminal and starts timing in response to the query result that the current network state of the corresponding user terminal does not support a dedicated network slice; and

[0011] prompting the user to switch the network based on the network state switching request, so that the service platform provides a dedicated network slice service for the corresponding user terminal based on the first dedicated network slice use request in response to determining that the corresponding user terminal has switched the network state to support a dedicated network slice within a first preset time threshold after timing starts, or in response to the query result that the current network state of the corresponding user terminal supports a dedicated network slice.

[0012] Optionally, after sending the application login request carrying the first identifier to the service platform, the method further comprises:

[0013] receiving service information of the dedicated network slice sent by the service platform; and

[0014] ending the original PDU session of the application, and establishing a new PDU session for the application based on the dedicated network slice service information, so that the service platform generates an add user notification message in response to the user terminal having established a new PDU session for the application using a dedicated network slice, and adds the user identifier to a user identifier list of the application account that is currently using a dedicated network slice based on the add user notification message.

[0015] Optionally, after sending the application login request carrying the first identifier to the service platform, the method further comprises:

[0016] In response to the inability to use the dedicated network slice, automatically sending a second dedicated network slice use request carrying the user identifier to the service platform according to a preset rule; or, receiving an active request input by the user, generating a second dedicated network slice use request carrying the user identifier based on the active request and sending the second dedicated network slice use request to the service platform, so that the service platform receives the second dedicated network slice use request and returns to the step of querying the corresponding application account, the first user quantity, and the second user quantity.

[0017] Optionally, after sending the application login request carrying the first identifier to the service platform, the method further comprises:

[0018] In response to the fact that the user identifier corresponds to a user terminal that has accessed the dedicated network slice and is the user identifier with the lowest priority among all user identifiers currently using the dedicated network slice under the corresponding application account, and the service platform receives an application login request sent by a user terminal corresponding to another user identifier with a higher priority than the user identifier and needing to use the slice service under the corresponding application account, the user terminal corresponding to the user identifier is prohibited by the service platform from continuing to use the dedicated network slice, and the user terminal corresponding to the user identifier periodically sends a third dedicated network slice use request carrying the user identifier to the service platform, so that the service platform receives the third dedicated network slice use request and provides the user terminal corresponding to the user identifier with the dedicated network slice service in response to a decrease in the number of user terminals currently using the dedicated network slice under the corresponding application account.

[0019] Optionally, after sending the application login request carrying the first identifier to the service platform, the method further comprises:

[0020] In response to the fact that the priority of the user identifier is not higher than the priority of one of all user identifiers currently using the dedicated network slice under the corresponding application account, receiving a prompt message about this situation sent by the service platform; and,

[0021] Based on the prompt message, periodically sending an application login request carrying the first identifier to the service platform, so that the service platform receives the application login request carrying the first identifier periodically sent by the user terminal corresponding to the first identifier, and returns to the step of querying the corresponding application account, the first user quantity, and the second user quantity.

[0022] Optionally, after sending the application login request carrying the first identifier to the service platform, the method further comprises:

[0023] in response to the priority of the user identifier being not higher than the priority of one of all user identifiers currently using the dedicated network slice under the corresponding application account, and the user terminal corresponding to the user identifier not being connected to the dedicated network slice after a third preset time threshold since the user terminal corresponding to the user identifier sends the application login request carrying the first identifier, periodically sending the application login request carrying the first identifier to the service platform, so that the service platform receives the application login request carrying the first identifier periodically sent by the user terminal corresponding to the user identifier, and returns to the steps of querying the corresponding application account, the first user number and the second user number.

[0024] According to another aspect of the application, a method for providing a multi-user shared slice service is provided, applied to a service platform, and the method comprises:

[0025] receiving an application login request carrying a first identifier sent by a user terminal, the first identifier comprising a user identifier;

[0026] querying an application account corresponding to the user identifier according to the correspondence between the user identifier and the application account pre-stored therein, querying a first user number of users allowed to use the slice service under the corresponding application account at the same time, and querying a second user number of users currently using the dedicated network slice under the application account;

[0027] in response to the first user number being equal to the second user number, querying the priority of the user identifier and the priority of one of all user identifiers currently using the dedicated network slice under the corresponding application account;

[0028] determining whether the priority of the user identifier is higher than the priority of one of all user identifiers currently using the dedicated network slice under the corresponding application account, and if so, generating a first dedicated network slice use request carrying the user identifier, and providing a dedicated network slice service for the user terminal based on the first dedicated network slice use request.

[0029] Optionally, before receiving the application login request carrying the first identifier sent by the user terminal, the method further comprises:

[0030] receiving slice subscription information sent by the user terminal, the slice subscription information comprising an application account, a user number of users allowed to use the slice service under the application account at the same time, user identifiers needing to use the slice service and respective priorities, and subscription requirements;

[0031] respectively subscribing to a dedicated network slice meeting the subscription requirements for each user needing to use the slice service under the application account; and

[0032] generate and store a user slice correspondence table based on the slice subscription information, the user slice correspondence table including the application account, a number of users under the application account that are simultaneously allowed to use slice services, and user identities that need to use slice services and respective priorities.

[0033] Optionally, the application account corresponding to the user identity is queried according to a correspondence relationship between a user identity and an application account pre-stored therein, and specifically:

[0034] The application account corresponding to the user identity is queried from the user slice correspondence table.

[0035] The number of users under the application account that are simultaneously allowed to use slice services is taken as a first number of users, and specifically:

[0036] The number of users under the application account that are simultaneously allowed to use slice services is queried from the user slice correspondence table as the first number of users.

[0037] The priority of the user identity and the priorities of all user identities that are currently using a dedicated network slice under the corresponding application account are queried, and specifically:

[0038] The respective priorities of the user identities that need to use slice services are queried from the user slice correspondence table, and the priority of the user identity and the priorities of all user identities that are currently using a dedicated network slice under the corresponding application account are obtained.

[0039] Optionally, after subscribing to a dedicated network slice that meets the subscription requirements for each user under the application account that needs to use slice services, the method further includes:

[0040] The corresponding network slice identifier is configured for each user under the application account that needs to use slice services.

[0041] Optionally, before providing a dedicated network slice service for the corresponding user terminal based on the first dedicated network slice usage request, the method further includes:

[0042] It is queried whether the current network state of the corresponding user terminal supports a dedicated network slice.

[0043] The dedicated network slice service is provided for the corresponding user terminal based on the first dedicated network slice usage request, and specifically:

[0044] In response to the query result that the current network state of the corresponding user terminal supports a dedicated network slice, the dedicated network slice service is provided for the corresponding user terminal based on the first dedicated network slice usage request.

[0045] Optionally, after inquiring whether the current network state of the corresponding user terminal supports the dedicated network slice, the method further comprises:

[0046] In response to the query result being that the current network state of the corresponding user terminal does not support the dedicated network slice, sending a network state switching request to the corresponding user terminal and starting a timer, so that the corresponding user terminal receives the network state switching request and prompts the user to switch the network based on the network state switching request; and

[0047] Within a first preset time threshold after the start of the timer, determining whether the corresponding user terminal has switched the network state to support the dedicated network slice;

[0048] The dedicated network slice service provided for the corresponding user terminal based on the first dedicated network slice use request comprises:

[0049] In response to determining within the first preset time threshold after the start of the timer that the corresponding user terminal has switched the network state to support the dedicated network slice, providing the dedicated network slice service for the corresponding user terminal based on the first dedicated network slice use request.

[0050] Optionally, the dedicated network slice service provided for the corresponding user terminal based on the first dedicated network slice use request comprises:

[0051] Based on the first dedicated network slice use request, switching and mapping the PDU session currently established by the corresponding user terminal from the original default network slice of the bearer to the dedicated network slice provided for it;

[0052] After providing the dedicated network slice service for the corresponding user terminal based on the first dedicated network slice use request, the method further comprises:

[0053] In response to the PDU session currently established by the corresponding user terminal having been switched and mapped from the original default network slice of the bearer to the dedicated network slice provided for it, generating an add user notification message; and

[0054] Based on the add user notification message, adding the user identifier to the user identifier list of the currently used dedicated network slice under the application account.

[0055] Optionally, the dedicated network slice service provided for the corresponding user terminal based on the first dedicated network slice use request comprises:

[0056] Based on the first dedicated network slice use request, returning the service information of the dedicated network slice to the corresponding user terminal, so that the corresponding user terminal receives the service information of the dedicated network slice, ends the original PDU session of the application, and establishes a new PDU session for the application based on the dedicated network slice service information.

[0057] after providing the dedicated network slice service for the corresponding user terminal based on the first dedicated network slice usage request, further comprising:

[0058] generating an add user notification message in response to the corresponding user terminal having established a new PDU session for the application using the dedicated network slice; and

[0059] adding the corresponding user identity to a list of user identities currently using the dedicated network slice under the application account based on the add user notification message.

[0060] Optionally, the method further comprises:

[0061] starting a timer in response to the corresponding user terminal having established a PDU session currently being switched from a default network slice of an original bearer to a dedicated network slice provided therefor, or in response to the corresponding user terminal having established a new PDU session for the application using the dedicated network slice.

[0062] periodically determining whether the corresponding user terminal has traffic usage on the dedicated network slice within a second preset time threshold after the timer is started.

[0063] If not, the corresponding user terminal is prohibited from continuing to use the dedicated network slice.

[0064] Optionally, after the corresponding user terminal is prohibited from continuing to use the dedicated network slice, further comprising:

[0065] generating a delete user notification message carrying the corresponding user identity; and

[0066] deleting the corresponding user identity from the list of user identities currently using the dedicated network slice under the application account based on the delete user notification message.

[0067] Optionally, after providing the dedicated network slice service for the corresponding user terminal based on the first dedicated network slice usage request, further comprising:

[0068] receiving a second dedicated network slice usage request carrying the corresponding user identity automatically sent by the corresponding user terminal according to a preset rule due to the inability to use the dedicated network slice, or receiving a second dedicated network slice usage request carrying the user identity generated and sent by the corresponding user terminal based on a user input active request; and

[0069] returning to the step of querying the corresponding application account, the first number of users, and the second number of users.

[0070] Optionally, after determining that the priority of the user identifier is higher than the priority of one of all user identifiers currently using the dedicated network slice under the corresponding application account, the method further comprises:

[0071] selecting a user identifier with the lowest priority from all user identifiers currently using the dedicated network slice under the application account;

[0072] generating a dedicated network slice prohibition use notification message carrying the user identifier with the lowest priority; and

[0073] prohibiting the user terminal corresponding to the user identifier with the lowest priority from continuing to use the dedicated network slice based on the dedicated network slice prohibition use notification message.

[0074] Optionally, after prohibiting the user terminal corresponding to the user identifier with the lowest priority from continuing to use the dedicated network slice based on the dedicated network slice prohibition use notification message, the method further comprises:

[0075] receiving a third dedicated network slice use request carrying the user identifier with the lowest priority periodically sent by the user terminal corresponding to the user identifier with the lowest priority due to being prohibited from continuing to use the dedicated network slice; and

[0076] providing the user terminal corresponding to the user identifier with the lowest priority with the dedicated network slice service in response to a decrease in the number of users currently using the dedicated network slice under the application account.

[0077] Optionally, after determining whether the priority of the user identifier is higher than the priority of one of all user identifiers currently using the dedicated network slice under the corresponding application account, the method further comprises:

[0078] if the priority of the user identifier is not higher than the priority of one of all user identifiers currently using the dedicated network slice under the corresponding application account, sending a corresponding prompt message to the user terminal corresponding to the user identifier, so that the user terminal corresponding to the user identifier receives the prompt message and periodically sends an application login request carrying the first identifier to the service platform based on the prompt message; and

[0079] receiving the application login request carrying the first identifier periodically sent by the user terminal corresponding to the user identifier, and returning to the steps of querying the corresponding application account, the first user quantity, and the second user quantity.

[0080] Optionally, after determining whether the priority of the user identifier is higher than the priority of one of all user identifiers currently using the dedicated network slice under the corresponding application account, the method further comprises:

[0081] if the priority of the user identifier is not higher than the priority of one of all user identifiers currently using the dedicated network slice under the corresponding application account, the user terminal corresponding to the user identifier has not been accessed to the dedicated network slice after a third preset time threshold since the user terminal sends the application login request carrying the first identifier to the service platform, and the application login request carrying the first identifier is periodically sent to the service platform;

[0082] returning to the step of querying the corresponding application account, the first user quantity and the second user quantity.

[0083] According to still another aspect of the present application, a user terminal is provided, comprising:

[0084] The sending module is configured to send an application login request carrying a first identifier to a service platform, the first identifier comprising a user identifier, so that the service platform receives the application login request, queries an application account corresponding to the user identifier according to a corresponding relationship between the user identifier and the application account pre-stored therein, queries a user quantity simultaneously allowed to use slice services under the corresponding application account as a first user quantity, and queries a user quantity currently using a dedicated network slice under the corresponding application account as a second user quantity, in response to the first user quantity being equal to the second user quantity, queries a priority of the user identifier and priorities of all user identifiers currently using the dedicated network slice under the corresponding application account, judges whether the priority of the user identifier is higher than the priority of one of all user identifiers currently using the dedicated network slice under the corresponding application account, if yes, generates a first dedicated network slice use request carrying the user identifier, and provides a dedicated network slice service for the corresponding user terminal based on the first dedicated network slice use request.

[0085] According to still another aspect of the present application, a service platform is provided, comprising:

[0086] The receiving module is configured to receive an application login request carrying a first identifier sent by a user terminal, the first identifier comprising a user identifier.

[0087] The querying module is configured to query an application account corresponding to the user identifier according to a corresponding relationship between the user identifier and the application account pre-stored therein, query a user quantity simultaneously allowed to use slice services under the corresponding application account as a first user quantity, and query a user quantity currently using a dedicated network slice under the corresponding application account as a second user quantity; in response to the first user quantity being equal to the second user quantity, query a priority of the user identifier and priorities of all user identifiers currently using the dedicated network slice under the corresponding application account.

[0088] a judging module configured to judge whether the priority of the user identifier is higher than the priority of one of all user identifiers currently using the dedicated network slice under the corresponding application account;

[0089] a request generating module configured to generate a first dedicated network slice usage request carrying the user identifier when the result of the judgment of the judging module is higher; and

[0090] a service providing module configured to provide the dedicated network slice service for the corresponding user terminal based on the first dedicated network slice usage request.

[0091] According to still another aspect of the present application, there is provided a computer device comprising a memory and a processor, the memory storing a computer program, when the processor executes the computer program stored in the memory, the processor executes the method for the multi-user shared slice service.

[0092] According to still another aspect of the present application, there is provided a computer readable storage medium storing a computer program, when the processor executes the computer program, the processor executes the method for the multi-user shared slice service.

[0093] The technical solution provided by the present application can include the following beneficial effects:

[0094] The method for the multi-user shared slice service provided by the present application, the user terminal sends an application login request carrying a first identifier to the service platform, the first identifier comprises a user identifier, so that the service platform receives the application login request, queries the application account corresponding to the user identifier according to the corresponding relationship between the user identifier and the application account pre-stored therein, queries the first user number of the number of users simultaneously allowed to use the slice service under the corresponding application account, and queries the second user number of the number of users currently using the dedicated network slice under the corresponding application account, in response to the first user number being equal to the second user number, queries the priority of the user identifier and the priority of all user identifiers currently using the dedicated network slice under the corresponding application account, judges whether the priority of the user identifier is higher than the priority of one of all user identifiers currently using the dedicated network slice under the corresponding application account, if higher, generates a first dedicated network slice usage request carrying the user identifier, and provides the dedicated network slice service for the corresponding user terminal based on the first dedicated network slice usage request, which can realize the simultaneous use of the slice service by the multi-user terminals (corresponding to multiple user identifiers) under the same application account without the need for each user to subscribe to the slice, thereby saving the use cost of the user and providing a better user experience.

[0095] Other features and advantages of the present application will be set forth in the description that follows, and in part will be apparent from the description, or can be learned by practice of the application. The purposes and other advantages of the present application will be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings. BRIEF DESCRIPTION OF DRAWINGS

[0096] The accompanying drawings are included to provide a further understanding of the application and are incorporated in and constitute a part of this specification, illustrate embodiments of the application and are used to explain the technical solution of the application, and do not constitute a limitation on the technical solution of the application.

[0097] Figure 1 A flowchart of a method for providing a multi-user shared slice service according to an embodiment of the present application is shown in FIG. 1.

[0098] Figure 2 A flowchart of another method for providing a multi-user shared slice service according to an embodiment of the present application is shown in FIG. 2.

[0099] Figure 3 A structural diagram of a user terminal according to an embodiment of the present application is shown in FIG. 3.

[0100] Figure 4 A structural diagram of a service platform according to an embodiment of the present application is shown in FIG. 4.

[0101] Figure 5 A structural diagram of a system for providing a multi-user shared slice service according to an embodiment of the present application is shown in FIG. 5.

[0102] Figure 6 A structural diagram of another system for providing a multi-user shared slice service according to an embodiment of the present application is shown in FIG. 6.

[0103] Figure 7 A structural diagram of a computer device according to an embodiment of the present application is shown in FIG. 7. DETAILED DESCRIPTION

[0104] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the specific embodiments of the present application are described in detail below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are only used to explain and illustrate the present application, and are not used to limit the present application.

[0105] The inventor finds that many applications (APP, the abbreviation of Application) support a same account to be logged in on multiple user terminals (such as some video applications), if the slice of an operator is not subscribed to a single user by a mobile phone number, but is subscribed to an application provider, and then is sold to users by the application provider, then the technical problem that the multiple user terminals under the same application account need to be subscribed to the slice respectively to use the slice service is solved, at this time, a slice subscription and slice service using scheme through the application provider is needed to realize that the multiple user terminals under the same application account can use the slice service at the same time, and the slice subscription price can be floated according to the number of users under the same application account that can use the slice service at the same time, which is described in detail below through specific embodiments.

[0106] It should be noted that the terms "first", "second" and the like in the description and claims of the present application and the above drawings are used to distinguish similar objects, and do not necessarily indicate a specific order or sequence; and, in the case of no conflict, the embodiments in the present application and the features in the embodiments can be combined with each other arbitrarily. In the following description, the suffixes such as "module", "part" or "unit" used to represent elements are only for the convenience of description of the present application, and have no specific meaning. Therefore, "module", "part" or "unit" can be used mixedly.

[0107] Figure 1 A flowchart of a method for sharing a slice service by multiple users provided by an embodiment of the present application is shown. The method is applied to a user terminal, such as Figure 1 As shown in the figure, the method comprises the following step S101.

[0108] S101. An application login request carrying a first identifier is sent to a service platform, the first identifier comprises a user identifier, so that the service platform receives the application login request, queries an application account corresponding to the user identifier according to the corresponding relationship between the user identifier and the application account pre-stored therein, queries a first user number of the users allowed to use the slice service under the corresponding application account at the same time, and queries a second user number of the users using the dedicated network slice under the corresponding application account at present, in response to the first user number being equal to the second user number, queries a priority of the user identifier and priorities of all user identifiers using the dedicated network slice under the corresponding application account at present, judges whether the priority of the user identifier is higher than the priority of one of all user identifiers using the dedicated network slice under the corresponding application account at present, if higher, generates a first dedicated network slice use request carrying the user identifier, and provides a dedicated network slice service for the corresponding user terminal based on the first dedicated network slice use request.

[0109] The user terminal can be a smart phone, a tablet computer (PAD), a PC terminal (computer terminal), etc.

[0110] The first identifier can include a user identifier. The user identifier is used to distinguish different users, for example, can be a mobile phone number, in which case the user terminal sends an application login request carrying the mobile phone number to the service platform. The user identifier can also be an IMSI (International Mobile Subscriber Identification) or an ICCID (Integrate circuit card identity, also known as a SIM card number). Of course, the user identifier can also be other identifiers that can distinguish different users, as long as it can uniquely identify the user. The application does not limit it. The user identifier corresponding to the user using the user terminal should be the user identifier that has subscribed to the slice service under the same application account.

[0111] When the user starts the application on the terminal, the user needs to send an application login request to the service platform through the terminal. The user can also switch different login accounts (i.e. the first identifier) multiple times, and each time the user needs to log in again and send an application login request carrying the corresponding first identifier to the service platform.

[0112] The number of users is the number of user identifiers. In the case of a mobile phone number, the user identifier that is allowed to use the slice service under the application account at the same time is the mobile phone number that is allowed to use the slice service under the application account at the same time; the user identifier currently using the dedicated network slice under the application account is the mobile phone number currently using the dedicated network slice, which means the mobile phone number currently using the dedicated network slice, and the same application account can correspond to multiple mobile phone numbers currently using the dedicated network slice. The first user number and the second user number are at least one.

[0113] In this embodiment, since the number of users allowed to use the slice service under the application account is equal to the number of users currently using the dedicated network slice under the application account, i.e., the number of users currently using the dedicated network slice has reached the upper limit, whether to allow the user terminal to use the dedicated network slice needs to judge whether the priority of the user identifier is higher than the priority of one of all user identifiers currently using the dedicated network slice under the corresponding application account. As long as the priority of the user identifier is higher than the priority of any one of all user identifiers currently using the dedicated network slice under the corresponding application account, the user terminal is allowed to use the dedicated network slice. In this case, the service platform generates a first dedicated network slice use request carrying the user identifier and provides the dedicated network slice service for the user terminal based on the first dedicated network slice use request, and the user terminal can run the application on the corresponding dedicated network slice.

[0114] Of course, the number of users allowed to use the slice service under the application account cannot be less than the number of users currently using the dedicated network slice under the application account, i.e., the first number of users cannot be less than the second number of users.

[0115] In actual application, the service platform can be an operator platform integrated with an application platform, or can include a separate application platform and a separate operator platform. In other words, the application platform and the operator platform can be integrated or separated, which can be selected by those skilled in the art according to actual needs. Correspondingly, the user terminal sends an application login request carrying a first identifier to the application platform, which queries the application account corresponding to the user identifier according to the corresponding relationship between the user identifier and the application account pre-stored therein, queries the number of users allowed to use the slice service under the corresponding application account as the first number of users, and queries the number of users currently using the dedicated network slice under the corresponding application account as the second number of users. When the first number of users is equal to the second number of users, the priority of the user identifier and the priority of all user identifiers currently using the dedicated network slice under the corresponding application account are queried, and it is judged whether the priority of the user identifier is higher than the priority of one of all user identifiers currently using the dedicated network slice under the corresponding application account. If it is higher, a first dedicated network slice use request carrying the user identifier is generated and sent to the operator platform, and then the operator platform provides the dedicated network slice service for the user terminal corresponding to the user identifier based on the first dedicated network slice use request carrying the user identifier.

[0116] In a specific embodiment, before step S101, the following step S102 is further included.

[0117] S102. The user terminal sends slice subscription information to the service platform, the slice subscription information including an application account, a number of users under the application account that are allowed to use slice services at the same time, user identities that need to use slice services and respective priorities, and subscription requirements, so that the service platform receives the slice subscription information, subscribes to dedicated network slices that meet the subscription requirements for each user under the application account that needs to use slice services respectively, and generates and stores a user-slice correspondence table based on the slice subscription information, the user-slice correspondence table including the application account, the number of users under the application account that are allowed to use slice services at the same time, and the user identities that need to use slice services and respective priorities.

[0118] It should be noted that the user terminal that sends the slice subscription information to the service platform in this step and the user terminal that sends the application login request to the service platform in step S101 can be the same user terminal or different user terminals, in other words, as long as one user subscribes to slice services, multiple users can share slice services.

[0119] 0If the service platform includes an application platform and an operator platform, then in this step, the user terminal sends the slice subscription information to the application platform, and the application platform subscribes to dedicated network slices that meet the subscription requirements for each user under the application account that needs to use slice services to the respective operator platform based on the slice subscription information, and simultaneously generates and stores a user-slice correspondence table based on the slice subscription information.

[0120] 5In this embodiment, when a user subscribes to slice services, the user terminal can upload slice subscription information. In addition to the application account, the number of users under the application account that are allowed to use slice services at the same time, the user identities that need to use slice services and respective priorities, and the subscription requirements, the slice subscription information can also include an application identifier for distinguishing different applications.

[0121] The application identifier is the identity of the application, which can be the package name of the application, etc. For example, the package name of iQiyi is com.qiyi.video, and the package name of Douyin is com.ss.android.ugc.aweme.

[0122] An application account can be shared by multiple users, and the same application account can be logged in and used on multiple user terminals (corresponding to multiple user identities) at the same time.

[0123] The number of users allowed to use the slice service under the application account at the same time can be set by the user. Specifically, when the user subscribes to the slice, the terminal can show the user the number of users allowed to use the slice service under the same application account and the corresponding price provided by the service platform for the user to choose. Generally, the more users allowed to use the slice service under the same application account, the higher the corresponding price. The user can choose according to actual needs.

[0124] The user terminal can provide a slice subscription information input interface under the application account. The user can input a plurality of user identifiers (such as mobile phone numbers) requiring to use the slice service under the application account on the interface, and set a corresponding priority for each user identifier, so that multiple users can share the slice service of an application after one user purchases the slice service of the application. Of course, the priorities of the corresponding user identifiers requiring to use the slice service under the same application account cannot be the same.

[0125] The user can also input the required subscription requirements, such as bandwidth and latency requirements of the slice, on the interface.

[0126] After the user completes the foregoing information selection, input, and setting work, the slice subscription information is formed and uploaded to the service platform.

[0127] In addition, after the user subscribes to the slice, the user identifier requiring to use the slice service and the priority thereof under the application account can also be modified. Specifically, the user terminal can also provide a slice subscription information modification interface under the application account, which shows the application identifier, the application account, the number of users allowed to use the slice service under the same application account, the user identifier requiring to use the slice service, and the corresponding priority of each user identifier. The user can modify the user identifier and the priority thereof having subscribed to the slice service under the same application account on the interface, and can also modify the number of users having subscribed to the slice service under the same application account. After the user modifies, the user terminal needs to upload the updated slice subscription information to the service platform again.

[0128] The service platform also generates and stores a user-slice correspondence table based on the slice subscription information. The user-slice correspondence table is used to store the correspondence of "application account-number of users allowed to use the slice service under the same application account-user identifier requiring to use the slice service and the corresponding priority of each user identifier".

[0129] Correspondingly, the service platform queries the application account corresponding to the user identifier according to the pre-stored correspondence of the user identifier and the application account in the service platform, specifically:

[0130] Querying the application account corresponding to the user identifier from the user-slice correspondence table.

[0131] The service platform queries the number of users under the corresponding application account that are simultaneously allowed to use the slice service as the first number of users, specifically as follows:

[0132] The number of users under the application account that are simultaneously allowed to use the slice service is queried from the user-slice correspondence table as the first number of users.

[0133] The service platform queries the priority of the user identifier and the priority of all user identifiers under the corresponding application account that are currently using the dedicated network slice, specifically as follows:

[0134] The priority of the user identifier and the priority of all user identifiers under the corresponding application account that are currently using the dedicated network slice are queried from the user-slice correspondence table.

[0135] An example is provided below to explain in detail how to provide a multi-user shared slice service according to priority.

[0136] For example, when a user subscribes to a slice, the slice subscription information uploaded by the user terminal to the service platform includes: application identifier A, application account B, the number of mobile phone numbers under application account B that are allowed to simultaneously use the slice service is 2, and the mobile phone numbers and priorities under application account B that need to use the slice service are "mobile phone number 1 - first priority", "mobile phone number 2 - second priority", and "mobile phone number 3 - third priority". When the user of application account B uses the terminal corresponding to mobile phone number 2 to send an application login request to the service platform, the service platform queries that the number of "mobile phone numbers that are currently using the dedicated network slice" corresponding to application account B is 2, and it can be seen that the number of users that are currently using the dedicated network slice is equal to the number of users that are allowed to simultaneously use the slice service. The "mobile phone numbers that are currently using the dedicated network slice" are mobile phone number 1 and mobile phone number 3, and since the priority of mobile phone number 2 is higher than that of mobile phone number 3, the service platform generates a first dedicated network slice use request carrying mobile phone number 2, and provides a dedicated network slice service for the terminal of mobile phone number 2 based on the first dedicated network slice use request.

[0137] In a specific embodiment, user authentication needs to be performed between the user terminal and the service platform, which can be implemented in one of the following four ways.

[0138] Method one, the first identifier includes a user identifier, and the user identifier is a mobile phone number. The authentication process is as follows: the user selects "one-key login with local number" on the user terminal, the user terminal obtains the mobile phone number from the user's mobile phone card inserted therein, and sends an application login request carrying the "mobile phone number" and the "one-key login with local number" identifier to the service platform. The service platform performs authentication through the "one-key login with local number" method.

[0139] The second mode, the first identifier includes a user identifier, and the user identifier is a mobile phone number. The authentication process is that the user terminal sends an application login request carrying the mobile phone number to the service platform, and the service platform authenticates by using a "verification code".

[0140] The third mode, the first identifier includes a user identifier and a password. The authentication process is that the user terminal sends an application login request carrying the user identifier and the password to the service platform, the service platform pre-stores a corresponding relationship between the user identifier and the password, and matches the user identifier and the password carried by the application login request with the pre-stored user identifier and password to realize authentication.

[0141] The fourth mode, the first identifier includes a user identifier, an application account and a password. The authentication process is that the user terminal sends an application login request carrying the user identifier, the application account and the password to the service platform, and the service platform authenticates the user based on the application account, the password and the user identifier in the application login request. Specifically, it is verified whether the application account and the password in the application login request match the pre-stored application account and password in the service platform, and whether the user identifier in the application login request matches the pre-stored user identifier corresponding to the application account in the service platform. If both are matched, the authentication is passed, and if any of them is not matched, the authentication fails. In addition, the application login request sent by the user terminal is encrypted by using a preset encryption algorithm, and the service platform receives the encrypted application login request and then decrypts it according to the corresponding decryption algorithm. Preferably, the application login request is encrypted and decrypted by using an asymmetric encryption algorithm (such as RSA algorithm).

[0142] Correspondingly, the service platform queries the corresponding application account, the first user quantity and the second user quantity, specifically as follows:

[0143] In response to the user authentication passing, the service platform queries the corresponding application account, the first user quantity and the second user quantity.

[0144] In this embodiment, after the user terminal sends an application login request to the service platform, the service platform needs to authenticate first. If the authentication is passed, the corresponding application account, the first user quantity and the second user quantity are queried. If the authentication is not passed, the application login request of the user terminal is rejected, and the process is ended.

[0145] In a specific embodiment, after step S101, the following steps S103 and S104 are further included.

[0146] S103. receiving a network state switching request sent by the service platform, wherein the service platform queries whether the current network state of the corresponding user terminal supports the dedicated network slice before providing the dedicated network slice service for the corresponding user terminal based on the first dedicated network slice use request, and sends the network state switching request to the corresponding user terminal and starts timing in response to the query result that the current network state of the corresponding user terminal does not support the dedicated network slice;

[0147] S104. prompting the user to switch the network based on the network state switching request, so that the service platform provides the dedicated network slice service for the corresponding user terminal based on the first dedicated network slice use request in response to determining that the corresponding user terminal has switched the network state to support the dedicated network slice within a first preset time threshold after the timing starts, or in response to the query result that the current network state of the corresponding user terminal supports the dedicated network slice.

[0148] The first preset time threshold can be set and adjusted by those skilled in the art, for example, it can be set to 20 seconds, 30 seconds, etc.

[0149] In this embodiment, if the current network state of the corresponding user terminal supports the dedicated network slice, the service platform directly provides the dedicated network slice service for the corresponding user terminal based on the first dedicated network slice use request; if the current network state of the corresponding user terminal does not support the dedicated network slice, the service platform sends the network state switching request to the user terminal, prompts the user to "switch to the network state that can use the dedicated network slice", and if the user terminal completes the network state switching within the first preset time threshold, the service platform provides the dedicated network slice service for the corresponding user terminal based on the first dedicated network slice use request; if the user terminal fails to complete the network state switching within the first preset time threshold, the current process is ended.

[0150] For example, the service platform queries that the user terminal corresponding to the user identifier currently resides in the 4G network, or the service platform queries that the user currently uses the wifi network and does not use the mobile data network, in which case the user terminal does not support using the 5G network slice, at this time the user terminal prompts the user to "switch to the network state that can use the dedicated network slice", if the user turns on the 5G switch of the terminal within the first preset time threshold and successfully switches to the 5G network, the service platform provides the dedicated network slice service for the corresponding user terminal based on the first dedicated network slice use request.

[0151] In one specific embodiment, after step S101, steps S105 and S106 are further included.

[0152] S105. receiving the service information of the dedicated network slice sent by the service platform.

[0153] The service information of the network slice includes at least S-NSSAI (Single Network Slice Selection Assistance Information) and TD (Traffic Descriptor). The S-NSSAI is an identifier of the network slice, and the TD can be an application identifier, application server network domain name information, application server address information, or the like. The service information of the network slice records a correspondence between the network slice and an application that can use the network slice. After the user terminal receives the service information of the dedicated network slice sent by the service platform, the user terminal performs a subsequent corresponding operation (for example, step S106), so that the application runs on the corresponding dedicated network slice.

[0154] S106. End the original PDU session of the application, and establish a new PDU session for the application based on the dedicated network slice service information, so that the service platform generates an add user notification message in response to the user terminal having established a new PDU session for the application based on the dedicated network slice, and adds the user identifier to a user identifier list of the current dedicated network slice under the application account based on the add user notification message.

[0155] The PDU session, i.e., PDU Session, provides data connectivity between a UE (User Equipment / User Terminal) and a DN (Data Network). All data traffic of the UE must be carried through the PDU session, in other words, the UE should establish a PDU session before sending data traffic; the PDU session must be initiated by the UE, and the core network accepts the request of the UE and allocates corresponding control plane and data plane resources, so that the UE can transmit data between the DN.

[0156] In this embodiment, after the user terminal receives the service information of the dedicated network slice sent by the service platform, the user terminal updates the terminal routing selection policy, specifically, ends the original PDU session of the application, and establishes a new PDU session for the application based on the dedicated network slice. Moreover, after the user terminal establishes a new PDU session based on the dedicated network slice, the service platform adds the user identifier to the user identifier list of the current dedicated network slice under the application account, thereby increasing the number of users of the current dedicated network slice under the application account, i.e., the second user number plus one.

[0157] In a specific implementation, after step S101, the following step S107 is further included.

[0158] S107. In response to the inability to use the dedicated network slice, automatically sending a second dedicated network slice use request carrying the user identifier to the service platform according to a preset rule; or, receiving a user input active request, generating a second dedicated network slice use request carrying the user identifier based on the active request and sending it to the service platform, so that the service platform receives the second dedicated network slice use request and returns to execute the steps of querying the corresponding application account, the first user quantity and the second user quantity.

[0159] In this embodiment, after the service platform provides the dedicated network slice service for the corresponding user terminal based on the first dedicated network slice use request, no matter for what reason, as long as the user terminal cannot use the dedicated network slice, on the one hand, the user terminal sends a second dedicated network slice use request carrying the user identifier to the service platform when the application login request is sent, or the user terminal sends a second dedicated network slice use request carrying the user identifier to the service platform when the application is switched from the background to the foreground in the application login state, on the other hand, the user terminal can periodically send a second dedicated network slice use request carrying the user identifier to the service platform, that is, the user terminal automatically requests the service platform to use the dedicated network slice according to a preset rule, wherein the period of the user terminal sending the second dedicated network slice use request to the service platform can be set and adjusted by those skilled in the art, for example, it can be set to 5 minutes, 10 minutes. Or, the user terminal can also provide an input page for the user to input an active request for using the dedicated network slice in the application login state, that is, the user actively selects to request the service platform to use the dedicated network slice. And the service platform, after receiving the second dedicated network slice use request sent by the user terminal, can first check whether the user identifier matches the user identifier corresponding to the application account stored in advance, and if it matches, it returns to execute the steps of querying the corresponding application account, the first user quantity and the second user quantity.

[0160] In one specific embodiment, after step S101, the following step S108 is further included.

[0161] S108. In response to the user terminal corresponding to the user identifier having accessed the dedicated network slice and being the user identifier with the lowest priority among all user identifiers currently using the dedicated network slice under the corresponding application account, the service platform receives an application login request sent by a user terminal corresponding to another user identifier with a higher priority than the user identifier under the corresponding application account and needing to use the slice service, and the user terminal corresponding to the user identifier is prohibited by the service platform from continuing to use the dedicated network slice. The user terminal corresponding to the user identifier periodically sends a third dedicated network slice use request carrying the user identifier to the service platform, so that the service platform receives the third dedicated network slice use request and provides the user terminal corresponding to the user identifier with the dedicated network slice service in response to a decrease in the number of users currently using the dedicated network slice under the corresponding application account.

[0162] In this embodiment, after the service platform provides the user terminal corresponding to the user identifier with the dedicated network slice service and the user terminal corresponding to the user identifier has accessed the dedicated network slice, if the user identifier happens to be the user identifier with the lowest priority among all user identifiers currently using the dedicated network slice under the corresponding application account, or although the user identifier is not the user identifier with the lowest priority among all user identifiers currently using the dedicated network slice under the corresponding application account at the moment, the user identifier becomes the user identifier with the lowest priority among all user identifiers currently using the dedicated network slice under the corresponding application account because other user terminals corresponding to user identifiers with higher priorities also send application login requests to the service platform and access the dedicated network slice, and then another user terminal corresponding to a user identifier with a higher priority than the user identifier under the corresponding application account and needing to use the slice service sends an application login request to the service platform, the user terminal corresponding to the user identifier is prohibited by the service platform from continuing to use the dedicated network slice. In this case, the user terminal corresponding to the user identifier can periodically send a third dedicated network slice use request carrying the user identifier to the service platform, and then the service platform receives the third dedicated network slice use request and provides the user terminal corresponding to the user identifier with the dedicated network slice service once the number of users currently using the dedicated network slice under the corresponding application account decreases (e.g., a user exits or is prohibited from using the dedicated network slice due to a long time of not using the dedicated network slice), without the need to repeatedly perform the previous query and authentication steps.

[0163] In a specific implementation, after step S101, the following steps S109 and S110 are further included.

[0164] S109. In response to the priority of the user identifier being not higher than the priority of one of all user identifiers currently using the dedicated network slice under the corresponding application account, receiving a prompt message about the situation sent by the service platform;

[0165] S110. Based on the prompt message, periodically sending an application login request carrying the first identifier to the service platform, so that the service platform receives the application login request carrying the first identifier periodically sent by the user terminal corresponding to the first identifier, and returns to the step of querying the corresponding application account, the first user quantity and the second user quantity.

[0166] In this embodiment, if the service platform determines that the priority of the user identifier is not higher than the priority of one of all user identifiers currently using the dedicated network slice under the corresponding application account, that is, the condition for providing the dedicated network slice service for the user terminal corresponding to the user identifier is not met, the service platform can send a corresponding prompt message to the user terminal corresponding to the user identifier about this situation. The specific message content is not limited in the present application. After receiving the prompt message sent by the service platform, if the user terminal still wants to use the dedicated network slice service, it can periodically send an application login request to the service platform until it is accessed to the dedicated network slice.

[0167] In a specific implementation, after step S101, the following step S111 is further included.

[0168] S111. In response to the priority of the user identifier being not higher than the priority of one of all user identifiers currently using the dedicated network slice under the corresponding application account, and the user terminal corresponding to the user identifier not being accessed to the dedicated network slice after a third preset time threshold from when the user terminal sends an application login request carrying the first identifier to the service platform, periodically sending an application login request carrying the first identifier to the service platform, so that the service platform receives the application login request carrying the first identifier periodically sent by the user terminal corresponding to the first identifier, and returns to the step of querying the corresponding application account, the first user quantity and the second user quantity.

[0169] In this embodiment, if the service platform determines that the priority of the user identifier is not higher than the priority of one of all user identifiers currently using the dedicated network slice under the corresponding application account, that is, the condition for providing the dedicated network slice service for the user terminal corresponding to the user identifier is not met, the service platform will not provide the dedicated network slice service for the user terminal corresponding to the user identifier. In this case, if the user terminal has not been accessed to the dedicated network slice after a third preset time threshold from when the user terminal sends an application login request carrying the first identifier to the service platform, it can periodically send an application login request to the service platform until it is accessed to the dedicated network slice.

[0170] It should be noted that the sequence of the above steps is only a specific example proposed for illustrating the embodiments of the present application, and the present application does not limit the sequence of the above steps, and those skilled in the art can adjust them as needed in actual application; and the sequence number of the above steps also does not limit the execution sequence.

[0171] The method for providing multi-user shared slice service provided by the embodiments of the present application provides a scheme for realizing multi-user shared slice service based on the same application account, which can realize that multiple user terminals under the same application account simultaneously use slice service without each user subscribing to slice, thereby saving the use cost of users and providing good user experience.

[0172] Figure 2 Another flowchart of the method for providing multi-user shared slice service provided by the embodiments of the present application is shown. The method is applied to a service platform, such as Figure 2 As shown in the figure, the method includes the following steps S201 to S204.

[0173] S201. Receiving an application login request carrying a first identifier sent by a user terminal, wherein the first identifier includes a user identifier.

[0174] In this step, the user terminal can be a smart phone, a tablet computer (PAD), a PC terminal (computer terminal), etc.

[0175] The first identifier can include a user identifier. The user identifier is used to distinguish different users, for example, can be a mobile phone number, in which case the user terminal sends an application login request carrying the mobile phone number to the service platform. The user identifier can also be an IMSI (International Mobile Subscriber Identification, International Mobile Subscriber Identification) or an ICCID (Integrate circuit card identity, also known as SIM card number). Of course, the user identifier can also be other identification codes that can distinguish different users, as long as it can uniquely identify the user, and the present application does not limit it. The user identifier corresponding to the user using the user terminal should be the user identifier of the user who has subscribed to slice service under the same application account.

[0176] When the user starts the application on the terminal, the user needs to send an application login request to the service platform through the terminal. The user can also switch different login accounts (i.e. the first identifier) multiple times, and each time the user needs to log in again and send an application login request carrying the corresponding first identifier to the service platform.

[0177] S202. According to the correspondence relationship between the user identifier and the application account pre-stored therein, an application account corresponding to the user identifier is queried, the number of users allowed to use the slice service simultaneously under the corresponding application account is queried as a first user number, and the number of users currently using the dedicated network slice under the application account is queried as a second user number.

[0178] In this step, the number of users is the number of user identifiers. In the case of a mobile phone number as a user identifier, the user identifier allowed to use the slice service simultaneously under the application account is the mobile phone number allowed to use the slice service simultaneously under the application account; the user identifier currently using the dedicated network slice under the application account is the mobile phone number currently using the dedicated network slice, which refers to the mobile phone number currently using the dedicated network slice, and the same application account can correspond to multiple mobile phone numbers currently using the dedicated network slice. The first user number and the second user number are at least one.

[0179] S203. In response to the first user number being equal to the second user number, the priority of the user identifier and the priority of all user identifiers currently using the dedicated network slice under the corresponding application account are queried.

[0180] S204. It is judged whether the priority of the user identifier is higher than the priority of one of all user identifiers currently using the dedicated network slice under the corresponding application account. If it is higher, a first dedicated network slice use request carrying the user identifier is generated, and the dedicated network slice service is provided for the corresponding user terminal based on the first dedicated network slice use request.

[0181] In this embodiment, since the number of users allowed to use the slice service simultaneously under the application account is equal to the number of users currently using the dedicated network slice under the application account, i.e., the number of users currently using the dedicated network slice has reached the upper limit, whether to allow the user terminal to use the dedicated network slice depends on whether the priority of the user identifier is higher than the priority of one of all user identifiers currently using the dedicated network slice under the application account. As long as the priority of the user identifier is higher than the priority of any one of all user identifiers currently using the dedicated network slice under the application account, the user terminal is allowed to use the dedicated network slice. In this case, the service platform generates a first dedicated network slice use request carrying the user identifier, and provides the dedicated network slice service for the user terminal based on the first dedicated network slice use request, so that the user terminal can run the application on the corresponding dedicated network slice.

[0182] Of course, the number of users allowed to use the slice service simultaneously under the application account cannot be less than the number of users currently using the dedicated network slice under the application account, i.e., the first user number cannot be less than the second user number.

[0183] In a specific embodiment, before step S201, the following steps S205 to S207 are further included.

[0184] S205. Receiving slice subscription information sent by the user terminal, the slice subscription information including an application account, a number of users under the application account that are allowed to use slice services at the same time, user identities that need to use slice services and respective corresponding priorities, and subscription requirements;

[0185] S206. Subscribing to a dedicated network slice that meets the subscription requirements for each user that needs to use slice services under the application account, respectively;

[0186] S207. Generating and storing a user-slice correspondence table based on the slice subscription information, the user-slice correspondence table including the application account, the number of users under the application account that are allowed to use slice services at the same time, and the user identities that need to use slice services and respective corresponding priorities.

[0187] In the embodiment, the user terminal that sends the application login request in step S201 and the user terminal that sends the slice subscription information in step S205 can be the same user terminal, or can be different user terminals, in other words, as long as one user subscribes to slice services, multiple users can share slice services.

[0188] In the embodiment, when a user subscribes to slice services, the user terminal can upload slice subscription information to the service platform. In addition to the application account, the number of users under the application account that are allowed to use slice services at the same time, the user identities that need to use slice services and respective corresponding priorities, and the subscription requirements, the slice subscription information can further include an application identifier for distinguishing different applications.

[0189] The application identifier is the identity of the application, which can be the package name of the application, etc. For example, the package name of iQiyi is com.qiyi.video, and the package name of Douyin is com.ss.android.ugc.aweme.

[0190] The application account can be shared by multiple users, and the same application account can be logged in and used on multiple user terminals (corresponding to multiple user identities) at the same time.

[0191] The number of users allowed to use the slice service under the application account at the same time can be set by the user. Specifically, when the user subscribes to the slice, the terminal can show the user the number of users allowed to use the slice service under the same application account at the same time and the corresponding price provided by the service platform for the user to choose. Generally, the more the number of users allowed to use the slice service under the same application account at the same time, the higher the corresponding price. The user can choose according to the actual demand.

[0192] The user terminal can provide a slice subscription information input interface under the application account. The user can input a plurality of user identifiers (such as mobile phone numbers) requiring to use the slice service under the application account on the interface, and set a corresponding priority for each user identifier, so that multiple users can share the slice service of an application after one user purchases the slice service of the application. Of course, the priorities of the corresponding user identifiers requiring to use the slice service under the same application account cannot be the same.

[0193] The user can also input the required subscription requirements, such as bandwidth and latency requirements of the slice, on the interface.

[0194] After the user completes the foregoing information selection, input, and setting work, the slice subscription information is formed and uploaded to the service platform.

[0195] In addition, after the user subscribes to the slice, the user identifier requiring to use the slice service and the priority thereof under the application account can also be modified. Specifically, the user terminal can also provide a slice subscription information modification interface under the application account, which shows the application identifier, the application account, the number of users allowed to use the slice service under the same application account at the same time, the user identifier requiring to use the slice service, and the corresponding priority of each user identifier. The user can modify the user identifier and the priority thereof having subscribed to the slice service under the same application account on the interface, and can also modify the number of users having subscribed to the slice service under the same application account. After the user modifies, the user terminal needs to upload the updated slice subscription information to the service platform again.

[0196] The service platform also generates and stores a user-slice correspondence table based on the slice subscription information. The user-slice correspondence table is used to store the correspondence of "application account-number of users allowed to use the slice service under the same application account at the same time-user identifier requiring to use the slice service and the corresponding priority of each user identifier".

[0197] In a specific embodiment, the application account corresponding to the user identifier is queried according to the correspondence between the user identifier and the application account pre-stored therein in step S202, specifically:

[0198] The application account corresponding to the user identifier is queried from the user-slice correspondence table.

[0199] In an embodiment, the query in step S202 corresponds to the number of users allowed to use the slice service under the application account as the first number of users, specifically:

[0200] Querying the number of users allowed to use the slice service under the application account from the user-slice correspondence table as the first number of users.

[0201] In an embodiment, the query in step S202 corresponds to the priority of the user identifier and the priority of all user identifiers currently using the dedicated network slice under the corresponding application account, specifically:

[0202] Querying the priority of each user identifier requiring slice service from the user-slice correspondence table to obtain the priority of the user identifier and the priority of all user identifiers currently using the dedicated network slice under the corresponding application account.

[0203] In an embodiment, after step S206, the following step S208 is further included.

[0204] S208. Configure the corresponding network slice identifier for each user requiring slice service under the application account.

[0205] In this embodiment, after the service platform subscribes to the dedicated network slice that meets the subscription requirements for each user requiring slice service under the application account, the service platform can configure the corresponding network slice identifier for each user requiring slice service under the application account. In this way, when the service platform receives an application login request sent by a user terminal of a user requiring slice service under the same application account, if the corresponding conditions are met, the service platform first searches for the network slice identifier configured for the user, and then provides dedicated network slice service based on the network slice corresponding to the network slice identifier.

[0206] Of course, after subscribing to the dedicated network slice, the service platform can not pre-configure the corresponding network slice identifier for each user requiring slice service under the application account. When the service platform receives an application login request sent by a user terminal of a user requiring slice service under the same application account, if the corresponding conditions are met, the service platform directly selects a network slice that meets the previous subscription requirements from the existing idle network slices at random, and uses the randomly selected network slice to provide dedicated network slice service.

[0207] In an embodiment, user authentication is required between the user terminal and the service platform, which can be achieved by one of the following four methods.

[0208] The first identification includes a user identification, and the user identification is a mobile phone number. The authentication process is as follows: the user selects "one-key login by local number" on the user terminal, the user terminal acquires the mobile phone number from the user mobile card inserted therein, and then sends an application login request carrying the "mobile phone number" and the "one-key login by local number" identification to the service platform. The service platform authenticates by the "one-key login by local number".

[0209] The second mode is as follows: the first identification includes a user identification, and the user identification is a mobile phone number. The authentication process is as follows: the service platform receives an application login request carrying a mobile phone number sent by the user terminal, and authenticates by a "verification code".

[0210] The third mode is as follows: the first identification includes a user identification and a password. The authentication process is as follows: the service platform receives an application login request carrying a user identification and a password sent by the user terminal, pre-stores a corresponding relationship between the user identification and the password, and matches the user identification and the password carried by the application login request with the pre-stored user identification and password to realize authentication.

[0211] The fourth mode is as follows: the first identification includes a user identification, an application account and a password. The authentication process is as follows: the service platform receives an application login request carrying a user identification, an application account and a password sent by the user terminal, and authenticates the user based on the application account, the password and the user identification in the application login request. Specifically, it is verified whether the application account and the password in the application login request match the pre-stored application account and password in the service platform, and whether the user identification in the application login request matches the pre-stored user identification corresponding to the application account in the service platform. If both are matched, the authentication is passed, and if any one is not matched, the authentication fails. In addition, the application login request sent by the user terminal is encrypted by a preset encryption algorithm, and the service platform receives the encrypted application login request and then decrypts it according to the corresponding decryption algorithm. Preferably, the application login request is encrypted and decrypted by an asymmetric encryption algorithm (such as RSA algorithm).

[0212] Correspondingly, step S202 is specifically as follows:

[0213] In response to the user authentication passing, the service platform queries the application account corresponding to the user identification according to the pre-stored corresponding relationship between the user identification and the application account, queries the first user number which is the number of users allowed to use the slice service under the corresponding application account, and queries the second user number which is the number of users currently using the dedicated network slice under the application account.

[0214] In this embodiment, after the service platform receives the application login request sent by the user terminal, it needs to be authenticated first. If the authentication is passed, the corresponding application account, the first user quantity and the second user quantity are queried. If the authentication is not passed, the application login request of the user terminal is rejected, and the process is ended.

[0215] In a specific implementation, the foregoing step S204 is split into three sub-steps, which are S204a. judging whether the priority of the user identifier is higher than the priority of one of all user identifiers currently using the dedicated network slice under the corresponding application account, if higher, executing step S204b, otherwise, ending the current process; S204b. generating a first dedicated network slice usage request carrying the user identifier; and S204c. providing the dedicated network slice service for the corresponding user terminal based on the first dedicated network slice usage request.

[0216] Then, before step S204c, the following step S204d is further included.

[0217] S204d. querying whether the current network state of the corresponding user terminal supports the dedicated network slice.

[0218] Correspondingly, step S203c is specifically:

[0219] In response to the query result that the current network state of the corresponding user terminal supports the dedicated network slice, the dedicated network slice service is provided for the corresponding user terminal based on the first dedicated network slice usage request.

[0220] In this embodiment, after the service platform receives the first dedicated network slice usage request sent by the user terminal, it needs to query whether the current network state of the user terminal supports the dedicated network slice. If it supports, step S203c is executed, and the service platform provides the dedicated network slice service for the corresponding user terminal based on the first dedicated network slice usage request.

[0221] In a specific implementation, after step S203d, the following steps S203e and S203f are further included.

[0222] S203e. in response to the query result that the current network state of the corresponding user terminal does not support the dedicated network slice, sending a network state switching request to the corresponding user terminal and starting timing, so that the corresponding user terminal receives the network state switching request and prompts the user to perform network switching based on the network state switching request;

[0223] S203f. judging whether the network state of the corresponding user terminal is switched to support the dedicated network slice within a first preset time threshold after the timing starts.

[0224] Correspondingly, step S203c is specifically:

[0225] In response to determining that the corresponding user terminal has switched the network state to support the dedicated network slice within a first preset time threshold after the timing starts, the service platform provides the dedicated network slice service for the corresponding user terminal based on the first dedicated network slice use request.

[0226] The first preset time threshold can be set and adjusted by those skilled in the art, for example, it can be set to 20 seconds, 30 seconds, etc.

[0227] In the embodiment, if the current network state of the user terminal corresponding to the user identifier does not support the dedicated network slice, the service platform sends a network state switching request to the user terminal, prompting the user to "switch to a network state that can use the dedicated network slice". If the user terminal completes the network state switching within the first preset time threshold, step S203c is executed, and the service platform provides the dedicated network slice service for the corresponding user terminal based on the first dedicated network slice use request; if the user terminal fails to complete the network state switching within the first preset time threshold, the current process is ended.

[0228] For example, the service platform queries that the user terminal corresponding to the user identifier currently resides in a 4G network, or the service platform queries that the user currently uses a wifi network and does not use a mobile data network. In these cases, the user terminal does not support the use of a 5G network slice. At this time, the user terminal prompts the user to "switch to a network state that can use the dedicated network slice". If the user turns on the 5G switch of the terminal within the first preset time threshold and successfully switches to the 5G network, the service platform provides the dedicated network slice service for the corresponding user terminal based on the first dedicated network slice use request.

[0229] In an optional embodiment, step S203c includes the following step C1.

[0230] C1. Based on the first dedicated network slice use request, the PDU session currently established by the corresponding user terminal is switched and mapped from the original default network slice of the bearer to the dedicated network slice provided for it.

[0231] The PDU session, i.e. PDU Session, provides data connectivity between the UE (User Equipment / User Terminal) and the DN (Data Network). All data traffic of the UE must be carried through the PDU session. In other words, the UE should establish a PDU session before sending data traffic; the PDU session must be initiated by the UE. After the core network accepts the request of the UE and allocates the corresponding control plane and data plane resources, the UE can transmit data between the DN.

[0232] In this embodiment, the service platform updates the routing policy of the user terminal based on the first dedicated network slice usage request, specifically, switches and maps the PDU session currently established by the user terminal from the original default network slice of the original bearer to the dedicated network slice provided for the user terminal, so as to establish a new PDU session for the application using the dedicated network slice.

[0233] In another optional embodiment, the step S203c comprises the following step C2.

[0234] C2. return the service information of the dedicated network slice to the corresponding user terminal based on the first professional network slice usage request, so that the corresponding user terminal receives the service information of the dedicated network slice, ends the original PDU session of the application, and establishes a new PDU session for the application based on the service information of the dedicated network slice.

[0235] The service information of the network slice at least comprises S-NSSAI (Single Network Slice Selection Assistance Information) and TD (Traffic Descriptor). The S-NSSAI is the identifier of the network slice, and the TD can be the identity of the application, the application server network domain name information, the application server address information, etc. The service information of the network slice records the correspondence between the network slice and the application that can use the network slice. After the user terminal receives the service information of the dedicated network slice sent by the service platform, the user terminal ends the original PDU session of the application, and establishes a new PDU session for the application based on the service information of the dedicated network slice, so that the application runs on the corresponding dedicated network slice.

[0236] In this embodiment, after the service platform returns the service information of the dedicated network slice to the corresponding user terminal based on the first professional network slice usage request, the user terminal updates the routing policy of the terminal based on the service information of the dedicated network slice, specifically, ends the original PDU session of the application, and establishes a new PDU session for the application using the dedicated network slice.

[0237] Correspondingly, after the step C1 or C2, the following steps S209 and S210 are further included.

[0238] S209. In response to that the PDU session currently established by the corresponding user terminal has been switched and mapped from the original default network slice of the original bearer to the dedicated network slice provided for the user terminal, or in response to that the corresponding user terminal has established a new PDU session for the application using the dedicated network slice, generate an add user notification message;

[0239] S210. Add the user identifier to the list of user identifiers currently using the dedicated network slice under the application account based on the add user notification message.

[0240] In this embodiment, after the service platform switches the PDU session currently established by the user terminal from the default network slice of the original bearer to the dedicated network slice provided for it, or after the user terminal establishes a new PDU session using the dedicated network slice, the service platform adds the user identifier to the list of user identifiers currently using the dedicated network slice under the application account, thereby increasing the number of users currently using the dedicated network slice under the application account, i.e., the second user number plus one.

[0241] In a specific implementation, after step C1 or C2, the following steps S211 to S213 are further included.

[0242] S211. Start timing in response to the PDU session currently established by the corresponding user terminal having been switched from the default network slice of the original bearer to the dedicated network slice provided for it, or in response to the corresponding user terminal having established a new PDU session for the application using the dedicated network slice;

[0243] S212. Periodically determine whether the corresponding user terminal has traffic usage on the dedicated network slice within a second preset time threshold after the timing starts, if yes, end the current process, if no, execute step S213;

[0244] S213. Inhibit the corresponding user terminal from continuing to use the dedicated network slice.

[0245] The second preset time threshold can be set and adjusted by those skilled in the art, for example, it can be set to 3 minutes, 5 minutes, etc.

[0246] In this embodiment, after the PDU session currently established by the corresponding user terminal has been switched from the default network slice of the original bearer to the dedicated network slice provided for it, or after the corresponding user terminal has established a new PDU session for the application using the dedicated network slice, if the corresponding user terminal still has no traffic usage on the dedicated network slice beyond the second preset time threshold, the service platform directly prohibits the corresponding user terminal from continuing to use the dedicated network slice to release resources to other user terminals that need to use the dedicated network slice service.

[0247] The method for the service platform to prohibit the user terminal from continuing to use the dedicated network slice can be that when the user identifier corresponding user terminal subsequently requests the service platform to use the dedicated network slice, the service platform directly rejects the request.

[0248] In a specific embodiment, after step S213, the method further comprises steps S214 and S215.

[0249] S214. Generating a delete user notification message carrying the corresponding user identifier;

[0250] S215. Deleting the corresponding user identifier from the list of user identifiers currently using the dedicated network slice under the application account based on the delete user notification message.

[0251] In this embodiment, after the service platform prohibits the corresponding user terminal from continuing to use the dedicated network slice, the user identifier is also deleted from the list of user identifiers currently using the dedicated network slice under the application account, thereby reducing the number of users currently using the dedicated network slice under the application account, i.e., the second user number is reduced by one.

[0252] In a specific embodiment, after step S204, the method further comprises step S216.

[0253] S216. Receiving a second dedicated network slice usage request carrying the corresponding user identifier automatically sent by the corresponding user terminal according to the preset rules due to the inability to use the dedicated network slice, or receiving a second dedicated network slice usage request carrying the user identifier generated and sent by the corresponding user terminal based on the active request input by the user, and then returning to step S202 to query the corresponding application account, the first user number, and the second user number.

[0254] In this embodiment, after the service platform provides the dedicated network slice service for the corresponding user terminal based on the first dedicated network slice use request, as long as the user terminal cannot use the dedicated network slice for any reason, on one hand, the user terminal sends a second dedicated network slice use request carrying the user identifier to the service platform when the application login request is applied or when the application is switched from the background to the foreground in the application login state, on the other hand, the user terminal can periodically send a second dedicated network slice use request carrying the user identifier to the service platform, that is, the user terminal automatically requests the service platform to use the dedicated network slice according to the preset rule, wherein the period of the user terminal sending the second dedicated network slice use request to the service platform can be set and adjusted by those skilled in the art, for example, it can be set to 5 minutes, 10 minutes. Alternatively, the user terminal can also provide an input page for the user to input an active request for using the dedicated network slice in the application login state through the input page, that is, the user actively selects to request the service platform to use the dedicated network slice. And after the service platform receives the second dedicated network slice use request sent by the user terminal, it can first verify whether the user identifier matches the user identifier corresponding to the application account stored in advance, and if it matches, it returns to execute the steps of querying the corresponding application account, the first user quantity and the second user quantity.

[0255] In a specific embodiment, after determining in step S204a that the priority of the user identifier is higher than the priority of one of all user identifiers of the current dedicated network slice corresponding to the application account, the following steps S217 to S219 are further included.

[0256] S217. Selecting a user identifier with the lowest priority from all user identifiers of the current dedicated network slice corresponding to the application account;

[0257] S218. Generating a dedicated network slice prohibition use notification message carrying the user identifier with the lowest priority;

[0258] S219. Prohibiting the user terminal corresponding to the user identifier with the lowest priority from continuing to use the dedicated network slice based on the dedicated network slice prohibition use notification message.

[0259] In this embodiment, if the priority of the user identifier is higher than the priority of any one of all user identifiers of the current dedicated network slice corresponding to the application account, the service platform will generate a dedicated network slice prohibition use notification message carrying the user identifier with the lowest priority, and prohibit the user terminal corresponding to the user identifier with the lowest priority from continuing to use the dedicated network slice based on the dedicated network slice prohibition use notification message.

[0260] The method for the service platform to prohibit the user terminal corresponding to the user identity with the lowest priority from continuing to use the dedicated network slice can comprise: when the user terminal corresponding to the user identity with the lowest priority subsequently requests the service platform to use the dedicated network slice, the service platform directly rejects the request; or the service platform can terminate the PDU session of the user terminal corresponding to the user identity with the lowest priority and send service information of a default network slice to the user terminal corresponding to the user identity with the lowest priority, the default network slice being a network slice that can be used by all applications, and after receiving the service information of the default network slice, the user terminal updates its routing strategy and establishes a new PDU session using the default network slice; or the service platform can remap the PDU session of the user terminal corresponding to the user identity with the lowest priority from the original dedicated network slice to the default network slice.

[0261] In a specific embodiment, after step S219, steps S220 and S221 are further included.

[0262] S220. Receiving a third dedicated network slice usage request carrying the user identity with the lowest priority, which is periodically sent by the user terminal corresponding to the user identity with the lowest priority because the user terminal is prohibited from continuing to use the dedicated network slice.

[0263] S221. In response to a decrease in the number of users currently using the dedicated network slice under the corresponding application account, providing the user terminal corresponding to the user identity with the lowest priority with the dedicated network slice service.

[0264] In the embodiment, after the service platform prohibits the user terminal corresponding to the user identity with the lowest priority from continuing to use the dedicated network slice, if the user subsequently still wants to use the dedicated network slice service, the user can periodically send a third dedicated network slice usage request to the service platform, and then once the number of users currently using the dedicated network slice under the corresponding application account decreases (e.g., a user exits or is prohibited from using the dedicated network slice because of a long period of inactivity), the service platform can directly provide the terminal used by the user with the dedicated network slice without needing to query the corresponding application account, the first number of users, and the second number of users in step S202, and without needing to repeatedly perform the previous query and authentication steps.

[0265] In a specific embodiment, after step S204a judges that the priority of the user identity is not higher than the priority of one of all user identities currently using the dedicated network slice corresponding to the application account, steps S222 and S223 are further included.

[0266] S222. sending a corresponding prompt message to the user terminal corresponding to the user identifier, so that the user terminal corresponding to the user identifier receives the prompt message and periodically sends an application login request carrying the first identifier to the service platform based on the prompt message;

[0267] S223. receiving the application login request carrying the first identifier periodically sent by the user terminal corresponding to the user identifier, and returning to step S202 to query the corresponding application account, the first user quantity and the second user quantity.

[0268] In this embodiment, if the service platform determines that the priority of the user identifier is not higher than the priority of one of all user identifiers currently using the dedicated network slice under the corresponding application account, that is, the condition for providing the dedicated network slice service for the user terminal corresponding to the user identifier is not met, the service platform can send a corresponding prompt message to the user terminal corresponding to the user identifier about this situation. The specific message content is not limited by the present application. After receiving the prompt message sent by the service platform, if the user terminal still wants to use the dedicated network slice service, it can periodically send an application login request to the service platform until it is connected to the dedicated network slice.

[0269] In a specific embodiment, after step S204a determines that the priority of the user identifier is not higher than the priority of one of all user identifiers currently using the dedicated network slice corresponding to the application account, the following step S224 is further included.

[0270] S224. receiving the application login request carrying the first identifier periodically sent by the user terminal corresponding to the user identifier after the third preset time threshold from when the user terminal sends the application login request carrying the first identifier to the service platform, and returning to step S202 to query the corresponding application account, the first user quantity and the second user quantity.

[0271] In this embodiment, if the service platform determines that the priority of the user identifier is not higher than the priority of one of all user identifiers currently using the dedicated network slice under the corresponding application account, that is, the condition for providing the dedicated network slice service for the user terminal corresponding to the user identifier is not met, the service platform will not provide the dedicated network slice service for the user terminal corresponding to the user identifier. In this case, if the user terminal has not been connected to the dedicated network slice after the third preset time threshold from when the user terminal sends the application login request carrying the first identifier to the service platform, it can periodically send an application login request to the service platform until it is connected to the dedicated network slice.

[0272] It should be noted that the sequence of the above steps is only a specific example proposed for the purpose of illustrating the embodiments of the present application, and the present application does not limit the sequence of the above steps, and those skilled in the art can adjust them as needed in actual application; moreover, the sequence number of the above steps does not limit the execution sequence.

[0273] The method for providing a multi-user shared slice service provided by the embodiments of the present application provides a scheme for realizing multi-user shared slice service based on the same application account, which can realize that multiple user terminals under the same application account simultaneously use the slice service without each user subscribing to the slice, thereby saving the use cost of the user and providing a better user experience.

[0274] Figure 3 The structure diagram of the user terminal provided by the embodiments of the present application is shown in FIG. 1. Figure 3 As shown in FIG. 1, the user terminal comprises a first sending module 301.

[0275] The first sending module 301 is configured to send an application login request carrying a first identifier to a service platform, the first identifier comprising a user identifier, so that the service platform receives the application login request, queries an application account corresponding to the user identifier according to the corresponding relationship between the user identifier and the application account pre-stored therein, queries a first user number of users simultaneously allowed to use the slice service under the corresponding application account, and queries a second user number of users currently using the dedicated network slice under the corresponding application account, in response to the first user number being equal to the second user number, queries a priority of the user identifier and priorities of all user identifiers of users currently using the dedicated network slice under the corresponding application account, judges whether the priority of the user identifier is higher than the priority of one of all user identifiers of users currently using the dedicated network slice under the corresponding application account, and if so, generates a first dedicated network slice use request carrying the user identifier, and provides the dedicated network slice service for the corresponding user terminal based on the first dedicated network slice use request.

[0276] In an embodiment, the first sending module 301 is further configured to send slice subscription information to the service platform before sending the application login request carrying the first identifier to the service platform, the slice subscription information comprising an application account, a number of users under the application account that are allowed to use slice services simultaneously, user identifiers that need to use slice services and respective priorities, and subscription requirements, so that the service platform subscribes to a dedicated network slice meeting the subscription requirements for each user under the application account that needs to use slice services based on the slice subscription information, and generates and stores a user-slice correspondence table based on the slice subscription information, the user-slice correspondence table comprising the application account, the number of users under the application account that are allowed to use slice services simultaneously, and the user identifiers that need to use slice services and respective priorities.

[0277] In an embodiment, the user terminal further comprises a first receiving module 302 and a prompting module 303.

[0278] The first receiving module 302 is configured to receive a network state switching request sent by the service platform after the first sending module 301 sends the application login request carrying the first identifier to the service platform, wherein the service platform queries whether the current network state of the corresponding user terminal supports a dedicated network slice before providing the dedicated network slice service for the corresponding user terminal based on the first dedicated network slice usage request, and sends a network state switching request to the corresponding user terminal and starts timing in response to the query result that the current network state of the corresponding user terminal does not support the dedicated network slice; the prompting module 303 is configured to prompt the user to switch the network based on the network state switching request, so that the service platform provides the dedicated network slice service for the corresponding user terminal based on the first dedicated network slice usage request in response to determining that the corresponding user terminal has switched the network state to support the dedicated network slice within a first preset time threshold after the timing starts, or in response to the query result that the current network state of the corresponding user terminal supports the dedicated network slice.

[0279] In an embodiment, the user terminal further comprises a PDU session establishment module 304.

[0280] The first receiving module 302 is further configured to receive the service information of the dedicated network slice sent by the service platform after the first sending module 301 sends the application login request carrying the first identifier to the service platform.

[0281] In a specific embodiment, the first sending module 301 is further configured to, after sending the application login request carrying the first identifier to the service platform, if the user terminal cannot use the dedicated network slice, automatically send a second dedicated network slice use request carrying the user identifier to the service platform according to a preset rule, so that the service platform receives the second dedicated network slice use request and returns to perform the operation of querying the corresponding application account, the first user quantity and the second user quantity.

[0282] Alternatively, the first receiving module 302 is further configured to, after the first sending module 301 sends the application login request carrying the first identifier to the service platform, if the user terminal cannot use the dedicated network slice, receive a user input active request; the first sending module 301 is further configured to generate a second dedicated network slice use request carrying the user identifier based on the active request and send it to the service platform, so that the service platform receives the second dedicated network slice use request and returns to perform the operation of querying the corresponding application account, the first user quantity and the second user quantity.

[0283] In a specific embodiment, the first sending module 301 is further configured to, if the user terminal corresponding to the user identifier has accessed the dedicated network slice and is the user identifier with the lowest priority among all user identifiers currently using the dedicated network slice under the corresponding application account, and the service platform receives an application login request sent by a user terminal corresponding to another user identifier with a higher priority than the user identifier under the corresponding application account and needing to use the slice service, causing the user terminal corresponding to the user identifier to be prohibited by the service platform from continuing to use the dedicated network slice, periodically send a third dedicated network slice use request carrying the user identifier to the service platform, so that the service platform receives the third dedicated network slice use request and provides the user terminal corresponding to the user identifier with the dedicated network slice service in response to the decrease in the number of user terminals currently using the dedicated network slice under the corresponding application account.

[0284] In an embodiment, the first receiving module 302 is further configured to receive a prompt message sent by the service platform when the priority of the user identifier is not higher than the priority of one of all user identifiers currently using the dedicated network slice under the corresponding application account, and the first sending module 301 is further configured to periodically send an application login request carrying the first identifier to the service platform based on the prompt message, so that the service platform receives the application login request carrying the first identifier periodically sent by the user terminal corresponding to the first identifier, and returns to perform the operation of querying the corresponding application account, the first user quantity and the second user quantity.

[0285] In an embodiment, the first sending module 301 is further configured to periodically send an application login request carrying the first identifier to the service platform when the priority of the user identifier is not higher than the priority of one of all user identifiers currently using the dedicated network slice under the corresponding application account, and the user terminal corresponding to the user identifier has not been accessed to the dedicated network slice after a third preset time threshold since the user terminal sends the application login request carrying the first identifier to the service platform, so that the service platform receives the application login request carrying the first identifier periodically sent by the user terminal corresponding to the user identifier, and returns to perform the operation of querying the corresponding application account, the first user quantity and the second user quantity.

[0286] The user terminal provided by the embodiment of the application can interact with the service platform, and can realize simultaneous use of slice services by multiple user terminals under the same application account without the need for each user to subscribe to a slice, thereby saving the use cost of the user and providing a good user experience.

[0287] Figure 4 The service platform provided by the embodiment of the application is shown in a structural schematic diagram. As shown in the figure, the service platform comprises a second receiving module 401, a querying module 402, a judging module 403, a request generating module 404 and a service providing module 405. Figure 4

[0288] ​The second receiving module 401 is configured to receive an application login request carrying a first identifier sent by a user terminal, and the first identifier comprises a user identifier; the querying module 402 is configured to query an application account corresponding to the user identifier according to a corresponding relationship between the user identifier and the application account pre-stored therein, query a first user quantity of users simultaneously allowed to use slice services under the corresponding application account, and query a second user quantity of users currently using a dedicated network slice under the application account; in response to the first user quantity being equal to the second user quantity, the querying module 402 is configured to query a priority of the user identifier and priorities of all user identifiers currently using the dedicated network slice under the corresponding application account; the judging module 403 is configured to judge whether the priority of the user identifier is higher than a priority of one of all user identifiers currently using the dedicated network slice under the corresponding application account; the request generating module 404 is configured to generate a first dedicated network slice use request carrying the user identifier when the judgment result of the judging module is higher; and the service providing module 405 is configured to provide a dedicated network slice service for the corresponding user terminal based on the first dedicated network slice use request.

[0289] In a specific embodiment, the service platform further comprises a slice subscription module 406 and a storage module 407.

[0290] The second receiving module 401 is further configured to receive slice subscription information sent by the user terminal before receiving the application login request carrying the first identifier sent by the user terminal, and the slice subscription information comprises an application account, a user quantity of users simultaneously allowed to use slice services under the application account, user identifiers needing to use slice services and respective corresponding priorities, and a subscription requirement; the slice subscription module 406 is configured to subscribe to a dedicated network slice meeting the subscription requirement for each user needing to use slice services under the application account; and the storage module 407 is configured to generate and store a user-slice corresponding relationship table based on the slice subscription information, and the user-slice corresponding relationship table comprises the application account, the user quantity of users simultaneously allowed to use slice services under the application account, and the user identifiers needing to use slice services and respective corresponding priorities.

[0291] In an embodiment, the query module 402 queries the application account corresponding to the user identifier according to the pre-stored correspondence between the user identifier and the application account, specifically, querying the application account corresponding to the user identifier from the user slice correspondence table stored in the storage module 407; the query module 402 queries the first user quantity as the number of users allowed to use the slice service under the corresponding application account, specifically, querying the first user quantity as the number of users allowed to use the slice service under the application account from the user slice correspondence table stored in the storage module 407; the query module 402 queries the priority of the user identifier and the priority of all user identifiers currently using the dedicated network slice under the corresponding application account, specifically, querying the priority of each user identifier needing to use the slice service from the user slice correspondence table stored in the storage module 407 to obtain the priority of the user identifier and the priority of all user identifiers currently using the dedicated network slice under the corresponding application account.

[0292] In an embodiment, the service platform further comprises an identifier allocation module 408.

[0293] The identifier allocation module 408 is configured to configure the corresponding network slice identifier for each user needing to use the slice service under the application account after the slice subscription module has respectively subscribed to the dedicated network slice meeting the subscription requirement for each user needing to use the slice service under the application account.

[0294] In an embodiment, the query module 402 is further configured to query whether the current network state of the corresponding user terminal supports the dedicated network slice. Correspondingly, the service providing module 405 is specifically configured to provide the dedicated network slice service for the corresponding user terminal based on the first dedicated network slice usage request when the query result of the query module 402 is that the current network state of the corresponding user terminal supports the dedicated network slice.

[0295] In an embodiment, the service platform further comprises a second sending module 409 and a timing module 410.

[0296] The second sending module 409 is configured to, when the query result of the query module 402 is that the current network state of the corresponding user terminal does not support the dedicated network slice, send a network state switching request to the corresponding user terminal, so that the corresponding user terminal receives the network state switching request and prompts the user to perform network switching based on the network state switching request. The timing module 410 is configured to start timing after the second sending module 409 sends the network state switching request to the corresponding user terminal. The judgment module 403 is further configured to judge whether the corresponding user terminal switches the network state to support the dedicated network slice within a first preset time threshold after the timing module 410 starts timing. The service providing module 405 is specifically configured to, when the judgment result of the judgment module 403 is that the corresponding user terminal has switched the network state to support the dedicated network slice within the first preset time threshold after the timing starts, provide the dedicated network slice service for the corresponding user terminal based on the first dedicated network slice use request.

[0297] In an optional implementation, the service providing module 405 includes a session mapping unit. The service platform further includes a message generation module 411 and an update module 412.

[0298] The session mapping unit is configured to, based on the first dedicated network slice use request, switch and map the PDU session currently established by the corresponding user terminal from the original bearing default network slice to the dedicated network slice provided for it. The message generation module 411 is configured to, after the PDU session currently established by the corresponding user terminal has been switched and mapped from the original bearing default network slice to the dedicated network slice provided for it, generate an add user notification message. The update module 412 is configured to, based on the add user notification message, add the user identifier to the user identifier list of the current dedicated network slice in use under the application account.

[0299] In another optional implementation, the service providing module 405 includes a sending unit. The service platform further includes a message generation module 411 and an update module 412.

[0300] The sending unit is configured to, based on the first professional network slice use request, return the service information of the dedicated network slice to the corresponding user terminal, so that the corresponding user terminal receives the service information of the dedicated network slice, ends the original PDU session of the application, and uses the dedicated network slice to establish a new PDU session for the application based on the service information of the dedicated network slice. The message generation module 411 is configured to, after the corresponding user terminal has used the dedicated network slice to establish a new PDU session for the application, generate an add user notification message. The update module 412 is configured to, based on the add user notification message, add the corresponding user identifier to the user identifier list of the current dedicated network slice in use under the application account.

[0301] In an embodiment, the timing module 410 is further configured to start timing when the PDU session currently established by the corresponding user terminal is switched from the default network slice of the original bearer to the dedicated network slice provided for the corresponding user terminal, or in response to that the corresponding user terminal has established a new PDU session for the application using the dedicated network slice. The judging module 403 is further configured to periodically judge whether the corresponding user terminal has traffic usage on the dedicated network slice within a second preset time threshold after the timing module 410 starts timing. The service providing module 404 is further configured to, in response to the judging result of the judging module 403 being that the corresponding user terminal has no traffic usage on the dedicated network slice within the second preset time threshold after the timing module starts timing, prohibit the corresponding user terminal from continuing to use the dedicated network slice.

[0302] In an embodiment, the message generating module 411 is further configured to, after the service providing module 404 prohibits the corresponding user terminal from continuing to use the dedicated network slice, generate a delete user notification message carrying the corresponding user identifier. The updating module 412 is further configured to delete the corresponding user identifier from the list of user identifiers currently using the dedicated network slice under the application account based on the delete user notification message.

[0303] In an embodiment, the second receiving module 401 is further configured to, after the service providing module 405 provides the dedicated network slice service for the corresponding user terminal based on the first dedicated network slice usage request, receive a second dedicated network slice usage request carrying the corresponding user identifier automatically sent by the corresponding user terminal according to a preset rule due to the inability to use the dedicated network slice, or receive a second dedicated network slice usage request carrying the user identifier generated and sent by the corresponding user terminal based on a user input active request. The querying module 402 is further configured to, after the second receiving module 401 receives the second dedicated network slice usage request, continue to perform the operation of querying the corresponding application account, the first number of users and the second number of users.

[0304] In an embodiment, the service platform further comprises a selection module 413.

[0305] The selection module 413 is configured to, in response to the judging result of the judging module 403 being that the priority of the user identifier is higher than the priority of one of all user identifiers currently using the dedicated network slice under the corresponding application account, select a user identifier with the lowest priority from all user identifiers currently using the dedicated network slice under the corresponding application account. The message generating module 411 is further configured to generate a dedicated network slice prohibition usage notification message carrying the user identifier with the lowest priority. The service providing module 405 is further configured to, based on the dedicated network slice prohibition usage notification message, prohibit the corresponding user terminal of the user identifier with the lowest priority from continuing to use the dedicated network slice.

[0306] In one specific embodiment, the second receiving module 401 is further configured to, after the service providing module 405 prohibits the user terminal corresponding to the lowest priority user identifier from continuing to use the dedicated network slice based on the dedicated network slice prohibition notification message, receive a third dedicated network slice usage request periodically sent by the user terminal corresponding to the lowest priority user identifier due to being prohibited from continuing to use the dedicated network slice. The service providing module 405 is further configured to, when the number of users currently using the dedicated network slice under the corresponding application account decreases, provide dedicated network slice services to the user terminal corresponding to the lowest priority user identifier.

[0307] In one specific implementation, the second sending module 408 is further configured to, when the judgment result of the judgment module 403 is that the priority of the user identifier is not higher than the priority of one of the user identifiers of all currently used dedicated network slices corresponding to the application account, send a corresponding prompt message to the user terminal corresponding to the user identifier, so that the user terminal corresponding to the user identifier receives the prompt message and periodically sends an application login request carrying the first identifier to the service platform based on the prompt message; the second receiving module 401 is further configured to receive the application login requests carrying the first identifier periodically sent by the user terminal corresponding to the user identifier. Then the query module 402 performs a corresponding query operation.

[0308] In one specific embodiment, the second receiving module 401 is further configured to, when the judgment result of the judgment module 403 is that the priority of the user identifier is not higher than the priority of one of the user identifiers of all currently used dedicated network slices corresponding to the application account, receive application login requests carrying the first identifier sent periodically to the service platform by the user terminal corresponding to the user identifier that has not been connected to the dedicated network slice after a third preset time threshold since it sent an application login request carrying the first identifier to the service platform. Then the query module 402 performs the corresponding query operation.

[0309] The service platform provided in this embodiment of the invention interacts with user terminals, enabling multiple user terminals under the same application account to use the slice service simultaneously without each user having to subscribe to slices separately, thus saving users usage costs and providing a better user experience.

[0310] Figure 5 and Figure 6 These are schematic diagrams illustrating two structural configurations of a system providing a multi-user shared slice service according to embodiments of the present invention. For example... Figure 5 and Figure 6 As shown, the system includes a user terminal 51 and a service platform 52. Figure 5In an embodiment, the service platform 52 comprises an operator platform 522 integrated with an application platform 521, and a plurality of application platforms 521 can be integrated in the same operator platform 522. Figure 6 In an embodiment, the service platform 52 comprises a plurality of separate application platforms 521 and a plurality of separate operator platforms 522, and the same application platform 521 can correspond to a plurality of operator platforms 522, the same operator platform 522 can correspond to a plurality of application platforms 521, and for the same application account, only one application platform corresponds, but at the same time, a plurality of user terminals and a plurality of operator platforms can correspond, wherein the user identifier corresponding to each user terminal respectively corresponds to the respective operator platform.

[0311] It should be noted that the system for sharing a slice service by multiple users in the embodiment comprises a user terminal and a service platform for executing each step in the foregoing method embodiment, and the principle has been described in detail in the foregoing method embodiment, which will not be described here.

[0312] The system for sharing a slice service by multiple users provided by the embodiment provides a scheme for realizing sharing of a slice service by multiple users based on the same application account, and can realize simultaneous use of a slice service by multiple user terminals under the same application account without the need for each user to separately subscribe to a slice, thereby saving the use cost of the user and providing a good user experience.

[0313] Based on the same technical concept, the embodiment of the application correspondingly provides a computer device, as shown in the accompanying drawings. Figure 7 The computer device comprises a memory 71 and a processor 72, and the memory 71 stores a computer program, and when the processor 72 runs the computer program stored in the memory 71, the processor 72 executes the foregoing method for sharing a slice service by multiple users.

[0314] Based on the same technical concept, the embodiment of the application correspondingly provides a computer readable storage medium, which stores a computer program, and when the processor executes the computer program, the processor executes the foregoing method for sharing a slice service by multiple users.

[0315] In summary, the method, system, user terminal, service platform, computer device, and storage medium for sharing a slice service by multiple users provided by the embodiment of the application can use the characteristic that the same application account can be logged in and used on multiple user terminals at the same time, and the slice service originally subscribed to a single user is subscribed to an application provider (application platform), and then sold to the user by the application provider, which can realize simultaneous use of a slice service by multiple user terminals under the same application account without the need for each user to separately subscribe to a slice, thereby saving the use cost of the user and providing a good user experience.

[0316] Those skilled in the art can understand that all or some of the steps in the method disclosed above, the functional modules / units in the system and the device can be implemented as software, firmware, hardware and appropriate combinations thereof. In the hardware implementation, the division between the functional modules / units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component can have multiple functions, or one function or step can be performed by several physical components in cooperation. Some or all of the physical components can be implemented as software executed by a processor, such as a central processing unit, a digital signal processor or a microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit. Such software can be distributed on a computer readable medium, which can include computer storage media (or non-transitory media) and communication media (or transitory media). As 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 storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tapes, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired information and can be accessed by a computer. In addition, as known to those skilled in the art, communication media typically includes computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism, and can include any information delivery medium.

[0317] Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, and not to limit them; although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that: it can still modify the technical solutions recorded in the foregoing embodiments, or make equivalent replacement to part or all of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A method of multi-user shared slice service, characterized by, The method applied to a user terminal comprises: sending an application login request carrying a first identifier to a service platform, the first identifier comprising a user identifier, so that the service platform receives the application login request, queries an application account corresponding to the user identifier according to a corresponding relationship between the user identifier and the application account pre-stored therein, queries a first user number of users simultaneously allowed to use slice services under the corresponding application account, and queries a second user number of users currently using a dedicated network slice under the corresponding application account, in response to the first user number being equal to the second user number, queries a priority of the user identifier and priorities of all user identifiers currently using the dedicated network slice under the corresponding application account, uses a user identifier corresponding to a user of the user terminal as a user identifier having subscribed to a slice service under the same application account, judges whether the priority of the user identifier is higher than a priority of one of all user identifiers currently using the dedicated network slice under the corresponding application account, if higher, generates a first dedicated network slice use request carrying the user identifier, and provides the dedicated network slice service for the corresponding user terminal based on the first dedicated network slice use request, and selects a user identifier with the lowest priority from all user identifiers currently using the dedicated network slice under the corresponding application account, generates a dedicated network slice use prohibition notification message carrying the user identifier with the lowest priority, and prohibits the user terminal corresponding to the user identifier with the lowest priority from continuing to use the dedicated network slice based on the dedicated network slice use prohibition notification message.

2. The method of claim 1, wherein, Before sending the application login request carrying the first identifier to the service platform, the method further comprises: sending slice subscription information to the service platform, the slice subscription information comprising an application account, a user number of users simultaneously allowed to use slice services under the application account, user identifiers needing to use slice services and respective corresponding priorities, and subscription requirements, so that the service platform receives the slice subscription information, subscribes to dedicated network slices meeting the subscription requirements for each user needing to use slice services under the application account, and generates and stores a user-slice corresponding relationship table based on the slice subscription information, the user-slice corresponding relationship table comprising the application account, the user number of users simultaneously allowed to use slice services under the application account, and the user identifiers needing to use slice services and respective corresponding priorities.

3. The method of claim 1, wherein, After sending the application login request carrying the first identifier to the service platform, the method further comprises: receiving a network state switching request sent by the service platform, wherein the service platform queries whether a current network state of the corresponding user terminal supports the dedicated network slice before providing the dedicated network slice service for the corresponding user terminal based on the first dedicated network slice use request, and in response to a query result that the current network state of the corresponding user terminal does not support the dedicated network slice, sends the network state switching request to the corresponding user terminal and starts timing; and The user is prompted to switch the network based on the network state switching request, so that the service platform provides the special network slice service for the corresponding user terminal based on the first special network slice use request in response to determining that the corresponding user terminal has switched the network state to support the special network slice within a first preset time threshold after the timing starts, or in response to the query result that the current network state of the corresponding user terminal supports the special network slice.

4. The method of claim 1, wherein, After sending the application login request carrying the first identifier to the service platform, the method further includes: receiving the service information of the special network slice sent by the service platform; and ending the original PDU session of the application, and establishing a new PDU session for the application based on the special network slice service information, so that the service platform generates an add user notification message in response to that the user terminal has established a new PDU session for the application using the special network slice, and adds the user identifier to the user identifier list of the current in-use special network slice under the application account based on the add user notification message.

5. The method according to any one of claims 1-4, characterized in that, After sending the application login request carrying the first identifier to the service platform, the method further includes: in response to being unable to use the special network slice, automatically sending a second special network slice use request carrying the user identifier to the service platform according to a preset rule; or, receiving a user input active request, generating a second special network slice use request carrying the user identifier based on the active request and sending it to the service platform, so that the service platform receives the second special network slice use request and returns to execute the steps of querying the corresponding application account, the first user quantity and the second user quantity.

6. The method according to any one of claims 1-4, characterized in that, After sending the application login request carrying the first identifier to the service platform, the method further includes: in response to that the user terminal corresponding to the user identifier has accessed the special network slice and is the user identifier with the lowest priority among all the user identifiers currently using the special network slice under the corresponding application account, and the service platform further receives an application login request sent by a user terminal corresponding to another user identifier with a higher priority than the user identifier under the corresponding application account and needing to use the slice service, the user terminal corresponding to the user identifier is prohibited by the service platform to continue using the special network slice, and a third special network slice use request carrying the user identifier is periodically sent to the service platform, so that the service platform receives the third special network slice use request and provides the special network slice service for the user terminal corresponding to the user identifier in response to that the number of user terminals currently using the special network slice under the corresponding application account is reduced.

7. The method according to any one of claims 1 to 4, characterized in that, After sending the application login request carrying the first identifier to the service platform, the method further includes: in response to that the priority of the user identifier is not higher than the priority of one of all the user identifiers currently using the special network slice under the corresponding application account, receiving a prompt message about this situation sent by the service platform; and in response to that the priority of the user identifier is not higher than the priority of one of all the user identifiers currently using the special network slice under the corresponding application account, receiving a prompt message about this situation sent by the service platform; and Periodically sending an application login request carrying the first identifier to the service platform based on the prompt message, so that the service platform receives the application login request carrying the first identifier periodically sent by the user terminal corresponding to the first identifier, and returns to execute the steps of querying the corresponding application account, the first user quantity and the second user quantity.

8. The method according to any one of claims 1-4, characterized in that, After sending the application login request carrying the first identifier to the service platform, further comprising: In response to the priority of the user identifier being not higher than the priority of one of all user identifiers currently using the dedicated network slice under the corresponding application account, and the user terminal corresponding to the user identifier not being accessed to the dedicated network slice after a third preset time threshold since the user terminal corresponding to the user identifier sends the application login request carrying the first identifier to the service platform, periodically sending an application login request carrying the first identifier to the service platform, so that the service platform receives the application login request carrying the first identifier periodically sent by the user terminal corresponding to the first identifier, and returns to execute the steps of querying the corresponding application account, the first user quantity and the second user quantity.

9. A method of a multi-user shared slice service, characterized by, Applied to the service platform, the method comprises: Receiving an application login request carrying a first identifier sent by a user terminal, the first identifier comprising a user identifier; According to the correspondence between the pre-stored user identifier and the application account, querying the application account corresponding to the user identifier, querying the number of users allowed to use the slice service at the same time under the corresponding application account as the first user quantity, and querying the number of users currently using the dedicated network slice under the application account as the second user quantity; In response to the first user quantity being equal to the second user quantity, querying the priority of the user identifier and the priority of all user identifiers currently using the dedicated network slice under the corresponding application account, using the user identifier corresponding to the user of the user terminal as the user identifier of the user who has subscribed to the slice service under the same application account; Judging whether the priority of the user identifier is higher than the priority of one of all user identifiers currently using the dedicated network slice under the corresponding application account, if higher, generating a first dedicated network slice use request carrying the user identifier, and providing the dedicated network slice service for the corresponding user terminal based on the first dedicated network slice use request; Selecting a user identifier with the lowest priority from all user identifiers currently using the dedicated network slice under the corresponding application account, generating a dedicated network slice prohibition use notification message carrying the user identifier with the lowest priority, and prohibiting the user terminal corresponding to the user identifier with the lowest priority from continuing to use the dedicated network slice based on the dedicated network slice prohibition use notification message.

10. The method of claim 9, wherein, Before receiving the application login request carrying the first identifier sent by the user terminal, further comprising: Receiving slice subscription information sent by the user terminal, the slice subscription information comprising an application account, the number of users allowed to use the slice service at the same time under the application account, user identifiers needing to use the slice service and respective corresponding priorities, and subscription requirements; respectively subscribe to the dedicated network slice meeting the subscription requirement for each user under the application account who needs to use the slice service; and generate and store a user-slice correspondence table based on the slice subscription information, the user-slice correspondence table including the application account, the number of users under the application account who are simultaneously allowed to use the slice service, and the user identifiers who need to use the slice service and their respective priorities.

11. The method of claim 10, wherein the application account corresponding to the user identifier is queried according to the correspondence relationship between the user identifier and the application account pre-stored therein, and specifically, the application account corresponding to the user identifier is queried from the user-slice correspondence table; the number of users under the application account who are simultaneously allowed to use the slice service is taken as the first number of users, and specifically, the number of users under the application account who are simultaneously allowed to use the slice service is queried from the user-slice correspondence table as the first number of users; the priority of the user identifier and the priorities of all user identifiers of the dedicated network slice currently in use under the corresponding application account are queried, and specifically, the priority of the user identifier and the priorities of all user identifiers of the dedicated network slice currently in use under the corresponding application account are obtained by querying the respective priorities of the user identifiers who need to use the slice service from the user-slice correspondence table.

12. The method of claim 10, wherein, After respectively subscribing to the dedicated network slice meeting the subscription requirement for each user under the application account who needs to use the slice service, the method further includes: configuring the corresponding network slice identifier for each user under the application account who needs to use the slice service.

13. The method of claim 9, wherein, Before providing the dedicated network slice service for the corresponding user terminal based on the first dedicated network slice usage request, the method further includes: querying whether the current network state of the corresponding user terminal supports the dedicated network slice; the dedicated network slice service is provided for the corresponding user terminal based on the first dedicated network slice usage request, and specifically, the dedicated network slice service is provided for the corresponding user terminal based on the first dedicated network slice usage request in response to the query result that the current network state of the corresponding user terminal supports the dedicated network slice.

14. The method of claim 13, wherein, After querying whether the current network state of the corresponding user terminal supports the dedicated network slice, the method further includes: in response to the query result that the current network state of the corresponding user terminal does not support the dedicated network slice, sending a network state switching request to the corresponding user terminal and starting timing to enable the corresponding user terminal to receive the network state switching request and prompt the user to perform network switching based on the network state switching request; and determining whether the network state of the corresponding user terminal is switched to support the dedicated network slice within a first predetermined time threshold after the timing starts; the dedicated network slice service is provided for the corresponding user terminal based on the first dedicated network slice usage request, and specifically, the dedicated network slice service is provided for the corresponding user terminal based on the first dedicated network slice usage request in response to the determination that the network state of the corresponding user terminal has been switched to support the dedicated network slice within the first predetermined time threshold after the timing starts.

15. The method of claim 9, wherein, The providing of the dedicated network slice service for the corresponding user terminal based on the first dedicated network slice use request comprises: switching and mapping a PDU session currently established by the corresponding user terminal from a default network slice of an original bearer to a dedicated network slice provided for the corresponding user terminal based on the first dedicated network slice use request; after the providing of the dedicated network slice service for the corresponding user terminal based on the first dedicated network slice use request, further comprising: generating an add user notification message in response to that the PDU session currently established by the corresponding user terminal has been switched and mapped from the default network slice of the original bearer to the dedicated network slice provided for the corresponding user terminal; and adding the user identity to a user identity list of the dedicated network slice currently in use under the application account based on the add user notification message.

16. The method of claim 9, wherein, The providing of the dedicated network slice service for the corresponding user terminal based on the first dedicated network slice use request comprises: returning service information of the dedicated network slice to the corresponding user terminal based on the first dedicated network slice use request, so that the corresponding user terminal receives the service information of the dedicated network slice, ends an original PDU session of the application, and establishes a new PDU session for the application based on the service information of the dedicated network slice; after the providing of the dedicated network slice service for the corresponding user terminal based on the first dedicated network slice use request, further comprising: generating an add user notification message in response to that the corresponding user terminal has established the new PDU session for the application based on the dedicated network slice; and adding the corresponding user identity to the user identity list of the dedicated network slice currently in use under the application account based on the add user notification message.

17. The method according to claim 15 or 16, characterized in that, Further comprising: starting timing in response to that the PDU session currently established by the corresponding user terminal has been switched and mapped from the default network slice of the original bearer to the dedicated network slice provided for the corresponding user terminal, or in response to that the corresponding user terminal has established the new PDU session for the application based on the dedicated network slice; periodically judging whether the corresponding user terminal has service use on the dedicated network slice within a second preset time threshold after the timing starts; if not, prohibiting the corresponding user terminal from continuing to use the dedicated network slice.

18. The method of claim 17, wherein, after the prohibiting of the corresponding user terminal from continuing to use the dedicated network slice, further comprising: generating a delete user notification message carrying the corresponding user identity; and deleting the corresponding user identity from the user identity list of the dedicated network slice currently in use under the application account based on the delete user notification message.

19. The method of claim 9, wherein, after the providing of the dedicated network slice service for the corresponding user terminal based on the first dedicated network slice use request, further comprising: receiving a second dedicated network slice use request carrying the corresponding user identity and automatically sent by the corresponding user terminal according to a preset rule due to the inability to use the dedicated network slice, or receiving the second dedicated network slice use request carrying the user identity and actively generated and sent by the corresponding user terminal based on a user input; and returning to the step of querying the corresponding application account, the first user quantity and the second user quantity. The providing of the dedicated network slice service for the corresponding user terminal based on the first dedicated network slice use request comprises: returning service information of the dedicated network slice to the corresponding user terminal based on the first dedicated network slice use request, so that the corresponding user terminal receives the service information of the dedicated network slice, ends an original PDU session of the application, and establishes a new PDU session for the application based on the service information of the dedicated network slice; after the providing of the dedicated network slice service for the corresponding user terminal based on the first dedicated network slice use request, further comprising: generating an add user notification message in response to that the corresponding user terminal has established the new PDU session for the application based on the dedicated network slice; and adding the corresponding user identity to a user identity list of the dedicated network slice currently in use under the application account based on the add user notification message. Further comprising: starting timing in response to that the PDU session currently established by the corresponding user terminal has been switched and mapped from the default network slice of the original bearer to the dedicated network slice provided for the corresponding user terminal, or in response to that the corresponding user terminal has established the new PDU session for the application based on the dedicated network slice; periodically judging whether the corresponding user terminal has service use on the dedicated network slice within a second preset time threshold after the timing starts; if not, prohibiting the corresponding user terminal from continuing to use the dedicated network slice. after the prohibiting of the corresponding user terminal from continuing to use the dedicated network slice, further comprising: generating a delete user notification message carrying the corresponding user identity; and deleting the corresponding user identity from the user identity list of the dedicated network slice currently in use under the application account based on the delete user notification message. after the providing of the dedicated network slice service for the corresponding user terminal based on the first dedicated network slice use request, further comprising: receiving a second dedicated network slice use request carrying the corresponding user identity and automatically sent by the corresponding user terminal according to a preset rule due to the inability to use the dedicated network slice, or receiving the second dedicated network slice use request carrying the user identity and actively generated and sent by the corresponding user terminal based on a user input; and returning to the step of querying the corresponding application account, the first user quantity and the second user quantity.

20. The method of claim 9, wherein, The method further comprises: receiving a third dedicated network slice usage request carrying the user identifier with the lowest priority periodically sent by the user terminal corresponding to the user identifier due to being prohibited from continuing to use the dedicated network slice; and providing the user terminal corresponding to the user identifier with the lowest priority with the dedicated network slice service in response to a decrease in the number of users currently using the dedicated network slice under the corresponding application account.

21. The method of claim 9, wherein, The method further comprises: if the priority of the user identifier is not higher than the priority of one of all user identifiers currently using the dedicated network slice under the corresponding application account, sending a corresponding prompt message to the user terminal corresponding to the user identifier, so that the user terminal corresponding to the user identifier receives the prompt message and periodically sends an application login request carrying the first identifier to the service platform based on the prompt message; and receiving the application login request carrying the first identifier periodically sent by the user terminal corresponding to the user identifier, and returning to the step of querying the corresponding application account, the first user quantity and the second user quantity.

22. The method of claim 9, wherein, The method further comprises: if the priority of the user identifier is not higher than the priority of one of all user identifiers currently using the dedicated network slice under the corresponding application account, receiving the application login request carrying the first identifier periodically sent by the user terminal corresponding to the user identifier after the third preset time threshold since the user terminal corresponding to the user identifier sends the application login request carrying the first identifier to the service platform; and returning to the step of querying the corresponding application account, the first user quantity and the second user quantity.

23. A user terminal, characterized by The method further comprises: a sending module configured to send an application login request carrying a first identifier to a service platform, the first identifier including a user identifier, so that the service platform receives the application login request, queries an application account corresponding to the user identifier according to a corresponding relationship between the user identifier and the application account pre-stored therein, queries a number of users allowed to use the slice service under the corresponding application account as a first user quantity, and queries a number of users currently using the dedicated network slice under the corresponding application account as a second user quantity, in response to the first user quantity being equal to the second user quantity, queries a priority of the user identifier and priorities of all user identifiers currently using the dedicated network slice under the corresponding application account; and The user identifier corresponding to the user of the user terminal is a user identifier that has subscribed to a slice service under the same application account, and it is determined whether the priority of the user identifier is higher than the priority of one of all user identifiers currently using a dedicated network slice under the corresponding application account. If it is higher, a first dedicated network slice use request carrying the user identifier is generated, and dedicated network slice service is provided for the corresponding user terminal based on the first dedicated network slice use request. In addition, the user identifier with the lowest priority is selected from all user identifiers currently using a dedicated network slice under the corresponding application account, a dedicated network slice prohibition use notification message carrying the user identifier with the lowest priority is generated, and the user terminal corresponding to the user identifier with the lowest priority is prohibited from continuing to use the dedicated network slice based on the dedicated network slice prohibition use notification message.

24. A service platform, characterized by Comprise: A receiving module is configured to receive an application login request carrying a first identifier sent by a user terminal, wherein the first identifier comprises a user identifier; A query module is configured to query an application account corresponding to the user identifier according to a pre-stored correspondence relationship between the user identifier and the application account, query a first user quantity as a quantity of users simultaneously allowed to use a slice service under the corresponding application account, and query a second user quantity as a quantity of users currently using a dedicated network slice under the application account; In response to the first user quantity being equal to the second user quantity, the priority of the user identifier and the priority of all user identifiers currently using a dedicated network slice under the corresponding application account are queried, and the user identifier corresponding to the user of the user terminal is a user identifier that has subscribed to a slice service under the same application account; A judgment module is configured to determine whether the priority of the user identifier is higher than the priority of one of all user identifiers currently using a dedicated network slice under the corresponding application account; A request generation module is configured to generate a first dedicated network slice use request carrying the user identifier when the judgment result of the judgment module is higher; A service providing module is configured to provide dedicated network slice service for the corresponding user terminal based on the first dedicated network slice use request; A selection module is configured to select a user identifier with the lowest priority from all user identifiers currently using a dedicated network slice under the corresponding application account when the priority of the user identifier is higher than the priority of one of all user identifiers currently using a dedicated network slice under the corresponding application account; And, A message generation module is configured to generate a dedicated network slice prohibition use notification message carrying the user identifier with the lowest priority; The service providing module is further configured to prohibit the user terminal corresponding to the user identifier with the lowest priority from continuing to use the dedicated network slice based on the dedicated network slice prohibition use notification message.

25. A computer device, comprising: A computer program product, comprising a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program stored in the memory, the processor executes the method of the multi-user shared slice service according to any one of claims 1-8 or the method of the multi-user shared slice service according to any one of claims 9-22.

26. A computer readable storage medium having stored thereon a computer program, characterized in that, The computer program is executed by the processor, and the processor executes the method of the multi-user shared slice service according to any one of claims 1-8 or the method of the multi-user shared slice service according to any one of claims 9-22.

Images