Slice management method and apparatus, operating system, and storage medium

Abstract

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

Description

Technical Field

[0001] The present application belongs to the field of communication technology, and specifically relates to a slice management method, device, operating system and storage medium. Background Art

[0002] With the development of electronic devices, network slicing technology is constantly evolving. For example, the enterprise type is a slice type for enterprise-level business applications. Enterprise-level applications may have multiple network slices, and currently supports up to five different enterprise-level applications. The latency type is used for services that require extremely low latency, such as millisecond-level response speeds, and is well suited for such requests. Currently, only one network slice of this type is supported. The bandwidth type is a slice type for high-bandwidth applications. Applications with extremely high bandwidth requirements can request this type of network slice. If multiple applications request slices at the same time, the slice network may experience congestion. Summary of the Invention

[0003] The purpose of the embodiments of the present application is to provide a slice management method, device, operating system and storage medium, which can solve the problem of slice network congestion when there are multiple applications making slice requests.

[0004] In a first aspect, an embodiment of the present application provides a slice management method, which includes: an operating system receives a slice connection request from a first application; when the operating system does not record the network congestion status, the operating system sends the slice connection request to a modem, and establishes a slice connection for the first application through the modem.

[0005] In the second aspect, an embodiment of the present application provides a slice management device, which includes: a receiving module and a processing module; the receiving module is used to receive a slice connection request from a first application; the processing module is used to send the slice connection request to the modem when the operating system does not record the network congestion status, and establish a slice connection for the first application through the modem.

[0006] In a third aspect, an embodiment of the present application provides an operating system comprising a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the programs or instructions are executed by the processor, the steps of the method described in the first aspect are implemented.

[0007] In a fourth aspect, an embodiment of the present application provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented.

[0008] In a fifth aspect, an embodiment of the present application provides a chip, which comprises a processor and a communication interface, the communication interface is coupled with the processor, and the processor is configured to run programs or instructions to implement the method in the first aspect.

[0009] In a sixth aspect, an embodiment of the present application provides a computer program product stored in a storage medium, which is executed by at least one processor to implement the method in the first aspect.

[0010] In the embodiment of the present application, the operating system receives a slice connection request of a first application, and sends the slice connection request to a modem and establishes a slice connection of the first application by the modem when the operating system does not record a network congestion state. In this scheme, when the operating system receives the slice connection request of the first application, the network condition can be determined, and the slice connection request of the first application is sent to the modem to establish the slice connection of the first application by the modem when the network is not congested, thereby avoiding the slice network congestion. BRIEF DESCRIPTION OF DRAWINGS

[0011] Figure 1 is one of flowcharts of a slice management method provided by an embodiment of the present application;

[0012] Figure 2 is another flowchart of a slice management method provided by an embodiment of the present application;

[0013] Figure 3 is a third flowchart of a slice management method provided by an embodiment of the present application;

[0014] Figure 4 is a structural schematic diagram of a slice management device provided by an embodiment of the present application;

[0015] Figure 5 is one of hardware structural schematic diagrams of an electronic device provided by an embodiment of the present application;

[0016] Figure 6 is another hardware structural schematic diagram of an electronic device provided by an embodiment of the present application. DETAILED DESCRIPTION

[0017] The 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. Obviously, the described embodiments are only some of the embodiments of the present application, but not all the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art belong to the scope of protection of the present application.

[0018] The terms "first," "second," and the like in the specification and claims of this application are used to distinguish similar objects, and are not used to describe a specific order or precedence. It should be understood that the terms used in this manner are interchangeable where appropriate, so that the embodiments of this application can be implemented in an order other than that illustrated or described herein, and that the objects distinguished by "first," "second," and the like are generally of the same type, and do not limit the number of objects; for example, the first object can be one or more. In addition, the term "and / or" in the specification and claims refers to at least one of the connected objects, and the character " / " generally indicates that the objects connected are in an "or" relationship.

[0019] The following describes in detail the slice management method provided in the embodiment of the present application through specific embodiments and their application scenarios in combination with the accompanying drawings.

[0020] With the development of electronic devices, network slicing technology is constantly evolving. For example, the enterprise type is a slice type for enterprise-level business applications. Enterprise applications may have multiple network slices, and currently supports up to five different enterprise applications. The latency type is used for services that require extremely low latency, such as millisecond-level response times, and is well suited for these requests. Currently, only one network slice of this type is supported. The bandwidth type is a slice type for high-bandwidth applications. Applications with extremely high bandwidth requirements can request this type of network slice. Some client applications, such as communication apps, music, and web games, do not have very stringent bandwidth and latency requirements. However, these applications are widely used and require high communication quality. These applications can establish connections with client-type slices. However, when multiple applications request slices simultaneously, congestion may occur in the slice network.

[0021] In an embodiment of the present application, an operating system receives a slice connection request from a first application; if the operating system does not record a network congestion status, the operating system sends the slice connection request to a modem, and establishes a slice connection for the first application through the modem. In this solution, since the operating system can determine the network status when receiving the slice connection request from the first application, and if the network is not congested, the operating system sends the slice connection request from the first application to the modem, so as to establish a slice connection for the first application through the modem, thereby avoiding the situation of slice network congestion.

[0022] The present invention provides a method for managing slices. Figure 1 FIG1 shows a flow chart of a slice management method provided by an embodiment of the present application, which can be applied to electronic devices. Figure 1As shown, the slice management method provided by the embodiments of the present application can include the following steps 201 to 203.

[0023] Step 201, the operating system receives a slice connection request of a first application.

[0024] Optionally, in the embodiments of the present application, the first application can be any one of the following: an enterprise application, a carrier application, a communication application, a game, music, a shopping application, etc.

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

[0026] Optionally, in the embodiments of the present application, when the network is congested, the network side can report a network congestion message to the modem, and then the modem can report the network congestion message to the operating system, and the slice management module of the operating system will record the current network congestion state.

[0027] Specifically, when the slice management module of the operating system does not record the network congestion state, the operating system can send the slice connection request to the modem, and the modem can match an appropriate slice for the first application, and request the slice from the network to establish the slice connection of the first application.

[0028] Optionally, in the embodiments of the present application, the slice connection request can include a target parameter, so that the modem establishes the slice connection of the first application based on the target parameter.

[0029] Exemplarily, the target parameter consists of slice type information required by the first application and an operating system identifier.

[0030] Exemplarily, after receiving the slice connection request of the first application, the operating system can determine the slice type required by the first application according to the application type of the first application, thereby obtaining the slice type information required by the first application.

[0031] Exemplarily, the target parameter can be represented by appid, which is determined by osid and osappid. According to different operating systems, osid can be an android os id or an ios id. osappid is the slice type information required by the first application.

[0032] Exemplarily, the enterprise type slice can be defined as NET_CAPABILITY_ENTERPRISE_1 to NET_CAPABILITY_ENTERPRISE_5; the cbs type slice can be defined as NET_CAPABILITY_CBS; the latency type slice can be defined as NET_CAPABILITY_Latency; the bandwidth type slice can be defined as NET_CAPABILITY_bandwidth; and the customer type slice (CCS) can be defined as NET_CAPABILITY_CUSTOMER_1 to NET_CAPABILITY_CUSTOMER_6.

[0033] It should be noted that some users use more widely used applications, such as communication applications, music, web games, etc. These client applications do not have very strict requirements on bandwidth and delay, but have higher requirements on communication quality. The client application corresponding to the slice required by the application with high communication quality requirement is defined as a customer type slice in the application. Similarly, the slice type corresponding to the customer application can be negotiated and specified by each operator, and the embodiments of the application are not limited.

[0034] Optionally, in the embodiments of the application, the application with high communication quality requirement is an application with communication quality requirement higher than a preset threshold, for example, an application with requirements on network stability and transmission information reliability higher than a preset threshold.

[0035] For example, when the first application is a communication application and the required slice is a customer type slice, the operating system can allocate NET_CAPABILITY_CUSTOMER_1 to the first application as the slice type information in the target parameter.

[0036] Optionally, in the embodiments of the application, after the modem receives the target parameter, the modem can select a matching slice for the first application according to a user route selection policy (URSP) issued by the network side, to establish a slice connection of the first application.

[0037] Exemplarily, the ursp includes an identifier of at least one available slice.

[0038] Specifically, after the modem receives the target parameter, the modem can select a matching slice for the first application from the at least one available slice based on the slice type information required by the first application, to establish a slice connection of the first application.

[0039] Exemplarily, among the at least one available slice, if the number of slices matching the first application is 1, a connection is established between the first application and the slice; if the number of slices matching the first application is greater than 1, a connection is established between the first application and any one of the matching slices.

[0040] Optionally, in an embodiment of the present application, the "operating system establishes a slice connection for the first application through a modem" in the above step 202 can be specifically implemented through the following steps 202a and 202b.

[0041] Step 202a: When the slice connection request is rejected by the modem, the operating system records the network congestion status.

[0042] Specifically, after the modem receives the slice connection request of the first application sent by the operating system, it can match the appropriate slice for the first application and request the slice from the network. At this time, if the network is congested, the network side will reject the slice connection request of the first application sent by the modem. Then the modem can reject the slice connection request of the first application sent by the operating system and report the network congestion message to the operating system, so that the operating system records the network congestion status.

[0043] For example, Figure 2 As shown, after the operating system receives the slice connection request from the first application (for example: App1), it sends the slice connection request 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, causing the modem to reject the slice connection request of App1 sent by the operating system and report the network congestion message to the operating system, causing the operating system to record the network congestion status.

[0044] Step 202b: Upon receiving the network non-congestion message reported by the network side, the operating system sends a slice connection request to the modem and establishes a slice connection for the first application through the modem.

[0045] It can be understood that when the network is not congested message is subsequently received from the network side, the operating system can send a slice connection request of the first application to the modem again to establish a slice connection of the first application through the modem.

[0046] An embodiment of the present application provides a slice management method, in which an operating system receives a slice connection request from a first application; if the operating system does not record a network congestion status, the operating system sends the slice connection request to a modem, and establishes a slice connection for the first application through the modem. In this solution, since the operating system can determine the network status when receiving the slice connection request from the first application, and if the network is not congested, the operating system sends the slice connection request from the first application to the modem, so as to establish a slice connection for the first application through the modem, thereby avoiding slice network congestion.

[0047] Optionally, in an embodiment of the present application, the slice management method provided in the embodiment of the present application may also include the following steps 301 and 302.

[0048] Step 301: When the operating system records the network congestion status, the operating system interrupts sending the slice connection request.

[0049] It can be understood that when the network congestion message has been reported on the network side and the operating system records the network congestion status, if the operating system receives a slice connection request from the first application, the operating system stops sending the slice connection request to the modem, that is, interrupts sending the slice connection request.

[0050] Step 302: Upon receiving the network non-congestion message reported by the network side, the operating system sends a slice connection request to the modem and establishes a slice connection for the first application through the modem.

[0051] It can be understood that when the network is not congested message is subsequently received from the network side, the operating system can send a slice connection request of the first application to the modem to establish a slice connection of the first application through the modem.

[0052] Optionally, in an embodiment of the present application, after the above step 202, the slice management method provided in the embodiment of the present application also includes the following step 401.

[0053] Step 401: If a network congestion message reported by the network side is received, the operating system sends a slice disconnect request to the modem to disconnect the slice connection of the first application.

[0054] Specifically, when establishing a slice connection for the first application, if the operating system receives a network congestion message reported by the network side through the modem, the operating system can send a slice disconnect request to the modem to disconnect the slice connection for the first application.

[0055] It is understandable that due to network congestion, the slice is no longer available, so the operating system can send a slice disconnect request to the modem to disconnect the slice connection of the first application.

[0056] Optionally, in an embodiment of the present application, the first application is an application with high communication quality requirements, and the "operating system establishes a slice connection for the first application through a modem" in the above step 202 can be specifically implemented through the following step 202b.

[0057] Step 202b: The operating system establishes a connection between the first application and the first slice through the modem.

[0058] In the embodiment of the present application, the first slice is a customer type slice.

[0059] Optionally, in an embodiment of the present application, the above-mentioned application with high communication quality requirements may be any one of the following: communication applications, games, music, shopping applications, etc.

[0060] Optionally, in an embodiment of the present application, when the first application is an application with high communication quality requirements and the operating system receives a slice connection request from 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 can select a first slice that matches the slice type required by the first application from at least one available slice based on the target parameter to establish a connection between the first application and the first slice.

[0061] Optionally, in an embodiment of the present application, after the above-mentioned step 202b, the slice management method provided in the embodiment of the present application also includes the following steps 501 and 502.

[0062] Step 501: The operating system receives a slice connection request from a second application.

[0063] In the embodiment of the present application, the second application is an application with high communication quality requirements.

[0064] Step 502: When the number of available client type slices indicated by the network side is less than or equal to the number of applications of connected client type slices, the operating system establishes a connection between the second application and the first slice through the modem.

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

[0066] It can be understood that since the number of applications connected to the customer type slices is greater than or equal to the number of available customer type slices, it means that the slice resources are tight. Therefore, the operating system can merge the slices 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.

[0067] For example: the first application (for example: App1) is connected to the first slice (for example: slice 1). When the number of available customer type slices indicated on the network side is 2 and the number of applications connected to customer type slices is 4, the operating system establishes a connection between the second application (for example: App2) and the first slice (for example: slice 1) through the modem.

[0068] Specifically, after establishing a connection between the first application and the first slice, a network card can be established and named name1; when the operating system receives the slice connection request of the second application and sends the slice connection request to the modem, the modem can know that the second application is also requesting a customer type slice through the slice type information required by the second application in the target parameter carried by the request (for example: the slice type information is NET_CAPABILITY_CUSTOMER_2), so that the second application can be directly paired with the first slice without sending it to the network side, and it is also paired with the network card name1; the network card will register and set the route in the operating system, and the data flow of the first application and the second application will flow from name1 to the modem, and finally be sent to the network side through the first slice in the protocol stack.

[0069] Optionally, in an embodiment of the present application, the operating system may set the number of applications using customer type slices to not exceed a first preset number, for example: 6.

[0070] For example, the application monitoring service module in the operating system can manage the requests of the client application, and the number of requests sent by the application monitoring service module to the slice management service module in the operating system will not exceed 6.

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

[0072] Furthermore, if after establishing a connection between the second application and the first slice through the modem, the operating system receives a slice connection request from an application with high communication quality requirements, the operating system can establish a connection between the application and another client type slice through the modem, and the other client type slice is different from the first slice.

[0073] Exemplarily, when the modem establishes a connection between the certain application and another customer type slice, if network resources change and the other customer type slice is unavailable, a connection between the certain application and the first slice is established.

[0074] It can be understood that since the number of applications using customer type slices is set to no more than 6, and the network side indicates that the number of available customer type slices is 3, every two applications with high communication quality requirements can be merged with the same customer type slice to establish a connection.

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

[0076] Furthermore, if after the connection between the second application and the first slice is established through the modem, the operating system receives a slice connection request from an application with high communication quality requirements, the operating system can still establish a connection between the application and the first slice through the modem.

[0077] It can be understood that since the number of applications using customer type slices is set to no more than 6, and the network side indicates that the number of available customer type slices is 2, every three applications with high communication quality requirements can be merged with the same customer type slice to establish a connection.

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

[0079] It can be understood that since the number of applications using customer type slices is set to no more than 6, and the network side indicates that the number of available customer type slices is 1, applications with high communication quality requirements are merged with the same customer type slice to establish a connection.

[0080] In this way, network slice resources can be fully utilized, network congestion can be avoided as much as possible, and at the same time, each application that establishes a connection with the customer type slice can ensure good slice communication quality.

[0081] Optionally, in an embodiment of the present application, after the above step 502, the slice management method provided in the embodiment of the present application also includes the following step 601.

[0082] In a case where the number of available customer type slices indicated at the network side is greater than the number of applications of connected customer type slices, the operating system disconnects the connection of the second application with the first slice through the modem and establishes the connection of the second application with the second slice.

[0083] In the embodiment of the application, the number of applications of the second slice with which the connection is established is zero.

[0084] It can be understood that after the operating system establishes the connection of the first application with the first slice and the connection of the second application with the first slice through the modem, if the number of applications of connected customer type slices is less than the number of available customer type slices, that is, the number of available customer type slices is sufficient, the operating system can cancel the slice merging, that is, disconnect the connection of the second application with the first slice through the modem and establish the connection of the second application with the second slice.

[0085] In this way, the flexibility of the application in establishing the slice connection is improved.

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

[0087] Step 701: The operating system receives a slice connection request of a third application.

[0088] In the embodiment of the application, the third application is an application with a high communication quality requirement.

[0089] It can be understood that the third application is an application requesting a customer type slice.

[0090] Step 702: If the number of applications with which the customer type slice connection is established is greater than a threshold number, the operating system interrupts the sending of the slice connection request.

[0091] Optionally, in the embodiment of the application, the operating system can set the priority of the application requesting a low-delay type slice, a high-bandwidth type slice, an enterprise type slice, an operator type slice, etc. as a high priority, and set the priority of the application requesting a customer type slice as a low priority.

[0092] Optionally, in the embodiment of the application, when the operating system receives the slice connection request of the third application, that is, the slice connection request of the application with a low priority, the operating system can determine whether the number of applications with which the customer type slice connection is established is greater than a threshold number, and if the number of applications is greater than the threshold number, the operating system interrupts the sending of the slice connection request.

[0093] In this way, since the operating system can control the number of applications with which the customer type slice connection is established, network congestion can be avoided.

[0094] Exemplarily, when the number of applications that have established client type slice connections is greater than a threshold number, the operating system can release the client type slice used by the target application, and then send a slice connection request to the modem to establish a slice connection for a third application through the modem.

[0095] It can be understood that since the operating system can release the client type slice used by the target application when the number of applications that have established client type slice connections is greater than the threshold number, so that the number of applications that have established client type slice connections is less than or equal to the threshold number, the operating system can send a slice connection request for the third application to the modem to establish a slice connection for the third application through the modem.

[0096] Exemplarily, the above-mentioned target application is an application that has established a customer type slice connection. The target application can be any of the following: an application whose usage information is less than a preset threshold in the background running application, an application that switches from an on state to an off state, and an application that has not used the network within a preset time period in the background running application.

[0097] Exemplarily, the above usage information may include at least one of the following: usage frequency, usage duration, number of times of use, etc.

[0098] In the embodiment of this application, Figure 3 As shown, the slice management method provided in the embodiment of the present application may include the following steps S1 to S5.

[0099] Step S1: If the number of applications that have established client-type slice connections exceeds a threshold, the operating system determines whether any of the applications that have established client-type slice connections have released a slice. If so, proceed to step S2; if not, proceed to step S3.

