WO2016023167A1 - 业务路由方法、装置和系统 - Google Patents

业务路由方法、装置和系统 Download PDF

Info

Publication number
WO2016023167A1
WO2016023167A1 PCT/CN2014/084199 CN2014084199W WO2016023167A1 WO 2016023167 A1 WO2016023167 A1 WO 2016023167A1 CN 2014084199 W CN2014084199 W CN 2014084199W WO 2016023167 A1 WO2016023167 A1 WO 2016023167A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
identifier
enabler
path
flow
Prior art date
Application number
PCT/CN2014/084199
Other languages
English (en)
French (fr)
Inventor
杨雪皎
周汉
王岩
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2014/084199 priority Critical patent/WO2016023167A1/zh
Priority to CN201480035955.9A priority patent/CN105531969B/zh
Publication of WO2016023167A1 publication Critical patent/WO2016023167A1/zh

Links

Definitions

  • the present invention relates to the field of communications and, more particularly, to a service routing method, apparatus and system. Background technique
  • ARPU Average Revenue Per User
  • VAS value-added service
  • SE Service Enablers
  • FIG. 1 shows a service-based routing system (referred to as a service routing system), including a Service Traffic Classifier (STC), a Service Path Controller (SPC), a switch, and a number of service enablers SE. , where STC and SE are interconnected through switches, and each switch is controlled by SPC.
  • STC Service Traffic Classifier
  • SPC Service Path Controller
  • SE service enablers SE
  • STC and SE are interconnected through switches, and each switch is controlled by SPC.
  • the STC identifies the type of the service flow, and reports the current service flow information and the corresponding service routing rule information to the SPC, where the service routing rule information is determined by the PCRF. Issued to the STC.
  • the SPC After receiving the service routing rule, the SPC determines the service path for the service flow according to the resource topology (the topology between the switch, the SE, and the STC), that is, determines which switches the service flow packets pass through, and sets the switches on the switches.
  • the forwarding rule of the packet of the service flow the forwarding rule can indicate which port of the switch the packet of the service flow is sent, and which specific SE the next hop passes.
  • the embodiments of the present invention provide a method, a device, and a system for service routing, which can solve congestion, packet loss, and the like caused by overload of a service enabler, and improve user experience, without causing service interruption of the user equipment.
  • a service routing method including: a policy and a charging rule function, a PCRF entity, determining a first service flow that is affected by an overload, where the first service flow is a traffic carried according to the first service path. a service flow of the service enabler; the PCRF entity sends an identifier of the second service path to the service flow classifier STC, so that the STC ends the current session of the first service flow or the first service flow
  • the identifier of the second service path is allocated to the first service flow, so that the new session of the first service flow is enabled by the second service according to the second service path.
  • the first service enabler is different from the second service enabler and has the same function type.
  • the determining, by the PCRF entity, the first service flow that is affected by the overload includes: acquiring an identifier of the first service enabler that is overloaded; The identifier of the enabler acquires an identifier of the first service path that passes through the first service enabler; and determines the first service flow in the service flow that is assigned the identifier of the first service path.
  • the PCRF entity determines the first service flow that is affected by the overload, and includes: receiving, by the service path controller SPC, the first service path An identifier, where the identifier of the first service path is obtained by the SPC according to an identifier of the overloaded first service enabler; determining the first in a service flow to which an identifier of the first service path is allocated business flow.
  • the method before the PCRF entity sends the identifier of the second service path to the STC, the method further includes: sending an event subscription request to the STC, In order for the STC to detect an event result of the first service flow, where the event result includes a current session end of the first service flow or a new session start; a response message sent by the STC when detecting the event result of the first service flow; determining an identifier of the second service path for the first service flow.
  • the determining, by the first service flow, the identifier of the second service path including: according to the first service enabler Determining, by the at least one of the service type of the first service flow, the service routing rule pre-stored by the PCRF, and the current load status of each service enabler, determining a second service that passes the second service enabler path.
  • the determining, by the first service flow, the identifier of the second service path, a request message of the identifier of the second service path, so that the SPC is based on at least one of an identifier of the first service enabler, a service type of the first service flow, and a current load status of each service enabler Determining, by the second service enabler, a second service path; receiving the
  • the identifier of the second service path sent by the SPC is the identifier of the second service path sent by the SPC.
  • the method before the sending an event subscription request to the STC, the method further includes: receiving, by the SPC, an identifier of the first service enabler, An identifier of the second service path that is determined and sent by at least one of a service type of the first service flow and a current load status of each service enabler, where the second service path is enabled by the second service Device.
  • the method before the sending, by the PCRF entity, the identifier of the second service path to the service flow classifier STC, the method further includes: according to the first service enabler Determining, by the at least one of the identifier of the traffic of the first service flow, the service routing rule pre-stored by the PCRF, and the current load state of each service enabler, determining the second pass of the second service enabler Business path.
  • the second aspect provides a service routing method, including: the service flow classifier STC determines a first service flow that is affected by the overload, where the first service flow is a first service that is carried according to the first service path flow.
  • the STC determines a current session state of the first service flow; the STC, when the current session of the first service flow ends or a new session of the first service flow starts, An identifier of the second service path is allocated to the first service flow, so that the new session of the first service flow flows through the second service enabler according to the second service path, where the first service enables
  • the energy device is different from the second service enabler and has the same function type.
  • the STC is determined to be affected by an overload
  • the first service flow includes: obtaining an identifier of the first service path; determining the first service flow in a service flow to which an identifier of the first service path is allocated.
  • the determining the identifier of the first service path includes: acquiring an identifier of the overloaded first service enabler, and according to the The identifier of the first service enabler is obtained by the identifier of the first service path of the first service enabler; or the identifier of the first service path sent by the service path controller SPC, where the first The identifier of the service path is obtained by the SPC according to the identifier of the first service enabler that is overloaded; or the identifier of the first service path sent by the PCRF entity of the policy and charging rule function, where the first service is The identifier of the path is obtained by the PCRF entity according to the identifier of the overloaded first service enabler.
  • the method before the determining, by the STC, the current session state of the first service flow, the method further includes: receiving the second service path sent by the PCRF The identifier of the second service path, where the PCRF is based on the identifier of the first service enabler, the service type of the first service flow, the service routing rule pre-stored by the PCRF, and each service At least one of the current load states of the energy device determines that the second service path passes the second service enabler.
  • the method further includes: sending, to the SPC, a request The request message of the identifier of the second service path, so that the SPC is based on the identifier of the first service enabler, the service type of the first service flow, and the current load status of each service enabler. At least one of determining a second service path that passes through the second service enabler; and receiving an identifier of the second service path sent by the SPC.
  • the method before the determining, by the STC, the current session state of the first service flow, the method further includes: receiving, by the SPC, the second service path An identifier, wherein the identifier of the second service path is determined by the SPC according to the identifier of the first service enabler, the service type of the first service flow, and the current load status of each service enabler. A determining that the second service path passes the second service enabler.
  • the third aspect provides a service routing method, including: the service path controller SPC acquires an identifier of the overloaded first service enabler; and the SPC obtains the identifier according to the identifier of the first service enabler.
  • the rule function PCRF entity or the service flow classifier STC sends the identifier of the first service path, so that the PCRF entity or the STC determines the first service flow to which the identifier of the first service path is allocated, where the first service flow Flowing the service flow of the first service enabler according to the first service path; and the SPC is configured according to the identifier of the first service enabler, the service type of the first service flow, and each service Determining, by at least one of a current load state of the energy device, an identity of a second service path through the second service enabler, wherein the first service enabler is different from the second service enabler, and The SPC sends the identifier
  • the method before the sending, by the SPC, the identifier of the second service path to the PCRF entity or the STC, the method further includes: receiving the PCRF entity or sending the STC A request message for requesting identification of the second service path.
  • a service routing apparatus including: a processing unit, configured to determine a first service flow that is affected by an overload, where the first service flow is a first service that is carried according to the first service path flow And a sending unit, configured to send an identifier of the second service path to the service flow classifier STC, so that the STC ends in the current session of the first service flow or the new service flow
  • the identifier of the second service path is allocated to the first service flow, so that the new session of the first service flow flows through the second service enabler according to the second service path.
  • the first service enabler is different from the second service enabler and has the same function type.
  • the processing unit is specifically configured to: obtain an identifier of the first service enabler that is overloaded; and obtain a pass through the identifier of the first service enabler. Determining an identifier of the first service path of the first service enabler; determining the first service flow in the service flow to which the identifier of the first service path is allocated.
  • the device further includes: a receiving unit, where the receiving unit is configured to: receive the identifier of the first service path sent by the service path controller SPC The identifier of the first service path is obtained by the SPC according to the identifier of the first service enabler that is overloaded; the processing unit is further configured to: the service that is assigned the identifier of the first service path The first service flow is determined in the flow.
  • the sending unit is further configured to: send an event subscription request to the STC, so that the STC detects an event of the first service flow.
  • the receiving unit is further configured to: receive, when the STC detects the event result of the first service flow, The sending response message; the processing unit is further configured to: determine an identifier of the second service path for the first service flow.
  • the processing unit is specifically configured to: according to the identifier of the first service enabler, the service type of the first service flow, Determining, by the device, at least one of a service routing rule pre-stored and a current load status of each service enabler, a second service path that passes through the second service enabler.
  • the sending unit is specifically configured to: send, to the SPC, a request message for requesting an identifier of the second service path, so that Determining, by the SPC, that the second service enabler passes the identifier of the first service enabler, the service type of the first service flow, and the current load status of each service enabler.
  • a second service path the receiving unit is specifically configured to receive an identifier of the second service path sent by the SPC.
  • the receiving unit is specifically configured to: receive, according to the identifier of the first service enabler, the first service flow, by the SPC An identification of the second service path determined and transmitted by at least one of a service type and a current load status of each service enabler, wherein the second service path passes the second service enabler.
  • the processing unit is further configured to: determine, according to the identifier of the first service enabler, the service type of the first service flow, Determining, by the PCRF, at least one of a service routing rule pre-stored and a current load state of each service enabler, determining a second service path that passes through the second service enabler.
  • a service routing apparatus including: a processing unit, configured to determine a first service flow that is affected by an overload, where the first service flow is a first service that is carried according to the first service path flow
  • the processing unit determines a current session state of the first service flow; when the current session of the first service flow ends or a new session of the first service flow starts, the processing unit Assigning an identifier of the second service path to the first service flow, so that the new session of the first service flow flows through the second service enabler according to the second service path, where The first service enabler is different from the second service enabler and has the same function type.
  • the processing unit is specifically configured to: obtain an identifier of the first service path, and determine the service flow in the service flow with the identifier of the first service path The first business flow.
  • the device further includes a receiving unit, where the processing unit is specifically configured to: obtain an identifier of the overloaded first service enabler, and Obtaining, by the identifier of the first service enabler, an identifier of the first service path that is sent by the first service enabler; or the receiving unit is configured to receive the first service path that is sent by the service path controller SPC The identifier of the first service path is obtained by the SPC according to the identifier of the overloaded first service enabler; or the receiving unit is configured to receive a policy and charging rule function sent by the PCRF entity An identifier of the first service path, where the identifier of the first service path is obtained by the PCRF entity according to the identifier of the first service enabler that is overloaded.
  • the receiving unit is further configured to: receive an identifier of the second service path that is sent by the PCRF, where the second service path is Identifying, by the PCRF, at least one of an identifier of the first service enabler, a service type of the first service flow, a service route rule pre-stored by the PCRF, and a current load state of each service enabler It is determined that the second service path passes the second service enabler.
  • the device further includes: a sending unit, where the sending unit is configured to: send, to the SPC, an identifier for requesting the second service path a request message, so that the SPC determines, according to at least one of an identifier of the first service enabler, a service type of the first service flow, and a current load status of each service enabler, The second service path of the second service enabler; the receiving unit is further configured to receive the identifier of the second service path sent by the SPC.
  • a sending unit is configured to: send, to the SPC, an identifier for requesting the second service path a request message, so that the SPC determines, according to at least one of an identifier of the first service enabler, a service type of the first service flow, and a current load status of each service enabler, The second service path of the second service enabler; the receiving unit is further configured to receive the identifier of the second service path sent by the SPC.
  • the receiving unit is further configured to: receive an identifier of the second service path that is sent by the SPC, where the second service path is The identifier is determined by the SPC according to at least one of an identifier of the first service enabler, a service type of the first service flow, and a current load status of each service enabler, where the second service path passes The second service enabler.
  • the sixth aspect provides a service routing apparatus, including: a processing unit, configured to acquire an identifier of an overloaded first service enabler; and the processing unit obtains, according to the identifier of the first service enabler, The identifier of the first service path of the first service enabler; the sending unit, used to the policy And the charging rule function PCRF entity or the service flow classifier STC sends the identifier of the first service path, so that the PCRF entity or the STC determines the first service flow to which the identifier of the first service path is allocated, where the a service flow is a service flow of the first service enabler that is carried according to the first service path; and the processing unit is configured according to the identifier of the first service enabler, the service type of the first service flow, And determining, by the at least one of the current load states of the service enablers, an identifier of the second service path that passes the second service enabler, where the first service enabler and the second service enabler Differentiated and functionally the same; the sending unit sends
  • the device further includes: a receiving unit, where the receiving unit is configured to: receive, by the PCRF entity, or the STC, for requesting the second service path The identified request message.
  • a service routing apparatus including a memory, a processor, and a transmitting circuit, where the memory stores an instruction that causes the processor to: determine a first service flow that is affected by the overload, where the first service flow is Traffic flowing through the first service enabler carried by the first service path; transmitting, by the transmitting circuit, an identifier of the second service path to the service flow classifier STC, so that the STC is in the first service flow
  • the identifier of the second service path is allocated to the first service flow, so that the new session of the first service flow is as described
  • the second service path flows through the second service enabler, wherein the first service enabler is different from the second service enabler and has the same function type.
  • the processor is specifically configured to obtain an identifier of the overloaded first service enabler, and obtain, according to the identifier of the first service enabler, An identifier of a first service path of the first service enabler; determining the first service flow in a service flow to which the identity of the first service path is allocated.
  • the service routing device further includes a receiving circuit, where the processor is specifically configured to: receive, by using the receiving circuit, a service path controller SPC The identifier of the first service path, where the identifier of the first service path is obtained by the SPC according to the identifier of the first service enabler that is overloaded; and the service that is assigned the identifier of the first service path The first service flow is determined in the flow.
  • the processor is further configured to: send, by using the sending circuit, an event subscription request to the STC, so that the STC detects the An event result of a service flow, wherein the event result includes a current session end of the first service flow or a new session start; receiving, by the receiving circuit, the event that the STC is detecting the first service flow a response message sent as a result; determining an identity of the second service path for the first traffic flow
  • the processor is further configured to: according to the identifier of the first service enabler, the service type of the first service flow, A second service path that passes through the second service enabler is determined by at least one of a service routing rule pre-stored by the PCRF and a current load status of each service enabler.
  • the processor is further configured to: send, by using the sending unit, a request for requesting the identifier of the second service path to the SPC a message, so that the SPC determines to pass the second according to at least one of an identifier of the first service enabler, a service type of the first service flow, and a current load status of each service enabler. a second service path of the service enabler; receiving, by the receiving unit, an identifier of the second service path sent by the SPC.
  • the receiving circuit is further configured to: receive, by the SPC, an identifier of the first service enabler, the first service flow, An identification of the second service path determined and transmitted by at least one of a service type and a current load status of each service enabler, wherein the second service path passes the second service enabler.
  • the processor is further configured to: determine, according to the identifier of the first service enabler, the service type of the first service flow, Determining, by the PCRF, at least one of a service routing rule pre-stored and a current load state of each service enabler, determining a second service path that passes through the second service enabler.
  • a service routing apparatus including a memory, a processor, and an instruction that causes the processor to: determine a first service flow that is affected by the overload, where the first service flow is according to the first The service path flows through the service flow of the first service enabler; the current session state of the first service flow is determined; the current session of the first service flow ends or a new session of the first service flow begins Assigning, to the first service flow, an identifier of the second service path, so that the new session of the first service flow flows through the second service enabler according to the second service path, where The first service enabler is different from the second service enabler and The energy type is the same.
  • the processor is specifically configured to: obtain an identifier of the first service path; determine the service flow in the service flow with the identifier of the first service path The first business flow.
  • the service routing device further includes a receiving circuit, where the processor is specifically configured to: obtain an identifier of the overloaded first service enabler And obtaining, according to the identifier of the first service enabler, an identifier of the first service path that passes the first service enabler; or receiving, by the receiving circuit, the first service sent by the service path controller SPC An identifier of the path, where the identifier of the first service path is obtained by the SPC according to the identifier of the first service enabler that is overloaded, or is received by the receiving circuit to receive a policy and charging rule function sent by the PCRF entity. An identifier of the first service path, where the identifier of the first service path is obtained by the PCRF entity according to the identifier of the first service enabler that is overloaded.
  • the receiving circuit is further configured to: receive an identifier of the second service path that is sent by the PCRF, where the second service path is Identifying, by the PCRF, at least one of an identifier of the first service enabler, a service type of the first service flow, a service route rule pre-stored by the PCRF, and a current load state of each service enabler It is determined that the second service path passes the second service enabler.
  • the service routing device further includes a transmitting circuit, where the transmitting circuit is configured to: send, to the SPC, a request for requesting the second service path And the identified request message, so that the SPC determines, according to at least one of an identifier of the first service enabler, a service type of the first service flow, and a current load status of each service enabler. a second service path of the second service enabler; the receiving circuit is further configured to receive an identifier of the second service path sent by the SPC.
  • the receiving circuit is further configured to: receive an identifier of the second service path that is sent by the SPC, where the second service path is The identifier is determined by the SPC according to at least one of an identifier of the first service enabler, a service type of the first service flow, and a current load status of each service enabler, where the second service path passes The second service enabler.
  • a ninth aspect provides a service routing apparatus, including a memory, a processor, and a transmitting circuit, where the memory stores an instruction that causes the processor to: obtain an overloaded first service enabler Identifying, according to the identifier of the first service enabler, an identifier of the first service path that passes the first service enabler; and using the transmit circuit to the policy and charging rule function, the PCRF entity or the service flow classifier
  • the STC sends the identifier of the first service path, so that the PCRF entity or the STC determines the first service flow to which the identifier of the first service path is allocated, where the first service flow is carried according to the flow of the first service path.
  • a traffic flow of the first service enabler and according to at least one of an identifier of the first service enabler, a service type of the first service flow, and a current load state of each service enabler, Determining, by the second service enabler, the identifier of the second service path, where the first service enabler is different from the second service enabler and has the same function;
  • the STC allocates the identifier of the second service path to the first service flow, so that the first The new traffic flow in accordance with said second session traffic path passing through the second service enabler.
  • the service routing device further includes a receiving circuit, where the receiving circuit is configured to: receive, by the PCRF entity, or the STC, to request the second service The request message for the identity of the path.
  • the embodiment determines whether to migrate the service flow of the first service enabler to the second by determining the current session state of the service flow flowing through the first service enabler.
  • the service enabler can ensure the uninterrupted user service while improving the overload of the service enabler, thereby improving the user experience.
  • Figure 1 is a schematic block diagram of a service routing system.
  • FIG. 2 is a flow chart of a service routing method according to an embodiment of the present invention.
  • FIG. 3 is an interaction diagram of a service routing system in accordance with an embodiment of the present invention.
  • FIG. 4 is an interaction diagram of a service routing system according to another embodiment of the present invention.
  • FIG. 5 is an interaction diagram of a service routing system according to another embodiment of the present invention.
  • 6 is an interaction diagram of a service routing system according to another embodiment of the present invention.
  • FIG. 7 is a flow chart of a service routing method according to an embodiment of the present invention.
  • FIG. 8 is an interaction diagram of a service routing system according to an embodiment of the present invention.
  • FIG. 9 is an interaction diagram of a service routing system according to another embodiment of the present invention.
  • FIG. 10 is an interaction diagram of a service routing system according to another embodiment of the present invention.
  • FIG 11 is a schematic block diagram of a Service Routing Device (PCRF) in accordance with one embodiment of the present invention.
  • PCRF Service Routing Device
  • FIG 12 is a schematic block diagram of a Service Routing Device (STC) in accordance with one embodiment of the present invention.
  • STC Service Routing Device
  • FIG. 13 is a schematic block diagram of a Service Routing Device (SPC) in accordance with one embodiment of the present invention.
  • SPC Service Routing Device
  • FIG 14 is a schematic block diagram of a Service Routing Apparatus (PCRF) in accordance with another embodiment of the present invention.
  • PCRF Service Routing Apparatus
  • FIG. 15 is a schematic block diagram of a Service Routing Apparatus (STC) in accordance with another embodiment of the present invention.
  • STC Service Routing Apparatus
  • FIG 16 is a schematic block diagram of a Service Routing Device (SPC) in accordance with another embodiment of the present invention. detailed description
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • FIG. 1 is a schematic block diagram of a service routing system.
  • the service routing system may include a Policy and Charging Rules Function (PCRF), a Service Traffic Classifier (STC), and a Service Path Controller (SPC). , SE Manager (SE Manager), Service Enabler Monitor (SE Monitor), at least one Switching Device (Switch), and n SE servers.
  • the n SE servers are divided into at least one service enabler pool (SE pool) or value added service service pool (VAS Pool) according to functions, for example, SE1 and SE2 belong to the first SE Pool l, SE a, SE b and SE c belongs to the second SE Pool 2.
  • SE1 and SE2 belong to the first SE Pool l
  • SE a, SE b and SE c belongs to the second SE Pool 2.
  • the service enabler SE may refer to a network element capable of providing value-added services, for example, may be video optimization. , firewall, traffic compressor, network (web) buffer, deep message probe or Hypertext Transfer Protocol (HTTP) header enhancer.
  • HTTP Hypertext Transfer Protocol
  • the STC has the function of detecting/recognizing the service flow, and can detect/identify the service type of the service flow, and perform the encapsulation operation on the data in the service flow after obtaining the service path identifier corresponding to the service flow, so that the service flow follows the service.
  • the path is processed.
  • the SPC has the function of selecting a service path, and can determine one or more SEs that specifically process the service flow according to the function type, load status, and network status of each SE.
  • the SE Manager has the ability to manage individual SEs and obtain information such as the SE's network topology.
  • the SE Monitor can monitor the load status of each SE and whether or not a fault has occurred.
  • the foregoing service flow may be an uplink service flow or a downlink service flow, which is not limited in this embodiment of the present invention.
  • PCRF and STC have a connection relationship with at least one of SPC, SE Monitor and SE Manage.
  • PCRF can be connected with any one of SPC, SE Monitor and SE Manage, SPC, SE Monitor and SE Manage.
  • the interconnection between the three allows the PCRF to interact with any of the three network elements.
  • the STC can also interact with SPC, SE Monitor and SE Manage via PCRF; similarly, STC can also interact with SPC, The SE Monitor and SE Manage have a connection relationship, so that the STC and PCRF can interact with SPC, SE Monitor and SE Manage.
  • connection manner in the embodiment of the present invention is not limited thereto.
  • information about the SE load, configuration, weight, etc. stored or acquired by the SPC, SE Monitor, and SE Manage can be sent to the PCRF and STC-sides, so that the PCRF and the STC can load, configure, and weight according to the SE.
  • the information is used to determine and allocate a specific service path identifier for the service flow of the user equipment UE.
  • the SPC can also obtain the service flow information about the UE from the PCRF and the STC side through the connection relationship with the PCRF and the STC, so that the SPC It is also possible to determine and assign a specific service path identifier for the service flow of the UE.
  • the PCRF is configured with a service routing policy and a weight of each SE in the SE pool, where the weight of each SE is mainly related to the processing capability of each SE, and the SE with a higher processing capability has a higher weight value, and correspondingly, SEs with lower processing power have lower weight values.
  • the service flow may be preferentially assigned to the SE with a higher weight according to the weighted round-robin Scheduling or other equalization algorithm, where the weight of each SE may be configured and processed according to the SE.
  • the specific service is pre-configured at the PCRF or SE Manager or SPC and is obtained by the PCRF from the PCRF local or SE Manager/SPC at the time of the call.
  • SE Manage and SE Monitor can be deployed separately or in combination, mainly for monitoring, configuring and managing each SE.
  • the PCRF can establish one or more SE pools according to the service type of the UE and the weight of each SE when establishing an Internet Protocol (IP) connection access network (IP-CAN) session for the UE.
  • IP Internet Protocol
  • IP-CAN Internet Protocol connection access network
  • the UE selects one or a series of SEs for the UE, and assigns a service path identifier to the UE, and then the PCRF sends the service path identifier to the SPC along with the identifier (Identification, ID) of one or a series of SEs on the service path.
  • IP Internet Protocol
  • IP-CAN Internet Protocol connection access network
  • the SE ID may be pre-configured in a database at the PCRF, or may be obtained from an SE Manager or an SPC, and the SE ID may be an IP address of the SE, a Uniform Resource Locator (URL), or other custom identifier.
  • 1-1 may be used to indicate SE1 in the first SE Pool 1, or 2-b to represent SE b in the second SE Pool 2.
  • the SPC calculates the specific flow table and sends it to the related switch switch according to the service path identifier, so that the related switch can allocate the UE service flow to the one or a series of SEs in order.
  • the STC may also obtain a service routing policy from the PCRF, including the access type of the UE (such as 2G/3G/4G access), the user subscription type of the UE (such as gold, silver, copper, common users), and services.
  • the SE Pool on the service route corresponding to the type (such as video and voice).
  • the service flow of the service type video may need to go through the SE Pool with Web Cache function and have video optimization (Video Optimization). )
  • the function of the SE Pool is a service routing policy from the PCRF, including the access type of the UE (such as 2G/3G/4G access), the user subscription type of the UE (such as gold, silver, copper, common users), and services.
  • the SE Pool on the service route corresponding to the type (such as video and voice).
  • the service flow of the service type video may need to go through the SE Pool with Web Cache function and have video optimization (Video Optimization). )
  • the function of the SE Pool may be used to go through the SE Pool with Web Cache function and have video optimization
  • the STC When the service flow of the UE arrives, the STC needs to select one or a series of SEs for the UE in the required one or more SE pools according to the weight of the SE, and allocate a service path identifier for the service flow of the UE, and then the STC will be the service.
  • the path identifier is sent to the SPC along with the ID of one or a series of SEs on the service path.
  • the ID of the SE may be obtained by the PCRF from the SPC in advance, for example, the IP address and URL of the SE, and may also be exemplarily represented by 1-1 for SE1 in the first SE Pool 1, or 2-b SE b in two SE Pool 2.
  • the SPC calculates the specific flow table and sends it to the related switch according to the service path identifier, so that the related switch can allocate the service flow of the UE to the one or a series of SEs, thereby completing the initial load balancing of allocating the service flow to each SE.
  • . 2 is a flow chart of a service routing method according to an embodiment of the present invention. The method of Figure 2 is performed by a policy and charging rules function PCRF entity.
  • the policy and charging rule function the PCRF entity determines the first service flow that is affected by the overload, where the first service flow is a service flow of the first service enabler that is carried according to the first service path flow; S202, the PCRF entity
  • the service flow classifier STC sends the identifier of the second service path, so that the STC allocates the identifier of the second service path to the first service flow when the current session of the first service flow ends or the new session of the first service flow starts.
  • the new session of the first service flow is caused to flow through the second service enabler according to the second service path, where the first service enabler is different from the second service enabler and the function type is the same.
  • the embodiment determines whether to migrate the service flow of the first service enabler to the second by determining the current session state of the service flow flowing through the first service enabler.
  • the service enabler can ensure the uninterrupted user service while improving the overload of the service enabler, thereby improving the user experience.
  • the first service flow of the UE has a specific service type (ie, a function type), and is used to complete a certain task or request, and the first service flow may be composed of at least one session, that is, constitute a first service flow. Multiple sessions also have the same service type and are used to complete a certain task or request.
  • TCP Transmission Control Protocol
  • the data stream is split into data packets of appropriate length for transmission, and the TCP connection is released when the session ends. Therefore, terminating the service flow in the middle of the session will cause the TCP connection to be interrupted, resulting in service interruption.
  • the determining, by the PCRF entity, the first service flow that is affected by the overload includes: acquiring an identifier of the overloaded first service enabler; acquiring, according to the identifier of the first service enabler, the first service Identification of the first service path of the energy device; determining the first service flow in the service flow to which the identity of the first service path is allocated.
  • the service enabler can perform overload detection by the PCRF entity. Specifically, when the first service enabler occurs, the PCRF can obtain the identifier (SE ID) of the first service enabler.
  • SE ID identifier
  • the SE ID of the first service enabler may be sent to the PCRF after the SE monitor detects that the first service enabler is overloaded, that is, the PCRF may obtain the SE ID of the first service enabler from the SE Monitor.
  • the PCRF may also obtain the identifier of the overloaded first service enabler by sending a request message to the SE Monitor.
  • the identifier of the first service enabler may be an IP address or a URL of the first service enabler, and the present invention is not limited thereto.
  • the identifier of the overload service enabler can also be sent by the SE Manager to the PCRF, and the SE Manager can detect the overload by itself.
  • a service enabler may also obtain the SE ID of the first service enabler from the SE Monitor and send it to the PCRF.
  • the first service is stored between the identifier of the service path and the identifier of the service enabler, because the PCRF device or the STC that initially allocates the service flow allocates the service path identifier for the service flow of the UE.
  • the PCRF may determine the first service flow of the UE affected by the overload according to the identifier of the first service enabler. Specifically, the PCRF may first determine the identifier of the first service path that passes the first service enabler according to the identifier of the first service enabler and the correspondence between the identifier of the service path and the identifier of the service enabler. .
  • the PCRF determines the identifier of the first service flow according to the identifier of the first service path, and the first service flow may be randomly selected by the PCRF among the multiple service flows to which the identifier of the first service path is allocated.
  • the PCRF entity determines the first service flow that is affected by the overload, and includes: receiving an identifier of the first service path sent by the service path controller SPC, where the identifier of the first service path is overloaded by the SPC. The identifier of the first service enabler is obtained; the first service flow is determined in the service flow to which the identifier of the first service path is allocated.
  • the overload detection of the service enabler is completed by the SPC, and the SPC can detect that the first service enabler is overloaded by the SE Monitor/SE Manager, that is, the overload detection process of the service enabler by the SPC may be The acquisition process of the SPC for the identification of the overload service enabler.
  • the SPC can also obtain the identity of the overloaded first service enabler by sending a request message to the SE Monitor/SE Manager.
  • the identifier of the first service path of the first service enabler is determined according to the identifier of the first service enabler, and the identifier of the first service path is sent to the PCRF.
  • the mapping between the identifier of the service path and the identifier of the service enabler passing through the service path is determined by the PCRF device or the STC that initially allocates the service flow to the service flow of the UE.
  • the SFC is sent to the SPC. Therefore, the PCRF device, the STC, or the SPC can determine, by using the foregoing correspondence, which service path identifiers the identifier of the first service enabler corresponds to, that is, which service paths are affected by the overload.
  • the PCRF may be based on the first service path.
  • the identifier of the path determines the first service flow. It should be understood that there may be more than one service path through the first service enabler, and the service flow flowing through the first service enabler according to the service path is a service flow affected by the overload. .
  • the PCRF determines, according to the identifier of the first service path, the first service flow that is affected by the overload, and the first service flow may be randomly selected by the PCRF in the multiple service flows to which the identifier of the first service path is allocated.
  • the method before the PCRF entity sends the identifier of the second service path to the STC, the method further includes: sending an event subscription request to the STC, so that the STC detects an event result of the first service flow, where the event result includes Ending the current session of the first service flow or starting a new session; receiving a response message sent by the STC when detecting the event result of the first service flow; determining an identity of the second service path for the first service flow.
  • the PCRF entity may send an event subscription request for the first service flow to the STC to request the STC to detect the end of the current session of the first service flow or the start of a new session. , responding to the event subscription request.
  • the first service flow of the UE has a specific service type (ie, a function type), and is used to complete a certain task or request.
  • the first service flow may be composed of at least one session, that is, the first service flow is formed. Multiple sessions also have the same service type and are used to complete a certain task or request.
  • Each session starts with establishing a TCP connection between the UE and the server. TCP divides the data stream contained in the session into data packets of appropriate length. For transmission, the TCP connection is released when the session ends. Therefore, terminating the service flow in the middle of the session will cause the TCP connection to be interrupted, resulting in service interruption.
  • the PCRF can be based on application detection control (Application Detection Control,
  • the ADC rule generates the above event subscription request to facilitate the subscription to the start and end of the event of the first service flow from the STC.
  • the PCRF can also perform event subscription for the UE affected by the overload, which is not limited by the present invention.
  • the STC notifies the PCRF of the event by a response message when it detects the end of the current session of the first service flow or the start of a new session.
  • the PCRF may determine a new service path identifier for the first service flow. It should be understood that the PCRF may also determine a new service path identifier for the first service flow at any time during the period before the PCRF prepares to send a new service path identifier to the STC after detecting that the first service enabler is overloaded, the present invention. This is not limited.
  • determining the identifier of the second service path for the first service flow including: according to the identifier of the first service enabler, the service type of the first service flow, the service routing rule pre-stored by the PCRF, and each At least one of the current load states of the service enabler is determined to pass the second The second service path of the service enabler.
  • the PCRF may be based on the identifier of the first service enabler, the service type of the first service flow, and the service routing rule pre-stored by the PCRF. And determining, by the at least one of the current load states of the service enablers, a second service path through the second service enabler.
  • the PCRF may replace the first service enabler in the first service path with the second service enabler to form a second service path.
  • the second service enabler can be a different service enabler that is located in the same SE Pool as the first service enabler, that is, the functions are the same and the individual is different.
  • the second service enabler may also be determined by the PCRF according to the load status of each service enabler. For example, in the SE Pool to which the first service enabler belongs, the service enabler with the lowest current load is determined to be the second service. Enabler. It should be understood that the PCRF may also re-determine the identity of the second service path according to the service routing rule and satisfy the condition that the second service path does not pass the first service enabler.
  • determining, by the first service flow, the identifier of the second service path includes: sending, to the SPC, a request message for requesting the identifier of the second service path, so that the SPC is configured according to the first service enabler. Determining, by at least one of a service type of the first service flow and a current load status of each service enabler, a second service path that passes through the second service enabler; and receiving an identifier of the second service path sent by the SPC .
  • the new service path identifier can be determined by the SPC. Specifically, after receiving the first service path identifier sent by the SPC and determining the first service flow, the PCRF may send a request message to the SPC to request a new service path identifier.
  • the request message may carry the identifier of the first service path or the identifier of the UE corresponding to the first service flow.
  • the SPC After receiving the request message sent by the PCRF, the SPC determines a new service path identifier (ie, the identifier of the second service path) for the first service flow, and the method for determining the second service path identifier may refer to the foregoing embodiment, where Narration. After determining the identifier of the second service path, the SPC sends it to the PCRF, so that the PCRF sends the identifier of the second service path to the STC, and the STC applies the identifier of the second service path.
  • a new service path identifier ie, the identifier of the second service path
  • the method before sending the event subscription request to the STC, the method further includes: receiving the SPC according to the identifier of the first service enabler, the service type of the first service flow, and the current load status of each service enabler. At least one identifier of the second service path determined and transmitted, wherein the second service path passes through the second service enabler.
  • the SPC may determine, according to at least one of the identifier of the first service enabler, the service type of the first service flow, and the current load status of each service enabler, the second service that passes the second service enabler. path.
  • the SPC may replace the first service enabler in the first service path with the second service enabler to form a second service path.
  • the second service enabler may be a different service enabler that is located in the same SE Pool as the first service enabler, that is, the functions are the same and the individuals are different.
  • the second service enabler may be determined by the SPC according to the load status of each service enabler. For example, the service enabler with the lowest load is determined to be the second service in the SE Pool to which the first service enabler belongs. Enabler. It should be understood that the SPC may also re-determine the identifier of the second service path according to the service routing rule sent by the PCRF, and satisfy the condition that the second service path does not pass the first service enabler.
  • the method before the sending, by the PCRF entity, the identifier of the second service path to the service flow classifier STC, the method further includes: according to the identifier of the first service enabler, the service type of the first service flow, and the pre-stored by the PCRF The at least one of the service routing rule and the current load status of each service enabler determines a second service path through the second service enabler.
  • the identifier of the second service path may be directly determined for the first service flow, and the identifier of the second service path is sent to At the STC, the STC determines the identity of the second application service path according to the session state of the first service flow.
  • the embodiment of the present invention determines, by using the PCRF, the first service flow that is affected by the overload of the first service enabler, and determines or acquires the second service path that does not pass the first service enabler, and sends the identifier of the second service path.
  • the STC is caused to assign the identity of the second service path to the first service flow when the current session of the first service flow ends or a new session of the first service flow begins. Therefore, the first service flow may change the path during the intermittent session, and flow through the second service enabler according to the second service path, to avoid continuing to be affected by the overload of the first service enabler, and aggravating the overloaded first service enabler.
  • Load In other words, when the overloaded service enabler reduces the load pressure, the continuity of the service can be ensured, and packet loss, service interruption, and the like are not caused, and the user experience is improved.
  • FIG. 3 is an interaction diagram of a service routing method according to an embodiment of the present invention.
  • the embodiment shown in Figure 3 can be used as one or more embodiments of the embodiment of Figure 2.
  • the implementation is mainly performed by the PCRF entity and the STC, and the service initiator is overloaded by the PCRF, and the new service path identifier is determined by the PCRF. specifically:
  • the PCRF entity performs an overload detection on the service enabler.
  • the PCRF entity can perform overload detection on the service enabler.
  • the PCRF can obtain the identifier (SE ID) of the first service enabler.
  • SE ID the identifier of the first service enabler
  • the identifier of the first service enabler may be sent to the PCRF after the SE monitor detects that the first service enabler is overloaded, that is, the PCRF is enabled for the service.
  • the overload detection process of the device may be an acquisition process of the identifier of the overload service enabler by the PCRF.
  • the PCRF can also obtain the identifier of the overloaded first service enabler by sending a request message to the SE Monitor.
  • the identity of the overload service enabler can also be sent to the PCRF through the SE Manager.
  • the identifier of the first service enabler may be an IP address or a URL of the first service enabler, and the present invention is not limited thereto.
  • the PCRF determines a first service flow that is affected by the overload.
  • the first service is stored between the identifier of the service path and the identifier of the service enabler, because the PCRF device or the STC that initially allocates the service flow allocates the service path identifier for the service flow of the UE.
  • the PCRF may determine the first service flow of the UE affected by the overload according to the identifier of the first service enabler.
  • the PCRF may first determine the identifier of the first service path that passes the first service enabler according to the identifier of the first service enabler and the correspondence between the identifier of the service path and the identifier of the service enabler. . It should be understood that there may be more than one service path through the first service enabler, and the service flow flowing through the first service enabler according to these service paths is a service flow affected by the overload.
  • the PCRF determines the identifier of the first service flow according to the identifier of the first service path, where the first service flow may be randomly selected by the PCRF in multiple service flows to which the identifier of the first service path is allocated.
  • the above process uses the first service flow as the description subject.
  • the PCRF may be randomly selected to be overloaded when performing load redistribution.
  • the service flow is redistributed by the load, and the service flow that is affected by the overload is randomly selected to perform load redistribution.
  • the present invention is not limited thereto.
  • the PCRF may determine the ID of the UE corresponding to the service flow of the identifier of the first service path, and the subsequent operation is performed for the service flow of the UE.
  • the UE may have multiple service flows passing through the first service enabler. That is to say, the PCRF may perform the traffic redistribution of the overloaded SE, or may be performed by using the UE as the granularity, and the present invention is not limited thereto.
  • the PCRF sends an event subscription request to the STC.
  • the PCRF entity may send an event subscription request for the first service flow to the STC to request the STC to detect the end of the current session of the first service flow or the start of a new session. , responding to the event subscription request.
  • the first service flow of the UE has a specific service type (ie, a function type), and is used to complete a certain task or request.
  • the first service flow may be composed of at least one session, that is, the first service flow is formed. Multiple sessions also have the same service type and are used to complete a certain task or request.
  • Each session starts with establishing a TCP connection between the UE and the server. TCP divides the data stream contained in the session into data packets of appropriate length. For transmission, the TCP connection is released when the session ends. Therefore, terminating the service flow in the middle of the session will cause the TCP connection to be interrupted, resulting in service interruption.
  • the PCRF can be based on application detection control (Application Detection Control,
  • the ADC rule generates the above event subscription request to facilitate the subscription to the start and end of the event of the first service flow from the STC.
  • the PCRF can also perform event subscription for the UE affected by the overload, which is not limited by the present invention.
  • the STC responds to the event subscription request of the PCRF.
  • the STC notifies the PCRF of the event when it detects the end of the current session of the first service flow or the start of a new session. Specifically, after receiving the event subscription request in step S303, the STC starts to perform event result detection for the first service flow. If the first service flow currently has a session in progress, the STC detects the current session when the session ends. The end of the event result informs the PCRF. If the first service flow does not currently have a session in progress, the STC notifies the PCRF of the event result of the start of the new session when the data message of the new session arrives, that is, when the new session starts.
  • the STC may send a Command-Code Request (CCR) message to the PCRF to indicate the result of the above event to notify the PCRF of the end of the current session of the first service flow or the start of a new session.
  • CCR Command-Code Request
  • the PCRF determines a new service path identifier for the first service flow.
  • step S305 can be performed at any time between step S302 and step S306, which is not limited by the present invention.
  • the PCRF determines a new service path identifier (ie, the identifier of the second service path) for the first service flow after receiving the event result sent by the STC.
  • the PCRF may be based on the first service.
  • the second service path of the second service enabler is determined by at least one of an identifier of the enabler, a service type of the first service flow, a service route rule pre-stored by the PCRF, and a current load status of each service enabler.
  • the PCRF may replace the first service enabler in the first service path with the second service enabler to form a second service path.
  • the second service enabler may be a different service enabler that is located in the same SE Pool as the first service enabler, that is, the functions are the same and the individuals are different.
  • the second service enabler may also be determined by the PCRF according to the load status of each service enabler. For example, in the SE Pool to which the first service enabler belongs, the service enabler with the lowest current load is determined to be the second service. Enabler. It should be understood that the PCRF may also re-determine the identity of the second service path according to the service routing rule, and satisfy the condition that the second service path does not pass the first service enabler.
  • Step S305 may also be performed after step S302. That is, after determining the first service flow of the UE affected by the overload, the PCRF may determine the identity of the second service path, and may cache the identifier of the second service path. The PCRF is waiting locally for a call.
  • the PCRF sends a new service path identifier to the STC.
  • the PCRF may initiate a service detection function (Traffic Detection Function) , TDF) sends the identifier of the second service path to the STC by triggering the session modification process.
  • a service detection function Traffic Detection Function
  • the STC After receiving the identifier of the second service path sent by the PCRF, the STC adds a second service path identifier to the first service flow when the STC receives the data packet of the new session of the first service flow, so that the first service flow is performed.
  • the data packet of the new session flows through the second service enabler according to the second service path, and the second service enabler replaces the original first service enabler to process the new session.
  • the STC may change the original first service path identifier to a new second service path identifier to perform a new session of the first service flow. Package.
  • the STC may send a response message to the PCRF.
  • FIG. 4 is an interaction diagram of a service routing method according to an embodiment of the present invention.
  • the embodiment shown in Figure 4 can be used as one or more embodiments of the embodiment of Figure 2.
  • the implementation is mainly performed by the PCRF entity and the STC, and the service initiator is overloaded by the PCRF, and the new service path identifier is determined by the PCRF. specifically:
  • the PCRF entity performs overload detection on the service enabler.
  • the PCRF entity can perform overload detection on the service enabler, for example, in the first industry.
  • the PCRF can obtain the identifier (SE ID) of the first service enabler.
  • SE ID identifier
  • the identifier of the first service enabler may be sent to the PCRF after the SE monitor detects that the first service enabler is overloaded, that is, the PCRF is enabled for the service.
  • the overload detection process of the device may be an acquisition process of the identifier of the overload service enabler by the PCRF.
  • the PCRF can also obtain the identifier of the overloaded first service enabler by sending a request message to the SE Monitor.
  • the identity of the overload service enabler can also be sent to the PCRF through the SE Manager.
  • the identifier of the first service enabler may be an IP address or a URL of the first service enabler, and the present invention is not limited thereto.
  • the PCRF determines a first service flow that is affected by the overload.
  • the first service is stored between the identifier of the service path and the identifier of the service enabler, because the PCRF device or the STC that initially allocates the service flow allocates the service path identifier for the service flow of the UE.
  • the PCRF may determine the first service flow of the UE affected by the overload according to the identifier of the first service enabler.
  • the PCRF may first determine the identifier of the first service path that passes the first service enabler according to the identifier of the first service enabler and the correspondence between the identifier of the service path and the identifier of the service enabler. . It should be understood that there may be more than one service path through the first service enabler, and the service flow flowing through the first service enabler according to these service paths is a service flow affected by the overload.
  • the PCRF determines the identifier of the first service flow according to the identifier of the first service path, where the first service flow may be randomly selected by the PCRF in multiple service flows to which the identifier of the first service path is allocated.
  • the above process uses a single first service flow as the description subject.
  • the PCRF may be randomly selected multiple times during load redistribution.
  • the service flow is subjected to load redistribution, and the traffic flow affected by the overload is randomly selected in batches for load redistribution.
  • the present invention is not limited thereto.
  • the PCRF may determine the ID of the UE corresponding to the service flow of the identifier of the first service path, and the subsequent operation is performed for the service flow of the UE.
  • the UE may have multiple service flows passing through the first service enabler. That is to say, the PCRF may perform the traffic redistribution of the overloaded SE, or may be performed by using the UE as the granularity, and the present invention is not limited thereto.
  • the PCRF determines and sends a new service path identifier to the STC.
  • the PCRF may determine a new service path identifier (ie, the identifier of the second service path) for the first service flow.
  • the PCRF may be configured according to the first service enabler. And determining, by the identifier, the service type of the first service flow, the service routing rule pre-stored by the PCRF, and the current load status of each service enabler, determining a second service path that passes through the second service enabler.
  • the PCRF may replace the first service enabler in the first service path with the second service enabler to form a second service path.
  • the second service enabler can be a different service enabler that is located in the same SE Pool as the first service enabler, that is, the functions are the same and the individual is different.
  • the second service enabler may also be determined by the PCRF according to the load status of each service enabler. For example, in the SE Pool to which the first service enabler belongs, the service enabler with the lowest current load is determined to be the second service. Enabler. It should be understood that the PCRF may also re-determine the identity of the second service path according to the service routing rule and satisfy the condition that the second service path does not pass the first service enabler.
  • the PCRF can directly deliver the identifier to the STC, and the STC determines when to use it.
  • the PCRF sends the identifier of the second service path to the STC
  • the identifier of the first service path or the identifier of the UE corresponding to the first service flow may be sent to the STC, so that the STC can learn the application of the identifier of the second service path.
  • the STC applies a new service path identifier according to the session state of the UE.
  • the STC When receiving the identifier of the second service path sent by the PCRF, the STC determines the current session state of the first service flow, and when the STC detects that the session ends or a new session starts, the second service path is marked for the first service flow.
  • the identifier is such that the data packet of the new session of the first service flow flows through the second service enabler according to the second service path, and the second service enabler replaces the original first service enabler to process the new session.
  • the STC may change the original first service path identifier to a new second service path identifier to perform a new session of the first service flow.
  • Package When receiving the data message of the new session of the first service flow, the STC may change the original first service path identifier to a new second service path identifier to perform a new session of the first service flow.
  • the first service flow of the UE has a specific service type (ie, a function type), and is used to complete a certain task or request.
  • the first service flow may be composed of at least one session, that is, the first service flow is formed. Multiple sessions also have the same service type and are used to complete a certain task or request.
  • Each session starts with establishing a TCP connection between the UE and the server. TCP divides the data stream contained in the session into data packets of appropriate length. For transmission, the TCP connection is released when the session ends. Therefore, terminating the service flow in the middle of the session will cause the TCP connection to be interrupted, resulting in service interruption.
  • the STC may send a response message to the PCRF.
  • FIG. 5 is an interaction diagram of a service routing method according to an embodiment of the present invention.
  • the embodiment shown in Figure 5 can be used as one or more embodiments of the embodiment of Figure 2.
  • the implementation is mainly performed by the PCRF entity, the STC, and the SPC, and the service enabler performs overload detection by the SPC, and the new service path identifier is determined by the SPC. specifically:
  • S501 The SPC performs overload detection on the service enabler.
  • the SPC can perform overload detection of the service enabler. For example, when the first service enabler is overloaded, the SPC can detect the identifier (SE ID) of the first service enabler. Specifically, the SPC may detect that the first service enabler is overloaded by the SE Monitor/SE Manager, that is, the overload detection process of the SPC for the service enabler may be an acquisition process of the SPC for the identifier of the overload service enabler. . In addition, the SPC can also obtain the identity of the overloaded first service enabler by sending a request message to the SE Monitor/SE Manager.
  • SE ID identifier
  • the SPC may detect that the first service enabler is overloaded by the SE Monitor/SE Manager, that is, the overload detection process of the SPC for the service enabler may be an acquisition process of the SPC for the identifier of the overload service enabler.
  • the SPC can also obtain the identity of the overloaded first service enabler by sending a request message to the SE Monitor/SE Manager.
  • an SPC integrated with the service enabler detection function can also perform overload detection by itself.
  • the identifier of the first service enabler may be an IP address or a URL of the first service enabler, and the like.
  • the SPC acquires an identifier of a service path that is affected by the overload.
  • the identifier of the first service path of the first service enabler may be determined according to the identifier of the first service enabler.
  • the PCRF device or the STC that initially allocates the service flow allocates a service path identifier to the service flow of the UE, and the correspondence between the identifier of the service path and the identifier of the service enabler through which the service path passes The relationship is sent to the SPC. Therefore, the PCRF device, the STC, or the SPC can determine, by using the foregoing correspondence, which service path identifiers the identifier of the first service enabler corresponds to, that is, which service paths are affected by the overload. The SPC then sends the identity of the first service path to the PCRF.
  • the PCRF determines a first service flow that is affected by the overload.
  • the PCRF may determine the first service flow according to the identifier of the first service path. It should be understood that the service path of the first service enabler may have more than one, according to the service path.
  • the traffic flowing through the first service enabler is a traffic flow affected by the overload.
  • the PCRF determines, according to the identifier of the first service path, the first service flow that is affected by the overload, and the first service flow may be randomly selected by the PCRF in the multiple service flows to which the identifier of the first service path is allocated. It should be understood that the PCRF may perform the traffic redistribution on the overloaded SE, and may be performed in the granularity of the service flow or in the granularity of the UE.
  • the present invention is not limited thereto.
  • the PCRF sends an event subscription request to the STC.
  • the PCRF entity may send an event subscription request for the first service flow to the STC to request the STC to detect the end of the current session of the first service flow or the start of a new session. , responding to the event subscription request.
  • the PCRF may generate the above event subscription request according to the ADC rules to facilitate the subscription of the start and end of the event of the first service flow from the STC.
  • the PCRF can also perform event subscription for the UE affected by the overload, which is not limited by the present invention.
  • the STC responds to the event subscription request of the PCRF.
  • the STC notifies the PCRF of the event when it detects the end of the current session of the first service flow or the start of a new session. Specifically, after receiving the event subscription request in step S303, the STC starts to perform event result detection for the first service flow. If the first service flow currently has a session in progress, the STC detects the current session when the session ends. The end of the event result informs the PCRF. If the first service flow does not currently have a session in progress, the STC notifies the PCRF of the event result of the start of the new session when the data message of the new session arrives, that is, when the new session starts. Specifically, the STC may send a CCR message indicating the result of the above event to the PCRF to notify the PCRF of the end of the current session of the first service flow or the start of a new session.
  • the PCRF requests a new service path identifier from the SPC.
  • step S506 can be performed at any time between step S503 and step S507, which is not limited by the present invention.
  • the PCRF can send a request message to the SPC to request a new service path identifier.
  • the request message may carry the identifier of the first service path or the identifier of the UE corresponding to the first service flow.
  • the SPC determines and sends a new service path identifier to the PCRF.
  • the SPC After receiving the request message sent by the PCRF, the SPC determines a new service path identifier (ie, the identifier of the second service path) for the first service flow. Specifically, the SPC may be based on the identifier of the first service enabler and the first service. A second service path through the second service enabler is determined by at least one of a traffic type of the flow and a current load status of each service enabler.
  • the SPC may replace the first service enabler in the first service path with the second service enabler to form a second service path.
  • the second service enabler can be the same A service enabler is located in a different service enabler of the same SE Pool, that is, the functions are the same and the individual is different.
  • the second service enabler may be determined by the SPC according to the load status of each service enabler. For example, the service enabler with the lowest load is determined to be the second service in the SE Pool to which the first service enabler belongs. Enabler. It should be understood that the SPC may also re-determine the identifier of the second service path according to the service routing rule sent by the PCRF, and satisfy the condition that the second service path does not pass the first service enabler.
  • the SPC After determining the identity of the second service path, the SPC sends it to the PCRF, so that the PCRF sends the identity of the second service path to the STC.
  • the STC After receiving the identifier of the second service path sent by the PCRF, the STC adds a second service path identifier to the first service flow when the STC receives the data packet of the new session of the first service flow, so that the first service flow is performed.
  • the data packet of the new session flows through the second service enabler according to the second service path, and the second service enabler replaces the original first service enabler to process the new session.
  • the STC may change the original first service path identifier to a new second service path identifier to perform a new session of the first service flow. Package.
  • the STC may send a response message to the PCRF.
  • FIG. 6 is an interaction diagram of a service routing method according to an embodiment of the present invention.
  • the embodiment shown in Figure 6 can be used as one or more embodiments of the embodiment of Figure 2.
  • the implementation is mainly performed by the PCRF entity, the STC, and the SPC, and the service enabler performs overload detection by the SPC, and the new service path identifier is determined by the SPC. specifically:
  • S601 The SPC performs overload detection on the service enabler.
  • the SPC can perform overload detection of the service enabler. For example, when the first service enabler is overloaded, the SPC can detect the identifier (SE ID) of the first service enabler. Specifically, the SPC may detect that the first service enabler is overloaded by the SE Monitor/SE Manager, that is, the overload detection process of the SPC for the service enabler may be an acquisition process of the SPC for the identifier of the overload service enabler. . In addition, the SPC can also obtain the identity of the overloaded first service enabler by sending a request message to the SE Monitor/SE Manager.
  • SE ID identifier
  • the SPC may detect that the first service enabler is overloaded by the SE Monitor/SE Manager, that is, the overload detection process of the SPC for the service enabler may be an acquisition process of the SPC for the identifier of the overload service enabler.
  • the SPC can also obtain the identity of the overloaded first service enabler by sending a request message to the SE Monitor/SE Manager.
  • the SPC integrated with the service enabler detection function can also perform overload detection by itself.
  • the identifier of the first service enabler may be an IP address or a URL of the first service enabler, etc., which is not limited by the present invention.
  • S602. The SPC determines, and sends, to the PCRF, a service path identifier and a new service path identifier that are affected by the overload.
  • the identifier of the first service path of the first service enabler may be determined according to the identifier of the first service enabler.
  • the PCRF device or the STC that initially allocates the service flow allocates a service path identifier to the service flow of the UE, and the correspondence between the identifier of the service path and the identifier of the service enabler through which the service path passes The relationship is sent to the SPC. Therefore, the PCRF device, the STC, or the SPC can determine, by using the foregoing correspondence, which service path identifiers the identifier of the first service enabler corresponds to, that is, which service paths are affected by the overload.
  • the SPC can determine the identifier of the second service path according to the identifier of the first service enabler and the current load status of each service enabler.
  • the SPC may replace the first service enabler in the first service path with the second service enabler to form a second service path.
  • the second service enabler can be a different service enabler that is located in the same SE Pool as the first service enabler, that is, the function is the same and the individual is different.
  • the second service enabler may be determined by the SPC according to the load status of each service enabler. For example, the service enabler with the lowest load is determined to be the second service in the SE Pool to which the first service enabler belongs. Enabler. It should be understood that the SPC may also re-determine the identity of the second service path according to the service routing rule sent by the PCRF, and satisfy the condition that the second service path does not pass the first service enabler.
  • the SPC may send the identity of the first service path and the identity of the second service path to the PCRF.
  • the PCRF determines a first service flow that is affected by the overload.
  • the PCRF may cache the identifier of the second service path in the PCRF for subsequent use, and determine the first according to the identifier of the first service path.
  • the service flow it should be understood that there may be more than one service path through the first service enabler, and the service flow flowing through the first service enabler according to the service path is a service flow affected by the overload.
  • the PCRF determines the first service flow affected by the overload according to the identifier of the first service path, and the first service flow may be randomly selected by the PCRF among the plurality of service flows to which the identifier of the first service path is allocated. It should be understood that the PCRF may perform the traffic redistribution of the overloaded SE, or may be performed by using the UE as the granularity, and the present invention is not limited thereto.
  • the PCRF sends an event subscription request to the STC.
  • the PCRF entity After the PCRF entity determines the first service flow affected by the overload, it can send a pin to the STC.
  • An event subscription request for the first service flow to request the STC to respond to the event subscription request upon detecting the end of the current session of the first service flow or the start of a new session.
  • the PCRF may generate the above event subscription request according to the ADC rules, so as to subscribe to the start and end of the event of the first service flow from the STC.
  • the PCRF can also perform event subscription for the UE affected by the overload, which is not limited by the present invention.
  • the STC responds to the event subscription request of the PCRF.
  • the STC notifies the PCRF of the event when it detects the end of the current session of the first service flow or the start of a new session. Specifically, after receiving the event subscription request in step S303, the STC starts to perform event result detection for the first service flow. If the first service flow currently has a session in progress, the STC detects the current session when the session ends. The end of the event result informs the PCRF. If the first service flow does not currently have a session in progress, the STC notifies the PCRF of the event result of the start of the new session when the data message of the new session arrives, that is, when the new session starts. Specifically, the STC may send a CCR message indicating the result of the above event to the PCRF to notify the PCRF of the end of the current session of the first service flow or the start of a new session.
  • the PCRF sends a new service path identifier to the STC.
  • the PCRF may send the identifier of the second service path buffered in step S603 to the STC.
  • the STC After receiving the identifier of the second service path sent by the PCRF, the STC adds a second service path identifier to the first service flow when the STC receives the data packet of the new session of the first service flow, so that the first service flow is performed.
  • the data packet of the new session flows through the second service enabler according to the second service path, and the second service enabler replaces the original first service enabler to process the new session.
  • the STC may change the original first service path identifier to a new second service path identifier to perform a new session of the first service flow. Package.
  • the STC may send a response message to the PCRF.
  • FIG. 7 is a flow chart of a service routing method according to an embodiment of the present invention. The method of Figure 7 is performed by the traffic classifier STC.
  • the traffic classifier STC determines a first service flow that is affected by the overload, where the first service flow is a service flow of the first service enabler that is carried according to the first service path.
  • the STC determines a current session state of the first service flow. S703. The STC allocates the identifier of the second service path to the first service flow when the current session of the first service flow ends or the new session of the first service flow starts, so that the new session of the first service flow is in accordance with the second service.
  • the path flows through the second service enabler, where the first service enabler is different from the second service enabler and has the same function type.
  • the embodiment determines whether to migrate the service flow of the first service enabler to the second by determining the current session state of the service flow flowing through the first service enabler.
  • the service enabler can ensure the uninterrupted user service while improving the overload of the service enabler, thereby improving the user experience.
  • the first service flow of the UE has a specific service type (ie, a function type), and is used to complete a certain task or request, and the first service flow may be composed of at least one session, that is, constitute a first service flow. Multiple sessions also have the same type of service and are used to complete a certain task or request.
  • Each session starts with a TCP connection between the UE and the server. TCP divides the data stream contained in the session into data of appropriate length. The message is transmitted for transmission, and the TCP connection is released when the session ends. Therefore, terminating the service flow in the middle of the session will cause the TCP connection to be interrupted, resulting in service interruption.
  • the STC determines the first service flow that is affected by the overload, and includes: obtaining an identifier of the first service path; and determining the first service flow in the service flow to which the identifier of the first service path is allocated.
  • the STC can obtain the identifier of the first service path from the PCRF or the SPC, or obtain the identifier of the first service path locally in the STC.
  • the STC can obtain the first service path identifier from the PCRF.
  • the STC can obtain the first service path identifier from the SPC.
  • the STC performs the overload detection, the STC The identity of the first service path can be determined by itself.
  • the STC may determine the first service flow according to the identifier of the first service path.
  • the service path of the first service enabler may have more than one, and the traffic path flows according to the service path.
  • the service flow of the first service enabler is a service flow affected by the overload.
  • the STC determines, according to the identifier of the first service path, the first service flow affected by the overload, and the first service flow may be randomly selected by the STC in the plurality of service flows to which the identifier of the first service path is allocated.
  • determining the identifier of the first service path includes: obtaining an identifier of the overloaded first service enabler, and acquiring, according to the identifier of the first service enabler, the first service enabler The identifier of the first service path; or the identifier of the first service path sent by the service path controller SPC, where the identifier of the first service path is determined by the S PC according to the overloaded first service enabler Or the identifier of the first service path sent by the PCRF entity, and the identifier of the first service path is obtained by the PCRF entity according to the identifier of the overloaded first service enabler.
  • the identifier of the first service enabler may be sent to the STC after the SE Monitor detects that the first service enabler is overloaded, that is, the STC is for the service enabler.
  • the overload detection process may be an acquisition process of the identifier of the overload service enabler by the STC.
  • the STC can also obtain the identity of the overloaded first service enabler by sending a request message to the SE Monitor/SE Manager. It should be understood that the identity of the overload service enabler can also be sent to the STC through the SE Manager.
  • the STC may determine the identifier of the first service path passing the first service enabler according to the identifier of the first service enabler, the identifier of the service path, and the identifier of the service enabler. It should be understood that there may be more than one service path through the first service enabler, and the service flow flowing through the first service enabler according to these service paths is a service flow affected by the overload.
  • the identifier of the first service enablement may be sent by the SE Monitor/SE Manager to the SPC after detecting that the first service enabler is overloaded, that is, the SPC is for the service enabler.
  • the overload detection process may be an acquisition process of the SPC for the identification of the overload service enabler.
  • the SPC can also obtain the identity of the overloaded first service enabler by sending a request message to the SE Monitor/SE Manager. It should be understood that an SPC integrated with a service enabler detection function can also perform overload detection by itself.
  • the SPC may determine the identifier of the first service path that passes the first service enabler according to the identifier of the first service enabler, and send the identifier of the first service path to the STC.
  • the PCRF device or the STC that initially allocates the service flow allocates a service path identifier to the service flow of the UE, and the correspondence between the identifier of the service path and the identifier of the service enabler through which the service path passes The relationship is sent to the SPC, so the PCRF device, the STC, or the SPC can determine, by using the foregoing correspondence, which service path identifiers the identifier of the first service enabler corresponds to, that is, which service paths are affected by the overload.
  • the identifier of the first service enabler may be sent to the PCRF after the SE Monitor detects that the first service enabler is overloaded, that is, the PCRF detects the overload of the service enabler.
  • the process may be an acquisition process of the PCRF for the identification of the overload service enabler.
  • the PCRF can also obtain the identifier of the overloaded first service enabler by sending a request message to the SE Monitor/SE Manager. It should be understood that the identification of the overload service enabler can also It is sent to the PCRF through the SE Manager.
  • the PCRF may determine the identifier of the first service path that passes the first service enabler according to the identifier of the first service enabler, the identifier of the service path, and the identifier of the service enabler. It should be understood that there may be more than one service path through the first service enabler, and the service flow flowing through the first service enabler according to the service path is a service flow affected by the overload.
  • the method before the determining, by the STC, the current session state of the first service flow, the method further includes: receiving an identifier of the second service path sent by the PCRF, where the identifier of the second service path is enabled by the PCRF according to the first service At least one of the identifier of the device, the service type of the first service flow, the service routing rule pre-stored by the PCRF, and the current load state of each service enabler is determined, and the second service path passes through the second service enabler.
  • the PCRF may determine the identifier of the first service flow according to the identifier of the first service path, where the first service flow is It may be that the PCRF is randomly selected among a plurality of service flows to which the identity of the first service path is allocated.
  • the PCRF may determine a new service path identifier (ie, the identifier of the second service path) for the first service flow.
  • the PCRF may be configured according to the first service enabler. And determining, by the identifier, the service type of the first service flow, the service routing rule pre-stored by the PCRF, and the current load status of each service enabler, determining a second service path that passes through the second service enabler.
  • the PCRF may replace the first service enabler in the first service path with the second service enabler to form a second service path.
  • the second service enabler can be a different service enabler that is located in the same SE Pool as the first service enabler, that is, the functions are the same and the individual is different.
  • the second service enabler may also be determined by the PCRF according to the load status of each service enabler. For example, in the SE Pool to which the first service enabler belongs, the service enabler with the lowest current load is determined to be the second service. Enabler. It should be understood that the PCRF may also re-determine the identity of the second service path according to the service routing rule and satisfy the condition that the second service path does not pass the first service enabler. After determining the identifier of the second service path, the PCRF can directly send it to the STC, and the STC determines when to use it.
  • the method further includes: sending, to the SPC, a request message for requesting the identifier of the second service path, so that the SPC is according to the first Determining, by the at least one of the identifier of the service enabler, the service type of the first service flow, and the current load status of each service enabler, the second pass through the second service enabler Service path; receiving the identifier of the second service path sent by the SPC.
  • the STC after receiving the first service path identifier sent by the SPC, the STC determines the current session state of the first service flow, after the current session of the first service flow ends, or a new session. Before starting, the STC sends a request message to the SPC to request a new service path identifier.
  • the request message may carry the identifier of the first service path or the identifier of the UE corresponding to the first service flow.
  • the SPC determines a new service path identifier (ie, the identifier of the second service path) for the first service flow and sends it to the STC.
  • the SPC may determine, according to at least one of the identifier of the first service enabler, the service type of the first service flow, and the current load status of each service enabler, the second service that passes the second service enabler. path.
  • the SPC may replace the first service enabler in the first service path with the second service enabler to form a second service path.
  • the second service enabler can be a different service enabler that is located in the same SE Pool as the first service enabler, that is, the functions are the same and the individual is different.
  • the second service enabler may be determined by the SPC according to the load status of each service enabler.
  • the service enabler with the lowest load is determined to be the second service in the SE Pool to which the first service enabler belongs. Enabler. It should be understood that the SPC may also re-determine the identity of the second service path according to the service routing rule sent by the PCRF, and satisfy the condition that the second service path does not pass the first service enabler.
  • the method before the determining, by the STC, the current session state of the first service flow, the method further includes: receiving an identifier of the second service path sent by the SPC, where the identifier of the second service path is enabled by the SPC according to the first service At least one of the identifier of the device, the service type of the first service flow, and the current load status of each service enabler is determined, and the second service path passes through the second service enabler.
  • the SPC may determine the second service path identifier of the second service enabler when determining the overloaded first service enabler and determining the first service path identifier, and A service path identifier and a second service path identifier are both sent to the STC.
  • the SPC may determine the second service path identifier of the second service enabler when determining the overloaded first service enabler and determining the first service path identifier, and A service path identifier and a second service path identifier are both sent to the STC.
  • the embodiment of the present invention determines, by the STC, the first service flow that is affected by the overload of the first service enabler, determines or acquires the second service path that does not pass the first service enabler, and ends the current session of the first service flow. Or, when the new session of the first service flow starts, the identifier of the second service path is allocated to the first service flow. Therefore, the first service flow can change the path during the interval of the session, and the second service enabler flows according to the second service path, so as to avoid continuing to be affected by the overload of the first service enabler and aggravating the overloaded first service enabler.
  • Load That is, enabling for overloaded services
  • the device can reduce the load pressure and ensure the continuity of the service, and there is no phenomenon such as packet loss and service interruption, and the user experience is improved.
  • FIG. 8 is a flowchart of a service routing method according to an embodiment of the present invention.
  • the embodiment shown in Figure 8 can be used as one or more embodiments of the embodiment of Figure 7. This implementation is mainly performed by the STC.
  • the STC performs overload detection on the service enabler, and the STC determines the new service path identifier. specifically:
  • the STC performs overload detection on the service enabler.
  • the STC can perform overload detection of the service enabler. For example, when the first service enabler is overloaded, the STC can detect the identifier (SE ID) of the first service enabler. Specifically, the STC itself cannot sense the status of the service enabler. The identifier of the first service enabler may be sent to the STC after the SE Monitor detects that the first service enabler is overloaded, that is, the STC is enabled for the service.
  • the overload detection process of the device may be an acquisition process of the identifier of the overload service enabler by the STC.
  • the STC can also obtain the identity of the overloaded first service enabler by sending a request message to the SE Monitor/SE Manager.
  • the identity of the overload service enabler can also be sent to the STC through the SE Manager.
  • the identifier of the first service enabler may be an IP address or a URL of the first service enabler, etc., which is not limited by the present invention.
  • the STC determines a first service flow that is affected by the overload.
  • the STC may determine the first service flow of the UE affected by the overload according to the identifier of the first service enabler.
  • the STC may first determine the identifier of the first service path that passes the first service enabler according to the identifier of the first service enabler and the correspondence between the identifier of the service path and the identifier of the service enabler. . It should be understood that there may be more than one service path through the first service enabler, and the service flow flowing through the first service enabler according to these service paths is a service flow affected by the overload.
  • the STC determines, according to the identifier of the first service path, the first service flow that is affected by the overload, and the first service flow may be randomly selected by the STC in the multiple service flows to which the identifier of the first service path is allocated.
  • the above process uses a single first service flow as the description subject.
  • the STC may randomly select the first service multiple times during load redistribution.
  • the flow is load redistributed, or it can be random batch selection.
  • the present invention does not limit the present invention to load redistribution.
  • the STC may perform the traffic redistribution of the overloaded SE, or may be performed by using the UE as the granularity, and the present invention is not limited thereto.
  • the STC determines a new service path identifier
  • the STC may determine a new service path identifier (ie, an identifier of the second service path) for the first service flow.
  • the STC may be configured according to the first service enabler. And determining, by the identifier, the service type of the first service flow, the service routing rule pre-stored by the PCRF, and the current load status of each service enabler, determining a second service path that passes through the second service enabler.
  • the STC may replace the first service enabler in the first service path with the second service enabler to form a second service path.
  • the second service enabler can be a different service enabler that is located in the same SE Pool as the first service enabler, that is, the functions are the same and the individual is different.
  • the second service enabler may be determined by the STC according to the load status of each service enabler. For example, the service enabler with the lowest load is determined to be the second service in the SE Pool to which the first service enabler belongs. Enabler. It should be understood that the STC may also re-determine the identity of the second service path according to the service routing rule and satisfy the condition that the second service path does not pass the first service enabler.
  • the STC applies a new service path identifier according to the session state of the UE.
  • the STC determines the current session state of the first service flow, and when the STC detects the end of the session or starts a new session, the identifier of the second service path is marked for the first service flow, so that the datagram of the new session of the first service flow is obtained.
  • the text flows through the second service enabler according to the second service path, and the second service enabler replaces the original first service enabler to process the new session.
  • the STC may change the original first service path identifier to a new second service path identifier to perform a new session of the first service flow.
  • FIG. 9 is an interaction diagram of a service routing method according to an embodiment of the present invention.
  • the embodiment shown in Figure 9 can be used as one or more embodiments of the embodiment of Figure 7.
  • the implementation is mainly performed by the STC and the SPC, and the service enabler performs overload detection by the SPC, and the new service path identifier is determined by the SPC.
  • S901 The SPC performs overload detection on the service enabler.
  • the SPC can perform overload detection of the service enabler. For example, when the first service enabler is overloaded, the SPC can detect the identifier (SE ID) of the first service enabler. Specifically, the SPC may detect that the first service enabler is overloaded by the SE Monitor/SE Manager, that is, the overload detection process of the SPC for the service enabler may be an acquisition process of the SPC for the identifier of the overload service enabler. . In addition, the SPC can also obtain the identity of the overloaded first service enabler by sending a request message to the SE Monitor/SE Manager.
  • SE ID identifier
  • the SPC may detect that the first service enabler is overloaded by the SE Monitor/SE Manager, that is, the overload detection process of the SPC for the service enabler may be an acquisition process of the SPC for the identifier of the overload service enabler.
  • the SPC can also obtain the identity of the overloaded first service enabler by sending a request message to the SE Monitor/SE Manager.
  • an SPC integrated with the service enabler detection function can also perform overload detection by itself.
  • the identifier of the first service enabler may be an IP address or a URL of the first service enabler, and the like.
  • the SPC determines the identity of the service path affected by the overload.
  • the identifier of the first service path of the first service enabler may be determined according to the identifier of the first service enabler.
  • the PCRF device or the STC that initially allocates the service flow allocates a service path identifier to the service flow of the UE, and the correspondence between the identifier of the service path and the identifier of the service enabler through which the service path passes The relationship is sent to the SPC. Therefore, the PCRF device, the STC, or the SPC can determine, by using the foregoing correspondence, which service path identifiers the identifier of the first service enabler corresponds to, that is, which service paths are affected by the overload. The SPC then sends the identity of the first service path to the STC.
  • the STC determines the first service flow affected by the overload.
  • the STC may first determine the first service flow according to the identifier of the first service path. It should be understood that there may be more than one service path through the first service enabler, and the service flow flowing through the first service enabler according to the service path is It is a business flow that is affected by overload.
  • the STC determines, according to the identifier of the first service path, the first service flow affected by the overload, and the first service flow may be randomly selected by the STC in the plurality of service flows to which the identifier of the first service path is allocated.
  • the STC may perform the traffic redistribution of the overloaded SE, or may be performed by using the UE as the granularity, and the present invention is not limited thereto.
  • the STC requests a new service path identifier from the SPC according to the session state.
  • the STC determines the current session state of the first traffic flow, and after the current session of the first traffic flow ends, or before the new session begins, the STC sends a request message to the SPC to request a new service path identity.
  • the request message may carry the identifier of the first service path or the identifier of the UE corresponding to the first service flow.
  • S905 the SPC determines and sends a new service path identifier
  • the SPC After receiving the request message sent by the STC, the SPC determines a new service path identifier (ie, the identifier of the second service path) for the first service flow. Specifically, the SPC may be based on the identifier of the first service enabler and the first service. A second service path through the second service enabler is determined by at least one of a traffic type of the flow and a current load status of each service enabler.
  • the SPC may replace the first service enabler in the first service path with the second service enabler to form a second service path.
  • the second service enabler can be a different service enabler that is located in the same SE Pool as the first service enabler, that is, the functions are the same and the individual is different.
  • the second service enabler may be determined by the SPC according to the load status of each service enabler. For example, the service enabler with the lowest load is determined to be the second service in the SE Pool to which the first service enabler belongs. Enabler. It should be understood that the SPC may also re-determine the identity of the second service path according to the service routing rule sent by the PCRF, and satisfy the condition that the second service path does not pass the first service enabler. After determining the identity of the second service path, the SPC sends it to the STC.
  • the STC After receiving the identifier of the second service path sent by the SPC, the STC adds a second service path identifier to the first service flow when the STC receives the data packet of the new session of the first service flow, so that the first service flow is performed.
  • the data packet of the new session flows through the second service enabler according to the second service path, and the second service enabler replaces the original first service enabler to process the new session.
  • the STC may change the original first service path identifier to a new second service path identifier to perform a new session of the first service flow.
  • Package the original first service path identifier to a new second service path identifier to perform a new session of the first service flow.
  • the STC may send a response message to the SPC.
  • FIG. 10 is an interaction diagram of a service routing method according to an embodiment of the present invention.
  • the embodiment shown in Figure 10 can be used as one or more embodiments of the embodiment of Figure 7.
  • the implementation is mainly performed by the STC and the SPC, and the service enabler performs overload detection by the SPC, and the new service path identifier is determined by the SPC. specifically:
  • the SPC performs overload detection on the service enabler.
  • the SPC can perform overload detection of the service enabler. For example, when the first service enabler is overloaded, the SPC can detect the identifier (SE ID) of the first service enabler. Specifically, the SPC can detect that the first service enabler is overloaded by the SE Monitor/SE Manager, that is, The overload detection process of the service enabler by the SPC may be an acquisition process of the identifier of the overload service enabler by the SPC. In addition, the SPC can also obtain the identity of the overloaded first service enabler by sending a request message to the SE Monitor/SE Manager.
  • SE ID identifier
  • SE Monitor/SE Manager that is, The overload detection process of the service enabler by the SPC may be an acquisition process of the identifier of the overload service enabler by the SPC.
  • the SPC can also obtain the identity of the overloaded first service enabler by sending a request message to the SE Monitor/SE Manager.
  • an SPC integrated with the service enabler detection function can also perform overload detection by itself.
  • the identifier of the first service enabler may be an IP address or a URL of the first service enabler, and the like.
  • the SPC determines and sends to the STC the service path identifier and the new service path identifier that are affected by the overload.
  • the identifier of the first service path of the first service enabler may be determined according to the identifier of the first service enabler.
  • the PCRF device or the STC that initially allocates the service flow allocates a service path identifier to the service flow of the UE, and the correspondence between the identifier of the service path and the identifier of the service enabler through which the service path passes The relationship is sent to the SPC. Therefore, the PCRF device, the STC, or the SPC can determine, by using the foregoing correspondence, which service path identifiers the identifier of the first service enabler corresponds to, that is, which service paths are affected by the overload.
  • the SPC can determine the identifier of the second service path according to the identifier of the first service enabler and the current load status of each service enabler.
  • the SPC may replace the first service enabler in the first service path with the second service enabler to form a second service path.
  • the second service enabler can be a different service enabler that is located in the same SE Pool as the first service enabler, that is, the function is the same and the individual is different.
  • the second service enabler may be determined by the SPC according to the load status of each service enabler. For example, the service enabler with the lowest load is determined to be the second service in the SE Pool to which the first service enabler belongs. Enabler. It should be understood that the SPC may also re-determine the identity of the second service path according to the service routing rule sent by the PCRF, and satisfy the condition that the second service path does not pass the first service enabler.
  • the SPC may send the identifier of the first service path and the identifier of the second service path to
  • the STC determines the first service flow affected by the overload.
  • the STC may cache the identifier of the second service path in the STC for subsequent use, and determine the first according to the identifier of the first service path.
  • Service flow it should be understood that there may be more than one service path through the first service enabler, and the service flow flowing through the first service enabler according to these service paths is A traffic flow affected by an overload.
  • the STC determines, according to the identifier of the first service path, the first service flow that is affected by the overload, and the first service flow may be randomly selected by the STC in the multiple service flows to which the identifier of the first service path is allocated.
  • the STC may be performed at a granularity of the service flow or may be performed at a granularity of the UE, which is not limited by the present invention.
  • S1004 The STC applies a new service path identifier according to the session state.
  • the STC determines the current session state of the first service flow, and when the STC detects that the session ends or a new session starts, the identifier of the second service path cached by the STC in the step S1002 is marked for the first service flow, so that the first service flow is
  • the data packet of the new session flows through the second service enabler according to the second service path, and the second service enabler replaces the original first service enabler to process the new session.
  • the STC may change the original first service path identifier to a new second service path identifier to perform a new session of the first service flow.
  • Package the original first service path identifier to a new second service path identifier to perform a new session of the first service flow.
  • FIG 11 is a schematic block diagram of a Service Routing Device (PCRF) in accordance with one embodiment of the present invention.
  • the processing unit 1101 determines a first service flow that is affected by the overload, where the first service flow is a service flow of the first service enabler that is carried according to the first service path.
  • the sending unit 1102 sends the identifier of the second service path to the service flow classifier STC, so that the STC assigns the identifier of the second service path to the first session when the current session of the first service flow ends or the new session of the first service flow starts.
  • a service flow such that the new session of the first service flow flows through the second service enabler according to the second service path, where the first service enabler is different from the second service enabler and has the same function type.
  • the embodiment determines whether to migrate the service flow of the first service enabler to the second by determining the current session state of the service flow flowing through the first service enabler.
  • the service enabler can ensure the uninterrupted user service while improving the overload of the service enabler, thereby improving the user experience.
  • the PCRF entity 1100 can perform the methods of any of the above-described Figures 2-6.
  • the processing unit 1101 is specifically configured to: obtain an identifier of the overloaded first service enabler, and acquire a first service path that passes the first service enabler according to the identifier of the first service enabler. Identification of the first service flow in the service flow to which the identity of the first service path is assigned.
  • the processing unit 1101 of the PCRF can learn the identifier (SE ID) of the first service enabler.
  • SE ID of the first service enabler can be SE
  • the Monitor detects that the first service enabler is overloaded and sends it to the PCRF. That is, the PCRF can obtain the SE ID of the first service enabler from the SE Monitor.
  • the PCRF may also obtain the identifier of the overloaded first service enabler by sending a request message to the SE Monitor.
  • the identifier of the first service enabler may be an IP address or a URL of the first service enabler, and the present invention is not limited thereto.
  • the identifier of the overload service enabler can also be sent by the SE Manager to the PCRF, and the SE Manager can detect the overload by itself.
  • a service enabler may also obtain the SE ID of the first service enabler from the SE Monitor and send it to the PCRF.
  • the first service is stored between the identifier of the service path and the identifier of the service enabler, because the PCRF device or the STC that initially allocates the service flow allocates the service path identifier for the service flow of the UE.
  • the processing unit 1101 of the PCRF may determine the first service flow of the UE affected by the overload according to the identifier of the first service enabler. Specifically, the processing unit 1101 of the PCRF may first determine, according to the identifier of the first service enabler, and the correspondence between the identifier of the service path and the identifier of the service enabler, the first through the first service enabler. The identity of the business path.
  • the PCRF determines the identifier of the first service flow according to the identifier of the first service path, where the first service flow may be randomly selected by the PCRF among the multiple service flows to which the identifier of the first service path is allocated.
  • the PCRF entity 1100 further includes a receiving unit 1103, where the receiving unit 1103 is configured to: receive an identifier of the first service path sent by the service path controller SPC, where the identifier of the first service path is overloaded by the SPC. The identifier of the first service enabler is obtained; the processing unit 1101 is further configured to: determine the first service flow in the service flow that is assigned the identifier of the first service path.
  • the overload detection of the service enabler is completed by the SPC, and the SPC can detect that the first service enabler is overloaded by the SE Monitor/SE Manager, that is, the overload detection process of the service enabler by the SPC may be The acquisition process of the SPC for the identification of the overload service enabler.
  • the SPC can also obtain the identity of the overloaded first service enabler by sending a request message to the SE Monitor/SE Manager.
  • the SPC After the SPC detects that the first service enabler is overloaded, it can be identified according to the identifier of the first service enabler.
  • the identifier of the first service path of the first service enabler is determined, and the identifier of the first service path is sent to the PCRF.
  • the mapping between the identifier of the service path and the identifier of the service enabler passing through the service path is determined by the PCRF device or the STC that initially allocates the service flow to the service flow of the UE.
  • the SFC is sent to the SPC. Therefore, the PCRF device, the STC, or the SPC can determine, by using the foregoing correspondence, which service path identifiers the identifier of the first service enabler corresponds to, that is, which service paths are affected by the overload.
  • the processing unit 1101 may determine the first service flow according to the identifier of the first service path. It should be understood that the service path of the first service enabler may have More than one, the traffic flowing through the first service enabler according to these service paths is a traffic flow affected by the overload.
  • the processing unit 1101 of the PCRF determines, according to the identifier of the first service path, the first service flow that is affected by the overload, and the first service flow may be randomly selected by the PCRF among the multiple service flows to which the identifier of the first service path is allocated.
  • the sending unit 1102 is further configured to: send an event subscription request to the STC, so that the STC detects an event result of the first service flow, where the event result includes a current session end of the first service flow or a new session.
  • the receiving unit 1103 is further configured to: receive a response message that is sent by the STC when detecting an event result of the first service flow; the processing unit 1101 is further configured to: determine an identifier of the second service path for the first service flow.
  • the PCRF entity may send an event subscription request for the first service flow to the STC through the sending unit 1102, to request the STC to detect the end of the current session of the first service flow or new When the session starts, it responds to the event subscription request.
  • the first service flow of the UE has a specific service type (ie, a function type), and is used to complete a certain task or request.
  • the first service flow may be composed of at least one session, that is, the first service flow is formed. Multiple sessions also have the same service type and are used to complete a certain task or request.
  • Each session starts with establishing a TCP connection between the UE and the server. TCP divides the data stream contained in the session into data packets of appropriate length. For transmission, the TCP connection is released when the session ends. Therefore, terminating the service flow in the middle of the session will cause the TCP connection to be interrupted, resulting in service interruption.
  • the PCRF may generate the event subscription request according to an Application Detection Control (ADC) rule to facilitate the subscription of the start and end of the event of the first service flow from the STC.
  • ADC Application Detection Control
  • the PCRF can also perform event subscription for the UE affected by the overload, which is not limited by the present invention.
  • the STC responds by detecting the end of the current session of the first service flow or the start of a new session.
  • the message notifies the PCRF of the event.
  • the processing unit 1101 may determine a new service path identifier for the first service flow. It should be understood that the PCRF may also determine a new service path identifier for the first service flow at any time during the period before the PCRF prepares to send the new service path identifier to the STC after detecting that the first service enabler is overloaded, the present invention. This is not limited.
  • the processing unit 1101 is specifically configured to: determine, according to the identifier of the first service enabler, the service type of the first service flow, the service routing rule pre-stored by the device, and the current load status of each service enabler. At least one of determining a second service path through the second service enabler.
  • the PCRF determines a new service path identifier (ie, the identifier of the second service path) for the first service flow.
  • the processing unit 1101 of the PCRF may be based on the identifier of the first service enabler, the service type of the first service flow, and the PCRF.
  • the at least one of the pre-stored service routing rule and the current load status of each service enabler determines a second service path that passes through the second service enabler.
  • the processing unit 1101 of the PCRF may replace the first service enabler in the first service path with the second service enabler to form a second service path.
  • the second service enabler can be a different service enabler in the same SE Pool as the first service enabler, that is, the function is the same and the individual is different.
  • the second service enabler may also be determined by the processing unit 1101 of the PCRF according to the load status of each service enabler, for example, determining the service load with the lowest current load in the SE Pool to which the first service enabler belongs. For the second service enabler. It should be understood that the processing unit 1101 of the PCRF may also re-determine the identity of the second service path according to the service routing rule, and satisfy the condition that the second service path does not pass the first service enabler.
  • the sending unit 1102 is specifically configured to: send, to the SPC, a request message for requesting an identifier of the second service path, so that the SPC is configured according to the identifier of the first service enabler, the first service flow.
  • the at least one of the service type and the current load status of each service enabler determines a second service path that passes through the second service enabler.
  • the receiving unit 1103 is specifically configured to receive the identifier of the second service path sent by the SPC.
  • the new service path identifier can be determined by the SPC. Specifically, after receiving the first service path identifier sent by the SPC and determining the first service flow, the receiving unit 1103 of the PCRF may send a request message to the SPC through the sending unit 1102 to request a new service path identifier.
  • the request message may carry the identifier of the first service path or the UE corresponding to the first service flow. logo.
  • the SPC After receiving the request message sent by the PCRF, the SPC determines a new service path identifier (ie, the identifier of the second service path) for the first service flow, and the method for determining the second service path identifier may refer to the foregoing embodiment. Narration. After determining the identifier of the second service path, the SPC sends it to the PCRF, so that the PCRF sends the identifier of the second service path to the STC through the sending unit 1102, and the STC applies the identifier of the second service path.
  • a new service path identifier ie, the identifier of the second service path
  • the receiving unit 1103 is specifically configured to: receive, by the SPC, at least one of an identifier of the first service enabler, a service type of the first service flow, and a current load state of each service enabler. Determining and transmitting an identification of the second service path, wherein the second service path passes the second service enabler.
  • the SPC may determine, according to at least one of the identifier of the first service enabler, the service type of the first service flow, and the current load status of each service enabler, the second service that passes the second service enabler. path.
  • the SPC may replace the first service enabler in the first service path with the second service enabler to form a second service path.
  • the second service enabler can be a different service enabler that is located in the same SE Pool as the first service enabler, that is, the functions are the same and the individual is different.
  • the second service enabler may also be determined by the SPC according to the load status of each service enabler, for example, the SE to which the first service enabler belongs.
  • the service enabler that determines the current load is the second service enabler in the pool. It should be understood that the SPC may also re-determine the identity of the second service path according to the service routing rule sent by the PCRF, and satisfy the condition that the second service path does not pass the first service enabler.
  • the processing unit 1101 is further configured to: determine, according to the identifier of the first service enabler, the service type of the first service flow, the service routing rule pre-stored by the PCRF, and the current load status of each service enabler. At least one of determining a second service path through the second service enabler.
  • the identifier of the second service path may be directly determined for the first service flow, where the second service path is determined.
  • the identifier is sent to the STC by the sending unit 1102, and the STC determines the identifier of the second application service path according to the session state of the first service flow.
  • the PCRF 1100 of the embodiment of the present invention determines the first service flow that is affected by the overload of the first service enabler, determines or acquires the second service path that does not pass the first service enabler, and identifies the second service path.
  • the STC is caused to assign an identifier of the second service path to the first service flow when the current session of the first service flow ends or a new session of the first service flow begins.
  • the first service flow can change the path during the intermittent session, and flow through the second according to the second service path.
  • the service enabler avoids the overload of the first service enabler and increases the load of the overloaded first service enabler. In other words, when the overloaded service enabler reduces the load pressure, the continuity of the service can be ensured, and packet loss, service interruption, and the like are not caused, and the user experience is improved.
  • FIG 12 is a schematic block diagram of a Service Routing Device (STC) in accordance with one embodiment of the present invention.
  • the traffic classifier STC 1200 shown in Figure 12 includes a processing unit 1201.
  • the processing unit 1201 determines a first service flow that is affected by the overload, where the first service flow is a service flow of the first service enabler that is carried according to the first service path. Processing unit 1201 determines a current session state of the first traffic flow. When the current session of the first service flow ends or a new session of the first service flow starts, the processing unit 1201 assigns the identifier of the second service path to the first service flow, so that the new session of the first service flow is in accordance with the second service. The path flows through the second service enabler, where the first service enabler is different from the second service enabler and has the same function type.
  • the embodiment determines whether to migrate the service flow of the first service enabler to the second by determining the current session state of the service flow flowing through the first service enabler.
  • the service enabler can ensure the uninterrupted user service while improving the overload of the service enabler, thereby improving the user experience.
  • STC 1200 can perform the relevant steps of the method of Figures 2-10 above.
  • the processing unit 1201 is specifically configured to: obtain an identifier of the first service path; and determine the first service flow in the service flow to which the identifier of the first service path is allocated.
  • the processing unit 1201 may also obtain the identifier of the first service path locally at the STC.
  • the processing unit 1201 of the STC may obtain the first service path identifier from the PCRF;
  • the processing unit 1201 of the STC may obtain the first service path identifier from the SPC;
  • the processing unit 1201 of the STC can determine the identity of the first service path by itself.
  • the processing unit 1201 of the STC may determine the first service flow according to the identifier of the first service path.
  • the service path of the first service enabler may have more than one.
  • the service flow of the service path flowing through the first service enabler is a service flow affected by the overload.
  • the processing unit 1201 of the STC determines, according to the identifier of the first service path, the first service flow affected by the overload, and the first service flow may be randomly selected by the STC among the plurality of service flows to which the identifier of the first service path is allocated.
  • the device further includes a receiving unit 1202, where the processing unit 1201 The method is specifically configured to: obtain an identifier of the first service enabler that is overloaded, and obtain an identifier of the first service path that passes the first service enabler according to the identifier of the first service enabler; or
  • the identifier of the first service enabler may be sent to the STC after the SE Monitor detects that the first service enabler is overloaded, that is, the STC is for the service enabler.
  • the overload detection process may be an acquisition process of the identifier of the overload service enabler by the STC.
  • the STC can also obtain the identity of the overloaded first service enabler by sending a request message to the SE Monitor/SE Manager. It should be understood that the identity of the overload service enabler can also be sent to the STC through the SE Manager.
  • the STC may determine the identifier of the first service path passing the first service enabler according to the identifier of the first service enabler, the identifier of the service path, and the identifier of the service enabler. It should be understood that there may be more than one service path through the first service enabler, and the service flow flowing through the first service enabler according to these service paths is a service flow affected by the overload.
  • the identifier of the first service enablement may be sent by the SE Monitor/SE Manager to the SPC after detecting that the first service enabler is overloaded, that is, the SPC is for the service enabler.
  • the overload detection process may be an acquisition process of the SPC for the identification of the overload service enabler.
  • the SPC can also obtain the identity of the overloaded first service enabler by sending a request message to the SE Monitor/SE Manager. It should be understood that an SPC integrated with a service enabler detection function can also perform overload detection by itself.
  • the SPC may determine the identifier of the first service path that passes the first service enabler according to the identifier of the first service enabler, and send the identifier of the first service path to the STC.
  • the PCRF device or the STC that initially allocates the service flow allocates a service path identifier to the service flow of the UE, and the correspondence between the identifier of the service path and the identifier of the service enabler through which the service path passes The relationship is sent to the SPC, so the PCRF device, the STC, or the SPC can determine, by using the foregoing correspondence, which service path identifiers the identifier of the first service enabler corresponds to, that is, which service paths are affected by the overload.
  • the identifier of the first service enabler may be an SE.
  • the monitor detects that the first service enabler is overloaded and sends it to the PCRF. That is, the overload detection process of the PCRF for the service enabler may be the process of obtaining the identifier of the overload service enabler by the PCRF.
  • the PCRF can also obtain the identifier of the overloaded first service enabler by sending a request message to the SE Monitor/SE Manager. It should be understood that the identifier of the overload service enabler may also be sent to the PCRF through the SE Manager.
  • the PCRF may determine the identifier of the first service path that passes the first service enabler according to the identifier of the first service enabler, the identifier of the service path, and the identifier of the service enabler. It should be understood that there may be more than one service path through the first service enabler, and the service flow flowing through the first service enabler according to the service path is a service flow affected by the overload.
  • the receiving unit 1202 is further configured to: receive an identifier of the second service path sent by the PCRF, where the identifier of the second service path is determined by the PCRF according to the identifier of the first service enabler, the first service flow. At least one of the service type, the pre-stored service routing rule of the PCRF, and the current load status of each service enabler is determined, and the second service path passes through the second service enabler.
  • the PCRF may determine the identifier of the first service flow according to the identifier of the first service path, where the first service flow is It may be that the PCRF is randomly selected among a plurality of service flows to which the identity of the first service path is allocated.
  • the PCRF may determine a new service path identifier (ie, the identifier of the second service path) for the first service flow.
  • the PCRF may be configured according to the first service enabler. And determining, by the identifier, the service type of the first service flow, the service routing rule pre-stored by the PCRF, and the current load status of each service enabler, determining a second service path that passes through the second service enabler.
  • the PCRF may replace the first service enabler in the first service path with the second service enabler to form a second service path.
  • the second service enabler may be a different service enabler that is located in the same SE Pool as the first service enabler, that is, the functions are the same and the individuals are different.
  • the second service enabler may also be determined by the PCRF according to the load status of each service enabler. For example, in the SE Pool to which the first service enabler belongs, the service enabler with the lowest current load is determined to be the second service. Enabler. It should be understood that the PCRF may also re-determine the identity of the second service path according to the service routing rule, and satisfy the condition that the second service path does not pass the first service enabler. After determining the identifier of the second service path, the PCRF can directly deliver the identifier to the STC, and the STC determines when to use it.
  • the STC 1200 further includes a sending unit 1203, configured to: send, by the SPC, a request message for requesting an identifier of the second service path, so that the SPC is configured according to the first service enabler. And determining, by the at least one of the service type of the first service flow and the current load status of each service enabler, a second service path that is sent by the second service enabler; the receiving unit 1202 is further configured to receive the The identification of the second business path.
  • the STC after receiving the first service path identifier sent by the SPC, the STC determines the current session state of the first service flow, after the current session of the first service flow ends, or a new session. Before starting, the STC sends a request message to the SPC to request a new service path identifier.
  • the request message may carry the identifier of the first service path or the identifier of the UE corresponding to the first service flow.
  • the SPC determines a new service path identifier (ie, the identifier of the second service path) for the first service flow and sends it to the STC.
  • the SPC may determine, according to at least one of the identifier of the first service enabler, the service type of the first service flow, and the current load status of each service enabler, the second service that passes the second service enabler. path.
  • the SPC may replace the first service enabler in the first service path with the second service enabler to form a second service path.
  • the second service enabler can be a different service enabler that is located in the same SE Pool as the first service enabler, that is, the functions are the same and the individual is different.
  • the second service enabler may be determined by the SPC according to the load status of each service enabler.
  • the service enabler with the lowest load is determined to be the second service in the SE Pool to which the first service enabler belongs. Enabler. It should be understood that the SPC may also re-determine the identity of the second service path according to the service routing rule sent by the PCRF, and satisfy the condition that the second service path does not pass the first service enabler.
  • the receiving unit 1202 is further configured to: receive an identifier of the second service path sent by the SPC, where the identifier of the second service path is determined by the SPC according to the identifier of the first service enabler, the first service flow At least one of a service type and a current load status of each service enabler is determined, and the second service path passes through the second service enabler.
  • the SPC may determine the second service path identifier of the second service enabler when determining the overloaded first service enabler and determining the first service path identifier, and A service path identifier and a second service path identifier are both sent to the STC 1200.
  • the SPC may determine the second service path identifier of the second service enabler when determining the overloaded first service enabler and determining the first service path identifier, and A service path identifier and a second service path identifier are both sent to the STC 1200.
  • the STC 1200 of the embodiment of the present invention determines the first service flow affected by the overload of the first service enabler, determines or acquires the second service path that does not pass the first service enabler, and is in the first industry.
  • the identifier of the second service path is assigned to the first service flow. Therefore, the first service flow can change the path during the interval of the session, and the second service enabler flows according to the second service path, so as to avoid continuing to be affected by the overload of the first service enabler and aggravating the overloaded first service enabler.
  • Load In other words, when the overloaded service enabler reduces the load pressure, the service continuity can be ensured, and packet loss, service interruption, and the like are not caused, and the user experience is improved.
  • FIG. 13 is a schematic block diagram of a Service Routing Device (SPC) in accordance with one embodiment of the present invention.
  • the service path controller SPC 1300 illustrated in FIG. 13 includes a processing unit 1301 and a transmitting unit 1302.
  • the processing unit 1301 obtains the identifier of the overloaded first service enabler.
  • the processing unit 1301 acquires the identifier of the first service path that passes through the first service enabler according to the identifier of the first service enabler.
  • the sending unit 1302 sends the identifier of the first service path to the policy and charging rule function PCRF entity or the traffic classifier STC, so that the PCRF entity or the STC determines the first service flow to which the identifier of the first service path is allocated, where the first
  • the service flow is a service flow of the first service enabler that is carried according to the first service path; and the processing unit 1301 is configured according to the identifier of the first service enabler, the service type of the first service flow, and each service enabler.
  • the identifier of the second service path of the second service enabler is determined, wherein the first service enabler is different from the second service enabler and has the same function; the sending unit 1302 Sending an identifier of the second service path to the PCRF entity or the STC, so that the PCRF entity or the STC assigns the identifier of the second service path to the first when the current session of the first service flow ends or the new session of the first service flow starts.
  • the service flow causes the new session of the first service flow to flow through the second service enabler according to the second service path.
  • the embodiment determines whether to migrate the service flow of the first service enabler to the second by determining the current session state of the service flow flowing through the first service enabler.
  • the service enabler can ensure the uninterrupted user service while improving the overload of the service enabler, thereby improving the user experience.
  • SPC 1300 can perform the corresponding steps of the methods of Figures 2, 5-7, 9, and 10 above.
  • the SPC 1300 further includes a receiving unit 1303, configured to: receive a request message sent by the PCRF entity or the STC to request the identifier of the second service path.
  • the SPC 1300 of the embodiment of the present invention determines the first service flow that is affected by the overload of the first service enabler, determines or acquires the second service path that does not pass the first service enabler, and is in the first industry.
  • the identifier of the second service path is assigned to the first service flow. Therefore, the first service flow can change the path during the interval of the session, and the second service enabler flows according to the second service path, so as to avoid continuing to be affected by the overload of the first service enabler and aggravating the overloaded first service enabler.
  • Load In other words, when the overloaded service enabler reduces the load pressure, the service continuity can be ensured, and packet loss, service interruption, and the like are not caused, and the user experience is improved.
  • FIG 14 is a schematic block diagram of a Service Routing Apparatus (PCRF) in accordance with another embodiment of the present invention.
  • the PCRF entity 1400 of Figure 14 includes a processor 1401 and a memory 1402.
  • the processor 1401 and the memory 1402 are connected by a bus system 1403.
  • the memory 1402 is configured to store an instruction that causes the processor 1401 to: determine a first service flow that is affected by the overload, where the first service flow is a service flow of the first service enabler that is carried according to the first service path; Sending an identifier of the second service path to the service flow classifier STC, so that the STC assigns the identifier of the second service path to the first service flow when the current session of the first service flow ends or a new session of the first service flow starts. And causing the new session of the first service flow to flow through the second service enabler according to the second service path, where the first service enabler is different from the second service enabler and the function type is the same.
  • the embodiment determines whether to migrate the service flow of the first service enabler to the second by determining the current session state of the service flow flowing through the first service enabler.
  • the service enabler can ensure the uninterrupted user service while improving the overload of the service enabler, thereby improving the user experience.
  • PCRF entity 1400 can perform the respective steps of the method of any of the above-described Figures 2-6, and that the processor of the PCRF entity 1400 can correspond to the processing unit 1101 of the PCRF entity 1100 of Figure 11 above.
  • the PCRF entity 1400 may also include a transmitting circuit 1404, a receiving circuit 1405, and the like.
  • the processor 1401 controls the operation of the PCRF entity 1400, which may also be referred to as a CPU (Central Processing Unit).
  • Memory 1402 can include read only memory and random access memory and provides instructions and data to processor 1401.
  • a portion of memory 1402 may also include non-volatile random access memory (NVRAM).
  • the various components of the PCRF entity 1400 are coupled together by a bus system 1403, which may include, in addition to the data bus, a power bus, a control bus, a status signal bus, and the like. However, for clarity of description, various buses are labeled as the bus system 1403 in the figure.
  • the method disclosed in the foregoing embodiment of the present invention may be applied to the processor 1401 or implemented by the processor 1401.
  • the processor 1401 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the foregoing method may be completed by an integrated logic circuit of hardware in the processor 1401 or an instruction in a form of software.
  • the processor 1401 described above may be a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware. Component.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA off-the-shelf programmable gate array
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present invention may be implemented or executed.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present invention may be directly implemented as a hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory 1402.
  • the processor 1401 reads the information in the memory 1402 and completes the steps of the above method in combination with its hardware.
  • the processor 1401 is configured to: obtain an identifier of the overloaded first service enabler, and acquire, according to the identifier of the first service enabler, the first service path that passes the first service enabler. Identification; determining the first service flow in the service flow to which the identity of the first service path is allocated.
  • the identifier of the first service path sent by the service path controller SPC is received by the receiving circuit 1405, where the identifier of the first service path is obtained by the SPC according to the identifier of the overloaded first service enabler;
  • the processor 1401 determines the first service flow in the service flow to which the identity of the first service path is allocated.
  • the event subscription request is sent to the STC by the sending circuit 1404, so that the STC detects an event result of the first service flow, where the event result includes the end of the current session of the first service flow or the start of a new session;
  • the receiving circuit 1405 receives the response message sent by the STC when detecting the event result of the first service flow; the processor 1401 determines the identifier of the second service path for the first service flow.
  • the processor 1401 is configured to: at least one of an identifier of the first service enabler, a service type of the first service flow, a service route rule pre-stored by the PCRF, and a current load state of each service enabler. And determining a second service path through the second service enabler.
  • the request message for requesting the identifier of the second service path is sent to the SPC by the sending circuit 1404, so that the SPC is configured according to the identifier of the first service enabler, the service type of the first service flow, and Determining at least one of the current load states of the respective service enablers Passing the second service path of the second service enabler; receiving, by the receiving circuit 1405, the identifier of the second service path sent by the SPC.
  • the SPC determines and sends according to at least one of an identifier of the first service enabler, a service type of the first service flow, and a current load state of each service enabler.
  • the processor 1401 is configured to: at least one of an identifier of the first service enabler, a service type of the first service flow, a service route rule pre-stored by the PCRF, and a current load state of each service enabler. And determining a second service path through the second service enabler.
  • the PCRF entity 1400 of the embodiment of the present invention determines the first service flow that is affected by the overload of the first service enabler, determines or acquires the second service path that does not pass the first service enabler, and then the second service path
  • the ID is sent to the STC.
  • the STC is caused to assign the identity of the second service path to the first service flow when the current session of the first service flow ends or a new session of the first service flow begins. Therefore, the first service flow can change the path during the interval of the session, and the second service enabler flows through the second service enabler to avoid the overload of the first service enabler and the overloaded first service enabler.
  • Load In other words, when the overloaded service enabler reduces the load pressure, the continuity of the service can be ensured, and packet loss, service interruption, and the like are not caused, and the user experience is improved.
  • FIG. 15 is a schematic block diagram of a Service Routing Apparatus (STC) in accordance with another embodiment of the present invention.
  • the traffic classifier STC 1500 of Figure 15 includes a processor 1501 and a memory 1502.
  • the processor 1501 and the memory 1502 are connected by a bus system 1503.
  • the memory 1502 is configured to store an instruction that causes the processor 1501 to: determine a first service flow that is affected by the overload, where the first service flow is a service flow of the first service enabler that is carried according to the first service path; Determining a current session state of the first service flow; assigning an identifier of the second service path to the first service flow when the current session of the first service flow ends or a new session of the first service flow starts, so that the first service flow The new session flows through the second service enabler according to the second service path, where the first service enabler is different from the second service enabler and has the same function type.
  • the embodiment determines whether to migrate the service flow of the first service enabler to the second by determining the current session state of the service flow flowing through the first service enabler.
  • the service enabler can ensure the uninterrupted user service while improving the overload of the service enabler, thereby improving the user experience.
  • the STC 1500 can perform the relevant steps of the method of FIGS. 2-10 above, and the processor 1501 of the STC 1500 can correspond to the processing unit 1201 of the STC 1200 of FIG. 12 described above.
  • the STC 1500 may further include a transmitting circuit 1504 and a receiving circuit 1505.
  • the processor 1501 controls the operation of the STC 1500, and the processor 1501 may also be referred to as a CPU (Central Processing Unit).
  • Memory 1502 can include read only memory and random access memory and provides instructions and data to processor 1501. A portion of memory 1502 may also include non-volatile random access memory (NVRAM).
  • NVRAM non-volatile random access memory
  • the various components of the STC 1500 are coupled together by a bus system 1503, which may include, in addition to the data bus, a power bus, a control bus, and a status signal bus. However, for clarity of description, various buses are labeled as bus system 1503 in the figure.
  • the method disclosed in the above embodiments of the present invention may be applied to the processor 1501 or implemented by the processor 1501.
  • the processor 1501 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method may be completed by an integrated logic circuit of hardware in the processor 1501 or an instruction in the form of software.
  • the processor 1501 described above may be a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware. Component.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA off-the-shelf programmable gate array
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present invention may be implemented or carried out.
  • the general purpose processor can be a microprocessor or the processor can be any conventional processor or the like.
  • the steps of the method disclosed in connection with the embodiments of the present invention may be directly embodied by the execution of the hardware decoding processor, or by a combination of hardware and software modules in the decoding processor.
  • the software modules can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory 1502, and the processor 1501 reads the information in the memory 1502 and completes the steps of the above method in combination with the hardware thereof.
  • the processor 1501 is configured to: obtain an identifier of the first service path; and determine the first service flow in the service flow to which the identifier of the first service path is allocated.
  • the processor 1501 obtains an identifier of the overloaded first service enabler, and obtains an identifier of the first service path that passes the first service enabler according to the identifier of the first service enabler; Or receiving, by the receiving circuit 1505, the identifier of the first service path sent by the service path controller SPC, where the identifier of the first service path is obtained by the S PC according to the identifier of the overloaded first service enabler; or receiving the policy by the receiving circuit 1505.
  • the identifier of the first service path sent by the PCRF entity with the charging rule function, where the identifier of the first service path is verified by the PCRF entity The identifier of the first service enabler is loaded.
  • the identifier of the second service path sent by the PCRF is received by the receiving circuit 1505, where the identifier of the second service path is determined by the PCRF according to the identifier of the first service enabler and the service type of the first service flow. And determining, by the PCRF, at least one of a service routing rule pre-stored and a current load state of each service enabler, where the second service path passes the second service enabler.
  • the request message for requesting the identifier of the second service path is sent to the SPC by the sending circuit 1504, so that the SPC is configured according to the identifier of the first service enabler, the service type of the first service flow, and At least one of the current load states of the service enablers determines a second service path that passes through the second service enabler; and receives, by the receiving circuit 1505, an identifier of the second service path sent by the SPC.
  • the identifier of the second service path sent by the SPC is received by the receiving circuit 1505, where the identifier of the second service path is determined by the SPC according to the identifier of the first service enabler and the service type of the first service flow. And determining, by the at least one of the current load states of the service enablers, that the second service path passes the second service enabler.
  • the STC 1500 of the embodiment of the present invention determines the first service flow affected by the overload of the first service enabler, determines or acquires the current session of the first service flow after the second service path that does not pass the first service enabler.
  • the identifier of the second service path is allocated to the first service flow. Therefore, the first service flow can change the path during the interval of the session, and the second service enabler flows according to the second service path, so as to avoid continuing to be affected by the overload of the first service enabler and aggravating the overloaded first service enabler.
  • Load In other words, when the overloaded service enabler reduces the load pressure, the service continuity can be ensured, and packet loss, service interruption, and the like are not caused, and the user experience is improved.
  • FIG. 16 is a schematic block diagram of a Service Routing Device (SPC) in accordance with another embodiment of the present invention.
  • the service path controller SPC 1600 of FIG. 16 includes a processor 1601 and a memory 1602.
  • the processor 1601 and the memory 1602 are connected by a bus system 1603.
  • the memory 1602 is configured to store an instruction that causes the processor 1601 to: obtain an identifier of the overloaded first service enabler; and acquire, according to the identifier of the first service enabler, the first service path that passes through the first service enabler Identifying, by the policy and charging rule function PCRF entity or the traffic classifier STC, the identifier of the first service path, so that the PCRF entity or the STC determines the first service flow to which the identifier of the first service path is allocated, where the first service The flow is a service flow of the first service enabler that is carried according to the first service path; and according to the identifier of the first service enabler, the first Determining, by at least one of a service type of the service flow and a current load status of each service enabler, an identifier of the second service path that passes through the second service enabler, where the first service enabler and the second service enable The identifiers are different and have the same function; the identifier of the second service path is sent to the PCRF entity or the
  • the embodiment determines whether to migrate the service flow of the first service enabler to the second by determining the current session state of the service flow flowing through the first service enabler.
  • the service enabler can ensure the uninterrupted user service while improving the overload of the service enabler, thereby improving the user experience.
  • the SPC 1600 can perform the corresponding steps of the methods of Figures 2, 5-7, 9, and 10 above, and the processor 1601 of the SPC 1600 can correspond to the processing unit 1301 of the SPC 1300 of Figure 13 above.
  • the SPC 1600 can also include a transmitting circuit 1604 and a receiving circuit 1605.
  • the processor 1601 controls the operation of the SPC 1600, which may also be referred to as a CPU (Central Processing Unit).
  • Memory 1602 can include read only memory and random access memory and provides instructions and data to processor 1601. A portion of memory 1602 may also include non-volatile random access memory (NVRAM).
  • NVRAM non-volatile random access memory
  • the various components of the SPC 1600 are coupled together by a bus system 1603, which may include, in addition to the data bus, a power bus, a control bus, and a status signal bus. However, for clarity of description, various buses are labeled as bus system 1603 in the figure.
  • the method disclosed in the foregoing embodiment of the present invention may be applied to the processor 1601 or implemented by the processor 1601.
  • the processor 1601 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the foregoing method may be completed by an integrated logic circuit of hardware in the processor 1601 or an instruction in a form of software.
  • the processor 1601 described above may be a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware. Component.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA off-the-shelf programmable gate array
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present invention may be implemented or executed.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present invention may be directly implemented as a hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor.
  • Software modules can be located at random Memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, etc. are well-established in the field of storage media.
  • the storage medium is located in the memory 1602, and the processor 1601 reads the information in the memory 1602, and completes the steps of the above method in combination with the hardware thereof.
  • the receiving circuit 1605 receives a request message sent by the PCRF entity or the STC for requesting the identifier of the second service path.
  • the SPC 1600 of the embodiment of the present invention determines the first service flow affected by the overload of the first service enabler, and determines or acquires the current session of the first service flow after the second service path that does not pass the first service enabler.
  • the identifier of the second service path is allocated to the first service flow. Therefore, the first service flow can change the path during the interval of the session, and the second service enabler flows according to the second service path, so as to avoid continuing to be affected by the overload of the first service enabler and aggravating the overloaded first service enabler.
  • Load In other words, when the overloaded service enabler reduces the load pressure, the service continuity can be ensured, and packet loss, service interruption, and the like are not caused, and the user experience is improved.
  • RAM random access memory
  • ROM read only memory
  • electrically programmable ROM electrically erasable programmable ROM
  • registers hard disk, removable disk, CD-ROM, or technical field. Any other form of storage medium known.
  • the invention is not limited to this.
  • Various equivalent modifications and alterations to the embodiments of the present invention can be made by those skilled in the art without departing from the spirit and scope of the invention.

Landscapes

  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本发明实施例提供一种业务路由系统和方法,能够使得在进行业务使能器的负载重分配时不会引起用户业务的中断。该方法包括:判断过载的第一业务使能器上受到过载影响的用户的会话状态,其中受到过载影响的用户的当前会话的业务流流经第一业务使能器;根据用户的会话状态将当前会话的新的会话分配到第二业务使能器,当前会话与新的会话的业务类型相同,第二业务使能器与第一业务使能器的功能相同。本发明实施例通过判断过载的业务使能器所服务的用户是否正在进行业务来决定如何迁移用户流量,从而在完成负载均衡的同时能够保证用户业务不中断,提高了用户体验。

Description

业务路由方法、 装置和系统 技术领域
本发明涉及通信领域,并且更具体地, 涉及业务路由方法、装置和系统。 背景技术
随着互联网技术的飞速发展和智能终端的广泛普及, 手机购物、 支付、 办公等移动应用在极大地方便了人们的生活的同时也带来了移动端流量的 井喷式增长,但运营商的收益不但没有因此增加,反而每用户收益( Average Revenue Per User, ARPU )在下降,运营商们面临着沦为应用服务商们的 "哑 管道" 的命运。 为了改变这种局面以寻求利润空间地提升, 运营商们需要对 业务流量进行更加精准细分的管道经营, 通过按需收费、 按业务类型收费以 提升 ARPUo
部署增值业务有助于对业务流量进行更精准的管道经营以及提升用户 的体验效果, 因此一些主流运营商已经釆用串并联各种增值业务服务器 ( Value Added Service, VAS )的方案来部署增值业务。 这些增值业务服务器 也可以称为业务使能器(Service Enabler, SE )。 为保证可靠和高效地为用户 提供增值服务, 在部署增值业务时, 对于每一个类型的增值服务提供多个 VAS实例( SE实例;), 而具有相同功能的 SE实例组成 VAS池( VAS pool ), 如图 1所示。
图 1 示出了基于业务的路由系统(简称业务路由系统), 包括业务流分 类器 (Service Traffic Classifier , STC )、 业务路径控制器 (Service Path Controller, SPC )、 交换机和若干业务使能器 SE, 其中 STC和 SE通过交换 机互联, 各交换机由 SPC统一控制。 在用户设备(User Equipment, UE )的 业务流到达 STC时, STC对业务流的类型进行识别, 并向 SPC上报当前业 务流的信息和对应的业务路由规则信息, 其中业务路由规则信息是由 PCRF 下发至 STC的。 SPC收到业务路由规则后, 根据资源拓朴(交换机、 SE、 STC间的拓朴)为该业务流确定业务路径, 即确定业务流的报文要经过哪些 交换机, 并在这些交换机上设置针对该业务流的报文的转发规则, 转发规则 能够指示业务流的报文从交换机的哪个端口发出, 下一跳经过哪个具体 SE。
由于为业务流进行业务路径分配是按照 SE的当前负载进行的, 在通常 情况下能够使得各个 SE承载的业务流(负载)达到均衡状态, 然而在业务 高峰期, 无可避免的会出现某个或者多个 SE承载的业务流过多的情况, 当 SE承载的业务流超过其最大处理能力时即发生过载,过载的 SE承载的业务 流发生拥塞、 丟包等现象, 使得用户体验降低。 因此, 如何对过载的业务使 能器承载的业务流进行负载重分配成为亟待解决的问题。 发明内容
本发明实施例提供一种业务路由的方法、 装置和系统, 能够在不引起用 户设备业务中断的情况下解决业务使能器过载造成的拥塞、 丟包等现象, 提 高用户体验。
第一方面,提供了一种业务路由方法, 包括:策略和计费规则功能 PCRF 实体确定受到过载影响的第一业务流, 其中所述第一业务流为按照第一业务 路径流经过载的第一业务使能器的业务流; 所述 PCRF实体向业务流分类器 STC发送第二业务路径的标识, 以使得所述 STC在所述第一业务流的当前 会话结束或者所述第一业务流的新会话开始时,将所述第二业务路径的标识 分配给所述第一业务流,使得所述第一业务流的所述新会话按照所述第二业 务路径流经第二业务使能器, 其中所述第一业务使能器与所述第二业务使能 器相异、 且功能类型相同。
结合第一方面, 在其第一种实现方式中, 所述 PCRF实体确定受到过载 影响的第一业务流, 包括: 获取过载的所述第一业务使能器的标识; 根据所 述第一业务使能器的标识获取经过所述第一业务使能器的第一业务路径的 标识; 在分配有所述第一业务路径的标识的业务流中确定所述第一业务流。
结合第一方面及其上述实现方式, 在其第二种实现方式中, 所述 PCRF 实体确定受到过载影响的第一业务流, 包括:接收业务路径控制器 SPC发送 的所述第一业务路径的标识,其中所述第一业务路径的标识由所述 SPC根据 过载的所述第一业务使能器的标识获取; 在分配有所述第一业务路径的标识 的业务流中确定所述第一业务流。
结合第一方面及其上述实现方式,在其第三种实现方式中,在所述 PCRF 实体向 STC发送第二业务路径的标识之前, 所述方法还包括: 向所述 STC 发送事件订阅请求, 以使得所述 STC检测所述第一业务流的事件结果, 其 中所述事件结果包括所述第一业务流的当前会话结束或者新会话开始; 接收 所述 STC在检测到所述第一业务流的所述事件结果时发送的响应消息; 为 所述第一业务流确定所述第二业务路径的标识。
结合第一方面及其上述实现方式, 在其第四种实现方式中, 所述为所述 第一业务流确定所述第二业务路径的标识, 包括: 根据所述第一业务使能器 的标识、 所述第一业务流的业务类型、 所述 PCRF预存的业务路由规则和各 个业务使能器当前的负载状态中的至少一种,确定经过所述第二业务使能器 的第二业务路径。
结合第一方面及其上述实现方式, 在其第五种实现方式中, 所述为所述 第一业务流确定所述第二业务路径的标识, 包括: 向所述 SPC发送用于请求 所述第二业务路径的标识的请求消息,以使得所述 SPC根据所述第一业务使 能器的标识、所述第一业务流的业务类型和各个业务使能器当前的负载状态 中的至少一种, 确定经过所述第二业务使能器的第二业务路径; 接收所述
SPC发送的所述第二业务路径的标识。
结合第一方面及其上述实现方式, 在其第六种实现方式中, 所述向所述 STC发送事件订阅请求之前, 还包括: 接收所述 SPC根据所述第一业务使 能器的标识、所述第一业务流的业务类型和各个业务使能器当前的负载状态 中的至少一种确定并且发送的所述第二业务路径的标识, 其中第二业务路径 经过所述第二业务使能器。
结合第一方面及其上述实现方式, 在其第七种实现方式中, 所述 PCRF 实体向业务流分类器 STC发送第二业务路径的标识之前, 还包括: 根据所 述第一业务使能器的标识、 所述第一业务流的业务类型、 所述 PCRF预存的 业务路由规则和各个业务使能器当前的负载状态中的至少一种,确定经过所 述第二业务使能器的第二业务路径。
第二方面, 提供了一种业务路由方法, 包括: 业务流分类器 STC确定 受到过载影响的第一业务流, 其中所述第一业务流为按照第一业务路径流经 过载的第一业务使能器的业务流; 所述 STC确定所述第一业务流的当前会 话状态; 所述 STC在所述第一业务流的当前会话结束或者所述第一业务流 的新会话开始时, 将第二业务路径的标识分配给所述第一业务流, 以使得所 述第一业务流的所述新会话按照所述第二业务路径流经第二业务使能器, 其 中所述第一业务使能器与所述第二业务使能器相异、 且功能类型相同。
结合第二方面, 在其第一种实现方式中, 所述 STC确定受到过载影响 的第一业务流, 包括: 获取所述第一业务路径的标识; 在分配有所述第一业 务路径的标识的业务流中确定所述第一业务流。
结合第二方面及其上述实现方式, 在其第二种实现方式中, 所述确定所 述第一业务路径的标识, 包括: 获取过载的所述第一业务使能器的标识, 并 根据所述第一业务使能器的标识获取经过所述第一业务使能器的第一业务 路径的标识; 或者接收业务路径控制器 SPC发送的所述第一业务路径的标 识,其中所述第一业务路径的标识由所述 SPC根据过载的所述第一业务使能 器的标识获取; 或者接收策略与计费规则功能 PCRF实体发送的所述第一业 务路径的标识, 其中所述第一业务路径的标识由所述 PCRF实体根据过载的 所述第一业务使能器的标识获取。
结合第二方面及其上述实现方式, 在其第三种实现方式中, 所述 STC 确定所述第一业务流的当前会话状态之前, 还包括: 接收所述 PCRF发送的 所述第二业务路径的标识, 其中所述第二业务路径的标识由所述 PCRF根据 所述第一业务使能器的标识、 所述第一业务流的业务类型、 所述 PCRF预存 的业务路由规则和各个业务使能器当前的负载状态中的至少一种确定, 所述 第二业务路径经过所述第二业务使能器。
结合第二方面及其上述实现方式, 在其第四种实现方式中, 所述接收业 务路径控制器 SPC发送的所述第一业务路径的标识之后, 还包括: 向所述 SPC发送用于请求所述第二业务路径的标识的请求消息, 以使得所述 SPC 根据所述第一业务使能器的标识、所述第一业务流的业务类型和各个业务使 能器当前的负载状态中的至少一种,确定经过所述第二业务使能器的第二业 务路径; 接收所述 SPC发送的所述第二业务路径的标识。
结合第二方面及其上述实现方式, 在其第五种实现方式中, 所述 STC 确定所述第一业务流的当前会话状态之前,还包括:接收所述 SPC发送的所 述第二业务路径的标识,其中所述第二业务路径的标识由所述 SPC根据所述 第一业务使能器的标识、所述第一业务流的业务类型和各个业务使能器当前 的负载状态中的至少一种确定, 所述第二业务路径经过所述第二业务使能 器。
第三方面, 提供了一种业务路由方法, 包括: 业务路径控制器 SPC获取 过载的第一业务使能器的标识;所述 SPC根据所述第一业务使能器的标识获 取经过所述第一业务使能器的第一业务路径的标识;所述 SPC向策略和计费 规则功能 PCRF实体或业务流分类器 STC发送所述第一业务路径的标识,以 便于所述 PCRF实体或 STC确定分配有第一业务路径的标识的第一业务流, 其中所述第一业务流为按照第一业务路径流经过载的第一业务使能器的业 务流; 并且所述 SPC根据所述第一业务使能器的标识、所述第一业务流的业 务类型、 和各个业务使能器当前的负载状态中的至少一种, 确定经过第二业 务使能器的第二业务路径的标识,其中所述第一业务使能器与所述第二业务 使能器相异、 且功能相同; 所述 SPC向所述 PCRF实体或所述 STC发送所 述第二业务路径的标识,以便于所述 PCRF实体或所述 STC在所述第一业务 流的当前会话结束或者所述第一业务流的新会话开始时,将所述第二业务路 径的标识分配给所述第一业务流,使得所述第一业务流的所述新会话按照所 述第二业务路径流经第二业务使能器。
结合第三方面,在其第一种实现方式中, 所述 SPC向所述 PCRF实体或 所述 STC发送所述第二业务路径的标识之前,还包括:接收所述 PCRF实体 或所述 STC发送的用于请求所述第二业务路径的标识的请求消息。
第四方面, 提供了一种业务路由装置, 包括: 处理单元, 用于确定受到 过载影响的第一业务流, 其中所述第一业务流为按照第一业务路径流经过载 的第一业务使能器的业务流; 发送单元, 用于向业务流分类器 STC发送第 二业务路径的标识, 以使得所述 STC在所述第一业务流的当前会话结束或 者所述第一业务流的新会话开始时,将所述第二业务路径的标识分配给所述 第一业务流,使得所述第一业务流的所述新会话按照所述第二业务路径流经 第二业务使能器, 其中所述第一业务使能器与所述第二业务使能器相异、 且 功能类型相同。
结合第四方面, 在其第一种实现方式中, 所述处理单元具体用于: 获取 过载的所述第一业务使能器的标识; 根据所述第一业务使能器的标识获取经 过所述第一业务使能器的第一业务路径的标识; 在分配有所述第一业务路径 的标识的业务流中确定所述第一业务流。
结合第四方面及其上述实现方式, 在其第二种实现方式中, 所述装置还 包括接收单元,所述接收单元用于:接收业务路径控制器 SPC发送的所述第 一业务路径的标识,其中所述第一业务路径的标识由所述 SPC根据过载的所 述第一业务使能器的标识获取; 所述处理单元还用于: 在分配有所述第一业 务路径的标识的业务流中确定所述第一业务流。 结合第四方面及其上述实现方式, 在其第三种实现方式中, 所述发送单 元还用于: 向所述 STC发送事件订阅请求, 以使得所述 STC检测所述第一 业务流的事件结果, 其中所述事件结果包括所述第一业务流的当前会话结束 或者新会话开始; 所述接收单元还用于: 接收所述 STC在检测到所述第一 业务流的所述事件结果时发送的响应消息; 所述处理单元还用于: 为所述第 一业务流确定所述第二业务路径的标识。
结合第四方面及其上述实现方式, 在其第四种实现方式中, 所述处理单 元具体用于:根据所述第一业务使能器的标识、所述第一业务流的业务类型、 所述装置预存的业务路由规则和各个业务使能器当前的负载状态中的至少 一种, 确定经过所述第二业务使能器的第二业务路径。
结合第四方面及其上述实现方式, 在其第五种实现方式中, 所述发送单 元具体用于: 向所述 SPC发送用于请求所述第二业务路径的标识的请求消 息, 以使得所述 SPC根据所述第一业务使能器的标识、所述第一业务流的业 务类型和各个业务使能器当前的负载状态中的至少一种,确定经过所述第二 业务使能器的第二业务路径;所述接收单元具体用于接收所述 SPC发送的所 述第二业务路径的标识。
结合第四方面及其上述实现方式, 在其第六种实现方式中, 所述接收单 元具体用于:接收所述 SPC根据所述第一业务使能器的标识、所述第一业务 流的业务类型和各个业务使能器当前的负载状态中的至少一种确定并且发 送的所述第二业务路径的标识, 其中第二业务路径经过所述第二业务使能 器。
结合第四方面及其上述实现方式, 在其第七种实现方式中, 所述处理单 元还用于: 根据所述第一业务使能器的标识、 所述第一业务流的业务类型、 所述 PCRF预存的业务路由规则和各个业务使能器当前的负载状态中的至少 一种, 确定经过所述第二业务使能器的第二业务路径。
第五方面, 提供了一种业务路由装置, 包括: 处理单元, 用于确定受到 过载影响的第一业务流, 其中所述第一业务流为按照第一业务路径流经过载 的第一业务使能器的业务流; 所述处理单元确定所述第一业务流的当前会话 状态; 在所述第一业务流的当前会话结束或者所述第一业务流的新会话开始 时, 所述处理单元将第二业务路径的标识分配给所述第一业务流, 以使得所 述第一业务流的所述新会话按照所述第二业务路径流经第二业务使能器, 其 中所述第一业务使能器与所述第二业务使能器相异、 且功能类型相同。
结合第五方面, 在其第一种实现方式中, 所述处理单元具体用于: 获取 所述第一业务路径的标识; 在分配有所述第一业务路径的标识的业务流中确 定所述第一业务流。
结合第五方面及其上述实现方式, 在其第二种实现方式中, 所述装置还 包括接收单元, 所述处理单元具体用于: 获取过载的所述第一业务使能器的 标识, 并根据所述第一业务使能器的标识获取经过所述第一业务使能器的第 一业务路径的标识;或者所述接收单元用于接收业务路径控制器 SPC发送的 所述第一业务路径的标识,其中所述第一业务路径的标识由所述 SPC根据过 载的所述第一业务使能器的标识获取; 或者所述接收单元用于接收策略与计 费规则功能 PCRF实体发送的所述第一业务路径的标识, 其中所述第一业务 路径的标识由所述 PCRF实体根据过载的所述第一业务使能器的标识获取。
结合第五方面及其上述实现方式, 在其第三种实现方式中, 所述接收单 元还用于: 接收所述 PCRF发送的所述第二业务路径的标识, 其中所述第二 业务路径的标识由所述 PCRF根据所述第一业务使能器的标识、 所述第一业 务流的业务类型、 所述 PCRF预存的业务路由规则和各个业务使能器当前的 负载状态中的至少一种确定, 所述第二业务路径经过所述第二业务使能器。
结合第五方面及其上述实现方式, 在其第四种实现方式中, 所述装置还 包括发送单元,所述发送单元用于: 向所述 SPC发送用于请求所述第二业务 路径的标识的请求消息, 以使得所述 SPC根据所述第一业务使能器的标识、 所述第一业务流的业务类型和各个业务使能器当前的负载状态中的至少一 种, 确定经过所述第二业务使能器的第二业务路径; 所述接收单元还用于接 收所述 SPC发送的所述第二业务路径的标识。
结合第五方面及其上述实现方式, 在其第五种实现方式中, 所述接收单 元还用于:接收所述 SPC发送的所述第二业务路径的标识,其中所述第二业 务路径的标识由所述 SPC根据所述第一业务使能器的标识、所述第一业务流 的业务类型和各个业务使能器当前的负载状态中的至少一种确定, 所述第二 业务路径经过所述第二业务使能器。
第六方面, 提供了一种业务路由装置, 包括: 处理单元, 用于获取过载 的第一业务使能器的标识; 所述处理单元根据所述第一业务使能器的标识获 取经过所述第一业务使能器的第一业务路径的标识; 发送单元, 用于向策略 和计费规则功能 PCRF实体或业务流分类器 STC发送所述第一业务路径的标 识,以便于所述 PCRF实体或 STC确定分配有第一业务路径的标识的第一业 务流, 其中所述第一业务流为按照第一业务路径流经过载的第一业务使能器 的业务流; 并且所述处理单元根据所述第一业务使能器的标识、 所述第一业 务流的业务类型、 和各个业务使能器当前的负载状态中的至少一种, 确定经 过第二业务使能器的第二业务路径的标识, 其中所述第一业务使能器与所述 第二业务使能器相异、 且功能相同; 所述发送单元向所述 PCRF实体或所述 STC发送所述第二业务路径的标识, 以便于所述 PCRF实体或所述 STC在 所述第一业务流的当前会话结束或者所述第一业务流的新会话开始时,将所 述第二业务路径的标识分配给所述第一业务流,使得所述第一业务流的所述 新会话按照所述第二业务路径流经第二业务使能器。
结合第六方面, 在其第一种实现方式中, 所述装置还包括接收单元, 所 述接收单元用于:接收所述 PCRF实体或所述 STC发送的用于请求所述第二 业务路径的标识的请求消息。
第七方面, 提供了一种业务路由装置, 包括存储器、处理器、发射电路, 存储器存储使得处理器执行以下操作的指令: 确定受到过载影响的第一业务 流, 其中所述第一业务流为按照第一业务路径流经过载的第一业务使能器的 业务流; 通过所述发射电路向业务流分类器 STC发送第二业务路径的标识, 以使得所述 STC在所述第一业务流的当前会话结束或者所述第一业务流的 新会话开始时, 将所述第二业务路径的标识分配给所述第一业务流, 使得所 述第一业务流的所述新会话按照所述第二业务路径流经第二业务使能器, 其 中所述第一业务使能器与所述第二业务使能器相异、 且功能类型相同。
结合第七方面, 在其第一种实现方式中, 所述处理器具体用于获取过载 的所述第一业务使能器的标识; 根据所述第一业务使能器的标识获取经过所 述第一业务使能器的第一业务路径的标识; 在分配有所述第一业务路径的标 识的业务流中确定所述第一业务流。
结合第七方面及其上述实现方式, 在其第二种实现方式中, 所述业务路 由装置还包括接收电路, 所述处理器具体用于: 通过所述接收电路接收业务 路径控制器 SPC发送的所述第一业务路径的标识,其中所述第一业务路径的 标识由所述 SPC根据过载的所述第一业务使能器的标识获取;在分配有所述 第一业务路径的标识的业务流中确定所述第一业务流。 结合第七方面及其上述实现方式, 在其第三种实现方式中, 所述处理器 还用于:通过所述发射电路向所述 STC发送事件订阅请求,以使得所述 STC 检测所述第一业务流的事件结果,其中所述事件结果包括所述第一业务流的 当前会话结束或者新会话开始; 通过所述接收电路接收所述 STC在检测到 所述第一业务流的所述事件结果时发送的响应消息; 为所述第一业务流确定 所述第二业务路径的标识
结合第七方面及其上述实现方式, 在其第四种实现方式中, 所述处理器 还用于根据所述第一业务使能器的标识、 所述第一业务流的业务类型、 所述 PCRF预存的业务路由规则和各个业务使能器当前的负载状态中的至少一 种, 确定经过所述第二业务使能器的第二业务路径。
结合第七方面及其上述实现方式, 在其第五种实现方式中, 所述处理器 还用于:通过所述发射单元向所述 SPC发送用于请求所述第二业务路径的标 识的请求消息, 以使得所述 SPC根据所述第一业务使能器的标识、所述第一 业务流的业务类型和各个业务使能器当前的负载状态中的至少一种,确定经 过所述第二业务使能器的第二业务路径; 通过所述接收单元接收所述 SPC 发送的所述第二业务路径的标识。
结合第七方面及其上述实现方式, 在其第六种实现方式中, 所述接收电 路还用于:接收所述 SPC根据所述第一业务使能器的标识、所述第一业务流 的业务类型和各个业务使能器当前的负载状态中的至少一种确定并且发送 的所述第二业务路径的标识, 其中第二业务路径经过所述第二业务使能器。
结合第七方面及其上述实现方式, 在其第七种实现方式中, 所述处理器 还用于: 根据所述第一业务使能器的标识、 所述第一业务流的业务类型、 所 述 PCRF预存的业务路由规则和各个业务使能器当前的负载状态中的至少一 种, 确定经过所述第二业务使能器的第二业务路径。
第八方面, 提供了一种业务路由装置, 包括存储器、 处理器, 存储器存 储使得处理器执行以下操作的指令: 确定受到过载影响的第一业务流, 其中 所述第一业务流为按照第一业务路径流经过载的第一业务使能器的业务流; 确定所述第一业务流的当前会话状态; 在所述第一业务流的当前会话结束或 者所述第一业务流的新会话开始时,将第二业务路径的标识分配给所述第一 业务流, 以使得所述第一业务流的所述新会话按照所述第二业务路径流经第 二业务使能器, 其中所述第一业务使能器与所述第二业务使能器相异、 且功 能类型相同。
结合第八方面, 在其第一种实现方式中, 所述处理器具体用于: 获取所 述第一业务路径的标识; 在分配有所述第一业务路径的标识的业务流中确定 所述第一业务流。
结合第八方面及其上述实现方式, 在其第二种实现方式中, 所述业务路 由装置还包括接收电路, 所述处理器具体用于: 获取过载的所述第一业务使 能器的标识, 并根据所述第一业务使能器的标识获取经过所述第一业务使能 器的第一业务路径的标识; 或者通过所述接收电路接收业务路径控制器 SPC 发送的所述第一业务路径的标识,其中所述第一业务路径的标识由所述 SPC 根据过载的所述第一业务使能器的标识获取; 或者通过所述接收电路接收策 略与计费规则功能 PCRF实体发送的所述第一业务路径的标识, 其中所述第 一业务路径的标识由所述 PCRF实体根据过载的所述第一业务使能器的标识 获取。
结合第八方面及其上述实现方式, 在其第三种实现方式中, 所述接收电 路还用于: 接收所述 PCRF发送的所述第二业务路径的标识, 其中所述第二 业务路径的标识由所述 PCRF根据所述第一业务使能器的标识、 所述第一业 务流的业务类型、 所述 PCRF预存的业务路由规则和各个业务使能器当前的 负载状态中的至少一种确定, 所述第二业务路径经过所述第二业务使能器。
结合第八方面及其上述实现方式, 在其第四种实现方式中, 所述业务路 由装置还包括发射电路,所述发射电路用于: 向所述 SPC发送用于请求所述 第二业务路径的标识的请求消息,以使得所述 SPC根据所述第一业务使能器 的标识、所述第一业务流的业务类型和各个业务使能器当前的负载状态中的 至少一种, 确定经过所述第二业务使能器的第二业务路径; 所述接收电路还 用于接收所述 SPC发送的所述第二业务路径的标识。
结合第八方面及其上述实现方式, 在其第五种实现方式中, 所述接收电 路还用于:接收所述 SPC发送的所述第二业务路径的标识,其中所述第二业 务路径的标识由所述 SPC根据所述第一业务使能器的标识、所述第一业务流 的业务类型和各个业务使能器当前的负载状态中的至少一种确定, 所述第二 业务路径经过所述第二业务使能器。
第九方面, 提供了一种业务路由装置, 包括存储器、处理器、发射电路, 存储器存储使得处理器执行以下操作的指令: 获取过载的第一业务使能器的 标识; 根据所述第一业务使能器的标识获取经过所述第一业务使能器的第一 业务路径的标识; 通过所述发射电路向策略和计费规则功能 PCRF实体或业 务流分类器 STC发送所述第一业务路径的标识, 以便于所述 PCRF实体或 STC确定分配有第一业务路径的标识的第一业务流,其中所述第一业务流为 按照第一业务路径流经过载的第一业务使能器的业务流; 并且根据所述第一 业务使能器的标识、 所述第一业务流的业务类型、 和各个业务使能器当前的 负载状态中的至少一种, 确定经过第二业务使能器的第二业务路径的标识, 其中所述第一业务使能器与所述第二业务使能器相异、 且功能相同; 通过所 便于所述 PCRF实体或所述 STC在所述第一业务流的当前会话结束或者所述 第一业务流的新会话开始时,将所述第二业务路径的标识分配给所述第一业 务流,使得所述第一业务流的所述新会话按照所述第二业务路径流经第二业 务使能器。
结合第九方面, 在其第一种实现方式中, 所述业务路由装置还包括接收 电路,所述接收电路用于:接收所述 PCRF实体或所述 STC发送的用于请求 所述第二业务路径的标识的请求消息。
本发明实施例在第一业务使能器过载时,通过确定流经该第一业务使能 器的业务流的当前会话状态来决定何时将第一业务使能器的业务流迁移至 第二业务使能器,从而在解决业务使能器过载的同时能够保证用户业务不中 断, 提高了用户体验。 附图说明
为了更清楚地说明本发明实施例的技术方案, 下面将对本发明实施例中 所需要使用的附图作简单地介绍, 显而易见地, 下面所描述的附图仅仅是本 发明的一些实施例, 对于本领域普通技术人员来讲, 在不付出创造性劳动的 前提下, 还可以根据这些附图获得其他的附图。
图 1是业务路由系统的示意框图。
图 2是本发明一个实施例的业务路由方法的流程图。
图 3是本发明一个实施例的业务路由系统的交互图。
图 4是本发明另一实施例的业务路由系统的交互图。
图 5是本发明另一实施例的业务路由系统的交互图。 图 6是本发明另一实施例的业务路由系统的交互图。
图 7是本发明一个实施例的业务路由方法的流程图。
图 8是本发明一个实施例的业务路由系统的交互图。
图 9是本发明另一实施例的业务路由系统的交互图。
图 10是本发明另一实施例的业务路由系统的交互图。
图 11是本发明一个实施例的业务路由装置 (PCRF ) 的示意框图。
图 12是本发明一个实施例的业务路由装置 (STC ) 的示意框图。
图 13是本发明一个实施例的业务路由装置 (SPC ) 的示意框图。
图 14是本发明另一实施例的业务路由装置 (PCRF ) 的示意框图。
图 15是本发明另一实施例的业务路由装置 (STC)的示意框图。
图 16是本发明另一实施例的业务路由装置 (SPC)的示意框图。 具体实施方式
下面将结合本发明实施例中的附图,对本发明实施例中的技术方案进行 清楚、 完整地描述, 显然, 所描述的实施例是本发明的一部分实施例, 而不 是全部实施例。 基于本发明中的实施例, 本领域普通技术人员在没有做出创 造性劳动的前提下所获得的所有其他实施例, 都应属于本发明保护的范围。
本发明的技术方案, 可以应用于各种通信系统, 例如: 全球移动通信系 统 ( Global System of Mobile communication, GSM ),码分多址 ( Code Division Multiple Access , CDMA ) 系统, 宽带码分多址(Wideband Code Division Multiple Access , WCDMA ) , 通用分组无线业务 ( General Packet Radio Service, GPRS ), 长期演进( Long Term Evolution, LTE )等。
图 1是业务路由系统的示意框图。 如图 1所示, 业务路由系统可以包括 策略和计费规则功能(Policy and Charging Rules Function, PCRF ), 业务流 分类器 (Service Traffic Classifier, STC ), 业务路径控制器 (Service Path Controller, SPC )、 SE管理器( SE Manager )、业务使能器监视器( SE Monitor )、 至少一个交换设备( Switch )和 n个 SE服务器。 其中 n个 SE服务器根据功 能的被划分为至少一个业务使能器池(SE pool ) 或增值业务服务池(VAS Pool ), 例如 SE1和 SE2属于第一个 SE Pool l, SE a、 SE b和 SE c属于第二 个 SE Pool 2。
业务使能器 SE可以指能够提供增值业务的网元, 例如可以是视频优化 器、 防火墙、 业务流压缩器、 网络(Web )緩存器、 深度报文探测器或超文 本传输协议 ( Hypertext Transfer Protocol, HTTP ) 头增强器等。
STC具有业务流检测 /识别的功能, 可以检测 /识别业务流的业务类型, 并且在获取业务流对应的业务路径标识后对该业务流中的数据进行封装操 作, 以使得该业务流按照该业务路径被处理。
SPC具有业务路径选择的功能, 可以根据各个 SE的功能类型、 负载状 态以及网络状态确定具体处理该业务流的一个或多个 SE。
SE Manager具有管理各个 SE的功能,可以获得 SE的网络拓朴等信息。 SE Monitor能够监控各个 SE的负载状态以及是否发生故障等。
上述业务流可以是上行业务流, 也可以指下行业务流, 本发明实施例对 此不做限定。
其中 PCRF和 STC, 与 SPC、 SE Monitor和 SE Manage中的至少一个具 有连接关系, 具体来说, PCRF可以与 SPC、 SE Monitor和 SE Manage中的 任意一个具有连接关系, SPC、 SE Monitor和 SE Manage三者之间的相互连 接关系使得 PCRF可以与三者中的任意一个网元进行交互, STC也可以通过 PCRF与 SPC、 SE Monitor和 SE Manage三者进行交互; 类似地, STC也可 以与 SPC、 SE Monitor和 SE Manage中的任意一个具有连接关系,从而 STC 和 PCRF能够与 SPC、 SE Monitor和 SE Manage三者进行交互。
应理解, 图 1 中仅仅示出了上述多种连接方式中的一种连接方式, 即 PCRF与 SPC相连接, STC可以通过 PCRF与 SPC、 SE Monitor和 SE Manage 进行交互, PCRF可以通过 SPC与 SE Monitor, SE Manage进行交互, 但本 发明实施例中的连接方式并不限于此。
基于上述连接关系, SPC、 SE Monitor和 SE Manage存储或获取的关于 SE的负载情况、配置、权重等信息可以发送至 PCRF和 STC—侧,以便 PCRF 和 STC能够根据 SE的负载情况、 配置、 权重等信息来为用户设备 UE的业 务流确定并分配具体的业务路径标识; 而 SPC也可以通过与 PCRF、 STC之 间的连接关系从 PCRF和 STC—侧获取关于 UE的业务流的情况,从而 SPC 也可以为 UE的业务流确定并分配具体的业务路径标识。
具体地, PCRF处配置有业务路由策略和 SE pool中各个 SE的权重, 其 中, 各个 SE的权重主要与各个 SE的处理能力相关, 处理能力较高的 SE具 有较高的权重值,相应地, 处理能力较低的 SE具有较低的权重值。在 PCRF 和 STC进行负载分配时,可以根据权重轮询调度算法( Weighted Round-Robin Scheduling )或其他均衡算法优先将业务流分配至权重较高的 SE, 其中各个 SE的权重可以是根据 SE的配置、 处理的具体业务在 PCRF或 SE Manager 或 SPC处预先配置的,在调用时由 PCRF从 PCRF本地或者 SE Manager/SPC 处获取。 应理解, SE Manage和 SE Monitor可以分别独立部署, 也可以联合 部署, 主要用于监视、 配置和管理各个 SE。 PCRF在为 UE建立互联网协议 ( Internet Protocol, IP )连接访问网络 ( IP-Connectivity Access Network, IP-CAN )会话时, 可以根据 UE的业务类型和各个 SE的权重在需要的一个 或多个 SE pool中为 UE选择好一个或一系列 SE, 并为该 UE分配业务路径 标识, 之后 PCRF将业务路径标识和该业务路径上的一个或一系列 SE的标 识(Identification, ID )一并发送给 SPC。 具体地, SE ID可以预先配置在 PCRF处的数据库中, 也可以从 SE Manager或 SPC处获取, SE ID可以是 SE的 IP地址、 统一资源定位符 ( Uniform Resource Locator, URL )或其他 自定义标识, 例如, 可以用 1-1表示第一个 SE Pool l中的 SE1, 或者 2-b表 示第二个 SE Pool 2中的 SE b。 SPC根据业务路径标识计算好具体的流表下 发给相关的交换机 Switch以使得相关 Switch能够将 UE业务流按顺序分配 到上述一个或一系列 SE上。
或者, 也可以由 STC从 PCRF处获取业务路由策略, 其中包括 UE的接 入类型 (如 2G/3G/4G接入), UE的用户签约类型 (如金、 银、 铜、 普通用 户), 业务类型 (如视频、 语音)对应的业务路由上的 SE Pool, 作为一个简 单的例子,业务类型为视频的业务流可能需要经过具有网络緩存 (Web Cache) 功能的 SE Pool以及具有视频优化 ( Video Optimization ) 功能的 SE Pool。
在 UE的业务流到来时, STC需要根据 SE的权重在需要的一个或多个 SE pool中为 UE选择好一个或一系列 SE, 并为该 UE的业务流分配业务路 径标识,之后 STC将业务路径标识和该业务路径上的一个或一系列 SE的 ID 一并发送给 SPC。 具体地, SE的 ID可以是 PCRF预先从 SPC处获取的, 例 如 SE的 IP地址、 URL, 也可以示例性地用 1-1表示第一个 SE Pool 1中的 SE1, 或者 2-b表示第二个 SE Pool 2中的 SE b。 SPC根据业务路径标识计算 好具体的流表下发给相关的 Switch以使得相关 Switch能够将 UE的业务流 分配到上述一个或一系列 SE上, 从而完成将业务流分配到各个 SE的初始 负载均衡。 图 2是本发明一个实施例的业务路由方法的流程图。 图 2的方法由策略 和计费规则功能 PCRF实体执行。
S201,策略和计费规则功能 PCRF实体确定受到过载影响的第一业务流, 其中第一业务流为按照第一业务路径流经过载的第一业务使能器的业务流; S202, PCRF实体向业务流分类器 STC发送第二业务路径的标识, 以使 得 STC在第一业务流的当前会话结束或者第一业务流的新会话开始时, 将 第二业务路径的标识分配给第一业务流,使得第一业务流的新会话按照第二 业务路径流经第二业务使能器, 其中第一业务使能器与第二业务使能器相 异、 且功能类型相同。
本发明实施例在第一业务使能器过载时,通过确定流经该第一业务使能 器的业务流的当前会话状态来决定何时将第一业务使能器的业务流迁移至 第二业务使能器,从而在解决业务使能器过载的同时能够保证用户业务不中 断, 提高了用户体验。
应理解, UE的第一业务流具有特定的业务类型(即功能类型), 用于完 成某一项任务或请求, 该第一业务流可以由至少一个会话组成, 也就是说组 成第一业务流的多个会话也具有相同的业务类型,且用于完成某一项任务或 请求,每个会话开始时建立 UE与服务器之间的传输控制协议( Transmission Control Protocol, TCP )连接, TCP将会话包含的数据流分割成适当长度的 数据报文以便传输, 当会话结束时 TCP连接释放。 因此会话中途终止业务 流会导致 TCP连接中断, 从而导致业务中断。
可选地,作为一个实施例, PCRF实体确定受到过载影响的第一业务流, 包括: 获取过载的第一业务使能器的标识; 根据第一业务使能器的标识获取 经过第一业务使能器的第一业务路径的标识; 在分配有第一业务路径的标识 的业务流中确定第一业务流。
首先, 可以由 PCRF实体对业务使能器进行过载检测。 具体地, 在第一 业务使能器发生过在时, PCRF可以获知第一业务使能器的标识(SE ID )。 第一业务使能器的 SE ID可以是 SE Monitor检测到第一业务使能器过载后发 送给 PCRF的,即 PCRF可以从 SE Monitor处获取第一业务使能器的 SE ID。 可选地, PCRF也可以通过向 SE Monitor发送请求消息来获取过载的第一业 务使能器的标识。 其中, 第一业务使能器的标识可以是第一业务使能器的 IP 地址或 URL等, 本发明对此并不限定。 此外, 由于 SE Manager和 SE Monitor可以是分别独立部署的, 也可以 是联合部署的, 因此过载业务使能器的标识也可以是由 SE Manager发送给 PCRF的, SE Manager可以自行检测到过载的第一业务使能器,也可以从 SE Monitor处获取第一业务使能器的 SE ID后发送至 PCRF。
由于最初对业务流进行负载分配的 PCRF设备或 STC在为 UE的业务流 分配业务路径标识时,存储有业务路径的标识和业务使能器的标识之间的对 应关系, 因此, 当第一业务使能器被检测到过载时, PCRF可以根据第一业 务使能器的标识确定受到过载影响的 UE的第一业务流。 具体地, PCRF首 先可以根据第一业务使能器的标识, 以及上述业务路径的标识和业务使能器 的标识之间的对应关系, 确定经过第一业务使能器的第一业务路径的标识。 应理解, 经过第一业务使能器的业务路径可以有不止一条, 按照这些业务路 径流经第一业务使能器的业务流都是受到过载影响的业务流。 PCRF根据第 一业务路径的标识确定第一业务流的标识, 第一业务流可以是 PCRF在分配 有第一业务路径的标识的多个业务流中随机选取的。
可选地,作为一个实施例, PCRF实体确定受到过载影响的第一业务流, 包括:接收业务路径控制器 SPC发送的第一业务路径的标识,其中第一业务 路径的标识由 SPC根据过载的第一业务使能器的标识获取;在分配有第一业 务路径的标识的业务流中确定第一业务流。
具体而言, 业务使能器的过载检测由 SPC 完成, SPC 可以通过 SE Monitor/SE Manager检测到第一业务使能器过载, 也就是说, SPC对于业务 使能器的过载检测过程, 可以是 SPC对于过载业务使能器的标识的获取过 程。 此外, SPC也可以通过向 SE Monitor/SE Manager发送请求消息来获取 过载的第一业务使能器的标识。
SPC检测到第一业务使能器过载后,可以根据第一业务使能器的标识确 定经过第一业务使能器的第一业务路径的标识, 并将第一业务路径的标识发 送至 PCRF。 其中, 由于最初对业务流进行负载分配的 PCRF设备或 STC在 为 UE的业务流分配业务路径标识时, 会将业务路径的标识和该业务路径经 过的业务使能器的标识之间的对应关系一并发送给 SPC, 所以 PCRF设备、 STC或 SPC都可以通过上述对应关系确定第一业务使能器的标识对应于哪 些业务路径标识, 即确定哪些业务路径受到了过载的影响。
PCRF接收到 SPC发送的第一业务路径的标识后, 可以根据第一业务路 径的标识确定第一业务流, 应理解, 经过第一业务使能器的业务路径可以有 不止一条,按照这些业务路径流经第一业务使能器的业务流都是受到过载影 响的业务流。 PCRF根据第一业务路径的标识确定受到过载影响的第一业务 流, 第一业务流可以是 PCRF在分配有第一业务路径的标识的多个业务流中 随机选取的。
可选地,作为一个实施例,在 PCRF实体向 STC发送第二业务路径的标 识之前, 方法还包括: 向 STC发送事件订阅请求, 以使得 STC检测第一业 务流的事件结果,其中事件结果包括第一业务流的当前会话结束或者新会话 开始; 接收 STC在检测到第一业务流的事件结果时发送的响应消息; 为第 一业务流确定第二业务路径的标识。
PCRF实体在确定了受到过载影响的第一业务流后,可以向 STC发送针 对该第一业务流的事件订阅请求, 以请求 STC在检测到第一业务流的当前 会话结束或新的会话开始时, 响应该事件订阅请求。
其中, UE的第一业务流具有特定的业务类型(即功能类型), 用于完成 某一项任务或请求, 该第一业务流可以由至少一个会话组成, 也就是说组成 第一业务流的多个会话也具有相同的业务类型,且用于完成某一项任务或请 求,每个会话开始时建立 UE与服务器之间的 TCP连接, TCP将会话包含的 数据流分割成适当长度的数据报文以便传输, 当会话结束时 TCP连接释放。 因此会话中途终止业务流会导致 TCP连接中断, 从而导致业务中断。
具体地, PCRF可以根据应用检测控制 (Application Detection Control,
ADC )规则来生成上述事件订阅请求, 以便于从 STC处订阅第一业务流的 事件的开始和结束。 此外, PCRF也可以针对受到过载影响的 UE进行事件 订阅, 本发明对此并不限定。
STC在检测到第一业务流的当前会话结束或新的会话开始时,通过响应 消息将该事件通知 PCRF。 PCRF在接收到 STC发送的响应消息时, 可以为 第一业务流确定新的业务路径标识。 应理解, PCRF也可以在检测到第一业 务使能器过载之后,到 PCRF准备向 STC发送新的业务路径标识之前的时段 内的任意时刻为第一业务流确定新的业务路径标识, 本发明对此并不限定。
可选地, 作为一个实施例, 为第一业务流确定第二业务路径的标识, 包 括: 根据第一业务使能器的标识、 第一业务流的业务类型、 PCRF预存的业 务路由规则和各个业务使能器当前的负载状态中的至少一种,确定经过第二 业务使能器的第二业务路径。
为第一业务流确定新的业务路径标识 (即第二业务路径的标识), 具体 地, PCRF可以根据第一业务使能器的标识、 第一业务流的业务类型、 PCRF 预存的业务路由规则和各个业务使能器当前的负载状态中的至少一种,确定 经过第二业务使能器的第二业务路径。
作为一个最简单的实施例, PCRF可以将第一业务路径中的第一业务使 能器替换为第二业务使能器, 形成第二业务路径。 第二业务使能器可以是与 第一业务使能器位于同一个 SE Pool的不同业务使能器, 即功能相同、 个体 相异。 此外, 第二业务使能器也可以是 PCRF根据各个业务使能器的负载状 态确定的, 例如在第一业务使能器所属的 SE Pool中确定当前负载最低的业 务使能器为第二业务使能器。 应理解, PCRF也可以根据业务路由规则重新 确定第二业务路径的标识, 并且满足第二业务路径不经过第一业务使能器的 条件。
可选地, 作为一个实施例, 为第一业务流确定第二业务路径的标识, 包 括: 向 SPC发送用于请求第二业务路径的标识的请求消息, 以使得 SPC根 据第一业务使能器的标识、第一业务流的业务类型和各个业务使能器当前的 负载状态中的至少一种, 确定经过第二业务使能器的第二业务路径; 接收 SPC发送的第二业务路径的标识。
当由 SPC对业务使能器进行过载检测时, 由于 SPC处有第一业务使能 器的 SE ID, 因此新的业务路径标识可以由 SPC确定。 具体地, PCRF在接 收到 SPC发送的第一业务路径标识,并确定了第一业务流后,便可以向 SPC 发送请求消息, 以请求新的业务路径标识。 请求消息可以携带有第一业务路 径的标识或第一业务流对应的 UE的标识。 在接收到 PCRF发送的请求消息 后, SPC 为第一业务流确定新的业务路径标识(即第二业务路径的标识), 第二业务路径标识的确定方法可以参照上述实施例, 此处不再赘述。 SPC在 确定第二业务路径的标识后, 将其发送至 PCRF, 以便于 PCRF将第二业务 路径的标识发送至 STC, 由 STC应用第二业务路径的标识。
可选地, 作为一个实施例, 向 STC发送事件订阅请求之前, 还包括: 接收 SPC根据第一业务使能器的标识、第一业务流的业务类型和各个业务使 能器当前的负载状态中的至少一种确定并且发送的第二业务路径的标识, 其 中第二业务路径经过第二业务使能器。 具体地, SPC可以根据第一业务使能器的标识、 第一业务流的业务类型 和各个业务使能器当前的负载状态中的至少一种,确定经过第二业务使能器 的第二业务路径。 作为一个最简单的实施例, SPC可以将第一业务路径中的 第一业务使能器替换为第二业务使能器, 形成第二业务路径。 第二业务使能 器可以是与第一业务使能器位于同一个 SE Pool的不同业务使能器, 即功能 相同、 个体相异。 此外, 第二业务使能器也可以是 SPC根据各个业务使能器 的负载状态确定的, 例如在第一业务使能器所属的 SE Pool中确定当前负载 最低的业务使能器为第二业务使能器。 应理解, SPC也可以根据 PCRF发送 的业务路由规则重新确定第二业务路径的标识, 并且满足第二业务路径不经 过第一业务使能器的条件。
可选地, 作为一个实施例, PCRF实体向业务流分类器 STC发送第二业 务路径的标识之前, 还包括: 根据第一业务使能器的标识、 第一业务流的业 务类型、 PCRF预存的业务路由规则和各个业务使能器当前的负载状态中的 至少一种, 确定经过第二业务使能器的第二业务路径。
在 PCRF检测到第一业务使能器过载后, 并确定受到过载影响的第一业 务流后, 可以直接为第一业务流确定第二业务路径的标识, 将该第二业务路 径的标识发送至 STC处, 由 STC根据第一业务流的会话状态自行确定合适 应用第二业务路径的标识。
本发明实施例通过 PCRF确定受到第一业务使能器过载影响的第一业务 流, 确定或者获取了不经过第一业务使能器的第二业务路径后, 将该第二业 务路径的标识发送至 STC。 使得 STC在第一业务流的当前会话结束或者第 一业务流的新会话开始时, 将第二业务路径的标识分配给第一业务流。 从而 第一业务流可以在会话间歇时段更改路径,按照第二业务路径流经第二业务 使能器, 避免继续通过第一业务使能器受到过载影响, 并加重过载的第一业 务使能器的负载。 也就是说, 在为过载的业务使能器减轻负载压力的同时能 够保证业务的连续性, 不会出现丟包、 服务中断等现象, 提高用户体验。
图 3是本发明一个实施例的业务路由方法的交互图。 图 3所示的实施方 式可以作为图 2 中实施例的一个或多个具体实施方式。 该实施方式主要由 PCRF实体和 STC执行, 由 PCRF对业务使能器进行过载检测, 并由 PCRF 确定新的业务路径标识。 具体地:
S301 , PCRF实体对业务使能器进行过载检测。 首先, PCRF实体可以对业务使能器进行过载检测, 例如在第一业务使 能器发生过载时, PCRF可以获知第一业务使能器的标识(SE ID )。 具体地, PCRF本身无法感知业务使能器的状态, 第一业务使能器的标识可以是 SE Monitor检测到第一业务使能器过载后发送给 PCRF的, 也就是说, PCRF对 于业务使能器的过载检测过程, 可以是 PCRF对于过载业务使能器的标识的 获取过程。 此外, PCRF也可以通过向 SE Monitor发送请求消息来获取过载 的第一业务使能器的标识。
应理解,过载业务使能器的标识还可以是通过 SE Manager发送给 PCRF 的。具体地,第一业务使能器的标识可以是第一业务使能器的 IP地址或 URL 等, 本发明对此并不限定。
5302, PCRF确定受到过载影响的第一业务流。
由于最初对业务流进行负载分配的 PCRF设备或 STC在为 UE的业务流 分配业务路径标识时,存储有业务路径的标识和业务使能器的标识之间的对 应关系, 因此, 当第一业务使能器被检测到过载时, PCRF可以根据第一业 务使能器的标识确定受到过载影响的 UE的第一业务流。
具体地, PCRF首先可以根据第一业务使能器的标识, 以及上述业务路 径的标识和业务使能器的标识之间的对应关系,确定经过第一业务使能器的 第一业务路径的标识。 应理解, 经过第一业务使能器的业务路径可以有不止 一条,按照这些业务路径流经第一业务使能器的业务流都是受到过载影响的 业务流。 PCRF根据第一业务路径的标识确定第一业务流的标识, 第一业务 流可以是 PCRF在分配有第一业务路径的标识的多个业务流中随机选取的。
还应理解,为了便于描述 PCRF在进行负载重分配时对于业务流的操作, 上述过程以第一业务流作为描述主体, 实际上 PCRF在进行负载重分配时可 以是多次随机选取受到过载影响的业务流进行负载重分配,也可以是随机批 量选取受到过载影响的业务流来进行负载重分配的, 本发明对此并不限定。
此外, PCRF确定经过第一业务使能器的第一业务路径的标识后, 也可 以确定被分配第一业务路径的标识的业务流对应的 UE的 ID,后续操作针对 该 UE的业务流进行, 该 UE可能有多个业务流都经过第一业务使能器。 也 就是说, PCRF在对过载的 SE进行负载重分配时, 可以以业务流为粒度进 行, 也可以以 UE为粒度进行, 本发明对此并不限定。
5303 , PCRF向 STC发送事件订阅请求。 PCRF实体在确定了受到过载影响的第一业务流后,可以向 STC发送针 对该第一业务流的事件订阅请求, 以请求 STC在检测到第一业务流的当前 会话结束或新的会话开始时, 响应该事件订阅请求。
其中, UE的第一业务流具有特定的业务类型(即功能类型), 用于完成 某一项任务或请求, 该第一业务流可以由至少一个会话组成, 也就是说组成 第一业务流的多个会话也具有相同的业务类型,且用于完成某一项任务或请 求,每个会话开始时建立 UE与服务器之间的 TCP连接, TCP将会话包含的 数据流分割成适当长度的数据报文以便传输, 当会话结束时 TCP连接释放。 因此会话中途终止业务流会导致 TCP连接中断, 从而导致业务中断。
具体地, PCRF可以根据应用检测控制 (Application Detection Control,
ADC )规则来生成上述事件订阅请求, 以便于从 STC处订阅第一业务流的 事件的开始和结束。 此外, PCRF也可以针对受到过载影响的 UE进行事件 订阅, 本发明对此并不限定。
S304, STC响应 PCRF的事件订阅请求。
STC在检测到第一业务流的当前会话结束或新的会话开始时,将该事件 通知 PCRF。 具体地, STC接收到步骤 S303中的事件订阅请求后, 开始针 对第一业务流进行事件结果检测, 如果第一业务流当前有会话正在进行, 则 STC在检测到该会话结束时, 将当前会话结束的事件结果通知 PCRF。 如果 第一业务流当前没有会话正在进行, 则 STC在检测到新会话的数据报文到 来时, 即新会话开始时, 将新会话开始的事件结果通知 PCRF。
具体地, STC 可以向 PCRF发送用于指示上述事件结果的命令码请求 ( Command-Code Request, CCR )消息来向 PCRF通知第一业务流的当前会 话结束或者新的会话开始。
S305, PCRF为第一业务流确定新的业务路径标识
应理解, 步骤 S305可以在步骤 S302-步骤 S306之间的任意时刻执行, 本发明对此并不限定。
步骤 S305在步骤 S304之后执行时, PCRF在接收到 STC发送的事件结 果后, 为第一业务流确定新的业务路径标识 (即第二业务路径的标识), 具 体地, PCRF可以根据第一业务使能器的标识、第一业务流的业务类型、 PCRF 预存的业务路由规则和各个业务使能器当前的负载状态中的至少一种,确定 经过第二业务使能器的第二业务路径。 作为一个最简单的实施例, PCRF可以将第一业务路径中的第一业务使 能器替换为第二业务使能器, 形成第二业务路径。 第二业务使能器可以是与 第一业务使能器位于同一个 SE Pool的不同业务使能器, 即功能相同、 个体 相异。 此外, 第二业务使能器也可以是 PCRF根据各个业务使能器的负载状 态确定的, 例如在第一业务使能器所属的 SE Pool中确定当前负载最低的业 务使能器为第二业务使能器。 应理解, PCRF也可以根据业务路由规则重新 确定第二业务路径的标识, 并且满足第二业务路径不经过第一业务使能器的 条件。
步骤 S305也可以在步骤 S302之后执行, 也就是说, PCRF在确定受到 过载影响的 UE的第一业务流之后, 便可以确定第二业务路径的标识, 并且 可以将第二业务路径的标识緩存在 PCRF本地等待调用。
S306, PCRF向 STC发送新的业务路径标识
当 PCRF接收到订阅的事件结果,即 STC向 PCRF通知第一业务流的当 前会话结束或者新的会话开始, 并且 PCRF已确定第二业务路径的标识时, PCRF可以发起业务检测功能( Traffic Detection Function, TDF )以触发会话 修改流程, 将第二业务路径的标识发送给 STC。
S307, STC应用新的业务路径标识
STC接收到 PCRF发送的第二业务路径的标识后, 在 STC接收到第一 业务流的新的会话的数据报文时, 为该第一业务流打上第二业务路径标识, 使得第一业务流的新的会话的数据报文按照第二业务路径流经第二业务使 能器,由第二业务使能器代替原来的第一业务使能器处理新的会话。具体地, STC在接收到第一业务流的新的会话的数据报文时,可以将原始的第一业务 路径标识更改为新的第二业务路径标识来对第一业务流的新的会话进行封 装。 此外, STC在应用了第二业务路径的标识后, 可以向 PCRF发送响应消 息。
图 4是本发明一个实施例的业务路由方法的交互图。 图 4所示的实施方 式可以作为图 2 中实施例的一个或多个具体实施方式。 该实施方式主要由 PCRF实体和 STC执行, 由 PCRF对业务使能器进行过载检测, 并由 PCRF 确定新的业务路径标识。 具体地:
S401 , PCRF实体对业务使能器进行过载检测。
首先, PCRF实体可以对进行业务使能器进行过载检测, 例如在第一业 务使能器发生过载时, PCRF可以获知第一业务使能器的标识(SE ID )。 具 体地, PCRF本身无法感知业务使能器的状态, 第一业务使能器的标识可以 是 SE Monitor检测到第一业务使能器过载后发送给 PCRF的, 也就是说, PCRF对于业务使能器的过载检测过程, 可以是 PCRF对于过载业务使能器 的标识的获取过程。 此外, PCRF也可以通过向 SE Monitor发送请求消息来 获取过载的第一业务使能器的标识。
应理解,过载业务使能器的标识还可以是通过 SE Manager发送给 PCRF 的。具体地,第一业务使能器的标识可以是第一业务使能器的 IP地址或 URL 等, 本发明对此并不限定。
S402, PCRF确定受到过载影响的第一业务流。
由于最初对业务流进行负载分配的 PCRF设备或 STC在为 UE的业务流 分配业务路径标识时,存储有业务路径的标识和业务使能器的标识之间的对 应关系, 因此, 当第一业务使能器被检测到过载时, PCRF可以根据第一业 务使能器的标识确定受到过载影响的 UE的第一业务流。
具体地, PCRF首先可以根据第一业务使能器的标识, 以及上述业务路 径的标识和业务使能器的标识之间的对应关系,确定经过第一业务使能器的 第一业务路径的标识。 应理解, 经过第一业务使能器的业务路径可以有不止 一条,按照这些业务路径流经第一业务使能器的业务流都是受到过载影响的 业务流。 PCRF根据第一业务路径的标识确定第一业务流的标识, 第一业务 流可以是 PCRF在分配有第一业务路径的标识的多个业务流中随机选取的。
还应理解,为了便于描述 PCRF在进行负载重分配时对于业务流的操作, 上述过程以单个第一业务流作为描述主体, 实际上 PCRF在进行负载重分配 时可以是多次随机选取受到过载影响的业务流进行负载重分配,也可以是随 机批量选取受到过载影响的业务流来进行负载重分配的, 本发明对此并不限 定。
此外, PCRF确定经过第一业务使能器的第一业务路径的标识后, 也可 以确定被分配第一业务路径的标识的业务流对应的 UE的 ID,后续操作针对 该 UE的业务流进行, 该 UE可能有多个业务流都经过第一业务使能器。 也 就是说, PCRF在对过载的 SE进行负载重分配时, 可以以业务流为粒度进 行, 也可以以 UE为粒度进行, 本发明对此并不限定。
S403, PCRF确定并向 STC下发新的业务路径标识 PCRF在确定受到过载影响的 UE的第一业务流之后, 可以为第一业务 流确定新的业务路径标识(即第二业务路径的标识), 具体地, PCRF可以根 据第一业务使能器的标识、 第一业务流的业务类型、 PCRF预存的业务路由 规则和各个业务使能器当前的负载状态中的至少一种,确定经过第二业务使 能器的第二业务路径。
作为一个最简单的实施例, PCRF可以将第一业务路径中的第一业务使 能器替换为第二业务使能器, 形成第二业务路径。 第二业务使能器可以是与 第一业务使能器位于同一个 SE Pool的不同业务使能器, 即功能相同、 个体 相异。 此外, 第二业务使能器也可以是 PCRF根据各个业务使能器的负载状 态确定的, 例如在第一业务使能器所属的 SE Pool中确定当前负载最低的业 务使能器为第二业务使能器。 应理解, PCRF也可以根据业务路由规则重新 确定第二业务路径的标识, 并且满足第二业务路径不经过第一业务使能器的 条件。
PCRF在确定第二业务路径的标识后, 可以直接下发给 STC, 由 STC确 定何时使用。
应理解, PCRF向 STC发送第二业务路径的标识时, 还可以将第一业务 路径的标识或者第一业务流对应的 UE的标识发送给 STC,以便于 STC获知 第二业务路径的标识的应用对象。
S404, STC根据 UE的会话状态应用新的业务路径标识。
STC在接收到 PCRF发送的第二业务路径的标识时,确定第一业务流的 当前会话状态, 在 STC检测到该会话结束或者新的会话开始时, 为第一业 务流打上第二业务路径的标识,使得第一业务流的新的会话的数据报文按照 第二业务路径流经第二业务使能器, 由第二业务使能器代替原来的第一业务 使能器处理新的会话。 具体地, STC在接收到第一业务流的新的会话的数据 报文时, 可以将原始的第一业务路径标识更改为新的第二业务路径标识来对 第一业务流的新的会话进行封装。
其中, UE的第一业务流具有特定的业务类型(即功能类型), 用于完成 某一项任务或请求, 该第一业务流可以由至少一个会话组成, 也就是说组成 第一业务流的多个会话也具有相同的业务类型,且用于完成某一项任务或请 求,每个会话开始时建立 UE与服务器之间的 TCP连接, TCP将会话包含的 数据流分割成适当长度的数据报文以便传输, 当会话结束时 TCP连接释放。 因此会话中途终止业务流会导致 TCP连接中断, 从而导致业务中断。 此外, STC在应用了第二业务路径的标识后, 可以向 PCRF发送响应消息。
图 5是本发明一个实施例的业务路由方法的交互图。 图 5所示的实施方 式可以作为图 2 中实施例的一个或多个具体实施方式。 该实施方式主要由 PCRF实体、 STC和 SPC执行, 由 SPC对业务使能器进行过载检测, 并由 SPC确定新的业务路径标识。 具体地:
S501, SPC对业务使能器进行过载检测。
首先, SPC可以进行业务使能器的过载检测, 例如在第一业务使能器发 生过载时, SPC可以检测到第一业务使能器的标识 (SE ID )。 具体地, SPC 可以通过 SE Monitor/SE Manager检测到第一业务使能器过载, 也就是说, SPC对于业务使能器的过载检测过程, 可以是 SPC对于过载业务使能器的 标识的获取过程。 此外, SPC也可以通过向 SE Monitor/SE Manager发送请 求消息来获取过载的第一业务使能器的标识。
应理解, 整合有业务使能器检测功能的 SPC也可以自行进行过载检测。 具体地,第一业务使能器的标识可以是第一业务使能器的 IP地址或 URL等, 本发明对此并不限定。
S502, SPC获取受到过载影响的业务路径的标识
SPC检测到第一业务使能器过载后,可以根据第一业务使能器的标识确 定经过第一业务使能器的第一业务路径的标识。 具体地, 由于最初对业务流 进行负载分配的 PCRF设备或 STC在为 UE的业务流分配业务路径标识时, 会将业务路径的标识和该业务路径经过的业务使能器的标识之间的对应关 系一并发送给 SPC, 所以 PCRF设备、 STC或 SPC都可以通过上述对应关 系确定第一业务使能器的标识对应于哪些业务路径标识, 即确定哪些业务路 径受到了过载的影响。 之后, SPC将第一业务路径的标识发送至 PCRF。
S503 , PCRF确定受到过载影响的第一业务流。
PCRF接收到 SPC发送的第一业务路径的标识后, 可以根据第一业务路 径的标识确定第一业务流, 应理解, 经过第一业务使能器的业务路径可以有 不止一条,按照这些业务路径流经第一业务使能器的业务流都是受到过载影 响的业务流。 PCRF根据第一业务路径的标识确定受到过载影响的第一业务 流, 第一业务流可以是 PCRF在分配有第一业务路径的标识的多个业务流中 随机选取的。 应理解, PCRF在对过载的 SE进行负载重分配时, 可以以业务流为粒 度进行, 也可以以 UE为粒度进行, 本发明对此并不限定。
S504, PCRF向 STC发送事件订阅请求。
PCRF实体在确定了受到过载影响的第一业务流后,可以向 STC发送针 对该第一业务流的事件订阅请求, 以请求 STC在检测到第一业务流的当前 会话结束或新的会话开始时, 响应该事件订阅请求。 具体地, PCRF可以根 据 ADC规则来生成上述事件订阅请求, 以便于从 STC处订阅第一业务流的 事件的开始和结束。 此外, PCRF也可以针对受到过载影响的 UE进行事件 订阅, 本发明对此并不限定。
S505 , STC响应 PCRF的事件订阅请求。
STC在检测到第一业务流的当前会话结束或新的会话开始时,将该事件 通知 PCRF。 具体地, STC接收到步骤 S303中的事件订阅请求后, 开始针 对第一业务流进行事件结果检测, 如果第一业务流当前有会话正在进行, 则 STC在检测到该会话结束时, 将当前会话结束的事件结果通知 PCRF。 如果 第一业务流当前没有会话正在进行, 则 STC在检测到新会话的数据报文到 来时, 即新会话开始时, 将新会话开始的事件结果通知 PCRF。 具体地, STC 可以向 PCRF发送用于指示上述事件结果的 CCR消息来向 PCRF通知第一 业务流的当前会话结束或者新的会话开始。
S506, PCRF向 SPC请求新的业务路径标识。
应理解, 步骤 S506可以在步骤 S503-步骤 S507之间的任意时刻执行, 本发明对此并不限定。
PCRF在确定第一业务流后, 便可以向 SPC发送请求消息, 以请求新的 业务路径标识。请求消息可以携带有第一业务路径的标识或第一业务流对应 的 UE的标识。
S507, SPC确定并向 PCRF发送新的业务路径标识
在接收到 PCRF发送的请求消息后, SPC为第一业务流确定新的业务路 径标识 (即第二业务路径的标识), 具体地, SPC 可以根据第一业务使能器 的标识、第一业务流的业务类型和各个业务使能器当前的负载状态中的至少 一种, 确定经过第二业务使能器的第二业务路径。
作为一个最简单的实施例, SPC可以将第一业务路径中的第一业务使能 器替换为第二业务使能器, 形成第二业务路径。 第二业务使能器可以是与第 一业务使能器位于同一个 SE Pool的不同业务使能器, 即功能相同、 个体相 异。此外,第二业务使能器也可以是 SPC根据各个业务使能器的负载状态确 定的, 例如在第一业务使能器所属的 SE Pool中确定当前负载最低的业务使 能器为第二业务使能器。 应理解, SPC也可以根据 PCRF发送的业务路由规 则重新确定第二业务路径的标识, 并且满足第二业务路径不经过第一业务使 能器的条件。
SPC在确定第二业务路径的标识后, 将其发送至 PCRF, 以便于 PCRF 将第二业务路径的标识发送至 STC。
S508, STC应用新的业务路径标识
STC接收到 PCRF发送的第二业务路径的标识后, 在 STC接收到第一 业务流的新的会话的数据报文时, 为该第一业务流打上第二业务路径标识, 使得第一业务流的新的会话的数据报文按照第二业务路径流经第二业务使 能器,由第二业务使能器代替原来的第一业务使能器处理新的会话。具体地, STC在接收到第一业务流的新的会话的数据报文时,可以将原始的第一业务 路径标识更改为新的第二业务路径标识来对第一业务流的新的会话进行封 装。 此外, STC在应用了第二业务路径的标识后, 可以向 PCRF发送响应消 息。
图 6是本发明一个实施例的业务路由方法的交互图。 图 6所示的实施方 式可以作为图 2 中实施例的一个或多个具体实施方式。 该实施方式主要由 PCRF实体、 STC和 SPC执行, 由 SPC对业务使能器进行过载检测, 并由 SPC确定新的业务路径标识。 具体地:
S601, SPC对业务使能器进行过载检测。
首先, SPC可以进行业务使能器的过载检测, 例如在第一业务使能器发 生过载时, SPC可以检测到第一业务使能器的标识 (SE ID )。 具体地, SPC 可以通过 SE Monitor/SE Manager检测到第一业务使能器过载, 也就是说, SPC对于业务使能器的过载检测过程, 可以是 SPC对于过载业务使能器的 标识的获取过程。 此外, SPC也可以通过向 SE Monitor/SE Manager发送请 求消息来获取过载的第一业务使能器的标识。
应理解, 整合有业务使能器检测功能的 SPC也可以自行进行过载检测。 具体地,第一业务使能器的标识可以是第一业务使能器的 IP地址或 URL等, 本发明对此并不限定。 S602, SPC确定并向 PCRF发送受到过载影响的业务路径标识和新的业 务路径标识
SPC检测到第一业务使能器过载后,可以根据第一业务使能器的标识确 定经过第一业务使能器的第一业务路径的标识。 具体地, 由于最初对业务流 进行负载分配的 PCRF设备或 STC在为 UE的业务流分配业务路径标识时, 会将业务路径的标识和该业务路径经过的业务使能器的标识之间的对应关 系一并发送给 SPC, 所以 PCRF设备、 STC或 SPC都可以通过上述对应关 系确定第一业务使能器的标识对应于哪些业务路径标识, 即确定哪些业务路 径受到了过载的影响。
同时, SPC可以根据第一业务使能器的标识和各个业务使能器当前的负 载状态确定第二业务路径的标识。 具体地, SPC可以将第一业务路径中的第 一业务使能器替换为第二业务使能器, 形成第二业务路径。 第二业务使能器 可以是与第一业务使能器位于同一个 SE Pool的不同业务使能器, 即功能相 同、 个体相异。 此外, 第二业务使能器也可以是 SPC根据各个业务使能器的 负载状态确定的, 例如在第一业务使能器所属的 SE Pool中确定当前负载最 低的业务使能器为第二业务使能器。 应理解, SPC也可以根据 PCRF发送的 业务路由规则重新确定第二业务路径的标识, 并且满足第二业务路径不经过 第一业务使能器的条件。
之后, SPC 可以将第一业务路径的标识和第二业务路径的标识发送至 PCRF。
S603 , PCRF确定受到过载影响的第一业务流。
PCRF在接收到 SPC发送的第一业务路径的标识和第二业务路径的标识 之后, 可以将第二业务路径的标识緩存在 PCRF本地以供后续使用, 并根据 第一业务路径的标识确定第一业务流, 应理解, 经过第一业务使能器的业务 路径可以有不止一条,按照这些业务路径流经第一业务使能器的业务流都是 受到过载影响的业务流。 PCRF才艮据第一业务路径的标识确定受到过载影响 的第一业务流, 第一业务流可以是 PCRF在分配有第一业务路径的标识的多 个业务流中随机选取的。 应理解, PCRF在对过载的 SE进行负载重分配时, 可以以业务流为粒度进行,也可以以 UE为粒度进行,本发明对此并不限定。
S604, PCRF向 STC发送事件订阅请求。
PCRF实体在确定了受到过载影响的第一业务流后,可以向 STC发送针 对该第一业务流的事件订阅请求, 以请求 STC在检测到第一业务流的当前 会话结束或新的会话开始时, 响应该事件订阅请求。 具体地, PCRF可以根 据 ADC规则来生成上述事件订阅请求, 以便于从 STC处订阅第一业务流的 事件的开始和结束。 此外, PCRF也可以针对受到过载影响的 UE进行事件 订阅, 本发明对此并不限定。
S605, STC响应 PCRF的事件订阅请求。
STC在检测到第一业务流的当前会话结束或新的会话开始时,将该事件 通知 PCRF。 具体地, STC接收到步骤 S303中的事件订阅请求后, 开始针 对第一业务流进行事件结果检测, 如果第一业务流当前有会话正在进行, 则 STC在检测到该会话结束时, 将当前会话结束的事件结果通知 PCRF。 如果 第一业务流当前没有会话正在进行, 则 STC在检测到新会话的数据报文到 来时, 即新会话开始时, 将新会话开始的事件结果通知 PCRF。 具体地, STC 可以向 PCRF发送用于指示上述事件结果的 CCR消息来向 PCRF通知第一 业务流的当前会话结束或者新的会话开始。
S606, PCRF向 STC发送新的业务路径标识。
在接收到 STC发送的事件结果后, PCRF可以将步骤 S603緩存的第二 业务路径的标识发送至 STC。
S607, STC应用新的业务路径标识
STC接收到 PCRF发送的第二业务路径的标识后, 在 STC接收到第一 业务流的新的会话的数据报文时, 为该第一业务流打上第二业务路径标识, 使得第一业务流的新的会话的数据报文按照第二业务路径流经第二业务使 能器,由第二业务使能器代替原来的第一业务使能器处理新的会话。具体地, STC在接收到第一业务流的新的会话的数据报文时,可以将原始的第一业务 路径标识更改为新的第二业务路径标识来对第一业务流的新的会话进行封 装。 此外, STC在应用了第二业务路径的标识后, 可以向 PCRF发送响应消 息。
图 7是本发明一个实施例的业务路由方法的流程图。 图 7的方法由业务 流分类器 STC执行。
5701 , 业务流分类器 STC确定受到过载影响的第一业务流, 其中第一 业务流为按照第一业务路径流经过载的第一业务使能器的业务流。
5702, STC确定第一业务流的当前会话状态。 S703 , STC在第一业务流的当前会话结束或者第一业务流的新会话开始 时, 将第二业务路径的标识分配给第一业务流, 以使得第一业务流的新会话 按照第二业务路径流经第二业务使能器,其中第一业务使能器与第二业务使 能器相异、 且功能类型相同。
本发明实施例在第一业务使能器过载时,通过确定流经该第一业务使能 器的业务流的当前会话状态来决定何时将第一业务使能器的业务流迁移至 第二业务使能器,从而在解决业务使能器过载的同时能够保证用户业务不中 断, 提高了用户体验。
应理解, UE的第一业务流具有特定的业务类型(即功能类型), 用于完 成某一项任务或请求, 该第一业务流可以由至少一个会话组成, 也就是说组 成第一业务流的多个会话也具有相同的业务类型,且用于完成某一项任务或 请求,每个会话开始时建立 UE与服务器之间的 TCP连接, TCP将会话包含 的数据流分割成适当长度的数据报文以便传输, 当会话结束时 TCP连接释 放。 因此会话中途终止业务流会导致 TCP连接中断, 从而导致业务中断。
可选地,作为一个实施例, STC确定受到过载影响的第一业务流, 包括: 获取第一业务路径的标识; 在分配有第一业务路径的标识的业务流中确定第 一业务流。
STC可以从 PCRF或 SPC处获取第一业务路径的标识, 也可以在 STC 本地获取第一业务路径的标识。其中由 PCRF进行过载检测时,则 STC可以 从 PCRF处获取第一业务路径标识; 由 SPC进行过载检测时, 则 STC可以 从 SPC处获取第一业务路径标识; 由 STC进行过载检测时, 则 STC可以自 行确定第一业务路径的标识。
在获取到第一业务路径的标识后, STC可以根据第一业务路径的标识确 定第一业务流, 具体地, 经过第一业务使能器的业务路径可以有不止一条, 按照这些业务路径流经第一业务使能器的业务流都是受到过载影响的业务 流。 STC根据第一业务路径的标识确定受到过载影响的第一业务流, 第一业 务流可以是 STC在分配有第一业务路径的标识的多个业务流中随机选取的。
可选地, 作为一个实施例, 确定第一业务路径的标识, 包括: 获取过载 的第一业务使能器的标识, 并根据第一业务使能器的标识获取经过第一业务 使能器的第一业务路径的标识;或者接收业务路径控制器 SPC发送的第一业 务路径的标识,其中第一业务路径的标识由 S PC根据过载的第一业务使能器 的标识获取; 或者接收策略与计费规则功能 PCRF实体发送的第一业务路径 的标识, 其中第一业务路径的标识由 PCRF实体根据过载的第一业务使能器 的标识获取。
其中, 在 STC进行过载检测的实施例中, 第一业务使能器的标识可以 是 SE Monitor检测到第一业务使能器过载后发送给 STC的,也就是说, STC 对于业务使能器的过载检测过程, 可以是 STC对于过载业务使能器的标识 的获取过程。 此外, STC也可以通过向 SE Monitor/SE Manager发送请求消 息来获取过载的第一业务使能器的标识。 应理解, 过载业务使能器的标识还 可以是通过 SE Manager发送给 STC的。 STC可以根据第一业务使能器的标 识, 业务路径的标识和业务使能器的标识之间的对应关系, 确定经过第一业 务使能器的第一业务路径的标识。 应理解, 经过第一业务使能器的业务路径 可以有不止一条,按照这些业务路径流经第一业务使能器的业务流都是受到 过载影响的业务流。
在 SPC 进行过载检测的实施例中, 第一业务使能的标识可以是 SE Monitor/SE Manager检测到第一业务使能器过载后发送给 SPC的,也就是说, SPC对于业务使能器的过载检测过程, 可以是 SPC对于过载业务使能器的 标识的获取过程。 此外, SPC也可以通过向 SE Monitor/SE Manager发送请 求消息来获取过载的第一业务使能器的标识。 应理解, 整合有业务使能器检 测功能的 SPC也可以自行进行过载检测。
SPC检测到第一业务使能器过载后,可以根据第一业务使能器的标识确 定经过第一业务使能器的第一业务路径的标识, 并且将第一业务路径的标识 发送至 STC。 具体地, 由于最初对业务流进行负载分配的 PCRF设备或 STC 在为 UE的业务流分配业务路径标识时, 会将业务路径的标识和该业务路径 经过的业务使能器的标识之间的对应关系一并发送给 SPC,所以 PCRF设备、 STC或 SPC都可以通过上述对应关系确定第一业务使能器的标识对应于哪 些业务路径标识, 即确定哪些业务路径受到了过载的影响。
在 PCRF进行过载检测的实施例中, 第一业务使能器的标识可以是 SE Monitor检测到第一业务使能器过载后发送给 PCRF的, 也就是说, PCRF对 于业务使能器的过载检测过程, 可以是 PCRF对于过载业务使能器的标识的 获取过程。 此外, PCRF也可以通过向 SE Monitor/SE Manager发送请求消息 来获取过载的第一业务使能器的标识。 应理解, 过载业务使能器的标识还可 以是通过 SE Manager发送给 PCRF的。 PCRF可以根据第一业务使能器的标 识, 业务路径的标识和业务使能器的标识之间的对应关系, 确定经过第一业 务使能器的第一业务路径的标识。 应理解, 经过第一业务使能器的业务路径 可以有不止一条,按照这些业务路径流经第一业务使能器的业务流都是受到 过载影响的业务流。
可选地, 作为一个实施例, STC确定第一业务流的当前会话状态之前, 还包括: 接收 PCRF发送的第二业务路径的标识, 其中第二业务路径的标识 由 PCRF根据第一业务使能器的标识、 第一业务流的业务类型、 PCRF预存 的业务路由规则和各个业务使能器当前的负载状态中的至少一种确定, 第二 业务路径经过第二业务使能器。
在 PCRF进行过载检测的实施例中, PCRF在确定了经过第一业务使能 器的第一业务路径的标识后, 可以根据第一业务路径的标识确定第一业务流 的标识, 第一业务流可以是 PCRF在分配有第一业务路径的标识的多个业务 流中随机选取的。
PCRF在确定受到过载影响的 UE的第一业务流之后, 可以为第一业务 流确定新的业务路径标识(即第二业务路径的标识), 具体地, PCRF可以根 据第一业务使能器的标识、 第一业务流的业务类型、 PCRF预存的业务路由 规则和各个业务使能器当前的负载状态中的至少一种,确定经过第二业务使 能器的第二业务路径。 作为一个最简单的实施例, PCRF可以将第一业务路 径中的第一业务使能器替换为第二业务使能器, 形成第二业务路径。 第二业 务使能器可以是与第一业务使能器位于同一个 SE Pool的不同业务使能器, 即功能相同、 个体相异。 此外, 第二业务使能器也可以是 PCRF根据各个业 务使能器的负载状态确定的, 例如在第一业务使能器所属的 SE Pool中确定 当前负载最低的业务使能器为第二业务使能器。 应理解, PCRF也可以根据 业务路由规则重新确定第二业务路径的标识, 并且满足第二业务路径不经过 第一业务使能器的条件。 PCRF在确定第二业务路径的标识后, 可以直接下 发给 STC, 由 STC确定何时使用。
可选地,作为一个实施例,接收业务路径控制器 SPC发送的第一业务路 径的标识之后,还包括: 向 SPC发送用于请求第二业务路径的标识的请求消 息, 以使得 SPC根据第一业务使能器的标识、第一业务流的业务类型和各个 业务使能器当前的负载状态中的至少一种,确定经过第二业务使能器的第二 业务路径; 接收 SPC发送的第二业务路径的标识。
在 SPC进行过载检测的实施例中, STC在接收到 SPC发送的第一业务 路径标识后, STC确定第一业务流的当前会话状态, 在第一业务流的当前会 话结束之后, 或者新的会话开始之前, STC向 SPC发送请求消息, 以请求 新的业务路径标识。请求消息可以携带有第一业务路径的标识或第一业务流 对应的 UE的标识。在接收到 STC发送的请求消息后, SPC为第一业务流确 定新的业务路径标识(即第二业务路径的标识), 并将其发送至 STC。
具体地, SPC可以根据第一业务使能器的标识、 第一业务流的业务类型 和各个业务使能器当前的负载状态中的至少一种,确定经过第二业务使能器 的第二业务路径。 作为一个最简单的实施例, SPC可以将第一业务路径中的 第一业务使能器替换为第二业务使能器, 形成第二业务路径。 第二业务使能 器可以是与第一业务使能器位于同一个 SE Pool的不同业务使能器, 即功能 相同、 个体相异。 此外, 第二业务使能器也可以是 SPC根据各个业务使能器 的负载状态确定的, 例如在第一业务使能器所属的 SE Pool中确定当前负载 最低的业务使能器为第二业务使能器。 应理解, SPC也可以根据 PCRF发送 的业务路由规则重新确定第二业务路径的标识, 并且满足第二业务路径不经 过第一业务使能器的条件。
可选地, 作为一个实施例, STC确定第一业务流的当前会话状态之前, 还包括:接收 SPC发送的第二业务路径的标识,其中第二业务路径的标识由 SPC根据第一业务使能器的标识、第一业务流的业务类型和各个业务使能器 当前的负载状态中的至少一种确定, 第二业务路径经过第二业务使能器。
在 SPC进行过载检测的实施例中, SPC可以在确定过载的第一业务使 能器, 并确定第一业务路径标识时, 确定经过第二业务使能器的第二业务路 径标识, 并将第一业务路径标识和第二业务路径标识都发送至 STC。 其中 SPC确定第二业务路径标识可以参照上述实施例, 此处不再赘述。
本发明实施例通过 STC确定受到第一业务使能器过载影响的第一业务 流, 确定或者获取了不经过第一业务使能器的第二业务路径后, 在第一业务 流的当前会话结束或者第一业务流的新会话开始时,将第二业务路径的标识 分配给第一业务流。 从而第一业务流可以在会话间歇时段更改路径, 按照第 二业务路径流经第二业务使能器,避免继续通过第一业务使能器受到过载影 响, 并加重过载的第一业务使能器的负载。 也就是说, 在为过载的业务使能 器减轻负载压力的同时能够保证业务的连续性, 不会出现丟包、 服务中断等 现象, 提高用户体验。
图 8是本发明一个实施例的业务路由方法的流程图。 图 8所示的实施方 式可以作为图 7 中实施例的一个或多个具体实施方式。 该实施方式主要由 STC执行, 由 STC对业务使能器进行过载检测, 并由 STC确定新的业务路 径标识。 具体地:
S801, STC对业务使能器进行过载检测。
首先, STC可以进行业务使能器的过载检测, 例如在第一业务使能器发 生过载时, STC可以检测到第一业务使能器的标识(SE ID )。 具体地, STC 本身无法感知业务使能器的状态, 第一业务使能器的标识可以是 SE Monitor 检测到第一业务使能器过载后发送给 STC的, 也就是说, STC对于业务使 能器的过载检测过程, 可以是 STC对于过载业务使能器的标识的获取过程。 此外, STC也可以通过向 SE Monitor/SE Manager发送请求消息来获取过载 的第一业务使能器的标识。 应理解, 过载业务使能器的标识还可以是通过 SE Manager发送给 STC的。 具体地, 第一业务使能器的标识可以是第一业 务使能器的 IP地址或 URL等, 本发明对此并不限定。
S802, STC确定受到过载影响的第一业务流。
由于最初对业务流进行负载分配的 PCRF设备或 STC在为 UE的业务流 分配业务路径标识时, 留存有业务路径的标识和业务使能器的标识之间的对 应关系, 因此, 当第一业务使能器被检测到过载时, STC可以根据第一业务 使能器的标识确定受到过载影响的 UE的第一业务流。
具体地, STC首先可以根据第一业务使能器的标识, 以及上述业务路径 的标识和业务使能器的标识之间的对应关系,确定经过第一业务使能器的第 一业务路径的标识。 应理解, 经过第一业务使能器的业务路径可以有不止一 条,按照这些业务路径流经第一业务使能器的业务流都是受到过载影响的业 务流。 STC根据第一业务路径的标识确定受到过载影响的第一业务流, 第一 业务流可以是 STC在分配有第一业务路径的标识的多个业务流中随机选取 的。
还应理解, 为了便于描述 STC在进行负载重分配时对于业务流的操作, 上述过程以单个第一业务流作为描述主体, 实际上 STC在进行负载重分配 时可以是多次随机选取第一业务流进行负载重分配,也可以是随机批量选取 业务流来进行负载重分配的, 本发明对此并不限定。
此外, STC确定经过第一业务使能器的第一业务路径的标识后, 也可以 确定被分配第一业务路径的标识的业务流对应的 UE, 后续操作针对该 UE 的业务流进行,该 UE可能有多个业务流都经过第一业务使能器。也就是说, STC在对过载的 SE进行负载重分配时, 可以以业务流为粒度进行, 也可以 以 UE为粒度进行, 本发明对此并不限定。
S803, STC确定新的业务路径标识
STC在确定受到过载影响的 UE的第一业务流之后, 可以为第一业务流 确定新的业务路径标识 (即第二业务路径的标识), 具体地, STC可以根据 第一业务使能器的标识、 第一业务流的业务类型、 PCRF预存的业务路由规 则和各个业务使能器当前的负载状态中的至少一种,确定经过第二业务使能 器的第二业务路径。
作为一个最简单的实施例, STC可以将第一业务路径中的第一业务使能 器替换为第二业务使能器, 形成第二业务路径。 第二业务使能器可以是与第 一业务使能器位于同一个 SE Pool的不同业务使能器, 即功能相同、 个体相 异。 此外, 第二业务使能器也可以是 STC根据各个业务使能器的负载状态 确定的, 例如在第一业务使能器所属的 SE Pool中确定当前负载最低的业务 使能器为第二业务使能器。 应理解, STC也可以根据业务路由规则重新确定 第二业务路径的标识, 并且满足第二业务路径不经过第一业务使能器的条 件。
S804, STC根据 UE的会话状态应用新的业务路径标识。
STC确定第一业务流的当前会话状态, 在 STC检测到该会话结束或者 新的会话开始时, 为第一业务流打上第二业务路径的标识, 使得第一业务流 的新的会话的数据报文按照第二业务路径流经第二业务使能器, 由第二业务 使能器代替原来的第一业务使能器处理新的会话。 具体地, STC在接收到第 一业务流的新的会话的数据报文时, 可以将原始的第一业务路径标识更改为 新的第二业务路径标识来对第一业务流的新的会话进行封装。
图 9是本发明一个实施例的业务路由方法的交互图。 图 9所示的实施方 式可以作为图 7 中实施例的一个或多个具体实施方式。 该实施方式主要由 STC和 SPC执行, 由 SPC对业务使能器进行过载检测, 并由 SPC确定新的 业务路径标识。 具体地: S901, SPC对业务使能器进行过载检测。
首先, SPC可以进行业务使能器的过载检测, 例如在第一业务使能器发 生过载时, SPC可以检测到第一业务使能器的标识 (SE ID )。 具体地, SPC 可以通过 SE Monitor/SE Manager检测到第一业务使能器过载, 也就是说, SPC对于业务使能器的过载检测过程, 可以是 SPC对于过载业务使能器的 标识的获取过程。 此外, SPC也可以通过向 SE Monitor/SE Manager发送请 求消息来获取过载的第一业务使能器的标识。
应理解, 整合有业务使能器检测功能的 SPC也可以自行进行过载检测。 具体地,第一业务使能器的标识可以是第一业务使能器的 IP地址或 URL等, 本发明对此并不限定。
5902, SPC确定受到过载影响的业务路径的标识。
SPC检测到第一业务使能器过载后,可以根据第一业务使能器的标识确 定经过第一业务使能器的第一业务路径的标识。 具体地, 由于最初对业务流 进行负载分配的 PCRF设备或 STC在为 UE的业务流分配业务路径标识时, 会将业务路径的标识和该业务路径经过的业务使能器的标识之间的对应关 系一并发送给 SPC, 所以 PCRF设备、 STC或 SPC都可以通过上述对应关 系确定第一业务使能器的标识对应于哪些业务路径标识, 即确定哪些业务路 径受到了过载的影响。 之后, SPC将第一业务路径的标识发送至 STC。
5903 , STC确定受到过载影响的第一业务流。
STC首先可以根据第一业务路径的标识确定第一业务流, 应理解, 经过 第一业务使能器的业务路径可以有不止一条,按照这些业务路径流经第一业 务使能器的业务流都是受到过载影响的业务流。 STC根据第一业务路径的标 识确定受到过载影响的第一业务流, 第一业务流可以是 STC在分配有第一 业务路径的标识的多个业务流中随机选取的。
应理解, STC在对过载的 SE进行负载重分配时, 可以以业务流为粒度 进行, 也可以以 UE为粒度进行, 本发明对此并不限定。
5904, STC根据会话状态向 SPC请求新的业务路径标识。
STC确定第一业务流的当前会话状态,在第一业务流的当前会话结束之 后, 或者新的会话开始之前, STC向 SPC发送请求消息, 以请求新的业务 路径标识。 请求消息可以携带有第一业务路径的标识或第一业务流对应的 UE的标识。 S905, SPC确定并发送新的业务路径标识
在接收到 STC发送的请求消息后, SPC为第一业务流确定新的业务路 径标识 (即第二业务路径的标识), 具体地, SPC 可以根据第一业务使能器 的标识、第一业务流的业务类型和各个业务使能器当前的负载状态中的至少 一种, 确定经过第二业务使能器的第二业务路径。
作为一个最简单的实施例, SPC可以将第一业务路径中的第一业务使能 器替换为第二业务使能器, 形成第二业务路径。 第二业务使能器可以是与第 一业务使能器位于同一个 SE Pool的不同业务使能器, 即功能相同、 个体相 异。此外,第二业务使能器也可以是 SPC根据各个业务使能器的负载状态确 定的, 例如在第一业务使能器所属的 SE Pool中确定当前负载最低的业务使 能器为第二业务使能器。 应理解, SPC也可以根据 PCRF发送的业务路由规 则重新确定第二业务路径的标识, 并且满足第二业务路径不经过第一业务使 能器的条件。 SPC在确定第二业务路径的标识后, 将其发送至 STC。
S906, STC应用新的业务路径标识
STC接收到 SPC发送的第二业务路径的标识后, 在 STC接收到第一业 务流的新的会话的数据报文时, 为该第一业务流打上第二业务路径标识, 使 得第一业务流的新的会话的数据报文按照第二业务路径流经第二业务使能 器, 由第二业务使能器代替原来的第一业务使能器处理新的会话。 具体地, STC在接收到第一业务流的新的会话的数据报文时,可以将原始的第一业务 路径标识更改为新的第二业务路径标识来对第一业务流的新的会话进行封 装。
此外, STC在应用了第二业务路径的标识后, 可以向 SPC发送响应消 息。
图 10是本发明一个实施例的业务路由方法的交互图。 图 10所示的实施 方式可以作为图 7中实施例的一个或多个具体实施方式。该实施方式主要由 STC和 SPC执行, 由 SPC对业务使能器进行过载检测, 并由 SPC确定新的 业务路径标识。 具体地:
S1001, SPC对业务使能器进行过载检测。
首先, SPC可以进行业务使能器的过载检测, 例如在第一业务使能器发 生过载时, SPC可以检测到第一业务使能器的标识 (SE ID )。 具体地, SPC 可以通过 SE Monitor/SE Manager检测到第一业务使能器过载, 也就是说, SPC对于业务使能器的过载检测过程, 可以是 SPC对于过载业务使能器的 标识的获取过程。 此外, SPC也可以通过向 SE Monitor/SE Manager发送请 求消息来获取过载的第一业务使能器的标识。
应理解, 整合有业务使能器检测功能的 SPC也可以自行进行过载检测。 具体地,第一业务使能器的标识可以是第一业务使能器的 IP地址或 URL等, 本发明对此并不限定。
S 1002, SPC确定并向 STC发送受到过载影响的业务路径标识和新的业 务路径标识。
SPC检测到第一业务使能器过载后,可以根据第一业务使能器的标识确 定经过第一业务使能器的第一业务路径的标识。 具体地, 由于最初对业务流 进行负载分配的 PCRF设备或 STC在为 UE的业务流分配业务路径标识时, 会将业务路径的标识和该业务路径经过的业务使能器的标识之间的对应关 系一并发送给 SPC, 所以 PCRF设备、 STC或 SPC都可以通过上述对应关 系确定第一业务使能器的标识对应于哪些业务路径标识, 即确定哪些业务路 径受到了过载的影响。
同时, SPC可以根据第一业务使能器的标识和各个业务使能器当前的负 载状态确定第二业务路径的标识。 具体地, SPC可以将第一业务路径中的第 一业务使能器替换为第二业务使能器, 形成第二业务路径。 第二业务使能器 可以是与第一业务使能器位于同一个 SE Pool的不同业务使能器, 即功能相 同、 个体相异。 此外, 第二业务使能器也可以是 SPC根据各个业务使能器的 负载状态确定的, 例如在第一业务使能器所属的 SE Pool中确定当前负载最 低的业务使能器为第二业务使能器。 应理解, SPC也可以根据 PCRF发送的 业务路由规则重新确定第二业务路径的标识, 并且满足第二业务路径不经过 第一业务使能器的条件。
之后, SPC 可以将第一业务路径的标识和第二业务路径的标识发送至
STC。
S1003 , STC确定受到过载影响的第一业务流。
STC在接收到 SPC发送的第一业务路径的标识和第二业务路径的标识 之后, 可以将第二业务路径的标识緩存在 STC本地以供后续使用, 并根据 第一业务路径的标识确定第一业务流, 应理解, 经过第一业务使能器的业务 路径可以有不止一条,按照这些业务路径流经第一业务使能器的业务流都是 受到过载影响的业务流。 STC根据第一业务路径的标识确定受到过载影响的 第一业务流, 第一业务流可以是 STC在分配有第一业务路径的标识的多个 业务流中随机选取的。 应理解, STC在对过载的 SE进行负载重分配时, 可 以以业务流为粒度进行, 也可以以 UE为粒度进行, 本发明对此并不限定。
S1004, STC根据会话状态应用新的业务路径标识。
STC确定第一业务流的当前会话状态, 在 STC检测到该会话结束或者 新的会话开始时, 为第一业务流打上步骤 S1002中 STC緩存的第二业务路 径的标识,使得第一业务流的新的会话的数据报文按照第二业务路径流经第 二业务使能器, 由第二业务使能器代替原来的第一业务使能器处理新的会 话。 具体地, STC在接收到第一业务流的新的会话的数据报文时, 可以将原 始的第一业务路径标识更改为新的第二业务路径标识来对第一业务流的新 的会话进行封装。
图 11是本发明一个实施例的业务路由装置(PCRF )的示意框图。 图 11 处理单元 1101确定受到过载影响的第一业务流, 其中第一业务流为按 照第一业务路径流经过载的第一业务使能器的业务流。 发送单元 1102向业 务流分类器 STC发送第二业务路径的标识, 以使得 STC在第一业务流的当 前会话结束或者第一业务流的新会话开始时,将第二业务路径的标识分配给 第一业务流,使得第一业务流的新会话按照第二业务路径流经第二业务使能 器, 其中第一业务使能器与第二业务使能器相异、 且功能类型相同。
本发明实施例在第一业务使能器过载时,通过确定流经该第一业务使能 器的业务流的当前会话状态来决定何时将第一业务使能器的业务流迁移至 第二业务使能器,从而在解决业务使能器过载的同时能够保证用户业务不中 断, 提高了用户体验。
应理解, PCRF实体 1100可以执行上述图 2-图 6中任意实施例的方法。 可选地, 作为一个实施例, 处理单元 1101具体用于: 获取过载的第一 业务使能器的标识; 根据第一业务使能器的标识获取经过第一业务使能器的 第一业务路径的标识; 在分配有第一业务路径的标识的业务流中确定第一业 务流。
具体地, 在第一业务使能器发生过在时, PCRF的处理单元 1101可以获 知第一业务使能器的标识 (SE ID )。 第一业务使能器的 SE ID 可以是 SE Monitor检测到第一业务使能器过载后发送给 PCRF的, 即 PCRF可以从 SE Monitor处获取第一业务使能器的 SE ID。 可选地, PCRF也可以通过向 SE Monitor发送请求消息来获取过载的第一业务使能器的标识。 其中, 第一业 务使能器的标识可以是第一业务使能器的 IP地址或 URL等, 本发明对此并 不限定。
此外, 由于 SE Manager和 SE Monitor可以是分别独立部署的, 也可以 是联合部署的, 因此过载业务使能器的标识也可以是由 SE Manager发送给 PCRF的, SE Manager可以自行检测到过载的第一业务使能器,也可以从 SE Monitor处获取第一业务使能器的 SE ID后发送至 PCRF。
由于最初对业务流进行负载分配的 PCRF设备或 STC在为 UE的业务流 分配业务路径标识时,存储有业务路径的标识和业务使能器的标识之间的对 应关系, 因此, 当第一业务使能器被检测到过载时, PCRF的处理单元 1101 可以根据第一业务使能器的标识确定受到过载影响的 UE的第一业务流。 具 体地, PCRF的处理单元 1101首先可以根据第一业务使能器的标识, 以及上 述业务路径的标识和业务使能器的标识之间的对应关系,确定经过第一业务 使能器的第一业务路径的标识。 应理解, 经过第一业务使能器的业务路径可 以有不止一条,按照这些业务路径流经第一业务使能器的业务流都是受到过 载影响的业务流。 PCRF根据第一业务路径的标识确定第一业务流的标识, 第一业务流可以是 PCRF在分配有第一业务路径的标识的多个业务流中随机 选取的。
可选地, 作为一个实施例, PCRF实体 1100还包括接收单元 1103, 接 收单元 1103用于: 接收业务路径控制器 SPC发送的第一业务路径的标识, 其中第一业务路径的标识由 SPC根据过载的第一业务使能器的标识获取;处 理单元 1101还用于: 在分配有第一业务路径的标识的业务流中确定第一业 务流。
具体而言, 业务使能器的过载检测由 SPC 完成, SPC 可以通过 SE Monitor/SE Manager检测到第一业务使能器过载, 也就是说, SPC对于业务 使能器的过载检测过程, 可以是 SPC对于过载业务使能器的标识的获取过 程。 此外, SPC也可以通过向 SE Monitor/SE Manager发送请求消息来获取 过载的第一业务使能器的标识。
SPC检测到第一业务使能器过载后,可以根据第一业务使能器的标识确 定经过第一业务使能器的第一业务路径的标识, 并将第一业务路径的标识发 送至 PCRF。 其中, 由于最初对业务流进行负载分配的 PCRF设备或 STC在 为 UE的业务流分配业务路径标识时, 会将业务路径的标识和该业务路径经 过的业务使能器的标识之间的对应关系一并发送给 SPC, 所以 PCRF设备、 STC或 SPC都可以通过上述对应关系确定第一业务使能器的标识对应于哪 些业务路径标识, 即确定哪些业务路径受到了过载的影响。
PCRF的接收单元 1103接收到 SPC发送的第一业务路径的标识后, 处 理单元 1101可以根据第一业务路径的标识确定第一业务流, 应理解, 经过 第一业务使能器的业务路径可以有不止一条,按照这些业务路径流经第一业 务使能器的业务流都是受到过载影响的业务流。 PCRF的处理单元 1101根据 第一业务路径的标识确定受到过载影响的第一业务流, 第一业务流可以是 PCRF在分配有第一业务路径的标识的多个业务流中随机选取的。
可选地, 作为一个实施例, 发送单元 1102还用于: 向 STC发送事件订 阅请求, 以使得 STC检测第一业务流的事件结果, 其中事件结果包括第一 业务流的当前会话结束或者新会话开始; 接收单元 1103还用于: 接收 STC 在检测到第一业务流的事件结果时发送的响应消息; 处理单元 1101还用于: 为第一业务流确定第二业务路径的标识。
PCRF实体在确定了受到过载影响的第一业务流后, 可以通过发送单元 1102向 STC发送针对该第一业务流的事件订阅请求, 以请求 STC在检测到 第一业务流的当前会话结束或新的会话开始时, 响应该事件订阅请求。
其中, UE的第一业务流具有特定的业务类型(即功能类型), 用于完成 某一项任务或请求, 该第一业务流可以由至少一个会话组成, 也就是说组成 第一业务流的多个会话也具有相同的业务类型,且用于完成某一项任务或请 求,每个会话开始时建立 UE与服务器之间的 TCP连接, TCP将会话包含的 数据流分割成适当长度的数据报文以便传输, 当会话结束时 TCP连接释放。 因此会话中途终止业务流会导致 TCP连接中断, 从而导致业务中断。
具体地, PCRF可以根据应用检测控制 (Application Detection Control, ADC )规则来生成上述事件订阅请求, 以便于从 STC处订阅第一业务流的 事件的开始和结束。 此外, PCRF也可以针对受到过载影响的 UE进行事件 订阅, 本发明对此并不限定。
STC在检测到第一业务流的当前会话结束或新的会话开始时,通过响应 消息将该事件通知 PCRF。 PCRF在通过接收单元 1103接收到 STC发送的响 应消息时, 可以通过处理单元 1101 为第一业务流确定新的业务路径标识。 应理解, PCRF也可以在检测到第一业务使能器过载之后, 到 PCRF准备向 STC发送新的业务路径标识之前的时段内的任意时刻为第一业务流确定新 的业务路径标识, 本发明对此并不限定。
可选地, 作为一个实施例, 处理单元 1101具体用于: 根据第一业务使 能器的标识、 第一业务流的业务类型、 装置预存的业务路由规则和各个业务 使能器当前的负载状态中的至少一种,确定经过第二业务使能器的第二业务 路径。
PCRF为第一业务流确定新的业务路径标识(即第二业务路径的标识), 具体地, PCRF的处理单元 1101可以根据第一业务使能器的标识、 第一业务 流的业务类型、 PCRF预存的业务路由规则和各个业务使能器当前的负载状 态中的至少一种, 确定经过第二业务使能器的第二业务路径。
作为一个最简单的实施例, PCRF的处理单元 1101可以将第一业务路径 中的第一业务使能器替换为第二业务使能器, 形成第二业务路径。 第二业务 使能器可以是与第一业务使能器位于同一个 SE Pool的不同业务使能器, 即 功能相同、个体相异。此外,第二业务使能器也可以是 PCRF的处理单元 1101 根据各个业务使能器的负载状态确定的, 例如在第一业务使能器所属的 SE Pool 中确定当前负载最低的业务使能器为第二业务使能器。 应理解, PCRF 的处理单元 1101也可以根据业务路由规则重新确定第二业务路径的标识, 并且满足第二业务路径不经过第一业务使能器的条件。
可选地, 作为一个实施例, 发送单元 1102具体用于: 向 SPC发送用于 请求第二业务路径的标识的请求消息,以使得 SPC根据第一业务使能器的标 识、 第一业务流的业务类型和各个业务使能器当前的负载状态中的至少一 种, 确定经过第二业务使能器的第二业务路径; 接收单元 1103具体用于接 收 SPC发送的第二业务路径的标识。
当由 SPC对业务使能器进行过载检测时, 由于 SPC处有第一业务使能 器的 SE ID, 因此新的业务路径标识可以由 SPC确定。 具体地, PCRF的接 收单元 1103在接收到 SPC发送的第一业务路径标识, 并确定了第一业务流 后, 便可以通过发送单元 1102向 SPC发送请求消息, 以请求新的业务路径 标识。 请求消息可以携带有第一业务路径的标识或第一业务流对应的 UE的 标识。 在接收到 PCRF发送的请求消息后, SPC为第一业务流确定新的业务 路径标识 (即第二业务路径的标识), 第二业务路径标识的确定方法可以参 照上述实施例, 此处不再赘述。 SPC在确定第二业务路径的标识后, 将其发 送至 PCRF,以便于 PCRF通过发送单元 1102将第二业务路径的标识发送至 STC, 由 STC应用第二业务路径的标识。
可选地, 作为一个实施例, 接收单元 1103具体用于: 接收 SPC根据第 一业务使能器的标识、第一业务流的业务类型和各个业务使能器当前的负载 状态中的至少一种确定并且发送的第二业务路径的标识, 其中第二业务路径 经过第二业务使能器。 具体地, SPC可以根据第一业务使能器的标识、 第一 业务流的业务类型和各个业务使能器当前的负载状态中的至少一种,确定经 过第二业务使能器的第二业务路径。 作为一个最简单的实施例, SPC可以将 第一业务路径中的第一业务使能器替换为第二业务使能器, 形成第二业务路 径。 第二业务使能器可以是与第一业务使能器位于同一个 SE Pool的不同业 务使能器, 即功能相同、 个体相异。 此外, 第二业务使能器也可以是 SPC 根据各个业务使能器的负载状态确定的, 例如在第一业务使能器所属的 SE
Pool中确定当前负载最低的业务使能器为第二业务使能器。应理解, SPC也 可以根据 PCRF发送的业务路由规则重新确定第二业务路径的标识, 并且满 足第二业务路径不经过第一业务使能器的条件。
可选地, 作为一个实施例, 处理单元 1101还用于: 根据第一业务使能 器的标识、 第一业务流的业务类型、 PCRF预存的业务路由规则和各个业务 使能器当前的负载状态中的至少一种,确定经过第二业务使能器的第二业务 路径。
在 PCRF的处理单元 1101检测到第一业务使能器过载后, 并确定受到 过载影响的第一业务流后, 可以直接为第一业务流确定第二业务路径的标 识, 将该第二业务路径的标识通过发送单元 1102发送至 STC处, 由 STC根 据第一业务流的会话状态自行确定合适应用第二业务路径的标识。
本发明实施例的 PCRF 1100确定受到第一业务使能器过载影响的第一 业务流, 确定或者获取了不经过第一业务使能器的第二业务路径后, 将该第 二业务路径的标识发送至 STC。 使得 STC在第一业务流的当前会话结束或 者第一业务流的新会话开始时, 将第二业务路径的标识分配给第一业务流。 从而第一业务流可以在会话间歇时段更改路径,按照第二业务路径流经第二 业务使能器, 避免继续通过第一业务使能器受到过载影响, 并加重过载的第 一业务使能器的负载。 也就是说, 在为过载的业务使能器减轻负载压力的同 时能够保证业务的连续性, 不会出现丟包、服务中断等现象,提高用户体验。
图 12是本发明一个实施例的业务路由装置 (STC ) 的示意框图。 图 12 所示的业务流分类器 STC 1200包括处理单元 1201。
处理单元 1201确定受到过载影响的第一业务流, 其中第一业务流为按 照第一业务路径流经过载的第一业务使能器的业务流。 处理单元 1201确定 第一业务流的当前会话状态。在第一业务流的当前会话结束或者第一业务流 的新会话开始时, 处理单元 1201将第二业务路径的标识分配给第一业务流, 以使得第一业务流的新会话按照第二业务路径流经第二业务使能器,其中第 一业务使能器与第二业务使能器相异、 且功能类型相同。
本发明实施例在第一业务使能器过载时,通过确定流经该第一业务使能 器的业务流的当前会话状态来决定何时将第一业务使能器的业务流迁移至 第二业务使能器,从而在解决业务使能器过载的同时能够保证用户业务不中 断, 提高了用户体验。
应理解, STC 1200可以执行上述图 2-图 10中方法的相关步骤。
可选地, 作为一个实施例, 处理单元 1201具体用于: 获取第一业务路 径的标识; 在分配有第一业务路径的标识的业务流中确定第一业务流。 处理单元 1201也可以在 STC本地获取第一业务路径的标识。 其中由 PCRF 进行过载检测时, 则 STC的处理单元 1201可以从 PCRF处获取第一业务路 径标识; 由 SPC进行过载检测时, 则 STC的处理单元 1201可以从 SPC处 获取第一业务路径标识; 由 STC进行过载检测时, 则 STC的处理单元 1201 可以自行确定第一业务路径的标识。
在获取到第一业务路径的标识后, STC的处理单元 1201可以根据第一 业务路径的标识确定第一业务流, 具体地, 经过第一业务使能器的业务路径 可以有不止一条,按照这些业务路径流经第一业务使能器的业务流都是受到 过载影响的业务流。 STC的处理单元 1201根据第一业务路径的标识确定受 到过载影响的第一业务流, 第一业务流可以是 STC在分配有第一业务路径 的标识的多个业务流中随机选取的。
可选地, 作为一个实施例, 装置还包括接收单元 1202, 处理单元 1201 具体用于: 获取过载的第一业务使能器的标识, 并根据第一业务使能器的标 识获取经过第一业务使能器的第一业务路径的标识; 或者通过接收单元
1202,接收业务路径控制器 SPC发送的第一业务路径的标识,其中第一业务 路径的标识由 SPC根据过载的第一业务使能器的标识获取;或者通过接收单 元 1202, 接收策略与计费规则功能 PCRF实体发送的第一业务路径的标识, 其中第一业务路径的标识由 PCRF实体根据过载的第一业务使能器的标识获 取。
其中, 在 STC进行过载检测的实施例中, 第一业务使能器的标识可以 是 SE Monitor检测到第一业务使能器过载后发送给 STC的,也就是说, STC 对于业务使能器的过载检测过程, 可以是 STC对于过载业务使能器的标识 的获取过程。 此外, STC也可以通过向 SE Monitor/SE Manager发送请求消 息来获取过载的第一业务使能器的标识。 应理解, 过载业务使能器的标识还 可以是通过 SE Manager发送给 STC的。 STC可以根据第一业务使能器的标 识, 业务路径的标识和业务使能器的标识之间的对应关系, 确定经过第一业 务使能器的第一业务路径的标识。 应理解, 经过第一业务使能器的业务路径 可以有不止一条,按照这些业务路径流经第一业务使能器的业务流都是受到 过载影响的业务流。
在 SPC 进行过载检测的实施例中, 第一业务使能的标识可以是 SE Monitor/SE Manager检测到第一业务使能器过载后发送给 SPC的,也就是说, SPC对于业务使能器的过载检测过程, 可以是 SPC对于过载业务使能器的 标识的获取过程。 此外, SPC也可以通过向 SE Monitor/SE Manager发送请 求消息来获取过载的第一业务使能器的标识。 应理解, 整合有业务使能器检 测功能的 SPC也可以自行进行过载检测。
SPC检测到第一业务使能器过载后,可以根据第一业务使能器的标识确 定经过第一业务使能器的第一业务路径的标识, 并且将第一业务路径的标识 发送至 STC。 具体地, 由于最初对业务流进行负载分配的 PCRF设备或 STC 在为 UE的业务流分配业务路径标识时, 会将业务路径的标识和该业务路径 经过的业务使能器的标识之间的对应关系一并发送给 SPC,所以 PCRF设备、 STC或 SPC都可以通过上述对应关系确定第一业务使能器的标识对应于哪 些业务路径标识, 即确定哪些业务路径受到了过载的影响。
在 PCRF进行过载检测的实施例中, 第一业务使能器的标识可以是 SE Monitor检测到第一业务使能器过载后发送给 PCRF的, 也就是说, PCRF对 于业务使能器的过载检测过程, 可以是 PCRF对于过载业务使能器的标识的 获取过程。 此外, PCRF也可以通过向 SE Monitor/SE Manager发送请求消息 来获取过载的第一业务使能器的标识。 应理解, 过载业务使能器的标识还可 以是通过 SE Manager发送给 PCRF的。 PCRF可以根据第一业务使能器的标 识, 业务路径的标识和业务使能器的标识之间的对应关系, 确定经过第一业 务使能器的第一业务路径的标识。 应理解, 经过第一业务使能器的业务路径 可以有不止一条,按照这些业务路径流经第一业务使能器的业务流都是受到 过载影响的业务流。
可选地, 作为一个实施例, 接收单元 1202还用于: 接收 PCRF发送的 第二业务路径的标识, 其中第二业务路径的标识由 PCRF根据第一业务使能 器的标识、 第一业务流的业务类型、 PCRF预存的业务路由规则和各个业务 使能器当前的负载状态中的至少一种确定, 第二业务路径经过第二业务使能 器。
在 PCRF进行过载检测的实施例中, PCRF在确定了经过第一业务使能 器的第一业务路径的标识后, 可以根据第一业务路径的标识确定第一业务流 的标识, 第一业务流可以是 PCRF在分配有第一业务路径的标识的多个业务 流中随机选取的。
PCRF在确定受到过载影响的 UE的第一业务流之后, 可以为第一业务 流确定新的业务路径标识(即第二业务路径的标识), 具体地, PCRF可以根 据第一业务使能器的标识、 第一业务流的业务类型、 PCRF预存的业务路由 规则和各个业务使能器当前的负载状态中的至少一种,确定经过第二业务使 能器的第二业务路径。 作为一个最简单的实施例, PCRF可以将第一业务路 径中的第一业务使能器替换为第二业务使能器, 形成第二业务路径。 第二业 务使能器可以是与第一业务使能器位于同一个 SE Pool的不同业务使能器, 即功能相同、 个体相异。 此外, 第二业务使能器也可以是 PCRF根据各个业 务使能器的负载状态确定的, 例如在第一业务使能器所属的 SE Pool中确定 当前负载最低的业务使能器为第二业务使能器。 应理解, PCRF也可以根据 业务路由规则重新确定第二业务路径的标识, 并且满足第二业务路径不经过 第一业务使能器的条件。 PCRF在确定第二业务路径的标识后, 可以直接下 发给 STC, 由 STC确定何时使用。 可选地, 作为一个实施例, STC 1200还包括发送单元 1203, 发送单元 1203用于: 向 SPC发送用于请求第二业务路径的标识的请求消息, 以使得 SPC根据第一业务使能器的标识、第一业务流的业务类型和各个业务使能器 当前的负载状态中的至少一种, 确定经过第二业务使能器的第二业务路径; 接收单元 1202还用于接收 SPC发送的第二业务路径的标识。
在 SPC进行过载检测的实施例中, STC在接收到 SPC发送的第一业务 路径标识后, STC确定第一业务流的当前会话状态, 在第一业务流的当前会 话结束之后, 或者新的会话开始之前, STC向 SPC发送请求消息, 以请求 新的业务路径标识。请求消息可以携带有第一业务路径的标识或第一业务流 对应的 UE的标识。在接收到 STC发送的请求消息后, SPC为第一业务流确 定新的业务路径标识(即第二业务路径的标识), 并将其发送至 STC。
具体地, SPC可以根据第一业务使能器的标识、 第一业务流的业务类型 和各个业务使能器当前的负载状态中的至少一种,确定经过第二业务使能器 的第二业务路径。 作为一个最简单的实施例, SPC可以将第一业务路径中的 第一业务使能器替换为第二业务使能器, 形成第二业务路径。 第二业务使能 器可以是与第一业务使能器位于同一个 SE Pool的不同业务使能器, 即功能 相同、 个体相异。 此外, 第二业务使能器也可以是 SPC根据各个业务使能器 的负载状态确定的, 例如在第一业务使能器所属的 SE Pool中确定当前负载 最低的业务使能器为第二业务使能器。 应理解, SPC也可以根据 PCRF发送 的业务路由规则重新确定第二业务路径的标识, 并且满足第二业务路径不经 过第一业务使能器的条件。
可选地, 作为一个实施例, 接收单元 1202还用于: 接收 SPC发送的第 二业务路径的标识,其中第二业务路径的标识由 SPC根据第一业务使能器的 标识、第一业务流的业务类型和各个业务使能器当前的负载状态中的至少一 种确定, 第二业务路径经过第二业务使能器。
在 SPC进行过载检测的实施例中, SPC可以在确定过载的第一业务使 能器, 并确定第一业务路径标识时, 确定经过第二业务使能器的第二业务路 径标识, 并将第一业务路径标识和第二业务路径标识都发送至 STC 1200。 其中 SPC确定第二业务路径标识可以参照上述实施例, 此处不再赘述。
本发明实施例的 STC 1200确定受到第一业务使能器过载影响的第一业 务流, 确定或者获取了不经过第一业务使能器的第二业务路径后, 在第一业 务流的当前会话结束或者第一业务流的新会话开始时,将第二业务路径的标 识分配给第一业务流。 从而第一业务流可以在会话间歇时段更改路径, 按照 第二业务路径流经第二业务使能器,避免继续通过第一业务使能器受到过载 影响, 并加重过载的第一业务使能器的负载。 也就是说, 在为过载的业务使 能器减轻负载压力的同时能够保证业务的连续性, 不会出现丟包、 服务中断 等现象, 提高用户体验。
图 13是本发明一个实施例的业务路由装置 (SPC ) 的示意框图。 图 13 所述的业务路径控制器 SPC 1300包括处理单元 1301和发送单元 1302。
处理单元 1301获取过载的第一业务使能器的标识。处理单元 1301根据 第一业务使能器的标识获取经过第一业务使能器的第一业务路径的标识。发 送单元 1302向策略和计费规则功能 PCRF实体或业务流分类器 STC发送第 一业务路径的标识,以便于 PCRF实体或 STC确定分配有第一业务路径的标 识的第一业务流,其中第一业务流为按照第一业务路径流经过载的第一业务 使能器的业务流; 并且处理单元 1301根据第一业务使能器的标识、 第一业 务流的业务类型、 和各个业务使能器当前的负载状态中的至少一种, 确定经 过第二业务使能器的第二业务路径的标识, 其中第一业务使能器与第二业务 使能器相异、 且功能相同; 发送单元 1302向 PCRF实体或 STC发送第二业 务路径的标识,以便于 PCRF实体或 STC在第一业务流的当前会话结束或者 第一业务流的新会话开始时, 将第二业务路径的标识分配给第一业务流, 使 得第一业务流的新会话按照第二业务路径流经第二业务使能器。
本发明实施例在第一业务使能器过载时,通过确定流经该第一业务使能 器的业务流的当前会话状态来决定何时将第一业务使能器的业务流迁移至 第二业务使能器,从而在解决业务使能器过载的同时能够保证用户业务不中 断, 提高了用户体验。
应理解, SPC 1300可以执行上述图 2、 图 5-7、 图 9和图 10中方法的相 应步骤。
可选地, 作为一个实施例, SPC 1300还包括接收单元 1303, 接收单元 1303用于: 接收 PCRF实体或 STC发送的用于请求第二业务路径的标识的 请求消息。
本发明实施例的 SPC 1300确定受到第一业务使能器过载影响的第一业 务流, 确定或者获取了不经过第一业务使能器的第二业务路径后, 在第一业 务流的当前会话结束或者第一业务流的新会话开始时,将第二业务路径的标 识分配给第一业务流。 从而第一业务流可以在会话间歇时段更改路径, 按照 第二业务路径流经第二业务使能器,避免继续通过第一业务使能器受到过载 影响, 并加重过载的第一业务使能器的负载。 也就是说, 在为过载的业务使 能器减轻负载压力的同时能够保证业务的连续性, 不会出现丟包、 服务中断 等现象, 提高用户体验。
图 14是本发明另一实施例的业务路由装置(PCRF )的示意框图。 图 14 的 PCRF实体 1400包括处理器 1401和存储器 1402。 处理器 1401和存储器 1402通过总线系统 1403相连。
存储器 1402用于存储使得处理器 1401执行以下操作的指令: 确定受到 过载影响的第一业务流, 其中第一业务流为按照第一业务路径流经过载的第 一业务使能器的业务流; 向业务流分类器 STC发送第二业务路径的标识, 以使得 STC在第一业务流的当前会话结束或者第一业务流的新会话开始时, 将第二业务路径的标识分配给第一业务流,使得第一业务流的新会话按照第 二业务路径流经第二业务使能器,其中第一业务使能器与第二业务使能器相 异、 且功能类型相同。
本发明实施例在第一业务使能器过载时,通过确定流经该第一业务使能 器的业务流的当前会话状态来决定何时将第一业务使能器的业务流迁移至 第二业务使能器,从而在解决业务使能器过载的同时能够保证用户业务不中 断, 提高了用户体验。
应理解, PCRF实体 1400可以执行上述图 2-图 6中任意实施例的方法的 相应步骤, 并且 PCRF实体 1400的处理器可以对应于上述图 11中 PCRF实 体 1100的处理单元 1101。
此外, PCRF实体 1400还可以包括发射电路 1404、 接收电路 1405等。 处理器 1401控制 PCRF实体 1400的操作, 处理器 1401还可以称为 CPU ( Central Processing Unit, 中央处理单元)。 存储器 1402可以包括只读存储 器和随机存取存储器, 并向处理器 1401提供指令和数据。 存储器 1402的一 部分还可以包括非易失性随机存取存储器( NVRAM )。 PCRF实体 1400的 各个组件通过总线系统 1403耦合在一起, 其中总线系统 1403除包括数据总 线之外, 还可以包括电源总线、 控制总线和状态信号总线等。 但是为了清楚 说明起见, 在图中将各种总线都标为总线系统 1403。 上述本发明实施例揭示的方法可以应用于处理器 1401 中, 或者由处理 器 1401实现。处理器 1401可能是一种集成电路芯片,具有信号的处理能力。 在实现过程中, 上述方法的各步骤可以通过处理器 1401 中的硬件的集成逻 辑电路或者软件形式的指令完成。 上述的处理器 1401可以是通用处理器、 数字信号处理器(DSP )、专用集成电路(ASIC )、现成可编程门阵列(FPGA ) 或者其他可编程逻辑器件、 分立门或者晶体管逻辑器件、 分立硬件组件。 可 以实现或者执行本发明实施例中的公开的各方法、 步骤及逻辑框图。 通用处 理器可以是微处理器或者该处理器也可以是任何常规的处理器等。 结合本发 明实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成, 或 者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机 存储器, 闪存、只读存储器,可编程只读存储器或者电可擦写可编程存储器、 寄存器等本领域成熟的存储介质中。 该存储介质位于存储器 1402, 处理器 1401读取存储器 1402中的信息, 结合其硬件完成上述方法的步骤。
可选地, 作为一个实施例, 处理器 1401用于: 获取过载的第一业务使 能器的标识; 根据第一业务使能器的标识获取经过第一业务使能器的第一业 务路径的标识; 在分配有第一业务路径的标识的业务流中确定第一业务流。
可选地,作为一个实施例,通过接收电路 1405接收业务路径控制器 SPC 发送的第一业务路径的标识,其中第一业务路径的标识由 SPC根据过载的第 一业务使能器的标识获取; 处理器 1401在分配有第一业务路径的标识的业 务流中确定第一业务流。
可选地, 作为一个实施例, 通过发射电路 1404向 STC发送事件订阅请 求, 以使得 STC检测第一业务流的事件结果, 其中事件结果包括第一业务 流的当前会话结束或者新会话开始; 通过接收电路 1405接收 STC在检测到 第一业务流的事件结果时发送的响应消息; 处理器 1401 为第一业务流确定 第二业务路径的标识。
可选地, 作为一个实施例, 处理器 1401根据第一业务使能器的标识、 第一业务流的业务类型、 PCRF预存的业务路由规则和各个业务使能器当前 的负载状态中的至少一种, 确定经过第二业务使能器的第二业务路径。
可选地, 作为一个实施例, 通过发射电路 1404向 SPC发送用于请求第 二业务路径的标识的请求消息, 以使得 SPC根据第一业务使能器的标识、第 一业务流的业务类型和各个业务使能器当前的负载状态中的至少一种,确定 经过第二业务使能器的第二业务路径; 通过接收电路 1405接收 SPC发送的 第二业务路径的标识。
可选地, 作为一个实施例, 通过接收电路 1405接收 SPC根据第一业务 使能器的标识、第一业务流的业务类型和各个业务使能器当前的负载状态中 的至少一种确定并且发送的第二业务路径的标识, 其中第二业务路径经过第 二业务使能器。
可选地, 作为一个实施例, 处理器 1401根据第一业务使能器的标识、 第一业务流的业务类型、 PCRF预存的业务路由规则和各个业务使能器当前 的负载状态中的至少一种, 确定经过第二业务使能器的第二业务路径。
本发明实施例的 PCRF实体 1400确定受到第一业务使能器过载影响的 第一业务流, 确定或者获取了不经过第一业务使能器的第二业务路径后, 将 该第二业务路径的标识发送至 STC。 使得 STC在第一业务流的当前会话结 束或者第一业务流的新会话开始时,将第二业务路径的标识分配给第一业务 流。 从而第一业务流可以在会话间歇时段更改路径, 按照第二业务路径流经 第二业务使能器, 避免继续通过第一业务使能器受到过载影响, 并加重过载 的第一业务使能器的负载。 也就是说, 在为过载的业务使能器减轻负载压力 的同时能够保证业务的连续性, 不会出现丟包、 服务中断等现象, 提高用户 体验。
图 15是本发明另一实施例的业务路由装置 (STC)的示意框图。 图 15的 业务流分类器 STC 1500包括处理器 1501和存储器 1502。 处理器 1501和存 储器 1502通过总线系统 1503相连。
存储器 1502用于存储使得处理器 1501执行以下操作的指令: 确定受到 过载影响的第一业务流, 其中第一业务流为按照第一业务路径流经过载的第 一业务使能器的业务流; 确定第一业务流的当前会话状态; 在第一业务流的 当前会话结束或者第一业务流的新会话开始时,将第二业务路径的标识分配 给第一业务流, 以使得第一业务流的新会话按照第二业务路径流经第二业务 使能器, 其中第一业务使能器与第二业务使能器相异、 且功能类型相同。
本发明实施例在第一业务使能器过载时,通过确定流经该第一业务使能 器的业务流的当前会话状态来决定何时将第一业务使能器的业务流迁移至 第二业务使能器,从而在解决业务使能器过载的同时能够保证用户业务不中 断, 提高了用户体验。 应理解, STC 1500可以执行上述图 2-图 10中方法的相关步骤, STC 1500 的处理器 1501可以对应于上述图 12中 STC 1200的处理单元 1201。
此外, STC1500还可以包括发射电路 1504、接收电路 1505。处理器 1501 控制 STC1500的操作,处理器 1501还可以称为 CPU( Central Processing Unit, 中央处理单元)。 存储器 1502可以包括只读存储器和随机存取存储器, 并向 处理器 1501提供指令和数据。存储器 1502的一部分还可以包括非易失性随 机存取存储器( NVRAM )。 STC1500的各个组件通过总线系统 1503耦合在 一起, 其中总线系统 1503除包括数据总线之外, 还可以包括电源总线、 控 制总线和状态信号总线等。 但是为了清楚说明起见, 在图中将各种总线都标 为总线系统 1503。
上述本发明实施例揭示的方法可以应用于处理器 1501 中, 或者由处理 器 1501实现。处理器 1501可能是一种集成电路芯片,具有信号的处理能力。 在实现过程中, 上述方法的各步骤可以通过处理器 1501 中的硬件的集成逻 辑电路或者软件形式的指令完成。 上述的处理器 1501可以是通用处理器、 数字信号处理器(DSP )、专用集成电路(ASIC )、现成可编程门阵列(FPGA ) 或者其他可编程逻辑器件、 分立门或者晶体管逻辑器件、 分立硬件组件。 可 以实现或者执行本发明实施例中的公开的各方法、 步骤及逻辑框图。 通用处 理器可以是微处理器或者该处理器也可以是任何常规的处理器等。 结合本发 明实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成, 或 者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机 存储器, 闪存、只读存储器,可编程只读存储器或者电可擦写可编程存储器、 寄存器等本领域成熟的存储介质中。 该存储介质位于存储器 1502, 处理器 1501读取存储器 1502中的信息, 结合其硬件完成上述方法的步骤。
可选地, 作为一个实施例, 处理器 1501用于: 获取第一业务路径的标 识; 在分配有第一业务路径的标识的业务流中确定第一业务流。
可选地, 作为一个实施例, 处理器 1501获取过载的第一业务使能器的 标识, 并根据第一业务使能器的标识获取经过第一业务使能器的第一业务路 径的标识; 或者通过接收电路 1505接收业务路径控制器 SPC发送的第一业 务路径的标识,其中第一业务路径的标识由 S PC根据过载的第一业务使能器 的标识获取; 或者通过接收电路 1505接收策略与计费规则功能 PCRF实体 发送的第一业务路径的标识, 其中第一业务路径的标识由 PCRF实体根据过 载的第一业务使能器的标识获取。
可选地, 作为一个实施例, 通过接收电路 1505接收 PCRF发送的第二 业务路径的标识, 其中第二业务路径的标识由 PCRF根据第一业务使能器的 标识、 第一业务流的业务类型、 PCRF预存的业务路由规则和各个业务使能 器当前的负载状态中的至少一种确定, 第二业务路径经过第二业务使能器。
可选地, 作为一个实施例, 通过发射电路 1504向 SPC发送用于请求第 二业务路径的标识的请求消息, 以使得 SPC根据第一业务使能器的标识、第 一业务流的业务类型和各个业务使能器当前的负载状态中的至少一种,确定 经过第二业务使能器的第二业务路径; 通过接收电路 1505接收 SPC发送的 第二业务路径的标识。
可选地, 作为一个实施例, 通过接收电路 1505接收 SPC发送的第二业 务路径的标识, 其中第二业务路径的标识由 SPC根据第一业务使能器的标 识、第一业务流的业务类型和各个业务使能器当前的负载状态中的至少一种 确定, 第二业务路径经过第二业务使能器。
本发明实施例的 STC 1500确定受到第一业务使能器过载影响的第一业 务流, 确定或者获取了不经过第一业务使能器的第二业务路径后, 在第一业 务流的当前会话结束或者第一业务流的新会话开始时,将第二业务路径的标 识分配给第一业务流。 从而第一业务流可以在会话间歇时段更改路径, 按照 第二业务路径流经第二业务使能器,避免继续通过第一业务使能器受到过载 影响, 并加重过载的第一业务使能器的负载。 也就是说, 在为过载的业务使 能器减轻负载压力的同时能够保证业务的连续性, 不会出现丟包、 服务中断 等现象, 提高用户体验。
图 16是本发明另一实施例的业务路由装置 (SPC)的示意框图。 图 16的 业务路径控制器 SPC1600包括处理器 1601和存储器 1602。 处理器 1601和 存储器 1602通过总线系统 1603相连。
存储器 1602用于存储使得处理器 1601执行以下操作的指令: 获取过载 的第一业务使能器的标识; 根据第一业务使能器的标识获取经过第一业务使 能器的第一业务路径的标识; 向策略和计费规则功能 PCRF实体或业务流分 类器 STC发送第一业务路径的标识, 以便于 PCRF实体或 STC确定分配有 第一业务路径的标识的第一业务流, 其中第一业务流为按照第一业务路径流 经过载的第一业务使能器的业务流; 并且根据第一业务使能器的标识、 第一 业务流的业务类型、 和各个业务使能器当前的负载状态中的至少一种, 确定 经过第二业务使能器的第二业务路径的标识, 其中第一业务使能器与第二业 务使能器相异、且功能相同;向 PCRF实体或 STC发送第二业务路径的标识, 以便于 PCRF实体或 STC在第一业务流的当前会话结束或者第一业务流的新 会话开始时, 将第二业务路径的标识分配给第一业务流, 使得第一业务流的 新会话按照第二业务路径流经第二业务使能器。
本发明实施例在第一业务使能器过载时,通过确定流经该第一业务使能 器的业务流的当前会话状态来决定何时将第一业务使能器的业务流迁移至 第二业务使能器,从而在解决业务使能器过载的同时能够保证用户业务不中 断, 提高了用户体验。
应理解, SPC 1600可以执行上述图 2、 图 5-7、 图 9和图 10中方法的相 应步骤, SPC1600的处理器 1601可以与上述图 13中 SPC1300的处理单元 1301相对应。
此外, SPC1600还可以包括发射电路 1604、接收电路 1605。处理器 1601 控制 SPC1600的操作,处理器 1601还可以称为 CPU( Central Processing Unit, 中央处理单元)。 存储器 1602可以包括只读存储器和随机存取存储器, 并向 处理器 1601提供指令和数据。存储器 1602的一部分还可以包括非易失性随 机存取存储器( NVRAM )。 SPC1600的各个组件通过总线系统 1603耦合在 一起, 其中总线系统 1603除包括数据总线之外, 还可以包括电源总线、 控 制总线和状态信号总线等。 但是为了清楚说明起见, 在图中将各种总线都标 为总线系统 1603。
上述本发明实施例揭示的方法可以应用于处理器 1601 中, 或者由处理 器 1601实现。处理器 1601可能是一种集成电路芯片,具有信号的处理能力。 在实现过程中, 上述方法的各步骤可以通过处理器 1601 中的硬件的集成逻 辑电路或者软件形式的指令完成。 上述的处理器 1601可以是通用处理器、 数字信号处理器(DSP )、专用集成电路(ASIC )、现成可编程门阵列(FPGA ) 或者其他可编程逻辑器件、 分立门或者晶体管逻辑器件、 分立硬件组件。 可 以实现或者执行本发明实施例中的公开的各方法、 步骤及逻辑框图。 通用处 理器可以是微处理器或者该处理器也可以是任何常规的处理器等。 结合本发 明实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成, 或 者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机 存储器, 闪存、只读存储器,可编程只读存储器或者电可擦写可编程存储器、 寄存器等本领域成熟的存储介质中。 该存储介质位于存储器 1602, 处理器 1601读取存储器 1602中的信息, 结合其硬件完成上述方法的步骤。
可选地, 作为一个实施例, 接收电路 1605接收 PCRF实体或 STC发送 的用于请求第二业务路径的标识的请求消息。
本发明实施例的 SPC 1600确定受到第一业务使能器过载影响的第一业 务流, 确定或者获取了不经过第一业务使能器的第二业务路径后, 在第一业 务流的当前会话结束或者第一业务流的新会话开始时,将第二业务路径的标 识分配给第一业务流。 从而第一业务流可以在会话间歇时段更改路径, 按照 第二业务路径流经第二业务使能器,避免继续通过第一业务使能器受到过载 影响, 并加重过载的第一业务使能器的负载。 也就是说, 在为过载的业务使 能器减轻负载压力的同时能够保证业务的连续性, 不会出现丟包、 服务中断 等现象, 提高用户体验。
本领域普通技术人员可以意识到, 结合本文中所公开的实施例中描述的 各方法步骤和单元, 能够以电子硬件、 计算机软件或者二者的结合来实现, 为了清楚地说明硬件和软件的可互换性,在上述说明中已经按照功能一般性 地描述了各实施例的步骤及组成。 这些功能究竟以硬件还是软件方式来执 行, 取决于技术方案的特定应用和设计约束条件。 本领域普通技术人员可以 对每个特定的应用来使用不同方法来实现所描述的功能,但是这种实现不应 认为超出本发明的范围。
结合本文中所公开的实施例描述的方法或步骤可以用硬件、处理器执行 的软件程序,或者二者的结合来实施。软件程序可以置于随机存储器( RAM )、 内存、 只读存储器(ROM )、 电可编程 ROM、 电可擦除可编程 ROM、 寄存 器、 硬盘、 可移动磁盘、 CD-ROM、 或技术领域内所公知的任意其它形式的 存储介质中。 但本发明并不限于此。 在不脱离本发明的精神和实质的前提下, 本领域普通 技术人员可以对本发明的实施例进行各种等效的修改或替换, 而这些修改或 替换都应在本发明的涵盖范围内。

Claims

权利要求
1. 一种业务路由方法, 其特征在于, 包括:
策略和计费规则功能 PCRF实体确定受到过载影响的第一业务流, 其中 所述第一业务流为按照第一业务路径流经过载的第一业务使能器的业务流; 所述 PCRF实体向业务流分类器 STC发送第二业务路径的标识,以使得 所述 STC在所述第一业务流的当前会话结束或者所述第一业务流的新会话 开始时, 将所述第二业务路径的标识分配给所述第一业务流, 使得所述第一 业务流的所述新会话按照所述第二业务路径流经第二业务使能器, 其中所述 第一业务使能器与所述第二业务使能器相异、 且功能类型相同。
2. 根据权利要求 1所述的方法, 其特征在于, 所述 PCRF实体确定受到 过载影响的第一业务流, 包括:
获取过载的所述第一业务使能器的标识;
根据所述第一业务使能器的标识获取经过所述第一业务使能器的第一 业务路径的标识;
在分配有所述第一业务路径的标识的业务流中确定所述第一业务流。
3. 根据权利要求 1所述的方法, 其特征在于, 所述 PCRF实体确定受到 过载影响的第一业务流, 包括:
接收业务路径控制器 SPC发送的所述第一业务路径的标识,其中所述第 一业务路径的标识由所述 SPC根据过载的所述第一业务使能器的标识获取; 在分配有所述第一业务路径的标识的业务流中确定所述第一业务流。
4. 根据权利要求 2或 3所述的方法,其特征在于,在所述 PCRF实体向 STC发送第二业务路径的标识之前, 所述方法还包括:
向所述 STC发送事件订阅请求, 以使得所述 STC检测所述第一业务流 的事件结果, 其中所述事件结果包括所述第一业务流的当前会话结束或者新 会话开始;
接收所述 STC在检测到所述第一业务流的所述事件结果时发送的响应 消息;
为所述第一业务流确定所述第二业务路径的标识。
5. 根据权利要求 4所述的方法,其特征在于,所述为所述第一业务流确 定所述第二业务路径的标识, 包括: 根据所述第一业务使能器的标识、 所述 第一业务流的业务类型、 所述 PCRF预存的业务路由规则和各个业务使能器 当前的负载状态中的至少一种,确定经过所述第二业务使能器的第二业务路 径。
6. 根据权利要求 4所述的方法,其特征在于,所述为所述第一业务流确 定所述第二业务路径的标识, 包括:
向所述 SPC发送用于请求所述第二业务路径的标识的请求消息,以使得 所述 SPC根据所述第一业务使能器的标识、所述第一业务流的业务类型和各 个业务使能器当前的负载状态中的至少一种,确定经过所述第二业务使能器 的第二业务路径;
接收所述 SPC发送的所述第二业务路径的标识。
7. 根据权利要求 4所述的方法, 其特征在于, 所述向所述 STC发送事 件订阅请求之前, 还包括: 接收所述 SPC根据所述第一业务使能器的标识、 所述第一业务流的业务类型和各个业务使能器当前的负载状态中的至少一 种确定并且发送的所述第二业务路径的标识, 其中第二业务路径经过所述第 二业务使能器。
8. 根据权利要求 2所述的方法, 其特征在于, 所述 PCRF实体向业务流 分类器 STC发送第二业务路径的标识之前, 还包括: 根据所述第一业务使 能器的标识、 所述第一业务流的业务类型、 所述 PCRF预存的业务路由规则 和各个业务使能器当前的负载状态中的至少一种,确定经过所述第二业务使 能器的第二业务路径。
9. 一种业务路由方法, 其特征在于, 包括:
业务流分类器 STC确定受到过载影响的第一业务流, 其中所述第一业 务流为按照第一业务路径流经过载的第一业务使能器的业务流;
所述 STC确定所述第一业务流的当前会话状态;
所述 STC在所述第一业务流的当前会话结束或者所述第一业务流的新 会话开始时, 将第二业务路径的标识分配给所述第一业务流, 以使得所述第 一业务流的所述新会话按照所述第二业务路径流经第二业务使能器,其中所 述第一业务使能器与所述第二业务使能器相异、 且功能类型相同。
10. 根据权利要求 9所述的方法, 其特征在于, 所述 STC确定受到过载 影响的第一业务流, 包括:
获取所述第一业务路径的标识;
在分配有所述第一业务路径的标识的业务流中确定所述第一业务流。
11. 根据权利要求 10所述的方法, 其特征在于, 所述确定所述第一业务 路径的标识, 包括:
获取过载的所述第一业务使能器的标识, 并根据所述第一业务使能器的 标识获取经过所述第一业务使能器的第一业务路径的标识; 或者
接收业务路径控制器 SPC发送的所述第一业务路径的标识,其中所述第 一业务路径的标识由所述 SPC根据过载的所述第一业务使能器的标识获取; 或者
接收策略与计费规则功能 PCRF实体发送的所述第一业务路径的标识, 其中所述第一业务路径的标识由所述 PCRF实体根据过载的所述第一业务使 能器的标识获取。
12根据权利要求 11所述的方法,其特征在于,所述 STC确定所述第一 业务流的当前会话状态之前, 还包括: 接收所述 PCRF发送的所述第二业务 路径的标识, 其中所述第二业务路径的标识由所述 PCRF根据所述第一业务 使能器的标识、 所述第一业务流的业务类型、 所述 PCRF预存的业务路由规 则和各个业务使能器当前的负载状态中的至少一种确定, 所述第二业务路径 经过所述第二业务使能器。
13. 根据权利要求 11所述的方法, 其特征在于, 所述接收业务路径控制 器 SPC发送的所述第一业务路径的标识之后, 还包括:
向所述 SPC发送用于请求所述第二业务路径的标识的请求消息,以使得 所述 SPC根据所述第一业务使能器的标识、所述第一业务流的业务类型和各 个业务使能器当前的负载状态中的至少一种,确定经过所述第二业务使能器 的第二业务路径;
接收所述 SPC发送的所述第二业务路径的标识。
14. 根据权利要求 11所述的方法, 其特征在于, 所述 STC确定所述第 一业务流的当前会话状态之前,还包括:接收所述 SPC发送的所述第二业务 路径的标识,其中所述第二业务路径的标识由所述 SPC根据所述第一业务使 能器的标识、所述第一业务流的业务类型和各个业务使能器当前的负载状态 中的至少一种确定, 所述第二业务路径经过所述第二业务使能器。
15. 一种业务路由方法, 其特征在于, 包括:
业务路径控制器 SPC获取过载的第一业务使能器的标识;
所述 SPC根据所述第一业务使能器的标识获取经过所述第一业务使能 器的第一业务路径的标识;
所述 SPC向策略和计费规则功能 PCRF实体或业务流分类器 STC发送 所述第一业务路径的标识,以便于所述 PCRF实体或 STC确定分配有第一业 务路径的标识的第一业务流, 其中所述第一业务流为按照第一业务路径流经 过载的第一业务使能器的业务流; 并且
所述 SPC根据所述第一业务使能器的标识、 所述第一业务流的业务类 型、 和各个业务使能器当前的负载状态中的至少一种, 确定经过第二业务使 能器的第二业务路径的标识, 其中所述第一业务使能器与所述第二业务使能 器相异、 且功能相同; 以便于所述 PCRF实体或所述 STC在所述第一业务流的当前会话结束或者所 述第一业务流的新会话开始时,将所述第二业务路径的标识分配给所述第一 业务流,使得所述第一业务流的所述新会话按照所述第二业务路径流经第二 业务使能器。
16. 根据权利要求 15所述的方法,其特征在于, 所述 SPC向所述 PCRF 实体或所述 STC发送所述第二业务路径的标识之前,还包括:接收所述 PCRF 实体或所述 STC发送的用于请求所述第二业务路径的标识的请求消息。
17. 一种业务路由装置, 其特征在于, 包括:
处理单元, 用于确定受到过载影响的第一业务流, 其中所述第一业务流 为按照第一业务路径流经过载的第一业务使能器的业务流;
发送单元, 用于向业务流分类器 STC发送第二业务路径的标识, 以使 得所述 STC在所述第一业务流的当前会话结束或者所述第一业务流的新会 话开始时, 将所述第二业务路径的标识分配给所述第一业务流, 使得所述第 一业务流的所述新会话按照所述第二业务路径流经第二业务使能器,其中所 述第一业务使能器与所述第二业务使能器相异、 且功能类型相同。
18. 根据权利要求 17所述的装置,其特征在于,所述处理单元具体用于: 获取过载的所述第一业务使能器的标识;
根据所述第一业务使能器的标识获取经过所述第一业务使能器的第一 业务路径的标识;
在分配有所述第一业务路径的标识的业务流中确定所述第一业务流。
19. 根据权利要求 17所述的装置,其特征在于,所述装置还包括接收单 元, 所述接收单元用于:
接收业务路径控制器 SPC发送的所述第一业务路径的标识,其中所述第 一业务路径的标识由所述 SPC根据过载的所述第一业务使能器的标识获取; 所述处理单元还用于: 在分配有所述第一业务路径的标识的业务流中确 定所述第一业务流。
20. 根据权利要求 18或 19所述的装置, 其特征在于, 所述发送单元还 用于:
向所述 STC发送事件订阅请求, 以使得所述 STC检测所述第一业务流 的事件结果, 其中所述事件结果包括所述第一业务流的当前会话结束或者新 会话开始;
所述接收单元还用于: 接收所述 STC在检测到所述第一业务流的所述 事件结果时发送的响应消息;
所述处理单元还用于: 为所述第一业务流确定所述第二业务路径的标 识。
21. 根据权利要求 20所述的装置,其特征在于,所述处理单元具体用于: 根据所述第一业务使能器的标识、 所述第一业务流的业务类型、 所述装置预 存的业务路由规则和各个业务使能器当前的负载状态中的至少一种,确定经 过所述第二业务使能器的第二业务路径。
22. 根据权利要求 20所述的装置,其特征在于,所述发送单元具体用于: 向所述 SPC发送用于请求所述第二业务路径的标识的请求消息,以使得 所述 SPC根据所述第一业务使能器的标识、所述第一业务流的业务类型和各 个业务使能器当前的负载状态中的至少一种,确定经过所述第二业务使能器 的第二业务路径;
所述接收单元具体用于接收所述 SPC发送的所述第二业务路径的标识。 23. 根据权利要求 20所述的装置,其特征在于,所述接收单元具体用于: 接收所述 SPC根据所述第一业务使能器的标识、所述第一业务流的业务类型 和各个业务使能器当前的负载状态中的至少一种确定并且发送的所述第二 业务路径的标识, 其中第二业务路径经过所述第二业务使能器。
24. 根据权利要求 18所述的装置, 其特征在于, 所述处理单元还用于: 根据所述第一业务使能器的标识、 所述第一业务流的业务类型、 所述 PCRF 预存的业务路由规则和各个业务使能器当前的负载状态中的至少一种,确定 经过所述第二业务使能器的第二业务路径。
25. 一种业务路由装置, 其特征在于, 包括:
处理单元, 用于确定受到过载影响的第一业务流, 其中所述第一业务流 为按照第一业务路径流经过载的第一业务使能器的业务流;
所述处理单元确定所述第一业务流的当前会话状态;
在所述第一业务流的当前会话结束或者所述第一业务流的新会话开始 时, 所述处理单元将第二业务路径的标识分配给所述第一业务流, 以使得所 述第一业务流的所述新会话按照所述第二业务路径流经第二业务使能器, 其 中所述第一业务使能器与所述第二业务使能器相异、 且功能类型相同。
26. 根据权利要求 25所述的装置,其特征在于,所述处理单元具体用于: 获取所述第一业务路径的标识;
在分配有所述第一业务路径的标识的业务流中确定所述第一业务流。
27. 根据权利要求 26所述的装置,其特征在于,所述处理单元具体用于: 获取过载的所述第一业务使能器的标识, 并根据所述第一业务使能器的 标识获取经过所述第一业务使能器的第一业务路径的标识; 或者
所述装置还包括接收单元,所述接收单元用于接收业务路径控制器 SPC 发送的所述第一业务路径的标识,其中所述第一业务路径的标识由所述 SPC 根据过载的所述第一业务使能器的标识获取; 或者
所述装置还包括接收单元, 所述接收单元用于接收策略与计费规则功能 PCRF实体发送的所述第一业务路径的标识, 其中所述第一业务路径的标识 由所述 PCRF实体根据过载的所述第一业务使能器的标识获取。
28. 根据权利要求 27所述的装置, 其特征在于, 所述接收单元还用于: 接收所述 PCRF发送的所述第二业务路径的标识, 其中所述第二业务路径的 标识由所述 PCRF根据所述第一业务使能器的标识、 所述第一业务流的业务 类型、 所述 PCRF预存的业务路由规则和各个业务使能器当前的负载状态中 的至少一种确定, 所述第二业务路径经过所述第二业务使能器。
29. 根据权利要求 27所述的装置,其特征在于,所述装置还包括发送单 元, 所述发送单元用于:
向所述 SPC发送用于请求所述第二业务路径的标识的请求消息,以使得 所述 SPC根据所述第一业务使能器的标识、所述第一业务流的业务类型和各 个业务使能器当前的负载状态中的至少一种,确定经过所述第二业务使能器 的第二业务路径;
所述接收单元还用于接收所述 SPC发送的所述第二业务路径的标识。
30. 根据权利要求 27所述的装置, 其特征在于, 所述接收单元还用于: 接收所述 SPC发送的所述第二业务路径的标识,其中所述第二业务路径的标 识由所述 SPC根据所述第一业务使能器的标识、所述第一业务流的业务类型 和各个业务使能器当前的负载状态中的至少一种确定, 所述第二业务路径经 过所述第二业务使能器。
31. 一种业务路由装置, 其特征在于, 包括:
处理单元, 用于获取过载的第一业务使能器的标识;
所述处理单元根据所述第一业务使能器的标识获取经过所述第一业务 使能器的第一业务路径的标识;
发送单元,用于向策略和计费规则功能 PCRF实体或业务流分类器 STC 发送所述第一业务路径的标识,以便于所述 PCRF实体或 STC确定分配有第 一业务路径的标识的第一业务流,其中所述第一业务流为按照第一业务路径 流经过载的第一业务使能器的业务流; 并且
所述处理单元根据所述第一业务使能器的标识、所述第一业务流的业务 类型、 和各个业务使能器当前的负载状态中的至少一种, 确定经过第二业务 使能器的第二业务路径的标识, 其中所述第一业务使能器与所述第二业务使 能器相异、 且功能相同; 识,以便于所述 PCRF实体或所述 STC在所述第一业务流的当前会话结束或 者所述第一业务流的新会话开始时,将所述第二业务路径的标识分配给所述 第一业务流,使得所述第一业务流的所述新会话按照所述第二业务路径流经 第二业务使能器。
32. 根据权利要求 31所述的装置,其特征在于,所述装置还包括接收单 元,所述接收单元用于:接收所述 PCRF实体或所述 STC发送的用于请求所 述第二业务路径的标识的请求消息。
33. —种业务路由系统, 其特征在于, 包括上述权利要求 17-32所述的 装置。
PCT/CN2014/084199 2014-08-12 2014-08-12 业务路由方法、装置和系统 WO2016023167A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2014/084199 WO2016023167A1 (zh) 2014-08-12 2014-08-12 业务路由方法、装置和系统
CN201480035955.9A CN105531969B (zh) 2014-08-12 2014-08-12 业务路由方法、装置和系统

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2014/084199 WO2016023167A1 (zh) 2014-08-12 2014-08-12 业务路由方法、装置和系统

Publications (1)

Publication Number Publication Date
WO2016023167A1 true WO2016023167A1 (zh) 2016-02-18

Family

ID=55303772

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/084199 WO2016023167A1 (zh) 2014-08-12 2014-08-12 业务路由方法、装置和系统

Country Status (2)

Country Link
CN (1) CN105531969B (zh)
WO (1) WO2016023167A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101557609A (zh) * 2008-04-07 2009-10-14 华为技术有限公司 用户负载转移的方法、通信系统及核心网控制节点
CN101610494A (zh) * 2008-06-16 2009-12-23 华为技术有限公司 实现过载控制或差异化服务的方法、系统及设备
CN103430580A (zh) * 2011-01-21 2013-12-04 黑莓有限公司 用于确定针对(本地)卸载使用的连接的连接上下文的网络装置和过程

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101557609A (zh) * 2008-04-07 2009-10-14 华为技术有限公司 用户负载转移的方法、通信系统及核心网控制节点
CN101610494A (zh) * 2008-06-16 2009-12-23 华为技术有限公司 实现过载控制或差异化服务的方法、系统及设备
CN103430580A (zh) * 2011-01-21 2013-12-04 黑莓有限公司 用于确定针对(本地)卸载使用的连接的连接上下文的网络装置和过程

Also Published As

Publication number Publication date
CN105531969B (zh) 2018-10-12
CN105531969A (zh) 2016-04-27

Similar Documents

Publication Publication Date Title
CN112136294B (zh) 应用功能影响业务路由的消息和系统
US11683716B2 (en) Communication apparatus, system, method, allocation apparatus, and non-transitory recording medium
US10595233B2 (en) Communication control method, controller, user equipment, and function instance
US10555214B2 (en) Coexistence of software defined network, network function virtualization and legacy networks
US9374307B2 (en) Group session management for policy control
JP5559357B2 (ja) 複数のインターネット・プロトコル・フローのグループ・セッション管理およびアドミッション制御
CN108259434B (zh) 一种用户侧QoS保障能力的开放方法及服务器
US9801227B2 (en) Systems and methods for implementing bearer call-back services
KR102056684B1 (ko) 통신 시스템에서 데이터 흐름 전송을 위한 개선된 우선권 핸들링
TW201345285A (zh) 為無線使用者提供智慧型編解碼率調整的方法及設備
JP6478358B2 (ja) サービス処理方法、pcrf、及びサービス処理システム
EP3841728B1 (en) Information-centric networking over 5g or later networks
WO2018010461A1 (zh) 一种业务流量的控制方法及系统
WO2023035925A1 (zh) 一种业务处理方法、装置和系统
WO2016115672A1 (zh) 承载资源的处理方法和装置
CN106792923B (zh) 一种配置QoS策略的方法及装置
US9756522B2 (en) Session assignment and balancing
US9161376B2 (en) System and method for managing access point communication channel utilization
WO2016023167A1 (zh) 业务路由方法、装置和系统
US9504021B1 (en) Long term evolution (LTE) network control of carrier aggregation for user equipment
WO2015085470A1 (zh) 一种业务路由的方法和装置
WO2017193303A1 (zh) 一种通信计费方法
WO2022247875A1 (zh) 建立连接的方法、装置和系统
WO2018124196A1 (ja) 無線ネットワークシステム、基地局装置、端末装置
CN118678400A (zh) 用于网络接入的装置、方法、和非暂态计算机可读存储介质

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 201480035955.9

Country of ref document: CN

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 14899865

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 14899865

Country of ref document: EP

Kind code of ref document: A1