KR100846868B1 - Method for managing tls session in supl based location information system - Google Patents

Abstract

In the present invention, when a SET roams from an H-SLP to a V-SLP and receives location information service from the V-SLP in a SUPL-based location information system, a hand shortened without creating a new TLS session after roaming. Create a new TLS connection only with the Abbreviated Handshake. That is, in the present invention, when a TLS session is opened to secure the security in a SUPL-based location tracking method, a new TLS session between a V-SLP (V-SPC) and a SET after opening a TLS session between an H-SLP and a SET, When you open it, you can reduce the overall system load by providing the V-SLP with the key information used in the previous TLS session.

Roaming, TLS Session, Position Measurement, SUPL, Key Information

Description

TLS session management method in SPL-based location information system {METHOD FOR MANAGING TLS SESSION IN SUPL BASED LOCATION INFORMATION SYSTEM}

1 is a view showing a location tracking procedure using SUPL when the SET roams.

2 is a diagram illustrating a method of performing a TLS session using a full handshake.

3 shows an extension of a TLS session for SUPL roaming.

4 is a diagram illustrating a TLS session management method according to a first embodiment of the present invention.

5 is a diagram illustrating a derivation process of encryption parameters.

6 illustrates transmission of a master secret when SUPL roaming.

7 is a diagram illustrating a transport relationship between roaming-master secrets

8 is a diagram illustrating a TLS session management method according to a second embodiment of the present invention.

The present invention relates to a location information system based on Secure User Plane Location (SUPL), and more particularly, to a TLS session management method for SUPL roaming.

In general, a mobile communication system includes a related function unit for calculating a location of a terminal in a mobile communication network to provide a location service that delivers a location of a terminal to a predetermined entity periodically or on request. have.

The network structure related to the location service is different depending on an internal network structure such as 3GPP or 3GPP2, and the method of calculating the position of the current terminal includes a cell-ID method for transmitting the ID of the cell to which the terminal belongs, from the terminal to each base station. After measuring the time that the radio wave is reached, there is a method of calculating the position of the terminal using triangulation and a method using GPS.

However, in order to provide the location service to a user, considerable signaling and location information must be transferred between the mobile terminal and the location server. Recently, standardized location technologies for providing location services, that is, location services based on the location of a mobile terminal, are rapidly spreading. The above technologies may be provided through a user plane and a control plane, and as an example of the technology, a secure user plane location (SUPL) providing a location service through the user plane is known. .

The SUPL is an efficient method of transmitting location information necessary for calculating the location of a mobile terminal. The SUPL is a user plane data bearer (PCB) for delivering location assistance information such as GPS assistance and carrying a location technology related protocol between the mobile terminal and the network. bearer).

In general, a SUPL network related to location services in a location information system includes a SUPL agent, a SULP Location Platform (SLP), and a SUPL enabled terminal (SET). The SUPL agent represents a logical service access point using actual measured location information, and the SLP represents a SUPL service access point of a network portion that accesses network resources to obtain location information. Also, SET is a device that can communicate with SUPL network using SUPL interface. For example, a user terminal (UMTS) of UMTS, mobile station (MS) of GSM, IS-95 MS or laptop with built-in SET function. Computer) or PDA (Personal Digital Assistants). In addition, the SET may be various mobile terminals connected through a wideband LAN (WLAN). The SET interworks with the network via a user plane bearer to support definition procedures in SUPL.

In addition, in the location information service, the network originally registered by the user is called a home network, and when the user moves and is located in an area other than the home network area, the network of the corresponding area is called a visited network. do. Thus, SLP in the home network is referred to as H-SLP (Home-SLP) and SLP in the visited network is referred to as V-SLP (Visited-SLP). In this case, when the SUPL procedure is started in the network, an SLP to which an external client first connects is called a requesting SLP (R-SLP), which may or may not be the same as an H-SLP as a logical entity. In addition, the SET that targets the current position tracking is defined as a target SET.

In addition, the SLP, which is a network element, is an SLC (SUPL Positioning Center) that is an entity that calculates actual position and an SLC that plays a role of SLP other than calculating position information, for example, roaming and resource management. SUPL Location Center). Accordingly, the SET calculates location information through communication with the SPC via SLC (Proxy mode), or calculates location information by directly accessing the SPC (Non-proxy mode).

