WO2022262608A1 - 一种计费方法、用户设备及网络侧设备 - Google Patents

一种计费方法、用户设备及网络侧设备 Download PDF

Info

Publication number
WO2022262608A1
WO2022262608A1 PCT/CN2022/097142 CN2022097142W WO2022262608A1 WO 2022262608 A1 WO2022262608 A1 WO 2022262608A1 CN 2022097142 W CN2022097142 W CN 2022097142W WO 2022262608 A1 WO2022262608 A1 WO 2022262608A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
charging
qos flow
charging information
user equipment
Prior art date
Application number
PCT/CN2022/097142
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 EP22824088.3A priority Critical patent/EP4358552A4/en
Priority to US18/571,193 priority patent/US20240283870A1/en
Publication of WO2022262608A1 publication Critical patent/WO2022262608A1/zh

Links

Images

Classifications

    • 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
    • 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
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing
    • 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
    • H04L12/1403—Architecture for metering, charging or billing
    • 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
    • H04L12/1403—Architecture for metering, charging or billing
    • H04L12/1407—Policy-and-charging control [PCC] architecture
    • 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/61—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP based on the service used
    • 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/66—Policy and 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/80—Rating or billing plans; Tariff determination aspects
    • H04M15/8033—Rating or billing plans; Tariff determination aspects location-dependent, e.g. business or home
    • 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/93—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP using near field or similar technologies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]

Definitions

  • the present application relates to the technical field of communications, and in particular to a charging method, user equipment and network side equipment.
  • Proximity based Services refers to a wireless communication technology that can use Proximity Based Services for direct connection and communication when user equipment (User Equipment, UE) are close to each other. It can allow new air interface (New Radio, NR)/Long Term Evolution (Long Term Evolution, LTE) UEs to use cell wireless resources to communicate directly under the control of the cellular communication system without going through the cellular network.
  • New Radio, NR New Radio
  • LTE Long Term Evolution
  • 5G fifth-generation mobile communication technology
  • 5G Fifth-generation mobile communication technology
  • SBA Service Based Architecture
  • CCS Converged Charging System
  • the billing and offline billing functions are integrated, and a service-based architecture is adopted to provide a unified interface to the outside world.
  • the purpose of the present application is to provide a charging method, user equipment and network side equipment, so as to solve the charging problem in the proximity service scenario.
  • An embodiment of the present application provides a charging method, including:
  • the user equipment obtains the charging information of the quality of service QoS flow, and the charging information is generated based on the user equipment providing ProSe;
  • the charging information includes: flow information of the QoS flow.
  • the user equipment obtains the charging information of the quality of service QoS flow, including:
  • the charging trigger event includes at least one or more of the following:
  • a time condition of the ProSe link where the time condition of the ProSe link is used to indicate that a charging event is triggered if a set time is met within the lifetime of the ProSe link;
  • the data volume condition of the ProSe link is used to indicate that if the set data volume is satisfied within the life cycle of the ProSe link, a charging event will be triggered;
  • the time condition of the QoS flow is used to indicate that if the set time is met within the life cycle of the QoS flow, a charging event will be triggered;
  • the data volume condition of the QoS flow is used to indicate that if the set data volume is satisfied within the life cycle of the QoS flow, a charging event will be triggered.
  • the configuration information includes at least one or more of the following:
  • First indication information where the first indication information is used to indicate whether to report charging information based on the QoS flow
  • the second indication information is used to indicate whether to report the data volume of the received data
  • Third indication information where the third indication information is used to indicate whether to report the data volume of the sent data.
  • the method also includes:
  • the sending the charging information to the network side device includes:
  • the usage information report is sent to the network side device according to the reporting period in the configuration information.
  • the sending the charging information to the network side device includes:
  • charging trigger function Charging Trigger Function, CTF
  • charging execution function Charging Enablement Function, CEF
  • the charging information is used by the CHF to charge the generated ProSe.
  • sending the charging information to the CEF of the network side device specifically includes:
  • NF Network Function
  • the flow information of the QoS flow includes at least one or more of the following:
  • the charging information further includes link information associated with the QoS flow, where the link information includes at least one or more of the following:
  • IP Internet Protocol
  • the IP multicast address of the proximity service group
  • the link ID of the ProSe link is The link ID of the ProSe link.
  • An embodiment of the present application provides a charging method, including:
  • the network side device acquires the charging information of the QoS flow sent by the user equipment, where the charging information is generated based on the proximity service provided by the user equipment;
  • the network side device sends the charging information to a charging function (Charging Function, CHF);
  • the charging information includes: flow information of the QoS flow.
  • the method before obtaining the charging information of the QoS flow sent by the user equipment, the method further includes:
  • the configuration information includes at least one or more of the following:
  • First indication information where the first indication information is used to indicate whether to report charging information based on the QoS flow
  • the second indication information is used to indicate whether to report the data volume of the received data
  • Third indication information where the third indication information is used to indicate whether to report the data volume of the sent data.
  • the acquiring the charging information of the QoS flow sent by the user equipment includes:
  • the acquiring the charging information sent by the user equipment includes:
  • the sending the charging information to the charging function CHF includes:
  • the charging information is used by the CHF to charge the generated ProSe.
  • receiving the charging information sent by the user equipment to the charging enforcement function CEF includes:
  • the flow information of the QoS flow includes at least one or more of the following:
  • the charging information further includes link information associated with the QoS flow, where the link information includes at least one or more of the following:
  • the IP multicast address of the proximity service group
  • the link ID of the ProSe link is The link ID of the ProSe link.
  • An embodiment of the present application provides a user equipment, including: a memory, a transceiver, and a processor:
  • the memory is used to store computer programs; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer programs in the memory and perform the following operations:
  • the transceiver is used to: send the charging information to the network side device;
  • the charging information includes: flow information of the QoS flow.
  • the processor is configured to read a computer program in the memory and perform the following operations:
  • the charging trigger event includes at least one or more of the following:
  • the time condition of the ProSe link is used to represent that if the set time is met within the lifetime of the ProSe link, a charging event will be triggered;
  • the data volume condition of the ProSe link is used to indicate that if the set data volume is satisfied within the life cycle of the ProSe link, a charging event will be triggered;
  • the time condition of the QoS flow is used to indicate that if the set time is met within the life cycle of the QoS flow, a charging event will be triggered;
  • the data volume condition of the QoS flow is used to indicate that if the set data volume is satisfied within the life cycle of the QoS flow, a charging event will be triggered.
  • the configuration information includes at least one or more of the following:
  • First indication information where the first indication information is used to indicate whether to report charging information based on the QoS flow
  • the second indication information is used to indicate whether to report the data volume of the received data
  • Third indication information where the third indication information is used to indicate whether to report the data volume of the sent data.
  • the processor is also configured to read a computer program in the memory and perform the following operations:
  • the transceiver sends the billing information to the network side device, including:
  • the usage information report is sent to the network side device according to the reporting period in the configuration information.
  • the transceiver sends the charging information to the network side device, including:
  • the charging information is used by the CHF to charge the generated ProSe.
  • the transceiver sends the charging information to the CEF of the network side device, specifically including:
  • the flow information of the QoS flow includes at least one of the following:
  • the charging information further includes link information associated with the QoS flow, where the link information includes at least one or more of the following:
  • the IP multicast address of the proximity service group
  • the link ID of the ProSe link is The link ID of the ProSe link.
  • An embodiment of the present application provides a network side device, including: a memory, a transceiver, and a processor:
  • the memory is used to store computer programs; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer programs in the memory:
  • the transceiver is configured to perform the following operations: acquire charging information of the QoS flow sent by the user equipment, where the charging information is generated based on the proximity service provided by the user equipment;
  • the charging information includes: flow information of the QoS flow.
  • the processor is also configured to read a computer program in the memory and perform the following operations
  • the configuration information includes at least one or more of the following:
  • the first indication information is used to indicate whether to report charging information based on QoS flow;
  • the second indication information is used to indicate whether to report the data volume of the received data
  • Third indication information where the third indication information is used to indicate whether to report the data volume of the sent data.
  • the transceiver acquires the charging information of the QoS flow sent by the user equipment, including:
  • the transceiver acquires the charging information sent by the user equipment, it is specifically used for:
  • the transceiver sends the charging information to a charging function CHF, including:
  • the charging information is used by the CHF to charge the generated ProSe.
  • the transceiver receives the charging information sent by the user equipment to the charging enforcement function CEF, including:
  • the flow information of the QoS flow includes at least one or more of the following:
  • the charging information further includes link information associated with the QoS flow, where the link information includes at least one or more of the following:
  • the IP multicast address of the proximity service group
  • the link ID of the ProSe link is The link ID of the ProSe link.
  • An embodiment of the present application provides a billing device, including:
  • a first acquiring unit configured to acquire charging information of a quality of service QoS flow, where the charging information is generated based on the proximity service provided by the user equipment;
  • a first sending unit configured to send the charging information to the network side device
  • the charging information includes: flow information of the QoS flow.
  • the first acquiring unit is specifically configured to:
  • the charging trigger event includes at least one or more of the following:
  • a time condition of the ProSe link where the time condition of the ProSe link is used to indicate that a charging event is triggered if a set time is met within the lifetime of the ProSe link;
  • the data volume condition of the ProSe link is used to indicate that if the set data volume is satisfied within the life cycle of the ProSe link, a charging event will be triggered;
  • the time condition of the QoS flow is used to indicate that if the set time is met within the life cycle of the QoS flow, a charging event will be triggered;
  • the data volume condition of the QoS flow is used to indicate that if the set data volume is satisfied within the life cycle of the QoS flow, a charging event will be triggered.
  • the configuration information includes at least one or more of the following:
  • the first indication information is used to indicate whether to report charging information based on QoS flow;
  • the second indication information is used to indicate whether to report the data volume of the received data
  • Third indication information where the third indication information is used to indicate whether to report the data volume of the sent data.
  • the device also includes:
  • a report generating unit configured to generate a usage information report including the charging information according to the generation cycle of generating the usage information report included in the configuration information after the charging information is acquired;
  • the first sending unit is specifically configured to: send the usage information report to the network side device according to the reporting period in the configuration information.
  • the first sending unit includes:
  • a first sending subunit configured to send the charging information to a charging trigger function CTF or a charging enforcement function CEF of the network side device, and the CTF or the CEF forward the charging information to the CHF ;
  • the charging information is used by the CHF to charge the generated ProSe.
  • the first sending subunit is specifically configured to: send the charging information to the CEF of the network side device through a charging-related network function NF service.
  • the flow information of the QoS flow includes at least one or more of the following:
  • the charging information further includes link information associated with the QoS flow, where the link information includes at least one or more of the following:
  • the IP multicast address of the proximity service group
  • the link ID of the ProSe link is The link ID of the ProSe link.
  • An embodiment of the present application provides a billing device, including:
  • the second acquiring unit is configured to acquire charging information of the QoS flow sent by the user equipment, where the charging information is generated based on the proximity service provided by the user equipment;
  • a second sending unit configured to send the charging information to a charging function CHF;
  • the charging information includes: flow information of the QoS flow.
  • the shown device also includes:
  • a configuration unit configured to configure configuration information of charging information for the user equipment.
  • the configuration information includes at least one or more of the following:
  • First indication information where the first indication information is used to indicate whether to report charging information based on the QoS flow
  • the second indication information is used to indicate whether to report the data volume of the received data
  • Third indication information where the third indication information is used to indicate whether to report the data volume of the sent data.
  • the second acquiring unit is specifically configured to: acquire a usage information report sent by the user equipment according to a reporting period of charging information, where the usage information report includes the charging information.
  • the second acquisition unit includes:
  • the first receiving subunit is configured to receive the charging information sent by the user equipment to the charging trigger function CTF or the charging enforcement function CEF;
  • the second sending unit is specifically configured to: send the charging information to the CHF through the CTF or the CEF by using a charging function service Nchf interface;
  • the charging information is used by the CHF to charge the generated ProSe.
  • the first receiving subunit is specifically configured to: receive the charging information sent by the NF service to the CEF; wherein the charging information is sent by the user equipment to the NF service.
  • the flow information of the QoS flow includes at least one or more of the following:
  • the charging information further includes link information associated with the QoS flow, where the link information includes at least one or more of the following:
  • the IP multicast address of the proximity service group
  • the link ID of the ProSe link is The link ID of the ProSe link.
  • An embodiment of the present application provides a processor-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, the steps of the above charging method are implemented.
  • the UE obtains the charging information of the QoS flow in the proximity service scenario and reports it to the network side device, and the charging information of the QoS flow obtained by the UE in the proximity service scenario includes the flow information of the QoS flow, After reporting to the network side device in this way, the network side device reports the charging information to the CHF to complete the charging.
  • This solution can complete billing based on ProSe business data, which effectively improves the billing accuracy based on QoS flow billing in proximity service scenarios, and can meet various potential vertical business billing scenarios in ProSe.
  • Figure 1 shows one of the schematic diagrams of the ProSe 5G billing architecture based on the service interface
  • Figure 2 shows the second schematic diagram of the ProSe 5G billing architecture based on the service interface
  • Figure 3 shows one of the schematic diagrams of the 4th Generation mobile communication technology (the 4th Generation mobile communication technology, 4G) ProSe based on PC5 direct communication billing;
  • Figure 4 shows the second schematic diagram of the architecture of 4G ProSe based on PC5 direct communication billing
  • FIG. 5 shows a schematic diagram of the basic billing process of direct communication
  • FIG. 6 shows one of the schematic flow charts of the billing method in the embodiment of the present application.
  • FIG. 7 shows the second schematic flow diagram of the billing method in the embodiment of the present application.
  • FIG. 8 shows the third schematic flow diagram of the billing method in the embodiment of the present application.
  • FIG. 9 shows the fourth schematic flow diagram of the billing method in the embodiment of the present application.
  • FIG. 10 shows a schematic diagram of the L3 relay architecture of the embodiment of the present application.
  • FIG. 11 shows the fifth schematic flow diagram of the billing method in the embodiment of the present application.
  • FIG. 12 shows the sixth schematic flow diagram of the billing method in the embodiment of the present application.
  • FIG. 13 shows one of the structural schematic diagrams of the billing device in the embodiment of the present application.
  • FIG. 14 shows the second structural schematic diagram of the billing device according to the embodiment of the present application.
  • FIG. 15 shows a schematic structural diagram of a user equipment according to an embodiment of the present application.
  • FIG. 16 shows a schematic structural diagram of a network-side device according to an embodiment of the present application.
  • sequence numbers of the following processes do not mean the order of execution, and the execution order of each process should be determined by its functions and internal logic, and should not be implemented in this application.
  • the implementation of the examples constitutes no limitation.
  • the 5G converged billing system In addition to the traditional billing mode (traffic, duration, event, etc.), the 5G converged billing system also supports multi-dimensional billing, that is, traffic and other services are calculated according to uplink and downlink rates, delays, vertical industry applications, and specific services (ultra-high-definition).
  • a billing model for billing elements such as video and live streaming), equipment (tracking devices, sensors), etc.
  • the main charging methods include triggers based on Flow Based Charging (FBC) and triggers based on Quality of Service (QoS) flow charging (QoS flow Based Charging, QBC).
  • FBC Flow Based Charging
  • QoS Quality of Service
  • CTF Charging Trigger Function
  • AMC Accounting Metrics Collection
  • ADF Accounting Data Forwarding
  • the AMC on the UE sends the usage information report (Usage Information Report) message to the ADF on the network side through the PC3ch interface, and ProSe-related network functions (Network Function, NF), such as 5G Direct Discovery Name Management (Direct Discovery Name Management) Function, DDNMF), check the received usage information (usage information), if it contains valid direct discovery (Direct Discovery) or direct communication (Direct communication) usage data (usage data), then trigger the charging function (Charging Function, CHF) charging data request (Charging Data Request) message, and CHF generates billing information (Charging Data Record, CDR).
  • 5G functional modules and billing architecture are based on service-based interfaces.
  • ProSe Function the functions of the ProSe Function (ProSe Function) module of 4G are decomposed into the corresponding ProSe Service (ProSe Service).
  • PCF Policy Control Function
  • ProSe Direct Discovery the 5G DDNMF ProSe Direct Discovery
  • the CTF (AMC) of the UE communicates with the 5G DDNMF through the PC3ch interface, and the communication between the 5G DDNMF and the CCS through the Service-based interface exhibited by Charging Function (Nchf) interface.
  • CCS includes: CHF, charging gateway function (Charging Gateway Function, CGF), rating function (Rating Function, RF), account balance management function (Account Balance Management Function, ABMF); CGF through the Bx interface (CGF and hot Billing function (CDR transmission interface) communicates with the billing system (Billing Domain).
  • the network side also includes a Charging Enablement Function (CEF).
  • CEF can subscribe to related services as a consumer of network function service (NF Service), and collect billing information that may be required from different NF Service or management service (Management Service).
  • NF Service network function service
  • Management Service management service
  • 4G ProSe is based on the architecture and basic process of PC5 direct communication billing.
  • 3GPP Third Generation Partnership Projects
  • 3GPP Third Generation Partnership Projects
  • the proximity communication function receives the charging information reported by the UE's CTF (AMC) through the PC3ch interface, and reports the Charging Data Request message to the charging data function (Charging Data Function, CDF), the billing information CDR is generated by the CDF.
  • the billing information can be sent to the CGF through the Ga interface, and the CGF can be set separately or integrated in the billing system.
  • the CGF communicates with the billing system through the Bpr interface.
  • Step 1 UE1 sends a direct communication request to UE2;
  • Step 2 Authentication between UE1 and UE2 and establishment of a security association
  • Step 3 establishing direct communication between UE1 and UE2;
  • Step 4 UE1 sends a disconnection request to UE2;
  • Step 5 UE1 receives a disconnection response
  • Step 7 UE1 sends usage information reporting to ProSe Function
  • Step 8 ProSe Function sends charging data request (event) (Charging Data Request) (Event) to CDF;
  • Step 9 CDF generates billing information CDR
  • Step 10 CDF sends charging data response (Charging Data Response) to ProSe Function.
  • the ProSe charging information collected by UE1 in step 7 mainly includes link-level charging information related to ProSe (for example: UE1's Mobile Subscriber Identity (International Mobile Subscriber Identity) (International Mobile Subscriber Identity) Mobile Subscriber Identification, IMSI), access public land mobile network (Public Land Mobile Network, PLMN) identification, location, proximity service method, etc.).
  • link-level charging information related to ProSe for example: UE1's Mobile Subscriber Identity (International Mobile Subscriber Identity) (International Mobile Subscriber Identity) Mobile Subscriber Identification, IMSI), access public land mobile network (Public Land Mobile Network, PLMN) identification, location, proximity service method, etc.).
  • the ProSe 5G charging architecture based on the service interface, the 5G data connectivity charging (data connectivity charging) function, including the protocol data unit (Protocol Data Unit, PDU) session in the SMF, the service data flow and QoS flow in the PDU session .
  • PDU Protocol Data Unit
  • SMF is not responsible for ProSe direct communication, so according to the above process, SMF cannot obtain the charging information at the QoS flow level, which leads to the fact that for the related 5G charging architecture, SMF cannot support QoS flow level based
  • the billing of ProSe QoS flow is not accurate enough, so the billing method for ProSe QoS flow needs to be redesigned.
  • embodiments of the present application provide a charging method, user equipment, and network side equipment.
  • the embodiment of the present application provides a schematic flowchart of a charging method, which is applied to a user equipment, and specifically includes the following steps:
  • step 601 the user equipment obtains charging information of a QoS flow, where the charging information is generated based on the proximity service provided by the user equipment.
  • the proximity service includes direct communication services (for example: wireless network device-to-device (Device to Device, D2D) services; vehicle wireless communication technology (vehicle to everything, V2X) services, etc.), ProSe services including relays, etc.
  • D2D wireless network device-to-device
  • V2X vehicle wireless communication technology
  • ProSe services including relays, etc.
  • the UE can be pre-configured or configured through the network side device whether to report charging information based on the QoS flow.
  • the UE can function as a CTF (AMC) to collect the charging information locally generated by the UE.
  • AMC CTF
  • Step 602. Send the charging information to the network side device; wherein, the charging information includes: flow information of the QoS flow.
  • the charging information further includes link information associated with the QoS flow.
  • the UE After acquiring the charging information, the UE sends the charging information to the network side device.
  • the charging information may include the flow information of the QoS flow (such as: information about the PC5 QoS flow) and/or the link information corresponding to the QoS flow.
  • the UE may serve as a CTF (AMC) to report the charging information to the CTF (ADF) of the network side device through the Usage Information Report, and then the CTF (ADF) or CEF of the network side device passes the Nchf interface. Billing information is reported to CHF, and CHF generates billing bills.
  • AMC CTF
  • the UE may use the PC3ch interface to report the Usage Information Report (that is, the charging information) to the network side device, or may use a non-access stratum (Non-Access-Stratum, NAS) message to report the
  • the above-mentioned Usage Information Report (that is, the charging information) is reported to the network-side device, which is not limited here.
  • the UE acquires the charging information of the QoS flow and reports it to the network side device, and the network side device reports the charging information to the CHF to complete the charging.
  • This solution can be billed based on ProSe-based service traffic, and can meet billing scenarios of various potential vertical services in ProSe.
  • the acquiring the charging information of the QoS flow may include but not limited to the following methods:
  • Method 1 Obtain the charging information of the QoS flow based on the charging trigger event.
  • the charging trigger event may be a charging trigger event of ProSe charging.
  • the charging triggering event can be customized or preconfigured by the user equipment or configured by the network side equipment.
  • the UE collects the charging information of the local QoS flow based on the charging trigger event.
  • Method 2 According to the configuration information, the acquisition of the charging information of the QoS flow is triggered.
  • the configuration information may be pre-configured by the network side equipment to the user equipment, for example: provided by a management element (Management Element, ME); the configuration information may also be pre-configured by the user equipment, For example, write to Universal Integrated Circuit Card (UICC).
  • ME Management Element
  • UICC Universal Integrated Circuit Card
  • the UE can determine whether charging information needs to be collected, what type of charging information to collect, and whether charging information reporting conditions are met. When the charging information reporting condition is met, the UE reports the charging information to the network side device through the CTF (AMC). It should be noted that the configuration information may indicate whether charging information needs to be reported based on QoS flow through a new flag bit.
  • the configuration information may be provided in the following ways:
  • UICC Universal Integrated Circuit Card
  • the charging trigger event may include at least one or more of the following:
  • a) ProSe link establishment For example: a Layer-2 link (Layer-2 link) is established between two UEs providing ProSe, that is, the ProSe UE collects the charging information based on QoS flow charging when the Layer-2 link is established.
  • the collection of the charging information may end.
  • the PC5 QoS flow is established, that is, the ProSe UE collects the charging information based on the PC5 QoS flow charging when the PC5 QoS flow is established.
  • the collection of the charging information may end.
  • PC5 QoS parameters include but are not limited to: direct link service quality indicator (PC5 Quality of Service Indication, PQI), guaranteed flow bit rate (Guaranteed Flow Bit Rate, GFBR), maximum flow bit rate (Maximum Flow Bit Rate, MFBR), PC5LINK-Aggregate Maximum Bit Rate (Aggregate Maximum Bit Rate, AMBR), Range (Range). That is, when the PC5 QoS attribute parameter changes, the charging information based on PC5 QoS flow charging is collected.
  • PC5 Quality of Service Indication PC5 Quality of Service Indication, PQI
  • PQI PC5 Quality of Service Indication
  • GFBR Guarantee Flow Bit Rate
  • Maximum Flow Bit Rate Maximum Flow Bit Rate
  • AMBR Maximum Bit Rate
  • Range Range
  • the ProSe link is, for example, a Layer 2 link.
  • the time condition is, for example: data time failure (Expiry of data time).
  • the time condition of the ProSe link is, for example: the time limit of each Layer 2 link expires.
  • the time condition of the link may be 10 minutes after the link is established, which means that the acquisition of charging information is triggered 10 minutes after the establishment of the ProSe link, that is, the charging starts 10 minutes after the establishment of the link.
  • the ProSe link is, for example, a Layer 2 link.
  • the data volume condition is, for example: data volume failure (Expiry of data volume).
  • the data volume condition of the ProSe link is for example: the data volume limit of each Layer 2 link expires.
  • the data volume condition of the link may be that the data volume of the data transmitted on the link is 10M, which means that after the establishment of the adjacent link, the data volume of the data transmitted on the link reaches 10M, triggering the acquisition of charging information , that is, billing starts after the amount of data transmitted on the link reaches 10M.
  • a time condition of the QoS flow the time condition of the QoS flow is used to indicate that a charging event will be triggered if a set time is met within the lifetime of the QoS flow. That is, when the ProSe UE meets the time condition of the QoS flow, the charging information of the QoS flow is collected.
  • the time condition is for example: Expiry of data time.
  • the time condition of the QoS flow is, for example: the time limit of each QoS flow expires.
  • the data volume condition of the QoS flow which is used to indicate that a charging event will be triggered if the set data volume is satisfied within the lifetime of the QoS flow. That is, when the ProSe UE meets the data volume condition of the QoS flow, the charging information of the QoS flow is collected.
  • the data volume condition is, for example: Expiry of data volume.
  • the data volume condition of the QoS flow is, for example: the data volume limit of each QoS flow expires.
  • the charging trigger event includes multiple items in a) to g) above, at least two of the above items are included.
  • the configuration information may include at least one or more of the following:
  • reporting cycle of reporting charging information that is, the reporting cycle of the charging information of the user equipment reporting QoS flow
  • first indication information is used to indicate whether to report charging information based on the QoS flow
  • second indication information is used to indicate whether to report the data volume of the received data
  • Third indication information where the third indication information is used to indicate whether to report the data volume of the sent data.
  • the configuration information of the charging information based on the QoS flow may be configured by the network side device for the UE or pre-configured by the UE.
  • the configuration information may include one or more items above.
  • the configuration information may indicate related information content through a newly added flag bit.
  • the UE collects and reports the charging information according to the generation period of the usage information report generated by the user equipment; when the first indication information indicates that the UE reports the charging information based on the QoS flow, the UE reports the charging information to the network
  • the side device reports the charging information; when the second indication information indicates that the UE reports the data volume of the received data, the UE may report the charging information at the same time when reporting the data volume of the received data;
  • the UE may report the charging information at the same time when reporting the data volume of the sent data.
  • the user equipment collects the charging information of the QoS flow, and may refer to the configuration information. Taking the configuration information of the user equipment including the first indication information as an example, when the first indication information indicates that the user equipment reports charging information based on the QoS flow, the user equipment collects the charging information based on the charging trigger event charging information of the QoS flow, and sending the charging information to the network side device.
  • the QoS flow-based charging triggering level of the user equipment may be QoS flow-based triggering and/or link-based triggering.
  • the link-based trigger is, for example, a layer-2 link-related trigger on PC5.
  • the trigger related to the layer-2 link may refer to the change of the Layer-2 link triggering the charging based on the PC5 QoS flow, wherein, when the Layer-2 link changes, the QoS flow in the layer-2 link also changes.
  • the trigger based on the QoS flow is for example: the trigger related to the PC5 QoS flow in the layer-2 link, that is, the QoS flow change in the Layer-2 link triggers the charging based on the PC5 QoS flow, which can be a separate QoS flow change trigger The charging based on the PC5 QoS flow.
  • the user equipment when it sends the charging information to the network side device, it may send a usage information report including the charging information.
  • the method further includes:
  • the sending the charging information to the network side device includes: sending the usage information report to the network side device according to the reporting period in the configuration information.
  • the user equipment after the user equipment obtains the charging information, it generates a usage information report (Usage Information Report) based on the generation period of the usage information report in the configuration information, and reports it at a predetermined reporting period
  • the usage information report includes the billing information.
  • the sending the charging information to the network side device includes:
  • the charging information is used by the CHF to charge the generated ProSe. .
  • the user equipment can locally collect charging information through the CTF (AMC), and report the charging information to the CTF (ADF) of the network side device when the charging information reporting condition based on the QoS flow is satisfied;
  • the CTF (ADF) of the network side device then sends the charging information to the CHF, and the CHF generates a charging bill.
  • the CTF (ADF) functional module can be co-located in the ProSe-related NF (such as 5G DDNMF).
  • the user equipment may locally collect charging information through a CTF (AMC), and report the charging information to the CEF of the network side device when the charging information reporting condition based on the QoS flow is satisfied; the network side device's The CEF then sends the charging information to the CHF, and the CHF generates a charging bill.
  • AMC CTF
  • the user equipment can report the charging information to the CTF (ADF) of the network side device through the Usage Information Report, and the CTF (ADF) of the network side device can use the Charging Data Request through the Nchf interface to report the charging information to the CTF (ADF) of the network side device. Send to CHF.
  • sending the charging information to the CEF of the network side device specifically includes:
  • the charging information may be subscribed by the CEF to the NF service.
  • the CEF can serve as a consumer of a ProSe Service (such as 5G DDNMF) to subscribe to related services, and collect charging information that may be required from different NF Services or management services (Management Service).
  • the CEF may subscribe to the NF service for charging information (for example, subscribe to a usage information report notification), and when the user equipment meets the reporting conditions for charging information based on the QoS flow, collect the charging information and send the charging information to the NF Service, NF Service sends the charging information to the CEF after receiving the charging information; the CEF sends the charging information to the CHF through the Nchf interface, and the CHF generates a charging bill.
  • a ProSe Service such as 5G DDNMF
  • the flow information of the QoS flow may include at least one or more of the following:
  • QoS attribute parameters For example, PC5 QoS parameters, PC5 QoS parameters such as: PQI, GFBR, MFBR, PC5LINK-AMBR, Range.
  • PC5 QoS characteristic parameters are for example: resource type, priority, packet delay budget, packet error rate, average window, maximum data burst, etc.
  • PFI PC5 QoS Flow Identifier
  • the user equipment can directly report the PQI (that is, PC5 5QI, 5G Qos identifier of the PC5 interface) in the QoS attribute parameter or the QoS characteristic parameter, or convert it into a corresponding 5QI report. That is: the PC5 QoS parameter or the PC5 QoS feature parameter may include PQI; or the user equipment maps the PQI to 5QI, and carries the 5QI in the PC5 QoS parameter or the PC5 QoS feature parameter.
  • the PC5 QoS parameter or the PC5 QoS feature parameter may include PQI
  • the user equipment maps the PQI to 5QI, and carries the 5QI in the PC5 QoS parameter or the PC5 QoS feature parameter.
  • the flow information of the QoS flow may include the end time of the QoS flow in addition to the above one or more items of information content.
  • the flow information of the QoS flow may also include other charging-related information, such as the following table:
  • trigger OC This field holds the reason for closing the QFI unit container trigger timestamp OC This field holds the timestamp of the trigger time OC This field holds the amount of time used total volume OC This field holds uplink and downlink usage.
  • uplink usage OC This field holds the uplink usage Downlink usage OC This field holds the downlink usage local serial number m This field holds the QFI data container serial number
  • the link information may include at least one or more of the following:
  • IP Internet Protocol
  • the IP multicast address of the adjacent service group such as the ProSe group IP multicast address
  • ProSe user equipment identification for example: ProSe user equipment identification, relay user equipment identification;
  • ProSe link ID of the ProSe link for example: ProSe layer 2 group ID, ProSe target layer 2 ID.
  • the link information may include a Layer-2 ID, a Layer-2 Group ID, a relay UE ID, and the like.
  • IP information may also be included.
  • Example 1 ProSe Direct Communication is based on session (Session) charging method.
  • Session Session
  • the UE reports charging information based on the PC5 QoS flow, specifically, including:
  • Step 1 UE service authorization and parameter configuration can be added by adding a flag bit, which is used to indicate whether the UE needs to report charging information based on PC5 QoS flow, and parameter configuration can be done through:
  • Step 1 UE1 and UE2 initiate a direct communication request
  • Step 2 UE1 and UE2 initiate a mutual authentication process, perform identity verification and establish a security association. After the authentication process is successful, the layer 2 security link on PC5 is established, and then the UE performs direct communication in unicast, multicast or broadcast mode;
  • Step 3 When the UE determines that the charging information reporting condition based on the PC5 QoS flow is met, according to the configuration information, the UE triggers the charging information acquisition and reporting process;
  • the configuration information includes the generation period for the user equipment to generate the usage information report, and the reporting condition is met when the UE reaches the generation period, and the collected charging information based on the PC5 QoS flow is reported;
  • the configuration information includes the first One instruction information, and the first instruction information indicates that the UE reports charging information based on the PC5 QoS flow, then the reporting condition is met, and the UE reports the collected charging information based on the PC5 QoS flow;
  • the configuration information includes the second instruction information, and the second indication information indicates that the UE reports the data volume of the received data, then the reporting condition is met, and the UE carries the charging information based on the PC5 QoS flow when sending the data volume of the received data;
  • the configuration information includes the first three indication information, and the third indication information indicates that the UE reports the amount of data to be sent, then the reporting condition is met, and the UE carries the charging information based on the PC5 QoS flow when sending the data volume of the received data;
  • Step 4 UE1 and UE2 respectively report the use information report containing the billing information, and send the use information report to ProSe Service (CTF-ADF); the message should carry the relevant information of one or more PC5 QoS flows, and relevant link information.
  • CTF-ADF ProSe Service
  • Step 5a CTF (ADF) sends charging data request (initial) to CHF, and carries flow information of PC5 QoS flow;
  • Step 5b Based on the policy, the CHF creates a ProSe service charging bill, and carries the flow information of the PC5 QoS flow and the link information related to the QoS flow;
  • Step 5c CHF authorizes NF (CTF) to start the service, and returns a charging data response message (initial).
  • Step 6 ProSe direct communication (One-to-One direct traffic) is continuously performed between UE1 and UE2.
  • Step 7 When the UE meets the charging information reporting condition based on the PC5 QoS flow, the charging information reporting process is triggered;
  • Step 8 The UE reports a usage information report containing charging information to the CTF, and the usage information report includes the flow information of the PC5 QoS flow and the link information related to the QoS flow;
  • Step 9a to step 9c similar to steps 5a to 5c, CTF (ADF) sends charging data request message (update), CHF updates CDR, and replies charging data response message (update);
  • Step 10 UE1 sends a disconnection request message to UE2; UE2 replies with a disconnection response message, and deletes all context data associated with the second-layer link;
  • Step 11 UE1 receives the disconnection response message of UE2, and triggers the charging information reporting process;
  • Step 12 UE1 sends a usage information report containing charging information to NF (CTF), and carries flow information of PC5 QoS flow and link information related to QoS flow;
  • Step 13a CTF (ADF) sends charging data request message (termination) to CHF, wherein carries the flow information of PC5 QoS flow and the relevant link information of QoS flow;
  • Step 13b based on the policy, the CHF creates a ProSe service charging bill, which can include the flow information carrying the PC5 QoS flow and the link information related to the QoS flow; the CDR in this step is the final bill reported to the billing system to generate the final After CDR, you can close CDR;
  • step 13c the CHF returns a charging data response message (termination).
  • Example 2 ProSe Direct Communication event-based charging method.
  • Event-based charging is a post-event charging method (Post Event Charging, PEC)), and reports to the CTF (ADF) of the network side device through the usage information report after the service is over, and is merged and processed by the ADF through the calculation
  • the fee data request message is reported to the CHF, and finally the CDR is generated by the CHF, taking the PC5 QoS flow as an example of the QoS flow, specifically, as shown in Figure 8, including:
  • Step 1 UE service authorization and parameter configuration, can add a flag bit to indicate whether the UE reports the charging information of PC5 QoS flow;
  • Step 1 UE1 and UE2 initiate a direct communication request
  • Step 2 UE1 and UE2 initiate a mutual authentication process, perform identity verification and establish a security association. After the authentication process is successful, the layer 2 security link on PC5 is established, and the UE performs direct communication in unicast, multicast or broadcast mode;
  • Step 3 ProSe direct communication is initiated between UEs.
  • Step 4 UE1 sends a disconnection request message to UE2; UE2 replies with a disconnection response message, and deletes all context data associated with the second-layer link;
  • Step 5 UE1 receives the disconnection response message of UE2, and triggers the usage reporting process;
  • Step 6-7 UE1 collects the flow information of QoS flow on PC5 during the PC5 communication process with UE2, and after the service ends, when UE determines that the charging information reporting condition based on PC5 QoS flow is satisfied, report by using the information Reported to the CTF of the network side device, that is, ProSe Service (CTF-ADF), the usage information report carries the flow information of the PC5 QoS flow and the link information related to the QoS flow.
  • CTF-ADF ProSe Service
  • Step 8a-c ADF reports to CHF through charging data request message (event), which carries flow information of PC5 QoS flow and link information related to QoS flow. Finally, the CHF generates charging and billing information CDRs, which may contain QoS-related charging information; the CHF sends a charging data response message (event) to the ADF.
  • event charging data request message
  • CDRs charging and billing information
  • ProSe Direct Communication is an event-based billing method, subscribes to billing information through CEF, and CEF can subscribe to related services as a user of ProSe Service (for example, 5G DDNMF), and collect possible required billing from different NF Service or Management Service fee information.
  • QoS flow Take described QoS flow as PC5 QoS flow as an example, specifically, as shown in Figure 9, including:
  • Step 1 CEF decides to subscribe to the usage information report notification from the billing-related ProSe Service Provider (such as: 5G DDNMF);
  • the billing-related ProSe Service Provider such as: 5G DDNMF
  • Step 2 CEF initiates a subscription request to ProSe Service Provider
  • Step 3 CEF receives the subscription response
  • Step 4 UE1 and UE2 initiate a direct communication request
  • Step 5 UE1 and UE2 initiate a mutual authentication process, perform identity verification and establish a security association. After the authentication process is successful, the layer 2 security link on PC5 is established, and the UE performs direct communication in unicast, multicast or broadcast mode;
  • Step 6 ProSe direct communication is initiated between UEs.
  • Step 7 UE1 sends a disconnection request message to UE2; UE2 replies with a disconnection response message, and deletes all context data associated with the second-layer link;
  • Step 8 UE1 receives the disconnection response message of UE2, and triggers the usage reporting process;
  • Step 9 When UE1 determines that the charging information reporting condition based on the PC5 QoS flow is met, the reporting of charging information is triggered;
  • Step 10 the UE sends a usage information report to the ProSe Service Provider, carrying the flow information of the PC5 QoS flow and the link information related to the QoS flow;
  • Step 11 billing ProSe Service Provider notifies CEF to process usage information report
  • Step 12 CEF replies with a notification confirmation message
  • Step 13a CEF sends charging data request message to CHF, carries flow information of PC5 QoS flow and link information related to QoS flow;
  • Step 13b CHF generates CDR
  • step 13c the CHF replies with a charging request response message.
  • Embodiment 4 ProSe Direct Communication relay UE (UE-Network relay) is event-based charging.
  • the L3 relay architecture (L3 relay architect) is shown in Figure 10.
  • the remote UE communicates with the ProSe relay UE through the PC5 interface; the relay UE communicates with the 5G access network (New Generation Radio Access Network, NG-RAN) through the Uu interface, and the 5G core network (5GC ) communicates with the access layer (Access Stratum, AS) through the N6 interface.
  • 5G access network New Generation Radio Access Network, NG-RAN
  • 5GC 5G core network
  • the PC5 QoS flow includes: remote UE, ProSe relay UE, NG-RAN, access and mobility management function (Access and Mobility Management Function, AMF ), session management function (Session Management Function, SMF), user plane function (User Plane Function, UPF), ProSe service CTF, CHF; wherein, the realization process of described billing method comprises:
  • Step 0a-b service authorization and configuration of the ProSe relay UE; service authorization and configuration of the remote UE. You can add the charging information flag whether to report QoS flow.
  • Step 1 the relay UE establishes a PDU session to relay, using the default PDU session parameters or pre-configured parameters received in step 0;
  • Step 2 According to the authorization and configuration in step 0, the Remote UE executes the ProSe discovery process
  • Step 3 the remote UE selects a relay UE and establishes direct communication
  • Step 4 IPv4 address/IPv6 prefix distribution
  • Step 5 the relay UE reports the relay UE report (for example: remote user ID, remote UE information) to the SMF;
  • Step 6 When the remote UE determines that the charging information reporting condition is satisfied, according to the configuration, the UE triggers the usage status reporting process.
  • the trigger levels and trigger conditions are not described here.
  • Step 7 the remote UE sends the use information report to the relay UE; and forwards it to the network side CTF by the relay UE; carries the flow information of the PC5 QoS flow and the link information related to the QoS flow;
  • Step 8 When the relay UE determines that the charging information reporting condition is met, according to the configuration, the UE triggers the usage reporting process
  • Step 9 the relay UE sends a usage information report to the ProSe service CTF on the network side;
  • steps 8 and 9 may occur before steps 6 and 7, and the specific sequence is not limited here.
  • Step 10a CTF (ADF) sends charging data request message (termination) to CHF, and carries relevant information of PC5QoS flow and corresponding link information;
  • Step 10b based on the policy, the CHF creates a CDR
  • step 10c the CHF returns a charging data response message (termination).
  • the UE obtains the charging information based on the QoS flow and reports it to the network side device, and the network side device reports the charging information to the CHF to complete the charging.
  • This solution can be billed based on ProSe-based service traffic, and can meet billing scenarios of various potential vertical services in ProSe.
  • the embodiment of this application also provides a charging method, which is applied to the network side device, including:
  • Step 121 the network side device obtains the charging information of the QoS flow sent by the user equipment, and the charging information is generated based on the proximity service provided by the user equipment;
  • Step 122 sending the charging information to the charging function CHF;
  • the charging information includes: flow information of the QoS flow.
  • the user equipment collects the charging information based on the QoS flow, and may send the charging information to the network side device by using an information report.
  • the network side device may generate a charging request message according to the charging information, the charging request message includes the charging information, and pass the charging request The message sends the charging information to the CHF, and the CHF generates a charging bill.
  • the network side device may configure whether the user equipment needs to report charging information based on the QoS flow.
  • the UE collects and reports the charging information of the QoS flow.
  • the UE acquires the charging information of the QoS flow and reports it to the network side device, and the network side device reports the charging information to the CHF to complete the charging.
  • This solution can be billed based on ProSe-based service traffic, and can meet billing scenarios of various potential vertical services in ProSe.
  • the method may further include: configuring the configuration information of the charging information for the user equipment, for example: the configuration information may be ProSe based on PC5 QoS Flow accounting configuration information.
  • the configuration information may include at least one or more of the following:
  • First indication information where the first indication information is used to indicate whether to report charging information based on the QoS flow
  • the second indication information is used to indicate whether to report the data volume of the received data
  • Third indication information where the third indication information is used to indicate whether to report the data volume of the sent data.
  • the network side device may configure configuration information for the UE, the configuration information may include one or more items above, and the multiple items may refer to at least two items.
  • the UE may determine whether the charging information reporting condition is met according to the configuration information, and when the charging reporting condition is met, the CTF (AMC) on the UE reports the charging information to the network side device.
  • the configuration information may indicate whether the UE reports charging information based on QoS flow through a new flag bit.
  • the configuration information may also be pre-configured by the user equipment, for example, configured in the UICC. In the case that the configuration information is pre-configured by the user equipment, the configuration Steps to configure information.
  • the configuration information may be provided in the following ways:
  • the UE may also acquire the charging information of the QoS flow based on a charging trigger event, which will not be described in detail here.
  • the QoS flow-based charging triggering level of the user equipment may be QoS flow-based triggering and/or link-based triggering.
  • the trigger based on the link is for example: the trigger related to the layer two link on PC5; the trigger related to the layer two link can refer to the change of the Layer-2 link triggering the charging based on the PC5 QoS flow, wherein, Layer -2 When the link changes, the QoS flow in the Layer 2 link also changes.
  • the trigger based on the QoS flow is for example: the trigger related to the PC5 QoS flow in the layer 2 link. That is, the change of the QoS flow in the Layer-2 link triggers the charging based on the PC5 QoS flow, and the charging based on the PC5 QoS flow may be triggered by a change of a separate QoS flow.
  • the acquiring the charging information of the QoS flow sent by the user equipment includes: acquiring a usage information report sent by the user equipment according to a reporting period of the charging information, and the usage information report includes the charging information.
  • the network side device may configure charging information configuration information for the UE, and the configuration information may also be pre-configured for the UE, and the configuration information may include the reporting period for the UE to report the usage information report, the The usage information report is generated according to the charging information, and the UE sends the usage information report to the network side device according to the reporting period.
  • the acquiring the charging information sent by the user equipment may include:
  • the sending the charging information to the charging function CHF includes: sending the charging information to the CHF by using the charging function service Nchf interface through the CTF or the CEF. Wherein, the charging information is used by the CHF to charge the generated ProSe.
  • the user equipment can locally collect QoS charging information through the CTF (AMC), and report the charging information to the CTF (ADF ); the CTF (ADF) of the network side device then sends the charging information to the CHF, and the CHF generates a charging bill.
  • the CTF (ADF) functional module can be co-located in the ProSe-related NF (such as 5G DDNMF).
  • the user equipment may locally collect QoS charging information through the CTF (AMC), and report the charging information to the CEF of the network side device when the charging information reporting condition based on the QoS flow is met; the network side The CEF of the device then sends the charging information to the CHF, and the CHF generates a charging bill.
  • AMC CTF
  • the user equipment can report the charging information to the CTF (ADF) or CEF of the network side equipment through the Usage Information Report, and the CTF (ADF) CEF of the network side equipment can use the Charging Data Request through the Nchf interface to report the charging information
  • the charging information is sent to the CHF, so that the CHF generates a charging bill according to the charging information.
  • the method before receiving the charging information sent by the user equipment to the charging enforcement function CEF, the method may further include:
  • the receiving the charging information sent by the user equipment to the charging execution function CEF includes: receiving the charging information sent to the CEF by the NF service; wherein the charging information is sent by the user equipment to the NF service.
  • CEF can serve as a consumer of ProSe Service (such as 5G DDNMF) to subscribe to related services, and collect charging information that may be required from different NF Services or Management Services.
  • the CEF may subscribe to the NF service for charging information (for example, subscribe to a usage information report notification), and when the user equipment meets the charging information reporting conditions of ProSe based QoS flow charging, collect the charging information and send the charging information After receiving the charging information, the NF Service sends the charging information to the CEF; the CEF sends the charging information to the CHF through the Nchf interface, and the CHF generates a charging bill.
  • ProSe Service such as 5G DDNMF
  • the flow information of the QoS flow may include at least one or more of the following:
  • QoS attribute parameters For example: PC5 QoS parameters, PC5 QoS parameters such as: PQI, GFBR, MFBR, PC5LINK-AMBR, Range.
  • PC5 QoS feature parameter Described PC5 QoS feature parameter is for example: resource type, priority, packet delay budget, packet error rate, average window, maximum data burst, etc.
  • PFI is the PC5 QoS flow ID, which is used to identify a QoS flow, and the Relay UE will do the mapping in the Relay scenario.
  • the user equipment may directly report the PQI in the QoS parameter or the QoS characteristic parameter, or convert it into a corresponding 5QI for reporting. That is: the QoS parameter or the QoS feature parameter may include PQI; or the user equipment maps the PQI to 5QI, and carries the 5QI in the PC5 QoS parameter or the PC5 QoS feature parameter.
  • the flow information of the QoS flow may include other billing-related information in addition to the above-mentioned one or more items of information content, which is not limited here.
  • the charging information also includes: link information associated with the QoS flow, where the link information may include at least one or more of the following:
  • the IP multicast address of the adjacent service group such as the ProSe group IP multicast address
  • ProSe link ID of the ProSe link for example: ProSe layer 2 group ID, ProSe target layer 2 ID.
  • the link information may include a Layer-2 ID, a Layer-2 Group ID, a relay UE ID, and the like.
  • IP information may also be included.
  • FIGS. 7-11 The implementation process of the billing method in the embodiment of the present application is shown in FIGS. 7-11 , and details are not described here. It should be noted that the embodiment of the charging method applied to the network-side device in this application can realize all the processes implemented by the network-side device in the above-mentioned embodiment of the charging method applied to the user equipment, and details are not described here.
  • the UE acquires the charging information of the QoS flow and reports it to the network side device, and the network side device reports the charging information to the CHF to complete the charging.
  • This solution can be billed based on ProSe-based service traffic, and can meet billing scenarios of various potential vertical services in ProSe.
  • the billing device 1300 in the embodiment of the present application is applied to user equipment, including:
  • the first obtaining unit 1310 is configured to obtain charging information of a quality of service QoS flow, where the charging information is generated based on the proximity service provided by the user equipment;
  • the first sending unit 1320 is configured to send the charging information to the network side device
  • the charging information includes: flow information of the QoS flow.
  • the first acquiring unit 1310 is specifically configured to:
  • the charging trigger event includes at least one or more of the following:
  • a time condition of the ProSe link where the time condition of the ProSe link is used to indicate that a charging event is triggered if a set time is met within the lifetime of the ProSe link;
  • the data volume condition of the ProSe link is used to indicate that if the set data volume is satisfied within the life cycle of the ProSe link, a charging event will be triggered;
  • the time condition of the QoS flow is used to indicate that if the set time is met within the life cycle of the QoS flow, a charging event will be triggered;
  • the data volume condition of the QoS flow is used to indicate that if the set data volume is satisfied within the life cycle of the QoS flow, a charging event will be triggered.
  • the configuration information includes at least one or more of the following:
  • First indication information where the first indication information is used to indicate whether to report charging information based on the QoS flow
  • the second indication information is used to indicate whether to report the data volume of the received data
  • Third indication information where the third indication information is used to indicate whether to report the data volume of the sent data.
  • the device also includes:
  • a report generating unit configured to generate a usage information report including the charging information according to the generation cycle of generating the usage information report included in the configuration information after the charging information is acquired;
  • the first sending unit 1320 is specifically configured to: send the usage information report to the network side device according to the reporting period in the configuration information.
  • the first sending unit 1320 includes:
  • a first sending subunit configured to send the charging information to a charging trigger function CTF or a charging enforcement function CEF of the network side device, and the CTF or the CEF forward the charging information to the CHF ;
  • the charging information is used by the CHF to charge the generated ProSe.
  • the first sending subunit is specifically configured to: send the charging information to the CEF of the network side device through a charging-related network function NF service.
  • the flow information of the QoS flow includes at least one or more of the following:
  • the charging information further includes link information associated with the QoS flow, where the link information includes at least one or more of the following:
  • the IP multicast address of the proximity service group
  • the link ID of the ProSe link is The link ID of the ProSe link.
  • the UE acquires the charging information of the QoS flow and reports it to the network side device, and the network side device reports the charging information to the CHF to complete the charging.
  • This solution can be billed based on ProSe-based service traffic, and can meet billing scenarios of various potential vertical services in ProSe.
  • the above-mentioned device provided by the embodiment of the present application can implement all the method steps implemented by the above-mentioned embodiment of the method applied to the user equipment, and can achieve the same technical effect.
  • the same parts and beneficial effects as those of the method embodiment will be described in detail.
  • the billing device 1400 provided by the embodiment of the present application is applied to network side equipment, including:
  • the second acquiring unit 1410 is configured to acquire the charging information of the QoS flow sent by the user equipment, where the charging information is generated based on the proximity service provided by the user equipment;
  • the second sending unit 1420 is configured to send the charging information to a charging function CHF;
  • the charging information includes: flow information of the QoS flow.
  • the shown device also includes:
  • a configuration unit configured to configure configuration information of charging information for the user equipment.
  • the configuration information includes at least one or more of the following:
  • First indication information where the first indication information is used to indicate whether to report charging information based on the QoS flow
  • the second indication information is used to indicate whether to report the data volume of the received data
  • Third indication information where the third indication information is used to indicate whether to report the data volume of the sent data.
  • the second obtaining unit 1410 is specifically configured to: obtain a usage information report sent by the user equipment according to a reporting period of charging information, where the usage information report includes the charging information.
  • the second obtaining unit 1410 includes:
  • the first receiving subunit is configured to receive the charging information sent by the user equipment to the charging trigger function CTF or the charging enforcement function CEF;
  • the second sending unit 1420 is specifically configured to: use the charging function service Nchf interface to send the charging information to the CHF through the CTF or the CEF;
  • the charging information is used by the CHF to charge the generated ProSe.
  • the first receiving subunit is specifically configured to: receive the charging information sent by the NF service to the CEF; wherein the charging information is sent by the user equipment to the NF service.
  • the flow information of the QoS flow includes at least one or more of the following:
  • the charging information further includes link information associated with the QoS flow, where the link information includes at least one or more of the following:
  • the IP multicast address of the proximity service group
  • the link ID of the ProSe link is The link ID of the ProSe link.
  • the UE acquires the charging information of the QoS flow and reports it to the network side device, and the network side device reports the charging information to the CHF to complete the charging.
  • This solution can be billed based on ProSe-based service traffic, and can meet billing scenarios of various potential vertical services in ProSe.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit.
  • the above-mentioned integrated units can be implemented in the form of hardware or in the form of software functional units.
  • the integrated unit is implemented in the form of a software function unit and sold or used as an independent product, it can be stored in a processor-readable storage medium.
  • the essence of the technical solution of this application or the part that contributes to the related technology or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium.
  • a computer device which may be a personal computer, a server, or a network device, etc.
  • a processor processor
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disc and other media that can store program codes. .
  • the embodiment of the present application also provides a user equipment, including: a memory 1520, a transceiver 1500, and a processor 1510; wherein, the memory 1520 is used to store computer programs; the transceiver 1500 is used to Sending and receiving data under the control of the processor 1510; the processor 1510 is used to read the computer program in the memory and perform the following operations:
  • the transceiver is used to: send the charging information to the network side device;
  • the charging information includes: flow information of the QoS flow.
  • the processor 1510 is configured to read the computer program in the memory and perform the following operations:
  • the charging trigger event includes at least one or more of the following:
  • a time condition of the ProSe link where the time condition of the ProSe link is used to indicate that a charging event is triggered if a set time is met within the lifetime of the ProSe link;
  • the data volume condition of the ProSe link is used to indicate that if the set data volume is satisfied within the life cycle of the ProSe link, a charging event will be triggered;
  • the time condition of the QoS flow is used to indicate that if the set time is met within the life cycle of the QoS flow, a charging event will be triggered;
  • the data volume condition of the QoS flow is used to represent that if the set data volume is satisfied within the life cycle of the QoS flow, a charging event will be triggered.
  • the configuration information includes at least one or more of the following:
  • First indication information where the first indication information is used to indicate whether to report charging information based on the QoS flow
  • the second indication information is used to indicate whether to report the data volume of the received data
  • Third indication information where the third indication information is used to indicate whether to report the data volume of the sent data.
  • the processor is also configured to read a computer program in the memory and perform the following operations:
  • the transceiver sends the billing information to the network side device, including:
  • the usage information report is sent to the network side device according to the reporting period in the configuration information.
  • the transceiver sends the charging information to the network side device, including:
  • the charging information is used by the CHF to charge the generated ProSe.
  • the transceiver sends the charging information to the CEF of the network side device, specifically including:
  • the flow information of the QoS flow includes at least one or more of the following:
  • the charging information further includes link information associated with the QoS flow, where the link information includes at least one or more of the following:
  • the IP multicast address of the proximity service group
  • the link ID of the ProSe link is The link ID of the ProSe link.
  • the UE acquires the charging information of the QoS flow and reports it to the network side device, and the network side device reports the charging information to the CHF to complete the charging.
  • This solution can be billed based on ProSe-based service traffic, and can meet billing scenarios of various potential vertical services in ProSe.
  • the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by the processor 1510 and various circuits of the memory represented by the memory 1520 are linked together.
  • the bus architecture can also link together various other circuits such as peripherals, voltage regulators, and power management circuits, etc., which are well known in the art and therefore will not be further described herein.
  • the bus interface provides the interface.
  • Transceiver 1500 may be a plurality of elements, including a transmitter and a transceiver, providing a means for communicating with various other devices over a transmission medium.
  • the user interface 1530 may also be an interface capable of connecting externally and internally to required devices, and the connected devices include but not limited to keypads, displays, speakers, microphones, joysticks, and the like.
  • the processor 1510 is responsible for managing the bus architecture and general processing, and the memory 1520 can store data used by the processor 510 when performing operations.
  • the processor 1510 may be a central processing unit (Central Processing Unit, CPU), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field-Programmable Gate Array, FPGA) or a complex programmable Logic device (Complex Programmable Logic Device, CPLD), the processor can also adopt a multi-core architecture.
  • CPU Central Processing Unit
  • ASIC Application Specific Integrated Circuit
  • FPGA Field-Programmable Gate Array
  • CPLD Complex Programmable Logic Device
  • the processor is used to execute any one of the methods provided in the embodiments of the present application according to the obtained executable instructions by calling the computer program stored in the memory.
  • the processor and memory may also be physically separated.
  • the user equipment involved in this embodiment of the present application may be a device that provides voice and/or data connectivity to a user, a handheld device with a wireless connection function, or other processing devices connected to a wireless modem.
  • the user equipment such as terminal equipment, includes wireless terminal equipment.
  • the wireless terminal equipment can communicate with one or more core networks (Core Network, CN) via a radio access network (Radio Access Network, RAN), and the wireless terminal equipment can be Mobile terminal equipment, such as mobile phones (or "cellular" phones) and computers with mobile terminal equipment, such as portable, pocket, hand-held, computer built-in or vehicle-mounted mobile devices, which are connected to wireless access network to exchange language and/or data.
  • Core Network Core Network
  • RAN Radio Access Network
  • Wireless terminal equipment can also be called system, subscriber unit, subscriber station, mobile station, mobile station, remote station, access point , remote terminal (remote terminal), access terminal (access terminal), user terminal (user terminal), user agent (user agent), and user device (user device), which are not limited in this embodiment of the application.
  • the embodiment of the present application also provides a network side device, including: a memory 1620, a transceiver 1600, and a processor 1610; wherein, the memory 1620 is used to store computer programs; send and receive data under the control of the processor 1610;
  • the transceiver 1600 is configured to perform the following operations: acquire the charging information of the QoS flow sent by the user equipment, where the charging information is generated based on the proximity service provided by the user equipment;
  • the charging information includes: flow information of the QoS flow and/or link information associated with the QoS flow.
  • the processor 1610 is configured to read the computer program in the memory and perform the following operations:
  • the configuration information includes at least one or more of the following:
  • First indication information where the first indication information is used to indicate whether to report charging information based on the QoS flow
  • the second indication information is used to indicate whether to report the data volume of the received data
  • Third indication information where the third indication information is used to indicate whether to report the data volume of the sent data.
  • the transceiver acquires the charging information of the QoS flow sent by the user equipment, including:
  • the transceiver acquires the charging information sent by the user equipment, it is specifically used for:
  • the transceiver sends the charging information to a charging function CHF, including:
  • the charging information is used by the CHF to charge the generated ProSe.
  • the transceiver receives the charging information sent by the user equipment to the charging enforcement function CEF, including:
  • the flow information of the QoS flow includes at least one or more of the following:
  • the charging information further includes link information associated with the QoS flow, where the link information includes at least one or more of the following:
  • the IP multicast address of the proximity service group
  • the link ID of the ProSe link is The link ID of the ProSe link.
  • the UE acquires the charging information of the QoS flow and reports it to the network side device, and the network side device reports the charging information to the CHF to complete the charging.
  • This solution can be billed based on ProSe-based service traffic, and can meet billing scenarios of various potential vertical services in ProSe.
  • the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by the processor 1610 and various circuits of the memory represented by the memory 1620 are linked together.
  • the bus architecture can also link together various other circuits such as peripherals, voltage regulators, and power management circuits, etc., which are well known in the art and therefore will not be further described herein.
  • the bus interface provides the interface.
  • Transceiver 1600 may be a plurality of elements, including a transmitter and a transceiver, providing a means for communicating with various other devices over transmission media.
  • the processor 1610 is responsible for managing the bus architecture and general processing, and the memory 1620 can store data used by the processor 1610 when performing operations.
  • the processor 1610 can be a central processing unit (Central Processing Unit, CPU), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field-Programmable Gate Array, FPGA) or a complex programmable logic device (Complex Programmable Logic Device, CPLD), the processor can also adopt a multi-core architecture.
  • CPU Central Processing Unit
  • ASIC Application Specific Integrated Circuit
  • FPGA Field-Programmable Gate Array
  • CPLD Complex Programmable Logic Device
  • the above-mentioned network-side device provided by the embodiment of the present application can implement all the method steps implemented by the above-mentioned embodiment of the method applied to the network-side device, and can achieve the same technical effect. Parts and beneficial effects in the embodiment that are the same as those in the method embodiment are specifically described in detail.
  • the network-side equipment involved in the embodiment of the present application can also be the service network (Service NE) in the billing architecture with distributed CTF functional modules, which is not limited here .
  • a specific embodiment of the present application also provides a processor-readable storage medium on which a computer program is stored, wherein, when the program is executed by the processor, the steps of the above charging method are implemented. And can achieve the same technical effect, in order to avoid repetition, no more details here.
  • the readable storage medium can be any available medium or data storage device that can be accessed by the processor, including but not limited to magnetic storage (such as floppy disk, hard disk, magnetic tape, magneto-optical disk (Magneto-Optical Disk, MO) etc.) , optical storage (such as compact disc (Compact Disk, CD), digital video disc (Digital Versatile Disc, DVD), Blu-ray Disc (Blu-ray Disc, BD), high-definition universal disc (High-Definition Versatile Disc, HVD), etc.), And semiconductor memory (such as read-only memory (Read-Only Memory, ROM), erasable programmable read-only memory (Erasable Programmable ROM, EPROM), charged erasable programmable read-only memory (Electrically EPROM, EEPROM), nonvolatile Non-volatile memory (NAND FLASH), solid state hard disk (Solid State Disk or Solid State Drive, SSD)), etc.
  • magnetic storage such as floppy disk, hard
  • the embodiments of the present application may be provided as methods, systems, or computer program products. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) having computer-usable program code embodied therein.
  • processor-executable instructions may also be stored in a processor-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, such that the instructions stored in the processor-readable memory produce a manufacturing product, the instruction device implements the function specified in one or more procedures of the flow chart and/or one or more blocks of the block diagram.
  • processor-executable instructions can also be loaded onto a computer or other programmable data processing device, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented
  • the executed instructions provide steps for implementing the functions specified in the flow or flows of the flowcharts and/or the block or blocks of the block diagrams.
  • the division of the above modules is only a division of logical functions, and may be fully or partially integrated into a physical entity or physically separated during actual implementation.
  • these modules can all be implemented in the form of calling software through processing elements; they can also be implemented in the form of hardware; some modules can also be implemented in the form of calling software through processing elements, and some modules can be implemented in the form of hardware.
  • the determining module may be a separate processing element, or may be integrated in a chip of the above-mentioned device.
  • it may be stored in the memory of the above-mentioned device in the form of program code, and a certain processing element of the above-mentioned device may Call and execute the functions of the modules identified above.
  • each step of the above method or each module above can be completed by an integrated logic circuit of hardware in the processor element or an instruction in the form of software.
  • each module, unit, subunit or submodule may be one or more integrated circuits configured to implement the above method, for example: one or more specific integrated circuits (Application Specific Integrated Circuit, ASIC), or, one or Multiple microprocessors (digital signal processor, DSP), or, one or more field programmable gate arrays (Field Programmable Gate Array, FPGA), etc.
  • ASIC Application Specific Integrated Circuit
  • DSP digital signal processor
  • FPGA Field Programmable Gate Array
  • the processing element may be a general-purpose processor, such as a central processing unit (Central Processing Unit, CPU) or other processors that can call program codes.
  • these modules can be integrated together and implemented in the form of a system-on-a-chip (SOC).
  • SOC system-on-a-chip

Landscapes

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

Abstract

本申请提供了一种计费方法、用户设备及网络侧设备。所述方法包括：用户设备获取服务质量QoS流的计费信息，所述计费信息是基于所述用户设备提供邻近服务产生的；向网络侧设备发送所述计费信息；其中，所述计费信息包括：所述QoS流的流信息。

Description

一种计费方法、用户设备及网络侧设备
相关申请的交叉引用
本申请主张在2021年06月17日在中国提交的中国专利申请号No.202110671716.4的优先权，其全部内容通过引用包含于此。
技术领域
本申请涉及通信技术领域，尤其涉及一种计费方法、用户设备及网络侧设备。
背景技术
邻近服务(Proximity based Services，ProSe)是指当用户设备(User Equipment，UE)彼此邻近时，能够使用邻近服务进行直接连接和通信的一种无线通讯技术。它可以在蜂窝通信系统的控制下允许新空口(New Radio，NR)/长期演进(Long Term Evolution，LTE)UE之间利用小区无线资源直接进行通信，而不经过蜂窝网络中转。
随着第五代移动通信技术(5th-Generation，5G)核心网基于服务架构(Service Based Architecture，SBA)的部署,计费系统也演进到融合计费系统(Converged Charging System，CCS)，将在线计费和离线计费功能融合在一起，采用基于服务的架构对外提供统一的接口。
然而，在邻近服务场景下，如何准确地对所发生的邻近服务进行计费成为亟需解决的重要问题。
发明内容
本申请的目的在于提供一种计费方法、用户设备及网络侧设备，解决邻近服务场景下的计费问题。
本申请的实施例提供一种计费方法，包括：
用户设备获取服务质量QoS流的计费信息，所述计费信息是基于所述用户设备提供邻近服务产生的；
向网络侧设备发送所述计费信息；
其中，所述计费信息包括：所述QoS流的流信息。
可选地，所述用户设备获取服务质量QoS流的计费信息，包括：
基于计费触发事件，获取QoS流的计费信息；
或者；
根据配置信息，触发获取QoS流的计费信息。
可选地，所述计费触发事件包括以下至少一项或者多项：
邻近服务链路建立；
QoS流建立；
QoS属性参数发生变化；
邻近服务链路的时间条件，所述邻近服务链路的时间条件用于表征在该邻近服务链路的生存周期内若满足设定时间就触发计费事件；
邻近服务链路的数据量条件，所述邻近服务链路的数据量条件用于表征在该邻近服务链路的生命周期内若满足设定数据量就触发计费事件；
QoS流的时间条件，所述QoS流的时间条件用于表征在该QoS流的生存周期内若满足设定时间就触发计费事件；
QoS流的数据量条件，所述QoS流的数据量条件用于表征在该QoS流的生存周期内若满足设定数据量就触发计费事件。
可选地，所述配置信息包括以下至少一项或者多项：
根据所述计费信息生成使用信息报告的生成周期；
上报计费信息的上报周期；
第一指示信息，所述第一指示信息用于指示是否上报基于QoS流的计费信息；
第二指示信息，所述第二指示信息用于指示是否上报接收数据的数据量；
第三指示信息，所述第三指示信息用于指示否上报发送数据的数据量。
可选地，所述方法还包括：
在获取所述计费信息之后，按照配置信息中包含的生成使用信息报告的生成周期，生成包含所述计费信息的使用信息报告；
所述向网络侧设备发送所述计费信息，包括：
按照配置信息中的上报周期，将所述使用信息报告发送给网络侧设备。
可选地，所述向网络侧设备发送所述计费信息，包括：
将所述计费信息发送至网络侧设备的计费触发功能(Charging Trigger Function，CTF)或者计费执行功能(Charging Enablement Function，CEF)，并由所述CTF或者所述CEF将所述计费信息转发给CHF；
其中，所述计费信息用于所述CHF对发生的所述邻近服务进行计费。
可选地，将所述计费信息发送至网络侧设备的CEF，具体包括：
通过计费相关的网络功能(Network Function，NF)服务，向所述网络侧设备的CEF发送所述计费信息。
可选地，所述QoS流的流信息包括以下至少一项或者多项：
QoS属性参数；
QoS特征参数；
QoS流标识PFI(PC5 QoS Flow Identifier，PFI)；
与PFI匹配的业务数据流的第一个数据包的传输时间；
与PFI匹配的业务数据流的最后一个数据包的传输时间；
QoS流发生的时间；
服务网络功能标识。
可选地，所述计费信息还包括与所述QoS流关联的链路信息，其中，所述链路信息包括以下至少一项或者多项：
源互联网协议(Internet Protocol，IP)地址；
目标IP地址；
中继IP地址；
邻近服务组的IP多播地址；
参与邻近服务的设备标识；
邻近服务链路的链路标识。
本申请的实施例提供一种计费方法，包括：
网络侧设备获取用户设备发送的QoS流的计费信息，所述计费信息是基于所述用户设备提供邻近服务产生的；
网络侧设备将所述计费信息发送至计费功能(Charging Function，CHF)；
其中，所述计费信息包括：所述QoS流的流信息。
可选地，在获取用户设备发送的QoS流的计费信息之前，所述方法还包括：
为所述用户设备配置计费信息的配置信息。
可选地，所述配置信息包括以下至少一项或者多项：
根据所述计费信息生成使用信息报告的生成周期；
上报计费信息的上报周期；
第一指示信息，所述第一指示信息用于指示是否上报基于QoS流的计费信息；
第二指示信息，所述第二指示信息用于指示是否上报接收数据的数据量；
第三指示信息，所述第三指示信息用于指示否上报发送数据的数据量。
可选地，所述获取用户设备发送的QoS流的计费信息，包括：
获取所述用户设备按照计费信息的上报周期发送的使用信息报告，所述使用信息报告包含所述计费信息。
可选地，所述获取用户设备发送的计费信息，包括：
接收用户设备发送至计费触发功能CTF或者计费执行功能CEF的计费信息；
所述将所述计费信息发送至计费功能CHF，包括：
通过所述CTF或者所述CEF，利用计费功能服务化(Service-based interface exhibited by Charging Function，Nchf)接口将所述计费信息发送至所述CHF；
其中，所述计费信息用于所述CHF对发生的所述邻近服务进行计费。
可选地，接收用户设备发送至计费执行功能CEF的计费信息，包括：
接收NF服务发送至所述CEF的所述计费信息；其中，所述计费信息由所述用户设备发送至所述NF服务。
可选地，所述QoS流的流信息包括以下至少一项或者多项：
QoS属性参数；
QoS特征参数；
PFI；
与PFI匹配的业务数据流的第一个数据包的传输时间；
与PFI匹配的业务数据流的最后一个数据包的传输时间；
QoS流发生的时间；
服务网络功能标识。
可选地，所述计费信息还包括与所述QoS流关联的链路信息，其中，所述链路信息包括以下至少一项或者多项：
源IP地址；
目标IP地址；
中继IP地址；
邻近服务组的IP多播地址；
参与邻近服务的设备标识；
邻近服务链路的链路标识。
本申请的实施例提供一种用户设备，包括：存储器，收发机，处理器：
存储器，用于存储计算机程序；收发机，用于在所述处理器的控制下收发数据；处理器，用于读取所述存储器中的计算机程序并执行以下操作：
获取服务质量QoS流的计费信息，所述计费信息是基于所述用户设备提供邻近服务产生的；
所述收发机用于：向网络侧设备发送所述计费信息；
其中，所述计费信息包括：所述QoS流的流信息。
可选地，所述处理器用于读取所述存储器中的计算机程序并执行以下操作：
基于计费触发事件，获取QoS流的计费信息；
或者；
根据配置信息，触发获取QoS流的计费信息。
可选地，所述计费触发事件包括以下至少一项或者多项：
邻近服务链路建立；
QoS流建立；
QoS属性参数发生变化；
邻近服务链路的时间条件，所述邻近服务链路的时间条件用于表征在该 邻近服务链路的生存周期内若满足设定时间就触发计费事件；
邻近服务链路的数据量条件，所述邻近服务链路的数据量条件用于表征在该邻近服务链路的生命周期内若满足设定数据量就触发计费事件；
QoS流的时间条件，所述QoS流的时间条件用于表征在该QoS流的生存周期内若满足设定时间就触发计费事件；
QoS流的数据量条件，所述QoS流的数据量条件用于表征在该QoS流的生存周期内若满足设定数据量就触发计费事件。
可选地，所述配置信息包括以下至少一项或者多项：
根据所述计费信息生成使用信息报告的生成周期；
上报计费信息的上报周期；
第一指示信息，所述第一指示信息用于指示是否上报基于QoS流的计费信息；
第二指示信息，所述第二指示信息用于指示是否上报接收数据的数据量；
第三指示信息，所述第三指示信息用于指示否上报发送数据的数据量。
可选地，所述处理器还用于读取所述存储器中的计算机程序并执行以下操作：
在获取所述计费信息之后，按照配置信息中包含的生成使用信息报告的生成周期，生成包含所述计费信息的使用信息报告；
所述收发机向网络侧设备发送所述计费信息，包括：
按照配置信息中的上报周期，将所述使用信息报告发送给网络侧设备。
可选地，所述收发机向网络侧设备发送所述计费信息，包括：
将所述计费信息发送至网络侧设备的计费触发功能CTF或者计费执行功能CEF，并由所述CTF或者所述CEF将所述计费信息转发给CHF；
其中，所述计费信息用于所述CHF对发生的所述邻近服务进行计费。
可选地，所述收发机将所述计费信息发送至网络侧设备的CEF，具体包括：
通过计费相关的网络功能NF服务，向所述网络侧设备的CEF发送所述计费信息。
可选地，所述QoS流的流信息包括以下至少一项：
QoS属性参数；
QoS特征参数；
QoS流标识PFI；
与PFI匹配的业务数据流的第一个数据传输包的时间；
与PFI匹配的业务数据流的最后一个数据传输包的时间；
QoS流发生的时间；
服务网络功能标识。
可选地，所述计费信息还包括与所述QoS流关联的链路信息，其中，所述链路信息包括以下至少一项或者多项：
源IP地址；
目标IP地址；
中继IP地址；
邻近服务组的IP多播地址；
参与邻近服务的设备标识；
邻近服务链路的链路标识。
本申请的实施例提供一种网络侧设备，包括：存储器，收发机，处理器：
存储器，用于存储计算机程序；收发机，用于在所述处理器的控制下收发数据；处理器，用于读取所述存储器中的计算机程序：
所述收发机用于执行以下操作：获取用户设备发送的QoS流的计费信息，所述计费信息是基于所述用户设备提供邻近服务产生的；
将所述计费信息发送至计费功能CHF；
其中，所述计费信息包括：QoS流的流信息。
可选地，所述处理器还用于读取所述存储器中的计算机程序并执行以下操作
为所述用户设备配置计费信息的配置信息。
可选地，所述配置信息包括以下至少一项或者多项：
根据所述计费信息生成使用信息报告的生成周期；
上报计费信息的上报周期；
第一指示信息，所述第一指示信息用于指示是否上报基于QoS流的计费 信息；
第二指示信息，所述第二指示信息用于指示是否上报接收数据的数据量；
第三指示信息，所述第三指示信息用于指示否上报发送数据的数据量。
可选地，所述收发机获取用户设备发送的QoS流的计费信息，包括：
获取所述用户设备按照计费信息的上报周期发送的使用信息报告，所述使用信息报告包含所述计费信息。
可选地，所述收发机获取用户设备发送的计费信息时，具体用于：
接收用户设备发送至计费触发功能CTF或者计费执行功能CEF的计费信息；
所述收发机将所述计费信息发送至计费功能CHF，包括：
通过所述CTF或者所述CEF，利用计费功能服务化Nchf接口将所述计费信息发送至所述CHF；
其中，所述计费信息用于所述CHF对发生的所述邻近服务进行计费。
可选地，所述收发机接收用户设备发送至计费执行功能CEF的计费信息，包括：
接收NF服务发送至所述CEF的所述计费信息；其中，所述计费信息由所述用户设备发送至所述NF服务。
可选地，所述QoS流的流信息包括以下至少一项或者多项：
QoS属性参数；
QoS特征参数；
PFI；
与PFI匹配的业务数据流的第一个数据包的传输时间；
与PFI匹配的业务数据流的最后一个数据包的传输时间；
QoS流发生的时间；
服务网络功能标识。
可选地，所述计费信息还包括与所述QoS流关联的链路信息，其中，所述链路信息包括以下至少一项或者多项：
源IP地址；
目标IP地址；
中继IP地址；
邻近服务组的IP多播地址；
参与邻近服务的设备标识；
邻近服务链路的链路标识。
本申请的实施例提供一种计费装置，包括：
第一获取单元，用于获取服务质量QoS流的计费信息，所述计费信息是基于所述用户设备提供邻近服务产生的；
第一发送单元，用于向网络侧设备发送所述计费信息；
其中，所述计费信息包括：所述QoS流的流信息。
可选地，所述第一获取单元具体用于：
基于计费触发事件，获取QoS流的计费信息；
或者；
根据配置信息，触发获取QoS流的计费信息。
可选地，所述计费触发事件包括以下至少一项或者多项：
邻近服务链路建立；
QoS流建立；
QoS属性参数发生变化；
邻近服务链路的时间条件，所述邻近服务链路的时间条件用于表征在该邻近服务链路的生存周期内若满足设定时间就触发计费事件；
邻近服务链路的数据量条件，所述邻近服务链路的数据量条件用于表征在该邻近服务链路的生命周期内若满足设定数据量就触发计费事件；
QoS流的时间条件，所述QoS流的时间条件用于表征在该QoS流的生存周期内若满足设定时间就触发计费事件；
QoS流的数据量条件，所述QoS流的数据量条件用于表征在该QoS流的生存周期内若满足设定数据量就触发计费事件。
可选地，所述配置信息包括以下至少一项或者多项：
根据所述计费信息生成使用信息报告的生成周期；
上报计费信息的上报周期；
第一指示信息，所述第一指示信息用于指示是否上报基于QoS流的计费 信息；
第二指示信息，所述第二指示信息用于指示是否上报接收数据的数据量；
第三指示信息，所述第三指示信息用于指示否上报发送数据的数据量。
可选地，所述装置还包括：
报告生成单元，用于在获取所述计费信息之后，按照配置信息中包含的生成使用信息报告的生成周期，生成包含所述计费信息的使用信息报告；
所述第一发送单元具体用于：按照配置信息中的上报周期，将所述使用信息报告发送给网络侧设备。
可选地，所述第一发送单元包括：
第一发送子单元，用于将所述计费信息发送至网络侧设备的计费触发功能CTF或者计费执行功能CEF，并由所述CTF或者所述CEF将所述计费信息转发给CHF；
其中，所述计费信息用于所述CHF对发生的所述邻近服务进行计费。
可选地，所述第一发送子单元具体用于：通过计费相关的网络功能NF服务，向所述网络侧设备的CEF发送所述计费信息。
可选地，所述QoS流的流信息包括以下至少一项或者多项：
QoS参数；
QoS特征参数；
QoS流标识PFI；
与PFI匹配的业务数据流的第一个数据传输包的时间；
与PFI匹配的业务数据流的最后一个数据传输包的时间；
QoS流发生的时间；
服务网络功能标识。
可选地，所述计费信息还包括与所述QoS流关联的链路信息，其中，所述链路信息包括以下至少一项或者多项：
源IP地址；
目标IP地址；
中继IP地址；
邻近服务组的IP多播地址；
参与邻近服务的设备标识；
邻近服务链路的链路标识。
本申请的实施例提供一种计费装置，包括：
第二获取单元，用于获取用户设备发送的QoS流的计费信息，所述计费信息是基于所述用户设备提供邻近服务产生的；
第二发送单元，用于将所述计费信息发送至计费功能CHF；
其中，所述计费信息包括：所述QoS流的流信息。
可选地，所示装置还包括：
配置单元，用于为所述用户设备配置计费信息的配置信息。
可选地，所述配置信息包括以下至少一项或者多项：
根据所述计费信息生成使用信息报告的生成周期；
上报计费信息的上报周期；
第一指示信息，所述第一指示信息用于指示是否上报基于QoS流的计费信息；
第二指示信息，所述第二指示信息用于指示是否上报接收数据的数据量；
第三指示信息，所述第三指示信息用于指示否上报发送数据的数据量。
可选地，所述第二获取单元具体用于：获取所述用户设备按照计费信息的上报周期发送的使用信息报告，所述使用信息报告包含所述计费信息。
可选地，所述第二获取单元包括：
第一接收子单元，用于接收用户设备发送至计费触发功能CTF或者计费执行功能CEF的计费信息；
所述第二发送单元具体用于：通过所述CTF或者所述CEF，利用计费功能服务化Nchf接口将所述计费信息发送至所述CHF；
其中，所述计费信息用于所述CHF对发生的所述邻近服务进行计费。
可选地，所述第一接收子单元具体用于：接收NF服务发送至所述CEF的所述计费信息；其中，所述计费信息由所述用户设备发送至所述NF服务。
可选地，所述QoS流的流信息包括以下至少一项或者多项：
QoS属性参数；
QoS特征参数；
PFI；
与PFI匹配的业务数据流的第一个数据包的传输时间；
与PFI匹配的业务数据流的最后一个数据包的传输时间；
QoS流发生的时间；
服务网络功能标识。
可选地，所述计费信息还包含所述QoS流关联的链路信息，其中，所述链路信息包括以下至少一项或者多项：
源IP地址；
目标IP地址；
中继IP地址；
邻近服务组的IP多播地址；
参与邻近服务的设备标识；
邻近服务链路的链路标识。
本申请的实施例提供一种处理器可读存储介质，其上存储有计算机程序，该计算机程序被处理器执行时实现上述计费方法的步骤。
本申请的上述技术方案的有益效果是：
本申请的实施例，UE在邻近服务场景下，获取QoS流的计费信息并上报至网络侧设备，由UE在邻近服务场景下，获取的QoS流的计费信息包含QoS流的流信息，这样上报给网络侧设备之后，由网络侧设备将所述计费信息上报给CHF进而完成计费。该方案可以基于ProSe的业务数据完成计费，有效提升了邻近服务场景下基于QoS流计费的计费准确性，进而能够满足ProSe中各种潜在垂直业务的计费场景。
附图说明
图1表示基于服务化接口的ProSe 5G计费架构示意图之一；
图2表示基于服务化接口的ProSe 5G计费架构示意图之二；
图3表示第四代移动通信技术(the 4th Generation mobile communication technology，4G)ProSe基于PC5直接通讯计费的架构示意图之一；
图4表示4G ProSe基于PC5直接通讯计费的架构示意图之二；
图5表示直接通信的基本计费流程示意图；
图6表示本申请实施例的计费方法的流程示意图之一；
图7表示本申请实施例的计费方法的流程示意图之二；
图8表示本申请实施例的计费方法的流程示意图之三；
图9表示本申请实施例的计费方法的流程示意图之四；
图10表示本申请实施例的L3中继架构示意图；
图11表示本申请实施例的计费方法的流程示意图之五；
图12表示本申请实施例的计费方法的流程示意图之六；
图13表示本申请实施例的计费装置的结构示意图之一；
图14表示本申请实施例的计费装置的结构示意图之二；
图15表示本申请实施例的用户设备的结构示意图；
图16表示本申请实施例的网络侧设备的结构示意图。
具体实施方式
为使本申请要解决的技术问题、技术方案和优点更加清楚，下面将结合附图及具体实施例进行详细描述。在下面的描述中，提供诸如具体的配置和组件的特定细节仅仅是为了帮助全面理解本申请的实施例。因此，本领域技术人员应该清楚，可以对这里描述的实施例进行各种改变和修改而不脱离本申请的范围和精神。另外，为了清楚和简洁，省略了对已知功能和构造的描述。
应理解，说明书通篇中提到的“一个实施例”或“一实施例”意味着与实施例有关的特定特征、结构或特性包括在本申请的至少一个实施例中。因此，在整个说明书各处出现的“在一个实施例中”或“在一实施例中”未必一定指相同的实施例。此外，这些特定的特征、结构或特性可以任意适合的方式结合在一个或多个实施例中。
在本申请的各种实施例中，应理解，下述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
本申请实施例中术语“和/或”，描述关联对象的关联关系，表示可以存 在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。
本申请实施例中术语“多个”是指两个或两个以上，其它量词与之类似。
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本申请一部分实施例，并不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
在进行本申请实施例的说明时，首先对下面描述中所用到的一些概念进行解释说明。
一、CCS：
将在线计费和离线计费功能融合在一起，采用基于服务的架构对外提供统一的接口。除了传统的计费模式(流量、时长、事件等)，5G融合计费系统还支持多量纲计费，即对流量等业务采用按上下行速率、时延、垂直行业应用、特定服务(超高清视频及直播)、设备(跟踪装置、传感器)等要素计费的计费模式。主要计费方法有基于流计费(Flow Based Charging，FBC)的触发器(triggers)、基于服务质量(Quality of Service，QoS)流计费(QoS flow Based Charging，QBC)的触发器。
二、基于服务化接口的ProSe 5G计费架构：
对于ProSe直接通信(Direct Communication)基于5G服务化的架构如图1和图2所示，计费触发功能(Charging Trigger Function，CTF)被分成两个功能模块，计费指标收集(Accounting Metrics Collection，AMC)和计费数据转发(Accounting Data Forwarding，ADF)。UE上的AMC通过PC3ch接口将计费使用信息报告(Usage Information Report)消息发送到网络侧的ADF，ProSe相关的网络功能(Network Function，NF)，例如5G直接发现名称管理功能(Direct Discovery Name Management Function，DDNMF)，检查收到的使用信息(usage information)，如果包含有效的直接发现(Direct Discovery)或者直接通信(Direct communication)的使用数据(usage data)，则触发计费功能(Charging Function，CHF)的计费数据请求(Charging Data Request) 消息，并且由CHF生成账单信息(Charging Data Record，CDR)。5G功能模块和计费架构基于服务化接口。在相关技术中，4G的邻近通信功能(ProSe Function)模块功能分解到相应的邻近服务(ProSe Service)，例如基于策略控制功能(Policy Control Function，PCF)负责ProSe的服务授权和配置，5G DDNMF负责ProSe直接发现(ProSe Direct Discovery)等。
对于图1，UE的CTF(AMC)与5G DDNMF之间通过PC3ch接口通讯，5G DDNMF与CCS之间通过计费功能服务化(Service-based interface exhibited by Charging Function，Nchf)接口通讯。其中，CCS包括：CHF、计费网关功能(Charging Gateway Function，CGF)、批价功能(Rating Function，RF)、账户余额管理功能(Account Balance Management Function，ABMF)；CGF通过Bx接口(CGF与热计费功能的话单传送接口)与计费系统(Billing Domain)通讯。如图2所示，网络侧还包括计费执行功能(Charging Enablement Function，CEF)。
CEF可以作为网络功能服务(NF Service)的用户(consumer)订阅相关服务，从不同的NF Service或者管理服务(Management Service)收集可能需要的计费信息。
三、4G ProSe基于PC5直接通信计费的架构和基本流程。
当前，第三代伙伴组织计划(Third Generation Partnership Projects，3GPP)定义了基于LTE的ProSe计费架构和实现，包括直接发现、直接通信、UE到网络中继(UE to Network Relay)等。
如图3和图4所示，LTE中，邻近通信功能(ProSe function)通过PC3ch接口接收UE的CTF(AMC)上报的计费信息，并将Charging Data Request消息上报给计费数据功能(Charging Data Function，CDF)，由CDF生成账单信息CDR。其中，CDF生成CDR后，可以通过Ga接口将账单信息发送至CGF，CGF可以单独设置也可以集成设置于计费系统中。如图3所示，CGF通过Bpr接口与计费系统通讯。
直接通信的基本计费流程如图5所示，包括：
步骤1、UE1向UE2发送直接通信请求；
步骤2、UE1和UE2之间进行身份验证并建立安全关联；
步骤3、UE1和UE2之间建立直接通信；
步骤4、UE1向UE2发送断开连接请求；
步骤5、UE1接收断开响应；
步骤6、满足上报条件；
步骤7、UE1向ProSe Function发送使用信息报告(Usage information reporting)；
步骤8、ProSe Function向CDF发送计费数据请求(事件)(Charging Data Request)(Event)；
步骤9、CDF生成账单信息CDR；
步骤10、CDF向ProSe Function发送计费数据响应(Charging Data Response)。
需要说明的是，在步骤7中UE1所收集的邻近服务的计费信息主要包含邻近服务有关的链路层面的计费信息(例如：UE1的移动用户身份码(国际移动用户识别号)(International Mobile Subscriber Identification，IMSI)、接入的公用陆地移动网(Public Land Mobile Network，PLMN)标识、位置、邻近服务的方式等)。
那么基于服务化接口的ProSe 5G计费架构，5G数据连接计费(data connectivity charging)功能，包含SMF中的协议数据单元(Protocol Data Unit，PDU)会话、PDU会话内的业务数据流和QoS流。然而在当前的ProSe邻近通信中，SMF不负责ProSe直接通信，那么按照上述流程，SMF无法获取QoS流层面的计费信息，这样就导致对于相关的5G计费架构，SMF无法支持基于QoS流层面的计费，导致计费不够精准，因此需要重新设计针对ProSe QoS流的计费方法。
为了解决上述技术问题，本申请实施例提供一种计费方法、用户设备及网络侧设备。如图6所示，为本申请的实施例提供了一种计费方法的流程示意图，应用于用户设备，具体包括以下步骤：
步骤601、用户设备获取服务质量QoS流的计费信息，所述计费信息是基于所述用户设备提供邻近服务产生的。
所述邻近服务包含直连通信服务(例如：无线网络设备到设备(Device to  Device，D2D)服务；车用无线通信技术(vehicle to everything，V2X)服务等)、包含中继的ProSe服务等。UE可以预配置或者通过网络侧设备配置是否需要基于QoS流上报计费信息。在UE根据配置信息确定需要基于QoS流上报计费信息时，UE可以作为CTF(AMC)收集UE本地产生的计费信息。
步骤602、向网络侧设备发送所述计费信息；其中，所述计费信息包括：QoS流的流信息。
可选地，所述计费信息中还包含与所述QoS流关联的链路信息。
UE获取到所述计费信息后，将所述计费信息发送至所述网络侧设备。其中，所述计费信息可以包括QoS流的流信息(如：PC5 QoS flow的相关信息)和/或与所述QoS流对应的链路信息。可选地，UE可以作为CTF(AMC)通过Usage Information Report将所述计费信息上报到网络侧设备的CTF(ADF)，再由网络侧设备的CTF(ADF)或者CEF通过Nchf接口将所述计费信息上报至CHF，并由CHF生成计费账单。
可选地，UE可以利用PC3ch接口将所述Usage Information Report(即所述计费信息)上报至所述网络侧设备，也可以通过非接入层(Non-Access-Stratum，NAS)消息将所述Usage Information Report(即所述计费信息)上报至所述网络侧设备，在此不做限定。
本申请的实施例，UE获取QoS流的计费信息并上报至网络侧设备，由网络侧设备将所述计费信息上报给CHF进而完成计费。该方案可以基于ProSe的业务流量计费，能够满足ProSe中各种潜在垂直业务的计费场景。
进一步地，所述获取QoS流的计费信息，可以包括但不限于如下方式：
方式一：基于计费触发事件，获取QoS流的计费信息。
该实施例中，所述计费触发事件可以为ProSe计费的计费触发事件。所述计费触发事件可以为用户设备自定义或者预配置或者由网络侧设备配置。UE基于所述计费触发事件收集在本地的QoS流的计费信息。
方式二：根据配置信息，触发获取QoS流的计费信息。
该实施例中，所述配置信息可以是网络侧设备预先配置给所述用户设备，例如：由管理网元(Management Element，ME)提供；所述配置信息也可以由所述用户设备预配置，例如写入通用集成电路卡(Universal Integrated  Circuit Card，UICC)中。
UE可以根据基于QoS流计费的配置信息，确定是否需要收集计费信息、收集什么类型的计费信息，以及是否满足计费信息上报条件。在满足计费信息上报条件时，UE通过CTF(AMC)上报所述计费信息至网络侧设备。需要说明的是，所述配置信息可以通过新增标志位指示是否需要基于QoS flow上报计费信息。
其中，所述配置信息可以通过如下几种方式提供：
a)管理网元(Management Element，ME)提供；
b)在通用集成电路卡(Universal Integrated Circuit Card，UICC)中配置；
c)ProSe应用服务器通过PCF和/或PC1参考点提供/更新；
d)由PCF提供/更新给UE。
具体地，所述计费触发事件可以包括以下至少一项或者多项：
a)邻近服务链路建立。例如：提供邻近服务的两个UE之间层二链路(Layer-2 link)建立，即ProSe UE在层二链路建立的情况下，收集所述基于QoS流计费的计费信息。可选地，可以在层二链路结束的情况下，结束收集所述计费信息。
b)QoS流建立。例如：PC5 QoS流建立，即ProSe UE在PC5 QoS流建立的情况下，收集所述基于PC5 QoS流计费的计费信息。可选地，可以在PC5QoS流结束的情况下，结束收集所述计费信息。
c)QoS属性参数发生变化。例如PC5 QoS参数，所述PC5 QoS参数包括但不限于：直联链路服务质量指示符(PC5 Quality of Service Indication，PQI)、保证流比特率(Guaranteed Flow Bit Rate，GFBR)、最大流比特率(Maximum Flow Bit Rate，MFBR)、PC5LINK-聚合最大比特率(Aggregate Maximum Bit Rate，AMBR)、范围(Range)。即在PC5 QoS属性参数发生变化的情况下，收集所述基于PC5 QoS流计费的计费信息。
d)邻近服务链路的时间条件，所述邻近服务链路的时间条件用于表征在该邻近服务链路的生存周期内若满足设定时间就触发计费事件。即在ProSe UE满足邻近服务链路的时间条件的情况下，收集所述QoS流的计费信息。所述邻近服务链路例如层二链路。所述时间条件例如：数据时间失效(Expiry  of data time)。所述邻近服务链路的时间条件例如：每个层二链路的时间限制到期。具体的，链路的时间条件可以是链路建立10分钟，意味着在邻近服务链路建立10分钟之后触发获取计费信息，即计费是从链路建立10分钟之后开始的。
e)邻近服务链路的数据量条件，所述邻近服务链路的数据量条件用于表征在该邻近服务链路的生命周期内若满足设定数据量就触发计费事件。即在ProSe UE满足邻近服务链路的数据量条件的情况下，收集所述QoS流的计费信息。所述邻近服务链路例如层二链路。所述数据量条件例如：数据量失效(Expiry of data volume)。邻近服务链路的数据量条件例如：每个层二链路的数据量限制到期。具体的，链路的数据量条件可以是链路上传输的数据的数据量为10M，意味着在邻近链路建立之后，该链路上传输的数据的数据量达到10M之后触发获取计费信息，即计费是从链路上传输的数据的数据量达到10M之后开始的。
f)QoS流的时间条件，所述QoS流的时间条件用于表征在该QoS流的生存周期内若满足设定时间就触发计费事件。即在ProSe UE满足QoS流的时间条件的情况下，收集所述QoS流的计费信息。所述时间条件例如：Expiry of data time。所述QoS流的时间条件例如：每个QoS流的时间限制到期。
g)QoS流的数据量条件，所述QoS流的数据量条件用于表征在该QoS流的生存周期内若满足设定数据量就触发计费事件。即在ProSe UE满足QoS流的数据量条件的情况下，收集所述QoS流的计费信息。所述数据量条件例如：Expiry of data volume。所述QoS流的数据量条件例如：每个QoS流的数据量限制到期。
需要说明的是，f、g项所表示的含义与d、e所表示的含义相同。区别在于针对的对象不同，一个是针对QoS流，一个是针对链路。
可选地，在所述计费触发事件包括上述a)～g)中的多项时，包括上述至少两项。
具体地，所述配置信息可以包括以下至少一项或者多项：
1)根据所述计费信息生成使用信息报告的生成周期；
2)上报计费信息的上报周期；即所述用户设备上报QoS流的计费信息 的上报周期；
3)第一指示信息，所述第一指示信息用于指示是否上报基于QoS流的计费信息；
4)第二指示信息，所述第二指示信息用于指示是否上报接收数据的数据量；
5)第三指示信息，所述第三指示信息用于指示否上报发送数据的数据量。
该实施例中，可以由网络侧设备为UE配置或者由UE预配置：基于QoS流的计费信息的配置信息。所述配置信息可以包括以上一项或者多项。所述配置信息可以通过新增标志位指示相关信息内容。例如：所述UE根据所述用户设备生成使用信息报告的生成周期，收集并上报所述计费信息；在所述第一指示信息指示所述UE基于QoS流上报计费信息时，UE向网络侧设备上报所述计费信息；在所述第二指示信息指示UE上报接收数据的数据量时，UE可以在上报所述接收数据的数据量时同时上报所述计费信息；在所述第三指示信息指示UE上报发送数据的数据量时，UE可以在上报所述发送数据的数据量时同时上报所述计费信息。
作为一个可选实施例，所述用户设备收集所述QoS流的计费信息，可以参考所述配置信息。以所述用户设备的配置信息包括所述第一指示信息为例，在所述第一指示信息指示用户设备基于QoS流上报计费信息的情况下，所述用户设备基于计费触发事件，收集所述QoS流的计费信息，并将所述计费信息发送至网络侧设备。
所述用户设备基于QoS流的计费触发层级可以为基于QoS流的触发和/或基于链路的触发。
所述基于链路的触发例如：PC5上的层二链路相关的触发。所述层二链路相关的触发可以是指Layer-2 link的改变触发基于PC5 QoS流的计费，其中，Layer-2 link改变的情况下，层二链路内的QoS流也改变。
所述基于QoS流的触发例如：层二链路内PC5 QoS流相关的触发，即Layer-2 link内的QoS流改变触发所述基于PC5 QoS流的计费，可以是单独的QoS流改变触发所述基于PC5 QoS流的计费。
可选地，所述用户设备在将所述计费信息发送至所述网络侧设备时，可 以发送包含所述计费信息的使用信息报告，具体地，所述方法还包括：
在获取所述计费信息之后，按照配置信息中包含的生成使用信息报告的生成周期，生成包含所述计费信息的使用信息报告；
所述向网络侧设备发送所述计费信息，包括：按照配置信息中的上报周期，将所述使用信息报告发送给网络侧设备。
该实施例中，所述用户设备在获取到所述计费信息后，基于所述配置信息中的使用信息报告的生成周期，生成使用信息报告(Usage Information Report)，并以预定的上报周期上报所述使用信息报告，该使用信息报告中包括所述计费信息。
作为一个可选实施例，所述向网络侧设备发送所述计费信息，包括：
将所述计费信息发送至网络侧设备的计费触发功能CTF或者计费执行功能CEF，并由所述CTF或者所述CEF将所述计费信息转发给CHF；
其中，所述计费信息用于所述CHF对发生的所述邻近服务进行计费。。
该实施例中，用户设备在本地可以通过CTF(AMC)收集计费信息，在满足基于QoS流的计费信息上报条件时，将所述计费信息上报至网络侧设备的CTF(ADF)；所述网络侧设备的CTF(ADF)再将所述计费信息发送至CHF，由CHF生成计费账单。其中，CTF(ADF)功能模块可以合设在ProSe相关的NF中(如5G DDNMF)。
或者，用户设备在本地可以通过CTF(AMC)收集计费信息，在满足基于QoS流的计费信息上报条件时，将所述计费信息上报至网络侧设备的CEF；所述网络侧设备的CEF再将所述计费信息发送至CHF，由CHF生成计费账单。
所述用户设备可以通过Usage Information Report将所述计费信息上报到网络侧设备的CTF(ADF)，所述网络侧设备的CTF(ADF)可以通过Nchf接口利用Charging Data Request将所述计费信息发送至CHF。
可选地，将所述计费信息发送至网络侧设备的CEF，具体包括：
通过计费相关的网络功能NF服务，向所述网络侧设备的CEF发送所述计费信息；其中，所述计费信息可以由所述CEF向所述NF服务订阅。
该实施例中，CEF可以作为ProSe Service(例如5G DDNMF)的consumer 订阅相关服务，从不同的NF Service或者管理服务(Management Service)收集可能需要的计费信息。CEF可以向所述NF服务订阅计费信息(例如订阅usage information report通知)，用户设备在满足基于QoS流的计费信息上报条件时，收集计费信息，并将所述计费信息发送至NF Service，NF Service接收到所述计费信息后将所述计费信息发送至所述CEF；所述CEF通过Nchf接口将所述计费信息发送至CHF，由CHF生成计费账单。
具体地，所述QoS流的流信息可以包括以下至少一项或者多项：
a)QoS属性参数。例如PC5 QoS参数，PC5 QoS参数例如：PQI、GFBR、MFBR、PC5LINK-AMBR、Range。
b)QoS特征参数。例如PC5 QoS特征参数，所述PC5 QoS特征参数例如：资源类型、优先级、包延时预算、误包率、平均窗口、最大数据突发量等。
c)QoS流标识PFI(PC5 QoS Flow Identifier，PFI)；PFI即PC5 QoS流身份标识号(Identity document，ID)，用于标识一条QoS流，在中继(Relay)场景中Relay UE会做映射。
d)与PFI匹配的业务数据流的第一个数据包的传输时间；
e)与PFI匹配的业务数据流的最后一个数据包的传输时间；
f)QoS流发生的时间；
g)服务网络功能标识。
其中，用户设备可以直接在QoS属性参数或者所述QoS特征参数中上报PQI(即PC5 5QI，PC5接口的5G Qos标识)，或者转换成对应的5QI上报。即：所述PC5 QoS参数或者所述PC5 QoS特征参数中可以包含PQI；或者所述用户设备将PQI映射为5QI，将所述5QI携带在所述PC5 QoS参数或者所述PC5 QoS特征参数中。
需要说明的是，所述QoS流的流信息除包括上述一项或者多项信息内容外，还可以包括QoS流结束的时间。所述QoS流的流信息还可以包括其他计费相关信息，例如下表：
触发器 OC 该字段保存关闭QFI单元容器的原因
触发时间戳 OC 该字段保存触发器的时间戳
时间 OC 该字段保存使用时间量
总容积 OC 该字段保存上行和下行使用量.
上行使用量 OC 该字段保存上行使用量
下行使用量 OC 该字段保存下行使用量
本地序列号 M 该字段保存QFI数据容器序列号
具体地，所述链路信息可以包括以下至少一项或者多项：
a)源互联网协议(Internet Protocol，IP)地址；
b)目标IP地址；
c)中继IP地址；
d)邻近服务组(Group)的IP多播地址，例如ProSe组IP多播地址；
e)参与邻近服务的设备标识，例如：ProSe用户设备标识、中继用户设备标识；
f)邻近服务链路的链路标识，例如：ProSe层二组标识、ProSe目标层二标识。
该实施例中，所述链路信息可以包括Layer-2 ID、Layer-2 Group ID、中继UE ID等。在ProSe直接通信是IP类型时，还可以包含IP信息。
下面通过具体实施例说明所述计费方法的实现过程。
示例一：ProSe Direct Communication基于会话(Session)的计费方法。如图7所示，以QoS流为PC5 QoS flow为例，则UE基于PC5 QoS flow上报计费信息，具体地，包括：
步骤0、UE业务授权和参数配置，可以通过新增标志位，该标志位用于指示UE是否需要基于PC5 QoS flow上报计费信息，参数配置可以通过：
a)ME提供；
b)在UICC中配置；
c)ProSe应用服务器通过PCF和/或PC1参考点提供/更新；
d)由PCF提供/更新给UE；
步骤1、UE1和UE2发起直接通信请求；
步骤2、UE1和UE2发起相互认证过程，进行身份验证并建立安全关联。认证过程成功后，PC5上的层二安全链路建立，然后UE进行单播或多播或广播方式的直连通信；
步骤3、当UE确定满足基于PC5 QoS流的计费信息上报条件时，根据配置信息，UE触发计费信息的获取和上报过程；
可选地，所述UE是否满足计费信息上报条件根据所述配置信息确定。例如：所述配置信息包括所述用户设备生成使用信息报告的生成周期，则在UE达到所述生成周期时满足上报条件，上报收集的基于PC5 QoS流的计费信息；所述配置信息包括第一指示信息，且所述第一指示信息指示UE基于PC5 QoS流上报计费信息，则满足上报条件，所述UE上报收集的基于PC5 QoS流的计费信息；所述配置信息包括第二指示信息，且所述第二指示信息指示UE上报接收数据的数据量，则满足上报条件，UE在发送接收数据的数据量时携带所述基于PC5 QoS流的计费信息；所述配置信息包括第三指示信息，且所述第三指示信息指示UE上报发送数据的数据量，则满足上报条件，UE在发送发送数据的数据量时携带所述基于PC5 QoS流的计费信息。
步骤4、UE1和UE2分别上报包含计费信息的使用信息报告，即将使用信息报告发送至ProSe Service(CTF-ADF)；该消息应携带一个或多个所述PC5 QoS流的相关信息，以及相关的链路信息。所述PC5 QoS流的流信息以及所述链路信息在此不做赘述。
步骤5a、CTF(ADF)发送计费数据请求(初始)到CHF，并携带PC5 QoS流的流信息；
步骤5b、基于策略，CHF创建一个ProSe服务计费账单，并携带PC5 QoS流的流信息以及QoS流相关的链路信息；
步骤5c、CHF向NF(CTF)授予启动服务的授权，并返回计费数据响应消息(初始)。
步骤6、UE1和UE2之间持续进行ProSe直接通信(One-to-One direct traffic)。
步骤7、UE在满足基于PC5 QoS流的计费信息上报条件时，触发计费信息上报过程；
步骤8、UE上报包含计费信息的使用信息报告至CTF，使用信息报告中包括PC5 QoS流的流信息以及QoS流相关的链路信息；
步骤9a至步骤9c、与步骤5a至步骤5c类似，CTF(ADF)发送计费数据请求消息(更新)，CHF更新CDR，并回复计费数据响应消息(更新)；
步骤10、UE1向UE2发送断开连接请求消息；UE2回复断开连接响应消息，并删除与第二层链路关联的所有上下文数据；
步骤11、UE1接收到UE2的断开连接响应消息，触发计费信息上报过程；
步骤12、UE1发送包含计费信息的使用信息报告至NF(CTF)，并携带PC5 QoS流的流信息以及QoS流相关的链路信息；
步骤13a、CTF(ADF)发送计费数据请求消息(终止)到CHF，其中携带PC5 QoS流的流信息以及QoS流相关的链路信息；
步骤13b、基于策略，CHF创建一个ProSe服务计费账单，其中可以包含携带PC5 QoS流的流信息以及QoS流相关的链路信息；该步骤中的CDR为上报计费系统的最终账单，生成最终CDR后，可以关闭CDR；
步骤13c、CHF返回计费数据响应消息(终止)。
示例二：ProSe Direct Communication基于事件(Event)的计费方法。
基于事件的计费是一种事件后计费方式(Post Event Charging，PEC))，并且在业务结束后通过使用信息报告上报给网络侧设备的CTF(ADF)，并由ADF合并处理后通过计费数据请求消息上报给CHF，最终由CHF生成CDR，以所述QoS流为PC5 QoS flow为例，具体地，如图8所示，包括：
步骤0、UE业务授权和参数配置，可以新增标志位，用于指示UE是否上报PC5 QoS flow的计费信息；
步骤1、UE1和UE2发起直接通信请求；
步骤2、UE1和UE2发起相互认证过程，进行身份验证并建立安全关联。认证过程成功后，PC5上的层二安全链路建立，UE进行单播或多播或广播方式的直连通信；
步骤3、UE之间发起ProSe直接通信。
步骤4、UE1向UE2发送断开连接请求消息；UE2回复断开连接响应消息，并删除与第二层链路关联的所有上下文数据；
步骤5、UE1接收到UE2的断开连接响应消息，触发使用情况上报过程；
步骤6-7、UE1在与UE2的PC5通信过程中收集PC5上的QoS flow的流信息，并且在业务结束后，当UE确定满足基于PC5 QoS流的计费信息上报条件时，通过使用信息报告上报给网络侧设备的CTF，即ProSe Service(CTF-ADF)，所述使用信息报告携带PC5 QoS流的流信息以及QoS流相关的链路信息。
步骤8a-c、ADF通过计费数据请求消息(事件)上报给CHF，其中携带PC5 QoS流的流信息以及QoS流相关的链路信息。最终CHF生成计费账单信息CDRs，其中可以包含QoS相关计费信息；CHF向ADF发送计费数据响应消息(事件)。
示例三：ProSe Direct Communication基于Event的计费方法，通过CEF订阅计费信息，CEF可以作为ProSe Service(例如，5G DDNMF)的用户订阅相关服务，从不同的NF Service或者Management Service收集可能需要的计费信息。以所述QoS流为PC5 QoS flow为例，具体地，如图9所示，包括：
步骤1、CEF决定向计费相关的ProSe服务提供者(ProSe Service Provider)(如：5G DDNMF)订阅使用信息报告通知；
步骤2、CEF向ProSe Service Provider发起订阅请求；
步骤3、CEF接收到订阅响应；
步骤4、UE1和UE2发起直接通信请求；
步骤5、UE1和UE2发起相互认证过程，进行身份验证并建立安全关联。认证过程成功后，PC5上的层二安全链路建立，UE进行单播或多播或广播方式的直连通信；
步骤6、UE之间发起ProSe直接通信。
步骤7、UE1向UE2发送断开连接请求消息；UE2回复断开连接响应消息，并删除与第二层链路关联的所有上下文数据；
步骤8、UE1接收到UE2的断开连接响应消息，触发使用情况上报过程；
步骤9、UE1确定满足基于PC5 QoS流的计费信息上报条件时，触发计费信息上报；
步骤10、UE向ProSe Service Provider发送使用信息报告，携带PC5 QoS 流的流信息以及QoS流相关的链路信息；
步骤11、计费ProSe Service Provider通知CEF处理使用信息报告；
步骤12、CEF回复通知确认消息；
步骤13a、CEF向CHF发送计费数据请求消息，携带PC5 QoS流的流信息以及QoS流相关的链路信息；
步骤13b、CHF生成CDR；
步骤13c、CHF回复计费请求响应消息。
实施例四、ProSe Direct Communication中继UE(UE-Network relay)基于event计费。
L3中继架构(L3 relay architect)如图10所示。
远端UE(Remote UE)与ProSe中继UE之间通过PC5接口通讯；中继UE与5G接入网(New Generation Radio Access Network，NG-RAN)之间通过Uu接口通讯，5G核心网(5GC)与接入层(Access Stratum，AS)通过N6接口通讯。
以所述QoS流为PC5 QoS flow为例，具体地，如图11所示，包括：远端UE、ProSe中继UE、NG-RAN、接入和移动管理功能(Access and Mobility Management Function，AMF)、会话管理功能(Session Management Function，SMF)、用户面功能(User Plane Function，UPF)、ProSe服务CTF、CHF；其中，所述计费方法的实现过程包括：
步骤0a-b、ProSe中继UE的业务授权和配置；远端UE的业务授权和配置。可以新增是否需要上报QoS flow的计费信息标志位。
步骤1、中继UE建立PDU会话来中继，使用步骤0接收到的缺省PDU会话参数或预先配置的参数；
步骤2、根据步骤0的授权和配置，Remote UE执行ProSe发现流程；
步骤3、远端UE选择一个中继UE并且建立直接通信；
步骤4、IPv4地址/IPv6前缀分配；
步骤5、中继UE上报中继UE报告(例如：远端用户ID、远端UE信息)给SMF；
步骤6、当远端UE确定满足计费信息上报条件时，根据配置，UE触发 使用情况上报过程。触发层级和触发条件在此不做赘述。
步骤7、远端UE发送使用信息报告到中继UE；并由中继UE转发到网络侧CTF；携带所述PC5 QoS流的流信息以及QoS流相关的链路信息；
步骤8、当中继UE确定满足计费信息上报条件时，根据配置，UE触发使用情况上报过程；
步骤9、中继UE发送使用信息报告到网络侧ProSe服务CTF；
需要说明的是：步骤8、9可能发生在步骤6、7之前，具体顺序在此不做限定。
步骤10a、CTF(ADF)发送计费数据请求消息(终止)到CHF，并携带PC5QoS流的相关信息以及对应的链路信息；
步骤10b、基于策略，CHF创建CDR；
步骤10c、CHF返回计费数据响应消息(终止)。
本申请的实施例，UE获取基于QoS流的计费信息并上报至网络侧设备，由网络侧设备将所述计费信息上报给CHF进而完成计费。该方案可以基于ProSe的业务流量计费，能够满足ProSe中各种潜在垂直业务的计费场景。
如图12所示，本申请的实施例还提供一种计费方法，应用于网络侧设备，包括：
步骤121、网络侧设备获取用户设备发送的QoS流的计费信息，所述计费信息是基于所述用户设备提供邻近服务产生的；
步骤122、将所述计费信息发送至计费功能CHF；
其中，所述计费信息包括：QoS流的流信息。
该实施例中，用户设备收集基于QoS流的计费信息，并可以通过使用信息报告将所述计费信息发送至所述网络侧设备。可选地，在所述网络侧设备接收到所述计费信息后，可以根据所述计费信息生成计费请求消息，所述计费请求消息中包括所述计费信息，通过计费请求消息将所述计费信息发送至CHF，由CHF生成计费账单。可选地，网络侧设备可以配置用户设备是否需要基于QoS流上报计费信息。在所述用户设备需要基于QoS流上报计费信息时，所述UE收集并上报所述QoS流的计费信息。
本申请的实施例，UE获取QoS流的计费信息并上报至网络侧设备，所 述网络侧设备将所述计费信息上报给CHF进而完成计费。该方案可以基于ProSe的业务流量计费，能够满足ProSe中各种潜在垂直业务的计费场景。
可选地，在获取用户设备发送的QoS流的计费信息之前，所述方法还可以包括：为所述用户设备配置计费信息的配置信息，例如：所述配置信息可以为ProSe基于PC5 QoS流的计费配置信息。
具体地，所述配置信息可以包括以下至少一项或者多项：
根据所述计费信息生成使用信息报告的生成周期；
上报计费信息的上报周期；
第一指示信息，所述第一指示信息用于指示是否上报基于QoS流的计费信息；
第二指示信息，所述第二指示信息用于指示是否上报接收数据的数据量；
第三指示信息，所述第三指示信息用于指示否上报发送数据的数据量。
该实施例中，可以由网络侧设备为UE配置配置信息，所述配置信息可以包括以上一项或者多项，所述多项可以是指至少两项。所述UE可以根据所述配置信息，确定是否满足计费信息上报条件，在满足计费上报条件时，UE上的CTF(AMC)上报所述计费信息至网络侧设备。所述配置信息可以通过新增标志位指示UE是否上报基于QoS flow的计费信息。需要说明的是，所述配置信息还可以由所述用户设备预配置，例如在UICC中配置，在所述配置信息由所述用户设备预配置的情况下，可省略该为所述用户设备配置配置信息的步骤。其中，所述配置信息可以通过如下几种方式提供：
a)ME提供；
b)在UICC中配置；
c)ProSe应用服务器通过PCF和/或PC1参考点提供/更新；
d)由PCF提供/更新给UE。
需要说明的是，UE还可以基于计费触发事件，获取QoS流的计费信息，所述计费触发事件在此不做赘述。
具体地，所述用户设备基于QoS流的计费触发层级可以为基于QoS流的触发和/或基于链路的触发。
所述基于链路的触发例如：PC5上的层二链路相关的触发；所述层二链 路相关的触发可以是指Layer-2 link的改变触发基于PC5 QoS流的计费，其中，Layer-2 link改变的情况下，层二链路内的QoS流也改变。
所述基于QoS流的触发例如：层二链路内PC5 QoS流相关的触发。即Layer-2 link内的QoS流改变触发所述基于PC5 QoS流的计费，可以是单独的QoS流改变触发所述基于PC5 QoS流的计费。
可选地，所述获取用户设备发送的QoS流的计费信息，包括：获取所述用户设备按照计费信息的上报周期发送的使用信息报告，所述使用信息报告包含所述计费信息。
该实施例中，所述网络侧设备可以为UE配置计费信息的配置信息，所述配置信息也可以为UE预配置，所述配置信息可以包括UE上报上使用信息报告的上报周期，所述使用信息报告根据所述计费信息生成，UE按照所述上报周期将所述使用信息报告发送至所述网络侧设备。
作为一个可选实施例，所述获取用户设备发送的计费信息，可以包括：
接收用户设备发送至计费触发功能CTF或者计费执行功能CEF的计费信息；
所述将所述计费信息发送至计费功能CHF，包括：通过所述CTF或者所述CEF，利用计费功能服务化Nchf接口将所述计费信息发送至所述CHF。其中，所述计费信息用于所述CHF对发生的所述邻近服务进行计费。
该实施例中，用户设备在本地可以通过CTF(AMC)收集QoS的计费信息，在满足基于QoS流的计费信息上报条件时，将所述计费信息上报至网络侧设备的CTF(ADF)；所述网络侧设备的CTF(ADF)再将所述计费信息发送至CHF，由CHF生成计费账单。其中，CTF(ADF)功能模块可以合设在ProSe相关的NF中(如5G DDNMF)。
或者，用户设备在本地可以通过CTF(AMC)收集QoS的计费信息，在满足基于QoS流的计费信息上报条件时，将所述计费信息上报至网络侧设备的CEF；所述网络侧设备的CEF再将所述计费信息发送至CHF，由CHF生成计费账单。
所述用户设备可以通过Usage Information Report将所述计费信息上报到网络侧设备的CTF(ADF)或者CEF，所述网络侧设备的CTF(ADF)CEF 可以通过Nchf接口利用Charging Data Request将所述计费信息发送至CHF，使CHF根据所述计费信息生成计费账单。
作为一个可选实施例，在接收用户设备发送至计费执行功能CEF的计费信息之前，所述方法还可以包括：
通过CEF向计费相关的NF服务订阅计费信息；
所述接收用户设备发送至计费执行功能CEF的计费信息，包括：接收NF服务发送至所述CEF的所述计费信息；其中，所述计费信息由所述用户设备发送至所述NF服务。
该实施例中，CEF可以作为ProSe Service(例如5G DDNMF)的consumer订阅相关服务，从不同的NF Service或者Management Service收集可能需要的计费信息。CEF可以向所述NF服务订阅计费信息(例如订阅usage information report通知)，用户设备在满足ProSe基于QoS流计费的计费信息上报条件时，收集计费信息，并将所述计费信息发送至NF Service，NF Service接收到所述计费信息后将所述计费信息发送至所述CEF；所述CEF通过Nchf接口将所述计费信息发送至CHF，由CHF生成计费账单。
具体地，所述QoS流的流信息可以包括以下至少一项或者多项：
a)QoS属性参数。例如：PC5 QoS参数，PC5 QoS参数例如：PQI、GFBR、MFBR、PC5LINK-AMBR、Range。
b)QoS特征参数。例如：PC5 QoS特征参数；所述PC5 QoS特征参数例如：资源类型、优先级、包延时预算、误包率、平均窗口、最大数据突发量等。
c)PFI；PFI即PC5 QoS流ID，用于标识一条QoS流，在Relay场景中Relay UE会做映射。
d)与PFI匹配的业务数据流的第一个数据包的传输时间；
e)与PFI匹配的业务数据流的最后一个数据包的传输时间；
f)QoS流发生的时间；
g)服务网络功能标识。
其中，用户设备可以直接在QoS参数或者所述QoS特征参数中上报PQI，或者转换成对应的5QI上报。即：所述QoS参数或者所述QoS特征参数中可 以包含PQI；或者所述用户设备将PQI映射为5QI，将所述5QI携带在所述PC5 QoS参数或者所述PC5 QoS特征参数中。
需要说明的是，所述QoS流的流信息除包括上述一项或者多项信息内容外，还可以包括其他计费相关信息，在此不做限定。
具体地，所述计费信息还包含：与所述QoS流关联的链路信息，其中，所述链路信息可以包括以下至少一项或者多项：
a)源IP地址；
b)目标IP地址；
c)中继IP地址；
d)邻近服务组的IP多播地址，例如ProSe组IP多播地址；
e)参与邻近服务的设备标识，例如ProSe用户设备到中继用户设备标识；
f)邻近服务链路的链路标识，例如：ProSe层二组标识、ProSe目标层二标识。
该实施例中，所述链路信息可以包括Layer-2 ID、Layer-2 Group ID、中继UE ID等。在ProSe直接通信是IP类型时，还可以包含IP信息。
本申请实施例的所述计费方法的实现过程如图7-图11所示，在此不做赘述。需要说明的是，本申请应用于网络侧设备的计费方法的实施例，能够实现上述应用于用户设备的计费方法实施例中网络侧设备实现的所有过程，在此不做赘述。
本申请的实施例，UE获取QoS流的计费信息并上报至网络侧设备，所述网络侧设备将所述计费信息上报给CHF进而完成计费。该方案可以基于ProSe的业务流量计费，能够满足ProSe中各种潜在垂直业务的计费场景。
以上实施例就本申请的定位方法做出介绍，下面本实施例将结合附图对其对应的装置做进一步说明。
具体地，如图13所示，本申请实施例的计费装置1300，应用于用户设备，包括：
第一获取单元1310，用于获取服务质量QoS流的计费信息，所述计费信息是基于所述用户设备提供邻近服务产生的；
第一发送单元1320，用于向网络侧设备发送所述计费信息；
其中，所述计费信息包括：所述QoS流的流信息。
可选地，所述第一获取单元1310具体用于：
基于计费触发事件，获取QoS流的计费信息；
或者；
根据配置信息，触发获取QoS流的计费信息。
可选地，所述计费触发事件包括以下至少一项或者多项：
邻近服务链路建立；
QoS流建立；
QoS属性参数发生变化；
邻近服务链路的时间条件，所述邻近服务链路的时间条件用于表征在该邻近服务链路的生存周期内若满足设定时间就触发计费事件；
邻近服务链路的数据量条件，所述邻近服务链路的数据量条件用于表征在该邻近服务链路的生命周期内若满足设定数据量就触发计费事件；
QoS流的时间条件，所述QoS流的时间条件用于表征在该QoS流的生存周期内若满足设定时间就触发计费事件；
QoS流的数据量条件，所述QoS流的数据量条件用于表征在该QoS流的生存周期内若满足设定数据量就触发计费事件。
可选地，所述配置信息包括以下至少一项或者多项：
根据所述计费信息生成使用信息报告的生成周期；
上报计费信息的上报周期；
第一指示信息，所述第一指示信息用于指示是否上报基于QoS流的计费信息；
第二指示信息，所述第二指示信息用于指示是否上报接收数据的数据量；
第三指示信息，所述第三指示信息用于指示否上报发送数据的数据量。
可选地，所述装置还包括：
报告生成单元，用于在获取所述计费信息之后，按照配置信息中包含的生成使用信息报告的生成周期，生成包含所述计费信息的使用信息报告；
所述第一发送单元1320具体用于：按照配置信息中的上报周期，将所述使用信息报告发送给网络侧设备。
可选地，所述第一发送单元1320包括：
第一发送子单元，用于将所述计费信息发送至网络侧设备的计费触发功能CTF或者计费执行功能CEF，并由所述CTF或者所述CEF将所述计费信息转发给CHF；
其中，所述计费信息用于所述CHF对发生的所述邻近服务进行计费。
可选地，所述第一发送子单元具体用于：通过计费相关的网络功能NF服务，向所述网络侧设备的CEF发送所述计费信息。
可选地，所述QoS流的流信息包括以下至少一项或者多项：
QoS参数；
QoS特征参数；
QoS流标识PFI；
与PFI匹配的业务数据流的第一个数据传输包的时间；
与PFI匹配的业务数据流的最后一个数据传输包的时间；
QoS流发生的时间；
服务网络功能标识。
可选地，所述计费信息还包括与所述QoS流关联的链路信息，其中，所述链路信息包括以下至少一项或者多项：
源IP地址；
目标IP地址；
中继IP地址；
邻近服务组的IP多播地址；
参与邻近服务的设备标识；
邻近服务链路的链路标识。
本申请的实施例，UE获取QoS流的计费信息并上报至网络侧设备，由网络侧设备将所述计费信息上报给CHF进而完成计费。该方案可以基于ProSe的业务流量计费，能够满足ProSe中各种潜在垂直业务的计费场景。
在此需要说明的是，本申请实施例提供的上述装置，能够实现上述应用于用户设备的方法实施例所实现的所有方法步骤，且能够达到相同的技术效果，在此不再对本实施例中与方法实施例相同的部分及有益效果进行具体赘 述。
如图14所示，本申请实施例提供的计费装置1400，应用于网络侧设备，包括：
第二获取单元1410，用于获取用户设备发送的QoS流的计费信息，所述计费信息是基于所述用户设备提供邻近服务产生的；
第二发送单元1420，用于将所述计费信息发送至计费功能CHF；
其中，所述计费信息包括：所述QoS流的流信息。
可选地，所示装置还包括：
配置单元，用于为所述用户设备配置计费信息的配置信息。
可选地，所述配置信息包括以下至少一项或者多项：
根据所述计费信息生成使用信息报告的生成周期；
上报计费信息的上报周期；
第一指示信息，所述第一指示信息用于指示是否上报基于QoS流的计费信息；
第二指示信息，所述第二指示信息用于指示是否上报接收数据的数据量；
第三指示信息，所述第三指示信息用于指示否上报发送数据的数据量。
可选地，所述第二获取单元1410具体用于：获取所述用户设备按照计费信息的上报周期发送的使用信息报告，所述使用信息报告包含所述计费信息。
可选地，所述第二获取单元1410包括：
第一接收子单元，用于接收用户设备发送至计费触发功能CTF或者计费执行功能CEF的计费信息；
所述第二发送单元1420具体用于：通过所述CTF或者所述CEF，利用计费功能服务化Nchf接口将所述计费信息发送至所述CHF；
其中，所述计费信息用于所述CHF对发生的所述邻近服务进行计费。
可选地，所述第一接收子单元具体用于：接收NF服务发送至所述CEF的所述计费信息；其中，所述计费信息由所述用户设备发送至所述NF服务。
可选地，所述QoS流的流信息包括以下至少一项或者多项：
QoS属性参数；
QoS特征参数；
PFI；
与PFI匹配的业务数据流的第一个数据包的传输时间；
与PFI匹配的业务数据流的最后一个数据包的传输时间；
QoS流发生的时间；
服务网络功能标识。
可选地，所述计费信息还包含所述QoS流关联的链路信息，其中，所述链路信息包括以下至少一项或者多项：
源IP地址；
目标IP地址；
中继IP地址；
邻近服务组的IP多播地址；
参与邻近服务的设备标识；
邻近服务链路的链路标识。
本申请的实施例，UE获取QoS流的计费信息并上报至网络侧设备，所述网络侧设备将所述计费信息上报给CHF进而完成计费。该方案可以基于ProSe的业务流量计费，能够满足ProSe中各种潜在垂直业务的计费场景。
在此需要说明的是，本申请实施例提供的上述装置，能够实现上述应用于网络侧设备的方法实施例所实现的所有方法步骤，且能够达到相同的技术效果，在此不再对本实施例中与方法实施例相同的部分及有益效果进行具体赘述。
需要说明的是，本申请实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个处理器可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对相关技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个 存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)或处理器(processor)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
如图15所示，本申请的实施例还提供了一种用户设备，包括：存储器1520、收发机1500、处理器1510；其中，存储器1520，用于存储计算机程序；收发机1500，用于在所述处理器1510的控制下收发数据；处理器1510，用于读取所述存储器中的计算机程序并执行以下操作：
获取服务质量QoS流的计费信息，所述计费信息是基于所述用户设备提供邻近服务产生的；
所述收发机用于：向网络侧设备发送所述计费信息；
其中，所述计费信息包括：所述QoS流的流信息。
可选地，所述处理器1510用于读取所述存储器中的计算机程序并执行以下操作：
基于计费触发事件，获取QoS流的计费信息；
或者；
根据配置信息，触发获取QoS流的计费信息。
可选地，所述计费触发事件包括以下至少一项或者多项：
邻近服务链路建立；
QoS流建立；
QoS属性参数发生变化；
邻近服务链路的时间条件，所述邻近服务链路的时间条件用于表征在该邻近服务链路的生存周期内若满足设定时间就触发计费事件；
邻近服务链路的数据量条件，所述邻近服务链路的数据量条件用于表征在该邻近服务链路的生命周期内若满足设定数据量就触发计费事件；
QoS流的时间条件，所述QoS流的时间条件用于表征在该QoS流的生存周期内若满足设定时间就触发计费事件；
QoS流的数据量条件，所述QoS流的数据量条件用于表征在该QoS流的 生存周期内若满足设定数据量就触发计费事件。
可选地，所述配置信息包括以下至少一项或者多项：
根据所述计费信息生成使用信息报告的生成周期；
上报计费信息的上报周期；
第一指示信息，所述第一指示信息用于指示是否上报基于QoS流的计费信息；
第二指示信息，所述第二指示信息用于指示是否上报接收数据的数据量；
第三指示信息，所述第三指示信息用于指示否上报发送数据的数据量。
可选地，所述处理器还用于读取所述存储器中的计算机程序并执行以下操作：
在获取所述计费信息之后，按照配置信息中包含的生成使用信息报告的生成周期，生成包含所述计费信息的使用信息报告；
所述收发机向网络侧设备发送所述计费信息，包括：
按照配置信息中的上报周期，将所述使用信息报告发送给网络侧设备。
可选地，所述收发机向网络侧设备发送所述计费信息，包括：
将所述计费信息发送至网络侧设备的计费触发功能CTF或者计费执行功能CEF，并由所述CTF或者所述CEF将所述计费信息转发给CHF；
其中，所述计费信息用于所述CHF对发生的所述邻近服务进行计费。
可选地，所述收发机将所述计费信息发送至网络侧设备的CEF，具体包括：
通过计费相关的网络功能NF服务，向所述网络侧设备的CEF发送所述计费信息。
可选地，所述QoS流的流信息包括以下至少一项或者多项：
QoS参数；
QoS特征参数；
QoS流标识PFI；
与PFI匹配的业务数据流的第一个数据传输包的时间；
与PFI匹配的业务数据流的最后一个数据传输包的时间；
QoS流发生的时间；
服务网络功能标识。
可选地，所述计费信息还包含所述QoS流关联的链路信息，其中，所述链路信息包括以下至少一项或者多项：
源IP地址；
目标IP地址；
中继IP地址；
邻近服务组的IP多播地址；
参与邻近服务的设备标识；
邻近服务链路的链路标识。
本申请的实施例，UE获取QoS流的计费信息并上报至网络侧设备，由网络侧设备将所述计费信息上报给CHF进而完成计费。该方案可以基于ProSe的业务流量计费，能够满足ProSe中各种潜在垂直业务的计费场景。
需要说明的是，在图15中，总线架构可以包括任意数量的互联的总线和桥，具体由处理器1510代表的一个或多个处理器和存储器1520代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。收发机1500可以是多个元件，即包括发送机和收发机，提供用于在传输介质上与各种其他装置通信的单元。针对不同的用户设备，用户接口1530还可以是能够外接内接需要设备的接口，连接的设备包括但不限于小键盘、显示器、扬声器、麦克风、操纵杆等。处理器1510负责管理总线架构和通常的处理，存储器1520可以存储处理器510在执行操作时所使用的数据。
可选地，处理器1510可以是中央处理器(Central Processing Unit，CPU)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现场可编程门阵列(Field－Programmable Gate Array，FPGA)或复杂可编程逻辑器件(Complex Programmable Logic Device，CPLD)，处理器也可以采用多核架构。
处理器通过调用存储器存储的计算机程序，用于按照获得的可执行指令执行本申请实施例提供的任一所述方法。处理器与存储器也可以物理上分开布置。
在此需要说明的是，本申请实施例提供的上述用户设备，能够实现上述应用于用户设备的方法实施例所实现的所有方法步骤，且能够达到相同的技术效果，在此不再对本实施例中与方法实施例相同的部分及有益效果进行具体赘述。
本申请实施例涉及的用户设备，可以是指向用户提供语音和/或数据连通性的设备，具有无线连接功能的手持式设备、或连接到无线调制解调器的其他处理设备等。所述用户设备如终端设备，包括无线终端设备，无线终端设备可以经无线接入网(Radio Access Network，RAN)与一个或多个核心网(Core Network，CN)进行通信，无线终端设备可以是移动终端设备，如移动电话(或称为“蜂窝”电话)和具有移动终端设备的计算机，例如，可以是便携式、袖珍式、手持式、计算机内置的或者车载的移动装置，它们与无线接入网交换语言和/或数据。例如，个人通信业务(Personal Communication Service，PCS)电话、无绳电话、会话发起协议(Session Initiated Protocol，SIP)话机、无线本地环路(Wireless Local Loop，WLL)站、个人数字助理(Personal Digital Assistant，PDA)等设备。无线终端设备也可以称为系统、订户单元(subscriber unit)、订户站(subscriber station)，移动站(mobile station)、移动台(mobile)、远程站(remote station)、接入点(access point)、远程终端设备(remote terminal)、接入终端设备(access terminal)、用户终端设备(user terminal)、用户代理(user agent)、用户装置(user device)，本申请实施例中并不限定。
如图16所示，本申请实施例还提供一种网络侧设备，包括：存储器1620、收发机1600、处理器1610；其中，存储器1620，用于存储计算机程序；收发机1600，用于在所述处理器1610的控制下收发数据；
所述收发机1600用于执行以下操作：获取用户设备发送的QoS流的计费信息，所述计费信息是基于所述用户设备提供邻近服务产生的；
将所述计费信息发送至计费功能CHF；
其中，所述计费信息包括：所述QoS流的流信息和/或与所述QoS流关联的链路信息。
可选地，所述处理器1610用于读取所述存储器中的计算机程序并执行以 下操作：
为所述用户设备配置计费信息的配置信息。
可选地，所述配置信息包括以下至少一项或者多项：
根据所述计费信息生成使用信息报告的生成周期；
上报计费信息的上报周期；
第一指示信息，所述第一指示信息用于指示是否上报基于QoS流的计费信息；
第二指示信息，所述第二指示信息用于指示是否上报接收数据的数据量；
第三指示信息，所述第三指示信息用于指示否上报发送数据的数据量。
可选地，所述收发机获取用户设备发送的QoS流的计费信息，包括：
获取所述用户设备按照计费信息的上报周期发送的使用信息报告，所述使用信息报告包含所述计费信息。
可选地，所述收发机获取用户设备发送的计费信息时，具体用于：
接收用户设备发送至计费触发功能CTF或者计费执行功能CEF的计费信息；
所述收发机将所述计费信息发送至计费功能CHF，包括：
通过所述CTF或者所述CEF，利用计费功能服务化Nchf接口将所述计费信息发送至所述CHF；
其中，所述计费信息用于所述CHF对发生的所述邻近服务进行计费。
可选地，所述收发机接收用户设备发送至计费执行功能CEF的计费信息，包括：
接收NF服务发送至所述CEF的所述计费信息；其中，所述计费信息由所述用户设备发送至所述NF服务。
可选地，所述QoS流的流信息包括以下至少一项或者多项：
QoS参数；
QoS特征参数；
PFI；
与PFI匹配的业务数据流的第一个数据传输包的时间；
与PFI匹配的业务数据流的最后一个数据传输包的时间；
QoS流发生的时间；
服务网络功能标识。
可选地，所述计费信息还包含所述QoS流关联的链路信息，其中，所述链路信息包括以下至少一项或者多项：
源IP地址；
目标IP地址；
中继IP地址；
邻近服务组的IP多播地址；
参与邻近服务的设备标识；
邻近服务链路的链路标识。
本申请的实施例，UE获取QoS流的计费信息并上报至网络侧设备，所述网络侧设备将所述计费信息上报给CHF进而完成计费。该方案可以基于ProSe的业务流量计费，能够满足ProSe中各种潜在垂直业务的计费场景。
其中，在图16中，总线架构可以包括任意数量的互联的总线和桥，具体由处理器1610代表的一个或多个处理器和存储器1620代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。收发机1600可以是多个元件，即包括发送机和收发机，提供用于在传输介质上与各种其他装置通信的单元。处理器1610负责管理总线架构和通常的处理，存储器1620可以存储处理器1610在执行操作时所使用的数据。
处理器1610可以是中央处理器(Central Processing Unit，CPU)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现场可编程门阵列(Field－Programmable Gate Array，FPGA)或复杂可编程逻辑器件(Complex Programmable Logic Device，CPLD)，处理器也可以采用多核架构。
在此需要说明的是，本申请实施例提供的上述网络侧设备，能够实现上述应用于网络侧设备的方法实施例所实现的所有方法步骤，且能够达到相同的技术效果，在此不再对本实施例中与方法实施例相同的部分及有益效果进行具体赘述。
本申请实施例涉及的网络侧设备例如计费架构中的核心网域(CN Domain)，也可以为具有分布式CTF功能模块的计费架构中的服务网络(Service NE)，在此不做限定。
另外，本申请具体实施例还提供一种处理器可读存储介质，其上存储有计算机程序，其中，该程序被处理器执行时实现如上述计费方法的步骤。且能达到相同的技术效果，为避免重复，这里不再赘述。其中，所述可读存储介质可以是处理器能够存取的任何可用介质或数据存储设备，包括但不限于磁性存储器(例如软盘、硬盘、磁带、磁光盘(Magneto-Optical Disk，MO)等)、光学存储器(例如光盘(Compact Disk，CD)、数字视频光盘(Digital Versatile Disc，DVD)、蓝光光碟(Blu-ray Disc，BD)、高清通用光盘(High-Definition Versatile Disc，HVD)等)、以及半导体存储器(例如只读存储器(Read-Only Memory，ROM)、可擦除可编程只读存储器(Erasable Programmable ROM，EPROM)、带电可擦可编程只读存储器(Electrically EPROM，EEPROM)、非易失性存储器(NAND FLASH)、固态硬盘(Solid State Disk或Solid State Drive，SSD))等。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器和光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机可执行指令实现流程图和/或方框图中的每一个流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机可执行指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图中的一个流程或多个流程和/或方框图中的一个方框或多个方框中指定的功能的装置。
这些处理器可执行指令也可存储在能引导计算机或其他可编程数据处理 设备以特定方式工作的处理器可读存储器中，使得存储在该处理器可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图的一个流程或多个流程和/或方框图的一个方框或多个方框中指定的功能。
这些处理器可执行指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图的一个流程或多个流程和/或方框图的一个方框或多个方框中指定的功能的步骤。
需要说明的是，应理解以上各个模块的划分仅仅是一种逻辑功能的划分，实际实现时可以全部或部分集成到一个物理实体上，也可以物理上分开。且这些模块可以全部以软件通过处理元件调用的形式实现；也可以全部以硬件的形式实现；还可以部分模块通过处理元件调用软件的形式实现，部分模块通过硬件的形式实现。例如，确定模块可以为单独设立的处理元件，也可以集成在上述装置的某一个芯片中实现，此外，也可以以程序代码的形式存储于上述装置的存储器中，由上述装置的某一个处理元件调用并执行以上确定模块的功能。其它模块的实现与之类似。此外这些模块全部或部分可以集成在一起，也可以独立实现。这里所述的处理元件可以是一种集成电路，具有信号的处理能力。在实现过程中，上述方法的各步骤或以上各个模块可以通过处理器元件中的硬件的集成逻辑电路或者软件形式的指令完成。
例如，各个模块、单元、子单元或子模块可以是被配置成实施以上方法的一个或多个集成电路，例如：一个或多个特定集成电路(Application Specific Integrated Circuit，ASIC)，或，一个或多个微处理器(digital signal processor，DSP)，或，一个或者多个现场可编程门阵列(Field Programmable Gate Array，FPGA)等。再如，当以上某个模块通过处理元件调度程序代码的形式实现时，该处理元件可以是通用处理器，例如中央处理器(Central Processing Unit，CPU)或其它可以调用程序代码的处理器。再如，这些模块可以集成在一起，以片上系统(system-on-a-chip，SOC)的形式实现。
本申请的说明书和权利要求书中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的 数据在适当情况下可以互换，以便这里描述的本申请的实施例，例如除了在这里图示或描述的那些以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。此外，说明书以及权利要求中使用“和/或”表示所连接对象的至少其中之一，例如A和/或B和/或C，表示包含单独A，单独B，单独C，以及A和B都存在，B和C都存在，A和C都存在，以及A、B和C都存在的7种情况。类似地，本说明书以及权利要求中使用“A和B中的至少一个”应理解为“单独A，单独B，或A和B都存在”。
显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (27)

  1. 一种计费方法，包括：
    用户设备获取服务质量QoS流的计费信息，所述计费信息是基于所述用户设备提供邻近服务产生的；
    向网络侧设备发送所述计费信息；
    其中，所述计费信息包括：所述QoS流的流信息。
  2. 根据权利要求1所述的方法，其中，所述获取服务质量QoS流的计费信息，包括：
    基于计费触发事件，获取QoS流的计费信息；
    或者；
    根据配置信息，触发获取QoS流的计费信息。
  3. 根据权利要求2所述的方法，其中，所述计费触发事件包括以下至少一项或者多项：
    邻近服务链路建立；
    QoS流建立；
    QoS属性参数发生变化；
    邻近服务链路的时间条件，所述邻近服务链路的时间条件用于表征在该邻近服务链路的生存周期内若满足设定时间就触发计费事件；
    邻近服务链路的数据量条件，所述邻近服务链路的数据量条件用于表征在该邻近服务链路的生命周期内若满足设定数据量就触发计费事件；
    QoS流的时间条件，所述QoS流的时间条件用于表征在该QoS流的生存周期内若满足设定时间就触发计费事件；
    QoS流的数据量条件，所述QoS流的数据量条件用于表征在该QoS流的生存周期内若满足设定数据量就触发计费事件。
  4. 根据权利要求2所述的方法，其中，所述配置信息包括以下至少一项或者多项：
    根据所述计费信息生成使用信息报告的生成周期；
    上报计费信息的上报周期；
    第一指示信息，所述第一指示信息用于指示是否上报基于QoS流的计费信息；
    第二指示信息，所述第二指示信息用于指示是否上报接收数据的数据量；
    第三指示信息，所述第三指示信息用于指示否上报发送数据的数据量。
  5. 根据权利要求1所述的方法，其中，所述方法还包括：
    在获取所述计费信息之后，按照配置信息中包含的生成使用信息报告的生成周期，生成包含所述计费信息的使用信息报告；
    所述向网络侧设备发送所述计费信息，包括：
    按照配置信息中的上报周期，将所述使用信息报告发送给网络侧设备。
  6. 根据权利要求1所述的方法，其中，所述向网络侧设备发送所述计费信息，包括：
    将所述计费信息发送至网络侧设备的计费触发功能CTF或者计费执行功能CEF，并由所述CTF或者所述CEF将所述计费信息转发给CHF；
    其中，所述计费信息用于所述CHF对发生的所述邻近服务进行计费。
  7. 根据权利要求6所述的方法，其中，将所述计费信息发送至网络侧设备的CEF，具体包括：
    通过计费相关的网络功能NF服务，向所述网络侧设备的CEF发送所述计费信息。
  8. 根据权利要求1所述的方法，其中，所述QoS流的流信息包括以下至少一项或者多项：
    QoS属性参数；
    QoS特征参数；
    QoS流标识PFI；
    与PFI匹配的业务数据流的第一个数据包的传输时间；
    与PFI匹配的业务数据流的最后一个数据包的传输时间；
    QoS流发生的时间；
    服务网络功能标识。
  9. 根据权利要求1所述的方法，其中，所述计费信息还包括与所述QoS流关联的链路信息，其中，所述链路信息包括以下至少一项或者多项：
    源IP地址；
    目标IP地址；
    中继IP地址；
    邻近服务组的IP多播地址；
    参与邻近服务的设备标识；
    邻近服务链路的链路标识。
  10. 一种计费方法，包括：
    网络侧设备获取用户设备发送的QoS流的计费信息，所述计费信息是基于所述用户设备提供邻近服务产生的；
    将所述计费信息发送至计费功能CHF；
    其中，所述计费信息包括：所述QoS流的流信息。
  11. 根据权利要求10所述的方法，其中，在获取用户设备发送的QoS流的计费信息之前，所述方法还包括：
    为所述用户设备配置与计费信息相关的配置信息。
  12. 根据权利要求11所述的方法，其中，所述配置信息包括以下至少一项或者多项：
    根据所述计费信息生成使用信息报告的生成周期；
    上报计费信息的上报周期；
    第一指示信息，所述第一指示信息用于指示是否上报基于QoS流的计费信息；
    第二指示信息，所述第二指示信息用于指示是否上报接收数据的数据量；
    第三指示信息，所述第三指示信息用于指示否上报发送数据的数据量。
  13. 根据权利要求10所述的方法，其中，所述获取用户设备发送的QoS流的计费信息，包括：
    获取所述用户设备按照计费信息的上报周期发送的使用信息报告，所述使用信息报告包含所述计费信息。
  14. 根据权利要求10所述的方法，其中，所述将所述计费信息发送至计费功能CHF，包括：
    通过计费触发功能CTF或者计费执行功能CEF，利用计费功能服务化 Nchf接口将所述计费信息发送至所述CHF；
    其中，所述计费信息用于所述CHF对发生的所述邻近服务进行计费。
  15. 根据权利要求10所述的方法，其中，所述QoS流的流信息包括以下至少一项或者多项：
    QoS参数；
    QoS特征参数；
    PFI；
    与PFI匹配的业务数据流的第一个数据传输包的时间；
    与PFI匹配的业务数据流的最后一个数据传输包的时间；
    QoS流发生的时间；
    服务网络功能标识。
  16. 一种用户设备，包括：存储器，收发机，处理器：
    存储器，用于存储计算机程序；收发机，用于在所述处理器的控制下收发数据；处理器，用于读取所述存储器中的计算机程序并执行以下操作：
    获取服务质量QoS流的计费信息，所述计费信息是基于所述用户设备提供邻近服务产生的；
    所述收发机用于：向网络侧设备发送所述计费信息；
    其中，所述计费信息包括：所述QoS流的流信息。
  17. 根据权利要求16所述的用户设备，其中，所述处理器用于读取所述存储器中的计算机程序并执行以下操作：
    基于计费触发事件，获取QoS流的计费信息；
    或者；
    根据配置信息，触发获取QoS流的计费信息。
  18. 根据权利要求17所述的用户设备，其中，所述计费触发事件包括以下至少一项或者多项：
    邻近服务链路建立；
    QoS流建立；
    QoS属性参数发生变化；
    邻近服务链路的时间条件，所述邻近服务链路的时间条件用于表征在该 邻近服务链路的生存周期内若满足设定时间就触发计费事件；
    邻近服务链路的数据量条件，所述邻近服务链路的数据量条件用于表征在该邻近服务链路的生命周期内若满足设定数据量就触发计费事件；
    QoS流的时间条件，所述QoS流的时间条件用于表征在该QoS流的生存周期内若满足设定时间就触发计费事件；
    QoS流的数据量条件，所述QoS流的数据量条件用于表征在该QoS流的生存周期内若满足设定数据量就触发计费事件。
  19. 根据权利要求17所述的用户设备，其中，所述配置信息包括以下至少一项或者多项：
    根据所述计费信息生成使用信息报告的生成周期；
    上报计费信息的上报周期；
    第一指示信息，所述第一指示信息用于指示是否上报基于QoS流的计费信息；
    第二指示信息，所述第二指示信息用于指示是否上报接收数据的数据量；
    第三指示信息，所述第三指示信息用于指示否上报发送数据的数据量。
  20. 根据权利要求16所述的用户设备，其中，所述处理器还用于读取所述存储器中的计算机程序并执行以下操作：
    在获取所述计费信息之后，按照配置信息中包含的生成使用信息报告的生成周期，生成包含所述计费信息的使用信息报告；
    所述收发机向网络侧设备发送所述计费信息，包括：
    按照配置信息中的上报周期，将所述使用信息报告发送给网络侧设备。
  21. 根据权利要求16所述的用户设备，其中，所述收发机向网络侧设备发送所述计费信息，包括：
    将所述计费信息发送至网络侧设备的计费触发功能CTF或者计费执行功能CEF，并由所述CTF或者所述CEF将所述计费信息转发给CHF；
    其中，所述计费信息用于所述CHF对发生的所述邻近服务进行计费。
  22. 根据权利要求16所述的用户设备，其中，所述QoS流的流信息包括以下至少一项或者多项：
    QoS属性参数；
    QoS特征参数；
    QoS流标识PFI；
    与PFI匹配的业务数据流的第一个数据包的传输时间；
    与PFI匹配的业务数据流的最后一个数据包的传输时间；
    QoS流发生的时间；
    服务网络功能标识。
  23. 根据权利要求16所述的用户设备，其中，所述计费信息还包括与所述QoS流关联的链路信息，其中，所述链路信息包括以下至少一项或者多项：
    源IP地址；
    目标IP地址；
    中继IP地址；
    邻近服务组的IP多播地址；
    参与邻近服务的设备标识；
    邻近服务链路的链路标识。
  24. 一种网络侧设备，包括：存储器，收发机，处理器：
    存储器，用于存储计算机程序；收发机，用于在所述处理器的控制下收发数据；处理器，用于读取所述存储器中的计算机程序：
    其中，所述收发机用于执行以下操作：获取用户设备发送的QoS流的计费信息，所述计费信息是基于所述用户设备提供邻近服务产生的；
    将所述计费信息发送至计费功能CHF；
    其中，所述计费信息包括：所述QoS流的流信息。
  25. 一种计费装置，包括：
    第一获取单元，用于获取服务质量QoS流的计费信息，所述计费信息是基于用户设备提供邻近服务产生的；
    第一发送单元，用于向网络侧设备发送所述计费信息；
    其中，所述计费信息包括：所述QoS流的流信息。
  26. 一种计费装置，包括：
    第二获取单元，用于获取用户设备发送的QoS流的计费信息，所述计费信息是基于所述用户设备提供邻近服务产生的；
    第二发送单元，用于将所述计费信息发送至计费功能CHF；
    其中，所述计费信息包括：所述QoS流的流信息。
  27. 一种计算机可读存储介质，其上存储有计算机程序，该计算机程序被处理器执行时实现如权利要求1至15中任一项所述计费方法的步骤。
PCT/CN2022/097142 2021-06-17 2022-06-06 一种计费方法、用户设备及网络侧设备 WO2022262608A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP22824088.3A EP4358552A4 (en) 2021-06-17 2022-06-06 BILLING METHOD, USER DEVICE AND NETWORK-SIDE DEVICE
US18/571,193 US20240283870A1 (en) 2021-06-17 2022-06-06 Charging method, user equipment and network-side equipment

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110671716.4 2021-06-17
CN202110671716.4A CN115499799A (zh) 2021-06-17 2021-06-17 一种计费方法、用户设备及网络侧设备

Publications (1)

Publication Number Publication Date
WO2022262608A1 true WO2022262608A1 (zh) 2022-12-22

Family

ID=84465289

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/097142 WO2022262608A1 (zh) 2021-06-17 2022-06-06 一种计费方法、用户设备及网络侧设备

Country Status (4)

Country Link
US (1) US20240283870A1 (zh)
EP (1) EP4358552A4 (zh)
CN (1) CN115499799A (zh)
WO (1) WO2022262608A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140134974A1 (en) * 2012-11-12 2014-05-15 Innovative Sonic Corporation Method and apparatus for reporting charging information of direct device to device communication in a wireless communication system
US20140273943A1 (en) * 2013-03-14 2014-09-18 Htc Corporation Charging method and apparatus for proximity-based service
CN105992184A (zh) * 2015-03-04 2016-10-05 阿尔卡特朗讯 一种对ProSe网络中继服务进行协同计费的方法与设备
CN112385262A (zh) * 2018-12-17 2021-02-19 英特尔公司 新空口车辆到万物侧链路通信中的资源利用和服务质量支持中的技术
CN114007196A (zh) * 2020-07-16 2022-02-01 上海朗帛通信技术有限公司 一种被用于无线通信的方法和设备

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3981176A1 (en) * 2019-09-30 2022-04-13 NEC Corporation Charging in device-to-device communications over pc5 for interactive services

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140134974A1 (en) * 2012-11-12 2014-05-15 Innovative Sonic Corporation Method and apparatus for reporting charging information of direct device to device communication in a wireless communication system
US20140273943A1 (en) * 2013-03-14 2014-09-18 Htc Corporation Charging method and apparatus for proximity-based service
CN105992184A (zh) * 2015-03-04 2016-10-05 阿尔卡特朗讯 一种对ProSe网络中继服务进行协同计费的方法与设备
CN112385262A (zh) * 2018-12-17 2021-02-19 英特尔公司 新空口车辆到万物侧链路通信中的资源利用和服务质量支持中的技术
CN114007196A (zh) * 2020-07-16 2022-02-01 上海朗帛通信技术有限公司 一种被用于无线通信的方法和设备

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
EP4358552A1 (en) 2024-04-24
US20240283870A1 (en) 2024-08-22
EP4358552A4 (en) 2024-06-05
CN115499799A (zh) 2022-12-20

Similar Documents

Publication Publication Date Title
US11979243B2 (en) Method and apparatus for supporting proximity discovery procedures
US20200162855A1 (en) Multicast data transmission method, related device, and communications system
US9992657B2 (en) Relay of charging information for proximity services
CN105453597B (zh) 中继设备的计费
CN111405493A (zh) 用于基于机器类型通信组的服务的协调分组
WO2013161670A1 (ja) 課金システム、課金装置及び課金方法
US9775018B2 (en) Offline charging for proximity services
CN102958029B (zh) 一种计费和服务质量策略管控方法与装置
WO2018023220A1 (zh) 一种业务数据传输方法及设备
CN102111741B (zh) 计费实现方法及装置
WO2019056244A1 (zh) 一种数据分发的方法、设备、存储介质及系统
JP2023120240A (ja) インタラクティブサービスのためのｐｃ５上での装置間通信における課金
CN102332985A (zh) 一种提供基于lipa承载的计费支持的方法及装置
CN110890967B (zh) 一种计费处理方法、网元及网络系统
WO2022262608A1 (zh) 一种计费方法、用户设备及网络侧设备
WO2014134819A1 (zh) 计费方法、接入网设备及网关设备
WO2019042218A1 (zh) 计费实现系统、计费实现方法及计费管理功能实体
CN103891328A (zh) 拜访的pcrf s9会话id生成
WO2024093738A1 (zh) 通信方法与通信装置
WO2024099016A1 (zh) 一种通信方法及装置
WO2022141390A1 (zh) 一种通信方法和网络设备
WO2023060408A1 (zh) 感知数据的收集方法、装置、设备、系统及存储介质
WO2018035687A1 (zh) 一种生成计费数据记录cdr的方法、设备和系统
TW202308356A (zh) 通信方法和裝置

Legal Events

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

Ref document number: 22824088

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 18571193

Country of ref document: US

WWE Wipo information: entry into national phase

Ref document number: 2022824088

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2022824088

Country of ref document: EP

Effective date: 20240117