CN113225761A

CN113225761A - Method for selecting network slice and electronic equipment

Info

Publication number: CN113225761A
Application number: CN202010069818.4A
Authority: CN
Inventors: 于晓靓; 刘彬俊; 樊宇伟; 连海; 李勇
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2020-01-21
Filing date: 2020-01-21
Publication date: 2021-08-06
Also published as: WO2021147665A1

Abstract

The embodiment of the application provides a method for selecting a network slice and electronic equipment. The method is applied to an electronic device, the electronic device comprises at least one application, and the method comprises the following steps: determining parameter information according to the at least one application, the parameter information being indicative of a network slice; performing a routing strategy according to the parameter information, wherein the routing strategy is used for selecting the network slice; binding routes to the network slice. According to the embodiment of the application, the implementation scheme of the specific network slice in the electronic equipment is provided, and various scenes of the network slice can be covered. The electronic device may obtain the parameter information by monitoring a service of at least one application or actively reporting by at least one application, may select a corresponding network slice for a service performed in at least one application according to the parameter information, and perform route binding.

Description

Method for selecting network slice and electronic equipment

Technical Field

The present application relates to the field of wireless communications, and in particular, to a method for selecting a network slice and an electronic device.

Background

With the advent of the 5G era, the definition of network slice (LINP) has been newly added. In the 5G system specified by the 3rd generation partnership project (3 GPP), the flexibility of the network architecture and service adaptability are emphasized, unlike previous systems that attempt to provide the same bearer capability for all services, 5G systems expect the ability to provide different customized optimizations for different services at the same time. LINP becomes a key concept to achieve this goal. A network slice means that in a physical network, related service functions and network resources are organized together to form a complete, autonomous, independent operation and maintenance logical network for satisfying specific users and services.

Disclosure of Invention

The application provides a method for selecting a network slice and electronic equipment. The electronic device obtains parameter information through at least one application, and selects a network slice through the parameter information, so that the route is bound to the network slice.

In a first aspect, a method for selecting a network slice is provided, and is applied to an electronic device, where the electronic device includes at least one application, and the method includes: determining parameter information according to the at least one application, the parameter information being indicative of a network slice; performing the routing strategy according to the parameter information, wherein the routing strategy is used for selecting the network slice; binding the route of the electronic device to the network slice.

According to the embodiment of the application, the implementation scheme of the specific network slice in the electronic equipment is provided, and various scenes of the network slice can be covered. The electronic device may obtain the parameter information by monitoring a service of at least one application or actively reporting by at least one application, may select a corresponding network slice for a service performed in at least one application according to the parameter information, and perform route binding.

It should be understood that each network slice is a protocol data unit session.

With reference to the first aspect, in certain implementations of the first aspect, the parameter information includes at least one of an application identification, a data network name, an internet protocol, IP, triplet, or a domain name.

According to the embodiment of the application, the electronic device can select the corresponding network slice for the service performed in at least one application according to at least one of the application identifier, the data network name, the Internet Protocol (IP) triple or the domain name, and perform the routing binding.

With reference to the first aspect, in certain implementations of the first aspect, the determining parameter information according to the at least one application includes: and monitoring the at least one application and determining the parameter information.

According to the embodiment of the application, the electronic equipment can acquire the parameter information by monitoring data interaction of at least one application with other layers or interfaces through the application layer.

With reference to the first aspect, in certain implementations of the first aspect, the monitoring the at least one application and determining the parameter information includes: determining an application identifier or a data network name by the at least one application entering a foreground or calling a request network interface; or, the kernel layer acquires the IP triple of the at least one application; or, obtaining the domain name of the at least one application by a network daemon.

According to the embodiment of the application, the electronic device can acquire the application identifier or the data network name through an application entering a foreground in at least one application or a call request network interface. It should be understood that the application entering the foreground of the at least one application may refer to the application being used by the user. The electronic device can perform data interaction with the kernel layer through at least one application to obtain the IP triple. The domain name may be obtained by data interaction with a network daemon by at least one application. The application to the foreground may refer to an application being used by a user, or an application needing to acquire data being run in the background.

With reference to the first aspect, in certain implementations of the first aspect, the determining parameter information according to the at least one application includes: and the at least one application reports the parameter information.

According to the embodiment of the application, when the service is changed in at least one application, the at least one application can actively report the parameter information, and the parameter information can correspond to the network slice required by the changed service.

With reference to the first aspect, in certain implementations of the first aspect, when the network slice is single-pass after the binding is routed to the network slice, the method further includes: binding the route to a network slice of a next priority of the network slice.

According to the embodiment of the application, after the route is bound to the network slice, the network slice only provides single-pass data connection, namely, data transmission between the network equipment and the electronic equipment is uploading or downloading. And after the electronic equipment determines that the data connection is abnormal, the self-healing process can be started.

With reference to the first aspect, in some implementations of the first aspect, the route is bound to a default network slice if there is no network slice of the next priority.

According to the embodiment of the application, when the network slices which can be selected according to the parameter information are all single-pass, the route can be bound to the default network slice, and data communication is achieved.

In a second aspect, an electronic device is provided, the electronic device comprising: at least one application; a processing unit configured to determine parameter information according to the at least one application, the parameter information indicating a network slice; the processing unit is further configured to perform the routing policy according to the parameter information, where the routing policy is used to select the network slice; the processing unit is further configured to bind routes to the network slice.

With reference to the second aspect, in certain implementations of the second aspect, the parameter information includes at least one of an application identification, a data network name, an internet protocol, IP, triplet, or a domain name.

With reference to the second aspect, in certain implementations of the second aspect, the determining parameter information according to the at least one application includes: and monitoring the at least one application and determining the parameter information.

With reference to the second aspect, in some implementations of the second aspect, the monitoring the at least one application and determining the parameter information includes: determining an application identifier or a data network name by the at least one application entering a foreground or calling a request network interface; or, the kernel layer acquires the IP triple of the at least one application; or, obtaining the domain name of the at least one application by a network daemon.

With reference to the second aspect, in certain implementations of the second aspect, the determining parameter information according to the at least one application includes: the processing unit is configured to receive the parameter information reported by the at least one application.

With reference to the second aspect, in some implementations of the second aspect, when the network slice is single-pass after the processing unit binds the route to the network slice, the processing module is further configured to bind the route to a network slice of a next priority of the network slice.

With reference to the second aspect, in some implementations of the second aspect, the processing module is further configured to bind the route to a default network slice if the network slice of the next priority does not exist.

In a third aspect, there is provided a computer storage medium having stored thereon computer-executable instructions for causing a computer, when invoked by the computer, to perform the method of any one of the first aspects.

Drawings

Fig. 1 is a schematic architecture diagram of a communication system suitable for use in embodiments of the present application.

Fig. 2 is a schematic diagram of a method for selecting a network slice according to an embodiment of the present application.

Fig. 3 is a schematic flowchart of selecting a network slice according to an embodiment of the present application.

Fig. 4 is a schematic flowchart of another method for selecting a network slice according to an embodiment of the present application.

Fig. 5 is a schematic diagram of performing a URSP policy provided in an embodiment of the present application.

Fig. 6 is a schematic diagram of a single-pass self-healing method provided in an embodiment of the present application.

Fig. 7 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Fig. 8 shows a schematic structural diagram of an electronic device provided in an embodiment of the present application.

Detailed Description

The technical solution in the present application will be described below with reference to the accompanying drawings.

The electronic equipment in this application embodiment can be the electronic equipment that has the camera such as cell-phone, panel computer, notebook computer, intelligent bracelet, intelligent wrist-watch, intelligent helmet, intelligent glasses, unmanned aerial vehicle. The electronic device may also be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, an electronic device in a 5G network, or an electronic device in a Public Land Mobile Network (PLMN) for future evolution, and the like, which are not limited in this embodiment.

Fig. 1 is a schematic architecture diagram of a mobile communication system suitable for use in the embodiments of the present application.

As shown in fig. 1, the mobile communication system 100 may include at least one network device 101 and at least one UE 102. Fig. 1 is a schematic diagram, and other network devices, such as a wireless relay device and a wireless backhaul device, may also be included in the communication system, which are not shown in fig. 1. The embodiments of the present application do not limit the number and specific types of network devices and UEs included in the mobile communication system.

The electronic device 102 in the embodiments of the present application may refer to an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a user terminal, a wireless communication device, a user agent, or a user equipment. The electronic device may also be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with Wireless communication function, a computing device or other processing device connected to a Wireless modem, a vehicle-mounted device, a wearable device, an electronic device in a 5G Network or an electronic device in a Public Land Mobile Network (PLMN) for future evolution, and may also be various chips for electronic devices, and the like, which are not limited in this embodiment.

The network device 101 in this embodiment may be a device for communicating with an electronic device, and the network device may be a network device in a 5G network (New Generation NodeB, gNB, or gnnodeb) or a network device in a PLMN network for future evolution, and a network device supporting 3rd Generation Partnership Project (3 GPP) protocol version, such as a network device of 6G or 7G, and the like, which is not limited in this embodiment.

Optionally, the communication method of the present application may also be extended to various communication systems, such as a 5G system, a New Radio (NR) system, a 6G system above the 5G system, and the like.

At present, no specific implementation scheme of the network slice in the electronic device exists, and the existing technology cannot fully cover various scenes of the network slice. The application provides a solution, which not only solves the problem that a third party application does not change the scene to select the network slice for the application, but also meets the requirement that the scene of the third party application is changed to provide a brand-new interface to select the network slice for the application. The electronic device includes at least one Application (APP), and acquires parameters for network slice selection according to the APP, thereby effectively solving the above-mentioned problems.

S201, determining parameter information according to at least one application. Wherein the parameter information is used to indicate the network slice.

Optionally, the parameter information may include at least one of an application identification (app ID), a Data Network Name (DNN), an Internet Protocol (IP) triplet or a domain name (FQDN).

Optionally, the electronic device may listen to at least one application to obtain the parameter information. For example, the electronic device may obtain the parameter information by listening to data interactions of at least one application with other layers or interfaces or the like through the application layer. The app ID or DNN may be acquired through an application entering a foreground among the at least one application or a call request network (request network) interface. It should be understood that the application entering the foreground of the at least one application may refer to the application being used by the user. The electronic device may perform data interaction with a kernel layer (kernel) through at least one application to obtain the IP triplet. The FQDN may be obtained by data interaction between at least one application and a network daemon (network). The application to the foreground may refer to an application being used by a user, or an application needing to acquire data being run in the background.

Optionally, at least one application reports parameter information. When a service change occurs in at least one application, the at least one application may actively report parameter information, and the parameter information may correspond to a network slice required by the changed service. For example, when a user performs an operation in at least one application, the required parameter information may be reported to the electronic device, and when the user uses a microblog, the app ID may be com.sina.weibo; when the mobile network user uses the multimedia message, DNN of the mobile network user may be cmwap; the IP triple is IPv4 address/IPv 6 address, protocol type (TCP, UDP) and port number; when a user uses a tremble, its FQDN may be aweme.

It should be understood that the electronic device may obtain the parameter information in various ways, and the present application does not limit the way of obtaining the information.

S202, perform a routing policy (UE routing policy, URSP) according to the parameter information. Wherein the routing policy is used to select a network slice.

Alternatively, the URSP policy may be executed according to the parameter information. Matching can be performed according to the parameter information, and the routing parameters can be selected after the matching is successful, so that the network slice bound by the routing can be determined.

S203, binding the route of the electronic equipment to the network slice.

Optionally, when the network slice is a single-pass network slice after the route of the electronic device is bound to the network slice, the route of the terminal device may be bound to the network slice of the next priority of the single-pass network slice.

Optionally, if there is no network slice of the next priority, the route of the terminal device may be bound to a default network slice.

It should be understood that the technical solution provided in the embodiments of the present application provides an implementation scheme of a specific network slice in an electronic device, and may cover various scenarios of the network slice. The electronic device may obtain the parameter information by monitoring a service of at least one application or actively reporting by at least one application, may select a corresponding network slice for a service performed in at least one application according to the parameter information, and perform route binding.

Fig. 3 is a schematic flowchart of selecting a network slice without modifying at least one application according to an embodiment of the present disclosure.

The network device may send the first information to a modem (modem) in the electronic device S301. The first information may include authorized network slice selection assistance information (authorized NSSAI).

Optionally, the network device may send the first information to a non-access stratum (NAS) of the modem.

Alternatively, the first information may be registration acceptance information (registration accept) or a configuration update command (configuration).

S302, the modem reports the allowed NSSAI included in the first information to an Application Processor (AP).

S303, storing the allowed NSSAI.

S304, the network device may send the second information to the modem in the electronic device. The second information may include a URSP policy.

Optionally, the network device may send the second information to a NAS layer of the modem.

Alternatively, the second message may be a downlink NAS transport message (downlink NAS transport message).

S305, the modem reports the URSP policy included in the second information to the AP.

S306, the AP stores the URSP strategy.

Optionally, decoding and validity checking of the URSP policy may be done by the AP.

S307, the AP sends third information to the modem, wherein the third information is used for indicating that the modem strategy is completed or rejected (modem management UE policy complete/management UE policy command request).

