Business charging method, communication device, and storage medium

Abstract

The application provides a service charging method, a communication device and a storage medium. The method comprises the following steps: obtaining a service request of a target service in a target application; sending the service request to a corresponding network slice, so that a charging function entity generates charging information corresponding to the target service according to a charging request, wherein the charging request is generated by the corresponding network slice according to the service request; wherein different network slices correspond to different target services, and the requirements of the target service correspond to the network characteristics of the network slice. The technical scheme of the embodiment of the application solves the problem that when only one network slice is used to provide resources and services for a complex application, the most suitable resources cannot be provided for each service in the complex application, reduces the waste of resources and improves the quality of network services, and makes the charging of the complex application more accurate.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of communication, in particular to a service charging method, a communication device and a storage medium. BACKGROUND

[0002] The main application scenarios of 5G communication network include enhanced mobile broadband (eMBB), ultra high-reliability and low-latency communication (uRLLC) and massive machine type communication (mMTC), etc., and these scenarios have great differences in the demand for network characteristics. In order to meet the needs of different application scenarios, the physical network can be divided at the end-to-end level to form network slices. In existing applications, each service in the application is usually implemented through a network slice according to the idea of network slice dedicated network, so as to improve the utilization rate of network resources and the service quality of network services. However, actual commercial applications are often complex applications that require multiple application scenarios to work together. If only one network slice is used to provide resources and services for complex applications, it will cause waste of resources and reduction of network service quality. SUMMARY

[0003] The present application provides a service charging method, a communication device and a storage medium, to realize the synergistic effect of multiple network slices in complex applications and the charging of each service in complex applications.

[0004] The present application provides a service charging method, which is applied to a user terminal and includes the following steps:

[0005] Obtaining a service request of a target service in a target application;

[0006] Sending the service request to a corresponding network slice, so that the charging function 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;

[0007] Wherein, the network slices corresponding to different target services are different, and the demand of the target service corresponds to the network characteristics of the network slice.

[0008] The present application provides a service charging method, which is applied to a network slice and includes the following steps:

[0009] Receiving a service request of a target service in a target application sent by a user terminal;

[0010] 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;

[0011] Different network slices correspond to different target services, and a demand of the target service corresponds to a network characteristic of the network slice.

[0012] The embodiment of the present application provides a service charging method, applied to a charging function entity, and comprising the following steps:

[0013] receiving a charging request sent by a network slice;

[0014] 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 charging information corresponding to the target service;

[0015] Different network slices correspond to different target services, and a demand of the target service corresponds to a network characteristic of the network slice.

[0016] The embodiment of the present application provides a communication device, comprising:

[0017] one or more processors;

[0018] a storage device configured to store one or more programs;

[0019] When the one or more programs are executed by the one or more processors, the one or more processors implement the above-mentioned service charging method.

[0020] The embodiment of the present application also provides a storage medium of computer executable instructions, which is used for executing the above-mentioned service charging method when executed by a computer processor.

[0021] The above embodiments and other aspects of the present application and implementation manners thereof are described in more detail in the description of drawings, specific embodiments and claims.

[0022] The embodiment of the application obtains a service request of a target service in a target application; sends the service request to a corresponding network slice, so that the charging function 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; wherein the network slices corresponding to different target services are different, and the requirements of the target service correspond to the network characteristics of the network slice. The requirements proposed by the corresponding application scenarios of different target services in the target application are quite different, and the network slice corresponding to the network characteristics is allocated to the target service, so that the functions required by the target service can be provided by the corresponding network slice, and the charging function entity generates the charging information corresponding to the target service according to the charging request sent by the different network slices, so that the functions of each service in the complex application can be provided by the multiple network slices, and each service in the complex application can be charged separately. The problem that the most suitable resources for each service in the complex application cannot be provided when only one network slice is used to provide resources and services for the complex application is solved, the waste of resources is reduced, the quality of network services is improved, and the charging of the complex application is more accurate. BRIEF DESCRIPTION OF DRAWINGS

[0023] Figure 1 A flowchart of a service charging method provided by an embodiment;

[0024] Figure 2 A flowchart of another service charging method provided by an embodiment;

[0025] Figure 3 A flowchart of another service charging method provided by an embodiment;

[0026] Figure 4 A flowchart of another service charging method provided by an embodiment;

[0027] Figure 5 A flowchart of another service charging method provided by an embodiment;

[0028] Figure 6 A flowchart of another service charging method provided by an embodiment;

[0029] Figure 7 A structural schematic diagram of a communication device provided by an embodiment. DETAILED DESCRIPTION

[0030] The present application will be described below in conjunction with the accompanying drawings and embodiments. It can be understood that the specific embodiments described herein are only used to explain the present application, but not to limit the present application. It should be noted that the features in the embodiments of the present application can be combined with each other arbitrarily without conflict. In addition, it should be noted that only the parts related to the present application are shown in the drawings for the convenience of description, not all the structures.

[0031] In the existing application, each service in the application is implemented through a network slice to provide the main service in the application with the most suitable network environment according to the network slice dedicated network. However, since the commercial application in actual use is often a complex application that needs to work in multiple application scenarios, using only one network slice to provide services for the complex application will cause some services to be difficult to work in the network environment suitable for their needs. If the network characteristics of the network slice are modified to adapt to all the needs of the complex application, it will cause a large waste of resources. The service charging method of the embodiment allocates different network slices to provide services for different target services according to the needs 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, which provides a decision basis for improving the service quality of the complex application and improving the charging accuracy of the complex application.

[0032] Figure 1 A flowchart of a service charging method provided by an embodiment is shown in Figure 1 The service charging method provided by the embodiment is applied to a user terminal, and the method includes steps 110 and 120.

[0033] In step 110, the service request of the target service in the target application is obtained.

[0034] In an embodiment, a user terminal (User Equipment, UE) can be understood as a station and a user interaction device, usually a general-purpose computer input and output device attached with a communication processing control function. Exemplarily, the user terminal can include a desktop computer, a notebook, a palm computer, a mobile phone, a vehicle telematics processor, etc. A target application can be understood as software installed in the user terminal, which can provide a variety of functions for the user to serve, that is, a set of computer data and instructions organized in a specific order, wherein the target application can include multiple services that implement different functions. A target service can be understood as a function that can be provided in the target application, or a function that can be provided by a sub-service of a certain service in the target application, such as an automatic driving function, a driving record function, etc., wherein different target services have different requirements and are applied in different application scenarios, which in turn leads to great differences in the requirements of the application scenarios for network characteristics. A service request can be understood as service demand information generated according to the user's operation in the user terminal for the target service.

[0035] In the embodiment, by receiving the operation information of the user at the user terminal, the application used by the user through the user terminal is determined according to the operation information, and the application is determined as the target application. The function that the user wants the target application to implement is determined according to the operation information, and then the target service in the target application that can provide the function is determined according to the function that the user wants the target application to implement. It is determined according to the operation information that the user wants to perform what operation on the target service (such as starting the service, updating the service parameter, ending the service, etc.), so that the user terminal generates a service request corresponding to the user's operation. Wherein, the service request can at least include a service start request, a service update request and a service end request. Wherein, the operation information of the user can be a trigger, an external device input or a voice input, etc., which is not limited in the embodiment of the present application.

[0036] 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, which is generated by the corresponding network slice according to the service request.

[0037] Wherein, different network slices correspond to different target services, and the requirements of the target service correspond to the network characteristics of the network slice.

[0038] In an embodiment, a network slice can be understood as a kind of on-demand networking manner, and an operator separates a plurality of virtual networks on an end-to-end level according to different requirements of different application scenarios on a unified infrastructure, each network slice is logically isolated from a radio access network, a bearer network to a core network, has different network characteristics, and can adapt to the requirements of various different types of applications and services. A charging function entity (CHF) can be understood as a kind of function 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 realize the functions of offline charging and online charging. Among them, the online charging system OCS can be understood as a charging system participating in the control of the communication process, which is the integration of the online charging system, and can solve the problems of real-time credit control of users, real-time charging of pre-paid data services and value-added services, etc.

[0039] For example, in a 5G communication network, its main application scenarios include eMBB (enhanced Mobile Broadband), uRLLC (ultra High-Reliability and Low-Latency Communication), mMTC (massive Machine Type Communication), etc. Different application scenarios have great differences in the requirements of network characteristics of network slices. For example, in the mMTC scenario, there are many terminal devices, but the throughput of each device may be low and the required bandwidth is small; in the eMBB scenario, only a small number of terminal devices need to be accessed, but each terminal device will transmit a large amount of data, and the required bandwidth is large; in the uRLLC scenario, the end-to-end delay requirement is high, and a small delay is required. Therefore, different network slices with different network characteristics should be selected to provide services for different application scenarios. Different target services can correspond to the above different application scenarios, such as the automatic driving service in the vehicle driving application, which mainly corresponds to the uRLLC scenario, and requires that the delay in information transmission is less than 3 milliseconds. The driving record service in the application corresponds to the eMBB scenario, which has a low requirement on the delay, but has certain requirements on the bandwidth and storage. Therefore, for different services in the same application, different network slices with different network characteristics should be configured according to the different requirements of the services.

[0040] In this embodiment, the network slice corresponding to the target service is determined according to the different requirements of the target service, and the user terminal sends the service requirement of the target service to the corresponding network slice, so that the network slice generates a charging request containing the information for charging, such as time and traffic, in the service request corresponding to the operation of the target service according to the received service request, and sends the charging request to the charging function entity, so that the charging function entity can generate charging information corresponding to the target service according to the time and traffic information carried in the charging request. For example, the charging information can be represented by a bill, which can be understood as the original communication record information in the communication field, and can also be called Call Detail Record (CDR).

[0041] Further, in the above-mentioned service charging method, the application identifier of the target application, the application identifier of the target service, and the application session identifier are carried in the service request, the charging request, and the charging information, 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.

[0042] The service charging method provided in this embodiment acquires the service request of the target service in the target application, sends the service request to the corresponding network slice, so that the charging function entity generates the 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. Different network slices correspond to different target services, and the requirements of different target services correspond to the network characteristics of the network slice. The requirements of different target services in the target application are greatly different according to the corresponding application scenarios, and the network slice with corresponding network characteristics is allocated to the target service, so that the functions required by the target service can be provided by the corresponding network slice, and the charging information corresponding to the target service is generated by the charging function entity according to the charging request sent by the different network slices, so that the functions of each service in the complex application can be provided by the multiple network slices, and each service in the complex application can be charged separately. The problem that only one network slice is used to provide resources and services for the complex application cannot provide the most suitable resources for each service in the complex application is solved, the waste of resources is reduced, and the quality of network service is improved, and the charging of the complex application is more accurate.

[0043] Figure 2 The flowchart of another service charging method provided in an embodiment is shown in FIG. 2, and the method includes steps 210 to 250. Figure 2

[0044] ​In step 210, a preset network slice corresponding to a preset service in the target application is acquired, and a registration request is sent to an access and mobility management function entity of the preset network slice.

[0045] In an embodiment, the preset service can be understood as a service function determined in the target application according to a preset rule, which can be determined according to the main function of the target application. The network slice corresponding to the preset service can be determined in advance according to the demand of the preset service, and the network slice is taken as the preset network slice corresponding to the preset service. The access and mobility management function entity (AMF) can be understood as a function entity for receiving all connection and session related information of a user terminal, and processing connection and mobility management tasks.

[0046] In this embodiment, when the user terminal accesses the network, the target application in the user terminal can determine the corresponding preset network slice according to the preset service therein, and send a registration request to the access and mobility function management entity AMF in the preset network slice. The registration request carries the demand of each service in the target application, so that the preset network slice can select a network slice with corresponding network characteristics according to the demand of each service in the registration request, and forward the registration request to the access and mobility 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.

[0047] In step 220, a registration response of the access and mobility management function entity is received, and the network slice corresponding to other services in the target application is determined according to the registration response.

[0048] The registration response includes the correspondence between the demand of each service in the target application and the network characteristics of the network slice.

[0049] In this embodiment, the target application of the user terminal receives the registration response sent by the access and mobility management function entity AMF of the preset network slice, and determines the network slice corresponding to other services in the target application except the preset service according to the correspondence between the demand of each service in the target application and the network characteristics of the network slice included in the registration response.

[0050] Further, the correspondence between each service in the target application and the network slice can be taken as a network slice selection policy (NSSP), and saved in a network slice selection module in the user terminal, so that in the actual application process, the corresponding network slice can be matched for the target service in time through the routing method according to the selection of the target service.

[0051] In step 230, a service request of the target service in the target application is acquired. In this step, the service request of the target service can include a service start request, a service update request and a service end request.

[0052] In step 240, the service start request is sent to the corresponding network slice, so that the charging function entity starts charging according to the charging start request generated by the corresponding network slice according to the service start request, and the charging start request carries the service start time of the target service.

[0053] In this embodiment, the target service in the target application receives the operation of the user, determines the type of the service request according to the actual operation, and generates a service start request when the target service is triggered for the first time. The user terminal sends the service start request carrying the service start time of the target service to the 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 the charging function entity, so that the charging entity starts charging from the service start time carried in the charging start request when receiving the charging start request. For example, when the charging function entity charges through a bill, a bill corresponding to the target service is opened after receiving the charging start request, and charging in the bill starts from the service start time.

[0054] In step 250, the service end request is sent to the corresponding network slice, so that the charging function entity generates the charging information of the target service according to the charging end request 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 running traffic from the start to the end.

[0055] In the embodiment, when the target service receives the information triggered by the user that the target service is expected to end, the service request of the target service is determined as a service end request, and the user terminal sends the service end request carrying the service end time of the target service to the 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 the first service running traffic from the start to the end of the target service obtained by internal statistics, and sends the charging end request to the charging function entity, so that the charging function entity generates the charging information of the target service according to the service end time and the first service running traffic in the received charging end request and the service start time of the target service received in advance. For example, when the charging function entity charges through a bill, after receiving the charging end request, the running time of the service is determined according to the service start time and the service end time in the bill corresponding to the target service, the charging processing of the target service is performed according to the determined running time of the service and the received first service running traffic, and the bill corresponding to the target service is closed, which is equivalent to generating a bill corresponding to the running of the target service this time.

[0056] In an embodiment, before the service end request is sent to the corresponding network slice, the method further comprises:

[0057] sending a service update request to the corresponding network slice, so that if the charging function entity does not receive the charging end request or the charging update request generated by the network slice within the first preset time, the charging information of the target service is generated according to the last charging update request within the first preset time, and the charging update request is generated by the corresponding network slice according to the service update request, and the charging update request carries the service running time from the start to the current update and the second service running traffic.

[0058] wherein the first preset time can be set by those skilled in the art according to the actual situation, and the embodiment of the application does not limit this.

[0059] In this embodiment, after the service start request is sent to the corresponding network slice and before the service end request is sent to the corresponding network slice, it can be considered that the target service in the target application is being executed, and the parameters and other information in the target service can be adjusted during the execution process, and the user can also operate the target service to update it. At this time, the generated service request is a service update request, and 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, so that the network slice determines the charging update request containing the service running time and the second service running traffic of the target service from the start to the current update according to the update information and the time information in the service update request, and sends the charging update request to the charging function entity, so that the charging information of the target service in the charging function entity is updated. Moreover, if the charging function entity does not receive the charging end request or the charging update request generated by the network slice within the first preset time, it can be considered that the network has an error and cannot normally complete the charging. At this time, according to the service running time and the second service running traffic carried in the last charging update request within the first preset time, the charging information of the target service in the abnormal charging situation can be determined, so that the charging information of the target service will not be completely lost when the abnormal situation occurs.

[0060] In an embodiment, the service request, the charging request and the charging information all include the application identifier of the target application, the service identifier of the target service and the application session identifier. The application session identifier is used to indicate all sessions in the use process of the target application, i.e. from the service start request of the first target service in the target application to the service end request of the last target service in the target application. The corresponding application session identifier is consistent in this time period, and the 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 to form a complex charging information containing all the cost information in the application.

[0061] The service charging method provided by the embodiment makes the demand of different services in the target service provided by the most suitable network slice, so that the resource allocation of the network slice is more reasonable, and the service quality of the network to the target application is improved; the charging information corresponding to different target services is generated according to the different network slices corresponding to the target services, so that the charging of the complex application working cooperatively through multiple network slices is more accurate; and different charging requests are sent to the charging function entity according to different service requests, so that the charging function entity generates the charging information of the corresponding target service according to different charging requests, and settles the charging information of the target service according to the last received charging update request when no charging end request or charging update request is received within the first preset time, thereby reducing the charging loss under abnormal conditions.

[0062] Figure 3 The flowchart of another service charging method provided by an embodiment is shown in Figure 3 The service charging method provided by the embodiment is applied to a network slice, and the method comprises steps 310 and 320.

[0063] In step 310, the service request of the target service in the target application sent by the user terminal is received.

[0064] In the embodiment, the network slice corresponding to the target service receives the service request of the target service in the target application sent by the user terminal, wherein the service request can comprise a service start request, a service update request and a service end request.

[0065] In step 320, the 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 the charging information of the corresponding target service according to the charging request.

[0066] The network slice corresponding to different target services is different, and the demand of the target service corresponds to the network characteristics of the network slice.

[0067] In the embodiment, the network slice obtains the time information (such as the service start time, the service update time and the service end time) in the service request according to the received different service requests, generates the charging request corresponding to the service request by combining the time information in the service request and the flow information determined by the network slice itself, and sends the charging request to the charging function entity, so that the charging function entity generates the charging information corresponding to the target service according to the time and flow information carried in the charging request.

[0068] Further, in the service charging method, the service request, the charging request and the charging information all carry the application identifier of the target application, the service identifier of the target service and the application session identifier, so that the charging function entity generates the charging information of the corresponding session according to the service request of the first target service and the service request of the last target service of the same session.

[0069] The service charging method provided in the embodiment receives a service request of a target service in a target application sent by a user terminal, generates a corresponding charging request according to the service request, and sends 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. Different network slices correspond to different target services, 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 the 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 network slices with corresponding network characteristics according to different requirements to provide services, 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 request, so that the respective charging of different services in a complex application requiring different network slices to provide services can be realized, and the charging of the complex application is more accurate.

[0070] Figure 4 The flowchart of another service charging method provided in an embodiment is shown in FIG. 4, and the method includes steps 410 to 460. Figure 4

[0071] In step 410, the access and mobility management function entity of a preset network slice receives a registration request sent by a target application in a user terminal.

[0072] The network slice includes a preset network slice corresponding to a preset service in the target application.

[0073] In the embodiment, when the user terminal accesses the network, the access and mobility management function entity AMF of the preset network slice corresponding to the preset service in the target application in the user terminal in each network slice in the core network receives a registration request sent by the target application in the user terminal, and the registration request carries the requirements of each service in the target application.

[0074] In step 420, the network slice corresponding to other services in the target application is determined according to the correspondence between the requirements 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 services.

[0075] ​In the embodiment, since the demands of the services correspond to the network characteristics of the network slices, and the demands of the services in the target application are carried in the registration request received by the preset network slice, the network slice corresponding to each service can be determined according to the correspondence between the demands of the services and the network characteristics of the network slices, and the registration request is forwarded to the access and mobility management function entity of the network slice corresponding to the other service, so that each service in the target application completes registration on the corresponding network slice.

[0076] In step 430, a registration response including the correspondence between the demands of the services in the target application and the network characteristics of the network slices is sent to the target application, so that the other services in the target application determine the corresponding network slices according to the registration response.

[0077] In the embodiment, the preset network slice determines the correspondence between the demands of the services and the network characteristics of the network slices according to the demands of the services in the target application carried in the registration request, and sends the correspondence to the target application in the registration response, so that the other services in the target application except the preset service can determine the network slices corresponding to the services according to the correspondence in the registration response.

[0078] In step 440, a service request of a target service in the target application sent by a user terminal is received.

[0079] 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.

[0080] In the embodiment, the network slice receives the service start request of the target service corresponding thereto, 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.

[0081] 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 function entity, so that the charging function 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 traffic from the start to the end.

[0082] In the embodiment, the network slice receives a service end request of a target service corresponding to the network slice, internally counts a first service running traffic from the start to the end of the target service when receiving the service end request, generates a charging end request carrying the information of the service end time of the target service in the service end request and the first service running traffic according to the counted first service running traffic, and sends the charging end request to the charging function entity, so that the charging function entity determines the service running time according to the received service end time and the previously received service start time when receiving the charging end request, and generates the charging information of the target service according to the first service running traffic in the charging end request.

[0083] In an embodiment, the network slice can also receive a service update request after receiving the service start request and before receiving the service end request.

[0084] The charging update request is generated according to the service update request, and is sent to the charging function entity, so that if the charging function entity does not receive the charging end request or the charging update request within the first preset time, the charging information of the target service is generated according to the last charging update request within the first preset time, and the charging update request carries the service running time from the start to the current update and the second service running traffic.

[0085] In the embodiment, the target service corresponding to the network slice is considered to be in execution after receiving the service start request and before receiving the service end request, and should be charged. The service update request carrying the update information of the target service sent by the user terminal can be received in the service execution process. The service running time from the start to the current update and the second service running traffic of the target service running in the network slice from the start to the current update are determined according to the update information and time information carried in the service update request and the second service running traffic counted internally by the network slice. The service running time from the start to the current update and the second service running traffic are carried in the generated charging update request, and the 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. If the charging function entity does not receive the charging end request or the charging update request generated by the network slice within the first preset time, it is considered that the network has an error and cannot normally complete the charging. At this time, the charging information of the target service in the abnormal charging condition can be determined according to the service running time and the second service running traffic carried in the last charging update request within the first preset time, so that the charging information of the target service will not be completely lost when the abnormal condition occurs.

[0086] In an embodiment, if the network slice does not receive the service request sent by the user terminal within the second preset time after generating the 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 and sent to the charging function entity, so that if the charging function entity does not receive the charging end request or the charging update request within the first preset time, the charging information of the target service is generated according to the last charging update request within the first preset time, and the charging update request carries the service running time from the start to the current update and the third service running traffic.

[0087] In the embodiment, if the network slice exceeds the second preset time from generating the charging start request according to the received service start request and sending the charging start request to the charging function entity to receiving the next service request sent by the user terminal, a charging update request is generated after the second preset time after sending the charging start request to the charging function entity, the charging update request carries the service running time from the start to the current update and the third service running traffic, 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. If the charging function entity does not receive the charging end request or the charging update request generated by the network slice within the first preset time, it is considered that the network has an error and cannot normally complete the charging. At this time, the charging information of the target service in the abnormal charging condition can be determined according to the service running time and the third service running traffic carried in the last charging update request within the first preset time, so that the charging information of the target service is not completely lost when the abnormal condition occurs. The second preset time can be set by those skilled in the art according to the actual situation, and the second preset time should be less than the first preset time, and the embodiment of the application does not make specific limitation.

[0088] The service charging method provided by the embodiment receives a registration request sent by a target application of a user terminal through a preset network slice, determines a target application according to the requirements of each service in the target application in the registration request and the corresponding relationship between the requirements of the services and the network characteristics of the network slice, and carries the corresponding relationship between each service in the target application and the network slice in the registration response and sends the registration response back to the target application, so that the requirements of different services in the target service can be provided by the most suitable network slice. Different charging requests are generated according to the received different service requests and sent to a charging function entity, so that the charging function entity generates charging information of the corresponding target service according to the different charging requests, and automatically generates a charging update request and sends it to the charging function entity when no service request of the user terminal is received within a second preset time, to complete the charging update of the corresponding target service in the charging function entity, so that the charging function entity can settle the charging information of the target service according to the last received charging update request in an abnormal situation, and the regular update can retain the update result closest to the time when the abnormal situation occurs, reducing the charging loss of the operator in the abnormal situation.

[0089] Figure 5 The flowchart of another service charging method provided by an embodiment is shown in Figure 5 The service charging method provided by the embodiment is applied to a charging function entity, and the method comprises steps 510 and 520.

[0090] In step 510, a charging request sent by a network slice is received.

[0091] In the embodiment, the charging function entity receives the charging request sent by the network slice, the charging object corresponding to the charging request is a target application of a target service corresponding to the network slice, and the charging request can comprise a charging start request, a charging update request and a charging end request.

[0092] 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 charging information of the corresponding target service.

[0093] The network slice corresponding to different target services is different, and the requirements of the target service correspond to the network characteristics of the network slice.

[0094] In the embodiment, the charging function entity determines the running time and the running traffic of the target service corresponding to the network slice according to the received charging request, and generates the charging information of the target service according to the determined running time, running traffic, service start time and service end time of the target service contained in the received charging request.

[0095] Further, in the service charging method, the service request, the charging request and the charging information all carry the application identifier of the target application, the service identifier of the target service and the application session identifier, so that the charging function entity generates the charging information of the corresponding session according to the service request of the first target service and the service request of the last target service of the same session.

[0096] The service charging method provided by the embodiment comprises the following steps: receiving a charging request sent by a network slice; and 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 charging information corresponding to the target service; wherein the network slice corresponding to different target services is different, and the demand of the target service corresponds to the network characteristics of the network slice. The charging request generated by the network slice of the target service in the corresponding target application is received, and the charging information of the target service is generated according to the charging request, so that the charging function entity can charge different network slices respectively, and thus the respective charging of different services in a complex application which needs to be provided by different network slices can be realized, and the charging of the complex application is more accurate.

[0097] Figure 6 The flowchart of another service charging method provided by an embodiment is shown in FIG. 6, which comprises steps 610 to 640. Figure 6

[0098] In step 610, a charging request sent by a network slice is received.

[0099] In an embodiment, the charging request can comprise a charging start request and a charging end request.

[0100] In step 620, the service start time of the target service is determined according to the charging start request.

[0101] In the embodiment, the charging start request carries the service start time of the target service corresponding to the network slice, and the charging function entity starts charging the target service according to the service start time carried in the charging start request after receiving the charging start request.

[0102] In step 630, the service end time of the target service and the first service running traffic from the start to the end are determined according to the charging end request.

[0103] In the embodiment, the charging end request carries the service end time of the target service corresponding to the network slice and the first service running traffic of the target service obtained by the network slice, and the charging function entity reads the service end time and the first service running traffic from the charging end request and stops charging the target service when receiving the charging end request. ​

[0104] In step 640, the charging information of the target service is generated according to the service start time, the first service running traffic and the service end time.

[0105] 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, the received first service running traffic and the pre-designed charging rule.

[0106] In an embodiment, after receiving the charging start request, the charging function entity can further receive a charging update request sent by the network slice before receiving the charging end request.

[0107] According to the charging update request, the service running time of the target service from the start to the current update and the second service running traffic or the third service running traffic are determined.

[0108] In this embodiment, if the charging update request is generated by the network slice according to the received service update request, the service running 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 running traffic carried is the second service running traffic; if the charging update request is generated by the network slice within the second preset time after the reception of the service start request without receiving the service request, the service running time from the start to the current update carried in the charging update request is the second preset time from the start to the reception of the last service request by the network slice, and the running traffic carried is the third service running traffic.

[0109] If the charging end request or the charging update request sent by the network slice is not received within the first preset time, the charging information of the target service is generated according to the service running time from the start to the current update of the target service carried in the last charging update request within the first preset time, and the second service running traffic or the third service running traffic.

[0110] In this embodiment, if the billing function entity does not receive a billing end request or billing update request generated by the network slice within a first preset time, it can be considered that a network error has occurred and billing cannot be completed normally. At this time, the billing information of the target service is generated based on the last billing update request within the first preset time. If the billing update request is generated by the network slice based on the received service update request, the billing information of the target service under this abnormal billing situation is determined based on the service running time from the start to the current update carried therein, which is the time from the start to the receipt of the service update request, and the second service running traffic. If the billing update request is generated by the network slice after receiving the service start request and not receiving the service request within a second preset time, the billing information of the target service under this abnormal billing situation is determined based on the second preset time from the start to the network slice after receiving the previous service request, and the third service running traffic carried therein.

[0111] The service billing method provided in this embodiment generates billing information for the target service of the corresponding network slice based on the received billing start request and billing end request. When a billing update request is received, the billing information of the target service is updated. In case of an anomaly, the billing information of the target service is confirmed based on the most recently received billing update request. This enables separate billing for different services in complex applications that require services from different network slices to provide services simultaneously. It also enables the billing function entity to settle the billing information of the target service based on the most recently received billing update request in case of an anomaly. The timed update can retain the update result most recent to the time of the anomaly, reducing the operator's billing losses in case of anomalies.

[0112] Figure 7 A schematic diagram of the structure of a communication device is provided as an embodiment, such as... Figure 7 As shown, the device includes a processor 710, a storage device 720, an input device 730, and an output device 740; the number of processors 710 in the device can be one or more. Figure 7 Taking a processor 710 as an example; the processor 710, storage device 720, input device 730, and output device 740 in the device can be connected via a bus or other means. Figure 7 Taking the example of a connection between China and Israel via a bus.

[0113] Storage device 720, as a computer-readable storage medium, can be used to store software programs, computer-executable programs, and modules, such as the program instructions / modules corresponding to the service billing method in the embodiments of this application. Processor 710 executes various functional applications and data processing of the device by running the software programs, instructions, and modules stored in storage device 720, thereby implementing the aforementioned service billing method.

[0114] The storage 720 can include a program storage area that can store an operating system, applications required for at least one function, and a data storage area that can store data created according to use of the terminal, etc. In addition, the storage 720 can include a high-speed random access memory, and can further include a non-volatile memory such as at least one of a magnetic disk storage device, a flash memory device, or other non-volatile solid state storage device. In some examples, the storage 720 can further include a memory disposed remotely with respect to the processor 710, which can be connected to the communication device through a network. Examples of the above network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and a combination thereof.

[0115] The input device 730 can be used to receive input digital or character information, and to generate signal input related to user settings and function controls of the device, and can include a touch screen, a keyboard, a mouse, etc. The output device 740 can include a display device such as a display screen, etc.

[0116] The embodiments of the present application also provide a storage medium containing computer executable instructions, which, when executed by a computer processor, are used to perform a service charging method.

[0117] From the above description of the embodiments, those skilled in the art can understand that the present application can be implemented by means of software and general hardware, or by hardware. Based on such understanding, the technical solutions of the present application can be embodied in the form of a software product. The computer software product can be stored in a computer readable storage medium, such as a floppy disk, a ROM, a RAM, a FLASH memory, a hard disk, or an optical disk, and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in any of the embodiments of the present application.

[0118] The above description is only exemplary embodiments of the present application, and is not intended to limit the protection scope of the present application.

[0119] The block diagrams of any logical flow of the present application in the drawings can represent program steps or can represent interconnected logic circuits, modules, and functions, or can represent a combination of program steps and logic circuits, modules, and functions. The computer program can be stored on a memory. The memory can be of any type suitable to the local technical environment and can be implemented using any suitable data storage technology, such as, but not limited to, random access memory (RAM), read only memory (ROM), optical storage devices, and systems, such as digital versatile disc (DVD) or CD-ROM, and the like. The computer readable media can include non-transitory storage media. The data processor can be of any type suitable to the local technical environment, and can include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), application specific integrated circuits (ASIC), programmable logic devices (PLD), and processors based on multi-core processor architectures, as examples.

[0120] A detailed description of exemplary embodiments of the application has been provided above with reference to the drawings. Numerous modifications and adjustments to the above embodiments will be apparent to those skilled in the art in view of the foregoing description, without departing from the scope of the application. Accordingly, the proper scope of the application is to be determined by the claims.

Claims

1. A service charging method characterized by, Applied to a user terminal, comprising: Obtaining a service request of a target service in a target application; Send the service request 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; Wherein, the network slice corresponding to different target services is different, and the demand of the target service corresponds to the network characteristics of the network slice; Send the service request 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, comprising: Send the service start request to the corresponding network slice, so that the charging function entity starts charging according to the charging start request, and 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; Send the service end request to the corresponding network slice, so that the charging function entity generates the charging information of the target service according to the charging end request, and 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 and the first service running traffic from the start to the end of the target service; After sending the service start request to the corresponding network slice, before sending the service end request to the corresponding network slice, send the service update request to the corresponding network slice, so that if the charging function entity does not receive the charging end request or the charging update request generated by the network slice within the first preset time, the charging information of the target service is generated according to the last charging update request within the first preset time, and the charging update request is generated by the corresponding network slice according to the service update request, and the charging update request carries the service running time from the start to the current update and the second service running traffic.

2. The method of claim 1, wherein, Before the obtaining of the service request of the target service in the target application, further comprising: Obtaining the preset network slice corresponding to the preset service in the target application, and sending a registration request to the access and mobility management function entity of the preset network slice; Receive the registration response of the access and mobility management function entity, and determine the network slice corresponding to other services in the target application according to the registration response; Wherein, the registration response includes the corresponding relationship between the demand of each service in the target application and the network characteristics of the network slice.

3. The method according to any of claims 1-2, characterized by, The service request, the charging request and the charging information carry the application identifier of the target application and the service identifier of the target service.

4. The method of any of claim 3, wherein, The service request, the charging request and the charging information further include an application session identifier, so that the charging function entity generates charging information corresponding to the same session according to the service request of the first target service and the service request of the last target service.

5. A service charging method characterized by, Applied to a network slice, comprising: Receive the service request of the target service in the target application sent by the 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; wherein different target services correspond to different network slices, and the requirement of the target service corresponds to network characteristics of the network slice; 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 comprises: 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, the charging start request carrying a service start time of the target service; generating a charging end request according to the service end request, and sending the charging end request to the charging function entity, so that the charging function entity generates charging information of the target service according to the charging end request, the charging end request carrying a service end time of the target service and a first service running traffic from the start to the end; generating a charging update request according to the service update request, and sending the charging update request 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, the charging information of the target service is generated according to the last charging update request within the first preset time, the charging update request carrying a service running time from the start to the current update and a second service running traffic.

6. The method of claim 5, wherein, the network slice comprises a preset network slice corresponding to a preset service in a target application, and before the receiving the service request of the target service in the target application sent by the user terminal, the method further comprises: an access and mobility management function entity of the preset network slice receives a registration request sent by the target application in the user terminal; determining a network slice corresponding to other services in the target application according to a corresponding relationship between the requirement of each service in the target application and network characteristics of the network slice, and forwarding a registration request to an access and mobility management function entity of the network slice corresponding to the other services; sending a registration response comprising the corresponding relationship between the requirement of each service in the target application and network characteristics of the network slice to the target application, so that the other services in the target application determine the corresponding network slice according to the registration response.

7. The method of claim 5, wherein, after the 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: If the service request sent by the user terminal is not received within the second preset time, 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 the first preset time, charging information of the target service is generated according to the last charging update request within the first preset time, and the charging update request carries service running time from the start to the current update and third service running traffic.

8. The method according to any of claims 5-7, characterized by, 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.

9. The method of any of claim 8, wherein, The service request, the charging request and the charging information further include an application session identifier, so that the charging function entity generates charging information of a corresponding session according to a service request of a first target service and a service request of a last target service in the same session.

10. A service charging method characterized by, Applied to a charging function entity, comprising: receiving a charging request sent by a network slice; generating charging information according to the charging request, the charging request being generated by the network slice according to a service request of a target service in a corresponding target application, and the charging information being charging information corresponding to the target service; wherein different network slices correspond to different target services, and requirements of the target service correspond to network characteristics of the network slice; The charging request includes a charging start request and a charging end request; and the generating of the charging information according to the charging request comprises: determining a service start time of the target service according to the charging start request; determining a service end time of the target service and first service running traffic from the start to the end according to the charging end request; generating charging information of the target service according to the service start time, the first service running traffic and the service end time; determining service running time of the target service from the start to the current update and second service running traffic or third service running traffic according to the charging update request; if the charging end request or the charging update 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 of the target service from the start to the current update and the second service running traffic or the third service running traffic carried in the last charging update request within the first preset time.

11. The method of any of claim 10, 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.

12. The method of any of claim 11, wherein, The service request, the charging request and the charging information further include an application session identifier, so that the charging function entity generates charging information of a corresponding session according to a service request of a first target service and a service request of a last target service in the same session.

13. A communication device, characterized by comprising: one or more processors; a storage device configured 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 implement the business charging method as claimed in any one of claims 1-4 or 5-9 or 10-12.

14. A storage medium of computer executable instructions, characterized in that, The computer executable instructions, when executed by a computer processor, perform the business charging method as claimed in any one of claims 1-4 or 5-9 or 10-12.

Images