However, in case of opening a transport layer security (TLS) session for securing security in the conventional location tracking method based on SUPL, in the case of non-proxy mode roaming, a TLS session is created after a V-SPC is created. When opening a new TLS session between the UE and the UE, a new TLS session must be created separately from the existing TLS session (between H-SLP and SET).

FIG. 1 is a diagram illustrating a procedure for performing location tracking using SUPL when a SET roams from an H-SLP to a V-SLP in a non-proxy mode. Hereinafter, the objective SET is abbreviated as SET.

Referring to FIG. 1, a SET (or a SUPL agent) may transmit a packet data network or a circuit switched network (3GPP or 3GPP2) when a data connection is not established in any network before transmitting a SUPL STRAT message. Network) to request a data connection (TCP connection) (S10).

Once the data connection is complete, the SET establishes a TLS session (encryption protocol) with the H-SLP (S11) and transmits a SUPL START message to the H-SLP to start the H-SLP and SUPL procedure (S12). The SUPL START message includes at least session-id, SET capabilities and lid (local identifier). The SET capabilities include a location tracking method supported by the SET (eg, SET supported A-GPS, a SET-based A-GPS, etc.) and a protocol to be used for location tracking (RRLP, RRC or TIA-801).

The H-SLP determines whether the SET is roaming based on routing information, and then, via the RLP SSRLIR (Standard SUPL Roaming Location Immediate Request), the SUPL START message including the session-id and msid to the V-SLC of the V-SLP. Pass (S13).

The V-SLC informs the V-SPC that the preparation of the SUPL POS procedure will be started through internal initialization with the V-SPC and exchanges necessary information. In addition, the V-SLC transmits a SUPL RESPONSE message including the address of the V-SPC to the H-SLP through an RLP SSRLIA (Standard SUPL Roaming Location Immediate Answer) (S14).

Accordingly, the H-SLP sends a SUPL RESPONSE message including at least the session-id and the address of the V-SPC to the SET (S15), and the SET terminates the IP connection with the H-SLP and the first TLS session. End (S16).

Thereafter, the SET establishes a second TLS session with the V-SPC (S17).

The procedure for setting up a second TLS session is basically the same as the procedure for setting up a first TLS session. When the second TLS session is established, the SET transmits a SUPL POS INIT message including session-id, lid and SET capabilities to the V-SPC to start the actual positioning procedure (S18). Accordingly, the SET and the V-SPC exchange successive messages for actual positioning (S19), so that the V-SPC (or SET) calculates the position of the SET through the message.

Once the position of the SET is calculated, the V-SPC sends a SUPL END message to the SET to inform the end of the SUPL procedure, and the SET receiving the SUPL END message ends the second TLS session with the V-SPC (S20, S21). ).

In addition, the V-SPC informs the V-SLC of the termination of the SUPL procedure and the calculated position value of the SET through internal communication (S22), and the V-SLC sends the received information to the RLP SSRP (Standard SUPL Roaming Position) message. Through the transmission to the H-SLP (S23).

After that, when the SET roams, the first and second TLS sessions will be described in detail.

FIG. 2 is a view showing in more detail a method (full handshake) for establishing a TLS session (the SET performs mutual authentication with the H-SLP and V-SLP) when the SET roams from the H-SLP to the V-SLP. to be.

As shown in Fig. 2, the SET first establishes a first TLS session (encryption protocol) with the H-SLP (S11).

That is, the SET transmits to the H-SLP including parameters such as Version, RandomNumber, sessionID [empty], CipherSuites, and CompressionMethod in the Client Hello message (ST1). Here, sessionID is set to empty when a new session is created, and CipherSuites and CompressionMethod indicate an ID of a list of encryption parameters supported by the SET and a data compression scheme.

In response to the Client Hello, the H-SLP transmits a Server Hello message including parameters such as Version, RandomNumber, sessionID [1], CipherSuites, and CompressionMethod selected by the H-SLP (ST2). If there is no session ID transmitted by the SET, the H-SLP transmits an empty session ID.

The H-SLP may sequentially transmit messages such as Certification *, ServerKeyExchange *, CertificateRequest *, and ServerHello Done to the SET after sending Server Hello. In this case, * indicates that it is optional.

The Certificate is a message transmitted after Server Hello, and the H-SLP transmits its public key through ServerKeyExchange or sends its public key and certificate authority's root certificate to the Certificate. Include in chain form and send.

The ServerKeyExchange is a message sent after the Certificate. The ServerKeyExchange includes the public key information of the H-SLP (server), and the exact information on the key information is in accordance with the corresponding public key algorithm (RSA, Diffie-Hellman). The Certificate Request is a message sent after the ServerKeyExchange. When the public key information of the SET is needed, the H-SLP is used for the certificate request. The ServerHello Done is a message transmitted after sending a certificate request and used to inform the SET of completion of initial negotiation.

When ServerHello Done is input from the H-SLP, the SET transmits a message such as Certificate, ClientKeyExchange and CertificateVerify *, ChangeCipherSpec and Finished to the H-SLP (ST3).

The ClientKeyExchange is a message transmitted after sending a certificate, and includes key information (Enc _{H - SLP _PK} (pre-master secret) encrypted with the public key of the H-SLP, which is used for the actual encryption in the H-SLP. It means the most basic pre-master secret for creating the keys (Integrity Key, Ciphering Key and Initialization Vector), and the key information is used for the Symmetric Encryption Algorithm.

CertificateVerify is a message sent after ClientKeyExchange, and indicates whether the SET owns the correct private key for the public key transmitted through the previous Certificate message, and the key information of the SET and the contents of the previous TLS handshake message are displayed. Contains a hashed and signed value.

Finally, the H-SLP transmits a ChangeCipherSpec and a Finished message sequentially to the SET, thereby completing all full handshake processes for establishing the first TLS session (ST4). The ChangeCipherSpec is a message transmitted after CertificateVerify and informs the time point of encryption after the negotiation of the H-SLP and the SET is completed, and the SET changes the TLS session state from a pending state to a current state. In addition, the Finished is a message transmitted after the ChangeCipherSpec, and indicates that the negotiation is completed successfully or that the security parameter is not damaged during the negotiation.

When the first TLS session is established by the above procedure, the SET sends a SUPL START message to the H-SLP to indicate the start of the SUPL procedure (S12), and the H-SLP determines the location information of the V-SLP to which the SET belongs. After recognizing the roaming of the SET, the SUPL START message is again transmitted to the V-SLC through the RLP SSRLIR message (S13).

The V-SLC informs the start of the SUPL procedure and exchanges necessary information through internal initialization with the V-SPC. In response to the RLP SSRLIR message, the V-SLC transfers the SUPL RESPONSE message including the address of the V-SPC to the H-SLP through the RLP SSRLIA message (S14), and the H-SLP sends the SUPL RESPONSE message. Send to SET.

Accordingly, the SET terminates the IP connection with the H-SLP and the first TLS session, and performs a step S17 for establishing a second TLS session with the V-SPC.

In other words, when a SET roams from H-SLP to V-SLP in SUPL-based location information system and receives location information service from a new location server (V-SPC), a new TLS session is created between the SET and V-SPC. Should be. In this case, parameters such as encryption, signature, and integrity check, which are set between the H-SLP and the SET, must be newly set.

However, the procedure for establishing a new (second) TLS session is the same as the procedure for establishing a first TLS session, as shown in FIG. In this case, the terminal first establishes a TLS session by H-SLP and full handshake for mutual authentication, and then, when roaming to V-SLP, a new TLS session by the same full handshake must be created. There is a disadvantage in that the time and resources required for authentication and encryption key exchange are increased.

Accordingly, an object of the present invention is to provide a TLS session management method that can increase the efficiency of TLS session establishment between the terminal and the V-SLP when SUPL roaming.

In order to achieve the above object, in roaming a Secure User Plane Location (SUPL) based location information system using TLS (Transport Layer Security), the TLS session management method according to the present invention, the terminal is H (Home) Establishing a TLS session with a SULP Location Platform (SLP) and transmitting SUPL START to the H-SLP; Transmitting, by the H-SLP, the set TLS session information to a V (Visited) -SLP roaming by the UE; Transmitting, by the H-SLP, information of the V-SLP to a terminal; The UE and the V-SLP establish a new TLS connection in the TLS session using the TLS session information.

Preferably, the TLS session information is a TLS session ID used when connecting the TLS session between the H-SLP and the terminal; Contains the master secret or roaming master secret that is key information for the TLS session.

Preferably, the TLS session information further includes a parameter indicating an encryption method and a compression method used when a TLS session is connected between the H-SLP and the terminal.

Preferably, the master secret generates a value obtained by concatenating a random value known between the pre-master secret and the UE and the H-SLP using a pseudo random function.

Preferably, the roaming master secret is generated by hashing the value of the master secret and the roaming count.

Preferably, the TLS session is characterized by being performed by a full handshake protocol.

Preferably, the new TLS connection is generated by an abbreviated handshake procedure.

Advantageously, when the new TLS connection is established, the V-SLP and the SET further perform a SPUL positioning procedure to calculate the SET position.

Preferably, the abbreviated handshake procedure may include: transmitting, by the SET, a Client Hello message including Version, SET-Random, and sessionID to the V-SPC; The V-SPC sequentially transmitting a Server Hello message including a Version, V-SLP-Random, sessionID, ChangeCipherSpec, and Finished as a SET; When the Finished message is input from the V-SPC, the SET sequentially transmits the ChangeCipherSpec and the Finished message to the V-SPC, thereby terminating the abbreviated handshake process.

Hereinafter, preferred embodiments of the present invention will be described in detail.

In the present invention, in the case of the SUPL-based location information system, when the SET roams from the H-SLP to the V-SLP and receives the location information service from the new location server (V-SPC), the SET and the H-SLP are already before roaming. We propose a method to perform authentication and cryptographic key exchange using TLS sessions generated between them.

That is, as shown in FIG. 3, when the SET having a TLS session with the H-SLP in the home network roams into a visited network, the TLS session established between the H-SLP and the SET is TLS between the V-SLP and the SET. Can be extended to sessions.

To this end, the present invention does not create a new TLS session when roaming, but only creates a new TLS connection in a TLS session created between the SET and the H-SLP using an abbreviated handshake protocol.

That is, in the present invention, after the SET terminates the TLS session with the H-SLP, the TLS session information is used to generate a new TLS connection without creating a new TLS session with the V-SPC. Reuse To this end, the H-SLP forwards the parameters used in the previous TLS session, the TLS session ID and the new key information (master secret or roaming master secret) in the RRL SSRLIR message to the V-SPC in the V-SLP.

Therefore, when the SET establishes a new TLS session, the empty session ID is transmitted to the H-SLP, and when only a new connection is created by using the previous TLS session, the SET uses the session ID of the V-SLP to be reused in the ClientHello message. Transmit to V-SPC. If the session ID sent by the SET cannot be found, the V-SLP sends an empty session ID to the SET with an error message, and if there is a matching session ID, the V-SPC and the SET use the ChangeCipherSpec using the Abbreviated Handshake protocol. Will be exchanged. When reusing a TLS session using the Abbreviated Handshake protocol, the existing session state is maintained as it is, and the TLS state is maintained by using the ChangeCihperSpec exchanged by H-SLP and SET.

4 illustrates a case of using a master secret between an H-SLP and a V-SLP as a method for managing a TLS session according to the first embodiment of the present invention.

First, H-SLP and V-SLP perform mutual authentication at the time of negotiating service support for the first time, and periodically validate Certificate Revocation List (CRL) or validate certificate through OCSP (Online Certificate Status Protocol). (S50). At this time, at least the H-SLP must authenticate the roamable V-SLP SET, and must have a certificate of a number of V-SLPs (V-SLPs).

In this state, the SET performs the first TLS session establishment procedure with the H-SLP (S51). During the procedure, the SET generates a pre-master secret and encrypts the generated pre-master secret with the public key of the H-SLP. Send to H-SLP [ Enc _{H - SLP _PK} (pre-master secret delivery)] (ST3). The pre-master secret represents an initial value required to generate a ciphering key used for encryption, an Integrity Key used for integrity verification, and an initialization initialization vector.

When the TLS session is established between the H-SLP and the SET, the SET transmits a SUPL START message to the H-SLP to start the H-SLP and SUPL procedures (S52), and the H-SLP belongs to the SET based on the routing information. The location information of the V-SLP is determined to recognize the roaming of the SET.

When the SET roams to the V-SLP, the H-SLP transfers TLS session information to the V-SLC through a SUPL START message, which is an RLP message (RLP SSRLIR) (S53), and the TLS session information performs internal communication. Is transmitted to the V-SPC. Here, the RLP message is transmitted in the form of an encrypted message through HTTPS (TLS). At this time, the parameter added to the RLP SSRLIR (START START) message is as follows.

master secret, sessionID , cipher Suites, compression methods: Used to extend the TLS session between the V-SLC and the SET.

Here, the master secret represents a pre-master secret (PRF), a SET master | V-SLP Random, and the sessionID is a number of a TLS session to be reused, that is, an initial TLS session connection between the H-SLP and the SET. Session number used at the time.

The V-SLP forwards an RLP SSRLIA (SUPL RESPONSE) including a sessionID and a V-SPC address to the H-SLP as a response (S54), and the H-SLP sends a SUPL RESPONSE message to the SET (SUPL sessionid, V- Send SPC address, etc.). That is, the H-SLP informs the SET of the SUPL session number and the server (V-SPC) that will receive the location service (S55).

Therefore, even if the previous TLS session is terminated, the SET generates a TLS connection using the handshake protocol abbreviated with the V-SPC based on the TLS session information used when establishing the TLS session between the first H-SLP and the SET. (S56).

That is, SET sends Client Hello message including parameters such as Version, SET-Random, sessionID [1] to V-SPC. As a response to the Client Hello, the V-SPC sends a Server Hello message including parameters such as Version, V-SLP-Random, and sessionID [1] to the SET, and then encrypts after the negotiation between the SET and the V-SPC ends. Send ChangeCipherSpec and Finished to indicate when to run.

When Finished is inputted from the V-SPC, the SET also sends a ChangeCipherSpec and Finished message to the V-SPC in order to complete all of the abbreviated handshake processes for establishing a TLS connection.

Accordingly, the SET and the V-SPC may derive the encryption parameters by using the exchanged parameters (SET-Random or V-SLP-Random) when performing the abbreviated handshake. The following functions (1) and (2) provided are used in the same way.

master secret = PRF (pre-master secret, "master secret", SET-Random | V-SLP-Random) -------------- (1)

-key material = PRF (master secret, "key expansion", V_ SLP -Random | SET-Random) ------------------ ( 2)

Here, the master secret and key expansion mean a string.

5 is a diagram illustrating a process of deriving encryption parameters in SET and V-SPC.

Referring to FIG. 5, the V-SPC substitutes a "key expansion" and a V-SLP-Random value to a Pseudo Random Function (PRF), which are strings for deriving keys differently for each connection and master secret received from the H-SLP. Obtain the key material as shown in Eq. (2). The master secret is created for each TLS session and the key material is generated for each connection. Therefore, the V-SLP finally obtains the Integrity Key, Ciphering Key, and Initialization Vector used for encryption transmission from the obtained key material.

6 is a diagram illustrating transmission of a master secret when SUPL roaming. In particular, FIG. 6 shows a master secret in each TLS session when the master secret used between the H-SLP and the SET is shared with the SET and the V-SLPs.

As shown in FIG. 6, the pre-master secret first generated in the SET is encrypted in the SET and then transmitted to the H-SLP. If the SET roams to V-SLP1 or V-SLP2, the H-SLP encrypts and transmits the master secret derived from the pre-master secret with the public key of V-SLP1 or V-SLP2, respectively. Therefore, even if the same pre-master is received from the SET, different master secrets are transmitted to V-SLP1 or V-SLP2, making it impossible for a third party to know the location of the SET not only in the current session but also after the roaming session. .

Meanwhile, in another embodiment of the present invention, a roaming-master secret may be transmitted from H-SLP to V-SLP instead of a master secret when SUPL roaming.

7 is a diagram illustrating the transmission of a roaming-master secret when SUPL roaming. FIG. 7 illustrates a master secret and a roaming master secret used in each TLS session when the master secret used between the H-SLP and the SET is not transmitted as it is and is shared with the SET and the V-SLPs. Indicates.

As shown in FIG. 7, when the SET roams to V-SLP1 or V-SLP2, the H-SLP concatenates the roaming-count of the SET to the master secret derived from the pre-master secret received from the SET. After concatenation, roaming-master secrets 1 and 2 are generated by hashing, and the roaming-master secrets 1 and 2 are encrypted with the public keys of V-SLP1 and V-SLP2, respectively.

Therefore, even if a third party acquires roaming-master secret 1 between H-SLP and V-SLP1 (or V-SLP2), the pre-master secret cannot be obtained from the roaming-master secret 1. The location will not be easily exposed. That is, the roaming master secret is a value obtained by concatenating a roaming count of a SET with a pre-master secret using a hash function such as SHA (). Since the hash function is unidirectional, it is difficult to calculate a pre-master secret from a roaming-master secret.

8 illustrates a case of using a roaming-master secret between the H-SLP and the V-SLP as a TLS session management method according to the second embodiment of the present invention. That is, in the second embodiment of the present invention, the master secret used between the H-SLP and the SET is not used as it is, and the master secret of the H-SLP is unknown in the V-SLC by changing the roaming-master secret. Changed value). The use of the roaming-master secret is to enable the V-SLP to establish a TLS connection without the V-SLP knowing the master secret used in the previous TLS session between the H-SLP and the SET.

