Secured map messages for telecommunications networks

[0001] This application claims the priority and benefit of U.S. Provisional Patent Application Ser. No. 60/231,581, filed Sep. 11, 2000, which is incorporated herein by reference in its entirety.

BACKGROUND

[0002] 1. Field of the Invention

[0003] The present invention pertains to mobile telecommunications, and particularly to providing security for mobile telecommunications transmissions.

[0004] 2. Related Art and other Considerations

[0005] In a typical cellular radio system, mobile user equipment units (UEs) communicate via a radio access network (RAN) to one or more core networks. The user equipment units (UEs) can be mobile stations such as mobile telephones (“cellular” telephones) and laptops with mobile termination, and thus can be, for example, portable, pocket, hand-held, computer-included, or car-mounted mobile devices which communicate voice and/or data with radio access network.

[0006] The radio access network (RAN) covers a geographical area which is divided into cell areas, with each cell area being served by a base station. A cell is a geographical area where radio coverage is provided by the radio base station equipment at a base station site. Each cell is identified by a unique identity, which is broadcast in the cell. The base stations communicate over the air interface (e.g., radio frequencies) with the user equipment units (UE) within range of the base stations. In the radio access network, several base stations are typically connected (e.g., by landlines or microwave) to a radio network controller (RNC). The radio network controller, also sometimes termed a base station controller (BSC), supervises and coordinates various activities of the plural base stations connected thereto. The radio network controllers are typically connected to one or more core networks.

[0007] One example of a radio access network is the Universal Mobile Telecommunications (UMTS) Terrestrial Radio Access Network (UTRAN). The UTRAN is a third generation system which in some respects builds upon the radio access technology known as Global System for Mobile communications (GSM) developed in Europe. UTRAN is essentially a wideband code division multiple access (W-CDMA) system. The Third Generation Partnership Project (3GPP) has undertaken to evolve further the UTRAN and GSM-based radio access network technologies.

[0008] In actuality, mobile telecommunications coverage for an area, e.g., a large region or country, may be provided by plural mobile telecommunication operators, each having their own radio access network with the nodes (e.g., network elements) including as those described above, for example. The plural mobile telecommunication operators (e.g., mobile telecommunications companies) must cooperate and communicate with one another to provide for their customers/subscriber services which span networks. For example, subscribers of a first network operated by one operator must be able to place/receive calls with subscribers of a second network maintained by a second operator. Moreover, the subscribers of the first network to be provided with coverage even when in the second network. Such communication and cooperation is effected, at least in part, by signaling between the network operators. Some of this signaling involves usage of the MAP (Mobile Application Part) protocol.

[0009] As the migration towards the third generation of mobile networks nears, the security of signaling traffic between the networks of different operators grows in importance. The third generation (3G) network signaling faces a diverse threat situation. The added computational power, the increasing number of operators on the market, and the new technologies available for potential intruders are all factors that contribute to the threat scene that the third generation signaling networks face.

[0010] What is needed, therefore, and an object of the present invention, is technique and/or method for securing the signaling traffic between network elements in different operators' networks, thereby preventing illegitimate uses of such information as the MAP (Mobile Application Part) protocol, for example.

BRIEF SUMMARY OF THE INVENTION

[0011] An encrypted/authenticated mobile application part (MAP) protocol message is sent between a first network element of a first telecommunications network and a second network element of a second telecommunications network. The first network element uses a master security association to derive a connection-specific security association, and includes in the encrypted/authenticated MAP message a parameter obtained from the connection-specific security association. Upon receipt at the second network element, the master security association is used to derive a connection-specific security association for use by the second network element. The second network element uses the connection-specific security association to decrypt/decode the MAP message.

[0012] The master security association is a set of security parameters that includes at least one of the following: (1) an authentication algorithm; (2) authentication keying material; (3) an encryption algorithm; (4) encryption keying material; and, (5) a lifetime value for the master security association. In one mode of the invention, the master security association is negotiated between a key administration center of the first telecommunications network and a key administration center of the second telecommunications network, preferably over an Internet Protocol network using an Internet Key Exchange Protocol (IKE). In the illustrated embodiment, the MAP message is sent over another network, e.g., a Signaling System No. 7 network.

[0013] In one embodiment of the invention, the first network element requests the master security association from the key administration center of the first telecommunications network and, if necessary, the second network element requests the master security association from the key administration center of the second telecommunications network. In an illustrated embodiment, at least one of these requests is performed utilizing an Internet Protocol.

[0014] The connection-specific security association is a set of security parameters that comprises security information that is required in order to extract protected information from the MAP message. In an illustrated embodiment, the parameter(s) included in the MAP message are a Security Parameters Index (SPI) and a network identifier, which are preferably included in a MAP Security Header. The Security Parameters Index (SPI) in conjunction with the sending network identifier (PLMNID) can be used to identify a master security association.

BRIEF DESCRIPTION OF THE DRAWINGS

[0015] The foregoing and other objects, features, and advantages of the invention will be apparent from the following more particular description of preferred embodiments as illustrated in the accompanying drawings in which reference characters refer to the same parts throughout the various views. The drawings are not necessarily to scale, emphasis instead being placed upon illustrating the principles of the invention.

[0016]FIG. 1 is a schematic view of telecommunication networks which transmit secure MAP messages according to an example mode of the present invention.

[0017]FIG. 2 is a diagrammatic representation of a portion of a key administration center (KAC) including in the telecommunication networks of FIG. 1.

[0018]FIG. 3 is a diagrammatic representation of a portion of a network element (NE) including in the telecommunication networks of FIG. 1.

[0019]FIG. 4 is a diagrammatic view of certain interfaces involved for implementing the present invention in the telecommunication networks of FIG. 1.

[0020]FIG. 5 is a diagrammatic view of a MAP Security Header utilized for a MAP message which implements an aspect of the present invention.

[0021]FIG. 6 is a flow diagram showing certain example actions involved in basic key negotiation between key administration centers of the telecommunication networks of FIG. 1 in accordance with a mode of the present invention.

[0022]FIG. 7A and FIG. 7B are diagrammatic views respectively showing a main mode and an aggressive mode of first phase security association.

[0023]FIG. 8A, FIG. 8B, and FIG. 8C are diagrammatic views respectively showing a quick mode, a new group mode, and a IKE MAP mode of second phase security association.

[0024]FIG. 9 is a diagrammatic view of example structure of a KAC-Z_C-SADB database.

[0025]FIG. 10 diagrammatic view showing a procedure for deriving MAP SAs from a master MAP SA.

DETAILED DESCRIPTION OF THE DRAWINGS

[0026] In the following description, for purposes of explanation and not limitation, specific details are set forth such as particular architectures, interfaces, techniques, etc. in order to provide a thorough understanding of the present invention. However, it will be apparent to those skilled in the art that the present invention may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well known devices, circuits, and methods are omitted so as not to obscure the description of the present invention with unnecessary detail.

Architecture Overview

