CN110324789B

CN110324789B - Method and device for acquiring VoLTE user position track information

Info

Publication number: CN110324789B
Application number: CN201910619900.7A
Authority: CN
Inventors: 范传庆; 叶志钢; 张本军; 胡文波; 杨晓兵; 张冉
Original assignee: Wuhan Greenet Information Service Co Ltd
Current assignee: Wuhan Greenet Information Service Co Ltd
Priority date: 2019-07-10
Filing date: 2019-07-10
Publication date: 2021-05-07
Anticipated expiration: 2039-07-10
Also published as: CN110324789A

Abstract

The invention relates to the technical field of network communication, in particular to a method and a device for acquiring VoLTE user position track information, wherein the method comprises the following steps: acquiring a plurality of interface data related to position information in a calling process of a user in a VoLTE network; performing correlation analysis on the collected interface data to form a user position information pool; acquiring user position information from the user position information pool in sequence according to the time sequence to obtain a position track in the user calling process; wherein the plurality of interface data comprises: UU, S1-MME, S6a, GM, and Rx interface data. According to the invention, the cell field information carried by different interfaces can be obtained by performing correlation analysis on the multi-interface data of the VOLTE single user, and the position track information in the user calling process can be obtained by reading the information according to the time sequence, so that the problem points existing in the user moving process can be found, and the existing network can be further optimized.

Description

Method and device for acquiring VoLTE user position track information

[ technical field ] A method for producing a semiconductor device

The invention relates to the technical field of network communication, in particular to a method and a device for acquiring VoLTE user position track information.

[ background of the invention ]

Volte (voice over lte) is a voice service based on IMS, and specifically is an IP data transmission technology, and all services are carried on a 4G network without a 2G/3G network, so that unification of data and voice services in the same network can be achieved. In other words, the 4G network not only provides high-rate data services, but also provides high-quality audio and video calls, and the latter requires VoLTE technology to implement.

Most of the existing position information obtaining methods in the call process of the VoLTE user obtain the initial position information from the signaling of the single interface (Mw interface or GM interface) in the IMS domain, that is, a single interface ticket is generated from the time when the interface receives the first Invite message and the time when the interface receives the 200 OK for bye response message. The calling side cell location information acquisition mode is as follows: a field with "utran-cell-id-3 gpp" in a P-Access-Network-Info field of a request message (e.g., Invite request message) is taken, for example, utran-cell-id-3gpp ═ 4600025242A1FC01, the TAI bit of 460002524 is ignored, the value of the next bit 2A1FC01 is extracted, or the cell information value is backfilled by associating records in Rx and Gx interfaces with the calling number. The called side cell location information is obtained as follows: and (3) taking a field with 'utran-cell-id-3 gpp' in a P-Access-Network-Info field in the first response message carrying the P-Access-Network-Info, for example, the field with the 'utran-cell-id-3 gpp' is 4600025242A1FC01, ignoring the TAI bit of 460002524, extracting the value of the next bit 2A1FC01, or associating records in Rx and Gx interfaces through a called number, and backfilling the cell information value.

However, when the VoLTE user uses the voice service, the location information acquiring method can only acquire the location information of the initial cell of the information of the calling and called users, and when the location cell of the user is switched in the calling process, the traditional method cannot accurately acquire the location information of all cells of the user, that is, cannot acquire the location track information of the VoLTE user in the calling process. This is because a single interface only records cell information of the initial position, and if the position cell changes during the user session, different switching types pass through different logical interfaces, the carried cell information is also different, and the moving position trajectory of the user can be represented only by associating a plurality of interfaces.

In view of the above, it is an urgent problem in the art to overcome the above-mentioned drawbacks of the prior art.

[ summary of the invention ]

The technical problems to be solved by the invention are as follows:

when a VoLTE user uses a voice service, the traditional position information acquisition method adopts a single interface, and can only acquire the position information of the initial cell of the information of the calling party and the called party, and when the user switches the position cells in the calling process, the position information of all the cells of the VoLTE user cannot be accurately acquired.

The invention achieves the above purpose by the following technical scheme:

in a first aspect, the present invention provides a method for acquiring VoLTE user location track information, including:

acquiring a plurality of interface data related to position information in a calling process of a user in a VoLTE network;

performing correlation analysis on the collected interface data to form a user position information pool;

and sequentially acquiring user position information from the user position information pool according to the time sequence to obtain a position track in the user calling process.

Preferably, the plurality of interface data related to the location information during the user call includes:

UU interface data, S1-MME interface data, S6a interface data, GM interface data, and Rx interface data.

Preferably, the correlation analysis is performed on the collected multiple interface data, specifically:

performing correlated backfill on the collected multiple interface data to obtain a Gm interface ticket, an S1-MME interface ticket and a UU interface ticket;

and performing associated backfill of interface data among the Gm interface ticket, the S1-MME interface ticket and the UU interface ticket.

Preferably, the performing associated backfill on the collected multiple interface data to obtain a Gm interface ticket, an S1-MME interface ticket, and a UU interface ticket specifically includes:

carrying out data association on the Gm interface and the Rx interface, backfilling cell ECI information of the Rx interface into a Gm interface ticket after the association is successful, and generating a unique user group ID on the Gm interface;

performing data association on the S1-MME interface and the S6a interface, and backfilling the user identification of the S6a interface into an S1-MME interface ticket after the association is successful; wherein the subscriber identity comprises the MSISDN code and/or IMSI code of the subscriber;

and decoding the collected UU interface data to form a corresponding UU interface ticket.

Preferably, the Gm interface and the Rx interface perform data association through a user identifier, and if the user identifiers of the two interface data are the same within a first preset time range, the association is successful;

and the S1-MME interface and the S6a interface perform data association through GUTI fields, and if the GUTI fields of the data of the two interfaces are the same in a second preset time range, the association is successful.

Preferably, the backfilling of the association of the interface data among the Gm interface ticket, the S1-MME interface ticket, and the UU interface ticket specifically includes:

performing data association on the Gm interface and the S1-MME interface, and backfilling the unique user group ID in the Gm interface ticket into the S1-MME interface ticket after the association is successful;

and performing data association on the UU interface and the S1-MME interface, and backfilling the unique user group ID in the S1-MME interface ticket into the UU interface ticket after the association is successful.

Preferably, the Gm interface and the S1-MME interface perform data association through a user identifier, and if the user identifiers of the two interface data are the same within a third preset time range, the association is successful;

and the UU interface and the S1-MME interface perform data association through the S1AP ID of the MME UE, and if the S1AP ID of the MME UE of the data of the two interfaces is the same in the fourth preset time range, the association is successful.

Preferably, the user location information pool includes Gm interface ticket information, S1-MME interface ticket information, and UU interface ticket information, and each interface ticket information includes one or more of a user group ID, a start time, an end time, a user MSISDN, a user IMSI, and a cell ECI.

Preferably, when a user performs a cell location handover during a call, the handover is divided into an intra-station handover and an inter-station handover, and the inter-station handover includes an x2 handover and an S1 handover.

In a second aspect, the present invention provides an apparatus for acquiring VoLTE user location track information, including at least one processor and a memory, where the at least one processor and the memory are connected through a data bus, and the memory stores instructions executable by the at least one processor, where the instructions are used to complete the method for acquiring VoLTE user location track information according to the first aspect after being executed by the processor.

The invention has the beneficial effects that:

according to the method, correlation analysis is carried out on the multi-interface data of the VOLTE single user, key information is extracted to form a user position information pool, cell field information carried by different interfaces can be obtained, and after the information is sequentially read according to a time sequence, all cell position information of the user in a voice service process can be obtained; compared with single interface analysis, when the user switches the position cell in the calling process, the invention can accurately acquire the position track of the user, thereby realizing the service track process of the user in the current network, being beneficial to finding the problem points of the user in the moving process and further optimizing the current network.

[ description of the drawings ]

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required to be used in the embodiments of the present invention will be briefly described below. It is obvious that the drawings described below are only some embodiments of the invention, and that for a person skilled in the art, other drawings can be derived from them without inventive effort.

Fig. 1 is a flowchart of a method for acquiring location track information of a VoLTE user according to an embodiment of the present invention;

fig. 2 is a schematic interface diagram in a VoLTE network according to an embodiment of the present invention;

FIG. 3 is a schematic diagram of collecting and correlating multi-interface data according to an embodiment of the present invention;

fig. 4 is a flowchart of a method for analyzing multi-interface data association according to an embodiment of the present invention;

fig. 5 is a schematic diagram of an association between a Gm interface and an Rx interface according to an embodiment of the present invention;

fig. 6 is a schematic diagram illustrating an association between an S1-MME interface and an S6a interface according to an embodiment of the present invention;

fig. 7 is a schematic diagram illustrating an association between a Gm interface and an S1-MME interface according to an embodiment of the present invention;

fig. 8 is a schematic diagram illustrating an association between a UU interface and an S1-MME interface according to an embodiment of the present invention;

fig. 9 is a flowchart of an intra-site handover in a user call process according to an embodiment of the present invention;

fig. 10 is a flowchart illustrating an X2 handover procedure during a user call according to an embodiment of the present invention;

fig. 11 is a flowchart illustrating an S1 handover procedure in a user call process according to an embodiment of the present invention;

fig. 12 is a diagram of an apparatus architecture for acquiring location track information of a VoLTE user according to an embodiment of the present invention.

[ detailed description ] embodiments

In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below 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 are not intended to limit the invention.

In the embodiments of the present invention, the symbol "/" indicates the meaning of having both functions, and the symbol "a and/or B" indicates that the combination between the preceding and following objects connected by the symbol includes three cases of "a", "B", "a and B".

In addition, the technical features involved in the embodiments of the present invention described below may be combined with each other as long as they do not conflict with each other. The invention will be described in detail below with reference to the figures and examples.

Example 1:

the embodiment of the invention provides a method for acquiring VoLTE user position track information, which can accurately acquire all cell position information of a user in a user calling process. As shown in fig. 1, the method provided in the embodiment of the present invention specifically includes:

step 201, a plurality of interface data related to the position information in the user calling process are collected in the VoLTE network.

Referring to fig. 2, there are multiple network elements in the VoLTE network, such as an MME (Mobility Management Entity) in the EPC domain, a PCRF (Policy and Charging Rules Function), and the like, and different network elements are connected through corresponding interfaces. Here, the collected interface data mainly related to the location information in the VoLTE user call process includes: UU interface data, S1-MME interface data, S6a interface data, GM interface data, and Rx interface data. When the interface data is collected, the corresponding data collection methods may be different due to the difference between different interfaces; for example, the information can be collected by means of a hardware acquisition card on the transmission side, and by means of software on the operation and maintenance center side.

The selection of the above interface data is due to the following considerations: when a user performs cell location switching during a call, the cell location switching is divided into intra-station switching and inter-station switching, and the inter-station switching comprises x2 switching and S1 switching. Different switching types are different in signaling process in different interfaces, for example, when a user has a session service in the process of high-speed movement, in order to ensure the user session experience, a user terminal needs to continuously switch a position cell to select different base stations for service, and after a user starts a call, the user can pass through a plurality of cells and a plurality of base stations to generate different switching types, so that different interfaces need to be selected to inquire the position information of the user cell. The UU interface carries the information of the switching cell in the user station; the S1-MME interface carries cell information of X2 and S1 switching, but the S1-MME interface may not have user identification information and needs to associate the S6 interface to backfill part of user information; the GM interface carries user information but may not carry user cell information, and the RX interface is required to be associated to backfill cell information; therefore, the interface data to be collected finally is as described above.

Step 202, performing correlation analysis on the collected multiple interface data to form a user position information pool.

Referring to fig. 3, a plurality of interface data (i.e., the raw data of the UU interface, the S1-MME interface, the S6a interface, the GM interface, and the Rx interface) collected in step 202 are decoded and backfilled in association, and a unique user single service identifier is added to obtain a required GM interface ticket, a S1-MME interface ticket, and a UU interface ticket; and performing associated backfill of interface data among the Gm interface ticket, the S1-MME interface ticket and the UU interface ticket, and adding a unique user single service identifier so as to extract key information to form a user position information pool. The UU interface ticket is formed directly after decoding collected UU interface data, the Gm interface ticket is formed after data association is carried out on a GM interface and an Rx interface, and the S1-MME interface ticket is formed after data association is carried out on an S1-MME interface and an S6a interface.

With reference to fig. 3, the user location information pool includes Gm interface ticket information, S1-MME interface ticket information, and UU interface ticket information, where each interface ticket information includes one or more of a user group ID, a start time, an end time, an MSISDN (Mobile station International ISDN number) of a user Mobile phone number, an IMSI (International Mobile Subscriber identity) of the user Mobile phone number, and a cell ECI; during a call, the MSISDN and IMSI may correspond uniquely. The data in the user position information pool are all information useful for subsequent analysis of the user cell position, extraction is not needed for the information useless for position analysis, and the efficiency of position track analysis can be effectively improved by performing targeted information extraction.

And 203, sequentially acquiring user position information from the user position information pool according to the time sequence to obtain a position track in the user calling process.

The cell field information carried by each relevant interface is acquired and counted in a user position information pool, and can be arranged according to a time ascending sequence, and the user position information is sequentially read according to the time sequence, and the adjacent repeated cell position information is subjected to duplication elimination, so that all cell position information of the user in the calling process can be acquired, and the position track information of the user is acquired.

For example, a user carries information of a call-initiating cell in a call-initiating phase, the information of the call-initiating cell has related location information on a GM interface and an RX interface, but when the user performs an in-station handover, the location information of the cell changes, and new location information exists on a UU interface, so that the information of the cell after the handover can be obtained through the information of the UU interface; similarly, when S1 or X2 handover occurs, related signaling carries the information of the location cell after handover in the S1MME interface, and there is no location information of the handover in the UU interface and the interfaces such as GM and MW.

With further reference to fig. 4, the performing a correlation analysis on the collected multiple interface data, namely step 202, specifically includes:

step 2021, performing data association between the Gm interface and the Rx interface, backfilling cell ECI information of the Rx interface into a Gm interface ticket after the association is successful, and generating a unique user group ID at the Gm interface.

The Gm interface data and the Rx interface data each at least include a subscriber identity, which is an MSISDN number and/or an IMSI number of the subscriber. Referring to fig. 5, the Gm interface and the Rx interface perform data association through the user identifier, and if the user identifiers of the two interface data are the same within a first preset time range, the association is successful; and after the association is successful, if the Gm interface has no cell ECI information, supplementing the cell ECI information of the Rx interface to the Gm interface, and generating a unique user group ID (user group unique identifier) on the Gm interface. The first preset time range and each of the following preset time ranges are obtained according to an actual current network experience value, and are not specifically limited herein; here, the first preset time range is usually 2s, and if the user identifiers of the Gm interface data and the Rx interface data are the same within 2s, the association is successful.

Step 2022, data association is performed between the S1-MME interface and the S6a interface, and after the association is successful, the user identifier of the S6a interface is backfilled into the S1-MME interface ticket.

The S1-MME interface data and the S6a interface data each include at least a GUTI (Globally Unique Temporary UE Identity) field consisting of mcc + mnc + MME _ code + m-tmsi. Referring to fig. 6, the S1-MME interface and the S6a interface perform data association through the GUTI field, and if the GUTI fields of the two interface data are the same within a second preset time range, the association is successful; and after the association is successful, the MSISDN and/or IMSI of the S6a interface is supplemented to the S1-MME interface, and a unique user group ID is not required to be added at the stage. Here, the second predetermined time range is usually 4S, and if the S1-MME interface data is the same as the GUTI field of the S6a interface data in 4S, the association is successful.

Step 2023, performing data association between the Gm interface and the S1-MME interface, and backfilling the unique user group ID in the Gm interface ticket into the S1-MME interface ticket after the association is successful.

The Gm interface data and the S1-MME interface data each include at least a subscriber identity, which is the MSISDN number and/or IMSI number of the subscriber. Referring to fig. 7, the Gm interface and the S1-MME interface perform data association through the user identifier, and if the user identifiers of the two interface data are the same within a third preset time range, the association is successful; and supplementing the user group ID of the Gm interface to the S1-MME interface after the association is successful. Here, the third preset time range is usually 2S, and if the user identifier of the Gm interface data is the same as that of the S1-MME interface data within 2S, the association is successful.

Step 2024, performing data association between the UU interface and the S1-MME interface, and backfilling the unique user group ID in the S1-MME interface ticket into the UU interface ticket after the association is successful.

The UU interface data and the S1-MME interface data both include at least MME UE S1AP ID, and with reference to fig. 8, the UU interface and the S1-MME interface perform data association through MME UE S1AP ID, and if the MME UE S1AP ID of the two interface data are the same within the fourth preset time range, the association is successful; and supplementing the user group ID of the S1-MME interface to the UU interface after the association is successful. The fourth preset time range is usually 4S, and if the UU interface data is the same as the MME UE S1AP ID identification of the S1-MME interface data within 4S, the association is successful.

Through the

step

2021 and 2024, association analysis is performed on the collected UU, S1-MME, S6a, Gm, Rx interface signaling data, a single service identifier unique to the user is added, a user location information pool can be formed according to the associated multi-interface data, and cell field information in the information pool is obtained in time sequence, that is, cell handover information of the user can be obtained, so as to obtain a location track.

The method provided by the embodiment of the invention can be used in the scene that the VOLTE user has cell switching in the calling process: when a user using network service moves from one cell to another cell, or due to the adjustment of wireless transmission service load, the activation of operation maintenance, equipment failure, etc., in order to ensure the continuity of communication and the quality of service, the system transfers the communication link between the user and the original cell to a new cell, which is a handover process. The cell handover described herein is an intra-LTE system handover, and the inter-system handover requires UE (User Equipment) support, which is not described in detail herein. In the LTE system, the handover can be divided into intra-station handover and inter-station handover (based on X2 port handover or based on S1 port handover).

The switching principle is as follows: firstly, switching judgment preparation (measurement report control and measurement report reporting), wherein a base station sends different types of measurement tasks to UE by using a mobility management algorithm according to different requirements, and sends measurement configuration to the UE by carrying a MeasConfig cell in an RRC reconfiguration message; the UE measures the measurement object after receiving the configuration information, evaluates the result by using the measurement reporting standard, and sends a corresponding measurement report to the base station when the evaluation measurement result meets the reporting standard, such as events of A2\ A3 and the like; the base station judges whether to execute switching or not through a measurement report reported by the terminal. When the decision condition is reached, the following steps are performed: firstly, switching preparation, namely the target network completes resource reservation; secondly, switching execution, namely the source base station informs the UE to execute switching, and the UE completes connection on the target base station; and thirdly, the switching is completed, namely the source base station releases resources and links and deletes the user information. It is noted that in LTE systems, the handover command is encapsulated in a message RRC _ CONN _ RECFG signaling message. The following describes the procedures of intra-station handover and inter-station handover in detail.

A. In-site switching

An intra-eNB handover occurs when the source cell in which the UE is located and the target cell to be handed over belong to the same base station eNB. The intra-eNB handover is the simplest one in various situations, because the information interaction between the eNB and the eNB is not involved in the handover process, that is, there is no signaling operation on the X2 and S1 interfaces, and only resource allocation is performed between two cells in one eNB, the base station makes an internal decision, and does not need to apply for changing the data transmission path to the core network. As shown in fig. 9, the intra-station handover process specifically includes the following steps:

step 301, the eNB issues measurement control to the UE, and configures the measurement type of the UE through an RRC Connection reconfiguration message. According to different UE, the measurement types can be divided into co-frequency measurement, pilot frequency measurement and Inter-RAT measurement, the co-frequency measurement refers to measurement on a downlink carrier frequency of a serving cell, and the pilot frequency measurement refers to measurement on a downlink carrier frequency different from the serving cell.

Step 302, the UE performs measurement configuration at the RRC protocol end of the UE according to the measurement control issued by the eNB, and sends an RRC Connection reconfiguration Complete message to the eNB, indicating that the measurement configuration is completed.

Step 303, the UE reports a measurement Report to the eNB according to the measurement configuration.

And step 304, the eNB judges according to the measurement report, judges that the UE is to be switched in the eNB, then carries out resource admission in the target cell, and applies for new air interface resources for the UE after the resource admission is successful. The measurement report includes information about whether the cell belongs to one base station, and if the handover cell is in the same base station, the handover is ready for the intra-station handover.

Step 305, after the resource application is successful, the eNB sends an RRC Connection reconfiguration message to the UE, instructing the UE to initiate a handover action.

Step 306, after the UE accesses the target cell, the UE sends an RRC Connection reconfiguration Complete message to the eNB to indicate that the UE has accessed the target cell.

Step 307, after receiving the reconfiguration complete message, the eNB releases the resource occupied by the UE in the source cell.

Wherein, step 301-.

B. Inter-station handover

When the source cell where the UE is located and the target cell to be handed over do not belong to the same base station eNB, inter-eNB handover occurs, the inter-eNB handover procedure is complex, and signaling operations of X2 and S1 interfaces need to be added. Wherein, when the data configuration of the X2 interface is perfect and the operation is good, the X2 handover will occur, otherwise, the S1 handover will occur between the base stations, that is, the precondition of the X2 handover is that the target base station and the source base station configure an X2 link and the link is available. Generally, the priority of the X2 switching is higher than that of the S1 switching, so that the switching delay is shorter and the user perception is better.

For the X2 handover, all inter-station interactive signaling and data forwarding need to be forwarded to a core network through an X2 interface, and after receiving a measurement report, a handover application needs to be sent to a target cell through an X2 interface; after the feedback of the target cell is obtained (at the moment, the resource preparation of the target cell is completed), a switching command is sent to the terminal, and an SNStatus Transfer message with information such as data packet cache, data packet cache numbers and the like is sent to a target side; after the UE is accessed in the target cell, the target cell sends a path change request to the core network, so as to inform the core network to transfer the service of the terminal to the target cell and update the node relation between the user plane and the control plane; after the handover is successful, the target eNB notifies the source eNB to release the radio resources. As shown in fig. 10, the flow of X2 switching is specifically as follows:

step 401, the source eNB issues measurement control to the UE, and configures the measurement type of the UE through an RRC Connection reconfiguration message.

Step 402, the UE performs measurement configuration at the RRC protocol end of the UE according to the measurement control issued by the source eNB, and sends an RRC Connection reconfiguration Complete message to the source eNB, indicating that the measurement configuration is completed.

In step 403, the UE reports a measurement Report to the source eNB according to the measurement configuration.

And step 404, the source eNB judges according to the measurement report, and judges that the UE is switched among eNBs. The measurement report includes information about whether the cells belong to the same base station, and if the handover cells are not in the same base station, the handover between stations is prepared, and possibly the reason for load sharing triggers the handover.

Step 405, the source eNB sends a HANDOVER REQUEST message to the target eNB to instruct the target eNB to prepare for HANDOVER, and the target eNB starts admission processing on ERABs to be handed over after receiving the HANDOVER REQUEST message. The handover request message includes an Old eNB UE X2AP ID allocated by the source eNB, an MME UE S1AP ID allocated by the MME, an EPS bearer list to be established, and an address of data transmission on the core network side corresponding to each EPS bearer.

Step 406, the target cell performs resource admission, and allocates air interface resources and SAE bearer resources of services for the access of the UE.

Step 407, after the target cell resource is successfully admitted, the target eNB sends a HANDOVER request acknowledge message HANDOVER request nowldewledge to the source eNB, indicating that the HANDOVER preparation work is completed. The handover request acknowledgement message includes New eNB UE X2AP ID, Old eNB UE X2AP ID, New EPS bearer corresponding to the address of uplink and downlink data transmission at the D side, and dedicated access signature allocated at the target side.

Step 408, the source eNB configures the allocated dedicated access signature to the UE, sends an RRC Connection reconfiguration message to the UE, and instructs the UE to perform a handover action.

Step 409, the UE sends an RRC Connection reconfiguration Complete message to the target eNB, indicating that the UE has accessed the target cell, i.e. the UE has been handed over to the target side; at the same time, the forwarding of traffic data during the handover begins.

In step 410, the target eNB sends PATH SWITCH a REQUEST message REQUEST to the MME requesting the MME to update the node address of the traffic data channel and informing the MME to switch the connection path of the traffic data from the source eNB to the target eNB. The request message includes the MME UE S1AP ID of the source side, the eNB UE S1AP allocated by the target side, the downlink address to be used by the EPS bearer on the target side, and the like.

In step 411, after the MME successfully updates the data PATH node address, it sends a PATH switch request node edge message to the target eNB, indicating that service communication can be performed on the new SAE routers.

Step 412, the target eNB sends a UE context message to the source eNB to prompt the source eNB to access the new cell at the UE, and release the resource occupied in the source cell after the new cell can perform service communication.

Step 413, the source eNB releases the context of the UE, including air interface resources and SAE bearers resources.

