Data routing method and device
By sending requests to users in front of routing terminal service data and routing based on user permissions, the problem that users cannot perceive network slicing differences is solved, and the user experience is improved.
Patent Information
- Application Number
- CN202210302687.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-03-25
- Publication Date
- 2024-11-05
- Estimated Expiration
- 2042-03-25
AI Technical Summary
In different network slices, the service data routing of the terminal causes users to be unable to perceive the differences in service quality, power consumption and billing rules, resulting in poor user experience.
Before routing the terminal service data, a routing request is sent to the user and the route is performed after the user's permission is made. If the user blocks it, the routing is terminated, the network slice is determined by searching for routing rules, and the route is updated in response to changes in the service data.
This enables users to perceive business data and their routing rules, improves user experience and avoids unexpected charges and power consumption problems.
Smart Images

Figure CN114666863B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of communication technology, and in particular to a data routing method and device. Background Art
[0002] In related technologies, the service data of a terminal can be routed to the corresponding network slice according to different routing rules. Different charging rules or terminal power consumption may be generated in different network slices, but users cannot perceive these differences, resulting in a poor user experience. Summary of the invention
[0003] In view of this, the present application provides a data routing method and device to solve the problem of poor user experience when routing terminal service data to a network.
[0004] In a first aspect, a data routing method is provided, the method comprising: determining a network slice corresponding to the current business data based on the current business data of a first terminal; sending a routing request to a user before routing the current business data; if the user approves the routing request, routing the current business data.
[0005] As a possible implementation manner, the method further includes: if the user blocks the routing request, terminating the routing of the current service data.
[0006] As a possible implementation method, determining the network slice corresponding to the current business data based on the current business data of the first terminal includes: determining the network slice corresponding to the current business data by searching a first routing rule, wherein the first routing rule contains a mapping relationship between the current business data and the network slice.
[0007] As a possible implementation manner, the sending a routing request to the user includes: presenting the first routing rule to the user.
[0008] As a possible implementation method, determining the network slice corresponding to the current business data according to the current business data of the first terminal includes: responding to changes in the business data of the first terminal, and determining the network slice corresponding to the current business data of the first terminal according to the current business data of the first terminal.
[0009] According to a second aspect, a data routing device is provided, comprising: a determination unit for determining, based on the current business data of a first terminal, a network slice corresponding to the current business data; a request unit for sending a routing request to a user before routing the current business data; and a first routing unit for routing the current business data if the user approves the routing request.
[0010] As a possible implementation manner, the device further includes: a second routing unit, configured to terminate routing of the current service data if the user blocks the routing request.
[0011] As a possible implementation method, the determination unit is also used to: determine the network slice corresponding to the current business data by searching a first routing rule, wherein the first routing rule contains a mapping relationship between the current business data and the network slice.
[0012] As a possible implementation manner, the requesting unit is further configured to: present the first routing rule to the user.
[0013] As a possible implementation method, the determination unit is also used to: in response to a change in the business data of the first terminal, determine the network slice corresponding to the current business data of the first terminal according to the current business data of the first terminal.
[0014] According to a third aspect, a data routing device is provided, comprising a memory and a processor, wherein the memory is used to store programs, and the processor is used to call the programs in the memory to execute the method described in the first aspect or any implementation of the first aspect.
[0015] According to a fourth aspect, a computer-readable storage medium is provided, on which an executable code is stored. When the executable code is executed, the method described in the first aspect or any implementation method of the first aspect can be implemented.
[0016] According to a fifth aspect, a computer program product is provided, comprising an executable code, which, when executed, can implement the method described in the first aspect or any implementation method of the first aspect.
[0017] The data routing method provided in the application embodiment needs to send a routing request to the user before routing the service data of the terminal. If the user approves the routing request, the current service data is routed. In this way, the user can perceive the current service data and its corresponding route, thereby improving the user experience. BRIEF DESCRIPTION OF THE DRAWINGS
[0018] Figure 1 A schematic diagram of the architecture of a communication system provided in one embodiment of the present application.
[0019] Figure 2 A flowchart of a data routing method provided in accordance with an embodiment of the present application.
[0020] Figure 3A schematic diagram of the mapping relationship between business data and network slices provided in one embodiment of the present application.
[0021] Figure 4 A flowchart of a data routing method provided in another embodiment of the present application.
[0022] Figure 5 A flowchart of a data routing method provided in yet another embodiment of the present application.
[0023] Figure 6 A flowchart of a method for configuring URSP rules provided in one embodiment of the present application is provided.
[0024] Figure 7 A structural schematic diagram of a data routing device provided in one embodiment of the present application.
[0025] Figure 8 A structural schematic diagram of a data routing device provided in another embodiment of the present application. DETAILED DESCRIPTION
[0026] The technical solutions in the embodiments of the present application are described clearly and completely below. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all of the embodiments.
[0027] Figure 1 The communication system 100 is applied in the embodiment of the present application. The communication system 100 may include a network device 110 and a user equipment (UE) 120. The network device 110 may be a device that communicates with the user equipment 120. The network device 110 may provide network coverage for a specific geographical area, and may communicate with the user equipment 120 located in the coverage area. The user equipment 120 may access a network (such as a wireless network) through the network device 110. Optionally, the wireless communication system 100 may also include other network entities such as a network controller and a mobility management entity, which is not limited in the embodiment of the present application.
[0028] It should be understood that the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: the fifth generation (5th generation, 5G) system or new radio (new radio, NR), long term evolution (long term evolution, LTE) system, LTE frequency division duplex (frequency division duplex, FDD) system, LTE time division duplex (time division duplex, TDD), etc. The technical solutions provided by the present application can also be applied to future communication systems, such as the sixth generation mobile communication system, satellite communication system, and so on.
[0029] The user equipment in the embodiments of the present application may also be referred to as terminal equipment, access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device. The terminal equipment in the embodiments of the present application may refer to a device that provides voice and / or data connectivity to a user, and may be used to connect people, objects and machines, such as a handheld device with a wireless connection function, a vehicle-mounted device, etc. The terminal device in the embodiments of the present application can be a mobile phone, a tablet computer (Pad), a laptop computer, a PDA, a mobile internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, etc.
[0030] The network device 110 in the embodiment of the present application may be a device for communicating with a terminal device, and the network device 110 may also be referred to as an access network device or a wireless access network device, such as a base station. The base station may broadly cover the following various names, or be replaced with the following names, such as: NodeB, evolved NodeB (eNB), next generation NodeB (gNB), relay station, access point, transmission point (transmitting and receiving point, TRP), transmission point (transmitting point, TP), master station MeNB, auxiliary station SeNB, multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (access point, AP), transmission node, transceiver node, baseband unit (base band unit, BBU), remote radio unit (Remote Radio Unit, RRU), active antenna unit (active antenna unit, AAU), radio head (remote radio head, RRH), central unit (central unit, CU), distributed unit (distributed unit, DU), positioning node, etc. The base station may be a macro base station, a micro base station, a relay node, a donor node, or the like, or a combination thereof.
[0031] For another example, the network device 110 may be a core network (CN) device that provides service support for the terminal. Common core network devices may include, for example, an access and mobility management function (AMF) entity, a (radio) access network (R) AN) entity, a session management function (SMF) entity, a user plane function (UPF) entity, and a core network policy control network element (PCF) entity, etc., which are not listed here one by one. Among them, the AMF entity may be responsible for the access management and mobility management of the terminal; the terminal device may access the AMF entity through the interface of the (R) AN; the SMF entity may be responsible for session management, such as user session establishment; the UPF entity may be a functional entity of the user plane, mainly responsible for connecting to the external network; the PCF entity may be responsible for providing policy information.
[0032] Network slicing technology can divide a physical network into multiple network slices, each of which can constitute an end-to-end logical network. The network can be divided into multiple logically isolated and mutually independent network slices according to different communication requirements. In some embodiments, the network can be divided into enhanced mobile broadband (eMBB) network slices, ultra-reliable and low-latency communications (URLLC) network slices, vehicle to X (V2X) network slices, Internet of Things (IoT) network slices, and massive IoT (MIoT) network slices. The network characteristics of different types of network slices can be different. For example, eMBB network slices can have the characteristics of supporting large bandwidth and low latency services; URLLC network slices can have the characteristics of high reliability and low latency.
[0033] 5G network operators need to control the way terminals (UE) use the network, that is, to provide differentiated quality of service (QoS) based on the user's contract information. Especially after the 5G network has the ability to slice, the demand for such customized services is even stronger. In some embodiments, a mapping relationship between terminal services and network slices can be established, and different terminal routing rules can route the terminal's services to different network slices to achieve differentiated QoS services. Among them, the routing rule can be, for example, a user equipment path selection policy (UE route selection policy, URSP), and the terminal's service data can be, for example, the data of an application on the terminal.
[0034] In some embodiments, the terminal can use routing rules to route the terminal's service data to the corresponding network slice through a protocol data unit session (PDU session). For example, the terminal can use routing rules to route the terminal's service data to an existing PDU session; it can also not use any existing PDU session and load balance the terminal's service data to non-3GPP access, such as accessing a network device through WIFI; it can also not use any existing PDU session and trigger a new PDU establishment request, which will be used after the new PDU is established.
[0035] The following takes the URSP policy as an example to introduce the process of establishing routing rules. It should be understood that the embodiment of the present application does not limit the terminal routing rules. The routing rules can be, for example, the URSP mentioned above, or the network slice selection policy (NSSP), or other forms of terminal device routing rules.
[0036] In some embodiments, the routing rules may be pre-configured in the terminal device by the operator, or may be sent to the terminal device by the network device when the terminal device accesses the network. For example, when the routing policy is a URSP rule, the URSP rule may be pre-configured in the terminal device. For example, the operator may pre-configure the URSP rule according to the network information, and configure the pre-configured URSP rule in the terminal device. The URSP rule may also be sent by the network. For example, when the terminal device registers to access the network, the core network element may provide the URSP rule to the AMF, and the AMF may send it to the UE via the "Manage UE Policy Command" signaling (which will be discussed later in conjunction with the URSP rule). Figure 6 This article provides an example of how the URSP rules are issued by the network. For details, please refer to Figure 6 ).
[0037] The URSP may include multiple URSP rules, and each URSP rule may include two parts: a traffic descriptor (TD) and a route selection descriptor (RSD). In some embodiments, each URSP rule may also include a rule priority.
[0038] Table 1
[0039]
[0040] Table 1 is a URSP rule list provided in an embodiment of the present application. As shown in Table 1, each URSP rule may include one or more traffic descriptors and one or more routing descriptors, wherein each routing descriptor may include one or more routing description components. Traffic descriptors may be of multiple types. Table 2 provides 22 optional traffic descriptor types. In some embodiments, the format of the traffic descriptor is [traffic descriptor type, traffic descriptor value], and the length of the traffic descriptor may vary with the type of the traffic descriptor.
[0041] Table 2
[0042]
[0043]
[0044] There may be multiple types of routing description components. Table 3 provides 9 optional routing description components. In some embodiments, the format of the routing description component is [routing component type, routing component value], and the length of the routing component value may vary with the type of component.
[0045] Table 3
[0046]
[0047] The traffic descriptor in the URSP rule can be used to match the service data of the terminal device. The service data of the terminal device can be, for example, the service type data of the terminal device, which can be, for example, video service or audio service; the service data of the terminal device can also be the service data of the terminal application, which can include, for example, the APP ID of the application. The routing descriptor in the URSP rule is used to select the routing method of the service data.
[0048] When using URSP rules to route the service data of the terminal device, the URSP rules can be matched according to the service data of the terminal device first, and then the routing rules of the service data can be determined according to the matched URSP rules. For example, according to the selected URSP rule, any RSD in the URSP rule can be selected, and any RSD rule can be matched with the existing PDU session. If any RSD matches the existing PDU session, the service data of the terminal device is routed to the network carrying the service data using the PDU session; if all RSDs in the URSP rule do not match the existing PDU, a new PDU session establishment request can be initiated, and after the PDU session is established, the service data of the terminal device is routed to the network carrying the service data. In some embodiments, the service data of the terminal device can also be load balanced to non-3GPP access, such as accessing the network through WIFI, according to the selected URSP rule. In some embodiments, there can be multiple URSP rules that match the service data of the terminal device, and the URSP rule matching can be performed according to the priority of the URSP. When all RSDs in the selected first URSP rule cannot match the existing PDU session, a second URSP rule may be selected according to the priority, and the RSDs may be matched with the existing PDU session, and so on.
[0049] As an example, the service data of the terminal device may include the APP ID of the application. When the application is started, the terminal device may initiate a service data routing request to the network device. After receiving the routing request, the network device matches the value of the APP ID in the service data with the value of the APP ID in the traffic descriptor in the URSP rule, and sends the matched URSP rule to the terminal device. Then, the terminal device may route the service data of the application to the network slice corresponding to the URSP rule according to the URSP rule.
[0050] It can be seen that in the prior art, the service data of the terminal can be routed to the corresponding network slice according to different routing rules. However, different service quality, terminal power consumption, billing rules, etc. may be generated in different network slices. For example, when the terminal is in high-speed mode or game mode, the current service data will be routed to the ultra-reliable and low-latency URLLC network slice, but higher billing and terminal power consumption will be generated in the URLLC network slice. Users cannot perceive these differences, resulting in a poor user experience.
[0051] In order to solve the above problem, the embodiment of the present application provides a data routing method, which first sends a routing request to the user before routing the service data of the terminal according to the routing rule; if the user approves the routing request, the current service data is routed. In this way, the user can perceive the current service data and its corresponding routing rules, thereby improving the user experience.
[0052] Combined with the following Figure 2 The data routing method in the embodiment of the present application is introduced in detail. Figure 2 The routing method 200 includes steps S220 to S260.
[0053] In step S220, the network slice corresponding to the current business data of the first terminal is determined based on the current business data of the first terminal.
[0054] The first terminal may be any terminal in the embodiments of the present application described above.
[0055] The embodiment of the present application does not specifically limit the type of service data. For example, the service data may be application data on a terminal device. The application may be, for example, browser data or data of a mobile game. It may also include the application's APP ID, data network name DNN, etc. For another example, the service data may also be service type data of a terminal device. The service type data may be, for example, video service or audio service.
[0056] In some embodiments, the first routing rule can be used to guide the terminal device to route service data to the corresponding network slice according to the current service characteristics. The network slice corresponding to the current service data of the terminal device can be determined by searching the first routing rule, wherein the first routing rule may include a mapping relationship between the current service data and the network slice. The first routing rule may be, for example, the URSP, NSSP, etc. mentioned above. It should be understood that the first routing rule in the embodiment of the present application may also be other forms of terminal routing rules. The mapping relationship mentioned above may be, for example, different network slices corresponding to the data of different applications, and the different network slices may provide differentiated QoS services. The following is combined with Figure 3 The mapping relationship between business data and network slices is illustrated by way of example.
[0057] like Figure 3 As shown, as an example, the service data of the terminal may be the data of application 1. At this time, the corresponding routing rule may be selected according to the service data matching of application 1. Then, application 1 may use the selected routing rule to route the service data to the corresponding network slice 1, and application service 1 may be provided in network slice 1. For example, application 1 may be a browser, and the network slice 1 corresponding to the service data of the browser may be, for example, an eMBB network slice. In this way, the browser data may use application service 1 provided by the eMBB network slice, i.e., application service quality with large bandwidth and low latency; similarly, if application 2 of the terminal is a mobile game, its corresponding network slice 2 may be, for example, a URLLC network slice. In this way, the mobile game data may use application service 2 provided by the URLLC network slice, i.e., application service quality with ultra-reliable and low latency.
[0058] It should be understood that different terminal service data may also be routed to the same network slice, and this application does not impose any specific restrictions on this.
[0059] It should be understood that the first routing rule may include a mapping relationship between one or more business data and network slices, and the embodiments of the present application do not impose any specific restrictions on this.
[0060] In step S240, before routing the current service data of the first terminal, a routing request is sent to the user.
[0061] The embodiments of the present application do not specifically limit the manner in which a routing request is sent to a user, as long as the user can perceive the current routing request. As an example, sending a routing request to a user may refer to presenting the routing request to the user through a terminal interface, and the user confirms the routing request (for example, the user may agree or reject it). In some embodiments, sending a routing request to a user may also include presenting the current business data (such as an application) and its corresponding routing rules to the user, and then the user confirms the current routing request.
[0062] As another example, sending a routing request to a user may also refer to sending a routing request to an application of a terminal device, and then the routing request is confirmed by program logic preset in the application. The embodiments of the present application do not impose specific limitations on this, as long as the current routing request can be automatically determined.
[0063] As another example, sending a routing request to a user may also refer to presenting the routing request to the user through a third-party device interface, or sending a routing request to an application of a third-party device, which then presents the routing request to the user through the interface of the third-party device for confirmation of the routing request, or confirming the routing request through application logic preset in the third party.
[0064] The embodiment of the present application does not impose any specific restrictions on the confirmation method of the routing request. For example, the routing request may be confirmed by presenting it to the user through a device interface, or by performing potential automatic confirmation through the program logic of the application. However, no matter which method is used, it means that the user knows the current business data and its corresponding routing rules, that is, the user can perceive the current business data and its corresponding routing rules, so that he can have a clear idea of it, which improves the user experience.
[0065] It should be understood that the embodiments of the present application do not impose any specific restrictions on the sender of the routing request. For example, it can be the current application or other applications of the terminal device, or it can be a routing management entity, etc.
[0066] It should be understood that the embodiment of the present application does not impose any specific restrictions on the sending object of the routing request. For example, the routing request can also be sent to a network device, and then the network device confirms the routing request.
[0067] In step S260, if the user approves the routing request, the current service data of the first terminal is routed according to the first routing rule.
[0068] In some embodiments, user permission (i.e., consent) to a routing request may refer to the first time the user agrees to the routing request, or may refer to the user having previously agreed to the routing request. It should be understood that user rejection of a routing request may refer to the first time the user rejects the routing request, or may refer to the user having previously rejected the current routing request. In other words, if the user agrees or has previously accepted the current routing request, the current service data of the terminal may be routed according to the routing rule. If the user rejects or has previously rejected the routing request, the routing of the current service data is terminated.
[0069] In some embodiments, before using a network with routing rules, an application may first apply to a routing entity. The routing management entity selects an appropriate routing strategy based on the routing rules and application characteristics. Before this strategy takes effect, the routing management entity needs to confirm with the user whether to allow the request (that is, the application uses a certain established routing rule). If the user allows, the application can use the network. Otherwise, the application cannot use the network.
[0070] In some cases, when the service data of the terminal changes, the method provided in the embodiment of the present application can also respond to the change in the service data of the terminal, and according to the current service data of the terminal, by searching for the corresponding routing rules, to determine and update the network slice corresponding to the current service data. As an example, when the service data of the terminal is browser data, the terminal can route the service data to the eMBB network slice according to the routing rules. When the service data of the terminal changes from browser data to the data of a mobile game, the routing rules can be reselected according to the service data of the mobile game, and then the terminal can route the service data of the mobile game to the URLLC network slice according to the new routing rules.
[0071] The embodiment of the present application provides a data routing method, which first sends a routing request to the user before routing the service data of the terminal according to the routing rule; if the user approves the routing request, the current service data is routed. In this way, the user can perceive the current service data and its corresponding routing rules, thereby improving the user experience.
[0072] In order to further illustrate the data routing method in the embodiment of the present application, the following takes the routing rule URSP as an example. Figure 4 and Figure 5 The process of the data routing method in the embodiment of the present application is described in detail.
[0073] like Figure 4As shown, another data routing method in an embodiment of the present application, the terminal side may include a routing management entity, an application and its corresponding URSP rules. Before using the network of the URSP rules, the application needs to apply to the routing management entity. The routing management entity selects a suitable routing strategy according to the URSP rules and the data characteristics of the application to route the service data of the application to the corresponding network, so that different service data of the terminal can enjoy different application services. However, before the routing strategy takes effect, the routing management entity needs to confirm with the user whether to allow this request (that is, the application uses a certain URSP route). If the user permits, the application can use the network, otherwise, the application cannot use the network.
[0074] As an example, if the routing request corresponding to the current service data is permitted by the customer, the terminal can use the current URSP routing rule to route the current application data to PDU session 1, and then route the service data of the application to the corresponding application service 1 through the network interface 1 on the terminal side. Exemplarily, when the service data of the terminal is changed, for example, the terminal can use the routing rule to route the service data of the terminal to PDU session 2, and then route the service data of the application to the corresponding application service 2 through the network interface 2 on the terminal side. It should be understood that the service data of the terminal can also be load-balanced to non-3GPP access without using any existing PDU session, for example, the service data of the application is routed to the corresponding application service 3 through the WIFI network interface.
[0075] like Figure 5 As shown, another data routing method in an embodiment of the present application, the method includes the following steps.
[0076] Step 1: The application requests to use the network.
[0077] Step 2: Select URSP rules according to the application data, and then select the appropriate route through the established URSP rules and send the routing request to the user.
[0078] Step 3: Before using a network under a certain URSP routing rule, the application needs to determine whether the user has agreed to the current routing request. If the user has agreed to the current routing request, jump to step 6; if the user has not agreed to the current routing request before, jump to step 4.
[0079] Step 4: The routing management entity will prompt the user through the terminal interface the current application and the URSP rules it uses.
[0080] Step 5: The user confirms. If the user agrees to the current routing rule, the user's confirmation behavior is recorded and the process goes to step 6. If the user rejects the current routing rule, the routing of the current business data is terminated and the application cannot use the network.
[0081] Step 6: Routing the current business data, the application can use the network.
[0082] URSP routing rules are an important module of 3GPP under 5G networks. Networks using different URSP rules may generate different charges, power consumption, etc. The solution in the embodiment of the present application sends a routing request to the user before applying for the use of the network, and then uses the network after the user's permission. This can avoid unexpected charges for users, unexpected terminal power consumption, and other problems, thereby improving the user experience.
[0083] Figure 6 Taking the way of sending URSP from the network as an example, a configuration process of URSP rules is given. The configuration process of URSP includes the following steps.
[0084] Step 1: When the core network policy control element PCF decides that the URSP policy needs to be updated, the PCF sends a Manage UE Policy Command to the AFM. For example, the PCF may call the Namf_Communication_N1N2MessageTransfer service provided by the AMF and include the subscription permanent identifier (SUPI) and the UE policy container in its message, and include the Manage UE Policy Command in the policy container.
[0085] Step 2: If AMF finds that the UE is reachable and in the CM-idle state, AMF needs to initiate a network-triggered service request (Service Request) process first. For example, AMF can connect to the UE through the interface of the (radio) access network (R)AN. After the UE enters the CM-connected state, AMF can send a NAS downlink direct transfer message (DL NASTransport) to the UE and include the "Manage UE PolicyCommand" in step 1 in the payload container (Payload Container).
[0086] Step 3: The UE updates the URSP policy and sends a NAS uplink direct transfer message (UL NASTransport) to the AMF. For example, the update confirmation "Manage UE Policy Complete" may be included in the payload container (Payload Container).
[0087] Step 4: AMF sends an update confirmation to PCF. For example, the update confirmation "Manage UE Policy Complete" can be transmitted to PCF via Namf_Communication_N1MessageNotify.
[0088] Combination of the above Figures 1 to 6 , describes the method embodiment of the present application in detail, and the following is combined with Figure 7 and Figure 8 , describes the device embodiment of the present application in detail. It should be understood that the description of the method embodiment corresponds to the description of the device embodiment, so the parts not described in detail can refer to the previous method embodiment.
[0089] Figure 7 It is a schematic structural diagram of a data routing device provided in an embodiment of the present application. The device provided in an embodiment of the present application can be set on the UE side, can also be set on the network device side, and can also be set on the communication link between the UE and the network device. Figure 7 The data routing device 700 shown may include a determining unit 720 , a requesting unit 740 , and a first routing unit 760 .
[0090] The determination unit 720 may be used to determine, according to the current service data of the first terminal, a network slice corresponding to the current service data;
[0091] The request unit 740 may be used to send a routing request to the user before routing the current service data;
[0092] The first routing unit 760 may be configured to route the current service data if the user approves the routing request.
[0093] Optionally, the device 700 further includes: a second routing unit 780 configured to terminate routing of the current service data if the user blocks the routing request.
[0094] Optionally, the determination unit 720 is also used to determine the network slice corresponding to the current business data by searching a first routing rule, wherein the first routing rule includes a mapping relationship between the current business data and the network slice.
[0095] Optionally, the requesting unit 740 may also be configured to present the first routing rule to the user.
[0096] Optionally, the first routing rule is a user equipment routing selection policy URSP.
[0097] Optionally, the determination unit 720 can also be used to: in response to a change in the business data of the first terminal, determine the network slice corresponding to the current business data of the first terminal according to the current business data of the first terminal.
[0098] Figure 8 It is a structural diagram of another data routing device provided in an embodiment of the present application. Figure 8 The data routing device 800 shown may include a memory 810 and a processor 820. The memory 810 may be used to store executable code. The processor 820 may be used to execute the executable code stored in the memory 810 to implement the steps in the various methods described above. In some embodiments, the device 800 may also include a network interface 830, and data exchange between the processor 820 and an external device may be implemented through the network interface 830.
[0099] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any other combination. When implemented using software, it can 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 process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (Digital Subscriber Line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server, data center, etc. that contains one or more available media integrated. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital video disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).
[0100] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments of the present application can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.
[0101] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.
[0102] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
[0103] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
[0104] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.
Claims
1. A data routing method, characterized in that: Applied to a first terminal, the method includes: Determine, according to the current service data of the first terminal, a network slice corresponding to the current service data; Before routing the current service data, sending a routing request to the user; If the user approves the routing request, routing the current service data; The sending of the routing request to the user comprises: The routing request is sent to an application of a third-party device, and the interface of the third-party device presents the routing request to the user to confirm the routing request.
2. The method according to claim 1, characterized in that: The method further comprises: If the user blocks the routing request, the routing of the current service data is terminated.
3. The method according to claim 2, wherein determining, according to the current service data of the first terminal, the network slice corresponding to the current service data comprises: By searching the first routing rule, the network slice corresponding to the current business data is determined, wherein the first routing rule includes a mapping relationship between the current business data and the network slice.
4. The method according to claim 3, characterized in that The sending the routing request to the user includes: presenting the first routing rule to the user.
5. The method according to claim 1, characterized in that The determining, according to the current service data of the first terminal, a network slice corresponding to the current service data includes: In response to changes in the business data of the first terminal, the network slice corresponding to the current business data of the first terminal is determined according to the current business data of the first terminal.
6. A data routing device, characterized in that: Applied to a first terminal, the device includes: A determining unit, configured to determine, according to current service data of the first terminal, a network slice corresponding to the current service data; A request unit, used for sending a routing request to a user before routing the current service data; A first routing unit, configured to route the current service data if the user approves the routing request; The request unit is used to: send the routing request to the application of the first terminal, and determine whether the user approves the routing request by the program logic preset in the application; or The routing request is sent to an application of a third-party device, and the interface of the third-party device presents the routing request to the user to confirm the routing request.
7. The device according to claim 6, characterized in that The device also includes: The second routing unit is configured to terminate the routing of the current service data if the user blocks the routing request.
8. The apparatus according to claim 7, wherein the determining unit is further configured to: By searching the first routing rule, the network slice corresponding to the current service data is determined, wherein: The first routing rule includes a mapping relationship between the current service data and the network slice.
9. The device according to claim 8, characterized in that The requesting unit is further configured to present the first routing rule to the user.
10. The device according to claim 6, characterized in that The determining unit is further configured to: In response to changes in the business data of the first terminal, the network slice corresponding to the current business data of the first terminal is determined according to the current business data of the first terminal.
11. A data routing device, characterized in that: The invention comprises a memory and a processor, wherein the memory is used to store a program, and the processor is used to call the program in the memory to execute the method according to any one of claims 1 to 5.
