WO2018001181A1 - 一种计费方法和计费系统 - Google Patents

一种计费方法和计费系统 Download PDF

Info

Publication number
WO2018001181A1
WO2018001181A1 PCT/CN2017/089765 CN2017089765W WO2018001181A1 WO 2018001181 A1 WO2018001181 A1 WO 2018001181A1 CN 2017089765 W CN2017089765 W CN 2017089765W WO 2018001181 A1 WO2018001181 A1 WO 2018001181A1
Authority
WO
WIPO (PCT)
Prior art keywords
session
account
sub
resource
charging
Prior art date
Application number
PCT/CN2017/089765
Other languages
English (en)
French (fr)
Inventor
魏霄鹏
张秀丽
郭建广
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2018001181A1 publication Critical patent/WO2018001181A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP

Definitions

  • the present application relates to the field of communications, for example, to a charging method and a charging system.
  • the traditional user billing service uses the user's mobile phone number as the billing account, and records information such as the short message, traffic, and duration of the call used by the user on the mobile phone number of the user, and pays according to the record corresponding to the mobile phone number.
  • the traditional method of using a single mobile phone number as the sole billing account is becoming smaller and smaller.
  • multi-platform calling terminals are required, and the same user may use terminals of different platforms, and real-time statistics are needed for information such as Internet traffic usage and call duration usage of terminals of different platforms, if still using the traditional
  • the user billing scheme performs charging according to the mobile phone number of the terminal.
  • the user needs to use multiple terminals, it is required to charge each terminal of the user, and the user needs to pay according to the telephone number of each terminal, whether it is statistics or not.
  • the service party of the fee, or the user side of the payment is cumbersome to manage, wastes time, and also reduces the user experience.
  • the embodiments of the present disclosure provide a charging method and a charging system, which solves the problem that the charging management is complicated, wastes time, increases the time required for users to pay, and reduces the user experience. problem.
  • An embodiment of the present disclosure provides a charging method, including:
  • the primary account is charged according to the session resource used by the session corresponding to the session request.
  • the embodiment of the present disclosure further provides a charging system, including: a charging platform and a sub-account storage entity, where a sub-account storage entity pre-stores a correspondence between a sub-account and a main account;
  • the charging platform is configured to receive the session request, obtain the information of the corresponding sub-account according to the session application, query the primary account corresponding to the sub-account from the sub-account storage entity according to the information of the sub-account; and apply the session corresponding to the session according to the session request
  • the resource bills the primary account.
  • Embodiments of the present disclosure also provide a computer readable storage medium storing computer executable instructions arranged to perform the above method.
  • An embodiment of the present disclosure further provides an electronic device, including:
  • At least one processor At least one processor
  • the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to cause the at least one processor to perform the method described above.
  • the embodiment of the present disclosure discloses a charging method and a charging system, which can obtain information of a corresponding sub-account according to the received session application, and query the corresponding sub-account according to the correspondence between the information of the sub-account and the main account. The account then charges the primary account according to the session resource used by the session requesting the corresponding session.
  • the session resource used by the session of the sub-account of the present disclosure is included in the primary account for deduction, different terminals may use different The sub-account sends a session request, so the present disclosure can use one master account to pay for at least one sub-account, and collect the billing of multiple sub-accounts into the main account, which satisfies the billing management requirements of the terminals of different platforms, as opposed to
  • the disclosure can record the cost of multiple terminals using the sub-account in one main account, save the charging time, improve the charging efficiency, and at the same time, use the present Publicly, users can only pay for the main account, which is beneficial to enhance the user experience.
  • FIG. 1 is a flowchart of a charging method according to Embodiment 1 of the present disclosure
  • FIG. 2 is a structural diagram of a charging system according to Embodiment 2 of the present disclosure.
  • FIG. 3 is a structural diagram of another charging system according to Embodiment 2 of the present disclosure.
  • FIG. 4 is a flowchart of a method for opening a primary account and a sub account by using a charging system according to Embodiment 2 of the present disclosure
  • FIG. 5 is a flowchart of a method for querying a primary account according to a session request by using a charging system according to Embodiment 2 of the present disclosure
  • FIG. 6 is a schematic structural diagram of an electronic device using an embodiment of the present disclosure.
  • Embodiment 1 is a diagrammatic representation of Embodiment 1:
  • this embodiment provides a charging method, including:
  • S104 Perform charging on the primary account according to the session resource used by the session corresponding to the session request.
  • the correspondence between the primary account and the sub-account is preset.
  • the charging system of the operator or the service provider provides the user with a primary account opening service, and when the user opens the account, the user can obtain a primary account and a corresponding sub-account, wherein the primary account can carry a default when the account is first opened.
  • the sub-account also provides the user with the function of setting the sub-account. The user sets multiple sub-accounts under the main account according to his own needs, and then stores the corresponding relationship between the sub-account and the main account for subsequent use.
  • the billing system can also provide services such as the main account's account cancellation business and the main account recharge service.
  • the main account's account cancellation business When the primary account is closed, all the sub accounts under the primary account can be deleted, and the corresponding relationship between the pre-stored sub-account and the primary account can be deleted. Since the sub-account fee is charged to the main account for unified billing, when recharging, only the main account can be recharged.
  • the session request in S101 may be a message reported by a terminal using a sub-account before starting the session.
  • the terminal can include a mobile phone, a tablet, a networked walkie-talkie, and the like.
  • the sub-account and the primary account may have a many-to-one relationship.
  • multiple terminals may use different sub-accounts to initiate a session application at the same time.
  • the S102 is configured according to the session request.
  • the sub-account information is used to distinguish sub-accounts corresponding to different session applications. Then, according to the pre-stored correspondence between the sub-account and the primary account, the information of the primary account corresponding to the sub-account can be quickly found, and the primary account corresponding to the different sub-accounts can be accurately charged.
  • the sub-account can be set when the sub-account is opened.
  • the expiration date, the expiration date, the sub-account automatically expires, and it is convenient to control the effective use duration of the sub-account.
  • the validity period of the sub-account can also be set during the use of the sub-account.
  • the sub-account can be opened when the primary account is opened, or can be opened during the use of the primary account. Therefore, the time for setting the validity period of the sub-account can be the time of opening the account of the primary account or the process of using the primary account. in.
  • the efficiency of reading the correspondence between the sub-account and the primary account in the above S103 has a certain influence on the charging efficiency of the embodiment.
  • the primary account corresponding to the sub-account can be quickly queried, and the sub-account and the primary account can be The correspondence is stored in a sub-account storage entity that employs efficient storage and read operations.
  • the corresponding primary account may be queried by using the message carrying the sub-account information to the sub-account storage entity.
  • the primary account that returns information corresponding to the sub-account is returned by the sub-account storage entity.
  • the session corresponding to each session application uses a certain session resource from the beginning to the end.
  • the charging of the primary account is actually performed according to the session resources used by the session initiated by the child account of the primary account. Billing.
  • the session resources in this embodiment may include a call duration slice, an Internet traffic slice, and the like.
  • the session resources of this embodiment may also include other resources used in the session, such as short messages.
  • the payment method of the main account includes the following two types: prepaid and postpaid: If the prepaid method is adopted, there will be a corresponding pre-stored package in the main account, and the package may include a certain amount of call duration and Internet traffic.
  • the session resource used by the session corresponding to the session request may be deducted from the package in the primary account, thereby charging the primary account. .
  • step S104 when the primary account is charged according to the session resource used by the session corresponding to the session request, the session resource used for the session corresponding to the session request of the child account may be converted into a fee according to the corresponding standard. The deduction of the main account.
  • the charging is performed in a prepaid manner.
  • the session resource may be allocated to the session corresponding to the session request according to the remaining situation of the session resource.
  • the preset allocation rule may be performed according to the preset allocation rule: each time a fixed-sized Internet traffic slice or a fixed-time call duration is allocated to the session request. Session; or, according to the remaining situation of the session resources in the primary account, each time 1/10 of the currently remaining session resources in the primary account are allocated to the session of the child account.
  • the session request in this embodiment may also carry the required number of session resources, and allocate corresponding session resources to the session corresponding to the session request according to the remaining situation of the session resources of the primary account, including: in the remaining session resources of the primary account, the session is The corresponding session is requested to allocate the session resources required by the session request.
  • the session request allocation requirement cannot be met, that is, when the remaining session resources of the primary account are insufficient to allocate a call duration slice or an Internet traffic slice, the session request is returned to the terminal that initiated the session.
  • a failed message telling you that the session request failed. Avoid users' losses caused by not knowing that the Internet is offline or the call is disconnected.
  • allocating corresponding session resources includes allocating corresponding call duration films or Internet traffic slices. It can be understood that the session resource allocated for a session request may not be sufficient for the session. In this case, the terminal performing the session may report the session request again, and obtain a new call duration or Internet traffic for the session. sheet. Therefore, when there are multiple session requests corresponding to the session, the first session application and the subsequent session application may be divided. When the session application is the initial session application, the The session corresponding to the session request has not used the session resource. From this point on, the session resources used by the session are counted.
  • the types of session resources required by different sessions may be different. For example, some session resources required by the session are Internet traffic, some session resources required by the session are call durations, and different types of session resources, billing units, and meters are calculated. Fee standards are different, so you can separate the session resources of different sessions. At the same time, multiple sessions of the same type of session resources are required, and the corresponding primary accounts may be different. In order to accurately charge different primary accounts, session resources of different sessions may be separately counted.
  • the session identifier of the session corresponding to the initial session request is obtained, where the session identifiers of different sessions are different.
  • the session identifier may be set by the device or the platform that receives the session request, or may be carried by the session request itself. This embodiment does not limit this.
  • the statistics on the session resources of the session become much simpler. After each session resource is allocated for the session corresponding to the session request, the session resources allocated to the same session are accumulated according to the session identifier.
  • the session resource allocated by the current session may be recorded according to the session identifier.
  • the current session identifier is *908, and the session resource allocated for the session request is a call of 5 minutes.
  • the corresponding records of *908 and 5min are established, and the correspondence between the two data is established.
  • the corresponding terminal When the current session needs to apply for a new session resource, the corresponding terminal continues to report the session request and obtain a new session resource.
  • the session resource corresponding to the same session can be accumulated according to the session identifier.
  • the session ID of the session corresponding to the received session request is *908, and the session resource allocated for the corresponding session is 5 minutes, and the previous session is found according to the session identifier *908 of the session request. Record, add 5min corresponding to *908 to 10min. After the allocation is performed, the session resources allocated for the corresponding session request for the session are accumulated for 10 minutes.
  • the session resources allocated this time may be left.
  • the session resource used by the session recorded according to the session identifier may be modified accordingly: before the primary account is charged based on the session resource accumulated according to the session identifier, the session identifier is added according to the unused session resource update. Session resources.
  • the session resources accumulated according to the session identifier are updated according to the unused session resources, and the unused session resources are actually subtracted from the session resources accumulated according to the session identifier.
  • the session resource accumulated according to the session identifier is the session resource used by the session corresponding to the session request, and in step S104, the primary account may be charged according to the accumulated session resource.
  • the information of the corresponding sub-account can be obtained according to the received session application, and the primary account corresponding to the sub-account is queried according to the correspondence between the pre-stored sub-account and the primary account based on the information, and then The primary account is charged according to the session resource used by the session corresponding to the session request.
  • different terminals can use different sub-accounts to issue a session request, and one primary account pays for multiple sub-accounts, which satisfies different platforms.
  • the charging management requirement of the terminal is compared with the related art, and each terminal is charged according to the mobile phone number.
  • the disclosure can record the cost of multiple terminals using the sub-account in one main account, thereby saving billing time and improving The billing efficiency, at the same time, using the present disclosure, the user can only pay for the main account, which is beneficial to enhance the user experience.
  • Obtaining the session identifier of each session, and recording the session resources allocated for different sessions according to the session identifier, can ensure that the session resources are accurately counted for each session when there are multiple sessions, and the accounting of the primary account is accurate. Ensure multi-session billing.
  • Setting the validity period for the sub-account can effectively reduce the occupancy rate of the sub-account storage entity resources, improve the query efficiency of the query main account, and improve the billing efficiency.
  • Embodiment 2 is a diagrammatic representation of Embodiment 1:
  • the embodiment provides a charging system, including a charging platform 21 and a sub-account storage entity 22; a sub-account storage entity pre-stores a correspondence between a sub-account and a main account; and the charging platform is configured to receive a session request. And obtaining the information of the corresponding sub-account according to the session application, and querying the primary account corresponding to the sub-account from the sub-account storage entity according to the information of the sub-account; and charging the main account according to the session resource used by the session corresponding to the session request.
  • the sub-account in order to quickly query the primary account corresponding to the sub-account from the sub-account storage entity, the sub-account The storage entity uses efficient storage and read operations. It can be understood that the information of the primary account of this embodiment can be stored on the charging platform.
  • the embodiment further provides an operation support platform 23, which is provided by the service support system of the operator, and completes the account opening of the user's primary account and sub-accounts. , sales account, main account recharge, sub-account query function.
  • the user can open the account, the account, the recharge, and the sub-account of the primary account and the sub-account by using the short message to perform information interaction with the operation support platform 23.
  • the operation support platform 23 can provide a user interface for the user, and the user can perform account opening, account cancellation, primary account refilling, and sub-account inquiry of the primary account and the sub-account by performing corresponding operations on the user interface.
  • the operation support platform 23 is connected to the billing platform 21, and the billing platform 21 receives information such as opening and closing accounts of the main account and the sub-account reported by the user through the operation support platform, and completing the account opening and canceling of the main account and the sub-account by the user. jobs.
  • the operation support platform 23 can provide a default number of sub-accounts for a primary account, where the default number is generally one.
  • the operation support platform 23 provides the user with the function of setting a sub-account.
  • the user sets a plurality of sub-accounts under the main account according to the needs of the user, and the set data is transmitted by the operation support platform to the billing platform 21, and the billing platform 21 The correspondence between the sub-account and the primary account is determined.
  • a method for opening a plurality of sub-accounts by using the billing system of the present disclosure includes:
  • S401 The user completes the setting of the sub-account and the plurality of sub-accounts on the operation support platform, and the operation support platform sends an account opening message to the charging platform.
  • the account opening information includes the account opening information of the primary account and the sub account.
  • the charging platform After receiving the account opening message request of the operation support platform, the charging platform completes the account opening of the primary account.
  • the charging platform cyclically processes all the sub-accounts, and increases the correspondence between the sub-account and the main account in the sub-account storage entity.
  • the charging platform 21 deletes the primary account information on the charging platform according to the primary account deletion information returned by the operation supporting platform, and controls the child account storage entity 22 to delete the pre-stored child. The correspondence between the account and the primary account.
  • the validity period of the sub-account can be set when the sub-account is opened. When the validity period expires, the sub-account is automatically invalidated, which can conveniently control the effective use duration of the sub-account. In addition, the validity period of the sub-account can also be set during the use of the sub-account.
  • the session request may be a message reported by a terminal using a sub-account before starting the session.
  • the terminal can include a mobile phone, a tablet, a networked walkie-talkie, and the like.
  • the session resources in this embodiment may include a long duration call or an internet traffic slice.
  • FIG. 5 a method for finally querying a primary account according to a session request by using the charging system of the embodiment is illustrated, including:
  • S501 The terminal initiates a session application for applying for a long film of the call or an internet traffic piece.
  • the charging platform parses the information of the sub-account corresponding to the session application.
  • the charging platform queries the sub-account storage entity to query the main account information according to the information of the sub-account.
  • the payment method of the main account includes the following two types: pre-paid and post-paid: if the pre-paid method is adopted, there will be a corresponding pre-stored package in the main account, and the package may include a certain amount of call duration and Internet traffic. .
  • the charging platform 21 charges the primary account according to the session resource used by the session corresponding to the session request, the charging resource used by the session corresponding to the session request may be deducted from the package in the primary account, thereby charging the primary account.
  • the session resources will be charged according to certain standards, such as charging the Internet traffic in units of M or Hz, or charging the call duration in minutes.
  • the charging platform 21 charges the primary account according to the session resource used by the session corresponding to the session request
  • the session resource used by the session corresponding to the session request of the child account may be converted into a fee according to the corresponding standard, and is included in the primary account. In the case of deductions.
  • the charging is performed in a first-paying manner, that is, the session resource is available in the primary account.
  • the session resource is available in the primary account.
  • the charging system in this embodiment may further include a resource control entity 24, which receives the session request reported by the user terminal, and reports the session request request session resource to the charging platform 21, and the charging platform 21 is based on the primary account.
  • the remaining condition of the session resource allocates the corresponding session resource for the session of the sub-account, returns the value of the allocated session resource to the resource control entity 24, and the resource control entity 24 controls the session resource used by the session according to the numerical control.
  • the resource control entity 24 can perform corresponding processing, for example, cutting off the current session of the terminal. Remind the terminal that the session resources are insufficient.
  • the resource control entity 24 may, according to the value of the session resource returned by the charging platform 21 for the current session, monitor the remaining session resources in real time, and remind the user of the current session resource when the session resource is exhausted. Insufficient, a new session request is required to prevent the user from interrupting the session.
  • the types of session resources required by different sessions may be different. For example, some session resources required by the session are Internet traffic, some session resources required by the session are the duration of the call, and different types of session resources, charging units, and charging standards. They are all different, so you can separate the session resources of different sessions. At the same time, multiple sessions with the same session resource type may eventually have different primary accounts. In order to accurately charge different primary accounts, session resources of different sessions may be separately collected.
  • the charging platform 21 of the present embodiment is further configured to acquire the session identifier of the session corresponding to the initial session request when the initial session request is received, where the session identifiers of the different sessions are different.
  • the session identifier may be set by the charging platform 21 for the session, or may be carried by the session request itself. This embodiment does not limit this.
  • the statistics of the session resources of the session by the billing platform 21 become simple. After each session session resource is allocated for the session request, the session resources allocated for the session are accumulated based on the session identifier, and then the session resources allocated according to the session identifier are accumulated, and then based on the session resources accumulated according to the session identifier. The account is billed.
  • the process of accumulating the session resources allocated by the same session according to the session identifier reference may be made to the related description in the first embodiment, which is not described in this embodiment.
  • the resource control entity 24 informs the charging platform 21 of the remaining value of the unused session resources that were last allocated for the session. Returning the unused session resources to the primary account by the charging platform 21, and updating the session resources accumulated according to the session identifier according to the unused session resources before charging the primary account based on the session resources accumulated according to the session identifier. .
  • the session resources accumulated according to the session identifier are updated according to the unused session resources, and the unused session resources are actually subtracted from the session resources accumulated according to the session identifier.
  • the session resource accumulated according to the session identifier is the session resource used by the session corresponding to the session request.
  • the charging platform can receive the session request, obtain the information of the corresponding sub-account according to the session application, and then query the primary account from the sub-account storage entity, and use the session resource pair according to the session of the sub-account.
  • the primary account is billed.
  • billing of multiple sub-accounts is realized in one master account.
  • the terminal of the different platform can use the sub-account of the same primary account, and the payment of the sub-account can be completed by charging the primary account.
  • the charging platform allocates session resources to the session according to the remaining session resources of the primary account, which is beneficial to control the session resources used by the child account, is beneficial to reduce the difficulty of calculating the session resources used by the child account, and simplifies the statistical process of the session resources of the child accounts. Simplify the billing process for the primary account.
  • Embodiments of the present disclosure also provide a computer readable storage medium storing computer executable instructions arranged to perform the method of any of the above embodiments.
  • the computer readable storage medium may be a transitory computer readable storage medium or a non-transitory computer readable storage medium.
  • the embodiment of the present disclosure further provides a schematic structural diagram of an electronic device.
  • the electronic device includes:
  • At least one processor 60 which is exemplified by a processor 60 in FIG. 6; and a memory 61, may further include a communication interface 62 and a bus 63.
  • the processor 60, the communication interface 62, and the memory 61 can complete communication with each other through the bus 63.
  • Communication interface 62 can be used for information transfer.
  • the processor 60 can call the logic instructions in the memory 61 to execute The method of the above embodiment is carried out.
  • logic instructions in the memory 61 described above may be implemented in the form of a software functional unit and sold or used as a stand-alone product, and may be stored in a computer readable storage medium.
  • the memory 61 is used as a computer readable storage medium for storing software programs, computer executable programs, and program instructions/modules corresponding to the methods in the embodiments of the present disclosure.
  • the processor 60 executes the function application and the data processing by executing software programs, instructions, and modules stored in the memory 61, that is, implementing the charging method in the above method embodiments.
  • the memory 61 may include a storage program area and an storage data area, wherein the storage program area may store an operating system, an application required for at least one function; the storage data area may store data created according to usage of the terminal device, and the like. Further, the memory 61 may include a high speed random access memory, and may also include a nonvolatile memory.
  • the technical solution of the embodiments of the present disclosure may be embodied in the form of a software product stored in a storage medium, including one or more instructions for causing a computer device (which may be a personal computer, a server, or a network) The device or the like) performs all or part of the steps of the method described in the embodiments of the present disclosure.
  • the foregoing storage medium may be a non-transitory storage medium, including: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and the like.
  • the various modules or steps of the above disclosure may be implemented by a general-purpose computing device, which may be centralized on a single computing device or distributed over a network of multiple computing devices, optionally using computing devices
  • Executable program code is implemented such that they can be stored in a storage medium (ROM/RAM, disk, optical disk) by a computing device and, in some cases, can be executed in a different order than here.
  • the steps shown or described are either made separately into individual integrated circuit modules, or a plurality of modules or steps are fabricated as a single integrated circuit module. Therefore, the present disclosure is not limited to any specific combination of hardware and software.
  • the charging method and the charging system disclosed in the present application meet the management requirements for convenient charging for terminals of different platforms, save billing time, improve billing efficiency, and improve user experience.

Landscapes

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

Abstract

本申请公开了一种计费方法和计费系统，可以根据接收的会话申请获取对应的子账户的信息，根据该信息以及子账户与主账户的对应关系，查询到子账户对应的主账户，然后再根据会话申请对应的会话使用的会话资源对主账户进行计费。相对于相关技术中，对每个终端按照单一手机号码进行计费的方案，通过本申请，不同的终端可以使用不同的子账户发出会话申请，同时，利用一个主账户为多个子账户付费，满足对不同平台的终端进行便捷计费的管理需求。本申请通过一个主账户实现了多个子账户费用管理，节约了计费时间，提高了计费效率，同时，使用本申请，对于用户而言，只对主账户进行缴费即可，有利于提升用户体验。

Description

一种计费方法和计费系统 技术领域
本申请涉及通信领域，例如涉及一种计费方法和计费系统。
背景技术
传统的用户计费业务作为一项较为成熟的增值业务，拥有广泛的用户群体，为运营商带来了丰厚的收益。传统的用户计费业务是通过用户的手机号码作为计费账户，将用户使用的短信、流量、通话时长等信息记录在用户的手机号码上，根据手机号码对应的记录进行缴费。
目前，随着互联网，特别是移动互联网的广泛使用，传统的以单一手机号码为唯一计费账户的方法，使用范围越来越小。互联网时代，需要多平台的呼叫终端，而同一用户可能会使用到多个不同平台的终端，需要对不同平台的终端的上网流量使用情况和通话时长使用情况等信息进行实时统计，如果还是采用传统的用户计费方案根据终端的手机号码进行计费，当用户需要使用多个终端时，需要对用户的每个终端进行计费，用户需根据每个终端的电话号码进行缴费，无论是对统计费用的服务方，还是缴费的用户一方，管理都很繁琐，浪费时间，同时也会降低用户体验。
发明内容
本公开实施例提供一种计费方法和计费系统，解决相关技术中由于采用单一手机号码进行计费，导致的计费管理繁琐，浪费时间，增加用户缴费所需时间，降低用户体验感的问题。
本公开实施例提供一种计费方法，包括：
接收会话申请；
根据会话申请获取对应的子账户的信息；
根据子账户的信息以及预存的子账户和主账户的对应关系，查询子账户对 应的主账户；
根据会话申请对应的会话使用的会话资源对主账户进行计费。
本公开实施例还提供一种计费系统，包括：计费平台和子账户存储实体，子账户存储实体中预存有子账户和主账户的对应关系；
计费平台被配置为接收会话申请，根据会话申请获取对应的子账户的信息，根据子账户的信息从子账户存储实体中查询子账户对应的主账户；并根据会话申请对应的会话使用的会话资源对主账户进行计费。
本公开实施例还提供了一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令设置为执行上述方法。
本公开实施例还提供了一种电子设备，包括：
至少一个处理器；以及
与所述至少一个处理器通信连接的存储器；其中，
所述存储器存储有可被所述至少一个处理器执行的指令，所述指令被所述至少一个处理器执行，以使所述至少一个处理器执行上述的方法。
本公开实施例公开了一种计费方法和计费系统，可以根据接收的会话申请获取对应的子账户的信息，根据该子账户的信息和主账户的对应关系，查询到子账户对应的主账户，然后再根据会话申请对应的会话使用的会话资源对主账户进行计费，由于本公开的子账户的会话使用的会话资源是计入主账户中进行扣费的，不同的终端可以使用不同的子账户发出会话申请，所以本公开可以利用一个主账户为至少一个子账户付费，将多个子账户的计费集中到主账户中进行，满足对不同平台的终端的计费管理需求，相对于相关技术中，对每个终端按照手机号码进行计费，本公开可以在一个主账户中记录多个使用子账户的终端的费用，节约了计费时间，提高了计费效率，同时，使用本公开，用户只对主账户进行缴费即可，有利于提升用户体验。
附图概述
图1为本公开实施例一提供的一种计费方法的流程图；
图2为本公开实施例二提供的一种计费系统的结构图；
图3为本公开实施例二提供的另一种计费系统的结构图；
图4为利用本公开实施例二的计费系统进行主账户和子账户开户的方法流程图；
图5为利用本公开实施例二的计费系统根据会话申请查询主账户的方法的流程图；以及
图6为利用本公开实施例的电子设备的结构示意图。
具体实施方式
下面通过实施方式结合附图对本公开进行详细说明。
实施例一：
参见图1，本实施例提供一种计费方法，包括：
S101、接收会话申请；
S102、根据会话申请获取对应的子账户的信息；
S103、根据子账户的信息以及预存的子账户和主账户的对应关系，查询子账户对应的主账户；
S104、根据会话申请对应的会话使用的会话资源对主账户进行计费。
在实施例中，主账户和子账户之间的对应关系是预先设置的。一般，运营商或服务提供商的计费系统会为用户提供主账户开户业务，用户在开户时，可以获取一个主账户和对应的子账户，其中，在初次开户时，主账户可以携带一个默认的子账户，同时为用户提供设置子账户的功能，由用户根据自身的需要在主账户下设置多个子账户，然后将子账户与主账户的对应关系存储起来以供后续使用。可以预见，为了便于管理，计费系统还可以提供主账户的销户业务、主账户充值业务等业务。进行主账户销户的时候，可以将主账户下的所有子账户删除，还可以将预存的子账户与主账户的对应关系删除。由于子账户的费用是计入主账户统一计费的，所以在进行充值时，只在主账户中充值即可。
在本实施例中，S101中的会话申请可以是某个使用子账户的终端在开始会话之前上报的消息。该终端可以包括手机、平板电脑、联网的对讲机等。
通过上述的介绍可知，子账户与主账户可以是多对一的关系，在同一时刻，可能有多个终端同时使用不同的子账户发起会话申请，本实施例在S102中是根据会话申请获取对应的子账户的信息，区分不同的会话申请所对应的子账户。之后，根据预存的子账户和主账户的对应关系可以快速地查找到子账户对应的主账户的信息，准确对属于不同子账户对应的主账户进行计费。
可以预见，当用户对子账户的需求数量减少时，如果之前的子账户还是保留，预存的子账户的信息就比较多，会占用多余的存储资源，同时为步骤S103中查询子账户对应的主账户带来干扰，降低查找效率，其次，还可能导致子账户信息泄露的概率增加的问题，所以，可以有一定的保护措施，为此，本实施例可以在开通子账户的时候，设置子账户的有效期限，有效期到时，子账户自动失效，可以方便控制子账户的有效使用时长。此外，也可以在子账户的使用过程中对该子账户设置有效期限。
其中，子账户可以在主账户开户时开通，也可以在主账户的使用过程中开通，所以，设置子账户的有效期限的时间，可以是主账户的开户时，也可以在主账户的使用过程中。
上述S103中的子账户和主账户的对应关系读取的效率对本实施例的计费效率有一定影响，为了S103中，能快速地查询出子账户对应的主账户，可以将子账户和主账户的对应关系存储在子账户存储实体中，该子账户存储实体采用高效的存储和读取操作。其中，在获取子账户的信息后，可以通过携带子账户信息的消息的方式到子账户存储实体中查询对应的主账户。由子账户存储实体返回对应于子账户的信息的主账户。
其中，每个会话申请对应的会话从开始到结束会使用一定的会话资源，在本实施例中，对主账户进行计费，实际上就是根据主账户的子账户发起的会话使用的会话资源进行计费。
本实施例的会话资源可以包括通话时长片和上网流量片等。此外，本实施例的会话资源还可以包括在会话使用的其他资源，如短信等。
可以预见，一般，主账户的付费方式包括以下两种：预付费和后付费：如 果采用预付费方式，则主账户中会有相应的预存套餐，套餐中可以包括一定数量的通话时长和上网流量。此时，步骤S104中，根据会话申请对应的会话使用的会话资源对主账户进行计费时，可以从主账户中的套餐中扣除会话申请对应的会话使用的会话资源，从而对主账户计费。
如果采用后付费的方式，主账户中一般不会有套餐，会话资源会按照一定的标准进行收费，例如将上网流量按照以M或Hz为单位进行收费，或者将通话时长以分钟为单位进行收费。此时，步骤S104中，根据会话申请对应的会话使用的会话资源对主账户进行计费时，可以对子账户的会话申请对应的会话使用的会话资源按照相应的标准，换算为费用，计入主账户的扣费情况中。
一般采用先付费的方式进行计费，当主账户具有会话资源时，在步骤S104之前，还可以包括根据主账户的会话资源剩余情况为会话申请对应的会话分配相应的会话资源。
在为子账户的会话进行会话资源的分配时，可以按照预设的分配规则进行，预设的分配规则包括：每次分配固定大小的上网流量片或固定时间长度的通话时长给会话申请对应的会话；或者，根据主账户中的会话资源的剩余情况，每次分配主账户中当前剩余的会话资源的1/10给子账户的会话。
此外，本实施例的会话申请中还可以携带要求的会话资源数量，根据主账户的会话资源剩余情况为会话申请对应的会话分配相应的会话资源包括：在主账户的剩余会话资源中，为会话申请对应的会话分配该会话申请要求的会话资源。
可以预见，当主账户中的剩余的会话资源不足，无法满足当前的会话申请的分配需求，即主账户剩余的会话资源不够分配一次通话时长片或上网流量片时，向发起会话的终端返回会话申请失败的消息，告知本次会话申请失败。避免用户由于不知道上网掉线或通话断线的原因造成的损失。
在本实例中，分配相应的会话资源包括分配相应的通话时长片或上网流量片。其中，可以理解的是，为一次会话申请分配的会话资源可能不够本次会话的使用，此时，进行该会话的终端，可以再次上报会话申请，为该会话获取新的通话时长片或上网流量片。由此，当会话对应的会话申请有多个的时候，可以分为初次会话申请和后续会话申请，当会话申请为初次会话申请的时候，该 会话申请对应的会话还未使用会话资源，从此时开始对会话使用的会话资源进行统计。
其中，不同的会话要求的会话资源的类型可能不同，例如，有的会话要求的会话资源是上网流量，有的会话要求的会话资源是通话时长，而不同类型的会话资源，计费单位和计费标准都不同，所以可以对不同会话的会话资源分开进行统计。同时，需要相同类型的会话资源的多个会话，最终对应的主账户可能不同，为了能对不同的主账户准确计费，可以将不同会话的会话资源分开统计。
鉴于此，本实施例在接收到初次会话申请时，获取该初次会话申请对应的会话的会话标识，其中，不同会话的会话标识不同。该会话标识可以由接收到会话申请的设备或平台为会话设置，也可以由每一次的会话申请自身携带，本实施例对此不作限定。
在获取会话标识之后，对会话的会话资源的统计就变得更加简单了。在每一次为会话申请对应的会话分配了会话资源后，根据该会话标识对同一会话分配的会话资源进行累加。
其中，当该会话申请为初始会话申请时，可以根据会话标识记录本次分配的会话资源即可，例如，本次的会话标识为*908，为本次会话申请分配的会话资源为5min的通话时长，则将*908和5min对应记录，建立这两个数据之间的对应关系。
当本次的会话还需要申请新的会话资源时，对应的终端继续上报会话申请，获取新的会话资源，此时，可以根据该会话申请对应的会话标识，对同一会话分配的会话资源进行累加，例如，接收到的会话申请对应的会话的会话标识为*908，为该会话申请对应的会话分配的会话资源为5min的通话时长，则根据此次会话申请的会话标识*908，找到之前的记录，将*908对应的5min累加到10min。表明此次分配后，为该会话申请对应的会话分配的会话资源累计为10min通话时长。
当本次的会话终止时，就不再进行会话资源的分配，可以预见，在会话终止时，本次分配的会话资源可能会有剩余，为了能够实时统计主账户的会话资源的剩余情况，一般可以将最后一次为会话分配的未使用完毕的会话资源返回 主账户中。此时，根据会话标识记录的会话使用的会话资源可进行相应的修改：在基于根据会话标识累加的会话资源，对主账户进行计费前，根据未使用完毕的会话资源更新根据会话标识累加的会话资源。
其中，根据未使用完毕的会话资源更新根据会话标识累加的会话资源，实际上就是在根据会话标识累加的会话资源中减去未使用完毕的会话资源。
此时根据会话标识累加的会话资源就是会话申请对应的会话使用的会话资源，步骤S104中，可以根据该累加的会话资源对主账户进行计费。
采用本实施例的计费方法，可以根据接收的会话申请获取对应的子账户的信息，在基于该信息根据预存的子账户与主账户的对应关系，查询到子账户对应的主账户，然后再根据会话申请对应的会话使用的会话资源对主账户进行计费，通过本实施例，不同的终端可以使用不同的子账户发出会话申请，由一个主账户为多个子账户付费，满足对不同平台的终端的计费管理需求，相对于相关技术中，对每个终端按照手机号码进行计费，本公开可以在一个主账户中记录多个使用子账户的终端的费用，节约了计费时间，提高了计费效率，同时，使用本公开，用户只对主账户进行缴费即可，有利于提升用户体验。
获取每个会话的会话标识，根据会话标识记录为不同会话分配的会话资源，可以确保在具有多个会话时，能准确地对每一个会话进行会话资源的统计，确保主账户的计费准确，确保实现多会话计费。
为子账户设置有效期，可以有效降低子账户对子账户存储实体资源的占用率，提高查询主账户的查询效率，提高计费效率。
实施例二：
参见图2，本实施例提供一种计费系统，包括计费平台21和子账户存储实体22；子账户存储实体中预存有子账户和主账户的对应关系；计费平台被配置为接收会话申请，根据会话申请获取对应的子账户的信息，根据子账户的信息从子账户存储实体中查询子账户对应的主账户；并根据会话申请对应的会话使用的会话资源对主账户进行计费。
考虑到子账户和主账户的对应关系读取的效率对本实施例的计费效率有一定影响，为了能快速地从子账户存储实体中查询出子账户对应的主账户，子账 户存储实体采用高效的存储和读取操作。可以理解的是，本实施例的主账户的信息可以存储在计费平台上。
在实施例中，主账户和子账户之间的对应关系是预先设置的。为了便于对主账户开户、设置和管理等处理，参见图3，本实施例还提供运营支撑平台23，该运营支撑平台23由运营商的业务支撑系统提供，完成用户的主账户和子账户的开户、销户、主账户充值、子账户查询功能。其中，用户对主账户和子账户的开户、销户、充值以及子账户查询可以通过短信与运营支撑平台23进行信息交互实现。此外，运营支撑平台23可以为用户提供用户界面，用户通过在用户界面上进行相应的操作实现主账户和子账户的开户、销户、主账户充值以及对子账户的查询。
其中，运营支撑平台23与计费平台21连接，计费平台21接收用户通过运营支撑平台上报的主账户和子账户的开户、销户等信息，完成用户对主账户和子账户的开户、销户等工作。
其中，用户在进行主账户开户时，运营支撑平台23可以为一个主账户提供默认数量的子账户，这里的默认数量一般为一个。运营支撑平台23为用户提供了设置子账户的功能，由用户根据自身的需要在主账户下设置多个子账户，由运营支撑平台将设置的数据传输到计费平台21，由计费平台21对子账户和主账户的对应关系进行确定。
参见图4，利用本公开的计费系统进行多子账户开户的方法包括：
S401、用户在运营支撑平台上完成子账户和多个子账户的设置，运营支撑平台向计费平台发送开户消息。
其中开户消息包括了主账户和子账户的开户信息。
S402、计费平台接收到运营支撑平台的开户消息请求后，完成主账户的开户。
S403、计费平台循环处理所有的子账户，在子账户存储实体中增加该子账户与主账户的对应关系。
当用户要进行主账户销户的时候，通过运营支撑平台23将主账户下的所有子账户删除，将主账户删除。计费平台21根据运营支撑平台返回的主账户删除信息，删除计费平台上的主账户信息，并控制子账户存储实体22删除预存的子 账户与主账户的对应关系。
可以预见，当用户对子账户的需求数量减少时，如果之前的子账户还是保留，预存的子账户的信息就比较多，会占用多余的存储资源，同时为查询子账户对应的主账户带来干扰，降低查找效率，其次，还可能导致子账户信息泄露的概率增加的问题，所以，可以有一定的保护措施，为此，本实施例可以在开通子账户的时候，设置子账户的有效期限，有效期到时，子账户自动失效，可以方便控制子账户的有效使用时长。此外，也可以在子账户的使用过程中对该子账户设置有效期限。
在本实施例中，会话申请可以是某个使用子账户的终端在开始会话之前上报的消息。该终端可以包括手机、平板电脑、联网的对讲机等。
本实施例的会话资源可以包括通话时长片或上网流量片等。
参见图5，示出了利用本实施例的计费系统，根据会话申请最终查询到主账户的方法，包括：
S501、终端发起申请通话时长片或上网流量片的会话申请。
S502、计费平台解析出会话申请对应的子账户的信息。
S503、计费平台根据子账户的信息到子账户存储实体中查询出主账户信息。
可以预见，一般，主账户的付费方式包括以下两种：预付费和后付费：如果采用预付费方式，则主账户中会有相应的预存套餐，套餐中可以包括一定数量的通话时长和上网流量。计费平台21根据会话申请对应的会话使用的会话资源对主账户进行计费时，可以从主账户中的套餐中扣除会话申请对应的会话使用的会话资源，从而对主账户计费。
如果采用后付费的方式，主账户中一般不会有套餐，会话资源会按照一定的标准进行收费，例如将上网流量按照以M或Hz为单位进行收费，或者将通话时长以分钟为单位进行收费。计费平台21根据会话申请对应的会话使用的会话资源对主账户进行计费时，可以对子账户的会话申请对应的会话使用的会话资源按照相应的标准，换算为费用，计入主账户的扣费情况中。
一般采用先付费的方式进行计费，即主账户中具有会话资源。此时，可以有一定的控制策略对会话的会话资源使用情况进行控制。
本实施例中的计费系统还可以包括资源控制实体24，该资源控制实体24接收用户终端上报的会话申请，并向计费平台21上报会话申请请求会话资源，计费平台21根据主账户的会话资源的剩余情况为子账户的会话分配相应的会话资源，向资源控制实体24返回分配的会话资源的数值，由资源控制实体24根据数值控制对会话使用的会话资源进行控制。
可以预见，当某次为会话分配的会话资源使用完毕，而进行该会话的终端没有上报会话申请要求再次分配会话资源时，资源控制实体24可以进行相应的处理，例如，切断终端当前的会话，提醒终端会话资源不足等信息。或者，资源控制实体24可以根据计费平台21对本次会话返回的会话资源的数值，实时监测会本次话对应剩余的会话资源，在会话资源将耗尽的时候，提醒用户当前的会话资源不足，需要进行新的会话申请，避免用户中断会话。
不同的会话要求的会话资源的类型可能不同，例如，有的会话要求的会话资源是上网流量，有的会话要求的会话资源是通话时长，而不同类型的会话资源，计费单位和计费标准都不同，所以可以对不同会话的会话资源分开进行统计。同时，会话资源类型相同的多个会话，最终对应的主账户可能不同，为了能对不同的主账户准确计费，可以将不同会话的会话资源分开统计。
鉴于此，本实施例的计费平台21还被配置为在接收到初次会话申请时，获取该初次会话申请对应的会话的会话标识，其中，不同会话的会话标识不同。该会话标识可以由计费平台21为会话设置，也可以由每一次的会话申请自身携带，本实施例对此不作限定。
在获取会话标识之后，计费平台21对会话的会话资源的统计就变得简单了。在每一次为会话申请对应的会话分配了会话资源后，基于为会话分配的会话资源，根据该会话标识对同一会话分配的会话资源进行累加，之后，基于根据会话标识累加的会话资源，对主账户进行计费。其中，根据该会话标识对同一会话分配的会话资源进行累加的过程可以参考实施例一的相关介绍，本实施例不再赘述。
当一次的会话终止时，就不再进行会话资源的分配，可以预见，在会话终止时，分配的会话资源可能会有剩余，为了能够实时统计主账户的会话资源的剩余情况，一般可以将最后一次为会话分配的未使用完毕的会话资源返回主账 户中。本实施例中，由资源控制实体24将最后一次为会话分配的未使用完毕的会话资源的剩余值告知计费平台21。由计费平台21将未使用完毕的会话资源返回主账户，并在基于根据会话标识累加的会话资源，对主账户进行计费前，根据未使用完毕的会话资源更新根据会话标识累加的会话资源。
其中，根据未使用完毕的会话资源更新根据会话标识累加的会话资源，实际上就是在根据会话标识累加的会话资源中减去未使用完毕的会话资源。此时根据会话标识累加的会话资源就是会话申请对应的会话使用的会话资源。
采用本实施例的计费系统，计费平台可以接收会话申请，根据会话申请得到对应的子账户的信息，然后从子账户存储实体中查询到主账户，根据子账户的会话使用的会话资源对主账户进行计费。通过计费平台的处理，在一个主账户中，实现多个子账户的计费。当不同平台的终端进行会话时，采用本实施例，不同平台的终端可以使用同一主账户的子账户，通过对主账户计费，即可完成对子账户的付费。
计费平台根据主账户剩余的会话资源为会话分配会话资源，有利于控制子账户使用的会话资源，有利于降低计算子账户使用的会话资源的难度，简化对子账户的会话资源的统计过程，简化对主账户计费过程。
本公开实施例还提供了一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令设置为执行上述任一实施例中的方法。
所述计算机可读存储介质可以是暂态计算机可读存储介质，也可以是非暂态计算机可读存储介质。
本公开实施例还提供了一种电子设备的结构示意图。参见图6，该电子设备包括：
至少一个处理器(processor)60，图6中以一个处理器60为例；和存储器(memory)61，还可以包括通信接口(Communications Interface)62和总线63。其中，处理器60、通信接口62、存储器61可以通过总线63完成相互间的通信。通信接口62可以用于信息传输。处理器60可以调用存储器61中的逻辑指令，以执 行上述实施例的方法。
此外，上述的存储器61中的逻辑指令可以通过软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。
存储器61作为一种计算机可读存储介质，可用于存储软件程序、计算机可执行程序，如本公开实施例中的方法对应的程序指令/模块。处理器60通过运行存储在存储器61中的软件程序、指令以及模块，从而执行功能应用以及数据处理，即实现上述方法实施例中的计费方法。
存储器61可包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需的应用程序；存储数据区可存储根据终端设备的使用所创建的数据等。此外，存储器61可以包括高速随机存取存储器，还可以包括非易失性存储器。
本公开实施例的技术方案可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括一个或多个指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本公开实施例所述方法的全部或部分步骤。而前述的存储介质可以是非暂态存储介质，包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等多种可以存储程序代码的介质，也可以是暂态存储介质。
上述本公开的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储介质(ROM/RAM、磁碟、光盘)中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。所以，本公开不限制于任何特定的硬件和软件结合。
以上内容是结合实施方式对本公开所作的详细说明，不能认定本公开的实 施只局限于这些说明。对于本公开所属技术领域的普通技术人员来说，在不脱离本公开实施例的范围的前提下，还可以做出若干简单推演或替换，都应当视为属于本公开的保护范围。
工业实用性
本申请公开的计费方法和计费系统，满足对不同平台的终端进行便捷计费的管理需求，节约了计费时间，提高了计费效率，还有利于提升用户体验。

Claims (12)

  1. 一种计费方法，包括：
    接收会话申请；
    根据所述会话申请获取对应的子账户的信息；
    根据所述子账户的信息以及预存的子账户和主账户的对应关系，查询所述子账户对应的主账户；
    根据所述会话申请对应的会话使用的会话资源对所述主账户进行计费。
  2. 如权利要求1所述的方法，其中，所述会话资源包括：通话时长片或上网流量片。
  3. 如权利要求1所述的方法，还包括：在所述主账户中开通子账户时，为所述子账户设置有效期。
  4. 如权利要求1所述的方法，其中，所述子账户和主账户的对应关系预存在子账户存储实体上，所述子账户存储实体采用高效的存储和读取操作。
  5. 如权利要求1-4任一项所述的方法，其中，在根据所述子账户的信息以及预存的子账户和主账户的对应关系，查询所述子账户对应的主账户后，还包括：
    根据所述主账户的会话资源的剩余情况为会话申请对应的会话分配相应的会话资源。
  6. 如权利要求5所述的方法，还包括：在接收到初次会话申请时，获取所述初次会话申请对应的会话的会话标识；
    所述根据所述会话申请对应的会话使用的会话资源对所述主账户进行计费包括：
    基于为所述会话分配的会话资源，根据所述会话标识对所述会话分配的会话资源进行累加；
    基于根据所述会话标识累加的会话资源，对所述主账户进行计费。
  7. 如权利要求6所述的方法，还包括：将最后一次为所述会话分配的未使 用完毕的会话资源返回所述主账户中；
    在基于根据所述会话标识累加的会话资源，对所述主账户进行计费前，还包括：
    根据所述未使用完毕的会话资源更新根据所述会话标识累加的会话资源。
  8. 一种计费系统，包括：计费平台和子账户存储实体，所述子账户存储实体中预存有子账户和主账户的对应关系；
    所述计费平台被配置为接收会话申请，根据所述会话申请获取对应的子账户的信息，根据所述子账户的信息从所述子账户存储实体中查询所述子账户对应的主账户；并根据所述会话申请对应的会话使用的会话资源对所述主账户进行计费。
  9. 如权利要求8所述的系统，还包括资源控制实体，所述资源控制实体被配置为向所述计费平台上报所述会话申请请求会话资源，所述计费平台根据主账户的会话资源的剩余情况为所述子账户的所述会话分配相应的会话资源，向所述资源控制实体返回分配的会话资源的数值，由所述资源控制实体根据所述数值对所述会话使用的会话资源进行控制。
  10. 如权利要求9所述的系统，其中，所述计费平台还被配置为在接收到初次会话申请时，获取所述初次会话申请对应的会话的会话标识；基于为所述会话分配的会话资源，根据所述会话标识对所述会话分配的会话资源进行累加；基于根据所述会话标识累加的会话资源，对所述主账户进行计费。
  11. 如权利要求10所述的系统，其中，所述资源控制实体还被配置为将最后一次为所述会话分配的未使用完毕的会话资源的剩余值告知所述计费平台，所述计费平台被配置为将未使用完毕的会话资源返回所述主账户，并在基于根据所述会话标识累加的会话资源，对所述主账户进行计费前，根据所述未使用完毕的会话资源更新根据所述会话标识累加的会话资源。
  12. 一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令设置为执行权利要求1-7中任一项的方法。
