WO2013000259A1 - 跟踪用户的系统及方法、用户调度判决装置 - Google Patents

跟踪用户的系统及方法、用户调度判决装置 Download PDF

Info

Publication number
WO2013000259A1
WO2013000259A1 PCT/CN2011/084664 CN2011084664W WO2013000259A1 WO 2013000259 A1 WO2013000259 A1 WO 2013000259A1 CN 2011084664 W CN2011084664 W CN 2011084664W WO 2013000259 A1 WO2013000259 A1 WO 2013000259A1
Authority
WO
WIPO (PCT)
Prior art keywords
user
queue
reporting
signaling
tracking
Prior art date
Application number
PCT/CN2011/084664
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 WO2013000259A1 publication Critical patent/WO2013000259A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports

Definitions

  • the present invention relates to a technique for tracking users, and more particularly to a system and method for tracking users, and a user scheduling decision device. Background technique
  • the Radio Network Controller is an important entity in the access network part of the Universal Mobile Telecommunications System (UMTS), which is also the most abundant device entity of the wireless side protocol stack. Therefore, if the RNC is signaled, more comprehensive data can be obtained, and the interfaces of the base station, the core network, and the user terminal can be located.
  • UMTS Universal Mobile Telecommunications System
  • the main object of the present invention is to provide a system and method for tracking users, a user scheduling decision device, which can track a large number of users, and can provide tracking for as many users as possible by the tracking capability of the communication system. service.
  • a system for tracking users including a background, a tracking master, a tracking agent, and a user scheduling decision device;
  • the background is used to deliver a task request for the user to the tracking proxy
  • a tracking agent configured to send a user's application report signaling to the user scheduling decision device after receiving the task request
  • the user scheduling decision device is configured to determine whether the number of users allowed to report the queue has reached a set threshold after receiving the application report signaling, and add the user to the allowed report queue when not reached; It is prohibited to report the queue, and sends a stop report signaling to the tracking agent.
  • the background is further used to deliver a task stop request for the user to the tracking proxy;
  • the tracking agent After receiving the task stop request, the tracking agent sends the user's application to the user scheduling stop decision signaling;
  • the user scheduling decision device When the user scheduling decision device further determines that the user is in the report reporting queue, the user is deleted from the allowed reporting queue, and the user is selected from the forbidden reporting queue to be added to the allowed reporting queue. Sending an enable report signaling message to the tracking proxy; determining that the user is located in the forbidden reporting queue when the user is in the forbidden reporting queue.
  • the user scheduling determining device reports that the signaling reported by the user is reported to the tracking total control when the user is located in the allowable reporting queue; When the user is in the forbidden reporting queue, the signaling reported by the user is discarded.
  • a method of tracking users including:
  • the user After receiving the application report signaling, the user determines whether the number of users in the current report queue reaches the set threshold. When the threshold is reached, the user is added to the prohibition report queue. When the set threshold is not reached, the user is added to the allowable escalation queue.
  • the method further includes:
  • the method further includes:
  • the extracting a user from the forbidden reporting queue and adding to the allowed reporting queue is:
  • the user who extracts the minimum sending application report request from the prohibition reporting queue is added to the allowed reporting queue.
  • a user scheduling decision device includes a receiving unit, a determining unit, a first adding unit, and a second adding unit, wherein:
  • a receiving unit configured to receive a request signaling of the user
  • a determining unit configured to determine whether the number of users in the current allowed reporting queue reaches a set threshold, triggering the first adding unit when the set threshold is reached, and triggering the second adding unit when the set threshold is not reached;
  • a first adding unit configured to add the user to a forbidden reporting queue
  • a second adding unit configured to add the user to the allowed reporting queue.
  • the device further includes: a first deleting unit, a second deleting unit, and a third adding unit;
  • the receiving unit is further configured to: receive an application of the user to stop reporting signaling;
  • the determining unit is further configured to: determine whether the user is located in the forbidden reporting queue, and trigger a first deleting unit when the prohibiting reporting queue is located, and trigger a second deleting unit when the allowed reporting queue is located;
  • a first deleting unit configured to delete the user from the forbidden reporting queue
  • a second deleting unit configured to delete the user from the allowed reporting queue, and trigger a third adding port unit
  • a third adding unit configured to extract a user from the forbidden reporting queue, and add to the allowed queue.
  • the device further includes a discarding unit and a reporting unit;
  • the receiving unit is further configured to: receive signaling that is reported by the user;
  • the determining unit is further configured to: determine whether the user is located in the forbidden reporting queue, trigger a discarding unit when the prohibiting reporting queue, and trigger a reporting unit when not in the prohibiting reporting queue;
  • a discarding unit configured to discard signaling reported by the user
  • the reporting unit is configured to report the signaling reported by the user.
  • the third adding unit is further configured to: extract, according to the principle of first-in-first-out, the user that sends the minimum sending application report signaling from the forbidden reporting queue, and adds the user to the allowed reporting queue.
  • the user scheduling decision device when the user scheduling decision device is set to initiate a tracking related request to the user in the background, it is determined whether to track the user according to the number of users in the current allowed reporting queue, if the current tracking user number reaches the setting.
  • the threshold will add the user to the forbidden reporting queue.
  • the number of users in the allowed reporting queue is lower than the set threshold, the corresponding number of users will be selected from the forbidden reporting queue and added to the allowed reporting queue. Achieve tracking of users.
  • the invention enables the RNC to automatically track as many users as possible and improve tracking efficiency. With limited tracking resources, tracking of as many users as possible is achieved.
  • FIG. 1 is a schematic structural diagram of a system for tracking a user according to an embodiment of the present invention
  • FIG. 2 is a schematic diagram of starting a tracking task according to an embodiment of the present invention.
  • FIG. 3 is a schematic diagram of stopping a tracking task according to an embodiment of the present invention.
  • FIG. 4 is a schematic diagram of user reporting signaling according to an embodiment of the present invention.
  • FIG. 5 is a schematic structural diagram of a structure of a user scheduling decision apparatus according to an embodiment of the present invention. detailed description
  • the basic idea of the present invention is: When tracking multiple users, under normal circumstances, the simultaneously tracked users at the same time actually only occupy a small proportion; if the capability of the system is to allow simultaneous reporting of N users, at a certain time Segment, the probability of reporting signaling is P, then theoretically it is allowed to track N/P users without exceeding the tracking ability of the system; in the actual running process, once the simultaneously tracked users reach or exceed the system threshold Tracking and scheduling can be performed according to the first-in-first-out policy, ensuring that first-time users can report signaling first.
  • the invention realizes the control of the number of reporting signaling users by setting a user scheduling judging device, thereby realizing the tracking capability of the current system and realizing tracking of as many users as possible.
  • the number of users reporting the signaling is controlled by maintaining the reporting queue and the prohibiting reporting queue, thereby ensuring that the user reporting the signaling at the same time does not exceed the tracking capability of the system.
  • the size of the report queue is N. If the user is in the forbidden report queue, the user is not allowed to report the message.
  • the size of the queue is (N/P-N). User scheduling can only be determined based on the queue status.
  • N may be the number of users allowed by the system to simultaneously report signaling, and different systems have different N values.
  • the present invention is not limited to N being the maximum number of tracking users supported by the communication system, or Any number smaller than the maximum number of users tracked.
  • the value of N can be set according to the specific requirements of the operator.
  • the background, the tracking agent, and the tracking total control are all existing network elements in the current tracking system, so the functions thereof are not described too much, and their respective functions and structures may refer to existing standards. Just understand.
  • FIG. 1 is a schematic structural diagram of a system for tracking a user according to an embodiment of the present invention.
  • a system for tracking a user according to an embodiment of the present invention includes a background, a tracking master control, a tracking proxy, and a user scheduling judgment device;
  • the background is used to deliver a task request for the user to the tracking proxy
  • a tracking agent configured to send a user's application report signaling to the user scheduling decision device after receiving the task request
  • the user scheduling decision device is configured to determine whether the number of users allowed to report the queue has reached a set threshold after receiving the application report signaling, and the user is added to the allowed report queue when not reached; determining the user allowed to report the queue When the number reaches the set threshold, the user is added to the prohibition report queue, and the stop report signaling is sent to the tracking proxy.
  • the set threshold for the number of users allowed to report queues can be set according to the specific needs and the ability of the tracking system. Since it is not technically difficult, the detailed values will not be described.
  • the tracking agent first dispatches the judgment request report signaling to the user; when the user scheduling judgment device receives the user application report signaling, the user schedule first determines the user who is allowed to report the queue. If the number is full, if it is not full, add the user to the allowable reporting queue; otherwise, add the user to the forbidden reporting queue and send a stop reporting signaling message to the tracking proxy.
  • the background is further used to deliver a task stop request for the user to the tracking proxy;
  • the tracking agent After receiving the task stop request, the tracking agent sends the user's application to the user scheduling stop decision signaling;
  • the user scheduling decision device receives the user to stop the reporting signaling, and determines that the user is located in the allowable reporting queue, the user is deleted from the allowed reporting queue, and is selected from the forbidden reporting queue.
  • a user, added to the allowable reporting queue sends an allowable reporting signaling message to the tracking proxy; is located in the forbidden reporting queue, and deletes the user from the forbidden reporting queue.
  • the user who first sends the application report signaling in the forbidden report queue is added to the allowable report queue according to the principle of first-in-first-out, so that the user is added to the allowable report queue.
  • the added user can implement the tracking service. Of course, it can also be determined according to the priority of the user. For example, the user with the highest priority (the service priority or the user priority) is selected from the forbidden reporting queue and added to the allowed reporting queue.
  • the present invention is not limited to the principle of selecting a user from a prohibition reporting queue.
  • the tracking agent first dispatches a judgment request to the user to stop reporting the signaling; when the user scheduling judgment device receives the user to stop the reporting signaling, first determines which queue the user is in. If the user is allowed to report the queue, the user is deleted from the allowed reporting queue, and then a user is taken out from the forbidden reporting queue according to the principle of first in first out, the user is added to the allowed reporting queue, and the permission reporting signaling message is sent to the tracking proxy; If the queue is forbidden to report, the user is removed from the forbidden escalation queue.
  • the user scheduling decision device After the user scheduling decision device receives the signaling reported by the user of the tracking proxy, and determines that the user is located in the allowable reporting queue, the signaling reported by the user is reported to the tracking master control; The signaling reported by the user is discarded when the queue is reported.
  • the user scheduling decision device receives the signaling reported by the tracking agent, it determines which queue the corresponding user is in; if the user is in the allowable reporting queue, the user signaling is allowed to report to the tracking master; otherwise, the signaling is discarded. A stop report signaling message is sent to the tracking proxy.
  • the background sends the task to the tracking master control, and the tracking master control agent returns the response to the background after completing the verification; if the tracking master control verifies, the corresponding task start message is sent to the tracking agent; the tracking agent sends the application to the user scheduling judgment device.
  • the user scheduling decision device After reporting the signaling request, the user scheduling decision device sends a permission or prohibition reporting message to the tracking agent;
  • the tracking agent receives the signaling reported by the user, and sends the signaling to the user, and the user scheduling decision device determines whether the signaling of the user can be reported. If the reporting is allowed, the signaling is sent to the tracking master; otherwise, the signaling is discarded. And sending a stop signaling report message to the tracking proxy;
  • the tracking master After the tracking master receives the signaling, the signaling is sent to the background.
  • FIG. 2 is a schematic diagram of a tracking task startup according to an embodiment of the present invention. As shown in FIG. 2, a specific implementation manner of starting a tracking task is:
  • the tracking master sends a task start message to the tracking agent
  • the tracking agent sends an application reporting signaling message to the user scheduling decision device;
  • the user scheduling decision device determines whether the number of users allowed to report the queue is full; if not, the user is added to the allowable reporting queue, and the permission reporting message is sent to the tracking proxy; otherwise, the user is added to the prohibition reporting queue, and the tracking is performed.
  • the proxy sends a stop signaling message.
  • FIG. 3 is a schematic diagram of stopping a tracking task according to an embodiment of the present invention. As shown in FIG. 3, the specific implementation manner of stopping the tracking task in the embodiment of the present invention is:
  • the background sends a task stop message to the front desk to track the master control
  • the tracking master sends a task stop message to the tracking agent
  • the tracking agent sends a request to the user scheduling decision device to stop reporting the signaling message
  • FIG. 4 is a schematic diagram of user reporting signaling according to an embodiment of the present invention. As shown in FIG. 4, the specific implementation manner of user reporting signaling in the embodiment of the present invention is:
  • Tracking agent reports user signaling to the user scheduling decision device
  • the user scheduling decision device After the user scheduling decision device receives the signaling reported by the tracking agent, it determines which queue the corresponding user is in; if the user is in the allowable reporting queue, the user signaling is allowed to report to the tracking master; the tracking master will receive the signaling. Send to the background. If the user is in the forbidden reporting queue, the tracking proxy is sent a message prohibiting the user from reporting the message, and the user is prohibited from reporting the signaling.
  • FIG. 5 is a schematic structural diagram of a user scheduling decision apparatus according to an embodiment of the present invention.
  • the user scheduling decision apparatus includes a receiving unit 50, a determining unit 51, a first adding unit 52, and a second adding. Unit 53, wherein:
  • the receiving unit 50 is configured to receive an application report signaling of the user.
  • the determining unit 51 is configured to determine whether the number of users in the current allowed reporting queue reaches a set threshold, triggering the first adding unit 52 when the set threshold is reached, and triggering the second adding port unit 53 when the set threshold is not reached;
  • a first adding unit 52 configured to add the user to a forbidden reporting queue
  • the second adding unit 53 is configured to add the user to the allowed reporting queue.
  • the user scheduling decision apparatus of the embodiment of the present invention further includes: a first deleting unit (not shown in FIG. 5) and a second deleting unit (not shown in FIG. 5). And a third adding unit (not shown in Figure 5);
  • the receiving unit 50 is further configured to: receive, by the user, the application to stop reporting signaling;
  • the determining unit 51 is further configured to: determine whether the user is located in the forbidden reporting queue, and trigger the first deleting unit when the prohibiting reporting queue is located, and trigger the second deleting unit when the allowed reporting queue is located;
  • a first deleting unit configured to delete the user from the forbidden reporting queue
  • a second deleting unit configured to delete the user from the allowed reporting queue, and trigger a third Add force unit
  • a third adding unit configured to extract a user from the forbidden reporting queue, and add to the allowed queue.
  • the user scheduling decision device of the embodiment of the present invention further includes: a discarding unit (not shown in FIG. 5) and a reporting unit (not shown in FIG. 5);
  • the unit 50 is further configured to: receive signaling of the user's report;
  • the determining unit 51 is further configured to: determine whether the user is located in the forbidden reporting queue, trigger a discarding unit when the prohibiting reporting queue, and trigger a reporting unit when not in the prohibiting reporting queue;
  • a discarding unit configured to discard signaling reported by the user
  • the reporting unit is configured to report the signaling reported by the user.
  • the third adding unit is further configured to: extract, according to the principle of first-in-first-out, the user who sends the minimum sending application report signaling from the forbidden reporting queue, and adds the user to the allowed reporting queue.
  • the present invention can be applied not only to multi-VIP customer tracking, but also to other multi-user tracking scenarios.
  • the present invention can be applied to RNC and wireless network side devices, but its application range is not limited to the communication field, and can be applied to all devices that require data tracking.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)

Abstract

本发明公开了一种跟踪用户的系统，包括后台、跟踪总控、跟踪代理和用户调度判决装置；其中，后台，用于向跟踪代理下发针对用户的任务请求；跟踪代理，用于接收到任务请求后，向用户调度判决装置发送用户的申请上报信令；用户调度判决装置，用于接收到用户的申请上报信令后，确定允许上报队列的用户数是否已达到设定阈值，未达到时将所述用户添加到允许上报队列；达到时将该用户添加到禁止上报队列，并向跟踪代理发送停止上报信令。本发明同时公开了一种跟踪用户的方法以及用户调度判决装置。本发明能使RNC自动跟踪尽可能多的用户，提高了跟踪效率。利用有限的跟踪资源，实现了对尽可能多用户的跟踪。

Description

跟踪用户的系统及方法、 用户调度判决装置 技术领域
本发明涉及一种跟踪用户的技术， 尤其涉及一种跟踪用户的系统及方 法、 用户调度判决装置。 背景技术
无线网络控制器（RNC, Radio Network Controller )是通用移动通信系 统（UMTS , Universal Mobile Telecommunications System ) 中接入网部分的 重要实体， 其也是无线侧协议栈最丰富的设备实体。 因此， 若对 RNC进行 信令跟踪， 则能够得到较全面的数据， 而且能够定位基站、 核心网和用户 终端等设备的接口。
对于 VIP客户， 运营商需要长期跟踪用户的动向， 根据客户的业务信 令分析其业务特性， 从而为这类用户提供高质量的服务， 以更好地满足用 户的业务及服务需求。 由于跟踪用户的动向需要消耗不少的系统开销， 因 此， 一般的跟踪方法只能通过后台同时跟踪相当有限数量的 VIP客户。 随 着通信业务的不断发展， 竟争也相当激烈， 跟踪大量客户的需求越来越强 烈， 根据目前的跟踪方法， 显然无法跟踪大量客户， 甚至， 当需要跟踪的 客户达到几百个时， 传统的跟踪方法就不能实现了。 发明内容
有鉴于此， 本发明的主要目的在于提供一种跟踪用户的系统及方法、 用户调度判决装置， 能跟踪数量较大的用户， 并能以通信系统的跟踪能力， 为尽可能多的用户提供跟踪服务。
为达到上述目的， 本发明的技术方案是这样实现的： 一种跟踪用户的系统， 包括后台、 跟踪总控、 跟踪代理和用户调度判 决装置； 其中，
后台， 用于向跟踪代理下发针对用户的任务请求；
跟踪代理， 用于接收到任务请求后， 向用户调度判决装置发送用户的 申请上报信令；
用户调度判决装置， 用于接收到用户的申请上报信令后， 确定允许上 报队列的用户数是否已达到设定阈值， 未达到时将所述用户添加到允许上 报队列； 达到时将该用户添加到禁止上报队列， 并向跟踪代理发送停止上 报信令。
优选地， 所述后台还用于向所述跟踪代理下发针对用户的任务停止请 求；
所述跟踪代理接收到任务停止请求后， 向所述用户调度判决装置发送 用户的申请停止上报信令；
所述用户调度判决装置进一步接收到用户停止上报信令时， 确定所述 用户位于允许上报队列时， 从允许上报队列中删除该用户， 并从禁止上报 队列中选取一个用户， 添加到允许上报队列， 向跟踪代理发送允许上报信 令消息； 确定所述用户位于禁止上报队列时， 从禁止上报队列中删除该用 户。
优选地， 所述用户调度判决装置接收到所述跟踪代理的用户上报的信 令后， 确定所述用户位于允许上报队列时， 将所述用户上报的信令上报到 所述跟踪总控； 确定所述用户位于禁止上报队列时丟弃所述用户上报的信 令。
一种跟踪用户的方法， 包括：
接收到用户的申请上报信令后， 确定当前允许上报队列中的用户数量 是否达到设定阈值， 达到设定阈值时， 将所述用户添加到禁止上报队列， 未达到设定阈值时， 将所述用户添加到允许上报队列。
优选地， 所述方法还包括：
接收到用户的申请停止上报信令后， 确定所述用户位于所述禁止上报 队列时， 从所述禁止上报队列中删除该用户， 确定所述用户位于所述允许 上报队列时， 从所述允许上报队列中删除该用户， 并从所述禁止上报队列 中提取一个用户， 添加到所述允许上报队列中。
优选地， 所述方法还包括：
接收到用户的上报的信令后， 确定所述用户位于所述禁止上报队列时， 丟弃该用户上报的信令， 确定所述用户位于所述允许上报队列时， 将该用 户上报的信令上报。
优选地， 所述从所述禁止上报队列中提取一个用户， 添加到所述允许 上报队列中， 为：
按先进先出的原则 , 从所述禁止上报队列中提取最小发送申请上报信 令的用户， 添加到所述允许上报队列中。
一种用户调度判决装置， 包括接收单元、 确定单元、 第一添加单元和 第二添加单元， 其中：
接收单元， 用于接收用户的申请上报信令；
确定单元， 用于确定当前允许上报队列中的用户数量是否达到设定阈 值， 达到设定阈值时触发第一添加单元， 未达到设定阈值时触发第二添加 单元；
第一添加单元， 用于将所述用户添加到禁止上报队列；
第二添加单元， 用于将所述用户添加到允许上报队列。
优选地， 所述装置还包括： 第一删除单元、 第二删除单元和第三添加 单元；
所述接收单元还用于， 接收用户的申请停止上报信令； 所述确定单元还用于， 确定所述用户是否位于所述禁止上报队列， 位 于所述禁止上报队列时触发第一删除单元， 位于所述允许上报队列时触发 第二删除单元；
第一删除单元， 用于从所述禁止上报队列中删除所述用户；
第二删除单元， 用于从所述允许上报队列中删除该用户， 并触发第三 添力口单元；
第三添加单元， 用于从所述禁止上报队列中提取一个用户， 添加到所 述允许上 ·^艮队列中。
优选地， 所述装置还包括丟弃单元和上报单元；
所述接收单元还用于， 接收到用户的上报的信令；
所述确定单元还用于， 确定所述用户是否位于所述禁止上报队列， 位 于所述禁止上报队列时触发丟弃单元， 未位于所述禁止上报队列时触发上 报单元；
丟弃单元， 用于丟弃所述用户上报的信令；
上报单元， 用于将该用户上报的信令上报。
优选地， 所述第三添加单元还用于， 按先进先出的原则， 从所述禁止 上报队列中提取最小发送申请上报信令的用户， 添加到所述允许上报队列 中。
本发明中， 通过设置用户调度判决装置， 在后台发起对用户的跟踪相 关请求时， 将根据当前的允许上报队列中的用户数量， 确定是否对用户进 行跟踪， 若当前跟踪用户数量达到了设定的阈值， 将会将用户添加到禁止 上报队列中， 而当允许上报队列中的用户数量低于设定阈值时， 将会从禁 止上报队列中选取相应数量的用户， 添加到允许上报队列中， 实现对用户 的跟踪。 本发明能使 RNC自动跟踪尽可能多的用户， 提高了跟踪效率。 利 用有限的跟踪资源， 实现了对尽可能多用户的跟踪。 附图说明
图 1为本发明实施例的跟踪用户的系统的组成结构示意图；
图 2为本发明实施例的跟踪任务启动示意图；
图 3为本发明实施例的跟踪任务停止示意图；
图 4为本发明实施例的用户上报信令的示意图；
图 5为本发明实施例的用户调度判决装置的组成结构示意图。 具体实施方式
本发明的基本思想为： 当跟踪多个用户时， 正常情况下， 同时在线的 被跟踪用户实际只占较小比例； 如果系统的能力是允许同时 N个用户上报 信令， 而在某个时间段， 上报信令的概率是 P, 那么理论上可以允许跟踪 N/P个用户， 而不会超过系统的跟踪能力； 在实际的运行过程中， 一旦同时 在线的被跟踪用户达到或超过系统阈值， 可以按照先进先出的策略进行跟 踪调度， 确保先到的用户可以优先上报信令。 本发明通过设置用户调度判 决装置来实现对上报信令用户数量的控制， 从而实现利用当前系统的跟踪 能力， 实现对尽可能多用户的跟踪。
本发明中， 通过维护允许上报队列和禁止上报队列来控制上报信令的 用户数量， 从而确保同时上报信令的用户不超过系统的跟踪能力。 允许上 报队列的大小是 N, 如果用户位于禁止上报队列， 该用户就不允许上报信 令， 该队列的大小是（N/P-N )。 用户调度只根据队列状态进行判决即可。
本发明中， N可以为系统支持的允许同时上报信令的用户数量， 不同 的系统， 对应的 N值不同； 本发明并不限定于 N为通信系统所支持的最大 跟踪用户数， 也可以是比最大跟踪用户数小的任意数。 N值可以根据运营 商的具体要求而设定。
本发明中， 后台、 跟踪代理以及跟踪总控均为当前跟踪系统中的已有 网元， 因此对其功能不再过多描述， 其各自的功能及结构， 可参考现有标 准而理解。
为使本发明的目的、 技术方案和优点更加清楚明白， 以下举实施例并 参照附图， 对本发明进一步详细说明。
图 1为本发明实施例的跟踪用户的系统的组成结构示意图， 如图 1所 示， 本发明实施例的跟踪用户的系统包括后台、 跟踪总控、 跟踪代理和用 户调度判决装置； 其中，
后台， 用于向跟踪代理下发针对用户的任务请求；
跟踪代理， 用于接收到任务请求后， 向用户调度判决装置发送用户的 申请上报信令；
用户调度判决装置， 用于接收到用户的申请上报信令后， 确定允许上 报队列的用户数是否已达到设定阈值， 未达到时将所述用户添加到允许上 报队列； 确定允许上报队列的用户数达到设定阈值时， 将该用户添加到禁 止上报队列， 并向跟踪代理发送停止上报信令。
允许上报队列的用户数的设定阈值， 可根据具体需要及跟踪系统的能 力而设定， 由于不是技术难点， 不再赘述其详细取值。
具体的， 当后台下发任务请求到跟踪代理后， 跟踪代理先向用户调度 判决申请上报信令； 当用户调度判决装置接收到用户申请上报信令通知时， 用户调度首先确定允许上报队列的用户数是否已满； 如果未满， 将用户添 加到允许上报队列； 否则， 将该用户添加到禁止上报队列， 向跟踪代理发 送停止上报信令消息。
后台还用于向所述跟踪代理下发针对用户的任务停止请求；
所述跟踪代理接收到任务停止请求后， 向所述用户调度判决装置发送 用户的申请停止上报信令；
用户调度判决装置接收到用户停止上报信令时， 确定所述用户位于允 许上报队列时， 从允许上报队列中删除该用户， 并从禁止上报队列中选取 一个用户， 添加到允许上报队列， 向跟踪代理发送允许上报信令消息； 位 于禁止上报队列， 从禁止上报队列中删除该用户。 其中， 从禁止上报队列 中选取一个用户添加到允许上报队列时， 一般根据先进先出的原则， 选取 禁止上报队列中最先发送申请上报信令的用户， 添加到允许上报队列， 这 样， 该被添加的用户即可实现跟踪服务。 当然， 也可以根据用户的优先级 来确定， 例如， 从禁止上报队列中选取优先级（业务优先级或用户优先级） 最高的用户， 添加到允许上报队列。 本发明不限定于从禁止上报队列中选 取用户的原则。
具体的， 当后台下发任务停止请求到跟踪代理后， 跟踪代理先向用户 调度判决申请停止上报信令； 当用户调度判决装置接收到用户停止上报信 令通知时， 先确定用户是位于哪个队列； 如果位于允许上报队列， 从允许 上报队列中删除该用户， 然后从禁止上报队列中按照先进先出的原则取出 一个用户， 将该用户添加允许上报队列， 向跟踪代理发送允许上报信令消 息； 如果位于禁止上报队列， 从禁止上报队列中删除该用户。
用户调度判决装置接收到所述跟踪代理的用户上报的信令后， 确定所 述用户位于允许上报队列时， 将所述用户上报的信令上报到所述跟踪总控； 确定所述用户位于禁止上报队列时丟弃所述用户上报的信令。
具体的， 当用户调度判决装置接收到跟踪代理上报的信令后， 确定对 应用户位于哪个队列； 如果用户位于允许上报队列， 那么此用户信令允许 上报到跟踪总控； 否则丟弃信令， 向跟踪代理发送停止上报信令消息。
结合图 1 , 以下对本发明实施方式的跟踪用户的系统进行总体描述。 后台下发任务到跟踪总控， 跟踪总控代理完成校验后向后台回响应； 若跟踪总控校验通过， 则将相应任务启动消息发送给跟踪代理； 跟踪代理向用户调度判决装置发送申请上报信令请求， 用户调度判决 装置进行判决后， 向跟踪代理发送允许或者禁止上报消息； 跟踪代理接收到用户上报的信令， 发送给用户调度判决装置； 用户调度判决装置判决该用户的信令是否可以上报， 如果允许上报， 将信令发送到跟踪总控； 否则， 丟弃信令， 并向跟踪代理发送停止信令上 报消息；
跟踪总控接收到信令后 , 将信令发送到后台。
图 2为本发明实施例的跟踪任务启动示意图， 如图 2所示， 启动跟踪 任务的具体实现方式为：
后台下发任务启动消息到跟踪总控；
跟踪总控进行基本校验通过后， 向后台发送任务启动应答；
跟踪总控向跟踪代理发送任务启动消息；
跟踪代理向用户调度判决装置发送申请上报信令消息；
用户调度判决装置确定允许上报队列的用户数是否已满； 如果未满， 将用户添加到允许上报队列， 向跟踪代理发送允许上报信令消息； 否则， 将该用户添加到禁止上报队列， 向跟踪代理发送停止上报信令消息。
图 3为本发明实施例的跟踪任务停止示意图， 如图 3所示， 本发明实 施例的跟踪任务停止具体实现方式为：
后台下发任务停止消息到前台跟踪总控；
跟踪总控进行基本校验通过后， 向后台发送任务停止应答；
跟踪总控向跟踪代理发送任务停止消息；
跟踪代理向用户调度判决装置发送申请停止上报信令消息；
用户调度判决装置接收到消息后， 先确定用户是位于哪个队列； 如果 位于允许上报队列， 则从允许上报队列中删除该用户， 然后从禁止上报队 列中按照先进先出的原则取出一个用户， 将该用户添加允许上报队列， 向 跟踪代理发送允许上报信令消息； 如果位于禁止上报队列， 则从禁止上报 队列中删除该用户。 图 4为本发明实施例的用户上报信令的示意图， 如图 4所示， 本发明 实施例的用户上报信令的具体实现方式为：
跟踪代理上报用户信令到用户调度判决装置；
当用户调度判决装置接收到跟踪代理上报的信令后， 确定对应用户位 于哪个队列； 如果用户位于允许上报队列， 那么此用户信令允许上报到跟 踪总控； 跟踪总控将接收到的信令发送到后台。 如果用户位于禁止上报队 列， 则向跟踪代理发送禁止用户上报信令消息， 禁止用户上报信令。
图 5 为本发明实施例的用户调度判决装置的组成结构示意图， 如图 5 所示， 本发明实施例的用户调度判决装置包括接收单元 50、 确定单元 51、 第一添加单元 52和第二添加单元 53 , 其中：
接收单元 50, 用于接收用户的申请上报信令；
确定单元 51 , 用于确定当前允许上报队列中的用户数量是否达到设定 阈值， 达到设定阈值时触发第一添加单元 52, 未达到设定阈值时触发第二 添力口单元 53;
第一添加单元 52, 用于将所述用户添加到禁止上报队列；
第二添加单元 53 , 用于将所述用户添加到允许上报队列。
在图 5 所示的用户调度判决装置的基础上， 本发明实施例的用户调度 判决装置还包括： 第一删除单元（图 5中未示出）、 第二删除单元（图 5中 未示出 )和第三添加单元（图 5中未示出）；
接收单元 50还用于， 接收用户的申请停止上报信令；
确定单元 51还用于， 确定所述用户是否位于所述禁止上报队列， 位于 所述禁止上报队列时触发第一删除单元， 位于所述允许上报队列时触发第 二删除单元；
第一删除单元， 用于从所述禁止上报队列中删除所述用户；
第二删除单元， 用于从所述允许上报队列中删除该用户， 并触发第三 添力口单元；
第三添加单元， 用于从所述禁止上报队列中提取一个用户， 添加到所 述允许上 ·^艮队列中。
在图 5 所示的用户调度判决装置的基础上， 本发明实施例的用户调度 判决装置还包括： 丟弃单元（图 5中未示出）和上报单元（图 5中未示出）； 接收单元 50还用于， 接收到用户的上报的信令；
确定单元 51还用于， 确定所述用户是否位于所述禁止上报队列， 位于 所述禁止上报队列时触发丟弃单元， 未位于所述禁止上报队列时触发上报 单元；
丟弃单元， 用于丟弃所述用户上报的信令；
上报单元， 用于将该用户上报的信令上报。
上述第三添加单元还用于， 按先进先出的原则， 从所述禁止上报队列 中提取最小发送申请上报信令的用户， 添加到所述允许上报队列中。
本领域技术人员应当理解， 本发明的用户调度判决装置中的上述处理 单元的功能可通过相应的硬件电路， 或处理器及相应的执行软件的方式而 实现。 上述各处理单元的相关功能， 可参见前述实施例的相关描述而理解。
本发明不仅仅可以应用于多 VIP客户跟踪， 而且也可以用于其它多用 户跟踪场景。 本发明可以应用于 RNC和无线网络侧设备中， 但其适用范围 不仅限于通信领域， 也可以被应用在所有需要数据跟踪的设备中。
以上所述， 仅为本发明的较佳实施例而已， 并非用于限定本发明的保 护范围。

Claims

权利要求书
1、 一种跟踪用户的系统， 包括后台、 跟踪总控和跟踪代理， 其特征在 于， 所述系统还包括用户调度判决装置； 其中，
后台， 用于向跟踪代理下发针对用户的任务请求；
跟踪代理， 用于接收到任务请求后， 向用户调度判决装置发送用户的 申请上报信令；
用户调度判决装置， 用于接收到用户的申请上报信令后， 确定允许上 报队列的用户数是否已达到设定阈值， 未达到时将所述用户添加到允许上 报队列； 达到时将该用户添加到禁止上报队列， 并向跟踪代理发送停止上 报信令。
2、 根据权利要求 1所述的系统， 其特征在于， 所述后台还用于向所述 跟踪代理下发针对用户的任务停止请求；
所述跟踪代理接收到任务停止请求后， 向所述用户调度判决装置发送 用户的申请停止上报信令；
所述用户调度判决装置接收到用户停止上报信令时， 确定所述用户位 于允许上报队列时， 从允许上报队列中删除该用户， 并从禁止上报队列中 选取一个用户， 添加到允许上报队列， 向跟踪代理发送允许上报信令消息； 确定所述用户位于禁止上报队列时， 从禁止上报队列中删除该用户。
3、 根据权利要求 1或 2所述的系统， 其特征在于， 所述用户调度判决 装置接收到所述跟踪代理的用户上报的信令后， 确定所述用户位于允许上 报队列时， 将所述用户上报的信令上报到所述跟踪总控； 确定所述用户位 于禁止上报队列时丟弃所述用户上报的信令。
4、 一种跟踪用户的方法， 其特征在于， 所述方法包括：
接收到用户的申请上报信令后， 确定当前允许上报队列中的用户数量 是否达到设定阈值， 达到设定阈值时， 将所述用户添加到禁止上报队列， 未达到设定阈值时， 将所述用户添加到允许上报队列。
5、 根据权利要求 4所述的方法， 其特征在于， 所述方法还包括： 接收到用户的申请停止上报信令后， 确定所述用户位于所述禁止上报 队列时， 从所述禁止上报队列中删除该用户， 确定所述用户位于所述允许 上报队列时， 从所述允许上报队列中删除该用户， 并从所述禁止上报队列 中提取一个用户， 添加到所述允许上报队列中。
6、 根据权利要求 4或 5所述的方法， 其特征在于， 所述方法还包括： 接收到用户的上报的信令后， 确定所述用户位于所述禁止上报队列时， 丟弃该用户上报的信令， 确定所述用户位于所述允许上报队列时， 将该用 户上报的信令上报。
7、 根据权利要求 5所述的方法， 其特征在于， 所述从所述禁止上报队 列中提取一个用户， 添加到所述允许上报队列中， 为：
按先进先出的原则 , 从所述禁止上报队列中提取最小发送申请上报信 令的用户， 添加到所述允许上报队列中。
8、 一种用户调度判决装置， 其特征在于， 所述装置包括接收单元、 确 定单元、 第一添加单元和第二添加单元， 其中：
接收单元， 用于接收用户的申请上报信令；
确定单元， 用于确定当前允许上报队列中的用户数量是否达到设定阈 值， 达到设定阈值时触发第一添加单元， 未达到设定阈值时触发第二添加 单元；
第一添加单元， 用于将所述用户添加到禁止上报队列；
第二添加单元， 用于将所述用户添加到允许上报队列。
9、 根据权利要求 8所述的装置， 其特征在于， 所述装置还包括： 第一 删除单元、 第二删除单元和第三添加单元；
所述接收单元还用于， 接收用户的申请停止上报信令； 所述确定单元还用于， 确定所述用户是否位于所述禁止上报队列， 位 于所述禁止上报队列时触发第一删除单元， 位于所述允许上报队列时触发 第二删除单元；
第一删除单元， 用于从所述禁止上报队列中删除所述用户；
第二删除单元， 用于从所述允许上报队列中删除该用户， 并触发第三 添力口单元；
第三添加单元， 用于从所述禁止上报队列中提取一个用户， 添加到所 述允许上 ·^艮队列中。
10、 根据权利要求 8或 9所述的装置， 其特征在于， 所述装置还包括 丟弃单元和上报单元；
所述接收单元还用于， 接收到用户的上报的信令；
所述确定单元还用于， 确定所述用户是否位于所述禁止上报队列， 位 于所述禁止上报队列时触发丟弃单元， 未位于所述禁止上报队列时触发上 报单元；
丟弃单元， 用于丟弃所述用户上报的信令；
上报单元， 用于将该用户上报的信令上报。
11、 根据权利要求 9所述的装置， 其特征在于， 所述第三添加单元还 用于， 按先进先出的原则， 从所述禁止上报队列中提取最小发送申请上报 信令的用户， 添加到所述允许上报队列中。
PCT/CN2011/084664 2011-06-29 2011-12-26 跟踪用户的系统及方法、用户调度判决装置 WO2013000259A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110179800.0A CN102857937B (zh) 2011-06-29 2011-06-29 跟踪用户的系统及方法、用户调度判决装置
CN201110179800.0 2011-06-29

Publications (1)

Publication Number Publication Date
WO2013000259A1 true WO2013000259A1 (zh) 2013-01-03

Family

ID=47404054

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/084664 WO2013000259A1 (zh) 2011-06-29 2011-12-26 跟踪用户的系统及方法、用户调度判决装置

Country Status (2)

Country Link
CN (1) CN102857937B (zh)
WO (1) WO2013000259A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103747484B (zh) * 2014-01-28 2017-06-09 大唐移动通信设备有限公司 一种rim流程系统信息处理方法和服务节点设备

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1529447A (zh) * 2003-10-17 2004-09-15 中兴通讯股份有限公司 移动通信网络协议信令分析系统和方法
CN1929666A (zh) * 2005-09-05 2007-03-14 中兴通讯股份有限公司 一种移动通信网络协议信令处理系统和方法
US20070201621A1 (en) * 2004-06-15 2007-08-30 Cisco Technology, Inc. System and Method for End-To-End Communications Tracing
CN101141764A (zh) * 2007-10-09 2008-03-12 中兴通讯股份有限公司 一种解决大话务下信令跟踪控制失效的方法
EP2051548A1 (en) * 2007-10-17 2009-04-22 Nokia Siemens Networks Oy Signalling based trace activation from SGSN towards GGSN
CN101917699A (zh) * 2010-07-20 2010-12-15 中兴通讯股份有限公司 基于用户的随机上报信令跟踪方法和装置

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101217499B (zh) * 2008-01-21 2010-12-01 中兴通讯股份有限公司 队列调度方法
CN101527654B (zh) * 2009-04-20 2012-01-25 中兴通讯股份有限公司 一种网管系统中的数据传输方法及系统

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1529447A (zh) * 2003-10-17 2004-09-15 中兴通讯股份有限公司 移动通信网络协议信令分析系统和方法
US20070201621A1 (en) * 2004-06-15 2007-08-30 Cisco Technology, Inc. System and Method for End-To-End Communications Tracing
CN1929666A (zh) * 2005-09-05 2007-03-14 中兴通讯股份有限公司 一种移动通信网络协议信令处理系统和方法
CN101141764A (zh) * 2007-10-09 2008-03-12 中兴通讯股份有限公司 一种解决大话务下信令跟踪控制失效的方法
EP2051548A1 (en) * 2007-10-17 2009-04-22 Nokia Siemens Networks Oy Signalling based trace activation from SGSN towards GGSN
CN101917699A (zh) * 2010-07-20 2010-12-15 中兴通讯股份有限公司 基于用户的随机上报信令跟踪方法和装置

Also Published As

Publication number Publication date
CN102857937B (zh) 2018-01-30
CN102857937A (zh) 2013-01-02

Similar Documents

Publication Publication Date Title
US11252196B2 (en) Method for managing data traffic within a network
WO2016065552A1 (zh) 一种心跳周期的设置方法及终端
US10171351B2 (en) Method for updating flow table
WO2016015465A1 (zh) 基于mbms承载的集群通信中拥塞状态上报方法及系统、存储介质
WO2016015472A1 (zh) 基于mbms承载的集群通信中查询节点状态的方法及系统、存储介质
CN107404759B (zh) 一种寻呼方法及装置
CN105336013B (zh) 一种通过信标广播实现点名的方法和系统
CN102413054B (zh) 数据流量控制方法、装置及系统、网关设备、交换机设备
KR20180046894A (ko) Nfv 기반 메시징 서비스 보안 제공 방법 및 이를 위한 시스템
WO2012089061A1 (zh) 一种识别并阻止设备发送垃圾短信的方法、设备和系统
WO2012139466A1 (zh) 一种资源的管理方法和设备
US20190036793A1 (en) Network service implementation method, service controller, and communications system
CN101141711B (zh) 一种集群系统资源建立的并行处理方法
WO2013000259A1 (zh) 跟踪用户的系统及方法、用户调度判决装置
WO2011026345A1 (zh) 一种深度报文检测系统及报文处理方法
WO2011140736A1 (zh) 网络实体和非结构化补充数据业务中保护数据的方法
CN104469745B (zh) 一种完整性保护参数的应用方法及装置
CN104660506B (zh) 一种数据包转发的方法、装置及系统
CN106470421A (zh) 一种防止恶意终端非法占用核心网资源的方法和设备
CN106301531B (zh) 基于卫星数字传输系统的专网通信方法
KR20150093194A (ko) 원격통신 네트워크에서 모바일 제어 장치
CN106992878B (zh) 一种组播检测的方法及装置
CN101883332A (zh) 集群通信系统中实现回叫请求业务的方法、系统及装置
KR20110069473A (ko) 모바일 애플리케이션과 서비스 서버 간의 중계 서버 및 이를 포함하는 무선 인터넷 통신 시스템
CN105264823A (zh) 一种位置信息上报方法、设备及系统

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: 11868691

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 11868691

Country of ref document: EP

Kind code of ref document: A1