阅读说明：本技术 一种流量业务处理方法及装置 (Traffic service processing method and device ) 是由 黄勇 于 2018-07-04 设计创作，主要内容包括：本发明实施例公开了一种流量业务处理方法及装置,应用于业务发布平台；所述方法包括：接收企业客户终端发送的流量包购买申请,所述流量包购买申请中至少携带有下述信息：企业客户标识、流量包大小、流量包类型、有效日期；基于所述流量包购买申请为所述企业客户终端签订流量包购买业务；接收企业客户终端发送的流量包分发申请；所述流量包分发申请携带有多个用户终端对应的用户识别卡号码信息；基于所述流量包分发申请,为每个所述用户终端确定待分发的流量包的大小。(The embodiment of the invention discloses a method and a device for processing a flow service, which are applied to a service publishing platform; the method comprises the following steps: receiving a traffic packet purchase application sent by an enterprise client terminal, wherein the traffic packet purchase application at least carries the following information: enterprise customer identification, traffic packet size, traffic packet type, and effective date; signing a flow packet purchasing service for the enterprise client terminal based on the flow packet purchasing application; receiving a flow packet distribution application sent by an enterprise client terminal; the flow packet distribution application carries user identification card number information corresponding to a plurality of user terminals; and determining the size of the traffic packet to be distributed for each user terminal based on the traffic packet distribution application.)

1. A traffic service processing method is applied to a service publishing platform; characterized in that the method comprises:

receiving a flow packet purchase application sent by an enterprise client terminal; the flow packet purchase request at least carries the following information: enterprise customer identification, traffic packet size, traffic packet type, and effective date;

and signing a flow packet purchasing service for the enterprise client terminal based on the flow packet purchasing application.

2. The method of claim 1, further comprising:

receiving a flow packet distribution application sent by an enterprise client terminal; the flow packet distribution application carries user identification card number information corresponding to a plurality of user terminals;

determining the size of a traffic packet to be distributed for each user terminal based on the traffic packet distribution application;

and establishing a binding relationship between the user identification card number corresponding to each user terminal and the flow packet with the corresponding size.

3. The method according to claim 1, wherein after establishing the binding relationship between the subscriber identity card number corresponding to each of the subscriber terminals and the traffic packet of the corresponding size, the method further comprises:

and sending a short message notification to a user terminal through a short message gateway, wherein the short message notification is used for prompting a user that the enterprise client terminal customizes the related information of the flow packet for the user.

4. The method of claim 1, further comprising:

receiving a flow usage statistics viewing request sent by an enterprise client terminal;

returning a traffic usage statistic based on the traffic usage statistic viewing request;

wherein, the flow use statistical condition at least comprises one or more of the following conditions: the total flow of the enterprise purchase flow package, the total distribution flow, the number of distribution users and the flow use condition of each user.

5. The method of claim 1, wherein the receiving of the traffic package purchase request sent by the enterprise client terminal comprises:

receiving a flow packet purchase application sent by an enterprise client terminal through an enterprise WEB portal provided by a service release platform; or

And receiving a flow packet purchase application sent by an enterprise client terminal through a capability open API interface provided by the service publishing platform.

6. The method according to claim 1, wherein after establishing the binding relationship between the subscriber identity card number corresponding to each of the subscriber terminals and the traffic packet of the corresponding size, the method further comprises:

and according to the binding relationship, preferentially reducing the flow presented to the user terminal by the enterprise client terminal.

7. A flow business processing device is applied to a business publishing platform; characterized in that the device comprises:

the acquisition unit is used for receiving a flow packet purchase application sent by an enterprise client terminal; the flow packet purchase request at least carries the following information: enterprise customer identification, traffic packet size, traffic packet type, and effective date;

and the signing unit is used for signing the flow package purchasing service for the enterprise client terminal based on the flow package purchasing application.

8. The apparatus of claim 7,

the acquiring unit is also used for receiving a flow packet distribution application sent by the enterprise client terminal; the flow packet distribution application carries user identification card number information corresponding to a plurality of user terminals;

the device further comprises:

the distribution unit is used for determining the size of the traffic packet to be distributed for each user terminal based on the traffic packet distribution application;

and the binding unit is used for establishing the binding relationship between the user identification card number corresponding to each user terminal and the flow packet with the corresponding size.

9. The apparatus of claim 7, further comprising:

and the notification unit is used for sending a short message notification to the user terminal through the short message gateway after the binding relationship between the user identification card number corresponding to each user terminal and the flow packet with the corresponding size is established, wherein the short message notification is used for prompting the user that the enterprise client terminal customizes the related information of the flow packet for the user.

10. The apparatus of claim 7, further comprising:

the checking unit is used for receiving a flow usage statistics checking request sent by an enterprise client terminal; returning a traffic usage statistic based on the traffic usage statistic viewing request;

wherein, the flow use statistical condition at least comprises one or more of the following conditions: the total flow of the enterprise purchase flow package, the total distribution flow, the number of distribution users and the flow use condition of each user.

Technical Field

The present invention relates to the field of communications, and in particular, to a method and an apparatus for processing a traffic service.

Background

For traditional telecom operator traffic packet marketing, the traffic packet is generally purchased by an individual from an operator, or donated to the individual by the individual, and the Business Operation Support System (BOSS) completes the relevant Business Support service. Currently, many enterprises offer an internal welfare for attracting more customers to expand their business or for promoting employee enthusiasm, willing to purchase traffic packages from telecommunications carriers, and then distribute the purchased traffic packages to customers or employees. However, currently, a Service Delivery Platform (SDP) does not have a related service function, and further does not provide an integrated solution for purchasing and distributing a traffic package for a third-party enterprise.

Disclosure of Invention

In order to solve the above technical problem, embodiments of the present invention are expected to provide a method and an apparatus for processing a traffic service, which can provide a solution for a third-party enterprise to purchase a traffic package and distribute the traffic package.

In a first aspect, an embodiment of the present invention provides a traffic service processing method, which is applied to a service publishing platform; the method comprises the following steps:

receiving a flow packet purchase application sent by an enterprise client terminal; the flow packet purchase request at least carries the following information: enterprise customer identification, traffic packet size, traffic packet type, and effective date;

and signing a flow packet purchasing service for the enterprise client terminal based on the flow packet purchasing application.

In this embodiment of the present invention, optionally, the method further includes:

receiving a flow packet distribution application sent by an enterprise client terminal; the flow packet distribution application carries user identification card number information corresponding to a plurality of user terminals;

determining the size of a traffic packet to be distributed for each user terminal based on the traffic packet distribution application;

and establishing a binding relationship between the user identification card number corresponding to each user terminal and the flow packet with the corresponding size.

In this embodiment of the present invention, optionally, after establishing the binding relationship between the subscriber identity card number corresponding to each subscriber terminal and the traffic packet of the corresponding size, the method further includes:

and sending a Short Message notification to the user terminal through a Short Message Gateway (SMG), wherein the Short Message notification is used for prompting the user that the enterprise client terminal customizes the related information of the traffic packet for the user.

In this embodiment of the present invention, optionally, the method further includes:

receiving a flow usage statistics viewing request sent by an enterprise client terminal;

returning a traffic usage statistic based on the traffic usage statistic viewing request;

wherein, the flow use statistical condition at least comprises one or more of the following conditions: the total flow of the enterprise purchase flow package, the total distribution flow, the number of distribution users and the flow use condition of each user.

In this embodiment of the present invention, optionally, the receiving a traffic packet purchase application sent by an enterprise client terminal includes:

receiving a flow packet purchase application sent by an enterprise client terminal through an enterprise WEB portal provided by a service release platform; or

And receiving a flow packet purchase application sent by the enterprise client terminal through a capability open API provided by the service publishing platform.

In this embodiment of the present invention, optionally, the establishing of the binding relationship between the subscriber identity card number corresponding to each subscriber terminal and the traffic packet of the corresponding size includes:

if the number of the user identification card corresponding to the user terminal is the first Subscription, the service publishing platform initiates an account opening request to a user attribute Storage (SPR);

after receiving a response of agreeing to open an account returned by the user attribute memory, initiating a synchronous request of a user signing package to the user attribute memory, and receiving the response of agreeing to sign returned by the user attribute memory;

and establishing a binding relationship between the number of the user identification card corresponding to the user terminal and the flow packet with the corresponding size.

In this embodiment of the present invention, optionally, after establishing the binding relationship between the subscriber identity card number corresponding to each subscriber terminal and the traffic packet of the corresponding size, the method further includes:

and according to the binding relationship, preferentially reducing the flow presented to the user terminal by the enterprise client terminal.

In a second aspect, an embodiment of the present invention provides a traffic service processing apparatus, which is applied to a service publishing platform; the device comprises:

the acquisition unit is used for receiving a flow packet purchase application sent by an enterprise client terminal; the flow packet purchase request at least carries the following information: enterprise customer identification, traffic packet size, traffic packet type, and effective date; and the signing unit is used for signing the flow package purchasing service for the enterprise client terminal based on the flow package purchasing application.

In the embodiment of the present invention, optionally, the obtaining unit is further configured to receive a traffic packet distribution application sent by an enterprise client terminal; the flow packet distribution application carries user identification card number information corresponding to a plurality of user terminals;

the device further comprises:

the distribution unit is used for determining the size of the traffic packet to be distributed for each user terminal based on the traffic packet distribution application;

and the binding unit is used for establishing the binding relationship between the user identification card number corresponding to each user terminal and the flow packet with the corresponding size.

In this embodiment of the present invention, optionally, the apparatus further includes:

and the notification unit is used for sending a short message notification to the user terminal through the short message gateway after the binding relationship between the user identification card number corresponding to each user terminal and the flow packet with the corresponding size is established, wherein the short message notification is used for prompting the user that the enterprise client terminal customizes the related information of the flow packet for the user.

In this embodiment of the present invention, optionally, the apparatus further includes:

the checking unit is used for receiving a flow usage statistics checking request sent by an enterprise client terminal; returning a traffic usage statistic based on the traffic usage statistic viewing request;

wherein, the flow use statistical condition at least comprises one or more of the following conditions: the total flow of the enterprise purchase flow package, the total distribution flow, the number of distribution users and the flow use condition of each user.

In this embodiment of the present invention, optionally, the receiving unit is further configured to:

receiving a flow packet purchase application sent by an enterprise client terminal through an enterprise WEB portal provided by a service release platform; or

And receiving a flow packet purchase application sent by an enterprise client terminal through a capability open API interface provided by the service publishing platform.

In this embodiment of the present invention, optionally, the binding relationship is further configured to:

if the user identification card number corresponding to the user terminal is the first subscription, initiating an account opening request to a user attribute memory;

after receiving a response of agreeing to open an account returned by the user attribute memory, initiating a synchronous request of a user signing package to the user attribute memory, and receiving the response of agreeing to sign returned by the user attribute memory;

and establishing a binding relationship between the number of the user identification card corresponding to the user terminal and the flow packet with the corresponding size.

In this embodiment of the present invention, optionally, the apparatus further includes:

and the flow deduction unit is used for preferentially deducting the flow given to the user terminal by the enterprise client terminal according to the binding relationship after the binding relationship between the user identification card number corresponding to each user terminal and the flow packet with the corresponding size is established.

In a third aspect, an embodiment of the present invention further provides a computer storage medium, where a computer-executable instruction is stored in the computer storage medium, and the computer-executable instruction is used to execute the traffic service processing method according to the embodiment of the present invention.

In the technical scheme of the embodiment of the invention, a flow packet purchase application sent by an enterprise client terminal is received; the flow packet purchase request at least carries the following information: enterprise customer identification, traffic packet size, traffic packet type, and effective date; (ii) a And signing a flow package purchasing service for the enterprise client terminal based on the flow package purchasing application, and at least providing a solution for purchasing and distributing the flow package for a third-party enterprise.

Drawings

Fig. 1 is a schematic diagram of a framework of a traffic service processing system according to an embodiment of the present invention;

fig. 2 is a schematic flow chart of a traffic service processing method according to an embodiment of the present invention;

fig. 3 is a schematic processing flow diagram for implementing the service of purchasing and distributing the traffic package by the enterprise in the SDP according to the embodiment of the present invention;

fig. 4 is a schematic structural diagram of a flow service device according to an embodiment of the present invention.

Detailed Description

So that the manner in which the features and aspects of the embodiments of the present invention can be understood in detail, a more particular description of the embodiments of the invention, briefly summarized above, may be had by reference to the embodiments, some of which are illustrated in the appended drawings.

Fig. 1 is a schematic diagram of a framework of a traffic service processing system according to an embodiment of the present invention, and as shown in fig. 1, the traffic service processing system includes: SDP (service distribution platform), third-party enterprise, BOSS (service operation support system), user attribute Storage (SPR), Short Message Gateway (SMG).

The SDP is responsible for providing WEB services and capability open interface services for purchasing the traffic package, distributing the traffic package and traffic operation statistics to third-party enterprises, authenticating the identity of enterprise users, making rating and charging requests for the purchasing traffic package, performing legal verification and background batch signing on the distributing users and providing services for enterprise traffic operation analysis statistics. And the business interacts with a third-party enterprise through a WEB portal or a Simple Object Access Protocol (SOAP) interface, interacts with a BOSS through a SOAP interface, and interacts with an SPR through a SOAP interface.

The BOSS is responsible for accepting a fee deduction request sent by the SDP, returning a success response to the SDP after fee deduction is successful, and the BOSS and the SDP are interacted through an SOAP interface.

The SPR is responsible for completing flow packet signing service in a core network for a terminal user, and interaction is carried out between the SPR and the SDP through an SOAP interface.

The SMG is responsible for sending a prompt short message to the user side after the enterprise traffic signs to the user successfully, and the SMG and the SDP interact with each other through SP Authentication Protocol (span).

The traffic service processing system provided by the embodiment of the invention provides one-stop service for purchasing, distributing and analyzing traffic packets and traffic operation, which is more efficient, convenient and flexible, for vast third-party enterprises, pulls the traffic sale and utilization rate of mobile communication networks such as 3G/4G/5G and the like, promotes the rapid development of traffic operation of telecom operators, and provides strong system support.

Fig. 2 is a schematic flow chart of a traffic service processing method according to an embodiment of the present invention, which is applied to a service publishing platform, and as shown in fig. 2, the method includes:

step 201: receiving a flow packet purchase application sent by an enterprise client terminal; the flow packet purchase request at least carries the following information: enterprise customer identification, traffic packet size, traffic packet type, expiration date.

In some optional embodiments, the receiving a traffic package purchase request sent by an enterprise client terminal includes:

and receiving a flow packet purchase application sent by an enterprise client terminal through an enterprise WEB portal provided by a service release platform.

In other optional embodiments, the receiving a traffic package purchase request sent by an enterprise client terminal includes:

and receiving a flow packet purchase application sent by the enterprise client terminal through a capability open API provided by the service publishing platform.

Step 202: and signing a flow packet purchasing service for the enterprise client terminal based on the flow packet purchasing application.

Further optionally, the method further comprises:

step 203 (not shown in fig. 2): receiving a flow packet distribution application sent by an enterprise client terminal; the flow packet distribution application carries user identification card number information corresponding to a plurality of user terminals.

Step 204 (not shown in fig. 2): and determining the size of the traffic packet to be distributed for each user terminal based on the traffic packet distribution application.

Optionally, the purchase request further includes at least information such as a size of the traffic packet, a type (general or directional) of the traffic packet, directional information, and time of validity and invalidity of the traffic packet.

Step 205 (not shown in fig. 2): and establishing a binding relationship between the user identification card number corresponding to each user terminal and the flow packet with the corresponding size.

In some optional embodiments, the establishing a binding relationship between a subscriber identity card number corresponding to each of the subscriber terminals and a traffic packet of a corresponding size includes:

if the user identification card number corresponding to the user terminal is the first subscription, the service issuing platform initiates an account opening request to the user attribute memory;

after receiving an account opening agreement response returned by the user attribute memory, initiating a user signing package synchronization request to the user attribute memory, and receiving a signing agreement response returned by the user attribute memory;

and after receiving a contract agreement response returned by the user attribute memory, establishing a binding relationship between the number of the user identification card corresponding to the user terminal and the flow packet with the corresponding size.

In this embodiment of the present invention, optionally, after establishing the binding relationship between the subscriber identity card number corresponding to each subscriber terminal and the traffic packet of the corresponding size, the method further includes:

and sending a short message notification to a user terminal through a short message gateway, wherein the short message notification is used for prompting a user that the enterprise client terminal customizes the related information of the flow packet for the user.

For example, the short message notification is: "you receive the flow package xxx million given by a certain enterprise, can use it free, and the validity period reaches xx month xx day".

In this embodiment of the present invention, optionally, the method further includes:

receiving a flow usage statistics viewing request sent by an enterprise client terminal;

returning a traffic usage statistic based on the traffic usage statistic viewing request;

wherein, the flow use statistical condition at least comprises one or more of the following conditions: the total flow of the enterprise purchase flow package, the total distribution flow, the number of distribution users and the flow use condition of each user.

Therefore, an enterprise or an operator can check the total flow, the total cost, the total distribution flow and the number of distribution users of the enterprise purchase flow package, the use flow of each user distributed by the enterprise and the like, analyze the online real-time check of data, master the flow expenditure condition and the flow use dynamic of the final user for the enterprise, and better promote the future flow marketing; the sales dynamics of the enterprise can be accurately mastered by the operator.

In this embodiment of the present invention, optionally, after establishing the binding relationship between the subscriber identity card number corresponding to each subscriber terminal and the traffic packet of the corresponding size, the method further includes:

and according to the binding relationship, preferentially reducing the flow presented to the user terminal by the enterprise client terminal.

For the use of the user, after the user finishes the flow packet subscription, the service publishing platform distributes the user internet flow in a quota distribution mode according to the subscription relation of the enterprise donation user flow packet, and finishes the preferential deduction of the enterprise donation user flow.

In this way, the traffic given to the user terminal by the enterprise client terminal is reduced preferentially, rather than the traffic purchased by the user, so that the user benefit can be fully considered.

In the technical scheme of the embodiment of the invention, a solution for purchasing the flow package and distributing the flow package can be provided for third-party enterprises, more efficient, convenient and flexible one-stop service for purchasing the flow package, distributing the flow package and analyzing and counting the flow operation can be provided for the third-party enterprises, the flow sale and utilization rate is pulled, and the rapid development of the flow operation of telecommunication operators is promoted.

Fig. 3 is a schematic processing flow diagram for implementing the service of purchasing and distributing the traffic package by the enterprise in the SDP provided by the embodiment of the present invention, and as shown in fig. 3, the flow includes:

step 301: the enterprise client initiates a flow packet purchase application;

in an alternative embodiment, the enterprise client initiates a traffic package purchase request through logging in an enterprise WEB portal provided by the SDP, for example, first filling in purchase information such as traffic package size, traffic package type (general or directional), directional information, traffic package validation and expiration time, and then submitting the purchase request.

In another alternative embodiment, the enterprise customer initiates the traffic package purchase request through a capability open API interface provided by the SDP.

It should be noted that, if the traffic package purchase request is initiated through the capability openness API interface provided by the SDP, the capability openness API interface can directly return a processing result response, that is, a manual operation link of step 302 described below need not be executed.

Step 302: SDP completes rating and enterprise validation.

Specifically, the SDP completes rating and displays the total cost at a WEB portal, and meanwhile, the enterprise client selects a traffic package purchase mode to complete confirmation submission operation.

In an alternative embodiment, the enterprise client preferably selects a telephone fee payment mode to purchase; if the approval is not passed, the enterprise client can directly delete the returned application information, or can jump to the step 301, and resubmit the returned application information after modifying the payment mode on the basis of the returned application information.

Step 303: the SDP initiates a fee deduction request to the BOSS, and the BOSS returns a fee deduction response to the SDP;

specifically, the BOSS returns a fee deduction result to the SDP after receiving the acceptance, and the SDP records the fee deduction result.

Step 304: the enterprise client imports the user number file through a WEB portal provided by the SDP.

Of course, the enterprise client may also enter the user number through a WEB portal provided by the SDP.

In an alternative embodiment, the enterprise customer imports a subscriber number file for the purchased traffic package and selects the amount of traffic to assign to each end user.

In another alternative embodiment, the enterprise client calls the user number file to distribute the traffic through the capability open API interface.

And the user number file carries the user number and the flow size distributed to each user.

It should be noted that, if the user number file is called through the capability openness API interface provided by the SDP, the capability openness API interface can directly return a processing result response, that is, WEB portal prompt information for executing the two steps of step 306 and step 308 described below is not required.

Here, the traffic size may be in megabytes (MByte).

Step 305: the SDP carries out legal verification on the imported number, eliminates the number which is not verified to pass and continuously processes the verification to pass;

step 306: if the user signs a contract for the first time, the SDP initiates a user account opening request to the SPR; the SPR returns a response result.

Further, the WEB portal simultaneously displays the prompt information of 'during batch signing and please wait'.

Step 307: SDP initiates a user signing package synchronization request to SPR, and SPR returns a response result;

step 308: the SDP returns a response result according to the SPR and records a corresponding flow packet bound when the user signs a package;

further, when the account opening and signing results of the users to be batched are completely finished, the WEB portal displays prompt information of 'batch signing is finished', provides a 'exporting failure detail' button, and clicks a user number list file capable of exporting signing failures.

Step 309: SDP sends short message notice to user through SMG, and receives response returned by SMG that user has received short message notice.

For example, the notification may relate to the following: "you receive the flow package xxx million given by yyy enterprise, can use it free, and the validity period is to xx month xx day".

Further, after the user completes the flow package subscription, the SDP distributes the user internet flow in a quota fragmentation mode according to the subscription relation of the enterprise presentation user flow package, and completes the preferential deduction of the enterprise presentation user flow.

Further, the SDP provides an enterprise traffic operation analysis statistical service, and an enterprise or an operator or an enterprise can view the total traffic of the enterprise purchase traffic package, the total distribution traffic, the number of distribution users, and the usage traffic of each user distributed by the enterprise.

The technical scheme flow of the embodiment of the invention mainly comprises three steps:

the first step is as follows: an enterprise initiates a flow package purchase application through an SDP capability open API interface call or a WEB portal provided by an SDP, wherein the flow package purchase application carries information such as the enterprise, the size of a flow package, the type (general or directional) of the flow package, directional information, the validity period and the like;

the second step is that: enterprises initiate flow package distribution application through SDP capability open API interface calling or WEB portals provided by SDP, distribute flow for terminal users, the flow package distribution application carries terminal user numbers and flow size distributed by each terminal user, and simultaneously informs the terminal users through short messages. The terminal user obtains the flow of the donation and then preferentially deducts the flow of the donation of the enterprise;

the third step: the enterprise can check the total flow, the total cost, the total distribution flow, the number of distribution users of the enterprise purchase flow package and the usage flow of each user distributed by the enterprise on line through the SDP capability open API interface call or a WEB portal provided by the SDP.

The technical scheme of the embodiment of the invention has the following beneficial effects: first, a third-party enterprise can complete the purchase service of the traffic package by using a WEB portal service or a capability open API interface provided by the SDP, and realize the customization of the type, size, validity period, and the like of online freely purchased traffic. Secondly, the third-party enterprise can utilize a WEB portal service or a capability open API interface provided by the SDP to complete the service of distributing the traffic package to the end user, and the user input can be list file import or number segment input, so as to realize the customization of the target user, the distribution size and the distribution times of the online free distribution traffic. Thirdly, an operator or an enterprise can check the total flow, the total cost, the total distribution flow and the number of distribution users of the enterprise purchase flow package, the use flow of each user distributed by the enterprise and the like, analyze the online real-time check of data, and accurately master the sales dynamics of the enterprise for the operator; for enterprises, the traffic expense condition and the traffic use dynamic state of end users can be mastered, and future traffic marketing can be better promoted.

Fig. 4 is a schematic diagram of a structure of a traffic service processing apparatus according to an embodiment of the present invention, which is applied to a service publishing platform; as shown in fig. 4, the apparatus includes:

an acquiring unit 10, configured to receive a flow packet purchase application sent by an enterprise client terminal; the flow packet purchase application at least carries user identification card number information corresponding to a plurality of user terminals;

and an signing unit 20, configured to sign a traffic package purchase service for the enterprise client terminal based on the traffic package purchase application.

In this embodiment of the present invention, optionally, the obtaining unit 10 is further configured to receive a flow packet distribution application sent by an enterprise client terminal; the flow packet distribution application carries user identification card number information corresponding to a plurality of user terminals.

Further, the apparatus further comprises:

the allocating unit 30 is configured to determine, for each user terminal, a size of a traffic packet to be distributed based on the traffic packet distribution application;

a binding unit 40, configured to establish a binding relationship between the subscriber identity card number corresponding to each subscriber terminal and the traffic packet of the corresponding size.

In this embodiment of the present invention, optionally, the apparatus further includes:

a notification unit 50, configured to send a short message notification to the user terminal through the short message gateway after establishing a binding relationship between the subscriber identity card number corresponding to each user terminal and the traffic packet of the corresponding size, where the short message notification is used to prompt the user that the enterprise client terminal customizes the relevant information of the traffic packet for the user.

In this embodiment of the present invention, optionally, the apparatus further includes:

a viewing unit 60, configured to receive a traffic usage statistics viewing request sent by an enterprise client terminal; returning a traffic usage statistic based on the traffic usage statistic viewing request;

wherein, the flow use statistical condition at least comprises one or more of the following conditions: the total flow of the enterprise purchase flow package, the total distribution flow, the number of distribution users and the flow use condition of each user.

As an optional implementation manner, the receiving unit 10 is specifically configured to:

and receiving a flow packet purchase application sent by an enterprise client terminal through an enterprise WEB portal provided by a service release platform.

As an optional implementation manner, the receiving unit 10 is specifically configured to:

and receiving a flow packet purchase application sent by an enterprise client terminal through a capability open API interface provided by the service publishing platform.

As an optional implementation manner, the binding unit 40 is further configured to:

if the user identification card number corresponding to the user terminal is the first subscription, initiating an account opening request to a user attribute memory;

after receiving an account opening agreement response returned by the user attribute memory, initiating a user signing package synchronization request to the user attribute memory;

and when a contract signing agreement response returned by the user attribute memory is received, establishing a binding relationship between the number of the user identification card corresponding to the user terminal and the flow packet with the corresponding size.

In this embodiment of the present invention, optionally, the apparatus further includes:

and a traffic deduction unit 70, configured to, after the binding unit 40 establishes a binding relationship between the subscriber identity card number corresponding to each subscriber terminal and a traffic packet of a corresponding size, preferentially deduct, according to the binding relationship, traffic given to the subscriber terminal by the enterprise client terminal.

In practical applications, the obtaining Unit 10, the signing Unit 20, the allocating Unit 30, the binding Unit 40, the notifying Unit 50, the viewing Unit 60, and the flow deducting Unit 70 may be implemented by a Central Processing Unit (CPU), a Microprocessor Unit (MPU), a Digital Signal Processor (DSP), a Field Programmable Gate Array (FPGA), or the like, which are located in the flow service Processing apparatus.

The traffic service processing apparatus according to this embodiment can provide a solution for purchasing a traffic package and distributing the traffic package for a third-party enterprise.

The present embodiment also provides a storage medium, where a computer program is stored, and after being executed by a processor, the computer program can implement any one or more of the foregoing traffic service processing methods.

The computer storage medium may be of various types, and in this embodiment may preferably be a non-transitory storage medium.

Those skilled in the art will understand that the functions of the programs in the storage medium of the present embodiment can be understood by referring to the related description of the traffic service processing method described in the embodiments.

Compared with the prior art, the device provided by the embodiment of the invention has the following beneficial effects: first, a third-party enterprise can complete the purchase service of the traffic package by using a WEB portal service or a capability open API interface provided by the SDP, and realize the customization of the type, size, validity period, and the like of online freely purchased traffic. Secondly, the third-party enterprise can utilize a WEB portal service or a capability open API interface provided by the SDP to complete the service of distributing the traffic package to the end user, and the user input can be list file import or number segment input, so as to realize the customization of the target user, the distribution size and the distribution times of the online free distribution traffic. Thirdly, an operator or an enterprise can check the total flow, the total cost, the total distribution flow and the number of distribution users of the enterprise purchase flow package, the use flow of each user distributed by the enterprise and the like, analyze the online real-time check of data, and accurately master the sales dynamics of the enterprise for the operator; for enterprises, the traffic expense condition and the traffic use dynamic state of end users can be mastered, and future traffic marketing can be better promoted.

The technical schemes described in the embodiments of the present invention can be combined arbitrarily without conflict.

In the embodiments provided in the present invention, it should be understood that the disclosed method and intelligent device 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 second processing unit, or each unit may be separately regarded 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.

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.