PCT/CN2017/089765 2016-06-29 2017-06-23 一种计费方法和计费系统 WO2018001181A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610494964.5A CN107547762A (zh) 2016-06-29 2016-06-29 一种计费方法和计费系统
CN201610494964.5 2016-06-29

Publications (1)

Publication Number Publication Date
WO2018001181A1 true WO2018001181A1 (zh) 2018-01-04

Family

ID=60785071

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/089765 WO2018001181A1 (zh) 2016-06-29 2017-06-23 一种计费方法和计费系统

Country Status (2)

Country Link
CN (1) CN107547762A (zh)
WO (1) WO2018001181A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113242303A (zh) * 2021-05-12 2021-08-10 北京京东拓先科技有限公司 会话处理方法、装置、电子设备、系统和存储介质
CN114257463A (zh) * 2020-09-11 2022-03-29 北京金山云网络技术有限公司 一种计费方法、装置、电子设备和计算机可读存储介质

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110417561B (zh) * 2018-04-28 2021-10-15 华为技术有限公司 一种基于区块链的分布式计费方法、装置和系统
CN112669025B (zh) * 2020-12-24 2021-07-16 广西中科曙光云计算有限公司 一种数据资源供给计费方法、装置、介质及终端设备
CN112667399A (zh) * 2020-12-28 2021-04-16 紫光云技术有限公司 一种云平台主子账号资源管理的方法
CN113674476A (zh) * 2021-07-19 2021-11-19 康大创新(广东)科技有限公司 基于账户共享的饮水机取水方法、系统及可读存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101345634A (zh) * 2008-08-15 2009-01-14 华为技术有限公司 计费方法、计费装置和计费系统
CN101998344A (zh) * 2009-08-20 2011-03-30 中国移动通信集团辽宁有限公司 多用户计费的方法及装置
US20140004821A1 (en) * 2012-06-29 2014-01-02 Telefonaktiebolaget L M Ericsson (Publ) Telecommunications charging with externally-controlled account selection
CN104378750A (zh) * 2013-08-16 2015-02-25 中国移动通信集团广东有限公司 一种多终端共享账户余额的计费方法和系统

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1330164C (zh) * 2002-03-13 2007-08-01 华为技术有限公司 手机计费扣费方法
CN1842116A (zh) * 2005-03-28 2006-10-04 华为技术有限公司 一种预付费共用账户实现方法
US9143622B2 (en) * 2006-02-17 2015-09-22 Qualcomm Incorporated Prepay accounts for applications, services and content for communication devices
CN101193175A (zh) * 2006-11-28 2008-06-04 中兴通讯股份有限公司 共用帐户金额管理方法
CN102843668A (zh) * 2012-06-28 2012-12-26 北京得实达康系统集成有限公司 一种实现多个移动终端卡共享流量的方法和系统
CN103826214B (zh) * 2014-03-04 2017-07-14 中国联合网络通信集团有限公司 智能计费方法及服务器

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101345634A (zh) * 2008-08-15 2009-01-14 华为技术有限公司 计费方法、计费装置和计费系统
CN101998344A (zh) * 2009-08-20 2011-03-30 中国移动通信集团辽宁有限公司 多用户计费的方法及装置
US20140004821A1 (en) * 2012-06-29 2014-01-02 Telefonaktiebolaget L M Ericsson (Publ) Telecommunications charging with externally-controlled account selection
CN104378750A (zh) * 2013-08-16 2015-02-25 中国移动通信集团广东有限公司 一种多终端共享账户余额的计费方法和系统

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114257463A (zh) * 2020-09-11 2022-03-29 北京金山云网络技术有限公司 一种计费方法、装置、电子设备和计算机可读存储介质
CN113242303A (zh) * 2021-05-12 2021-08-10 北京京东拓先科技有限公司 会话处理方法、装置、电子设备、系统和存储介质
CN113242303B (zh) * 2021-05-12 2023-04-18 北京京东拓先科技有限公司 会话处理方法、装置、电子设备、系统和存储介质

