WO2023050787A1 - 一种计费方法和装置 - Google Patents

一种计费方法和装置 Download PDF

Info

Publication number
WO2023050787A1
WO2023050787A1 PCT/CN2022/089213 CN2022089213W WO2023050787A1 WO 2023050787 A1 WO2023050787 A1 WO 2023050787A1 CN 2022089213 W CN2022089213 W CN 2022089213W WO 2023050787 A1 WO2023050787 A1 WO 2023050787A1
Authority
WO
WIPO (PCT)
Prior art keywords
roaming
charging
information
roaming charging
service
Prior art date
Application number
PCT/CN2022/089213
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 WO2023050787A1 publication Critical patent/WO2023050787A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403—Architecture for metering, charging or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403—Architecture for metering, charging or billing
    • H04L12/1407—Policy-and-charging control [PCC] architecture
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/50—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP for cross-charging network operators
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/61—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP based on the service used
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/62—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP based on trigger specification
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/64—On-line charging system [OCS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/65—Off-line charging system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/66—Policy and charging system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/70—Administration or customization aspects; Counter-checking correct charges
    • H04M15/73—Validating charges
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/80—Rating or billing plans; Tariff determination aspects
    • H04M15/8016—Rating or billing plans; Tariff determination aspects based on quality of service [QoS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/80—Rating or billing plans; Tariff determination aspects
    • H04M15/8038—Roaming or handoff
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/82—Criteria or parameters used for performing billing operations
    • H04M15/8228—Session based

Definitions

  • the present application relates to the technical field of communications, and in particular to a charging method and device.
  • the current roaming settlement adopts the international roaming settlement process TAP (Transferred Account Procedure) defined by GSMA. And TAP generates a detailed list according to the transfer data of each piece, or the transfer data of each minute, or the transfer data of each message. Therefore, the TAP method for roaming clearing results in a very large amount of data, which cannot meet the real-time requirements of the fifth generation (Fifth Generation, 5G) mobile communication technology business, and cannot be applied to small traffic data services such as IOT.
  • TAP Transferred Account Procedure
  • BCE Billing and Charging Evolutio
  • the clearing, reconciliation, and conflict resolution between the visited network and the home network are based on the BCE process.
  • the billing information collected by the visited network and the home network is the basis for generating detailed data recording (DDR) in roaming scenarios.
  • DDR detailed data recording
  • 5G has various business requirements, so DDR for roaming settlement of 5G services also has various requirements.
  • the current roaming settlement method between the visited network and the home network is based on BCE.
  • the DDR file generated by the visited network cannot support roaming settlement, account reconciliation, and conflict resolution, and thus cannot meet various service settlement needs.
  • the embodiment of the present application provides a charging method and device, so that in the roaming charging scenario, the roaming charging information reported for the user data connection session can meet the needs of various services, and support the roaming settlement of the visited network and the home network , reconciliation, and conflict resolution.
  • the first aspect of the embodiment of the present application provides the following technical solutions including: after the charging trigger device determines that the user corresponding to the data connection session is a roaming user, obtain roaming charging configuration information, and the roaming charging configuration information includes roaming charging Information granularity indication, service information, roaming multi-user plane function reporting indication, roaming multi-access data connection session reporting indication, and/or reporting conditions of roaming charging information.
  • the charging triggering device According to the roaming charging information granularity indication, service information, roaming multi-user plane function reporting indication, roaming multi-access data connection session reporting indication, and/or roaming charging information reporting conditions, the charging triggering device generates a roaming accounting data connection session. fee information. The charging triggering device reports roaming charging information to the roaming charging system.
  • the roaming charging configuration information is expanded to include roaming charging information granularity indication, service information, roaming multi-user plane function reporting indication, roaming multi-access data connection session reporting indication, and/or roaming charging information Reporting conditions, so that roaming charging information that supports various settlement requirements can be generated according to the roaming charging profile. It enables the roaming charging system to perform flexible roaming settlement according to different roaming charging configuration information, and provides data support for conflict resolution when a conflict occurs.
  • the granularity indication of roaming charging information can ensure that the granularity of the charging information of the user in the visited network and the home network is synchronized, thereby satisfying roaming settlement between different operators for user groups according to the granularity of service quality. Or liquidation according to the granularity of the business or low-cost liquidation of the total traffic at the granularity of the data connection session and other different business needs.
  • roaming settlement can be performed for specific services (such as MEC services) or specific types of services (such as IoT small traffic services), so that roaming settlement capabilities between operators can better support roaming of specific industries and customers need.
  • specific services such as MEC services
  • specific types of services such as IoT small traffic services
  • the operator can more accurately perform roaming settlement based on the use of network resources, realize real payment according to the use of network resources, and make the roaming settlement capability more refined to meet different settlements. need.
  • the roaming information of fixed network access and mobile access can be distinguished, thereby better supporting the accurate settlement capability of the fixed network and mobile convergence network roaming network, and avoiding the combination of fixed access and mobile access. Packing mobile access together for liquidation will cause losses to the visited network (when the user uses more mobile access on the visited network) or the home network (when the user uses more fixed access on the visited network).
  • roaming charging information it is possible to flexibly divide roaming charging information according to a specified time point, thereby supporting more flexible settlement cycles (such as settlement by day, week, month, quarter, etc.) .
  • the charging triggering means determining that the user corresponding to the PDU data connection session is a roaming user includes: the charging triggering means determining that the user is a roaming user according to the user's home network identifier reported by the user equipment. By being able to determine that the user is a roaming user according to the user's home network identifier reported by the user equipment, it is more accurate to determine that the user is a roaming user.
  • acquiring the roaming charging configuration information of the user includes: the charging triggering means acquires the roaming charging configuration information configured in the charging triggering means as the roaming charging configuration information.
  • acquiring the roaming charging configuration information of the user includes: the charging triggering device receives the roaming charging configuration information sent by the roaming charging system.
  • the charging triggering device uses the roaming charging configuration information sent by the roaming charging system as the roaming charging configuration information.
  • the roaming charging configuration information is obtained through the roaming charging system, so that the method for obtaining the roaming charging configuration information of the user is more flexible and diversified.
  • the indication of the granularity of the roaming charging information is: an indication at the granularity of a quality of service flow (QoS Flow), an indication at the granularity of a service, or an indication at the granularity of a data connection session.
  • QoS Flow quality of service flow
  • the charging information corresponding to the QoS Flow is included in the roaming charging interest calculation.
  • the charging information corresponding to the service is included in the roaming charging interest calculation.
  • the charging information corresponding to the data connection session is included in the charging information of the roaming charging.
  • the roaming charging configuration information is extended to include roaming charging information granularity indication, so that the roaming charging information supporting various settlement requirements can be generated according to the roaming charging profile. It enables the roaming charging system to perform flexible roaming settlement according to different roaming charging configuration information, and provides data support for conflict resolution when a conflict occurs.
  • the charging information corresponding to the service when the roaming charging information granularity indicates the service granularity, includes the usage amount of the service corresponding to the rate group in the data connection session, or the data connection session The usage amount of the service corresponding to the service identifier in the data connection session, or the usage amount of the service corresponding to the service type in the data connection session, or the usage amount of the service corresponding to the rate group and the service identifier in the data connection session.
  • the charging information corresponding to the service is based on the granularity of the roaming charging information, so that the charging information based on the service can be provided, and various charging requirements of the roaming charging system can be met.
  • the roaming charging information granularity is an indication based on a service granularity
  • the roaming charging configuration information further includes service-related information
  • the service-related information includes a service type, a rate group, and/or a service identifier
  • Roaming charging and interest calculation further includes service type, rate group, and/or service identifier.
  • the granularity of the roaming charging information is an indication of the granularity of the service and the roaming charging configuration information also includes service-related information, so that service-based charging information can be provided to meet various charging requirements of the roaming charging system.
  • the roaming charging configuration information when the charging triggering device is the charging triggering device of the visited network, the roaming charging configuration information further includes the network slice identifier of the home network corresponding to the data connection session; and/or
  • the roaming charging configuration information also includes the reporting indication of the multi-user plane function UPF, and the roaming charging information also includes the charging information reported by each user plane function of the data connection session or the charging information reported by multiple UPFs including the data connection session consolidated billing information; and/or
  • the roaming charging configuration information includes the reporting indication of multiple access data connection sessions, and the roaming charging information includes the charging information corresponding to each access of the data connection session or the combination of charging information corresponding to multiple accesses in the data connection session subsequent billing information.
  • the roaming charging configuration information includes the above-mentioned multiple information, so that the roaming charging information based on the roaming charging configuration information can be provided, and various charging requirements of the roaming charging system can be met.
  • the network slice identification can support liquidation according to network slices, and different usage fees can be used for different slices (such as slices of different types and different quality requirements), so as to avoid the loss of the visited network operator and the home network operator. Basically reduce the slice usage cost.
  • generating the roaming charging information includes: the charging triggering device determines that the roaming charging information reporting condition is met, generates the roaming charging information, and Report roaming charging information to the roaming charging system.
  • the embodiment of the present application provides a roaming charging method, including: the roaming charging system receives the charging resource creation request of the user's data connection session sent by the charging trigger device, and the charging resource creation request includes the user's Data connection session information.
  • the roaming charging system generates second roaming charging configuration information, the second roaming charging configuration information includes roaming charging information granularity indication, service information, roaming multi-user plane function reporting indication, roaming multi-access data connection session reporting indication , and/or roaming charging information reporting conditions;
  • the roaming charging system sends the second roaming charging configuration information to the charging triggering device.
  • the roaming charging information sent by the charging triggering device is received, and the roaming charging information is generated according to the second roaming charging configuration information sent by the roaming charging system.
  • the roaming charging configuration information is expanded to include roaming charging information granularity indication, service information, roaming multi-user plane function reporting indication, roaming multi-access data connection session reporting indication, and/or roaming charging information Reporting conditions, so that roaming charging information that supports various settlement requirements can be generated according to the roaming charging profile. It enables the roaming charging system to perform flexible roaming settlement according to different roaming charging configuration information, and provides data support for conflict resolution when a conflict occurs.
  • the charging resource creation request includes first roaming charging configuration information
  • the first roaming charging configuration information includes roaming charging information granularity indication, service information, roaming multi-user plane function reporting indication, The reporting indication of the roaming multi-access data connection session, and/or the reporting condition of roaming charging information
  • the second roaming charging configuration information is used by the charging triggering device to update the first roaming charging configuration information in the charging triggering device.
  • the roaming charging system can update the roaming charging configuration information, so that the roaming charging configuration information can better meet the charging service requirements of the roaming charging system.
  • the roaming charging system determines to generate the second roaming charging configuration information for updating the first roaming charging configuration information .
  • the roaming charging system determines to update the roaming charging configuration information, so that the roaming charging configuration information can better meet the charging service requirements of the roaming charging system.
  • the roaming charging system generates a charging data record (CDR) of the user, and the charging data record includes roaming charging information.
  • CDR charging data record
  • the CDR generated by the roaming charging system includes roaming charging information, so that the roaming charging information meets the charging service requirements of the roaming charging system.
  • the charging information corresponding to the QoS Flow is included in the roaming charging interest calculation, and then the billing bill includes the charging information corresponding to the QoS Flow; or, the roaming charging interest calculation includes the charging information corresponding to the service corresponding charging information, the billing bill includes the billing information corresponding to the service; fee information.
  • the charging bill includes charging information of different granularities, so that the roaming charging system can perform flexible roaming settlement according to different roaming charging configuration information, and provides data support for conflict resolution when a conflict occurs.
  • the roaming charging information when the charging triggering device is the charging triggering device of the visited network, the roaming charging information includes the network slice identifier of the home network corresponding to the data connection session, and the charging bill includes the network slice identifier of the home network Network slice identifier.
  • the charging bill includes the network slice identifier of the home network, so that the roaming charging information meets the requirements of the roaming charging system for charging services related to the network slice.
  • the roaming charging system generates detailed data records, which include detailed data records corresponding to QoS Flow or detailed data records corresponding to services or detailed data records corresponding to data connection sessions, detailed data records Records are generated based on billing records.
  • the detailed data record includes the detailed data record corresponding to the QoS Flow or the detailed data record corresponding to the service or the detailed data record corresponding to the data connection session, so that the roaming charging system can realize charging or service based on the QoS Flow Billing to meet different business needs.
  • a roaming charging device in a third aspect, is provided, and the device body has the function of a charging trigger device for implementing the method in the first aspect.
  • This function may be implemented by hardware, or may be implemented by executing corresponding software on the hardware.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • a roaming charging device including: a processor and a memory; the memory is used to store computer-executable instructions, and when the device is running, the processor executes the computer-executable instructions stored in the memory, so that The device executes the method according to any one of the first aspect above.
  • the device may be a chip in the billing trigger device involved in any one of the methods in the first aspect.
  • a computer-readable storage medium stores instructions, and when it is run on a computer, the computer can execute the roaming charging method in any one of the above-mentioned first aspects .
  • a computer program product containing instructions is provided, and when it is run on a computer, the computer can execute the roaming charging method in any one of the above first aspects.
  • the technical effect brought by any one of the design methods in the second aspect to the sixth aspect can refer to the technical effect brought by different design methods in the first aspect, which will not be repeated here.
  • a roaming charging system has a function of implementing the second method above.
  • This function may be implemented by hardware, or may be implemented by executing corresponding software on the hardware.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • a roaming charging system including: a processor and a memory; the memory is used to store computer-executable instructions, and when the device is running, the processor executes the computer-executable instructions stored in the memory, so that The device executes any one of the methods in the second aspect above.
  • a computer-readable storage medium is provided, and instructions are stored in the computer-readable storage medium, and when the computer-readable storage medium is run on a computer, the computer can execute the charging method in any one of the above-mentioned second aspects.
  • a computer program product containing instructions, which, when run on a computer, enable the computer to execute the roaming charging method in any one of the above-mentioned second aspects.
  • a system including a charging trigger device and a roaming charging system.
  • the control plane function may perform the processing performed by the charging trigger device in any of the above aspects.
  • the roaming charging system can perform the processing performed by the charging function in any of the above aspects.
  • FIG. 1A is a schematic structural diagram of a roaming charging system provided by an embodiment of the present application.
  • FIG. 1B is a schematic diagram of a network structure for implementing roaming under the HR roaming scenario provided by the embodiment of the application;
  • FIG. 2 is a schematic diagram of a hardware structure of a communication device provided by an embodiment of the present application
  • FIG. 3 is a schematic flowchart of a method for charging in a roaming scenario provided by an embodiment of the present application
  • FIG. 4 is a schematic flowchart of a charging method based on an HR roaming scenario provided by an embodiment of the present application
  • Fig. 5 is a schematic structural diagram of the device provided by the embodiment of the present application.
  • Fig. 6 is a schematic structural diagram of the device provided by the embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of a system provided by an embodiment of the present application.
  • the network architecture and business scenarios described in the embodiments of the present invention are to more clearly illustrate the technical solutions of the embodiments of the present invention, and do not constitute limitations on the technical solutions provided by the embodiments of the present invention.
  • the evolution of the architecture and the emergence of new business scenarios, the technical solutions provided by the embodiments of the present invention are also applicable to similar technical problems.
  • Multiple means two or more.
  • “And/or” describes the association relationship of associated objects, indicating that there may be three types of relationships, for example, A and/or B may indicate: A exists alone, A and B exist simultaneously, and B exists independently.
  • the character “/” generally indicates that the contextual objects are an "or” relationship.
  • User device a device for an end user; the device may have wireless communication capabilities to connect to wireless access devices through an air interface, or may have wired communication capabilities to connect to wired access devices through a wired interface; From the perspective of product form, the device can be a smartphone, a laptop with wireless communication function (Laptop), a tablet, a wearable device, an AR (Augmented Reality, augmented reality) device, an IoT (Internet of Things, everything Internet) equipment, desktop computers on office desks, etc.; this equipment can consume application services provided by application servers in the data network through data connection sessions.
  • Laser wireless communication function
  • IoT Internet of Things, everything Internet
  • the user equipment may include UE (user equipment, user equipment) functions defined in 3GPP standard specifications, such as the UE in the subsequent figures.
  • UE user equipment, user equipment
  • Roaming user equipment User equipment in a roaming state.
  • Operator network the communication network of the operator where the user equipment is visiting; the embodiment of the present application assumes that the user equipment has roamed into the operator network, so that the user equipment is an in-bound roamer of the operator network , the operator's network is the visited network of the user equipment, referred to as "visited network”.
  • Data Network used to transmit data, a network composed of data switches as transit points, such as the Internet (Internet), which contains at least one application server (not shown in the figure), which is the user equipment Provide application services; usually use DNN (data network name, data network name) as the identifier of the data network.
  • Internet Internet
  • application server not shown in the figure
  • DNN data network name, data network name
  • Data connection session It is an association between the user equipment and the data network, which is used to provide connection services for the communication between the user equipment and the data network, so that the communication data packet (Packet) can be transmitted between the user equipment and the data network.
  • the creation process can be initiated by the user equipment, and the teardown process can be initiated by the user equipment or other equipment (such as a user plane data gateway).
  • the data connection session can be an IP-CAN (IP-connectivity access network, IP connectivity access network) session or a protocol data unit session (protocol data unit session, PDU session) defined by the 3GPP standard specification, or it can be another form of session , which is not limited in this embodiment of the present application.
  • the data connection session may be a protocol data unit session applicable to a 5G network, or may be another session applicable to another network, which is not limited in this embodiment of the present application.
  • User plane data gateway Provide support services for data connection sessions (for example, transmit data packets from user equipment to the data network through the user plane data gateway, or transmit data packets from the data network through the user plane data gateway to The core network element of the user equipment).
  • the user plane data gateway collects charging information related to data connection sessions (such as service unit usage) according to the configuration parameters of the collection operation, and provides the collected charging information to the charging trigger device; wherein, the configuration parameters of the collection operation can be in the user
  • the local default configuration of the data gateway on the user plane may also be sent to the data gateway on the user plane by the charging trigger device.
  • the user plane data gateway can include the functions of UPF (user plane function, user plane function) equipment defined in the 3GPP standard specification, the function of PGW-U (packet data network gateway for user plane, user plane packet data gateway) or the function of SGW-U ( serving gateway for user plane, user plane service gateway) functions, etc.
  • the user plane data gateway may be a user plane function UPF applicable to a 5G network architecture, or a network element applicable to other network architectures, which is not limited in this embodiment of the application.
  • the UPF under the 5G network architecture as the user plane data gateway is used as an example for illustration.
  • Roaming charging information refers to the charging information related to the data connection session in the roaming scenario, which can be the charging information related to the roaming data connection session collected by the charging trigger device of the visited network, or it can be the charging information of the home network Charging information related to roaming data connection sessions collected by the trigger device.
  • Roaming charging configuration parameters refer to configuration parameters related to the operation of roaming charging information
  • the operations include collecting operations and/or reporting operations
  • the collecting operations refer to collecting roaming charging information from roaming data connection sessions
  • the reporting operation refers to sending the collected roaming charging information to the corresponding charging processing device; therefore, the roaming charging configuration parameters include collecting operation configuration parameters and/or reporting operation configuration parameters; when one or more roaming charging
  • the configuration parameters are shared or synchronized between the home network and the visited network, the synchronization and consistency between the charging processing results of the two parties on the same roaming data connection session can be improved, thereby reducing cross-network (that is, cross-operator network ) error during liquidation.
  • the collection operation configuration parameter is a configuration parameter related to the collection operation of charging information, which is used to enable the user plane data gateway to determine how to collect roaming charging information for the roaming data connection session;
  • HR Roaming The media route does not select local forwarding, but the route returns to the home network and is transferred through the home network. In HR roaming mode, all traffic passes through the visited network and the home network.
  • LBO Local Breakout
  • Multiple access PDU Session refers to a PDU session that provides PDU connection services.
  • the PDU session can be used for one type of access at a certain time, or can support multiple different accesses at the same time (for example, support 3GPP access and non-3GPP access).
  • Multi-user plane function means that a PDU session involves multiple UPFs.
  • a roaming UE refers to a UE that moves to the local network (referring to the visited network) but belongs to another operator's network.
  • QoS Flow is the smallest granularity of QoS forwarding treatment (finest granularity) in the communication system. All traffic mapped to the same QoS Flow will receive the same forwarding treatment (such as scheduling policy, queue management policy, rate policy, etc.).
  • the communication system provides different QoS forwarding processing and needs to use different QoS Flow. If other communication systems use the same concept as QoS Flow, the method of this application is still applicable.
  • FIG. 1A is a roaming charging system provided by an embodiment of the present application.
  • the system includes a charging trigger device 110 and a roaming charging system 120 .
  • the charging triggering device and roaming charging system may be network equipment of the home network, or the charging triggering device and roaming charging system may also be network equipment of the visited network, and this application does not limit the interaction in other home forms.
  • the charging triggering device 110 is used to obtain roaming charging configuration information, update the roaming charging configuration information according to the roaming charging configuration update information issued by the roaming charging system, and generate roaming charging information according to the roaming charging configuration information.
  • the charging triggering device 110 is also configured to send the generated roaming charging information to the roaming charging system 120 .
  • the charging trigger device may be a network element under the 5G system architecture.
  • the charging trigger device can be set in the session management function SMF in the 5G network, or in the access and mobility management function (Access and Mobility Management Function, AMF) in the 5G network.
  • the roaming charging system 120 may be a charging function CHF or a converged charging system (Converged Charging System, CCS) in the 5G network, or other entities including roaming bill generation and roaming charging processing functions.
  • the roaming charging system can also be a charging function CHF or a converged charging system (Converged Charging System, CCS), or other entities including roaming bill generation and roaming charging processing functions.
  • the roaming charging system 120 is configured to generate a roaming charging bill (Charging Data Record, CDR) according to the roaming charging information sent by the charging trigger device, and generate a detailed data record (Detail Data Record, DDR) according to the roaming CDR.
  • the charging triggering device and roaming charging system in this application are not limited to the 5G network architecture, but can be applied to any network architecture and support roaming charging scenarios.
  • the follow-up content of this application is described by taking the charging trigger device set in the session management function in the 5G network architecture, or taking the charging trigger device as an SMF in the 5G network architecture as an example.
  • the charging triggering device and roaming charging system in this application are not limited to the 5G network architecture, but can be applied to any network architecture and support roaming charging scenarios.
  • the follow-up content of this application is described by taking the charging trigger device set in the session management function in the 5G network architecture, or taking the charging trigger device as an SMF in the 5G network architecture as an example. That is to say, the charging triggering device in FIG. 1A is used to execute corresponding operations of the session management function of the visited network in FIG. 1B to FIG. 5 .
  • the roaming charging system in FIG. 1A is used to execute corresponding operations of the roaming charging system (including V-CHF) of the visited network or the roaming charging system (including H-CHF) of the home network in FIG. 1B to FIG. 5 .
  • FIG. 1B is a schematic diagram of a network structure for implementing roaming in an HR roaming scenario provided by the embodiment of the application.
  • the network structure includes a home Public Land Mobile Network (HPLMN) and a visited Public Land Mobile Network (VPLMN).
  • HPLMN home Public Land Mobile Network
  • VPNLMN visited Public Land Mobile Network
  • the home public land mobile network is referred to as the home network
  • the visited public land mobile network is referred to as the visited network.
  • the UPF 103-1 of the visited network communicates with the UPF 103-2 of the home network, and sends the uplink service data flow of the user accessing the visited network to UPF 103-2 of the home network, or receives it from UPF 103-2. User's downlink service data flow.
  • the SMF101-1 of the visited network generates roaming charging information according to the information (such as traffic information, or duration information) sent by the UPF103-1 of the visited network to access the service data flow used by the user to access the visited network, and sends it to the included roaming charging system ( Including the charging function V-CHF of the visited network).
  • the SMF101-2 of the home network generates roaming charging information according to the service data flow information sent by the UPF103-2 of the home network to access the visited network and sends it to the roaming charging system (including the charging function H-CHF of the home network) .
  • the roaming charging system including the charging function V-CHF of the visited network and the roaming charging system including the charging function H-CHF of the home network are used to process the roaming charging information of the user sent by the SMF in their respective networks, For example, generate a roaming bill for a user in a roaming scenario.
  • the roaming charging system 102-1 of the visited network may be V-CHF or include V-CHF.
  • the roaming charging system 102-2 of the home network may be H-CHF or include H-CHF.
  • the roaming charging system 102-1 of the visited network generates a DDR according to the user's roaming CDR generated by the V-CHF, and generates a usage data report (Usage Data Report, UDR) according to the user's DDR.
  • UDR Usage Data Report
  • the roaming charging system 102-2 of the home network generates a roaming DDR according to the user's roaming CDR generated by the H-CHF, and generates a usage data report according to the user's
  • the SMF 101-1 of the visited network communicates with the SMF 101-2 of the home network to establish a PDU session for the user and update the roaming charging configuration information of the user.
  • the SMF101-1 of the visited network sends the roaming charging configuration information of the user to the SMF101-2 of the home network, and obtains the updated roaming charging configuration information of the user from the SMF101-2 of the home network.
  • the roaming charging system 102-1 of the visited network and the roaming charging system 102-2 of the home network communicate with each other, and exchange the user's UDR generated by each to perform fee settlement.
  • FIG. 2 is a schematic diagram of a hardware structure of a communication device provided by an embodiment of the present application.
  • the communication device 200 includes at least one processor 201 , a communication line 202 , a memory 203 and at least one communication interface 204 .
  • the processor 201 can be a general-purpose central processing unit (central processing unit, CPU), a microprocessor, a specific application integrated circuit (application-specific integrated circuit, ASIC), or one or more for controlling the execution of the program program of this application integrated circuit.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • Communication line 202 may comprise a pathway for communicating information between the above-described components.
  • the communication interface 204 uses any device such as a transceiver for communicating with other devices or communication networks, such as Ethernet and the like.
  • Memory 203 may be read-only memory (read-only memory, ROM) or other types of static storage devices that can store static information and instructions, random access memory (random access memory, RAM) or other types that can store information and instructions It can also be an electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be programmed by a computer Any other medium accessed, but not limited to.
  • the memory may exist independently and be connected to the processor through the communication line 202 . Memory can also be integrated with the processor.
  • the memory 203 is used to store computer-executed instructions for implementing the solution of the present application, and the execution is controlled by the processor 201 .
  • the processor 201 is configured to execute computer-executed instructions stored in the memory 203, so as to implement the session establishment method provided in the following embodiments of the present application.
  • the computer-executed instructions in the embodiments of the present application may also be referred to as application program codes, which is not specifically limited in the embodiments of the present application.
  • the processor 201 may include one or more CPUs.
  • the communication device 200 may include multiple processors, for example, the processor 201 and the processor 208 in FIG. 2 .
  • Each of these processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor.
  • a processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (eg, computer program instructions).
  • the communication device shown in FIG. 2 may be the SMF or the roaming charging system in the embodiment of the present application.
  • FIG. 3 is a schematic flowchart of a method for charging in a roaming scenario provided by an embodiment of the present application.
  • roaming may be roaming based on an HR scenario, or roaming based on an LBO scenario.
  • a policy control and charging rule for the session where the PCF sends the PDU to the SMF may also be included.
  • the PCC rule includes information about a rating group (rating group, RG) and a service data flow corresponding to the rate group, or the PCC rule includes a service identifier and information about a service data flow corresponding to the service identifier. Or the PCC rule includes the rate group, the service identifier and the information of the service data flow corresponding to the rate group.
  • the PCF may be the PCF of the visited network (ie V-PCF).
  • V-PCF determines that the user is a roaming user
  • it generates a PCC rule for the roaming user's session (such as a PDU session) based on the roaming protocol.
  • the V-PCF can obtain the charging policy parameters of the roaming user from the PCF of the home network (that is, the H-PCF), and based on the acquired charging policy parameters of the roaming user
  • the policy parameter generates the PCC rule for the session of the roaming user.
  • the charging policy parameters of the roaming user include: rate group, service identifier, and/or information of service data flow corresponding to the rate group.
  • V-PCF determines that the user is a roaming user, and this embodiment of the present application will not describe it in detail here.
  • the PCF may not send information about the rating group (RG) and the service data flow corresponding to the rate group to the SMF, or the PCC rule does not include the service identifier and the service data flow corresponding to the service identifier information.
  • Step 302 the SMF obtains roaming charging configuration information (Roaming Charging Profile) corresponding to the roaming user.
  • Roaming Charging Profile a roaming charging configuration information
  • SMF can be V-SMF or H-SMF.
  • the following SMF uses V-SMF, and the roaming charging system is V-CHF as an example for illustration.
  • the roaming charging configuration information is also called roaming charging Profile.
  • the SMF determines that the user is a roaming user. Specifically, the SMF determines according to the user's home network identity (that is, the home network PLMN identity) and the SMF's network identity (that is, the SMF's home PLMN identity) reported by the user equipment. If the user's home network identity is different from the SMF's network identity, then It is determined that the user equipment is a roaming user equipment.
  • the method for the SMF to obtain roaming charging configuration information includes the following methods:
  • Method 1 Configure the roaming charging configuration information of the visited network user on the SMF, and the SMF obtains the roaming charging profile corresponding to the roaming user according to the configured roaming charging configuration information.
  • Method 2 The SMF receives the roaming charging profile sent by the roaming charging configuration information update of the visited network or the home network, and then obtains the roaming charging profile corresponding to the roaming user.
  • the update of the roaming charging configuration information may be the visited network charging function (V-CHF) or the home network charging function (H-CHF), or other charging configuration information that can be updated.
  • the roaming charging profile includes one or more parameters in the following roaming parameter list:
  • Indication of the granularity of the roaming charging information indicating the granularity of the acquired roaming charging information.
  • the granularity of the roaming charging information may be an indication at a granularity of a quality of service flow (QoS flow), an indication at a granularity of a service (service), or an indication at a granularity of a PDU session.
  • An example of this indication is the "Roaming charging info level" parameter in Table 1.
  • Table 1 only shows the indication that the granularity of the roaming charging information is service.
  • the roaming charging profile also includes trigger information corresponding to different roaming charging information granularities.
  • the trigger information includes: a trigger name (trigger type), a trigger type (trigger category), and/or a limit value (limit) of a specific trigger.
  • the roaming charging Profile may further include service information.
  • the service information includes: the rate group of the service, the service identifier of the service, the service type of the service, and/or other information of the service.
  • Service information is used to indicate the collection of roaming charging information for services corresponding to service types, service roaming charging information corresponding to rate groups, roaming charging information for services corresponding to service identifiers, or service information is used to indicate collection Service type, rate group, and roaming charging information of the service corresponding to the service identifier.
  • the indication of the granularity of the roaming charging information is the indication of the granularity of the service, and the roaming charging configuration information does not include the information of the service, it is instructed to collect the roaming charging information for the services corresponding to all the rate groups.
  • the rate group is the rate group ID corresponding to the service in the PDU session
  • the service ID is the service ID corresponding to the service in the PDU session
  • the service type is the service type corresponding to the service in the PDU session
  • other information of the service is the service corresponding to the service.
  • the identification rules of the business data flow (namely: flow characteristic information).
  • flow characteristic information For business information, please refer to the information included in the service info in Table 1.
  • the service info in Table 1 includes: rating group (rate group), service ID (service identification), service type (service type), flow information (flow information) feature).
  • the SMF can obtain the flow characteristics corresponding to the rate group or service identifier in other ways (for example, it can be obtained through the PCC rule issued by the PCF, if the PCF is a vPCF, after the V-PCF determines that the user is a roaming user, The roaming user's rate group/service ID and corresponding flow feature information can be obtained from the PCF of the home network, and the generated roaming user's PCC rule includes the rate group or service ID corresponding to the flow feature), then the roaming parameter does not include stream feature information.
  • This indication information is used to indicate whether the charging information reported by each UPF needs to be written in the roaming charging information when the PDU session uses multiple UPFs (refer to Table 1 perUPF). For example, it indicates that the roaming charging information includes the charging information reported by each interface function of the PDU session, or includes the charging information after combining the charging information reported by multiple UPFs of the PDU session.
  • Roaming multi-access PDU session reporting indication If the PDU session is a multi-access PDU session (MA PDU SESSION, for example: a PDU session has multiple access technologies at the same time, for example, the same PDU session uses 3GPP access and non-3GPP access at the same time access), it may also carry multi-PDU session roaming charging indication information (refer to maPDUSupport in Table 1). The indication information is used to indicate whether the roaming charging information carries the charging information of each access mode separately, or carries the charging information combined with the charging information corresponding to multiple accesses in the PDU session.
  • MA PDU SESSION for example: a PDU session has multiple access technologies at the same time, for example, the same PDU session uses 3GPP access and non-3GPP access at the same time access
  • multi-PDU session roaming charging indication information (refer to maPDUSupport in Table 1).
  • the indication information is used to indicate whether the roaming charging information carries the charging information of each access mode separately, or carries the
  • Roaming charging information reporting conditions Instruct the SMF to report the roaming charging information reporting conditions to the roaming charging system (such as the reporting time point, refer to ReportTime in Table 1), so as to ensure that the roaming charging information can be generated when DDR is generated, etc. Accurate segmentation. For example, if roaming settlement needs to be settled on a daily basis, you can specify to report once at 24:00 every day, and if roaming settlement needs to be settled on a monthly basis, you can specify to report once at 24:00 on the last day of each month.
  • Table 1 is an example of roaming charging configuration information.
  • the roaming charging configuration information shown in Table 1 includes trigger (trigger) information, which is used to indicate to report to the roaming charging system.
  • the granularity is business or QoS Flow granularity, or PDU session granularity.
  • the trigger information shown in Table 1 includes parameters: trigger type, trigger category, time limit, and/or volume limit. For the meaning of the parameters included in the trigger information, refer to the explanation of the corresponding parameters in Table 1.
  • the roaming charging configuration information shown in Table 1 may also include an indication of the granularity of the roaming charging information (Roaming charging in for level).
  • the indication of the granularity of the roaming charging information may be an indication of the granularity of the quality of service flow (QoS Flow), an indication of the granularity of the service, or an indication of the granularity of the protocol data unit session.
  • QoS Flow quality of service flow
  • the indication parameter of granularity is an explicit indication. In another implementation, the indication of the granularity of the roaming charging information may also be an implicit indication.
  • the roaming charging profile does not carry the Roaming charging info level parameter, but the roaming charging profile directly carries the roaming charging configuration information parameters with service as the granularity (such as Service Info in Table 1), indicating the roaming charging information
  • the granularity is based on the business.
  • the roaming charging configuration information shown in Table 1 may also include a service granular roaming charging configuration information parameter (Service Info) parameter group.
  • the Service Info group parameter can be independent of the indication of the granularity of the roaming charging information (Roaming charging in for level), and can also be used as a value of the indication of the granularity of the roaming charging information (Roaming charging in for level). That is to say, the Service Info group parameter in Table 1 can be juxtaposed with the Roaming charging infor level parameter, and can also be combined with the Roaming charging infor level parameter (that is, the Roaming charging infor level parameter includes the service info parameter).
  • the service information (Service Info) in Table 1 may include rating group (rate group), service identifier (service ID), service type, and/or Flow Information.
  • the rating group (rate group) and/or service ID (service ID) are used to identify a service, and the service type is used to identify a type of service.
  • Flow Information is used to identify the flow characteristics of the business data flow of the business.
  • the roaming charging configuration information in Table 1 is the roaming charging configuration information of the service identified by the rating group or service ID of the user. If the service information (Service Info) includes rating group or service ID parameters, and also includes flow information, then the flow feature in the flow information parameter is the flow feature of the service identified by the rating group or service ID parameter.
  • the roaming charging configuration information shown in Table 1 may also include a per UPF parameter, which refers to whether the charging information reported by each UPF is reported to the roaming charging system separately when the user’s PDU session uses multiple UPFs, or whether each UPF The charging information reported by the UPF is combined and reported to the roaming charging system.
  • a per UPF parameter refers to whether the charging information reported by each UPF is reported to the roaming charging system separately when the user’s PDU session uses multiple UPFs, or whether each UPF The charging information reported by the UPF is combined and reported to the roaming charging system.
  • the roaming charging configuration information shown in Table 1 may also include the two parameters of multi-access reporting indication or roaming charging information reporting condition.
  • these two parameters please refer to the introduction of 6 or 7 of the aforementioned parameters.
  • the embodiments of the present application will not be described in detail here.
  • Step 304 The SMF generates roaming charging information according to the roaming charging configuration information.
  • SMF can be V-SMF or H-SMF.
  • the following SMF uses V-SMF as an example.
  • both the V-SMF and the H-SMF can configure information based on roaming charging Generate roaming billing information.
  • the SMF determines the roaming charging information to be generated according to the roaming charging configuration information, and generates the roaming charging information for the PDU session.
  • the roaming charging information refers to the charging information to be reported generated according to the collected charging information.
  • the SMF determines that the granularity of roaming charging information (Roaming charging info level) in the roaming charging configuration information indicates QoS Flow as the granularity, then it is determined to obtain the charging information corresponding to the QoS Flow, and the charging information corresponding to the QoS Flow Write roaming billing information.
  • the SMF writes the charging information of the QoS Flow into the roaming charging information.
  • the charging information of the QoS flow written in the roaming charging information includes the QoS Flow identifier and the flow value of the up/down service data flow corresponding to the QoS flow, etc.
  • the SMF determines that the granularity of roaming charging information (Roaming charging info level) in the roaming charging configuration information indicates the service granularity (ie: Service granularity), then determine to obtain the charging information of the Service, and write the charging information of the Service to Enter roaming billing information. When the trigger corresponding to the Service is satisfied, the SMF writes the charging information of the Service into the roaming charging information.
  • Roaming charging info level the granularity of roaming charging information in the roaming charging configuration information indicates the service granularity (ie: Service granularity)
  • the SMF generates roaming charging information according to the rate group and/or service identifier or service type carried in the Service Info (that is, the rate group, service identifier, or service).
  • the usage amount corresponding to the type is respectively written into the roaming charging information, and the roaming charging information includes the usage amount corresponding to the rate group, service identifier, or service type).
  • the use corresponding to the service type may be the duration corresponding to the service type, or the value of the up/down flow corresponding to the service type.
  • SMF will generate roaming charging information for all rate groups in the PDU session (that is, write the usage amount corresponding to each rate group (which can be uplink/downlink traffic or duration) Into the roaming charging information. That is to say, if the roaming Profile does not include service info, the usage amount corresponding to each rate group is included in the roaming charging information.
  • SMF will Service When the billing information is written into the roaming billing information, the QoS Flow billing information business corresponding to the Service is also written into the roaming billing information.
  • the SMF determines that the granularity of roaming charging information (Roaming charging info level) in the roaming charging configuration information indicates that PDU session is the granularity, it determines that it is necessary to obtain the charging information of the PDU session, and write the charging information of the PDU session into Roaming billing information.
  • the roaming charging information includes the total uplink and downlink traffic value of the PDU session (no distinction between services and QoS flow).
  • the SMF is a VSMF and it is determined that there is a home network slice identifier, then obtain the network slice identifier of the home network corresponding to the slice where the PDU session is located, and write the acquired network slice identifier of the home network into the roaming charging information.
  • the SMF writes the charging information reported by each UPF into the roaming charging information according to the multiple UPF reporting instructions (for example, for For the same tariff group, if UPF1 reports 50M and UPF2 reports 100M, then the roaming charging information carries UPF1 traffic 50M and UPF2 traffic 100M respectively). If the roaming charging configuration information does not include the reporting indication of multiple UPFs, the SMF will summarize the charging information on multiple UPFs and write it into the roaming charging information (for example, in the same tariff group, UPF1 reports 50M, UPF2 reports 100M, Then the summary is that the traffic corresponding to this rate group is 150M);
  • the SMF collects the charging information according to the differentiated access methods indicated by the reporting indication of the multi-access PDU session, and adds the roaming charging information
  • the charging information corresponding to each access mode of the PDU session is written in the PDU session (for example, write in the roaming charging information: 50M is used for 3GPP access, and 100M is used for non-3GPP access).
  • the SMF will summarize the charging information corresponding to each access mode and write it into the roaming charging information (for example, 50M for 3GPP access, 50M for non-3GPP access If 100M is used, it will be written in the roaming billing information that a total of 150M has been used);
  • SMF can also obtain other information of the PDU session (such as SMF address, RAT type, etc.) and write it into the roaming charging information.
  • other information of the PDU session such as SMF address, RAT type, etc.
  • the SMF If the roaming charging configuration information includes roaming charging information reporting conditions, the SMF generates roaming charging information and reports it to the roaming charging system when the reporting conditions indicated by the roaming charging information reporting conditions are met.
  • the roaming charging information generated by V-SMF includes the charging information of Service and the corresponding QoS Flow charging information, as shown in Table 2 for example:
  • Table 2 is an example of roaming charging information generated based on information reported by a UPF, including roaming charging information of QoS flow and roaming charging information of Service.
  • the roaming charging information shown in Table 2 shows an example of a QoS flow (corresponding to a QFI container instance) in a PDU session. If the PDU includes multiple QFI containers, each QFI container contains the Multiple QFI in Table 2 One or more parameters of the lower layer of the container.
  • a Multiple QFI container parameter includes a QFI container infomration, indicating the detailed information of a QFI container. That is, a Multiple QFI container corresponds to information about a QoS flow.
  • the triggers (triggers) at the lower layer of the Multiple QFI container in Table 2 are the triggers corresponding to the QoS flow.
  • the trigger effective time (trigger timestamp) is the effective time of the trigger corresponding to the QoS flow.
  • the use time time is the use time corresponding to the QoS flow.
  • the used traffic information and the like are the used traffic corresponding to the QoS flow. Wherein, time, total volume, uplink volume, and/or downlink volume in Table 2 are usage volumes related to the QoS flow.
  • a QoS flow can correspond to one or more service data flows (Service).
  • a business data flow is represented by a multiple service container.
  • Table 2 shows a business container (Multiple service container).
  • a Multiple service container parameter indicates the information of a service data flow.
  • a Multiple service container includes a rating group, which indicates the rate group corresponding to the Service.
  • Service identifier indicates the service identifier corresponding to the Service.
  • Triggers indicate the triggers that generate the billing information of the Service. Time, total volume, uplink volume and/or downlink volume are the usage of the Service.
  • a QFI container infomration indicates the detailed information of a QFI container.
  • a QFI container infomration includes one or more parameters of the following information, such as: QoS flow ID, Time of first usage, Time of last usage, QoS Information, User location information, UE time zone and/or rat type.
  • QoS flow ID Time of first usage
  • Time of last usage Time of last usage
  • QoS Information User location information
  • UE time zone User location information
  • the V-SMF will generate a Roaming QBC information (including lower layer parameters) in Table 2 for each UPF.
  • the roaming charging information generated by V-SMF includes the charging information of Service, but does not include the charging information of QoS flow, as shown in Table 3:
  • Table 3 is the roaming charging information generated by the V-SMF according to the information reported by a UPF.
  • the roaming charging information includes an example of the roaming charging information of the Service.
  • a multiple service container indicates the charging information of a service data flow.
  • the parameters contained in a multiple service container refer to the corresponding description in Table 2. If a PDU session has multiple service data streams, the roaming charging information for the PDU session can include multiple multiple service containers, each multiple service container corresponds to a service, and the parameters include one or more of the multiple service container lower layer parameters in Table 3 parameters.
  • the V-SMF will generate a Roaming information (including lower layer parameters) in Table 3 for each UPF.
  • Table 4 is an example of roaming charging information at the granularity of PDU session. If the roaming charging configuration information includes the reporting indication of multiple UPFs, if a PDU session has multiple UPFs, the V-SMF will generate roaming charging information containing one Roaming information (including lower layer parameters) in Table 4 for each UPF .
  • the method and time of the roaming charging information generated by the H-SMF and the generated roaming charging information are similar to the above-mentioned V-SMF.
  • Step 306. The SMF reports the roaming charging information generated in step 304 to the roaming charging system.
  • the roaming charging system generates a roaming charging bill (Charging Data Record, CDR) of the user's PDU session according to the received roaming charging information, and the roaming CDR includes the roaming charging information.
  • CDR Charging Data Record
  • Step 310 When the roaming charging system determines to generate a detailed data record (detailed data record, DDR), the roaming charging system generates a DDR according to the roaming agreement, the roaming charging Profile and the roaming CDR.
  • DDR failed data record
  • the method for the roaming charging system to determine to generate the detailed data record may be that the roaming charging system generates the DDR according to the time point or time period stipulated in the roaming agreement.
  • the method of generating DDR by the roaming charging system can be:
  • the roaming charging system determines the granularity at which the DDR is generated.
  • the roaming charging system can determine according to the roaming charging Profile, or determine the granularity of generating DDR according to the roaming agreement;
  • the roaming charging system determines that the granularity of generating DDR is the QoS Flow granularity (ie: write the charging information of QoS flow into DDR), then the roaming charging system generates a DDR for each QoS Flow, and writes the PDU session
  • the charging information of the QoS Flow in the CDR (for example: the identification of the QoS Flow, corresponding traffic, etc.) is written into the DDR.
  • the roaming charging system determines that the granularity of generating DDR is Service granularity (that is, writing the charging information of a Service flow into DDR)
  • the roaming charging system generates a DDR for each Service, and writes the DDR in the CDR of the PDU session
  • the Service charging information (such as: rate group, corresponding traffic, etc.) or the Service's charging information and the corresponding QoS flow's charging information combined charging information are written into the DDR.
  • the roaming charging system determines that the granularity of generating the DDR is the PDU session granularity (that is, writing the charging information of the PDU session into the DDR)
  • the roaming charging system generates a DDR for each PDU session, and writes the PDU session
  • the charging information of the PDU session in the CDR (for example: the total traffic of the PDU session, etc.) is written into the DDR.
  • the roaming charging system can also write the information related to the PDU session (such as PDU session identifier, PDU address, etc.) in the CDR of the PDU session into the user's DDR.
  • information related to the PDU session such as PDU session identifier, PDU address, etc.
  • the roaming charging system may also write the identifier of the network slice to which the PDU belongs in the CDR of the PDU session into the DDR of the user. Specifically, if the roaming charging system can obtain the network slice identifier of the home network of the slice from the CDR of the PDU session, write the network slice identifier of the home network into the user's DDR.
  • the roaming charging configuration information includes the reporting indication of multiple UPFs, and if a PDU session has multiple UPFs, a DDR record containing some parameters shown in Table 5 is generated for each UPF. If the roaming charging configuration information includes multiple access reporting instructions, and if a PDU session has multiple access types, the roaming charging system generates a DDR containing some parameters as shown in Table 5 for each access type Record.
  • the session management function obtains roaming charging information granularity, service data flow information, multi-UPF reporting indication, multi-access reporting indication, and roaming charging information reporting conditions in the roaming charging profile, so that it can
  • the profile generates roaming charging information that supports various settlement requirements. It enables the roaming charging system to perform flexible roaming settlement according to different roaming charging configuration information, and provides data support for conflict resolution when a conflict occurs.
  • FIG. 4 is a schematic flowchart of a charging method based on HR roaming in a roaming scenario provided by an embodiment of the present application.
  • the roaming charging method in conjunction with FIG. 1B includes the following steps:
  • Step 401 User equipment (user equipment, UE) sends a first request for a PDU session to the V-SMF, so as to request to establish a PDU session for the user.
  • the first request carries user information.
  • Step 402. After receiving the first request, the V-SMF determines that the UE is a roaming UE according to the user information carried in the first request, obtains the PDU session roaming charging profile applicable to the UE, and sends the V-Roaming Accounting Profile to the V-SMF.
  • the charging system sends a first charging resource creation request, where the first charging resource creation request includes a PDU session roaming charging profile applicable to the UE.
  • the V-SMF obtains the roaming charging configuration information configured on the V-SMF. For detailed information included in the roaming charging configuration information, refer to step 302, which will not be described in detail in this embodiment of the present application.
  • the first charging resource creation request is used to request the V-CHF to generate a charging resource for the user PDU session, so as to process the roaming charging information of the UE's PDU session reported by the V-SMF.
  • Step 403. After receiving the first charging resource creation request, the V-CHF creates the first charging resource (including the assigned charging resource identifier) for the PDU session according to the first charging resource creation request, and returns to the V-SMF The first billing resource creates a response.
  • the V-CHF determines whether to update the roaming charging configuration information for the UE's PDU session according to the roaming charging profile for the UE's PDU session reported by the V-SMF. If updated, the V-CHF generates roaming charging profile update information for the UE. Specifically, the V-CHF may determine whether to update the roaming charging profile for the UE's PDU session according to the roaming agreement. For example: the roaming agreement specifies that new agreement content will start in the new quarter, and V-CHF judges based on this that the original roaming profile needs to be updated in the quarter.
  • the first charging resource creation response includes update information of roaming charging configuration information provided by the V-HF for the UE. For information contained in the update information of the roaming charging configuration information, refer to step 304 .
  • the update information of the roaming charging configuration information is used to update the configured roaming charging configuration information acquired by the V-SMF in step 402 .
  • the roaming charging profile included in the first charging resource creation response may only include one or more parameters to be updated in the roaming charging configuration information, or may include all information in the roaming charging configuration information.
  • Step 404 The V-SMF sends the second request of the PDU session to the H-SMF, so as to request the H-SMF to complete the establishment of the PDU session.
  • the second request of the PDU session carries the information of the PDU session establishment request and the roaming charging profile used by the V-SMF for the user's PDU session.
  • the roaming charging profile carried in the second request of the PDU session may be a configured roaming charging profile acquired by the V-SMF, or may be an updated roaming charging profile using the roaming charging profile sent by the V-CHF.
  • the roaming charging profile in step 404 is the roaming charging profile currently used by the user's PDU session. If the V-CHF does not provide the roaming charging profile update information for the UE in step 403, the roaming charging profile carried in step 404 is the roaming charging profile configured in the V-SMF, if in step 403 the V-CHF If the update information of the roaming charging profile for the UE is provided, the roaming charging profile carried in step 404 is the updated roaming charging profile of the V-CHF.
  • Step 405. After receiving the second request of the PDU session, the H-SMF sends a second charging resource creation request to the H-CHF.
  • the second charging resource request is used to request the H-CHF to create a charging resource for the user PDU session, so as to process the roaming charging information of the UE's PDU session reported by the V-SMF.
  • the second charging resource creation request carries the roaming charging profile sent by the V-SMF.
  • the roaming charging profile carried in the creation of the second charging resource may be a configured roaming charging profile acquired by the V-SMF, or may be an updated roaming charging profile using the roaming charging profile sent by the V-CHF.
  • Step 406 After receiving the second charging resource creation request, the H-CHF creates (create) a second charging resource for the PDU session according to the second charging resource creation request (including assigning an identifier for the second charging resource) , and return the second charging resource establishment response to the H-SMF.
  • the H-CHF determines whether to update the roaming charging profile for the UE's PDU session according to the roaming charging profile for the UE's PDU session reported by the H-SMF .
  • the H-CHF may determine whether to update the roaming profile for the UE's PDU session according to roaming agreements, user subscription changes, and/or new settlement scenarios. For example: to adjust the monthly settlement to weekly settlement, and for another example, H-CHF provides service information (such as the service rate group) according to the roaming agreement requirements, etc., then it is determined that the roaming of the PDU session used for the UE needs to be updated Profile.
  • the H-CHF determines to update the roaming charging profile used for the UE's PDU session, it generates a roaming charging profile (H-profile for short) of the home network.
  • the roaming charging profile of the home network is used to provide the V-SMF to update the roaming charging profile information provided by the V-SMF to the H-SMF in step 404 or step 405 for the user PDU session.
  • the roaming charging profile information provided to the H-SMF for the user PDU session is the configured roaming charging profile obtained by the V-SMF (the roaming charging system of the visited network has not been updated), or the roaming charging profile of the visited network Roaming billing profile after billing system update.
  • the second charging resource creation response includes the roaming charging profile of the home network and the identifier of the second charging resource.
  • the H-profile included in the second charging resource establishment response may only include one or more parameters to be updated, or may include all information of the H-profile.
  • Step 407. The H-SMF sends a response to the second request of the PDU session to the V-SMF.
  • the response to the second request of the PDU session contains the roaming charging profile of the home network.
  • Steps 408-409 After the V-SMF receives the response of the second request of the PDU session returned by the H-SMF, if the response of the second request of the PDU session carries the roaming charging profile of the home network, it sends a report to the V-SMF. - The CHF reports the roaming charging profile of the home network, and receives a response from the V-CHF that the roaming charging profile of the home network has been received.
  • the V-SMF uses the roaming charging profile of the home network to update the roaming charging profile of the user PDU session (configured roaming charging profile, or the roaming charging profile of the visited network has been used) The roaming charging profile after the charging profile is updated), and generate the roaming charging information of the user PDU session according to the updated roaming charging profile.
  • the V-SMF also generates a new policy for reporting the charging information of the user PDU session according to the updated roaming charging profile, and sends the new policy for reporting the charging information of the user PDU session to the UPF Escalation strategy.
  • Step 410 The V-SMF sends the first response of the PDU session to the UE to indicate that the establishment of the first session (such as the PDU session) for the UE is completed.
  • V-SMF obtains usage information (not shown in the figure) of the user PDU session from V-UPF when the charging reporting condition is satisfied, and generates roaming charging information according to the information reported by V-UPF.
  • the V-SMF sends a third charging request to the V-roaming charging system, and the third charging request carries roaming charging information generated by the V-SMF.
  • the V-SMF receives the third charging response returned by the V-CHF.
  • the V network roaming and charging system generates a roaming and charging bill (Charging Data Record, CDR) of the user's PDU session according to the received roaming and charging information.
  • the roaming CDR includes the roaming charging information.
  • Step 414 When the V network roaming charging system determines to generate a detailed data record (detailed data record, DDR), it generates the user's detailed data record (detailed data record, DDR) according to the roaming CDR of the user's PDU session.
  • DDR detailed data record
  • Step 411'-step 414' refer to the description of steps 411-414.
  • the H-SMF generates roaming charging information according to the usage information of the PDU session reported by the H-UPF.
  • the H-SMF sends the generated roaming charging information to the H network roaming charging system.
  • the H network roaming charging system generates the roaming CDR of the user PDU session according to the received roaming charging information.
  • the H network roaming charging system determines to generate DDR, it generates the user's DDR according to the roaming CDR of the user's PDU session.
  • the V network roaming charging system and the home network roaming charging system summarize the charging information according to the generated DDR and the roaming agreement, and generate a UDR.
  • the charging information can be aggregated according to the user group according to the roaming agreement (such as the Summarize the usage of a group of users), or summarize billing information according to services (such as summarizing the usage of the same service used by a group of users), etc., where the usage can be traffic.
  • the V network roaming billing system sends the generated UDR to the home network roaming billing system, and the home network roaming billing system uses the locally generated UDR to verify the UDR sent by the V network roaming billing system to verify the UDR.
  • the session management function 101 and the roaming charging system 102 and other devices can be divided into functional modules according to the above-mentioned method examples.
  • each functional module can be divided corresponding to each function, or two or more functions can be divided into integrated in one processing module.
  • the above-mentioned integrated modules can be implemented in the form of hardware or in the form of software function modules. It should be noted that the division of modules in the embodiment of the present application is schematic, and is only a logical function division, and there may be other division methods in actual implementation.
  • FIG. 5 is a schematic structural diagram of a roaming charging device (or charging triggering device) 500 .
  • the apparatus 500 may be the session management function 101 in the foregoing embodiment, or may be a chip within the session management function 101 , which is not specifically limited in this embodiment of the present application.
  • the device includes: an acquisition module 501 , a processing module 502 and a sending module 503 .
  • the acquiring module 501 is configured to acquire roaming charging configuration information after the processing module determines that the user corresponding to the data connection session is a roaming user, and the roaming charging configuration information includes roaming charging information granularity indication, service information, and reporting of roaming multi-user plane functions indication, roaming multi-access data connection session reporting indication, and/or reporting conditions of roaming charging information;
  • the processing module 502 is configured to, according to the roaming charging information granularity indication, the service information, the roaming multi-user plane function reporting indication, the roaming multi-access data connection session reporting indication, and/or the roaming charging information reporting condition, the charging trigger means generate Roaming billing information for data connection sessions;
  • the sending module 503 is configured to report roaming charging information to the roaming charging system.
  • the processing module 502 determining that the user corresponding to the PDU data connection session is a roaming user includes, the processing module 502 determining that the user is a roaming user according to the user's home network identifier reported by the user equipment.
  • acquiring the roaming charging configuration information of the user by the acquiring module 501 includes acquiring, by the acquiring module, the roaming charging configuration information configured in the charging trigger device as the roaming charging configuration information.
  • obtaining the roaming charging configuration information of the user by the obtaining module 501 includes: the obtaining module 501 receives the roaming charging configuration information sent by the roaming charging system, and the obtaining module 501 uses the roaming charging configuration information sent by the roaming charging system as the roaming charging configuration information. Billing configuration information.
  • the indication of the granularity of the roaming charging information is: an indication at the granularity of a quality of service flow (QoS Flow), an indication at the granularity of a service, or an indication at the granularity of a data connection session;
  • QoS Flow quality of service flow
  • the charging information corresponding to the QoS Flow is included in the roaming charging interest calculation;
  • the charging information corresponding to the service is included in the roaming charging interest calculation;
  • the charging information corresponding to the data connection session is included in the roaming charging information calculation.
  • the processing module 502 generating the roaming charging information of the data connection session includes: when the roaming charging information granularity indicates the service granularity, the charging information corresponding to the service includes the data connection session corresponding to the rate group The usage of the service, or the usage of the service corresponding to the service identifier in the data connection session, or the usage of the service corresponding to the service type in the data connection session, or the service corresponding to the rate group and the service identifier in the data connection session usage.
  • FIG. 6 is a schematic structural diagram of a roaming charging system 600 .
  • the roaming charging system 600 may be the roaming charging system 102 in the foregoing embodiment, or may be a chip in the roaming charging system 102, which is not specifically limited in this embodiment of the present application.
  • the device includes: a receiving module 601 , a processing module 602 and a sending module 603 . in,
  • the receiving module 601 is configured to receive the billing resource creation request of the user's data connection session sent by the billing trigger device, where the billing resource creation request includes the user's data connection session information;
  • the processing module 602 is configured to generate second roaming charging configuration information, the second roaming charging configuration information includes roaming charging information granularity indication, service information, roaming multi-user plane function reporting indication, roaming multi-access data connection session Reporting instructions, and/or conditions for reporting roaming charging information;
  • the sending module 603 is configured to send the second roaming charging configuration information to the charging triggering device.
  • the receiving module 601 is further configured to receive the roaming charging information sent by the charging trigger device, and the roaming charging information is generated according to the second roaming charging configuration information sent by the roaming charging system.
  • the charging resource creation request includes first roaming charging configuration information
  • the first roaming charging configuration information includes roaming charging information granularity indication, service information, roaming multi-user plane function reporting indication, roaming multi-access data
  • the reporting indication of the connection session and/or the reporting condition of roaming charging information, the second roaming charging configuration information is used by the charging triggering device to update the first roaming charging configuration information in the charging triggering device.
  • the processing module 602 is further configured to determine and generate second roaming charging configuration information for updating the first roaming charging configuration information according to the first roaming charging configuration information carried in the charging resource creation request.
  • the processing module 602 is further configured to generate a charging data record (CDR) of the user, and the charging data record includes roaming charging information.
  • CDR charging data record
  • modules in FIG. 6 may also be used to execute the steps performed by the roaming charging system in the method flow in FIGS. 3-4 .
  • the apparatus 500 is presented in a form of dividing various functional modules in an integrated manner.
  • a “module” here may refer to an application-specific integrated circuit (ASIC), a circuit, a processor and memory executing one or more software or firmware programs, an integrated logic circuit, and/or other device.
  • ASIC application-specific integrated circuit
  • the device 500 can take the form shown in FIG. 2 .
  • the processor 201 in FIG. 2 may invoke the computer-executed instructions stored in the memory 203, so that the roaming charging system executes the roaming charging method in the foregoing method embodiments.
  • the computer executes instructions stored in the memory 203 to implement.
  • the functions/implementation process of each module may also be implemented by software or circuits.
  • the memory 203 may be a storage unit in the chip, such as a register, a cache, and the like.
  • this embodiment of the present application does not specifically limit it.
  • the charging triggering device 600 and/or the roaming charging system 500 may be implemented on an integrated circuit, a wireless radio frequency integrated circuit, a printed circuit board, or the like.
  • the device can be a self-supporting device or a part of a larger device.
  • the charging triggering device 600 and/or the roaming charging system 500 are presented in the form of dividing various functional modules in an integrated manner.
  • a "module" here may refer to a specific ASIC, a circuit, a processor and a memory executing one or more software or firmware programs, an integrated logic circuit, and/or other devices that can provide the functions described above.
  • Figure 7 is a schematic diagram of the system provided by the present application, including a billing trigger device 110 and a roaming billing system 120.
  • the billing trigger device can be used to execute the steps performed by the session management function in Figure 3 and Figure 4, and can also execute the steps in Figure 5 Function of the roaming charging device.
  • the roaming charging system 120 may be used to execute the steps performed by the roaming charging system in FIG. 3 and FIG. 4 .
  • all or part of them may be implemented by software, hardware, firmware or any combination thereof.
  • a software program it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions.
  • the computer program instructions When the computer program instructions are loaded and executed on the computer, the processes or functions according to the embodiments of the present application will be generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website, computer, server, or data center Transmission to another website site, computer, server or data center by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.).
  • the computer-readable storage medium may be any available medium that can be accessed by a computer, or may be a data storage device including one or more servers, data centers, etc. that can be integrated with the medium.
  • the available medium may be a magnetic medium (such as a floppy disk, a hard disk, or a magnetic tape), an optical medium (such as a DVD), or a semiconductor medium (such as a solid state disk (solid state disk, SSD)), etc.

