CN108207006B

CN108207006B - Data domain shutdown strategy control method and communication system

Info

Publication number: CN108207006B
Application number: CN201611187666.8A
Authority: CN
Inventors: 史嫄嫄; 黄震宁; 朱琳
Original assignee: China Mobile Communications Group Co Ltd; China Mobile Communications Ltd Research Institute
Current assignee: China Mobile Communications Group Co Ltd; China Mobile Communications Ltd Research Institute
Priority date: 2016-12-20
Filing date: 2016-12-20
Publication date: 2021-07-06
Anticipated expiration: 2036-12-20
Also published as: CN108207006A

Abstract

The embodiment of the invention discloses a data domain shutdown method and a communication system, wherein the method comprises the following steps: the business operation support BOSS generates data domain shutdown information according to the first preset information; the first entity acquires the shutdown information of the data domain; the first entity generates a data domain shutdown strategy according to the data domain shutdown information; the first entity sends the data domain shutdown strategy to a second entity; and the second entity executes a restriction strategy of the first class of service data and a passing strategy of the second class of service data according to the data domain shutdown strategy. In the embodiment, even if the data domain is stopped, the transmission of all the service data in the data domain is not stopped, and the transmission of the second service data is reserved, so that the effective utilization rate of the network and the use satisfaction degree of a user are improved.

Description

Data domain shutdown strategy control method and communication system

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a data domain shutdown policy control method and a communication system.

Background

In an Evolved Packet System (EPS), data domain shutdown is performed, and generally, a Business and Operation Support System (BOSS) acquires a user Business state and issues the user Business state to a network element on a network side, and the network side completes the user data domain shutdown. The existing methods have two kinds:

the first method comprises the following steps: EPS locking; with EPS locking, the user equipment cannot attach to the network, thereby completing the data domain outage.

And the second method comprises the following steps: and replacing the data of the Access Point Name (APN) in the subscription data, wherein the routing node can not be accessed by the user equipment based on the newly replaced APN data, thereby realizing the shutdown of the data domain.

In the two methods, once the data domain is executed to stop, all services of the data domain are forbidden, and some services are services which a user or an operator does not want to stop and are also forbidden; the shutdown of the coarse-grained data domain causes the problems of poor user satisfaction, poor network control effect, low network effective utilization rate and the like.

Disclosure of Invention

In view of the above, embodiments of the present invention are directed to a method for controlling a data domain shutdown policy and a communication system, which at least partially solve the above problems.

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

a first aspect of this embodiment provides a data domain shutdown method, including:

the business operation support system BOSS generates data domain shutdown information according to the first preset information;

the first entity acquires the shutdown information of the data domain;

the first entity generates a data domain shutdown strategy according to the data domain shutdown information;

the first entity sends the data domain shutdown strategy to a second entity;

the second entity executes a restriction strategy of the first type of service data and a passing strategy of the second type of service data according to the data domain shutdown strategy; the first type of service data and the second type of service data are service data of the data domain, and are different types of service data.

Based on the above scheme, the second type of service data includes: based on at least one of voice VoLTE service data of a network protocol multimedia subsystem, call forwarding service data, service data of a Ut interface configured by supplementary service, service data of a 53 port and DNS service data of a domain name system.

Based on the above scheme, the acquiring, by the first entity, the data domain shutdown information includes:

receiving a data domain shutdown instruction from the BOSS indicating a data domain shutdown when there is an interface between the first entity and the BOSS.

Based on the above scheme, the method further comprises:

when the first entity and the BOSS have no interface, the BOSS appoints a message to a Mobile Management Entity (MME) through a Home Subscriber Server (HSS);

the MME entity replaces the APN data of the network entry point in the corresponding user identification signing data with the APN data of the shutdown according to the designated message;

when user equipment corresponding to a user identifier requests attachment, the MME sends APN data in subscription data to the first entity;

the first entity obtaining the data domain shutdown information includes:

and receiving the shutdown APN data sent by the MME.

Based on the above scheme, the data domain shutdown strategy includes: a gating strategy;

the second entity executes a restriction policy of the first class of service data according to the data domain shutdown policy, and the restriction policy comprises:

traffic states enabling the first type of traffic data are omitted based on the gating policy.

Based on the above scheme, the data domain shutdown strategy includes: a rate control strategy;

and setting the transmission rate of the first type of service data to be 0 according to an execution rate control strategy.

Based on the above scheme, the service operation support BOSS generates data domain shutdown information according to first predetermined information, including:

and the BOSS generates the data field shutdown information according to at least one of the use state information, the payment state information and the user shutdown instruction of the first type of service data.

Based on the above scheme, the method further comprises:

the BOSS generates data domain reset information according to second preset information;

the first entity acquires the data domain reset information;

the RCRF entity sends a reset instruction to the second entity according to the data domain reset information;

the second entity enables execution of the restriction policy according to the reset instruction.

A second aspect of an embodiment of the present invention provides a communication system, including:

the business operation support BOSS is used for generating data domain shutdown information according to the first preset information;

the first entity is used for acquiring the data domain shutdown information, generating a data domain shutdown strategy according to the data domain shutdown information and sending the data domain shutdown strategy to the second entity;

the second entity is used for executing a restriction strategy of the first type of service data and a passing strategy of the second type of service data according to the data domain shutdown strategy; the first type of service data and the second type of service data are service data of the data domain, and are different types of service data.

Based on the above scheme, the second type of service data includes: based on at least one of voice VoLTE service data of a network protocol multimedia subsystem, call forwarding service data, service data of a supplementary service configuration Ut port, service data of a 53 port and DNS service data.

Based on the above scheme, the first entity is specifically configured to receive a data domain shutdown instruction indicating data domain shutdown from the BOSS when an interface exists between the first entity and the BOSS.

Based on the scheme, the BOSS is configured to assign a message to a mobility management entity MME through a home subscriber server HSS when there is no interface between the first entity and the BOSS;

the MME entity is used for replacing APN data of a network access point in the subscription data corresponding to the user identification with stop APN data according to the designated message, and sending the APN data in the subscription data to the first entity through the second entity when the user equipment corresponding to the user identification requests to attach;

the first entity is specifically configured to receive the APN stop data sent by the MME.

the second entity is specifically configured to omit a traffic state enabling the first type of service data based on the gating policy.

the second entity is specifically configured to set the transmission rate of the first type of service data to 0 according to an execution rate control policy.

Based on the above scheme, the BOSS is specifically configured to generate the data domain shutdown information according to at least one of the usage state information, the payment state information, and the user shutdown instruction of the first type of service data.

Based on the scheme, the BOSS is further used for generating data field reset information according to second preset information;

the first entity is further configured to acquire the data domain reset information, and send a reset instruction to the second entity according to the data domain reset information;

the second entity is further configured to enable execution of the restriction policy according to the reset instruction.

In the technical scheme provided by the embodiment of the invention, when the data domain is stopped, the transmission of all data in the data domain is not simply prohibited, but the service data is subdivided into the first type of service data and the second type of service data; and executing a restriction strategy on the first type of service data, thereby restricting the transmission of the first type of service data and allowing the transmission of the second type of service data. Therefore, the transmission of the second type of service data is reserved, the requirement that a user is connected to a network by using a mobile communication network can be met, and the effective utilization rate of the network, the intelligence of a communication system and the use satisfaction degree of the user are improved.

Drawings

Fig. 1 is a schematic flowchart of a first data domain shutdown policy control method according to an embodiment of the present invention;

FIG. 2 is a flow chart illustrating a data domain shutdown recovery according to an embodiment of the present invention;

fig. 3 is a schematic structural diagram of a data domain shutdown policy control apparatus according to an embodiment of the present invention;

fig. 4 and fig. 5 are schematic flow charts of a second data domain shutdown strategy control method according to an embodiment of the present invention;

fig. 6 and fig. 7 are schematic flowcharts of a third data domain shutdown policy control method according to an 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 data domain shutdown method, including:

step S110: the business operation support BOSS generates data domain shutdown information according to the first preset information;

step S120: the first entity acquires the shutdown information of the data domain;

step S130: the first entity generates a data domain shutdown strategy according to the data domain shutdown information;

step S140: the first entity sends the data domain shutdown strategy to a second entity;

step S150: the second entity executes a restriction strategy of the first type of service data and a passing strategy of the second type of service data according to the data domain shutdown strategy; the first type of service data and the second type of service data are service data of the data domain, and are different types of service data.

The data domain shutdown method described in this embodiment may be a method applied to each network element on the network side, and may implement subdivision of data domain shutdown, implement prohibition of transmission on part of service data, and reserve transmission on another part of service data.

In this embodiment, the first service data and the second service data are different service data. At least one of the first service data and the second service data may be preset or designated data. When the first service data is the designated data, the service data transmitted in the data domain except the first service data is the second service data; and if the second service data is the designated data, the service data transmitted in the data domain except the second service data is the first service data. In a specific implementation, the service data with less data types may be selected and designated according to the types of the first service data and the second service data. Usually, the clock of the first service data is more than the kind of the second service data, and the second service data may be specified in advance in this embodiment, in order to reduce the amount of stored data in the system.

And after the BOSS generates the data domain shutdown information according to the first preset information, directly or indirectly transmitting the information representing the data domain shutdown to the first entity. The first entity generates a corresponding data domain shutdown policy. The first entity may be a Policy and Charging Rules Function (PCRF) entity or an Online Charging System (OCS), and the corresponding second entity may be a Policy and Charging Enforcement Function (PCEF) entity.

The data domain shutdown policy includes at least the constraint policy; in the present embodiment, the restriction policy is executed only on the first type of traffic data. The restriction policy may also be referred to as a prohibition policy, which is a policy for prohibiting transmission of the first type of service data. And executing a traffic policy for the second type of service data, where the traffic policy is various policies that allow the second type of service data to be transmitted, for example, the policy before the data field is stopped is used to perform traffic control on the second type of service data.

Therefore, by using the method of the embodiment, a cutting process can not be executed when the data domain is stopped, the problem that transmission of all data in the data domain is stopped when the data domain is stopped, so that some non-specific service data can not be transmitted is solved, and the user satisfaction and the effective use of the network are improved.

For example, when a certain mobile phone number is stopped, if the user equipment using the mobile phone number cannot utilize any data transmission in the data domain according to the prior art, however, in some specific cases, the user may need first aid, and if transmission of service data in a part of the data domain is reserved, the user equipment using the mobile phone number may also utilize the reserved service to send distress information.

In some embodiments, the second type of service data includes: based on at least one of voice VoLTE service data of a network protocol multimedia subsystem, call forwarding service data, service data of a Ut interface, service data of a 53 port and DNS service data of a domain name system.

If the second type of service data includes VoLTE service data, the user can still perform VoLTE call even if the system is shut down. If the second service data includes the DNS service data, the user may still send a DNS resolution request even if the system is down. The call transfer data is service data generated by transferring the call originally to the first device to the second device.

Of course, the above is only an example of the second type of service data, and various service data may be divided into the second type of service, for example, various mobile supplementary services. The mobile supplementary service may include a communication collect service. For example, user a is down, but the opposite end of the call of user a is user B; and the current opposite communication terminal is user B, it is obvious that the collect-call service can be one of the second type of services.

There may be a direct connection interface between the first entity and the BOSS, or there may be no direct connection interface, and if the BOSS needs to send information to the first entity, it needs to forward the information through other network elements.

Specifically, in some embodiments, the step S120 may include:

and when an interface exists between the first entity and a business operation support system BOSS, receiving a data domain shutdown instruction indicating data domain shutdown from the BOSS.

Since there is an interface between the BOSS and the PCRF entity, it is obvious that the BOSS can directly issue the data domain shutdown information to the first entity. In this embodiment, the data domain shutdown information may be directly a data domain machine instruction. The data domain shutdown command here may be: the information indicating the shutdown corresponding to the user identifier may include the user identifier and a shutdown instruction.

And after receiving the data domain shutdown instruction, the first entity generates a data domain shutdown strategy of the user identifier. The data domain shutdown policy may include the user identification and control parameters. And sending the data domain shutdown strategy to a second entity. After receiving the data domain shutdown strategy, the second entity knows which user needs to perform data domain shutdown according to the user identifier, and knows how to perform data domain shutdown for the user corresponding to the user identifier according to the control parameters.

In some embodiments, the method further comprises:

when the first entity and the BOSS have no interface, the BOSS appoints a message to a Home Subscriber Server (HSS), and then the HSS appoints a message to a Mobile Management Entity (MME); the specific message here may be an Insert Subscriber Data (ISD) message.

The MME entity replaces APN data of a network access point in the subscription data of the corresponding user identification with shutdown APN data according to the designated message; the stop APN data is APN data correspondingly generated after a certain user identifier is subjected to data domain stop.

When user equipment corresponding to a user identifier requests attachment, the MME sends APN data in subscription data to the first entity; the user equipment needs to use the network, and firstly needs to be attached to the network, the user equipment sends an attachment request; after receiving the attach request, the MME initiates a bearer establishment request and sends the bearer establishment request to the second entity, the second entity extracts user information in the bearer establishment request or sends the user information obtained by the MME querying a subscription database to the first entity, the first entity needs to perform reverse account opening by using user data submitted by the second entity because there is no direct connection interface with the BOSS, and after the account opening, the user information of the user equipment is stored in the network correspondingly, and then can be normally attached. In this embodiment, if the MME finds that the current user is a data domain outage user, the MME submits the outage APN information of the user to the first entity through the second entity. As such, the step S120 may include: and receiving the shutdown APN data sent by the MME and a second entity. Obviously, in this embodiment, the data domain stop information is sent by the MME to the second entity, and the second entity further sends the stop APN data to the first entity, and the first entity receives the stop APN data.

Obviously, the first entity obtains the data domain shutdown information in more than one way, and the above are only two optional examples, and the specific implementation is not limited to the above method. For example, after receiving the APN data sent by the BOSS, or after querying the APN data from the subscription database, the MME actively sends the APN data to the second entity and further to the first entity without waiting for the user equipment to request for attachment. In this embodiment, the MME sends the APN data for shutdown to the first entity through the second entity only after the ue sends the attach request, which, on one hand, is highly compatible with the prior art and does not need an additional configuration instruction to specially send the APN data for shutdown, thereby reducing signaling overhead, and on the other hand, can also prevent that the MME forgets to update the ANP data to the first entity through the second entity if the data domain shutdown is no longer performed, resulting in that the first service cannot be performed under the condition that the data domain is not shutdown.

In some embodiments, the data domain shutdown policy comprises: a gating strategy; i.e. the data domain shutdown strategy generated in said step S130 comprises a gating strategy.

The step S150 may include:

After the flow state of the first type service data is enabled, it is equivalent to that the corresponding user identifier does not have the transmission authority of the first type service data, so that the transmission of the first type service data is inhibited.

In the embodiment, the gating strategy is utilized, and the limitation or prohibition of the sub-service types is simply and conveniently finished by enabling the execution of the operation.

In other embodiments, the data domain shutdown policy comprises: a rate control strategy; here, the data field shutdown policy generated in step S130 includes a rate control policy.

The step S150 may include:

In this embodiment, the first type of service data is not directly disabled, which is equivalent to that the right of the corresponding user identifier for transmitting the first type of service is reserved, but the transmission rate is set to 0, which is equivalent to that one transmission rate in the transmission policy of the first type of service data is modified. If the transmission rate is 0, the network does not allocate transmission resources for the service, and thus data transmission cannot be realized, which is equivalent to prohibiting transmission of the first service data. In this way, the prohibition of the first type of service is realized without largely rewriting the policy information stored in the network.

The above data domain shutdown strategy is only an example, and the specific implementation is not limited to the gating strategy and the rate control strategy, but may also include a transmission bandwidth strategy for setting the transmission bandwidth to 0, and may also include a transmission control strategy for modifying the traffic type. For example, the transmission control policy includes content for making a transmission service field, for example, a service identifier of the first type service data in the transmission control policy may be deleted or invalidated, and transmission of the first type service data may also be limited. It is obvious that it is not limited to the above.

However, in the embodiment, the gating strategy or the rate control strategy is implemented, the modification of the strategy information in the second entity is small, and when the machine is stopped and recovered, the communication of the first type of service data can be recovered simply and conveniently through the modification of individual parameters or the starting of enabling operation, so that the service recovery is simplified.

In some embodiments, the step S110 may include:

The usage status information may include a pre-purchased remaining amount of traffic, e.g., 0 remaining amount of traffic or traffic overdraw, and the data field outage information may be generated. The payment state information can comprise arrearage state information, if the arrearage state information is detected, corresponding user identification arrearage can be considered, and certain service data can be stopped, so that the arrearage is prevented from being further increased. For another example, if the user automatically requests shutdown through the user device or goes to a business hall, the BOSS receives a user shutdown command. These are the first predetermined information that triggers the BOSS to generate the data field shutdown information. And after the BOSS generates the data domain shutdown information, the BOSS directly or indirectly sends the data domain shutdown information to the first entity so as to generate a corresponding data domain shutdown strategy.

As shown in fig. 2, the method further comprises:

step S210: the BOSS generates data domain reset information according to second preset information;

step S220: the first entity acquires the data domain reset information;

step S230: the RCRF entity sends a reset instruction to the second entity according to the data domain reset information;

step S240: the second entity enables execution of the restriction policy according to the reset instruction.

In this embodiment, the BOSS further includes data field recovery information according to the second predetermined information. The second predetermined information here is obviously information opposite to the state characterized by the first predetermined information. The second predetermined information may include information that the remaining traffic is not 0, information that no charge is owed, or a user reset instruction.

In this embodiment, the first entity obtains the data domain reset information, where the data domain reset information may be a reset instruction and is transmitted to the first entity by the BOSS through a direct connection interface with the first entity. APN data, which may be non-stop, may be relayed by the MME to the first entity. And the PCRF directly sends a reset instruction to the second entity, and the second entity executes the reset instruction to enable the execution of the restriction policy. The implementation of the disabling data field shutdown strategy herein includes enabling the flow state of the first type service data, and may further include resetting the transmission rate or transmission bandwidth, and canceling the case where the transmission rate is 0 or the transmission bandwidth is 0, thereby implementing resetting of the first type service. It is obvious that the data domain shutdown and recovery is also a very simple matter in this embodiment.

In short, the data field recovery information is information that the data field is no longer stopped, and may be information indicating to resume transmission of the first type of service data.

As shown in fig. 3, the communication system provided in this embodiment includes:

the business operation support BOSS 110 is used for generating data domain shutdown information according to the first preset information;

the first entity 120 is configured to obtain the data domain shutdown information, generate a data domain shutdown policy according to the data domain shutdown information, and send the data domain shutdown policy to the second entity;

the second entity 130 is configured to execute a restriction policy for the first type of service data and a traffic policy for the second type of service data according to the data domain shutdown policy; the first type of service data and the second type of service data are service data of the data domain, and are different types of service data.

The communication system provided in this embodiment at least includes a BOSS 110, a second entity 130 and a first entity 120. The BOSS 110 is a subsystem of the communication system provided in this embodiment, and may be referred to as a BOSS subsystem.

In the embodiment, reference may be made to the prior art for specific network nodes or communication devices corresponding to the BOSS 110, the first entity 120, and the second entity 130, which will not be repeated here.

In this embodiment, the second type of service data includes: at least one of voice over internet protocol (VoLTE) service data, call forwarding service data, Ut interface and/or 53 port service data and Domain Name System (DNS) service data.

The second type of service data is not limited to the above-mentioned type of service data, and may be implemented as any supplementary service data or extended service data, or may be one or more types of existing service data, and in any case, may be preset or designated service data.

In some embodiments, the first entity 120 is specifically configured to receive a data domain shutdown instruction indicating data domain shutdown from the BOSS 110 when there is an interface between the first entity 120 and the BOSS 110.

In this embodiment, if the first entity 120 and the BOSS 110 directly have a direct connection port, the BOSS 110 directly sends the data field shutdown command to the first entity for simplifying transmission.

In other embodiments, the BOSS 110 is configured to assign a message to a mobility management entity MME via an HSS when there is no interface between the first entity and the BOSS;

the MME entity is used for replacing APN data of a network access point in the subscription data corresponding to the user identification with stop APN data according to the designated message, and sending the APN data in the subscription data to the first entity when the user equipment corresponding to the user identification requests to attach;

the first entity 120 is specifically configured to receive the APN stop data sent by the MME.

Generally, the MME is also a commonly used network element in the communication system, and in this embodiment, the MME receives the APN data from the BOSS through the home subscriber server HSS, and sends the corresponding APN data to the first entity through the second entity when the user equipment operating corresponding to the user identifier requests to attach.

In this embodiment, the limiting includes: a gating strategy; here equivalent to the first entity 120 being available to generate the gating strategy. The second entity 130 is specifically configured to omit a traffic state enabling the first type of service data based on the gating policy.

In this embodiment, the second entity 130 may simply disable the first service data transmission through the disabling operation.

In some embodiments, the restriction policy comprises: a rate control strategy; here, the first entity 120 is also used to form the rate control policy, and when the implementation is specific, may also be used to form other policies, such as a bandwidth control policy, that can control the first type of service data restriction transmission of the data field. In this embodiment, the data domain shutdown policy at least includes the restriction policy, and of course, may also include the pass policy; the traffic policy may also be a processing policy previously configured on the second type of traffic data. In this embodiment, the policies for not intercepting the second type of service data may be collectively referred to as a traffic policy.

The second entity 130 is specifically configured to set the transmission rate of the first type of service data to 0 according to an execution rate control policy.

In this embodiment, the second entity 130 simply prohibits the transmission of the first type of service data by setting the transmission rate to 0.

In some further embodiments, the BOSS 110 is specifically configured to generate the data domain shutdown information according to at least one of the usage status information, the payment status information, and a user shutdown instruction of the first type of service data.

Here, the detailed description of the first predetermined information may refer to the foregoing embodiments, and is not repeated again. Of course, the BOSS 110 may also be configured to generate data field recovery information according to second predetermined information;

the first entity 120 is further configured to obtain the data domain reset information, and send a reset instruction to the second entity according to the data domain reset information;

the second entity 130 is further configured to enable execution of the restriction policy according to the machine recovery instruction.

The communication system provided by the embodiment can not be stopped through the data domain, limit the transmission of the first type of service data, and can also be used for transmitting the first type of service data of the simple and convenient multi-phone.

Several specific examples are provided below in connection with the above embodiments:

example one:

in this example, taking VoLTE service data as the second type of service data as an example, a method for controlling data domain shutdown is provided, including:

the PCRF entity is endowed with the control capability of data domain shutdown, and the goals of data domain shutdown and no influence on the VoLTE service are realized:

when the BOSS and the PCRF entity have an interface, the PCRF entity can execute the strategy of data domain shutdown and no influence on the VoLTE service according to a shutdown instruction transmitted by the BOSS.

When the BOSS has no interface with the PCRF entity, the BOSS issues the halt APN information to an access network side through a Home Subscription Server (HSS), for example, in an MME (mobility management entity), and the PCRF entity executes a user reverse account opening and data domain halt strategy and a strategy that VoLTE service is not influenced according to the halt APN information and whether a user exists.

The example can also be used for resetting the data service in real time according to the user resetting information, and the VoLTE service is not influenced.

In this example, the PCRF entity is given the capability of configuring the release of the telecommunication supplementary services, such as the Ut interface service and the 53-port DNS service, so that the telecommunication supplementary services (including but not limited to call forwarding) are not affected when the data domain is down.

By endowing the PCRF entity with the control capability of shutdown and recovery of the data domain, the reconstruction of related entities in the network is reduced to the greatest extent, the cost is reduced, and the flexible realization of shutdown and recovery strategies is also increased.

In this example, the PCRF entity generates a data domain shutdown policy, and provides two data domain shutdown policies, but is not limited to the following:

first, gating strategy:

after receiving shutdown information of a certain user from the BOSS, the PCRF entity executes a gating strategy and sets a field flow-status corresponding to the flow state as disabled; disabled means disabled and is issued to the PCEF entity. When a user resets, the PCRF entity receives reset information of a certain user from the BOSS, executes a gating strategy and sets the flow-status as enabled.

And the second method comprises the following steps: a rate control strategy.

When the PCRF entity receives the outage information from the BOSS for a certain user, the MBR of the data Service is 0 or the APN _ AMBR is 0. When a user resets, the policy control function entity receives reset information of a certain user from the BOSS, and the MBR and APN _ AMBR are reset.

In this example, the PCRF entity is performed based on the APN of the digital domain.

For example, the BOSS informs the PCRF entity of traffic exhaustion information of the subscriber or subscriber data traffic outage policy information. The traffic exhaustion information or user data traffic outage policy information may include, but is not limited to: a user identity usrIdentifier, which may be a communication number used by the UE, for example, usrIdentifier, MSISDN, and a data field shutdown user policy code.

2. And the PCRF entity performs data APN (access point name) shutdown policy control on the data service shutdown user and does not perform shutdown policy control on the VoLTE service APN (such as IMS APN). The policy control function entity puts through the configuration of the outage user data APN, including but not limited to Ut interface traffic and telecommunication supplementary traffic such as 53-port DNS traffic.

3. Because the strategy control functional entity executes the shutdown strategy control on the APN, the network can not be accessed, and the shutdown effect is realized. The strategy control functional entity does not execute shutdown strategy control on the VoLTE service APN, and the VoLTE service is not influenced. Because the scheme releases the communication supplementary service to the data APN, the communication supplementary service such as call forwarding and the like is not influenced.

Example two:

this example provides a specific example if the PCRF entity and the BOSS have a direct interface, in this example, the PCRF entity is abbreviated as PCRF, and the PCEF entity detects the PCEF, which is specifically shown in fig. 4 and 5, and this example provides a data domain shutdown method, including:

step S1: PCRF/SPR configuration data APN shutdown strategy;

step S2: the BOSS informs the traffic exhaustion information of the user or the user data service shutdown information to the PCRF/SPR;

step S3: PCRF/SPR carries out data APN shutdown strategy control on part of data services, and does not carry out shutdown strategy control on IMS APN, wherein the part of data services for carrying out shutdown strategy control is the first type of service data; the service data corresponding to the IMS APN is the second type of service data;

step S4: the PCEF does not execute shutdown strategy control on the IMS APN, the VoLTE service is not influenced, and the shutdown strategy control is executed on other service data, so that the UE cannot obtain network service of other service data, and the effect of absorbing and shutting down is achieved.

Example three:

this example provides a specific example if the PCRF entity and the BOSS do not have a direct connection interface, in this example, the PCRF entity is abbreviated as PCRF, and the PCEF entity detects the PCEF, which is specifically shown in fig. 4 and 5, and this example provides a data domain shutdown method, including:

step S11: the PCRF/SPR configures a direction opening strategy and a shutdown strategy for shutdown ASN;

step S12: the BOSS issues a shutdown instruction to the HSS;

step S13: and the HSS sends an ISD message to the MME, and replaces the original APN data with the subscription data of the halt APN + IMS APN. The stop APN + IMS APN subscription data here corresponds to the stop APN data described above.

Step S14: UE sends out halt user attachment;

step S15: after receiving the halt user attachment, the MME executes APN error correction and sends halt APN data to the PCRF/SPR through a PCEF entity;

step S16: PCRF/SPR judges whether the user information does not exist and the APN data is shut down, if yes, the direction is opened, and a data domain shut down strategy is issued to the PCEF entity;

step S17: and the PCRF entity does not execute the shutdown strategy on the IMS APN, the VoLTE service is not influenced, the APN is shut down to execute the shutdown strategy, and the data domain is shut down.

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

1. A data domain shutdown method, comprising:

the first entity acquires the shutdown information of the data domain;

the first entity sends the data domain shutdown strategy to a second entity;

the second entity executes a restriction strategy of the first type of service data and a passing strategy of the second type of service data according to the data domain shutdown strategy; the first type of service data and the second type of service data are service data of the data domain and are different types of service data;

the first entity is a policy control and charging rule function PCRF entity or an online charging system OCS, and the second entity is a policy control and charging enforcement function PCEF entity.

2. The method of claim 1,

the second type of service data comprises: based on at least one of voice VoLTE service data of a network protocol multimedia subsystem, call forwarding service data, service data of a Ut interface configured by supplementary service, service data of a 53 port and DNS service data of a domain name system.

3. The method according to claim 1 or 2,

the first entity obtaining the data domain shutdown information includes:

4. The method according to claim 1 or 2,

the method further comprises the following steps:

the MME entity replaces APN data of a network access point in the subscription data of the corresponding user identification with shutdown APN data according to the designated message;

the first entity obtaining the data domain shutdown information includes:

and receiving the shutdown APN data sent by the MME.

5. The method according to claim 1 or 2,

the limiting strategy comprises the following steps: a gating strategy;

6. The method according to claim 1 or 2,

the limiting strategy comprises the following steps: a rate control strategy;

7. The method according to claim 1 or 2,

the business operation support BOSS generates data domain shutdown information according to the first preset information, and the data domain shutdown information comprises the following steps:

8. The method according to claim 1 or 2,

the method further comprises the following steps:

the first entity acquires the data domain reset information;

the CRF entity sends a recovery instruction to the second entity according to the data domain recovery information;

9. A communication system, comprising:

the business operation support system BOSS is used for generating data domain shutdown information according to the first preset information;

the second entity is used for executing a restriction strategy of the first type of service data and a passing strategy of the second type of service data according to the data domain shutdown strategy; the first type of service data and the second type of service data are service data of the data domain and are different types of service data;

10. The system of claim 9,

11. The system of claim 9 or 10,

the first entity is specifically configured to receive a data domain shutdown instruction indicating data domain shutdown from the BOSS when an interface exists between the first entity and the BOSS.

12. The system of claim 9 or 10,

the BOSS is used for assigning a message to a Mobile Management Entity (MME) through a Home Subscriber Server (HSS) when no interface exists between the first entity and the BOSS;

13. The system of claim 9 or 10,

the limiting strategy comprises the following steps: a gating strategy;

14. The system of claim 9 or 10,

the limiting strategy comprises the following steps: a rate control strategy;

15. The system of claim 9 or 10,

the BOSSs is specifically configured to generate the data domain shutdown information according to at least one of the usage state information, the payment state information, and a user shutdown instruction of the first type of service data.

16. The system of claim 9 or 10,

the BOSS is also used for generating data field reset information according to second preset information;