WO2015184840A1 - 响应消息的获取、响应消息的路由方法、装置及系统 - Google Patents

响应消息的获取、响应消息的路由方法、装置及系统 Download PDF

Info

Publication number
WO2015184840A1
WO2015184840A1 PCT/CN2015/072006 CN2015072006W WO2015184840A1 WO 2015184840 A1 WO2015184840 A1 WO 2015184840A1 CN 2015072006 W CN2015072006 W CN 2015072006W WO 2015184840 A1 WO2015184840 A1 WO 2015184840A1
Authority
WO
WIPO (PCT)
Prior art keywords
request message
service request
group
service
identifier information
Prior art date
Application number
PCT/CN2015/072006
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 US15/512,002 priority Critical patent/US10129749B2/en
Priority to EP15802459.6A priority patent/EP3203692B1/en
Publication of WO2015184840A1 publication Critical patent/WO2015184840A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/302—Route determination based on requested QoS
    • H04L45/304—Route determination for signalling traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/34—Source routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/16—Discovering, processing access restriction or access information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H04W8/082—Mobility data transfer for traffic bypassing of mobility servers, e.g. location registers, home PLMNs or home agents

Definitions

  • the present invention relates to the field of communications, and in particular, to a method, device, and system for obtaining a response message, routing a response message.
  • Diameter Basic Protocol a protocol for managing Diameter Access
  • IETF Internet Engineering Task Force
  • LTE Long Term Evolution
  • Evolved Packet Core Evolved Packet Core
  • AAA authentication, authorization, and accounting
  • the "Diameter Basic Protocol” defines that the network role of the Diameter node is various agents, which may include: Relay Agent, Proxy Agent, Redirect Agent, and translation. Translate Agent, all types of agents maintain the Transaction State, and agents other than the relay agent can maintain the Session State.
  • FIG. 1 is a schematic diagram of networking of an online network (ie, Diameter signaling transit network) established on an IP network according to the related art.
  • an online network ie, Diameter signaling transit network
  • IP Internet Protocol
  • the Diameter signaling network can be divided into an international Diameter signaling network and a domestic Diameter signaling network, and a location update request (ULR) message of a mobile management entity (MME) of a roaming country is transferred through a DRA signaling of a roaming country.
  • the network is forwarded to the roaming country iDRA1 of the international DRA signaling transit network, and then forwarded to the home country iDRA2, and then forwarded to the DRA signaling transit network of the home country, and finally to the home subscriber server (HSS) of the home country.
  • the ULR message in Figure 2 is forwarded by a total of 6 DRAs.
  • the Diameter nodes can be connected as a data bearer link through a Stream Control Transmission Protocol (SCTP) or a Control Transmission Protocol (TCP) connection.
  • the Capabilities Exchange Request can be exchanged. , referred to as CER) / Capabilities Exchange Answer (CEA) message interaction
  • CER Capabilities Exchange Request
  • CEA Capabilities Exchange Answer
  • the capability negotiation is performed, and the signaling link detection and recovery are performed by means of Device Viewdog Request (DER)/Device Watchdog Answer (DEA) message interaction to form a Diameter signaling link layer. .
  • FIG. 3 is a schematic diagram of a protocol hierarchy of a DRA network according to the OSI model according to the related art.
  • FIG. 3 refers to the seven-layer network model of the Open Systems Interconnection Reference Model (OSI) proposed by International Standardized Resistance (ISO), although the Flow Control Transmission Protocol (SCTP) belongs to the transaction layer in the IP network, but In the Diameter signaling transit network or SigTran network, they are only part of the signaling link layer.
  • OSI Open Systems Interconnection Reference Model
  • SCTP Flow Control Transmission Protocol
  • the Realm Routing Table in the DRA network layer only provides routing for request messages. The ACK message is returned according to the original path of the request message, and no route analysis is performed.
  • the ISO organization has also proposed a standard model for messages to be delivered in the network.
  • the intermediate node ie, the signaling transfer point
  • the transaction layer and the transaction layer are "end-to-end".
  • 4 is a schematic diagram of a standard model of signaling forwarding between service nodes in accordance with the OSI model in accordance with the related art. As shown in Figure 4, the intermediate nodes can be forwarded through the network layer, and the transaction layer and the above layers are 'end-to-end'. IP networks, SS7 networks, and SigTran networks all conform to this model.
  • the DRA acts as an intermediate node, providing a transaction layer and even a session layer.
  • FIG. 5 is a schematic diagram of signaling transfer mode 1 when a DIA is forwarded by a DIA according to the related art, and the DRA only maintains a transaction state.
  • the intermediate nodes are forwarded at the transaction layer, maintaining transaction layer processing.
  • FIG. 6 is a schematic diagram of a signaling mode 2, DRA maintaining a transaction state and a session state when a Diameter service node transfers through DRA according to the related art.
  • the intermediate nodes are forwarded at the session layer, maintaining transaction layer and session layer processing.
  • neither the network layer function is provided in FIG. 5 and FIG. 6, that is, the response message cannot be separately routed, but needs to be returned in the original path according to the incoming path of the request message.
  • DRA provides transaction management is actually a flaw.
  • the DRA needs to maintain the transaction state, and once the DRA exits the service, all transactions carried on it will fail.
  • the current measures that can be taken are: for a failed transaction, the Diameter client or the DRA sends a message retransmission to the request message of the transaction (in case the timer waiting for the Diameter response times out) or routing reselection (when waiting When the ACK responds, it receives the response carrying the failure code), and selects another DRA node to try again.
  • the Diameter client or DRA node will resend the request message (the 'T' flag is set for the retransmitted request message), and a large number of retransmission request messages cause very much to the entire Diameter signaling network. Big impact. If the DRA of the service exit has a load sharing node, in addition to its own load, the load sharing node must bear the load of the DRA to withdraw from the service, and also bear the signaling load of all message retransmissions, and the short-term load is increased by 3 times. . When multiple retransmissions are initiated and multiple nodes are resent, the impact on the network is even greater.
  • the transaction resources (and session resources) of the DRA node may become a bottleneck and become an unintentional or malicious attack on the object.
  • a Home Location Register (HLR) does not respond to REQ messages, which is equivalent to a Deny Of Service (DoS) attack. It can occupy all transaction resources in a few seconds, causing other The transaction could not be forwarded normally.
  • DoS Deny Of Service
  • the embodiments of the present invention provide a method, a device, and a system for obtaining a response message, and a method for routing a response message, so as to at least solve the problem of relying on a transaction layer retransmission or a route reselection in the related art to compensate for the fact that the Diameter response message cannot be separately routed.
  • the problem of larger defects are possible.
  • a method of acquiring a response message is provided.
  • the method for obtaining a response message includes: the source node sends a service request message to the second group of nodes by using the first group of DRA nodes, where the second group of nodes includes: a destination node and a second group of DRA nodes;
  • the message carries the first identifier information, the second identifier information, and the third identifier information.
  • the first identifier information of the service request message is used to identify the destination node, and the second identifier information of the service request message is used to indicate that the first group of DRA nodes follow
  • the first identifier information is used for routing and forwarding the service request message, and the first identifier information indicating that the destination node sets the service response message is the third identifier information of the service request message, and the third identifier information of the service request message is used to identify the source node;
  • the node obtains the service response message returned by the destination node through the second group of DRA nodes.
  • the first identification information of the service request message is an attribute value pair (AVP) of a destination domain name (Destination-Realm) and a destination host name (Destination-Host).
  • AVP attribute value pair
  • the third identification information of the service request message is an AVP of a source domain name (Origin-Realm) and a source host name (Origin-Host).
  • the second identification information of the service request message is a command flag added in the Diameter message header.
  • each of the first group of DRA nodes forwards the service request message to the next adjacent one after performing route analysis on the service request message.
  • DRA node or destination node no transaction processing and/or session processing is required.
  • the first group of DRA nodes and the second group of DRA nodes are respectively two different links between the source node and the destination node, wherein one or more of the first group of DRA nodes are in the service request message Exit the service during the route forwarding process.
  • a routing method of a response message is provided.
  • the routing method of the response message includes: the destination node receives the service request message from the source node by using the first group of DRA nodes, where the service request message carries the first identifier information, the second identifier information, and the The third identifier information, the first identifier information of the service request message is an identifier of the destination node, and the second identifier information of the service request message is used to indicate that the first group of DRA nodes forwards and forwards the service request message according to the first identifier information of the service request message.
  • the destination node sets the first identifier information of the service response message as the third identifier information of the service request message
  • the third identifier information of the service request message is used to identify the source node, and the destination node according to the second identifier information of the service request message
  • the first identifier information of the service response message is set to the third identifier information of the service request message
  • the service response message is returned to the source node by the second group of nodes, where the second group of nodes includes: the destination node and the second group of DRA nodes .
  • the third identifier information that the destination node sets the first identifier information of the service request message to the service request message according to the second identifier information of the service request message includes at least one of the following: the destination domain name carried by the destination node in the service response message (Destination-Realm) is set to the source domain name of the source node (Origin-Realm); the destination node sets the destination host name (Destination-Host) carried in the service response message to the source host name (Origin-Host) of the source node.
  • the destination domain name carried by the destination node in the service response message (Destination-Realm) is set to the source domain name of the source node (Origin-Realm)
  • the destination node sets the destination host name (Destination-Host) carried in the service response message to the source host name (Origin-Host) of the source node.
  • the second identification information of the service request message is a command flag added in the Diameter message header.
  • each node of the second group of nodes performs route analysis on the service response message, and forwards the service response message to the next adjacent one according to the routing result.
  • DRA node or source node without transaction processing and/or session processing.
  • an apparatus for acquiring a response message is provided.
  • the apparatus for acquiring a response message includes: a sending module, configured to send a service request message to a second group of nodes by using the first group of DRA nodes, where the second group of nodes includes: a destination node and a second group of DRA nodes
  • the service request message carries the first identifier information, the second identifier information, and the third identifier information.
  • the first identifier information of the service request message is used to identify the destination node, and the second identifier information of the service request message is used to indicate the first group.
  • the DRA node performs routing and forwarding of the service request message according to the first identification information, and indicates that the destination node sets the first identification information of the service response message to the third identifier information of the service request message, and the third identifier information of the service request message is used to identify
  • the source node is configured to obtain a service response message returned by the destination node by using the second group of DRA nodes.
  • the first identification information of the service request message is an AVP of a destination domain name (Destination-Realm) and a destination host name (Destination-Host).
  • the third identification information of the service request message is an AVP of a source domain name (Origin-Realm) and a source host name (Origin-Host).
  • the second identification information of the service request message is a command flag added in the Diameter message header.
  • each of the first group of DRA nodes forwards the service request message to the next adjacent one after performing route analysis on the service request message.
  • DRA node or destination node no transaction processing and/or session processing is required.
  • the first group of DRA nodes and the second group of DRA nodes are respectively two different links between the source node and the destination node, wherein one or more of the first group of DRA nodes are in the service request message Exit the service during the route forwarding process.
  • a routing device for responding to a message is provided.
  • the routing device of the response message includes: a receiving module, configured to receive, by the first group of DRA nodes, a service request message from the source node, where the service request message carries the first identifier information and the second identifier
  • the information and the third identifier information, the first identifier information of the service request message is an identifier of the destination node, and the second identifier information of the service request message is used to indicate that the first group of DRA nodes subscribe to the service request message according to the first identifier information of the service request message.
  • the identification information is set as the third identification information of the service request message
  • the third identification information of the service request message is used to identify the source node
  • the determining module is configured to set the first identification information of the service response message according to the second identification information of the service request message.
  • the third identifier information is set as the service request message, and the service response message is returned to the source node by the second group of DRA nodes, where the second group of nodes includes: the destination node and the second group of DRA nodes.
  • the determining module includes: a first processing unit configured to set a destination domain name (Destination-Realm) carried in the service response message as a source domain name (Origin-Realm) of the source node; and a second processing unit configured to set the service
  • the destination host name (Destination-Host) carried in the response message is set to the source host name (Origin-Host) of the source node.
  • the second identification information of the service request message is a command flag added in the Diameter message header.
  • each node of the second group of nodes performs route analysis on the service response message, and forwards the service response message to the next adjacent one according to the reason result.
  • the DRA node is either the source node and does not require transaction processing and/or session processing.
  • a routing system for obtaining and responding to a message is provided.
  • a routing system for obtaining and responding to a response message includes: a service source node, a service destination node, a first group of DRA nodes through which a service request message is sent from a service source node to a service destination node, and a service destination The second group of DRA nodes through which the node sends the service response message to the service source node.
  • the source node sends a service request message to the second group of nodes through the first group of DRA nodes, where the second group of nodes includes: the destination node and the second group of DRA nodes; the service request message carries the first The first identifier information of the service request message is used to identify the destination node, and the second identifier information of the service request message is used to indicate that the first group of DRA nodes are in accordance with the first identifier information.
  • the request message is routed and the first node information indicating that the destination node sets the service response message is the third identifier information of the service request message, the third identifier information of the service request message is used to identify the source node, and the source node passes the second group of DRAs.
  • the node obtains the service response message returned by the destination node, and solves the problem of relying on the transaction layer message retransmission or the route reselection measure in the related art to compensate for the problem that the Diameter response message cannot be separately routed, thereby improving the reliability of the network layer. Reduces the dependency on the Diameter server's ability to resend messages.
  • FIG. 1 is a schematic diagram of networking of an online network (ie, Diameter signaling transit network) established on an IP network according to the related art;
  • an online network ie, Diameter signaling transit network
  • FIG. 2 is a schematic diagram of dividing a Diameter signaling switching network into an international layer and a domestic layer according to the related art
  • FIG. 3 is a schematic diagram of a protocol hierarchy of a DRA network according to an OSI model according to the related art
  • FIG. 4 is a schematic diagram of a standard model for signaling forwarding between service nodes according to the OSI model according to the related art
  • FIG. 5 is a schematic diagram of signaling transfer mode 1 when a DIA is forwarded by a DRA according to the related art, and the DRA only maintains a transaction state;
  • FIG. 6 is a schematic diagram of a signaling mode 2, DRA maintaining a transaction state and a session state when a Diameter service node transfers through DRA according to the related art;
  • FIG. 7 is a flowchart of a method for acquiring a response message according to an embodiment of the present invention.
  • FIG. 8 is a schematic diagram of a Diameter header definition in accordance with a preferred embodiment of the present invention.
  • FIG. 9 is a schematic diagram of a command mark definition in accordance with a preferred embodiment of the present invention.
  • FIG. 10 is a flowchart of a method for routing a response message according to an embodiment of the present invention.
  • FIG. 11 is a schematic diagram of a DRA gateway proxy network in which an international DRA network does not support an 'N' flag in accordance with a preferred embodiment of the present invention
  • FIG. 12 is a schematic diagram of a single-layer dual-plane simplification networking composed of four DRAs according to a preferred embodiment of the present invention
  • FIG. 13 is a flow diagram of a forwarding process of a transaction request and response message when a particular DRA exits the service, in accordance with a preferred embodiment of the present invention
  • FIG. 14 is a schematic diagram of a two-layer dual-plane simplification networking composed of eight DRAs according to a preferred embodiment of the present invention.
  • 15 is a flow diagram of a forwarding process of a transaction request and response message when a particular HDRA exits the service;
  • 16 is a schematic diagram of a DRA gateway proxy network in which a service node does not support an 'N' flag, in accordance with a preferred embodiment of the present invention
  • 17 is a structural block diagram of an apparatus for acquiring a response message according to an embodiment of the present invention.
  • FIG. 18 is a structural block diagram of a routing apparatus for a response message according to an embodiment of the present invention.
  • 19 is a schematic structural diagram of a routing system of a response message acquisition and response message according to an embodiment of the present invention.
  • FIG. 7 is a flowchart of a method for acquiring a response message according to an embodiment of the present invention. As shown in FIG. 7, the method may include the following processing steps:
  • Step S702 The source node sends a service request message to the second group of nodes by using the first group of DRA nodes, where the second group of nodes includes: a destination node and a second group of DRA nodes; the service request message carries the first identifier information, The second identifier information and the third identifier information, the first identifier information of the service request message is used to identify the destination node, and the second identifier information of the service request message is used to instruct the first group of DRA nodes to route the service request message according to the first identifier information. Forwarding and indicating that the destination node sets the first identifier information of the service response message to the third identifier information of the service request message, where the third identifier information of the service request message is used to identify the source node;
  • Step S704 The source node obtains the service response message returned by the destination node by using the second group of DRA nodes.
  • the first identifier information for identifying the destination node is carried in the service request message, and is further configured to instruct the first group of DRA nodes to forward and forward the service request message according to the first identifier information.
  • the destination node sets the first identification information of the service response message to the third identifier information of the service request message that identifies the source node, simplifies the function of the DRA as a signaling transfer point, and removes transaction processing and session processing, thereby solving Retransmission of messages relying on the transaction layer in the related art or
  • the routing re-selection measures to compensate for the large defect of the Diameter response message cannot be separately routed, thereby improving the reliability of the network layer and reducing the dependence on the Diameter server's retransmission message processing capability.
  • the second identification information of the service request message may be a command flag added in a Diameter message header.
  • a flag may be added to the Diameter header, and when the 'N' flag in the request message and the response message are both set to 1, the technical solution according to the embodiment of the present invention is represented. Process it. When the header of the received Diameter request/response message does not contain a 'N' flag, then the processing is performed in the existing manner.
  • FIG. 8 is a schematic diagram of a Diameter header definition in accordance with a preferred embodiment of the present invention. As shown in FIG. 8, see RFC 3588, in which Command Flags are defined as shown in FIG. 9, which is a schematic diagram of a command mark definition in accordance with a preferred embodiment of the present invention. In Fig. 9, the bits 4/5/6/7 of the command flag are reserved fields, and bit 4 can be defined as 'N', which means a network.
  • the network-wide Diameter node if the network-wide Diameter node supports the technical solution provided by the embodiment of the present invention, it can be set on the Diameter service node; if a service node does not support The 'N' flag sets the DRA directly connected to the service node as the DRA proxy gateway node, which is set when the message is forwarded on the DRA proxy gateway node. In this way, the business node does not need an upgraded version. If only the local network supports the ‘N’ flag, the DRA directly connected to other DRA networks (for example, the international DRA network) is used as the DRA proxy gateway node, and is not set when the message is forwarded on the DRA proxy gateway node. In this way, the non-local Diameter node does not require an upgraded version.
  • DRA directly connected to other DRA networks for example, the international DRA network
  • the first identifier information of the service request message may be an attribute value pair AVP of a destination domain name (Destination-Realm) and a destination host name (Destination-Host).
  • the third identifier information of the service request message is an AVP of a source domain name (Origin-Realm) and a source host name (Origin-Host).
  • the DRA node When the message header of the received Diameter response message contains an 'N' flag, the DRA node performs route analysis on the Destination-Realm and Destination-Host and forwards the response message, and also forwards the Destination carried in the message during the message forwarding process. Realm, Destination-Host attribute value pairs.
  • each of the first group of DRA nodes forwards the service request message to the next adjacent one after performing route analysis on the service request message.
  • DRA node or destination node no transaction processing and/or session processing is required.
  • the DRA node When the header of the received Diameter request message contains a 'N' flag, the DRA node performs route analysis and forwards the request message, but does not save the transaction status (or session state). That is to simplify the function of DRA as a signaling transfer point, eliminating transaction processing and session processing. And because the transaction/session resources are removed, the DRA will not suffer from a shortage of transaction/session resources or be attacked maliciously or unintentionally.
  • the message when the DRA receives the Diameter message, the message contains the processing of the 'N' command flag. If the message is a Diameter request message, that is, the 'R' flag in the message is 1, the DRA does not maintain the transaction status and session. Status, route is obtained through route analysis, and the message is forwarded (including the 'N' flag). If the message is a Diameter response message, that is, the 'R' flag in the message is 0, the DRA obtains the route through the route analysis and forwards the message (may include: Destination-Realm, Destination-Host AVP, 'N' tag).
  • the first group of DRA nodes and the second group of DRA nodes are respectively two different links between the source node and the destination node, wherein one or more of the first group of DRA nodes are in the service request message Exit the service during the route forwarding process. That is, once a DRA temporarily or permanently exits the service, the diameter response message can be forwarded from other nodes, thereby improving the reliability of the network layer.
  • FIG. 10 is a flowchart of a method of routing a response message according to an embodiment of the present invention. As shown in FIG. 10, the method may include the following processing steps:
  • Step S1002 The destination node receives the service request message from the source node by using the first group of DRA nodes, where the service request message carries the first identifier information, the second identifier information, and the third identifier information, where the service request message is first.
  • the identifier information is an identifier of the destination node, and the second identifier information of the service request message is used to indicate that the first group of DRA nodes forwards the service request message according to the first identifier information of the service request message, and indicates that the destination node sends the service response message.
  • An identifier information is set as the third identifier information of the service request message, and the third identifier information of the service request message is used to identify the source node;
  • Step S1004 The destination node sets the first identifier information of the service response message as the third identifier information of the service request message according to the second identifier information of the service request message, and returns a service response message to the source node by using the second group node, where
  • the second group of nodes includes: a destination node and a second group of DRA nodes.
  • the setting, by the destination node, the first identifier information of the service request message as the third identifier information of the service request message according to the second identifier information of the service request message may include at least one of the following operations:
  • Step S1 The destination node sets the destination domain name (Destination-Realm) carried in the service response message to the source domain name of the source node (Origin-Realm);
  • Step S2 The destination node sets the destination host name (Destination-Host) carried in the service response message to the source node source host name (Origin-Host).
  • the destination domain name (Destination-Realm) and the destination host name (Destination-Host) are added to all Diameter response (ACK) messages as optional attribute value pairs (AVPs) for routing of ACK messages.
  • AVPs attribute value pairs
  • each node of the second group of nodes performs route analysis on the service response message, and forwards the service response message to the adjacent one according to the routing result.
  • the next DRA node or source node, and no transaction processing and/or session processing is required.
  • FIG. 11 is a schematic diagram of a DRA gateway proxy network in which an international DRA network does not support an 'N' flag, in accordance with a preferred embodiment of the present invention.
  • DRA2 acts as a DRA gateway agent, and its home Diameter signaling forwarding network on the lower left supports the 'N' flag, while all Diameter nodes on the upper right side do not support the 'N' flag, which facilitates compatibility and does not support the present invention.
  • Other networks of the technical solutions provided by the embodiments are examples of the technical solutions provided by the embodiments.
  • the DRA2 acts as a DRA gateway agent, and can set the Origin-Realm in the received REQ message to the Destination-Realm of the ACK message according to the request message recorded in the transaction data area; and will receive the Origin- in the REQ message. Host is set to the Destination-Host of the ACK message.
  • FIG. 12 is a schematic diagram of a single layer dual plane most simplified networking composed of 4 DRAs according to a preferred embodiment of the present invention.
  • the DRA can be divided into two planes, A/B. Each large area has a pair of DRAs, one for each plane. Any one of the service nodes in the large area is connected to a pair of DRAs at the same time, and the load sharing mode is adopted. The DRAs of the same plane are interconnected. There are Diameter signaling links between the two pairs of DRAs, called C links.
  • FIG. 13 is a flow diagram of a forwarding process of a transaction request and response message when a particular DRA exits the service, in accordance with a preferred embodiment of the present invention. As shown in FIG. 13, the process may include the following processing steps:
  • Step S1302 The MME user initiates registration, and the terminal sends an Update Location Request (ULR) message to the DRA1, where the ULR message carries an International Mobile Subscriber Identity (IMSI) number and a destination domain name information, and is set to ' N' mark.
  • ULR Update Location Request
  • IMSI International Mobile Subscriber Identity
  • Step S1304 After receiving the ULR message, DRA1 performs route analysis and forwards the ULR message to DRA3, and sets a 'N' flag.
  • Step S1306 After receiving the message, the DRA3 performs route analysis, and forwards the message to the HSS, and sets a ‘N’ flag.
  • Steps S1308-S1314 At this time, the DRA1 sends a SHUTDOWN message on the SCTP coupling of all Diameters due to the version upgrade, and after receiving the SHUTDOWN ACK message, the service is exited.
  • Step S1316 After receiving the ULR message, the HSS sends a ULA message to the DRA3, and the Destination-Host of the ULA message is set to the MME, and the 'N' flag is set.
  • Step S1318 After receiving the ULA message, the DRA performs route analysis and sends a ULA message to the DRA4, where the ULA message carries the ‘N’ flag.
  • Step S1320 After receiving the ULA message, the DRA4 performs route analysis and sends a ULA message to the DRA2, where the ULA message carries the 'N' flag.
  • Step S1322 After receiving the ULA message, the DRA2 performs route analysis and sends an ULA message to the MME. The transaction on the MME was successful.
  • the DRA signaling switching network can be divided into two layers: an H layer and an L layer. All large areas form the H layer, and all provinces of each large area form the L layer.
  • the L layer can be divided into two planes A/B, each province having a pair of DRAs, one for each plane. Any one of the service nodes (for example, MME) in the province is connected to a pair of low-level DRAs (Low Diameter Routing Agents, LDRA for short). The same plane LDRA is interconnected. There is a Diameter signaling link between the two planes, called the C link.
  • MME service nodes
  • LDRA Low Diameter Routing Agents
  • the H layer can also be divided into two planes A/B, each of which has a pair of DRAs, one for each plane. Any pair of LDRAs in the region is connected to a pair of LDRAs in a load sharing mode.
  • the high-level DRA (High Diameter Routing Agent, or HDRA) of the same plane is interconnected. There is a Diameter signaling link between the two planes, called the C link.
  • a service node for example, HSS
  • HSS service node
  • Figure 15 is a flow diagram of the forwarding process of a transaction request and response message when a particular HDRA exits the service. As shown in FIG. 15, the process may include the following processing steps:
  • Step 1502 The MME user initiates registration, and the terminal sends a ULR message to the DRA1, where the ULR message carries the IMSI number, the destination domain name information, and the ‘N’ flag is set.
  • Step 1504 After receiving the message, DRA1 performs route analysis and forwards the message to DRA3, setting the 'N' flag.
  • Step 1506 After receiving the message, DRA3 performs route analysis, and forwards the message to HDRA1, setting the 'N' flag.
  • Step 1508 After receiving the message, HDRA1 performs route analysis and forwards the message to HDRA3, setting the 'N' flag.
  • Step 1510 After receiving the message, the HDRA3 performs route analysis and forwards the message to the HSS, setting the ‘N’ flag.
  • Steps 1512-1522 At this time, the HDDA1 sends a SHUTDOWN message on the SCTP coupling of all Diameters due to the version upgrade, and exits the service after receiving the SHUTDOWN ACK message.
  • Step 1524 After receiving the ULR message, the HSS sends an ULA message to the HDRA3, where the DestHost of the ULA message is set to the MME, and the ‘N’ flag is set.
  • Step 1526 After receiving the ULA message, the HDRA3 performs route analysis and sends a ULA message to the HDRA4, where the ULA message carries the ‘N’ flag.
  • Step 1528 After receiving the ULA message, the HDRA4 performs route analysis and sends a ULA message to the HDRA2, where the ULA message carries the ‘N’ flag.
  • Step 1530 After receiving the ULA message, the HDRA2 performs route analysis and sends an ULA message to the LDRA4, where the ULA message carries the ‘N’ flag.
  • Step 1532 After receiving the ULA message, the LDRA4 performs route analysis and sends an ULA message to the LDRA2, where the ULA message carries the ‘N’ flag.
  • Step 1534 After receiving the ULA message, LDRA2 performs route analysis and sends a ULA message to the MME. The transaction on the MME was successful.
  • FIG. 16 is a schematic diagram of a DRA gateway proxy network in which a service node does not support an 'N' flag, in accordance with a preferred embodiment of the present invention.
  • DRA1 acts as a DRA gateway agent, and the MME node at the lower left is not supported.
  • the 'N' tag is used, and the Diameter node on the upper right side supports the 'N' tag, which is convenient for the service node that does not support the technical solution provided by the embodiment of the present invention.
  • DRA1 needs to maintain the transaction with the MME.
  • the response message on this segment does not need to be routed. It directly returns according to the original transaction path recorded on DRA1.
  • DRA1 does not need to maintain the transaction with DRA2.
  • the response message on this segment, DRA2 follows Route analysis is routed separately. This reflects the dual identity of DRA1 as a gateway agent. Except for DRA1, other DRAs do not need to maintain transaction status.
  • FIG. 17 is a structural block diagram of an apparatus for acquiring a response message according to an embodiment of the present invention.
  • the apparatus may be applied to the source node.
  • the apparatus for acquiring the response message may include: the sending module 10, configured to send a service request message to the second group of nodes by using the first group of DRA nodes, where the second group
  • the node includes: a destination node and a second group of DRA nodes; the service request message carries the first identifier information, the second identifier information, and the third identifier information, where the first identifier information of the service request message is used to identify the destination node, the service request message
  • the second identifier information is used to indicate that the first group of DRA nodes forwards the service request message according to the first identifier information, and indicates that the destination node sets the first identifier information of the service response message to the third identifier information of the sending service request message.
  • the third identifier information of the service request message is used to identify the source node
  • the device shown in FIG. 17 is used to solve the problem of relying on the transaction layer retransmission or routing reselection in the related art to compensate for the problem that the Diameter response message cannot be separately routed, thereby improving the reliability of the network layer. Reduced reliance on the Diameter server's ability to resend messages.
  • the first identification information of the service request message is an AVP of a destination domain name (Destination-Realm) and a destination host name (Destination-Host).
  • the third identification information of the service request message is an AVP of a source domain name (Origin-Realm) and a source host name (Origin-Host).
  • the second identification information of the service request message is a command flag added in the Diameter message header.
  • each of the first group of DRA nodes forwards the service request message to the next adjacent one after performing route analysis on the service request message.
  • DRA node or destination node no transaction processing and/or session processing is required.
  • the first group of DRA nodes and the second group of DRA nodes are respectively two different links between the source node and the destination node, wherein one or more of the first group of DRA nodes are in the service request message Exit the service during the route forwarding process.
  • FIG. 18 is a structural block diagram of a routing apparatus for a response message according to an embodiment of the present invention.
  • the routing device of the response message may include: a receiving module 30, configured to receive, by the first group of DRA nodes, a service request message from the source node, where the service request message carries the first identifier information, The second identifier information and the third identifier information, the first identifier information of the service request message is an identifier of the destination node, and the second identifier information of the service request message is used to indicate that the first group of DRA nodes are in accordance with the first identifier information of the service request message.
  • the service request message performs routing and forwarding, and indicates that the destination node sets the first identification information of the service response message to the third identifier information of the service request message, and the third identifier information of the service request message is used to identify the source node;
  • the determining module 40 is configured to And replacing the first identifier information of the service response message with the third identifier information of the service request message according to the second identifier information of the service request message, and returning a service response message to the source node by using the second group of DRA nodes, where the second group of nodes Including: the destination node and the second group of DRA nodes.
  • the determining module 40 may include: a first processing unit (not shown) configured to set a destination domain name (Destination-Realm) carried in the service response message as a source domain name (Origin-Realm) of the source node;
  • the second processing unit (not shown) is configured to set the destination host name (Destination-Host) carried in the service response message to the source host name (Origin-Host) of the source node.
  • the second identification information of the service request message is a command flag added in the Diameter message header.
  • each node of the second group of nodes performs route analysis on the service response message, and forwards the service response message to the adjacent one according to the reason result.
  • a DRA node is either a source node and does not require transaction processing and/or session processing.
  • routing device of the foregoing response message may be set not only in the service destination node, but also in the DRA node through which the service response message is routed.
  • the routing system for obtaining and responding to the response message may include: a service source node 1, a service destination node 2, and a first group of DRA nodes through which the service source message is sent from the service source node to the service destination node. 3 and a second group of DRA nodes 4 through which the service response message is sent from the service destination node to the service source node.
  • the foregoing service source node and service destination node are all nodes that support Diameter signaling, such as: HSS, MME, PCRF, PCEF, BBERF, OCS, SGSN, DRA, and gateway agent.
  • the foregoing embodiments achieve the following technical effects (it is required that the effects are achievable by some preferred embodiments): using the technical solution provided by the embodiment of the present invention, when DRA When the Diameter signaling network is established as a signaling transfer point, the DRA that regulates message forwarding provides a complete network.
  • Layer function All messages (including: request REQ message and response ACK message) are treated as completely independent messages, which can be routed independently; transaction layer management (and session layer management) is removed, and a DRA node exits service through the network layer itself.
  • the network layer forwarding of the response message is not compensated by the upper layer (transaction layer) by retransmission to avoid the defects of the transaction resource bottleneck and the network load explosion, thereby improving the reliability of the signaling transit network.
  • modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.
  • the method, device, and system for obtaining a response message and routing a response message provided by the embodiments of the present invention have the following beneficial effects: gradually eliminating the message retransmission or routing reselection measures relying on the transaction layer to compensate for the Diameter response message. There is a large defect in the individual route, which improves the reliability of the network layer and reduces the dependence on the Diameter server's retransmission message processing capability.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Databases & Information Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本发明公开了一种响应消息的获取、响应消息的路由方法、装置及系统，该方法包括：源节点通过第一组DRA节点向第二组节点发送业务请求消息，第二组节点包括：目的节点和第二组DRA节点；业务请求消息中携带有第一标识信息、第二标识信息和第三标识信息，上述第一标识信息用于标识目的节点，上述第二标识信息用于指示第一组DRA节点按照上述第一标识信息对业务请求消息进行路由转发以及指示目的节点将业务响应消息的第一标识信息设置为业务请求消息的第三标识信息，该第三标识信息用于标识源节点；源节点通过第二组DRA节点获取目的节点返回的业务响应消息，降低了对Diameter服务器的重发消息处理能力的依赖。

Description

响应消息的获取、响应消息的路由方法、装置及系统 技术领域
本发明涉及通信领域，具体而言，涉及一种响应消息的获取、响应消息的路由方法、装置及系统。
背景技术
目前，请求注解(RFC)3588和RFC6733是互联网工程任务组(IETF)提出的“Diameter基本协议”的两个版本，为长期演进(Long Term Evolution，简称为LTE)/分组核心演进(Evolved Packet Core，简称为EPC)/策略与计费控制(Policy and Charging Control，简称为PCC)网络提供了一种通用的认证、授权和计费(AAA)信令支持。“Diameter基本协议”定义了Diameter节点的网络角色是各种代理(Agent)，其中，可以包括：中继代理(Relay Agent)、代理人代理(Proxy Agent)、重定向代理(Redirect Agent)和翻译代理(Translate Agent)，所有类型的代理都维护事务状态(Transaction State)，除中继代理之外的其他代理还可以维护会话状态(Session State)。
由于第四代移动通信技术(4G)用户的增长导致LTE/EPC/PCC网络中的Diameter信令呈爆炸性增长。为了应对上述情况发生，运营商仿效SS7信令网，通过路由代理节点(Diameter Routing Agent，简称为DRA)组建Diameter信令网，用于Diameter信令的疏通。图1是根据相关技术的在IP网上建立的网上网(即Diameter信令转接网)的组网示意图。如图1所示，即使没有一个DRA，业务节点之间也是可以通过Diameter信令直接访问的。故而称DRA信令转接网是在互联网协议(IP)承载网上构建的网上网。图2是根据相关技术的将Diameter信令转接网分为国际层和国内层的示意图。如图2所示，Diameter信令网可以分为国际Diameter信令网和国内Diameter信令网，漫游国的移动管理实体(MME)的位置更新请求(ULR)消息通过漫游国的DRA信令转接网转发至国际DRA信令转接网的漫游国iDRA1，再转发到归属国iDRA2，继而转发到归属国的DRA信令转接网，最后落地到归属国的归属用户服务器(HSS)，在图2中ULR消息总共经过6次DRA转发。
Diameter节点之间可以通过流控制传输协议(Stream Control Transmission Protocol，简称为SCTP)偶连或者传输控制协议(Control Transmission Protocol，简称为TCP)连接作为数据承载链路，通过能够交换请求(Capabilities Exchange Request，简称为CER)/能力交换响应(Capabilities Exchange Answer，简称为CEA)消息交互 进行能力协商，通过设备监控请求(Device Watchdog Request，简称为DER)/设备监控响应(Device Watchdog Answer，简称为DEA)消息交互进行信令链路的检测和恢复，以构成Diameter信令链路层。通过域路由表(Realm Routing Table)为Diameter请求(Request)消息进行网路路由；通过Diameter事务处理(一个Diameter事务可以包括一个请求消息以及一个与之对应的响应消息)和Diameter会话处理(一个Diameter会话可以包括一个或者多个事务且所有事务均具有相同的会话标识(SessionId))，以此为各个应用接口提供了通用的实现框架。图3是根据相关技术的按照OSI模型，DRA网络的协议层次示意图。如图3所示，参考国际标准化阻值(ISO)提出的开放系统互连参考模型(OSI)的七层网络模型，虽然流控制传输协议(SCTP)在IP网络中属于事务层，但是，在Diameter信令转接网络或者SigTran网络中，都只是信令链路层的一部分。DRA网络层中的域路由表(Realm Routing Table)仅为请求消息提供路由，ACK消息按照请求消息的原路径返回，而不再进行路由分析。
除了OSI七层网络构架外，ISO组织还提出了消息在网络中传递的标准模型。消息在网络中传递时，中间节点(即信令转接点)仅提供网络层功能，事务层及事务层以上层才是“端到端”的。图4是根据相关技术的按照OSI模型，业务节点之间信令转发的标准模型的示意图。如图4所示，中间节点可以通过网络层进行转发，事务层及以上层才是‘端到端’的。IP网络、SS7网络、SigTran网络都是符合这个模型的。
但是，通过Diameter节点组网时，DRA作为中间节点，提供了事务层甚至还有会话层。
图5是根据相关技术的Diameter业务节点之间通过DRA转发时信令传递方式1，DRA仅维持事务状态的示意图。如图5所示，中间节点在事务层转发，维护事务层处理。图6是根据相关技术的Diameter业务节点之间通过DRA转发时信令传递方式2，DRA维持事务状态和会话状态的示意图。如图6所示，中间节点在会话层转发，维护事务层和会话层处理。然而，在图5和图6中均没有提供完善的网络层功能，即响应消息无法单独路由，而需要按照请求消息的入局路径原路返回。
作为信令转接点，DRA提供事务管理其实是一个缺陷。DRA需要维护事务状态，一旦该DRA退出服务，其上承载的所有事务都将失败。对于此缺陷，当前可采取的措施是：对于失败的事务，Diameter客户端或者DRA对事务的请求消息进行消息重发(在等待Diameter响应的定时器超时的情况下)或者路由重选(当等待ACK响应时，接收到携带失败码的响应)，选择其他DRA节点进行再次尝试。
依靠事务层的消息重发或者路由重选措施来弥补Diameter响应消息无法单独路由的缺陷会带来以下弊端：
(1)当作为中间节点的某个DRA退出服务时，其维护的任何一个事务，该事务经过的所有中间节点和业务节点对应的事务资源都会短暂吊死，直到各个节点的事务保护定时器超时或接收到失败的ACK响应。由于退出服务的DRA同时转发的事务可能成千上万，此短暂吊死现象将会影响整个Diameter网络全部节点的事务资源。
(2)一旦事务保护定时器超时，Diameter客户端或DRA节点则会重发请求消息(对于重发的请求消息设置‘T’标记)，大量的重发请求消息对整个Diameter信令网造成很大的冲击。如果该退出服务的DRA有一个负荷分担节点，除本身的负荷外，此负荷分担节点既要承担该DRA退出服务的负荷，还需要承担所有消息重发的信令负荷，短期负荷剧增3倍。当开启多次重发，多个节点重发时，对网络的影响更甚。
(3)DRA节点的事务资源(以及会话资源)可能成为瓶颈，成为无意的或者恶意地攻击对象。例如：某个归属位置寄存器(Home Location Register，简称为HLR)对REQ消息不回响应，相当于拒绝服务(Deny Of Service，简称为DoS)攻击，数秒钟即可占用所有事务资源，进而造成其他事务无法正常转发。
发明内容
本发明实施例提供了一种响应消息的获取、响应消息的路由方法、装置及系统，以至少解决相关技术中依靠事务层的消息重发或者路由重选措施来弥补Diameter响应消息无法单独路由存在较大缺陷的问题。
根据本发明的一个方面，提供了一种响应消息的获取方法。
根据本发明实施例的响应消息的获取方法包括：源节点通过第一组DRA节点向第二组节点发送业务请求消息，其中，第二组节点包括：目的节点和第二组DRA节点；业务请求消息中携带有第一标识信息、第二标识信息和第三标识信息，业务请求消息的第一标识信息用于标识目的节点，业务请求消息的第二标识信息用于指示第一组DRA节点按照第一标识信息对业务请求消息进行路由转发以及指示目的节点将业务响应消息的第一标识信息设置为业务请求消息的第三标识信息，业务请求消息的第三标识信息用于标识源节点；源节点通过第二组DRA节点获取目的节点返回的业务响应消息。
优选地，业务请求消息的第一标识信息为目的域名(Destination-Realm)和目的主机名(Destination-Host)的属性值对(AVP)。
优选地，业务请求消息的第三标识信息为源域名(Origin-Realm)和源主机名(Origin-Host)的AVP。
优选地，业务请求消息的第二标识信息为在Diameter消息头中新增的命令标记。
优选地，业务请求消息在经由第一组DRA节点进行路由转发过程中，第一组DRA节点中的每个DRA节点在对业务请求消息进行路由分析后将业务请求消息转发至相邻的下一个DRA节点或者目的节点，且无需进行事务处理和/或会话处理。
优选地，第一组DRA节点和第二组DRA节点分别为源节点与目的节点之间的两条不同链路，其中，第一组DRA节点中的一个或多个DRA节点在业务请求消息的路由转发过程中退出服务。
根据本发明的另一方面，提供了一种响应消息的路由方法。
根据本发明实施例的响应消息的路由方法包括：目的节点通过第一组DRA节点接收来自于源节点的业务请求消息，其中，业务请求消息中携带有第一标识信息、第二标识信息和第三标识信息，业务请求消息的第一标识信息为目的节点的标识，业务请求消息的第二标识信息用于指示第一组DRA节点按照业务请求消息的第一标识信息对业务请求消息进行路由转发以及指示目的节点将业务响应消息的第一标识信息设置为业务请求消息的第三标识信息，业务请求消息的第三标识信息用于标识源节点；目的节点按照业务请求消息的第二标识信息将业务响应消息的第一标识信息设置为为业务请求消息的第三标识信息，并通过第二组节点向源节点返回业务响应消息，其中，第二组节点包括：目的节点和第二组DRA节点。
优选地，目的节点按照业务请求消息的第二标识信息将业务请求消息的第一标识信息设置为业务请求消息的第三标识信息包括以下至少之一：目的节点将业务响应消息中携带的目的域名(Destination-Realm)设置为源节点的源域名(Origin-Realm)；目的节点将业务响应消息中携带的目的主机名(Destination-Host)设置为源节点的源主机名(Origin-Host)。
优选地，业务请求消息的第二标识信息为在Diameter消息头中新增的命令标记。
优选地，业务响应消息在通过第二组节点进行路由转发过程中，第二组节点中的每一个节点对业务响应消息进行路由分析，并根据路由结果将业务响应消息转发至相邻的下一个DRA节点或者源节点，且无需进行事务处理和/或会话处理。
根据本发明的又一方面，提供了一种响应消息的获取装置。
根据本发明实施例的响应消息的获取装置包括：发送模块，设置为通过第一组DRA节点向第二组节点发送业务请求消息，其中，第二组节点包括：目的节点和第二组DRA节点；业务请求消息中携带有第一标识信息、第二标识信息和第三标识信息，业务请求消息的第一标识信息用于标识目的节点，业务请求消息的第二标识信息用于指示第一组DRA节点按照第一标识信息对业务请求消息进行路由转发以及指示目的节点将业务响应消息的第一标识信息设置为发送业务请求消息的第三标识信息，业务请求消息的第三标识信息用于标识源节点；获取模块，设置为通过第二组DRA节点获取目的节点返回的业务响应消息。
优选地，业务请求消息的第一标识信息为目的域名(Destination-Realm)和目的主机名(Destination-Host)的AVP。
优选地，业务请求消息的第三标识信息为源域名(Origin-Realm)和源主机名(Origin-Host)的AVP。
优选地，业务请求消息的第二标识信息为在Diameter消息头中新增的命令标记。
优选地，业务请求消息在经由第一组DRA节点进行路由转发过程中，第一组DRA节点中的每个DRA节点在对业务请求消息进行路由分析后将业务请求消息转发至相邻的下一个DRA节点或者目的节点，且无需进行事务处理和/或会话处理。
优选地，第一组DRA节点和第二组DRA节点分别为源节点与目的节点之间的两条不同链路，其中，第一组DRA节点中的一个或多个DRA节点在业务请求消息的路由转发过程中退出服务。
根据本发明的再一方面，提供了一种响应消息的路由装置。
根据本发明实施例的响应消息的路由装置包括：接收模块，设置为通过第一组DRA节点接收来自于源节点的业务请求消息，其中，业务请求消息中携带有第一标识信息、第二标识信息和第三标识信息，业务请求消息的第一标识信息为目的节点的标识，业务请求消息的第二标识信息用于指示第一组DRA节点按照业务请求消息的第一标识信息对业务请求消息进行路由转发以及指示目的节点将业务响应消息的第一标 识信息设置为业务请求消息的第三标识信息，业务请求消息的第三标识信息用于标识源节点；确定模块，设置为按照业务请求消息的第二标识信息将业务响应消息的第一标识信息设置为业务请求消息的第三标识信息，并通过第二组DRA节点向源节点返回业务响应消息，其中，第二组节点包括：目的节点和第二组DRA节点。
优选地，确定模块包括：第一处理单元，设置为将业务响应消息中携带的目的域名(Destination-Realm)设置为源节点的源域名(Origin-Realm)；第二处理单元，设置为将业务响应消息中携带的目的主机名(Destination-Host)设置为源节点的源主机名(Origin-Host)。
优选地，业务请求消息的第二标识信息为在Diameter消息头中新增的命令标记。
优选地，业务响应消息在通过第二组节点进行路由转发过程中，第二组节点中的每一个节点对业务响应消息进行路由分析，并根据理由结果将业务响应消息转发至相邻的下一个DRA节点或者是源节点，且无需进行事务处理和/或会话处理。
根据本发明的再一方面，提供了一种响应消息的获取和响应消息的路由系统。
根据本发明实施例的响应消息的获取和响应消息的路由系统包括：业务源节点、业务目的节点，从业务源节点向业务目的节点发送业务请求消息所经过的第一组DRA节点以及从业务目的节点向业务源节点发送业务响应消息所经过的第二组DRA节点。
通过本发明实施例，采用源节点通过第一组DRA节点向第二组节点发送业务请求消息，其中，第二组节点包括：目的节点和第二组DRA节点；业务请求消息中携带有第一标识信息、第二标识信息和第三标识信息，业务请求消息的第一标识信息用于标识目的节点，业务请求消息的第二标识信息用于指示第一组DRA节点按照第一标识信息对业务请求消息进行路由转发以及指示目的节点将业务响应消息的第一标识信息设置为业务请求消息的第三标识信息，业务请求消息的第三标识信息用于标识源节点；源节点通过第二组DRA节点获取目的节点返回的业务响应消息，解决了相关技术中依靠事务层的消息重发或者路由重选措施来弥补Diameter响应消息无法单独路由存在较大缺陷的问题，进而提高了网络层的可靠性，降低了对Diameter服务器的重发消息处理能力的依赖。
附图说明
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1是根据相关技术的在IP网上建立的网上网(即Diameter信令转接网)的组网示意图；
图2是根据相关技术的将Diameter信令转接网分为国际层和国内层的示意图；
图3是根据相关技术的按照OSI模型，DRA网络的协议层次示意图；
图4是根据相关技术的按照OSI模型，业务节点之间信令转发的标准模型的示意图；
图5是根据相关技术的Diameter业务节点之间通过DRA转发时信令传递方式1，DRA仅维持事务状态的示意图；
图6是根据相关技术的Diameter业务节点之间通过DRA转发时信令传递方式2，DRA维持事务状态和会话状态的示意图；
图7是根据本发明实施例的响应消息的获取方法的流程图；
图8是根据本发明优选实施例的Diameter消息头定义的示意图；
图9是根据本发明优选实施例的命令标记定义的示意图；
图10是根据本发明实施例的响应消息的路由方法的流程图；
图11是根据本发明优选实施例的DRA关口代理组网，国际DRA网络不支持‘N’标记的示意图；
图12是根据本发明优选实施例的由4个DRA组成单层双平面最简化组网的示意图；
图13是根据本发明优选实施例的当特定DRA退出服务时，事务请求和响应消息的转发过程的流程图；
图14是根据本发明优选实施例的由8个DRA组成双层双平面最简化组网的示意图；
图15是在特定HDRA退出服务时，事务请求和响应消息的转发过程的流程图；
图16是根据本发明优选实施例的DRA关口代理组网，业务节点不支持‘N’标记的示意图；
图17是根据本发明实施例的响应消息的获取装置的结构框图；
图18是根据本发明实施例的响应消息的路由装置的结构框图；
图19是根据本发明实施例的响应消息的获取和响应消息的路由系统的结构示意图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本发明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
图7是根据本发明实施例的响应消息的获取方法的流程图。如图7所示，该方法可以包括以下处理步骤：
步骤S702：源节点通过第一组DRA节点向第二组节点发送业务请求消息，其中，第二组节点包括：目的节点和第二组DRA节点；业务请求消息中携带有第一标识信息、第二标识信息和第三标识信息，业务请求消息的第一标识信息用于标识目的节点，业务请求消息的第二标识信息用于指示第一组DRA节点按照第一标识信息对业务请求消息进行路由转发以及指示目的节点将业务响应消息的第一标识信息设置为业务请求消息的第三标识信息，业务请求消息的第三标识信息用于标识源节点；
步骤S704：源节点通过第二组DRA节点获取目的节点返回的业务响应消息。
相关技术中依靠事务层的消息重发或者路由重选措施来弥补Diameter响应消息无法单独路由存在较大缺陷。采用如图7所示的方法，通过在业务请求消息中携带用于标识目的节点的第一标识信息，并且还携带有用于指示第一组DRA节点按照第一标识信息对业务请求消息进行路由转发以及指示目的节点将业务响应消息的第一标识信息设置为标识源节点的业务请求消息的第三标识信息，简化了DRA作为信令转接点的功能，去掉事务处理和会话处理，由此解决了相关技术中依靠事务层的消息重发或 者路由重选措施来弥补Diameter响应消息无法单独路由存在较大缺陷的问题，进而提高了网络层的可靠性，降低了对Diameter服务器的重发消息处理能力的依赖。
优选地，上述业务请求消息的第二标识信息可以为在Diameter消息头中新增的命令标记。
在优选实施例中，可以在Diameter消息头中增加一个标记(‘N’)，当请求消息和响应消息中的‘N’标记均设置为1时，表示按照本发明实施例所提供的技术方案进行处理。当接收的Diameter请求/响应消息的消息头中未含有‘N’标记时，则按照现有的方式进行处理。
图8是根据本发明优选实施例的Diameter消息头定义的示意图。如图8所示，参见RFC 3588，其中，命令标记(Command Flags)定义如图9所示，图9是根据本发明优选实施例的命令标记定义的示意图。在图9中，命令标记的比特4/5/6/7均为保留字段，可以定义比特4为‘N’，其含义为网络(Network)。
在优选实施例中，对于Diameter消息中‘N’命令标记的设置，如果全网Diameter节点均支持本发明实施例所提供的技术方案，则可以在Diameter业务节点设置；如果某个业务节点不支持‘N’标记，则将直接连接该业务节点的DRA作为DRA代理关口节点，在DRA代理关口节点上转发消息时设置。这样，业务节点不需要升级版本。如果仅本网支持‘N’标记，则将直接连接其他DRA网络(例如：国际DRA网络)的DRA作为DRA代理关口节点，在DRA代理关口节点上转发消息时不设置。这样，非本网Diameter节点不需要升级版本。
优选地，上述业务请求消息的第一标识信息可以为目的域名(Destination-Realm)和目的主机名(Destination-Host)的属性值对AVP。
优选地，上述业务请求消息的第三标识信息为源域名(Origin-Realm)和源主机名(Origin-Host)的AVP。
当接收的Diameter响应消息的消息头中含有‘N’标记时，DRA节点对Destination-Realm、Destination-Host进行路由分析并转发该响应消息，在消息转发过程中也同时转发消息中携带的Destination-Realm、Destination-Host属性值对。
优选地，业务请求消息在经由第一组DRA节点进行路由转发过程中，第一组DRA节点中的每个DRA节点在对业务请求消息进行路由分析后将业务请求消息转发至相邻的下一个DRA节点或者目的节点，且无需进行事务处理和/或会话处理。
当接收的Diameter请求消息的消息头中含有‘N’标记时，DRA节点进行路由分析并转发该请求消息，但不保存事务状态(或会话状态)。即简化了DRA作为信令转接点的功能，去掉事务处理和会话处理。又由于去掉了事务/会话资源，DRA就不会发生事务/会话资源短缺，或被恶意或无意的攻击。
在优选实施过程中，对于DRA接收到Diameter消息，消息含‘N’命令标记时的处理，如果消息为Diameter请求消息，即消息中的‘R’标记为1，本DRA不维护事务状态和会话状态，通过路由分析获取路由，转发消息(含‘N’标记)；如果消息为Diameter响应消息，即消息中的‘R’标记为0，本DRA通过路由分析获取路由，转发消息(可以包括：Destination-Realm、Destination-Host AVP、‘N’标记)。
优选地，第一组DRA节点和第二组DRA节点分别为源节点与目的节点之间的两条不同链路，其中，第一组DRA节点中的一个或多个DRA节点在业务请求消息的路由转发过程中退出服务。即一旦某个DRA临时或者永久地退出服务，diameter响应消息可以从其他节点转发，从而提高了网络层的可靠性。
图10是根据本发明实施例的响应消息的路由方法的流程图。如图10所示，该方法可以包括以下处理步骤：
步骤S1002：目的节点通过第一组DRA节点接收来自于源节点的业务请求消息，其中，业务请求消息中携带有第一标识信息、第二标识信息和第三标识信息，业务请求消息的第一标识信息为目的节点的标识，业务请求消息的第二标识信息用于指示第一组DRA节点按照业务请求消息的第一标识信息对业务请求消息进行路由转发以及指示目的节点将业务响应消息的第一标识信息设置为业务请求消息的第三标识信息，业务请求消息的第三标识信息用于标识源节点；
步骤S1004：目的节点按照业务请求消息的第二标识信息将业务响应消息的第一标识信息设置为业务请求消息的第三标识信息，并通过第二组节点向源节点返回业务响应消息，其中，第二组节点包括：目的节点和第二组DRA节点。
优选地，在步骤S1004中，目的节点按照业务请求消息的第二标识信息将业务请求消息的第一标识信息设置为业务请求消息的第三标识信息可以包括以下操作至少之一：
步骤S1：目的节点将业务响应消息中携带的目的域名(Destination-Realm)设置为源节点的源域名(Origin-Realm)；
步骤S2：目的节点将业务响应消息中携带的目的主机名(Destination-Host)设置为源节点源主机名(Origin-Host)。
在优选实施例中，所有Diameter响应(ACK)消息中均增加目的域名(Destination-Realm)、目的主机名(Destination-Host)为可选属性值对(AVP)，用于ACK消息的路由。当请求消息中的‘N’标记为1时，产生响应消息的节点将请求消息中的源域名(Origin-Realm)设置为响应消息的Destination-Realm；将请求消息中的源主机名(Origin-Host)设置为响应消息的Destination-Host。
优选地，上述业务响应消息在通过第二组DRA节点进行路由转发过程中，第二组节点中的每一个节点对业务响应消息进行路由分析，并根据路由结果将业务响应消息转发至相邻的下一个DRA节点或者源节点，且无需进行事务处理和/或会话处理。
下面将结合图11至图16所示优选实施方式对上述优选实施过程作进一步的描述。
图11是根据本发明优选实施例的DRA关口代理组网，国际DRA网络不支持‘N’标记的示意图。如图11所示，DRA2作为DRA关口代理，其左下方的本国Diameter信令转发网络支持‘N’标记，而其右上方的所有Diameter节点都不支持‘N’标记，便于兼容不支持本发明实施例所提供的技术方案的其他网络。当关口DRA转发响应消息时，DRA2作为DRA关口代理，可以根据事务数据区记录的请求消息将接收REQ消息中的Origin-Realm设置为ACK消息的Destination-Realm；并且将接收REQ消息中的Origin-Host设置为ACK消息的Destination-Host。
图12是根据本发明优选实施例的由4个DRA组成单层双平面最简化组网的示意图。如图12所示，在该组网模型下，当‘N’标记为1时，所有转发Diameter响应消息的节点都进行路由分析，获取可用的DRA节点并进行消息转发。DRA可以分为A/B两个平面，每个大区有一对DRA，每个平面一个。该大区的任何一个业务节点同时与一对DRA连接，负荷分担方式。相同平面的DRA两两互连，在两个平面之间，仅成对的DRA之间存在Diameter信令链接，称为C链路。
图13是根据本发明优选实施例的当特定DRA退出服务时，事务请求和响应消息的转发过程的流程图。如图13所示，该流程可以包括以下处理步骤：
步骤S1302：MME用户发起注册，终端发送更新位置请求(Update Location Request，简称为ULR)消息到DRA1，其中，该ULR消息中携带有国际移动用户识别码(IMSI)号码、目的域名信息，设置‘N’标记。
步骤S1304：DRA1在接收到该ULR消息后，进行路由分析并将该ULR消息转发至DRA3，设置‘N’标记。
步骤S1306：DRA3接收到该消息后，进行路由分析，并将消息转发给HSS，设置‘N’标记。
步骤S1308-S1314：此时DRA1由于版本升级，在所有Diameter的SCTP偶联上发送SHUTDOWN消息，接收到SHUTDOWN ACK消息后，退出服务。
步骤S1316：HSS在接收到ULR消息后，向DRA3发送ULA消息，ULA消息的Destination-Host设置为MME，设置‘N’标记。
步骤S1318：DRA3在接收到ULA消息后，进行路由分析，向DRA4发送ULA消息，其中，该ULA消息中携带有‘N’标记。
步骤S1320：DRA4在接收到ULA消息后，进行路由分析，向DRA2发送ULA消息，其中，该ULA消息中携带有‘N’标记。
步骤S1322：DRA2在接收到ULA消息后，进行路由分析，向MME发送ULA消息。MME上的事务成功。
图14是根据本发明优选实施例的由8个DRA组成双层双平面最简化组网的示意图。如图14所示，DRA信令转接网可以分为两层：H层和L层。所有大区组成H层，每个大区的全部省组成L层。
L层可以分为A/B两个平面，每个省有一对DRA，每个平面一个。该省的任何一个业务节点(例如：MME)同时与一对低级DRA(Low Diameter Routing Agent，简称为LDRA)连接，负荷分担方式。相同平面的LDRA两两互连，两个平面之间，仅成对的LDRA之间存在Diameter信令链接，称为C链路。
H层也可以分为A/B两个平面，每个大区有一对DRA，每个平面一个。该大区的任何一对LDRA与一对LDRA连接，负荷分担方式。相同平面的高级DRA(High Diameter Routing Agent，简称为HDRA)两两互连，两个平面之间，仅成对的HDRA之间存在Diameter信令链接，称为C链路。对于业务节点(例如：HSS)，则同时与一对HDRA链接，负荷分担。
图15是在特定HDRA退出服务时，事务请求和响应消息的转发过程的流程图。如图15所示，该流程可以包括以下处理步骤：
步骤1502：MME用户发起注册，终端向DRA1发送ULR消息，其中，该ULR消息中携带有IMSI号码，目的域名信息，设置‘N’标记。
步骤1504：DRA1在接收到该消息后，进行路由分析，并将消息转发至DRA3，设置‘N’标记。
步骤1506：DRA3在接收到该消息后，进行路由分析，并将消息转发至HDRA1，设置‘N’标记。
步骤1508：HDRA1在接收到该消息后，进行路由分析，并将消息转发至HDRA3，设置‘N’标记。
步骤1510：HDRA3在接收到该消息后，进行路由分析，并将消息转发至HSS，设置‘N’标记。
步骤1512-1522：此时，HDRA1由于版本升级，在所有Diameter的SCTP偶联上发送SHUTDOWN消息，接收到SHUTDOWN ACK消息后，退出服务。
步骤1524：HSS在接收到ULR消息后，向HDRA3发送ULA消息，其中，该ULA消息的DestHost设置为MME，设置‘N’标记。
步骤1526：HDRA3在接收到ULA消息后，进行路由分析，向HDRA4发送ULA消息，其中，该ULA消息中携带有‘N’标记。
步骤1528：HDRA4在接收到ULA消息后，进行路由分析，向HDRA2发送ULA消息，其中，该ULA消息中携带有‘N’标记。
步骤1530：HDRA2在接收到ULA消息后，进行路由分析，向LDRA4发送ULA消息，其中，该ULA消息中携带有‘N’标记。
步骤1532：LDRA4在接收到ULA消息后，进行路由分析，向LDRA2发送ULA消息，其中，该ULA消息中携带有‘N’标记。
步骤1534：LDRA2在接收到ULA消息后，进行路由分析，向MME发送ULA消息。MME上的事务成功。
图16是根据本发明优选实施例的DRA关口代理组网，业务节点不支持‘N’标记的示意图。如图16所示，DRA1作为DRA关口代理，其左下方的MME节点不支 持‘N’标记，而其右上方的Diameter节点都支持‘N’标记，便于兼容不支持本发明实施例所提供的技术方案的业务节点。
DRA1需要维护与MME之间的事务，此段上的响应消息不需要路由，直接按照DRA1上记录的原事务路径返回；DRA1不需要维护与DRA2之间的事务，此段上响应消息，DRA2按照路由分析方式单独路由。由此体现了DRA1作为关口代理的双重身份。除DRA1外，其他DRA都不需要维护事务状态。
图17是根据本发明实施例的响应消息的获取装置的结构框图。该装置可以应用于源节点，如图17所示，该响应消息的获取装置可以包括：发送模块10，设置为通过第一组DRA节点向第二组节点发送业务请求消息，其中，第二组节点包括：目的节点和第二组DRA节点；业务请求消息中携带有第一标识信息、第二标识信息和第三标识信息，业务请求消息的第一标识信息用于标识目的节点，业务请求消息的第二标识信息用于指示第一组DRA节点按照第一标识信息对业务请求消息进行路由转发以及指示目的节点将业务响应消息的第一标识信息设置为发送业务请求消息的第三标识信息，业务请求消息的第三标识信息用于标识源节点；获取模块20，设置为通过第二组DRA节点获取目的节点返回的业务响应消息。
采用如图17所示的装置，解决了相关技术中依靠事务层的消息重发或者路由重选措施来弥补Diameter响应消息无法单独路由存在较大缺陷的问题，进而提高了网络层的可靠性，降低了对Diameter服务器的重发消息处理能力的依赖。
优选地，业务请求消息的第一标识信息为目的域名(Destination-Realm)和目的主机名(Destination-Host)的AVP。
优选地，业务请求消息的第三标识信息为源域名(Origin-Realm)和源主机名(Origin-Host)的AVP。
优选地，业务请求消息的第二标识信息为在Diameter消息头中新增的命令标记。
优选地，业务请求消息在经由第一组DRA节点进行路由转发过程中，第一组DRA节点中的每个DRA节点在对业务请求消息进行路由分析后将业务请求消息转发至相邻的下一个DRA节点或者目的节点，且无需进行事务处理和/或会话处理。
优选地，第一组DRA节点和第二组DRA节点分别为源节点与目的节点之间的两条不同链路，其中，第一组DRA节点中的一个或多个DRA节点在业务请求消息的路由转发过程中退出服务。
图18是根据本发明实施例的响应消息的路由装置的结构框图。如图18所示，该响应消息的路由装置可以包括：接收模块30，设置为通过第一组DRA节点接收来自于源节点的业务请求消息，其中，业务请求消息中携带有第一标识信息、第二标识信息和第三标识信息，业务请求消息的第一标识信息为目的节点的标识，业务请求消息的第二标识信息用于指示第一组DRA节点按照业务请求消息的第一标识信息对业务请求消息进行路由转发以及指示目的节点将业务响应消息的第一标识信息设置为业务请求消息的第三标识信息，业务请求消息的第三标识信息用于标识源节点；确定模块40，设置为按照业务请求消息的第二标识信息将业务响应消息的第一标识信息替换为业务请求消息的第三标识信息，并通过第二组DRA节点向源节点返回业务响应消息，其中，第二组节点包括：目的节点和第二组DRA节点。
优选地，确定模块40可以包括：第一处理单元(图中未示出)，设置为将业务响应消息中携带的目的域名(Destination-Realm)设置为源节点的源域名(Origin-Realm)；第二处理单元(图中未示出)，设置为将业务响应消息中携带的目的主机名(Destination-Host)设置为源节点的源主机名(Origin-Host)。
优选地，业务请求消息的第二标识信息为在Diameter消息头中新增的命令标记。
优选地，上述业务响应消息在通过第二组节点进行路由转发过程中，第二组节点中的每一个节点对业务响应消息进行路由分析，并根据理由结果将业务响应消息转发至相邻的下一个DRA节点或者是源节点，且无需进行事务处理和/或会话处理。
需要说明的是，上述响应消息的路由装置不仅可以设置在业务目的节点中，当然还可以设置在业务响应消息路由经过的DRA节点中。
图19是根据本发明实施例的响应消息的获取和响应消息的路由系统的结构示意图。如图19所示，该响应消息的获取和响应消息的路由系统可以包括：业务源节点1、业务目的节点2，从业务源节点向业务目的节点发送业务请求消息所经过的第一组DRA节点3以及从业务目的节点向业务源节点发送业务响应消息所经过的第二组DRA节点4。
上述业务源节点和业务目的节点为所有支持Diameter信令的节点，例如：HSS、MME、PCRF、PCEF、BBERF、OCS、SGSN、DRA、关口代理。
从以上的描述中，可以看出，上述实施例实现了如下技术效果(需要说明的是这些效果是某些优选实施例可以达到的效果)：采用本发明实施例所提供的技术方案，当DRA作为信令转接点组建Diameter信令网时，规范消息转发的DRA提供完善的网络 层功能：全部消息(包括：请求REQ消息和响应ACK消息)都当成完全独立的消息，可独立进行路由；去掉事务层管理(和会话层管理)，通过网络层本身解决某DRA节点退出服务的响应消息的网络层转发，而并非依靠上层(事务层)通过重发来弥补，以避免事务资源的瓶颈和网络负荷暴增等缺陷，由此提高信令转接网的可靠性。
显然，本领域的技术人员应该明白，上述的本发明的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
以上所述仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。
工业实用性
如上所述，本发明实施例提供的一种响应消息的获取、响应消息的路由方法、装置及系统具有以下有益效果：逐步摆脱依靠事务层的消息重发或者路由重选措施来弥补Diameter响应消息无法单独路由存在较大缺陷，提高了网络层的可靠性，降低了对Diameter服务器的重发消息处理能力的依赖。

Claims (21)

  1. 一种响应消息的获取方法，包括：
    源节点通过第一组路由代理DRA节点向第二组节点发送业务请求消息，其中，所述第二组节点包括：目的节点和第二组DRA节点；所述业务请求消息中携带有第一标识信息、第二标识信息和第三标识信息，所述业务请求消息的第一标识信息用于标识所述目的节点，所述业务请求消息的第二标识信息用于指示所述第一组DRA节点按照所述第一标识信息对所述业务请求消息进行路由转发以及指示所述目的节点将业务响应消息的第一标识信息设置为所述业务请求消息的第三标识信息，所述业务请求消息的第三标识信息用于标识所述源节点；
    所述源节点通过第二组DRA节点获取所述目的节点返回的所述业务响应消息。
  2. 根据权利要求1所述的方法，其中，所述业务请求消息的第一标识信息为目的域名Destination-Realm和目的主机名Destination-Host的属性值对AVP。
  3. 根据权利要求1所述的方法，其中，所述业务请求消息的第三标识信息为源域名Origin-Realm和源主机名Origin-Host的AVP。
  4. 根据权利要求1所述的方法，其中，所述业务请求消息的第二标识信息为在Diameter消息头中新增的命令标记。
  5. 根据权利要求1所述的方法，其中，所述业务请求消息在经由所述第一组DRA节点进行路由转发过程中，所述第一组DRA节点中的每个DRA节点在对所述业务请求消息进行路由分析后将所述业务请求消息转发至相邻的下一个DRA节点或者所述目的节点，且无需进行事务处理和/或会话处理。
  6. 根据权利要求1至5中任一项所述的方法，其中，所述第一组DRA节点和所述第二组DRA节点分别为所述源节点与所述目的节点之间的两条不同链路，其中，所述第一组DRA节点中的一个或多个DRA节点在所述业务请求消息的路由转发过程中退出服务。
  7. 一种响应消息的路由方法，包括：
    目的节点通过第一组路由代理DRA节点接收来自于源节点的业务请求消息，其中，所述业务请求消息中携带有第一标识信息、第二标识信息和第三标识信息，所述业务请求消息的第一标识信息为目的节点的标识，所述业务请求消息的第二标识信息用于指示所述第一组DRA节点按照所述业务请求消息的第一标识信息对所述业务请求消息进行路由转发以及指示所述目的节点将业务响应消息的第一标识信息设置为所述业务请求消息的第三标识信息，所述业务请求消息的第三标识信息用于标识所述源节点；
    所述目的节点按照所述业务请求消息的第二标识信息将所述业务响应消息的第一标识信息设置为所述业务请求消息的第三标识信息，并通过第二组节点向所述源节点返回所述业务响应消息，其中，所述第二组节点包括：所述目的节点和第二组DRA节点。
  8. 根据权利要求7所述的方法，其中，所述目的节点按照所述业务请求消息的第二标识信息将所述业务请求消息的第一标识信息设置为所述业务请求消息的第三标识信息包括以下至少之一：
    所述目的节点将所述业务响应消息中携带的目的域名Destination-Realm设置为所述源节点的源域名Origin-Realm；
    所述目的节点将所述业务响应消息中携带的目的主机名Destination-Host设置为所述源节点的源主机名Origin-Host。
  9. 根据权利要求7所述的方法，其中，所述业务请求消息的第二标识信息为在Diameter消息头中新增的命令标记。
  10. 根据权利要求7所述的方法，其中，所述业务响应消息在通过所述第二组节点进行路由转发过程中，所述第二组节点中的每一个节点对所述业务响应消息中的所述第一信息标识进行路由分析，并根据路由结果将所述业务响应消息转发至相邻的下一个DRA节点或者所述源节点，且无需进行事务处理和/或会话处理。
  11. 一种响应消息的获取装置，包括：
    发送模块，设置为通过第一组路由代理DRA节点向第二组节点发送业务请求消息，其中，所述第二组节点包括：目的节点和第二组DRA节点；所述业务请求消息中携带有第一标识信息、第二标识信息和第三标识信息，所述业务请求消息的第一标识信息用于标识所述目的节点，所述业务请求消息的第二标识信息用于指示所述第一组DRA节点按照所述第一标识信息对所述业务请 求消息进行路由转发以及指示所述目的节点将业务响应消息的第一标识信息设置为所述业务请求消息的第三标识信息，所述业务请求消息的第三标识信息用于标识所述源节点；
    获取模块，设置为通过第二组节点获取所述目的节点返回的所述业务响应消息。
  12. 根据权利要求11所述的装置，其中，所述业务请求消息的第一标识信息为目的域名Destination-Realm和目的主机名Destination-Host的属性值对AVP。
  13. 根据权利要求11所述的装置，其中，所述业务请求消息的第三标识信息为源域名Origin-Realm和源主机名Origin-Host的AVP。
  14. 根据权利要求11所述的装置，其中，所述业务请求消息的第二标识信息为在Diameter消息头中新增的命令标记。
  15. 根据权利要求11所述的装置，其中，所述业务请求消息在经由所述第一组DRA节点进行路由转发过程中，所述第一组DRA节点中的每个DRA节点在对所述业务请求消息进行路由分析后将所述业务请求消息转发至相邻的下一个DRA节点或者所述目的节点，且无需进行事务处理和/或会话处理。
  16. 根据权利要求11至15中任一项所述的装置，其中，所述第一组DRA节点和所述第二组DRA节点分别为所述源节点与所述目的节点之间的两条不同链路，其中，所述第一组DRA节点中的一个或多个DRA节点在所述业务请求消息的路由转发过程中退出服务。
  17. 一种响应消息的路由装置，包括：
    接收模块，设置为通过第一组路由代理DRA节点接收来自于源节点的业务请求消息，其中，所述业务请求消息中携带有第一标识信息、第二标识信息和第三标识信息，所述业务请求消息的第一标识信息为目的节点的标识，所述业务请求消息的第二标识信息用于指示所述第一组DRA节点按照所述业务请求消息的第一标识信息对所述业务请求消息进行路由转发以及指示目的节点将业务响应消息的第一标识信息设置为所述业务请求消息的第三标识信息，所述业务请求消息的第三标识信息用于标识所述源节点；
    确定模块，设置为按照所述业务请求消息的第二标识信息将所述业务响应消息的第一标识信息设置为所述业务请求消息的第三标识信息，并通过第二组 节点向所述源节点返回所述业务响应消息，其中，所述第二组节点包括：所述目的节点和第二组DRA节点。
  18. 根据权利要求17所述的装置，其中，所述确定模块包括：
    第一处理单元，设置为将所述业务响应消息中携带的目的域名Destination-Realm设置为所述源节点的源域名Origin-Realm；
    第二处理单元，设置为将所述业务响应消息中携带的目的主机名Destination-Host设置为所述源节点的源主机名Origin-Host。
  19. 根据权利要求17所述的装置，其中，所述业务请求消息的第二标识信息为在Diameter消息头中新增的命令标记。
  20. 根据权利要求17所述的装置，其中，所述业务响应消息在通过所述第二组节点进行路由转发过程中，所述第二组节点中的每一个节点对所述业务响应消息中的所述第一信息标识进行路由分析，并根据路由结果将所述业务响应消息转发至相邻的下一个DRA节点或者是所述源节点，且无需进行事务处理和/或会话处理。
  21. 一种响应消息的获取和响应消息的路由系统，包括：业务源节点、业务目的节点，从所述业务源节点向所述业务目的节点发送业务请求消息所经过的第一组路由代理DRA节点以及从所述业务目的节点向所述业务源节点发送业务响应消息所经过的第二组DRA节点。
PCT/CN2015/072006 2014-09-30 2015-01-30 响应消息的获取、响应消息的路由方法、装置及系统 WO2015184840A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US15/512,002 US10129749B2 (en) 2014-09-30 2015-01-30 Method and device for acquiring response message, method and device for routing response message, and system for acquiring response message and routing response message
EP15802459.6A EP3203692B1 (en) 2014-09-30 2015-01-30 Method, apparatus and system for acquiring response message, and method, apparatus and system for routing response message

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410526406.3 2014-09-30
CN201410526406.3A CN105530183B (zh) 2014-09-30 2014-09-30 响应消息的获取、响应消息的路由方法、装置及系统

Publications (1)

Publication Number Publication Date
WO2015184840A1 true WO2015184840A1 (zh) 2015-12-10

Family

ID=54766073

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/072006 WO2015184840A1 (zh) 2014-09-30 2015-01-30 响应消息的获取、响应消息的路由方法、装置及系统

Country Status (4)

Country Link
US (1) US10129749B2 (zh)
EP (1) EP3203692B1 (zh)
CN (1) CN105530183B (zh)
WO (1) WO2015184840A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112751935A (zh) * 2020-12-31 2021-05-04 江苏云柜网络技术有限公司 请求处理方法、装置、电子设备及存储介质

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10002004B2 (en) * 2016-05-26 2018-06-19 International Business Machines Corporation Stream computing application shutdown and restart without data loss
CN112311677B (zh) * 2019-07-29 2023-04-14 中兴通讯股份有限公司 一种融合通信中实现信令路由的方法及装置
CN112954625B (zh) * 2021-03-02 2022-03-11 武汉绿色网络信息服务有限责任公司 信令传输方法、装置、设备及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101217810A (zh) * 2008-01-16 2008-07-09 中兴通讯股份有限公司 一种策略和计费规则功能的选择方法
CN101283523A (zh) * 2005-10-28 2008-10-08 香港应用科技研究院有限公司 无线网络里带宽预留的多跳路由方法
US20130279406A1 (en) * 2012-04-24 2013-10-24 Telefonaktiebolaget Lm Ericsson (Publ) Policy and charging control methods

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101442419B (zh) * 2007-11-21 2010-12-08 华为技术有限公司 确定组播代理节点的方法、组播方法、设备及系统
EP2218010B1 (en) * 2007-12-01 2019-07-03 Alcatel-Lucent USA Inc. Ims diameter router with load balancing
US8613073B2 (en) * 2009-10-16 2013-12-17 Tekelec, Inc. Methods, systems, and computer readable media for providing diameter signaling router with firewall functionality
WO2011100603A2 (en) * 2010-02-12 2011-08-18 Tekelec Methods, systems, and computer readable media for providing peer routing at a diameter node
EP2577930B1 (en) * 2010-06-06 2020-05-27 Tekelec, Inc. Methods, systems, and computer readable media for obscuring diameter node information in a communication network
US8675659B2 (en) * 2010-12-16 2014-03-18 Openet Telecom Ltd. Methods, systems and devices for multiphase decoding
US8824370B2 (en) * 2010-12-16 2014-09-02 Openet Telecom Ltd. Methods, systems and devices for dynamic context-based routing
US8923204B2 (en) * 2012-05-29 2014-12-30 Alcatel Lucent Message handling extension using context artifacts
US10027580B2 (en) * 2013-03-28 2018-07-17 Oracle International Corporation Methods, systems, and computer readable media for performing stateful diameter routing with diameter routing agents that use different mechanisms to achieve stateful routing
US11388082B2 (en) * 2013-11-27 2022-07-12 Oracle International Corporation Methods, systems, and computer readable media for diameter routing using software defined network (SDN) functionality
US9668135B2 (en) * 2015-08-14 2017-05-30 Oracle International Corporation Methods, systems, and computer readable media for providing access network signaling protocol interworking for user authentication

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101283523A (zh) * 2005-10-28 2008-10-08 香港应用科技研究院有限公司 无线网络里带宽预留的多跳路由方法
CN101217810A (zh) * 2008-01-16 2008-07-09 中兴通讯股份有限公司 一种策略和计费规则功能的选择方法
US20130279406A1 (en) * 2012-04-24 2013-10-24 Telefonaktiebolaget Lm Ericsson (Publ) Policy and charging control methods

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112751935A (zh) * 2020-12-31 2021-05-04 江苏云柜网络技术有限公司 请求处理方法、装置、电子设备及存储介质
CN112751935B (zh) * 2020-12-31 2022-08-12 南京云柜网络科技有限公司 请求处理方法、装置、电子设备及存储介质

Also Published As

Publication number Publication date
US10129749B2 (en) 2018-11-13
CN105530183B (zh) 2019-11-05
EP3203692A4 (en) 2017-11-01
CN105530183A (zh) 2016-04-27
EP3203692A1 (en) 2017-08-09
US20170303124A1 (en) 2017-10-19
EP3203692B1 (en) 2021-03-17

Similar Documents

Publication Publication Date Title
CN113475045B (zh) 基于控制面的时间敏感网络配置
EP3759870B1 (en) Network slicing with smart contracts
EP4404627A1 (en) Smf, amf and upf relocation during ue registration
US8218490B2 (en) GGSN proxy for one tunnel solution
CN102754409B (zh) 用于直径协议协调的方法、系统和计算机可读介质
CN108141743B (zh) 处置通信交换的方法、网络、装备、系统、介质和装置
US8862869B1 (en) Method and apparatus for providing network initiated session encryption
CN113454948A (zh) 增强up功能请求的pfcp关联释放
WO2015184840A1 (zh) 响应消息的获取、响应消息的路由方法、装置及系统
CN107404715B (zh) 位置信息提供方法及装置
US20130242918A1 (en) Method for providing a local traffic shortcut in a packet-oriented mobile communication network
US11849351B2 (en) Removal of application identifier
Tschofenig et al. Diameter: New Generation AAA Protocol-Design, Practice, and Applications
US9237595B2 (en) Diameter based communication session discovery and recovery
EP2852242B1 (en) Session establishment method and device
CN102378399A (zh) 用户设备接入方法、装置及系统
JP2021141374A (ja) 移動通信ネットワークにおけるプレーン間の死活監視方法、ｐｇｗ−ｃ及びプログラム
EP3269096B1 (en) Topology discovery for an application layer messaging protocol with hop-by-hop routing
CN103369626A (zh) 一种融合网络中的策略控制方法及系统
WO2024195282A1 (ja) コアネットワークノード、データ生成方法、プログラム及び通信システム
CN117880781A (zh) 针对5g无线有线融合中客户场所设备的本地疏导
KR20150001515A (ko) 다이어미터 프로토콜 기반의 라우팅 처리 방법 및 다이어미터 메시지 처리 방법

Legal Events

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

Ref document number: 15802459

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 15512002

Country of ref document: US

REEP Request for entry into the european phase

Ref document number: 2015802459

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2015802459

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE