WO2022152303A1 - 对移动局域网业务进行计费处理的方法、系统及相关设备 - Google Patents

对移动局域网业务进行计费处理的方法、系统及相关设备 Download PDF

Info

Publication number
WO2022152303A1
WO2022152303A1 PCT/CN2022/072382 CN2022072382W WO2022152303A1 WO 2022152303 A1 WO2022152303 A1 WO 2022152303A1 CN 2022072382 W CN2022072382 W CN 2022072382W WO 2022152303 A1 WO2022152303 A1 WO 2022152303A1
Authority
WO
WIPO (PCT)
Prior art keywords
charging
local area
area network
information
data
Prior art date
Application number
PCT/CN2022/072382
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 AU2022208946A priority Critical patent/AU2022208946A1/en
Priority to EP22739178.6A priority patent/EP4277309A4/en
Priority to CA3205377A priority patent/CA3205377A1/en
Priority to JP2023542856A priority patent/JP2024503864A/ja
Publication of WO2022152303A1 publication Critical patent/WO2022152303A1/zh
Priority to US18/352,789 priority patent/US20230362306A1/en

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/82—Criteria or parameters used for performing billing operations
    • H04M15/8228—Session based
    • 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
    • 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
    • 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/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/70—Administration or customization aspects; Counter-checking correct charges
    • H04M15/765—Linked or grouped accounts, e.g. of users or devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/70—Administration or customization aspects; Counter-checking correct charges
    • H04M15/785—Reserving amount on the account
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/80—Rating or billing plans; Tariff determination aspects
    • H04M15/8066—According to the number of recipients
    • H04M15/8077—Group MMS or SMS; Point-to-multi-point services or broadcast services
    • 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/83—Notification aspects
    • H04M15/85—Notification aspects characterised by the type of condition triggering a notification
    • H04M15/854—Available credit

Definitions

  • the present application relates to the field of communications, and in particular, to a method, a system and related equipment for charging and processing mobile local area network services.
  • the traditional local area network refers to a communication network formed by interconnecting multiple user devices, servers, etc. in a specific geographical area, which can realize file management and data sharing among multiple user devices. It has the advantages of high data transmission efficiency and low bit error rate, but the coverage is usually small, for example, it can only cover one enterprise campus, and the user equipment in it also lacks mobility.
  • Wireless local area network although it has a great improvement in the mobility of user equipment than traditional local area networks, is limited by the transmission power and networking scale of wireless access devices (such as wireless routers). It covers a small geographical area, such as only one workshop, one floor, etc. can be covered.
  • Virtual Private Network can realize the interconnection between components and resources of different networks, and can use the infrastructure of the Internet (Internet) or other public Internet networks to create tunnels for users, which can cover a large range. Such as the whole province, or even the whole country, and provide the same security and functional guarantee as the private network.
  • Internet Internet
  • this is a connection technology built on a public communication infrastructure. Operators have weak control over the network resources, making it difficult to ensure the quality of service (QoS) of communication between user equipment. Meet the needs of the market.
  • QoS quality of service
  • the 5th Generation local area network can provide data exchange or routing and forwarding capabilities of telecom operators' core network equipment for a group of user equipment.
  • Any two or more user equipments provide Internet protocol (IP) type or non-IP type (such as Ethernet type) communication to realize point-to-point or point-to-multipoint data transmission between user equipment; such communication services
  • IP Internet protocol
  • non-IP type such as Ethernet type
  • hundreds of industrial control devices located in a multinational factory in different provinces, cities or countries can form an "industrial control device group", and the industrial control devices belonging to this group send Ethernet data packets to each other;
  • the office equipment (such as mobile phones, computers, notebook computers, etc.) of a large enterprise located in different offices can form an "office equipment group", and the office equipment belonging to this group can send IP data packets to each other.
  • the operator has the ability to manage and control the user plane data gateway, which can better ensure the QoS of data transmission between user equipment, so it is better than traditional LAN, WLAN and VPN as a whole.
  • the existing charging processing equipment such as the charging function (CHarging Function, CHF) equipment defined by the 3GPP (3rd Generation Partnership Project, 3rd Generation Partnership Project) standard specification, can only perform communication services for traditional single user equipment.
  • CHF charging Function
  • 3GPP 3rd Generation Partnership Project
  • 3rd Generation Partnership Project 3rd Generation Partnership Project
  • an embodiment of the present application provides a method for performing charging processing on a mobile local area network service, which is applied to a charging triggering device, where the charging triggering device communicates with a charging processing device, and the charging triggering device manages At least one user plane data gateway, the mobile local area network service refers to a service that provides intra-group communication for a mobile local area network group based on the at least one user plane data gateway, and the method includes:
  • the charging processing device sends a charging request message to the charging processing device, where the charging request message includes the local area network charging information acquired by the charging triggering device, and the local area network charging information is the charging information related to the mobile local area network service ;
  • a charging response message is received from the charging processing device, where the charging response message includes a charging processing result, and the charging processing result is the result of the charging processing performed by the charging processing device on the LAN charging information. result.
  • the local area network charging information includes the charging information of the member data connection session
  • the charging processing result includes that the charging processing device calculates the charging information of the member data connection session.
  • the result of the fee processing wherein, the member data connection session is a data connection session between the member user equipment using the mobile local area network service and the corresponding user plane data gateway.
  • the charging information of the member data connection session includes first service indication information, and the first service indication information indicates that the member data connection session is used for intra-group communication of the mobile local area network group .
  • the charging information of the member data connection session includes a group identifier, and the group identifier is an identifier of the mobile local area network group.
  • the charging information of the member data connection session further includes first charging data, and the first charging data includes the usage amount and/or quota application amount of the member data connection session;
  • the charging processing result includes a result of performing charging processing on the first charging data by the charging processing device.
  • the charging information of the member data connection session further includes an intra-group forwarding mode corresponding to the first charging data; wherein, the intra-group forwarding mode is any one of the following: local exchange forwarding , Gateway tunnel forwarding, data network forwarding.
  • the charging information of the member data connection session further includes an intra-group communication mode of the member user equipment, and the intra-group communication mode is any one of the following: unicast, multicast, and broadcast.
  • the charging request message is used to request the charging processing device to create charging resources for the member data connection session, and the charging processing result includes that the charging processing device is the The identifier of the billing resource created by the member data connection session.
  • the charging request message is used to request the charging processing device to update the charging resources of the member data connection session, and the charging processing result contains the accounting data of the member data connection session. Update results for free resources.
  • the charging request message is used to request the charging processing device to delete the charging resources of the member data connection session, and the charging processing result includes the accounting data of the member data connection session.
  • the deletion result of the free resource is used to request the charging processing device to delete the charging resources of the member data connection session.
  • the above-mentioned charging processing method of the first aspect enables the charging triggering device to collect and report the charging information related to the data connection session of each member of the mobile local area network group, so that the charging processing device can better measure the telecom operator network as a group.
  • the contribution made by internal communication can perform refined billing processing for mobile LAN services; this helps to improve the accuracy of billing, and can flexibly support various billing requirements, for example, it can be based on end-to-end usage. billing, etc.
  • the charging triggering device manages two or more user plane data gateways
  • the local area network charging information includes charging information of tunnels between data gateways
  • the charging processing result includes all
  • the charging processing device performs charging processing on the charging information of the inter-data gateway tunnel; wherein, the inter-data gateway tunnel is data between two user plane data gateways managed by the charging triggering device
  • the transmission tunnel, the charging information of the tunnel between data gateways includes the information of the tunnel between data gateways.
  • the charging information of the tunnel between data gateways further includes second service indication information, where the second service indication information indicates that the tunnel between data gateways is used in the group of the mobile local area network group communication.
  • the charging information of the tunnel between the data gateways further includes a group identifier, and the group identifier is an identifier of the mobile local area network group.
  • the billing information of the member data connection session further includes second billing data, and the second billing data includes the usage amount transmitted through the tunnel between the data gateways; the billing process The result includes the result of the charging processing performed by the charging processing device on the second charging data.
  • the charging request message is used to request the charging processing device to create charging resources for the inter-data gateway tunnel, and the charging processing result includes that the charging processing device is the The identifier of the charging resource created by the tunnel between the data gateways.
  • the charging request message is used to request the charging processing device to update the charging resources of the inter-data gateway tunnel, and the charging processing result includes the accounting for the inter-data gateway tunnel. Update results for free resources.
  • the charging request message is used to request the charging processing device to delete the charging resources of the tunnel between data gateways, and the result of the charging processing includes the calculation of the tunnel between data gateways. The deletion result of the free resource.
  • the above-mentioned charging processing method of the first aspect enables the charging triggering device to further collect and report the charging information of the data gateway tunnel related to the intra-group communication of the mobile local area network group, so that the charging processing device can measure the operator more comprehensively.
  • the network's contribution to intra-group communication (supplementing the contribution of the tunnel between data gateways) enables more refined billing processing for mobile local area network services; For example, charging can be performed according to the usage of network resources (such as tunnels between data gateways).
  • an embodiment of the present application provides a method for charging and processing a mobile local area network service, which is applied to a charging processing device, where the charging processing device communicates with a charging triggering device, and the mobile local area network service refers to Providing a service of intra-group communication for a mobile local area network group, the method includes:
  • the charging request message includes local area network charging information acquired by the charging triggering device, where the local area network charging information is charging information related to the mobile local area network service ;
  • the charging processing result is the result of the charging processing performed by the charging processing device on the local area network charging information. result.
  • the local area network charging information includes charging information of a member data connection session
  • the method further includes: The charging information of the connection session is subjected to charging processing, and the charging processing result includes the result of performing charging processing on the charging information of the member data connection session; wherein, the member data connection session uses the mobile local area network.
  • the charging information of the member data connection session includes first service indication information
  • performing charging processing on the charging information of the member data connection session includes: based on the first service indication information.
  • the service indication information determines that the member data connection session is used for intra-group communication of the mobile local area network group.
  • the performing charging processing on the charging information of the member data connection session further includes: determining whether the member user equipment can use the mobile local area network service based on the first service indication information If authentication is performed, the accounting processing result includes the authentication result.
  • the charging information of the member data connection session includes a group identifier, and the group identifier is the identifier of the mobile local area network group, then the charging information for the member data connection session Information for billing processing, including any of the following:
  • the external group identifier corresponding to the mobile local area network group is queried based on the group identifier, so as to perform charging processing on the charging information of the member data connection session based on the external group identifier.
  • the charging information of the member data connection session includes first charging data, and the first charging data includes the usage amount and/or quota application amount of the member data connection session, then the The performing charging processing on the charging information of the member data connection session includes: performing charging processing on the first charging data, and the charging processing result includes performing charging on the first charging data the result of processing.
  • the charging information of the member data connection session further includes an intra-group forwarding mode corresponding to the first charging data
  • the intra-group forwarding mode is any one of the following: local exchange forwarding, gateway forwarding Tunnel forwarding and data network forwarding; then performing the charging processing on the charging information of the member data connection session further includes: determining the rate of the first charging data according to the intra-group forwarding mode, or, The first charging data and its corresponding intra-group forwarding mode are recorded in the charging CDR of the member data connection session.
  • the charging information of the member data connection session further includes the intra-group communication mode of the member user equipment, and the intra-group communication mode is any one of the following: unicast, multicast, and broadcast; Then, performing the charging processing on the charging information of the member data connection session further includes: determining the rate of the first charging data according to the intra-group communication mode, or determining the rate of the first charging data according to the intra-group communication mode, or in the data connection session of the member.
  • the intra-group communication mode is recorded in the billing bill.
  • the charging request message is used to request the charging processing device to create charging resources for the member data connection session, then the charging information of the member data connection session is calculated.
  • the charging processing includes: creating a charging resource for the member data connection session, and the charging processing result includes an identifier of the charging resource.
  • the charging request message is used to request the charging processing device to update the charging resources of the member data connection session, then the charging information of the member data connection session is calculated.
  • the charging processing includes: updating the charging resource of the member data connection session, and the charging processing result includes the update result of the charging resource of the member data connection session.
  • the charging request message is used to request the charging processing device to delete the charging resources of the member data connection session, then the charging information of the member data connection session is calculated.
  • the charging processing includes: deleting the charging resource of the member data connection session, and the charging processing result includes an update result of the charging resource of the member data connection session.
  • the local area network charging information includes charging information of a tunnel between data gateways, and before sending a charging response message to the charging triggering device, the method further includes:
  • the charging information of the inter-data gateway tunnel is used for charging processing, and the charging processing result includes the result of performing charging processing on the charging information of the inter-data gateway tunnel; wherein, the inter-data gateway tunnel is the charging trigger.
  • the data transmission tunnel between two user plane data gateways managed by the device, and the charging information of the tunnel between the data gateways includes the information of the tunnel between the data gateways.
  • the charging information of the tunnel between data gateways further includes second service indication information
  • performing charging processing on the charging information of the tunnel between data gateways includes: based on the first The second service indication information determines that the inter-data gateway tunnel is used for intra-group communication of the mobile local area network group.
  • the charging information of the tunnel between data gateways further includes a group identifier, and the group identifier is the identifier of the mobile local area network group; then the accounting for the tunnel between data gateways Charge information for billing, including any of the following:
  • the external group identifier corresponding to the mobile local area network group is queried based on the group identifier, so as to perform charging processing on the charging information of the tunnel between data gateways based on the external group identifier.
  • the charging information of the member data connection session further includes second charging data, and the second charging data includes the usage amount transmitted through the tunnel between the data gateways; performing charging processing on the charging information of the tunnel between the data gateways, and further comprising: performing charging processing on the second charging data, and the charging processing result includes a result of performing charging processing on the second charging data. result.
  • the charging request message is used to request the charging processing device to create charging resources for the inter-data gateway tunnel, and then the charging information of the inter-data gateway tunnel is calculated.
  • the charging processing includes: creating a charging resource for the inter-data gateway tunnel, and the charging processing result includes an identifier of the charging resource.
  • the charging request message is used to request the charging processing device to update the charging resources of the tunnel between data gateways, and then the charging information of the tunnel between data gateways is calculated.
  • the charging processing includes: updating the charging resource of the tunnel between the data gateways, and the charging processing result includes the update result of the charging resource of the tunnel between the data gateways.
  • the charging request message is used to request the charging processing device to delete the charging resources of the tunnel between data gateways, and then the charging information of the tunnel between data gateways is calculated.
  • the charging processing includes: deleting the charging resource of the tunnel between the data gateways, and the charging processing result includes the deletion result of the charging resource of the tunnel between the data gateways.
  • an embodiment of the present application provides a charging processing system for performing charging processing on a mobile local area network service, including: a charging triggering device and a charging processing device, the charging triggering device and the accounting
  • the charging trigger device manages at least one user plane data gateway
  • the mobile local area network service refers to a service that provides intra-group communication for a mobile local area network group based on the at least one user plane data gateway, wherein:
  • the charging triggering device is configured to send a charging request message to the charging processing device, where the charging request message includes the local area network charging information acquired by the charging triggering device, and the local area network charging information is the Billing information related to mobile local area network services;
  • the charging processing device is configured to receive the charging request message from the charging triggering device, and send a charging response message to the charging triggering device, where the charging response message includes the charging processing result.
  • the charging processing result is a result of performing charging processing on the local area network charging information by the charging processing device;
  • the charging triggering device is further configured to receive the charging response message from the charging processing device.
  • the local area network charging information includes the charging information of the member data connection session
  • the charging processing device is further configured to perform charging processing on the charging information of the member data connection session
  • the charging processing result includes the charging processing result performed by the charging processing device on the charging information of the member data connection session; wherein, the member data connection session is the member user equipment using the mobile local area network service and the member user equipment. Data connection sessions between corresponding user plane data gateways.
  • the charging information of the member data connection session includes first service indication information
  • the charging processing device is further configured to determine, based on the first service indication information, that the member data connection session is used for Intra-group communication of the mobile local area network group.
  • the charging processing device is further configured to authenticate whether the member user equipment can use the mobile local area network service based on the first service indication information, and the charging processing result includes the the result of the certification.
  • the charging information of the member data connection session further includes a group identifier, and the group identifier is the identifier of the mobile local area network group, and the charging processing device is further configured to:
  • the external group identifier corresponding to the mobile local area network group is queried based on the group identifier, so as to perform charging processing on the charging information of the member data connection session based on the external group identifier.
  • the charging information of the member data connection session includes first charging data and an intra-group forwarding method
  • the first charging data includes the usage amount and/or quota of the member data connection session
  • the intra-group forwarding method is any one of the following: local exchange forwarding, gateway tunnel forwarding, data network forwarding, then the charging processing device is also used for:
  • the first charging data and its corresponding intra-group forwarding mode are recorded in the charging CDR of the member data connection session.
  • the charging triggering device manages two or more user plane data gateways
  • the local area network charging information includes the charging information of the tunnel between the data gateways
  • the charging processing device also uses In: before sending a charging response message to the charging trigger device, perform charging processing on the charging information of the tunnel between the data gateways; the charging processing result includes the charging processing device for the data
  • the charging information of the inter-gateway tunnel is the result of charging processing; wherein, the inter-data gateway tunnel is a data transmission tunnel between two user plane data gateways managed by the charging trigger device, and the inter-data gateway tunnel is a data transmission tunnel between two user plane data gateways managed by the charging trigger device.
  • the charging information contains the information of the tunnel between the data gateways.
  • the charging information of the tunnel between data gateways further includes second service indication information
  • the charging processing device is further configured to determine the use of the tunnel between data gateways based on the second service indication information.
  • the charging information of the tunnel between the data gateways further includes a group identifier, where the group identifier is the identifier of the mobile local area network group, and the charging processing device is further configured to:
  • the external group identifier corresponding to the mobile local area network group is queried based on the group identifier, so as to perform charging processing on the charging information of the tunnel between data gateways based on the external group identifier.
  • an embodiment of the present application provides a charging triggering device for performing charging processing on a mobile local area network service
  • the charging triggering device communicates with a charging processing device
  • the charging triggering device manages at least one A user plane data gateway
  • the mobile local area network service refers to a service that provides intra-group communication for a mobile local area network group based on the at least one user plane data gateway
  • the charging trigger device includes an acquisition module, a transmission module and a reception module, wherein :
  • the acquiring module is configured to acquire local area network charging information, where the local area network charging information is charging information related to the mobile local area network service;
  • the sending module is configured to send a charging request message to the charging processing device, where the charging request message includes the local area network charging information;
  • the receiving module is configured to receive a charging response message from the charging processing device, where the charging response message includes a charging processing result, and the charging processing result is that the charging processing device charges the local area network The result of billing processing of information.
  • the local area network charging information includes the charging information of the member data connection session
  • the charging processing result includes that the charging processing device performs charging on the charging information of the member data connection session The processing result; wherein, the member data connection session is a data connection session between a member user equipment using the mobile local area network service and a corresponding user plane data gateway.
  • the charging information of the member data connection session includes first service indication information, and the first service indication information indicates that the member data connection session is used for intra-group communication of the mobile local area network group .
  • the charging information of the member data connection session includes a group identifier, and the group identifier is an identifier of the mobile local area network group.
  • the charging information of the member data connection session includes first charging data and an intra-group forwarding method, and the first charging data includes the usage amount and/or quota of the member data connection session
  • the number of applications, and the intra-group forwarding mode is any one of the following: local exchange forwarding, gateway tunnel forwarding, and data network forwarding.
  • the charging triggering device manages two or more user plane data gateways
  • the local area network charging information includes charging information of tunnels between data gateways
  • the charging processing result includes The result of the charging processing device performing charging processing on the charging information of the tunnel between the data gateways; wherein the tunnel between the data gateways is a data gateway between two user plane data gateways managed by the charging triggering device.
  • a data transmission tunnel, the charging information of the tunnel between data gateways includes the information of the tunnel between data gateways.
  • the charging information of the tunnel between data gateways further includes second service indication information, where the second service indication information is used to indicate that the tunnel between data gateways is used for the mobile local area network group. intra-group communication.
  • the charging information of the tunnel between the data gateways further includes a group identifier, and the group identifier is an identifier of the mobile local area network group.
  • an embodiment of the present application provides a charging processing device for performing charging processing on a mobile local area network service
  • the charging processing device communicates with a charging triggering device
  • the mobile local area network service refers to a mobile local area network service.
  • the local area network group provides intra-group communication services
  • the billing processing device includes a receiving module, a processing module and a sending module, wherein:
  • the receiving module is configured to receive a charging request message from the charging triggering device, where the charging request message includes local area network charging information, and the local area network charging information is charging information related to the mobile local area network service;
  • the processing module is configured to perform charging processing on the local area network charging information to obtain a charging processing result
  • the sending module is configured to send a charging response message to the charging triggering device, where the charging response message includes the charging processing result.
  • the local area network charging information includes the charging information of the member data connection session
  • the processing module is further configured to perform charging processing on the charging information of the member data connection session
  • the fee processing result includes the result of the processing module performing charging processing on the charging information of the member data connection session; wherein the member data connection session is the member user equipment and the corresponding user plane using the mobile local area network service.
  • the charging information of the member data connection session includes first service indication information
  • the processing module is further configured to determine, based on the first service indication information, that the member data connection session is used for the member data connection session.
  • the processing module is further configured to authenticate whether the member user equipment can use the mobile local area network service based on the first service indication information.
  • the charging information of the member data connection session includes a group identifier, and the group identifier is the identifier of the mobile local area network group, and the processing module is further configured to:
  • the external group identifier corresponding to the mobile local area network group is queried based on the group identifier, so as to perform charging processing on the charging information of the member data connection session based on the external group identifier.
  • the charging information of the member data connection session includes an intra-group forwarding method
  • the first charging data includes the usage amount and/or quota application amount of the member data connection session
  • the internal forwarding mode is any one of the following: local exchange forwarding, gateway tunnel forwarding, and data network forwarding, then the processing module is also used for:
  • the first charging data and its corresponding intra-group forwarding mode are recorded in the charging CDR of the member data connection session.
  • the local area network charging information includes charging information of a tunnel between data gateways
  • the processing module is further configured to: Perform charging processing on the charging information of the tunnel between data gateways; wherein the tunnel between data gateways is a data transmission tunnel between two user plane data gateways managed by the charging trigger device, and the data gateway
  • the charging information of the inter-tunnel includes the information of the inter-data gateway tunnel.
  • the charging information of the tunnel between data gateways further includes second service indication information
  • the processing module is further configured to determine, based on the second service indication information, that the tunnel between data gateways is used for all data gateways. Describe the intra-group communication of the mobile local area network group.
  • the charging information of the tunnel between the data gateways further includes a group identifier, where the group identifier is the identifier of the mobile local area network group, and the charging processing device is further configured to:
  • the external group identifier corresponding to the mobile local area network group is queried based on the group identifier, so as to perform charging processing on the charging information of the tunnel between data gateways based on the external group identifier.
  • an embodiment of the present application provides a charging trigger device, including a processor and a memory, wherein:
  • the memory for storing program instructions
  • the processor is configured to invoke and execute the program instructions stored in the memory, so that the charging triggering device executes the charging processing method in any possible solution under the first aspect.
  • an embodiment of the present application provides a charging processing device, including a processor and a memory, wherein:
  • the memory for storing program instructions
  • the processor is configured to invoke and execute the program instructions stored in the memory, so that the charging processing device executes the charging processing method in any possible solution under the second aspect.
  • an embodiment of the present application provides a computer-readable storage medium, including instructions, which, when run on a computer, cause the computer to execute the first aspect, the second aspect, and any of the following aspects of the first aspect.
  • Fig. 1 is an architecture diagram of an existing communication system
  • FIG. 2A is an architectural diagram of a first communication system provided by an embodiment of the present application.
  • FIG. 2B is a schematic diagram of an intra-group forwarding manner provided by an embodiment of the present application.
  • 3A is an architectural diagram of a second communication system provided by an embodiment of the present application.
  • 3B is a flowchart of a first charging processing method provided by an embodiment of the present application.
  • 3C is a flowchart of a second charging processing method provided by an embodiment of the present application.
  • 4A is an architectural diagram of a third communication system provided by an embodiment of the present application.
  • 4B is a schematic diagram of a first intra-group forwarding mode in a 5G local area network provided by an embodiment of the present application;
  • 4C is a schematic diagram of a second intra-group forwarding mode in a 5G local area network provided by an embodiment of the present application.
  • 4D is a schematic diagram of a third intra-group forwarding method in a 5G local area network provided by an embodiment of the present application.
  • FIG. 5 is a flowchart of a third charging processing method provided by an embodiment of the present application.
  • FIG. 6 is a flowchart of a fourth charging processing method provided by an embodiment of the present application.
  • FIG. 7A is a schematic diagram of a first networking of multiple CHF devices provided by an embodiment of the present application.
  • FIG. 7B is a schematic diagram of a second networking of multiple CHF devices provided by an embodiment of the present application.
  • FIG. 8 is a schematic diagram of a hardware structure of a charging trigger device and a charging processing device provided by an embodiment of the present application;
  • FIG. 9 is a schematic diagram of a logical structure of a charging processing device provided by an embodiment of the present application.
  • FIG. 10 is a schematic diagram of a logical structure of a charging triggering device provided by an embodiment of the present application.
  • words such as “first” and “second” are used to distinguish the same or similar items with basically the same function and effect.
  • words “first”, “second” and the like do not limit the quantity and execution order, and the words “first”, “second” and the like are not necessarily different.
  • the communication system includes user equipment 103, wireless access equipment 104, user plane data gateway 105, data network 106, charging triggering device 102 and charging processing device 101;
  • the device 103 establishes a data connection session 103P through the user plane data gateway 105 to communicate with the server or other communication devices in the data network 106;
  • the charging trigger device 102 is deployed in combination with the control plane data gateway to collect the data connection session of the user equipment 103 103P information on the usage (traffic or duration) in the P, and send it to the charging processing device 101, so that the charging processing device 101 performs charging processing on the user equipment 103.
  • the data connection sessions of each user equipment are independent of each other, and the process of creating charging resources and charging processing (including online charging and offline charging) are also independent and non-interfering with each other.
  • the communication system includes a control plane data gateway 202 and the user plane data gateways 203-205 managed by it, access devices 206-209, and a mobile local area network group
  • the device of the end user may have wireless communication capability, and can be connected to a wireless access device (such as the access device 206) through an air interface; the device may also have wired communication capability, then It can be connected to a wired access device (such as access device 207) through a wired interface; in terms of product form, the device can be a smart phone, a laptop with wireless communication function (Laptop), a tablet computer, a wearable device , AR (Augmented Reality, Augmented Reality) devices, IoT (Internet of Things, Internet of Everything) devices, desktop desktops, etc.
  • a wireless access device such as the access device 206
  • the device may also have wired communication capability, then It can be connected to a wired access device (such as access device 207) through a wired interface
  • the device in terms of product form, the device can be a smart phone, a laptop with wireless communication function (Laptop), a tablet computer, a wearable device , AR (Augmented Reality, Augmented Reality) devices, Io
  • the user equipment may be a UE (user equipment, user equipment) defined by the 3GPP standard specification, such as UEs 410-413 in FIG. 4A .
  • connection or “connected” described in the embodiments of the present application includes direct connection or indirect connection, the latter refers to connection through one or more intermediate network devices, which will not be described again.
  • Data Network A network composed of data switches as transfer points for data transmission, such as the Internet (Internet), which includes application servers (not shown in Figure 2A).
  • DNN data network name, data network name
  • identifier of the data network is used as the identifier of the data network.
  • Mobile local area network refers to a virtual local area network based on a mobile communication network (such as a 5G network), which mainly includes at least one user plane data gateway, such as the user plane data gateways 203-205 in Figure 2A.
  • plane data gateway connection (for example, the user plane data gateways 203-205 are all connected to the control plane data gateway 202) to accept the management of the control plane data gateway; when the mobile local area network includes multiple user plane data gateways, different user plane data gateways They are connected to each other (for example, the user plane data gateway 203 is connected with the user plane data gateway 204, and the user plane data gateway 203 is connected with the user plane data gateway 205 through the data network 216), so as to be the communication between the member user equipments of the mobile local area network group. Communication provides services. Multiple mobile LAN groups can share the same user plane data gateway.
  • the control plane data gateway can also trigger the establishment of a data gateway between the user plane data gateway 204 and the user plane data gateway 205.
  • the data packets sent by the user equipment 212 to the user equipment 213 do not need to be forwarded by the user plane data gateway 203, but can be directly sent from the user plane data gateway 204 to the user plane data gateway 205.
  • some user equipments in the mobile local area network may also be wired communication devices, such as desktop computers.
  • the mobile local area network can be a 5G local area network (5G LAN-Virtual Network, 5G LAN VN) defined by the 3GPP standard specification.
  • the 5G local area network can provide point-to-point data transmission between the UE and the UE. Before data transmission, an association needs to be established between the protocol data unit (PDU) sessions of the two UEs.
  • PDU protocol data unit
  • the PDU sessions of all member UEs of the same 5G local area network group can be managed and controlled by the same session management function (session management function, SMF) device, or can be managed and controlled by multiple SMF devices. In the embodiment of this application, the same 5G local area network group is used.
  • the PDU sessions of all member UEs are managed and controlled by the same SMF device as an example to illustrate the technical solution.
  • each SMF device may refer to the embodiments of this application.
  • the transmission of data packets between UEs is performed based on a routing rule on a user plane function (UPF) device, and the routing rule is delivered by the SMF device to the UPF device.
  • UPF user plane function
  • Mobile local area network group refers to a set of member user equipments that can access the mobile local area network. Each member user equipment in the set can be connected to its own user plane data gateway through its own access device.
  • the ingress device 206 is connected to the user plane data gateway 203; based on the data exchange or routing forwarding service of the user plane data gateway, IP type or non-IP type communication can be performed between different member user equipments; different member user equipments in the set can distributed in different geographical areas.
  • Member user equipments of the mobile LAN group can be added or deleted.
  • the member user equipments of the mobile local area network group may not all access the mobile local area network at the same time.
  • FIG. 2A illustrates four member user equipments accessing the mobile local area network. It should be understood that in practical applications, the member user equipments in the mobile local area network group may access or leave the mobile local area network as required.
  • the mobile local area network group has two identifiers; one is the external group identifier, which is mainly used in the external system of the mobile network operator; the other is the internal group identifier, which is controlled by the unified data management (unified data management, UDM) equipment allocation, mainly used in the internal system of the mobile network operator; the unified data management equipment establishes the mapping relationship between the external group identification and the internal group identification.
  • the "group identifier" in the embodiments of the present application refers to the internal group identifier of the mobile local area network group.
  • the mobile local area network group may be a 5G local area network group (5G LAN Group) defined by the 3GPP standard specification.
  • 5G LAN Group 5G local area network group
  • Intra-group communication also known as “intra-LAN”, “private communication”, refers to the communication between at least two member user equipments of the mobile local area network group.
  • Mobile local area network service refers to the service that provides intra-group communication for member user equipment of a mobile local area network group based on at least one user plane data gateway; the group identity of the mobile local area network service refers to the identity of the mobile local area network group; 3GPP standard specification definition
  • the 5G local area network type service (5G LAN-Type service) belongs to a mobile local area network service.
  • Usage amount refers to the number of transmission or consumption business units reported to the charging processing device for charging processing within a specific time range.
  • the usage amount information includes the number of business units, transmission direction, etc.
  • the unit can be flow or duration, etc.
  • Upstream traffic refers to the number of bytes flowing from the member user equipment to the user plane data gateway within a specific time range.
  • Downlink traffic refers to the number of bytes transmitted from the user plane data gateway to the member user equipment within a specific time range.
  • Intra-group communication mode The data exchange mode between member user equipments in the mobile local area network service. Specifically, there are at least the following three different intra-group communication modes:
  • Unicast refers to the communication between two member user equipments, also known as "1:1 communication", “one-to-one communication” or “point-to-point communication”, etc.;
  • Multicast refers to the communication between one member user equipment and multiple other member user equipments, that is, one member user equipment sends data packets to multiple member user equipments at the same time.
  • the data packets sent by the member user equipment are distributed to multiple other member user equipments, also known as "1:N communication", “one-to-many communication” or “point-to-multipoint communication", etc.;
  • Broadcasting refers to the communication between a member user equipment and all other member user equipments connected to the mobile local area network, that is, a member user equipment sends data packets to all online member user equipments in the mobile local area network group.
  • Control plane data gateway used to select the user plane data gateway for the member user equipment of the mobile LAN group to use the mobile LAN service, manage the data connection session of the member user equipment, and instruct the user plane data gateway to establish a tunnel, and send the data to the user plane Forwarding rules for data flows delivered by the data gateway.
  • the control plane data gateway can be a PGW-C (packet data network gateway for control plane, control plane packet data gateway) or an SMF (session management function, session management function) device defined by the 3GPP standard specification (as shown in Figure 4A SMF device 402).
  • PGW-C packet data network gateway for control plane, control plane packet data gateway
  • SMF session management function, session management function
  • each control plane data gateway may manage intra-group communications of multiple mobile local area networks.
  • Data connection session It is the association between the user equipment and the user plane data gateway, and is used to provide connection services for the communication between the user equipment and the visited network or with other user equipment; the creation process can be initiated by the user equipment. , the dismantling process can be initiated by the user equipment or by other network devices.
  • the data connection session is also referred to as a "data session” or a "session” for short.
  • the data connection session can be an IP-CAN (IP-connectivity access network, IP connectivity access network) session, a protocol data unit session (protocol data unit session, PDU session) defined by the 3GPP standard specification (as shown in the PDU session in Figure 4A ) 410P), or other forms of conversations, which are not limited in this embodiment of the present application.
  • IP-CAN IP-connectivity access network, IP connectivity access network
  • PDU session protocol data unit session
  • 3GPP standard specification as shown in the PDU session in Figure 4A ) 410P
  • other forms of conversations which are not limited in this embodiment of the present application.
  • the data connection sessions in the embodiments of the present application all refer to data connection sessions that require charging processing, and do not include data connection sessions that are free or do not require charging processing.
  • Mobile local area network data connection session refers to a data connection session used for intra-group communication of a mobile local area network group, such as 210P-213P in Figure 2B; session".
  • QoS flow Refers to the minimum granularity of forwarding processing of QoS differentiation in a data connection session, usually using QFI (QoS Flow identifier, QoS flow identifier) to identify a QoS flow.
  • QFI QoS Flow identifier, QoS flow identifier
  • User plane data gateway a core network element that provides intra-group communication services for the mobile local area network group, and is used to create intra-group sessions for member user equipment of the mobile local area network group; for example, referring to FIG. 2B, in the control plane data gateway 202 Under management, user plane data gateway 203 establishes intra-group sessions 210P and 211P for user equipment 210 and 211 respectively, user plane data gateway 204 establishes intra-group session 212P for user equipment 212, and user plane data gateway 205 establishes intra-group sessions for user equipment 213. Session 213P.
  • the user plane data gateway is also used to forward data packets between different intra-group sessions (such as between intra-group sessions 210P and 213P).
  • the way in which the data packets of the intra-group session are transmitted by the user plane data gateway of the intra-group session to another intra-group session is called the intra-group forwarding mode of the intra-group session.
  • 203 is taken as an example for further description, see FIG. 2B .
  • the user plane data gateway can be PGW-U (packet data network gateway for user plane, user plane packet data gateway) or PSA (PDU session anchor, PDU session anchor point) UPF (User Plane Function, user plane function) defined by the 3GPP standard specification ) equipment (such as PSA UPF 403-405 in Figure 4A), etc.
  • PGW-U packet data network gateway for user plane, user plane packet data gateway
  • PSA PDU session anchor, PDU session anchor point
  • UPF User Plane Function, user plane function
  • 3GPP standard specification 3GPP standard specification
  • FIG. 2B is a schematic diagram of an intra-group forwarding method provided by an embodiment of the present application, including the following methods:
  • the user plane data gateway 203 provides the local data exchange service LS-210-211, so that the data packets in the intra-group session 210P are forwarded to the intra-group
  • the session 211P or the data packets in the intra-group session 211P are forwarded to the intra-group session 210P, so that the user equipment 210 can communicate with the user equipment 211;
  • the data exchange service, the way or way of forwarding data packets between two intra-group sessions that belong to the user plane data gateway, is called forwarding through local data exchange service, abbreviated as local exchange forwarding.
  • the user plane data gateway 203 interacts with the user plane data gateway 204 to establish the inter-data gateway tunnel TN-203-204, so that the intra-group session 210P is The data packets in the group are forwarded to the intra-group session 212P, or the data packets in the intra-group session 212P are caused to be forwarded to the intra-group session 210P, so that the user equipment 210 can communicate with the user equipment 212 .
  • data is forwarded between two intra-group sessions (or data services therein) that belong to the two user plane data gateways respectively through the tunnel between the two user plane data gateways.
  • the way or way of the packet is called forwarding through the data gateway tunnel, referred to as gateway tunnel forwarding.
  • the inter-data gateway tunnel may be an N19 tunnel defined by the 3GPP standard specification (such as the N19 tunnel N19-403-404 in FIG. 4A ).
  • the data packets in the intra-group session 210P are transmitted to the data network 216, and then forwarded to the intra-group session 213P by the data network 216, or make the intra-group session 213P forward.
  • the data packets in session 213P are transmitted to data network 216 and then forwarded by data network 216 to intra-group session 210P so that user equipment 210 can communicate with user equipment 213 .
  • the method or approach of forwarding data packets between intra-group sessions of two user plane data gateways is referred to as forwarding through a gateway inter-network interface, or data network forwarding for short.
  • the interface between the user plane data gateway and the data network may be the N6 interface defined by the 3GPP standard specification (such as the N6 interfaces N6-403-DN and N6-405-DN in FIG. 4A ).
  • a mobile local area network may be composed of user plane data gateway 203, access devices 206-207, user equipment 210-211 and other devices; there is only one user plane data gateway in the local area network, with local data exchange services, but no data gateways The interface between the tunnel and the gateway network.
  • a mobile local area network may consist of user plane data gateways 203-204, access devices 206-208, user equipment 210-212 and other devices; there are two user plane data gateways in the local area network, with local data exchange services and Data inter-gateway tunnel, but no gateway inter-network interface.
  • a mobile local area network may be composed of user plane data gateway 203, user plane data gateway 205, access devices 206-207, access device 209, user equipment 210-211, user equipment 213 and other devices; there are two devices in the local area network.
  • the wireless access device can be a wireless access device or a wired access device.
  • the wireless access device is usually the NG-RAN defined by the 3GPP standard specification, including but not limited to eNB (evolved NodeB, evolved base station) and gNB (gNodeB, 5G base station).
  • eNB evolved NodeB, evolved base station
  • gNB gNodeB, 5G base station
  • the user equipment 210 is taken as an example below to describe the end-to-end transmission path of data packets during intra-group communication, as shown in Table 1.
  • the first row when the user equipment 210 and the user equipment 211 communicate within the group, the data packets are sent between the user equipment 210, the data connection session 210P, the local data exchange service LS-210-211 of the user plane data gateway 203, and the data connection session 211P. and user equipment 211 (one-way or two-way) transmission;
  • the second row when the user equipment 210 and the user equipment 212 communicate within the group, the data packets are in the tunnel TN-203-204 between the user equipment 210, the data connection session 210P, the user plane data gateway 203 and the user plane data gateway 204 , transmission between the data connection session 212P and the user equipment 212 (one-way or two-way);
  • the third row when the user equipment 210 and the user equipment 213 perform intra-group communication, the data packets between the user equipment 210, the data connection session 210P, the interface IF-203-DN between the user plane data gateway 203 and the data network, the data network Transmission between the interface IF-205-DN with the user plane data gateway 205, the data connection session 213P and the user equipment 213 (one-way or two-way).
  • the transmission of data packets in the communication system shown in FIG. 2A has at least the following characteristics:
  • the data packets transmitted by different user equipments are related, so their usage is also related. For example, when user equipment 210 and user equipment 211 communicate within the group, the uplink data packets of the former become the downlink of the latter. data packets, thus, the upstream usage of the former is equal to the downstream usage of the latter.
  • the data packets of the user equipment pass through more links in the communication network of the operator.
  • the data packets transmitted between the two not only pass through the data connection session of the two 210P and 212P also pass through the tunnel TN-203-204 between data gateways, which requires operators to invest additional network resources.
  • the data packets of the user equipment are forwarded more widely.
  • the user plane data gateway 203 will need to forward the data packets from the user equipment 210.
  • this also requires operators to invest more network resources.
  • the billing processing method shown in FIG. 1 cannot determine whether the usage of each member user equipment is used for intra-group communication, so that the corresponding rate cannot be used for pricing, and there is no way to know the identity of the corresponding mobile local area network group. , so that the usage of different member user equipments cannot be correlated; in some charging demand scenarios, this will lead to inaccurate charging; for example, when the charging demand is charging based on end-to-end transmission services In this case, it will result in double billing, because for the same amount of usage, one member user equipment (such as user equipment 210) is billed once, and another member user equipment (such as user equipment) that communicates with it within the group 211), the charging process needs to be processed again because the correlation between the two cannot be determined.
  • the charging processing method shown in FIG. 1 can only perform charging processing on the usage of the session link of each user equipment, but cannot perform charging processing on the usage volume of the forwarding link; in some charging demand scenarios , which will also lead to inaccurate billing; for example, in the case of billing based on network transmission services, due to the lack of usage information in the forwarding link, the billing results will be different from those made by the operator to ensure the QoS of intra-group communication. The contribution does not match, which is also a manifestation of inaccurate billing.
  • the charging processing method shown in FIG. 1 does not determine the rate according to the intra-group communication mode of each user equipment, which is equivalent to the unicast rate by default.
  • the embodiment of the present application adds a charging trigger module and a charging processing module on the basis of the communication system shown in FIG. 2 , and their functions are briefly described as follows.
  • the functions of the charging trigger module include, but are not limited to: reporting the local area network charging information (that is, the information used for charging processing for intra-group communication of the mobile local area network group, for example, the usage related to intra-group communication) to the charging processing module. information and quota application information related to intra-group communication), manage intra-group communication according to the LAN charging processing result returned by the charging processing module (that is, the result of performing charging processing on the LAN charging information); these functions can be superimposed on the 3GPP standard
  • the CTF (Charging Trigger Function, charging trigger function) defined in the specification can also be independent of the CTF and become a module or component such as "Mobile LAN Charging Trigger Function".
  • the functions of the charging processing module include but are not limited to: performing charging processing on the local area network charging information reported by the charging triggering module, for example, performing account deduction based on the usage information related to intra-group communication, and generating charging bills (Charging bills). Data Record, CDR) and other operations, grant corresponding quotas based on the quota application information related to intra-group communication, etc., and return the results of the charging processing to the charging trigger module, such as the indication information of the successful usage processing, the writing of the charging CDR Indication information of successful entry, granted quota, etc.; these functions can be superimposed on the CHF defined by the 3GPP standard specification, or independent of CHF, become modules or components such as "mobile LAN charging processing function"; in addition, charging processing
  • the module can also include a billing export function for exporting bills for the mobile local area network group.
  • the deployment method may be adopted as shown in FIG. 3A , or other deployment methods may be adopted, for example, multiple functions included in the charging processing module are respectively deployed to different on the physical device.
  • the charging processing module can be deployed on an existing charging processing device that performs charging processing for a single user equipment, or can be deployed on a device dedicated to performing charging processing on a mobile local area network. For example, "mobile local area network billing processing equipment".
  • FIG. 3A is an architectural diagram of a second communication system provided by an embodiment of the present application.
  • the communication system deploys a charging trigger module to the control plane data gateway 202, and adds a charging trigger module. It is obtained from the charging processing device 201 of the processing module; the communication system includes the first charging processing system provided by the embodiment of the present application, which is used for charging processing of mobile local area network services; the charging processing system includes control plane data The gateway 202 and the charging processing device 201, wherein the control plane data gateway 202 provides the charging processing device 201 with charging information related to the mobile local area network service, so that the charging processing device 201 performs charging processing for the mobile local area network service.
  • FIGS. 2B and 3A are both obtained based on FIG. 2A .
  • the embodiments of the present application hide (rather than remove) access devices, user equipment, and data networks therein.
  • a device including a charging triggering module such as the control plane data gateway 202 in FIG. 3A and the SMF device 402 in FIG. 4A , are collectively referred to as “charging triggering device", and will include a charging processing module
  • the devices, such as the charging processing device 201 in FIG. 3A and the CHF device 401 in FIG. 4A are collectively referred to as “charging processing devices”.
  • the numbers of charging triggering devices and charging processing devices in the embodiments of the present application are exemplary and not limited. In practical applications, a communication system may include multiple charging triggering devices and multiple charging processing devices.
  • the interaction flow between the charging triggering device and the charging processing device is further described below with reference to the specific content of the local area network charging information.
  • the local area network charging information includes the charging information of the member data connection session, wherein the member data connection session is the data connection session of the member user equipment, and the member user equipment is the user in the mobile communication local area network group device, the interaction flow between the charging triggering device and the charging processing device is shown in FIG. 3B .
  • the charging processing method is used to perform charging processing on mobile local area network services, and mainly includes the following steps:
  • Step 310 The charging triggering device acquires the charging information of the member data connection session.
  • the charging triggering device constructs the charging information of the member data connection session or sends the data from the user plane data gateway to the charging information.
  • the billing information includes one or more of the following:
  • the first billing data including the usage amount and/or the quota application amount in the member data connection session
  • the first service indication information which is used to indicate that the data connection session of the member user equipment is used for intra-group communication
  • group identification which is the internal group identification of the mobile local area network group corresponding to the intra-group communication
  • Intra-group forwarding mode which is the intra-group forwarding mode corresponding to the first charging data
  • Intra-group communication mode that is, intra-group communication mode of member user equipment
  • the charging triggering device can send the charging triggering condition to the user plane data gateway, so that the user plane data gateway can send the usage related data of the member data connection session to the charging triggering device when the charging triggering condition is satisfied.
  • Information can be sent to the user plane data gateway, so that the user plane data gateway can send the usage related data of the member data connection session to the charging triggering device when the charging triggering condition is satisfied.
  • Step 311 The charging triggering device sends a charging request message to the charging processing device, where the request message includes the charging information of the member data connection session.
  • the charging trigger device constructs a charging request message, and the request message carries the charging information of the above member data connection session; in the scenario where the charging processing device provides a service-oriented interface, the request message may be a charging resource creation request message (ChargingResourceCreateRequest), charging resource update request message (ChargingResourceUpdateRequest) or charging resource delete request message (ChargingResourceDeleteRequest).
  • ChargingResourceCreateRequest charging resource creation request message
  • ChargingResourceUpdateRequest charging resource update request message
  • ChargingResourceDeleteRequest ChargingResourceDeleteRequest
  • Step 312 The charging processing device performs charging processing on the charging information of the member data connection session.
  • the charging processing device receives the charging request message in step 311, parses the charging information of the member data connection session therefrom, and then performs one or more of the following operations.
  • the charging processing device determines, based on the first service indication information, that the data connection session of the member user equipment is used for intra-group communication, and then performs access authentication for the member user equipment, that is, whether the member user equipment can use the mobile local area network service for Authentication, or determining whether to allow the member user equipment to perform intra-group communication; optionally, the charging processing device may also determine a rate based on the first service indication information, and then apply the rate to the calculation of the first charging data.
  • the processing device saves the first service indication information, for example, the identifier of the data connection session between the first service indication information and the member user equipment, or the count of the first service indication information and the data connection session of the member user equipment.
  • the identifier of the free resource corresponds to storage;
  • the charging processing device determines the account corresponding to the mobile local area network group where the member user equipment is located according to the group identifier, or records the group identifier in the billing bill of the member data connection session, or uses the group identifier as the associated identifier to accumulate.
  • Accounting processing for example, determining the account according to the external group ID or correlating the charging CDR to correlate the application-layer charging information or the client information of the mobile local area network service, for example, record it in the charging CDR of the member data connection session external group identification); optionally, the billing processing device saves the group identification, for example, stores the group identification corresponding to the identification of the member data connection session, or stores the group identification and the calculation of the member data connection session
  • the identifier of the free resource corresponds to storage;
  • the charging processing device performs charging processing on the first charging data based on the intra-group forwarding mode; for example, the charging processing device applies the rate determined according to the intra-group forwarding mode corresponding to the first charging data to the first charging data.
  • the billing processing of the billing data includes: deducting the usage based on the rate, and freezing the account based on the rate and the quota application amount; for another example, the billing processing device performs a billing session in the member data connection session.
  • the first billing data and the corresponding intra-group forwarding method are recorded in the list;
  • the charging processing device performs charging processing on the first charging data based on the intra-group communication mode; for example, the charging processing device applies the rate determined according to the intra-group communication mode to the charging processing of the first charging data, This includes: deducting the usage based on the rate, and freezing the account based on the rate and the quota application amount; for another example, the charging processing device records the intra-group communication method in the billing bill of the member's data connection session .
  • the accounting processing device generates an accounting processing result of the member data connection session based on one or more of the above operations; exemplarily, the accounting processing result includes an authentication result (indication information of successful authentication or indication information of authentication failure) , Granted quota, usage deduction result (indication information of successful deduction or indication of deduction failure), result of writing billing bills (indication information of successful writing billing bills or writing billing bills) CDR failure indication information) and so on.
  • the accounting processing result includes an authentication result (indication information of successful authentication or indication information of authentication failure) , Granted quota, usage deduction result (indication information of successful deduction or indication of deduction failure), result of writing billing bills (indication information of successful writing billing bills or writing billing bills) CDR failure indication information) and so on.
  • Step 313 The charging processing device sends a charging response message to the charging triggering device, where the response message includes the charging processing result of the member data connection session.
  • the charging processing device constructs a charging response message and sends it to the charging triggering device, where the response message carries the charging processing result of the member data connection session. Subsequently, the charging triggering device receives the charging response message.
  • the charging triggering device and the charging processing device may repeatedly perform processes similar to steps 310 to 313, so as to continuously perform charging processing on data connection sessions of member user equipments and perform charging processing on data connection sessions of other member user equipments .
  • Step 349 The charging processing device performs charging processing on the mobile local area network group.
  • This step is optional.
  • the charging processing device saves the charging bills of the data connection sessions of different member user equipments in different time periods, and the charging processing device stores these bills according to the group identifier.
  • the billing bills are associated to generate billing bills of the mobile local area network group.
  • the charging processing device acquires the previously generated charging bills of the data connection sessions of the mobile local area network member user equipment, and the charging bills of the data connection sessions of different member user equipments or the same user equipment Perform an association operation on the single to obtain the aggregated bills of the mobile local area network; wherein, the association operation includes vertical association and horizontal association:
  • -Vertical association means that the charging processing device associates the charging information of the data connection session of the same member user equipment at different time points, specifically, the identification of the user equipment can be used as the association identification;
  • Horizontal association refers to that the charging processing device associates the charging information of the data connection sessions of the user equipments of different members of the same mobile local area network group.
  • the group identifier may be used as the association identifier.
  • the charging processing device may further trigger the user plane data gateway to control the QoS of the data connection session of each member user equipment according to the account deduction result.
  • the charging processing method shown in FIG. 3B enables the charging processing device to perform charging processing on the first charging data in the data connection session based on the relevant information of the mobile local area network, and can perform refined charging processing for mobile local area network services , to improve the accuracy of charging and flexibly support a variety of charging requirements; for details, further reference may be made to other embodiments of the present application, such as the method corresponding to FIG. 5 .
  • the local area network charging information in addition to the charging information of the member data connection session, also includes the charging information of the tunnel between data gateways (such as TN-203-204), then the charging trigger device and the computer
  • the interaction flow of the fee processing device is shown in Figure 3C.
  • 3C is a flowchart of a second charging processing method provided by an embodiment of the present application.
  • the charging processing method is used to perform charging processing on mobile local area network services, and mainly includes the following steps:
  • Step 350-Step 353 The charging triggering device and the charging processing device perform charging processing on the charging information of the member data connection session. This process is similar to the process from step 310 to step 313, and will not be repeated here. According to charging requirements, this process may not be performed in the flow of this method.
  • Step 360 The charging triggering device acquires the charging information of the tunnel between the data gateways.
  • the charging reporting trigger condition for example, when an inter-data gateway tunnel is created, or when the time point for periodic reporting arrives, the charging information of the inter-data-gateway tunnel is constructed or data from the user plane is constructed.
  • the gateway obtains the charging information of the tunnel between the data gateways, and the charging information includes one or more of the following:
  • Tunnel information that is, the information of the tunnel between the data gateways, such as the identifier of the tunnel, etc.
  • the second service indication information which is used to indicate that the tunnel between data gateways is used for intra-group communication
  • Group identification that is, the internal group identification of the mobile local area network group corresponding to the intra-group communication
  • Transmission direction that is, the direction in which the data packet corresponding to the second charging data is transmitted in the tunnel between data gateways.
  • the charging trigger device can send the charging trigger condition to the user plane data gateway, so that the user plane data gateway can send the charging information of the tunnel between the data gateways to the charging trigger condition when the charging trigger condition is satisfied.
  • Step 361 The charging triggering device sends a charging request message to the charging processing device, where the request message includes the charging information of the tunnel between the data gateways.
  • the charging trigger device constructs a charging request message, and the request message carries the charging information of the tunnel between the data gateways; in the scenario where the charging processing device provides a service-oriented interface, the request message may be a charging resource creation request message, a charging resource update request message, or a charging resource deletion request message.
  • Step 362 The charging processing device performs charging processing on the charging information of the tunnel between the data gateways.
  • the charging processing device receives the charging request message in step 361, parses the charging information of the tunnel between data gateways from the charging request message, and then performs one or more of the following operations.
  • the charging processing device determines, based on the tunnel information, that the charging request message contains the charging information of the tunnel between the data gateways (to distinguish it from the charging information of the member data connection session);
  • the charging processing device determines that the tunnel between data gateways is used for intra-group communication based on the second service indication information, and then determines the rate corresponding to the tunnel between data gateways, and then applies the rate to the charging processing of the second charging data ;
  • the charging processing device saves the second service indication information, for example, stores the second service indication information corresponding to the identifier of the tunnel between the data gateways, or stores the second service indication information and the data gateway.
  • the identifier of the charging resource of the tunnel is stored correspondingly;
  • the charging processing device determines the account corresponding to the mobile local area network group served by the inter-data gateway tunnel according to the group identifier; or, the charging processing device records the group in the charging CDR of the inter-data gateway tunnel or, the charging processing device queries the external group identifier corresponding to the mobile local area network group based on the group identifier, so as to charge the charging information of the tunnel between data gateways based on the external group identifier Processing (for example, recording the external group identifier in the billing bill of the tunnel between the data gateways); optionally, the charging processing device saves the group identifier, for example, records the group identifier with the data gateway
  • the identifier of the tunnel is stored correspondingly, or the group identifier is stored corresponding to the identifier of the charging resource of the tunnel between the data gateways;
  • the charging processing device generates a charging processing result of the tunnel between the data gateways based on one or more of the above operations; exemplarily, the charging processing result includes the granted quota, the indication information that the usage amount is deducted successfully, and the usage amount has been deducted successfully. Write the instruction information of the billing bill, etc.
  • Step 363 The charging processing device sends a charging response message to the charging triggering device, where the response message includes the charging processing result of the above-mentioned inter-data gateway tunnel.
  • the charging processing device constructs a charging response message and sends it to the charging triggering device, where the response message carries the charging processing result of the tunnel between the data gateways. Subsequently, the charging triggering device receives the charging response message.
  • the charging triggering device and the charging processing device may repeatedly perform the above steps 360 to 363, so as to continuously perform charging processing on the tunnel between data gateways and other tunnels between data gateways in the mobile local area network.
  • Step 399 The charging processing device performs charging processing on the mobile local area network group.
  • This step is optional.
  • the charging processing device saves the charging bills of the data connection sessions of different member user equipments in different time periods, and the tunnels between different data gateways in different time periods
  • the charging bills are associated with the billing bills according to the group ID, and the billing bills of the mobile local area network group are generated by the billing processing device.
  • the charging processing device performs various association operations according to the group identification, for example, associates the charging bills of the tunnels between the data gateways with the same group identification.
  • step 349 For the operation of associating the charging CDRs of the data connection sessions of different member user equipments, reference may be made to the relevant description in step 349, which will not be repeated here.
  • the charging processing method shown in FIG. 3C enables the charging processing device to further perform charging processing on the second charging data of the tunnel between data gateways based on the relevant information of the mobile local area network, which can further improve the accuracy of charging and realize the The used network resources are charged; for details, further reference may be made to other embodiments of the present application, such as the method flow corresponding to FIG. 6 .
  • the communication system includes a CHF device 401, an SMF device 402 and a 5G local area network managed by them;
  • the 5G local area network includes PSA UPF devices 403-405, wireless access devices 406a-409a (not shown in Figure 4A) and a 5G local area network group, the 5G local area network group includes UEs 410-413;
  • UE 410 and UE 411 implement intra-group communication through the local exchange forwarding service of the PSA UPF device 403, see Figure 4B for details
  • the related description of the UE 410 and the UE 412 realize intra-group communication through the N19 tunnel N19-403-404 between the PSA UPF device 403 and the PSA UPF device 404, see the related description of FIG.
  • the SMF device 402 includes a CTF (equivalent to a charging trigger module), which not only manages the 5G local area network, but also is responsible for triggering the CHF device to perform charging processing on the charging information communicated within the group. Therefore, the CHF device 401 is equivalent to the charging processing device described above, and the SMF device 402 is equivalent to the charging triggering device described above. Therefore, the communication system includes the second charging processing system provided by the embodiment of the present application, which is used to perform charging processing on the 5G local area network service; the charging processing system includes the SMF device 402 and the CHF device 401 .
  • the N4 session is the session between the SMF device and the PSA UPF device, and the SMF device manages the PDU session and the N19 tunnel through this session; for ease of distinction, the embodiment of the present application refers to the N4 session for managing the PDU session as "" "Normal N4 session", the N4 session used to manage the N19 tunnel is called "tunnel N4 session”.
  • the topology of the 5G local area network shown in FIG. 4A is exemplary and not limiting; in practical applications, a 5G local area network may contain more or less PSA UPF devices, and more or less UEs, among which PSA UPF devices The connection relationship between them can also be different.
  • the PSA UPF device 404 can also be connected to the PSA UPF device 405 through the N19 tunnel.
  • "UPF equipment” is also called “UPF network element”.
  • FIG. 4B is a schematic diagram of the first intra-group forwarding mode in the 5G local area network provided by the embodiment of the present application; wherein, UE 410 and UE 411 both belong to PSA UPF device 403, and the PDU session of UE 410 and the PDU session of UE 411 pass through
  • the local data exchange service of the PSA UPF device 403 forwards the data packet, so that the transmission path of the data packet for intra-group communication between UE 410 and UE 411 is: UE 410 ⁇ ->(R)AN 406a ⁇ ->I-UPF Device 406i ⁇ ->PSA UPF Device 403 ⁇ ->I-UPF Device 407i ⁇ ->(R)AN 407a ⁇ ->UE 411.
  • FIG. 4C is a schematic diagram of a second intra-group forwarding method in a 5G local area network provided by an embodiment of the present application; wherein, UE 410 and UE 412 belong to PSA UPF device 403 and PSA UPF device 404 respectively, and the PDU session of UE 410 is communicated with UE 412.
  • the data packets are forwarded between the PDU sessions through the N19 tunnel between the PSA UPF device 403 and the PSA UPF device 404, so that the transmission path of the data packets used for intra-group communication between the UE 410 and the UE 412 is: UE 410 ⁇ ->( R)AN 406a ⁇ ->I-UPF device 406i ⁇ ->PSA UPF device 403 ⁇ ->PSA UPF device 404 ⁇ ->I-UPF device 408i ⁇ ->(R)AN 408a ⁇ ->UE 412.
  • FIG. 4D is a schematic diagram of a third intra-group forwarding mode in a 5G local area network provided by an embodiment of the present application; wherein, UE 410 and UE 413 belong to PSA UPF device 403 and PSA UPF device 405 respectively, and the PDU session of UE 410 is connected with UE 413.
  • Data packets are forwarded between PDU sessions through DN 416, so that the transmission path of data packets used for intra-group communication between UE 410 and UE 413 is: UE 410 ⁇ ->(R)AN 406a ⁇ ->I-UPF device 406i ⁇ ->PSA UPF Device 403 ⁇ ->DN 416 ⁇ ->PSA UPF Device 405 ⁇ ->I-UPF Device 409i ⁇ ->(R)AN 409a ⁇ ->UE 413.
  • FIG. 5 is a flowchart of a third charging processing method provided by an embodiment of the present application, and the charging processing method is used to perform charging processing for 5G local area network services; wherein, unless otherwise specified, “SMF” refers to FIG. 4A SMF device 402 in FIG. 4A, “CHF” refers to CHF device 401 in FIG. 4A, “5G LAN group” refers to the 5G LAN group in FIG. 4A, “UE” refers to UE 410, and “UPF” refers to PSA UPF device 403, “PDU session” refers to PDU session 410P; the method flow mainly includes the following steps:
  • Step 501 The SMF receives the PDU session establishment request message sent by the UE, and determines that the PDU session is used for intra-group communication of the 5G local area network group.
  • the UE when the 5G local area network application in the UE runs and causes the UE to access the 5G local area network, the UE sends a first PDU session establishment request message to an AMF (Access Management Function) device to request the creation of a PDU session.
  • the AMF device then sends a second PDU session establishment request message to the SMF based on the received first PDU session establishment request message. Examples of these two request messages are as follows:
  • S-NSSAI is the single network slice selection support information (Single Network Slice Selection Assistance Information), which carries the identifier of the network slice corresponding to the 5G local area network.
  • the UE may read Dnn51 and S-nssai51 from the locally saved configuration information about the 5G local area network to construct the first PDU session establishment request message.
  • the SMF receives the second PDU session establishment request message, parses the UEID, Dnn51 and S-nssai51 from it, and then uses the UEID, Dnn51 and S-nssai51 as query conditions to query the UE's subscription information from the unified data management device, and further According to the subscription information, it is determined that the PDU session requested to be created is used for intra-group communication of the 5G local area network.
  • Step 502 The SMF sends a charging resource creation request message to the CHF, where the request message carries SesId51, UEId51, SrvInd51 and GrpId51.
  • the SMF constructs a charging resource creation request message (such as ChargingDataRequest[Create]), or ChargingResourceCreateRequest) and sends it to the CHF to request the CHF to create charging resources for the PDU session.
  • the request message carries SesId51, UEId51, SrvInd51 and GrpId51; wherein, SrvInd51 is the first service indication information generated by SMF to indicate that the PDU session is used for intra-group communication, and GrpId51 is an identifier allocated by SMF for the 5G local area network group; SrvInd51 and GrpId51 are both optional.
  • An exemplary billing resource creation request message is as follows:
  • UEId51 is the 5G local area network group member identifier, which may be GPSI (generic public subscription identifier, general public subscription identifier), or SUPI (subscription permanent identifier, user permanent identifier).
  • GPSI generator public subscription identifier
  • SUPI subscription permanent identifier
  • user permanent identifier user permanent identifier
  • Step 503 The CHF creates charging resources and saves SrvInd51 and GrpId51.
  • the CHF receives the above-mentioned charging resource creation request message, parses the SesId51, UEId51, SrvInd51 and GrpId51 from it, and then performs the following operations:
  • the CHF can query the UE's subscription information according to UEId51, and then determine whether to allow the UE to use the group provided by the 5G local area network.
  • CHF searches for the account corresponding to the 5G LAN group according to GrpId51, and then judges whether the UE is allowed to use the intra-group communication service provided by the 5G LAN according to the balance of the account; Including GrpId51, the CHF can query the UE's subscription information according to the UEId51, and determine the identity GrpId51 of the 5G local area network group according to the subscription information.
  • the CHF also saves the received or determined SrvInd51 and GrpId51, for example, stores SrvInd51, GrpId51 and ResId51 in correspondence.
  • Step 504 The CHF sends a charging resource creation response message to the SMF, where the response message carries ResId51.
  • the CHF constructs a charging resource creation response message (eg, ChargingDataResponse[Create], or ChargingResourceCreateResponse) and sends it to the SMF, where the response message carries ResId51.
  • a charging resource creation response message eg, ChargingDataResponse[Create], or ChargingResourceCreateResponse
  • An exemplary billing resource creation response message is as follows:
  • the SMF receives the above-mentioned charging resource creation response message, and parses the ResId51 from it, so that the usage of the PDU session can be subsequently reported based on the ResId51, and the SMF can also confirm the successful access authentication of the UE according to the response message.
  • the network devices in the 5G local area network communicate within the group, and then issue charging rules to the UPF through ordinary N4 sessions (that is, N4 sessions for PDU sessions, which are different from N4 sessions for N19 tunnels).
  • the charging rules include PDR (packet detection rule, packet detection rule), URR (usage reporting rule, usage reporting rule); in a possible solution, the PDR and URR instruct UPF to detect and report local forwarding, forwarding through N6 interface, or through N19 tunnel Forwarding usage.
  • Step 505 The SMF determines the quota application amount RSU51, the intra-group forwarding mode Fwd51, and the intra-group communication mode Com51.
  • the SMF determines the quota application amount RSU51 (eg, 5M) according to the local configuration information or the charging policy provided by the policy control device, so as to generate quota application information.
  • RSU51 eg, 5M
  • the SMF also determines the intra-group forwarding mode Fwd51 of the data packet corresponding to the above-mentioned quota application amount RSU51, and its exemplary value and corresponding meaning are: "Local”-represents local forwarding via PSA UPF, "N19"-represents Forwarded via N19 tunnel between PSA UPFs, "N6" - means forwarded via N6 interface between PSA UPF and DN.
  • the SMF also determines the intra-group communication mode Com51 of the UE, and its exemplary values and corresponding meanings are: "Unicast”-represents unicast, "Multicast”-represents multicast, and "Broadcast”-represents broadcast.
  • Step 506 The SMF sends a charging resource update request message to the CHF, where the request message includes ResId51, RSU51, SrvInd51, GrpId51, Fwd51 and Com51.
  • the SMF constructs a charging resource update request message (such as ChargingDataRequest[Update], or ChargingResourceUpdateRequest) based on the quota application amount RSU51 determined in step 505, and sends it to the CHF to request the CHF to update the charging resources for the PDU session.
  • the request message contains ResId51, RSU51, Fwd51, SrvInd51, GrpId51 and Com51.
  • An exemplary charging resource update request message is as follows:
  • RSU51 and Fwd51 in the above charging resource update request message is only an example and not a limitation. Other structural relationships can be used in practical applications.
  • Fwd51 can be placed outside the RSU-INF data structure and be paralleled with SrvInd51, etc. .
  • the above-mentioned charging resource update request message may not include SrvInd51 and GrpId51.
  • the above-mentioned charging resource update request message may also not include Fwd51 and Com51.
  • Step 507 The CHF grants the quota GSU51 corresponding to the quota application amount RSU51.
  • the CHF receives the charging resource update request message in step 506, parses it out ResId51, RSU51, Fwd51, SrvInd51, GrpId51 and Com51, and then grants the quota GSU51 corresponding to RSU51.
  • CHF can conduct an appraisal based on any one or any combination of Fwd51, SrvInd51, GrpId51 and Com51, and then grant the corresponding quota GSU51; CHF can also determine the account corresponding to the 5G LAN group based on GrpId51, and grant it based on RSU51. The account is used during the corresponding quota GSU51 process.
  • the CHF may obtain the previously stored SrvInd51 or GrpId51 locally according to ResId51.
  • Step 508 The CHF sends a charging resource update response message to the SMF, where the response message includes ResId51 and GSU51.
  • the CHF constructs a charging resource update response message (eg, ChargingDataResponse[Update], or ChargingResourceUpdateResponse), and sends it to the SMF.
  • the charging resource update response message includes ResId51 and GSU51.
  • An exemplary charging resource update response message is as follows:
  • the SMF receives the above-mentioned charging resource update response message, parses the ResId51 and GSU51 from it, and manages the use of the GSU51, that is, manages the consumption of the GSU51 by the PDU session.
  • the SMF sends the GSU51 to the UPF, and the UPF manages the consumption of the GSU51 by the PDU session.
  • the SMF and the CHF do not perform the processes of steps 505 to 508 (ie, the process of applying for quota).
  • Step 509 The SMF determines the usage amount USU51, the intra-group forwarding mode Fwd52, and the intra-group communication mode Com52.
  • the SMF acquires the usage amount USU51, the corresponding intra-group forwarding mode Fwd52 and the intra-group communication mode Com52.
  • Fwd52 can be the same as Fwd51 or different
  • Com52 can be the same as Com51 or different.
  • SMF can obtain usage USU51 through ordinary N4 sessions. For example, SMF generates corresponding PDRs and URRs based on PCC (Policy and Charging Control) rules, and sends PDRs and URRs to UPF through ordinary N4 sessions, UPF Report the usage USU51 corresponding to the URR through a common N4 session.
  • PCC Policy and Charging Control
  • Step 510 The SMF sends a charging resource update request message to the CHF, where the request message includes ResId51, USU51, Fwd52, SrvInd51, GrpId51 and Com52.
  • the SMF constructs a charging resource update request message based on the USU51, Fwd52 and Com52 determined in step 509, and sends it to the CHF.
  • the request message includes ResId51, USU51, Fwd52, SrvInd51, GrpId51 and Com52.
  • An exemplary charging resource update request message is as follows:
  • the above-mentioned charging resource update request message may not include SrvInd51 and GrpId51.
  • the above-mentioned charging resource update request message may also not include Fwd52 and Com52.
  • the aforementioned RG51 may be replaced with an identifier of data connection services of other granularities in the PDU session, such as an identifier of a QoS flow.
  • Step 511 The CHF performs charging processing on the USU51.
  • the CHF receives the charging resource update request message in step 510, parses it out ResId51, USU51, Fwd52, SrvInd51, GrpId51 and Com52, and then performs charging processing on USU51.
  • CHF can determine the rate based on any one or any combination of Fwd52, SrvInd51, GrpId51, and Com52, and determine the account corresponding to the 5G local area network group based on GrpId51; if the charging mode is online charging, CHF is based on all The determined rate and the USU51 deduct the account for the determined account. If the charging mode is offline charging, the CHF records any one of Fwd52, SrvInd51, GrpId51 and Com52 in the charging CDR of the PDU session or Any combination and USU51.
  • the CHF may obtain the previously stored SrvInd51 and GrpId51 locally according to ResId51.
  • the CHF can use GrpId51 as the associated identifier in this step or in subsequent steps to accumulate the total usage of the 5G local area network group, and the total usage can be used for the QoS of the intra-group communication of the 5G local area network group.
  • Control for example, perform QoS control on each PDU session; for example, assuming that the "GRPID" values in multiple ChargingResourceUpdateRequests received by CHF are all "GRP414", then CHF accumulates the usage in the PDU sessions in these ChargingResourceUpdateRequests to obtain The usage of 5G LAN groups.
  • Step 512 The CHF sends a charging resource update response message to the SMF, where the response message includes ResId51 and the charging processing result ChgRst51.
  • the CHF constructs a charging resource update response message and sends it to the SMF.
  • the charging resource update response message includes ResId51 and the charging processing result ChgRst51, and its exemplary values and corresponding meanings are: "SucInDeduction”- Indicates that the account deduction is successful, "SucInRecording”-indicates that the billing record is written successfully.
  • An exemplary charging resource update response message is as follows:
  • the SMF receives the charging resource update response message, parses the charging processing result therefrom, and manages the PDU session accordingly, such as maintaining the release of the PDU session to maintain the intra-group communication service of the UE.
  • Step 513 The SMF determines to delete the charging resource, determines the usage USU52, and determines the intra-group forwarding mode Fwd53 and the intra-group communication mode Com53.
  • the SMF receives the request message for releasing the PDU session sent by the UE or other devices (such as PCF devices), and determines accordingly to trigger the CHF to delete the previously created charging resources; due to the unreported usage, the SMF obtains the The usage amount USU52 before the PDU session is released (it is assumed to be 3M), the corresponding intra-group forwarding mode Fwd53 and the intra-group communication mode Com53.
  • Fwd53 may be the same as Fwd51 or Fwd52, or may be different
  • Com53 may be the same as Com52 or Com51, or may be different.
  • the SMF obtains the USU52 reference may be made to the relevant description in step 510, which will not be repeated here.
  • Step 514 The SMF sends a charging resource deletion request message to the CHF, where the request message includes ResId51, USU52, Fwd53, SrvInd51, GrpId51 and Com53.
  • the SMF constructs a charging resource deletion request message based on the USU52, Fwd53 and Com53 determined in step 513, and sends it to the CHF to request the CHF to delete the charging resource for the PDU session.
  • the request message includes ResId51, USU52, Fwd53, SrvInd51, GrpId51 and Com53.
  • An exemplary charging resource update request message is as follows:
  • the charging resource deletion request message may not include SrvInd51 and GrpId51.
  • the above-mentioned charging resource deletion request message may also not include Fwd53 and Com53.
  • Step 515 The CHF performs charging processing on the USU 52 and deletes the charging resources.
  • the CHF receives the charging resource deletion request message in step 514, parses it out ResId51, USU52, Fwd53, SrvInd51, GrpId51 and Com53, and then performs charging processing on USU53.
  • ResId51 USU52
  • Fwd53 Fwd53
  • SrvInd51 SrvInd51
  • GrpId51 Com53
  • the CHF can obtain the previously stored SrvInd51 and GrpId51 locally according to ResId51.
  • the CHF After completing the charging processing for the USU52, the CHF deletes the charging resource corresponding to the previously created ResId51, so as to recover the computing resources on the CHF occupied by the charging resource, such as memory and CPU resources.
  • Step 516 The CHF sends a charging resource deletion response message to the SMF, where the response message includes ResId51, the charging processing result ChgRst52 and the charging resource deletion result DelRst51.
  • the CHF constructs a charging resource deletion response message and sends it to the SMF.
  • the charging resource deletion response message includes ResId51, the charging processing result ChgRst52 and the resource deletion result DelRst51.
  • the exemplary values and corresponding meanings of ChgRst52 are the same as ChgRst51 is the same, and will not be described again; the exemplary value and corresponding meaning of DelRst51 are: "SucInDeleting"-indicates that the charging resource corresponding to the PDU session is successfully deleted.
  • An exemplary billing resource deletion response message is as follows:
  • the SMF receives the charging resource deletion response message, parses out ChgRst52 and DelRst51 from it, and manages the PDU session accordingly, such as releasing the PDU session, to terminate the UE's intra-group communication service.
  • the SMF may determine the RSU51 and/or the USU51 before step 502, and make the create charging resource request message in the step 502 carry the RSU51 and/or the USU51, so that, in the step 504, the SMF obtains the information from the CHF Obtain GSU51 and/or ChgRst51 in the sent billing resource creation response message.
  • the above steps 501-516 are the charging process for intra-group communication of UE 410.
  • the method flow may also include the charging process for intra-group communication of other UEs in the 5G local area network group, for example:
  • Steps 521-536 the charging processing procedure of UE 411 for intra-group communication.
  • the SMF triggers the CHF to perform charging processing on the intra-group communication of the UE 411.
  • the SMF triggers the CHF to perform charging processing on the intra-group communication of the UE 411.
  • steps 501-516 refer to the process of steps 501-516.
  • Steps 541-556 The charging process for intra-group communication of UE 412.
  • the SMF triggers the CHF to perform charging processing on the intra-group communication of the UE 412.
  • the SMF triggers the CHF to perform charging processing on the intra-group communication of the UE 412.
  • steps 501-516 refer to the process of steps 501-516.
  • Steps 561-570 The charging process for intra-group communication of UE 413.
  • the SMF triggers the CHF to perform charging processing on the intra-group communication of the UE 413.
  • the SMF triggers the CHF to perform charging processing on the intra-group communication of the UE 413.
  • steps 501-516 refer to the process of steps 501-516.
  • the order of the charging processing procedures for intra-group communication of the above multiple UEs is not fixed, and may be different from the above order, and the charging processing procedures for intra-group communication of different UEs may also be performed in parallel.
  • Step 599 The CHF performs charging processing on the 5G local area network group.
  • the CHF saves the charging bills of the PDU sessions of different UEs in different time periods, and the CHF device stores the USU in the charging bills according to GrpId51.
  • output bills for 5G LAN groups for example, as follows.
  • UE 410 communicates with UE 411, UE 412, and UE 413 in broadcast mode, the data packet transmitted in the PDU session (410P) is 5M, and the forwarding mode includes local exchange forwarding, forwarding through N19 tunnel and forwarding through N6 interface ;
  • UE 411 communicates with UE 410 and UE 412 in a multicast mode
  • the data packet transmitted in the PDU session (411P) is 3M
  • the forwarding mode includes forwarding through local exchange and forwarding through N19 tunnel
  • the data packet transmitted in the PDU session (412P) is 2M, and the forwarding method includes forwarding through the N19 tunnel;
  • the data packet transmitted in the PDU session (413P) is 1M
  • the forwarding mode includes forwarding through the N6 interface.
  • UL indicates uplink
  • DL indicates downlink
  • Local indicates local switching forwarding
  • N19 indicates forwarding through N19 tunnel
  • N6 indicates forwarding through N6 interface.
  • the CHF will charge the uplink usage, that is, the usage numbers 1, 3, 5, 7, 9, 11, and 13 in Table 2 will be charged to get the cost. Yes:
  • the CHF will charge the usage through the N19 tunnel, that is, the usage with the forwarding mode "N19" in the group in Table 2.
  • the resulting charges are:
  • FIG. 6 is a flowchart of a fourth charging processing method provided by an embodiment of the present application, and the charging processing method is used to perform charging processing for 5G local area network services; wherein, unless otherwise specified, “SMF” refers to FIG. 4A In the SMF device 402, “CHF” refers to the CHF device 401 in Fig. 4A, “5G LAN group” refers to the 5G LAN group in Fig. 4A, “UPF 403" refers to the PSA UPF device 403, “UPF 404" ” refers to the PSA UPF equipment 404; the method flow mainly includes the following steps:
  • Step 601-Step 676 the charging processing process of the PDU session of UE 410-UE 413; this process is similar to the process of step 501-step 576, and will not be repeated; according to charging requirements, this process may not be performed in the flow of this method .
  • Step 681 The SMF establishes an N19 tunnel between the UPF device 403 and the UPF device 404, and generates tunnel information TunInf61.
  • the SMF determines that an N19 tunnel needs to be established between the UPF device 403 and the UPF device 404 to support intra-group communication of the 5G local area network, and then sends the establishment of the N19 tunnel to the UPF device 403 and the UPF device 404 respectively.
  • the indication information of the tunnel triggers the interaction between the UPF device 403 and the UPF device 404 to establish an N19 tunnel.
  • the SMF generates tunnel information TunInf61, which at least includes the identifier TEId61 allocated by the SMF for the N19 tunnel.
  • the SMF device manages two UPF devices (for 5G local area network communication), in other words, the UPF device set of the 5G local area network includes two UPF devices, assuming that an N19 tunnel is established between these two UPF devices, then the SMF The device requests CHF to create a dedicated charging resource for this N19 tunnel.
  • the SMF device can obtain the charging information of the N19 tunnel from any one of the two UPF devices, or can obtain the charging information of the N19 tunnel from the two UPF devices, respectively. After they merge and deduplicate, they obtain the aggregated billing information of the N19 tunnel.
  • the SMF device manages more than two UPF devices (for 5G LAN communication), in other words, the UPF device set of the 5G LAN contains more than two UPF devices, assuming that an N19 tunnel will be established between any two UPF devices , at this time the same UPF establishes N19 tunnels with multiple UPF devices at the same time, that is to say, the SMF device may manage multiple N19 tunnels, then the SMF device can request CHF to create a corresponding charging resource for each N19 tunnel, It is also possible to request the CHF to create a common charging resource for all these N19 tunnels. For each N19 tunnel, the method for generating the charging information is the same as that in the previous paragraph, and details are not repeated here.
  • the method for creating the charging resource corresponding to the PDU session is the same as the method flow corresponding to FIG. 5 ; optionally, after the charging resource corresponding to the PDU session is created, the SMF passes the
  • the PDR and URR (usage reporting rule, usage reporting rule) delivered by a common N4 session to the UPF device only include charging rules for local switching forwarding and forwarding through the N6 interface, excluding the charging rules for forwarding through the N19 tunnel.
  • the PDR and URR delivered to the UPF device through the tunnel N4 session include the charging rules forwarded through the N19 tunnel.
  • Step 682 The SMF sends a charging resource creation request message to the CHF, where the request message carries TunInf61, SrvInd61 and GrpId51.
  • the SMF issues FAR (Forwarding Action Rule, forwarding action rule), PDR (Packet Detection Rule, packet detection rule), or the locally configured charging policy to determine the need
  • FAR Forwarding Action Rule, forwarding action rule
  • PDR Packet Detection Rule, packet detection rule
  • the request message includes TunInf61, SrvInd61 and GrpId51, where SrvInd61 is the second service indication
  • GrpId51 has been described in the corresponding method flow of FIG. 5 , and will not be repeated here.
  • the request message may not carry SrvInd61.
  • the SMF may send the request message to the CHF when sending an instruction to establish the N19 tunnel to the UPF, or when the UPF returns that the N19 tunnel is successfully established.
  • An exemplary billing resource creation request message is as follows:
  • Step 683 The CHF creates charging resources and saves TunInf61, SrvInd51 and GrpId51.
  • the CHF receives the above-mentioned charging resource creation request message, parses out TunInf61, SrvInd61 and GrpId51 from it, and then performs the following operations:
  • the CHF stores TunInf61 and GrpId51, and also stores the received or determined SrvInd61, for example, stores TunInf61, SrvInd61, GrpId51 and ResId61 in correspondence.
  • the SMF issues the PDR and/or URR to the UPF devices (such as the UPF device 403 and the UPF device 404) at both ends of the N19 tunnel to instruct the UPF to collect the charging in the N19 tunnel. data.
  • the UPF devices such as the UPF device 403 and the UPF device 404
  • the charging resource created for the N19 tunnel is shared across PDU sessions, and the usage amount transmitted in the N19 tunnel caused by the communication between different UEs is reported to the charging processing device through the charging resource, that is, through the A charging request message (such as a charging resource update request message or a charging resource deletion request message) carrying the charging resource identifier reports the usage amount.
  • a charging request message such as a charging resource update request message or a charging resource deletion request message
  • Step 684 The CHF sends a charging resource creation response message to the SMF, where the response message carries ResId61.
  • the CHF constructs a charging resource creation response message and sends it to the SMF, where the response message carries ResId61.
  • An exemplary billing resource creation response message is as follows:
  • Step 689 The SMF determines the usage amount USU61 and the transmission direction Dir61.
  • the SMF interacts with the UPF device 403 and/or the UPF device 404 respectively through the tunnel N4 session (Group N4 for N19), and obtains the usage amount USU61 transmitted through the N19 tunnel from the UPF.
  • the tunnel N4 session Group N4 for N19
  • the UPF devices such as UPF 403
  • the identifiers of the UPF devices at both ends, and the number of service units are the same
  • It can be merged and deduplicated by SMF and reported to CHF, or it can be merged and deduplicated by CHF after being reported by SMF.
  • De-duplication refers to choosing one of the above two usages and discarding the other.
  • the SMF also determines the direction Dir61 in which the data packet corresponding to the USU61 is transmitted in the N19 tunnel, and its exemplary values and corresponding meanings are: "403-404" - indicates that it is sent from the UPF device 403 to the UPF device 404, " 404-403" - means sent from UPF device 404 to UPF device 403.
  • Step 690 The SMF sends a charging resource update request message to the CHF, where the request message includes ResId61, USU61, Dir61, TunInf61, SrvInd61 and GrpId51.
  • the SMF constructs a charging resource update request message based on the USU61 and Dir61 determined in step 689, and sends it to the CHF.
  • the request message includes ResId61, USU61, Dir61, TunInf61, SrvInd61 and GrpId51.
  • An exemplary charging resource update request message is as follows:
  • the CHF has stored TunInf61, SrvInd61 or GrpId51, then optionally, in order to avoid redundant transmission of information, the above-mentioned charging resource update request message may not include TunInf61, SrvInd61 or GrpId51.
  • the above-mentioned charging resource update request message may also not include Dir61.
  • Step 691 The CHF performs charging processing on the USU61.
  • the CHF receives the charging resource update request message in step 690, parses it out ResId61, USU61, Dir61, TunInf61, SrvInd61 and GrpId51, and then performs charging processing on USU61.
  • CHF can determine the rate based on any one or any combination of TunInf61, Dir61, SrvInd61 and GrpId51, and determine the account corresponding to the 5G local area network group based on GrpId51; if the charging mode is online charging, CHF is based on all The determined rate and USU61 deduct the account for the determined account. If the charging mode is offline charging, CHF records any one of TunInf61, Dir61, SrvInd61 and GrpId51 in the charging CDR corresponding to the N19 tunnel. or any combination and USU61.
  • the CHF may locally obtain previously stored TunInf61, SrvInd61 or GrpId51 according to ResId61.
  • CHF can use GrpId51 as the associated identifier in this step or in subsequent steps to accumulate the total usage of the 5G local area network group. ", CHF accumulates the usage of these ChargingResourceUpdateRequests transmitted through the N19 tunnel to obtain the usage of the 5G LAN group.
  • Step 692 The CHF sends a charging resource update response message to the SMF, where the response message includes ResId61 and the charging processing result ChgRst61.
  • the CHF constructs a charging resource update response message and sends it to the SMF.
  • the charging resource update response message includes ResId61 and the charging processing result ChgRst61, and its exemplary values and corresponding meanings are: "SucInDeduction”- Indicates that the account deduction is successful, and "SucInRecording"-indicates that the billing record is written successfully.
  • An exemplary charging resource update response message is as follows:
  • the SMF receives the charging resource update response message, parses the charging processing result therefrom, and manages the N19 tunnel accordingly, for example: tearing down or releasing the tunnel.
  • Step 693 The SMF determines to delete the charging resource, determines the usage USU62, and determines the transmission direction Dir62.
  • the SMF determines to release the N19 tunnel according to the communication situation between the member UEs in the 5G local area network group (for example, the N19 tunnel has no traffic for T consecutive seconds), and accordingly determines to trigger the CHF to delete the billing previously created for the N19 tunnel. resource; since there is an unreported usage amount, the SMF determines the usage amount USU62 transmitted through the N19 tunnel by interacting with the UPF 403 and/or the UPF 404; optionally, the SMF also determines that the data packet corresponding to the USU62 is in the N19 tunnel The direction of transmission is Dir62.
  • Step 694 The SMF sends a charging resource deletion request message to the CHF, where the request message includes ResId61, USU62, Dir62, TunInf61, SrvInd61 and GrpId51.
  • the SMF constructs a charging resource deletion request message based on the USU62 and Dir62 determined in step 693, and sends it to the CHF, where the request message includes ResId61, USU62, Dir62, TunInf61, SrvInd61 and GrpId51.
  • An exemplary charging resource update request message is as follows:
  • the charging resource deletion request message may not include TunInf61, SrvInd61 and GrpId51.
  • the above-mentioned charging resource deletion request message may also not include Dir62.
  • Step 695 The CHF performs charging processing on the USU 62 and deletes the charging resources.
  • the CHF receives the charging resource deletion request message in step 694, parses it out ResId61, USU62, Dir62, TunInf61, SrvInd61 and GrpId51, and then performs charging processing on USU62.
  • ResId61 ResId61
  • USU62 Dir62
  • TunInf61 TunInf61
  • SrvInd61 SrvInd61
  • GrpId51 GrpId51
  • the CHF may locally obtain previously stored TunInf61, SrvInd61 or GrpId51 according to ResId61.
  • the CHF After completing the charging processing for the USU62, the CHF deletes the charging resource corresponding to the previously created ResId61, so as to recover the computing resources on the CHF occupied by the charging resource, such as memory and CPU resources.
  • Step 696 The CHF sends a charging resource deletion response message to the SMF, where the response message includes ResId61, the charging processing result ChgRst62 and the resource deletion result DelRst61.
  • the CHF constructs a charging resource deletion response message and sends it to the SMF.
  • the charging resource deletion response message includes ResId61, the charging processing result ChgRst62 and the resource deletion result DelRst61.
  • the exemplary values and corresponding meanings of ChgRst62 are the same as ChgRst61 is the same, and will not be described again; the exemplary value and corresponding meaning of DelRst61 are: "SucInDeleting"-indicates that the charging resource corresponding to the N19 tunnel is successfully deleted.
  • An exemplary billing resource deletion response message is as follows:
  • the SMF receives the charging resource deletion response message, parses out ChgRst62 and DelRst61 from it, and according to the N19 tunnel, for example, closes the N19 tunnel, to terminate the UE's intra-group communication service.
  • the CHF creates charging resource A for the PDU session, and creates charging resource B for the N19 tunnel, and then the SMF reports the usage in the PDU session through the identifier of the charging resource A, and forwards it through the local switching service.
  • the usage volume and the usage volume forwarded through the N6 interface, and the usage volume transmitted through the N19 tunnel is reported through the identifier of the billing resource B, which can more comprehensively measure the operator's communication network's contribution to the 5G LAN group communication and improve billing. accuracy.
  • the CHF can also create charging resource A for the PDU session, create charging resource B for the forwarding path of the local switching service of the UPF device, and create the charging resource C for the UPF device through the N6 interface forwarding path.
  • the UPF device creates the charging resource D through the N19 tunnel, and then the SMF reports the usage in the PDU session through the identifier of the accounting resource A, and reports the usage in the PDU session through the local switching service forwarding path of the UPF device through the identifier of the accounting resource B.
  • reporting the usage of the forwarding route through the N6 interface in the PDU session through the identifier of the charging resource C reporting the usage of the forwarding route through the N19 tunnel in the PDU session through the identifier of the charging resource D.
  • reporting the usage through the identification of the charging resource X refers to the identification of the charging resource X, the amount of usage to be reported, and the amount of usage carried in the charging resource update request message or the charging resource deletion request message.
  • the above embodiment assumes that the charging information (usage information and/or quota application information) of all UEs in a 5G local area network is processed by the same CHF device.
  • the charging information of all UEs in a 5G local area network is processed by different CHF devices (one of the benefits of this is to reduce the burden of a single CHF device, thereby reducing the delay of intra-group communication),
  • each CHF device only has the charging information of some member UEs; in order to perform charging processing on the entire 5G local area network group, the method shown in FIG. 7A or the method shown in FIG. 7B can be used.
  • FIG. 7A is a schematic diagram of the first networking of multiple CHF devices provided by an embodiment of the application; in this networking, the SMF device 402 is connected to the CHF device 401 and the CHF device 401a respectively, and the CHF device 401 is connected to the CHF device 401a; the SMF device
  • the charging information of a part of UEs in the 5G LAN group is reported to the CHF device 401 for processing, and the charging information of another part of the UEs is reported to the CHF device 401a for processing; in order to perform charging processing on the entire 5G LAN group (eg output bill), it may be that the CHF device 401 sends the received part of the UE's charging information to the CHF device 401a for processing, or the CHF device 401a sends the received part of the UE's charging information to the CHF device 401a. CHF device 401 merges processing.
  • FIG. 7B is a schematic diagram of the second networking of multiple CHF devices according to an embodiment of the present application; wherein, the SMF device reports the charging information of a part of UEs in the 5G local area network group to the CHF device 401 for processing, and reports the charging information of another part of the UEs to the CHF device 401 for processing.
  • the charging information is reported to the CHF device 401a for processing; in order to perform charging processing on the entire 5G local area network group, the CHF device 401 and the CHF device 401a respectively send the received part of the UE's charging information to the CHF device 401b for combined processing.
  • the above merging process includes using the identifier of the 5G local area network group as the associated identifier, and performing summary statistics on different billing information with the same 5G local area network group identifier.
  • FIG. 8 is a schematic diagram of a hardware structure of a charging triggering device and a charging processing device provided by an embodiment of the present application. All charging triggering devices (or SMF devices, for example, 402 in FIG. 4A ) and charging processing devices (or CHF devices, for example, 401 in FIG. 4A ) in the embodiments of the present application may adopt the general purpose shown in FIG. 8 . It is realized by a computer hardware structure, which includes a processor 801, a memory 802, a bus 803, an input device 804, an output device 805, and a network interface 806, wherein the input device 804 and the output device 805 are optional.
  • a computer hardware structure which includes a processor 801, a memory 802, a bus 803, an input device 804, an output device 805, and a network interface 806, wherein the input device 804 and the output device 805 are optional.
  • memory 802 may include computer storage media in the form of volatile and/or non-volatile memory, such as read-only memory and/or random access memory.
  • Memory 802 may store operating systems, application programs, other program modules, executable code, and program data.
  • the input device 804 can be used to input information to facilitate the system administrator to operate and manage the charging triggering device and the charging processing device, for example, configure charging parameters on the charging processing device, and set default settings on the charging triggering device
  • the usage amount acquisition method or the default quota application amount, etc.; the input device 804 can be a keyboard or a pointing device, such as a mouse, trackball, touchpad, microphone, joystick, game pad, satellite TV antenna, scanner or similar devices, Both can be connected to the processor 801 through the bus 803 .
  • the output device 805 can be used to output information, which is convenient for the system administrator to operate and manage the charging triggering device and the charging processing device; for example, display the charging policy on the charging processing device, and display the default on the charging triggering device
  • the output device 805 can also be other peripheral output devices, such as speakers and/or printing devices, which can also be connected to the processor 801 through the bus 803.
  • Both the charging triggering device and the charging processing device can be connected to the network through the network interface 806, for example, to the Internet.
  • the computer-executed instructions stored in the charging triggering device and the charging processing device may be stored in a remote storage device, and are not limited to being stored locally.
  • the charging triggering device executes the executable code or application program stored in the memory 802, the charging triggering device is caused to execute the method steps corresponding to the charging triggering device (or the SMF device) in all the above embodiments , such as steps 310 , 311 , 360 , 361 , 501 , 502 , 505 , 681 , and 682 , etc.; the specific execution process can refer to the above-mentioned embodiments, and details are not repeated here.
  • the charging processing device executes the executable code or application program stored in the memory 802
  • the charging processing device is caused to execute the method steps corresponding to the charging processing device (or CHF device) in all the above embodiments , such as steps 312 , 362 , 503 , 507 , 683 , 691 and 695 , etc.; for the specific execution process, refer to the above embodiments, and details are not repeated here.
  • FIG. 9 is a schematic diagram of a logical structure of a charging processing device provided by an embodiment of the present application; the charging processing device communicates with a charging trigger device, and is used to perform charging processing on a mobile local area network service, and the mobile local area network service is a telecom operator
  • the network provides intra-group communication services for the mobile local area network group based on at least one user plane data gateway managed by the charging trigger device; specifically, the charging processing device includes a receiving module 901, a processing module 903 and a sending module 902, wherein :
  • a receiving module 901 configured to receive a charging request message from the charging triggering device, where the charging request message includes local area network charging information, and the local area network charging information is charging information related to mobile local area network services.
  • the charging processing device or CHF device
  • the processing module 903 is configured to perform charging processing on the received local area network charging information to obtain the charging processing result.
  • the specific execution process refer to the description of the steps on the charging processing device (or CHF device) side in the above-mentioned embodiment. 312, 362, 503, 507, 683, 691 and 695, etc.;
  • Step descriptions such as steps 313, 363, 504, 508, 512, 516, and 684, are the descriptions of actions performed by the charging processing device (or the CHF device).
  • the charging triggering device communicates with a charging processing device, and is used to perform charging processing on a mobile local area network service, and the mobile local area network service is a telecom operator Based on at least one user plane data gateway managed by the charging triggering device, the mobile local area network group is provided with intra-group communication services; specifically, the charging triggering device includes an acquiring module 1003, a sending module 1001 and a receiving module 1002, wherein:
  • -Acquiring module 1003 configured to acquire local area network charging information, where the local area network charging information is the charging information related to the mobile local area network service.
  • the steps on the side of the charging trigger device (or SMF device) in the above embodiment such as steps 310, 360, 361, 501, 505, 681 and 689, etc.;
  • -Sending module 1001 configured to send a charging request message to the charging processing device, where the charging request message includes the acquired local area network charging information.
  • the charging triggering device (or SMF device) side in the above embodiment step description, such as steps 310, 311, 360, 361, 501, 502, 505, 681 and 682, etc.
  • a receiving module 1002 configured to receive a charging response message from the charging processing device, where the charging response message includes a charging processing result, and the charging processing result is the result of performing charging processing on the local area network charging information by the charging processing device,
  • the charging response message includes a charging processing result
  • the charging processing result is the result of performing charging processing on the local area network charging information by the charging processing device
  • the charging processing device shown in FIG. 9 and the charging triggering device shown in FIG. 10 are presented in the form of functional modules.
  • a “module” as used herein may refer to an application-specific integrated circuit (ASIC), a circuit, a processor and memory executing one or more software or firmware programs, an integrated logic circuit, and/or others that may provide the functions described above device.
  • ASIC application-specific integrated circuit
  • the receiving module 901 , the sending module 1001 , the sending module 902 , and the receiving module 1002 can all be implemented by the processor 801 and the memory 802 in FIG. 8 .
  • the function of the receiving module 901 to receive the charging request message and the function of the sending module 1001 to send the charging request message can be implemented by the processor 801 executing the code stored in the memory 802 .
  • the disclosed system, apparatus and method may be implemented in other manners.
  • the division of the units is only a logical function division, and there may be other division methods in actual implementation, for example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not implement.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may also be electrical, mechanical or other forms of connection.
  • the units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solutions of the embodiments of the present application.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the above-mentioned integrated units may be implemented in the form of hardware, or may be implemented in the form of software functional units.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as an independent product, may be stored in a computer-readable storage medium.
  • the technical solutions of the present application are essentially or part of contributions to the prior art, or all or part of the technical solutions can be embodied in the form of software products, and the computer software products are stored in a storage medium , including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage medium includes: a U disk, a removable hard disk, a read-only memory, a random access memory, a magnetic disk or an optical disk and other media that can store program codes.

Landscapes

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

Abstract

一种对移动局域网业务进行计费处理的方法，包括：计费触发设备向计费处理设备发送局域网计费信息，该局域网计费信息为移动局域网业务相关的计费信息，该移动局域网业务为电信运营商基于计费触发设备管理的至少一个用户面数据网关为移动局域网群组提供群内通信的业务；计费处理设备接收该局域网计费信息并对其进行计费处理，再向计费触发设备发送该局域网计费信息的计费处理结果。该方法可以对移动局域网业务进行精细化的计费处理，有助于提高计费的准确性，灵活支持多种计费需求。

Description

对移动局域网业务进行计费处理的方法、系统及相关设备
本申请要求于2021年01月15日提交中国专利局、申请号为202110058017.2、申请名称为“对移动局域网业务进行计费处理的方法、系统及相关设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，尤其涉及一种对移动局域网业务进行计费处理的方法、系统及相关设备。
背景技术
传统的局域网(local area network，LAN)是指在一个特定的地理区域内的多个用户设备、服务器等互联起来形成的一个通信网络，可以实现多个用户设备之间的文件管理、数据共享等功能，具有数据传输效率高、误码率低的优点，但覆盖的地理范围通常较小，例如一般只能覆盖一个企业园区，并且其中的用户设备也缺乏可移动性。
无线局域网(wireless local area network，WLAN)，虽然在用户设备的可移动性方面比传统局域网有较大的改进，但受限于无线接入设备(如无线路由器)的发射功率和组网规模，其覆盖的地理范围较小，如只能覆盖一个车间、一个楼层等。
虚拟专用网(Virtual Private Network，VPN)可以实现不同网络的组件和资源之间的相互连接，能够利用因特网(Internet)或其他公共互联网络的基础设施为用户创建隧道，能覆盖较大的范围，如全省、甚至全国，并提供与专用网络一样的安全和功能保障。不过，这是在公共通信基础设施上构建的连接技术，运营商对其中的网络资源的控制力较弱，难以保障用户设备之间通信的服务质量(Quality of Service，QoS)，越来越难以满足市场的需求。
最近出现的移动局域网，例如，第五代移动通信系统局域网(5th Generation local area network，5G LAN)，借助电信运营商的核心网设备的数据交换或路由转发能力，能够为一组用户设备中的任意两个或者多个用户设备提供互联网协议(internet protocol，IP)类型或者非IP类型(如以太类型)的通信，实现用户设备之间的点对点或者点对多点的数据传输；这样的通信服务可以覆盖很广的地理范围，如全省、乃至全国，因此，适用于企业办公、工厂制造、车联网、电网维护、家庭通信等场景中。比如，上百个位于不同的省市或者国家的某跨国工厂的工控设备可以组成一个“工控设备群组”，属于这个群组的工控设备之间相互发送以太数据包；再比如，上千个位于不同办事处的某大型企业的办公设备(例如手机、计算机、笔记本电脑等)可以组成一个“办公设备群组”，属于这个群组的办公设备之间可以相互发送IP数据包。这些场景中，运营商对用户面数据网关具有管控能力，可以更好地保障用户设备之间的数据传输的QoS，因此整体上优于传统的LAN、WLAN和VPN。
然而，现有计费处理设备，如3GPP(3rd Generation Partnership Project，第三代合作伙伴计划)标准规范定义的计费功能(CHarging Function，CHF)设备，仅能对传统的单个用户设备的通信业务独立地进行计费处理。如何对移动局域网中成员用户设备之间的通信业务进行计费处理，是亟需解决的技术问题。
发明内容
鉴于此，有必要提供一种对移动局域网业务进行计费处理的方法，解决采用传统计费处理方法对移动局域网业务进行计费处理导致计费不准确、无法灵活支持多种计费需求等问题。
第一方面，本申请实施例提供了一种对移动局域网业务进行计费处理的方法，应用于计费触发设备，所述计费触发设备与计费处理设备通信，所述计费触发设备管理至少一个用户面数据网关，所述移动局域网业务是指基于所述至少一个用户面数据网关为移动局域网群组提供群内通信的业务，所述方法包括：
向所述计费处理设备发送计费请求消息，所述计费请求消息包含所述计费触发设备获取的局域网计费信息，所述局域网计费信息为所述移动局域网业务相关的计费信息；
从所述计费处理设备接收计费响应消息，所述计费响应消息包含计费处理结果，所述计费处理结果为所述计费处理设备对所述局域网计费信息进行计费处理的结果。
在一个可能的方案中，所述局域网计费信息包括成员数据连接会话的计费信息，则所述计费处理结果包含所述计费处理设备对所述成员数据连接会话的计费信息进行计费处理的结果；其中，所述成员数据连接会话为使用所述移动局域网业务的成员用户设备与相应的用户面数据网关之间的数据连接会话。
在一个可能的方案中，所述成员数据连接会话的计费信息包含第一业务指示信息，所述第一业务指示信息指示所述成员数据连接会话用于所述移动局域网群组的群内通信。
在一个可能的方案中，所述成员数据连接会话的计费信息包含群组标识，所述群组标识为所述移动局域网群组的标识。
在一个可能的方案中，所述成员数据连接会话的计费信息还包含第一计费数据，所述第一计费数据包含所述成员数据连接会话的使用量和/或配额申请量；所述计费处理结果包含所述计费处理设备对所述第一计费数据进行计费处理的结果。
在一个可能的方案中，所述成员数据连接会话的计费信息还包含所述第一计费数据对应的群内转发方式；其中，所述群内转发方式为以下任意一项：本地交换转发、网关隧道转发、数据网络转发。
在一个可能的方案中，所述成员数据连接会话的计费信息还包含所述成员用户设备的群内通信方式，所述群内通信方式为以下任意一项：单播、多播、广播。
在一个可能的方案中，所述计费请求消息用于请求所述计费处理设备为所述成员数据连接会话创建计费资源，则所述计费处理结果包含所述计费处理设备为所述成员数据连接会话创建的计费资源的标识。
在一个可能的方案中，所述计费请求消息用于请求所述计费处理设备更新所述成员数据连接会话的计费资源，则所述计费处理结果包含所述成员数据连接会话的计费资源 的更新结果。
在一个可能的方案中，所述计费请求消息用于请求所述计费处理设备删除所述成员数据连接会话的计费资源，则所述计费处理结果包含所述成员数据连接会话的计费资源的删除结果。
第一方面的上述计费处理方法使得计费触发设备可以采集并上报移动局域网群组的各成员数据连接会话相关的计费信息，使计费处理设备可以较好地衡量电信运营商网络为群内通信做出的贡献，可以对移动局域网业务进行精细化的计费处理；如此有助于提高计费的准确性，还可以灵活支持多种计费需求，例如，可以按端到端使用量进行计费等。
在一个可能的方案中，所述计费触发设备管理两个或两个以上用户面数据网关，所述局域网计费信息包括数据网关间隧道的计费信息，则所述计费处理结果包含所述计费处理设备对所述数据网关间隧道的计费信息进行计费处理的结果；其中，所述数据网关间隧道为所述计费触发设备管理的两个用户面数据网关之间的数据传输隧道，所述数据网关间隧道的计费信息包含所述数据网关间隧道的信息。
在一个可能的方案中，所述数据网关间隧道的计费信息还包含第二业务指示信息，所述第二业务指示信息指示所述数据网关间隧道用于所述移动局域网群组的群内通信。
在一个可能的方案中，所述数据网关间隧道的计费信息还包含群组标识，所述群组标识为所述移动局域网群组的标识。
在一个可能的方案中，所述成员数据连接会话的计费信息还包含第二计费数据，所述第二计费数据包含通过所述数据网关间隧道传输的使用量；所述计费处理结果包含所述计费处理设备对所述第二计费数据进行计费处理的结果。
在一个可能的方案中，所述计费请求消息用于请求所述计费处理设备为所述数据网关间隧道创建计费资源，则所述计费处理结果包含所述计费处理设备为所述数据网关间隧道创建的计费资源的标识。
在一个可能的方案中，所述计费请求消息用于请求所述计费处理设备更新所述数据网关间隧道的计费资源，则所述计费处理结果包含所述数据网关间隧道的计费资源的更新结果。
在一个可能的方案中，所述计费请求消息用于请求所述计费处理设备删除所述数据网关间隧道的计费资源，则所述计费处理结果包含所述数据网关间隧道的计费资源的删除结果。
第一方面的上述计费处理方法使得计费触发设备可以进一步采集并上报移动局域网群组的群内通信相关的数据网关间隧道的计费信息，使计费处理设备可以更全面地衡量运营商网络为群内通信做出的贡献(补充了数据网关间隧道的贡献)，可以对移动局域网业务进行更精细化的计费处理；如此有助于进一步提高计费的准确性，也可以支持更多的计费需求，例如，可以按网络资源(如数据网关间隧道)的使用情况进行计费。
第二方面，本申请实施例提供了一种对移动局域网业务进行计费处理的方法，应用于计费处理设备，所述计费处理设备与计费触发设备通信，所述移动局域网业务是指为移动局域网群组提供群内通信的业务，所述方法包括：
从所述计费触发设备接收计费请求消息，所述计费请求消息包含所述计费触发设备 获取的局域网计费信息，所述局域网计费信息为所述移动局域网业务相关的计费信息；
向所述计费触发设备发送计费响应消息，所述计费响应消息包含计费处理结果，所述计费处理结果为所述计费处理设备对所述局域网计费信息进行计费处理的结果。
在一个可能的方案中，所述局域网计费信息包括成员数据连接会话的计费信息，则在向所述计费触发设备发送计费响应消息之前，所述方法还包括：对所述成员数据连接会话的计费信息进行计费处理，所述计费处理结果包含对所述成员数据连接会话的计费信息进行计费处理的结果；其中，所述成员数据连接会话为使用所述移动局域网业务的成员用户设备与相应的用户面数据网关之间的数据连接会话。
在一个可能的方案中，所述成员数据连接会话的计费信息包含第一业务指示信息，则所述对所述成员数据连接会话的计费信息进行计费处理，包括：基于所述第一业务指示信息确定所述成员数据连接会话用于所述移动局域网群组的群内通信。
在一个可能的方案中，所述对所述成员数据连接会话的计费信息进行计费处理，还包括：基于所述第一业务指示信息对所述成员用户设备是否可使用所述移动局域网业务进行认证，则所述计费处理结果包含所述认证的结果。
在一个可能的方案中，所述成员数据连接会话的计费信息包含群组标识，所述群组标识为所述移动局域网群组的标识，则所述对所述成员数据连接会话的计费信息进行计费处理，包括以下任意一项：
基于所述群组标识确定所述移动局域网群组对应的账户，或者，
在所述成员数据连接会话的计费话单中记录所述群组标识，或者，
以所述群组标识为关联标识累积所述移动局域网群组的使用量，或者，
基于所述群组标识查询所述移动局域网群组对应的外部群组标识，以基于所述外部群组标识对所述成员数据连接会话的计费信息进行计费处理。
在一个可能的方案中，所述成员数据连接会话的计费信息包含第一计费数据，所述第一计费数据包含所述成员数据连接会话的使用量和/或配额申请量，则所述对所述成员数据连接会话的计费信息进行计费处理，包括：对所述第一计费数据进行计费处理，所述计费处理结果包含对所述第一计费数据进行计费处理的结果。
在一个可能的方案中，所述成员数据连接会话的计费信息还包含所述第一计费数据对应的群内转发方式，所述群内转发方式为以下任意一项：本地交换转发、网关隧道转发、数据网络转发；则所述对所述成员数据连接会话的计费信息进行计费处理，还包括：根据所述群内转发方式确定所述第一计费数据的费率，或者，在所述成员数据连接会话的计费话单中记录所述第一计费数据及其对应的群内转发方式。
在一个可能的方案中，所述成员数据连接会话的计费信息还包含所述成员用户设备的群内通信方式，所述群内通信方式为以下任意一项：单播、多播、广播；则所述对所述成员数据连接会话的计费信息进行计费处理，还包括：根据所述群内通信方式确定所述第一计费数据的费率，或者在所述成员数据连接会话的计费话单中记录所述群内通信方式。
在一个可能的方案中，所述计费请求消息用于请求所述计费处理设备为所述成员数据连接会话创建计费资源，则所述对所述成员数据连接会话的计费信息进行计费处理包括：为所述成员数据连接会话创建计费资源，所述计费处理结果包含所计费资源的标识。
在一个可能的方案中，所述计费请求消息用于请求所述计费处理设备更新所述成员 数据连接会话的计费资源，则所述对所述成员数据连接会话的计费信息进行计费处理包括：更新所述成员数据连接会话的计费资源，所述计费处理结果包含所述成员数据连接会话的计费资源的更新结果。
在一个可能的方案中，所述计费请求消息用于请求所述计费处理设备删除所述成员数据连接会话的计费资源，则所述对所述成员数据连接会话的计费信息进行计费处理包括：删除所述成员数据连接会话的计费资源，所述计费处理结果包含所述成员数据连接会话的计费资源的更新结果。
在一个可能的方案中，所述局域网计费信息包括数据网关间隧道的计费信息，则在向所述计费触发设备发送计费响应消息之前，所述方法还包括：对所述数据网关间隧道的计费信息进行计费处理，所述计费处理结果包含对所述数据网关间隧道的计费信息进行计费处理的结果；其中，所述数据网关间隧道为所述计费触发设备管理的两个用户面数据网关之间的数据传输隧道，所述数据网关间隧道的计费信息包含所述数据网关间隧道的信息。
在一个可能的方案中，所述数据网关间隧道的计费信息还包含第二业务指示信息，则所述对所述数据网关间隧道的计费信息进行计费处理，包括：基于所述第二业务指示信息确定所述数据网关间隧道用于所述移动局域网群组的群内通信。
在一个可能的方案中，所述数据网关间隧道的计费信息还包含群组标识，所述群组标识为所述移动局域网群组的标识；则所述对所述数据网关间隧道的计费信息进行计费处理，包括以下任意一项：
基于所述群组标识确定所述移动局域网群组对应的账户，或者，
在所述数据网关间隧道的计费话单中记录所述群组标识，或者，
基于所述群组标识查询所述移动局域网群组对应的外部群组标识，以基于所述外部群组标识对所述数据网关间隧道的计费信息进行计费处理。
在一个可能的方案中，所述成员数据连接会话的计费信息还包含第二计费数据，所述第二计费数据包含通过所述数据网关间隧道传输的使用量；则所述对所述数据网关间隧道的计费信息进行计费处理，还包括：对所述第二计费数据进行计费处理，所述计费处理结果包含对所述第二计费数据进行计费处理的结果。
在一个可能的方案中，所述计费请求消息用于请求所述计费处理设备为所述数据网关间隧道创建计费资源，则所述对所述数据网关间隧道的计费信息进行计费处理包括：为所述数据网关间隧道创建计费资源，所述计费处理结果包含所述计费资源的标识。
在一个可能的方案中，所述计费请求消息用于请求所述计费处理设备更新所述数据网关间隧道的计费资源，则所述对所述数据网关间隧道的计费信息进行计费处理包括：更新所述数据网关间隧道的计费资源，所述计费处理结果包含所述数据网关间隧道的计费资源的更新结果。
在一个可能的方案中，所述计费请求消息用于请求所述计费处理设备删除所述数据网关间隧道的计费资源，则所述对所述数据网关间隧道的计费信息进行计费处理包括：删除所述数据网关间隧道的计费资源，所述计费处理结果包含所述数据网关间隧道的计费资源的删除结果。
第三方面，本申请实施例提供了一种计费处理系统，用于对移动局域网业务进行计费处理，包括：计费触发设备和计费处理设备，所述计费触发设备与所述计费处理设备 通信，所述计费触发设备管理至少一个用户面数据网关，所述移动局域网业务是指基于所述至少一个用户面数据网关为移动局域网群组提供群内通信的业务，其中：
所述计费触发设备用于向所述计费处理设备发送计费请求消息，所述计费请求消息包含所述计费触发设备获取的局域网计费信息，所述局域网计费信息为所述移动局域网业务相关的计费信息；
所述计费处理设备用于从所述计费触发设备接收所述计费请求消息，且向所述计费触发设备发送计费响应消息，所述计费响应消息包含计费处理结果，所述计费处理结果为所述计费处理设备对所述局域网计费信息进行计费处理的结果；
所述计费触发设备还用于从所述计费处理设备接收所述计费响应消息。
在一个可能的方案中，所述局域网计费信息包括成员数据连接会话的计费信息，则所述计费处理设备还用于对所述成员数据连接会话的计费信息进行计费处理，所述计费处理结果包括所述计费处理设备对所述成员数据连接会话的计费信息进行计费处理的结果；其中，所述成员数据连接会话为使用所述移动局域网业务的成员用户设备与相应的用户面数据网关之间的数据连接会话。
在一个可能的方案中，所述成员数据连接会话的计费信息包含第一业务指示信息，所述计费处理设备还用于基于所述第一业务指示信息确定所述成员数据连接会话用于所述移动局域网群组的群内通信。
在一个可能的方案中，所述计费处理设备还用于基于所述第一业务指示信息对所述成员用户设备是否可使用所述移动局域网业务进行认证，则所述计费处理结果包含所述认证的结果。
在一个可能的方案中，所述成员数据连接会话的计费信息还包含群组标识，所述群组标识为所述移动局域网群组的标识，则所述计费处理设备还用于：
基于所述群组标识确定所述移动局域网群组对应的账户，或者，
在所述成员数据连接会话的计费话单中记录所述群组标识，或者，
以所述群组标识为关联标识累积所述移动局域网群组的使用量，或者，
基于所述群组标识查询所述移动局域网群组对应的外部群组标识，以基于所述外部群组标识对所述成员数据连接会话的计费信息进行计费处理。
在一个可能的方案中，所述成员数据连接会话的计费信息包含第一计费数据和群内转发方式，所述第一计费数据包含所述成员数据连接会话的使用量和/或配额申请量，所述群内转发方式为以下任意一项：本地交换转发、网关隧道转发、数据网络转发，则所述计费处理设备还用于：
根据所述群内转发方式确定所述第一计费数据的费率，或者，
在所述成员数据连接会话的计费话单中记录所述第一计费数据及其对应的群内转发方式。
在一个可能的方案中，所述计费触发设备管理两个或两个以上用户面数据网关，所述局域网计费信息包括数据网关间隧道的计费信息，则所述计费处理设备还用于：在向所述计费触发设备发送计费响应消息之前，对所述数据网关间隧道的计费信息进行计费处理；所述计费处理结果包括所述计费处理设备对所述数据网关间隧道的计费信息进行计费处理的结果；其中，所述数据网关间隧道为所述计费触发设备管理的两个用户面数据网关之间的数据传输隧道，所述数据网关间隧道的计费信息包含所述数据网关间隧道 的信息。
在一个可能的方案中，所述数据网关间隧道的计费信息还包含第二业务指示信息，所述计费处理设备还用于基于所述第二业务指示信息确定所述数据网关间隧道用于提供移动局域网业务。
在一个可能的方案中，所述数据网关间隧道的计费信息还包含群组标识，所述群组标识为所述移动局域网群组的标识，则所述计费处理设备还用于：
基于所述群组标识确定所述移动局域网群组对应的账户，或者，
在所述数据网关间隧道的计费话单中记录所述群组标识，或者，
基于所述群组标识查询所述移动局域网群组对应的外部群组标识，以基于所述外部群组标识对所述数据网关间隧道的计费信息进行计费处理。
第四方面，本申请实施例提供了一种计费触发设备，用于对移动局域网业务进行计费处理，所述计费触发设备与计费处理设备通信，所述计费触发设备管理至少一个用户面数据网关，所述移动局域网业务是指基于所述至少一个用户面数据网关为移动局域网群组提供群内通信的业务，所述计费触发设备包括获取模块、发送模块和接收模块，其中：
所述获取模块用于获取局域网计费信息，所述局域网计费信息为所述移动局域网业务相关的计费信息；
所述发送模块用于向所述计费处理设备发送计费请求消息，所述计费请求消息包含所述局域网计费信息；
所述接收模块用于从所述计费处理设备接收计费响应消息，所述计费响应消息包含计费处理结果，所述计费处理结果为所述计费处理设备对所述局域网计费信息进行计费处理的结果。
在一个可能的方案中,所述局域网计费信息包括成员数据连接会话的计费信息，所述计费处理结果包括所述计费处理设备对所述成员数据连接会话的计费信息进行计费处理的结果；其中，所述成员数据连接会话为使用所述移动局域网业务的成员用户设备与相应的用户面数据网关之间的数据连接会话。
在一个可能的方案中，所述成员数据连接会话的计费信息包含第一业务指示信息，所述第一业务指示信息指示所述成员数据连接会话用于所述移动局域网群组的群内通信。
在一个可能的方案中，所述成员数据连接会话的计费信息包含群组标识，所述群组标识为所述移动局域网群组的标识。
在一个可能的方案中，所述成员数据连接会话的计费信息包含第一计费数据和群内转发方式，所述第一计费数据包含所述成员数据连接会话的使用量和/或配额申请量，所述群内转发方式为以下任意一项：本地交换转发、网关隧道转发、数据网络转发。
在一个可能的方案中，所述计费触发设备管理两个或两个以上用户面数据网关，所述局域网计费信息包括数据网关间隧道的计费信息，所述所述计费处理结果包括所述计费处理设备对所述数据网关间隧道的计费信息进行计费处理的结果；其中，所述数据网关间隧道为所述计费触发设备管理的两个用户面数据网关之间的数据传输隧道，所述数据网关间隧道的计费信息包含所述数据网关间隧道的信息。
在一个可能的方案中，所述数据网关间隧道的计费信息还包含第二业务指示信息， 所述第二业务指示信息用于指示所述数据网关间隧道用于所述移动局域网群组的群内通信。
在一个可能的方案中，所述数据网关间隧道的计费信息还包含群组标识，所述群组标识为所述移动局域网群组的标识。
第五方面，本申请实施例提供了一种计费处理设备，用于对移动局域网业务进行计费处理，所述计费处理设备与计费触发设备通信，所述移动局域网业务是指为移动局域网群组提供群内通信的业务，所述计费处理设备包括接收模块、处理模块和发送模块，其中：
所述接收模块用于从所述计费触发设备接收计费请求消息，所述计费请求消息包含局域网计费信息，所述局域网计费信息为所述移动局域网业务相关的计费信息；
所述处理模块用于对所述局域网计费信息进行计费处理，得到计费处理结果；
所述发送模块用于向所述计费触发设备发送计费响应消息，所述计费响应消息包含所述计费处理结果。
在一个可能的方案中，所述局域网计费信息包括成员数据连接会话的计费信息，则所述处理模块还用于对所述成员数据连接会话的计费信息进行计费处理，所述计费处理结果包括所述处理模块对所述成员数据连接会话的计费信息进行计费处理的结果；其中，所述成员数据连接会话为使用所述移动局域网业务的成员用户设备与相应的用户面数据网关之间的数据连接会话。
在一个可能的方案中，所述成员数据连接会话的计费信息包含第一业务指示信息，所述处理模块还用于基于所述第一业务指示信息确定所述成员数据连接会话用于所述移动局域网群组的群内通信。
在一个可能的方案中，所述处理模块还用于基于所述第一业务指示信息对所述成员用户设备是否可使用所述移动局域网业务进行认证。
在一个可能的方案中，所述成员数据连接会话的计费信息包含群组标识，所述群组标识为所述移动局域网群组的标识，则所述处理模块还用于：
基于所述群组标识确定所述移动局域网群组对应的账户，或者，
在所述成员数据连接会话的计费话单中记录所述群组标识，或者，
以所述群组标识为关联标识累积所述移动局域网群组的使用量，或者，
基于所述群组标识查询所述移动局域网群组对应的外部群组标识，以基于所述外部群组标识对所述成员数据连接会话的计费信息进行计费处理。
在一个可能的方案中，所述成员数据连接会话的计费信息包含群内转发方式，所述第一计费数据包含所述成员数据连接会话的使用量和/或配额申请量，所述群内转发方式为以下任意一项：本地交换转发、网关隧道转发、数据网络转发，则所述处理模块还用于：
根据所述群内转发方式确定所述第一计费数据的费率，或者，
在所述成员数据连接会话的计费话单中记录所述第一计费数据及其对应的群内转发方式。
在一个可能的方案中，所述局域网计费信息包括数据网关间隧道的计费信息，则在所述发送模块向所述计费触发设备发送计费响应消息之前，所述处理模块还用于对所述数据网关间隧道的计费信息进行计费处理；其中，所述数据网关间隧道为所述计费触发 设备管理的两个用户面数据网关之间的数据传输隧道，所述数据网关间隧道的计费信息包含所述数据网关间隧道的信息。
在一个可能的方案中，所述数据网关间隧道的计费信息还包含第二业务指示信息，所述处理模块还用于基于所述第二业务指示信息确定所述数据网关间隧道用于所述移动局域网群组的群内通信。
在一个可能的方案中，所述数据网关间隧道的计费信息还包含群组标识，所述群组标识为所述移动局域网群组的标识，则所述计费处理设备还用于：
基于所述群组标识确定所述移动局域网群组对应的账户，或者，
在所述数据网关间隧道的计费话单中记录所述群组标识，或者，
基于所述群组标识查询所述移动局域网群组对应的外部群组标识，以基于所述外部群组标识对所述数据网关间隧道的计费信息进行计费处理。
第六方面，本申请实施例提供了一种计费触发设备，包括处理器和存储器，其中：
所述存储器，用于存储程序指令；
所述处理器，用于调用并执行所述存储器中存储的程序指令，以使所述计费触发设备执行第一方面下任一可能的方案中的计费处理的方法。
第七方面，本申请实施例提供了一种计费处理设备，包括处理器和存储器，其中：
所述存储器，用于存储程序指令；
所述处理器，用于调用并执行所述存储器中存储的程序指令，以使所述计费处理设备执行第二方面下任一可能的方案中的计费处理的方法。
第八方面，本申请实施例提供了一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得所述计算机执行上述第一方面、上述第二方面、上述第一方面下任意可能方案或者上述第二方面下任意可能方案对应的计费处理的方法。
附图说明
图1为一种现有通信系统的架构图；
图2A是本申请实施例提供的第一通信系统的架构图；
图2B为本申请实施例提供的群内转发方式的示意图；
图3A为本申请实施例提供的第二通信系统的架构图；
图3B为本申请实施例提供的第一计费处理方法的流程图；
图3C为本申请实施例提供的第二计费处理方法的流程图；
图4A是本申请实施例提供的第三通信系统的架构图；
图4B是本申请实施例提供的5G局域网中第一群内转发方式的示意图；
图4C是本申请实施例提供的5G局域网中第二群内转发方式的示意图；
图4D是本申请实施例提供的5G局域网中第三群内转发方式的示意图；
图5是本申请实施例提供的第三计费处理方法的流程图；
图6是本申请实施例提供的第四计费处理方法的流程图；
图7A为本申请实施例提供的多个CHF设备第一组网的示意图；
图7B为本申请实施例提供的多个CHF设备第二组网的示意图；
图8为本申请实施例提供的计费触发设备、计费处理设备的硬件结构的示意图；
图9为本申请实施例提供的计费处理设备的逻辑结构的示意图；
图10为本申请实施例提供的计费触发设备的逻辑结构的示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述。
在本申请的描述中，除非另有说明，“/”表示前后关联的对象是一种“或”的关系，例如，A/B可以表示A或B；本申请中的“和/或”是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A、同时存在A和B、单独存在B这三种情况，其中A,B可以是单数或者复数。并且，在本申请的描述中，除非另有说明，“多个”是指两个或多于两个。另外，为了便于清楚描述本申请实施例的技术方案，在本申请的实施例中，采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。
图1为一种现有通信系统的架构图，该通信系统包括用户设备103、无线接入设备104、用户面数据网关105、数据网络106、计费触发设备102和计费处理设备101；用户设备103通过用户面数据网关105建立数据连接会话103P，以与数据网络106中的服务器或其他通信设备进行通信；计费触发设备102与控制面数据网关合并部署，采集用户设备103的数据连接会话103P中的使用量(流量或时长)的信息，并将其发送给计费处理设备101，以使计费处理设备101对用户设备103进行计费处理。该计费处理方法中，每个用户设备的数据连接会话互相独立，其计费资源的创建、计费处理(包括在线计费和离线计费)过程也是相互独立、互不干涉的。
然而，如果将这种计费处理方法应用于移动局域网群组，将无法满足多样化的市场需求。下面先结合图2A-2B，描述移动局域网群组的内部通信机制，并说明现有计费处理方法的问题所在；再结合图3A-3C，描述如何对移动局域网群组的内部通信进行计费处理。
图2A是本申请实施例提供的第一通信系统的架构图；该通信系统包括控制面数据网关202及其所管理的用户面数据网关203-205、接入设备206-209和移动局域网群组的成员用户设备210-213；此外，该通信系统还包括其他设备，例如接入管理设备等，将不一一赘述。
为便于本领域技术人员理解本申请实施例，下面对图2A所示出的各组成部分及相关概念作简要解释。
用户设备(user device)：即终端用户的设备；该设备可以具有无线通信能力，则可以通过空中接口与无线接入设备(如接入设备206)相连；该设备也可以具有有线通信能力，则可以通过有线接口与有线接入设备(如接入设备207)相连；从产品形态上看，该设备可以是智能手机、带有无线通信功能的膝上电脑(Laptop)、平板电脑、可穿戴设备、AR(Augmented Reality，增强现实)设备、IoT(Internet of Things，万物互联)设备、办公桌面的台式机等。
用户设备可以是3GPP标准规范定义的UE(user equipment，用户设备)，如图4A中的UE 410-413。
注意，本申请实施例所述的“相连”或者“连接”包括直接连接或者间接连接，后者指通过一个或多个中间网络设备连接，将不再赘述。
数据网络(Data Network，DN)：用于传输数据、以数据交换机为转接点而组成的网络，如英特网(Internet)，其中包含应用服务器(图2A中未显示)。通常用DNN(data network name，数据网络名称)作为数据网络的标识。
移动局域网：是指基于移动通信网络(如：5G网络)实现的虚拟局域网，主要包括至少一个用户面数据网关，如图2A中用户面数据网关203-205，每个用户面数据网关都与控制面数据网关连接(例如，用户面数据网关203-205都与控制面数据网关202连接)，以接受控制面数据网关的管理；当移动局域网包含多个用户面数据网关时，不同用户面数据网关之间彼此连接(例如，用户面数据网关203与用户面数据网关204连接，用户面数据网关203通过数据网络216与用户面数据网关205连接)，以为移动局域网群组的成员用户设备之间的通信提供服务。多个移动局域网群组可以共享同一个用户面数据网关。
应理解，图2A中关于用户面数据网关之间的拓扑关系是示例性的，并非限定，例如，控制面数据网关还可以触发在用户面数据网关204与用户面数据网关205之间建立数据网关间隧道，这样用户设备212发送给用户设备213的数据包就不必经用户面数据网关203绕路转发，而可以直接从用户面数据网关204发送到用户面数据网关205。
应理解，在有些应用场景下，移动局域网中的部分用户设备也可以是有线通信设备，如台式机。
移动局域网可以是3GPP标准规范定义的5G局域网(5G LAN-Virtual Network，5G LAN VN)。5G局域网可提供UE和UE之间的点对点的数据传输，在进行数据传输之前，需要在两个UE的协议数据单元(protocol data unit，PDU)会话之间建立关联。同一5G局域网群组的所有成员UE的PDU会话可以由同一个会话管理功能(session management function，SMF)设备管理控制，也可以由多个SMF设备管理控制，本申请实施例以同一5G局域网群组的所有成员UE的PDU会话由同一个SMF设备管理控制为例说明技术方案，由多个SMF设备管理控制的场景，则每个SMF设备的相关操作可参考本申请实施例。UE之间的数据包的传输是基于用户面功能(user plane function，UPF)设备上的路由规则进行的，该路由规则由SMF设备下发到UPF设备。
移动局域网群组：指可接入移动局域网的成员用户设备的集合，该集合中的每一个成员用户设备都可以通过各自的接入设备与各自的用户面数据网关连接，如用户设备210通过接入设备206与用户面数据网关203连接；基于用户面数据网关的数据交换或路由转发服务，不同成员用户设备之间可以进行IP类型或非IP类型的通信；该集合中的不同成员用户设备可以分布在不同的地理区域。
移动局域网群组的成员用户设备可以增加或者删除。移动局域网群组的成员用户设备不一定全部同时接入移动局域网。图2A中示例的是接入移动局域网的4个成员用户设备，应理解，实际应用中，移动局域网群组中的成员用户设备可以根据需要接入或者离开移动局域网。
本申请实施例中，移动局域网群组有两个标识；一个是外部群组标识，主要在移动 网络运营商外部系统中使用；另一个是内部群组标识，由统一数据管理(unified data management，UDM)设备分配，主要在移动网络运营商内部系统中使用；统一数据管理设备建立外部群组标识与内部群组标识之间的映射关系。除非另有说明，本申请实施例中的“群组标识”均指移动局域网群组的内部群组标识。
移动局域网群组可以是3GPP标准规范定义的5G局域网群组(5G LAN Group)。
群内通信：也称为“局域网内部通信”、“私有通信”，指移动局域网群组的至少两个成员用户设备之间的通信。
移动局域网业务：是指基于至少一个用户面数据网关为移动局域网群组的成员用户设备提供群内通信的业务；移动局域网业务的群组标识是指该移动局域网群组的标识；3GPP标准规范定义的5G局域网类型业务(5G LAN-Type service)属于一种移动局域网业务。
使用量：指特定时间范围内上报给计费处理设备用于计费处理的传输或消耗业务单元的数量，本申请实施例中，使用量信息包括业务单元的数量、传输方向等，其中，业务单元可以是流量或者时长等。
上行流量：指在特定时间范围内从成员用户设备到用户面数据网关方向流动的字节数。
下行流量：指在特定时间范围内从用户面数据网关到成员用户设备方向传输的字节数。
群内通信方式：移动局域网业务里成员用户设备之间的数据交换方式，具体地，至少有以下三种不同的群内通信方式：
(1)单播，是指两个成员用户设备之间的通信，也称为“1:1通信”、“一对一通信”或“点对点通信”等；
(2)多播，是指一个成员用户设备与多个其他成员用户设备之间的通信，即：一个成员用户设备同时给多个成员用户设备发送数据包，实现上，用户面数据网关将一个成员用户设备发送的数据包分发给多个其他成员用户设备，也称为“1:N通信”、“一对多通信”或“点对多点通信”等；
(3)广播，是指一个成员用户设备与所有其他接入移动局域网的成员用户设备之间的通信，即：一个成员用户设备向移动局域网群组内所有在线的成员用户设备发送数据包。
控制面数据网关：用于为移动局域网群组的成员用户设备使用移动局域网业务而选择用户面数据网关，管理成员用户设备的数据连接会话，以及指示用户面数据网关之间建立隧道，向用户面数据网关下发数据流的转发规则。
控制面数据网关可以是3GPP标准规范定义的PGW-C(packet data network gateway for control plane，控制面分组数据网关)或者SMF(session management function，会话管理功能)设备(如图4A SMF设备402)。
应理解，实际应用中，一个通信系统中可以有多个控制面数据网关，每个控制面数据网关可以管理多个移动局域网的群内通信。
数据连接会话：为用户设备与用户面数据网关之间的联结(association)，用于为用户设备与被访问网络或者与其他用户设备之间的通信提供连接服务；其创建过程可以由用户设备发起，其拆除过程可以由用户设备发起，也可以由其他网络设备发起。本 申请实施例有时候也将数据连接会话简称为“数据会话”或“会话”。
数据连接会话可以是3GPP标准规范定义的IP-CAN(IP-connectivity access network，IP连通性接入网)会话、协议数据单元会话(protocol data unit session，PDU会话)(如图4A中的PDU会话410P)，也可以是其他形式的会话，对此本申请实施例不做限定。
本申请实施例中的数据连接会话，均指需要计费处理的数据连接会话，不包括免费的或不需要计费处理的数据连接会话。
移动局域网数据连接会话：指用于移动局域网群组的群内通信的数据连接会话，如图2B中的210P-213P；为叙述方便，本申请实施例将移动局域网数据连接会话简称为“群内会话”。
QoS流：是指数据连接会话中QoS差异化的最小粒度的转发处理，通常用QFI(QoS Flow identifier，QoS流标识)标识一个QoS流。
用户面数据网关：为移动局域网群组提供群内通信服务的核心网网元，用于为移动局域网群组的成员用户设备创建群内会话；例如，参见图2B，在控制面数据网关202的管理下，用户面数据网关203为用户设备210和211分别建立群内会话210P和211P，用户面数据网关204为用户设备212建立群内会话212P，用户面数据网关205为用户设备213建立群内会话213P。在此基础上，为实现移动局域网群组的群内通信，用户面数据网关还用于在不同群内会话之间(如在群内会话210P与213P之间)转发数据包；为叙述方便，本申请实施例将群内会话的数据包被该群内会话的用户面数据网关传输至另一个群内会话的途径，称为该群内会话的群内转发方式，具体将以用户面数据网关203为例进一步说明，参见图2B。
用户面数据网关可以是3GPP标准规范定义的PGW-U(packet data network gateway for user plane，用户面分组数据网关)或PSA(PDU session anchor，PDU会话锚点)UPF(User Plane Function，用户面功能)设备(如图4A中的PSA UPF 403-405)等。
图2B为本申请实施例提供的群内转发方式的示意图，包括以下方式：
(1)通过本地数据交换服务转发：在控制面数据网关202的管理下，用户面数据网关203提供本地数据交换服务LS-210-211，使得群内会话210P中的数据包被转发至群内会话211P或者使得群内会话211P中的数据包被转发至群内会话210P，从而使得用户设备210可以与用户设备211通信；为叙述方便，本申请实施例将这种通过用户面数据网关的本地数据交换服务，在同属于该用户面数据网关的两个群内会话之间转发数据包的方式或途径，称为通过本地数据交换服务转发，简称为本地交换转发。
(2)通过数据网关间隧道转发：在控制面数据网关202的管理下，用户面数据网关203与用户面数据网关204交互，建立数据网关间隧道TN-203-204，使得群内会话210P中的数据包被转发至群内会话212P，或者使得群内会话212P中的数据包被转发至群内会话210P，从而使得用户设备210可以与用户设备212通信。为叙述方便，本申请实施例将这种通过两个用户面数据网关之间的隧道，在分别属于这两个用户面数据网关的两个群内会话(或其中的数据业务)之间转发数据包的方式或途径，称为通过数据网关间隧道转发，简称网关隧道转发。
数据网关间隧道可以是3GPP标准规范定义的N19隧道(如图4A中N19隧道N19-403-404)。
(3)通过数据网络转发：在控制面数据网关202的管理下，，群内会话210P中的数据包被传输至数据网络216，然后由数据网络216转发至群内会话213P，或者使得群内会话213P中的数据包被传输至数据网络216，然后由数据网络216转发至群内会话210P，从而使得用户设备210可以与用户设备213通信。为叙述方便，本申请实施例将这种两个用户面数据网关的群内会话之间转发数据包的方式或途径，称为通过网关网络间接口转发，简称数据网络转发。
用户面数据网关与数据网络的接口可以是3GPP标准规范定义的N6接口(如图4A的N6接口N6-403-DN和N6-405-DN)。
应理解，实际应用中，一个移动局域网中可以有更多或更少的用户面数据网关，具体数量与移动局域网群组的成员用户设备的数量、地理位置以及用户的需求相关，属于本领域现有技术。
例如，一个移动局域网可以由用户面数据网关203、接入设备206-207、用户设备210-211等设备组成；该局域网中只有一个用户面数据网关，有本地数据交换服务，但没有数据网关间隧道和网关网络间接口。
再如，一个移动局域网可以由用户面数据网关203-204、接入设备206-208、用户设备210-212等设备组成；该局域网中有两个用户面数据网关，有本地数据交换服务，有数据网关间隧道，但没有网关网络间接口。
再如，一个移动局域网可以由用户面数据网关203、用户面数据网关205、接入设备206-207、接入设备209、用户设备210-211、用户设备213等设备组成；该局域网中有两个用户面数据网关，有本地数据交换服务，有网关网络间接口，但没有数据网关间隧道。
接入设备：可以是无线接入设备，也可以是有线接入设备。其中，无线接入设备通常为3GPP标准规范定义的NG-RAN，包括但不限于eNB(evolved NodeB，演进型基站)、gNB(gNodeB，5G基站)。
下面以用户设备210为例，描述群内通信时数据包的端到端传输路径，如表1所示。
表1
Figure PCTCN2022072382-appb-000001
表1中数据的含义解释如下：
第一行：当用户设备210与用户设备211进行群内通信时，数据包在用户设备210、数据连接会话210P、用户面数据网关203的本地数据交换服务LS-210-211、数据连接会话211P和用户设备211之间(单向或双向)传输；
第二行：当用户设备210与用户设备212进行群内通信时，数据包在用户设备210、数据连接会话210P、用户面数据网关203与用户面数据网关204之间的隧道TN-203-204、数据连接会话212P和用户设备212之间(单向或双向)传输；
第三行：当用户设备210与用户设备213进行群内通信时，数据包在用户设备210、数据连接会话210P、用户面数据网关203与数据网络之间的接口IF-203-DN、数据网络 与用户面数据网关205之间的接口IF-205-DN、数据连接会话213P和用户设备213之间(单向或双向)传输。
综上可见，相对于图1所示的通信系统，图2A所示的通信系统中的数据包的传输至少存在以下特点：
a)不同用户设备传输的数据包是相关的，从而它们的使用量也是相关的，例如，当用户设备210与用户设备211进行群内通信时，前者的上行数据包最后成为了后者的下行数据包，从而，前者的上行使用量等于后者的下行使用量。
b)用户设备的数据包经过运营商通信网络的环节更多，例如，当用户设备210与用户设备212进行群内通信时，二者之间的传输的数据包不仅经过二者的数据连接会话210P和212P，还经过数据网关间隧道TN-203-204，这就需要运营商投入额外的网络资源。
c)用户设备的数据包被转发的面更广，例如，当用户设备210的群内通信方式为多播或广播时，针对用户设备210传来的数据包，用户面数据网关203将需要转发给多个用户设备，这也需要运营商投入更多的网络资源。
因此，假如直接将图1所示的通信系统的计费处理方法应用于图2A所示的通信系统，至少存在以下三个方面的问题。
1)图1所示的计费处理方法不能确定每一个成员用户设备的使用量是否用于群内通信，从而无法采用相应的费率进行批价，也无从获知相应的移动局域网群组的标识，从而无法将不同成员用户设备的使用量进行关联处理；在某些计费需求场景下，这将导致计费不准确的问题；例如，在计费需求为按端到端传输服务进行计费的情况下，将导致重复计费，因为针对同一份使用量，在一个成员用户设备(如用户设备210)上计费处理一次，在与其进行群内通信的另一个成员用户设备(如用户设备211)上还要再计费处理一次，其原因在于无法确定二者的相关性。
2)图1所示的计费处理方法只能针对每一个用户设备的会话环节的使用量进行计费处理，而无法对转发环节的使用量进行计费处理；在某些计费需求场景下，这也将导致计费不准确的问题；例如，在按网络传输服务计费的情况下，由于缺乏转发环节的使用量信息，将导致计费结果与运营商为保障群内通信QoS所作出的贡献不匹配，这也是一种计费不准确的体现。
3)图1所示的计费处理方法并不会根据每个用户设备的群内通信方式确定费率，相当于默认按单播的费率批价，
为此，本申请实施例在图2所示通信系统基础上增加了计费触发模块和计费处理模块，其功能分别简要描述如下。
计费触发模块的功能包括但不限于：向计费处理模块上报局域网计费信息(即用于对移动局域网群组的群内通信进行计费处理的信息，例如，群内通信相关的使用量信息、群内通信相关的配额申请信息)，根据计费处理模块返回的局域网计费处理结果(即对局域网计费信息进行计费处理的结果)管理群内通信；这些功能可以叠加到3GPP标准规范定义的CTF(Charging Trigger Function，计费触发功能)上，也可以独立于CTF，成为诸如“移动局域网计费触发功能”的模块或组件。
计费处理模块的功能包括但不限于：对计费触发模块上报的局域网计费信息进行计费处理，例如，基于群内通信相关的使用量信息进行账户扣减、生成计费话单(Charging  Data Record，CDR)等操作，基于群内通信相关的配额申请信息授予相应的配额等，并向计费触发模块返回计费处理的结果，如使用量处理成功的指示信息、计费话单写入成功的指示信息、授予的配额等；这些功能可以叠加到3GPP标准规范定义的CHF上，也可以独立于CHF，成为诸如“移动局域网计费处理功能”的模块或组件；此外，计费处理模块还可以包含账单输出功能，用于为移动局域网群组输出账单。
本申请实施例不限定这两个模块的部署方式，例如，可以采用如图3A所示的方式部署，还可以采用其他方式部署，例如将计费处理模块所包含的多个功能分别部署到不同的物理设备上。在一种可能的方案中，计费处理模块可以部署到现有针对单个用户设备进行计费处理的计费处理设备上，也可以部署在专门用于对移动局域网进行计费处理的设备上，例如“移动局域网计费处理设备”。
图3A为本申请实施例提供的第二通信系统的架构图，该通信系统是在图2A所示的通信系统基础上，将计费触发模块部署到控制面数据网关202，增加了包含计费处理模块的计费处理设备201而得；该通信系统包含了本申请实施例提供的第一种计费处理系统，用于对移动局域网业务进行计费处理；该计费处理系统包含控制面数据网关202和计费处理设备201，其中，控制面数据网关202向计费处理设备201提供移动局域网业务相关的计费信息，使计费处理设备201对移动局域网业务进行计费处理。需说明，图2B和3A均基于图2A而得，为了简化拓扑，本申请实施例将其中的接入设备、用户设备、数据网络等隐藏(而非移除)。
为了叙述方便，本申请实施例将包含计费触发模块的设备，如图3A中的控制面数据网关202和图4A中SMF设备402，统称为“计费触发设备”，将包含计费处理模块的设备，如图3A中计费处理设备201和图4A中CHF设备401，统称为“计费处理设备”。本申请实施例中计费触发设备和计费处理设备的个数是示例性的，不是限定，实际应用中，一个通信系统可以包含多个计费触发设备和多个计费处理设备。
下面结合局域网计费信息的具体内容，进一步描述计费触发设备与计费处理设备的交互流程。
在一种可能的方案中，局域网计费信息包含成员数据连接会话的计费信息，其中，成员数据连接会话为成员用户设备的数据连接会话，而成员用户设备为移动通信局域网群组中的用户设备，则计费触发设备与计费处理设备的交互流程如图3B所示。
图3B为本申请实施例提供的第一计费处理方法的流程图，该计费处理方法用于对移动局域网业务进行计费处理，主要包括以下步骤：
步骤310：计费触发设备获取成员数据连接会话的计费信息。
具体地，计费触发设备在计费上报触发条件满足时，例如，在数据连接会话创建时、或者在定时上报的时间点到达时，构建成员数据连接会话的计费信息或者从用户面数据网关获取成员数据连接会话的计费信息，该计费信息包含以下一项或多项：
1)第一计费数据，包含成员数据连接会话中的使用量和/或配额申请量；
2)第一业务指示信息，用于指示成员用户设备的数据连接会话用于群内通信；
3)群组标识，为群内通信对应的移动局域网群组的内部群组标识；
4)群内转发方式，为第一计费数据对应的群内转发方式；
5)群内通信方式，即成员用户设备的群内通信方式；
可选地，计费触发设备可以将计费触发条件发送给用户面数据网关，这样，用户面数据网关可以在计费触发条件满足时，向计费触发设备发送成员数据连接会话的使用量相关的信息。
步骤311：计费触发设备向计费处理设备发送计费请求消息，该请求消息包含上述成员数据连接会话的计费信息。
具体地，计费触发设备构建计费请求消息，该请求消息携带上述成员数据连接会话的计费信息；在计费处理设备提供服务化接口的场景下，该请求消息可以是计费资源创建请求消息(ChargingResourceCreateRequest)、计费资源更新请求消息(ChargingResourceUpdateRequest)或者计费资源删除请求消息(ChargingResourceDeleteRequest)。
步骤312：计费处理设备对成员数据连接会话的计费信息进行计费处理。
具体地，计费处理设备接收步骤311的计费请求消息，从中解析出成员数据连接会话的计费信息，进而执行以下一项或多项操作。
1)计费处理设备基于第一业务指示信息确定成员用户设备的数据连接会话用于群内通信，进而对该成员用户设备进行接入认证，即对该成员用户设备是否可使用移动局域网业务进行认证，或者说确定是否允许该成员用户设备进行群内通信；可选地，计费处理设备还可以基于第一业务指示信息确定费率，再将该费率应用到第一计费数据的计费处理，包括：基于该费率对使用量进行账户扣减、基于该费率和配额申请量进行账户冻结、将使用量和该费率写入计费话单等；可选地，计费处理设备保存该第一业务指示信息，例如，将该第一业务指示信息与该成员用户设备的数据连接会话的标识，或者将该第一业务指示信息与该成员用户设备的数据连接会话的计费资源的标识对应存储；
2)计费处理设备根据群组标识确定成员用户设备所在移动局域网群组对应的账户，或者在成员数据连接会话的计费话单中记录该群组标识，或者以群组标识为关联标识累积移动局域网群组的使用量，或者基于群组标识查询移动局域网群组对应的外部群组标识(例如从统一数据管理设备查询)，以基于外部群组标识对成员数据连接会话的计费信息进行计费处理(例如根据外部群组标识确定账户或者进行计费话单关联以关联应用层计费信息或者关联移动局域网业务的客户信息，再如，在成员数据连接会话的计费话单中记录外部群组标识)；可选地，计费处理设备保存该群组标识，例如，将该群组标识与成员数据连接会话的标识对应存储，或者将该群组标识与成员数据连接会话的计费资源的标识对应存储；
3)计费处理设备基于群内转发方式对第一计费数据进行计费处理；例如，计费处理设备将根据第一计费数据对应的群内转发方式确定的费率并应用到第一计费数据的计费处理，包括：基于该费率对使用量进行账户扣减、基于该费率和配额申请量进行账户冻结；再如，计费处理设备在成员数据连接会话的计费话单中记录该第一计费数据及对应的群内转发方式；
4)计费处理设备基于群内通信方式对第一计费数据进行计费处理；例如，计费处理设备根据该群内通信方式确定的费率应用到第一计费数据的计费处理，包括：基于该费率对使用量进行账户扣减、基于该费率和配额申请量进行账户冻结；再例如，计费处理设备在成员数据连接会话的计费话单中记录该群内通信方式。
计费处理设备基于上述一项或多项操作，生成成员数据连接会话的计费处理结果；示例性地，该计费处理结果包含认证的结果(认证成功的指示信息或者认证失败的指示信息)、授予的配额、使用量扣减结果(扣减成功的指示信息或者扣减失败的指示信息)、写入计费话单的结果(写入计费话单成功的指示信息或者写入计费话单失败的指示信息)等。
步骤313：计费处理设备向计费触发设备发送计费响应消息，该响应消息包含上述成员数据连接会话的计费处理结果。
具体地，计费处理设备构建计费响应消息,将其发送给计费触发设备，该响应消息携带上述成员数据连接会话的计费处理结果。随后，计费触发设备接收该计费响应消息。
计费触发设备和计费处理设备可以反复执行类似步骤310-步骤313的过程，以便持续对成员用户设备的数据连接会话进行计费处理、以及对其他成员用户设备的数据连接会话进行计费处理。
步骤349：计费处理设备对移动局域网群组进行计费处理。
该步骤是可选的。在计费模式为离线计费的情况下，通过上述过程，计费处理设备保存了不同成员用户设备的数据连接会话在不同时间段的计费话单，计费处理设备根据群组标识将这些计费话单相关联，生成移动局域网群组的计费话单。
具体地，在预设时间段内，计费处理设备获取此前生成的移动局域网成员用户设备的数据连接会话的计费话单，对不同成员用户设备或者同一用户设备的数据连接会话的计费话单进行关联操作，得到汇总的移动局域网的计费话单；其中，关联操作包括纵向关联和横向关联：
-纵向关联：指计费处理设备将同一成员用户设备的数据连接会话在不同时间点的计费信息相关联，具体可以以用户设备的标识作为关联标识；
-横向关联：指计费处理设备将同一移动局域网群组的不同成员用户设备的数据连接会话的计费信息相关联，具体可以以群组标识作为关联标识。
可选地，计费处理设备还可以根据账户扣减的结果，触发用户面数据网关控制各成员用户设备的数据连接会话的QoS。
图3B所示的计费处理方法，使得计费处理设备能基于移动局域网的相关信息对数据连接会话中的第一计费数据进行计费处理，可以针对移动局域网业务进行精细化的计费处理，提高计费的准确性并灵活支持多种计费需求；具体还可以进一步参考本申请其他实施例，如图5对应的方法。
在另一种可能的方案中，除了成员数据连接会话的计费信息外，局域网计费信息还包含数据网关间隧道(如TN-203-204)的计费信息，则计费触发设备与计费处理设备的交互流程如图3C所示。
图3C为本申请实施例提供的第二计费处理方法的流程图，该计费处理方法用于对移动局域网业务进行计费处理，主要包括以下步骤：
步骤350-步骤353：计费触发设备与计费处理设备对成员数据连接会话的计费信息进行计费处理。该过程与步骤310-步骤313的过程类似，不再赘述。根据计费需求，在本方法流程中可以不执行该过程。
步骤360：计费触发设备获取数据网关间隧道的计费信息。
具体地，计费触发设备在计费上报触发条件满足时，例如，在数据网关间隧道创建时、或者在定时上报的时间点到达时，构建数据网关间隧道的计费信息或者从用户面数据网关获取数据网关间隧道的计费信息，该计费信息包含以下一项或多项：
1)第二计费数据，包含通过数据网关间隧道传输的使用量；
2)隧道信息，即数据网关间隧道的信息，如隧道的标识等；
3)第二业务指示信息，用于指示数据网关间隧道用于群内通信；
4)群组标识，即群内通信对应的移动局域网群组的内部群组标识；
5)传输方向，即第二计费数据对应数据包在数据网关间隧道中传输的方向。
可选地，计费触发设备可以将计费触发条件发送给用户面数据网关，这样，用户面数据网关可以在计费触发条件满足时，向计费触发条件发送数据网关间隧道的计费信息。
步骤361：计费触发设备向计费处理设备发送计费请求消息，该请求消息包含上述数据网关间隧道的计费信息。
具体地，计费触发设备构建计费请求消息，该请求消息携带上述数据网关间隧道的计费信息；在计费处理设备提供服务化接口的场景下，该请求消息可以是计费资源创建请求消息、计费资源更新请求消息或者计费资源删除请求消息。
步骤362：计费处理设备对数据网关间隧道的计费信息进行计费处理。
具体地，计费处理设备接收步骤361的计费请求消息，从中解析出数据网关间隧道的计费信息，进而执行以下一项或多项操作。
1)计费处理设备基于隧道信息，确定计费请求消息包含数据网关间隧道的计费信息(以区别于成员数据连接会话的计费信息)；
2)计费处理设备基于第二业务指示信息确定数据网关间隧道用于群内通信，进而确定数据网关间隧道对应的费率，再将该费率应用到第二计费数据的计费处理；可选地，计费处理设备保存该第二业务指示信息，例如，将该第二业务指示信息与该数据网关间隧道的标识对应存储，或者将该第二业务指示信息与该数据网关间隧道的计费资源的标识对应存储；
3)计费处理设备根据群组标识确定数据网关间隧道所服务的移动局域网群组对应的账户；或者，计费处理设备在所述数据网关间隧道的计费话单中记录所述群组标识；或者，计费处理设备基于所述群组标识查询所述移动局域网群组对应的外部群组标识，以基于所述外部群组标识对所述数据网关间隧道的计费信息进行计费处理(例如，在所述数据网关间隧道的计费话单中记录外部群组标识)；可选地，计费处理设备保存该群组标识，例如，将该群组标识与该数据网关间隧道的标识对应存储，或者将该群组标识与该数据网关间隧道的计费资源的标识对应存储；
4)基于传输方向对第二计费数据进行计费处理，例如，在账户扣减过程采用传输方向对应的费率(假设费率因传输方向不同而异)，或者将使用量和传输方向写入计费话单，或者将使用量和基于传输方向确定的费率写入话计费单。
计费处理设备基于上述一项或多项操作，生成数据网关间隧道的计费处理结果；示例性地，该计费处理结果包含授予的配额、使用量扣减成功的指示信息、使用量已写入计费话单的指示信息等。
步骤363：计费处理设备向计费触发设备发送计费响应消息，该响应消息包含上述 数据网关间隧道的计费处理结果。
具体地，计费处理设备构建计费响应消息,将其发送给计费触发设备，该响应消息携带上述数据网关间隧道的计费处理结果。随后，计费触发设备接收该计费响应消息。
计费触发设备和计费处理设备可以反复执行上述步骤360-步骤363的过程，以便持续对数据网关间隧道进行计费处理、以及对移动局域网中其他数据网关间隧道进行计费处理。
步骤399：计费处理设备对移动局域网群组进行计费处理。
该步骤是可选的。在计费模式为离线计费的情况下，通过上述过程，计费处理设备保存了不同成员用户设备的数据连接会话在不同时间段的计费话单，以及不同数据网关间隧道在不同时间段的计费话单，计费处理设备根据群组标识将这些计费话单相关联，生成移动局域网群组的计费话单。
计费处理设备根据群组标识，进行各种关联操作，例如，将具有相同群组标识的数据网关间隧道的计费话单进行关联。
关于将不同成员用户设备的数据连接会话的计费话单的关联操作，可参考步骤349中的相关描述，这里不再赘述。
图3C所示的计费处理方法，使得计费处理设备能进一步基于移动局域网的相关信息对数据网关间隧道的第二计费数据进行计费处理，可以进一步提高计费的准确性，实现按使用的网络资源计费；具体还可以进一步参考本申请其他实施例，如图6对应的方法流程。
图4A是本申请实施例提供的第三通信系统的架构图；该通信系统包括CHF设备401、SMF设备402及其所管理的5G局域网；5G局域网包括PSA UPF设备403-405、无线接入设备406a-409a(图4A中未显示)和5G局域网群组，5G局域网群组包括UE 410-413；UE 410与UE 411通过PSA UPF设备403的本地交换转发服务实现群内通信，具体参见图4B的相关描述；UE 410与UE 412通过PSA UPF设备403与PSA UPF设备404之间的N19隧道N19-403-404实现群内通信，具体参见图4C的相关描述；UE 410与UE 413通过PSA UPF设备403与DN(Data Network，数据网络)416之间的N6接口N6-403-DN，以及DN 416与PSA UPF设备405之间的N6接口N6-405-DN实现群内通信，具体参见图4D的相关描述；SMF设备402中包含CTF(相当于计费触发模块)，既管理5G局域网，又负责触发CHF设备对其群内通信的计费信息进行计费处理。因此，CHF设备401相当于上文所述计费处理设备，SMF设备402相当于上文所述计费触发设备。从而，该通信系统包含了本申请实施例提供的第二种计费处理系统，用于对5G局域网业务进行计费处理；该计费处理系统包含SMF设备402和CHF设备401。
图4A中，N4会话为SMF设备与PSA UPF设备之间的会话，SMF设备通过该会话管理PDU会话和N19隧道；为便于区分，本申请实施例将用于管理PDU会话的N4会话称为“普通N4会话”，将用于管理N19隧道的N4会话称为“隧道N4会话”。
图4A所示的5G局域网的拓扑结构是示例性的，并非限定；实际应用中，一个5G局域网可以包含更多或更少的PSA UPF设备，以及更多或更少的UE，PSA UPF设备之间的连接关系也可以不同，例如，PSA UPF设备404也可以通过N19隧道与PSA UPF设备405连接。有些场合下，“UPF设备”也被称为“UPF网元”。
图4B是本申请实施例提供的5G局域网中第一群内转发方式的示意图；其中，UE 410和UE 411都归属于PSA UPF设备403，UE 410的PDU会话与UE 411的PDU会话之间通过PSA UPF设备403的本地数据交换服务转发数据包，这样UE 410与UE 411之间用于群内通信的数据包的传输路径是：UE 410<->(R)AN 406a<->I-UPF设备406i<->PSA UPF设备403<->I-UPF设备407i<->(R)AN 407a<->UE 411。
图4C是本申请实施例提供的5G局域网中第二群内转发方式的示意图；其中，UE 410和UE 412分别归属于PSA UPF设备403、PSA UPF设备404，UE 410的PDU会话与UE 412的PDU会话之间通过PSA UPF设备403与PSA UPF设备404之间的N19隧道转发数据包，这样UE 410与UE 412之间用于群内通信的数据包的传输路径是：UE 410<->(R)AN 406a<->I-UPF设备406i<->PSA UPF设备403<->PSA UPF设备404<->I-UPF设备408i<->(R)AN 408a<->UE 412。
图4D是本申请实施例提供的5G局域网中第三群内转发方式的示意图；其中，UE 410和UE 413分别归属于PSA UPF设备403、PSA UPF设备405，UE 410的PDU会话与UE 413的PDU会话之间通过DN 416转发数据包，这样UE 410与UE 413之间用于群内通信的数据包的传输路径是：UE 410<->(R)AN 406a<->I-UPF设备406i<->PSA UPF设备403<->DN 416<->PSA UPF设备405<->I-UPF设备409i<->(R)AN 409a<->UE 413。
图5是本申请实施例提供的第三计费处理方法的流程图，该计费处理方法用于对5G局域网业务进行计费处理；其中，除非另有特别说明，“SMF”是指图4A中的SMF设备402，“CHF”是指图4A中的CHF设备401，“5G局域网群组”是指图4A中的5G局域网群组，“UE”是指UE 410，“UPF”是指PSA UPF设备403，“PDU会话”是指PDU会话410P；该方法流程主要包括如下步骤：
步骤501：SMF接收UE发送的PDU会话建立请求消息，确定PDU会话用于5G局域网群组的群内通信。
具体地，当UE里的5G局域网应用程序运行、致使UE要接入5G局域网时，UE向AMF(Access Management Function，接入管理功能)设备发送第一PDU会话建立请求消息，以请求创建PDU会话；AMF设备继而基于接收到的第一PDU会话建立请求消息向SMF发送第二PDU会话建立请求消息，这两个请求消息的示例如下：
Figure PCTCN2022072382-appb-000002
其中：“S-NSSAI”为单网络切片选择支撑信息(Single Network Slice Selection Assistance Information)，携带5G局域网对应的网络切片的标识。
可选地，UE可以从本地保存的关于5G局域网的配置信息中读取Dnn51和S-nssai51，以构造第一PDU会话建立请求消息。
具体地，SMF接收到第二PDU会话建立请求消息，从中解析出UEID、Dnn51和S-nssai51，再以UEID、Dnn51和S-nssai51作为查询条件从统一数据管理设备查询得到UE的签约信息，进而根据签约信息确定所请求创建的PDU会话用于5G局域网的群内通信。
SMF触发UPF创建PDU会话的过程为现有技术，不再赘述。
步骤502：SMF向CHF发送计费资源创建请求消息，该请求消息携带SesId51、UEId51、SrvInd51和GrpId51。
具体地，SMF构造计费资源创建请求消息(如ChargingDataRequest[Create])，或者ChargingResourceCreateRequest)并将其发送给CHF，以请求CHF为PDU会话创建计费资源，该请求消息携带SesId51、UEId51、SrvInd51和GrpId51；其中，SrvInd51为SMF生成的第一业务指示信息，用于指示(indicate)PDU会话用于群内通信，GrpId51是SMF为5G局域网群组分配的标识；SrvInd51和GrpId51均是可选的。
示例性的计费资源创建请求消息如下：
Figure PCTCN2022072382-appb-000003
其中，UEId51为5G局域网群组成员标识，具体可以是GPSI(generic public subscription identifier，一般公共订阅标识符)，也可以是SUPI(subscription permanent identifier，用户永久标识)。
步骤503：CHF创建计费资源、保存SrvInd51和GrpId51。
具体地，CHF接收上述计费资源创建请求消息，从中解析出SesId51、UEId51、SrvInd51和GrpId51，进而执行以下操作：
1)基于SrvInd51确定PDU会话用于群内通信；如果上述计费资源创建请求消息不包含SrvInd51，CHF可以根据UEId51查询UE的签约信息，并根据签约信息确定PDU会话用于群内通信，且生成SrvInd51这个指示信息；
2)可选的，对UE进行接入认证，以确定允许UE使用5G局域网提供的群内通信业务；例如，CHF可以根据UEId51查询UE的签约信息，进而判断是否允许UE使用5G局域网提供的群内通信业务；再如，CHF根据GrpId51查找5G局域网群组对应的账户，再根据该账户的余额情况，判断是否允许UE使用5G局域网提供的群内通信业务；如果计费资源创建请求消息中不包含GrpId51，CHF可以根据UEId51查询UE的签约信息，并根据签约信息确定5G局域网群组的标识GrpId51。
3)为PDU会话创建相应的计费资源，并为该计费资源分配标识为ResId51。
可选地，CHF还保存上述接收到的或者确定出的SrvInd51和GrpId51，例如，将 SrvInd51、GrpId51与ResId51对应存储。
步骤504：CHF向SMF发送计费资源创建响应消息，该响应消息携带ResId51。
具体地，CHF构造计费资源创建响应消息(如ChargingDataResponse[Create],或ChargingResourceCreateResponse)并将其发送给SMF，该响应消息携带ResId51。
示例性的计费资源创建响应消息如下：
ChargingResourceCreateResponse{
    "RESID":"RES410P"//ResId51，PDU会话的计费资源的标识
}
相应地,SMF接收上述计费资源创建响应消息，从中解析出ResId51，这样后续可以基于ResId51上报PDU会话的使用量，SMF也可以根据该响应消息确认UE的接入认证成功，即CHF允许UE基于5G局域网中的网络设备进行群内通信，进而通过普通N4会话(即面向PDU会话的N4会话，区别于面向N19隧道的N4会话)向UPF下发计费规则，该计费规则包含PDR(packet detection rule，包检测规则)、URR(usage reporting rule，使用量上报规则)；在一种可能的方案中，所述PDR、URR指示UPF检测并上报本地转发、通过N6接口转发、或者通过N19隧道转发的使用量。
步骤505：SMF确定配额申请量RSU51、群内转发方式Fwd51和群内通信方式Com51。
具体地，SMF根据本地配置信息或者策略控制设备提供的计费策略，确定配额申请量RSU51(例如为5M)，以生成配额申请信息。
可选地，SMF还确定上述配额申请量RSU51对应的数据包的群内转发方式Fwd51，其示例性的取值及对应含义为：“Local”-表示经PSA UPF本地转发、“N19”-表示经PSA UPF间N19隧道转发、“N6”-表示经PSA UPF与DN之间的N6接口转发。
可选地，SMF还确定UE的群内通信方式Com51，其示例性的取值及对应含义为：“Unicast”-表示单播、“Multicast”-表示多播，“Broadcast”-表示广播。
步骤506：SMF向CHF发送计费资源更新请求消息，该请求消息包含ResId51、RSU51、SrvInd51、GrpId51、Fwd51和Com51。
具体地，SMF基于步骤505确定的配额申请量RSU51，构建计费资源更新请求消息(如ChargingDataRequest[Update],或ChargingResourceUpdateRequest)，将其发送给CHF，以请求CHF为PDU会话更新计费资源，该请求消息包含ResId51、RSU51、Fwd51、SrvInd51、GrpId51和Com51。
示例性的计费资源更新请求消息如下：
Figure PCTCN2022072382-appb-000004
Figure PCTCN2022072382-appb-000005
上述计费资源更新请求消息中RSU51和Fwd51的并列关系，只是一种示例，并非限定，实际应用中可以采用其他的结构关系，例如，Fwd51可以放在RSU-INF数据结构外部，与SrvInd51等并列。
如果步骤503中，CHF已经保存了SrvInd51和GrpId51，则可选地，为了避免冗余传输信息，上述计费资源更新请求消息可以不包含SrvInd51和GrpId51。
与步骤505相对应，在一种可能的技术方案中，上述计费资源更新请求消息也可以不包含Fwd51和Com51。
步骤507：CHF授予配额申请量RSU51对应的配额GSU51。
具体地，CHF接收步骤506中的计费资源更新请求消息，从中解析出ResId51、RSU51、Fwd51、SrvInd51、GrpId51和Com51，进而授予与RSU51对应的配额GSU51。
具体地，CHF可基于Fwd51、SrvInd51、GrpId51和Com51中的任意一项或任意组合进行批价，进而授予相应的配额GSU51；CHF还可以基于GrpId51确定5G局域网群组对应的账户，在基于RSU51授予相应的配额GSU51过程中使用该账户。
如果接收到的计费资源更新请求消息不包含SrvInd51或GrpId51，则CHF可以根据ResId51从本地获取此前存储的SrvInd51或GrpId51。
步骤508：CHF向SMF发送计费资源更新响应消息，该响应消息包含ResId51和GSU51。
具体地，CHF构建计费资源更新响应消息(如ChargingDataResponse[Update],或ChargingResourceUpdateResponse)，并将其发送给SMF，该计费资源更新响应消息包含ResId51和GSU51。
示例性的计费资源更新响应消息如下：
Figure PCTCN2022072382-appb-000006
相应地，SMF接收上述计费资源更新响应消息，从中解析出ResId51和GSU51，并管理GSU51的使用，即管理PDU会话对GSU51的消费。在一种可能的方案中，SMF将GSU51发送给UPF，由UPF管理PDU会话对GSU51的消费。
需说明，如果PDU会话的计费模式是离线计费，则SMF和CHF不执行步骤505-步骤508的过程(即申请配额的过程)。
步骤509：SMF确定使用量USU51、群内转发方式Fwd52、群内通信方式Com52。
具体地，SMF获取使用量USU51、相应的群内转发方式Fwd52和群内通信方式Com52。其中，Fwd52可以与Fwd51相同，也可以不同，Com52可以与Com51相同，也可以不同。
SMF可以通过普通N4会话获取使用量USU51，例如，SMF基于PCC(Policy and Charging Control，策略与计费控制)规则生成相应的PDR和URR，并通过普通N4会话 将PDR和URR发送给UPF，UPF通过普通N4会话上报URR对应的使用量USU51。
步骤510：SMF向CHF发送计费资源更新请求消息，该请求消息包含ResId51、USU51、Fwd52、SrvInd51、GrpId51和Com52。
具体地，SMF基于步骤509确定的USU51、Fwd52和Com52，构建计费资源更新请求消息，将其发送给CHF，该请求消息包含ResId51、USU51、Fwd52、SrvInd51、GrpId51和Com52。
示例性的计费资源更新请求消息如下：
Figure PCTCN2022072382-appb-000007
上述计费资源更新请求消息中USU51和Fwd52的并列关系，只是一种示例，并非限定，实际应用中可以采用其他的结构关系，例如，Fwd52可以放在USU-INF数据结构外部，与SrvInd51等并列。
此外，如果步骤503中，CHF已经保存了SrvInd51和GrpId51，则可选地，为了避免信息的冗余传输，上述计费资源更新请求消息可以不包含SrvInd51和GrpId51。
在一种可能的技术方案中，上述计费资源更新请求消息也可以不包含Fwd52和Com52。
在一种可能的技术方案中，上述RG51可以替换为PDU会话中其他粒度的数据连接业务的标识，如QoS流的标识。
步骤511：CHF对USU51进行计费处理。
具体地，CHF接收步骤510的计费资源更新请求消息，从中解析出ResId51、USU51、Fwd52、SrvInd51、GrpId51和Com52，进而对USU51进行计费处理。
具体地，CHF可基于Fwd52、SrvInd51、GrpId51和Com52中的任意一项或任意组合确定费率，以及基于GrpId51确定5G局域网群组对应的账户；如果计费模式为在线计费，则CHF基于所确定的费率和USU51对所确定的账户进行账户扣减，如果计费模式为离线计费，则CHF在PDU会话的计费话单中记录Fwd52、SrvInd51、GrpId51和Com52中的任一项或任意组合以及USU51。
如果接收到的计费资源更新请求消息不包含SrvInd51和GrpId51，则CHF可以根据ResId51从本地获取此前存储的SrvInd51和GrpId51。
可选地，CHF可以在该步骤中或者在后续步骤中以GrpId51为关联标识累积得到5G局域网群组的总使用量，该总使用量，可以用于对5G局域网群组的群内通信的QoS进 行控制，例如，对个PDU会话进行QoS控制；例如，假设CHF接收到的多个ChargingResourceUpdateRequest中"GRPID"值都为"GRP414"，则CHF将这些ChargingResourceUpdateRequest中PDU会话中的使用量进行累加，得到5G局域网群组的使用量。
步骤512：CHF向SMF发送计费资源更新响应消息，该响应消息包含ResId51和计费处理结果ChgRst51。
具体地，CHF构建计费资源更新响应消息，并将其发送给SMF，该计费资源更新响应消息包含ResId51和计费处理结果ChgRst51，其示例性的取值及对应含义为："SucInDeduction"-表示账户扣减成功，"SucInRecording"-表示计费话单写入成功。
示例性的计费资源更新响应消息如下：
Figure PCTCN2022072382-appb-000008
相应地，SMF接收该计费资源更新响应消息，从中解析计费处理结果，据此管理PDU会话，如维持PDU会话的放通以维持UE的群内通信业务。
应理解，上述步骤505-步骤512之间的过程，可以重复执行，直到确定PDU会话将被释放，转步骤513。
步骤513：SMF确定要删除计费资源，确定使用量USU52，确定群内转发方式Fwd53和群内通信方式Com53。
具体地，SMF接收到UE或者其他设备(如PCF设备)发送的释放PDU会话的请求消息，据此确定要触发CHF删除此前创建的计费资源；由于有未上报的使用量，因此，SMF获取PDU会话释放前的使用量USU52(假设是3M)、相应的群内转发方式Fwd53和群内通信方式Com53。其中，Fwd53可以与Fwd51或Fwd52相同，也可以不同，Com53可以与Com52或Com51相同，也可以不同。SMF获取USU52的方式可以参考步骤510中的相关描述，这里不再赘述。
步骤514：SMF向CHF发送计费资源删除请求消息，该请求消息包含ResId51、USU52、Fwd53、SrvInd51、GrpId51和Com53。
具体地，SMF基于步骤513确定的USU52、Fwd53和Com53，构建计费资源删除请求消息，将其发送给CHF，以请求CHF为PDU会话删除计费资源，该请求消息包含ResId51、USU52、Fwd53、SrvInd51、GrpId51和Com53。
示例性的计费资源更新请求消息如下：
Figure PCTCN2022072382-appb-000009
Figure PCTCN2022072382-appb-000010
类似地，计费资源删除请求消息可以不包含SrvInd51和GrpId51。
在一种可能的技术方案中，上述计费资源删除请求消息也可以不包含Fwd53和Com53。
步骤515：CHF对USU52进行计费处理，删除计费资源。
具体地，CHF接收步骤514的计费资源删除请求消息，从中解析出ResId51、USU52、Fwd53、SrvInd51、GrpId51和Com53，进而对USU53进行计费处理，具体可以参考步骤511中的相关描述。
如果接收到的计费资源删除请求消息不包含SrvInd51和GrpId51，则CHF可以根据ResId51从本地获取此前存储的SrvInd51和GrpId51。
完成对USU52进行计费处理之后，CHF删除此前创建的ResId51对应的计费资源，以回收该计费资源所占用的CHF上的计算资源，如内存、CPU资源等。
步骤516：CHF向SMF发送计费资源删除响应消息，该响应消息包含ResId51、计费处理结果ChgRst52和计费资源删除结果DelRst51。
具体地，CHF构建计费资源删除响应消息，并将其发送给SMF，该计费资源删除响应消息包含ResId51、计费处理结果ChgRst52和资源删除结果DelRst51，ChgRst52示例性的取值及对应含义与ChgRst51相同，不再赘述；DelRst51示例性的取值及对应含义为："SucInDeleting"-表示PDU会话对应的计费资源删除成功。
示例性的计费资源删除响应消息如下：
Figure PCTCN2022072382-appb-000011
相应地，SMF接收该计费资源删除响应消息，从中解析出ChgRst52和DelRst51，据此管理PDU会话，如释放PDU会话，以终止UE的群内通信业务。
在一种可能的方案中，SMF可以在步骤502之前确定RSU51和/或USU51，且使步骤502的创建计费资源请求消息携带将RSU51和/或USU51，从而，在步骤504中，SMF从CHF发送的计费资源创建响应消息中获取GSU51和/或ChgRst51。
以上步骤501-516为UE 410的群内通信的计费处理过程，可选地，该方法流程还可以包含5G局域网群组中其他UE的群内通信的计费处理过程，例如：
步骤521-536：UE 411的群内通信的计费处理过程。
可选地，SMF触发CHF对UE 411的群内通信进行计费处理，具体可以参考步骤501-516的过程。
步骤541-556：UE 412的群内通信的计费处理过程。
可选地，SMF触发CHF对UE 412的群内通信进行计费处理，具体可以参考步骤 501-516的过程。
步骤561-570：UE 413的群内通信的计费处理过程。
可选地，SMF触发CHF对UE 413的群内通信进行计费处理，具体可以参考步骤501-516的过程。
应理解，上述多个UE的群内通信的计费处理过程的顺序并不固定，可以是不同于上面的顺序，不同UE的群内通信的计费处理过程还可以并行进行。
步骤599：CHF对5G局域网群组进行计费处理。
在PDU会话的计费模式为离线计费的情况下，通过上述过程，CHF保存了不同UE的PDU会话在不同时间段的计费话单，CHF设备根据GrpId51将这些计费话单中的USU相关联，为5G局域网群组输出账单，举例如下。
假设组内通信情况如下：
(1)UE 410与UE 411、UE 412、UE 413进行广播方式群内通信，PDU会话(410P)中传输的数据包是5M，转发方式包括本地交换转发、通过N19隧道转发和通过N6接口转发；
(2)UE 411与UE 410和UE 412进行多播方式群内通信，PDU会话(411P)中传输的数据包是3M，转发方式包括通过本地交换转发、通过N19隧道转发；
(3)UE 412与UE 411进行单播方式群内通信，PDU会话(412P)中传输的数据包是2M，转发方式包括通过N19隧道转发；
(4)UE 413余UE 411进行单播方式群内通信，PDU会话(413P)中传输的数据包为1M，转发方式包括通过N6接口转发。
则某个时间段内，CHF写入计费话单的计费信息如表2所示，这些计费信息通过共同的群组标识“GRP414”关联到一起：
表2
编号 群组标识 UE 使用量 方向 群内转发方式 群内通信方式
1 GRP414 410 5M UL Local Broadcast
2 GRP414 411 5M DL Local -
3 GRP414 410 5M UL N19 Broadcast
4 GRP414 412 5M DL N19 -
5 GRP414 410 5M UL N6 Broadcast
6 GRP414 413 5M DL N6 -
7 GRP414 411 3M UL Local Multicast
8 GRP414 410 3M DL Local -
9 GRP414 411 3M UL N19 Multicast
10 GRP414 412 3M DL N19 -
11 GRP414 412 2M UL N19 Unicast
12 GRP414 411 2M DL N19 -
13 GRP414 413 1M UL N6 Unicast
14 GRP414 411 1M DL N6 -
其中，“UL”表示上行，“DL”表示下行，“Local”表示本地交换转发，“N19” 表示通过N19隧道转发，“N6”表示通过N6接口转发。假设运营商将Local的计费费率设为R、N6的计费费率设为2R，N19的计费费率设为3R。
如果要按端到端使用量计费，则CHF对上行使用量进行计费，即对表2编号为1、3、5、7、9、11、13中的使用量进行计费，得到费用是：
5M*R+5M*3R+5M*2R+3M*R+3M*3R+2M*3R+1M*2R＝50MR
如果要N19隧道使用量计费，则CHF对通过N19隧道的使用量进行计费，即对表2群内转发方式为“N19”的使用量进行计费，得到的费用是：
5M*3R*2+3M*3R*2+2M*3R*2＝60MR
图6是本申请实施例提供的第四计费处理方法的流程图，该计费处理方法用于对5G局域网业务进行计费处理；其中，除非另有特别说明，“SMF”是指图4A中的SMF设备402，“CHF”是指图4A中的CHF设备401，“5G局域网群组”是指图4A中的5G局域网群组，“UPF 403”是指PSA UPF设备403，“UPF 404”是指PSA UPF设备404；该方法流程主要包括如下步骤：
步骤601-步骤676：UE 410-UE 413的PDU会话的计费处理过程；该过程与步骤501-步骤576过程类似，不再赘述；根据计费需求，在本方法流程中可以不执行该过程。
步骤681：SMF在UPF设备403与UPF设备404之间建立N19隧道，生成隧道信息TunInf61。
具体地，SMF根据5G局域网的配置信息，确定需要在UPF设备403与UPF设备404之间建立N19隧道，以支持5G局域网的群内通信，进而分别向UPF设备403与UPF设备404下发建立N19隧道的指示信息，触发UPF设备403与UPF设备404交互、建立N19隧道。
进而，SMF生成隧道信息TunInf61，其中至少包含SMF为N19隧道分配的标识TEId61。
关于SMF与N19隧道的管理与计费信息的上报，进一步解释如下：
具体地，若SMF设备管理两个UPF设备(用于5G局域网通信)，换句话说，5G局域网的UPF设备集合包含两个UPF设备，假设这两个UPF设备之间建立了N19隧道，则SMF设备请求CHF为该N19隧道创建一个专门的计费资源。生成N19隧道的计费信息时，SMF设备可以从这两个UPF设备中的任意一个UPF设备获取N19隧道的计费信息，也可以从这两个UPF设备分别获取N19隧道的计费信息、将他们合并去重后得到该N19隧道汇总的计费信息。
具体地，若SMF设备管理两个以上UPF设备(用于5G局域网通信)，换句话说，5G局域网的UPF设备集合包含两个以上UPF设备，假设任意两个UPF设备之间会建立一个N19隧道，此时同一UPF同时与多个UPF设备建立了N19隧道，也就是说，该SMF设备可能管理了多个N19隧道，则SMF设备可以请求CHF为每个N19隧道创建一个对应的计费资源，也可以请求CHF为所有这些N19隧道创建一个共用的计费资源。对于每一个N19隧道，生成计费信息的方法同上一段，不再赘述。
应理解，在为N19隧道创建专门计费资源的场景下，PDU会话对应的计费资源创建方法与图5对应的方法流程相同；可选地，PDU会话对应的计费资源创建后，SMF通过普通N4会话给UPF设备下发的PDR和URR(usage reporting rule，使用量上报规则)中只包含针对本地交换转发和通过N6接口转发的计费规则，不包含通过N19隧道转发的计费规则，再通过隧道N4会话给UPF设备下发的PDR和URR中包含通过N19隧道转 发的计费规则。
步骤682：SMF向CHF发送计费资源创建请求消息，该请求消息携带TunInf61、SrvInd61和GrpId51。
具体地，SMF根据PCF(Policy Control Function，策略控制功能)设备下发FAR(Forwarding Action Rule，转发动作规则)、PDR(Packet Detection Rule，包检测规则)，或者本地配置的计费策略，确定需要针对N19隧道中转发的使用量进行计费的情况下，构建计费资源创建请求消息，并将其发送给CHF，该请求消息包含TunInf61、SrvInd61和GrpId51，其中SrvInd61为第二业务指示信息，用于指示TunInf61对应的N19隧道用于5G局域网群内通信，GrpId51已在图5对应方法流程中说明，不再赘述。在一种可能的方案中，该请求消息中可以不携带SrvInd61。
具体地，SMF可以在向UPF下发指示建立N19隧道时，也可以在UPF返回N19隧道建立成功时，向CHF发送该请求消息。
示例性的计费资源创建请求消息如下：
Figure PCTCN2022072382-appb-000012
步骤683：CHF创建计费资源，保存TunInf61、SrvInd51和GrpId51。
具体地，CHF接收上述计费资源创建请求消息，从中解析出TunInf61、SrvInd61和GrpId51，进而执行以下操作：
1)基于SrvInd61确定TunInf61对应的N19隧道用于5G局域网的群内通信；如果上述计费资源创建请求消息不包含SrvInd61，CHF可以默认该N19隧道用于5G局域网的群内通信，且生成SrvInd61这个指示信息；
2)为N19隧道创建相应的计费资源，并为该计费资源分配标识为ResId61。
可选地，CHF保存TunInf61和GrpId51，还保存上述接收到的或者确定出的SrvInd61，例如，将TunInf61、SrvInd61、GrpId51与ResId61对应存储。
可选地，SMF在创建N19隧道对应计费资源后，给N19隧道两端的UPF设备(如UPF设备403和UPF设备404)下发PDR和/或URR，以指示UPF采集N19隧道中的计费数据。
注意，为N19隧道创建的计费资源是跨PDU会话共享的，不同UE之间通信所导致的在该N19隧道中传输的使用量，都通过该计费资源上报给计费处理设备，即通过携带该计费资源标识的计费请求消息(如计费资源更新请求消息或者计费资源删除请求消息)上报该使用量。
步骤684：CHF向SMF发送计费资源创建响应消息，该响应消息携带ResId61。
具体地，CHF构造计费资源创建响应消息并将其发送给SMF，该响应消息携带ResId61。
示例性的计费资源创建响应消息如下：
ChargingResourceCreateResponse{
"RESID":"RES403-404"//ResId61，N19隧道的计费资源的标识
}步骤689：SMF确定使用量USU61、传输方向Dir61。
具体地，SMF通过隧道N4会话(Group N4 for N19)分别与UPF设备403和/或UPF设备404交互，从UPF获取通过N19隧道传输的使用量USU61。
具体地，对于一个N19隧道两端的UPF设备(如UPF 403)分别上报的使用量，如有重复(即两份使用量的时间段、两端的UPF设备的标识和业务单元数量等均相同)，可以由SMF合并去重后上报给CHF，也可以在SMF上报后由CHF合并去重。
例如，假设N19隧道介于UPF1与UPF2之间，则如下两个使用量为重复使用量：
Figure PCTCN2022072382-appb-000013
“去重”则指对上述两个使用量选择一个，丢弃另一个。
可选地，SMF还确定USU61对应的数据包在N19隧道中传输的方向Dir61，其示例性的取值及对应含义为：“403-404”-表示从UPF设备403发送到UPF设备404、“404-403”-表示从UPF设备404发送到UPF设备403。
步骤690：SMF向CHF发送计费资源更新请求消息，该请求消息包含ResId61、USU61、Dir61、TunInf61、SrvInd61和GrpId51。
具体地，SMF基于步骤689确定的USU61和Dir61，构建计费资源更新请求消息，将其发送给CHF，该请求消息包含ResId61、USU61、Dir61、TunInf61、SrvInd61和GrpId51。
示例性的计费资源更新请求消息如下：
Figure PCTCN2022072382-appb-000014
Figure PCTCN2022072382-appb-000015
上述计费资源更新请求消息中USU61和Dir61的并列关系，只是一种示例，并非限定，实际应用中可以采用其他的结构关系，例如，Dir61可以放在USU-INF数据结构外部，与SrvInd61等并列。
此外，如果步骤683中，CHF已经保存了TunInf61、SrvInd61或GrpId51，则可选地，为了避免信息的冗余传输，上述计费资源更新请求消息可以不包含TunInf61、SrvInd61或GrpId51。
在一种可能的技术方案中，上述计费资源更新请求消息也可以不包含Dir61。
步骤691：CHF对USU61进行计费处理。
具体地，CHF接收步骤690的计费资源更新请求消息，从中解析出ResId61、USU61、Dir61、TunInf61、SrvInd61和GrpId51，进而对USU61进行计费处理。
具体地，CHF可基于TunInf61、Dir61、SrvInd61和GrpId51中的任意一项或任意组合确定费率，以及基于GrpId51确定5G局域网群组对应的账户；如果计费模式为在线计费，则CHF基于所确定的费率和USU61对所确定的账户进行账户扣减，如果计费模式为离线计费，则CHF在N19隧道对应的计费话单中记录TunInf61、Dir61、SrvInd61和GrpId51中的任意一项或任意组合以及USU61。
如果接收到的计费资源更新请求消息不包含TunInf61、SrvInd61或GrpId51，则CHF可以根据ResId61从本地获取此前存储的TunInf61、SrvInd61或GrpId51。
可选地，CHF可以在该步骤中或者在后续步骤中以GrpId51为关联标识累积得到5G局域网群组的总使用量，例如，假设CHF接收到的多个ChargingResourceUpdateRequest中"GRPID"值都为"GRP414"，则CHF将这些ChargingResourceUpdateRequest中通过N19隧道传输的使用量进行累加，得到5G局域网群组的使用量。
步骤692：CHF向SMF发送计费资源更新响应消息，该响应消息包含ResId61和计费处理结果ChgRst61。
具体地，CHF构建计费资源更新响应消息，并将其发送给SMF，该计费资源更新响应消息包含ResId61和计费处理结果ChgRst61，其示例性的取值及对应含义为："SucInDeduction"-表示账户扣减成功，"SucInRecording"-表示计费话单写入成功。
示例性的计费资源更新响应消息如下：
Figure PCTCN2022072382-appb-000016
相应地，SMF接收该计费资源更新响应消息，从中解析计费处理结果，据此管理N19隧道，例如：拆除或释放隧道。
应理解，上述步骤689-步骤692之间的过程，可以重复执行，直到确定N19隧道将被拆除或释放，转步骤693。
步骤693：SMF确定要删除计费资源，确定使用量USU62，确定传输方向Dir62。
具体地，SMF根据5G局域网群组中各成员UE之间通信情况(例如N19隧道已连续 T秒无流量)，确定要释放N19隧道，据此确定要触发CHF删除此前为N19隧道创建的计费资源；由于有未上报的使用量，因此，SMF通过与UPF 403和/或UPF 404交互，确定通过N19隧道传输的使用量USU62；可选地，SMF还确定USU62对应的数据包在N19隧道中传输的方向Dir62。
步骤694：SMF向CHF发送计费资源删除请求消息，该请求消息包含ResId61、USU62、Dir62、TunInf61、SrvInd61和GrpId51。
具体地，SMF基于步骤693确定的USU62和Dir62，构建计费资源删除请求消息，将其发送给CHF，该请求消息包含ResId61、USU62、Dir62、TunInf61、SrvInd61和GrpId51。
示例性的计费资源更新请求消息如下：
Figure PCTCN2022072382-appb-000017
类似地，计费资源删除请求消息可以不包含TunInf61、SrvInd61和GrpId51。
在一种可能的技术方案中，上述计费资源删除请求消息也可以不包含Dir62。
步骤695：CHF对USU62进行计费处理，删除计费资源。
具体地，CHF接收步骤694的计费资源删除请求消息，从中解析出ResId61、USU62、Dir62、TunInf61、SrvInd61和GrpId51，进而对USU62进行计费处理，具体可以参考步骤691中的相关描述。
如果接收到的计费资源删除请求消息不包含TunInf61、SrvInd61或GrpId51，则CHF可以根据ResId61从本地获取此前存储的TunInf61、SrvInd61或GrpId51。
完成对USU62进行计费处理之后，CHF删除此前创建的ResId61对应的计费资源，以回收该计费资源所占用的CHF上的计算资源，如内存、CPU资源等。
步骤696：CHF向SMF发送计费资源删除响应消息，该响应消息包含ResId61、计费处理结果ChgRst62和资源删除结果DelRst61。
具体地，CHF构建计费资源删除响应消息，并将其发送给SMF，该计费资源删除响应消息包含ResId61、计费处理结果ChgRst62和资源删除结果DelRst61，ChgRst62示例性的取值及对应含义与ChgRst61相同，不再赘述；DelRst61示例性的取值及对应含义为："SucInDeleting"-表示N19隧道对应的计费资源删除成功。
示例性的计费资源删除响应消息如下：
Figure PCTCN2022072382-appb-000018
相应地，SMF接收该计费资源删除响应消息，从中解析出ChgRst62和DelRst61，据此N19隧道，如关闭N19隧道，以终止UE的群内通信业务。
图6对应的方法流程中，CHF为PDU会话创建计费资源A，为N19隧道创建计费资源B，然后SMF通过计费资源A的标识上报PDU会话中的使用量、通过本地交换服务转发的使用量和通过N6接口转发的使用量，通过计费资源B的标识上报通过N19隧道传输的使用量，可以更全面地衡量运营商通信网络为5G局域网群组通信做出的贡献，提高计费的准确性。
在一种可能的方案中，CHF也可以分别为PDU会话创建计费资源A，为UPF设备本地交换服务转发途径创建计费资源B，为UPF设备通过N6接口转发途径创建计费资源C，为UPF设备通过N19隧道创建计费资源D，然后SMF通过计费资源A的标识上报PDU会话中的使用量，通过计费资源B的标识上报PDU会话中通过UPF设备本地交换服务转发途径的使用量、通过计费资源C的标识上报PDU会话中通过N6接口转发途径的使用量以及通过计费资源D的标识上报PDU会话中通过N19隧道转发途径的使用量。具体可以参考图6对应方法流程，这里不再赘述。
应理解，上述“通过计费资源X的标识上报使用量”是指在计费资源更新请求消息或计费资源删除请求消息中携带计费资源X的标识、待上报的使用量和使用量的相关信息。
上述实施例假设一个5G局域网中的所有UE的计费信息(使用量信息和/或配额申请信息)都归同一个CHF设备处理。
在一种可能的方案中，一个5G局域网中的所有UE的计费信息归不同的CHF设备处理(这样做的好处之一是降低单个CHF设备的负担，从而降低群内通信的时延)，这样每一个CHF设备都只掌握部分成员UE的计费信息；为对整个5G局域网群组进行计费处理，可以采用图7A所示的方法，也可以采用图7B所示的方法。
图7A为本申请实施例提供的多个CHF设备第一组网的示意图；该组网中，SMF设备402分别与CHF设备401和CHF设备401a连接，CHF设备401与CHF设备401a连接；SMF设备将5G局域网群组中的一部分UE的计费信息上报给CHF设备401处理，而将另一部分UE的计费信息上报给CHF设备401a处理；为了对整个5G局域网群组进行计费处理(如输出账单)，可以是CHF设备401将其所收到的那部分UE的计费信息发送给CHF设备401a合并处理，也可以是CHF设备401a将其所收到的那部分UE的计费信息发送给CHF设备401合并处理。
图7B为本申请实施例提供的多个CHF设备第二组网的示意图；其中，SMF设备将5G局域网群组中的一部分UE的计费信息上报给CHF设备401处理，而将另一部分UE的计费信息上报给CHF设备401a处理；为了对整个5G局域网群组进行计费处理，CHF设备401和CHF设备401a分别将各自收到的那部分UE的计费信息发送给CHF设备401b 合并处理。
上述在合并过程包括用5G局域网群组的标识作为关联标识，将具有相同5G局域网群组标识的不同计费信息进行汇总统计。
图8为本申请实施例提供的计费触发设备、计费处理设备的硬件结构的示意图。本申请实施例中的所有计费触发设备(或者SMF设备，例如，图4A的402)、计费处理设备(或者CHF设备，例如，图4A的401)，均可以采用图8所示的通用的计算机硬件结构实现，其中包括处理器801、存储器802、总线803、输入设备804、输出设备805以及网络接口806，其中输入设备804与输出设备805为可选的。
具体地，存储器802可以包括以易失性和/或非易失性存储器形式的计算机存储媒体，如只读存储器和/或随机存取存储器。存储器802可以存储操作系统、应用程序、其他程序模块、可执行代码和程序数据。
输入设备804可以用于输入信息，便于系统管理员对计费触发设备、计费处理设备进行操作和管理等，例如，在计费处理设备上配置计费参数、在计费触发设备上设置默认的使用量获取方式或默认的配额申请量等；输入设备804可以为键盘或指向设备，如鼠标、轨迹球、触摸板、麦克风、操纵杆、游戏垫、卫星电视天线、扫描仪或类似设备，均可以通过总线803连接至处理器801。
输出设备805可以用于输出信息，便于系统管理员对计费触发设备、计费处理设备进行操作和管理等；例如，在计费处理设备上显示计费策略、在计费触发设备上显示默认的使用量获取方式或默认的配额申请量等；除了监视器之外，输出设备805还可以为其他外围输出设备，如扬声器和/或打印设备，也均可以通过总线803连接到处理器801。
计费触发设备、计费处理设备均可以通过网络接口806连接到网络中，例如连接到因特网中。在联网环境下，计费触发设备、计费处理设备中存储的计算机执行指令可以存储在远程存储设备中，而不限于在本地存储。
当计费触发设备中的处理器801执行存储器802中存储的可执行代码或应用程序时，使得计费触发设备执行以上所有实施例中与计费触发设备(或SMF设备)相对应的方法步骤，如步骤310、311、360、361、501、502、505、681和682等；具体执行过程均参见上述实施例，在此不再赘述。
当计费处理设备中的处理器801执行存储器802中存储的可执行代码或应用程序时，使得计费处理设备执行以上所有实施例中与计费处理设备(或CHF设备)相对应的方法步骤，如步骤312、362、503、507、683、691和695等；具体执行过程均参见上述实施例，在此不再赘述。
图9为本申请实施例提供的计费处理设备的逻辑结构的示意图；该计费处理设备与计费触发设备通信，用于对移动局域网业务进行计费处理，该移动局域网业务为电信运营商网络基于该计费触发设备所管理的至少一个用户面数据网关为移动局域网群组提供群内通信的业务；具体地，该计费处理设备包括接收模块901、处理模块903和发送 模块902，其中：
-接收模块901，用于从计费触发设备接收计费请求消息，计费请求消息包含局域网计费信息，该局域网计费信息为移动局域网业务相关的计费信息，具体执行过程参见上述实施例中计费处理设备(或CHF设备)侧的步骤说明，如步骤312、362、503、507、683、691和695等；
-处理模块903，用于对所接收的局域网计费信息进行计费处理，得到计费处理结果，具体执行过程参见上述实施例中计费处理设备(或CHF设备)侧的步骤说明，如步骤312、362、503、507、683、691和695等；
-发送模块902，用于向计费触发设备发送计费响应消息，计费响应消息包含所得到的计费处理结果，具体执行过程参见上述实施例中计费处理设备(或CHF设备)侧的步骤说明，如步骤313、363、504、508、512、516和684等关于计费处理设备(或CHF设备)执行动作的说明。
图10为本申请实施例提供的计费触发设备的逻辑结构的示意图，该计费触发设备与计费处理设备通信，用于对移动局域网业务进行计费处理，该移动局域网业务为电信运营商基于该计费触发设备所管理的至少一个用户面数据网关为移动局域网群组提供群内通信的业务；具体地，计费触发设备包括获取模块1003、发送模块1001和接收模块1002，其中：
-获取模块1003，用于获取局域网计费信息，该局域网计费信息为移动局域网业务相关的计费信息，具体执行过程可以参见上述实施例中计费触发设备(或SMF设备)侧的步骤说明，如步骤310、360、361、501、505、681和689等；
-发送模块1001，用于向计费处理设备发送计费请求消息，该计费请求消息包含所获取的局域网计费信息，具体执行过程参见上述实施例中计费触发设备(或SMF设备)侧的步骤说明，如步骤310、311、360、361、501、502、505、681和682等。
-接收模块1002，用于从计费处理设备接收计费响应消息，该计费响应消息包含计费处理结果，计费处理结果为计费处理设备对局域网计费信息进行计费处理的结果，具体执行过程参见上述实施例中计费触发设备(或SMF设备)侧的步骤说明，如步骤313、363、504、508、512、516和684等关于计费触发设备(或SMF设备)执行动作的说明。
图9所示计费处理设备、图10所示计费触发设备是以功能模块的形式来呈现。这里的“模块”可以指特定应用集成电路(application-specific integrated circuit，ASIC)，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到这些设备也可以采用图8所示的形式。例如接收模块901、发送模块1001、发送模块902、接收模块1002都可以通过图8中的处理器801和存储器802来实现。例如，接收模块901接收计费请求消息的功能、发送模块1001发送计费请求消息的功能，均可以通过由处理器801来执行存储器802中存储的代码来实现。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、计算机软件或者二者的结合来实现，为了清楚地说明硬件和软件的可互换性，在上述说明中已经按照功能一般性地描述了各示例的组成及步骤。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本领域普通技术人员可以清楚地了解到，为了描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另外，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口、装置或单元的间接耦合或通信连接，也可以是电的，机械的或其它的形式连接。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本申请实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以是两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分，或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器、随机存取存储器、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到各种等效的修改或替换，这些修改或替换都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以权利要求的保护范围为准。

Claims (56)

  1. 一种对移动局域网业务进行计费处理的方法，应用于计费触发设备，所述计费触发设备与计费处理设备通信，其特征在于，所述计费触发设备管理至少一个用户面数据网关，所述移动局域网业务是指基于所述至少一个用户面数据网关为移动局域网群组提供群内通信的业务，所述方法包括：
    向所述计费处理设备发送计费请求消息，所述计费请求消息包含所述计费触发设备获取的局域网计费信息，所述局域网计费信息为所述移动局域网业务相关的计费信息；
    从所述计费处理设备接收计费响应消息，所述计费响应消息包含计费处理结果，所述计费处理结果为所述计费处理设备对所述局域网计费信息进行计费处理的结果。
  2. 如权利要求1所述的方法，其特征在于，所述局域网计费信息包括成员数据连接会话的计费信息，则所述计费处理结果包含所述计费处理设备对所述成员数据连接会话的计费信息进行计费处理的结果；
    其中，所述成员数据连接会话为使用所述移动局域网业务的成员用户设备与相应的用户面数据网关之间的数据连接会话。
  3. 如权利要求2所述的方法，其特征在于，所述成员数据连接会话的计费信息包含第一业务指示信息，所述第一业务指示信息指示所述成员数据连接会话用于所述移动局域网群组的群内通信。
  4. 如权利要求2或3所述的方法，其特征在于，所述成员数据连接会话的计费信息包含群组标识，所述群组标识为所述移动局域网群组的标识。
  5. 如权利要求2-4任一所述的方法，其特征在于：
    所述成员数据连接会话的计费信息还包含第一计费数据，所述第一计费数据包含所述成员数据连接会话的使用量和/或配额申请量；
    所述计费处理结果包含所述计费处理设备对所述第一计费数据进行计费处理的结果。
  6. 如权利要求5所述的方法，其特征在于,所述成员数据连接会话的计费信息还包含所述第一计费数据对应的群内转发方式。
  7. 如权利要求5或6所述的方法，其特征在于，所述成员数据连接会话的计费信息还包含所述成员用户设备的群内通信方式，所述群内通信方式为以下任意一项：单播、多播、广播。
  8. 如权利要求2-7任一所述的方法，其特征在于：
    所述计费请求消息用于请求所述计费处理设备为所述成员数据连接会话创建计费资源，则所述计费处理结果包含所述计费处理设备为所述成员数据连接会话创建的计费资源的标识；或者
    所述计费请求消息用于请求所述计费处理设备更新所述成员数据连接会话的计费资源，则所述计费处理结果包含所述成员数据连接会话的计费资源的更新结果；或者
    所述计费请求消息用于请求所述计费处理设备删除所述成员数据连接会话的计费资源，则所述计费处理结果包含所述成员数据连接会话的计费资源的删除结果。
  9. 如权利要求1所述的方法，其特征在于，所述计费触发设备管理两个或两个以上用户面数据网关，所述局域网计费信息包括数据网关间隧道的计费信息，则所述计费 处理结果包含所述计费处理设备对所述数据网关间隧道的计费信息进行计费处理的结果；
    其中，所述数据网关间隧道为所述计费触发设备管理的两个用户面数据网关之间的数据传输隧道，所述数据网关间隧道的计费信息包含所述数据网关间隧道的信息。
  10. 如权利要求9所述的方法，其特征在于，所述数据网关间隧道的计费信息还包含第二业务指示信息，所述第二业务指示信息指示所述数据网关间隧道用于所述移动局域网群组的群内通信。
  11. 如权利要求9或10所述的方法，其特征在于，所述数据网关间隧道的计费信息还包含群组标识，所述群组标识为所述移动局域网群组的标识。
  12. 如权利要求9-11任一所述的方法，其特征在于：
    所述成员数据连接会话的计费信息还包含第二计费数据，所述第二计费数据包含通过所述数据网关间隧道传输的使用量；
    所述计费处理结果包含所述计费处理设备对所述第二计费数据进行计费处理的结果。
  13. 如权利要求9-12任一所述的方法，其特征在于：
    所述计费请求消息用于请求所述计费处理设备为所述数据网关间隧道创建计费资源，则所述计费处理结果包含所述计费处理设备为所述数据网关间隧道创建的计费资源的标识；或者
    所述计费请求消息用于请求所述计费处理设备更新所述数据网关间隧道的计费资源，则所述计费处理结果包含所述数据网关间隧道的计费资源的更新结果；或者
    所述计费请求消息用于请求所述计费处理设备删除所述数据网关间隧道的计费资源，则所述计费处理结果包含所述数据网关间隧道的计费资源的删除结果。
  14. 一种对移动局域网业务进行计费处理的方法，应用于计费处理设备，所述计费处理设备与计费触发设备通信，所述移动局域网业务是指为移动局域网群组提供群内通信的业务，其特征在于，所述方法包括：
    从所述计费触发设备接收计费请求消息，所述计费请求消息包含所述计费触发设备获取的局域网计费信息，所述局域网计费信息为所述移动局域网业务相关的计费信息；
    向所述计费触发设备发送计费响应消息，所述计费响应消息包含计费处理结果，所述计费处理结果为所述计费处理设备对所述局域网计费信息进行计费处理的结果。
  15. 如权利要求14所述的方法，其特征在于，所述局域网计费信息包括成员数据连接会话的计费信息，则在向所述计费触发设备发送计费响应消息之前，所述方法还包括：对所述成员数据连接会话的计费信息进行计费处理，所述计费处理结果包含对所述成员数据连接会话的计费信息进行计费处理的结果；
    其中，所述成员数据连接会话为使用所述移动局域网业务的成员用户设备与相应的用户面数据网关之间的数据连接会话。
  16. 如权利要求15所述的方法，其特征在于：
    所述成员数据连接会话的计费信息包含第一业务指示信息，则所述对所述成员数据连接会话的计费信息进行计费处理，包括：
    基于所述第一业务指示信息确定所述成员数据连接会话用于所述移动局域网群组 的群内通信。
  17. 如权利要求16所述的方法，其特征在于，所述对所述成员数据连接会话的计费信息进行计费处理，还包括：
    基于所述第一业务指示信息对所述成员用户设备是否可使用所述移动局域网业务进行认证，则所述计费处理结果包含所述认证的结果。
  18. 如权利要求15-17任一所述的方法，其特征在于：
    所述成员数据连接会话的计费信息包含群组标识，所述群组标识为所述移动局域网群组的标识，则所述对所述成员数据连接会话的计费信息进行计费处理，包括以下任意一项：
    基于所述群组标识确定所述移动局域网群组对应的账户，或者，
    在所述成员数据连接会话的计费话单中记录所述群组标识，或者，
    以所述群组标识为关联标识累积所述移动局域网群组的使用量，或者，
    基于所述群组标识查询所述移动局域网群组对应的外部群组标识，以基于所述外部群组标识对所述成员数据连接会话的计费信息进行计费处理。
  19. 如权利要求15-18任一所述的方法，其特征在于，所述成员数据连接会话的计费信息包含第一计费数据，所述第一计费数据包含所述成员数据连接会话的使用量和/或配额申请量，则所述对所述成员数据连接会话的计费信息进行计费处理，包括：对所述第一计费数据进行计费处理，所述计费处理结果包含对所述第一计费数据进行计费处理的结果。
  20. 如权利要求19所述的方法，其特征在于,所述成员数据连接会话的计费信息还包含所述第一计费数据对应的群内转发方式；则所述对所述成员数据连接会话的计费信息进行计费处理，还包括：
    根据所述群内转发方式确定所述第一计费数据的费率，或者，在所述成员数据连接会话的计费话单中记录所述第一计费数据及其对应的群内转发方式。
  21. 如权利要求19或20所述的方法，其特征在于，所述成员数据连接会话的计费信息还包含所述成员用户设备的群内通信方式，所述群内通信方式为以下任意一项：单播、多播、广播；则所述对所述成员数据连接会话的计费信息进行计费处理，还包括：
    根据所述群内通信方式确定所述第一计费数据的费率，或者在所述成员数据连接会话的计费话单中记录所述群内通信方式。
  22. 如权利要求15-21任一所述的方法，其特征在于：
    所述计费请求消息用于请求所述计费处理设备为所述成员数据连接会话创建计费资源，则所述对所述成员数据连接会话的计费信息进行计费处理包括：为所述成员数据连接会话创建计费资源，所述计费处理结果包含所计费资源的标识；或者，
    所述计费请求消息用于请求所述计费处理设备更新所述成员数据连接会话的计费资源，则所述对所述成员数据连接会话的计费信息进行计费处理包括：更新所述成员数据连接会话的计费资源，所述计费处理结果包含所述成员数据连接会话的计费资源的更新结果；或者，
    所述计费请求消息用于请求所述计费处理设备删除所述成员数据连接会话的计费资源，则所述对所述成员数据连接会话的计费信息进行计费处理包括：删除所述成员数据连接会话的计费资源，所述计费处理结果包含所述成员数据连接会话的计费资源的更 新结果。
  23. 如权利要求14所述的方法，其特征在于，所述局域网计费信息包括数据网关间隧道的计费信息，则在向所述计费触发设备发送计费响应消息之前，所述方法还包括：对所述数据网关间隧道的计费信息进行计费处理，所述计费处理结果包含对所述数据网关间隧道的计费信息进行计费处理的结果；
    其中，所述数据网关间隧道为所述计费触发设备管理的两个用户面数据网关之间的数据传输隧道，所述数据网关间隧道的计费信息包含所述数据网关间隧道的信息。
  24. 如权利要求23所述的方法，其特征在于，所述数据网关间隧道的计费信息还包含第二业务指示信息，则所述对所述数据网关间隧道的计费信息进行计费处理，包括：基于所述第二业务指示信息确定所述数据网关间隧道用于所述移动局域网群组的群内通信。
  25. 如权利要求23或24所述的方法，其特征在于，所述数据网关间隧道的计费信息还包含群组标识，所述群组标识为所述移动局域网群组的标识；则所述对所述数据网关间隧道的计费信息进行计费处理，包括以下任意一项：
    基于所述群组标识确定所述移动局域网群组对应的账户，或者，
    在所述数据网关间隧道的计费话单中记录所述群组标识，或者，
    基于所述群组标识查询所述移动局域网群组对应的外部群组标识，以基于所述外部群组标识对所述数据网关间隧道的计费信息进行计费处理。
  26. 如权利要求23-25任一所述的方法，其特征在于：
    所述成员数据连接会话的计费信息还包含第二计费数据，所述第二计费数据包含通过所述数据网关间隧道传输的使用量；则所述对所述数据网关间隧道的计费信息进行计费处理，还包括：对所述第二计费数据进行计费处理，所述计费处理结果包含对所述第二计费数据进行计费处理的结果。
  27. 如权利要求23-26任一所述的方法，其特征在于：
    所述计费请求消息用于请求所述计费处理设备为所述数据网关间隧道创建计费资源，则所述对所述数据网关间隧道的计费信息进行计费处理包括：为所述数据网关间隧道创建计费资源，所述计费处理结果包含所述计费资源的标识；或者，
    所述计费请求消息用于请求所述计费处理设备更新所述数据网关间隧道的计费资源，则所述对所述数据网关间隧道的计费信息进行计费处理包括：更新所述数据网关间隧道的计费资源，所述计费处理结果包含所述数据网关间隧道的计费资源的更新结果；或者，
    所述计费请求消息用于请求所述计费处理设备删除所述数据网关间隧道的计费资源，则所述对所述数据网关间隧道的计费信息进行计费处理包括：删除所述数据网关间隧道的计费资源，所述计费处理结果包含所述数据网关间隧道的计费资源的删除结果。
  28. 一种计费处理系统，用于对移动局域网业务进行计费处理，包括：计费触发设备和计费处理设备，所述计费触发设备与所述计费处理设备通信，其特征在于：所述计费触发设备管理至少一个用户面数据网关，所述移动局域网业务是指基于所述至少一个用户面数据网关为移动局域网群组提供群内通信的业务，其中：
    所述计费触发设备用于向所述计费处理设备发送计费请求消息，所述计费请求消息包含所述计费触发设备获取的局域网计费信息，所述局域网计费信息为所述移动局域网 业务相关的计费信息；
    所述计费处理设备用于从所述计费触发设备接收所述计费请求消息，且向所述计费触发设备发送计费响应消息，所述计费响应消息包含计费处理结果，所述计费处理结果为所述计费处理设备对所述局域网计费信息进行计费处理的结果；
    所述计费触发设备还用于从所述计费处理设备接收所述计费响应消息。
  29. 如权利要求28所述的计费处理系统，其特征在于：
    所述局域网计费信息包括成员数据连接会话的计费信息，则所述计费处理设备还用于对所述成员数据连接会话的计费信息进行计费处理，所述计费处理结果包括所述计费处理设备对所述成员数据连接会话的计费信息进行计费处理的结果；
    其中，所述成员数据连接会话为使用所述移动局域网业务的成员用户设备与相应的用户面数据网关之间的数据连接会话。
  30. 如权利要求29所述的计费处理系统，其特征在于，所述成员数据连接会话的计费信息包含第一业务指示信息，所述计费处理设备还用于基于所述第一业务指示信息确定所述成员数据连接会话用于所述移动局域网群组的群内通信。
  31. 如权利要求30所述的计费处理系统，其特征在于，所述计费处理设备还用于基于所述第一业务指示信息对所述成员用户设备是否可使用所述移动局域网业务进行认证，则所述计费处理结果包含所述认证的结果。
  32. 如权利要求29-31任一所述的计费处理系统，其特征在于，所述成员数据连接会话的计费信息还包含群组标识，所述群组标识为所述移动局域网群组的标识，则所述计费处理设备还用于：
    基于所述群组标识确定所述移动局域网群组对应的账户，或者，
    在所述成员数据连接会话的计费话单中记录所述群组标识，或者，
    以所述群组标识为关联标识累积所述移动局域网群组的使用量，或者，
    基于所述群组标识查询所述移动局域网群组对应的外部群组标识，以基于所述外部群组标识对所述成员数据连接会话的计费信息进行计费处理。
  33. 如权利要求29-32任一所述的计费处理系统，其特征在于，所述成员数据连接会话的计费信息包含第一计费数据和群内转发方式，所述第一计费数据包含所述成员数据连接会话的使用量和/或配额申请量，则所述计费处理设备还用于：
    根据所述群内转发方式确定所述第一计费数据的费率，或者，
    在所述成员数据连接会话的计费话单中记录所述第一计费数据及其对应的群内转发方式。
  34. 如权利要求28所述的计费处理系统，其特征在于，所述计费触发设备管理两个或两个以上用户面数据网关，所述局域网计费信息包括数据网关间隧道的计费信息，则所述计费处理设备还用于：在向所述计费触发设备发送计费响应消息之前，对所述数据网关间隧道的计费信息进行计费处理；所述计费处理结果包括所述计费处理设备对所述数据网关间隧道的计费信息进行计费处理的结果；
    其中，所述数据网关间隧道为所述计费触发设备管理的两个用户面数据网关之间的数据传输隧道，所述数据网关间隧道的计费信息包含所述数据网关间隧道的信息。
  35. 如权利要求34所述的计费处理系统，其特征在于，所述数据网关间隧道的计费信息还包含第二业务指示信息，所述计费处理设备还用于基于所述第二业务指示信息 确定所述数据网关间隧道用于提供移动局域网业务。
  36. 如权利要求34或35所述的计费处理系统，其特征在于，所述数据网关间隧道的计费信息还包含群组标识，所述群组标识为所述移动局域网群组的标识，则所述计费处理设备还用于：
    基于所述群组标识确定所述移动局域网群组对应的账户，或者，
    在所述数据网关间隧道的计费话单中记录所述群组标识，或者，
    基于所述群组标识查询所述移动局域网群组对应的外部群组标识，以基于所述外部群组标识对所述数据网关间隧道的计费信息进行计费处理。
  37. 一种计费触发设备，用于对移动局域网业务进行计费处理，所述计费触发设备与计费处理设备通信，其特征在于，所述计费触发设备管理至少一个用户面数据网关，所述移动局域网业务是指基于所述至少一个用户面数据网关为移动局域网群组提供群内通信的业务，所述计费触发设备包括获取模块、发送模块和接收模块，其中：
    所述获取模块用于获取局域网计费信息，所述局域网计费信息为所述移动局域网业务相关的计费信息；
    所述发送模块用于向所述计费处理设备发送计费请求消息，所述计费请求消息包含所述局域网计费信息；
    所述接收模块用于从所述计费处理设备接收计费响应消息，所述计费响应消息包含计费处理结果，所述计费处理结果为所述计费处理设备对所述局域网计费信息进行计费处理的结果。
  38. 如权利要求37所述的计费触发设备，其特征在于,所述局域网计费信息包括成员数据连接会话的计费信息，所述计费处理结果包括所述计费处理设备对所述成员数据连接会话的计费信息进行计费处理的结果；
    其中，所述成员数据连接会话为使用所述移动局域网业务的成员用户设备与相应的用户面数据网关之间的数据连接会话。
  39. 如权利要求38所述的计费触发设备，其特征在于，所述成员数据连接会话的计费信息包含第一业务指示信息，所述第一业务指示信息指示所述成员数据连接会话用于所述移动局域网群组的群内通信。
  40. 如权利要求38或39所述的计费触发设备，其特征在于，所述成员数据连接会话的计费信息包含群组标识，所述群组标识为所述移动局域网群组的标识。
  41. 如权利要求38-40任一所述的计费触发设备，其特征在于，所述成员数据连接会话的计费信息包含第一计费数据和群内转发方式，所述第一计费数据包含所述成员数据连接会话的使用量和/或配额申请量。
  42. 如权利要求37所述的计费触发设备，其特征在于，所述计费触发设备管理两个或两个以上用户面数据网关，所述局域网计费信息包括数据网关间隧道的计费信息，所述所述计费处理结果包括所述计费处理设备对所述数据网关间隧道的计费信息进行计费处理的结果；
    其中，所述数据网关间隧道为所述计费触发设备管理的两个用户面数据网关之间的数据传输隧道，所述数据网关间隧道的计费信息包含所述数据网关间隧道的信息。
  43. 如权利要求42所述的计费处理系统，其特征在于，所述数据网关间隧道的计费信息还包含第二业务指示信息，所述第二业务指示信息用于指示所述数据网关间隧道 用于所述移动局域网群组的群内通信。
  44. 如权利要求42或43所述的计费触发设备，其特征在于，所述数据网关间隧道的计费信息还包含群组标识，所述群组标识为所述移动局域网群组的标识。
  45. 一种计费处理设备，用于对移动局域网业务进行计费处理，所述计费处理设备与计费触发设备通信，其特征在于，所述移动局域网业务是指为移动局域网群组提供群内通信的业务，所述计费处理设备包括接收模块、处理模块和发送模块，其中：
    所述接收模块用于从所述计费触发设备接收计费请求消息，所述计费请求消息包含局域网计费信息，所述局域网计费信息为所述移动局域网业务相关的计费信息；
    所述处理模块用于对所述局域网计费信息进行计费处理，得到计费处理结果；
    所述发送模块用于向所述计费触发设备发送计费响应消息，所述计费响应消息包含所述计费处理结果。
  46. 如权利要求45所述的计费处理设备，其特征在于，所述局域网计费信息包括成员数据连接会话的计费信息，则所述处理模块还用于对所述成员数据连接会话的计费信息进行计费处理，所述计费处理结果包括所述处理模块对所述成员数据连接会话的计费信息进行计费处理的结果；
    其中，所述成员数据连接会话为使用所述移动局域网业务的成员用户设备与相应的用户面数据网关之间的数据连接会话。
  47. 如权利要求46所述的计费处理设备，其特征在于，所述成员数据连接会话的计费信息包含第一业务指示信息，所述处理模块还用于基于所述第一业务指示信息确定所述成员数据连接会话用于所述移动局域网群组的群内通信。
  48. 如权利要求47所述的计费处理设备，其特征在于，所述处理模块还用于基于所述第一业务指示信息对所述成员用户设备是否可使用所述移动局域网业务进行认证。
  49. 如权利要求46-48任一所述的计费处理设备，其特征在于，所述成员数据连接会话的计费信息包含群组标识，所述群组标识为所述移动局域网群组的标识，则所述处理模块还用于：
    基于所述群组标识确定所述移动局域网群组对应的账户，或者，
    在所述成员数据连接会话的计费话单中记录所述群组标识，或者，
    以所述群组标识为关联标识累积所述移动局域网群组的使用量，或者，
    基于所述群组标识查询所述移动局域网群组对应的外部群组标识，以基于所述外部群组标识对所述成员数据连接会话的计费信息进行计费处理。
  50. 如权利要求46-49任一所述的计费处理设备，其特征在于，所述成员数据连接会话的计费信息包含群内转发方式，所述第一计费数据包含所述成员数据连接会话的使用量和/或配额申请量，则所述处理模块还用于：
    根据所述群内转发方式确定所述第一计费数据的费率，或者，
    在所述成员数据连接会话的计费话单中记录所述第一计费数据及其对应的群内转发方式。
  51. 如权利要求45所述的计费处理设备，其特征在于，所述局域网计费信息包括数据网关间隧道的计费信息，则在所述发送模块向所述计费触发设备发送计费响应消息之前，所述处理模块还用于对所述数据网关间隧道的计费信息进行计费处理；
    其中，所述数据网关间隧道为所述计费触发设备管理的两个用户面数据网关之间的 数据传输隧道，所述数据网关间隧道的计费信息包含所述数据网关间隧道的信息。
  52. 如权利要求51所述的计费处理设备，其特征在于，所述数据网关间隧道的计费信息还包含第二业务指示信息，所述处理模块还用于基于所述第二业务指示信息确定所述数据网关间隧道用于所述移动局域网群组的群内通信。
  53. 如权利要求51或52所述的计费处理设备，其特征在于，所述数据网关间隧道的计费信息还包含群组标识，所述群组标识为所述移动局域网群组的标识，则所述计费处理设备还用于：
    基于所述群组标识确定所述移动局域网群组对应的账户，或者，
    在所述数据网关间隧道的计费话单中记录所述群组标识，或者，
    基于所述群组标识查询所述移动局域网群组对应的外部群组标识，以基于所述外部群组标识对所述数据网关间隧道的计费信息进行计费处理。
  54. 一种计费触发设备，包括处理器和存储器，其特征在于：
    所述存储器，用于存储程序指令；
    所述处理器，用于调用并执行所述存储器中存储的程序指令，以使所述计费触发设备执行权利要求1-13任一所述的计费处理的方法。
  55. 一种计费处理设备，包括处理器和存储器，其特征在于：
    所述存储器，用于存储程序指令；
    所述处理器，用于调用并执行所述存储器中存储的程序指令，以使所述计费处理设备执行权利要求14-27任一所述的计费处理的方法。
  56. 一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得所述计算机执行权利要求1-27任一所述的计费处理的方法。
PCT/CN2022/072382 2021-01-15 2022-01-17 对移动局域网业务进行计费处理的方法、系统及相关设备 WO2022152303A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
AU2022208946A AU2022208946A1 (en) 2021-01-15 2022-01-17 Method and system for performing billing processing on mobile local area network service, and related device
EP22739178.6A EP4277309A4 (en) 2021-01-15 2022-01-17 METHOD AND SYSTEM FOR PERFORMING BILLING PROCESSING ON A MOBILE LOCAL NETWORK SERVICE AND ASSOCIATED DEVICE
CA3205377A CA3205377A1 (en) 2021-01-15 2022-01-17 Method for performing charging processing on mobile local area network service, system, and related device
JP2023542856A JP2024503864A (ja) 2021-01-15 2022-01-17 モバイルローカルエリアネットワークサービスに対する課金処理を実行する方法、システム、および関連するデバイス
US18/352,789 US20230362306A1 (en) 2021-01-15 2023-07-14 Method for performing charging processing on mobile local area network service, system, and related device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110058017.2A CN114765749A (zh) 2021-01-15 2021-01-15 对移动局域网业务进行计费处理的方法、系统及相关设备
CN202110058017.2 2021-01-15

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/352,789 Continuation US20230362306A1 (en) 2021-01-15 2023-07-14 Method for performing charging processing on mobile local area network service, system, and related device

Publications (1)

Publication Number Publication Date
WO2022152303A1 true WO2022152303A1 (zh) 2022-07-21

Family

ID=82365475

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/072382 WO2022152303A1 (zh) 2021-01-15 2022-01-17 对移动局域网业务进行计费处理的方法、系统及相关设备

Country Status (7)

Country Link
US (1) US20230362306A1 (zh)
EP (1) EP4277309A4 (zh)
JP (1) JP2024503864A (zh)
CN (1) CN114765749A (zh)
AU (1) AU2022208946A1 (zh)
CA (1) CA3205377A1 (zh)
WO (1) WO2022152303A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107040674A (zh) * 2016-02-04 2017-08-11 华为技术有限公司 一种计费方法、装置及系统
US20180270073A1 (en) * 2017-03-17 2018-09-20 Huawei Technologies Co., Ltd. Method and apparatus for charging operations in a communication network
WO2020205725A1 (en) * 2019-03-29 2020-10-08 Weihua Qiao Charging control for non-public network
CN111917563A (zh) * 2019-05-07 2020-11-10 华为技术有限公司 一种路由规则的配置方法及通信装置
US20200396673A1 (en) * 2019-06-14 2020-12-17 Samsung Electronics Co., Ltd. Method and system for handling of closed access group related procedure

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107040674A (zh) * 2016-02-04 2017-08-11 华为技术有限公司 一种计费方法、装置及系统
US20180270073A1 (en) * 2017-03-17 2018-09-20 Huawei Technologies Co., Ltd. Method and apparatus for charging operations in a communication network
WO2020205725A1 (en) * 2019-03-29 2020-10-08 Weihua Qiao Charging control for non-public network
CN111917563A (zh) * 2019-05-07 2020-11-10 华为技术有限公司 一种路由规则的配置方法及通信装置
US20200396673A1 (en) * 2019-06-14 2020-12-17 Samsung Electronics Co., Ltd. Method and system for handling of closed access group related procedure

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects Charging management Study on charging aspect of 5G LAN-type services; (Release 17)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TR 28.822, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. V1.0.0, 6 December 2021 (2021-12-06), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, pages 1 - 27, XP052083033 *
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Service requirements for the 5G system; Stage 1 (Release 18)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 22.261, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG1, no. V18.1.0, 17 December 2020 (2020-12-17), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , pages 1 - 85, XP051975146 *
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Charging management; 5G system; Services, operations and procedures of charging using Service Based Interface (SBI) (Release 17)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 32.290, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG5, no. V17.0.0, 17 December 2020 (2020-12-17), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , pages 1 - 37, XP051999347 *
SA WG5: "New SID on Charging Aspects of 5G LAN-type Services", 3GPP DRAFT; SP-201081, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. TSG SA, no. Electronic meeting; 20201208 - 20201214, 2 December 2020 (2020-12-02), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051964514 *
See also references of EP4277309A4

Also Published As

Publication number Publication date
JP2024503864A (ja) 2024-01-29
EP4277309A1 (en) 2023-11-15
CA3205377A1 (en) 2022-07-21
US20230362306A1 (en) 2023-11-09
AU2022208946A1 (en) 2023-07-27
EP4277309A4 (en) 2024-03-27
CN114765749A (zh) 2022-07-19

Similar Documents

Publication Publication Date Title
WO2017088501A1 (zh) 一种计费方法及装置
US20220150166A1 (en) Methods and apparatuses for supporting a local area network (lan)
US8965962B2 (en) Diameter session audits
WO2020177497A1 (zh) 对网络切片客户进行计费处理的方法、系统及相关设备
WO2019001109A1 (zh) 一种计费方法及设备
US20110320544A1 (en) Diameter session audits
WO2017219905A1 (zh) 一种计费方法、装置、系统和存储介质
CN114667746A (zh) 无线通信系统中用于psa-upf重定位的装置和方法
WO2021017669A1 (zh) 一种通信方法及设备
WO2013178113A1 (zh) 一种对无线侧本地流量进行计费的方法和装置
WO2021051420A1 (zh) 一种dns缓存记录的确定方法及装置
WO2020248709A1 (zh) 一种mdbv的确定方法、装置及系统
EP3656089A1 (en) Methods, systems, and computer readable media for operating a telecommunications network using an on-premises computing system and an off-premises cloud computing system
WO2022152303A1 (zh) 对移动局域网业务进行计费处理的方法、系统及相关设备
US20220217005A1 (en) Network Slice Charging Method and Apparatus
WO2018177003A1 (zh) 一种计费方法、相关设备和系统
WO2021057342A1 (zh) 一种网络切片的计费方法及装置
WO2022028076A1 (zh) 一种计费处理的方法、系统及相关设备
Ungureanu et al. Leveraging the cloud-native approach for the design of 5G NextGen Core Functions
WO2021179598A1 (zh) 通信方法、装置及系统
WO2008061477A1 (fr) Système et procédé de commande de facturation d&#39;une structure de commande de facturation de politique de fusion de réseau
US20090016237A1 (en) Accounting apparatus and method in portable internet system
WO2023213156A1 (zh) 通信方法、通信装置及通信系统
Talarico et al. Efficient service auto-discovery for next generation network slicing architecture
KR20220057963A (ko) 데이터처리 노드장치 및 그 장치에서 수행되는 정보 전달 방법

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 3205377

Country of ref document: CA

WWE Wipo information: entry into national phase

Ref document number: 2023542856

Country of ref document: JP

ENP Entry into the national phase

Ref document number: 2022208946

Country of ref document: AU

Date of ref document: 20220117

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2022739178

Country of ref document: EP

Effective date: 20230811