WO2022028076A1 - 一种计费处理的方法、系统及相关设备 - Google Patents

一种计费处理的方法、系统及相关设备 Download PDF

Info

Publication number
WO2022028076A1
WO2022028076A1 PCT/CN2021/097739 CN2021097739W WO2022028076A1 WO 2022028076 A1 WO2022028076 A1 WO 2022028076A1 CN 2021097739 W CN2021097739 W CN 2021097739W WO 2022028076 A1 WO2022028076 A1 WO 2022028076A1
Authority
WO
WIPO (PCT)
Prior art keywords
charging
data connection
redundant
processing
usage
Prior art date
Application number
PCT/CN2021/097739
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 华为技术有限公司
Priority to CA3190682A priority Critical patent/CA3190682A1/en
Priority to AU2021321730A priority patent/AU2021321730A1/en
Priority to EP21853317.2A priority patent/EP4187942A4/en
Priority to JP2023507740A priority patent/JP2023536967A/ja
Publication of WO2022028076A1 publication Critical patent/WO2022028076A1/zh
Priority to US18/164,459 priority patent/US20230187946A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing
    • H—ELECTRICITY
    • H02—GENERATION; CONVERSION OR DISTRIBUTION OF ELECTRIC POWER
    • H02J—CIRCUIT ARRANGEMENTS OR SYSTEMS FOR SUPPLYING OR DISTRIBUTING ELECTRIC POWER; SYSTEMS FOR STORING ELECTRIC ENERGY
    • H02J7/00—Circuit arrangements for charging or depolarising batteries or for supplying loads from batteries
    • H02J7/00032—Circuit arrangements for charging or depolarising batteries or for supplying loads from batteries characterised by data exchange
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/08—Arrangements for detecting or preventing errors in the information received by repeating transmission, e.g. Verdan system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/22—Arrangements for detecting or preventing errors in the information received using redundant apparatus to increase reliability
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • 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
    • 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
    • H04M15/41—Billing record details, i.e. parameters, identifiers, structure of call data record [CDR]
    • 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
    • H04M15/62—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP based on trigger specification
    • 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
    • H04M15/64—On-line charging system [OCS]
    • 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
    • H04M15/65—Off-line charging system
    • 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
    • H04M15/70—Administration or customization aspects; Counter-checking correct charges
    • H04M15/785—Reserving amount on the account
    • 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
    • H04M15/80—Rating or billing plans; Tariff determination aspects
    • 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
    • H04M15/80—Rating or billing plans; Tariff determination aspects
    • H04M15/8016—Rating or billing plans; Tariff determination aspects based on quality of service [QoS]
    • 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
    • H04M15/82—Criteria or parameters used for performing billing operations
    • H04M15/8228—Session based

Definitions

  • the present application relates to the field of communications, and in particular, to a method, a system and related equipment for performing charging processing on data connection services in a data connection session.
  • 5GS 5th Generation System
  • PDU protocol data unit
  • QoS quality of service, quality of service
  • PDU sessions Flow QoS Flow, quality of service flow
  • an embodiment of the present application provides a charging processing method, the method is applied to a charging trigger device, the charging trigger device communicates with the charging processing device, and the method includes:
  • the charging triggering device sends a first charging request message to the charging processing device, where the first charging request message includes redundant transmission information, and the redundant transmission information refers to the first charging request message in the data connection session.
  • the redundant transmission information refers to the first charging request message in the data connection session.
  • the charging triggering device receives a first charging response message from the charging processing device, the first charging response message includes a charging processing result, and the charging processing result is that the charging processing device is based on the The result of charging processing on the redundant transmission information.
  • the method enables the charging processing device to provide the charging processing device with information about the redundant transmission of the data connection service in the data connection session, so that the charging processing can perceive the redundant transmission in time, and perform calculation based on the redundant transmission. It helps to improve the accuracy of the charging results of redundantly transmitted data connection services, and meets the diversified charging requirements of operators or end users.
  • the method before sending the first charging request message to the charging processing device, the method further includes: the charging triggering device determining a redundant transmission mode of the first data connection service.
  • the redundant transmission information indicates that the transmission of the first data connection service is redundant transmission.
  • the redundant transmission information further indicates a redundant transmission mode of the first data connection service, and the redundant transmission mode is any one of the following: session redundancy, tunnel redundancy, or transport layer redundancy.
  • the redundant transmission mode of the first data connection service is session redundancy
  • the redundant transmission information further indicates that the data connection session is a master data connection session or a slave data connection session, or
  • the redundant transmission information also includes information of a data connection session that is redundant with the data connection session.
  • the charging processing result includes a quota granted by the charging processing device for the first data connection service and corresponding first processing indication information, where the first processing indication information indicates the
  • the charging triggering device sets a redundancy flag for the usage amount corresponding to the quota; the method further includes: the charging triggering device sends a second charging request message to the charging processing device, the second charging The request message includes the usage amount corresponding to the quota and the redundancy flag; the redundancy flag indicates that the usage amount is the usage amount of the redundantly transmitted data connection service.
  • the charging processing result includes second processing indication information, and the second processing indication information indicates that the second data connection service in the data connection session executes: contains redundant usage processing Or remove redundant usage processing.
  • the method enables the charging trigger device to collect the corresponding usage according to the needs of the charging processing device, which helps to improve the performance of the overall charging processing system.
  • the redundant transmission mode of the first data connection service is session redundancy or transport layer redundancy
  • the second data connection service corresponds to a rate group in the first data connection service , corresponding to the QoS flow in the first data connection service or corresponding to the data connection session corresponding to the first data connection service; or, the redundant transmission mode of the first data connection service is tunnel redundancy, so
  • the second data connection service corresponds to a rate group in the first data connection service, or corresponds to a QoS flow corresponding to the first data connection service.
  • the redundant transmission mode of the first data connection service is session redundancy, tunnel redundancy or transport layer redundancy
  • the redundant usage is performed for the second data connection service
  • the processing includes: taking half of the traffic of the redundant transmission of the second data connection service in the data connection session as the usage amount of the second data connection service; performing execution for the second data connection service including
  • the redundant usage processing includes: taking the redundantly transmitted traffic of the second data connection service in the data connection session as the usage of the second data connection service; or, the first data connection service
  • the redundant transmission mode is tunnel redundancy or transmission layer redundancy
  • performing redundant usage processing for the second data connection service includes: transferring all data transmitted between the user plane data gateway and the data network.
  • the traffic of the second data connection service is used as the usage amount of the second data connection service, and performing the usage processing including redundancy for the second data connection service includes: connecting the data gateway at the user plane with the wireless connection
  • the traffic of the second data connection service transmitted between the incoming network devices is used as the usage of the second data connection service; or, the redundant transmission mode of the first data connection service is tunnel redundancy or transport layer redundancy.
  • the performing redundant usage processing for the second data connection service includes: taking the traffic of the second data connection service transmitted through one of the two mutually redundant transmission paths as the The usage of the second data connection service, the performing the processing of usage including redundancy for the second data connection service includes: transferring the second data connection service through two mutually redundant transmission paths The traffic is used as the usage of the second data connection service.
  • the second data connection service is an online charging service, and performing the redundant usage processing or the redundant removal processing for the second data connection service, further comprising: The quota granted by the charging processing device is consumed with the usage of the second data connection service.
  • the charging triggering device sends the usage amount corresponding to the rate group or QoS flow in the first data connection service and the corresponding usage amount description information to the charging processing device, and the The usage description information indicates that the usage is any one of the following: the traffic for which the redundant-removing usage processing is not performed, the traffic after performing the redundant usage-removing processing, and the relationship between the user plane data gateway and the wireless access network device.
  • the traffic transmitted between the user plane data gateway and the data network.
  • the charging triggering device sends the transmission delay of the first data connection service to the charging processing device.
  • the charging processing result includes non-charging indication information, and the non-charging indication information instructs the charging processing device to determine that the data connection session is a slave data connection session without performing accounting on it. charge processing, or determine to perform charging on a data connection session that is redundant with the data connection session without performing charging processing on the data connection session.
  • the charging triggering device determines that the data connection session becomes the primary data connection session; the charging triggering device sends a third charging request message to the charging processing device, the first The third charging request message includes indication information that the data connection session becomes the primary data connection session.
  • an embodiment of the present application provides a charging processing method, the method is applied to a charging processing device, the charging processing device communicates with a charging triggering device, and the method includes:
  • the charging processing device receives a first charging request message from the charging triggering device, the first charging request message includes redundant transmission information, and the redundant transmission information refers to the first charging request message in the data connection session. - Information about redundant transmissions used by data connection services;
  • the charging processing device performs charging processing based on the redundant transmission information, obtains a charging processing result, and sends a first charging response message to the charging triggering device, where the first charging response message includes the the charging processing result.
  • the redundant transmission information indicates that the transmission of the first data connection service is redundant transmission.
  • the redundant transmission information further indicates a redundant transmission mode of the first data connection service, and the redundant transmission mode is any one of the following: session redundancy, tunnel redundancy, or transport layer redundancy.
  • the redundant transmission mode of the first data connection service is session redundancy
  • the redundant transmission information further indicates that the data connection session is a master data connection session or a slave data connection session, or
  • the redundant transmission information also includes information of a data connection session that is redundant with the data connection session.
  • the charging processing device performs charging processing based on the redundant transmission information, including: determining, based on the redundant transmission information, and performing redundancy removal on the usage of the first data connection service the charging processing or including redundant charging processing, and granting a quota for the first data connection service; the charging processing result contains the quota; the method further includes: the charging processing device from the The charging triggering device receives a second charging request message, where the second charging request message includes the usage amount corresponding to the quota; the charging processing device performs redundant charging on the usage amount of the quota Handle or contain redundant billing processing.
  • the method further includes: generating, by the charging processing device, first processing indication information for the quota, where the first processing indication information indicates that the charging triggering device is the one corresponding to the quota.
  • a redundant flag is set for the usage amount;
  • the charging processing result further includes the first processing indication information;
  • the second charging request message also includes the redundant flag;
  • Performing the redundant-removing charging processing or the redundant-containing charging processing for the usage amount including: the charging processing device performing the redundant-removing charging processing or the redundant-removing charging processing on the usage amount of the quota based on the redundancy flag Redundant billing processing; the redundancy flag indicates that the usage is the usage of redundantly transmitted data connection services.
  • the charging processing device performs charging processing based on the redundant transmission information, including: the charging processing device generates second processing indication information based on the redundant transmission information;
  • the fee processing result includes the second processing indication information; wherein, the second processing indication information instructs the charging triggering device to perform: including redundant usage processing for the second data connection service in the data connection session Or remove redundant usage processing.
  • the redundant transmission information indicates that the redundant transmission mode of the first data connection service is session redundancy or transport layer redundancy, and the second data connection service is connected to the first data connection corresponding to a rate group in the service, corresponding to a QoS flow in the first data connection service, or corresponding to a data connection session corresponding to the first data connection service; or, the redundant transmission information indicates that the first data connection service
  • the redundant transmission mode of the data connection service is tunnel redundancy
  • the second data connection service corresponds to a rate group in the first data connection service or to a QoS flow corresponding to the first data connection service.
  • the method further includes: the charging processing device receives, from the charging triggering device, the usage amount corresponding to the rate group or QoS flow in the first data connection service and the corresponding usage
  • the usage description information indicates that the usage is any one of the following: the traffic for which the redundant usage processing is not performed, the traffic after performing the redundant usage processing, the user plane data gateway and the The traffic transmitted between wireless access network devices and the traffic transmitted between the user plane data gateway and the data network.
  • the method further includes: the charging processing device receives the transmission delay of the first data connection service from the charging triggering device; the charging processing device is based on the redundancy Performing charging processing on the transmission information includes: the charging processing device performs charging processing according to the redundant transmission information and the transmission delay.
  • the method further includes: the charging processing device writes the information of the first data connection service into a bill, and the information of the first data connection service includes any one of the following: redundant remaining transmission information, usage description information or transmission delay.
  • the charging processing device performs charging processing based on the redundant transmission information, including: the charging processing device determines not to perform charging processing on the connection session; the charging processing device determines not to perform charging processing on the connection session; generating non-accounting indication information, the non-accounting indication information instructing the charging processing device to determine that the data connection session is a slave data connection session without performing charging processing on it, or to determine that the data connection session is a slave data connection session
  • the redundant data connection session performs charging without performing charging processing; the charging processing result includes the non-charging indication information.
  • an embodiment of the present application provides a charging processing system, including: a charging triggering device and a charging processing device, the charging triggering device communicates with the charging processing device, wherein:
  • the charging processing device is configured to: perform charging processing based on the redundant transmission information, obtain a charging processing result, and send a first charging response message to the charging triggering device, where the first charging response The message contains the charging processing result.
  • the redundant transmission information indicates that the transmission of the first data connection service is redundant transmission.
  • the redundant transmission information further indicates a redundant transmission mode of the first data connection service, and the redundant transmission mode is any one of the following: session redundancy, tunnel redundancy, or transport layer redundancy.
  • the redundant transmission mode of the first data connection service is session redundancy
  • the redundant transmission information further indicates that the data connection session is a master data connection session or a slave data connection session, or
  • the redundant transmission information also includes information of a data connection session that is redundant with the data connection session.
  • the charging processing device is further configured to: determine, based on the redundant transmission information, to perform redundant charging processing on the usage of the first data connection service, and perform charging processing for the first data connection service. granting a quota for the data connection service; making the charging processing result include the quota; and the charging triggering device is further configured to: send a second charging request message to the charging processing device, the second charging request The message includes the usage amount corresponding to the quota; and the charging processing device is further configured to: perform a redundant-removing accounting process or a redundant-inclusive accounting process on the usage amount of the quota.
  • the charging processing device is further configured to: generate first processing indication information for the quota, where the first processing indication information instructs the charging triggering device to be the usage amount corresponding to the quota setting a redundancy flag; making the charging processing result further include the first processing indication information; the charging triggering device is further configured to: include the redundancy flag in the second charging request message; wherein , and the redundancy flag indicates that the usage amount is the usage amount of the redundantly transmitted data connection service.
  • the charging processing device is further configured to: generate second processing indication information based on the redundant transmission information; make the charging processing result include the second processing indication information;
  • the fee triggering device is further configured to: according to the second processing indication information, perform for the second data connection service in the data connection session: include redundant usage processing or remove redundant usage processing.
  • the redundant transmission information further indicates that the data connection session is a slave data connection session or the redundant transmission information includes information of a data connection session that is redundant with the data connection session;
  • the charging processing device is further configured to: determine not to perform charging processing on the data connection session, generate non-accounting indication information, and make the charging processing result include the non-accounting indication information, and the non-accounting indication information is not counted.
  • the charging indication information instructs the charging processing device to determine that the data connection session is a slave data connection session without performing charging processing on it, or determine to perform charging on a data connection session that is redundant with the data connection session and perform charging on the data connection session. No billing process is performed for the data connection session.
  • an embodiment of the present application provides a charging trigger device, the charging trigger device communicates with a charging processing device, and includes a sending module and a receiving module, wherein:
  • the sending module is configured to: send a first charging request message to the charging processing device, where the first charging request message includes redundant transmission information, and the redundant transmission information refers to the data in the data connection session. Information about redundant transmission used by the first data connection service;
  • the redundant transmission information indicates that the transmission of the first data connection service is redundant transmission.
  • the redundant transmission information further indicates a redundant transmission mode of the first data connection service, and the redundant transmission mode is any one of the following: session redundancy, tunnel redundancy, or transport layer redundancy.
  • the redundant transmission mode of the first data connection service is session redundancy
  • the redundant transmission information further indicates that the data connection session is a master data connection session or a slave data connection session, or
  • the redundant transmission information also includes information of a data connection session that is redundant with the data connection session.
  • the charging processing result includes a quota granted by the charging processing device for the first data connection service and corresponding first processing indication information, where the first processing indication information indicates the
  • the charging triggering device sets a redundancy flag for the usage amount corresponding to the quota
  • the sending module is further configured to: send a second charging request message to the charging processing device, where the second charging request message includes the The usage amount corresponding to the quota and the redundancy flag; the redundancy flag indicates that the usage amount is the usage amount of the redundantly transmitted data connection service.
  • the charging processing result includes second processing indication information
  • the second processing indication information indicates that the second data connection service in the data connection session executes: contains redundant usage processing Or remove redundant usage processing.
  • the sending module is further configured to send the transmission delay of the first data connection service to the charging processing device.
  • the charging processing result includes non-charging indication information, and the non-charging indication information instructs the charging processing device to determine that the data connection session is a slave data connection session without performing accounting on it. charge processing, or determine to perform charging on a data connection session that is redundant with the data connection session without performing charging processing on the data connection session.
  • an embodiment of the present application provides a charging processing device, the charging processing device communicates with a charging triggering device, and includes a receiving module and a sending module, wherein:
  • the receiving module is configured to: receive a first charging request message from the charging triggering device, where the first charging request message includes redundant transmission information, and the redundant transmission information refers to the data in the data connection session. Information about redundant transmission used by the first data connection service;
  • the sending module is configured to: perform charging processing based on the redundant transmission information, obtain a charging processing result, and send a first charging response message to the charging triggering device, where the first charging response message includes the charging processing result.
  • the redundant transmission information indicates that the transmission of the first data connection service is redundant transmission.
  • the redundant transmission information further indicates a redundant transmission mode of the first data connection service, and the redundant transmission mode is any one of the following: session redundancy, tunnel redundancy, or transport layer redundancy.
  • the redundant transmission mode of the first data connection service is session redundancy
  • the redundant transmission information further indicates that the data connection session is a master data connection session or a slave data connection session, or
  • the redundant transmission information also includes information of a data connection session that is redundant with the data connection session.
  • the sending module is further configured to: determine, based on the redundant transmission information, to perform a redundant-removing charging process or a redundant-inclusive charging process for the usage of the first data connection service , and grant a quota for the first data connection service; the charging processing result includes the quota; the receiving module is further configured to: receive a second charging request message from the charging trigger device, the first 2.
  • the charging request message contains the usage amount corresponding to the quota; the charging processing device performs the charging process of removing redundancy or the charging process including redundancy on the usage amount of the quota.
  • the sending module is further configured to: generate second processing indication information based on the redundant transmission information; the charging processing result includes the second processing indication information; wherein the second processing indication information is The processing indication information instructs the charging triggering device to perform, for the second data connection service in the data connection session: processing of including redundant usage or processing of removing redundant usage.
  • the receiving module is further configured to: receive, from the charging triggering device, the usage amount corresponding to the rate group or QoS flow in the first data connection service and the corresponding usage amount description information,
  • the usage description information indicates that the usage is any one of the following: the traffic for which the redundant-removing usage processing is not performed, the traffic after performing the redundant usage-removing processing, the user plane data gateway and the wireless access network Traffic transmitted between devices, and traffic transmitted between the user plane data gateway and the data network.
  • the receiving module is further configured to: receive the transmission delay of the first data connection service from the charging trigger device; the sending module is further configured to: according to the redundant transmission information and the transmission delay to perform charging processing.
  • the sending module is further configured to: write the information of the first data connection service into a bill, and the information of the first data connection service includes any one of the following: redundant transmission information, Usage description information or transmission delay.
  • the sending module is further configured to: determine not to perform charging processing on the connection session; generate non-accounting indication information, the non-accounting indication information instructs the charging processing device to determine the The data connection session is a slave data connection session without performing charging processing on it, or determining that the data connection session redundant with the data connection session performs charging without performing charging processing on it; the charging processing result includes the non-charging indication information.
  • an embodiment of the present application provides a charging trigger device, including a processor and a memory, wherein: the memory is used to store program instructions; the processor is used to call and execute the memory stored in the memory The program instructions, so that the charging trigger device executes the charging processing method corresponding to the first aspect or any possible solution under the first aspect.
  • an embodiment of the present application provides a charging processing device, including a processor and a memory, wherein: the memory is used to store program instructions; the processor is used to call and execute the storage in the memory The program instructions, so that the charging processing device executes the charging processing method corresponding to the second aspect or any possible solution under the second aspect.
  • an embodiment of the present application provides a computer-readable storage medium, including instructions, which, when run on a computer, cause the computer to execute the first aspect, the second aspect, and any of the following aspects of the first aspect.
  • FIG. 1 is a schematic diagram of a session redundancy transmission mode provided by an embodiment of the present application
  • FIG. 2A is a first schematic diagram of a tunnel redundant transmission mode provided by an embodiment of the present application.
  • FIG. 2B is a second schematic diagram of a tunnel redundant transmission mode provided by an embodiment of the present application.
  • FIG. 3 is a schematic diagram of a transmission layer redundancy transmission mode provided by an embodiment of the present application.
  • 4A is an architecture diagram of a first communication system provided by an embodiment of the present application.
  • 4B is a flowchart of a first method for performing charging processing on redundantly transmitted data connection services provided by an embodiment of the present application
  • FIG. 5 is an architecture diagram of a second communication system provided by an embodiment of the present application.
  • 6A is a flowchart of a second method for performing charging processing on redundantly transmitted data connection services provided by an embodiment of the present application
  • 6B is a flowchart of a third method for performing charging processing on redundantly transmitted data connection services provided by an embodiment of the present application
  • FIG. 7A is an architecture diagram of a third communication system provided by an embodiment of the present application.
  • FIG. 7B is a flowchart of a fourth method for performing charging processing on redundantly transmitted data connection services provided by an embodiment of the present application.
  • FIG. 8 is a hardware structure diagram of a charging trigger device and a charging processing device provided by an embodiment of the present application.
  • FIG. 9 is a schematic diagram of a logical structure of a charging processing device provided by an embodiment of the present application.
  • FIG. 10 is a schematic diagram of a logical structure of a charging triggering device provided by an embodiment of the present application.
  • words such as “first” and “second” are used to distinguish the same or similar items with basically the same function and effect.
  • words “first”, “second” and the like do not limit the quantity and execution order, and the words “first”, “second” and the like are not necessarily different.
  • the communication network of the operator may adopt at least the following three modes of redundant transmission to improve its reliability.
  • Session redundancy (denoted as “S1"): the redundancy of data connection sessions, which means that there are two mutually redundant data connection sessions between the user equipment and the data network, and the service data streams of the same service of the user are simultaneously transmitted in the two mutually redundant data connection sessions.
  • UE user equipment, user equipment
  • PDU protocol data unit, protocol data unit
  • user plane user plane path for transmitting the same data between UE 101 and DN (Data Network, data network) 109.
  • the embodiment of the present application refers to the redundant transmission mode as "session redundancy" for short.
  • Tunnel redundancy refers to the existence of two user plane transmission tunnels that transmit the same data between the wireless access network device and the user plane data gateway, corresponding to the same QoS flow in the data connection session ( That is, the service data flow in the QoS flow is redundantly transmitted through the two user plane transmission tunnels), forming two mutually redundant transmission tunnel (N3/N9) level transmission paths. For example, as shown in FIG. 2A or FIG.
  • the SMF (Session Management Function) device 204 notifies the PSA (PDU session anchor, PDU session anchor) UPF (User Plane Function, user face function) device 205 and NG-RAN (Next-Generation Radio Access Network, Next-Generation Radio Access Network, Next-Generation Radio Access Network) device 203 perform redundant transmission of QoS flow granularity.
  • PSA PDU session anchor, PDU session anchor
  • UPF User Plane Function, user face function
  • NG-RAN Next-Generation Radio Access Network, Next-Generation Radio Access Network, Next-Generation Radio Access Network
  • the two N3 interface tunnels (N3 Tunnel) between the devices 203 transmit the same data, and the two N3 interface tunnels share the same QoS flow identifier, as shown in Figure 2A; -The two N3 and N9 interface tunnels (N3 and N9 Tunnel) between the RAN device 203 transmit the same data, and the two N3 and N9 tunnels also share the same QoS flow identifier, as shown in Figure 2B.
  • the redundant transmission mode is referred to as "tunnel redundancy" for short in this embodiment of the present application, which corresponds to the QoS flow identifier.
  • Transport layer redundancy refers to the existence of two transport layer paths between the wireless access network device and the user plane data gateway that jointly correspond to the data connection session to transmit the same data (that is, the data All service data streams in the connection session are redundantly transmitted through the two transport layer paths respectively), forming two mutually redundant transmission paths at the data connection session level. For example, as shown in FIG.
  • the traffic between the UE and the user plane data gateway is the same as the data connection between the user plane data gateway and the data gateway.
  • the data traffic between the networks is consistent (not considering the situation of packet loss due to policy control or network reasons); and the redundant transmission in S2 or S3 mode only occurs between the wireless access network device and the user plane data gateway.
  • the traffic of the data connection service of the same redundant transmission on both sides of the user plane data gateway is inconsistent, that is, regardless of network anomalies, such as packet loss, in any collection period, the traffic on the wireless access network device side is the data network twice the flow on the side.
  • the above-mentioned improvement in reliability is the result of the additional investment of network resources by the operator.
  • the second channel PDU session supported by NG-RAN 104 and UPF 107 in FIG. 1 N3 tunnel 2 between NG-RAN 203 and UPF 205 in FIG. 2A , and between NG-RAN 203 and UPF 205 in FIG. 2B N3 tunnel 2 and N9 tunnel 2, and the second transport layer path between NG-RAN 303 and UPF 305 in Figure 3, etc. Therefore, the charging processing device should provide a new charging capability, for example, perform charging processing for the extra traffic caused by redundant transmission, so that the operator can charge for the extra network resources invested by it.
  • the billing processing device also needs to distinguish which usage is the original usage without redundant transmission, and which is the reason.
  • FIG. 4A is an architectural diagram of a first communication system provided by an embodiment of the application, which includes a user equipment 411 , a wireless network access device 412 , a user plane data gateway 413 , a data network 414 , a charging processing device 402 , and a charging triggering device 401 ;
  • the charging triggering device 401 and the charging processing device 402 form a charging processing system, which includes performing charging processing on the data connection session 415.
  • the billing processing system further includes a policy control device (not shown in FIG. 4A ), a bill management device (not shown in FIG. 4A ), and the like. The following is a brief introduction to some of these devices.
  • User equipment 411 a device of an end user, connected to the wireless network device 412 through an air interface (Note: “connected” or “connected” in the embodiments of this application include direct connection or indirect connection, the latter refers to one or more is responsible for initiating the creation or dismantling of the data connection session 415; communicates with the device or server in the data network 414 through the data connection session 415 to provide end users with diversified services, Such as voice calls, video playback, etc.;
  • the user equipment 411 may be a UE (user equipment, user equipment) defined by the 3GPP standard specification; exemplary user equipment includes: a smart phone, a laptop with a wireless communication function (Laptop), a tablet computer, a wearable device, an AR (Augmented Reality, Augmented Reality) devices, IoT (Internet of Things, Internet of Everything) devices, etc.
  • UE user equipment, user equipment
  • 3GPP standard specification 3GPP standard specification
  • exemplary user equipment includes: a smart phone, a laptop with a wireless communication function (Laptop), a tablet computer, a wearable device, an AR (Augmented Reality, Augmented Reality) devices, IoT (Internet of Things, Internet of Everything) devices, etc.
  • the communication system shown in FIG. 4A may have more user equipments.
  • the wireless access network device 412 is a network element in the wireless access network, responsible for sending radio frequency signals to or receiving radio frequency signals from the user equipment 411, so as to send the data packets of the user plane data gateway 413 to the user equipment 411 or Send the data packet sent by the user equipment 411 to the user plane data gateway 413; usually the NG-RAN defined by the 3GPP standard specification, including but not limited to eNB (evolved NodeB, evolved base station), gNB (gNodeB, 5G base station); It is understood that, in practical applications, there may be more wireless access network devices in the communication system shown in FIG. 4A .
  • eNB evolved NodeB, evolved base station
  • gNB gNodeB, 5G base station
  • User plane data gateway 413 is a network element in the core network, and transmits data packets from user equipment 411 via wireless access network equipment 412 to data network 414, or transmits data packets sent by data network 414 to wireless access
  • the network equipment 412, and then transmitted to the user equipment 411 are usually UPF equipment, PGW-U (packet data network gateway for user plane, user plane packet data gateway) or SGW-U (serving gateway for user plane) defined by the 3GPP standard specification, User plane service gateway); it should be understood that in practical applications, there may be more user plane data gateways in the communication system shown in FIG. 4A .
  • Data network 414 a network used for data transmission and composed of a data switch as a transfer point, such as the Internet, which includes an application server (not shown in FIG. 4A ), which are various APPs (Application, application) to provide a service or capability.
  • an application server not shown in FIG. 4A
  • APPs Application, application
  • the data connection session 415 is an association between the user equipment 411 and the data network 414 (English: association between the UE and a data network that provides a connectivity service), used to provide communication between the user equipment 411 and the data network 414 connection service to transmit packets between user equipment, radio access network equipment, user plane data gateway and data network; its creation process can be initiated by user equipment 411, and its teardown process can be initiated by user equipment 411, It can also be initiated by other network devices.
  • the data connection session 415 may be a PDU session under the 5G network architecture, or may be an IP-CAN (IP-connectivity access network, IP connectivity access network) session under the 4G (4th generation, fourth generation) network architecture, or It may be other forms of sessions between the user equipment and the data network, which are not limited in this embodiment of the present application.
  • IP-CAN IP-connectivity access network, IP connectivity access network
  • the data connection session is also referred to as a "session" for short.
  • Charging trigger device 401 a device that collects charging information for data in the data connection session 415 and reports charging information to the charging processing device, and is connected to the user plane data gateway 413 and the charging processing device 402 respectively.
  • the main functions include:
  • the charging trigger device 401 can also transmit the data connection services in the data connection session 415 to the traffic on different sides of the user plane data gateway 413. and description information (such as describing which side of the traffic) is reported to the charging processing device 402.
  • the charging trigger device 401 includes a CTF (Charging Trigger Function, charging trigger function) defined by the 3GPP standard specification.
  • the charging trigger device 401 can be deployed in an SMF device (that is, a control plane gateway) defined by the 3GPP standard specification, or can be deployed in other devices with the same or similar functions as the SMF device, such as PGW-C (packet data network gateway for control plane, packet user plane data gateway on the control plane), SGW-C (serving gateway for control plane, service gateway on the control plane), and can also be deployed in other data connection sessions that can obtain information such as usage, redundant transmission methods, etc. In other devices; the embodiment of this application does not limit the physical deployment mode of the charging trigger device 401 .
  • the communication system shown in FIG. 4A may have more charging triggering devices.
  • the charging trigger device is sometimes referred to as “CTF device” or “CTF” for short in the embodiments of this application; in the scenario where the CTF device is deployed on the SMF device, the “SMF device” or “SMF” is also directly used. It refers to “CTF device”, which will not be repeated in subsequent embodiments.
  • Charging processing device 402 a device that performs charging processing on the data connection service in the data connection session 415 based on the information sent by the charging triggering device (including the charging triggering device 401 and other charging triggering devices not shown in FIG. 4A ) , the main functions include:
  • (2.2) based on the redundant transmission information, determine the redundant service charging processing mode for the data connection session 415 or the data connection service therein, and then determine the usage management mode that satisfies the requirements of the redundant service charging processing mode, And send instruction information to the charging trigger device, so that the charging trigger device can perform quota management, usage collection and reporting according to the specified usage management method; optionally, it can also be combined with other information, such as user subscription information, charging Process the local storage policy of the device, etc., and determine the usage management method;
  • the charging processing device can also determine accordingly. Corresponding data connection services are redundantly transmitted, and then charging processing is performed according to the charging policy.
  • the charging processing device 402 may be implemented based on the CHF (Charging Function, charging function) device defined by the current 3GPP standard specification, or may be implemented based on the CCS (Converged Charging System, converged charging system) device defined by the current 3GPP standard specification (which includes The function of the CHF device) can also be realized based on other devices with the same or similar functions as the CHF device or the CCS device; in addition, the charging processing device 402 can be deployed in a physical device alone, or can be deployed together with other functional devices. In the same physical device; the embodiment of the present application does not limit the physical deployment manner of the charging processing device 402 .
  • CHF Charging Function, charging function
  • CCS Converged Charging System, converged charging system
  • the charging processing device is sometimes referred to as "CHF device” or “CHF” for short.
  • Traffic refers to the number of bits transmitted by a user plane data gateway (such as a UPF device) within a specific time range (such as a collection period).
  • Usage amount refers to the traffic reported to the charging processing device (such as a CHF device) for charging processing; in this embodiment of the present application, the usage usage information includes usage amount and usage amount description information.
  • QoS flow It is the minimum granularity forwarding processing of QoS differentiation in the PDU session.
  • QFI QoS Flow identifier, QoS flow identifier
  • Redundantly transmitted traffic refers to the traffic transmitted on any one of the two mutually redundant transmission channels.
  • Data connection service a collection of service data streams in a data connection session, which can have any of the following granularities:
  • Data connection session granularity that is, the service data flow in the data connection service is the service data flow in the data connection session
  • QoS flow granularity that is, the service data flow in the data connection service is the service data flow in a certain QoS flow in the data connection session
  • rate group granularity that is, the service data flow in the data connection service is the service data flow in a certain rate group in the data connection session
  • Service granularity in the rate group that is, the service data flow in the data connection service is the service data flow corresponding to a certain service identifier in a certain rate group in the data connection session.
  • the data connection service is sometimes referred to as “service” or “data service” for short.
  • service data streams constituting the data connection service in the embodiments of the present application all refer to service data streams that require charging processing, and do not include service data streams that are free or do not require charging processing.
  • Data connection service with redundant transmission also known as redundant data connection service, refers to the data connection service for which the communication network implements or uses redundant transmission, not only includes the data connection service for which redundant transmission in S2 or S3 mode is implemented , and also includes a data connection service that is redundantly transmitted in the S1 mode (ie, the data in the data connection service is also redundantly transmitted in another data connection session).
  • Redundant Transmission Mode Abbreviation for network implementation of redundant transmission, including at least session redundancy (S1), tunnel redundancy (S2) or transport layer redundancy (S3) described above ); "redundant transmission mode of data connection session” or “redundant transmission mode of data connection service” refers to the network implementation mode of redundant transmission implemented or used by the communication network for the data connection session or data connection service. It should be understood that the redundant transmission mode may also sometimes be referred to as a "redundant transmission type".
  • Redundant Transmission Information refers to information related to redundant transmission; the redundant transmission information of a data connection session or a data connection service in the data connection session can only indicate whether the communication network is Implement or use redundant transmission for the data connection session or the data connection service in the data connection session, or whether the transmission of the data connection session or the data connection service in the data connection session is a redundant transmission, or only indicate or Further indicate the redundant transmission mode of the data connection session or the data connection service in the data connection session; optionally, in the case that the redundant transmission mode is indicated as session redundancy, the data connection session can be further instructed in two The "status" in a mutually redundant data connection session (or indicating the role of the data connection session in the redundant transmission, such as the master data connection session, the slave data connection session), or further indicating the interaction with the data connection session Information about another data connection session that is redundant, such as the identifier of the other data connection session, the address or identifier of the user plane data gateway of the other data connection session, and the like.
  • redundant transmission information also refers to usage information from which redundant transmissions can be deduced; collected), it can also be regarded as a kind of redundant transmission information; for example, if the usage of the user plane data gateway on the wireless access network is twice the usage on the data network side, the billing processing device can determine that The data connection service corresponding to the usage is the redundant transmission in the S2 or S3 mode.
  • Redundant usage refers to the additional data traffic transmitted by the data connection service due to redundant transmission during a specific collection period.
  • Basic usage refers to the data traffic of the data connection service assuming no redundant transmission during a specific collection period.
  • the sources of redundant usage and basic usage are relative; in S1 mode, in the mutually redundant A and B data connection sessions, if part or all of A's data connection session The traffic (in the collection period) is regarded as the basic usage, then the corresponding part of the traffic in the B data connection session or all of the traffic (in the collection period) is regarded as the redundant usage, and vice versa; similarly, in S2 In this mode, in the mutually redundant A and B tunnels, if part or all of the traffic in the A tunnel is regarded as the basic usage, then the corresponding part or all of the traffic in the B tunnel is regarded as redundant.
  • Redundant service charging processing method refers to the charging processing device for the redundant transmission data connection service charging processing method, including "including redundant charging processing” and “removing redundant charging processing”. point.
  • Billing processing with redundancy refers to the billing processing device that performs billing processing on both the basic usage and redundant usage of redundantly transmitted data connection services, such as account deduction or CDR writing, among which, Basic usage and redundant usage can be at the same rate or at different rates, depending on the operator's billing policy.
  • the billing processing device only performs billing processing on the basic usage of redundantly transmitted data connection services, such as: deducting the basic usage with a specific rate, writing the bills to the account etc., no redundant usage is processed.
  • Redundant usage processing refers to the management of the quota and/or usage of redundantly transmitted data connection services by the billing-triggered device.
  • the redundant usage processing method is the specific method of redundant usage processing. The method is divided into “processing with redundant usage” and “processing with redundant usage removed”.
  • Processing of usage with redundancy refers to making the reported usage include redundant usage (S2/S3), or to make the reported usage meet the requirements of the billing processing device to perform billing processing including redundancy (S1). ), the processing operation that the charging triggers the device to take on the data traffic of the redundantly transmitted data connection service. See the examples of this application.
  • Removing redundant usage processing refers to the requirement that the reported usage does not include redundant usage (S2/S3), or that the reported usage meets the requirements of the billing processing device to perform redundant-removing billing processing (S2/S3).
  • S1 the processing operation performed by the charging trigger device on the data traffic of the redundantly transmitted data connection service.
  • the processing operation may be different due to different charging modes and redundant transmission modes. For details, refer to the embodiments of the present application.
  • the charging processing device 402 can acquire the data connection session 415 or the redundancy of the data connection service in the data connection session through the charging triggering device 401 deployed on the SMF device or the PGW-C.
  • the related information transmitted, and the charging processing is performed accordingly.
  • billing triggering device refers to “Device” refers to the billing processing device 402
  • User Equipment refers to the User Equipment 411
  • Radio Access Network Device refers to the Wireless Access Network Device 412
  • User Plane Data Gateway refers to the User Plane Data Gateway 413
  • Data Network refers to the data network 414
  • data connection session refers to the data connection session 415, which will not be repeated here.
  • FIG. 4B is a flowchart of a first method for performing charging processing on redundantly transmitted data connection services provided by an embodiment of the present application.
  • the charging processing device determines, according to the redundant transmission information reported by the charging triggering device, that there is redundant transmission of the data connection service in the data connection session, and performs charging processing accordingly.
  • the interaction between the charging triggering device and the charging processing device has the following possible solutions:
  • the charging processing device determines that the data connection session needs charging processing based on the redundant transmission information, and the charging processing device interacts with the charging triggering device for charging processing. Specifically, there are the following possible solutions:
  • the charging trigger device reports the combined usage amount to the charging processing device by default, and the charging processing device performs charging processing based on the reported combined usage amount according to the redundant service charging processing method determined by it;
  • the charging processing device delivers usage processing indication information to the charging triggering device according to the needs of the redundant service charging processing method, and the charging triggering device manages the quota according to the indication information, obtains and reports the basic usage, or obtains And report the basic usage and redundant usage.
  • the charging processing device determines that the redundant charging processing will be performed, and further determines that the redundant data connection session does not require charging processing, and terminates or suspends the charging processing with the charging trigger device. interaction.
  • Step 430 The charging triggering device sends a first charging request message to the charging processing device, where the request message includes redundant transmission information.
  • the charging triggering device acquires redundant transmission information, that is, redundant transmission information implemented or used by the communication network for the first data connection service in the data connection session, and sends a first charging request to the charging processing device message, the request message contains the redundant transmission information; of course, in addition to the redundant transmission information, those skilled in the art know that the charging request message may also contain other information related to the data connection session.
  • Information such as the identifier of the first data connection session, the information of the first data connection service, and the like.
  • the granularity of the first data connection service in this application may be the granularity of the data connection session, or may be the granularity of the QoS flow in the data connection session, which will not be repeated.
  • the redundant data connection session is used.
  • S2 mode it means that the data connection service uses a redundant transmission tunnel
  • S3 mode it means that a redundant transmission layer path is used.
  • the redundant transmission information may also be information that implicitly indicates that the first data connection service uses redundant transmission, for example, the charging triggering device defaults to the charging processing device simultaneously Report the combined usage (for example, in the S2 or S3 mode, the traffic transmitted between the user plane data gateway and the wireless access network device) and the basic usage amount (for example, in the S2 or S3 mode, between the user plane data gateway and the data network) based on the reported combined usage and basic usage, the billing processing device determines that the first data connection service is a redundantly transmitted data connection service, then the combined usage and the basic usage together form the redundant transmission information.
  • the charging triggering device defaults to the charging processing device simultaneously Report the combined usage (for example, in the S2 or S3 mode, the traffic transmitted between the user plane data gateway and the wireless access network device) and the basic usage amount (for example, in the S2 or S3 mode, between the user plane data gateway and the data network) based on the reported combined usage and basic usage, the billing processing device determines that the first data connection service is a redundantly transmitted
  • the redundant transmission information may also indicate a redundant transmission mode of the first data connection service, such as session redundancy, tunnel redundancy or transport layer redundancy;
  • the redundant transmission information may further indicate the "status" of the data connection session or a role in redundant transmission, for example, indicating that the data connection session is the primary data connection session Either from the data connection session, or indicate the relevant information of another data connection session that is redundant with the data connection session, such as the identifier of the other data connection session, the address or identifier of the corresponding user plane data gateway, and the like.
  • the first charging request message may further include the transmission delay of the first data connection service.
  • the charging request message may specifically be a charging resource creation request message or a charging resource update request message, which will not be described again.
  • the manner in which the charging trigger device obtains redundant transmission information is not limited.
  • the charging trigger device can use the DNN (Data Network Name, data network name) or S-NSSAI (Single Network Slice Selection Assistance) contained in the data connection session establishment request message.
  • Step 440 The charging processing device performs charging processing based on the redundant transmission information.
  • the charging processing device receives and parses the first charging request message, obtains the redundant transmission information and other information related to the data connection session, and then performs charging processing.
  • the specific processing process is as follows.
  • the fee processing device determines that the first data connection service has redundant transmission, and further combines the user subscription information, etc., to determine the redundant service charging processing method for the data connection service: including redundant charging Process or remove redundant billing processing.
  • the charging processing device further performs the following operations.
  • the charging processing device receives the combined usage amount from the charging triggering device, and performs the charging processing including redundancy or the charging processing removing the redundancy for the combined usage amount.
  • the charging processing device may acquire the combined usage amount from the first charging request message, or may receive another charging request message from the charging trigger device, and acquire the combined usage amount therefrom.
  • the charging processing device directly performs charging processing on the combined usage (that is, without distinguishing between the basic usage and the redundant usage). , or separate the basic usage and redundant usage from the combined usage, and then perform billing processing separately, including but not limited to using different rates for the basic usage and redundant usage, for example,
  • the billing processing device may use half of the combined usage as the basic usage, and charge at the rate 1, and use the other half as the redundant usage, and charge at the rate 2.
  • the charging processing device obtains the basic usage amount from the combined usage amount, and performs charging processing on the basic usage amount. For example, if the combined usage reported by the charging trigger device is 4M, then half of the combined usage, 2M, is used as the basic usage, and then the 2M basic usage is charged.
  • the charging processing device further grants a quota for the first data connection service (which may be based on the charging trigger sent by the device).
  • the quota application is passively granted, or it can be granted actively without receiving the quota application sent by the charging trigger device); the quota can be twice the quota actually reserved by the charging processing device in the corresponding account (this can reduce the The number of times the charging triggering device requests quota from the charging processing device), which may also be equal to the actual reserved quota; optionally, the charging processing device may also generate first processing indication information corresponding to the quota, the indication information Instruct (instruct) the charging trigger device to set a redundancy mark for the usage amount corresponding to the quota, where the redundancy mark indicates that the usage amount corresponding to the quota is the usage amount of the redundantly transmitted data connection service; the charging processing device The first processing indication information may be sent to the charging triggering device together
  • the charging processing device sends the usage processing indication information to the charging triggering device, so that the charging triggering device executes the redundant usage processing or the redundant usage processing, so as to satisfy the requirements of the redundant usage processing respectively.
  • the charging processing device generates second processing indication information based on the determined charging processing method for the redundant service: if the charging processing method for the redundant service is the charging processing including redundancy, the second processing indication information The information instructs the charging trigger device to perform a redundant usage processing operation for the second data connection service in the data connection session; if the redundant service charging processing method is to remove the redundant charging processing, then The second processing indication information instructs the charging trigger device to perform a redundant usage processing operation for the second data connection service.
  • the rate between the second data connection service and the first data connection service corresponds to or corresponds to the QoS flow in the first data connection service or corresponds to the data connection session corresponding to the first data connection service.
  • the second data connection service corresponds to the tariff group in the first data connection service, or the corresponding to the QoS flow corresponding to the first data connection service.
  • the billing processing device calculates the ratio between the usage amounts on both sides of the user plane data gateway.
  • the usage amount is 2 times of the usage amount between the user plane data gateway and the data network, then it is determined that the first data connection service has redundant transmission in the S2 or S3 mode, and then the redundant service charging processing mode is determined, and then based on
  • the usage on both sides of the user plane data gateway performs charging processing including redundancy or removing redundancy; the charging processing device can regard the usage between the user plane data gateway and the wireless access network device as a combination
  • the usage between the user plane data gateway and the data network is regarded as the basic usage; how to perform the charging process that includes redundancy or removes the redundant charging process, please refer to the paragraph (1.1) of this step. relevant description;
  • the charging processing device After the charging processing including redundancy or the charging processing for removing redundancy is successful, the charging processing device generates the indication information of successful account deduction (for online charging) or the indication information of successful CDR writing (for offline charging). ).
  • the charging processing device can select one of the two mutually redundant data connection sessions to perform charging The processing is as follows.
  • the charging processing device may generate non-charging indication information, and the indication information is used to indicate to the charging triggering device the accounting The charging processing device does not perform charging processing on the data connection session because it is a slave data connection session;
  • the charging processing device chooses to perform charging on the other data connection session, then generating non-billing indication information for the data connection session, the indication information is used to indicate to the charging triggering device to perform charging for the data connection session that is mutually redundant with the data connection session without charging the data
  • the connection session performs accounting processing.
  • the charging processing device does not necessarily choose not to charge the data connection session; regarding the choice between these two data connection sessions, this application
  • the embodiment does not limit the specific selection method; the charging processing device may randomly select a data connection session, or may select a data connection session with a lower transmission delay, if the two data connection sessions are in different network slices, the The data connection session with the higher priority of the network slice where it is located can be selected; the charging processing device can obtain the transmission delay of the data connection session from the charging request sent by the charging trigger device, and obtain the location of the data connection session from the network slice management device. The priority of the network slice.
  • the non-accounting indication information in the above two points may be represented in various ways, for example, it may be composed of "failure to create charging resources" and "indication information that the reason for the failure is that the data connection session is not charged", please refer to the follow-up of this application for details. Example.
  • the charging processing device performs charging processing according to the redundant transmission information and the transmission delay; for example, the charging processing device performs charging processing according to the The transmission delay selects a data connection session that needs to be billed or a data connection session that does not need to be billed; for another example, the charging processing device performs the above-mentioned redundant charging processing or includes redundant charging During the processing, the billing rate for the usage is determined according to the transmission delay; for another example, the billing processing device selects the usage to be billed according to the transmission delay (for example, in the S2 mode, the billing triggers The device can report the usage in each transmission tunnel and the corresponding transmission delay respectively, and the billing processing device selects the usage corresponding to the smaller transmission delay).
  • the method further includes: the charging processing device writes the information of the first data connection service into a bill, and the information of the first data connection service includes any one of the following Item: redundant transmission information, usage description information, or transmission delay (if the first charging request message includes the transmission delay).
  • Step 450 The charging processing device sends a first charging response message to the charging triggering device, where the first charging response message includes the result of the charging processing.
  • the charging processing device constructs and sends a first charging response message to the charging triggering device, where the response message includes the charging processing result and is one of the following items:
  • the charging response message may specifically be a charging resource creation response message or a charging resource update response message, which will not be described again.
  • the first charging response message may be a response message corresponding to the charging request message in step 430, or may be a response message corresponding to other charging request messages.
  • the charging triggering device receives and parses the first charging response message, obtains the charging processing result provided by the charging processing device, and performs further operations based on the charging processing result, and the specific operations are as follows.
  • the charging trigger device manages the consumption of the quota and obtains the usage amount corresponding to the quota (for combined usage), and send the usage and the redundant flag to the charging processing device through a second charging request message; then the charging processing device receives and parses the second charging request message, according to the In the redundant flag, the billing process that includes redundancy or the billing process that removes redundancy is performed on the usage amount. If the charging processing result does not contain the redundant flag, the charging processing device may perform charging processing including redundancy or removing redundant charging for the usage according to the redundant flag stored locally in step 440 deal with. Regarding the charging processing including redundancy and the charging processing removing redundancy, reference may be made to the relevant description in step 440 .
  • the charging triggering device uses the redundancy indicated by the second processing indication information according to the difference in the redundant transmission mode.
  • different processing is carried out, as follows:
  • the charging processing device performs the following operations according to the instruction:
  • the usage amount of the second data connection service consumes the quota granted by the charging processing device.
  • the charging processing device performs the following operations according to the indication:
  • the usage of the second data connection service consumes the quota granted by the charging processing device.
  • the traffic of the redundant transmission of the second data connection service in the data connection session in the S1 mode, refers to the traffic of the second data connection service transmitted in the data connection session.
  • the traffic of the second data connection service transmitted between the user plane data gateway corresponding to the data connection session and the wireless access network device in the S1 mode, refers to the traffic of the second data connection service transmitted between the user plane data gateway corresponding to the data connection session and the wireless access network device.
  • the charging processing device performs the following operations according to the instruction:
  • the quota granted by the charging processing device is also consumed by the usage of the second data connection service (that is, the traffic of the second data connection service transmitted between the user plane data gateway and the data network).
  • the charging processing device performs the following operations according to the instruction:
  • the consumption meter is also calculated by the usage of the second data connection service (that is, the flow of the second data connection service transmitted between the user plane data gateway and the wireless access network device). The quota granted by the fee processing device.
  • the redundant transmission mode of the first data connection service is tunnel redundancy or transport layer redundancy, it can also be processed as follows:
  • the charging processing device performs the following operations according to the instruction:
  • the quota granted by the charging processing device is also consumed by the usage amount of the second data connection service (that is, the flow of the second data connection service transmitted through one of the two mutually redundant transmission paths).
  • the method for selecting a transmission path is not limited in this embodiment of the present application; the charging trigger device may randomly select one of the above two transmission paths, or may select the one with a lower transmission delay. If the two transmission paths are on different networks In the slice, the transmission path with higher priority of the network slice where it is located can also be selected; the charging trigger device can obtain the transmission delay of the transmission path from the user plane data gateway.
  • the charging processing device performs the following operations according to the indication:
  • the quota granted by the charging processing device is consumed by the usage amount of the second data connection service (that is, the flow of the second data connection service transmitted through the two mutually redundant transmission paths).
  • two mutually redundant transmission paths refers to two transmission tunnels in the S2 mode, and refers to two transmission layer paths in the S3 mode.
  • traffic refers to the traffic generated within the time interval (or within the collection period) between two reports of usage.
  • the charging triggering device After obtaining the usage amount, the charging triggering device sends it to the charging processing device through another charging request message.
  • the charging trigger device may also be the obtained usage amount (for example, the usage amount corresponding to the rate group in the first data connection service, or the usage amount corresponding to the QoS flow in the first data connection service. usage amount) to generate usage amount description information and send it to the billing processing device together with the acquired usage amount, the usage amount description information is used to describe whether the usage amount is used for performing redundant-removing usage amount processing Traffic, or describe where the traffic occurs, for example, the usage description information indicates any of the following:
  • the traffic may be: the traffic for which the redundant usage processing is not performed or the traffic after the redundant usage processing is performed;
  • the usage is the traffic of which side of the user plane data gateway, specifically: the traffic transmitted between the user plane data gateway and the wireless access network device or the traffic transmitted between the user plane data gateway and the data network.
  • the charging triggering device terminates or suspends charging, for example, quota management, usage collection, and the charging processing device are Interactions for charging processing (for example, requesting quotas from charging processing equipment, sending charging data such as usage).
  • the charging triggering device may monitor the data connection session, and once it finds that the data connection session has become the primary data connection session, it sends a third charging request message to the charging processing device, which includes that the data connection session is: Indication information of the primary data connection session, which can be represented by the redundant transmission information described above.
  • the method by which the charging trigger device obtains the usage of the data connection service is not limited.
  • the charging trigger device may obtain the usage from the message actively reported by the user plane data gateway, or may send the data to the user plane data gateway. Get the usage request message, and then get the usage from the corresponding response message or notification message.
  • the request message for obtaining the usage amount may specify which side of the user plane data gateway traffic is required.
  • the request message may include the indication information of "NG-GW", indicating that it is necessary to obtain the traffic between the wireless access network device and the data gateway.
  • the traffic transmitted between the user plane data gateways, or the indication information including "GW-DN" indicates that the traffic transmitted between the user plane data gateway and the data network needs to be obtained.
  • the method flow of FIG. 4B enables the charging processing device to know the redundant transmission of the data connection service through the charging trigger device, and perform charging processing based on the redundant transmission, which is helpful to improve the accuracy of charging and satisfy the Diversified billing needs of operators or end users.
  • FIG. 5 is an architectural diagram of a second communication system provided by an embodiment of the present application.
  • the communication system is formed on the basis of the communication system shown in FIG. 4A , using the device defined by the 3GPP standard specification for each device as an example.
  • the user equipment 411 takes the UE 511 as an example
  • the access network device 412 takes the gNB 512 as an example
  • the user plane data gateway 413 takes the UPF device 513 as an example
  • the data network 414 takes the DN 514 as an example.
  • the SMF device 501 is taken as an example
  • the charging processing device 402 is taken as an example of the CHF device 502
  • the data connection session 415 is taken as an example of the PDU session 515, as shown in FIG. 5 .
  • UPF device 513 communicates with gNB 512 through N3 interface, DN 514 through N6 interface, SMF device 501 through N4 interface, and SMF device 501 communicates with CHF device 502 through N40 interface.
  • SMSF refers to the SMF device 501
  • CHF refers to the CHF device 502
  • UE refers to the ” refers to UE 511
  • gNB refers to gNB 512
  • UPF UPF device 513
  • DN refers to DN 514
  • PDU Session refers to PDU Session 512.
  • CTF CTF
  • 6A is a flowchart of a second method for performing charging processing on redundantly transmitted data connection services provided by an embodiment of the present application, which is used for performing charging processing on the first data connection services in a PDU session.
  • the combined usage amount is used for charging processing including redundancy or removing redundancy charging processing; the method flow mainly includes the following steps:
  • Step 601 The SMF generates redundant transmission information RTI61 for the first data connection service.
  • the granularity of the first data connection service is PDU session granularity or QoS flow granularity.
  • the SMF may only determine that there is redundant transmission of the first data connection service, and the generated RTI61 may only indicate that the transmission of the first data connection service is redundant transmission;
  • redundant transmission for the S1 mode, it means that the first data connection service uses a redundant PDU session, and for the S2 mode, it means that the first data connection service uses a redundant N3/N9 transmission tunnel , for the S3 mode, it means that the first data connection service uses a redundant transport layer path;
  • RTI61 is as follows:
  • the SMF may further determine the redundant transmission mode of the PDU session, and the generated RTI61 further indicates the redundant transmission mode of the first data connection service.
  • Exemplary RTI61 are as follows:
  • SMF determines that the PDU session requires a redundant PDU session according to the DNN or S-NSSAI in the PDU session establishment request and the local configuration information, and reports to the wireless network access device (such as NG- RAN 103) sends an instruction to establish a dual connection, if the wireless network access device successfully establishes a dual connection (the response message received by the NG-RAN carries a success indication or does not carry a failure indication), then the SMF determines that the PDU session is Redundant PDU sessions.
  • the wireless network access device such as NG- RAN 103
  • the SMF determines the authorization-based 5QI (5G QoS Indicator, 5G QoS identifier), NG-RAN capability and/or operator configuration information for redundant transmission of the first data connection service, the SMF notifies the PSA UPF through the N4 interface and the NG-RAN through the N2 interface for redundant transmission .
  • the redundant transmission mode is S3 mode: when the UE establishes a PDU session for the URLLC service, the SMF selects a PDU session that supports redundant transmission at the transport layer based on the capability of DNN, S-NSSAI, and NG-RAN to support redundant transmission at the transport layer.
  • UPF to establish two mutually redundant transport layer paths between UPF and NG-RAN.
  • the generated RTI61 may further indicate that the PDU session is a master PDU session or a slave PDU session, or indicate the relevant information of another PDU session that is redundant with the PDU session, such as the information of another PDU session. ID, address or ID of the corresponding user plane data gateway, etc.
  • Exemplary RTI61 are as follows:
  • the SMF determines that the first data connection service is an online charging service (that is, a data connection service that requires online charging), go to step 602;
  • the SMF determines that the first data connection service is an offline charging service (ie, a data connection service that requires offline charging), then go to step 610 .
  • an offline charging service ie, a data connection service that requires offline charging
  • Step 602 The SMF sends a charging request message to the CHF, where the request message includes the RTI61, the identifier SesId61 of the PDU session, and the quota application RSU61 (optional).
  • the SMF constructs a charging request message and sends it to the CHF, which includes RTI61 and SesId61; optionally, the charging request message further includes RSU61, where RSU61 is used for One or more rate groups apply for quota.
  • the charging request message further includes a transmission delay.
  • an exemplary message structure is as follows:
  • RTI redundant transmission information
  • data connection services for example: for S1 mode or S3 mode, RTI can correspond to PDU session identifier; for S2 mode, RTI can correspond to QoS corresponding to the stream ID.
  • the charging request message may further include the transmission delay of the first data connection service.
  • the first data connection service corresponds to a PDU session or a QoS flow
  • the example representations of the transmission delay are as follows:
  • the embodiment of the present application refers to the transmission delay corresponding to the PDU session as "the transmission delay of the PDU session granularity”.
  • QFI Qosflow61
  • the embodiment of the present application refers to the transmission delay corresponding to the QoS flow as "transmission delay of QoS granularity”.
  • Step 603 The CHF determines the redundant service charging processing mode RCM61 according to the RTI61 and/or the transmission delay.
  • the CHF receives and parses the charging request message, and obtains RTI61, SesId61 and RSU61 (if any) and the transmission delay (if any) therefrom. Based on the RTI61, the CHF determines that the transmission of the first data connection service is redundant transmission. The CHF further determines the redundant service charging processing mode RCM61 for the first data connection service according to the CHF charging policy or user subscription information and/or the transmission delay (if any); for example, the CHF may The RTI and the user subscription information determine that charging processing including redundancy is used for the first data connection service, or it may be determined that charging processing that removes redundancy is used for it; CHF may also be used when the transmission delay is higher than a preset value. When the threshold value is reached, it is determined to adopt the charging processing including redundancy, and when the transmission delay is lower than the preset threshold value, it is determined to adopt the charging processing that removes the redundancy.
  • Step 604 The CHF grants the quota GSU61 according to the RCM61.
  • the quota actually reserved by CHF in the user account is A, then: if the RCM61 is the charging process that includes redundancy, then the GSU61 is A; if the RCM61 is the charging process that removes the redundancy, then the GSU61 can be A, can also be 2A.
  • the CHF may also generate corresponding processing indication information ProcInd (corresponding to the first processing indication information above) for the GSU61, which is used to instruct the SMF to set a redundancy flag for the usage amount corresponding to the GSU61, so that the subsequent CHF will use the corresponding usage amount of the GSU61.
  • the amount of data connection service usage of the redundant transmission is performed to include the redundant charging process or to perform the redundant charging process.
  • the CHF may grant the above-mentioned quota for the first data connection service based on the RSU61.
  • Step 605 The CHF returns a charging response message to the SMF, where the response message includes GSU61 and ProcInd (optional).
  • the CHF constructs a charging response message and sends it to the SMF, the response message includes GSU61, and optionally, the response message also includes ProcInd. If the charging response message does not contain ProcInd, the CHF may generate a redundant flag Uflg for the GSU61, and locally store the identifier of the GSU61 corresponding to Uflg, where the redundant flag Uflg is used to indicate the usage of the GSU61 The usage of data connection traffic for redundant transmission.
  • An exemplary charging response message is as follows:
  • Step 606 The SMF acquires the usage USU61 corresponding to the GSU61.
  • the SMF receives and parses the above charging response message, obtains the GSU61 and ProcInd (if any) therefrom, and then consumes the GSU61 for the first data connection service, and records the usage USU61 of the GSU61.
  • SMF can use the traffic consumption quota GSU61 in the column "Data Traffic” in Table 1 (where the data connection service is the first data connection service), and record the corresponding usage USU61.
  • the SMF can send the GSU61 to the UPF (so that the UPF can release the service data flow with the GSU61 as the limit).
  • the SMF also generates a redundancy flag Uflg for the USU 61 to indicate (indicate) the usage of the data connection service that the USU 61 transmits redundantly.
  • Step 607 SMF sends a charging request message to CHF, where the request message includes USU61, redundancy flag Uflg (optional) and transmission delay (optional).
  • the SMF constructs a charging request message and sends it to the CHF, and the update request message includes USU61, Uflg (if ProcInd was previously issued by the CHF) and transmission delay (optional).
  • An exemplary charging request message is as follows:
  • Uflg corresponds to USU61, and the specific data structure is not limited.
  • the charging request message further includes a transmission delay
  • the transmission delay is the transmission delay of the PDU session granularity or the transmission delay of the QoS flow granularity in the reporting period corresponding to the sending of the charging request message.
  • the transmission delay may correspond to a PDU session identifier, a QoS flow identifier or a rate group in the charging request message.
  • Step 608 CHF debits the account based on USU61 according to RCM61/Uflg.
  • the CHF receives and parses the charging request message from the SMF, and obtains the USU61, Uflg (if any) and transmission delay (optional) therefrom. Furthermore, CHF performs account deduction based on USU61 according to RCM61/Uflg/Delay.
  • the CHF determines that the USU61 is the usage of the redundantly transmitted data connection service, and further determines that the USU61 needs to be debited from the account according to the RCM61. If RCM61 is a billing process that includes redundancy, CHF deducts the usage (2M) corresponding to USU61 or the corresponding fee in the account corresponding to rate group RG1; if RCM61 is a billing process that removes redundancy, CHF will Half of the usage amount corresponding to USU61 or the corresponding fee will be deducted from the account.
  • RCM61 is a billing process that includes redundancy
  • CHF deducts the usage (2M) corresponding to USU61 or the corresponding fee in the account corresponding to rate group RG1
  • RCM61 is a billing process that removes redundancy, CHF will Half of the usage amount corresponding to USU61 or the corresponding fee will be deducted from the account.
  • CHF instructs SMF to set the redundancy flag Uflg for USU61 through ProcInd, which can more accurately identify whether the usage includes redundant traffic, and then flexibly grant quota and usage processing according to the billing requirements of redundant transmission, such as : Only some of the data connection services are charged with redundancy including or without redundancy, and other data connection services are charged according to the traditional charging method.
  • the CHF may further determine the rate used in the account deduction process according to the transmission delay.
  • Step 609 The CHF sends a charging response message to the SMF, where the response message includes indication information that the account deduction is successful. If there is an granted quota, the same as step 605 .
  • the SMF can continue to apply for the quota and/or report the new usage amount to the CHF through the charging request message.
  • Step 610 The SMF sends a charging request message to the CHF, where the request message includes the RTI61 and the identifier SesId61 of the PDU session.
  • the SMF constructs a charging request message and sends it to the CHF, which includes RTI61 and SesId6, and optionally, transmission delay.
  • the billing request message is a billing resource creation request
  • an example of the message is as follows:
  • RTI redundant transmission information
  • data connection services for example: for S1 mode or S3 mode, RTI can correspond to PDU session identifier; for S2 mode, RTI can correspond to QoS corresponding to the stream ID.
  • Step 611 The CHF determines the redundant service charging processing mode RCM62 according to the RTI61 and other information.
  • This step is similar to step 603 and will not be repeated here.
  • Step 612 The CHF returns a charging response message to the SMF, optionally, the response message includes ProcInd.
  • step 605 This step is similar to step 605 (except that no quota is granted) and will not be repeated here.
  • An exemplary charging response message is as follows:
  • the CHF may further include processing indication information ProcInd in the response message, which is used to instruct the SMF to set the redundancy flag Uflg for its reported usage.
  • ProcInd may correspond to a certain rate group or some rate groups or all the rate groups of the first data connection service. rate group.
  • Step 613 The SMF acquires the usage amount USU62.
  • the manner in which the SMF acquires the usage amount USU62 is the same as the manner in which the usage amount USU61 is acquired in step 606, and will not be described again.
  • the SMF may also generate a redundancy flag Uflg for the USU 62 to indicate the usage amount of the data connection service that the USU 62 transmits redundantly.
  • Step 614 SMF sends a charging request message to CHF, where the request message includes USU62, redundancy flag Uflg (optional) and transmission delay (optional).
  • the SMF constructs a charging request message and sends it to the CHF, and the update request message includes ResId61, USU61, Uflg (optional) and transmission delay (optional).
  • An exemplary charging request message is as follows:
  • Step 615 The CHF writes the CDR based on the USU62 according to the RCM62/Uflg.
  • the CHF receives and parses the charging request message from the SMF, and obtains the USU62, Uflg (if any) and transmission delay (if any) therefrom. Furthermore, the CHF writes the redundant transmission information, the usage amount, the usage amount description information or the transmission delay into the bill of the PDU session.
  • the CHF determines that the USU 62 is the usage of the redundantly transmitted data connection service, and further determines that a CDR needs to be written to the USU 62 according to the RCM 62. If RCM62 includes redundant charging processing, CHF writes the usage amount (4M) corresponding to USU62 in the bill; Half of the usage corresponding to USU62. If the bill does not exist, CHF creates the bill.
  • the CHF may also write any one or more of RTI61, RCM62 or Uflg and USU62 into the CDR.
  • Step 616 The CHF sends a charging response message to the SMF, where the response message includes indication information that the writing of the CDR is successful.
  • the SMF may continue to report the new usage amount to the CHF through the charging request message until the PDU session is interrupted, and the process ends.
  • the method flow corresponding to FIG. 6A above enables the CHF to sense the existence of redundant transmission in time according to the information reported by the SMF, and according to this, the combined usage reported by the SMF is performed to remove redundancy or to include redundancy. It avoids the problem of inaccurate billing caused by redundant transmission, and can also meet diverse billing needs.
  • 6B is a flowchart of a third method for performing charging processing on redundantly transmitted data connection services according to an embodiment of the present application, which is used for performing charging processing on the first data connection service in a PDU session, and SMF performs redundancy removal
  • Step 651 The SMF generates redundant transmission information RTI62 for the first data connection service.
  • This step is similar to step 601 and will not be repeated.
  • step 660 If the SMF determines that QF2 is an offline charging service, go to step 660 .
  • Step 652 The SMF sends a charging request message to the CHF, where the request message includes the identifier SesId62 of the PDU session, the RTI62, and the quota application RSU62 (optional).
  • the charging request message may further include transmission delay.
  • the billing request message is a billing resource creation request
  • an example of the message is as follows:
  • Step 653 The CHF determines the redundant service charging processing mode RCM63 according to the RTI62 and/or the transmission delay, and generates quota and usage management indication information QUMI.
  • the CHF receives and parses the charging request message, and obtains RTI62, SesId62, RSU62 (if any) and transmission delay (if any) therefrom. Based on the RTI62, the CHF determines that the transmission of the first data connection service is redundant transmission. The CHF further determines the redundant service charging processing method RCM63 for the data connection service according to the charging policy or user subscription information; for example, the RCM63 may be determined to include redundant charging processing, or may be determined to remove redundant charging processing. Billing processing.
  • the CHF generates quota and usage management indication information QUMI (corresponding to the "second processing indication information" above) based on the RCM63, which is used to instruct the SMF to perform some kind of redundant usage processing for the second data connection service: if the RCM63 For charging processing including redundancy, QUMI is used to instruct SMF to perform redundant usage processing on the second data connection service; if RCM63 is charging processing for removing redundancy, QUMI is used to instruct SMF to The second data connection service performs redundant usage processing.
  • QUMI usage management indication information
  • the second data connection service corresponds to the rate group in the first data connection service, or corresponds to the first data connection service.
  • a QoS flow in a data connection service corresponds to or corresponds to a data connection session corresponding to the first data connection service.
  • the redundant transmission mode of the first data connection service is tunnel redundancy, and the second data connection service corresponds to a rate group in the first data connection service, or corresponds to the first data connection service.
  • QoS flow corresponds.
  • QUMI may correspond to all data connection services in the PDU session, or may correspond to one or some QoS flows in the PDU session, and may correspond to a service identifier in the QoS flow in the PDU session.
  • the service data flow can also correspond to the rate group in the PDU session.
  • the QUMI may correspond to some service data flows in the QoS flow QF2, such as several service data flows corresponding to a certain rate group therein.
  • the meaning of "corresponding” here is "scope of action", that is, QUMI is used to instruct SMF to perform a certain way of redundant usage processing for the data connection service of what scope. In this way, the CHF can issue the QUMI for a part of the service data flow in the redundantly transmitted data connection service.
  • Step 654 The CHF grants the quota GSU62 according to the RCM63.
  • the CHF grants a quota GSU62 for the first data connection service based on the RSU62.
  • the quota actually reserved by CHF in the user account is A
  • the GSU 62 is A
  • the RCM 63 is the charging process that removes the redundancy
  • the GSU 62 can be A, can also be 2A.
  • the CHF may grant a quota GSU62 for the first data connection service based on the RSU62.
  • Step 655 The CHF returns a charging response message to the SMF, where the response message includes the GSU62 and the QUMI.
  • the CHF constructs a charging response message and sends it to the SMF, and the response message includes the GSU62 and the QUMI.
  • An exemplary charging response message is as follows:
  • Step 656 The SMF obtains the usage amount USU63 corresponding to the GSU62 according to the QUMI.
  • the SMF receives and parses the above charging response message, obtains GSU62 and QUMI from it, and then consumes the GSU62 for the data connection service according to the QUMI, and records the corresponding usage USU63.
  • SMF can use the traffic consumption in the column "Data Traffic” in Table 3 (where the data connection service is the second data connection service). Quota GSU62, and record the corresponding usage USU63. The SMF can send the GSU62 to the UPF, so that the UPF uses the GSU62 as the limit to release the service data flow of the second data connection service, and obtains the data flow shown in the "Data Flow" column in Table 3 based on the message reported by the UPF.
  • SMF also generates usage description information UD63 for USU63; UD63 indicates that the usage is any of the following:
  • the UD63 may indicate the above four kinds of information, or more specifically, may also include the information in the column "Data Flow" in Table 3.
  • Step 657 The SMF sends a charging request message to the CHF, where the request message includes USU63, UD63 (optional) and transmission delay Delay (optional).
  • the SMF constructs a charging request message and sends it to the CHF, where the update request message includes USU63, UD63 (optional) and transmission delay (optional).
  • An exemplary charging request message is as follows:
  • the UD63 of the USU obtained by performing redundant usage processing can also look like:
  • the UD63 of the USU obtained by processing the usage including redundancy can be as follows:
  • the UD63 may be within the data structure corresponding to the USU63, or may be parallel to the data structure corresponding to the USU63.
  • the charging request message further includes the transmission delay, for details, please refer to the relevant description in step 607 .
  • Step 658 CHF debits the account according to RCM63 and USU63/UD63.
  • the CHF receives and parses the charging resource update request message from the SMF, and obtains the USU63, UD63 (if any) and transmission delay (optional) therefrom. Furthermore, CHF performs account deduction based on USU63 according to the transmission delay described in RCM63/UD63/.
  • CHF determines according to UD63 that the specific traffic (8M) in USU63 is obtained by SMF by executing the QUMI instruction issued by CHF before, and then directly deducts the traffic (8M) corresponding to USU63 in the account corresponding to QoS flow QF2 or corresponding cost.
  • the specific flow (8M) in the default USU63 of CHF is obtained by SMF by performing the processing of the usage including redundancy, and then, if the RCM63 is to remove the redundant charging processing, then CHF deducts half of the traffic (8M) corresponding to the USU63 (ie, 4M) or half of the corresponding fee from the account corresponding to the QoS flow QF2.
  • the CHF may determine the rate used in the account deduction according to the transmission delay, for example, use a higher rate for usage corresponding to a lower delay.
  • Step 659 The CHF sends a charging resource update response message to the SMF, where the response message includes indication information that the account deduction is successful. If there is an granted quota, the same as step 654.
  • the SMF may continue to apply for a quota and/or report a new usage amount to the CHF through the charging resource update request message.
  • Step 660 The SMF sends a charging request message to the CHF, where the request message includes the RTI62 and the identifier SesId62 of the PDU session.
  • This step is similar to step 610 and will not be repeated.
  • Step 661 CHF determines the redundant service charging processing mode RCM64 according to RTI62, and generates usage management indication information UMI
  • step 653 UMI is compared with QUMI, the former is used in offline charging mode, the latter is used in online charging mode, and other steps are similar to step 653.
  • Step 662 The CHF returns a charging response message to the SMF, where the response message includes the charging processing result information and UMI of the CHF.
  • step 654 This step is similar to step 654 (except that no quota is granted) and will not be repeated here.
  • Step 663 The SMF obtains the usage amount USU64 according to the UMI.
  • the SMF receives and parses the above charging response message, obtains the UMI therefrom, and then obtains the usage USU64 according to the UMI.
  • the method by which the SMF obtains the USU64 is the same as that in step 654, and will not be repeated here.
  • the SMF also generates usage description information UD64 for the USU 64 , for details, please refer to the relevant description in step 654 .
  • Step 664 The SMF sends a charging resource update request message to the CHF, where the request message includes ResId62, USU64, UD64 (optional) and transmission delay Delay (optional).
  • the SMF constructs a charging resource update request message and sends it to the CHF, where the update request message includes ResId62, USU64, UD64 (optional) and transmission delay (optional).
  • An exemplary charging resource update request message is as follows:
  • UD64 For more examples of UD64, please refer to the related description in step 657.
  • Step 665 The CHF writes the CDR based on the USU64 according to the RCM64/UD64.
  • the CHF receives and parses the charging resource update request message from the SMF, and obtains the USU64, UD64 (if any) and transmission delay (optional) therefrom. Furthermore, the CHF writes the redundant transmission information, the usage amount, the usage amount description information or the transmission delay into the bill corresponding to the PDU session.
  • the CHF determines according to the UD64 that the specific traffic (8M) in the USU64 is obtained by the SMF by executing the UMI instruction previously issued by the CHF, and then directly writes the traffic (8M) corresponding to the USU64 in the bill. If there is no UD64 in the above-mentioned charging resource update request message, then the specific traffic (8M) in the CHF default USU64 is obtained by SMF by performing the processing of the usage including redundancy, and then, if the RCM64 is the charging processing for removing the redundancy, then The CHF writes half (ie, 4M) of the traffic (8M) corresponding to the USU64 in the bill corresponding to the PDU session. If the bill does not exist, CHF creates the bill.
  • the CHF may also write any one or more of RTI62, RCM64 or UD64 and USU64 into the CDR.
  • Step 666 The CHF sends a charging resource update response message to the SMF, where the response message includes the indication information that the CDR is written successfully.
  • the SMF may continue to report the new usage amount to the CHF through the charging resource update request message until the PDU session is interrupted, and the process ends.
  • the above-mentioned method flow corresponding to FIG. 6B enables CHF not only to sense the existence of redundant transmission in time according to the information reported by SMF, but also to instruct SMF to report the traffic that has undergone redundant usage processing for part of the service data flow in the data connection service. Or, by removing the traffic processed by the redundant usage, unnecessary performance overhead on the SMF can be saved, and the bandwidth consumption between the SMF and the CHF can also be reduced. In addition, since the usage is collected on demand by the SMF that directly interacts with the UPF, the accuracy of billing can also be improved to a certain extent.
  • FIG. 7A is an architecture diagram of a third communication system provided by an embodiment of the present application.
  • the communication system is based on the communication system shown in FIG. 5 and adds gNB 522, UPF 523, and SMF 521, so that a connection between UE and DN can be established.
  • the second PDU session the PDU session between UE 511-gNB 522-UPF 523-DN 514.
  • the PDU session is called PDU session 2
  • the PDU session 515 is called PDU session 1
  • the SMF 501 is called SMF1
  • SMF 521 is called SMF2.
  • FIG. 7B is a flowchart of a fourth method for charging and processing redundantly transmitted data connection services provided by an embodiment of the present application.
  • the method process is implemented based on the architecture shown in FIG. 7A , wherein it is assumed that PDU session 1 and PDU session 2 interact with each other.
  • the CHF performs de-redundancy charging processing on them, and selects one of them for charging processing.
  • the method process mainly includes the following steps:
  • Step 701-1 SMF1 generates redundant transmission information RTI71 for the data connection service in PDU session 1.
  • Step 701-2 SMF2 generates redundant transmission information RTI72 for the data connection service in PDU session 2.
  • step 601 The above two steps are similar to step 601 and will not be repeated.
  • Step 702-1 SMF1 sends a charging request message to CHF, where the request message includes RTI71, identifier SesId71 of PDU session 1, and transmission delay Delay71 (optional).
  • the SMF1 determines to perform charging on the mutually redundant PDU Session 1, and sends a charging request message to the CHF.
  • This step is similar to step 660 and will not be repeated here.
  • An exemplary billing resource creation request message is as follows:
  • the primary PDU session refers to the PDU session corresponding to the primary NG-RAN
  • the secondary PDU session is the PDU session corresponding to the secondary NG-RAN.
  • the CHF receives and parses the charging request message in this step, obtains SedId71 and RTI71 from it, and determines to perform redundant charging processing for PDU session 1 based on information such as RTI71.
  • Step 702-2 The SMF2 sends a charging request message to the CHF, the request message including the RTI72, the identifier SesId72 of the PDU session 2, and the transmission delay Delay72 (optional).
  • SMF2 determines to perform charging on the mutually redundant PDU session 1, it does not send a charging request message to the CHF, which means that for the two mutually redundant PDU sessions, only the PDU session 1 will be charged. Perform charging; or, if SMF2 determines to perform charging on mutually redundant PDU Session 2, it sends a charging request message to CHF.
  • This step is similar to step 660 and will not be repeated here.
  • An exemplary billing resource creation request message is as follows:
  • the CHF receives and parses the charging resource creation request message described in the step, obtains SedId72 and RTI72 therefrom, and determines to perform redundant charging processing for PDU session 2 based on RTI72 and the charging policy.
  • Step 703 The CHF determines to perform the charging process for removing redundancy: charging for PDU session 1 and not charging for PDU session 2.
  • RTI71 or RTI72 contains a "RoleInRT" field (representing the role of the corresponding PDU session in redundant transmission: whether it is a master PDU session or a slave PDU session)
  • the CHF can determine which one to use based on the information represented by this field.
  • the PDU session is charged; usually, the CHF decides to charge the primary PDU session, but not the slave PDU session; therefore, the CHF sends a "no charge” indication NoChgInd to the SMF2 (the CHF can only receive the step
  • the billing resource creation request message of 702-2 sends NoChgInd).
  • the CHF can determine which PDU session to charge based on this field, for example, the CHF can randomly select a PDU session to charge. If the RTI71 or RTI72 also contains the "Delay" field (representing the delay between the UE and the corresponding UPF of the corresponding PDU session), the CHF can compare the delays of the two PDU sessions after both charging resource creation request messages are received. delay, and choose to charge for PDU sessions with a smaller delay.
  • RTI71 or RTI72 also contains the "NSId" field (representing the identifier of the network slice where the corresponding PDU session is located)
  • the CHF can obtain the location of each PDU session based on the "NSId" field after receiving both charging resource creation request messages.
  • the priority information of the network slice for example, query the network slice management device for the priority information), and then select to charge the PDU session with the higher priority of the network slice.
  • the CHF sends the indication information NoChgInd of "no charging" to the SMF corresponding to the PDU session that does not require charging.
  • Step 704-1 The CHF sends a charging resource creation response message to the SMF1.
  • the CHF constructs a charging resource creation response message and sends it to SMF1.
  • Step 704-2 The CHF sends a charging resource creation response message to the SMF2, where the response message includes NoChgInd.
  • CHF constructs a charging resource creation response message and sends it to SMF2, the response message contains NoChgInd.
  • Step 705-1 SMF1 performs charging operation for PDU Session 1.
  • the SMF1 performs charging-related operations for the PDU session 1, such as applying for a quota for the data connection service in the PDU session 1 to the CHF, reporting the usage of the data connection service in the PDU session 1 to the CHF, and the like.
  • Step 705-2 SMF2 stops performing charging operations for PDU Session 2.
  • SMF2 ends or suspends performing charging for PDU Session 2.
  • Step 706-1 SMF1 finds that PDU Session 1 becomes a slave PDU session.
  • the SMF1 determines that the PDU session 1 becomes the slave PDU session.
  • Step 706-2 SMF2 finds that PDU session 2 becomes the primary PDU session.
  • the SMF2 determines that the PDU session 2 becomes the primary PDU session according to the information sent by the UE.
  • Step 707-1 The SMF1 sends a charging resource update request message to the CHF, and the request message includes the indication information ToSecondary of "becoming a slave PDU session".
  • Step 707-2 The SMF2 sends a charging resource update request message to the CHF, and the request message includes the indication information ToMastery of "becoming a master PDU session".
  • Step 708 The CHF determines to charge for PDU Session 2 and does not charge for PDU Session 1.
  • This step is similar to step 703 and will not be repeated.
  • Step 709-1 The CHF sends a charging resource update response message to the SMF1, where the response message includes NoChgInd.
  • Step 709-2 The CHF sends a charging resource update response message to the SMF2.
  • Step 710-1 SMF1 stops performing charging operations for PDU Session 1.
  • This step is similar to step 705-2 and will not be repeated.
  • Step 710-2 SMF2 performs charging operation for PDU Session 2.
  • This step is similar to step 705-1 and will not be repeated.
  • the method flow corresponding to FIG. 7B above enables CHF to select one of the two mutually redundant PDU sessions for charging processing, which can reduce the performance overhead of SMF and also reduce the bandwidth consumption between SMF and CHF.
  • the embodiments of the present application all use "two-way redundancy" as an example to describe the solution, that is, there are two PDU sessions in the S1 mode, two transmission tunnels in the S2 mode, and two transmission layers in the S3 mode path.
  • there may also be a "multi-channel redundancy” solution and those skilled in the art can extend the solution to support "multi-channel redundancy” based on the solution. For example, assuming that the total number of mutually redundant paths is R, in this embodiment of the present application, the redundant usage processing (such as step 609, step 615, step 656, etc.) is removed by "halving" the method.
  • the ratio can be adjusted to (R-1)/R, and the redundant usage processing (such as step 656, step 663, etc.) can be removed by "choose one from two", and it can be changed to "choose one from R", for example, in R One tunnel is selected from the mutually redundant N3 tunnels, or one PDU session is selected from the R mutually redundant PDU sessions, etc., which will not be described again.
  • FIG. 8 is a hardware structural diagram of a charging triggering device and a charging processing device provided by an embodiment of the present application. All charging triggering devices (or SMF devices, CTF devices, for example, 430 in FIG. 4B ) and charging processing devices (or CHF devices, for example, 440 in FIG. 4B ) in the embodiments of the present application may adopt the method shown in FIG. 8 .
  • the shown general computer hardware structure includes a processor 801, a memory 802, a bus 803, an input device 804, an output device 805 and a network interface 806, wherein the input device 804 and the output device 805 are optional.
  • memory 802 may include computer storage media in the form of volatile and/or non-volatile memory, such as read-only memory and/or random access memory.
  • Memory 802 may store operating systems, application programs, other program modules, executable code, and program data.
  • the input device 804 can be used to input information to facilitate the system administrator to operate and manage the charging triggering device and the charging processing device, for example, configure charging policies on the charging processing device, and set default settings on the charging triggering device
  • the input device 804 can be a keyboard or a pointing device, such as a mouse, a trackball, a touchpad, a microphone, a joystick, a game pad, a satellite TV antenna, a scanner or similar devices, all of which can be connected through the bus 803 to processor 801.
  • the output device 805 can be used to output information, which is convenient for the system administrator to operate and manage the charging triggering device and the charging processing device; for example, display the charging policy on the charging processing device, and display the default on the charging triggering device
  • the output device 805 can also be other peripheral output devices, such as speakers and/or printing devices, which can also be connected to the processor 801 through the bus 803 .
  • Both the charging triggering device and the charging processing device may be connected to the network through the network interface 806, for example, to a local area network (Local Area Network, LAN).
  • LAN Local Area Network
  • the computer-executed instructions stored in the charging triggering device and the charging processing device may be stored in a remote storage device, and are not limited to being stored locally.
  • the charging trigger device can execute the method steps corresponding to the charging trigger device (or SMF) in all the above embodiments, For example, steps 430, 601, 606, 613, 651, 656, 663, 701-1, and 705-2, etc.; for the specific execution process, refer to the above embodiments, and details are not repeated here.
  • the charging processing device can execute the method steps corresponding to the charging processing device (or CHF) in all the above embodiments, For example, steps 440 , 603 , 604 , 608 , 615 , 653 , 661 , 665 , 703 and 708 ; for the specific execution process, refer to the above embodiments, and details are not repeated here.
  • FIG. 9 is a schematic diagram of a logical structure of a charging processing device provided by an embodiment of the present application.
  • the charging processing device is connected to a charging triggering device, including:
  • a receiving module 901 configured to receive a first charging request message from the charging triggering device, where the first charging request message includes redundant transmission information, and the redundant transmission information refers to the For the relevant information of redundant transmission used by the first data connection service, for the specific execution process, refer to the description of the steps on the side of the charging processing device (or SMF) in the foregoing embodiment, such as steps 430 , 602 , 607 , 610 , 652 , 657 , and 702 -1 and 702-2, etc.;
  • a sending module 902 configured to perform charging processing based on the redundant transmission information, obtain a charging processing result, and send a first charging response message to the charging triggering device.
  • Step description on the fee processing device (or SMF) side such as steps 440, 603, 604, 653, 654, 661, 703 and 708, etc.
  • FIG. 10 is a schematic diagram of a logical structure of a charging triggering device provided by an embodiment of the present application, where the charging triggering device communicates with a charging processing device, including:
  • the -Sending module 1001 configured to send a first charging request message to the charging processing device, where the first charging request message includes redundant transmission information, and the redundant transmission information refers to the data in the data connection session
  • the relevant information about the redundant transmission used by the first data connection service please refer to the description of the steps on the side of the charging trigger device (or SMF) in the above embodiment, such as steps 430 , 602 , 607 , 610 , 652 , 655 , and 702 -1 and 702-2 etc.
  • a receiving module 1002 configured to receive a first charging response message from the charging processing device, where the first charging response message includes a charging processing result, and the charging processing result is based on the charging processing device
  • the step description on the charging trigger device (or SMF) side in the above-mentioned embodiment for the specific execution process such as steps 450, 605, 609, 612, 655, 659, 662, 704-1 and 704-2 etc.
  • the charging processing device shown in FIG. 9 and the charging triggering device shown in FIG. 10 are presented in the form of functional modules.
  • a “module” as used herein may refer to an application-specific integrated circuit (ASIC), a circuit, a processor and memory executing one or more software or firmware programs, an integrated logic circuit, and/or others that may provide the functions described above device.
  • ASIC application-specific integrated circuit
  • the receiving module 901 , the sending module 1001 , the sending module 902 , and the receiving module 1002 can all be implemented by the processor 801 and the memory 802 in FIG. 8 .
  • the function of the receiving module 901 to receive the charging request message and the function of the sending module 1001 to send the charging request message can be implemented by the processor 801 executing the code stored in the memory 802 .
  • the disclosed system, apparatus and method may be implemented in other manners.
  • the division of the units is only a logical function division, and there may be other division methods in actual implementation, for example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not implement.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may also be electrical, mechanical or other forms of connection.
  • the units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solutions of the embodiments of the present application.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the above-mentioned integrated units may be implemented in the form of hardware, or may be implemented in the form of software functional units.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as an independent product, may be stored in a computer-readable storage medium.
  • the technical solutions of the present application are essentially or part of contributions to the prior art, or all or part of the technical solutions can be embodied in the form of software products, and the computer software products are stored in a storage medium , including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage medium includes: a U disk, a removable hard disk, a read-only memory, a random access memory, a magnetic disk or an optical disk and other media that can store program codes.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Power Engineering (AREA)
  • Quality & Reliability (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Meter Arrangements (AREA)

Abstract

一种计费处理方法，包括：计费触发设备向计费处理设备发送计费请求消息，其中包含冗余传输信息，即数据连接会话中的数据连接业务的冗余传输的相关信息，计费处理设备基于该冗余传输信息进行计费处理，包括决策冗余业务计费处理方式、对计费触发设备上报的使用量进行计费处理或者向计费触发设备设备发送使用量处理指示信息等。该方法有助于提高对冗余传输的数据连接业务的计费结果的准确性。

Description

一种计费处理的方法、系统及相关设备
本申请要求于2020年8月4日提交中国国家知识产权局、申请号为202010774810.8、申请名称为“一种计费处理的方法、系统及相关设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，尤其涉及对数据连接会话中的数据连接业务进行计费处理的方法、系统及相关设备。
背景技术
为支持URLLC(Ultra-reliable and Low Latency Communication，超高可靠性低时延通信)类数据连接业务，3GPP(3rd Generation Partnership Project，第三代合作伙伴计划)标准规范定义了5GS(5th Generation System，第五代移动通信系统)中实现可靠传输的冗余传输技术方案，例如，通过冗余的PDU(protocol data unit，协议数据单元)会话、通过对PDU会话的QoS(quality of service，服务质量)流(QoS Flow，服务质量流)使用冗余数据传输隧道或通过对PDU会话使用传输层冗余路径传输数据。
现有计费处理设备，如3GPP标准规范定义的计费功能(CHarging Function，CHF)设备，并不参与数据连接业务的冗余传输，也无从获知数据连接业务的冗余传输的情况。按照其现有机制进行计费，将无法满足运营商或终端用户的多样化计费需求，例如，可能导致计费结果不准确：或漏了对冗余传输的流量的计费，造成运营商的经济损失，或导致被计费的流量与用户可感知的流量不一致，造成终端用户的误会，降低用户体验。
如何使计费处理设备能基于冗余传输的情况进行计费处理，是亟需解决的技术问题。
发明内容
鉴于此，有必要提供一种计费处理方法，使计费处理设备能基于数据连接业务的冗余传输的情况进行计费处理，解决这种情况下计费结果不准确的问题。
第一方面，本申请实施例提供了一种计费处理的方法，该方法应用于计费触发设备，所述计费触发设备与计费处理设备通信，该方法包括：
所述计费触发设备向所述计费处理设备发送第一计费请求消息，所述第一计费请求消息包含冗余传输信息，所述冗余传输信息是指为数据连接会话中的第一数据连接业务使用的冗余传输的相关信息；
所述计费触发设备从所述计费处理设备接收第一计费响应消息，所述第一计费响应消息包含计费处理结果，所述计费处理结果为所述计费处理设备基于所述冗余传输信息进行计费处理的结果。
该方法使得计费处理设备可以向计费处理设备提供数据连接会话中数据连接业务的冗余传输的有关信息，使得计费处理可以及时感知冗余传输的情况，并基于冗余传输情况进行计费处理，有助于提高冗余传输的数据连接业务的计费结果的准确性，满足运营商或终端用 户的多样化计费需求。
在一个可能的方案中，向所述计费处理设备发送第一计费请求消息之前，所述方法还包括：所述计费触发设备确定所述第一数据连接业务的冗余传输方式。
在一个可能的方案中，所述冗余传输信息指示所述第一数据连接业务的传输为冗余传输。
在一个可能的方案中，所述冗余传输信息还指示所述第一数据连接业务的冗余传输方式，所述冗余传输方式为以下任意一项：会话冗余、隧道冗余或传输层冗余。
在一个可能的方案中，所述第一数据连接业务的冗余传输方式为会话冗余，所述冗余传输信息还指示所述数据连接会话为主数据连接会话或从数据连接会话，或者，所述冗余传输信息还包含与所述数据连接会话互为冗余的数据连接会话的信息。
在一个可能的方案中，所述计费处理结果包含所述计费处理设备为所述第一数据连接业务授予的配额和对应的第一处理指示信息，所述第一处理指示信息指示所述计费触发设备为所述配额对应的使用量设置冗余标记；所述方法还包括：所述计费触发设备向所述计费处理设备发送第二计费请求消息，所述第二计费请求消息包含所述配额对应的使用量和所述冗余标记；所述冗余标记指示所述使用量为冗余传输的数据连接业务的使用量。该方案使得计费处理设备可以更精确地确定哪些使用量需要执行去除冗余的计费处理或者包含冗余的计费处理，可以提高计费性能。
在一个可能的方案中，所述计费处理结果包含第二处理指示信息，所述第二处理指示信息指示为所述数据连接会话中的第二数据连接业务执行：包含冗余的使用量处理或者去除冗余的使用量处理。该方法使得计费触发设备可以根据计费处理设备的需要采集相应的使用量，有助于提高整体计费处理系统的性能。
在一个可能的方案中，所述第一数据连接业务的冗余传输方式为会话冗余或者传输层冗余，所述第二数据连接业务与所述第一数据连接业务中的费率组对应、与所述第一数据连接业务中的QoS流对应或者与所述第一数据连接业务对应的数据连接会话对应；或者，所述第一数据连接业务的冗余传输方式为隧道冗余，所述第二数据连接业务与所述第一数据连接业务中的费率组对应、或者与所述第一数据连接业务对应的QoS流对应。
在一个可能的方案中，所述第一数据连接业务的冗余传输方式为会话冗余、隧道冗余或传输层冗余，所述为所述第二数据连接业务执行去除冗余的使用量处理，包括：将所述数据连接会话中所述第二数据连接业务的冗余传输的流量的一半作为所述第二数据连接业务的使用量；所述为所述第二数据连接业务执行包含冗余的使用量处理，包括：将所述数据连接会话中所述第二数据连接业务的冗余传输的流量作为所述第二数据连接业务的使用量；或者，所述第一数据连接业务的冗余传输方式为隧道冗余或者传输层冗余，所述为所述第二数据连接业务执行去除冗余的使用量处理，包括：将在用户面数据网关与数据网络之间传输的所述第二数据连接业务的流量作为所述第二数据连接业务的使用量，所述为所述第二数据连接业务执行包含冗余的使用量处理，包括：将在用户面数据网关与无线接入网络设备之间传输的所述第二数据连接业务的流量作为所述第二数据连接业务的使用量；或者，所述第一数据连接业务的冗余传输方式为隧道冗余或传输层冗余，所述为所述第二数据连接业务执行去除冗余的使用量处理，包括：将通过互为冗余的两条传输通路之一传输的所述第二数据连接业务的流量作为所述第二数据连接业务的使用量，所述为所述第二数据连接业务执行包含冗余的使用量处理，包括：将通过互为冗余的两条传输通路传输的所述第二数据连接业务的流 量作为所述第二数据连接业务的使用量。
在一个可能的方案中，所述第二数据连接业务为在线计费业务，所述为所述第二数据连接业务执行包含冗余的使用量处理或去除冗余的使用量处理，还包括：用所述第二数据连接业务的使用量消费所述计费处理设备授予的配额。
在一个可能的方案中，所述计费触发设备向所述计费处理设备发送所述第一数据连接业务中的费率组或QoS流对应的使用量及相应的使用量描述信息，所述使用量描述信息指示所述使用量为以下任意一项：未执行去除冗余的使用量处理的流量、执行去除冗余的使用量处理后的流量、用户面数据网关与无线接入网络设备之间传输的流量、用户面数据网关与数据网络之间传输的流量。
在一个可能的方案中，所述计费触发设备向所述计费处理设备发送所述第一数据连接业务的传输时延。
在一个可能的方案中，所述计费处理结果包含不计费指示信息，所述不计费指示信息指示所述计费处理设备确定所述数据连接会话为从数据连接会话而不对其执行计费处理，或者确定对与所述数据连接会话互为冗余的数据连接会话执行计费而不对所述数据连接会话执行计费处理。
在一个可能的方案中，所述计费触发设备确定所述数据连接会话变为主数据连接会话；所述计费触发设备向所述计费处理设备发送第三计费请求消息，所述第三计费请求消息包含所述数据连接会话变为主数据连接会话的指示信息。
第二方面，本申请实施例提供了一种计费处理的方法，该方法应用于计费处理设备，所述计费处理设备与计费触发设备通信，该方法包括：
所述计费处理设备从所述计费触发设备接收第一计费请求消息，所述第一计费请求消息包含冗余传输信息，所述冗余传输信息是指为数据连接会话中的第一数据连接业务使用的冗余传输的相关信息；
所述计费处理设备基于所述冗余传输信息进行计费处理，得到计费处理结果，且向所述计费触发设备发送第一计费响应消息，所述第一计费响应消息包含所述计费处理结果。
该方法使得计费处理设备可以获取数据连接业务的冗余传输的有关信息，基于冗余传输的情况进行计费处理，有助于提高对冗余传输的数据连接业务的计费结果的准确性。
在一个可能的方案中，所述冗余传输信息指示所述第一数据连接业务的传输为冗余传输。
在一个可能的方案中，所述冗余传输信息还指示所述第一数据连接业务的冗余传输方式，所述冗余传输方式为以下任意一项：会话冗余、隧道冗余或传输层冗余。
在一个可能的方案中，所述第一数据连接业务的冗余传输方式为会话冗余，所述冗余传输信息还指示所述数据连接会话为主数据连接会话或从数据连接会话，或者，所述冗余传输信息还包含与所述数据连接会话互为冗余的数据连接会话的信息。
在一个可能的方案中，所述计费处理设备基于所述冗余传输信息进行计费处理，包括：基于所述冗余传输信息确定对所述第一数据连接业务的使用量执行去除冗余的计费处理或者包含冗余的计费处理，并为所述第一数据连接业务授予配额；所述计费处理结果包含所述配额；所述方法还包括：所述计费处理设备从所述计费触发设备接收第二计费请求消息，所述第二计费请求消息包含所述配额对应的使用量；所述计费处理设备对所述配额的使用量执行去除冗余的计费处理或者包含冗余的计费处理。
在一个可能的方案中，所述方法还包括：所述计费处理设备为所述配额生成第一处理指示信息，所述第一处理指示信息指示所述计费触发设备为所述配额对应的使用量设置冗余标记；所述计费处理结果还包含所述第一处理指示信息；所述第二计费请求消息还包含所述冗余标记；所述计费处理设备对所述配额的使用量执行去除冗余的计费处理或者包含冗余的计费处理，包括：所述计费处理设备基于所述冗余标记对所述配额的使用量执行去除冗余的计费处理或者包含冗余的计费处理；所述冗余标记指示所述使用量为冗余传输的数据连接业务的使用量。
在一个可能的方案中，所述计费处理设备基于所述冗余传输信息进行计费处理，包括：所述计费处理设备基于所述冗余传输信息生成第二处理指示信息；所述计费处理结果包含所述第二处理指示信息；其中，所述第二处理指示信息指示所述计费触发设备为所述数据连接会话中的第二数据连接业务执行：包含冗余的使用量处理或者去除冗余的使用量处理。
在一个可能的方案中，所述冗余传输信息指示所述第一数据连接业务的冗余传输方式为会话冗余或者传输层冗余，所述第二数据连接业务与所述第一数据连接业务中的费率组对应、与所述第一数据连接业务中的QoS流对应或与所述第一数据连接业务对应的数据连接会话对应；或者，所述冗余传输信息指示所述第一数据连接业务的冗余传输方式为隧道冗余，所述第二数据连接业务与所述第一数据连接业务中的费率组对应、或者与所述第一数据连接业务对应的QoS流对应。
在一个可能的方案中，所述方法还包括：所述计费处理设备从所述计费触发设备接收所述第一数据连接业务中的费率组或QoS流对应的使用量及相应的使用量描述信息，所述使用量描述信息指示所述使用量为如下任意一项：未执行去除冗余的使用量处理的流量，执行去除冗余的使用量处理后的流量，用户面数据网关与无线接入网络设备之间传输的流量，用户面数据网关与数据网络之间传输的流量。
在一个可能的方案中，所述方法还包括：所述计费处理设备从所述计费触发设备接收所述第一数据连接业务的传输时延；所述计费处理设备基于所述冗余传输信息进行计费处理，包括：所述计费处理设备根据所述冗余传输信息和所述传输时延进行计费处理。
在一个可能的方案中，所述方法还包括：所述计费处理设备将所述第一数据连接业务的信息写入话单，所述第一数据连接业务的信息包括以下任意一项：冗余传输信息、使用量描述信息或传输时延。
在一个可能的方案中，所述计费处理设备基于所述冗余传输信息进行计费处理，包括：所述计费处理设备确定不对所述连接会话执行计费处理；所述计费处理设备生成不计费指示信息，所述不计费指示信息指示所述计费处理设备确定所述数据连接会话为从数据连接会话而不对其执行计费处理，或者确定与所述数据连接会话互为冗余的数据连接会话执行计费而不对其执行计费处理；所述计费处理结果包含所述不计费指示信息。
第三方面，本申请实施例提供了一种计费处理系统，包括：计费触发设备和计费处理设备，所述计费触发设备与所述计费处理设备通信，其中：
所述计费触发设备用于：向所述计费处理设备发送第一计费请求消息，所述第一计费请求消息包含冗余传输信息，所述冗余传输信息是指为数据连接会话中的第一数据连接业务使用的冗余传输的相关信息；
所述计费处理设备用于：基于所述冗余传输信息进行计费处理，得到计费处理结果，且向所述计费触发设备发送第一计费响应消息，所述第一计费响应消息包含所述计费处理结 果。
在一个可能的方案中，所述冗余传输信息指示所述第一数据连接业务的传输为冗余传输。
在一个可能的方案中，所述冗余传输信息还指示所述第一数据连接业务的冗余传输方式，所述冗余传输方式为以下任意一项：会话冗余、隧道冗余或传输层冗余。
在一个可能的方案中，所述第一数据连接业务的冗余传输方式为会话冗余，所述冗余传输信息还指示所述数据连接会话为主数据连接会话或从数据连接会话，或者，所述冗余传输信息还包含与所述数据连接会话互为冗余的数据连接会话的信息。
在一个可能的方案中，所述计费处理设备还用于：基于所述冗余传输信息确定对所述第一数据连接业务的使用量执行去除冗余的计费处理并为所述第一数据连接业务授予配额；使所述计费处理结果包含所述配额；所述计费触发设备还用于：向所述计费处理设备发送第二计费请求消息，所述第二计费请求消息包含所述配额对应的使用量；所述计费处理设备还用于：对所述配额的使用量执行去除冗余的计费处理或者包含冗余的计费处理。
在一个可能的方案中，所述计费处理设备还用于：为所述配额生成第一处理指示信息，所述第一处理指示信息指示所述计费触发设备为所述配额对应的使用量设置冗余标记；使所述计费处理结果还包含所述第一处理指示信息；所述计费触发设备还用于：在所述第二计费请求消息中包含所述冗余标记；其中，所述冗余标记指示所述使用量为冗余传输的数据连接业务的使用量。
在一个可能的方案中，所述计费处理设备还用于：基于所述冗余传输信息生成第二处理指示信息；使所述计费处理结果包含所述第二处理指示信息；所述计费触发设备还用于：根据所述第二处理指示信息，为所述数据连接会话中的第二数据连接业务执行：包含冗余的使用量处理或者去除冗余的使用量处理。
在一个可能的方案中，所述冗余传输信息还指示所述数据连接会话为从数据连接会话或者所述冗余传输信息包含与所述数据连接会话互为冗余的数据连接会话的信息；所述计费处理设备还用于：确定不对所述数据连接会话执行计费处理，生成不计费指示信息，且使所述计费处理结果包含所述不计费指示信息，所述不计费指示信息指示所述计费处理设备确定所述数据连接会话为从数据连接会话而不对其执行计费处理，或者确定对与所述数据连接会话互为冗余的数据连接会话执行计费而不对所述数据连接会话执行计费处理。
第四方面，本申请实施例提供了一种计费触发设备，所述计费触发设备与计费处理设备通信，包括发送模块和接收模块，其中：
所述发送模块用于：向所述计费处理设备发送第一计费请求消息，所述第一计费请求消息包含冗余传输信息，所述冗余传输信息是指为数据连接会话中的第一数据连接业务使用的冗余传输的相关信息；
所述接收模块用于：从所述计费处理设备接收第一计费响应消息，所述第一计费响应消息包含计费处理结果，所述计费处理结果为所述计费处理设备基于所述冗余传输信息进行计费处理的结果。
在一个可能的方案中，所述冗余传输信息指示所述第一数据连接业务的传输为冗余传输。
在一个可能的方案中，所述冗余传输信息还指示所述第一数据连接业务的冗余传输方式，所述冗余传输方式为以下任意一项：会话冗余、隧道冗余或传输层冗余。
在一个可能的方案中，所述第一数据连接业务的冗余传输方式为会话冗余，所述冗余传输信息还指示所述数据连接会话为主数据连接会话或从数据连接会话，或者，所述冗余传输信息还包含与所述数据连接会话互为冗余的数据连接会话的信息。
在一个可能的方案中，所述计费处理结果包含所述计费处理设备为所述第一数据连接业务授予的配额和对应的第一处理指示信息，所述第一处理指示信息指示所述计费触发设备为所述配额对应的使用量设置冗余标记；所述发送模块还用于：向所述计费处理设备发送第二计费请求消息，所述第二计费请求消息包含所述配额对应的使用量和所述冗余标记；所述冗余标记指示所述使用量为冗余传输的数据连接业务的使用量。
在一个可能的方案中，所述计费处理结果包含第二处理指示信息，所述第二处理指示信息指示为所述数据连接会话中的第二数据连接业务执行：包含冗余的使用量处理或者去除冗余的使用量处理。
在一个可能的方案中，所述发送模块还用于向所述计费处理设备发送所述第一数据连接业务中的费率组或QoS流对应的使用量及相应的使用量描述信息，所述使用量描述信息指示所述使用量为以下任意一项：未执行去除冗余的使用量处理的流量，执行去除冗余的使用量处理后的流量，用户面数据网关与无线接入网络设备之间传输的流量，用户面数据网关与数据网络之间传输的流量。
在一个可能的方案中，所述发送模块还用于向所述计费处理设备发送所述第一数据连接业务的传输时延。
在一个可能的方案中，所述计费处理结果包含不计费指示信息，所述不计费指示信息指示所述计费处理设备确定所述数据连接会话为从数据连接会话而不对其执行计费处理，或者确定对与所述数据连接会话互为冗余的数据连接会话执行计费而不对所述数据连接会话执行计费处理。
第五方面，本申请实施例提供了一种计费处理设备，所述计费处理设备与计费触发设备通信，包括接收模块和发送模块，其中：
所述接收模块用于：从所述计费触发设备接收第一计费请求消息，所述第一计费请求消息包含冗余传输信息，所述冗余传输信息是指为数据连接会话中的第一数据连接业务使用的冗余传输的相关信息；
所述发送模块用于：基于所述冗余传输信息进行计费处理，得到计费处理结果，且向所述计费触发设备发送第一计费响应消息，所述第一计费响应消息包含所述计费处理结果。
在一个可能的方案中，所述冗余传输信息指示所述第一数据连接业务的传输为冗余传输。
在一个可能的方案中，所述冗余传输信息还指示所述第一数据连接业务的冗余传输方式，所述冗余传输方式为以下任意一项：会话冗余、隧道冗余或传输层冗余。
在一个可能的方案中，所述第一数据连接业务的冗余传输方式为会话冗余，所述冗余传输信息还指示所述数据连接会话为主数据连接会话或从数据连接会话，或者，所述冗余传输信息还包含与所述数据连接会话互为冗余的数据连接会话的信息。
在一个可能的方案中，所述发送模块还用于：基于所述冗余传输信息确定对所述第一数据连接业务的使用量执行去除冗余的计费处理或者包含冗余的计费处理，并为所述第一数据连接业务授予配额；所述计费处理结果包含所述配额；所述接收模块还用于：从所述计费触发设备接收第二计费请求消息，所述第二计费请求消息包含所述配额对应的使用量；所述计 费处理设备对所述配额的使用量执行去除冗余的计费处理或者包含冗余的计费处理。
在一个可能的方案中，所述发送模块还用于：基于所述冗余传输信息生成第二处理指示信息；所述计费处理结果包含所述第二处理指示信息；其中，所述第二处理指示信息指示所述计费触发设备为所述数据连接会话中的第二数据连接业务执行：包含冗余的使用量处理或者去除冗余的使用量处理。
在一个可能的方案中，所述接收模块还用于：从所述计费触发设备接收所述第一数据连接业务中的费率组或QoS流对应的使用量及相应的使用量描述信息，所述使用量描述信息指示所述使用量为如下任意一项：未执行去除冗余的使用量处理的流量、执行去除冗余的使用量处理后的流量、用户面数据网关与无线接入网络设备之间传输的流量、用户面数据网关与数据网络之间传输的流量。
在一个可能的方案中，所述接收模块还用于：从所述计费触发设备接收所述第一数据连接业务的传输时延；所述发送模块还用于：根据所述冗余传输信息和所述传输时延进行计费处理。
在一个可能的方案中，所述发送模块还用于：将所述第一数据连接业务的信息写入话单，所述第一数据连接业务的信息包括以下任意一项：冗余传输信息、使用量描述信息或传输时延。
在一个可能的方案中，所述发送模块还用于：确定不对所述连接会话执行计费处理；生成不计费指示信息，所述不计费指示信息指示所述计费处理设备确定所述数据连接会话为从数据连接会话而不对其执行计费处理，或者确定与所述数据连接会话互为冗余的数据连接会话执行计费而不对其执行计费处理；所述计费处理结果包含所述不计费指示信息。
第六方面，本申请实施例提供了一种计费触发设备，包括处理器和存储器，其中：所述存储器，用于存储程序指令；所述处理器，用于调用并执行所述存储器中存储的程序指令，以使所述计费触发设备执行上述第一方面或者上述第一方面下任意可能方案对应的计费处理的方法。
第七方面，本申请实施例提供了一种计费处理设备，包括处理器和存储器，其中：所述存储器，用于存储程序指令；所述处理器，用于调用并执行所述存储器中存储的程序指令，以使所述计费处理设备执行上述第二方面或者上述第二方面下任意可能方案对应的计费处理的方法。
第八方面，本申请实施例提供了一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得所述计算机执行上述第一方面、上述第二方面、上述第一方面下任意可能方案或者上述第二方面下任意可能方案对应的计费处理的方法。
附图说明
图1为本申请实施例提供的会话冗余传输方式示意图；
图2A为本申请实施例提供的隧道冗余传输方式第一示意图；
图2B为本申请实施例提供的隧道冗余传输方式第二示意图；
图3为本申请实施例提供的传输层冗余传输方式示意图；
图4A为本申请实施例提供的第一通信系统架构图；
图4B为本申请实施例提供的对冗余传输的数据连接业务进行计费处理的第一方法流程图；
图5为本申请实施例提供的第二通信系统架构图；
图6A为本申请实施例提供的对冗余传输的数据连接业务进行计费处理的第二方法流程图；
图6B为本申请实施例提供的对冗余传输的数据连接业务进行计费处理的第三方法流程图；
图7A为本申请实施例提供的第三通信系统架构图；
图7B为本申请实施例提供的对冗余传输的数据连接业务进行计费处理的第四方法流程图；
图8为本申请实施例提供的计费触发设备、计费处理设备的硬件结构图；
图9为本申请实施例提供的计费处理设备的逻辑结构示意图；
图10为本申请实施例提供的计费触发设备的逻辑结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述。其中，在本申请的描述中，除非另有说明，“/”表示前后关联的对象是一种“或”的关系，例如，A/B可以表示A或B；本申请中的“和/或”是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A、同时存在A和B、单独存在B这三种情况，其中A,B可以是单数或者复数。并且，在本申请的描述中，除非另有说明，“多个”是指两个或多于两个。另外，为了便于清楚描述本申请实施例的技术方案，在本申请的实施例中，采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。
针对一个数据连接会话或者该数据连接会话中的数据连接业务，运营商通信网络至少可以采用如下三种方式的冗余传输来提高其可靠性。
会话冗余(记为“S1”)：即数据连接会话的冗余，是指在用户设备与数据网络之间存在两条互为冗余的数据连接会话，用户的同一业务的业务数据流同时在所述两个互为冗余的数据连接会话中传输。例如，如图1所示，UE(user equipment，用户设备)101建立了两个PDU(protocol data unit，协议数据单元)会话，基于这两个PDU会话，建立了两条互相独立的用户面(user plane)路径，用于在UE 101与DN(Data Network，数据网络)109之间传输相同的数据。为叙述方便，本申请实施例将该冗余传输方式简称为“会话冗余”。
隧道冗余(记为“S2”)：是指在无线接入网络设备与用户面数据网关之间存在两条传输相同数据的用户面传输隧道，对应所述数据连接会话内同一个QoS流(即所述QoS流中的业务数据流经过所述两条用户面传输隧道进行冗余地传输)，构成两条互为冗余的传输隧道(N3/N9)级别的传输通路。例如，如图2A或图2B所示，在QoS流的建立过程中，SMF(Session Management Function，会话管理功能)设备204通知PSA(PDU session anchor，PDU会话锚点)UPF(User Plane Function，用户面功能)设备205和NG-RAN(Next-Generation Radio Access Network,下一代无线接入网络)设备203执行QoS流粒度的冗余传输，具体地，可以是通过在PSA UPF设备205与NG-RAN设备203之间的两条N3接口隧道(N3 Tunnel)传输相同的数据，这两条N3接口隧道共用相同的QoS流的标识，如图2A所示；也可以是通过在PSA UPF设备205与NG-RAN设备203之间的两条N3和N9接口隧道(N3 and N9 Tunnel) 传输相同的数据，这两条N3和N9隧道也共用相同的QoS流的标识，如图2B所示。为叙述方便，本申请实施例将该冗余传输方式简称为“隧道冗余”，其与QoS流标识对应。
传输层冗余(记为“S3”)：是指在无线接入网络设备与用户面数据网关之间存在两条共同对应所述数据连接会话的传输层路径传输相同的数据(即所述数据连接会话中的所有业务数据流都分别经过所述两条传输层路径进行冗余地传输)，构成两条互为冗余的数据连接会话级别的传输通路。例如，如图3所示，在N3 GTP-U(GPRS Tunneling Protocol-User Plane，GPRS隧道协议用户面部分)隧道建立时，UPF设备305和NG-RAN设备303之间建立两条相互独立的传输层路径(path at transport layer)；UPF设备305发送下行数据到N3 GTP-U隧道过程中，复制下行数据到两条传输层路径，NG-RAN设备303接收到下行数据后排除重复的下行数据再转发给UE 301；NG-RAN设备303发送上行数据到N3 GTP-U隧道过程中，也复制上行数据到两条传输层路径，UPF设备305接收到上行数据后排除重复的上行数据再转发到DN 307。为叙述方便，本申请将该冗余传输方式简称为“传输层冗余方式”。
其中，S1方式的冗余传输时，对于冗余的两个数据连接会话中的任一数据连接会话，在任一采集周期内，UE到用户面数据网关之间的流量与用户面数据网关到数据网络之间的数流量是一致的(不考虑因为策略控制或者网络原因造成丢包的情况)；而S2或S3方式的冗余传输仅发生在无线接入网络设备与用户面数据网关之间，同一冗余传输的数据连接业务在用户面数据网关两侧的流量是不一致的，即：不考虑网络异常，如丢包等，在任一采集周期内，无线接入网络设备侧的流量是数据网络侧的流量的两倍。
上述可靠性的提升是运营商额外投入的网络资源换来的。例如，图1中NG-RAN 104和UPF 107所支撑的第二路PDU会话，图2A中NG-RAN 203与UPF 205之间的N3隧道2，图2B的NG-RAN 203与UPF 205之间的N3隧道2和N9隧道2，以及图3中NG-RAN 303和UPF 305之间的第二条传输层路径等。因此，计费处理设备应该提供新的计费能力，例如，对因冗余传输而引起的额外流量进行计费处理，使得运营商可以针对其额外投入的网络资源收费。不仅如此，由于用户设备可感知的使用量与用户面数据网关可采集的使用量上有差异，计费处理设备还需要区分出哪些是不进行冗余传输本来就有的使用量、哪些是因冗余传输而额外增加的使用量，然后再进行计费处理，否则可能造成终端用户不必要的误会，形成不良的用户体验。
这就需要计费处理设备能在数据传输过程中及时获取数据连接会话的冗余传输情况，及时管理使用量的获取方式，及时对获取到的使用量进行相应的计费处理，以满足运营商或终端用户多样化的计费需求。
图4A为本申请实施例提供的第一通信系统架构图，其中包括用户设备411、无线网络接入设备412、用户面数据网关413、数据网络414、计费处理设备402和计费触发设备401；其中，计费触发设备401和计费处理设备402组成计费处理系统，这其中包括对数据连接会话415进行计费处理。在可能的方案中，所述计费处理系统还包含策略控制设备(图4A未显示)、账单管理设备(图4A未显示)等。下面就其中部分设备作简要介绍。
用户设备411：为终端用户的设备，通过空中接口与无线网络设备412相连(注：本申请实施例所述的“相连”或者“连接”包括直接连接或者间接连接，后者指通过一个或多个中间网络设备连接，将不再赘述)；负责发起数据连接会话415的创建或拆除；经数据连接会话415与数据网络414中的设备或者服务器进行通信，以向终端用户提供多样化的业务，如语音通话、视频播放等；
用户设备411可以是3GPP标准规范定义的UE(user equipment，用户设备)；示例性的用户设备包括：智能手机、带有无线通信功能的膝上电脑(Laptop)、平板电脑、可穿戴设备、AR(Augmented Reality，增强现实)设备、IoT(Internet of Things，万物互联)设备等。
应理解，实际应用中，图4A所示通信系统可以有更多的用户设备。
无线接入网络设备412：为无线接入网络中的网元，负责向用户设备411发送射频信号或者从用户设备411接收射频信号，以将用户面数据网关413的数据包发送到用户设备411或者将用户设备411发送的数据包发送到用户面数据网关413；通常为3GPP标准规范定义的NG-RAN，包括但不限于eNB(evolved NodeB，演进型基站)、gNB(gNodeB，5G基站)；应理解，实际应用中，图4A所示的通信系统中可以有更多的无线接入网络设备。
用户面数据网关413：为核心网中的网元，将来自用户设备411、经由无线接入网络设备412的数据包传送到数据网络414，或者将数据网络414发送的数据包传送到无线接入网络设备412、进而传送到用户设备411,通常为3GPP标准规范定义的UPF设备、PGW-U(packet data network gateway for user plane，用户面分组数据网关)或SGW-U(serving gateway for user plane，用户面服务网关)；应理解，实际应用中，图4A所示的通信系统中可以有更多的用户面数据网关。
数据网络414：用于传输数据、以数据交换机为转接点而组成的网络，如英特网，其中包含应用服务器(图4A中未显示)，为用户设备411上的各种APP(Application，应用程序)提供服务或能力。
数据连接会话415：为用户设备411与数据网络414之间的联结(英文：association between the UE and a data network that provides a connectivity service)，用于为用户设备411与数据网络414之间的通信提供连接服务，以在用户设备、无线接入网络设备、用户面数据网关和数据网络之间传输数据包(paket)；其创建过程可以由用户设备411发起，其拆除过程可以由用户设备411发起，也可以由其他网络设备发起。
数据连接会话415可以是5G网络架构下的PDU会话，还可以是4G(4th generation，第四代)网络架构下的IP-CAN(IP-connectivity access network，IP连通性接入网)会话，还可以是用户设备与数据网络之间其他形式的会话，对此本申请实施例不做限定。
本申请实施例有时候也将数据连接会话简称为“会话”。
计费触发设备401：对数据连接会话415中数据执行计费信息采集、向计费处理设备上报计费信息的设备，分别与用户面数据网关413和计费处理设备402相连，主要功能包括：
(1)获取数据连接会话415或者其中的数据连接业务的冗余传输的有关信息，据此形成冗余传输信息；
(2)向计费处理设备402发送所述冗余传输信息及计费数据；
(3)从计费处理设备402接收计费处理结果，进而基于该结果执行进一步的计费相关操作或者停止计费相关操作。
此外，S2或S3方式下，针对用户面数据网关413两侧流量不对称的特点，计费触发设备401还可以将数据连接会话415中的数据连接业务在用户面数据网关413不同侧传输的流量及描述信息(如描述哪一侧的流量)上报给计费处理设备402。
计费触发设备401包含3GPP标准规范定义的CTF(Charging Trigger Function，计费触发功能)。计费触发设备401可以部署在3GPP标准规范定义的SMF设备(即控制面网关) 中，也可以部署在具有与SMF设备相同或类似功能的其他设备中，如PGW-C(packet data network gateway for control plane，控制面分组用户面数据网关)、SGW-C(serving gateway for control plane，控制面服务网关)，还可以部署在其他可以获取到数据连接会话中的使用量、冗余传输方式等信息的其他设备中；本申请实施例对计费触发设备401的物理部署方式不做限定。
应理解，实际应用中，图4A所示的通信系统可以有更多的计费触发设备。例如，在图1所示冗余传输方式示意图中，就可以有两个计费触发设备，分别部署于SMF 105和SMF 108中。
为叙述方便，本申请实施例中有时候也将计费触发设备简称为“CTF设备”或“CTF”；在CTF设备部署在SMF设备的场景下，也直接用“SMF设备”或“SMF”指代“CTF设备”，后续实施例将不赘述。
计费处理设备402：基于计费触发设备(包括计费触发设备401及图4A未显示的其他计费触发设备)发送的信息，对数据连接会话415中的数据连接业务进行计费处理的设备，主要功能包括：
(1)从所述计费触发设备接收冗余传输信息，以获知数据连接会话415或其中的数据连接业务的冗余传输的有关信息；
(2)基于所述冗余传输信息执行计费处理操作，该操作包括以下任意一项：
(2.1)基于所述冗余传输信息，确定对数据连接会话415或其中的数据连接业务的冗余业务计费处理方式，且从所述计费触发设备接收计费数据，为所述数据连接会话中的数据连接业务执行诸如配额授予、账户扣减、话单写入等操作，且向所述计费触发设备发送这些操作的结果，以使所述计费触发设备基于该结果进一步执行配额申请、使用量上报等计费相关的操作；可选地，还可以结合其他信息，如用户签约信息(用户签约信息可能指定是否针对额外流量进行计费或额外流量的费率等)，确定所述冗余业务计费处理方式；
(2.2)基于所述冗余传输信息，确定对数据连接会话415或其中的数据连接业务的冗余业务计费处理方式，进而确定满足该冗余业务计费处理方式要求的使用量管理方式，且向计费触发设备发送指示信息，以使计费触发设备按照指定的使用量管理方式进行配额管理、使用量采集和上报；可选地，还可以结合其他信息，如用户签约信息、计费处理设备的本地存储的策略等，确定所述使用量管理方式；
(2.3)基于所述冗余传输信息，确定所述数据连接会话无需计费，进而向所述计费触发设备发送不计费指示信息，以使其停止/暂停对所述数据连接会话的计费操作；可选地，还可以结合其他信息，如用户签约信息、如用户签约信息、计费处理设备的本地存储的策略等，确定所述数据连接会话无需计费。
此外，S2或S3方式下，如果计费触发设备401上报了数据连接会话415中的数据连接业务在用户面数据网关413不同侧传输的流量及描述信息，则计费处理设备还可以据此确定相应的数据连接业务是冗余传输的，进而根据计费策略进行计费处理。
计费处理设备402可以基于当前3GPP标准规范定义的CHF(Charging Function，计费功能)设备实现，也可以基于当前3GPP标准规范定义的CCS(Converged Charging System，融合计费系统)设备(其中包含了CHF设备的功能)实现，还可以基于其他具有与CHF设备或CCS设备等同或类似功能的设备实现；此外，计费处理设备402可以单独部署在一个物理设备中，也可以与其他功能设备共同部署在同一个物理设备中；本申请实施例对计费处理设 备402的物理部署方式不做限定。
应理解，实际应用中，图4A所示的通信系统中可以有更多的计费处理设备。
为叙述方便，本申请实施例中，有时候也将计费处理设备简称为“CHF设备”或“CHF”。
为便于理解本申请实施例，下面对一些概念进行解释。
流量：指在特定时间范围(如采集周期)内用户面数据网关(如UPF设备)传输的比特数量。
使用量：指上报给计费处理设备(如CHF设备)用于计费处理的流量；本申请实施例中，使用使用量信息包括使用量和使用量描述信息。
QoS流：是PDU会话中QoS差异化的最小粒度的转发处理，通常用QFI(QoS Flow identifier，QoS流标识)标识一个QoS流。
冗余传输的流量：指在互为冗余的两条传输通路中任一传输通路传输的流量。
数据连接业务：为数据连接会话中的业务数据流的集合，可以有以下任一种粒度：
(1)数据连接会话粒度(即所述数据连接业务中的业务数据流为所述数据连接会话中的业务数据流)；
(2)QoS流粒度(即所述数据连接业务中的业务数据流为所述数据连接会话中某个QoS流中的业务数据流)；
(3)费率组粒度(即所述数据连接业务中的业务数据流为所述数据连接会话中某个费率组中的业务数据流)；
(4)费率组中的业务粒度(即所述数据连接业务中的业务数据流为所述数据连接会话中某个费率组中的某一个业务标识对应的业务数据流)。
为叙述方便，本申请实施例中，有时候也将数据连接业务简称为“业务”或“数据业务”。应理解，本申请实施例中组成数据连接业务的业务数据流，均指需要计费处理的业务数据流，不包括免费或不需要计费处理的业务数据流。
冗余传输的数据连接业务：也称为冗余的数据连接业务，是指通信网络为其实施或使用冗余传输的数据连接业务，不仅包括被实施S2或S3方式冗余传输的数据连接业务，还包括被实施S1方式冗余传输的数据连接业务(即，该数据连接业务中的数据还在另一个数据连接会话中冗余地传输)。
冗余传输方式(Redundant Transmission Mode，RTM)：为冗余传输的网络实现方式的简称，至少包括上文所述的会话冗余(S1)、隧道冗余(S2)或传输层冗余(S3)；“数据连接会话的冗余传输方式”或“数据连接业务的冗余传输方式”则是指通信网络为该数据连接会话或数据连接业务实施或使用的冗余传输的网络实现方式。应理解，冗余传输方式，有时候也可以称为“冗余传输类型”。
冗余传输信息(Redundant Transmission Information，RTI)：指冗余传输的相关信息；某个数据连接会话或该数据连接会话中的数据连接业务的冗余传输信息，可以仅指示(indicate)通信网络是否为该数据连接会话或该数据连接会话中的数据连接业务实施或使用冗余传输，或者该数据连接会话或该数据连接会话中的数据连接业务的传输是否为冗余传输，也可以仅指示或进一步指示该数据连接会话或该数据连接会话中的数据连接业务的冗余传输方式；可选地，在指示冗余传输方式为会话冗余的情况下，还可以进一步指示该数据连接会话在两个互为冗余的数据连接会话中的“地位”(或指示该数据连接会话在冗余传输中的角色，如主数据连接会话、从数据连接会话)，或者进一步指示与该数据连接会话互为冗 余的另一个数据连接会话的有关信息，如所述另一个数据连接会话的标识、所述另一个数据连接会话的用户面数据网关的地址或标识等。
可选地，冗余传输信息也指从中可以推导出存在冗余传输情况的使用量信息；例如，如果使用量信息包含了使用量和使用量采集位置(即在用户面数据网关的哪一侧采集的)，则也可以视为一种冗余传输信息；例如，如果用户面数据网关在无线接入网络的使用量是在数据网络侧使用量的两倍，则计费处理设备可以确定出使用量对应的数据连接业务是采用S2或S3方式的冗余传输。
冗余使用量：是指在特定采集周期内，数据连接业务因冗余传输而额外传输的数据流量。
基础使用量：是指在特定采集周期内，数据连接业务在假设没有冗余传输的情况下的数据流量。
在实际处理中，冗余使用量和基础使用量的出处是相对的；在S1方式下，在互为冗余的A、B两个数据连接会话中，若A数据连接会话中的部分或全部流量(在采集周期内)被视为基础使用量，则B数据连接会话中的对应部分流量或全部流量(在采集周期内)被视为冗余使用量，反之亦然；类似地，在S2方式下，在互为冗余的A、B两个隧道中，若在A隧道中的部分或全部流量被视为基础使用量，则B隧道中的对应部分流量或全部流量就被视为冗余使用量，反之亦然；类似地，在S3方式下，在互为冗余的A、B两个传输层路径中，若在A传输层路径中的部分流量或全部流量被视为基础使用量，则B传输层路径中的对应部分流量或全部流量就被视为冗余使用量，反之亦然。
组合使用量：是指基础使用量与冗余使用量之和。例如，基础使用量是2M，冗余使用量也是2M，则组合使用量是2M+2M＝4M。
冗余业务计费处理方式：是指计费处理设备对冗余传输的数据连接业务进行计费处理的方式，有“包含冗余的计费处理”和“去除冗余的计费处理”之分。
包含冗余的计费处理：指计费处理设备对冗余传输的数据连接业务的基础使用量和冗余使用量都进行计费处理，如：账户扣减或话单写入等，其中，基础使用量与冗余使用量可以采用相同的费率，也可以采用不同的费率，具体取决于运营商的计费策略。
去除冗余的计费处理：指计费处理设备仅对冗余传输的数据连接业务的基础使用量进行计费处理，如：使用特定费率对基础使用量进行账户扣减、话单写入等，不对冗余使用量进行处理。
冗余使用量处理方式：冗余使用量处理是指计费触发设备对冗余传输的数据连接业务的配额和/或使用量进行管理，冗余使用量处理方式是冗余使用量处理的具体方式，有“含冗余的使用量处理”和“去除冗余的使用量处理”之分。
包含冗余的使用量处理：指为使上报的使用量包含冗余使用量(S2/S3)，或者为使上报的使用量满足计费处理设备执行包含冗余的计费处理的需求(S1)，计费触发设备对冗余传输的数据连接业务的数据流量采取的处理操作，该处理操作会因计费模式(在线计费或离线计费)、冗余传输方式的不同而不同，详见本申请实施例。
去除冗余的使用量处理：指为使上报的使用量不包含冗余使用量(S2/S3)，或者为使上报的使用量满足计费处理设备执行去除冗余的计费处理的需求(S1)，计费触发设备对冗余传输的数据连接业务的数据流量采取的处理操作，该处理操作会因计费模式、冗余传输方式的不同而不同，详见本申请实施例。
图4A所示的通信系统架构中，计费处理设备402可以通过部署在SMF设备或PGW-C上 的计费触发设备401获取数据连接会话415或者该数据连接会话中的数据连接业务的冗余传输的有关信息，据此进行计费处理，具体可以进一步参考图4B对应的方法流程；该方法流程中，如无特别说明，“计费触发设备”指计费触发设备401、“计费处理设备”指计费处理设备402、“用户设备”指用户设备411、“无线接入网络设备”指无线接入网络设备412、“用户面数据网关”指用户面数据网关413、“数据网络”指数据网络414、“数据连接会话”指数据连接会话415，将不再赘述。
图4B为本申请实施例提供的对冗余传输的数据连接业务进行计费处理的第一方法流程图。该方法流程中，计费处理设备根据计费触发设备上报的冗余传输信息，确定数据连接会话中的数据连接业务存在冗余传输，据此进行计费处理。计费触发设备和计费处理设备之间的交互，有以下可能的方案：
(1)计费处理设备基于冗余传输信息，确定所述数据连接会话需要计费处理，计费处理设备与计费触发设备为计费处理进行交互，具体有以下可能的方案：
(1.1)计费触发设备默认向计费处理设备上报组合使用量，计费处理设备基于上报的组合使用量，根据其确定的冗余业务计费处理方式进行计费处理；
(1.2)计费处理设备根据冗余业务计费处理方式的需要向计费触发设备下发使用量处理指示信息，计费触发设备根据该指示信息管理配额、获取并上报基础使用量，或者获取并上报基础使用量和冗余使用量。
(2)计费处理设备基于冗余传输信息，确定将进行去除冗余的计费处理，进而确定冗余的数据连接会话无需进行计费处理，终止或暂停与计费触发设备为计费处理而进行的交互。
图4B对应方法流程的具体步骤如下：
步骤430：计费触发设备向计费处理设备发送第一计费请求消息，该请求消息包含冗余传输信息。
具体地，计费触发设备获取冗余传输信息，即通信网络为所述数据连接会话中的第一数据连接业务实施或使用的冗余传输的信息，向计费处理设备发送第一计费请求消息，该请求消息中包含所述冗余传输信息；当然，除此了冗余传输信息之外，本领域技术人员知道，该计费请求消息中还可以包含其他与所述数据连接会话相关的信息，如所述第一数据连接会话的标识、所述第一数据连接业务的信息等。
本申请中的第一数据连接业务的粒度可以为数据连接会话粒度，也可以为数据连接会话中的QoS流粒度，将不再赘述。
在一种可能的方案中，所述冗余传输信息显式地指示(indicate)为所述第一数据连接业务使用了冗余传输，或者显式地指示所述数据连接业务的传输是冗余传输，例如，所述冗余传输信息可以是“RedundantIndicator＝true”这样的指示信息；具体地，“所述数据连接业务的传输是冗余传输”，对于S1方式，是指所述数据连接业务使用了冗余的数据连接会话，对于S2方式，是指所述数据连接业务使用了冗余的传输隧道，对于S3方式，是指使用了冗余的传输层路径。
在又一种可能的方案中，所述冗余传输信息还可以是隐式地指示所述第一数据连接业务使用了冗余传输的信息，例如：计费触发设备默认向计费处理设备同时上报组合使用量(例如，S2或S3方式下，用户面数据网关与无线接入网络设备之间传输的流量)与基础使用量(例如，S2或S3方式下，用户面数据网关与数据网络之间传输的流量)，计费处理设备基于 上报的组合使用量和基础使用量，确定所述第一数据连接业务为冗余传输的数据连接业务，则所述组合使用量和基础使用量共同形成了所述冗余传输信息。
在又一种可能的方案中，所述冗余传输信息还可以指示所述第一数据连接业务的冗余传输方式，例如：会话冗余、隧道冗余或传输层冗余；
在又一种可能的方案中，所述冗余传输信息还可以进一步指示所述数据连接会话的“地位”或在冗余传输中的角色，例如，指示所述数据连接会话为主数据连接会话或从数据连接会话，或者指示与所述数据连接会话互为冗余的另一个数据连接会话的有关信息，如另一个数据连接会话的标识、相应用户面数据网关的地址或标识等。
需要说明的是，上述几种冗余传输信息可以独立使用也可以组合使用。
可选地，第一计费请求消息还可以包括所述第一数据连接业务的传输时延。
本申请实施例中，计费请求消息具体可以为计费资源创建请求消息或计费资源更新请求消息，将不再赘述。
计费触发设备获取冗余传输信息的方式不限定，例如，计费触发设备可以通过数据连接会话建立请求消息包含的DNN(Data Network Name，数据网络名称)或S-NSSAI(Single Network Slice Selection Assistance Information，单网络切片选择支撑信息)以及本地配置的策略，确定所述数据连接会话的冗余传输方式。
步骤440：计费处理设备基于所述冗余传输信息进行计费处理。
具体地，计费处理设备接收并解析所述第一计费请求消息，从中获取所述冗余传输信息以及其他与所述数据连接会话相关的信息，进而进行计费处理，具体处理过程如下。
(1)如果所述冗余传输信息指示所述第一数据连接业务的传输为冗余传输，和/或，所述冗余传输方式指示所述第一数据连接业务的冗余传输方式，计费处理设备据此确定所述第一数据连接业务存在冗余传输，且进一步结合用户签约信息等，确定将对所述数据连接业务进行的冗余业务计费处理方式：包含冗余的计费处理或去除冗余的计费处理。为实现这两种冗余业务计费处理方式，计费处理设备进一步执行以下操作。
(1.1)计费处理设备从计费触发设备接收组合使用量，对组合使用量进行包含冗余的计费处理或去除冗余的计费处理。
具体地，计费处理设备可以从所述第一计费请求消息中获取所述组合使用量，也可以从计费触发设备接收另一个计费请求消息，从中获取所述组合使用量。
具体地，如果冗余业务计费处理方式为包含冗余的计费处理，则计费处理设备对所述组合使用量直接(即不区分出基础使用量和冗余使用量)进行计费处理，或者从所述组合使用量中区分出基础使用量和冗余使用量后，再分别进行计费处理，包括但不限于对基础使用量和冗余使用量采用不同的费率等，例如，计费处理设备可以将组合使用量的一半作为基础使用量，采用费率1计费，另外一半作为冗余使用量，采用费率2计费。
具体地，如果冗余业务计费处理方式为去除冗余的计费处理，则计费处理设备从所述组合使用量中得出基础使用量，对基础使用量进行计费处理。例如，计费触发设备上报的组合使用量为4M，则将组合使用量的一半2M作为基础使用量，再对该2M的基础使用量进行计费处理。
如果所述第一数据连接业务为在线计费业务(即应进行在线计费的数据连接业务)，计费处理设备还为所述第一数据连接业务授予配额(可以基于计费触发设备发送的配额申请被动授予，也可以在未收到计费触发设备发送的配额申请的情况下主动授予)；所述配额可以 是计费处理设备在相应账户中实际预留配额的两倍(这样可以减少计费触发设备向计费处理设备请求配额的次数)，也可以与实际预留配额相等；可选地，计费处理设备还可以生成与所述配额相应的第一处理指示信息，该指示信息指示(instruct)计费触发设备为所述配额对应的使用量设置冗余标记，所述冗余标记表明所述配额对应的使用量为冗余传输的数据连接业务的使用量；计费处理设备可以将所述第一处理指示信息随所述配额一起发送给计费触发设备，也可以不发送所述第一处理指示信息，而是将所述冗余标记与所述配额的对应关系保存在本地。
(1.2)计费处理设备向计费触发设备下发使用量处理指示信息，使计费触发设备执行包含冗余的使用量处理或者去除冗余的使用量处理，以分别满足包含冗余的计费处理和去除冗余的计费处理的需要。
具体地，计费处理设备基于所确定的冗余业务计费处理方式，生成第二处理指示信息：如果冗余业务计费处理方式为包含冗余的计费处理，则所述第二处理指示信息指示(instruct)计费触发设备为所述数据连接会话中的第二数据连接业务执行包含冗余的使用量处理操作；如果冗余业务计费处理方式为去除冗余的计费处理，则所述第二处理指示信息指示计费触发设备为所述第二数据连接业务执行去除冗余的使用量处理操作。
如果所述冗余传输信息指示所述第一数据连接业务的冗余传输方式为会话冗余或者传输层冗余，则所述第二数据连接业务与所述第一数据连接业务中的费率组对应、或者与所述第一数据连接业务中的QoS流对应或者与所述第一数据连接业务对应的数据连接会话对应。
如果所述冗余传输信息指示所述第一数据连接业务的冗余传输方式为隧道冗余，所述第二数据连接业务与所述第一数据连接业务中的费率组对应、或者与所述第一数据连接业务对应的QoS流对应。
(1.3)如果所述冗余传输信息为使用量和采集位置信息，则计费处理设备计算用户面数据网关两侧使用量之间的比例，如果用户面数据网关与无线接入网络设备之间的使用量是用户面数据网关与数据网络之间使用量的2倍，则确定所述第一数据连接业务存在S2或S3方式的冗余传输，进而确定冗余业务计费处理方式，再基于用户面数据网关两侧的使用量执行包含冗余的计费处理或者去除冗余的计费处理；计费处理设备可以将用户面数据网关与无线接入网络设备之间的使用量当作组合使用量，而将用户面数据网关与数据网络之间使用量当作基础使用量；如何执行包含冗余的计费处理或者去除冗余的计费处理，可参考本步骤(1.1)段中的相关描述；
执行包含冗余的计费处理或者去除冗余的计费处理成功之后，计费处理设备生成账户扣减成功的指示信息(对在线计费)或者写话单成功的指示信息(对离线计费)。
(2)如果所述冗余传输信息在指示冗余传输方式为会话冗余，且还进一步指示所述数据连接会话的“地位”或者在冗余传输中的角色，或者，还进一步包含与所述数据连接会话互为冗余的另一个数据连接会话的有关信息，为实现去除冗余的计费处理，计费处理设备可以在两个互为冗余的数据连接会话中择一进行计费处理，具体如下。
(2.1)假设所述冗余传输信息指示所述数据连接会话为从数据连接会话，则计费处理设备可以生成不计费指示信息，该指示信息用于向计费触发设备指示(indicate)计费处理设备因所述数据连接会话为从数据连接会话而不对其进行计费处理；
(2.2)假设所述冗余传输信息指示与所述数据连接会话互为冗余的另一个数据连接会话的有关信息，则计费处理设备选择对所述另一个数据连接会话执行计费，则对所述数据连 接会话生成不计费指示信息，该指示信息用于向计费触发设备指示(indicate)对与所述数据连接会话互为冗余的数据连接会话执行计费而不对所述数据连接会话执行计费处理。
应理解，在所述数据连接会话与另一个数据连接会话之间，计费处理设备不一定选择对所述数据连接会话不计费；关于在这两个数据连接会话之间做选择，本申请实施例不作限定具体选择方式；计费处理设备可以随机选择出一个数据连接会话，也可以选择传输时延较低的数据连接会话，如果这两个数据连接会话在不同的网络切片中，则还可以选择所在网络切片的优先级较高的数据连接会话；计费处理设备可以从计费触发设备发送的计费请求中获取数据连接会话的传输时延，从网络切片管理设备获取数据连接会话所在网络切片的优先级。
上述两点中的不计费指示信息可以有多种表示方式，例如，可以由“创建计费资源失败”以及“失败原因为数据连接会话不计费的指示信息”组成，详见本申请后续实施例。
若所述第一计费请求消息包含第一数据连接业务的传输时延，则计费处理设备根据所述冗余传输信息和所述传输时延进行计费处理；例如，计费处理设备根据所述传输时延选择需要计费的数据连接会话或者不需要计费的数据连接会话；再如，计费处理设备在上文所述执行去除冗余的计费处理或者包含冗余的计费处理过程中，根据所述传输时延确定使用量的计费费率；再如，计费处理设备根据所述传输时延，选择待计费的使用量(例如在S2方式下，计费触发设备可以分别上报每个传输隧道中的使用量及相应的传输时延，计费处理设备选择较小的传输时延对应的使用量)。
若所述数据连接业务为离线计费业务，则还包括：所述计费处理设备将所述第一数据连接业务的信息写入话单，所述第一数据连接业务的信息包括以下任意一项：冗余传输信息、使用量描述信息或传输时延(如果所述第一计费请求消息包含所述传输时延)。
步骤450：计费处理设备向计费触发设备发送第一计费响应消息，所述第一计费响应消息包含所述计费处理的结果。
具体地，计费处理设备构建第一计费响应消息并将其发送给计费触发设备，该响应消息包含计费处理结果，为以下项目之一：
-步骤440中计费处理设备授予的配额，或者，所述授予的配额和相应的第一处理指示信息；
-步骤440中计费处理设备生成的第二处理指示信息；
-步骤440中计费处理设备生成的账户扣减成功或者话单写入成功的指示信息；
-步骤440中计费处理设备生成的不计费指示信息。
本申请实施例中，计费响应消息具体可以为计费资源创建响应消息或计费资源更新响应消息，将不再赘述。所述第一计费响应消息可以是步骤430计费请求消息对应的响应消息，也可以是其他计费请求消息对应的响应消息。
计费触发设备接收并解析所述第一计费响应消息，从中获取计费处理设备提供的计费处理结果，基于该计费处理结果执行进一步的操作，具体操作如下。
(1)具体地，如果所述计费处理结果包含计费处理设备授予的配额以及相应的第一处理指示信息，则计费触发设备管理所述配额的消费，获取所述配额对应的使用量(为组合使用量)，且将所述使用量和上述冗余标记通过第二计费请求消息发送给计费处理设备；随后计费处理设备接收并解析所述第二计费请求消息，根据其中的冗余标记，对所述使用量进行包含冗余的计费处理或者去除冗余的计费处理。如果计费处理结果不包含所述冗余标记，则计费处理设备可以根据步骤440中在本地保存的冗余标记对所述使用量进行包含冗余的计费 处理或者去除冗余的计费处理。关于包含冗余的计费处理和去除冗余的计费处理，可以参考步骤440中的相关描述。
(2)具体地，如果计费处理结果包含计费处理设备生成的第二处理指示信息，则计费触发设备根据冗余传输方式的不同、所述第二处理指示信息所指示的冗余使用量处理方式的不同，进行不同的处理，具体如下：
(2.1)不论所述第一数据连接业务的冗余传输方式为会话冗余、隧道冗余还是传输层冗余，都可以按如下方式进行处理：
(2.1.1)如果所述第二处理指示信息指示为所述第二数据连接业务执行去除冗余的使用量处理，则计费处理设备根据该指示执行以下操作：
将所述数据连接会话中所述第二数据连接业务的冗余传输的流量的一半作为所述数据连接业务的使用量；如果所述第二数据连接业务为在线计费业务，则还用所述第二数据连接业务的使用量(即所述数据连接会话中所述第二数据连接业务的冗余传输的流量的一半)消费计费处理设备授予的配额。
(2.1.2)如果所述第二处理指示信息指示为所述第二数据连接业务执行包含冗余的使用量处理，则计费处理设备根据该指示执行以下操作：
将所述数据连接会话中所述第二数据连接业务的冗余传输的流量作为所述数据连接业务的使用量；如果所述第二数据连接业务为在线计费业务，则还用所述第二数据连接业务的使用量(即所述数据连接会话中所述第二数据连接业务的冗余传输的流量)消费计费处理设备授予的配额。
上述两点中“所述数据连接会话中所述第二数据连接业务的冗余传输的流量”，在S1方式下是指在所述数据连接会话中传输的所述第二数据连接业务的流量，在S2或S3方式下是指在所述数据连接会话对应的用户面数据网关与无线接入网络设备之间传输的所述第二数据连接业务的流量。
(2.2)如果所述第一数据连接业务的冗余传输方式为隧道冗余或者传输层冗余，可以按如下方式进行处理：
(2.2.1)如果所述第二处理指示信息指示为所述第二数据连接业务执行去除冗余的使用量处理，则计费处理设备根据该指示执行以下操作：
将在所述数据连接会话对应的用户面数据网关与数据网络之间传输的所述第二数据连接业务的流量作为所述第二数据连接业务的使用量；如果所述第二数据连接业务为在线计费业务，则还用所述第二数据连接业务的使用量(即在用户面数据网关与数据网络之间传输的所述第二数据连接业务的流量)消费计费处理设备授予的配额。
(2.2.2)如果所述第二处理指示信息指示为所述第二数据连接业务执行包含冗余的使用量处理，则计费处理设备根据该指示执行以下操作：
将在所述数据连接会话对应的用户面数据网关与无线接入网络设备之间传输的所述第二数据连接业务的流量作为所述第二数据连接业务的使用量；如果所述第二数据连接业务为在线计费业务，则还用所述第二数据连接业务的使用量(即在用户面数据网关与无线接入网络设备之间传输的所述第二数据连接业务的流量)消费计费处理设备授予的配额。
(2.3)不论所述第一数据连接业务的冗余传输方式为隧道冗余还是传输层冗余，都还可以按如下方式进行处理：
(2.3.1)如果所述第二处理指示信息指示为所述第二数据连接业务执行去除冗余的使 用量处理，则计费处理设备根据该指示执行以下操作：
将通过互为冗余的两条传输通路之一传输的所述第二数据连接业务的流量作为所述第二数据连接业务的使用量；如果所述第二数据连接业务为在线计费业务，则还用所述第二数据连接业务的使用量(即通过互为冗余的两条传输通路之一传输的所述第二数据连接业务的流量)消费计费处理设备授予的配额。
关于传输通路的选择方式，本申请实施例不作限定；计费触发设备可以在上述两条传输通路中随机选择一条，也可以选择传输时延较低的一条，如果两条传输通路在不同的网络切片中，则还可以选择所在网络切片优先级较高的传输通路；计费触发设备可以从用户面数据网关获取传输通路的传输时延。
(2.3.2)如果所述第二处理指示信息指示为所述第二数据连接业务执行包含冗余的使用量处理，则计费处理设备根据该指示执行以下操作：
将通过互为冗余的两条传输通路传输的所述第二数据连接业务的流量作为所述第二数据连接业务的使用量；如果所述第二数据连接业务为在线计费业务，则还用所述第二数据连接业务的使用量(即通过互为冗余的两条传输通路传输的所述第二数据连接业务的流量)消费计费处理设备授予的配额。
上述两点中，“互为冗余的两条传输通路”，在S2方式下是指两个传输隧道，在S3方式下是指两个传输层路径。
应理解，上述流量是指两次上报使用量的时间间隔内(或者采集周期内)的产生的流量。
获得使用量之后，计费触发设备将其通过又一个计费请求消息发送给计费处理设备。可选地，计费触发设备还可以为所获得的使用量(例如，所述第一数据连接业务中的费率组对应的使用量，或者所述第一数据连接业务中的QoS流对应的使用量)生成使用量描述信息，且将其与所获取的使用量一起发给计费处理设备，所述使用量描述信息用于描述所述使用量是否为执行去除冗余的使用量处理的流量，或者描述流量的发生位置，例如，所述使用量描述信息指示(indicate)以下任意一项：
-所述使用量是否为执行去除冗余的使用量处理的流量，具体可以为：未执行去除冗余的使用量处理的流量或者执行去除冗余的使用量处理后的流量；
-所述使用量为用户面数据网关的哪一侧的流量，具体可以为：用户面数据网关与无线接入网络设备之间传输的流量或者用户面数据网关与数据网络之间传输的流量。
(3)具体地，如果计费处理结果包含计费处理设备生成的不计费指示信息，则计费触发设备终止或暂停计费，例如，配额管理、使用量采集、与计费处理设备为计费处理而进行的交互(例如向计费处理设备请求配额、发送使用量等计费数据)。
可选地，计费触发设备可以监视数据连接会话，一旦发现所述数据连接会话变为主数据连接会话，则向计费处理设备发送第三计费请求消息，其中包含所述数据连接会话为主数据连接会话的指示信息，该指示信息可以通过上文所述的冗余传输信息表示。
上述操作步骤中，计费触发设备获取数据连接业务的使用量的方法不限定，例如：计费触发设备可以从用户面数据网关主动上报的消息中获取使用量，也可以向用户面数据网关发送获取使用量的请求消息，再从相应的响应消息或通知消息中获取使用量。可选地，获取使用量的请求消息可以指定需要用户面数据网关的哪一侧的流量，例如，该请求消息可以包含“NG-GW”的指示信息，表示需要获取在无线接入网络设备与用户面数据网关之间传输的流量，或者包含“GW-DN”的指示信息，表示需要获取在用户面数据网关与数据网络之间传输 的流量。
图4B的方法流程使得计费处理设备可以通过计费触发设备获知数据连接业务的冗余传输的情况，并基于冗余传输的情况进行计费处理，有助于提高计费的准确性，满足运营商或终端用户的多样化计费需求。
图5为本申请实施例提供的第二通信系统架构图，该通信系统是在图4A所示的通信系统基础上对每个设备以3GPP标准规范定义的设备为例形成，具体地，用户设备411以UE 511为例、接入网络设备412以gNB 512为例、用户面数据网关413以UPF设备513为例、数据网络414以DN 514为例、计费触发设备401的部署位置以部署于SMF设备501为例、计费处理设备402以CHF设备502为例、数据连接会话415以PDU会话515为例，如图5所示。示例性地，UPF设备513通过N3接口与gNB 512通信、通过N6接口与DN 514通信、通过N4接口与SMF设备501通信，SMF设备501通过N40接口与CHF设备502通信。
本申请后续实施例中，将基于图5所示架构描述方法流程，这些方法流程中，如果无特别说明，缺省情况下“SMF”指SMF设备501、“CHF”指CHF设备502、“UE”指UE 511、“gNB”指gNB 512、“UPF”指UPF设备513、“DN”指DN 514、“PDU会话”指PDU会话512。应注意，SMF设备501上部署了计费触发设备的功能，因此，在描述与计费有关操作的时候，例如，在与CHF交互、管理配额或采集使用量相关的描述中，所提及的“SMF”是指“CTF”。
本领域技术人员将图5中的设备替换为等同或类似的其他设备，得到与本申请实施例类似的技术方案，均属于本申请要保护的范畴。
图6A为本申请实施例提供的对冗余传输的数据连接业务进行计费处理的第二方法流程图，用于对PDU会话中的第一数据连接业务进行计费处理，CHF对SMF上报的组合使用量进行包含冗余的计费处理或者去除冗余的计费处理；该方法流程主要包括如下步骤：
步骤601：SMF为所述第一数据连接业务生成冗余传输信息RTI61。
具体地，所述第一数据连接业务的粒度为PDU会话粒度或者QoS流粒度。
SMF可以仅确定所述第一数据连接业务存在冗余传输，则生成的RTI61可以仅指示所述第一数据连接业务的传输为冗余传输；具体地，“所述第一数据连接业务的传输为冗余传输”，针对S1方式，是指所述第一数据连接业务使用了冗余的PDU会话，针对S2方式，是指所述第一数据连接业务使用了冗余的N3/N9传输隧道，针对S3方式，是指所述第一数据连接业务使用了冗余的传输层路径；
示例性的RTI61如下：
"RedundantIndicator":"True"//表示存在冗余传输
SMF还可以一步确定所述PDU会话的冗余传输方式，则生成的RTI61还指示所述第一数据连接业务的冗余传输方式。示例性的RTI61如下：
Figure PCTCN2021097739-appb-000001
或者
"RedundantIndicator":"2"//表示存在冗余传输且冗余传输方式为隧道冗余关于SMF确定冗余传输方式，示例性方法如下：
确定冗余传输方式为S1方式：SMF根据PDU会话建立请求中的DNN或S-NSSAI以及本地 配置信息确定所述PDU会话需要一个冗余的PDU会话，并向无线网络接入设备(如NG-RAN 103)发送指示建立双连接，如果所述无线网络接入设备建立双连接成功(SMF收到NG-RAN的响应消息中携带成功指示或者未携带失败指示)，则SMF确定所述PDU会话为冗余的PDU会话。
确定冗余传输方式为S2方式：在URLLC业务的QoS流建立期间或建立之后，如果SMF根据PDU会话建立请求中的DNN或S-NSSAI以及本地配置信息决定基于授权的5QI(5G QoS Indicator，5G QoS标识符)、NG-RAN的能力和/或运营商配置信息对所述第一数据连接业务进行冗余传输，则SMF通过N4接口通知PSA UPF以及通过N2接口通知NG-RAN进行冗余传输。
确定冗余传输方式为S3方式：UE建立URLLC业务的PDU会话时，SMF基于DNN、S-NSSAI、NG-RAN支持传输层冗余传输的能力等，为PDU会话选择支持传输层冗余传输的UPF，以在UPF与NG-RAN之间建立两条互为冗余的传输层路径。
可选地，生成的RTI61还可以进一步指示所述PDU会话为主PDU会话或从PDU会话，或者指示与所述PDU会话互为冗余的另一个PDU会话的有关信息，如另一个PDU会话的标识、相应用户面数据网关的地址或标识等。示例性的RTI61如下：
Figure PCTCN2021097739-appb-000002
若SMF确定所述第一数据连接业务为在线计费业务(即需要进行在线计费的数据连接业务)，则转步骤602；
若SMF确定所述第一数据连接业务为离线计费业务(即需要进行离线计费的数据连接业务)，则转步骤610。
步骤602：SMF向CHF发送计费请求消息，该请求消息中包含RTI61、所述PDU会话的标识SesId61和配额申请RSU61(可选的)。
具体地，SMF构建计费请求消息并将其发送给CHF，其中包含RTI61、SesId61；可选地，所述计费请求消息还包含RSU61，其中RSU61用于为所述第一数据连接业务中的一个或多个费率组申请配额。可选地，所述计费请求消息还包含传输时延。
假定所述计费请求消息为计费资源创建请求，则示例性消息结构如下：
Figure PCTCN2021097739-appb-000003
需说明，不同的冗余传输方式下，冗余传输信息RTI与数据连接业务的对应关系不同，如：对于S1方式或S3方式，RTI可以与PDU会话标识对应；对于S2方式，RTI可以与QoS 流标识对应。
可选地，所述计费请求消息还可以包括所述第一数据连接业务的传输时延。当所述第一数据连接业务与PDU会话对应或者与QoS流对应的情况下，所述传输时延的示例表示分别如下：
"SesId":"SesId61"//所述PDU会话的标识
"Delay":"50ms"//所述PDU会话对应的传输时延
为叙述方便，本申请实施例将与PDU会话对应的传输时延称为“PDU会话粒度的传输时延”。
或者
"QFI":"Qosflow61"//所述PDU会话中某一QoS流的标识(QFI)
"Delay":"100ms"//所述QoS流对应的传输时延
为叙述方便，本申请实施例将QoS流对应的传输时延称为“QoS粒度的传输时延”。
步骤603：CHF根据RTI61和/或所述传输时延，确定冗余业务计费处理方式RCM61。
具体地，CHF接收并解析所述计费请求消息，从中获取RTI61、SesId61和RSU61(若有)和所述传输时延(若有)。CHF基于RTI61，确定所述第一数据连接业务的传输是冗余传输。CHF进一步根据CHF计费策略或者用户签约信息和/或所述传输时延(如果有)，确定对所述第一数据连接业务的冗余业务计费处理方式RCM61；例如，CHF可以基于所述RTI和用户签约信息确定对所述第一数据连接业务采用包含冗余的计费处理，也可以确定为其采用去除冗余的计费处理；CHF也可以在所述传输时延高于预设阈值时，确定采用包含冗余的计费处理，而在所述传输时延低于预设阈值时，确定采用去除冗余的计费处理。
步骤604：CHF根据RCM61，授予配额GSU61。
具体地，假设CHF在用户账户中实际预留的配额为A，则：如果RCM61为包含冗余的计费处理，则GSU61为A；如果RCM61为去除冗余的计费处理，则GSU61可以为A，也可以为2A。
可选地，CHF还可以为GSU61生成相应的处理指示信息ProcInd(对应上文第一处理指示信息)，用于指示SMF为GSU61对应的使用量设置冗余标记，以便后续CHF将GSU61对应的使用量当成冗余传输的数据连接业务的使用量执行包含冗余的计费处理或者去除冗余的计费处理。
可选地，CHF可以基于RSU61为所述第一数据连接业务授予上述配额。
步骤605：CHF向SMF返回计费响应消息，该响应消息包含GSU61和ProcInd(可选)。
具体地，CHF构建计费响应消息并将其发送给SMF,所述响应消息包含GSU61，可选地，所述响应消息还包含ProcInd。如果所述计费响应消息中不包含ProcInd，则CHF可以为GSU61生成冗余标记Uflg，且在本地将GSU61的标识与Uflg对应存储，其中冗余标记Uflg用于指示(indicate)GSU61的使用量为冗余传输的数据连接业务的使用量。
示例性的计费响应消息如下：
Figure PCTCN2021097739-appb-000004
Figure PCTCN2021097739-appb-000005
步骤606：SMF获取GSU61对应的使用量USU61。
具体地，SMF接收并解析上述计费响应消息，从中获取GSU61和ProcInd(如果有)，进而为所述第一数据连接业务消费所述GSU61，并记录GSU61的使用量USU61。
具体地，针对不同的冗余传输方式，SMF可以用表1(其中数据连接业务为所述第一数据连接业务)中“数据流量”列的流量消费配额GSU61，并记录对应的使用量USU61。SMF可以将GSU61发给UPF(以使UPF以GSU61为限放通业务数据流)。
表1
Figure PCTCN2021097739-appb-000006
如果上述计费响应消息中包含ProcInd，则SMF还为USU61生成冗余标记Uflg，用于指示(indicate)USU61为冗余传输的数据连接业务的使用量。
步骤607：SMF向CHF发送计费请求消息，该请求消息包含USU61、冗余标记Uflg(可选)和传输时延(可选)。
具体地，SMF构建计费请求消息并将其发送给CHF，所述更新请求消息包含USU61、Uflg(如果此前CHF下发了ProcInd)和传输时延(可选)。
示例性的计费请求消息如下：
Figure PCTCN2021097739-appb-000007
应理解，Uflg与USU61对应，具体数据结构不限。
可选地，所述计费请求消息还包含传输时延，所述传输时延为在发送上述计费请求消息对应的上报周期内的PDU会话粒度的传输时延或者QoS流粒度的传输时延；可选地，所述传输时延在所述计费请求消息中可以与PDU会话标识、QoS流标识或者费率组对应。
步骤608：CHF根据RCM61/Uflg，基于USU61进行账户扣减。
具体地，CHF从SMF接收并解析所述计费请求消息，从中获取USU61、Uflg(如果有)和传输时延(可选)。进而，CHF根据RCM61/Uflg/时延，基于USU61进行账户扣减。
具体地，如果USU61有对应的Uflg(冗余标记)，则CHF确定USU61是冗余传输的数据连接业务的使用量，进而确定需要根据RCM61对USU61进行账户扣减。如果RCM61是包含冗余的计费处理，则CHF在费率组RG1对应的账户中扣减USU61对应的使用量(2M)或相应费用；如果RCM61是去除冗余的计费处理，则CHF在所述账户中扣减USU61对应的使用量的一半或相应费用。
CHF通过ProcInd指示SMF为USU61设置冗余标记Uflg，可以更为准确的识别使用量是否为包含冗余流量的使用量，进而根据冗余传输的计费需求灵活地授予配额及使用量处理，如：只对其中部分数据连接业务执行包含冗余的计费处理或去除冗余的计费处理，其他数据连接业务按传统计费方式进行计费。
可选地，CHF还可以根据所述传输时延确定所述账户扣减过程中所采用的费率。
步骤609：CHF向SMF发送计费响应消息，该响应消息包含账户扣减成功的指示信息。若有授予的配额，则同步骤605。
此后，SMF可以通过计费请求消息持续向CHF申请配额和/或上报新的使用量。
步骤610：SMF向CHF发送计费请求消息，该请求消息中包含RTI61、所述PDU会话的标识SesId61。
具体地，SMF构建计费请求消息并将其发送给CHF，其中包含RTI61和SesId6，可选的，还包括传输时延。
假定所述计费请求消息为计费资源创建请求，消息示例如下：
Figure PCTCN2021097739-appb-000008
需说明，不同的冗余传输方式下，冗余传输信息RTI与数据连接业务的对应关系不同，如：对于S1方式或S3方式，RTI可以与PDU会话标识对应；对于S2方式，RTI可以与QoS流标识对应。
步骤611：CHF根据RTI61等信息，确定冗余业务计费处理方式RCM62。
该步骤与步骤603类似，不再赘述。
步骤612：CHF向SMF返回计费响应消息，可选地，该响应消息包含ProcInd。
该步骤与步骤605类似(除了不授予配额)，不再赘述。
示例性的计费响应消息如下：
ChargingResourceCreateResponse{
   "ResId":"ResId61"//计费资源标识
}
可选地，CHF还可以在所述响应消息中包含处理指示信息ProcInd，用于指示SMF为其上报的使用量设置冗余标记Uflg。与步骤605的ProcInd不同，步骤605的ProcInd对应为某一费率组授予的配额，而这里ProcInd可以对应所述第一数据连接业务的某一个费率组或者某几个费率组或者所有费率组。
步骤613：SMF获取使用量USU62。
SMF获取使用量USU62的方式与步骤606中获取使用量USU61方式相同，不再赘述。
可选地，如果上述计费响应消息还包含ProcInd，则SMF还可以为USU62生成冗余标记Uflg，用于指示USU62为冗余传输的数据连接业务的使用量。
步骤614：SMF向CHF发送计费请求消息，该请求消息包含USU62、冗余标记Uflg(可选)和传输时延(可选)。
具体地，SMF构建计费请求消息并将其发送给CHF，所述更新请求消息包含ResId61、USU61、Uflg(可选)和传输时延(可选)。
示例性的计费请求消息如下：
Figure PCTCN2021097739-appb-000009
步骤615：CHF根据RCM62/Uflg，基于USU62写话单。
具体地，CHF从SMF接收并解析所述计费请求消息，从中获取USU62、Uflg(如果有)和传输时延(如果有)。进而，CHF将冗余传输信息、使用量、使用量描述信息或传输时延写入所述PDU会话的话单。
具体地，如果USU62有对应的Uflg，则CHF确定USU62是冗余传输的数据连接业务的使用量，进而确定需要根据RCM62对USU62写话单。如果RCM62是包含冗余的计费处理，则CHF在所述话单中写入USU62对应的使用量(4M)；如果RCM62是去除冗余的计费处理，则CHF在所述话单写入USU62对应的使用量的一半。如果所述话单不存在，CHF创建所述话单。
可选地，CHF也可以将RTI61、RCM62或Uflg中的任意一项或多项以及USU62写入所述话单。
步骤616：CHF向SMF发送计费响应消息，该响应消息中包含写话单成功的指示信息。
此后，SMF可以通过计费请求消息持续向CHF上报新的使用量，直到所述PDU会话中断，流程结束。
上述图6A对应的方法流程使得CHF可以根据SMF上报的信息及时感知冗余传输的存在，据此对SMF上报的组合使用量执行去除冗余的计费处理或包含冗余的计费处理，可以避免因冗余传输而引起的计费不准确的问题，也可以满足多样化的计费需求。
图6B为本申请实施例提供的对冗余传输的数据连接业务进行计费处理的第三方法流程图，用于对PDU会话中的第一数据连接业务进行计费处理，SMF执行去除冗余的使用量处理或者包含冗余的使用量处理，以使CHF可以执行去除冗余的计费处理或包含冗余的计费处理；该方法流程主要包括如下步骤：
步骤651：SMF为所述第一数据连接业务生成冗余传输信息RTI62。
该步骤与步骤601类似，不赘述。
若SMF确定QF2为在线计费业务，则转步骤652；
若SMF确定QF2为离线计费业务，则转步骤660。
步骤652：SMF向CHF发送计费请求消息，该请求消息中包含所述PDU会话的标识SesId62、RTI62和配额申请RSU62(可选)。
该步骤与步骤602类似，不再赘述。可选地，所述计费请求消息还可以包含传输时延。
假定所述计费请求消息为计费资源创建请求，消息示例如下：
Figure PCTCN2021097739-appb-000010
步骤653：CHF根据RTI62和/或传输时延，确定冗余业务计费处理方式RCM63、生成配额及使用量管理指示信息QUMI。
具体地，CHF接收并解析所述计费请求消息，从中获取RTI62、SesId62、RSU62(若有)和传输时延(若有)。CHF基于RTI62，确定所述第一数据连接业务的传输为冗余传输。CHF进一步根据计费策略或者用户签约信息，确定对所述数据连接业务的冗余业务计费处理方式RCM63；例如，RCM63可以确定为包含冗余的计费处理，也可以确定为去除冗余的计费处理。
进而，CHF基于RCM63生成配额及使用量管理指示信息QUMI(对应上文“第二处理指示信息”)，用于指示SMF对第二数据连接业务执行某种方式的冗余使用量处理：如果RCM63为包含冗余的计费处理，则QUMI用于指示SMF对所述第二数据连接业务执行包含冗余的使用量处理；如果RCM63为去除冗余的计费处理，则QUMI用于指示SMF对所述第二数据连接业务执行去除冗余的使用量处理。
当所述第一数据连接业务的冗余传输方式为会话冗余或者传输层冗余，所述第二数据连接业务与所述第一数据连接业务中的费率组对应，或者与所述第一数据连接业务中的QoS流对应，或者与所述第一数据连接业务对应的数据连接会话对应。
所述第一数据连接业务的冗余传输方式为隧道冗余，所述第二数据连接业务与所述第一数据连接业务中的费率组对应，或者与所述第一数据连接业务对应的QoS流对应。
应理解，QUMI可以对应所述PDU会话中的所有数据连接业务，也可以对应所述PDU会话中的某个或某些QoS流，可以对应所述PDU会话中QoS流中的某个业务标识对应的业务数据流，还可以对应PDU会话中的费率组。例如，假设对所述PDU会话中的QoS流QF2进行计费 处理，则QUMI可以对应QoS流QF2中部分业务数据流，如其中的某个费率组对应的几个业务数据流。这里“对应”的含义是“作用范围”，即QUMI用于指示SMF对什么范围的数据连接业务执行某种方式的冗余使用量处理。这样，CHF可以针对冗余传输的数据连接业务中的一部分业务数据流下发QUMI。
步骤654：CHF根据RCM63，授予配额GSU62。
具体地，CHF基于RSU62为所述第一数据连接业务授予配额GSU62。
具体地，假设CHF在用户账户中实际预留的配额为A，则：如果RCM63为包含冗余的计费处理，则GSU62为A；如果RCM63为去除冗余的计费处理，则GSU62可以为A，也可以为2A。
可选地，CHF可以基于RSU62为所述第一数据连接业务授予配额GSU62。
步骤655：CHF向SMF返回计费响应消息，该响应消息包含GSU62和QUMI。
具体地，CHF构建计费响应消息并将其发送给SMF,所述响应消息包含GSU62和QUMI。
示例性的计费响应消息如下：
Figure PCTCN2021097739-appb-000011
步骤656：SMF根据QUMI，获取GSU62对应的使用量USU63。
具体地，SMF接收并解析步骤上述计费响应消息，从中获取GSU62和QUMI，进而根据QUMI，为所述数据连接业务消费所述GSU62，并记录对应的使用量USU63。
具体地，针对不同的配额及使用量管理指示信息、不同的冗余传输方式，SMF可以用表3(其中的数据连接业务为所述第二数据连接业务)中“数据流量”列的流量消费配额GSU62，并记录对应的使用量USU63。SMF可以将GSU62发给UPF，以使UPF以GSU62为限放通所述第二数据连接业务的业务数据流，并基于UPF上报的消息获取表3中“数据流量”列所示的数据流量。
表3
Figure PCTCN2021097739-appb-000012
Figure PCTCN2021097739-appb-000013
可选地，SMF还为USU63生成使用量描述信息UD63；UD63指示(indicate)所述使用量为如下任意一项：
-未执行去除冗余的使用量处理的流量，
-执行去除冗余的使用量处理后的流量，
-用户面数据网关与无线接入网络设备之间传输的流量，
-用户面数据网关与数据网络之间传输的流量。
UD63可以指示上述4种信息，或者更详细的，还可以包含表3中“数据流量”列中的信息。
示例性的UD63参见步骤657。
步骤657：SMF向CHF发送计费请求消息，该请求消息包含USU63、UD63(可选)和传输时延Delay(可选)。
具体地，SMF构建计费请求消息并将其发送给CHF，所述更新请求消息包含USU63、UD63(可选)和传输时延(可选)。
示例性的计费请求消息如下：
Figure PCTCN2021097739-appb-000014
Figure PCTCN2021097739-appb-000015
执行去除冗余的使用量处理得到的USU，其UD63还可以形如：
"UD":"UPF-DN"//指示上述8M为在UPF与DN之间传输的流量
"UD":"gNB-UPF/2"//指示上述8M为在UPF与gNB之间传输的流量的一半
"UD":"1 N3 Tunnel"//指示上述8M为在两个N3隧道之一传输的流量
"UD":"1 TL path"//指示上述8M为在两个传输层路径之一传输的流量
执行包含冗余的使用量处理得到的USU，其UD63可以形如：
"UD":"-UPF-"//指示上述8M为在UPF中传输的流量
"UD":"gNB-UPF"//指示上述8M为gNB与UPF之间的流量
"UD":"2*UPF-DN"//指示上述8M为在UPF与DN之间传输的流量的两倍
"UD":"2 N3 Tunnels"//指示上述8M为在两个N3隧道传输的流量
"UD":"2 TL paths"//指示上述8M为在两个传输层路径传输的流量
应理解，UD63可以在USU63对应的数据结构内部，也可以与USU63对应的数据结构并列。
可选的，所述计费请求消息还包含传输时延，具体可以参见步骤607中的相关说明。
步骤658：CHF根据RCM63，基于USU63/UD63进行账户扣减。
具体地，CHF从SMF接收并解析所述计费资源更新请求消息，从中获取USU63、UD63(如果有)和传输时延(可选)。进而，CHF根据RCM63/UD63/所述传输时延，基于USU63进行账户扣减。
具体地，CHF根据UD63确定USU63中的具体流量(8M)是SMF通过执行此前CHF下发的QUMI指示得到的，进而直接在QoS流QF2对应的账户中扣减USU63对应的流量(8M)或相应费用。如果上述计费资源更新请求消息中没有UD63，则CHF默认USU63中的具体流量(8M)是SMF通过执行包含冗余的使用量处理得到，进而，如果RCM63为去除冗余的计费处理，则CHF在QoS流QF2对应的账户中扣减USU63对应的流量(8M)的一半(即4M)或相应费用的一半。
可选地，CHF可以根据所述传输时延确定所述账户扣减中所采用的费率，例如，对较低的时延对应的使用量采用较高的费率。
步骤659：CHF向SMF发送计费资源更新响应消息，该响应消息包含账户扣减成功的指示信息。若有授予的配额，则同步骤654。
此后，SMF可以通过计费资源更新请求消息持续向CHF申请配额和/或上报新的使用量。
步骤660：SMF向CHF发送计费请求消息，该请求消息中包含RTI62和所述PDU会话的标识SesId62。
该步骤与步骤610类似，将不再赘述。
步骤661：CHF根据RTI62，确定冗余业务计费处理方式RCM64、生成使用量管理指示信息UMI
与步骤653相比，UMI与QUMI相比，前者用于离线计费模式，后者用于在线计费模式，其他该步骤与步骤653类似。
步骤662：CHF向SMF返回计费响应消息，该响应消息包含CHF的计费处理结果信息和UMI。
该步骤与步骤654类似(除了不授予配额)，不再赘述。
步骤663：SMF根据UMI，获取使用量USU64。
具体地，SMF接收并解析上述计费响应消息，从中获取UMI，进而根据UMI，获取使用量USU64。SMF获取USU64的方法与步骤654相同，不再赘述。
可选地，SMF还为USU64生成使用量描述信息UD64，具体可以参考步骤654中的相关描述。
步骤664：SMF向CHF发送计费资源更新请求消息，该请求消息包含ResId62、USU64、UD64(可选)和传输时延Delay(可选)。
具体地，SMF构建计费资源更新请求消息并将其发送给CHF，所述更新请求消息包含ResId62、USU64、UD64(可选)和传输时延(可选)。
示例性的计费资源更新请求消息如下：
Figure PCTCN2021097739-appb-000016
更多UD64的例子，可以参考步骤657中的相关描述。
步骤665：CHF根据RCM64/UD64，基于USU64写话单。
具体地，CHF从SMF接收并解析所述计费资源更新请求消息，从中获取USU64、UD64(如果有)和传输时延(可选)。进而，CHF将冗余传输信息、使用量、使用量描述信息或传输时延写入所述PDU会话对应的话单。
具体地，CHF根据UD64确定USU64中的具体流量(8M)是SMF通过执行此前CHF下发的UMI指示得到的，进而直接在所述话单中写入USU64对应的流量(8M)。如果上述计费资源更新请求消息中没有UD64，则CHF默认USU64中的具体流量(8M)是SMF通过执行包含冗余的使用量处理得到，进而，如果RCM64为去除冗余的计费处理，则CHF在所述PDU会话对应的话单中写入USU64对应的流量(8M)的一半(即4M)。如果所述话单不存在，CHF创建所述话单。
可选地，CHF也可以将RTI62、RCM64或UD64中的任意一项或多项以及USU64写入所述话单。
步骤666：CHF向SMF发送计费资源更新响应消息，该响应消息中包含话单写入成功的指示信息。
此后，SMF可以通过计费资源更新请求消息持续向CHF上报新的使用量，直到所述PDU会话中断，流程结束。
上述图6B对应的方法流程使得CHF不仅可以根据SMF上报的信息及时感知冗余传输的存在，还可以针对数据连接业务中的部分业务数据流，指示SMF上报经过包含冗余的使用量处理的流量或者去除冗余的使用量处理的流量，可以省去SMF上不必要的性能开销，也可以 减少SMF与CHF之间的带宽消耗。此外，由于使用量是由与UPF直接交互的SMF按需地进行采集，也可以在一定程度上提高计费的精确性。
图7A为本申请实施例提供的第三通信系统架构图，该通信系统是在图5所示的通信系统基础上增加了gNB 522、UPF 523、SMF 521，这样在UE与DN之间可以建立第二个PDU会话，即UE 511-gNB 522-UPF 523-DN 514之间的PDU会话。为便于区分，该PDU会话称为PDU会话2，而PDU会话515，称为PDU会话1，SMF 501称为SMF1，SMF 521称为SMF2。
图7B为本申请实施例提供的对冗余传输的数据连接业务进行计费处理的第四方法流程图，该方法流程基于图7A所示架构实现，其中，假设PDU会话1和PDU会话2互为冗余的PDU会话，CHF对它们执行去除冗余的计费处理，在它们中择一进行计费处理。该方法流程主要包括如下步骤：
步骤701-1：SMF1为PDU会话1中的数据连接业务生成冗余传输信息RTI71。
步骤701-2：SMF2为PDU会话2中的数据连接业务生成冗余传输信息RTI72。
以上两个步骤与步骤601类似，不赘述。
步骤702-1：SMF1向CHF发送计费请求消息，该请求消息包含RTI71、PDU会话1的标识SesId71和传输时延Delay71(可选)。
具体地，SMF1确定对互为冗余的PDU会话1执行计费，则向CHF发送计费请求消息。
该步骤与步骤660类似，不再赘述。
示例性的计费资源创建请求消息如下：
Figure PCTCN2021097739-appb-000017
或者
Figure PCTCN2021097739-appb-000018
其中，主PDU会话是指主NG-RAN对应的PDU会话，从PDU会话为从NG-RAN对应的PDU会话。
随后，CHF接收并解析本步骤所述计费请求消息，从中获取SedId71和RTI71，且基于RTI71等信息，确定对PDU会话1执行去除冗余的计费处理。
如果CHF确定对PDU会话1执行包含冗余的计费处理，则进一步的操作可以参考图6A或图6B对应的方法流程。
步骤702-2：SMF2向CHF发送计费请求消息，该请求消息包含RTI72、PDU会话2的标识SesId72和传输时延Delay72(可选)。
具体地，SMF2确定对互为冗余的PDU会话1执行计费，则不向CHF发送计费请求消息，此时意味着对于该互为冗余的两个PDU会话，只会对PDU会话1执行计费；或者，SMF2确定对互为冗余的PDU会话2执行计费，则向CHF发送计费请求消息。
该步骤与步骤660类似，不再赘述。
示例性的计费资源创建请求消息如下：
Figure PCTCN2021097739-appb-000019
或者
Figure PCTCN2021097739-appb-000020
随后，CHF接收并解析步骤所述计费资源创建请求消息，从中获取SedId72和RTI72，且基于RTI72和计费策略，确定对PDU会话2执行去除冗余的计费处理。
步骤703：CHF确定执行去除冗余的计费处理：对PDU会话1计费，对PDU会话2不计费。
具体地，如果RTI71或RTI72包含"RoleInRT"字段(表示相应PDU会话在冗余传输中的角色：是主PDU会话还是从PDU会话)，则CHF可以根据该字段所表示的信息，确定对哪一个PDU会话进行计费；通常，CHF决策对主PDU会话进行计费，而对从PDU会话不计费；因此，CHF向SMF2发送“不计费”的指示信息NoChgInd(CHF可以在仅收到步骤702-2的计费资源创建请求消息就发送NoChgInd)。
具体地，如果RTI71或RTI72包含"SiblingSession"字段，则CHF可以根据该字段确定 对哪一个PDU会话进行计费，例如，CHF可以随机选择一个PDU会话进行计费。如果RTI71或RTI72还包含"Delay"字段(表示相应PDU会话在UE与相应UPF之间的时延)，则CHF可以在两个计费资源创建请求消息都收到之后，比较两个PDU会话的时延，而选择对时延较小的PDU会话进行计费。如果RTI71或RTI72还包含"NSId"字段(表示相应PDU会话所在网络切片的标识)，则CHF可以在两个计费资源创建请求消息都收到之后，基于"NSId"字段获取每个PDU会话所在网络切片的优先级信息(例如，向网络切片管理设备查询该优先级信息)，进而选择对所在网络切片的优先级较高的那个PDU会话进行计费。这样确定之后，CHF向不需要计费的PDU会话对应的SMF发送“不计费”的指示信息NoChgInd。
应理解，本申请实施例对“不计费”指示信息的形式不做限定。
应理解，若本申请实施例中，若CHF确定对PDU会话1和PDU会话2同时计费，则其处理参见图6A和图6B对应实施例。
以下假设CHF的决策是对PDU会话1计费，对PDU会话2不计费。
步骤704-1：CHF向SMF1发送计费资源创建响应消息。
具体地，CHF构建计费资源创建响应消息并将其发送给SMF1。
步骤704-2：CHF向SMF2发送计费资源创建响应消息，该响应消息包含NoChgInd。
具体地，CHF构建计费资源创建响应消息并将其发送给SMF2，该响应消息包含NoChgInd。
步骤705-1：SMF1为PDU会话1执行计费操作。
具体地，SMF1为PDU会话1执行计费相关操作，例如为PDU会话1中的数据连接业务向CHF申请配额、将PDU会话1中的数据连接业务的使用量上报给CHF等。
步骤705-2：SMF2停止为PDU会话2执行计费操作。
具体地，SMF2结束或暂停为PDU会话2执行计费。
步骤706-1：SMF1发现PDU会话1变为从PDU会话。
具体地，SMF1根据UE发送的信息，确定PDU会话1变为从PDU会话。
步骤706-2：SMF2发现PDU会话2变为主PDU会话。
具体地，SMF2根据UE发送的信息，确定PDU会话2变为主PDU会话。
步骤707-1：SMF1向CHF发送计费资源更新请求消息，该请求消息中包含“变为从PDU会话”的指示信息ToSecondary。
步骤707-2：SMF2向CHF发送计费资源更新请求消息，该请求消息中包含“变为主PDU会话”的指示信息ToMastery。
步骤708：CHF确定对PDU会话2计费，对PDU会话1不计费。
该步骤与步骤703类似，不赘述。
步骤709-1：CHF向SMF1发送计费资源更新响应消息，该响应消息包含NoChgInd。
步骤709-2：CHF向SMF2发送计费资源更新响应消息。
步骤710-1：SMF1停止为PDU会话1执行计费操作。
该步骤与步骤705-2类似，不赘述。
步骤710-2：SMF2为PDU会话2执行计费操作。
该步骤与步骤705-1类似，不赘述。
应理解，上述步骤之间的顺序是示例性的，不是限定，例如，步骤702-1和步骤702-2之间、步骤704-2和步骤704-2之间、步骤705-1和步骤705-2之间的顺序可以颠倒。
上述图7B对应的方法流程使得CHF可以在两个互为冗余的PDU会话中选择一路进行计 费处理，可以减少SMF的性能开销，也可以降低SMF与CHF之间的带宽消耗。
应理解，以上不同方法流程之间的技术方案可以自由组合，例如，图6B中的使用量描述信息也可以用于图6A的方法流程。
还需要说明的是，本申请实施例均是以“两路冗余”为例进行方案描述，即：S1方式有两个PDU会话，S2方式有两个传输隧道，S3方式有两条传输层路径。而随着可靠性要求的提升，还可能有“多路冗余”的方案，本领域技术人员可以在其基础上扩展到支持“多路冗余”的方案。例如，假设是互为冗余的总路数是R路，则在本申请实施例中通过“减半”的方式去除冗余的使用量处理(如步骤609、步骤615、步骤656等)中，可以将比率调整为(R-1)/R，通过“二选一”方式去除冗余的使用量处理(如步骤656、步骤663等)，可以改为“R选一”，例如在R个互为冗余的N3隧道中选择一个隧道，或者在R个互为冗余的PDU会话中选择一个PDU会话等，不再赘述。
图8为本申请实施例提供的计费触发设备、计费处理设备的硬件结构图。本申请实施例中的所有计费触发设备(或者SMF设备、CTF设备，例如，图4B的430)、计费处理设备(或者CHF设备，例如，图4B的440)，均可以采用图8所示的通用的计算机硬件结构实现，其中包括处理器801、存储器802、总线803、输入设备804、输出设备805以及网络接口806，其中输入设备804与输出设备805为可选的。
具体地，存储器802可以包括以易失性和/或非易失性存储器形式的计算机存储媒体，如只读存储器和/或随机存取存储器。存储器802可以存储操作系统、应用程序、其他程序模块、可执行代码和程序数据。
输入设备804可以用于输入信息，便于系统管理员对计费触发设备、计费处理设备进行操作和管理等，例如，在计费处理设备上配置计费策略、在计费触发设备上设置默认的使用量获取方式等；输入设备804可以为键盘或指向设备，如鼠标、轨迹球、触摸板、麦克风、操纵杆、游戏垫、卫星电视天线、扫描仪或类似设备，均可以通过总线803连接至处理器801。
输出设备805可以用于输出信息，便于系统管理员对计费触发设备、计费处理设备进行操作和管理等；例如，在计费处理设备上显示计费策略、在计费触发设备上显示默认的使用量获取方式等；除了监视器之外，输出设备805还可以为其他外围输出设备，如扬声器和/或打印设备，也均可以通过总线803连接到处理器801。
计费触发设备、计费处理设备均可以通过网络接口806连接到网络中，例如连接到局域网(Local Area Network，LAN)。在联网环境下，计费触发设备、计费处理设备中存储的计算机执行指令可以存储在远程存储设备中，而不限于在本地存储。
当计费触发设备中的处理器801执行存储器802中存储的可执行代码或应用程序时，计费触发设备可以执行以上所有实施例中与计费触发设备(或SMF)相对应的方法步骤，如步骤430、601、606、613、651、656、663、701-1和705-2等；具体执行过程均参见上述实施例，在此不再赘述。
当计费处理设备中的处理器801执行存储器802中存储的可执行代码或应用程序时，计费处理设备可以执行以上所有实施例中与计费处理设备(或CHF)相对应的方法步骤，如步骤440、603、604、608、615、653、661、665、703和708；具体执行过程均参见上述实施例，在此不再赘述。
图9为本申请实施例提供的计费处理设备的逻辑结构示意图，所述计费处理设备与计费触发设备连接，包括：
-接收模块901，用于从所述计费触发设备接收第一计费请求消息，所述第一计费请求消息包含冗余传输信息，所述冗余传输信息是指为数据连接会话中的第一数据连接业务使用的冗余传输的相关信息，具体执行过程参见上述实施例中计费处理设备(或SMF)侧的步骤说明，如步骤430、602、607、610、652、657、702-1和702-2等；
-发送模块902，用于基于所述冗余传输信息进行计费处理，得到计费处理结果，且向所述计费触发设备发送第一计费响应消息，具体执行过程参见上述实施例中计费处理设备(或SMF)侧的步骤说明，如步骤440、603、604、653、654、661、703和708等。
图10为本申请实施例提供的计费触发设备的逻辑结构示意图，所述计费触发设备与计费处理设备通信，包括：
-发送模块1001，用于向所述计费处理设备发送第一计费请求消息，所述第一计费请求消息包含冗余传输信息，所述冗余传输信息是指为数据连接会话中的第一数据连接业务使用的冗余传输的相关信息，具体执行过程参见上述实施例中计费触发设备(或SMF)侧的步骤说明，如步骤430、602、607、610、652、655、702-1和702-2等。
-接收模块1002，用于从所述计费处理设备接收第一计费响应消息，所述第一计费响应消息包含计费处理结果，所述计费处理结果为所述计费处理设备基于所述冗余传输信息进行计费处理的结果，具体执行过程参见上述实施例中计费触发设备(或SMF)侧的步骤说明，如步骤450、605、609、612、655、659、662、704-1和704-2等。
图9所示计费处理设备、图10所示计费触发设备是以功能模块的形式来呈现。这里的“模块”可以指特定应用集成电路(application-specific integrated circuit，ASIC)，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到这些设备也可以采用图8所示的形式。例如接收模块901、发送模块1001、发送模块902、接收模块1002都可以通过图8中的处理器801和存储器802来实现。例如，接收模块901接收计费请求消息的功能、发送模块1001发送计费请求消息的功能，均可以通过由处理器801来执行存储器802中存储的代码来实现。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、计算机软件或者二者的结合来实现，为了清楚地说明硬件和软件的可互换性，在上述说明中已经按照功能一般性地描述了各示例的组成及步骤。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本领域普通技术人员可以清楚地了解到，为了描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另外，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过 一些接口、装置或单元的间接耦合或通信连接，也可以是电的，机械的或其它的形式连接。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本申请实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以是两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分，或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器、随机存取存储器、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到各种等效的修改或替换，这些修改或替换都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以权利要求的保护范围为准。

Claims (50)

  1. 一种计费处理的方法，应用于计费触发设备，所述计费触发设备与计费处理设备通信，其特征在于，包括：
    所述计费触发设备向所述计费处理设备发送第一计费请求消息，所述第一计费请求消息包含冗余传输信息，所述冗余传输信息是指为数据连接会话中的第一数据连接业务使用的冗余传输的相关信息；
    所述计费触发设备从所述计费处理设备接收第一计费响应消息，所述第一计费响应消息包含计费处理结果，所述计费处理结果为所述计费处理设备基于所述冗余传输信息进行计费处理的结果。
  2. 如权利要求1所述的方法，其特征在于，所述冗余传输信息指示所述第一数据连接业务的传输为冗余传输。
  3. 如权利要求1或2所述的方法，其特征在于，所述冗余传输信息还指示所述第一数据连接业务的冗余传输方式，所述冗余传输方式为以下任意一项：会话冗余、隧道冗余或传输层冗余。
  4. 如权利要求1-3任一所述的方法，其特征在于，所述第一数据连接业务的冗余传输方式为会话冗余，所述冗余传输信息还指示所述数据连接会话为主数据连接会话或从数据连接会话，或者，所述冗余传输信息还包含与所述数据连接会话互为冗余的数据连接会话的信息。
  5. 如权利要求1-4任一所述的方法，其特征在于：
    所述计费处理结果包含所述计费处理设备为所述第一数据连接业务授予的配额和对应的第一处理指示信息，所述第一处理指示信息指示所述计费触发设备为所述配额对应的使用量设置冗余标记；
    所述方法还包括：所述计费触发设备向所述计费处理设备发送第二计费请求消息，所述第二计费请求消息包含所述配额对应的使用量和所述冗余标记；
    所述冗余标记指示所述使用量为冗余传输的数据连接业务的使用量。
  6. 如权利要求1-4任一所述的方法，其特征在于：
    所述计费处理结果包含第二处理指示信息，所述第二处理指示信息指示为所述数据连接会话中的第二数据连接业务执行：包含冗余的使用量处理或者去除冗余的使用量处理。
  7. 如权利要求6所述的方法，其特征在于：
    所述第一数据连接业务的冗余传输方式为会话冗余或者传输层冗余，所述第二数据连接业务与所述第一数据连接业务中的费率组对应、与所述第一数据连接业务中的QoS流对应或者与所述第一数据连接业务对应的数据连接会话对应；
    或者，
    所述第一数据连接业务的冗余传输方式为隧道冗余，所述第二数据连接业务与所述第一数据连接业务中的费率组对应、或者与所述第一数据连接业务对应的QoS流对应。
  8. 如权利要求6或7所述的方法，其特征在于：
    所述第一数据连接业务的冗余传输方式为会话冗余、隧道冗余或传输层冗余，所述为所述第二数据连接业务执行去除冗余的使用量处理，包括：将所述数据连接会话中所述第二数据连接业务的冗余传输的流量的一半作为所述第二数据连接业务的使用量；所述为所述第二 数据连接业务执行包含冗余的使用量处理，包括：将所述数据连接会话中所述第二数据连接业务的冗余传输的流量作为所述第二数据连接业务的使用量；
    或者，
    所述第一数据连接业务的冗余传输方式为隧道冗余或者传输层冗余，所述为所述第二数据连接业务执行去除冗余的使用量处理，包括：将在用户面数据网关与数据网络之间传输的所述第二数据连接业务的流量作为所述第二数据连接业务的使用量，所述为所述第二数据连接业务执行包含冗余的使用量处理，包括：将在用户面数据网关与无线接入网络设备之间传输的所述第二数据连接业务的流量作为所述第二数据连接业务的使用量；
    或者，
    所述第一数据连接业务的冗余传输方式为隧道冗余或传输层冗余，所述为所述第二数据连接业务执行去除冗余的使用量处理，包括：将通过互为冗余的两条传输通路之一传输的所述第二数据连接业务的流量作为所述第二数据连接业务的使用量，所述为所述第二数据连接业务执行包含冗余的使用量处理，包括：将通过互为冗余的两条传输通路传输的所述第二数据连接业务的流量作为所述第二数据连接业务的使用量。
  9. 如权利要求8所述的方法，其特征在于：
    所述第二数据连接业务为在线计费业务，所述为所述第二数据连接业务执行包含冗余的使用量处理或去除冗余的使用量处理，还包括：用所述第二数据连接业务的使用量消费所述计费处理设备授予的配额。
  10. 如权利要求1-9任一所述的方法，其特征在于，所述方法还包括：
    所述计费触发设备向所述计费处理设备发送所述第一数据连接业务中的费率组或QoS流对应的使用量及相应的使用量描述信息，所述使用量描述信息指示所述使用量为以下任意一项：
    未执行去除冗余的使用量处理的流量，
    执行去除冗余的使用量处理后的流量，
    用户面数据网关与无线接入网络设备之间传输的流量，
    用户面数据网关与数据网络之间传输的流量。
  11. 如权利要求1-10任一所述的方法，其特征在于，所述方法还包括：
    所述计费触发设备向所述计费处理设备发送所述第一数据连接业务的传输时延。
  12. 如权利要求4所述的方法，其特征在于：
    所述计费处理结果包含不计费指示信息，所述不计费指示信息指示所述计费处理设备确定所述数据连接会话为从数据连接会话而不对其执行计费处理，或者确定对与所述数据连接会话互为冗余的数据连接会话执行计费而不对所述数据连接会话执行计费处理。
  13. 一种计费处理的方法，应用于计费处理设备，所述计费处理设备与计费触发设备通信，其特征在于，包括：
    所述计费处理设备从所述计费触发设备接收第一计费请求消息，所述第一计费请求消息包含冗余传输信息，所述冗余传输信息是指为数据连接会话中的第一数据连接业务使用的冗余传输的相关信息；
    所述计费处理设备基于所述冗余传输信息进行计费处理，得到计费处理结果，且向所述计费触发设备发送第一计费响应消息，所述第一计费响应消息包含所述计费处理结果。
  14. 如权利要求13所述的方法，其特征在于，所述冗余传输信息指示所述第一数据连接业务的传输为冗余传输。
  15. 如权利要求13或14所述的方法，其特征在于，所述冗余传输信息还指示所述第一数据连接业务的冗余传输方式，所述冗余传输方式为以下任意一项：会话冗余、隧道冗余或传输层冗余。
  16. 如权利要求13-15任一所述的方法，其特征在于，所述第一数据连接业务的冗余传输方式为会话冗余，所述冗余传输信息还指示所述数据连接会话为主数据连接会话或从数据连接会话，或者，所述冗余传输信息还包含与所述数据连接会话互为冗余的数据连接会话的信息。
  17. 如权利要求13-16任一所述的方法，其特征在于：
    所述计费处理设备基于所述冗余传输信息进行计费处理，包括：基于所述冗余传输信息确定对所述第一数据连接业务的使用量执行去除冗余的计费处理或者包含冗余的计费处理，并为所述第一数据连接业务授予配额；
    所述计费处理结果包含所述配额；
    所述方法还包括：所述计费处理设备从所述计费触发设备接收第二计费请求消息，所述第二计费请求消息包含所述配额对应的使用量；所述计费处理设备对所述配额的使用量执行去除冗余的计费处理或者包含冗余的计费处理。
  18. 如权17，其特征在于，所述方法还包括：
    所述计费处理设备为所述配额生成第一处理指示信息，所述第一处理指示信息指示所述计费触发设备为所述配额对应的使用量设置冗余标记；
    所述计费处理结果还包含所述第一处理指示信息；
    所述第二计费请求消息还包含所述冗余标记；
    所述计费处理设备对所述配额的使用量执行去除冗余的计费处理或者包含冗余的计费处理，包括：所述计费处理设备基于所述冗余标记对所述配额的使用量执行去除冗余的计费处理或者包含冗余的计费处理；
    所述冗余标记指示所述使用量为冗余传输的数据连接业务的使用量。
  19. 如权利要求13-16，其特征在于：
    所述计费处理设备基于所述冗余传输信息进行计费处理，包括：所述计费处理设备基于所述冗余传输信息生成第二处理指示信息；
    所述计费处理结果包含所述第二处理指示信息；
    其中，所述第二处理指示信息指示所述计费触发设备为所述数据连接会话中的第二数据连接业务执行：包含冗余的使用量处理或者去除冗余的使用量处理。
  20. 如权利要求19所述的方法，其特征在于：
    所述冗余传输信息指示所述第一数据连接业务的冗余传输方式为会话冗余或者传输层冗余，所述第二数据连接业务与所述第一数据连接业务中的费率组对应、与所述第一数据连接业务中的QoS流对应或与所述第一数据连接业务对应的数据连接会话对应；
    或者，
    所述冗余传输信息指示所述第一数据连接业务的冗余传输方式为隧道冗余，所述第二数据连接业务与所述第一数据连接业务中的费率组对应、或者与所述第一数据连接业务对应的QoS流对应。
  21. 如权利要求13-20任一所述的方法，其特征在于，所述方法还包括：
    所述计费处理设备从所述计费触发设备接收所述第一数据连接业务中的费率组或QoS流对应的使用量及相应的使用量描述信息，所述使用量描述信息指示所述使用量为如下任意一 项：
    未执行去除冗余的使用量处理的流量，
    执行去除冗余的使用量处理后的流量，
    用户面数据网关与无线接入网络设备之间传输的流量，
    用户面数据网关与数据网络之间传输的流量。
  22. 如权利要求13-21任一所述的方法，其特征在于：
    所述方法还包括：所述计费处理设备从所述计费触发设备接收所述第一数据连接业务的传输时延；
    所述计费处理设备基于所述冗余传输信息进行计费处理，包括：所述计费处理设备根据所述冗余传输信息和所述传输时延进行计费处理。
  23. 如权利要求22所述的方法，其特征在于，所述方法还包括：
    所述计费处理设备将所述第一数据连接业务的信息写入话单，所述第一数据连接业务的信息包括以下任意一项：冗余传输信息、使用量描述信息或传输时延。
  24. 如权利要求16所述的方法，其特征在于：
    所述计费处理设备基于所述冗余传输信息进行计费处理，包括：所述计费处理设备确定不对所述连接会话执行计费处理；所述计费处理设备生成不计费指示信息，所述不计费指示信息指示所述计费处理设备确定所述数据连接会话为从数据连接会话而不对其执行计费处理，或者确定与所述数据连接会话互为冗余的数据连接会话执行计费而不对其执行计费处理；
    所述计费处理结果包含所述不计费指示信息。
  25. 一种计费处理系统，包括：计费触发设备和计费处理设备，所述计费触发设备与所述计费处理设备通信，其特征在于：
    所述计费触发设备用于：向所述计费处理设备发送第一计费请求消息，所述第一计费请求消息包含冗余传输信息，所述冗余传输信息是指为数据连接会话中的第一数据连接业务使用的冗余传输的相关信息；
    所述计费处理设备用于：基于所述冗余传输信息进行计费处理，得到计费处理结果，且向所述计费触发设备发送第一计费响应消息，所述第一计费响应消息包含所述计费处理结果。
  26. 如权利要求25所述的计费处理系统，其特征在于，
    所述计费处理设备还用于：为所述配额生成第一处理指示信息，所述第一处理指示信息指示所述计费触发设备为所述配额对应的使用量设置冗余标记；使所述计费处理结果还包含所述第一处理指示信息；
    所述计费触发设备还用于：在所述第二计费请求消息中包含所述冗余标记；
    其中，所述冗余标记指示所述使用量为冗余传输的数据连接业务的使用量。
  27. 如权利要求25所述的计费处理系统，其特征在于：
    所述计费处理设备还用于：基于所述冗余传输信息生成第二处理指示信息；使所述计费处理结果包含所述第二处理指示信息；
    所述计费触发设备还用于：根据所述第二处理指示信息，为所述数据连接会话中的第二数据连接业务执行：包含冗余的使用量处理或者去除冗余的使用量处理。
  28. 如权利要求25所述的计费处理系统，其特征在于：
    所述冗余传输信息还指示所述数据连接会话为从数据连接会话或者所述冗余传输信息包含与所述数据连接会话互为冗余的数据连接会话的信息；
    所述计费处理设备还用于：确定不对所述数据连接会话执行计费处理，生成不计费指示信息，且使所述计费处理结果包含所述不计费指示信息，所述不计费指示信息指示所述计费处理设备确定所述数据连接会话为从数据连接会话而不对其执行计费处理，或者确定对与所述数据连接会话互为冗余的数据连接会话执行计费而不对所述数据连接会话执行计费处理。
  29. 一种计费触发设备，所述计费触发设备与计费处理设备通信，包括发送模块和接收模块，其特征在于：
    所述发送模块用于：向所述计费处理设备发送第一计费请求消息，所述第一计费请求消息包含冗余传输信息，所述冗余传输信息是指为数据连接会话中的第一数据连接业务使用的冗余传输的相关信息；
    所述接收模块用于：从所述计费处理设备接收第一计费响应消息，所述第一计费响应消息包含计费处理结果，所述计费处理结果为所述计费处理设备基于所述冗余传输信息进行计费处理的结果。
  30. 如权利要求29所述的计费触发设备，其特征在于，所述冗余传输信息指示所述第一数据连接业务的传输为冗余传输。
  31. 如权利要求29或30所述的计费触发设备，其特征在于，所述冗余传输信息还指示所述第一数据连接业务的冗余传输方式，所述冗余传输方式为以下任意一项：会话冗余、隧道冗余或传输层冗余。
  32. 如权利要求29-31任一所述的计费触发设备，其特征在于，所述第一数据连接业务的冗余传输方式为会话冗余，所述冗余传输信息还指示所述数据连接会话为主数据连接会话或从数据连接会话，或者，所述冗余传输信息还包含与所述数据连接会话互为冗余的数据连接会话的信息。
  33. 如权利要求29-32任一所述的计费触发设备，其特征在于：
    所述计费处理结果包含所述计费处理设备为所述第一数据连接业务授予的配额和对应的第一处理指示信息，所述第一处理指示信息指示所述计费触发设备为所述配额对应的使用量设置冗余标记；
    所述发送模块还用于：向所述计费处理设备发送第二计费请求消息，所述第二计费请求消息包含所述配额对应的使用量和所述冗余标记；
    所述冗余标记指示所述使用量为冗余传输的数据连接业务的使用量。
  34. 如权利要求29-33任一所述的计费触发设备，其特征在于：
    所述计费处理结果包含第二处理指示信息，所述第二处理指示信息指示为所述数据连接会话中的第二数据连接业务执行：包含冗余的使用量处理或者去除冗余的使用量处理。
  35. 如权利要求29-34任一所述的计费触发设备，其特征在于：
    所述发送模块还用于向所述计费处理设备发送所述第一数据连接业务中的费率组或QoS流对应的使用量及相应的使用量描述信息，所述使用量描述信息指示所述使用量为以下任意一项：
    未执行去除冗余的使用量处理的流量，
    执行去除冗余的使用量处理后的流量，
    用户面数据网关与无线接入网络设备之间传输的流量，
    用户面数据网关与数据网络之间传输的流量。
  36. 如权利要求29-35任一所述的计费触发设备，其特征在于：
    所述发送模块还用于向所述计费处理设备发送所述第一数据连接业务的传输时延。
  37. 如权利要求32所述的计费触发设备，其特征在于：
    所述计费处理结果包含不计费指示信息，所述不计费指示信息指示所述计费处理设备确定所述数据连接会话为从数据连接会话而不对其执行计费处理，或者确定对与所述数据连接会话互为冗余的数据连接会话执行计费而不对所述数据连接会话执行计费处理。
  38. 一种计费处理设备，所述计费处理设备与计费触发设备通信，包括接收模块和发送模块，其特征在于：
    所述接收模块用于：从所述计费触发设备接收第一计费请求消息，所述第一计费请求消息包含冗余传输信息，所述冗余传输信息是指为数据连接会话中的第一数据连接业务使用的冗余传输的相关信息；
    所述发送模块用于：基于所述冗余传输信息进行计费处理，得到计费处理结果，且向所述计费触发设备发送第一计费响应消息，所述第一计费响应消息包含所述计费处理结果。
  39. 如权利要求38所述的计费处理设备，其特征在于，所述冗余传输信息指示所述第一数据连接业务的传输为冗余传输。
  40. 如权利要求38或39所述的计费处理设备，其特征在于，所述冗余传输信息还指示所述第一数据连接业务的冗余传输方式，所述冗余传输方式为以下任意一项：会话冗余、隧道冗余或传输层冗余。
  41. 如权利要求38-40任一所述的计费处理设备，其特征在于，所述第一数据连接业务的冗余传输方式为会话冗余，所述冗余传输信息还指示所述数据连接会话为主数据连接会话或从数据连接会话，或者，所述冗余传输信息还包含与所述数据连接会话互为冗余的数据连接会话的信息。
  42. 如权利要求38-41任一所述的计费处理设备，其特征在于：
    所述发送模块还用于：基于所述冗余传输信息确定对所述第一数据连接业务的使用量执行去除冗余的计费处理或者包含冗余的计费处理，并为所述第一数据连接业务授予配额；
    所述计费处理结果包含所述配额；
    所述接收模块还用于：从所述计费触发设备接收第二计费请求消息，所述第二计费请求消息包含所述配额对应的使用量；所述计费处理设备对所述配额的使用量执行去除冗余的计费处理或者包含冗余的计费处理。
  43. 如权利要求38-41任一所述的计费处理设备，其特征在于：
    所述发送模块还用于：基于所述冗余传输信息生成第二处理指示信息；
    所述计费处理结果包含所述第二处理指示信息；
    其中，所述第二处理指示信息指示所述计费触发设备为所述数据连接会话中的第二数据连接业务执行：包含冗余的使用量处理或者去除冗余的使用量处理。
  44. 如权利要求38-43任一所述的计费处理设备，其特征在于：
    所述接收模块还用于：从所述计费触发设备接收所述第一数据连接业务中的费率组或QoS流对应的使用量及相应的使用量描述信息，所述使用量描述信息指示所述使用量为如下任意一项：
    未执行去除冗余的使用量处理的流量，
    执行去除冗余的使用量处理后的流量，
    用户面数据网关与无线接入网络设备之间传输的流量，
    用户面数据网关与数据网络之间传输的流量。
  45. 如权利要求38-44任一所述的计费处理设备，其特征在于：
    所述接收模块还用于：从所述计费触发设备接收所述第一数据连接业务的传输时延；
    所述发送模块还用于：根据所述冗余传输信息和所述传输时延进行计费处理。
  46. 如权利要求45所述的计费处理设备，其特征在于：
    所述发送模块还用于：将所述第一数据连接业务的信息写入话单，所述第一数据连接业务的信息包括以下任意一项：冗余传输信息、使用量描述信息或传输时延。
  47. 如权利要求41所述的计费处理设备，其特征在于：
    所述发送模块还用于：确定不对所述连接会话执行计费处理；生成不计费指示信息，所述不计费指示信息指示所述计费处理设备确定所述数据连接会话为从数据连接会话而不对其执行计费处理，或者确定与所述数据连接会话互为冗余的数据连接会话执行计费而不对其执行计费处理；
    所述计费处理结果包含所述不计费指示信息。
  48. 一种计费触发设备，包括处理器和存储器，其特征在于：
    所述存储器，用于存储程序指令；
    所述处理器，用于调用并执行所述存储器中存储的程序指令，以使所述计费触发设备执行权利要求1-12任一所述的计费处理的方法。
  49. 一种计费处理设备，包括处理器和存储器，其特征在于：
    所述存储器，用于存储程序指令；
    所述处理器，用于调用并执行所述存储器中存储的程序指令，以使所述计费处理设备执行权利要求13-24任一所述的计费处理的方法。
  50. 一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得所述计算机执行权利要求1-24任一项所述的计费处理的方法。
PCT/CN2021/097739 2020-08-04 2021-06-01 一种计费处理的方法、系统及相关设备 WO2022028076A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
CA3190682A CA3190682A1 (en) 2020-08-04 2021-06-01 Charging processing method system and related device
AU2021321730A AU2021321730A1 (en) 2020-08-04 2021-06-01 Charging processing method, system, and related device
EP21853317.2A EP4187942A4 (en) 2020-08-04 2021-06-01 BILLING PROCESSING METHOD, SYSTEM, AND ASSOCIATED DEVICE
JP2023507740A JP2023536967A (ja) 2020-08-04 2021-06-01 課金処理方法およびシステム、および関連デバイス
US18/164,459 US20230187946A1 (en) 2020-08-04 2023-02-03 Charging processing method and system and related device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010774810.8A CN114071390A (zh) 2020-08-04 2020-08-04 一种计费处理的方法、系统及相关设备
CN202010774810.8 2020-08-04

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/164,459 Continuation US20230187946A1 (en) 2020-08-04 2023-02-03 Charging processing method and system and related device

Publications (1)

Publication Number Publication Date
WO2022028076A1 true WO2022028076A1 (zh) 2022-02-10

Family

ID=80119889

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/097739 WO2022028076A1 (zh) 2020-08-04 2021-06-01 一种计费处理的方法、系统及相关设备

Country Status (7)

Country Link
US (1) US20230187946A1 (zh)
EP (1) EP4187942A4 (zh)
JP (1) JP2023536967A (zh)
CN (1) CN114071390A (zh)
AU (1) AU2021321730A1 (zh)
CA (1) CA3190682A1 (zh)
WO (1) WO2022028076A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023237035A1 (en) * 2022-06-10 2023-12-14 Telefonaktiebolaget Lm Ericsson (Publ) Repetitive data optimization in n40 interface

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105247903A (zh) * 2013-05-07 2016-01-13 诺基亚技术有限公司 用于通过多个网络节点进行动态计费的方法和装置
CN105659690A (zh) * 2013-10-21 2016-06-08 Lg电子株式会社 在双连接中发送上行链路数据的方法及其设备
CN105992181A (zh) * 2015-01-30 2016-10-05 上海贝尔股份有限公司 在双连接系统中确定计费策略的方法和装置
US9553913B2 (en) * 2014-05-30 2017-01-24 Apple Inc. Seamless video pipeline transition between WiFi and cellular connections for real-time applications on mobile devices
CN111211912A (zh) * 2018-04-28 2020-05-29 华为技术有限公司 计费的方法、装置及系统

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110278581B (zh) * 2018-03-16 2021-09-28 中兴通讯股份有限公司 一种无线接入网流量报告方法、装置和系统、存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105247903A (zh) * 2013-05-07 2016-01-13 诺基亚技术有限公司 用于通过多个网络节点进行动态计费的方法和装置
CN105659690A (zh) * 2013-10-21 2016-06-08 Lg电子株式会社 在双连接中发送上行链路数据的方法及其设备
US9553913B2 (en) * 2014-05-30 2017-01-24 Apple Inc. Seamless video pipeline transition between WiFi and cellular connections for real-time applications on mobile devices
CN105992181A (zh) * 2015-01-30 2016-10-05 上海贝尔股份有限公司 在双连接系统中确定计费策略的方法和装置
CN111211912A (zh) * 2018-04-28 2020-05-29 华为技术有限公司 计费的方法、装置及系统

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "Add description of solution 4 in 23.725 to 23.501", 3GPP DRAFT; S2-1901370 WAS S2-1901228 WAS S2-1900290 TS 23.501 ADD DESCRIPTION OF SOLUTION 4 IN 23.725 TO 23.501 V3, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRAN, vol. SA WG2, no. Kochi, India; 20190121 - 20190125, 25 January 2019 (2019-01-25), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051597181 *
HUAWEI: "Add Highly reliable URLLC services Charging", 3GPP DRAFT; S5-205085, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG5, no. e-meeting; 20201012 - 20201021, 2 October 2020 (2020-10-02), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051938845 *
See also references of EP4187942A4 *
ZTE: "Discussion on Secondary RAT data volume reporting", 3GPP DRAFT; R3-182789 DISCUSSION ON SECONDARY RAT DATA VOLUME REPORTING, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. Busan, South Korea; 20180521 - 20180525, 20 May 2018 (2018-05-20), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051445289 *

Also Published As

Publication number Publication date
US20230187946A1 (en) 2023-06-15
CN114071390A (zh) 2022-02-18
EP4187942A1 (en) 2023-05-31
JP2023536967A (ja) 2023-08-30
CA3190682A1 (en) 2022-02-10
AU2021321730A1 (en) 2023-03-16
EP4187942A4 (en) 2023-11-29

Similar Documents

Publication Publication Date Title
US10924294B2 (en) Evolved multimedia broadcast/multicast service (EMBMS) system and EMBMS system management method
EP3968664A1 (en) Charging method and device
EP3883180B1 (en) Charging method, apparatus, computer program and system.
CN110557724A (zh) 一种多播业务的数据传输方法以及相关设备
EP2509256B1 (en) Flow charging method and apparatus
WO2017219905A1 (zh) 一种计费方法、装置、系统和存储介质
WO2019095726A1 (zh) 一种融合计费的方法和设备
US20110320544A1 (en) Diameter session audits
WO2021223745A1 (zh) 组播业务切换的方法和装置
WO2007082446A1 (fr) Procede et systeme de taxation hors ligne
WO2022028076A1 (zh) 一种计费处理的方法、系统及相关设备
CN109495857A (zh) 计费方法、移动边缘计算服务器、计费系统及策略控制规则网元
KR20090130409A (ko) 응용 계층 멀티캐스트 네트워크에서 미디어 데이터를 취득하는 방법 및 시스템
US8493878B2 (en) Flexible parameter cache for machine type connections
KR20160068448A (ko) 무선 통신 시스템에서 전송 계층의 속도를 제어하기 위한 장치 및 방법
WO2019042218A1 (zh) 计费实现系统、计费实现方法及计费管理功能实体
US11223968B2 (en) Method, apparatus and system for reporting radio access network traffic
EP4277309A1 (en) Method and system for performing billing processing on mobile local area network service, and related device
WO2019179370A1 (zh) 数据传输通道地址分配方法、关联方法、装置及存储介质
WO2023051782A1 (zh) 管理漫游计费配置参数的方法、系统及相关设备
WO2024067475A1 (zh) 数据传输方法和通信装置
WO2023143255A1 (zh) 一种通信方法及装置
WO2024111549A1 (ja) 通信制御方法、移動通信システム、セッション管理装置、ユーザプレーン装置、及びネットワークデータ分析装置
WO2022160210A1 (zh) 业务数据流的传输方法、通信装置及通信系统
JP2024030173A (ja) 通信制御方法、通信制御プログラムおよび通信制御装置

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: 21853317

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2023507740

Country of ref document: JP

Kind code of ref document: A

Ref document number: 3190682

Country of ref document: CA

WWE Wipo information: entry into national phase

Ref document number: 2021853317

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2021853317

Country of ref document: EP

Effective date: 20230223

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2021321730

Country of ref document: AU

Date of ref document: 20210601

Kind code of ref document: A