User identifier storage association method and system based on mobile communication control plane signaling

Abstract

The invention provides a mobile communication control plane signaling-based user identifier storage association method and system, and the method comprises the steps: obtaining a structured information data packet of a control plane signaling, extracting a user identifier key field, and obtaining a user identifier storage structure table; taking an F-TEID network element I P, an F-TEID tunnel I D and an inner layer I P address in the user identification storage structure table as a control plane triple key, and sending the user identification storage structure table to a user identification storage unit corresponding to the database cluster according to a hash value corresponding to the control plane triple key; managing the survival time period of the user identifier according to the PDU session operation type and the interception timestamp; and taking an F-TEID network element I P, an F-TEID tunnel I D and an inner layer I P address of the user plane data as a user plane triple key, and associating the user identifier with the user plane data by adding fields. According to the method and the device, the problems of user plane association errors and signaling plane time delay are solved, and accuracy verification, distributed storage and dynamic capacity expansion can be realized while query is performed.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of communication and big data technology, in particular to a user identifier storage association method and system based on mobile communication control plane signaling. BACKGROUND

[0002] 4G / 5G mobile communication core network data gradually increases with the increase of user scale and the improvement of service complexity, and the existing user plane data tracing system mainly relies on centralized data management and processing architecture. The traditional centralized architecture relies on centralized processing system of single device, which is not easy to expand when the user scale is large, resulting in bottleneck.

[0003] Since the 4G / 5G communication core network adopts the architecture of separating control plane and user plane data, the user identifier is only in the control signaling, and the user plane data does not carry the user identifier. If only the user plane data is parsed, the business data flow cannot be associated with the specific user, therefore, the signaling plane data needs to be effectively maintained to realize the association of user plane data and user identifier.

[0004] The association method of the existing mobile communication user plane data association system is generally that the signaling analysis restoration module stores the control plane data into the database or the device running memory, so that the user plane data association module finds the corresponding signaling plane data to form the user plane data carrying the user identifier. In reality, due to the transmission link, the user plane data association system may exist the situation that the signaling plane data lags behind the user plane data, which has obvious influence on the association effect. And in the extreme case, the multiplexing mechanism of the core network tunnel endpoint identifier may cause association error.

[0005] In view of the deficiencies of the existing scheme, combined with the characteristics and needs of specific application, the present application provides a user identifier storage association method and system based on mobile communication control plane signaling. SUMMARY

[0006] In view of one or more technical defects in the prior art, the present application provides the following technical solutions.

[0007] Based on the first aspect of the present application, a user identifier storage association method based on mobile communication control plane signaling is provided, comprising:

[0008] S1: obtaining the structured information data packet of the control plane signaling and extracting the user identifier key field to obtain the user identifier storage structure table, taking the F-TEID network element IP, F-TEID tunnel ID and inner IP address in the user identifier storage structure table as the control plane three tuple key, and taking the remaining fields as the value for encapsulation;

[0009] S2: Calculate the hash value corresponding to the control plane triple key, and send the user identifier storage structure table to the user identifier storage unit corresponding to the database cluster according to the hash value.

[0010] S3: Search for the user identifier corresponding to the control plane triple key in all tables of the user identifier storage unit, and manage the lifespan of the user identifier according to the PDU session operation type PDU_ACTION and the interception timestamp ISP_MARKED_TIME;

[0011] S4: Use the F-TEID network element IP, F-TEID tunnel ID, and inner IP address of the user plane data as the user plane triple key. Locate the corresponding user identifier storage unit based on the user plane triple key and the corresponding hash value. Find the user identifier in the user identifier storage structure table by combining the data interception time of the user plane data. Associate the user identifier with the user plane data by adding a field.

[0012] This application achieves load balancing of control plane signaling data and horizontal scaling of the system, fundamentally solving the bottleneck problem of traditional centralized architecture. By introducing "lifetime period" for user identifier lifecycle management, it effectively solves the technical problem of user plane data association errors caused by F-TEID reuse and signaling plane data transmission delay or loss. Finally, through a unified query mechanism, it achieves accurate and efficient association and synthesis of user plane data and user identifier.

[0013] Furthermore, the key user identification fields include F-TEID network element IP, F-TEID tunnel ID, inner IP address, PDU session operation type PDU_ACTION, interception timestamp ISP_MARKED_TIME, and user identifier;

[0014] The PDU session operation type PDU_ACTION indicates the signaling status, including tunnel activation, tunnel modification, and tunnel deactivation;

[0015] The user identifier includes user ID, network cell location identifier (NCGI), and tracking area identifier (TAI).

[0016] Furthermore, in step S2, the storage capacity and allocation weight of the user identifier storage unit are mapped to the user identifier storage structure table of each inbound client. The hash value is moduloed to obtain the IP and port of the corresponding user identifier storage unit. The sending function is called to send the user identifier storage structure table to the user identifier storage unit corresponding to the database cluster.

[0017] This step enables intelligent and uniform distribution of data in the distributed storage cluster, which can make full use of the hardware resources of nodes with different performance levels, avoid data hotspots, improve resource utilization, and provide technical support for dynamic expansion and stable operation.

[0018] Furthermore, step S3 specifically includes:

[0019] If no user identifier corresponding to the control plane triple key is found in any of the tables in the user identifier storage unit, and the PDU session operation type PDU_ACTION is tunnel activation and tunnel modification, then the latest user identifier is inserted, and a survival time period is generated based on the intercepted timestamp ISP_MARKED_TIME in the user identifier storage structure table to activate the user identifier.

[0020] Furthermore, step S3 specifically includes: if the user identifier corresponding to the queried control plane triple key is different from the user identifier in the user identifier storage structure table, then the lifespan of the queried user identifier is deactivated according to the interception timestamp ISP_MARKED_TIME in the user identifier storage structure table to form a lifespan time period with fixed boundaries. At the same time, a new user identifier is inserted into the user identifier storage unit, and the interception timestamp ISP_MARKED_TIME in the user identifier storage structure table is used as the lifespan time period of the user identifier storage unit.

[0021] This step ensures the continuity and accuracy of historical time records when signaling loss or severe delays lead to zombie sessions.

[0022] Furthermore, step S3 specifically includes: if the queried user identifier is the same as the user identifier in the user identifier storage structure table, then update the survival time period corresponding to the queried user identifier according to the interception timestamp ISP_MARKED_TIME in the user identifier storage structure table to form a new survival time period range value.

[0023] Furthermore, step S3 specifically includes: if the PDU session operation type PDU_ACTION of the user identifier is tunnel activation and tunnel modification, then update the current user identifier;

[0024] If the PDU session operation type PDU_ACTION is tunnel deactivation, then the liveness time of the queried user identifier is deactivated according to the intercepted timestamp ISP_MARKED_TIME in the user identifier storage structure table, forming a fixed boundary time period.

[0025] A second aspect of this application also proposes a user identifier storage and association system based on mobile communication control plane signaling, comprising:

[0026] Encapsulation module: Obtains structured information data packets of control plane signaling and extracts key user identification fields to obtain a user identification storage structure table. The F-TEID network element IP, F-TEID tunnel ID, and inner IP address in the user identification storage structure table are used as the control plane triple key, and the remaining fields are used as the value for encapsulation.

[0027] Calculation module: Calculates the hash value corresponding to the control plane triple key, and sends the user identifier storage structure table to the user identifier storage unit corresponding to the database cluster based on the hash value;

[0028] Management module: Searches for the user identifier corresponding to the control plane triple key in all tables of the user identifier storage unit, and manages the lifespan of the user identifier according to the PDU session operation type PDU_ACTION and the interception timestamp ISP_MARKED_TIME;

[0029] Association Module: The F-TEID network element IP, F-TEID tunnel ID, and inner IP address of the user plane data are used as the user plane triple key. Based on the user plane triple key and the corresponding hash value, the corresponding user identifier storage unit is located. Combined with the data interception time of the user plane data, the user identifier in the user identifier storage structure table is found. The user identifier and user plane data are associated by adding a field.

[0030] Based on a third aspect of this application, a computer program product is also proposed, having one or more computer programs thereon that, when executed by a computer processor, perform the method as described in any of the above.

[0031] The technical advantages of this application are as follows: This application achieves efficient storage by mapping user identifiers and lifespan time periods, solves the user plane data association errors caused by the F-TEID reuse mechanism in extreme cases and the latency problem in the signaling plane, avoids association failure caused by signaling plane data lag by storing the historical lifespan range of user identifiers, can realize accuracy verification while querying, and also features distributed storage and dynamic expansion. Attached Figure Description

[0032] Other features, objects, and advantages of this application will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings.

[0033] Figure 1 This is a general flowchart of a user identifier storage association method based on mobile communication control plane signaling, provided according to an embodiment of this application.

[0034] Figure 2This is a module architecture diagram of a user identifier storage association system based on mobile communication control plane signaling, provided according to an embodiment of this application.

[0035] Figure 3 This is a block diagram of the structured reconstruction stage of a user identifier storage association system based on mobile communication control plane signaling, according to an embodiment of this application.

[0036] Figure 4 This is a module diagram of the inbound phase of a user identifier storage association system based on mobile communication control plane signaling, provided according to an embodiment of this application.

[0037] Figure 5 This is a user identifier fusion stage block diagram of a user identifier storage association system based on mobile communication control plane signaling, provided according to an embodiment of this application.

[0038] Figure 6 This is a flowchart of the user identifier fusion stage of a user identifier storage association system based on mobile communication control plane signaling, according to an embodiment of this application.

[0039] Figure 7 This is a block diagram of the associated user identifier stage of a user identifier storage and association system based on mobile communication control plane signaling, provided according to an embodiment of this application.

[0040] Figure 8 This is a flowchart of the associated user identifier stage of a user identifier storage and association system based on mobile communication control plane signaling, according to an embodiment of this application.

[0041] Figure 9 This is a schematic diagram of the structure of a computer system suitable for implementing the electronic devices of the present application embodiments. Detailed Implementation

[0042] The present application will now be described in further detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and not intended to limit it. Furthermore, it should be noted that, for ease of description, only the parts relevant to the invention are shown in the accompanying drawings.

[0043] It should be noted that, unless otherwise specified, the embodiments and features described in this application can be combined with each other. This application will now be described in detail with reference to the accompanying drawings and embodiments.

[0044] Figure 1 This application illustrates a user identifier storage association method based on a first aspect of mobile communication control plane signaling, comprising:

[0045] S1: Obtain the structured information data packet of the control plane signaling and extract the key field of the user identifier to obtain the user identifier storage structure table. Use the F-TEID network element IP, F-TEID tunnel ID and inner IP address in the user identifier storage structure table as the key of the control plane triple, and encapsulate the remaining fields as the value.

[0046] S2: Calculate the hash value corresponding to the control plane triple key, and send the user identifier storage structure table to the user identifier storage unit corresponding to the database cluster according to the hash value.

[0047] S3: Search for the user identifier corresponding to the control plane triple key in all tables of the user identifier storage unit, and manage the lifespan of the user identifier according to the PDU session operation type PDU_ACTION and the interception timestamp ISP_MARKED_TIME;

[0048] S4: Use the F-TEID network element IP, F-TEID tunnel ID, and inner IP address of the user plane data as the user plane triple key. Locate the corresponding user identifier storage unit based on the user plane triple key and the corresponding hash value. Find the user identifier in the user identifier storage structure table by combining the data interception time of the user plane data. Associate the user identifier with the user plane data by adding a field.

[0049] It should be noted that this application achieves load balancing of control plane signaling data and horizontal scaling of the system, fundamentally solving the bottleneck problem of traditional centralized architecture. By introducing a "lifetime period" for user identifier lifecycle management, it effectively solves the technical problem of user plane data association errors caused by F-TEID reuse and signaling plane data transmission delay or loss. Finally, through a unified query mechanism, it achieves accurate and efficient association and synthesis of user plane data and user identifier.

[0050] It should be noted that the key user identification fields include F-TEID network element IP, F-TEID tunnel ID, inner IP address, PDU session operation type PDU_ACTION, interception timestamp ISP_MARKED_TIME, and user identifier;

[0051] The PDU session operation type PDU_ACTION indicates the signaling status, including tunnel activation, tunnel modification, and tunnel deactivation;

[0052] The user identifier includes user ID, network cell location identifier (NCGI), and tracking area identifier (TAI).

[0053] It should be noted that in step S2, the storage capacity and allocation weight of the user identifier storage unit are mapped to the user identifier storage structure table of each inbound client. The hash value is moduloed to obtain the IP and port of the corresponding user identifier storage unit. The sending function is called to send the user identifier storage structure table to the user identifier storage unit corresponding to the database cluster.

[0054] It should be noted that this step enables intelligent and uniform distribution of data in the distributed storage cluster, which can make full use of the hardware resources of nodes with different performance levels, avoid data hotspots, improve resource utilization, and provide technical support for dynamic expansion and stable operation.

[0055] It should be noted that step S3 specifically includes:

[0056] If no user identifier corresponding to the control plane triple key is found in any of the tables in the user identifier storage unit, and the PDU session operation type PDU_ACTION is tunnel activation and tunnel modification, then the latest user identifier is inserted, and a survival time period is generated based on the intercepted timestamp ISP_MARKED_TIME in the user identifier storage structure table to activate the user identifier.

[0057] It should be noted that step S3 further includes: if the user identifier corresponding to the queried control plane triple key is different from the user identifier in the user identifier storage structure table, then the lifespan of the queried user identifier is deactivated according to the interception timestamp ISP_MARKED_TIME in the user identifier storage structure table to form a lifespan time period with fixed boundaries. At the same time, a new user identifier is inserted into the user identifier storage unit, and the interception timestamp ISP_MARKED_TIME in the user identifier storage structure table is used as the lifespan time period of the user identifier storage unit.

[0058] It should be noted that this step can ensure the continuity and accuracy of historical time records when signaling loss or severe delays lead to zombie sessions.

[0059] It should be noted that step S3 further includes: if the queried user identifier is the same as the user identifier in the user identifier storage structure table, then update the survival time period corresponding to the queried user identifier according to the interception timestamp ISP_MARKED_TIME in the user identifier storage structure table to form a new survival time period range value.

[0060] It should be noted that step S3 further includes: if the PDU session operation type PDU_ACTION of the user identifier is tunnel activation and tunnel modification, then update the current user identifier;

[0061] If the PDU session operation type PDU_ACTION is tunnel deactivation, then the liveness time of the queried user identifier is deactivated according to the intercepted timestamp ISP_MARKED_TIME in the user identifier storage structure table, forming a fixed boundary time period.

[0062] Figure 2 A user identifier storage association system based on mobile communication control plane signaling is shown, including encapsulation module a, calculation module b, management module c, and association module d.

[0063] In a specific embodiment, the encapsulation module a is configured to: acquire structured information data packets of control plane signaling and extract key user identification fields to obtain a user identification storage structure table; encapsulate the F-TEID network element IP, F-TEID tunnel ID, and inner IP address in the user identification storage structure table as control plane triple keys and the remaining fields as values.

[0064] In a specific embodiment, the calculation module b is configured to: calculate the hash value corresponding to the control plane triple key, and send the user identifier storage structure table to the user identifier storage unit corresponding to the database cluster based on the hash value.

[0065] In a specific embodiment, the management module c is configured to: search for the user identifier corresponding to the control plane triple key in all tables of the user identifier storage unit, and manage the lifespan of the user identifier according to the PDU session operation type PDU_ACTION and the intercepted timestamp ISP_MARKED_TIME.

[0066] In a specific embodiment, the association module d is configured to: use the F-TEID network element IP, F-TEID tunnel ID, and inner IP address of the user plane data as the user plane triple key; locate the corresponding user identifier storage unit based on the user plane triple key and the corresponding hash value; find the user identifier in the user identifier storage structure table by combining the data interception time of the user plane data; and associate the user identifier with the user plane data by adding a field.

[0067] It should be noted that this application achieves efficient storage by mapping user identifiers to live time periods, which solves the user plane data association errors caused by the F-TEID reuse mechanism in extreme cases and the latency problem in the signaling plane. By storing the historical live time range of user identifiers, it avoids the association failure problem caused by the lag of signaling plane data, and can realize accuracy verification while querying, as well as distributed storage and dynamic expansion.

[0068] In specific embodiments, the system described in this application includes a signaling structured information restoration stage, a database entry stage, a user identifier fusion stage, and a user identifier association stage.

[0069] In a specific embodiment, the signaling structured information restoration stage is performed in the encapsulation module a, such as... Figure 3 As shown, the system includes a packet receiving module 101, a parsing module 102, and an identification data encapsulation module 103. The structured information data packet is a data packet with user identifier and control plane signaling description fields, which is parsed from control plane signaling. The packet receiving module 101 receives the signaling structured information data, and the parsing module 102 assembles the structured information in TLV format and parses it to obtain the user identifier storage structure table, as shown in Table 1. In the identification data encapsulation module 103, the information extracted by the parsing module 102 is encapsulated in key-value format.

[0070] Table 1 User ID Storage Structure

[0071]

[0072]

[0073] In a specific embodiment, the data entry stage is performed in the calculation module b, such as... Figure 4 As shown, the system includes a calculation module 201, a storage unit allocation module 202, and a sending module 203. The calculation module 201 obtains the hash value corresponding to the control plane triple key through a hash algorithm. The storage unit allocation module 202 maps the capabilities and allocation weights of the storage unit nodes deployed on-site to the dynamic maintenance table of each inbound client. It uses the hash value obtained from the control plane triple key to perform modulo operation to obtain the IP and port of the storage unit to which the key-value belongs. The sending module 203 calls the sending function to send the key-value to the corresponding storage unit.

[0074] In a specific embodiment, the user identifier fusion stage is executed in management module c, such as... Figure 5 As shown, it includes a search module 301, a comparison module 302, and an update module 303;

[0075] After receiving key-value data in the search module 301, the data corresponding to the tunnel information is found in the table of the current storage unit node through the control plane triple key. The data contains user identification information of all users who have appeared in the control plane triple key in a recent period of time, including specific user ID, location information and corresponding survival time period.

[0076] In comparison module 302, the acquired data is compared with the currently received structured information to confirm the update method. The user identifier storage unit structure table is shown in Table 2. One triplet key can correspond to multiple user identifier storage units at the same time. The PDU_ACTION type and corresponding action are shown in Table 3.

[0077] Table 2 User ID Storage Unit Structure Table

[0078]

[0079] Table 3. PDU_ACTION Types and Corresponding Actions

[0080]

[0081] The update module 303 searches for the user identifier storage area corresponding to the control plane triple key in all tables of the user identifier storage unit, and manages the lifespan time period of the user identifier according to the PDU session operation type PDU_ACTION and the interception timestamp ISP_MARKED_TIME.

[0082] The process of user identity fusion is as follows: Figure 6 As shown, it includes:

[0083] S61: Query the control plane triplet key in the storage unit. If the key does not exist, create the user ID and activity time period. If the key exists, proceed to the next step.

[0084] S62: Determine if a user identifier exists. If no user identifier exists, create a user identifier and an activity time period. If a user identifier exists, proceed to the next step.

[0085] Specifically, it includes:

[0086] If no user identifier is found for the current key, and the PDU_ACTION is "Tunnel Activation" or "Tunnel Modification", then the latest user identifier data is inserted, and the corresponding survival time period is generated using the intercepted timestamp ISP_MARKED_TIME in the structured information to activate the user identifier.

[0087] If the user identifier found by the current key is inconsistent with the user identifier in the currently received structured information, the interception timestamp ISP_MARKED_TIME in the structured information is used to activate (end) the lifespan corresponding to the found user identifier, forming a fixed-boundary time period that cannot be modified; at the same time, a new user identifier is inserted into the currently received structured information, and a corresponding lifespan time period is generated.

[0088] If the user identifier retrieved by the current key matches the user identifier in the currently received structured information, then the intercepted timestamp ISP_MARKED_TIME in the structured information is updated to the time period corresponding to the current user identifier, forming a new interval value; if PDU_ACTION is "tunnel activation" or "tunnel modification", then the current user identifier is updated; if PDU_ACTION is "tunnel deactivation", then the intercepted timestamp ISP_MARKED_TIME in the structured information is used to deactivate the live time corresponding to the retrieved user identifier, forming a fixed-boundary time period that cannot be modified further;

[0089] S63: Update information. After confirming the modification of node information, call update module 303 to complete data synchronization.

[0090] In a specific embodiment, the user identifier association phase is executed in the association module d, such as... Figure 7 As shown, it includes a field extraction module 401, a query module 402, and a synthesis module 403. It forms a user plane triplet key structure based on the F-TEID (tunnel ID and network element IP) and the user plane inner layer IP in the user data packet. It finds the corresponding storage unit through the key value and hash algorithm, finds the corresponding user identifier through the time when the user plane data occurs, and performs association synthesis.

[0091] In the field extraction module 401, the field information required for association synthesis is extracted by parsing the user plane data packets, including F-TEID (network element IP, tunnel ID), inner IP, and data capture time.

[0092] In the query module 402, the extracted fields are combined into a triplet key and the corresponding storage node is obtained through the storage unit allocation module 202. The key is then sent to the storage node along with the data capture time as a parameter to query the user identification data.

[0093] In the synthesis module 403, the queried user identifier is synthesized with the user face data, and the traceability of the user face data is achieved by adding an identifier field;

[0094] The flowchart for the associated user identification stage is as follows: Figure 8 As shown:

[0095] S81: Query user identifiers using the key of user plane uplink data and user plane log time;

[0096] S82: If a user identifier is found, determine whether verification is required. If verification is required, proceed to the next step; otherwise, execute S85.

[0097] S83: If the user identifier cannot be found, the user identifier will be queried using the key of the user plane downlink data and the user plane log time. If it cannot be found, the association will fail.

[0098] S84: If a user identifier is found, determine whether the verification was successful. If the verification is successful, proceed to the next step; otherwise, the association fails.

[0099] S85: Compositional Association.

[0100] It should be noted that the purpose of the data capture time is to determine which time interval the user identifier data is actually matched after the triple key is used to query the user identifier data. The user identifier mapped to the matched time period is the final user identifier queried. The user plane data consists of uplink data and downlink data, each corresponding to its own F-TEID. Different triple keys are needed to query the user identifier. If the accuracy of the queried user identifier needs to be further verified, the results of the uplink and downlink data queries are compared. Only when the uplink and downlink data are consistent are they associated and synthesized.

[0101] The following is for reference. Figure 9 It shows a schematic diagram of the structure of a computer system suitable for implementing the electronic device of the present application. Figure 9 The electronic device shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of this application.

[0102] like Figure 9 As shown, the computer system includes a central processing unit (CPU) 901, which can perform various appropriate actions and processes based on programs stored in read-only memory (ROM) 902 or programs loaded from storage section 908 into random access memory (RAM) 903. RAM 903 also stores various programs and data required for system operation. CPU 901, ROM 902, and RAM 903 are interconnected via bus 904. Input / output (I / O) interface 905 is also connected to bus 904.

[0103] The following components are connected to I / O interface 905: an input section 906 including a keyboard, mouse, etc.; an output section 907 including a liquid crystal display (LCD) and speakers, etc.; a storage section 908 including a hard disk, etc.; and a communication section 909 including a network interface card such as a LAN card and a modem, etc. The communication section 909 performs communication processing via a network such as the Internet. A drive 910 is also connected to I / O interface 905 as needed. A removable medium 911, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on drive 910 as needed so that computer programs read from it can be installed into storage section 908 as needed.

[0104] Specifically, according to embodiments of this disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this disclosure include a computer program product comprising a computer program carried on a computer-readable storage medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 909, and / or installed from removable medium 911. When the computer program is executed by central processing unit (CPU) 901, it performs the functions defined in the methods of this application. It should be noted that the computer-readable storage medium of this application can be a computer-readable signal medium or a computer-readable storage medium or any combination thereof. The computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this application, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in connection with an instruction execution system, apparatus, or device. In this application, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium can also be any computer-readable storage medium other than a computer-readable storage medium that can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. Program code contained on a computer-readable storage medium may be transmitted using any suitable medium, including but not limited to: wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.

[0105] Computer program code for performing the operations of this application can be written in one or more programming languages ​​or a combination thereof. Programming languages ​​include object-oriented programming languages—such as Java, Smalltalk, and C++—as well as conventional procedural programming languages—such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0106] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0107] The modules described in the embodiments of this application can be implemented in software or in hardware.

[0108] On the other hand, this application also provides a computer-readable storage medium, which may be included in the electronic device described in the above embodiments; or it may exist independently and not assembled into the electronic device. The computer-readable storage medium carries one or more programs, which, when executed by the electronic device, cause the electronic device to: acquire structured information data packets of control plane signaling and extract user identification key fields to obtain a user identification storage structure table; encapsulate the F-TEID network element IP, F-TEID tunnel ID, and inner IP address in the user identification storage structure table as control plane triple keys, and the remaining fields as values; calculate the hash value corresponding to the control plane triple key; and send the user identification storage structure table to the user identification storage unit corresponding to the database cluster according to the hash value; and in the user identification storage... The system searches all tables in the storage unit for the user identifier corresponding to the control plane triple key, and manages the lifespan of the user identifier based on the PDU session operation type PDU_ACTION and the interception timestamp ISP_MARKED_TIME. It uses the F-TEID network element IP, F-TEID tunnel ID, and inner IP address of the user plane data as the user plane triple key, locates the corresponding user identifier storage unit based on the user plane triple key and the corresponding hash value, and finds the user identifier in the user identifier storage structure table by combining the data interception time of the user plane data. Finally, it associates the user identifier with the user plane data by adding a field.

[0109] The above description is merely a preferred embodiment of this application and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of the invention involved in this application is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the above-described inventive concept. For example, technical solutions formed by substituting the above features with (but not limited to) technical features with similar functions disclosed in this application.

[0110] Finally, it should be noted that the above embodiments are for illustration only and not for limiting the technical solutions of the present invention. Although the present invention has been described in detail with reference to the above embodiments, those skilled in the art should understand that modifications or equivalent substitutions can still be made to the present invention without departing from the spirit and scope of the present invention. Any modifications or partial substitutions should be covered within the scope of the claims of the present invention.

Claims

1. A user identifier storage and association method based on mobile communication control plane signaling, characterized in that, include: S1: Obtain the structured information data packet of the control plane signaling and extract the key field of the user identifier to obtain the user identifier storage structure table. Use the F-TEID network element IP, F-TEID tunnel ID and inner IP address in the user identifier storage structure table as the key of the control plane triple, and encapsulate the remaining fields as the value. S2: Calculate the hash value corresponding to the control plane triple key, and send the user identifier storage structure table to the user identifier storage unit corresponding to the database cluster according to the hash value. S3: Search for the user identifier corresponding to the control plane triple key in all tables of the user identifier storage unit, and manage the lifespan of the user identifier according to the PDU session operation type PDU_ACTION and the interception timestamp ISP_MARKED_TIME; S4: Use the F-TEID network element IP, F-TEID tunnel ID, and inner IP address of the user plane data as the user plane triple key. Locate the corresponding user identifier storage unit based on the user plane triple key and the corresponding hash value. Find the user identifier in the user identifier storage structure table by combining the data interception time of the user plane data. Associate the user identifier with the user plane data by adding a field.

2. The method according to claim 1, characterized in that, The key user identification fields include F-TEID network element IP, F-TEID tunnel ID, inner IP address, PDU session operation type PDU_ACTION, interception timestamp ISP_MARKED_TIME, and user identifier; The PDU session operation type PDU_ACTION indicates the signaling status, including tunnel activation, tunnel modification, and tunnel deactivation; The user identifier includes user ID, network cell location identifier (NCGI), and tracking area identifier (TAI).

3. The method according to claim 1, characterized in that, In step S2, the storage capacity and allocation weight of the user identifier storage unit are mapped to the user identifier storage structure table of each inbound client. The hash value is moduloed to obtain the IP and port of the corresponding user identifier storage unit. The sending function is called to send the user identifier storage structure table to the user identifier storage unit corresponding to the database cluster.

4. The method according to claim 1, characterized in that, Step S3 specifically includes: If no user identifier corresponding to the control plane triple key is found in any of the tables in the user identifier storage unit, and the PDU session operation type PDU_ACTION is tunnel activation and tunnel modification, then the latest user identifier is inserted, and a survival time period is generated based on the intercepted timestamp ISP_MARKED_TIME in the user identifier storage structure table to activate the user identifier.

5. The method according to claim 1, characterized in that, Step S3 further includes: if the user identifier corresponding to the queried control plane triple key is different from the user identifier in the user identifier storage structure table, then the lifespan of the queried user identifier is deactivated according to the interception timestamp ISP_MARKED_TIME in the user identifier storage structure table to form a lifespan time period with fixed boundaries. At the same time, a new user identifier is inserted into the user identifier storage unit, and the interception timestamp ISP_MARKED_TIME in the user identifier storage structure table is used as the lifespan time period of the user identifier storage unit.

6. The method according to claim 1, characterized in that, Step S3 further includes: if the queried user identifier is the same as the user identifier in the user identifier storage structure table, then update the survival time period corresponding to the queried user identifier according to the intercepted timestamp ISP_MARKED_TIME in the user identifier storage structure table to form a new survival time period range value.

7. The method according to claim 6, characterized in that, Step S3 further includes: if the PDU session operation type PDU_ACTION of the user identifier is tunnel activation and tunnel modification, then update the current user identifier; If the PDU session operation type PDU_ACTION is tunnel deactivation, then the liveness time of the queried user identifier is deactivated according to the intercepted timestamp ISP_MARKED_TIME in the user identifier storage structure table, forming a fixed boundary time period.

8. A user identifier storage and association system based on mobile communication control plane signaling, characterized in that, include: Encapsulation module: Obtains structured information data packets of control plane signaling and extracts key user identification fields to obtain a user identification storage structure table. The F-TEID network element IP, F-TEID tunnel ID, and inner IP address in the user identification storage structure table are used as the control plane triple key, and the remaining fields are used as the value for encapsulation. Calculation module: Calculates the hash value corresponding to the control plane triple key, and sends the user identifier storage structure table to the user identifier storage unit corresponding to the database cluster based on the hash value; Management module: Searches for the user identifier corresponding to the control plane triple key in all tables of the user identifier storage unit, and manages the lifespan of the user identifier according to the PDU session operation type PDU_ACTION and the interception timestamp ISP_MARKED_TIME; Association Module: The F-TEID network element IP, F-TEID tunnel ID, and inner IP address of the user plane data are used as the user plane triple key. Based on the user plane triple key and the corresponding hash value, the corresponding user identifier storage unit is located. Combined with the data interception time of the user plane data, the user identifier in the user identifier storage structure table is found. The user identifier and user plane data are associated by adding a field.

9. A computer program product having one or more computer programs thereon, characterized in that, When the computer program is executed by a computer processor, the method described in any one of claims 1-7 is performed.

Images