CN114257973A - Service charging method, communication device and storage medium - Google Patents

Service charging method, communication device and storage medium Download PDF

Info

Publication number
CN114257973A
CN114257973A CN202011004698.6A CN202011004698A CN114257973A CN 114257973 A CN114257973 A CN 114257973A CN 202011004698 A CN202011004698 A CN 202011004698A CN 114257973 A CN114257973 A CN 114257973A
Authority
CN
China
Prior art keywords
service
charging
request
target
network slice
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202011004698.6A
Other languages
Chinese (zh)
Inventor
骆旭剑
王修中
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
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 ZTE Corp filed Critical ZTE Corp
Priority to CN202011004698.6A priority Critical patent/CN114257973A/en
Priority to PCT/CN2021/113303 priority patent/WO2022062778A1/en
Publication of CN114257973A publication Critical patent/CN114257973A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information

Abstract

The application provides a service charging method, a communication device and a storage medium. The method comprises the following steps: acquiring a service request of a target service in a target application; sending the service request to a corresponding network slice so that the charging functional entity generates charging information corresponding to the target service according to the charging request, wherein the charging request is generated by the corresponding network slice according to the service request; the network slices corresponding to different target services are different, and the requirements of the target services correspond to the network characteristics of the network slices. According to the technical scheme of the embodiment of the application, the problem that the most suitable resource cannot be provided for each service in the complex application when the resource and the service are provided for the complex application by only one network slice is solved, the resource waste is reduced, the quality of the network service is improved, and meanwhile, the charging of the complex application is more accurate.

Description

Service charging method, communication device and storage medium
Technical Field
The present application relates to the field of communications technologies, and in particular, to a service charging method, a communications device, and a storage medium.
Background
The main application scenarios of the 5G Communication Network include enhanced Mobile Broadband (eMBB), ultra-High-Reliability and Low-Latency Communication (urrllc), large connectivity Machine Type Communication (mtc), and the like, and these scenarios have a great difference in the requirements for Network characteristics, and in order to meet the requirements of different application scenarios, the physical Network can be divided on an end-to-end level to form a Network Slice (Network Slice). In the existing application, each service in the application is realized through one network slice according to the special thought of a network slice private network so as to improve the utilization rate of network resources and the service quality of network services. However, the actual commercial application is often a complex application requiring a plurality of application scenarios to work in a complex manner, and if only one network slice is used to provide resources and services for the complex application, resource waste and network service quality degradation are caused.
Disclosure of Invention
The application provides a service charging method, communication equipment and a storage medium, so as to realize the synergistic effect of multiple network slices in complex application and charge various services in the complex application.
The embodiment of the application provides a service charging method, which is applied to a user terminal and comprises the following steps:
acquiring a service request of a target service in a target application;
sending the service request to a corresponding network slice so that the charging functional entity generates charging information corresponding to the target service according to the charging request, wherein the charging request is generated by the corresponding network slice according to the service request;
the network slices corresponding to different target services are different, and the requirements of the target services correspond to the network characteristics of the network slices.
The embodiment of the application provides a service charging method, which is applied to network slicing and comprises the following steps:
receiving a service request of a target service in a target application sent by a user terminal;
generating a corresponding charging request according to the service request, and sending the charging request to a charging function entity so that the charging function entity generates charging information corresponding to the target service according to the charging request;
the network slices corresponding to different target services are different, and the requirements of the target services correspond to the network characteristics of the network slices.
The embodiment of the application provides a service charging method, which is applied to a charging functional entity and comprises the following steps:
receiving a charging request sent by a network slice;
generating charging information according to the charging request, wherein the charging request is generated by the network slice according to a service request of a target service in a corresponding target application, and the charging information is the charging information corresponding to the target service;
the network slices corresponding to different target services are different, and the requirements of the target services correspond to the network characteristics of the network slices.
An embodiment of the present application provides a communication device, including:
one or more processors;
a storage device arranged to store one or more programs;
when the one or more programs are executed by the one or more processors, the one or more processors are caused to implement the service charging method described above.
The embodiment of the present application also provides a storage medium of computer executable instructions, which when executed by a computer processor, is used for executing the service charging method.
With regard to the above embodiments and other aspects of the present application and implementations thereof, further description is provided in the accompanying drawings description, detailed description and claims.
The method comprises the steps of obtaining a service request of a target service in a target application; sending the service request to a corresponding network slice so that the charging functional entity generates charging information corresponding to the target service according to the charging request, wherein the charging request is generated by the corresponding network slice according to the service request; the network slices corresponding to different target services are different, and the requirements of the target services correspond to the network characteristics of the network slices. The method comprises the steps of distributing network slices corresponding to network characteristics according to requirements provided by corresponding application scenes of different target services in target application, enabling functions required by the target services to be provided by the corresponding network slices, generating charging information corresponding to the target services according to charging requests sent by the different network slices through a charging function entity, enabling functions of all services in the complex application to be cooperatively provided through multiple network slices, and enabling all services in the complex application to be charged respectively. The problem that the most suitable resource cannot be provided for each service in the complex application when only one network slice is adopted to provide the resource and the service for the complex application is solved, the resource waste is reduced, the quality of the network service is improved, and meanwhile, the charging of the complex application is more accurate.
Drawings
Fig. 1 is a flowchart of a service charging method according to an embodiment;
fig. 2 is a flowchart of another service charging method according to an embodiment;
fig. 3 is a flowchart of another service charging method according to an embodiment;
fig. 4 is a flowchart of another service charging method according to an embodiment;
fig. 5 is a flowchart of another service charging method according to an embodiment;
fig. 6 is a flowchart of another service charging method according to an embodiment;
fig. 7 is a schematic structural diagram of a communication device according to an embodiment.
Detailed Description
The present application will be described with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the application and are not limiting of the application. It should be noted that, in the present application, features in the embodiments may be arbitrarily combined with each other without conflict. It should be further noted that, for the convenience of description, only some of the structures related to the present application are shown in the drawings, not all of the structures.
In the existing application, each service in the application is usually realized through one network slice, so as to provide a network environment which is most suitable for the requirement of the main service in the application according to the special idea of the network slice private network, but because the commercial application in practical use is often a complex application which needs to perform composite work in a plurality of application scenes, only one network slice is adopted to provide service for the complex application, so that part of the services in the complex application are difficult to work in the network environment which is suitable for the requirement, and if the network characteristics corresponding to the network slices are modified to enable the complex application to be suitable for all the requirements in the complex application, a large amount of resource waste is caused. The service charging method of this embodiment allocates different network slices to different target services to provide services according to the requirements of the target services and the network characteristics of the network slices, and charges the target services corresponding to each network slice through the charging function entity, so as to provide decision bases for improving the service quality of the complex application and improving the charging accuracy of the complex application.
Fig. 1 is a flowchart of a service charging method according to an embodiment, and as shown in fig. 1, the service charging method according to the embodiment is applied to a user terminal, and the method includes step 110 and step 120.
In step 110, a service request of a target service in a target application is obtained.
In one embodiment, a User Equipment (UE) may be understood as an interactive device between a station and a User, often a general-purpose computer input/output device with a communication processing control function, and the User terminal may include, for example, a desktop computer, a notebook computer, a palm computer, a mobile phone, a vehicle telematics processor, and the like. A target application is understood to be software installed in a user terminal that can provide a plurality of functions for a user to perform a service, that is, a series of computer data and instruction sets organized in a specific order, wherein the target application may include a plurality of services for implementing different functions. The target service may be understood as a function provided in the target application, or a function provided for a sub-service of a certain service in the target application, such as an automatic driving function, a driving recording function, and the like, where different target services have different requirements and are applicable to different application scenarios, so that the requirements of the application scenarios on network characteristics are greatly different. The service request may be understood as service requirement information generated according to a target service operation of a user in a user terminal.
In this embodiment, the user terminal receives operation information of a user, determines an application used by the user through the user terminal according to the operation information, determines the application as a target application, determines a function that the user desires to be implemented by the target application according to the operation information, further determines a target service capable of providing the function in the target application according to the function that the user desires to be implemented by the target application, and determines what operation the user desires to perform on the target service (such as starting a service, updating a service parameter, ending a service, and the like) according to the operation information, so that the user terminal generates a service request corresponding to the user operation. The service request may include at least a service start request, a service update request, and a service end request. The operation information of the user may be a trigger, an input of an external device, or a voice input, which is not limited in the embodiment of the present application.
In step 120, the service request is sent to the corresponding network slice, so that the charging function entity generates charging information corresponding to the target service according to the charging request, and the charging request is generated by the corresponding network slice according to the service request.
The network slices corresponding to different target services are different, and the requirements of the target services correspond to the network characteristics of the network slices.
In an embodiment, a Network Slice (Network Slice) may be understood as an on-demand networking manner, an operator separates a plurality of virtual networks on an end-to-end level on a unified infrastructure according to different requirements of different application scenarios, and each Network Slice performs logical isolation from a radio access Network, a bearer Network and a core Network, has different Network characteristics, and can adapt to requirements of various different types of applications and services. A Charging Function (CHF) may be understood as a functional entity in an Online Charging System (OCS) component in a telecommunications network, and is specifically used for collecting, formatting, transferring and evaluating information related to Charging events so as to implement functions of offline Charging and Online Charging. The online charging system OCS can be understood as a charging system participating in communication process control, is the fusion of the online charging systems, and can solve the problems of real-time credit control of users, real-time charging of prepaid data service and value-added service, and the like.
Exemplarily, in a 5G Communication network, the main application scenarios thereof include eMBB (enhanced Mobile Broadband), urrllc (ultra High-Reliability and Low-Latency Communication), mtc (large Machine Type Communication), and the like. Different application scenarios have different requirements on the network characteristics of the network slice, for example, many terminal devices are provided in an mtc scenario, but the throughput of each device may be very low, and the required bandwidth is very small; in the eMB scene, only a few terminal devices need to be accessed, but each terminal device receives and transmits a large amount of data, so that the required bandwidth is large; in the urrllc scenario, the requirement on the time delay of the end and the end is high, and a small time delay is required, so that network slices with different network characteristics are selected to provide services for different application scenarios. Different target services can correspond to the different application scenarios, for example, an automatic driving service in a vehicle driving application mainly corresponds to a urlllc scenario which requires that the time delay in information transmission is less than 3 milliseconds, and a driving record service in the application corresponds to an eMBB scenario which has low requirements on time delay, but has certain requirements on bandwidth and storage, so that for different services in the same application, network slices with different network characteristics should be configured for the services according to different requirements of the services.
In this embodiment, a network slice corresponding to a target service and having corresponding network characteristics is determined according to different requirements of the target service, and a user terminal sends an acquired service requirement of the target service to the corresponding network slice, so that the network slice generates a corresponding charging request including information for charging, such as time, flow and the like, which are matched with an operation on the target service in the service request, according to the received service request, and sends the charging request to a charging function entity, so that the charging function entity can generate charging information corresponding to the target service according to the information, such as the time, flow and the like, carried in the charging request. For example, the charging information may be represented by a Call ticket, wherein the Call ticket may be understood as original communication Record information in the communication field, which may also be referred to as Call Detail Record (CDR).
Further, in the service charging method, the service request, the charging request, and the charging information all carry an application identifier of a target application, an application identifier of a target service, and an application session identifier, so that the charging function entity generates charging information corresponding to a session according to a service request of a first target service and a service request of a last target service of the same session.
In the service charging method provided by this embodiment, a service request of a target service in a target application is obtained; sending the service request to a corresponding network slice so that the charging functional entity generates charging information corresponding to the target service according to the charging request, wherein the charging request is generated by the corresponding network slice according to the service request; the network slices corresponding to different target services are different, and the requirements of the target services correspond to the network characteristics of the network slices. The method comprises the steps of distributing network slices corresponding to network characteristics according to requirements provided by corresponding application scenes of different target services in target application, enabling functions required by the target services to be provided by the corresponding network slices, generating charging information corresponding to the target services according to charging requests sent by the different network slices through a charging function entity, enabling functions of all services in the complex application to be cooperatively provided through multiple network slices, and enabling all services in the complex application to be charged respectively. The problem that the most suitable resource cannot be provided for each service in the complex application when only one network slice is adopted to provide the resource and the service for the complex application is solved, the resource waste is reduced, the quality of the network service is improved, and meanwhile, the charging of the complex application is more accurate.
Fig. 2 is a flowchart of another service charging method according to an embodiment, and as shown in fig. 2, the method includes steps 210 to 250.
In step 210, a preset network slice corresponding to a preset service in the target application is obtained, and a registration request is sent to an access and mobility management function entity of the preset network slice.
In an embodiment, the preset service may be understood as a service function determined according to a preset rule in the target application, which may be determined according to a main implementation function of the target application, and the network slice corresponding to the preset service may be determined in advance according to a requirement of the preset service, and the network slice is used as the preset network slice corresponding to the preset service. An Access and Mobility Management Function (AMF) may be understood as a functional entity for receiving all connection and session related information of a user terminal and processing connection and Mobility Management tasks.
In this embodiment, when the user terminal accesses the network, the target application in the user terminal may determine the corresponding preset network slice according to the preset service therein, and send a registration request to the access and mobile function management entity AMF in the preset network slice. The registration request carries the requirements of each service in the target application, so that the preset network slice can select the network slice with the corresponding network characteristic according to the requirements of each service in the registration request, and the registration request is forwarded to the access and mobile function management entity AMF of the corresponding network slice to complete the registration of the corresponding service in the target application on different network slices.
In step 220, a registration response of the access and mobility management function entity is received, and a network slice corresponding to other services in the target application is determined according to the registration response.
The registration response includes a corresponding relationship between the network characteristics of the network slice and the requirements of each service in the target application.
In this embodiment, the target application of the user terminal receives the access of the preset network slice and the registration response sent by the mobile management function entity AMF, and determines the network slice corresponding to other services in the target application except the preset service according to the corresponding relationship between the requirements of each service in the target application and the network characteristics of the network slice included in the registration response.
Further, the correspondence between each service in the target application and the Network Slice may be used as a Network Slice Selection Policy (NSSP) and stored in a Network Slice Selection module in the user terminal, so that the corresponding Network Slice may be matched with the target service in time through a routing method according to different selections of the target service in the actual application process.
In step 230, a service request of a target service in the target application is obtained. In this step, the service request of the target service may include: a service start request, a service update request and a service end request.
In step 240, a service start request is sent to the corresponding network slice, so that the charging function entity starts charging according to the charging start request, the charging start request is generated by the corresponding network slice according to the service start request, and the service start request carries the service start time of the target service.
In this embodiment, a target service in a target application receives an operation of a user on the target service, a type of a service request is determined according to an actual operation condition, when the target service is triggered for the first time, the generated service request is a service start request, a user terminal sends the service start request carrying a service start time of the target service to a network slice corresponding to the target service, so that the network slice generates a charging start request carrying the service start time according to the service start request, and sends the charging start request to a charging function entity, so that the charging entity starts charging with the service start time carried therein as a start time after receiving the charging start request. Illustratively, when the charging functional entity performs charging through a ticket, after receiving a charging start request, a ticket corresponding to a target service is opened, and charging is started in the ticket by taking the service start time as the start time.
In step 250, the service end request is sent to the corresponding network slice, so that the charging functional entity generates charging information of the target service according to the charging end request, the charging end request is generated by the corresponding network slice according to the service end request, and the charging end request carries the service end time of the target service and the first service operation flow from start to end.
In this embodiment, when a target service receives information that a user wants to end, which is triggered by the user, the service request of the target service is determined as a service end request, the user terminal sends the service end request carrying service end time of the target service to a network slice corresponding to the target service, so that the network slice generates a charging end request according to the service end time in the service end request and a first service operation flow of the target service counted inside the network slice from the start to the end, and sends the charging end request to a charging function entity, so that the charging function entity generates charging information corresponding to the target service according to the service end time and the first service operation flow in the received charging end request and the service start time of the target service received in advance. Illustratively, when the charging functional entity performs charging through a ticket, after receiving a charging end request, determining service running time in a ticket corresponding to a target service according to service start time and service end time, performing charging processing on the target service according to the determined service running time and received first service running flow, and closing the ticket corresponding to the target service, which is equivalent to generating a ticket corresponding to the current running of the target service.
In an embodiment, after sending the service start request to the corresponding network slice and before sending the service end request to the corresponding network slice, the method further includes:
and sending the service updating request to a corresponding network slice, so that if the charging functional entity does not receive a charging ending request or a charging updating request generated by the network slice within a first preset time, charging information of a target service is generated according to the last charging updating request within the first preset time, the charging information updating request is generated by the corresponding network slice according to the service updating request, and the charging updating request carries service operation time from the beginning to the current updating and second service operation flow.
The first preset time can be set by a person skilled in the art according to an actual situation, and the embodiment of the present application does not limit this.
In this embodiment, after sending the service start request to the corresponding network slice and before sending the service end request to the corresponding network slice, it may be considered that the target service in the target application is executing, in the execution process, parameters and other information in the target service may be adjusted, the user may also operate the target service to update the target service, the generated service request at this time is a service update request, the user terminal sends the service update request carrying the update information of the target service to the network slice corresponding to the target service, the network slice determines a charging updating request containing the service running time from the beginning to the current updating of the target service and the second service running flow according to the updating information and the time information in the service updating request, and sending the charging updating request to the charging functional entity, so that the charging information of the target service is correspondingly updated in the charging functional entity. And if the charging functional entity does not receive a charging ending request or a charging updating request generated by the network slice within the first preset time, the charging is considered to be difficult to be normally completed if the network has errors, and at the moment, the charging information of the target service under the abnormal charging condition can be determined according to the service running time and the second service running flow carried in the last charging updating request within the first preset time, so that the charging information of the target service cannot be completely lost when the abnormal condition occurs.
In an embodiment, the service request, the charging request, and the charging information all include an application identifier of a target application, a service identifier of a target service, and an application session identifier, where the application session identifier is used to identify all sessions in a process of using the target application once, that is, from a service start request of a first target service in the target application to a service end request of a last target service in the target service, corresponding application session identifiers in the time period are consistent, and charging information corresponding to each service request in the target application in the same time period can be synthesized according to the same application session identifier and the same application identifier, so as to form a complex charging information including all charge information in the application.
In the service charging method provided by this embodiment, different network slices are allocated to each service in the target application during registration, so that the requirements of different services in the target service can be provided by the most suitable network slice, the resource allocation of the network slice is more reasonable, and the service quality of the target application by the network is improved; according to different network slices corresponding to the target services, charging information corresponding to different target services is generated, so that the charging of complex applications working cooperatively through multiple network slices is more accurate; and meanwhile, different charging requests are sent to the charging function entity according to different service requests, so that the charging function entity generates charging information corresponding to the target service according to the different charging requests, and the charging information of the target service is settled according to the latest received charging update request when the charging end request or the charging update request is not received within the first preset time, and the charging loss under abnormal conditions is reduced.
Fig. 3 is a flowchart of another service charging method provided in an embodiment, and as shown in fig. 3, the service charging method provided in this embodiment is applied to a network slice, and the method includes step 310 and step 320.
In step 310, a service request of a target service in a target application sent by a user terminal is received.
In this embodiment, a network slice corresponding to a target service receives a service request of the target service in a target application, where the service request may include a service start request, a service update request, and a service end request.
In step 320, a corresponding charging request is generated according to the service request, and the charging request is sent to the charging function entity, so that the charging function entity generates charging information corresponding to the target service according to the charging request.
The network slices corresponding to different target services are different, and the requirements of the target services correspond to the network characteristics of the network slices.
In this embodiment, the network slice obtains time information (such as service start time, service update time, and service end time) in the service request according to different received service requests, generates a charging request corresponding to the service request by combining the time information in the service request and flow information determined by the network slice, and sends the charging request to the charging function entity, so that the charging function entity generates charging information corresponding to the target service according to the information such as time, flow, and the like carried in the charging request.
Further, in the service charging method, the service request, the charging request, and the charging information all carry an application identifier of a target application, a service identifier of a target service, and an application session identifier, so that the charging function entity generates charging information corresponding to a session according to a service request of a first target service and a service request of a last target service of the same session.
In the service charging method provided by this embodiment, a service request of a target service in a target application sent by a user terminal is received; generating a corresponding charging request according to the service request, and sending the charging request to a charging function entity so that the charging function entity generates charging information corresponding to the target service according to the charging request; the network slices corresponding to different target services are different, and the requirements of the target services correspond to the network characteristics of the network slices. The network slice corresponding to the target service in the target application receives a service request of the target service in the target application sent by the user terminal, so that different target services in the target application can be matched with the network slices corresponding to the network characteristics according to different requirements to provide services for the target service, and the corresponding network slices generate corresponding charging requests according to the service request and send the charging requests to the charging function entity, so that the charging function entity can generate charging information corresponding to the target service according to the charging requests, and different network slices are required to perform respective charging of different services in complex applications providing services simultaneously, so that the charging of the complex applications is more accurate.
Fig. 4 is a flowchart of another service charging method provided in an embodiment, as shown in fig. 4, the method includes steps 410 to 460.
In step 410, the access and mobility management function entity of the preset network slice receives a registration request sent by a target application in the user terminal.
The network slice comprises a preset network slice corresponding to a preset service in the target application.
In this embodiment, when the user terminal accesses the network, the access and mobility management functional entity AMF of each network slice in the core network, which corresponds to the preset service in the target application of the user terminal, receives a registration request sent by the target application in the user terminal, where the registration request carries the requirements of each service in the target application.
In step 420, the network slice corresponding to the other service in the target application is determined according to the correspondence between the requirement of each service in the target application and the network characteristics of the network slice, and the registration request is forwarded to the access and mobility management function entity of the network slice corresponding to the other service.
In this embodiment, since the service requirements correspond to the network characteristics of the network slices, and the registration request received by the preset network slice carries the requirements of each service in the target application, the network slice with the corresponding network characteristics corresponding to each service can be determined for each service according to the correspondence between the service requirements and the network characteristics of the network slices, and the registration request is forwarded to the access and mobile management functional entities of the network slices corresponding to other services, so that each service in the target application completes registration on the corresponding network slice.
In step 430, a registration response including a correspondence between the requirements of each service in the target application and the network characteristics of the network slice is sent to the target application, so that other services in the target application determine the corresponding network slice according to the registration response.
In this embodiment, the preset network slice determines a correspondence between the requirements of each service and the network characteristics of the network slice according to the requirement of each service in the target application carried in the registration request, and sends the correspondence to the target application carried in the registration response, so that other services except the preset service in the target application can determine the network slice corresponding to each service according to the correspondence in the registration response.
In step 440, a service request of a target service in a target application sent by a user terminal is received.
In step 450, a charging start request is generated according to the service start request, and the charging start request is sent to the charging function entity, so that the charging function entity starts charging according to the charging start request, and the charging start request carries the service start time of the target service.
In this embodiment, the network slice receives a service start request of a target service corresponding to the network slice, generates a charging start request carrying the service start time according to the service start time of the target service carried in the service start request, and sends the charging start request to the charging function entity, so that the charging function entity starts charging according to the service start time in the charging start request when receiving the charging start request.
In step 460, a charging end request is generated according to the service end request, and the charging end request is sent to the charging functional entity, so that the charging functional entity generates charging information of the target service according to the charging end request, and the charging end request carries the service end time of the target service and the first service running flow from start to end.
In this embodiment, a network slice receives a service end request of a target service corresponding to the network slice, internally counts to obtain a first service operation flow from start to end of the target service when the service end request is received, generates a charging end request carrying the information according to a service end time of the target service carried in the service end request and the counted first service operation flow, and sends the charging end request to a charging function entity, so that the charging function entity determines a service operation time according to the received service end time and a service start time received earlier when the charging end request is received, and generates charging information corresponding to the target service according to the first service operation flow in the charging end request.
In an embodiment, the network slice may also receive a service update request after receiving a service start request and before receiving a service end request.
And generating a charging updating request according to the service updating request, and sending the charging updating request to the charging function entity, so that if the charging function entity does not receive a charging ending request or a charging updating request within a first preset time, charging information of a target service is generated according to the last charging updating request within the first preset time, wherein the charging updating request carries service operation time from the beginning to the current updating and second service operation flow.
In this embodiment, after receiving the service start request and before receiving the service end request, it may be considered that the target service corresponding to the network slice is being executed and should be charged, a service update request carrying update information of a target service sent by a user terminal can be received in the service execution process, determining the service running time from the beginning to the current updating according to the updating information and the time information carried in the service updating request, and the second service operation flow rate which is obtained by the internal statistics of the network slice and runs in the network slice from the beginning to the current target service carries the service operation time from the beginning to the current update and the second service operation flow rate in the generated charging update request, and sending the charging updating request to the charging functional entity, so that the charging information of the target service is correspondingly updated in the charging functional entity. And if the charging functional entity does not receive a charging ending request or a charging updating request generated by the network slice within the first preset time, the charging is considered to be difficult to be normally completed if the network has errors, and at the moment, the charging information of the target service under the abnormal charging condition can be determined according to the service running time and the second service running flow carried in the last charging updating request within the first preset time, so that the charging information of the target service cannot be completely lost when the abnormal condition occurs.
In an embodiment, if a charging start request is generated by a network slice according to a service start request and a service request sent by a user terminal is not received within a second preset time after the charging start request is sent to a charging function entity, a charging update request is generated and sent to the charging function entity, so that if the charging function entity does not receive a charging end request or a charging update request within a first preset time, charging information of a target service is generated according to a last charging update request within the first preset time, and the charging update request carries service running time from start to current update and third service running flow.
In this embodiment, if the time before the network slice receives a next service request sent from the user terminal exceeds a second preset time after generating a charging start request according to the received service start request and sending the charging start request to the charging function entity, a charging update request is generated after the charging start request is sent to the charging function entity for the second preset time, the charging update request carries a currently updated service running time and a third service running flow from the start to a time point of generating the charging update request, and the generated charging update request is sent to the charging function entity, so that the charging information of the target service in the charging function entity is updated correspondingly. And if the charging functional entity does not receive a charging ending request or a charging updating request generated by the network slice within the first preset time, the charging is considered to be difficult to be normally completed if the network has errors, and the charging information of the target service under the abnormal charging condition can be determined according to the service running time and the third service running flow carried in the last charging updating request within the first preset time, so that the charging information of the target service cannot be completely lost when the abnormal condition occurs. The second preset time may be set by a person skilled in the art according to an actual situation, and the second preset time should be less than the first preset time, which is not specifically limited in the embodiment of the present application.
The service charging method provided in this embodiment receives, through a preset network slice, a registration request sent by a target application of a user terminal, determines, according to a requirement of each service in the target application in the registration request and a correspondence between the requirement of the service and a network characteristic of the network slice, a correspondence between each service in the target application and the network slice, and sends the correspondence back to the target application by carrying the correspondence in a registration response, so that requirements of different services in the target service can be provided by an optimum network slice. Different charging requests are generated according to different received service requests and are sent to the charging function entity, so that the charging function entity generates charging information corresponding to the target service according to the different charging requests, and a charging updating request is automatically generated and sent to the charging function entity when the service request of the user terminal is not received within a second preset time period, so that the charging updating of the target service in the charging function entity is completed, the charging function entity can settle the charging information of the target service according to the charging updating request received last time in abnormal conditions, the updating result which is the latest when the abnormal conditions occur can be reserved by the timing updating, and the charging loss of an operator in the abnormal conditions is reduced.
Fig. 5 is a flowchart of another service charging method provided in an embodiment, and as shown in fig. 5, the service charging method provided in this embodiment is applied to a charging function entity, and the method includes step 510 and step 520.
In step 510, a charging request sent by the network slice is received.
In this embodiment, the charging functional entity receives a charging request sent by a network slice, where a charging object corresponding to the charging request is a target application of a target service corresponding to the network slice, and the charging request may include a charging start request, a charging update request, and a charging end request.
In step 520, charging information is generated according to the charging request, the charging request is generated by the network slice according to the service request of the target service in the corresponding target application, and the charging information is the charging information of the corresponding target service.
The network slices corresponding to different target services are different, and the requirements of the target services correspond to the network characteristics of the network slices.
In this embodiment, the charging functional entity determines the running time and the running flow of the target service corresponding to the network slice according to the received charging request, and comprehensively generates the charging information of the target service according to the determined running time, running flow, and the service start time and service end time of the target service included in the received charging request.
Further, in the service charging method, the service request, the charging request, and the charging information all carry an application identifier of a target application, a service identifier of a target service, and an application session identifier, so that the charging function entity generates charging information corresponding to a session according to a service request of a first target service and a service request of a last target service of the same session.
In the service charging method provided by this embodiment, a charging request sent by a network slice is received; generating charging information according to the charging request, wherein the charging request is generated by the network slice according to a service request of a target service in a corresponding target application, and the charging information is the charging information corresponding to the target service; the network slices corresponding to different target services are different, and the requirements of the target services correspond to the network characteristics of the network slices. The charging request generated by the network slice corresponding to the target service in the target application is received, and the charging information corresponding to the target service is generated according to the charging request, so that the charging functional entity can respectively charge different network slices, and further, the respective charging of different services can be realized in the complex application which needs different network slices to provide services simultaneously, and the charging of the complex application is more accurate.
Fig. 6 is a flowchart of another service charging method according to an embodiment, and as shown in fig. 6, the method includes steps 610 to 640.
In step 610, a charging request sent by the network slice is received.
In an embodiment, the charging request may include a charging start request and a charging end request.
In step 620, the service start time of the target service is determined according to the charging start request.
In this embodiment, the charging start request carries the service start time of the target service corresponding to the network slice, and the charging functional entity starts charging the target service with the service start time carried in the charging start request after receiving the charging start request.
In step 630, the service end time of the target service and the first service operation flow from the beginning to the end are determined according to the charging end request.
In this embodiment, the charging end request carries a service end time of a target service corresponding to a network slice and a first service operation flow obtained by counting the target service in the network slice, and the charging functional entity reads the service end time and the first service operation flow from the charging end request and stops charging the target service when receiving the charging end request.
In step 640, charging information of the target service is generated according to the service start time, the first service operation flow and the service end time.
In this embodiment, the service running time of the target service is determined according to the received service start time and the service end time, and the charging information of the target service is generated according to the determined service running time and the received first service running flow in combination with the preset charging rule.
In an embodiment, after receiving the charging start request, the charging function entity may further receive a charging update request sent by the network slice before receiving the charging end request.
And determining the service operation time of the target service from the beginning to the current update and the second service operation flow or the third service operation flow according to the charging update request.
In this embodiment, if the charging update request is generated by the network slice according to the received service update request, the service operation time from the start to the current update carried in the charging update request is the time from the start to the reception of the service update request, and the carried operation flow is the second service operation flow; if the charging update request is generated by the network slice not receiving the service request within the second preset time after receiving the service start request, the service operation time from the start to the current update carried in the charging update request is the second preset time from the start to the network slice receiving the last service request, and the carried operation flow is the third service operation flow.
And if the charging ending request or the charging updating request sent by the network slice is not received within the first preset time, generating charging information of the target service according to the service running time from the beginning to the current updating of the target service carried in the last charging updating request within the first preset time and the second service running flow or the service running flow.
In this embodiment, if the charging functional entity does not receive a charging end request or a charging update request generated by a network slice within a first preset time, it may be considered that it is difficult for the network to normally complete charging due to an error, at this time, charging information of a target service is generated according to a last charging update request within the first preset time, and if the charging update request is generated by the network slice according to the received service update request, the charging information of the target service under this abnormal charging condition is determined according to service running time carried in the charging update request from the beginning to the current updating, which is time from the beginning to the receiving of the service update request, and a second service running flow; and if the charging updating request is generated by the network slice not receiving the service request within a second preset time after receiving the service starting request, determining the charging information of the target service under the abnormal charging condition according to the second preset time from the start to the network slice receiving the last service request and the third service operation flow carried in the charging updating request.
The service charging method provided by this embodiment generates charging information of a target service corresponding to a network slice according to a received charging start request and a charging end request, updates the charging information of the target service when a charging update request is received, and confirms the charging information of the target service according to a recently received charging update request under an abnormal condition, thereby implementing respective charging of different services in complex applications requiring different network slices to provide services at the same time, and implementing settlement of the charging information of the target service according to the recently received charging update request by a charging function entity under the abnormal condition, and the latest update result at the time when the abnormal condition occurs can be retained by timing update, thereby reducing the charging loss of an operator under the abnormal condition.
Fig. 7 is a schematic structural diagram of a communication device according to an embodiment, as shown in fig. 7, the device includes a processor 710, a storage 720, an input unit 730, and an output unit 740; the number of processors 710 in the device may be one or more, and one processor 710 is taken as an example in fig. 7; the processor 710, the storage device 720, the input device 730, and the output device 740 of the apparatus may be connected by a bus or other means, which is exemplified in fig. 7.
The storage device 720 is a computer-readable storage medium, and can be used to store software programs, computer-executable programs, and modules, such as program instructions/modules corresponding to the service charging method in the embodiment of the present application. The processor 710 executes various functional applications and data processing of the device by running software programs, instructions and modules stored in the storage 720, so as to implement the service charging method described above.
The storage device 720 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function; the storage data area may store data created according to the use of the terminal, and the like. Additionally, the storage 720 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device. In some examples, the storage 720 may further include memory located remotely from the processor 710, which may be connected to a communication device via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The input device 730 may be used to receive input numeric or character information and generate signal inputs related to user settings and function control of the apparatus, and may include a touch screen, a keyboard, a mouse, and the like. The output device 740 may include a display device such as a display screen.
Embodiments of the present application also provide a storage medium containing computer-executable instructions, which when executed by a computer processor, are configured to perform a service charging method.
Through the above description of the embodiments, those skilled in the art will appreciate that the present application can be implemented by software, general hardware, or hardware. Based on such understanding, the technical solution of the present application may be embodied in the form of a software product, and the computer software product may be stored in a computer-readable storage medium, such as a floppy disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a FLASH Memory (FLASH), a hard disk or an optical disk of a computer, and includes a plurality of instructions for enabling a computer device (which may be a personal computer, a server, or a network device) to execute the method according to any embodiment of the present application.
The above description is only exemplary embodiments of the present application, and is not intended to limit the scope of the present application.
Any logic flow block diagrams in the figures of this application may represent program steps, or may represent interconnected logic circuits, modules, and functions, or may represent a combination of program steps and logic circuits, modules, and functions. The computer program may be stored on a memory. The memory may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as, but not limited to, Read Only Memory (ROM), Random Access Memory (RAM), optical storage devices and systems (digital versatile disks, DVDs, or CD discs), etc. The computer readable medium may include a non-transitory storage medium. The data processor may be of any type suitable to the local technical environment, such as but not limited to general purpose computers, special purpose computers, microprocessors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), programmable logic devices (FGPAs), and processors based on a multi-core processor architecture.
The foregoing has provided by way of exemplary and non-limiting examples a detailed description of exemplary embodiments of the present application. Various modifications and adaptations to the foregoing embodiments may become apparent to those skilled in the relevant arts in view of the following drawings and the appended claims without departing from the scope of the invention. Therefore, the proper scope of the invention is to be determined according to the claims.

Claims (20)

1. A service charging method is applied to a user terminal, and comprises the following steps:
acquiring a service request of a target service in a target application;
sending the service request to a corresponding network slice so that the charging functional entity generates charging information corresponding to the target service according to the charging request, wherein the charging request is generated by the corresponding network slice according to the service request;
the network slices corresponding to different target services are different, and the requirements of the target services correspond to the network characteristics of the network slices.
2. The method of claim 1, wherein before the obtaining the service request of the target service in the target application, the method further comprises:
acquiring a preset network slice corresponding to a preset service in the target application, and sending a registration request to an access and mobile management functional entity of the preset network slice;
receiving registration response of the access and mobile management functional entity, and determining network slices corresponding to other services in the target application according to the registration response;
and the registration response comprises the corresponding relation between the network characteristics of the network slice and the requirements of each service in the target application.
3. The method of claim 1, wherein sending the service request to a corresponding network slice to enable the charging function entity to generate charging information corresponding to the target service according to a charging request, the charging request being generated by the corresponding network slice according to the service request, comprises:
sending a service start request to a corresponding network slice so that a charging function entity starts charging according to the charging start request, wherein the charging start request is generated by the corresponding network slice according to the service start request, and the service start request carries the service start time of the target service;
and sending a service ending request to a corresponding network slice so that a charging functional entity generates charging information of the target service according to the charging ending request, wherein the charging ending request is generated by the corresponding network slice according to the service ending request, and the charging ending request carries the service ending time of the target service and the first service running flow from beginning to end.
4. The method of claim 3, wherein the service request is sent to a corresponding network slice, so that the charging functional entity generates charging information corresponding to the target service according to a charging request, and the charging request is generated by the corresponding network slice according to the service request, further comprising:
after a service start request is sent to a corresponding network slice, and before a service end request is sent to the corresponding network slice, a service update request is sent to the corresponding network slice, so that if a charging end request or a charging update request generated by the network slice is not received by the charging function entity within a first preset time, charging information of the target service is generated according to a last charging update request within the first preset time, the charging update request is generated by the corresponding network slice according to the service update request, and the charging update request carries service operation time from start to current update and second service operation flow.
5. The method according to any of claims 1-4, wherein the service request, the charging request and the charging information carry an application identifier of the target application and a service identifier of the target service.
6. The method according to claim 5, wherein the service request, the charging request and the charging information further include an application session identifier, so that the charging functional entity generates the charging information corresponding to the session according to the service request of the first target service and the service request of the last target service in the same session.
7. A service charging method is applied to network slicing and comprises the following steps:
receiving a service request of a target service in a target application sent by a user terminal;
generating a corresponding charging request according to the service request, and sending the charging request to a charging function entity so that the charging function entity generates charging information corresponding to the target service according to the charging request;
the network slices corresponding to different target services are different, and the requirements of the target services correspond to the network characteristics of the network slices.
8. The method of claim 7, wherein the network slice includes a preset network slice corresponding to a preset service in a target application, and before receiving a service request of the target service in the target application sent by the user terminal, the method further includes:
the access and mobile management functional entity of the preset network slice receives a registration request sent by a target application in a user terminal;
determining network slices corresponding to other services in the target application according to the corresponding relation between the requirements of each service in the target application and the network characteristics of the network slices, and forwarding a registration request to access and mobile management functional entities of the network slices corresponding to the other services;
and sending a registration response comprising the corresponding relation between the requirement of each service in the target application and the network characteristics of the network slice to the target application so as to enable other services in the target application to determine the corresponding network slice according to the registration response.
9. The method of claim 7, wherein the service request comprises a service start request and a service end request; the generating a corresponding charging request according to the service request and sending the charging request to a charging function entity includes:
generating a charging start request according to the service start request, and sending the charging start request to the charging function entity so that the charging function entity starts charging according to the charging start request, wherein the charging start request carries the service start time of the target service;
and generating a charging ending request according to the service ending request, and sending the charging ending request to the charging functional entity so that the charging functional entity generates charging information of the target service according to the charging ending request, wherein the charging ending request carries service ending time of the target service and first service operation flow from beginning to end.
10. The method of claim 9, wherein the service request further comprises a service update request; the generating a corresponding charging request according to the service request and sending the charging request to a charging function entity further comprises:
generating a charging updating request according to the service updating request, and sending the charging updating request to the charging function entity, so that if the charging function entity does not receive a charging ending request or a charging updating request within a first preset time, charging information of the target service is generated according to the last charging updating request within the first preset time, wherein the charging updating request carries service operation time from beginning to current updating and second service operation flow.
11. The method of claim 10, wherein after generating a charging start request according to the service start request and sending the charging start request to the charging function entity, the method further comprises:
and if the service request sent by the user terminal is not received within the second preset time, generating a charging updating request, and sending the charging updating request to the charging function entity, so that if the charging function entity does not receive a charging ending request or a charging updating request within the first preset time, the charging information of the target service is generated according to the last charging updating request within the first preset time, and the charging updating request carries service operation time from the beginning to the current updating and third service operation flow.
12. The method according to any of claims 7-11, wherein the service request, the charging request, and the charging information carry an application identifier of the target application and a service identifier of the target service.
13. The method according to claim 12, wherein the service request, the charging request and the charging information further include an application session identifier, so that the charging function entity generates the charging information corresponding to the session according to the service request of the first target service and the service request of the last target service in the same session.
14. A service charging method is applied to a charging function entity, and comprises the following steps:
receiving a charging request sent by a network slice;
generating charging information according to the charging request, wherein the charging request is generated by the network slice according to a service request of a target service in a corresponding target application, and the charging information is the charging information corresponding to the target service;
the network slices corresponding to different target services are different, and the requirements of the target services correspond to the network characteristics of the network slices.
15. The method of claim 14, wherein the charging request comprises a charging start request and a charging end request; generating charging information according to the charging request comprises the following steps:
determining the service starting time of the target service according to the charging starting request;
determining the service end time of the target service and the first service operation flow from the beginning to the end according to the charging end request;
and generating charging information of the target service according to the service starting time, the first service operation flow and the service ending time.
16. The method of claim 15, wherein the charging request further comprises a charging update request; generating charging information according to the charging request, further comprising:
determining the service operation time of the target service from the beginning to the current update and the second service operation flow or the third service operation flow according to the charging update request;
and if the charging ending request or the charging updating request sent by the network slice is not received within the first preset time, generating charging information of the target service according to the service running time from the beginning to the current updating of the target service carried in the last charging updating request within the first preset time and the second service running flow or the third service running flow.
17. The method according to any of claims 14-16, wherein the service request, the charging request, and the charging information carry an application identifier of the target application and a service identifier of the target service.
18. The method according to claim 17, wherein the service request, the charging request and the charging information further include an application session identifier, so that the charging function entity generates the charging information corresponding to the session according to the service request of the first target service and the service request of the last target service in the same session.
19. A communication device, comprising:
one or more processors;
a storage device arranged to store one or more programs;
when executed by the one or more processors, cause the one or more processors to implement a service charging method as recited in any of claims 1-6 or 7-13 or 14-18.
20. A storage medium of computer executable instructions, which when executed by a computer processor is for performing a service charging method as claimed in any one of claims 1-6 or 7-13 or 14-18.
CN202011004698.6A 2020-09-22 2020-09-22 Service charging method, communication device and storage medium Pending CN114257973A (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202011004698.6A CN114257973A (en) 2020-09-22 2020-09-22 Service charging method, communication device and storage medium
PCT/CN2021/113303 WO2022062778A1 (en) 2020-09-22 2021-08-18 Service charging method, communication device and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202011004698.6A CN114257973A (en) 2020-09-22 2020-09-22 Service charging method, communication device and storage medium

Publications (1)

Publication Number Publication Date
CN114257973A true CN114257973A (en) 2022-03-29

Family

ID=80789698

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202011004698.6A Pending CN114257973A (en) 2020-09-22 2020-09-22 Service charging method, communication device and storage medium

Country Status (2)

Country Link
CN (1) CN114257973A (en)
WO (1) WO2022062778A1 (en)

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106572517B (en) * 2015-10-09 2018-12-18 中国移动通信集团公司 The processing method of network slice, the selection method and device for accessing network
EP3646641A1 (en) * 2017-06-29 2020-05-06 Nokia Solutions and Networks Oy Network slice selection based on charging rules
CN109429277A (en) * 2017-07-05 2019-03-05 中兴通讯股份有限公司 The selection method of network slice, apparatus and system
CN110461027B (en) * 2018-05-07 2020-11-17 华为技术有限公司 Network slice selection method and device
US11330648B2 (en) * 2019-02-15 2022-05-10 Ofinno, Llc Charging aggregation control for network slices
CN113784300A (en) * 2019-03-07 2021-12-10 华为技术有限公司 Method, system and related equipment for carrying out charging processing on network slice client

Also Published As

Publication number Publication date
WO2022062778A1 (en) 2022-03-31

Similar Documents

Publication Publication Date Title
US10715680B2 (en) Charging method and device involved in a protocol data unit (PDU) session
KR20200012981A (en) Network slice management methods, devices, and computer readable storage media
EP3920562A1 (en) Method and system for performing charging processing on network slice client, and related device
WO2018215046A1 (en) Edge cloud broker and method therein for allocating edge cloud resources
CN109787780B (en) Charging method based on API content and capability open function entity
CN108632063B (en) Method, device and system for managing network slice instances
US11470202B2 (en) Charging method, apparatus, and system
CN113596863A (en) Method, apparatus and medium for determining user plane function and providing information
CN114554550A (en) Communication method and device for 5G access network and edge cloud gateway
KR102596498B1 (en) Billing methods, devices, and systems
CN114302426A (en) Method, apparatus, medium, and electronic device for controlling quality of service in heterogeneous network
CN114666423A (en) TCP stream adjusting method and system
EP3086530A1 (en) Network resource sharing processing and sharing method, device and system
CN107426109B (en) Traffic scheduling method, VNF module and traffic scheduling server
CN111436029A (en) Method, system and related equipment for carrying out charging processing on network slice example
EP3101926A1 (en) Charging processing method, centralized network control node, function node and system
CN114257973A (en) Service charging method, communication device and storage medium
CN112584336B (en) Charging method and device for network slices
CN112584337B (en) Charging method and device for network slice
CN114826920B (en) Network slice opening method, device, equipment and storage medium
KR20190135298A (en) Network apparatus and control method thereof
EP3855808A1 (en) Setup of communication session for assigning a network slice based on an unique transaction identifier
EP4013082A1 (en) Charging method, apparatus and system
US20230362306A1 (en) Method for performing charging processing on mobile local area network service, system, and related device
EP3177067A1 (en) Network controller, system, and method for resource allocation

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination