CN116781436A - Charging method, charging device, charging equipment and readable storage medium - Google Patents
Charging method, charging device, charging equipment and readable storage medium Download PDFInfo
- Publication number
- CN116781436A CN116781436A CN202210238170.8A CN202210238170A CN116781436A CN 116781436 A CN116781436 A CN 116781436A CN 202210238170 A CN202210238170 A CN 202210238170A CN 116781436 A CN116781436 A CN 116781436A
- Authority
- CN
- China
- Prior art keywords
- slice
- message
- stage
- charging
- level
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 80
- 238000012545 processing Methods 0.000 claims abstract description 20
- 238000013475 authorization Methods 0.000 claims description 22
- 238000005516 engineering process Methods 0.000 claims description 15
- 238000004891 communication Methods 0.000 claims description 6
- 230000000977 initiatory effect Effects 0.000 claims 2
- 238000010586 diagram Methods 0.000 description 11
- 230000008569 process Effects 0.000 description 9
- 238000004590 computer program Methods 0.000 description 8
- 230000006870 function Effects 0.000 description 8
- 238000007619 statistical method Methods 0.000 description 6
- 230000000694 effects Effects 0.000 description 5
- 238000012986 modification Methods 0.000 description 4
- 230000004048 modification Effects 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 3
- 230000008901 benefit Effects 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
- H04L12/1403—Architecture for metering, charging or billing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
- H04L12/1432—Metric aspects
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
- H04L12/1432—Metric aspects
- H04L12/1439—Metric aspects time-based
-
- 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
Abstract
The embodiment of the application provides a charging method, a charging device, charging equipment and a readable storage medium, wherein the charging method comprises the following steps: a first message is sent, and the first message is 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; the first message carries information of at least two stages of slices, and the at least two stages of slices at least comprise: a first level slice, which is a slice divided based on a first object, and a second level slice, which is a slice divided based on a second object on the basis of the first level slice.
Description
Technical Field
The embodiment of the application relates to the technical field of communication, in particular to a charging method, a charging device, charging equipment and a readable storage medium.
Background
Along with the continuous evolution of cloud network convergence technology driven by the continuous cloud of government enterprise user services, simultaneously, under the guidance of a business emphasis big strategy of an operator 2B, the types of private line services of industry users and government enterprise users are more diversified, including user cloud private lines, user site interview private lines/private networks, cloud interconnection private lines/private networks and the like. Different types of cloud network services or private line services have differentiated requirements on network services, and an IP network is required to support thousands of layered slice services with certain resource guarantees.
Current IP networks are primarily charged for network resource usage, such as bandwidth used, duration used, number of input/output bytes/packet, etc. Such as by remote authentication dial-up user service (Remote Authentication Dial In User Service, radius) protocol as billing management. The current charging scheme can only carry out statistical charging on bandwidth, flow and duration of a certain device and a certain interface, can not distinguish slices with different grades, and further can not meet the charging requirements of multi-level, multi-dimension and multi-scene in the vertical industry.
Disclosure of Invention
The embodiment of the application provides a charging method, a device, equipment and a readable storage medium, which solve the problem that the conventional charging mode cannot meet the charging requirements of multiple layers, dimensions and scenes in the vertical industry.
In a first aspect, a charging method is provided, applied to a network device, and includes:
a first message is sent, and the first message is 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;
the first message carries information of at least two stages of slices, and the at least two stages of slices at least comprise: a first level slice, which is a slice divided based on a first object, and a second level slice, which is a slice divided based on a second object on the basis of the first level slice.
Optionally, the first message includes a first request, where the first request is used to request to start charging of a first object corresponding to the first level slice, and/or a second object corresponding to the second level slice, or the first message includes a second request, where the second request is used to request to stop charging of the first object corresponding to the first level slice, and/or a second object corresponding to the second level slice.
Optionally, the second request further carries the time of stopping charging and/or the reason of stopping charging.
Optionally, the method further comprises:
receiving a sixth message, wherein the sixth message is used for requesting authentication, and the sixth message carries the information of the at least two-stage slices;
and sending a seventh message, wherein the seventh message carries user authorization information related to the at least two-stage slices.
Optionally, the information of the at least two-stage slices is carried in a slice field of the first message.
Optionally, the information of the at least two-stage slice includes: a first identification and a second identification, the first identification being an identification of a first level slice of a first object, the second identification being an identification of a second level slice of the first level slice corresponding to a second object.
Optionally, the first identifier is an identifier introduced by a control plane technology for slicing; the second identifier is an identifier introduced by a data plane technology for slicing.
In a second aspect, a charging method is provided, applied to a server, including:
receiving a first message, wherein the first message carries information of at least two stages of slices, and the at least two stages of slices at least comprise: a first level slice, which is a slice divided based on a first object, and a second level slice, which is a slice divided based on a second object on the basis of the first level slice;
and according to the first message, charging the first object corresponding to the first-stage slice and/or the second object corresponding to the second-stage slice.
Optionally, the first message includes a first request, where the first request is used to request to start charging for a first object corresponding to a first level slice, and/or for charging for a second object corresponding to a second level slice;
according to the first message, charging the first object corresponding to the first-stage slice and/or the second object corresponding to the second-stage slice, including:
And according to the first request, starting to charge a first object corresponding to the first-stage slice and/or a second object corresponding to the second-stage slice.
Optionally, the first message includes a second request, where the second request is used to request to stop charging the first object corresponding to the first level slice, and/or the second request is used to request to stop charging the second object corresponding to the second level slice;
according to the first message, charging the first object corresponding to the first-stage slice and/or the second object corresponding to the second-stage slice, including:
and stopping charging the first object corresponding to the first-stage slice according to the second request, and/or charging the second object corresponding to the second-stage slice.
Optionally, the second request further carries the time of stopping charging and/or the reason of stopping charging.
Optionally, the information of the at least two-stage slices is carried in a slice field of the first message.
Optionally, the method further comprises:
receiving a second message, wherein the second message is used for requesting authentication, and the second message carries the information of the at least two-stage slices;
and sending a third message, wherein the third message carries user authorization information related to the at least two-stage slices.
Optionally, the method further comprises:
and receiving a fourth message, wherein the fourth message carries the charging policy of the at least two-stage slices.
Optionally, the method further comprises:
a fifth message is received, the fifth message carrying a dynamic authorization, the dynamic authorization being associated with a user-customized service.
Optionally, the information of the at least two-stage slice includes: a first identification and a second identification, the first identification being an identification of a first level slice of a first object, the second identification being an identification of a second level slice of the first level slice corresponding to a second object.
Optionally, the first identifier is an identifier introduced by a control plane technology for slicing; the second identifier is an identifier introduced by a data plane technology for slicing.
In a third aspect, a charging method is provided, applied to a terminal, including:
a sixth message is sent, wherein the sixth message is used for requesting authentication, and the sixth message carries the information of the at least two-stage slices;
wherein the at least two-stage slicing comprises at least: a first level slice, which is a slice divided based on a first object, and a second level slice, which is a slice divided based on a second object on the basis of the first level slice.
Optionally, the method further comprises:
and receiving a seventh message, wherein the seventh message carries user authorization information related to the at least two-stage slices.
In a fourth aspect, a charging device is provided, applied to a network device, including:
the first sending module is used for sending a first message, wherein the first message is used for requesting to charge a first object corresponding to the first-stage slice and/or a second object corresponding to the second-stage slice;
the first message carries information of at least two stages of slices, and the at least two stages of slices at least comprise: a first level slice, which is a slice divided based on a first object, and a second level slice, which is a slice divided based on a second object on the basis of the first level slice.
In a fifth aspect, there is provided a charging device applied to a server, including:
the second receiving module is configured to receive a first message, where the first message carries information of at least two stages of slices, and the at least two stages of slices at least include: a first level slice, which is a slice divided based on a first object, and a second level slice, which is a slice divided based on a second object on the basis of the first level slice;
And the charging processing module is used for carrying out charging processing on the first object corresponding to the first-stage slice and/or the second object corresponding to the second-stage slice according to the first message.
A sixth aspect provides a charging apparatus, applied to a terminal, including:
a fourth sending module, configured to send a sixth message, where the sixth message is used to request authentication, and the sixth message carries information of the at least two-stage slices;
wherein the at least two-stage slicing comprises at least: a first level slice, which is a slice divided based on a first object, and a second level slice, which is a slice divided based on a second object on the basis of the first level slice.
In a seventh aspect, there is provided a communication device comprising a processor, a memory and a program or instruction stored on the memory and executable on the processor, which when executed by the processor implements the steps of the method of the first, second or third aspects.
In an eighth aspect, there is provided a readable storage medium having stored thereon a program or instructions which when executed by a processor performs the steps of the method according to the first, second or third aspects.
In the embodiment of the present application, the first message sent by the network device carries information of at least two stages of slices, where the at least two stages of slices at least include: the first-stage slice is a slice divided based on a first object, and the second-stage slice is a slice divided based on a second object on the basis of the first-stage slice, so that the multi-level multi-dimension charging requirement of the vertical industry can be met, and meanwhile, the operator can conveniently carry out overall management statistical analysis on a certain industry and a certain user/application.
Drawings
Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the application. Also, like reference numerals are used to designate like parts throughout the figures. In the drawings:
fig. 1 is one of flowcharts of a charging method provided in an embodiment of the present application;
FIG. 2 is a second flowchart of a charging method according to an embodiment of the present application;
FIG. 3 is a third flowchart of a charging method according to an embodiment of the present application;
FIG. 4 is a fourth flowchart of a charging method according to an embodiment of the present application;
FIG. 5 is a fifth flowchart of a charging method according to an embodiment of the present application;
fig. 6a and fig. 6b are schematic diagrams of a Radius protocol message format according to an embodiment of the present application;
fig. 7 is a schematic diagram of a charging device according to an embodiment of the present application;
FIG. 8 is a second schematic diagram of a billing device according to an embodiment of the present application;
FIG. 9 is a third schematic diagram of a billing device according to an embodiment of the present application;
fig. 10 is a schematic diagram of a communication device according to an embodiment of the present application.
Detailed Description
The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all embodiments of the application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
The terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus. Furthermore, the use of "and/or" in the specification and claims means at least one of the connected objects, e.g., a and/or B, meaning that it includes a single a, a single B, and that there are three cases of a and B.
In embodiments of the application, words such as "exemplary" or "such as" are used to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" or "e.g." in an embodiment should not be taken as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete fashion.
Referring to fig. 1, an embodiment of the present application provides a charging method, where an implementation body of the method may be a network device, for example, a network attached storage (Network Attached Storage, NAS) or a broadband access server (Broadband Remote Access Server, BRAS), and the specific steps include:
step 101: the network equipment sends a first message to a server (or described as a charging server), wherein the first message is used for requesting to charge a first object corresponding to a first-level slice and/or a second object corresponding to a second-level slice;
the first message carries information of at least two-stage slices, and the at least two-stage slices at least comprise: a first level slice, which is a slice divided based on a first object, and a second level slice, which is a slice divided based on a second object on the basis of the first level slice.
In an embodiment of the present application, slices are classified into different levels (or described as layers) according to the charging-related object. If the charging-related object comprises two types, the slice is divided into two levels, namely a first level slice, a second level slice, if the charging-related object comprises three types, the slice is divided into three levels, namely a first level slice, a second level slice and a third level slice, if the charging-related object comprises four types, the slice is divided into four levels, namely a first level slice, a second level slice, a third level slice and a fourth level slice, and so on.
Illustratively, the hierarchy of slices includes two hierarchies, a slice is divided into a first level slice (or described as a first level slice) by a first object, and a second level slice (or described as a second level slice) is obtained by dividing the slice into a second object based on the first level slice.
Also, for example, the slice level may include three levels, where the slice is divided into a first level slice according to a first object, a second level slice is obtained by dividing the slice into a second level slice according to a second object on the basis of the first level slice, and a third level slice is obtained by dividing the slice into a third level slice according to a third object on the basis of the second level slice.
Alternatively, the object may include, but is not limited to, an industry, a user, or an application, etc. For example, if the object includes two types, the first object may be an industry, the second object may be a user or an application, and of course, the method is not limited thereto, and a person skilled in the art may configure the types of the objects to be two, three, four, etc. according to a multi-level multi-dimensional billing requirement or a statistical analysis requirement of the vertical industry.
Taking a two-stage slice as an example, the two-stage slice includes: a first level slice, which is a slice partitioned for an industry (the first level slice has its own exclusive slice resources, such as bandwidth resources), and a second level slice, which is a slice further partitioned for different users or applications within the industry first level slice (each second level slice has its own exclusive slice resources).
In one embodiment of the present application, the first message includes a first request for requesting to start charging of a first object corresponding to the first level slice, and/or a second object corresponding to the second level slice, or the first message includes a second request for requesting to stop charging of the first object corresponding to the first level slice, and/or the second object corresponding to the second level slice.
In one embodiment of the present application, the second request further carries a time to stop charging and/or a reason for stopping charging.
In one embodiment of the application, the method further comprises:
receiving a sixth message from the terminal, wherein the sixth message is used for requesting authentication, and the sixth message carries the information of the at least two-stage slices;
and sending a seventh message to the terminal, wherein the seventh message carries user authorization information related to the at least two-stage slices.
In one embodiment of the application, the information of the at least two-stage slices is carried in a slice field of the first message.
In one embodiment of the present application, the information of the at least two-stage slice includes: a first identification and a second identification, the first identification being an identification of a first level slice of a first object, the second identification being an identification of a second level slice of the first level slice corresponding to a second object.
In one embodiment of the application, the first identity is an identity introduced by a control plane technology for the slice, such as FA (FlexAlgo) ID; the second identification is an identification introduced by the data plane technology for the slice, such as a slice ID.
In the embodiment of the present application, the first message sent by the network device carries information of at least two stages of slices, where the at least two stages of slices at least include: the first-stage slice is a slice divided based on a first object, and the second-stage slice is a slice divided based on a second object on the basis of the first-stage slice, so that the multi-level multi-dimension charging requirement of the vertical industry can be met, and meanwhile, the operator can conveniently carry out overall management statistical analysis on a certain industry and a certain user/application.
Referring to fig. 2, an embodiment of the present application provides a charging method, where an execution body of the method may be a server (or described as a charging server), for example, a network device, a network element or a network function with a charging function, and specific steps include:
step 201: the server receives a first message from the network device, wherein the first message carries information of at least two stages of slices, and the at least two stages of slices at least comprise: a first level slice, which is a slice divided based on a first object, and a second level slice, which is a slice divided based on a second object on the basis of the first level slice;
In an embodiment of the present application, slices are classified into different levels (or described as layers) according to the charging-related object. If the charging-related object includes two types, the slice is divided into two levels, if the charging-related object includes three types, the slice is divided into three levels, if the charging-related object includes four types, the slice is divided into four levels, and so on.
Illustratively, the hierarchy of slices includes two hierarchies, a slice is divided into a first level slice (or described as a first level slice) by a first object, and a second level slice (or described as a second level slice) is obtained by dividing the slice into a second object based on the first level slice.
Also, for example, the slice level may include three levels, where the slice is divided into a first level slice according to a first object, a second level slice is obtained by dividing the slice into a second level slice according to a second object on the basis of the first level slice, and a third level slice is obtained by dividing the slice into a third level slice according to a third object on the basis of the second level slice.
Alternatively, the object may include, but is not limited to, an industry, a user, or an application, etc. For example, if the object includes two types, the first object may be an industry, the second object may be a user or an application, and of course, the object may be configured to be two, three, four or other types by one skilled in the art according to the multi-level multi-dimensional billing requirements or statistical analysis requirements of the vertical industry.
Taking a two-stage slice as an example, the two-stage slice includes: a first level slice, which is a slice partitioned for an industry (the first level slice has its own exclusive slice resources, such as bandwidth resources), and a second level slice, which is a slice further partitioned for different users or applications within the industry first level slice (each second level slice has its own exclusive slice resources).
Step 202: and the server carries out charging processing on the first object corresponding to the first-stage slice and/or the second object corresponding to the second-stage slice according to the first message.
It can be appreciated that the first message may carry, in addition to at least two-stage slice information, original charging-related information, for example, a network duration, an incoming and outgoing byte/packet number, etc., where the at least two-stage slice information may identify which level of slice the current bandwidth, etc. information is for.
In the embodiment of the application, the first message carries the information of at least two-stage slices, so that the subsequent correlation of the charging strategy to the specific user or application of at least two-stage slices is facilitated, and the charging strategies of different application scenes of different industries are different, so that the rich requirements of the vertical industry can be met. For example, according to the first message, a first object corresponding to the first-level slice is subjected to a first charging policy, and/or a second object corresponding to the second-level slice is subjected to charging processing through a second charging policy.
In one embodiment of the present application, the first message includes a first request (or referred to as a start message), for example, see step 5 in fig. 4, where the first request is used to request start (start) of a first object corresponding to a first level slice, and/or charge a second object corresponding to a second level slice;
according to the first message, the server performs charging processing on a first object corresponding to the first-stage slice and/or on a second object corresponding to the second-stage slice, including:
and the server starts a first object corresponding to the first-stage slice according to the first request, and/or starts charging for a second object corresponding to the second-stage slice.
In one embodiment of the present application, the first message includes a second request, for example, see step 7 in fig. 4, for requesting to stop (stop) the first object corresponding to the first level slice, and/or charging the second object corresponding to the second level slice;
according to the first message, the server performs charging processing on a first object corresponding to the first-stage slice and/or on a second object corresponding to the second-stage slice, including:
and stopping charging the first object corresponding to the first-stage slice and/or the second object corresponding to the second-stage slice by the server according to the second request.
Optionally, the second request further carries the time of stopping charging and/or the reason of stopping charging.
For example, the unit of time to stop billing may be days, hours, minutes, or seconds; reasons for stopping billing include, but are not limited to, the user disconnecting, etc.
It will be appreciated that the server may send response messages to the network device for the first request and the second request, for example see step 6 and step 8 in fig. 4.
In one embodiment of the application, the information of the at least two-stage slices is carried in a slice field of the first message.
In one embodiment of the application, the method further comprises:
the server receives a second message from the network equipment, wherein the second message is used for requesting authentication, and the second message carries the information of the at least two-stage slices;
the server sends a third message to the network device, wherein the third message carries user authorization information related to the at least two-stage slices.
In one embodiment of the present application, the method may further include:
the server receives a fourth message from the controller, where the fourth message carries the charging policy of the at least two-stage slice, for example, the at least two-stage slice includes: and the fourth message carries the charging policy of the first level slice and the charging policy of the second level slice. In the embodiment, the content in the charging policy for each level slice is not particularly limited.
It will be appreciated that the interface protocol between the controller and the server also requires the addition of related fields for information representing at least two levels of slices.
In one embodiment of the application, the method further comprises:
the server receives a fifth message from the web portal, the fifth message carrying a dynamic authorization of the at least two-level slice, the dynamic authorization being related to a service of the at least two-level slice newly customized by the user.
For example, when the user has customized a service at a Portal server, the billing server receives a fifth message from the Portal server, the fifth message including information of the service of the at least two-level slice customized by the user at the Portal server.
In one embodiment of the present application, the information of the at least two-stage slice includes: a first identification and a second identification, the first identification being an identification of a first level slice of a first object, the second identification being an identification of a second level slice of the first level slice corresponding to a second object.
In one embodiment of the application, the first identity is an identity introduced by a control plane technology for the slice, such as FA (FlexAlgo) ID; the second identification is an identification introduced by the data plane technology for the slice, such as a slice ID.
The control plane technology for the IP network slice is FlexAlgo (a flexible algorithm that a user can independently create an independent topology and calculate paths in an internal gateway protocol (Interior Gateway Protocols, IGP, abbreviated as FA)), each L3 link corresponds to one or more FA algorithm spaces based on the IGP single topology, the IGP protocol releases the algorithm spaces to form IGP sub-algorithm path spaces, and different algorithm spaces are distinguished on one topology through the FA. The FA algorithm consists of two parts: topology constraints and algorithm logic. The result of the topology constraints is that different sub-topologies are formed. The service may find the corresponding FA-label switched path (Label Switched Paths, LSP) according to a single prefix (prefix) Segment Routing ID (SID) or a list of specific Segment Routes (SRs) based on the FA.
The data plane technology for the IP network slice is to introduce slice identification (SliceID) to guide the data message forwarding. The specific SliceID may be carried by a Hop-by-Hop option extension header (Hop-by-Hop Options Header, HBH) in an internet protocol version 6, internet Protocol Version, IPv 6) header or a segment routing (Segment Routing IPv6, SRv 6) header based on an IPv6 forwarding plane.
Alternatively, flexAlgo will be used as the identification of the first level slice and SliceID as the identification of the second level slice.
In an embodiment of the present application, a first message received by a server carries information of at least two stages of slices, where the at least two stages of slices at least include: the first-stage slice is a slice divided based on a first object, and the second-stage slice is a slice divided based on a second object on the basis of the first-stage slice, so that the multi-level multi-dimension charging requirement of the vertical industry can be met, and meanwhile, the operator can conveniently carry out overall management statistical analysis on a certain industry and a certain user/application.
Referring to fig. 3, an embodiment of the present application provides a charging method, where an execution body of the method may be a terminal, and specific steps include:
step 301: the terminal sends a sixth message to the network equipment, wherein the sixth message is used for requesting authentication, and the sixth message carries the information of the at least two-stage slices;
wherein the at least two-stage slicing comprises at least: a first level slice, which is a slice divided based on a first object, and a second level slice, which is a slice divided based on a second object on the basis of the first level slice.
In one embodiment of the application, the method further comprises:
and the terminal receives a seventh message sent by the network equipment, wherein the seventh message carries user authorization information related to the at least two-stage slices.
In the embodiment of the present application, when the terminal requests authentication, the transmitted sixth message carries information of at least two stages of slices, where the at least two stages of slices at least include: the first-stage slice is a slice divided based on a first object, and the second-stage slice is a slice divided based on a second object on the basis of the first-stage slice, so that the multi-level multi-dimension charging requirement of the vertical industry can be met, and meanwhile, the operator can conveniently carry out overall management statistical analysis on a certain industry and a certain user/application.
As shown in fig. 4, an embodiment of interaction between a terminal, a network device (such as a RADIUS client), a server (such as a RADIUS server), a controller, and a web portal server is illustrated, where the sequence of steps is not limited in this embodiment, for example, step 11 or step 12 may be performed after another step, before another step, or simultaneously with another step.
The network device may be located in a router or access server, such as a network attached storage (Network Attached Storage, NAS) or broadband access server (Broadband Remote Access Server, BRAS), among others.
Referring to fig. 5, a radius protocol charging mode is taken as an example, and the charging flow of the slice is as follows:
1. when a user logs in a RADIUS client (equivalent to network equipment), the user name, the password, the FA ID and the slice ID are sent to the RADIUS client;
2. the RADIUS client receives the user name, the password, the FA ID and the slice ID and sends the user name, the password, the FA ID and the slice ID to a RADIUS server (corresponding to the server);
3. after receiving the legal request, the RADIUS server completes authentication and returns the required user authorization information related to the two-stage slice to the RADIUS client.
4. When the RADIUS client starts to log in, the RADIUS server starts accounting for the user or application within the slice.
2. The charging flow is as follows:
1. if authentication and authorization are successful, the RADIUS server starts accounting.
2. The RADIUS client receives a first request (add FA ID + slice ID attribute). I.e. a message requesting accounting start is sent to the RADIUS server.
3. If the request is legitimate, the RADIUS server records the two-level slice and the user or application information in a database and returns a REPLY message to the RADIUS client.
4. When the user logs out, the RADIUS client receives a second request carrying the stop time and the reason for stopping accounting. I.e. a message requesting accounting stop or termination (FA ID + slice ID) is sent to the RADIUS server.
5. The RADIUS server records the two-level slice and the information that the user or application stops accounting in the database.
6. The interaction between the RADIUS client and RADIUS server is authenticated by a shared key that is never sent over the network. Meanwhile, the user password information between the RADIUS client and the RADIUS server is transmitted on the network after being encrypted, so that the user password is prevented from being stolen on an unsafe network.
Referring to fig. 6a and 6b, a Radius protocol message format is illustrated, a Radius protocol message Attribute (Attribute) field is extended between a Radius client and a Radius server, slice field information is added, and the slice field information is used for carrying at least two-stage slice information such as FA-ID, slice-ID and the like.
Referring to fig. 7, an embodiment of the present application provides a charging apparatus, applied to a network device, where the apparatus 700 includes:
a first sending module 701, configured to send a first message, where the first message is used to request charging processing for a first object corresponding to a first level slice and/or for a second object corresponding to a second level slice;
Wherein the at least two-stage slicing comprises at least: a first level slice, which is a slice divided based on a first object, and a second level slice, which is a slice divided based on a second object on the basis of the first level slice.
In one embodiment of the present application, the first message includes a first request for requesting to start charging of a first object corresponding to the first level slice, and/or a second object corresponding to the second level slice, or the first message includes a second request for requesting to stop charging of the first object corresponding to the first level slice, and/or the second object corresponding to the second level slice.
In one embodiment of the present application, the second request further carries a time to stop charging and/or a reason for stopping charging.
In one embodiment of the application, the apparatus further comprises:
the first receiving module is used for receiving a sixth message, the sixth message is used for requesting authentication, and the sixth message carries the information of the at least two-stage slices;
and the second sending module is used for sending a seventh message, and the seventh message carries user authorization information related to the at least two-stage slices.
The device provided by the embodiment of the application can realize each process realized by the embodiment of the method shown in fig. 1 and achieve the same technical effects, and in order to avoid repetition, the description is omitted here.
Referring to fig. 8, an embodiment of the present application provides a charging device, applied to a server, where the device 800 includes:
a second receiving module 801, configured to receive a first message, where the first message carries information of at least two-stage slices, where the at least two-stage slices at least include: a first level slice, which is a slice divided based on a first object, and a second level slice, which is a slice divided based on a second object on the basis of the first level slice;
and the charging processing module 802 is configured to perform charging processing on a first object corresponding to the first slice and/or a second object corresponding to the second slice according to the first message.
In one embodiment of the present application, the first message includes a first request, where the first request is used to request to start charging for a first object corresponding to a first level slice, and/or for charging for a second object corresponding to a second level slice;
the charging processing module 802 is further configured to: and according to the first request, starting to charge a first object corresponding to the first-stage slice and/or a second object corresponding to the second-stage slice.
In one embodiment of the present application, the first message includes a second request, where the second request is used to request to stop charging the first object corresponding to the first level slice, and/or the second request is used to request to stop charging the second object corresponding to the second level slice;
the charging processing module 802 is further configured to: and stopping charging the first object corresponding to the first-stage slice according to the second request, and/or charging the second object corresponding to the second-stage slice.
In one embodiment of the present application, the second request further carries a time to stop charging and/or a reason for stopping charging.
In one embodiment of the application, the information of the at least two-stage slices is carried in a slice field of the first message.
In one embodiment of the application, the apparatus further comprises:
the third receiving module is used for receiving a second message, the second message is used for requesting authentication, and the second message carries the information of the at least two-stage slices;
and the third sending module is used for sending a third message, and the third message carries user authorization information related to the at least two-stage slices.
In one embodiment of the application, the apparatus further comprises:
And the fourth receiving module is used for receiving a fourth message, and the fourth message carries the charging policy of the at least two-stage slices.
In one embodiment of the application, the apparatus further comprises:
and the fifth receiving module is used for receiving a fifth message, wherein the fifth message carries dynamic authorization, and the dynamic authorization is related to the service customized by the user.
In one embodiment of the present application, the information of the at least two-stage slice includes: a first identification and a second identification, the first identification being an identification of a first level slice of a first object, the second identification being an identification of a second level slice of the first level slice corresponding to a second object.
In one embodiment of the present application, the first identifier is an identifier introduced by a control plane technology for slicing; the second identifier is an identifier introduced by a data plane technology for slicing.
The device provided by the embodiment of the application can realize each process realized by the embodiment of the method shown in fig. 2 and achieve the same technical effects, and in order to avoid repetition, the description is omitted here.
Referring to fig. 9, an embodiment of the present application provides a charging device, applied to a terminal, where the device 900 includes:
A fourth sending module 901, configured to send a sixth message, where the sixth message is used to request authentication, and the sixth message carries information of the at least two stages of slices;
wherein the at least two-stage slicing comprises at least: a first level slice, which is a slice divided based on a first object, and a second level slice, which is a slice divided based on a second object on the basis of the first level slice.
In one embodiment of the application, the apparatus further comprises:
and a sixth receiving module, configured to receive a seventh message, where the seventh message carries user authorization information related to the at least two-stage slice.
The device provided by the embodiment of the application can realize each process realized by the embodiment of the method shown in fig. 3 and achieve the same technical effects, and in order to avoid repetition, the description is omitted here.
As shown in fig. 10, an embodiment of the present application further provides a communication device 1000, including a processor 1001, a memory 1002, and a program or an instruction stored in the memory 1002 and capable of running on the processor 1001, where the program or the instruction implements each process of the method embodiments of fig. 1, 2 or 3 described above when executed by the processor 1001, and achieves the same technical effect. In order to avoid repetition, a description thereof is omitted.
The embodiment of the present application further provides a readable storage medium, where a program or an instruction is stored, where the program or the instruction realizes each process of the method embodiment shown in the foregoing fig. 1 or fig. 2 or fig. 3 when being executed by a processor, and the process can achieve the same technical effect, so that repetition is avoided and no redundant description is given here.
Wherein the processor is a processor in the terminal described in the above embodiment. The readable storage medium includes a computer readable storage medium such as a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk or an optical disk, and the like.
The steps of a method or algorithm described in connection with the present disclosure may be embodied in hardware, or may be embodied in software instructions executed by a processor. The software instructions may be comprised of corresponding software modules that may be stored in RAM, flash memory, ROM, EPROM, EEPROM, registers, hard disk, a removable disk, a read-only optical disk, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. In addition, the ASIC may be carried in a core network interface device. The processor and the storage medium may reside as discrete components in a core network interface device.
Those skilled in the art will appreciate that in one or more of the examples described above, the functions described in the present application may be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, these functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer.
The foregoing embodiments have been provided for the purpose of illustrating the general principles of the present application in further detail, and are not to be construed as limiting the scope of the application, but are merely intended to cover any modifications, equivalents, improvements, etc. based on the teachings of the application.
It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, embodiments of the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the application may take the form of a computer program product on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.
Embodiments of the present application are described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may 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, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
It will be apparent to those skilled in the art that various modifications and variations can be made to the embodiments of the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the embodiments of the present application fall within the scope of the claims and the equivalents thereof, the present application is also intended to include such modifications and variations.
Claims (24)
1. A charging method applied to a network device, comprising:
a first message is sent, and the first message is 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;
the first message carries information of at least two stages of slices, and the at least two stages of slices at least comprise: a first level slice, which is a slice divided based on a first object, and a second level slice, which is a slice divided based on a second object on the basis of the first level slice.
2. The method of claim 1, wherein the first message comprises a first request for initiating charging of 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 for requesting to stop charging the first object corresponding to the first slice and/or the second object corresponding to the second slice.
3. The method according to claim 2, characterized in that the second request also carries the time to stop charging and/or the reason for stopping charging.
4. The method according to claim 1, wherein the method further comprises:
receiving a sixth message, wherein the sixth message is used for requesting authentication, and the sixth message carries the information of the at least two-stage slices;
and sending a seventh message, wherein the seventh message carries user authorization information related to the at least two-stage slices.
5. The method of claim 1, wherein the information of the at least two-stage slices is carried in a slice field of the first message.
6. The method of claim 1, wherein the information of the at least two-stage slices comprises: a first identification and a second identification, the first identification being an identification of a first level slice of a first object, the second identification being an identification of a second level slice of the first level slice corresponding to a second object.
7. The method of claim 6, wherein the first identifier is an identifier introduced for a control plane technique of slicing; the second identifier is an identifier introduced by a data plane technology for slicing.
8. A charging method applied to a server, comprising:
receiving a first message, wherein the first message carries information of at least two stages of slices, and the at least two stages of slices at least comprise: a first level slice, which is a slice divided based on a first object, and a second level slice, which is a slice divided based on a second object on the basis of the first level slice;
and according to the first message, charging the first object corresponding to the first-stage slice and/or the second object corresponding to the second-stage slice.
9. The method according to claim 8, wherein the first message comprises a first request for requesting initiation of charging for a first object corresponding to a first level slice and/or for charging for a second object corresponding to a second level slice;
according to the first message, charging the first object corresponding to the first-stage slice and/or the second object corresponding to the second-stage slice, including:
and according to the first request, starting to charge a first object corresponding to the first-stage slice and/or starting to charge a second object corresponding to the second-stage slice.
10. The method according to claim 8, wherein the first message comprises a second request for requesting to stop charging 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, charging the first object corresponding to the first-stage slice and/or the second object corresponding to the second-stage slice, including:
and according to the second request, stopping charging the first object corresponding to the first-stage slice, and/or stopping charging the second object corresponding to the second-stage slice.
11. The method according to claim 10, characterized in that the second request also carries the time to stop charging and/or the reason for stopping charging.
12. The method of claim 8, wherein the information of the at least two-stage slices is carried in a slice field of the first message.
13. The method of claim 8, wherein the method further comprises:
receiving a second message, wherein the second message is used for requesting authentication, and the second message carries the information of the at least two-stage slices;
and sending a third message, wherein the third message carries user authorization information related to the at least two-stage slices.
14. The method of claim 8, wherein the method further comprises:
and receiving a fourth message, wherein the fourth message carries the charging policy of the at least two-stage slices.
15. The method of claim 8, wherein the method further comprises:
a fifth message is received, the fifth message carrying a dynamic authorization, the dynamic authorization being associated with a user-customized service.
16. The method of claim 8, wherein the information of the at least two-stage slices comprises: a first identification and a second identification, the first identification being an identification of a first level slice of a first object, the second identification being an identification of a second level slice of the first level slice corresponding to a second object.
17. The method of claim 16, wherein the first identifier is an identifier introduced for a control plane technique of slicing; the second identifier is an identifier introduced by a data plane technology for slicing.
18. A charging method applied to a terminal, comprising:
a sixth message is sent, wherein the sixth message is used for requesting authentication, and the sixth message carries at least two-stage slicing information;
wherein the at least two-stage slicing comprises at least: a first level slice, which is a slice divided based on a first object, and a second level slice, which is a slice divided based on a second object on the basis of the first level slice.
19. The method of claim 18, wherein the method further comprises:
and receiving a seventh message, wherein the seventh message carries user authorization information related to the at least two-stage slices.
20. A charging apparatus for use in a network device, comprising:
the first sending module is used for sending a first message, wherein the first message is used for requesting to charge a first object corresponding to the first-stage slice and/or a second object corresponding to the second-stage slice;
The first message carries information of at least two stages of slices, and the at least two stages of slices at least comprise: a first level slice, which is a slice divided based on a first object, and a second level slice, which is a slice divided based on a second object on the basis of the first level slice.
21. A billing apparatus applied to a server, comprising:
the second receiving module is configured to receive a first message, where the first message carries information of at least two stages of slices, and the at least two stages of slices at least include: a first level slice, which is a slice divided based on a first object, and a second level slice, which is a slice divided based on a second object on the basis of the first level slice;
and the charging processing module is used for carrying out charging processing on the first object corresponding to the first-stage slice and/or the second object corresponding to the second-stage slice according to the first message.
22. A charging device applied to a terminal, comprising:
a fourth sending module, configured to send a sixth message, where the sixth message is used to request authentication, and the sixth message carries information of at least two stages of slicing;
Wherein the at least two-stage slicing comprises at least: a first level slice, which is a slice divided based on a first object, and a second level slice, which is a slice divided based on a second object on the basis of the first level slice.
23. A communication device comprising a processor, a memory and a program or instruction stored on the memory and executable on the processor, which when executed by the processor implements the steps of the method of any one of claims 1 to 19.
24. A readable storage medium, characterized in that it has stored thereon a program or instructions which, when executed by a processor, implement the steps of the method according to any of claims 1 to 19.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210238170.8A CN116781436A (en) | 2022-03-11 | 2022-03-11 | Charging method, charging device, charging equipment and readable storage medium |
| PCT/CN2023/080300 WO2023169468A1 (en) | 2022-03-11 | 2023-03-08 | Billing method and apparatus, device, and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210238170.8A CN116781436A (en) | 2022-03-11 | 2022-03-11 | Charging method, charging device, charging equipment and readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116781436A true CN116781436A (en) | 2023-09-19 |
Family
ID=87936044
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210238170.8A Pending CN116781436A (en) | 2022-03-11 | 2022-03-11 | Charging method, charging device, charging equipment and readable storage medium |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN116781436A (en) |
| WO (1) | WO2023169468A1 (en) |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10681589B1 (en) * | 2018-12-03 | 2020-06-09 | At&T Itellectual Property I, L.P. | Vertical slice management and selection leveraging dynamic alliances of access core and service network resources |
| CN113784300A (en) * | 2019-03-07 | 2021-12-10 | 华为技术有限公司 | Method, system and related equipment for carrying out charging processing on network slice client |
| CN113302958B (en) * | 2019-04-26 | 2023-01-06 | 华为技术有限公司 | Communication method and device |
| CN111356207A (en) * | 2020-02-18 | 2020-06-30 | 中国联合网络通信集团有限公司 | Service slice selection method and device |
| CN113973273A (en) * | 2020-07-22 | 2022-01-25 | 中移物联网有限公司 | Charging method and device for network slicing service |
| CN113014425B (en) * | 2021-02-08 | 2023-04-07 | 北京中电飞华通信有限公司 | Companion network slice generation method and device and electronic equipment |
-
2022
- 2022-03-11 CN CN202210238170.8A patent/CN116781436A/en active Pending
-
2023
- 2023-03-08 WO PCT/CN2023/080300 patent/WO2023169468A1/en unknown
Also Published As
| Publication number | Publication date |
|---|---|
| WO2023169468A1 (en) | 2023-09-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6529882B1 (en) | Method for managing group membership in internet multicast applications | |
| KR101260188B1 (en) | Secure node identifier assignment in a distributed hash table for peer-to-peer networks | |
| CN111010372A (en) | Block chain network identity authentication system, data processing method and gateway equipment | |
| KR102124665B1 (en) | Method and apparatus of identifying user risk | |
| US20070130343A1 (en) | Means and method for generating a unique user's identity for use between different domains | |
| CN109474916B (en) | Equipment authentication method, device and machine readable medium | |
| US10965461B1 (en) | Method of verifying telecommunications messaging traffic based on decentralized identifiers | |
| JP2004535697A (en) | Billing method in telecommunications network | |
| US9647876B2 (en) | Linked identifiers for multiple domains | |
| EP3477561A1 (en) | System for goods delivery | |
| US9369873B2 (en) | Network application function authorisation in a generic bootstrapping architecture | |
| CN111132305B (en) | Method for 5G user terminal to access 5G network, user terminal equipment and medium | |
| CN110913011B (en) | Session holding method, session holding device, readable storage medium and electronic device | |
| CN114297678A (en) | Operation method, device, equipment and storage medium of union chain system | |
| CN112235290B (en) | Block chain-based Internet of things equipment management method and first Internet of things equipment | |
| CN107426452B (en) | Internet call method and device | |
| CN116781436A (en) | Charging method, charging device, charging equipment and readable storage medium | |
| US8667564B1 (en) | Mobile internet protocol V6 SIP proxy bootstrapping | |
| CN108055262A (en) | Video conference terminal register method, terminal and gatekeeper | |
| Shin et al. | A verifier-based password-authenticated key exchange using tamper-proof hardware | |
| CN114218558A (en) | Cross-domain identity authentication method and server in secure multi-party computing | |
| CN111404901A (en) | Information verification method and device | |
| CN116743377B (en) | Data processing method, device, equipment and storage medium based on blockchain key | |
| US10841283B2 (en) | Smart sender anonymization in identity enabled networks | |
| RU2604328C1 (en) | Method of secured connection forming in network computer system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |