Method for backfilling user identity to SRVCC/eSRVCC A interface records
A user identification and user identification technology, which is applied in the field of backfilling user identification in SRVCC/eSRVCCA interface records, can solve the problems of no user identification in the A interface switching record, inability to analyze the user level of the A interface, and inability to obtain the service status of the A interface, etc.
- Summary
- Abstract
- Description
- Claims
- Application Information
AI Technical Summary
Problems solved by technology
Method used
Image
Examples
Embodiment 1
[0038] figure 2 It is the message flow diagram of the Sv interface and the A interface when SRVCC / eSRVCC occurs. The SRVCC PS to CS request message of the Sv interface contains the UE (User Equipment, User Equipment) user identification: IMSI (International Mobile Subscriber Identity, International Mobile Subscriber Identification) and MSISDN (Mobile Subscriber ISDN Number, Mobile Station ISDN number). The A interface is a standard switching process, and all messages do not contain user identification.
[0039] Usually, the association between the interfaces of the communication network is to use user identification: TMSI (Temporary Mobile Subscriber Identity), IMSI (International Mobile Subscriber Identification, International Mobile Subscriber Identification), etc., but when SRVCC / eSRVCC occurs, A The interface does not have this information and cannot be used.
[0040] When SRVCC / eSRVCC occurs, what actually occurs is a cross-system handover process. During the handover pr...
Embodiment 2
[0046] image 3 It is a flow chart of a method for backfilling user IDs in SRVCC / eSRVCC A interface records provided by an embodiment of the present invention. The method for backfilling user IDs in SRVCC / eSRVCC A interface records first performs underlying message decoding to determine the interface type of the current message, Also includes the following steps:
[0047] Step a: Decoding and synthesizing Sv interface messages, and extracting corresponding parameters according to different information.
[0048] Specifically, the target cell identity and user identity (IMSI and MSISDN) are extracted from the SRVCC PS to CS request message; the handover reference is extracted from the SRVCC PS to CS response message.
[0049] Step b: According to the key switching parameters, establish a node for A interface association search, and fill in the user identity information in the node.
[0050] Specifically, it is judged whether an SRVCC PS-to-CS response message is received, and ...
Embodiment 3
[0057] This embodiment provides the C language description of the data structure associated with the Sv interface and the A interface, and the code is as follows:
[0058] struct sv_a_asso_info{
[0059] short dst_lac;
[0060] short dst_ci;
[0061] unsigned char dst_mcc;
[0062] unsigned char dst_mnc;
[0063] unsigned char hd_ref;
[0064] unsigned char reserved;
[0065] char imsi[MAX_IMSI_LEN];
[0066] char msisdn[MAX_ISDN_LEN];
[0067]};
[0068] Wherein, the target cell ID is filled in dst_mcc, dst_mnc, dst_lac and dst_ci, and the handover reference is filled in hd_ref.
[0069] The present invention backfills the user identity (IMSI and MSISDN) into the A interface switching record, so that user-level analysis can be performed on the A interface switching record without the user ID, and then the association analysis of SRVCC / eSRVCC services is extended to the A interface .
PUM
Login to View More Abstract
Description
Claims
Application Information
Login to View More 