[0100] Step S2: The operating system releases the client type slice used by the application.

[0101] Step S3: The operating system determines whether any application among the applications that have established a client-type slice connection has been closed. If so, execute step S2; if not, execute step S4.

[0102] Step S4: The operating system determines whether any of the applications for which the client-type slice connection has been established are running in the background and have not used the network for a preset period of time. If so, the operating system proceeds to step S2; if not, the operating system proceeds to step S5.

[0103] Step S5: The operating system determines whether any application among the applications for which the client type slice connection has been established is running in the background and the usage information is less than a preset threshold. If so, the operating system proceeds to step S2.

[0104] In this way, unnecessary slice resources can be released in a timely manner, avoiding waste of slice resources and network congestion.

[0105] Optionally, in an embodiment of the present application, after the operating system establishes a connection between the first application and the first slice, and a connection between the second application and the first slice through the modem, if it receives a slice connection request from a high-priority application, the operating system does not perform any restrictive processing.

[0106] Optionally, in an embodiment of the present application, the slice management method provided in the embodiment of the present application may also include the following step 801.

[0107] Step 801: Upon receiving a message from the network side indicating that the network is in a congested state and is not in a congested state, the operating system sends a connection request for at least one fourth application to the modem within a first time period, and establishes a connection between at least one fourth application and N third slices through the modem.

[0108] Among them, at least one fourth application is an application with high communication quality requirements that sends a slice connection request to the operating system within the first time period, the third slice is a customer type slice, and N is a positive integer.

[0109] Optionally, in an embodiment of the present application, upon receiving a message reported by the network side indicating that the network has changed from a congested state to an uncongested state, the operating system may start a timer to establish a connection with N third slices for at least one fourth application within the first time period through a modem.

[0110] Exemplarily, the first time period is a time period corresponding to a preset duration after the timer is started.

[0111] Specifically, the operating system can start a timer, for example: 10 minutes, and recommend to the modem the number of customer type slices to be used within the first time period; the modem can determine the number of customer type slices to be used within the first time period in combination with the number of available customer type slices indicated by the network side.

[0112] It should be noted that the number of customer type slices used is the value of N. For example, if the number of customer type slices used is 2 and the number of fourth applications is 3, a combined connection of 3 fourth applications and 2 third slices is established through the modem.

[0113] Exemplarily, the modem may select a smaller value between the number of client type slices recommended by the operating system and the number of available client type slices indicated by the network side as the number of client type slices used within the first time period.

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

[0115] In this way, the problem of the network becoming congested again if multiple fourth applications are connected to more third slices through a modem after the network changes from a congested state to an uncongested state is avoided.

[0116] Optionally, in an embodiment of the present application, after the above-mentioned step 801, the slice management method provided in the embodiment of the present application also includes the following step 901.

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

[0118] Among them, at least one fifth application includes a fourth application, an application with high communication quality requirements that sends a slice connection request to the operating system within the second time period, the fourth slice is a customer type slice, and M is an integer greater than N.

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

[0120] Exemplarily, the second time period is a time period corresponding to a preset duration after the timer is started.

[0121] Specifically, the operating system can start the timer again, for example: 10 minutes, and recommend the modem the number of customer type slices to be used within the second time period; the modem can determine the number of customer type slices to be used within the second time period in combination with the number of available customer type slices indicated by the network side.

[0122] Exemplarily, the modem may select a smaller value between the number of client type slices recommended by the operating system and the number of available client type slices indicated by the network side as the number of client type slices used within the second time period.

[0123] For example: if the operating system recommends using 2 customer type slices, and the number of available customer type slices indicated by the network side is 3, the modem selects a smaller value (the number of customer type slices recommended by the operating system) as the number of customer type slices used within the second time period, so as to establish a connection between at least one fifth application and two fourth slices through the modem within the second time period.

[0124] It is understandable that since the network may have limited resources when it changes from a congested state to an uncongested state, hierarchical adjustments can be made to avoid network congestion again.

[0125] Optionally, in an embodiment of the present application, the functions of the application monitoring service module in the operating system include at least one of the following: detecting the startup status of the application, detecting the foreground and background status of the application, counting the usage information of the application, counting the number of application slice requests, and sorting by queue, judging the application priority, and sending the application request to the slice management service module.

[0126] 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 are currently sent by the application monitoring service module, recording the correspondence between the application and the slices for establishing the connection, and controlling the number of customer type slices used.

[0127] Optionally, in an embodiment of the present application, the functions of the modem include at least one of the following: pairing the application with the slice, sending a slice request to the network side, merging slices, retrying the slice request if an error occurs, and receiving messages about network congestion.

[0128] It should be noted that the slice management method provided in the embodiment of the present application can be executed by a slice management device. In the embodiment of the present application, the slice management device executing the slice management method is taken as an example to illustrate the slice management device provided in the embodiment of the present application.

[0129] Figure 4 A possible structural diagram of the slice management device involved in the embodiment of the present application is shown. Figure 4 As shown, the slice management device 70 may include: a receiving module 71 and a processing module 72. The receiving module is configured to receive a slice connection request from a first application. The processing module is configured to send the slice connection request to a modem without recording a network congestion status, and establish a slice connection for the first application through the modem.

[0130] An embodiment of the present application provides a slice management device. When the slice management device receives a slice connection request from a first application, it can judge the network situation. When the network is not congested, the slice connection request of the first application is sent to the modem to establish a slice connection for the first application through the modem, thereby avoiding slice network congestion.

[0131] In one possible implementation, the processing module 72 is specifically used to record the network congestion status when the slice connection request is rejected by the modem; and when receiving the network non-congestion message reported by the network side, send the slice connection request to the modem, and establish a slice connection for the first application through the modem.

[0132] In one possible implementation, the processing module 72 is also used to interrupt sending the slice connection request when the network congestion status is recorded; and when receiving the network non-congestion message reported by the network side, send the slice connection request to the modem, and establish a slice connection for the first application through the modem.

[0133] In one possible implementation, the processing module 72 is also used to, after establishing a slice connection for the first application through the modem, send a slice disconnect request to the modem to disconnect the slice connection for the first application if a network congestion message reported by the network side is received.

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

[0135] In one possible implementation, the receiving module 72 is further used to receive a slice connection request from a second application after establishing a connection between the first application and the first slice through a modem, where the second application is an application with high communication quality requirements; and to establish a connection between the second application and the first slice through a modem when the number of available customer type slices indicated on the network side is less than or equal to the number of applications with connected customer type slices.

[0136] In one possible implementation, the processing module 72 is further used to disconnect the second application from the first slice through the modem after establishing a connection between the second application and the first slice through the modem, and establish a connection between the second application and the second slice through the modem, if the number of available customer type slices indicated by the network side is greater than the number of applications of the connected customer type slices, and the number of applications connected to the second slice is zero.

[0137] In a possible implementation, the receiving module 71 is further configured to, after the first application establishes the connection with the first slice through the modem, receive a slice connection request of a third application, the third application being an application with high communication quality requirement; and if the number of applications that have established the client type slice connection is greater than a threshold number, interrupt sending the slice connection request.

[0138] In a possible implementation, the slice management apparatus 70 further includes a sending module. The sending module is further configured to, in a case where a message indicating that the network congestion state is changed to the network non-congestion state is received from the network side, send a connection request of at least one fourth application to the modem within a first time period. The processing module 72 is further configured to establish a connection between the at least one fourth application and N third slices through the modem, the at least one fourth application being an application with high communication quality requirement that sends a slice connection request to the operating system within the first time period, the third slice being a client type slice, and N being a positive integer.

[0139] In a possible implementation, the processing module 72 is further configured to, after the at least one fourth application establishes the connection with the N third slices through the modem, if no network congestion message is received from the network side within the first time period, establish a connection between at least one fifth application and M fourth slices through the modem within a second time period, the at least one fifth application including the fourth application and an application with high communication quality requirement that sends a slice connection request to the operating system within the second time period, the fourth slice being a client type slice, and M being an integer greater than N.

[0140] The slice management apparatus in the embodiments of the present application can be an electronic device or a component in an electronic device, for example, an integrated circuit or a chip. The electronic device can be a terminal or other devices other than a terminal. For example, the electronic device can be a mobile phone, a tablet computer, a notebook computer, a palm computer, a vehicle-mounted electronic device, a Mobile Internet Device (MID), an augmented reality (AR) / virtual reality (VR) device, a robot, a wearable device, an ultra-mobile personal computer (UMPC), a netbook, or a personal digital assistant (PDA), etc. The electronic device can also be a server, a Network Attached Storage (NAS), a personal computer (PC), a television (TV), a teller machine, or a self-service machine, etc. The embodiments of the present application are not limited in this regard.

[0141] The slice management device in the embodiment of the present application can be a device having an operating system. The operating system can be an Android operating system, an iOS operating system, or other possible operating systems, which are not specifically limited in the embodiment of the present application.

[0142] The slice management device provided in the embodiment of the present application can implement each process implemented in the above method embodiment. To avoid repetition, it will not be repeated here.

[0143] Alternatively, as Figure 5 As shown, an embodiment of the present application also provides an electronic device 900, including a processor 901 and a memory 902, wherein the memory 902 stores a program or instruction that can be run on the processor 901, and when the program or instruction is executed by the processor 901, the various steps of the above-mentioned method embodiment are implemented and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0144] It should be noted that the electronic devices in the embodiments of the present application include the mobile electronic devices and non-mobile electronic devices mentioned above.

[0145] Figure 6 A schematic diagram of the hardware structure of an electronic device implementing an embodiment of the present application.

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

[0147] Those skilled in the art will understand that the electronic device 100 may also include a power source (such as a battery) to power each component, and the power source may be logically connected to the processor 110 through a power management system, thereby implementing functions such as charging, discharging, and power consumption management through the power management system. Figure 6 The electronic device structure shown in the figure does not constitute a limitation on the electronic device. The electronic device may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently, which will not be repeated here.

[0148] Among them, the processor 110 is used to receive a slice connection request from the first application, and send the slice connection request to the modem without recording the network congestion status, and establish a slice connection for the first application through the modem.

[0149] The embodiment of the application provides an electronic device, because the electronic device can judge a network condition when receiving a slice connection request of a first application, and sends the slice connection request of the first application to a modem in a non-congestion state of the network, so that the slice connection of the first application is established through the modem, and therefore, the situation of slice network congestion is avoided.

[0150] Optionally, the processor 110 is specifically configured to record a network congestion state in the case that the slice connection request is rejected by the modem; and in the case that a network non-congestion message reported by the network side is received, the processor 110 is configured to send the slice connection request to the modem, and establish the slice connection of the first application through the modem.

[0151] Optionally, the processor 110 is further configured to interrupt sending the slice connection request in the case that the network congestion state is recorded; and in the case that the network non-congestion message reported by the network side is received, the processor 110 is configured to send the slice connection request to the modem, and establish the slice connection of the first application through the modem.

[0152] 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 the network congestion message reported by the network side is received after the slice connection of the first application is established through the modem.

[0153] Optionally, the first application is an application with high communication quality requirement, and the processor 110 is specifically configured to establish the connection of the first application and a first slice through the modem, and the first slice is a customer type slice.

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

[0155] Optionally, the processor 110 is further configured to disconnect the connection of the second application and the first slice through the modem and establish the connection of the second application and a second slice in the case that the number of available customer type slices indicated by the network side is greater than the number of connected customer type slice applications after the processor 110 establishes the connection of the second application and the first slice through the modem, and the number of connected applications of the second slice is zero.

[0156] Optionally, the radio frequency unit 101 is also used to receive a slice connection request from 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 high communication quality requirements; the processor 110 is also used to interrupt sending the slice connection request if the number of applications for which customer type slice connections have been established is greater than a threshold number.

[0157] Optionally, the radio frequency unit 101 is further configured to, upon receiving a message reported by the network side indicating a transition from a congested state to an uncongested state, send a connection request for at least one fourth application to the modem within a first time period. The processor 110 is further configured to establish, via the modem, a connection between the at least one fourth application and N third slices; wherein the at least one fourth application is an application requiring high communication quality that sends a slice connection request to the operating system within the first time period, the third slice is a client-type slice, and N is a positive integer.

[0158] Optionally, the processor 110 is further used to establish a connection between at least one fourth application and N third slices through a modem, and then, if no network congestion message reported by the network side is received within a first time period, establish a connection between at least one fifth application and M fourth slices through a modem within a second time period; wherein, the at least one fifth application includes a fourth application, an application with high communication quality requirements that sends a slice connection request to the operating system within the second time period, the fourth slice is a client type slice, and M is an integer greater than N.

[0159] The electronic device provided in the embodiment of the present application can implement each process implemented in the above method embodiment and can achieve the same technical effect. To avoid repetition, it will not be described here.

[0160] The beneficial effects of various implementations in this embodiment can be specifically referred to the beneficial effects of the corresponding implementations in the above method embodiment. To avoid repetition, they will not be described here.

[0161] It should be understood that in an embodiment of the present application, the input unit 104 may include a graphics processing unit (GPU) 1041 and a microphone 1042, and the graphics processor 1041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture 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, etc. The user input unit 107 includes a touch panel 1071 and at least one of other input devices 1072. The touch panel 1071 is also called a touch screen. The touch panel 1071 may include two parts: a touch detection device and a touch controller. Other input devices 1072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and an operating stick, which will not be repeated here.

[0162] The memory 109 can be used to store software programs and various data. The memory 109 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, applications or instructions required for at least one function (such as a sound playback function, an image playback function, etc.). In addition, the memory 109 may include a volatile memory or a non-volatile memory, or the memory 109 may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate synchronous dynamic random access memory (DDRSDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synchronous link dynamic random access memory (SLDRAM), and a direct memory bus random access memory (DRRAM). The memory 109 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0163] Processor 110 may include one or more processing units. Optionally, processor 110 integrates an application processor and a modem processor. The application processor primarily handles operations related to the operating system, user interface, and application programs, while the modem processor primarily processes wireless communication signals, such as a baseband processor. It is understood that the modem processor may not be integrated into processor 110.

