Charging method, apparatus, device, and readable storage medium

Abstract

Embodiments of the present application provide a charging method, device and equipment and readable storage medium, the method comprising: sending a first message, the first message being used for requesting charging processing of a first object corresponding to a first level slice and / or a second object corresponding to a second level slice; wherein the first message carries information of at least two level slices, the at least two level slices at least including the first level slice and the second level slice, the first level slice being a slice divided based on the first object, and the second level slice being a slice divided based on the second object on the basis of the first level slice.

Description

Technical Field

[0001] This application relates to the field of communication technology, specifically to a billing method, apparatus, device, and readable storage medium. Background Technology

[0002] As enterprise and government users continue to cloudify their businesses, driving the evolution of cloud-network convergence technology, and guided by operators' major strategies for focusing on B2B business, the types of leased line services for industry and enterprise users are becoming more diversified, including leased lines for users migrating to the cloud, leased lines / networks for users to access each other's sites, and cloud interconnection leased lines / networks. Different types of cloud-network services or leased line services have differentiated requirements for network services, requiring IP networks to support thousands of hierarchical slice services with guaranteed resources.

[0003] Current IP network billing primarily focuses on network resource usage, such as bandwidth, usage duration, and input / output bytes / packets. For example, it uses the Remote Authentication DialIn User Service (RADIUS) protocol for billing management. However, current billing schemes can only perform bandwidth, traffic, and duration statistics and billing for a specific device or interface, failing to differentiate between different levels of network slices. Consequently, they cannot meet the multi-layered, multi-dimensional, and multi-scenario billing needs of vertical industries. Summary of the Invention

[0004] This application provides a billing method, apparatus, device, and readable storage medium to solve the problem that existing billing methods cannot meet the multi-level, multi-dimensional, and multi-scenario billing needs of vertical industries.

[0005] Firstly, a billing method is provided for use in network devices, including:

[0006] Send a first message, which is used to request billing processing for the first object corresponding to the first-level slice and / or the second object corresponding to the second-level slice;

[0007] The first message carries information about at least two levels of slices, which include at least a first-level slice and a second-level slice. The first-level slice is a slice based on a first object, and the second-level slice is a slice based on a second object based on the first-level slice.

[0008] Optionally, the first message includes a first request, which is used to request the initiation of billing for a first object corresponding to a first-level slice and / or a second object corresponding to a second-level slice; or, the first message includes a second request, which is used to request the cessation of billing for a first object corresponding to a first-level slice and / or a second object corresponding to a second-level slice.

[0009] Optionally, the second request may also include the time and / or reason for stopping billing.

[0010] Optionally, the method further includes:

[0011] Receive a sixth message, which is used to request authentication and carries information about the at least two levels of slices;

[0012] Send a seventh message, which carries user authorization information related to the at least two levels of slices.

[0013] Optionally, the information of the at least two levels of slices is carried in the slice field of the first message.

[0014] Optionally, the information of the at least two levels of slices includes: a first identifier and a second identifier, wherein the first identifier is the identifier of the first level slice of the first object, and the second identifier is the identifier of the second level slice of the first level slice corresponding to the second object.

[0015] Optionally, the first identifier is an identifier introduced for the control plane technology of the slice; the second identifier is an identifier introduced for the data plane technology of the slice.

[0016] Secondly, a billing method is provided for use with servers, including:

[0017] Receive a first message, the first message carrying information of at least two levels of slices, wherein the at least two levels of slices include at least: a first level slice and a second level slice, the first level slice is a slice based on a first object, and the second level slice is a slice based on a second object based on the first level slice;

[0018] Based on the first message, billing processing is performed on the first object corresponding to the first-level slice and / or the second object corresponding to the second-level slice.

[0019] Optionally, the first message includes a first request, which is used to request the initiation of billing for a first object corresponding to a first-level slice and / or a second object corresponding to a second-level slice;

[0020] Based on the first message, billing processing is performed on the first object corresponding to the first-level slice, and / or the second object corresponding to the second-level slice, including:

[0021] Based on the first request, billing is initiated for the first object corresponding to the first-level slice and / or the second object corresponding to the second-level slice.

[0022] Optionally, the first message includes a second request, which is used to request the cessation of billing for the first object corresponding to the first-level slice and / or the second object corresponding to the second-level slice;

[0023] Based on the first message, billing processing is performed on the first object corresponding to the first-level slice, and / or the second object corresponding to the second-level slice, including:

[0024] Based on the second request, billing shall be stopped for the first object corresponding to the first-level slice and / or the second object corresponding to the second-level slice.

[0025] Optionally, the second request may also include the time and / or reason for stopping billing.

[0026] Optionally, the information of the at least two levels of slices is carried in the slice field of the first message.

[0027] Optionally, the method further includes:

[0028] Receive a second message, which is used to request authentication, and the second message carries information about the at least two levels of slices;

[0029] A third message is sent, which carries user authorization information related to the at least two levels of slices.

[0030] Optionally, the method further includes:

[0031] Receive a fourth message, which carries the billing policies for the at least two levels of slices.

[0032] Optionally, the method further includes:

[0033] Receive a fifth message, which carries a dynamic authorization related to user-customized services.

[0034] Optionally, the information of the at least two levels of slices includes: a first identifier and a second identifier, wherein the first identifier is the identifier of the first level slice of the first object, and the second identifier is the identifier of the second level slice of the first level slice corresponding to the second object.

[0035] Optionally, the first identifier is an identifier introduced for the control plane technology of the slice; the second identifier is an identifier introduced for the data plane technology of the slice.

[0036] Thirdly, a billing method is provided for use on a terminal, including:

[0037] Send a sixth message, which is used to request authentication and carries information about the at least two levels of slices;

[0038] The at least two levels of slicing include at least: a first-level slice and a second-level slice, wherein the first-level slice is a slice based on a first object, and the second-level slice is a slice based on a second object based on the first-level slice.

[0039] Optionally, the method further includes:

[0040] A seventh message is received, which carries user authorization information related to the at least two levels of slices.

[0041] Fourthly, a billing device is provided, applied to network equipment, comprising:

[0042] The first sending module is used to send a first message, which is used to request billing processing for the first object corresponding to the first level slice and / or the second object corresponding to the second level slice.

[0043] The first message carries information about at least two levels of slices, which include at least a first-level slice and a second-level slice. The first-level slice is a slice based on a first object, and the second-level slice is a slice based on a second object based on the first-level slice.

[0044] Fifthly, a billing device is provided for use on a server, comprising:

[0045] The second receiving module is used to receive a first message, the first message carrying information of at least two levels of slices, wherein the at least two levels of slices include at least: a first level slice and a second level slice, the first level slice is a slice divided based on a first object, and the second level slice is a slice divided based on a second object based on the first level slice;

[0046] The billing processing module is used to perform billing processing on the first object corresponding to the first level slice and / or the second object corresponding to the second level slice, based on the first message.

[0047] Sixthly, a billing device is provided for use in a terminal, comprising:

[0048] The fourth sending module is used to send a sixth message, which is used to request authentication and carries information about the at least two levels of slices.

[0049] The at least two levels of slicing include at least: a first-level slice and a second-level slice, wherein the first-level slice is a slice based on a first object, and the second-level slice is a slice based on a second object based on the first-level slice.

[0050] A seventh aspect provides a communication device, including a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the method as described in the first aspect, the second aspect, or the third aspect.

[0051] Eighthly, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method as described in the first, second, or third aspect.

[0052] In this embodiment of the application, the first message sent by the network device carries information on at least two levels of slices. The at least two levels of slices include at least a first-level slice and a second-level slice. The first-level slice is a slice divided based on a first object, and the second-level slice is a slice divided based on a second object on the basis of the first-level slice. This can meet the billing needs of multi-level and multi-dimensional industries in vertical industries, and at the same time, it can facilitate operators to perform overall management, statistical analysis on a certain industry or a certain user / application. Attached Figure Description

[0053] Various other advantages and benefits will become apparent to those skilled in the art upon reading the following detailed description of preferred embodiments. The accompanying drawings are for illustrative purposes only and are not intended to limit the scope of this application. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings:

[0054] Figure 1 This is one of the flowcharts of a billing method provided in the embodiments of this application;

[0055] Figure 2 This is a second flowchart of a billing method provided in the embodiments of this application;

[0056] Figure 3 This is the third flowchart of a billing method provided in the embodiments of this application;

[0057] Figure 4 This is the fourth flowchart of a billing method provided in the embodiments of this application;

[0058] Figure 5 This is the fifth flowchart of a billing method provided in the embodiments of this application;

[0059] Figure 6a , Figure 6b This is a schematic diagram of the Radius protocol message format provided in the embodiments of this application;

[0060] Figure 7 This is one of the schematic diagrams of a billing device provided in the embodiments of this application;

[0061] Figure 8 This is a second schematic diagram of a billing device provided in an embodiment of this application;

[0062] Figure 9 This is the third schematic diagram of a billing device provided in the embodiments of this application;

[0063] Figure 10 This is a schematic diagram of the communication device provided in the embodiments of this application. Detailed Implementation

[0064] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0065] The term "comprising," and any variations thereof, used in the specification and claims of this application, is intended to cover a non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not necessarily limited to those explicitly listed, but may include other steps or units not explicitly listed or inherent to such process, method, product, or apparatus. Furthermore, the use of "and / or" in the specification and claims indicates at least one of the connected objects, such as A and / or B, indicating the inclusion of A alone, B alone, or both A and B.

[0066] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of the terms "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0067] See Figure 1This application provides a billing method, the execution subject of which can be a network device, such as a Network Attached Storage (NAS) or a Broadband Remote Access Server (BRAS). Specific steps include:

[0068] Step 101: The network device sends a first message to the server (or described as a billing server), the first message being used to request billing processing for the first object corresponding to the first level slice and / or the second object corresponding to the second level slice;

[0069] The first message carries information about at least two levels of slices. The at least two levels of slices include at least a first-level slice and a second-level slice. The first-level slice is a slice divided based on a first object, and the second-level slice is a slice divided based on a second object based on the first-level slice.

[0070] In this embodiment, slices are divided into different levels (or layers) according to the objects related to billing. If the objects related to billing include two types, the slice is divided into two levels, namely, level 1 slice and level 2 slice. If the objects related to billing include three types, the slice is divided into three levels, namely, level 1 slice, level 2 slice, and level 3 slice. If the objects related to billing include four types, the slice is divided into four levels, namely, level 1 slice, level 2 slice, level 3 slice, and level 4 slice, and so on.

[0071] For example, the slice hierarchy includes two levels: the slice is divided into a first-level slice (or described as a first-layer slice) according to a first object, and a second-level slice (or described as a second-layer slice) is obtained by further dividing the first-level slice according to a second object.

[0072] For example, the slice levels can also include three levels. The slice is divided into first-level slices according to the first object, and then divided into second-level slices according to the second object based on the first-level slices. Then, the slice is divided into third-level slices according to the third object based on the second-level slices. It can be understood that the case of more than three levels can be deduced by analogy, which will not be elaborated here.

[0073] Optionally, the objects may include, but are not limited to, industries, users, or applications. For example, if the objects include two types, the first object can be an industry, and the second object can be a user or application. Of course, this is not the case. Those skilled in the art can configure the object types to be two, three, four, etc., according to the multi-level and multi-dimensional billing or statistical analysis needs of the vertical industry.

[0074] Taking two-level slicing as an example, two-level slicing includes: first-level slicing and second-level slicing. First-level slicing is slicing that is divided for a certain industry (first-level slicing has its own exclusive slicing resources, such as bandwidth resources). Second-level slicing is slicing that is further divided within the first-level slicing of the industry for different users or applications (each second-level slicing has its own exclusive slicing resources).

[0075] In one embodiment of this application, the first message includes a first request, which is used to request the initiation of billing for a first object corresponding to a first-level slice and / or a second object corresponding to a second-level slice; or, the first message includes a second request, which is used to request the cessation of billing for a first object corresponding to a first-level slice and / or a second object corresponding to a second-level slice.

[0076] In one embodiment of this application, the second request also includes the time of billing cessation and / or the reason for billing cessation.

[0077] In one embodiment of this application, the method further includes:

[0078] A sixth message is received from the terminal, the sixth message being used to request authentication, and the sixth message carrying information about the at least two levels of slices;

[0079] A seventh message is sent to the terminal, the seventh message carrying user authorization information related to the at least two levels of slices.

[0080] In one embodiment of this application, the information of the at least two levels of slices is carried in the slice field of the first message.

[0081] In one embodiment of this application, the information of the at least two levels of slices includes: a first identifier and a second identifier, wherein the first identifier is the identifier of a first-level slice of a first object, and the second identifier is the identifier of a second-level slice of the first-level slice corresponding to a second object.

[0082] In one embodiment of this application, the first identifier is an identifier introduced for the control plane technology of the slice, such as FA (short for FlexAlgo) ID; the second identifier is an identifier introduced for the data plane technology of the slice, such as slice ID.

[0083] In this embodiment of the application, the first message sent by the network device carries information on at least two levels of slices. The at least two levels of slices include at least a first-level slice and a second-level slice. The first-level slice is a slice divided based on a first object, and the second-level slice is a slice divided based on a second object on the basis of the first-level slice. This can meet the billing needs of multi-level and multi-dimensional industries in vertical industries, and at the same time, it can facilitate operators to perform overall management, statistical analysis on a certain industry or a certain user / application.

[0084] See Figure 2 This application provides a billing method, the execution subject of which can be a server (or described as a billing server), such as a network device, network element, or network function with billing functionality. Specific steps include:

[0085] Step 201: The server receives a first message from the network device. The first message carries information about at least two levels of slices. The at least two levels of slices include at least a first-level slice and a second-level slice. The first-level slice is a slice divided based on a first object, and the second-level slice is a slice divided based on a second object based on the first-level slice.

[0086] In this embodiment, slices are divided into different levels (or layers) according to the objects related to billing. If the objects related to billing include two types, the slice is divided into two levels; if the objects related to billing include three types, the slice is divided into three levels; if the objects related to billing include four types, the slice is divided into four levels, and so on.

[0087] For example, the slice hierarchy includes two levels: the slice is divided into a first-level slice (or described as a first-layer slice) according to a first object, and a second-level slice (or described as a second-layer slice) is obtained by further dividing the first-level slice according to a second object.

[0088] For example, the slice levels can also include three levels. The slice is divided into first-level slices according to the first object, and then divided into second-level slices according to the second object based on the first-level slices. Then, the slice is divided into third-level slices according to the third object based on the second-level slices. It can be understood that the case of more than three levels can be deduced by analogy, which will not be elaborated here.

[0089] Optionally, the objects may include, but are not limited to, industries, users, or applications. For example, if the objects include two types, the first object can be an industry, and the second object can be a user or application. Of course, this is not the case. Those skilled in the art can configure the object types to be two, three, four, or other types according to the multi-level and multi-dimensional billing or statistical analysis needs of the vertical industry.

[0090] Taking two-level slicing as an example, two-level slicing includes: first-level slicing and second-level slicing. First-level slicing is slicing that is divided for a certain industry (first-level slicing has its own exclusive slicing resources, such as bandwidth resources). Second-level slicing is slicing that is further divided within the first-level slicing of the industry for different users or applications (each second-level slicing has its own exclusive slicing resources).

[0091] Step 202: The server performs billing processing on the first object corresponding to the first level slice and / or the second object corresponding to the second level slice, based on the first message.

[0092] Understandably, in addition to carrying information about at least two levels of slicing, the first message can also carry existing billing-related information, such as internet access duration, number of incoming and outgoing bytes / packets, etc. This information about at least two levels of slicing can identify which level of slice the current bandwidth and other information are for.

[0093] In this embodiment, the first message carries information about at least two levels of slices, facilitating the subsequent association of billing policies with specific users or applications within those at least two levels of slices. This is because billing policies differ across industries and application scenarios, thus meeting the diverse needs of vertical industries. For example, based on the first message, billing can be performed on the first object corresponding to the first level slice using a first billing policy, and / or on the second object corresponding to the second level slice using a second billing policy.

[0094] In one embodiment of this application, the first message includes a first request (or a start message), for example, see [link to relevant documentation]. Figure 4 In step 5, the first request is used to request the start of billing for the first object corresponding to the first-level slice and / or the second object corresponding to the second-level slice;

[0095] Based on the first message, the server performs billing processing on the first object corresponding to the first-level slice, and / or on the second object corresponding to the second-level slice, including:

[0096] Based on the first request, the server initiates billing for the first object corresponding to the first-level slice, and / or initiates billing for the second object corresponding to the second-level slice.

[0097] In one embodiment of this application, the first message includes a second request, such as see [link to relevant documentation]. Figure 4 In step 7, the second request is used to request a stop to billing the first object corresponding to the first-level slice and / or the second object corresponding to the second-level slice;

[0098] Based on the first message, the server performs billing processing on the first object corresponding to the first-level slice, and / or on the second object corresponding to the second-level slice, including:

[0099] Based on the second request, the server stops billing for the first object corresponding to the first-level slice and / or the second object corresponding to the second-level slice.

[0100] Optionally, the second request may also include the time and / or reason for stopping billing.

[0101] For example, the unit for the time during which billing is suspended can be days, hours, minutes, or seconds; the reasons for suspending billing include, but are not limited to, the user disconnecting.

[0102] Understandably, the server can send response messages to the network device in response to the first and second requests, for example, see [link to relevant documentation]. Figure 4 Steps 6 and 8 in the process.

[0103] In one embodiment of this application, the information of the at least two levels of slices is carried in the slice field of the first message.

[0104] In one embodiment of this application, the method further includes:

[0105] The server receives a second message from the network device, the second message being used to request authentication, and the second message carrying information about the at least two levels of slices;

[0106] The server sends a third message to the network device, the third message carrying user authorization information related to the at least two levels of slices.

[0107] In one embodiment of this application, the method may further include:

[0108] The server receives a fourth message from the controller, which carries the billing policies for the at least two levels of slices. For example, if the at least two levels of slices include a first-level slice and a second-level slice, then the fourth message carries the billing policies for both the first-level and second-level slices. In this embodiment, the content of the billing policy for each level of slice is not specifically limited.

[0109] Understandably, the interface protocol between the controller and the server also needs to add relevant fields to represent information about at least two levels of slices.

[0110] In one embodiment of this application, the method further includes:

[0111] The server receives a fifth message from the portal website, the fifth message carrying dynamic authorization for the at least two levels of slices, the dynamic authorization being related to the services of the at least two levels of slices newly customized by the user.

[0112] For example, when a user subscribes to a service on the portal server, the billing server receives a fifth message from the portal server. The fifth message includes information about the service that the user subscribed to at least two levels of the slice on the portal server.

[0113] In one embodiment of this application, the information of the at least two levels of slices includes: a first identifier and a second identifier, wherein the first identifier is the identifier of a first-level slice of a first object, and the second identifier is the identifier of a second-level slice of the first-level slice corresponding to a second object.

[0114] In one embodiment of this application, the first identifier is an identifier introduced for the control plane technology of the slice, such as FA (short for FlexAlgo) ID; the second identifier is an identifier introduced for the data plane technology of the slice, such as slice ID.

[0115] The control plane technology for IP network slicing is FlexAlgo (a flexible algorithm that allows users to create separate topologies and calculate paths within Interior Gateway Protocols (IGP, or FA)). Based on an IGP single topology, each L3 link corresponds to one or more FA algorithm spaces, published by the IGP protocol, forming IGP sub-path spaces. Different algorithm spaces are distinguished within a topology through FA. The FA algorithm comprises two parts: topology constraints and algorithm logic. The topology constraints result in different sub-topologies. Services can find corresponding FA-label switched paths (LSPs) based on FA-based single prefix segment routing IDs (SIDs) or specific segment routing (SR) lists.

[0116] For IP network slicing, a data plane technology introduces a SliceID to guide data packet forwarding. Specifically, the SliceID can be carried in the Hop-by-Hop Options Header (HBH) of Internet Protocol Version 6 (IPv6) packets or in related fields of the Segment Routing IPv6 (SRv6) header based on the IPv6 forwarding plane.

[0117] Optionally, FlexAlgo will be used as the identifier for the first-level slice, and SliceID will be used as the identifier for the second-level slice.

[0118] In this embodiment of the application, the first message received by the server carries information on at least two levels of slices. The at least two levels of slices include at least a first-level slice and a second-level slice. The first-level slice is a slice divided based on a first object, and the second-level slice is a slice divided based on a second object on the basis of the first-level slice. This can meet the billing needs of multi-level and multi-dimensional industries in vertical industries, and at the same time, it can facilitate operators to perform overall management, statistical analysis on a certain industry or a certain user / application.

[0119] See Figure 3 This application provides a billing method, the execution subject of which can be a terminal, and the specific steps include:

[0120] Step 301: The terminal sends a sixth message to the network device, the sixth message being used to request authentication, and the sixth message carrying information about the at least two levels of slices;

[0121] The at least two levels of slicing include at least: a first-level slice and a second-level slice, wherein the first-level slice is a slice based on a first object, and the second-level slice is a slice based on a second object based on the first-level slice.

[0122] In one embodiment of this application, the method further includes:

[0123] The terminal receives a seventh message sent by the network device, the seventh message carrying user authorization information related to the at least two levels of slices.

[0124] In this embodiment of the application, when the terminal requests authentication, the sixth message sent carries information of at least two levels of slices. The at least two levels of slices include at least: a first-level slice and a second-level slice. The first-level slice is a slice divided based on a first object, and the second-level slice is a slice divided based on a second object on the basis of the first-level slice. This can meet the billing needs of multi-level and multi-dimensional industries in vertical industries, and at the same time, it can facilitate operators to perform overall management, statistical analysis for a certain industry or a certain user / application.

[0125] like Figure 4As shown in the figure, this is an implementation of the interaction between a terminal, a network device (such as a RADIUS client), a server (such as a RADIUS server), a controller, and a portal website server. It should be noted that the order of the steps is not limited in this embodiment. For example, step 11 or step 12 can be performed after other steps, before other steps, or simultaneously with other steps.

[0126] The network devices can be located in routers or access servers, such as Network Attached Storage (NAS) or Broadband Remote Access Server (BRAS).

[0127] See Figure 5 Taking the Radius protocol billing method as an example, the billing process for slices is as follows:

[0128] 1. When a user logs into the RADIUS client (equivalent to a network device), they will send their username, password, FA ID, and sliceID to the RADIUS client.

[0129] 2. The RADIUS client receives the username, password, FA ID, and slice ID, and sends them to the RADIUS server (which is equivalent to the server).

[0130] 3. After receiving a valid request, the RADIUS server completes the authentication and returns the necessary user authorization information related to the two-level slice to the RADIUS client.

[0131] 4. When a RADIUS client starts logging in, the RADIUS server begins billing the user or application within the slice.

[0132] II. Billing Process:

[0133] 1. If authentication and authorization are successful, the RADIUS server will begin billing.

[0134] 2. The RADIUS client receives the first request (adding the FA ID + slice ID attributes). That is, a message requesting the start of billing is sent to the RADIUS server.

[0135] 3. If the request is valid, the RADIUS server records the information of the two-level slice and the user or application in the database and returns a reply (REPLY) message to the RADIUS client.

[0136] 4. When a user logs out, the RADIUS client receives a second request carrying the stop time and the reason for stopping billing. That is, a message requesting the suspension or termination of billing (FA ID + slice ID) is sent to the RADIUS server.

[0137] 5. The RADIUS server records information about the two-level slices and the user or application that has stopped billing in the database.

[0138] 6. The interaction between the RADIUS client and the RADIUS server is authenticated through a shared key that is never sent over the network. Furthermore, user password information between the RADIUS client and the RADIUS server is encrypted before being transmitted over the network to prevent user passwords from being stolen on insecure networks.

[0139] See Figure 6a and Figure 6b The diagram illustrates the Radius protocol message format. The Radius protocol message attribute field is extended between the RADIUS client and the RADIUS server to add slice field information, which is used to carry information about at least two levels of slices, such as FA-ID and slice-ID.

[0140] See Figure 7 This application provides a billing device for use in network equipment. The device 700 includes:

[0141] The first sending module 701 is used to send a first message, the first message being used to request billing processing for the first object corresponding to the first level slice and / or the second object corresponding to the second level slice;

[0142] The at least two levels of slicing include at least: a first-level slice and a second-level slice, wherein the first-level slice is a slice based on a first object, and the second-level slice is a slice based on a second object based on the first-level slice.

[0143] In one embodiment of this application, the first message includes a first request, which is used to request the initiation of billing for a first object corresponding to a first-level slice and / or a second object corresponding to a second-level slice; or, the first message includes a second request, which is used to request the cessation of billing for a first object corresponding to a first-level slice and / or a second object corresponding to a second-level slice.

[0144] In one embodiment of this application, the second request also includes the time of billing cessation and / or the reason for billing cessation.

[0145] In one embodiment of this application, the apparatus further includes:

[0146] The first receiving module is configured to receive a sixth message, which is used to request authentication and carries information about the at least two levels of slices.

[0147] The second sending module is used to send a seventh message, which carries user authorization information related to the at least two-level slices.

[0148] The apparatus provided in this application embodiment can achieve... Figure 1 The various processes implemented in the method embodiments shown achieve the same technical effects, and will not be described again here to avoid repetition.

[0149] See Figure 8 This application provides a billing device applied to a server. The device 800 includes:

[0150] The second receiving module 801 is used to receive a first message, the first message carrying information of at least two levels of slices, wherein the at least two levels of slices include at least: a first level slice and a second level slice, the first level slice is a slice divided based on a first object, and the second level slice is a slice divided based on a second object based on the first level slice.

[0151] The billing processing module 802 is used to perform billing processing on the first object corresponding to the first level slice and / or the second object corresponding to the second level slice according to the first message.

[0152] In one embodiment of this application, the first message includes a first request, which is used to request the initiation of billing for a first object corresponding to a first-level slice and / or a second object corresponding to a second-level slice;

[0153] The billing processing module 802 is further configured to: initiate billing for the first object corresponding to the first-level slice and / or the second object corresponding to the second-level slice according to the first request.

[0154] In one embodiment of this application, the first message includes a second request, which is used to request the cessation of billing for the first object corresponding to the first-level slice and / or the second object corresponding to the second-level slice;

[0155] The billing processing module 802 is further configured to: stop billing the first object corresponding to the first-level slice and / or the second object corresponding to the second-level slice according to the second request.

[0156] In one embodiment of this application, the second request also includes the time of billing cessation and / or the reason for billing cessation.

[0157] In one embodiment of this application, the information of the at least two levels of slices is carried in the slice field of the first message.

[0158] In one embodiment of this application, the apparatus further includes:

[0159] The third receiving module is used to receive a second message, which is used to request authentication and carries information about the at least two levels of slices.

[0160] The third sending module is used to send a third message, which carries user authorization information related to the at least two-level slices.

[0161] In one embodiment of this application, the apparatus further includes:

[0162] The fourth receiving module is used to receive a fourth message, which carries the billing strategy of the at least two-level slices.

[0163] In one embodiment of this application, the apparatus further includes:

[0164] The fifth receiving module is used to receive a fifth message, which carries a dynamic authorization related to user-customized services.

[0165] In one embodiment of this application, the information of the at least two levels of slices includes: a first identifier and a second identifier, wherein the first identifier is the identifier of a first-level slice of a first object, and the second identifier is the identifier of a second-level slice of the first-level slice corresponding to a second object.

[0166] In one embodiment of this application, the first identifier is an identifier introduced for the control plane technology of the slice; the second identifier is an identifier introduced for the data plane technology of the slice.

[0167] The apparatus provided in this application embodiment can achieve... Figure 2 The various processes implemented in the method embodiments shown achieve the same technical effects, and will not be described again here to avoid repetition.

[0168] See Figure 9 This application provides a billing device for use in a terminal. The device 900 includes:

[0169] The fourth sending module 901 is used to send a sixth message, which is used to request authentication and carries information about the at least two levels of slices.

[0170] The at least two levels of slicing include at least: a first-level slice and a second-level slice, wherein the first-level slice is a slice based on a first object, and the second-level slice is a slice based on a second object based on the first-level slice.

[0171] In one embodiment of this application, the apparatus further includes:

[0172] The sixth receiving module is used to receive a seventh message, which carries user authorization information related to the at least two levels of slices.

[0173] The apparatus provided in this application embodiment can achieve... Figure 3 The various processes implemented in the method embodiments shown achieve the same technical effects, and will not be described again here to avoid repetition.

[0174] like Figure 10 As shown, this application embodiment also provides a communication device 1000, including a processor 1001, a memory 1002, and a program or instructions stored in the memory 1002 and executable on the processor 1001. When the program or instructions are executed by the processor 1001, they implement the above-mentioned... Figure 1 or Figure 2 or Figure 3 The various processes in the method embodiments can achieve the same technical effect. To avoid repetition, they will not be described again here.

[0175] This application embodiment also provides a readable storage medium storing a program or instructions that, when executed by a processor, implement the above-described functionality. Figure 1 or Figure 2 or Figure 3 The various processes of the method embodiments shown can achieve the same technical effect, and will not be described again here to avoid repetition.

[0176] The processor mentioned above is the processor in the terminal described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0177] The steps of the methods or algorithms described in this application can be implemented in hardware or by executing software instructions on a processor. The software instructions can consist of corresponding software modules, which can be stored in RAM, flash memory, ROM, EPROM, EEPROM, registers, hard disk, portable hard disk, read-only optical disk, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can be housed in an ASIC. Alternatively, the ASIC can be housed in a core network interface device. Of course, the processor and storage medium can also exist as discrete components in the core network interface device.

[0178] Those skilled in the art will recognize that, in one or more of the examples above, the functions described in this application can be implemented using hardware, software, firmware, or any combination thereof. When implemented in software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any medium that facilitates the transfer of a computer program from one place to another. Storage media can be any available medium accessible to a general-purpose or special-purpose computer.

[0179] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of this application. It should be understood that the above description is only a specific embodiment of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made on the basis of the technical solution of this application should be included within the scope of protection of this application.

[0180] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, embodiments of this application can take the form of entirely hardware embodiments, entirely software embodiments, or embodiments combining software and hardware aspects. Furthermore, embodiments of this application can take the form of computer program products implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0181] This application describes embodiments of methods, apparatus (systems), and computer program products according to embodiments of this application with reference to flowchart illustrations and / or block diagrams. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0182] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0183] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0184] Obviously, those skilled in the art can make various modifications and variations to the embodiments of this application without departing from the spirit and scope of this application. Therefore, if these modifications and variations to the embodiments of this application fall within the scope of the claims of this application and their equivalents, this application also intends to include these modifications and variations.

Claims

1. A billing method applied to network equipment, characterized in that, include: Send a first message, which is used to request billing processing for the first object corresponding to the first-level slice and / or the second object corresponding to the second-level slice; The first message carries information about at least two levels of slices, which include at least a first-level slice and a second-level slice. The first-level slice is a slice based on a first object, and the second-level slice is a slice based on a second object based on the first-level slice. The information of the at least two levels of slices includes: a first identifier and a second identifier, wherein the first identifier is the identifier of the first level slice of the first object, and the second identifier is the identifier of the second level slice of the first level slice corresponding to the second object; The first identifier is an identifier introduced for the control plane technology of the slice; the second identifier is an identifier introduced for the data plane technology of the slice.

2. The method according to claim 1, characterized in that, The first message includes a first request, which is used to request the initiation of billing for a first object corresponding to a first-level slice, and / or a second object corresponding to a second-level slice, or... The first message includes a second request, which requests the cessation of billing for the first object corresponding to the first-level slice and / or the second object corresponding to the second-level slice.

3. The method according to claim 2, characterized in that, The second request also includes the time and / or reason for stopping billing.

4. The method according to claim 1, characterized in that, The method further includes: Receive a sixth message, which is used to request authentication and carries information about the at least two levels of slices; Send a seventh message, which carries user authorization information related to the at least two levels of slices.

5. The method according to claim 1, characterized in that, The information of the at least two levels of slices is carried in the slice field of the first message.

6. A billing method applied to a server, characterized in that, include: Receive a first message, the first message carrying information of at least two levels of slices, wherein the at least two levels of slices include at least: a first level slice and a second level slice, the first level slice is a slice based on a first object, and the second level slice is a slice based on a second object based on the first level slice; Based on the first message, billing processing is performed on the first object corresponding to the first level slice and / or the second object corresponding to the second level slice; The information of the at least two levels of slices includes: a first identifier and a second identifier, wherein the first identifier is the identifier of the first level slice of the first object, and the second identifier is the identifier of the second level slice of the first level slice corresponding to the second object; The first identifier is an identifier introduced for the control plane technology of the slice; the second identifier is an identifier introduced for the data plane technology of the slice.

7. The method according to claim 6, characterized in that, The first message includes a first request, which is used to request the initiation of billing for a first object corresponding to a first-level slice and / or a second object corresponding to a second-level slice; Based on the first message, billing processing is performed on the first object corresponding to the first-level slice, and / or the second object corresponding to the second-level slice, including: Based on the first request, billing is initiated for the first object corresponding to the first-level slice, and / or billing is initiated for the second object corresponding to the second-level slice.

8. The method according to claim 6, characterized in that, The first message includes a second request, which is used to request the cessation of billing for the first object corresponding to the first-level slice and / or the second object corresponding to the second-level slice; Based on the first message, billing processing is performed on the first object corresponding to the first-level slice, and / or the second object corresponding to the second-level slice, including: Based on the second request, stop billing for the first object corresponding to the first-level slice, and / or stop billing for the second object corresponding to the second-level slice.

9. The method according to claim 8, characterized in that, The second request also includes the time and / or reason for stopping billing.

10. The method according to claim 6, characterized in that, The information of the at least two levels of slices is carried in the slice field of the first message.

11. The method according to claim 8, characterized in that, The method further includes: Receive a second message, which is used to request authentication, and the second message carries information about the at least two levels of slices; A third message is sent, which carries user authorization information related to the at least two levels of slices.

12. The method according to claim 6, characterized in that, The method further includes: Receive a fourth message, which carries the billing strategy for the at least two levels of slices.

13. The method according to claim 6, characterized in that, The method further includes: Receive a fifth message, which carries a dynamic authorization related to user-customized services.

14. A billing method applied to a terminal, characterized in that, include: Send a sixth message, which is used to request authentication, and the sixth message carries information about at least two levels of slices; The at least two levels of slicing include at least: a first level slice and a second level slice, wherein the first level slice is a slice based on a first object, and the second level slice is a slice based on a second object based on the first level slice; The information of the at least two levels of slices includes: a first identifier and a second identifier, wherein the first identifier is the identifier of the first level slice of the first object, and the second identifier is the identifier of the second level slice of the first level slice corresponding to the second object; The first identifier is an identifier introduced for the control plane technology of the slice; the second identifier is an identifier introduced for the data plane technology of the slice.

15. The method according to claim 14, characterized in that, The method further includes: A seventh message is received, which carries user authorization information related to the at least two levels of slices.

16. A billing device, applied to network equipment, characterized in that, include: The first sending module is used to send a first message, which is used to request billing processing for the first object corresponding to the first level slice and / or the second object corresponding to the second level slice. The first message carries information about at least two levels of slices, which include at least a first-level slice and a second-level slice. The first-level slice is a slice based on a first object, and the second-level slice is a slice based on a second object based on the first-level slice. The information of the at least two levels of slices includes: a first identifier and a second identifier, wherein the first identifier is the identifier of the first level slice of the first object, and the second identifier is the identifier of the second level slice of the first level slice corresponding to the second object; The first identifier is an identifier introduced for the control plane technology of the slice; the second identifier is an identifier introduced for the data plane technology of the slice.

17. A billing device applied to a server, characterized in that, include: The second receiving module is used to receive a first message, the first message carrying information of at least two levels of slices, wherein the at least two levels of slices include at least: a first level slice and a second level slice, the first level slice is a slice divided based on a first object, and the second level slice is a slice divided based on a second object based on the first level slice; The billing processing module is used to perform billing processing on the first object corresponding to the first level slice and / or the second object corresponding to the second level slice according to the first message. The information of the at least two levels of slices includes: a first identifier and a second identifier, wherein the first identifier is the identifier of the first level slice of the first object, and the second identifier is the identifier of the second level slice of the first level slice corresponding to the second object; The first identifier is an identifier introduced for the control plane technology of the slice; the second identifier is an identifier introduced for the data plane technology of the slice.

18. A billing device, applied to a terminal, characterized in that, include: The fourth sending module is used to send a sixth message, which is used to request authentication and carries information about at least two levels of slices. The at least two levels of slicing include at least: a first level slice and a second level slice, wherein the first level slice is a slice based on a first object, and the second level slice is a slice based on a second object based on the first level slice; The information of the at least two levels of slices includes: a first identifier and a second identifier, wherein the first identifier is the identifier of the first level slice of the first object, and the second identifier is the identifier of the second level slice of the first level slice corresponding to the second object; The first identifier is an identifier introduced for the control plane technology of the slice; the second identifier is an identifier introduced for the data plane technology of the slice.

19. A communication device, characterized in that, It includes a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the method as described in any one of claims 1 to 15.

20. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the method as described in any one of claims 1 to 15.

Images