WO2020133996A1 - 一种终端的跟踪方法、设备及存储介质 - Google Patents

一种终端的跟踪方法、设备及存储介质 Download PDF

Info

Publication number
WO2020133996A1
WO2020133996A1 PCT/CN2019/093910 CN2019093910W WO2020133996A1 WO 2020133996 A1 WO2020133996 A1 WO 2020133996A1 CN 2019093910 W CN2019093910 W CN 2019093910W WO 2020133996 A1 WO2020133996 A1 WO 2020133996A1
Authority
WO
WIPO (PCT)
Prior art keywords
tracking
terminal information
packet
uplink message
peer
Prior art date
Application number
PCT/CN2019/093910
Other languages
English (en)
French (fr)
Inventor
王国强
白晓春
郭伟丽
张玉院
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2020133996A1 publication Critical patent/WO2020133996A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W64/00—Locating users or terminals or network equipment for network management purposes, e.g. mobility management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H04W76/16—Involving different core network technologies, e.g. a packet-switched [PS] bearer in combination with a circuit-switched [CS] bearer

Definitions

  • the present application relates to the field of communication technology, and in particular, to a terminal tracking method, device, and storage medium.
  • the tracking method of a single UE (User Equipment) in a wireless network mainly includes the tracking task mode issued by the core network, the tracking method of the terminal IMSI (International Mobile Subscriber Identification Number), and the TMSI (Temporary Mobile Subscriber Identity) , Temporary mobile user ID) tracking method.
  • IMSI International Mobile Subscriber Identification Number
  • TMSI Temporary Mobile Subscriber Identity
  • the way of tracking tasks issued by the core network is mainly to deliver tracking tasks through the core network.
  • This method depends on the core network, which requires the cooperation of both the core network and the access network, and there are some interoperability issues, such as the IMSI information of the terminal How to report the corresponding relationship with Trace and Reference to TCE is actually more troublesome.
  • the way of TMSI tracking depends on the MME (Mobility Management Entity, network node) rules for allocating TMSI numbers.
  • MME Mobility Management Entity, network node
  • MME's TMSI distribution strategy is very flexible. Due to factors such as access time, handover, and re-access, MME may redistribute TMSI, and continuous tracking is very difficult. Therefore, the current UE tracking method has problems such as identification failure.
  • the technical problem to be solved by the present application is to provide a terminal tracking method, device and storage medium.
  • the user terminal is tracked.
  • a communication node device in an embodiment of the present application includes a memory and a processor.
  • the memory stores a tracking program of the terminal, and the processor executes the program to implement the steps of the method described in any one of the above.
  • a computer-readable storage medium in an embodiment of the present application stores a tracking program of a terminal, and the computer program may be executed by at least one processor to implement the steps of the method described in any one of the above.
  • Each of the foregoing embodiments determines whether the characteristics of the analyzed upstream packet satisfy the pre-configured tracking terminal information, so that the user terminal can be tracked when it is satisfied, and thus does not need to rely on the core network, and does not require communication node equipment and core
  • the cooperation of the network can quickly and accurately identify the user terminal that needs to be tracked, effectively improve the recognition rate of the tracking terminal, and can realize continuous tracking, thereby effectively solving the problem of continuous tracking difficulty in the TMSI tracking mode.
  • FIG. 1 is a flowchart of a terminal tracking method in an embodiment of the present application.
  • FIG. 3 is a flowchart of tracking initiated by the dual-connection LTE side in the embodiment of the present application.
  • FIG. 6 is a flowchart of a base station identifying a UDP filling UE in an embodiment of the present application
  • FIG. 7 is a schematic structural diagram of a communication node device in an embodiment of the present application.
  • module means, “part” or “unit” used to represent elements is only for the benefit of the description of the present application, and has no specific meaning in itself. Therefore, “module”, “component” or “unit” can be used in a mixed manner.
  • An embodiment of the present application provides a terminal tracking method. As shown in FIG. 1, the method includes:
  • the tracking terminal is a user terminal that the base station needs to track.
  • the tracking terminal information may include one or more of the protocol type of the upstream message, the peer IP address, and the data packet length of the upstream message. Of course, it may also include the upstream report. The content of the text packet.
  • the protocol type can be ICMP (Internet Control Message Protocol) protocol ping (network diagnostic tool) packet request, using the ping packet request peer IP address, ping packet length and data packet content (data packet content is available) (Optional); it can also use the UDP (User Datagram Protocol, user datagram protocol) upstream filling protocol, using the destination IP address of the filling packet, the length of the UDP message and the content of the data packet (the content of the data packet is optional; also It can be a protocol that uses upstream TCP (Transmission Control Protocol) transmission packet, using the destination IP address and port of the packet, TCP packet length and data packet content (data packet content is optional).
  • ICMP Internet Control Message Protocol
  • UDP User Datagram Protocol
  • user datagram protocol User Datagram Protocol
  • upstream filling protocol using the destination IP address of the filling packet, the length of the UDP message and the content of the data packet (the content of the data packet is optional
  • TCP Transmission Control Protocol
  • the method in the embodiment of the present application is executed on the side of the communication node, and the communication node may be a base station or the like.
  • the user terminal by judging whether the characteristics of the uplink message obtained by parsing meet the pre-configured tracking terminal information, the user terminal can be tracked when it is satisfied, and thus does not need to rely on the core network, and does not require communication node equipment and the core network
  • the cooperation can further quickly and accurately identify the user terminal that needs to be tracked, effectively improve the recognition rate of the tracking terminal, and can achieve continuous tracking, thereby effectively solving the problem of continuous tracking difficulty in the TMSI tracking mode.
  • the pre-configured tracking terminal information before determining whether the characteristics of the parsed uplink message meet the pre-configured tracking terminal information, it may include:
  • the tracking terminal information includes one or more of the protocol type of the upstream message, the peer IP address, and the data packet length of the upstream message.
  • the tracking terminal information also includes the data packet content of the uplink message
  • the configuring the tracking terminal information includes:
  • the content of the data packet is configured at the head, middle, or tail of the data packet.
  • the base station can be configured to track UE information, for example, configure the protocol type of the upstream packet, the peer IP address, the packet length, and part of the packet content (the packet content can be (No configuration, it can also be configured as head part data or middle part data, tail part data, which can be flexibly configured).
  • the UE terminal initiates the corresponding service, such as ping packet request or UDP upstream filling packet.
  • the base station determines whether the upstream data packet service type conforms to the configured protocol type, and determines the peer's IP address, data packet length, and data packet content (optional). Do these items meet the configuration requirements? Track this UE.
  • the IP address of the peer can be the IP address of the real host, or it can be an IP address not configured in the network; for the length of the data packet, a special length is generally specified, such as the ping request is generally different from the system default ping packet length of 32 bytes Or 64 bytes, such as 97 bytes; or the length of the data packet meets special conditions, such as length modulo 7 is 0, then 97, 107, 117 and other lengths meet the requirements.
  • the system can also configure a set of IP addresses and data lengths to identify multiple UEs that meet the conditions.
  • the number of tracking UEs can be set. If the number of tracking UEs of the base station reaches a certain number, the recognition is stopped and system resource consumption is reduced.
  • the configuration of the tracking terminal information includes:
  • a 5G base station is added as a secondary connection. If the UE initiates the corresponding service before adding the secondary connection, after the LTE base station recognizes the tracking UE, it will track the UE's information when adding the secondary connection, including information such as protocol type, peer IP address, data packet length, and data packet content. It is sent to the 5G base station, and the 5G base station tracks and reports the tracking data of this UE. If the UE initiates the corresponding service after adding the secondary connection, the 5G base station recognizes the tracking UE and notifies the primary connection LTE base station of the tracking information of the UE.
  • the judging whether the characteristic of the analyzed upstream message meets the pre-configured tracking terminal information may include:
  • the matching result it is determined whether the characteristics of the uplink message satisfy the tracking terminal information.
  • the source-side base station carries the UE information to the target side, and the target-side base station tracks and reports the UE's tracking data. That is to say, in some embodiments, when the user terminal accesses from the primary connection to the secondary connection, the tracking terminal information is sent to the secondary connection.
  • This embodiment may carry UE tracking information to the target side base station when the UE performs a handover, thereby continuously tracking the UE.
  • the UE uplink message is parsed to determine the message type, and the method of combining the peer IP address + packet length + packet content is used to analyze whether it is a UE that needs to be tracked.
  • the content of the data packet is optional. If you compare the content of the data packet, you can compare the content of the head part, the tail part, or the content of the middle part, which can be flexibly configured.
  • Upstream packets can be judged by using ping packet request or UDP upstream packets.
  • the ping packet request can set a special peer IP address.
  • the base station recognizes the combination of parameters such as the peer address of the ping packet and the length of the ping packet.
  • Ping packet length can be a set of special length addresses (the default length of most operating systems is 32 bytes or 64 bytes), such as length 79, 85, etc., or meet special conditions, such as length mantissa 7, ping The remainder of the packet length and 7 is 0.
  • UDP upstream packets can be used to identify and track UEs based on the peer IP address, message length, and part of the data packet, so that they can quickly and accurately identify UEs that need to be tracked without relying on the core network. Carry the UE tracking information to the target side base station and continue to track the UE.
  • the embodiment of the present application describes the tracking method of the terminal involved in Embodiment 1 through the interaction process between the base station and the UE. As shown in FIG. 2, the interaction process includes:
  • Step 101 The base station configures the tracking terminal information of the tracking UE, including the IP address and ping packet length of the peer of the ping packet request.
  • Step 102 The UE side initiates a ping packet service, and the ping packet requests the peer's IP address and ping packet length to meet the information configured by the base station. You can also customize the APP on the UE side, preset the IP address of the peer end of the ping packet request, and the length of the qualified ping packet request.
  • Step 103 The base station parses the uplink message to identify if it is an ICMP message.
  • the type of the parsed message is the peer IP address of the ping request and the data packet length of the ping request. If the analysis result meets the configured tracking terminal information, the UE is tracked.
  • Step 104 The base station reports and tracks UE-related data, such as signaling and scheduling information.
  • This embodiment of the present application describes the process of identifying a primary connection in a dual-connection scenario, and describes the tracking method of the terminal involved in the first embodiment.
  • the embodiment of the present application takes the NSA networking as an example, the base station of LTE is the primary connection, and 5G is the secondary connection;
  • the recognition process includes:
  • Step 11 the base station of LTE and 5G tracks the UE information through the network management configuration, including the peer IP address of the ping packet and the length of the ping packet.
  • Step 12 the UE accesses the eNodeB, and initiates a ping packet request.
  • Step 13 The eNodeB parses the upstream message. If it is a ping packet request message, and the peer IP address and ping packet length satisfy the tracking UE information, the UE is tracked.
  • Step 14 after measuring the 5G base station information, the UE reports to the eNodeB, and the eNodeB carries the tracking information of the UE (ping packet peer IP address and ping packet length) to the 5G base station when adding the secondary connection.
  • step 15 the 5G base station determines that the tracking information satisfies the tracking condition, and then tracks the UE.
  • This embodiment of the present application describes the tracking method of the terminal involved in the first embodiment through a dual-connection scenario secondary connection identification process.
  • the NSA networking is used as an example
  • the LTE base station serves as the primary connection
  • 5G serves as the secondary connection, such as As shown in Figure 4, the identification process includes:
  • the LTE and 5G base stations track UE information through network management configuration, including the peer IP address of the ping packet and the length of the ping packet.
  • Step 22 the UE accesses the eNodeB. After measuring the 5G base station cell, the UE reports to the eNodeB, and the eNodeB adds a secondary connection.
  • Step 23 The UE initiates a ping packet service request.
  • the base station identifies and tracks the UE and reports data. For example, the 5G base station parses the uplink message and determines that if it is a ping packet request message, and the peer IP address and ping packet length of the ping packet satisfy the tracking UE information, the UE is tracked.
  • the primary connection is notified to track the UE.
  • the 5G base station carries UE tracking information (ping packet peer IP address and ping packet length) to the eNodeB side through X2 messages (such as SN Modification Required).
  • step 26 if the eNodeB judges that the tracking information of the UE meets the condition, it tracks the UE.
  • the base station reports UE tracking data.
  • the handover scenario of the present embodiment includes X2 handover of LTE and XN handover of 5G base stations, as shown in FIG. 5,
  • the identification process includes:
  • Step 31 The base station tracks UE information through network management configuration, including the peer IP address of the ping packet and the length of the ping packet.
  • the base station includes the source and target stations that are switched.
  • Step 32 After the UE accesses or switches into the source station, it initiates a ping packet service request.
  • Step 33 The base station reports the UE tracking.
  • the source station parses the uplink message of the UE, and if it is a ping packet request message, and if the peer IP address of the ping request and the length of the ping packet meet the conditions, the UE is tracked.
  • step 34 the UE performs a handover, and the source station carries the UE tracking information (the IP address of the peer end of the ping packet and the length of the ping packet) in the handover request message to the target station.
  • the UE tracking information the IP address of the peer end of the ping packet and the length of the ping packet
  • Step 35 The base station identifies and tracks the UE, and reports the data. For example, if the target station judges that the tracking information meets the conditions, it continues to track the UE.
  • the process of identifying the UDP encapsulation UE by the base station is described, and the tracking method of the terminal involved in Embodiment 1 is described. As shown in FIG. 6, the identification process includes:
  • the base station configures the information for tracking the UE, including the message type as UDP upstream message, the peer IP address, the length of the UDP message, and the content of the verified message header.
  • Step 202 the UE side initiates an uplink UDP filling service.
  • the base station parses the UE uplink message, recognizes that if it is a UDP message, and the peer IP address and data packet length meet the requirements, and then compares the content of the packet header with the configuration comparison content, then tracks the UE.
  • step 204 the base station tracks this UE and reports relevant data.
  • An embodiment of the present application provides a communication node device.
  • the communication node device includes a memory 20 and a processor 22.
  • the memory 20 stores a tracking program of a terminal.
  • the processor 22 executes the program to implement the embodiment.
  • the communication node device may be a communication node such as a base station.
  • Embodiments of the present application provide a computer-readable storage medium that stores a tracking program of a terminal, and the computer program can be executed by at least one processor to implement the steps of the method described in any embodiment.

Abstract

本申请公开了一种终端的跟踪方法、设备及存储介质，所述跟踪方法包括：解析用户终端的上行报文；判断解析得到的上行报文特征是否满足预先配置的跟踪终端信息；在满足时，跟踪所述用户终端。

Description

一种终端的跟踪方法、设备及存储介质
相关申请的交叉引用
本申请基于申请号为201811585304.3、申请日为2018年12月24日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本申请涉及通信技术领域，特别是涉及一种终端的跟踪方法、设备及存储介质。
背景技术
目前无线网络对于单个UE(User Equipment，用户终端)跟踪方法主要包括核心网下发跟踪任务方式、终端IMSI(International Mobile Subscriber Identification Number，国际移动用户识别码)的跟踪方式和TMSI(Temporary Mobile Subscriber Identity，临时移动用户标识)跟踪的方式。
其中，核心网下发跟踪任务方式主要是通过核心网下发跟踪任务，该方式依赖于核心网，需要核心网和接入网两者配合，并且存在一些互操作的问题，比如终端的IMSI信息与Trace Reference的对应关系如何上报给TCE等问题，实际使用比较麻烦。TMSI跟踪的方式，依赖MME(Mobility Management Entity，网络节点)分配TMSI号码的规则，UE需要反复接入，比较分配的TMSI，查找分配的规律来识别UE。并且MME的TMSI分配策略非常灵活，受接入时长、切换、重新接入等因素影响，MME可能重新分配TMSI，连续跟踪非常困难。因此，目前的UE跟踪方法存在识别失败等问题。
发明内容
本申请要解决的技术问题是提供一种终端的跟踪方法、设备及存储介质。
本申请实施例中的一种终端的跟踪方法，包括：
解析用户终端的上行报文；
判断解析得到的上行报文特征是否满足预先配置的跟踪终端信息；
在满足时，跟踪所述用户终端。
本申请实施例中的一种通信节点设备，包括存储器和处理器，所述存储器存储有终端的跟踪程序，所述处理器执行所述程序，以实现如上任意一项所述方法的步骤。
本申请实施例中的一种计算机可读存储介质，存储有终端的跟踪程序，所述计算机程序可被至少一个处理器执行，以实现如上任意一项所述方法的步骤。
上述的各个实施例通过判断解析得到的上行报文特征是否满足预先配置的跟踪终端信息，从而在满足时就可以跟踪所述用户终端，进而不需要依赖于核心网，不需要通信节点设备与核心网的配合，进而可以快速准确的识别需要跟踪的用户终端，有效提高跟踪终端的识别率，并且可以实现连续跟踪，进而有效解决TMSI跟踪的方式连续跟踪困难的问题。
上述说明仅是本申请技术方案的概述，为了能够更清楚了解本申请的技术手段，而可依照说明书的内容予以实施，并且为了让本申请的上述和其它目的、特征和优点能够更明显易懂，以下特举本申请的具体实施方式。
附图说明
通过阅读下文优选实施方式的详细描述，各种其他的优点和益处对于本领域普通技术人员将变得清楚明了。附图仅用于示出优选实施方式的目 的，而并不认为是对本申请的限制。而且在整个附图中，用相同的参考符号表示相同的部件。在附图中：
图1是本申请实施例中一种终端的跟踪方法的流程图；
图2是本申请实施例中基站识别跟踪用户终端的流程图；
图3是本申请实施例中双连接LTE侧先发起跟踪的流程图；
图4是本申请实施例中双连接NR侧发起跟踪的流程图；
图5是本申请实施例中切换场景的流程图；
图6是本申请实施例中基站识别UDP灌包UE的流程图；
图7是本申请实施例中通信节点设备的结构示意图。
具体实施方式
下面将参照附图更详细地描述本公开的示例性实施例。虽然附图中显示了本公开的示例性实施例，然而应当理解，可以以各种形式实现本公开而不应被这里阐述的实施例所限制。相反，提供这些实施例是为了能够更透彻地理解本公开，并且能够将本公开的范围完整的传达给本领域的技术人员。
在后续的描述中，使用用于表示元件的诸如“模块”、“部件”或“单元”的后缀仅为了有利于本申请的说明，其本身没有特定的意义。因此，“模块”、“部件”或“单元”可以混合地使用。
使用用于区分元件的诸如“第一”、“第二”等前缀仅为了有利于本申请的说明，其本身没有特定的意义。
本申请实施例提供一种终端的跟踪方法，如图1所示，所述方法包括：
S10，解析用户终端的上行报文；
S12，判断解析得到的上行报文特征是否满足预先配置的跟踪终端信息；
S14，在满足时，跟踪所述用户终端。
其中，跟踪终端即为基站需要跟踪的用户终端，跟踪终端信息可以包括上行报文的协议类型、对端IP地址和上行报文的数据包长度中一种或多种，当然还可以包括上行报文的数据包内容。协议类型可以是采用ICMP(Internet Control Message Protocol，Internet控制消息协议)协议ping(网络诊断工具)包请求，使用ping包请求的对端IP地址、ping包长度和数据包内容(数据包内容是可选的)；也可以是采用UDP(User Datagram Protocol，用户数据报协议)上行灌包协议，使用灌包的目的IP地址、UDP报文长度和数据包内容(数据包内容是可选的；还可以是可采用上行TCP(Transmission Control Protocol，传输控制协议)灌包的协议，使用灌包的目的IP地址和端口，TCP报文长度和数据包内容(数据包内容是可选的)。
本申请实施例中方法在通信节点侧执行，通信节点可以是基站等。
本申请实施例通过判断解析得到的上行报文特征是否满足预先配置的跟踪终端信息，从而在满足时就可以跟踪所述用户终端，进而不需要依赖于核心网，不需要通信节点设备与核心网的配合，进而可以快速准确的识别需要跟踪的用户终端，有效提高跟踪终端的识别率，并且可以实现连续跟踪，进而有效解决TMSI跟踪的方式连续跟踪困难的问题。
在上述原理性实施例的基础上，下面给出几个具体及可选实施方式，用以细化和优化本申请实施例，以使本申请实施例的方案的实施更方便，准确。需要说明的是，在不冲突的情况下，以下实施方式可以互相任意组合。
在一些实施方式中，所述判断解析得到的上行报文特征是否满足预先配置的跟踪终端信息之前，可以包括：
配置所述跟踪终端信息，所述跟踪终端信息包括上行报文的协议类型、对端IP地址和上行报文的数据包长度中一种或多种。
其中，所述跟踪终端信息还包括上行报文的数据包内容；
在所述跟踪终端信息为上行报文的数据包内容时，所述配置所述跟踪终端信息，包括：
在所述数据包的头部、中间或尾部配置所述数据包内容。
以基站为例，详细说，在一些实施方式中，可以向基站配置跟踪UE信息，例如，配置上行报文的协议类型，对端IP地址，数据包长度和数据包部分内容(数据包内容可以不配置，也可配置为头部部分数据或者中间部分数据、尾部部分数据，可以灵活配置)。
然后，UE终端发起相应的业务，如ping包请求或者UDP上行灌包。
即而，基站通过判断上行数据报文业务类型是否符合配置的协议类型，并且判断对端的IP地址、数据包长度、数据包内容(可选)，这几项是否都满足配置要求，如果满足则跟踪此UE。
其中，对端的IP地址可以是真实主机的IP地址，也可以是网络中没有配置的IP地址；对于数据包长度一般会指定特殊的长度，如ping请求一般不同于系统默认ping包长度32字节或者64字节，如97字节；或者数据包长度满足特殊条件，如长度模7为0，那么97、107、117等长度都满足要求。
以此类推，系统也可以配置一组IP地址和数据长度，识别出满足条件的多个UE。并且可以设置跟踪UE的数目，如果基站跟踪UE的数目达到一定数目的话，停止识别，减少系统资源消耗。
也就是说，在一些实施方式中，在所述跟踪终端信息为对端IP地址和上行报文的数据包长度时，所述配置所述跟踪终端信息，包括：
配置多对的对端IP地址和上行报文的数据包长度；其中，每对的对端IP地址和上行报文的数据包长度对应一个跟踪终端信息。所述在满足时，跟踪所述用户终端之后，包括：
在跟踪的用户终端达到预设数量时，停止解析用户终端的上行报文。
对于双连接的场景，如NSA场景，UE接入LTE之后，再添加5G基站作为辅连接。如果UE在添加辅连接之前发起相应业务，LTE基站识别出跟踪UE之后，在添加辅连接时将跟踪UE的信息，包括协议类型、对端的IP地址、数据包长度和数据包部分内容等信息，发送给5G基站，5G基站跟踪并上报此UE的跟踪数据。如果UE在添加辅连接完成之后，发起相应业务，5G基站识别出跟踪UE之后，通知主连接LTE基站该UE的跟踪信息。
也就是说，在一些实施方式中，所述判断解析得到的上行报文特征是否满足预先配置的跟踪终端信息，可以包括：
将所述上行报文特征与所述跟踪终端信息进行匹配；
根据匹配结果，判断所述上行报文特征是否满足所述跟踪终端信息。
如果UE发生切换，源侧基站携带UE信息到目标侧，目标侧基站跟踪并上报UE的跟踪数据。即是说，在一些实施方式中，在所述用户终端从主连接接入到辅连接时，将所述跟踪终端信息发送给所述辅连接。该实施方式在UE发生切换可以携带UE跟踪信息到目标侧基站，从而持续跟踪UE。
本申请实施例的一些实施方式中，通过解析UE上行报文，判断报文类型，并且使用对端的IP地址+数据包长度+数据包内容组合的方法，分析是否为需要跟踪的UE。数据包内容为可选条件，如果比较数据包内容的话，可以比较头部部分内容、或者尾部部分内容，也可比较中间部分内容，可以灵活配置。
上行报文可以采用ping包请求、或者UDP上行报文来判断。ping包请求可以设置特殊的对端IP地址，基站根据ping包的对端地址、ping包的长度等参数组合作为识别的依据。Ping包长度可以是一组特殊的长度地址(大多数操作系统默认长度是32字节或者64字节)，如长度为79、85等，或 者满足特殊的条件，如长度尾数为7，即ping包长度与7取余为0。UDP上行报文可以根据对端IP地址、报文长度、以及数据包部分内容作为识别跟踪UE，从而可以不依赖于核心网的前提下，快速准确的识别需要跟踪的UE，同时UE发生切换可以携带UE跟踪信息到目标侧基站，持续跟踪UE。
本申请实施例通过基站和UE之间的交互流程，描述实施例一所述涉及的终端的跟踪方法，如图2所示，交互流程包括：
步骤101，基站配置跟踪UE的跟踪终端信息，包括ping包请求对端的IP地址和ping包长度。
步骤102，UE侧发起ping包业务，并且ping包请求对端的IP地址和ping包长度满足基站配置的信息。也可以UE侧定制APP，预先设置好ping包请求对端的IP地址，及符合条件的ping包请求的长度。
步骤103，基站解析上行报文，识别如果是ICMP报文，解析报文类型为ping请求的对端IP地址和ping请求的数据包长度，如果解析结果满足配置的跟踪终端信息，则跟踪UE。
步骤104，基站上报跟踪UE相关的数据，如信令、调度信息等。
本申请实施例通过描述双连接场景主连接识别过程，描述实施例一所述涉及的终端的跟踪方法，本申请实施例以NSA组网为例，LTE的基站作为主连接，5G作为辅连接；如图3所示，识别过程包括：
步骤11，LTE、5G的基站通过网管配置跟踪UE信息，包括ping包的对端IP地址和ping包的长度。
步骤12，UE接入eNodeB，并且发起ping包请求。
步骤13，eNodeB解析上行报文，如果是ping包请求报文，并且对端IP地址和ping包长度满足跟踪UE信息，则跟踪此UE。
步骤14，UE测量到5G基站信息之后，上报到eNodeB，eNodeB添加 辅连接时将UE的跟踪信息(ping包对端IP地址和ping包长度)携带给5G基站。
步骤15，5G基站判断跟踪信息满足跟踪条件，则跟踪此UE。
本申请实施例通过双连接场景辅连接识别过程，描述实施例一所述涉及的终端的跟踪方法，本申请实施例以NSA组网为例，LTE的基站作为主连接，5G作为辅连接，如图4所示，识别过程包括：
步骤21，LTE、5G的基站通过网管配置跟踪UE信息，包括ping包的对端IP地址和ping包的长度。
步骤22，UE接入eNodeB。UE测量到5G基站小区之后，上报到eNodeB，eNodeB添加辅连接。
步骤23，UE发起ping包业务请求。
步骤24，基站识别跟踪UE，并上报数据。例如，5G基站解析上行报文，判断如果是ping包请求报文，并且ping包的对端IP地址和ping包长度满足跟踪UE信息，则跟踪此UE。
步骤25，通知主连接跟踪UE。例如，5G基站通过X2消息(如SN Modification Required)携带UE跟踪信息(ping包对端IP地址和ping包长度)到eNodeB侧。
步骤26，eNodeB判断UE的跟踪信息满足条件的话，则跟踪此UE。基站上报UE跟踪数据。
本申请实施例通过切换场景辅连接识别过程，描述实施例一所述涉及的终端的跟踪方法，本申请实施例切换场景，包括LTE的X2切换，5G基站的XN切换，如图5所示，识别过程包括：
步骤31，基站通过网管配置跟踪UE信息，包括ping包的对端IP地址和ping包的长度。基站包括切换的源站和目标站。
步骤32，UE接入或者切换入源站之后，发起ping包业务请求。
步骤33，基站上报UE跟踪。例如，源站解析UE的上行报文，如果是ping包请求报文，并且ping请求的对端IP地址和ping包长度满足条件的话，则跟踪此UE。
步骤34，UE发生切换，源站在切换请求消息中携带UE跟踪信息(ping包对端IP地址和ping包长度)到目标站。
步骤35，基站识别跟踪UE，并上报数据。例如，目标站判断跟踪信息满足条件的话，继续跟踪此UE。
本申请实施例通过基站识别UDP灌包UE过程，描述实施例一所述涉及的终端的跟踪方法，如图6所示，识别过程包括：
步骤201，基站配置跟踪UE的信息，包括报文类型为UDP上行报文、对端IP地址、UDP报文长度、校验的报文头部内容。
步骤202，UE侧发起上行UDP灌包业务。
步骤203，基站解析UE上行报文，识别如果是UDP报文，并且对端IP地址和数据包长度满足要求，再比较数据包头部内容与配置比对内容相符，则跟踪UE。
步骤204，基站跟踪此UE，并上报相关数据。
本申请实施例提供一种通信节点设备，所述通信节点设备包括存储器20和处理器22，所述存储器20存储有终端的跟踪程序，所述处理器22执行所述程序，以实现如实施例一至实施例六中任意一项所述方法的步骤。其中，通信节点设备可以是基站等通信节点。
本申请实施例提供一种计算机可读存储介质，所述存储介质存储有终端的跟踪程序，所述计算机程序可被至少一个处理器执行，以实现如任意 实施例所述方法的步骤。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。
上述本申请实施例序号仅仅为了描述，不代表实施例的优劣。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端(可以是手机，计算机，服务器，空调器，或者网络设备等)执行本申请各个实施例所述的方法。
上面结合附图对本申请的实施例进行了描述，但是本申请并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的，本领域的普通技术人员在本申请的启示下，在不脱离本申请宗旨和权利要求所保护的范围情况下，还可做出很多形式，这些均属于本申请的保护之内。

Claims (10)

  1. 一种终端的跟踪方法，所述方法包括：
    解析用户终端的上行报文；
    判断解析得到的上行报文特征是否满足预先配置的跟踪终端信息；
    在满足时，跟踪所述用户终端。
  2. 如权利要求1所述的方法，其中，所述判断解析得到的上行报文特征是否满足预先配置的跟踪终端信息之前，包括：
    配置所述跟踪终端信息，所述跟踪终端信息包括上行报文的协议类型、对端IP地址和上行报文的数据包长度中一种或多种。
  3. 如权利要求2所述的方法，其中，所述跟踪终端信息还包括上行报文的数据包内容；
    在所述跟踪终端信息为上行报文的数据包内容时，所述配置所述跟踪终端信息，包括：
    在所述数据包的头部、中间或尾部配置所述数据包内容。
  4. 如权利要求2所述的方法，其中，在所述跟踪终端信息为对端IP地址和上行报文的数据包长度时，所述配置所述跟踪终端信息，包括：
    配置多对的对端IP地址和上行报文的数据包长度；其中，每对的对端IP地址和上行报文的数据包长度对应一个跟踪终端信息。
  5. 如权利要求4所述的方法，其中，所述在满足时，跟踪所述用户终端之后，包括：
    在跟踪的用户终端达到预设数量时，停止解析用户终端的上行报文。
  6. 如权利要求1所述的方法，其中，所述判断解析得到的上行报文特征是否满足预先配置的跟踪终端信息，包括：
    将所述上行报文特征与所述跟踪终端信息进行匹配；
    根据匹配结果，判断所述上行报文特征是否满足所述跟踪终端信息。
  7. 如权利要求1-6中任意一项所述的方法，其中，所述方法还包括：
    在所述用户终端从主连接接入到辅连接时，将所述跟踪终端信息发送给所述辅连接。
  8. 如权利要求1-6中任意一项所述的方法，其中，所述方法还包括：
    在所述用户终端从源接入节点切换到目标节点时，将所述跟踪终端信息发送给所述目标节点。
  9. 一种通信节点设备，所述设备包括存储器和处理器，所述存储器存储有终端的跟踪程序，所述处理器执行所述程序，以实现如权利要求1至8中任意一项所述方法的步骤。
  10. 一种计算机可读存储介质，其中，所述存储介质存储有终端的跟踪程序，所述计算机程序可被至少一个处理器执行，以实现如权利要求1至8中任意一项所述方法的步骤。
PCT/CN2019/093910 2018-12-24 2019-06-28 一种终端的跟踪方法、设备及存储介质 WO2020133996A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811585304.3 2018-12-24
CN201811585304.3A CN111356165A (zh) 2018-12-24 2018-12-24 一种终端的跟踪方法、设备及存储介质

Publications (1)

Publication Number Publication Date
WO2020133996A1 true WO2020133996A1 (zh) 2020-07-02

Family

ID=71125898

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/093910 WO2020133996A1 (zh) 2018-12-24 2019-06-28 一种终端的跟踪方法、设备及存储介质

Country Status (2)

Country Link
CN (1) CN111356165A (zh)
WO (1) WO2020133996A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101272576A (zh) * 2007-03-19 2008-09-24 华为技术有限公司 一种用户信令跟踪方法及通讯系统以及用户设备
CN101330656A (zh) * 2008-07-08 2008-12-24 华为技术有限公司 一种根据终端的能力进行跟踪的方法
WO2017131442A1 (ko) * 2016-01-25 2017-08-03 삼성전자 주식회사 무선 통신 시스템에서 단말에 대한 추적(trace)을 수행하기 위한 방법 및 장치
CN107347193A (zh) * 2016-05-05 2017-11-14 大唐移动通信设备有限公司 一种信令跟踪方法和系统

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101132648A (zh) * 2007-10-11 2008-02-27 华为技术有限公司 基站跟踪方法及设备
WO2016000187A1 (zh) * 2014-06-30 2016-01-07 华为技术有限公司 消息处理方法和装置
CN107517458B (zh) * 2016-06-17 2022-06-21 中兴通讯股份有限公司 跟踪的确定方法及装置、终端

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101272576A (zh) * 2007-03-19 2008-09-24 华为技术有限公司 一种用户信令跟踪方法及通讯系统以及用户设备
CN101330656A (zh) * 2008-07-08 2008-12-24 华为技术有限公司 一种根据终端的能力进行跟踪的方法
WO2017131442A1 (ko) * 2016-01-25 2017-08-03 삼성전자 주식회사 무선 통신 시스템에서 단말에 대한 추적(trace)을 수행하기 위한 방법 및 장치
CN107347193A (zh) * 2016-05-05 2017-11-14 大唐移动通信设备有限公司 一种信令跟踪方法和系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
NOKIA: "CR R15 to TS 32422-f00 Add support for 5G Trace (triggering events in 5GC)", 3GPP TSG-SA5 MEETING #118 S5-182085, 13 April 2018 (2018-04-13), XP051433670, DOI: 20190819145745A *

Also Published As

Publication number Publication date
CN111356165A (zh) 2020-06-30

Similar Documents

Publication Publication Date Title
US20200374742A1 (en) Resource allocation method and apparatus
US11272555B2 (en) Data transmission channel processing method, apparatus, and system
US9264972B2 (en) Home networking with integrated cellular communication
US11811670B2 (en) Packet delay parameter obtaining method, system, and apparatus
EP3621360B1 (en) System information transmission method and related device
EP3720052A1 (en) Service identification method and device, and network device
WO2020199960A1 (zh) 时延获取方法及装置、优化方法及装置
US11109277B2 (en) Service configuration method and related product
US20230379747A1 (en) Method and apparatus to synchronize radio bearers
CN106454959B (zh) 一种分布式网络的服务质量控制方法、及服务器
US20210289400A1 (en) Selection of Edge Application Server
US20160119848A1 (en) Method for service data management, apparatus, and system
US11147039B2 (en) Paging strategy determination method, device, RAN network element and core network element
CN112087777A (zh) 一种mdbv的确定方法、装置及系统
JP7367186B2 (ja) ページング方法と機器
US8315192B2 (en) Method and system for configuring a media access control header to reduce a header overhead
US20230363024A1 (en) Transmission method, transmission apparatus, communication device, and readable storage medium
CN106572030B (zh) 一种分布式网络中多路径发送控制方法、及系统
US8773990B1 (en) Detecting unauthorized tethering
US11943145B2 (en) Apparatus, method, and computer program for determining time sensitive communication assistance information in a mobile communication system
US20220303201A1 (en) Traffic Monitoring in a Network Node
WO2020133996A1 (zh) 一种终端的跟踪方法、设备及存储介质
KR101929804B1 (ko) 세션 자원 관리 방법 및 장치
US20220116798A1 (en) Data transmission method, apparatus, and device
US11382022B2 (en) Method, apparatus, and computer program product for packet forwarding control protocol messages bundling

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19902440

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 18.11.2021)

122 Ep: pct application non-entry in european phase

Ref document number: 19902440

Country of ref document: EP

Kind code of ref document: A1