WO2007124644A1 - An accounting method, apparatus and system based on roles in the business of push-to-talk over cellular - Google Patents

An accounting method, apparatus and system based on roles in the business of push-to-talk over cellular Download PDF

Info

Publication number
WO2007124644A1
WO2007124644A1 PCT/CN2007/000571 CN2007000571W WO2007124644A1 WO 2007124644 A1 WO2007124644 A1 WO 2007124644A1 CN 2007000571 W CN2007000571 W CN 2007000571W WO 2007124644 A1 WO2007124644 A1 WO 2007124644A1
Authority
WO
WIPO (PCT)
Prior art keywords
charging
role
request
session
user
Prior art date
Application number
PCT/CN2007/000571
Other languages
English (en)
French (fr)
Inventor
Dong Zhao
Aiqin Zhang
Original Assignee
Huawei Technologies Co., Ltd.
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 Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Priority to EP07710989.0A priority Critical patent/EP2009840B1/en
Publication of WO2007124644A1 publication Critical patent/WO2007124644A1/zh

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/02Details
    • H04L12/14Charging, metering or billing arrangements for data wireline or wireless communications
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/02Details
    • H04L12/14Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1485Tariff-related aspects
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/43Billing software details
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/56Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP for VoIP communications
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/82Criteria or parameters used for performing billing operations
    • H04M15/8228Session based
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24Accounting or billing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/40Connection management for selective distribution or broadcast
    • H04W76/45Connection management for selective distribution or broadcast for Push-to-Talk [PTT] or Push-to-Talk over cellular [PoC] services
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2215/00Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/20Technology dependant metering
    • H04M2215/202VoIP; Packet switched telephony
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2215/00Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/20Technology dependant metering
    • H04M2215/2026Wireless network, e.g. GSM, PCS, TACS
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2215/00Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/20Technology dependant metering
    • H04M2215/2093Push to talk
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2215/00Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/78Metric aspects
    • H04M2215/7833Session based
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H04W4/10Push-to-Talk [PTT] or Push-On-Call services