Also Published As

Publication number Publication date
CN107547762A (zh) 2018-01-05

Similar Documents

Publication Publication Date Title
WO2018001181A1 (zh) 一种计费方法和计费系统
KR101160377B1 (ko) 가입자에 대한 통합식 선불 과금 및 후불 과금 제공 통신 네트워크, 방법 및 통신 네트워크의 과금 선택 시스템
US7860762B2 (en) Charging system and charging method
RU2407182C2 (ru) Wap-шлюз и способ осуществления управления биллингом для абонентов тарифа с предоплатой
CN101132289B (zh) 融合计费方法及计费系统及应用服务器及融合计费系统
RU2491632C1 (ru) Система и способ предоставления дополнительной платной услуги
WO2016188020A1 (zh) 流量管理方法、装置、系统、终端及计算机存储介质
SG173513A1 (en) An online charging method and system based on user's traffic
EP3282729B1 (en) Policy and charging execution function device and method, online charging device and method
US11470202B2 (en) Charging method, apparatus, and system
WO2009100669A1 (zh) 计费方法、控制装置、计费装置与计费系统
CN110381455B (zh) 流量监控处理方法和相关装置和系统
US20100145838A1 (en) Method, system, and apparatus for opening accounting data capabilities
US20160150396A1 (en) System and method for tracking communications network resources and utilizing non-reusable, obligated network resources to support the communications network resources
CN108076477A (zh) 一种数据流量监控方法、装置及系统
CN102291704B (zh) 计费方法、计费设备、交换设备和计费系统
CN1859132A (zh) 一种分组数据预付费业务实现方法
CN101562775B (zh) 实时累计赠送的预付费智能网业务的实现方法及系统
CN109547956B (zh) 一种多业务并发处理方法
CN103607707A (zh) 基于反算计费的资源分配方法及装置
CN110324153A (zh) 计费方法以及系统
CN112153585B (zh) 一种计费系统、方法、存储介质及电子装置
WO2020207280A1 (zh) 资源计费方法、mec管理系统和mec主机
KR20130039394A (ko) 가입자 데이터 할당 시스템 및 그 방법
CN108270580B (zh) 在线计费的提醒方法、设备及系统

Legal Events

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

Ref document number: 17819178

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17819178

Country of ref document: EP

Kind code of ref document: A1