As shown in FIG. 8, the H-SLP and the V-SLP perform mutual authentication at the time of negotiating service support at the first time, periodically verifying the CRL or validating the certificate through the OCSP (S60). At this time, at least the H-SLP must authenticate the V-SLP rotatable by the SET and must have the certificates of the V-SLPs.

In this state, the SET performs the first TLS session establishment procedure with the H-SLP (S61). When performing the procedure, the SET encrypts and transmits the pre-master secret with the public key of the H-SLP. Once the TLS session is established between the H-SLP and the SET, the SET sends a SUPL START message to the H-SLP to initiate the H-SLP and SUPL procedures (S62), and the H-SLP sets the SET based on the routing information. Roaming of SET is detected by judging the location information of V-SLP.

When the SET roams to the V-SLP, the H-SLP transfers the TLS session information to the V-SLC through the RLP SSRLIR (SUPL START) (S63), and the V-SLC transmits the corresponding information to the V-SLC through internal communication. Deliver to SPC. Here, the RLP message is transmitted in the form of an encrypted message through HTTPS (TLS). In this case, parameters added to the RLP SSRLIR message are as follows.

roaming-master secret, sessionID , cipher Suites, compression methods: Used to extend the TLS session between the V-SLC and the SET.

The roaming-master secret represents a hashed value after concatenating a master secret and a roaming count as shown in the following function (3). The sessionID is a session number of a TLS session to be reused, and cipher Suites The encryption method, and the compression method, indicates a compression method.

roaming-master secret = SHA (master secret | roaming-count) --- Equation (3)

Here, the roaming count means the number of times roaming has occurred.

As described above, in the second embodiment of the present invention, the master secret used between the H-SLP and the SET is not used as it is, and the master secret of the H-SLP is unknown in the V-SLC by changing the roaming-master secret. Changed value). The use of the roaming-master secret is to enable the V-SLP to establish a TLS connection without the V-SLP knowing the master secret used in the previous TLS session between the H-SLP and the SET.

The V-SLP forwards an RLP SSRLIA (SUPL RESPONSE) including a sessionID and a V-SPC address to the H-SLP as a response to the RLP SSRLIR message (S64), and the H-SLP is a SUPL RESPONSE as a SET. Send a message (including SUPL sessionid, V-SPC address, ..). That is, the H-SLP informs the SET of the SUPL session number and the server (V-SPC) to receive the location service (S65).

Therefore, even if the previous TLS session is terminated, the SET uses the TLS session information used when establishing the TLS session between the first H-SLP and the SET, and uses the A-Breviated Handshake protocol with the V-SPC. Create a connection (S66).

That is, SET sends Client Hello message including parameters such as Version, SET-Random, sessionID [1] to V-SPC. As a response to the Client Hello, the V-SPC sends a Server Hello message including parameters such as Version, V-SLP-Random, and sessionID [1] to the SET, and then encrypts after the negotiation between the SET and the V-SPC ends. Send ChangeCipherSpec and Finished to indicate when to run.

When Finished is inputted from the V-SPC, the SET also sends a ChangeCipherSpec and Finished message to the V-SPC in order to complete all of the abbreviated handshake processes for establishing a TLS connection.

Accordingly, the SET and the V-SPC may derive encryption parameters using parameter values (SET-Random or V-SLP-Random) exchanged with each other when performing an abbreviated handshake. At this time, the derivation process of encryption parameters uses PRF () provided by the same TLS session as follows.

key material = PRF (roaming master secret, "key expansion", V-SPC | V-SPC-Random)

In other words, V-SPC gets roaming-master secret from V-SLC through internal initialization and obtains key material, SET derives roaming-master secret (roaming-MS) from master secret, and then obtains key material again. Used for integrity verification.

As described above, the present invention provides a new TLS between the V-SPC and the SET of the V-SLP when opening a TLS session to secure the security in SUPL-based location tracking, in particular, opening the TLS session between the H-SLP and the SET. By providing the V-SLP with the key information used in the previous TLS session when opening the session, it is possible to reduce the overall system load by reducing the conventional burden of establishing a new TLS session from the beginning.

In addition, although the present invention has been described with reference to the embodiments illustrated in the drawings, this is merely exemplary and will be understood by those skilled in the art that various modifications and equivalent other embodiments are possible. . Therefore, the true technical protection scope of the present invention will be defined by the technical spirit of the appended claims.

Claims (26)

In a system where a terminal having a TLS session with H (Home) -SLP (SUPL Location Platform) roams with V (Visited) -SLP to provide location information service, Transmitting, by the H-SLP, the TLS session information used when establishing a TLS (Transport Layer Security) session with the terminal to the V-SLP; And establishing, by the SET, a new TLS connection for position calculation with the V-SLP, using the TLS session information. The method of claim 1, wherein the TLS session information is TLS session management method comprising the TLS session ID and new key information. The method of claim 2, wherein the key information is TLS session management method characterized in that the master secret or roaming master secret. The method of claim 2, wherein the TLS session information is TLS session management method, characterized in that it further comprises a parameter indicating the encryption method and compression method used when connecting the TLS session between the H-SLP and the terminal. The method of claim 1, wherein the TLS session information is The SUPL START message is transmitted through a SUPL START message, wherein the SUPL START message is an RLP SSRLIR (Standard SUPL Roaming Location Immediate Request) delivered by the H-SLP to the V-SLP. The method of claim 3, wherein the master secret A method of managing a TLS session, comprising: generating a value obtained by concatenating a pre-master secret with a known random value between a UE and an H-SLP using a pseudo random function. 4. The roaming master secret of claim 3, wherein A method for managing a TLS session, comprising generating a hash of a concatenation of a master secret and a roaming count. The method of claim 1, wherein establishing a new TLS connection comprises: TLS session management method characterized by being performed by an abbreviated handshake protocol. The method of claim 1, wherein establishing a new TLS connection comprises: Transmitting, by the SET, a Client Hello message including Version, SET-Random, and sessionID to the V-SPC; The V-SPC sequentially transmitting a Server Hello message including a Version, V-SLP-Random, sessionID, ChangeCipherSpec, and Finished as a SET; And when the Finished message is input from the V-SPC, the SET sequentially transmitting the ChangeCipherSpec and the Finished message to the V-SPC to terminate the abbreviated handshake process. In roaming a location information system based on Secure User Plane Location (SUPL) using Transport Layer Security (TLS), Establishing, by the terminal, a TLS session with a H (Home) -SUPL Location Platform (SLP) and transmitting SUPL START to the H-SLP; Transmitting, by the H-SLP, the set TLS session information to a V (Visited) -SLP roaming by the UE; Transmitting, by the H-SLP, information of the V-SLP to a terminal; And establishing, by the terminal and the V-SLP, a new TLS connection in the TLS session by using the TLS session information. The method of claim 10, wherein the TLS session information is A TLS session ID used to connect a TLS session between the H-SLP and the UE; TLS session management method comprising a master secret or roaming master secret that is key information of the TLS session. 12. The method of claim 11, wherein the TLS session information is TLS session management method, characterized in that it further comprises a parameter indicating the encryption method and compression method used when connecting the TLS session between the H-SLP and the terminal. The method of claim 11, wherein the master secret A method of managing a TLS session, comprising generating a value obtained by concatenating a pre-master secret with a known random value between a UE and an H-SLP using a pseudo random function. 12. The method of claim 11, wherein the roaming master secret is A method of managing a TLS session, comprising generating a hash of a concatenation of a master secret and a roaming count. The method of claim 10, wherein the TLS session is TLS session management method characterized in that performed by the Full Handshake protocol. 11. The method of claim 10, wherein the new TLS connection is TLS session management method characterized in that performed by the abbreviated handshake protocol. 11. The method of claim 10, further comprising the step of calculating the SET position by the V-SLP and the SET performing a SPUL positioning procedure when the new connection is established. 11. The method of claim 10, wherein establishing a new TLS connection is Transmitting, by the SET, a Client Hello message including Version, SET-Random, and sessionID to the V-SPC; The V-SPC sequentially transmitting a Server Hello message including a Version, V-SLP-Random, sessionID, ChangeCipherSpec, and Finished as a SET; And when the Finished message is input from the V-SPC, the SET sequentially transmitting the ChangeCipherSpec and the Finished message to the V-SPC to terminate the abbreviated handshake process. In roaming a location information system based on Secure User Plane Location (SUPL) using Transport Layer Security (TLS), The SET establishing a TLS session with H (Home) -SUPL Location Platform (SLP); The SET sending a SUPL Start message to the H-SLP; When the SUPL Start message is received, transmitting, by the H-SLP, the TLS session information to a V-SLC (SUPL Location Center) of the V-SLP through an RLP SSRLIR message; Transmitting, by the V-SLC, the received TLS session information to a V-SPC (SUPL Positioning Center) through internal initialization; Sending, by the V-SLC, a V-SPC address for performing a session ID and location calculation through an RLP SSRLIA message to the H-SLP; Transmitting, by the H-SLP, the session ID and the V-SPC address to a SET through a response message for a SUPL Start message; The SET and the V-SPC establishing a new TLS connection using the TLS session information; Calculating the position of the SET by performing a SPUL positioning procedure between the V-SPC and the SET; And transmitting the SUPL END message by the V-SPC when the position calculation of the SET is completed. 20. The method of claim 19, wherein the TLS session information is A TLS session ID used to connect a TLS session between the H-SLP and the UE; TLS session management method comprising a master secret or roaming master secret that is key information of the TLS session. The method of claim 20, wherein the TLS session information is TLS session management method, characterized in that it further comprises a parameter indicating the encryption method and compression method used when connecting the TLS session between the H-SLP and the terminal. The method of claim 20, wherein the master secret TLS session management method comprising generating a pre-master secret and a random value known between the UE and the H-SLP using a pseudo random function. 21. The method of claim 20, wherein the roaming master secret is A method of managing a TLS session, comprising generating a hash of a concatenation of a master secret and a roaming count. 20. The method of claim 19, wherein the TLS session is TLS session management method characterized in that performed by the Full Handshake protocol. 20. The method of claim 19, wherein the new TLS connection is TLS session management method characterized in that performed by the abbreviated handshake protocol. 20. The method of claim 19, wherein establishing a new TLS connection comprises: Transmitting, by the SET, a Client Hello message including Version, SET-Random, and sessionID to the V-SPC; The V-SPC sequentially transmitting a Server Hello message including a Version, V-SLP-Random, sessionID, ChangeCipherSpec, and Finished as a SET; And when the Finished message is input from the V-SPC, the SET sequentially transmitting the ChangeCipherSpec and the Finished message to the V-SPC to terminate the abbreviated handshake process.

Images