Wherein, step 401-.

For the S1 handover, it is similar to the X2 handover, except that all inter-station interactive signaling and data forwarding need to be forwarded to the core network through the S1 port, and the time delay is slightly larger than that of the X2 port. The protocol 36.300 specifies that inter-eNB handover is generally performed over the X2 interface, but that inter-eNB handover over the S1 interface is triggered when any of the following conditions is met: the first is that no X2 interface exists between the source eNB and the target eNB; the second is that the source eNB attempts handover over the X2 interface but is rejected by the target eNB.

From the LTE network structure, the S1 interface between two enbs and the MME together with the MME entity can be regarded as a logical X2 interface, and compared with the X2 handover, the flow of the S1 handover is different between the handover preparation process and the handover completion process. Preconditions for S1 switching are as follows: the target base station and the source base station are not provided with an X2 link or a configured X2 link is unavailable; if both X2 and S1 links are configured, the X2 handoff is prioritized. As shown in fig. 11, the switching flow of S1 is specifically as follows:

step 501, the source eNB issues measurement control to the UE, and configures the measurement type of the UE through an RRC Connection reconfiguration message.

Step 502, the UE performs measurement configuration at the RRC protocol end of the UE according to the measurement control issued by the source eNB, and sends an RRC Connection reconfiguration Complete message to the source eNB, indicating that the measurement configuration is completed.

Step 503, the UE reports a measurement Report to the source eNB according to the measurement configuration.

And step 504, the source eNB judges according to the measurement report, and judges that the UE is switched among eNBs.

In step 505, the source eNB sends a HANDOVER request message to the MME via the S1 interface, where the message includes information such as MME UE S1AP ID and eNB UE S1AP ID assigned by the source side.

Step 506, the MME sends a HANDOVER REQUEST message to the target eNB to indicate the target eNB to prepare for HANDOVER; the message includes MME UE S1AP ID allocated by the MME, an EPS list to be established, and parameters such as an address for core network side data transmission corresponding to each EPS bearer.

Step 507, the target cell performs resource admission, and allocates air interface resources and service bearing resources for the access of the UE.

Step 508, after the target cell resource is successfully admitted, the target eNB sends a HANDOVER REQUEST ACKNOWLEDGE message to the MME, including parameters such as the eNB S1AP ID allocated by the target side, and the eNB side data transfer address corresponding to the EPS bearer successfully admitted.

Step 509, the MME sends a HANDOVER COMMAND message to the source eNB, and after receiving the message, the source eNB learns the bearer information successfully admitted and the destination address of the service data forwarding during the HANDOVER.

In step 510, the source eNB sends an RRC Connection Reconfiguration message to the UE, instructing the UE to switch to the designated target cell.

Step 511, the UE sends an RRC Connection reconfiguration Complete message to the target eNB, indicating that the UE has accessed the target cell; the target eNB receives the message indicating that the handover was successful.

Step 512, the target eNB sends PATH SWITCH a REQUEST message REQUEST to the MME requesting the MME to update the node address of the traffic data channel, and notifies the MME to switch the connection path of the traffic data from the source eNB to the target eNB. The request message includes the MME UE S1AP ID of the source side, the eNB UE S1AP allocated by the target side, the downlink address to be used by the EPS bearer on the target side, and the like.

Step 513, after the MME successfully updates the data tunnel node address, the MME sends PATH SWITCH a request for uplink traffic edge message to the target eNB, indicating that traffic communication can be performed on the new SAE routers.

Step 514, the target eNB sends a HANDOVER NOTIFY message to the MME, notifying the MME that the UE has successfully accessed the target side.

Step 515, the target eNB sends a UE CONTEXT RELEASE COMMAND message to the source eNB, prompting the source eNB to access the new cell at the UE, and releasing the resource occupied in the source cell after the new cell can perform service communication.

In step 516, the source eNB releases the context of the UE, including air interface resources and SAE bearers resources.

Wherein, the step 501-509 is a handover preparation process, the step 510-511 is a handover execution process, and the step 512-516 is a handover completion process.

Example 2:

on the basis of the method for acquiring the location track information of the VoLTE user provided in embodiment 1, the present invention further provides a device for acquiring the location track information of the VoLTE user, which is capable of implementing the method, as shown in fig. 12, is a schematic diagram of a device architecture in an embodiment of the present invention. The apparatus for acquiring VoLTE user location track information of the present embodiment includes one or more processors 21 and a memory 22. In fig. 12, one processor 21 is taken as an example. The processor 21 and the memory 22 may be connected by a bus or other means, and fig. 12 illustrates the connection by a bus as an example.

The memory 22, as a non-volatile computer-readable storage medium for a method of acquiring VoLTE user location track information, may be used to store non-volatile software programs, non-volatile computer-executable programs, and modules, such as the method of acquiring VoLTE user location track information in embodiment 1. The processor 21 executes various functional applications and data processing of the apparatus for acquiring VoLTE user location trajectory information by running the nonvolatile software program, instructions and modules stored in the memory 22, that is, implements the method for acquiring VoLTE user location trajectory information of embodiment 1.

The memory 22 may include high speed random access memory and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device. In some embodiments, the memory 22 may optionally include memory located remotely from the processor 21, and these remote memories may be connected to the processor 21 via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The program instructions/modules are stored in the memory 22 and when executed by the one or more processors 21, perform the method for acquiring VoLTE user location trajectory information in embodiment 1 above, for example, perform the steps illustrated in fig. 1 and 4 described above.

Those of ordinary skill in the art will appreciate that all or part of the steps of the various methods of the embodiments may be implemented by associated hardware as instructed by a program, which may be stored on a computer-readable storage medium, which may include: read Only Memory (ROM), Random Access Memory (RAM), magnetic or optical disks, and the like.

The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents and improvements made within the spirit and principle of the present invention are intended to be included within the scope of the present invention.

Claims

1. A method for acquiring VoLTE user position track information is characterized by comprising the following steps:

sequentially acquiring user position information from the user position information pool according to the time sequence, and removing the duplication of the position information of adjacent repeated cells to obtain a position track in the user calling process;

wherein the plurality of interface data related to the location information during the user call comprises: UU interface data, S1-MME interface data, S6a interface data, GM interface data and Rx interface data; performing correlation analysis on the collected multiple interface data to form a user position information pool specifically as follows:

respectively decoding and associated backfilling the collected interface data, and adding a unique user single service identifier to obtain a Gm interface ticket, an S1-MME interface ticket and a UU interface ticket; and then performing associated backfill of interface data among the Gm interface ticket, the S1-MME interface ticket and the UU interface ticket, and adding a unique user single service identifier so as to extract key information to form a user position information pool.

2. The method for acquiring the VoLTE user position track information according to claim 1, wherein the steps of respectively decoding and associated backfilling the collected interface data, adding a unique user single service identifier to obtain a Gm interface ticket, an S1-MME interface ticket and a UU interface ticket specifically comprise:

3. The method for acquiring the VoLTE user location track information according to claim 2, wherein the Gm interface and the Rx interface perform data association through a user identifier, and if the user identifiers of the two interface data are the same within a first preset time range, the association is successful;

4. The method for acquiring the VoLTE user location trajectory information according to claim 2, wherein the backfilling of the association of the interface data among the Gm interface ticket, the S1-MME interface ticket, and the UU interface ticket specifically comprises:

5. The method for acquiring VoLTE user location track information according to claim 4, wherein the Gm interface and the S1-MME interface perform data association through user identification, and if the user identifications of the two interface data are the same in a third preset time range, the association is successful;

6. The method for acquiring VoLTE user location trajectory information according to any of claims 1-5, wherein the user location information pool comprises Gm interface ticket information, S1-MME interface ticket information and UU interface ticket information, and each interface ticket information comprises one or more of a user group ID, a start time, an end time, a user MSISDN, a user IMSI and a cell ECI.

7. The method for acquiring VoLTE user location track information as claimed in any of claims 1-5, wherein when the user performs cell location handover during the call, the handover is divided into intra-station handover and inter-station handover, and the inter-station handover includes x2 handover and S1 handover.

8. An apparatus for acquiring VoLTE user location track information, comprising at least one processor and a memory, wherein the at least one processor and the memory are connected through a data bus, and the memory stores instructions executable by the at least one processor, and the instructions are used for completing the method for acquiring VoLTE user location track information according to any one of claims 1 to 7 after being executed by the processor.