S308, the modem sends fourth information to the network device, and the fourth information is used for replying to the second information sent by the network device.

Optionally, the fourth information may be uplink NAS transport message (uplink NAS transport message), where the fourth information may include a part of the information in the third information.

S309, monitoring at least one application, thereby obtaining parameter information.

Optionally, at least one application acquisition parameter information may be listened to through a framework layer (framework) to perform the URSP policy selection network slice.

Optionally, S310, after at least one application reaches the foreground, a request network information (request network) may be sent to the AP.

It should be appreciated that S310 is an optional step. When an application in at least one application reaches the foreground, the AP may obtain parameter information by monitoring the application reaching the foreground, and perform network slice selection for the application reaching the foreground.

Optionally, when a service change occurs in at least one application, the AP may obtain the parameter information by monitoring data interaction between the at least one application and other layers or interfaces through the application layer.

Optionally, the framework layer listens to at least one application foreground and acquires the app ID or DNN. Or calling a native request Network interface by an application from the foreground in at least one application, and identifying that app ID or DNN is acquired later by the framework layer to perform URSP selection Network slice.

Optionally, the Netd reports the FQDN information to the framework layer in a domain name system protocol (DMS) query process, and the framework layer integrates the FQDN information and app ID or DNN of the foreground application to perform the URSP policy selection network slice.

Optionally, the kernel layer reports the IP triplet information to the framework layer in a socket (socket) establishing process, and the framework layer integrates the IP triplet information and app ID or DNN of the foreground application to perform the URSP policy selection network slice.

S311, judging whether to acquire parameter information.

Alternatively, if the parameter information is obtained by monitoring, the URSP may be performed. If the parameter information is not acquired, the network slice selection fails, and a network slice is not selected or a default network slice is selected.

And S312, carrying out URSP strategy.

And S313, initiating network slice activation according to the URSP strategy.

S314, the electronic device sends a session establishment request (session establishment request) to the network device.

Alternatively, the network device may be a Protocol Data Unit (PDU).

It should be understood that each PDU session constitutes a network slice.

S315, the network device sends a session establishment acceptance (session establishment accept) to the electronic device.

S316, the modem sends activation success information to the AP.

S317, route binding to network slice.

According to the technical scheme provided by the embodiment of the application, the AP monitors the application to the foreground, acquires the parameter information to match the URSP for the application and initiates the network slice, and binds the route to the new network slice after the network slice is successfully activated.

Fig. 4 is a schematic flowchart of selecting a network slice when at least one application is modified according to an embodiment of the present disclosure.

S401, the network device may send the fifth information to the modem in the electronic device. The fifth information may include allowed NSSAI.

Optionally, the network device can send the first information to a NAS of the modem.

Alternatively, the first information may be registration acceptance information or a configuration update command.

S402, the modem reports the allowed NSSAI included in the first information to the AP.

S403, storing allowed NSSAI.

S404, the network device may send the sixth information to the modem in the electronic device. The URSP policy may be included in the sixth information.

Optionally, the network device may send the sixth information to a NAS layer of the modem.

Alternatively, the sixth message may be a downlink NAS transport message (downlink NAS transport message).

S405, the modem reports the URSP policy included in the sixth information to the AP.

S406, the AP stores the URSP strategy.

S407, the AP sends seventh information to the modem, where the seventh information is used to indicate that the modem policy is completed or rejected.

S408, the modem sends the eighth information to the network device for replying to the sixth information sent by the network device.

Optionally, the eighth information may be uplink NAS transport information, where the eighth information may include part of information in the seventh information.

S409, at least one application reports the parameter information.

Optionally, when a service change occurs in at least one application, the at least one application may actively report parameter information, and the parameter information may correspond to a network slice required by the changed service.

And S410, carrying out URSP strategy.

And S411, initiating network slice activation according to the URSP strategy.

S412, the electronic device sends a session establishment request to the network device.

Alternatively, the network device may be a PDU.

S413, the network device transmits a session establishment acceptance to the electronic device.

S414, the modem sends activation success information to the AP.

S415, the route is bound to the network slice.

According to the technical scheme provided by the embodiment of the application, the AP can provide an expansion interface for at least one application according to service requirements, so that the at least one application can report parameter information, and a URSP policy is carried out.

As shown in fig. 5, the method for performing the URSP policy provided in this embodiment of the present application may be used in S312 or S410 described above.

S501, traversing the URSP strategy list according to the priority.

Optionally, traversing the list of URSP policies according to the reference information, and selecting the highest priority URSP policy.

S502, judging whether the next priority URSP strategy exists.

Optionally, if there is a next priority URSP policy, performing traffic identifier (traffic descriptor) matching; if not, the selection fails and a default network slice may be bound.

Optionally, if all USRPs are not successfully traversed, matching a full match (match all) for the default network slice by the traffic identifier, and binding the default network slice.

And S503, matching the traffic identifiers.

Alternatively, the traffic identifier may be included in the second message in fig. 3 or the sixth message in fig. 4, and issued to the electronic device by the network device.

S504, whether the flow identifiers are successfully matched is judged.

Optionally, matching is performed on the parameter information through the traffic identifier, and if the matching fails, returning to S502 to try the URSP policy of the next priority.

S505, traverse the routing list (route selection list).

Optionally, the routing parameter is selected according to the priority from the information obtained by matching the parameter information, and a single network slice selection establishment information (S-NSSAI) is matched according to the routing parameter.

S506, judging whether the S-NSSAI is contained in the allowed NSSAI.

Alternatively, if the S-NSSAI is not in an allowed NSSAI, then the URSP policy for the next priority is attempted. If the S-NSSAI is in an allowed NSSAI, then the next step is performed.

S507, selecting S-NSSAI as PDU conversation activating parameter.

And S508, judging whether the activation is performed according to the S-NSSAI and the DNN.

The technical scheme provided by the embodiment of the application can select the URSP strategy with higher priority for the routing of the electronic equipment.

As shown in fig. 6, the method provided by the embodiment of the present application may be applied to the network slice after the routes shown in fig. 3 and fig. 4 are bound to the network slice, where the network slice only provides a single-pass data connection, that is, data transmission between the network device and the electronic device is upload or download. The method provided by the embodiment of the application can be executed by the AP, and the self-healing process is started after the AP receives the one-way information.

S601, receiving the one-way message.

Optionally, the one-way message may be reported to the AP after the kernel layer detects that only one way exists in a foreground application in the at least one application.

S602, judging whether the next priority URSP strategy exists.

Alternatively, if there is a next priority URSP policy, the method shown in fig. 5 is performed according to the next priority URSP policy. And if the URSP strategy matching is successful, activating the URSP strategy of the next priority.

Optionally, if there is no next priority URSP policy, the binding route is routed to the default network slice, and the default network slice activation is initiated.

And S603, if the next priority URSP strategy exists and the matching is successful, initiating new network slice activation.

And S604, judging whether the new network slice is successfully activated.

S605, if the activation is successful, the route is bound to a new network slice; if not, returning to S602, the URSP policy of the next priority is tried. According to the technical scheme provided by the embodiment of the application, when a certain service in at least one application in the electronic equipment is single-pass, the method can be automatically executed, the rapid network slice self-healing process is realized, and the data connection is recovered.

Fig. 7 is a schematic structural diagram of an electronic device according to an embodiment of the present application. For implementing the operation of the electronic device in the above embodiment.

As shown in fig. 7, the electronic device may include at least one application and may further include a processing unit 701.

Wherein, the processing unit 701 may be configured to determine parameter information according to at least one application, the parameter information being used to indicate a network slice; the processing unit 701 may be configured to perform a routing policy according to the parameter information, where the routing policy is used to select a network slice; the processing unit 701 may also be used to bind routes to network slices.

Optionally, the parameter information includes at least one of an application identification, a data network name, an internet protocol, IP, triplet, or a domain name.

Optionally, the method for determining parameter information according to at least one application includes: and monitoring at least one application and determining parameter information.

Optionally, monitoring at least one application, and determining parameter information, including: at least one application enters a foreground or calls a request network interface to determine an application identifier or a data network name; or, the kernel layer acquires at least one IP triple of the application; or, the domain name of the at least one application is obtained by the network daemon.

Optionally, the method for determining parameter information according to at least one application includes: the processing unit is used for receiving parameter information reported by at least one application.

Optionally, when the network slice is a single pass after the processing unit binds the route to the network slice, the processing module is further configured to bind the route to the network slice of the next priority of the network slice.

Optionally, the processing module is further configured to bind the route to the default network slice if there is no network slice of the next priority.

Fig. 8 shows a schematic structural diagram of an electronic device provided in an embodiment of the present application. For implementing the operation of the electronic device in the above embodiment.

As shown in fig. 8, the electronic apparatus includes: antenna 810, radio frequency device 820, baseband device 830. Antenna 810 is coupled to radio 820. In the downlink direction, rf apparatus 820 receives information transmitted by the network device through antenna 810, and transmits the information transmitted by the network device to baseband apparatus 830 for processing. In the uplink direction, the baseband device 830 processes the information of the electronic device and sends the information to the radio frequency device 820, and the radio frequency device 820 processes the information of the electronic device and sends the information to the network device through the antenna 810.

The baseband apparatus 830 may include a modem subsystem for implementing processing of various communication protocol layers of data; the system also comprises a central processing subsystem used for realizing the processing of a terminal operating system and an application layer; in addition, other subsystems, such as a multimedia subsystem for controlling a camera, a screen display, etc. of the electronic device, peripheral subsystems for connecting with other devices, etc. may be included. The modem subsystem may be a separate chip. Alternatively, the above means for the terminal may be located at the modem subsystem.

The modem subsystem may include one or more processing elements 831, including, for example, a host CPU and other integrated circuits. The modem subsystem may also include a storage element 832 and an interface circuit 833. The storage element 832 is used to store data and programs, but programs for carrying out the methods performed by the electronic device in the above methods may not be stored in the storage element 832, but in a memory external to the modem subsystem. The interface circuit 833 is used to communicate with other subsystems. The above apparatus for an electronic device may be located in a modem subsystem, which may be implemented by a chip comprising at least one processing element for performing the steps of any of the methods performed by the above electronic device and interface circuitry for communicating with other apparatus. In one implementation, the unit of the electronic device for implementing the steps in the above method may be implemented in the form of a processing element scheduler, for example, an apparatus for an electronic device includes a processing element and a storage element, and the processing element calls a program stored in the storage element to execute the method executed by the terminal in the above method embodiment. The memory elements may be memory elements with the processing elements on the same chip, i.e. on-chip memory elements.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the procedures or functions according to the embodiments of the present invention are generated in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website site, computer, server, or data center to another website site, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device including one or more available media integrated servers, data centers, and the like. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method for selecting a network slice, applied to an electronic device including at least one application, the method comprising:

determining parameter information according to the at least one application, the parameter information being indicative of a network slice;

performing a routing strategy according to the parameter information, wherein the routing strategy is used for selecting the network slice;

binding the route of the electronic device to the network slice.

2. The method of claim 1, wherein the parameter information comprises at least one of an application identification, a data network name, an Internet Protocol (IP) triplet, or a domain name.

3. The method of claim 1, wherein determining parameter information according to the at least one application comprises:

and monitoring the at least one application and determining the parameter information.

4. The method of claim 3, wherein the listening for the at least one application to determine the parameter information comprises:

determining an application identifier or a data network name by the at least one application entering a foreground or calling a request network interface;

or, the kernel layer acquires the IP triple of the at least one application;

or, obtaining the domain name of the at least one application by a network daemon.

5. The method of claim 1, wherein determining parameter information according to the at least one application comprises:

and the at least one application reports the parameter information.

6. The method of any of claims 1 to 5, wherein when the network slice is single-pass after the binding is routed to the network slice, the method further comprises:

binding the route to a network slice of a next priority of the network slice.

7. The method of claim 6, wherein the route is bound to a default network slice if the next priority network slice does not exist.

8. An electronic device, characterized in that the electronic device comprises:

at least one application;

a processing unit configured to determine parameter information according to the at least one application, the parameter information indicating a network slice;

the processing unit is further configured to perform the routing policy according to the parameter information, where the routing policy is used to select the network slice;

the processing unit is further configured to bind routes to the network slice.

9. The electronic device of claim 8, wherein the parameter information comprises at least one of an application identification, a data network name, an Internet Protocol (IP) triplet, or a domain name.

10. The electronic device of claim 8, wherein the means for determining parameter information according to the at least one application comprises:

11. The electronic device of claim 10, wherein said listening for the at least one application, determining the parameter information, comprises:

or, the kernel layer acquires the IP triple of the at least one application;

12. The electronic device of claim 8, wherein the means for determining parameter information according to the at least one application comprises:

the processing unit is configured to receive the parameter information reported by the at least one application.

13. The electronic device of any of claims 8-12, wherein when the network slice is single-pass after the processing unit binds the route to the network slice, the processing module is further configured to bind the route to a next-priority network slice of the network slice.

14. The electronic device of claim 13, wherein the processing module is further configured to bind the route to a default network slice if the next priority network slice does not exist.

15. A computer storage medium having stored therein computer-executable instructions for causing a computer to perform the method of any one of claims 1 to 7 when invoked by the computer.