KR20170096531A - System and method for TAS restoration based home subscribe server - Google Patents

System and method for TAS restoration based home subscribe server Download PDF

Info

Publication number
KR20170096531A
KR20170096531A KR1020160018034A KR20160018034A KR20170096531A KR 20170096531 A KR20170096531 A KR 20170096531A KR 1020160018034 A KR1020160018034 A KR 1020160018034A KR 20160018034 A KR20160018034 A KR 20160018034A KR 20170096531 A KR20170096531 A KR 20170096531A
Authority
KR
South Korea
Prior art keywords
information
call processing
tas
header
message
Prior art date
Application number
KR1020160018034A
Other languages
Korean (ko)
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 KR1020160018034A priority Critical patent/KR20170096531A/en
Publication of KR20170096531A publication Critical patent/KR20170096531A/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/30—Network data restoration; Network data reliability; Network data fault tolerance
    • H04L65/1006—
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1016—IP multimedia subsystem [IMS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition
    • 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/04—Registration at HLR or HSS [Home Subscriber Server]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/08—Upper layer protocols
    • H04W80/10—Upper layer protocols adapted for application session management, e.g. SIP [Session Initiation Protocol]

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Multimedia (AREA)
  • Telephonic Communication Services (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

In order to recover the failure, the TAS receives an INVITE message for call processing of the terminal from the serving call session control server, and determines whether the telephone number included in the invite message exists in the call processing information . If the telephone number does not exist in the call processing information, it is determined that a failure has occurred, and the lost call processing information is recovered using the backup information received from the home subscriber server and the invite message.

Description

[0001] The present invention relates to a TAS failure recovery system and a TAS failure recovery method using the same,

The present invention relates to a TAS fault recovery system and a TAS fault recovery method using the same.

Telephony Application Server (TAS) is an application server for providing call service in Voice over LTE (VoLTE). The terminal is based on information about the network when registering the network and subscriber information in the network, Initiation Protocol). That is, the TAS parses the SIP registration message and stores necessary information. In the SIP registration message transmitted to the TAS by the Serving-Call Session Control Server (S-CSCF) And stores it as call processing information. Then, in the network registration procedure, the UDR / UDA operation (User Data Request / User Data Answer) is received from the home subscriber server (HSS) to obtain the subscriber's registration information registered in the network.

The opening information from the home subscriber server includes various information for providing the VoLTE communication service such as the type of the additional service to which the subscriber subscribes, the QoS, and the function of the terminal. The details of this information may vary depending on the provider policy and the service provided Do. At this time, integrity of information stored in TAS may be broken or information may be lost due to abnormality of TAS. In such a case, there arises a problem such as interruption of the call service provided to the subscriber.

Accordingly, the present invention provides a TAS failure recovery system based on a telephony application server and an HSS (Home Subscribe Server) and a TAS failure recovery method using the same.

According to an aspect of the present invention, there is provided a TAS failure recovery system,

A home subscriber server for managing subscriber opening information, receiving recovery target information from information necessary for registering in an IP Multimedia Subsystem (IMS) network of a terminal from a serving call session control server, and storing the target information for recovery as backup information; And a TAS (Telephony Application Server) for storing call processing information extracted from a register message (REGISTER Message) received from the serving call session control server and adding the subscriber opening information received from the home subscriber server to the call processing information, Wherein the TAS determines that a failure occurs if a telephone number included in the invite message does not exist in the call processing information upon receiving an INVITE message from the serving call session control server, And restores lost call processing information using the backup information and the invite message received from the home subscriber server.

The call processing information includes information included in the To header, information included in the Contact header, information included in the User Agent header, or information included in the P-Access-Network-Info header included in the register message can do.

If the invite message is an incoming byte message and it is determined that a failure has occurred, the TAS extracts the information contained in the To header from the incoming-by-byte message to recover call processing information, The information contained in the Agent header and the subscriber opening information can be received from the home subscriber server and recover the call processing information.

If the invite message is a sender byte message and it is determined that a failure has occurred, the TAS extracts information included in the To header, information included in the Contact header, and information included in the User Agent header from the sender byte message And the subscriber opening information is received from the home subscriber server as backup information to recover call processing information.

According to another aspect of the present invention, there is provided a method for restoring a fault in a TAS,

Receiving an INVITE message for processing a call from a serving call session control server; Determining whether a telephone number included in the invite message exists in call processing information; And recovering the lost call processing information using the backup information received from the home subscriber server and the invite message if the phone number is not present in the call processing information.

Receiving a register message (REGISTER Message) from the call session control server before receiving the invite message; And parsing the register message to extract and store call processing information necessary for call processing.

The call processing information includes information included in the To header, information included in the Contact header, information included in the User Agent header, or information included in the P-Access-Network-Info header included in the register message can do.

Receiving subscriber opening information from the home subscriber server prior to receiving the Invite message; And storing the received subscriber opening information in addition to the call processing information.

Prior to the step of receiving the invite message, the home subscriber server receiving recovery object information from the serving call gateway control server; And storing the subscriber opening information and the recovery object information stored in advance as backup information.

According to the present invention, even if the integrity of the information is broken or the information is lost due to an error in the telephony application server, the call service can be provided to the subscriber through the restoration of the telephony application server.

FIG. 1 is a flowchart of a procedure in which a general TAS stores information.
2 is an exemplary diagram of a fault recovery system according to an embodiment of the present invention.
3 is a structural view of a TAS according to an embodiment of the present invention.
4 is a structural diagram of a home subscriber server according to an embodiment of the present invention.
5 is a configuration diagram of a serving call session control server according to an embodiment of the present invention.
6 is a flowchart of a method for recovering a failure of a called TAS according to an embodiment of the present invention.
FIG. 7 is a flowchart of a fault recovery method of a source TAS according to an embodiment of the present invention.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings so that those skilled in the art can easily carry out the present invention. The present invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. In order to clearly illustrate the present invention, parts not related to the description are omitted, and similar parts are denoted by like reference characters throughout the specification.

Throughout the specification, when an element is referred to as "comprising ", it means that it can include other elements as well, without excluding other elements unless specifically stated otherwise.

In this specification, a terminal includes a mobile station (MS), a mobile terminal (MT), a subscriber station (SS), a portable subscriber station (PSS) An access terminal (AT), and the like, and may include all or some of functions of a mobile terminal, a subscriber station, a mobile subscriber station, a user equipment, and the like.

Hereinafter, a TAS failure recovery system according to an embodiment of the present invention and a TAS failure recovery method using the same will be described with reference to the drawings.

Before describing an embodiment of the present invention, a TAS information storage procedure in a process of registering a terminal in an IMS network will be described with reference to FIG. FIG. 1 shows only a part of the IMS network registration procedure of the terminal for convenience of explanation.

FIG. 1 is a flowchart of a procedure in which a general TAS stores information.

In general, when a terminal performs a registration procedure in an IMS (IP Multimedia Subsystem) network, the TAS takes charge of processing the SIP (Session Initiation Protocol) based on the information registered in the network and the subscriber information held in the network .

Such a TAS is shown in FIG. 1 in order to store information necessary for call processing. First, when the terminal transmits an SIP register message to a Proxy-Call Session Control Function (P-CSCF) (S10), the P-CSCF looks up the domain of the subscriber and transmits the received SIP register message to the I- Call Session Control Function) (S11).