[0027] In order to illustrate certain basic aspects of the present invention, FIG. 1 shows two example, representative telecommunication networks <b>40</b>A and <b>40</b>B. The two example telecommunication networks <b>40</b>A and <b>40</b>B can be (and likely are) maintained and operated by different network operators (e.g., different telecommunications companies). Each telecommunication network 40 is comprised of at least one (and likely) numerous network elements (NEs) <b>42</b>, and further for the purposes of the present invention includes a functionality known as the key administration center (KAC) <b>44</b>. Specifically, telecommunication network <b>40</b>A has network element (NE) <b>42</b>A and key administration center (KAC) <b>44</b>A. Similarly, telecommunication network <b>40</b>B has network elements (NE) <b>42</b>₁B and <b>42</b>₂B, as well as key administration center (KAC) <b>44</b>B. With each telecommunication network <b>40</b>, the key administration center (KAC) <b>44</b> communicates with the network elements (NEs) <b>42</b> of the network over an interface labeled as the Zb interface.

[0028] The key administration centers (KACs) <b>44</b> of the various telecommunication networks <b>40</b> perform certain communications as hereinafter described over a first network, such as IP Network <b>46</b>. The interface over which the key administration centers (KACs) <b>44</b> is referenced herein as the Za interface.

[0029] The network elements (NEs) <b>42</b> of the various telecommunication network <b>40</b> also communicate with one another, but over a second network such as (for example) the signaling system no. 7 (SS7) network <b>48</b>. The interface over which the network elements (NEs) <b>42</b> of the various telecommunication network <b>40</b> communicate key is referenced herein as the Zc interface.

[0030] One aspect of the present invention particularly concerns a key management architecture, such as that shown in FIG. 1, that is used in a key exchange procedure to ensure secure transport of MAP (Mobile Application Part) messages. The key administration centers (KAC) <b>44</b> negotiate (e.g., over the Za interface) certain master MAP Security Associations (SAs). These master MAP Security Associations (SAs) are in turn used by network elements (NEs) <b>42</b> to create MAP-protecting security associations, also known as connection-specific MAP SAs. These MAP-protecting security associations or connection-specific MAP SAs are the actual MAP SAs that are used to protect the MAP signaling messages to and from other NEs in the same network or with NEs in another network.

[0031] MAP SAs, which include both master MAP SAs and connection-specific MAP SAs (used between NEs), are unidirectional so that separate security associations (Sas) are created for both directions of communication. A connection-specific MAP SAs is a unidirectional set of security parameters. A connection-specific MAP SA specifies the protection mode, it's parameters, and the cryptographic keys used in the communication between two nodes. A connection-specific MAP SA remains active until its lifetime (as defined by the master MAP SA expires).

[0032] A security association is identified by a Security Parameters Index (SPI) value together with the sending network's PLMNID. An Security Parameters Index (SPI) is an arbitrary 32-bit number that is assigned to a security association when the security association is created. An address for the destination network is thus a PLMNID, which consists of MCC and MNC.

Operational Overview

[0033] Describing certain operational aspects of the invention in brief, the key administration center (KAC) <b>44</b> of a network <b>40</b> negotiates a master MAP SA with each network specified by the network operator. Thus, although only two telecommunication networks <b>40</b> are illustrated in FIG. 1, it should be understand that likely each telecommunication network <b>40</b> will be connected via IP Network <b>46</b> with several other telecommunication networks <b>40</b>, and therefore there will be several master MAP SAs (one for each network) in each key administration center (KAC) <b>44</b>. These negotiated master MAP SAs are stored in at each key administration center (KAC) <b>44</b>. In the illustrated embodiment, these negotiated master MAP SAs are stored in a database referenced herein as the KAC-Z_C-SADB database (Key Administration Center, Interface Z_C, Security Association Database). FIG. 1 shows, as action <b>1</b>-<b>0</b>, the key administration center (KAC) <b>44</b>A and the key administration center (KAC) <b>44</b>B negotiating master MAP SAs.

[0034] When a network element (NE) wishes to communicate with another network element (NE), either in the home network or in a foreign operator's network, the network element (NE) first fetches a master MAP SA from the KAC-Z_C-SADB database of its key administration center (KAC). FIG. 1 shows as action <b>1</b>-<b>1</b> network element (NE) <b>42</b>A fetching (requesting and receiving) a master MAP SA from key administration center (KAC) <b>44</b>A. The network element (NE) then uses this master MAP SA to create a connection specific MAP SA. In this regard, action <b>1</b>-<b>2</b> shows network element (NE) <b>42</b>A generation a connection specific MAP SA. This connection specific MAP SA is used to secure all MAP traffic between the communicating nodes. In particular, using the connection specific MAP SA, the sending network element (NE) [network element (NE) <b>42</b>A] sends a protected MAP message to a responding network element (NE) [network element (NE) <b>42</b>B], as depicted by action <b>4</b>-<b>3</b>. The responding network element (NE) recognizes the protected message by a certain field included in the secured MAP message, in particular a security parameter index (SPI) described subsequently with respect to FIG. 5 (see action <b>1</b>-<b>4</b> in FIG. 1). Then, the responding network element (NE) obtains the corresponding master MAP SA from KAC-Z_C-SADB database. In the FIG. 1 example, action <b>1</b>-<b>5</b> represents network element (NE) <b>42</b>B obtaining the corresponding master MAP SA from KAC-Z_C-SADB database of key administration center (KAC) <b>44</b>B. The responding network element (NE) <b>42</b> then uses the master MAP SA to derive the connection specific MAP SA (illustrated by action <b>1</b>-<b>6</b> in FIG. 1).

Key Administration Center (KAC)

[0035] As mentioned above, there is a key administration center (KAC) <b>44</b> in every network that supports the key management architecture of the present invention. As shown in FIG. 2, a key administration center (KAC) <b>44</b> includes a internet key exchange functionality <b>44</b>-<b>1</b>; an IPsec policy engine <b>44</b>-<b>2</b>; and a certificate management interface <b>44</b>-<b>3</b>. In addition, the key administration center (KAC) <b>44</b> has the following databases: KAC-Zb-SPD database <b>44</b>-<b>4</b>, KAC-Zb-SADB database <b>44</b>-<b>5</b>, KAC-Za-SPD database <b>44</b>-<b>6</b>, and KAC-Z_C-SADB database <b>44</b>-<b>7</b>. Of these, KAC-Zb-SPD database <b>44</b>-<b>4</b> and KAC-Za-SPD database <b>44</b>-<b>6</b> are logically distinct databases which collectively form a security policy database (SPD). The security policy database (SPD) defines the data protection policy; the traffic to be allowed or denied; and, who is allowed to use network resources.

[0036] The IPsec policy engine <b>44</b>-<b>2</b> allows or disallows packets inbound or outbound according to currently loaded security policy as defined in IPsec policy engine <b>44</b>-<b>2</b> and certificate management interface <b>44</b>-<b>3</b>. The certificate management interface <b>44</b>-<b>3</b> is used, e.g., to show that IKE/IPsec can be easily extended to support public key infrastructures (PKIs). X.509 certificates are a scalable solution for verifying the identity of the other end of the transmission

[0037] The key administration center (KAC) <b>44</b> performs various functionalities. For example, a key administration center (KAC) <b>44</b> performs the master MAP SA negotiation with key administration centers (KACs) <b>44</b> of different networks, as alluded to above with reference to action <b>1</b>-<b>0</b>. Master MAP SA negotiation is done using IKE (Internet Key Exchange). A master MAP SA is negotiated on demand (i.e. when a network element (NE) <b>42</b> sends a request for a master MAP SA to the key administration center (KAC) <b>44</b>). In addition, the key administration center (KAC) <b>44</b> maintains the KAC-Z_C-SADB database <b>44</b>-<b>7</b> that stores the negotiated Master MAP SAs. Further, the key administration center (KAC) <b>44</b> performs SA re-keying (the refreshing of master MAP SA) by maintaining a lifetime counter for each master MAP SA. After the master MAP SA has been negotiated, the internet key exchange functionality <b>44</b>-<b>1</b> of the key administration center (KAC) <b>44</b> returns the MAP SA to IPsec Policy Engine (IPE) <b>44</b>-<b>2</b>, which stores the negotiated master MAP SA to KAC-Z_C-SADB database <b>44</b>-<b>7</b>. Yet further, the key administration center (KAC) <b>44</b> provides the network elements (NEs) <b>42</b> with access to KAC-Z_C-SADB database <b>44</b>-<b>7</b> in order to fetch a valid master MAP SA for a communication. Moreover, the key administration center (KAC) <b>44</b> manages and maintains a secure IP connection from the key administration center (KAC) <b>44</b> to the network elements (NEs) <b>42</b> (over the Zb interface). The IPsec/IKE provides security for the Zb interface.

Network Element (NE)

[0038] As illustrated in FIG. 3, the network elements (NE) <b>42</b> that support the key management architecture of the present invention includes an internet key exchange functionality <b>42</b>-<b>1</b>; an IPsec policy engine <b>42</b>-<b>2</b>; and a certificate management interface <b>42</b>-<b>3</b>. In addition, the key administration center (KAC) <b>44</b> has the following databases: NE-Zb-SPD database <b>42</b>-<b>4</b>, NE-Zb-SADB database <b>42</b>-<b>5</b>, and NE-Z_C-SADB database <b>42</b>-<b>7</b>.

[0039] The network element (NE) <b>42</b> performs various functionalities. For example, the network element (NE) <b>42</b> generates secure a MAP message as defined in the MAP SA (that is derived from the master MAP SA retrieved from KAC-Z_C-SADB database <b>44</b>-<b>7</b>). The network element (NE) <b>42</b> maintains NE-Z_C-SADB database <b>42</b>-<b>7</b> to contain the valid MAP SAs that are derived from the master MAP SA retrieved from KAC-Z_C-SADB database <b>44</b>-<b>7</b>. Moreover, the network element (NE) <b>42</b> NE maintains a lifetime timer for each MAP SA stored in NE-Z_C-SADB database <b>42</b>-<b>7</b>. In this regard, the MAP SA lifetimes are defined by the master MAP SA received from the key administration center (KAC) <b>44</b>. The network element (NE) <b>42</b> manages the expiry of MAP SAs as dictated by their lifetimes. Optionally, the network element (NE) <b>42</b> performs IKE negotiation and establishes protected IP connections (IPsec) with the home network key administration center (KAC) <b>44</b>. On the responding end, a network element (NE) <b>42</b> calculates a connection specific MAP SA from the master MAP SAs (as alluded to with respect to action <b>1</b>-<b>6</b> in FIG. 1). Moreover, the network element (NE) <b>42</b> NE maintains a connection specific replay prevention counter for each NE-to-NE connection (over the Zc interface).

Interfaces

[0040]FIG. 4 and Table 1 show in more detail aspects of certain interfaces involved in the present invention. The key management architecture for MAPSec defines three interfaces: Za, Zb and Zc.

[0041] Interface Za can be, for example, over an IP network (e.g., IP Network <b>46</b> in FIG. 1). The key administration centers (KACs) <b>44</b> in different networks use IKE over interface Za to negotiate the master MAP SAs. The master MAP SA IKE is negotiated under the MAPSec domain of interpretation (DoI) for ISAKMP, as described subsequently. The key administration centers (KACs) <b>44</b> can also perform IKE negotiations to create IPsec SAs under IPsec domain of interpretation for ISAKMP to protect other communications between key administration centers (KACs) <b>44</b> or between a key administration center (KAC) <b>44</b> and other network elements (NEs) <b>42</b>.

[0042] Interface Zb can also be, by way of example, over an IP network. IKE, IPsec and HTTP are protocols used over the interface Zb. The key administration center (KAC) <b>44</b> and network elements (NEs) <b>42</b> perform master MAP SA delivery over the Zb interface. The network elements (NEs) <b>42</b> use HTTP to access the KAC-Z_C-SADB database <b>44</b>-<b>7</b> to obtain the master MAP SAs. This procedure must be protected with IPsec. Before a network element (NE) <b>42</b> accesses KAC-Z_C-SADB database <b>44</b>-<b>7</b>, its internet key exchange functionality <b>42</b>-<b>1</b>(IKE) negotiates IPsec SA for the connection. After this negotiation all HTTP operations are protected with IPsec according to the policy defined by the operator.

[0043] In the illustrated embodiment, interface Zc is over an SS7 (network 48 of FIG. 1 as an example second network). MAPSec is used to protect MAP messages (such as message <b>1</b>-<b>3</b>) over the Zc interface. As reflected by action <b>1</b>-<b>6</b> in FIG. 1, the master MAP SA fetched over the interface Zb is be used to derive a connection specific MAP SA that defines the security parameters of the MAPSec traffic.

Map Security Header of Map Message

[0044] As indicated above, when a MAP message such as MAP message <b>1</b>-<b>3</b> of FIG. 1 is transmitted between two network elements (NEs) <b>42</b>, in accordance with the present invention a MAP Security Header is added to secure or protect the MAP message. The MAP Security Header carries information that is required by a receiving entity in order to extract the protected information from a securely transported MAP message

[0045] An example format of one embodiment of a MAP Security Header <b>50</b> is shown in FIG. 5. The MAP Security Header <b>50</b> includes the following fields or information elements: initialization vector (IV) <b>5</b>-<b>1</b>; replay counter <b>5</b>-<b>2</b>; security parameter index (SPI) <b>5</b>-<b>3</b>; and, sending PLMNID <b>5</b>-<b>4</b>. Each of these fields/information elements are discussed subsequently below.

[0046] The initialization vector (IV) <b>5</b>-<b>1</b> is used with block ciphers in a certain mode known as the chained mode to force an identical plaintext to encrypt to different cipher texts. Using initialization vectors (IVs) prevents launching a codebook attack against encrypted traffic. With stream cipher algorithms, an initialization vector (IV) is not used.

[0047] The replay counter <b>5</b>-<b>2</b> is used to prevent replay attacks against network elements (NEs) <b>42</b>. The replay counter <b>5</b>-<b>2</b> is a 32 bits integer that is used for keeping track of the messages that have been passed between a single NE-NE pair. The replay counter <b>5</b>-<b>2</b> counter must be incremented every time either network element (NE) <b>42</b> sends a MAP message to a peer. The replay counter <b>5</b>-<b>2</b> is initialized to zero when a MAP SAs is created. A new MAP SA must be created prior to the replay counter <b>5</b>-<b>2</b> reaches <b>2</b>Â<b>32</b>. Without replay counter <b>5</b>-<b>2</b>, an attacker may resend any previously sent MAP message to the recipient network element (NE) <b>42</b>. For example, an attacker could resend a Location Update message an hour after the original message was sent, causing erroneous location updates.

[0048] The security parameter index (SPI) <b>5</b>-<b>3</b> is an arbitrary value that is used in combination with sending PLMNID <b>5</b>-<b>4</b> to uniquely identify a master MAP SA. In one embodiment, the size of security parameter index (SPI) <b>5</b>-<b>3</b> is 32 bits. The security parameter index (SPI) <b>5</b>-<b>3</b> is used in the calculation of a value known as KEYMAT. The use of a security parameter index (SPI) <b>5</b>-<b>3</b> smaller than 32 bits decreases the randomness of KEYMAT. A 32 bit value of security parameter index (SPI) <b>5</b>-<b>3</b> enhances compatibility to other vendors' implementations.

[0049] The sending PLMNID <b>5</b>-<b>4</b> is the PLMNID for the sending network element (NE) <b>42</b>. PLMNID is the ID number of the sending Public Land Mobile Network (PLMN). The value for the PLMNID is formed from the Mobile Country Code (MCC) and Mobile Network Code (MNC) of the destination network. For example: (MCC+MNC)=244+91 for the Sonera mobile network in Finland.

Key Negotiation

[0050]FIG. 6 is a flow diagram showing, in more detail than FIG. 1, certain example steps involved in basic key negotiation between key administration centers of the telecommunication networks of FIG. 1 in accordance with a mode of the present invention. FIG. 6 also describes the MAPSec procedure, and illustrates a PULL procedure for obtaining a MAP SA for a network element.

[0051] At step <b>6</b>-<b>1</b>, network element (NE) <b>42</b>A requests a master MAP SA from key administration center (KAC) <b>44</b>A to derive a MAP SA that defines security parameters for protected MAP traffic. Steps <b>6</b>-<b>2</b> through <b>6</b>-<b>7</b>, and steps <b>6</b>-<b>8</b> through <b>6</b>-<b>10</b>, are optional if a valid master MAP SA already exists in KAC-Z_C-SADB database <b>44</b>-<b>7</b>, but are described below for completeness. Steps <b>6</b>-<b>2</b> through <b>6</b>-<b>7</b> involve IKE phase 1 negotiation. In particular, for step <b>6</b>-<b>2</b> ISAKMP (described in more detail infra) establishes a secure authenticated channel for further negotiation traffic and defines the security association to be used during the negotiations. Steps <b>6</b>-<b>8</b> through <b>6</b>-<b>10</b> involve IKE phase 2 negotiation, with IKE negotiates a master MAP SA between two networks.

[0052] Step <b>6</b>-<b>11</b> of FIG. 6 shows key administration center (KAC) <b>44</b>A returning a valid master MAP SA in Master MAP SA Response message to network element (NE) <b>42</b>A. Then, as step <b>6</b>-<b>12</b>, network element (NE) <b>42</b>A uses the received master MAP SA to derive the MAP SA, which defines the security parameters to be used for protecting MAP traffic over the Zc interface. After deriving the security parameters, network element (NE) <b>42</b>A sends the encrypted (or authenticated MAP message depending on the MAP PP) to network element (NE) <b>42</b>B. The encrypted MAP message includes PLMNID and SPI values in the respective security parameter index (SPI) <b>5</b>-<b>3</b> and sending PLMNID <b>5</b>-<b>4</b> fields of MAP Security Header <b>50</b>.

[0053] As step <b>6</b>-<b>13</b>, the responding network element (NE) <b>42</b>B receives the encrypted MAP message. The MAPSec message is recognized, but no MAP SA exists in the NE-Z_C-SADB database <b>42</b>-<b>7</b> for network element (NE) <b>42</b>B. Therefore, <b>42</b>B sends a Master MAP SA Request to key administration center (KAC) <b>44</b>B. The request includes the PLMNID and SPI acquired from the MAP Security Header <b>50</b> of the received MAP message.

[0054] At step <b>6</b>-<b>14</b> key administration center (KAC) <b>44</b>B uses the received PLMNID and SPI values to index the master MAP SA in KAC-Z_C-SADB database <b>44</b>-<b>7</b> of key administration center (KAC) <b>44</b>B (see FIG. 2). The master MAP SA is previously negotiated, so it is uniquely identified with PLMNID and SPI in KAC-Z_C-SADB database <b>44</b>-<b>7</b>. The key administration center (KAC) <b>44</b>Bthen returns the master MAP SA to network element (NE) <b>42</b>B with a Master MAP SA Response message.

[0055] As step <b>6</b>-<b>15</b>, network element (NE) <b>42</b>B derives the connection specific MAP SA from the master MAP SA acquired from key administration center (KAC) <b>44</b>B. The received MAPSec message now can be processed and the response to the message can be generated according to the security parameters described in MAP SA.

[0056]FIG. 10 shows a procedure for deriving MAP SAs from a master MAP SA.

Map Security Associations

[0057] MAP security associations (MAP SAs) are used to define the security parameters used to protect the traffic over the Zc interface (e.g., over the SS7 network <b>48</b> in FIG. 1).

[0058] The master MAP SA is a unidirectional set of security parameters (the concept is analogous to IPsec SA). Master MAP SAs are negotiated between two key administration centers (KACs) <b>44</b>. A master MAP SA specifies the protection mode, it's parameters, and the cryptographic keying material used between two networks. The master MAP SA is created either during the start-up of the key administration center (KAC) <b>44</b> or after a network element (NE) <b>42</b> requests a master MAP SA for that network according to operator's policy.

[0059] Master MAP security association specifies the following parameters: Protection mode (e.g., No protection; Integrity and authentication; or Integrity, authentication and confidentiality); the authentication algorithm for integrity and authentication; the encryption algorithm for confidentiality; the encryption and authentication keying material; and the SA lifetime.

[0060] The master MAP SA lifetime should be selected according to various industry recommendations (e.g., recommendations of the IKE working group of IETF). The exact limit preferably depends on such factors as the chosen authentication or encryption algorithms.

[0061] It is currently preferred that the operation mode (e.g. ECB, CBC) be combined to algorithms and not defined as a separate parameter, thereby avoding configuration problems among other things.

[0062] A connection specific MAP SA is a unidirectional set of security parameters. MAP SA is created between two network elements (NEs) <b>42</b>. The connection specific MAP SA specifies the protection mode, it's parameters, and the cryptographic keys used between two hosts. A MAP security association is created when hosts communicate for the first time, and remains active until its lifetime expires. The MAP security association specifies the same parameters as the master MAP SA, with inclusion of the following distinctions (1) an encryption key generated from the master MAP SA keying material and from network element's SS7 identity of initiator and responder; and (2) an authentication algorithm key (integrity key) generated as encryption key.

[0063] It is currently preferred that the final key material be generated according to the following expression:

<i>F_KEYMAT=</i><i>PRF</i>(SKEYID_—<i>d</i>, KEYMAT|LOCAL_ID|REMOTE_ID)

[0064] wherein:

[0065] F_KEYMAT is the final keying material.

[0066] PRF is a pseudo-random function.

[0067] SKEYID_d is used to derive keying material for MAPSec. SKEYID_d is derived as described in RFC 2409 The Internet Key Exchange (IKE).

[0068] KEYMAT is the keying material from master MAP SA. KEYMAT is derived as described in RFC 2409 The Internet Key Exchange (IKE).

[0069] LOCAL_ID is the local SS7 identity of the initiating NE.

[0070] REMOTE_ID is the SS7 identity of the responding NE.

[0071] From the point of view of an IPsec implementation, a security association is a data structure that determines the transformation that is to be applied to an IP packet, and method of how it should be applied. The security association specifies the following parameters: (1) an authentication algorithm for AH and ESP protocols; (2) an encryption algorithm for ESP protocol; (3) encryption and authentication keys; (4) the lifetime of the security association in bytes; (4) the lifetime of the security association in seconds; and (5) a replay prevention counter sequence number.

[0072] Concerning differences between IPsec SAs and MAP SAs, a MAP SA does not have a limit on the amount of traffic after which the MAP SA expires. This is due to several peers using the same master MAP SA simultaneously. The fact that the master MAP SAs are shared by many network elements (NEs) <b>42</b> makes the counting of the amount of traffic an extremely complex and heavy operation.

[0073] The lifetime of encryption keys is not defined in MAP SA. The encryption keys are re-keyed every time the master MAP SA needs to be refreshed.

Trust Distribution for IKE

[0074] To guarantee the trust distribution for IKE, certificates can be used. Certificates provide authentication, integrity and confidentiality in the communication and are scalable solution to trust distribution.

Authentication and Encryption Algorithms

[0075] In one example embodiment, a single algorithm is used for authentication and a single algorithm is used for encryption. Usage of single algorithms for authentication and encryption tend to speed up standardization and simplify the implementation. Preferably, a Secure Hash Algorithm (SHA), version one, is used for authentication and a Twofish is used for encryption. The Secure Hash Algorithm (SHA), version one, was was designed by NSA, and is part of the U.S. Digital Signature Standard. Twofish is a AES (Advanced Encryption Standard) candidate created by Bruce Schneier et al

Internet Key Exchange

[0076] Before a secure session begins, the communicating parties need to negotiate the terms for the communication. These terms are the ones that are defined in the security association (SA). In order to make the process feasible in a global network like the Internet, there needs to be an automated protocol for establishing the security associations. This automated protocol is the Internet Key Exchange Protocol (IKE), also known as ISAKMP/Oakley (Internet Security Association and Key Management Protocol combined with the Oakley key exchange).

[0077] The Internet Key Exchange (IKE) protocol is the standard protocol for negotiating the security mechanisms to be used between two hosts. It securely produces random short-term session keys for the hosts and authenticates the hosts either using shared secrets (passwords), or cryptographically using certificates. IKE combines the Internet Security Association and Key Management Protocol (ISAKMP) with the Oakley key exchange. ISAKMP is a framework for creating connection-specific parameters while Oakley is the actual instance of the ISAKMP framework for IPsec key and security association generation.

[0078] The Internet Key Exchange (IKE) key negotiation and exchange works in two phases. During the first phase, ISAKMP establishes a secure authenticated channel for further negotiation traffic and defines the security association to be used during the negotiations. During the second phase, it negotiates a security association to be used by IPsec. Although the first phase is time consuming, in the final result is time saving; after the first phase negotiations have been performed once, the more frequent second phase negotiations can then be performed faster.

[0079] The first phase security association can be established using one of two available modes: Main Mode (illustrated in FIG. 7A) and Aggressive Mode (illustrated in FIG. 7B). The Aggressive Mode is a little faster, but typically it does not protect the identities of the negotiating nodes.

[0080] The second phase can be established using Quick Mode (illustrated in FIG. 8A), as the initial negotiations have already taken place. In addition, New Group Mode (illustrated in FIG. 8B)can be used to negotiate a new group (MODP or elliptic curve) that is used to perform a Diffie-Hellman exchange.

[0081] In the Main Mode illustrated in FIG. 7A, the negotiating parties use the first two messages <b>7</b>A-<b>1</b> and <b>7</b>A-<b>2</b> to negotiate the security policy for the exchange. They then use the next two messages <b>7</b>A-<b>3</b> and <b>7</b>A-<b>4</b> to perform a Diffie-Hellman key exchange and pass nonces to each other. The last two messages <b>7</b>A-<b>5</b> and <b>7</b>A-<b>6</b> are used to authenticate the parties using signatures or hashes and optional certificates. The Diffie-Hellman key exchange algorithm allows two parties to agree on a shared value without requiring encryption. The shared value is immediately available for use in encrypting subsequent conversations such as a data transmission or authentication.

[0082] The Aggressive Mode of FIG. 7B resembles Main Mode, but fewer packet exchanges are needed. The first message <b>7</b>B-<b>1</b> proposes the security policy, passes data for the key exchange and passes the nonce for identification. The second message <b>7</b>B-<b>2</b> is a response that authenticates the responder and concludes the policy negotiation and key exchange. The last message <b>7</b>B-<b>3</b> is used to authenticate the initiator. Aggressive mode does not protect the identities of negotiators.

[0083] The Quick Mode of FIG. 8A is used to negotiate IPsec security services and to generate new keying material. A full Diffie-Hellman key exchange can be done to provide perfect forward secrecy, although it is not mandated. If a Diffie-Hellman exchange is not needed, the parties can just generate a new key using hashes and identify each other by using nonces. If a Diffie-Hellman key exchange is needed, the new keying material is included in the exchange.

[0084] The New Group Mode of FIG. 8B is used to negotiate a new group (MODP or elliptic curve) where to do Diffie-Hellman exchange.

[0085]FIG. 7A is based on authentication by using signatures. The payloads are slightly different when other authentication methods are used. The main difference is that the signature is replaced by a has.

[0086] In FIG. 7A, FIG. 7B, FIG. 8A, and FIG. 8B, various abbreviations have been employed. “SA” refers to the negotiated security association. “Header” is an ISAKMP header corresponding to the used mode. “KE” is key exchange data for Diffie-Hellman key exchange. “Sig” is signature payload used for authentication. “Cert” is a certificate for the public key. “Nonce” is a random number sent for signing. “ID” is an identity payload. “[ ]” denotes an optional payload.

[0087] The functionality of IKE is not altered when IKE is extended to master MAP SA negotiation capabilities. A new Phase 2 (a new “quick mode”) called MAP mode implements the new MAPSec functionality. Changes involved in the new quick mode are described below.

[0088] After the IKE MAP mode finishes, IKE returns the master MAP SA to IPE. IPE stores the negotiated master MAP SA to KAC-Z_C-SADB. Whenever key administration center (KAC) <b>44</b> notices that the soft limit of a master MAP SA is exceeded, the master MAP SA is refreshed according to the operator's policy that is described in KAC-Z_A-SPD as described herein.

[0089] In Phase 1 there is no changes to main mode, but it is currently preferred that only main mode be used under MAPSec DoI of ISAKMP.