Landscapes

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

Abstract

一种计费方法和装置，应用于漫游场景。该方法包括：计费触发装置确定数据连接对应的用户为漫游用户后，获取漫游计费配置信息，漫游计费配置信息包括漫游计费信息粒度指示、业务信息、漫游多用户面功能的上报指示、漫游多接入数据连接会话上报指示、和/或漫游计费信息的上报条件；根据漫游计费配置信息，计费触发装置生成数据连接会话的漫游计费信息，并向漫游计费系统上报漫游计费信息。

Description

一种计费方法和装置
本申请要求于2021年10月01日提交中国专利局、申请号为202111166971.X、申请名称为“一种计费方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种计费方法和装置。
背景技术
在当前的漫游清算采用GSMA定义的国际漫游清算流程TAP(Transferred Account Procedure)。而TAP按照每条转帐数据，或每分钟的转帐数据，或每条消息的转帐数据生成的详单。因此，TAP方式进行漫游清算导致数据量非常大，无法满足第五代(Fifth Generation，5G)移动通信技术业务的实时性要求，以及无法适用IOT等小流量数据业务。
当前另一种漫游清算采用账务与计费演进(Billing and Charging Evolutio，BCE)的方式。BCE支持基于每天、每月、每季度、每年或者按约定汇总的使用数据计费。然而，采用BCE方式在漫游清算过程中，如果拜访网络(visited network)和归属网络(home network)在清算过程中不一致，拜访网络(visited network)和归属网络(home network)详细数据记录。
在5G漫游架构下，拜访网与归属网的清算、对账、及冲突解决是基于BCE流程。拜访网和归属网采集的计费信息是生成漫游场景下的详细数据记录(detailed data recording,DDR)的基础。5G的业务需求多种多样，因此5G业务的漫游清算的DDR也有多种需求。但当前拜访网和归属网之间基于BCE漫游清算方式，面临拜访网生成的DDR文档难以支持漫游清算、对账、及冲突解决，进而无法满足多种业务清算需求。
发明内容
本申请实施例提供计费方法和装置，使得在漫游计费的场景下，为用户数据连接会话上报的漫游计费信息，可以满足多种业务的需求，并支撑拜访网和归属网的漫游清算、对账、及冲突解决。
为达到上述目的，本申请实施例第一方面提供如下技术方案包括：计费触发装置确定数据连接会话对应的用户为漫游用户后，获取漫游计费配置信息，漫游计费配置信息包括漫游计费信息粒度指示、业务信息、漫游多用户面功能的上报指示、漫游多接入数据连接会话上报指示、和/或漫游计费信息的上报条件。根据漫游计费信息粒度指示、业务信息、漫游多用户面功能上报指示、漫游多接入数据连接会话上报指示、和/或漫游计费信息上报条件，计费触发装置生成数据连接会话的漫游计费信息。计费触发装置向漫游计费系统上报漫游计费信息。
根据上述方法，漫游计费配置信息经过扩展后包括漫游计费信息粒度指示、业务信息、漫游多用户面功能的上报指示、漫游多接入数据连接会话上报指示、和/或漫游计费信息的上报条件，从而可以根据漫游计费的profile生成支持多种清算需求的漫游计费信息。使得 漫游计费系统可以根据不同漫游计费配置信息进行灵活的漫游清算，并在出现冲突时，为冲突解决提供了数据支撑。
比如，在本申请实施例中，通过使用漫游计费信息粒度指示可以确保用户在拜访网和归属网的计费信息粒度同步，进而满足不同运营商之间针对用户群按照服务质量粒度进行漫游清算或者按照业务为粒度进行清算或者以数据连接会话粒度的总流量低成本清算等不同业务的需求。
或者，通过使用业务信息可以针对特定业务(如MEC业务)或者特定类型业务(如IoT的小流量业务)进行漫游清算，使得运营商之间的漫游清算能力更好的支持特定行业和客户的漫游需求。
或者，通过使用漫游多用户面功能的上报指示可以使得运营商可以更准确的基于网络资源的使用进行漫游清算，实现真正的按网络资源使用付费，使得漫游清算能力更为精细化以满足不同清算需求。
或通过使用漫游多接入协议数据单元会话上报指示可以区分固网接入和移动接入的漫游信息，进而更好的支持固网移动融合网络漫游网的精确清算能力，避免将固定接入和移动接入打包在一起进行清算对拜访网(用户在拜访网使用移动接入更多时)或者归属网(用户在拜访网使用固定接入更多时)造成损失。
或通过使用漫游计费信息的上报条件，可以灵活的实现按照指定时间点分割漫游计费信息，进而支持更为灵活的清算周期(如按天、按周、按月、按季度等)的清算。
在一个可选的实施例中，计费触发装置确定协议数据单元数据连接会话对应的用户为漫游用户包括：计费触发装置根据用户设备上报的用户的归属网标识确定用户为漫游用户。通过能根据用户设备上报的用户的归属网标识确定用户为漫游用户，使得确定用户为漫游用户更为精确。
在一个可选的实施例中，获取用户的漫游计费配置信息包括：计费触发装置获取配置在计费触发装置的漫游计费配置信息作为漫游计费配置信息。通过在计费触发装置配置用户的漫游计费配置信息，使得对用户的漫游计费配置信息的获取方法更为灵活，多样化。
在一个可选的实施例中，获取用户的漫游计费配置信息包括：计费触发装置接收漫游计费系统发送的漫游计费配置信息。计费触发装置将漫游计费系统发送的漫游计费配置信息作为漫游计费配置信息。通过漫游计费系统获取漫游计费配置信息，使得对用户的漫游计费配置信息的获取方法更为灵活，多样化。
在一个可选的实施例中，漫游计费信息的粒度的指示为：以服务质量流(QoS Flow)为粒度的指示、以业务为粒度的指示、或以数据连接会话为粒度的指示。当漫游计费信息粒度指示为以QoS Flow为粒度的指示时，漫游计费计息中包含与QoS Flow对应的计费信息。当漫游计费信息粒度指示为以业务粒度的指示时，漫游计费计息中包含与业务对应的计费信息。或，当漫游计费信息粒度指示为以数据连接会话为粒度的指示时，漫游计费计息中包含与数据连接会话对应的计费信息。漫游计费配置信息经过扩展后包括漫游计费信息粒度指示，从而可以根据漫游计费的profile生成支持多种清算需求的漫游计费信息。使得漫游计费系统可以根据不同漫游计费配置信息进行灵活的漫游清算，并在出现冲突时，为冲突解决提供了数据支撑。
在一个可选的实施例中，当漫游计费信息粒度指示为以业务粒度的指示时，业务对应的 计费信息包括数据连接会话中与费率组对应的业务的使用量，或数据连接会话中与业务标识对应的业务的使用量，或数据连接会话中与业务类型对应的业务的使用量，或数据连接会话中与费率组和业务标识对应的业务的使用量。通过本方法，业务对应的计费信以漫游计费信息的粒度为依据，从而使得可以提供基于业务的计费信息，满足漫游计费系统的多种计费需求。
在一个可选的实施例中，漫游计费信息粒度为以业务为粒度的指示且漫游计费配置信息还包括业务相关信息，业务相关信息包括业务类型、费率组、和/或业务标识，漫游计费计息进一步包含业务类型、费率组、和/或业务标识。漫游计费信息粒度为以业务为粒度的指示且漫游计费配置信息还包括业务相关信息，从而使得可以提供基于业务的计费信息，满足漫游计费系统的多种计费需求。
在一个可选的实施例中，所述计费触发装置为拜访网的计费触发装置时漫游计费配置信息还包括数据连接会话对应的归属网的网络切片标识；和/或
漫游计费配置信息还包括多用户面功能UPF的上报指示，漫游计费信息还包括数据连接会话的每个户面功能上报的计费信息或者包括数据连接会话的多个UPFs上报的计费信息合并后的计费信息；和/或
漫游计费配置信息包括多接入数据连接会话的上报指示，漫游计费信息包括数据连接会话的每个接入对应的计费信息或包括数据连接会话中多个接入对应的计费信息合并后的计费信息。
通过本方法，漫游计费配置信息包括上述多种信息，从而使得可以提供基于漫游计费配置信息的漫游计费信息，满足漫游计费系统的多种计费需求。进一步的，网络切片标识，可以支持按照网络切片的清算，可以针对不同切片(比如不同类型，不同质量要求的切片)使用不同的使用费用，从而在避免拜访网运营商和归属网运营商损失的基础上降低切片使用成本。
在一个可选的实施例中，当漫游计费配置信息包括漫游计费信息上报条件，生成漫游计费信息包括：计费触发装置确定漫游计费信息上报条件满足，生成漫游计费信息，并向漫游计费系统上报漫游计费信息。
第二方面，本申请实施例提供一种漫游计费方法，包括：漫游计费系统接收计费触发装置体发送的用户的数据连接会话的计费资源创建请求，计费资源创建请求包括用户的数据连接会话信息。漫游计费系统生成第二漫游计费配置信息，第二漫游计费配置信息包括漫游计费信息粒度指示、业务信息、漫游多用户面功能的上报指示、漫游多接入数据连接会话的上报指示、和/或漫游计费信息上报条件；
漫游计费系统向计费触发装置发送第第二漫游计费配置信息。接收计费触发装置发送的漫游计费信息，漫游计费信息根据漫游计费系统发送的第二漫游计费配置信息生成。
根据上述方法，漫游计费配置信息经过扩展后包括漫游计费信息粒度指示、业务信息、漫游多用户面功能的上报指示、漫游多接入数据连接会话上报指示、和/或漫游计费信息的上报条件，从而可以根据漫游计费的profile生成支持多种清算需求的漫游计费信息。使得漫游计费系统可以根据不同漫游计费配置信息进行灵活的漫游清算，并在出现冲突时，为冲突解决提供了数据支撑。
在一种可选实施例中，计费资源创建请求包含第一漫游计费配置信息，第一漫游计费配 置信息包括漫游计费信息粒度指示、业务信息、漫游多用户面功能的上报指示、漫游多接入数据连接会话的上报指示、和/或漫游计费信息上报条件，第二漫游计费配置信息用于计费触发装置更新计费触发装置中的第一漫游计费配置信息。
通过本方法，漫游计费系统可以更新漫游计费配置信息，从而合使得漫游计费配置信息更能满足漫游计费系统的计费业务的需求。
在一种可选实施例中，根据计费资源创建请求中携带的第一漫游计费配置信息，漫游计费系统确定生成用于更新第一漫游计费配置信息的第二漫游计费配置信息。通过本方法，漫游计费系统确定更新漫游计费配置信息，从而合使得漫游计费配置信息更能满足漫游计费系统的计费业务的需求。
在一种可选实施例中，漫游计费系统生成用户的计费话单(Charging Data Record，CDR)，计费话单包括漫游计费信息。通过本方法，漫游计费系统生成的CDR包括漫游计费信息，从而使得漫游计费信息满足漫游计费系统的计费业务的需求。
在一种可选实施例中，漫游计费计息中包含与QoS Flow对应的计费信息，则计费话单包括QoS Flow对应的计费信息；或，漫游计费计息中包含与业务对应的计费信息，则计费话单包括业务对应的计费信息；或，漫游计费计息中包含与数据连接会话对应的计费信息，则计费话单包括数据连接会话对应的计费信息。通过本方法，计费话单包括不同粒度的计费信息，使得漫游计费系统可以根据不同漫游计费配置信息进行灵活的漫游清算，并在出现冲突时，为冲突解决提供了数据支撑。
在一种可选实施例中，所述计费触发装置为拜访网的计费触发装置时漫游计费信息包括数据连接会话对应的归属网的网络切片标识，则计费话单包括归属网的网络切片标识。计费话单包括归属网的网络切片标识，从而使得漫游计费信息满足漫游计费系统对网络切片相关的计费业务的需求。
在一种可选实施例中，漫游计费系统生成详细数据记录，在详细数据记录中包括QoS Flow对应的详细数据记录或者业务对应的详细数据记录或者数据连接会话对应的详细数据记录，详细数据记录基于计费话单生成。通过本方法，详细数据记录包括QoS Flow对应的详细数据记录或者业务对应的详细数据记录或者数据连接会话对应的详细数据记录，从而使得漫游计费系统可以实现对基于QoS Flow的计费或业务的计费，满足不同的业务需求。
第三方面，提供了一种漫游计费装置，该装置体具有实现上述第一方面的方法的计费触发装置的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第四方面，提供了一种漫游计费装置，包括：处理器和存储器；该存储器用于存储计算机执行指令，当该装置运行时，该处理器执行该存储器存储的该计算机执行指令，以使该装置执行如上述第一方面中任一的方法。该装置具体可以是第一方面中任一的方法中涉及的计费触发装置中的芯片。
第五方面，提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机可以执行上述第一方面中任意一项的漫游计费方法。
第六方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机可以执行上述第一方面中任意一项的漫游计费方法计费方法。
其中，第二方面至第六方面中任一种设计方式所带来的技术效果可参见第一方面中不同设计方式所带来的技术效果，此处不再赘述。
第七方面，提供了一种漫游计费系统，该系统具有实现上述第二的方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第八方面，提供了一种漫游计费系统，包括：处理器和存储器；该存储器用于存储计算机执行指令，当该装置运行时，该处理器执行该存储器存储的该计算机执行指令，以使该装置执行如上述第二方面中任一方法。
第九方面，提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机可以执行上述第二方面中任意一项的计费方法。
第十方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机可以执行上述第二面中任意一项的漫游计费方法。
第十一方面，提供了一种系统，包括计费触发装置和漫游计费系统。控制面功能可以执行上述任一方面中计费触发装置执行的处理。漫游计费系统可以执行上述任一方面中计费功能执行的处理。
本申请的这些方面或其他方面在以下实施例的描述中会更加简明易懂。
附图说明
图1A为本申请实施例提供的实现漫游计费系统的结构示意图；
图1B为申请实施例提供的在HR漫游场景下的实现漫游的网络结构示意；
图2为本申请实施例提供的通信设备的硬件结构示意图；
图3为本申请实施例提供的在漫游场景下进行计费的方法流程示意图；
图4为本申请实施例提供的基于HR漫游游场景下的计费的方法流程示意图；
图5为本申请实施例提供的装置的结构示意图；
图6为本申请实施例提供的装置的结构示意图，
图7为本申请实施例提供的系统结构示意图。
具体实施方式
本发明实施例描述的网络架构以及业务场景是为了更加清楚的说明本发明实施例的技术方案，并不构成对于本发明实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本发明实施例提供的技术方案对于类似的技术问题，同样适用。
在本文中提及“实施例”意味着，结合实施例描述的特定特征、结构或特性可以包含在本申请的至少一个实施例中。在说明书中的各个位置出现该短语并不一定均是指相同的实施例，也不是与其它实施例互斥的独立的或备选的实施例。本领域技术人员显式地和隐式地理解的是，本文所描述的实施例可以与其它实施例相结合。
“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。
本申请的说明书和权利要求书及附图中的术语“第一”、“第二”、“第三”和“第四”等是用于区别不同对象，而不是用于描述特定顺序。此外，术语“包括”和“具有”以及它们任何变形，意图在于覆盖不排他的包含。例如包含了一系列步骤或单元的过程、方法、系统、产品或设备没有限定于已列出的步骤或单元，而是可选地还包括没有列出的步骤或单元，或可选地还包括对于这些过程、方法、产品或设备固有的其它步骤或单元。
对本申请涉及的术语定义如下：
用户设备(user device)：为终端用户的设备；该设备可以具有无线通信能力，以通过空中接口与无线接入设备相连，也可以具有有线通信能力，以通过有线接口与有线接入设备相连；从产品形态上看，该设备可以是智能手机、带有无线通信功能的膝上电脑(Laptop)、平板电脑、可穿戴设备、AR(Augmented Reality，增强现实)设备、IoT(Internet of Things，万物互联)设备、办公桌面的台式机等；该设备可以通过数据连接会话消费数据网络中的应用服务器提供的应用服务。
用户设备可以包含3GPP标准规范定义的UE(user equipment，用户设备)的功能，如后续图中的UE。
漫游用户设备：处于漫游状态的用户设备。
运营商网络:为用户设备的拜访地的运营商的通信网络；本申请实施例假设用户设备已漫入到运营商网络，从而，用户设备是运营商网络的漫入者(in-bound roamer)，运营商网络是用户设备的拜访网络(visited network)，简称“拜访网”。
数据网络(Data Network，DN)：用于传输数据、以数据交换机为转接点而组成的网络，如英特网(Internet)，其中包含至少一个应用服务器(图中未显示)，为用户设备提供应用服务；通常用DNN(data network name，数据网络名称)作为数据网络的标识。
数据连接会话：为用户设备与数据网络之间的一种联结(association)，用于为用户设备与数据网络之间的通信提供连接服务，使通信数据包(Packet)可以在用户设备和数据网络之间来回传输；其创建过程可以由用户设备发起，其拆除过程可以由用户设备发起，也可以由其他设备(如用户面数据网关)发起。数据连接会话可以是3GPP标准规范定义的IP-CAN(IP-connectivity access network，IP连通性接入网)会话或者协议数据单元会话(protocol data unit session，PDU会话)，也可以是其他形式的会话，对此本申请实施例不作限定。数据连接会话可以是适用于5G网络的协议数据单元会话，也可以是适用于其它网络的其它会话，本申请实施例在此不做限定。
用户面数据网关：为数据连接会话提供支撑服务(例如，把来自用户设备的数据包通过用户面数据网关传送到数据网络，或者把来自数据网络、通过用户面数据网关传来的数据包传送到用户设备)的核心网网元。用户面数据网关根据采集操作配置参数采集数据连接会话相关的计费信息(如业务单元使用量)，且提供所采集的计费信息给计费触发装置；其中，采集操作配置参数可以是在用户面数据网关本地缺省配置的，也可以是计费触发装置下发给用户面数据网关的。
用户面数据网关可以包含3GPP标准规范定义的UPF(user plane function，用户面功能)设备的功能、PGW-U(packet data network gateway for user plane，用户面分组数据网关)的功能或SGW-U(serving gateway for user plane，用户面服务网关)的功能等。用户面数据网关可以是适用于5G网络架构下的用户面功能UPF,也可以是适用于其它网络架构下的网元，本 申请实施例不做限定。后续的内容中，为便于介绍，以用户面数据网关为5G网络架构下的UPF为例进行说明。
漫游计费信息：是指在漫游场景下与数据连接会话有关的计费信息，可以是拜访网的计费触发装置收集的漫游数据连接会话有关的计费信息，也可以是归属网的计费触发装置收集的漫游数据连接会话有关的计费信息。
漫游计费配置参数：是指与漫游计费信息的操作有关的配置参数，所述操作包括采集操作和/或上报操作，所述采集操作是指从漫游数据连接会话中采集漫游计费信息，所述上报操作是指个采集的漫游计费信息发送给相应的计费处理设备；因此，漫游计费配置参数包括采集操作配置参数和/或上报操作配置参数；当一到多个漫游计费配置参数在归属网和拜访网之间共享或同步时，可以提高双方就同一个漫游数据连接会话的计费处理结果之间的同步性、一致性，从而可以减少跨网(即跨运营商网络)清算时产生的错误。
采集操作配置参数为计费信息的采集操作有关的配置参数，用于使用户面数据网关确定如何针对漫游数据连接会话采集漫游计费信息；
归属网路由(HomeRouted，HR)漫游：媒体路由不选择本地转出，而路由回归属网络，经归属网络中转的模式。在HR漫游模式下，所有流量经过拜访网络和归属网络。
本地转出(Local Breakout,筒称LBO)漫游，即UE漫游到拜访网络后，媒体路由选择本地直出，而不路由至归属网络。在LBO漫游模式下，所有流量只经过拜访网络。
多接入PDU会话(multiple access PDU Session),指提供PDU连接业务的PDU会话，该PDU会话在一定的时间可用于一种接入，或可同时支持多种不同的接入(比如支持3GPP接入和非3GPP接入)。
多用户面功能，指一个PDU会话涉及了多个UPF。
漫入UE指移动到本网络(指拜访网络)接入但归属于其它运营商网络的UE。
QoS Flow为通讯系统中QoS转发处理(forwarding treatment)的最小粒度(finest granularity)，映射到同一QoS Flow的所有流量都会接受相同的转发处理(例如调度策略、队列管理策略、速率策略等)。通讯系统提供不同的QoS转发处理需使用不同的QoS Flow。对于其他通信系统若使用了与QoS Flow相同作用的概念，该申请的方法依然适用。
图1A为本申请实施例提供的实现漫游计费系统。该系统包括计费触发装置110和漫游计费系统120。计费触发装置和漫游计费系统可以为归属网络的网络设备，或者计费触发装置和漫游计费系统也可以为拜访网络的网络设备，本申请不限定其他归属形态下的交互。计费触发装置110用于获取漫游计费配置信息，根据漫游计费系统下发的漫游计费配置更新信息更新漫游计费配置信息，并根据漫游计费配置信息生成漫游计费信息。计费触发装置110还用于向漫游计费系统120发送生成的漫游计费信息。计费触发装置可以为5G系统架构下的网元。比如计费触发装置可以设置在5G网络中的会话管理功能SMF中，也可以设置在5G网络中的接入和移动管理功能(Access and Mobility Management Function，AMF)。漫游计费系统120可以是5G网络中的计费功能CHF或者融合计费系统(Converged Charging System，CCS)或者包括漫游话单生成及漫游计费处理功能的其他实体。漫游计费系统还可以是包含计费功能CHF或者融合计费系统(Converged Charging System，CCS)或者包括漫游话单生成及漫游计费处理功能的其他实体。漫游计费系统120用于根据计费触发装置发送的漫游计费信息生成漫游计费话单(Charging Data Record,CDR),并根据漫游CDR生成详细数据记录 (Detail Data Record，DDR)。
此外，本申请中的计费触发装置和漫游计费系统还可以不限于5G网络架构，可以应用于任何网络架构并支持实现漫游计费的场景中。本申请后续内容以计费触发装置设置于5G网络架构中的会话管理功能中，或以计费触发装置为5G网络架构中的SMF为例进行说明。
此外，本申请中的计费触发装置和漫游计费系统还可以不限于5G网络架构，可以应用于任何网络架构并支持实现漫游计费的场景中。本申请后续内容以计费触发装置设置于5G网络架构中的会话管理功能中，或以计费触发装置为5G网络架构中的SMF为例进行说明。也就是说，图1A中的计费触发装置用于执行图1B到图5中的拜访网的会话管理功能的相应操作。图1A中的漫游计费系统用于执行图1B到图5中拜访网的漫游计费系统(包括V-CHF)或归属网的漫游计费系统(包括H-CHF)的相应操作。
图1B为申请实施例提供的在HR漫游场景下的实现漫游的网络结构示意。该网络结构包括归属公共陆地移动网(home Public Land Mobile Network,HPLMN)，和拜访公共陆地移动网(visited Public Land Mobile Network,VPLMN)。归属公共陆地移动网简称归属网，拜访公共陆地移动网简称拜访网。在图1B所示的场景中，拜访网的UPF103-1与归属网的UPF103-2互通，将用户接入拜访网的上行业务数据流发送给归属网的UPF103-2，或者从UPF103-2接收用户的下行业务数据流。拜访网的SMF101-1根据拜访网的UPF103-1发送的用户接入拜访网使用的业务数据流的信息(如流量信息，或时长信息)生成漫游计费信息发送给包含的漫游计费系统(包含拜访网的计费功能V-CHF)。归属网的SMF101-2根据归属网的UPF103-2发送的用户接入拜访网使用的业务数据流的信息生成漫游计费信息发送给漫游计费系统(包括归属网的计费功能H-CHF)。包含拜访网的计费功能V-CHF的漫游计费系统和包含归属网的计费功能H-CHF的漫游计费系统用于根据各自网络中的SMF发送的用户的漫游计费息进行处理，比如生成用户在漫游场景下的漫游话单。拜访网的漫游计费系统102-1可以是V-CHF或者包含V-CHF。归属网的漫游计费系统102-2可以是H-CHF或者包含H-CHF。拜访网的漫游计费系统102-1根据V-CHF生成的用户的漫游CDR生成DDR,并根据用户的DDR生成使用数据报表(Usage Data Report，UDR)。归属网的漫游计费系统102-2根据H-CHF生成的用户的漫游CDR生成漫游DDR,并根据H-CHF生成的用户的DDR生成使用数据报表。
拜访网的SMF101-1与归属网的SMF101-2互通，用以为用户建立PDU会话，以及更新用户的漫游计费配置信息。比如，拜访网的SMF101-1将用户的漫游计费配置信息发送给归属网的SMF101-2,并从归属网的SMF101-2获取更新的用户的漫游计费配置信息。拜访网的漫游计费系统102-1和归属网的漫游计费系统102-2互通，交互各自生成的用户的UDR，以进行费用清算。
图2所示为本申请实施例提供的通信设备的硬件结构示意图。该通信设备200包括至少一个处理器201，通信线路202，存储器203以及至少一通信接口204。
处理器201可以是一个通用中央处理器(central processing unit，CPU)，微处理器，特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制本申请方案程序执行的集成电路。
通信线路202可包括一通路，在上述组件之间传送信息。
通信接口204，使用任何收发器一类的装置，用于与其他设备或通信网络通信，如以太网 等。
存储器203可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是独立存在，通过通信线路202与处理器相连接。存储器也可以和处理器集成在一起。
其中，存储器203用于存储执行本申请方案的计算机执行指令，并由处理器201来控制执行。处理器201用于执行存储器203中存储的计算机执行指令，从而实现本申请下述实施例提供的会话建立方法。
可选的，本申请实施例中的计算机执行指令也可以称之为应用程序代码，本申请实施例对此不作具体限定。
在具体实现中，作为一种实施例，处理器201可以包括一个或多个CPU。
在具体实现中，作为一种实施例，通信设备200可以包括多个处理器，例如图2中的处理器201和处理器208。这些处理器中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
图2所示的通讯设备，可以是本申请实施例中的SMF或漫游计费系统。
下面将结合图1A,图1B和图2，对本申请实施例提供的会话建立方法进行具体阐述。
图3为本申请实施例提供的在漫游场景下进行计费的方法流程示意图。本实施例中，漫游可以是基于HR场景下的漫游，也可以是基于LBO场景下的漫游。
在申请实施例中，在执行步骤302之前，还可以包括PCF向SMF发送PDU会话的策略控制及计费规则(policy control and charging rule,PCC rule)。该PCC rule包括费率组(rating group,RG)及与费率组对应的业务数据流的信息，或者PCC rule包含业务标识及与业务标识对应的业务数据流的信息。或者PCC rule包含费率组，业务标识以及与费率组对应的业务数据流的信息。
PCF可以是拜访网络的PCF(即V-PCF)。V-PCF在确定用户为漫游用户后，基于漫游协议生成漫游用户的会话(比如PDU会话)的PCC rule。作为另一可选方式，V-PCF在确定用户为漫游用户后，V-PCF可以从归属网络的PCF(即H-PCF)漫游用户的计费策略参数，并基于获取的漫游用户的计费策略参数生成漫游用户的会话的PCC rule。漫游用户的计费策略参数包括：费率组、业务标识，和/或与费率组对应的业务数据流的信息。
V-PCF确定用户为漫游用户为现有技术，本申请实施例在此不再详述。
值得说明的是，PCF可以不向SMF发送费率组(rating group,RG)及与费率组对应的业务数据流的信息，或者PCC rule不包含业务标识及与业务标识对应的业务数据流的信息。
步骤302、SMF获取漫游用户对应的漫游计费配置信息(Roaming Charging Profile)。
SMF可以是V-SMF，也可以是H-SMF。以下SMF以V-SMF，漫游计费系统为V-CHF为例进行说明。漫游计费配置信息也称之为漫游计费Profile。
SMF确定用户为漫游用户。具体的，SMF根据用户设备上报的用户的归属网标识(即：归属网PLMN标识)与SMF的网络标识(即SMF的归属PLMN标识)确定，若用户的归属网标识与SMF的网络标识不同则确定该用户设备为漫游用户设备。
SMF获取漫游计费配置信息的方法包括如下方式：
方式一、在SMF上配置该拜访网用户的漫游计费配置信息，SMF根据配置的漫游计费配置信息获取该漫游用户对应的漫游计费profile。
方式二、SMF接收拜访网或归属网的漫游计费配置信息更新发送的漫游计费profile，进而获取该漫游用户对应的漫游计费profile。其中，漫游计费配置信息更新可以是拜访网计费功能(V-CHF)或者归属网计费功能(H-CHF)，也可以是其他可以更新计费配置信息的。
漫游计费Profile包括如下漫游参数列表中一个或多个参数：
1.漫游计费信息的粒度的指示：指示获取的漫游计费信息的粒度。漫游计费信息的粒度可以是以服务质量流(QoS flow)为粒度的指示、以业务(service)为粒度的指示、或以PDU会话为粒度的指示。该指示示例如表1中的“Roaming charging info level”参数。表一中仅示出了漫游计费信息的粒度为以业务为粒度的指示。漫游计费profile还包括不同漫游计费信息粒度对应的触发器的信息。触发器的信息包括：触发器名称(trigger type)、触发器类型(trogger category)、和/或特定触发器的限额值(limit)。
若漫游计费信息的粒度的指示为以业务为粒度的指示，则漫游计费Profile进一步还可以包括业务信息。业务信息包括：业务的费率组、业务的业务标识、业务的业务类型，和/或业务的其他信息。业务信息用于指示收集与业务类型对应的业务的漫游计费信息、费率组对应的业务的漫游计费信息、与业务标识对应的业务的漫游计费信息，或业务信息用于指示收集与业务类型，费率组、和业务标识对应的业务的漫游计费信息。若漫游计费信息的粒度的指示为以业务为粒度的指示，且漫游计费配置信息未包括业务的信息，则指示分别对所有费率组对应业务收集漫游计费信息。费率组为该PDU会话中业务对应的费率组标识，业务标识为该PDU会话中业务对应的业务标识，业务类型为该PDU会话中业务对应的业务类型，业务的其他信息为该业务对应的业务数据流的识别规则(即：流特征信息)。业务的信息可参考表一中的service info包括的信息，比如表一中的service info包含：rating group(费率组),service ID(业务标识),service type(业务类型)、flow information(流特征)。在实现上，若SMF可以通过其他方式获得费率组或者业务标识对应的流特征(比如：可以通过PCF下发的PCC rule获得，若PCF为vPCF，V-PCF在确定用户为漫游用户后，可以从归属网络的PCF获取漫游用户的费率组/业务标识、及对应的流特征信息，在生成的漫游用户的PCC rule中包括费率组或者业务标识对应的流特征)，则在漫游参数中不包括流特征信息。
2.漫游多用户面功能UPFs的上报指示：该指示信息用于指示当PDU会话使用多个UPF时，在漫游计费信息中是否需要分别写入各UPF上报的计费信息(参考表一中的perUPF)。比如指示漫游计费信息中包括PDU会话的每个户面功能上报的计费信息，或者包括PDU会话的多个UPFs上报的计费信息合并后的计费信息。
3.漫游多接入PDU会话上报指示：如果PDU会话为多接入PDU会话(MA PDU SESSION，比如：一个PDU会话同时有多种接入技术，比如同一PDU会话同时使用3GPP接入和非3GPP接入)，则还可以携带多PDU会话漫游计费指示信息(参考表一中的maPDUSupport)。该指示信息用于指示在漫游计费信息中是分别携带每种接入方式下的计费信息，还是携带PDU会话中多个接入对应的 计费信息合并后的计费信息。
4.漫游计费信息上报条件：指示SMF向漫游计费系统上报漫游计费信息的上报条件(如上报时间点，参考表一中的ReportTime)，以保证漫游计费信息在生成DDR等时可以准确分割。比如，漫游清算有按天清算需求，则可以指定每天24:00点上报一次，漫游清算有按月清算需求，则可以指定每月最后一天的24:00点上报一次。
漫游profile包括的参数可以如表一所示：
Figure PCTCN2022089213-appb-000001
表一
参见表一，表一为漫游计费配置信息的例子。在表一所示的漫游计费配置信息包括触发器(trigger)的信息,用于指示向漫游计费系统上报该表一所示例子中以业务为粒度，或以服务质量流(QoS Flow)为粒度、或以PDU会话为粒度。表一所示的触发器的信息包含的参数为：trigger type,trigger category,time limit,和/或volume limit。触发器的信息包含的参数的意思可参考表一中对应参数的解释。
在表一所示的漫游计费配置信息还可以包括漫游计费信息的粒度的指示(Roaming  charging infor level)。漫游计费信息的粒度的指示可以为以服务质量流(QoS Flow)为粒度的指示、以业务为粒度的指示、或以协议数据单元会话为粒度的指示，该示例中的漫游计费信息的粒度的指示参数是显式的指示。另一实现，漫游计费信息的粒度的指示也可以是隐式的指示。比如：漫游计费profile没有携带Roaming charging info level参数，但漫游计费Profile直接携带了以业务为粒度的漫游计费配置信息参数(如表1的Service Info)，则指示该漫游计费信息的粒度为以业务为粒度。
在表一所示的漫游计费配置信息还可以包括业务粒度的漫游计费配置信息参数(Service Info)参数组。该Service Info组参数可以独立于漫游计费信息的粒度的指示(Roaming charging infor level)，也可以作为漫游计费信息的粒度的指示(Roaming charging infor level)的取值。也就是说，表一中的Service Info组参数可以与Roaming charging infor level参数并列，也可以与Roaming charging infor level参数合并(即Roaming charging infor level参包含service info参数)。当业务信息(Service Info)作为漫游计费信息的粒度的指示(Roaming charging infor level)的取值时，表明漫游计费信息的粒度为以业务为粒度。表一的业务信息(Service Info)可以包含rating group(费率组),业务标识(service ID)、业务类型、和/或Flow Information。rating group(费率组)和/或业务标识(service ID)用于标识一个业务，业务类型用于标识一类业务。Flow Information用于标识业务的业务数据流的流特征。例如，如果业务信息(Service Info)只包含rating group或service ID参数，则表一的漫游计费配置信息为用户的由rating group或service ID标识的业务的漫游计费配置信息。如果业务信息(Service Info)包含rating group或service ID参数，还包含flow information,则flow information参数中的流特征为由rating group或service ID参数标识的业务的流特征。
在表一所示的漫游计费配置信息还可以包括per UPF参数，指在用户的PDU会话使用多个UPF时，是按各UPF上报的计费信息分开上报给漫游计费系统，还是将各UPF上报的计费信息合并后上报给漫游计费系统。
在表一所示的漫游计费配置信息还可以包括多接入上报指示或漫游计费信息上报条件这两个参数。这两个参数的说明可参见前述参数的6或7的介绍。本申请实施例在些不再详述。
步骤304.SMF根据漫游计费配置信息，生成漫游计费信息。
SMF可以是V-SMF，也可以是H-SMF，以下SMF以V-SMF为例。
通常，在归属路由(Home Routed，HR)漫游架构中(即：用户在拜访网接入的业务数据流路由需要通过归属网UPF)，V-SMF和H-SMF都可以根据漫游计费配置信息生成漫游计费信息。
SMF根据漫游计费配置信息确定需要生成的漫游计费信息，并为PDU会话生成漫游计费信息。这里漫游计费信息指根据采集的计费信息生成的要上报的计费信息。
SMF确定生成的漫游计费信息具体方法：
若SMF确定漫游计费配置信息中的漫游计费信息的粒度(Roaming charging info level)指示为以QoS Flow为粒度，则确定获取QoS Flow对应的计费信息，并将QoS flow对应的计费信息写入漫游计费信息。SMF在QoS Flow对应的触发器(trigger)满足时，将QoS flow的计费信息写入漫游计费信息中。写入漫游计费信息中的QoS flow的计费信息包括QoS Flow标识以及与该QoS flow对应的上/下行业务数据流的流量值等。
若SMF确定漫游计费配置信息中的漫游计费信息的粒度(Roaming charging info level)指示以业务粒度(即：Service粒度)，则确定获取Service的计费信息，并将Service的计费信息写入漫游计费信息。SMF在Service对应的触发器满足时，将Service的计费信息写入漫游计费信息中。具体的，若漫游Profile进一步包括了service info，则SMF根据Service Info中携带的费率组和/或业务标识或业务类型生成漫游计费信息(即：将该费率组、业务标识、或业务类型对应的使用量分别写入漫游计费信息中，在漫游计费信息中包括该费率组、业务标识、或业务类型对应的使用量)。使业务类型对应的使用为可以是业务类型对应的时长，或业务类型对应的上/下行流量的值。若漫游Profile未包括service info，则SMF针对该PDU会话中所有的费率组生成漫游计费信息(即：将每个费率组对应的使用量(可以为上/下行流量或时长)分别写入漫游计费信息中。也就是说，若漫游Profile未包括service info，在漫游计费信息中包括了每个费率组对应的使用量。。另一种可选实现中，SMF将Service的计费信息写入漫游计费信息的同时，也将Service对应QoS Flow计费信息业务写入漫游计费信息中。
若SMF确定漫游计费配置信息中的漫游计费信息的粒度(Roaming charging info level)指示以PDU session为粒度，则确定需要获取PDU会话的计费信息，并将PDU会话的计费信息写入漫游计费信息。在漫游计费信息中包括PDU会话总的上下行流量值(不区分业务、也不区分QoS flow)。
若SMF为VSMF且确定有归属网切片标识，则获取该PDU会话所在的切片对应的归属网的网络切片标识，并将获取的归属网的网络切片标识写入漫游计费信息中。
若漫游计费配置信息中包括漫游场景中的多UPF的上报指示为各UPF分别上报，则SMF根据该多UPF上报指示在漫游计费信息中分别写入各UPF上报的计费信息(比如针对同一费率组，UPF1上报了50M，UPF2上报100M，则在漫游计费信息中分别携带了UPF1的流量50M，UPF2的流量100M)。若漫游计费配置信息中未包括多UPF的上报指示，则SMF将多个UPF上的计费信息汇总后写入漫游计费信息(比如同一费率组，UPF1上报了50M，UPF2上报100M，则汇总为该费率组对应的流量为150M)；
若漫游计费配置信息中的包括多接入PDU会话(MA PDU session)的上报指示，则SMF根据多接入PDU会话的上报指示的区分接入方式收集计费信息，并在漫游计费信息中分别写入该PDU会话的与各接入方式对应的计费信息(比如在漫游计费信息中写入：3GPP接入用了50M，非3GPP接入用了100M)。若漫游计费配置信息中未包括多接入PDU会话上报指示，则SMF将各接入方式对应的计费信息汇总后写入漫游计费信息(比如3GPP接入用了50M，非3GPP接入用了100M，则在漫游计费信息中写入共使用了150M)；
SMF还可以获取PDU会话的其他信息(如SMF地址、RAT type等)并写入漫游计费信息中。
若漫游计费配置信息中包括漫游计费信息上报条件，则SMF在该漫游计费信息上报条件指明的上报条件满足时，生成漫游计费信息并向漫游计费系统上报。
V-SMF生成的漫游计费信息包括Service的计费信息及其对应的QoS Flow的计费信息，示例如表二所示：
Figure PCTCN2022089213-appb-000002
Figure PCTCN2022089213-appb-000003
表二
参见表二，表二为根据一个UPF上报的信息生成的漫游计费信息包括QoS flow的漫游计费信息和Service的漫游计费信息例子。在表二所示的漫游计费信息中示出了PDU会话中一个QoS flow(对应一个QFI container实例)的例子，如果PDU包括多个QFI container,每个QFI container都包含表二中的Multiple QFI container下层参数的一个或多个。
在表二中，一个Multiple QFI container参数包括一个QFI container infomration，表明一个QFI容器的详细信息。即一个Multiple QFI container对应一个QoS流的相关信息。表二中Multiple QFI container下层的触发器(triggers)为与该QoS流对应的触发器。触发器生效的时间(trigger timestamp)为与该QoS流对应的触发器生效时间。使用时长(time)为与该QoS流对应的使用时长。使用流量信息等为与该QoS流对应的使用流量。其中，表二中的time,total volume,uplink volume,和/或downlink volume为与该QoS流的使用量。
在表二中，一个QoS流可以对应一个或多个业务的数据流(Service)。一个业务数据流用一个multiple service container表示。表二中示出了一个业务容器(Multiple service container)。一个Multiple service container参数表示一个业务的数据流的信息。一个Multiple service container包括rating group,表明该Service对应的费率组。Service identifier表明该Service对应的业务标识。Triggers表明生成该Service的计费信息的触发器。Time,total volume,uplink volume和/或downlink volume为该Service的使用量。
在表二中，一个QFI container infomration，表明一个QFI容器的详细信息。一个QFI container infomration包括如下信息的一个或多个参数,比如：QoS flow ID，Time of first usage，Time of last usage，QoS Information，User location information，UE time zone和/或rat type。QFI container infomration包含的各参数的意义可参考表二中的解释列。
若漫游计费配置信息中包括多UPF的上报指示，如果一个PDU会话有多个UPF，则V-SMF会针对每一个UPF生成包含表二中一个Roaming QBC information(包括下层参数)。
V-SMF生成的漫游计费信息包括Service的计费信息,但不包括QoS flow的计费信息示例如表三所示：
Figure PCTCN2022089213-appb-000004
表三
参见表三，表三为V-SMF根据一个UPF上报的信息生成的漫游计费信息。该漫游计费信息包括Service的漫游计费信息例子。在表三中，一个multiple service container表明一个业务数据流的计费信息。一个multiple service container包含的参数可参考针对表二的相应描述。如果一个PDU会话有多个业务数据流，针对PDU会话的漫游计费信息可以包含多个multiple service container,每一个multiple service container对应一个业务，参数包含表三中multiple service container下层参数的一个或多个参数。
若漫游计费配置信息中包括多UPF的上报指示，如果一个PDU会话有多个UPF，则V-SMF会针对每一个UPF生成包含表三中一个Roaming information(包括下层参数)。
V-SMF生成的漫游计费信息包括PDU会话粒度的计费信息的示例如表四所示：
Figure PCTCN2022089213-appb-000005
表四
参见表四，表四为以PDU会话为粒度的漫游计费信息例子。若漫游计费配置信息中包括多UPF的上报指示，如果一个PDU会话有多个UPF，则V-SMF会针对每一个UPF生成包含表四中一个Roaming information(包括下层参数)的漫游计费信息。
表四中包含的参数可参考表四中第二列的相应描述，本申请实施例在此不再详述。
在HR的漫游场景下，H-SMF生成的漫游计费信息的方法、时间及生成的漫游计费信息与上述V-SMF类似。
步骤306.SMF向漫游计费系统上报步骤304生成的漫游计费信息。
步骤308.漫游计费系统根据接收到的漫游计费信息生成该用户的PDU会话的漫游计费话单(Charging Data Record,CDR)，该漫游CDR包含漫游计费信息。
步骤310.漫游计费系统在确定生成详细数据记录(detailed data record,DDR)时，漫游计费系统根据漫游协议、漫游计费Profile和漫游CDR，生成DDR。
漫游计费系统确定生成详细数据记录的方法可以是漫游计费系统根据漫游协议规定的时间点或者时间周期生成DDR。
漫游计费系统生成DDR的方法可以是：
-漫游计费系统确定生成DDR的粒度。漫游计费系统可以根据该漫游计费Profile确定，或者根据漫游协议确定生成DDR的粒度；
-若漫游计费系统确定生成DDR的粒度为QoS Flow粒度(即：将QoS flow的计费信息写入DDR)，则漫游计费系统为每个QoS Flow生成一个DDR，并将该PDU会话的CDR中的该QoS Flow的计费信息(比如：QoS Flow的标识、对应流量等)写入该DDR。若漫游计费系统确定生成DDR的粒度为Service粒度(即：将一个Serivce flow的计费信息写入DDR)，则漫游计费系统为每个Service生成一个DDR，并将该PDU会话的CDR中的该Service计费信息(比如：费率组、对应流量等)或者该Service的计费信息及其对应的QoS flow的计费信息组合计费信息写入该DDR。或者若漫游计费系统确定生成DDR的粒度为PDU会话粒度(即：将PDU会话的计费信息写入DDR)，则漫游计费系统为每个PDU会话生成一个DDR，并将该PDU会话的CDR中的该PDU会话的计费信息(比如：PDU 会话的总流量等)写入该DDR。
-漫游计费系统还可以将该PDU会话的CDR中的该PDU会话相关的信息(如PDU会话标识、PDU地址等)写入该用户的DDR。
-漫游计费系统还可以将该PDU会话的CDR中的该PDU所属网络切片标识写入该用户的DDR。具体的，若漫游计费系统可以从该PDU会话的CDR中获取该切片的归属网的网络切片标识，则将该归属网的网络切片标识写入该用户的DDR。
具体漫游DDR包含的部分参数示例参见表五。
漫游计费系统生成的DDR包含的部分信息可以参考表五所示:
Figure PCTCN2022089213-appb-000006
Figure PCTCN2022089213-appb-000007
表五
参考表五，若漫游计费配置信息中包括多UPF的上报指示，如果一个PDU会话有多个UPF，则为每一个UPF生成一个包含如表五所示部分参数的DDR记录。若漫游计费配置信息中包括多接入的上报指示，如果一个PDU会话有多个接入类型，则漫游计费系统为每种接入类型生成生成一个包含如表五所示部分参数的DDR记录。
通过本方法，会话管理功能获取漫游计费的profile中漫游计费信息粒度、业务数据流的信息、多UPF上报指示、多接入上报指示、漫游计费信息上报条件，从而可以根据漫游计费的profile生成支持多种清算需求的漫游计费信息。使得漫游计费系统可以根据不同漫游计费配置信息进行灵活的漫游清算，并在出现冲突时，为冲突解决提供了数据支撑。
图4为本申请实施例提供的基于HR漫游游场景下的计费的方法流程示意图。本实施例中，结合图1B该漫游计费方法包括如下步骤：
步骤401.用户设备(user equipment,UE)向V-SMF发送PDU会话的第一请求，以请求为用户建立PDU会话。该第一请求携带用户信息。
步骤402.V-SMF在收到该第一请求后，根据该第一请求中携带的用户信息确定UE为漫入UE，获取适用于该UE的PDU会话漫游计费profile,向V-漫游计费系统发送第一计费资源创建请求，该第一计费资源创建请求包括适用于该UE的PDU会话漫游计费profile。具体的，V-SMF获取配置在V-SMF的漫游计费配置信息，该漫游计费配置信息包含的详细信息参考骤302，本申请实施例不再详述。
第一计费资源创建请求用于请求V-CHF该用户PDU会话生成计费资源，以对由V-SMF上报的UE的PDU会话的漫游计费信息进行处理。
步骤403.V-CHF在收到第一计费资源创建请求后，根据第一计费资源创建请求为PDU会话创建第一计费资源(包括分配计费资源标识)，并向V-SMF返回第一计费资源创建响应。
V-CHF根据V-SMF上报的用于该UE的PDU会话的漫游计费profile，确定是否更新用于该UE的PDU会话的漫游计费配置信息。若更新，V-CHF生成用于该UE的漫游计费profile更新信息。具体的，V-CHF可以根据漫游协议确定是否需要更新用于该UE的PDU会话的漫游计费Profile。如：漫游协议指明在新季度开始新的协议内容，则V-CHF据此判断需要在季度开始更新原有漫游Profile。
第一计费资源创建响应包含V-HF提供的用于该UE的漫游计费配置息的更新信息。该漫游计费配置信息的更新信息包含的信息描述参考骤304。该漫游计费配置信息的更新信息用于更新V-SMF在步骤402中获取的配置的漫游计费配置信息。第一计费资源创建响应中包含的漫游计费profile可以只包含漫游计费配置信息中的需更新的一个或多个参数，也可以包含漫游计费配置信息的全部信息。
步骤404.V-SMF向H-SMF发送该PDU会话的第二请求，以请求H-SMF完成PDU会话建立。该PDU会话的第二请求中携带该PDU会话建立请求的信息，以及携带了V-SMF为该用户的PDU会话使用的漫游计费profile。携带在PDU会话的第二请求中的漫游计费profile可以是V-SMF获取的配 置的漫游计费profile,也可以是使用V-CHF发送的漫游计费profile更新后的漫游计费profile。
步骤404中的漫游计费profile为当前该用户的PDU会话使用的漫游计费profile。若步骤403中V-CHF未提供用于该UE的漫游计费profile更新信息，则步骤404中携带的漫游计费profile为配置在V-SMF的漫游计费profile，若步骤403中V-CHF提供了用于该UE的漫游计费profile的更新信息，则步骤404中携带的漫游计费profile为V-CHF更新后的漫游计费profile。
步骤405.H-SMF接收到该PDU会话的第二请求后，向H-CHF发送第二计费资源创建请求。第二计费资源请求用于请求H-CHF为该用户PDU会话创建计费资源，以对由V-SMF上报的UE的PDU会话的漫游计费信息进行处理。第二计费资源创建请求携带了V-SMF发送的漫游计费profile。携带在第二计费资源创建中的漫游计费profile可以是V-SMF获取的配置的漫游计费profile,也可以是使用V-CHF发送的漫游计费profile更新后的漫游计费profile。
步骤406.H-CHF在收到第二计费资源创建请求后，根据第二计费资源创建请求为该PDU会话创建(create)第二计费资源(包括为第二计费资源分配标识)，并向H-SMF返回第二计费资源建立响应。
H-CHF在收到第二计费资源创建请求后，根据H-SMF上报的用于该UE的PDU会话的漫游计费profile，确定是否需要更新用于该UE的PDU会话的漫游计费Profile。比如，H-CHF可以根据漫游协议、用户签约变化和/或新清算场景需要等确定是否需要更新用于该UE的PDU会话的漫游Profile。如：要将按月清算调整为按周清算，再比如，H-CHF根据漫游协议要求提供业务信息(比如该业务的费率组)等，则确定需要更新用于该UE的PDU会话的漫游Profile。若H-CHF确定更新用于该UE的PDU会话的漫游计费Profile，则生成由归属网的漫游计费profile(简称H-profile)，H-profile包含的信息描述参考骤304。该归属网的漫游计费profile用于提供给V-SMF以更新V-SMF在步骤404或步骤405中提供给H-SMF的用于该用户PDU会话的漫游计费profile的信息。该提供给H-SMF的用于该用户PDU会话的漫游计费profile的信息V-SMF获取的配置的漫游计费profile(拜访网的漫游计费系统没有更新过)，或拜访网的漫游计费系统更新后的漫游计费profile.
第二计费资源创建响应中包含归属网的漫游计费profile以及第二计费资源的标识。第二计费资源建立响应中包含的H-profile可以只包含需更新的一个或多个参数，也可以包含H-profile的全部信息。
步骤407.H-SMF向V-SMF发送该PDU会话的第二请求的响应。该PDU会话的第二请求的响应包含归属网的漫游计费profile。
步骤408-409.V-SMF在接收到H-SMF返回的该PDU会话的第二请求的响应后，若该PDU会话的第二请求的响应携带了归属网的漫游计费profile，则向V-CHF上报该归属网的漫游计费profile，并接收V-CHF返回的接收了归属网的漫游计费profile的响应。
V-SMF在收到该PDU会话的第二请求的响应后，使用归属网的漫游计费profile更新该用户PDU会话的漫游计费Profile(配置的漫游计费profile,或已使用拜访网的漫游计费profile更新后的漫游计费profile)，并根据更新后的漫游计费profile生成该用户PDU会话的漫游计费信息。
进一步的，V-SMF还根据该更新后的漫游计费profile生成该用户PDU会话的新的用于计费信息上报的策略，并向UPF下发该用户PDU会话的新的用于计费信息上报的策略。
步骤410.V-SMF向UE发送PDU会话的第一响应，以指示为UE的第一会话(如PDU会话)建立完成。
步骤411-412，V-SMF在计费上报条件满足时，从V-UPF获取该用户PDU会话的使用信息(图中未示出)，根据V-UPF上报的信息生成漫游计费信息。V-SMF向V-漫游计费系统发送第三计费请求，第三计费请求携带V-SMF生成的漫游计费信息。V-SMF接收V-CHF返回的第三计费响应。
V-SMF生成的漫游计费信息可参考表二至表四所示，或步骤306的描述，本申请实施例在些不再详述。
步骤413.V网漫游计费系统根据接收到的漫游计费信息生成该用户PDU会话的漫游计费话单(Charging Data Record,CDR)。该漫游CDR包含该漫游计费信息。
步骤414.V网漫游计费系统在确定生成详细数据记录(detailed data record,DDR)时，根据该用户PDU会话的漫游CDR生成该用户的详细数据记录(detailed data record,DDR)。V网漫游计费系统生成DDR参考步骤310的描述，本申请实施例在此不再详述。
步骤411’-步骤414’参考步骤411-414的描述。H-SMF根据H-UPF上报的PDU会话的使用信息，生成漫游计费信息。H-SMF将生成的漫游计费信息发送的H网漫游计费系统。H网漫游计费系统根据接收的漫游计费信息生成该用户PDU会话的漫游CDR。H网漫游计费系统在确定要生成DDR时，根据该用户PDU会话的漫游CDR生成该用户的DDR。
后续，V网漫游计费系统和归属网漫游计费系统根据生成的DDR和漫游协议进行计费信息汇总，生成UDR，具体的，可以根据漫游协议规定，按照用户组汇总计费信息(如将一组用户的用量进行汇总)、或者按照业务汇总计费信息(如将一组用户使用的同一业务的用量进行汇总)等，这里的用量可以为流量。
后续，V网漫游计费系统将生成的UDR发送给归属网漫游计费系统，归属网漫游计费系统用本地生成的UDR验证V网漫游计费系统发送的UDR，进行UDR的验证。
后续冲突解决及清算步骤参见GSMA定义的BCE流程。
本申请实施例可以根据上述方法示例对会话管理功能101和漫游计费系统102等设备进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
比如，以采用集成的方式划分各个功能模块的情况下，图5为一种漫游计费装置(或计费触发装置)500的结构示意图。该装置500可以是上述实施例中的会话管理功能101，也可以是会话管理功能101内的芯片，本申请实施例对此不作具体限定。如图5所示，该装置包括：获取模块501、处理模块502和发送模块503。
获取模块501，用于处理模块确定数据连接会话对应的用户为漫游用户后，获取漫游计费配置信息，漫游计费配置信息包括漫游计费信息粒度指示、业务信息、漫游多用户面功能的上报指示、漫游多接入数据连接会话上报指示、和/或漫游计费信息的上报条件；
处理模块502，用于根据漫游计费信息粒度指示、业务信息、漫游多用户面功能上报指示、漫游多接入数据连接会话上报指示、和/或漫游计费信息上报条件，计费触发装置生成数据连接会话的漫游计费信息；
发送模块503，用于向漫游计费系统上报漫游计费信息。
可选的，处理模块502确定协议数据单元数据连接会话对应的用户为漫游用户包括，处理模块502根据用户设备上报的用户的归属网标识确定用户为漫游用户。
可选的，获取模块501获取用户的漫游计费配置信息包括，获取模块获取配置在计费触发装置的漫游计费配置信息作为漫游计费配置信息。
可选的，获取模块501获取用户的漫游计费配置信息包括：获取模块501接收漫游计费系统发送的漫游计费配置信息，获取模块501将漫游计费系统发送的漫游计费配置信息作为漫游计费配置信息。
可选的，漫游计费信息的粒度的指示为：以服务质量流(QoS Flow)为粒度的指示、以业务为粒度的指示、或以数据连接会话为粒度的指示；
当漫游计费信息粒度指示为以QoS Flow为粒度的指示时，漫游计费计息中包含与QoS Flow对应的计费信息；或
当漫游计费信息粒度指示为以业务粒度的指示时，漫游计费计息中包含与业务对应的计费信息；或
当漫游计费信息粒度指示为以数据连接会话为粒度的指示时，漫游计费计息中包含与数据连接会话对应的计费信息。
可选的，处理模块502生成数据连接会话的漫游计费信息包括：当漫游计费信息粒度指示为以业务粒度的指示时，业务对应的计费信息包括数据连接会话中与费率组对应的业务的使用量，或数据连接会话中与业务标识对应的业务的使用量，或数据连接会话中与业务类型对应的业务的使用量，或数据连接会话中与费率组和业务标识对应的业务的使用量。
图6为一种漫游计费系统600的结构示意图。该漫游计费系统600可以是上述实施例中的漫游计费系统102，也可以是漫游计费系统102内的芯片，本申请实施例对此不作具体限定。如图6所示，该装置包括：接收模块601、处理模块602和发送模块603。其中，
接收模块601，用于接收计费触发装置体发送的用户的数据连接会话的计费资源创建请求，计费资源创建请求包括用户的数据连接会话信息；
处理模块602，用于生成第二漫游计费配置信息，第二漫游计费配置信息包括漫游计费信息粒度指示、业务信息、漫游多用户面功能的上报指示、漫游多接入数据连接会话的上报指示、和/或漫游计费信息上报条件；
发送模块603，用于向计费触发装置发送第第二漫游计费配置信息。
接收模块601进一步用于，接收计费触发装置发送的漫游计费信息，漫游计费信息根据漫游计费系统发送的第二漫游计费配置信息生成。
可选的，计费资源创建请求包含第一漫游计费配置信息，第一漫游计费配置信息包括漫游计费信息粒度指示、业务信息、漫游多用户面功能的上报指示、漫游多接入数据连接会话的上报指示、和/或漫游计费信息上报条件，第二漫游计费配置信息用于计费触发装置更新计费触发装置中的第一漫游计费配置信息。
可选的，处理模块602，进一步用于根据计费资源创建请求中携带的第一漫游计费配置信息，确定生成用于更新第一漫游计费配置信息的第二漫游计费配置信息。
可选的，处理模块602，进一步用于生成用户的计费话单(Charging Data Record，CDR)，计费话单包括漫游计费信息。
作为另一可选方式，所述图6中的模块还可以用来执行图3-图4的方法流程中漫游计费系 统所执行的步骤。
在本实施例中，该装置500以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定应用集成电路(application-specific integrated circuit，ASIC)，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到装置500可以采用图2所示的形式。
比如，图2中的处理器201可以通过调用存储器203中存储的计算机执行指令，使得漫游计费系统执行上述方法实施例中的漫游计费方法。
具体的，图6中的接收模块601、处理模块602和发送模块603，以及图5中的获取模块501、处理模块502和发送模块503的功能/实现过程可以通过图2中的处理器201调用存储器203中存储的计算机执行指令来实现。
可选的，当该装置600，和/或500是芯片时，则各模块的功能/实现过程还可以通过软件或电路等来实现。可选地，当该装置600，和/或500是芯片时，存储器203可以为芯片内的存储单元，如寄存器、缓存等。当然，本申请实施例对此不作具体限定。
由于本申请实施例提供的装置可用于执行上述计费方法，因此其所能获得的技术效果可参考上述方法实施例，在此不再赘述。
其中，上述计费触发装置600，和/或漫游计费系统500可以实现在集成电路、无线射频集成电路、印刷电路板等上。同时该装置可以是自立设备，也可以是较大设备的一部分。在本实施例中，该计费触发装置600，和/或漫游计费系统500以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定ASIC，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。
图7为本申请提供的系统示意图，包括计费触发装置110和漫游计费系统120.计费触发装置可用于执行图3，图4中的会话管理功能执行的步骤,也可以执行图5中漫游计费装置的功能。漫游计费系统120可用于执行图3，图4中的漫游计费系统执行的步骤。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件程序实现时，可以全部或部分地以计算机程序产品的形式来实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或者数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可以用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)，光介质(例如，DVD)、或者半导体介质(例如固态硬盘(solid state disk，SSD))等。
尽管在此结合各实施例对本申请进行了描述，然而，在实施所要求保护的本申请过程中，本领域技术人员通过查看所述附图、公开内容、以及所附权利要求书，可理解并实现所述公开实施例的其他变化。在权利要求中，“包括”(comprising)一词不排除其他组成部分或 步骤，“一”或“一个”不排除多个的情况。单个处理器或其他单元可以实现权利要求中列举的若干项功能。相互不同的从属权利要求中记载了某些措施，但这并不表示这些措施不能组合起来产生良好的效果。
尽管结合具体特征及其实施例对本申请进行了描述，显而易见的，在不脱离本申请的精神和范围的情况下，可对其进行各种修改和组合。相应地，本说明书和附图仅仅是所附权利要求所界定的本申请的示例性说明，且视为已覆盖本申请范围内的任意和所有修改、变化、组合或等同物。显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (33)

  1. 一种漫游计费方法，其特征在于，包括：
    计费触发装置确定数据连接对应的用户为漫游用户后，获取漫游计费配置信息，所述漫游计费配置信息包括漫游计费信息粒度指示、业务信息、漫游多用户面功能的上报指示、漫游多接入数据连接会话上报指示、和/或漫游计费信息的上报条件；
    根据所述漫游计费信息粒度指示、业务信息、漫游多用户面功能上报指示、漫游多接入数据连接会话上报指示、和/或漫游计费信息上报条件，所述计费触发装置生成所述数据连接会话的漫游计费信息；
    所述计费触发装置向漫游计费系统上报所述漫游计费信息。
  2. 根据权利要求1所述的方法，其特征在于，所述计费触发装置确定协议数据单元数据连接会话对应的用户为漫游用户包括：
    所述计费触发装置根据用户设备上报的所述用户的归属网标识确定所述用户为漫游用户。
  3. 根据权利要求1或2所述的方法，其特征在于，所述获取用户的漫游计费配置信息包括：
    所述计费触发装置获取配置在所述计费触发装置的漫游计费配置信息作为所述漫游计费配置信息。
  4. 根据权利要求1-3任一所述的方法，其特征在于，所述获取用户的漫游计费配置信息包括：
    所述计费触发装置接收所述漫游计费系统发送的漫游计费配置信息；
    所述计费触发装置将所述漫游计费系统发送的漫游计费配置信息作为所述漫游计费配置信息。
  5. 根据权利要求1-4任一所述的方法，其特征在于，漫游计费信息的粒度的指示为：以服务质量流(QoS Flow)为粒度的指示、以业务为粒度的指示、或以数据连接会话为粒度的指示；
    当所述漫游计费信息粒度指示为所述以QoS Flow为粒度的指示时，所述漫游计费计息中包含与所述QoS Flow对应的计费信息；或
    当所述漫游计费信息粒度指示为所述以业务粒度的指示时，所述漫游计费计息中包含与所述业务对应的计费信息；或
    当所述漫游计费信息粒度指示为所述以数据连接会话为粒度的指示时，所述漫游计费计息中包含与所述数据连接会话对应的计费信息。
  6. 根据权利要求5所述的方法，其特征在于，所述计费触发装置生成所述数据连接会话的漫游计费信息包括：
    当所述漫游计费信息粒度指示为所述以业务粒度的指示时，所述业务对应的计费信息包括所述数据连接会话中与费率组对应的业务的使用量，或所述数据连接会话中与业务标识对应的业务的使用量，或所述数据连接会话中与业务类型对应的业务的使用量，或所述数据连接会话中与费率组和业务标识对应的业务的使用量。
  7. 根据权利要求5或6所述的方法，其特征在于，
    所述漫游计费信息粒度为所述以业务为粒度的指示且所述漫游计费配置信息还包括业务相关信息，所述业务相关信息包括业务类型、费率组、和/或业务标识，所述漫游计费计息进一步包含所述业务类型、所述费率组、和/或业务标识。
  8. 根据权利要求5-7任一所述的方法，其特征在于，
    所述计费触发装置为拜访网的计费触发装置时所述漫游计费信息还包括所述归属网的网络切片标识和所述拜访网的网络切片标识；和/或
    所述漫游计费配置信息还包括多用户面功能UPF的上报指示，所述漫游计费信息还包括所述数据连接会话的每个户面功能上报的计费信息或者包括所述数据连接会话的多个UPFs上报的计费信息合并后的计费信息；和/或
    所述漫游计费配置信息包括所述多接入数据连接会话的上报指示，所述漫游计费信息包括所述数据连接会话的每个接入对应的计费信息或包括所述数据连接会话中所述多个接入对应的计费信息合并后的计费信息。
  9. 根据权利要求1～8任一所述的方法，其特征在于，当所述漫游计费配置信息包括漫游计费信息上报条件，所述生成所述漫游计费信息包括：
    所述计费触发装置确定所述漫游计费信息上报条件满足，生成所述漫游计费信息，并向所述漫游计费系统上报所述漫游计费信息。
  10. 一种漫游计费方法，其特征在于，包括：
    漫游计费系统接收计费触发装置体发送的用户的数据连接会话的计费资源创建请求，所述计费资源创建请求包括所述用户的数据连接会话信息；
    所述漫游计费系统生成第二漫游计费配置信息，所述第二漫游计费配置信息包括漫游计费信息粒度指示、业务信息、漫游多用户面功能的上报指示、漫游多接入数据连接会话的上报指示、和/或漫游计费信息上报条件；
    所述漫游计费系统向所述计费触发装置发送所述第第二漫游计费配置信息；
    所述漫游计费系统接收所述计费触发装置发送的所述漫游计费信息，所述漫游计费信息根据所述漫游计费系统发送的第二漫游计费配置信息生成。
  11. 根据权利要求10所述的计费方法，其特征在于，该方法进一步包括：
    所述计费资源创建请求包含第一漫游计费配置信息，所述第一漫游计费配置信息包括漫游计费信息粒度指示、业务信息、漫游多用户面功能的上报指示、漫游多接入数据连接会话的上报指示、和/或漫游计费信息上报条件，所述第二漫游计费配置信息用于所述计费触发装置更新所述计费触发装置中的第一漫游计费配置信息。
  12. 根据权利要求11所述的计费方法，其特征在于，该方法进一步包括：
    根据所述计费资源创建请求中携带的第一漫游计费配置信息，所述漫游计费系统确定生成用于更新所述第一漫游计费配置信息的第二漫游计费配置信息。
  13. 根据权利要求10～12任一所述的计费方法，其特征在于，该方法进一步包括：
    所述漫游计费系统生成所述用户的计费话单(Charging Data Record，CDR)，所述计费 话单包括所述漫游计费信息。
  14. 根据权利要求13所述的计费方法，其特征在于，该方法进一步包括：
    所述漫游计费计息中包含与所述QoS Flow对应的计费信息，则所述计费话单包括所述QoS Flow对应的计费信息；或
    所述漫游计费计息中包含与所述业务对应的计费信息，则所述计费话单包括所述业务对应的计费信息；或
    所述漫游计费计息中包含与所述数据连接会话对应的计费信息，则所述计费话单包括所述数据连接会话对应的计费信息。
  15. 根据权利要求13或14所述的计费方法，其特征在于，所述计费触发装置为拜访网的计费触发装置时所述漫游计费信息包括所述数据连接会话对应的所述归属网的网络切片标识，则所述计费话单包括所述归属网的网络切片标识。
  16. 根据权利要求13～15任一所述的计费方法，其特征在于，所述漫游计费系统生成详细数据记录，在所述详细数据记录中包括QoS Flow对应的详细数据记录或者业务对应的详细数据记录或者所述数据连接会话对应的详细数据记录，所述详细数据记录基于所述计费话单生成。
  17. 一种漫游计费装置，其特征在于，包括：
    获取模块，用于处理模块确定数据连接会话对应的用户为漫游用户后，获取漫游计费配置信息，所述漫游计费配置信息包括漫游计费信息粒度指示、业务信息、漫游多用户面功能的上报指示、漫游多接入数据连接会话上报指示、和/或漫游计费信息的上报条件；
    所述处理模块，用于根据所述漫游计费信息粒度指示、业务信息、漫游多用户面功能上报指示、漫游多接入数据连接会话上报指示、和/或漫游计费信息上报条件，所述计费触发装置生成所述数据连接会话的漫游计费信息；
    发送模块，用于向漫游计费系统上报所述漫游计费信息。
  18. 根据权利要求17所述的装置，其特征在于，所述处理模块确定数据连接会话对应的用户为漫游用户包括：
    所述处理模块根据用户设备上报的所述用户的归属网标识确定所述用户为漫游用户。
  19. 根据权利要求17或18所述的装置，其特征在于，所述获取模块获取用户的漫游计费配置信息包括：
    所述获取模块获取配置在所述计费触发装置的漫游计费配置信息作为所述漫游计费配置信息。
  20. 根据权利要求17-19任一所述的装置，其特征在于，所述获取模块获取用户的漫游计费配置信息包括：
    所述获取模块接收所述漫游计费系统发送的漫游计费配置信息；
    所述获取模块将所述漫游计费系统发送的漫游计费配置信息作为所述漫游计费配置信息。
  21. 根据权利要求17-20任一所述的装置，其特征在于，漫游计费信息的粒度的指示为： 以服务质量流(QoS Flow)为粒度的指示、以业务为粒度的指示、或以数据连接会话为粒度的指示；
    当所述漫游计费信息粒度指示为所述以QoS Flow为粒度的指示时，所述漫游计费计息中包含与所述QoS Flow对应的计费信息；或
    当所述漫游计费信息粒度指示为所述以业务粒度的指示时，所述漫游计费计息中包含与所述业务对应的计费信息；或
    当所述漫游计费信息粒度指示为所述以数据连接会话为粒度的指示时，所述漫游计费计息中包含与所述数据连接会话对应的计费信息。
  22. 根据权利要求21所述的装置，其特征在于，所述处理模块生成所述数据连接会话的漫游计费信息包括：
    当所述漫游计费信息粒度指示为所述以业务粒度的指示时，所述业务对应的计费信息包括所述数据连接会话中与费率组对应的业务的使用量，或所述数据连接会话中与业务标识对应的业务的使用量，或所述数据连接会话中与业务类型对应的业务的使用量，或所述数据连接会话中与费率组和业务标识对应的业务的使用量。
  23. 一种漫游计费系统，其特征在于，包括：
    接收模块，用于接收计费触发装置体发送的用户的数据连接会话的计费资源创建请求，所述计费资源创建请求包括所述用户的数据连接会话信息；
    处理模块，用于生成第二漫游计费配置信息，所述第二漫游计费配置信息包括漫游计费信息粒度指示、业务信息、漫游多用户面功能的上报指示、漫游多接入数据连接会话的上报指示、和/或漫游计费信息上报条件；
    发送模块，用于向所述计费触发装置发送所述第第二漫游计费配置信息；
    所述接收模块进一步用于，接收所述计费触发装置发送的所述漫游计费信息，所述漫游计费信息根据所述漫游计费系统发送的第二漫游计费配置信息生成。
  24. 根据权利要求23所述的计费系统，其特征在于，
    所述计费资源创建请求包含第一漫游计费配置信息，所述第一漫游计费配置信息包括漫游计费信息粒度指示、业务信息、漫游多用户面功能的上报指示、漫游多接入数据连接会话的上报指示、和/或漫游计费信息上报条件，所述第二漫游计费配置信息用于所述计费触发装置更新所述计费触发装置中的第一漫游计费配置信息。
  25. 根据权利要求23所述的计费系统，其特征在于，
    所述处理模块，进一步用于根据所述计费资源创建请求中携带的第一漫游计费配置信息，确定生成用于更新所述第一漫游计费配置信息的第二漫游计费配置信息。
  26. 根据权利要求23-25任一所述的计费系统，其特征在于，该方法进一步包括：
    所述处理模块，进一步用于生成所述用户的计费话单(Charging Data Record，CDR)，所述计费话单包括所述漫游计费信息。
  27. 一种漫游计费装置，包括通信接口、存储器，一个或多个处理器；其中，一个或多个程序被存储在所述存储器中；其特征在于，所述一个或多个处理器在执行所述一个或多个程序时，使得所述电子设备实现如权利要求1至9任一项所述的方法。
  28. 一种计算机存储介质，其特征在于，包括计算机指令，当所述计算机指令在电子设备上运行时，使得所述电子设备执行如权利要求1至9任一项所述的方法。
  29. 一种计算机程序产品，其特征在于，当所述计算机程序产品在计算机上运行时，使得所述计算机执行如权利要求1至9任一项所述的方法。
  30. 一种漫游计费系统，包括通信接口、存储器，一个或多个处理器；其中，一个或多个程序被存储在所述存储器中；其特征在于，所述一个或多个处理器在执行所述一个或多个程序时，使得所述电子设备实现如权利要求10至16任一项所述的方法。
  31. 一种计算机存储介质，其特征在于，包括计算机指令，当所述计算机指令在电子设备上运行时，使得所述电子设备执行如权利要求10至16任一项所述的方法。
  32. 一种计算机程序产品，其特征在于，当所述计算机程序产品在计算机上运行时，使得所述计算机执行如权利要求10至16任一项所述的方法。
  33. 一种系统，其特征在于，包括计费触发装置和漫游计费系统，
    所述计费触发装置用于执行如权利要求1至9任一项所述的方法，所述漫游计费系弘用于执行如权利要求10至16任一项所述的方法。
PCT/CN2022/089213 2021-10-01 2022-04-26 一种计费方法和装置 WO2023050787A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202111166971.X 2021-10-01
CN202111166971.XA CN115942267A (zh) 2021-10-01 2021-10-01 一种计费方法和装置

Publications (1)

Publication Number Publication Date
WO2023050787A1 true WO2023050787A1 (zh) 2023-04-06

Family

ID=85780406

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/089213 WO2023050787A1 (zh) 2021-10-01 2022-04-26 一种计费方法和装置

Country Status (2)

Country Link
CN (1) CN115942267A (zh)
WO (1) WO2023050787A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111865623A (zh) * 2019-03-28 2020-10-30 华为技术有限公司 计费规则绑定的方法、设备及系统
CN112449316A (zh) * 2019-08-30 2021-03-05 华为技术有限公司 一种漫游计费的处理方法、装置及系统
CN112823536A (zh) * 2018-08-10 2021-05-18 诺基亚技术有限公司 漫游场景中的协调会话计费

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112823536A (zh) * 2018-08-10 2021-05-18 诺基亚技术有限公司 漫游场景中的协调会话计费
CN111865623A (zh) * 2019-03-28 2020-10-30 华为技术有限公司 计费规则绑定的方法、设备及系统
CN112449316A (zh) * 2019-08-30 2021-03-05 华为技术有限公司 一种漫游计费的处理方法、装置及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
NOKIA, NOKIA SHANGHAI BELL: "Complete description for CHF selection in roaming", 3GPP TSG-SA5 MEETING #121, S5-186254, 28 September 2018 (2018-09-28), XP051544486 *

Also Published As

Publication number Publication date
CN115942267A (zh) 2023-04-07

Similar Documents

Publication Publication Date Title
US11277522B2 (en) Service domain charging systems and methods
US10856183B2 (en) Systems and methods for network slice service provisioning
WO2021218274A1 (zh) 一种通信方法、装置及系统
US11202240B2 (en) Systems and methods for managing and monitoring communication sessions
RU2643451C2 (ru) Система и способ виртуализации функции мобильной сети
JP4414632B2 (ja) ユーザコンフィギュラブルワイヤレスネットワークにおける課金システムおよびワイヤレスネットワークにおけるサービスクリエーションおよび／またはネゴシエーションに対する課金方法
WO2021119216A1 (en) Methods, systems, and computer readable media for providing for network slice management using feedback mechanism
US20120250613A1 (en) Rules system version cloning
WO2021204299A1 (zh) 一种确定策略的方法、装置及系统
US11470202B2 (en) Charging method, apparatus, and system
CN112398662B9 (zh) 一种计费方法、装置及系统
CN109818769A (zh) 发送信息的方法和装置
CN114302426A (zh) 在异质网络控制服务质量的方法、装置、介质及电子设备
JP7227392B2 (ja) 課金方法および装置
WO2023050787A1 (zh) 一种计费方法和装置
WO2023050782A1 (zh) 一种计费方法和设备
CN112910662B (zh) 一种流量信息上报及接收上报方法、设备、介质
WO2023051782A1 (zh) 管理漫游计费配置参数的方法、系统及相关设备
WO2022032517A1 (zh) 通信方法和装置
JP2012039325A (ja) ネットワーク制御方法及びシステム
WO2022032891A1 (zh) 通信方法及装置
Yao et al. Content-Centric and Software-Defined Networking with Big Data
KR20050062329A (ko) 무선패킷서비스게이트웨이지원노드 및 그 자원 할당 방법

Legal Events

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

Ref document number: 22874186

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2022874186

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2022874186

Country of ref document: EP

Effective date: 20240408

NENP Non-entry into the national phase

Ref country code: DE