KR101342726B1 - Session state information record storing method and apparatus - Google Patents

Abstract

According to one embodiment of the present invention, a method of storing a Session State Information Record is provided. The method includes receiving session state information including parameters related to one or more protocols, respectively, as a plurality of parameters from a terminal, and at least one configured with at least one parameter related to the same protocol among the plurality of parameters. Generating a data group, generating an identifier for each generated data group, storing or discarding the generated at least one data group and an identifier for the data group in a data group storage module, and storing the stored data group Generating reference information for the corresponding data group each time, and storing the generated reference information in an SSIR storage module as a session state information record for the received session state information.

1xEV-DO (Evolution Data Only), session state information

Description

Method and device for storing session state information record {SESSION STATE INFORMATION RECORD STORING METHOD AND APPARATUS}

The present invention relates to a wireless communication system, and more particularly, to a method and apparatus for storing information on a wireless communication protocol to be used for a wireless interface between a terminal and a connection network of a wireless communication system.

The 1xEV-DO (Evolution Data Only) system is a wireless communication system that was evolved from CDMA 2000 Code Division Multiple Access 2000 1X (1x) and provides packet data services such as video on demand (VOD) up to 2.4 Mbps without using a voice call network. The transmission is by using a dedicated channel. The 1xEV-DO system includes an access terminal (AT), an access network (AN) providing wireless access service to the AT, a packet control function (PCF) providing packet relay service to at least one AN, and a PCF and AN A packet switch data network (PDSN) (eg, the Internet) for providing a packet data service to the AT through the AP.

Among the above components, the AT negotiates with the AN in advance the types of protocols to be used for the wireless connection or the air interface with the AN and the parameters related to the protocols, and negotiated information (that is, session state). Information (Session State Information (SSI)) is stored as a Session State Information Record (Session State Information Record) in a session control module or session control device (e.g., SC / MM (Session Control and Mobility Management) module). The SSIR is used as configuration information of protocols used to connect the AT and the AN when the AT later establishes a connection with the AN. That is, when the AT requests the AN to establish a connection, the AN receives an SSIR from the PCF and uses the connection to establish the connection. This configuration saves you from having to negotiate between the AT and AN each time you establish a connection, as well as the type of protocols and associated parameters that will be used for the connection. In addition, SSIR can be used by AT, AN, or other components in a variety of situations, such as when an AT is handing off, saving radio resources.

The conventional session control device generates and stores an SSIR for each AT that it manages. Specifically, upon receiving the SSI from the AT, a memory space having a predetermined size is allocated to the AT, and the received SSI is stored as an SSIR in the allocated memory space. However, since the size of the SSI can vary from several tens to thousands of bytes, the method of allocating a fixed memory size as described above has a problem in that a large portion of the allocated memory space is not used and wasted. In addition, according to the above configuration, as the number of ATs managed by the session managing apparatus increases, more memory resources are required for SSIR storage in proportion to this. However, in view of the fact that there are many overlapping contents among SSIRs stored in the session storage device, there is a problem in that memory resources are seriously wasted by redundantly storing the same contents.

The present invention has been made to solve the above problems, and an object thereof is to provide a method and apparatus for efficiently storing session state information records of a wireless communication system.

According to one embodiment of the present invention, a method of storing a Session State Information Record is provided. The method includes receiving session state information from any device, wherein the session state information includes a plurality of parameter values, each parameter value being associated with one or more type information; Generating at least one data group from the plurality of parameter values, and when there are parameter values related to the same type information among the plurality of parameter values, classifying the parameter values related to the same type information into one data group. Comprising a step; Generating an identifier for each of the generated data groups; Determining whether the generated identifier is stored in a data group storage module; Storing or discarding the generated data group and the identifier for the generated data group in a data group storage module according to the determination; Generating reference information for any one of the data groups stored in the data group storage module for each of the generated data groups; And storing the generated reference information in an SSIR storage module as a session state information record for the received session state information.

According to another embodiment of the present invention, an apparatus for storing session state information records is provided. The apparatus includes a data group storage module; SSIR storage module; A receiving module for receiving, from a device, session state information as a plurality of parameter values, each parameter value including a plurality of parameter values associated with one or more type information; Generate at least one data group from the plurality of parameter values, generate an identifier for each generated data group, determine whether the generated identifier is stored in a data group storage module, and generate the generated Storing or discarding a data group and an identifier for the created data group in a data group storage module, and generating reference information for any one of the data groups stored in the data group storage module for each generated data group; And a processing module for storing the generated reference information in the SSIR storage module as a session state information record for the received session state information. The processing module may generate the data group by classifying parameter values related to the same type information into one data group when there are parameter values related to the same type information among the plurality of parameter values.

The above summary of embodiments is provided to illustrate some of the concepts of the simplified form of the detailed description of the invention, which is described in more detail below. The summary of these embodiments is not intended to identify essential features of the claimed subject matter, nor is it intended to be used as a means for determining the scope of the claimed subject matter.

According to the present invention as described above, it is possible to provide a session control apparatus for efficiently storing the session state information record of the wireless communication system.

Reference is now made to the accompanying drawings, which form a part of this specification. In the drawings, like numerals refer to similar constructions unless the context clearly indicates otherwise. The illustrative embodiments described in the detailed description, drawings, and claims are not meant to be limiting. Other embodiments may be utilized, and other changes may be made, without departing from the spirit or scope of the subject matter presented herein. It will be readily understood that the configurations of the present disclosure generally described herein and illustrated in the drawings may be arranged, replaced, or combined in various other configurations, all of which are expressly contemplated, and part of this specification Configure.

1 is a conceptual diagram of a 1xEV-DO system 100 according to an embodiment of the present invention. Referring to FIG. 1, the 1xEV-DO system 100 includes an AT 110, an AN 120 providing a wireless access service to the AT 110, and a PCF 130 providing a packet data relay service to the AN 120. And the PDSN 140 that provides packet data services to the AT 110 via the AN 120 and the PCF 130. Although FIG. 1 illustrates only one AT 110, AN 120, PCF 130, and PDSN 130 for convenience of description, the 1xEV-DO system 100 includes one or more of the above components. In addition, these components can be interconnected in various ways.

The AT 110 is a terminal that provides a packet data service of the PDSN 140 to a user, and may exchange packets through an air interface with the AN 120. For packet exchange, the AT 110 may perform two procedures with the AN 120, namely, session negotiation procedure and connection establishment procedure.

The session negotiation procedure is a procedure in which the AT 110 and the AN 120 negotiate information about protocols and parameters to be used for the air interface, and determine the information between the AT 110 and the AN 120 as a result of the session negotiation. Session State Information (SSI) is created that defines information about protocols and parameters to be used for the air interface. The details of the session negotiation procedure above are detailed in the relevant Recommendations of 3GPP2.

After the session negotiation procedure is completed, AT 110 or AN 120 transmits the generated SSI to a session control module (eg, a Session Control and Mobility Management (SC / MM) module) in PCF 130. The session control module is a module for storing and managing the SSI. The session control module receives the SSI for the AT from the AT in charge of the PCF 130, including the AT 110, and stores and manages the SSI after performing a predetermined process.

In detail, the session control module may classify the data included in the received SSI according to a predetermined criterion to generate at least one data group including data belonging to the same classification. The session control module may store other data groups generated by receiving SSI from other ATs before receiving the SSI from the AT 110. The session control module may discard the data groups having the same contents as any one of the data groups already stored in the session control module among the data groups generated by the SSI received from the AT 110 and store the remaining data groups. The session control module generates reference information for each data group already stored in the thin wire control module having the same contents as the discarded data groups, and generates reference information for each newly stored data group. Can be. The reference information generated in the session control module may be stored in the session control module as a session state information record (SSIR) for the SSI. According to the above configuration, since the session control module does not repeatedly store the same contents as other SSIs stored in the SSI, it is possible to efficiently manage memory resources of the session control module.

The connection establishment procedure is a procedure following the session negotiation procedure and the session storing procedure above. The AN 120 allocates one or more radio channels to the AT 110 in response to the connection establishment request from the AT 110. This is a procedure for establishing a wireless connection between the AN (120). When the AT 110 transmits a connection establishment request to the AN 120, the AN 120 receives the SSI from the PCF 130 and establishes a wireless connection based on protocol and parameter information stored in the SSI. Used to set. The session control module of the PCF 130, which is requested to transmit the SSI from the AN 120, retrieves the stored SSIR associated with the AT 110, and reads the data group indicated by each reference information of the corresponding SSIR. Reconfigure the SSI. The PCF 130 then transmits the reconstructed SSI to the AN 120.

2 is a conceptual diagram of an SSI according to an embodiment of the present invention. Referring to FIG. 2, the SSI may include TLV (Type, Length, Value) data 200 including a type field 210, a length field 220, and a value field 230.

The type field 210 of the TLV data 200 may be a numeric code indicating what kind of content is included in the TLV data 200 or a value field following the type field. For example, the protocol type field 211 may indicate which protocol the TLV data 200 is associated with. Each parameter type field 212 and 213 may indicate which type of parameter information is a value field (ie, parameter attribute fields 231 and 232) subsequent to the corresponding parameter type field 212 and 213. have. The length field 220 may indicate the length of the value field subsequent to the corresponding length field. For example, the length fields 221 and 222 may indicate the lengths of the parameter attribute fields 231 and 232, respectively. The value field 230 is a variable size field and may include a specific parameter value. For example, the parameter attribute fields 231 and 232 may each include values representing attributes of various parameters. The protocol type field 211 is protocol related information, and the parameter type fields 212 and 213, the length fields 221 and 222 and the parameter attribute fields 231 and 232 are parameter related information.

Although FIG. 2 illustrates one TLV data 200 in relation to SSI, the SSI may be a TLV data stream composed of a series of TLV data, the size of which may vary depending on a result of a specific session negotiation procedure. The SSI may include other types of data in addition to the TLV data. In one embodiment, the SSI may be configured in the form defined in 14.8 Session State Information Record of 3GPP2 C.S0024-A v3.0. In another embodiment, the SSI may include a type field indicating a type of another type and a value field associated with the type field, in addition to the type field shown in FIG. 2.

3 is a detailed block diagram of the session control module of the PCF shown in FIG. Referring to FIG. 3, the session control module 300 is a receiving module (not shown) for receiving SSI and SSI transmission requests from the AT 110 or AN 120, and a processing module for processing the received SSI and SSI transmission requests. 310, a storage module 320 for storing information generated by the processing module.

The processing module 310 may include a data group generation module 311, a data group identifier generation module 312, a data group retrieval module 313, a data group generation module 311, and an SSIR processing module 312. . The data group generation module 311 may generate at least one data group based on the SSI received from the AT 110 or the AN 120. The data group generation module 311 classifies and generates parameter values related to the same type information among the plurality of parameter values included in the SSI received from the AT 110 or the AN 120 into one data group, and generates a plurality of parameters. Parameter values other than parameter values related to the same type information among the values may be generated by being classified into one data group for each parameter value. In one embodiment, the data group generation module 311 classifies a series of TLV data included in the SSI based on a protocol type field of the TLV data, thereby including at least one data group including TLV data having the same protocol type. Can be generated.

The data group identifier generation module 312 generates an identifier for each data group generated by the data group generation module 311. In one embodiment, the data group identifier generation module 312 may generate an identifier using an algorithm for generating a unique identifier according to the content of the data group. For example, the algorithm may be a message digest algorithm such as Message Digest Algorithm 5 (MD5) or Secure Hash Algorithm 1 (SHA-1). For embodiments employing MD5, data group identifier generation module 312 generates MD5 hashes whose data groups are unique according to their content. All MD5 hashes generated by the data group identifier generation module 312 may have the same fixed length (eg, 128 bytes).

The data group search module 313 may receive an identifier for the data group and search for a data group having the same identifier as the input identifier among the data groups stored in the data group storage module 321. In an embodiment, the data group having the same MD5 hash may be searched among the data groups stored in the data group storage module 321.