[0090] A new Phase 2 mode—the MAP mode—is introduced. The MAP mode, illustrated in FIG. 8C, differs from the existing IKE quick mode in the following respects: (1) payloads included to the messages of MAP mode are the same as in Quick Mode but the contents of the payloads differ in the case SA payload and ID payloads; (2) either the identity is never sent or if sent it will be the PLMDID in fqdn or der_gn encoded form (or the key_id); (3) KEYMAT for MAPSec SA template is as in the present Quick mode.

Mapsec Domain of Interpretation for ISAKMP

[0091] RFC2408: ISAKMP places the following significant requirements on a DoI definition: (1) Define the interpretation for the Situation field; (2) Define the set of applicable security policies; (3) Define the syntax for DoI-specific SA Attributes (Phase II); (4) Define the syntax for DoI-specific payload contents; (5) Define additional Key Exchange types, if necessary; (6) Define additional Notification Message types, if needed.

[0092] IANA will not normally assign a DoI value without referencing some public specification, such as an Internet RFC. Without a DoI value assigned by IANA, the MAP SA negotiation over the interface Za is not possible. MAPSec DoI for ISAKMP draft must be written, since the new DoI is an essential part of the key management architecture described herein.

[0093] Within ISAKMP, the MAPSec Situation Definition provides information that the responder can use to determine, how to process incoming SA request. For the MAPSec DoI, the Situation field is always left empty. The MAPSec DoI does not impose specific security policy requirements on any implementation.

[0094] The following list the Assigned Numbers for the MAPSec DoI: protocol identifiers and transform identifiers.

[0095] MAPSec Protocol Identifier defines a value for the Security Protocol Identifier referenced in an ISAKMP Proposal Payload for the MAPSec DoI. See Table 2. It is preferred that the chosen value should not overlap existing IPsec DoI values.

[0096] The MAPSec Transform Identifier defines one mandatory transform used to provide data confidentiality. See Table 3.

[0097] MAPSec Payload Content require inclusion of both the Security association payload and the Identification payload. MAPSec DoI does not introduce additional MAPSec Key Exchange Requirements

Policies and Structure of KAC-Z

A

-SPD

[0098] Policies and Structure of KAC-Z_A-SPD are as described as in the RFC 2401 with following changes:

[0099] (1) The lifetime of the master MAP SA is not defined as an amount of data transferred, but as lifetime in seconds. The lifetime cannot be defined in amount of data transferred, since several NEs will use the same master MAP SA.

[0100] (2) The generated master MAP SA will not be used for processing inbound and outbound traffic in KACs and thus processing choices discard, bypass IPsec and apply IPsec are no applicable.

[0101] (3) The operator defines which networks the master MAP SAs are negotiated with.

[0102] The security policies for MAPSec key management are specified in the KACs' security policy database (SPD) by the network operator. The SPDs in the network elements are derived from the security policy database (SPD) of the key administration center (KAC) <b>44</b> in the network. There can be no local security policy definitions for individual network elements (NEs) <b>42</b>.

[0103] The security policy database (SPD) can be implemented as a text file to ease the porting to different systems. Text-file based implementation is also easier to alter by possible third parties than a GUI interface. The security policy database (SPD) file contains the information required to implement the security policy and does not require a lot of memory. It can be easily cached to improve the performance of the system (real time requirements).

Storing Negotiated MAP SA

[0104] After internet key exchange functionality <b>44</b>-<b>1</b> has finished the negotiation of master MAP SA, the negotiated master MAP SA is returned to internet key exchange functionality <b>44</b>-<b>1</b>. The internet key exchange functionality <b>44</b>-<b>1</b> will store the negotiated master MAP SA to KAC-Z_C-SADB database <b>44</b>-<b>7</b>, from where all authorized network elements (NEs) <b>42</b> can obtain an appropriate master MAP SA. The internet key exchange functionality <b>44</b>-<b>1</b> always returns a DoI value with the negotiated SA. This DoI value can be used to identify the negotiated SA. If the DoI value returned by internet key exchange functionality <b>44</b>-<b>1</b> corresponds to IPsec DoI for ISAKMP, the negotiated SA is an IPsec SA. If the DoI value corresponds to MAPSec DoI for ISAKMP, the negotiated SA is a MAP SA. According to the DoI value, SAs will be stored in the correct SADB.

[0105] After the key administration center (KAC) <b>44</b> has negotiated a master MAP SA pair, the key administration center (KAC) <b>44</b> stores the master MAP SAs in an HTTP server or an LDAP directory. Master MAP SAs must be stored in a way that they can be found using the remote network PLMNID and the SPI value of the master MAP SA. The structure of the KAC-Z_C-SADB database <b>44</b>-<b>7</b> that is currently preferred is illustrated in FIG. 9.

[0106] The key administration center (KAC) <b>44</b> must delete expired SAs from the server. When the lifetime of an SA ends or a soft limit of SA is reached (as defined in the operator's policy) the key administration center (KAC) <b>44</b> may negotiate a new master MAP SA with the destination network and insert it into the database (in which case it must delete the old SA). The network element (NE) <b>42</b> may keep the SA it has fetched and use it until the lifetime of that SA ends.

Distribution MAP SA Over Interface Zb

[0107] When a network element (NE) <b>42</b> needs to communicate with a foreign network element (NE) <b>42</b> in a different network, the initiating NE always needs to perform a query to KAC-Z_C-SADB database <b>44</b>-<b>7</b> to obtain a master MAP SA for the connection. The initiating <b>42</b> uses the destination network's PLMNID to identify the recipient network. The key administration center (KAC) <b>44</b> returns a master MAP SA negotiated with the network identified by the destination PLMNID. The query to KAC-Z_C-SADB database <b>44</b>-<b>7</b> is done using HTTP or LDAP.

[0108] If the initiating network element (NE) <b>42</b> gets a valid master MAP SA it can derive a connection specific MAP SA from the master and continue to secure the MAP traffic using this MAP SA.

[0109] When a responding network element (NE) <b>42</b> receives a protected MAP message, the responding network element (NE) <b>42</b> first performs a query to KAC-Z_C-SADB database <b>44</b>-<b>7</b> of its key administration center (KAC) <b>44</b> to obtain the corresponding master MAP SA. The master MAP SAs are identified using tuple &lt;sending PLMNID, SPI&gt;. After receiving the corresponding master MAP SA from the key administration center (KAC) 44, the responding key administration center (KAC) <b>44</b> derives the connection specific MAP SA from the master and can continue processing the received MAP messages.

[0110] If the responding NE's query for a matching master MAP SA is not responded with a correct master MAP SA that corresponds to the &lt;sending PLMNID, SPI&gt;, the responding NE must drop the received MAP message.

[0111] If the responding party is receiving secured MAP messages, but no MAP SAs exists for the corresponding Security Parameters Index (SPI), the MAP messages could be used, for example, to perform Denial of Service (DoS) attack against a network element (NE) <b>42</b> over the SS7 network.

[0112] If no master MAP SA exists for the requested network the NE must send “master MAP SA request” message to key administration center (KAC) <b>44</b>. When the key administration center (KAC) <b>44</b> receives a “master MAP SA request”, it must negotiate a new master MAP SA with the corresponding network and send “master MAP SA created response” message back to the network element (NE) <b>42</b>.

[0113] All KAC-Z_C-SADB databases <b>44</b>-<b>7</b> mentioned above refer to the KAC-Z_C-SADB databases <b>44</b>-<b>7</b> of the home network of the network element (NE) <b>42</b> that originates the communication. It must not be possible to access the key administration center (KAC) <b>44</b> of a foreign network to obtain MAP SAs.

[0114] The network elements (NEs) <b>42</b> will need the master MAP SA from the key administration center (KAC) <b>44</b> to be able to connect to network elements (NEs) <b>42</b> in a separate network. When a network element (NE) <b>42</b> requires a SS7 connection to another network element (NE) <b>42</b>, it will fetch a master MAP SA from the key administration center (KAC) <b>44</b>. This is done with a query to the key administration center (KAC) <b>44</b>. The query returns the master MAP SA to be used for securing the connection.

[0115] There are are two protocols that can be used for distributing the master MAP SAs from the KAC-Z_C-SADB database <b>44</b>-<b>7</b> to individual network elements. The first protocol is the Hypertext transfer protocol (HTTP), the second protocol is the Lightweight Directory Access Protocol (LDAP).

[0116] HTTP is a generic, stateless, object-oriented protocol that can be used for many tasks, such as name servers and distributed object management systems. In context of the key management architecture presented in this document HTTP can be used as the key distribution protocol between network elements (NEs) <b>42</b> and their KAC-Z_C-SADB databases <b>44</b>-<b>7</b>. A feature of HTTP is the typing and negotiation of data representation, allowing systems to be built independently of the data being transferred. When HTTP is used as the protocol between KAC-Z_C-SADB database <b>44</b>-<b>7</b> and network elements (NEs) <b>42</b>, the HTTP connection should be secured with the IPsec protocol. The secure HTTP connection between the KAC-Z_C-SADB database <b>44</b>-<b>7</b> and each network element (NE) <b>42</b> remains persistent if a valid IPsec SA exists for the connection at all times. Persistent connections improve the performance (the real time requirements) of data transfer by sharing a single IPsec SA between several HTTP requests. In practice the key administration center (KAC) <b>44</b> should run a HTTP server that the network elements (NEs) <b>42</b> can connect to retrieve the master MAP SAs from a standard HTTP database.

[0117] Lightweight Directory Access Protocol (LDAP) is a simple protocol used to access, modify and add data to and from a directory server. It allows basic searching, adding, modifying, and deleting operations. It does not provide real user authentication, but uses simple plain text name and password based authentication. Because of this, it is normally only used to search and retrieve data from the directory server. In this case, a network element (NE) <b>42</b> will only make searches to the directory. When using LDAP to fetch master MAP SA from the key administration center (KAC) <b>44</b> there will be a need for strong security between each key administration center (KAC) <b>44</b> and network element (NE) <b>42</b>, which can be achieved by IPsec, IKE and certificates. Certificates provide a scalable and easy to maintain solution for authentication of the hosts involved.

[0118] It is currently preferred that the access method to be used for the distribution of master MAP SAs from the KAC to the network elements be HTTP. This is due to the simplicity and scalability of the solution. HTTP is a proven, well-known and thoroughly researched protocol. Different implementations for HTTP servers are readily available on the market today.

[0119] It is currently preferred that the MAP SA distribution method selected be protected with the IPsec protocol. Each NE has a certificate that is used for authenticating the host requesting information from the HTTP/LDAP server. IPsec is a very thorough and complete solution for the problems it tries to address, namely protecting IP traffic on the packet level. It can protect all traffic against unauthorized modification and eavesdropping, as well as securely authenticate the parties that are communicating with each other. It is an exact match for securing host-to-host communications such as the connection from network elements to the Key Administration Center.

[0120] It is currently preferred that the lifetime of IPsec SA between network element (NE) <b>42</b> and key administration center (KAC) <b>44</b> be relatively long in seconds but small in bytes to ensure maximal performance and security.

[0121] Table 4 list various abbreviations, terms, and acronyms employed herein.

[0122] In a first alternative embodiment, the Zb interface comprises running IPsec without IKE in order to (A) provide security for the transport of SAs from the key administration center (KAC) <b>44</b> to the network element (NE) <b>42</b>; (B) requires no complete IKE implementation or computations from the network elements (NEs) <b>42</b>.

[0123] In a second alternative embodiment, the Zb interface comprises the RSA encryption of the SAs sent by the key administration center (KAC) <b>44</b> to the network element (NE) <b>42</b>. This enables each network element (NE) <b>42</b> to decrypt the messages using its own private key, while the key administration center (KAC) <b>44</b> uses the public key of the network element (NE) <b>42</b> to encrypt. Communication from the network element (NE) <b>42</b> back to the key administration center (KAC) <b>44</b> uses the public-private key pair of the key administration center (KAC) <b>44</b> in a similar fashion. This method avoids the use of IPSec and IKE altogether on the network elements (NEs) <b>42</b>, and all security can be implemented solely on the application layer.

[0124] While the invention has been described in connection with what is presently considered to be the most practical and preferred embodiment, it is to be understood that the invention is not to be limited to the disclosed embodiment, but on the contrary, is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims. <tables id="TABLE-US-00001" num="1"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="center" /><thead><row><entry namest="1" nameend="1" align="center">TABLE 1</entry></row></thead><tbody valign="top"><row><entry /></row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row><row><entry>Summary of used protocols in each interface</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="49PT" align="left" /><colspec colname="2" colwidth="56PT" align="left" /><colspec colname="3" colwidth="98PT" align="left" /><tbody valign="top"><row><entry /><entry>Interface</entry><entry>Protocol(s)</entry><entry>Explanation</entry></row><row><entry /><entry namest="OFFSET" nameend="3" align="center" rowsep="1" /></row><row><entry /><entry>Za</entry><entry>IKE</entry><entry>IKE is used to negotiate the</entry></row><row><entry /><entry /><entry /><entry>master MAP SA. MAP SA</entry></row><row><entry /><entry /><entry /><entry>requires a new domain of</entry></row><row><entry /><entry /><entry /><entry>interpretation for ISAKMP.</entry></row><row><entry /><entry>Zb</entry><entry>IKE</entry><entry>IKE is used to negotiate</entry></row><row><entry /><entry /><entry>IPsec</entry><entry>IPsec SA between KAC and</entry></row><row><entry /><entry /><entry>HTTP</entry><entry>NE. IPsec is used to secure</entry></row><row><entry /><entry /><entry /><entry>the transfer of MAP SA.</entry></row><row><entry /><entry /><entry /><entry>HTTP is used to fetch the</entry></row><row><entry /><entry /><entry /><entry>MAP SAs from KAC-Z_C-</entry></row><row><entry /><entry /><entry /><entry>SADB.</entry></row><row><entry /><entry>Zc</entry><entry>MAPSec</entry><entry>Master MAP SA negotiated</entry></row><row><entry /><entry /><entry /><entry>through interface Z_Ais used</entry></row><row><entry /><entry /><entry /><entry>to derive MAP SA that</entry></row><row><entry /><entry /><entry /><entry>defines the security</entry></row><row><entry /><entry /><entry /><entry>parameters used in MAPSec.</entry></row><row><entry /><entry namest="OFFSET" nameend="3" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

[0125]<tables id="TABLE-US-00002" num="2"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="3"><colspec colname="OFFSET" colwidth="42PT" align="left" /><colspec colname="1" colwidth="63PT" align="left" /><colspec colname="2" colwidth="112PT" align="center" /><thead><row><entry /><entry namest="OFFSET" nameend="2" align="center">TABLE 2</entry></row><row><entry /><entry /></row><row><entry /><entry namest="OFFSET" nameend="2" align="center" rowsep="1" /></row><row><entry /><entry>Protocol ID</entry><entry>Value</entry></row><row><entry /><entry namest="OFFSET" nameend="2" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry /><entry>PROTO_MAPSEC</entry><entry>5</entry></row><row><entry /><entry namest="OFFSET" nameend="2" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

[0126]<tables id="TABLE-US-00003" num="3"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="3"><colspec colname="OFFSET" colwidth="42PT" align="left" /><colspec colname="1" colwidth="70PT" align="left" /><colspec colname="2" colwidth="105PT" align="center" /><thead><row><entry /><entry namest="OFFSET" nameend="2" align="center">TABLE 3</entry></row><row><entry /><entry /></row><row><entry /><entry namest="OFFSET" nameend="2" align="center" rowsep="1" /></row><row><entry /><entry>Transform ID</entry><entry>Value</entry></row><row><entry /><entry namest="OFFSET" nameend="2" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry /><entry>RESERVED</entry><entry>0</entry></row><row><entry /><entry>MAPSEC_SHA1</entry><entry>1</entry></row><row><entry /><entry>MAPSEC_TWOFISH</entry><entry>2</entry></row><row><entry /><entry namest="OFFSET" nameend="2" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

[0127]<tables id="TABLE-US-00004" num="4"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="1" colwidth="42PT" align="left" /><colspec colname="2" colwidth="175PT" align="left" /><thead><row><entry namest="1" nameend="2" align="center">TABLE 4</entry></row><row><entry /></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row><row><entry>Term or</entry><entry /></row><row><entry>Acronym</entry><entry>Explanation</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry>AES</entry><entry>Advanced Encryption Standard</entry></row><row><entry>AH</entry><entry>Authentication Header. An upper level header</entry></row><row><entry /><entry>located between the IP header and a payload within an IP</entry></row><row><entry /><entry>packet. The AH transformation is defined in RFC 2402.</entry></row><row><entry>CA</entry><entry>Certification Authority. An entity that attests to the</entry></row><row><entry /><entry>identity of a person or an organization. A CA can be an</entry></row><row><entry /><entry>external company that offers certificate services or it can</entry></row><row><entry /><entry>be an internal organization such as a corporate</entry></row><row><entry /><entry>Management Information System (MIS) department. The</entry></row><row><entry /><entry>chief function of the CA is to verify the identity of entities</entry></row><row><entry /><entry>and issue digital certificates attesting to that identity.</entry></row><row><entry>Diffie-</entry><entry>A method for key exchange between two parties.</entry></row><row><entry>Hellman</entry></row><row><entry>DoI</entry><entry>Domain of Interpretation</entry></row><row><entry>DoS</entry><entry>Denial of Service</entry></row><row><entry>ESP</entry><entry>Encapsulating Security Payload. An upper level IP</entry></row><row><entry /><entry>header that denotes that the contents of the payload are</entry></row><row><entry /><entry>encrypted and possibly also otherwise protected. An ESP</entry></row><row><entry /><entry>may also contain integrity protection. The ESP protocol is</entry></row><row><entry /><entry>defined in RFC 2406.</entry></row><row><entry>IANA</entry><entry>Internet Assigned Numbers Authority</entry></row><row><entry>IKE</entry><entry>Internet Key Exchange</entry></row><row><entry>IP</entry><entry>Internet Protocol</entry></row><row><entry>IPE</entry><entry>IPsec Policy Engine</entry></row><row><entry>IPsec</entry><entry>IP security protocol</entry></row><row><entry>ISAKMP</entry><entry>Internet Security Association and Key</entry></row><row><entry /><entry>management Protocol</entry></row><row><entry>IV</entry><entry>Initialization vector. Initialization vectors are used</entry></row><row><entry /><entry>with block ciphers in chained mode to force identical</entry></row><row><entry /><entry>plaintext to encrypt to different cipher text. Usually</entry></row><row><entry /><entry>random data to make each block unique by filling the</entry></row><row><entry /><entry>cipher feedback registers.</entry></row><row><entry>KAC</entry><entry>Key Administration Center</entry></row><row><entry>KEYMAT</entry><entry>Keying material from master MAP SA. KEYMAT</entry></row><row><entry /><entry>is derived as described in RFC 2409 The Internet Key</entry></row><row><entry /><entry>Exchange (IKE).</entry></row><row><entry>LDAP</entry><entry>Lightweight Directory Access Protocol, as defined</entry></row><row><entry /><entry>by RFC 2251, and RFC 1777.</entry></row><row><entry>MAP</entry><entry>Mobile Application Part (a part of the SS7 protocol</entry></row><row><entry /><entry>stack)</entry></row><row><entry>MAPSec</entry><entry>MAP Security</entry></row><row><entry>MCC</entry><entry>Mobile Country Code</entry></row><row><entry>MNC</entry><entry>Mobile Network Code, a number to differentiate</entry></row><row><entry /><entry>different networks within one country</entry></row><row><entry>NE</entry><entry>Network Element</entry></row><row><entry>NE-Z_C-</entry><entry>A database maintained by each NE supporting</entry></row><row><entry>SADB</entry><entry>MAPSec. The NE-Z_C-SADB contains the MAP SAs that</entry></row><row><entry /><entry>are derived from the master MAP SAs.</entry></row><row><entry>PLMNID</entry><entry>Public Land Mobile Network ID</entry></row><row><entry>SA</entry><entry>Security Association. A unidirectional connection</entry></row><row><entry /><entry>created for security purposes. All traffic traversing an SA</entry></row><row><entry /><entry>is provided the same security processing.</entry></row><row><entry>SADB</entry><entry>Security Association Database</entry></row><row><entry>SHA-1</entry><entry>The Secure Hash Algorithm (SHA), version one.</entry></row><row><entry /><entry>The algorithm was designed by NSA (the U.S. National</entry></row><row><entry /><entry>Security Agency), and is part of the U.S. Digital Signature</entry></row><row><entry /><entry>Standard. This algorithm is considered very good.</entry></row><row><entry>SPD</entry><entry>Security Policy Database</entry></row><row><entry>SPI</entry><entry>Security Parameters Index. An arbitrary 32-bit</entry></row><row><entry /><entry>number that is assigned to a SA.</entry></row><row><entry>SS7</entry><entry>Signaling System no. 7</entry></row><row><entry>TCP</entry><entry>Transmission Control Protocol</entry></row><row><entry>URI</entry><entry>Universal Resource Indicator</entry></row><row><entry>Z_A</entry><entry>Interface between two KACs over an IP network</entry></row><row><entry>Z_B</entry><entry>Interface between KAC and NE inside the</entry></row><row><entry /><entry>operator's (presumably) IP network</entry></row><row><entry>Z_C</entry><entry>Interface between two NEs over SS7 network</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>