Methods and equipment for determining business paths
By monitoring service performance and QoS information, and dynamically switching the service path of terminal devices, the problem of improving user experience in 5G systems has been solved, and more efficient network access has been achieved.
Patent Information
- Application Number
- CN201780093731.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2017-08-10
- Publication Date
- 2025-10-31
- Estimated Expiration
- 2037-08-10
AI Technical Summary
In 5G systems, how terminal devices can select appropriate service access paths to improve user experience is an urgent problem to be solved.
By monitoring the service performance information of terminal devices, such as throughput and latency, the service path can be switched; and the target service path can be determined based on the QoS information of the service to be initiated.
It improved the user experience of terminal devices, ensured the efficiency and stability of service paths, and enhanced network performance.
Smart Images

Figure CN110999396B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of communications, and more specifically, to a method and apparatus for determining a service path. Background Technology
[0002] In 5G systems, terminal devices can access services through 3GPP (3rd Generation Partnership Project) networks or non-3GPP networks. Specifically, on the network side, there is a service access network node that is responsible for managing services accessed through 3GPP or non-3GPP networks.
[0003] Therefore, for terminal devices or service access network nodes, how to select the appropriate service access path to improve user experience is an urgent problem to be solved. Summary of the Invention
[0004] In view of this, embodiments of this application provide a method and device for determining a business path, which can improve the user experience.
[0005] Firstly, a method for determining a service path is provided, the method comprising: obtaining service performance information of the current service of a terminal device; and, based on the service performance information, switching the service path of the current service from a first service path to a second service path, wherein the service path is the path through which the terminal device accesses the network.
[0006] In one possible implementation, the service path is the path through which the terminal device accesses the service access management node.
[0007] By monitoring the performance of current services to trigger the switching of service paths for terminal devices accessing the network, the user experience of the terminal can be improved.
[0008] In one possible implementation, the first service path is a non-3GPP access path and the second service path is a 3GPP access path, or the first service path is a 3GPP access path and the second service path is a non-3GPP access path.
[0009] In one possible implementation, the service performance information includes throughput information and / or latency information. The process of switching the service path of the current service from the first service path to the second service path based on the service performance information includes: switching the service path of the current service from the first service path to the second service path when the throughput information and / or the latency information meet the triggering conditions.
[0010] In one possible implementation, the triggering condition is configured by the network device, or is preset in the terminal device using rules agreed upon by the protocol, or is agreed upon by the terminal device through a contract.
[0011] In one possible implementation, switching the service path of the current service from the first service path to the second service path when the throughput information meets the triggering condition includes: if the throughput of the current service is lower than a first threshold, switching the service path of the current service from the first service path to the second service path.
[0012] In one possible implementation, switching the service path of the current service from the first service path to the second service path when the throughput information meets the triggering condition includes: if the rate at which the throughput of the current service decreases is greater than a second threshold, switching the service path of the current service from the first service path to the second service path.
[0013] In one possible implementation, switching the service path of the current service from the first service path to the second service path when the latency information meets the triggering condition includes: if the latency of the current service is greater than a third threshold, switching the service path of the current service from the first service path to the second service path.
[0014] In one possible implementation, switching the service path of the current service from the first service path to the second service path when the latency information meets the triggering condition includes: if the latency jitter of the current service is greater than a fourth threshold, switching the service path of the current service from the first service path to the second service path.
[0015] In one possible implementation, obtaining the service performance information of the current service of the terminal device includes: obtaining the service performance information from the core network device, the terminal device, or the device storing the subscription information of the terminal device.
[0016] In one possible implementation, the method is executed by the terminal device or the service access management node.
[0017] Secondly, a method for determining a service path is provided, the method comprising: determining the target service path for the terminal device to access the network based on the Quality of Service (QoS) information of the service to be initiated by the terminal device; and connecting the terminal device to the network based on the target service path.
[0018] In one possible implementation, the terminal device is connected to the service access management node according to the target service path.
[0019] By determining the service path for a terminal device to access the network using the QoS information of the service to be initiated, the user experience of the terminal can be improved.
[0020] In one possible implementation, the target service path includes a non-3GPP access path or a 3GPP access path.
[0021] In one possible implementation, determining the target service path for the terminal device to access the network based on the Quality of Service (QoS) information of the service to be initiated by the terminal device includes: determining the target service path based on at least one of the following information: QoS identifier, source type, priority, service latency requirement and packet error rate, and a first rule.
[0022] In one possible implementation, the first rule is configured by the network device, or is a rule agreed upon by the protocol and preset in the terminal device, or is agreed upon by the terminal device through a contract.
[0023] In one possible implementation, the first rule is a first correspondence between a QoS identifier and a service path. Determining the target service path based on the QoS identifier and the first rule includes: determining the target service path based on the QoS identifier and the first correspondence.
[0024] In one possible implementation, the first rule is a second correspondence between source type and business path. Determining the target business path based on the source type includes: determining the target business path based on the source type and the second correspondence.
[0025] In one possible implementation, determining the target service path based on the priority and the first rule includes: if the priority is greater than or equal to the first threshold, determining the target service path as a 3GPP access path; if the priority is less than the first threshold, determining the target service path as a non-3GPP access path.
[0026] In one possible implementation, the target service path is determined based on the service latency requirement and a first rule, including: if the service latency requirement is greater than or equal to a first threshold, the target service path is determined to be a non-3GPP access path; if the service latency requirement is less than the first threshold, the target service path is determined to be a 3GPP access path.
[0027] In one possible implementation, determining the target service path based on the packet error rate and a first rule includes: if the packet error rate is greater than or equal to a first threshold, determining the target service path as a non-3GPP access path; if the packet error rate is less than the first threshold, determining the target service path as a 3GPP access path.
[0028] In one possible implementation, the method further includes: obtaining the Quality of Service (QoS) information of the service to be initiated.
[0029] In one possible implementation, obtaining the Quality of Service (QoS) information of the service to be initiated includes obtaining the service performance information from the core network equipment, the terminal equipment, or the equipment storing the subscription information of the terminal equipment.
[0030] In one possible implementation, the method is executed by the terminal device or the service access management node.
[0031] Thirdly, an apparatus for determining a business path is provided for executing the method in the first aspect or any possible implementation thereof. Specifically, the apparatus includes units for executing the method in the first aspect or any possible implementation thereof.
[0032] Fourthly, an apparatus for determining a business path is provided for executing the method in the second aspect or any possible implementation thereof. Specifically, the apparatus includes units for executing the method in the second aspect or any possible implementation thereof.
[0033] Fifthly, a device for determining a service path is provided, the device comprising: a memory, a processor, an input interface, and an output interface. The memory, processor, input interface, and output interface are connected via a bus system. The memory stores instructions, and the processor executes the instructions stored in the memory to perform the methods described in the first aspect or any possible implementation thereof.
[0034] Sixthly, a device for determining a service path is provided, the device comprising: a memory, a processor, an input interface, and an output interface. The memory, processor, input interface, and output interface are connected via a bus system. The memory is used to store instructions, and the processor is used to execute the instructions stored in the memory, for performing the methods described in the second aspect or any possible implementation thereof.
[0035] A seventh aspect provides a computer storage medium for storing computer software instructions for performing the method of the first aspect or any possible implementation thereof, or the method of the second aspect or any possible implementation thereof, comprising a program designed for performing the aspects.
[0036] Eighthly, a computer program product including instructions is provided, which, when run on a computer, causes the computer to perform the method of the first aspect or any optional implementation thereof, or the method of the second aspect or any optional implementation thereof.
[0037] These or other aspects of this application will become more apparent in the following description of the embodiments. Attached Figure Description
[0038] Figure 1 A schematic diagram of an application scenario according to an embodiment of this application is shown.
[0039] Figure 2 A schematic block diagram illustrating a method for determining a business path according to an embodiment of this application is shown.
[0040] Figure 3 Another schematic block diagram of a method for determining a business path according to an embodiment of this application is shown.
[0041] Figure 4 A schematic block diagram of a device for determining a service path according to an embodiment of this application is shown.
[0042] Figure 5 Another schematic block diagram of a device for determining a service path according to an embodiment of this application is shown.
[0043] Figure 6 Another schematic block diagram of a device for determining a service path according to an embodiment of this application is shown.
[0044] Figure 7 Another schematic block diagram of a device for determining a service path according to an embodiment of this application is shown. Detailed Implementation
[0045] The technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings.
[0046] It should be understood that the technical solutions of the embodiments of this application can be applied to various communication systems, such as: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), LTE system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD) system, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication system, New Radio (NR) or future 5G system, etc.
[0047] In particular, the technical solutions of the embodiments of this application can be applied to various communication systems based on non-orthogonal multiple access technologies, such as Sparse Code Multiple Access (SCMA) systems, Low Density Signature (LDS) systems, etc. Of course, SCMA systems and LDS systems can also be called by other names in the field of communication. Furthermore, the technical solutions of the embodiments of this application can be applied to multi-carrier transmission systems that employ non-orthogonal multiple access technologies, such as Orthogonal Frequency Division Multiplexing (OFDM), Filter Bank Multi-Carrier (FBMC), Generalized Frequency Division Multiplexing (GFDM), Filtered-OFDM (F-OFDM) systems, etc.
[0048] The terminal device in this application embodiment can refer to user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device. The access terminal can be a cellular phone, cordless phone, Session Initiation Protocol (SIP) phone, Wireless Local Loop (WLL) station, Personal Digital Assistant (PDA), handheld device with wireless communication capabilities, computing device, or other processing device connected to a wireless modem, in-vehicle device, wearable device, terminal device in future 5G networks, or terminal device in future evolved Public Land Mobile Network (PLMN), etc., and is not limited to this application embodiment.
[0049] The network device in this application embodiment can be a device for communicating with terminal devices. The network device can be a base station (BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA system, an evolved NodeB (eNB or eNodeB) in LTE system, a radio controller in a cloud radio access network (CRAN) scenario, or a relay station, access point, vehicle-mounted device, wearable device, and network device in future 5G networks or future evolved PLMN networks, etc. The embodiments of this application are not limited.
[0050] Figure 1 A schematic block diagram illustrating an application scenario according to an embodiment of this application is shown. For example... Figure 1As shown, a UE can access the Evolved Packet Core (EPC) through either a 3GPP or non-3GPP access system. The EPC mainly includes a Mobility Management Entity (MME), a User Plane Entity (UPE), and a Service Access Management Node. The MME is responsible for control plane mobility management, including user context and mobility state management, allocating temporary user identities, security functions, etc. The UPE is responsible for initiating paging for downlink data in idle states, managing Internet Protocol (IP) bearer parameters, and managing intra-network routing information. The Service Access Management Node is primarily responsible for managing access to either the 3GPP or non-3GPP access systems. 3GPP access systems typically include communication systems such as LTE or WCDMA, while non-3GPP access systems include Wireless Local Area Networks (WLAN), High Rate Packet Data (HRPD), or Worldwide Interoperability for Microwave Access (WiMAX), etc. It should be understood that the 3GPP access system and non-3GPP access system in the embodiments of this application include, but are not limited to, the various communication systems described above. Figure 1 The user subscription server is the main user database for IP Multimedia Subsystem (IMS) network entities that handle calls / sessions. It contains user profiles, performs user authentication and authorization, and provides information about user physical locations. This user subscription server can be, for example, the Home Subscriber Server (HSS) in 3GPP. The Policy and Charging Rules Function (PCRF) is the policy and charging control decision point for service data flows and IP bearer resources. It selects and provides available policy and charging control decisions for the Policy and Charging Enforcement Function (PCEF).
[0051] Figure 2 A schematic block diagram of a method 100 for determining a business path according to an embodiment of this application is shown. Figure 2 As shown, method 100 can be executed by a terminal device or a service access management node, and method 100 includes some or all of the following:
[0052] S110: Obtain the current service performance information of the terminal device.
[0053] S120, based on the service performance information, switch the service path of the current service from the first service path to the second service path, which is the access path for the terminal device to access the network.
[0054] Specifically, in this embodiment, the terminal device or service access management node can periodically obtain the service performance information of the current service. If the terminal device or service access management node determines that certain service performance meets the triggering conditions, then the terminal device or service access management node can directly switch the service path of the current service. For example, if the terminal device is currently accessing the network using LTE, specifically, the terminal device is accessing the service access management node using LTE and is using LTE for service transmission, when the terminal device determines that certain service performance of the current service meets the triggering conditions, such as the latency of the current service being greater than a certain threshold, the terminal device can consider that the performance of the currently accessed network is poor and can choose to directly switch the terminal device to the WLAN system to transmit the currently transmitted service.
[0055] Therefore, the method for determining the service path in this application embodiment can improve the user experience of the terminal by monitoring the service performance of the current service to trigger the switching of the service path for the terminal device to access the network.
[0056] The method described in the above-mentioned embodiments of this application can be executed by a terminal device or by a service access management node. The service access management node can be a functional entity within the core network device or a device outside the core network device. For ease of description, the terminal device will be used as an example to describe this solution in some places below. However, it should be understood that the various solutions described below are also applicable to the service access management node.
[0057] In this embodiment, the first service path is a non-3GPP access path, and the second service path is a 3GPP access path, or the first service path is a 3GPP access path and the second service path is a non-3GPP access path. For example, the first service path can be an LTE network, and the second service path can be a WLAN network. The first and second service paths can also be service paths other than the aforementioned 3GPP and non-3GPP access paths. This embodiment does not constitute a limitation in this regard.
[0058] In this embodiment, the service performance information of the current service may include throughput information and / or latency information, or it may be other service performance information such as the current service rate. Specifically, the terminal device can determine whether these service performance conditions of the current service meet the triggering conditions. If they do, the terminal device is triggered to switch the service path of the current service; otherwise, the terminal device does not need to switch the service path of the current service, that is, it can continue to use the current service path to continue processing the current service.
[0059] It should be understood that the triggering condition for a terminal device to switch service paths can be configured by the network device or can be a rule agreed upon using a protocol, such as the terminal device's factory settings. The triggering condition can also be an agreement between the terminal device and the operator. The embodiments in this application are not limited to these.
[0060] In this embodiment of the application, the step of switching the service path of the current service from the first service path to the second service path when the throughput information meets the triggering condition includes: if the throughput of the current service is lower than a first threshold, switching the service path of the current service from the first service path to the second service path.
[0061] Specifically, network devices can pre-configure a threshold for throughput, and the trigger condition can be configured such that if the obtained throughput is less than the threshold, the current network performance is considered poor, and a service path needs to be switched. In one possible implementation, it can also be configured that if the obtained throughput is greater than or equal to the threshold, the current network performance is considered good, and the current service path can be used to process the current service without switching.
[0062] In this embodiment of the application, the step of switching the service path of the current service from the first service path to the second service path when the throughput information meets the triggering condition includes: if the rate at which the throughput of the current service decreases is greater than a second threshold, the service path of the current service is switched from the first service path to the second service path.
[0063] Specifically, network devices can pre-configure a threshold for the rate of throughput reduction, and the trigger condition can be configured such that if the detected rate of throughput reduction exceeds the threshold, the current network performance is considered poor, and a service path switch is required. In one possible implementation, it can also be configured that if the detected rate of throughput reduction is less than or equal to the threshold, the current network performance is considered good, and the current service path can be used to handle the current service without switching.
[0064] In this embodiment of the application, the step of switching the service path of the current service from the first service path to the second service path when the latency information meets the triggering condition includes: if the latency of the current service is greater than a third threshold, switching the service path of the current service from the first service path to the second service path.
[0065] Specifically, network devices can pre-configure a threshold for service latency, and the trigger condition can be configured such that if the acquired service latency exceeds the threshold, the current network performance is considered poor, and a service path needs to be switched. In one possible implementation, it can also be configured that if the acquired service latency is less than or equal to the threshold, the current network performance is considered good, and the current service path can be used to process the current service without switching.
[0066] It should be understood that the latency configuration threshold for network devices for services can also be the service latency requirement in the Quality of Service (QoS) of the service.
[0067] In one possible implementation, the network device can also configure a threshold for the rate at which service latency increases. This threshold can be configured to trigger a switch if the rate of increase in service latency exceeds this threshold, indicating poor network performance and requiring a service path switch. Alternatively, if the rate of increase in service latency is less than or equal to this threshold, the network performance is considered relatively good, and the current service path can be used to process the current service without switching.
[0068] In this embodiment of the application, the step of switching the service path of the current service from the first service path to the second service path when the latency information meets the triggering condition includes: if the latency jitter of the current service is greater than a fourth threshold, the service path of the current service is switched from the first service path to the second service path.
[0069] Specifically, network devices can pre-configure a threshold for service latency jitter, and configure this threshold as follows: if the acquired service latency jitter exceeds the threshold, the current network performance is considered poor, and a service path switch is required. In one possible implementation, the device can also be configured to consider the current network performance relatively good if the acquired service latency jitter is less than or equal to the threshold, and the current service path can be used to process the current service without switching.
[0070] Similarly, network devices can also pre-configure a threshold for the rate at which latency jitter increases for a service. The triggering conditions are described in the various embodiments above, and for simplicity, will not be repeated here.
[0071] It should be understood that the above description in the embodiments of this application uses various service performances such as throughput size, throughput reduction rate, latency, and latency jitter as examples, and the embodiments of this application should not be limited to these.
[0072] It should also be understood that the above describes the triggering conditions based on the relationship between various service performance and thresholds. The triggering condition can also be a functional relationship. For example, it can be agreed that the triggering condition is that the service throughput increases exponentially, which can trigger the terminal device to switch service paths.
[0073] In this embodiment of the application, obtaining the service performance information of the current service of the terminal device includes: obtaining the service performance information from the core network device, the terminal device, or the device storing the subscription information of the terminal device.
[0074] It should also be understood that the various thresholds mentioned above can be configured by network devices, or they can be values agreed upon using protocols and preset in terminal devices, or they can be agreed upon by the terminal devices and operators in a contract.
[0075] For example, if the method is executed by the terminal device, the core network device or the device storing the terminal device's subscription information can monitor the terminal device's service performance in real time. The terminal device can periodically send request messages to the core network device, requesting the core network device to send the monitored service performance information of the terminal device, or the service performance information of the terminal device obtained from the device storing the terminal device's subscription information, to the terminal device. The terminal device can also monitor its own service performance in real time. As another example, if the method is executed by the service access management node, the service access management node or the terminal device can monitor the terminal device's service performance in real time. Alternatively, a control node in the core network device, such as the MME, can monitor the terminal device's service performance in real time, and the service access management node can send request messages to the terminal device or the MME, requesting that the monitored service performance information of the terminal device be sent to the service access management node.
[0076] In this embodiment of the application, connecting the terminal device to the network according to the target service path includes connecting the terminal device to the service access management node according to the target service path.
[0077] Figure 3 A schematic block diagram of a method 200 for determining a business path according to an embodiment of this application is shown. Figure 3 As shown, method 200 can be executed by a terminal device or a service access management node, and method 200 includes some or all of the following:
[0078] S210: Based on the Quality of Service (QoS) information of the service to be initiated by the terminal device, determine the target service path for the terminal device to access the network.
[0079] S220: Based on the target service path, connect the terminal device to the network.
[0080] Specifically, in this embodiment, the network device can pre-configure different service paths for different QoS values of the same type of QoS information. For example, the network device can pre-configure that latency 1 in the QoS corresponds to service path 1, and latency 2 in the QoS corresponds to service path 2. Before initiating a service, the terminal device or the service access management node can obtain the QoS information of the service to be initiated. The terminal device can determine which service path it corresponds to based on the latency in the QoS information of the service to be initiated. After determining which service path it is, the terminal device can access the network through that service path.
[0081] Therefore, the method for determining the service path in this application embodiment can improve the user experience of the terminal by determining the service path for the terminal device to access the network based on the QoS information of the service to be initiated.
[0082] The method described in the above-mentioned embodiments of this application can be executed by a terminal device or by a service access management node. The service access management node can be a functional entity within the core network device or a device outside the core network device. For ease of description, the terminal device will be used as an example to describe this solution in some places below. However, it should be understood that the various solutions described below are also applicable to the service access management node.
[0083] In this embodiment, the target service path includes a non-3GPP access path or a 3GPP access path. For example, the target service path can be an LTE network or a WLAN network. The target service path can also be a service path other than the aforementioned 3GPP access path and non-3GPP access path. This embodiment does not constitute a limitation in this regard.
[0084] In this embodiment of the application, determining the target service path for the terminal device to access the network based on the Quality of Service (QoS) information of the service to be initiated by the terminal device includes: determining the target service path based on at least one of the following information: QoS identifier, source type, priority, service latency requirement and packet error rate, and a first rule.
[0085] For network services, QoS includes transmission bandwidth, transmission latency, and data packet loss rate. In a network, service quality can be improved by ensuring transmission bandwidth, reducing transmission latency, reducing data packet loss rate, and mitigating latency jitter. QoS may also include availability, throughput, or other parameters. Any parameter used to improve service quality can be used to determine the target service path; this application does not impose any limitations on this.
[0086] Network devices can pre-set rules for various parameters in QoS information. For example, a parameter in the QoS information can be classified according to certain rules, with each category corresponding to a service path. For instance, latency requirements in the QoS information can be divided according to a threshold, with those exceeding the threshold corresponding to 3GPP service paths and those below the threshold corresponding to non-3GPP service paths.
[0087] It should be understood that the rules for setting different parameters in QoS information can be configured by the network, or they can be agreed upon using a protocol and preset in the terminal device, such as the terminal device's factory settings. These rules can also be agreed upon in a contract between the terminal device and the operator. The embodiments in this application are not limited to these.
[0088] In this embodiment of the application, the first rule is a first correspondence between a QoS identifier and a service path. Determining the target service path based on the QoS identifier and the first rule includes: determining the target service path based on the QoS identifier and the first correspondence.
[0089] Specifically, network devices can pre-configure a mapping relationship for QoS identifiers. For example, QoS identifier 1 can be configured to correspond to target service path 1, QoS identifier 2 to target service path 2, and so on. When the terminal device obtains the QoS identifier of the service to be initiated, it can determine the target service path based on this mapping relationship.
[0090] In this embodiment of the application, the first rule is a second correspondence between source type and business path. Determining the target business path based on the source type includes: determining the target business path based on the source type and the second correspondence.
[0091] Specifically, network devices can pre-configure a correspondence for source types. For example, source type 1 can be configured to correspond to target service path 1, source type 2 to target service path 2, and so on. When the terminal device obtains the source type of the service to be initiated, it can determine the target service path based on this correspondence.
[0092] In this embodiment of the application, determining the target service path according to the priority and the first rule includes: if the priority is greater than or equal to the first threshold, determining the target service path as a 3GPP access path; if the priority is less than the first threshold, determining the target service path as a non-3GPP access path.
[0093] Specifically, network devices can pre-configure a threshold for priority. For example, they can configure a target service path 1 with a priority greater than the threshold, a target service path 2 with a priority less than the threshold, and so on. When the terminal device obtains the priority of the service to be initiated, it can determine the target service path based on the relationship between the priority and the threshold.
[0094] In this embodiment of the application, determining the target service path based on the service latency requirement and the first rule includes: if the service latency requirement is greater than or equal to the first threshold, determining the target service path as a non-3GPP access path; if the service latency requirement is less than the first threshold, determining the target service path as a 3GPP access path.
[0095] Specifically, network devices can pre-configure a threshold for service latency requirements. For example, they can configure a target service path 1 for service latency requirements greater than the threshold, a target service path 2 for service latency requirements less than the threshold, and so on. When the terminal device obtains the service latency requirements of the service to be initiated, it can determine the target service path based on the relationship between the service latency requirements and the threshold.
[0096] In this embodiment of the application, determining the target service path based on the data packet error rate and the first rule includes: if the data packet error rate is greater than or equal to the first threshold, determining the target service path as a non-3GPP access path; if the data packet error rate is less than the first threshold, determining the target service path as a 3GPP access path.
[0097] Specifically, network devices can pre-configure a threshold for packet error rate. For example, they can configure a target service path 1 with a packet error rate greater than the threshold, a target service path 2 with a packet error rate less than the threshold, and so on. When the terminal device obtains the packet error rate of the service to be initiated, it can determine the target service path based on the relationship between the packet error rate and the threshold.
[0098] It should be understood that in the embodiments of this application, the above description is based on QoS information such as QoS identifier, source type, priority, service latency requirements and packet error rate, and the embodiments of this application should not be limited to this.
[0099] In this embodiment of the application, obtaining the QoS information of the service to be initiated includes obtaining the service performance information from the core network device, the terminal device, or the device storing the subscription information of the terminal device.
[0100] It should be understood that the various thresholds and corresponding relationships mentioned above can be configured by network devices, or agreed upon by usage protocols and preset in terminal devices, or agreed upon by the terminal devices and operators in a contract.
[0101] It should also be understood that, in the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.
[0102] The method for determining a business path according to embodiments of this application has been described in detail above. The following will combine... Figures 4 to 7 This application describes an apparatus for determining a business path according to embodiments of the present application. The technical features described in the method embodiments are applicable to the following apparatus embodiments.
[0103] Figure 4 A schematic block diagram of a device 300 for determining a service path according to an embodiment of this application is shown. Figure 4 As shown, the device 300 includes:
[0104] The acquisition unit 310 is used to acquire the service performance information of the current service of the terminal device;
[0105] The switching unit 320 is used to switch the service path of the current service from the first service path to the second service path, which is the path through which the terminal device accesses the network.
[0106] Therefore, the device for determining the service path in this application embodiment can improve the user experience of the terminal by monitoring the service performance of the current service to trigger the switching of the service path for the terminal device to access the network.
[0107] In this application embodiment, the first service path is a non-3GPP access path and the second service path is a 3GPP access path, or the first service path is a 3GPP access path and the second service path is a non-3GPP access path.
[0108] In this embodiment of the application, the service performance information includes throughput information and / or latency information. The switching unit is specifically used to switch the service path of the current service from the first service path to the second service path when the throughput information and / or the latency information meet the triggering conditions.
[0109] In this embodiment of the application, the triggering condition is configured by the network device, preset in the terminal device, or agreed upon by the terminal device through a subscription agreement.
[0110] In this embodiment of the application, the switching unit is specifically used to: if the throughput of the current service is lower than a first threshold, switch the service path of the current service from the first service path to the second service path.
[0111] In this embodiment of the application, the switching unit is specifically used to: if the rate at which the throughput of the current service decreases is greater than a second threshold, switch the service path of the current service from the first service path to the second service path.
[0112] In this embodiment of the application, the switching unit is specifically used to: if the latency of the current service is greater than a third threshold, switch the service path of the current service from the first service path to the second service path.
[0113] In this embodiment of the application, the switching unit is specifically used to: if the latency jitter of the current service is greater than the fourth threshold, switch the service path of the current service from the first service path to the second service path.
[0114] In this embodiment of the application, the acquisition unit is specifically used to: acquire the service performance information from the core network device, or the terminal device, or the device storing the subscription information of the terminal device.
[0115] In this embodiment of the application, the device is the terminal device or the service access management node.
[0116] In this embodiment of the application, the service path is the path through which the terminal device accesses the service access management node.
[0117] It should be understood that the device 300 according to the embodiments of this application may correspond to the execution subject in the embodiments of method 100 of this application, and the above and other operations and / or functions of each unit in the device 300 are respectively for implementing Figure 2 The corresponding processes of the device in the method shown will not be elaborated here for the sake of brevity.
[0118] Figure 5 A schematic block diagram of a device 400 for determining a service path according to an embodiment of this application is shown. Figure 5 As shown, the device 400 includes:
[0119] The determining unit 410 is used to determine the target service path for the terminal device to access the network based on the Quality of Service (QoS) information of the service to be initiated by the terminal device.
[0120] Access unit 420 is used to connect the terminal device to the network according to the target service path.
[0121] Therefore, the device for determining the service path in this application embodiment can improve the user experience of the terminal by determining the service path for the terminal device to access the network based on the QoS information of the service to be initiated.
[0122] In this application embodiment, the target service path includes a non-3GPP access path or a 3GPP access path.
[0123] In this embodiment of the application, the determining unit is specifically used to: determine the target service path based on at least one of the following information: QoS identifier, source type, priority, service latency requirement and packet error rate, and a first rule.
[0124] In this embodiment of the application, the first rule is configured by the network device, or preset in the terminal device, or agreed upon by the terminal device through a contract.
[0125] In this embodiment of the application, the first rule is a first correspondence between a QoS identifier and a service path, and the determining unit is specifically used to: determine the target service path based on the QoS identifier and the first correspondence.
[0126] In this embodiment of the application, the first rule is a second correspondence between source type and business path, and the determining unit is specifically used to: determine the target business path according to the source type and the second correspondence.
[0127] In this embodiment of the application, the determining unit is specifically used to: if the priority is greater than or equal to the first threshold, determine the target service path as a 3GPP access path; if the priority is less than the first threshold, determine the target service path as a non-3GPP access path.
[0128] In this embodiment of the application, the determining unit is specifically used to: if the service latency requirement is greater than or equal to a first threshold, determine the target service path as a non-3GPP access path; if the service latency requirement is less than the first threshold, determine the target service path as a 3GPP access path.
[0129] In this embodiment of the application, the determining unit is specifically used to: if the error rate of the data packet is greater than or equal to a first threshold, determine that the target service path is a non-3GPP access path;
[0130] If the error rate of the data packet is less than the first threshold, the target service path is determined to be a 3GPP access path.
[0131] In this embodiment of the application, the device further includes: an acquisition unit, used to acquire the Quality of Service (QoS) information of the service to be initiated.
[0132] In this embodiment of the application, the acquisition unit is specifically used to: acquire the service performance information from the core network device, or the terminal device, or the device storing the subscription information of the terminal device.
[0133] In this embodiment of the application, the device is the terminal device or the service access management node.
[0134] It should be understood that the device 400 according to the embodiments of this application may correspond to the execution subject in the embodiments of method 200 of this application, and the above and other operations and / or functions of each unit in the device 400 are respectively for implementing Figure 3 The corresponding processes of the device in the method shown will not be elaborated here for the sake of brevity.
[0135] like Figure 6 As shown in the illustration, this application embodiment also provides a device 500 for determining a service path, which can be... Figure 4 Device 300, which is capable of performing and Figure 2 The execution entity corresponding to method 100. The device 500 includes: an input interface 510, an output interface 520, a processor 530, and a memory 540. The input interface 510, output interface 520, processor 530, and memory 540 can be connected via a bus system. The memory 540 is used to store programs, instructions, or code. The processor 530 is used to execute the programs, instructions, or code stored in the memory 540 to control the input interface 510 to receive signals, control the output interface 520 to send signals, and complete the operations described in the aforementioned method embodiments.
[0136] Therefore, the device for determining the service path in this application embodiment can improve the user experience of the terminal by monitoring the service performance of the current service to trigger the switching of the service path for the terminal device to access the network.
[0137] It should be understood that, in the embodiments of this application, the processor 530 may be a central processing unit (CPU), or it may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.
[0138] The memory 540 may include read-only memory and random access memory, and provides instructions and data to the processor 530. A portion of the memory 540 may also include non-volatile random access memory. For example, the memory 540 may also store device type information.
[0139] In implementation, each part of the above method can be accomplished through the integrated logic circuits in the hardware of the processor 530 or through software instructions. The content of the method disclosed in the embodiments of this application can be directly manifested as execution by the hardware processor, or as execution by a combination of hardware and software modules in the processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory 540, and the processor 530 reads the information in memory 540 and, in conjunction with its hardware, completes the content of the above method. To avoid repetition, a detailed description is not provided here.
[0140] In one specific implementation, the acquisition unit and switching unit of device 300 can be composed of... Figure 6 The processor 530 is implemented in the system.
[0141] like Figure 7 As shown in the illustration, this application embodiment also provides a device 600 for determining a service path, which can be... Figure 5 Device 400, which is capable of performing and Figure 3 The device corresponding to method 200 includes an input interface 610, an output interface 620, a processor 630, and a memory 640. These components are connected via a bus system. The memory 640 stores programs, instructions, or code. The processor 630 executes the programs, instructions, or code stored in the memory 640 to control the input interface 610 to receive signals, control the output interface 620 to send signals, and complete the operations described in the aforementioned method embodiments.
[0142] Therefore, the terminal device in this application embodiment can improve the user experience of the terminal by determining the service path of the terminal device to access the network by using the QoS information of the service to be initiated.
[0143] It should be understood that, in the embodiments of this application, the processor 630 may be a Central Processing Unit (CPU), or it may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.
[0144] The memory 640 may include read-only memory and random access memory, and provides instructions and data to the processor 630. A portion of the memory 640 may also include non-volatile random access memory. For example, the memory 640 may also store device type information.
[0145] In implementation, each part of the above method can be accomplished through the integrated logic circuits in the hardware of the processor 630 or through software instructions. The content of the method disclosed in the embodiments of this application can be directly manifested as execution by the hardware processor, or as execution by a combination of hardware and software modules in the processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory 640, and the processor 630 reads the information in memory 640 and, in conjunction with its hardware, completes the content of the above method. To avoid repetition, a detailed description is not provided here.
[0146] In one specific implementation, the determining unit, access unit, and acquisition unit in device 400 can be composed of... Figure 7 The processor 630 is implemented in the system.
[0147] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.
[0148] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.
[0149] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.
[0150] The unit described as a separate component may or may not be physically separate. The component shown as a unit may or may not be a physical unit; that is, it may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.
[0151] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.
[0152] If this function is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.
[0153] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.
Claims
1. A method for determining a business path, characterized in that, include: Obtain the current service performance information of the terminal device; Based on the service performance information, the service path of the current service is switched from the first service path to the second service path, where the service path is the path through which the terminal device accesses the network; The service performance information includes throughput information and latency information. The step of switching the service path of the current service from the first service path to the second service path based on the service performance information includes: If the throughput information and the latency information meet the triggering conditions, the service path of the current service will be switched from the first service path to the second service path; When the throughput information and the latency information meet the triggering conditions, switching the service path of the current service from the first service path to the second service path includes: If the throughput of the current service increases exponentially and the rate of increase of the latency jitter of the current service exceeds a threshold, the service path of the current service will be switched from the first service path to the second service path. The acquisition of the current service performance information of the terminal device includes: The service performance information of the current service of the terminal device is obtained from the device storing the subscription information of the terminal device, wherein the service performance information is monitored in real time by the device storing the subscription information of the terminal device.
2. The method according to claim 1, characterized in that, The first service path is a non-3GPP access path, and the second service path is a 3GPP access path, or the first service path is a 3GPP access path and the second service path is a non-3GPP access path.
3. The method according to claim 1, characterized in that, The triggering conditions are configured by the network device, preset on the terminal device, or agreed upon by the terminal device through a subscription agreement.
4. The method according to claim 1 or 2, characterized in that, The method is executed by the terminal device or the service access management node.
5. The method according to claim 1 or 2, characterized in that, The service path is the path through which the terminal device accesses the service access management node.
6. A device for determining a business path, characterized in that, The device includes: The acquisition unit is used to acquire the service performance information of the current service of the terminal device; The switching unit is used to switch the service path of the current service from the first service path to the second service path, wherein the service path is the path through which the terminal device accesses the network; The service performance information includes throughput information and latency information, and the switching unit is specifically used for: If the throughput information and the latency information meet the triggering conditions, the service path of the current service will be switched from the first service path to the second service path; The switching unit is specifically used for: If the throughput of the current service increases exponentially and the rate of increase of the latency jitter of the current service exceeds a threshold, the service path of the current service will be switched from the first service path to the second service path. The acquisition unit is specifically used for: The service performance information of the current service of the terminal device is obtained from the device storing the subscription information of the terminal device, wherein the service performance information is monitored in real time by the device storing the subscription information of the terminal device.
7. The device according to claim 6, characterized in that, The first service path is a non-3GPP access path, and the second service path is a 3GPP access path, or the first service path is a 3GPP access path and the second service path is a non-3GPP access path.
8. The device according to claim 6, characterized in that, The triggering conditions are configured by the network device, preset on the terminal device, or agreed upon by the terminal device through a subscription agreement.
9. The device according to claim 6 or 7, characterized in that, The device is either the terminal device or the service access management node.
10. The device according to claim 6 or 7, characterized in that, The service path is the path through which the terminal device accesses the service access management node.
11. A device for determining a business path, characterized in that, include: The system includes a memory, a processor, an input interface, and an output interface, wherein the memory, the processor, the input interface, and the output interface are connected via a bus system, the memory is used to store instructions, and the processor is used to execute the instructions stored in the memory to perform the method according to any one of claims 1 to 5.
12. A computer storage medium, characterized in that, Used for storing computer software instructions for performing the method of any one of claims 1 to 5, comprising a program designed for performing the method of any one of claims 1 to 5.
Citation Information
Patent Citations
Network switching method and device
CN103974355A
IMS based WWAN-WLAN mobility
US20160021673A1