WO2023173937A1 - 一种计费的方法和通信装置 - Google Patents

一种计费的方法和通信装置 Download PDF

Info

Publication number
WO2023173937A1
WO2023173937A1 PCT/CN2023/073131 CN2023073131W WO2023173937A1 WO 2023173937 A1 WO2023173937 A1 WO 2023173937A1 CN 2023073131 W CN2023073131 W CN 2023073131W WO 2023173937 A1 WO2023173937 A1 WO 2023173937A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
terminal
network element
charging
message
Prior art date
Application number
PCT/CN2023/073131
Other languages
English (en)
French (fr)
Inventor
周晓云
宗在峰
廖婷
郑小春
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2023173937A1 publication Critical patent/WO2023173937A1/zh

Links

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

Definitions

  • the embodiments of the present application relate to the field of communications, and more specifically, to a charging method and a communications device.
  • P-IoT Passive Internet of things
  • the embodiments of the present application provide a charging method and a communication device, which can realize charging in the terminal management process.
  • the first aspect provides a charging method, which can be executed by a terminal management function network element, or can also be executed by a chip or circuit configured in the terminal management function network element. This application is not limited to this.
  • the method includes: receiving a first message from an application network element of the application, the first message being used to request to perform a first operation on the target terminal; and sending a second message, the second message being used to request starting the first operation on the target terminal. Charging of the operation; sending first charging information, the first charging information including execution information of one or more terminals in the target terminal, the first charging information being used to perform the first operation on the one or more terminals process billing.
  • the terminal management function network element can initiate a charging request to the charging network element based on the first message, and after the first operation of one or more terminals is completed, send charging information to the charging network element, Therefore, the charging network element can charge the process of performing the first operation on one or more terminals according to the charging request and the charging information.
  • the charging of the terminal management process can be realized.
  • the execution information of one or more terminals is the information obtained after performing the first operation on one or more terminals.
  • the one or more terminals include a first terminal, and the method further includes: obtaining first information, wherein the first information is used to indicate the first terminal The first operation is completed; or the first information includes execution information of the first terminal.
  • the terminal management function network element can send the execution of the first terminal to the charging network element after receiving an indication that the first operation of the first terminal is completed, or after receiving the execution information of the first terminal. Charging information, so that the charging network element can charge for the process of the first terminal performing the first operation.
  • the one or more terminals include at least two first terminals, and the method further includes: obtaining first information, wherein the first information is used to indicate the first The first operation execution of a terminal is completed; or, the first information includes execution information of the first terminal.
  • the terminal management function network element can send a message to the charging network element after receiving instructions from at least two first terminals that the first operation has been completed, or after receiving execution information from at least two first terminals. Execution charging information of the at least two first terminals, so that the charging network element can charge for the process of the at least two first terminals performing the first operation.
  • the first information comes from a first access network device or an application network element, wherein the first access network device is used to perform the first step on the first terminal. operate.
  • the method of this application can be applied to a variety of different architectures and has strong scalability.
  • the execution information of the first terminal includes at least one of the following: an identification of the first terminal and an execution result of the first operation performed by the first terminal.
  • the first charging information may include execution information of the first terminal, which helps to improve charging accuracy.
  • the one or more terminals include terminals within the coverage area of the first access network device, and the method further includes: receiving a message from the first access network device.
  • the second information wherein the second information is used to indicate that the first operation of the terminal within the coverage area of the first access network device in the target terminal is completed; or, the second information includes the first access network device in the target terminal Execution information of terminals within the coverage area.
  • the terminal management function network element may receive an instruction that the first operation of the terminal within the coverage area of the first access network device is completed, or after receiving an instruction from the terminal within the coverage area of the first access network device. After receiving the execution information of the terminal, the execution information of the terminal in the coverage area of the first access network device is sent to the charging network element, so that the charging network element can execute the first execution information on the terminal in the coverage area of the first access network device.
  • One operation process billing Through this solution, granular charging of access network equipment can be achieved, which helps to improve the flexibility of charging.
  • the one or more terminals include terminals within the coverage area of at least two first access network devices, and the method further includes: receiving signals from at least two first access network devices. Second information of the first access network device, where the second information is used to indicate completion of the first operation of the terminal in the target terminal within the coverage area of the first access network device; or, the second information includes the second information of the target terminal. Execution information of terminals within the coverage area of the first access network device.
  • the terminal management function network element may receive instructions from at least two first access network devices regarding the completion of the first operation of the terminal within the coverage area of the first access network device, or after receiving at least After the two first access network devices have executed information about the terminals in the coverage area of the first access network device, they send the execution information of the terminals in the coverage area of the at least two first access network devices to the charging network element. information, so that the charging network element can charge the terminals in the coverage area of the at least two first access network devices for the process of performing the first operation.
  • the inventory process billing of any number of access network equipment can be realized, which helps to improve the flexibility of billing.
  • the execution information of the terminals in the target terminal within the coverage area of the first access network device includes at least one of the following: the terminal obtained by the first access network device list of identifiers, No. The number of terminals obtained by one access network device, and the execution result of the first operation performed by the terminals obtained by the first access network device.
  • the first charging information may include execution information of terminals in the target terminal within the coverage area of the first access network device, which helps to improve charging accuracy.
  • the method further includes: determining that the first operation of the target terminal is completed; sending a third message, the third message being used to request to close the first operation of the target terminal. of billing.
  • the terminal management function network element can request to turn off the charging of the first operation of the target terminal when the first operation of the target terminal is completed, which can avoid waste of resources.
  • the method further includes: determining one or more access network devices according to the first message; wherein determining that the first operation of the target terminal is completed includes: according to The second information of one or more access network devices determines that the first operation execution of the target terminal is completed, and the second information is used to indicate the first operation execution of the terminal in the target terminal within the coverage area of one or more access network devices. Finish.
  • the method further includes: when receiving the first message, starting a timer for the target terminal to perform the first operation; when the timer times out, sending a third Three messages, the third message is used to request to close the charging of the first operation on the target terminal.
  • the terminal management function network element can use the timer to request to close the charging of the first operation of the target terminal when the timer expires, which can avoid resource waste.
  • the first charging information includes an identification of a first access network device, and the first access network device is used to perform the first step on one or more terminals. operate.
  • the first charging information may include the identification of the first access network device that performs the first operation on one or more terminals, which helps to improve charging accuracy.
  • the method further includes: sending a policy rule to the terminal management user plane function network element, the policy rule being used for the first information or the second information, wherein the terminal management The user plane functional network element is used to transmit execution information of one or more terminals to applications.
  • the terminal management function network element can send the detection rules of the first information or the second information to the terminal management user plane function network element, so that the terminal management user plane function network element can identify the first information or the second information, and further Sending the first information or the second information to the terminal management function network element helps to improve accuracy.
  • the first message and the second message include at least one of the following: instruction information for the first operation, operation parameters corresponding to the first operation, and first instruction information. , the identification information of the target terminal, the identification information of the application, the address information of the application network element, and the first tunnel information, where the first indication information is used to indicate the area where the first operation is to be performed, and the first tunnel information is used to indicate the area of the application.
  • instruction information for the first operation the identification information of the target terminal, the identification information of the application, the address information of the application network element, and the first tunnel information
  • the user plane port through which the server receives data.
  • the second message may include different information in the first message, providing more charging-related information and improving charging performance.
  • the identification information of the target terminal includes at least one of the following information: indication information of any one of the target terminals, the access point to which the identification of the target terminal belongs. The value range, the list of identifiers of the target terminal, the group identifier of the terminal group to which the target terminal belongs, the identification information of the user to which the target terminal belongs, or the identification information of the application to which the target terminal belongs.
  • the identification information of the target terminal can be in a variety of different forms, increasing the flexibility of the solution.
  • the first operation includes at least one of the following operations: querying terminal identification, reading, writing, inactivating, locking, block writing, block erasing, access, encryption , or decrypt.
  • the second aspect provides a charging method, which can be executed by the session management network element, or can also be executed by the chip, chip system or circuit in the session management network element, which is not limited in this application.
  • the method includes: receiving a fourth message, the fourth message is used to request the establishment of a first session, the first session is used to transmit execution information of one or more terminals in the target terminal to perform a first operation, the fourth message includes a An identifier, the first identifier is used to identify the charging of the first operation performed on the target terminal initiated by the terminal management function network element; and a fifth message is sent, the fifth message is used to request to start accounting for the first operation on the target terminal.
  • Charge, the fifth message includes the first identification; send second charging information, the second charging information includes execution information of one or more terminals in the target terminal, the second charging information is used to charge one or more terminals.
  • the process of multiple terminals performing the first operation is billed.
  • the session management network element can initiate a charging request to the charging network element based on the fourth message, and after the first operation of one or more terminals is completed, send the charging information to the charging network element, thereby
  • the charging network element may charge one or more terminals for the process of performing the first operation according to the charging request and the charging information.
  • the execution information of one or more terminals is the information obtained after performing the first operation on one or more terminals.
  • the one or more terminals include a first terminal, and the method further includes: obtaining first information, wherein the first information is used to indicate the first terminal. The first operation is completed; or the first information includes execution information of the first terminal.
  • the session management network element may send the execution plan of the first terminal to the charging network element after receiving an indication that the first operation of the first terminal is completed, or after receiving the execution information of the first terminal.
  • the charging information is collected, so that the charging network element can charge for the process in which the first terminal performs the first operation.
  • the one or more terminals include at least two first terminals, and the method further includes: obtaining first information, wherein the first information is used to indicate the The first operation execution of a terminal is completed; or, the first information includes execution information of the first terminal.
  • the session management network element may send the message to the charging network element after receiving instructions from at least two first terminals that the first operation is completed, or after receiving execution information from at least two first terminals. Execution charging information of at least two first terminals, so that the charging network element can charge for the process of the at least two first terminals performing the first operation.
  • the first information comes from a first access network device or an application network element, wherein the first access network device is used to perform the first step on the first terminal. operate.
  • the method of this application can be applied to a variety of different architectures and has strong scalability.
  • the execution information of the first terminal includes at least one of the following: an identification of the first terminal, an execution result of the first operation performed by the first terminal.
  • the first charging information may include execution information of the first terminal, which helps to improve charging accuracy.
  • the one or more terminals include terminals within the coverage area of the first access network device, and the method further includes: receiving a message from the first access network device.
  • the second information wherein the second information is used to indicate that the first operation of the terminal in the target terminal within the coverage area of the first access network device is completed;
  • the second information includes execution information of terminals in the target terminal within the coverage area of the first access network device.
  • the session management network element may receive an indication that the first operation is completed from the terminal within the coverage area of the first access network device, or after receiving the instruction from the terminal within the coverage area of the first access network device. After executing the execution information, the execution information of the terminals in the coverage area of the first access network device is sent to the charging network element, so that the charging network element can execute the first execution information on the terminals in the coverage area of the first access network device. Operation process billing. Through this solution, granular charging of access network equipment can be achieved, which helps to improve the flexibility of charging.
  • the one or more terminals include terminals within the coverage area of at least two first access network devices, and the method further includes: receiving signals from at least two first access network devices. Second information of the first access network device, where the second information is used to indicate completion of the first operation of the terminal in the target terminal within the coverage area of the first access network device; or, the second information includes the second information of the target terminal. Execution information of terminals within the coverage area of the first access network device.
  • the session management network element may receive instructions from at least two first access network devices regarding completion of the first operation of the terminal within the coverage area of the first access network device, or after receiving instructions from at least two first access network devices. After receiving the execution information of the terminals in the coverage area of the first access network device from the first access network device, sending the execution information of the terminals in the coverage area of the at least two first access network devices to the charging network element. , so that the charging network element can charge the terminals in the coverage area of the at least two first access network devices for the process of performing the first operation.
  • the inventory process billing of any number of access network equipment can be realized, which helps to improve the flexibility of billing.
  • the execution information of the terminals in the target terminal within the coverage area of the first access network device includes at least one of the following: the terminal obtained by the first access network device The identification list, the number of terminals obtained by the first access network device, and the execution result of the first operation performed by the terminal obtained by the first access network device.
  • the first charging information may include execution information of terminals in the target terminal within the coverage area of the first access network device, which helps to improve charging accuracy.
  • the method further includes: sending a sixth message, where the sixth message is used to request to close charging for the first operation of the target terminal.
  • the session management network element can request to turn off the charging of the first operation of the target terminal when the first operation of the target terminal is completed, thereby avoiding waste of resources.
  • the second charging information includes an identification of a first access network device, and the first access network device is used to perform the first step on one or more terminals. operate.
  • the second charging information may include the identification of the first access network device that performs the first operation on one or more terminals, which helps to improve charging accuracy.
  • the method further includes: sending a policy rule to a user plane network element, the policy rule being used for the first information or the second information, wherein the user plane network element uses For transmitting execution information of one or more terminals to the application.
  • the session management network element can send the detection rules of the first information or the second information to the user plane network element, so that the user plane network element can identify the first information or the second information, and further send the third information to the session management network element.
  • Primary information or secondary information helps improve accuracy.
  • the fourth message and the fifth message include at least one of the following: first tunnel information, identification information of the target terminal, and identification information of the application, wherein the One tunnel information Indicates the user plane port on which the application's server receives data.
  • the fifth message may include different information in the fourth message, providing more charging-related information and improving charging performance.
  • the identification information of the target terminal includes at least one of the following information: indication information of any one of the target terminals, the access point to which the identification of the target terminal belongs. The value range, the list of identifiers of the target terminal, the group identifier of the terminal group to which the target terminal belongs, the identification information of the user to which the target terminal belongs, or the identification information of the application to which the target terminal belongs.
  • the identification information of the target terminal can be in a variety of different forms, increasing the flexibility of the solution.
  • the first operation includes at least one of the following operations: querying terminal identification, reading, writing, inactivating, locking, block writing, block erasing, access, encryption , or decrypt.
  • a charging method is provided.
  • the method can be executed by the first user plane network element, or can also be executed by the chip, chip system or circuit in the first user plane network element.
  • This application focuses on Not limited. For the convenience of description, the following description takes the execution by the first user plane network element as an example.
  • the first user plane network element may be a user plane network element in the method described in the first aspect or a terminal management user plane network element in the third aspect.
  • the method includes: receiving first data, the first data including first information or second information; sending the first information or second information,
  • the first information is used to indicate completion of the first operation of the first terminal; or, the first information includes execution information of the first terminal;
  • the second information is used to indicate completion of execution of the first operation by the terminal within the coverage area of the first access network device; or, the second information includes execution information of the terminal within the coverage area of the first access network device.
  • the first user plane network element can forward the received first information or second information, so that the terminal management function network element or the session management network element can obtain the first information or the second information, and then provide the information to the billing network. Yuan sends billing information. Through this solution, it can be used to support the charging of the terminal management process.
  • sending the first information or the second information includes: sending the first information or the second information to the terminal management function network element; or, or, sending the first information or the second information to the session management network element.
  • the first user plane network element is a terminal management user plane function network element or a user plane network element.
  • the method of this application can be applied to a variety of different architectures and has strong scalability.
  • the execution information of the first terminal includes at least one of the following: an identification of the first terminal, an execution result of the first operation performed by the first terminal.
  • the first charging information may include execution information of the first terminal, which helps to improve charging accuracy.
  • the execution information of terminals within the coverage of the first access network device includes at least one of the following:
  • the identification list of terminals obtained by the first access network device the number of terminals obtained by the first access network device, and the execution result of the first operation performed by the terminal obtained by the first access network device.
  • the first charging information may include execution information of terminals in the target terminal within the coverage area of the first access network device, which helps to improve charging accuracy.
  • the method also includes: receiving policy rules, the policy The omission rule is used to detect the first information or the second information.
  • the terminal management user plane function network element can identify the first information or the second information according to the policy rules, and further send the first information or the second information to the terminal management function network element, which helps to improve accuracy.
  • the first operation includes at least one of the following operations: querying terminal identification, reading, writing, inactivating, locking, block writing, block erasing, access, encryption , or decrypt.
  • the fourth aspect provides a charging method, which is executed by a system including a terminal management function network element, a session management network element and a charging network element.
  • the method includes:
  • the terminal management function network element receives a seventh message from the application network element of the application, where the seventh message is used to request to perform the first operation on the target terminal;
  • the terminal management function network element sends an eighth message to the charging network element.
  • the eighth message is used to request to start charging for the first operation of the target terminal.
  • the eighth message includes a first identifier.
  • the first identifier is used to identify Charging initiated by the terminal management function network element to perform the first operation on the target terminal;
  • the terminal management function network element sends a ninth message to the access and mobility management network element.
  • the ninth message is used to request to perform the first operation on the target terminal, and the ninth message includes the first identifier;
  • the access and mobility management network element sends a fourth message to the session management network element.
  • the fourth message is used to request the establishment of a first session.
  • the first session is used to transmit execution information of one or more terminals in the target terminal.
  • the fourth includes the first logo;
  • the session management network element sends a fifth message to the charging network element, the fifth message is used to request to start charging for the first operation of the target terminal, the fifth message includes the first identifier;
  • the charging network element associates the eighth message and the fifth message according to the first identifier.
  • the terminal management function network element can initiate the eighth message to the charging network element based on the first message, and the session management network element can initiate the fifth message to the charging network element based on the fourth message, so that the charging network element can initiate The first identifier manages the eighth message and the fifth message.
  • the one or more terminals include a first terminal, and the method further includes:
  • the session management network element receives first information, the first information is used to indicate completion of the first operation of the first terminal, or the first information includes execution information of the first terminal;
  • the session management network element sends second charging information, where the second charging information includes execution information of the first terminal;
  • the charging network element generates a bill for the first terminal performing the first operation based on the second charging information.
  • the charging information is sent to the charging network element, so that the charging network element can charge the first terminal for performing the first operation based on the charging information.
  • terminal-granular billing can be achieved, which helps improve billing flexibility.
  • the execution information of the first terminal includes at least one of the following: an identification of the first terminal, an execution result of the first operation performed by the first terminal.
  • the first charging information may include execution information of the first terminal, which helps to improve charging accuracy.
  • the one or more terminals include terminals within the coverage area of the first access network device, and the method further includes:
  • the first access network device sends second information to the session management network element.
  • the second information is used to indicate that the first operation of the terminal in the target terminal within the coverage area of the first access network device is completed, or the second information includes Execution information of terminals within the coverage area of the first access network device in the target terminal;
  • the session management network element sends second charging information, where the second charging information includes execution information of terminals within the coverage area of the first access network device;
  • the charging network element generates a bill for the first operation performed by the terminal in the target terminal within the coverage area of the first access network device according to the second charging information.
  • the session management network element may receive an indication that the first operation is completed from the terminal within the coverage area of the first access network device, or after receiving the instruction from the terminal within the coverage area of the first access network device. After executing the execution information, the execution information of the terminals in the coverage area of the first access network device is sent to the charging network element, so that the charging network element can execute the first execution information on the terminals in the coverage area of the first access network device. Operation process billing. Through this solution, granular charging of access network equipment can be achieved, which helps to improve the flexibility of charging.
  • the execution information of the terminals within the coverage area of the first access network device includes at least one of the following: an identification list of the terminal obtained by the first access network device , the number of terminals obtained by the first access network device, and the execution result of the first operation performed by the terminals obtained by the first access network device.
  • the second charging information may include execution information of terminals in the target terminal within the coverage area of the first access network device, which helps to improve charging accuracy.
  • the method further includes: the session management network element sending a sixth message to the charging network element, the sixth message being used to request to close the first operation on the target terminal. of billing.
  • the session management network element can request to turn off the charging of the first operation of the target terminal when the first operation of the target terminal is completed, thereby avoiding waste of resources.
  • the method also includes:
  • the terminal management function network element determines that the first operation of the target terminal is completed; the terminal management function network element sends a tenth request message to the charging network element, and the tenth request message is used to request to close the charging of the first operation of the target terminal.
  • the terminal management function network element can request to turn off the charging of the first operation of the target terminal when the first operation of the target terminal is completed, which can avoid waste of resources.
  • the method further includes: when receiving the seventh message, the terminal management function network element starts a timer for the target terminal to perform the first operation; when the timer expires, In this case, the terminal management function network element sends a tenth request message to the charging network element, where the tenth request message is used to request to close the charging of the first operation of the target terminal.
  • the terminal management function network element can use the timer to request to close the charging of the first operation of the target terminal when the timer expires, which can avoid resource waste.
  • the seventh message and the eighth message include at least one of the following: instruction information for the first operation, operation parameters corresponding to the first operation, first instruction information , the identification information of the target terminal, the identification information of the application, and the first tunnel information, wherein the first indication information is used to indicate the area where the first operation is to be performed, and the first tunnel information is used to indicate the user plane port through which the server of the application receives data. .
  • the eighth message may include different information in the seventh message, providing more charging-related information and improving charging performance.
  • the fourth message and the fifth message include at least one of the following: first tunnel information, identification information of the target terminal, and identification information of the application.
  • the fifth message may include different information in the fourth message, providing more charging-related information and improving charging performance.
  • the identification information of the target terminal includes at least one of the following information: indication information of any one of the target terminals, the access point to which the identification of the target terminal belongs. The value range, the list of identifiers of the target terminal, the group identifier of the terminal group to which the target terminal belongs, the identification information of the user to which the target terminal belongs, or the identification information of the application to which the target terminal belongs.
  • the identification information of the target terminal can be in a variety of different forms, increasing the flexibility of the solution.
  • the first operation includes at least one of the following operations: querying terminal identification, reading, writing, inactivating, locking, block writing, block erasing, access, encryption , or decrypt.
  • a fifth aspect provides a communication device.
  • the communication device includes a processor for implementing the functions of the terminal management function network element in the method described in the first aspect.
  • the communication device may further include a memory coupled to the processor, and the processor is configured to implement the function of the terminal management function network element in the method described in the first aspect.
  • this memory is used to store program instructions and data.
  • the memory is coupled to the processor, and the processor can call and execute program instructions stored in the memory to implement the functions of the terminal management function network element in the method described in the first aspect.
  • the communication device may also include a communication interface, and the communication interface is used for the communication device to communicate with other devices.
  • the communication interface is a transceiver, an input/output interface, or a circuit.
  • the communication device includes: a processor and a communication interface, used to implement the functions of the terminal management function network element in the method described in the first aspect, specifically including:
  • the processor uses the communication interface to communicate with the outside;
  • the processor is used to run a computer program, so that the device implements any method described in the first aspect.
  • the external device may be an object other than the processor or an object other than the device.
  • the communication device is a chip or a chip system.
  • the communication interface may be an input/output interface, interface circuit, output circuit, input circuit, pin or related circuit on the chip or chip system, etc.
  • the processor may also be embodied as a processing circuit or logic circuit.
  • a sixth aspect provides a communication device.
  • the communication device includes a processor for implementing the function of the session management network element in the method described in the second aspect.
  • the communication device may further include a memory coupled to the processor, and the processor is configured to implement the function of the session management network element in the method described in the second aspect.
  • this memory is used to store program instructions and data.
  • the memory is coupled to the processor, and the processor can call and execute program instructions stored in the memory to implement the function of the session management network element in the method described in the second aspect.
  • the communication device may also include a communication interface, and the communication interface is used for the communication device to communicate with other devices.
  • the transceiver may be a communication interface or an input/output interface.
  • the communication device includes: a processor and a communication interface, used to implement the function of the session management network element in the method described in the second aspect, specifically including:
  • the processor uses the communication interface to communicate with the outside;
  • the processor is used to run a computer program, so that the device implements any method described in the second aspect.
  • the external device may be an object other than the processor or an object other than the device.
  • the communication interface may be an input/output interface, an interface circuit, an output circuit, an input circuit, a pin or a related circuit on the chip or chip system. wait.
  • the processor may also be embodied as a processing circuit or logic circuit.
  • a seventh aspect provides a communication device.
  • the communication device includes a processor for implementing the function of the first user plane network element in the method described in the third aspect.
  • the communication device may further include a memory coupled to the processor, and the processor is configured to implement the function of the first user plane network element in the method described in the third aspect.
  • this memory is used to store program instructions and data.
  • the memory is coupled to the processor, and the processor can call and execute program instructions stored in the memory to implement the functions of the first user plane network element in the method described in the third aspect.
  • the communication device may also include a communication interface, and the communication interface is used for the communication device to communicate with other devices.
  • the transceiver may be a communication interface or an input/output interface.
  • the communication device includes: a processor and a communication interface, used to implement the function of the first user plane network element in the method described in the third aspect, specifically including:
  • the processor uses the communication interface to communicate with the outside;
  • the processor is used to run a computer program, so that the device implements any method described in the third aspect.
  • the external device may be an object other than the processor or an object other than the device.
  • the communication interface may be an input/output interface, an interface circuit, an output circuit, an input circuit, a pin or a related circuit on the chip or chip system. wait.
  • the processor may also be embodied as a processing circuit or logic circuit.
  • An eighth aspect provides a computer-readable storage medium on which a computer program is stored.
  • the communication device When the computer program is executed by a communication device, the communication device enables the communication device to implement any of the possible implementations of the first to third aspects. method.
  • a ninth aspect provides a computer program product containing instructions, which when executed by a computer causes a communication device to implement the method in any possible implementation manner of the first to third aspects.
  • a tenth aspect provides a chip.
  • the chip includes a processor and a communication interface.
  • the processor reads instructions stored in the memory through the communication interface and executes the above-mentioned first aspect, or any of the above-mentioned implementations of the first aspect, or the third aspect.
  • the chip also includes a memory, in which computer programs or instructions are stored.
  • the processor is used to execute the computer programs or instructions stored in the memory.
  • the processor is used to execute The above-mentioned first aspect, or any one of the above-mentioned implementations of the first aspect, or the second aspect or any one of the above-mentioned implementations of the second aspect, or the third aspect or any one of the above-mentioned implementations of the third aspect. method.
  • Figure 1 is a schematic diagram of a communication system suitable for embodiments of the present application.
  • Figure 2 shows a schematic diagram of the network architecture of a passive Internet of Things.
  • FIG. 3 is a schematic diagram of a charging method provided by an embodiment of the present application.
  • Figure 4 is another schematic diagram of a charging method provided by an embodiment of the present application.
  • Figure 5 is another schematic diagram of a charging method provided by an embodiment of the present application.
  • Figure 6 is another schematic diagram of a charging method provided by an embodiment of the present application.
  • Figure 7 is another schematic diagram of a charging method provided by an embodiment of the present application.
  • Figure 9 is another schematic diagram of a charging method provided by an embodiment of the present application.
  • Figure 10 is another schematic diagram of a charging method provided by an embodiment of the present application.
  • Figure 12 is another schematic diagram of a charging method provided by an embodiment of the present application.
  • Figure 13 is another schematic diagram of a charging method provided by an embodiment of the present application.
  • Figure 15 is a schematic block diagram of a communication device provided by this application.
  • Figure 16 is another schematic diagram of the communication device provided by this application.
  • the technical solutions provided by this application can be applied to various communication systems, such as fifth generation (5th generation, 5G) or new radio (NR) systems, long term evolution (LTE) systems, LTE frequency division Duplex (frequency division duplex, FDD) system, LTE time division duplex (TDD) system, etc.
  • 5G fifth generation
  • NR new radio
  • LTE long term evolution
  • LTE frequency division Duplex frequency division duplex
  • TDD time division duplex
  • the technical solution provided by this application can also be applied to future communication systems, such as the sixth generation mobile communication system.
  • D2D device-to-device
  • V2X vehicle-to-everything
  • M2M machine-to-machine
  • MTC machine type communication
  • IoT Internet of things
  • Figure 1 shows a network architecture suitable for embodiments of the present application.
  • the network architecture 100 takes the 5G system (the 5th generation system, 5GS) as an example.
  • the network architecture may include but is not limited to: user equipment (UE) 101, (radio) access network equipment (RAN) 102, user plane function (UPF) network element 103 , data network (DN) network element 104, access and mobility management function (AMF) network element 105, session management function (SMF) network element 106, authentication server function (authentication server function, AUSF) network element 107, service communication proxy (SCP) network element 108, network data analytics function (NWDAF) network element 109, network exposure function (NEF) ) network element 110, charging function (CHF) network element 111, policy control function (PCF) network element 112, unified data management (UDM) network element 113, application function ( application function, AF) network element 114, etc.
  • UE user equipment
  • RAN radio access network equipment
  • UPF user plane function
  • DN data network
  • AMF access and mobility management function
  • SMF session
  • DN can be the Internet
  • UPF, AUSF, AMF, SMF, SCP, NWDAF, NEF, CHF, PCF, UDM, and AF belong to the network elements in the core network.
  • the core network can say It is the 5G core network (5GC or 5GCN).
  • User equipment (UE) 101 can be called terminal equipment, terminal, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, wireless communication equipment , user agent or user device.
  • the UE may also be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), or a device with wireless communication capabilities
  • Handheld devices computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, terminal devices in 5G networks or future evolved public land mobile communications networks (public land mobile network, PLMN) or non-terrestrial Network (non-terrestrial networks, NTN) terminal equipment, etc.
  • PLMN public land mobile network
  • NTN non-terrestrial networks
  • IoT Internet of Things
  • the terminal can also be an unmanned aerial vehicle (unmanned aerial vehicle or uncrewed aerial vehicle, UAV) with communication capabilities.
  • UAV unmanned aerial vehicle
  • the terminal can receive or send data by acquiring energy.
  • Energy can be obtained through radio frequency, radio, solar energy, light energy, wind energy, water energy, thermal energy, kinetic energy, etc.
  • This application does not limit the way passive, semi-active, or semi-passive terminals obtain energy. It can be understood that when the terminal is a passive terminal, the terminal itself is not equipped with or does not rely on power devices such as batteries, but obtains energy from the environment for functions such as data sensing, transmission, and distributed computing.
  • the terminal When the terminal is a semi-active terminal, the terminal can have a built-in battery, but the battery is used to power the internal circuit and is not used to actively transmit signals.
  • the terminal When the terminal is a semi-passive terminal, the terminal can have a built-in capacitor; the capacitor can store the energy obtained by the terminal; for example, the terminal can obtain energy by obtaining solar energy and store it in the capacitor.
  • the tag involved in this application may be in the form of a tag, or may be in the form of any terminal.
  • terminal equipment and access network equipment can communicate with each other using certain air interface technology (such as NR or LTE technology, etc.).
  • Terminal devices can also communicate with each other using some air interface technology (such as NR or LTE technology, etc.).
  • the device used to implement the functions of the terminal device may be a terminal device, or may be a device capable of supporting the terminal device to implement the function, such as a chip system or a chip, and the device may be installed in the terminal device.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • (Radio) access network ((R)AN) device 102 It can provide authorized users in a specific area with the function of accessing a communication network. Specifically, it can include the third generation partner program (3rd generation). Wireless network devices in partnership project (3GPP) networks can also include access points in non-3GPP (non-3GPP) networks. The following uses AN equipment representation for convenience of description.
  • AN equipment can adopt different wireless access technologies.
  • 3GPP access technologies for example, wireless access technologies used in third generation (3G), fourth generation (4G) or 5G systems
  • non- 3GPP (non-3GPP) access technology refers to access technology that complies with 3GPP standard specifications.
  • the access network equipment in the 5G system is called next generation Node Base station (gNB) or next generation wireless access network (next generationradioaccess).
  • gNB next generation Node Base station
  • NG-RAN next generation wireless access network
  • Non-3GPP access technologies may include air interface technology represented by access point (AP) in wireless fidelity (WiFi), global interoperability for microwave access (WiMAX), code Code division multiple access (CDMA), etc.
  • AP access point
  • WiFi wireless fidelity
  • WiMAX global interoperability for microwave access
  • CDMA code Code division multiple access
  • AN equipment can allow interconnection and interworking between terminal equipment and the 3GPP core network using non-3GPP technologies.
  • AN equipment can be responsible for wireless resource management, quality of service (QoS) management, data compression and encryption on the air interface side.
  • AN equipment provides access services to terminal equipment, thereby completing the forwarding of control signals and user data between the terminal equipment and the core network.
  • QoS quality of service
  • AN equipment may include, for example, but is not limited to: macro base station, micro base station (also known as small station), radio network controller (radio network controller, RNC), Node B (Node B, NB), base station controller (base station controller) , BSC), base transceiver station (BTS), home base station (for example, home evolved NodeB, or home Node B, HNB), baseband unit (baseband unit, BBU), AP in WiFi system, wireless relay Node, wireless backhaul node, transmission point (TP) or transmission and reception point (TRP), etc., can also be a gNB or transmission point (TRP or TP) in the 5G (such as NR) system , one or a group (including multiple antenna panels) antenna panels of a base station in a 5G system, or it can also be a network node that constitutes a gNB or transmission point, such as a distributed unit (DU), or next-generation communications Base stations in 6G systems, etc.
  • RNC radio network controller
  • User plane network element used for packet routing and forwarding and quality of service (QoS) processing of user plane data.
  • QoS quality of service
  • the user plane network element may be a user plane function (UPF) network element 103.
  • UPF user plane function
  • user plane network elements can still be UPF network elements, or they can have other names, which are not limited in this application.
  • Data network used to provide a network for transmitting data.
  • the data network may be a data network (DN) 104.
  • the data network may still be a DN, or may have other names, which are not limited in this application.
  • Access and mobility management network element used for routing and forwarding user plane data, or quality of service (QoS) processing of user plane data, etc.
  • QoS quality of service
  • the access and mobility management network element may be an access and mobility management function (AMF) network element 105.
  • AMF access and mobility management function
  • the access and mobility management network element can still be an AMF network element, or it can also have other names, which is not limited in this application.
  • Session management network element It can be used for session management, Internet protocol (IP) address allocation and management of terminal devices, selection of endpoints that can manage user plane functions, policy control and charging function interfaces, and downlink data notifications. wait.
  • IP Internet protocol
  • the session management network element may be a session management function (session management function, SMF) network element 106.
  • SMF session management function
  • the session management network element can still be an SMF network element, or it can also have other names, which is not limited in this application.
  • Authentication server network element mainly responsible for providing authentication services.
  • the authentication server network element may be an authentication server function (AUSF) network element 107.
  • AUSF authentication server function
  • the authentication server network element can still be AUSF
  • a network element may also have other names, which are not limited in this application.
  • Service communication agent network element Mainly responsible for indirect communication between network elements and corresponding network element services.
  • the service communication proxy network element may be a service communication proxy (SCP) network element 108.
  • SCP service communication proxy
  • the session management network element can still be an SCP network element, or it can also have other names, which is not limited in this application.
  • Network data analysis network element responsible for network data collection, statistics, analysis and decision-making feedback, and provides network data collection and analysis functions based on technologies such as big data and artificial intelligence.
  • the network data analysis network element may be a network data analytics function (NWDAF) network element 109.
  • NWDAF network data analytics function
  • the session management network element can still be an NWDAF network element, or it can also have other names, which are not limited in this application.
  • Network opening network element mainly used to support the opening of capabilities and events.
  • the network exposure network element may be a network exposure function (NEF) network element 110.
  • NEF network exposure function
  • future communication systems network open network elements can still be NEF network elements, or they can also have other names, which are not limited in this application.
  • Charging network element As a control node for online charging and/or offline charging, it performs online charging and/or offline charging rate processing for various services of user equipment.
  • the charging network element may be a charging function (CHF) network element 111.
  • CHF network element may be a converged charging function (converged charging function) network element or an offline charging function ( offline only charging function) network element.
  • the charging network element can still be a CHF network element, or it can also have other names, which is not limited in this application.
  • Policy control network element A unified policy framework used to guide network behavior, providing policy rule information for network network elements (such as AMF, SMF network elements, etc.) or terminal devices.
  • the policy control network element may be a policy control function (PCF) network element.
  • PCF policy control function
  • the policy control network element can still be a PCF network element, or it can also have other names, which is not limited in this application.
  • Data management network element used to process terminal device identification, access authentication, registration and mobility management, etc.
  • the data management network element may be a unified data management (UDM) network element 113.
  • UDM unified data management
  • future communication systems unified data management can still be a UDM network element, or it can also have other names, which is not limited by this application.
  • Application network element used for data routing affected by applications, access to network open function network elements, and interaction with the policy framework for policy control, etc.
  • the application network element may be an application function (AF) network element.
  • AF application function
  • the application network element may still be the AF network element 114, or may have other names, which are not limited in this application.
  • the above network elements or functions can be network elements in hardware devices, software functions running on dedicated hardware, or virtualization functions instantiated on a platform (for example, a cloud platform).
  • a platform for example, a cloud platform.
  • the specific forms of the above network elements are not limited.
  • the AMF, SMF, UPF, PCF, NEF, etc. shown in Figure 1 can be understood as network elements used to implement different functions, and can, for example, be combined into network slices as needed. These network elements can be independent devices or integrated into the same device to implement different functions.
  • the access and mobility management network element is the AMF network element
  • the session management network element is the SMF network element
  • the policy control network element is the AF network element as an example.
  • AMF AMF
  • SMF SMF
  • AF AF
  • the AMF described later in this application can be replaced by the access and mobility management network element
  • the SMF can be replaced by the session management network element
  • the AF can be replaced by the application network element.
  • each network element can communicate with each other through interfaces.
  • N1 is the interface between UE101 and AMF105
  • N2 is the interface between (R)AN102 and AMF105, used for sending (non-access stratum, NAS) messages, etc.
  • N3 is the interface between RAN102 and UPF103, used for Transmit user plane data, etc.
  • N4 is the interface between SMF106 and UPF103, used to transmit information such as tunnel identification information of the N3 connection, data cache indication information, and downlink data notification messages
  • N6 interface is the interface between UPF103 and DN104 Interface, used to transmit user plane data, etc.
  • N9 is the interface between UPFs.
  • Namf is the service-based interface shown by AMF105
  • Nsmf is the service-based interface shown by SMF106
  • Nausf is the service-based interface shown by AUSF107
  • Nnwdaf is the service-based interface shown by NWDAF109
  • Nnef is the service-based interface shown by NEF110
  • Nchf is the service-based interface displayed by CHF111
  • Npcf is the service-based interface displayed by PCF112
  • Nudm is the service-based interface displayed by UDM113
  • Naf is the service-based interface displayed by AF114.
  • network architecture shown in Figure 1 is only an exemplary illustration, and the network architecture applicable to the embodiment of the present application is not limited thereto. Any network architecture that can realize the functions of each of the above network elements is applicable to the embodiment of the present application.
  • passive Internet of things (P-IoT) tags e.g., radio frequency identification (RFID), also known as passive tags
  • RFID radio frequency identification
  • passive Internet of Things means that some network nodes can be passive. These nodes themselves are not equipped with or do not mainly rely on power devices such as batteries. Instead, they obtain energy from the environment for functions such as data sensing, transmission, and distributed computing.
  • Application scenarios of passive IoT can be:
  • Figure 2 shows a schematic diagram of the network architecture of a passive Internet of Things. As shown in Figure 2, the network architecture includes passive tags, readers and operation requesters.
  • the card reader can also be called a reader or a reader/writer.
  • the reader interacts with passive tags through radio frequency signals or wireless signals.
  • the operation requester can be an application server (server) or an application function (AF).
  • the operation requester can be understood as the device that sends the operation instructions.
  • the operation requester corresponds to a certain type of user, which can include enterprises, tenants, third parties, or companies without restrictions. Among them, if the operation requester corresponds to a certain type of user, it can be understood that the operation requester belongs to this type of user and is managed by this type of user.
  • the card reader can manage passive tags according to the instructions of the operation requester.
  • the so-called tag management can also be called tag inventory, including but not limited to at least one of the following: query tags Identify, perform read operations, write operations, access operations or kill operations on tags.
  • query tags Identify perform read operations, write operations, access operations or kill operations on tags.
  • label can also be understood as a terminal.
  • the read operation is to read data from the tag.
  • the write operation is to write the data into the storage area of the tag. Invalidation operation, even if the label is invalid. After the invalidation operation is completed, the tag will become invalid and may no longer be inventoried or perform other operations, such as message interaction with the invalid tag.
  • the passive IoT tag is used as a terminal device.
  • Enterprises with tag management needs use the deployed third-generation partner program ( The 3rd generation partnership project (3GPP) network completed the inventory of passive IoT tags.
  • 3GPP 3rd generation partnership project
  • this application proposes a charging method and communication device, which can realize charging in the tag inventory process.
  • tags in the network architecture can be semi-active tags, semi-passive tags or active tags.
  • FIG 3 is a schematic diagram of a charging method provided by an embodiment of the present application. As shown in Figure 3, the method 300 includes the following steps.
  • the application network element AF of the application sends the first message to the terminal management function network element, and accordingly, the terminal management function network element receives the first message.
  • the terminal management functional network element involved in the embodiment of this application can be a newly added functional network element independently established in the 5G core network (5G core, 5GC), or it can be co-located with existing network elements in the 5GC.
  • network element for example, co-located with NEF or AMF.
  • the terminal management function network element co-located with an existing network element can be understood as an enhancement of the function of an existing network element, so that the existing network element
  • the network element has the function of terminal management.
  • the terminal management function network element may also be called the terminal management control plane function network element, which is used to process and send and receive signaling in the terminal management process.
  • the first message is used to request to perform a first operation on the target terminal.
  • the first message can be understood as a request message for requesting the terminal management function network element to inventory the target terminal, and can be called: an inventory request message.
  • inventory refers to performing the first operation on the target terminal.
  • the first operation includes at least one of the following: querying terminal identification, reading, writing, inactivating, locking, block writing, block erasing, access, encryption, decryption, etc.
  • the first message may include at least one of the following: instruction information for the first operation, operation parameters corresponding to the first operation, first instruction information, identification information of the target terminal, identification information of the application, address information of the application network element, first Tunnel information.
  • the instruction information of the first operation is used to indicate the first operation to be performed, including but not limited to:
  • the identifier of the first operation The identifier of the first operation, the value interval to which the identifier of the first operation belongs, the list of identifiers of the first operation, the group identifier of the operation group to which the first operation belongs, etc.
  • the operation to be performed includes an operation, and the identifier of the operation is operation #1.
  • the above-mentioned indication information of the first operation may be the identifier of the first operation, such as operation #1.
  • the operation to be performed includes three operations, and the identifiers of the three operations are operation #1, operation #2, and operation #3 respectively.
  • the above-mentioned instruction information of the first operation may be a list of operation identifiers, such as: operation #1, Operation #2 and Operation 3.
  • the operation to be performed includes three operations, and the three operations belong to an operation group.
  • the group identifier of the operation group is operation group #1.
  • the above-mentioned indication information of the first operation may be the group identifier of the operation group to which the operation belongs. , such as, operation group #1.
  • the above-mentioned first operation may include one or more operations.
  • the instruction information of the above-mentioned first operation may include respectively Instruction information indicating the multiple operations (eg, instruction information indicating operation #1 and instruction information indicating operation #2).
  • the first message may not include the instruction information of the first operation.
  • the AF does not have a command to perform the operation; for another example, the first operation defaults to querying the terminal identification, and there is no need to go through the first operation. instructions for additional instructions.
  • the first message when the instruction information of the first operation indicates that the first operation is an operation other than querying the terminal identity, the first message also includes operation parameters corresponding to the first operation.
  • the instruction information of the first operation may be called a read command.
  • the operation parameters include the storage area to be read, the starting word address of the storage area to be read, the number of words, etc.
  • the instruction information of the first operation may be called a write command.
  • the operation parameters include the storage area to be written, the starting word of the storage area to be read, and the data to be written.
  • the same write information may be carried for all target terminals, or different write information may be carried for different target terminals.
  • the first indication information is used to indicate an area where the first operation is to be performed.
  • the area in which the first operation is to be performed indicated by the first indication information includes the location where the target terminal to be inventoried is located, and the first indication information includes but is not limited to geographical location, municipal location, and 3GPP location information, for example,
  • the location information of 3GPP can be tracking area (trace area, TA) list (list), cell list (cell list), etc.
  • the target terminals to be inventoried include three terminals, which are respectively located in cell #1, cell #2 and cell #3.
  • the above-mentioned first indication information may be the 3GPP location information of the terminal, such as cell #1 , cell#2 and cell#3.
  • the specific form used to indicate the first indication information is not limited in the embodiments of the present application, as long as it can indicate the location of the target terminal to be inventoried.
  • the identification information of the target terminal is used to indicate the target terminal to be inventoried.
  • the identification information of the target terminal includes but Not limited to: the indication information of any one of the target terminals, the value interval to which the target terminal's identification belongs, the list of target terminal identifications, the group identification of the terminal group to which the target terminal belongs, the identification information of the user to which the target terminal belongs, the target terminal The type or the identification information of the application to which the target terminal belongs, etc.
  • the target terminals to be inventoried include three terminals, and the identifiers of the three terminals are terminal #1, terminal #2, and terminal #3 respectively.
  • the identification information of the target terminals mentioned above can be a list of terminal identifiers, for example, terminal # 1. Terminal #2 and Terminal 3.
  • the target terminals to be inventoried include three terminals, and the identifiers of the three terminals are 100, 101, and 102 respectively.
  • the above identification information of the target terminal may be a range of terminal identifiers, such as 100 to 102.
  • the target terminals to be inventoried include three terminals, and the identifiers of the three terminals are terminal #1, terminal #2 and terminal #3 respectively.
  • the indication information for any one of the target terminals refers to inventory of all three terminals.
  • the terminals to be inventoried include three terminals, and the three terminals belong to a terminal group.
  • the group identifier of the terminal group is terminal group #1.
  • the identification information of the target terminal may be the group identifier of the terminal group to which the target terminal belongs. , such as terminal group #1.
  • the terminals to be inventoried include three terminals, and the three terminals belong to one user, and the user ID of this user is user #1.
  • the identification information of the target terminal may be the ID of the user to which the target terminal belongs, for example, user #1.
  • the terminals to be inventoried include three terminals, and all three terminals are passive terminals or semi-passive terminals.
  • the above identification information of the target terminal may be a passive terminal or a semi-passive terminal.
  • the terminals to be inventoried include three terminals, and the three terminals belong to one application, and the application identifier of the application is application #1.
  • the identification information of the target terminal may be the identifier of the application to which the target terminal belongs, for example, application #1. 1.
  • the first message may not include the identification information of the target terminal.
  • the first message may include the first instruction information, and the first instruction information may be used to indicate an inventory of the terminals in a certain area.
  • the first message only triggers the inventory process, and the specific target terminals for inventory may be all terminals managed by the terminal management function network element.
  • the first message may also include identification information of the target terminal without including the first indication information.
  • the identification information of the application is used to identify the application that initiated the inventory request.
  • the identifier of the AF that initiated the inventory request is AF#1, and the above-mentioned application identifier may be AF#1.
  • the address information of the application network element may also be called a notification address, which is used to represent the address where the AF receives terminal information and command execution results. For example, the address of AF.
  • the first tunnel information indicates a user plane port through which the application server receives data.
  • the first tunnel information may indicate the address of the application server.
  • the first message may also include an association identifier, and the association identifier is used to associate the first message with a response message to the first message.
  • the first message may not include the first tunnel information.
  • the first message includes the address information of the application network element, and the address information of the application network element indicates that the execution result of the first operation passes through Control plane signaling is sent to the address of the application network element.
  • the first message may not include the address information of the application network element.
  • the first message includes the first tunnel information, and the first tunnel information indicates that the execution result of the first operation passes through the user plane. Data sent to The application's server.
  • S320 The terminal management function network element sends the second message to the charging network element, and accordingly, the charging network element receives the second message.
  • the charging network element can be a converged charging function network element or an offline charging function network element, which is not limited by this application.
  • the second message is used to request to start charging for the first operation on the target terminal. That is, the second step is used to start charging for the inventory request initiated in S310.
  • the second message may be a converged charging creation request (Nchf_ConvergedCharging_Create Request) message, and the requested universal resource identifier (URI) is ⁇ apiRoot ⁇ /nchf-convergedcharging/ ⁇ apiVersion ⁇ /chargingdata.
  • the charging network element creates the corresponding individual charging data resource (Individual Charging Data Resource) based on the second message, and generates the corresponding URI#1.
  • URI#1 is ⁇ apiRoot ⁇ /nchf-convergedcharging/ ⁇ apiVersion ⁇ /chargingdata / ⁇ ChargingDataRef1 ⁇ .
  • the charging network element returns URI#1 to the terminal management function network element.
  • the second message may also be an offline charging creation request (Nchf_OfflineOnlyCharging_CreateRequest) message, and the request URI is ⁇ apiRoot ⁇ /nchf-offlineonlycharging/ ⁇ apiVersion ⁇ /offlinechargingdata.
  • the charging network element creates corresponding individual offline charging data (Individual Offline Only Charging Data) based on the second message, and generates the corresponding resource identifier URI#2.
  • URI#2 is ⁇ apiRoot ⁇ /nchf-offlineonlycharging/ ⁇ apiVersion ⁇ /offlinechargingdata/ ⁇ OfflineChargingDataRef2 ⁇ .
  • the charging network element returns URI#2 to the terminal management function network element.
  • the second message may include a start (start) instruction, and the charging network element starts charging according to the start instruction.
  • start start
  • the charging network element starts charging according to the start instruction.
  • the second message includes a start instruction, and the charging network element can start charging according to the start instruction.
  • the second message does not include the start indication, the second message may indicate the start indication, and the charging network element starts charging according to the second message.
  • the second message may include instruction information for the first operation, operation parameters corresponding to the first operation, first instruction information, identification information of the target terminal, identification information of the application, address information of the application network element, and the first tunnel. At least one of the messages.
  • the terminal management function network element can send the information in the first message to the charging network element, and the charging network element charges for the inventory request initiated in S310 based on this information.
  • the terminal management function network element sends the first charging information to the charging network element, and accordingly, the charging network element receives the first charging information.
  • the terminal management function network element can send a converged charging update request (Nchf_ConvergedCharging_Update Request) message to the charging network element, and the request URI is ⁇ apiRoot ⁇ /nchf-convergedcharging/ ⁇ apiVersion ⁇ /chargingdata/ ⁇ ChargingDataRef1 ⁇ /update.
  • the converged charging update request message includes the first charging information.
  • the charging network element updates the previously created Individual Charging Data Resource according to the request URI, saves the first charging information, and generates a charging data record (CDR) based on the first charging information, and sends it to the accounting system.
  • CDR charging data record
  • the terminal management function network element can send an offline charging update request (Nchf_OfflineOnlyCharging_Update Request) message to the charging network element, and the request URI is ⁇ apiRoot ⁇ /nchf-offlineonlycharging/ ⁇ apiVersion ⁇ /offlinechargingdata/ ⁇ OfflineChargingDataRe f2 ⁇ /update.
  • the offline charging update request message includes the first charging information.
  • the charging network element updates the previously created Individual Offline Only Charging Data according to the request URI, saves the first charging information, and calculates the first charging information based on the first charging information. Generate CDR and send to accounting system.
  • the first charging information includes an interim indication or an update indication, and the interim indication or update indication is used to instruct the charging network element to update the charging information.
  • the first charging information includes an interval instruction or an update instruction, and the charging network element can update the CDR according to the interval instruction or update instruction.
  • the first charging information does not include an interim indication or an update indication, the first charging information is an interim indication or an update indication, and the charging network element updates the CDR according to the first charging information.
  • the first charging information includes execution information of the one or more terminals.
  • the execution information of one or more terminals is the information obtained after performing the first operation on one or more terminals.
  • the execution information of the one or more terminals includes at least one of an execution result of the first operation performed by the one or more terminals, identification information of one or more terminals, and the number of one or more terminals.
  • the execution information of one or more terminals includes the identification information of one or more terminals and/or the number of one or more terminals.
  • the execution information of one or more terminals includes execution of the first operation by the one or more terminals. result.
  • the execution result includes the read data.
  • the execution result includes an indication of success or failure of writing.
  • Any first operation other than querying the terminal identifier may also be called an execution command.
  • the results obtained by executing any first operation other than querying the terminal identification may also be called execution results.
  • the one or more terminals include a first terminal, and the first terminal is a random terminal among the target terminals to be inventoried, or in other words, the first terminal is the target terminal to be inventoried.
  • Any terminal in S330, "one or more terminals" refers to the first terminal.
  • the execution information of one or more terminals includes the execution information of the first terminal, where the execution information of the first terminal includes at least one of the following: the identity of the first terminal, the quantity 1, the execution of the first terminal by the first terminal. The execution result of an operation.
  • the one or more terminals include terminals within the coverage area of the first access network device, or in other words, the target terminal consists of terminals within the coverage area of the first access network device.
  • Terminal group, "one or more terminals" in S330 refers to the terminals of the terminal group.
  • the execution information of one or more terminals includes execution information of terminals in the coverage area of the first access network device in the target terminal, where the execution information of the terminals in the coverage area of the first access network device in the target terminal
  • the execution information of the terminal includes at least one of the following: the identification list of the terminal obtained by the first access network device, the number of terminals obtained by the first access network device, the terminal execution of the first step obtained by the first access network device. The execution result of the operation.
  • the first charging information is used to charge the process of performing the first operation on one or more terminals.
  • the charging network element may generate a bill of the process of the first terminal performing the first operation based on the first charging information.
  • the bill can also be understood as CDR.
  • the CDR generated by the charging network element includes one or more of the following: identification information of the application, identification information of the target terminal Identification information, instruction information of the first operation, operation parameters corresponding to the first operation, first tunnel information, address information of the application network element, and The identification of the first terminal.
  • the CDR includes at least one of the following: identification information of the application, identification information of the target terminal, instruction information of the first operation, operation parameters corresponding to the first operation, address information of the application network element, first tunnel information, and quantity 1.
  • the CDR generated by the charging network element includes the identification information of the application, the identification information of the target terminal, the first The instruction information of the operation, the operation parameters corresponding to the first operation, the address information of the application network element, the first tunnel information, the identification of the first terminal, and the execution result of the first terminal performing the first operation.
  • the charging network element may generate a CDR of a process in which the terminal in the target terminal within the coverage area of the first access network device performs the first operation based on the first charging information.
  • the CDR generated by the charging network element includes at least one of the following: identification information of the application, The identification information of the target terminal, the instruction information of the first operation, the operation parameters corresponding to the first operation, the address information of the application network element, the first tunnel information, and the acquired identification list of the terminal.
  • the CDR includes at least one of the following: identification information of the application, identification information of the target terminal, instruction information of the first operation, operation parameters corresponding to the first operation, address information of the application network element, first tunnel information, and the acquired terminal. quantity.
  • the CDR generated by the charging network element includes at least one of the following: Application The identification information, the identification information of the target terminal, the instruction information of the first operation, the operation parameters corresponding to the first operation, the address information of the application network element, the first tunnel information, the obtained identification of the terminal and the list of corresponding execution result combinations .
  • the charging network element may generate a CDR based on each piece of first charging information received, or generate a CDR based on multiple first charging information based on a network policy or the like.
  • the terminal management function network element can initiate a charging request to the charging network element based on the first message, and after the first operation of one or more terminals is completed, send the charging request to the charging network element. information, so that the charging network element can charge one or more terminals for the process of performing the first operation according to the charging request and the charging information.
  • the method 300 before S330, further includes: S341, the terminal management function network element obtains the first information, wherein the first information is used to indicate the first terminal's An operation execution is completed; or, the first information includes execution information of the first terminal.
  • the terminal management function network element After acquiring the first information, the terminal management function network element sends the first charging information to the charging network element, where the first charging information includes the execution information of the first terminal.
  • the terminal management function network element obtains the first information, including:
  • the terminal management function network element receives the first information from the application network element; or the terminal management function network element receives the first information from the first access network device; or the terminal management function network element determines the first information.
  • the first information may come from the first access network device, the application network element or the terminal management function network element, where the first access network device is used to perform the first operation on the first terminal.
  • the first information is used to indicate completion of the first operation of the first terminal, and the first information comes from the application network element.
  • the application network element when the application network element initiates an execution command to the first terminal, after receiving the execution result of the first terminal performing the first operation, the application network element determines that the first operation of the first terminal has been completed according to the execution result, thus towards the end
  • the terminal management function network element sends the first information.
  • the application network element sends the first information to the terminal management function network element, including: the application network element sends the first information to the first access network device through control, and the first information passes through the terminal management function network element, or the application network
  • the user sends the first information to the first access network device through the user.
  • the first information passes through the terminal management user plane functional network element.
  • the terminal management user plane functional network element sends the first information to the terminal management control plane functional network element.
  • the first information includes execution information of the first terminal, and the first information comes from the first access network device.
  • the first access network device when the first access network device initiates an execution command to the first terminal, after receiving the execution result of the first terminal performing the first operation, the first access network device determines the first terminal according to the execution result. After the first operation is executed, the first information is sent to the terminal management function network element.
  • the first access network device sends the first information to the terminal management function network element, including: the first access network device sends the first information to the application network element through control, and the first information passes through the terminal management function network element, or , the first access network device sends the first information through the user application-oriented server, the first information passes through the terminal management user plane functional network element, and the terminal management user plane functional network element sends the first information to the terminal management control plane functional network element .
  • the first information is used to indicate completion of the first operation of the first terminal, and the first information comes from the terminal management function network element.
  • the terminal management function network element when the terminal management function network element initiates an execution command to the first terminal, after receiving the execution result of the first terminal performing the first operation, the terminal management function network element determines the first operation of the first terminal based on the execution result. After the operation is completed, the first information is obtained.
  • the terminal management function network element may send the first charging information to the charging control network element after receiving the first information corresponding to at least two first terminals, At this time, the first charging information includes an identification list of the at least two first terminals or the number of the at least two first terminals.
  • one or more terminals in S330 refers to the at least two first terminals.
  • the method 300 further includes: S342, the terminal management function network element receives second information, the second information is used to indicate the first access in the target terminal.
  • the first operation execution of the terminal within the coverage area of the network device is completed; or, the second information includes execution information of the terminal in the target terminal within the coverage area of the first access network device.
  • the terminal management function network element after receiving the second information, the terminal management function network element sends the first charging information to the charging network element.
  • the first charging information includes the execution information of the terminal within the coverage area of the first access network device. .
  • the second information comes from the first access network device.
  • the first access network device may determine that the inventory of target terminals within its coverage is completed according to the inventory process, and thereby send the second information to the terminal management function network element.
  • the first access network device may send dedicated instruction information to the terminal management function network element to indicate the number of target terminals in the coverage area of the first access network device. The first operation of the terminal is completed.
  • the first access network device may send execution information of the terminals within its coverage area to the terminal management function network element.
  • the terminal management function network element may send the first information to the charging control network element after receiving the second information corresponding to at least two first access network devices.
  • Charging information at this time, the first charging information includes a list of target terminals within the coverage area of the at least two first access network devices or a list of target terminals within the coverage area of the at least two first access network devices. The list or the number of target terminals within the coverage area of the at least two first access network devices.
  • one or more terminals in S330 refers to terminals within the coverage area of the at least two first access network devices.
  • method 300 further includes: S351, the terminal management function network element determines that the first operation of the target terminal is completed.
  • the terminal management function network element determines one or more access and mobility management network elements according to the first message, and one or more access and mobility management network elements corresponding to each access and mobility management network element. access network equipment.
  • the terminal management function network element sends a first inventory request to one or more access and mobility management network elements, where the first inventory request is used to request to perform a first operation on the target terminal.
  • Each access and mobility management network element sends a second inventory request to one or more access network devices in its management area, where the second inventory request is used to request to perform the first operation on the target terminal.
  • Each access network device performs the first operation on the terminals within its coverage area according to the third inventory request.
  • each access network device After completing the first operation of determining the terminal within its coverage area, each access network device sends second information to the terminal management function network element through the access and mobility management network element.
  • the terminal management function network element determines that the first operation of the target terminal is completed based on the second information of one or more access network devices determined by it.
  • the access network device performs the first operation on the terminals within its coverage area, that is, the access network device triggers the inventory process based on the third inventory request, which specifically includes:
  • the access network equipment sends radio frequency information to all terminals in the coverage area to provide excitation signals to all terminals in the coverage area of the access network equipment, so that the terminals can send signals to the access network equipment;
  • the access network device sends a selection message to all terminals in the coverage area.
  • the selection message is used to select a terminal to be inventoried among all terminals.
  • the terminal to be inventoried is determined according to the third inventory request;
  • the access network device sends a query request message to the selected terminal among all terminals.
  • the query request message is used to obtain the identity of the selected terminal.
  • the selected terminal is the to-be-inventoryed terminal among all terminals. terminal.
  • the selected target terminal initiates a random access process, and one terminal device is randomly accessed successfully, which is the first terminal in this embodiment.
  • the specific random access process may be: the access network device includes the first random number in the first query message, and the selected terminal locally sets the second random number based on the first random number. If the second random number set by a terminal is 0, the terminal sends the third random number to the access network device. If the access network device can correctly receive the third random number, the access network device sends the third random number to the terminal device. When the terminal receives the third random number, the terminal device determines that the random access is successful. After the terminal confirms that the randomization is successful, it sends the identification information of the terminal to the RAN;
  • the access network device receives the identification from the first terminal.
  • method 300 also includes: S361, the terminal management function network element sends a third message to the charging network element, and accordingly, the charging network element receives the third message.
  • the third message is used to request to close (that is, end) the charging of the first operation on the target terminal. That is, the third message is used to end the accounting for the inventory request initiated in S310.
  • the third message may be a converged charging release request message.
  • (Nchf_ConvergedCharging_Release Request) message the request URI is ⁇ apiRoot ⁇ /nchf-convergedcharging/ ⁇ apiVersion ⁇ /chargingdata/ ⁇ ChargingDataRef1 ⁇ /release.
  • the charging network element deletes the previously created Individual Charging Data Resource based on the request URI. If the charging network element still has an unclosed CDR, the charging network element sends the CDR to the accounting system.
  • the third message may be an offline charging release request (Nchf_OfflineOnlyCharging_Release Request) message
  • the request URI is ⁇ apiRoot ⁇ /nchf-offlineonlycharging/ ⁇ apiVersion ⁇ /offlinechargingdata/ ⁇ OfflineChargingDataRef2 ⁇ / release.
  • the charging network element deletes the previously created Individual Offline Only Charging Data based on the request URI. If the charging network element still has an unclosed CDR, the CHF sends the CDR to the accounting system.
  • the third message may include a stop instruction, and the charging network element turns off charging according to the stop instruction.
  • the third message includes a stop instruction, and the charging network element can end charging according to the stop instruction.
  • the third message does not include the stop instruction, the third message is the stop instruction, and the charging network element ends charging according to the third message.
  • method 300 also includes: S352, the terminal management function network element determines that the timer has expired.
  • the terminal management function network element When receiving the first message, the terminal management function network element starts a timer for the target terminal to perform the first operation.
  • the timer is used to determine when to end charging for the first operation of the target terminal.
  • the terminal management function network element can stop accounting. This method helps improve accounting accuracy and reduce resource consumption.
  • the timer duration may be a default duration, for example, the timer duration may be 5 minutes. If the terminal management function network element does not receive other first messages within the default time period for receiving the first message, it ends charging for the first operation of the target terminal.
  • the method 300 also includes: the terminal management function network element sends a policy rule to the terminal management user plane function network element, the policy rule is used to detect the completion of the first operation of the target terminal, or is used to detect the completion of the target terminal's execution of the second operation.
  • the policy rule is used to detect the first information or the second information.
  • the terminal management function network element may send the detection rule of the first information or the second information to the terminal management user plane function network element, so that the terminal management user plane function network element can identify the first information or the second information according to the detection rule. information, further, sending the first information or the second information to the terminal management function network element.
  • method 300 also includes: S362, the terminal management function network element sends a third message to the charging network element, and accordingly, the charging network element receives the third message.
  • S362 may refer to S361 above, and will not be described again here.
  • FIG 4 is another schematic diagram of a charging method provided by an embodiment of the present application. As shown in Figure 4, the method 400 includes the following steps.
  • the application network element AF of the application sends the seventh message to the terminal management function network element, and accordingly, the terminal management function network element receives the seventh message.
  • the seventh message is used to request to perform the first operation on the target terminal.
  • the seventh message can be understood as a request message for requesting the terminal management function network element to inventory the target terminal, and can be called: an inventory request message.
  • inventory refers to performing the first operation on the target terminal.
  • the first operation includes at least one of the following: querying terminal identification, reading, writing, inactivating, locking, block writing, block erasing, access, encryption, decryption, etc.
  • the seventh message may include at least one of the following: indication information of the first operation, operation parameters corresponding to the first operation, first indication information, identification information of the target terminal, identification information of the application, and first tunnel information.
  • the operation parameters corresponding to the first operation, the first instruction information, the identification information of the target terminal, the identification information of the application, and the first tunnel information please refer to the description of S310 above, and will not be repeated here. Repeat.
  • S420 The terminal management function network element sends the eighth message to the charging network element, and accordingly, the charging network element receives the eighth message.
  • the charging network element can be a converged charging function network element or an offline charging function network element, which is not limited by this application.
  • the eighth message is used to request to start charging for the first operation on the target terminal.
  • the eighth message may be an Nchf_ConvergedCharging_Create Request message, and the request URI is ⁇ apiRoot ⁇ /nchf-convergedcharging/ ⁇ apiVersion ⁇ /chargingdata.
  • the charging network element creates the corresponding Individual Charging Data Resource based on the eighth message, and generates the corresponding URI#1.
  • URI#1 is ⁇ apiRoot ⁇ /nchf-convergedcharging/ ⁇ apiVersion ⁇ /chargingdata/ ⁇ ChargingDataRef1 ⁇ .
  • the charging network element returns URI#1 to the terminal management function network element.
  • the eighth message may also be an Nchf_OfflineOnlyCharging_CreateRequest message, and the request URI is ⁇ apiRoot ⁇ /nchf-offlineonlycharging/ ⁇ apiVersion ⁇ /offlinechargingdata.
  • the charging network element creates the corresponding Individual Offline Only Charging Data according to the eighth message, and generates the corresponding resource identifier URI#12.
  • URI#2 is ⁇ apiRoot ⁇ /nchf-offlineonlycharging/ ⁇ apiVersion ⁇ /offlinechargingdata/ ⁇ OfflineChargingDataRef2 ⁇ .
  • the charging network element returns URI#2 to the terminal management function network element.
  • the eighth message may include a start instruction, and the charging network element starts charging according to the start instruction.
  • the eighth message includes a start instruction, and the charging network element can start charging according to the start instruction.
  • the eighth message does not include the start indication, the eighth message may indicate the start indication, and the charging network element starts charging according to the eighth message.
  • the eighth message also includes a first identifier, and the first identifier is used to identify charging initiated by the terminal management function network element for performing the first operation on the target terminal.
  • the first identifier may also be called a charging ID, which is used to identify the eighth message.
  • the first identifier is assigned by the terminal management function network element. For example, for different first messages sent by the application network element, the terminal management function network element can assign different first identifiers and carry the corresponding third identifier in the eighth message. An identifier to identify this billing request.
  • the eighth message also includes the network element type that sends the message, and the network element type here is the terminal management function network element.
  • the eighth message may include at least one of indication information of the first operation, operation parameters corresponding to the first operation, first indication information, identification information of the target terminal, identification information of the application, and first tunnel information.
  • the terminal management function network element can send the information in the ninth message to the charging network element, and the charging network element charges for the inventory request initiated in S410 based on this information.
  • S430 The terminal management function network element sends the ninth message to the access and mobility management network element, and accordingly, the access and mobility management network element receives the ninth message.
  • the ninth message is used to request to perform the first operation on the target terminal.
  • the terminal management function network element determines one or more access points based on the first message.
  • One or more access network devices corresponding to the mobility management network element and each access and mobility management network element and sends a ninth message to one or more access and mobility management network elements to request access.
  • the access and mobility management network element performs the first operation on the target terminal within its management area.
  • the ninth message includes the first identifier.
  • the ninth message also includes at least one of the instruction information of the first operation, the operation parameters corresponding to the first operation, the second instruction information, the identification information of the target terminal, the identification information of the application, and the first tunnel information, and a description of these information Refer to S410.
  • the second indication information is used to indicate an area where the first operation is to be performed.
  • the area in which the first operation is to be performed indicated by the second indication information includes the location of the target terminal to be inventoried, and the second indication information includes 3GPP location information, such as TA list or cell list.
  • the terminal management function network element needs to map the area indicated by the first indication information into a TA list or cell list.
  • S440 The access and mobility management network element sends a fourth message to the session management network element, and accordingly, the session management network element receives the fourth message.
  • the access and mobility management network element determines that a user plane tunnel needs to be established based on the application identification information and the first tunnel information in the ninth message.
  • the access and mobility management network element Send a fourth message to the session management network element.
  • the fourth message is used to request the establishment of a first session, and the first session is used to transmit execution information of one or more terminals in the target terminal.
  • the first session may refer to a tunnel, that is, execution information of one or more terminals in the target terminal is transmitted through a tunnel.
  • the execution information of one or more terminals is the information obtained after performing the first operation on one or more terminals.
  • the fourth includes the first identifier.
  • the fourth message also includes at least one of the following: first tunnel information, identification information of the target terminal, and identification information of the application.
  • S450 The session management network element sends the fifth message to the charging network element, and accordingly, the charging network element receives the fifth message.
  • the session management network element can determine the user plane network element according to the identification information of the application, and jointly establish a connection between the user plane network element and the application server with the user plane network element and the application server. User plane tunnel. Further, the session management network element sends a fifth message to the charging network element.
  • the fifth message is used to request to start charging for the first operation on the target terminal.
  • the fifth message may be an Nchf_ConvergedCharging_Create Request message, and the request URI is ⁇ apiRoot ⁇ /nchf-convergedcharging/ ⁇ apiVersion ⁇ /chargingdata.
  • the charging network element creates the corresponding Individual Charging Data Resource according to the fifth message, and generates the corresponding resource identifier URI#3.
  • URI#3 is ⁇ apiRoot ⁇ /nchf-convergedcharging/ ⁇ apiVersion ⁇ /chargingdata/ ⁇ ChargingDataRef3 ⁇ .
  • the charging network element returns URI#3 to the session management network element.
  • the fifth message may also be an Nchf_OfflineOnlyCharging_CreateRequest message, and the request URI is ⁇ apiRoot ⁇ /nchf-offlineonlycharging/ ⁇ apiVersion ⁇ /offlinechargingdata.
  • the charging network element creates the corresponding Individual Offline Only Charging Data based on the fifth message, and generates the corresponding resource identifier URI#4.
  • URI#4 is ⁇ apiRoot ⁇ /nchf-offlineonlycharging/ ⁇ apiVersion ⁇ /offlinechargingdata/ ⁇ OfflineChargingDataRef4 ⁇ .
  • the charging network element returns URI#4 to the session management network element.
  • the fifth message includes the first identifier.
  • the fifth message also includes the network element type that sends the message, and the network element type here is the session management network element.
  • the fifth message may also include a start (start) instruction, and the charging network element starts charging according to the start instruction.
  • the fifth message includes a start instruction, and the charging network element can start charging according to the start instruction.
  • the fifth message does not include the start indication, the fifth message may indicate the start indication, and the charging network element starts charging according to the fifth message.
  • the terminal management function network element determines one or more access and mobility management network elements.
  • the one or more access and mobility management network elements correspond to one or more session management network elements.
  • the fifth message includes The first identification enables the charging network element to associate the eighth message with the fifth message initiated by one or more session management network elements.
  • the fifth message further includes at least one of the following: first tunnel information, identification information of the target terminal, and identification information of the application.
  • the charging network element associates the eighth message and the fifth message according to the first identifier.
  • the charging network element associates the session initiated by the terminal management function network element and the session initiated by the session management network element according to the first identifier, that is, the sessions including the same first identifier belong to the same inventory request. For subsequent charging requests that include the same first identifier, the charging network element may generate a CDR based on the information obtained from the terminal management function network element and the session management network element.
  • the charging network element associates the resources identified as URI#1 and URI#3 according to the first identifier, or associates the resources identified as URI#2 and URI#4 according to the first identifier.
  • S470 The session management network element sends the second charging information, and accordingly, the charging network element receives the second charging information.
  • the session management network element sends an Nchf_ConvergedCharging_Update Request message to the charging network element, and the request URI is ⁇ apiRoot ⁇ /nchf-convergedcharging/ ⁇ apiVersion ⁇ /chargingdata/ ⁇ ChargingDataRef3 ⁇ /update.
  • the converged charging creation request message includes second charging information.
  • the charging network element updates the Individual Charging Data Resource created before requesting the URI, saves the second charging information, generates a CDR based on the second charging information and the information carried in the fifth message, and sends it to the accounting system.
  • the terminal management function network element sends an Nchf_OfflineOnlyCharging_Update Request message to the charging network element, and the request URI is ⁇ apiRoot ⁇ /nchf-offlineonlycharging/ ⁇ apiVersion ⁇ /offlinechargingdata/ ⁇ OfflineChargingDataRef2 ⁇ /update.
  • the offline charging creation request message includes second charging information.
  • the charging network element updates the previously created Individual Offline Only Charging Data based on the request URI, saves the second charging information, and generates a CDR based on the information carried in the second charging information and the fifth message, and sends it to the accounting system.
  • the second charging information includes execution information of one or more terminals in the target terminal.
  • the execution information of the one or more terminals includes the execution information of the one or more terminals performing the first operation. At least one of execution results, identification information of one or more terminals, and the number of one or more terminals.
  • the second charging information is used to charge the process of performing the first operation on one or more terminals.
  • the charging network element may generate a CDR of a process in which the first terminal performs the first operation based on the first charging information.
  • the CDR generated by the charging network element includes one or more of the following: identification information of the application, identification information of the target terminal Identification information, instruction information of the first operation, operation parameters corresponding to the first operation, first tunnel information, address information of the application network element, and identification of the first terminal.
  • the CDR includes at least one of the following: identification information of the application, identification information of the target terminal, instruction information of the first operation, operation parameters corresponding to the first operation, address information of the application network element, first tunnel information, and quantity 1.
  • the CDR generated by the charging network element includes the identification information of the application, the identification information of the target terminal, the first The instruction information of the operation, the operation parameters corresponding to the first operation, the address information of the application network element, the first tunnel information, the identification of the first terminal, and the execution result of the first terminal performing the first operation.
  • the charging network element may generate a CDR of a process in which the terminal in the target terminal within the coverage area of the first access network device performs the first operation based on the first charging information.
  • the CDR generated by the charging network element includes at least one of the following: identification information of the application, The identification information of the target terminal, the instruction information of the first operation, the operation parameters corresponding to the first operation, the address information of the application network element, the first tunnel information, and the acquired identification list of the terminal.
  • the CDR includes at least one of the following: identification information of the application, identification information of the target terminal, instruction information of the first operation, operation parameters corresponding to the first operation, address information of the application network element, first tunnel information, and the acquired terminal. quantity.
  • the CDR generated by the charging network element includes at least one of the following: Application The identification information, the identification information of the target terminal, the instruction information of the first operation, the operation parameters corresponding to the first operation, the address information of the application network element, the first tunnel information, the obtained identification of the terminal and the list of corresponding execution result combinations .
  • the charging network element may generate a CDR after receiving each second charging information, or may generate a CDR based on multiple second charging information after receiving multiple second charging information according to network policies.
  • the session management network element can initiate a charging request to the charging network element based on the fourth message, and after the first operation of one or more terminals is completed, send charging information to the charging network element , so that the charging network element can charge one or more terminals for the process of performing the first operation according to the charging request and the charging information.
  • the method 400 further includes: S481, the session management network element receives the first information, where the first information is used to indicate the first terminal of the first terminal. The operation execution is completed; or, the first information includes execution information of the first terminal.
  • the session management network element after receiving the first information, the session management network element sends the first charging information to the charging network element.
  • the charging information includes execution information of the first terminal.
  • the session management network element receives the first information, including:
  • the session management network element receives the first information from the application network element; or the session management network element receives the first information from the first access network device.
  • the first information may come from the first access network device or the application network element, where the first access network device is used to perform the first operation on the first terminal.
  • the first information is used to indicate completion of the first operation of the first terminal, and the first information comes from the application network element.
  • the application network element initiates an execution command to the first terminal, after receiving the execution result of the first terminal performing the first operation, the application network element determines that the first operation of the first terminal has been completed according to the execution result, Therefore, the application server sends the first information to the first access network device through the user, the first information passes through the user plane network element, and the user plane network element sends the first information to the session management network element.
  • the first information includes execution information of the first terminal, and the first information comes from the first access network device.
  • the first access network device when the first access network device initiates an execution command to the first terminal, after receiving the execution result of the first terminal performing the first operation, the first access network device determines the first terminal according to the execution result. After the first operation is executed, the first information is sent to the user-oriented application server. The first information passes through the user plane network element, and the user plane network element sends the first information to the session management network element.
  • the session management network element may send the first charging information to the charging control network element after receiving the first information corresponding to at least two first terminals.
  • the first charging information includes an identification list of the at least two first terminals or a number of the at least two first terminals.
  • the method 400 further includes: S482, the session management network element receives second information, the second information is used to indicate the first access network in the target terminal.
  • the first operation execution of the terminal within the coverage area of the device is completed; or, the second information includes execution information of the terminal in the target terminal within the coverage area of the first access network device.
  • the session management network element after receiving the second information, sends the first charging information to the charging network element, where the first charging information includes the execution information of the terminal within the coverage area of the first access network device.
  • the second information comes from the first access network device.
  • the first access network device may determine that the inventory of target terminals within its coverage is completed according to the inventory process, and may send the second information to the session management network element.
  • the first access network device determines that the inventory of target terminals within its coverage is completed, it can send dedicated instruction information through the access and mobility management network element to indicate the coverage of the first access network device in the target terminal.
  • the first operation of the terminal in the area is completed.
  • the first access network device determines that the inventory of target terminals within its coverage area is completed, it can send the execution information of the terminals within its coverage area through the user application-oriented server.
  • the execution information passes through the user plane network element, The user plane network element reports the execution information to the session management network element.
  • the session management network element may send the first accounting information to the charging control network element after receiving the second information corresponding to at least two first access network devices.
  • Charging information at this time, the first charging information includes a list of target terminals within the coverage area of the at least two first access network devices or a list of target terminals within the coverage area of the at least two first access network devices. Or the number of target terminals within the coverage area of the at least two first access network devices.
  • one or more terminals in S470 refers to terminals within the coverage area of the at least two first access network devices.
  • method 400 also includes: S490, the access and mobility management network element sends an eleventh message to the session management network element, and accordingly, the session function network element receives the eleventh message.
  • the access and mobility management network element determines that the first operation of the target terminal is completed based on the second information of an access network device in its management area, and the access and mobility management network element sends the third operation to the session management network element. Eleven news.
  • the eleventh message is used to request the release of the first session.
  • the method 400 also includes: S4100, the session management network element sends a sixth message to the charging network element, and accordingly, the charging network element receives the sixth message.
  • the session management network element After the session management network element receives the eleventh message, it releases the first session and sends the sixth message to the charging network element.
  • the sixth message is used to request to close the charging of the first operation on the target terminal.
  • the sixth message may be an Nchf_ConvergedCharging_Release Request message, and the request URI is ⁇ apiRoot ⁇ /nchf-convergedcharging/ ⁇ apiVersion ⁇ /chargingdata/ ⁇ ChargingDataRef3 ⁇ /release.
  • the charging network element deletes the previously created Individual Charging Data Resource based on the request URI.
  • the message may also include unreported second charging information.
  • the sixth message may be an Nchf_OfflineOnlyCharging_Release Request message, and the request URI is ⁇ apiRoot ⁇ /nchf-offlineonlycharging/ ⁇ apiVersion ⁇ /offlinechargingdata/ ⁇ OfflineChargingDataRef4 ⁇ /release.
  • the charging network element deletes the previously created Individual Offline Only Charging Data based on the request URI.
  • the message may also include unreported second charging information.
  • the sixth message includes a stop instruction, and the charging network element turns off charging according to the stop instruction.
  • method 400 further includes: S4111, the terminal management function network element determines that the first operation of the target terminal is completed.
  • method 400 also includes: S4121, the terminal management function network element sends a tenth request message to the charging network element, where the tenth request message is used to request to close the charging of the first operation of the target terminal.
  • the terminal management function network element sends an Nchf_ConvergedCharging_Release Request message to the charging network element, and the request URI is ⁇ apiRoot ⁇ /nchf-convergedcharging/ ⁇ apiVersion ⁇ /chargingdata/ ⁇ ChargingDataRef11 ⁇ /release.
  • the charging network element deletes the previously created Individual Charging Data Resource based on the request URI. If the charging network element still has an unclosed CDR, the charging network element sends the CDR to the accounting system.
  • the terminal management function network element sends an Nchf_OfflineOnlyCharging_ReleaseRequest message to the charging network element, and the request URI is ⁇ apiRoot ⁇ /nchf-offlineonlycharging/ ⁇ apiVersion ⁇ / offlinechargingdata/ ⁇ OfflineChargingDataRef2 ⁇ /release.
  • the charging network element deletes the previously created Individual Offline Only Charging Data based on the request URI. If the charging network element still has an unclosed CDR, the charging network element sends the CDR to the accounting system.
  • method 400 also includes: S4112, the terminal management function network element determines that the timer has expired.
  • the terminal management function network element When receiving the seventh message, the terminal management function network element starts a timer for the target terminal to perform the first operation.
  • the method 400 also includes: S4122, the terminal management function network element sends a tenth request message to the charging network element, where the tenth request message is used to request to close the charging of the first operation of the target terminal. At this time, the charging of the first operation on the target terminal ends.
  • method 400 further includes: the session management network element sending policy rules to the user plane network element, the policy rules being used to detect completion of the first operation of the target terminal, or used to detect execution of the first operation of the target terminal.
  • the policy rule includes identification information of the target terminal.
  • the policy rule is used to detect the first information or the second information.
  • the session management network element can send the detection rule of the first information or the second information to the user plane network element, so that the user plane network element can identify the first information or the second information according to the detection rule, and further, the first information The information or second information is sent to the session management network element.
  • the charging network element is CHF
  • the access network equipment is RAN
  • the access and mobility management network element is AMF
  • the terminal management user plane function network element is terminal management function network element-UP
  • session management The network element is SMF
  • the application network element is AF
  • the application server is AS
  • the user plane network element is UPF.
  • FIG. 5 is another schematic flow chart of a charging method provided by this application.
  • the method 500 shown in Figure 5 can be regarded as a specific implementation of the above method 300.
  • the method 500 shown in Figure 5 introduces the charging in the scenario where the terminal management function network element sends the execution command to the RAN, the RAN saves and initiates the execution command, and the RAN reports the inventory results through the control plane.
  • S501 The applied AF sends request message #1 (an example of the first message) to the terminal management function network element.
  • the request message #1 is used to request a first operation on the target terminal.
  • the request message #1 includes identification information of the target terminal, instruction information of the first operation, and application information.
  • the application information includes identification information of the application or data network access identification information of the application.
  • the above request message #1 when the above request message #1 does not carry the indication information of the first operation, it means that the first operation is query, that is, querying the terminal identity; or, when the above request message #1 carries the instruction information of the first operation, and the instruction information of the first operation includes query, it means that the first operation is a query.
  • any first operation other than querying the terminal identity may be called an execution command.
  • the request message #1 also includes first indication information, operation parameters, notification address #1 and association identification #1.
  • the identification information of the target terminal the instruction information of the first operation, the first instruction information, the operation parameters, the identification information of the application, and the notification address #1 are as described above and will not be described again here.
  • association identifier #1 is used to associate message #1 and response message #1 to the message #1.
  • the terminal management function network element when the terminal management function network element receives the request message #1, the terminal management function network element can start the timer.
  • the terminal management function network element sends the accounting request message #1 (an example of the second message) to the CHF.
  • the accounting request message #1 includes a Start indication.
  • the charging request message #1 may also include identification information of the target terminal, instruction information of the first operation, operation parameters, first instruction information, identification information of the application, and notification address #1.
  • CHF starts accounting according to the accounting request message #1, and sends a response message to the terminal management function network element.
  • the response message may be an Nchf_ConvergedCharging_CreateResponse.
  • the charging request message #1 is an Nchf_OfflineOnlyCharging_CreateRequest message
  • the response message can be an Nchf_OfflineOnlyCharging_Create Response.
  • the terminal management function network element sends inventory request #1 (an example of the first inventory request) to the AMF.
  • the terminal management function network element can determine the AMF according to the information in the request message #1 (for example, the identification information of the target terminal, the first indication information, the identification information of the application, etc.), and RAN corresponding to AMF. For example, the terminal management function network element determines the corresponding RAN or AMF based on the first indication information (for example, cell identification), or determines the RAN or AMF corresponding to the identification information based on the identification information of the target terminal.
  • the first indication information for example, cell identification
  • the RAN is a RAN with a terminal inventory function.
  • the terminal management function network element may send inventory request #1 to the AMF.
  • the inventory request #1 is used to request a first operation on the target terminal.
  • the inventory request #1 includes the identification information of the target terminal and the instruction information of the first operation.
  • the identification information of the target terminal and the instruction information of the first operation are as described above and will not be described again here.
  • the inventory request #1 also includes second indication information.
  • the area used for indication by the second indication information includes an area managed by the AMF, and the second indication information includes 3GPP location information (such as TA list, Cell list, etc.).
  • 3GPP location information such as TA list, Cell list, etc.
  • the terminal management function network element shall send inventory request #1 to each AMF respectively.
  • the second indication information included in different inventory requests #1 is different. Indicates the areas managed by different AMFs.
  • the inventory request #1 also includes operation parameters, where the operation parameters are as described above and will not be described again here.
  • inventory request #1 also includes notification address #2 and association identification #2.
  • notification address #2 is used to represent the address where the terminal management function network element receives terminal information and command execution results.
  • the address of the terminal management function network element is used to represent the address where the terminal management function network element receives terminal information and command execution results.
  • association identifier #2 is used to associate the inventory request #1 and the response message #2 for the inventory request #1.
  • AMF sends inventory request #2 (an example of the second inventory request) to the RAN.
  • the inventory request #2 is used to request a first operation on the target terminal.
  • the inventory request #2 includes the identification information of the target terminal and the instruction information of the first operation.
  • the identification information of the target terminal and the instruction information of the first operation are as described above and will not be described again here.
  • inventory request #2 also includes third indication information, operation parameters, notification address #2 and association identification #2.
  • the area used for indication by the third indication information includes an area managed by the RAN, and the third indication information includes 3GPP location information (such as TA list, Cell list, etc.).
  • 3GPP location information such as TA list, Cell list, etc.
  • the terminal management function network element shall send inventory request #2 to each RAN respectively.
  • the third indication information included in different inventory requests #2 is different. Indicates areas managed by different RANs.
  • the AMF when the area managed by the AMF covers multiple RANs, the AMF sends inventory requests #2 to the multiple RANs, sends inventory requests #2 to different RANs, and sends inventory requests #2 to a certain RAN.
  • the process of inventory request #2 is similar, except that the RAN inventory area needs to be determined for different RANs.
  • steps S504 and S505 may be: the terminal management function network element determines to send inventory request #2 to each RAN, and the terminal management function network element encapsulates the inventory request #2 in message #A, Message #A also includes identification information of the RAN.
  • AMF receives message #A
  • AMF decapsulates message #A and obtains inventory request #2.
  • It encapsulates inventory request #2 in message #B and sends it to the RAN corresponding to the identification information of the RAN. This can be understood as AMF transparent transmission.
  • Got inventory request #2 In this case, inventory request #1 includes inventory request #2.
  • S506 RAN takes inventory of the target terminal.
  • the RAN sends radio frequency signals to all terminals in the coverage area to provide excitation signals to the terminals in the RAN's coverage area, thereby causing the terminal equipment to send signals to the RAN.
  • the RAN sends a selection message to the terminals within the coverage area of the RAN.
  • the RAN then sends a query request to all selected terminals. Any target terminal covered by the RAN, recorded as terminal #1 (an example of the first terminal), will send identification information to the RAN.
  • this step is a random access process for terminal #1, and the random access process will be performed for any terminal among the target terminals.
  • the RAN sends the execution commands to the terminal #1.
  • terminal #1 After terminal #1 completes executing the command, it sends the execution result to the RAN. For example, if the execution command is read, the execution result includes the read data; if the execution command is write, the execution result is an indication of success or failure and the execution result.
  • S507 The RAN determines that the inventory of the terminal #1 is completed, the RAN sends a query request for the next tag to all selected tags, and continues to step 506.
  • S508 The RAN determines that the inventory of all selected terminals is completed.
  • the RAN determines that the inventory of all terminals selected within its coverage is complete, as follows: After executing step S506, if the RAN does not receive a random access request message initiated by any terminal within the configured time, the RAN determines that the target terminal is within its coverage. The inventory is completed (it can also be said that the query is completed or the target operation is completed).
  • the RAN After the RAN determines that the inventory of all terminals selected within its coverage is completed, it can send response message #2 to the terminal management function network element according to notification address #2.
  • the response message #2 is a response to the inventory request #1 in S504, and the response message #2 includes the relevant information. Coupon ID #2.
  • the RAN After the RAN receives the identification and execution results of the target terminal, it can report them in two ways:
  • Method 1 After RAN determines that terminal #1 has completed the steps of S506, it sends response message #2 to the terminal management function network element.
  • S509 can be executed after S506.
  • the response message #2 includes the execution information of the terminal #1 (an example of the first information), that is, the identification and/or quantity of the terminal #1. It should be understood that the value of the quantity is 1 at this time.
  • the execution information of terminal #1 also includes the execution result.
  • response message #2 also includes the identification of the RAN.
  • response message #2 also includes information #1, which is used to indicate that the inventory of terminal #1 is completed.
  • Method 2 After all received target terminals have completed the steps of S506, the RAN sends response message #2 to the terminal management function network element.
  • the identification and execution results of the target terminals are uniformly reported for all received target terminals.
  • S509 can be executed after S508.
  • the response message #2 includes the execution information (an example of the second information) of the terminals in the RAN coverage area of the target terminal, that is, the identification list and/or the number of terminals obtained by the RAN.
  • the terminal acquired by the RAN is the terminal that sends the identifier to the RAN, that is, the terminal within the RAN coverage area of the target terminal.
  • the execution information of the terminals in the RAN coverage area of the target terminal also includes a list of execution results corresponding to each terminal.
  • response message #2 also includes the identification of the RAN.
  • response message #2 also includes information #2, which is used to indicate that the inventory of target terminals in the RAN coverage area is completed, or that the RAN inventory is completed.
  • the terminal management function network element sends response message #1 to the AF.
  • the terminal management function network element After receiving the response message #2, the terminal management function network element will send the response message #1 to the AF.
  • the response message #1 is a response to the request message #1 in S501, and the response message #1 includes the association identifier #1.
  • response message #2 also includes the identification of the RAN.
  • the response message #1 also includes the information in the response message #2. Specifically, the information included in the response message #1 is different for the first and second methods in S509.
  • the response message #1 includes the execution information of the terminal #1, that is, at least one of the identification, the quantity 1, and the execution result of the terminal #1.
  • the response message #1 includes the execution information of the terminals in the RAN coverage area of the target terminal, that is, at least one of the identification list of the terminals obtained by the RAN, the number of terminals obtained by the RAN, and the list of execution results corresponding to each terminal. .
  • the terminal management function network element sends charging information #1 (an example of the first charging information) to the CHF.
  • the terminal management function network element After receiving the response message #2, that is, after receiving the execution information of the terminal #1 or the execution information of the terminals in the RAN coverage area of the target terminal, the terminal management function network element can send the charging information #1 to the CHF.
  • the charging information #1 includes an interim instruction or an update instruction, and the interim instruction or update instruction is used to instruct the CHF to update the charging information and to generate a bill for the charging information #1.
  • charging information #1 may also include information about terminal #1 in the target terminal, that is, at least one of the identification, quantity 1, and execution result of terminal #1, or charging information #1 It includes information about the terminals within the RAN coverage area of the target terminal, that is, at least one of the identification list of the terminals obtained by the RAN, the number of terminals obtained by the RAN, and a list of execution results corresponding to each terminal.
  • the charging information #1 also includes the identification of the RAN.
  • the terminal management function network element may first send response message #1 to AF, or may first send accounting information #1 to CHF, which is not limited in this application. That is, there is no necessary sequence between S510 and S511.
  • the CHF can generate a CDR of the process of RAN inventory of the terminal #1 based on the charging information #1.
  • the CHF may generate a CDR of the process of RAN inventory of the terminals in its coverage area based on the charging information #1.
  • the CHF may generate a CDR based on each received charging information #1, or generate a CDR based on multiple charging information #1 according to a network policy or the like.
  • the terminal management function network element determines that the target terminal inventory is completed or determines that the timer has expired.
  • the specific way in which the terminal management function network element determines that the target terminal inventory is completed is that the terminal management function network element determines that all the RANs determined in S504 have sent information #2.
  • the terminal management function network element executes S514.
  • S514 The terminal management function network element sends the accounting request message #2 (an example of the third message) to the CHF.
  • the accounting request message #2 includes a stop indication, and the stop indication is used to instruct the CHF to close the accounting for the accounting request message #1.
  • S515 CHF returns a response message to the terminal management function network element.
  • CHF can turn off this billing according to the stop instruction. If CHF still has an unclosed CDR, CHF sends the CDR to the accounting system.
  • S513 to S515 are optional steps.
  • the terminal management function network element may not execute S513 and S514. In this case, the CHF will not execute S515.
  • Method 500 shown in Figure 5 introduces charging in an inventory scenario where the RAN reports the inventory results through the control plane, and in this inventory scenario, the execution command is initiated by the RAN. Therefore, the charging method provided by the embodiment of the present application can be applied to various inventory scenarios and has better compatibility and flexibility.
  • FIG. 6 is another schematic flow chart of a charging method provided by this application.
  • the method 600 shown in Figure 6 can be regarded as another specific implementation of the above method 300.
  • the method 600 shown in Figure 6 introduces the charging in the scenario where the terminal management function network element saves the execution command, initiates the execution command, and the RAN reports the inventory result through the control plane.
  • S601 The applied AF sends request message #1 to the terminal management function network element.
  • the terminal management function network element sends the accounting request message #1 to the CHF.
  • S601 to S603 refer to S501 to S503, which will not be described again here.
  • the terminal management function network element sends inventory request #3 (another example of the first inventory request) to the AMF.
  • S605 The AMF sends inventory request #4 (another example of the second inventory request) to the RAN.
  • inventory request #4 does not include execution commands and operation parameters.
  • S606 RAN performs inventory of target terminals.
  • the inventory process includes the RAN sending radio frequency signals, selection messages, and query requests.
  • Terminal #1 completes the random access process and sends identification information to the RAN.
  • the RAN sends response message #2 to the terminal management function network element.
  • the response message #2 in S607 is a response to the inventory request #4 in S605, and the response message #2 includes the association identification #2.
  • Response message #2 includes execution information of terminal #1, that is, the identification and/or quantity of terminal #1. It should be understood that the value of quantity is 1 at this time.
  • response message #2 also includes the identification of the RAN.
  • S608 If S601 includes an execution command, the terminal management function network element sends the execution command to the RAN.
  • Terminal #1 sends the execution result to the RAN.
  • the terminal management function network element sends an instruction to complete the inventory of terminal #1 to the RAN.
  • the terminal management function network element determines that the execution of all execution commands is completed based on the execution results. That is, the terminal management function network element determines that the inventory of terminal #1 is completed, and then sends an instruction of completion of the inventory of terminal #1 to the RAN (an example of the first information).
  • the indication of completion of inventory of terminal #1 is an example of the first information
  • S612 can be understood as a process in which the terminal management function network element determines the first information and sends the first information to the RAN.
  • the terminal management function network element sends charging information #2 (another example of the first charging information) to the CHF.
  • accounting information #2 includes interim ) instruction or update (update) instruction, the interim instruction or update instruction is used to instruct the CHF to update the charging information and generate a bill for the charging information #2.
  • the charging information #2 also includes the execution information of the terminal #1 in S607, that is, the identification and/or quantity 1 of the terminal #1.
  • the execution information of terminal #1 received by the terminal management function network element also includes the execution result. Therefore, the accounting information #2 also includes the execution information of terminal #1 in S611, that is, Results of the.
  • the charging information #1 also includes the identification of the RAN.
  • S613 may not be executed, that is, the terminal management function network element saves the received execution information of terminal #1.
  • the CHF may generate a bill for the process of RAN inventory of terminal #1 based on charging information #1.
  • the RAN determines that the inventory of terminal #1 is completed, the RAN sends a query request for the next tag to all selected tags, and continues to step S606.
  • the RAN determines that the inventory for the terminal #1 is completed based on the instruction from the terminal management function network element in S612.
  • the RAN, target terminal, terminal management function network element, and CHF can continue to execute S607-S614.
  • RAN determines that the inventory of all selected tags is completed, and sends information #2 (an example of the second information) to the terminal management function network element.
  • Information #2 is used to indicate that the inventory of target terminals in the RAN coverage area is completed, or in other words, RAN The inventory is over.
  • information #2 is an example of the second information
  • S616 can be understood as a process in which the terminal management function network element receives the second information.
  • the method 600 also includes S617-S618.
  • the terminal management function network element sends charging information #3 (another example of the first charging information) to the CHF.
  • the terminal management function network element After receiving information #2, the terminal management function network element can send accounting information #1 to the CHF.
  • the charging information #3 includes an interim instruction or an update instruction, and the interim instruction or update instruction is used to instruct the CHF to generate a bill for the charging information #3.
  • Charging information #3 may also include execution information of multiple terminals #1 saved by the terminal management function network element. It should be understood that the execution information of multiple terminal #1 is summarized into the execution information of the terminals within the RAN coverage area of the target terminal, that is, the identification list of the terminals obtained by the RAN, the number of terminals obtained by the RAN, and the execution results corresponding to each terminal. list of at least one.
  • the charging information #3 also includes the identification of the RAN.
  • the terminal management function network element may not send the accounting information #2 after receiving the execution information of the terminal #1, but save the execution information of the terminal #1, and send the accounting information after receiving the information #2.
  • Charging information #3 includes execution information that stores multiple terminals #1, thereby requesting CHF to charge for the inventory process of target terminals within the RAN coverage area.
  • the message in the charging information #3 includes the execution information of the terminals in the RAN coverage area of the target terminal, and the CHF can generate a bill for the process of RAN inventorying the terminals in its coverage area based on the charging information #3.
  • the response message #1 in S619 is a response to the request message #1 in S601.
  • the response message #1 #1 includes association identifier #1.
  • Response message #1 includes at least one of a list of terminal identifiers obtained by the RAN, the number of terminals obtained by the RAN, an identification of the RAN, and a list of execution results corresponding to each terminal.
  • the terminal management function network element may also execute S619 after S613, that is, the terminal management function network element reports the execution information of terminal #1 to the AF after the inventory of terminal #1 is completed.
  • the response message #1 may include at least one of the identifier of the terminal #1, the quantity 1, the identifier of the RAN, and the execution result.
  • the terminal management function network element can execute S619.
  • the terminal management function network element may first send response message #1 to AF, or may first send accounting information #1 to CHF, which is not limited in this application. That is, there is no necessary sequence between S617 and S619.
  • the terminal management function network element can execute S617 first or S619 first.
  • S620 The terminal management function network element determines that the inventory of the target terminal is completed or determines that the timer has expired.
  • S621 The terminal management function network element sends the accounting request message #2 to the CHF.
  • the method 600 shown in Figure 6 introduces the charging in the inventory scenario where the RAN reports the inventory results through the control plane, and in this inventory scenario, the initiation of the execution command is decided by the terminal management function. Therefore, the charging method provided by the embodiment of the present application can be applied to various inventory scenarios and has better compatibility and flexibility.
  • FIG 7 is another schematic flow chart of a charging method provided by this application.
  • the method 700 shown in Figure 7 can be regarded as another specific implementation of the above method 300.
  • the method 700 shown in Figure 7 introduces the charging in the scenario where the AF determines the execution command, initiates the execution command, and the RAN reports the inventory results through the control plane.
  • S701 The applied AF sends request message #2 (another example of the first message) to the terminal management function network element.
  • request message #2 does not include the execution command that may be included in request message #1.
  • the terminal management function network element sends the accounting request message #3 (an example of the second message) to the CHF.
  • the difference is that the accounting request message #3 does not include the execution command that may be included in the accounting request message #1.
  • the CHF starts accounting according to the accounting request message #3, and sends a response message to the terminal management function network element.
  • the response message may be a charging data response message.
  • S704 The terminal management function network element sends inventory request #5 (another example of the first inventory request) to the AMF.
  • AMF sends inventory request #4 to RAN.
  • the RAN sends response message #2 to the terminal management function network element.
  • S705 to S707 refer to the description of S605 to S607.
  • S708 The terminal management function network element sends response message #1 to the AF.
  • the response message #1 in S708 is a response to the request message #2 in S701, and the response message #1 includes the association identifier #1.
  • Response message #1 includes execution information of terminal #1, that is, the identification and/or quantity 1 of terminal #1.
  • response message #1 also includes the identification of the RAN.
  • the terminal management function network element sends an execution command to the RAN.
  • Terminal #1 sends the execution result to the RAN.
  • S711 to S713, refer to S609 to S611.
  • the terminal management function network element reports the execution result of terminal #1 to the AF.
  • S715 AF sends an instruction to complete the inventory of terminal #1 to the terminal management function network element (another example of the first information).
  • the AF determines that the execution of all execution commands is completed based on the execution result of the terminal #1, that is, the AF determines that the inventory of the terminal #1 is completed, and then sends an instruction of the completion of the inventory of the terminal #1 to the terminal management function network element.
  • the indication of completion of inventory of terminal #1 is an example of the first information.
  • S715 can be understood as a process in which the AF determines the first information and sends the first information to the terminal management function network element.
  • the terminal management function network element sends an instruction to complete the inventory of terminal #1 to the RAN.
  • S717 The terminal management function network element sends accounting information #2 to the CHF.
  • the terminal management function network element may send charging information #1 to the CHF.
  • accounting information #2 also includes the execution command received in S709.
  • S717 may not be executed, that is, the terminal management function network element saves the received execution information of terminal #1.
  • the RAN determines that the inventory of the terminal #1 is completed, the RAN sends a query request for the next tag to all selected tags, and continues to step S706.
  • the RAN, target terminal, terminal management function network element, AF, and CHF can continue to execute S706-S719.
  • the RAN determines that the inventory of all selected tags is completed, and sends information #2 (an example of the second information) to the terminal management function network element.
  • the information #2 is used to indicate that the inventory of target terminals in the RAN coverage area is completed.
  • information #2 is an example of the second information
  • S720 can be understood as a process in which the terminal management function network element receives the second information.
  • S717 to S720 refer to S613 to S616.
  • the terminal management function network element sends information #2 to the AF.
  • the terminal management function network element may send an indication of the end of RAN inventory to the AF.
  • the method 700 also includes S722-S723.
  • S722 The terminal management function network element sends accounting information #3 to the CHF.
  • the charging information #3 also includes multiple execution commands received when S709 is repeatedly executed.
  • the terminal management function network element can first send accounting information #3 to CHF, or Information #2 may be sent to AF first, which is not limited by this application, that is, there is no necessary sequence between S721 and S722.
  • S724 The terminal management function network element sends response message #1 to the AF.
  • the terminal management function network element determines that the inventory of the target terminal is completed or determines that the timer has expired.
  • S726 The terminal management function network element sends accounting request message #2 to the CHF.
  • S722 to S727 refer to S617 to S622, which will not be described again here.
  • the method 700 shown in Figure 7 introduces the charging in the inventory scenario where the RAN reports the inventory results through the control plane, and in this inventory scenario, the execution of the command is initiated by the AF. Therefore, the charging method provided by the embodiment of the present application can be applied to various inventory scenarios and has better compatibility and flexibility.
  • terminal management function network element in Figure 5, Figure 6, and Figure 7 can be co-located with the NEF.
  • the above-mentioned actions performed by the terminal management function network element can be understood as actions performed by the NEF.
  • the terminal management function network element in Figures 5, 6, and 7 can be a newly added independent functional network element, which can be used to forward inventory requests and responses between AF and AMF.
  • the terminal management function network element in Figure 5, Figure 6, and Figure 7 can be a newly added independent functional network element, which can be used to forward inventory requests and responses between NEF and AMF, that is to say The inventory requests and responses between the terminal management function network element and the AF shown in Figure 5, Figure 6, and Figure 7 need to be forwarded through NEF.
  • terminal management function network element in Figure 5, Figure 6, and Figure 7 can be co-located with the AMF.
  • the interaction between the above terminal management function network element and the AMF can be understood as internal interaction.
  • the RAN can also report the inventory results through the tunnel.
  • the charging process in the scenario of reporting the inventory results through the tunnel will be described in detail below with reference to Figures 9 to 10.
  • Figure 9 is another schematic flow chart of a charging method provided by this application.
  • the method 900 shown in Figure 9 can be regarded as another specific implementation of the above method 300. Specifically, the method 900 shown in Figure 9 introduces the method in which the terminal management function network element-CP sends the execution command to the RAN, the RAN saves and initiates the execution command, and the RAN reports the inventory results through the terminal management function network element-UP. Billing in scenarios.
  • S901 The applied AF sends request message #3 (another example of the first message) to the terminal management function network element-CP.
  • the request message #3 is similar to the request message #1 shown in the above-mentioned S501.
  • the request message #3 is used to request the first operation on the target terminal.
  • the difference between the request message #3 and the request message #1 is that :
  • Request message #3 does not include notification address #1 and association identifier #1, but includes application server (AS) tunnel information. (An example of first tunnel information).
  • AS application server
  • the AS tunnel information is used to indicate the user plane port or user plane address of the application server for receiving the inventory result.
  • the AS tunnel information is the address of the AS.
  • the terminal management function network element-CP sends the accounting request message #4 (another example of the second message) to the CHF.
  • the charging request message #4 is similar to the charging request message #1 shown in the above-mentioned S502, except that the charging request message #4 does not include the notification address #1, but includes the AS tunnel information.
  • the CHF starts accounting according to the accounting request message #4, and sends a response message to the terminal management function network element-CP.
  • the response message may be a charging data response message.
  • the terminal management function network element-CP sends request message #4 to the terminal management function network element-UP.
  • the terminal management function network element-CP needs to determine the terminal management function network element-UP based on the identification information of the application and other information, where the terminal management function network element-CP saves the identification information of the application and the terminal management function network element -UP correspondence.
  • the terminal management function network element-CP After the terminal management function network element-CP determines the terminal management function network element-UP, it can send a request message #4 to the terminal management function network element-UP.
  • the request message #4 can also be called a tunnel information request message, which is used to Get tunnel information.
  • the accounting request message #4 includes the identification information of the target terminal and the AS tunnel information.
  • S905 The terminal management function network element-UP sends response message #4 to the terminal management function network element-CP.
  • response message #4 is used to respond to request message #4 in S904, and response message #4 may also be called a tunnel information response message.
  • Response message #4 includes CN tunnel information #1, which is the tunnel endpoint through which the terminal management function network element-UP receives uplink data.
  • S906 The terminal management function network element-CP sends inventory request #5 (another example of the first inventory request) to the AMF.
  • the terminal management function network element-CP can determine the AMF and the RAN corresponding to the AMF based on the information in the request message #3. For the specific process, refer to the description of S504, which will not be described again here.
  • the terminal management function network element-CP may send an inventory request #5 to the AMF.
  • the content included in inventory request #5 can refer to inventory request #1 in S504. The difference is that inventory request #5 does not include notification address #2 and association identifier #2, but includes CN tunnel information #1.
  • S907 The AMF sends inventory request #6 (another example of the second inventory request) to the RAN.
  • the content included in inventory request #6 can refer to inventory request #2 in S505. The difference is that inventory request #6 does not include notification address #2 and association identifier #2, but includes CN tunnel information #1.
  • This inventory response #6 may also be called an inventory response message, which includes the AN tunnel information.
  • the AN tunnel information is the tunnel endpoint through which the RAN receives downlink data.
  • AMF sends inventory response #5 to the label management function-CP.
  • This inventory response #5 may also be called an inventory response message, which includes the AN tunnel information.
  • the label management function-CP sends a session update request message to the label management function-UP, and the message includes AN Tunnel information.
  • the label management function-UP returns a response message, that is, a session update response message, to the label management function-CP.
  • S904 to S911 can also be understood as the process of establishing a tunnel.
  • RAN determines that the inventory of terminal #1 is completed, RAN sends a query request for the next tag to all selected tags, and continues to step S912.
  • the RAN determines that the inventory of all selected terminals is completed.
  • S912 to S914 refer to S506 to S508.
  • the RAN sends data #1 (an example of the first data) to the terminal management function network element-UP based on the CN tunnel information #1. Further, the terminal management function network element-UP sends data #1 to the AS based on the AS tunnel information.
  • the RAN After the RAN receives the identification and execution results of the target terminal, it can report them in two ways:
  • Method 1 After RAN determines that terminal #1 has completed the steps of S912, it sends data #1 to the terminal management function network element based on CN tunnel information #1.
  • S915 can be executed after S912.
  • data #1 includes execution information of terminal #1 (another example of the first information), that is, the identification and/or quantity of terminal #1. It should be understood that the value of the quantity is 1 at this time.
  • the execution information of terminal #1 also includes the execution result.
  • data #1 also includes the identification of the RAN.
  • data #1 also includes information #1, which is used to indicate that the inventory of terminal #1 is completed.
  • Method 2 After all received target terminals in the coverage area of the RAN complete the steps of S912, the RAN sends data #1 to the terminal management function network element-UP according to the CN tunnel information #1.
  • the identification and execution results of the target terminals are uniformly reported for all received target terminals.
  • S915 can be executed after S914.
  • data #1 includes the execution information (an example of the second information) of the terminals in the RAN coverage area of the target terminal, that is, the identification list and/or the number of terminals obtained by the RAN.
  • the terminal acquired by the RAN is the terminal that sends the identifier to the RAN, that is, the terminal within the RAN coverage area of the target terminal.
  • the execution information of the terminals in the RAN coverage area of the target terminal also includes a list of execution results corresponding to each terminal.
  • data #1 also includes the identification of the RAN.
  • the terminal management function network element-UP sends data #1 to the AS according to the AS tunnel information.
  • S916 The terminal management function network element-UP sends data report #1 to the terminal management function network element-CP.
  • the terminal management function network element-UP After receiving data #1, the terminal management function network element-UP can send the information in data #1 to the terminal management function network element-CP.
  • the terminal management function network element-UP can detect the information in data #1 according to the policy rules, thereby converting the data
  • the execution information of terminal #1 in #1 or the execution information of terminals in the RAN coverage area of the target terminal are sent to the terminal management function network element-CP.
  • the terminal management function network element-UP can also detect information #1 or information #2 according to the policy rules, thereby converting information #1 or information #2 Sent to the terminal management function network element-CP.
  • data report #1 is different for Method 1 and Method 2 in S915.
  • data report #1 includes execution information of terminal #1, that is, at least one of the identification, quantity 1, and execution result of terminal #1.
  • data report #1 also includes information #1, which is used to indicate that the inventory of terminal #1 is completed.
  • the data report #1 includes the execution information of the terminals in the RAN coverage area of the target terminal, that is, at least one of the identification list of the terminals obtained by the RAN, the number of terminals obtained by the RAN, and the list of execution results corresponding to each terminal. .
  • data report #1 also includes the identification of the RAN.
  • the terminal management function network element-CP sends charging information #4 (another example of the first charging information) to the CHF.
  • the terminal management function network element-CP After receiving the data report #1, that is, after receiving the execution information of the terminal #1 or the execution information of the terminals in the RAN coverage area of the target terminal, the terminal management function network element-CP can send the charging information #4 to the CHF. .
  • the content included in the charging information #4 is similar to the charging information #1 in S511, including an interim instruction or an update instruction.
  • charging information #4 may also include execution information of terminal #1 in the target terminal, that is, at least one of the identification, quantity 1, and execution result of terminal #1, or, charging Information #4 includes execution information of terminals within the RAN coverage area of the target terminal, that is, at least one of the terminal identification list obtained by the RAN, the number of terminals obtained by the RAN, and a list of execution results corresponding to each terminal.
  • the charging information #4 also includes the identification of the RAN.
  • the CHF can generate a bill for the process of RAN inventory of the terminal #1 based on the charging information #4.
  • the CHF can generate a bill for the process of RAN inventorying the terminals in its coverage area based on the charging information #4.
  • the RAN determines that the inventory of all selected tags is completed, and sends information #2 to the terminal management function network element.
  • the information #2 is used to indicate that the inventory of target terminals in the RAN coverage area is completed, or that the RAN inventory is completed.
  • the RAN can send information #2 to the terminal management function network element-CP through the AMF.
  • the RAN may send information #2 to the terminal management function network element-CP through the user.
  • the RAN includes information #2 in data #1
  • the terminal management function network element-UP includes information #2 in data report #1.
  • the terminal management function network element-CP After receiving information #2, the terminal management function network element-CP determines that the RAN inventory is completed, thereby initiating tunnel release.
  • the terminal management function network element-CP determines that the inventory of the target terminal is completed or determines that the timer has expired.
  • the specific way for the terminal management function network element-CP to determine that the target terminal inventory is completed may be the terminal management function.
  • the network element-CP determines that all the RANs determined in S906 have sent information #2.
  • the terminal management function network element-CP executes S922.
  • the terminal management function network element-CP sends the accounting request message #5 (another example of the third message) to the CHF.
  • S921 to S923 are optional steps.
  • the terminal management function network element may not execute S921 and S922. In this case, the CHF will not execute S923.
  • the method 900 shown in Figure 9 introduces the charging in the inventory scenario where the RAN reports the inventory results through the terminal management function network element-UP, and in this inventory scenario, the execution of the command is initiated by the RAN. Therefore, the charging method provided by the embodiment of the present application can be applied to various inventory scenarios and has better compatibility and flexibility.
  • FIG 10 is another schematic flow chart of a charging method provided by this application.
  • the method 1000 shown in Figure 10 can be regarded as another specific implementation of the above method 300. Specifically, the method 1000 shown in Figure 10 introduces the charging in the scenario where the AF initiates an execution command and the RAN reports the inventory results through the terminal management function network element-UP.
  • the applied AF sends request message #5 (another example of the first message) to the terminal management function network element-CP.
  • the request message #5 is similar to the request message #3 shown in the above-mentioned S901.
  • the request message #5 is used to request the first operation on the target terminal.
  • the difference between the request message #5 and the request message #3 is that : Request message #5 does not include an execution command.
  • the terminal management function network element-CP sends the accounting request message #6 (another example of the second message) to the CHF.
  • the charging request message #6 is similar to the charging request message #5 shown in the above-mentioned S902, except that the charging request message #6 does not include an execution command.
  • the CHF starts accounting according to the accounting request message #6, and sends a response message to the terminal management function network element-CP.
  • the response message may be a charging data response message.
  • the terminal management function network element-CP sends request message #4 to the terminal management function network element-UP.
  • the terminal management function network element-UP sends response message #4 to the terminal management function network element-CP.
  • S1004 to S1005 refer to S904 to S905.
  • the terminal management function network element-CP sends inventory request #7 (another example of the first inventory request) to the AMF.
  • the content included in inventory request #7 can refer to inventory request #5 in S906. The difference is that inventory request #7 does not include an execution command.
  • AMF sends inventory request #8 (another example of the second inventory request) to the RAN.
  • the content included in inventory request #8 can refer to inventory request #6 in S907. The difference is that inventory request #8 does not include an execution command.
  • AMF sends inventory response #7 to the tag management function-CP.
  • the label management function-CP sends a session update request message to the label management function-UP, and the message includes AN tunnel information.
  • the label management function-UP returns a response message, that is, the session update response message, to the label management function-CP.
  • S1008 to S101 refer to S908 to S911.
  • the inventory process includes the RAN sending radio frequency signals, selection messages, and query requests.
  • Terminal #1 completes the random access process and sends identification information to the RAN.
  • the RAN sends data #2 to the terminal management function network element-UP based on the CN tunnel information #1. Further, the terminal management function network element-UP sends data #2 to the AS based on the AS tunnel information.
  • data #2 includes execution information of terminal #1, that is, the identification and/or quantity of terminal #1. It should be understood that the value of quantity is 1 at this time.
  • data #2 also includes the identification of the RAN.
  • the AF sends the execution commands to the RAN through the user.
  • the AF sends data #3 to the terminal management function network element-UP through the AS, and further, the terminal management function network element-UP sends data #3 to the RAN.
  • data #3 includes execution commands.
  • Terminal #1 sends the execution result to the RAN.
  • the RAN sends data #4 (an example of the first data) to the terminal management function network element-UP based on the CN tunnel information #1. Further, the terminal management function network element-UP sends data #4 to the AS based on the AS tunnel information.
  • data #4 includes execution results.
  • S1018 The AF sends an instruction of completion of inventory of terminal #1 to the RAN through the user (another example of the first information).
  • data #5 includes an indication that the inventory of terminal #1 is completed.
  • the indication of completion of the inventory of terminal #1 is an example of the first information
  • S1018 can be understood as a process in which the AF determines the first information and sends the first information to the RAN.
  • the terminal management function network element-UP sends data report #2 to the terminal management function network element-CP.
  • the terminal management function network element-UP may send data report #2 to the terminal management function network element-CP after receiving data #5.
  • data report #2 includes the execution information of terminal #1 included in data #2 in S1013, that is, the identification or quantity 1 of terminal #1.
  • the data #2 sent by the terminal management function network element-UP may also include the execution information of the terminal #1 included in the data #4, that is, execution result.
  • data report #2 may also include the identification of the RAN.
  • data report #2 may also include execution commands included in data #3.
  • data report #2 also includes an indication that the inventory of terminal #1 in S1018 is completed.
  • the terminal management function network element-CP sends charging information #5 (another example of the first charging information) to the CHF.
  • charging information #5 may be sent to the CHF.
  • the charging information #5 may include the information included in the data report #2, that is, at least one of the identification of the terminal #1, the quantity 1, the execution command, and the execution result.
  • the charging information #5 includes an interim instruction or an update instruction.
  • the charging information #5 also includes the identification of the RAN.
  • S1020 may not be executed, that is, the terminal management function network element-CP saves the received execution information of terminal #1.
  • CHF returns a response message to the terminal management function network element-CP.
  • the CHF may generate a bill for the process of RAN inventory of terminal #1 based on charging information #5.
  • RAN determines that the inventory of terminal #1 is completed, RAN sends a query request for the next tag to all selected tags, and continues to execute step S1012.
  • the RAN determines that the command for terminal #1 has been executed based on the information #1 from the terminal management function network element in S1018.
  • the RAN, the target terminal, the terminal management function network element-CP, the terminal management function network element-UP, AF, AS, and CHF can continue to execute S1013-S1022.
  • the RAN determines that the inventory of all selected tags is completed, and sends information #2 (an example of the second information) to the terminal management function network element-CP.
  • This information #2 is used to indicate that the target terminal inventory within the RAN coverage area is completed, or in other words, the RAN inventory is completed.
  • the method 1000 also includes S1024 to S1025.
  • the terminal management function network element-CP sends charging information #6 (another example of the first charging information) to the CHF.
  • the accounting information #6 includes an interim instruction or an update instruction.
  • the charging information #6 includes the execution information of multiple terminals #1 saved by the terminal management function network element-CP. It should be understood that the execution information of multiple terminal #1 is summarized into the execution information of the terminals within the RAN coverage area of the target terminal, that is, the identification list of the terminals obtained by the RAN, the number of terminals obtained by the RAN, and the execution results corresponding to each terminal. list of at least one.
  • the charging information #6 also includes the identification of the RAN.
  • the terminal management function network element-CP may not send the accounting information #5 after receiving the execution information of the terminal #1, but save the execution information of the terminal #1, and after receiving the information #2, send the accounting information #5.
  • Charging information #6 includes execution information that stores multiple terminals #1, thereby requesting CHF to charge for the inventory process of target terminals within the RAN coverage area.
  • CHF returns a response message to the terminal management function network element-CP.
  • the message in the charging information #6 includes the execution information of the terminals in the RAN coverage area of the target terminal, and the CHF can generate a bill for the process of RAN inventorying the terminals in its coverage area based on the charging information #6.
  • the terminal management function network element-CP initiates tunnel release.
  • the terminal management function network element-CP determines that the inventory of the target terminal is completed or determines that the timer has expired.
  • the terminal management function network element-CP sends the accounting request message #7 (another example of the third message) to the CHF.
  • CHF returns a response message to the terminal management function network element.
  • S1026 to S1029 refer to S920 to S923.
  • the method 1000 shown in Figure 10 introduces the charging in the inventory scenario where the RAN reports the inventory results through the terminal management function network element-UP, and in this inventory scenario, the execution command is initiated by the AF. Therefore, the charging method provided by the embodiment of the present application can be applied to various inventory scenarios and has better compatibility and flexibility.
  • this application can also provide charging in a scenario where the terminal management function network element saves execution commands, initiates execution commands, and the RAN reports the inventory results through the terminal management function network element-UP.
  • the specific steps can be combined with method 600 and method 1000, and will not be described again here.
  • terminal management function network element-CP and terminal management function network element-UP in Figures 9 and 10 can be co-located with NEF.
  • the above-mentioned terminal management function network element-CP and terminal management function network element-CP can be understood as the actions performed by NEF.
  • terminal management function network element-CP and the terminal management function network element-UP in Figures 9 and 10 can be newly added independent functional network elements, and the terminal management function network element-CP can be used for forwarding Inventory requests and responses between AF and AMF, the terminal management function network element-UP can be used to forward user plane data between RAN and AS.
  • terminal management function network element-CP and terminal management function network element-UP in Figures 9 and 10 can be newly added independent functional network elements, and the terminal management function network element-CP can be used for forwarding
  • the inventory request and response between NEF and AMF, that is to say, the inventory request and response between the terminal management function network element-CP and AF shown in Figure 9 and Figure 10 need to be forwarded through NEF, the terminal management function network element- UP can be used to forward user plane data between RAN and AS.
  • terminal management function network element-CP in Figures 9 and 10 can be co-located with the AMF.
  • the interaction between the AMF and the terminal management function network element-CP can be regarded as internal interaction.
  • the terminal management function network element -UP can be a newly added independent functional network element that can be used to forward user plane data between RAN and AS.
  • the user plane tunnel is initiated and established by the terminal management function network element-UP.
  • the user plane tunnel may be initiated and established by the AMF. The following describes the process of tunnel establishment initiated by AMF with reference to Figures 12 to 13.
  • FIG 12 is another schematic flow chart of a charging method provided by this application.
  • the method 1200 shown in Figure 12 can be regarded as a specific implementation of the above method 400.
  • the method 1200 shown in Figure 12 introduces the charging in the scenario where the terminal management function network element sends the execution command to the RAN, the RAN saves and initiates the execution command, and the RAN reports the inventory results through UPF.
  • the applied AF sends request message #6 (an example of the seventh message) to the terminal management function network element.
  • the request message #6 is used to request a first operation on the target terminal.
  • the request message #6 includes the identification information of the target terminal, the instruction information of the first operation, and the application information.
  • the application information includes identification information of the application or data network access identification information of the application.
  • the above request message #6 when the above request message #6 does not carry the indication information of the first operation, it means that the first operation is query, that is, querying the terminal identity; or, when the above request message #6 carries the instruction information of the first operation, and the instruction information of the first operation includes query, it means that the first operation is a query.
  • any first operation other than querying the terminal identity may be called an execution command.
  • the request message #1 also includes first indication information, operating parameters and application server (AS) tunnel information.
  • AS application server
  • the AS tunnel information is used to indicate the user plane port or user plane address of the application server for receiving the inventory result.
  • the AS tunnel information is the address of the AS.
  • the terminal management function network element when the terminal management function network element receives the request message #6, the terminal management function network element can start the timer.
  • the terminal management function network element sends the accounting request message #8 (an example of the eighth message) to the CHF.
  • the accounting request message #8 includes a start indication.
  • the accounting request message #8 may also include identification information of the target terminal, instruction information of the first operation, operation parameters, first instruction information, identification information of the application, and AS tunnel information.
  • the charging request message #8 also includes identification #1, or charging identification #1, which is used to identify the charging request of the terminal management function network element, or is used to identify the charging request message #8.
  • the CHF starts accounting according to the accounting request message #8, and sends a response message to the terminal management function network element.
  • the response message may be a charging data response message.
  • the terminal management function network element sends request message #7 (an example of the ninth message) to the AMF.
  • This request message #7 is used to request to perform the first operation on the target terminal.
  • the terminal management function network element can determine the AMF and the RAN corresponding to the AMF based on the information in the request message #6. For the specific process, refer to the description of S504, which will not be described again here.
  • the terminal management function network element may send request message #7 to the AMF.
  • the request message #7 includes the identification information of the target terminal, the instruction information of the first operation, the operation parameters, the second instruction information, the identification information of the application, and the AS tunnel information.
  • the area used by the second indication information includes the area managed by the AMF, and the second indication information includes 3GPP location information (such as TA list, Cell list, etc.)
  • Request message #7 also includes identification #1.
  • S1205 AMF sends a session establishment request message (an example of the fourth message) to SMF.
  • the AMF determines that a user plane tunnel needs to be established based on the application identifier and other information in order to transmit the inventory results. Therefore, the AMF sends a session establishment request message to the SMF.
  • the session establishment request message includes identification information of the target terminal, identification information of the application, AS tunnel information and identification #1.
  • the session establishment request message is used to request the establishment of tunnel #1 (an example of the first session), where tunnel #1 is used to transmit execution information of one or more terminals in the target terminal.
  • S1206 SMF sends a tunnel establishment request message to UPF.
  • SMF selects an appropriate UPF based on the application identifier.
  • the SMF After the SMF selects the appropriate UPF, it sends a request message to the UPF to establish a tunnel, that is, a tunnel establishment request message.
  • the tunnel establishment request message is used to request establishment of a user plane tunnel, and the tunnel establishment request message includes AS tunnel information.
  • tunnel #1 is established between UPF and AS.
  • the user plane tunnel between the UPF and the AS can be established.
  • UPF sends a tunnel establishment response message to SMF.
  • the tunnel establishment response message includes CN tunnel information #2, and CN tunnel information #2 is the tunnel endpoint for UPF to receive uplink data.
  • S1209 SMF sends accounting request message #9 (an example of the fifth message) to CHF.
  • the SMF sends a charging request message #9 to the CHF.
  • the charging request message #9 is used to request to start charging for the first operation of the target terminal.
  • the accounting request message #9 includes a Start indication.
  • the accounting request message #9 may also include the identification information of the target terminal, the identification information of the application, and the AS tunnel information.
  • Accounting request message #9 also includes identification #1.
  • CHF starts accounting according to the accounting request message #9.
  • CHF associates the charging request message #8 with the charging request message #9.
  • the CHF determines based on the identifier #1 that the charging request message #8 and the charging request message #9 are associated with the same charging request. Therefore, the charging request initiated by the SMF and the charging initiated by the terminal management function network element are associated. ask. CHF generates CDR after summarizing the information obtained from the terminal management function network element and SMF.
  • CHF associates the resources identified by URI#1 and URI#3 based on identification #1, or associates the resources identified by URI#2 and URI#4 based on identification #1.
  • the SMF sends an establishment response message to the AMF.
  • the establishment response message includes CN tunnel information #2.
  • AMF sends inventory request #9 to RAN.
  • the inventory request #9 includes the identification information of the target terminal, the instruction information of the first operation, the operation parameters, and the identification information of the application received by the AMF in S1204.
  • Inventory request #9 also includes third indication information, and the area used by the third indication information to indicate includes the RAN management area, the third indication information includes 3GPP location information (such as TA list, Cell list, etc.).
  • Inventory request #9 also includes CN tunnel information #2.
  • RAN saves the received target terminal identification information, first operation instruction information, operation parameters, application identification information, third instruction information, CN tunnel information #2 and other information, and sends a response to the AMF, that is, inventory response #9 .
  • This inventory response #9 may also be called an inventory response message, which includes AN tunnel information.
  • the AN tunnel information is the tunnel endpoint through which the RAN receives downlink data.
  • AMF sends a request message to SMF.
  • the request message includes AN tunnel information.
  • SMF sends a request message to UPF.
  • the request message includes AN tunnel information.
  • the RAN sends radio frequency signals to all terminals in the coverage area to provide excitation signals to the terminals in the RAN's coverage area, thereby causing the terminal equipment to send signals to the RAN.
  • the RAN sends a selection message to the terminals within the coverage area of the RAN.
  • the RAN then sends a query request to all selected terminals. Any target terminal covered by the RAN, recorded as terminal #1 (an example of the first terminal), will send identification information to the RAN.
  • this step is a random access process for terminal #1, and the random access process will be performed for any terminal among the target terminals.
  • the RAN sends the execution commands to the terminal #1.
  • terminal #1 After terminal #1 completes executing the command, it sends the execution result to the RAN. For example, if the execution command is read, the execution result includes the read data; if the execution command is write, the execution result is an indication of success or failure and the execution result.
  • the RAN sends data #6 (another example of the first data) to the UPF based on the CN tunnel information #2. Further, the UPF sends data #6 to the AS based on the AS tunnel information.
  • the RAN After the RAN determines that the inventory of terminal #1 is completed, it can send data #6 to the UPF.
  • data #6 includes execution information of terminal #1, that is, the identification and/or quantity of terminal #1. It should be understood that the value of quantity is 1 at this time.
  • the execution information of terminal #1 in data #6 also includes the execution result.
  • data #6 also includes information #1, which is used to indicate that terminal #1 has completed the inventory.
  • S1218 may not be executed, that is, the RAN may also save the execution information of terminal #1 first.
  • UPF sends data report #3 to SMF.
  • UPF After receiving data #6, UPF can send data report #3 to SMF.
  • Data report #3 includes execution information of terminal #1 in data #6, that is, at least one of terminal #1's identification, quantity 1, and execution result.
  • data report #3 also includes information #1, which is used to indicate that the inventory of terminal #1 is completed.
  • data report #3 also includes the identification of the RAN.
  • UPF can detect the execution information of terminal #1 according to the policy rules, thereby converting the execution information of terminal #1 Send to SMF.
  • UPF can also detect information #1 according to the policy rules, thereby sending information #1 to the SMF.
  • the SMF sends charging information #7 (another example of the second charging information) to the CHF.
  • the SMF After receiving the data report #3, that is, after receiving the execution information of the terminal #1, the SMF can send the charging information #7 to the CHF.
  • the accounting information #7 includes the execution information of the terminal #1 in the data report #3, that is, at least one of the identification, quantity 1, and execution result of the terminal #1.
  • the charging information #7 also includes the identification of the RAN.
  • CHF can generate a CDR based on the information carried in the charging information #7 and the charging request message #9, and send it to the accounting system.
  • the CHF may generate a CDR after receiving each piece of charging information #7, or generate a CDR based on multiple pieces of charging information #7 after receiving multiple second charging information according to network policies.
  • S1220 to S1221 may not be executed. That is, SMF may also save the information in data report #3 first.
  • RAN determines that the inventory of terminal #1 is completed, RAN sends a query request for the next tag to all selected tags, and continues to step S1217.
  • the RAN determines that the inventory for the terminal #1 is completed by determining that both the indication information and the operation parameters of the first operation in S1213 have been completed for the terminal #1.
  • the RAN, target terminal, UPF, SMF, terminal management function network element, AS, and CHF can continue to execute S1218 to S1222.
  • the method 1200 also includes S1223 to S1225.
  • RAN determines that the inventory of all selected tags is completed and sends data #6 to UPF. Further, UPF sends data #6 to the AS based on the AS tunnel information.
  • This data #6 includes the execution information (an example of the second information) of the terminals in the RAN coverage area of the target terminal, that is, the identification list and/or the number of terminals acquired by the RAN.
  • the terminal acquired by the RAN is the terminal that sends the identifier to the RAN, that is, the terminal within the RAN coverage area of the target terminal.
  • information #2 also includes a list of execution results corresponding to each terminal.
  • data #6 also includes the identification of the RAN.
  • UPF sends data report #3 to SMF.
  • UPF After receiving data #6, UPF can send data report #3 to SMF.
  • the data report #3 includes execution information of terminals in the target terminal within the RAN coverage area, that is, at least one of the identification list of the terminals obtained by the RAN, the number of terminals obtained by the RAN, and a list of execution results corresponding to each terminal.
  • data report #3 also includes the identification of the RAN.
  • UPF can detect the information in data #1 according to the policy rules, thereby converting the target terminal in data #1 to The execution information of terminals within the RAN coverage area is sent to the SMF.
  • UPF can also detect information #2 according to the policy rules, thereby sending information #2 to the SMF.
  • the SMF sends charging information #8 (another example of the second charging information) to the CHF.
  • the SMF may send the charging information #8 to the CHF after receiving the data report #3, that is, after receiving the execution information of the terminals within the RAN coverage area of the target terminal.
  • the charging information #8 includes execution information of terminals in the target terminal within the RAN coverage area, that is, at least one of the identification list of the terminals obtained by the RAN, the number of terminals obtained by the RAN, and the list of execution results corresponding to each terminal.
  • the charging information #8 also includes the identification of the RAN.
  • CHF returns a response message to SMF.
  • the CHF may generate a bill for the process of RAN inventorying terminals within its coverage area based on the charging information #8 and the charging request message #9.
  • the RAN sends information #2 (an example of the second information) to the SMF.
  • the information #2 is used to indicate that the target terminal inventory in the RAN coverage area is completed, or that the RAN inventory is completed.
  • the SMF can execute S1225 after receiving the information #2, that is, send the charging information #8 to the CHF.
  • the RAN may send information #2 to the SMF via the AMF.
  • the AMF can send information #2 to the SMF, or it can also send a release request message (an example of the eleventh message) to the SMF to request the release of tunnel #1.
  • SMF can trigger tunnel release after receiving message #2 or release request message.
  • S1229 The SMF sends the accounting request message #10 (an example of the sixth message) to the CHF.
  • SMF After receiving information #2, SMF can also send accounting request message #10 to CHF.
  • the accounting request message #10 includes a stop indication, and the stop indication is used to instruct the CHF to close the accounting for the accounting request message #9.
  • the CHF can turn off the current charging of the SMF according to the stop instruction.
  • the terminal management function network element determines that the inventory of the target terminal is completed or determines that the timer has expired.
  • the specific way in which the terminal management function network element determines that the target terminal inventory is completed is that the terminal management function network element receives the information #2 of each of the RANs determined in S1204.
  • the AMF can further send information #2 to the terminal management function network element.
  • the terminal management function network element starts the timer, then when the terminal management function network element determines that the timer has expired, the terminal management function network element executes S1232.
  • the terminal management function network element sends the accounting request message #11 (an example of the tenth request message) to the CHF.
  • the accounting request message #11 includes a Stop indication, and the stop indication is used to instruct the CHF to close accounting for the accounting request message #8.
  • CHF can close this billing according to the stop instruction. If CHF still has an unclosed CDR, CHF sends the CDR to the accounting system.
  • S1231 to S1233 are optional steps.
  • the terminal management function network element may not execute S1231 and S1232. In this case, the CHF will not execute S1233.
  • the method 1200 shown in Figure 12 introduces the charging in the inventory scenario where the RAN reports the inventory results through UPF, and in this inventory scenario, the execution command is initiated by the RAN. Therefore, the charging method provided by the embodiment of the present application can be applied to various inventory scenarios and has better compatibility and flexibility.
  • FIG 13 is another schematic flow chart of a charging method provided by this application.
  • the method 1300 shown in Figure 13 can be regarded as a specific implementation of the above method 400.
  • the method 1300 shown in Figure 13 introduces the charging in the scenario where the AF determines the execution command, initiates the execution command, and the RAN reports the inventory result through UPF.
  • the applied AF sends request message #8 (another example of the seventh message) to the terminal management function network element.
  • the request message #8 is similar to the request message #6 shown in the above-mentioned S1201.
  • the request message #8 is used to request the first operation on the target terminal.
  • the request message #8 is different from the request message #6.
  • the problem is: request message #8 does not include an execution command.
  • the terminal management function network element sends the accounting request message #12 (an example of the eighth message) to the CHF.
  • the charging request message #12 is similar to the charging request message #9 shown in the above-mentioned S1202, except that the charging request message #12 does not include an execution command.
  • the CHF starts accounting according to the accounting request message #12, and sends a response message to the terminal management function network element.
  • the response message may be a charging data response message.
  • the terminal management function network element sends request message #9 (an example of the ninth message) to the AMF.
  • the request message #9 is similar to the request message #7 shown in the above-mentioned S1204, except that the request message #9 does not include an execution command.
  • AMF sends a session establishment request message to SMF.
  • S1306 SMF sends a tunnel establishment request message to UPF.
  • UPF sends a tunnel establishment response message to SMF.
  • S1309 SMF sends accounting request message #9 to CHF.
  • CHF associates the charging request message #8 with the charging request message #9.
  • S1312 SMF sends a session establishment response message to AMF.
  • S1305 to S1312 refer to S1205 to S1212, which will not be described again here.
  • AMF sends inventory request #10 to RAN.
  • inventory request #10 is similar to inventory request #9 shown in the above-mentioned S1213, except that the inventory Request #10 does not include an execution command.
  • AMF sends a request message to SMF.
  • SMF sends a request message to UPF.
  • S1314 to S1316 refer to S1214 to S1216, which will not be described again here.
  • the inventory process includes the RAN sending radio frequency signals, selection messages, and query requests.
  • Terminal #1 completes the random access process and sends identification information to the RAN.
  • the RAN sends data #7 (another example of the first data) to the UPF based on the CN tunnel information #2. Further, the UPF sends data #7 to the AS based on the AS tunnel information.
  • data #7 includes execution information of terminal #1, that is, the identification and/or quantity of terminal #1. It should be understood that the value of quantity is 1 at this time.
  • the AF sends the execution commands to the RAN through the user.
  • the AF sends data #8 to the UPF through the AS, and further, the UPF sends data #8 to the RAN.
  • data #8 includes execution commands.
  • Terminal #1 sends the execution result to the RAN.
  • the RAN sends data #9 (an example of the first data) to the UPF based on the CN tunnel information #2. Further, the UPF sends data #9 to the AS based on the AS tunnel information.
  • data #9 includes execution information of terminal #1, that is, execution results.
  • S1323 The AF sends an instruction to complete the inventory of terminal #1 through the user to the RAN (another example of the first information).
  • the AF sends data #10 to the UPF through the AS, and further, the UPF sends data #10 to the RAN.
  • data #10 includes information #1, and information #1 is used to indicate that terminal #1 has completed the inventory.
  • UPF sends data report #4 to SMF.
  • Data report #4 includes execution information of terminal #1 in data #7, that is, at least one of the identification and/or the number of terminal #1.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请实施例提供了一种计费的方法和通信装置，该方法包括：接收来自应用的应用网元的第一消息，该第一消息用于请求对目标终端执行第一操作；发送第二消息，该第二消息用于请求启动对目标终端的第一操作的计费；发送第一计费信息，该第一计费信息包括目标终端中的一个或多个终端的执行信息，该第一计费信息用于对一个或多个终端执行第一操作的过程计费。通过该方案，能够实现终端管理过程的计费。

Description

一种计费的方法和通信装置
本申请要求申请日为2022年3月17日、申请号为202210262669.2、申请名称为“一种计费的方法和通信装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信领域，更具体地，涉及一种计费的方法和通信装置。
背景技术
无源物联网(passive Internet of things，P-IoT)终端具有大规模部署的应用前景，预测未来将覆盖千亿级别的设备数目。
目前，提出一种新型无源物联网技术，将读卡器集成于接入网设备，具有终端管理需求的企业通过部署的第三代合作伙伴计划(3rd generation partnership project，3GPP)网络完成无源物联网终端的管理。该技术能够实现通信距离的增加以及终端的统一管理，为无源物联网终端的大规模部署提供技术支持。
在这种新型无源物联网技术中，运营商需要向具有终端管理需求的企业收取费用，因此，如何实现终端管理过程的计费是一个值得关心的问题。
发明内容
本申请实施例提供一种计费的方法和通信装置，能够实现终端管理过程的计费。
第一方面，提供了一种计费的方法，该方法可以由终端管理功能网元执行，或者，也可以由配置于终端管理功能网元中的芯片或电路执行，本申请对此不作限定。
该方法包括：接收来自应用的应用网元的第一消息，该第一消息用于请求对目标终端执行第一操作；发送第二消息，该第二消息用于请求启动对目标终端的第一操作的计费；发送第一计费信息，该第一计费信息包括目标终端中的一个或多个终端的执行信息，该第一计费信息用于对一个或多个终端执行第一操作的过程计费。
基于上述技术方案，终端管理功能网元可以基于第一消息向计费网元发起计费请求，并在一个或多个终端的第一操作执行完成后，向计费网元发送计费信息，从而计费网元可以根据计费请求和计费信息对一个或多个终端执行第一操作的过程计费。通过该方案，能够实现终端管理过程的计费。
其中，一个或多个终端的执行信息也就是对一个或多个终端执行第一操作后所获得的信息。
结合第一方面，在第一方面的某些实现方式中，该一个或多个终端包括第一终端，该方法还包括：获取第一信息，其中，该第一信息用于指示第一终端的第一操作执行完成；或，该第一信息包括第一终端的执行信息。
基于上述方案，终端管理功能网元可以在接收到第一终端的第一操作执行完成的指示后，或者在接收到第一终端的执行信息后，向计费网元发送该第一终端的执行计费信息，从而计费网元可以针对第一终端执行第一操作的过程计费。通过该方案，能够实现终端粒度的计费，有助于提升计费的灵活性。
结合第一方面，在第一方面的某些实现方式中，该一个或多个终端包括至少两个第一终端，该方法还包括：获取第一信息，其中，该第一信息用于指示第一终端的第一操作执行完成；或，该第一信息包括第一终端的执行信息。
基于上述方案，终端管理功能网元可以在接收到至少两个第一终端的第一操作执行完成的指示后，或者在接收到至少两个第一终端的执行信息后，向计费网元发送该至少两个第一终端的执行计费信息，从而计费网元可以针对该至少两个第一终端执行第一操作的过程计费。通过该方案，能够实现对任意个数的终端的计费，有助于提升计费的灵活性。
结合第一方面，在第一方面的某些实现方式中，该第一信息来自于第一接入网设备或应用网元，其中，第一接入网设备用于对第一终端执行第一操作。
基于上述方案，本申请的方法可以适用于多种不同的架构，扩展性较强。
结合第一方面，在第一方面的某些实现方式中，该第一终端的执行信息包括以下至少一项：第一终端的标识、第一终端执行第一操作的执行结果。
基于上述方案，第一计费信息可以包括第一终端的执行信息，有助于提升计费精度。
结合第一方面，在第一方面的某些实现方式中，该一个或多个终端包括第一接入网设备的覆盖区域内的终端，该方法还包括：接收来自于第一接入网设备的第二信息，其中，第二信息用于指示目标终端中第一接入网设备的覆盖区域内的终端的第一操作执行完成；或，第二信息包括目标终端中第一接入网设备的覆盖区域内的终端的执行信息。
基于上述方案，终端管理功能网元可以在接收到第一接入网设备的覆盖区域内的终端的第一操作执行完成的指示后，或者在接收到第一接入网设备的覆盖区域内的终端的执行信息后，向计费网元发送该第一接入网设备的覆盖区域内的终端的执行信息，从而计费网元可以针对第一接入网设备的覆盖区域内的终端执行第一操作的过程计费。通过该方案，能够实现接入网设备粒度的计费，有助于提升计费的灵活性。
结合第一方面，在第一方面的某些实现方式中，该一个或多个终端包括至少两个第一接入网设备的覆盖区域内的终端，该方法还包括：接收来自于至少两个第一接入网设备的第二信息，其中，第二信息用于指示目标终端中第一接入网设备的覆盖区域内的终端的第一操作执行完成；或，第二信息包括目标终端中第一接入网设备的覆盖区域内的终端的执行信息。
基于上述方案，终端管理功能网元可以在接收到来自至少两个第一接入网设备关于第一接入网设备覆盖区域内的终端的第一操作执行完成的指示后，或者在接收到至少两个第一接入网设备关于第一接入网设备的覆盖区域内的终端的执行信息后，向计费网元发送该至少两个第一接入网设备的覆盖区域内的终端的执行信息，从而计费网元可以针对该至少两个第一接入网设备的覆盖区域内的终端执行第一操作的过程计费。通过该方案，能够实现任意个数的接入网设备的盘点过程计费，有助于提升计费的灵活性。
结合第一方面，在第一方面的某些实现方式中，目标终端中第一接入网设备的覆盖区域内的终端的执行信息包括以下至少一项：第一接入网设备所获取的终端的标识列表、第 一接入网设备所获取的终端的数量、第一接入网设备所获取的终端执行第一操作的执行结果。
基于上述方案，第一计费信息可以包括目标终端中第一接入网设备的覆盖区域内的终端的执行信息，有助于提升计费精度。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：确定目标终端的第一操作执行完成；发送第三消息，第三消息用于请求关闭对目标终端的第一操作的计费。
基于上述方案，终端管理功能网元可以在目标终端的第一操作执行完成时请求关闭对目标终端的第一操作的计费，能够避免资源浪费。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：根据第一消息确定一个或多个接入网设备；其中，确定目标终端的第一操作执行完成，包括：根据一个或多个接入网设备的第二信息确定目标终端的第一操作执行完成，第二信息用于指示目标终端中一个或多个接入网设备的覆盖区域内的终端的第一操作执行完成。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：当接收到第一消息时，启动目标终端执行第一操作的定时器；在定时器超时的情况下，发送第三消息，该第三消息用于请求关闭对目标终端的第一操作的计费。
基于上述方案，终端管理功能网元可以利用定时器，在定时器超时时请求关闭对目标终端的第一操作的计费，能够避免资源浪费。
结合第一方面，在第一方面的某些实现方式中，该第一计费信息包括第一接入网设备的标识，该第一接入网设备用于对一个或多个终端执行第一操作。
基于上述方案，第一计费信息可以包括对一个或多个终端执行第一操作的第一接入网设备的标识，有助于提升计费精度。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：向终端管理用户面功能网元发送策略规则，该策略规则用于第一信息或第二信息，其中，终端管理用户面功能网元用于向应用传输一个或多个终端的执行信息。
基于上述方案，终端管理功能网元可以将第一信息或第二信息的检测规则发送至终端管理用户面功能网元，从而终端管理用户面功能网元能够识别第一信息或第二信息，进一步向终端管理功能网元发送第一信息或第二信息，有助于提升准确性。
结合第一方面，在第一方面的某些实现方式中，该第一消息和第二消息中包括以下至少一种：第一操作的指示信息、第一操作对应的操作参数、第一指示信息、目标终端的标识信息、应用的标识信息、应用网元的地址信息、第一隧道信息，其中，第一指示信息用于指示待执行第一操作的区域，第一隧道信息用于指示应用的服务器接收数据的用户面端口。
基于上述技术方案，该第二消息中可以包括第一消息中的不同信息，提供更多与计费相关的信息，提高计费性能。
结合第一方面，在第一方面的某些实现方式中，该目标终端的标识信息，包括以下信息中的至少一项：目标终端中任意一个目标终端的指示信息、目标终端的标识所属的取值区间、目标终端的标识的列表、目标终端所属终端组的组标识、目标终端所属用户的标识信息、或者目标终端所属应用的标识信息。
基于上述技术方案，目标终端的标识信息可以有多种不同的形式，增加方案灵活性。
结合第一方面，在第一方面的某些实现方式中，该第一操作包括以下操作中的至少一个：查询终端标识、读、写、灭活、锁、块写、块擦、访问、加密、或解密。
第二方面，提供了一种计费的方法，该方法可以由会话管理网元执行，或者，也可以由会话管理网元中的芯片、芯片系统或电路执行，本申请对此不作限定。
该方法包括：接收第四消息，该第四消息用于请求建立第一会话，该第一会话用于传输目标终端中一个或多个终端执行第一操作的执行信息，该第四消息包括第一标识，该第一标识用于标识终端管理功能网元发起的对目标终端执行第一操作的计费；发送第五消息，该第五消息用于请求启动对目标终端的第一操作的计费，该第五消息包括该第一标识；发送第二计费信息，该第二计费信息包括目标终端中的一个或多个终端的执行信息，该第二计费信息用于对一个或多个终端执行第一操作的过程计费。
基于上述技术方案，会话管理网元可以基于第四消息向计费网元发起计费请求，并在一个或多个终端的第一操作执行完成后，向计费网元发送计费信息，从而计费网元可以根据计费请求和计费信息对一个或多个终端执行第一操作的过程计费。通过该方案，能够实现终端管理过程的计费。
其中，一个或多个终端的执行信息也就是对一个或多个终端执行第一操作后所获得的信息。
结合第二方面，在第二方面的某些实现方式中，该一个或多个终端包括第一终端，该方法还包括：获取第一信息，其中，该第一信息用于指示第一终端的第一操作执行完成；或，该第一信息包括第一终端的执行信息。
基于上述方案，会话管理网元可以在接收到第一终端的第一操作执行完成的指示后，或者在接收到第一终端的执行信息后，向计费网元发送该第一终端的执行计费信息，从而计费网元可以针对第一终端执行第一操作的过程计费。通过该方案，能够实现终端粒度的计费，有助于提升计费的灵活性。
结合第二方面，在第二方面的某些实现方式中，该一个或多个终端包括至少两个第一终端，该方法还包括：获取第一信息，其中，该第一信息用于指示第一终端的第一操作执行完成；或，该第一信息包括第一终端的执行信息。
基于上述方案，会话管理网元可以在接收到至少两个第一终端的第一操作执行完成的指示后，或者在接收到至少两个第一终端的执行信息后，向计费网元发送该至少两个第一终端的执行计费信息，从而计费网元可以针对该至少两个第一终端执行第一操作的过程计费。通过该方案，能够实现对任意个数的终端的计费，有助于提升计费的灵活性。
结合第二方面，在第二方面的某些实现方式中，该第一信息来自于第一接入网设备或应用网元，其中，第一接入网设备用于对第一终端执行第一操作。
基于上述方案，本申请的方法可以适用于多种不同的架构，扩展性较强。
结合第二方面，在第二方面的某些实现方式中，该第一终端的执行信息包括以下至少一项：第一终端的标识、第一终端执行第一操作的执行结果。
基于上述方案，第一计费信息可以包括第一终端的执行信息，有助于提升计费精度。
结合第二方面，在第二方面的某些实现方式中，该一个或多个终端包括第一接入网设备的覆盖区域内的终端，该方法还包括：接收来自于第一接入网设备的第二信息，其中，第二信息用于指示目标终端中第一接入网设备的覆盖区域内的终端的第一操作执行完成； 或，第二信息包括目标终端中第一接入网设备的覆盖区域内的终端的执行信息。
基于上述方案，会话管理网元可以在接收到第一接入网设备的覆盖区域内的终端的第一操作执行完成的指示后，或者在接收到第一接入网设备的覆盖区域内的终端的执行信息后，向计费网元发送该第一接入网设备的覆盖区域内的终端的执行信息，从而计费网元可以针对第一接入网设备的覆盖区域内的终端执行第一操作的过程计费。通过该方案，能够实现接入网设备粒度的计费，有助于提升计费的灵活性。
结合第二方面，在第二方面的某些实现方式中，该一个或多个终端包括至少两个第一接入网设备的覆盖区域内的终端，该方法还包括：接收来自于至少两个第一接入网设备的第二信息，其中，第二信息用于指示目标终端中第一接入网设备的覆盖区域内的终端的第一操作执行完成；或，第二信息包括目标终端中第一接入网设备的覆盖区域内的终端的执行信息。
基于上述方案，会话管理网元可以在接收到来自至少两个第一接入网设备关于第一接入网设备覆盖区域内的终端的第一操作执行完成的指示后，或者在接收到至少两个第一接入网设备关于第一接入网设备的覆盖区域内的终端的执行信息后，向计费网元发送该至少两个第一接入网设备的覆盖区域内的终端的执行信息，从而计费网元可以针对该至少两个第一接入网设备的覆盖区域内的终端执行第一操作的过程计费。通过该方案，能够实现任意个数的接入网设备的盘点过程计费，有助于提升计费的灵活性。
结合第二方面，在第二方面的某些实现方式中，目标终端中第一接入网设备的覆盖区域内的终端的执行信息包括以下至少一项：第一接入网设备所获取的终端的标识列表、第一接入网设备所获取的终端的数量、第一接入网设备所获取的终端执行第一操作的执行结果。
基于上述方案，第一计费信息可以包括目标终端中第一接入网设备的覆盖区域内的终端的执行信息，有助于提升计费精度。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：发送第六消息，第六消息用于请求关闭对目标终端的第一操作的计费。
基于上述方案，会话管理网元可以在目标终端的第一操作执行完成时请求关闭对目标终端的第一操作的计费，能够避免资源浪费。
结合第二方面，在第二方面的某些实现方式中，该第二计费信息包括第一接入网设备的标识，该第一接入网设备用于对一个或多个终端执行第一操作。
基于上述方案，第二计费信息可以包括对一个或多个终端执行第一操作的第一接入网设备的标识，有助于提升计费精度。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：向用户面网元发送策略规则，该策略规则用于第一信息或第二信息，其中，用户面网元用于向应用传输一个或多个终端的执行信息。
基于上述方案，会话管理网元可以将第一信息或第二信息的检测规则发送至用户面网元，从而用户面网元能够识别第一信息或第二信息，进一步向会话管理网元发送第一信息或第二信息，有助于提升准确性。
结合第二方面，在第二方面的某些实现方式中，该第四消息和第五消息中包括以下至少一种：第一隧道信息、目标终端的标识信息、应用的标识信息，其中，第一隧道信息用 于指示应用的服务器接收数据的用户面端口。
基于上述技术方案，该第五消息中可以包括第四消息中的不同信息，提供更多与计费相关的信息，提高计费性能。
结合第二方面，在第二方面的某些实现方式中，该目标终端的标识信息，包括以下信息中的至少一项：目标终端中任意一个目标终端的指示信息、目标终端的标识所属的取值区间、目标终端的标识的列表、目标终端所属终端组的组标识、目标终端所属用户的标识信息、或者目标终端所属应用的标识信息。
基于上述技术方案，目标终端的标识信息可以有多种不同的形式，增加方案灵活性。
结合第二方面，在第二方面的某些实现方式中，该第一操作包括以下操作中的至少一个：查询终端标识、读、写、灭活、锁、块写、块擦、访问、加密、或解密。
第三方面，提供了一种计费的方法，该方法可以由第一用户面网元执行，或者，也可以由第一用户面网元中的芯片、芯片系统或电路执行，本申请对此不作限定。为了便于描述，下文中以由第一用户面网元执行为例进行说明。
应理解，第一用户面网元可以是第一方面描述的方法中用户面网元或者第三方面中终端管理用户面网元。
该方法包括：接收第一数据，该第一数据包括第一信息或第二信息；发送第一信息或第二信息，
其中，第一信息用于指示第一终端的第一操作执行完成；或，第一信息包括第一终端的执行信息；
其中，第二信息用于指示第一接入网设备的覆盖区域内的终端的第一操作执行完成；或，第二信息包括第一接入网设备的覆盖范围内的终端的执行信息。
基于上述技术方案，第一用户面网元可以转发接收到的第一信息或第二信息，使得终端管理功能网元或会话管理网元能够获取第一信息或第二信息，进而向计费网元发送计费信息。通过该方案，能够用于支持终端管理过程的计费。
其中，发送第一信息或第二信息，包括：向终端管理功能网元发送第一信息或第二信息；或，或，向会话管理网元发送第一信息或第二信息。
结合第三方面，在第三方面的某些实现方式中，该第一用户面网元为终端管理用户面功能网元或用户面网元。
基于上述方案，本申请的方法可以适用于多种不同的架构，扩展性较强。
结合第三方面，在第三方面的某些实现方式中，该第一终端的执行信息包括以下至少一项：第一终端的标识、第一终端执行第一操作的执行结果。
基于上述方案，第一计费信息可以包括第一终端的执行信息，有助于提升计费精度。
结合第三方面，在第三方面的某些实现方式中，该第一接入网设备的覆盖范围内的终端的执行信息包括以下至少一项：
第一接入网设备所获取的终端的标识列表、第一接入网设备所获取的终端的数量、第一接入网设备所获取的终端执行第一操作的执行结果。
基于上述方案，第一计费信息可以包括目标终端中第一接入网设备的覆盖区域内的终端的执行信息，有助于提升计费精度。
结合第三方面，在第三方面的某些实现方式中，该方法还包括：接收策略规则，该策 略规则用于检测第一信息或第二信息。
基于上述方案，终端管理用户面功能网元能够根据策略规则识别第一信息或第二信息，进一步向终端管理功能网元发送第一信息或第二信息，有助于提升准确性。
结合第三方面，在第三方面的某些实现方式中，该第一操作包括以下操作中的至少一个：查询终端标识、读、写、灭活、锁、块写、块擦、访问、加密、或解密。
第四方面，提供了一种计费的方法，该方法由包括终端管理功能网元、会话管理网元和计费网元的系统执行，该方法包括：
终端管理功能网元接收来自应用的应用网元的第七消息，该第七消息用于请求对目标终端执行第一操作；
终端管理功能网元向计费网元发送第八消息，该第八消息用于请求启动对目标终端的第一操作的计费，该第八消息包括第一标识，该第一标识用于标识终端管理功能网元发起的对目标终端执行第一操作的计费；
终端管理功能网元向接入与移动性管理网元发送第九消息，该第九消息用于请求对目标终端执行第一操作，第九消息包括第一标识；
接入与移动性管理网元向会话管理网元发送第四消息，该第四消息用于请求建立第一会话，该第一会话用于传输目标终端中一个或多个终端的执行信息，该第四包括第一标识；
会话管理网元向计费网元发送第五消息，该第五消息用于请求启动对目标终端的第一操作的计费，该第五消息包括第一标识；
计费网元根据该第一标识关联第八消息和第五消息。
基于上述技术方案，终端管理功能网元可以基于第一消息向计费网元发起第八消息，会话管理网元可以基于第四消息向计费网元发起第五，从而计费网元可以根据第一标识管理第八消息和第五消息。通过该方案，能够实现终端管理过程的计费。
结合第四方面，在第四方面的某些实现方式中，该一个或多个终端包括第一终端，该方法还包括：
会话管理网元接收第一信息，该第一信息用于指示第一终端的第一操作执行完成，或，第一信息包括第一终端的执行信息；
会话管理网元发送第二计费信息，该第二计费信息包括第一终端的执行信息；
计费网元根据第二计费信息生成第一终端执行第一操作的话单。
基于上述技术方案，在第一终端的第一操作执行完成后，向计费网元发送计费信息，从而计费网元可以根据计费信息对第一终端执行第一操作的过程计费。通过该方案，能够实现终端粒度的计费，有助于提升计费的灵活性。
结合第四方面，在第四方面的某些实现方式中，该第一终端的执行信息包括以下至少一项：第一终端的标识、第一终端执行第一操作的执行结果。
基于上述方案，第一计费信息可以包括第一终端的执行信息，有助于提升计费精度。
结合第四方面，在第四方面的某些实现方式中，该一个或多个终端包括第一接入网设备覆盖区域内的终端，该方法还包括：
第一接入网设备向会话管理网元发送第二信息，第二信息用于指示目标终端中第一接入网设备的覆盖区域内的终端的第一操作执行完成，或，第二信息包括目标终端中第一接入网设备的覆盖区域内的终端的执行信息；
会话管理网元发送第二计费信息，第二计费信息包括第一接入网设备覆盖区域内的终端的执行信息；
计费网元根据第二计费信息生成目标终端中第一接入网设备覆盖区域内的终端执行第一操作的话单。
基于上述方案，会话管理网元可以在接收到第一接入网设备的覆盖区域内的终端的第一操作执行完成的指示后，或者在接收到第一接入网设备的覆盖区域内的终端的执行信息后，向计费网元发送该第一接入网设备的覆盖区域内的终端的执行信息，从而计费网元可以针对第一接入网设备的覆盖区域内的终端执行第一操作的过程计费。通过该方案，能够实现接入网设备粒度的计费，有助于提升计费的灵活性。
结合第四方面，在第四方面的某些实现方式中，该第一接入网设备覆盖区域内的终端的执行信息包括以下至少一项：第一接入网设备所获取的终端的标识列表、第一接入网设备所获取的终端的数量、第一接入网设备所获取的终端执行第一操作的执行结果。
基于上述方案，第二计费信息可以包括目标终端中第一接入网设备的覆盖区域内的终端的执行信息，有助于提升计费精度。
结合第四方面，在第四方面的某些实现方式中，该方法还包括：会话管理网元向计费网元发送第六消息，该第六消息用于请求关闭对目标终端的第一操作的计费。
基于上述方案，会话管理网元可以在目标终端的第一操作执行完成时请求关闭对目标终端的第一操作的计费，能够避免资源浪费。
结合第四方面，在第四方面的某些实现方式中，该方法还包括：
终端管理功能网元确定目标终端的第一操作执行完成；终端管理功能网元向计费网元发送第十请求消息，该第十请求消息用于请求关闭目标终端的第一操作的计费。
基于上述方案，终端管理功能网元可以在目标终端的第一操作执行完成时请求关闭对目标终端的第一操作的计费，能够避免资源浪费。
结合第四方面，在第四方面的某些实现方式中，该方法还包括：当接收到第七消息时，终端管理功能网元启动目标终端执行第一操作的定时器；在定时器超时的情况下，终端管理功能网元向计费网元发送第十请求消息，该第十请求消息用于请求关闭目标终端的第一操作的计费。
基于上述方案，终端管理功能网元可以利用定时器，在定时器超时时请求关闭对目标终端的第一操作的计费，能够避免资源浪费。
结合第四方面，在第四方面的某些实现方式中，该第七消息和第八消息中包括以下至少一种：第一操作的指示信息、第一操作对应的操作参数、第一指示信息、目标终端的标识信息、应用的标识信息、第一隧道信息，其中，第一指示信息用于指示待执行第一操作的区域，第一隧道信息用于指示应用的服务器接收数据的用户面端口。
基于上述技术方案，该第八消息中可以包括第七消息中的不同信息，提供更多与计费相关的信息，提高计费性能。
结合第四方面，在第四方面的某些实现方式中，该第四消息和第五消息中包括以下至少一种：第一隧道信息、目标终端的标识信息、应用的标识信息。
基于上述技术方案，该第五消息中可以包括第四消息中的不同信息，提供更多与计费相关的信息，提高计费性能。
结合第四方面，在第四方面的某些实现方式中，该目标终端的标识信息，包括以下信息中的至少一项：目标终端中任意一个目标终端的指示信息、目标终端的标识所属的取值区间、目标终端的标识的列表、目标终端所属终端组的组标识、目标终端所属用户的标识信息、或者目标终端所属应用的标识信息。
基于上述技术方案，目标终端的标识信息可以有多种不同的形式，增加方案灵活性。
结合第四方面，在第四方面的某些实现方式中，该第一操作包括以下操作中的至少一个：查询终端标识、读、写、灭活、锁、块写、块擦、访问、加密、或解密。
第五方面，提供一种通信的装置，该通信的装置包括处理器，用于实现上述第一方面描述的方法中终端管理功能网元的功能。
可选地，该通信的装置还可以包括存储器，该存储器与该处理器耦合，该处理器用于实现上述第一方面描述的方法中终端管理功能网元的功能。
在一种可能的实现中，该存储器用于存储程序指令和数据。该存储器与该处理器耦合，该处理器可以调用并执行该存储器中存储的程序指令，用于实现上述第一方面描述的方法中终端管理功能网元的功能。
可选地，该通信的装置还可以包括通信接口，该通信接口用于该通信的装置与其它设备进行通信。当该通信的装置为终端管理功能网元时，该通信接口为收发器、输入/输出接口、或电路等。
在一种可能的设计中，该通信的装置包括：处理器和通信接口，用于实现上述第一方面描述的方法中终端管理功能网元的功能，具体地包括：
该处理器利用该通信接口与外部通信；
该处理器用于运行计算机程序，使得该装置实现上述第一方面描述的任一种方法。
可以理解，该外部可以是处理器以外的对象，或者是该装置以外的对象。
在另一种可能的设计中，该通信的装置为芯片或芯片系统。该通信接口可以是该芯片或芯片系统上的输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等。该处理器也可以体现为处理电路或逻辑电路。
第六方面，提供一种通信的装置，该通信的装置包括处理器，用于实现上述第二方面描述的方法中会话管理网元的功能。
可选地，该通信的装置还可以包括存储器，该存储器与该处理器耦合，该处理器用于实现上述第二方面描述的方法中会话管理网元的功能。
在一种可能的实现中，该存储器用于存储程序指令和数据。该存储器与该处理器耦合，该处理器可以调用并执行该存储器中存储的程序指令，用于实现上述第二方面描述的方法中会话管理网元的功能。
可选地，该通信的装置还可以包括通信接口，该通信接口用于该通信的装置与其它设备进行通信。当该通信的装置为会话管理网元时，该收发器可以是通信接口，或，输入/输出接口。
在一种可能的设计中，该通信的装置包括：处理器和通信接口，用于实现上述第二方面描述的方法中会话管理网元的功能，具体地包括：
该处理器利用该通信接口与外部通信；
该处理器用于运行计算机程序，使得该装置实现上述第二方面描述的任一种方法。
可以理解，该外部可以是处理器以外的对象，或者是该装置以外的对象。
在另一种实现方式中，该通信的装置为芯片或芯片系统时，该通信接口可以是是该芯片或芯片系统上输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等。该处理器也可以体现为处理电路或逻辑电路。
第七方面，提供一种通信的装置，该通信的装置包括处理器，用于实现上述第三方面描述的方法中第一用户面网元的功能。
可选地，该通信的装置还可以包括存储器，该存储器与该处理器耦合，该处理器用于实现上述第三方面描述的方法中第一用户面网元的功能。
在一种可能的实现中，该存储器用于存储程序指令和数据。该存储器与该处理器耦合，该处理器可以调用并执行该存储器中存储的程序指令，用于实现上述第三方面描述的方法中第一用户面网元的功能。
可选地，该通信的装置还可以包括通信接口，该通信接口用于该通信的装置与其它设备进行通信。当该通信的装置为第一用户面网元时，该收发器可以是通信接口，或，输入/输出接口。
在一种可能的设计中，该通信的装置包括：处理器和通信接口，用于实现上述第三方面描述的方法中第一用户面网元的功能，具体地包括：
该处理器利用该通信接口与外部通信；
该处理器用于运行计算机程序，使得该装置实现上述第三方面描述的任一种方法。
可以理解，该外部可以是处理器以外的对象，或者是该装置以外的对象。
在另一种实现方式中，该通信的装置为芯片或芯片系统时，该通信接口可以是是该芯片或芯片系统上输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等。该处理器也可以体现为处理电路或逻辑电路。
第八方面，提供一种计算机可读存储介质，其上存储有计算机程序，该计算机程序被通信装置执行时，使得该通信装置实现第一方面至第三方面的任一可能的实现方式中的方法。
第九方面，提供一种包含指令的计算机程序产品，该指令被计算机执行时使得通信装置实现第一方面至第三方面的任一可能的实现方式中的方法。
第十方面，提供一种芯片，芯片包括处理器与通信接口，处理器通过通信接口读取存储器上存储的指令，执行上述第一方面、或第一方面的上述任意一种实现方式、或第二方面或第二方面的上述任意一种实现方式、或第三方面或第三方面的上述任意一种实现方式提供的方法。
可选地，作为一种实现方式，芯片还包括存储器，存储器中存储有计算机程序或指令，处理器用于执行存储器上存储的计算机程序或指令，当计算机程序或指令被执行时，处理器用于执行上述第一方面、或第一方面的上述任意一种实现方式、或第二方面或第二方面的上述任意一种实现方式、或第三方面或第三方面的上述任意一种实现方式提供的方法。
附图说明
图1是适用于本申请实施例的一种通信系统的示意图。
图2示出了一种无源物联网的网络架构示意图。
图3是本申请实施例提供的一种计费的方法的示意图。
图4是本申请实施例提供的一种计费的方法的又一示意图。
图5是本申请实施例提供的一种计费的方法的又一示意图。
图6是本申请实施例提供的一种计费的方法的又一示意图。
图7是本申请实施例提供的一种计费的方法的又一示意图。
图8中的(a)至(d)是本申请实施例提供的网络架构示意图。
图9是本申请实施例提供的一种计费的方法的又一示意图。
图10是本申请实施例提供的一种计费的方法的又一示意图。
图11中的(a)至(d)是本申请实施例提供的网络架构示意图。
图12是本申请实施例提供的一种计费的方法的又一示意图。
图13是本申请实施例提供的一种计费的方法的又一示意图。
图14中的(a)至(d)是本申请实施例提供的网络架构示意图。
图15是本申请提供的通信装置的示意性框图。
图16是本申请提供的通信装置的又一示意图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
本申请提供的技术方案可以应用于各种通信系统，例如：第五代(5th generation，5G)或新无线(new radio，NR)系统、长期演进(long term evolution，LTE)系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)系统等。本申请提供的技术方案还可以应用于未来的通信系统，如第六代移动通信系统。
本申请提供的技术方案还可以应用于设备到设备(device to device，D2D)通信，车到万物(vehicle-to-everything，V2X)通信，机器到机器(machine to machine，M2M)通信，机器类型通信(machine type communication，MTC)，以及物联网(Internet of things，IoT)通信系统或者其他通信系统。
作为示例，图1示出了适用于本申请实施例的一种网络架构。
如图1所示，该网络架构100以5G系统(the 5th generation system，5GS)为例。该网络架构可以包括但不限于：用户设备(user equipment，UE)101、(无线)接入网设备((radio)access network，RAN)102、用户面功能(user plane function，UPF)网元103、数据网络(data network，DN)网元104、接入和移动管理功能(access and mobility management function，AMF)网元105、会话管理功能(session management function，SMF)网元106、鉴权服务器功能(authentication server function，AUSF)网元107、服务通信代理(service communication proxy，SCP)网元108、网络数据分析功能(network data analytics function，NWDAF)网元109、网络开放功能(network exposure function，NEF)网元110、计费功能(charging function，CHF)网元111、策略控制功能模块(policy control function，PCF)网元112、统一数据管理(unified data management，UDM)网元113、应用功能(application function，AF)网元114等。
其中，DN可以是互联网；UPF、AUSF、AMF、SMF、SCP、NWDAF、NEF、CHF、PCF、UDM、AF属于核心网中的网元，由于图1以5G系统为例，那么该核心网可以称 为5G核心网(5G core network，5GC或5GCN)。
下面对图1中示出的各网元做简单介绍。
1、用户设备(user equipment，UE)101：可以称终端设备、终端、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、无线通信设备、用户代理或用户装置。
UE还可以是蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，5G网络中的终端设备或者未来演进的公用陆地移动通信网络(public land mobile network，PLMN)中或者非陆地网络(non-terrestrial networks，NTN)的终端设备等，还可以是端设备，逻辑实体，智能设备，如手机，智能终端等终端设备，或者服务器，网关，基站，控制器等通信设备，或者物联网设备，如标签，无源标签，有源标签，半无源标签、半有源标签、传感器，电表，水表等物联网(internet of things，IoT)设备。还可以是具有通信功能的无人机(unmanned aerial vehicle或uncrewed aerial vehicle，UAV)。当终端为无源、半有源或者半无源的终端或者标签时，可以通过获取能量以接收或者发送数据。获取能量的方式可以通过射频、无线电、太阳能、光能、风能、水能、热能、动能等方式获取。本申请对于无源、半有源、或者半无源的终端获取能量的方式不做限定。可以理解的，当终端为无源的终端时，该终端自身不配备或者不依赖电池等电源设备，而是从环境中获取能量，用于数据的感知、传输和分布式计算等功能。当终端为半有源的终端时，该终端可以内置电池，但该电池的作用是用于内部电路供电，并不用于主动发射信号。当终端为半无源的终端时，该终端可以内置电容；该电容可以存储该终端获取的能量；例如该终端可以通过获取太阳能等方式获取能量并存储于电容中。
需要说明的是，本申请中涉及到的标签可以是标签形态，或者，也可以是任意终端形态。
需要指出的是，终端设备与接入网设备之间可以采用某种空口技术(如NR或LTE技术等)相互通信。终端设备与终端设备之间也可以采用某种空口技术(如NR或LTE技术等)相互通信。
本申请实施例中，用于实现终端设备的功能的装置可以是终端设备，也可以是能够支持终端设备实现该功能的装置，例如芯片系统或芯片，该装置可以被安装在终端设备中。本申请实施例中，芯片系统可以由芯片构成，也可以包括芯片和其他分立器件。
2、(无线)接入网((radio)access network，(R)AN)设备102：可以为特定区域的授权用户提供接入通信网络的功能，具体可以包括第三代合作伙伴计划(3rd generation partnership project，3GPP)网络中无线网络设备也可以包括非3GPP(non-3GPP)网络中的接入点。下文为方便描述采用AN设备表示。
AN设备可以为采用不同的无线接入技术。目前的无线接入技术有两种类型：3GPP接入技术(例如，第三代(3rd generation，3G)、第四代(4th generation，4G)或5G系统中采用的无线接入技术)和非3GPP(non-3GPP)接入技术。3GPP接入技术是指符合3GPP标准规范的接入技术，例如，5G系统中的接入网设备称为下一代基站节点(next generation Node Base station，gNB)或者下一代无线接入网(next generationradioaccess  network，NG-RAN)设备。非3GPP接入技术可以包括以无线保真(wireless fidelity，WiFi)中的接入点(access point，AP)为代表的空口技术、全球互联微波接入(worldwide interoperability for microwave access，WiMAX)、码分多址(code division multiple access，CDMA)等。AN设备可以允许终端设备和3GPP核心网之间采用非3GPP技术互连互通。
AN设备能够负责空口侧的无线资源管理、服务质量(quality of service，QoS)管理、数据压缩和加密等功能。AN设备为终端设备提供接入服务，进而完成控制信号和用户数据在终端设备和核心网之间的转发。
AN设备例如可以包括但不限于：宏基站、微基站(也称为小站)、无线网络控制器(radio network controller，RNC)、节点B(Node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(例如，home evolved NodeB，或home Node B，HNB)、基带单元(baseband unit，BBU)，WiFi系统中的AP、无线中继节点、无线回传节点、传输点(transmission point，TP)或者发送接收点(transmission and reception point，TRP)等，还可以为5G(如，NR)系统中的gNB或传输点(TRP或TP)，5G系统中的基站的一个或一组(包括多个天线面板)天线面板，或者，还可以为构成gNB或传输点的网络节点，如分布式单元(distributed unit，DU)，或者下一代通信6G系统中的基站等。本申请实施例对AN设备所采用的具体技术和具体设备形态不做限定。
3、用户面网元：用于分组路由和转发以及用户面数据的服务质量(quality of service，QoS)处理等。
在5G通信系统中，该用户面网元可以是用户面功能(user plane function，UPF)网元103。在未来通信系统中，用户面网元仍可以是UPF网元，或者，还可以有其它的名称，本申请不做限定。
4、数据网络：用于提供传输数据的网络。
在5G通信系统中，该数据网络可以是数据网络(data network，DN)104。在未来通信系统中，数据网络仍可以是DN，或者，还可以有其它的名称，本申请不做限定。
5、接入与移动性管理网元：用于路由和转发用户面数据，或用户面数据的服务质量(quality of service，QoS)处理等。
在5G通信系统中，该接入与移动性管理网元可以是接入与移动性管理功能(access and mobility management function，AMF)网元105。在未来通信系统中，接入与移动性管理网元仍可以是AMF网元，或者，还可以有其它的名称，本申请不做限定。
6、会话管理网元：可用于会话管理、终端设备的网络互连协议(internet protocol，IP)地址分配和管理、选择可管理用户平面功能、策略控制和收费功能接口的终结点以及下行数据通知等。
在5G通信系统中，该会话管理网元可以是会话管理功能(session management function，SMF)网元106。在未来通信系统中，会话管理网元仍可以是SMF网元，或者，还可以有其它的名称，本申请不做限定。
7、鉴权服务器网元：主要负责提供鉴权服务。
在5G通信系统中，该鉴权服务器网元可以是鉴权服务器功能网元(authentication server function，AUSF)网元107。在未来通信系统中，鉴权服务器网元仍可以是AUSF 网元，或者，还可以有其它的名称，本申请不做限定。
8、服务通信代理网元：主要负责网元与对应网元服务之间的间接通信。
在5G通信系统中，该服务通信代理网元可以是服务通信代理(service communication proxy，SCP)网元108。在未来通信系统中，会话管理网元仍可以是SCP网元，或者，还可以有其它的名称，本申请不做限定。
9、网络数据分析网元：负责网络数据采集、统计、分析与决策反馈，提供基于大数据和人工智能等技术的网络数据采集和分析功能。
在5G通信系统中，该网络数据分析网元可以是网络数据分析功能(network data analytics function，NWDAF)网元109。在未来通信系统中，会话管理网元仍可以是NWDAF网元，或者，还可以有其它的名称，本申请不做限定。
10、网络开放网元：主要用于支持能力和事件的开放。
在5G通信系统中，该网络开放网元可以是网络开放功能(network exposure function，NEF)网元110。在未来通信系统中，网络开放网元仍可以是NEF网元，或者，还可以有其它的名称，本申请不做限定。
11、计费网元：作为在线计费和/或离线计费的控制节点，对用户设备的各种业务执行在线计费和/或离线计费的费率处理。
在5G通信系统中，该计费网元可以是计费功能(charging function，CHF)网元111，具体地，CHF网元可以融合计费功能(converged charging function)网元或离线计费功能(offline only charging function)网元。在未来通信系统中，计费网元仍然可以是CHF网元，或者，还可以有其它的名称，本申请不做限定。
12、策略控制网元：用于指导网络行为的统一策略框架，为网络网元(例如AMF，SMF网元等)或终端设备提供策略规则信息等。
在5G通信系统中，该策略控制网元可以是策略控制功能(policy control function，PCF)网112元。在未来通信系统中，策略控制网元仍可以是PCF网元，或者，还可以有其它的名称，本申请不做限定。
13、数据管理网元：用于处理终端设备标识，接入鉴权，注册以及移动性管理等。
在5G通信系统中，该数据管理网元可以是统一数据管理(unified data management，UDM)网元113。在未来通信系统中，统一数据管理仍可以是UDM网元，或者，还可以有其它的名称，本申请不做限定。
14、应用网元：用于进行应用影响的数据路由，接入网络开放功能网元，与策略框架交互进行策略控制等。
在5G通信系统中，该应用网元可以是应用功能(application function，AF)网元。在未来通信系统中，应用网元仍可以是AF网元114，或者，还可以有其它的名称，本申请不做限定。
可以理解的是，上述网元或者功能既可以是硬件设备中的网络元件，也可以是在专用硬件上运行软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能，本申请对于上述网元的具体形态不作限定。还应理解，图1中所示的AMF、SMF、UPF、PCF、NEF等可以理解为用于实现不同功能的网元，例如可以按需组合成网络切片。这些网元可以各自独立的设备，也可以集成于同一设备中实现不同的功能。
为方便说明，本申请后续，以接入与移动性管理网元为AMF网元，会话管理网元为SMF网元，策略控制网元为AF网元为例进行说明。进一步地，将AMF网元简称为AMF，SMF网元简称为SMF，AF网元简称为AF。即本申请后续所描述的AMF均可替换为接入与移动性管理网元，SMF均可替换为会话管理网元，AF均可替换为应用网元。
在图1所示的网络架构中，各网元之间可以接口通信。例如，N1为UE101和AMF105之间的接口，N2为(R)AN102和AMF105的接口，用于(non-access stratum，NAS)消息的发送等；N3为RAN102和UPF103之间的接口，用于传输用户面的数据等；N4为SMF106和UPF103之间的接口，用于传输例如N3连接的隧道标识信息，数据缓存指示信息，以及下行数据通知消息等信息；N6接口为UPF103和DN104之间的接口，用于传输用户面的数据等；N9为UPF之间的接口。Namf为AMF105展现的基于服务的接口，Nsmf为SMF106展现的基于服务的接口，Nausf为AUSF107展现的基于服务的接口，Nnwdaf为NWDAF109展现的基于服务的接口，Nnef为NEF110展现的基于服务的接口，Nchf为CHF111展现的基于服务的接口，Npcf为PCF112展现的基于服务的接口，Nudm为UDM113展现的基于服务的接口，Naf为AF114展现的基于服务的接口。
需要说明的是，图1中所涉及的各个网元以及网元之间的通信接口的名称是以目前协议中规定的为例进行简单说明的，但并不限定本申请实施例只能够应用于目前已知的通信系统。因此，以目前协议为例描述时出现的标准名称，都是功能性描述，本申请对于网元、接口或信令等的具体名称并不限定，仅表示网元、接口或者信令的功能，可以对应的扩展到其它系统，比如2G、3G、4G或未来通信系统中。
应理解，图1所示的网络架构仅是示例性说明，适用本申请实施例的网络架构并不局限于此，任何能够实现上述各个网元的功能的网络架构都适用于本申请实施例。
在物联网技术中，无源物联网(passive Internet of things，P-IoT)标签(tag)(例如，射频识别(radio frequency identification，RFID)，又称为无源标签)具有大规模部署的应用前景，预测未来将覆盖千亿级别的设备数目。所谓无源物联网，即有些网络节点可以是无源的。这些节点自身不配备或不主要依赖电池等电源设备，而是从环境中获取能量，用于数据的感知、传输和分布式计算等功能。无源物联网的应用场景可以是：
(1)仓库/运输/物资：给货品嵌入或贴上无源标签，在存储和物流过程中，货品相关信息被阅读器自动采集，管理人员就可以在系统中迅速查询货品信息，降低丢弃或者被盗的风险，可以提高货品交接速度，提高准确率，并且防止窜货和防伪；
(2)固定资产管理：像图书馆、艺术馆及博物馆等资产庞大或者物品贵重的一些场所，对图书或者贵重物品贴上无源标签，当书籍或者贵重物品的存放信息有异常变动，就会第一时间在系统中提醒管理员，从而管理员能够及时处理相关情况。
图2示出了一种无源物联网的网络架构示意图。如图2所示，该网络架构包括无源标签、读卡器(reader)以及操作请求方。
其中，读卡器也可以称为阅读器或者读写器。读卡器通过射频信号或者无线信号与无源标签交互。操作请求方可以是应用服务器(server)或者应用功能(application function，AF)。操作请求方可以理解为发送操作指令的设备。操作请求方对应某类用户，该类用户可以包括企业、租户、第三方或者公司，不予限制。其中，操作请求方对应某类用户可以理解为该操作请求方属于该类用户，由该类用户管理。
在无源物联网架构中，读卡器可以根据操作请求方的指示，对无源标签进行管理，所谓标签管理也可以称为标签盘点，包括但不限于以下至少一种：查询(query)标签标识、对标签进行读(read)操作、写(write)操作、访问(access)操作或灭活(kill)等操作。需要说明的是，上述的“标签”也可以理解为终端。
其中，读操作，即对标签进行数据读取。写操作，即将数据写入标签的存储区中。失效操作，即使标签失效。失效操作完成后，该标签会失效，而不得再被盘点或被执行其他操作，例如，与该失效标签进行消息交互。
目前，提出一种新型无源物联网技术，将读卡器集成于接入网设备，无源物联网标签作为一种终端设备，具有标签管理需求的企业利用部署的第三代合作伙伴计划(3rd generation partnership project，3GPP)网络完成无源物联网标签的盘点。该技术能够实现通信距离的增加以及标签的统一管理，为无源物联网标签的大规模部署提供技术支持。
在这种新型无源物联网技术中，运营商需要向具有标签管理需求的企业收取费用，因此，如何实现标签盘点过程的计费是一个值得关心的问题。
有鉴于此，本申请提出一种计费的方法和通信装置，能够实现标签盘点过程的计费。
需要说明的是，本申请的通信方法以无源物联网为例阐述。本申请中的方法不限于无源物联网技术，还可以适用于其他技术，比如适用于半有源物联网技术、半无源物联网技术、有源物联网技术等等。对应地，网络架构中的标签可以为半有源的标签、半无源的标签或者有源的标签。
图3是本申请实施例提供的一种计费的方法的示意图。如图3所示，该方法300包括以下步骤。
S310，应用的应用网元AF向终端管理功能网元发送第一消息，相应地，终端管理功能网元接收第一消息。
本申请实施例中涉及的终端管理功能网元可以是独立设立在5G核心网(5G core，5GC)中的一个新增的功能网元，还可以是与5GC中目前已有的网元合设的网元(如，与NEF或AMF合设)，其中，终端管理功能网元与某个已有的网元合设可以理解为对某个已有网元的功能增强，使得该已有的网元具有终端管理的功能。
还应理解，在本申请实施例中，终端管理功能网元也可以称为终端管理控制面功能网元，用于处理和收发终端管理过程中的信令。
其中，该第一消息用于请求对目标终端执行第一操作。
具体地，第一消息可以理解为是用于请求终端管理功能网元盘点目标终端的请求消息，可以称为：盘点请求消息。在本申请中，盘点是指对目标终端执行第一操作。
示例性地，第一操作包括以下至少一种：查询终端标识、读、写、灭活、锁、块写、块擦、访问、加密、解密等。
第一消息可以包括以下至少一种：第一操作的指示信息、第一操作对应的操作参数、第一指示信息、目标终端的标识信息、应用的标识信息、应用网元的地址信息、第一隧道信息。
其中，第一操作的指示信息用于指示待执行的第一操作，包括但不限于：
第一操作的标识、第一操作的标识所属的取值区间、第一操作的标识的列表、第一操作所属操作组的组标识等。
例如，待执行的操作包括一个操作，该操作的标识为操作#1，上述的第一操作的指示信息可以为第一操作的标识，如，操作#1。
还例如，待执行的操作包括三个操作，该三个操作的标识分别为操作#1、操作#2和操作#3，上述的第一操作的指示信息可以是操作的标识列表，如，操作#1、操作#2和操作3。
又例如，待执行的操作包括三个操作，该三个操作属于一个操作组，该操作组的组标识为操作组#1，上述的第一操作的指示信息可以是操作所属操作组的组标识，如，操作组#1。
应理解，上述的第一操作可以包括一个或者多个操作，在第一操作包括多个操作(如，操作#1和操作#2)的情况下，上述的第一操作的指示信息可以包括分别指示该多个操作的指示信息(如，指示操作#1的指示信息和指示操作#2的指示信息)。
需要说明的是，上述只是举例说明待执行的操作的指示信息可能的形式，对本申请的保护范围不构成任何的限定，其他能够指示待盘点的操作的指示信息也在本申请的保护范围之内，这里不再一一举例说明。
示例性地，在某些情况下，第一消息中可以不包括第一操作的指示信息，例如，AF没有执行操作的命令；还例如，第一操作默认为查询终端标识，无需通过第一操作的指示信息进行额外的指示。
其中，在第一操作的指示信息指示第一操作为除查询终端标识之外的操作的情况下，第一消息中还包括第一操作对应的操作参数。
例如，在第一操作的指示信息用于指示执行read的情况下，第一操作的指示信息可以称为read命令。具体地，对于read命令，操作参数包括读取的存储区，读取存储区的起始字地址以及字数目等。
还例如，在第一操作的指示信息用于指示执行write的情况下，第一操作的指示信息可以称为write命令。具体地，对于write命令，操作参数包括写入的存储区，读取存储区的起始字以及写入的数据。
可选地，对于写入信息，可以针对所有目标终端，携带相同的写入信息，也可以针对不同的目终端分别携带不同的写入信息。
需要说明的是，本申请实施例中对于第一消息中可能包括的第一操作的指示信息和操作参数不做限定，可以参考相关技术中读卡器接收到的操作的指示信息和操作参数，还可以是未来技术发展之后读卡器接收到的操作的指示信息和操作参数，这里不再赘述。
其中，第一指示信息用于指示待执行第一操作的区域。
示例性地，第一指示信息所指示的待执行第一操作的区域包括待盘点的目标终端所位于的位置，第一指示信息包括但不限于地理位置、市政位置、3GPP的位置信息，例如，3GPP的位置信息可以是跟踪区(trace area，TA)列表(list)，小区列表(cell list)等。
例如，待盘点的目标终端包括三个终端，该三个终端的分别位于cell#1、cell#2和cell#3，上述第一指示信息可以是终端的3GPP的位置信息，如，cell#1、cell#2和cell#3。
需要说明的是，本申请实施例中对于用于指示第一指示信息的具体形式不做限定，能够指示待盘点的目标终端所位于的位置即可。
其中，目标终端的标识信息用于指示待盘点的目标终端。目标终端的标识信息包括但 不限于：目标终端中任意一个目标终端的指示信息、目标终端的标识所属的取值区间、目标终端的标识的列表、目标终端所属终端组的组标识、目标终端所属用户的标识信息、目标终端的类型或者目标终端所属应用的标识信息等。
例如，待盘点的目标终端包括三个终端，该三个终端的标识分别为终端#1、终端#2和终端#3，上述的目标终端的标识信息可以是终端的标识列表，如，终端#1、终端#2和终端3。
又例如，待盘点的目标终端包括三个终端，该三个终端的标识分别为100、101和102，上述的目标终端的标识信息可以是终端标识的区间，如，100～102。
又例如，待盘点的目标终端包括三个终端，该三个终端的标识分别为终端#1、终端#2和终端#3。目标终端中任意一个目标终端的指示信息是指盘点所有这三个终端。
又例如，待盘点的终端包括三个终端，该三个终端属于一个终端组，该终端组的组标识为终端组#1，上述的目标终端的标识信息可以是目标终端所属终端组的组标识，如，终端组#1。
又例如，待盘点的终端包括三个终端，该三个终端属于一个用户，该用户的用户的标识为用户#1，上述的目标终端的标识信息可以是目标终端所属用户的标识，如，用户#1。
又例如，待盘点的终端包括三个终端，该三个终端都属于无源终端或都属于半无源终端。上述的目标终端的标识信息可以是无源终端或者半无源终端。
又例如，待盘点的终端包括三个终端，该三个终端属于一个应用，该应用的应用标识为应用#1，上述的目标终端的标识信息可以是目标终端所属应用的标识，如，应用#1。
需要说明的是，上述只是举例说明待盘点的终端的标识信息可能的形式，对本申请的保护范围不构成任何的限定，其他能够标识出待盘点的终端的标识信息也在本申请的保护范围之内，这里不再一一举例说明。
示例性地，在某些情况下，第一消息中可以不包括目标终端的标识信息，例如，第一消息中包括第一指示信息，通过第一指示信息指示对某个区域中的终端进行盘点；又如，第一消息仅触发盘点流程，具体盘点的目标终端可以是终端管理功能网元管理的全部的终端。类似地，第一消息也可以包括目标终端的标识信息，而不包括第一指示信息。
其中，应用的标识信息用于标识发起盘点请求的应用。
例如，发起盘点请求的AF的标识为AF#1，上述的应用标识可以是AF#1。
其中，应用网元的地址信息也可以称为通知地址，用于表示AF接收终端信息以及命令执行结果的地址。例如，AF的地址。
其中，第一隧道信息指示应用的服务器接收数据的用户面端口。例如，该第一隧道信息可以指示应用服务器的地址。
可选地，第一消息还可以包括关联标识，关联标识用于关联第一消息和针对第一消息的响应消息。
示例性地，在某些情况下，第一消息中可以不包括第一隧道信息，例如，第一消息包括应用网元的地址信息，该应用网元的地址信息表示第一操作的执行结果通过控制面信令发送至该应用网元的地址。
类似地，在某些情况下，第一消息中可以不包括应用网元的地址信息，例如，第一消息包括第一隧道信息，该第一隧道信息表示第一操作的执行结果通过用户面的数据发送至 该应用的服务器。
S320，终端管理功能网元向计费网元发送第二消息，相应地，计费网元接收第二消息。
计费网元可以是融合计费功能网元，也可以离线计费功能网元，本申请不予限制。
其中，该第二消息用于请求启动对该目标终端的第一操作的计费。即第二用于启动对S310中发起的盘点请求的计费。
具体地，第二消息可以是融合计费创建请求(Nchf_ConvergedCharging_Create Request)消息，请求通用资源标识(universal resource identifier，URI)为{apiRoot}/nchf-convergedcharging/{apiVersion}/chargingdata。计费网元根据第二消息创建对应的个人计费数据资源(Individual Charging Data Resource)，并生成对应的URI#1，例如，URI#1为{apiRoot}/nchf-convergedcharging/{apiVersion}/chargingdata/{ChargingDataRef1}。计费网元将URI#1返回给终端管理功能网元。
第二消息还可以是离线计费创建请求(Nchf_OfflineOnlyCharging_CreateRequest)消息，请求URI为{apiRoot}/nchf-offlineonlycharging/{apiVersion}/offlinechargingdata。计费网元根据第二消息创建对应的个人离线计费数据(Individual Offline Only Charging Data)，并生成对应的资源标识URI#2，例如，URI#2为{apiRoot}/nchf-offlineonlycharging/{apiVersion}/offlinechargingdata/{OfflineChargingDataRef2}。计费网元将URI#2返回给终端管理功能网元。
可选地，第二消息可以包括开始(start)指示，计费网元根据start指示启动计费。
具体来说，第二消息中包括start指示，计费网元可以根据start指示启动计费。或者，第二消息中不包括start指示，第二消息可以表示start指示，计费网元根据第二消息启动计费。
可选地，第二消息可以包括第一操作的指示信息、第一操作对应的操作参数、第一指示信息、目标终端的标识信息、应用的标识信息、应用网元的地址信息、第一隧道信息中至少一个。
也就是，终端管理功能网元可以将第一消息中的信息发送至计费网元，计费网元根据这些信息对S310中发起的盘点请求的进行计费。
S330，终端管理功能网元向计费网元发送第一计费信息，相应地，计费网元接收第一计费信息。
具体地，若第二消息为融合计费创建请求消息，则终端管理功能网元可以向计费网元发送融合计费更新请求(Nchf_ConvergedCharging_Update Request)消息，请求URI为{apiRoot}/nchf-convergedcharging/{apiVersion}/chargingdata/{ChargingDataRef1}/update。融合计费更新请求消息中包括第一计费信息。计费网元根据请求URI更新之前创建的Individual Charging Data Resource，保存第一计费信息，并根据第一计费信息生成计费数据记录(charging data record，CDR)，发送给记账系统。
若第二消息为离线计费创建请求消息，则终端管理功能网元可以向计费网元发送离线计费更新请求(Nchf_OfflineOnlyCharging_Update Request)消息，请求URI为{apiRoot}/nchf-offlineonlycharging/{apiVersion}/offlinechargingdata/{OfflineChargingDataRe f2}/update。离线计费更新请求消息中包括第一计费信息。计费网元根据请求URI更新之前创建的Individual Offline Only Charging Data，保存第一计费信息，并根据第一计费信息 生成CDR，发送给记账系统。
可选地，第一计费信息中包括临时(interim)指示或更新(update)指示，该interim指示或update指示用于指示计费网元更新计费信息。
具体来说，第一计费信息中包括interim指示或update指示，计费网元可以根据interim指示或update指示更新CDR。或者，第一计费信息中不包括interim指示或update指示，第一计费信息即为interim指示或update指示，计费网元根据第一计费信息更新CDR。
其中，该第一计费信息包括该一个或多个终端的执行信息。一个或多个终端的执行信息也就是对一个或多个终端执行第一操作后所获得的信息。
具体地，该一个或多个终端的执行信息包括该一个或多个终端执行第一操作的执行结果、一个或多个终端的标识信息、一个或多个终端的数量中的至少一项。
作为一个示例，在第一操作的指示信息指示第一操作为查询终端标识的情况下，一个或多个终端的执行信息包括一个或多个终端的标识信息和/或一个或多个终端的数量。
作为又一个示例，在第一操作的指示信息指示第一操作为除查询终端标识之外的操作的情况下，一个或多个终端的执行信息包括该一个或多个终端执行第一操作的执行结果。例如，在第一操作的指示信息指示第一操作为read的情况下，执行结果包括读取的数据。又如，在第一操作的指示信息指示第一操作为write的情况下，执行结果包括写入成功或者失败的指示。
其中，除查询终端标识之外的任一第一操作，也可以称为执行命令。执行除查询终端标识之外的任一第一操作所获得的结果也可以称为执行结果。
在上述实施例一种实现方式中，该一个或多个终端包括第一终端，该第一终端为待盘点的目标终端中的随机的一个终端，或者说，第一终端为待盘点的目标终端中的任一个终端，S330中“一个或多个终端”指的是该第一终端。
在该实现方式中，一个或多个终端的执行信息包括第一终端的执行信息，其中，第一终端的执行信息包括以下至少一项：第一终端的标识、数量1、第一终端执行第一操作的执行结果。
在上述实施例的又一种实现方式中，该一个或多个终端包括第一接入网设备的覆盖区域内的终端，或者说，目标终端中第一接入网设备覆盖范围内的终端组成终端组，S330中“一个或多个终端”指的是该终端组的终端。
在该实现方式中，一个或多个终端的执行信息包括目标终端中第一接入网设备的覆盖区域内的终端的执行信息，其中，目标终端中第一接入网设备的覆盖区域内的终端的执行信息包括以下至少一项：第一接入网设备所获取的终端的标识列表、第一接入网设备所获取的终端的数量、第一接入网设备所获取的终端执行第一操作的执行结果。
其中，该第一计费信息用于对一个或多个终端执行第一操作的过程计费。
具体地，在上述实施例的一种实现方式中，计费网元可以根据第一计费信息生成第一终端执行第一操作的过程的话单。
其中，话单也可以理解为CDR。
作为示例，在一个或多个终端的执行信息包括第一终端的标识和/或数量1的情况下，计费网元生成的CDR包括以下一项或多项：应用的标识信息、目标终端的标识信息、第一操作的指示信息、第一操作对应的操作参数、第一隧道信息、应用网元的地址信息以及 第一终端的标识。或者，CDR包括以下至少一项：应用的标识信息、目标终端的标识信息、第一操作的指示信息、第一操作对应的操作参数、应用网元的地址信息、第一隧道信息、数量1。
作为又一示例，在一个或多个终端的执行信息包括第一终端执行第一操作的执行结果的情况下，计费网元生成的CDR包括应用的标识信息、目标终端的标识信息、第一操作的指示信息、第一操作对应的操作参数、应用网元的地址信息、第一隧道信息、第一终端的标识以及第一终端执行第一操作的执行结果。
具体地，在上述实施例的另一种实现方式中，计费网元可以根据第一计费信息生成目标终端中第一接入网设备的覆盖区域内的终端执行第一操作的过程的CDR。
作为示例，在一个或多个终端的执行信息包括第一接入网设备所获取的终端的标识列表或数量的情况下，计费网元生成的CDR包括以下至少一项：应用的标识信息、目标终端的标识信息、第一操作的指示信息、第一操作对应的操作参数、应用网元的地址信息、第一隧道信息、获取的终端的标识列表。或者CDR包括以下至少一项：应用的标识信息、目标终端的标识信息、第一操作的指示信息、第一操作对应的操作参数、应用网元的地址信息、第一隧道信息、所获取的终端的数量。
作为又一示例，在一个或多个终端的执行信息包括第一接入网设备所获取的终端执行第一操作的执行结果的情况下，计费网元生成的CDR包括以下至少一项：应用的标识信息、目标终端的标识信息、第一操作的指示信息、第一操作对应的操作参数、应用网元的地址信息、第一隧道信息、所获取终端的标识以及对应的执行结果组合的列表。
计费网元可以根据每一个接收到第一计费信息生成一个CDR，或者根据网络策略等根据多个第一计费信息生成一个CDR。
根据上述实施例的方案，终端管理功能网元可以基于第一消息向计费网元发起计费请求，并在一个或多个终端的第一操作执行完成后，向计费网元发送计费信息，从而计费网元可以根据计费请求和计费信息对一个或多个终端执行第一操作的过程计费。通过该方案，能够实现终端管理过程的计费。
可选地，在上述实施例的一种实现方式中，在S330之前，方法300还包括：S341，终端管理功能网元获取第一信息，其中，该第一信息用于指示第一终端的第一操作执行完成；或，第一信息包括第一终端的执行信息。
也就是，终端管理功能网元在获取到第一信息后，向计费网元发送第一计费信息，该第一计费信息包括第一终端的执行信息。
其中，终端管理功能网元获取第一信息，包括：
终端管理功能网元接收来自应用网元的第一信息；或，终端管理功能网元接收来自第一接入网设备的第一信息；或，终端管理功能网元确定第一信息。
也就是，该第一信息可以来自于第一接入网设备、应用网元或终端管理功能网元，其中，第一接入网设备用于对第一终端执行第一操作。
作为一个示例，该第一信息用于指示第一终端的第一操作执行完成，该第一信息来自于应用网元。
具体地，在应用网元对第一终端发起执行命令的情况下，应用网元在接收到第一终端执行第一操作的执行结果后，根据执行结果确定第一终端的第一操作执行完毕，从而向终 端管理功能网元发送第一信息。
其中，应用网元向终端管理功能网元发送第一信息，包括：应用网元通过控制面向第一接入网设备发送第一信息，该第一信息经过终端管理功能网元，或者，应用网元通过用户面向第一接入网设备发送第一信息，该第一信息经过终端管理用户面功能网元，终端管理用户面功能网元向终端管理控制面功能网元发送第一信息。
作为又一示例，该第一信息包括第一终端的执行信息，该第一信息来自于第一接入网设备。
具体地，在第一接入网设备对第一终端发起执行命令的情况下，第一接入网设备在接收到第一终端执行第一操作的执行结果后，根据执行结果确定第一终端的第一操作执行完毕，从而向终端管理功能网元发送第一信息。
其中，第一接入网设备向终端管理功能网元发送第一信息，包括：第一接入网设备通过控制面向应用网元发送第一信息，该第一信息经过终端管理功能网元，或者，第一接入网设备通过用户面向应用的服务器发送第一信息，该第一信息经过终端管理用户面功能网元，终端管理用户面功能网元向终端管理控制面功能网元发送第一信息。
作为再一示例，该第一信息用于指示第一终端的第一操作执行完成，该第一信息来自于终端管理功能网元。
具体地，在终端管理功能网元对第一终端发起执行命令的情况下，终端管理功能网元在接收到第一终端执行第一操作的执行结果后，根据执行结果确定第一终端的第一操作执行完毕，即获得第一信息。
应理解，第一信息的来源和第一信息的内容没有必然联系，上述几种示例仅为举例说明，本申请不予限制。
可选地，作为上述实施例的又一种实现方式，终端管理功能网元可以在接收到至少两个第一终端对应的第一信息后，向计费控制网元发送第一计费信息，此时第一计费信息中包括该至少两个第一终端的标识列表或是该至少两个第一终端的数量。
换言之，在该实现方式中，S330中“一个或多个终端”指的是该至少两个第一终端。
可选地，在上述实施例的一种实现方式中，在S330之前，方法300还包括：S342，终端管理功能网元接收第二信息，该第二信息用于指示目标终端中第一接入网设备的覆盖区域内的终端的第一操作执行完成；或，第二信息包括目标终端中第一接入网设备的覆盖范围内的终端的执行信息。
也就是，终端管理功能网元在接收到第二信息后，向计费网元发送第一计费信息，该第一计费信息包括第一接入网设备的覆盖区域内的终端的执行信息。
其中，该第二信息来自于第一接入网设备。
应理解，第一接入网设备可以根据盘点过程确定其覆盖范围内的目标终端盘点完成，从而向终端管理功能网元发送第二信息。
作为一个示例，第一接入网设备确定其覆盖范围内的目标终端盘点完成后，可以向终端管理功能网元发送专用的指示信息，指示目标终端中第一接入网设备的覆盖区域内的终端的第一操作执行完成。
作为又一个示例，第一接入网设备确定其覆盖范围内的目标终端盘点完成后，可以向终端管理功能网元发送其覆盖区域内的终端的执行信息。
可选地，作为上述实施例的又一种实现方式，终端管理功能网元可以在接收到来自至少两个第一接入网设备对应的第二信息后，向计费控制网元发送第一计费信息，此时第一计费信息中包括该至少两个第一接入网设备覆盖区域内的目标终端的列表或是该至少两个第一接入网设备覆盖区域内的目标终端的列表或是该至少两个第一接入网设备覆盖区域内的目标终端的数量。
换言之，在该实现方式中，S330中“一个或多个终端”指的是该至少两个第一接入网设备的覆盖区域内的终端。
可选地，在一种实现方式中，方法300还包括：S351，终端管理功能网元确定目标终端的第一操作执行完成。
具体地，终端管理功能网元在接收到第一消息后，根据第一消息确定一个或多个接入与移动性管理网元，以及每个接入与移动性管理网元对应的一个或多个接入网设备。终端管理功能网元向一个或多个接入与移动性管理网元发送第一盘点请求，该第一盘点请求用于请求对目标终端执行第一操作。每个接入与移动性管理网元向其管理区域的一个或多个接入网设备发送第二盘点请求，该第二盘点请求用于请求对目标终端执行第一操作。每个接入网设备根据第三盘点请求对其覆盖区域内的终端执行第一操作。
每个接入网设备确定其覆盖区域内的终端的第一操作执行完成后，经过接入与移动性管理网元向终端管理功能网元发送第二信息。终端管理功能网元根据其确定的一个或多个接入网设备的第二信息确定目标终端的第一操作执行完成。
作为示例，接入网设备对其覆盖区域内的终端执行第一操作，也就是，接入网设备根据第三盘点请求触发盘点流程，具体包括：
接入网设备向覆盖区域内的所有终端发送射频信息，以便给该接入网设备的覆盖区域内的所有终端提供激励信号，从而使终端能够向接入网设备发送信号；
接着，接入网设备向覆盖区域内的所有终端发送选择消息，选择消息用于选择所有终端中待盘点的终端，该待盘点的终端根据第三盘点请求确定；
然后，接入网设备向所有终端中被选择的终端发送查询请求消息，查询请求消息用于获取所述被选择的终端的标识，所述被选择的终端为所述所有终端中所述待盘点的终端。被选择的目标终端发起随机接入过程，其中一个终端设备随机接入成功，本实施例中为第一终端。具体的随机接入过程可以是：接入网设备在第一查询消息中包括第一随机数，选中的终端根据第一随机数本地设置第二随机数。若一个终端设置的第二随机数为0时，则这个终端向接入网设备发送第三随机数。若接入网设备能够正确接收到第三随机数，则接入网设备向这个终端设备发送第三随机数。当这个终端接收到第三随机数时，这个终端设备确定随机接入成功。终端确认随机成功后，向RAN发送终端的标识信息；
最后，接入网设备接收来自第一终端的标识。
本申请中对于具体的盘点流程不做详细的描述，可以参考目前盘点流程的描述。
在上述实现方式中，方法300还包括：S361，终端管理功能网元向计费网元发送第三消息，相应地，计费网元接收第三消息。
其中，该第三消息用于请求关闭(即结束)对目标终端的第一操作的计费。即第三消息用于结束对S310中发起的盘点请求的计费。
具体地，若第二消息为融合计费创建请求消息，则第三消息可以是融合计费释放请求 (Nchf_ConvergedCharging_Release Request)消息，请求URI为{apiRoot}/nchf-convergedcharging/{apiVersion}/chargingdata/{ChargingDataRef1}/release。计费网元根据请求URI删除之前创建的Individual Charging Data Resource。若计费网元还有未关闭的CDR，则计费网元向记账系统发送该CDR。
若第二消息为离线计费创建请求消息，则第三消息可以是离线计费释放请求(Nchf_OfflineOnlyCharging_Release Request)消息，请求URI为{apiRoot}/nchf-offlineonlycharging/{apiVersion}/offlinechargingdata/{OfflineChargingDataRef2}/release。计费网元根据请求URI删除之前创建的Individual Offline Only Charging Data。若计费网元还有未关闭的CDR，则CHF向记账系统发送该CDR。
可选地，第三消息可以包括关闭(stop)指示，计费网元根据stop指示关闭计费。
具体来说，第三消息中包括stop指示，计费网元可以根据stop指示结束计费。或者，第三消息中不包括stop指示，第三消息即为stop指示，计费网元根据第三消息结束计费。
可选地，在又一种实现方式中，方法300还包括：S352，终端管理功能网元确定定时器超时。
当接收到第一消息时，终端管理功能网元启动目标终端执行第一操作的定时器，该定时器用于何时确定结束对目标终端的第一操作的计费。当定时器超时时，终端管理功能网元可以停止计费，这种方式有助于提高计费精度，减少资源消耗。
其中，定时器的时长可以是默认时长，例如，定时器的时长可以是5分钟。终端管理功能网元在接收到第一消息的默认时长内未接收到其他第一消息，则结束对目标终端的第一操作的计费。
可选地，方法300还包括：终端管理功能网元向终端管理用户面功能网元发送策略规则，策略规则用于检测目标终端的第一操作执行完成，或，用于检测目标终端的执行第一操作的执行结果，其中，策略规则中包括目标终端的标识信息。
也就是，该策略规则用于检测第一信息或第二信息。
具体地，终端管理功能网元可以将第一信息或第二信息的检测规则发送给终端管理用户面功能网元，从而终端管理用户面功能网元可以根据该检测规则识别第一信息或第二信息，进一步，将第一信息或第二信息发送给终端管理功能网元。
在定时器超时的情况下，方法300还包括：S362，终端管理功能网元向计费网元发送第三消息，相应地，计费网元接收第三消息。
S362的具体描述可以参照上文S361，在此不再赘述。
图4是本申请实施例提供的一种计费的方法的又一示意图。如图4所示，该方法400包括以下步骤。
S410，应用的应用网元AF向终端管理功能网元发送第七消息，相应地，终端管理功能网元接收第七消息。
其中，该第七消息用于请求对目标终端执行第一操作。
具体地，第七消息可以理解为是用于请求终端管理功能网元盘点目标终端的请求消息，可以称为：盘点请求消息。在本申请中，盘点是指对目标终端执行第一操作。
示例性地，第一操作包括以下至少一种：查询终端标识、读、写、灭活、锁、块写、块擦、访问、加密、解密等。
第七消息可以包括以下至少一种：第一操作的指示信息、第一操作对应的操作参数、第一指示信息、目标终端的标识信息、应用的标识信息、第一隧道信息。
关于第一操作的指示信息、第一操作对应的操作参数、第一指示信息、目标终端的标识信息、应用的标识信息、第一隧道信息的说明可以参考上文S310的描述，在此不再赘述。
S420，终端管理功能网元向计费网元发送第八消息，相应地，计费网元接收第八消息。
计费网元可以是融合计费功能网元，也可以是离线计费功能网元，本申请不予限制。
其中，该第八消息用于请求启动对该目标终端的第一操作的计费。
具体地，第八消息可以是Nchf_ConvergedCharging_Create Request消息，请求URI为{apiRoot}/nchf-convergedcharging/{apiVersion}/chargingdata。计费网元根据第八消息创建对应的Individual Charging Data Resource，并生成对应的URI#1，例如，URI#1为{apiRoot}/nchf-convergedcharging/{apiVersion}/chargingdata/{ChargingDataRef1}。计费网元将URI#1返回给终端管理功能网元。
具体地，第八消息还可以是Nchf_OfflineOnlyCharging_CreateRequest消息，请求URI为{apiRoot}/nchf-offlineonlycharging/{apiVersion}/offlinechargingdata。计费网元根据第八消息创建对应的Individual Offline Only Charging Data，并生成对应的资源标识URI#12，例如，URI#2为{apiRoot}/nchf-offlineonlycharging/{apiVersion}/offlinechargingdata/{OfflineChargingDataRef2}。计费网元将URI#2返回给终端管理功能网元。
可选地，第八消息可以包括开始(start)指示，计费网元根据start指示启动计费。
具体来说，第八消息中包括start指示，计费网元可以根据start指示启动计费。或者，第八消息中不包括start指示，第八消息可以表示start指示，计费网元根据第八消息启动计费。
第八消息还包括第一标识，第一标识用于标识终端管理功能网元发起的对目标终端执行第一操作的计费。
具体地，第一标识也可以称为计费标识(charging ID)，其用于标识第八消息。
其中，第一标识由终端管理功能网元分配，例如，针对应用网元发送的不同的第一消息，终端管理功能网元可以分配不同的第一标识，并在第八消息中携带对应的第一标识，从而标识本次计费请求。
具体地，第八消息中还包括发送消息的网元类型，这里的网元类型为终端管理功能网元。
可选地，第八消息可以包括第一操作的指示信息、第一操作对应的操作参数、第一指示信息、目标终端的标识信息、应用的标识信息、第一隧道信息中至少一个。
也就是，终端管理功能网元可以将第九消息中的信息发送至计费网元，计费网元根据这些信息对S410中发起的盘点请求的进行计费。
S430，终端管理功能网元向接入与移动性管理网元发送第九消息，相应地，接入与移动性管理网元接收第九消息。
其中，第九消息用于请求对目标终端执行第一操作。
具体地，终端管理功能网元在接收到第一消息后，根据第一消息确定一个或多个接入 与移动性管理网元，以及每个接入与移动性管理网元对应的一个或多个接入网设备，并向一个或多个接入与移动性管理网元发送第九消息，请求接入与移动性管理网元对其管理区域内的目标终端执行第一操作。
其中，第九消息包括第一标识。
此外，第九消息还包括第一操作的指示信息、第一操作对应的操作参数、第二指示信息、目标终端的标识信息、应用的标识信息、第一隧道信息至少一种，这些信息的描述参考S410。
其中，第二指示信息用于指示待执行第一操作的区域。
具体地，第二指示信息所指示的待执行第一操作的区域包括待盘点的目标终端所位于的位置，第二指示信息包括3GPP的位置信息，例如，TA list或cell list等。
需要说明的是，若应用网元提供的区域(例如，上述的S410中终端管理功能网元接收到的第一消息中包括的第一指示信息所指示的区域)是地理位置和/或市政位置时，终端管理功能网元需要将第一指示信息所指示的区域映射成TA list或cell list。
S440，接入与移动性管理网元向会话管理网元发送第四消息，相应地，会话管理网元接收第四消息。
具体地，接入与移动性管理网元在收到第九消息后，根据第九消息中的应用的标识信息和第一隧道信息等确定需要建立用户面隧道，接入与移动性管理网元向会话管理网元发送第四消息。
该第四消息用于请求建立第一会话，该第一会话用于传输目标终端中一个或多个终端的执行信息。
应理解，在某些情况下，第一会话可以是指隧道，也就是通过隧道传输目标终端中一个或多个终端的执行信息。
其中，一个或多个终端的执行信息也就是对一个或多个终端执行第一操作后所获得的信息。
其中，该第四包括第一标识。
此外，该第四消息还包括以下至少一种：第一隧道信息、目标终端的标识信息、应用的标识信息。
第一或多个终端的执行信息、第一隧道信息、目标终端的标识信息、应用的标识信息的具体描述可以参考上文S330，在此不再赘述。。
S450，会话管理网元向计费网元发送第五消息，相应地，计费网元接收第五消息。
具体地，会话管理网元在接收到第四消息后，可以根据应用的标识信息确定用户面网元，并与用户面网元、应用的服务器共同建立用户面网元和应用的服务器之间的用户面隧道。进一步，会话管理网元向计费网元发送第五消息。
其中，第五消息用于请求启动对目标终端的第一操作的计费。
具体地，第五消息可以是Nchf_ConvergedCharging_Create Request消息，请求URI为{apiRoot}/nchf-convergedcharging/{apiVersion}/chargingdata。计费网元根据第五消息创建对应的Individual Charging Data Resource，并生成对应的资源标识URI#3，例如，URI#3为{apiRoot}/nchf-convergedcharging/{apiVersion}/chargingdata/{ChargingDataRef3}。计费网元将URI#3返回给会话管理网元。
第五消息还可以是Nchf_OfflineOnlyCharging_CreateRequest消息，请求URI为{apiRoot}/nchf-offlineonlycharging/{apiVersion}/offlinechargingdata。计费网元根据第五消息创建对应的Individual Offline Only Charging Data，并生成对应的资源标识URI#4，例如，URI#4为{apiRoot}/nchf-offlineonlycharging/{apiVersion}/offlinechargingdata/{OfflineChargingDataRef4}。计费网元将URI#4返回给会话管理网元。
其中，第五消息包括第一标识。
具体地，第五消息中还包括发送消息的网元类型，这里的网元类型为会话管理网元。
此外，第五消息还可以包括开始(start)指示，计费网元根据start指示启动计费。
具体来说，第五消息中包括start指示，计费网元可以根据start指示启动计费。或者，第五消息中不包括start指示，第五消息可以表示start指示，计费网元根据第五消息启动计费。
在S430中，终端管理功能网元会确定一个或多个接入与移动性管理网元，一个或多个接入与移动性管理网元对应一个或多个会话管理网元，第五消息包括第一标识，从而使得计费网元可以关联第八消息和一个或多个会话管理网元发起的第五消息。
可选地，第五消息包括还包括以下至少一种：第一隧道信息、目标终端的标识信息、应用的标识信息。
S460，计费网元根据第一标识关联第八消息和第五消息。
具体地，计费网元根据第一标识关联终端管理功能网元发起的会话和会话管理网元发起的会话，也就是包括相同第一标识的会话是属于同一盘点请求的。后续对于包括相同第一标识的计费请求，计费网元可以根据从终端管理功能网元和会话管理网元获取的信息汇总后生成CDR。
具体的，计费网元根据第一标识将标识为URI#1和标识为URI#3的资源进行关联，或者根据第一标识将标识为URI#2和标识为URI#4的资源进行关联。
S470，会话管理网元发送第二计费信息，相应地，计费网元接收第二计费信息。
具体地，若第五消息为融合计费创建请求消息，则会话管理网元向计费网元发送Nchf_ConvergedCharging_Update Request消息，请求URI为{apiRoot}/nchf-convergedcharging/{apiVersion}/chargingdata/{ChargingDataRef3}/update。融合计费创建请求消息中包括第二计费信息。计费网元根据请求URI更新之前创建的Individual Charging Data Resource，保存第二计费信息，并根据第二计费信息和第五消息中携带的信息生成CDR，发送给记账系统。
具体地，若第五消息为离线计费创建请求消息，则终端管理功能网元向计费网元发送Nchf_OfflineOnlyCharging_Update Request消息，请求URI为{apiRoot}/nchf-offlineonlycharging/{apiVersion}/offlinechargingdata/{OfflineChargingDataRef2}/update。离线计费创建请求消息中包括第二计费信息。计费网元根据请求URI更新之前创建的Individual Offline Only Charging Data，保存第二计费信息，并根据第二计费信息和第五消息中携带的信息生成CDR，发送给记账系统。
其中，第二计费信息包括目标终端中的一个或多个终端的执行信息。
与S330类似，该一个或多个终端的执行信息包括该一个或多个终端执行第一操作的 执行结果、一个或多个终端的标识信息、一个或多个终端的数量中的至少一项。
“一个或多个终端的执行信息”以及“一个或多个终端”的具体内容可以参考S330中第一计费信息的描述，在此不再赘述。
其中，第二计费信息用于对一个或多个终端执行第一操作的过程计费。
计费网元生成话单CDR的具体方式可以参考上文S340中的描述。
具体地，在上述实施例的一种实现方式中，计费网元可以根据第一计费信息生成第一终端执行第一操作的过程的CDR。
作为示例，在一个或多个终端的执行信息包括第一终端的标识和/或数量1的情况下，计费网元生成的CDR包括以下一项或多项：应用的标识信息、目标终端的标识信息、第一操作的指示信息、第一操作对应的操作参数、第一隧道信息、应用网元的地址信息以及第一终端的标识。或者，CDR包括以下至少一项：应用的标识信息、目标终端的标识信息、第一操作的指示信息、第一操作对应的操作参数、应用网元的地址信息、第一隧道信息、数量1。
作为又一示例，在一个或多个终端的执行信息包括第一终端执行第一操作的执行结果的情况下，计费网元生成的CDR包括应用的标识信息、目标终端的标识信息、第一操作的指示信息、第一操作对应的操作参数、应用网元的地址信息、第一隧道信息、第一终端的标识以及第一终端执行第一操作的执行结果。
具体地，在上述实施例的另一种实现方式中，计费网元可以根据第一计费信息生成目标终端中第一接入网设备的覆盖区域内的终端执行第一操作的过程的CDR。
作为示例，在一个或多个终端的执行信息包括第一接入网设备所获取的终端的标识列表或数量的情况下，计费网元生成的CDR包括以下至少一项：应用的标识信息、目标终端的标识信息、第一操作的指示信息、第一操作对应的操作参数、应用网元的地址信息、第一隧道信息、获取的终端的标识列表。或者CDR包括以下至少一项：应用的标识信息、目标终端的标识信息、第一操作的指示信息、第一操作对应的操作参数、应用网元的地址信息、第一隧道信息、所获取的终端的数量。
作为又一示例，在一个或多个终端的执行信息包括第一接入网设备所获取的终端执行第一操作的执行结果的情况下，计费网元生成的CDR包括以下至少一项：应用的标识信息、目标终端的标识信息、第一操作的指示信息、第一操作对应的操作参数、应用网元的地址信息、第一隧道信息、所获取终端的标识以及对应的执行结果组合的列表。
计费网元可以在接收到每一个第二计费信息生成一个CDR，或者根据网络策略等接收到多个第二计费信息后再根据多个第二计费信息生成一个CDR。
根据上述实施例的方案，会话管理网元可以基于第四消息向计费网元发起计费请求，并在一个或多个终端的第一操作执行完成后，向计费网元发送计费信息，从而计费网元可以根据计费请求和计费信息对一个或多个终端执行第一操作的过程计费。通过该方案，能够实现终端管理过程的计费。
可选地，在上述实施例的一种实现方式中，在S470之前，方法400还包括：S481，会话管理网元接收第一信息，其中，该第一信息用于指示第一终端的第一操作执行完成；或，第一信息包括第一终端的执行信息。
也就是，会话管理网元在接收到第一信息后，向计费网元发送第一计费信息，该第一 计费信息包括第一终端的执行信息。
其中，会话管理网元接收第一信息，包括：
会话管理网元接收来自应用网元的第一信息；或，会话管理网元接收来自第一接入网设备的第一信息。
也就是，该第一信息可以来自于第一接入网设备或应用网元，其中，第一接入网设备用于对第一终端执行第一操作。
作为一个示例，该第一信息用于指示第一终端的第一操作执行完成，该第一信息来自于应用网元。
具体地，在应用网元对第一终端发起执行命令的情况下，应用网元在接收到第一终端执行第一操作的执行结果后，根据执行结果确定第一终端的第一操作执行完毕，从而应用的服务器通过用户面向第一接入网设备发送第一信息，第一信息经过用户面网元，用户面网元向会话管理网元发送第一信息。
作为又一示例，该第一信息包括第一终端的执行信息，该第一信息来自于第一接入网设备。
具体地，在第一接入网设备对第一终端发起执行命令的情况下，第一接入网设备在接收到第一终端执行第一操作的执行结果后，根据执行结果确定第一终端的第一操作执行完毕，从而向通过用户面向应用的服务器发送第一信息，该第一信息经过用户面网元，用户面网元向会话管理网元发送第一信息。
应理解，第一信息的来源和第一信息的内容没有必然联系，上述几种示例仅为举例说明，本申请不予限制。
可选地，作为上述实施例的又一种实现方式，会话管理网元可以在接收到至少两个第一终端对应的第一信息后，向计费控制网元发送第一计费信息，此时第一计费信息中包括该至少两个第一终端的标识列表或是该至少两个第一终端的数量。
换言之，在该实现方式中，S470中“一个或多个终端”指的是该至少两个第一终端。可选地，在上述实施例的一种实现方式中，在S470之前，方法400还包括：S482，会话管理网元接收第二信息，该第二信息用于指示目标终端中第一接入网设备的覆盖区域内的终端的第一操作执行完成；或，第二信息包括目标终端中第一接入网设备的覆盖范围内的终端的执行信息。
也就是，会话管理网元在接收到第二信息后，向计费网元发送第一计费信息，该第一计费信息包括第一接入网设备的覆盖区域内的终端的执行信息。
其中，该第二信息来自于第一接入网设备。
应理解，第一接入网设备可以根据盘点过程确定其覆盖范围内的目标终端盘点完成，可以向会话管理网元发送第二信息。
作为一个示例，第一接入网设备确定其覆盖范围内的目标终端盘点完成后，可以经过接入与移动性管理网元发送专用的指示信息，指示目标终端中第一接入网设备的覆盖区域内的终端的第一操作执行完成。
作为又一个示例，第一接入网设备确定其覆盖范围内的目标终端盘点完成后，可以通过用户面向应用的服务器发送其覆盖区域内的终端的执行信息，该执行信息经过用户面网元，用户面网元向会话管理网元该执行信息。
可选地，作为上述实施例的又一种实现方式，会话管理网元可以在接收到来自至少两个第一接入网设备对应的第二信息后，向计费控制网元发送第一计费信息，此时第一计费信息中包括该至少两个第一接入网设备覆盖区域内的目标终端的列表或是该至少两个第一接入网设备覆盖区域内的目标终端的列表或是该至少两个第一接入网设备覆盖区域内的目标终端的数量。
换言之，在该实现方式中，S470中“一个或多个终端”指的是该至少两个第一接入网设备的覆盖区域内的终端。
可选地，方法400还包括：S490，接入与移动性管理网元向会话管理网元发送第十一消息，相应地，会话功能网元接收第十一消息。
具体地，接入与移动性管理网元根据其管理区域内一个接入网设备的第二信息确定目标终端的第一操作执行完成，接入与移动性管理网元向会话管理网元发送第十一消息。
其中，该第十一消息用于请求释放第一会话。
可选地，该方法400还包括：S4100，会话管理网元向计费网元发送第六消息，相应地，计费网元接收第六消息。
具体地，在会话管理网元接收到第十一消息后，释放第一会话，并向计费网元发送第六消息。
其中，第六消息用于请求关闭对目标终端的第一操作的计费。
具体地，若第五消息为融合计费创建请求消息，则第六消息可以是Nchf_ConvergedCharging_Release Request消息，请求URI为{apiRoot}/nchf-convergedcharging/{apiVersion}/chargingdata/{ChargingDataRef3}/release。计费网元根据请求URI删除之前创建的Individual Charging Data Resource。可选的，消息中还可以包括未上报的第二计费信息。
具体地，若第五消息为离线计费创建请求消息，则第六消息可以是Nchf_OfflineOnlyCharging_Release Request消息，请求URI为{apiRoot}/nchf-offlineonlycharging/{apiVersion}/offlinechargingdata/{OfflineChargingDataRef4}/release。计费网元根据请求URI删除之前创建的Individual Offline Only Charging Data。可选的，消息中还可以包括未上报的第二计费信息。
类似地，第六消息包括关闭(stop)指示，计费网元根据stop指示关闭计费。
可选地，在一种实现方式中，方法400还包括：S4111，终端管理功能网元确定目标终端的第一操作执行完成。
在上述实现方式中，方法400还包括：S4121，终端管理功能网元向计费网元发送第十请求消息，第十请求消息用于请求关闭目标终端的第一操作的计费。
具体地，终端管理功能网元向计费网元发送Nchf_ConvergedCharging_Release Request消息，请求URI为{apiRoot}/nchf-convergedcharging/{apiVersion}/chargingdata/{ChargingDataRef11}/release。计费网元根据请求URI删除之前创建的Individual Charging Data Resource。若计费网元还有未关闭的CDR，则计费网元向记账系统发送该CDR。
具体地，终端管理功能网元向计费网元发送Nchf_OfflineOnlyCharging_ReleaseRequest消息，请求URI为{apiRoot}/nchf-offlineonlycharging/{apiVersion}/ offlinechargingdata/{OfflineChargingDataRef2}/release。计费网元根据请求URI删除之前创建的Individual Offline Only Charging Data。若计费网元还有未关闭的CDR，则计费网元向记账系统发送该CDR。
S4111和S4121的具体过程可以参考S351和S361。
可选地，在又一种实现方式中，方法400还包括：S4112，终端管理功能网元确定定时器超时。
当接收到第七消息时，终端管理功能网元启动目标终端执行第一操作的定时器。
在定时器超时的情况下，该方法400还包括：S4122，终端管理功能网元向计费网元发送第十请求消息，第十请求消息用于请求关闭目标终端的第一操作的计费。此时，对目标终端的第一操作的计费结束。
S4112和S4122的具体过程可以参考S352和S362。
可选地，方法400还包括：会话管理网元向用户面网元发送策略规则，策略规则用于检测目标终端的第一操作执行完成，或，用于检测目标终端的执行第一操作的执行结果，其中，策略规则中包括目标终端的标识信息。
也就是，该策略规则用于检测第一信息或第二信息。
具体地，会话管理网元可以将第一信息或第二信息的检测规则发送给用户面网元，从而用户面网元可以根据该检测规则识别第一信息或第二信息，进一步，将第一信息或第二信息发送给会话管理网元。
下面结合图5至图14详细说明本申请实施例提供的计费的方法。
为了便于理解，下文中以计费网元为CHF、接入网设备为RAN、接入与移动性管理网元为AMF、终端管理用户面功能网元为终端管理功能网元-UP、会话管理网元为SMF、应用的应用网元为AF、应用的服务器为AS、用户面网元为UPF为例进行说明。
图5是本申请提供的一种计费的方法的又一示意性流程图。图5所示的方法500可以视为上文方法300的一种具体实现方式。图5所示的方法500介绍了在终端管理功能网元将执行命令发送给RAN，由RAN保存并发起执行命令，并由RAN通过控制面上报盘点结果的场景下的计费。
S501，应用的AF向终端管理功能网元发送请求消息#1(第一消息的一例)。
该请求消息#1用于请求对目标终端进行第一操作，该请求消息#1中包括目标终端的标识信息、第一操作的指示信息和应用的信息。
其中，应用的信息包括所述应用的标识信息或所述应用的数据网络接入标识信息。
在该实施例中，当上述的请求消息#1中不携带第一操作的指示信息的情况下，表示第一操作为查询(query)，即查询终端标识；或者，当上述的请求消息#1中携带第一操作的指示信息，且该第一操作的指示信息包括query的情况下，表示第一操作为查询(query)。
可选地，在第一操作的指示信息指示第一操作为除查询终端标识之外的操作的情况下，除了查询终端标识之外的任一种第一操作可以称为执行命令。
可选地，请求消息#1中还包括第一指示信息、操作参数、通知地址#1和关联标识#1。
其中，目标终端的标识信息、第一操作的指示信息、第一指示信息、操作参数、应用的标识信息、通知地址#1如上文中所述，这里不再赘述。
示例性地，关联标识#1用于关联消息#1和针对该消息#1的响应消息#1。
可选地，在终端管理功能网元收到请求消息#1时，终端管理功能网元可以启动定时器。
具体参考上文S310的描述。
S502，终端管理功能网元向CHF发送计费请求消息#1(第二消息的一例)。
其中，计费请求消息#1中包括Start指示。
可选地，计费请求消息#1还可以包括目标终端的标识信息、第一操作的指示信息、操作参数、第一指示信息、应用的标识信息、通知地址#1。
具体参考上文S320的描述。
S503，CHF返回应答消息。
具体地，CHF根据计费请求消息#1启动计费，并向终端管理功能网元发送应答消息。
其中，若计费请求消息#1是Nchf_ConvergedCharging_Create Request消息，则该应答消息可以是Nchf_ConvergedCharging_CreateResponse。或者，若计费请求消息#1是Nchf_OfflineOnlyCharging_CreateRequest消息，则该应答消息可以是Nchf_OfflineOnlyCharging_Create Response。
S504，终端管理功能网元向AMF发送盘点请求#1(第一盘点请求的一例)。
具体地，终端管理功能网元在接收到请求消息#1后，可以根据请求消息#1中的信息(例如，目标终端的标识信息、第一指示信息和应用的标识信息等)确定AMF，以及AMF对应的RAN。譬如终端管理功能网元根据第一指示信息(例如，小区标识)确定对应的RAN或是AMF，或是根据目标终端的标识信息确定该标识信息对应的RAN或是AMF。
本申请实施例中RAN为具有终端盘点功能的RAN。
进一步地，在终端管理功能网元确定AMF之后，终端管理功能网元可以向AMF发送盘点请求#1。
该盘点请求#1用于请求对目标终端进行第一操作，该盘点请求#1中包括目标终端的标识信息、第一操作的指示信息。其中，目标终端的标识信息和第一操作的指示信息如上文中所述，这里不再赘述。
可选地，盘点请求#1中还包括第二指示信息。
示例性地，第二指示信息所用于指示的区域包括该AMF管理的区域，第二指示信息包括3GPP的位置信息(如，TA list，Cell list等)。
若第一指示信息所指示的区域由不同的AMF管理，那么终端管理功能网元要向每个AMF分别发送盘点请求#1，不同的盘点请求#1中包括的第二指示信息不同，用于指示不同的AMF管理的区域。
可选地，盘点请求#1中还包括操作参数，其中，操作参数如上文中所述，这里不再赘述。
可选地，盘点请求#1中还包括通知地址#2和关联标识#2。
示例性地，通知地址#2用于表示终端管理功能网元接收终端信息以及命令执行结果的地址。例如，终端管理功能网元的地址。
示例性地，关联标识#2用于关联盘点请求#1和针对该盘点请求#1的响应消息#2。
S505，AMF向RAN发送盘点请求#2(第二盘点请求的一例)。
该盘点请求#2用于请求对目标终端进行第一操作，该盘点请求#2中包括目标终端的标识信息、第一操作的指示信息。其中，目标终端的标识信息和第一操作的指示信息如上文中所述，这里不再赘述。
可选地，盘点请求#2中还包括第三指示信息、操作参数、通知地址#2和关联标识#2。
示例性地，第三指示信息所用于指示的区域包括该RAN管理的区域，第三指示信息包括3GPP的位置信息(如，TA list，Cell list等)。
若第二指示信息所指示的区域由不同的RAN管理，那么终端管理功能网元要向每个RAN分别发送盘点请求#2，不同的盘点请求#2中包括的第三指示信息不同，用于指示不同的RAN管理的区域。
需要说明的是，在该AMF管理的区域覆盖多个RAN的情况下，该AMF分别向该多个RAN发送盘点请求#2，向不同的RAN发送盘点请求#2与上述的向某个RAN发送盘点请求#2的过程类似，不同的是需要针对不同的RAN确定出该RAN盘点的区域。
应理解，步骤S504和步骤S505的另一种实现方式可以是：终端管理功能网元确定向每一个RAN发送盘点请求#2，终端管理功能网元将盘点请求#2封装在消息#A中，消息#A中还包括RAN的标识信息。当AMF接收到消息#A后，AMF将消息#A解封装后获得盘点请求#2，将盘点请求#2封装在消息#B中发送给RAN的标识信息对应的RAN，可以理解为AMF透传了盘点请求#2。这种情况下，盘点请求#1包括盘点请求#2。
S506，RAN对目标终端进行盘点。
具体地，RAN向覆盖区的所有终端发送射频信号，以便给RAN的覆盖区域内的终端提供激励信号，从而使终端设备向RAN发送信号。
进一步，RAN向RAN的覆盖区域内的终端发送选择消息。
随后RAN向所有选择的终端发送查询请求，对该RAN覆盖范围下的任一个目标终端，记为终端#1(第一终端的一例)，会向RAN发送标识信息。
应理解，此步骤为终端#1的随机接入过程，对于目标终端中的任一个终端，都会进行随机接入过程。
进一步，若在S505中RAN接收到了其他执行命令，则RAN向该终端#1发送执行命令。
终端#1完成执行命令后，向RAN发送执行结果。譬如，若执行命令是read，执行结果中包括读取的数据；若执行命令为write，执行结果是成功或是失败的指示和执行结果。
S507，RAN确定针对该终端#1的盘点完毕，RAN向所有选择的标签发送下一个标签的查询请求，继续执行步骤506。
S508，RAN确定选择的所有终端盘点完成。
RAN确定其覆盖范围内选择的所有终端盘点完成，具体如下：RAN在执行步骤S506之后，在配置的时间内未收到任何终端发起的随机接入请求消息，则RAN判断其覆盖范围内目标终端盘点完成(也可以说查询完成或目标操作完成)。
S509，RAN根据通知地址2向终端管理功能网元发送响应消息#2。
RAN确定其覆盖范围内选择的所有终端盘点完成后，可以根据通知地址#2向终端管理功能网元发送响应消息#2。
具体地，该响应消息#2是针对S504中的盘点请求#1的响应，该响应消息#2包括关 联标识#2。
具体地，RAN接收到目标终端的标识和执行结果之后，可以通过两种方式上报：
方式一、RAN确定终端#1将S506的步骤执行完成后，向终端管理功能网元发送响应消息#2。
即针对每个目标终端分别上报该目标终端的标识和执行结果。
在方式一中，S509可以在S506之后执行。
在方式一中，响应消息#2包括终端#1的执行信息(第一信息的一例)，即终端#1的标识和/或数量，应理解，此时数量的值为1。
可选地，若S506中RAN发送了执行命令并接收到了执行结果，则终端#1的执行信息还包括执行结果。
可选地，响应消息#2还包括RAN的标识。
可选地，响应消息#2还包括信息#1，用于指示终端#1盘点完成。
具体参考上文S341的描述。
方式二、RAN在所有接收到的目标终端都将S506的步骤执行完成后，向终端管理功能网元发送响应消息#2。
即针对所有接收到的目标终端统一上报目标终端的标识和执行结果。
在方式二中，S509可以在S508之后执行。
在方式二中，响应消息#2包括目标终端中RAN覆盖区域内的终端的执行信息(第二信息的一例)，即RAN获取的终端的标识列表和/或数量。其中，RAN获取的终端，也就是向RAN发送标识的终端，也就是目标终端中RAN覆盖区域内的终端。
可选地，若S506中RAN发送了执行命令并接收到了执行结果，则目标终端中RAN覆盖区域内的终端的执行信息还包括每个终端对应的执行结果的列表。
可选地，响应消息#2还包括RAN的标识。
可选地，响应消息#2还包括信息#2，用于指示该RAN覆盖区域内的目标终端盘点完成，或者说，RAN盘点结束。
具体参考上文S342的描述。
S510，终端管理功能网元向AF发送响应消息#1。
终端管理功能网元在接收到响应消息#2后，会向AF发送响应消息#1。
具体地，该响应消息#1是针对S501中的请求消息#1的响应，该响应消息#1包括关联标识#1。
可选地，响应消息#2还包括RAN的标识。
该响应消息#1还包括响应消息#2中的信息，具体地，针对S509中的方式一和方式二，响应消息#1中包括的信息不同。
针对方式一，响应消息#1包括终端#1的执行信息，即终端#1的标识、数量1、执行结果至少一种。
针对方式二，响应消息#1包括目标终端中RAN覆盖区域内的终端的执行信息，即RAN获取的终端的标识列表、RAN获取的终端的数量、每个终端对应的执行结果的列表至少一种。
S511，终端管理功能网元向CHF发送计费信息#1(第一计费信息的一例)。
终端管理功能网元在接收到响应消息#2后，即在接收到终端#1的执行信息或目标终端中RAN覆盖区域内的终端的执行信息后，可以向CHF发送计费信息#1。
具体地，计费信息#1中包括临时(interim)指示或更新(update)指示，该interim指示或update指示用于指示CHF更新计费信息，用于生成针对该计费信息#1的话单。
针对响应消息#2中包括的信息，计费信息#1还可以包括目标终端中终端#1的信息，即终端#1的标识、数量1、执行结果至少一种，或者，计费信息#1包括目标终端中RAN覆盖区域内的终端的信息，即RAN获取的终端的标识列表、RAN获取的终端的数量、每个终端对应的执行结果的列表至少一种。
可选地，计费信息#1还包括RAN的标识。
具体参考上文S330的描述。
应理解，终端管理功能网元可以先向AF发送响应消息#1，也可以先向CHF发送计费信息#1，本申请不做限定。即，S510和S511之间没有必然的先后顺序。
S512，CHF向终端管理功能网元返回应答消息。
具体地，若计费信息#1中包括终端#1的执行信息，则CHF可以根据计费信息#1生成RAN盘点终端#1的过程的CDR。
具体地，若计费信息#1中包括目标终端中RAN覆盖区域内的终端的执行信息，则CHF可以根据计费信息#1生成RAN盘点其覆盖区域内的终端的过程的CDR。
CHF可以根据每一个接收到计费信息#1生成一个CDR，或者根据网络策略等根据多个计费信息#1生成一个CDR。
S513，终端管理功能网元确定目标终端盘点完成或者确定定时器超时。
其中，终端管理功能网元确定目标终端盘点完成的具体方式可以是终端管理功能网元确定S504中确定的RAN均发送了信息#2。
具体参考上文S351的描述。
可选地，若S501中终端管理功能网元启动了定时器，则当终端管理功能网元确定定时器超时时，终端管理功能网元执行S514。
具体参考上文S352的描述。
S514，终端管理功能网元向CHF发送计费请求消息#2(第三消息的一例)。
其中，计费请求消息#2中包括stop指示，该stop指示用于指示CHF关闭针对计费请求消息#1的计费。
具体参考上文S361的描述。
S515，CHF向终端管理功能网元返回应答消息。
具体地，CHF可以根据stop指示关闭本次计费。若CHF还有未关闭的CDR，则CHF向记账系统发送该CDR。
应理解，S513至S515为可选的步骤，例如，在永久在线计费的场景下，终端管理功能网元可以不执行S513和S514，此时，CHF也不会执行S515。
图5所示的方法500介绍了在RAN通过控制面上报盘点结果的盘点场景下的计费，且在该盘点场景中，执行命令是由RAN发起的。因此，本申请实施例提供的计费方法能够适用于各种不同的盘点场景，具有更好的兼容性和灵活性。
图6是本申请提供的一种计费的方法的又一示意性流程图。图6所示的方法600可以视为上文方法300的又一种具体实现方式。图6所示的方法600介绍了终端管理功能网元保存执行命令、发起执行命令，并由RAN通过控制面上报盘点结果的场景下的计费。
S601，应用的AF向终端管理功能网元发送请求消息#1。
S602，终端管理功能网元向CHF发送计费请求消息#1。
S603，CHF返回应答消息。
S601至S603，参考S501至S503，这里不再赘述。
S604，终端管理功能网元向AMF发送盘点请求#3(第一盘点请求的又一例)。
与S504类似，不同点在于，若S601中包括执行命令，则终端管理功能网元保存该执行命令，在盘点请求#3中不包括该执行命令，因此也不包括操作参数。
S605，AMF向RAN发送盘点请求#4(第二盘点请求的又一例)。
与S505类似，可能的不同点在于，盘点请求#4相对盘点请求#2来说，不包括执行命令和操作参数。
S606，RAN进行目标终端盘点。
与S506类似，盘点过程包括RAN发送射频信号、选择消息、查询请求，终端#1完成随机接入过程，向RAN发送标识信息。
不同点在于，S606中，RAN不会向该终端#1发送执行命令，因此终端#1也不会向RAN发送执行结果。
S607，RAN向终端管理功能网元发送响应消息#2。
具体地，S607中的响应消息#2是针对S605中的盘点请求#4的响应，该响应消息#2包括关联标识#2。
响应消息#2包括终端#1的执行信息，即终端#1的标识和/或数量，应理解，此时数量的值为1。
可选地，响应消息#2还包括RAN的标识。
S608，若S601中包括执行命令，则终端管理功能网元向RAN发送执行命令。
S609，RAN向终端#1发送执行命令。
S610，终端#1向RAN发送执行结果。
S611，RAN向终端管理功能网元发送执行结果。
应理解，执行结果也是终端#1的执行信息。
S612，终端管理功能网元向RAN发送终端#1盘点完成的指示。
终端管理功能网元根据执行结果确定所有执行命令执行完成，即终端管理功能网元确定终端#1盘点完成，则向RAN发送终端#1盘点完成的指示(第一信息的一例)。
在方法600中，终端#1盘点完成的指示即为第一信息的一例，S612可以理解为是终端管理功能网元确定第一信息并向RAN发送第一信息的过程。
S613，终端管理功能网元向CHF发送计费信息#2(第一计费信息的又一例)。
终端管理功能网元在根据请求消息#1中的执行命令确定终端#1盘点完成后，即确定第一信息后，可以向CHF发送计费信息#2，计费信息#2中包括临时(interim)指示或更新(update)指示，该interim指示或update指示用于指示CHF更新计费信息，生成针对该计费信息#2的话单。
计费信息#2还包括S607中的终端#1的执行信息，即终端#1的标识和/或数量1。
可选地，若S608至S610执行，则终端管理功能网元接收到的终端#1的执行信息还包括执行结果，因此，计费信息#2中还包括S611中终端#1的执行信息，即执行结果。
可选地，计费信息#1还包括RAN的标识。
可选地，S613可以不执行，也就是，终端管理功能网元保存接收到的终端#1的执行信息。
S614，CHF向终端管理功能网元返回应答消息。
具体地，CHF可以根据计费信息#1生成RAN盘点终端#1的过程的话单。
应理解，若S613不执行，则S614也不执行。
S615，RAN确定针对该终端#1的盘点完成，RAN向所有选择的标签发送下一个标签的查询请求，继续执行步骤S606。
具体地，RAN确定针对该终端#1的盘点完成可以是根据S612中来自终端管理功能网元的指示。
进一步，RAN、目标终端、终端管理功能网元、CHF可以继续执行S607-S614。
S616，RAN判断选择的所有标签盘点完成，向终端管理功能网元发送信息#2(第二信息的一例)，信息#2用于指示该RAN覆盖区域内的目标终端盘点完成，或者说，RAN盘点结束。
RAN判断选择的所有标签盘点完成的具体方法参考S508，在此不再赘述。
在方法600中，信息#2即为第二信息的一例，S616可以理解为是终端管理功能网元接收第二信息的过程。
若S613-S614不执行，则在S616之后，该方法600还包括S617-S618。
S617，终端管理功能网元向CHF发送计费信息#3(第一计费信息的又一例)。
终端管理功能网元在接收到信息#2后，可以向CHF发送计费信息#1。
计费信息#3中包括临时(interim)指示或更新(update)指示，该interim指示或update指示用于指示CHF生成针对该计费信息#3的话单。
计费信息#3还可以包括终端管理功能网元保存的多个终端#1的执行信息。应理解，多个终端#1的执行信息汇总成了目标终端中RAN覆盖区域内的终端的执行信息，即RAN获取的终端的标识列表、RAN获取的终端的数量、每个终端对应的执行结果的列表至少一种。
可选地，计费信息#3还包括RAN的标识。
也就是，终端管理功能网元可以在接收到终端#1的执行信息后，不发送计费信息#2，而是保存终端#1的执行信息，在接收到信息#2后，发送计费信息#3，计费信息#3包括其保存多个终端#1的执行信息，从而请求CHF对RAN覆盖区域内的目标终端的盘点过程进行计费。
S618，CHF向终端管理功能网元返回应答消息。
具体地，计费信息#3中的消息包括目标终端中RAN覆盖区域内的终端的执行信息，则CHF可以根据计费信息#3生成RAN盘点其覆盖区域内的终端的过程的话单。
S619，终端管理功能网元向AF发送响应消息#1。
具体地，S619中的该响应消息#1是针对S601中的请求消息#1的响应，该响应消息 #1包括关联标识#1。
响应消息#1包括RAN获取的终端的标识列表、RAN获取的终端的数量、RAN的标识、每个终端对应的执行结果的列表至少一种。
可选地，终端管理功能网元也可以在S613之后执行S619，即终端管理功能网元在终端#1盘点完成后，将终端#1的执行信息上报至AF。此时，响应消息#1中可以包括终端#1的标识、数量1、RAN的标识、执行结果至少一种。对于RAN上报的每一个目标终端的标识和执行结果，终端管理功能网元均可以执行S619。
应理解，终端管理功能网元可以先向AF发送响应消息#1，也可以先向CHF发送计费信息#1，本申请不做限定。即，S617和S619之间没有必然的先后顺序，终端管理功能网元可以先执行S617，也可以先执行S619。
S620，终端管理功能网元确定目标终端盘点完成或者确定定时器超时。
S621，终端管理功能网元向CHF发送计费请求消息#2。
S622，CHF向终端管理功能网元返回应答消息。
S620至S622，参考S513至S515的描述，这里不再赘述。
图6所示的方法600介绍了RAN通过控制面上报盘点结果的盘点场景下的计费，且在该盘点场景下，执行命令的发起是由终端管理功能决策的。因此，本申请实施例提供的计费方法能够适用于各种不同的盘点场景，具有更好的兼容性和灵活性。
图7是本申请提供的一种计费的方法的又一示意性流程图。图7所示的方法700可以视为上文方法300的又一种具体实现方式。图7所示的方法700介绍了AF确定执行命令、发起执行命令，并由RAN通过控制面上报盘点结果的场景下的计费。
S701，应用的AF向终端管理功能网元发送请求消息#2(第一消息的又一例)。
参考S501的描述，不同点在于，请求消息#2中不包括请求消息#1中可能包括的执行命令。
S702，终端管理功能网元向CHF发送计费请求消息#3(第二消息的一例)。
参考S502的描述，不同点在于，计费请求消息#3中不包括计费请求消息#1中可能包括的执行命令。
S703，CHF返回应答消息。
具体地，CHF根据计费请求消息#3启动计费，并向终端管理功能网元发送应答消息，该应答消息可以是计费数据应答消息。
S704，终端管理功能网元向AMF发送盘点请求#5(第一盘点请求的又一例)。
参考S504的描述，可能的不同点在于，在盘点请求#5中不包括执行命令和操作参数。
S705，AMF向RAN发送盘点请求#4。
S706，RAN进行目标终端盘点。
S707，RAN向终端管理功能网元发送响应消息#2。
S705至S707，参考S605至S607的描述。
S708，终端管理功能网元向AF发送响应消息#1。
具体地，S708中的该响应消息#1是针对S701中的请求消息#2的响应，该响应消息#1包括关联标识#1。
响应消息#1包括终端#1的执行信息，即终端#1的标识和或数量1。
可选地，响应消息#1还包括RAN的标识。
S709，若AF还有后续的执行命令，则AF向终端管理功能网元发送执行命令。
S710，终端管理功能网元向RAN发送执行命令。
S711，RAN向终端#1发送执行命令。
S712，终端#1向RAN发送执行结果。
S713，RAN向终端管理功能网元发送执行结果。
S711至S713，参考S609至S611。
S714，终端管理功能网元向AF发送执行结果。
在方法700中，终端管理功能网元在接收到终端#1的执行结果后，将终端#1的执行结果上报至AF。
应理解，执行结果也是终端#1的执行信息。
S715，AF向终端管理功能网元发送终端#1盘点完成的指示(第一信息的又一例)。
AF根据终端#1的执行结果确定所有执行命令执行完成，即AF确定终端#1盘点完成，则向终端管理功能网元发送终端#1盘点完成的指示。
在方法700中，终端#1盘点完成的指示即为第一信息的一例，S715可以理解为是AF确定第一信息并向终端管理功能网元发送第一信息的过程。
S716，终端管理功能网元向RAN发送终端#1盘点完成的指示。
S717，终端管理功能网元向CHF发送计费信息#2。
终端管理功能网元在接收到第一信息后，可以向CHF发送计费信息#1。
可选地，计费信息#2还包括S709中接收到的执行命令。
可选地，S717可以不执行，也就是，终端管理功能网元保存接收到的终端#1的执行信息。
S718，CHF向终端管理功能网元返回应答消息。
应理解，若S717不执行，则S718也不执行。
S719，RAN确定针对该终端#1的盘点完成，RAN向所有选择的标签发送下一个标签的查询请求，继续执行步骤S706。
进一步，RAN、目标终端、终端管理功能网元、AF、CHF可以继续执行S706-S719。
S720，RAN判断选择的所有标签盘点完成，向终端管理功能网元发送信息#2(第二信息的一例)，信息#2用于指示该RAN覆盖区域内的目标终端盘点完成。
在方法700中，信息#2即为第二信息的一例，S720可以理解为是终端管理功能网元接收第二信息的过程。
S717至S720，参考S613至S616。
S721，终端管理功能网元向AF发送信息#2。
可选地，终端管理功能网元可以将RAN盘点结束的指示发送给AF。
若S717-S718不执行，则在S721之后，该方法700还包括S722-S723。
S722，终端管理功能网元向CHF发送计费信息#3。
可选地，计费信息#3还包括在重复执行S709时所接收到的多个执行命令。
S723，CHF向终端管理功能网元返回应答消息。
可选地，终端管理功能网元在接收到信息#2后，可以先向CHF发送计费信息#3，也 可以先向AF发送信息#2，本申请不作限定，也就是，S721和S722之间没有必然的先后顺序。
S724，终端管理功能网元向AF发送响应消息#1。
S725，终端管理功能网元确定目标终端盘点完成或者确定定时器超时。
S726，终端管理功能网元向CHF发送计费请求消息#2。
S727，CHF向终端管理功能网元返回应答消息。
S722至S727，参考S617至S622，这里不再赘述。
图7所示的方法700介绍了RAN通过控制面上报盘点结果的盘点场景下的计费，且在该盘点场景中，执行命令的是由AF发起的。因此，本申请实施例提供的计费方法能够适用于各种不同的盘点场景，具有更好的兼容性和灵活性。
一种可能的实现方式，图5、图6、图7中终端管理功能网元可以和NEF合设，上述的终端管理功能网元执行的动作可以理解为NEF执行的动作。
该实现方式下，图5、图6、图7所示的方法流程可以应用于图8中的(a)所示的网络架构中。
另一种可能的实现方式，图5、图6、图7中终端管理功能网元可以为新增的独立功能网元，能够用于转发AF和AMF之间的盘点请求和响应。
该实现方式下，图5、图6、图7所示的方法流程可以应用于图8中的(b)所示的网络架构中。
又一种可能的实现方式，图5、图6、图7中终端管理功能网元可以为新增的独立功能网元，能够用于转发NEF和AMF之间的盘点请求和响应，也就是说图5、图6、图7中所示的终端管理功能网元和AF之间的盘点请求和响应需要通过NEF转发。
该实现方式下，图5、图6、图7所示的方法流程可以应用于图8中的(c)所示的网络架构中。
又一种可能的实现方式，图5、图6、图7中终端管理功能网元可以为和AMF合设，上述终端管理功能网元和AMF之间的交互可以理解为内部交互。
该实现方式下，图5、图6、图7所示的方法流程可以应用于图8中的(d)所示的网络架构中。
图5、图6、图7所示的方法信息介绍了RAN通过AMF、终端管理功能网元上报盘点结果的场景下的计费流程。
示例性地，RAN还可以通过隧道上报盘点结果，下面将结合图9至图10详细介绍通过隧道上报盘点结果的场景下的计费流程。
图9是本申请提供的一种计费的方法的又一示意性流程图。图9所示的方法900可以视为上文方法300的又一种具体实现方式。具体地，图9所示的方法900介绍了在终端管理功能网元-CP将执行命令发送给RAN，由RAN保存并发起执行命令，并由RAN通过终端管理功能网元-UP上报盘点结果的场景下的计费。
S901，应用的AF向终端管理功能网元-CP发送请求消息#3(第一消息的又一例)。
具体地，请求消息#3与上述的S501中所示的请求消息#1类似，该请求消息#3用于请求对目标终端进行第一操作，该请求消息#3与请求消息#1的不同在于：请求消息#3不包括通知地址#1和关联标识#1，但是包括应用服务器(application server，AS)隧道信息 (第一隧道信息的一例)。
其中，AS隧道信息用于指示应用的服务器接收盘点结果的用户面端口，或者用户面地址，例如，该AS隧道信息为AS的地址。
具体参考上文S310的描述。
S902，终端管理功能网元-CP向CHF发送计费请求消息#4(第二消息的又一例)。
具体地，计费请求消息#4与上述的S502中所示的计费请求消息#1类似，不同之处在于计费请求消息#4不包括通知地址#1，但是包括AS隧道信息。
具体参考上文S320的描述。
S903，CHF返回应答消息。
具体地，CHF根据计费请求消息#4启动计费，并向终端管理功能网元-CP发送应答消息，该应答消息可以是计费数据应答消息。
S904，终端管理功能网元-CP向终端管理功能网元-UP发送请求消息#4。
具体地，该实施例中终端管理功能网元-CP需要根据应用的标识信息等信息确定终端管理功能网元-UP，其中终端管理功能网元-CP保存应用的标识信息与终端管理功能网元-UP的对应关系。
在终端管理功能网元-CP确定终端管理功能网元-UP之后，可以向终端管理功能网元-UP发送请求消息#4，该请求消息#4也可以称为隧道信息请求消息，其用于获取隧道信息。
其中，计费请求消息#4包括目标终端的标识信息、AS隧道信息。
S905，终端管理功能网元-UP向终端管理功能网元-CP发送响应消息#4。
其中，响应消息#4用于响应S904中的请求消息#4，响应消息#4也可以称为隧道信息应答消息。
响应消息#4包括CN隧道信息#1，CN隧道信息#1为终端管理功能网元-UP接收上行数据的隧道端点。
S906，终端管理功能网元-CP向AMF发送盘点请求#5(第一盘点请求的又一例)。
具体地，终端管理功能网元-CP在接收到请求消息#3后，可以根据请求消息#3中的信息确定AMF，以及AMF对应的RAN。具体过程参考S504的描述，在此不再赘述。
进一步地，在终端管理功能网元-CP确定AMF之后，终端管理功能网元-CP可以向AMF发送盘点请求#5。
盘点请求#5包括的内容可以参考S504中盘点请求#1，不同之处在于盘点请求#5不包括通知地址#2和关联标识#2，但是包括CN隧道信息#1。
S907，AMF向RAN发送盘点请求#6(第二盘点请求的又一例)。
盘点请求#6包括的内容可以参考S505中盘点请求#2，不同之处在于盘点请求#6不包括通知地址#2和关联标识#2，但是包括CN隧道信息#1。
S908，RAN向AMF发送盘点响应#6。
该盘点响应#6也可以称为盘点应答消息，其包括AN隧道信息。
其中，AN隧道信息为RAN接收下行数据的隧道端点。
S909，AMF向标签管理功能-CP发送盘点响应#5。
该盘点响应#5也可以称为盘点应答消息，其包括AN隧道信息。
S910，标签管理功能-CP向标签管理功能-UP发送会话更新请求消息，消息中包括AN 隧道信息。
S911，标签管理功能-UP向标签管理功能-CP返回应答消息，即会话更新响应消息。
应理解，S904至S911也可以理解为建立隧道的过程。
S912，RAN对目标终端进行盘点。
S913，RAN确定针对该终端#1的盘点完成，RAN向所有选择的标签发送下一个标签的查询请求，继续执行步骤S912。
S914，RAN确定选择的所有终端盘点完成。
S912至S914，参考S506至S508。
S915，RAN根据CN隧道信息#1向终端管理功能网元-UP发送数据#1(第一数据的一例)，进一步，终端管理功能网元-UP根据AS隧道信息向AS发送数据#1。
具体地，RAN接收到目标终端的标识和执行结果之后，可以通过两种方式上报：
方式一、RAN确定终端#1将S912的步骤执行完成后，根据CN隧道信息#1向终端管理功能网元发送数据#1。
即针对每个目标终端分别上报该目标终端的标识和执行结果。
在方式一中，S915可以在S912之后执行。
在方式一中，数据#1包括终端#1的执行信息(第一信息的又一例)，即终端#1的标识和/或数量，应理解，此时数量的值为1。
可选地，若S907中RAN发送了执行命令并接收到了执行结果，则终端#1的执行信息还包括执行结果。
可选地，数据#1还包括RAN的标识。
可选地，数据#1还包括信息#1，用于指示终端#1盘点完成。
具体参考上文S341的描述。
方式二、RAN在其覆盖区域内所有接收到的目标终端都将S912的步骤执行完成后，根据CN隧道信息#1向终端管理功能网元-UP发送数据#1。
即针对所有接收到的目标终端统一上报目标终端的标识和执行结果。
在方式二中，S915可以在S914之后执行。
在方式二中，数据#1包括目标终端中RAN覆盖区域内的终端的执行信息(第二信息的一例)，即RAN获取的终端的标识列表和/或数量。其中，RAN获取的终端，也就是向RAN发送标识的终端，也就是目标终端中RAN覆盖区域内的终端。
可选地，若S907中RAN发送了执行命令并接收到了执行结果，则目标终端中RAN覆盖区域内的终端的执行信息还包括每个终端对应的执行结果的列表。
可选地，数据#1还包括RAN的标识。
具体参考上文S342的描述。
进一步，无论方式一或方式二，终端管理功能网元-UP根据AS隧道信息向AS发送数据#1。
S916，终端管理功能网元-UP向终端管理功能网元-CP发送数据报告#1。
终端管理功能网元-UP在接收到数据#1后，可以将数据#1中的信息发送给终端管理功能网元-CP。
应理解，终端管理功能网元-UP可以根据策略规则检测数据#1中的信息，从而将数据 #1中终端#1的执行信息或目标终端中RAN覆盖区域内的终端的执行信息发送给终端管理功能网元-CP。
可选地，若数据报告#1中包括信息#1或信息#2，则终端管理功能网元-UP还可以根据策略规则检测信息#1或信息#2，从而将信息#1或信息#2发送给终端管理功能网元-CP。
具体地，针对S915中的方式一和方式二，数据报告#1中包括的信息不同。
针对方式一，数据报告#1包括终端#1的执行信息，即终端#1的标识、数量1、执行结果至少一种。
可选地，数据报告#1还包括信息#1，用于指示终端#1盘点完成。
针对方式二，数据报告#1包括目标终端中RAN覆盖区域内的终端的执行信息，即RAN获取的终端的标识列表、RAN获取的终端的数量、每个终端对应的执行结果的列表至少一种。
可选地，无论针对方式一还是方式二，数据报告#1还包括RAN的标识。
S917，终端管理功能网元-CP向CHF发送计费信息#4(第一计费信息的又一例)。
终端管理功能网元-CP在接收到数据报告#1后，即在接收到终端#1的执行信息或目标终端中RAN覆盖区域内的终端的执行信息后，可以向CHF发送计费信息#4。
具体地，计费信息#4中包括的内容与S511中计费信息#1类似，包括临时(interim)指示或更新(update)指示。
此外，针对数据报告#1中包括的信息，计费信息#4还可以包括目标终端中终端#1的执行信息，即终端#1的标识、数量1、执行结果至少一种，或者，计费信息#4包括目标终端中RAN覆盖区域内的终端的执行信息，即RAN获取的终端的标识列表、RAN获取的终端的数量、每个终端对应的执行结果的列表至少一种。
可选地，计费信息#4还包括RAN的标识。
具体参考上文S330的描述。
S918，CHF向终端管理功能网元-CP返回应答消息。
具体地，若计费信息#4中的消息包括终端#1的执行信息，则CHF可以根据计费信息#4生成RAN盘点终端#1的过程的话单。
具体地，若计费信息#4中的消息包括目标终端中RAN覆盖区域内的终端的执行信息，则CHF可以根据计费信息#4生成RAN盘点其覆盖区域内的终端的过程的话单。
S919，RAN向终端管理功能网元-CP发送信息#2。
RAN判断选择的所有标签盘点完成，向终端管理功能网元发送信息#2，该信息#2用于指示该RAN覆盖区域内的目标终端盘点完成，或者说，RAN盘点结束。
应理解，RAN可以经过AMF向终端管理功能网元-CP发送信息#2。
可选地，RAN可以通过用户面向终端管理功能网元-CP发送信息#2。
具体地，RAN在数据#1中包括信息#2，终端管理功能网元-UP在数据报告#1中包括信息#2。
S920，终端管理功能网元-CP发起隧道释放。
终端管理功能网元-CP在接收到信息#2后，确定RAN盘点完成，从而发起隧道释放。
S921，终端管理功能网元-CP确定目标终端盘点完成或者确定定时器超时。
其中，终端管理功能网元-CP确定目标终端盘点完成的具体方式可以是终端管理功能 网元-CP确定S906中确定的RAN均发送了信息#2。
可选地，若S901中终端管理功能网元-CP启动了定时器，则当终端管理功能网元-CP确定定时器超时时，终端管理功能网元-CP执行S922。
具体参考上文S513的描述。
S922，终端管理功能网元-CP向CHF发送计费请求消息#5(第三消息的又一例)。
具体参考上文S514的描述。
S923，CHF向终端管理功能网元返回应答消息。
具体参考上文S515的描述。
应理解，S921至S923为可选的步骤，例如，在永久在线计费的场景下，终端管理功能网元可以不执行S921和S922，此时，CHF也不会执行S923。
图9所示的方法900介绍了RAN通过终端管理功能网元-UP上报盘点结果的盘点场景下的计费，且在该盘点场景下，执行命令的是由RAN发起的。因此，本申请实施例提供的计费方法能够适用于各种不同的盘点场景，具有更好的兼容性和灵活性。
图10是本申请提供的一种计费的方法的又一示意性流程图。图10所示的方法1000可以视为上文方法300的又一种具体实现方式。具体地，图10所示的方法1000介绍了AF发起执行命令，并由RAN通过终端管理功能网元-UP上报盘点结果的场景下的计费。
S1001，应用的AF向终端管理功能网元-CP发送请求消息#5(第一消息的又一例)。
具体地，请求消息#5与上述的S901中所示的请求消息#3类似，该请求消息#5用于请求对目标终端进行第一操作，该请求消息#5与请求消息#3的不同在于：请求消息#5不包括执行命令。
S1002，终端管理功能网元-CP向CHF发送计费请求消息#6(第二消息的又一例)。
具体地，计费请求消息#6与上述的S902中所示的计费请求消息#5类似，不同之处在于计费请求消息#6不包括执行命令。
S1003，CHF返回应答消息。
具体地，CHF根据计费请求消息#6启动计费，并向终端管理功能网元-CP发送应答消息，该应答消息可以是计费数据应答消息。
S1004，终端管理功能网元-CP向终端管理功能网元-UP发送请求消息#4。
S1005，终端管理功能网元-UP向终端管理功能网元-CP发送响应消息#4。
S1004至S1005，参考S904至S905。
S1006，终端管理功能网元-CP向AMF发送盘点请求#7(第一盘点请求的又一例)。
盘点请求#7包括的内容可以参考S906中盘点请求#5，不同之处在于盘点请求#7不包括执行命令。
S1007，AMF向RAN发送盘点请求#8(第二盘点请求的又一例)。
盘点请求#8包括的内容可以参考S907中盘点请求#6，不同之处在于盘点请求#8不包括执行命令。
S1008，RAN向AMF发送盘点响应#8。
S1009，AMF向标签管理功能-CP发送盘点响应#7。
S1010，标签管理功能-CP向标签管理功能-UP发送会话更新请求消息，消息中包括AN隧道信息。
S1011，标签管理功能-UP向标签管理功能-CP返回应答消息，即会话更新响应消息
S1008至S1011，参考S908至S911。
S1012，RAN进行目标终端盘点。
与S506类似，盘点过程包括RAN发送射频信号、选择消息、查询请求，终端#1完成随机接入过程，向RAN发送标识信息。
不同点在于，S1012中，RAN不会向该终端#1发送执行命令，因此终端#1也不会向RAN发送执行结果。
S1013，RAN根据CN隧道信息#1向终端管理功能网元-UP发送数据#2，进一步，终端管理功能网元-UP根据AS隧道信息向AS发送数据#2。
其中，数据#2包括终端#1的执行信息，即终端#1的标识和/或数量，应理解，此时数量的值为1。
可选地，数据#2还包括RAN的标识。
S1014，若AF还有后续的执行命令，则AF通过用户面向RAN发送执行命令。
具体地，AF通过AS向终端管理功能网元-UP发送数据#3，进一步，终端管理功能网元-UP向RAN发送数据#3。其中，数据#3包括执行命令。
S1015，RAN向终端#1发送执行命令。
S1016，终端#1向RAN发送执行结果。
应理解，执行结果也是终端#1的执行信息。
S1017，RAN根据CN隧道信息#1向终端管理功能网元-UP发送数据#4(第一数据的一例)，进一步，终端管理功能网元-UP根据AS隧道信息向AS发送数据#4。
其中，数据#4包括执行结果。
S1018，AF通过用户面向RAN发送终端#1盘点完成的指示(第一信息的又一例)。
具体地，若AF没有其他执行命令，则AF通过AS向终端管理功能网元-UP发送数据#5，进一步，终端管理功能网元-UP向RAN发送数据#5。其中，数据#5包括终端#1盘点完成的指示。
在方法1000中，终端#1盘点完成的指示即为第一信息的一例，S1018可以理解为是AF确定第一信息并向RAN发送第一信息的过程。
S1019，终端管理功能网元-UP向终端管理功能网元-CP发送数据报告#2。
具体地，终端管理功能网元-UP可以在接收到数据#5后，可以向终端管理功能网元-CP发送数据报告#2。
其中，数据报告#2包括S1013中数据#2中包括的终端#1的执行信息，即终端#1的标识或数量1。
可选地，若终端管理功能网元-UP接收到数据#4，则终端管理功能网元-UP发送的数据#2中还可以包括数据#4中包括的终端#1的执行信息，即执行结果。
可选地，数据报告#2还可以包括RAN的标识。
可选地，数据报告#2还可以包括数据#3中包括执行命令。
可选地，数据报告#2还包括S1018中的终端#1盘点完成的指示。
S1020，终端管理功能网元-CP向CHF发送计费信息#5(第一计费信息的又一例)。
具体地，终端管理功能网元-CP在接收到数据报告#2后，即在接收到终端#1的执行 信息，或者在接收到终端#1的盘点完成的指示后，可以向CHF发送计费信息#5。其中，计费信息#5可以包括数据报告#2中包括的信息，即终端#1的标识、数量1、执行命令、执行结果至少一种。
其中，计费信息#5中包括临时(interim)指示或更新(update)指示。
可选地，计费信息#5还包括RAN的标识。
可选地，S1020可以不执行，也就是，终端管理功能网元-CP保存接收到的终端#1的执行信息。
S1021，CHF向终端管理功能网元-CP返回应答消息。
CHF可以根据计费信息#5生成RAN盘点终端#1的过程的话单。
应理解，若S1020不执行，则S1021也不执行。
S1022，RAN确定针对该终端#1的盘点完毕，RAN向所有选择的标签发送下一个标签的查询请求，继续执行步骤S1012。
具体地，RAN确定针对该终端#1的命令执行完毕可以是根据S1018中来自终端管理功能网元的信息#1。
进一步，RAN、目标终端、终端管理功能网元-CP、终端管理功能网元-UP、AF、AS、CHF可以继续执行S1013-S1022。
S1023，RAN判断选择的所有标签盘点完成，向终端管理功能网元-CP发送信息#2(第二信息的一例)。
该信息#2用于指示RAN覆盖区域内的目标终端盘点完成，或者说，RAN盘点结束。
具体参考S720，在此不再赘述。
若S1020至S1021不执行，则在S1023之后，该方法1000还包括S1024至S1025。
S1024，终端管理功能网元-CP向CHF发送计费信息#6(第一计费信息的又一例)。
计费信息#6中包括临时(interim)指示或更新(update)指示。
其中，计费信息#6包括终端管理功能网元-CP保存的多个终端#1的执行信息。应理解，多个终端#1的执行信息汇总成了目标终端中RAN覆盖区域内的终端的执行信息，即RAN获取的终端的标识列表、RAN获取的终端的数量、每个终端对应的执行结果的列表至少一种。
可选地，计费信息#6还包括RAN的标识。
也就是，终端管理功能网元-CP可以在接收到终端#1的执行信息后，不发送计费信息#5，而是保存终端#1的执行信息，在接收到信息#2后，发送计费信息#6，计费信息#6包括其保存多个终端#1的执行信息，从而请求CHF对RAN覆盖区域内的目标终端的盘点过程进行计费。
S1025，CHF向终端管理功能网元-CP返回应答消息。
具体地，计费信息#6中的消息包括目标终端中RAN覆盖区域内的终端的执行信息，CHF可以根据计费信息#6生成RAN盘点其覆盖区域内的终端的过程的话单。
S1026，终端管理功能网元-CP发起隧道释放。
S1027，终端管理功能网元-CP确定目标终端盘点完成或者确定定时器超时。
S1028，终端管理功能网元-CP向CHF发送计费请求消息#7(第三消息的又一例)。
S1029，CHF向终端管理功能网元返回应答消息。
S1026至S1029参考S920至S923。
图10所示的方法1000介绍了RAN通过终端管理功能网元-UP上报盘点结果的盘点场景下的计费，且在该盘点场景下，执行命令是由AF发起的。因此，本申请实施例提供的计费方法能够适用于各种不同的盘点场景，具有更好的兼容性和灵活性。
可选地，结合方法600和方法1000，本申请还可以提供终端管理功能网元保存执行命令、发起执行命令，并由RAN通过终端管理功能网元-UP上报盘点结果的场景下的计费。具体步骤可以结合方法600和方法1000，在此不再赘述。
一种可能的实现方式，图9和图10中终端管理功能网元-CP、终端管理功能网元-UP可以和NEF合设，上述的终端管理功能网元-CP、终端管理功能网元-UP执行的动作可以理解为NEF执行的动作。
该实现方式下，图9和图10所示的方法流程可以应用于图11中的(a)所示的网络架构中。
另一种可能的实现方式，图9和图10中终端管理功能网元-CP、终端管理功能网元-UP可以为新增的独立功能网元，终端管理功能网元-CP能够用于转发AF和AMF之间的盘点请求和响应，终端管理功能网元-UP能够用于转发RAN和AS之间的用户面数据。
该实现方式下，图9和图10所示的方法流程可以应用于图11中的(b)所示的网络架构中。
又一种可能的实现方式，图9和图10中终端管理功能网元-CP、终端管理功能网元-UP可以为新增的独立功能网元，终端管理功能网元-CP能够用于转发NEF和AMF之间的盘点请求和响应，也就是说图9和图10中所示的终端管理功能网元-CP和AF之间的盘点请求和响应需要通过NEF转发，终端管理功能网元-UP能够用于转发RAN和AS之间的用户面数据。
该实现方式下，图9和图10所示的方法流程可以应用于图11中的(c)所示的网络架构中。
又一种可能的实现方式，图9和图10中终端管理功能网元-CP可以和AMF合设，AMF和终端管理功能网元-CP的交互可以看成是内部交互，终端管理功能网元-UP可以为新增的独立功能网元，能够用于转发RAN和AS之间的用户面数据。
该实现方式下，图9和图10所示的方法流程可以应用于图11中的(d)所示的网络架构中。
应理解，在图9和图10所示的方法中，用户面隧道是由终端管理功能网元-UP发起建立的，在一种实现方式中，用户面隧道可以是AMF发起建立的。下面结合图12至图13说明AMF发起隧道建立的过程。
图12是本申请提供的一种计费的方法的又一示意性流程图。图12所示的方法1200可以视为上文方法400的一种具体实现方式。图12所示的方法1200介绍了在终端管理功能网元将执行命令发送给RAN，由RAN保存并发起执行命令，并由RAN通过UPF上报盘点结果的场景下的计费。
S1201，应用的AF向终端管理功能网元发送请求消息#6(第七消息的一例)。
具体地，该请求消息#6用于请求对目标终端进行第一操作，该请求消息#6中包括目标终端的标识信息、第一操作的指示信息和应用的信息。
其中，应用的信息包括所述应用的标识信息或所述应用的数据网络接入标识信息。
在该实施例中，当上述的请求消息#6中不携带第一操作的指示信息的情况下，表示第一操作为查询(query)，即查询终端标识；或者，当上述的请求消息#6中携带第一操作的指示信息，且该第一操作的指示信息包括query的情况下，表示第一操作为查询(query)。
可选地，在第一操作的指示信息指示第一操作为除查询终端标识之外的操作的情况下，除了查询终端标识之外的任一种第一操作可以称为执行命令。
可选地，请求消息#1中还包括第一指示信息、操作参数和应用服务器(application server，AS)隧道信息。
其中，AS隧道信息用于指示应用的服务器接收盘点结果的用户面端口，或者用户面地址，例如，该AS隧道信息为AS的地址。
可选地，在终端管理功能网元收到请求消息#6时，终端管理功能网元可以启动定时器。
具体参考上文S410的描述。
S1202，终端管理功能网元向CHF发送计费请求消息#8(第八消息的一例)。
其中，计费请求消息#8中包括start指示。
可选地，计费请求消息#8还可以包括目标终端的标识信息、第一操作的指示信息、操作参数、第一指示信息、应用的标识信息、AS隧道信息。
计费请求消息#8还包括标识#1，或者称为计费标识#1，其用于标识终端管理功能网元的计费请求，或者说，其用于标识计费请求消息#8。
具体参考上文S420的描述。
S1203，CHF返回应答消息。
具体地，CHF根据计费请求消息#8启动计费，并向终端管理功能网元发送应答消息，该应答消息可以是计费数据应答消息。
S1204，终端管理功能网元向AMF发送请求消息#7(第九消息的一例)。
该请求消息#7用于请求对目标终端执行第一操作。
具体地，终端管理功能网元在接收到请求消息#6后，可以根据请求消息#6中的信息确定AMF，以及AMF对应的RAN。具体过程参考S504的描述，在此不再赘述。
进一步地，在终端管理功能网元确定AMF之后，终端管理功能网元可以向AMF发送请求消息#7。
可选地，请求消息#7包括目标终端的标识信息、第一操作的指示信息、操作参数、第二指示信息、应用的标识信息、AS隧道信息。
其中，第二指示信息所用于指示的区域包括该AMF管理的区域，第二指示信息包括3GPP的位置信息(如，TA list，Cell list等)
请求消息#7还包括标识#1。
具体参考上文S430的描述。
S1205，AMF向SMF发送会话建立请求消息(第四消息的一例)。
具体地，AMF根据应用标识等信息确定需要建立用户面隧道，以便于传输盘点结果，因此，AMF向SMF发送会话建立请求消息。
其中，会话建立请求消息包括目标终端的标识信息、应用的标识信息、AS隧道信息和标识#1。
会话建立请求消息用于请求建立隧道#1(第一会话的一例)，其中，隧道#1用于传输目标终端中一个或多个终端的执行信息。
具体参考上文S440的描述。
S1206，SMF向UPF发送隧道建立请求消息。
具体地，SMF根据应用标识选择合适的UPF。
SMF选择合适的UPF之后，向UPF发送请求建立隧道的请求消息，即隧道建立请求消息。
其中，隧道建立请求消息用于请求建立用户面隧道，该隧道建立请求消息中包括AS隧道信息。
S1207，UPF和AS之间建立隧道#1。
在UPF接收到隧道建立请求消息后，可以建立UPF和AS之间的用户面隧道。
S1208，UPF向SMF发送隧道建立响应消息。
其中，隧道建立响应消息包括CN隧道信息#2，CN隧道信息#2为UPF接收上行数据的隧道端点。
S1209，SMF向CHF发送计费请求消息#9(第五消息的一例)。
具体地，SMF向CHF发送计费请求消息#9，该计费请求消息#9用于请求启动对目标终端的第一操作的计费。
其中，计费请求消息#9包括Start指示。
可选地，计费请求消息#9还可以包括目标终端的标识信息、应用的标识信息、AS隧道信息。
计费请求消息#9还包括标识#1。
具体参考上文S450的描述。
S1210，CHF返回应答消息。
具体地，CHF根据计费请求消息#9启动计费。
S1211，CHF关联计费请求消息#8和计费请求消息#9。
也就是说，CHF根据标识#1确定计费请求消息#8和计费请求消息#9关联于同一个计费请求，因此，关联SMF发起的计费请求和终端管理功能网元发起的计费请求。CHF将从终端管理功能网元和SMF获取的信息汇总后生成CDR。
具体的，将CHF根据标识#1将URI#1和URI#3标识的资源进行关联，或者根据标识#1将URI#2和URI#4标识的资源进行关联。
具体参考上文S460的描述。
S1212，SMF向AMF发送建立响应消息。
其中，建立响应消息包括CN隧道信息#2。
S1213，AMF向RAN发送盘点请求#9。
其中，盘点请求#9包括AMF在S1204中接收到的目标终端的标识信息、第一操作的指示信息、操作参数、应用的标识信息。
盘点请求#9还包括第三指示信息，第三指示信息所用于指示的区域包括该RAN管理 的区域，第三指示信息包括3GPP的位置信息(如，TA list，Cell list等)。
盘点请求#9还包括CN隧道信息#2。
S1214，RAN向AMF发送盘点响应#9。
RAN保存接收到的目标终端的标识信息、第一操作的指示信息、操作参数、应用的标识信息、第三指示信息、CN隧道信息#2等信息，并向AMF发送响应，即盘点响应#9。
该盘点响应#9也可以称为盘点应答消息，其包括AN隧道信息。
其中，AN隧道信息为RAN接收下行数据的隧道端点。
S1215，AMF向SMF发送请求消息。
其中，请求消息包括AN隧道信息。
S1216，SMF向UPF发送请求消息。
其中，请求消息包括AN隧道信息。
S1217，RAN对目标终端进行盘点。
具体地，RAN向覆盖区的所有终端发送射频信号，以便给RAN的覆盖区域内的终端提供激励信号，从而使终端设备向RAN发送信号。
进一步，RAN向RAN的覆盖区域内的终端发送选择消息。
随后RAN向所有选择的终端发送查询请求，对该RAN覆盖范围下的任一个目标终端，记为终端#1(第一终端的一例)，会向RAN发送标识信息。
应理解，此步骤为终端#1的随机接入过程，对于目标终端中的任一个终端，都会进行随机接入过程。
进一步，若在S1213中RAN接收到了其他执行命令，则RAN向该终端#1发送执行命令。
终端#1完成执行命令后，向RAN发送执行结果。譬如，若执行命令是read，执行结果中包括读取的数据；若执行命令为write，执行结果是成功或是失败的指示和执行结果。
S1218，RAN根据CN隧道信息#2向UPF发送数据#6(第一数据的又一例)，进一步，UPF根据AS隧道信息向AS发送数据#6。
RAN确定终端#1的盘点结束后，可以向UPF发送数据#6。
其中，数据#6包括终端#1的执行信息，即终端#1的标识和/或数量，应理解，此时数量的值为1。
若在S1217中RAN向终端#1发送了执行命令，则数据#6中的终端#1的执行信息还包括执行结果。
可选地，数据#6中还包括信息#1，用于指示终端#1盘点完成。
可选地，S1218可以不执行，也就是，RAN也可以先保存终端#1的执行信息。
S1219，UPF向SMF发送数据报告#3。
UPF在接收到数据#6后，可以向SMF发送数据报告#3。
数据报告#3包括数据#6中的终端#1的执行信息，即终端#1的标识、数量1、执行结果至少一种。
可选地，数据报告#3还包括信息#1，用于指示终端#1盘点完成。
可选地，数据报告#3还包括RAN的标识。
应理解，UPF可以根据策略规则检测终端#1的执行信息，从而将终端#1的执行信息 发送给SMF。
可选地，UPF还可以根据策略规则检测信息#1，从而将信息#1发送给SMF。
S1218至S1219的具体内容参考上文S481的描述。
S1220，SMF向CHF发送计费信息#7(第二计费信息的又一例)。
SMF在接收到数据报告#3后，即在接收到终端#1的执行信息后，可以向CHF发送计费信息#7。
其中，计费信息#7包括数据报告#3中的终端#1的执行信息，即终端#1的标识、数量1、执行结果至少一种。
可选地，计费信息#7还包括RAN的标识。
具体参考上文S470的描述。
S1221，CHF返回应答消息。
具体地，CHF可以根据计费信息#7和计费请求消息#9中携带的信息生成CDR，发送给记账系统。
CHF可以在接收到每一个计费信息#7生成一个CDR，或者根据网络策略等接收到多个第二计费信息后再根据多个计费信息#7生成一个CDR。
可选地，若S1218不执行，则S1219至S1221也不执行。
可选地，若S1218至S1219执行，则S1220至S1221也可以不执行，也就是，SMF也可以先保存数据报告#3中的信息。
S1222，RAN确定针对该终端#1的盘点完成，RAN向所有选择的标签发送下一个标签的查询请求，继续执行步骤S1217。
具体地，RAN确定针对该终端#1的盘点完成可以是确定S1213中的第一操作的指示信息和操作参数均已对终端#1执行完成。
进一步，RAN、目标终端、UPF、SMF、终端管理功能网元、AS、CHF可以继续执行S1218至S1222。
若S1218至S1221不执行，则方法1200还包括S1223至S1225。
S1223，RAN判断选择的所有标签盘点完成，向UPF发送数据#6。进一步，UPF根据AS隧道信息向AS发送数据#6。
该数据#6中包括目标终端中RAN覆盖区域内的终端的执行信息(第二信息的一例)，即RAN获取的终端的标识列表和/或数量。其中，RAN获取的终端，也就是向RAN发送标识的终端，也就是目标终端中RAN覆盖区域内的终端。
可选地，若在S1217中RAN向终端#1发送了执行命令，则信息#2中还包括每个终端对应的执行结果的列表。
可选地，数据#6还包括RAN的标识。
S1224，UPF向SMF发送数据报告#3。
UPF在接收到数据#6后，可以向SMF发送数据报告#3。
该数据报告#3包括目标终端中RAN覆盖区域内的终端的执行信息，即RAN获取的终端的标识列表、RAN获取的终端的数量、每个终端对应的执行结果的列表至少一种。
可选地，数据报告#3还包括RAN的标识。
应理解，UPF可以根据策略规则检测数据#1中的信息，从而将数据#1中的目标终端 中RAN覆盖区域内的终端的执行信息发送给SMF。
可选地，若数据#6中包括信息#2，则UPF还可以根据策略规则检测信息#2，从而将信息#2发送给SMF。
S1225，SMF向CHF发送计费信息#8(第二计费信息的又一例)。
SMF可以在接收到数据报告#3后，即在接收到目标终端中RAN覆盖区域内的终端的执行信息后，向CHF发送计费信息#8。
其中，计费信息#8包括目标终端中RAN覆盖区域内的终端的执行信息，即RAN获取的终端的标识列表、RAN获取的终端的数量、每个终端对应的执行结果的列表至少一种。
可选地，计费信息#8还包括RAN的标识。
S1226，CHF向SMF返回应答消息。
CHF可以根据计费信息#8和计费请求消息#9生成RAN盘点其覆盖区域内的终端的过程的话单。
S1227，RAN向SMF发送信息#2(第二信息的一例)，该信息#2用于指示RAN覆盖区域内的目标终端盘点完成，或者说，RAN盘点结束。
应理解，若S1218至S1219执行，且S1220和S1221未执行，则SMF可以在接收到信息#2后，执行S1225，即向CHF发送计费信息#8。
还应理解，RAN可以经过AMF向SMF发送信息#2。
应理解，AMF在接收到信息#2后，可以向SMF发送信息#2，或者，也可以向SMF发送释放请求消息(第十一消息的一例)，用于请求释放隧道#1。
具体参考上文S490的描述。
S1228，SMF发起隧道释放。
SMF可以在接收到信息#2或释放请求消息后，触发隧道释放。
S1229，SMF向CHF发送计费请求消息#10(第六消息的一例)。
SMF在接收到信息#2后，还可以向CHF发送计费请求消息#10。
其中，计费请求消息#10包括stop指示，该stop指示用于指示CHF关闭针对计费请求消息#9的计费。
具体参考上文S4100的描述。
S1230，CHF向终端管理功能网元返回应答消息。
具体地，CHF可以根据stop指示关闭SMF的本次计费。
S1231，终端管理功能网元确定目标终端盘点完成或者确定定时器超时。
其中，终端管理功能网元确定目标终端盘点完成的具体方式可以是终端管理功能网元收到了S1204中确定的RAN中的每个的信息#2。
应理解，AMF在收到信息#2后，进一步，AMF还可以向终端管理功能网元发送信息#2。
可选地，若在S1201中，终端管理功能网元启动了定时器，则当终端管理功能网元确定定时器超时时，终端管理功能网元执行S1232。
具体参考上文S513的描述。
S1232，终端管理功能网元向CHF发送计费请求消息#11(第十请求消息的一例)。
其中，计费请求消息#11中包括Stop指示，该stop指示用于指示CHF关闭针对计费请求消息#8的计费。
具体参考上文S514和S4121的描述。
S1233，CHF向终端管理功能网元返回应答消息。
具体地，CHF可以根据stop指示关闭本次计费，若CHF还有未关闭的CDR，则CHF向记账系统发送该CDR。
具体参考上文S514的描述。
应理解，S1231至S1233为可选的步骤，例如，在永久在线计费的场景下，终端管理功能网元可以不执行S1231和S1232，此时，CHF也不会执行S1233。
图12所示的方法1200介绍了RAN通过UPF上报盘点结果的盘点场景下的计费，且在该盘点场景下，执行命令是由RAN发起的。因此，本申请实施例提供的计费方法能够适用于各种不同的盘点场景，具有更好的兼容性和灵活性。
图13是本申请提供的一种计费的方法的又一示意性流程图。图13所示的方法1300可以视为上文方法400的一种具体实现方式。图13所示的方法1300介绍了AF确定执行命令、发起执行命令，并由RAN通过UPF上报盘点结果的场景下的计费。
S1301，应用的AF向终端管理功能网元发送请求消息#8(第七消息的又一例)。
具体地，该请求消息#8与上述的S1201中所示的请求消息#6类似，该请求消息#8用于请求对目标终端进行第一操作，该请求消息#8与请求消息#6的不同在于：请求消息#8不包括执行命令。
S1302，终端管理功能网元向CHF发送计费请求消息#12(第八消息的一例)。
具体地，计费请求消息#12与上述的S1202中所示的计费请求消息#9类似，不同之处在于计费请求消息#12不包括执行命令。
S1303，CHF返回应答消息。
具体地，CHF根据计费请求消息#12启动计费，并向终端管理功能网元发送应答消息，该应答消息可以是计费数据应答消息。
S1304，终端管理功能网元向AMF发送请求消息#9(第九消息的一例)。
具体地，请求消息#9与上述的S1204中所示的请求消息#7类似，不同之处在于请求消息#9不包括执行命令。
S1305，AMF向SMF发送会话建立请求消息。
S1306，SMF向UPF发送隧道建立请求消息。
S1307，UPF和AS之间建立隧道。
S1308，UPF向SMF发送隧道建立响应消息。
S1309，SMF向CHF发送计费请求消息#9。
S1310，CHF返回应答消息。
S1311，CHF关联计费请求消息#8和计费请求消息#9。
S1312，SMF向AMF发送会话建立响应消息。
S1305至S1312参考S1205至S1212，在此不再赘述。
S1313，AMF向RAN发送盘点请求#10。
具体地，盘点请求#10与上述的S1213中所示的盘点请求#9类似，不同之处在于盘点 请求#10不包括执行命令。
S1314，RAN向AMF发送盘点响应#10。
S1315，AMF向SMF发送请求消息。
S1316，SMF向UPF发送请求消息。
S1314至S1316参考S1214至S1216，在此不再赘述。
S1317，RAN对目标终端进行盘点。
与S1217类似，盘点过程包括RAN发送射频信号、选择消息、查询请求，终端#1完成随机接入过程，向RAN发送标识信息。
不同点在于，S1317中，RAN不会向该终端#1发送执行命令，因此终端#1也不会向RAN发送执行结果。
S1318，RAN根据CN隧道信息#2向UPF发送数据#7(第一数据的又一例)，进一步，UPF根据AS隧道信息向AS发送数据#7。
其中，数据#7包括终端#1的执行信息，即终端#1的标识和/或数量，应理解，此时数量的值为1。
S1319，若AF还有后续的执行命令，则AF通过用户面向RAN发送执行命令。
具体地，AF通过AS向UPF发送数据#8，进一步，UPF向RAN发送数据#8。其中，数据#8包括执行命令。
S1320，RAN向终端#1发送执行命令。
S1321，终端#1向RAN发送执行结果。
S1322，RAN根据CN隧道信息#2向UPF发送数据#9(第一数据的一例)，进一步，UPF根据AS隧道信息向AS发送数据#9。
其中，数据#9包括终端#1的执行信息，即执行结果。
S1323，AF通过用户面向RAN发送终端#1盘点完成的指示(第一信息的又一例)。
具体地，AF通过AS向UPF发送数据#10，进一步，UPF向RAN发送数据#10。其中，数据#10包括信息#1，信息#1用于指示终端#1盘点完成的指示。
S1324，UPF向SMF发送数据报告#4。
数据报告#4包括数据#7中的终端#1的执行信息，即终端#1的标识和/或数量1至少一种。
可选地，数据报告#4还包括数据9中的终端#1的执行信息，即终端#1的执行结果。
可选地，数据报告#4还可以包括数据#8中包括的终端#1的信息，即执行命令。
可选地，数据报告#4还包括数据#10中的信息，即信息#1。
可选地，数据报告#4还包括RAN的标识。
S1325，SMF向CHF发送计费信息#7(第二计费信息的又一例)。
其中，计费信息#7包括数据报告#4中的信息，即终端#1的标识、数量1、执行命令、执行结果至少一种。
可选地，计费信息#7还包括RAN的标识。
可选地，S1325可以不执行，也就是，SMF也可以先保存数据报告#4中的终端#1的执行信息，待RAN盘点完成后，集中向CHF发送。具体见S1330-S1331。
S1326，CHF返回应答消息。
可选地，若S1225不执行，则S1226也不执行。
S1327，RAN确定针对该终端#1的盘点完成，RAN向所有选择的标签发送下一个标签的查询请求，继续执行步骤S1317。
进一步，RAN、目标终端、UPF、SMF、终端管理功能网元、AS、CHF可以继续执行S1318至S13227。
S1328，RAN判断选择的所有标签盘点完成，向SMF发送信息#2(第二信息的一例)，该信息#2用于指示RAN覆盖区域内的目标终端盘点完成，或者说，RAN盘点结束。
应理解，RAN可以经过AMF向SMF发送信息#2。
应理解，AMF在接收到信息#2后，可以向SMF发送信息#2，或者，也可以向SMF发送释放请求消息，用于请求释放隧道#1。
若S1325至S1326不执行，则方法1300还包括S1329至S1330。
S1329，SMF向CHF发送计费信息#8(第二计费信息的又一例)。
其中，计费信息#8包括SMF保存的多个终端#1的执行信息。应理解，多个终端#1的执行信息汇总成了目标终端中RAN覆盖区域内的终端的执行信息，即RAN获取的终端的标识列表、RAN获取的终端的数量、每个终端对应的执行结果的列表至少一种。
可选地，计费信息#8还包括RAN的标识。
也就是，SMF可以在接收到终端#1的执行信息后，不发送计费信息#7，而是保存终端#1的执行信息，在接收到信息#2后，发送计费信息#8，计费信息#8包括其保存多个终端#1的执行信息，从而请求CHF对RAN覆盖区域内的目标终端的盘点过程进行计费。
S1330，CHF向SMF返回应答消息。
CHF可以根据计费信息#8生成RAN盘点其覆盖区域内的终端的过程的话单。
S1331，SMF发起隧道释放。
S1332，SMF向CHF发送计费请求消息#10。
S1333，CHF向终端管理功能网元返回应答消息。
S1334，终端管理功能网元确定目标终端盘点完成或者确定定时器超时。
S1335，终端管理功能网元向CHF发送计费请求消息#11(第八消息的又一例)。
其中，计费请求消息#11中包括Stop指示，该stop指示用于指示CHF关闭针对计费请求消息#8的计费。
S1336，CHF向终端管理功能网元返回应答消息。
S1331至S1336参考S1228至S1233，在此不再赘述。
图13所示的方法1300介绍了RAN通过UPF上报盘点结果的盘点场景下的计费，且在该盘点场景下，执行命令是由AF发起的。因此，本申请实施例提供的计费方法能够适用于各种不同的盘点场景，具有更好的兼容性和灵活性。
可选地，结合方法600和方法1300，本申请还可以提供终端管理功能网元保存执行命令、发起执行命令，并由RAN通过UPF上报盘点结果的场景下的计费。具体步骤可以结合方法600和方法1300，在此不再赘述。
一种可能的实现方式，图12和图13中终端管理功能网元可以和NEF合设，上述的终端管理功能网元执行的动作可以理解为NEF执行的动作。
该实现方式下，图12和图13所示的方法流程可以应用于图14中的(a)所示的网络 架构中。
另一种可能的实现方式，图12和图13中终端管理功能网元可以为新增的独立功能网元，能够用于转发AF和AMF之间的盘点请求和响应。
该实现方式下，图12和图13所示的方法流程可以应用于图14中的(b)所示的网络架构中。
又一种可能的实现方式，图12和图13中终端管理功能网元可以为新增的独立功能网元，能够用于转发NEF和AMF之间的盘点请求和响应，也就是说图4中所示的终端管理功能网元和AF之间的盘点请求和响应需要通过NEF转发。
该实现方式下，图12和图13所示的方法流程可以应用于图14中的(c)所示的网络架构中。
又一种可能的实现方式，图12和图13中终端管理功能网元可以和AMF合设，AMF和终端管理功能网元之间的交互可以看成内部交互。
该实现方式下，图12和图13所示的方法流程可以应用于图14中的(d)所示的网络架构中。
应理解，本申请实施例中的图3至图14所示的具体的例子只是为了帮助本领域技术人员更好地理解本申请实施例，而非限制本申请实施例的范围。还应理解，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
还应理解，在本申请的各个实施例中，如果没有特殊说明以及逻辑冲突，不同的实施例之间的术语和/或描述具有一致性、且可以相互引用，不同的实施例中的技术特征根据其内在的逻辑关系可以组合形成新的实施例。
还应理解，在上述一些实施例中，主要以现有的网络架构中的网元为例进行了示例性说明(如AF、AMF、SMF等等)，应理解，对于网元的具体形式本申请实施例不作限定。例如，在未来可以实现同样功能的网元都适用于本申请实施例。
可以理解的是，上述各个方法实施例中，由网络设备(如各个网元)实现的方法和操作，也可以由可用于网络设备的部件(例如芯片或者电路)实现。
以上结合图3至图14详细说明了本申请提供的计费方法，下面介绍本申请提供的通信装置。应理解，装置实施例的描述与方法实施例的描述相互对应，因此，未详细描述的内容可以参见上文方法实施例，为了简洁，部分内容不再赘述。
图15是本申请提供的通信装置1500的示意性框图。该装置1500包括收发单元1510和处理单元1520。收发单元1510可以实现相应的通信功能，处理单元1520用于进行数据处理。收发单元1510还可以称为通信接口或通信单元。
可选地，该装置1500还可以包括存储单元，该存储单元可以用于存储指令和/或数据，处理单元1520可以读取存储单元中的指令和/或数据，以使得装置实现前述方法实施例。
该装置1500可以用于执行上文方法实施例中网络设备(如上述各个网元)所执行的动作，这时，该装置1500可以为网络设备或者可配置于网络设备的部件，收发单元1510用于执行上文方法实施例中网络设备的收发相关的操作，处理单元1520用于执行上文方法实施例中网络设备处理相关的操作。
作为一种设计，该装置1500用于执行上文方法300实施例中终端管理功能网元所执 行的动作。
具体地，收发单元1510，用于：接收来自应用的应用网元的第一消息，第一消息用于请求对目标终端执行第一操作；发送第二消息，第二消息用于请求启动对目标终端的第一操作的计费；发送第一计费信息，第一计费信息包括目标终端中的一个或多个终端的执行信息，第一计费信息用于对一个或多个终端执行第一操作的过程计费。
可选地，一个或多个终端包括第一终端，收发单元1510还用于：获取第一信息，
其中，第一信息用于指示第一终端的第一操作执行完成；或，第一信息包括第一终端的执行信息。
可选地，第一信息来自于第一接入网设备或应用网元，其中，第一接入网设备用于对第一终端执行第一操作。
可选地，第一终端的执行信息包括以下至少一项：第一终端的标识、第一终端执行第一操作的执行结果。
可选地，一个或多个终端包括第一接入网设备的覆盖区域内的终端，收发单元1510还用于：接收来自于第一接入网设备的第二信息，其中，第二信息用于指示目标终端中第一接入网设备的覆盖区域内的终端的第一操作执行完成；或，第二信息包括目标终端中第一接入网设备的覆盖区域内的终端的执行信息。
可选地，目标终端中第一接入网设备的覆盖区域内的终端的执行信息包括以下至少一项：第一接入网设备所获取的终端的标识列表、第一接入网设备所获取的终端的数量、第一接入网设备所获取的终端执行第一操作的执行结果。
可选地，处理单元1520，用于确定目标终端的第一操作执行完成；收发单元1510还用于：发送第三消息，第三消息用于请求关闭对目标终端的第一操作的计费。
可选地，处理单元1520还用于：根据第一消息确定一个或多个接入网设备；处理单元1520具体用于：根据一个或多个接入网设备的第二信息确定目标终端的第一操作执行完成，第二信息用于指示目标终端中一个或多个接入网设备的覆盖区域内的终端的第一操作执行完成。
可选地，处理单元1520还用于：当接收到第一消息时，启动目标终端执行第一操作的定时器；在定时器超时的情况下，发送第三消息，第三消息用于请求关闭对目标终端的第一操作的计费。
该装置1500可实现对应于根据本申请实施例的方法实施例中的终端管理功能网元的步骤或者流程，该装置1500可以包括用于执行方法300、500、600、700中的终端管理功能网元执行的方法的单元，或包括用于执行方法900、1000中的终端管理功能网元-CP执行的方法的单元，或包括用于执行方法400、1200、1300中的终端管理功能网元执行的方法的单元。并且，该装置1500中的各单元和上述其他操作和/或功能分别为了实现方法实施例中的相应流程。
应理解，各单元执行上述相应步骤的具体过程在上述各方法实施例中已经详细说明，为了简洁，在此不再赘述。
作为另一种设计，该装置1500用于执行上文方法实施例中会话管理网元所执行的动作。
具体地，收发单元1510，用于：接收第四消息，第四消息用于请求建立第一会话， 第一会话用于传输目标终端中一个或多个终端执行第一操作的执行信息，第四消息包括第一标识，第一标识用于标识终端管理功能网元发起的对目标终端执行第一操作的计费；发送第五消息，第五消息用于请求启动对目标终端的第一操作的计费，第五消息包括第一标识；发送第二计费信息，第二计费信息包括目标终端中的一个或多个终端的执行信息，第二计费信息用于对一个或多个终端执行第一操作的过程计费。
可选地，一个或多个终端包括第一终端，收发单元1510还用于：接收第一信息，第一信息用于指示第一终端的第一操作执行完成，或，第一信息包括第一终端的执行信息。
可选地，第一信息来自于第一接入网设备或应用网元，其中，第一接入网设备用于对第一终端执行第一操作。
可选地，第一终端的执行信息包括以下至少一项：第一终端的标识、第一终端执行第一操作的执行结果。
可选地，一个或多个终端包括第一接入网设备的覆盖区域内的终端，收发单元1510还用于：接收来自第一接入网设备的第二信息，第二信息用于指示第一接入网设备的覆盖范围内的终端的第一操作执行完成，或，第二信息包括目标终端中第一接入网设备的覆盖区域内的终端的执行信息。
可选地，目标终端中第一接入网设备的覆盖区域内的终端的执行信息包括以下至少一项：第一接入网设备所获取的终端的标识列表、第一接入网设备所获取的终端的数量、第一接入网设备所获取的终端执行第一操作的执行结果。
可选地，收发单元1510还用于：发送第六消息，第六消息用于请求关闭对目标终端的第一操作的计费。
该装置1500可实现对应于根据本申请实施例的方法实施例中的会话管理网元的步骤或者流程，该装置1500可以包括用于执行方法400中的会话管理网元执行的方法的单元，或包括方法1200、1300中的SMF执行的方法的单元。并且，该装置1500中的各单元和上述其他操作和/或功能分别为了实现方法实施例中的相应流程。
应理解，各单元执行上述相应步骤的具体过程在上述各方法实施例中已经详细说明，为了简洁，在此不再赘述。
作为另一种设计，该装置1500用于执行上文方法实施例中第一用户面网元所执行的动作。
具体地，收发单元1510，用于：接收第一数据，第一数据包括第一信息或第二信息；发送第一信息或第二信息，
其中，第一信息用于指示第一终端的第一操作执行完成；或，第一信息包括第一终端的执行信息；
其中，第二信息用于指示第一接入网设备的覆盖区域内的终端的第一操作执行完成；或，第二信息包括第一接入网设备的覆盖范围内的终端的执行信息。
可选地，该装置1500为终端管理用户面功能网元或用户面网元。
可选地，第一终端的执行信息包括以下至少一项：第一终端的标识、第一终端执行第一操作的执行结果。
可选地，第一接入网设备的覆盖范围内的终端的执行信息包括以下至少一项：
第一接入网设备所获取的终端的标识列表、第一接入网设备所获取的终端的数量、第 一接入网设备所获取的终端执行第一操作的执行结果。
可选地，收发单元1510还用于：接收策略规则，该策略规则用于检测第一信息或第二信息。
该装置1500可实现对应于根据本申请实施例的方法实施例中的第一用户面网元的步骤或者流程，该装置1500可以包括用于执行方法300中的用户面网元执行的方法的单元，或包括用于执行方法400中的终端管理用户面网元执行的方法的单元，或包括用于执行方法900、1000中的UPF执行的方法的单元，或包括用于执行方法1200、1300中的终端管理功能网元-UP执行的方法的单元。并且，该装置1500中的各单元和上述其他操作和/或功能分别为了实现方法实施例中的相应流程。
应理解，各单元执行上述相应步骤的具体过程在上述各方法实施例中已经详细说明，为了简洁，在此不再赘述。
上文实施例中的处理单元1220可以由至少一个处理器或处理器相关电路实现。收发单元1210可以由收发器或收发器相关电路实现。存储单元可以通过至少一个存储器实现。
图16是本申请提供的通信装置的又一示意图。如图16所示，该装置1600包括处理器1610，还可以包括一个或多个存储器1620。处理器1610与存储器1620耦合，存储器1620用于存储计算机程序或指令和/或数据，处理器1610用于执行存储器1620存储的计算机程序或指令和/或数据，使得上文方法实施例中的方法被执行。可选地，该装置1600包括的处理器1610为一个或多个。
可选地，该存储器1620可以与该处理器1610集成在一起，或者分离设置。
可选地，如图16所示，该装置1600还可以包括收发器1630，收发器1630用于信号的接收和/或发送。例如，处理器1610用于控制收发器1630进行信号的接收和/或发送。
作为一种方案，该装置1600用于实现上文方法实施例中由网络设备(如上述各个网元)执行的操作。
本申请实施例还提供一种计算机可读存储介质，其上存储有用于实现上述方法实施例中由网络设备(如各个网元)执行的方法的计算机指令。
例如，该计算机程序被计算机执行时，使得该计算机可以实现上述方法实施例中由网络设备执行的方法。
本申请实施例还提供一种包含指令的计算机程序产品，该指令被计算机执行时使得该计算机实现上述方法实施例中由网络设备(如各个网元)执行的方法。
本申请实施例还提供一种通信系统，该通信系统包括上文实施例中的网络设备(如各个网元)，如包括终端管理功能网元和计费网元。
上述提供的任一种装置中相关内容的解释及有益效果均可参考上文提供的对应的方法实施例，此处不再赘述。
应理解，本申请实施例中提及的处理器可以是中央处理单元(central processing unit，CPU)，还可以是其他通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
还应理解，本申请实施例中提及的存储器可以是易失性存储器和/或非易失性存储器。 其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)。例如，RAM可以用作外部高速缓存。作为示例而非限定，RAM可以包括如下多种形式：静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。
在本申请实施例中，“示例的”、“例如”等词用于表示作例子、例证或说明。本申请中被描述为“示例”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言，使用示例的一词旨在以具体方式呈现概念。
应理解，说明书通篇中提到的“实施例”意味着与实施例有关的特定特征、结构或特性包括在本申请的至少一个实施例中。因此，在整个说明书各个实施例未必一定指相同的实施例。此外，这些特定的特征、结构或特性可以任意适合的方式结合在一个或多个实施例中。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。本申请中所有节点、消息的名称仅仅是本申请为描述方便而设定的名称，在实际网络中的名称可能不同，不应理解本申请限定各种节点、消息的名称，相反，任何具有和本申请中用到的节点或消息具有相同或类似功能的名称都视作本申请的方法或等效替换，都在本申请的保护范围之内。
还应理解，在本申请中，“当…时”、“若”以及“如果”均指在某种客观情况下UE或者基站会做出相应的处理，并非是限定时间，且也不要求UE或基站实现时一定要有判断的动作，也不意味着存在其它限定。
需要说明的是，本申请实施例中，“预先设定”、“预先配置”等可以通过在设备(例如，终端设备)中预先保存相应的代码、表格或其他可用于指示相关信息的方式来实现，本申请对于其具体的实现方式不做限定，例如本申请实施例中预设的规则、预设的常数等。
另外，本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。
本文中术语“……中的至少一个”或“……中的至少一种”，表示所列出的各项的全部或任意组合，例如，“A、B和C中的至少一种”，可以表示：单独存在A，单独存在B，单独存在C，同时存在A和B，同时存在B和C，同时存在A、B和C这六种情况。本文中的“至少一个”表示一个或者多个。“多个”表示两个或者两个以上。
应理解，在本申请各实施例中，“与A相应的B”表示B与A相关联，根据A可以确定B。但还应理解，根据A确定B并不意味着仅仅根据A确定B，还可以根据A和/或其它信息确定B。术语“包括”、“包含”、“具有”及它们的变形都意味着“包括但不限于”，除 非是以其他方式另外特别强调。
应理解，在本申请中示出的第一、第二以及各种数字编号(例如，“#1”、“#2”等)仅为描述方便，用于区分的对象，并不用来限制本申请实施例的范围。例如，区分不同消息等。而不是用于描述特定的顺序或先后次序。应该理解这样描述的对象在适当情况下可以互换，以便能够描述本申请的实施例以外的方案。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (33)

  1. 一种计费的方法，其特征在于，包括：
    终端管理功能网元接收来自应用的应用网元的第一消息，所述第一消息用于请求对目标终端执行第一操作；
    所述终端管理功能网元发送第二消息，所述第二消息用于请求启动对所述目标终端的所述第一操作的计费；
    所述终端管理功能网元发送第一计费信息，所述第一计费信息包括所述目标终端中的一个或多个终端的执行信息，所述第一计费信息用于对所述一个或多个终端执行所述第一操作的过程计费。
  2. 根据权利要求1所述的方法，其特征在于，所述一个或多个终端包括第一终端，在所述终端管理功能网元发送第一计费信息之前，所述方法还包括：
    所述终端管理功能网元获取第一信息，
    其中，所述第一信息用于指示所述第一终端的所述第一操作执行完成；或，
    所述第一信息包括所述第一终端的执行信息。
  3. 根据权利要求2所述的方法，其特征在于，所述第一信息来自于第一接入网设备或所述应用网元，
    其中，所述第一接入网设备用于对所述第一终端执行所述第一操作。
  4. 根据权利要求2或3所述的方法，其特征在于，所述第一终端的执行信息包括以下至少一项：
    所述第一终端的标识、所述第一终端执行所述第一操作的执行结果。
  5. 根据权利要求1所述的方法，其特征在于，所述一个或多个终端包括第一接入网设备的覆盖区域内的终端，在所述终端管理功能网元发送第一计费信息之前，所述方法还包括：
    所述终端管理功能网元接收来自于所述第一接入网设备的第二信息，
    其中，所述第二信息用于指示所述目标终端中所述第一接入网设备的覆盖区域内的终端的所述第一操作执行完成；或，
    所述第二信息包括所述目标终端中所述第一接入网设备的覆盖区域内的终端的执行信息。
  6. 根据权利要求5所述的方法，其特征在于，所述目标终端中所述第一接入网设备的覆盖区域内的终端的执行信息包括以下至少一项：
    所述第一接入网设备所获取的终端的标识列表、所述第一接入网设备所获取的终端的数量、所述第一接入网设备所获取的终端执行所述第一操作的执行结果。
  7. 根据权利要求1至6中任一项所述的方法，其特征在于，所述方法还包括：
    所述终端管理功能网元确定所述目标终端的所述第一操作执行完成；
    所述终端管理功能网元发送第三消息，所述第三消息用于请求关闭对所述目标终端的所述第一操作的计费。
  8. 根据权利要求7所述的方法，其特征在于，所述方法还包括：
    所述终端管理功能网元根据所述第一消息确定一个或多个接入网设备；
    所述终端管理功能网元确定所述目标终端的所述第一操作执行完成，包括：
    所述终端管理功能网元根据所述一个或多个接入网设备的第二信息确定所述目标终端的所述第一操作执行完成，所述第二信息用于指示所述目标终端中所述一个或多个接入网设备的覆盖区域内的终端的所述第一操作执行完成。
  9. 根据权利要求1至6中任一项所述的方法，其特征在于，所述方法还包括：
    当接收到所述第一消息时，所述终端管理功能网元启动所述目标终端执行所述第一操作的定时器；
    在所述定时器超时的情况下，所述终端管理功能网元发送第三消息，所述第三消息用于请求关闭对所述目标终端的第一操作的计费。
  10. 一种计费的方法，其特征在于，包括：
    会话管理网元接收第四消息，所述第四消息用于请求建立第一会话，所述第一会话用于传输目标终端中一个或多个终端执行第一操作的执行信息，所述第四消息包括第一标识，所述第一标识用于标识终端管理功能网元发起的对目标终端执行所述第一操作的计费；
    所述会话管理网元发送第五消息，所述第五消息用于请求启动对所述目标终端的所述第一操作的计费，所述第五消息包括所述第一标识；
    所述会话管理网元发送第二计费信息，所述第二计费信息包括所述目标终端中的一个或多个终端的执行信息，所述第二计费信息用于对所述一个或多个终端执行所述第一操作的过程计费。
  11. 根据权利要求10所述的方法，其特征在于，所述一个或多个终端包括第一终端，在所述会话管理网元发送第二计费信息之前，所述方法还包括：
    所述会话管理网元接收第一信息，所述第一信息用于指示所述第一终端的所述第一操作执行完成，或，所述第一信息包括所述第一终端的执行信息。
  12. 根据权利要求11所述的方法，其特征在于，所述第一信息来自于第一接入网设备或所述应用网元，
    其中，所述第一接入网设备用于对所述第一终端执行所述第一操作。
  13. 根据权利要求14或12所述的方法，其特征在于，所述第一终端的执行信息包括以下至少一项：所述第一终端的标识、所述第一终端执行所述第一操作的执行结果。
  14. 根据权利要求10所述的方法，其特征在于，所述一个或多个终端包括第一接入网设备覆盖区域内的终端，在所述会话管理网元发送第二计费信息之前，所述方法还包括：
    所述会话管理网元接收来自所述第一接入网设备的第二信息，所述第二信息用于指示所述第一接入网设备的覆盖范围内的终端的所述第一操作执行完成，或，所述第二信息包括所述目标终端中所述第一接入网设备的覆盖区域内的终端的执行信息。
  15. 根据权利要求14所述的方法，其特征在于，所述目标终端中所述第一接入网设备的覆盖区域内的终端的执行信息包括以下至少一项：
    所述第一接入网设备所获取的终端的标识列表、所述第一接入网设备所获取的终端的数量、所述第一接入网设备所获取的终端执行所述第一操作的执行结果。
  16. 根据权利要求10至15中任一项所述的方法，其特征在于，所述方法还包括：
    所述会话管理网元发送第六消息，所述第六消息用于请求关闭所述对所述目标终端的 所述第一操作的计费。
  17. 一种计费的方法，其特征在于，包括：
    第一用户面网元接收第一数据，所述第一数据包括第一信息或第二信息；
    所述第一用户面网元发送所述第一信息或所述第二信息，
    其中，所述第一信息用于指示第一终端的第一操作执行完成；或，所述第一信息包括所述第一终端的执行信息；
    其中，所述第二信息用于指示第一接入网设备的覆盖区域内的终端的第一操作执行完成；或，所述第二信息包括所述第一接入网设备的覆盖范围内的终端的执行信息。
  18. 根据权利要求17所述的方法，其特征在于，所述第一用户面网元为终端管理用户面功能网元或用户面网元。
  19. 根据权利要求17或18所述的方法，其特征在于，所述第一终端的执行信息包括以下至少一项：
    所述第一终端的标识、所述第一终端执行所述第一操作的执行结果。
  20. 根据权利要求17或18所述的方法，其特征在于，所述第一接入网设备的覆盖范围内的终端的执行信息包括以下至少一项：
    所述第一接入网设备所获取的终端的标识列表、所述第一接入网设备所获取的终端的数量、所述第一接入网设备所获取的终端执行所述第一操作的执行结果。
  21. 根据权利要求17至20中任一项所述的方法，其特征在于，所述方法还包括：
    所述第一用户面网元接收策略规则，所述策略规则用于检测所述第一信息或所述第二信息。
  22. 一种计费的方法，其特征在于，包括：
    终端管理功能网元接收来自应用的应用网元的第七消息，所述第七消息用于请求对目标终端执行第一操作；
    所述终端管理功能网元向计费网元发送第八消息，所述第八消息用于请求启动对所述目标终端的所述第一操作的计费，所述第八消息包括第一标识，所述第一标识用于标识所述终端管理功能网元发起的对所述目标终端执行所述第一操作的计费；
    所述终端管理功能网元向接入与移动性管理网元发送第九消息，所述第九消息用于请求对所述目标终端执行所述第一操作，所述第九消息包括所述第一标识；
    所述接入与移动性管理网元向会话管理网元发送第四消息，所述第四消息用于请求建立第一会话，所述第一会话用于传输所述目标终端的执行，所述第四消息包括所述第一标识；
    所述会话管理网元向所述计费网元发送第五消息，所述第五消息用于请求启动对所述目标终端的所述第一操作的计费，所述第五消息包括所述第一标识；
    所述计费网元根据所述第一标识关联所述第八消息和所述第五消息。
  23. 根据权利要求所述的方法，其特征在于，所述包括第一终端，所述方法还包括：
    所述会话管理网元第一信息，所述第一信息用于指示所述第一终端的所述第一操作执行完成，或，所述第一信息包括所述第一终端的执行；
    所述会话管理网元发送第二计费信息，所述第二计费信息包括所述第一终端的信息；
    所述计费网元根据所述第二计费信息生成所述第一终端执行所述第一操作的话单。
  24. 根据权利要求23所述的方法，其特征在于，所述第一终端的信息包括所述第一终端的标识所述第一终端执行所述第一操作的执行结果。
  25. 根据权利要求22所述的方法，其特征在于，所述一个或多个终端包括第一接入网设备覆盖区域内的终端，所述方法还包括：
    所述第一接入网设备向所述会话管理网元发送第二信息，所述第二信息用于指示所述目标终端中所述第一接入网设备的覆盖区域内的终端的所述第一操作执行完成，或，所述第二信息包括所述目标终端中所述第一接入网设备的覆盖区域内的终端的执行信息；
    所述会话管理网元发送第二计费信息，所述第二计费信息包括所述第一接入网设备覆盖区域内的终端的执行信息；
    所述计费网元根据所述第二计费信息生成所述目标终端中所述第一接入网设备覆盖区域内的终端执行所述第一操作的话单。
  26. 根据权利要求25所述的方法，其特征在于，所述第一接入网设备覆盖区域内的终端的执行信息包括以下至少一项：
    所述第一接入网设备所获取的终端的标识列表、所述第一接入网设备所获取的终端的数量、所述第一接入网设备所获取的终端执行所述第一操作的执行结果。
  27. 根据权利要求22至26中任一项所述的方法，其特征在于，所述方法还包括：
    所述会话管理网元向所述计费网元发送第六消息，所述第六消息用于请求关闭所述对所述目标终端的所述第一操作的计费。
  28. 根据权利要求22至27中任一项所述的方法，其特征在于，所述方法还包括：
    所述终端管理功能网元确定所述目标终端的所述第一操作执行完成；
    所述终端管理功能网元向所述计费网元发送第十请求消息，所述第十请求消息用于请求关闭所述目标终端的所述第一操作的计费。
  29. 根据权利要求22至27中任一项所述的方法，其特征在于，所述方法还包括：
    当接收到所述第七消息时，所述终端管理功能网元启动所述目标终端执行所述第一操作的定时器；
    在所述定时器超时的情况下，所述终端管理功能网元向所述计费网元发送第十请求消息，所述第十请求消息用于请求关闭所述目标终端的所述第一操作的计费。
  30. 一种通信的装置，其特征在于，包括用于执行如权利要求1至9中任一项所述的方法的单元或模块，或包括用于执行如权利要求10至16中任一项所述的方法的单元或模块，或包括用于执行如权利要求17至21中任一项所述的方法的单元或模块。
  31. 一种通信系统，其特征在于，包括用于执行如权利要求22至29中任一项所述的方法的设备。
  32. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质中存储有计算机指令，当所述计算机指令在计算机上运行时，如权利要求1至21中任一项所述的方法被执行。
  33. 一种计算机程序产品，其特征在于，包含指令，当所述计算机指令在计算机上运行时，如权利要求1至21中任一项所述的方法被执行。
PCT/CN2023/073131 2022-03-17 2023-01-19 一种计费的方法和通信装置 WO2023173937A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210262669.2 2022-03-17
CN202210262669.2A CN116801208A (zh) 2022-03-17 2022-03-17 一种计费的方法和通信装置

Publications (1)

Publication Number Publication Date
WO2023173937A1 true WO2023173937A1 (zh) 2023-09-21

Family

ID=88022270

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/073131 WO2023173937A1 (zh) 2022-03-17 2023-01-19 一种计费的方法和通信装置

Country Status (2)

Country Link
CN (1) CN116801208A (zh)
WO (1) WO2023173937A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102006185A (zh) * 2010-11-15 2011-04-06 中国联合网络通信集团有限公司 物联网终端计费查询方法和物联网终端计费查询系统
CN103188082A (zh) * 2011-12-30 2013-07-03 中国移动通信集团公司 一种物联网终端计费管理方法及系统
CN112312339A (zh) * 2019-07-31 2021-02-02 华为技术有限公司 计费方法、计费系统和通信装置
CN112312340A (zh) * 2019-08-02 2021-02-02 华为技术有限公司 计费的方法、装置及系统
WO2022141498A1 (zh) * 2020-12-31 2022-07-07 华为技术有限公司 一种计费方法、装置和系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102006185A (zh) * 2010-11-15 2011-04-06 中国联合网络通信集团有限公司 物联网终端计费查询方法和物联网终端计费查询系统
CN103188082A (zh) * 2011-12-30 2013-07-03 中国移动通信集团公司 一种物联网终端计费管理方法及系统
CN112312339A (zh) * 2019-07-31 2021-02-02 华为技术有限公司 计费方法、计费系统和通信装置
CN112312340A (zh) * 2019-08-02 2021-02-02 华为技术有限公司 计费的方法、装置及系统
WO2022141498A1 (zh) * 2020-12-31 2022-07-07 华为技术有限公司 一种计费方法、装置和系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
JI HAIJIN, CHEN FUBING;HUA CHENJIANG: "The Accounting System Design based on RFID", INTELLIGENT COMPUTER AND APPLICATIONS, vol. 1, no. 4, 1 December 2011 (2011-12-01), pages 68 - 69, XP055947000, ISSN: 2095-2163 *

Also Published As

Publication number Publication date
CN116801208A (zh) 2023-09-22

Similar Documents

Publication Publication Date Title
WO2020073855A1 (zh) 建立会话的方法和装置以及发送报文的方法和装置
JP5957543B2 (ja) スマートカードの初期パーソナライゼーション
EP3634081B1 (en) Session context deletion methods and apparatus
CN109691059B (zh) 用于ip版本的选择的方法、无线通信设备、以及网络节点
CN105340212A (zh) 用于生成在设备至设备通信中的密钥的方法和装置
WO2021068830A1 (zh) 用于多播传输的方法和装置
CN109428853A (zh) 一种通信方法和相关设备
EP3579589B1 (en) Session migration method and device
US11330475B2 (en) Method and apparatus for providing rule information in wireless communication system
WO2023173937A1 (zh) 一种计费的方法和通信装置
EP4109939A1 (en) Message forwarding method and apparatus
WO2021184219A1 (zh) 连接云端的方法和终端设备
CN113573297B (zh) 一种通信方法及装置
WO2020200297A1 (zh) 选择会话管理网元的方法和装置
WO2024027339A1 (zh) 一种盘点方法及装置
EP4090061B1 (en) Wireless communication method, terminal device and network element
CN105813064A (zh) 服务开通的处理方法和网元
WO2024066436A1 (zh) 一种通信方法及装置
WO2023116735A1 (zh) 一种终端管理方法及装置
WO2024104246A1 (zh) 通信方法和通信装置
WO2023207462A1 (zh) 一种安全验证方法及装置
WO2022218099A1 (zh) 组播通信方法及通信装置
WO2023142815A1 (zh) 通信的方法和装置
WO2024067046A1 (zh) 一种通信方法及装置
WO2023246431A1 (zh) 一种通信方法和装置

Legal Events

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

Ref document number: 23769448

Country of ref document: EP

Kind code of ref document: A1