JP5445237B2 - Protocol proxy processing apparatus and method - Google Patents

Description

  The present invention relates to a protocol proxy processing apparatus and method. The present invention is a communication system that performs call control and the like constituting an IMS (IP Multimedia Subsystem), and can be applied to protocol processing and the like in a communication system that uses the Diameter protocol.

  The Diameter protocol is an authentication, authorization, and accounting (AAA) protocol that succeeds the RADIUS protocol, and is not a UDP (User Datagram Protocol) used in RADIUS, but a reliable transport protocol. A transmission control protocol (TCP) or a stream control transmission protocol (SCTP) is used.

  FIG. 12 shows a configuration example of IMS (IP Multimedia Subsystem). In FIG. 12, a call session control device (CSCF: Call Session Control Function) 11 receives subscriber information from a subscriber location information server (SLF: Subscription Locator Function) 12 and holds subscriber information such as called subscribers. Information of a server (HSS: Home Subscriber Server) 13 is acquired.

  The call session control device (CSCF) 11 acquires subscriber information such as a called subscriber from the home subscriber information server (HSS) 13 and performs call session control based on the subscriber information. The call session control device (CSCF) 11 provides various services in cooperation with an application server (AS) 14.

  Between the call session control device (CSCF) 11 and the subscriber location information server (SLF) 12 and between the call session control device (CSCF) 11 and the home subscriber information server (HSS) 13, Diameter / SCTP A protocol or the like is used. Further, between the call session control device (CSCF) 11 and the application server (AS) 14 and between the call session control device (CSCF) 11 and a node 15 of another IP network, SIP (Session Initiation Protocol) is used. A protocol or the like is used.

  In order to handle Diameter / SCTP (the Diameter protocol on the SCTP protocol), at least the first (Secondary) and the second (Secondary) physically in the interface with the opposite device in the standard of the stream control transmission protocol (SCTP). Different network interface cards (NICs) will be provided.

  Therefore, in the conventional call session control device (CSCF), a first (Primary) and a second (Secondary) are provided for each opposing device such as the opposing subscriber location information server (SLF) and the home subscriber information server (HSS). A physically different network interface card (NIC) was provided.

  Further, when each network interface card (NIC) is physically redundantly configured by a bond or the like, the number of network interface cards (NIC) provided for connection with one opposing device is four. For this reason, when the Diameter / SCTP protocol is applied between opposing devices belonging to a plurality of different segments, the number of network interface cards (NIC) increases, exceeding the limit of the number that can be physically mounted. There was a problem that it was difficult to apply the SCTP protocol.

  According to the Diameter protocol standard, a configuration that supports only the transmission control protocol (TCP) as a transport protocol is allowed. However, when the Diameter / SCTP protocol is applied to an apparatus having such a configuration, there is a problem that remodeling becomes large, the burden of mounting change is large, and it cannot be easily applied.

  Further, when the operating system (OS) is Linux, the operating system (OS) is also 32 bits due to limitations of the stream control transmission protocol (SCTP), and the maximum memory space available for application software is 3 GB.

  This is because when the application software is 32 bits, the OS also operates with 32 bits in SCTP, and in Linux, the OS cannot be operated with 64 bits in the 32-bit compatible mode of EMT64T (Extended Memory 64 Technology). It is. Note that TCP can operate even when the OS is 64 bits.

  The stream control transmission protocol (SCTP) and the transmission control protocol (TCP) are described in Patent Document 1, for example. Patent Document 1 describes a technique for achieving seamless handoff between a mobile station connected by SCTP multihoming and a station connected by TCP. Further, as a session relay technique, a technique in which a session identification unit determines a session to which an arrived packet belongs, and a session relay unit relays a session of a transmission terminal and a session of a reception terminal is described in Patent Document 2 and the like Yes.

JP 2005-535230 gazette International Publication No. 2005/020523

  The present invention is a node device that does not support the Diameter / SCTP protocol, and that transmits / receives a Diameter message using a Diameter / SCTP protocol to a node device such as a call session control device (CSCF) that supports the Diameter / TCP protocol. The purpose of this is to enable communication of Diameter telegrams.

  A protocol proxy processing device that solves the above-described problem is a protocol proxy processing device that relays a Diameter message transmitted and received between opposing first and second node devices, and includes session identification information and a transmission source of the Diameter message Is stored in the transaction management table in association with the first node device identification information, and is transmitted from the second node device and refers to the transaction message for the Diameter message in the same session as the Diameter message, Transaction control means for transferring the Diameter message to the first node device associated with the session identification information, a transmission control protocol (TCP) used for transferring the Diameter message, and a stream control transmitter And transport protocol conversion means for converting between Deployment Protocol (SCTP), those having a.

  A node device such as a call session control device (CSCF) that supports the Diameter / TCP protocol, but does not support the Diameter / SCTP protocol, via the disclosed protocol proxy processing device, is supported by the Diameter / SCTP protocol. It is possible to communicate a Diameter message with a node device that transmits and receives a Diameter message using a protocol, and it is possible to solve the above-described various problems of the related art.

It is a figure which shows the system example to which the protocol proxy processing apparatus is applied. It is a figure which shows the sequence of Diameter / SCTP connection establishment. It is a figure which shows the sequence of Diameter / TCP connection establishment. It is a figure which shows an example of an original header. It is a figure which shows the example of the transmission origin and destination information of an original header and a Diameter message | telegram. It is a figure which shows an example of the command of a Diameter protocol. It is a figure which shows the sequence example (HSS normal) of the transaction control of a Diameter request / response. It is a figure which shows the sequence example (HSS no response) of the transaction control of a Diameter request / response. It is a figure which shows the example of a sequence of the transaction control of a PPR message | telegram. It is a figure which shows the example of a sequence of the transaction control of a PPR message | telegram. It is a figure which shows the example of a sequence of the response process of a PPA message. It is a figure which shows the structural example of IMS (IP Multimedia Subsystem).

  FIG. 1 shows an example of a system to which the disclosed proxy proxy processing apparatus is applied. In this system example, a protocol proxy processing device (Diameter) is connected between a call session control device (CSCF) 11, a subscriber location information server (SLF) 12, and a home subscriber information server (HSS) 13 in an IMS (IP Multimedia Subsystem). -Proxy) 20 is deployed.

  Here, the call session control device (CSCF) 11 is a node device that supports only the Diameter / TCP protocol. The protocol proxy processing device (Diameter-Proxy) 20 performs transport protocol conversion and transaction control for converting the Diameter signal of the call session control device (CSCF) 11 into a Diameter / SCTP protocol.

  The protocol proxy processing device (Diameter-Proxy) 20 includes the following means. In the following description, the node device of the call session control device (CSCF) may be abbreviated as CSCF, the node device of the subscriber location information server (SLF) as SLF, and the node device of the home subscriber information server (HSS) as HSS. is there.

(1) Diameter / SCTP connection control Based on the SLF / HSS station data managed by the maintenance function, the stream control transmission protocol (SCTP) connection to the opposite SLF / HSS by two multi-homing each. Establish. Note that, in the SCTP connection, the protocol proxy processing device (Diameter-Proxy) side is an SCTP client, and SLF / HSS is an SCTP server. The trigger for establishing the connection is when each restart processing of the protocol proxy processing device (Diameter-Proxy) is detected. When an SCTP connection is established, timer monitoring is performed until the connection is completed. If the connection is not completed by the timer monitoring time, a retry process is performed.

(2) Diameter / TCP connection control A TCP socket for Diameter / TCP connection connected to the call session control device (CSCF) is prepared in the protocol proxy processing device (Diameter-Proxy). The protocol proxy processing device (Diameter-Proxy) operates as a TCP connection server, and does not establish a connection from the protocol proxy processing device (Diameter-Proxy).

  However, when a plurality of TCP connections are connected from the same call session control device (CSCF), the last connected TCP connection is treated as an effective connection, and the same call session control device ( Disconnect the TCP connection with the CSCF).

(3) Diameter transport protocol conversion Transport protocol conversion is performed in the transmission and reception of Diameter messages between the opposing call session control device (CSCF) and the SLF and HSS. The call session control device (CSCF) side is Diameter / TCP, and the SLF and HSS sides are Diameter / SCTP.

(4) Transaction control In response to the message of the Diameter request (UAR / SAR / LIR) received from the call session control device (CSCF), the transaction information (session identification information) of Diameter and the source call session control device (CSCF) Identification information is held in an internal transaction management table. Then, after converting the transport protocol of Diameter from TCP to SCTP, those messages are transferred to SLF or HSS.

  In addition, the transaction management table is searched using the Diameter transaction information (session identification information) added to the message of the Diameter response (UAA / SAA / LIA) received from the SLF or HSS as a search key. Then, a call session control device (CSCF) associated with the transaction information (session identification information) is obtained, and routing is performed as the call session control device (CSCF) to which the message is returned.

  In order to reduce the load on Diameter message analysis / reconstruction processing in the protocol proxy processing device (Diameter-Proxy), the call session control device (CSCF) and the protocol proxy processing device (Diameter-Proxy) normally A new unique header is added to the Diameter message and sent and received.

  By performing analysis / routing processing based on the information of the unique header, these processing can be performed at high speed. The unique header may include version information, message length, command type, session identification information (Session-ID), source host IP address, destination host IP address, and response code information.

(5) PPR control When a PPR (Push-Profile-Request) message, which is a push-type Diameter signal transmitted from the HSS, is received, the PPR message is distributed to all opposing call session control devices (CSCFs). (Fork) and transmit. Thereafter, when a PPA (Push-Profile-Answer) message as a response is received from each call session control device (CSCF) of the destination of the PPR message, the PPA message including the corresponding profile is selected, and the PPA message A message is transmitted to the HSS. At this time, transport protocol conversion is performed between SCTP between the HSS and the protocol proxy processing device (Diameter-Proxy) and TCP between the call session control device (CSCF) and the protocol proxy processing device (Diameter-Proxy). .

  When a PPA message that does not include the corresponding profile is received from all the call session control devices (CSCFs), a PPA message indicating “no corresponding profile” is returned to the HSS. In addition, when a reception waiting timer expires without receiving a PPA message including the corresponding profile from some or all call session control devices (CSCFs), no PPA message is returned to the HSS. Act as a response.

(6) Replacing hop-by-hop identification information / end-to-end identification information For the Diameter request transmitted to the SLF / HSS, the protocol proxy processing device (Diameter-Proxy) uses the hop-by-hop identification information (Hop- by-Hop Identifier) header or end-to-end identifier (End-to-End Identifier) header replacement processing.

(Diameter / SCTP connection established)
The sequence for establishing a Diameter / SCTP connection is shown in FIG. The SCTP connection is started from the client-side protocol proxy processing device (Diameter-Proxy) to the server-side SLF / HSS. As shown in FIG. 2, the Diameter / SCTP connection is first established between the protocol proxy processing device (Diameter-Proxy) and the SLF / HSS, and then a Diameter session is established.

(Diameter / TCP connection established)
A sequence for establishing a Diameter / TCP connection is shown in FIG. In the TCP connection, the call session control device (CSCF) is a TCP client, and the protocol proxy processing device (Diameter-Proxy) is a TCP server. As shown in FIG. 3, a Diameter / TCP connection is first established between a call session control device (CSCF) and a protocol proxy processing device (Diameter-Proxy), and then a Diameter session is established. Is done.

(Transport protocol conversion)
Transport conversion of Diameter signals transmitted and received between the opposing call session control device (CSCF) and SLF / HSS is performed. The call session control device (CSCF) side is a Diameter / TCP protocol, and the SLF / HSS side is a Diameter / SCTP protocol.

  In addition, for the message of the Diameter request (UAR / SAR / LIR) from the call session control device (CSCF) side, the analysis / reconstruction processing of the message is skipped, and it is given separately from the normal Diameter message Analysis and routing processing is performed using the header information. By doing so, the processing speed can be increased. This unique header can be configured to be provided by a Diameter library on the call session control device (CSCF) side.

  FIG. 4 shows an example of the unique header. 4A shows an example of a frame structure in which a unique header is added to a Diameter message and is encapsulated. FIG. 4B shows an example of the structure of the unique header. FIG. 4C shows each of the unique headers. The detailed contents of the constituent elements are shown.

  As shown in FIG. 4B, the configuration of the unique header is as follows: Local-ID, Message-Length, Command-flags, Command-Code, Session-ID-length, Session-ID, Origin-Host, Destination-Host, and Return. -It can be set as the structure containing Code.

  As shown in FIG. 4C, each component of the unique header represents the version of the Local-ID at the head of the header. In this case, for example, 255 is identified to identify the unique header. It will be set. The length of the entire message is set in Message-Length. A value obtained by adding the length of the unique header to the length of the Diameter message is set.

  In Command-flags, a bit string representing the type of command is set. That is, the same value as Command-flags of the Diameter message is set. In the Command-Code, a code representing processing defined by IANA (Internet Assigned Number Authority) is set. That is, the same value as the Command-Code of the Diameter message is set.

  In Session-ID-Length, the length of the session identification information is set. Set 0 if invalid. Session identification information is set in Session-ID. That is, the same value as the value of Session-ID of the Diameter message is set. In Origin-Host, the IP address of the transmission source host is set. In Destination-Host, the IP address of the destination host is set.

  In the Return-Code, the value of Result-Code or Experimental-Result-Code is set together with the flag F in the case of a command response. Here, when the flag F is set to 0, the value of Result-Code is set. When the flag F is set to 1, the value of Experimental-Result-Code is set. In the case of invalidity, 0 is set for both the flag F and the Return-Code. FIG. 5 shows an example of the source / destination information of the unique header and Diameter message. FIG. 6 shows an example of a Diameter protocol command.

(Transaction control)
In response to a Diameter request (UAR / SAR / LIR) from the call session control device (CSCF), the transaction information (session identification information) and the logical number of the source call session control device (CSCF) are held in the transaction management table. . The SLF / HSS of the transmission destination of the Diameter request is obtained from Destination-Host of the unique header.

  When a Diameter response (UAA / SAA / LIA) is received from the HSS, the transaction management table is searched using the session identification information of the Diameter response as a search key, and the logical number of the call session control device (CSCF) as the return destination is obtained. . Then, the Diameter response is transmitted to the call session control device (CSCF) of the system (ACT system) in which the TCP connection is valid.

  The session identification information and the source call session control device (CSCF) information are extracted from the unique header of the Diameter request from the call session control device (CSCF). The logical number of the call session control device (CSCF) is obtained by searching station data from the IP address of the device. When the content of the unique header is abnormal, the Diameter request received from the call session control device (CSCF) is discarded.

  When a Diameter request is transmitted from the protocol proxy processing device (Diameter-Proxy) to the SLF / HSS, a response waiting timer is set when the request is transmitted, and the response is monitored. When the response waiting timer expires, it does not retransmit to the HSS and does not return a response to the call session control device (CSCF), and behaves as no response.

  In addition, the transaction information (session identification information) on the transaction management table and the call session control device (CSCF) information are deleted when the Diameter response is transmitted to the call session control device (CSCF) or the response waiting timer expires. .

  FIG. 7 shows a sequence example of transaction control of Diameter request / response (HSS normal). The call session control device (CSCF) transmits the Diameter request message xxR (Cx / Dx) with the unique header to the protocol proxy processing device (Diameter-Proxy) using the TCP transport protocol (7-1). ). Cx is a telegram of the interface with the HSS, and Dx is a telegram of the interface with the SLF.

  The protocol proxy processing device (Diameter-Proxy) holds the session identification information (Session-ID) of the unique header and the information of the source CSCF (information converted from the IP address to the logical number) in the transaction management table (7 -2). Then, the protocol proxy processing device (Diameter-Proxy) converts the Diameter request message xxR into an SCTP transport protocol and transmits it to the SLF or HSS (7-3). At this time, the protocol proxy processing device (Diameter-Proxy) sets a response wait timer when a Diameter request message is transmitted to the HSS, and performs response monitoring.

  Upon receiving the Diameter request message xxR, the SLF or HSS transmits a Diameter response message xxA as a response to the protocol proxy processing device (Diameter-Proxy) using the SCTP transport protocol (7-4). The protocol proxy processing device (Diameter-Proxy) analyzes the Diameter message xxA, searches the transaction management table using the session identification information (Session-ID) as a search key, and selects the destination call session control device (CSCF). Calculate (7-5).

  Then, the protocol proxy processing device (Diameter-Proxy) converts the Diameter response message xxA into a TCP transport protocol and transmits it to the call session control device (CSCF) (7-6). The protocol proxy processing device (Diameter-Proxy) deletes the transaction information related to the transaction from the transaction management table when a response is returned to the call session control device (CSCF) (7-7). This is because the transaction information is accumulated in the transaction management table, and the transaction management table is prevented from overflowing with a lot of invalid transaction information.

  FIG. 8 shows a sequence example of transaction control of Diameter request / response (HSS no response). The call session control device (CSCF) transmits the Diameter request message xxR (Cx / Dx) with the unique header to the protocol proxy processing device (Diameter-Proxy) using the TCP transport protocol (8-1). ).

  The protocol proxy processing device (Diameter-Proxy) holds the session identification information (Session-ID) of the unique header and the information of the source CSCF (information converted from the IP address to the logical number) in the transaction management table (8 -2). Then, the protocol proxy processing device (Diameter-Proxy) converts the Diameter request message xxR into an SCTP transport protocol and transmits it to the SLF or HSS (8-3). At this time, the protocol proxy processing device (Diameter-Proxy) sets a response wait timer when a Diameter request message is transmitted to the HSS, and performs response monitoring.

  Thereafter, the protocol proxy processing device (Diameter-Proxy) waits for a response from the SLF or HSS, but detects no response from the SLF or HSS when the response wait timer has expired (8-4). . The protocol proxy processing device (Diameter-Proxy) deletes the transaction information related to the transaction from the transaction management table upon detection of no response from the SLF or HSS (8-5). This is because the transaction information is accumulated in the transaction management table, and the transaction management table is prevented from overflowing with a lot of invalid transaction information.

  Next, transaction control of a push-type-diagram signal PPR (Push-Profile-Request) message in which a request message is issued from the SLF / HSS side to the call session control device (CSCF) side will be described.

(Fork processing (normal sequence))
The protocol proxy processing device (Diameter-Proxy) receives a PPR (Push-Profile-Request) message based on the SCTP transport protocol from the opposite HSS. In this case, since the call session control device (CSCF) to which the PPR message is transmitted is undefined, the PPR message is transmitted to all the call session control devices (CSCF) registered as station data in the TCP transport protocol. The data is converted and distributed (Fork).

  When the PPR message is distributed and transmitted to each call session control device (CSCF), a PPA message reception waiting timer is set as a response to monitor the reception of the PPA message. At the same time, the session identification information of the PPR message and the logical number of the source HSS are registered in the internal transaction management table (PPR transaction management table).

  If a PPA message (that is, a message with user registration) of the same session identification information in which “DIAMETER_ERROR_USER_UNKNOWN” is not set in the Experimental-Result of the original header of the Diameter is received before the PPA message reception waiting timer expires, The PPA message is converted to the SCTP transport protocol and transmitted to the source HSS.

  Data related to the transaction on the PPR transaction management table is deleted when the PPA reception waiting timer expires. In addition, before transmitting the PPA message to the HSS, “DIAMETER_ERROR_USER_UNKNOWN” (that is, a message without user registration) is received in the Experimental-Result in the PPA message of the same session identification information received from another call session control device (CSCF). If a PPA message with the same session identification information is received from another call session control device (CSCF) after transmitting the PPA message to the HSS, the PPA message is also discarded.

  9 and 10 show a sequence example of transaction control of a PPR message. The HSS transmits the PPR message of the Diameter request to the protocol proxy processing device (Diameter-Proxy) using the SCTP transport protocol (9-1). The protocol proxy processing device (Diameter-Proxy) distributes (Forks) the PPR message to each of the call session control devices (CSCF) # 1, # 2, #n. In addition, the session identification information (Session-ID) and the logical number of the source HSS are held in the PPR transaction management table (9-2).

  The protocol proxy processing device (Diameter-Proxy) sets a PPA message response waiting timer. Here, it is assumed that a PPA message (that is, a message without user registration (REG)) in which “DIAMETER_ERROR_USER_UNKNOWN” is set in the Experimental-Result of the original header of the Diameter is received from the call session control device (CSCF) # 1 (9 -3).

  The protocol proxy processing device (Diameter-Proxy) determines whether the received PPA message is the same PPA message as the session identification information (Session-ID) of the PPR message that has been distributed and transmitted (Fork), and then USER_UNKNOWN (user Recognize that it is a PPA message without registration (REG), and discard the PPA message (9-4) There is no PPA message that matches the session identification information (Session-ID) of the PPR message that has been distributed and transmitted (Fork) In this case, the PPA message is discarded.

  Thereafter, as shown in FIG. 10, it is assumed that a PPA message in which “DIAMETER_SUCCESS” is set in the Result-Code of the Diameter unique header is received from the call session control device (CSCF) # 2 (10-1). The PPA message is a message indicating that “DIAMETER_ERROR_USER_UNKNOWN” is not set in the Experimental-Result, that is, there is user registration (REG).

  The protocol proxy processing device (Diameter-Proxy) determines whether the received PPA message is the same PPA message as the session identification information (Session-ID) of the PPR message that has been distributed and transmitted (Fork), and then “USER_UNKNOWN” is Recognizing that the PPA message is not set (that is, with user registration (REG)), the PPA message is transferred to the HSS (10-2).

  Thereafter, it is assumed that a PPA message (that is, a message without user registration (REG)) in which “DIAMETER_ERROR_USER_UNKNOWN” is set in the Experimental-Result of the original header of the Diameter is received from the call session control device (CSCF) #n (10− 3).

  The protocol proxy processing device (Diameter-Proxy) determines whether the received PPA message is the same PPA message as the session identification information (Session-ID) of the PPR message that has been distributed and transmitted (Fork). Since it is a PPA message of session identification information (Session-ID), the PPA message is discarded (10-4). The protocol proxy processing device (Diameter-Proxy) deletes the transaction information on the PPA transaction management table when the PPA message reception waiting timer expires (10-5).

(Fork processing (quasi-normal sequence))
If the PPA message indicating the presence of user registration (REG) is not returned from any call session control device (CSCF) before the PPA message reception waiting timer expires, the protocol proxy processing device (Diameter-Proxy) Perform the process.

(A) When PPA telegrams are received from all call session control devices (CSCF) before the PPA telegram reception waiting timer expires (a1) All received PPA telegrams have no user registration (REG) (Experimental-Result -Code: DIAMETER_ERROR_USER_UNKNOWN) is set, a PPA message indicating that there is no user registration (REG) is transmitted to the HSS.

  (A2) If there is a PPA message (PPA message such as Diameter syntax error) in which information other than no user registration (REG) is set in a part of the received PPA message, the protocol is the first in the PPA message The PPA telegram received by the proxy processing device (Diameter-Proxy) is transmitted to the HSS.

  In the case of (a2) above, the call session control device (CSCF) that returns the PPA telegram in which the information with user registration (REG) is set returns the PPA telegram that includes error information other than with no user registration (REG) Judge that it is. When a plurality of PPA messages containing error information other than no user registration (REG) is returned, the protocol proxy processing device (Diameter-Proxy) determines which error information PPA message is to be transferred with priority. I can't. Therefore, the protocol proxy processing device (Diameter-Proxy) transmits a PPA message including error information other than the first received user registration (REG) to the HSS.

(B) When the PPA telegram has not been received from all the call session control devices (CSCF) before the reception wait timer expires When the reception wait timer expires, no PPA telegram has been received from all the call session control devices (CSCF) Or, if a PPA message is received from some call session control devices (CSCF), but a PPA message with user registration (REG) is not received, regardless of the contents of some received PPA messages , No response to HSS. This is because the call session control device (CSCF) that should return a PPA message with user registration (REG) may not respond.

  FIG. 11 shows a sequence example of PPA message response processing in the protocol proxy processing device (Diameter-Proxy). When the protocol proxy processing device (Diameter-Proxy) receives the PPA message (11-1), it determines whether the PPA message reception waiting timer has expired (11-2). If the reception waiting timer has not expired, it is determined whether or not the received PPA message is a PPA message with user registration (REG) (11-3).

  If it is a PPA message with user registration (REG), the PPA message with user registration (REG) is transferred to the HSS (11-5). This flow is the fork processing in the case of the normal sequence described above. If the PPA message is not a PPA message with user registration (REG), it is determined whether or not the PPA message is the last PPA message of the same session identification information (11-6).

  If it is the last PPA message, it means that the PPA message has been received from all the call session control devices (CSCF), and the PPA message of the same session identification information including error information other than no user registration (REG) has been received. It is determined whether or not (11-7). If a PPA message with the same session identification information including error information other than no user registration (REG) is received, the first received PPA message including error information other than no user registration (REG) is transferred to the HSS. (11-8). This process flow corresponds to the process (a2) of the fork process of the quasi-normal sequence described above.

  When a PPA message including information without user registration (REG) is received, the PPA message including information without user registration (REG) is transferred to the HSS (11-9). This process flow corresponds to the process (a1) of the fork process of the semi-normal sequence described above.

  The above processing is executed until the reception waiting timer of the PPA message expires. When the reception waiting timer expires, no response is made to the HSS regardless of the contents of some of the received PPA messages (11 -10). This process flow corresponds to the process (b) of the fork process of the quasi-normal sequence described above.

(Replacement of hop-by-hop identification information / end-to-end identification information)
For a Diameter request to be transmitted to the SLF / HSS, a hop-by-hop identifier header or an end-to-end identifier header of the Diameter message is sent to the protocol proxy processing device (Diameter). -Proxy), change as follows.

(Hop-by-hop identification information)
For all Diameter requests sent to the SLF / HSS, the protocol proxy processing device (Diameter-Proxy) uses a 32-bit random number calculated at restart for each SLF / HSS as an initial value, and sends 1 each time a Diameter request is sent. The incremented value is set in the hop-by-hop identifier.

  When the SLF / HSS is added, the initial value is set with a random number when the SLF / HSS is added. Note that the value of this hop-by-hop identifier is managed for each SLF / HSS.

  For Diameter requests (UAR / SAR / LIA) received from the call session control device (CSCF) and transmitted to the SLF / HSS, before changing the hop-by-hop identifier (Hop-by-Hop Identifier), The value of hop-by-hop identification information (Hop-by-Hop Identifier) set by the call session control device (CSCF) is stored in the memory. When a response corresponding to the request is returned, the value of hop-by-hop identification information (Hop-by-Hop Identifier) stored in the memory is set on the response. When the value of Hop-by-Hop Identifier reaches the value of 0xFFFFFFFF, the value of 0x0 is set in the next increment.

(End-to-end identification information)
For all Diameter requests sent to the SLF / HSS, the lower 12 bits of the current time, for example, are set in the upper 12 bits of the end-to-end identifier header (End-to-End Identifier) header, and a random value (by random number) Generation) is set to the lower 20 bits, for example.

  For Diameter requests (UAR / SAR / LIA) received from the call session control device (CSCF) and transmitted to the SLF / HSS, the end-to-end identifier is not changed. The value of end-to-end identification information (End-to-End Identifier) set by the call session control device (CSCF) is stored in the memory. Then, when returning a response corresponding to the request, the value of end-to-end identification information (End-to-End Identifier) stored in the memory is set on the response.

  In this way, the same session identification information (Session-ID) is given by changing hop-by-hop identification information (Hop-by-Hop Identifier) or end-to-end identification information (End-to-End Identifier). Thus, even when a collision of session identification information occurs, it is possible to strictly distinguish the sessions using these pieces of information.

  As described above, the call session control device (CSCF) has been described as an example of a node device that does not support the Diameter / SCTP protocol and supports the Diameter / TCP protocol. However, the present invention is not limited to this, and the application The same can be applied to a server (AS) or the like.

11 Call session controller (CSCF)
12 Subscriber Location Information Server (SLF)
13 Home Subscriber Information Server (HSS)
14 Application Server (AS)
15 Other IP network nodes

Claims (6)

A protocol proxy processing device that relays a Diameter message sent and received between first and second node devices facing each other,
The session identification information of the Diameter message and the first node device identification information of the transmission source are associated with each other and stored in the transaction management table, transmitted from the second node device, and for the Diameter message of the same session as the Diameter message Transaction control means for referring to the transaction management table and transferring the Diameter message to the first node device associated with the session identification information;
Transport protocol conversion means for converting between a transmission control protocol (TCP) and a stream control transmission protocol (SCTP) used in the transfer of the Diameter message;
A protocol proxy processing apparatus comprising: A protocol proxy processing device that relays a Diameter message sent and received between a call session control device (CSCF) and a counter node device facing the call session control device (CSCF),
Session identification information of the Diameter message and the call session control device (CSCF) identification information of the transmission source are associated with each other and held in a transaction management table, transmitted from the opposite node device, and the Diameter message of the same session as the Diameter message On the other hand, referring to the transaction management table, transaction control means for transferring the Diameter message to the call session control device (CSCF) associated with the session identification information;
Transport protocol conversion means for converting between a transmission control protocol (TCP) and a stream control transmission protocol (SCTP) used in the transfer of the Diameter message;
A protocol proxy processing apparatus comprising:   The hop-by-hop identification information or end-to-end identification information of the Diameter message is transferred to the second node device with different values sequentially transferred for each session, and the hop-by-hop identification information together with the session identification information. 3. The protocol proxy processing apparatus according to claim 1, further comprising means for identifying a session of the Diameter message using end-to-end identification information.   Receives a Diameter message to which a unique header including session identification information, an IP address of the transmission source host, an IP address of the destination host, and a response code is added, and analyzes the Diameter message with reference to the unique header 4. The protocol proxy processing device according to claim 1, further comprising means.   When the Diameter PPR message is received from the home subscriber information server, the PPR message is distributed and transmitted to all the call session control devices (CSCFs) that do not support the stream control transmission protocol (SCTP). 3. The protocol proxy processing device according to claim 2, further comprising means for returning a PPA message including the corresponding profile information to a home subscriber information server that is a transmission source of the PPR message. A protocol proxy processing method for relaying a Diameter message sent and received between opposing first and second node devices,
The session identification information of the Diameter message and the first node device identification information of the transmission source are associated with each other and stored in the transaction management table, transmitted from the second node device, and for the Diameter message of the same session as the Diameter message Referring to the transaction management table and forwarding the Diameter message to the first node device associated with the session identification information;
Converting between transmission control protocol (TCP) and stream control transmission protocol (SCTP) used in the transfer of the Diameter message;
A protocol proxy processing method comprising:

Images