CN113115202A

CN113115202A - Method and device for acquiring longitude and latitude information of terminal equipment

Info

Publication number: CN113115202A
Application number: CN202110309622.2A
Authority: CN
Inventors: 金雨超; 李京辉; 郭省力; 李德屹; 程新洲
Original assignee: China United Network Communications Group Co Ltd
Current assignee: China United Network Communications Group Co Ltd
Priority date: 2021-03-23
Filing date: 2021-03-23
Publication date: 2021-07-13
Anticipated expiration: 2041-03-23
Also published as: CN113115202B

Abstract

The application provides a method and a device for acquiring longitude and latitude information of a terminal device, relates to the field of communication, and can acquire the longitude and latitude information of the terminal device from MR data in a 5G network scene. The method comprises the following steps: the following information is obtained for a first time period: a measurement report MR, first call bill data of at least one first terminal device and second call bill data of at least one first terminal device; determining target MR data; determining first target call ticket data, wherein the first target call ticket data is the first call ticket data of at least one first terminal device, and the first call ticket data and the target MR data have the same AMF UE NGAP ID; determining second target call bill data, wherein the second target call bill data is the second call bill data which has the same TLI (transport layer identity) as the first target call bill data in the second call bill data of at least one first terminal device; and adding the longitude and latitude information in the second target ticket data into the target MR data.

Description

Method and device for acquiring longitude and latitude information of terminal equipment

Technical Field

The present application relates to the field of communications, and in particular, to a method and an apparatus for acquiring longitude and latitude information of a terminal device.

Background

Currently, when evaluating network coverage of a specified area, it is necessary to obtain longitude and latitude information of the specified area, so that network coverage of the specified area can be evaluated by obtaining received signal strength or received signal quality index of the specified area.

In the prior art, a method for acquiring latitude and longitude information of a terminal device is to acquire the latitude and longitude information from a Measurement Report (MR), but the latitude and longitude information serving as a field is reported in an MR data source and simultaneously meets two conditions, one of which is that a terminal chip supports the function of reporting the latitude and longitude information; and secondly, a wireless network element (base station) connected with the terminal equipment starts an MR (magnetic resonance) collection function with longitude and latitude information. However, in a 5G SA network, the terminal chip of the 5G SA does not support the function of reporting latitude and longitude information, that is, the above condition cannot be satisfied, and therefore, in the 5G network of the SA networking architecture, latitude and longitude information of the terminal device of the 5G SA network cannot be acquired from the reported MR data.

Disclosure of Invention

The application provides a method and a device for acquiring longitude and latitude information of terminal equipment, which can acquire the longitude and latitude information of the terminal equipment from MR data in a 5G network scene.

In order to achieve the purpose, the technical scheme is as follows:

in a first aspect, the present application provides a method for acquiring latitude and longitude information of a terminal device, including: the following information is obtained for a first time period: a measurement report MR, first call ticket data of at least one first terminal device and second call ticket data of at least one first terminal device; the MR comprises MR data of at least one second terminal device, the MR data comprises an authentication management function terminal application layer signaling protocol identifier AMF UE NGAP ID, the first ticket data comprises TLI and AMF UE NGAP ID, the TLI is composed of a fifth generation network base station gNodeB user plane network protocol address and a gNodeB user plane tunnel endpoint identifier, the second ticket data comprises TLI and latitude and longitude information, the at least one first terminal device is part or all of a plurality of terminal devices connected with a plurality of access network devices, and the at least one second terminal device is part or all of a plurality of terminal devices connected with one access network device; determining target MR data, wherein the target MR data is one of the MR data of at least one second terminal device; determining first target call ticket data, wherein the first target call ticket data is the first call ticket data of at least one first terminal device, and the first call ticket data and the target MR data have the same AMF UE NGAP ID; determining second target call bill data, wherein the second target call bill data is the second call bill data which has the same TLI (transport layer identity) as the first target call bill data in the second call bill data of at least one first terminal device; and adding the longitude and latitude information in the second target ticket data into the target MR data.

Based on the technical scheme, according to the method for acquiring longitude and latitude information of the terminal device, the MR data and the second phone bill data are associated through the first phone bill data, so that the longitude and latitude information in the second phone bill data can be added into the MR data, and under a 5G network architecture, if the network coverage quality of a specified area needs to be evaluated or an area with poor network coverage needs to be optimized, the specified area or the area with poor network coverage can be determined through acquiring the longitude and latitude information in the MR data, so that the coverage condition in a specified position range can be analyzed, the area with poor coverage quality can also be positioned, the evaluation of the network coverage quality is facilitated, and the optimization of the area with poor coverage quality is also facilitated.

In a possible implementation manner, the latitude and longitude information in the second target ticket data is obtained from the core network side when the terminal device uses the service. In this implementation manner, when the terminal device uses a service, the latitude and longitude information can be acquired from the core network side, and a precondition is provided for subsequently adding the latitude and longitude information to the MR data.

In a possible implementation manner, the second target ticket data further includes a user permanent identity SUPI, and in the process of adding the latitude and longitude information in the second target ticket data to the target MR data, the method further includes: and adding the SUPI in the second target ticket data to the target MR data. In the implementation mode, the computing device associates the second target ticket data with the target MR data through the first target ticket data, and can also add the SUPI in the second target ticket data to the target MR data, so that the terminal device can be identified according to the permanent identifier in the following process, and inconvenience caused by timeliness of the temporary identifier is avoided.

In a possible implementation manner, before adding the latitude and longitude information in the second target ticket data to the target MR data, the method further includes: judging whether the first target call ticket data, the second target call ticket data and the target MR data meet preset conditions, wherein the preset conditions comprise: the ending time of the first target ticket data is less than the starting time of the second target ticket data, and the starting time of the first target ticket data and the second target ticket data is in the time period of the target MR data; if so, adding the longitude and latitude information in the second target ticket data into the target MR data; if not, acquiring the following information in the second time period: MR, first call ticket data of at least one first terminal device and second call ticket data of at least one first terminal device; and adding longitude and latitude information into the MR data according to the MR in the second time period, the first call ticket data of at least one first terminal device and the second call ticket data of at least one first terminal device. In the implementation mode, the start time of the first target ticket data and the start time of the second target ticket data are limited within the sampling period of the target MR data, and the end time of the first target ticket data is less than the start time of the second target ticket data, so that the information in the first target ticket data, the second target ticket data and the target MR data can be effective, the problem of information addition error caused by information failure in the data is avoided, and the accuracy of the added information is effectively improved.

In a second aspect, the present application provides a latitude and longitude information acquiring apparatus for a terminal device, the apparatus comprising: a communication unit and a processing unit; a communication unit for acquiring the following information within a first time period: a measurement report MR, first call ticket data of at least one first terminal device and second call ticket data of at least one first terminal device; the MR comprises MR data of at least one second terminal device, the MR data comprises an authentication management function terminal application layer signaling protocol identifier AMF UE NGAP ID, the first ticket data comprises TLI and AMF UE NGAP ID, the TLI is composed of a fifth generation network base station gNodeB user plane network protocol address and a gNodeB user plane tunnel endpoint identifier, the second ticket data comprises TLI and latitude and longitude information, the at least one first terminal device is part or all of a plurality of terminal devices connected with a plurality of access network devices, and the at least one second terminal device is part or all of a plurality of terminal devices connected with one access network device; a processing unit for determining target MR data, the target MR data being one of MR data of at least one second terminal device; the processing unit is further used for determining first target call ticket data, wherein the first target call ticket data is the first call ticket data of at least one first terminal device, and the first call ticket data has the same AMF UE NGAP ID as the target MR data; the processing unit is further used for determining second target call ticket data, wherein the second target call ticket data is second call ticket data which has the same TLI (transport layer identity) as the first target call ticket data in the second call ticket data of at least one first terminal device; and the processing unit is also used for adding the longitude and latitude information in the second target ticket data into the target MR data.

In a possible implementation manner, the latitude and longitude information in the second target ticket data is obtained from the core network side when the terminal device uses the service.

In a possible implementation manner, the second target ticket data further includes a user permanent identifier SUPI, and in the process of adding the latitude and longitude information in the second target ticket data to the target MR data, the processing unit is further configured to: and adding the SUPI in the second target ticket data to the target MR data.

In a possible implementation manner, before adding the latitude and longitude information in the second target ticket data to the target MR data, the processing unit is further configured to: judging whether the first target call ticket data, the second target call ticket data and the target MR data meet preset conditions, wherein the preset conditions comprise: the ending time of the first target ticket data is less than the starting time of the second target ticket data, and the starting time of the first target ticket data and the second target ticket data is in the time period of the target MR data; if so, adding the longitude and latitude information in the second target ticket data into the target MR data; if not, the following information in the second time period is acquired through the communication unit: MR, first call ticket data of at least one first terminal device and second call ticket data of at least one first terminal device; and adding longitude and latitude information into the MR data according to the MR in the second time period, the first call ticket data of at least one first terminal device and the second call ticket data of at least one first terminal device.

In a third aspect, the present application provides a device for acquiring longitude and latitude information of a terminal device, where the device includes: a processor and a communication interface; the communication interface is coupled to a processor, and the processor is configured to execute a computer program or instructions to implement the method for acquiring latitude and longitude information of a terminal device as described in the first aspect and any one of the possible implementations of the first aspect.

In a fourth aspect, the present application provides a computer-readable storage medium, where instructions are stored, and when the instructions are executed on a terminal, the terminal is caused to execute the method for acquiring latitude and longitude information of a terminal device as described in the first aspect and any possible implementation manner of the first aspect.

In a fifth aspect, an embodiment of the present application provides a computer program product including instructions, which, when running on a latitude and longitude information acquisition device of a terminal device, causes the latitude and longitude information acquisition device of the terminal device to execute the latitude and longitude information acquisition method of the terminal device as described in the first aspect and any possible implementation manner of the first aspect.

In a sixth aspect, an embodiment of the present application provides a chip, where the chip includes a processor and a communication interface, where the communication interface is coupled to the processor, and the processor is configured to run a computer program or an instruction to implement the method for acquiring latitude and longitude information of a terminal device as described in the first aspect and any possible implementation manner of the first aspect.

In particular, the chip provided in the embodiments of the present application further includes a memory for storing a computer program or instructions.

Drawings

Fig. 1 is a schematic diagram illustrating establishment of a user plane transport bearer according to an embodiment of the present application;

fig. 2 is a structural diagram of a latitude and longitude information acquisition device of a terminal device according to an embodiment of the present application;

fig. 3 is an architecture diagram of a 5G network according to an embodiment of the present application;

fig. 4 is a flowchart of a method for acquiring latitude and longitude information of a terminal device according to an embodiment of the present application;

fig. 5 is a flowchart of another method for acquiring latitude and longitude information of a terminal device according to an embodiment of the present application;

fig. 6 is a flowchart of another method for acquiring latitude and longitude information of a terminal device according to an embodiment of the present application;

fig. 7 is a schematic diagram of an example of satisfying a preset rule according to an embodiment of the present application;

fig. 8 is a schematic diagram of an example that does not satisfy a preset rule according to an embodiment of the present application;

fig. 9 is a flowchart of another method for acquiring latitude and longitude information of a terminal device according to an embodiment of the present application;

FIG. 10 is a schematic diagram of association data provided by an embodiment of the present application;

FIG. 11 is a schematic diagram of another related data provided by an embodiment of the present application;

FIG. 12 is a schematic diagram of another related data provided in an embodiment of the present application;

fig. 13 is a schematic structural diagram of a latitude and longitude information acquiring apparatus of a terminal device according to an embodiment of the present invention;

fig. 14 is a schematic structural diagram of an electronic device according to an embodiment of the present invention;

fig. 15 is a schematic structural diagram of another electronic device according to an embodiment of the present invention.

Detailed Description

The method and the device for acquiring latitude and longitude information of a terminal device according to the embodiments of the present application are described in detail below with reference to the accompanying drawings.

The term "and/or" herein is merely an association describing an associated object, meaning that three relationships may exist, e.g., a and/or B, may mean: a exists alone, A and B exist simultaneously, and B exists alone.

The terms "first" and "second" and the like in the description and drawings of the present application are used for distinguishing different objects or for distinguishing different processes for the same object, and are not used for describing a specific order of the objects.

Furthermore, the terms "including" and "having," and any variations thereof, as referred to in the description of the present application, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements but may alternatively include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

It should be noted that in the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or explanations. Any embodiment or design described herein as "exemplary" or "e.g.," is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word "exemplary" or "such as" is intended to present concepts related in a concrete fashion.

In the description of the present application, the meaning of "a plurality" means two or more unless otherwise specified.

Hereinafter, terms related to the embodiments of the present application are explained for the convenience of the reader.

1. The Trace (Trace) data is a general name of all detailed signaling data of the wireless side, and each control plane signaling generated by the terminal equipment can be analyzed and acquired in the Trace data. The Trace data includes MR and the like.

2. MR is used to provide indicators for evaluating network coverage. The acquisition of the MR is performed in units of access network devices, that is, the acquired MR includes MR data of one or more terminal devices connected to the same access network device. As shown in table 1, the MR data includes a start time of the MR sample, an end time of the MR sample, an authentication management function terminal application layer signaling protocol identifier (AMF UE NGAP ID), an authentication management function Region identifier (AMF Region ID), an authentication management function Set identifier (AMF Set ID), an authentication management function Pointer (AMF power), a Reference Signal Reception Power (RSRP), a reference signal reception quality (q), and the like. The information in table 1 is explained as follows:

the AMF UE NGAP ID is used for temporarily characterizing the identification of the terminal equipment, and the identification is time-efficient.

The AMF Region ID is used to identify a Region of an AMF.

The AMF Set ID is used to identify a Set of AMFs in the AMF area.

The AMF Pointer is used to identify an AMF in a set of AMFs in the AMF area.

RSRP is an index used to measure radio signal strength and physical layer measurement requirements.

The RSRQ is an index for measuring the reception quality of the downlink specific cell reference signal.

TABLE 1

3. The call detail document (XDR) includes, but is not limited to, call ticket data (e.g., N2 call ticket data, N3 call ticket data) of each interface on the core network side.

3.1, the call ticket data of N2 is obtained from the N2 interface. The N2 interface connects the AMF with the gsdeb for transmitting data of the signaling plane. As shown in table 2, the N2 ticket data includes the following information: the starting time of the N2 ticket, the ending time of the N2 ticket, AMF UE NGAP ID, AMF Region ID, AMF Set ID, AMF Pointer, gNodeB user plane IP ADDRESS, gNodeB user plane TEID, and the like. The information in table 2 is explained as follows:

the gNodeB user plane IP and the gNodeB user plane TEID are the address and the identification of a transmission layer of the terminal equipment, and after the character string of the gNodeB user plane IP and the character string of the gNodeB user plane TEID are spliced, a TLI can be formed and used for subsequent association with the N3 ticket.

It should be noted that the same information as in table 1 above can be understood by referring to the corresponding position, and is not described herein again.

TABLE 2

It should be noted that, since the data of the signaling plane is transmitted by N2, when the terminal device has a service requirement, a connection of the signaling plane of the N2 interface needs to be established first, and the AMF UE NGAP ID is transmitted in the process of establishing the connection of the signaling plane, so that the N2 ticket data may include the AMF UE NGAP ID.

It should be noted that, after the connection establishment of the N2 interface signaling plane is successful, a transport bearer of the user plane needs to be established (i.e., PDU SESSION RESOURCE REQUEST) through Protocol Data Unit (PDU) SESSION RESOURCE establishment REQUEST information. In the process of establishing the user plane transport bearer, as shown in fig. 1, a PDU SESSION response REQUEST is first sent to a nodeb by an AMF; and the gNodeB establishes a RESPONSE message (namely PDU Session RESPONSE SETUP RESPONSE) to the PDU SESSION RESOURCE sent by the AMF. The PDU SESSION RESOURCE REQUEST carries transport layer addresses (UPF serving IP ADDRESS and UPF GTP TEID) allocated by the network element UPF of the core network to the current user, and the PDU SESSION RESOURCE REQUEST RESPONSE REQUEST carries transport layer addresses (i.e., the gdnodeb user plane IP ADDRESS and the gdnodeb user plane TEID) allocated by the gdnodeb to the current user, so that it can be known that the N2 ticket data may include the gdnodeb user plane IP ADDRESS and the gdnodeb user plane TEID.

3.2 and N3 ticket data are obtained from the N3 interface. The N3 interface is used to connect the UPF with the gsdeb for transmitting user plane data. As shown in table 3, the N3 ticket data includes the following information: the starting time of the N3 ticket, the ending time of the N3 ticket, a user permanent identifier (SUPI), a nodeb user plane IP ADDRESS, a nodeb user plane TEID, and the like. The information in table 3 is explained as follows:

the SUPI is a unique identification of the terminal device stored on the core network side and has permanent validity.

The GPS longitude and the GPS latitude are used for representing longitude and latitude information of the terminal equipment.

It should be noted that the same information in table 2 as described above can be understood by referring to the corresponding position, and is not described herein again.

TABLE 3

It should be noted that, since the N3 interface transmits data of the user plane, a bearer of the user plane also needs to be established, in this process, the gdnodeb user plane IP ADDRESS and the gdnodeb user plane TEID are transmitted, and thus the N3 ticket data may include the gdnodeb user plane IP ADDRESS and the gdnodeb user plane TEID. When the terminal device obtains the right to call the device location information (i.e., latitude and longitude information), the location information of the terminal device is transmitted in the N3 interface, so that the N3 ticket data may include the location information of the terminal device.

The above is a brief introduction to some of the concepts involved in the embodiments of the present application.

Fig. 2 shows a schematic structural diagram of a latitude and longitude information acquisition device of a terminal device according to an embodiment of the present application. The longitude and latitude information acquisition device of the terminal equipment comprises: the system comprises a computing device 10, a wireless network side network management device 20 and a core network side network management device 30.

It should be noted that the computing device 10 may obtain data (for example, MR data, N2 ticket data, and N3 ticket data) from the wireless network side network management device 20 and the core network side network management device 30, perform association on different data, add information in one data to another data, and so on.

It should be noted that the network management device 20 on the wireless network side is used for monitoring various network elements on the wireless network side and providing data, such as MR data, for the computing device 10.

It should be noted that the network management device on the core network side is configured to monitor each network element on the core network side, and provide data, such as N2 ticket data and N3 ticket data, for the computing device 10.

The method and the device can be applied to 5G systems and various systems based on 5G system evolution. The core network of the 5G system may be referred to as 5GC (5G core), and the access network may be referred to as New Radio (NR). For convenience of description, the present application is exemplified by applying the present application to a 5G system hereinafter, but it is to be understood that the present application is also applicable to various systems and the like based on 5G system evolution, and is not limited.

Fig. 3 shows a network architecture diagram of a 5G network, and referring to fig. 3, the 5G network includes the following network element functional entities: a 5G (wireless) access network (R) AN), a User Equipment (UE), a User Plane Function (UPF), a Data Network (DN), and a network element function entity in a 5G core network. Wherein, the network element functional entity in the 5G core network comprises: AMF, SMF, authentication service function (AUSF), Network Slice Selection Function (NSSF), network capability open function (NEF), network element data repository function (NF relocation function, NRF), Policy Control Function (PCF), unified data management function (UDM), and application layer function (AF). The network element functional entity has the following specific functions: the AMF is used for being responsible for access and mobility management of users; the SMF is used for being responsible for session management of the user; AUSF is responsible for authenticating 3GPP and non-3 GPP access of users; the UPF is used for being responsible for user plane processing; the DN is responsible for data networks such as operator services, internet access or third party services; the NSSF is used for selecting the network slice adopted by the user service; NRF is responsible for registration, discovery and selection of network functions; NEF is responsible for opening the capabilities of the 5G network to external systems; the PCF is used for being responsible for the policy control of the user, including the policy of the session, the mobility policy and the like; the UDM is used for being responsible for subscription data management of the user; the AF is responsible for interworking with the core network to provide services to the user.

The connection relationship of the network element functional entities is as follows:

the UE is connected with the AMF through an N1 interface.

The (R) AN and AMF are connected via AN N2 interface.

The (R) AN and UPF are connected via AN N3 interface.

The UPF interfaces with the SMF through an N4 interface.

The UPF internally transmits data over an N9 interface (data is transmitted between the upstream classifier UPF and the anchor UPF over an N9 interface).

The UPF and DN interface via N6.

An IT bus is adopted in the service architecture:

the AMF accesses the bus through a service-based interface Namf.

The AUSF accesses the bus through a service-based interface Nausf.

The SMF accesses the bus via a service based interface Nsmf.

The NSSF accesses the bus through a service based interface NSSF.

The NEF accesses the bus via a service-based interface Nnef.

The NRF accesses the bus via a service based interface, nrrf.

The PCF accesses the above-mentioned bus via a service based interface Npcf.

The UDM accesses the above-mentioned bus via a service-based interface numm.

The AF accesses the bus through a service-based interface Naf.

In the above, the application scenario of the present application is briefly introduced.

In addition, the communication system described in the embodiment of the present application is for more clearly illustrating the technical solution of the embodiment of the present application, and does not constitute a limitation to the technical solution provided in the embodiment of the present application, and it is known by a person of ordinary skill in the art that the technical solution provided in the embodiment of the present application is also applicable to similar technical problems with the evolution of network architecture and the appearance of new communication systems.

In 4G networks, it is very common to have a terminal chip that reports latitude and longitude information, i.e., it is very common to include latitude and longitude information in MR data. Therefore, when the latitude and longitude information of the terminal device needs to be acquired, the latitude and longitude information can be acquired from the MR data. However, the 5G terminal chip does not have a function of reporting latitude and longitude information of the terminal device, so that the latitude and longitude information of the terminal device cannot be obtained from the MR data, and thus, the network coverage condition of the specified area cannot be analyzed, and the area with poor network coverage quality (for example, weak coverage and over coverage) cannot be accurately located, which is not beneficial to the evaluation of the network coverage quality and the optimization of the area with poor coverage quality.

In order to solve the problems in the prior art, an embodiment of the present application provides a method for acquiring longitude and latitude information of a terminal device, so that a computing device can acquire the longitude and latitude information of the terminal device from MR data in a 5G network scene. As shown in fig. 4, the method includes:

s401, the computing device obtains a measurement report MR, first bill data of at least one first terminal device and second bill data of at least one first terminal device.

The MR comprises MR data of at least one second terminal device, and the MR data comprises AMF UE NGAP ID.

The first ticket data includes a Transport Layer Identifier (TLI) and an AMF UE NGAP ID, where the transport layer identifier is composed of a gdnodeb user plane network protocol address (gdnodeb incoming packet IP ADDRESS) and a gdnodeb user plane tunnel ENDPOINT identifier (gdnodeb GTP TEID).

Illustratively, the first ticket data may be N2 ticket data.

The second phone bill data comprises TLI and latitude and longitude information. The second ticket data may be, for example, N3 ticket data.

And acquiring the longitude and latitude information in the second phone bill data from the core network side when the terminal equipment uses the service.

The at least one first terminal device is part or all of a plurality of terminal devices connected to the plurality of access network devices. And establishing communication connection between the plurality of access network devices and the same AMF, or establishing communication connection between the plurality of access network devices and the same UPF.

The at least one second terminal device is part or all of a plurality of terminal devices connected to one access network device. It should be noted that the access network device is one of the access network devices.

It should be noted that, according to the comparison, the number of the terminal devices connected to the plurality of access network devices is usually greater than the number of the terminal devices connected to one terminal device, and therefore, the range of selecting the first terminal device by the computing device is greater than or equal to the range of selecting the second terminal device by the computing device.

S402, the computing device determines target MR data.

Wherein the target MR data is one of the MR data of the at least one second terminal device.

In one possible implementation, the computing device may randomly determine the target MR data from the plurality of MR data. That is, the computing device determines MR data of any one of the second terminal devices from the MR data of the at least one second device as target MR data.

In yet another possible implementation, the computing device may specify a particular MR data from the plurality of MR data as the target MR data. For example, the computing device determines, from the MR data of at least one second device, the MR data of the second device as the target MR data by specifying an identifier of the terminal device, and determines, for example, the MR data of the second terminal device as the target MR data by using a temporary identifier (AMF UE NGAP ID) of the second terminal device, which is not limited in this application.

S403, the computing equipment determines first target ticket data.

The first target ticket data is the first ticket data which has the same AMF UE NGAP ID with the target MR data in the first ticket data of at least one first terminal device.

In a possible implementation manner, S403 may specifically be implemented by the following steps:

the computing device determines the AMF UE NGAP ID of the target MR data from the target MR data determined in S402 above.

The computing device determines first call ticket data which have the same AMF UE NGAP ID with the target MR data from the first call ticket data of at least one second terminal device.

And the computing equipment determines the first ticket data which has the same AMF UE NGAP ID with the target MR data as the first target ticket data.

S404, the computing equipment determines second target call ticket data.

And the second target call ticket data is the second call ticket data which has the same TLI as the first target call ticket data in the second call ticket data of at least one first terminal device.

In a possible implementation manner, S404 may specifically be implemented by the following steps:

the computing device determines the TLI of the first target ticket data from the first target ticket data determined in S403.

The computing device determines second call ticket data which has the same TLI as the first target call ticket data from the second call ticket data of at least one first terminal device.

And the computing equipment determines the second call ticket data with the same TLI as the first target call ticket data as the second target call ticket data.

S405, adding the latitude and longitude information in the second target ticket data to the target MR data by the computing equipment.

The application provides a method for acquiring longitude and latitude information of terminal equipment, wherein a computing device associates MR data with second bill data through first bill data, so that the longitude and latitude information in the second bill data can be added into the MR data, and under a 5G network architecture, if the network coverage quality of a specified area needs to be evaluated or an area with poor network coverage needs to be optimized, the specified area or the area with poor network coverage can be determined by acquiring the longitude and latitude information in the MR data, so that the coverage condition in a specified position range can be analyzed, the area with poor coverage quality can be positioned, the evaluation of the network coverage quality is facilitated, and the optimization of the area with poor coverage quality is facilitated.

In a possible implementation manner, as shown in fig. 5 in conjunction with fig. 4, in the case that the terminal device permanent identity SUPI is further included in the second ticket data, the method further includes the following S501.

S501, adding the SUPI in the second target ticket data to the target MR data by the computing equipment.

It should be noted that, in the embodiment of the present application, the computing device may first execute S405, and then execute S501; alternatively, the computing device may perform S501 first and then S405, or the computing device may perform S501 and S405 simultaneously, which is not limited in this embodiment of the application.

The application provides a method for acquiring latitude and longitude information of a terminal device.A computing device associates second target ticket data with target MR data through first target ticket data, and can add SUPI in the second target ticket data into the target MR data, so that the terminal device can be identified according to a permanent identifier in the following process, and inconvenience caused by timeliness of the temporary identifier is avoided.

In a possible implementation manner, as shown in fig. 6 in conjunction with fig. 4 or fig. 5, before S405, the method may further include the following S601 to S603.

S601, the computing equipment judges whether the target MR data, the first target ticket data and the second target ticket data meet a preset rule.

Wherein, the preset rule comprises: the starting time of the first target ticket data and the second target ticket data is within the sampling period of the target MR data, and the ending time of the first target ticket data is less than the starting time of the second target ticket data.

It should be noted that the following cases 1.1 and 1.2 are included in the determination of whether the target MR data, the first target ticket data, and the second target ticket data satisfy the preset rule by the computing device. The following are specifically described below:

and 1.1, the target MR data, the first target ticket data and the second target ticket data meet the preset rule.

That is, the starting time of the target data MR is T1 and is smaller than the starting time T2 of the first target ticket data, the starting time T2 of the first target ticket data is smaller than the starting time T3 of the second target ticket data, and the starting time T3 of the second target ticket data is smaller than the ending time T4 of the target MR data. As shown in FIG. 7, T1 < T2 < T3 < T4.

And 1.2, the target MR data, the first target ticket data and the second target ticket data do not meet the preset rule.

In a possible implementation manner, the starting time T1 of the target data MR is less than the starting time T3 of the second target ticket data, the starting time T3 of the second target ticket data is less than the starting time T2 of the first target ticket data, and the starting time T2 of the first target ticket data is less than the ending time T4 of the target MR data. As shown in FIG. 8, T1 < T3 < T2 < T4.

It should be noted that, the above is only an exemplary description of the case 1.2, and the case 1.2 may also have other examples (for example, the start time T1 of the target data MR is less than the start time T2 of the first target ticket data, the start time T2 of the first target ticket data is less than the start time T4 of the second target ticket data, and the start time T4 of the second target ticket data is less than the end time T3 of the target MR data).

In a possible implementation manner, in conjunction with the above case 1.1 and case 1.2, the actions performed by the computing device in different cases are different, and are specifically described below:

in connection with case 1.1 above, the computing device performs the following S602.

S602, the computing device adds the longitude and latitude information in the second target ticket data to the target MR data.

Table 4 is an example of MR data to which latitude and longitude information is added. As shown in table 4, both latitude and longitude information and SUPI have been added to the MR data. The description about the SUPI addition to the target MR data can be understood with reference to S401 described above, and is not described herein again.

TABLE 4

In connection with case 1.2 above, the computing device performs the following S603.

S603, the computing device obtains the MR in the second time period, the first call ticket data of at least one first terminal device and the second call ticket data of at least one first terminal device, and matching is carried out according to the method recorded in the S402-S405.

The computing equipment limits the starting time of first target ticket data and the starting time of second target ticket data to be within the sampling period of target MR data, and the ending time of the first target ticket data is smaller than the starting time of the second target ticket data, so that the information in the first target ticket data, the second target ticket data and the target MR data can be effective, the problem of information addition error caused by information failure in the data is avoided, and the accuracy of the added information is effectively improved.

It should be noted that, all the information in the first target ticket data, the second target ticket data, and the target MR data are valid, that is, AMF UE NGAP and SUPI are valid, because AMF UE NGAP is a temporary identifier representing a terminal device, that is, AMF UE NGAP has timeliness, and TLI is information transmitted when a PDU session bearer is established, when the PDU session fails, TLI also fails, that is, TLI also has timeliness.

In an implementation manner, as shown in fig. 9, taking the first ticket data as the N2 ticket data, the second ticket data as the N3 ticket data, and the time period of 17:00 to 17:15 as an example, the method for acquiring latitude and longitude information of a terminal device provided in the embodiment of the present application is specifically described as follows:

s901, acquiring the MR by the computing device.

Illustratively, MR data of two terminal devices is carried in MR. The AMF UE NGAP IDs of the MR data of the two terminal devices are 2097827 and 7340549, respectively.

S902, the computing equipment obtains the N2 ticket data of at least one terminal equipment.

Illustratively, the N2 ticket data of two terminal devices are obtained. The AMF UE NGAP IDs of the N2 ticket data of the two terminal devices are 2097827 and 7340549, respectively.

It should be noted that the number of the N2 ticket data or the N3 ticket data is greater than that of the MR data, and for the convenience of understanding, the present application takes the same number of the N2 ticket data, the N3 ticket data, and the MR data as an example for explanation.

S903, the computing equipment obtains the N3 ticket data of at least one terminal device.

Illustratively, the computing device obtains N3 ticket data for two terminal devices. The TLIs of the N3 ticket data of the two terminal devices are 10.110.144.210.571465147 and 10.110.131.78.3721078940, respectively.

S904, the computing device determines the target MR data.

In connection with the above example, the computing device determines MR data with AMF UE NGAP ID 2097827 as the target MR data in the MR of the above example.

S905, the computing equipment determines target N2 ticket data.

With reference to the above example, as shown in fig. 10, the computing device searches the N2 ticket data with 2097827 (i.e., the AMF UE NGAP ID in the target MR data) as an index, and determines that the N2 ticket data with the AMF UE NGAP ID of the terminal device also being 2097827 is used as the target N2 ticket data. However, it can be determined from the target N2 ticket data that the TLI in the target N2 ticket data is 10.110.144.210.571465147.

S906, the computing equipment determines target N3 ticket data.

With reference to the above example, as shown in fig. 11, the computing device searches the N3 ticket data with 10.110.144.210.571465147 (i.e., the TLI in the target N2 ticket data) as an index, and determines that the N3 ticket data with the TLI of the terminal device also being 10.110.144.210.571465147 is used as the target N3 ticket data.

S907, the computing equipment judges whether the target MR data, the target N2 ticket data and the target N3 ticket data meet preset rules.

It should be noted that the following two cases are included in the determination, by the computing device, whether the target MR data, the target N2 ticket data, and the target N3 ticket data satisfy the preset rule:

and 2.1, the target MR data, the target N2 ticket data and the target N3 ticket data meet the preset rule.

Note that case 2.1 corresponds to case 1.1 described above.

And 2.2, the target MR data, the target N2 ticket data and the target N3 ticket data do not meet the preset rule.

Note that case 2.2 corresponds to case 1.2 described above.

The actions performed by the computing device differ in different situations, as described in more detail below:

in connection with case 2.1 above, the computing device performs the following S908.

S908, filling the longitude and latitude information and the SUPI in the target N3 ticket data into the target MR data by the computing equipment.

In conjunction with the above example, as shown in fig. 12, the computing device determines the latitude and longitude information and the SUPI in the target N3 ticket data, and adds the latitude and longitude information and the SUPI to the target MR data.

In connection with case 2.2 above, the computing device performs the following S909.

S909, acquiring MR in a second time period, N2 ticket data of at least one first terminal device and N3 ticket data of at least one first terminal device;

and adding longitude and latitude information and SUPI into the MR data according to the MR in the second time period, the N2 ticket data of the at least one first terminal device and the N3 ticket data of the at least one first terminal device.

It can be understood that the method for acquiring the longitude and latitude information of the terminal equipment can be realized by the device for acquiring the longitude and latitude information of the terminal equipment. The longitude and latitude information acquisition device of the terminal equipment comprises a hardware structure and/or a software module corresponding to each function in order to realize the functions. Those of skill in the art will readily appreciate that the various illustrative modules and algorithm steps described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the embodiments disclosed herein.

The latitude and longitude information acquiring device of the terminal device generated according to the method example of the present disclosure may divide the functional modules, for example, each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. It should be noted that, the division of the modules in the embodiments disclosed in the present application is schematic, and is only one division of logic functions, and there may be another division manner in actual implementation.