Definitions

  • the present invention relates to billing techniques in the field of communications, and more particularly to a method, apparatus and system for role-based billing in push-to-talk services. Background technique
  • the Push to Talk over Cellular (PoC) service is a cluster-based media communication service based on IP technology. It uses a bearer network to implement half-duplex VoIP technology. After setting the group list, PoC users can perform point-to-point and point-to-multipoint half-duplex calls with other PoC users.
  • the PoC service system is shown in Figure 1A.
  • the Controlling PoC Function is the core part of communication. It is used for centralized control.
  • the execution includes session control (establish/cancel session, signaling and media). Functions such as negotiation, processing of requests, communication control such as distribution of media streams, group policy enforcement (including collection and control of QoS), and user plane adaptation.
  • Each client (Client) corresponds to a Participant PoC Function (PPF).
  • PPF Participant PoC Function
  • Each PPF performs a session operation to send a request to the CPF.
  • the CPF coordinates the control of the session process (such as media distribution, data transfer, permission, and role transfer). , QoE certification, etc.).
  • the client that joins the session communicates with the CPF through the PPF and receives the CPF command.
  • the CPF distributes the media and data to the PPF according to the policy. Afterwards, each PPF forwards the packet to the corresponding connected client, and completes the point/point between the clients. Communication to multiple points.
  • CPF and EPF are functional modules. They can exist on one PoC server or on different PoC servers.
  • a client is a functional entity that a PoC user joins a session.
  • the role is one of the attributes of the PoC user, and the PoC user can form a PoC group.
  • the current PoC user roles are: Regular PoC Participant, PoC Dispatcher, PoC Moderator, fleet member, etc. The role is still being supplemented.
  • the charging of the PoC is to charge the PPF and the CPF separately, and is divided into offline charging and online charging.
  • the offline charging module is called CDF
  • the online charging module is called OCS.
  • the main process of the PoC charging is as follows:
  • the charging object triggers the charging request due to the event, and carries the required data parameters, which are sent to the charging module (CDF or OCS); the charging module performs charging processing according to this parameter.
  • the user account data will be affected; after the billing process is completed, the billing module returns the operation result to the billed object.
  • CDF charging module
  • OCS charging module
  • Embodiments of the present invention provide a role-based charging method, apparatus, and system in a push-to-talk (PoC) service to perform differentiated charging for different user roles.
  • PoC push-to-talk
  • a role-based charging method in a push-to-talk service including the following steps:
  • the PoC server sends a charging request to the charging function entity, and carries related information of the user role in the request;
  • the charging function entity After receiving the request, the charging function entity selects a charging policy by referring to the related information, performs charging processing according to the selected charging policy, and returns an accounting response to the PoC server.
  • a PoC server including:
  • a charging device comprising:
  • a module for returning a charging response to a sending charging requestor is provided.
  • a communication system comprising:
  • a PoC server configured to send a charging request that carries related information of a user role;
  • the charging function entity is configured to receive the charging request and refer to related information of the user role therein to select a charging policy, perform charging processing according to the selected charging policy, and return a charging response to the PoC server.
  • the charging request carries the related information of the user role
  • the charging function entity selects the charging policy according to the information about the user role, so that differentiated charging can be provided for different user roles.
  • FIG. 1A is a schematic structural diagram of a PoC service system in the prior art
  • 1B is a schematic diagram of relationships between entities in a PoC communication in the prior art
  • FIG. 3 is a flow chart of charging according to a role of establishing/joining a PoC session according to an embodiment of the present invention
  • FIG. 4 is a schematic diagram showing relationship between components of a user and a role according to an embodiment of the present invention
  • FIG. 5 is a flowchart of offline charging according to an embodiment of the present invention.
  • FIG. 6 is a flowchart of online charging in an embodiment of the present invention. . detailed description
  • the embodiment of the present invention considers the user role in the executed charging policy, thereby providing differentiated charging.
  • the Controlling PoC Function (CPF) and the PPC (Participation PoC Function) are stored in the same PoC server (which can also exist in different PoC servers).
  • the PoC server can establish a session.
  • the charging operation is triggered during the joining session, the session update, or the end session, and the charging function is sent to the charging function entity, where the request carries the information about the PoC user role.
  • the related information may be part of the role information, such as: role identifier, role ID, non-role information related to the role (such as user name, ID, etc.), role validity period, part or all of the information related to the role-related function identifier, etc. Can be the details of the character Information.
  • the charging function entity stores the charging policy for different roles. After receiving the charging request, the charging policy is selected according to the related information of the user role, and the charging process is performed according to the policy. The charging process may be charging or not.
  • the same PoC user may have more than one role (the roles cannot be mutually exclusive), each role has different operations, rights, and levels, and the charging function entity performs different charging policies on this, and generates corresponding Billing Data Record (CDR).
  • a role feature can contain a variety of content, such as role flags, permissions, levels, scope of operations, etc., which are associated with billing policies and billing methods. Roles and their characteristics can be recorded anywhere in the PoC user, and they can be distributed and recorded. For example, it is recorded in the Group attribute in the XML Document Management Server (XDMS), on the running PoC server or on the Poc client; when it is saved on the PoC server, it may exist on its corresponding PPF, or it may exist. On the CPF, or both.
  • XDMS XML Document Management Server
  • the PoC server can obtain information about the user's role in various ways, such as:
  • the PoC server directly obtains role information from the sent SIP INVITE.
  • the PoC server obtains role information from an external server such as XDMS by the Client user ID/role ID in the SIP INVITE.
  • the PoC server determines the role assigned to a PoC user according to the current situation and the combined context information.
  • the PoC server and Chargingtreatment entity in Figure 2 indicates the functional meaning, and does not indicate the number of functions. There may be multiple PoC servers and charging function entities.
  • the PPF/CPF includes: a module for obtaining related information of a user role, a module for transmitting a charging request including the related information to a charging function entity, and receiving a charging response. Module. That is, the PPF/CPF can send charging requests to different charging function entities.
  • the charging function entity includes: a module for receiving a charging request including related information of a user role; and a mode for selecting a charging policy for charging by referring to the related information. a block; and means for returning a charging response to the sending charging requestor.
  • Step 300 The PoC server receives a SIP request (INVITE) to establish/join a PoC session.
  • the SIP request source may be diverse, such as: the PoC server receives the request sent from the PoC client; or the request sent by the other server to the PoC server; or the PoC server internally triggers and generates the SIP request according to the current situation. .
  • Step 310 PoC server session processing: The PoC server obtains role information from the INVITE information, and performs role-related processing (for example, after the role identification and the authentication are passed, the session type matching the role type is established, and the corresponding attribute is set and the like. ), concurrent session processing (such as issuing a session invitation to other users).
  • role-related processing for example, after the role identification and the authentication are passed, the session type matching the role type is established, and the corresponding attribute is set and the like.
  • concurrent session processing such as issuing a session invitation to other users.
  • the related information of the invited user role is carried in the response message 200 OK.
  • Step 320 The PoC server sends a charging request (Charging Request) carrying the related information of the user role to the Charging Function entity, that is, the request is role related.
  • Charging Request a charging request carrying the related information of the user role to the Charging Function entity, that is, the request is role related.
  • Step 330 After receiving the charging request of the PoC server, the charging function entity selects an accounting policy by referring to the related information of the user role, and starts charging according to the charging policy.
  • role-related information is not the only factor that uniquely determines the billing selection strategy, but needs to be considered in the role-related billing strategy selection.
  • the accounting policy can be flexibly customized according to requirements.
  • a charging policy determines the rate by role and time.
  • the specific charging policy can be as follows:
  • the user role is A, in the time period, corresponding to the rate A1; the role is B, in the period a, the corresponding rate B1; the role is A, in the period b, corresponding to free (or no rate, directly free) deal with).
  • Step 340 The charging function entity returns a Charging Respone to the PoC server.
  • Step 350 After the session is successfully established, perform other session operations.
  • step 330 a series of operations may be performed because the PoC server accepts SIP messages fed back by multiple invited users, each of which causes the PPF and CPF to generate corresponding charging requests (and PPF and CPF charging processing). It is also different, CPF will continue to update this operation).
  • the charging process during the session update process and the end session is the same as step 320 to step 340 in the above process.
  • the related information of the user role is carried by a role information structure capable of indicating multi-user and multi-role.
  • a role information structure capable of indicating multi-user and multi-role.
  • it is represented by a group of [user ⁇ -> multi-role information] ( [Users-roles] ]).
  • a user role information structure indicates that there are multiple users; each user has multiple roles, and each role has multiple related information fields.
  • Figure 4 The specific information structure relationship description is shown in Figure 4, where:
  • A, 1 [Users-roles] is the user role information structure, which consists of [0..*) (ie 0 to more) [user-role].
  • 0 role means: if the session is owned by the session owner
  • Each [User-role] can contain [0..*] role information [Role-info]. This field is empty when a user joining a session has no role or policy to ignore role information.
  • the role information consists of [0..*] role information units (ie at least one). This field can be changed depending on the role.
  • the content is expanded by role, such as the operation, authority, scope, and effective time of the role.
  • the 0 information element indicates that the user has a role, but the role is the default information or the policy requires that the role information be ignored.
  • Fig. 4 mainly describes the mutual relationship of the components constituting the character, and the implementation is not limited to this form.
  • User-role and Role-info can be implicit or display.
  • Explicit representation means every Each of the described data units is explicitly declared and represents the method of their relationship; implicit representation refers to a non-explicit representation, ie, separate data structures such as User-role and/or Role-info will be used, eight, B, C
  • the method described in the relationship described such as a formal description of a data table.
  • the role information structure [Users-Roles]) saves all the participant role information of the CPF-controlled session, and the information group is continuously updated as the user joins; there is a mechanism to initiate the situation to the charging function. Requests, create corresponding incomplete CDR records (Partial CDRs) (which will be merged later), documenting this change and its impact on the billing strategy.
  • the user information is saved in the role information structure ([Users-Roles]).
  • the role information structure [Users-Roles]
  • the charging may be offline charging (Offline Charging) or online charging; for online charging, the session-based resource reserved charging (SCUR) or the event-based resource reserved charging (ECUR) to achieve.
  • offline charging Offline Charging
  • SCUR session-based resource reserved charging
  • ECUR event-based resource reserved charging
  • Step 500 The PoC server receives the request SIP INVITE, and establishes/joins the PoC session.
  • Step 510 The PoC server performs role related information processing and performs session control.
  • Step 520 The PoC server sends a role-related charging request (ACR[start, Users, Roles Info]) to the counting data function (CDF) entity.
  • ACR[start, Users, Roles Info] a role-related charging request
  • CDF counting data function
  • Step 530 The CDF entity performs a series of processing related to the role, including performing a charging policy according to related information of the user role, and performing a charging policy to generate a PPF-CDR and a PPF-CDR.
  • Step 540 The CDF entity returns a charging response (ACA[start]) to the PoC server (responding to CPF and PPF, respectively).
  • Step 550 The session is successfully established, and the PoC server performs other PoC session operations. Correspondingly, the billing process is completed, and the CDF performs other PoC services.
  • session update process Similar to the billing process for establishing a session, there are session update process and end session process. They are the same as the process shown in Figure 5, but the billing request message is different: ACR [Interim, Users used in the update process) , Roles info]; and the ACR [Stop, Users, Roles info] used in the end process, after the completion of the billing is the end of the session.
  • ACR Interim, Users used in the update process
  • Roles info Roles info
  • ACR Interim, Users, Roles info
  • the last [user-role] information can be recorded, but due to the role operation, there will be billing triggered by the event, and the details of the role operation will be recorded.
  • Step 600 The PoC server receives the request SIP INVITE, and establishes/joins the PoC session.
  • Step 605 The PoC server performs role related information processing and performs session control.
  • Step 610 The PoC server sends a resource pre-allocation request to the online charging system (OCS), which carries the user role information, after the INVITE is accepted.
  • OCS online charging system
  • Step 615 The OCS pre-allocates resources according to the role and the pre-allocated amount of the request.
  • the OCS may also consider factors such as the number of invitations to determine whether to allow and allow allocation of resources.
  • factors such as the number of invitations to determine whether to allow and allow allocation of resources.
  • the description of the process is omitted, and only the success of the assignment is taken as an example.
  • Step 620 The OCS pre-allocation succeeds, and the response result is returned to the PoC server, including the allocated resource quantity (Quota).
  • Step 625 The PoC server establishes a PoC session successfully, and sends a SIP INVITE request to other users.
  • Step 630 the invited user responds with 200 OK, agrees to join the session, and is invited in the 200 ⁇ Please ask the user for the role information.
  • Step 635 After receiving the response from the invited user, the PoC server returns a response 200 OK to the user.
  • Step 650 After the session is established successfully, the OCS returns an accounting response message (CCA[Initial]) to the PoC server.
  • CCA[Initial] an accounting response message
  • Step 655 The session is successfully established, and the PoC server performs other session operations.
  • the session update process and the end session process are different from the billing process for establishing a session, where:
  • step 600 For the session end process, there is no process of step 600 to step 630 in FIG. 6, in the step corresponding to step 635, the SIP BYE message is returned; before the PoC server initiates the end of the charging CCR [Terminate] request, there is a The resource usage update process (Update Quota Control) calculates the amount of remaining resources.
  • the resource usage update process (Update Quota Control) calculates the amount of remaining resources.
  • CCR[Update, Users, Roles [nfo] requests the record.
  • the billing data record the last [user-role] information can be recorded, but due to the role operation, there will be billing triggered by the event, and the role operation details will be recorded.
  • the PoC user role may include, in addition to the existing Regular PoC Participant, the PoC Dispatcher, the PoC Moderator, and the fleet member. Including roles that are added later, their role-based billing implementation is the same.
  • the role-based PoC charging policy and scheme can provide necessary data for the operator differentiated service, and can be implemented by making minor modifications to the current technology.
  • the source of the role, the possible scenarios, and the solution to the scenario are proposed to solve the problem encountered in the role-based charging process as much as possible.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Telephonic Communication Services (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Meter Arrangements (AREA)

Description

在即按即通业务中基于角色计费的方法、 装置及系统 技术领域
本发明涉及通信领域中的计费技术, 尤其涉及在即按即通业务中基于角 色计费的方法、 装置及系统。 背景技术
即按即通( Push to Talk over Cellular, PoC )业务是一种基于 IP技术的集 群媒体通信业务, 它利用承载网络, 以半双工 VoIP技术来实现。 PoC用户在 设定好群组名单后, 可与其他 PoC用户进行点对点、点对多点的半双工通话。 PoC业务系统如图 1A所示。
PoC通信中各实体的关系如图 1B所示, 控制 PoC功能( Controlling PoC Function, CPF )是通信的核心部分, 用于进行集中式控制, 执行包括会话控 制(建立 /取消会话、 信令和媒体协商、 处理请求、 分发媒体流等通信控制)、 群组策略执行(包括收集并控制 QoS )及用户面适配等功能。 每个客户端 ( Client )对应一个加入 PoC功能(Participate PoC Function, PPF ), 各 PPF 进行会话操作都是向 CPF发送请求,由 CPF协调控制会话过程(如媒体分发、 数据转送、 权限及角色转移、 QoE认证等)。 加入会话的 Client之间通信是通 过 PPF向 CPF请求并接收 CPF指令, CPF依据策略向 PPF分发媒体、 数据, 之后, 各 PPF将其转发给对应连接的 Client, 完成点 Client之间对点 /点对多 点的通信。
CPF与 EPF为功能模块, 它们可以存在于 1个 PoC服务器上, 也可以分 属不同的 PoC服务器上。 Client是 PoC用户加入会话的功能实体,角色是 PoC 用户的属性之一, 而 PoC用户可组成 PoC群组(Group )。 当前 PoC用户角色 有: 普通加入用户 ( Regular PoC Participant )、 调度员 ( PoC Dispatcher )、 中 间緩和角色(PoC Moderator ), fleet member (被调度成员)等, 角色还在补 充之中。
PoC的计费是分别对 PPF和 CPF进行计费的,分为离线计费和在线计费, 离线计费模块称之为 CDF, 在线计费模块称之为 OCS。
当 PPF或 CPF因 PoC操作而产生事件(EVENT ) 时, 或者在会话的建 立、 更新、 结束时, 都会引发相应的计费请求和计费操作。
PoC 计费主要流程是: 被计费对象因事件产生而触发计费请求, 请中携 带所需数据参数, 被发送到计费模块 ( CDF或 OCS ); 计费模块按此参数进行 计费处理, 将影响用户帐务数据; 完成计费处理后, 计费模块向被计费对象 返回操作结果。 但发明人在研发过程发现, 现有技术无法针对用户角色进行 计费。 发明内容
本发明实施例提供一种在即按即通(PoC ) 业务中基于角色的计费方法、 装置及系统, 以针对不同用户角色进行差异化计费。
一种在即按即通业务中基于角色的计费方法, 包括如下步骤:
PoC 服务器向计费功能实体发送计费请求, 并且在该请求中携带用户角 色的相关信息;
所述计费功能实体接收到请求后参考所述相关信息选择计费策略 按选 择的计费策略进行计费处理, 并向 PoC服务器返回计费响应。
一种 PoC服务器, 包括:
用于获得用户角色的相关信息的模块;
用于向计费功能实体发送包含所述相关信息的计费请求的模块; 用于接收计费响应的模块。
一种计费装置, 包括:
用于接收包含用户角色的相关信息的计费请求的模块;
用于参考所述相关信息选择计费策略进行计费的模块;
用于向发送计费请求方返回计费响应的模块。
一种通信系统, 包括:
PoC服务器, 用于发送携带用户角色的相关信息的计费请求; 计费功能实体, 用于接收所述计费请求和参考其中的用户角色的相关信 息选择计费策略, 并按选择的计费策略进行计费处理和向所述 PoC服务器返 回计费响应。
本发明实施例在计费请求中携带用户角色的相关信息, 计费功能实体根 据用户角色相关信息选择计费策略, 从而可以实现针对不同的用户角色提供 差异化计费。 附图说明
图 1A为现有技术中 PoC业务系统结构示意图;
图 1B为现有技术的 PoC通信中各实体的关系示意图;
图 2为本发明实施例中实现按角色计费的 PoC通信系统;
图 3为本发明实施例中按角色建立 /加入 PoC会话的计费流程图; 图 4为本发明实施例中用户-角色各組成部分的关系示意图;
图 5为本发明实施例中离线计费的流程图;
图 6为本发明实施例中在线计费的流程图。. 具体实施方式
由于用户角色的区别, 其操作权限、 操作范围以及可进行的操作都会有 所区别, 因此, 本发明实施例将用户角色考虑到执行的计费策略中, 以此提 供差异化的计费。
参阅图 2所示, 控制 PoC功能 CPF ( Controlling PoC Function ) 与加入 PoC功能 PPF ( Participate PoC Function )存在于同一个 PoC服务器中 (也可 存在于不同的 PoC服务器中), PoC服务器可以在建立会话、 加入会话、 会话 更新或结束会话过程中触发计费操作, 向计费功能实体发送计费请求, 该请 求中携带 PoC用户角色的相关信息。 该相关信息可以是角色的部分信息, 例 如: 角色标识、 角色 ID、 与角色相关的非角色信息 (如用户名、 ID等)、 角 色有效期、 角色相关功能标识中的部分或全部信息等, 也可以是角色的详细 信息。 计费功能实体上保存有针对不同角色的计费策略, 在接收到计费请求 后, 参考用户角色的相关信息选择计费策略并按该策略进行计费处理。 所述 的计费处理可以是计费, 也可以是不计费。
在本实施例中, 同一个 PoC用户可以拥有 1个以上角色(角色间不能互 斥), 每个角色拥有不同操作、 权限、 级别, 计费功能实体对此执行不同计费 策略, 产生相应的计费数据记录(CDR )。 角色特征可以包含多方面的内容, 比如角色标志、 权限、 级别、 操作范围等, 这些数据与计费策略和计费方式 关联。 角色及其特征可以记录在 PoC用户相关的任何地方, 同时它们可以分 散配置和记录。 如记录在 XML文档管理艮务器 (XDMS ) 中的組(Group ) 属性中、 运行时的 PoC服务器或 Poc客户端上; 保存在 PoC服务器上时, 可 以存在其对应的 PPF上, 也可以存在于 CPF上, 或者两者兼而有之。
PoC服务器可以有多种途径获得用户角色的相关信息, 如:
A、 PoC服务器从发送来的 SIP INVITE直接获得角色信息;
B、 PoC服务器由 SIP INVITE中的 Client用户 ID/角色 ID, 从 XDMS等 外部服务器获得角色信息;
C、 PoC服务器根据当前状况,组合上下文信息确定赋予某个 PoC用户角 色。
图 2中的 PoC服务器和计费功能(Charging fonction )实体表示功能含意, 并不表示功能数量, PoC服务器和计费功能实体都可能有多个。
在一个具体实例中, PPF/CPF 包括: 用于获得用户角色的相关信息的模 块, 用于向计费功能实体发送包含所述相关信息的计费请求的模块, 以及用 于接收计费响应的模块。 即 PPF/CPF可以向不同的计费功能实体发送计费请 求。
在一个具体实例中, 计费功能实体包括: 用于接收包含用户角色的相关 信息的计费请求的模块; 用于参考所述相关信息选择计费策略进行计费的模 块; 以及用于向发送计费请求方返回计费响应的模块。
参阅图 3所示, 以用户角色的建立或加入 PoC会话过程为例, 实现计费 的过程如下:
步骤 300、 PoC服务器收到 SIP请求(INVITE )建立 /加入 PoC会话。 所述 SIP请求来源可以是多样的, 如: PoC服务器收到来自 PoC客户端 发送来的请求; 或其它服务器向 PoC服务器发送的请求; 或 PoC服务器根据 当前状况, 由其内部触发并产生 SIP请求。
步骤 310、 PoC服务器会话处理: PoC服务器由 INVITE信息得到角色信 息, 进行角色相关处理(例如: 在对角色识别、 认证通过后, 将建立与角色 类型相符合的会话类型, 设定相应属性等处理), 同时进行会话处理(如向其 它用户发出会话邀请)。在被邀请用户同意加入会话时,在其响应消息 200 OK 中携带被邀请用户角色的相关信息。
步骤 320、 PoC服务器向计费功能(Charging Function ) 实体发送携带用 户角色的相关信息的计费请求( Charging Request ), 即该请求是角色相关的。
步骤 330、 计费功能实体收到 PoC服务器的计费请求后, 参考其中的用 户角色的相关信息选择计费策略, 根据该计费策略开始计费。
选择计费策略时, 除参考角色相关信息外, 还可以参考其它因素, 比如: 当前所处的时间段、 用户会话优先级、前当费率有效范围、 当前运行环境(如 承载媒体类型、 媒体变化)等, 这些因素及它们的任何组合情形, 都可以影 响到如何选择计策略, 因此, 角色相关信息并非唯一确定计费选择策略的唯 一因素, 但在角色相关的计费策略选择中需要考虑用户角色。
计费策略可以根据需要灵活定制, 如, 一种计费策略为按角色和时段确 定费率, 具体的计费策略可如下所示:
用户角色为 A, 处于时段 , 对应费率 A1; 角色为 B, 处于时段 a, 对应 费率 B1; 角色为 A, 处于时段 b, 对应免费 (或不选择费率, 直接进行免费 处理)。
步驟 340、计费功能实体向 PoC服务器返回计费响应( Charging Respone )。 步骤 350、 会话建立成功后, 执行其它的会话操作。
在步骤 330中, 可能会进行一系列操作, 这是因为 PoC服务器会接受多 个被邀请用户回馈的 SIP消息, 每个都会使 PPF及 CPF产生相应的计费请求 (而且 PPF和 CPF计费处理也有所不同, CPF会对此连续更新操作)。
对于会话更新过程和结束会话过程中的计费处理与上述流程中的步驟 320至步骤 340同理。
在计费请求消息中, 用户角色的相关信息采用能够表明多用户多角色的 角色信息结构携带, 在一个具体实例中, 以 [用户 <—>多角色信息]组的形式表 示( [Users-roles] )。 一个用户角色信息结构表示有多个用户; 每个用户有多个 角色, 每个角色有多个相关信息字段。 具体的信息结构关系描述如图 4所示, 其中:
A、 1个 [Users-roles]即是用户角色信息结构, 它由 [0..* )个(即 0至多个) [用户一角色]组成(User-role )。 其中 0 角色表示: 如果会话由会话所有者
( Session Owner )发起 Chat型会话, 所有者本身不加入会话, 而该会话尚无 其它用户加入时, CPF记录的角色信息结构里就没有 User-role。
B、 每个 [User-role]可包含 [0..* )个角色信息 [Role-info]。 加入会话的某一 用户无角色或策略要求忽略角色信息时, 该字段就是空。
C、 角色信息由 [0..* )个角色信息单元(即至少一个), 该字段因角色不 同而可以变化, 内容按角色扩展, 如角色的操作、 权限、 范围、 有效时间等。 其中, 0信息单元表示: 用户有角色, 但角色为缺省信息或策略要求忽略角色 信息, 则可以没有角色信息字段。
图 4主要是描述组成角色的各部分的相互关系, 实现时并不限于该形式。 其中 User-role、 Role-info可以是隐式, 也可以是显示表示。 显式表示是指每 个描述的数据单元都明确声明, 并表示他们的关系的方法; 隐式表示是指非 显式表示, 即不使用 User-role和 /或 Role-info这样的单独数据结构将八、 B、 C中描述的关系表示出来的方法, 比如类似数据表的形式描述。
由于 CPF与 PPF产生的计费功能请求有所不同, 因而计费功能实体所做 的操作也会有所差异:
1、 对于 CPF, 角色信息结构 ([Users-Roles] ) 中保存 CPF控制的会话的 所有加入者角色信息, 随着用户的加入, 不断更新该信息组; 有机制将该情 况向计费功能发起请求, 创建相应的不完全 CDR记录(Partial CDR ) (之后它 们会被合并), 记录这种变化及其对计费策略的影响。
2、 对于 PPF, 角色信息结构 ([Users-Roles] ) 中保存该用户信息, PPF 建立 /参加会话时, 不用更新该信息,计费功能在 CDR中记录下该用户的角色 信息。
在本实施例中, 计费可以是离线计费 (Offline Charging ), 也可以是在线 计费; 对于在线计费由基于会话的资源预留计费(SCUR )或基于事件的资源 预留计费 (ECUR ) 来实现。
参阅图 5所示, 以用户角色的建立或加入 PoC会话过程为例, 实现离线 计费的过程如下:
步骤 500、 PoC服务器收到请求 SIP INVITE, 建立 /加入 PoC会话。
步骤 510、 PoC服务器进行角色相关信息处理, 并进行会话控制。
步骤 520、 PoC服务器向计数数据功能(CDF )实体发角色相关的计费请 求( ACR[start, Users, Roles Info] )。
步驟 530、 CDF 实体进行角色相关的一系列处理, 包括根据用户角色的 相关信息执行计费策略, 执行计费策略生成 PPF-CDR和 PPF-CDR。
步驟 540、 CDF实体向 PoC服务器返回计费响应( ACA[start] ) ) (分别回 应 CPF和 PPF )。 步骤 550、 会话建立成功, PoC服务器进行其它 PoC会话操作。 相应的, 计费处理完成, CDF执行其它 PoC业务。
与建立会话的计费过程有相似的还有会话更新过程、 结束会话过程, 它 们与图 5 所示的流程同理, 但计费请求消息有所不同: 更新过程用到的 ACR[Interim, Users, Roles info]; 而结束过程用到的 ACR[Stop, Users, Roles info], 完成计费后是会话结束。
离线计费中, 对于更新过程, 当更新的同期内 (比如更新的时间间隔为 6 秒) 出现多次的角色操作(如角色转移等), 那么 ACR[Interim, Users, Roles info]请求记录的计费数据记录里, 记录的可以是最后的 [用户一角色]信息, 但 由于发生了角色操作, 则还会有该事件触发的计费, 记录下角色操作详细情 况。
参阅图 6所示, 以用户角色的建立或加入 PoC会话过程为例, 实现在线 计费 ( Online Charging ) 的处理过程如下:
步骤 600、 PoC服务器收到请求 SIP INVITE, 建立 /加入 PoC会话。
步骤 605、 PoC服务器进行角色相关信息处理, 并进行会话控制。
步骤 610、 由于是建立会话, PoC服务器接受 INVITE后向在线计费系统 ( OCS )发送资源预分配请求, 其中携带用户角色信息。
步驟 615、 OCS根据角色及其请求的预分配量预分配资源。
在该步骤中, OCS可能还要考虑邀请人数等因素来判断是否允许以及允 许分配多少资源, 本实施中省略对该过程描述, 仅以分配成功为例。
步骤 620、 OCS预分配成功, 向 PoC服务器返回响应结果, 包括分配资 源数量( Quota )。
步骤 625、 PoC服务器建立 PoC会话成功, 向其它用户发 SIP INVITE请 求。
步驟 630、 被邀请用户响应 200 OK, 同意加入会话, 200 ΟΚ中带有被邀 请用户的角色信息。
步骤 635、 PoC服务器收到被邀请用户响应后, 向用户返回响应 200 OK。 步骤 640、 PPF/CPF向在线计费系统 OCS发送角色相关的计费请求。 步骤 645、 OCS 进行角色相关的计费处理, 产生相应的 CPF-CDR和
Figure imgf000011_0001
步驟 650、 建立会话成功, OCS 向 PoC 服务器返回计费响应消息 ( CCA[Initial] )。
步骤 655、 会话建立成功, PoC服务器进行其它会话操作。
与建立会话的计费过程有所不同的还有会话更新过程、 结束会话过程, 其中:
1、 对于更新会话过程, 没有图 6中步驟 600至步骤 635的处理过程, 但 PoC服务器发起更新计费 CCR[Update]请求之前,有一个对当前已分配资源使 用情况的更新过程(Update Quota Control ), 以计算剩余资源数量。 如果资源 用尽, 则向 OCS请求再分配资源。 在更新资源使用情况时, 并不要求 定要 有角色信息。
2、 对于会话结束过程, 没有图 6中步骤 600至步骤 630的处理过程, 在 在对应步骤 635的步骤中, 返回 SIP BYE消息; 在 PoC服务器发起结束计费 CCR[Terminate]请求之前, 有一个资源使用情况更新过程 (Update Quota Control ), 计算剩余资源数量, PoC服务器在发起结束计费 CCR[terminate]请 求时, 将此数值包括在请求中; 在完成计费处理后结束会话。 因此, 在结束 会话过程中没有资源预分配过程。
在线计费中, 对于更新过程, 当更新的同期内 (比如更新的时间间隔为 6 秒) 出现多次的角色操作(如角色转移等), 那么 CCR[Update, Users, Roles [nfo]请求记录的计费数据记录里, 记录的可以是最后的 [用户一角色]信息, 但 由于发生了角色操作, 则还会有该事件触发的计费, 记录下角色操作详细情 况。
在本实施例中, PoC用户角色除了包括现有的普通加入用户( Regular PoC Participant )、调度员 ( PoC Dispatcher )、 中间緩和角色( PoC Moderator )、 fleet member (被调度成员)外, 同样还可包括以后补充的角色, 其基于角色的计 费实现相同。
本实施例基于角色的 PoC计费的策略及方案, 能够为运营商差异化服务 提供必需的数据, 而且通过对现技术进行较小的改动即可实现。 同时, 提出 在建立 /加入 PoC会话时, 角色产生的来源、 可能遇到的场景、 对该场景的解 决方法, 以便尽可能解决基于角色计费过程中遇到的问题。
显然, 本领域的技术人员可以对本发明进行各种改动和变型而不脱离本 发明的精神和范围。 这样, 倘若对本发明的这些修改和变型属于本发明权利 要求及其等同技术的范围之内, 则本发明也意图包含这些改动和变型在内。

Claims

权利要求
1、 一种在即按即通(PoC )业务中基于角色的计费方法, 其特征在于, 包括如下步骤:
PoC服务器向计費功能实体发送计费请求, 并且在该请求中携带用户角 色的相关信息;
所述计费功能实体接收到请求后参考所述相关信息选择计费策略, 按选 择的计费策略进行计费处理, 并向 PoC服务器返回计费响应。
2、 如权利要求 1所述的计费方法, 其特征在于, 所述 PoC服务器直接从 SIP消息中获取用户角色的相关信息; 或者, 从外部服务器获得用户角色的相 关信息; 或者, 通过组合上下文获得用户角色的相关信息。
3、 如权利要求 1所述的计费方法, 其特征在于, 在所述计费请求中采用 能够表明多用户多角色的数据结构携带所述用户角色的相关信息。
4、 如权利要求 3所述的计费方法, 其特征在于, 由能够表示用户与角色 关系的信息组构成所述数据结构。
5、 如权利要求 1至 4之一项所述的计费方法, 其特征在于, PoC服务器 在建立会话、 加入会话、 会话更新或结束会话过程中发送所述计费请求。
6、 如权利要求 5所述的计费方法, 其特征在于, 所述 PoC服务器向离线 计费功能(CDF ) 实体发送计费请求, 由离线计费功能实体完成计费处理。
7、 如权利要求 5所述的计费方法, 其特征在于, 所述 PoC服务器向在线 计费系统发送计费请求, 由在线计费系统完成计费处理。
8、 如权利要求 7所述的计费方法, 其特征在于, 在建立会话和加入会话 过程中, PoC服务器发送计费请求前进一步请求所述在线计费系统为用户分 配资源, 并且在分配资源成功和建立 PoC会话成功后发送所述计费请求。
9、如权利要求 7所述的计费方法, 其特征在于,在会话更新过程中, PoC 服务器在发送计费请求前进一步计算剩余资源数量, 并且在用完已分配资源 时请求所述在线计费系统分配资源。
10、 如权利要求 7所述的计费方法, 其特征在于, 在会话结束过程中, PoC服务器发送计费请求前进一步使用资源的信息, 并将该信息携带在计费 请求中。
11、 一种 PoC服务器, 其特征在于, 包括:
用于获得用户角色的相关信息的模块;
用于向计费功能实体发送包含所述相关信息的计费倩求的模块; 用于接收计费响应的模块。
12、 如权利要求 11所述的 PoC服务器, 其特征在于, 直接从 SIP消息中 获取用户角色的相关信息; 或者, 从外部服务器获得用户角色的相关信息; 或者, 通过组合上下文获得用户角色的相关信息。
13、 如权利要求 11或 12所述的 PoC服务器, 其特征在于, 在建立会话、 加入会话、 会话更新或结束会话过程中发送所述计费请求。
14、 一种计费装置, 其特征在于, 包括:
用于接收包含用户角色的相关信息的计费请求的模块;
用于参考所述相关信息选择计费策略进行计费的模块;
用于向发送计费请求方返回计费响应的模块。
15、 如权利要求 14所述的计费装置, 其特征在于, 该计费装置为在线计 费装置或离线计费装置。
16、 一种通信系统, 其特征在于, 包括:
PoC服务器, 用于发送携带用户角色的相关信息的计费请求;
计费功能实体, 用于接收所述计费请求和参考其中的用户角色的相关信 息选择计费策略, 并按选择的计费策略进行计费处理和向所述 PoC服务器返 回计费响应。
17、 如权利要求 16所述的通信系统, 其特征在于, 所述 PoC服务器直接 从 SIP 消息中获取用户角色的相关信息; 或者, 从外部服务器获得用户角色 的相关信息; 或者, 通过组合上下文获得用户角色的相关信息。
PCT/CN2007/000571 2006-04-28 2007-02-15 An accounting method, apparatus and system based on roles in the business of push-to-talk over cellular WO2007124644A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP07710989.0A EP2009840B1 (en) 2006-04-28 2007-02-15 An accounting method, apparatus and system based on roles in the business of push-to-talk over cellular

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN2006100789658A CN101064615B (zh) 2006-04-28 2006-04-28 一种在即按即通业务中基于角色计费的方法及系统
CN200610078965.8 2006-04-28

Publications (1)

Publication Number Publication Date
WO2007124644A1 true WO2007124644A1 (en) 2007-11-08

Family

ID=38655048

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2007/000571 WO2007124644A1 (en) 2006-04-28 2007-02-15 An accounting method, apparatus and system based on roles in the business of push-to-talk over cellular

Country Status (4)

Country Link
EP (2) EP2942904B1 (zh)
CN (1) CN101064615B (zh)
ES (1) ES2634247T3 (zh)
WO (1) WO2007124644A1 (zh)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102123353A (zh) * 2010-01-12 2011-07-13 华为技术有限公司 业务计费方法、系统及业务服务器
WO2012148326A1 (en) * 2011-04-27 2012-11-01 Telefonaktiebolaget Lm Ericsson (Publ) Method and arrangement for supporting charging in a communications network
US9357359B2 (en) 2013-02-05 2016-05-31 Qualcomm Incorporated Dynamic quality of service (QoS) for services over cellular
CN104601338A (zh) * 2014-12-31 2015-05-06 曙光信息产业(北京)有限公司 系统的计费方法和装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1440158A (zh) * 2002-02-19 2003-09-03 阿尔卡塔尔公司 呼叫计费方法和相关网络元件
CN1444824A (zh) * 2000-05-24 2003-09-24 诺基亚有限公司 用于通信网络的公共计费标识符
CN1585519A (zh) * 2004-06-04 2005-02-23 中兴通讯股份有限公司 数字集群系统计费信息收集及计费方法
WO2005117344A1 (en) 2004-05-24 2005-12-08 Orange Personal Communications Services Limited Charging control system for group communication sessions

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050268328A1 (en) * 2002-07-03 2005-12-01 Gabriele Corliano Trust establishment for multi-party communications
JP4061308B2 (ja) * 2002-10-15 2008-03-19 テレフオンアクチーボラゲット エル エム エリクソン(パブル) ネットワークにおいて弾力的な課金を提供するシステム
FI20030802A0 (fi) * 2003-05-28 2003-05-28 Nokia Corp Menetelmä ja järjestelmä esimaksettujen datapalveluiden ohjaamiseksi
EP1569473B1 (en) * 2004-02-27 2009-02-25 Research In Motion Limited Methods and apparatus for facilitating concurrent push-to-talk over cellular (POC) group communication sessions
GB0408990D0 (en) * 2004-04-22 2004-05-26 Nokia Corp Charging in communication networks
JP4575097B2 (ja) * 2004-09-28 2010-11-04 株式会社エヌ・ティ・ティ・ドコモ 電子メール課金システム及び電子メール課金方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1444824A (zh) * 2000-05-24 2003-09-24 诺基亚有限公司 用于通信网络的公共计费标识符
CN1440158A (zh) * 2002-02-19 2003-09-03 阿尔卡塔尔公司 呼叫计费方法和相关网络元件
WO2005117344A1 (en) 2004-05-24 2005-12-08 Orange Personal Communications Services Limited Charging control system for group communication sessions
CN1585519A (zh) * 2004-06-04 2005-02-23 中兴通讯股份有限公司 数字集群系统计费信息收集及计费方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2009840A4 *

Also Published As

Publication number Publication date
EP2942904B1 (en) 2017-06-07
EP2009840A4 (en) 2013-06-12
EP2009840A1 (en) 2008-12-31
EP2009840B1 (en) 2015-05-27
CN101064615B (zh) 2010-12-08
EP2942904A1 (en) 2015-11-11
CN101064615A (zh) 2007-10-31
ES2634247T3 (es) 2017-09-27

Similar Documents

Publication Publication Date Title
RU2340113C1 (ru) Способ и устройство для формирования счетов для групповой связи на основе использования между устройствами радиосвязи
JP5189108B2 (ja) サービス処理方法およびサービス処理システム、ならびにポリシー制御および料金請求規則機能
US20050058070A1 (en) Method for transferring messages between communication terminals
WO2006047963A1 (fr) Correlation et gestion de la taxation des communications vocales interurbaines
WO2007112685A1 (fr) Procédé et système de facturation, centre de facturation et dispositif pour service d&#39;application
EP1802028A1 (en) A charging network , charging agent apparatus as well and the charging method thereof
CN108401231B (zh) 一种计费方法、装置和系统
CN101777987B (zh) 多媒体会议业务计费方法及系统
WO2007124644A1 (en) An accounting method, apparatus and system based on roles in the business of push-to-talk over cellular
WO2008000170A1 (fr) PROCÉDÉ DE FACTURATION, SYSTÈME DE FACTURATION ET DISPOSITIF DANS UN SYSTÈME PoC
CN101720108A (zh) 业务层融合网络的策略控制方法与系统
KR20060076298A (ko) 과금 방법 및 과금 유닛
CN101316179B (zh) 设置会话角色的方法、服务器与终端
EP2023588B1 (en) Charging method for poc service, system and communication system
WO2017084394A1 (zh) 漫游计费方法、相关装置及在线计费系统
WO2008083621A1 (fr) Procédé et système de traitement de flux de service ainsi que procédé et système d&#39;association d&#39;une prise en charge
WO2009076900A1 (zh) 实现即按即通计费的方法、设备及系统
CN101350770A (zh) 一种资源预留方法、装置及系统
CN101072112B (zh) 一种基于体验质量参数的计费方法
CN101959146B (zh) 一种在即按即通业务中基于角色计费的方法及系统
WO2008089681A1 (fr) Procédé et système de facturation dans un système de communication
TWI445372B (zh) Dynamic charging method for IMS Multicast service
CN102711053B (zh) 一种即按即通系统中的计费方法和装置
CN101094078A (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: 07710989

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2007710989

Country of ref document: EP