CN109660996A - user number monitoring method, network element entity and storage medium - Google Patents
user number monitoring method, network element entity and storage medium Download PDFInfo
- Publication number
- CN109660996A CN109660996A CN201710936232.1A CN201710936232A CN109660996A CN 109660996 A CN109660996 A CN 109660996A CN 201710936232 A CN201710936232 A CN 201710936232A CN 109660996 A CN109660996 A CN 109660996A
- Authority
- CN
- China
- Prior art keywords
- monitoring
- user number
- entity
- application server
- number threshold
- Prior art date
- Legal status (The legal status 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 status listed.)
- Granted
Links
- 238000012544 monitoring process Methods 0.000 title claims abstract description 422
- 238000000034 method Methods 0.000 title claims abstract description 56
- 238000013507 mapping Methods 0.000 claims description 38
- 238000004590 computer program Methods 0.000 claims description 17
- 238000004891 communication Methods 0.000 description 12
- 238000010586 diagram Methods 0.000 description 7
- 230000008859 change Effects 0.000 description 6
- 230000003993 interaction Effects 0.000 description 6
- 230000005540 biological transmission Effects 0.000 description 5
- 230000006870 function Effects 0.000 description 4
- 238000007726 management method Methods 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000006243 chemical reaction Methods 0.000 description 2
- 238000012790 confirmation Methods 0.000 description 2
- 230000007423 decrease Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 238000006467 substitution reaction Methods 0.000 description 2
- SPBWHPXCWJLQRU-FITJORAGSA-N 4-amino-8-[(2r,3r,4s,5r)-3,4-dihydroxy-5-(hydroxymethyl)oxolan-2-yl]-5-oxopyrido[2,3-d]pyrimidine-6-carboxamide Chemical compound C12=NC=NC(N)=C2C(=O)C(C(=O)N)=CN1[C@@H]1O[C@H](CO)[C@@H](O)[C@H]1O SPBWHPXCWJLQRU-FITJORAGSA-N 0.000 description 1
- 102100021677 Baculoviral IAP repeat-containing protein 2 Human genes 0.000 description 1
- 102100021662 Baculoviral IAP repeat-containing protein 3 Human genes 0.000 description 1
- 101000896157 Homo sapiens Baculoviral IAP repeat-containing protein 2 Proteins 0.000 description 1
- 101000896224 Homo sapiens Baculoviral IAP repeat-containing protein 3 Proteins 0.000 description 1
- 102100027069 Odontogenic ameloblast-associated protein Human genes 0.000 description 1
- 101710091533 Odontogenic ameloblast-associated protein Proteins 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000001914 filtration Methods 0.000 description 1
- 230000009191 jumping Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 230000011664 signaling Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/02—Arrangements for optimising 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/16—Threshold monitoring
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
- Telephonic Communication Services (AREA)
Abstract
The embodiment of the invention discloses a user number monitoring method, a monitoring network element and a storage medium. The user number monitoring method applied to the monitoring entity comprises the following steps: receiving a monitoring request carrying monitoring parameters; wherein the monitoring parameters include at least: a user number threshold; monitoring the number of users in a designated area; and if the current user number exceeds the user number threshold value, sending a monitoring result to the application server.
Description
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a user number monitoring method, a monitoring network element, and a storage medium.
Background
With the increase of internet services, the provider of internet services needs to dynamically adjust the network capability provided for the internet services according to the number of users, user requirements and the like, so as to ensure the quality and capability of providing the services. Therefore, in order to meet the above requirements of the service provider in network operation, a capability opening architecture is proposed, which opens the network capability of the communication network in network operation and the like to the service provider.
Fig. 1 shows a network capability open architecture. In fig. 1, an Application Server (AS) may directly call control Capability of each network element of a core network of mobile communication or extract some network-aware information through a Service Capability Exposure Function (SCEF) or indirectly through a Service Capability Server (SCS).
In fig. 1, n Application Programming Interfaces (APIs), i.e., API1 and API2 … … APIn, are shown, and can be used for access by SCS or AS. Various network elements in the communication network, for example, network elements of the communication network such as a Mobility Management Entity (MME), a Policy and Charging Rules Function (PCRF), a Home Subscriber Server (HSS), a System Architecture Evolution Gateway (SAE-GW), a Packet Flow Description Function (PFDF), and a Radio Congestion Awareness Function (RCAF), are connected to the SCEF through various interfaces. Network operators are in security concern, isolating networks as trust domains and other domains outside of trust domains. If the AS is provided by a provider other than the network operator itself, it may generally be a third-party AS, which is generally located in another domain, but needs to be supported by the network of the trust domain to provide data transmission of the service.
The application server of the third party, which may be referred to as a third party application server for short, generally has a demand for acquiring the number of users in a certain area, so as to facilitate operations such as capacity expansion or load balancing according to the number of users in the area, and provide better service quality.
In the prior art, a third-party server sends a request to a specific network element of a communication network, the network element returns the number of currently monitored users to the third-party server, and the number of users in the area changes substantially in the transmission process, and the mode based on the request of the third-party server is often seriously lagged behind the actual demand, for example, when the third-party server finds that congestion occurs currently, the third-party server requests the number of users again, and determines whether capacity expansion is performed based on the number of users, so that the method obviously has serious hysteresis; this obviously leads to a problem of poor experience for the user.
Disclosure of Invention
In view of the above, embodiments of the present invention are directed to a user quantity monitoring method, a monitoring network element, and a storage medium, which at least partially solve the above problems.
In order to achieve the purpose, the technical scheme of the invention is realized as follows:
in a first aspect, an embodiment of the present invention provides a user number monitoring method, which is applied to a monitoring entity, and includes:
receiving a monitoring request carrying monitoring parameters; wherein the monitoring parameters include at least: a user number threshold;
monitoring the number of users in a designated area;
and if the current user number exceeds the user number threshold value, sending a monitoring result to the application server.
Optionally, the number of the user number threshold is N, which is respectively a 1 st user number threshold to an nth user number threshold, where the nth user number threshold is smaller than an N +1 st user number threshold; n is less than N, N is an integer not less than 2, and N is a positive integer;
the monitoring parameters further include: mapping rules and reporting rules; wherein the mapping rule comprises: exceeding the corresponding relation between the threshold identification and the user number threshold;
if the current user number exceeds the user number threshold, sending a monitoring result to an application server, including:
if the current user number exceeds an mth user number threshold, determining a monitoring result according to the mapping rule, wherein the monitoring result comprises: an exceeding threshold identification corresponding to the mth user number threshold;
and sending the monitoring result to the application server according to a reporting rule.
Optionally, the monitoring parameters further include: a location monitoring type;
the monitoring the number of users in the designated area comprises:
tracking the position parameters of the user equipment according to the position monitoring type;
and counting the number of users in the designated area according to the position parameters.
Optionally, the tracking, according to the location monitoring type, a location parameter of the user equipment includes:
when the position monitoring type is a real-time monitoring type, tracking the current position of the user equipment in real time;
the counting the number of users in the designated area according to the position parameters includes:
and counting the number of users in the designated area according to the current position of the user equipment.
Optionally, the tracking, according to the location monitoring type, a location parameter of the user equipment includes:
when the position monitoring type is a tracking area updating type, determining an updating position according to the latest tracking area updating of the user equipment;
the counting the number of users in the designated area according to the position parameters includes:
and counting the number of users in the designated area according to the updated position.
Optionally, if the current number of users exceeds the user number threshold, sending a monitoring result to the application server, including:
if the current user number exceeds the user number threshold value and the monitoring parameter comprises monitoring time, sending the monitoring result to the application server within the monitoring time;
or,
and if the current user number exceeds the user number threshold and the monitoring parameter does not include the monitoring time, continuously sending the monitoring result to the application server according to a preset mode until a sending end event is detected.
Optionally, the monitoring entity is a mobility management entity MME or a general packet radio service support node SGSN;
if the current user number exceeds the user number threshold, sending a monitoring result to an application server, including:
the MME or the SGSN sends the monitoring result to the application server through an access entity;
or,
the MME or the SGSN sends the monitoring result to a policy and charging rule entity (PCRF); and the monitoring result is used for forwarding the PCRF to the application server through the access entity.
A second aspect of the embodiments of the present invention provides a method for monitoring a number of users, which is applied to an access entity, and includes:
receiving a monitoring request which is sent by an application server and carries monitoring parameters, wherein the monitoring parameters comprise: a user number threshold;
forwarding the monitoring request to a monitoring entity;
receiving a monitoring result sent by the monitoring entity when the monitoring entity detects that the number of users in the designated area exceeds the user number threshold;
and sending the monitoring result to the application server.
Optionally, the monitoring parameters further include: a geographic location parameter for the specified area;
the method further comprises the following steps:
determining a network parameter corresponding to the geographic position parameter according to the coverage condition of the network on the geographic area;
the forwarding the monitoring request to the monitoring entity includes:
and sending the monitoring request to the monitoring entity which can monitor the designated area according to the network parameters.
A third aspect of the embodiments of the present invention provides a method for monitoring a number of users, where an application server includes:
sending a monitoring request to an access entity, wherein the monitoring request carries monitoring parameters, and the monitoring parameters comprise: a user number threshold;
and receiving a monitoring result sent by the monitoring entity when the number of users in the designated area exceeds the user number threshold.
Optionally, the monitoring parameters further include at least one of:
a mapping rule, wherein the mapping rule comprises: the mapping relation between the user number threshold and the mark exceeding the threshold;
reporting rules, wherein the reporting rules are used for the monitoring entity to send monitoring results;
a geographic location parameter for the designated area;
the time is monitored.
A fourth aspect of the present invention provides a network element entity, where the network element entity is a monitoring entity, and the network element entity includes:
the first receiving unit is used for receiving a monitoring request carrying monitoring parameters; wherein the monitoring parameters include at least: a user number threshold;
the monitoring unit is used for monitoring the number of users in the designated area;
and the first sending unit is used for sending a monitoring result to the application server if the current user number exceeds the user number threshold.
A fifth aspect of the present invention provides a network element entity, where the network element entity is an access entity, and the network element entity includes:
a second receiving unit, configured to receive a monitoring request with monitoring parameters sent by an application server, where the monitoring parameters include: a user number threshold;
a second sending unit, configured to forward the monitoring request to a monitoring entity;
the second receiving unit is further configured to receive a monitoring result sent by the monitoring entity when detecting that the number of users in the designated area exceeds the user number threshold;
the second sending unit is further configured to send the monitoring result to the application server.
A sixth aspect of the present embodiment provides a network element entity, where the network element entity is an application server, and the network element entity includes:
a third sending unit, configured to send a monitoring request to an access entity, where the monitoring request carries monitoring parameters, where the monitoring parameters include: a user number threshold;
and the third receiving unit is used for receiving a monitoring result sent by the monitoring entity when the number of users in the designated area exceeds the user number threshold.
A seventh aspect of the present embodiment provides a network element entity, including: a transceiver, a memory, a processor, and a computer program stored on the memory and executed by the processor;
the processor is respectively connected with the transceiver and the memory, and is used for realizing the user number monitoring method provided by one or more schemes by executing the computer program.
An eighth aspect of the present invention provides a network element entity, including: a transceiver, a memory, and a processor;
the processor is respectively connected with the transceiver and the memory and is used for realizing the user number monitoring method provided by one or more schemes by executing a computer program.
A ninth aspect of the embodiments of the present invention provides a computer storage medium, in which a computer program is stored; the computer program can implement one or more of the above schemes to provide a user number monitoring method after being executed.
According to the user number monitoring method, the monitoring network element and the storage medium provided by the embodiment of the invention, the monitoring request received by the monitoring entity carries the user number threshold value, the monitoring entity monitors the user number in the designated area, and the monitoring result is sent to the application server only when the user number exceeds the user number threshold value, so that the problem that the monitoring result is complicated to obtain because the monitoring result is sent once when the application server requests for once is avoided, and meanwhile, the monitoring result is autonomously notified to the application server when the user number threshold value is exceeded, the monitoring intelligence is improved, the problem that the service capability is not adjusted timely because the application server requests for the user number when congestion occurs can be avoided, the timeliness of adjusting the service capability is improved, and further the user experience is improved.
Drawings
FIG. 1 is a diagram illustrating a capability openness architecture according to an embodiment of the present invention;
fig. 2 is a schematic flow chart of a first user number monitoring method according to an embodiment of the present invention;
fig. 3 is a schematic flow chart of a second user quantity monitoring method according to an embodiment of the present invention;
fig. 4 is a schematic flow chart of a third user number monitoring method according to an embodiment of the present invention;
fig. 5 is a schematic flow chart of a fourth user number monitoring method according to an embodiment of the present invention
Fig. 6 is a schematic structural diagram of a monitoring entity according to an embodiment of the present invention;
fig. 7 is a schematic structural diagram of an access entity according to an embodiment of the present invention;
fig. 8 is a schematic structural diagram of an application server according to an embodiment of the present invention;
fig. 9 is a schematic structural diagram of a network element entity according to an embodiment of the present invention;
fig. 10 is a schematic flow chart of a fifth user quantity monitoring method according to an embodiment of the present invention;
fig. 11 is a schematic diagram of connections between network element entities according to an embodiment of the present invention;
fig. 12 is a flowchart illustrating a sixth method for monitoring a number of users according to an embodiment of the present invention;
fig. 13 is a schematic diagram of a connection between network element entities according to another embodiment of the present invention.
Detailed Description
The technical solution of the present invention is further described in detail with reference to the drawings and the specific embodiments of the specification.
As shown in fig. 1, the present embodiment provides a user number monitoring method, which is applied to a monitoring entity, and includes:
step S110: receiving a monitoring request carrying monitoring parameters; wherein the monitoring parameters include at least: a user number threshold;
step S120: monitoring the number of users in a designated area;
step S130: and if the current user number exceeds the user number threshold value, sending a monitoring result to the application server.
In this embodiment, the monitoring entity may be a network element entity capable of counting the number of user equipments in a specified area, and for example, the monitoring entity may be an MME, a user plane gateway, or a control plane gateway, to which each base station in the specified area is connected.
In this embodiment, the monitoring entity receives the monitoring request, where the monitoring request may be sent directly by the application server, or the application server provides the original data of the monitoring request, and performs security filtering on the original data of the monitoring request through SCEF or the like, and forwards the monitoring request after parsing some specific data. In summary, the monitoring request triggers the monitoring entity to monitor the user data of the specified area. The User number here may be understood as the number of User Equipments (UEs) in a specified area, and may also be the number of User accounts. In some cases, there may be a case where one mobile phone uses a plurality of user accounts. For example, a dual-card dual-standby mobile phone, it is possible to connect to the network using two phone numbers at the same time. The mobile phone number is one of the user accounts. In this embodiment, the number of users may also be: the number of connections to the network corresponding to the specified area with the user equipment.
In step S120, the number of users in a designated area is monitored, and the designated area may be a geographical area that can be monitored by the monitoring entity, or a sub-area in the geographical area that can be monitored.
If the number of users in the designated area exceeds the user number threshold, the monitoring result is transmitted to the application server in step S130. The monitoring result at least prompts the application server that the number of the users currently exceeds the number of the users specified by the application server, so that the application server can make a decision to perform capacity expansion operation or not conveniently. In some embodiments, the monitoring result may further include: the number of users in the specified area is monitored at present, and the application server can know the number of users specifically included in the specified area at present conveniently.
In still other embodiments, the monitoring may further include: the monitoring entity predicts the change trend of the user number according to historical monitoring data, and the application server conveniently determines whether capacity adjustment and other operations are needed or not by combining the user number or the prompt message exceeding the user number threshold. For example, when the current time is 9 pm, the current number of users exceeds the user number threshold, but according to the conventional rule, the number of users decreases after 9 pm, and if 9 pm passes, the number of users decreases, and if the application server receives such a monitoring result, even if the result that the number of users exceeds the user number threshold occurs, a decision that relevant parameters of service capacity are not adjusted can be made according to a change trend, thereby assisting the application server in making a more intelligent decision.
In this embodiment, on one hand, the monitoring entity may automatically report the monitoring result without requiring the application server to request for reporting once. One user number threshold value can actively inform the monitoring result of the user monitoring entity for a plurality of times.
On the other hand, the threshold of the number of users is automatically set by the application server, and normally, the threshold of the number of users indicates that the application server can at least meet the requirement of the service with the number of users in the designated area. The service providing capability corresponding to the user number threshold is prepared in advance by the application server, if the user number does not exceed the user number threshold, the negative influence on the service obtaining experience of the user is small, and the satisfaction degree of the service experience of the user still keeps high. In some embodiments, the service capacity of the application server required by the user number threshold may be slightly lower than the service capacity of the application server, such that the application server has sufficient response time to adjust its service capacity once the monitoring result is exceeded. The service capabilities may include: the maximum number of users allowed to access, the maximum service bandwidth provided, etc.
Therefore, obviously, compared with the method that the application server requests the number of the users once, the monitoring entity notifies the number of the users once, the intelligence of the user number monitoring method provided by the embodiment is greatly improved, the monitoring operation of the number of the users is simplified, the adjustment delay of the application server for automatically adjusting the capacity and other service capabilities according to the number of the users is reduced, and more satisfactory service can be provided for the users.
Optionally, the number of the user number threshold is N, which is respectively a 1 st user number threshold to an nth user number threshold, where the nth user number threshold is smaller than an N +1 st user number threshold; n is less than N, N is an integer not less than 2, and N is a positive integer. That is, the 1 st user number threshold may be a minimum user number threshold, and the nth user number threshold may be a maximum user number threshold. The monitoring parameters further comprise mapping rules; wherein the mapping rule comprises: and exceeding the corresponding relation between the threshold identification and the user number threshold.
The step S130 includes:
if the current user number exceeds the user number threshold, sending a monitoring result to an application server, including:
if the current user number exceeds an mth user number threshold, determining a monitoring result according to the mapping rule, wherein the monitoring result comprises: an exceeding threshold identification corresponding to the mth user number threshold;
and sending the monitoring result to the application server according to a reporting rule.
Firstly, the number of user thresholds is set to be more, and the corresponding relationship between the number of user thresholds of different levels and the identifier exceeding the threshold is determined through a mapping rule, in this embodiment, the monitoring result includes: and the exceeding threshold mark corresponds to the user number threshold value exceeding the current user number. In this way, after receiving the monitoring result, the application server knows which user number threshold the current user number exceeds. In addition, in this embodiment, the exceeding threshold flag carried by the monitoring result, rather than the entire current number of users, may be indicated by a predetermined number of bits, so that transmission of data amount is reduced. Particularly, when the monitoring entity performs information interaction with the application server through the control plane instruction, the bit length of the control plane instruction is reduced, on one hand, the monitoring entity can be well compatible with the prior art so as to be simple, convenient and real-time, and on the other hand, the bandwidth occupied by a control plane channel is also reduced.
Secondly, the monitoring of the parameters in this embodiment may further include: reporting a rule; several optional reporting rules are provided below;
reporting a rule I:
the step S130 may include:
and if the current user number exceeds the 1 st user number threshold value, generating the monitoring result and sending the monitoring result to user equipment.
Reporting a rule II:
if the current user number exceeds the m1 user number threshold value and the user number when the monitoring result is sent to the application server exceeds the m2 user number threshold value, if the m2 user number threshold value is the same as the m1 user number threshold value, the report is not carried out at this time; and if the m1 th user number threshold is different from the m2 th user number threshold, at least sending an exceeding threshold mark corresponding to the m1 th user number threshold to the application server.
If the number of the users exceeding the user number threshold twice in the adjacent time corresponds to the user number threshold of the same level, the fact that the number of the users in the current designated area does not change greatly is shown, and the users are notified when the number of the users exceeds the user number threshold for the last time or for the last time, the application server does not need to be notified, and the inexpedient information interaction is reduced.
Reporting a rule III:
the reporting rule includes a reporting period.
Reporting the monitoring result as long as the current user number exceeds the minimum user number threshold and the current time is the reporting time point corresponding to the reporting period, regardless of the user number threshold exceeded in the previous reporting; if the current time does not reach the reporting time point, and the number of users exceeding the current time is the same as the number of users exceeding the previous time, the reporting is not required.
Reporting a rule four:
if the number of the first-time users exceeds a user number threshold, the monitoring entity sends the monitoring result to an application server;
and if the number of the users monitored next time exceeds the user number threshold value and the exceeded maximum user number threshold value is still the user data threshold value exceeded last time, determining whether to send the monitoring result to the application server according to whether the number of the users monitored currently is within the variation interval of the user number threshold value. Specifically, if the current number of users is within the change interval, the monitoring result is not reported; the change interval is preset to shield the problem of frequent reporting caused by frequent jumping of the user number around the user number threshold. And if the current user number is within a change interval corresponding to the user number threshold value, reporting a monitoring result.
In some embodiments, the monitoring parameters further comprise: a location monitoring type.
As shown in fig. 3, the step S120 may include:
step S121: tracking the position parameters of the user equipment according to the position monitoring type;
step S122: and counting the number of users in the designated area according to the position parameters.
In this embodiment, the monitoring parameter further carries a location monitoring type. For example, the current location of the UE is monitored in real time, or the current location of the UE is monitored periodically, or the current location of the UE is monitored when a certain trigger condition is met. The location monitoring types are classified into at least three types. The implementation of monitoring the current location of the UE may include: the UE carries out positioning by itself, and sends a positioning result to the base station in real time and reports the positioning result to a monitoring entity and the like by the base station; or, the base station monitors the position of the UE in real time and reports the monitored position to the UE in real time. The current location of the UE is periodically monitored, and although the UE has mobility, most UEs do not have a large moving range in a short time, so the current location of the UE can be updated once in a long period, such as 10 minutes or 5 minutes in this embodiment.
Due to its mobility, the UE may switch between different cells, thereby causing a Tracking Area Update (TAU) event of the UE, and the base station may acquire location information of the UE when executing TAU. In this embodiment, the monitoring of the location of the UE meeting a certain trigger condition may include: and when the UE is detected to execute the TAU, acquiring the position information of the UE.
Therefore, in some embodiments, the step S121 may include:
when the position monitoring type is a real-time monitoring type, tracking the current position of the user equipment in real time; in this embodiment, the real-time tracking may be continuously acquiring the current location information of the user equipment.
The step 122 may include: and counting the number of users in the designated area according to the current position of the user equipment.
In this way, the real-time data of the number of users in the specified area is actually counted, and the requirement of the application server with strong real-time requirement can be met.
In still other embodiments, the step S121 may include: when the location monitoring type is a tracking area updating type, determining an updating location according to the latest TAU of the user equipment; the step S122 may include: and counting the number of users in the designated area according to the updated position. In this way, the load caused by the location tracking of the network side equipment to the UE can be reduced.
Optionally, the step S130 may include:
if the current user number exceeds the user number threshold value and the monitoring parameter comprises monitoring time, sending the monitoring result to the application server within the monitoring time;
or,
and if the current user number exceeds the user number threshold and the monitoring parameter does not include the monitoring time, continuously sending the monitoring result to the application server according to a preset mode until a sending end event is detected.
In this embodiment, the monitoring time is set, and if the number of users exceeds the user number threshold, the monitoring entity reports the monitoring result within the monitoring time, and knows that the monitoring time is over.
In other embodiments, the monitoring parameter may not set the monitoring time, and the monitoring entity may continue to send the monitoring result until a new monitoring request is received, or a new user number threshold is received, or an indication that the device such as the application server instructs to stop sending is received, or an end-of-sending event such as an indication that the application server indicates that a confirmation of the monitoring result is received.
Optionally, the monitoring entity is a mobility management entity MME or a general packet radio service support node SGSN.
The step S130 may include:
and the MME or the SGSN sends the monitoring result to the application server through access. The Access entity can be SCEF or Application Access Control entity (ACC)
In still other embodiments, the step S130 may include: the MME or the SGSN sends the monitoring result to a policy and charging rule entity (PCRF); and the monitoring result is used for forwarding the PCRF to the application server through the SCEF. At this time, the PCRF reports the monitoring result to the SCEF and other access entities, and the SCEF and other access entities forward to the application server.
As shown in fig. 4, the present embodiment provides a method for monitoring a number of users, which is applied to an access entity such as a capability openness entity SCEF, and includes:
step S210: receiving a monitoring request which is sent by an application server and carries monitoring parameters, wherein the monitoring parameters comprise: a user number threshold;
step S220: forwarding the monitoring request to a monitoring entity;
step S230: receiving a monitoring result sent by the monitoring entity when the monitoring entity detects that the number of users in the designated area exceeds the user number threshold;
step S240: and sending the monitoring result to the application server.
In this embodiment, the access entity such as the SCEF may serve as a connection entity between network elements of a trust domain and other domains, receive the monitoring request from the application server, and forward the monitoring request to a corresponding monitoring entity, for example, forward a network element such as an MME or an SGSN that can monitor the number of users.
Optionally, the monitoring parameters further include: a geographic location parameter for the specified area;
the method further comprises the following steps:
determining a network parameter corresponding to the geographic position parameter according to the coverage condition of the network on the geographic area;
the forwarding the monitoring request to the monitoring entity includes:
and sending the monitoring request to the monitoring entity which can monitor the designated area according to the network parameters.
The monitoring request sent by the application server may carry monitoring parameters, where the monitoring parameters may also carry geographic location parameters of a specified area to be monitored, such as longitude and latitude, or various information for identifying a geographic location, such as an identifier of an administrative area, such as a town, province, or town, in addition to the user number threshold. The SCEF corresponds the geographical position of the designated area to the network according to the geographical position parameter, thereby determining the network parameter in the network coverage area, and sends the monitoring request to the corresponding monitoring entity according to the network parameter.
Specifically, the determining the network area corresponding to the designated area according to the geographic location parameter may include:
and determining network parameters such as a cell identifier of a cell located in the specified Area, a base station identifier of a base station located in the specified Area, a Routing Area Identifier (RAI), a Tracking Area Identifier (TAI) and the like according to the coverage condition of the network to the geographic Area.
Based on these network parameters, it may be determined that a monitoring entity may monitor the specified area, and then the SCEF sends the monitoring request to the corresponding monitoring entity.
In a specific implementation, the conversion from the geographic location parameter to the network parameter is not limited to be processed by the SEEF, but may also be performed by other network elements, for example, a PCRF of a core network, but since the monitoring request must pass through the SCEF, the SCEF performs the conversion of the network parameter in a forward manner, which may reduce the forwarding of the monitoring request between different network elements, thereby increasing the processing speed.
As shown in fig. 5, this embodiment provides a user number monitoring method, where an application server includes:
step S310: sending a monitoring request to an access entity, wherein the monitoring request carries monitoring parameters, and the monitoring parameters comprise: a user number threshold;
step S320: and receiving a monitoring result sent by the monitoring entity when the number of users in the designated area exceeds the user number threshold.
In this embodiment, the AS does not simply send a request for acquiring the number of users, but sends a request carrying at least a threshold of the number of users, and after receiving the monitoring request, the monitoring entity actively notifies the application server when the number of users in the designated area exceeds the threshold of the number of users, so that the operation of the application server for acquiring the monitoring results such AS the number of users is simplified, and the response delay of the application server for adjusting the service capabilities such AS capacity expansion according to the number of users can be reduced.
Optionally, the monitoring parameters further include at least one of:
a mapping rule, wherein the mapping rule comprises: the mapping relation between the user number threshold and the mark exceeding the threshold;
reporting rules, wherein the reporting rules are used for the monitoring entity to send monitoring results;
a geographic location parameter for the designated area;
the time is monitored.
The above description and detailed usage of the monitoring parameters can be referred to the foregoing embodiments, and will not be repeated here.
As shown in fig. 6, this embodiment provides a network element entity, where the network element entity is a monitoring entity, and the monitoring entity may be a communication node in a network, such as an MME or an SGSN. As shown in fig. 6, the monitoring entity may include:
a first receiving unit 110, configured to receive a monitoring request carrying monitoring parameters; wherein the monitoring parameters include at least: a user number threshold;
a monitoring unit 120, configured to monitor the number of users in a specified area;
a first sending unit 130, configured to send a monitoring result to the application server if the current user number exceeds the user number threshold.
Here, the first receiving unit 110 and the first sending unit 130 may each correspond to a communication interface, for example, an optical cable interface or an electrical cable interface, and may exchange information with other network elements.
The monitoring unit 120 may correspond to a processor, and the processor may be configured to determine whether the current number of users exceeds a user number threshold. Therefore, when the current number of users in the designated area exceeds the user number threshold, the first sending unit 130 is triggered to send the monitoring result to the application server.
Optionally, the number of the user number threshold is N, which is respectively a 1 st user number threshold to an nth user number threshold, where the nth user number threshold is smaller than an N +1 st user number threshold; n is less than N, N is an integer not less than 2, and N is a positive integer;
the monitoring parameters further include: mapping rules and reporting rules; wherein the mapping rule comprises: exceeding the corresponding relation between the threshold identification and the user number threshold;
the first sending unit 130 is specifically configured to determine a monitoring result according to the mapping rule if the current user number exceeds an mth user number threshold, where the monitoring result includes: an exceeding threshold identification corresponding to the mth user number threshold; and sending the monitoring result to the application server according to a reporting rule.
Optionally, the monitoring parameters further include: a location monitoring type;
the monitoring unit 120 is specifically configured to track a location parameter of the user equipment according to the location monitoring type; and counting the number of users in the designated area according to the position parameters.
Optionally, the monitoring unit 120 is specifically configured to track, in real time, a current location of the user equipment when the location monitoring type is a real-time monitoring type; and counting the number of users in the designated area according to the current position of the user equipment.
Further, the monitoring unit 120 is specifically configured to determine, when the location monitoring type is a tracking area update type, an update location according to a latest tracking area update of the ue; and counting the number of users in the designated area according to the updated position.
Optionally, the first sending unit 130 is specifically configured to send the monitoring result to the application server within the monitoring time if the current number of users exceeds the user number threshold and the monitoring parameter includes the monitoring time; or, if the current number of users exceeds the user number threshold and the monitoring parameter does not include the monitoring time, the monitoring result is continuously sent to the application server according to a preset mode until a sending end event is detected.
Optionally, the monitoring entity is a mobility management entity MME or a general packet radio service support node SGSN;
the first sending unit 130 sends the monitoring result to the application server through an access entity such as a capability openness entity SCEF; or sending the monitoring result to a policy and charging rule entity PCRF; and the monitoring result is used for forwarding the PCRF to the application server through the SCEF.
As shown in fig. 7, this embodiment provides a network element entity, where the network element entity is an access entity, and the access entity may be an SCEF or an ACC, and includes:
a second receiving unit 210, configured to receive a monitoring request with monitoring parameters sent by an application server, where the monitoring parameters include: a user number threshold;
a second sending unit 220, configured to forward the monitoring request to a monitoring entity;
the second receiving unit 210 is further configured to receive a monitoring result sent by the monitoring entity when detecting that the number of users in the designated area exceeds the user number threshold;
the second sending unit 220 is further configured to send the monitoring result to the application server.
The second receiving unit 210 and the second sending unit 220 may both correspond to the communication interface of the SCEF.
Optionally, the monitoring parameters further include: a geographic location parameter for the specified area;
the network element entity further comprises:
the determining unit can be fixed on the processor and used for determining a network parameter corresponding to the geographic position parameter according to the coverage condition of the network on the geographic area;
the second sending unit 220 is specifically configured to send the monitoring request to the monitoring entity that can monitor the specified area according to the network parameter.
As shown in fig. 8, this embodiment provides a network element entity, where the network element entity is an application server, and the network element entity includes:
a third sending unit 310, configured to send a monitoring request to an access entity, where the monitoring request carries monitoring parameters, and the monitoring parameters include: a user number threshold;
a third receiving unit 320, configured to receive a monitoring result sent by the monitoring entity when the number of users in the designated area exceeds the user number threshold.
The third sending unit 310 and the third receiving unit 320 may both correspond to a communication interface of an application server, and may be configured to communicate with the SCEF, so as to request information interaction, such as monitoring of the number of users in a specified area.
The monitoring parameters further include at least one of:
a mapping rule, wherein the mapping rule comprises: the mapping relation between the user number threshold and the mark exceeding the threshold;
reporting rules, wherein the reporting rules are used for the monitoring entity to send monitoring results;
a geographic location parameter for the designated area;
the time is monitored.
As shown in fig. 9, this embodiment further provides a network element entity, including: a transceiver 430, a memory 410, a processor 420, and a computer program 440 stored on the memory 420 and executed by the processor;
the processor 420 is respectively connected to the transceiver 430 and the memory 410, and is configured to implement one or more of the methods for monitoring the number of users applied to the monitoring entity, the SCEF, or the application server by executing the computer program 440.
In this embodiment, the transceiver 430 may correspond to a wireless communication interface such as a transceiver antenna, and may also correspond to a wired interface such as a cable interface or an optical cable interface, where the transceiver antenna may be used for information interaction between a base station and a UE.
The memory 410 may include: various types of storage media may be used for data storage. In this embodiment, the memory 410 includes a storage medium, which is at least partially a non-volatile storage medium, and can be used for storing the computer program 440.
The processor 420 may include: a central processor, microprocessor, digital signal processor, application specific integrated circuit or programmable array, or the like, may be used for cell signal quality determination by execution of the computer program 440.
In this embodiment, the processor 420 may be connected to the transceiver 430 and the memory 410 via an intra-device bus such as an integrated circuit bus.
The present embodiment further provides a network element entity, including: a transceiver, a memory, and a processor;
the processor is connected with the transceiver and the memory respectively, and is used for implementing one or more of the user number monitoring methods applied to the monitoring entity, the SCEF or the application server by executing a computer program.
An embodiment of the present invention further provides a computer storage medium, where a computer program is stored, and after the computer program is executed by a processor, the method for monitoring a user number provided in one or more of the foregoing technical solutions is executed, for example, any one of the methods for monitoring a user number applied to a monitoring entity, an SCEF, or an application server is implemented.
The computer storage medium provided by the embodiment of the invention comprises: a mobile storage device, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes. Alternatively, the computer storage medium may be a non-transitory storage medium. The non-transitory storage medium herein may also be referred to as a non-volatile storage medium.
Several examples are provided below in connection with any of the embodiments described above:
example 1:
this example presents a method of monitoring the number of users.
In this example, the application server configures a user number threshold event, and the monitoring entity automatically reports to the application server after finding that the number of users in the specified area exceeds the user number threshold. The method comprises the steps that an application server sets a user number threshold reported by the number of users in the area, the user number threshold is sent to a monitoring entity in a network through a reporting request, and once the monitoring entity finds that the number of users in the designated area exceeds the user number threshold, the monitoring entity actively notifies the application server at any time.
The threshold reporting request at least comprises: a user number threshold value, information such as exceeding threshold identification and mapping rules, region and position monitoring types, monitoring time intervals and the like;
the user number threshold and the exceeding threshold mark can be set with step values according to service needs and are in one-to-one correspondence according to mapping rules (for example, the threshold value can be 1 ten thousand, 5 ten thousand, 10 ten thousand, etc., and the corresponding non/exceeding threshold mark is 0/1, 2, 3, etc.)
In order to avoid ping-pong effect of signaling reporting, the user number threshold can also be an upper threshold and a lower threshold.
The application server only needs to issue a request once to configure the event report on the monitoring entity, and once the monitoring entity finds that the report time interval exceeds the threshold value, the report is reported to the application server until the monitoring time is over. If the monitoring time interval does not exist, the default monitoring entity needs to report all the time until a new user number threshold value request is issued.
The monitoring entity in this example needs to have the capability of real-time monitoring and real-time reporting, and the entity includes, but is not limited to, an MME/SGSN, a PCRF, and the like.
The MME/SGSN is used AS a monitoring entity, and the MME actively informs the monitoring result to the application server through the transmission path of the MME- > SCEF- > AS.
MME/SGSN is used AS a monitoring entity, MME sends the monitoring result to PCRF and actively informs the application server through the transmission path of MME- > SAE-GW- > PCRF- > AS.
Example 2:
in this example, the MME is taken as a monitoring entity, and the SCEF is automatically reported as an example, so as to illustrate the user number monitoring method. The method comprises the steps that an application server sends a real-time monitoring user number threshold event request to an MME, the MME specifies the number of regional users in real time, and once the number of users exceeds a user number threshold, the MME notifies the application server in real time through an MME-SCEF capacity open interface.
As shown in fig. 10, the user number monitoring method provided by this example includes:
step S1: the AS sends a user number threshold event request message to a capability openness entity (SCEF), and the user number threshold event request message carries indications of a user number threshold, an exceeding threshold identifier, a mapping rule, a geographical location area, a location type (such AS the current location of the UE or the location of the latest confirmation), a monitoring time interval and the like.
Step S2: the SCEF (or an access entity such as AAC) performs network location mapping, and configures a request event to a related MME/SGSN, which may specifically include: mapping the geographic position of the designated area to parameters such as a cell, an eNB, an RAI or a TAI, judging the MME/SGSN where the area is located, and reporting an event to the related MME/SGSN configuration request user number threshold.
Step S3: the MME/SGSN monitors in real time, calculates the number of users in an area, and maps to an identifier exceeding a threshold according to a mapping rule once the number of users exceeds the threshold, for example, the method may specifically include: and monitoring and calculating the number of regional users in real time according to the configuration information of the reported event of the number of regional users, and mapping the number of regional users to be an exceeding threshold identification according to a mapping rule once the number of regional users exceeds a user threshold.
Step S4: and the MME/SGSN reports the regional user number reporting event to the SCEF/AAC, and the reported information at least comprises the mark exceeding the threshold value.
Step S5: and the SCEF/AAC reports the received regional user number threshold value reporting event to the AS.
In fig. 11, interfaces between network elements are shown, AS reports a user number threshold event request message to SCEF/AAC through an interface ①, where the user number threshold event request message is one of the foregoing monitoring requests, SCEF/AAC sends a configuration request event to MME ③ or SAE-GW ④ through an interface ②, where SAE-GW is one of the foregoing monitoring entities.
Example three:
in this example, the MME specifies the number of regional users in real time, and after exceeding the user number threshold, transmits threshold related information to the PCRF, and the PCRF notifies the application server in real time through an interface between the PCRF and the SCEF.
The application server sends a real-time monitoring user number threshold event request to the PCRF, the MME specifies the regional user number in real time, once the user number threshold is exceeded, the relevant information of the threshold is transmitted to the PCRF, and the PCRF notifies the application server in real time through a PCRF-SCEF interface.
As shown in fig. 12, the user number monitoring method provided by this example includes:
step S11: the AS sends a user number threshold event request message to a capability openness entity (SCEF), carries the user number threshold, and indicates the exceeding threshold identifier, the mapping rule, the geographic location area, the location type (such AS the current location or the location confirmed at the last time), the monitoring time interval and the like.
Step S12: performing network location mapping, and configuring a request event to a relevant PCRF, which may specifically include: the SCEF/AAC mapping geographic position is parameters such as a cell/eNB/RAI/TAI, the MME/SGSN where the area is located and the related PCRF are judged, and a request user number threshold reporting event is configured to the related PCRF.
Step S13: the PCRF transmits the relevant parameters of the reported user number threshold event request to the MME/SGSN;
step S14: and the MME/SGSN monitors in real time, calculates the number of users in the area, and maps the identifier exceeding the threshold value according to the mapping rule once the number of users exceeds the threshold value. The step S14 may specifically include: and the MME or the SGSN monitors and calculates the number of regional users in real time according to the configuration information of the user number threshold reporting event, and once the number exceeds the threshold, the MME or the SGSN is mapped into an exceeding threshold identifier according to a mapping rule.
Step S15: and the MME/SGSN responds to the user number threshold value reporting event request of the PCRF, executes the user number and threshold value reporting event and reports a monitoring result to the PCRF, wherein the monitoring result is one of reported information. The reporting information at least comprises an identification exceeding a threshold value.
Step S16: the PCRF reports the user number threshold reporting event to the SCEF, and the SCEF/AAC reports the received regional user number reporting event to the AS.
In fig. 13, interfaces between network elements are shown, an AS reports a user number threshold event request message to a SCEF/AAC through an interface ①, where the user number threshold event request message is one of the foregoing monitoring requests, the SCEF/AAC transfers the user number threshold event to a PCRF through an interface ⑧, the PCRF performs information interaction with an SAE-GW through interfaces ③ and ⑦, and the MME performs information interaction with the SAE-GW through interfaces ⑤ and ⑥ before the MME and the SAE-GW.
In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. The above-described device embodiments are merely illustrative, for example, the division of the unit is only a logical functional division, and there may be other division ways in actual implementation, such as: multiple units or components may be combined, or may be integrated into another system, or some features may be omitted, or not implemented. In addition, the coupling, direct coupling or communication connection between the components shown or discussed may be through some interfaces, and the indirect coupling or communication connection between the devices or units may be electrical, mechanical or other forms.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed on a plurality of network units; some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, all the functional units in the embodiments of the present invention may be integrated into one processing module, or each unit may be separately used as one unit, or two or more units may be integrated into one unit; the integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional unit.
Those of ordinary skill in the art will understand that: all or part of the steps for implementing the method embodiments may be implemented by hardware related to program instructions, and the program may be stored in a computer readable storage medium, and when executed, the program performs the steps including the method embodiments; and the aforementioned storage medium includes: a mobile storage device, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the appended claims.
Claims (17)
1. A user number monitoring method is applied to a monitoring entity, and comprises the following steps:
receiving a monitoring request carrying monitoring parameters; wherein the monitoring parameters include at least: a user number threshold;
monitoring the number of users in a designated area;
and if the current user number exceeds the user number threshold value, sending a monitoring result to the application server.
2. The method of claim 1,
the number of the user number threshold values is N, and the number of the user number threshold values is from 1 st to Nth, wherein the nth user number threshold value is smaller than the (N + 1) th user number threshold value; n is less than N, N is an integer not less than 2, and N is a positive integer;
the monitoring parameters further include: mapping rules and reporting rules; wherein the mapping rule comprises: exceeding the corresponding relation between the threshold identification and the user number threshold;
if the current user number exceeds the user number threshold, sending a monitoring result to an application server, including:
if the current user number exceeds an mth user number threshold, determining a monitoring result according to the mapping rule, wherein the monitoring result comprises: an exceeding threshold identification corresponding to the mth user number threshold;
and sending the monitoring result to the application server according to a reporting rule.
3. The method according to claim 1 or 2,
the monitoring parameters further include: a location monitoring type;
the monitoring the number of users in the designated area comprises:
tracking the position parameters of the user equipment according to the position monitoring type;
and counting the number of users in the designated area according to the position parameters.
4. The method of claim 3,
the tracking the location parameter of the user equipment according to the location monitoring type includes:
when the position monitoring type is a real-time monitoring type, tracking the current position of the user equipment in real time;
the counting the number of users in the designated area according to the position parameters includes:
and counting the number of users in the designated area according to the current position of the user equipment.
5. The method of claim 3,
the tracking the location parameter of the user equipment according to the location monitoring type includes:
when the position monitoring type is a tracking area updating type, determining an updating position according to the latest tracking area updating of the user equipment;
the counting the number of users in the designated area according to the position parameters includes:
and counting the number of users in the designated area according to the updated position.
6. The method according to claim 1 or 2,
if the current user number exceeds the user number threshold, sending a monitoring result to an application server, including:
if the current user number exceeds the user number threshold value and the monitoring parameter comprises monitoring time, sending the monitoring result to the application server within the monitoring time;
or,
and if the current user number exceeds the user number threshold and the monitoring parameter does not include the monitoring time, continuously sending the monitoring result to the application server according to a preset mode until a sending end event is detected.
7. The method according to claim 1 or 2,
the monitoring entity is a mobile management entity MME or a general packet radio service support node SGSN;
if the current user number exceeds the user number threshold, sending a monitoring result to an application server, including:
the MME or the SGSN sends the monitoring result to the application server through an access entity;
or,
the MME or the SGSN sends the monitoring result to a policy and charging rule entity (PCRF); and the monitoring result is used for forwarding the PCRF to the application server through the access entity.
8. A user number monitoring method is applied to an access entity, and comprises the following steps:
receiving a monitoring request which is sent by an application server and carries monitoring parameters, wherein the monitoring parameters comprise: a user number threshold;
forwarding the monitoring request to a monitoring entity;
receiving a monitoring result sent by the monitoring entity when the monitoring entity detects that the number of users in the designated area exceeds the user number threshold;
and sending the monitoring result to the application server.
9. The method of claim 8,
the monitoring parameters further include: a geographic location parameter for the specified area;
the method further comprises the following steps:
determining a network parameter corresponding to the geographic position parameter according to the coverage condition of the network on the geographic area;
the forwarding the monitoring request to the monitoring entity includes:
and sending the monitoring request to the monitoring entity which can monitor the designated area according to the network parameters.
10. A user number monitoring method is characterized in that an application server comprises the following steps:
sending a monitoring request to an access entity, wherein the monitoring request carries monitoring parameters, and the monitoring parameters comprise: a user number threshold;
and receiving a monitoring result sent by the monitoring entity when the number of users in the designated area exceeds the user number threshold.
11. The method of claim 10, wherein the monitoring parameters further comprise at least one of:
a mapping rule, wherein the mapping rule comprises: the mapping relation between the user number threshold and the mark exceeding the threshold;
reporting rules, wherein the reporting rules are used for the monitoring entity to send monitoring results;
a geographic location parameter for the designated area;
the time is monitored.
12. A network element entity, wherein the network element entity is a monitoring entity, comprising:
the first receiving unit is used for receiving a monitoring request carrying monitoring parameters; wherein the monitoring parameters include at least: a user number threshold;
the monitoring unit is used for monitoring the number of users in the designated area;
and the first sending unit is used for sending a monitoring result to the application server if the current user number exceeds the user number threshold.
13. A network element entity, wherein the network element entity is an access entity, comprising:
a second receiving unit, configured to receive a monitoring request with monitoring parameters sent by an application server, where the monitoring parameters include: a user number threshold;
a second sending unit, configured to forward the monitoring request to a monitoring entity;
the second receiving unit is further configured to receive a monitoring result sent by the monitoring entity when detecting that the number of users in the designated area exceeds the user number threshold;
the second sending unit is further configured to send the monitoring result to the application server.
14. A network element entity, wherein the network element entity is an application server, comprising:
a third sending unit, configured to send a monitoring request to an access entity, where the monitoring request carries monitoring parameters, where the monitoring parameters include: a user number threshold;
and the third receiving unit is used for receiving a monitoring result sent by the monitoring entity when the number of users in the designated area exceeds the user number threshold.
15. A network element entity, comprising: a transceiver, a memory, a processor, and a computer program stored on the memory and executed by the processor;
the processor, which is connected to the transceiver and the memory respectively, is configured to implement the user number monitoring method provided in any one of claims 1 to 11 by executing the computer program.
16. A network element entity, comprising: a transceiver, a memory, and a processor;
the processor is connected to the transceiver and the memory, respectively, and is configured to implement the user number monitoring method provided in any one of claims 1 to 11 by executing a computer program.
17. A computer storage medium storing a computer program; the computer program, when executed, enables a user number monitoring method as provided in any one of claims 1 to 11.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710936232.1A CN109660996B (en) | 2017-10-10 | 2017-10-10 | User number monitoring method, network element entity and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710936232.1A CN109660996B (en) | 2017-10-10 | 2017-10-10 | User number monitoring method, network element entity and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109660996A true CN109660996A (en) | 2019-04-19 |
| CN109660996B CN109660996B (en) | 2022-05-13 |
Family
ID=66109372
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710936232.1A Active CN109660996B (en) | 2017-10-10 | 2017-10-10 | User number monitoring method, network element entity and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109660996B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102833725A (en) * | 2011-06-17 | 2012-12-19 | 中兴通讯股份有限公司 | Central tracking method and system |
| CN104144434A (en) * | 2013-05-09 | 2014-11-12 | 华为技术有限公司 | Method and device for achieving MTC monitoring |
| CN104427476A (en) * | 2013-09-10 | 2015-03-18 | 中兴通讯股份有限公司 | Position information reporting method, cluster service processing method and cluster service processing system |
| CN106937323A (en) * | 2015-12-30 | 2017-07-07 | 华为技术有限公司 | The monitoring method and relevant device of a kind of user terminal quantity |
-
2017
- 2017-10-10 CN CN201710936232.1A patent/CN109660996B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102833725A (en) * | 2011-06-17 | 2012-12-19 | 中兴通讯股份有限公司 | Central tracking method and system |
| CN104144434A (en) * | 2013-05-09 | 2014-11-12 | 华为技术有限公司 | Method and device for achieving MTC monitoring |
| CN104427476A (en) * | 2013-09-10 | 2015-03-18 | 中兴通讯股份有限公司 | Position information reporting method, cluster service processing method and cluster service processing system |
| CN106937323A (en) * | 2015-12-30 | 2017-07-07 | 华为技术有限公司 | The monitoring method and relevant device of a kind of user terminal quantity |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109660996B (en) | 2022-05-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| AU2019251152B2 (en) | Method and device for subscribing to service | |
| CN112188533B (en) | Method and device for reporting network performance | |
| CN102948115B (en) | Methods, systems, and computer readable media for policy charging and rules function (pcrf) node selection | |
| US11075841B2 (en) | Network congestion control method, device, and system | |
| KR101632525B1 (en) | Network-controlled adaptive terminal behavior managing high-network-load scenarios | |
| US20210345237A1 (en) | Communication Method and Communications Apparatus | |
| CN109996216B (en) | Subscription request processing method, network entity and capability opening platform | |
| CN113079541B (en) | Report information sending method, device and system | |
| US20230127601A1 (en) | Dynamic update of path selection policy for user equipment in wireless communication network | |
| US11144962B2 (en) | Method for managing the standby state of a mobile terminal | |
| US11039294B2 (en) | Non-throttling on emergency cell sites in cellular systems | |
| CN113873569A (en) | Radio resource management method, storage medium, and electronic device | |
| CN107078914B (en) | Telecommunications system and method | |
| CN111919501A (en) | Dedicated bearer management | |
| JP6079121B2 (en) | COMMUNICATION SYSTEM, MANAGEMENT DEVICE, BASE STATION, COMMUNICATION DEVICE, AND COMMUNICATION PATH CONTROL METHOD | |
| US11882587B2 (en) | Systems and methods for dynamic event-based resource allocation in a radio access network | |
| CN109660996B (en) | User number monitoring method, network element entity and storage medium | |
| JP7568868B2 (en) | Resource Allocation Status Subscription for Application Related Functions | |
| CN107787590B (en) | Spatially resolved quality of data transmission | |
| WO2011110009A1 (en) | Method and apparatus for location subscription | |
| EP2526710B1 (en) | Method and system for monitoring the performance of a network | |
| CN114040448B (en) | Base station load balancing method, system, device and storage medium | |
| US11395215B2 (en) | Systems and methods for detecting and remediating excessive messaging by wireless telecommunications devices | |
| JP5882821B2 (en) | Discovery information distribution device, mobility management device, and program | |
| CN116827845A (en) | Routing policy configuration method, device, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |