WO2024093738A1 - 通信方法与通信装置 - Google Patents

通信方法与通信装置 Download PDF

Info

Publication number
WO2024093738A1
WO2024093738A1 PCT/CN2023/126256 CN2023126256W WO2024093738A1 WO 2024093738 A1 WO2024093738 A1 WO 2024093738A1 CN 2023126256 W CN2023126256 W CN 2023126256W WO 2024093738 A1 WO2024093738 A1 WO 2024093738A1
Authority
WO
WIPO (PCT)
Prior art keywords
network element
information
user plane
function network
session management
Prior art date
Application number
PCT/CN2023/126256
Other languages
English (en)
French (fr)
Inventor
龙思锐
刘佳琦
尤正刚
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2024093738A1 publication Critical patent/WO2024093738A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic
    • 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

Definitions

  • the present application relates to the field of wireless communications, and more specifically, to a communication method and a communication device.
  • the service traffic of different parks can be associated with different rate groups (RGs), and the free traffic and the normally charged traffic of different parks can be distinguished according to different RGs. Since RGs are planned uniformly by operators and the number of regions and parks involved in this implementation is very large, the feasibility is low. Therefore, how to implement the billing of free traffic within the park has become an urgent problem to be solved.
  • RGs rate groups
  • the present application provides a communication method and a communication device, which can realize free flow traffic billing within the park.
  • a communication method is provided, which can be executed by a session management network element, or can also be executed by a component (such as a chip or circuit) of the session management network element, which is not limited in the present application.
  • a component such as a chip or circuit
  • the following is an example of execution.
  • the method may include: a session management network element obtains first information of a first terminal device, the first information includes a usage amount of a first data flow, the first data flow includes a data flow of the first terminal device diverted from a first user plane function network element to a second user plane function network element, the first user plane function network element is used to divert data flows of terminal devices in a first area, the first area is a signing location of a dedicated network signed by the first terminal device, the second user plane function network element is used to transmit user plane data between the first terminal device and a data network; the session management network element sends a first billing request message to a billing function network element, the first billing request message includes first identification information and the first information, the first identification information is used to associate the first area.
  • the session management network element can obtain the usage of the first data flow of the terminal device, where the first data flow includes the data flow of the first terminal device diverted from the first user plane function network element to the second user plane function network element, and send the first identification information and the first information to the billing function network element, so that the billing function network element generates a call bill for the usage of the first data flow, thereby realizing billing for the first data flow.
  • the session management network element sends first indication information to the first user plane function network element, and the first indication information indicates statistics and reporting of the usage of the first data flow; the session management network element receives the usage of the first data flow from the first user plane function network element.
  • the session management network element sends second indication information to the second user plane function network element, and the second indication information indicates that the usage of the first data flow is not counted.
  • the session management network element before the session management network element sends a first billing request message to the billing function network element, the session management network element receives second information from the second user plane function network element, and the second information includes the usage of the data flow of the first terminal device counted by the second user plane function network element.
  • the session management network element sends the first charging request message to the charging function network element based on the second information, and the first charging request message also includes identification information of the second user plane function network element and the second information.
  • the session management network element determines the first billing request message and the second billing request message based on the first information and the second information, and the second billing request message includes the identification information of the second user plane function network element and the second information; the session management network element sends the second billing request message to the billing function network element.
  • the first identification information includes at least one of the following information: an identification of the first user plane functional network element, location information of the first terminal device, and a rate group RG associated with the first area.
  • the method before the session management network element obtains the first information of the first terminal device, the method also includes: the session management network element receives a charging rule from a policy control function network element, and the charging rule indicates that the data flow type of the first terminal device is a free data flow.
  • the session management network element obtains the usage of a second data flow, where the second data flow is a data flow of the first terminal device that is diverted from the first user plane function network element to a third user plane function network element, and the third user plane function network element is used to transmit user plane data between the first terminal device and the dedicated network; the session management network element sends a third billing request message to the billing management function, where the third billing request message includes identification information of the third user plane function network element and the usage of the second data flow.
  • the first charging request message also includes identification information of the third user plane function network element and usage of the second data flow.
  • a communication method comprising: a session management network element receives first information from a second user plane function network element, the first information comprising a usage amount of a first data flow, the first data flow comprising a data flow of a first terminal device diverted from the first user plane function network element to the second user plane function network element, the first user plane function network element being used to divert data flows of terminal devices in a first area, the first area being a signing location of a dedicated network signed by the first terminal device, the second user plane function network element being used to transmit user plane data between the first terminal device and a data network; the session management network element sends a first billing request message to the billing function network element, the first billing request message comprising second identification information and the first information, the second identification information being associated with the identification information of the first user plane function network element.
  • the session management network element can receive the usage of the first data flow of the terminal device from the second user plane function network element, where the first data flow includes the data flow of the first terminal device diverted from the first user plane function network element to the second user plane function network element, and send the first identification information and the first information to the billing function network element, so that the billing function network element generates a call bill for the usage of the first data flow, thereby realizing billing for the first data flow.
  • the session management network element before the session management network element receives the first information from the second user plane function network element, the session management network element sends third indication information to the second user plane function network element, and the third indication information indicates to count and report the usage of the first data flow.
  • the first information is associated with the identification information of the second user plane function network element.
  • the session management network element modifies the identification information of the second user plane function network element to second identification information, and the second identification information is associated with the identification information of the first user plane function network element.
  • the session management network element before the session management network element sends a first billing request message to the billing function network element, the session management network element receives second information from the second user plane function network element, and the second information includes the usage of the data flow of the first terminal device counted by the second user plane function network element.
  • the session management network element sends the first charging request message to the charging function network element based on the second information, and the first charging request message also includes identification information of the second user plane function network element and the second information.
  • the session management network element determines the first billing request message and the second billing request message based on the first information and the second information, and the second billing request message includes the identification information of the second user plane function network element and the second information; the session management network element sends the second billing request message to the billing function network element.
  • the session management network element before the session management network element obtains the first information of the first terminal device, the session management network element receives a charging rule from a policy control function network element, and the charging rule indicates that the data flow type of the first terminal device is a free data flow.
  • a communication method comprising: a billing function network element receives a first billing request message from a session management network element, the first billing request message comprising first identification information and first information, the first information comprising a usage amount of a first data flow of a first terminal device, the first data flow comprising a data flow of the first terminal device diverted from a first user plane function network element to a second user plane function network element; the billing function network element generates a first call record for the first terminal device based on the first identification information and the first information; wherein the first user plane function network element is used to divert data flows of terminal devices in a first area, the first area being the signing location of a dedicated network signed by the first terminal device, the second user plane function network element is used to transmit data between the first terminal device and a data network, and the first identification information is used to associate the first area.
  • the first charging request message also includes the second user plane function network element identification information and second information, the second information including the usage of the data flow of the first terminal device counted by the second user plane function network element.
  • the billing function network element before the billing function network element generates a first call bill for the first terminal device based on the first identification information and the first information, the billing function network element splits the first identification information and the first information from the first billing request message.
  • the first billing request message also includes fourth indication information, which indicates that the first data flow is a free data flow. Based on the fourth indication information, the billing function network element stores the first call record of the first terminal device in a first call record directory, and the first call record directory is a call record directory for storing free data flows.
  • the billing function network element is configured with first configuration information, and the first configuration information is used to configure call record processing for free data flows, and the first configuration information includes at least one type of identification information: identification information of the user plane function network element, location area information, and rate group RG information; wherein the identification information of the user plane function network element includes the identification of at least one user plane function network element, the identification of the at least one user plane function network element includes the identification of the first user plane network element, the location area information includes location information of at least one area, the location information of at least one area includes location information of the first terminal device, the rate group information includes information of at least one rate group, and the at least one rate group RG includes the rate group RG associated with the first area.
  • the billing function network element stores the first call record of the first terminal device in a first call record directory based on the first configuration information, and the first call record directory is a call record directory for storing free data streams.
  • the first identification information includes at least one of the following information: an identification of the first user plane functional network element, location information of the first terminal device, and a rate group RG associated with the first area.
  • the billing function network element receives a third billing request message from the session management network element, the third billing request message including identification information of the third user plane function network element and the usage of the second data flow, the second data flow being the data flow of the first terminal device diverted from the first user plane function network element to the third user plane function network element, the third user plane function network element being used to transmit user plane data between the first terminal device and the dedicated network; the third billing function network element generates a third call bill for the terminal device based on the third billing request message, and stores the third call bill in the first call bill directory.
  • the first billing request message also includes identification information of the third user plane function network element and the usage of the second data flow.
  • the billing function network element splits the identification information of the third user plane function network element and the usage of the second data flow from the first billing request message.
  • the third user plane function network element is used to transmit user plane data between the first terminal device and the private network; the third billing function network element generates a third call bill for the terminal device based on the third billing request message, and stores the third call bill in the first call bill directory.
  • a communication device which includes a transceiver unit, and the transceiver unit is used to obtain first information of a first terminal device, the first information including a usage amount of a first data flow, the first data flow including a data flow of the first terminal device diverted from a first user plane function network element to a second user plane function network element, the first user plane function network element being used to divert data flows of terminal devices in a first area, the first area being a signing location of a dedicated network signed by the first terminal device, and the second user plane function network element being used to transmit user plane data between the first terminal device and a data network; the transceiver unit is also used to send a first billing request message to the billing function network element, the first billing request message including first identification information and the first information, and the first identification information being used to associate with the first area.
  • the transceiver unit is specifically used to send first indication information to the first user plane functional network element, the first indication information indicating the statistics and reporting of the usage of the first data flow; and the receiving unit receives the usage of the first data flow from the first user plane functional network element.
  • the transceiver unit is further used to send second indication information to the second user plane function network element, and the second indication information indicates that the usage of the first data flow should not be counted.
  • the transceiver unit is further used to receive second information from the second user plane function network element, and the second information includes the usage of the data flow of the first terminal device counted by the second user plane function network element.
  • the transceiver unit is specifically used to send the first billing request message to the billing function network element based on the second information, and the first billing request message also includes identification information of the second user plane function network element and the second information.
  • the device also includes a processing unit, which is used to determine the first billing request message and the second billing request message based on the first information and the second information, and the second billing request message includes the identification information of the second user plane function network element and the second information; the transceiver unit is also used to send the second billing request message to the billing function network element.
  • the first identification information includes at least one of the following information: An identifier of a user plane functional network element, location information of the first terminal device, and a rate group RG associated with the first area.
  • the transceiver unit is further used to receive a charging rule from a policy control function network element, and the charging rule indicates that the data flow type of the first terminal device is a free data flow.
  • a communication device which includes a transceiver unit, and the transceiver unit is used to receive first information from a second user plane function network element, the first information including a usage amount of a first data flow, the first data flow including a data flow of the first terminal device diverted from the first user plane function network element to the second user plane function network element, the first user plane function network element is used to divert the data flow of the terminal device in a first area, the first area is the signing location of the dedicated network signed by the first terminal device, and the second user plane function network element is used to transmit user plane data between the first terminal device and the data network; the transceiver unit is also used to send a first billing request message to the billing function network element, the first billing request message including second identification information and the first information, and the second identification information is associated with the identification information of the first user plane function network element.
  • the transceiver unit is further used to send third indication information to the second user plane function network element, and the third indication information indicates statistics and reporting of usage of the first data flow.
  • the first information is associated with the identification information of the second user plane functional network element
  • the processing unit is also used to modify the identification information of the second user plane functional network element to second identification information
  • the second identification information is associated with the identification information of the first user plane functional network element
  • the transceiver unit is further used to receive second information from the second user plane function network element, and the second information includes the usage of the data flow of the first terminal device counted by the second user plane function network element.
  • the transceiver unit is specifically used to send the first billing request message to the billing function network element based on the second information, and the first billing request message also includes identification information of the second user plane function network element and the second information.
  • the processing unit is also used to determine the first billing request message and the second billing request message based on the first information and the second information, the second billing request message including the identification information of the second user plane function network element and the second information; the transceiver unit is also used to send the second billing request message to the billing function network element.
  • the transceiver unit is further used to receive a charging rule from a policy control function network element, and the charging rule indicates that the data flow type of the first terminal device is a free data flow.
  • a communication device which includes a transceiver unit and a processing unit, the transceiver unit being used to receive a first billing request message from a session management network element, the first billing request message including first identification information and first information, the first information including a usage amount of a first data stream of a first terminal device, the first data stream including a data stream of the first terminal device diverted from a first user plane function network element to a second user plane function network element; the processing unit being used to generate a first call record for the first terminal device based on the first identification information and the first information; wherein the first user plane function network element is used to divert data streams of terminal devices in a first area, the first area being the signing location of a dedicated network signed by the first terminal device, the second user plane function network element being used to transmit data between the first terminal device and a data network, and the first identification information being used to associate with the first area.
  • the first billing request message also includes identification information of the second user plane function network element and second information, and the second information includes the usage of the data flow of the first terminal device counted by the second user plane function network element.
  • the processing unit is further used to split the first identification information and the first information from the first charging request message.
  • the first billing request message also includes fourth indication information, which indicates that the first data flow is a free data flow.
  • the billing function network element stores the first call record of the first terminal device in a first call record directory based on the fourth indication information, and the first call record directory is a call record directory for storing free data flows.
  • the apparatus is configured with first configuration information, the first configuration information being used to configure call record processing for free data flows, the first configuration information including at least one type of identification information: identification information of a user plane function network element, location area information, and rate group RG information; wherein the identification information of the user plane function network element includes an identification of at least one user plane function network element, the identification of the at least one user plane function network element includes an identification of the first user plane network element, the location area information includes location information of at least one area, the location information of the at least one area includes location information of the first terminal device, the rate group information includes information of at least one rate group, and the at least one rate group RG includes the rate group RG associated with the first area.
  • identification information of the user plane function network element includes an identification of at least one user plane function network element
  • the identification of the at least one user plane function network element includes an identification of the first user plane network element
  • the location area information includes location information of at least one area
  • the location information of the at least one area includes location information of the first terminal device
  • the device further includes a storage unit, and the processing unit is further configured to store the first call record of the first terminal device in a first call record directory based on the first configuration information, and the first call record directory is a directory for storing free data.
  • the call list directory of the flow is a directory for storing free data.
  • the first identification information includes at least one of the following information: an identification of the first user plane functional network element, location information of the first terminal device, and a rate group RG associated with the first area.
  • a communication device comprising: at least one processor, configured to execute a computer program or instruction stored in a memory, so as to execute the method in any possible implementation of the first to third aspects above.
  • the device further comprises a memory, configured to store a computer program or instruction.
  • the device further comprises a communication interface, and the processor reads the computer program or instruction stored in the memory through the communication interface.
  • the device is a session management network element or a charging function network element.
  • the device is a chip, a chip system or a circuit used for a session management network element or a charging function network element.
  • the present application provides a processor for executing the methods provided in the first to third aspects above.
  • a computer-readable storage medium which stores a program code for execution by a device, wherein the program code includes a method for executing any possible implementation of the first to third aspects above.
  • a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute a method in any possible implementation of the first to third aspects.
  • FIG1 is a schematic diagram of a communication system applicable to the method provided in an embodiment of the present application.
  • Figure 2 is a schematic diagram of the inter-provincial roaming architecture applicable to the present application.
  • FIG3 is a diagram of an uplink split local split architecture applicable to the present application.
  • FIG4 is a schematic diagram of an application scenario to which the present application is applicable.
  • FIG. 5 is a schematic flowchart of a communication method 500 provided in an embodiment of the present application.
  • FIG. 6 is a schematic flowchart of a communication method 600 provided in an embodiment of the present application.
  • FIG. 7 is a schematic flowchart of a communication method 700 provided in an embodiment of the present application.
  • FIG. 8 is a schematic flowchart of a communication method 800 provided in an embodiment of the present application.
  • FIG. 9 is a schematic diagram of a communication device provided in an embodiment of the present application.
  • FIG10 is a schematic block diagram of a communication device provided in another embodiment of the present application.
  • FIG. 11 is a schematic diagram of a chip system provided in an embodiment of the present application.
  • the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: long term evolution (LTE) system, frequency division duplex (FDD) system, time division duplex (TDD) system, worldwide interoperability for microwave access (WiMAX) communication system, fifth generation (5G) system or new radio (NR), sixth generation (6G) system or future communication system, etc.
  • LTE long term evolution
  • FDD frequency division duplex
  • TDD time division duplex
  • WiMAX worldwide interoperability for microwave access
  • 5G fifth generation
  • NR new radio
  • 6G sixth generation
  • the 5G mobile communication system described in the present application includes a non-standalone (NSA) 5G mobile communication system or a standalone (SA) 5G mobile communication system.
  • the communication system may also be a public land mobile network (PLMN), a device to device (D2D) communication system, a machine to machine (M2M) communication system, an Internet of things (IoT) communication system, a vehicle to everything (V2X) communication system, an uncrewed aerial vehicle (UAV) communication system or other communication systems.
  • PLMN public land mobile network
  • D2D device to device
  • M2M machine to machine
  • IoT Internet of things
  • V2X vehicle to everything
  • UAV uncrewed aerial vehicle
  • FIG1 shows a schematic diagram of a communication system 100 applicable to the method provided in an embodiment of the present application.
  • the communication system 100 may include but is not limited to the following parts:
  • UE User equipment
  • UE can include various handheld devices with wireless communication functions, vehicle-mounted devices, wearable devices, computing devices or other processing devices connected to wireless modems, as well as various forms of terminals, mobile stations (MS), terminals or soft terminals, etc.
  • MS mobile stations
  • terminals or soft terminals etc.
  • water meters electricity meters, sensors, etc.
  • the user equipment in the embodiments of the present application may refer to an access terminal, a user unit, a user station, a mobile station, a mobile station, a Relay station, remote station, remote terminal, mobile device, user terminal, terminal equipment, wireless communication device, user agent or user device.
  • the user equipment may also be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a user equipment in a 5G network or a user equipment in a future evolved public land mobile network (PLMN) or a user equipment in a future Internet of Vehicles, etc., and the embodiments of the present application are not limited to this.
  • SIP session initiation protocol
  • WLL wireless local loop
  • PDA personal digital assistant
  • PDA personal digital assistant
  • wearable devices may also be referred to as wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed by applying wearable technology to daily wear, such as glasses, gloves, watches, clothing, and shoes.
  • a wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction.
  • wearable smart devices include full-featured, large-sized, and independent of smartphones to achieve complete or partial functions, such as smart watches or smart glasses, as well as devices that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various types of smart bracelets and smart jewelry for vital sign monitoring.
  • the user device may also be a user device in the Internet of Things (IoT) system.
  • IoT Internet of Things
  • Its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network of human-machine interconnection and object-to-object interconnection.
  • IOT technology can achieve massive connections, deep coverage, and terminal power saving through narrowband (NB) technology, for example.
  • the user device may also include sensors such as smart printers, train detectors, and gas stations.
  • the main functions include collecting data (part of the user device), receiving control information and downlink data of the access network device, and sending electromagnetic waves to transmit uplink data to the access network device.
  • Radio access network (R)AN) used to provide network access for authorized user devices in a specific area, and can use transmission tunnels of different qualities according to the level of user equipment, business requirements, etc.
  • (R)AN can manage wireless resources, provide access services for user equipment, and then complete the forwarding of control signals and user equipment data between user equipment and the core network.
  • (R)AN can also be understood as a base station in a traditional network.
  • the access network device in the embodiment of the present application can be any communication device with wireless transceiver function for communicating with user equipment.
  • the access network device includes but is not limited to: evolved Node B (eNB), radio network controller (RNC), Node B (NB), base station controller (BSC), base transceiver station (BTS), home evolved Node B (HeNB, or home Node B, HNB), baseband unit (BBU), wireless fidelity (wireless fidelity)
  • the invention may be an access point (AP), a wireless relay node, a wireless backhaul node, a transmission point (TP) or a transmission and reception point (TRP) in a wireless cellular network (e.g., WiFi) system, and may also be a gNB in a 5G, such as NR, system, or a transmission point (TRP or TP), one or a group of (including multiple antenna panels) antenna panels of a base station in a 5G system, or may also be a network node constituting a gNB or
  • the gNB may include a centralized unit (CU) and a DU.
  • the gNB may also include an active antenna unit (AAU).
  • the CU implements some functions of the gNB, and the DU implements some functions of the gNB.
  • the CU is responsible for processing non-real-time protocols and services, and implements the functions of the radio resource control (RRC) and packet data convergence protocol (PDCP) layers.
  • the DU is responsible for processing physical layer protocols and real-time services, and implements the functions of the radio link control (RLC), media access control (MAC) and physical (PHY) layers.
  • the AAU implements some physical layer processing functions, RF processing, and related functions of active antennas.
  • the access network device may be a device including one or more of a CU node, a DU node, and an AAU node.
  • the CU may be classified as an access network device in an access network (radio access network, RAN), or the CU may be classified as an access network device in a core network (core network, CN), and this application does not limit this.
  • AMF Access and mobility management function
  • the access and mobility management function network element can be used for mobility management and access management, etc., and can be used to implement other functions of the mobility management entity (MME) function except session management, such as legal detection or access authorization, etc., and is also used to transmit user policies between terminal equipment and policy control function (PCF) network element.
  • MME mobility management entity
  • PCF policy control function
  • the access and mobility management function network element can be used to implement the functions of the access and mobility management network element.
  • the session management function network element can be used for session management, allocation and management of Internet protocol (IP) addresses of terminal devices, selection and management of user plane function (UPF) network elements, termination points of policy control and charging function interfaces, and downlink data notification, etc.
  • IP Internet protocol
  • UPF user plane function
  • the session management function network element can be used to implement the functions of the session management network element.
  • the user plane functional network element can be used for packet routing and forwarding, or quality of service (QoS) parameter processing of user plane data, etc.
  • User data can be connected to the data network (DN) through this network element.
  • DN data network
  • the user plane function network element can be used to implement the functions of the user plane network element.
  • the session management function network element is required to select a suitable user plane function network element for the session of the terminal device.
  • the policy control network element is used to guide the unified policy framework of network behavior and provide policy rule information for control plane function network elements (such as access and mobility management function network element, session management function network element, etc.). It is mainly responsible for policy control functions such as charging for sessions and service flows, QoS bandwidth guarantee and mobility management, and terminal device policy decision-making.
  • the policy control network element can have the capabilities of both the access and mobility management policy control network element (policy control function for access and mobility control, AM PCF) and the session management policy control network element (PCF for session management, SM PCF).
  • policy control function for access and mobility control, AM PCF
  • PCF session management policy control network element
  • the access and mobility management policy control network element and the session management policy control network element can be understood as different network elements with different capabilities.
  • the access and mobility management policy control network element and the session management policy control network element can be the same policy control network element entity, that is, deployed separately, or two different policy control network element entities, that is, deployed in one.
  • the access and mobility management policy control network element can be directly connected to the access and mobility management function network element, and the access and mobility management policy control network element can provide mobility and access selection related policies of terminal devices to the access and mobility management function network element.
  • the mobility policy may include, for example, service area restriction management, radio access technology frequency selection priority (RFSP) index management and session management function network element selection management;
  • the access selection related policies of terminal devices may include access network discovery and selection policy (ANDSP) and route selection policy (URSP) of terminal devices.
  • RFSP radio access technology frequency selection priority
  • ANDSP access network discovery and selection policy
  • URSP route selection policy
  • the session management policy control network element can be directly connected to the session management function network element to provide the session management function network element with protocol data unit (PDU) session-related policies.
  • PDU session-related policies include, for example, gating policies, charging policies, QoS control policies, usage monitoring control policies, etc.
  • the policy control network element of the visited location can logically include the access and mobility management policy control network element of the visited location and the session management policy control network element of the visited location; the policy control network of the home location can logically include the access and mobility management policy control network element of the home location and the session management policy control network element of the home location.
  • the access and mobility management policy control network element of the visited location and the session management policy control network element of the visited location can be the same policy control network element entity of the visited location, or they can be two different policy control network element entities of the visited location.
  • the access and mobility management policy control network element of the home location and the session management policy control network element of the home location can be the same policy control network element entity of the home location, or they can be two different policy control network element entities of the home location.
  • NEF Network exposure function
  • AF application function
  • the network capability exposure function network element is used to open the services and network capability information (such as terminal location) provided by the 3GPP network function to the outside.
  • the application function is mainly used to send the application side's requirements to the network side, such as QoS requirements or user status event subscriptions.
  • AF can be a third-party functional entity or an application service deployed by an operator, such as IP multimedia subsystem (IMS) voice call service.
  • IMS IP multimedia subsystem
  • the unified data management network element can be used for unified data management, supporting authentication trust state processing in 3GPP authentication and key negotiation mechanism, user identity processing, access authorization, registration and mobility management, contract management, short message management, etc.
  • the unified data storage network element can be used for access functions of contract data, policy data, application data and other types of data.
  • a data network refers to a specific data service network that a terminal device accesses.
  • typical data networks include the Internet. (internet), IMS.
  • the above network elements may also be referred to as entities, devices, apparatuses or modules, etc., which are not specifically limited in this application.
  • the above parts may be represented by abbreviations.
  • the session management function network element is referred to as SMF, and the "SMF" should be understood as a session management function network element, or as a network element or device having functions similar to those of the session management function network element. The same is true for other purposes and will not be repeated.
  • the network architecture involved in Figure 1 may also include other network elements, such as a unified data repository (UDR) or a charging function (CHF) and other network elements or devices, without specific limitation.
  • UDR unified data repository
  • CHF charging function
  • N7 The interface between PCF and SMF, used to deliver PDU session granularity and service data flow granularity control strategy.
  • N15 The interface between PCF and AMF, used to deliver UE policies and access control related policies.
  • N5 The interface between AF and PCF, used for issuing application service requests and reporting network events.
  • N4 The interface between SMF and UPF is used to transmit information between the control plane and the user plane, including the control of the forwarding rules, QoS control rules, traffic statistics rules, etc. for the user plane and the reporting of information on the user plane.
  • N11 The interface between SMF and AMF, used to transmit PDU session tunnel information between RAN and UPF, control messages sent to UE, radio resource control information sent to RAN, etc.
  • N2 The interface between AMF and RAN, used to transmit radio bearer control information from the core network to the RAN.
  • N1 The interface between AMF and UE, access-independent, used to transmit QoS control rules to UE.
  • N36 The interface between PCF and UDR is used by PCF to obtain policy-related contract data and application data-related information from UDR.
  • NEF also has direct interfaces with AMF and SMF, corresponding to N29 interface and N51 interface respectively (not shown in the above figure to simplify the diagram), which are used to open the operator's network capabilities to third-party application functional entities.
  • the former can be used for NEF to directly subscribe to corresponding network events from AMF and update user configuration information, and the latter can be used to update application configuration data on SMF/UPF, such as the packet flow description (PFD) corresponding to the application identity.
  • PFD packet flow description
  • the above-mentioned network architecture applied to the embodiments of the present application is merely an example of a network architecture described from the perspective of a traditional point-to-point architecture and a service-oriented architecture.
  • the network architecture applicable to the embodiments of the present application is not limited to this. Any network architecture that can realize the functions of the above-mentioned network elements is applicable to the embodiments of the present application.
  • the interface name between the network elements in Figure 1 is only an example, and the name of the interface in the specific implementation may be other names, which are not specifically limited in this application.
  • the name of the message (or signaling) transmitted between the above network elements is only an example and does not constitute any limitation on the function of the message itself.
  • the above network element or function can be a network element in a hardware device, a software function running on dedicated hardware, or a virtualized function instantiated on a platform (e.g., a cloud platform).
  • a platform e.g., a cloud platform
  • the above network element or function can be implemented by one device, or by multiple devices together, or by a functional module in one device, which is not specifically limited in the embodiments of the present application.
  • each component network element is merely exemplary, and not all functions of each component network element are required when applied in the embodiments of the present application.
  • each network element such as PCF, AMF, etc.
  • Figure 1 the naming of each network element (such as PCF, AMF, etc.) included in Figure 1 is only a name, and the name does not limit the function of the network element itself.
  • the above network elements may also have other names, and this application does not make specific restrictions on this.
  • some or all of the above network elements may use the terminology in 5G, or may be named otherwise.
  • the communication between the various network elements of the control plane function in Figure 1 is described using a non-service interface as an example, but this does not limit the scope of protection of the embodiments of the present application.
  • the various network elements of the control plane function in Figure 1 can also communicate through a service interface.
  • the service interface provided by AMF to the outside may be Namf; the service interface provided by SMF may be Nsmf; the service interface provided by CHF may be Nchf; the service interface provided by PCF to the outside may be Npcf, and so on.
  • the network element in FIG. 1 above is an architecture based on a reference point and does not constitute a limitation on the embodiments of the present application.
  • FIG. 2 shows a schematic diagram of an inter-provincial roaming architecture applicable to the present application.
  • the UE is a roaming user whose contract information is in the home network.
  • the DN of the visited location is accessed through the RAN and UPF of the visited location.
  • Both the AMF and SMF are located in the visited location (i.e., the visited province).
  • the PCF (home-PCF, H-PCF) of the home location i.e., the home province) sends corresponding policy rules to the SMF of the visited location through the N7 interface, and can provide services for the UE according to the policy rules.
  • the AMF of the visited location can obtain the corresponding access and mobility management policies through the PCF (visited-PCF, V-PCF) of the visited location, and provide services for the UE according to the access and mobility management policies.
  • the H-PCF here can be a separately deployed SM-PCF at the home location, or it can be the SM-PCF and AM-PCF at the home location deployed in a unified manner;
  • the V-PCF here can be a separately deployed AM-PCF at the visited location, or it can be the SM-PCF and AM-PCF at the visited location deployed in a unified manner.
  • FIG3 shows a UL CL local offload architecture diagram applicable to the present application.
  • the architecture shown in FIG3 is located in the visited location, and the UE can be a roaming user or a home user.
  • operators may deploy UPF nodes near the RAN, namely UPF/UL CL, PDU session anchor (PSA) 1-UPF, PSA2-UPF, so that users can access application services nearby.
  • PDU session anchor (PSA) 1-UPF PDU session anchor
  • PSA2-UPF PDU session anchor
  • the visited network adopts the UL CL method to route the regional related service flows directly to different data networks via ULCL/UPF, such as the internal service network of the campus and the Internet.
  • the DN connected to the PSA2-UPF through the N6 interface can be the internal service network of the campus; the DN connected to the PSA1-UPF through the N6 interface is the Internet.
  • PSA1-UPF can be understood as the primary anchor point UPF, and PSA2-UPF can be understood as the secondary anchor point UPF.
  • the DN connected to the PSA2-UPF through the N6 interface can also be connected to the Internet, that is, users can also access Internet services through the internal service network of the campus.
  • the UPF/UL CL, PSA1-UPF, and PSA2-UPF in Figure 3 can be deployed separately or in combination.
  • the UL CL/UPF can be deployed in combination with the PSA2-UPF, or in combination with the PSA1-UPF, or in combination with both the PSA1-UPF and the PSA2-UPF.
  • a park can also be called a park institution or a commercial institution.
  • a park can be a shopping mall or corporate park, a central business district, or a cafe or restaurant.
  • the method provided by the embodiment of this application is mainly introduced by taking the park of the visited place as an example.
  • the home place of the terminal device is Shanghai
  • the visited place is Beijing
  • the park of the visited place can be a shopping mall in Beijing.
  • the park internal service network is a network that provides resources or services by the park and provides services to users within the park. It is understandable that a network with the same or similar functions can also be regarded as the park internal service network in this application, and the name is not limited.
  • the service can be an enterprise's office service, AR, VR, etc.
  • the DN connected to the PSA2-UPF in Figure 3 can be the park internal service network.
  • the campus private network i.e., the campus operator network deployed within the campus, can support campus users to access campus services through the network, and/or access Internet services, such as instant messaging, email, web browsing, etc.
  • the equipment used to provide the campus private network can be a 5G device, such as the UL CL/UPF, PSA2-UPF, and DN connected to the PSA2-UPF in Figure 3.
  • the traffic can include Internet service traffic and park service traffic. That is, users can access park services for free within the park, and can access Internet services for free or for a fee; users are charged normally for accessing the Internet outside the park.
  • Free/unified payment means that under certain conditions (for example, within the park), when users access the park's internal service network or the Internet, the operator does not charge the user, but settles fees with the park.
  • the free/unified payment traffic is referred to as free traffic below.
  • SMF sends billing rules to the secondary anchor point UPF and the main anchor point UPF respectively, so that the anchor point UPF (including the main anchor point UPF and the secondary anchor point UPF) can count the user's traffic; the anchor point UPF reports the user's traffic usage to the CHF of the province through SMF, so that the CHF can generate a call bill.
  • the operator's billing collection system collects call bills from CHF, and the call bills of non-visited users are sent back to the user's home location through the collection system.
  • the operator's business operation support system processes the call bill and performs billing. In the process of processing the call bill, it is necessary to distinguish between free traffic and normal charging traffic, and settle the free traffic with the campus, and the normal charging part with the end user.
  • the UE when the UE is outside the campus, the UE can transmit the data flow of the service in the data network through PSA1 (PSA1-UPF), and the data network can be the Internet; when the UE is inside the campus, the UE can transmit the data flow of the campus private network service through ULCL+PSA2 (which can be a network element deployed with UL CL/UPF and PSA2-UPF), and the UE can also access the Internet service in the campus through ULCL+PSA2 and PSA1.
  • ULCL+PSA2 which can be a network element deployed with UL CL/UPF and PSA2-UPF
  • the UE can also access the Internet service in the campus through ULCL+PSA2 and PSA1.
  • the Internet traffic of the UE In the campus, the Internet traffic of the UE is diverted to PSA1. If a rating group (RG) is not applied for separately for the campus, it may not be possible to filter out the free Internet traffic.
  • RG rating group
  • the service traffic of different parks can be associated with different RGs, that is, the traffic of different parks and the free and normal paid traffic can be distinguished according to different RGs. Since RGs are planned uniformly by operators and the number of locations and parks involved in this implementation is very large, the feasibility is low. Therefore, how to implement the billing of free traffic within the park has become an urgent problem to be solved.
  • an embodiment of the present application provides a communication method to implement billing of free traffic within a park.
  • Fig. 5 shows a schematic flow chart of a communication method 500 provided by the present application. The method may include the following steps.
  • the session management network element obtains first information of the first terminal device.
  • the first information includes the usage of the first data flow, and the first data flow includes the data flow of the first terminal device that is diverted from the first user plane function network element to the second user plane function network element.
  • the first user plane function network element can be used to divert data streams of terminal devices in the first area, that is, the first user plane function network element can divert data streams of terminal devices in the first area to the anchor user plane function network element.
  • the first area can be the signing location of the dedicated network signed by the first terminal device.
  • the first terminal device can be any terminal device in the first area.
  • the second user plane function network element may be used to transmit user plane data between the first terminal device and the data network.
  • the second user plane function network element may be a primary anchor user plane function network element, which may not be changed during the session life cycle of the first terminal device; the data network may be the Internet.
  • the first area may be the area where the park #1 is located
  • the first user plane function may be a user plane function network element for uplink diversion deployed near the park #1
  • the second user plane function network element may be an anchor user plane function network element deployed in the city to which the park #1 belongs
  • the first user plane function network element may divert the data flow of the first terminal device to the second user plane function network element and/or the third user plane function network element according to the diversion rule.
  • the third user plane function network element may be an auxiliary anchor user plane function network element, which is used to transmit user plane data between the first terminal device and the dedicated network.
  • the third user plane function network element may be deployed together with the first user plane function network element, or deployed separately.
  • the session management network element sends first indication information to the first user plane function network element, and the first indication information instructs the first user plane function network element to count and report the usage of the first data flow; the session management network element receives first information from the first user plane function network element, and the first information includes the statistical results of the first user plane function network element; the session management network element associates the usage of the first data flow with the first identification information.
  • the first information may also include the first identification information
  • the session management network element may associate the first identification information with the usage of the first data flow according to the first information.
  • the session management network element may obtain the first identification information and associate the first identification information with the usage of the first data flow.
  • associating the first identification information with the usage of the first data flow may be understood as that the usage of the first data flow may be known by querying the first identification information.
  • the first identification information includes at least one of the following information: the identification of the first user plane functional network element, the location information of the first terminal device, and the rating group (RG) associated with the first area.
  • the location information of the first terminal device may be, for example, an identifier of a cell where the first terminal device is located, such as an NR cell global identifier (NCGI), a tracking area code (TAC) corresponding to the tracking area where the first terminal device is located, an identifier of an access network device to which the first terminal device is connected, and an identifier of the geographical location where the first terminal device is located.
  • NCGI NR cell global identifier
  • TAC tracking area code
  • the range of the geographical location may be smaller than the range of the TA.
  • the geographical location may be a county or a street.
  • the method further includes: the session management network element sends second indication information to the second user plane function network element, and the second indication information may instruct the second user plane function network element not to count the usage of the first data flow. That is, while the session management network element instructs the first user plane function network element to count the first data flow, the session management network element also instructs the second user plane function network element not to count the usage of the first data flow, thereby ensuring that the first data flow is not overcharged or undercharged.
  • the session management network element may also obtain second information.
  • the second information includes the usage of the data flow of the first terminal device counted by the second user plane function network element.
  • the session management network element may actively query the second user plane function network element for the data flow usage of the first terminal device; or, when the session of the first terminal device is deleted, the second user plane function network element may report the data flow usage of the first terminal device.
  • the second user plane function network element periodically reports the statistics of the data flow usage of the first terminal device.
  • the session management network element may receive the first information from the second user plane function network element, that is, the session management network element may receive the usage of the first data flow counted by the second user plane function network element.
  • the session management network element sends third indication information to the second user plane function network element, and the third indication information can instruct the second user plane function network element to count and report the usage of the first data flow; the session management network element receives the usage of the first data flow from the second user plane function network element, and the usage of the first data flow is associated with the identifier of the second user plane function network element.
  • the second user plane function network element can report the identification information of the second user plane function network element and the usage of the first data flow, or the session management network element can obtain the identification information of the second user plane function network element and associate the identification information of the second user plane function network element with the usage of the first data flow.
  • the session management network element modifies the identification information of the second user plane function network element into second identification information.
  • the second identification information is associated with the identification information of the first user plane network element.
  • the identification information of the second user plane function network element is a second character string
  • the identifier of the first user plane function network element is a first character string
  • the session management network element may modify the identifier of the second user plane function network element into the first character string plus the second character string.
  • the session management network element can modify the identifier of the second user plane network element associated with the usage of the first data flow to an identifier associated with the identifier of the first user plane network element.
  • the method further includes: the session management network element sends indication information to the third user plane function network element, and the indication information can instruct the third user plane function network element to count and report the usage of the second data flow.
  • the second data flow is the data flow of the first terminal device that is diverted from the first user plane network element to the third user plane network element.
  • the second data flow can be a data flow of a service in the dedicated network.
  • the third user plane function network element sends the usage of the second data flow to the session management network element.
  • the third user plane function network element may also send identification information of the third user plane function network element to the session management network element, so that the identification information of the third user plane function network element is associated with the usage of the second data flow.
  • the identification information of the first user plane function network element and the identification information of the third user plane function network element may be the same; when the first user plane function network element and the third user plane function network element are deployed independently, the identification information of the first user plane function network element and the identification information of the third user plane function network element may be different.
  • the method further includes: the session management network element receiving a charging rule from a policy control function network element.
  • the charging rule indicates that the first data flow is free traffic.
  • S520 The session management network element sends a first charging request message to the charging function network element.
  • the charging function network element receives the first charging request message from the session management network element.
  • the first charging request message may include the first identification information and the usage amount of the first data flow.
  • the first charging request message may also include the identification information of the second user plane function network element and the usage of the data flow of the first terminal device counted by the second user plane function network element, the identification information of the third user plane network element and the usage of the second data flow (third information).
  • the method may also include: the session management network element determines the first billing request message based on the first information, the second information, and at least one of the third information, or in other words, when the session management network element receives the first information, the second information and the third information from the first user plane function network element, the session management network element splits the first billing request message, the second billing request message and the third billing request message, so that the first billing request message includes the first identification information and the usage of the first data flow, the second billing request message includes the identification information of the second user plane function network element and the usage of the data flow of the first terminal device counted by the second user plane function network element, and the third billing request message includes the identification information of the third user plane function network element and the usage of the second data flow.
  • the usage of the data flow of the first terminal device counted by the second user plane functional network element may be zero or empty.
  • the billing function network element generates a first call bill for the first terminal device based on the first identifier and the first information.
  • the first call bill can be used to bill usage of the first data flow of the first terminal device.
  • the method may further include: the billing function network element splits the first identification information and the usage of the first data flow from the first billing request message, and generates a first call bill for the first terminal device based on the first identification and the first information; optionally, the billing function network element splits the second identification information and the usage of the data flow of the first terminal device counted by the second user plane function network element from the first billing request message, and generates a second call bill for the first terminal device; the billing function network element splits the identification information of the third user plane function network element and the usage of the second data flow from the first billing request message, and generates a third call bill for the first terminal device.
  • the method further includes S540, the charging function network element storing the first call record of the first terminal device in a first call record directory.
  • the first call record directory is used to store call records of free data flows.
  • the billing function network element stores the third call record of the first terminal device in the first call record directory.
  • the billing function network element is configured with first configuration information, and the billing function network element stores the first call record in a first call record directory based on the first configuration information.
  • the first configuration information may include at least one of the following types of information: identification information of a user plane function network element, location area information, and rate group information.
  • the identification information of the user plane function network element may include the identification of at least one free-flow user plane function network element, and the at least one free-flow user plane function network element includes the first user plane function network element.
  • the identification information of the user plane function network element may be an identification list of user function network elements, and the identification list includes the identification of the first user plane function network element.
  • the free-flow user plane function network element can be understood as a user plane function network element that transmits free data flows.
  • the location area information may include location information of at least one area, and the at least one area is a free flow area.
  • the free flow area can be understood as a data flow of the terminal device in the area can be free.
  • the at least one area can be a cell, a tracking area TA, a geographical location, etc.
  • the at least one area includes the first area.
  • the at least one rate group may include a rate group corresponding to at least one free flow user plane function network element, or a rate group corresponding to at least one free flow area.
  • the billing function network element can query whether the first identification information belongs to the identification list of the free-flow user plane function network element configured by the first configuration information, or the identification list of the location area or the list of rate groups. If so, the billing function network element stores the first call record in the first call record directory.
  • the first billing request message carries fourth indication information, and the fourth indication information indicates that the first data flow is free data volume.
  • the billing function network element stores the first call record in the first call record directory according to the fourth indication information.
  • the operator's billing system may not collect the first call record back to the home location, thereby avoiding the situation in the prior art where the first call record is collected back to the home location and processed by the home location, but the home location cannot identify the data flow that requires free of charge at the visited location.
  • the session management network element can obtain the usage of the first data flow of the terminal device, the first data flow includes the data flow of the first terminal device diverted by the first user plane function network element to the second user plane function network element, and send the first identification information and the first information to the billing function network element, so that the billing function network element generates a bill for the usage of the first data flow, and realizes the billing of the first data flow.
  • the first user plane function network element is used to divert the data flow of the terminal device in the first area, the first area is the contract location of the dedicated network contracted by the first terminal device, and the second user plane network element is used to transmit the user plane data between the first terminal device and the data network.
  • UE#1 in Figure 6 is an example of the first terminal device in Figure 5
  • PCF is an example of the policy control network element in Figure 5
  • ULCL+PSA1 is an example of the first user plane network element in Figure 5
  • SMF is an example of the session management network element in Figure 5
  • PSA2 is an example of the second user plane network element in Figure 5.
  • UE#1 Before S601, UE#1 registers as a member in the campus membership system.
  • UE#1 registers to become a member of the park.
  • the campus membership system enters the membership information of UE#1 (eg, user identification information) and may send the membership information of UE#1 to PCF.
  • the campus membership system may send the membership information of UE#1 to PCF via the capability exposure platform.
  • the PCF may be an H-PCF or a V-PCF.
  • the H-PCF may be an AM-PCF or an SM-PCF, or an AM-PCF and an S-PCF deployed in one;
  • the PCF is a V-PCF, the V-PCF may be an AM-PCF, or an AM-PCF and an S-PCF deployed in one.
  • the user identifier can also be understood as the user's number, such as mobile station international integrated services digital network number (MSISDN), generic public subscription identifier (GPSI), international mobile subscriber identity (IMSI) or subscription permanent identifier (SUPI).
  • MSISDN mobile station international integrated services digital network number
  • GPSI generic public subscription identifier
  • IMSI international mobile subscriber identity
  • SUPI subscription permanent identifier
  • PCF sends campus policy to SMF via AMF.
  • SMF receives campus policy from PCF.
  • the PCF can send the campus policy of the campus to the SMF through the AMF based on the membership information.
  • the campus policy may include a charging rule.
  • the charging rule may indicate processing and charging of different types of data flows, where different types of data flows may include normally charged data flows and free data flows.
  • the campus strategy may also include information such as diversion rules and QoS parameters.
  • the diversion rules are used to instruct UPF, such as ULCL UPF, to divert the contracted services;
  • QoS parameters may include aggregate maximum bit rate (AMBR), allocation and retention priority (ARP), guaranteed flow bit rate (GFBR), maximum flow bit rate (MFBR), 5G QoS identifier (5QI), etc.
  • the PCF may also send an identifier of a campus policy to the SMF, in which at least one campus policy and an identifier corresponding to the campus policy are configured.
  • the SMF may match the corresponding campus policy through the identifier of the campus policy.
  • S602a SMF sends a session management message to ULCL+PSA2.
  • ULCL+PSA1 receives the session management message from SMF.
  • the session management message is used by UPF to manage the PDU session of the UE.
  • the session management message may be a PFCP session establishment request (PFCP Session Establishment Request) message or a PFCP session modification request (PFCP Session Modification Request) message.
  • the session management message may carry charging rules.
  • the charging rules may include packet detection rules (PDR) and usage reporting rules (URR).
  • PDR packet detection rules
  • URR usage reporting rules
  • PDR and URR indicate that ULCL+PSA2 detects and reports the data flow of UE#1 forwarded locally, forwarded through the N6 interface, or forwarded through the N19 tunnel.
  • the session management message carries indication information #1 (an example of the first indication information), and the indication information #1 indicates the usage of the data flow diverted to PSA1 by the ULCL UPF statistics.
  • the SMF will associate the PDR used to divert traffic to PSA1 with the URR, and send the PDR and the associated URR to the ULCL UPF to instruct the ULCL UPF to make statistical reports on the data flow (an example of the first data flow) diverted to PSA1.
  • the session management message may carry a diversion rule so that the ULCL UPF diverts the data flow of UE#1 to multiple anchor UPFs, such as PSA1 and PSA2.
  • the data flow diverted to PSA2 may be the data flow of the campus service subscribed by UE#1
  • the service diverted to PSA1 may be the data flow of the Internet service.
  • S603a, ULCL+PSA2 sends the usage of the data flow diverted to PSA1 to the SMF.
  • ULCL+PSA2 may send the usage of the data flow diverted to PSA1 to SMF via a PFCP session report request (PFCP Session Report Request message).
  • PFCP Session Report Request message may also carry the identifier of ULCL+PSA2, or the identifier of ULCL UPF.
  • S602b SMF sends a session management message to PSA1.
  • the session management request message may refer to the relevant description in S603a.
  • the session management message carries indication information #2 (an example of second indication information), and the indication information #2 indicates that the PSA1 does not count the usage of the data flow diverted to the PSA1.
  • This step can be executed before S603a, or, this step can be executed simultaneously with S602a, that is, while SMF instructs ULCL UPF to report the usage of the first data flow, SMF can instruct PSA1 not to make statistics on the data flow of UE#1 diverted to PSA1.
  • SMF can also send session management messages to PSA2.
  • the session management message may carry a charging rule to instruct PSA2 to perform statistics reporting on the data flow diverted to PSA2.
  • PSA2 sends the statistical usage of the data flow of UE#1 to SMF.
  • the statistical usage of the data flow of UE#1 by PSA2 may be the data flow of the campus service.
  • SMF may also obtain the usage of the data flow of UE#1 counted by PSA1.
  • the SMF can actively query PSA1 about the data flow usage of UE#1; or, when the session of UE#1 is deleted, PSA1 can report the data flow usage of UE#1.
  • S605 SMF sends a charging request message to CHF based on the usage of the data flow diverted to PSA1 sent by ULCL+PSA2 and the usage of the data flow of UE#1 counted by PSA1.
  • CHF receives the charging request message from SMF.
  • the charging request message may be a charging data request (Charging Data Request) message.
  • the charging request message may include the identifier of ULCL+PSA2 and the usage of the data flow diverted to PSA1 sent by ULCL+PSA2, the identifier of PSA1 and the usage of the data flow of UE#1 reported by PSA1. That is, a charging request message sent by SMF to CHF may include multiple UPF IDs and the usage of the data flow of UE#1 counted by the corresponding UPF.
  • SMF needs to split the call record based on UPF ID, that is, split the usage of the data flow counted by ULCL+PSA2 and PSA1 into different messages and report them to CHF.
  • CHF generates a call record for UE#1 based on the charging request message, and stores the call record corresponding to the data flow usage of UE#1 counted by ULCL+PSA2 in call record directory #1.
  • the bill directory #1 is used to store bills corresponding to the free data flow usage.
  • the bill directory #1 can be a newly added bill directory in CHF.
  • the CHF can split the call bill of UE#1 based on the charging request message. That is, the CHF can generate call bills based on each UPF ID and the usage of UE#1's data flow counted by the UPF corresponding to the UPF ID.
  • the multiple UPFs may include ULCL+PSA2 and PSA1.
  • the CHF may configure a UPF ID list of free flows, and the CHF determines whether the data flow of UE#1 counted by the UPF is a free flow according to the UPF ID in the charging request message. For example, if the charging request message includes the ID of ULCL+PSA2, the CHF may determine to store the call record corresponding to the ID of ULCL+PSA2 in the call record directory #1 by querying the UPF ID list.
  • the charging request message may also carry indication information #4, where the indication information #4 indicates that the data flow counted by ULCL+PSA2 is a free flow.
  • CHF may determine through the indication information #4 that the call record corresponding to the ID of ULCL+PSA2 is stored in the call record directory #1.
  • the operator's billing system may not collect the call records in the newly added free-flow directory (call record directory #1) back to the home location.
  • the billing of the home location can extract the free-flow call records from the call record directory #1 of the visited CHF, distinguish the parks according to the UPF ID, and settle with the parks.
  • FIG7 is an exemplary flow chart of another communication method 700 provided in an embodiment of the present application.
  • UE#1 in FIG7 is an example of the first terminal device in FIG5
  • PCF is an example of the policy control network element in FIG5
  • ULCL+PSA1 is an example of the first user plane network element in FIG5
  • SMF is an example of the session management network element in FIG5
  • PSA2 is an example of the second user plane network element in FIG5.
  • PCF sends campus policy to SMF via AMF.
  • SMF receives campus policy from PCF.
  • SMF sends a session management message to ULCL+PSA2.
  • ULCL+PSA1 receives the session management message from SMF.
  • S703a, ULCL+PSA2 sends the usage of the data flow diverted to PSA1 to SMF.
  • the SMF receives the usage of the data flow diverted from ULCL+PSA2 to PSA1.
  • S702b SMF sends a session management message to PSA1.
  • the SMF can instruct PSA1 not to make statistics on the data flow of UE#1 diverted to PSA1.
  • SMF sends a session management message to PSA2.
  • the session management message may carry a charging rule to instruct PSA2 to perform statistics reporting on the data flow diverted to PSA2.
  • PSA2 sends the statistical usage of the data flow of UE#1 to SMF.
  • the statistical usage of the data flow of UE#1 by PSA2 may be the data flow of the campus service.
  • SMF may also obtain the usage of the data flow of UE#1 counted by PSA1.
  • the SMF can actively query PSA1 about the data flow usage of UE#1; or, when the session of UE#1 is deleted, PSA1 can report the data flow usage of UE#1.
  • steps S701 to S704 reference may be made to the descriptions in S601 to S604 , which will not be described in detail.
  • S705 SMF sends a charging request message to CHF based on the usage of the data flow diverted to PSA1 sent by ULCL+PSA2 and the usage of the data flow of UE#1 counted by PSA1.
  • CHF receives the charging request message from SMF.
  • the charging request message may be a charging data request (Charging Data Request) message.
  • the charging request message may include the location information of UE#1 and the usage of the data flow sent by ULCL+PSA2 and diverted to PSA1.
  • location information of UE#1 reference may be made to the description in S510.
  • the charging request message may include the RG associated with ULCL+PSA2 (or the RG associated with the campus) and the usage of the data flow sent by ULCL+PSA2 and diverted to PSA1.
  • CHF generates a call record for UE#1 based on the charging request message, and stores the call record corresponding to the data flow usage of UE#1 counted by ULCL+PSA2 in call record directory #1.
  • the call record directory #1 is used to store the call records corresponding to the free data flow usage.
  • the CHF may configure a free-flow location area information list, and the CHF determines whether the data flow of UE#1 is free-flow according to the location information of UE#1 in the charging request message. If yes, the CHF stores the call record corresponding to the ID of ULCL+PSA2 in the call record directory #1.
  • the CHF may configure a list of RGs for free flows, and the CHF determines whether the data flow of the UE#1 is free flow according to the RG associated with the ULCL+PSA2 in the charging request message. If yes, the CHF stores the bill corresponding to the ID of the ULCL+PSA2 in the bill directory #1.
  • the operator's billing system may not collect the call records in the newly added free-flow directory (call record directory #1) back to the home location.
  • the home location's billing can extract the free-flow call records from the call record directory #1 of the visited CHF, and settle with the campus based on the location information of UE#1 or the RG division.
  • FIG8 is an exemplary flow chart of another communication method 800 provided in an embodiment of the present application.
  • UE#1 in FIG8 is an example of the first terminal device in FIG5
  • PCF is an example of the policy control network element in FIG5
  • ULCL+PSA1 is an example of the first user plane network element in FIG5
  • SMF is an example of the session management network element in FIG5
  • PSA2 is an example of the second user plane network element in FIG5.
  • PCF sends campus policy to SMF via AMF.
  • SMF receives campus policy from PCF.
  • S802a SMF sends a session management message to ULCL+PSA2.
  • ULCL+PSA2 receives the session management message from SMF.
  • the session management message carries a charging rule, which instructs PSA2 to count and report the usage of the data flow of UE#1.
  • ULCL+PSA2 sends the usage of the data flow diverted to PSA2 to SMF.
  • the SMF receives the usage of the data flow diverted from ULCL+PSA2 to PSA2.
  • S802b SMF sends a session management message to PSA1.
  • the session management message carries a charging rule, which instructs PSA1 to count and report the usage of the data flow of UE#1.
  • PSA1 sends the statistical usage of the data flow of UE#1 to SMF.
  • the data flow is the data flow diverted to PSA1.
  • SMF may also obtain the usage of the data flow of UE#1 counted by PSA1.
  • S805 SMF sends a charging request message to CHF.
  • CHF receives the charging request message from SMF.
  • the charging request message may carry the ID of ULCL+PSA2 and the usage of the data flow diverted to PSA1.
  • the charging request message may also carry the usage of the data flow of UE#1 counted by PSA2.
  • the SMF modifies the ID of PSA1 to an ID associated with the ID of ULCL+PSA2, for example, the ID of PSA1 is modified to the ID of PSA1 plus the ID of ULCL+PSA2.
  • CHF generates a call record for UE#1 based on the charging request message, and stores the call record in call record directory #1.
  • the operator's billing system may not collect the call records in the newly added free-flow directory (call record directory #1) back to the home location.
  • the billing of the home location can extract the free-flow call records from the call record directory #1 of the visited CHF, distinguish the parks according to the UPF ID, and settle with the parks.
  • FIG9 is a schematic block diagram of a communication device 1000 provided in an embodiment of the present application.
  • the communication device 1000 may include: a transceiver unit 1010 and a processing unit 1020 .
  • the communication device 1000 may be the session management network element in the above method embodiment, or may be a chip for implementing the functions of the session management network element in the above method embodiment.
  • the communication device 1000 may correspond to the session management network element in the method 500 of the embodiment of the present application, or correspond to the SMF in methods 600 to 800.
  • the communication device 1000 may include a unit for executing the method executed by the session management network element in the method 500 in FIG. 5, or may include a unit for executing the method executed by the SMF in methods 600 to 800.
  • each unit in the communication device 1000 and the above-mentioned other operations and/or functions are respectively for implementing the corresponding processes of the method 500 in FIG. 5, the method 600 in FIG. 6, the method 700 in FIG. 7, or the method 800 in FIG. 8. It should be understood that the specific process of each unit executing the above-mentioned corresponding steps has been described in detail in the above-mentioned method embodiment, and for the sake of brevity, it will not be repeated here.
  • the communication device 1000 may be the billing function network element in the above method embodiment, or may be a chip for implementing the functions of the billing function network element in the above method embodiment.
  • the communication device 1000 may correspond to the billing function network element in the method 500 of the embodiment of the present application, or correspond to the CHF in methods 600 to 800.
  • the communication device 1000 may include a unit for executing the method executed by the billing function network element in the method 500 in Figure 5, or may include a unit for executing the method executed by the CHF in methods 600 to 800.
  • each unit in the communication device 1000 and the above-mentioned other operations and/or functions are respectively for implementing the corresponding processes of method 500 in Figure 5, method 600 in Figure 6, method 700 in Figure 7, or method 800 in Figure 8. It should be understood that the specific process of each unit executing the above-mentioned corresponding steps is described in the above-mentioned method. The embodiments have been described in detail and will not be repeated here for the sake of brevity.
  • the communication device 1000 may be the first user plane functional network element in the above method embodiment, or may be a chip for implementing the function of the first user plane functional network element in the above method embodiment.
  • the communication device 1000 may correspond to the first user plane function network element in the method 500 of the embodiment of the present application, or correspond to the ULCL+PSA2 in the methods 600 to 800.
  • the communication device 1000 may include a unit for executing the method executed by the first user plane function network element in the method 500 in Figure 5, or may include a unit for executing the method executed by the ULCL+PSA2 in the methods 600 to 800.
  • each unit in the communication device 1000 and the above-mentioned other operations and/or functions are respectively for implementing the corresponding processes of the method 500 in Figure 5, the method 600 in Figure 6, the method 700 in Figure 7, or the method 800 in Figure 8. It should be understood that the specific process of each unit performing the above-mentioned corresponding steps has been described in detail in the above-mentioned method embodiment, and for the sake of brevity, it will not be repeated here.
  • transceiver unit 1010 in the communication device 1000 may correspond to the transceiver 2020 in the communication equipment 2000 shown in FIG. 9
  • processing unit 1020 in the communication device 1000 may correspond to the processor 2010 in the communication equipment 2000 shown in FIG. 9 .
  • the chip when the communication device 1000 is a chip, the chip includes a transceiver unit.
  • the chip may also include a processing unit.
  • the transceiver unit may be an input/output circuit or a communication interface; the processing unit may be a processor or a microprocessor or an integrated circuit integrated on the chip.
  • the transceiver unit 1010 is used to implement the signal transceiver operation of the communication device 1000, and the processing unit 1020 is used to implement the signal processing operation of the communication device 1000.
  • the transceiver unit 1010 constitutes an acquisition unit, or the transceiver unit 1010 can be called an acquisition unit.
  • the transceiver unit 1010 and the processing unit 1020 constitute an acquisition unit.
  • the communication device 1000 further includes a storage unit 1030, and the storage unit 1030 is used to store instructions.
  • FIG10 is a schematic block diagram of an apparatus 2000 provided in an embodiment of the present application.
  • the apparatus 2000 includes: at least one processor 2010.
  • the processor 2010 is coupled to the memory and is used to execute instructions stored in the memory to execute the method described in FIG5 , FIG6 , FIG7 or FIG8 .
  • the apparatus 2000 further includes a transceiver 2020, and the processor 2010 is coupled to the memory and is used to execute instructions stored in the memory to control the transceiver 2020 to send signals and/or receive signals.
  • the apparatus 2000 further includes a memory 2030 for storing instructions.
  • processor 2010 and the memory 2030 can be combined into one processing device, and the processor 2010 is used to execute the program code stored in the memory 2030 to implement the above functions.
  • the memory 2030 can also be integrated into the processor 2010, or independent of the processor 2010.
  • the transceiver 2020 may include a receiver (or receiver) and a transmitter (or transmitter).
  • the transceiver 2020 may further include an antenna, and the number of antennas may be one or more.
  • the transceiver 2020 may also be a communication interface or an interface circuit.
  • the chip When the device 2000 is a chip, the chip includes a transceiver unit and a processing unit, wherein the transceiver unit may be an input/output circuit or a communication interface; and the processing unit may be a processor or a microprocessor or an integrated circuit integrated on the chip.
  • FIG11 is a schematic diagram of a chip system according to an embodiment of the present application.
  • the chip system here may also be a system composed of circuits.
  • the chip system 3000 shown in FIG11 includes: a logic circuit 3010 and an input/output interface (input/output interface) 3020, wherein the logic circuit is used to couple with the input interface and transmit data (such as an IP address) through the input/output interface to execute the method described in FIG5, FIG6, FIG7 or FIG8.
  • the present application also provides a processing device, including a processor and an interface.
  • the processor can be used to execute the method in the above method embodiment.
  • the above-mentioned processing device can be a chip.
  • the processing device can be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a system on chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a microcontroller unit (MCU), a programmable logic device (PLD) or other integrated chips.
  • FPGA field programmable gate array
  • ASIC application specific integrated circuit
  • SoC system on chip
  • CPU central processor unit
  • NP network processor
  • DSP digital signal processor
  • MCU microcontroller unit
  • PLD programmable logic device
  • each step of the above method can be completed by an integrated logic circuit of hardware in a processor or an instruction in the form of software.
  • the steps of the method disclosed in conjunction with the embodiment of the present application can be directly embodied as a hardware processor for execution, or a combination of hardware and software modules in a processor for execution.
  • the software module can be located in a storage medium mature in the art such as a random access register, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc.
  • the storage medium is located in a memory, and the processor reads the information in the memory and completes the steps of the above method in conjunction with its hardware. To avoid repetition, it is not described in detail here.
  • the processor in the embodiment of the present application can be an integrated circuit chip with signal processing capabilities.
  • each step of the above method embodiment can be completed by an integrated logic circuit of hardware in the processor or an instruction in the form of software.
  • the above processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • DSP digital signal processor
  • ASIC application-specific integrated circuit
  • FPGA field programmable gate array
  • the disclosed methods, steps and logic block diagrams in the embodiments of the present application can be implemented or executed.
  • the general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc.
  • the memory in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories.
  • the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory.
  • the volatile memory can be a random access memory (RAM), which is used as an external cache.
  • the present application also provides a computer program product, which includes: a computer program code, when the computer program code is run on a computer, the computer executes the method of any one of the embodiments shown in Figures 5 to 8.
  • the present application also provides a computer-readable medium, which stores a program code.
  • the program code runs on a computer, the computer executes the method of any one of the embodiments shown in Figures 5 to 8.
  • the present application also provides a system, which includes the aforementioned session management network element and charging function network element.
  • the system also includes the aforementioned first user plane function network element and second user plane function network element.
  • the computer program product includes one or more computer instructions.
  • the computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable information medium to another computer-readable storage medium.
  • the computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media integrated.
  • the available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a high-density digital video disc (digital video disc, DVD)), or a semiconductor medium (e.g., a solid-state drive (solid state disc, SSD)), etc.
  • a magnetic medium e.g., a floppy disk, a hard disk, a tape
  • an optical medium e.g., a high-density digital video disc (digital video disc, DVD)
  • a semiconductor medium e.g., a solid-state drive (solid state disc, SSD)
  • the disclosed systems, devices and methods can be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed.
  • Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

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)

Abstract

本申请提供了一种通信方法和通信装置，该方法包括：会话管理网元获取第一终端设备的第一信息，该第一信息包括由第一用户面功能网元分流到第二用户面功能网元的该第一终端设备的第一数据流的使用量，该第一用户面功能网元用于对第一区域内终端设备的数据流进行分流，该第一区域为该第一终端设备签约的专用网络的签约地，该第二用户面网元用于传输该第一终端设备和数据网络之间的用户面数据；该会话管理网元向计费功能网元发送第一计费请求消息，该第一计费请求消息包括第一标识信息和该第一信息，该第一标识信息用于关联该第一区域。通过向计费管理网元发送第一区域关联的标识信息以及该第一数据流的使用量，能够实现该第一数据流的免流计费。

Description

通信方法与通信装置
本申请要求于2022年11月04日提交中国专利局、申请号为202211380617.1、发明名称为“通信方法与通信装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及无线通信领域，并且更具体地，涉及一种通信方法与通信装置。
背景技术
在实际商用场景下，用户访问园区(例如商场、医院、文旅)有流量免费/统付的诉求，即终端用户在园区内访问园区业务产生的流量由运营商跟园区结算，运营商不向终端用户收取费用。用户出园区访问数据网路产生的流量正常收费。
在现有的计费方法中，可以将不同园区的业务流量与不同的费率组(rating group，RG)关联，根据不同RG区分不同园区的免流流量和正常收费的流量。由于RG由运营商统一规划，且该实现方式涉及到的地区以及地区的园区的数量非常多，可行性较低。因此，如何实现园区内免流流量的计费成为亟待解决的问题。
发明内容
本申请提供一种通信方法与通信装置，能够实现园区内免流流量计费。
第一方面，提供了一种通信方法，该方法可以由会话管理网元执行，或者，也可以由会话管理网元的组成部件(例如芯片或者电路)执行，本申请对此不作限定。为了便于描述，下面以由执行为例进行说明。
该方法可以包括：会话管理网元获取第一终端设备的第一信息，该第一信息包括第一数据流的使用量，该第一数据流包括由第一用户面功能网元分流到第二用户面功能网元的该第一终端设备的数据流，该第一用户面功能网元用于对第一区域内终端设备的数据流进行分流，该第一区域为该第一终端设备签约的专用网络的签约地，该第二用户面功能网元用于传输该第一终端设备和数据网络之间的用户面数据；该会话管理网元向计费功能网元发送第一计费请求消息，该第一计费请求消息包括第一标识信息和该第一信息，该第一标识信息用于关联该第一区域。
基于上述方案，会话管理网元可以获取终端设备的第一数据流的使用量，该第一数据流包括由第一用户面功能网元分流到第二用户面功能网元的该第一终端设备的数据流，并向计费功能网元发送第一标识信息和该第一信息，以使该计费功能网元生成该第一数据流的使用量的话单，从而实现对该第一数据流的计费。
结合第一方面，在第一方面的某些实现方式中，该会话管理网元向该第一用户面功能网元发送第一指示信息，该第一指示信息指示统计并上报该第一数据流的使用量；该会话管理网元接收来自该第一用户面功能网元的该第一数据流的使用量。
结合第一方面，在第一方面的某些实现方式中，该会话管理网元向该第二用户面功能网元发送第二指示信息，该第二指示信息指示不统计该第一数据流的使用量。
结合第一方面，在第一方面的某些实现方式中，在该会话管理网元向计费功能网元发送第一计费请求消息之前，该会话管理网元接收来自该第二用户面功能网元的第二信息，该第二信息包括该第二用户面功能网元统计的该第一终端设备的数据流的使用量。
结合第一方面，在第一方面的某些实现方式中，该会话管理网元基于该第二信息向该计费功能网元发送该第一计费请求消息，该第一计费请求消息还包括该第二用户面功能网元的标识信息和该第二信息。
结合第一方面，在第一方面的某些实现方式中，该会话管理网元基于该第一信息和该第二信息确定该第一计费请求消息和第二计费请求消息，该第二计费请求消息包括该第二用户面功能网元的标识信息和该第二信息；该会话管理网元向该计费功能网元发送该第二计费请求消息。
结合第一方面，在第一方面的某些实现方式中，该第一标识信息包括以下信息中的至少一项：该第一用户面功能网元的标识，该第一终端设备的位置信息，该第一区域关联的费率组RG。
结合第一方面，在第一方面的某些实现方式中，在该会话管理网元获取第一终端设备的第一信息之前，该方法还包括：该会话管理网元接收来自策略控制功能网元的计费规则，该计费规则指示该第一终端设备的数据流类型为免费的数据流。
结合第一方面，在第一方面的某些实现方式中，在该会话管理网元获取第二数据流的使用量，该第二数据流为由该第一用户面功能网元分流到第三用户面功能网元的该第一终端设备的数据流，该第三用户面功能网元用于传输该第一终端设备与该专用网络之间的用户面数据；该会话管理网元向计费管理功能发送第三计费请求消息，该第三计费请求消息包括该第三用户面功能网元的标识信息以及该第二数据流的使用量。
结合第一方面，在第一方面的某些实现方式中，该第一计费请求消息还包括该第三用户面功能网元的标识信息以及该第二数据流的使用量。
第二方面，提供一种通信方法，该方法包括：会话管理网元接收来自第二用户面功能网元的第一信息，该第一信息包括第一数据流的使用量，该第一数据流包括由第一用户面功能网元分流到第二用户面功能网元的该第一终端设备的数据流，该第一用户面功能网元用于对第一区域内终端设备的数据流进行分流，该第一区域为该第一终端设备签约的专用网络的签约地，该第二用户面功能网元用于传输该第一终端设备和数据网络之间的用户面数据；该会话管理网元向计费功能网元发送第一计费请求消息，该第一计费请求消息包括第二标识信息和该第一信息，该第二标识信息与该第一用户面功能网元的标识信息相关联。
基于上述方案，会话管理网元可以接收来自第二用户面功能网元该终端设备的第一数据流的使用量，该第一数据流包括由第一用户面功能网元分流到第二用户面功能网元的该第一终端设备的数据流，并向计费功能网元发送第一标识信息和该第一信息，以使该计费功能网元生成该第一数据流的使用量的话单，从而实现对该第一数据流的计费。
结合第二方面，在第二方面的某些实现方式中，在该会话管理网元接收来自第二用户面功能网元的第一信息之前，该会话管理网元向该第二用户面功能网元发送第三指示信息，该第三指示信息指示统计并上报该第一数据流的使用量。
结合第二方面，在第二方面的某些实现方式中，该第一信息关联该第二用户面功能网元的标识信息，在该会话管理网元向计费功能网元发送第一计费请求消息之前，该会话管理网元将该第二用户面功能网元的标识信息修改为第二标识信息，该第二标识信息与该第一用户面功能网元的标识信息相关联。
结合第二方面，在第二方面的某些实现方式中，在该会话管理网元向计费功能网元发送第一计费请求消息之前，该会话管理网元接收来自该第二用户面功能网元的第二信息，该第二信息包括该第二用户面功能网元统计的该第一终端设备的数据流的使用量。
结合第二方面，在第二方面的某些实现方式中，该会话管理网元基于该第二信息向该计费功能网元发送该第一计费请求消息，该第一计费请求消息还包括该第二用户面功能网元的标识信息和该第二信息。
结合第二方面，在第二方面的某些实现方式中，该会话管理网元基于该第一信息和该第二信息确定该第一计费请求消息和第二计费请求消息，该第二计费请求消息包括该第二用户面功能网元的标识信息和该第二信息；该会话管理网元向该计费功能网元发送该第二计费请求消息。
结合第二方面，在第二方面的某些实现方式中，在该会话管理网元获取第一终端设备的第一信息之前，该会话管理网元接收来自策略控制功能网元的计费规则，该计费规则指示该第一终端设备的数据流类型为免费的数据流。
第三方面，提供一种通信方法，该方法包括：计费功能网元接收来自会话管理网元的第一计费请求消息，该第一计费请求消息包括第一标识信息和第一信息，该第一信息包括第一终端设备的第一数据流的使用量，该第一数据流包括由第一用户面功能网元分流到第二用户面功能网元的该第一终端设备的数据流；该计费功能网元基于该第一标识信息和该第一信息生成该第一终端设备的第一话单；其中，该第一用户面功能网元用于对第一区域内终端设备的数据流进行分流，该第一区域为该第一终端设备签约的专用网络的签约地，该第二用户面功能网元用于传输该第一终端设备和数据网络之间的数据，该第一标识信息用于关联该第一区域。
结合第三方面，在第三方面的某些实现方式中，该第一计费请求消息还包括该第二用户面功能网元 的标识信息和第二信息，该第二信息包括该第二用户面功能网元统计的该第一终端设备的数据流的使用量。
结合第三方面，在第三方面的某些实现方式中，在该计费功能网元基于该第一标识信息和该第一信息生成该第一终端设备的第一话单之前，该计费功能网元从该第一计费请求消息中拆分出该第一标识信息和该第一信息。
结合第三方面，在第三方面的某些实现方式中，该第一计费请求消息还包括第四指示信息，该第四指示信息指示该第一数据流为免费的数据流，该计费功能网元基于该第四指示信息，将该第一终端设备的第一话单存储在第一话单目录，该第一话单目录为存储免费的数据流的话单目录。
结合第三方面，在第三方面的某些实现方式中，该计费功能网元配置有第一配置信息，该第一配置信息用于配置免费的数据流的话单处理，该第一配置信息包括以下至少一种类型的标识信息：用户面功能网元的标识信息，位置区域信息，费率组RG信息；其中，该用户面功能网元的标识信息包括至少一个用户面功能网元的标识，该至少一个用户面功能网元的标识包括该第一用户面网元的标识，该位置区域信息包括至少一个区域的位置信息，该至少一个区域的位置信息包括该第一终端设备的位置信息，该费率组信息包括至少一个费率组的信息，该至少一个费率组RG的包括该第一区域关联的费率组RG。
结合第三方面，在第三方面的某些实现方式中，该计费功能网元基于该第一配置信息，将该第一终端设备的第一话单存储在第一话单目录，该第一话单目录为存储免费的数据流的话单目录。
结合第三方面，在第三方面的某些实现方式中，该第一标识信息包括以下信息中的至少一项：该第一用户面功能网元的标识，该第一终端设备的位置信息，该第一区域关联的费率组RG。
结合第三方面，在第三方面的某些实现方式中，该计费功能网元接收来自会话管理网元的第三计费请求消息，该第三计费请求消息包括该第三用户面功能网元的标识信息以及该第二数据流的使用量，该第二数据流为由该第一用户面功能网元分流到第三用户面功能网元的该第一终端设备的数据流，该第三用户面功能网元用于传输该第一终端设备与该专用网络之间的用户面数据；该第三计费功能网元基于该第三计费请求消息生成该终端设备的第三话单，并将该第三话单存储于该第一话单目录。
结合第一方面，在第一方面的某些实现方式中，该第一计费请求消息还包括该第三用户面功能网元的标识信息以及该第二数据流的使用量，该计费功能网元从该第一计费请求消息中拆分出该第三用户面功能网元的标识信息以及该第二数据流的使用量，该第三用户面功能网元用于传输该第一终端设备与该专用网络之间的用户面数据；该第三计费功能网元基于该第三计费请求消息生成该终端设备的第三话单，并将该第三话单存储于该第一话单目录。
第四方面，提供一种通信装置，该装置包括收发单元，该收发单元用于获取第一终端设备的第一信息，该第一信息包括第一数据流的使用量，该第一数据流包括由第一用户面功能网元分流到第二用户面功能网元的该第一终端设备的数据流，该第一用户面功能网元用于对第一区域内终端设备的数据流进行分流，该第一区域为该第一终端设备签约的专用网络的签约地，该第二用户面功能网元用于传输该第一终端设备和数据网络之间的用户面数据；该收发单元还用于向计费功能网元发送第一计费请求消息，该第一计费请求消息包括第一标识信息和该第一信息，该第一标识信息用于关联该第一区域。
结合第四方面，在第四方面的某些实现方式中，该收发单元具体用于向该第一用户面功能网元发送第一指示信息，该第一指示信息指示统计并上报该第一数据流的使用量；该接收来自该第一用户面功能网元的该第一数据流的使用量。
结合第四方面，在第四方面的某些实现方式中，该收发单元还用于向该第二用户面功能网元发送第二指示信息，该第二指示信息指示不统计该第一数据流的使用量。
结合第四方面，在第四方面的某些实现方式中，该收发单元还用于接收来自该第二用户面功能网元的第二信息，该第二信息包括该第二用户面功能网元统计的该第一终端设备的数据流的使用量。
结合第四方面，在第四方面的某些实现方式中，该收发单元具体用于基于该第二信息向该计费功能网元发送该第一计费请求消息，该第一计费请求消息还包括该第二用户面功能网元的标识信息和该第二信息。
结合第四方面，在第四方面的某些实现方式中，该装置还包括处理单元，该处理单元用于基于该第一信息和该第二信息确定该第一计费请求消息和第二计费请求消息，该第二计费请求消息包括该第二用户面功能网元的标识信息和该第二信息；该收发单元还用于向该计费功能网元发送该第二计费请求消息。
结合第四方面，在第四方面的某些实现方式中，该第一标识信息包括以下信息中的至少一项：该第 一用户面功能网元的标识，该第一终端设备的位置信息，该第一区域关联的费率组RG。
结合第四方面，在第四方面的某些实现方式中，该收发单元还用于接收来自策略控制功能网元的计费规则，该计费规则指示该第一终端设备的数据流类型为免费的数据流。
第五方面，提供一种通信装置，该装置包括收发单元，该收发单元用于接收来自第二用户面功能网元的第一信息，该第一信息包括第一数据流的使用量，该第一数据流包括由第一用户面功能网元分流到第二用户面功能网元的该第一终端设备的数据流，该第一用户面功能网元用于对第一区域内终端设备的数据流进行分流，该第一区域为该第一终端设备签约的专用网络的签约地，该第二用户面功能网元用于传输该第一终端设备和数据网络之间的用户面数据；该收发单元还用于向计费功能网元发送第一计费请求消息，该第一计费请求消息包括第二标识信息和该第一信息，该第二标识信息与该第一用户面功能网元的标识信息相关联。
结合第五方面，在第五方面的某些实现方式中，该收发单元还用于向该第二用户面功能网元发送第三指示信息，该第三指示信息指示统计并上报该第一数据流的使用量。
结合第五方面，在第五方面的某些实现方式中，该第一信息关联该第二用户面功能网元的标识信息，该处理单元还用于将该第二用户面功能网元的标识信息修改为第二标识信息，该第二标识信息与该第一用户面功能网元的标识信息相关联。
结合第五方面，在第五方面的某些实现方式中，该收发单元还用于接收来自该第二用户面功能网元的第二信息，该第二信息包括该第二用户面功能网元统计的该第一终端设备的数据流的使用量。
结合第五方面，在第五方面的某些实现方式中，该收发单元具体用于基于该第二信息向该计费功能网元发送该第一计费请求消息，该第一计费请求消息还包括该第二用户面功能网元的标识信息和该第二信息。
结合第五方面，在第五方面的某些实现方式中，该处理单元还用于基于该第一信息和该第二信息确定该第一计费请求消息和第二计费请求消息，该第二计费请求消息包括该第二用户面功能网元的标识信息和该第二信息；该收发单元还用于向该计费功能网元发送该第二计费请求消息。
结合第五方面，在第五方面的某些实现方式中，该收发单元还用于接收来自策略控制功能网元的计费规则，该计费规则指示该第一终端设备的数据流类型为免费的数据流。
第六方面，提供一种通信装置，该装置包括收发单元和处理单元，该收发单元用于接收来自会话管理网元的第一计费请求消息，该第一计费请求消息包括第一标识信息和第一信息，该第一信息包括第一终端设备的第一数据流的使用量，该第一数据流包括由第一用户面功能网元分流到第二用户面功能网元的该第一终端设备的数据流；该处理单元用于基于该第一标识信息和该第一信息生成该第一终端设备的第一话单；其中，该第一用户面功能网元用于对第一区域内终端设备的数据流进行分流，该第一区域为该第一终端设备签约的专用网络的签约地，该第二用户面功能网元用于传输该第一终端设备和数据网络之间的数据，该第一标识信息用于关联该第一区域。
结合第六方面，在第六方面的某些实现方式中，该第一计费请求消息还包括该第二用户面功能网元的标识信息和第二信息，该第二信息包括该第二用户面功能网元统计的该第一终端设备的数据流的使用量。
结合第六方面，在第六方面的某些实现方式中，该处理单元还用于从该第一计费请求消息中拆分出该第一标识信息和该第一信息。
结合第六方面，在第六方面的某些实现方式中，该第一计费请求消息还包括第四指示信息，该第四指示信息指示该第一数据流为免费的数据流，该计费功能网元基于该第四指示信息，将该第一终端设备的第一话单存储在第一话单目录，该第一话单目录为存储免费的数据流的话单目录。
结合第六方面，在第六方面的某些实现方式中，该装置配置有第一配置信息，该第一配置信息用于配置免费的数据流的话单处理，该第一配置信息包括以下至少一种类型的标识信息：用户面功能网元的标识信息，位置区域信息，费率组RG信息；其中，该用户面功能网元的标识信息包括至少一个用户面功能网元的标识，该至少一个用户面功能网元的标识包括该第一用户面网元的标识，该位置区域信息包括至少一个区域的位置信息，该至少一个区域的位置信息包括该第一终端设备的位置信息，该费率组信息包括至少一个费率组的信息，该至少一个费率组RG的包括该第一区域关联的费率组RG。
结合第六方面，在第六方面的某些实现方式中，该装置还包括存储单元，该处理单元还用于基于该第一配置信息，将该第一终端设备的第一话单存储在第一话单目录，该第一话单目录为存储免费的数据 流的话单目录。
结合第六方面，在第六方面的某些实现方式中，该第一标识信息包括以下信息中的至少一项：该第一用户面功能网元的标识，该第一终端设备的位置信息，该第一区域关联的费率组RG。
第七方面，提供一种通信装置，该装置包括：至少一个处理器，用于执行存储器存储的计算机程序或指令，以执行上述第一方面至第三方面任一种可能实现方式中的方法。可选地，该装置还包括存储器，用于存储的计算机程序或指令。可选地，该装置还包括通信接口，处理器通过通信接口读取存储器存储的计算机程序或指令。
在一种实现方式中，该装置为会话管理网元或计费功能网元。
在另一种实现方式中，该装置为用于会话管理网元或计费功能网元的芯片、芯片系统或电路。
第八方面，本申请提供一种处理器，用于执行上述第一方面至第三方面提供的方法。
对于处理器所涉及的发送和获取/接收等操作，如果没有特殊说明，或者，如果未与其在相关描述中的实际作用或者内在逻辑相抵触，则可以理解为处理器输出和接收、输入等操作，也可以理解为由射频电路和天线所进行的发送和接收操作，本申请对此不做限定。
第九方面，提供一种计算机可读存储介质，该计算机可读介质存储用于设备执行的程序代码，该程序代码包括用于执行上述第一方面至第三方面任一种可能实现方式中的方法。
第十方面，提供一种包含指令的计算机程序产品，当该计算机程序产品在计算机上运行时，使得计算机执行上述第一方面至第三方面任一种可能实现方式中的方法。
附图说明
图1是适用于本申请实施例提供的方法的通信系统的示意图。
图2是本申请适用的省间漫游架构的示意图。
图3是本申请适用的上行分流本地分流架构图。
图4是本申请适用的应用场景示意图。
图5是本申请实施例提供的通信方法500的示意性流程图。
图6是本申请实施例提供的通信方法600的示意性流程图。
图7是本申请实施例提供的通信方法700的示意性流程图。
图8是本申请实施例提供的通信方法800的示意性流程图。
图9是本申请实施例提供的通信装置的示意图。
图10是本申请另一实施例提供的通信装置的示意性框图。
图11是本申请实施例提供的一种芯片系统的示意图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
本申请实施例的技术方案可以应用于各种通信系统，例如：长期演进(long term evolution，LTE)系统、频分双工(frequency division duplex，FDD)系统、时分双工(time division duplex，TDD)系统、全球互联微波接入(worldwide interoperability for microwave access，WiMAX)通信系统、第五代(5th generation，5G)系统或新无线(new radio，NR)、第六代(6th generation，6G)系统或未来的通信系统等。本申请中所述的5G移动通信系统包括非独立组网(non-standalone，NSA)的5G移动通信系统或独立组网(standalone，SA)的5G移动通信系统。通信系统还可以是公共陆地移动网络(public land mobile network，PLMN)、设备到设备(device to device，D2D)通信系统、机器到机器(machine to machine，M2M)通信系统、物联网(Internet of things，IoT)通信系统、车联万物(vehicle to everything，V2X)通信系统、无人机(uncrewed aerial vehicle，UAV)通信系统或者其他通信系统。
图1示出了一种适用于本申请实施例提供的方法的通信系统100的示意图。如图1所示，通信系统100可以包括但不限于以下部分：
1、用户设备(user equipment，UE)：可以包括各种具有无线通信功能的手持设备、车载设备、可穿戴设备、计算设备或连接到无线调制解调器的其它处理设备，以及各种形式的终端、移动台(mobile station，MS)、终端(terminal)或软终端等等。例如，水表、电表、传感器等。
示例性地，本申请实施例中的用户设备可以指接入终端、用户单元、用户站、移动站、移动台、中 继站、远方站、远程终端、移动设备、用户终端(user terminal)、终端(terminal equipment)、无线通信设备、用户代理或用户装置。用户设备还可以是蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，5G网络中的用户设备或者未来演进的公用陆地移动通信网络(public land mobile network，PLMN)中的用户设备或者未来车联网中的用户设备等，本申请实施例对此并不限定。
作为示例而非限定，在本申请实施例中，可穿戴设备也可以称为穿戴式智能设备，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称，如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上，或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备，更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能，例如：智能手表或智能眼镜等，以及只专注于某一类应用功能，需要和其它设备如智能手机配合使用，如各类进行体征监测的智能手环、智能首饰等。
此外，在本申请实施例中，用户设备还可以是物联网(internet of Things，IoT)系统中的用户设备，IoT是未来信息技术发展的重要组成部分，其主要技术特点是将物品通过通信技术与网络连接，从而实现人机互连，物物互连的智能化网络。在本申请实施例中，IOT技术可以通过例如窄带(narrow band，NB)技术，做到海量连接，深度覆盖，终端省电。此外，在本申请实施例中，用户设备还可以包括智能打印机、火车探测器、加油站等传感器，主要功能包括收集数据(部分用户设备)、接收接入网设备的控制信息与下行数据，并发送电磁波，向接入网设备传输上行数据。
2、(无线)接入网设备(radio access network，(R)AN)：用于为特定区域的授权用户设备提供入网功能，并能够根据用户设备的级别，业务的需求等使用不同质量的传输隧道。
(R)AN能够管理无线资源，为用户设备提供接入服务，进而完成控制信号和用户设备数据在用户设备和核心网之间的转发，(R)AN也可以理解为传统网络中的基站。
示例性地，本申请实施例中的接入网设备可以是用于与用户设备通信的任意一种具有无线收发功能的通信设备。该接入网设备包括但不限于：演进型节点B(evolved Node B，eNB)、无线网络控制器(radio network controller，RNC)、节点B(Node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(home evolved NodeB，HeNB，或home Node B，HNB)、基带单元(baseBand unit，BBU)，无线保真(wireless fidelity，WIFI)系统中的接入点(access point，AP)、无线中继节点、无线回传节点、传输点(transmission point，TP)或者发送接收点(transmission and reception point，TRP)等，还可以为5G，如，NR，系统中的gNB，或，传输点(TRP或TP)，5G系统中的基站的一个或一组(包括多个天线面板)天线面板，或者，还可以为构成gNB或传输点的网络节点，如基带单元(BBU)，或，分布式单元(distributed unit，DU)等。
在一些部署中，gNB可以包括集中式单元(centralized unit，CU)和DU。gNB还可以包括有源天线单元(active antenna unit，AAU)。CU实现gNB的部分功能，DU实现gNB的部分功能。例如，CU负责处理非实时协议和服务，实现无线资源控制(radio resource control，RRC)，分组数据汇聚层协议(packet data convergence protocol，PDCP)层的功能。DU负责处理物理层协议和实时服务，实现无线链路控制(radio link control，RLC)层、媒体接入控制(media access control，MAC)层和物理(physical，PHY)层的功能。AAU实现部分物理层处理功能、射频处理及有源天线的相关功能。由于RRC层的信息最终会变成PHY层的信息，或者，由PHY层的信息转变而来，因而，在这种架构下，高层信令，如RRC层信令，也可以认为是由DU发送的，或者，由DU+AAU发送的。可以理解的是，接入网设备可以为包括CU节点、DU节点、AAU节点中一项或多项的设备。此外，可以将CU划分为接入网(radio access network，RAN)中的接入网设备，也可以将CU划分为核心网(core network，CN)中的接入网设备，本申请对此不做限定。
3、接入与移动性管理功能(access and mobility management function，AMF)网元
接入与移动性管理功能网元可以用于移动性管理和接入管理等，可以用于实现移动性管理实体(mobility management entity，MME)功能中除会话管理之外的其它功能，例如，合法探测、或接入授权等功能，此外还用于在终端设备与策略控制功能(policy control function，PCF)网元之间传输用户策略。在本申请实施例中，接入与移动性管理功能网元可用于实现接入与移动性管理网元的功能。
4、会话管理功能(session management function，SMF)网元
会话管理功能网元可以用于会话管理、终端设备的网络互连协议(internet protocol，IP)地址分配和管理、选择和管理用户面功能(user plane function，UPF)网元、策略控制和收费功能接口的终结点以及下行数据通知等。在本申请实施例中，会话管理功能网元可用于实现会话管理网元的功能。
5、用户面功能网元
用户面功能网元可用于分组路由和转发、或用户面数据的服务质量(quality of service，QoS)参数处理等。用户数据可通过该网元接入到数据网络(data network，DN)。
在本申请实施例中，用户面功能网元可用于实现用户面网元的功能，例如，在不同的用户面功能网元上建立会话时，终端设备的业务体验也会不同，因此需要会话管理功能网元为终端设备的会话选择一个合适用户面功能网元。
6、策略控制网元
策略控制网元用于指导网络行为的统一策略框架，为控制平面功能网元(例如接入与移动性管理功能网元，会话管理功能网元等)提供策略规则信息等。主要负责针对会话、业务流级别进行计费、QoS带宽保障及移动性管理、终端设备策略决策等策略控制功能。策略控制网元既可以具备接入与移动性管理策略控制网元(policy control function for access and mobility control，AM PCF)的能力，又可以具备会话管理策略控制网元(PCF for session management，SM PCF)的能力。在逻辑上，接入与移动性管理策略控制网元和会话管理策略控制网元可以理解为分别具备不同能力的不同的网元。在实际部署场景中，接入与移动性管理策略控制网元和会话管理策略控制网元可以是同一个策略控制网元实体，即单独部署，也可以是两个不同的策略控制网元实体，即合一部署。
例如，接入与移动性管理策略控制网元可以与接入与移动性管理功能网元直接相连，接入与移动性管理策略控制网元可以向接入与移动性管理功能网元提供移动性、终端设备的接入选择相关策略。其中，移动性策略可以包括例如服务区限制管理、无线电接入技术频率选择优先级(radio access technology frequency selection priority，RFSP)索引(index)管理和会话管理功能网元选择管理；终端设备的接入选择相关策略可以包括接入网发现和选择策略(access network discovery and selection policy，ANDSP)和终端设备的路由选择策略(route selection policy，URSP)。
再如，会话管理策略控制网元可以与会话管理功能网元直接相连，向会话管理功能网元提供协议数据单元(protocol data unit，PDU)会话相关策略。PDU会话相关策略例如包括门控策略、计费策略、QoS控制策略、用量监控控制策略等。
应理解，对于漫游场景，拜访地的策略控制网元在逻辑上可以包括拜访地的接入与移动性管理策略控制网元和拜访地的会话管理策略控制网元；归属地的策略控制网络在逻辑上可以包括归属地的接入与移动性管理策略控制网元和归属地的会话管理策略控制网元。在实际部署中，拜访地的接入与移动性管理策略控制网元和拜访地的会话管理策略控制网元可以是同一个拜访地的策略控制网元实体，也可以是两个不同的拜访地的策略控制网元实体。类似地，归属地的接入与移动性管理策略控制网元和归属地的会话管理策略控制网元可以是同一个归属地的策略控制网元实体，也可以是两个不同的归属地的策略控制网元实体。
7、网络能力开放功能(network exposure function，NEF)网元或应用功能(application function，AF)
网络能力开放功能网元用于向外部开放由3GPP网络功能提供的业务和网络能力信息(如终端位置)等。
应用功能主要用于发送应用侧对网络侧的需求，例如，QoS需求或用户状态事件订阅等。AF可以是第三方功能实体，也可以是运营商部署的应用服务，如IP多媒体子系统(IP multimedia subsystem，IMS)语音呼叫业务。
8、统一数据管理(unified data management，UDM)网元
统一数据管理网元可以用于统一数据管理，支持3GPP认证和密钥协商机制中的认证信任状态处理，用户身份处理，接入授权，注册和移动性管理，签约管理，短消息管理等。
9、统一数据存储(unified data repository，UDR)网元
统一数据存储网元可以用于签约数据、策略数据、应用数据等类型数据的存取功能。
10、数据网络(data network，DN)
数据网络是指终端设备接入的某个特定的数据服务网络，例如，典型的数据网络包括因特网 (internet)、IMS。
需要说明的是，上述网元也可以称为实体、设备、装置或模块等，本申请并未特别限定。在本申请中，为了便于理解和说明，上述部分可以用简称进行表示，例如，将会话管理功能网元简称为SMF，该“SMF”应理解为会话管理功能网元，或者理解为具有与会话管理功能网元功能类似的网元或者装置。其他同理，不再赘述。
图1所涉及的网络架构中还可能包括其他网元，如统一数据存储库(unified data repository，UDR)或计费功能网元(charging function，CHF)等网元或设备等，不作具体限定。
此外，在上述架构中，各接口功能描述如下：
N7：PCF与SMF之间的接口，用于下发PDU会话粒度以及业务数据流粒度控制策略。
N15：PCF与AMF之间的接口，用于下发UE策略及接入控制相关策略。
N5：AF与PCF之间的接口，用于应用业务请求下发以及网络事件上报。
N4：SMF与UPF之间的接口，用于控制面与用户面之间传输信息，包括控制面向用户面的转发规则、QoS控制规则、流量统计规则等的下发以及用户面的信息上报。
N11：SMF与AMF之间的接口，用于传输RAN和UPF之间的PDU会话隧道信息、发送给UE的控制消息、发送给RAN的无线资源控制信息等。
N2：AMF与RAN之间的接口，用于传输核心网侧至RAN的无线承载控制信息等。
N1：AMF与UE之间的接口，接入无关，用于向UE传输QoS控制规则等。
N36：PCF与UDR间的接口，用于PCF从UDR中获取策略相关签约数据以及应用数据相关信息。
此外，NEF还与AMF、SMF均有直接接口，分别对应N29接口和N51接口(为简化图示，上图中并未展示)，用于开放运营商网络能力至第三方应用功能实体，前者可用于NEF直接向AMF订阅相应网络事件、更新用户配置信息，后者可用于更新SMF/UPF上的应用配置数据，如应用标识(application identity)所对应的分组流描述信息(packet flow description，PFD)。
应理解，上述应用于本申请实施例的网络架构仅是举例说明的从传统点到点的架构和服务化架构的角度描述的网络架构，适用本申请实施例的网络架构并不局限于此，任何能够实现上述各个网元的功能的网络架构都适用于本申请实施例。
应理解，图1中的各个网元之间的接口名称只是一个示例，具体实现中接口的名称可能为其他的名称，本申请对此不作具体限定。此外，上述各个网元之间的所传输的消息(或信令)的名称也仅仅是一个示例，对消息本身的功能不构成任何限定。
可以理解的是，上述网元或者功能既可以是硬件设备中的网络元件，也可以是在专用硬件上运行的软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能。可选地，上述网元或者功能可以由一个设备实现，也可以由多个设备共同实现，还可以是一个设备内的一个功能模块，本申请实施例对此不作具体限定。
还应理解，在图1所示的通信系统中，各组成网元的功能仅为示例性的，各个组成网元在应用于本申请的实施例中时，并非全部功能都是必需的。
此外，如图1中包括的各个网元(例如PCF、AMF等)的命名仅是一个名字，名字对网元本身的功能不构成限定。在5G网络以及未来其它的网络中，上述各个网元也可以是其他的名字，本申请对此不作具体限定。例如，在6G网络中，上述各个网元中的部分或全部可以沿用5G中的术语，也可能是其他命名。
还需说明的是，图1中控制面功能的各个网元之间的通信是以非服务化接口为例进行描述，但是并不对本申请实施例的保护范围构成限定的。本领域技术人员可以理解，图1中控制面功能的各个网元也可以通过服务化接口进行通信，例如，AMF对外提供的服务化接口可以为Namf；SMF提供的服务化接口可以为Nsmf；CHF提供的服务化接口可以为Nchf；PCF对外提供的服务化接口可以为Npcf等等。
上述图1中的网元是基于参考点的架构，并不对本申请实施例构成限定。
图2示出了一种本申请适用的省间漫游架构的示意图。在该漫游架构中，UE为漫游用户，其签约信息在归属地网络，目前通过拜访地的RAN和UPF接入拜访地的DN。AMF和SMF均位于拜访地(即拜访省)，归属地(即归属省)的PCF(home-PCF，H-PCF)通过N7接口向拜访地的SMF下发相应策略规则，并根据该策略规则可以为UE提供服务。拜访地的AMF则可经由拜访地PCF(visited-PCF，V-PCF)获取相应的接入与移动性管理策略，并根据接入与移动性管理策略为UE提供服务。
需要说明的是，在实际部署中，这里的H-PCF可以是单独部署的归属地的SM-PCF，也可以是合一部署的归属地的SM-PCF和AM-PCF；这里的V-PCF可以是单独部署的拜访地的AM-PCF，也可以是合一部署的拜访地的SM-PCF和AM-PCF。
图3示出了一种本申请适用的UL CL本地分流架构图。图3所示的架构位于拜访地，UE可以为漫游用户或归属地用户。为降低业务接入时延，运营商可能在RAN附近部署UPF节点，即UPF/UL CL、PDU会话锚点(PDU session anchor，PSA)1-UPF、PSA2-UPF，以使得用户可以就近接入应用服务。
如图3所示，拜访地网络采用UL CL方式，将区域相关业务流直接经由ULCL/UPF分别路由至不同的数据网络，例如园区内部服务网和互联网。示例性地，与PSA2-UPF通过N6接口连接的DN可以为园区内部服务网；通过N6接口与PSA1-UPF连接的DN为互联网。PSA1-UPF可以理解为主锚点UPF，PSA2-UPF可以理解为辅锚点UPF。进一步地，与PSA2-UPF通过N6接口连接的DN也可以连接到互联网，即用户也可以通过园区内部服务网访问互联网的业务。
在实际部署中，图3中的UPF/UL CL、PSA1-UPF、PSA2-UPF可以单独部署，也可以合一部署。例如，UL CL/UPF可以与PSA2-UPF合一部署，也可以与PSA1-UPF合一部署，或者同时与PSA1-UPF和PSA2-UPF合一部署。
为了更好地理解本申请实施例，下文介绍一些本申请实施例可能涉及的术语。
1.园区、园区内部服务网、园区专网
园区也可以称为园区机构或商业机构。例如，园区可以是一个商城或企业园区，可以是一个中央商务区，也可以是一个咖啡厅或餐馆。
本申请中，主要以拜访地的园区为例介绍本申请实施例提供的方法。例如，终端设备的归属地为上海，拜访地为北京，拜访地的园区可以是北京的某商城。
园区内部服务网为一种由园区提供资源或服务，并为园区内用户提供服务的网络。可以理解，具有相同或相似功能的网络也可以被视为本申请中的园区内部服务网，名称并不限定。示例性地，该服务可以是企业的办公服务、AR、VR等。例如，图3中与PSA2-UPF连接的DN可以为园区内部服务网。
园区专网，即园区范围部署的园区运营商网络，可支持园区用户通过该网络接入园区业务，和/或接入互联网业务，例如即时通讯、邮件、网页浏览等业务。其中，用于提供园区专网的设备可以是5G设备，例如图3中的UL CL/UPF、PSA2-UPF，以及与PSA2-UPF连接的DN。当用户进入园区专网的区域内，用户都可以接入园区内部服务网。
在实际商用场景下，用户访问园区有流量免费/统付的诉求，这里的流量可以包括互联网业务流量和园区业务流量。即用户在园区内访问园区业务免费，访问互联网业务免费或收费；用户出园区访问互联网正常收费。其中，免费/统付是指，在特定条件下(例如在园区内)，用户访问园区内部服务网或者互联网时，运营商不向用户收费，而是跟园区统一结算收取费用。为了简洁，下文将免费/统付的流量称为免流。
在现有的计费方法中，SMF分别给辅锚点UPF和主锚点UPF下发计费规则，以使锚点UPF(包括主锚点UPF和辅锚点UPF)对用户的流量进行统计；锚点UPF通过SMF将用户的流量使用情况上报给本省CHF，以使CHF生成话单。运营商的计费采集系统从CHF采集话单，对于非拜访地用户的话单通过采集系统送回用户归属地。最终由运营商的业务运营支撑系统处理话单并进行计费。在处理的话单的过程中需要能区分免流和正常收费流量，免流部分和园区结算，正常收费部分和终端用户结算。
如图4所示，当UE在园区外时，UE可以通过PSA1(PSA1-UPF)传输数据网络中业务的数据流，该数据网络可以为互联网；当UE在园区内时，UE可以通过ULCL+PSA2(可以是UL CL/UPF与PSA2-UPF合一部署的网元)传输园区专网业务的数据流，UE还可以通过ULCL+PSA2以及PSA1在园区内访问互联网(Internet)业务。在园区内，UE的Internet流量分流到PSA1，在不为园区单独申请费率组(rating group，RG)的情况下，可能无法筛选出免流的Internet流量。
为了区分不同园区的免流流量和正常收费流量，可以将不同园区的业务流量与不同的RG关联，即根据不同RG区分不同园区的流量、区分免费和正常收费的流量。由于RG由运营商统一规划，且该实现方式涉及到的归属地以及归属地的园区的数量非常多，因此可行性较低。因此，如何实现园区内免流流量的计费成为亟待解决的问题。
有鉴于此，本申请实施例提供一种通信方法，以实现园区内免费流量的计费。
图5示出了一种本申请提供的通信方法500的示意性流程图。该方法可以包括以下几个步骤。
S510，会话管理网元获取第一终端设备的第一信息。
该第一信息包括该第一数据流的使用量，该第一数据流包括由第一用户面功能网元分流到第二用户面功能网元的该第一终端设备的数据流。
其中，该第一用户面功能网元可以用于对第一区域内的终端设备的数据流进行分流，即该第一用户面功能网元可以将该第一区域内终端设备的数据流分流至锚点用户面功能网元。该第一区域可以为该第一终端设备签约的专用网络的签约地。该第一终端设备可以为该第一区域中的任一终端设备。
该第二用户面功能网元可以用于传输该第一终端设备和数据网络之间的用户面数据。示例性地，该第二用户面功能网元可以为主锚点用户面功能网元，该主锚点用户面功能网元在该第一终端设备的会话生命周期内可以不变更；该数据网络可以为互联网。
举例来说，该第一区域可以为园区#1所在的区域，该第一用户面功能可以是部署在园区#1附近的用于上行分流的用户面功能网元，该第二用户面功能网元可以是该园区#1所属地市部署的锚点用户面功能网元；该第一用户面功能网元可以根据分流规则将该第一终端设备的数据流分流至该第二用户面功能网元和/或第三用户面功能网元。该第三用户面功能网元可以为辅锚点用户面功能网元，用于传输该第一终端设备和该专用网络之间的用户面数据。该第三用户面功能网元可以与该第一用户面功能网元合一部署，或者单独部署。
一种可能的实现方式中，该会话管理网元向该第一用户面功能网元发送第一指示信息，该第一指示信息指示该第一用户面功能网元统计并上报该第一数据流的使用量；该会话管理网元接收来自该第一用户面功能网元的第一信息，该第一信息包括该第一用户面功能网元的统计结果；该会话管理网元将该第一数据流的使用量与第一标识信息相关联。
示例性地，该第一信息还可以包括该第一标识信息，该会话管理网元根据该第一信息关联该第一标识信息和该第一数据流的使用量。或者，该会话管理网元可以获取该第一标识信息，并将该第一标识信息关联该第一数据流的使用量。其中，将第一标识信息关联第一数据流的使用量可以理解为，通过查询该第一标识信息可以获知该第一数据流的使用量。
其中，该第一标识信息包括以下信息中的至少一项：该第一用户面功能网元的标识，该第一终端设备的位置信息，该第一区域关联的费率组(rating group，RG)。
该第一终端设备的位置信息例如可以是该第一终端设备所在的小区(cell)的标识，例如NR小区全球标识(NR cell global identifier，NCGI)、该第一终端设备所在追踪区域对应的追踪区域代码(tracking area code，TAC)、该第一终端设备所接入的接入网设备的标识，该第一终端设备所在的该地理位置的标识，该地理位置的范围可以小于TA的范围，例如，该地理位置可以是某县或者某街道等。
可选地，该方法还包括：该会话管理网元向该第二用户面功能网元发送第二指示信息，该第二指示信息可以指示该第二用户面功能网元不统计该第一数据流的使用量。也就是说，在该会话管理网元指示该第一用户面功能网元统计该第一数据流的同时，该会话管理网元还指示该第二用户面功能网元不统计该第一数据流的使用量，从而保证对该第一数据流不会多计费或少计费。
可选地，该会话管理网元还可以获取第二信息。该第二信息包括该第二用户面功能网元统计的该第一终端设备的数据流的使用量。例如，在第一终端设备的位置发生变化的情况下，该会话管理网元可以主动向该第二用户面功能网元查询该第一终端设备的数据流使用量；或者，在该第一终端设备的会话删除时，该第二用户面功能网元可以上报该第一终端设备的数据流使用量。或者，该第二用户面功能网元周期性上报统计的该第一终端设备的数据流的使用量。
另一种可能的实现方式中，该会话管理网元可以接收来自该第二用户面功能网元的第一信息，即该会话管理网元可以接收该第二用户面功能网元统计的该第一数据流的使用量。
示例性地，该会话管理网元向该第二用户面功能网元发送第三指示信息，该第三指示信息可以指示该第二用户面功能网元统计并上报该第一数据流的使用量；该会话管理网元接收来自该第二用户面功能网元的该第一数据流的使用量，该第一数据流的使用量与该第二用户面功能网元的标识相关联。例如，该第二用户面功能网元可以上报该第二用户面功能网元的标识信息以及该第一数据流的使用量，或者，该会话管理网元可以获取该第二用户面功能网元的标识信息，并将该第二用户面功能网元的标识信息与该第一数据流的使用量相关联。
进一步地，该会话管理网元将该第二用户面功能网元的标识信息修改为第二标识信息。该第二标识信息与该第一用户面网元的标识信息相关联。例如，该第二用户面功能网元的标识信息为第二字符串， 该第一用户面功能网元的标识为第一字符串，该会话管理网元可以将该第二用户面功能网元的标识修改为该第一字符串加该第二字符串。
也就是说，该会话管理网元在接收到来自该第二用户面功能网元的该第一数据流的使用量后，可以将该第一数据流的使用量关联的该第二用户面网元的标识修改为与该第一用户面网元的标识的相关联的标识。
可选地，该方法还包括：该会话管理网元向该第三用户面功能网元发送指示信息，该指示信息可以指示该第三用户面功能网元统计并上报第二数据流的使用量。该第二数据流为由该第一用户面网元分流到该第三用户面网元的该第一终端设备的数据流。该第二数据流可以是该专用网络中业务的数据流。
相应地，该第三用户面功能网元向该会话管理网元发送该第二数据流的使用量。可选地，该第三用户面功能网元还可以向该会话管理网元发送该第三用户面功能网元的标识信息，以使该第三用户面功能网元的标识信息与该第二数据流的使用量相关联。
应理解，在该第一用户面功能网元与该第三用户面功能网元合一部署的情况下，该第一用户面功能网元标识信息与该第三用户面功能网元的标识信息可以相同；在该第一用户面功能网元与该第三用户面功能网元独立部署的情况下，该第一用户面功能网元的标识信息与该第三用户面功能网元的标识信息可以不同。
可选地，在S510之前，该方法还包括：该会话管理网元接收来自策略控制功能网元的计费规则。该计费规则指示该第一数据流为免费流量。
S520，该会话管理网元向计费功能网元发送第一计费请求消息。
相应地，该计费功能网元接收来自该会话管理网元的该第一计费请求消息。
该第一计费请求消息可以包括该第一标识信息和该第一数据流的使用量。
在该会话管理网元获取了第二信息(参考S510中第一种可能的实现方式中的描述)和/或该会话管理网元接收到来自该第三用户面功能网元的该第二数据流的使用量的情况下，该第一计费请求消息还可以包括该第二用户面功能网元的标识信息和该第二用户面功能网元统计的该第一终端设备的数据流的使用量，该第三用户面网元的标识信息以及该第二数据流的使用量(第三信息)。
可选地，在该情况下，该方法还可以包括：该会话管理网元基于该第一信息和该第二信息，以及该第三信息中的至少一种确定该第一计费请求消息，或者说，在该会话管理网元接收到来自该第一用户面功能网元的第一信息、第二信息以及该第三信息的情况下，该会话管理网元拆分出该第一计费请求消息、第二计费请求消息和第三计费请求消息，以使该第一计费请求消息包括该第一标识信息和该第一数据流的使用量，该第二计费请求消息包括该第二用户面功能网元的标识信息和该第二用户面功能网元统计的该第一终端设备的数据流的使用量，该第三计费请求消息该第三用户面功能网元的标识信息和该第二数据流的使用量。
示例性地，该第二用户面功能网元统计的该第一终端设备的数据流的使用量可以为零或为空。
S530，该计费功能网元基于该第一标识和该第一信息生成该第一终端设备的第一话单。
该第一话单可以用于对该第一终端设备的第一数据流的使用量计费。
在该第一计费请求消息包括该第二标识信息和该第二用户面功能网元统计的该第一终端设备的数据流的使用量的情况下，该方法还可以包括：该计费功能网元从该第一计费请求消息中拆分出该第一标识信息和该第一数据流的使用量，基于该第一标识和该第一信息生成该第一终端设备的第一话单；可选地，该计费功能网元从该第一计费请求消息中拆分出该第二标识信息和该第二用户面功能网元统计的该第一终端设备的数据流的使用量，并生成该第一终端设备的第二话单；该计费功能网元从该第一计费请求消息中拆分出该第三用户面功能网元的标识信息和该第二数据流的使用量，并生成该第一终端设备的第三话单。
可选地，该方法还包括S540，该计费功能网元将该第一终端设备的该第一话单存储于第一话单目录。该第一话单目录用于存储免费的数据流的话单。
可选地，该计费功能网元将该第一终端设备的该第三话单存储于该第一话单目录。
一种可能的实现方式中，该计费功能网元配置有第一配置信息，该计费功能网元基于该第一配置信息将该第一话单存储于第一话单目录。
该第一配置信息可以包括以下至少一种类型的信息：用户面功能网元的标识信息，位置区域信息，费率组信息。
其中，该用户面功能网元的标识信息可以包括至少一个免流的用户面功能网元的标识，该至少一个免流的用户面功能网元包括该第一用户面功能网元。例如，该用户面功能网元的标识信息可以是一个用户功能网元的标识列表，该标识列表中包括该第一用户面功能网元的标识。免流的用户面功能网元可以理解为传输免费的数据流的用户面功能网元。
该位置区域信息可以包括至少一个区域的位置信息，该至少一个区域为免流的区域。免流的区域可以理解为，终端设备在该区域中的数据流可以免费。该至少一个区域可以是小区(cell)、追踪区域TA、地理位置等。该至少一个区域包括该第一区域。该至少一个费率组可以包括至少一个免流的用户面功能网元对应的费率组，或至少一个免流的区域对应的费率组。
示例性地，该计费功能网元在接收到该第一计费请求消息后，可以查询该第一标识信息是否属于该第一配置信息配置的免流的用户面功能网元的标识列表、或位置区域的标识列表或费率组的列表，若是，则该计费功能网元将该第一话单存储在该第一话单目录。
另一种可能的实现方式中，该第一计费请求消息携带第四指示信息，该第四指示信息指示该第一数据流为免费的数据量，该计费功能网元根据该第四指示信息将该第一话单存储在该第一话单目录。
可选地，若该计费功能网元为该第一终端设备的拜访地计费功能网元，运营商计费系统可以不将该第一话单采集回归属地，避免了现有技术中该第一话单被采集回归属地，由归属地处理，但归属地无法识别拜访地需免费的数据流的情况。
根据本申请实施例提供的通信方法，会话管理网元可以获取终端设备的第一数据流的使用量，该第一数据流包括由第一用户面功能网元分流到第二用户面功能网元的该第一终端设备的数据流，并向计费功能网元发送第一标识信息和该第一信息，以使该计费功能网元生成该第一数据流的使用量的话单，实现对该第一数据流的计费。其中，该第一用户面功能网元用于对第一区域内终端设备的数据流进行分流，该第一区域为该第一终端设备签约的专用网络的签约地，该第二用户面网元用于传输该第一终端设备和数据网络之间的用户面数据。
应理解，图5所示的方法中，各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
下面结合图6，对本申请实施例提供的通信方法600进行说明。图6中的UE#1是图5中第一终端设备的一个示例，PCF是图5中策略控制网元的一个示例，ULCL+PSA1是图5中第一用户面网元的一个示例，SMF是图5中会话管理网元的一个示例，PSA2是图5中第二用户面网元的一个示例。
在S601之前，UE#1向园区会员系统注册会员。
也可以理解为，UE#1注册成为园区会员。
可选地，园区会员系统录入UE#1的会员信息(例如可以是用户标识等信息)，可以向PCF发送UE#1的会员信息。例如，园区会员系统可以通过能力开放平台向PCF发送UE#1的会员信息。
其中，该PCF可以是H-PCF或V-PCF。在该PCF为H-PCF的情况下，该H-PCF可以是AM-PCF或者SM-PCF，或者是合一部署的AM-PCF和S-PCF；在该PCF为V-PCF的情况下，该V-PCF可以是AM-PCF，或者是合一部署的AM-PCF和S-PCF。
示例性地，用户标识还可以理解为用户的号码，例如移动台国际综合业务数字网号码(mobile station international integrated services digital network number，MSISDN)、通用公共用户标识(generic public subscription identifier，GPSI)、国际移动用户识别码(International Mobile Subscriber Identity，IMSI)或用户永久标识(subscription permanent identifier，SUPI)等。
S601，PCF通过AMF向SMF发送园区策略。相应地，SMF接收来自PCF的园区策略。
示例性地，在PCF接收到来自园区会员系统的会员信息后，可以基于该会员信息通过AMF向SMF发送该园区的园区策略。
该园区策略可以包括计费规则。该计费规则可以指示对不同类型的数据流的处理和计费，不同类型的数据流可以包括正常收费的数据流和免费的数据流。
该园区策略还可以包括分流规则，QoS参数等信息。其中，分流规则用于指示UPF例如ULCL UPF对签约业务进行分流；QoS参数可以包括聚合最大比特速率(aggregate maximum bit rate，AMBR)、分配与保留优先级(allocation and retention priority,ARP)、保证流比特速率(guaranteed flow bit rate，GFBR)、最大流比特速率(maximum flow bit rate，MFBR)、5G业务质量标识(5G QoS identifier，5QI)等。
可选地，PCF还可以向SMF发送园区策略的标识，该SMF中配置有至少一个园区策略以及园区策略对应的标识。SMF可以通过该园区策略的标识匹配相应的园区策略。
S602a，SMF向ULCL+PSA2发送会话管理消息。
相应地，ULCL+PSA1接收来自SMF的该会话管理消息。
该会话管理消息用于UPF管理UE的PDU会话。示例性地，该会话管理消息可以是PFCP会话建立请求(PFCP Session Establishment Request)消息或者PFCP会话修改请求(PFCP Session Modification Request)消息。
该会话管理消息可以携带计费规则。该计费规则可以包括数据包检测规则(packet detection rule，PDR)和使用量上报规则(usage reporting rule，URR)。示例性地，PDR、URR指示ULCL+PSA2检测并上报本地转发、通过N6接口转发、或者通过N19隧道转发的该UE#1的数据流。
在该园区策略指示计费规则为免流的情况下，该会话管理消息携带指示信息#1(第一指示信息的一例)，该指示信息#1指示该ULCL UPF统计分流到PSA1的数据流的使用量。
具体地，SMF在园区策略的计费规则为免流的情况下，将用于分流到PSA1的PDR关联URR，并向ULCL UPF发送该PDR以及关联的URR，以指示ULCL UPF对分流到PSA1的数据流(第一数据流的一例)进行统计上报。
可选地，该会话管理消息可以携带分流规则，以使ULCL UPF将UE#1的数据流分流到多个锚点UPF，例如PSA1和PSA2。示例性地，分流到PSA2的可以是UE#1签约的园区业务的数据流，分流到PSA1的业务可以是互联网业务的数据流。
可选地，S603a，ULCL+PSA2向SMF发送分流到PSA1的数据流的使用量。
示例性地，ULCL+PSA2可以通过PFCP会话报告请求(PFCP Session Report Request消息)向SMF发送分流到PSA1的数据流的使用量。可选地，该PFCP会话报告请求消息还可以携带ULCL+PSA2的标识，或者携带ULCL UPF的标识。
可选地，S602b，SMF向PSA1发送会话管理消息。
该会话管理请求消息可以参考S603a中的相关描述。该会话管理消息携带指示信息#2(第二指示信息的一例)，该指示信息#2指示该PSA1不统计分流到PSA1的数据流的使用量。
该步骤可以在S603a之前执行，或者，该步骤可以和S602a同时执行，也就是说，SMF指示ULCL UPF上报第一数据流的使用量的同时，SMF可以指示PSA1不对分流到PSA1的UE#1的数据流做统计。
可选地，SMF还可以向PSA2发送会话管理消息。
该会话管理请求消息可以参考S602a中的相关描述。该会话管理消息可以携带计费规则，以指示PSA2对分流到PSA2的数据流进行统计上报。
相应地，PSA2向SMF发送统计的UE#1的数据流的使用量。PSA2统计的UE#1的数据流的使用量可以是园区业务的数据流。
可选地，S604，SMF获取还可以获取PSA1统计的UE#1的数据流的使用量。
例如，在UE#1的位置发生变化的情况下，该，SMF可以主动向PSA1查询UE#1的数据流使用量；或者，在UE#1的会话删除时，PSA1可以上报UE#1的数据流使用量。
可选地，S605，SMF基于ULCL+PSA2发送的分流到PSA1的数据流的使用量，以及PSA1统计的UE#1的数据流的使用量向CHF发送计费请求消息。
相应地，CHF接收来自SMF的该计费请求消息。
示例性地，该计费请求消息可以是数据计费请求(Charging Data Request)消息。
一个示例中，该计费请求消息可以包括ULCL+PSA2的标识以及ULCL+PSA2发送的分流到PSA1的数据流的使用量，PSA1的标识以及PSA1上报的UE#1的数据流使用量。即SMF向CHF发送的一个计费请求消息中可以包括多个UPF ID以及对应的UPF统计的UE#1的数据流的使用量。
另一个示例中，SMF需要基于UPF ID拆分话单，即将ULCL+PSA2和PSA1统计的数据流的使用量拆分成不同的消息上报给CHF。
S606，CHF基于该计费请求消息生成该UE#1的话单，并将ULCL+PSA2统计的UE#1的数据流使用量对应的话单存储在话单目录#1。
该话单目录#1用于存储免费的数据流使用量对应的话单。该话单目录#1可以是CHF中新增的话单目录。
若该计费请求消息包括多个UPF ID以及多个UPF统计的UE#1的数据流的使用量，该CHF可以基于该计费请求消息拆分该UE#1的话单。即CHF可以基于每个UPF ID以及UPF ID对应的UPF统计的UE#1的数据流的使用量分别生成话单。其中，该多个UPF可以包括ULCL+PSA2和PSA1。
示例性地，该CHF可以配置免流的UPF ID列表，CHF根据该计费请求消息中的UPF ID确定该UPF统计的UE#1的数据流是否为免流。例如，该计费请求消息包括ULCL+PSA2的ID，则CHF可通过查询该UPF ID列表确定将ULCL+PSA2的ID对应的话单存储在该话单目录#1。
可选地，该计费请求消息中还可以携带指示信息#4，该指示信息#4指示ULCL+PSA2统计的数据流为免流，CHF可通过该指示信息#4确定将ULCL+PSA2的ID对应的话单存储在该话单目录#1。
若该CHF为拜访地CHF，后续，运营商计费系统可以不将新增的免流目录(话单目录#1)中的话单采集回归属地，归属地的计费可以从拜访地CHF的话单目录#1中提取免流的话单，根据UPF ID区分园区，跟园区进行结算。
图7为本申请实施例提供的另一种通信方法700的示例性流程图。图7中的UE#1是图5中第一终端设备的一个示例，PCF是图5中策略控制网元的一个示例，ULCL+PSA1是图5中第一用户面网元的一个示例，SMF是图5中会话管理网元的一个示例，PSA2是图5中第二用户面网元的一个示例。
S701，PCF通过AMF向SMF发送园区策略。相应地，SMF接收来自PCF的园区策略。
S702a，SMF向ULCL+PSA2发送会话管理消息。
相应地，ULCL+PSA1接收来自SMF的该会话管理消息。
可选地，S703a，ULCL+PSA2向SMF发送分流到PSA1的数据流的使用量。
相应地，SMF接收来自ULCL+PSA2的分流到PSA1的数据流的使用量。
可选地，S702b，SMF向PSA1发送会话管理消息。
也就是说，SMF指示ULCL+PSA2上报第一数据流的使用量的同时，SMF可以指示PSA1不对分流到PSA1的UE#1的数据流做统计。
可选地，SMF向PSA2发送会话管理消息。
该会话管理请求消息可以参考S602a中的相关描述。该会话管理消息可以携带计费规则，以指示PSA2对分流到PSA2的数据流进行统计上报。
相应地，PSA2向SMF发送统计的UE#1的数据流的使用量。PSA2统计的UE#1的数据流的使用量可以是园区业务的数据流。
可选地，S704，SMF获取还可以获取PSA1统计的UE#1的数据流的使用量。
例如，在UE#1的位置发生变化的情况下，该，SMF可以主动向PSA1查询UE#1的数据流使用量；或者，在UE#1的会话删除时，PSA1可以上报UE#1的数据流使用量。
步骤S701至步骤S704可以参考S601至S604中的描述，不再赘述。
可选地，S705，SMF基于ULCL+PSA2发送的分流到PSA1的数据流的使用量，以及PSA1统计的UE#1的数据流的使用量向CHF发送计费请求消息。
相应地，CHF接收来自SMF的该计费请求消息。
示例性地，该计费请求消息可以是数据计费请求(Charging Data Request)消息。
一个示例中，该计费请求消息可以包括UE#1的位置信息以及ULCL+PSA2发送的分流到PSA1的数据流的使用量。UE#1的位置信息可以参考S510中的描述。
另一个示例中，该计费请求消息可以包括ULCL+PSA2关联的RG(或者园区关联的RG)以及ULCL+PSA2发送的分流到PSA1的数据流的使用量。
S707，CHF基于该计费请求消息生成该UE#1的话单，并将ULCL+PSA2统计的UE#1的数据流使用量对应的话单存储在话单目录#1。
该话单目录#1用于存储免费的数据流使用量对应的话单。
示例性地，该CHF可以配置免流的位置区域信息列表，CHF根据该计费请求消息中的UE#1的位置信息确定该UE#1的数据流是否为免流。如果是，则CHF将该ULCL+PSA2的ID对应的话单存储在该话单目录#1。
或者，该CHF可以配置免流的RG列表，CHF根据该计费请求消息中的ULCL+PSA2关联的RG确定该UE#1的数据流是否为免流。如果是，则CHF将该ULCL+PSA2的ID对应的话单存储在该话单目录#1。
若该CHF为拜访地CHF，后续，运营商计费系统可以不将新增的免流目录(话单目录#1)中的话单采集回归属地，归属地的计费可以从拜访地CHF的话单目录#1中提取免流的话单，根据UE#1的位置信息或RG区分园区，跟园区进行结算。
图8为本申请实施例提供的另一种通信方法800的示例性流程图。图8中的UE#1是图5中第一终端设备的一个示例，PCF是图5中策略控制网元的一个示例，ULCL+PSA1是图5中第一用户面网元的一个示例，SMF是图5中会话管理网元的一个示例，PSA2是图5中第二用户面网元的一个示例。
S801，PCF通过AMF向SMF发送园区策略。相应地，SMF接收来自PCF的园区策略。
S802a，SMF向ULCL+PSA2发送会话管理消息。
相应地，ULCL+PSA2接收来自SMF的该会话管理消息。
该会话管理消息携带计费规则，该计费规则指示PSA2统计并上报UE#1的数据流的使用量。
S803a，ULCL+PSA2向SMF发送分流到PSA2的数据流的使用量。
相应地，SMF接收来自ULCL+PSA2的分流到PSA2的数据流的使用量。
S802b，SMF向PSA1发送会话管理消息。
该会话管理消息携带计费规则，该计费规则指示PSA1统计并上报UE#1的数据流的使用量。
S803b，PSA1向SMF发送统计的UE#1的数据流的使用量。示例性地，该数据流为分流到该PSA1的数据流。
可选地，S804，SMF获取还可以获取PSA1统计的UE#1的数据流的使用量。
该步骤可以参考S704中的描述。
S805，SMF向CHF发送计费请求消息。相应地，CHF接收来自SMF的该计费请求消息。
该计费请求消息可以携带ULCL+PSA2的ID以及分流到PSA1的数据流的使用量。可选地，该计费请求消息还可以携带PSA2统计的该UE#1的数据流的使用量。
示例性地，在SMF发送该计费请求消息之前，SMF将PSA1的ID修改为与ULCL+PSA2的ID相关联的ID。例如将PSA1的ID修改为PSA1的ID加ULCL+PSA2的ID。
S806，CHF基于该计费请求消息生成该UE#1的话单，并将该话单存储在话单目录#1。
该步骤可以参考S606中的描述，不再赘述。
若该CHF为拜访地CHF，后续，运营商计费系统可以不将新增的免流目录(话单目录#1)中的话单采集回归属地，归属地的计费可以从拜访地CHF的话单目录#1中提取免流的话单，根据UPF ID区分园区，跟园区进行结算。
以上结合图5至图8详细说明了本申请实施例提供的方法。以下，结合图9至图11详细说明本申请实施例提供的通信装置。应理解，装置实施例的描述与方法实施例的描述相互对应，因此，未详细描述的内容可以参见上文方法实施例，为了简洁，这里不再赘述。
图9是本申请实施例提供的通信装置1000的示意性框图。如图9所示，该通信装置1000可以包括：收发单元1010和处理单元1020。
在一种可能的设计中，该通信装置1000可以是上文方法实施例中的会话管理网元，也可以是用于实现上文方法实施例中会话管理网元的功能的芯片。
应理解，该通信装置1000可对应于本申请实施例方法500中的会话管理网元，或者，对应于方法600至方法800中的SMF。该通信装置1000可以包括用于执行图5中的方法500中的会话管理网元执行的方法的单元，或者可以包括用于执行方法600至方法800中的SMF执行的方法的单元。并且，该通信装置1000中的各单元和上述其他操作和/或功能分别为了实现图5中的方法500、图6中的方法600、图7中的方法700或图8中的方法800的相应流程。应理解，各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
在另一种可能的设计中，该通信装置1000可以是上文方法实施例中的计费功能网元，也可以是用于实现上文方法实施例中计费功能网元的功能的芯片。
应理解，该通信装置1000可对应于本申请实施例方法500中的计费功能网元，或者，对应于方法600至方法800中的CHF。该通信装置1000可以包括用于执行图5中的方法500中的计费功能网元执行的方法的单元，或者可以包括用于执行方法600至方法800中的CHF执行的方法的单元。并且，该通信装置1000中的各单元和上述其他操作和/或功能分别为了实现图5中的方法500、图6中的方法600、图7中的方法700或图8中的方法800的相应流程。应理解，各单元执行上述相应步骤的具体过程在上述方法 实施例中已经详细说明，为了简洁，在此不再赘述。
在另一种可能的设计中，该通信装置1000可以是上文方法实施例中的第一用户面功能网元，也可以是用于实现上文方法实施例中第一用户面功能网元的功能的芯片。
应理解，该通信装置1000可对应于本申请实施例方法500中的第一用户面功能网元，或者，对应于方法600至方法800中的ULCL+PSA2。该通信装置1000可以包括用于执行图5中的方法500中的第一用户面功能网元执行的方法的单元，或者可以包括用于执行方法600至方法800中的ULCL+PSA2执行的方法的单元。并且，该通信装置1000中的各单元和上述其他操作和/或功能分别为了实现图5中的方法500、图6中的方法600、图7中的方法700或图8中的方法800的相应流程。应理解，各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
还应理解，该通信装置1000中的收发单元1010可对应于图9中示出的通信设备2000中的收发器2020，该通信装置1000中的处理单元1020可对应于图9中示出的通信设备2000中的处理器2010。
还应理解，当该通信装置1000为芯片时，该芯片包括收发单元。可选的，该芯片还可以包括处理单元。其中，收发单元可以是输入输出电路或通信接口；处理单元可以为该芯片上集成的处理器或者微处理器或者集成电路。
收发单元1010用于实现通信装置1000的信号的收发操作，处理单元1020用于实现通信装置1000的信号的处理操作。可选的，收发单元1010组成获取单元，或者说收发单元1010可以称为获取单元。可选的，收发单元1010和处理单元1020组成获取单元。
可选的，该通信装置1000还包括存储单元1030，该存储单元1030用于存储指令。
图10是本申请实施例提供的装置2000的示意性框图。如图10所示，该装置2000包括：至少一个处理器2010。该处理器2010与存储器耦合，用于执行存储器中存储的指令，以执行图5、图6、图7或图8所述的方法。可选的，该装置2000还包括收发器2020，该处理器2010与存储器耦合，用于执行存储器中存储的指令，以控制收发器2020发送信号和/或接收信号。可选的，该装置2000还包括存储器2030，用于存储指令。
应理解，上述处理器2010和存储器2030可以合成一个处理装置，处理器2010用于执行存储器2030中存储的程序代码来实现上述功能。具体实现时，该存储器2030也可以集成在处理器2010中，或者独立于处理器2010。
还应理解，收发器2020可以包括接收器(或者称，接收机)和发射器(或者称，发射机)。收发器2020还可以进一步包括天线，天线的数量可以为一个或多个。收发器2020又可以是通信接口或者接口电路。
当该装置2000为芯片时，该芯片包括收发单元和处理单元。其中，收发单元可以是输入输出电路或通信接口；处理单元可以为该芯片上集成的处理器或者微处理器或者集成电路。
图11是本申请实施例的一种芯片系统的示意图。这里的芯片系统也可为电路组成的系统。图11所示的芯片系统3000包括：逻辑电路3010以及输入/输出接口(input/output interface)3020，所述逻辑电路用于与输入接口耦合，通过所述输入/输出接口传输数据(例如IP地址)，以执行图5、图6、图7或图8所述的方法。
本申请实施例还提供了一种处理装置，包括处理器和接口。所述处理器可用于执行上述方法实施例中的方法。
应理解，上述处理装置可以是一个芯片。例如，该处理装置可以是现场可编程门阵列(field programmable gate array，FPGA)，可以是专用集成芯片(application specific integrated circuit，ASIC)，还可以是系统芯片(system on chip，SoC)，还可以是中央处理器(central processor unit，CPU)，还可以是网络处理器(network processor，NP)，还可以是数字信号处理电路(digital signal processor，DSP)，还可以是微控制器(micro controller unit，MCU)，还可以是可编程控制器(programmable logic device，PLD)或其他集成芯片。
在实现过程中，上述方法的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机寄存器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。为避免重复，这里不再详细描述。
应注意，本申请实施例中的处理器可以是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
可以理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。
根据本申请实施例提供的方法，本申请还提供一种计算机程序产品，该计算机程序产品包括：计算机程序代码，当该计算机程序代码在计算机上运行时，使得该计算机执行图5至图8所示实施例中任意一个实施例的方法。
根据本申请实施例提供的方法，本申请还提供一种计算机可读介质，该计算机可读介质存储有程序代码，当该程序代码在计算机上运行时，使得该计算机执行图5至图8所示实施例中任意一个实施例的方法。
根据本申请实施例提供的方法，本申请还提供一种系统，该系统包括前述的会话管理网元和计费功能网元。可选的，该系统还包括前述的第一用户面功能网元和第二用户面功能网元。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现，当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读信息介质向另一个计算机可读存储介质传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，高密度数字视频光盘(digital video disc，DVD))、或者半导体介质(例如，固态硬盘(solid state disc，SSD))等。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其他的形式。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (26)

  1. 一种通信方法，其特征在于，包括：
    会话管理网元获取第一终端设备的第一信息，所述第一信息包括第一数据流的使用量，所述第一数据流包括由第一用户面功能网元分流到第二用户面功能网元的所述第一终端设备的数据流，所述第一用户面功能网元用于对第一区域内终端设备的数据流进行分流，所述第一区域为所述第一终端设备签约的专用网络的签约地，所述第二用户面功能网元用于传输所述第一终端设备和数据网络之间的用户面数据；
    所述会话管理网元向计费功能网元发送第一计费请求消息，所述第一计费请求消息包括第一标识信息和所述第一信息，所述第一标识信息用于关联所述第一区域。
  2. 根据权利要求1所述的方法，其特征在于，所述会话管理网元获取第一终端设备的第一信息，包括：
    所述会话管理网元向所述第一用户面功能网元发送第一指示信息，所述第一指示信息指示统计并上报所述第一数据流的使用量；
    所述会话管理网元接收来自所述第一用户面功能网元的所述第一数据流的使用量。
  3. 根据权利要求1或2所述的方法，其特征在于，所述方法还包括：
    所述会话管理网元向所述第二用户面功能网元发送第二指示信息，所述第二指示信息指示不统计所述第一数据流的使用量。
  4. 根据权利要求1至3中任一项所述的方法，其特征在于，在所述会话管理网元向计费功能网元发送第一计费请求消息之前，所述方法还包括：
    所述会话管理网元接收来自所述第二用户面功能网元的第二信息，所述第二信息包括所述第二用户面功能网元统计的所述第一终端设备的数据流的使用量。
  5. 根据权利要求4所述的方法，其特征在于，所述会话管理网元向计费功能网元发送第一计费请求消息，包括：
    所述会话管理网元基于所述第二信息向所述计费功能网元发送所述第一计费请求消息，所述第一计费请求消息还包括所述第二用户面功能网元的标识信息和所述第二信息。
  6. 根据权利要求4所述的方法，其特征在于，所述方法还包括：
    所述会话管理网元基于所述第一信息和所述第二信息确定所述第一计费请求消息和第二计费请求消息，所述第二计费请求消息包括所述第二用户面功能网元的标识信息和所述第二信息；
    所述会话管理网元向所述计费功能网元发送所述第二计费请求消息。
  7. 根据权利要求1至6中任一项所述的方法，其特征在于，所述第一标识信息包括以下信息中的至少一项：
    所述第一用户面功能网元的标识，所述第一终端设备的位置信息，所述第一区域关联的费率组RG。
  8. 根据权利要求1至7中任一项所述的方法，其特征在于，在所述会话管理网元获取第一终端设备的第一信息之前，所述方法还包括：
    所述会话管理网元接收来自策略控制功能网元的计费规则，所述计费规则指示所述第一终端设备的数据流类型为免费的数据流。
  9. 一种通信方法，其特征在于，包括：
    会话管理网元接收来自第二用户面功能网元的第一信息，所述第一信息包括第一数据流的使用量，所述第一数据流包括由第一用户面功能网元分流到第二用户面功能网元的所述第一终端设备的数据流，所述第一用户面功能网元用于对第一区域内终端设备的数据流进行分流，所述第一区域为所述第一终端设备签约的专用网络的签约地，所述第二用户面功能网元用于传输所述第一终端设备和数据网络之间的用户面数据；
    所述会话管理网元向计费功能网元发送第一计费请求消息，所述第一计费请求消息包括第二标识信息和所述第一信息，所述第二标识信息与所述第一用户面功能网元的标识信息相关联。
  10. 根据权利要求9所述的方法，其特征在于，在所述会话管理网元接收来自第二用户面功能网元的第一信息之前，所述方法还包括：
    所述会话管理网元向所述第二用户面功能网元发送第三指示信息，所述第三指示信息指示统计并上 报所述第一数据流的使用量。
  11. 根据权利要求9或10所述的方法，其特征在于，所述第一信息关联所述第二用户面功能网元的标识信息，在所述会话管理网元向计费功能网元发送第一计费请求消息之前，所述方法还包括：
    所述会话管理网元将所述第二用户面功能网元的标识信息修改为第二标识信息。
  12. 根据权利要求9至11中任一项所述的方法，其特征在于，在所述会话管理网元向计费功能网元发送第一计费请求消息之前，所述方法还包括：
    所述会话管理网元接收来自所述第二用户面功能网元的第二信息，所述第二信息包括所述第二用户面功能网元统计的所述第一终端设备的数据流的使用量。
  13. 根据权利要求12所述的方法，其特征在于，所述会话管理网元向计费功能网元发送第一计费请求消息，包括：
    所述会话管理网元基于所述第二信息向所述计费功能网元发送所述第一计费请求消息，所述第一计费请求消息还包括所述第二用户面功能网元的标识信息和所述第二信息。
  14. 根据权利要求12所述的方法，其特征在于，所述方法还包括：
    所述会话管理网元基于所述第一信息和所述第二信息确定所述第一计费请求消息和第二计费请求消息，所述第二计费请求消息包括所述第二用户面功能网元的标识信息和所述第二信息；
    所述会话管理网元向所述计费功能网元发送所述第二计费请求消息。
  15. 根据权利要求9至14中任一项所述的方法，其特征在于，在所述会话管理网元获取第一终端设备的第一信息之前，所述方法还包括：
    所述会话管理网元接收来自策略控制功能网元的计费规则，所述计费规则指示所述第一终端设备的数据流类型为免费的数据流。
  16. 一种通信方法，其特征在于，包括：
    计费功能网元接收来自会话管理网元的第一计费请求消息，所述第一计费请求消息包括第一标识信息和第一信息，所述第一信息包括第一终端设备的第一数据流的使用量，所述第一数据流包括由第一用户面功能网元分流到第二用户面功能网元的所述第一终端设备的数据流；
    所述计费功能网元基于所述第一标识信息和所述第一信息生成所述第一终端设备的第一话单；
    其中，所述第一用户面功能网元用于对第一区域内终端设备的数据流进行分流，所述第一区域为所述第一终端设备签约的专用网络的签约地，所述第二用户面功能网元用于传输所述第一终端设备和数据网络之间的数据，所述第一标识信息用于关联所述第一区域。
  17. 根据权利要求16所述的方法，其特征在于，所述第一计费请求消息还包括所述第二用户面功能网元的标识信息和第二信息，所述第二信息包括所述第二用户面功能网元统计的所述第一终端设备的数据流的使用量。
  18. 根据权利要求17所述的方法，其特征在于，在所述计费功能网元基于所述第一标识信息和所述第一信息生成所述第一终端设备的第一话单之前，所述方法还包括：
    所述计费功能网元从所述第一计费请求消息中拆分出所述第一标识信息和所述第一信息。
  19. 根据权利要求16至18中任一项所述的方法，其特征在于，所述第一计费请求消息还包括第四指示信息，所述第四指示信息指示所述第一数据流为免费的数据流，所述方法还包括：
    所述计费功能网元基于所述第四指示信息，将所述第一终端设备的第一话单存储在第一话单目录，所述第一话单目录为存储免费的数据流的话单目录。
  20. 根据权利要求16至18中任一项所述的方法，其特征在于，所述计费功能网元配置有第一配置信息，所述第一配置信息用于配置免费的数据流的话单处理，所述第一配置信息包括以下至少一种类型的标识信息：
    用户面功能网元的标识信息，位置区域信息，费率组RG信息；
    其中，所述用户面功能网元的标识信息包括至少一个用户面功能网元的标识，所述至少一个用户面功能网元的标识包括所述第一用户面网元的标识，所述位置区域信息包括至少一个区域的位置信息，所述至少一个区域的位置信息包括所述第一终端设备的位置信息，所述费率组信息包括至少一个费率组的信息，所述至少一个费率组RG的包括所述第一区域关联的费率组RG。
  21. 根据权利要求20所述的方法，其特征在于，所述方法还包括：
    所述计费功能网元基于所述第一配置信息，将所述第一终端设备的第一话单存储在第一话单目录， 所述第一话单目录为存储免费的数据流的话单目录。
  22. 根据权利要求16至21中任一项所述的方法，其特征在于，所述第一标识信息包括以下信息中的至少一项：
    所述第一用户面功能网元的标识，所述第一终端设备的位置信息，所述第一区域关联的费率组RG。
  23. 一种通信装置，其特征在于，所述装置包括用于执行如权利要求1至8中任一项所述方法的步骤的单元，或所述装置包括用于执行如权利要求9至15中任一项所述方法的步骤的单元，或所述装置包括用于执行如权利要求16至22中任一项所述方法的步骤的单元。
  24. 一种通信装置，其特征在于，所述装置包括处理器，所述处理器与存储器耦合，所述存储器存储有指令，所述指令被所述处理器运行时，使得所述处理器执行如权利要求1至8中任一项所述的方法，或执行如权利要求9至15中任一项所述的方法，或执行如权利要求16至22中任一项所述的方法。
  25. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质上存储有计算机程序，当所述计算机程序在计算机上运行时，使得所述计算机执行如权利要求1至8中任一项所述的方法，或执行如权利要求9至15中任一项所述的方法，或执行如权利要求16至22中任一项所述的方法。
  26. 一种计算机程序产品，其特征在于，所述计算机程序产品包括：计算机程序代码，当所述计算机程序代码被运行时，实现如权利要求1至8中任一项所述的方法，或执行如权利要求9至15中任一项所述的方法，或执行如权利要求16至22中任一项所述的方法。
PCT/CN2023/126256 2022-11-04 2023-10-24 通信方法与通信装置 WO2024093738A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202211380617.1A CN117998312A (zh) 2022-11-04 2022-11-04 通信方法与通信装置
CN202211380617.1 2022-11-04

Publications (1)

Publication Number Publication Date
WO2024093738A1 true WO2024093738A1 (zh) 2024-05-10

Family

ID=90892325

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/126256 WO2024093738A1 (zh) 2022-11-04 2023-10-24 通信方法与通信装置

Country Status (2)

Country Link
CN (1) CN117998312A (zh)
WO (1) WO2024093738A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105515797A (zh) * 2015-12-15 2016-04-20 福建星网锐捷网络有限公司 一种园区网用户认证计费方法、装置及系统
WO2021018021A1 (zh) * 2019-07-31 2021-02-04 华为技术有限公司 计费方法、计费系统和通信装置
WO2021179598A1 (zh) * 2020-03-09 2021-09-16 华为技术有限公司 通信方法、装置及系统
CN114554538A (zh) * 2022-03-22 2022-05-27 中国电信股份有限公司 流量统计方法、装置、电子设备及存储介质

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105515797A (zh) * 2015-12-15 2016-04-20 福建星网锐捷网络有限公司 一种园区网用户认证计费方法、装置及系统
WO2021018021A1 (zh) * 2019-07-31 2021-02-04 华为技术有限公司 计费方法、计费系统和通信装置
WO2021179598A1 (zh) * 2020-03-09 2021-09-16 华为技术有限公司 通信方法、装置及系统
CN114554538A (zh) * 2022-03-22 2022-05-27 中国电信股份有限公司 流量统计方法、装置、电子设备及存储介质

Also Published As

Publication number Publication date
CN117998312A (zh) 2024-05-07

Similar Documents

Publication Publication Date Title
US11606734B2 (en) Handover method in wireless communication system and apparatus therefor
US20220345929A1 (en) Apparatus and method for psa-upf relocation in wireless communication system
TW201406191A (zh) 支援鄰近發現程序方法及裝置
WO2011050737A1 (zh) 一种实现本地接入的方法及系统
WO2021212439A1 (zh) 一种通信方法及装置
WO2021196185A1 (zh) 无线通信方法、终端设备和网络设备
WO2010003359A1 (zh) 区别用户计费规则的计费方法和系统
WO2022110214A1 (zh) 通信方法及装置
WO2021238331A1 (zh) 获取网络资源的方法、设备及系统
CN102332985A (zh) 一种提供基于lipa承载的计费支持的方法及装置
WO2024093738A1 (zh) 通信方法与通信装置
WO2022002119A1 (zh) 一种通信方法及装置
WO2022170543A1 (zh) 一种组播/广播业务的通信方法和装置
CN115484582A (zh) 通信方法和通信装置
CN116723467A (zh) 无线通信的方法和网络设备
TWI833316B (zh) 通信方法、裝置、電腦可讀存儲介質、電腦程式產品以及通信系統
WO2024114288A1 (zh) 接入网络的方法和通信装置
WO2023207958A1 (zh) 策略传输的方法、通信装置和系统
WO2022262608A1 (zh) 一种计费方法、用户设备及网络侧设备
WO2023160199A1 (zh) 一种接入通信网络的方法和装置
KR20150024689A (ko) 이벤트 기반의 단말 위치정보 획득 방법 및 그 장치
WO2022170588A1 (zh) 一种通信的方法和通信装置
WO2023213132A1 (zh) 一种网络切片的通信方法、通信装置、接入网设备和终端设备
WO2022042553A1 (zh) 一种定位业务计费方法及装置
WO2023138452A1 (zh) 通信方法、装置及系统