CN116319942A

CN116319942A - Slice management method, device, operating system and storage medium

Info

Publication number: CN116319942A
Application number: CN202310237562.7A
Authority: CN
Inventors: 万文寅
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Priority date: 2023-03-10
Filing date: 2023-03-10
Publication date: 2023-06-23

Abstract

The application discloses a slice management method, a slice management device, an operation system and a storage medium, wherein the slice management method comprises the following steps: the method comprises the steps that an operating system receives a slice connection request of a first application; in the case where the operating system does not record the network congestion status, the operating system sends a slice connection request to the modem, through which the slice connection of the first application is established.

Description

Slice management method, device, operating system and storage medium

Technical Field

The application belongs to the technical field of communication, and particularly relates to a slice management method, a slice management device, an operating system and a storage medium.

Background

With the development of electronic devices, the technology of network slicing is continuously evolving, for example, an enterprise type is a slice type for applying to enterprise-level services, and there may be multiple enterprise-level applications, and network slicing supporting up to 5 different enterprise-level applications currently. The Latency delay type is a service type requiring extremely low delay requirements for the terminal, such as requiring a response speed of the order of milliseconds, and is well suited for making this type of request, and currently only one such network slice is supported. The Bandwidth type is a slice type for high Bandwidth applications, where applications with extremely high Bandwidth requirements may request such network slices. Then in a slicing network, a situation may occur in which the slicing network is congested when there are multiple applications making slicing requests at the same time.

Disclosure of Invention

An object of the embodiments of the present application is to provide a slice management method, apparatus, operating system, and storage medium, which can solve the problem of slice network congestion when there are multiple applications to make a slice request.

In a first aspect, an embodiment of the present application provides a slice management method, including: the method comprises the steps that an operating system receives a slice connection request of a first application; in the case that the operating system does not record the network congestion state, the operating system sends a slice connection request to the modem, and establishes a slice connection of the first application through the modem.

In a second aspect, an embodiment of the present application provides a slice management apparatus, including: a receiving module and a processing module; the receiving module is used for receiving a slice connection request of the first application; and the processing module is used for sending the slice connection request to the modem and establishing the slice connection of the first application through the modem under the condition that the operating system does not record the network congestion state.

In a third aspect, embodiments of the present application provide an operating system comprising a processor and a memory storing a program or instructions executable on the processor, which when executed by the processor, implement the steps of the method as described in the first aspect.

In a fourth aspect, embodiments of the present application provide a readable storage medium having stored thereon a program or instructions which when executed by a processor implement the steps of the method according to the first aspect.

In a fifth aspect, embodiments of the present application provide a chip, where the chip includes a processor and a communication interface, where the communication interface is coupled to the processor, and where the processor is configured to execute a program or instructions to implement a method according to the first aspect.

In a sixth aspect, embodiments of the present application provide a computer program product stored in a storage medium, the program product being executable by at least one processor to implement the method according to the first aspect.

In the embodiment of the application, an operating system receives a slice connection request of a first application; in the case that the operating system does not record the network congestion state, the operating system sends a slice connection request to the modem, and establishes a slice connection of the first application through the modem. In the scheme, when the operating system receives the slice connection request of the first application, the operating system can judge the network condition, and in the network uncongested state, the slice connection request of the first application is sent to the modem so as to establish the slice connection of the first application through the modem, thereby avoiding the condition of slice network congestion.

Drawings

FIG. 1 is one of the flowcharts of a slice management method provided in an embodiment of the present application;

FIG. 2 is a second flowchart of a slice management method according to an embodiment of the present disclosure;

FIG. 3 is a third flowchart of a slice management method according to an embodiment of the present disclosure;

fig. 4 is a schematic structural diagram of a slice management apparatus according to an embodiment of the present application;

fig. 5 is a schematic diagram of a hardware structure of an electronic device according to an embodiment of the present application;

fig. 6 is a second schematic diagram of a hardware structure of an electronic device according to an embodiment of the present application.

Detailed Description

Technical solutions in the embodiments of the present application will be clearly described below with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present application are within the scope of the protection of the present application.

The terms first, second and the like in the description and in the claims, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged, as appropriate, such that embodiments of the present application may be implemented in sequences other than those illustrated or described herein, and that the objects identified by "first," "second," etc. are generally of a type and not limited to the number of objects, e.g., the first object may be one or more. Furthermore, in the description and claims, "and/or" means at least one of the connected objects, and the character "/", generally means that the associated object is an "or" relationship.

The slice management method provided by the embodiment of the application is described in detail below through specific embodiments and application scenes thereof with reference to the accompanying drawings.

With the development of electronic devices, the technology of network slicing is continuously evolving, for example, an enterprise type is a slice type for applying to enterprise-level services, and there may be multiple enterprise-level applications, and network slicing supporting up to 5 different enterprise-level applications currently. The Latency delay type is a service type requiring extremely low delay requirements for the terminal, such as requiring a response speed of the order of milliseconds, and is well suited for making this type of request, and currently only one such network slice is supported. The Bandwidth type is a slice type for high Bandwidth applications, where applications with extremely high Bandwidth requirements may request such network slices. Some client applications, for example: communication applications, music, web games and the like have no very strict requirements on bandwidth and delay, but the application of the type is the application which is most widely used by users and has higher requirements on communication quality; such applications may establish a connection with a client type slice. Then in a slicing network, a situation may occur in which the slicing network is congested when there are multiple applications making slicing requests at the same time.

An embodiment of the present application provides a slice management method, and fig. 1 shows a flowchart of the slice management method provided in the embodiment of the present application, where the method may be applied to an electronic device. As shown in fig. 1, the slice management method provided in the embodiment of the present application may include the following steps 201 to 203.

Step 201, an operating system receives a slice connection request of a first application.

Alternatively, in an embodiment of the present application, the first application may be any one of the following: enterprise-level applications, carrier applications, communication-type applications, games, music, shopping-type applications, etc.

Step 202, in the case that the operating system does not record the network congestion state, the operating system sends a slice connection request to the modem, and establishes a slice connection of the first application through the modem.

Optionally, in this embodiment of the present application, when the network is congested, the network side may report a network congestion message to the modem, and then the modem may report the network congestion message to the operating system, where the slice management module of the operating system may record the current network congestion state.

Specifically, when the slice management module of the operating system does not record the network congestion state, the operating system may send a slice connection request to the modem, which may match the appropriate slice for the first application and request the slice from the network to establish a slice connection for the first application.

Optionally, in an embodiment of the present application, the slice connection request may include a target parameter, so that the modem establishes the slice connection of the first application based on the target parameter.

Illustratively, the above-described target parameters consist of slice type information and operating system identification required by the first application.

For example, after receiving the slice connection request of the first application, the operating system may determine, according to an application type of the first application, a slice type required by the first application, thereby obtaining slice type information required by the first application.

Illustratively, the above-mentioned target parameter may be represented by an app id, which is determined by an os id and an app id, and the os id may be an android os id or an ios id depending on the operating system. The oapplid is slice type information required for the first application.

Illustratively, an entry ENTERPRISE type slice may be defined as identified as NET_CAPABITY_ENTERPRISE_1 through NET_CAPABITY_ENTERPRISE_5; CBS type slices may be defined identified as net_capability_cbs; the latex type slice may be defined as NET_CAPABLITY_latex; the bandwidth type slice may be defined as NET_CAPABLITY_bandwidth; the client type slice (Customer Category Slicing, CCS) may be defined as net_capability_ CUSTOMER_1 to NET_CAPABLITY_CUSTOMER_6.

It should be noted that some users use a wide range of applications, for example: communication applications, music, web games, etc., where these client applications have no very strict requirements on bandwidth and delay, but have high requirements on communication quality, the application defines slices required by the client applications with high requirements on communication quality as client type slices, and similarly, the client applications can be defined by negotiations of various operators according to the slice types required by the client applications, which is not limited in the embodiments of the application.

Optionally, in the embodiment of the present application, the application of the high communication quality requirement is an application of the communication quality requirement higher than a preset threshold, for example: applications requiring network stability, reliability of transmitted information, etc. above a preset threshold.

For example: when the first application is a communication type application and the required slice is a client type slice, the operating system may allocate net_capability_CUSTOMER_1 to the first application as slice type information in the target parameter.

Optionally, in the embodiment of the present application, after receiving the target parameter, the modem may select, according to a user routing policy (UE Route Selection Policy, urs) issued by the network side, a matched slice for the first application, so as to establish a slice connection of the first application.

Illustratively, the ursp includes an identification of at least one available slice.

Specifically, after the modem receives the target parameter, a matching slice may be selected for the first application based on slice type information required by the first application from the at least one available slice, so as to establish a slice connection of the first application.

Illustratively, in the at least one available slice, if the number of slices matched with the first application is 1, establishing a connection between the first application and the slice; if the number of the slices matched with the first application is greater than 1, establishing connection between the first application and any one slice in the matched slices.

Alternatively, in the embodiment of the present application, the "the operating system establishes the slice connection of the first application through the modem" in the above step 202 may be specifically implemented through the following steps 202a and 202 b.

In step 202a, the operating system records a network congestion status in case the slice connection request is rejected by the modem.

Specifically, after receiving the slice connection request of the first application sent by the operating system, the modem may match an appropriate slice for the first application and request the slice to the network, where if the network is congested, the network side may reject the slice connection request of the first application sent by the modem, and then the modem may reject the slice connection request of the first application sent by the operating system and report a network congestion message to the operating system, so that the operating system records the network congestion state.

For example, as shown in fig. 2, after the operating system receives the slice connection request of the first application (e.g., app 1), the slice connection request is sent to the modem, and the modem continues to send the slice connection request to the network side, at this time, if the network is congested, the network side will reject the slice connection request of App1 sent by the modem, so that the modem rejects the slice connection request of App1 sent by the operating system, and reports a network congestion message to the operating system, so that the operating system records the network congestion state.

Step 202b, under the condition that a network uncongested message reported by a network side is received, the operating system issues a slice connection request to the modem, and establishes slice connection of the first application through the modem.

It will be appreciated that, when a network uncongested message reported by the network side is subsequently received, the operating system may send a slice connection request of the first application to the modem again, so as to establish a slice connection of the first application through the modem.

The embodiment of the application provides a slice management method, wherein an operating system receives a slice connection request of a first application; in the case that the operating system does not record the network congestion state, the operating system sends a slice connection request to the modem, and establishes a slice connection of the first application through the modem. In the scheme, when the operating system receives the slice connection request of the first application, the operating system can judge the network condition, and in the network uncongested state, the slice connection request of the first application is sent to the modem so as to establish the slice connection of the first application through the modem, thereby avoiding the condition of slice network congestion.

Optionally, in the embodiment of the present application, the slice management method provided in the embodiment of the present application may further include the following step 301 and step 302.

Step 301, in the case that the operating system records the network congestion state, the operating system interrupts sending the slice connection request.

It can be understood that when the network side has reported the network congestion message and the operating system records the network congestion state, if the operating system receives the slice connection request of the first application, the operating system stops sending the slice connection request to the modem, i.e. interrupts sending the slice connection request.

Step 302, under the condition that a network uncongested message reported by a network side is received, the operating system issues a slice connection request to the modem, and establishes slice connection of a first application through the modem.

It will be appreciated that, when a network uncongested message reported by the network side is subsequently received, the operating system may send a slice connection request of the first application to the modem, so as to establish a slice connection of the first application through the modem.

Optionally, in an embodiment of the present application, after the step 202, the slice management method provided in an embodiment of the present application further includes a step 401 described below.

Step 401, if a network congestion message reported by a network side is received, the operating system sends a slice disconnection request to the modem to disconnect the slice connection of the first application.

Specifically, in the case of establishing slice connection of the first application, if the operating system receives, through the modem, a network congestion message reported by the network side, the operating system may send a slice disconnection request to the modem to disconnect the slice connection of the first application.

It will be appreciated that the slice is already unavailable due to network congestion, and thus the operating system may send a slice disconnect request to the modem to disconnect the slice of the first application.

Alternatively, in the embodiment of the present application, the first application is an application with a high communication quality requirement, and the "the operating system establishes the slice connection of the first application through the modem" in the above step 202 may be specifically implemented through the following step 202 b.

Step 202b, the operating system establishes a connection between the first application and the first slice through the modem.

In this embodiment of the present application, the first slice is a client type slice.

Alternatively, in the embodiment of the present application, the application of the above high communication quality requirement may be any one of the following: communication applications, games, music, shopping applications, etc.

Optionally, in the embodiment of the present application, when the first application is an application with a high communication quality requirement, and the operating system receives a slice connection request of the first application, the operating system may send a target parameter to the modem, where the target parameter includes slice type information required by the first application, so that the modem may select, based on the target parameter, a first slice matching a slice type required by the first application from at least one available slice, to establish a connection between the first application and the first slice.

Optionally, in the embodiment of the present application, after the step 202b, the slice management method provided in the embodiment of the present application further includes the following steps 501 and 502.

Step 501, the operating system receives a slice connection request of the second application.

In this embodiment of the present application, the second application is an application with a high communication quality requirement.

Step 502, in a case that the number of available client type slices indicated by the network side is smaller than or equal to the number of applications of the connected client type slices, the operating system establishes connection between the second application and the first slice through the modem.

It can be understood that, after the operating system establishes connection between the first application with high communication quality requirement and the first slice through the modem, the operating system receives a slice connection request of the second application with high communication quality requirement, and at this time, if the number of available client type slices indicated by the network side is less than or equal to the number of applications of the connected client type slices, the operating system establishes connection between the second application and the first slice through the modem.

It will be appreciated that since the number of applications connected to a client type slice is greater than or equal to the number of available client type slices, indicating that the slice resources are strained, the operating system may perform slice consolidation, and establish a connection between the second application and the first slice through the modem based on the connection between the first application and the first slice.

Illustrating: the first application (e.g., app 1) is connected to the first slice (e.g., slice 1), and in the case where the number of available client type slices indicated on the network side is 2 and the number of applications of connected client type slices is 4, the operating system establishes a connection of the second application (e.g., app 2) to the first slice (e.g., slice 1) through the modem.

Specifically, after the connection between the first application and the first slice is established, a network card may be established and named as name1; after the operating system receives the slice connection request of the second application and issues the slice connection request to the modem, the modem can know that the second application requests a client type slice through slice type information (for example, the slice type information is NET_CAPABILITY_CUSTOMER_2) required by the second application in the target parameters carried by the request, so that the second application can be directly paired to the first slice without being issued to the network side and paired to the network card name1; the network card registers in the operating system and sets a route, and the data flows of the first application and the second application flow from the name1 to the modem and are finally sent to the network side through the first slice in the protocol stack.

Optionally, in the embodiment of the present application, the operating system may set that the number of applications using the client type slice cannot exceed the first preset number, for example: 6.

For example, an application listening service module in the operating system may manage requests of client applications, where the requests issued by the application listening service module to a slice management service module in the operating system may not exceed 6.

In the first case, when the connection between the first application and the first slice is established and the network side indicates that the number of available client type slices is 3, if a slice connection request of the second application is received, the operating system may establish the connection between the second application and the first slice through the modem.

Further, if the operating system receives a slice connection request of an application with a high communication quality requirement after establishing a connection between the second application and the first slice through the modem, the operating system may establish a connection between the certain application and another client type slice through the modem, the another client type slice being different from the first slice.

Illustratively, when the modem establishes a connection of the certain application with another client-type slice, if the network resource changes, the other client-type slice is not available, and the connection of the certain application with the first slice is established.

It will be appreciated that since the number of applications using client type slices is set to not exceed 6 and the network side indicates that the number of available client type slices is 3, every two applications with high communication quality requirements can be combined with the same client type slice to establish a connection.

In the second case, when the connection between the first application and the first slice is established and the network side indicates that the number of available client type slices is 2, if a slice connection request of the second application is received, the operating system may establish the connection between the second application and the first slice through the modem.

Further, if the operating system receives a slice connection request of an application with a certain high communication quality requirement after the connection between the second application and the first slice is established through the modem, the operating system can still establish the connection between the certain application and the first slice through the modem.

It will be appreciated that since the number of applications using client type slices is set to not exceed 6 and the network side indicates that the number of available client type slices is 2, every three applications with high communication quality requirements can be combined with the same client type slice to establish a connection.

In the third case, when the connection between the first application and the first slice is established and the number of available client type slices indicated by the network side is 1, if a slice connection request of other applications with high communication quality requirements is received, the operating system still establishes the connection between the other applications with high communication quality requirements and the first slice through the modem.

It will be appreciated that since the number of applications using client type slices is set to not exceed 6 and the network side indicates that the number of available client type slices is 1, applications requiring high communication quality are all merged with the same client type slice to establish a connection.

Therefore, the network slice resources can be fully utilized, network congestion is avoided as much as possible, and meanwhile, good slice communication quality of each application establishing connection with the client type slice is ensured.

Optionally, in an embodiment of the present application, after the step 502, the slice management method provided in an embodiment of the present application further includes a step 601 described below.

In step 601, in case that the number of available client type slices indicated by the network side is greater than the number of applications connected to the client type slices, the operating system disconnects the second application from the first slice through the modem, and establishes connection between the second application and the second slice.

In this embodiment of the present application, the number of applications where the second slice has established a connection is zero.

It will be appreciated that after the operating system establishes a connection between the first application and the first slice through the modem and a connection between the second application and the first slice, if the number of applications of the connected client type slices is less than the number of available client type slices, i.e. the number of available client type slices is sufficient, the operating system may cancel the slice merging, i.e. disconnect the second application from the first slice through the modem and establish a connection between the second application and the second slice.

Thus, the flexibility of the application in establishing slice connection is improved.

Optionally, in the embodiment of the present application, after the step 502, the slice management method provided in the embodiment of the present application further includes the following steps 701 and 702.

Step 701, the operating system receives a slice connection request of the third application.

In the embodiment of the present application, the third application is an application with high communication quality requirements.

It will be appreciated that the third application described above is an application requesting client type slicing.

Step 702, if the number of applications for which the client type slice connection has been established is greater than the threshold number, the operating system interrupts sending the slice connection request.

Alternatively, in the embodiment of the present application, the operating system may set the priority of the application requesting the low-latency type slice, the high-bandwidth type slice, the enterprise type slice, the operator type slice, and the like to be high priority, and the priority of the application requesting the client type slice to be low priority.

Optionally, in the embodiment of the present application, when receiving a slice connection request of a third application, that is, a slice connection request of a low-priority application, the operating system may determine whether the number of applications for which client-type slice connection has been established is greater than a threshold number, and if so, the operating system interrupts sending the slice connection request.

In this way, network congestion can be avoided since the operating system can control the number of applications that establish client-type slice connections.

For example, in the event that the number of applications for which client-type slice connections have been established is greater than a threshold number, the operating system may release the client-type slice used by the target application and then send a slice connection request to the modem through which the slice connection for the third application is established.

It will be appreciated that since the operating system may release the client type slice used by the target application when the number of applications for which the client type slice connection has been established is greater than the threshold number such that the number of applications for which the client type slice connection has been established is less than or equal to the threshold number, the operating system may send a slice connection request for the third application to the modem to establish the slice connection for the third application through the modem.

Illustratively, the target application is an application for which a client type slice connection has been established, and the target application may be any one of the following: the method comprises the steps of using applications with the information smaller than a preset threshold value in the background running applications, switching the application from an open state to a closed state, and not using a network in preset duration in the background running applications.

Illustratively, the above-described usage information may include at least one of: frequency of use, duration of use, number of uses, etc.

In this embodiment of the present application, as shown in fig. 3, the slice management method provided in this embodiment of the present application may include the following steps S1 to S5.

In step S1, if the number of applications for which the client type slice connection has been established is greater than the threshold number, the operating system determines whether there is an application release slice in the applications for which the client type slice connection has been established. If yes, executing step S2; if not, go to step S3.

And S2, the operating system releases the client type slice used by the application.

And step S3, the operating system judges whether an application is closed in the applications with the established client type slice connection. If yes, executing step S2; if not, go to step S4.

And S4, the operating system judges whether an application runs in the background in the application with the established client type slice connection, and the network is not used in a preset time period. If yes, executing step S2; if not, go to step S5.

And S5, the operating system judges whether an application runs in the background in the application with the established client type slice connection, and the use information is smaller than a preset threshold. If yes, go to step S2.

Therefore, unnecessary slice resources can be released in time, the waste of slice resources is avoided, and meanwhile, network congestion is avoided.

Optionally, in the embodiment of the present application, after the operating system establishes the connection between the first application and the first slice through the modem and the connection between the second application and the first slice, if a slice connection request of the high priority application is received, the operating system does not perform any restriction processing.

Optionally, in an embodiment of the present application, the slice management method provided in the embodiment of the present application may further include a step 801 described below.

In step 801, when a message from a network congestion state to a network non-congestion state is received, the operating system sends a connection request of at least one fourth application to the modem within a first time period, and establishes connection between the at least one fourth application and the N third slices through the modem.

The at least one fourth application is an application with high communication quality requirement for sending a slice connection request to the operating system in a first time period, the third slice is a client type slice, and N is a positive integer.

Optionally, in the embodiment of the present application, when receiving a message reported by the network side and converted from a network congestion state to a network non-congestion state, the operating system may start a timer to establish, through the modem, connection with the N third slices for at least one fourth application in the first period.

The first period of time is a period of time corresponding to a preset duration after the timer is started.

Specifically, the operating system may start a timer, such as: 10 minutes, and suggesting a modem number of customer type slices to use over a first time period; the modem may determine the number of client type slices to use over a first time period in combination with the number of available client type slices indicated at the network side.

It should be noted that, the number of the client type slices is the value of N, for example, the number of the client type slices is 2, and the number of the fourth applications is 3, and then the combined connection between the 3 fourth applications and the 2 third slices is established through the modem.

For example, the modem may select a smaller value among the number of client type slices recommended by the operating system to use and the number of available client type slices indicated by the network side as the number of client type slices to use within the first time period.

For example: if the number of client type slices recommended to be used by the operating system is 1 and the number of available client type slices indicated by the network side is 2, the modem selects a smaller value (the number of client type slices recommended to be used by the operating system) as the number of client type slices used in the first time period range, so that when the operating system sends a connection request of at least one fourth application to the modem in the first time period range, connection between the at least one fourth application and 1 third slice is established through the modem.

Therefore, the problem that the network is congested again because a plurality of fourth applications are connected with more third slices through the modem after the network is changed from the congested state to the uncongested state is avoided.

Optionally, in the embodiment of the present application, after the step 801, the slice management method provided in the embodiment of the present application further includes a step 901 described below.

Step 901, if no network congestion message reported by the network side is received within the first time period, the operating system establishes connection between at least one fifth application and M fourth slices through the modem within the second time period.

The at least one fifth application includes a fourth application, and an application with high communication quality requirement for sending a slice connection request to the operating system in a second time period, wherein the fourth slice is a client type slice, and M is an integer greater than N.

Optionally, in the embodiment of the present application, after connection with the N third slices is established for at least one fourth application in the first period through the modem, if no network congestion message reported by the network side is received, the operating system may start the timer again, so as to establish connection with the M fourth slices for at least one fifth application in the second period through the modem.

The second period of time is a period of time corresponding to a preset duration after the timer is started.

Specifically, the operating system may restart the timer, for example: 10 minutes, and suggesting a modem, the number of customer type slices to use over a second time period; the modem may determine the number of client type slices to use over the second time period in combination with the number of available client type slices indicated by the network side.

For example, the modem may select a smaller value among the number of client type slices recommended by the operating system to use and the number of available client type slices indicated by the network side as the number of use of client type slices within the second time period range.

For example: if the number of client type slices used is 2, and the number of available client type slices indicated by the network side is 3, the modem selects a smaller value (the number of client type slices used is suggested by the operating system) as the number of client type slices used in the second time period range, so that connection between at least one fifth application and 2 fourth slices is established through the modem in the second time period range.

It will be appreciated that since the network may not have as much resources as it is from a congested state to an uncongested state, a hierarchical adjustment may be made to avoid re-congestion of the network.

Optionally, in an embodiment of the present application, the function of the application listening service module in the operating system includes at least one of the following: detecting the starting condition of the application, detecting the foreground and background condition of the application, counting the use information of the application, counting the number of application slicing requests, sequencing the application slicing requests in a queue, judging the priority of the application, and sending the application requests to a slicing management service module.

Optionally, in an embodiment of the present application, the functions of the slice management service module in the operating system include at least one of the following: recording how many application requests sent by an application monitoring service module exist at present, recording the corresponding relation between the application and the slice for establishing connection, and controlling the number of the client type slices.

Optionally, in an embodiment of the present application, the functions of the modem include at least one of: the method comprises the steps of pairing with the slice, sending the slice request to the network, merging the slice, retrying the slice request with errors and receiving the message of network congestion.

It should be noted that, in the slice management method provided in the embodiment of the present application, the execution subject may be a slice management device. In the embodiment of the present application, a slice management device is described by taking an example of a slice management method performed by the slice management device.

Fig. 4 shows a schematic diagram of one possible configuration of a slice management apparatus according to an embodiment of the present application. As shown in fig. 4, the slice management apparatus 70 may include: a receiving module 71 and a processing module 72. And the receiving module is used for receiving the slice connection request of the first application. And the processing module is used for sending the slice connection request to the modem and establishing the slice connection of the first application through the modem under the condition that the network congestion state is not recorded.

The embodiment of the application provides a slice management device, which can judge the network condition when receiving a slice connection request of a first application, and send the slice connection request of the first application to a modem in a network uncongested state so as to establish the slice connection of the first application through the modem, thereby avoiding the situation of slice network congestion.

In one possible implementation, the processing module 72 is specifically configured to record a network congestion status in a case where the slice connection request is rejected by the modem; and under the condition that a network uncongested message reported by a network side is received, a slice connection request is issued to the modem, and slice connection of the first application is established through the modem.

In a possible implementation, the processing module 72 is further configured to interrupt sending the slice connection request in case of recording a network congestion status; and under the condition that a network uncongested message reported by a network side is received, a slice connection request is issued to the modem, and slice connection of the first application is established through the modem.

In a possible implementation manner, the processing module 72 is further configured to send a slice disconnection request to the modem to disconnect the slice connection of the first application if a network congestion message reported by the network side is received after the slice connection of the first application is established through the modem.

In one possible implementation, the first application is an application with high communication quality requirements, and the processing module 72 is specifically configured to establish a connection between the first application and a first slice through the modem, where the first slice is a client-type slice.

In a possible implementation manner, the receiving module 72 is further configured to receive a slice connection request of a second application after the connection between the first application and the first slice is established through the modem, where the second application is an application with a high communication quality requirement; and establishing connection of the second application with the first slice through the modem in case that the number of available client type slices indicated by the network side is smaller than or equal to the number of applications of the connected client type slices.

In a possible implementation manner, the processing module 72 is further configured to disconnect the second application from the first slice through the modem and establish a connection between the second application and the second slice, where the number of available client type slices indicated by the network side is greater than the number of applications of the connected client type slices, and the number of applications for which the second slice has established a connection is zero.

In a possible implementation manner, the receiving module 71 is further configured to receive a slice connection request of a third application after the connection between the first application and the first slice is established through the modem, where the third application is an application with a high communication quality requirement; if the number of applications for which the client type slice connection has been established is greater than a threshold number, interrupting sending the slice connection request.

In one possible implementation, the slice management apparatus 70 further includes: and a transmitting module. And the sending module is also used for sending at least one connection request of the fourth application to the modem in the first time period under the condition of receiving the message of converting the network congestion state into the network non-congestion state, wherein the message is reported by the network side. A processing module 72, further configured to establish, through the modem, a connection between at least one fourth application and the N third slices; the at least one fourth application is an application with high communication quality requirement for sending a slice connection request to the operating system in a first time period, the third slice is a client type slice, and N is a positive integer.

In a possible implementation manner, the processing module 72 is further configured to, after establishing, by using the modem, connection between the at least one fourth application and the N third slices, if no network congestion message reported by the network side is received within the first time period, establish, by using the modem, connection between the at least one fifth application and the M fourth slices within the second time period; the at least one fifth application includes a fourth application, and an application with high communication quality requirement for sending a slice connection request to the operating system in a second time period, wherein the fourth slice is a client type slice, and M is an integer greater than N.

The slice management device in the embodiment of the application may be an electronic device, or may be a component in the electronic device, for example, an integrated circuit or a chip. The electronic device may be a terminal, or may be other devices than a terminal. By way of example, the electronic device may be a mobile phone, tablet computer, notebook computer, palm computer, vehicle-mounted electronic device, mobile internet appliance (Mobile Internet Device, MID), augmented reality (augmented reality, AR)/Virtual Reality (VR) device, robot, wearable device, ultra-mobile personal computer, UMPC, netbook or personal digital assistant (personal digital assistant, PDA), etc., but may also be a server, network attached storage (Network Attached Storage, NAS), personal computer (personal computer, PC), television (TV), teller machine or self-service machine, etc., and the embodiments of the present application are not limited in particular.

The slice management apparatus in the embodiment of the present application may be an apparatus having an operating system. The operating system may be an Android operating system, an ios operating system, or other possible operating systems, which are not specifically limited in the embodiments of the present application.

The slice management device provided in the embodiment of the present application can implement each process implemented by the foregoing method embodiment, and in order to avoid repetition, details are not repeated here.

Optionally, as shown in fig. 5, the embodiment of the present application further provides an electronic device 900, including a processor 901 and a memory 902, where a program or an instruction capable of being executed on the processor 901 is stored in the memory 902, and the program or the instruction when executed by the processor 901 implements each step of the embodiment of the method, and the steps can achieve the same technical effect, so that repetition is avoided, and no further description is given here.

The electronic device in the embodiment of the application includes the mobile electronic device and the non-mobile electronic device described above.

Fig. 6 is a schematic hardware structure of an electronic device implementing an embodiment of the present application.

The electronic device 100 includes, but is not limited to: radio frequency unit 101, network module 102, audio output unit 103, input unit 104, sensor 105, display unit 106, user input unit 107, interface unit 108, memory 109, and processor 110.

Those skilled in the art will appreciate that the electronic device 100 may further include a power source (e.g., a battery) for powering the various components, and that the power source may be logically coupled to the processor 110 via a power management system to perform functions such as managing charging, discharging, and power consumption via the power management system. The electronic device structure shown in fig. 6 does not constitute a limitation of the electronic device, and the electronic device may include more or less components than shown, or may combine certain components, or may be arranged in different components, which are not described in detail herein.

The processor 110 is configured to receive a slice connection request of the first application, and send the slice connection request to the modem, and establish a slice connection of the first application through the modem, where a network congestion state is not recorded.

The embodiment of the application provides an electronic device, which can judge the network condition when receiving a slice connection request of a first application, and send the slice connection request of the first application to a modem in a network uncongested state so as to establish slice connection of the first application through the modem, so that the situation of slice network congestion is avoided.

Optionally, the processor 110 is specifically configured to record a network congestion status in a case where the slice connection request is rejected by the modem; and under the condition that a network uncongested message reported by a network side is received, a slice connection request is issued to the modem, and slice connection of the first application is established through the modem.

Optionally, the processor 110 is further configured to interrupt sending the slice connection request in case of recording a network congestion status; and under the condition that a network uncongested message reported by a network side is received, a slice connection request is issued to the modem, and slice connection of the first application is established through the modem.

Optionally, the processor 110 is further configured to send a slice disconnection request to the modem to disconnect the slice connection of the first application if a network congestion message reported by the network side is received after the slice connection of the first application is established through the modem.

Optionally, the first application is an application with high communication quality requirements, and the processor 110 is specifically configured to establish a connection between the first application and a first slice through the modem, where the first slice is a client type slice.

Optionally, the radio frequency unit 101 is configured to receive a slice connection request of a second application after the processor 110 establishes a connection between the first application and the first slice through the modem, where the second application is an application with a high communication quality requirement. The processor 110 is further configured to establish, by means of the modem, a connection of the second application to the first slice in case the number of available client type slices indicated at the network side is smaller than or equal to the number of applications of the connected client type slices.

Optionally, the processor 110 is further configured to disconnect the second application from the first slice through the modem and establish a connection between the second application and the second slice, and in a case where the number of available client type slices indicated by the network side is greater than the number of applications of the connected client type slices, the number of applications for which the second slice has established a connection is zero.

Optionally, the radio frequency unit 101 is further configured to receive a slice connection request of a third application after the processor 110 establishes a connection between the first application and the first slice through the modem, where the third application is an application with a high communication quality requirement; the processor 110 is further configured to interrupt sending the slice connection request if the number of applications for which the client type slice connection has been established is greater than a threshold number.

Optionally, the radio frequency unit 101 is further configured to send, in the first time period, a connection request of at least one fourth application to the modem when receiving a message reported by the network side and converted from a network congestion state to a network non-congestion state. The processor 110 is further configured to establish, through the modem, a connection between at least one fourth application and the N third slices; the at least one fourth application is an application with high communication quality requirement for sending a slice connection request to the operating system in a first time period, the third slice is a client type slice, and N is a positive integer.

Optionally, the processor 110 is further configured to, after establishing connection between the at least one fourth application and the N third slices through the modem, establish connection between the at least one fifth application and the M fourth slices through the modem in the second time period if no network congestion message reported by the network side is received in the first time period; the at least one fifth application includes a fourth application, and an application with high communication quality requirement for sending a slice connection request to the operating system in a second time period, wherein the fourth slice is a client type slice, and M is an integer greater than N.

The electronic device provided in the embodiment of the present application can implement each process implemented by the above method embodiment, and can achieve the same technical effects, so that repetition is avoided, and details are not repeated here.

The beneficial effects of the various implementation manners in this embodiment may be specifically referred to the beneficial effects of the corresponding implementation manners in the foregoing method embodiment, and in order to avoid repetition, the description is omitted here.

It should be appreciated that in embodiments of the present application, the input unit 104 may include a graphics processor (Graphics Processing Unit, GPU) 1041 and a microphone 1042, the graphics processor 1041 processing image data of still pictures or video obtained by an image capturing device (e.g., a camera) in a video capturing mode or an image capturing mode. The display unit 106 may include a display panel 1061, and the display panel 1061 may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like. The user input unit 107 includes at least one of a touch panel 1071 and other input devices 1072. The touch panel 1071 is also referred to as a touch screen. The touch panel 1071 may include two parts of a touch detection device and a touch controller. Other input devices 1072 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and so forth, which are not described in detail herein.

Memory 109 may be used to store software programs as well as various data. The memory 109 may mainly include a first memory area storing programs or instructions and a second memory area storing data, wherein the first memory area may store an operating system, application programs or instructions (such as a sound playing function, an image playing function, etc.) required for at least one function, and the like. Further, the memory 109 may include volatile memory or nonvolatile memory, or the memory 109 may include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM), static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (ddr SDRAM), enhanced SDRAM (Enhanced SDRAM), synchronous DRAM (SLDRAM), and Direct RAM (DRRAM). Memory 109 in embodiments of the present application includes, but is not limited to, these and any other suitable types of memory.

Processor 110 may include one or more processing units; optionally, the processor 110 integrates an application processor that primarily processes operations involving an operating system, user interface, application programs, etc., and a modem processor that primarily processes wireless communication signals, such as a baseband processor. It will be appreciated that the modem processor described above may not be integrated into the processor 110.

The embodiment of the present application further provides a readable storage medium, where a program or an instruction is stored, and when the program or the instruction is executed by a processor, the program or the instruction implement each process of the embodiment of the method, and the same technical effects can be achieved, so that repetition is avoided, and no further description is given here.

Wherein the processor is a processor in the electronic device described in the above embodiment. The readable storage medium includes computer readable storage medium such as computer readable memory ROM, random access memory RAM, magnetic or optical disk, etc.

The embodiment of the application further provides a chip, the chip includes a processor and a communication interface, the communication interface is coupled with the processor, and the processor is used for running a program or an instruction, implementing each process of the above method embodiment, and achieving the same technical effect, so as to avoid repetition, and not repeated here.

It should be understood that the chips referred to in the embodiments of the present application may also be referred to as system-on-chip chips, chip systems, or system-on-chip chips, etc.

The embodiments of the present application provide a computer program product, which is stored in a storage medium, and the program product is executed by at least one processor to implement the respective processes of the above method embodiments, and achieve the same technical effects, and are not repeated herein.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element. Furthermore, it should be noted that the scope of the methods and apparatus in the embodiments of the present application is not limited to performing the functions in the order shown or discussed, but may also include performing the functions in a substantially simultaneous manner or in an opposite order depending on the functions involved, e.g., the described methods may be performed in an order different from that described, and various steps may also be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solutions of the present application may be embodied essentially or in a part contributing to the prior art in the form of a computer software product stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk), comprising several instructions for causing a terminal (which may be a mobile phone, a computer, a server, or a network device, etc.) to perform the methods described in the embodiments of the present application.

The embodiments of the present application have been described above with reference to the accompanying drawings, but the present application is not limited to the above-described embodiments, which are merely illustrative and not restrictive, and many forms may be made by those of ordinary skill in the art without departing from the spirit of the present application and the scope of the claims, which are also within the protection of the present application.

Claims

1. A method of slice management, the method comprising:

the method comprises the steps that an operating system receives a slice connection request of a first application;

and under the condition that the operating system does not record the network congestion state, the operating system sends the slice connection request to a modem, and the slice connection of the first application is established through the modem.

2. The method of claim 1, wherein the establishing, by the modem, a slice connection for the first application comprises:

in the event that the slice connection request is denied by the modem, the operating system records a network congestion status;

and under the condition that a network uncongested message reported by a network side is received, the operating system issues the slice connection request to a modem, and establishes the slice connection of the first application through the modem.

3. The method according to claim 1, wherein the method further comprises:

under the condition that the operating system records the network congestion state, the operating system interrupts sending the slice connection request;

and under the condition that a network uncongested message reported by a network side is received, the operating system issues the slice connection request to the modem, and establishes the slice connection of the first application through the modem.

4. The method of claim 1, wherein after the establishing of the slice connection of the first application by the modem, the method further comprises:

and if the network congestion message reported by the network side is received, the operating system sends a slice disconnection request to the modem to disconnect the slice connection of the first application.

5. The method of claim 1, wherein the first application is an application requiring high communication quality, and wherein the establishing a slice connection of the first application through the modem comprises:

and establishing connection between the first application and a first slice through the modem, wherein the first slice is a client type slice.

6. The method of claim 5, wherein after the establishing the connection of the first application to the first slice by the modem, the method further comprises:

the operation system receives a slice connection request of a second application, wherein the second application is an application with high communication quality requirements;

and establishing connection between the second application and the first slice through the modem under the condition that the number of the available client type slices indicated by the network side is smaller than or equal to the number of the applications connected with the client type slices.

7. The method of claim 6, wherein the establishing, by the modem, the connection of the second application to the first slice further comprises:

and disconnecting the second application from the first slice through the modem and establishing the connection between the second application and the second slice, wherein the number of applications for which the second slice has established a connection is zero, under the condition that the number of available client type slices indicated by the network side is greater than the number of applications for which the client type slices have been connected.

8. The method of claim 5, wherein the establishing, by the modem, the connection of the first application to the first slice further comprises:

the method comprises the steps that an operating system receives a slice connection request of a third application, wherein the third application is an application with high communication quality requirements;

if the number of applications for which the client-type slice connection has been established is greater than a threshold number, the operating system interrupts sending the slice connection request.

9. The method according to claim 1, wherein the method further comprises:

under the condition that a message of converting a network congestion state into a network non-congestion state, which is reported by a network side, is received, in a first time period range, the operating system sends a connection request of at least one fourth application to a modem, and connection between the at least one fourth application and N third slices is established through the modem;

The at least one fourth application is an application with high communication quality requirement for sending a slice connection request to the operating system in the first time period, the third slice is a client type slice, and N is a positive integer.

10. The method of claim 9, wherein after the establishing, by the modem, the connection of the at least one fourth application to the N third slices, the method further comprises:

if the network congestion message reported by the network side is not received in the first time period, establishing connection between the at least one fifth application and M fourth slices through the modem in a second time period;

the at least one fifth application includes the fourth application and an application with high communication quality requirement for sending a slice connection request to the operating system in the second time period, wherein the fourth slice is a client type slice, and M is an integer greater than N.

11. A slice management apparatus, comprising: a receiving module and a processing module;

the receiving module is used for receiving a slice connection request of the first application;

And the processing module is used for sending the slice connection request to a modem and establishing slice connection of the first application through the modem under the condition that the operating system does not record the network congestion state.

12. An operating system comprising a processor and a memory storing a program or instructions executable on the processor, which when executed by the processor, implement the steps of the slice management method of any one of claims 1 to 10.

13. A readable storage medium, characterized in that the readable storage medium has stored thereon a program or instructions which, when executed by a processor, implement the steps of the slice management method according to any one of claims 1-10.