The SIP register message includes various information such as a URI (Uniform Resource Identifier) of the terminal to be registered in the network, an IP of the terminal, a unique ID of the terminal, the type of the terminal, network information to which the terminal is connected, Call ID, and contact information. The SIP register message is already known, and a detailed description will be omitted in the embodiment of the present invention.

Upon receipt of the SIP register message, the I-CSCF registers a subscriber or requests a User Authorization Request (UAR) signal to request the designation of the S-CSCF to which the subscriber is to be registered with an HSS (Home Subscription Server) (S12). The I-CSCF receives a UAA (User Authorization Answer) indicating that the S-CSCF to which the subscriber is to be registered is designated from the HSS (S13).

The I-CSCF forwards the SIP register message to the S_CSCF (Serving-Call Session Control Function) allocated from the HSS (S14). The S-CSCF requests the subscriber's service profile from the HSS (Server Assignment Request) (SAA: Server Assignment Answer) (S15, S16), and transmits the SIP register message to the TAS (S17). Here, the TAS parses the SIP register message received in step S17 and stores information necessary for the call processing.

Then, the TAS receives UDP (User Data Request) (UDA: User Data Answer) (S18, S19) from the HSS to inquire about the subscriber's registration information registered in the network. The subscriber opening information includes various information for providing the VoLTE communication service such as the type of the additional service to which the subscriber subscribes, the QoS, and the function of the terminal.

Through such a procedure, TAS acquires and stores information necessary for processing a call from a register message in the process of registering the terminal in the network. Therefore, in order to recover the integrity of the stored information due to an error in the TAS or loss of information, the terminals that have already been registered in the network and have not been provided with the call service must perform the registration process again before obtaining the information necessary for the call processing . Accordingly, the time required for the network registration process of the terminal takes time, and the call service provided to the terminal is interrupted.

Therefore, in the embodiment of the present invention, a TAS failure recovery system and method for providing a call service without interruption to a subscriber even if the integrity of stored information is broken or information is lost due to an error in TAS, which is an important system of VoLTE call processing .

2 is an exemplary diagram of a fault recovery system according to an embodiment of the present invention.

2, a TAS (Telephony Application Server) 110 is connected to a TAS failure recovery system 100 for convenience of explanation, and a telephony application server (hereinafter referred to as a TAS (Telephony Application Server) (Hereinafter referred to as HSS for convenience of description) 120 and a serving call session control server (hereinafter referred to as S-CSCF for convenience of description) in the TAS failure recovery system 100, But the present invention is not limited thereto.

When a terminal (not shown) performs a network registration procedure, the TAS 110, which is an application server for providing a call service in VoLTE, transmits a REGISTER message transmitted by the terminal to the S-CSCF 130 . The TAS 110 parses the received register message to obtain call processing information, which is information necessary for call processing. In addition, the TAS 110 also receives subscriber opening information already stored from the HSS 120.

Here, the call processing information includes information included in the To header in the register message, information included in the Contact header, information included in the User Agent header, and information included in the P-Access-Network-Info header. The information contained in the To header is the subscriber URI information to be registered in the network, and the information included in the Contact header is information such as the IP of the terminal, ICSI, the feature tag of the terminal capabilities, and the unique ID of the terminal. The information included in the User Agent header is information such as the type and model name of the terminal, and the information included in the P-Access-network-Info header is network information connected to the terminal.

Then, the TAS 110 checks whether the telephone number of the terminal included in the INVITE message is stored in the TAS 110. If the phone number of the terminal is not stored in the TAS 110, it is determined that a failure has occurred, and the backup information is requested and received from the HSS 120.

The TAS 110 receiving the backup information from the HSS 120 performs the recovery procedure of lost call processing information. Therefore, even if a failure occurs, the TAS 110 can immediately recover the service without re-performing the registration procedure for the terminal, thereby providing a continuous call service to the subscriber.

The S-CSCF 130 extracts the information included in the Contact header and the information included in the User Agent header from the information included in the register message transmitted when the UE attempts to access the initial network, as HSS 120 ).

The HSS 120 stores and manages the subscriber opening information stored in advance and the recovery target information received from the S-CSCF 130 as backup information. Upon receipt of the backup information request from the failed TAS 110, the backup information is transferred to the TAS 110 so that the TAS 110 can be recovered.

The structure of the TAS 110, the HSS 120, and the S-CSCF 130 will be described with reference to FIGS.

FIG. 3 is a structural diagram of a TAS according to an embodiment of the present invention, and FIG. 4 is a structural diagram of a home subscriber server according to an embodiment of the present invention. And FIG. 5 is a diagram illustrating a configuration of a serving call session control server according to an embodiment of the present invention.

3, the TAS 110 includes a call processing information receiving unit 111, a call processing information storage unit 112, a call processing unit 113, and a backup backup information requesting unit 114. [ The TAS 110 includes a call processing information receiving unit 111, a call processing information storing unit 112, a call processing unit 113, and a backup information requesting unit 114 in the form of a form However, the present invention is not limited thereto.

The call processing information receiving unit 111 receives a register message via the S-CSCF 130. The call processing information receiving unit 111 parses the received register message to extract call processing information.

In the SIP message structure system, a plurality of message headers are located after a start line, and a blank line and a message body are formed after the header. In the embodiment of the present invention, among the plurality of headers, information included in the To header, the Contact header, the User Agent header, and the P-Access-Network-Info header necessary for call processing is extracted as call processing information However, the present invention is not limited thereto.

Here, examples of a plurality of headers in a register message including call processing information are as shown in Table 1 below.

REGISTER sip: wm-scscf4.octave.com SIP / 2.0
To: <sip: 01012345678@ims.mnc008.mcc450.3gppnetwork.org>
......
Call-ID: Ld7m21BZAehhTLl1bSwqz2tx
Contact: <sip: 821012345678@102.125.129.175:5060>; + g.3gpp.icsi-ref = "urn% 3Aurn-7% 3A3gpp-service.ims.icsi.mmtel"; + sip.instance = "<urn: gsma: imei: 35922806-949541-0>"
......
P-Visited-Network-ID: "ims.mnc008.mcc450.3gppnetwork.org"
P-Access-Network-Info: 3GPP-E-UTRAN-FDD; utran-cell-id-3gpp = 450080008026670e
P-User-Database: lte-testbed.ewhlr1b.ltehss.kt.com
User Agent: TTA-VoLTE / 1.0 iOS / 8.3 iPhone / 1.0 / KT

Then, the call processing information receiving unit 111 receives subscriber opening information from the HSS 120. The subscriber opening information includes the type of additional service to which the subscriber subscribes, QoS, terminal function information, etc., and details of the subscriber opening information may be variously included according to the provider policy and the providing service.

The call processing information storage unit 112 adds the subscriber opening information received from the HSS 120 to the call processing information extracted by the call processing information receiving unit 111 and stores the addition information. The call processing information storage unit 112 receives the backup information from the backup information request unit 114 when any of a plurality of pieces of information included in the call processing information is lost due to a failure in the TAS 110 Update.

The call processing unit 113 receives an INVITE message transmitted from the S-CSCF 130. The invite message is divided into an incoming byte message and a sender byte message according to whether the terminal is a called terminal or a calling terminal. Accordingly, in the embodiment of the present invention, the TAS receiving the incoming byte message is referred to as a 'called TAS 110-1', the TAS receiving the outgoing byte message is referred to as 'originating TAS 110-2' Quot;

The call processing unit 113 extracts call processing information from the information included in the received invite message. Here, if the call processing information is an incoming byte message, the called terminal number is included in the request URI of the invite message. In the case of the outgoing byte message, the call processing information is the calling terminal telephone number included in the P-Asserted-Identify-Info header.

The call processing unit 113 checks whether the information corresponding to the extracted call processing information, that is, the called terminal telephone number, is stored in the call processing information storage unit 112. Or the call processing unit 113 checks whether the telephone number of the calling terminal is stored in the call processing information storage unit 112. [

If the extracted calling terminal phone number or called terminal phone number is stored in the call processing information storage unit 112, the call processing procedure is performed by transmitting the call / outgoing call processing signal through the interworking with the S-CSCF 130 . However, if it is confirmed that the extracted calling terminal phone number or calling terminal phone number is not stored in the call processing information storage unit 112, it is determined that the TAS 110 has failed and the call processing information is lost.

That is, when the call processing unit 113 included in the receiving TAS 110-1 determines that a failure has occurred in the receiving TAS 110-1, the call processing unit 113 adds the received To inbox message to the To header Obtain the included information. The information for the remaining call processing that has not been acquired in the incoming byte message requests the backup information requesting unit 114 to acquire the backup information. Here, the backup information for the incoming byte message includes information included in the User Agent header, information included in the Contact header, and subscriber opening information, which are referred to as 'first backup information'.

Similarly, when the call processing unit 113 included in the calling TAS 110-2 determines that the calling TAS 110-2 has failed, the received TAS 110-2 stores information contained in the To header, User Agent Obtain the information contained in the header and contained in the Contact header. Then, the backup information requesting unit 114 requests the HSS 120 to acquire the subscriber opening information that can not be acquired in the sender byte message. Herein, the subscriber opening information is referred to as &quot; second backup information &quot;.

The call processing unit 113 restores the lost call processing information using the first backup information received from the backup information requesting unit 114 and the information included in the To header acquired by the call processing unit 113, And performs call processing procedures using call processing information. In addition, the call processing unit 113 includes the second backup information received from the backup information request unit 114, the information included in the To header acquired by the call processing unit 113, the information included in the Contact header, And performs a call processing procedure for the normal call processing using the received information.

When the call processing unit 113 determines that a failure has occurred in the TAS 110, the backup information request unit 114 transmits the first backup information or the second backup information to the HSS 120 in response to a request received from the call processing unit 113 Requests to provide any one backup information. When the first backup information or the second backup information is received from the HSS 120, the received backup information is transferred to the call processing information storage unit 112 to recover the call processing information, And transmits the second backup information to the call processing unit 113 so that the normal call processing procedure is performed.

Referring to FIG. 4, the HSS 120 includes a backup information storage unit 121 and an information request receiving unit (not shown). The HSS 120 includes a backup information storage unit 121, 122).

The backup information storage unit 121 receives recovery information including information included in the Contact header and information included in the User Agent header from the S-CSCF 130 and stores the information as backup information. And also stores subscriber opening information previously stored in the HSS 120 in the backup information.

 In general, the information contained in the To header included in the call processing information can be recovered from the invite message. Therefore, the information included in the contact header and the information included in the User Agent header are stored in the backup information storage unit 121 as recovery object information, excluding the information included in the To header included in the byte message.

The information request receiving unit 122 transmits the requested first backup information or second backup information to the TAS 110 when the TAS 110 receives the request to provide either the first backup information or the second backup information. Here, the first backup information includes subscriber opening information, information included in the Contact header, and information included in the User Agent header, and the second backup information includes subscriber opening information.

In the process of transmitting / receiving the backup information between the HSS 120 and the TAS 110, the backup information is requested and transmitted through the UDR / UDA procedure of the Sh interface. The Sh interface type or the UDR / UDA procedure is already known and will not be described in detail in the embodiments of the present invention.

5, the S-CSCF 130 includes a message reception unit 131, a call processing information transmission unit 130, and a call control information transmission unit 130. The S- (132) and a message transfer unit (133).

The message receiving unit 131 receives the register message transmitted in the network registration procedure of the initial terminal. And receives either the incoming byte message or the outgoing byte message. Here, the incoming byte message or the originator byte message is a SIP INVITE message transmitted from the S-CSCF 130 to the TAS 110 when the terminal attempts to terminate the call or requests a call. The format of the invite message is already known and will not be described in detail in the embodiment of the present invention.

The call processing information transmitting unit 132 transmits to the TAS 110 a register message including call processing information among the messages received by the message receiving unit 131. [ Here, the register message is transmitted to the TAS 110 via the S-CSCF 130. For convenience of explanation, it is described that the S-CSCF 130 transfers the register message to the TAS 110. Then, the recovery target information is extracted from the information included in the register message and is transmitted to the HSS 120, and is stored as backup information together with subscriber opening information.

The S-CSCF 130 and the HSS 120 use the Cx interface in order for the call processing information transmitting unit 132 to transmit the recovery object information to the HSS 120. [ The recovery object information is transmitted through the SAR / SAA (Server Authorization Request / Answer) procedure, which is a procedure in which the S-CSCF 130 registers information in the HSS 120 and downloads necessary data.

The message transferring unit 133 transfers the inbox message received by the message receiving unit 131 to the TAS 110.

A method of recovering a failed TAS through the above-described failure recovery system will be described with reference to FIGS. 6 and 7. FIG. FIG. 6 is a flowchart illustrating a data recovery procedure when the TAS performs the termination processing of the terminal, and FIG. 7 is a flowchart of the data recovery procedure when the TAS performs the termination processing of the terminal.

FIG. 6 is a flowchart illustrating a fault recovery method of a called TAS according to an exemplary embodiment of the present invention, and FIG. 7 is a flowchart illustrating a fault recovery method of a calling TAS according to an exemplary embodiment of the present invention.

First, referring to FIG. 6, a description will be given of a procedure for restoring the data to be performed when the called party TAS 110-1 performs a call termination process of the terminal. In order to recover the TAS 110, The procedure for registering a network is described first.

6, when a network registration request is generated in order to use a call service in VoLTE from the terminal, the S-CSCF 130 transmits a REGISTER message, which is a received network registration request signal, And the information contained in the User Agent header to the HSS 120 as recovery object information (S100). In step S100, recovery object information is transferred from the S-CSCF 130 to the HSS 120 through the SAR / SAA procedure. The SAR / SAA procedure is already known, and a detailed description thereof will be omitted in the embodiment of the present invention .

The information included in the User Agent header transmitted from the S-CSCF 130 to the HSS 120 among the recovery target information transmitted in the step S100 is not the information held by the HSS 120, Added information.

That is, the restoration information included in the SAR (Server Authorization Request) basically includes information included in the Path header defined in the standard and information included in the Contact header. In addition, in the embodiment of the present invention, the information included in the User Agent header, which is the terminal information indicating the terminal type and the model name, and the information included in the P-Access-Network-Info header, which is the network information connected to the terminal, are added. This is for restoring the information stored in the TAS 110 to the backup information in the HSS 120 when the TAS 110 fails, and the recovery information included in the recovery SAR is shown in Table 2 below.

Restoration-Info :: = <AVP Header: 649, 10415>
{Path}
{Contact}
{User Agent}
{P-Access-Network-Info}
[Subscription-Info]

In step S100, the S-CSCF 130 transmits a register message to the HSS 120, and the S-CSCF 130 transmits a register message to the TAS 110 in step S101.

Upon receipt of the register message in step S101, the TAS 110 parses the register message to extract and store call processing information, which is data necessary for call processing. The types of parameters and information included in call processing information are not limited to any one.

The TAS 110 stores the call processing information received in step S101, receives the subscriber opening information from the HSS 120, and stores it in addition to the call processing information stored in step S101 (S102). The method of transmitting / receiving subscriber opening information is already known, and a detailed description thereof will be omitted in the embodiment of the present invention.

Through this procedure, information included in the Contact header, information included in the User Agent header, and subscriber opening information are stored in the HSS 120 as backup information, and the TAS 110 stores call processing information.

Upon receiving the incoming INVITE message, the S-CSCF 130 delivers the received incoming byte message to the called TAS 110-1 (S103). The incoming byte message includes the information of the calling terminal as well as the telephone number of the called terminal, as shown in the following Table 3.

INVITE sip: 01012345678@ims.mnc008.mcc450.3gppnetwork.org SIP / 2.0
To: <tel: +821012345678>
......
CONTACT: <sip: 821012345678@102.125.129.175: 5060>; + g.3gpp.icsi-ref = "urn% 3Aurn-
7% 3A3gpp-service.ims.icsi.mmtel "; + sip.instance ="<urn: gsma: imei: 35922806-949541-0>"
......

The called party TAS 110-1 parses the Invite message and extracts the called party telephone number. The called terminal telephone number can be confirmed from the underscored Request URI in the example of the invite message shown in Table 3 above. And confirms whether the extracted destination telephone number is stored in the call processing information (S104).

If there is no failure in the TAS 110, the called terminal telephone number extracted in step S104 is included in the call processing information stored in the TAS 110. [ Accordingly, if the TAS 110 confirms that the called terminal number is stored in the call processing information of the called TAS 110-1 as a result of checking in step S104, the called TAS 110-1 transmits the S-CSCF 130) (S105). At this time, the type and the transmission method of the call termination processing signal are already known, and a detailed description will be omitted in the embodiment of the present invention. Based on the signal received in step S105, the S-CSCF 130 transmits an incoming byte message to the called terminal.

On the other hand, as a result of checking in step S104, the called terminal telephone number extracted and parsed in step S103 may not be stored in the call processing information of the receiving TAS 110-1. That is, when there is no call processing information, it is determined that call processing information extracted from the register message is lost in steps S100 to S102 of the initial network registration procedure, and it is recognized that a failure has occurred in the destination TAS 110-1 .

Therefore, the called TAS 110-1 requests the HSS 120 to provide the first backup information (S106). The first backup information includes information included in the User Agent header, information included in the Contact header, and subscriber opening information. In response to the request of step S106, the HSS 120 transmits the first backup information stored in advance to the TAS 110 (S107). That is, since the information contained in the Contact header of the incoming-by-byte message and the information contained in the User Agent header are information on the calling terminal, information included in the Contact header and information included in the User Agent header are obtained from the incoming- It is impossible. And thus receives these information from the HSS 120 as first backup information.

In step S106, the HSS 120 requests the HSS 120 to provide the first backup information, and the TAS 110-1 on the receiving side extracts the information included in the To header in the incoming-by-byte message (S108). The called TAS 110-1 updates the already stored call processing information to the information included in the first backup information received in step S107 and the To header extracted in step S108 to recover the lost call processing information (S109).

Then, the S-CSCF 130 transmits a call termination processing signal for the incoming byte message. The S-CSCF 130, which has received the call termination processing signal, transmits the call-in byte message to the called terminal and continues the call processing procedure (S110).

FIG. 6 illustrates a procedure for recovering lost data when the TAS 110 performs a terminal call procedure, and FIG. 7 illustrates a data loss recovery procedure of the TAS when the terminal performs a call origination procedure.

In FIG. 7, the procedure for registering a network requested by the terminal is described first for failure recovery of the TAS. 7, when a network registration request is generated in order to use the call service in the VoLTE from the terminal, the S-CSCF 130 transmits a REGISTER message, which is a network registration request signal received from the calling terminal, And the information included in the User Agent header to the HSS 120 as recovery object information (S200). Here, in step S200, the recovery object information is transferred from the S-CSCF 130 to the HSS 120 through the SAR / SAA procedure, and the SAR / SAA procedure is already known and will not be described in detail in the embodiment of the present invention .

In this case, the information included in the User Agent header transmitted from the S-CSCF 130 to the HSS 120 among the recovery subject information transmitted in the step S200 is not information held by the HSS 120, Is added information.

That is, the restoration information included in the SAR (Server Authorization Request) basically includes information included in the Path header defined in the standard and information included in the Contact header. In addition, in the embodiment of the present invention, the information included in the User Agent header, which is the terminal information indicating the terminal type and the model name, and the information included in the P-Access-Network-Info header, which is the network information connected to the terminal, are added. This is to restore the information stored in the TAS 110 to the backup information in the HSS 120 when the TAS 110 fails, and the recovery information included in the recovery SAR is stored in the table 2 As shown in Fig.

In step S200, the S-CSCF 130 transmits the register object message to the HSS 120 and the register message to the TAS 110 in step S201.

Upon receipt of the register message in step S201, the TAS 110 parses and extracts call processing information, which is data necessary for call processing, and stores the extracted call processing information. The types of parameters and information included in call processing information are not limited to any one.

The TAS 110 stores the received call processing information in step S201, receives subscriber opening information from the HSS 120, and stores the received subscriber opening information in the call processing information (S202). The method of transmitting / receiving subscriber opening information is already known, and a detailed description thereof will be omitted in the embodiment of the present invention.

Through this procedure, information included in the Contact header, information included in the User Agent header, and subscriber opening information are stored in the HSS 120 as backup information, and the TAS 110 stores call processing information.

When the S-CSCF 130 receives the sender byte message from the source terminal, it transfers the received sender byte message to the TAS 110 (S203). Herein, the S-CSCF 130 does not receive the sender byte message directly from the originating terminal but is shown as being transmitted from the terminal for convenience of explanation in the embodiment of the present invention.

The outgoing byte message is as shown in Table 4 below.

INVITE tel: +821087654321 SIP / 2.0
To: <tel: 01087654321; phone-context = ims.mnc008.mcc450.3gppnetwork.org>
... ...
Contact: <sip: 821012345678@102.125.129.175: 5060>; + g.3gpp.icsi-ref = "urn% 3Aurn-7% 3A3gpp-service.ims.icsi.mmtel"
......
P-Asserted-Identity: <sip: 01012345678@ims.mnc008.mcc450.3gppnetwork.org>, <tel: +821012345678>
P-Access-Network-Info: 3GPP-E-UTRAN-FDD; utran-cell-id-3gpp = 450080008026670e
User Agent: TTA-VoLTE / 1.0 iOS / 8.3 iPhone / 1.0 / KT
......

The originating TAS 110-2 parses the origination byte message received in step S203, extracts the originating terminal telephone number, and checks whether the extracted originating terminal telephone number is stored in the call processing information (S204). Herein, the calling terminal telephone number is the information included in the P-Asserted-Identity header in Table 4, which shows an example of the sender byte message.

If there is no fault in the calling TAS 110-2, the calling terminal telephone number extracted in step S204 is stored in the TAS 110. [ Accordingly, when the TAS 110 confirms that the calling terminal telephone number is included in the call processing information stored in the calling TAS 110-2 as a result of checking in step S204, the TAS 110 transmits the S- (S205). &Lt; / RTI &gt; At this time, the form and the transmission method of the signal for normal calling processing are already known, and the detailed description will be omitted in the embodiment of the present invention.

On the other hand, as a result of checking in step S204, the calling terminal telephone number extracted and parsed in step S203 may not be stored in the calling TAS 110-2. In this case, it is recognized that the source TAS 110-2 has failed. Therefore, the source TAS 110-2 requests the HSS 120 to provide the second backup information (S207).

6, since the information included in the Contact header included in the message and the information included in the User Agent header are information on the calling terminal, the receiving TAS 110-1 is the receiving terminal, It is impossible to obtain the incoming information from the byte message. However, in the outgoing byte message, the telephone number of the called terminal is included in the To header and the information of the calling terminal is included in the Contact header and User Agent header. At the same time, the P-Asserted-Identity header includes the telephone number of the calling terminal.

Therefore, when requesting the provision of the second backup information in step S207, the source TAS 110-2 obtains the information included in the Contact header and the information included in the User Agent header from the origination byte message (S206). The HSS 120 transmits second backup information including subscriber opening information among the stored backup information to the TAS 110 (S208).

The source TAS 110-2 updates the already stored call processing information with the information obtained in step S206 and the second backup information received from the HSS 120 in step S208 to recover the lost call processing information (S209). The S-CSCF 130 transmits a call origination process signal for the sender byte message to perform a call process procedure (S210).

In this way, even if the call processing information is lost due to the failure of the TAS 110, the information backed up in the HSS 120 is recovered from the TAS 110, so that the normal terminal can be called.

While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it is to be understood that the invention is not limited to the disclosed exemplary embodiments, It belongs to the scope of right.

Claims (15)

A home subscriber server for managing subscriber opening information, receiving recovery target information from information necessary for registering in an IP Multimedia Subsystem (IMS) network of a terminal from a serving call session control server, and storing the target information for recovery as backup information; And
A TAS (Telephony Application Server) for storing call processing information extracted from a register message (REGISTER Message) received from the serving call session control server and adding the subscriber opening information received from the home subscriber server to the call processing information,
/ RTI &gt;
Upon receipt of an INVITE message from the serving call session control server, the TAS determines that a failure occurs if the phone number included in the invite message does not exist in the call processing information, And recovering the lost call processing information using the backup information and the invite message received from the TAS. The method according to claim 1,
The call processing information includes:
A TAS failure recovery system including information included in a To header, information included in a contact header, information included in a User Agent header, or information included in a P-Access-Network-Info header among the information included in the register message. 3. The method of claim 2,
If the invite message is an incoming byte message and it is determined that a failure has occurred,
To header information is extracted from the incoming-by-byte message to recover call processing information,
Wherein the information included in the contact header, the information included in the User Agent header, and the subscriber opening information are received from the home subscriber server to recover the call processing information. The method of claim 3,
The home subscriber server comprises:
And receiving the recovery object information from the serving call session control server through a SAR / SAA (Server Authorization Request / Server Authorization Answer) procedure. 5. The method of claim 4,
The TAS,
And acquires information included in the Contact header, which is one of the recovery object information, from the home subscriber server through a UDR / UDA (User Data Request / User Data Answer) procedure. 3. The method of claim 2,
If the invite message is a sender byte message and it is determined that a failure has occurred,
The information included in the To header, the information included in the Contact header, and the information included in the User Agent header are recovered from the caller byte message to recover call processing information,
Wherein the subscriber opening information is received from the home subscriber server as backup information to recover call processing information. In the manner in which the TAS restores the fault,
Receiving an INVITE message for processing a call from a serving call session control server;
Determining whether a telephone number included in the invite message exists in call processing information; And
Determining that a failure has occurred if the telephone number does not exist in the call processing information, recovering the lost call processing information using the backup information received from the home subscriber server and the invite message
And a TAS failure recovery method. 8. The method of claim 7,
Before the step of receiving the invite message,
Receiving a register message (REGISTER message) from the call session control server; And
Parsing the register message to extract and store call processing information necessary for call processing
Further comprising a TAS failure recovery method. 9. The method of claim 8,
The call processing information includes:
A TAS fault recovery method including information included in a To header, information included in a contact header, information included in a User Agent header, or information included in a P-Access-Network-Info header among data included in the register message. 10. The method of claim 9,
Before the step of receiving the invite message,
Receiving subscriber opening information from the home subscriber server; And
Further storing the received subscriber opening information in the call processing information
And a TAS failure recovery method. 8. The method of claim 7,
Wherein the recovering lost call processing information when the invite message is an incoming byte message comprises:
To header information is extracted from the incoming-by-byte message to recover call processing information,
The information included in the Contact header, the information included in the User Agent header, and the subscriber opening information, from the home subscriber server to recover the call processing information. 8. The method of claim 7,
Wherein the recovering lost call processing information when the invite message is an outgoing byte message comprises:
The information included in the To header, the information included in the Contact header, and the information included in the User Agent header are recovered from the caller byte message to recover call processing information,
Wherein the subscriber opening information is received from a home subscriber server to recover call processing information. 8. The method of claim 7,
Before the step of receiving the invite message,
The serving call session control server receiving a register message; And
Extracting the recovery object information from the received register message, and transmitting the extracted recovery object information to the home subscriber server
And a TAS failure recovery method. 14. The method of claim 13,
Wherein the recovery object information includes information included in a User Agent header and information included in a Contact header. 14. The method of claim 13,
Before the step of receiving the invite message,
The home subscriber server receiving recovery object information from the serving call gateway control server; And
Storing the pre-stored subscriber opening information and the recovery target information as backup information
And a TAS failure recovery method.
KR1020160018034A 2016-02-16 2016-02-16 System and method for TAS restoration based home subscribe server KR20170096531A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
KR1020160018034A KR20170096531A (en) 2016-02-16 2016-02-16 System and method for TAS restoration based home subscribe server

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
KR1020160018034A KR20170096531A (en) 2016-02-16 2016-02-16 System and method for TAS restoration based home subscribe server

Publications (1)

Publication Number Publication Date
KR20170096531A true KR20170096531A (en) 2017-08-24

Family

ID=59758377

Family Applications (1)

Application Number Title Priority Date Filing Date
KR1020160018034A KR20170096531A (en) 2016-02-16 2016-02-16 System and method for TAS restoration based home subscribe server

Country Status (1)

Country Link
KR (1) KR20170096531A (en)

Similar Documents

Publication Publication Date Title
US9294618B2 (en) Call-back to a UE that has made an emergency call via a visited IMS network
US8208930B2 (en) Message routing in a telecommunication system
US9854005B2 (en) Methods and apparatus for providing network based services to non-registering endpoints
US10044553B2 (en) Media resource reservation request failure handling for voice over mobile wireless network
US11824903B2 (en) Voice service restoration after element failure
US7936665B2 (en) IMS network system and data restoring method
US9148288B2 (en) Conditional telecommunications
WO2007045991A1 (en) Ims call routing using tel-uris
CN101931923B (en) Method for user registration of IP multimedia subsystem network and service fulfillment system
EP2056556A1 (en) An intercommunication method and a communication system between different networks
US20150312281A1 (en) Method and system for selection in multi-device scenario
CN106941669B (en) Wireless communication method and P-CSCF (proxy Call Session control function) equipment
KR100703426B1 (en) Method and apparatus for sending and receiving call unregistered user in a ip multimedia subsystem network
EP2898647B1 (en) Methods and apparatus for processing an ims session
CN101365240B (en) Call connecting method, apparatus and system in IP multimedia subsystem
US9071620B2 (en) Method and system for enabling communication in a hybrid network
US10412127B2 (en) Method and apparatus for establishing an additional session to an anonymous user
US20080186956A1 (en) Method and system for processing call change request in an internet protocol multimedia subsystem
CN100477824C (en) Emmergency log-on method of Internet protocol multimedia subsystem field
KR20170096531A (en) System and method for TAS restoration based home subscribe server
JP7045129B2 (en) Session control server switching method, management server and program
CN101060704B (en) An Internet protocol multimedia subsystem domain emergency register method
KR101473588B1 (en) Call processing system of ims, control method thereof, and recording medium for recording program for executing the control method
KR20200049715A (en) Vioce call service swiching system, gateway apparatus and service swiching apparatus and control method each of them