CN114071386B - Method, device and system for charging of cooperative network side and charging side - Google Patents
Method, device and system for charging of cooperative network side and charging side Download PDFInfo
- Publication number
- CN114071386B CN114071386B CN202010744260.5A CN202010744260A CN114071386B CN 114071386 B CN114071386 B CN 114071386B CN 202010744260 A CN202010744260 A CN 202010744260A CN 114071386 B CN114071386 B CN 114071386B
- Authority
- CN
- China
- Prior art keywords
- charging
- charging request
- request
- ticket
- gateway
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 26
- 230000004044 response Effects 0.000 claims abstract description 49
- 230000002159 abnormal effect Effects 0.000 claims description 65
- 230000006870 function Effects 0.000 claims description 35
- 238000004891 communication Methods 0.000 claims description 14
- 238000003379 elimination reaction Methods 0.000 claims description 10
- 230000008030 elimination Effects 0.000 claims description 5
- 230000003068 static effect Effects 0.000 claims description 4
- 238000010586 diagram Methods 0.000 description 14
- 230000008569 process Effects 0.000 description 6
- 239000000284 extract Substances 0.000 description 4
- 230000006855 networking Effects 0.000 description 2
- 230000005856 abnormality Effects 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000003139 buffering effect Effects 0.000 description 1
- 235000019800 disodium phosphate Nutrition 0.000 description 1
- GVVPGTZRZFNKDS-JXMROGBWSA-N geranyl diphosphate Chemical compound CC(C)=CCC\C(C)=C\CO[P@](O)(=O)OP(O)(O)=O GVVPGTZRZFNKDS-JXMROGBWSA-N 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 239000000463 material Substances 0.000 description 1
- 239000000203 mixture Substances 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/24—Accounting or billing
Landscapes
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Meter Arrangements (AREA)
- Charge And Discharge Circuits For Batteries Or The Like (AREA)
Abstract
The disclosure provides a method, a device and a system for billing at a collaborative network side and a billing side. The session management functional entity sends a first charging request to the charging functional entity so that the charging functional entity forwards the first charging request to the charging equipment, and the charging equipment generates a normal ticket by using the first charging request; after receiving the charging request response sent by the charging function entity, the charging gateway sends the first charging request and the charging request response to the charging gateway so that the charging gateway generates a normal ticket by using the first charging request. After the non-standard network element is deployed in the 5G SA mode, the network side and the charging side simultaneously generate the ticket, and the network side and the charging side do not collide.
Description
Technical Field
The present disclosure relates to the field of charging, and in particular, to a method, an apparatus, and a system for charging on a coordinated network side and a charging side.
Background
The communication between the core network elements in the 5G SA (Stand alone networking) mode adopts service interface communication, and follows HTTP/2 protocol stack. Unlike 4G, the 3GPP (3 rd Generation Partnership Project, third generation partnership project) international standards organization does not introduce CG (Charging Gateway) on the network side in the definition of 5G SA. The operators deploy CG network elements in the 5G SA core network networking due to the fact that the operators need roaming settlement among nationwide provinces, the number of nationwide billing side manufacturers is large, and the intra-provincial network side manufacturers are different from the billing side manufacturers. The CG generates a billing ticket based on a billing message sent from the SMF (Session Management Function ) and stores the billing ticket on the network side. At the same time, the charging side also receives the charging message through CHF (Charging Function ) to charge the user.
Disclosure of Invention
The inventors found through research that CG cannot register on NRF (Network Resource Function ) because CG network element in 5G SA is not a standard network element defined by 3 GPP. Whereby the SMF cannot discover the CG by means of service discovery and send charging messages to the CG. Meanwhile, CHF cannot sense CG state, so that charging loss and cross-weight loss may be caused under the condition of network abnormality.
Accordingly, the present disclosure provides a scheme for billing by a collaborative network side and a billing side, where after a CG of a non-standard network element is deployed in a 5G SA mode, the network side and the billing side generate a ticket at the same time, and at the same time, the network side and the billing side do not collide.
According to a first aspect of embodiments of the present disclosure, there is provided a method for billing on a collaborative network side and a billing side, performed by a session management function entity, including: sending a first charging request to a charging functional entity, so that the charging functional entity forwards the first charging request to charging equipment, and the charging equipment generates a normal ticket by using the first charging request; and after receiving the charging request response sent by the charging function entity, sending the first charging request and the charging request response to a charging gateway so that the charging gateway can generate a normal ticket by using the first charging request.
In some embodiments, in a case that the session management functional entity cannot communicate with the charging functional entity, a second charging request is sent to a charging gateway, where the second charging request includes a first abnormal identifier, so that the charging gateway generates a first abnormal ticket by using the second charging request, and sends the first abnormal ticket to the charging device for charging processing.
In some embodiments, after receiving the charging request response sent by the charging function entity, if the session management function entity cannot communicate with the charging gateway, buffering the first charging request and the charging request response; adding a second abnormal identifier in the first charging request to generate a third charging request under the condition that the session management functional entity and the charging gateway resume communication; and sending the third charging request and the charging request response to a charging gateway so that the charging gateway generates a second abnormal ticket by using the third charging request, and sending the second abnormal ticket to the charging equipment so that the charging equipment uses the first abnormal ticket to carry out repeated elimination processing.
In some embodiments, the session management functional entity is directly connected with the charging gateway by means of static configuration of an IP address, and communicates by adopting an HTTP/2 protocol; the session management functional entity communicates with the charging functional entity through an N40 interface, the N40 interface following a servitization interface protocol.
According to a second aspect of the embodiments of the present disclosure, there is provided a session management function entity for billing on a collaborative network side and a billing side, including: an interface module configured to send a first charging request to a charging function entity, so that the charging function entity forwards the first charging request to a charging device, and the charging device generates a normal ticket by using the first charging request; and is further configured to receive the charging request response sent by the charging function entity; and the cooperative processing module is configured to send the first charging request and the charging request response to a charging gateway after the interface module receives the charging request response, so that the charging gateway generates a normal ticket by using the first charging request.
In some embodiments, the cooperative processing module is configured to send a second charging request to a charging gateway in a case that the interface module cannot communicate with the charging functional entity, where the second charging request includes a first anomaly identifier, so that the charging gateway generates a first anomaly ticket by using the second charging request, and sends the first anomaly ticket to the charging device for charging processing.
In some embodiments, the cooperative processing module is further configured to buffer the first charging request and the charging request response after the interface module receives the charging request response, if communication with the charging gateway is impossible, and add a second abnormal identifier to the first charging request to generate a third charging request, send the third charging request and the charging request response to the charging gateway, so that the charging gateway generates a second abnormal ticket by using the third charging request, and send the second abnormal ticket to the charging device, so that the charging device uses the second abnormal ticket to perform a duplication elimination process.
In some embodiments, the co-processing module is directly connected with the charging gateway by means of static configuration of an IP address, and communicates by adopting an HTTP/2 protocol; the interface module communicates with the charging function entity through an N40 interface, and the N40 interface conforms to a service interface protocol.
According to a third aspect of embodiments of the present disclosure, there is provided a session management functional entity, including: a memory configured to store instructions; a processor coupled to the memory, the processor configured to perform a method according to any of the embodiments described above based on instructions stored in the memory.
According to a fourth aspect of the embodiments of the present disclosure, there is provided a system for billing on a collaborative network side and a billing side, including: a session management function as in any above embodiment; a charging function entity configured to forward a first charging request sent by the session management function entity to a charging device, and send a charging request response to the session management function entity; a charging device configured to generate a normal ticket using the first charging request; and the charging gateway is configured to generate a normal ticket by using the first charging request after receiving the first charging request and the charging request response sent by the session management function entity.
In some embodiments, the charging gateway is further configured to generate a first abnormal ticket by using the second charging request after receiving the second charging request sent by the session management function entity, and send the first abnormal ticket to the charging device for charging processing.
In some embodiments, the charging gateway is further configured to generate a second abnormal ticket by using the third charging request after receiving the third charging request and the charging request response sent by the session management function entity, and send the second abnormal ticket to the charging device, so that the charging device uses the second abnormal ticket to perform a duplication elimination process.
According to a fifth aspect of embodiments of the present disclosure, there is provided a computer readable storage medium, wherein the computer readable storage medium stores computer instructions which, when executed by a processor, implement a method as referred to in any of the embodiments above.
Other features of the present disclosure and its advantages will become apparent from the following detailed description of exemplary embodiments of the disclosure, which proceeds with reference to the accompanying drawings.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the disclosure and together with the description, serve to explain the principles of the disclosure.
The disclosure may be more clearly understood from the following detailed description taken in conjunction with the accompanying drawings in which:
fig. 1 is a flow diagram of a method of collaborative network side and charging side charging according to one embodiment of the present disclosure;
fig. 2 is a schematic diagram of the structure of an SMF entity according to an embodiment of the present disclosure;
fig. 3 is a schematic diagram of a structure of an SMF entity according to another embodiment of the present disclosure;
fig. 4 is a schematic structural diagram of a system for collaborative network side and charging side charging according to an embodiment of the present disclosure;
FIG. 5 is a schematic diagram of a billing process according to one embodiment of the disclosure;
fig. 6 is a schematic diagram of a billing process according to another embodiment of the disclosure;
fig. 7 is a schematic diagram of a billing process according to yet another embodiment of the disclosure.
It should be understood that the dimensions of the various elements shown in the figures are not drawn to actual scale. Further, the same or similar reference numerals denote the same or similar members.
Detailed Description
Various exemplary embodiments of the present disclosure will now be described in detail with reference to the accompanying drawings. The description of the exemplary embodiments is merely illustrative, and is in no way intended to limit the disclosure, its application, or uses. The present disclosure may be embodied in many different forms and is not limited to the embodiments described herein. These embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. It should be noted that: the relative arrangement of parts and steps, the composition of materials, and the numerical values set forth in these examples should be construed as merely illustrative, and not limiting unless specifically stated otherwise.
The use of the terms "comprising" or "including" and the like in this disclosure means that elements preceding the term encompass the elements recited after the term, and does not exclude the possibility of also encompassing other elements.
All terms (including technical or scientific terms) used in this disclosure have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs, unless specifically defined otherwise. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.
Techniques, methods, and apparatus known to one of ordinary skill in the relevant art may not be discussed in detail, but are intended to be part of the specification where appropriate.
Fig. 1 is a flow diagram of a method of collaborative network side and charging side charging according to one embodiment of the present disclosure. In some embodiments, the following method steps of collaborative network side and charging side charging are performed by the SMF entity.
In step 101, a first billing request is sent to the CHF entity so that the CHF entity forwards the first billing request to the billing device, such that the billing device generates a normal ticket using the first billing request, and the CHF entity also sends a billing request response to the SMF entity.
In some embodiments, the SMF entity communicates with the CHF entity over an N40 interface, the N40 interface following a servitization interface protocol.
After receiving the charging request response sent by the CHF entity, the first charging request and the charging request response are sent to the CG in step 102, so that the CG generates a normal ticket using the first charging request.
In some embodiments, the SMF entity is directly connected to the CG by way of a statically configured IP address and communicates using the HTTP/2 protocol.
In the method for billing on the collaborative network side and the billing side provided in the above embodiment, it is possible to achieve that both the network side and the billing side have a normal ticket.
In some embodiments, in a case where the SMF entity cannot communicate with the CHF entity, the SMF entity sends a second charging request to the CG, where the second charging request includes the first abnormal identifier, so that the CG generates a first abnormal ticket using the second charging request, and sends the first abnormal ticket to the charging device for charging processing.
For example, a field rating indicator for identifying an anomaly in the second charging request is filled with 0. And the CG generates a first abnormal ticket after identifying the content of the RatingInductor field in the second charging request. At this time, only the network side has an abnormal ticket, and the charging device extracts the abnormal ticket from the CG to perform charging processing.
In some embodiments, after receiving the charging request response sent by the CHF entity, if the SMF entity cannot communicate with the CG, the SMF entity caches the first charging request and the charging request response. In the case where the SMF entity and CG resume communication, a second anomaly identification is added to the first charging request to generate a third charging request. The SMF entity sends the third charging request and the charging request response to the CG so that the CG generates a second abnormal ticket by using the third charging request, and sends the second abnormal ticket to the charging equipment so that the charging equipment performs repeated processing by using the first abnormal ticket.
For example, after the communication between the SMF entity and the CG is restored, the SMF entity fills 1 in a field for identifying anomalies in the first charging request, so as to obtain a third charging request. The CG generates a second abnormal ticket after identifying the content of the rating indicator field in the third charging request. At this time, the charging side has a normal ticket, the network side has an abnormal ticket, and the charging device extracts the abnormal ticket from the CG to perform duplication elimination.
Fig. 2 is a schematic diagram of the structure of an SMF entity according to an embodiment of the present disclosure. As shown in fig. 2, the SMF entity includes an interface module 21 and a co-processing module 22.
Interface module 21 is configured to send a first billing request to the CHF entity for the CHF entity to forward the first billing request to the billing device such that the billing device generates a normal ticket with the first billing request and is also configured to receive a billing request response sent by the CHF entity.
In some embodiments, interface module 21 communicates with CHF entities over an N40 interface, the N40 interface conforming to a servitization interface protocol.
The co-processing module 22 is configured to send the first charging request and the charging request response to the CG after the interface module 21 receives the charging request response, so that the CG generates a normal ticket using the first charging request.
In some embodiments, the co-processing module 22 is directly connected to the CG by way of a statically configured IP address and communicates using the HTTP/2 protocol.
By the SMF entity provided by the embodiment, the network side and the charging side can both have a normal ticket.
In some embodiments, the co-processing module 22 is configured to send a second charging request to the CG in the event that the interface module 21 is unable to communicate with the CHF entity, where the second charging request includes the first abnormal identifier, so that the CG generates a first abnormal ticket using the second charging request and sends the first abnormal ticket to the charging device for charging processing.
In this case, only the network side has an abnormal ticket, and the charging device extracts the abnormal ticket from the CG to perform charging processing.
In some embodiments, the co-processing module 22 is further configured to buffer the first charging request and the charging request response after the interface module 21 receives the charging request response if the co-processing module 22 cannot communicate with the CG. In the case where the co-processing module 22 and the CG resume communication, a second abnormal identifier is added to the first charging request to generate a third charging request, the third charging request and the charging request response are sent to the CG, so that the CG generates a second abnormal ticket using the third charging request, and the second abnormal ticket is sent to the charging device, so that the charging device performs a duplication elimination process using the second abnormal ticket.
In this case, the charging side has a normal ticket, the network side has an abnormal ticket, and the charging device extracts the abnormal ticket from the CG to perform the duplication elimination process.
Fig. 3 is a schematic diagram of a structure of an SMF entity according to another embodiment of the present disclosure. As shown in fig. 3, the SMF entity comprises a memory 31 and a processor 32.
The memory 31 is used for storing instructions. The processor 32 is coupled to the memory 31. The processor 32 is configured to perform a method as referred to in any of the embodiments of fig. 1 based on the instructions stored by the memory.
As shown in fig. 3, the SMF entity further comprises a communication interface 33 for information interaction with other devices. Meanwhile, the RSMF entity further includes a bus 34, and the processor 32, the communication interface 33, and the memory 31 communicate with each other through the bus 34.
The Memory 31 may include a high-speed RAM (Random Access Memory ) and may further include a Non-Volatile Memory (NVM). Such as at least one disk storage. The memory 31 may also be a memory array. The memory 31 may also be partitioned and the blocks may be combined into virtual volumes according to certain rules.
Further, the processor 32 may be a central processing unit, or may be an ASIC (Application Specific Integrated Circuit ), or one or more integrated circuits configured to implement embodiments of the present disclosure.
The present disclosure also provides a computer-readable storage medium. The computer readable storage medium stores computer instructions that, when executed by a processor, implement a method as referred to in any of the embodiments of fig. 1.
Fig. 4 is a schematic structural diagram of a system for collaborative network side and charging side charging according to an embodiment of the present disclosure. As depicted in fig. 4, the system comprises an SMF entity 41, a CHF entity 42, a CG43 and a charging device 44. The SMF entity 41 is an SMF entity as described in any of the embodiments of fig. 2 or fig. 3.
CHF entity 42 is configured to forward the first charging request sent by SMF entity 41 to charging device 44 and to send a charging request response to SMF entity 41.
The charging device 44 is configured to generate a normal ticket using the first charging request.
CG43 is configured to generate a normal ticket with the first charging request after receiving the first charging request and the charging request response sent by SMF entity 41.
Fig. 5 is a schematic diagram of a billing process according to one embodiment of the disclosure.
In step 501, the smf entity sends a first charging request to a CHF entity.
In step 502, the chf entity sends a first billing request to a billing device.
In step 503, the charging device generates a normal ticket according to the first charging request.
In step 504, the chf entity sends a billing request response to the SMF entity.
In step 505, the smf sends the first charging request and the charging request response to the CG.
At step 506, the cg generates a normal ticket with the first billing request.
In step 507, the cg sends the generated normal ticket to the billing device.
In this case, both the network side and the charging side have a normal ticket, and the charging device can use any normal ticket to perform charging processing.
Fig. 6 is a schematic diagram of a billing process according to another embodiment of the disclosure.
In step 601, in a case where the SMF entity cannot communicate with the CHF entity, the SMF entity sends a second charging request to the CG, where the second charging request includes the first anomaly identification.
For example, a field rating indicator for identifying an anomaly in the second charging request is filled with 0.
At step 602, the cg generates a first abnormal ticket using the second charging request.
In step 603, the cg sends the first abnormal ticket to the billing device.
In step 604, the billing device performs billing processing using the first abnormal ticket.
Fig. 7 is a schematic diagram of a billing process according to yet another embodiment of the disclosure.
In step 701, the smf entity sends a first charging request to a CHF entity.
In step 702, the chf entity sends a first billing request to a billing device.
In step 703, the charging device generates a normal ticket according to the first charging request.
In step 704, the chf entity sends a billing request response to the SMF entity.
In step 705, if the SMF entity cannot communicate with the CG, the SMF entity caches the first charging request and the charging request response.
In step 706, in the event that the SMF entity and CG resume communication, a second anomaly identification is added to the first charging request to generate a third charging request. The SMF entity sends the third charging request and the charging request response to the CG.
For example, the SMF entity fills 1 in a field for identifying anomalies in the first charging request, so as to obtain a third charging request.
In step 707, the cg generates a second abnormal ticket using the third charging request.
At step 708, the cg sends a second abnormal ticket to the billing device.
In step 709, the billing device performs a duplication elimination process using the first abnormal ticket.
By implementing the scheme disclosed by the invention, the network side and the charging side can generate the normal ticket at the same time. Under the abnormal condition of the network, the ticket can be prevented from being lost and the ticket is not repeated in a crossing way, thereby ensuring the normal charging.
In some embodiments, the functional modules described above may be implemented as general-purpose processors, programmable logic controllers (Programmable Logic Controller, abbreviated as PLCs), digital signal processors (Digital Signal Processor, abbreviated as DSPs), application specific integrated circuits (Application Specific Integrated Circuit, abbreviated as ASICs), field programmable gate arrays (Field-Programmable Gate Array, abbreviated as FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or any suitable combination thereof for performing the functions described herein.
Thus, embodiments of the present disclosure have been described in detail. In order to avoid obscuring the concepts of the present disclosure, some details known in the art are not described. How to implement the solutions disclosed herein will be fully apparent to those skilled in the art from the above description.
Although some specific embodiments of the present disclosure have been described in detail by way of example, it should be understood by those skilled in the art that the above examples are for illustration only and are not intended to limit the scope of the present disclosure. It will be understood by those skilled in the art that the foregoing embodiments may be modified and equivalents substituted for elements thereof without departing from the scope and spirit of the disclosure. The scope of the present disclosure is defined by the appended claims.
Claims (11)
1. A method for billing in coordination with a network side and a charging side, performed by a session management function entity, comprising:
sending a first charging request to a charging functional entity, so that the charging functional entity forwards the first charging request to charging equipment, and the charging equipment generates a normal ticket by using the first charging request;
after receiving a charging request response sent by the charging function entity, sending the first charging request and the charging request response to a charging gateway so that the charging gateway can generate a normal ticket by using the first charging request;
after receiving the charging request response sent by the charging function entity, if the session management function entity cannot communicate with the charging gateway, caching the first charging request and the charging request response;
adding a second abnormal identifier in the first charging request to generate a third charging request under the condition that the session management functional entity and the charging gateway resume communication;
and sending the third charging request and the charging request response to a charging gateway so that the charging gateway generates a second abnormal ticket by using the third charging request, and sending the second abnormal ticket to the charging equipment so that the charging equipment uses the second abnormal ticket to carry out repeated elimination processing.
2. The method of claim 1, further comprising:
and under the condition that the session management functional entity cannot communicate with the charging functional entity, sending a second charging request to a charging gateway, wherein the second charging request comprises a first abnormal identifier, so that the charging gateway generates a first abnormal ticket by using the second charging request, and sending the first abnormal ticket to the charging equipment for charging processing.
3. The method according to any one of claims 1-2, wherein,
the session management functional entity is directly connected with the charging gateway through a static IP address configuration mode, and adopts an HTTP/2 protocol for communication;
the session management functional entity communicates with the charging functional entity through an N40 interface, the N40 interface following a servitization interface protocol.
4. A session management functional entity for billing in coordination with a network side and a charging side, comprising:
an interface module configured to send a first charging request to a charging function entity, so that the charging function entity forwards the first charging request to a charging device, and the charging device generates a normal ticket by using the first charging request; the charging function entity is further configured to receive a charging request response sent by the charging function entity;
the coordination processing module is configured to send the first charging request and the charging request response to a charging gateway after the interface module receives the charging request response, so that the charging gateway generates a normal ticket by using the first charging request; and after the interface module receives the charging request response, if communication with the charging gateway is impossible, the interface module caches the first charging request and the charging request response, adds a second abnormal identifier in the first charging request to generate a third charging request, sends the third charging request and the charging request response to the charging gateway so that the charging gateway generates a second abnormal ticket by using the third charging request, and sends the second abnormal ticket to the charging equipment so that the charging equipment uses the second abnormal ticket to perform repeated elimination processing.
5. The session management function of claim 4, wherein,
the cooperative processing module is configured to send a second charging request to a charging gateway under the condition that the interface module cannot communicate with the charging functional entity, wherein the second charging request comprises a first abnormal identifier, so that the charging gateway generates a first abnormal ticket by using the second charging request, and sends the first abnormal ticket to the charging equipment for charging processing.
6. The session management functional entity according to any of claims 4-5, wherein,
the cooperative processing module is directly connected with the charging gateway through a static IP address configuration mode, and adopts an HTTP/2 protocol for communication;
the interface module communicates with the charging function entity through an N40 interface, and the N40 interface conforms to a service interface protocol.
7. A session management functional entity comprising:
a memory configured to store instructions;
a processor coupled to the memory, the processor configured to perform the method of any of claims 1-3 based on instructions stored by the memory.
8. A system for billing in coordination with a network side and a billing side, comprising:
a session management functional entity according to any of claims 4-7;
a charging function entity configured to forward a first charging request sent by the session management function entity to a charging device, and send a charging request response to the session management function entity;
a charging device configured to generate a normal ticket using the first charging request;
and the charging gateway is configured to generate a normal ticket by using the first charging request after receiving the first charging request and the charging request response sent by the session management function entity.
9. The system of claim 8, wherein,
the charging gateway is further configured to generate a first abnormal ticket by using the second charging request after receiving the second charging request sent by the session management function entity, and send the first abnormal ticket to the charging equipment for charging processing.
10. The system of claim 8, wherein,
the charging gateway is further configured to generate a second abnormal ticket by using the third charging request after receiving the third charging request and the charging request response sent by the session management functional entity, and send the second abnormal ticket to the charging device, so that the charging device uses the second abnormal ticket to perform repeated elimination processing.
11. A computer readable storage medium storing computer instructions which, when executed by a processor, implement the method of any one of claims 1-3.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010744260.5A CN114071386B (en) | 2020-07-29 | 2020-07-29 | Method, device and system for charging of cooperative network side and charging side |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010744260.5A CN114071386B (en) | 2020-07-29 | 2020-07-29 | Method, device and system for charging of cooperative network side and charging side |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114071386A CN114071386A (en) | 2022-02-18 |
| CN114071386B true CN114071386B (en) | 2024-01-30 |
Family
ID=80226905
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010744260.5A Active CN114071386B (en) | 2020-07-29 | 2020-07-29 | Method, device and system for charging of cooperative network side and charging side |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114071386B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2023237035A1 (en) * | 2022-06-10 | 2023-12-14 | Telefonaktiebolaget Lm Ericsson (Publ) | Repetitive data optimization in n40 interface |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2019035836A1 (en) * | 2017-08-17 | 2019-02-21 | Nokia Solutions And Networks Oy | Charging support for continuity in next generation networks |
| CN110166961A (en) * | 2018-02-13 | 2019-08-23 | 中兴通讯股份有限公司 | A kind of charging method, device and session management entity |
| CN110417560A (en) * | 2018-04-28 | 2019-11-05 | 华为技术有限公司 | The method, apparatus and system of charging |
| CN111327432A (en) * | 2018-12-14 | 2020-06-23 | 中兴通讯股份有限公司 | Charging processing method and device, storage medium and electronic device |
-
2020
- 2020-07-29 CN CN202010744260.5A patent/CN114071386B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2019035836A1 (en) * | 2017-08-17 | 2019-02-21 | Nokia Solutions And Networks Oy | Charging support for continuity in next generation networks |
| CN110166961A (en) * | 2018-02-13 | 2019-08-23 | 中兴通讯股份有限公司 | A kind of charging method, device and session management entity |
| CN110417560A (en) * | 2018-04-28 | 2019-11-05 | 华为技术有限公司 | The method, apparatus and system of charging |
| CN111327432A (en) * | 2018-12-14 | 2020-06-23 | 中兴通讯股份有限公司 | Charging processing method and device, storage medium and electronic device |
Non-Patent Citations (1)
| Title |
|---|
| S5-186389 Correction of errors from Edithelp";Nokia等;3GPP TSG-SA5 Meeting #121 S5-186389;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114071386A (en) | 2022-02-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110752943B (en) | Distributed fault diagnosis system and method for power transmission line | |
| US8521624B2 (en) | Method for accounting information handling in an interworking | |
| EP3544232A1 (en) | Processing method, device and system for nf component abnormality | |
| CN110177010B (en) | Link switching method and device | |
| CN111211912A (en) | Charging method, device and system | |
| US11612006B2 (en) | Routing method and device | |
| CN112887229B (en) | Session information synchronization method and device | |
| CN105282773B (en) | The configuration method and system of WiFi equipment | |
| WO2018166328A1 (en) | Information processing method, apparatus, computer readable storage medium and electronic device | |
| CN112367257B (en) | Route notification method and device | |
| CN114071386B (en) | Method, device and system for charging of cooperative network side and charging side | |
| US8654643B2 (en) | Wide field indexing for packet tracking | |
| CN105722040A (en) | Service message transmission method, apparatus and system | |
| CN104426816B (en) | A kind of virtual machine communication method and device | |
| EP3796615A1 (en) | Fault tolerance processing method, device, and server | |
| US20090080419A1 (en) | Providing consistent manageability interface to a management controller for local and remote connections | |
| CN112822646A (en) | Message processing method and device, electronic equipment and computer readable storage medium | |
| CN103051484B (en) | Session service processing method, system and Session Border Controll | |
| US11436172B2 (en) | Data frame interface network device | |
| CN113672416B (en) | Method and device for positioning cause of hard buffer leakage | |
| CN102510398A (en) | Request concurrent processing method and device, and server | |
| CN109768868A (en) | Processing method, device and the equipment of ether broadcast frame | |
| CN113923696A (en) | Method and electronic equipment for notifying fault | |
| CN110808909A (en) | Message processing method and device across virtual systems | |
| CN109151863A (en) | Android system network management and system based on routing table |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |