WO2021057020A1 - 一种网络切片的计费方法及装置 - Google Patents

一种网络切片的计费方法及装置 Download PDF

Info

Publication number
WO2021057020A1
WO2021057020A1 PCT/CN2020/086880 CN2020086880W WO2021057020A1 WO 2021057020 A1 WO2021057020 A1 WO 2021057020A1 CN 2020086880 W CN2020086880 W CN 2020086880W WO 2021057020 A1 WO2021057020 A1 WO 2021057020A1
Authority
WO
WIPO (PCT)
Prior art keywords
charging
network
network element
request
data
Prior art date
Application number
PCT/CN2020/086880
Other languages
English (en)
French (fr)
Inventor
朱雷
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP20868159.3A priority Critical patent/EP4024913A4/en
Publication of WO2021057020A1 publication Critical patent/WO2021057020A1/zh
Priority to US17/705,059 priority patent/US20220217005A1/en

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
    • H04L12/1407—Policy-and-charging control [PCC] architecture
    • 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/141—Indication of costs
    • H04L12/1414—Indication of costs in real-time
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/41—Billing record details, i.e. parameters, identifiers, structure of call data record [CDR]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/61—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP based on the service used
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/66—Policy and charging system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/70—Administration or customization aspects; Counter-checking correct charges
    • H04M15/785—Reserving amount on the account
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/80—Rating or billing plans; Tariff determination aspects
    • H04M15/8016—Rating or billing plans; Tariff determination aspects based on quality of service [QoS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]

Definitions

  • This application relates to the field of mobile communication technology, and in particular to a charging method and device for network slicing.
  • the current 5th generation (5G) charging system supports charging based on a protocol data unit (PDU) session, and the charging data is generated by a session management network element. Since the session management network element is responsible for session management, its functions include the creation, maintenance, modification, and deletion of PDU sessions. Therefore, the session management network element collects the usage information of the PDU session data connection on the user plane network element to obtain the accounting data generation data source.
  • PDU protocol data unit
  • Network slicing can be considered as a communication network composed of multiple network function network elements created to meet a certain service requirement.
  • This application provides a charging method and device for network slicing to provide a charging method for network slicing.
  • the present application provides a network slicing charging method, the method includes: a network slicing management network element receives a first request, the first request includes a network slicing charging requirement; the network slicing management network element A second request is sent to a network slicing subnet management network element, where the second request includes the charging requirement; the network slicing management network element receives the first charging data of the network slicing, and the first charging Data is collected according to the charging requirements; the network slicing management network element sends the first charging data to the charging network element, and the first charging data is used by the charging network element to perform network slicing Billing.
  • the first charging data comes from one or more of the following network elements: a network slicing subnet management network element, a network function network element, and a network function management network element.
  • the network slice management network element collects second charging data according to the charging requirements; the network slice management network element sends the second accounting data to the charging network element. Charge data, the second charging data is used by the charging network element to perform network slicing charging.
  • the network slice management network element sends a third request to the charging network element, and the third request is used to request to enable the network slice instance charging function.
  • the third request is a network slice charging session request or an event charging request.
  • the charging requirements include at least one of the following: charging objects, charging methods, and charging function selection rules.
  • the first request is a network slice instance creation request
  • the second request is a network slice subnet instance creation request
  • the first request is a network slice instance modification request
  • the second request is a network slicing subnet instance modification request.
  • the present application provides a network slicing charging method, the method includes: a network slicing subnet management network element receives a second request from the network slicing management network element, the second request includes a charging requirement; The network slicing subnet management network element determines the first sub-charging requirement corresponding to the network function network element according to the charging requirement; the network slicing subnet management network element sends the first sub-network element to the network function network element The charging requirement, the first sub-charging requirement is used for the network function network element to collect first charging data of the network slice, and the first charging data is used for the charging network element to perform network slice charging.
  • the network slice subnet management network element receives the first charging data from the network function network element; the network slice subnet management network element sends the network slice management network element to the network slice management network element. Sending the first charging data, the first charging data is sent by the network slicing management network element to the charging network element; or, the network slicing subnet management network element is sent to the charging network Yuan sends the first charging data.
  • the network slicing subnet management network element determines a second sub-charging requirement corresponding to the network slicing subnet management network element according to the charging requirement; the network slicing subnet The management network element collects second charging data of the network slice according to the second sub-charging requirement, and the second charging data is used by the charging network element to perform network slice charging.
  • the network slice subnet management network element sends the second charging data to the network slice management network element, and the second charging data is sent by the network slice management network element to The charging network element; or, the network slicing subnet management network element sends the second charging data to the charging network element.
  • the second request is a network slice subnet instance creation request or a network slice subnet instance modification request.
  • this application provides a network slicing charging method.
  • the method includes: a network function network element receives a network slice charging requirement; the network function network element collects network slice accounting according to the charging requirement. Charge data; the network function network element sends the charging data, and the charging data is used for the charging network element to perform network slice charging.
  • the network function network element sending the charging data includes: the network function network element sending the charging data to a network slicing subnet management network element, the charging data Sent by the network slicing subnet management network element to the charging network element; or, the network function network element sends the charging data to the network slicing management network element, and the charging data is sent by the network slice
  • the management network element sends to the charging network element; or, the network function network element sends the charging data to the charging network element.
  • the present application provides a communication device, which may be a network slicing management network element, or a chip for network slicing management network element.
  • the device has the function of realizing the above-mentioned first aspect or each embodiment of the first aspect. This function can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the present application provides a communication device, which may be a network slicing subnet management network element, or a chip used for the network slicing subnet management network element.
  • the device has the function of realizing the above-mentioned second aspect or each embodiment of the second aspect. This function can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the present application provides a communication device, which may be a network function network element, or a chip for a network function network element.
  • the device has the function of realizing the foregoing third aspect or the embodiments of the third aspect. This function can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the present application provides a communication device including a processor and a memory; the memory is used to store computer-executable instructions.
  • the processor executes the computer-executable instructions stored in the memory to make the device Perform the method as described above in each aspect or each embodiment of each aspect.
  • the present application provides a communication device, including a unit or means for executing each of the above aspects or each step of each aspect.
  • the present application provides a communication device including a processor and an interface circuit, where the processor is configured to communicate with other devices through the interface circuit and execute the methods of the foregoing aspects or the embodiments of the aspects.
  • the processor includes one or more.
  • the present application provides a communication device including a processor, which is configured to be connected to a memory and used to call a program stored in the memory to execute the methods of the above aspects or the embodiments of the aspects.
  • the memory can be located inside the device or outside the device.
  • the processor includes one or more.
  • this application also provides a computer-readable storage medium having instructions stored in the computer-readable storage medium, which when run on a computer, cause a processor to execute the foregoing aspects or implementations of each aspect The method described in the example.
  • this application also provides a computer program product including instructions, which when run on a computer, causes the computer to execute the methods described in the above aspects or the embodiments of the aspects.
  • the present application also provides a chip system, including a processor, configured to execute the methods described in the foregoing aspects or the embodiments of the aspects.
  • this application also provides a communication system, including a network slicing management network element for implementing the foregoing first aspect or any implementation method of the first aspect and a network slicing management network element for implementing the foregoing second aspect or any implementation method of the second aspect
  • the network slicing subnet management network element is included in this application.
  • system further includes a network function network element for implementing the foregoing third aspect or any implementation method of the third aspect.
  • Figure 1A is a schematic diagram of a 5G network architecture based on a service-oriented architecture
  • Figure 1B is a schematic diagram of a 5G network architecture based on a point-to-point interface
  • FIG. 2 is a schematic diagram of a network slicing charging method provided by this application.
  • FIG. 3 is a schematic diagram of another network slicing charging method provided by this application.
  • FIG. 4 is a schematic diagram of another network slicing charging method provided by this application.
  • FIG. 5 is a schematic diagram of a communication device provided by this application.
  • FIG. 6 is a schematic diagram of another communication device provided by this application.
  • FIG. 7 is a schematic diagram of another communication device provided by this application.
  • FIG. 8 is a schematic diagram of a communication device provided by this application.
  • FIG. 1A it is a schematic diagram of a 5G network architecture based on a service-oriented architecture.
  • the 5G network architecture shown in FIG. 1A may include three parts, namely, a terminal equipment part, a data network (DN), and an operator network part.
  • DN data network
  • the functions of some of the network elements are briefly introduced below.
  • the operator network may include one or more of the following network elements: network exposure function (NEF) network elements, network storage function (Network Repository Function, NRF) network elements, policy control function (policy control function) , PCF) network element, unified data management (UDM) network element, application function (AF) network element, access and mobility management function (access and mobility management function, AMF) network element, session Management function (session management function, SMF) network elements, radio access network (radioaccess network, RAN), and user plane function (user plane function, UPF) network elements, etc.
  • NRF network exposure function
  • NRF Network Repository Function
  • policy control function policy control function
  • PCF Policy control function
  • UDM unified data management
  • AF application function
  • AMF access and mobility management function
  • SMF session Management function
  • radio access network radio access network
  • UPF user plane function
  • Terminal device also called user equipment (user equipment, UE)
  • UE user equipment
  • UE user equipment
  • UE user equipment
  • UE wireless transceiver function
  • land including indoor or outdoor, handheld or vehicle-mounted; it can also be deployed on water On board (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons, and satellites, etc.).
  • the terminal device may be a mobile phone (mobile phone), a tablet computer (pad), a computer with wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, an industrial control (industrial control) Wireless terminals in ), wireless terminals in self-driving, wireless terminals in remote medical, wireless terminals in smart grid, and wireless terminals in transportation safety , Wireless terminals in smart cities, wireless terminals in smart homes, etc.
  • VR virtual reality
  • AR augmented reality
  • industrial control industrial control
  • Wireless terminals in wireless terminals in self-driving, wireless terminals in remote medical, wireless terminals in smart grid, and wireless terminals in transportation safety , Wireless terminals in smart cities, wireless terminals in smart homes, etc.
  • the above-mentioned terminal equipment can establish a connection with the operator's network through an interface (such as N1, etc.) provided by the operator's network, and use the data and/or voice services provided by the operator's network.
  • the terminal device can also access the DN through the operator's network, and use the operator's service deployed on the DN and/or the service provided by a third party.
  • the above-mentioned third party may be a service party other than the operator's network and terminal equipment, and may provide other services such as data and/or voice for the terminal equipment.
  • the specific form of expression of the above-mentioned third party can be determined according to actual application scenarios, and is not limited here.
  • RAN is a sub-network of an operator's network, and an implementation system between service nodes and terminal equipment in the operator's network.
  • the terminal device To access the operator's network, the terminal device first passes through the RAN, and then can be connected to the service node of the operator's network through the RAN.
  • the RAN device in this application is a device that provides wireless communication functions for terminal devices, and the RAN device is also called an access network device.
  • the RAN equipment in this application includes but is not limited to: next-generation base stations (gnodeB, gNB), evolved node B (evolved node B, eNB), radio network controller (RNC), node B in 5G (node B, NB), base station controller (BSC), base transceiver station (BTS), home base station (for example, home evolved nodeB, or home node B, HNB), baseband unit (baseBand) unit, BBU), transmission point (transmitting and receiving point, TRP), transmission point (transmitting point, TP), mobile switching center, etc.
  • next-generation base stations gnodeB, gNB
  • evolved node B evolved node B
  • RNC radio network controller
  • node B in 5G node B, NB
  • BSC base station controller
  • BTS base transceiver station
  • home base station for example, home evolved nodeB, or home node B, HNB
  • TRP transmission point
  • the AMF network element is a control plane network element provided by the operator's network. It is responsible for the access control and mobility management of terminal equipment accessing the operator's network, including mobile status management, allocation of temporary user identities, authentication and authorization of users, etc. Features.
  • the SMF network element is mainly responsible for session management in the mobile network, such as session establishment, modification, and release. Specific functions include assigning IP addresses to users and selecting UPF that provides packet forwarding functions.
  • the UPF network element is responsible for the forwarding and receiving of user data in the terminal equipment.
  • User data can be received from the data network and transmitted to the terminal device through the access network device; the UPF network element can also receive user data from the terminal device through the access network device and forward it to the data network.
  • the transmission resources and scheduling functions of the UPF network element that provide services for the terminal equipment are managed and controlled by the SMF network element.
  • UDM network element used to generate authentication credential, user identification processing (such as storage and management of user permanent identities, etc.), access authorization control and contract data management, etc.
  • NEF network elements are mainly used to support the opening of capabilities and events.
  • the AF network element mainly supports interaction with the 3rd generation partnership project (3rd generation partnership project, 3GPP) core network to provide services, such as influencing data routing decisions, policy control functions, or providing third-party services to the network side.
  • 3rd generation partnership project 3rd generation partnership project, 3GPP
  • the PCF network element mainly supports the provision of a unified policy framework to control network behavior, provides policy rules to the control layer network functions, and is responsible for obtaining user subscription information related to policy decisions.
  • the NRF network element can be used to provide the network element discovery function, and provide the network element information corresponding to the network element type based on the request of other network elements.
  • NRF also provides network element management services, such as network element registration, update, de-registration, and network element status subscription and push.
  • a DN is a network located outside the operator's network.
  • the operator's network can access multiple DNs, and multiple services can be deployed on the DN, which can provide data and/or voice services for terminal devices.
  • DN is a private network of a smart factory.
  • the sensors installed in the workshop of the smart factory can be terminal devices.
  • a control server for the sensors is deployed in the DN, and the control server can provide services for the sensors.
  • the sensor can communicate with the control server, obtain instructions from the control server, and transmit the collected sensor data to the control server according to the instructions.
  • the DN is the internal office network of a company.
  • the mobile phones or computers of the employees of the company can be terminal devices, and the mobile phones or computers of the employees can access the information and data resources on the internal office network of the company.
  • Nnef, Nnrf, Npcf, Nudm, Naf, Namf, Nsmf, N1, N2, N3, N4, and N6 are interface serial numbers.
  • the meaning of these interface serial numbers can be referred to the meaning defined in the 3GPP standard protocol, which is not limited here.
  • FIG. 1B it is a schematic diagram of a 5G network architecture based on a point-to-point interface.
  • the interfaces between the various network elements in FIG. 1B are point-to-point interfaces, rather than service-oriented interfaces.
  • FIG. 1B also includes other network elements, such as NEF, NRF, etc., which are not shown in FIG. 1B.
  • the interface between the UE and the AMF network element is called the N1 interface
  • the interface between the AMF network element and the RAN device is called the N2 interface
  • the interface between the RAN device and the UPF network element It can be called N3 interface
  • the interface between SMF network element and UPF network element is called N4 interface
  • the interface between PCF network element and AF network element is called N5 interface
  • the interface between UPF network element and DN is called N6 Interface
  • the interface between SMF network element and PCF network element is called N7 interface
  • the interface between AMF network element and UDM network element is called N8 interface
  • the interface between different UPF network elements is called N9 interface
  • UDM network element The interface with the SMF network element is called the N10 interface
  • the interface between the AMF network element and the SMF network element is called the N11 interface
  • the interface between different AMF network elements is called the N14 interface
  • the one between the AMF network element and the PCF network element The interface between is called N15 interface.
  • the aforementioned network elements or functions may be network elements in hardware devices, software functions running on dedicated hardware, or virtualization functions instantiated on a platform (for example, a cloud platform).
  • a platform for example, a cloud platform.
  • the foregoing network element or function may be implemented by one device, or jointly implemented by multiple devices, or may be a functional module in one device, which is not specifically limited in the embodiment of the present application.
  • network slicing management network elements may also be added.
  • the network slice management network element may be, for example, a network slice management function (NSMF) network element, referred to as NSMF for short.
  • the network slice subnet management network element may be, for example, a network slice subnet management function (NSSMF) network element, referred to as NSSMF for short.
  • the network function management network element may be, for example, a network function management function (NFMF) network element, referred to as NFMF for short.
  • the charging network element may be, for example, a charging function (CHF) network element, referred to as CHF for short.
  • CHF charging function
  • the mobility management network element, the session management network element, the policy control network element, the application function network element, the access network device, the network opening function network element, and the user plane network element in this application may be those in FIG. 1A or FIG. 1B, respectively.
  • AMF, SMF, PCF, AF, RAN, NEF, UPF, or future communications such as the 6th generation (6G) network with the above-mentioned functions of AMF, SMF, PCF, AF, RAN, NEF, UPF Yuan, this application is not limited.
  • mobility management network elements session management network elements, policy control network elements, application function network elements, access network equipment, network open function network elements, and user plane network elements are respectively the above-mentioned AMF, SMF, and SMF.
  • AMF Access Management Function
  • SMF Session Management Function
  • SMF Session Management Function
  • SMF Session Management Function
  • UPF User Plane Function
  • NF network function
  • AMF Access Management Function
  • UPF User Plane Function
  • SMF Serving Mobility Management Function
  • PCF Packet Control Function
  • the charging system includes charging trigger function (Charging Trigger Function, CTF) network elements (hereinafter referred to as CTF) and CHF.
  • CTF Charging Trigger Function
  • CHF includes the function of generating charging data record (CDR).
  • CGF Charging GateWay Function
  • CGF Charging GateWay Function
  • the current 5G charging system supports charging based on protocol data unit (PDU) sessions, and the charging data is generated by SMF integrated with CTF. Since SMF is responsible for session management and its functions include the creation, maintenance, modification, and deletion of PDU sessions, SMF collects the usage information of the PDU session data connection on the UPF, thereby obtaining the data source that generates the charging data.
  • PDU protocol data unit
  • Quota management is also supported between SMF and CHF. Quota is the limit on the usage of slice billing in the billing system, which is generally allocated to the network first Part of the quota, when the quota is reached, apply for a new quota to the billing system.
  • SMF maintains charging data in a charging session, so SMF needs to establish a charging session between SMF and CHF during the PDU session establishment phase.
  • the SMF supports the inclusion of single network slice selection assistance information (S-NSSAI) in the charging data sent to the CHF, and thus can support network slice-based charging.
  • the charging data received by the CHF includes the S-NSSAI of the network slice instance where the PDU session is located. Therefore, the S-NSSAI can be included in the generated CDR, so that data connections in a network slice can be counted. Usage.
  • network slicing can be regarded as a communication network composed of multiple network function network elements created to meet a certain service requirement.
  • Network slicing can be shared by multiple services, or exclusive to one service, and is suitable for multiple communication services deployed on the same infrastructure of the operator.
  • Network slicing is an on-demand networking method.
  • Network operators deploy multiple virtual network slices or end-to-end networks on a unified infrastructure.
  • Each network slice ranges from the wireless access network to the bearer network to the core network. It is logically isolated and adapts to various types of business applications.
  • a network slice includes at least a wireless sub-slice, a bearer sub-slice, and a core network sub-slice.
  • the deployment template of a network slice defines the structure and configuration of a network slice.
  • the network slicing instance deployed based on the network slicing deployment template is a complete logical network formed by a series of orchestration, deployment and configuration of network functions and the resources contained in the network functions, which can meet specific network requirements.
  • NFV Network Function Virtualization
  • the hardware is uniformly deployed by general-purpose servers, and the software part is undertaken by different NFs (network functions), so as to achieve the needs of flexible assembly services.
  • SLA service level agreement
  • SLA includes parameters such as the number of users, quality of service (QoS), and bandwidth.
  • QoS quality of service
  • bandwidth bandwidth
  • the creation of a network slice instance is an instantiation process triggered according to the business requirements of the communication service consumers.
  • Consumers of communication services have many types of business requirements for network slicing, which can be roughly divided into: Latency, Guaranteed/non-guaranteed QoS (Guaranteed/non-guaranteed QoS), Peak throughput, and data volume ( Data Volumes, Reliability, Upstream/Downstream Throughput for Single Network Slice Instance, Average Number of PDU Sessions of Network Slice Instance (Mean number of PDU sessions of network) Slice Instance, Registered Subscribers of Network Slice Instance, Mobility (Mobility), and Coverage (Coverage Area).
  • the above SLA requirements are partly achieved through the modification process of network slicing instances, such as the problem of network slicing capacity, and partly achieved through the process of network service configuration, such as the coverage of a certain service, the UE of a certain service Density support, maximum peak rate, etc.
  • the charging system hopes to collect information related to the network slice SLA as a basis for the charging system to generate charging data, CDR, and even bills.
  • Different types of communication services have different SLA requirements for network slicing, so there are differences in the charging requirements for network slicing, and the relevant charging requirements and differences need to be clarified in the charging process.
  • the network slice instance is deactivated before network slice modification; after network slice modification, the service configuration of the network function needs to be modified. After the service configuration modification is completed, the activation operation is started.
  • the life cycle management operations of network slicing are generally in the deployment stage.
  • the network slice creation/modification/delete operation that the network slice management entity is responsible for may be an instantiation operation of a network slice instance (for example, creating a virtual resource, creating a virtual machine, loading a software image, loading an initial configuration, etc.).
  • the network slicing instance runs as a network instance, and the management entity for which the operation and maintenance data is reported is the operation and maintenance (Operation, Administration and Management, OAM) entity.
  • OAM Operaation, Administration and Management
  • the network slicing management entity can be used as one of the entities that obtain the operation and maintenance data.
  • Another situation is that when the instantiation process of the network slice instance has been completed, for example, after a shared slice has been deployed, a new service is added to the shared network slice instance (for example, using an S-NSSAI to identify the network Slice instance service).
  • This process may require appropriate expansion operations on the network slice instance, as well as service configuration for network functions, such as configuring the corresponding S-NSSAI operation.
  • the operation of the network slice instance can be an operation during the instantiation of the network slice; it can also be the modification of the network slice, the modification of network service parameters, and the modification of the network slice in order to add a certain service after the network slice instance is created. Activation and deactivation operations.
  • the current standard defines a series of standards for 5G network and network slicing management orchestration, adopts a 5G management service-oriented architecture, and defines management services.
  • the management services of 5G network management include: Provisioning management service, Performance management service (PM) and Fault management service (FM).
  • the management capabilities provided by the management service can be divided into NF management capabilities (for example, 5G core network NF management), network slicing subnet management capabilities, and network slicing management capabilities.
  • NF management services or management capabilities provided by NF management services
  • NFMF network slice subnet management service
  • NSSMF network slice subnet management capability
  • NFMF network slice management capability
  • CSMF communication service management function
  • CSMF Complete the user business communication service demand ordering and processing, convert the communication service demand into the network slicing demand for NSMF, and then send the network slice deployment request to NSMF according to the network slicing demand.
  • the CSMF management object is communication services, and each communication service is completed by one or more network slicing functions.
  • NSMF Receive a network slice deployment request issued by CSMF, and issue a network subnet slice deployment request to NSSMF.
  • the management object of NSMF is network slices, and each network slice may include one or more network subnet slices (also referred to as sub-network slices, or network sub-slices, or sub-slices, or network-slicing subnets, etc.).
  • NSSMF Receive the network subnet slice deployment request issued from the NSMF, and issue the network function deployment request to the NFMF.
  • the NSSMF management object is a network subnet slice, and each network subnet slice can be a basic subslice, or a subslice composed of multiple basic subslices. Each sub-slice can contain one or more network functions.
  • NFMF used to manage NFs, such as AMF, SMF, UPF, PCF, etc.
  • the functions of network slicing management include life cycle management of network slicing, PM and FM of network slicing, etc.
  • the scope of network management includes network configuration, PM and FM. Since the data sources of PM/FM for network slicing management and PM/FM for network management are the same, and the management objectives to be achieved are similar, it can be considered that there is no significant difference between PM/FM for network slicing management and PM/FM for network management.
  • the network slicing management function and network slicing subnet management function mainly work in the network slicing deployment stage.
  • the operating state of the network management is mainly the scope of network management.
  • the management data for a certain tenant in the network slice instance needs to be separately counted. Therefore, in the charging process of network slicing, for the management data of a certain tenant, charging data needs to be separately generated based on the tenant identification (tenant ID) and the charging data of the corresponding tenant, and an independent charging session is established.
  • the network slice subnet management function and the network function management function are deployed in the same location, and are responsible for slice subnet management and NF management respectively, and the relationship between them refers to the coordination relationship between network slice management and network management.
  • the identifier for distinguishing different services at the NF level is S-NSSAI, and the relevant management data of different network slice instances are distinguished by S-NSSAI.
  • this application provides a network slicing charging method. As shown in FIG. 2, the method includes the following steps:
  • Step 201 NSMF receives a first request, where the first request includes a charging requirement for network slicing.
  • the NSMF receives the first request from CSMF or other network elements.
  • the charging requirements here include at least one of the following: charging objects, charging methods, and charging function (CHF) selection rules.
  • the charging object includes at least one of the following: the number of user connections, the number of users, the throughput, the number of sessions, the length of the session, and the virtual resources.
  • Billing methods include offline or online.
  • the charging function selection rule is used to find the address of the charging function network element.
  • Step 202 The NSMF sends a second request to the NSSMF, where the second request includes the aforementioned charging requirements.
  • NSSMF can receive the second request.
  • the above-mentioned first request is a network slice instance creation request
  • the second request is a network slice subnet instance creation request
  • the above-mentioned first request is a network slice instance modification request
  • the second request is a network slice subnet instance modification request.
  • Step 203 NSMF sends a third request to CHF.
  • the CHF can receive the third request.
  • the third request is used to request to enable the network slicing instance charging function.
  • the third request may be, for example, a network slicing charging session request or an event charging request.
  • This step is optional.
  • Step 204 The NSSMF determines the first sub-charging requirement corresponding to the NF according to the charging requirement, and sends the first sub-charging requirement to the NF.
  • the first sub-charging requirement is used by the NF to collect the first charging data of the network slice.
  • the first charging data is used for CHF to perform network slice charging.
  • the NF can receive the first sub-charging request.
  • the first sub-charging request sent to the AMF carries the charging object (such as the number of user connections, the number of users, and the throughput), the charging method (such as offline or online), and the rules for the selection of charging functions.
  • the first sub-charging request sent to the SMF carries the charging object (such as the number of sessions, the duration of the session), the charging method (such as offline or online), and the rules for the selection of charging functions.
  • Step 205 NSMF, NSSMF, NFMF and each NF report the collected charging data to CHF.
  • each NF collects the charging data for the corresponding charging object according to the corresponding charging method according to the first sub-charging request sent to it, and then reports it to the CHF.
  • NSSMF obtains the second sub-charging request according to the charging request sent by NSMF, collects charging data for the corresponding charging object according to the corresponding charging method, and then reports it to CHF.
  • the NFMF collects the charging data for the corresponding charging object according to the corresponding charging method according to the sub-charging requirement (may be called the third sub-charging requirement) sent by the NSSMF, and then reports it to the CHF.
  • the sub-charging requirement may be called the third sub-charging requirement
  • NSMF collects charging data for the corresponding charging objects according to the corresponding charging method, and then reports it to the CHF.
  • the following describes the charging data collected and reported by NSMF, NSSMF, NFMF, and each NF.
  • SMF can provide charging data related to the PDU session in the network slicing instance, such as the length of the session and the number of sessions.
  • the related charging data is based on PDU session statistics.
  • AMF can provide charging data related to AMF handover of a certain UE in a certain network slice instance.
  • the AMF handover When the mobility of the UE (ie, the AMF handover) is used as the charging data, the AMF handover times of a certain UE based on the AMF statistics can be provided to the CHF according to the event charging trigger condition.
  • AMF can also provide charging data such as the number of user connections, the number of users, and throughput.
  • NEF can provide the number of times that a certain application (application service) calls the network capability application programming interface (API) in a network slicing instance. The number of times that a certain application calls the network capability API can be provided to the CHF as the charging data according to the event charging trigger condition.
  • application service application service
  • API application programming interface
  • NWDAF can provide real-time performance statistics of network performance in network slicing instances, and can also provide advanced performance statistics based on data analysis capabilities, such as statistics on service experience of a certain service. Based on the performance statistical content and statistical frequency requirements provided in the billing requirements, NWDAF can adopt the event billing method to provide performance statistical data to the CHF.
  • NFMF provides NF-related performance metrics.
  • Typical performance metrics related to network slicing include:
  • Performance metrics related to UPF including: the number of packets on the N3 interface, the throughput on the N3 interface, the number of packets on the N6 interface, and the throughput on the N6 interface;
  • the performance metrics provided by AMF include: the number of registered users on a network slice instance, the number of successfully registered users on a network slice instance, the number of successful service requests on a network slice instance, and a network slice The number of users registered on the non-3GPP network on the instance, and the number of cross-AMF handovers on a network slice instance;
  • the performance metrics provided by SMF include: the number of PDU sessions on a network slice instance, the number of PDU sessions modified on a network slice instance, and the number of PDU sessions released on a network slice instance;
  • Each network function can provide the usage of virtual resources.
  • NSMF can provide CHF with charging data for network slicing management operations according to the requirements of network slicing charging.
  • NSSMF can provide CHF with charging data for network slicing management operations according to the requirements of network slicing charging.
  • the methods for each NF to report the collected charging data to the CHF include but are not limited to:
  • the path for NF such as AMF and SMF to report charging data to CHF can be: NF->NWDAF->NFMF->NSSMF->NSMF->CHF. That is, NF reports charging data to CHF through NWDAF, NFMF, NSSMF, and NSMF.
  • the path for NF such as AMF and SMF to report charging data to CHF can be: NF->NFMF->NSSMF->NSMF->CHF. That is, NF reports charging data to CHF through NFMF, NSSMF, and NSMF.
  • the path for NF such as AMF and SMF to report charging data to CHF can be: NF->NFMF->NSSMF->CHF. That is, NF reports charging data to CHF through NFMF and NSSMF.
  • the path for NF such as AMF and SMF to report charging data to CHF can be: NF->NFMF->CHF. That is, NF reports charging data to CHF through NFMF.
  • the path for NF such as AMF and SMF to report charging data to CHF can be: NF->NWDAF->CHF. That is, NF reports charging data to CHF through NWDAF.
  • the path for NF such as AMF and SMF to report charging data to CHF can be: NF->CHF. That is, the NF directly reports the charging data to the CHF.
  • NFMF neurotrophic factor
  • the path for NFMF to report charging data to CHF can be: NFMF->NSSMF->NSMF->CHF. That is, NFMF reports charging data to CHF through NSSMF and NSMF.
  • the path for NFMF to report charging data to CHF can be: NFMF->NSMF->CHF. That is, NFMF reports charging data to CHF through NSMF.
  • the path for NFMF to report charging data to CHF can be: NFMF->NSSMF->CHF. That is, NFMF reports charging data to CHF through NSSMF.
  • the path for NFMF to report charging data to CHF can be: NFMF->CHF. That is, NFMF directly reports charging data to CHF.
  • the methods for NSMF to report the collected charging data to CHF include but are not limited to:
  • the path for NSMF to report charging data to CHF can be: NSMF->CHF. That is, NSMF directly reports charging data to CHF.
  • NSSMF NSSMF to report the collected charging data to CHF.
  • the path for NSSMF to report charging data to CHF can be: NSSMF->CHF. That is, NSSMF directly reports charging data to CHF.
  • the path for NSSMF to report charging data to CHF can be: NSSMF->NSMF->CHF. That is, NSSMF reports charging data to CHF through NSMF.
  • the charging data can also be sorted according to the network slice charging requirements, and then the charging data is provided to the CHF according to the corresponding transmission frequency requirements.
  • Step 206 The CHF charges the network slice according to the received charging data.
  • FIG. 3 it is a schematic flowchart of another network slicing charging method provided by this application. This method is to charge the network slice during the deployment process of the network slice.
  • the method includes the following steps:
  • Step 301 The communication service user sends a communication service creation request to CSMF.
  • the CSMF can receive the communication service creation request.
  • Step 302 CSMF sends a network slice instance creation request to NSMF.
  • the NSMF can receive the network slice instance creation request.
  • the network slicing instance creation request carries the charging requirements required by the network slicing instance.
  • the content contained in the charging requirements reference may be made to the description of the embodiment in FIG. 2, which will not be repeated here.
  • the network slice instance creation request may also carry service requirements for network slice creation.
  • Step 303 NSMF sends a network slicing subnet instance creation request to NSSMF.
  • NSSMF can receive the network slicing subnet instance creation request.
  • the network slicing subnet instance creation request carries the foregoing charging requirements.
  • Step 304 NSSMF creates a network slicing subnet instance.
  • NSSMF instantiates the network slice and configures the corresponding network configuration parameters; on the other hand, it decomposes the above-mentioned charging requirements into multiple sub-charging requirements and sends them to each NF.
  • Step 305 NSMF sends a network slice charging session request to CHF.
  • the CHF can receive the network slice charging session request.
  • NSMF can send a network slicing charging session request to the CHF (this request is an initial request), and the CHF will start the network after receiving the network slicing charging session request Charging CHF and CDR for slice instance.
  • NSMF can also send an event charging request to CHF (this request is an initial request), and CHF receives After the event charging request is received, the network slice instance charging CHF CDR is turned on.
  • the NSMF can obtain the CHF address according to the charging function selection rule in the charging requirement.
  • Step 306 the running state of the network slicing subnet instance after it is created.
  • Step 307 NSMF, NSSMF, NFMF and each NF report the collected charging data to CHF.
  • FIG. 4 it is a schematic flowchart of another network slicing charging method provided by this application. This method is to charge the network slice during the process of adding network slice instances during the operation phase of the network slice instance.
  • the method includes the following steps:
  • Step 401 The communication service user sends a communication service creation request to CSMF.
  • the CSMF can receive the communication service creation request.
  • Step 402 CSMF sends a network slice instance modification request to NSMF.
  • NSMF can receive the request for creation and modification of the network slice instance.
  • the network slicing instance modification request carries the charging requirements required by the network slicing instance.
  • the content contained in the charging requirements reference may be made to the description of the embodiment in FIG. 2, which will not be repeated here.
  • Step 403 NSMF sends a modification request to NSSMF.
  • NSSMF can receive the modification request.
  • the modification request carries the aforementioned charging requirements.
  • the modification request is used to request modification of the network slicing subnet instance and NF configuration parameters.
  • Step 404 NSSMF modifies the network slicing subnet instance and NF configuration parameters.
  • the network slicing instance is in a running state, and the modification of the network slicing subnet instance can be completed by modifying the network configuration or by expanding the network slicing subnet instance.
  • the modified NF configuration parameters here include but are not limited to: adding capacity and adding new configured S-NSSAI parameters.
  • NSSMF decomposes the above charging requirements into multiple sub-charging requirements and sends them to each NF.
  • Step 405 NSMF sends a network slice charging session request to CHF.
  • the CHF can receive the network slice charging session request.
  • NSMF can send a network slicing charging session request to CHF (this request is an initial request), and CHF will start the network after receiving the network slicing charging session request Charging CHF and CDR for slice instance.
  • step 405 if the network slice charging created by NSMF to CHF is an event charging, NSMF can also send an event charging request to CHF (this request is an initial request), and CHF receives After the event charging request is received, the network slice instance charging CHF CDR is turned on.
  • the NSMF can obtain the CHF address according to the charging function selection rule in the charging requirement.
  • Step 406 the modified operating state of the network slicing subnet instance.
  • Step 407 NSMF, NSSMF, NFMF and each NF report the collected charging data to CHF.
  • each network element described above includes hardware structures and/or software modules corresponding to each function.
  • the present invention can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software-driven hardware depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered as going beyond the scope of the present invention.
  • a device for implementing any of the above methods.
  • a device is provided that includes units (or means) for implementing each step performed by the network slice management network element in any of the above methods.
  • another device is also provided, including a unit (or means) for implementing each step performed by the network slicing subnet management network element in any of the above methods.
  • another device is also provided, including a unit (or means) for implementing each step performed by a network function network element in any of the above methods.
  • FIG. 5 is a schematic diagram of a communication device provided by an embodiment of the application.
  • the device is used for network slicing management network elements.
  • the device 500 includes a receiving unit 501 and a sending unit 502.
  • the device 500 further includes a charging data collecting unit 503.
  • the receiving unit 501 is configured to receive a first request, and the first request includes a charging requirement for network slicing; and the sending unit 502 is configured to send a second request to a network slicing subnet management network element.
  • the second request includes the charging requirement;
  • the receiving unit 501 is further configured to receive the first charging data of the network slice, the first charging data is collected according to the charging requirement;
  • the sending The unit 502 is further configured to send the first charging data to the charging network element, where the first charging data is used for the charging network element to perform network slice charging.
  • the first charging data comes from one or more of the following network elements: a network slicing subnet management network element, a network function network element, and a network function management network element.
  • the charging data collecting unit 503 is configured to collect the second charging data according to the charging requirements; the sending unit 502 is also configured to send all the charging data to the charging network element.
  • the second charging data is used by the charging network element to perform network slice charging.
  • the sending unit 502 is further configured to send a third request to the charging network element, and the third request is used to request to enable the network slice instance charging function.
  • the third request is a network slice charging session request or an event charging request.
  • the charging requirements include at least one of the following: charging objects, charging methods, and charging function selection rules.
  • the first request is a network slice instance creation request
  • the second request is a network slice subnet instance creation request
  • the first request is a network slice instance modification request
  • the second request is a network slicing subnet instance modification request.
  • FIG. 6 is a schematic diagram of another communication device provided by an embodiment of the application.
  • the device is used for network slicing subnet management network elements.
  • the device 600 includes a receiving unit 601, a charging requirement determining unit 602, and a sending unit 603.
  • the device 600 further includes a charging data collecting unit 604.
  • the receiving unit 601 is further configured to receive the first charging data from the network function network element; the sending unit 603 is further configured to manage the network element from the network slice Sending the first charging data, the first charging data is sent by the network slice management network element to the charging network element; or, used to send the first charging data to the charging network element Fee data.
  • the charging requirement determining unit 602 is further configured to determine a second sub-charging requirement corresponding to the network slicing subnet management network element according to the charging requirement; charging data The collecting unit 604 is configured to collect second charging data of the network slice according to the second sub-charging requirement, where the second charging data is used for the charging network element to perform network slice charging.
  • the sending unit 603 is further configured to send the second charging data to a network slice management network element, and the second charging data is sent by the network slice management network element to The charging network element; or, for sending the second charging data to the charging network element.
  • the second request is a network slice subnet instance creation request or a network slice subnet instance modification request.
  • FIG. 7 is a schematic diagram of another communication device provided by an embodiment of the application.
  • the device is used for network function network elements.
  • the device 700 includes a receiving unit 701, a sending unit 702, and a charging data collecting unit 703.
  • the receiving unit 701 is used to receive the charging requirements of the network slice; the charging data collecting unit 703 is used to collect the charging data of the network slice according to the charging requirements; the sending unit 702 is used to send the charging data , The charging data is used for charging network elements to perform network slice charging.
  • the sending unit 702 is specifically configured to: send the charging data to a network slicing subnet management network element, and the charging data is sent by the network slicing subnet management network element To the charging network element; or, to send the charging data to the network slice management network element, and the charging data is sent to the charging network element by the network slice management network element; or, to the The charging network element sends the charging data.
  • each unit in the device can be all implemented in the form of software called by processing elements; they can also be all implemented in the form of hardware; part of the units can also be implemented in the form of software called by the processing elements, and some of the units can be implemented in the form of hardware.
  • each unit can be a separate processing element, or it can be integrated in a certain chip of the device for implementation.
  • it can also be stored in the memory in the form of a program, which is called and executed by a certain processing element of the device.
  • each step of the above method or each of the above units may be implemented by an integrated logic circuit of hardware in a processor element or implemented in a form of being called by software through a processing element.
  • the unit in any of the above devices may be one or more integrated circuits configured to implement the above methods, for example: one or more application specific integrated circuits (ASICs), or, one or Multiple microprocessors (digital singnal processors, DSPs), or, one or more field programmable gate arrays (Field Programmable Gate Arrays, FPGAs), or a combination of at least two of these integrated circuits.
  • ASICs application specific integrated circuits
  • DSPs digital singnal processors
  • FPGAs Field Programmable Gate Arrays
  • the unit in the device can be implemented in the form of a processing element scheduler
  • the processing element can be a general-purpose processor, such as a central processing unit (CPU) or other processors that can call programs.
  • CPU central processing unit
  • these units can be integrated together and implemented in the form of a system-on-a-chip (SOC).
  • the above receiving unit is an interface circuit of the device for receiving signals from other devices.
  • the receiving unit is an interface circuit used by the chip to receive signals from other chips or devices.
  • the above unit for sending is an interface circuit of the device for sending signals to other devices.
  • the sending unit is an interface circuit used by the chip to send signals to other chips or devices.
  • FIG. 8 is a schematic structural diagram of a communication device provided by an embodiment of this application.
  • the communication device may be a network slicing management network element, or a network slicing subnet management network element, or a network function network element for implementing The operations of the network slice management network element, or the network slice subnet management network element, or the network function network element in the above embodiments.
  • the communication device includes: a processor 810, a memory 820, and an interface 830, and the processor 810, the memory 820, and the interface 830 are connected in signal.
  • the method executed by the communication device in the above embodiment may be implemented by the processor 810 calling a program stored in the memory 820. That is, the communication device includes a memory and a processor, and the memory is used to store a program, and the program is called by the processor to execute the method executed by the communication device in the above method embodiment.
  • the processor here may be an integrated circuit with signal processing capability, such as a CPU.
  • the apparatus for the session management network element may be realized by one or more integrated circuits configured to implement the above method. For example: one or more ASICs, or, one or more microprocessors DSP, or, one or more FPGAs, etc., or a combination of at least two of these integrated circuit forms. Or, the above implementations can be combined.
  • the computer may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software it can be implemented in the form of a computer program product in whole or in part.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • the computer instructions may be transmitted from a website, computer, server, or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or a data center integrated with one or more available media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)).
  • the various illustrative logic units and circuits described in the embodiments of this application can be implemented by general-purpose processors, digital signal processors, application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, Discrete gates or transistor logic, discrete hardware components, or any combination of the above are designed to implement or operate the described functions.
  • the general-purpose processor may be a microprocessor.
  • the general-purpose processor may also be any traditional processor, controller, microcontroller, or state machine.
  • the processor can also be implemented by a combination of computing devices, such as a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors combined with a digital signal processor core, or any other similar configuration. achieve.
  • the aforementioned functions described in this application can be implemented in hardware, software, firmware, or any combination of the three. If implemented in software, these functions can be stored on a computer-readable medium, or transmitted on the computer-readable medium in the form of one or more instructions or codes.
  • Computer-readable media include computer storage media and communication media that facilitate the transfer of computer programs from one place to another. The storage medium can be any available medium that can be accessed by a general-purpose or special computer.
  • Such computer-readable media may include, but are not limited to, RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other device that can be used to carry or store instructions or data structures and Other program code media that can be read by general-purpose or special computers, or general-purpose or special processors.
  • any connection can be appropriately defined as a computer-readable medium, for example, if the software is from a website, server, or other remote source through a coaxial cable, fiber optic computer, twisted pair, or digital subscriber line (DSL) Or transmitted by wireless means such as infrared, wireless and microwave are also included in the definition of computer-readable media.
  • DSL digital subscriber line
  • the said disks and discs include compressed disks, laser disks, optical discs, digital versatile discs (English: Digital Versatile Disc, abbreviated as: DVD), floppy disks and Blu-ray discs.
  • Disks usually copy data with magnetism.
  • Discs usually use lasers to copy data optically.
  • the combination of the above can also be contained in a computer readable medium.
  • the functions described in this application can be implemented by hardware, software, firmware, or any combination thereof. When implemented by software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on the computer-readable medium.
  • the computer-readable medium includes a computer storage medium and a communication medium, where the communication medium includes any medium that facilitates the transfer of a computer program from one place to another.
  • the storage medium may be any available medium that can be accessed by a general-purpose or special-purpose computer.

Landscapes

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

Abstract

本申请提供一种网络切片的计费方法及装置。该方法包括：网络切片管理网元接收第一请求，第一请求包括网络切片的计费要求；网络切片管理网元向网络切片子网管理网元发送第二请求，第二请求包括计费要求；网络切片管理网元接收网络切片的第一计费数据，第一计费数据是根据计费要求收集的；网络切片管理网元向计费网元发送第一计费数据，第一计费数据用于计费网元进行网络切片计费。通过上述方案，可以实现对网络切片进行计费。并且，还给出了各个网元上报计费数据的不同实现方法，有助于提升网络切片计费的准确性。

Description

一种网络切片的计费方法及装置
相关申请的交叉引用
本申请要求在2019年09月29日提交中国专利局、申请号为201910936221.2、申请名称为“一种网络切片的计费方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及移动通信技术领域，尤其涉及一种网络切片的计费方法及装置。
背景技术
当前第五代(5th generation，5G)计费系统支持基于协议数据单元(protocol data unit，PDU)会话的计费，计费数据由会话管理网元产生。由于会话管理网元负责会话管理，其功能包括PDU会话的创建、维护、修改和删除，因而会话管理网元收集用户面网元上的PDU会话数据连接的使用信息，从而得到产生计费数据的数据源。
目前，在5G通信中引入了网络切片的概念。网络切片可以认为是为了满足某一个业务需求，而创建的由多个网络功能网元组成的通信网络。
如何对网络切片进行计费，目前还没有相应的方法。
发明内容
本申请提供一种网络切片的计费方法及装置，用以提供一种网络切片的计费方法。
第一方面，本申请提供一种网络切片的计费方法，该方法包括：网络切片管理网元接收第一请求，所述第一请求包括网络切片的计费要求；所述网络切片管理网元向网络切片子网管理网元发送第二请求，所述第二请求包括所述计费要求；所述网络切片管理网元接收所述网络切片的第一计费数据，所述第一计费数据是根据所述计费要求收集的；所述网络切片管理网元向计费网元发送所述第一计费数据，所述第一计费数据用于所述计费网元进行网络切片计费。通过该方案，可以实现对网络切片进行计费，可以实现对网络切片进行准确计费。
在一种可能的实现方法中，所述第一计费数据来自以下一个或多个网元：网络切片子网管理网元、网络功能网元、网络功能管理网元。
在一种可能的实现方法中，所述网络切片管理网元根据所述计费要求，收集第二计费数据；所述网络切片管理网元向所述计费网元发送所述第二计费数据，所述第二计费数据用于所述计费网元进行网络切片计费。
在一种可能的实现方法中，所述网络切片管理网元向所述计费网元发送第三请求，所述第三请求用于请求开启网络切片实例计费功能。
在一种可能的实现方法中，所述第三请求为网络切片计费会话请求、或事件计费请求。
在一种可能的实现方法中，所述计费要求包括以下至少一项：计费对象、计费方式和计费功能选择的规则。
在一种可能的实现方法中，所述第一请求为网络切片实例创建请求，所述第二请求为网络切片子网实例创建请求；或者，所述第一请求为网络切片实例修改请求，所述第二请求为网络切片子网实例修改请求。
第二方面，本申请提供一种网络切片的计费方法，该方法包括：网络切片子网管理网元从网络切片管理网元接收第二请求，所述第二请求包括计费要求；所述网络切片子网管理网元根据所述计费要求，确定网络功能网元对应的第一子计费要求；所述网络切片子网管理网元向所述网络功能网元发送所述第一子计费要求，所述第一子计费要求用于所述网络功能网元收集网络切片的第一计费数据，所述第一计费数据用于计费网元进行网络切片计费。通过该方案，可以实现对网络切片进行计费，可以实现对网络切片进行准确计费。
在一种可能的实现方法中，所述网络切片子网管理网元接收来自所述网络功能网元的所述第一计费数据；所述网络切片子网管理网元向网络切片管理网元发送所述第一计费数据，所述第一计费数据由所述网络切片管理网元发送至所述计费网元；或者，所述网络切片子网管理网元向所述计费网元发送所述第一计费数据。
在一种可能的实现方法中，所述网络切片子网管理网元根据所述计费要求，确定所述网络切片子网管理网元对应的第二子计费要求；所述网络切片子网管理网元根据所述第二子计费要求，收集网络切片的第二计费数据，所述第二计费数据用于所述计费网元进行网络切片计费。
在一种可能的实现方法中，所述网络切片子网管理网元向网络切片管理网元发送所述第二计费数据，所述第二计费数据由所述网络切片管理网元发送至所述计费网元；或者，所述网络切片子网管理网元向所述计费网元发送所述第二计费数据。
在一种可能的实现方法中，所述第二请求为网络切片子网实例创建请求、或网络切片子网实例修改请求。
第三方面，本申请提供一种网络切片的计费方法，该方法包括：网络功能网元接收网络切片的计费要求；所述网络功能网元根据所述计费要求，收集网络切片的计费数据；所述网络功能网元发送所述计费数据，所述计费数据用于计费网元进行网络切片计费。通过该方案，可以实现对网络切片进行计费，可以实现对网络切片进行准确计费。
在一种可能的实现方法中，所述网络功能网元发送所述计费数据，包括：所述网络功能网元向网络切片子网管理网元发送所述计费数据，所述计费数据由所述网络切片子网管理网元发送至所述计费网元；或者，所述网络功能网元向网络切片管理网元发送所述计费数据，所述计费数据由所述网络切片管理网元发送至所述计费网元；或者，所述网络功能网元向所述计费网元发送所述计费数据。
第四方面，本申请提供一种通信装置，该装置可以是网络切片管理网元，还可以是用于网络切片管理网元的芯片。该装置具有实现上述第一方面或第一方面的各实施例的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第五方面，本申请提供一种通信装置，该装置可以是网络切片子网管理网元，还可以是用于网络切片子网管理网元的芯片。该装置具有实现上述第二方面或第二方面的各实施例的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第六方面，本申请提供一种通信装置，该装置可以是网络功能网元，还可以是用于网 络功能网元的芯片。该装置具有实现上述第三方面或第三方面的各实施例的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第七方面，本申请提供一种通信装置，包括处理器和存储器；该存储器用于存储计算机执行指令，当该装置运行时，该处理器执行该存储器存储的该计算机执行指令，以使该装置执行如上述各方面或各方面的各实施例的方法。
第八方面，本申请提供一种通信装置，包括用于执行上述各方面或各方面的各个步骤的单元或手段(means)。
第九方面，本申请提供一种通信装置，包括处理器和接口电路，所述处理器用于通过接口电路与其它装置通信，并执行上述各方面或各方面的各实施例的方法。该处理器包括一个或多个。
第十方面，本申请提供一种通信装置，包括处理器，用于与存储器相连，用于调用所述存储器中存储的程序，以执行上述各方面或各方面的各实施例的方法。该存储器可以位于该装置之内，也可以位于该装置之外。且该处理器包括一个或多个。
第十一方面，本申请还提供一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得处理器执行上述各方面或各方面的各实施例所述的方法。
第十二方面，本申请还提供一种包括指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述各方面或各方面的各实施例所述的方法。
第十三方面，本申请还提供一种芯片系统，包括：处理器，用于执行上述各方面或各方面的各实施例所述的方法。
第十四方面，本申请还提供一种通信系统，包括用于实现上述第一方面或第一方面任意实现方法的网络切片管理网元和用于实现上述第二方面或第二方面任意实现方法的网络切片子网管理网元。
在一种可能的实现方法中，所述系统还包括用于实现上述第三方面或第三方面任意实现方法的网络功能网元。
附图说明
图1A为基于服务化架构的5G网络架构示意图；
图1B为基于点对点接口的5G网络架构示意图；
图2为本申请提供的一种网络切片的计费方法示意图；
图3为本申请提供的又一种网络切片的计费方法示意图；
图4为本申请提供的又一种网络切片的计费方法示意图；
图5为本申请提供的一种通信装置示意图；
图6为本申请提供的又一种通信装置示意图；
图7为本申请提供的又一种通信装置示意图；
图8为本申请提供的一种通信装置示意图。
具体实施方式
为了使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请作进一步地详细描述。方法实施例中的具体操作方法也可以应用于装置实施例或系统实施例中。其中，在本申请的描述中，除非另有说明，“多个”的含义是两个或两个以上。
如图1A所示，为基于服务化架构的5G网络架构示意图。图1A所示的5G网络架构中可包括三部分，分别是终端设备部分、数据网络(data network，DN)和运营商网络部分。下面对其中的部分网元的功能进行简单介绍说明。
其中，运营商网络可包括以下网元中的一个或多个：网络开放功能(network exposure function，NEF)网元、网络存储功能(Network Repository Function，NRF)网元、策略控制功能(policy control function，PCF)网元、统一数据管理(unified data management，UDM)网元、应用功能(application function，AF)网元、接入与移动性管理功能(access and mobility management function，AMF)网元、会话管理功能(session management function，SMF)网元、无线接入网(radioaccess network，RAN)以及用户面功能(user plane function，UPF)网元等。上述运营商网络中，除无线接入网部分之外的部分可以称为核心网络部分。
终端设备(terminal device)，也可以称为用户设备(user equipment，UE)，是一种具有无线收发功能的设备，可以部署在陆地上，包括室内或室外、手持或车载；也可以部署在水面上(如轮船等)；还可以部署在空中(例如飞机、气球和卫星上等)。所述终端设备可以是手机(mobile phone)、平板电脑(pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端、增强现实(augmented reality，AR)终端、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等。
上述终端设备可通过运营商网络提供的接口(例如N1等)与运营商网络建立连接，使用运营商网络提供的数据和/或语音等服务。终端设备还可通过运营商网络访问DN，使用DN上部署的运营商业务，和/或第三方提供的业务。其中，上述第三方可为运营商网络和终端设备之外的服务方，可为终端设备提供他数据和/或语音等服务。其中，上述第三方的具体表现形式，具体可根据实际应用场景确定，在此不做限制。
RAN是运营商网络的子网络，是运营商网络中业务节点与终端设备之间的实施系统。终端设备要接入运营商网络，首先是经过RAN，进而可通过RAN与运营商网络的业务节点连接。本申请中的RAN设备，是一种为终端设备提供无线通信功能的设备，RAN设备也称为接入网设备。本申请中的RAN设备包括但不限于：5G中的下一代基站(g nodeB，gNB)、演进型节点B(evolved node B，eNB)、无线网络控制器(radio network controller，RNC)、节点B(node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(例如，home evolved nodeB，或home node B，HNB)、基带单元(baseBand unit，BBU)、传输点(transmitting and receiving point，TRP)、发射点(transmitting point，TP)、移动交换中心等。
AMF网元，是由运营商网络提供的控制面网元，负责终端设备接入运营商网络的接入控制和移动性管理，例如包括移动状态管理，分配用户临时身份标识，认证和授权用户等功能。
SMF网元，主要负责移动网络中的会话管理，如会话建立、修改、释放。具体功能如 为用户分配IP地址、选择提供报文转发功能的UPF等。
UPF网元，负责终端设备中用户数据的转发和接收。可以从数据网络接收用户数据，通过接入网设备传输给终端设备；UPF网元还可以通过接入网设备从终端设备接收用户数据，转发到数据网络。UPF网元中为终端设备提供服务的传输资源和调度功能由SMF网元管理控制的。
UDM网元，用于生成认证信任状，用户标识处理(如存储和管理用户永久身份等)，接入授权控制和签约数据管理等。
NEF网元，主要用于支持能力和事件的开放。
AF网元，主要支持与第三代合作伙伴计划(3rd generation partnership project，3GPP)核心网交互来提供服务，例如影响数据路由决策，策略控制功能或者向网络侧提供第三方的一些服务。
PCF网元，主要支持提供统一的策略框架来控制网络行为，提供策略规则给控制层网络功能，同时负责获取与策略决策相关的用户签约信息。
NRF网元，可用于提供网元发现功能，基于其他网元的请求，提供网元类型对应的网元信息。NRF还提供网元管理服务，如网元注册、更新、去注册以及网元状态订阅和推送等。
DN，是位于运营商网络之外的网络，运营商网络可以接入多个DN，DN上可部署多种业务，可为终端设备提供数据和/或语音等服务。例如，DN是某智能工厂的私有网络，智能工厂安装在车间的传感器可为终端设备，DN中部署了传感器的控制服务器，控制服务器可为传感器提供服务。传感器可与控制服务器通信，获取控制服务器的指令，根据指令将采集的传感器数据传送给控制服务器等。又例如，DN是某公司的内部办公网络，该公司员工的手机或者电脑可为终端设备，员工的手机或者电脑可以访问公司内部办公网络上的信息、数据资源等。
图1A中Nnef、Nnrf、Npcf、Nudm、Naf、Namf、Nsmf、N1、N2、N3、N4，以及N6为接口序列号。这些接口序列号的含义可参见3GPP标准协议中定义的含义，在此不做限制。
如图1B所示，为基于点对点接口的5G网络架构示意图，其中的网元的功能的介绍可以参考图1A中对应的网元的功能的介绍，不再赘述。图1B与图1A的主要区别在于：图1B中的各个网元之间的接口是点对点的接口，而不是服务化的接口。需要说明的是，图1B中还包括其他网元，如NEF、NRF等，图1B中未示出。
在图1B所示的架构中，其中，UE与AMF网元之间的接口称为N1接口，AMF网元与RAN设备之间的接口称为N2接口，RAN设备与UPF网元之间的接口可以称为N3接口，SMF网元与UPF网元之间的接口称为N4接口，PCF网元与AF网元之间的接口称为N5接口，UPF网元与DN之间的接口称为N6接口，SMF网元与PCF网元之间的接口称为N7接口，AMF网元与UDM网元之间的接口称为N8接口，不同UPF网元之间的接口称为N9接口，UDM网元与SMF网元之间的接口称为N10接口，AMF网元与SMF网元之间的接口称为N11接口，不同AMF网元之间的接口称为N14接口，AMF网元与PCF网元之间的接口称为N15接口。
可以理解的是，上述网元或者功能既可以是硬件设备中的网络元件，也可以是在专用 硬件上运行软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能。可选的，上述网元或者功能可以由一个设备实现，也可以由多个设备共同实现，还可以是一个设备内的一个功能模块，本申请实施例对此不作具体限定。
进一步的，在图1A或图1B所示的架构中，还可以增加网络切片管理网元、网络切片子网管理网元、网络功能管理网元、计费网元。其中，网络切片管理网元比如可以是网络切片管理功能(Network slice management function，NSMF)网元，简称为NSMF。网络切片子网管理网元比如可以是网络切片子网管理功能(Network slice subnet management function，NSSMF)网元，简称为NSSMF。网络功能管理网元比如可以是网络功能管理功能(Network function management function，NFMF)网元，简称为NFMF。计费网元比如可以是计费功能(Charging Function，CHF)网元，简称为CHF。
本申请中的移动性管理网元、会话管理网元、策略控制网元、应用功能网元、接入网设备、网络开放功能网元、用户面网元分别可以是图1A或图1B中的AMF、SMF、PCF、AF、RAN、NEF、UPF，也可以是未来通信如第六代(6th generation，6G)网络中具有上述AMF、SMF、PCF、AF、RAN、NEF、UPF的功能的网元，本申请对此不限定。为方便说明，本申请以移动性管理网元、会话管理网元、策略控制网元、应用功能网元、接入网设备、网络开放功能网元、用户面网元分别为上述AMF、SMF、PCF、AF、RAN、NEF、UPF为例进行说明。并且，本申请中将终端设备简称为UE。
需要说明的是，上述核心网的部分网元可以统称为网络功能(Network function，NF)网元，简称为NF。比如NF包括AMF、UPF、SMF、PCF等。
为便于理解本发明，下面对本发明实施例中出现的一些术语进行统一说明，后续不再赘述。
一、5G计费系统技术
在5G核心网网络架构中，计费系统包括计费触发功能(Charging Trigger Function，CTF)网元(以下简称为CTF)和CHF。根据计费网络架构，CTF产生计费数据，将计费数据发给CHF。其中，CHF包括产生计费话单(charging data record，CDR)功能。计费系统还包括计费网关功能(Charging GateWay Function，CGF)网元(以下简称为CGF)，CHF将CDR转发给CGF。
当前5G计费系统支持基于协议数据单元(protocol data unit，PDU)会话的计费，计费数据由集成了CTF的SMF产生。由于SMF负责会话管理，其功能包括PDU会话的创建、维护、修改和删除，因而SMF收集UPF上的PDU会话数据连接的使用信息，从而得到产生计费数据的数据源。
在SMF将产生的计费数据发送给CHF的过程中，SMF和CHF之间还支持配额管理(Quota management)，配额是计费系统中对切片计费使用量的限额，一般会先给网络分配一部分配额，当配额达到以后，再向计费系统申请新的配额。并且，SMF在一个计费会话中维护计费数据，因此SMF在PDU会话建立阶段需要建立SMF和CHF之间的计费会话。
5G网络中，SMF支持在发送给CHF的计费数据中包括单网络切片选择辅助信息(single network slice selection assistance information，S-NSSAI)，因而可以支持基于网络切片的计费。在此情况下，CHF收到的计费数据包括了PDU会话所在的网络切片实例的S-NSSAI，因而，可以在产生的CDR中包括S-NSSAI，从而可以统计在一个网络切片中的 数据连接的使用情况。
二、网络切片
网络切片根据业界的定义，可以认为是为了满足某一个业务需求，而创建的由多个网络功能网元组成的通信网络。网络切片可以被多个业务共享，也可以被一个业务所独享，适用于在运营商的同一个基础设施上部署的多种通信服务。
网络切片是一种按需组网的方式，网络运营商在统一的基础设施上部署多个虚拟的网络切片或端到端网络，每个网络切片从无线接入网到承载网再到核心网在逻辑上隔离，适配各种类型的业务应用。在一个网络切片内，至少包括无线子切片、承载子切片和核心网子切片。
网络切片的部署模板定义了一个网络切片的结构和配置等。基于网络切片的部署模板部署的网络切片实例是一系列编排部署和配置的网络功能以及网络功能内包含的资源形成的完整逻辑网络，可以满足特定的网络需求。
网络功能虚拟化(Network Function Virtualization，NFV)是网络切片的先决条件。以核心网为例，NFV从传统网元设备中分解出软硬件的部分。硬件由通用服务器统一部署，软件部分由不同的NF(网络功能)承担，从而实现灵活组装业务的需求。
网络切片的创建，可以根据服务等级协议(service level agreement，SLA)为特定的通信服务类型选择它所需要的虚拟资源和物理资源，并且部署为支持该SLA所需要的网络功能。SLA包括用户数、服务质量(Quality of Service，QoS)、带宽等参数，不同的SLA定义了不同的通信服务类型。
网络切片实例的创建(从管理层面观察)是根据通信服务消费者的业务要求而触发的一个实例化的过程。通信服务消费者对网络切片的业务要求种类有多种，大致可以分为：延迟(Latency)、保证/非保证QoS(Guaranteed/non-guaranteed QoS)、峰值吞吐量(Peak throughput)、数据量(Data Volumes)、可靠性(Reliability)、单网络切片实例的上下行流的吞吐量(Upstream/Downstream Throughput for Single Network Slice Instance)、网络切片实例的PDU会话的平均数(Mean number of PDU sessions of network Slice Instance)、网络切片实例的注册用户(Registered Subscribers of network Slice Instance)、移动性(Mobility)、覆盖范围(Coverage area)。
如上这些SLA要求，一部分是通过网络切片实例的修改过程达成的，例如网络切片容量的问题，还有一部分是通过网络业务配置的过程达成的，例如某一个业务的覆盖范围，某一个业务的UE密度支持，最大峰值速率等。
对于网络切片的计费来说，计费系统希望通过收集与网络切片SLA相关的信息，作为计费系统生成计费数据，CDR以至于生成账单(bill)的依据。不同类型通信服务对网络切片的SLA要求有差异，因而对网络切片计费的要求存在差异，而且需要在计费过程中明确相关的计费要求和差异。
三、网络切片的管理操作与网络切片计费之间的关系
在网络切片的计费中，对网络切片的生命周期管理存在依赖关系，例如网络切片实例的创建、修改或删除，切片的激活或去激活。一般情况下，网络切片修改前先对网络切片实例进行去激活操作；网络切片修改后需要对网络功能的业务配置进行修改，在业务配置 修改完成后，启动激活操作。
需要说明的是，网络切片的生命周期管理操作，一般是处于部署阶段。网络切片管理实体负责的网络切片创建/修改/删除操作可以是一个网络切片实例的实例化操作(例如，创建虚拟资源、创建虚拟机、加载软件镜像，加载初始配置等)。
在网络切片实例的运行阶段，网络切片实例作为一个网络实例运行，其运维数据上报的管理实体为运维操作维护(Operation,Administration and Management，OAM)实体。网络切片管理实体作为运维系统的一部分，可以作为获得运维数据的实体之一。
另外一种情况是，当网络切片实例的实例化过程已经完成后，例如，一个共享的切片已经部署后，在这个共享的网络切片实例中添加新的业务(例如，用一个S-NSSAI标识网络切片实例业务)，这个过程可能需要对网络切片实例做适当的扩容操作，还需要网络功能做业务配置，例如配置对应的S-NSSAI操作。
因而，可以认为网络切片实例操作，可以是网络切片的实例化过程中的操作；也可以是网络切片实例创建后，为了添加某一个业务对网络切片的修改、网络业务参数的修改、网络切片的激活和去激活操作。
四、本申请涉及的一些管理功能
目前标准中定义了5G网络和网络切片管理编排系列标准，采用了5G管理服务化架构，定义了管理服务。5G网管的管理服务包括：指配管理服务(Provisioning management service)，性能管理服务(Performance management service，PM)和故障管理服务(Fault management service，FM)。
管理服务所提供管理的能力，可以分为NF管理能力(例如5G核心网NF管理)、网络切片子网管理能力和网络切片管理能力。从管理功能上看，NF管理服务(或者NF管理服务提供的管理能力)由NFMF提供。网络切片子网管理服务(或者网络切片子网管理能力)由NSSMF提供；网络切片管理服务(或者网络切片管理能力)由NFMF提供。此外，还包括通信服务管理功能(Communication service management function，CSMF)。下面对CSMF、NSMF、NSSMF和NFMF进行介绍说明。
1、CSMF：完成用户业务通信服务的需求订购和处理，将通信服务需求转换为对NSMF的网络切片需求，然后根据网络切片需求向NSMF发送网络切片部署请求。CSMF管理对象为通信服务，每个通信服务由1个或者多个网络切片功能完成。
2、NSMF：接收CSMF下发的网络切片部署请求，向NSSMF下发网络子网切片部署请求。NSMF管理对象为网络切片，每个网络切片可以包括1个或者多个网络子网切片(也称为子网络切片、或网络子切片、或子切片、或网络切片子网等)。
3、NSSMF：接收从NSMF下发的网络子网切片部署请求，并向NFMF下发网络功能部署请求。NSSMF管理对象为网络子网切片，每个网络子网切片可以是一个基础的子切片，也可以是多个基础子切片组合成的子切片。每个子切片可以包含1个或者多个网络功能。
4、NFMF：用于管理NFs，如AMF、SMF、UPF、PCF等。
五、网络切片管理和网络管理之间的配合关系
网络切片管理的功能包括网络切片的生命周期管理，网络切片的PM和FM等。网络管理的范围包括网络配置，PM和FM。由于网络切片管理的PM/FM和网管的PM/FM的 数据来源是相同，所要达成的管理目的是类似，因而可以认为网络切片管理的PM/FM和网络管理的PM/FM没有明显差异。
由于NFMF对网络切片生命周期有管理的能力，因而网络切片管理功能和网络切片子网管理功能主要工作在网络切片部署阶段。当网络切片实例创建完成后，运行状态的网管(OAM等能力)主要是网络管理的范围。
需要说明的是，网络切片实例在被多个租户共享的情况下，网络切片实例中针对某一个租户的管理数据是需要单独统计的。因而在网络切片的计费过程中，针对某一个租户的管理数据，需要基于租户标识(租户ID)和对应的租户的计费数据单独生成计费数据，并建立独立的计费会话。进一步地，网络切片子网管理功能和网络功能管理功能部署在同一个位置，分别负责切片子网管理和NF管理，其关系参考网络切片管理和网管之间的配合关系。其中，在NF层次区分不同业务的标识是S-NSSAI，不同的网络切片实例的相关管理数据通过S-NSSAI来区分。
为解决背景技术提到的问题，基于图1A或图1B所示的网络架构，本申请提供一种网络切片的计费方法，如图2所示，该方法包括以下步骤：
步骤201，NSMF接收第一请求，第一请求包括网络切片的计费要求。
比如，NSMF从CSMF或其他网元接收所述第一请求。
这里的计费要求包括以下至少一项：计费对象、计费方式和计费功能(CHF)选择的规则。其中，计费对象包括以下至少一个：用户连接数、用户数、吞吐量、会话数、会话时长、虚拟资源。计费方式包括离线、或在线。计费功能选择的规则用于查找计费功能网元的地址。
步骤202，NSMF向NSSMF发送第二请求，第二请求包括上述计费要求。相应地，NSSMF可以接收到该第二请求。
作为一种实现方式，上述第一请求为网络切片实例创建请求，第二请求为网络切片子网实例创建请求。作为又一种实现方式，上述第一请求为网络切片实例修改请求，第二请求为网络切片子网实例修改请求。
步骤203，NSMF向CHF发送第三请求。相应地，CHF可以接收到该第三请求。
该第三请求用于请求开启网络切片实例计费功能。该第三请求比如可以是网络切片计费会话请求、或事件计费请求。
该步骤可选。
步骤204，NSSMF根据计费要求，确定NF对应的第一子计费要求，并向NF发送第一子计费要求，第一子计费要求用于NF收集网络切片的第一计费数据，第一计费数据用于CHF进行网络切片计费。相应地，NF可以接收到第一子计费要求。
比如发给AMF的第一子计费要求中携带计费对象(如用户连接数、用户数、吞吐量)、计费方式(如离线或在线)、计费功能选择的规则。再比如发给SMF的第一子计费要求中携带计费对象(如会话数、会话时长)、计费方式(如离线或在线)、计费功能选择的规则。
步骤205，NSMF、NSSMF、NFMF及各个NF向CHF上报收集到的计费数据。
即各个NF根据发给自己的第一子计费要求，对相应的计费对象，按照相应的计费方式进行计费数据的收集，然后上报至CHF。
NSSMF根据NSMF发送的计费要求，得到第二子计费要求，对相应的计费对象，按 照相应的计费方式进行计费数据的收集，然后上报至CHF。
NFMF根据NSSMF发送的子计费要求(可以称为第三子计费要求)，对相应的计费对象，按照相应的计费方式进行计费数据的收集，然后上报至CHF。
NSMF根据计费要求，对相应的计费对象，按照相应的计费方式进行计费数据的收集，然后上报至CHF。
作为示例，下面对NSMF、NSSMF、NFMF及各个NF收集并上报的计费数据进行说明。
一、NF(以SMF、AMF、NEF、NWDAF为例)收集并上报的计费数据
1、SMF可以提供网络切片实例中的PDU会话相关的计费数据，如会话时长、会话数。相关的计费数据是基于PDU会话统计的。
2、AMF可以提供某一个网络切片实例中的某一个UE的在AMF相关切换的计费数据。当UE的移动性(即AMF切换)作为计费数据时，可以按照事件计费触发条件，向CHF提供AMF统计的某一个UE的AMF切换次数。以及，AMF还可以提供用户连接数、用户数、吞吐量等计费数据。
3、NEF可以提供在一个网络切片实例中的以某一个应用(application service)调用网络能力应用程序编程接口(Application Programming Interface，API)的次数。可以按照事件计费触发条件，向CHF提供某个应用调用网络能力API的次数作为计费数据。
4、NWDAF可以提供网络切片实例中的网络性能的实时性能统计数据，还可以基于数据分析能力提供高级性能统计，例如关于某一个业务的业务体验的统计。NWDAF基于计费要求中提供的性能统计内容和统计频度的要求，可以采用事件计费方式，向CHF提供性能统计数据。
二、NFMF收集并上报的计费数据
NFMF提供NF相关的性能度量，典型和网络切片相关的性能度量包括：
1)、和UPF相关的性能度量，包括：N3接口上的报文数量、N3接口上的吞吐量、N6接口上的报文数量、N6接口上的吞吐量；
2)、AMF提供的性能度量，包括：一个网络切片实例上的注册用户数、一个网络切片实例上成功注册用户的数量、一个网络切片实例上成功的service request(业务请求)数量、一个网络切片实例上非3GPP网络注册的用户数、一个网络切片实例上跨AMF切换的数量；
3)、SMF提供的性能度量，包括：一个网络切片实例上的PDU会话数量、一个网络切片实例上的PDU会话修改数量、一个网络切片实例上的PDU会话释放数量；
4)、各个网络功能(NF)可以提供虚拟资源的使用量。
三、NSMF收集并上报的计费数据
作为一种实现方法，NSMF可以根据网络切片计费的要求，向CHF提供网络切片管理操作的计费数据。
四、NSSMF收集并上报的计费数据
作为一种实现方法，NSSMF可以根据网络切片计费的要求，向CHF提供网络切片管理操作的计费数据。
下面对NSMF、NSSMF、NFMF及各个NF向CHF上报收集到的计费数据的方法进行说明。
一、各个NF向CHF上报收集到的计费数据的方法包括但不限于：
作为一种实现方法，NF如AMF、SMF向CHF上报计费数据的路径可以为：NF->NWDAF->NFMF->NSSMF->NSMF->CHF。即NF通过NWDAF、NFMF、NSSMF、NSMF上报计费数据至CHF。
作为又一种实现方法，NF如AMF、SMF向CHF上报计费数据的路径可以为：NF->NFMF->NSSMF->NSMF->CHF。即NF通过NFMF、NSSMF、NSMF上报计费数据至CHF。
作为又一种实现方法，NF如AMF、SMF向CHF上报计费数据的路径可以为：NF->NFMF->NSSMF->CHF。即NF通过NFMF、NSSMF上报计费数据至CHF。
作为又一种实现方法，NF如AMF、SMF向CHF上报计费数据的路径可以为：NF->NFMF->CHF。即NF通过NFMF上报计费数据至CHF。
作为又一种实现方法，NF如AMF、SMF向CHF上报计费数据的路径可以为：NF->NWDAF->CHF。即NF通过NWDAF上报计费数据至CHF。
作为又一种实现方法，NF如AMF、SMF向CHF上报计费数据的路径可以为：NF->CHF。即NF直接上报计费数据至CHF。
二、NFMF向CHF上报收集到的计费数据的方法包括但不限于：
作为一种实现方法，NFMF向CHF上报计费数据的路径可以为：NFMF->NSSMF->NSMF->CHF。即NFMF通过NSSMF、NSMF上报计费数据至CHF。
作为又一种实现方法，NFMF向CHF上报计费数据的路径可以为：NFMF->NSMF->CHF。即NFMF通过NSMF上报计费数据至CHF。
作为又一种实现方法，NFMF向CHF上报计费数据的路径可以为：NFMF->NSSMF->CHF。即NFMF通过NSSMF上报计费数据至CHF。
作为又一种实现方法，NFMF向CHF上报计费数据的路径可以为：NFMF->CHF。即NFMF直接上报计费数据至CHF。
三、NSMF向CHF上报收集到的计费数据的方法包括但不限于：
作为一种实现方法，NSMF向CHF上报计费数据的路径可以为：NSMF->CHF。即NSMF直接上报计费数据至CHF。
四、NSSMF向CHF上报收集到的计费数据的方法包括但不限于：
作为一种实现方法，NSSMF向CHF上报计费数据的路径可以为：NSSMF->CHF。即NSSMF直接上报计费数据至CHF。
作为又一种实现方法，NSSMF向CHF上报计费数据的路径可以为：NSSMF->NSMF->CHF。即NSSMF通过NSMF上报计费数据至CHF。
需要说明的是，在NSSMF或NSMF向CHF提供上述计费数据时，还可以根据网络切片计费要求对计费数据进行整理，然后根据对应的发送频度要求，向CHF提供计费数据。
步骤206，CHF根据接收到的计费数据，对网络切片计费。
通过上述方案，可以实现对网络切片进行计费。并且，还给出了各个网元上报计费数据的不同实现方法，有助于提升网络切片计费的准确性。
下面结合具体示例，对图2所示的方法进行具体说明。
如图3所示，为本申请提供的又一种网络切片的计费方法流程示意图。该方法是在网络切片的部署过程中，对网络切片进行计费。
该方法包括以下步骤：
步骤301，通信服务用户向CSMF发送通信服务创建请求。相应地，CSMF可以接收到该通信服务创建请求。
步骤302，CSMF向NSMF发送网络切片实例创建请求。相应地，NSMF可以接收到该网络切片实例创建请求。
该网络切片实例创建请求携带该网络切片实例所需要的计费要求，该计费要求包含的内容可以参考图2实施例的描述，这里不再赘述。
可选的，该网络切片实例创建请求还可以携带网络切片创建的业务要求。
步骤303，NSMF向NSSMF发送网络切片子网实例创建请求。相应地，NSSMF可以接收到该网络切片子网实例创建请求。
该网络切片子网实例创建请求携带上述计费要求。
步骤304，NSSMF创建网络切片子网实例。
在该过程中，NSSMF一方面实例化网络切片，配置对应的网络配置参数；另一方面，将上述计费要求分解为多个子计费要求，并发送至各个NF。
步骤305，NSMF向CHF发送网络切片计费会话请求。相应地，CHF可以接收到该网络切片计费会话请求。
如果网络切片实例对应一个独占业务，或者是开启了一个业务，则NSMF可以向CHF发送网络切片计费会话请求(该请求是一个初始请求)，CHF收到网络切片计费会话请求后，开启网络切片实例计费CHF CDR。
作为该步骤305的一种可替代实现方案，如果NSMF向CHF创建的网络切片计费是一个事件计费，则NSMF也可以向CHF发送事件计费请求(该请求是一个初始请求)，CHF收到事件计费请求后，开启网络切片实例计费CHF CDR。
作为一种实现方法，该步骤中，NSMF可以根据计费要求中的计费功能选择的规则，获取到CHF的地址。
步骤306，网络切片子网实例创建后的运行态。
网络切片子网实例创建后，处于运行态。
步骤307，NSMF、NSSMF、NFMF及各个NF向CHF上报收集到的计费数据。
NSMF、NSSMF、NFMF及NF收集计费数据并向CHF上报收集到的计费数据的方法，可以参考图2实施例的相关描述，这里不再赘述。
如图4所示，为本申请提供的又一种网络切片的计费方法流程示意图。该方法是在网络切片实例运行阶段的网络切片实例添加过程中，对网络切片进行计费。
该方法包括以下步骤：
步骤401，通信服务用户向CSMF发送通信服务创建请求。相应地，CSMF可以接收到该通信服务创建请求。
步骤402，CSMF向NSMF发送网络切片实例修改请求。相应地，NSMF可以接收到该网络切片实例创修改请求。
该网络切片实例修改请求携带该网络切片实例所需要的计费要求，该计费要求包含的内容可以参考图2实施例的描述，这里不再赘述。
步骤403，NSMF向NSSMF发送修改请求。相应地，NSSMF可以接收到该修改请求。
该修改请求携带上述计费要求。该修改请求用于请求修改网络切片子网实例和NF配置参数。
步骤404，NSSMF修改网络切片子网实例和NF配置参数。
需要说明的是，网络切片实例处于运行状态，对网络切片子网实例的修改，可以通过修改网络配置完成，也可以通过网络切片子网实例的扩容完成。
这里的修改NF配置参数包括但不限于：添加容量、添加新配置的S-NSSAI参数。
在该过程中，NSSMF将上述计费要求分解为多个子计费要求，并发送至各个NF。
步骤405，NSMF向CHF发送网络切片计费会话请求。相应地，CHF可以接收到该网络切片计费会话请求。
如果网络切片实例是一个独占业务，或者是开启了一个业务，则NSMF可以向CHF发送网络切片计费会话请求(该请求是一个初始请求)，CHF收到网络切片计费会话请求后，开启网络切片实例计费CHF CDR。
作为该步骤405的一种可替代实现方案，如果NSMF向CHF创建的网络切片计费是一个事件计费，则NSMF也可以向CHF发送事件计费请求(该请求是一个初始请求)，CHF收到事件计费请求后，开启网络切片实例计费CHF CDR。
作为一种实现方法，该步骤中，NSMF可以根据计费要求中的计费功能选择的规则，获取到CHF的地址。
步骤406，网络切片子网实例修改后的运行态。
步骤407，NSMF、NSSMF、NFMF及各个NF向CHF上报收集到的计费数据。
NSMF、NSSMF、NFMF及NF收集计费数据并向CHF上报收集到的计费数据的方法，可以参考图2实施例的相关描述，这里不再赘述。
上述主要从各个网元之间交互的角度对本申请提供的方案进行了介绍。可以理解的是，上述实现各网元为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本发明能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。
本申请实施例还提供用于实现以上任一种方法的装置，例如，提供一种装置包括用以实现以上任一种方法中网络切片管理网元所执行的各个步骤的单元(或手段)。再如，还提供另一种装置，包括用以实现以上任一种方法中网络切片子网管理网元所执行的各个步骤的单元(或手段)。再如，还提供另一种装置，包括用以实现以上任一种方法中网络功能网元所执行的各个步骤的单元(或手段)。
例如，请参考图5，其为本申请实施例提供的一种通信装置的示意图。该装置用于网络切片管理网元，如图5所示，该装置500包括接收单元501和发送单元502。可选的，该装置500还包括计费数据收集单元503。
所述接收单元501，用于接收第一请求，所述第一请求包括网络切片的计费要求；所述发送单元502，用于向网络切片子网管理网元发送第二请求，所述第二请求包括所述计费要求；所述接收单元501，还用于接收所述网络切片的第一计费数据，所述第一计费数据是根据所述计费要求收集的；所述发送单元502，还用于向计费网元发送所述第一计费数据，所述第一计费数据用于所述计费网元进行网络切片计费。
在一种可能的实现方法中，所述第一计费数据来自以下一个或多个网元：网络切片子网管理网元、网络功能网元、网络功能管理网元。
在一种可能的实现方法中，计费数据收集单元503，用于根据所述计费要求，收集第二计费数据；所述发送单元502，还用于向所述计费网元发送所述第二计费数据，所述第二计费数据用于所述计费网元进行网络切片计费。
在一种可能的实现方法中，所述发送单元502，还用于向所述计费网元发送第三请求，所述第三请求用于请求开启网络切片实例计费功能。
在一种可能的实现方法中，所述第三请求为网络切片计费会话请求、或事件计费请求。
在一种可能的实现方法中，所述计费要求包括以下至少一项：计费对象、计费方式和计费功能选择的规则。
在一种可能的实现方法中，所述第一请求为网络切片实例创建请求，所述第二请求为网络切片子网实例创建请求；或者，所述第一请求为网络切片实例修改请求，所述第二请求为网络切片子网实例修改请求。
例如，请参考图6，其为本申请实施例提供的又一种通信装置的示意图。该装置用于网络切片子网管理网元，如图6所示，该装置600包括接收单元601、计费要求确定单元602和发送单元603。可选的，该装置600还包括计费数据收集单元604。
接收单元601，用于从网络切片管理网元接收第二请求，所述第二请求包括计费要求；计费要求确定单元602，用于根据所述计费要求，确定网络功能网元对应的第一子计费要求；发送单元603，用于向所述网络功能网元发送所述第一子计费要求，所述第一子计费要求用于所述网络功能网元收集网络切片的第一计费数据，所述第一计费数据用于计费网元进行网络切片计费。
在一种可能的实现方法中，所述接收单元601，还用于接收来自所述网络功能网元的所述第一计费数据；所述发送单元603，还用于向网络切片管理网元发送所述第一计费数据，所述第一计费数据由所述网络切片管理网元发送至所述计费网元；或者，用于向所述计费网元发送所述第一计费数据。
在一种可能的实现方法中，所述计费要求确定单元602，还用于根据所述计费要求，确定所述网络切片子网管理网元对应的第二子计费要求；计费数据收集单元604，用于根据所述第二子计费要求，收集网络切片的第二计费数据，所述第二计费数据用于所述计费网元进行网络切片计费。
在一种可能的实现方法中，所述发送单元603，还用于向网络切片管理网元发送所述第二计费数据，所述第二计费数据由所述网络切片管理网元发送至所述计费网元；或者，用于向所述计费网元发送所述第二计费数据。
在一种可能的实现方法中，所述第二请求为网络切片子网实例创建请求、或网络切片子网实例修改请求。
例如，请参考图7，其为本申请实施例提供的又一种通信装置的示意图。该装置用于网络功能网元，如图7所示，该装置700包括接收单元701、发送单元702和计费数据收集单元703。
接收单元701，用于接收网络切片的计费要求；计费数据收集单元703，用于根据所述计费要求，收集网络切片的计费数据；发送单元702，用于发送所述计费数据，所述计费数据用于计费网元进行网络切片计费。
在一种可能的实现方法中，所述发送单元702，具体用于：向网络切片子网管理网元发送所述计费数据，所述计费数据由所述网络切片子网管理网元发送至所述计费网元；或者，向网络切片管理网元发送所述计费数据，所述计费数据由所述网络切片管理网元发送至所述计费网元；或者，向所述计费网元发送所述计费数据。
应理解以上装置中单元的划分仅仅是一种逻辑功能的划分，实际实现时可以全部或部分集成到一个物理实体上，也可以物理上分开。且装置中的单元可以全部以软件通过处理元件调用的形式实现；也可以全部以硬件的形式实现；还可以部分单元以软件通过处理元件调用的形式实现，部分单元以硬件的形式实现。例如，各个单元可以为单独设立的处理元件，也可以集成在装置的某一个芯片中实现，此外，也可以以程序的形式存储于存储器中，由装置的某一个处理元件调用并执行该单元的功能。此外这些单元全部或部分可以集成在一起，也可以独立实现。这里所述的处理元件又可以成为处理器，可以是一种具有信号的处理能力的集成电路。在实现过程中，上述方法的各步骤或以上各个单元可以通过处理器元件中的硬件的集成逻辑电路实现或者以软件通过处理元件调用的形式实现。
在一个例子中，以上任一装置中的单元可以是被配置成实施以上方法的一个或多个集成电路，例如：一个或多个特定集成电路(Application Specific Integrated Circuit，ASIC)，或，一个或多个微处理器(digital singnal processor，DSP)，或，一个或者多个现场可编程门阵列(Field Programmable Gate Array，FPGA)，或这些集成电路形式中至少两种的组合。再如，当装置中的单元可以通过处理元件调度程序的形式实现时，该处理元件可以是通用处理器，例如中央处理器(Central Processing Unit，CPU)或其它可以调用程序的处理器。再如，这些单元可以集成在一起，以片上系统(system-on-a-chip，SOC)的形式实现。
以上用于接收的单元(例如接收单元)是一种该装置的接口电路，用于从其它装置接收信号。例如，当该装置以芯片的方式实现时，该接收单元是该芯片用于从其它芯片或装置接收信号的接口电路。以上用于发送的单元(例如发送单元)是一种该装置的接口电路，用于向其它装置发送信号。例如，当该装置以芯片的方式实现时，该发送单元是该芯片用于向其它芯片或装置发送信号的接口电路。
请参考图8，其为本申请实施例提供的一种通信装置的结构示意图，该通信装置可以是网络切片管理网元、或网络切片子网管理网元、或网络功能网元，用于实现以上实施例中网络切片管理网元、或网络切片子网管理网元、或网络功能网元的操作。如图8所示，该通信装置包括：处理器810，存储器820，和接口830，处理器810、存储器820和接口830信号连接。
以上实施例中通信装置执行的方法可以通过处理器810调用存储器820中存储的程序来实现。即，通信装置包括存储器和处理器，存储器用于存储程序，该程序被处理器调用， 以执行以上方法实施例中的通信装置执行的方法。这里的处理器可以是一种具有信号的处理能力的集成电路，例如CPU。用于会话管理网元的装置可以通过配置成实施以上方法的一个或多个集成电路来实现。例如：一个或多个ASIC，或，一个或多个微处理器DSP，或，一个或者多个FPGA等，或这些集成电路形式中至少两种的组合。或者，可以结合以上实现方式。
本领域普通技术人员可以理解：本申请中涉及的第一、第二等各种数字编号仅为描述方便进行的区分，并不用来限制本申请实施例的范围，也表示先后顺序。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包括一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘(solid state disk，SSD))等。
本申请实施例中所描述的各种说明性的逻辑单元和电路可以通过通用处理器，数字信号处理器，专用集成电路(ASIC)，现场可编程门阵列(FPGA)或其它可编程逻辑装置，离散门或晶体管逻辑，离散硬件部件，或上述任何组合的设计来实现或操作所描述的功能。通用处理器可以为微处理器，可选地，该通用处理器也可以为任何传统的处理器、控制器、微控制器或状态机。处理器也可以通过计算装置的组合来实现，例如数字信号处理器和微处理器，多个微处理器，一个或多个微处理器联合一个数字信号处理器核，或任何其它类似的配置来实现。
在一个或多个示例性的设计中，本申请所描述的上述功能可以在硬件、软件、固件或这三者的任意组合来实现。如果在软件中实现，这些功能可以存储与电脑可读的媒介上，或以一个或多个指令或代码形式传输于电脑可读的媒介上。电脑可读媒介包括电脑存储媒介和便于使得让电脑程序从一个地方转移到其它地方的通信媒介。存储媒介可以是任何通用或特殊电脑可以接入访问的可用媒体。例如，这样的电脑可读媒体可以包括但不限于RAM、ROM、EEPROM、CD-ROM或其它光盘存储、磁盘存储或其它磁性存储装置，或其它任何可以用于承载或存储以指令或数据结构和其它可被通用或特殊电脑、或通用或特殊处理器读取形式的程序代码的媒介。此外，任何连接都可以被适当地定义为电脑可读媒介，例如，如果软件是从一个网站站点、服务器或其它远程资源通过一个同轴电缆、光纤电脑、双绞线、数字用户线(DSL)或以例如红外、无线和微波等无线方式传输的也被包含在所定义的电脑可读媒介中。所述的碟片(disk)和磁盘(disc)包括压缩磁盘、镭射盘、光盘、数字通用光盘(英文：Digital Versatile Disc，简称：DVD)、软盘和蓝光光盘，磁盘通常以磁性复制数据，而碟片通常以激光进行光学复制数据。上述的组合也可以包含在电脑可读媒介中。
本领域技术人员应该可以意识到，在上述一个或多个示例中，本申请所描述的功能可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时，可以将这些功能存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。
尽管结合具体特征及其实施例对本申请进行了描述，显而易见的，在不脱离本申请的精神和范围的情况下，可对其进行各种修改和组合。相应地，本说明书和附图仅仅是所附权利要求所界定的本申请的示例性说明，且视为已覆盖本申请范围内的任意和所有修改、变化、组合或等同物。显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包括这些改动和变型在内。

Claims (32)

  1. 一种网络切片的计费方法，其特征在于，包括：
    网络切片管理网元接收第一请求，所述第一请求包括网络切片的计费要求；
    所述网络切片管理网元向网络切片子网管理网元发送第二请求，所述第二请求包括所述计费要求；
    所述网络切片管理网元接收所述网络切片的第一计费数据，所述第一计费数据是根据所述计费要求收集的；
    所述网络切片管理网元向计费网元发送所述第一计费数据，所述第一计费数据用于所述计费网元进行网络切片计费。
  2. 如权利要求1所述的方法，其特征在于，所述第一计费数据来自以下一个或多个网元：
    网络切片子网管理网元、网络功能网元、网络功能管理网元。
  3. 如权利要求1或2所述的方法，其特征在于，还包括：
    所述网络切片管理网元根据所述计费要求，收集第二计费数据；
    所述网络切片管理网元向所述计费网元发送所述第二计费数据，所述第二计费数据用于所述计费网元进行网络切片计费。
  4. 如权利要求1-3任一所述的方法，其特征在于，还包括：
    所述网络切片管理网元向所述计费网元发送第三请求，所述第三请求用于请求开启网络切片实例计费功能。
  5. 如权利要求4所述的方法，其特征在于，所述第三请求为网络切片计费会话请求、或事件计费请求。
  6. 如权利要求1-5任一所述的方法，其特征在于，所述计费要求包括以下至少一项：
    计费对象、计费方式和计费功能选择的规则。
  7. 如权利要求1-6任一所述的方法，其特征在于，所述第一请求为网络切片实例创建请求，所述第二请求为网络切片子网实例创建请求；或者，
    所述第一请求为网络切片实例修改请求，所述第二请求为网络切片子网实例修改请求。
  8. 一种网络切片的计费方法，其特征在于，包括：
    网络切片子网管理网元从网络切片管理网元接收第二请求，所述第二请求包括计费要求；
    所述网络切片子网管理网元根据所述计费要求，确定网络功能网元对应的第一子计费要求；
    所述网络切片子网管理网元向所述网络功能网元发送所述第一子计费要求，所述第一子计费要求用于所述网络功能网元收集网络切片的第一计费数据，所述第一计费数据用于计费网元进行网络切片计费。
  9. 如权利要求8所述的方法，其特征在于，还包括：
    所述网络切片子网管理网元接收来自所述网络功能网元的所述第一计费数据；
    所述网络切片子网管理网元向网络切片管理网元发送所述第一计费数据，所述第一计费数据由所述网络切片管理网元发送至所述计费网元；或者，所述网络切片子网管理网元向所述计费网元发送所述第一计费数据。
  10. 如权利要求8所述的方法，其特征在于，还包括：
    所述网络切片子网管理网元根据所述计费要求，确定所述网络切片子网管理网元对应的第二子计费要求；
    所述网络切片子网管理网元根据所述第二子计费要求，收集网络切片的第二计费数据，所述第二计费数据用于所述计费网元进行网络切片计费。
  11. 如权利要求10所述的方法，其特征在于，还包括：
    所述网络切片子网管理网元向网络切片管理网元发送所述第二计费数据，所述第二计费数据由所述网络切片管理网元发送至所述计费网元；或者，
    所述网络切片子网管理网元向所述计费网元发送所述第二计费数据。
  12. 如权利要求8-11任一所述的方法，其特征在于，所述第二请求为网络切片子网实例创建请求、或网络切片子网实例修改请求。
  13. 一种网络切片的计费方法，其特征在于，包括：
    网络功能网元接收网络切片的计费要求；
    所述网络功能网元根据所述计费要求，收集网络切片的计费数据；
    所述网络功能网元发送所述计费数据，所述计费数据用于计费网元进行网络切片计费。
  14. 如权利要求13所述的方法，其特征在于，所述网络功能网元发送所述计费数据，包括：
    所述网络功能网元向网络切片子网管理网元发送所述计费数据，所述计费数据由所述网络切片子网管理网元发送至所述计费网元；或者，
    所述网络功能网元向网络切片管理网元发送所述计费数据，所述计费数据由所述网络切片管理网元发送至所述计费网元；或者，
    所述网络功能网元向所述计费网元发送所述计费数据。
  15. 一种通信装置，其特征在于，包括接收单元和发送单元；
    所述接收单元，用于接收第一请求，所述第一请求包括网络切片的计费要求；
    所述发送单元，用于向网络切片子网管理网元发送第二请求，所述第二请求包括所述计费要求；
    所述接收单元，还用于接收所述网络切片的第一计费数据，所述第一计费数据是根据所述计费要求收集的；
    所述发送单元，还用于向计费网元发送所述第一计费数据，所述第一计费数据用于所述计费网元进行网络切片计费。
  16. 如权利要求15所述的装置，其特征在于，所述第一计费数据来自以下一个或多个网元：
    网络切片子网管理网元、网络功能网元、网络功能管理网元。
  17. 如权利要求15或16所述的装置，其特征在于，所述装置还包括计费数据收集单元，用于根据所述计费要求，收集第二计费数据；
    所述发送单元，还用于向所述计费网元发送所述第二计费数据，所述第二计费数据用于所述计费网元进行网络切片计费。
  18. 如权利要求15-17任一所述的装置，其特征在于，所述发送单元，还用于向所述计费网元发送第三请求，所述第三请求用于请求开启网络切片实例计费功能。
  19. 如权利要求18所述的装置，其特征在于，所述第三请求为网络切片计费会话请 求、或事件计费请求。
  20. 如权利要求15-19任一所述的装置，其特征在于，所述计费要求包括以下至少一项：
    计费对象、计费方式和计费功能选择的规则。
  21. 如权利要求15-20任一所述的装置，其特征在于，所述第一请求为网络切片实例创建请求，所述第二请求为网络切片子网实例创建请求；或者，
    所述第一请求为网络切片实例修改请求，所述第二请求为网络切片子网实例修改请求。
  22. 一种通信装置，其特征在于，包括：
    接收单元，用于从网络切片管理网元接收第二请求，所述第二请求包括计费要求；
    计费要求确定单元，用于根据所述计费要求，确定网络功能网元对应的第一子计费要求；
    发送单元，用于向所述网络功能网元发送所述第一子计费要求，所述第一子计费要求用于所述网络功能网元收集网络切片的第一计费数据，所述第一计费数据用于计费网元进行网络切片计费。
  23. 如权利要求22所述的装置，其特征在于，
    所述接收单元，还用于接收来自所述网络功能网元的所述第一计费数据；
    所述发送单元，还用于向网络切片管理网元发送所述第一计费数据，所述第一计费数据由所述网络切片管理网元发送至所述计费网元；或者，用于向所述计费网元发送所述第一计费数据。
  24. 如权利要求22所述的装置，其特征在于，所述计费要求确定单元，还用于根据所述计费要求，确定所述网络切片子网管理网元对应的第二子计费要求；
    所述装置还包括计费数据收集单元，用于根据所述第二子计费要求，收集网络切片的第二计费数据，所述第二计费数据用于所述计费网元进行网络切片计费。
  25. 如权利要求24所述的装置，其特征在于，所述发送单元，还用于向网络切片管理网元发送所述第二计费数据，所述第二计费数据由所述网络切片管理网元发送至所述计费网元；或者，用于向所述计费网元发送所述第二计费数据。
  26. 如权利要求22-25任一所述的装置，其特征在于，所述第二请求为网络切片子网实例创建请求、或网络切片子网实例修改请求。
  27. 一种通信装置，其特征在于，包括：
    接收单元，用于接收网络切片的计费要求；
    计费数据收集单元，用于根据所述计费要求，收集网络切片的计费数据；
    发送单元，用于发送所述计费数据，所述计费数据用于计费网元进行网络切片计费。
  28. 如权利要求27所述的装置，其特征在于，所述发送单元，具体用于：
    向网络切片子网管理网元发送所述计费数据，所述计费数据由所述网络切片子网管理网元发送至所述计费网元；或者，
    向网络切片管理网元发送所述计费数据，所述计费数据由所述网络切片管理网元发送至所述计费网元；或者，
    向所述计费网元发送所述计费数据。
  29. 一种通信装置，其特征在于，包括：处理器，用于调用存储器中的程序，以执行权利要求1-7任一所述的方法。
  30. 一种通信装置，其特征在于，包括：处理器，用于调用存储器中的程序，以执行权利要求8-12任一所述的方法。
  31. 一种通信装置，其特征在于，包括：处理器，用于调用存储器中的程序，以执行权利要求13或14所述的方法。
  32. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质存储程序，所述程序被处理器调用时，权利要求1-14任一所述的方法被执行。
PCT/CN2020/086880 2019-09-29 2020-04-24 一种网络切片的计费方法及装置 WO2021057020A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP20868159.3A EP4024913A4 (en) 2019-09-29 2020-04-24 NETWORK SLOT BILLING METHOD AND DEVICE
US17/705,059 US20220217005A1 (en) 2019-09-29 2022-03-25 Network Slice Charging Method and Apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910936221.2 2019-09-29
CN201910936221.2A CN112584336B (zh) 2019-09-29 2019-09-29 一种网络切片的计费方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/705,059 Continuation US20220217005A1 (en) 2019-09-29 2022-03-25 Network Slice Charging Method and Apparatus

Publications (1)

Publication Number Publication Date
WO2021057020A1 true WO2021057020A1 (zh) 2021-04-01

Family

ID=75111143

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/086880 WO2021057020A1 (zh) 2019-09-29 2020-04-24 一种网络切片的计费方法及装置

Country Status (4)

Country Link
US (1) US20220217005A1 (zh)
EP (1) EP4024913A4 (zh)
CN (2) CN115767452A (zh)
WO (1) WO2021057020A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11864069B2 (en) * 2020-11-03 2024-01-02 Cisco Technology, Inc. Network slice based billing

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180316564A1 (en) * 2017-04-28 2018-11-01 Huawei Technologies Co., Ltd. Service provision for offering network slices to a customer
CN109873730A (zh) * 2017-12-04 2019-06-11 华为技术有限公司 一种网络切片测试管理方法及相关产品
CN110213800A (zh) * 2019-05-17 2019-09-06 中国联合网络通信集团有限公司 网络切片业务的处理方法及装置
CN110225474A (zh) * 2018-03-02 2019-09-10 华为技术有限公司 一种多连接下的数据量上报方法
WO2019182493A1 (en) * 2018-03-23 2019-09-26 Telefonaktiebolaget Lm Ericsson (Publ) Network slicing awareness in ip multimedia subsystem

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10271186B2 (en) * 2017-01-27 2019-04-23 Huawei Technologies Co., Ltd. Method and apparatus for charging operations in a communication network supporting service sessions for direct end users
CN110574489A (zh) * 2017-04-27 2019-12-13 英特尔Ip公司 用于无线通信的增强网络切片管理
CN109429244B (zh) * 2017-08-29 2022-06-28 中兴通讯股份有限公司 一种网络切片子网实例的管理数据隔离的方法和装置
CN109600246B (zh) * 2017-09-30 2021-09-21 华为技术有限公司 网络切片管理方法及其装置
US10855851B2 (en) * 2018-09-13 2020-12-01 Ofinno, Llc Charging control with SMF
US10999447B2 (en) * 2018-11-02 2021-05-04 Ofinno, Llc Charging control in roaming scenario
EP3737197B1 (en) * 2019-05-06 2022-12-07 Comcast Cable Communications LLC Wireless communications for asymmetric services

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180316564A1 (en) * 2017-04-28 2018-11-01 Huawei Technologies Co., Ltd. Service provision for offering network slices to a customer
CN109873730A (zh) * 2017-12-04 2019-06-11 华为技术有限公司 一种网络切片测试管理方法及相关产品
CN110225474A (zh) * 2018-03-02 2019-09-10 华为技术有限公司 一种多连接下的数据量上报方法
WO2019182493A1 (en) * 2018-03-23 2019-09-26 Telefonaktiebolaget Lm Ericsson (Publ) Network slicing awareness in ip multimedia subsystem
CN110213800A (zh) * 2019-05-17 2019-09-06 中国联合网络通信集团有限公司 网络切片业务的处理方法及装置

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on security aspects of 5G network slicing management (Release 15)", 3GPP STANDARD; TECHNICAL REPORT; 3GPP TR 33.811, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG3, no. V1.0.0, 5 June 2018 (2018-06-05), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, pages 1 - 19, XP051451581 *
See also references of EP4024913A4 *

Also Published As

Publication number Publication date
EP4024913A1 (en) 2022-07-06
EP4024913A4 (en) 2022-11-02
CN112584336B (zh) 2022-10-11
CN112584336A (zh) 2021-03-30
US20220217005A1 (en) 2022-07-07
CN115767452A (zh) 2023-03-07

Similar Documents

Publication Publication Date Title
JP7183416B2 (ja) 時間依存ネットワーキング通信方法及び装置
WO2020220747A1 (zh) 一种tsn业务的处理方法、装置及系统
CN111684774B (zh) 移动边缘计算(mec)中的服务质量(qos)控制方法、系统
WO2020103828A1 (zh) 群组通信方法、设备及系统
WO2020221266A1 (zh) 一种通信方法及装置
WO2021017550A1 (zh) 一种事件报告的发送方法、装置及系统
WO2020034976A1 (zh) 一种用户群组的会话管理方法及装置
WO2021017669A1 (zh) 一种通信方法及设备
WO2020220799A1 (zh) 一种通信方法、装置及系统
WO2022021971A1 (zh) 通信方法、第一策略控制网元及通信系统
US11824783B2 (en) Maximum data burst volume (MDBV) determining method, apparatus, and system
WO2021051420A1 (zh) 一种dns缓存记录的确定方法及装置
KR20240060722A (ko) 논리적 tsn 브리지를 위한 방법 및 장치
WO2018233451A1 (zh) 通信方法、装置和系统
US20220263879A1 (en) Multicast session establishment method and network device
WO2021057020A1 (zh) 一种网络切片的计费方法及装置
WO2021057342A1 (zh) 一种网络切片的计费方法及装置
WO2018177003A1 (zh) 一种计费方法、相关设备和系统
WO2021134347A1 (zh) 资源分配方法、装置及系统
WO2023061207A1 (zh) 一种通信方法、通信装置及通信系统
JP7472279B2 (ja) 通信方法、装置、およびシステム
WO2024074095A1 (zh) 一种通信方法及装置
WO2023056784A1 (zh) 数据收集方法、通信装置及通信系统
WO2023213156A1 (zh) 通信方法、通信装置及通信系统
US20230362306A1 (en) Method for performing charging processing on mobile local area network service, system, and related device

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020868159

Country of ref document: EP

Effective date: 20220331