[go: up one dir, main page]

WO2022062778A1 - Procédé de modulation de données, dispositif de communication et support de stockage - Google Patents

Procédé de modulation de données, dispositif de communication et support de stockage Download PDF

Info

Publication number
WO2022062778A1
WO2022062778A1 PCT/CN2021/113303 CN2021113303W WO2022062778A1 WO 2022062778 A1 WO2022062778 A1 WO 2022062778A1 CN 2021113303 W CN2021113303 W CN 2021113303W WO 2022062778 A1 WO2022062778 A1 WO 2022062778A1
Authority
WO
WIPO (PCT)
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.)
Ceased
Application number
PCT/CN2021/113303
Other languages
English (en)
Chinese (zh)
Inventor
骆旭剑
王修中
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
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
Publication of WO2022062778A1 publication Critical patent/WO2022062778A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • 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

Definitions

  • the present application relates to the field of communication technologies, and in particular, to a service charging method, a communication device and a storage medium.
  • 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 (massive Machine Type). Communication, mMTC), etc. These scenarios have very different requirements for network characteristics.
  • the physical network can be divided at the end-to-end level to form a network slice (Network Slice).
  • Network Slice In some applications, according to the idea of dedicated network slicing, all services in the application are implemented through a network slicing, so as to improve the utilization rate of network resources and the service quality of network services.
  • 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 result in wasted resources and reduced network service quality.
  • the embodiment of the present application provides a service charging method, which is applied to a user terminal, including: acquiring 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 can perform the charging request according to the charging request.
  • the charging information corresponding to the target service is generated, 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.
  • An embodiment of the present application provides a service charging method, which is applied to network slicing, including: 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 the 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 requirements of the target service correspond to the network characteristics of the network slice.
  • the embodiment of the present application provides a service charging method, which is applied to a charging functional entity, including: receiving a charging request sent by a network slice; generating charging information according to the charging request, and the charging request is performed by the network slice according to a corresponding target
  • the service request of the target service in the application is generated, and the charging information is the charging information corresponding to the target service; wherein, different target services correspond to different network slices, and the requirements of the target service correspond to the network characteristics of the network slice.
  • An embodiment of the present application provides a communication device, including: 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, one or more A plurality of processors implement the above-mentioned service charging method.
  • Embodiments of the present application further provide a storage medium for computer-executable instructions, where the computer-executable instructions are used to execute the foregoing service charging method when executed by a computer processor.
  • FIG. 1 is a flowchart 1 of a service charging method applied to a user terminal provided by an embodiment
  • FIG. 2 is a second flowchart of a service charging method applied to a user terminal provided by an embodiment
  • FIG. 3 is a flowchart 1 of a service charging method applied to network slicing provided by an embodiment
  • FIG. 4 is a second flowchart of a service charging method applied to network slicing provided by an embodiment
  • FIG. 5 is a flowchart 1 of a service charging method applied to a charging functional entity provided by an embodiment
  • FIG. 6 is a second flowchart of a service charging method applied to a charging functional entity provided by an embodiment
  • FIG. 7 is a schematic structural diagram of a communication device according to an embodiment.
  • the present application provides a service charging method, a communication device and a storage medium, so as to realize the synergistic effect of multiple network slices in complex applications and the charging of various services in complex applications.
  • various services in the application are often implemented through a network slice, so as to provide the most suitable network environment for the main services in the application according to the idea of dedicated to the dedicated network of network slices. It is often a complex application that needs to perform compound work in multiple application scenarios. Therefore, using only one network slice to provide services for complex applications will make it difficult for some of these services to work in a network environment that suits their needs. The corresponding network characteristics make it suitable for all requirements in complex applications, which will result in a large waste of resources.
  • the service charging method in this embodiment allocates different network slices to provide services for different target services according to the requirements of the target service and the network characteristics of the network slice, and charges the target services corresponding to each network slice through the charging functional entity , to provide decision-making basis for improving the service quality of complex applications and improving the charging accuracy of complex applications.
  • the service request of the target service in the target application is obtained; the service request is sent 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 processed by the corresponding network slice.
  • the network slice is generated according to the service request; wherein, different target services correspond to different network slices, and the requirements of the target service correspond to the network characteristics of the network slice. According to the corresponding application scenarios of different target services in the target application, the requirements are very different, and network slices corresponding to network characteristics are allocated to them, so that the functions required by the target services can be provided by the corresponding network slices and billed.
  • the functional entity generates charging information corresponding to the target service according to the charging requests sent by different network slices, so that the functions of each service in the complex application can be provided collaboratively through multiple network slices, and each service in the complex application can be charged separately . It solves the problem that when only one network slice is used to provide resources and services for complex applications, it cannot provide the most suitable resources for each business in complex applications, reduces waste of resources and improves the quality of network services, while making complex applications billing more accurate.
  • FIG. 1 is a flowchart of a service charging method provided by an embodiment. As shown in FIG. 1 , the service charging method provided by this embodiment is applied to a user terminal, and the method includes step 110 and step 120 .
  • step 110 the service request of the target service in the target application is obtained.
  • a user terminal can be understood as an interactive device between a site and a user, and is often a general-purpose computer input and output device with a communication processing control function.
  • the target application can be understood as software installed in the user terminal that can provide users with multiple functions and services, that is, a collection of computer data and instructions organized in a specific order, wherein the target application may include multiple implementations. Different functions of business.
  • the target service can be understood as a function that can be provided in the target application, and can also be a function that can be provided by a sub-service of a certain service in the target application, such as automatic driving function, driving record function, etc. Different requirements have different applicable application scenarios, which in turn lead to very different requirements for network characteristics in application scenarios.
  • the service request can be understood as service requirement information generated by the user in the user terminal for the target service operation.
  • the user's operation information is received at the user terminal, the application used by the user through the user terminal is determined according to the operation information, the application is determined as the target application, the function that the user wants the target application to realize is determined according to the operation information, and then the application is determined according to the operation information.
  • the function that the target application is expected to implement determines the target service that can provide the function in the target application, and determines what operation the user wants to perform on the target service (such as starting a service, updating service parameters, ending a service, etc.) according to the operation information, so that the user terminal can generate
  • the service request may at least include 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 from an external device, or a voice input such as voice, which is not limited in this embodiment of the present application.
  • 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.
  • a network slice can be understood as a method of on-demand networking.
  • the charging function entity (Charging Function, CHF) can be understood as a functional entity in the online charging system (Online Charging System, OCS) component in the telecommunication network, which is specifically used for the collection, formatting, Transfer and evaluation for offline billing and online billing functionality.
  • CHF Charge Function
  • OCS Online Charging System
  • the online charging system OCS can be understood as a charging system that participates in the control of the communication process, and is the integration of the online charging system, which can solve the problems of real-time credit control of users, prepaid use of data services, and real-time charging of value-added services.
  • eMBB enhanced Mobile Broadband, enhanced mobile broadband
  • uRLLC ultra High-Reliability and Low-Latency Communication, ultra-high reliability and low latency communication
  • mMTC massive Machine Type Communication, large connection machine type communication
  • the throughput of each device may be very low and the required bandwidth is very small; while in the eMBB scenario, only Fewer terminal devices need to be accessed, but each terminal device will send and receive a large amount of data, and the required bandwidth is large; in the uRLLC scenario, the end-to-end delay is very high and requires a small delay.
  • Application scenarios should select network slices with different network characteristics to provide services for them. Different target services can correspond to the above different application scenarios.
  • the automatic driving service in the vehicle driving application mainly corresponds to the uRLLC scenario, which requires the delay in information transmission to be less than 3 milliseconds.
  • the eMBB scenario it does not have high requirements on latency, but has certain requirements on bandwidth and storage. Therefore, for different services in the same application, different networks should be configured for them according to the different requirements of the services. Featured network slices.
  • a corresponding network slice with corresponding network characteristics is determined according to different requirements of the target service, and the user terminal sends the acquired service requirements of the target service to the corresponding network slice, so that the network slice can be based on the received service requirements.
  • a service request generating a corresponding charging request containing the information for charging such as the time and flow that match the target service operation in the service request, and sending the charging request to the charging function entity, so that the accounting
  • the charging function entity can generate charging information corresponding to the target service according to information such as time and traffic carried in the charging request.
  • the billing information can be represented by a bill, wherein the bill can be understood as the original communication record information in the communication field, which can also be referred to as a call detail record (CDR).
  • CDR call detail record
  • the service request, the charging request and the charging information all carry the application identifier of the target application, the application identifier of the target service and the application session identifier, so that the charging function entity can first use the same session as the first indicator.
  • the service requests of each target service and the service request of the last target service generate charging information for the corresponding session.
  • the service request of the target service in the target application is obtained; the service request is sent to the corresponding network slice, so that the charging function entity generates a corresponding target service according to the charging request.
  • the charging information of the service, 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 services correspond to the network characteristics of the network slice.
  • the requirements are very different, and network slices corresponding to network characteristics are allocated to them, so that the functions required by the target services can be provided by the corresponding network slices and billed.
  • the functional entity generates charging information corresponding to the target service according to the charging requests sent by different network slices, so that the functions of each service in the complex application can be provided collaboratively through multiple network slices, and each service in the complex application can be charged separately . It solves the problem that when only one network slice is used to provide resources and services for complex applications, it cannot provide the most suitable resources for each business in complex applications, reduces waste of resources and improves the quality of network services, while making complex applications billing more accurate.
  • FIG. 2 is a flowchart of another service charging method provided by an embodiment. As shown in FIG. 2 , the method includes steps 210 to 250 .
  • step 210 a preset network slice corresponding to the preset service in the target application is acquired, and a registration request is sent to the access and mobility management functional entity of the preset network slice.
  • the preset service can be understood as a service function determined according to preset rules in the target application, which can be determined according to the main realization function of the target application, and the corresponding network can be determined in advance according to the requirements of the preset service. slice, and use the network slice as the preset network slice corresponding to the preset service.
  • the Access and Mobility Management Function can be understood as a functional entity for receiving all connection and session related information of the user terminal and processing connection and mobility management tasks.
  • the target application in the user terminal can determine the corresponding preset network slice according to the preset service therein, and report to the access and mobility function management entity in the preset network slice AMF sends a registration request.
  • the registration request carries the requirements 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 requirements of each service in the registration request, and forward the registration request to the connection of the corresponding network slice.
  • Access and mobility function management entity AMF to complete the registration of the corresponding services in the target application on different network slices.
  • step 220 a registration response from the access and mobility management functional entity is received, and network slices corresponding to other services in the target application are determined according to the registration response.
  • the registration response includes the corresponding relationship between the requirements of each service in the target application and the network characteristics of the network slice.
  • 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 according to the requirements of each service in the target application and the network characteristics of the network slice included in the registration response The corresponding relationship is determined, and network slices corresponding to other services in the target application except the preset services are determined.
  • the corresponding relationship between each service in the target application and the network slice can be used as a network slice selection policy (Network Slice Selection Policy, NSSP), and stored in the network slice selection module in the user terminal, so that in the actual application process, it can be used.
  • NSSP Network Slice Selection Policy
  • the corresponding network slice is matched for the target service through the routing method in time.
  • the service request of the target service in the target application is obtained.
  • the service request of the target service may include: a service start request, a service update request and a service end request.
  • 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, 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 business start time of the target business.
  • the target service in the target application receives the user's operation on it, and determines the type of service request according to the actual operation.
  • the generated service request is a service start request
  • the user terminal Send 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 network slice.
  • the charging function entity enables the charging entity to start charging with the service start time carried in the charging start request as the start time after receiving the charging start request.
  • the charging function entity performs charging through the bill, after receiving the charging start request, it opens a bill corresponding to the target service, and starts charging in the bill with the service start time as the starting time.
  • step 250 the service end request is sent to the corresponding network slice, so that the charging function entity generates 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,
  • the charging end request carries the service end time of the target service and the running flow of the first service from start to end.
  • the service request of the target service is determined as the service end request, and the user terminal sends the service end request carrying the service end time of the target service to the target service.
  • the network slice corresponding to the 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 of the target service obtained from its internal statistics from the start to the end, and sends the charging end request to the 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 running flow in the received charging end request, and the service start time of the target service received in advance .
  • the charging function entity when the charging function entity performs charging through the bill, after receiving the billing end request, it determines the running time of the service in the bill corresponding to the target service according to the service start time and the service end time, and according to the determined The running time of the service and the received first service running traffic are used for charging processing of the target service, and the bill corresponding to the target service is closed, which is equivalent to generating a bill corresponding to the current operation of the target service.
  • the method further includes:
  • the last charging update request generates the charging information of the target service.
  • the charging information update request is generated by the corresponding network slice according to the service update request.
  • the charging update request carries the service running time from the start to the current update and the second service running time. flow.
  • the first preset time can be set by those skilled in the art according to actual conditions, which is not limited in this embodiment of the present application.
  • 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. Such information may be adjusted, and the user can also operate the target service to update it.
  • the service request generated at this time is a service update request, and the user terminal sends the service update request carrying the update information of the target service to the corresponding target service.
  • the network slice so that the network slice determines the charging update request including the service running time from the start to the current update of the target service and the running flow of the second service according to the update information and time information in the service update request, and updates the charging
  • the request is sent to the charging function entity, so that the charging function entity correspondingly updates the charging information of the target service.
  • 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 may be considered that there is an error in the network and it is difficult to complete the charging normally.
  • the service running time and the second service running flow carried in the last charging update request in the past can be used to determine the charging information of the target service in this abnormal charging situation, so that the charging of the target service when the abnormal situation occurs Information is not completely lost.
  • the application session identifier is used to indicate that the target application is used once. All sessions in the target application, that is, 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 service, the corresponding application session marks in this time period are consistent, and can be based on the same application
  • the session identifier and the same application identifier combine the charging information corresponding to each service request in the target application in the same time period to form a complex charging information including all the fee information in the application.
  • the service charging method by allocating different network slices for each service in the target application during registration, the requirements of different services in the target service can be provided by the most suitable network slice, so that the resource allocation of the network slice can be achieved. It is more reasonable and improves the service quality of the network for the target application; according to the different network slices corresponding to the target service, the charging information corresponding to different target services is generated, so that the charging of complex applications working together through multiple network slices is more accurate; Send different charging requests to the charging functional entity according to different service requests, so that the charging functional entity generates charging information corresponding to the target service according to the different charging requests, and no charging is received within the first preset time. When an end request or a charging update request is received, the charging information of the target service is settled according to the charging update request received last time, thereby reducing the charging loss in an abnormal situation.
  • FIG. 3 is a flowchart of another service charging method provided by an embodiment. As shown in FIG. 3 , the service charging method provided by this embodiment is applied to network slicing, and the method includes steps 310 and 320 .
  • step 310 a service request of the target service in the target application sent by the user terminal is received.
  • 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, where the service request may include a service start request, a service update request and a service end request.
  • 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.
  • 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 service requests received, and combines the time information in the service request with the time information in the network slice itself.
  • Determine the flow information generate a charging request corresponding to the service request, and send the charging request to the charging function entity, so that the charging function entity generates a corresponding target service according to the time and flow information carried in the charging request. billing information.
  • 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 can firstly identify the target application according to the same session.
  • the service requests of each target service and the service request of the last target service generate charging information for the corresponding session.
  • a service request of a target service in a target application sent by a user terminal is received; a corresponding charging request is generated according to the service request, and the charging request is sent 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 requirements of the target services are related to the network characteristics of the network slice. correspond.
  • 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 according to different requirements.
  • the corresponding network slice generates a corresponding charging request according to the service request and sends it to the charging function entity, so that the charging function entity can generate the charging information corresponding to the target service according to the charging request, which makes it complicated to provide services at the same time when different network slices are required. Separate billing for different services is implemented in the application, which makes the billing of complex applications more accurate.
  • FIG. 4 is a flowchart of another service charging method provided by an embodiment. As shown in FIG. 4 , the method includes steps 410 to 460 .
  • step 410 the access and mobility management function entity of the preset network slice receives the registration request sent by the target application in the user terminal.
  • the network slice includes a preset network slice corresponding to a preset service in the target application.
  • each network slice in the core network corresponds to the preset service in the target application of the user terminal, and the access and mobility management function entity AMF of the preset network slice will receive the information from the user terminal.
  • the registration request sent by the target application the registration request carries the requirements of each service in the target application.
  • the network slice corresponding to other services in the target application is determined according to the corresponding relationship between the requirements of each service in the target application and the network characteristics of the network slice, and forwarded to the access and mobility management function entities of the network slice corresponding to the other services Registration request.
  • the network slicing network since the service requirements correspond to the network characteristics of the network slice, and it is preset that the registration request received by the network slice carries the requirements of each service in the target application, the network slicing network The corresponding relationship between the characteristics, determine the corresponding network slice with corresponding network characteristics for each service, and forward the registration request to the access and mobility management function entities of the network slice corresponding to other services, so that each service in the target application can be Complete the registration on its corresponding network slice.
  • step 430 the registration response including the 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.
  • the preset network slice determines the corresponding relationship between the requirements of each service and the network characteristics of the network slice according to the requirements of each service in the target application carried in the registration request, and carries the corresponding relationship in the registration response to send to the target application, so that other services in the target application except the preset services can determine the network slice corresponding to each service according to the corresponding relationship in the registration response.
  • step 440 the service request of the target service in the target application sent by the user terminal is received.
  • 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 target service business start time.
  • the network slice receives the service start request of the corresponding target service, 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 converts the charging start request to the It is sent to the charging function entity, so that when the charging function entity receives the charging start request, it starts charging according to the service start time in the charging start request.
  • 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 ends
  • the request carries the service end time of the target service and the running flow of the first service from start to end.
  • the network slice receives the service end request of the target service corresponding to it, and when receiving the service end request, the first service running traffic of the target service from start to end is obtained by internal statistics, according to the target service carried in the service end request.
  • the end time of the service and the first service running flow obtained by statistics generate a charging end request carrying the above information, and send the charging end request to the charging function entity, so that the charging function entity receives the end of charging
  • the service running time is determined according to the received service end time and the previously received service start time, and charging information corresponding to the target service is generated according to the first service running flow in the charging end request.
  • the network slice may also receive a service update request.
  • the charging function entity Generate a charging update request according to the service update request, and send the charging update request 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, Then, 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 flow.
  • the service start request after the service start request is received and before the service end request is received, it may be considered that the target service corresponding to the network slice is being executed, and charging should be performed for it.
  • the service update request carrying the update information of the target service, according to the update information and time information carried in the service update request, to determine the service running time from the start to the current update, and the internal statistics of the network slice from the start to the current target.
  • the second service running traffic of the service running in 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 is updated correspondingly in the charging function entity.
  • 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 may be considered that there is an error in the network and it is difficult to complete the charging normally.
  • the service running time and the second service running flow carried in the last charging update request in the past can be used to determine the charging information of the target service in this abnormal charging situation, so that the charging of the target service when the abnormal situation occurs Information is not completely lost.
  • the network slice if the service request sent by the user terminal is not received within a second preset time after the network slice generates the charging start request according to the service start request and sends the charging start request to the charging function entity, Then generate a charging update request, and send the charging update request 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, it will The last charging update request within a preset time generates charging information of the target service, and the charging update request carries the service running time from the start to the current update and the third service running flow.
  • the network slicing if the network slicing generates a charging start request according to the received service start request and sends it to the charging function entity, if the time before receiving the next service request sent from the user terminal exceeds the second preset time time, the charging update request is generated after the second preset time after the charging start request is sent to the charging function entity, and the charging update request carries the current update from the start to the time when the charging update request is generated the service running time and the third service running flow, and send the generated charging update request to the charging function entity, so that the charging function entity can update the charging information of the target service correspondingly.
  • 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 may be considered that there is an error in the network and it is difficult to complete the charging normally.
  • the service running time and the third service running flow carried in the last charging update request in the past can be used to determine the charging information of the target service in this abnormal charging situation, so that the target service can be charged when the abnormal situation occurs. Information is not completely lost.
  • the second preset time can be set by those skilled in the art according to actual conditions, and the second preset time should be smaller than the first preset time, which is not specifically limited in this embodiment of the present application.
  • a registration request sent by a target application of a user terminal is received by a preset network slice, according to the requirements of each service in the target application in the registration request, and the relationship between the service requirements and the network characteristics of the network slice.
  • Corresponding relationship, including the corresponding relationship between each service in the target application and the network slice is determined, and it is carried in the registration response and sent back to the target application, so that the needs 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 the charging functional entity, so that the charging functional entity generates charging information corresponding to the target service according to the different charging requests, and the charging information is generated within a second preset time for a period of time.
  • the charging update request is automatically generated and sent to the charging function entity to complete the charging update corresponding to the target service in the charging function entity, so that in an abnormal situation, the charging function entity can
  • the received charging update request settles the charging information of the target service, and the regular update can retain the update result closest to the time when the abnormal situation occurs, thereby reducing the operator's charging loss in the abnormal situation.
  • FIG. 5 is a flowchart of another service charging method provided by an embodiment. As shown in FIG. 5 , the service charging method provided by this embodiment is applied to a charging function entity, and the method includes step 510 and step 520 .
  • step 510 a charging request sent by the network slice is received.
  • the charging function entity receives the charging request sent by the network slice, the charging object corresponding to the charging request is the target application of the target service corresponding to the network slice, and the charging request may include charging Start Request, Accounting Update Request, and Accounting End Request.
  • step 520 the 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 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 function entity determines the running time and running flow of the target service corresponding to the network slice according to the received charging request, and determines the running time and running flow according to the determined running time, running flow and the received charging request.
  • the service start time and service end time of the target service are integrated to generate the charging information of the target service.
  • 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 can firstly identify the target application according to the same session.
  • the service request of the target service and the service request of the last target service generate charging information for the corresponding session.
  • a charging request sent by a network slice is received; charging information is generated according to the charging request, and the charging request is performed by the network slice according to the corresponding target service in the target application.
  • a service request is generated, and the charging information is charging information corresponding to the target service; wherein, different target services correspond to different network slices, and the requirements of the target services correspond to the network characteristics of the network slices.
  • Receive the charging request generated by the network slice corresponding to the target service in the target application and generate the charging information corresponding to the target service according to the charging request, so that the charging function entity can charge different network slices separately, so that different requirements are required at the same time.
  • different services can be billed separately, making the billing of complex applications more accurate.
  • FIG. 6 is a flowchart of another service charging method provided by an embodiment. As shown in FIG. 6 , the method includes steps 610 to 640 .
  • step 610 a charging request sent by the network slice is received.
  • the charging request may include a charging start request and a charging end request.
  • step 620 the service start time of the target service is determined according to the charging start request.
  • the charging start request carries the service start time of the target service corresponding to the network slice.
  • the charging function entity uses the service start time carried in the charging start request to Business starts billing.
  • step 630 the service end time of the target service and the running flow of the first service from start to end are determined according to the charging end request.
  • the end-of-charge request carries the service end time of the target service corresponding to the network slice, and the first service running traffic obtained by statistics of the target service in the network slice. Read the end time of the service and the running flow of the first service, and stop charging for the target service when receiving the charging end request.
  • step 640 the charging information of the target service is generated according to the service start time, the first service running flow and the service end time.
  • the service operation time of the target service is determined according to the received service start time and service end time, and the target service is generated according to the determined service operation time and the received first service operation flow in combination with preset charging rules. billing information.
  • the charging function entity may further receive a charging update request sent by the network slice.
  • the service running time of the target service from the start to the current update and the second service running flow or the third service running flow are determined according to the charging 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 receipt of the service update request. time, the running traffic carried is the running traffic of the second service; if the charging update request is a charging update request generated by the network slice not receiving the service request within the second preset time after receiving the service start request, the The service running time from the start to the current update carried in the fee update request is the second preset time from the start to the network slice since the last service request is received, and the running traffic carried is the third service running traffic.
  • the charging end request or the charging update request sent by the network slice is not received within the first preset time, according to the The updated service running time and the second service running traffic or the service running traffic generate charging information of the target service.
  • 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 may be considered that there is an error in the network and it is difficult to complete the charging normally.
  • the charging information of the target service is generated from the last charging update request within the preset time. 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 generated according to the network slice.
  • the service charging method provided in this embodiment generates charging information of the target service corresponding to the network slice according to the received charging start request and charging end request, and when the charging update request is received, the charging information of the target service is Update, and confirm the charging information of the target service according to the recently received charging update request in the event of an abnormality. It is realized that the charging function entity settles the charging information of the target service according to the latest charging update request received in an abnormal situation, and the regular update can keep the update results closest to the time when the abnormal situation occurs, reducing the operation in abnormal situations. billing losses for the merchant.
  • FIG. 7 is a schematic structural diagram of a communication device according to an embodiment.
  • 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 may be One or more, a 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 in the device can be connected by a bus or in other ways. In FIG. 7, the connection by the bus is example.
  • the storage device 720 may be used to store software programs, computer-executable programs, and modules, such as program instructions/modules corresponding to the service charging method in the embodiments of the present application.
  • the processor 710 executes various functional applications and data processing of the device by running the software programs, instructions and modules stored in the storage device 720 , that is, to implement the above-mentioned service charging method.
  • 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, storage device 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, storage device 720 may further include memory located remotely from processor 710, which may be connected to the communication device through a network. Examples of such networks include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.
  • the input device 730 can be used to receive input numerical or character information, and generate signal input related to user settings and function control of the device, and can 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 further provide a storage medium containing computer-executable instructions, where the computer-executable instructions are used to execute a service charging method when executed by a computer processor.
  • the present application can be implemented by means of software and general hardware, and can also be implemented by hardware. Based on this understanding, the technical solution of the present application can be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, such as a floppy disk of a computer, a read-only memory (Read-Only Memory, ROM), Random access memory (Random Access Memory, RAM), flash memory (FLASH), hard disk or optical disk, etc., including multiple instructions to enable a computer device (which may be a personal computer, server, or network device, etc.) to execute any methods described in the examples.
  • a computer-readable storage medium such as a floppy disk of a computer, a read-only memory (Read-Only Memory, ROM), Random access memory (Random Access Memory, RAM), flash memory (FLASH), hard disk or optical disk, etc.
  • the block diagrams of any logic flow in the figures of the present 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.
  • Computer programs can be stored on memory.
  • the memory may be of any type suitable for 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 memory devices and systems (Digital Versatile Discs). DVD or CD disc) etc.
  • Computer-readable media may include non-transitory storage media.
  • the data processor may be of any type suitable for the local technical environment, such as, but not limited to, a general purpose computer, special purpose computer, microprocessor, digital signal processor (DSP), application specific integrated circuit (ASIC), programmable logic device (FGPA) and processors based on multi-core processor architectures.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FGPA programmable logic device

Landscapes

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

Abstract

L'invention concerne un procédé de modulation de données, un dispositif de communication et un support de stockage. Le procédé consiste à : acquérir une demande de service pour un service cible dans une application cible ; et envoyer la demande de service à une tranche de réseau correspondante de façon à ce qu'une entité à fonction de charge génère, en fonction d'une demande de charge, des informations de charge correspondant au service cible, la demande de charge étant générée par la tranche de réseau correspondante en fonction de la demande de service, différents services cibles correspondant à différentes tranches de réseau, et les exigences pour les services cibles correspondant aux caractéristiques de réseau des tranches de réseau.
PCT/CN2021/113303 2020-09-22 2021-08-18 Procédé de modulation de données, dispositif de communication et support de stockage Ceased WO2022062778A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202011004698.6A CN114257973B (zh) 2020-09-22 2020-09-22 业务计费方法、通信设备及存储介质
CN202011004698.6 2020-09-22

Publications (1)

Publication Number Publication Date
WO2022062778A1 true WO2022062778A1 (fr) 2022-03-31

Family

ID=80789698

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/113303 Ceased WO2022062778A1 (fr) 2020-09-22 2021-08-18 Procédé de modulation de données, dispositif de communication et support de stockage

Country Status (2)

Country Link
CN (1) CN114257973B (fr)
WO (1) WO2022062778A1 (fr)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106572517A (zh) * 2015-10-09 2017-04-19 中国移动通信集团公司 网络切片的处理方法、接入网络的选择方法及装置
WO2019005067A1 (fr) * 2017-06-29 2019-01-03 Nokia Solutions And Networks Oy Sélection de tranche de réseau sur la base de règles de facturation
CN109429277A (zh) * 2017-07-05 2019-03-05 中兴通讯股份有限公司 网络切片的选择方法、装置及系统
CN110461027A (zh) * 2018-05-07 2019-11-15 华为技术有限公司 一种网络切片选择方法及装置
US20200267786A1 (en) * 2019-02-15 2020-08-20 Weihua QIAO Charging aggregation control for network slices
CN111669719A (zh) * 2019-03-07 2020-09-15 华为技术有限公司 对网络切片客户进行计费处理的方法、系统及相关设备

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100413248C (zh) * 2005-03-31 2008-08-20 杭州华三通信技术有限公司 一种基于流量进行计费的改进方法和系统
CN101425908A (zh) * 2007-11-01 2009-05-06 华为技术有限公司 业务计费的方法及应用服务器和计费系统
CN101686134B (zh) * 2008-09-28 2012-02-01 华为技术有限公司 一种计费处理方法、装置和系统
KR102067379B1 (ko) * 2012-10-30 2020-01-17 에스케이텔레콤 주식회사 무선 데이터 통신망 기반 통화 서비스를 위한 지원 시스템, 서비스 장치 및 방법
CN104717627A (zh) * 2013-12-13 2015-06-17 中国移动通信集团公司 计费话单创建方法、数据业务计费方法及相关装置
US10321371B2 (en) * 2016-04-11 2019-06-11 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for communication over network slices in wireless communication systems
CN109842858B (zh) * 2017-11-24 2020-12-08 中移(苏州)软件技术有限公司 一种业务异常订购检测方法及装置
CN110838926A (zh) * 2018-08-15 2020-02-25 中国移动通信有限公司研究院 管理网络切片的方法及系统
CN111385754B (zh) * 2018-12-29 2022-05-31 华为技术有限公司 计费的方法、装置及系统

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106572517A (zh) * 2015-10-09 2017-04-19 中国移动通信集团公司 网络切片的处理方法、接入网络的选择方法及装置
WO2019005067A1 (fr) * 2017-06-29 2019-01-03 Nokia Solutions And Networks Oy Sélection de tranche de réseau sur la base de règles de facturation
CN109429277A (zh) * 2017-07-05 2019-03-05 中兴通讯股份有限公司 网络切片的选择方法、装置及系统
CN110461027A (zh) * 2018-05-07 2019-11-15 华为技术有限公司 一种网络切片选择方法及装置
US20200267786A1 (en) * 2019-02-15 2020-08-20 Weihua QIAO Charging aggregation control for network slices
CN111669719A (zh) * 2019-03-07 2020-09-15 华为技术有限公司 对网络切片客户进行计费处理的方法、系统及相关设备

Also Published As

Publication number Publication date
CN114257973A (zh) 2022-03-29
CN114257973B (zh) 2025-11-21

Similar Documents

Publication Publication Date Title
US10764727B2 (en) Method for charging inter-PLMN roaming data service online, and device
US20250219853A1 (en) Method and system for performing charging processing on network slice customer, and related device
US20200267008A1 (en) Api content based charging method and capability exposure function entity
WO2017088501A1 (fr) Procédé et dispositif de facturation
US8897745B2 (en) Method and apparatus for optimizing delivery of network usage and billing data
US11470202B2 (en) Charging method, apparatus, and system
EP3282729B1 (fr) Dispositif et procédé de fonction d'exécution de politique et de facturation, et dispositif et procédé de facturation en ligne
KR102596498B1 (ko) 과금 방법, 장치, 및 시스템
US20240251041A1 (en) Charging method and device
CN111512594B (zh) 虚拟网络功能管理方法和装置
US10700879B2 (en) Charging method and device, access device, service quality control method and device
US20220286564A1 (en) Method and Apparatus for Dynamic Realtime Sharing of Credit Units for Online Charging
WO2022062778A1 (fr) Procédé de modulation de données, dispositif de communication et support de stockage
CN117221841A (zh) 流量计费系统和方法
US10003696B2 (en) Distributed collaborative offline charging system
WO2016141708A1 (fr) Procédé et système pour réaliser une facturation en ligne
CN110636518B (zh) 一种性能数据统计方法及相关设备
CN118803635A (zh) 通信计费方法、系统、电子设备、存储介质及程序产品
EP4226581A1 (fr) Gestion d'opération de facturation dans un réseau de communication

Legal Events

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

Ref document number: 21871151

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205 DATED 11/08/2023)

122 Ep: pct application non-entry in european phase

Ref document number: 21871151

Country of ref document: EP

Kind code of ref document: A1