[0164] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the above-mentioned method embodiment are implemented and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0165] The processor is the processor in the electronic device described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0166] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned method embodiment and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0167] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0168] An embodiment of the present application provides a computer program product, which is stored in a storage medium. The program product is executed by at least one processor to implement the various processes of the above-mentioned method embodiment and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0169] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the statement "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, it should be noted that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in the opposite order according to the functions involved. For example, the described method may be performed in an order different from that described, and various steps may also be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0170] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus the necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art can be embodied in the form of a computer software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), including a number of instructions for enabling a terminal (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods described in each embodiment of the present application.

[0171] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms without departing from the purpose of this application and the scope of protection of the claims, all of which are within the protection of this application.

Claims

1. A slice management method, characterized in that: The method comprises: The operating system receives a slice connection request from the first application; When the operating system does not record the network congestion status, the operating system sends the slice connection request to the modem, and establishes a slice connection for the first application through the modem; Upon receiving a message reported by the network side indicating that the network is in a non-congested state, the operating system sends a connection request for at least one fourth application to the modem within a first time period, and establishes a connection between the at least one fourth application and the N third slices through the modem; Among them, the at least one fourth application is an application with high communication quality requirements that sends a slice connection request to the operating system within the first time period, the third slice is a customer type slice, and N is a positive integer.

2. The method according to claim 1, characterized in that The establishing a slice connection for the first application through the modem includes: In a case where the slice connection request is rejected by the modem, the operating system records a network congestion status; Upon receiving the network non-congestion message reported by the network side, the operating system sends the slice connection request to the modem and establishes a slice connection for the first application through the modem.

3. The method according to claim 1, characterized in that The method further comprises: When the operating system records a network congestion state, the operating system interrupts sending the slice connection request; Upon receiving the network non-congestion message reported by the network side, the operating system sends the slice connection request to the modem and establishes a slice connection for the first application through the modem.

4. The method according to claim 1, wherein After establishing the slice connection of the first application through the modem, the method further includes: If a network congestion message reported by the network side is received, the operating system sends a slice disconnect request to the modem to disconnect the slice connection of the first application.

5. The method according to claim 1, wherein The first application is an application requiring high communication quality, and establishing a slice connection for the first application through the modem includes: A connection is established between the first application and a first slice through the modem, where the first slice is a client type slice.

6. The method according to claim 5, characterized in that After establishing the connection between the first application and the first slice through the modem, the method further includes: The operating system receives a slice connection request from a second application, where the second application is an application with high communication quality requirements; In a case where the number of available customer type slices indicated by the network side is less than or equal to the number of applications of connected customer type slices, a connection is established between the second application and the first slice through the modem.

7. The method according to claim 6, characterized in that After establishing the connection between the second application and the first slice through the modem, the method further includes: In a case where the number of available customer type slices indicated by the network side is greater than the number of applications of the connected customer type slices, the connection between the second application and the first slice is disconnected through the modem, and a connection between the second application and the second slice is established, and the number of applications connected to the second slice is zero.

8. The method according to claim 5, characterized in that After establishing the connection between the first application and the first slice through the modem, the method further includes: The operating system receives a slice connection request from a third application, where the third application is an application with high communication quality requirements; If the number of applications that have established client-type slice connections is greater than a threshold number, the operating system interrupts sending the slice connection request.

9. The method according to claim 1, characterized in that After establishing, by the modem, a connection between the at least one fourth application and the N third slices, the method further includes: If no network congestion message reported by the network side is received within the first time period, establishing a connection between the at least one fifth application and the M fourth slices through the modem within a second time period; Among them, the at least one fifth application includes the fourth application and an application with high communication quality requirements that sends a slice connection request to the operating system within the second time period, the fourth slice is a customer type slice, and M is an integer greater than N.

10. A slice management device, characterized in that: Executed by an operating system, the slice management device includes: a receiving module and a processing module; The receiving module is configured to receive a slice connection request from a first application; The processing module is configured to, when the operating system does not record the network congestion status, send the slice connection request to the modem, and establish a slice connection for the first application through the modem; The slice management device further includes: a sending module; The sending module is configured to send a connection request of at least one fourth application to the modem within a first time period when receiving a message reported by the network side indicating that the network is changed from a congested state to a non-congested state; The processing module is further configured to establish, through the modem, a connection between the at least one fourth application and the N third slices; Among them, the at least one fourth application is an application with high communication quality requirements that sends a slice connection request to the operating system within the first time period, the third slice is a customer type slice, and N is a positive integer.

11. An operating system, characterized in that: It includes a processor and a memory, the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the slice management method as described in any one of claims 1 to 9 are implemented.

12. A readable storage medium, characterized in that: The readable storage medium stores programs or instructions, which, when executed by the processor, implement the steps of the slice management method as described in any one of claims 1 to 9.

Images