The data group processing module 314 stores at least one data group generated by the data group generation module 311 and an identifier for the data group based on the search result of the data group retrieval module 313. ) Or discard it. In one embodiment, the data group processing module 314 discards the data groups in which the data group having the same identifier is found in the data group storage module 321 among the generated data groups, and the identifiers of the corresponding data groups. The data groups are stored in the data group storage module 321.

In addition, the data group processing module 314 may delete a data group that is not referenced by any of the reference information of the SSIRs stored in the SSIR storage module 322 among the data groups stored in the data group storage module 321. have. This is to reduce waste of memory resources by deleting data groups that are no longer needed among the data groups stored in the data group storage module 321.

SSIR processing module 315 generates reference information for each data group stored in data group storage module 321 (eg, information indicating a storage location within data group storage module 321 of each data group). do. The SSIR processing module 315 is responsible for data groups discarded by the data group processing module 314 with data groups having the same identifier as the discarded data groups already stored in the data group storage module 321. Generate reference information for. The SSIR processing module 315 stores the generated reference information in the SSIR storage module 322 as the SSIR for the SSI received from the AT 110 or the AN 120.

In addition, SSIR processing module 315 deletes the associated SSIR stored in SSIR storage module 322 when the session associated with the SSI received from AT 110 or AN 120 is released. The release of the session may occur due to various factors such as the AT 110 moving from the area of the currently connected PCF 130 to the area of another PCF (not shown) and handing off. In this case, session control of the PCF 130 is performed. SSIR processing module 315 of module 300 may delete the SSIR associated with the session of AT 110.

When the SSI generation module 316 receives an SSI transmission request from the AN 120 to the AT 110, the SSI generation module 316 retrieves the stored SSIR associated with the AT 110 and indicates data indicated by each reference information of the corresponding SSIR. Read the group and reconfigure the SSI.

4 is a flowchart of an SSIR storage method according to an embodiment of the present invention. 5A and 5B are conceptual diagrams of an SSIR storage method according to an embodiment of the present invention. Referring to FIG. 4, in block 400, the data group generation module 311 of the session control module 300 receives the SSI 500 from the AT 110 or the AN 120. In block 410, the data group generation module 311 classifies the information included in the SSI 500 according to a predetermined criterion to generate at least one data group 510 that collects information for each classification. In one embodiment where the SSI 500 includes a TLV data stream, the data group generation module 311 classifies the series of TLV data based on the protocol type field of the TLV data to classify the TLV data having the same protocol type. The data groups 510 may be created. For example, as shown in FIG. 5A, a series of TLV data included in the SSI 500 for any session is classified according to a protocol type, so that the data includes TLV data having a value of A in the protocol type field. A group 511, a data group 512 including TLV data having a value of B in the protocol type field, and a data group 513 including TLV data having a value in the protocol type field, X may be generated.

At block 415, the data group identifier generation module 312 generates a unique identifier, eg, an MD5 hash, based on the contents of the data group 510 for each data group 510 created. In the example shown in FIG. 5, MD5 hashes 0x02, 0x05 and 0x03 are generated for each data group 511, 512, 513. In block 420, the data group retrieval module 313 sets the number of the generated MD5 hashes to n, selects one of the generated MD5 hashes, and stores the data groups stored in the data group storage module 321. A data group having the same MD5 hash of 526 is searched (block 425) to determine whether the same MD5 hash is stored (block 430). In the example shown in FIG. 5, the data group storage module 321 is searched for MD5 hashes 0x02, 0x05 or 0x03, respectively, and data groups 522 and 523 having MD5 hashes 0x02 and 0x03 are stored, respectively, and MD5 hash 0x05. Verify that the data group with is not stored.

For an MD5 hash where the same MD5 hash is not found in the block 430 determination, the data group processing module 314 stores the data group in the data group generated in block 415 identified by the MD5 hash generated in block 415 and the MD5 hash. Save to module 321 (block 435) and generate reference information for the stored data group and MD5 hash (block 440). For an MD5 hash where the same MD5 hash is found as a result of block 430, the data group processing module 314 discards the corresponding MD5 hash generated at block 415 and the data group created at block 415 identified by the MD5 hash (block 445, generate reference information for the data group having the same MD5 hash retrieved in the data group storage module 321 (block 450).

For the example shown in FIG. 5A, MD5 hash 0x02 and data group 511, and MD5 hash 0x03 and data group 513 are discarded and the MD5 hash stored in data group storage module 321 as shown in FIG. 5B. Reference information 531, 533 is generated for each data group 522 with 0x02 and data group 523 with MD5 hash 0x03. On the other hand, data group 512 with MD5 hash 0x05 is stored in data group storage module 321 as data group 527 with MD5 hash 0x05, and reference information 532 for data group 527 is generated. do.

In block 455, the data group retrieval module 313 sets the value of n minus 1 to n, and determines whether the newly set n is 0 (block 460). If the newly set n is 0, the flow proceeds to block 425. If the newly set n is not 0, the SSIR processing module 315 generates the generated reference information as the SSIR for the SSI received at block 400 (block 465), and stores it in the SSIR storage module 322 (block 470), the procedure ends. In the example shown in FIG. 5B, the generated reference information 531, 532, 533 is stored in the SSIR storage module 322 as the SSIR 530 of the SSI 500.

In addition to the procedure shown in FIG. 4, the data group processing module 314 is not referenced by any of the reference information of the SSIRs stored in the SSIR storage module 322, among the data groups stored in the data group storage module 321. You can delete data groups that do not. For the example shown in FIG. 5B, the data groups 521, 524, 525, 526 that are not referenced by the SSIR 530 of the data groups 521-527 are the same if they are other SSIRs not shown in FIG. 5B. If not also referred to by, it may be deleted by data group processing module 314 (see FIG. 3).

In addition to the procedure shown in FIG. 4, the SSIR processing module 315 may delete the associated SSIR stored in SSIR storage module 322 when the session associated with the SSI received from AT 110 or AN 120 is released. . In the example shown in FIG. 5B, if the session associated with the SSI 500 is released due to reasons such as the AT 110 transmitting the SSI 500 handing off to another network, the SSIR processing module 315 may perform an SSIR. 530 may be deleted.

In addition to the procedure shown in FIG. 4, when the SSI generation module 316 receives an SSI transmission request for the AT 110 from the AN 120, the SSI generation module 316 retrieves the SSIR stored in association with the AT 110, The data group indicated by each reference information is withdrawn from the data group storage module 321, and the SSI is reconstructed based on the retrieved data groups. The PCF 130 then transmits the reconstructed SSI to the AN 120.

Those skilled in the art will appreciate that in the processes described above and other processes, interactions, and methods, the functions performed within the processes, interactions, and methods may be implemented in a different order. In addition, the steps and operations described are provided by way of example only. That is, some of the steps and actions may be optional and may be combined into fewer steps and actions or extended to additional steps and actions without compromising the nature of the disclosed embodiments.

Those skilled in the art will also appreciate that the devices and methods described herein may be implemented in hardware, software, firmware, middleware, or combinations thereof, and may be used in systems, subsystems, components, or subcomponents thereof. Will know. For example, a method implemented in software can include computer code for performing the operations of the method. Such computer code may be stored on a machine readable medium, such as a processor readable medium or a computer program product, or transmitted over a transmission medium or communication link as a computer data signal embodied as a carrier wave or a signal modulated by a carrier wave. . Machine-readable media or processor-readable media can include any medium that can store or convey information in a form that can be read and executed by a machine (eg, processor, computer, etc.).

From the foregoing, various embodiments of the present disclosure have been described for purposes of illustration, and may be embodied in various modified forms without departing from the scope and spirit of the present disclosure. Accordingly, the various embodiments described herein are not to be taken in a limiting sense, and the true scope and spirit of the specification are indicated by the following claims.

1 is a conceptual diagram of a 1xEV-DO system 100 in accordance with an embodiment of the present invention.

2 is a conceptual diagram of SSI according to an embodiment of the present invention.

3 is a detailed block diagram of the session control module of the PCF shown in FIG.

4 is a process diagram of an SSIR storage method according to an embodiment of the present invention.

5A and 5B are conceptual diagrams of an SSIR storage method according to an embodiment of the present invention.

Claims (20)

A method of storing a session state information record, the method comprising: Receiving Session State Information comprising a plurality of parameter values from any device, wherein each parameter value is associated with one or more type information; Generating at least one data group from the plurality of parameter values, wherein the generating step includes setting the parameter values related to the same type information into one data group when there are parameter values related to the same type information among the plurality of parameter values. Classifying as; Generating an identifier for each of the generated data groups; Determining whether the generated identifier is stored in a data group storage module; Storing or discarding the generated data group and the identifier for the generated data group in a data group storage module according to the determination; Generating reference information for any one of the data groups stored in the data group storage module for each of the generated data groups; And Storing the generated reference information in an SSIR storage module as a session state information record for the received session state information. ≪ / RTI > The method of claim 1, wherein storing or discarding the data group storage module comprises: If the generated identifier is not stored in the data group storage module, storing the generated identifier and the generated data group in the data group storage module; And Discarding the generated identifier and the generated data group if the generated identifier is stored in the data group storage module ≪ / RTI > The method of claim 1, wherein the creating of the data group comprises: Classifying parameter values other than parameter values related to the same type information among the plurality of parameter values into one data group for each parameter value; ≪ / RTI > The method of any one of claims 1 to 3, wherein generating the identifier comprises: Generating an identifier for each generated data group using an algorithm for generating a unique identifier according to the contents of a data group; ≪ / RTI > 5. The method of claim 4, The algorithm is a message digest algorithm. 4. The method according to any one of claims 1 to 3, Deleting the session state information record stored in the SSIR storage module when the session related to the received session state information is released; ≪ / RTI > 4. The method according to any one of claims 1 to 3, Deleting, from among the data groups stored in the data group storage module, a data group not referenced by any of the reference information of the session state information record stored in the SSIR storage module. ≪ / RTI > The method of claim 1, The session state information is a TLV (Type, Length, Value) data stream. 9. The method of claim 8, Wherein the TLV data stream comprises at least one of a protocol type field and a parameter type field. The method of claim 1, Retrieving at least one of the data groups stored in the data group storage module based on the session state information record stored in the SSIR storage module; And Generating session state information based on the retrieved at least one data group ≪ / RTI > A device for storing a session state information record, A data group storage module; SSIR storage module; A receiving module for receiving session state information comprising a plurality of parameter values from any device, wherein each parameter value is associated with one or more type information; Generate at least one data group from the plurality of parameter values, wherein the data group includes parameter values associated with the same type information as one data group when there are parameter values associated with the same type information among the plurality of parameter values. Generated by classifying-generating an identifier for each of the generated data groups, determining whether the generated identifier is stored in a data group storage module, and determining the generated data group and the generated data group according to the determination Store or discard an identifier in a data group storage module, generate reference information for any one of the data groups stored in the data group storage module for each generated data group, and generate the received reference information in the received Session state definition for session state information A processing module for storing as a beam record in the SSIR storage module / RTI > The method of claim 11, wherein the processing module, If the generated identifier is not stored in the data group storage module, the generated identifier and the generated data group are stored in the data group storage module, and the generated identifier is stored in the data group storage module. And if present, discard the generated identifier and the created data group. The method of claim 12, wherein the processing module, And classifying parameter values other than the parameter values related to the same type information among the plurality of parameter values into one data group for each parameter value. The processing module according to any one of claims 11 to 12, wherein And generating an identifier for each generated data group by using an algorithm for generating a unique identifier according to the contents of the data group. The method of claim 14, And the algorithm is a message digest algorithm. 13. The process according to any of claims 11 to 12, wherein the processing module is And when the session associated with the received session state information is released, deleting the session state information record stored in the SSIR storage module. The processing module according to any one of claims 11 to 12, wherein Deleting, from among the data groups stored in the data group storage module, a data group that is not referenced by any of the reference information of the session state information record stored in the SSIR storage module. 12. The method of claim 11, And the session state information is a TLV (Type, Length, Value) data stream. 19. The method of claim 18, And the TLV data stream includes at least one of a protocol type field and a parameter type field. The method of claim 11, wherein the processing module, Retrieving at least one of the data groups stored in the data group storage module based on the session state information record stored in the SSIR storage module and generating session state information based on the retrieved at least one data group Device.

Images