[go: up one dir, main page]

WO2020143502A1 - Procédé et système permettant d'effectuer un traitement de facturation sur des instances de tranches de réseau et dispositif associé - Google Patents

Procédé et système permettant d'effectuer un traitement de facturation sur des instances de tranches de réseau et dispositif associé Download PDF

Info

Publication number
WO2020143502A1
WO2020143502A1 PCT/CN2019/130238 CN2019130238W WO2020143502A1 WO 2020143502 A1 WO2020143502 A1 WO 2020143502A1 CN 2019130238 W CN2019130238 W CN 2019130238W WO 2020143502 A1 WO2020143502 A1 WO 2020143502A1
Authority
WO
WIPO (PCT)
Prior art keywords
network slice
reporting
ppro
charging
function device
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2019/130238
Other languages
English (en)
Chinese (zh)
Inventor
柴晓前
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of WO2020143502A1 publication Critical patent/WO2020143502A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

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
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/04—Terminal devices adapted for relaying to or from another terminal or user

Definitions

  • the present application relates to the field of communications, and in particular, to a method, system, and related device for charging a network slice instance.
  • 5G (5th Generation) network examples include eMBB (enhanced Mobile Broadband), uRLLC (ultra High-Reliability and Low-Latency Communication, ultra-high reliability and low-latency communication), mMTC ( mass, machine, type, communication, etc. These scenarios have very different requirements for network characteristics.
  • eMBB enhanced Mobile Broadband
  • uRLLC ultra High-Reliability and Low-Latency Communication, ultra-high reliability and low-latency communication
  • mMTC mass, machine, type, communication, etc.
  • mMTC scenario will have a lot of devices, but the throughput of each device may be very low, and the required bandwidth is very small; while eMBB scenarios require almost the opposite characteristics , Because it will have much fewer devices, but each device will send or receive a lot of data, and the required bandwidth is very large; uRLLC scenarios have high requirements for end-to-end latency, such as autonomous driving, the latency requirement is less than 3 milliseconds.
  • the physical network can be divided at the end-to-end level to form a network slice (Network Slice) to achieve traffic grouping, isolation of tenants, and macro-level resource allocation.
  • Network Slice Network Slice
  • the essence of network slicing is a virtual network that runs on top of a shared physical network infrastructure. Operators can create different services based on different service requirements (such as delay, bandwidth, security, and reliability) on the basis of physical networks.
  • the virtual network of service requirements (corresponding to a network slice instance, Network Slice instance, NSI), is used by customers with different network characteristics, so as to improve the utilization rate of network resources and the service quality of network services.
  • the solution for charging the network resources is that the business system triggers the charging system to perform charging based on business events such as the start and end of the business, and the business system counts accurate business information (such as traffic used by the business) , The length of service used, etc.), reported to the billing system, so that the billing system will be based on the evaluation and deduction.
  • business events such as the start and end of the business
  • business system counts accurate business information (such as traffic used by the business) , The length of service used, etc.), reported to the billing system, so that the billing system will be based on the evaluation and deduction.
  • the charging result will not match the operator's investment for the corresponding network slicing instance, which is not conducive to the implementation of the above-mentioned diversified application scenarios, thereby reducing network resources Use efficiency or reduce the service quality of network services.
  • an embodiment of the present application provides a system for charging a network slice instance, the system includes: a network slice charging control function NSCCF device, a network slice management function NSMF device, and a network slice charging function NSCF device , wherein the NSCCF device is used to: determine performance indicator report indication information and send it to the NSMF device, the performance indicator report indication information is used to instruct the NSMF device to perform a performance indicator report operation PPRO, the PPRO
  • the method includes obtaining data corresponding to the network slice performance index of the network slice instance NSI and reporting it to the NSCF device; the NSMF device is used for receiving the performance index report indication information from the NSCCF device and according to the performance The index reporting instruction information obtains the data corresponding to the NSI network slice performance index and reports it to the NSCF device; the NSCF device is used to receive data corresponding to the NSI network slice performance index from the NSMF device , And perform charging processing on the NSI based on the data.
  • this method can charge the network slice instance based on the data corresponding to the network slice performance index, because the network slice performance index
  • the corresponding data is not only the data that the customer cares about, but also better reflects the operator's investment, so it helps to improve the matching degree of the billing result and the network resource investment, which is conducive to the implementation of the above diversified application scenarios, which in turn Improve the use efficiency of network resources or improve the service quality of network services.
  • the performance indicator report indication information includes the NSI identifier and a report parameter set RPC.
  • the report parameters in the RPC are used to describe the content of the PPRO.
  • the RPC contains any one or more of the following, or contains information used to obtain any one or more of the following:
  • the report indicator refers to the network slicing performance indicator of the NSI, which corresponds to The data will be reported to the NSCF device;
  • the acquisition method refers to the acquisition method of the data corresponding to the reporting indicator;
  • the reporting method refers to the method of reporting the data corresponding to the reporting indicator to the NSCF device.
  • the reporting method includes session-based reporting or independent reporting; a starting condition, when the starting condition is met, the NSMF device starts to execute the PPRO; a reporting condition, when the reporting condition is met Next, the NSMF device reports the data corresponding to the reporting index to the NSCF device; an end condition, and when the end condition is met, the NSMF device ends the execution of the PPRO;
  • the report address refers to To receive the address of the data corresponding to the reported indicator.
  • the data corresponding to the network slice performance index includes any one of the following: the sampling value of the network slice performance index; the statistical value of the network slice performance index; the sampling of the network slice performance index The storage address of the value; the storage address of the statistical value of the network slice performance index.
  • the NSCCF device is further used to: send a PPRO management request to the NSMF device; the NSMF device is also used to: receive the PPRO management request from the NSCCF device, and based on the PPRO Management request to manage the execution of the PPRO.
  • an embodiment of the present application provides a charging processing method for a network slice instance.
  • the method is applied to a network slice charging control function NSCCF device.
  • the method includes: determining performance index reporting indication information, and the performance index
  • the reporting instruction information is used to instruct to perform the performance index reporting operation PPRO.
  • the PPRO includes acquiring data corresponding to the network slice performance index of the network slice instance NSI and reporting it to the network slice charging function NSCF device; to the network slice management function NSMF device Send the performance index report indication information.
  • the performance indicator report indication information includes the NSI identifier and a report parameter set RPC, the report parameter in the RPC is used to describe the content of the PPRO, and the determination performance indicator report indication information Including: determining the RPC.
  • the RPC contains any one or more of the following, or contains information used to obtain any one or more of the following:
  • the report indicator refers to the network slicing performance indicator of the NSI, which corresponds to The data will be reported to the NSCF device;
  • the acquisition method refers to the acquisition method of the data corresponding to the reporting indicator;
  • the reporting method refers to the method of reporting the data corresponding to the reporting indicator to the NSCF device.
  • the reporting method includes session-based reporting or independent reporting; a starting condition, when the starting condition is met, the NSMF device starts to execute the PPRO; a reporting condition, when the reporting condition is met Next, the NSMF device reports the data corresponding to the reporting index to the NSCF device; an end condition, and when the end condition is met, the NSMF device ends the execution of the PPRO;
  • the report address refers to To receive the address of the data corresponding to the reported indicator.
  • the RPC is a first parameter set
  • the first parameter set includes the report indicator, the acquisition method, the report method, the start condition, the report condition, and the Any one or more of the end condition and the reported address.
  • the RPC includes an identifier of a second parameter set and a third parameter set
  • the second parameter set includes the report indicator, the acquisition method, the report method, and the report condition and Any one or more of the reported addresses
  • the third parameter set includes the start condition and/or the end condition
  • the identifier of the second parameter set is used to obtain the second parameter set.
  • the method before determining the RPC, further includes any one or more of the following: sending the second parameter set to the NSMF device to instruct the NSMF device to store the first Two parameter sets and receive the identifier of the second parameter set from the NSMF device; send the identifier of the second parameter set and parameter set update information to the NSMF device to instruct the NSMF device to use the parameter
  • the set update information updates the second parameter set
  • the parameter set update information includes information for updating the reported parameter in the second parameter set.
  • the method further includes: sending the identification and deletion indication of the second parameter set to the NSMF device to instruct the NSMF device to delete the second parameter set.
  • the determining the RPC specifically includes: acquiring the order information of the NSI; and determining the RPC according to the order information of the NSI.
  • the method further includes: determining that the operation process in the PPRO needs to be changed; sending a first PPRO management request to the NSMF device, where the first PPRO management request includes the PPRO logo and the NSI Any one of the ID and the charging session ID and the change instruction, the PPRO ID is used to uniquely identify the PPRO, and the charging session ID is used to uniquely identify the relationship between the NSMF device and the NSCF device The charging session corresponding to the NSI.
  • the change indication includes RPC update information
  • the RPC update information includes information used to update the reporting parameters in the RPC.
  • the change instruction includes a report instruction.
  • the method further includes: determining that the operation process in the PPRO needs to be ended; and sending a second PPRO management request to the NSMF device, the second PPRO management request including the PPRO logo, all Any one of the NSI identifier and the charging session identifier and an end instruction, the PPRO identifier is used to uniquely identify the PPRO, and the charging session identifier is used to uniquely identify the NSMF device and the NSCF device Charging session corresponding to the NSI.
  • the method before sending the first PPRO management request to the NSMF device, or before sending the second PPRO management request to the NSMF device, the method further includes: The device receives the PPRO identification and/or the charging session identification.
  • the data corresponding to the network slice performance index includes any one of the following: the sampling value of the network slice performance index; the statistical value of the network slice performance index; the sampling of the network slice performance index The storage address of the value; the storage address of the statistical value of the network slice performance index.
  • the above method enables the NSCCF device to deliver a report operation for a single NSI (reporting data corresponding to the performance index of one NSI in one PPRO), or to report a report operation for multiple NSIs (report the performance of multiple NSIs in one PPRO)
  • the data corresponding to the indicator) is executed by the NSMF device, and can be managed at the granularity of PPRO, or at the granularity of NSI or billing session, and manage a part of PPRO (for the reporting process of a certain NSI), which improves The control strength of NSCCF equipment to charge the network slice instance.
  • an embodiment of the present application provides a charging processing method for a network slice instance.
  • the method is applied to a network slice management function NSMF device.
  • the method includes: receiving performance index reports from a network slice charging control function NSCCF device Indication information; according to the performance index reporting instruction information, perform performance index reporting operation PPRO, the PPRO includes obtaining data corresponding to the network slice performance index of the network slice instance NSI and reporting it to the network slice charging function NSCF device.
  • the performance indicator report indication information includes the NSI identifier and a report parameter set RPC
  • the report parameter in the RPC is used to describe the content of the PPRO
  • the report is based on the performance indicator
  • the instruction information, performing the performance index reporting operation PPRO specifically includes: executing the PPRO according to the NSI identifier and the RPC.
  • the RPC contains any one or more of the following, or contains information used to obtain any one or more of the following:
  • the report indicator refers to the network slicing performance indicator of the NSI, which corresponds to The data will be reported to the NSCF device;
  • the acquisition method refers to the acquisition method of the data corresponding to the reporting indicator;
  • the reporting method refers to the method of reporting the data corresponding to the reporting indicator to the NSCF device.
  • the reporting method includes session-based reporting or independent reporting; a starting condition, when the starting condition is met, the NSMF device starts to execute the PPRO; a reporting condition, when the reporting condition is met Next, the NSMF device reports the data corresponding to the reporting index to the NSCF device; an end condition, and when the end condition is met, the NSMF device ends the execution of the PPRO;
  • the report address refers to To receive the address of the data corresponding to the reported indicator.
  • the RPC is a first parameter set
  • the first parameter set includes the report indicator, the acquisition method, the report method, the start condition, the report condition, and the Any one or more of the end condition and the reported address.
  • the RPC includes an identifier of a second parameter set and a third parameter set
  • the second parameter set includes the report indicator, the acquisition method, the report method, and the report condition and Any one or more of the reported addresses
  • the third parameter set includes the start condition and/or the end condition
  • the method further includes: according to the The identification of the second parameter set acquires the second parameter set; according to the second parameter set and the third parameter set, the RPC is formed.
  • the method before receiving the NSI identifier and the RPC, further includes any one or more of the following: receiving the second parameter set from the NSCCF device, and storing the A second parameter set, generating an identifier of the second parameter set and returning the identifier of the second parameter set to the NSCCF device; receiving the identifier of the second parameter set and the parameter set update from the NSCCF device Information, the second parameter set is updated using the parameter set update information, and the parameter set update information includes information for updating parameters in the second parameter set.
  • the method further includes: receiving an identifier and a deletion indication of the second parameter set from the NSCCF device, and deleting the second parameter set.
  • executing the PPRO according to the NSI identifier and the RPC specifically includes: determining that the data corresponding to the reporting index in the RPC needs to be reported to the NSCF device; The data corresponding to the reporting index in the RPC is reported to the NSCF device.
  • the acquiring the data corresponding to the reporting index in the RPC and reporting it to the NSCF device specifically includes: sending a first charging request to the NSCF device, and the first accounting
  • the fee request includes a charging session identifier, one of the NSI identifiers, and data corresponding to the reporting index in the RPC.
  • the charging session identifier is used to uniquely identify the location between the NSMF device and the NSCF device. The charging session corresponding to NSI is described.
  • the method before the sending the first charging request to the NSCF device, the method further includes: sending a second charging request to the NSCF device, where the second charging request includes The identification of the NSI and an instruction to create a charging session; receiving the charging session identifier from the NSCF device.
  • the method further includes: returning the charging session identifier to the NSCCF device.
  • the second charging request further includes a reason for reporting.
  • the determining that the data corresponding to the reporting index in the RPC needs to be reported to the NSCF device includes: receiving a third PPRO management request from the NSCCF device, and the third PPRO management The request contains a report instruction; determine that the data corresponding to the report index in the RPC needs to be reported to the NSCF device according to the report instruction; or specifically include: determine that the RPC needs to be determined according to the report condition satisfied in the RPC The data corresponding to the reporting index in is reported to the NSCF device.
  • the method before executing the PPRO according to the NSI identifier and the RPC, the method further includes: determining that the start condition in the RPC is satisfied.
  • the executing the PPRO according to the NSI identifier and the RPC specifically includes: determining that the execution of the PPRO needs to be ended; and ending the execution of the PPRO.
  • the determining that the execution of the PPRO needs to be ended specifically includes: receiving a fourth PPRO management request from the NSCCF device, where the fourth PPRO management request includes an end instruction; and according to the end instruction, determining The execution of the PPRO needs to be ended; or specifically includes: determining that the execution of the PPRO needs to be ended according to satisfaction of the end condition in the RPC.
  • the end of executing the PPRO specifically includes: sending a third charging request to the NSCF device and stopping acquiring data corresponding to the reporting index in the RPC, the third charging request It includes one of the identifier of the charging session and the identifier of the NSI and the data corresponding to the reporting index in the RPC.
  • the method further includes: receiving a fifth PPRO management request from the NSCCF device, the fifth PPRO management request including any one of a PPRO identifier, the NSI identifier, and a charging session identifier Items and RPC update information, the PPRO identifier is used to uniquely identify the PPRO, and the charging session identifier is used to uniquely identify the charging session corresponding to the NSI between the NSMF device and the NSCF device; Any one of the PPRO ID, the NSI ID and the charging session ID, and the RPC change information, update the information in the PPRO ID, the NSI ID and the charging session ID Report parameter in RPC corresponding to any item.
  • the data corresponding to the network slice performance index includes any one of the following: the sampling value of the network slice performance index, the statistical value of the network slice performance index, and the sampling of the network slice performance index The storage address of the value, the storage address of the statistical value of the network slice performance index.
  • the above method allows the NSMF device to execute PPRO based on the management instructions/management messages of the NSCCF device to support the billing processing service of the NSCF device.
  • the independent reporting method is beneficial to the timely release of the computing resources of the reporting party and the receiving party.
  • the session reporting method is beneficial to improve the efficiency or performance of reporting.
  • an embodiment of the present application provides a network slice charging control function NSCCF device, including a processor and a memory, wherein: the memory is used to store program instructions; the processor is used to call and execute the Program instructions stored in the memory, so that the network slice charging control function device executes the method for charging processing of the network slice instance in the second aspect described above.
  • an embodiment of the present application provides a computer-readable storage medium, including instructions that, when run on a computer, cause the computer to perform the method for charging a network slice instance in the second aspect described above .
  • an embodiment of the present application provides a network slice management function NSMF device, including a processor and a memory, wherein: the memory is used to store program instructions; and the processor is used to call and execute the memory Program instructions stored in the network to enable the network slicing management device to perform the method of charging processing for the network slicing instance in the third aspect above.
  • an embodiment of the present application provides a computer-readable storage medium, including instructions that, when run on a computer, cause the computer to perform the charging process for the network slice instance described in the third aspect above Methods.
  • the embodiments of the present application provide a chip including programmable logic circuits and/or program instructions, which are used to implement the second aspect, the third aspect, and the second aspect when the chip is running Any possible implementation manner of the third aspect or any possible implementation manner of the third aspect.
  • FIG. 1 is an architectural diagram of a charging system provided by an embodiment of this application
  • FIG. 2 is a flowchart of a method for charging a network resource according to an embodiment of this application
  • 3A is a flowchart of another method for charging a network resource according to an embodiment of the present application.
  • 3B is a flowchart of another method for charging a network resource according to an embodiment of the present application.
  • FIG. 5 is a flowchart of another method for charging a network resource according to an embodiment of the present application.
  • FIG. 6 shows another architectural diagram of a charging system provided by an embodiment of the present application.
  • FIG. 7 is a flowchart of another method for charging a network resource according to an embodiment of the present application.
  • FIG. 8 is a hardware structure diagram of a network slice charging control function NSCCF device, a network slice charging function NSCF device, or a network slice management function NSMF device provided by an embodiment of the present application;
  • FIG. 9 is a schematic structural diagram of a network slice charging control function NSCCF device provided by an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of a network slice management function NSMF device provided by an embodiment of the present application.
  • NSCCF Network Slice Charging Control Function
  • NSCF Network Slice Control Charging Function
  • NSMF Network Slice Management Function
  • the NSCCF device 101 used to determine performance index report indication information and send it to the NSMF device, the performance index report indication information is used to instruct the NSMF device to perform performance index report operation (PerformaceParameter ReportingOperation, PPRO),
  • the PPRO includes acquiring data corresponding to the network slicing performance index of the network slicing instance NSI and reporting it to the NSCF device; specifically, the performance index reporting indication information includes the identification of the NSI and a reporting parameter set (ReportingParameter) Collection, RPC), the NSCCF device 101 is further used to determine the RPC of the PPRO that needs to be performed by the NSMF device 103, and sends the NSI identification and the RPC to the NSMF device 103, so that it is based on the NSI identification and The RPC executes the PPRO; the "report" mentioned here may be sent through a message, or may be transferred through a file transfer protocol (File Transfer Protocol, FTP), or other data transfer methods.
  • the NSCCF device 101 can also be used to 103 Send a PPRO management message to manage the PPRO executed on the NSMF device 103, for example, change the execution of the PPRO, end the execution of the PPRO, etc.; optionally, in order to share RPC between different network slice instances to improve management efficiency, the NSCCF device 101 can also be used to send RPC management messages to the NSMF device 103, such as creating RPC, updating RPC, and deleting RPC. Wherein, the RPC includes reporting indicators, reporting conditions, end conditions, etc. The NSCCF device 101 may determine the RPC based on the customer's order information and network slice instance information, which will be described in further detail in subsequent embodiments of this application.
  • the performance indicator reporting instruction information may also include multiple NSI identifiers and multiple corresponding RPCs, so that the NSMF device 102 can report multiple NSIs in a PPRO Data corresponding to network slice performance indicators.
  • the functions of the NSCCF device 101 may be deployed in a separate physical device or in an existing charging device, which is not limited in this embodiment of the present application.
  • NSCF device 102 used to receive data corresponding to the performance index of the network slice instance reported from the NSMF device 103 through the service interface provided by itself (Nnscf is an exemplary interface identifier), and charge the corresponding network slice instance based on the data Processing, or further calculating the usage fee of the corresponding network slice instance based on the corresponding charging rule.
  • the NSCF device 102 may also be used to send the billing processing result to the billing system (not shown in FIG. 1), so that the billing system generates a billing bill for the customer.
  • the NSCF device 102 may also obtain the charging rule from the NSCCF device or the ordering entity.
  • NSCF device 102 may be deployed in a separate physical device or an existing charging device, which is not limited in this embodiment of the present application.
  • the functions of the NSCF device 102 and the functions of the NSCCF device 101 may also be deployed on the same physical device.
  • NSMF device 103 In addition to creating and managing network slice instances, it is also used to receive the above-mentioned RPC sent by NSCCF device 101 through a service interface provided by itself (Nnsmf is an exemplary interface identifier), and obtain the network slice instance based on the RPC.
  • Nnsmf is an exemplary interface identifier
  • the NSMF device 103 can also be used to receive PPRO management messages from the NSCCF device 101 To perform corresponding PPRO management operations under the control of NSCCF device 101; optionally, NSMF device 103 can also be used to receive management messages from NSCCF device 101 or other management clients to maintain RPC locally and Different network slice instances are shared in PPRO to improve management efficiency.
  • the NSMF device 103 may be a cross-domain network slice manager or a network slice manager in a sub-domain of a core network or other functional entity or device that can provide data corresponding to performance indicators of network slice instances.
  • the cross-domain network slice manager is used to manage multiple sub-domains, and the sub-domain includes an access network sub-domain, a transmission network sub-domain, a core network sub-domain, and the like. It should be understood that the functions of the NSMF device 103 may be deployed in a separate physical device or other existing management devices, which is not limited in this embodiment of the present application.
  • Network slice performance index is a parameter or parameter set used to describe the network performance of the network slice instance, which may include but not limited to one or more of the following parameters:
  • -End-to-end delay refers to the transmission delay of data packets in the access domain, transmission domain and core network domain of the network slice instance;
  • -PDU protocol data unit session: the number of PDU sessions established on the network slice instance (that is, the number of PDU sessions established between the user equipment using the network slice instance and the data gateway on the network slice Quantity);
  • -Bandwidth refers to the total bandwidth used by all concurrent PDU sessions of the network slice instance
  • -Number of users refers to the number of users who have actually used or concurrently used the network slice instance or the number of users registered on the network slice instance;
  • the network slicing performance index is also simply referred to as "index" in the embodiments of the present application.
  • one network slicing instance may have one or more network slicing performance indicators.
  • the embodiment of the present application does not limit the number of network slicing performance indicators of the network slicing instance.
  • network slicing performance indicators can reflect not only the customer or user's focus on using the network slicing instance, but also the operator's investment in the network slicing instance. Therefore, Charging based on the data corresponding to the network slice performance index can take into account the interests of both parties. For example, operators and customers can agree on SLA (Service Level Agreement) for network slicing instances, and can stipulate constraints on network slicing performance indicators, for example, "times exceeding 5ms should be within 10 times", “bandwidth The cumulative time less than 100G does not exceed 30 hours", etc., and agree on the billing method or billing rate under different satisfaction levels of SLA.
  • SLA Service Level Agreement
  • the network slice performance index transmitted through the message can be expressed by the parameter name or parameter identifier of the index, for example, "E2EDelay" or "101" is used to indicate the "latency" network slice performance index.
  • the embodiment of the present application does not limit the representation method of the network slice performance index.
  • the embodiment of the present application takes the parameter name as an example for description.
  • the performance index value can refer to a certain moment, a certain time slot or a certain time period (such as within a certain minute), NSMF equipment or other equipment
  • the specific value of the network slice performance index is detected, sampled or obtained by other means; for convenience of description, the embodiment of the present application is also referred to as the sampled value and instantaneous value of the network slice performance index, or even directly referred to as the sampled value Or instantaneous value.
  • Time of network slicing performance index refers to the time point, time slot or time period of detecting, sampling or otherwise obtaining the specific value of the network slicing performance index; for convenience of description, the embodiments of the present application are also referred to as The sampling time of the network slice performance index or the acquisition time of the network slice performance index is even directly referred to as the sampling time or acquisition time; it should be understood that the time/sampling time/acquisition time of the network slice performance index may be a specific time point , Can also be a specific time period (such as a certain minute); for example, the sampling time of "concurrent sessions” can be "2018-10-2623:58:52", and the sampling time of "delay” can be " 2018-09-26 13:46:00/2018-09-26 13:47:00” or "2018-09-26 13:46” etc.
  • Constraint conditions of network slice performance indicators refers to the quantitative constraints or quantization requirements for network slice performance indicators within a certain statistical time range, which is usually expressed in a numerical range or can also be expressed in specific numerical values.
  • the constraints of network slicing performance indicators are usually the result of agreement with the operator during the ordering of network slicing instances.
  • Statistical value of network slicing performance index refers to the result obtained by statistically calculating the value of the network slicing performance index whose sampling time or acquisition time falls within a certain statistical time range according to a certain statistical method.
  • the statistical method may be a statistical method irrelevant to the constraint condition, such as averaging, weighted average, etc., or a statistical method related to the constraint condition, that is, a statistical method determined according to parameters in the constraint condition.
  • the types of statistical values of several network slicing performance indicators are respectively illustrated below with reference to the situation shown in Table 1. It should be understood that the types of statistical values of network slice performance indicators are not limited to the situations listed in Table 1.
  • FIG. 2 is a flowchart of a method for charging network resources according to an embodiment of the present application.
  • the method flow is implemented based on the architecture shown in FIG. 1, where the NSCCF device corresponds to the NSCCF device 101 in FIG. 1 and the NSMF device corresponds to FIG. 1
  • the NSMF device 103 in FIG. 1 corresponds to the NSCF device 102 in FIG. 1.
  • the NSCCF device determines the report parameter RPC of the performance index reporting operation PPRO for the network slice instance NSI
  • the NSMF device performs the operation based on the RPC, so that the NSCF device can charge the NSI
  • the process includes the following steps:
  • Step 201 The NSCCF device determines the report parameter set RPC of the performance index reporting operation PPRO for NSI.
  • the NSCCF device may determine that the NSI needs to be billed based on the data corresponding to the performance index of the NSI based on the information about the NSI of the network slice instance, and then determine that the performance index of the NSI needs to be reported for the operation of the PPRO Report the parameter set RPC.
  • the PPRO includes obtaining data corresponding to the NSI's network slicing performance index and reporting it to the NSCF device; the relevant information of the NSI includes but is not limited to customer's ordering information about the NSI, information of the NSI itself (such as NSI identification, NSI network slice type, etc.); the RPC includes at least one reporting parameter RP (Reporting Parameters), the RP is used to describe the content of the PPRO (what to report, how to obtain, how to report, etc.). Specifically, the RPC contains any one or more of the following, or contains information for obtaining any one or more of the following:
  • Reporting index refers to the NSI network slicing performance index, and the corresponding data will be reported to the NSSI network slicing performance index of the NCF device, for example: bandwidth, delay, number of online users, etc. . It should be understood that the reporting index is a subset or a complete set of the NSI network slicing performance index.
  • the reporting indicators corresponding to NSI will be different, including the number of reporting indicators and the content of the reporting indicators; for example, an NSI reporting indicator includes bandwidth and Delay, and another NSI reporting index includes delay, number of online users and bandwidth.
  • the embodiment of the present application does not limit the number of reporting indicators included in the reporting parameter set RPC, but for convenience of description, the embodiment of the present application uses a reporting indicator as an example for description; optionally, the NCCCF device may be ordered according to the The type of slices and/or constraints contained in the information determine the reporting index.
  • the reporting index is optional.
  • the NSMF device can use the default reporting index. For example, according to the NSI network slice type, select this The default report index corresponding to the network slice type.
  • Acquisition method refers to the acquisition method of the data corresponding to the reporting indicator; if the data corresponding to the reporting indicator is the sampling value of the reporting indicator, the acquisition method may include a sampling time interval (such as every 5 minutes ), if the data corresponding to the reported indicator is the statistical value of the reported indicator, the acquisition method may include not only the sampling time interval, but also a statistical method; for example, an acquisition method may be expressed as “sampling every 5 minutes Once, while another method of acquisition can be expressed as "statistical monthly average", and another method of acquisition can be expressed as "time of cumulative bandwidth less than 100M/s" and so on.
  • the NSCCF device may determine the acquisition method according to the order information.
  • the acquisition method is optional.
  • the NSMF device can use the default acquisition method. For example, according to the name of the reported indicator, select the default acquisition method .
  • Reporting method refers to a method for reporting data corresponding to the above reporting index to the NSCF device, including but not limited to session-based reporting or independent reporting.
  • the session-based reporting refers to the establishment of a session between the reporting entity (the NSMF device) and the receiving entity (the NSCF device), where the reporting entity and the receiving entity can be Create corresponding computing resources for the session, the identifier generated or allocated by the receiving entity for the created computing resources can be used as the identifier of the session, and then the reporting entity reports the same NSI reporting index to the receiving entity multiple times or periodically based on the session Corresponding data or data corresponding to the reporting index of the NSI belonging to the same customer, that is to say, the multiple reports are associated through the session identifier, that is, the request messages corresponding to the multiple reports all carry the session Identification; the embodiments of the present application sometimes refer to the session between the NSMF device and the NSCF device as a charging session.
  • the independent reporting refers to the fact that no session is established between the reporting entity and the receiving entity, the data corresponding to the reporting index of the same NSI or the NSI belonging to the same customer
  • the data corresponding to the performance indicators of multiple times are not associated by a session or session identifier.
  • the reporting entity or the receiving entity can create a new computing resource, and the NSI logo can be passed between multiple reports Or information such as customer identification.
  • the session reporting method can be used, which can reuse the created computing resources and improve the reporting performance; when the reporting interval is long and the reporting is infrequent, independent reporting can be used In this way, it can release computing resources in time and improve the availability of the system or equipment.
  • the NSCCF device may determine the reporting method according to the order information, for example, determine the reporting frequency or period according to the order information, and then determine the reporting method according to the reporting frequency or period, for example, in When it is determined that reporting is more frequent, select session reporting, and choose to report independently when reporting interval is longer or reporting times are less.
  • the reporting method is optional.
  • the NSMF device can use the default reporting method (such as session reporting). For example, based on the name of the reporting indicator, Select the default reporting method.
  • Start condition when the start condition is satisfied, the NSMF device starts to execute the PPRO, including obtaining the data corresponding to the corresponding reporting index and reporting it to the NSCF device, etc.; Condition”, the NSCCF device may send a PPRO execution instruction (such as a PPRO creation request) to the NSMF device in advance, so that the NSMF device executes the PPRO when the start condition is satisfied or when the start time arrives or after the arrival, thereby effectively avoiding the NSMF
  • the device has surge requests during peak hours.
  • a start condition may be "starting from 20190101-00:00:00", assuming that the time point at which the start condition (or the RPC where it is received) is earlier than "20190101-00:00:00", the start condition indicates The NSMF device does not need to start executing the PPRO immediately after receiving the start condition (or the RPC where it is located), but can wait for the time to reach "20190101-00:00:00"; then, for example, when the NSMF device is required to PPRO starts to execute when RPC is received, and the start condition can also be set to "start immediately”.
  • the NSCCF device may determine the start condition according to the order information.
  • the start condition is optional.
  • the NSMF device can use the default start condition (such as starting when the RPC is received or according to the report The name of the indicator selects the default starting condition).
  • reporting conditions When the reporting conditions are met, the NSMF device reports data corresponding to the reporting index to the NSCF device; reporting conditions include but are not limited to periodic reporting, reporting at a specified time, and event reporting (Critical billing events, such as network slice modification, serious failure):
  • the NSMF device sends the data corresponding to the reporting indicator to the NSCF device periodically (the interval is the reporting period);
  • the NSMF device will report the data corresponding to the reporting indicator to the NSCF device at the specified time;
  • the NSMF device reports the data corresponding to the reporting indicator to the NSCF device when the event occurs or occurs.
  • the NSCCF device may determine the reporting condition according to the order information.
  • the reporting condition is related to the reporting method.
  • the reporting method can be set to session reporting.
  • the reporting condition is optional.
  • the NSMF device may use the default reporting condition (such as periodic reporting).
  • an end condition may be: "end at 20190131-23:59:59".
  • the NSCCF device does not need to send an end instruction to the NSMF device, thereby improving management efficiency.
  • the NSCCF device may determine the end condition according to the order information or account information of the corresponding customer.
  • Reporting address refers to an address for receiving data corresponding to the reporting indicator, for example, an address where the NSCF device provides a charging service, for receiving data corresponding to the reporting indicator reported from an NSMF device;
  • the address can be a URL (Uniform Resource Locator).
  • the NSCCF device may determine the report address according to preset configuration information.
  • some parameters may be the same or common to different NSIs, such as: reporting indicators, acquisition methods, reporting methods, reporting conditions, and reporting addresses, etc., while some parameters may vary due to different NSIs, different customers, or Ordering information varies, for example: start conditions and end conditions.
  • Step 202 The NSCCF device sends the NSI identifier NSIId and the RPC to the NSMF device.
  • the NSCCF device may send a request message to the NSMF device (this embodiment of the present application does not limit the name of the request message, for example, it may be "create PPRO request” or "execute PPRO request”), and the request message carries the The NSI identifier and the RPC, and the NSI identifier and the RPC are used as performance index reporting indication information, and are used to instruct the NSMF device to perform the corresponding performance index reporting operation.
  • the NSCCF device can manage or maintain the Reporting Parameter Collection Template (RPCT) on the NSMF device in advance, and the RPCT contains report parameters that can be shared or shared, so that the NSCCF device and the NSMF device can be managed differently
  • the PPRO corresponding to the NSI is shared.
  • the NSCCF device may include the RPCT identifier and the unique reporting parameters related to the NSI ordering information (such as the PPRO start time and/or end time) in the request message and send it to The NSMF device obtains the corresponding RPCT from the local according to the RPCT identification, and combines with the unique reporting parameters to form the PPRO reporting parameter set RPC.
  • RPCT Reporting Parameter Collection Template
  • the NSCCF device and the NSMF device may preset a default RPCT (for example, preset a default RPCT for different network slice types), then the NSCCF device may not send the RPCT identifier but only send the NSI-specific reporting parameter, NSMF The device forms the report parameter set RPC of the PPRO based on the preset default RPCT and the unique report parameters.
  • a default RPCT for example, preset a default RPCT for different network slice types
  • Step 203 The NSMF device returns the PPRO logo PPROId to the NSCCF device.
  • the NSMF device parses out the NSI identifier and the RPC, creates or allocates computing resources for executing the PPRO, and assigns a unique identifier for the PPRO (that is, the PPRO logo PPROId), and returns a response message to the NSCCF device (corresponding to step 202, the message name may be "create PPRO response" or "execute PPRO response"), and the response message contains the PPRO logo PPROId.
  • the unique identifier of the PPRO can be assigned or generated by the NSMF device, it is returned to the NSCCF device through the response message so that it can manage the PPRO in subsequent steps (such as changing or ending the PPRO); It may also be distributed or generated by the NSCCF device and sent to the NSMF device through the request message described in step 202, so that the response message in this step may not carry the PPRO logo PPROId.
  • the NSCCF device and the NSMF device may also use the NSI identification as the PPRO identification, so that the above operation of "assigning a unique identification" does not need to be performed.
  • the NSMF device may store the RPC to continue to execute the PPRO according to the RPC after the NSMF device restarts or the fault is recovered.
  • Step 204 The NSMF device obtains and reports data corresponding to the report index in the RPC to the NSCF device according to the NSI identifier NSIId and the RPC.
  • the NSMF device obtains data corresponding to the report indicator in the RPC according to the NSI identifier NSIId and the RPC, for example, according to the report indicator and the acquisition method in the RPC, and sends a request to the NSCF device Message (this embodiment of the present application does not limit the name of the request message, for example, it may be "network slice charging request” or "network slice performance index reporting request"), and the request message includes the corresponding index of the reporting index in the RPC data.
  • the NSIId is used to determine the NSI
  • each reporting parameter in the RPC is used to determine how to obtain the data corresponding to the reporting index and report it to the NSCF device.
  • the NSMF device determines the data in the RPC When the reporting conditions are met (depending on the reporting conditions, the data corresponding to the reporting index in the RPC can be obtained during the process of determining whether the reporting conditions are met, or the reporting in the RPC can be obtained after determining that the reporting conditions are met Data corresponding to the index), reporting the data corresponding to the reporting index in the RPC to the NSCF device, which will be described in further detail in subsequent embodiments of the present application.
  • this step may be performed multiple times, that is, the NSMF device may report data corresponding to the reporting index in the RPC to the NSCF device multiple times to meet the needs of the NSCF device side to perform charging processing on the NSI.
  • the NSMF device and the NSCF device may first establish a session, called a charging session, and the NSMF device and the NSCF device respectively create computing resources for the session, to facilitate subsequent reporting between the NSMF device and the NSCF device
  • the NSMF device or NSCF device may assign the same unique identifier to the respective computing resources as the charging session identifier (Charging Session Identifier, CSId), so that the request message in this step may also include CSId for the NSCF
  • the device determines the corresponding computing resource according to the CSId and processes the reported data through it.
  • Step 205 The NSCF device performs charging processing.
  • the NSCF device may perform charging processing on the network slice instance based on the data.
  • the charging process may include: generating a network slicing bill based on the data, or calculating the usage fee of the network slicing instance based on the data, wherein the usage of the network slicing instance is calculated based on the data
  • the method for the fee may include: obtaining the charging rule related to the above network slice instance, and based on the data and the charging rule, calculating the usage fee for the above network slice instance.
  • Step 206 The NSCCF device determines that the operation process of the PPRO needs to be changed.
  • the NSCCF device determines that the operation process of the PPRO needs to be changed according to the change in the order information about the NSI or the change in other charging factors.
  • the customer proposes to extend the order period it can be determined that the end condition in the RPC needs to be changed to delay the end of the reporting time; for another example, when the customer temporarily requests (not reached the bill cycle) to check the bill, then It can be determined that the data corresponding to the currently unreported performance index needs to be reported to the NSCF device for billing processing or bill output.
  • Step 207 The NSCCF device sends the PPRO logo PPROId and the change instruction to the NSMF device.
  • the NSCCF device sends a request message to the NSMF device (the embodiment of the present application does not limit the name of the request message, for example, it may be "change PPRO request” or "update PPRO request”), and the request message includes the PPRO Identify PPROId and a change instruction.
  • the change instruction is used to instruct the NSMF device to change the operation process of the PPRO.
  • the change instruction may be an instruction of "change the end condition" to instruct the NSMF device to end the reporting time point in advance or late; again, when the NSMF device is required to receive After the change instruction, immediately report the data corresponding to the performance indicator, the change instruction may be an "report immediately” instruction, so that the NSMF device reports the data corresponding to the currently unreported performance indicator to the NSCF device for billing processing or output Bills.
  • the PPROId can be replaced by the above NSIId
  • the NSMF device can use NSIId as the PPRO logo, or a mapping relationship between NSIId and PPROId can be established locally, and then the corresponding PPROId is determined by the NSIId through the mapping relationship, so that the PPROId can be based on the PPROId Identify the corresponding PPRO computing resources and then change them.
  • Step 208 The NSMF device changes the operation process of the PPRO based on the change instruction.
  • the NSMF device receives the request message described in step 207 and parses out the PPRO logo PPROId and the change instruction therefrom, and based on the PPRO logo and the change instruction, executes the PPRO corresponding to the change instruction For example, for the "change end condition” instruction, execute the change end condition operation; for the "report immediately” instruction, perform the operation of immediately reporting the data corresponding to the reporting index; for the "change reporting period” Instruct to perform the operation to adjust the reporting period.
  • steps 206-208 can be performed before, during, or after steps 204-205, that is, changes to PPRO can occur before, during, or after PPRO begins.
  • the sequence shown in FIG. 2 is only It is exemplary and does not limit the execution order of these steps.
  • Steps 206-208 are optional steps, that is, it is optional to change the PPRO halfway.
  • Step 209 The NSCCF device determines that PPRO needs to be ended.
  • the NSCCF device determines that the PPRO needs to be ended according to the change in the order information about the NSI or the change in other charging factors.
  • the customer proposes to end the order before the end of the order period, or before the end of the order period, the balance on the customer's account is insufficient, it may be determined that the execution of the PPRO needs to be ended.
  • Step 210 The NSCCF device sends the PPRO identifier PPROId and the end instruction to the NSMF device.
  • the NSCCF device sends a request message to the NSMF device (the embodiment of the present application does not limit the name of the request message, for example, it may be "end PPRO request” or "delete PPRO request”), and the request message includes the PPRO logo PPROId and an end instruction, the end instruction is used to instruct the NSMF device to end the PPRO.
  • the request message includes the PPRO logo PPROId and an end instruction, the end instruction is used to instruct the NSMF device to end the PPRO.
  • Step 211 The NSMF device determines that PPRO needs to be ended.
  • the NSMF device may not perform this step, otherwise, specifically, the NSMF device determines that the execution of the PPRO needs to be ended according to the end condition in the RPC. That is to say, there are at least two triggering factors for the NSMF device to end the PPRO, one is to receive an end instruction sent by the NSCCF device, and the other is to judge by itself that the end condition in the RPC is satisfied (such as reaching the end time point) .
  • Step 212 The NSMF device sends an end-of-report indication and data corresponding to the report index in the RPC to the NSCF device.
  • the NSMF device determines that the execution of the PPRO needs to be ended through step 210 or step 211, and may send a request message to the NSCF device (this embodiment of the present application does not limit the name of the request message, for example, it may be "network slice charging end request "Or “Network slice performance index reporting end request"), the request message includes an end reporting instruction to enable the NSCF device to perform corresponding billing processing, such as outputting a bill.
  • the request message may further include data corresponding to the reported indicator in the RPC, so as to report data corresponding to the reported indicator that has not been reported to the NSCF device.
  • steps 209 to 212 may be performed during or after the execution of steps 204 to 205.
  • the sequence shown in FIG. 2 is only exemplary, and does not limit the execution order of these steps.
  • Steps 209 to 210 are that the NSMF device passively determines that the PPRO needs to be ended (the NSCCF device triggers the end), and step 211 is that the NSMF device autonomously determines that the PPRO needs to be ended.
  • the above method flow takes one NSI corresponding to one RPC as an example for illustration, but the embodiment of the present application does not limit the number of NSIs and the number of corresponding RPCs in the above method flow, for example, when a customer orders For a network slice instance, the request message in step 202 may contain multiple NSIIds and multiple corresponding RPCs, or multiple NSIIds and common RPCs (that is, NSIId and RPC may correspond one-to-one or many-to-one , Can also be many-to-many), in step 204, the data corresponding to the respective reporting indicators can be reported separately for different NSIs, and the request message in step 207 or step 210 can be replaced with NSIId or other information that identifies the reporting operation corresponding to NSI instead of PPROId To separately manage or end the data acquisition and reporting operations corresponding to the reporting indicators corresponding to each NSI.
  • PPROId can indicate that the corresponding management operations are performed on the multiple NSIs.
  • the request message in step 210 contains PPROId and end instruction indicate that the data acquisition and reporting operations corresponding to the reporting indicators corresponding to the multiple NSIs are stopped, and if the request message includes an NSIId and end instruction, it indicates that the NSI reporting indicators corresponding to the NSIId are stopped Corresponding data acquisition and reporting operations, data acquisition and reporting operations corresponding to other NSI reporting indicators are not affected.
  • the method for charging a network slice instance corresponding to FIG. 2 can be based on the data corresponding to the network slice performance index.
  • the slicing instance performs charging processing. Since the data corresponding to the network slicing performance index is not only the data that the customer cares about, but also better reflects the operator's investment, it helps to improve the matching degree of the charging result and the network resource investment. It is conducive to the implementation of the above-mentioned diversified application scenarios, which in turn helps to improve the efficiency of the use of network resources or improve the quality of network service.
  • FIG. 3A is a flowchart of another method for charging network resources according to an embodiment of the present application.
  • the method flow is implemented based on the architecture shown in FIG. 1, where the NSCCF device corresponds to the NSCCF device 101 in FIG. 1 and the NSMF device corresponds to The NSMF device 103 in FIG. 1 corresponds to the NSCF device 102 in FIG. 1.
  • the method flow uses a more specific example to explain how the NSCCF device determines the PPRO's RPC and how the NSMF device executes the PPRO accordingly to implement charging processing for the network slice instance, which specifically includes the following steps:
  • Step 301 The NSCCF device determines the report parameter set RPC01 for the NSI performance index report operation PPRO.
  • the NSCCF device may be based on any one or any of the NSI ordering information, the NSI information, the operator's pre-configured information, and customer account balance information
  • the report parameter set RPC for the PSI performance index reporting operation PPRO is determined as follows:
  • each reporting parameter in RPC01 is optional, and when it does not appear in the above RPC data structure or takes a null value, it can be regarded as a default value agreed between the NSCCF device and the NSMF device, for example
  • the "report address" may use the default address and port of the NSCF device shared by the NSMF device and the NSCCF device.
  • Step 302 The NSCCF device sends a PPRO creation request to the NSMF device, and the request includes NSIId01 and RPC01.
  • Step 303 The NSMF device returns a PPRO creation response to the NSCCF device, and the response includes PPROId01.
  • This step is optional, and the NSMF device may respond to the above PPRO creation request at step 309 again.
  • the NSMF device determines the PPRO to be executed and assigns it a unique identifier PPROId01, and returns a creation PPRO response to the NSCCF device, where the response contains PPROId01.
  • PPROId01 can be allocated by the NSMF device and returned to the NSCCF device through the PPRO response created in this step, or can be allocated by the NSCCF device or obtained by other means, and sent to the NSMF device through the create PPRO request in step 302, which is the step
  • the PPRO request for creating 302 can also include PPROId01 assigned by the NSCCF device.
  • the PPROId01 included in the corresponding PPRO creation can be used for subsequent management (change, end, etc.) of the corresponding PPRO, or it can be used to indicate to the NSCCF device that the PPRO creation request has been successfully processed.
  • Step 304 The NSMF device determines that the start condition is satisfied.
  • the NSMF device determines that the current time is "20190101:00:00:00", which meets the start condition in RPC01.
  • the starting condition is not limited to "arriving at a certain point in time”, but can also be other conditions, for example, "the network slice instance starts to be used" or "the user equipment accesses the network slice instance", then the NSMF device can monitor the network slice In the running state of the instance, once the user equipment accesses the network slice instance, it is determined that the start condition is satisfied.
  • the NSMF device determines that the start condition is satisfied will be different due to the different start conditions in the RPC, and the embodiments of the present application will not repeat them one by one.
  • Step 305 The NSMF device starts to obtain data corresponding to the reported indicator.
  • the NSMF device starts to acquire the bandwidth data of the network slice instance corresponding to NSIId01 according to the reporting index (that is, "bandwidth") in RPC01.
  • Step 306 The NSMF device sends a network slice NS charging initial request to the NSCF device, and the NS charging initial request includes NSIId01.
  • the NSMF device determines that a reporting session needs to be established between it and the NSCF device according to the reporting method in RPC01 as "session reporting", so as to subsequently report data corresponding to the reporting index in RPC01 based on the charging session, and then based on The reporting address "http://NSCF-ip:port" in RPC01 initiates an NS charging initial request to the NSCF device, and the NS initial request includes NSIId01 to establish a charging session with the NSCF device.
  • the NS charging initial request may further include "creation session” indication information, which is used to instruct the NSCF device to create a charging session and assign a unique identifier of the charging session.
  • NS charging initial request is an exemplary message name, and the message may be other names, such as "create charging session request” and the like.
  • Step 307 The NSCF device creates a charging session CS01.
  • the NSCF device receives the NS charging initial request and parses out NSIId01 from it, and creates a charging session (Charging Session, CS), such as CS01, and assigns CS01 a unique identifier for CS01.
  • CS Charging Session
  • the NSCF device may also parse out the indication information of “creating a session” from the NS charging initial request, and create CS01 according to the indication information.
  • the NSCF device may use the name of the initial NS charging request message as a basis for creating CS01, that is, the NSCF device receives the In the message, the charging session is established by default, the charging session identifier is assigned, and the charging session identifier is returned in the response message.
  • the NSCF device may also obtain the corresponding NSI information from the NSMF device or other devices according to NSIId01, and determine the need to create the charging session CS01 according to the NSI information, such as the NSI type (such as eMBB type).
  • the embodiments of the present application are not limited.
  • Step 308 The NSCF device returns an NS charging initial response to the NSMF device, and the NS charging initial response includes CSId01.
  • CSId01 can be used by the NSMF device to report the data corresponding to the reporting index to the NSCF device, or it can be used to distinguish the reporting process or reporting operation corresponding to different NSIs in the NSMF device. It is applicable to a customer with multiple NSIs, or a PPRO It is necessary to report the data corresponding to multiple NSI reporting indicators. In addition, CSId01 can also be used to indicate that the NS charging initial request has been successfully processed.
  • CSId01 may be allocated by the NSCF device in step 307 and returned to the NSMF device through the NS charging initial response in step 308, or may be allocated by the NSMF device before step 306 and then sent to the NS charging initial request in step 306
  • this embodiment of the present application is not limited.
  • step 305 may also be performed after step 308, that is, the NSMF device may start acquiring data corresponding to the reported indicator before establishing a charging session with the NSCF device, or may start acquiring the data after establishing the charging session Report the data corresponding to the indicator.
  • the sequence of steps shown in FIG. 3A is only an example, and is not a limitation in timing.
  • Step 309 The NSMF device returns a PPRO creation response to the NSCCF device.
  • the PPRO creation response includes the PPRO identifier PPROId01 and the charging session identifier CSId01.
  • this step may be omitted.
  • the NSMF device may include the PPROId01 and the CSId01 in the PPRO creation response through two parameters, or may include the PPROd response through one parameter.
  • PPROId01_CSId01 may be used to indicate a parameter or information that includes both PPROId01 and CSId01.
  • “included” means that the PPROId01 and the CSId01 can be parsed or read from the parameter or information.
  • the NSMF device can include the 64-character string in the create PPRO response, and the NSCCF device can parse or read the first 32 characters from the string as PPROId01 and the last 32 characters as CSId01.
  • PPROId01 is used for subsequent management (change, end, etc.) of the corresponding PPRO, and can also be used to indicate that the request to create a PPRO has been successfully processed. Since the creation PPRO response also includes CSId01, subsequent NSCCF devices may initiate management (change, end, etc.) instructions or management messages to NSMF devices based on PPROId01 or based on CSId01.
  • the PPRO response may not include CSId01, and the NSCCF device may subsequently be based on PPROId01 Send management instructions to the NSMF device.
  • the NSMF device can maintain the corresponding relationship between PPROId and CSId in advance, and find the corresponding CSId01 from PPROId01 according to the corresponding relationship, and initiate various charging messages to the NSCF device based on the CSId01.
  • a PPRO creation response may be:
  • the NSCCF device when it needs to manage the reporting operation of a certain NSI, it can initiate a management instruction or management message to the NSMF device based on the corresponding CSId.
  • the Create PPRO response may not include the charging session identifier CSId corresponding to each NSI.
  • the NSCCF device can subsequently send management instructions to the NSMF device based on the identification of the network slice instance NSIId.
  • the NSMF device can maintain the corresponding relationship between NSIId and CSId locally in advance, and the corresponding CSId is found by NSIId according to the corresponding relationship, and initiated based on the CSId to the NSCF device Various billing messages.
  • step 319 For the use of PPROId and CSId, reference may be made to the description in step 319, step 322, and step 327 and their related steps.
  • Step 310 The NSMF device determines that the reporting condition is satisfied.
  • the NSMF device determines that it is necessary to report the data corresponding to the reporting index in the RPC to the NSCF device according to the reporting conditions, which is one of the implementation methods for determining that the data corresponding to the reporting index in the RPC needs to be reported to the NSCF device (other One way is to determine according to the report instruction received from the NSCCF device, see step 322 and step 323 for details).
  • the NSMF device can determine that the reporting condition is met every 5 minutes. To this end, the NSMF device may be a cyclic timer with a reporting start period of 5 minutes, and the reporting conditions are met when the timing time ends.
  • the reporting conditions are not limited to “periodic reporting”, but may also be other conditions, for example, "time delay exceeds 100ms" (assuming that the reporting index in RPC01 is “time delay”), the NSMF device needs to monitor the NSI’s End-to-end delay. When the end-to-end delay exceeds 100ms, determine that the reporting conditions are met.
  • the method for the NSMF device to determine that the reporting conditions are met will vary depending on the reporting conditions in RPC01, and the embodiments of the present application will not repeat them one by one.
  • Step 311 The NSMF device sends an NS charging update request to the NSCF device, where the NS charging update request includes CSId01, data pfmParData01 corresponding to the reporting index, and reporting reason rptRsn01.
  • the NSMF device obtains the sampling value pfmParData01 of the reporting index "bandwidth" according to the acquisition method in RPC01 (ie, "acquisition sample value”), and sends an NS charging update request to the NSCF device.
  • the NS charging update request Contains CSId01, pfmParData01, and reporting reason rptRsn01.
  • the value of rptRsn01 is "reporting condition is met", indicating that the NSMF device reports the bandwidth sampling value to the NSCF device when the reporting condition is satisfied.
  • NSIId01 may be used in place of CSId01 in the NS charging update request in this step, and the NSCF device may use NSIId01 as the identifier of the charging session CS01.
  • CSId01 can be replaced with NSIId01, which will not be described in detail.
  • the NSMF device may first store the data corresponding to the reported indicator, and take pfmParData01 as the storage address of the data corresponding to the reported indicator, or include the storage address of the data corresponding to the reported indicator in pfmParData01, and then Send it to the NSCF device according to the above procedure in this step.
  • Step 312 The NSCF device performs charging processing.
  • the NSCF device receives the NS charging update request, and parses out CSId01, pfmParData01, and rptRsn01 from it, and then performs charging processing based on CSId01, pfmParData01, and rptRsn01, which may specifically be: generating a plan for the network slice instance based on pfmParData01 Charge bill, or, based on pfmParData01 and the charging rule corresponding to the NSI, calculate the usage fee of the network slice instance.
  • pfmParData01 is the sampling value (bandwidth sampling value) corresponding to the reporting index, but if the above acquisition method takes other values, pfmParData01 can also be the statistical value corresponding to the reporting index, or the sampling value or sampling value of the reporting index. A combination of sampling times.
  • the NSCF device can write each group of the sampling value and sampling time combination into the billing bill of the index sampling value corresponding to NSIId01, and subsequently based on the index sampling value Calculate the cost of the bill; the NSCF device can further determine the corresponding statistical time range and statistical method, and according to this statistical method, the combination of multiple sets of sampling values and sampling time in the bill bill charged from the index sampling value Statistics to obtain the statistical value of the reported index, and then use the statistical value to calculate the usage cost of the network slice instance corresponding to NSIId01.
  • the NSCF device can write the statistical value into the indicator statistical value bill corresponding to the NSIId01, and subsequently perform cost calculation based on the indicator statistical value bill; the NSCF device can also use the statistics The value directly calculates the usage fee of the network slice instance corresponding to NSIId01.
  • Table-2 shows the above charging process and corresponding exemplary applicable scenarios.
  • the NSCF device may first obtain related charging rules, and then calculate the usage fee of the network slice instance based on the charging rules and the statistical value. For example, suppose that the charging rule configured by the operator for this network slicing template is "cumulative end-to-end delay exceeding 50ms for more than 10 monthly rent halvings", and the above reported index is "delay”, and its statistical value is "11 "Times", the usage of the above network slicing instance is charged at a 50% rate.
  • the NSCF device may obtain the charging rule from customer order information.
  • rptRsn01 Due to reporting reasons, rptRsn01 is "reporting conditions met", and the billing system may not be triggered to output corresponding billing bills for the time being.
  • the NSCF device may first obtain the data corresponding to the reported indicator according to the storage address , And then perform the charging process according to the above procedure in this step.
  • Step 313 The NSCF device returns an NS charging update response to the NSMF device.
  • the NS charging update response may include information indicating that the NS charging update request is successfully processed, for example: "200OK".
  • step 313 may be performed before step 312, and the order of the steps shown in FIG. 3A is only an example, not a limitation in timing.
  • the process from step 310 to step 313 is a process in which the NSMF device independently reports the data corresponding to the performance index according to the reporting parameters in the RPC, and it can be executed multiple times; the NSMF device can report according to the start condition, end condition, and acquisition method in the RPC01
  • the parameter determines the specific number of executions. For example, the total number of executions can be determined according to the start time in the start condition, the end time in the end condition, and the reporting period in the acquisition mode.
  • the NSCCF device can manage (change or end) it. Therefore, the determined number of executions is not fixed. For details, refer to the descriptions in the subsequent steps 319, 322, and 327 and related steps.
  • Step 314 The NSMF device determines that the end condition is satisfied.
  • the NSMF device may determine that the end condition is satisfied at 23:59:59 on March 31, 2019 according to the end condition in RPC01 "20190331:23:59:59".
  • the reporting condition is not limited to "arriving at a certain time point", but can also be other conditions, for example, "some event occurs” (assuming the reporting index in RPC01 is "delay"), the NSMF device determines that the reporting condition is met
  • the method will be different, and the embodiments of the present application will not repeat them one by one.
  • the start condition is not limited to "a certain point of time is reached", but can also be other conditions, for example, "some event occurs", the method for the NSMF device to determine that the start condition is met will be different, and the embodiments of this application are different Repeat.
  • Step 315 The NSMF device sends an NS charging end request to the NSCF device, where the NS charging end request contains CSId01 and data pfmParData02 corresponding to the reported indicator.
  • the NSMF device determines that the PPRO needs to be ended according to the end condition determined in step 314, including sending an NS accounting end request to the NSCF device, stopping acquiring data corresponding to the reporting index in RPC01, etc., where the NS counts
  • the fee end request includes CSId01.
  • the NSMF device determines that the data corresponding to the reporting index in RPC01 has not been reported, it can report it to the NSCF device before the end of the PPRO. To this end, it can further include pfmParData02 in the NS charging end request. pfmParData02 is optional in the NS charging end request.
  • the acquisition and end of reporting operations corresponding to different NSIs can be performed separately, that is: for multiple NSIs, NSMF
  • the device can determine that the corresponding end conditions are met one by one, and then send an NS accounting end request to the NSCF device, which contains the corresponding CSId/NSIId, and stop acquiring the data corresponding to the corresponding NSI reporting index.
  • the NSMF device determines that the PPRO needs to be ended according to the end condition in the RPC01, which is one of the ways in which it determines that the PPRO needs to be ended (another way is based on the delete PPRO request or end instruction received from the NSCCF device, specific (See steps 327, 328, etc.).
  • Step 316 The NSCF device performs charging processing and releases the charging session CS01.
  • the NSCF device receives the NS charging end request in step 315 and parses out the charging session identifier CSId01 and the data pfmParData02 corresponding to the reporting index from it, and then performs charging processing based on pfmParData02. For details, see step 312. Furthermore, the corresponding charging session CS01 is determined according to CSId01, and the computing resources corresponding to CS01 are released or recovered.
  • pfmParData02 is optional in the NS charging end request in step 315, when it does not appear in the NS charging end request, the charging process performed by the NSCF device based on pfmParData02 will also be omitted .
  • the NSCF device may receive data corresponding to multiple NSI performance indicators at the same time and perform billing processing in parallel, the above-mentioned CSId01 based targeted release or recovery of computing resources helps to maintain the stability of billing processing transactions on the NSCF device. At the same time, it helps to improve the overall usability and stability of NSCF equipment.
  • Step 317 The NSCF device returns an NS charging end response to the NSMF device.
  • the NS charging end response contains information indicating that the NS charging end request is successfully processed, for example: "200OK”.
  • Step 318 The NSMF device stops acquiring data corresponding to the reported index.
  • the NSMF device stops acquiring bandwidth data of the network slice instance corresponding to NSIId01.
  • step 316 may also be performed after step 317, and step 318 may also be performed before step 315.
  • the sequence of steps shown in FIG. 3A is only an example, and is not a limitation in timing.
  • the process from step 314 to step 318 is a process in which the NSMF device autonomously ends the reporting of the data corresponding to the performance indicator according to the reporting parameters in the RPC. This mechanism of autonomous termination can reduce the number of interactions between the NSCCF device and the NSMF device.
  • Step 319 The NSCCF device sends a change PPRO request to the NSMF device.
  • the change PPRO request includes PPROId01 or CSId01 and RPC011.
  • the change PPRO request may include PPROId01 and RPC011, or may include CSId01 and RPC011, both of which indicate that the reporting parameters corresponding to the one NSI reporting operation
  • the set is updated to RPC011, and RPC011 is a reporting parameter set different from RPC01;
  • the change PPRO request may include PPROId01 and RPC011, indicating that the reporting parameter set of the reporting operations of the multiple NSIs needs to be updated (assuming The reporting operation shares the same reporting parameter set), and may also include the correspondence between multiple sets of CSId and RPC or the correspondence between NSIId and RPC, indicating that the reporting parameter set needs to be updated for each of the multiple NSIs.
  • a change PPRO request can be:
  • the NSCCF device may determine that the reporting parameter set RPC in the PPRO needs to be changed. For example, the NSCCF device may determine that the RPC in the PPRO needs to be changed based on a change in customer ordering information, a change in the operator's billing strategy, etc. .
  • Step 320 The NSMF device updates the RPC and executes PPRO based on the new RPC.
  • the NSMF device receives the change PPRO request, parses out PPROId01/CSId01 and RPC011, updates the RPC corresponding to the reporting operation corresponding to PPROId01 or CSId01 with the RPC011, and performs the reporting operation based on the updated RPC, and the specific reporting operation See steps 310-318.
  • Step 321 The NSMF device returns a change PPRO response to the NSCCF device.
  • the change PPRO response may include information indicating that the change PPRO request has been successfully processed, for example: "200OK".
  • step 321 may be performed before step 321.
  • step 319 to step 321 is an optional process, which is the process of passive change of PPRO by the NSMF device, which will affect or change the reporting process previously determined according to RPC01, for example, the number of reports and time interval will be changed.
  • Step 322 The NSCCF device sends a change PPRO request to the NSMF device.
  • the change PPRO request includes PPROId01 or CSId01, and an immediate report indication rptImd.
  • the change PPRO request may include PPROId01 and rptImd, or may include CSId01 and rptImd, all indicating that data corresponding to the one NSI performance index needs to be reported To NSCF equipment;
  • the change PPRO request may include PPROId01 and rptImd, indicating that the data corresponding to the multiple NSI performance indicators needs to be reported to the NSCF device, or may include multiple CSId and rptImd or contain multiple NSIId and rptImd, indicating that the data corresponding to the performance index of NSI corresponding to these CSId or NSIId needs to be reported to the NSCF device.
  • a change PPRO request can be:
  • the NSCCF device may determine that the NSMF device is required to report the data corresponding to the performance index of the NSI to the NSCF device.
  • the NSCCF device may be based on the customer's request for query bills temporarily, The demand for output of bills, etc., makes the above judgment.
  • the immediate reporting instruction rptImd can also be embodied by the message name, that is, if the name of the request message in this step is changed to another name, so that it can reflect the immediate reporting instruction (or the default immediate reporting instruction) ,
  • the request message may not carry the rptImd.
  • Step 323 The NSMF device sends an NS charging update request to the NSCF device, where the NS charging update request includes CSId01, pfmParData03, and rptRsn02.
  • the NSMF device determines that the data corresponding to the reporting index in the RPC needs to be reported to the NSCF device according to the reporting instruction (rptImd) sent by the NSCCF device, and sends the NS charging update request to the NSCF device, and the NS charging
  • the update request includes CSId01, pfmParData03herptRsn02. This step is similar to step 311, but pfmParData03 is different from pfmParData01 (data corresponding to the performance indicators of the NSI at different times), and the reporting reason rptRsn02 is different from rptRsn01, which is "NSCCF device trigger".
  • the NSMF device determines that the data corresponding to the index reported in the RPC needs to be reported to the NSCF device based on the rptImd received from the NSCCF device, which is one of the ways in which it determines that the data corresponding to the index reported in the RPC needs to be reported to the NSCF device (Another way is to determine that the reporting conditions in RPC are satisfied, see step 310, etc. for details).
  • the NS charging update request in this step has the same message name as the NS charging update request in step 311.
  • reporting reason the reason for triggering the reporting of the data corresponding to the reporting index
  • Different charging processes are performed according to different reporting reasons (for example, when the reporting reason is "reporting conditions are met", the charging process performed by the NSCF device is to write the data corresponding to the reporting index to the charging bill, while reporting the reason
  • the charging process performed by the NSCF device is to write the data corresponding to the reported indicator to the charging bill and trigger the billing system to output the bill)
  • these two messages carry rptRsn01 and rptRsn02, respectively;
  • the two messages have different names, so that the reason for triggering the report can be distinguished based on the message name, the rptRsn01 and rptRsn02 may not be carried in the two messages.
  • Step 324 The NSCF device performs charging processing.
  • the NSCF device receives the NS charging update request, and parses out CSId01, pfmParData03, and rptRsn02, and then performs charging processing based on CSId01, pfmParData03, and rptRsn02.
  • pfmParData03 bandwidth sampling value
  • rptRsn02 is "NSCCF device trigger", which means that the corresponding billing bill needs to be output, and the NSCF device can trigger the billing system to output the billing bill.
  • the NSCF device can further combine the charging rules (including data corresponding to the network slicing performance index, such as its statistical value, and the corresponding relationship with the charging method) determined between the customer and the operator when ordering, to calculate the cost of the corresponding network slicing instance.
  • the NSCF device can obtain the charging rule corresponding to the corresponding network slice instance from the ordering entity or the NSCCF device.
  • the NSCF device may also store the charging rules in a permanent storage medium, so as to continue to use the charging rules after restarting or recovering from a failure.
  • the charging processing method is different, and the embodiments of the present application will not repeat them one by one.
  • Step 325 The NSCF device returns an NS charging update response to the NSMF device.
  • the NS charging update response may include information indicating that the NS charging update request has been successfully processed, for example, "200 OK".
  • step 324 may be performed after step 325.
  • Step 326 The NSMF device returns a change PPRO response to the NSCCF device.
  • the change PPRO response may include information indicating that the change PPRO request has been successfully processed, for example, "200 OK".
  • step 322 to step 326 is an optional process, which is a process of passively reporting data corresponding to the performance index of NSI for the NSMF device.
  • Step 327 The NSCCF device sends a delete PPRO request to the NSMF device, and the delete PPRO request includes PPROId01 or CSId01.
  • the delete PPRO request may include PPROId01 or CSId01, all of which indicate that the reporting operation of the one NSI is to be ended;
  • the delete PPRO request may include PPROId01, indicating that the reporting operations of the multiple NSIs are to be ended, or may include multiple CSIds or NSIIds, indicating that these CSIds need to be ended Or the NSI reporting operation corresponding to NSIId.
  • a delete PPRO request can be:
  • csid01, csid02, and csid03 are used to indicate the reporting process of ending charging session identifiers csid01, csid02, and csid03 (including the acquisition and reporting of data corresponding to the reporting indicators), and csid01, csid02, and csid03 respectively correspond to an NSI.
  • the NSCCF device may determine that the NSMF device is required to end the NSI reporting operation. For example, the NSCCF device may make the above judgment based on the customer's account balance and order changes.
  • Step 328 The NSMF device sends an NS charging end request to the NSCF device, where the NS charging end request includes CSId01 and the data pfmParData04 corresponding to the reported indicator.
  • step 315 is similar to step 315, and pfmParData04 is also optional.
  • the NSMF device is determined according to the request to delete the PPRO in step 327 (the indication information of "End PPRO" may also be included in the message, so that it may be determined according to the indication information) and the PPRO needs to be ended.
  • the NSMF device can perform the following processing:
  • the NSMF device can end the acquisition and reporting operations corresponding to the multiple NSIs, that is, send multiple NS charging end requests to the NSCF device , Each NS charging end request contains the corresponding CSId/NSIId, and stop acquiring data corresponding to the reported indicators of the multiple NSIs;
  • the delete PPRO request contains a single charging session identifier (such as CSId01) or a single network slice instance identifier (such as NSIId01), and the NSMF device can end the NSI corresponding to the single charging session identifier or single network slice instance identifier
  • the corresponding acquisition and reporting operation is to send an NS accounting end request to the NSCF device, which contains the corresponding CSId/NSIId, and stop acquiring the data corresponding to the reporting index of the corresponding NSI.
  • the acquisition and reporting operations corresponding to other NSIs in PPRO are not Affected. If the deletion PPRO request in step 327 contains multiple charging session identifiers or multiple network slice instance identifiers, perform the above operations on these charging session identifiers or network slice instance identifiers one by one.
  • the NSMF device determines that the PPRO needs to be ended according to the delete PPRO request or the "end PPRO" instruction message sent by the NSCCF device, which is one of the ways in which it determines that the PPRO needs to be ended (another way is based on the end condition in RPC01 being satisfied , See steps 314, 315, etc.).
  • Step 329 The NSCF device performs charging processing and releases the charging session CS01.
  • This step is similar to step 316, and the charging process based on pfmParData04 is also optional.
  • Step 330 The NSCF device sends an NS charging end response to the NSMF device.
  • This step is similar to step 317
  • Step 331 The NSMF device stops acquiring data corresponding to the reported index.
  • This step is similar to step 318.
  • step 331 may be performed before step 328, and step 329 may be performed after step 330.
  • Step 332 The NSMF device returns a delete PPRO response to the NSCCF device.
  • the delete PPRO response may contain information indicating that the delete PPRO request has been successfully processed, for example, "200 OK".
  • Figure 3A corresponds to the charging processing method for network resources, so that the NSCCF device can send a report operation for a single NSI (a PPRO reports data corresponding to the performance index of an NSI), or it can send a report for multiple NSIs
  • the operation (reporting data corresponding to performance indicators of multiple NSIs in one PPRO) is performed by the NSMF device, and can be managed at the granularity of PPRO, or at the granularity of NSI or billing session to manage a part of PPRO (for a certain NSI reporting process) to improve the control of the NSCCF device to charge the network slice instance.
  • reporting (receiving) between the NSMF device and the NSCF device based on the session
  • the NSMF device and/or the NSCF device can reuse computing resources between different reporting operations, saving time in creating corresponding computing resources, It is beneficial to improve the operating efficiency of NSMF equipment and/or NSCF equipment.
  • an independent reporting method can also be used. For details, see FIG. 3B.
  • FIG. 3B is a flowchart of another method for charging a network resource according to an embodiment of the present application. Compared with the method flow of FIG. 3A, in this method flow, an independent reporting method is used for reporting between the NSMF device and the NSCF device. It includes the following steps:
  • Step 350 to step 354 similar to step 301 to step 305, and will not be repeated here.
  • the reporting method in RPC02 determined in step 350 takes the value of "independent reporting".
  • Step 355-step 358 Compared with the process of step 310-step 313, the difference is that the NS charging request in step 356 replaces the charging session identifier in the NS charging update request in step 311 with the network slice instance identifier NSIId02 CSId01, each time the NSMF device sends an NS charging request to the NSCF device, the NSCF device creates or allocates new computing resources for charging processing, etc. Accordingly, after the NSCF performs charging processing, the newly created or allocated computing resources are also counted After the fee processing is completed, it will be released or recovered in time.
  • Step 359-step 361 Compared with the process of step 319-step 321, the difference is that in the change PPRO request of step 359, the identifier of the network slice instance NSIId02 is used instead of the charging session identifier CSId01 in the change PPRO request of step 319.
  • Step 362-step 366 Compared with the process of step 322-step 326, the difference is that: in the change PPRO request of step 356, the identifier of the network slice instance NSIId02 is used instead of the charging session identifier CSId01 in the change PPRO request of step 322 In the NS charging request of step 363, the identifier NSIId02 of the network slice instance is used to replace the charging session identifier CSId01 in the NS charging update request of step 323; and accordingly, the NSCF device creates new computing resources for receiving the NS billing request and billing processing (instead of reusing computing resources created or allocated previously).
  • Step 367-step 372 Compared with the process of step 327-step 332, the difference is that: in the delete PPRO request in step 367, the network segment instance identifier NSIId02 is used instead of the charging session identifier CSId01 in the delete PPRO request in step 327 In the NS charging request of step 368, the identifier NSIId02 of the network slice instance is used to replace the charging session identifier CSId01 in the NS charging update request of step 328; and accordingly, the NSCF device does not need to perform the operation of releasing the charging session.
  • step 368 may also include the reporting reason rptRsn05, which is "end of reporting" to instruct the NSCF device to perform the charging process of the response, such as triggering the billing system to output bills.
  • 3B corresponds to the charging processing method for network resources, so that the NSMF device and the NSCF device are reported (received) in an independent way, and the NSMF device and/or NSCF device can be released or recycled in time after each report Computing resources to avoid occupying too many computing resources in the NSMF device and/or NSCF device when there are many network slice instances, which is beneficial to improve the availability and stability of the NSMF device and/or NSCF device.
  • FIG. 4 is a flowchart of a method for managing a parameter set template provided by an embodiment of the present application, where the RPCT management client may be the NSCCF device 101 in FIG. 1 or other devices, and the RPCT management server may be the NSMF in FIG. 1
  • the device 103 may also be other devices, and this embodiment is not limited in this embodiment.
  • the method flow includes the following steps:
  • Step 401 The RPCT management client sends an RPCT creation request to the RPCT management server, which carries the RPCT to be created.
  • RPCT is essentially an RPC.
  • Step 402 The RPCT management server stores the RPCT.
  • the RPCT management server receives most RPCT creation requests, parses out the RPCT to be created from it, and assigns a unique identifier RPCTId to the RPCT, and stores the RPCT to be created.
  • Step 403 The RPCT management server returns an RPCT creation response to the RPCT management client.
  • the RPCT creation response includes the RPCTId.
  • Subsequent RPCT management clients such as NSCCF devices, can only send the RPCTId to the NSMF device without sending the entire RPCT corresponding to the RPCTId, which can improve the efficiency of information transmission between the NSCCF device and the NSMF device.
  • the RPCTId may also be used to indicate to the RPCT management client that the request to create an RPCT has been successfully processed, and the RPCT has taken effect on the RPCT management server.
  • Step 404 The RPCT management client sends an update RPCT request to the RPCT management server, where the update RPCT request carries RPCTId and RPCTUpdtInfo.
  • RPCTId is used to determine the existing RPCT
  • RPCTUpdtInfo is used to update the reporting parameters in the existing RPCT.
  • the RPCT management client may first determine that the RPCT needs to be updated. For example, the RPCT management client may make the above judgment according to the change in the charging policy uniformly formulated by the operator. For example, as network bandwidth capabilities provided by operators increase, the bandwidth constraint conditions in the RPCT for eMBB-type NSI can be adjusted upwards, so that when NSMF devices perform reporting operations for this type of NSI, the bandwidth constraint conditions that are adjusted up are used uniformly.
  • Step 405 The RPCT management server updates the RPCT.
  • the RPCT management server receives the update RPCT request, parses out RPCTId and RPCTUpdtInfo from it, and updates the reporting parameters in the RPCT corresponding to RPCTId according to RPCTUpdtInfo.
  • Step 406 The RPCT management server returns an update RPCT response to the RPCT management client.
  • the update RPCT response may include information indicating that the update RPCT request has been successfully processed, for example: "200 OK".
  • the update of the RPCT may not affect the report operation that has been performed based on the RPCT before the update.
  • the RPCT management client or the RPCT management server may broadcast a message that the RPCT has been updated to other RPCT management clients.
  • Step 407 The RPCT management client sends an RPCT delete request to the RPCT management server, where the RPCT delete request carries the RPCTId.
  • the RPCT management client may first determine that the RPCT needs to be deleted. For example, according to the unified plan of the operator, when a certain charging rule is no longer applicable to any network slice, its corresponding RPCT will be deleted.
  • Deleting the name of the RPCT request message here can be regarded as a deletion instruction, which is used to instruct the RPCT management server to delete the RPCT corresponding to RPCTId. If the deletion request RPCT request message is changed to another name, the RPCT management client may also include a deletion instruction in the request message.
  • Step 408 The RPCT management server deletes the RPCT.
  • the RPCT management server receives the delete RPCT request, parses out the RPCTId from it, and finds and deletes the RPCT corresponding to the RPCTId according to the delete request.
  • the RPCT management client or the RPCT management server can broadcast a message that the RPCT has been deleted to other RPCT management clients.
  • Step 409 The RPCT management server returns a delete RPC response to the RPCT management client.
  • the delete RPCT response may include information indicating that the delete RPCT request has been successfully processed, for example: "200 OK".
  • the corresponding method flow in FIG. 4 makes it possible for the NSCCF device and the NSMF device to have a common understanding and identification of RPCT, which is convenient for use when the NSCCF device issues PPRO.
  • FIG. 5 is a flowchart of another method for charging network resources according to an embodiment of the present application.
  • the method flow is implemented based on the architecture shown in FIG. 1, where the NSCCF device corresponds to the NSCCF device 101 in FIG. 1 (including FIG. 4).
  • the functions of the RPCT management client shown) the NSMF device corresponds to the NSMF device 103 in FIG. 1 (including the function of the RPCT management server shown in FIG. 4), and the NSCF device corresponds to the NSCF device 102 in FIG.
  • the method flow illustrates how the NSCCF equipment and NSMF equipment use the RPCT that will be maintained in advance to create and execute PPRO, with specific examples including the following steps:
  • Step 501 The NSCCF device determines the RPCTI identifier RPCTId corresponding to the NSI and the specific reporting parameter specRP of the NSI.
  • the NSCCF device may determine the RPCT or the corresponding RPCTId applicable to the NSI according to the NSI network slice type or other charging factors. For example, the NSCCF device may locally store a correspondence table of network slice types to RPCTId, as shown in Table-3, in order to determine the corresponding RPCTId according to the network slice type corresponding to NSI.
  • the NSCCF device may determine the NSI-specific reporting parameter specRP according to the customer's ordering information, and the specRP includes, but is not limited to, the above-mentioned RPC start condition and/or end condition.
  • Step 502 The NSCCF device sends a create PPRO request to the NSMF device, where the create PPRO request includes the NSIId, the RPCTId, and the specRP.
  • Step 503 The NSMF device forms an RPC corresponding to PPRO according to the RPCTId and specRP.
  • the NSMF device receives the create PPRO request, parses out the NSIId, the RPCTId, and the specRP, and forms an RPC corresponding to the PPRO to be created or to be executed based on the RPCTId and the specRP.
  • the NSMF device retrieves the corresponding locally stored RPCT according to the RPCTId, and combines the specRP and the RPCT to form the RPC. Examples are as follows:
  • An RPCT is:
  • the value is the "to be determined” reporting parameter, and its value needs to be determined in conjunction with the NSI specific reporting parameter specRP.
  • a specRP is:
  • the value is the field of "reference template", and its value needs to be determined in combination with the reporting parameters in the corresponding RPCT.
  • NSMF equipment can combine the two to form RPC as follows:
  • the NSMF device can store RPC03 in order to continue to execute PPRO according to RPC03 after the NSMF device restarts or recovers from failure, and the implementation of PPRO is not affected by the RPCT change (see the corresponding method flow in FIG. 4 for RPCT changes).
  • Step 504 The NSMF device obtains and reports data corresponding to the performance index of NSI according to the RPC.
  • step 304 please refer to the process from step 304 to step 318.
  • Step 505 The NSCCF device changes or ends the execution of PPRO.
  • the corresponding method flow in FIG. 5 allows the NSCCF device to send the RPCTId to the NSMF device, instead of sending the entire RPCT corresponding to the RPCTId, which can improve the efficiency of information transmission between the NSCCF device and the NSMF device, and also help to improve the RPC adoption of the NSCCF device Unified management and control capabilities.
  • FIG. 6 is a diagram of yet another charging system architecture provided by an embodiment of the present application.
  • a subscription entity 604 based on the architecture of the charging system shown in FIG. 1 (other devices correspond to devices with the same number in FIG. 1), Its brief functional description is as follows:
  • Ordering entity 604 used to receive a network slicing order request from a customer, notify NSMF device 103 to open a network slicing instance, and send order information and network slicing instance information to NSCCF device 101, so that it can determine the network slicing instance
  • the ordering entity 604 is a functional module, which can be deployed in a CRM (Customer Relationship Management) server or in other devices.
  • the NSCCF device corresponds to the NSCCF device 101 and the NSMF device in FIG. 6.
  • the ordering entity corresponds to the ordering entity 604 in FIG. 6.
  • the NSCCF device is responsible for determining the PPRO reporting parameter set RPC based on the information provided by the ordering entity, and the NSMF device is responsible for executing the PPRO according to the RPC to report the data corresponding to the network slice performance index to the NSCF device.
  • the NSCF device performs charging processing based on the data, specifically including the following steps:
  • Step 701 The ordering entity receives a network slice ordering request from the customer.
  • a customer (assuming that its identifier is "1381234567") can submit a network slice order request to the ordering entity through its terminal (such as a mobile terminal, a laptop, etc., through a browser or through other channels), and the order request Contains the customer's demand information on the network performance of the network slice.
  • the demand information may include the network slice type, network slice performance index requirements, and so on.
  • the ordering entity can provide multiple network slicing types, which can be displayed on the client terminal for customers to choose.
  • the ordering entity can provide: eMBB type (less equipment but large bandwidth requirements), uRLLC type (requires end-to-end delay is very small ), mMTC type (small bandwidth but extremely large number of devices) three types for customers to choose.
  • the customer can further specify the constraints of the network slicing performance index (this value can be a specific value or a range value). For example: if the customer selects an eMBB type network slice, then the bandwidth of the network slice instance can be further specified to be higher than 1000G; if the customer chooses uRLLC type network slice, then the maximum delay of the network slice instance can be further specified to be less than 5 milliseconds; the customer By selecting an eMTC type network slice, you can further specify that the number of concurrent PDU sessions for this network slice instance is more than 1 million.
  • the above “bandwidth”, “maximum delay” and “number of concurrent PDU sessions” are all network slice performance indicators.
  • the customer may specify the constraint conditions corresponding to each network slice performance index separately.
  • the embodiment of the present application takes an index as an example for description.
  • the ordering entity may also provide a network slicing template for the customer to choose from or as a basis for customer modification.
  • a network slicing template for the customer to choose from or as a basis for customer modification.
  • a network slice template can be:
  • the charging rule includes a charging method corresponding to the statistical value of the network slice performance index. For different statistical values, the examples are as follows:
  • the correspondence between the degree of compliance and the charging method can also be in the form of expressions, formulas, or functions, but it is also essentially a mapping or correspondence.
  • the correspondence between the non-compliance duration and the charging method can also be in the form of an expression, formula, or function.
  • the statistic value is the number of cumulative failures: For example, with regard to the end-to-end latency network slicing performance index, the constraint condition specified by the customer should be "the whole process is less than 5ms", while the actual end-to-end delay is greater than 5ms If the cumulative number of occurrences reaches 60, the 60 times are the cumulative number of non-compliances; the correspondence between the cumulative number of non-compliances and the charging method may be similar to the corresponding relationship between the above-mentioned compliance level and the charging method, and will not be repeated here.
  • the above charging rules are only schematic, and the embodiments of the present application do not exclude other charging rules for charging based on the value of the network slice performance index.
  • the ordering entity can create and store network slicing order information, for example:
  • the value of the "Billing Rule” field may be a text string obtained by converting the above charging rules (for example, the contents of Table 3).
  • the string may be in XML (Extensible Markup Language) format, JSON ( JavaScript object notation) format or other text format, it can also be a computer-executable script, or it can be data in a binary format obtained by converting the above charging rules.
  • XML Extensible Markup Language
  • JSON JavaScript object notation
  • the subsequent NSCF device may perform charging processing on the corresponding network slice instance according to the charging rule.
  • the charging rules may be provided by the ordering entity to the NSCCF device, and then provided by the NSCCF device to the NSCF device (such as sending, file sharing, etc.); due to different network slice instances, the charging rules may be different ,
  • the ordering entity and/or the NSCCF device may provide the correspondence between the identification of the network slice instance and the charging rules.
  • customers described in the embodiments of this application may be industry customers or enterprise customers with many user equipments, such as bicycle sharing companies, taxi companies, etc., or natural person customers.
  • this application is implemented Cases are called customers.
  • Step 702 The ordering entity notifies the NSMF device to activate the network slicing service.
  • the ordering entity may send the NSMF device a provisioning slice service notification, and the provisioning slice service notification may include the slice type and the constraint conditions in the above network slice ordering information, so that the NSMF device creates a network slice instance that meets customer requirements.
  • the notification of opening a slicing service may further include a customer identification, so that the NSMF device may subsequently establish a correspondence between the created network slicing instance and the customer identification.
  • Step 703 The NSMF device creates a network slice instance for the customer.
  • the NSMF device receives the above-mentioned opening network slicing notification from the ordering entity, and creates a corresponding network slicing instance according to the network slicing type and the constraint conditions in the notification, and assigns a unique identifier to the network slicing instance identifier.
  • the NSMF device may allocate the newly created network slice instance to the client, that is, establish a correspondence between the network slice instance identifier and the client identifier.
  • the NSMF device can also check whether there is already a network slicing instance that can meet the customer's needs in the network. If it is determined that it already exists and the network slicing instance can be assigned to the customer, the NSMF device can directly slice the already existing network Instances are directly assigned to the above customers, so that the process of creating a new network slice instance can be omitted.
  • the NSMF device may obtain the above-mentioned customer identification from the above-mentioned network slicing notification message.
  • Step 704 The NSMF device returns the network slice instance information to the ordering entity.
  • the NSMF device may return a network slice opening response to the ordering entity, and the response may include indication information of successful network slice creation and information of the network slice instance, and the information may include the identifier of the network slice instance and the network slice.
  • the creation time of the instance and the current state of the above network slice instance (such as created, activated, etc.), etc.
  • Step 705 The ordering entity sends network slice ordering information and network slice instance information to the NSCCF device.
  • the subscription entity may send a subscription information notification to the NSCCF device, where the notification includes the network slice subscription information described in step 701 and the network slice instance information described in step 704.
  • the above steps 704 and 705 can be understood as that the NSMF device sends the network slice instance information to the NSCCF device through the ordering entity.
  • the NSMF device may also directly send the network slice instance information to the NSCCF device, such as: network slice instance identification, network slice instance creation time, network slice instance current status (such as created, activated, etc.), etc.
  • Step 706 The NSCCF device determines the report parameter set RPC for the NSI performance index report operation PPRO.
  • the NSCCF device may determine the PPRO report parameter set RPC according to the network slice order information and the network slice instance information
  • the reporting parameters of, for example, can be determined according to the slice type and/or constraints in the network slice ordering information, and determined according to the constraints and/or charging rules in the network slice ordering information
  • the report address can be configured in advance.
  • Step 707 The NSCCF device sends the NSI identification and RPC to the NSMF device.
  • This step is similar to step 302.
  • Step 708 The NSMF device executes PPRO against NSI according to RPC.
  • step 304 For the content of this step, please refer to the process from step 304 to step 332.
  • the flow chart of the method shown in FIG. 7 allows the NSCCF device to determine the RPC of PPRO based on the customer's order information and/or network slice instance information, so that the entire billing system (including NSCCF device, NSMF device, NSCF device, etc.) can better Meet the personalized billing needs of different customers and different NSIs.
  • FIG. 8 is a hardware structure diagram of an NSCCF device, an NSCF device, or an NSMF device provided by an embodiment of this application. All NSCCF devices (for example, 101 in FIGS. 1 and 6), all NSMF devices (for example, 103 in FIGS. 1 and 6), and all NSCF devices (for example, in FIGS. 1 and 6) in the embodiments of the present application 102), all of which can use the general computer hardware shown in FIG. 8, which includes a processor 801, a memory 802, a bus 803, an input device 804, an output device 805, and a network interface 806, where the input device 804 and the output device 805 are Selected.
  • All NSCCF devices for example, 101 in FIGS. 1 and 6
  • all NSMF devices for example, 103 in FIGS. 1 and 6
  • all NSCF devices for example, in FIGS. 1 and 6) in the embodiments of the present application 102
  • the memory 802 may include computer storage media in the form of volatile and/or nonvolatile memory, such as read-only memory and/or random access memory.
  • the memory 802 may store an operating system, application programs, other program modules, executable codes, and program data.
  • the input device 804 can be used to input information to facilitate the system administrator to operate and manage the NSCCF device, NSMF device or NSCF device, such as configuring the default report parameter set RPC on the NSCCF device and configuring the default NSCF device on the NSMF device
  • the input device 804 may be a keyboard or pointing device, such as a mouse, trackball, touch pad, microphone, joystick, game pad, satellite TV antenna, scanner, or similar device. These input devices may be connected to the processor 801 through the bus 803.
  • the output device 805 can be used to output information, which is convenient for the system administrator to operate and manage the NSCCF device, NSMF device, or NSCF device. In addition to the monitor, the output device 805 can also be provided for other peripheral output, such as speakers And/or printing devices, these output devices may also be connected to the processor 801 via a bus 803.
  • the NSCCF device, NSMF device or NSCF device may be connected to the network through the network interface 806, for example, connected to a local area network (Local Area Network, LAN).
  • LAN Local Area Network
  • computer-executed instructions stored in the device may be stored in a remote storage device, not limited to local storage.
  • the NSCCF device when the processor 801 executes the executable code or application program stored in the memory 802, the NSCCF device can perform the method steps corresponding to the NSCCF device in all the above embodiments, such as steps 201, 202, 301, 351, 401, 501, 706, etc.; for the specific execution process, please refer to the above embodiments, which will not be repeated here.
  • the NSMF device when the processor 801 executes the executable code or application program stored in the memory 802, the NSMF device can perform the method steps corresponding to the NSMF device in all the above embodiments, such as steps 204, 208, 304, 353, 402, 503, 708, etc.; for the specific execution process, please refer to the above embodiments, which will not be repeated here.
  • the NSCF device when the processor 801 executes the executable code or application stored in the memory 802, the NSCF device can perform the method steps corresponding to the NSCF device in all the above embodiments, such as steps 205, 307, 329, 364, 402, 504, etc.; for the specific execution process, please refer to the above embodiments, which will not be repeated here.
  • FIG. 9 is a schematic structural diagram of an NSCCF device provided by an embodiment of the present application.
  • the NSCCF device includes:
  • the determination module 901 is used to determine the report parameter set RPC, the RPC contains at least one report parameter, the report parameter is used to describe the content of the performance index report operation PPRO, the PPRO includes obtaining the network slice instance NSI network slice performance The data corresponding to the index is reported to the NSCF device of the network slice charging function.
  • the specific execution process refer to the description of the steps on the NSCCF device side in the foregoing embodiment, such as steps 201, 301, 350, 401, 501, and 706.
  • -A sending module 902 used to send the NSI identification and the RPC to the NSMF device to instruct the NSMF device to execute the PPRO according to the NSI identification and the RPC, for the specific execution process, refer to the above embodiment
  • the NSCCF device is presented in the form of a functional module.
  • Module here can refer to an application-specific integrated circuit (ASIC), a circuit, a processor and memory that execute one or more software or firmware programs, an integrated logic circuit, and/or other functions that can provide the above functions Device.
  • ASIC application-specific integrated circuit
  • the NSCCF device may also take the form shown in FIG. 8.
  • Both the determining module 901 and the sending module 902 can be implemented by the processor 801 and the memory 802 in FIG. 8.
  • the determination module 901 determines that the function of reporting the parameter set RPC of the performance index reporting operation PPRO for the network slice instance NSI can be implemented by the processor 801 executing the code stored in the memory 802.
  • the NSMF device includes:
  • the receiving module 1001 is used to receive the identification and reporting parameter set RPC of the network slice instance NSI from the NSCCF device, the RPC includes at least one reporting parameter, the reporting parameter is used to describe the operation content of the performance index reporting operation PPRO, the PPRO includes obtaining data corresponding to the network slicing performance index of the network slicing instance NSI and reporting it to the network slicing billing function NSCF device.
  • the specific execution process refer to the step description on the NSMF device side in the above embodiments, such as steps 203, 204, and 303 , 352 and 503 etc.
  • -Reporting module 1002 which is used to execute the PPRO according to the NSI identifier and the RPC, including obtaining data corresponding to the network slice performance index of the NSI and reporting it to the NSCF device, for the specific execution process, see the above implementation In the example, the steps on the NSMF device side are described, such as steps 204, 311, 356, and 504.
  • the NSMF equipment is presented in the form of functional modules.
  • Module here may refer to an application-specific integrated circuit (ASIC), a circuit, a processor and memory that execute one or more software or firmware programs, an integrated logic circuit, and/or other functions that can provide the above functions Device.
  • ASIC application-specific integrated circuit
  • the NSMF device may also adopt the form shown in FIG. 8.
  • Both the receiving module 1001 and the reporting module 1002 can be implemented by the processor 801 and the memory 802 in FIG. 8.
  • the function of the reporting module 1002 to report the data corresponding to the performance index of the network slice may be implemented by the processor 801 executing the code stored in the memory 802.
  • the disclosed system, device, and method may be implemented in other ways.
  • the division of the unit is only a division of logical functions, and there may be other divisions in actual implementation, for example, multiple units or components may be combined or integrated into another system, or some features may be ignored, or not carried out.
  • the displayed or discussed mutual couplings or direct couplings or communication connections may be indirect couplings or communication connections through some interfaces, devices, or units, and may also be electrical, mechanical, or other forms of connection.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place or may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments of the present application.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or software function unit.
  • the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it may be stored in a computer-readable storage medium.
  • the technical solution of the present application essentially or part of the contribution to the existing technology, or all or part of the technical solution can be embodied in the form of a software product
  • the computer software product is stored in a storage medium
  • several instructions are included to enable a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application.
  • the foregoing storage media include various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory, a random access memory, a magnetic disk, or an optical disk.

Landscapes

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

Abstract

L'invention concerne un procédé permettant d'effectuer un traitement de facturation sur des ressources de réseau, le procédé consistant à : déterminer un ensemble de paramètres de rapport RPC, le paramètre de rapport étant utilisé pour décrire un contenu d'opération d'une opération de rapport d'indice de performance PPRO et le PPRO comprend le rapport de données correspondant à un indice de performance de tranche de réseau d'une instance de tranche de réseau (NSI) à un dispositif de fonction de facturation de tranche de réseau ; envoyer un identifiant de la NSI et le RPC à un dispositif de fonction de gestion de tranche de réseau de façon à ordonner au dispositif de fonction de gestion de tranche de réseau d'exécuter le PPRO selon l'identifiant de la NSI et le RPC, de sorte que le dispositif de fonction de facturation de tranche de réseau puisse effectuer un traitement de facturation sur la NSI. Le procédé selon la présente invention provoque la mise en correspondance du résultat de la facturation du client avec l'investissement d'un opérateur des NSI, ce qui aide à améliorer l'efficacité d'utilisation de ressources de réseau et à répondre aux divers besoins de service de réseau de clients industriels.
PCT/CN2019/130238 2019-01-11 2019-12-31 Procédé et système permettant d'effectuer un traitement de facturation sur des instances de tranches de réseau et dispositif associé Ceased WO2020143502A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910028389.3A CN111436029B (zh) 2019-01-11 2019-01-11 对网络切片实例进行计费处理的方法、系统及相关设备
CN201910028389.3 2019-01-11

Publications (1)

Publication Number Publication Date
WO2020143502A1 true WO2020143502A1 (fr) 2020-07-16

Family

ID=71520883

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/130238 Ceased WO2020143502A1 (fr) 2019-01-11 2019-12-31 Procédé et système permettant d'effectuer un traitement de facturation sur des instances de tranches de réseau et dispositif associé

Country Status (2)

Country Link
CN (1) CN111436029B (fr)
WO (1) WO2020143502A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114205459A (zh) * 2020-08-31 2022-03-18 中国移动通信集团浙江有限公司 基于网络切片的异常话单检测方法及装置
CN115134855A (zh) * 2021-03-24 2022-09-30 中国电信股份有限公司 网络切片性能测量方法和装置
US20230205733A1 (en) * 2021-12-23 2023-06-29 T-Mobile Innovations Llc Systems and methods for immutable archiving of user equipment connection data for wireless communications networks
US11864069B2 (en) 2020-11-03 2024-01-02 Cisco Technology, Inc. Network slice based billing

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11133946B2 (en) 2019-11-14 2021-09-28 Verizon Patent And Licensing Inc. Systems and methods for selective provisioning of a charging function in a wireless network
CN114095369A (zh) * 2020-07-31 2022-02-25 中国电信股份有限公司 切片标识管理方法、装置和存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106572517A (zh) * 2015-10-09 2017-04-19 中国移动通信集团公司 网络切片的处理方法、接入网络的选择方法及装置
US20180220277A1 (en) * 2017-01-27 2018-08-02 Huawei Technologies Co., Ltd. Method and apparatus for charging operations in a communication network supporting service sessions for direct end users
WO2019005069A1 (fr) * 2017-06-29 2019-01-03 Nokia Solutions And Networks Oy Interfaces améliorées pour une sélection de tranche de réseau basée sur des règles de facturation

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9172678B2 (en) * 2011-06-28 2015-10-27 At&T Intellectual Property I, L.P. Methods and apparatus to improve security of a virtual private mobile network
CN107318113B (zh) * 2016-04-27 2021-09-21 华为技术有限公司 网络切片处理方法和装置
CN107580360A (zh) * 2016-07-04 2018-01-12 中国移动通信有限公司研究院 一种网络切片选择的方法、设备及网络架构
CN107820291B (zh) * 2016-09-12 2021-04-20 华为技术有限公司 网络切片控制方法及相关设备
CN108632945B (zh) * 2017-03-20 2020-11-06 华为技术有限公司 一种网络切片选择方法、用户设备及网络设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106572517A (zh) * 2015-10-09 2017-04-19 中国移动通信集团公司 网络切片的处理方法、接入网络的选择方法及装置
US20180220277A1 (en) * 2017-01-27 2018-08-02 Huawei Technologies Co., Ltd. Method and apparatus for charging operations in a communication network supporting service sessions for direct end users
WO2019005069A1 (fr) * 2017-06-29 2019-01-03 Nokia Solutions And Networks Oy Interfaces améliorées pour une sélection de tranche de réseau basée sur des règles de facturation

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
ANONYMOOUS: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Charging management; Study on Charging Aspects of Network Slicing; (Release 16)", 3GPP STANDARD; TECHNICAL REPORT; 3GPP TR 32.845, no. V0.3.0, 15 March 2019 (2019-03-15), pages 1 - 17, XP051722803 *
ANONYMOUS: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Charging management; Study on charging aspects of 5G system architecture phase 1 (Release 15)", 3GPP TR 32.899 V15.1.0, no. V15.0.0, 31 January 2018 (2018-01-31), pages 1 - 104, XP051392332 *
HUAWEI: "Addition of key issues and solution for SLA based charging", 3GPP DRAFT; S5-191088, 25 January 2019 (2019-01-25), Montreal,Canada, pages 1 - 3, XP051590608 *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114205459A (zh) * 2020-08-31 2022-03-18 中国移动通信集团浙江有限公司 基于网络切片的异常话单检测方法及装置
US11864069B2 (en) 2020-11-03 2024-01-02 Cisco Technology, Inc. Network slice based billing
CN115134855A (zh) * 2021-03-24 2022-09-30 中国电信股份有限公司 网络切片性能测量方法和装置
US20230205733A1 (en) * 2021-12-23 2023-06-29 T-Mobile Innovations Llc Systems and methods for immutable archiving of user equipment connection data for wireless communications networks
US12423266B2 (en) * 2021-12-23 2025-09-23 T-Mobile Innovations Llc Systems and methods for immutable archiving of user equipment connection data for wireless communications networks

Also Published As

Publication number Publication date
CN111436029B (zh) 2022-03-29
CN111436029A (zh) 2020-07-21

Similar Documents

Publication Publication Date Title
WO2020143502A1 (fr) Procédé et système permettant d'effectuer un traitement de facturation sur des instances de tranches de réseau et dispositif associé
CN109120426B (zh) 一种网络切片管理方法、装置及计算机可读存储介质
US10681222B2 (en) Charging management method, user plane function entity, and control plane function entity
US20250219853A1 (en) Method and system for performing charging processing on network slice customer, and related device
WO2020098598A1 (fr) Procédé et système permettant d'effectuer un traitement de facturation sur des ressources de réseau, et dispositif associé
WO2022121735A1 (fr) Procédé, appareil et système d'exploitation et de maintenance pour une tranche de réseau, et support de stockage
US10609225B2 (en) Charging method, apparatus, and system
CN109996216B (zh) 订阅请求处理方法、网络实体及能力开放平台
WO2020108507A1 (fr) Procédé et système d'utilisation d'informations de métadonnées d'un service de fonction de réseau et dispositif associé
US11711674B2 (en) Method and system for performing charging on network resource, and device
WO2014194869A1 (fr) Procédé, dispositif et système de traitement d'une demande
CN109964507B (zh) 网络功能的管理方法、管理单元及系统
CN103004171A (zh) Diameter会话审核
US20220038871A1 (en) Charging method, apparatus, and system
US20120303795A1 (en) Qos control in wireline subscriber management
WO2021012933A1 (fr) Procédé de traitement de facturation, système et dispositif associé
WO2021027757A1 (fr) Procédé et système de traitement de calcul de redevance pour un service de données garanti, et appareil associé
CN109787911A (zh) 负载分担的方法、控制面实体和转发器
WO2016109970A1 (fr) Entité de réseau et procédé de gestion de politique de service
WO2016107374A1 (fr) Procédé, appareil et système de commande de bande passante
JP2024503864A (ja) モバイルローカルエリアネットワークサービスに対する課金処理を実行する方法、システム、および関連するデバイス
CN111698677A (zh) 用户面统计信息的上报、接收方法及网络设备
CN108667630A (zh) 一种计费方法、相关设备和系统
CN104702529A (zh) 控制业务带宽的方法、系统和设备
CN110636518B (zh) 一种性能数据统计方法及相关设备

Legal Events

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

Ref document number: 19909357

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19909357

Country of ref document: EP

Kind code of ref document: A1