WO2016114476A1 - Appareil et procédé de gestion de sessions volte dans un réseau mobile 4g - Google Patents

Appareil et procédé de gestion de sessions volte dans un réseau mobile 4g Download PDF

Info

Publication number
WO2016114476A1
WO2016114476A1 PCT/KR2015/011934 KR2015011934W WO2016114476A1 WO 2016114476 A1 WO2016114476 A1 WO 2016114476A1 KR 2015011934 W KR2015011934 W KR 2015011934W WO 2016114476 A1 WO2016114476 A1 WO 2016114476A1
Authority
WO
WIPO (PCT)
Prior art keywords
user information
information table
packet
message
user
Prior art date
Application number
PCT/KR2015/011934
Other languages
English (en)
Inventor
Chae Tae Im
Joo Hyung Oh
Se Kwon Kim
Bon Min Koo
Seong Min Park
Su Jeong Woo
Eun Hye Ko
Original Assignee
Korea Internet & Security Agency
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 Korea Internet & Security Agency filed Critical Korea Internet & Security Agency
Publication of WO2016114476A1 publication Critical patent/WO2016114476A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/22—Parsing or analysis of headers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • 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
    • 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/1066—Session management
    • H04L65/1069—Session establishment or de-establishment
    • 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/1066—Session management
    • H04L65/1073—Registration or de-registration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/2866—Architectures; Arrangements
    • H04L67/30—Profiles
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/75—Indicating network or usage conditions on the user display

Definitions

  • the present inventive concept relates to an apparatus and a method for VoLTE session management, and more particularly, to an apparatus and a method for VoLTE session management in a 4G mobile network using GPRS tunneling protocol (GTP).
  • GTP GPRS tunneling protocol
  • a 4G network (or an LTE network) includes a 4G Enterprise Radio Access Network (E-RAN) for management of a radio resource and a 4G Evolved Packet Core (EPC) for performing data processing, authentication, charging and the like.
  • E-RAN 4G Enterprise Radio Access Network
  • EPC 4G Evolved Packet Core
  • the 4G E-RAN includes components such as user equipment (UE), evolved Node B (eNB) and the like, and the 4G EPC includes components such as Mobility Management Entity (MME), Serving Gateway (S-GW), PDN Gateway (P-GW), Home Subscriber Server (HSS), Policy & Charging Rule Function (PCRF) and the like.
  • MME Mobility Management Entity
  • S-GW Serving Gateway
  • PDN Gateway PDN Gateway
  • HSS Home Subscriber Server
  • PCRF Policy & Charging Rule Function
  • a data packet may be transmitted/received through an S1-U GPRS tunneling protocol (GTP) tunnel generated between eNB and an S-GW and an S5 GTP tunnel generated between S-GW and P-GW in the 4G network.
  • the data packet may include a session initiation protocol (SIP) for VoLTE call set-up, and the data packet may be transmitted/received by being capsulated in a payload of a GTP packet.
  • SIP session initiation protocol
  • the P-GW may transfer the data packet into an IP Multimedia Subsystem (IMS) network without considering the values included in the SIP message.
  • IMS IP Multimedia Subsystem
  • An embodiment of the present inventive concept provides an apparatus for VoLTE session management, capable of analyzing a type of a message included in GTP-U packet information so as to manage a user information table.
  • Another embodiment of the present inventive concept provides a method for VoLTE session management, capable of analyzing a type of a message included in GTP-U packet information so as to manage a user information table.
  • an apparatus and a method for VoLTE session management capable of creating, updating and deleting a user information table by using message type information included in the packet information extracted from GTP-U packet so as to manage a VoLTE-related user session.
  • According to the present inventive concept relates to the apparatus and the method for managing a VoLTE session, by which a user session related VoLTE can be managed to create, update, and delete user information tables by using message type information within packet information extracted from a GTP-U packet.
  • FIG. 1 is a schematic block diagram of a system including a VoLTE session management apparatus according to an embodiment of the present inventive concept
  • FIG. 2 illustrates a data frame acquired by processing a GTP-U packet and a GTP-C packet
  • FIG. 3 is a block diagram illustrating a detailed module of a packet management unit of FIG. 1;
  • FIG. 4 is a block diagram illustrating a detailed module of a packet analysis unit of FIG. 1 ;
  • FIG. 5 is a block diagram illustrating a detailed module of a GTP tunnel information collection module of FIG. 4;
  • FIG. 6 is a data table illustrating an operation of a control message management module of FIG. 5;
  • FIG. 7 is a flow chart illustrating an operation of a message processing module of FIG. 5;
  • FIG. 8 is a flow chart illustrating a session generating operation of the message processing module
  • FIG. 9 and FIG. 10 are data tables illustrating a session generating operation of the message processing module
  • FIG. 11 is a flow chart illustrating a session updating operation of the message processing module
  • FIG. 12 and FIG. 13 are data tables illustrating the session updating operation of the message processing module
  • FIG. 14 is a flow chart illustrating a session deleting operation of the message processing module
  • FIG. 15 and FIG. 16 are data tables illustrating a session deleting operation of the message processing module
  • FIG. 17 is a block diagram illustrating a detailed module of a VoLTE session management engine of FIG. 4;
  • FIG. 18 is a data table illustrating an operation of the VoLTE session management engine of FIG. 4;
  • FIG. 19 to FIG. 21 are index hash tables
  • FIG. 22 is a flow chart illustrating an operation of a VoLTE session management module of FIG. 17;
  • FIG. 23 is a flow chart illustrating an operation of a message processing module of FIG. 17;
  • FIG. 24 illustrates an example of a unitary message completed for creating a user information table
  • FIG. 25 is a flow chart illustrating a user information table creating operation of the message processing module
  • FIG. 26 illustrates an example of the created user information table
  • FIG. 27 illustrates an example of a unitary message completed for deleting a user information table
  • FIG. 28 is a flow chart illustrating a user information table deleting operation of the message processing module
  • FIG. 29 illustrates an example of the unitary message completed for creating an RTP table
  • FIG. 30 is a flow chart illustrating an RTP table creating operation of the message processing module
  • FIG. 31 illustrates an example of the created RTP table
  • FIG. 32 illustrates an example of a unitary message completed for deleting field values of the Call ID table and RTP table
  • FIG. 33 is a flow chart illustrating a field value deleting operation of the Call ID table and RTP table of the message processing module
  • FIG. 34 illustrates examples of a Call ID table and an RTP table from which a field value is deleted
  • FIG. 35 illustrates an example of a unitary message completed for updating the field value of the Call ID table
  • FIG. 36 is a flow chart illustrating a field value updating operation of the Call ID table of the message processing module
  • FIG. 37 illustrates an example of a Call ID table in which a field value is updated
  • FIG. 38 is flow chart illustrating an operation of checking the Timestamp field value and deleting the user information table by the message processing module
  • FIG. 39 illustrates an example of the user information table from which a field value is deleted
  • FIG. 40 illustrates a structure of a 4G network to which the VoLTE session management apparatus according to the present inventive concept is applied;
  • FIG. 41 illustrates a structure of an IMS network linked to the 4G network of FIG. 40.
  • FIG. 42 is a flow chart illustrating a VoLTE session management method according to an embodiment of the present inventive concept.
  • Each block may represent a part of a module, segment or code including one or more executable instructions for specified logical function(s). Further, it should be noted that, in some alternative execution examples, the functions mentioned in the blocks can occur out of the order. For example, two successively shown blocks can be substantially simultaneously executed, or can sometimes be executed in the reverse order depending on the corresponding function.
  • first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. Thus, for example, a first element, a first component or a first section discussed below could be termed a second element, a second component or a second section without departing from the teachings of the present inventive concept.
  • FIG. 1 is a schematic block diagram of a system including a VoLTE session management apparatus according to an embodiment of the present inventive concept.
  • FIG. 2 illustrates a data frame acquired by processing a GTP-U packet and a GTP-C packet.
  • a system including a VoLTE session management apparatus includes a network interface card (NIC) 10, a packet management unit 100, a packet analysis unit 200, a packet analysis result management unit 300, a system management unit 400, a system communication unit 500 and first to fourth storage units DB1, DB2, DB3 and DB4.
  • NIC network interface card
  • the NIC 10 may receive a GTP packet and transmit the received GTP packet to the packet management unit 100, and forward or drop the GTP packet according to a control signal of the packet management unit 100.
  • the NIC 10 may be a general network interface card or a hardware accelerating network interface card.
  • the GTP packet may include a GTP-C packet and a GTP-U packet, and the GTP-U packet may be used to transmit a data packet of a user in a 4G network.
  • the packet management unit 100 may receive the GTP packet from the NIC 10, classify the received GTP packet into a GTP-U packet and a GTP-C packet, extract first packet information D1 from the GTP-U packet and extract second packet information D2 from the GTP-C packet.
  • the first packet information D1 may include an SIP message extracted from a payload of the GTP-U packet, and a destination IP, a destination PORT, a source IP, a source PORT or a user equipment identification number extracted from the SIP message.
  • the second packet information D2 may include GTP-C TEID extracted from a header of the GTP-C packet.
  • the second packet information D2 may further include GTP-U TEID and UE IP.
  • the packet management unit 100 may extract necessary information from the GTP-U packet and generate a first data frame F1, and the first data frame F1 may include data such as TEID(UL-DATA), Src IP, Dst IP, protocol, Src port, Dst port, length and the like. Furthermore, the packet management unit 100 may extract necessary information from the GTP-C packet and generate a second data frame F2, and the second data frame F2 may include data such as Src IP, Src port, Msg type, TEID, GTP-C information element (IE) and the like.
  • the GTP-C IE may include different information depending on a message type (Msg Type_1). For example, GTP-C IE may include information such as TEID, MSISDN, IP and the like.
  • the packet management unit 100 may communicate with the second storage unit DB2 so as to check a packet filtering policy, system operation mode and the like.
  • the second storage unit DB2 may be, for example, an operation mode information storage unit.
  • the packet analysis unit 200 may receive and analyze first and second packet information D1 and D2, and create, update or delete first and second user information tables (Regi Table and Call ID Table) according to a message type (Msg Type_2) included in the first packet information D1.
  • the first user information table (Regi Table) may include information regarding a terminal registration
  • the second user information table (Call ID Table) may include information regarding a call ID.
  • the packet analysis unit 200 may generate packet blocking information D3 for blocking an abnormal GTP packet and transmit the generated packet blocking information D3 to the packet management unit 100.
  • the packet analysis unit 200 may transmit packet analysis result information D4 to the packet analysis result management unit 300, and transmit GTP-C/U packet analysis information D5 to the first storage unit DB1.
  • the first storage unit DB1 may be, for example, a user GTP tunnel information storage unit.
  • the first storage unit DB11 may store therein the first and second user information tables (Regi Table and Call ID Table).
  • the packet analysis unit 200 may communicate with the third storage unit DB3 so as to check a detection/blocking policy.
  • the third storage unit DB3 may be, for example, a detection/blocking policy storage unit.
  • the packet analysis result management unit 300 may receive the packet analysis result information D4 from the packet analysis unit 200 so as to extract user information, and generate detection/blocking result information D6.
  • the detection/blocking result information D6 may be information on the result of the analysis of the user information extracted from the GTP-U packet and the GTP-C packet.
  • the packet analysis result management unit 300 may communicate with the first storage unit DB1 so as to make an inquiry about a packet-forwarded user by using the extracted user information. Further, the packet analysis result management unit 300 may transmit the detection/blocking result information D6 to the fourth storage unit DB4.
  • the fourth storage unit DB4 may be, for example, a detection/blocking log storage unit.
  • the system management unit 400 may monitor the state of a system through a traffic input/output status, set an operation mode of the system according to the result of the monitoring, and transmit system operation mode information D7 to the second storage unit DB2.
  • the system management unit 400 may transmit traffic input/output status information D8 to the system communication unit 500.
  • the system communication unit 500 may analyze and manage a system message transmitted to an internal system or an external system.
  • the system message may include a system management message for setting an operation mode of the internal system, a policy management message for setting a detection/blocking policy of the internal system, a detection/blocking log inquiry message for detection/blocking log inquiry of the internal system, a GUI protocol for communication with GUI, an external system linked protocol for setting a detection/blocking policy in linkage with the external system, and the like.
  • FIG. 3 is a block diagram illustrating a detailed module of the packet management unit of FIG. 1.
  • the packet management unit 100 may apply an IPS mode or a BYPASS mode of a system by using the system operation mode information stored in the second storage unit DB2.
  • the IPS mode analyzes whether the GTP packet transmitted through the NIC 10 is normal or abnormal and forwards or drops the GTP packet, and the BYPASS mode forwards all GTP packets without analyzing whether the GTP packet transmitted through the NIC 10 is normal or abnormal.
  • the packet management unit 100 may receive the GTP packet according to a system operation mode, and analyze the GTP packet so as to filter the GTP packet on the basis of a destination IP and a destination port which are set. The packet management unit 100 may then classify the GTP packet into a GTP-U packet and a GTP-C packet. The packet management unit 100 may process the classified GTP-U packet and GTP-C packet so as to generate the first data frame F1 and the second data frame F2 and transmit the generated data frames F1 and F2 to the packet analysis unit 200 (see FIG. 2).
  • the packet management unit 100 may control (that is, forward or drop) the packet through a packet control module by using the packet blocking information D3 transmitted from the packet analysis unit 200.
  • the packet control may be performed only when the system is in an IPS mode.
  • FIG. 4 is a block diagram illustrating a detailed module of a packet analysis unit of FIG. 1.
  • FIG. 5 is a block diagram illustrating a detailed module of a GTP tunnel information collection module of FIG. 4.
  • FIG. 6 is a data table illustrating an operation of a control message management module of FIG. 5.
  • FIG. 7 is a flow chart illustrating an operation of a message processing module of FIG. 5.
  • the packet analysis unit 200 may communicate with the third storage unit DB3 so as to check a detection/blocking policy.
  • the packet analysis unit 200 may analyze the first packet information D1 and detect a GTP packet including an abnormal SIP message through an abnormal SIP detection module according to the detection/blocking policy applied to the system.
  • the GTP packet may be processed according to the result of the analysis of the first packet information D1 performed by the packet analysis unit 200. That is, the packet analysis unit 200 may transmit the packet blocking information D3 to the packet management unit 100 such that the packet management unit 100 may forward or drop the GTP packet.
  • the packet analysis unit 200 may include a GTP tunnel information collection module 210, and extract session information from the second packet information D2 through the GTP tunnel information collection module 210.
  • the packet analysis unit 200 may create, update or delete a user information table (a UC table, a UD table and an IP table) according to the message type (Msg Type_1) included in the second packet information D2.
  • the GTP tunnel information collection module 210 may include a control message management module 220 and a message processing module 230.
  • the control message management module 220 may include a message buffer 221, and complete a unitary message (UM_1) through a request message and a response message.
  • the control message management module 220 may add, to the message buffer 221, a message column with MME IP and sequence number values as a key value upon confirming a request message. Since the S-GW may receive messages from a plurality of MMEs, the control message management module 220 may add MME IP as a key value considering a duplication of the sequence number value. The control message management module 220 may check, from the message column, whether a message having the same value exists in the request message stored in the message buffer 221 upon confirming a response message. When the key value of the response message is the same as the key value of the request message, the field content of the corresponding response message is added to the message column so as to complete the unitary message (UM_1) (see FIG. 6; the underlined data is added from the response message).
  • UM_1 unitary message
  • the completed unitary message (UM_1) may be transmitted to the message processing module 230, and then deleted from the message buffer 221.
  • the message processing module 230 may manage the user information table (UC table, UD table and IP table) stored in the first storage unit DB1 through the unitary message (UM_1). That is, the message processing module 230 may create, update or delete the user information table (UC table, UD table and IP table) stored in the first storage unit DB1.
  • the message processing module 230 may receive the unitary message (UM_1), and check the message type (Msg Type_1) information included in the unitary message (UM_1). If the message type (Msg Type_1) is a user information table create request (hereinafter, Type 0), the message processing module 230 may determine whether the UC TEID and EBI information included in the second packet information D2 exists in a pre-existing user information table (UIT_1), and if the UC TEID and EBI information exists in the user information table (UIT_1), the message processing module 230 may delete the user information table (UIT_1) and create a new user information table (UIT_2). If the UC TEID and EBI information does not exist in the user information table (UIT_1), the message processing module 230 may not delete the user information table (UIT_1) and may create the user information table (UIT_2).
  • the message processing module 230 may not delete the user information table (UIT_1) and may create the user information table (UIT_2).
  • the message processing module 230 may determine whether the UC TEID and EBI information included in the second packet information D2 exists in the pre-existing user information table (UIT_1), and if the UC TEID and EBI information exists in the user information table (UIT_1), the message processing module 230 may update user information UI included in the user information table (UIT_1). In this case, the user information UI may be UD TEID information.
  • the message processing module 230 may determine whether the UC TEID and EBI information included in the second packet information D2 exists in the pre-existing user information table (UIT_1), and if the UC TEID and EBI information exists in the user information table (UIT_1), the message processing module 230 may delete the user information table (UIT_1).
  • FIG. 8 is a flow chart illustrating a session generating operation of the message processing module.
  • FIG. 9 and FIG. 10 are data tables illustrating a session generating operation of the message processing module.
  • FIG. 11 is a flow chart illustrating a session updating operation of the message processing module.
  • FIG. 12 and FIG. 13 are data tables illustrating the session updating operation of the message processing module.
  • FIG. 14 is a flow chart illustrating a session deleting operation of the message processing module.
  • FIG. 15 and FIG. 16 are data tables illustrating a session deleting operation of the message processing module.
  • the session generating operation of the message processing module 230 may first receive the Type 0 message (that is, the user information table create request message), and determine whether the UC TEID and EBI information of the received Type 0 message (see FIG. 9) exists in the UC table stored in the first storage unit DB1. If the UC TEID and EBI information of the received Type 0 message exists in the UC table, the message processing module 230 may delete the UC table and create a new UC table (1). Subsequently, the message processing module 230 may create a UD table (2), and create an IP table (3).
  • the Type 0 message that is, the user information table create request message
  • the message processing module 230 may delete the UC table and create a new UC table (1).
  • the message processing module 230 may create a UD table (2), and create an IP table (3).
  • the message processing module 230 may not delete UC table and may create a new UC table (1). Subsequently, the message processing module 230 may create a UD table (2), and create an IP table (3).
  • UD TEID information may be input with the UC TEID and EBI values as a key value
  • UE IP information may be input to the UD table with the UD TEID information as a key value
  • MSISDN information may be input to the IP table with the UE IP information as a key value.
  • the session updating operation of the message processing module 230 may first receive the Type 1 message (that is, the user information table update request message), and determine whether the UC TEID and EBI information of the received Type 1 message (see FIG. 12) exists in the UC table stored in the first storage unit DB1. If the UC TEID and EBI information of the received Type 1 message exists in the UC table, the message processing module 230 may determine whether user equipment identification number information (for example, MSISDN) exists in the message buffer 221, and if the user equipment identification number information exists, the message processing module 230 may search the UD table by using the UC table information (1).
  • user equipment identification number information for example, MSISDN
  • the message processing module 230 may search the IP table by using the UD table information (2), and update the user equipment identification number information of the IP table (3). Then, the message processing module 230 may update UD TEID information of the UD table (4), and update UD TEID information of the UC table (5).
  • the message processing module 230 may search the UD table by using the UC table information (1), update the UD TEID information of the UD table (2), and update the UD TEID information of the UC table (3).
  • the session deleting operation of the message processing module 230 may first receive the Type 2 message (that is, the user information table delete request message), and determine whether the UC TEID and EBI information of the received Type 2 message (see FIG. 15) exists in the UC table stored in the first storage unit DB1. If the UC TEID and EBI information of the received Type 2 message exists in the UC table, the message processing module 230 may search the UD table by using the UC table information (1).
  • the Type 2 message that is, the user information table delete request message
  • the message processing module 230 may search the UD table by using the UC table information (1).
  • the message processing module 230 may search an IP table by using the UD table information (2), delete a corresponding field from the IP table (3), delete a corresponding field from the UD table (4), and delete a corresponding field from the UC table (5).
  • FIG. 17 is a block diagram illustrating a detailed module of a VoLTE session management engine of FIG. 4.
  • FIG. 18 is a data table illustrating an operation of the VoLTE session management engine of FIG. 4.
  • FIG. 19 to FIG. 21 are index hash tables.
  • FIG. 22 is a flow chart illustrating an operation of a VoLTE session management module of FIG. 17.
  • a VoLTE session management engine 250 may include a VoLTE session management module 260 and a message processing module 270, and the VoLTE session management module 260 may include a message buffer 261.
  • the VoLTE session management module 260 may complete a unitary message (UM_2) through a request message and a response message by using a message buffer 261.
  • UM_2 unitary message
  • the VoLTE session management module 260 may add, to the message buffer 261, a message column with a call ID value as a key value upon confirming a request message. Furthermore, the VoLTE session management module 260 may check whether a message having the same key value exists among the messages stored in the message buffer 261 upon confirming a response message. If the key value of the response message is the same as the key value of the request message, the field content of the corresponding response message may be added to the message column so as to complete the unitary message (UM_2) (see FIG. 18; the underlined data is added from the request message, and a receiving UE IP and a receiving UE RTP Port are added from the response message).
  • UM_2 unitary message
  • the completed unitary message (UM_2) may be transmitted to the message processing module 270, and then deleted from the message buffer 261.
  • the message processing module 270 may manage the first and second user information tables (Regi Table and Call ID Table) stored in the first storage unit DB1 through the unitary message (UM_2). That is, the message processing module 270 may create, update or delete the first and second user information tables (Regi Table and Call ID Table) stored in the first storage unit DB1.
  • the message processing module 270 may receive the unitary message (UM_2), and check the message type (Msg Type_2) information included in the unitary message (UM_2).
  • the message type (Msg Type_2) may vary depending on the value included in a Method field value.
  • FIG. 19 illustrates an index hash table.
  • the message type (Msg Type_2) is any one of REGISTER, DE-REGISTER, INVITE, BYE or UPDATE types, and the information included in the message in each case is illustrated in a table.
  • the message type (Msg Type_2) is a REGISTER type or a DE-REGISTER type
  • the message may include Call ID, UE IP, MSISDN, Expire and UE information
  • the message type (Msg Type_2) is an INVITE type
  • the message may include Call ID, calling UE IP and calling UE RTP Port information
  • the message type (Msg Type_2) is a BYE type or an UPDATE type
  • the message may include Call ID information.
  • the response message to the REGISTER type or the BYE type may include Call ID information
  • the response message to the INVITE message may include Call ID, receiving UE IP and receiving UE RTP Port information.
  • FIG. 20 and FIG. 21 illustrate examples of fields included in the first user information table (Regi Table) and the second user information table Call ID Table) and information stored in each field.
  • FIG. 22 illustrates an operation of the VoLTE session management module 260.
  • the VoLTE session management module 260 may receive an SIP packet, determine whether the SIP packet includes a request message or a response message, register the request message to the message buffer 261 so as to add a message column for completing the unitary message (UM_2) if the SIP packet includes a request message, check a Timestamp value in the message buffer 261, check whether a user information table in which 60 seconds have lapsed exists, and delete the corresponding user information table if such a user information table exists.
  • UM_2 unitary message
  • the VoLTE session management module 260 may check whether a message column having the same key value exists in the message buffer 261, add user information to the field value of the corresponding message in the message buffer 261 so as to complete the unitary message (UM_2) if a message column having the same key value exists in the message buffer 261, and transmit the unitary message (UM_2) to the message processing module 270 and delete the unitary message (UM_2) from the message buffer 261.
  • the VoLTE session management module 260 may check a Timestamp value in the message buffer 261, check whether a user information table in which 60 seconds have lapsed exists, and delete the corresponding user information table if such a user information table exists.
  • FIG. 23 is a flow chart illustrating an operation of a message processing module of FIG. 17.
  • the message processing module 270 may receive the unitary message (UM_2) and check the message type (Msg Type_2) information included in the Method field value. For example, if the value included in the Method field value of the unitary message (UM_2) is 0, the message may be defined as a REGISTER type, if the value included in the Method field value of the unitary message (UM_2) is 1, the message may be defined as a DE-REGISTER type, if the value included in the Method field value of the unitary message (UM_2) is 2, the message may be defined as an INVITE type, if the value included in the Method field value of the unitary message (UM_2) is 3, the message may be defined as a BYE type, and if the value included in the Method field value of the unitary message (UM_2) is 4, the message may be defined as an UPDATE type.
  • the message processing module 270 may check whether the MSISDN value included in the unitary message (UM_2) exists in the first user information table (Regi Table), delete an existing user information table if the MSISDN value exists in the first user information table (Regi Table), and create a new user information table. If the MSISDN value does not exist in the first user information table (Regi Table), the message processing module 270 may not delete the existing user information table and may create a new user information table.
  • the message processing module 270 may check whether the MSISDN value included in the unitary message (UM_2) exists in the first user information table (Regi Table), and delete the first user information table (Regi Table) if the MSISDN value exists in the first user information table (Regi Table).
  • the message processing module 270 may check whether the Call ID value included in the unitary message (UM_2) exists in the second user information table (Call ID Table), delete an existing user information table if the Call ID value exists in the second user information table (Call ID Table), and create a new user information table. If the Call ID value does not exist in the second user information table (Call ID Table), the message processing module 270 may not delete the existing user information table and may create a new user information table.
  • the message processing module 270 may check whether the Call ID value included in the unitary message (UM_2) exists in the second user information table (Call ID Table), and delete the second user information table (Call ID Table) if the Call ID value exists in the second user information table (Call ID Table).
  • the message processing module 270 may check whether the Call ID value included in the unitary message (UM_2) exists in the second user information table (Call ID Table), and update the corresponding user information if the Call ID value exists in the second user information table (Call ID Table).
  • FIG. 24 illustrates an example of a unitary message completed for creating a user information table.
  • FIG. 25 is a flow chart illustrating a user information table creating operation of the message processing module.
  • FIG. 26 illustrates an example of the created user information table.
  • the message processing module 270 may check whether the MSISDN value included in the unitary message (UM_2) exists in the first user information table (Regi Table), delete an existing user information table if the MSISDN value included in the unitary message (UM_2) exists in the first user information table (Regi Table), and create a new user information table (Regi Table of FIG. 26). If the MSISDN value does not exist in the first user information table (Regi Table), the message processing module 270 may not delete the existing user information table and may create a new user information table (Regi Table of FIG. 26).
  • FIG. 27 illustrates an example of a unitary message completed for deleting a user information table.
  • FIG. 28 is a flow chart illustrating a user information table deleting operation of the message processing module.
  • the message processing module 270 may check whether the MSISDN value included in the unitary message (UM_2) exists in the first user information table (Regi Table), and delete the first user information table (Regi Table) if the MSISDN value exists in the first user information table (Regi Table). Furthermore, the message processing module 270 may check the Expire value in another user information table and delete the corresponding user information table if an expiration date has been reached.
  • FIG. 29 illustrates an example of the unitary message completed for creating an RTP table.
  • FIG. 30 is a flow chart illustrating an RTP table creating operation of the message processing module.
  • FIG. 31 illustrates an example of the created RTP table.
  • the message processing module 270 may check whether the Call ID value included in the unitary message (UM_2) exists in the second user information table (Call ID Table), delete an existing user information table if the Call ID value exists in the second user information table (Call ID Table), create a new Call ID table, and create a new RTP table with the calling UE IP and calling UE RTP Port field values of the Call ID table as a key value.
  • the message processing module 270 may not delete the existing user information table and may create a new Call ID table, and create a new RTP table with the calling UE IP and calling UE RTP Port field values of the Call ID table as a key value.
  • FIG. 32 illustrates an example of a unitary message completed for deleting field values of the Call ID table and RTP table.
  • FIG. 33 is a flow chart illustrating a field value deleting operation of the Call ID table and RTP table of the message processing module.
  • FIG. 34 illustrates examples of a Call ID table and an RTP table from which a field value is deleted.
  • the message processing module 270 may check whether the Call ID value included in the unitary message (UM_2) exists in the second user information table (Call ID Table), and delete the second user information table (Call ID Table) if the Call ID value exists in the second user information table (Call ID Table). That is, the message processing module 270 may search the Call ID Table by using the Call ID value, search the RTP table, delete the corresponding field value of the RTP table, and delete the corresponding field value of the Call ID table by using the Call ID table information.
  • FIG. 35 illustrates an example of a unitary message completed for updating the field value of the Call ID table.
  • FIG. 36 is a flow chart illustrating a field value updating operation of the Call ID table of the message processing module.
  • FIG. 37 illustrates an example of a Call ID table in which a field value is updated.
  • the message processing module 270 may check whether the Call ID value included in the unitary message (UM_2) exists in the second user information table (Call ID Table), and update the corresponding user information if the Call ID value exists in the second user information table (Call ID Table).
  • FIG. 35 and FIG. 36 illustrate an operation of the message processing module 270 for updating a Timestamp field value. If the Call ID value exists in the second user information table (Call ID Table), the message processing module 270 may update the Timestamp field value of the second user information table (Call ID Table).
  • FIG. 38 is flow chart illustrating an operation of checking the Timestamp field value and deleting the user information table by the message processing module.
  • FIG. 39 illustrates an example of the user information table from which a field value is deleted.
  • the message processing module 270 may search an RTP table, delete the corresponding field value of the RTP table, and delete the corresponding field value of the Call ID table by using the Call ID table information, Since then, the message processing module 270 may be maintained at a standby state again.
  • the message processing module 270 may repeat the above-described operation so as to delete the corresponding field value of the RTP table and Call ID table when a table standby state ends.
  • the packet analysis unit 200 may check the system operation mode information D7 so as to operate in a static policy mode or a real-time policy mode.
  • the static policy mode (or default mode) makes an inquiry about a detection/blocking policy in the third storage unit DB3 during an initial system operation, and maintains the inquired detection/blocking policy until the system operation is paused.
  • the real-time policy mode makes an inquiry about the detection/blocking policy in the third storage DB3 on a specific time basis set in the packet analysis unit 200, and checks whether the detection/blocking policy has changed and operates by reflecting the change if the detection/blocking policy has changed.
  • the packet analysis result management unit 300 may receive the packet analysis result information D4 from the packet analysis unit 200 and extract user information through a user information extraction module.
  • the packet analysis result management unit 300 may makes an inquiry about a packet transmission user in the first storage unit DB1. Furthermore, the packet analysis result management unit 300 may transmit the detection/blocking result information D6 to the fourth storage unit DB4 through an analysis result storage module.
  • the system management unit 400 may monitor the state of the system through a traffic input/output status. Furthermore, the system management unit 400 may monitor the state of the system by using information such as a CPU utilization rate and a memory utilization rate as well as the traffic input/output status. A system monitoring module may make an inquiry about a traffic input/output status in the NIC 10, and monitor the state of the system through the traffic input/output status. Furthermore, the system monitoring module may transmit the traffic input/output status information D8 to the system communication unit 500. A system control module may control a system operation mode according to the monitoring result of the system monitoring module. That is, the system control module may set the system operation mode to an IPS mode or a BYPASS mode. The system control module may transmit the system operation mode information D7 to the second storage unit DB2.
  • the system communication unit 500 may include a system management message analysis module, a policy management message analysis module, a detection/blocking log inquiry message analysis module, a GUI protocol analysis module, an external system linked protocol analysis module and the like.
  • the system management message analysis module may be linked to the second storage unit DB2 so as to make an inquiry about system operation mode information, and analyze a system management message for setting a system operation mode.
  • the policy management message analysis module may linked to the third storage unit DB2 so as to make an inquiry about a detection/blocking policy, and analyze a policy management message for setting a detection/blocking policy of the system.
  • the detection/blocking log inquiry message analysis module may be linked to the fourth storage DB4 so as to make an inquiry about a detection/blocking log, and analyze a detection/blocking log inquiry message for inquiring a detection/blocking log of the system.
  • the GUI protocol analysis module may be linked to a GUI so as to analyze a GUI protocol which is input to control the system.
  • the external system linked protocol analysis module may be linked to an external system so as to analyze an external system linked protocol which is input to set up the detection/blocking policy.
  • FIG. 40 illustrates a structure of a 4G network to which the VoLTE session management apparatus according to the present inventive concept is applied.
  • a 4G network 1000 may include 4G Enterprise Radio Access Network (E-RAN) which manages a radio resource and 4G Evolved Packet Core (EPC) which performs data processing/authentication/charging and the like.
  • E-RAN 4G Enterprise Radio Access Network
  • EPC Evolved Packet Core
  • the 4G E-RAN may include user equipment 1100 and eNB 1200.
  • the user equipment 1100 may be a portable terminal subscribed to a 4G network.
  • the eNB 1200 may be a base station for providing a radio connection between the user equipment 1100 and the 4G network.
  • the 4G EPC may include an MME(1300), a S-GW(1400), a P-GW(1500), a Home Subscriber Server (HSS) 1600, and a Policy & Charging Rule Function (PCRF) 1700.
  • the MME 1300 may transmit/receive a GTP packet to/from the eNB 1200 through a S1-MME GTP tunnel.
  • the S-GW 1400 may transmit/receive a GTP packet to/from the eNB 1200 through a S1-U GTP tunnel.
  • the MME 1300 may transmit/receive a GTP packet to/from the S-GW 1400 through a S11 GTP tunnel.
  • the P-GW 1500 may be connected to a P-CSCF 2100 of an IMS network and Internet.
  • the S1-U GTP tunnel may be a path for data traffic
  • the S11 GTP tunnel may be a path for signaling
  • the S5 GTP tunnel may be a path for data traffic and signaling in the 4G network.
  • the system including the VoLTE session management apparatus described with reference to FIG. 1 to FIG. 39 may be provided to a point P1 between the eNB 1200 and the MME 1300 and a point P2 between the MME 1300 and the S-GW 1400, or to a point P3 between the S-GW 1400 and the P-GW 1500. Furthermore, the system including the session management apparatus described with reference to FIG. 1 to FIG. 39 may be provided to an internal component of the S-GW 1400 or the P-GW 1500. Although not clearly shown in FIG. 40, the 4G network may be linked to a 3G network, a femtocell network and the like through the S-GW 1400.
  • FIG. 41 illustrates a structure of an IMS network linked to the 4G network of FIG. 40.
  • an IMS network 2000 may include a P-CSCF 2100, an I-CSCF 2200, an S-CSCF 2300, a Border Gateway Control Function (BGCF) 2400, an HSS 2500, a Media Gateway Control Function (MGCF) 2700, an Application Server (AS) 2800, a Media Gateway (M-GW) 2900.
  • BGCF Border Gateway Control Function
  • HSS HSS 2500
  • MGCF Media Gateway Control Function
  • AS Application Server
  • M-GW Media Gateway
  • the SIP message transmitted from the user equipment 1100 in the 4G network may be transferred into the IMS network through the P-GW 1500.
  • the P-CSCF 2100 connected to the P-GW 1500 may transmit the SIP message to the I-CSCF 2200, and the I-CSCF 2200 may transmit the SIP message to the S-CSCF 2300.
  • the MGCF 2700 and the M-GW 2900 may be connected to a public switching telephone network (PSTN).
  • PSTN public switching telephone network
  • FIG. 42 is a flow chart illustrating the VoLTE session management method according to an embodiment of the present inventive concept.
  • the VoLTE session management method may first receive a GTP packet and classify the received GTP packet into a GTP-U packet and a GTP-C packet (S100), and extract packet information from the GTP-U packet (S110).
  • the VoLTE session management method may analyze the message type (Msg Type_2) from the packet information (S120), create or delete the first user information table (Regi Table) or create, update or delete the second user information table (Call ID Table) according to the message type (Msg Type_2) (S130).
  • the first user information table (Regi Table) may include information regarding an equipment registration
  • the second user information table (Call ID Table) may include information regarding call ID.
  • creating a new user information table may check whether the MSISDN value included in the unitary message (UM_2) exists in the first user information table (Regi Table), and delete an existing user information table and create a new user information table if the MSISDN value exists. If the MSISDN value does not exist in the first user information table (Regi Table), the existing user information table may not be deleted, and a new user information table may be generated.
  • deleting an existing user information table may check whether the MSISDN value included in the unitary message (UM_2) exists in the first user information table (Regi Table), and delete the first user information table (Regi Table) if the MSISDN value exists in the first user information table (Regi Table).
  • creating an RTP table may check whether the Call ID value included in the unitary message (UM_2) exists in the second user information table (Call ID Table), delete an existing user information table if the Call ID value exists in the second user information table (Call ID Table), create a new Call ID table, and create a new RTP table with the calling UE IP and calling UE RTP Port field values of the Call ID table as a key value.
  • the existing user information table may not be deleted, a new Call ID table may be created, and a new RTP table may be created with the calling UE IP and calling UE RTP Port field values of the Call ID table as a key value.
  • deleting a Call ID table may check whether the Call ID value included in the unitary message (UM_2) exists in the second user information table(Call ID Table), and delete the second user information table(Call ID table) if the Call ID value exists in the second user information table (Call ID Table). That is, the Call ID table may be searched by using the Call ID value, the RTP table may be searched by using information of the Call ID table, the corresponding field value of the RTP table may be deleted, and the corresponding field value of the Call ID table may be deleted.
  • updating a Call ID table may check whether the Call ID value included in the unitary message (UM_2) exists in the second user information table (Call ID Table), and update the corresponding user information if the Call ID value exists in the second user information table (Call ID Table).
  • the steps of the method or algorithm described with regard to the embodiments of the present inventive concept may be directly implemented with a hardware module, a software module or a combination thereof executed by a processor.
  • the software module may reside in a RAM, a flash memory, a ROM, an EPROM, an EEPROM, a register, a hard disk, a removable disk, a CD-ROM, or a computer-readable recording medium having an arbitrary form widely known in the art to which the present inventive concept pertains.
  • An exemplary recording medium may be connected to the processor, and the processor may read information from the recording medium and write information onto the recording medium. Alternatively, the recording medium may be integrated with the processor.
  • the processor and the recording medium may reside in an application specific integrated circuit (ASIC).
  • the ASIC may reside in user equipment.
  • the processor and the recording medium may reside as a discrete component in user equipment.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Computer Security & Cryptography (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

L'invention concerne un appareil de gestion de sessions VoLTE comprenant une unité de gestion de paquet qui reçoit un paquet GTP et classifie le paquet GTP en un paquet GTP-U et un paquet GTP-C, et extrait des informations de paquet du paquet GTP-U, une unité d'analyse de paquet qui reçoit les informations de paquet et analyse un type de message compris dans les informations de paquet, et une unité de base de données qui stocke des première et deuxième tables d'informations d'utilisateurs, l'unité d'analyse de paquet créant ou supprimant la première table d'informations d'utilisateurs, ou créant, mettant à jour ou supprimant la deuxième table d'informations d'utilisateurs en fonction du type de message.
PCT/KR2015/011934 2015-01-16 2015-11-06 Appareil et procédé de gestion de sessions volte dans un réseau mobile 4g WO2016114476A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR1020150007831A KR101534160B1 (ko) 2015-01-16 2015-01-16 4G 모바일 네트워크에서의 VoLTE 세션 관리 장치 및 방법
KR10-2015-0007831 2015-01-16

Publications (1)

Publication Number Publication Date
WO2016114476A1 true WO2016114476A1 (fr) 2016-07-21

Family

ID=53875973

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2015/011934 WO2016114476A1 (fr) 2015-01-16 2015-11-06 Appareil et procédé de gestion de sessions volte dans un réseau mobile 4g

Country Status (2)

Country Link
KR (1) KR101534160B1 (fr)
WO (1) WO2016114476A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108243057A (zh) * 2016-12-27 2018-07-03 中国移动通信集团浙江有限公司 一种VoLTE转化率分析方法及系统

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101785680B1 (ko) * 2015-12-28 2017-10-16 한국인터넷진흥원 4g 모바일 네트워크에서의 rtp 터널링 패킷 탐지 장치, 시스템 및 방법
KR102116307B1 (ko) * 2019-11-26 2020-05-29 한국인터넷진흥원 이동 통신망에서의 diameter 프로토콜 idr 메시지 스푸핑 공격 탐지 방법 및 그 장치

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20100120823A (ko) * 2009-05-07 2010-11-17 충남대학교산학협력단 플로우 데이터를 이용한 ＶｏＩＰ 응용 이상 트래픽 탐지 방법
KR101388628B1 (ko) * 2013-11-07 2014-04-24 한국인터넷진흥원 4g 이동통신망에서의 비정상 트래픽 차단 방법
KR101388627B1 (ko) * 2013-11-07 2014-04-24 한국인터넷진흥원 4g 이동통신망에서의 비정상 트래픽 차단 장치
KR101414231B1 (ko) * 2013-08-28 2014-07-01 한국인터넷진흥원 비정상 호 탐지 장치 및 방법
KR101418967B1 (ko) * 2012-11-30 2014-07-15 한국인터넷진흥원 이동통신망에서 사용자 세션 관리 방법

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20100120823A (ko) * 2009-05-07 2010-11-17 충남대학교산학협력단 플로우 데이터를 이용한 ＶｏＩＰ 응용 이상 트래픽 탐지 방법
KR101418967B1 (ko) * 2012-11-30 2014-07-15 한국인터넷진흥원 이동통신망에서 사용자 세션 관리 방법
KR101414231B1 (ko) * 2013-08-28 2014-07-01 한국인터넷진흥원 비정상 호 탐지 장치 및 방법
KR101388628B1 (ko) * 2013-11-07 2014-04-24 한국인터넷진흥원 4g 이동통신망에서의 비정상 트래픽 차단 방법
KR101388627B1 (ko) * 2013-11-07 2014-04-24 한국인터넷진흥원 4g 이동통신망에서의 비정상 트래픽 차단 장치

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108243057A (zh) * 2016-12-27 2018-07-03 中国移动通信集团浙江有限公司 一种VoLTE转化率分析方法及系统

Also Published As

Publication number Publication date
KR101534160B1 (ko) 2015-07-24

Similar Documents

Publication Publication Date Title
WO2015030458A1 (fr) Appareil et procédé pour détecter un appel anormal
WO2017161883A1 (fr) Procédé et dispositif de traitement de transmission de données, et terminal
WO2013063897A1 (fr) Procédé et dispositif de remplissage d'identité fixe d'abonné
WO2016114476A1 (fr) Appareil et procédé de gestion de sessions volte dans un réseau mobile 4g
WO2012044085A2 (fr) Perfectionnement de commandes attention
EP2499757A2 (fr) Procédé et système de support de continuité d'appel radio vidéo unique pendant un transfert
WO2011160300A1 (fr) Procédé, appareil et système de mise en œuvre d'une diffusion groupée
WO2021012489A1 (fr) Procédé d'interrogation de journal de plateforme téléphonique, dispositif terminal, support de stockage et appareil
WO2017007122A1 (fr) Procédé et système de fourniture de service de réseau privé
WO2020077832A1 (fr) Procédé, appareil et dispositif d'accès à un bureau dans le nuage et support de stockage
WO2019109957A1 (fr) Procédé, appareil, et dispositif de fourniture de service basé sur un bus de service d'entreprise (esb), et support d'informations lisible
WO2016013718A1 (fr) Système et procédé permettant de fournir une publicité en ligne au moyen d'un réseau wi-fi
WO2016123898A1 (fr) Procédé de gestion de message court et terminal mobile associé
WO2021072881A1 (fr) Procédé, appareil et dispositif de traitement de demande fondée sur un stockage d'objet, et support de stockage
WO2016098997A1 (fr) Appareil, système et procédé de détection de message d'enregistrement volte anormal dans un réseau mobile 4g
WO2018128226A1 (fr) Procédé de transmission de contenu sur un réseau hétérogène et appareil associé
WO2012047074A2 (fr) Procédés et appareil pour obtenir un service
WO2010047458A1 (fr) Systeme et procede de transmission efficace de donnees durant un jeu d'equipe dans un environnement cpns, et serveur cpns, terminal de communications mobile, et terminal de point d'extremite associe
WO2022086000A1 (fr) Dispositif nœud d'accès sans fil et procédé d'interface mis en œuvre par un dispositif nœud d'accès sans fil
WO2016068475A1 (fr) Appareil et procédé de gestion de session d'utilisateur dans un réseau mobile 4g
WO2017054598A1 (fr) Procédé d'enregistrement de réseau et terminal mobile
KR101388627B1 (ko) 4g 이동통신망에서의 비정상 트래픽 차단 장치
WO2021012490A1 (fr) Procédé et appareil de commutation de relais de service, dispositif terminal, et support d'informations
WO2020042482A1 (fr) Procédé, appareil et dispositif de traitement de service d'agent, et support de stockage lisible par ordinateur
WO2013176431A1 (fr) Système et procédé pour allouer un serveur à un serveur et pour une messagerie efficace

Legal Events

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

Ref document number: 15878120

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15878120

Country of ref document: EP

Kind code of ref document: A1