Fig. 13 is a schematic structural diagram of a latitude and longitude information acquisition device of a terminal device according to an embodiment of the present invention. As shown in fig. 13, the terminal device longitude and latitude information acquiring apparatus 130 may be configured to execute the terminal device longitude and latitude information acquiring methods shown in fig. 4-6 and 9. The latitude and longitude information acquiring device 130 of the terminal equipment comprises a communication unit 1301 and a processing unit 1302;

a communication unit 1301, configured to acquire the following information in a first time period: a measurement report MR, first call ticket data of at least one first terminal device and second call ticket data of at least one first terminal device; the MR comprises MR data of at least one second terminal device, the MR data comprises an authentication management function terminal application layer signaling protocol identifier AMF UE NGAP ID, the first ticket data comprises TLI and AMF UE NGAP ID, the TLI is composed of a fifth generation network base station gNodeB user plane network protocol address and a gNodeB user plane tunnel endpoint identifier, the second ticket data comprises TLI and latitude and longitude information, the at least one first terminal device is part or all of a plurality of terminal devices connected with a plurality of access network devices, and the at least one second terminal device is part or all of a plurality of terminal devices connected with one access network device.

A processing unit 1302, configured to determine target MR data, where the target MR data is one of MR data of at least one second terminal device; determining first target call ticket data, wherein the first target call ticket data is the first call ticket data of at least one first terminal device, and the first call ticket data and the target MR data have the same AMF UE NGAP ID; determining second target call bill data, wherein the second target call bill data is the second call bill data which has the same TLI (transport layer identity) as the first target call bill data in the second call bill data of at least one first terminal device; and adding the longitude and latitude information in the second target ticket data into the target MR data.

In the case of implementing the functions of the integrated module in the form of hardware, the embodiment of the present invention provides another possible structural schematic diagram of the electronic device (including the first network device and the second network device) involved in the foregoing embodiment. As shown in fig. 14, an electronic device 140 is, for example, configured to execute the latitude and longitude information acquisition method of the terminal device shown in fig. 4. The electronic device 140 includes a processor 1401, a memory 1402, and a bus 1403. The processor 1401 and the memory 1402 may be connected by a bus 1403.

The processor 1401 is a control center of the communication apparatus, and may be a single processor or a collective term for a plurality of processing elements. For example, the processor 1401 may be a general-purpose Central Processing Unit (CPU), or may be another general-purpose processor. Wherein a general purpose processor may be a microprocessor or any conventional processor or the like.

For one embodiment, processor 1401 may include one or more CPUs, such as CPU 0 and CPU 1 shown in FIG. 14.

The memory 1402 may be, but is not limited to, a read-only memory (ROM) or other type of static storage device that may store static information and instructions, a Random Access Memory (RAM) or other type of dynamic storage device that may store information and instructions, an electrically erasable programmable read-only memory (EEPROM), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer.

As a possible implementation, the memory 1402 may exist separately from the processor 1401, and the memory 1402 may be connected to the processor 1401 via a bus 1403 for storing instructions or program code. The processor 1401, when calling and executing the instructions or program codes stored in the memory 1402, can implement the rich media determination method provided by the embodiment of the present invention.

In another possible implementation, the memory 1402 may also be integrated with the processor 1401.

The bus 1403 may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, an Extended ISA (EISA) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 14, but this is not intended to represent only one bus or type of bus.

It is to be noted that the structure shown in fig. 14 does not constitute a limitation of the electronic apparatus 140. In addition to the components shown in fig. 14, the electronic device 140 may include more or fewer components than shown, or some components may be combined, or a different arrangement of components.

Optionally, as shown in fig. 14, the electronic device 140 provided in the embodiment of the present invention may further include a communication interface 1404.

A communication interface 1404 for connecting with other devices through a communication network. The communication network may be an ethernet network, a radio access network, a Wireless Local Area Network (WLAN), etc. Communication interface 1404 may include a receiving unit for receiving data, and a transmitting unit for transmitting data.

In one design, in the electronic device provided by the embodiment of the present invention, the communication interface may be further integrated in the processor.

Fig. 15 shows another hardware configuration of an electronic device (including a first device and a second device) in the embodiment of the present invention. As shown in fig. 15, the electronic device 150 may include a processor 1501 and a communication interface 1502. The processor 1501 is coupled to the communication interface 1502.

The functions of the processor 1501 can be referred to as described above with reference to the processor 1501. The processor 1501 also has a memory function, and the function of the memory 1502 described above can be referred to.

The communication interface 1502 is used to provide data to the processor 1501. The communication interface 1502 may be an internal interface of the communication apparatus, or may be an external interface (corresponding to the communication interface 1504) of the communication apparatus.

It is noted that the configuration shown in fig. 15 does not constitute a limitation of the electronic device 150, and that the electronic device 150 may include more or less components than those shown in fig. 15, or combine some components, or arrange different components, in addition to the components shown in fig. 15.

Through the above description of the embodiments, it is clear for a person skilled in the art that, for convenience and simplicity of description, only the division of the above functional units is illustrated. In practical applications, the above function allocation can be performed by different functional units according to needs, that is, the internal structure of the device is divided into different functional units to perform all or part of the above described functions. For the specific working processes of the system, the apparatus and the unit described above, reference may be made to the corresponding processes in the foregoing method embodiments, and details are not described here again.

The embodiment of the present invention further provides a computer-readable storage medium, where instructions are stored in the computer-readable storage medium, and when the instructions are executed by a computer, the computer executes each step in the method flow shown in the above method embodiment.

Embodiments of the present invention provide a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of determining rich media in the above-described method embodiments.

The computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, and a hard disk. Random Access Memory (RAM), Read-Only Memory (ROM), Erasable Programmable Read-Only Memory (EPROM), registers, a hard disk, an optical fiber, a portable Compact disk Read-Only Memory (CD-ROM), an optical storage device, a magnetic storage device, or any other form of computer-readable storage medium, in any suitable combination, or as appropriate in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. Of course, the storage medium may also be integral to the processor. The processor and the storage medium may reside in an Application Specific Integrated Circuit (ASIC). In embodiments of the invention, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

Since the apparatus, the device, the computer-readable storage medium, and the computer program product in the embodiments of the present invention may be applied to the method described above, for technical effects obtained by the apparatus, the computer-readable storage medium, and the computer program product, reference may also be made to the method embodiments described above, and details of the embodiments of the present invention are not repeated herein.

The above description is only an embodiment of the present invention, but the scope of the present invention is not limited thereto, and any changes or substitutions within the technical scope of the present invention are intended to be covered by the scope of the present invention.

Claims

1. A method for acquiring longitude and latitude information of terminal equipment is characterized by comprising the following steps:

the following information is obtained for a first time period: a measurement report MR, first call ticket data of at least one first terminal device and second call ticket data of the at least one first terminal device; the MR comprises MR data of at least one second terminal device, the MR data comprises an authentication management function terminal application layer signaling protocol identifier AMF UE NGAPID, the first ticket data comprises the TLI and the AMF UE NGAPID, the TLI is composed of a fifth generation network base station gNodeB user plane network protocol address and a gNodeB user plane tunnel endpoint identifier, the second ticket data comprises the TLI and latitude and longitude information, the at least one first terminal device is part or all of a plurality of terminal devices connected with a plurality of access network devices, and the at least one second terminal device is part or all of a plurality of terminal devices connected with one access network device;

determining target MR data, wherein the target MR data is one of the MR data of the at least one second terminal device;

determining first target call ticket data, wherein the first target call ticket data is the first call ticket data of the at least one first terminal device, and the first call ticket data and the target MR data have the same AMF UE NGAP ID;

determining second target call bill data, wherein the second target call bill data is the second call bill data which has the same TLI as the first target call bill data in the second call bill data of the at least one first terminal device;

and adding the longitude and latitude information in the second target ticket data into the target MR data.

2. The method of claim 1, wherein the latitude and longitude information in the second target ticket data is obtained from a core network side when the terminal device uses the service.

3. The method according to claim 1 or 2, wherein the second target ticket data further comprises a user permanent identity (SUPI), and during the process of adding the latitude and longitude information in the second target ticket data to the target MR data, the method further comprises:

and adding the SUPI in the second target ticket data into the target MR data.

4. The method of any one of claims 1-3, wherein prior to said adding latitude and longitude information in said second target ticket data to said target MR data, said method further comprises:

judging whether the first target call ticket data, the second target call ticket data and the target MR data meet preset conditions, wherein the preset conditions comprise: the ending time of the first target ticket data is less than the starting time of the second target ticket data, and the starting time of the first target ticket data and the second target ticket data is within the time period of the target MR data;

if yes, adding the longitude and latitude information in the second target ticket data into the target MR data;

if not, acquiring the following information in the second time period: MR, first call ticket data of at least one first terminal device and second call ticket data of the at least one first terminal device;

and adding longitude and latitude information into the MR data according to the MR in the second time period, the first call ticket data of at least one first terminal device and the second call ticket data of at least one first terminal device.

5. A longitude and latitude information acquisition device of a terminal device is characterized by comprising: a communication unit and a processing unit;

the communication unit is used for acquiring the following information in a first time period: a measurement report MR, first call ticket data of at least one first terminal device and second call ticket data of the at least one first terminal device; the MR comprises MR data of at least one second terminal device, the MR data comprises an authentication management function terminal application layer signaling protocol identifier AMF UE NGAP ID, the first ticket data comprises the TLI and the AMF UE ngapi, the TLI is composed of a fifth generation network base station gNodeB user plane network protocol address and a gNodeB user plane tunnel endpoint identifier, the second ticket data comprises the TLI and latitude and longitude information, the at least one first terminal device is part or all of a plurality of terminal devices connected with a plurality of access network devices, and the at least one second terminal device is part or all of a plurality of terminal devices connected with one access network device;

the processing unit is configured to determine target MR data, where the target MR data is one of MR data of the at least one second terminal device;

the processing unit is further configured to determine first target ticket data, where the first target ticket data is first ticket data of the at least one first terminal device, and the first ticket data and the target MR data have the same AMF UE NGAP ID;

the processing unit is further configured to determine second target ticket data, where the second target ticket data is second ticket data of the at least one first terminal device and has the same TLI as the first target ticket data;

the processing unit is further configured to add the latitude and longitude information in the second target ticket data to the target MR data.

6. The apparatus of claim 5, wherein the latitude and longitude information in the second target ticket data is obtained from a core network side when the terminal device uses the service.

7. The apparatus according to claim 5 or 6, wherein the second target ticket data further comprises a user permanent identity (SUPI), and in the process of adding the latitude and longitude information in the second target ticket data to the target MR data, the processing unit is further configured to:

and adding the SUPI in the second target ticket data into the target MR data.

8. The apparatus according to any one of claims 5-7, wherein before the adding the latitude and longitude information in the second target ticket data to the target MR data, the processing unit is further configured to:

if not, the following information in a second time period is acquired through the communication unit: MR, first call ticket data of at least one first terminal device and second call ticket data of the at least one first terminal device;

9. A longitude and latitude information acquisition device of a terminal device is characterized by comprising: a processor and a communication interface; the communication interface is coupled to the processor, and the processor is configured to run a computer program or instructions to implement the method for acquiring latitude and longitude information of a terminal device as claimed in any one of claims 1 to 4.

10. A computer-readable storage medium having instructions stored therein, wherein when the instructions are executed by a computer, the computer performs the method for acquiring latitude and longitude information of a terminal device according to any one of claims 1 to 4.